[Touch-packages] [Bug 1982730] Re: Suspending Lubuntu when the "Lock Screen After" box is checked in XScreenSaver results in an error message about xdg-screensaver

Sorry, I thought xscreensaver-systemd would have been started by systemd, because it was in the name, but I'm certain now it's started by lxqt-session, as correctly determined by the original reporter. ** Package changed: systemd (Ubuntu) => lxqt-session (Ubuntu) -- You received this bug notific

[Touch-packages] [Bug 1982730] Re: Suspending Lubuntu when the "Lock Screen After" box is checked in XScreenSaver results in an error message about xdg-screensaver

So I just restarted my system, and I got the bug. BUT, when I killed and reran xscreensaver-systemd, THE BUG DISAPPEARED. This seems to indicate that xscreensaver-systemd is being run too early in the login/startup process. -- You received this bug notification because you are a member of Ubunt

[Touch-packages] [Bug 1982730] Re: Suspending Lubuntu when the "Lock Screen After" box is checked in XScreenSaver results in an error message about xdg-screensaver

Okay, here's an EVER WEIRDER UPDATE! The interactions between xscreensaver and systemd are determined by xscreensaver-systemd. So I killed xscreensaver-systemd and then ran xscreensaver-systemd -verbose to look at the terminal output. AND I COULDN'T REPRODUCE THE BUG!!! Having “lock screen afte

[Touch-packages] [Bug 1982730] Re: Suspending Lubuntu when the "Lock Screen After" box is checked in XScreenSaver results in an error message about xdg-screensaver

So here's the problem: if you have “lock screen after X minutes” enabled in xscreensaver, and you run `systemctl suspend`, then for some reason systemd first LOCKS the screen, which stops the suspend; only after unlocking the screen does the system suspend. If you uncheck “lock screen after X minu

[Touch-packages] [Bug 1889443] Re: "ValueError: ['separator'] has no binary content" when running `apport-unpack /var/crash/...`

I second that! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1889443 Title: "ValueError: ['separator'] has no binary content" when running `apport-unpack /var/crash/...`

[Touch-packages] [Bug 1976313] [NEW] GPG Key Expired

Public bug reported: I get the following error when trying to run `sudo apt update`: W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://ddebs.ubuntu.com focal-updates Release: The following signature

[Touch-packages] [Bug 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)

I have a similar error Ign:16 http://ddebs.ubuntu.com focal-updates Release.gpg Err:17 http://ddebs.ubuntu.com focal Release.gpg The following signatures were invalid: EXPKEYSIG C8CAB6

[Touch-packages] [Bug 1891799] [NEW] upowerd: did not recognise USB path

Public bug reported: >From my jouranlctl upowerd[1045]: did not recognise USB path /sys/devices/platform/USBC000:00/power_supply/ucsi-source-psy- USBC000:001, please report ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: upower 0.99.11-1build2 Uname: Linux 5.8.0-050800-generic x86_64 Appor

[Touch-packages] [Bug 1869078] Re: dhclient then ath10k firmware crashes

It seems to have disappeared when I updated dhclient to 4.4.2 ** Changed in: isc-dhcp (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/

[Touch-packages] [Bug 1869078] [NEW] dhclient then ath10k firmware crashes

Public bug reported: I had to restart so not sure if automatically generated debug-info is relevant. In my journalctl I get this error: Mar 25 21:17:10 dhclient[29542]: For info, please visit https://www.isc.org/software/dhcp/ Mar 25 21:17:10 dhclient[29542]: Mar 25 21:17:10 dhclient[29542]