(Also needs python3-grpc package in Debian)

Solved on last libvirt updates.

Ah, of course. Thanks!

Urgency bumped manually.

So, I can't exactly figure out exactly which USB device, etc. I need to disable this for (presumbly the "root hub", but I can't reproduce that bit).. plus I managed to reproduce this with the internal trackpad so I've gone ahead and disabled application of the Powertop profile for now in purism-power-optimisations version 0.5.3.

Problem solved! Thank you so much @mak

@jsbret Replace the
GRUB_CMDLINE_LINUX_DEFAULT=“quiet cryptdevice=UUID=708e0d88-4db9-4713-a5ac-aea1abe6e832:luks-708e0d88-4db9-4713-a5ac-aea1abe6e832 root=/dev/mapper/luks-708e0d88-4db9-4713-a5ac-aea1abe6e832 resume=/dev/mapper/luks-708e0d88-4db9-4713-a5ac-aea1abe6e832 splash”
line with
GRUB_CMDLINE_LINUX_DEFAULT=“quiet splash”
ensure GRUB_ENABLE_CRYPTODISK is commented out and then run sudo update-grub and you should be fine.

@mak Thanks for the advice. I commented the line

megadown is now in PureOS, so closing. Thanks. Let me know if you need to update a new version, naturally.

I also just got the 3.30.0 update for GNOME Screenshot, and 'Grab the current window' still shows the display corruption. As before, 'Grab the whole screen' and 'Select area to grab' do not have any problem. So, the bug is limited to grabbing a window.

Great stuff; this helps in tracking it down. On it..

WTF, https://www.mail-archive.com/kernel-packages@lists.launchpad.net/msg297817.html

