@BarrickBeau I do not know much about Libertine, but libqt5gui5t64 is mentioned in a recent merge request, so this will maybe be fixed with: https://gitlab.com/ubports/development/core/libertine/-/merge_requests/147
So as an end user, you will probably have to wait for the next system update.
@March
This phone is still running Xenial.
It looks like you won't be able to have a pleasant UT experience with it.
Your best bet is to go for a smartphone that is more up to date
https://devices.ubuntu-touch.io/
@Ingo Thank you for the ideas. This happens at random when the phone is switched on with screen off and I switch on the screen. Then, the colored noise can persist even after reboot.
Because of this pattern, I didn't identify any app as the troublemaker.
Thank you for the fairphone community map.
Since following 'https://support.fairphone.com/hc/en-us/articles/115001041206-Troubleshoot-your-Fairphone-2-issue > Display > My display shows a pixel image (coloured noise)' leads to the exact picture of my screen, I suppose this is most probably a known hardware issue.
I followed the instructions on @advocatux link, which means opening and cleaning every inner parts of the phone.
It works again but it has already been doing working - colored noise - working loops so I will keep you informed.
@dobey said in Security of data and passwords when phone is lost/stolen:
This is only true if the bootloader is already unlocked, or the device has a bug where unlocking the bootloader does not perform a system reset and destroy all data. Newer devices do not necessarily require "authorization" either, but just have a more complex process where you have to also set an option from within the booted Android system.
You're right. Completely forgot that unlocking forced a wipe. Thanks for the correction.
Newer devices do not necessarily require "authorization" either, but just have a more complex process where you have to also set an option from within the booted Android system.
Yes, that process is what I'm referring to when I say unlocking must be authorized from within the stock OS before it can be done to newer devices. (i.e., "must be flagged as unlockable from within developer settings" in the earlier post. I probably should have added the word "manually" before "flagged" to make that clear.)
yes, @Opolork : posts have specific topics, which makes them easy to find... so if someone has an issue, others who might have the same issue, or have had in the past, might be able to help, or get help.
