[Bug 1620128] [NEW] Keys that are held down for more than 1s repeat endlessly
Public bug reported: I'm not sure how else to describe this than the title: keys that are held down for more than 1s (as near as I can judge) repeat endlessly. If I strike the 'n' key, I get one 'n'. If I hold it down for over one second, I get a never-ending stream of 'n's, until I press the 'n' key again. Attached is the output of xev where I have run `xev > xev.log`, held the 'n' key for approx 1.5 seconds, released it, waited approx 10 seconds, stuck the 'n' key quickly and then exited xev. The problem is not that keyboard events in general go missing; keypress events are never missed and normal typing is fine. It is only when a key is held down. The defect appears to be in the X server, as the same problem does not happen on a text console. The system is a Lenovo ThinkPad E560 running Ubuntu 16.04 with the stock kernel. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16 Uname: Linux 4.4.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Sep 4 22:39:30 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake Integrated Graphics [17aa:5049] InstallationDate: Installed on 2016-07-23 (43 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 5986:0708 Acer, Inc Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 17ef:6022 Lenovo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20EVCTO1WW ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic.efi.signed root=UUID=87a15932-e388-46bb-bf7c-25de78ada2de ro quiet splash i8042.nomux=1 i8042.reset vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/03/2015 dmi.bios.vendor: LENOVO dmi.bios.version: R00ET35W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR00ET35W(1.10):bd12/03/2015:svnLENOVO:pn20EVCTO1WW:pvrThinkPadE560:rvnLENOVO:rn20EVCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20EVCTO1WW dmi.product.version: ThinkPad E560 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun Sep 4 22:28:58 2016 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1191 vendor LGD xserver.version: 2:1.18.3-1ubuntu2.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial ** Attachment added: "xev output" https://bugs.launchpad.net/bugs/1620128/+attachment/4734466/+files/xev.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1620128 Title: Keys that are held down for more than 1s repeat endlessly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1620128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1620128] Re: Keys that are held down for more than 1s repeat endlessly
Note this only happens with the laptop's built-in keyboard, not a USB keyboard. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1620128 Title: Keys that are held down for more than 1s repeat endlessly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1620128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774188] Re: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions)
I have this same problem on 18.04. It's very noticeable that when my network has no DNS working, screen unlock takes a long time - as much as a minute or two. I notice this because I often manually configure my network to do DNS lookups over an SSH tunnel. If I just close the lid of my laptop it locks and then goes to sleep, and of course when I open it again the SSH session is down & I have no DNS. In this state, the screen unlock is really slow. If I shut the lid not in this state, screen unlock is quick as normal. I use an Xorg session. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774188 Title: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1733888] Re: iwlwifi Error sending STATISTICS_CMD: time out after 2000ms.
I'm still seeing this in 18.04 LTS. Linux newt 4.15.0-54-generic #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux I've attached dmesg output. ** Attachment added: "dmesg.save" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733888/+attachment/5279363/+files/dmesg.save -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1733888 Title: iwlwifi Error sending STATISTICS_CMD: time out after 2000ms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733888/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838245] Re: dkms script is missing function find_module
For me, the fix is to change line 812 of /usr/sbin/dkms from: [ -z $kernels_module ] || return 0 to [ -z $kernels_module ] && return 0 This was fixed upstream here: https://github.com/dell/dkms/commit/b95779938805aca8e98d57492b18dee07d35d285 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838245 Title: dkms script is missing function find_module To manage notifications about this bug go to: https://bugs.launchpad.net/dkms/+bug/1838245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838245] Re: dkms script is missing function find_module
I'm still seeing this on Eoan, which has dkms 2.7.1-4ubuntu2 - the symptom is that virtualbox-dkms does not correctly build and install its kernel modules with the message `modinfo: ERROR: missing module or filename.` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838245 Title: dkms script is missing function find_module To manage notifications about this bug go to: https://bugs.launchpad.net/dkms/+bug/1838245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835540] Re: Confusing "modinfo: ERROR: missing module or filename." during normal operation
According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943569, this is fixed in debian dkms=2.7.1-5. ** Bug watch added: Debian Bug tracker #943569 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943569 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1835540 Title: Confusing "modinfo: ERROR: missing module or filename." during normal operation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1835540/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874424] [NEW] USB external disks are not torn down correctly when they are unplugged
Public bug reported: System information: $ lsb_release -rd Description:Ubuntu 19.10 Release:19.10 $ apt-cache policy udev udev: Installed: 242-7ubuntu3.7 Candidate: 242-7ubuntu3.7 Version table: *** 242-7ubuntu3.7 500 500 http://gb.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 242-7ubuntu3.6 500 500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 Packages 242-7ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu eoan/main amd64 Packages I have a USB3 external SSD (VID/PID is /). The whole device is encrypted (ie /dev/sdc is an encrypted LUKS volume) and the encrypted volume contains an LVM2 physical volume, a volume group called "vms" and two logical volumes. If I plug it into a booted system, everything works as expected. I'm prompted for the volume password, the volume is unlocked and LVM then maps the logical volumes: $ ls -l /dev/mapper total 0 crw--- 1 root root 10, 236 Apr 23 11:49 control lrwxrwxrwx 1 root root 7 Apr 23 11:51 luks-5e586d40-5f49-4c33-8f73-22da39d2728a -> ../dm-3 lrwxrwxrwx 1 root root 7 Apr 23 11:49 nvme0n1p3_crypt -> ../dm-0 lrwxrwxrwx 1 root root 7 Apr 23 11:49 vgubuntu-root -> ../dm-1 lrwxrwxrwx 1 root root 7 Apr 23 11:49 vgubuntu-swap_1 -> ../dm-2 lrwxrwxrwx 1 root root 7 Apr 23 11:51 vms-veeabuild -> ../dm-4 lrwxrwxrwx 1 root root 7 Apr 23 11:51 vms-veea--mirror -> ../dm-5 (The volumes "vms-*" are the ones on the external disk). I can mount the volumes and use them. If I'm careful to unmount the LVM volumes correctly and lock the disks, everything works as expected: $ vgchange -a n vms 0 logical volume(s) in volume group "vms" now active $ sudo udisksctl lock -b /dev/sdc Locked /dev/sdc. I then unplug the disk and repeat the process - everything works. If, for whatever reason, the device gets unplugged without the proper cleanup, things get messy: $ ls -l /dev/mapper total 0 crw--- 1 root root 10, 236 Apr 23 11:49 control lrwxrwxrwx 1 root root 7 Apr 23 12:04 luks-5e586d40-5f49-4c33-8f73-22da39d2728a -> ../dm-3 lrwxrwxrwx 1 root root 7 Apr 23 11:49 nvme0n1p3_crypt -> ../dm-0 lrwxrwxrwx 1 root root 7 Apr 23 11:49 vgubuntu-root -> ../dm-1 lrwxrwxrwx 1 root root 7 Apr 23 11:49 vgubuntu-swap_1 -> ../dm-2 lrwxrwxrwx 1 root root 7 Apr 23 12:04 vms-veeabuild -> ../dm-4 lrwxrwxrwx 1 root root 7 Apr 23 12:04 vms-veea--mirror -> ../dm-5 Note that the "vms-*" volumes are still there. $ ls -l /dev/dm-* brw-rw 1 root disk 253, 0 Apr 23 11:49 /dev/dm-0 brw-rw 1 root disk 253, 1 Apr 23 11:49 /dev/dm-1 brw-rw 1 root disk 253, 2 Apr 23 11:49 /dev/dm-2 brw-rw 1 root disk 253, 3 Apr 23 12:04 /dev/dm-3 brw-rw 1 root disk 253, 4 Apr 23 12:04 /dev/dm-4 brw-rw 1 root disk 253, 5 Apr 23 12:04 /dev/dm-5 /dev/dm-* still exists. However, sdc has been removed: $ ls -l /dev/sdc ls: cannot access '/dev/sdc': No such file or directory If I then plug the disk in again, I'm again prompted for the passphrase and the disk is mapped to /dev/sdd (not /dev/sdc like previous times). If I try to mount one of the volumes: $ sudo mount /dev/mapper/vms-veeabuild mnt2 mount: /home/tkcook/mnt2: can't read superblock on /dev/mapper/vms-veeabuild. Something is not getting cleaned up when the disk is forcibly removed. There doesn't seem to be any way to clean up from here; vgchange can't deactivate the volume group and udisksctl can't lock the LUKS volume. The only way I've found of using the disk again is to reboot (!) I'm raising this on the udev package but that is a bit of a guess; I'm assuming this is udev not processing the disconnection event correctly (though since I can't find a way of cleaning this up, it's not clear what it could do). ** Affects: udev (Ubuntu) Importance: Undecided Status: New ** Summary changed: - USB external disks are not torn down correctly when the are unplugged + USB external disks are not torn down correctly when they are unplugged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874424 Title: USB external disks are not torn down correctly when they are unplugged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1874424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874424] Re: USB external disks are not torn down correctly when they are unplugged
Just to note that I have figured out how to clean this up manually: $ sudo dmsetup remove vms-veeabuild $ sudo dmsetup remove vms-veea--mirror Although this is rather a violent thing to do to a volume, since the disk has already been physically unplugged while working, we've pretty much crossed that bridge. I guess from here I should be able to write a udev rule to do this when the device is unplugged, but that's waaay beyond my udev skills. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874424 Title: USB external disks are not torn down correctly when they are unplugged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1874424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903292] Re: System hangs after suspend
I'm running a custom kernel build because when I installed Ubuntu on this laptop (19.10) various things were not supported in the stock kernel. I'm now trying to apply a BIOS update which apparently has some ACPI-related stuff in it, but this is proving difficult as HP's BIOS updates are somewhat Windows-centric. Once I've done that, I'll switch to the 5.8.0-26-generic kernel and report back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: System hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903292] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1903292/+attachment/5433478/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: System hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903292] Re: System hangs after suspend
apport information ** Tags added: groovy staging ** Description changed: I'm running 20.04 LTS on an HP Envy x360 Ryzen 7 3700U with Radeon Vega Mobile. The gdm3 package is at version 3.36.3-0ubuntu0.20.04.2. When I trigger a suspend with `echo mem > /sys/power/state` the system appears to go into mem suspend correctly. Hitting a key should bring the display back with the lock screen displayed, but instead briefly brings a slightly scrambled screen to life and then the screen goes black and stays that way. The system is still up as I can SSH into it. Killing the gdm-wayland-session process then brings me back to the GDM login screen and I can start a new session. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-10-17 (388 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: wayland-session third-party-packages focal Uname: Linux 5.9.0 x86_64 UpgradeStatus: Upgraded to focal on 2020-04-28 (194 days ago) UserGroups: adm cdrom dip disk docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu50 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: tkcook 2526 F pulseaudio + /dev/snd/controlC0: tkcook 2526 F pulseaudio + CasperMD5CheckResult: skip + DistroRelease: Ubuntu 20.10 + InstallationDate: Installed on 2019-10-17 (390 days ago) + InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) + MachineType: HP HP ENVY x360 Convertible 15-ds0xxx + Package: linux (not installed) + ProcEnviron: + LANGUAGE=en_GB:en + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_GB.UTF-8 + SHELL=/bin/bash + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-26-generic root=/dev/mapper/vgubuntu-root ro splash acpi.debug_level=2 acpi.debug_layer=0x acpi_osi=Linux amd_iommu=off amdgpu.gpu_recovery=1 xhci_hcd.quirks=1074143232 + ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-5.8.0-26-generic N/A + linux-backports-modules-5.8.0-26-generic N/A + linux-firmware1.190.1 + StagingDrivers: ashmem_linux + Tags: groovy staging + Uname: Linux 5.8.0-26-generic x86_64 + UpgradeStatus: Upgraded to groovy on 2020-11-09 (1 days ago) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 05/28/2020 + dmi.bios.release: 15.20 + dmi.bios.vendor: AMI + dmi.bios.version: F.20 + dmi.board.asset.tag: Base Board Asset Tag + dmi.board.name: 85DD + dmi.board.vendor: HP + dmi.board.version: 40.36 + dmi.chassis.type: 31 + dmi.chassis.vendor: HP + dmi.chassis.version: Chassis Version + dmi.ec.firmware.release: 40.36 + dmi.modalias: dmi:bvnAMI:bvrF.20:bd05/28/2020:br15.20:efr40.36:svnHP:pnHPENVYx360Convertible15-ds0xxx:pvr:rvnHP:rn85DD:rvr40.36:cvnHP:ct31:cvrChassisVersion: + dmi.product.family: 103C_5335KV HP Envy + dmi.product.name: HP ENVY x360 Convertible 15-ds0xxx + dmi.product.sku: 6TD06EA#ABU + dmi.sys.vendor: HP + mtime.conffile..etc.apport.crashdb.conf: 2020-11-09T09:19:45.442981 ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1903292/+attachment/5433472/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: System hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903292] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1903292/+attachment/5433486/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: System hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903292] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1903292/+attachment/5433489/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: System hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903292] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1903292/+attachment/5433476/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: System hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903292] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1903292/+attachment/5433484/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: System hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903292] Re: System hangs after suspend
I've applied the latest BIOS update from HP but this has not made any difference to the problem. I've also verified the problem still exists when running the 2.8.0-26-generic kernel from groovy. I've also run the apport-collect requested above using that kernel. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: System hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903292] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1903292/+attachment/5433483/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: System hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903292] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1903292/+attachment/5433482/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: System hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903292] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1903292/+attachment/5433480/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: System hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903292] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1903292/+attachment/5433477/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: System hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903292] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1903292/+attachment/5433475/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: System hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903292] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1903292/+attachment/5433481/+files/PaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: System hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903292] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1903292/+attachment/5433479/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: System hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903292] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1903292/+attachment/5433487/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: System hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903292] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1903292/+attachment/5433474/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: System hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903292] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1903292/+attachment/5433488/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: System hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903292] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1903292/+attachment/5433485/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: System hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903292] modified.conffile..etc.apport.crashdb.conf.txt
apport information ** Attachment added: "modified.conffile..etc.apport.crashdb.conf.txt" https://bugs.launchpad.net/bugs/1903292/+attachment/5433490/+files/modified.conffile..etc.apport.crashdb.conf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: System hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903292] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1903292/+attachment/5433473/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: System hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903890] Re: python3-openssl appears to be built against the wrong version of libffi
A couple more notes: * I've removed my per-user install of requests but this doesn't help. * This doesn't kill all HTTPS requests; it seems to be related to the format of the CA certificate being used to verify the server. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903890 Title: python3-openssl appears to be built against the wrong version of libffi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyopenssl/+bug/1903890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903890] Re: python3-openssl appears to be built against the wrong version of libffi
I've confirmed that setting up a virtualenv with the pyopenssl and requests packages from PyPI does not result in the same defect. If I get a chance, I'll try to put together a minimal test case to reproduce this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903890 Title: python3-openssl appears to be built against the wrong version of libffi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyopenssl/+bug/1903890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903890] [NEW] python3-openssl appears to be built against the wrong version of libffi
Public bug reported:
I've just upgraded to Ubuntu 20.10 which comes with python3-openssl
version 19.0.1-2. It breaks (at least some) Python applications that
use the `requests` library to access HTTPS URLS. For instance, this
stack trace (note that I have clipped the first few frames from the
stack as they are proprietary):
File "/home/tkcook/.local/lib/python3.8/site-packages/requests/api.py", line
76, in get
return request('get', url, params=params, **kwargs)
File "/home/tkcook/.local/lib/python3.8/site-packages/requests/api.py", line
61, in request
return session.request(method=method, url=url, **kwargs)
File "/home/tkcook/.local/lib/python3.8/site-packages/requests/sessions.py",
line 530, in request
resp = self.send(prep, **send_kwargs)
File "/home/tkcook/.local/lib/python3.8/site-packages/requests/sessions.py",
line 643, in send
r = adapter.send(request, **kwargs)
File "/home/tkcook/.local/lib/python3.8/site-packages/requests/adapters.py",
line 439, in send
resp = conn.urlopen(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 670, in
urlopen
httplib_response = self._make_request(
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 381, in
_make_request
self._validate_conn(conn)
File "/usr/lib/python3/dist-packages/urllib3/connectionpool.py", line 978, in
_validate_conn
conn.connect()
File "/usr/lib/python3/dist-packages/urllib3/connection.py", line 342, in
connect
self.ssl_context = create_urllib3_context(
File "/usr/lib/python3/dist-packages/urllib3/util/ssl_.py", line 289, in
create_urllib3_context
context.verify_mode = cert_reqs
File "/usr/lib/python3/dist-packages/urllib3/contrib/pyopenssl.py", line 438,
in verify_mode
self._ctx.set_verify(_stdlib_to_openssl_verify[value], _verify_callback)
File "/usr/lib/python3/dist-packages/OpenSSL/SSL.py", line 1119, in set_verify
self._verify_helper = _VerifyHelper(callback)
File "/usr/lib/python3/dist-packages/OpenSSL/SSL.py", line 337, in __init__
self.callback = _ffi.callback(
SystemError: ffi_prep_closure(): bad user_data (it seems that the version of
the libffi library seen at runtime is different from the 'ffi.h' file seen at
compile-time)
** Affects: pyopenssl (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903890
Title:
python3-openssl appears to be built against the wrong version of
libffi
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pyopenssl/+bug/1903890/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904759] [NEW] libpipewire0.2 packages would be very useful
Public bug reported: Chrome / Chromium seems to be the main platform for screensharing but still uses libpipewire version 0.2, which can't be installed on Groovy (no installation candidate). Even a PPA build would be really handy... ** Affects: pipewire (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904759 Title: libpipewire0.2 packages would be very useful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1904759/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903292] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1903292/+attachment/5432572/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: GNOME Wayland session hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903292] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1903292/+attachment/5432573/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: GNOME Wayland session hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903292] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1903292/+attachment/5432571/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: GNOME Wayland session hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903292] Re: GNOME Wayland session hangs after suspend
apport information ** Tags added: apport-collected third-party-packages ** Description changed: I'm running 20.04 LTS on an HP Envy x360 Ryzen 7 3700U with Radeon Vega Mobile. The gdm3 package is at version 3.36.3-0ubuntu0.20.04.2. When I trigger a suspend with `echo mem > /sys/power/state` the system appears to go into mem suspend correctly. Hitting a key should bring the display back with the lock screen displayed, but instead briefly brings a slightly scrambled screen to life and then the screen goes black and stays that way. - The system is still up as I can SSH into it. Killing the gdm-wayland- - session process then brings me back to the GDM login screen and I can - start a new session. + The system is still up as I can SSH into it. Killing the gdm-wayland-session process then brings me back to the GDM login screen and I can start a new session. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.10 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2019-10-17 (388 days ago) + InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) + Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 + PackageArchitecture: amd64 + RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 + Tags: wayland-session third-party-packages focal + Uname: Linux 5.9.0 x86_64 + UpgradeStatus: Upgraded to focal on 2020-04-28 (194 days ago) + UserGroups: adm cdrom dip disk docker lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1903292/+attachment/5432569/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: GNOME Wayland session hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903292] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1903292/+attachment/5432574/+files/ShellJournal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: GNOME Wayland session hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903292] Re: GNOME Wayland session hangs after suspend
Hi Daniel, Thanks for the follow-up. I've done the `apport-collect`, see above. I've also uploaded a potentially-related crash file from Xwayland, see https://errors.ubuntu.com/oops/39763900-226c-11eb-b3ef-fa163e102db1. I'm not absolutely certain this is related but the timestamp on it is about right. Regards, Tom -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: GNOME Wayland session hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903292] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1903292/+attachment/5432575/+files/monitors.xml.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: GNOME Wayland session hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903292] Re: GNOME Wayland session hangs after suspend
I've done the full-upgrade and disabled the non-Ubuntu extensions and then re-triggered the crash with `echo mem > /sys/power/state`. This now causes a hard hang of the whole system - its no longer accessible over the network when it tries to wake up. There is no new log in /var/crash and the last thing in kern.log is it going to sleep. This doesn't seem promising. The kernel is a custom-built 5.9.0 built from Linus' repository - I'm not expecting a lot of support with that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: GNOME Wayland session hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1903292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903292] [NEW] GNOME Wayland session hangs after suspend
Public bug reported: I'm running 20.04 LTS on an HP Envy x360 Ryzen 7 3700U with Radeon Vega Mobile. The gdm3 package is at version 3.36.3-0ubuntu0.20.04.2. When I trigger a suspend with `echo mem > /sys/power/state` the system appears to go into mem suspend correctly. Hitting a key should bring the display back with the lock screen displayed, but instead briefly brings a slightly scrambled screen to life and then the screen goes black and stays that way. The system is still up as I can SSH into it. Killing the gdm-wayland- session process then brings me back to the GDM login screen and I can start a new session. ** Affects: gdm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903292 Title: GNOME Wayland session hangs after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1903292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903890] Re: libffi7 missing from Ubuntu (pip's python3-openssl appears to be built against the wrong version of libffi)
I've confirmed that my use case (the original report of this ticket) is resolved in 21.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903890 Title: libffi7 missing from Ubuntu (pip's python3-openssl appears to be built against the wrong version of libffi) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1903890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926580] [NEW] pip3 launches the KDE Wallet Service
Public bug reported: Since upgrading to 21.04 (python3-pip package version 20.3.4-1ubuntu2), every time I run `pip3` I get the KDE Wallet Service starting and showing a window, saying: The application '/usr/bin/pip3' has requested to create a new wallet named 'kdewallet'. This is used to store sensitive data in a secure fashion. Please choose the new wallet's type below or click cancel to deny the application's request. I'm given a choice of blowfish or GPG. Pressing cancel seems to have no negative consequences for the package install. ** Affects: python-pip (Ubuntu) Importance: Undecided Status: New ** Bug watch added: github.com/pypa/pip/issues #8090 https://github.com/pypa/pip/issues/8090 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926580 Title: pip3 launches the KDE Wallet Service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1926580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926580] Re: pip3 launches the KDE Wallet Service
Note that this has been reported upstream: https://github.com/pypa/pip/issues/8090 It's not obvious from a quick look through the history of that ticket whether it has been properly fixed. A workaround is to `export PYTHON_KEYRING_BACKEND=keyring.backends.null.Keyring`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926580 Title: pip3 launches the KDE Wallet Service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1926580/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899224] Re: Should ship libpipewire0.2 alongside pipewire 0.3 for chrome support?
Some progress in 21.04. Screen sharing in Chrome now sort of works, but with some weirdness. I'm working on laptop with two external screens; sharing the laptop's built-in screen works, but sharing an external screen with a different resolution doesn't; I get a somewhat-old-school effect where the remote side sees three copies of my screen side-by-side with an interlaced effect. Screen-sharing in Slack allegedly works now if you use a command-line argument to enable pipewire though I haven't had occasion to test it; Teams is still waiting for an update to the most recent version of Electron, though presumably the web client run in Chrome would work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899224 Title: Should ship libpipewire0.2 alongside pipewire 0.3 for chrome support? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1899224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899224] Re: Should ship libpipewire0.2 alongside pipewire 0.3 for chrome support?
Firefox might not but lots of other things do. It is allegedly possible to install the libpipewire0.2 binaries from an earlier Ubuntu on 20.10 but I've had no success doing so; no applications are able to share my screen (firefox, chrome, slack, teams...) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899224 Title: Should ship libpipewire0.2 alongside pipewire 0.3 for chrome support? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1899224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956401] Re: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works
Confirmed on Ryzen 7 3700U, and that the -24 pre-release update fixes it. Standby has never worked on this system so I can't comment on that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956401 Title: amdgpu hangs for 90 seconds at a time in 5.13.0-23, but 5.13.0-22 works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1975685] [NEW] Wifi hotspot does not work when band A is selected
Public bug reported: I'm using a built-in RTL8822BE WiFi adapter on a Ryzen 7 system. When I create a hotspot by opening the GNOME settings app, opening the WiFi settings page and selecting "Turn on hotspot..." from the drop-down menu, everything works fine. If I then open nm-connection-editor and edit the connection to select band A (5GHz), the hotspot fails to start. If I then open the connection editor again and switch back to automatic band selection, the hotspot works again. When it fails, this appears in syslog: May 25 10:21:30 frog NetworkManager[815]: [1653470490.8638] device (wlo1): Activation: starting connection 'Hotspot' (514f603b-25e2-4c1e-9220-7b77ed966ff5) May 25 10:21:30 frog NetworkManager[815]: [1653470490.8643] device (wlo1): supplicant interface state: completed -> disconnected May 25 10:21:30 frog NetworkManager[815]: [1653470490.8653] device (wlo1): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') May 25 10:21:30 frog NetworkManager[815]: [1653470490.8676] device (wlo1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') May 25 10:21:30 frog NetworkManager[815]: [1653470490.8783] device (wlo1): Activation: (wifi) access point 'Hotspot' has security, but secrets are required. May 25 10:21:30 frog NetworkManager[815]: [1653470490.8783] device (wlo1): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') May 25 10:21:30 frog NetworkManager[815]: [1653470490.8800] device (wlo1): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed') May 25 10:21:30 frog NetworkManager[815]: [1653470490.8810] device (wlo1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') May 25 10:21:30 frog NetworkManager[815]: [1653470490.8883] device (wlo1): Activation: (wifi) connection 'Hotspot' has security, and secrets exist. No new secrets needed. May 25 10:21:30 frog wpa_supplicant[866]: wlo1: Failed to start AP functionality May 25 10:21:56 frog NetworkManager[815]: [1653470516.1521] device (wlo1): Activation: (wifi) Hotspot network creation took too long, failing activation May 25 10:21:56 frog NetworkManager[815]: [1653470516.1522] device (wlo1): state change: config -> failed (reason 'supplicant-timeout', sys-iface-state: 'managed') May 25 10:21:56 frog NetworkManager[815]: [1653470516.1526] device (wlo1): Activation: failed for connection 'Hotspot' May 25 10:21:56 frog wpa_supplicant[866]: wlo1: CTRL-EVENT-DSCP-POLICY clear_all May 25 10:21:56 frog NetworkManager[815]: [1653470516.1530] device (wlo1): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') May 25 10:21:56 frog wpa_supplicant[866]: wlo1: Reject scan trigger since one is already pending May 25 10:21:59 frog wpa_supplicant[866]: wlo1: CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN I'm guessing that NetworkManager is getting the way it drives wpa_supplicant wrong when the 5GHz band is selected, but it's only a guess. Ubuntu version is: tkcook@frog:~$ lsb_release -rd Description:Ubuntu 22.04 LTS Release:22.04 NetworkManager version is: tkcook@frog:~$ apt-cache policy network-manager-gnome network-manager-gnome: Installed: 1.24.0-1ubuntu3 Candidate: 1.24.0-1ubuntu3 Version table: *** 1.24.0-1ubuntu3 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager-gnome 1.24.0-1ubuntu3 Uname: Linux 5.18.0 x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 25 10:29:37 2022 InstallationDate: Installed on 2021-08-27 (270 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: network-manager-applet UpgradeStatus: Upgraded to jammy on 2022-05-05 (19 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled disabled ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1975685 Title: Wifi hotspot does not work when band A is selected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1975685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068574] [NEW] Screen lock crashes after playing fullscreen games
Public bug reported: This appears to be new after an upgrade to 24.04. My laptop has a 2560x1600 panel. When I play a fullscreen Steam game (in this case Satisfactory) set to that resolution, afterwards the virtual display size in GNOME is increased, so that if I move the mouse off the bottom or right-hand sides of the screen then the desktop scrolls. The GNOME shell has not resized and the extra virtual space is just grey. If I then suspend the system by shutting the lid and then unsuspend it again, the lock screen does not appear and I get a brief glimpse of the screen content before the "Something went wrong" screen and a forced log off. After logging off, everything is okay again. I am using the Xorg display session. This only happens after playing the game and therefore when the virtual display size is increased. My guess is that GNOME Shell is not handling the mismatched display sizes. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5.1 ProcVersionSignature: Ubuntu 6.8.0-35.35-generic 6.8.4 Uname: Linux 6.8.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Thu Jun 6 08:39:09 2024 DisplayManager: gdm3 InstallationDate: Installed on 2023-12-05 (184 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) RelatedPackageVersions: mutter-common 46.0-1ubuntu9 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2024-04-28 (39 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068574 Title: Screen lock crashes after playing fullscreen games To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068574] Re: Screen lock crashes after playing fullscreen games
I'm not locking the screen while in the overview. This happened this morning and I'm not absolutely sure that I'd had Satisfactory running beforehand. I've uploaded the journal files from this crash above. The crash this morning produced crash files from chrome and vscode but I don't think these are a symptom rather than the cause; previous crashes have not produced these. There is a crash file for /usr/lib/xorg/Xorg but `ubuntu-bug --save bug.txt /var/crash/_usr_lib_xorg_Xorg.1000.crash` produces an empty file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068574 Title: Screen lock crashes after playing fullscreen games To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068574] Re: Screen lock crashes after playing fullscreen games
And the only whoopsie link is from January, ie before the upgrade to 24.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068574 Title: Screen lock crashes after playing fullscreen games To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068574] Re: Screen lock crashes after playing fullscreen games
Attaching journal.txt ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068574/+attachment/5787096/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068574 Title: Screen lock crashes after playing fullscreen games To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068574] Re: Screen lock crashes after playing fullscreen games
** Attachment added: "prevjournal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068574/+attachment/5787097/+files/prevjournal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068574 Title: Screen lock crashes after playing fullscreen games To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068574] Re: Screen lock crashes after playing fullscreen games
Also trying to set the kernel commandline with `sudo snap set system system.kernel.cmdline-append` appears to have crashed snapd. Quite what state that's left my system in is anyone's guess. It _might_ be bootable... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068574 Title: Screen lock crashes after playing fullscreen games To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068574] Re: Screen lock crashes after playing fullscreen games
I'm uncertain how to tell if I'm affected by that bug. I'm not seeing the main symptom - a "phantom" display in settings. But I'm only running Nvidia drivers version 535, so possibly that symptom doesn't show up until you install 545? I do have a /dev/card0 which is from the simple-framebuffer module. I'll try adding the initcall_blacklist but I don't think it'll do anything; AFAICT there is no simpledrm driver on the system, only simple-framebuffer, and I thought that module init methods and to match the name of the module? Or maybe not when it's not loaded as a module, IDK (and simple-framebuffer appears to be compiled-in on this system). I saw the crash again this morning and again there are no crash files in /var/crash - the most recent was three days ago. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068574 Title: Screen lock crashes after playing fullscreen games To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2068574] Re: Screen lock crashes after playing fullscreen games
I've managed to recover my system to the point that snap is working again - see #2068874 - but won't get a chance to test this just now. Yes, drm_info reports card0 as simpledrm and card1 as nvidia-drm. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2068574 Title: Screen lock crashes after playing fullscreen games To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2068574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