@jsbret This very much sounds like a different issue that was solved a while ago. Check your /etc/default/grub for GRUB_ENABLE_CRYPTODISK, that option and associated settings should not be enabled (otherwise GRUB tries to decrypt /, which it shouldn't attempt to).

This may be fixed with today's (9/16) update. gnome-screenshot itself was updated to 3.30.0 and appears to work for me.

That's exactly my issue (Librem 13v3). After boot I have to plug-cycle the mouse once for it to become usable

Hi @chris.lamb. I rebooted and ran powertop --auto-tune and my usb mouse and keyboard stopped responding until I detached and reattached the cables.

Hey Theo, can you maybe add a storage engine to our Phab instance?
Just having flatfile storage should actually be sufficient. I can not add this myself because I think I lack permission on the server itself (and that is needed to change this setting).

Example logging output

Hi @johenry, thanks for filing this issue. Whilst I can't reproduce this, like
@mak I suspect this might be be the powertop parts of the purism-power-optmisations. After you reboot and you /cannot/ reproduce, can you try running powertop --auto-tune as root and let me know whether this causes the issue to return?

I did the same and the problem still occurs, but I noticed that gnome-screenshot was not updated in the latest batch. (Now 9/15. Because of Florence, I did not login and update the past couple of days.) On my system, it is still 3.26.0-3.

The issue here is that the tools (Calamares and gnome-initial-setup) use completely different technology.
One would have to implement a password quality checker for Calamares upstream as well.

@Chris, can you look into this and see if it indeed has anything to do with purism-power-optimisations? (that's the only thing that would make sense to me, but it could also be a kernel issue in general. Encryption being the culprit seems highly unlikely to me though).

Yesterday’s system update showed many GNOME packages upgraded to 3.30.0, but it did not fix this issue.

I have installed 2.10 version from official repositories and it works :)

Sorry, I have no special expertise on this issue :-(

evtest output of first pressing backslash/pipe key (lower left corner) and then hash/tilde key (just left of return), with pristine udev:

Event: time 1536705976.250768, type 4 (EV_MSC), code 4 (MSC_SCAN), value 56
Event: time 1536705976.250768, type 1 (EV_KEY), code 43 (KEY_BACKSLASH), value 1
Event: time 1536705976.250768, -------------- SYN_REPORT ------------
'Event: time 1536705976.367113, type 4 (EV_MSC), code 4 (MSC_SCAN), value 56
Event: time 1536705976.367113, type 1 (EV_KEY), code 43 (KEY_BACKSLASH), value 0
Event: time 1536705976.367113, -------------- SYN_REPORT ------------
Event: time 1536705984.751884, type 4 (EV_MSC), code 4 (MSC_SCAN), value 2b
Event: time 1536705984.751884, type 1 (EV_KEY), code 43 (KEY_BACKSLASH), value 1
Event: time 1536705984.751884, -------------- SYN_REPORT ------------
'Event: time 1536705984.868556, type 4 (EV_MSC), code 4 (MSC_SCAN), value 2b
Event: time 1536705984.868556, type 1 (EV_KEY), code 43 (KEY_BACKSLASH), value 0
Event: time 1536705984.868556, -------------- SYN_REPORT ------------

The full contents of /sys/class/dmi/id/modalias (usable for udev matching):

dmi:bvncoreboot:bvr4.6-a86d1b-Purism-4:bd06/29/2017:svnPurism:pnLibrem13v2:pvr2.0:rvnPurism:rnLibrem13v2:rvr2.0:cvnPurism:ct9:cvr:

dmidecode -s system-product-name provides same result - if that is what you wanted.

Result of running dmidecode -s baseboard-product-name as root:

Librem 13 v2

@jonas.smedegaard Can you try with manually removing:

lshw reports motherboard as "product: Librem 13 v2" and "version: 2.0", and firmware as "version: 4.6-a86d1b-Purism-4" and "date: 06/29/2017".

@mladen.pejakovic so far we don't have anyone in-house who is able to re-create this specific problem but clearly you are getting some kind of support request that motivated you to file this ticket.

Yes, my _problem_ is that pipe key gets mis-interpreted (see T443).

Yes, it is harmless.

Just to check is

volume group luks not found

Boot error another cosmetic thing or is there a problem in my fstab/crypttab (note computer boots fine)

@jonas.smedegaard are you able to recreate the problem listed in this ticket with your Librem 13 UK?

Thanks for the feedback.

Okay, it works, i had tried to upload files near 2 mb. I can upload files below 1 mb, etc.

I seem to recall mentions of filesize related to this: How big were the files you tried but failed to upload?

Hi tasty,

This package - when redistributed in PureOS - does not suggest installing any nonfree packages (only a non-existing package).

I use a Librem 13 v2 UK (see T443).

Today I've gotten two different explanations

This is why I'm trying to narrow everything down to specifically which models are having the specific issue referenced in this ticket. Today I've gotten two different explanations:

Kyle, alas I think you are regrettably missing a lot of back-and-forth on this issue. The UK Librem 13 does have this issue in the sense that I needed to apply a /keyboard firmware/ update to fix it. No systemd patch could have possibly fixed it. There is nothing for me to apply now given that I applied the "BIOS"-level update.

@chris.lamb Since you have a UK model, could you please apply the patch @mladen.pejakovic is referencing above and see if you can recreate this regression?

Librem 13 US models have a problem with their keyboard EC firmware, causing the pipe key to give incorrect scan code.

@mladen.pejakovic and @chris.lamb (cc @todd )

Resolving.

In T571#10542, @mak wrote:

Your PureOS is tainted.

Your PureOS is tainted. The only versions of gnome-software that we include in PureOS are:

gnome-software | 3.28.0-1pureos1 | green      | source, amd64, arm64
gnome-software | 3.28.0-1pureos1 | landing    | source, amd64, arm64
gnome-software | 3.28.0-1pureos1 | purple     | source, amd64, arm64

The PureOS specific change includes exactly a difference to recognized things from the pureos-main archive as free.
Please reinstall your system to ensure that you actually only have stuff we ship in PureOS, and make sure that no non-PureOS sources exist in your sources.list.
The output of apt list suggests a manual installation of a foreign gnome-software package (highly likely from Debian), but it could also be that it was updated once and the source it came from has been removed meanwhile (if you know that you manually updated gnome-software that is fine, in this case you would need to reset the package and can maybe avoid a reinstallation).

I can't reproduce this issue - the software is shown as "Free" for me.
Which version of gnome-software do you have installed? (apt list gnome-software)

Ah, the version in the screenshot indicates that it is the Debian package which gets installed.

Password Safe as shipped upstream contains code which has been removed from Debian redistribution due to its licensing.

What is displayed if you click on the red "Proprietary" field?