@kakaroto Is this an issue with PureOS or the Librem laptops? If it is the latter then please track that somewhere at the Puri.sm Gitlab instead.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
May 27 2021
@kakaroto Is this an issue with PureOS or an issue with laptop hardware?
@kakaroto Is this still an issue?
@kakaroto Is this still an issue?
@kakaroto Is this still an issue?
Is this still an issue, now almost 4 years later?
@kakaroto is this still an issue?
According to https://tracker.pureos.net/T315#10888 this feature is unneeded and unwanted in PureOS.
This issue is likely solved in newer releases of PureOS. If not, please shout...
Is this still an issue with PureOS amber and/or byzantium?
This issue should be fixed with newer releases of PureOS. If not, then please shout...
Assuming this was a configuration error, not an issue in PureOS...
This issue was fixed with newer releases of PureOS.
Hopefully this issue was fixed with newer releases of PureOS. If not, then please shout...
Closed due to lack of response from original reporter.
sadly there can be no followup for this issue.
Closing due to lack of response from original reporter.
Closing as a non-issue: Phones are known to work with their memory constraints, which seems the only real concern here.
Hopefully this issue was fixed with newer releases of LibrOffice...
I have no idea what caused that issue, but blindly assume that it is fixed with newer releases of LibrOffice...
@tbernard do you still suffer from this (super frustrating, I imagine) issue now 3 years later?
@EchedeyLR Do I understand you correctly that this issue is solved by now?
Thanks for the detailed issue report, and sorry for the loooong silence.
Sorry for the looong silence.
May 26 2021
I hope you have found a different distro more to your liking, then.
Mabe this is useful: https://salsa.debian.org/smcv/deb-build-snapshot/
May 25 2021
I assume - and sincerely hope - that this issue is solved by now.
No, we do not apply pressure on Debian developers - we collaborate with them.
I would guess this issue to be tied to graphics drivers or the linux kernel. Both have seen many changes since this issue was reported - is it still reproducible with up-to-date amber or byzantium?