Bug#1053427: firefox-esr: YubiKey stopped working on firefox-esr, but works on firefox from official website

Package: firefox-esr Version: 115.2.1esr-1 Severity: normal X-Debbugs-Cc: ono...@gmail.com Dear Maintainer, After the upgrade few versions back, my YubiKey become unusable, but firefox downloaded from official mozilla site - keeps working. You can reproduce it on: https://demo.yubico.com/webaut

Bug#942430: gnome-control-center: Segfaults when 2 monitors attached and switched to Devices tab

Package: gnome-control-center Version: 1:3.34.1-1 Severity: important Dear Maintainer, I run i3wm with i3-gnome: https://github.com/i3-gnome/i3-gnome.git gnome-control-center segfaults when I connect my external monitor and go to devices tab. When I do the same without external monitor - it wor

Bug#788400: systemd-logind only fires suspend on lid close once even though it sees the event

works for me! Thank you very much! 2015-07-03 18:13 GMT+08:00 Michael Biebl : > Control: forwarded -1 https://github.com/systemd/systemd/issues/451 > > Hi Jessie, hi Yaroslav! > > Am 12.06.2015 um 17:21 schrieb Michael Biebl: >> Am 11.06.2015 um 20:44 schrieb Jessica Frazelle: Can you reboot,

Bug#788400: result for "for i in /sys/class/drm/*/status; do echo $i; cat $i; done"

When I do first boot, the requested command output looks like: = for i in /sys/class/drm/*/status; do echo $i; cat $i; done /sys/class/drm/card0-DP-1/status disconnected /sys/class/drm/card0-DP-2/status disconnected /sys/class/drm/card0-eDP-1/status connected /sys/class/drm/card0-HDMI-A-1/statu

Bug#788400: In my case it's:

for i in /sys/class/drm/*/status; do echo $i; cat $i; done /sys/class/drm/card0-DP-1/status unknown /sys/class/drm/card0-DP-2/status unknown /sys/class/drm/card0-eDP-1/status unknown /sys/class/drm/card0-HDMI-A-1/status unknown /sys/class/drm/card0-HDMI-A-2/status unknown -- To UNSUBSCRIBE, emai

Bug#788400: this is duplicate of Bug #784742

I have the same problem bug #784742, you can find there debug log for systemd, here is the interesting part from it: === May 08 17:17:27 x systemd-logind[1457]: Lid closed. May 08 17:17:27 x systemd[1]: Got notification message for unit systemd-logind.service May 08 17:17:27 x systemd[1]:

Bug#784742: Any update?

I've updated my system several times, now I have: Linux kernel: 4.1.0-rc8 and systemd version 220-7 but problem still don't go away.. I'm tired to type "systemctl suspend" each time I need to close the lid. I've never had any problems with suspend with initd for 10 years using debian, and now with

Bug#784742: Acknowledgement (systemd-logind doesn't suspend after first successful suspend)

Do you need any help to debug from me? Is there anything I do for you? I'm tired to type systemctl suspend every time I'm about to close the lid. JFYI, I had updated to version 4.1.0-rc3 problem gone almost completely, system slept 90% from LID close and onlye around 10% (rough calculation) I had t