[Desktop-packages] [Bug 2026790] Re: Slow refresh rate (5-6hz) on Display managed by gnome-shell
To avoid all of these problems, please just select 'Ubuntu on Xorg' at the login screen. ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2026790 Title: Slow refresh rate (5-6hz) on Display managed by gnome-shell Status in gnome-shell package in Ubuntu: New Bug description: NVIDIA GPU sending out frames to an LG Electronics 27" display. At the moment, just a single display. The NVIDIA GPU is available across a Thunderbolt 3 link. Here is what the Nvidia Drivers are reporting: beadon@semiauto:~$ nvidia-smi Mon Jul 10 20:35:25 2023 +---+ | NVIDIA-SMI 535.54.03 Driver Version: 535.54.03CUDA Version: 12.2 | |-+--+--+ | GPU Name Persistence-M | Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |=+==+==| | 0 NVIDIA GeForce GTX 1650Off | :52:00.0 On | N/A | | 0% 33CP8 N/A / 85W | 99MiB / 4096MiB | 0% Default | | | | N/A | +-+--+--+ +---+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |===| |0 N/A N/A 2341 G /usr/bin/gnome-shell 1MiB | +---+ Performing an strace I am seeing that the gnome-shell is **very** frequently hitting : EAGAIN (Resource temporarily unavailable) It's not clear to me what is causing this. strace on the 33 threads included for reference. To show different behaviors, clicks, movement of windows, typing in a terminal, as running glxgears to show(get) the refresh rate of 5 frames per second. Is there some kind of heavy CPU-based communication happening for gnome-shell ? I am seeing the CPU usage spike to 90+% when simple movements are done on screen. However, the nvidia-smi tools reports that it truly is attached to the right GPU, the PID is correct. Please see the strace for further information. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.2-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 10 20:40:20 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-09 (182 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-04-26 (75 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026790] Re: Slow refresh rate (5-6hz) on Display managed by gnome-shell
And I suspect the "5-6hz" is just that it managed to allocate some dumb buffers, but not enough of them to get every frame to the monitor. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2026790 Title: Slow refresh rate (5-6hz) on Display managed by gnome-shell Status in gnome-shell package in Ubuntu: New Bug description: NVIDIA GPU sending out frames to an LG Electronics 27" display. At the moment, just a single display. The NVIDIA GPU is available across a Thunderbolt 3 link. Here is what the Nvidia Drivers are reporting: beadon@semiauto:~$ nvidia-smi Mon Jul 10 20:35:25 2023 +---+ | NVIDIA-SMI 535.54.03 Driver Version: 535.54.03CUDA Version: 12.2 | |-+--+--+ | GPU Name Persistence-M | Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |=+==+==| | 0 NVIDIA GeForce GTX 1650Off | :52:00.0 On | N/A | | 0% 33CP8 N/A / 85W | 99MiB / 4096MiB | 0% Default | | | | N/A | +-+--+--+ +---+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |===| |0 N/A N/A 2341 G /usr/bin/gnome-shell 1MiB | +---+ Performing an strace I am seeing that the gnome-shell is **very** frequently hitting : EAGAIN (Resource temporarily unavailable) It's not clear to me what is causing this. strace on the 33 threads included for reference. To show different behaviors, clicks, movement of windows, typing in a terminal, as running glxgears to show(get) the refresh rate of 5 frames per second. Is there some kind of heavy CPU-based communication happening for gnome-shell ? I am seeing the CPU usage spike to 90+% when simple movements are done on screen. However, the nvidia-smi tools reports that it truly is attached to the right GPU, the PID is correct. Please see the strace for further information. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.2-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 10 20:40:20 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-09 (182 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-04-26 (75 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026790] Re: Slow refresh rate (5-6hz) on Display managed by gnome-shell
To work around this problem, please log into a Xorg session instead. ** Tags added: hybrid multigpu multimonitor nvidia ** Tags added: nvidia-wayland -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2026790 Title: Slow refresh rate (5-6hz) on Display managed by gnome-shell Status in gnome-shell package in Ubuntu: New Bug description: NVIDIA GPU sending out frames to an LG Electronics 27" display. At the moment, just a single display. The NVIDIA GPU is available across a Thunderbolt 3 link. Here is what the Nvidia Drivers are reporting: beadon@semiauto:~$ nvidia-smi Mon Jul 10 20:35:25 2023 +---+ | NVIDIA-SMI 535.54.03 Driver Version: 535.54.03CUDA Version: 12.2 | |-+--+--+ | GPU Name Persistence-M | Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |=+==+==| | 0 NVIDIA GeForce GTX 1650Off | :52:00.0 On | N/A | | 0% 33CP8 N/A / 85W | 99MiB / 4096MiB | 0% Default | | | | N/A | +-+--+--+ +---+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |===| |0 N/A N/A 2341 G /usr/bin/gnome-shell 1MiB | +---+ Performing an strace I am seeing that the gnome-shell is **very** frequently hitting : EAGAIN (Resource temporarily unavailable) It's not clear to me what is causing this. strace on the 33 threads included for reference. To show different behaviors, clicks, movement of windows, typing in a terminal, as running glxgears to show(get) the refresh rate of 5 frames per second. Is there some kind of heavy CPU-based communication happening for gnome-shell ? I am seeing the CPU usage spike to 90+% when simple movements are done on screen. However, the nvidia-smi tools reports that it truly is attached to the right GPU, the PID is correct. Please see the strace for further information. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.2-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 10 20:40:20 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-09 (182 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-04-26 (75 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026790] Re: Slow refresh rate (5-6hz) on Display managed by gnome-shell
Actually I think I've seen this before. One of the graphics drivers has run out of memory: [ 198.184944] semiauto gnome-shell[2341]: Failed to allocate onscreen framebuffer for /dev/dri/card1: Failed to create dumb drm buffer: Cannot allocate memory [ 198.209428] semiauto gnome-shell[2341]: Failed to allocate onscreen framebuffer for /dev/dri/card1: Failed to create dumb drm buffer: Cannot allocate memory ... [ 199.493073] semiauto gnome-shell[2341]: meta_frame_native_release: assertion '!frame_native->kms_update' failed [ 199.494175] semiauto gnome-shell[2341]: (../clutter/clutter/clutter-frame-clock.c:425):clutter_frame_clock_notify_presented: code should not be reached [ 199.494260] semiauto gnome-shell[2341]: (../clutter/clutter/clutter-frame-clock.c:425):clutter_frame_clock_notify_presented: code should not be reached [ 199.527787] semiauto gnome-shell[2341]: (../clutter/clutter/clutter-frame-clock.c:425):clutter_frame_clock_notify_presented: code should not be reached If I recall correctly the solution is to just reboot. But certainly gnome-shell shouldn't keep trying to run in this situation. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2026790 Title: Slow refresh rate (5-6hz) on Display managed by gnome-shell Status in gnome-shell package in Ubuntu: New Bug description: NVIDIA GPU sending out frames to an LG Electronics 27" display. At the moment, just a single display. The NVIDIA GPU is available across a Thunderbolt 3 link. Here is what the Nvidia Drivers are reporting: beadon@semiauto:~$ nvidia-smi Mon Jul 10 20:35:25 2023 +---+ | NVIDIA-SMI 535.54.03 Driver Version: 535.54.03CUDA Version: 12.2 | |-+--+--+ | GPU Name Persistence-M | Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |=+==+==| | 0 NVIDIA GeForce GTX 1650Off | :52:00.0 On | N/A | | 0% 33CP8 N/A / 85W | 99MiB / 4096MiB | 0% Default | | | | N/A | +-+--+--+ +---+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |===| |0 N/A N/A 2341 G /usr/bin/gnome-shell 1MiB | +---+ Performing an strace I am seeing that the gnome-shell is **very** frequently hitting : EAGAIN (Resource temporarily unavailable) It's not clear to me what is causing this. strace on the 33 threads included for reference. To show different behaviors, clicks, movement of windows, typing in a terminal, as running glxgears to show(get) the refresh rate of 5 frames per second. Is there some kind of heavy CPU-based communication happening for gnome-shell ? I am seeing the CPU usage spike to 90+% when simple movements are done on screen. However, the nvidia-smi tools reports that it truly is attached to the right GPU, the PID is correct. Please see the strace for further information. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.2-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 10 20:40:20 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-09 (182 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded
[Desktop-packages] [Bug 2026790] Re: Slow refresh rate (5-6hz) on Display managed by gnome-shell
Your log is mostly showing bug 1967707 but I think the root cause that comes before it is: [ 199.493073] semiauto gnome-shell[2341]: meta_frame_native_release: assertion '!frame_native->kms_update' failed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2026790 Title: Slow refresh rate (5-6hz) on Display managed by gnome-shell Status in gnome-shell package in Ubuntu: New Bug description: NVIDIA GPU sending out frames to an LG Electronics 27" display. At the moment, just a single display. The NVIDIA GPU is available across a Thunderbolt 3 link. Here is what the Nvidia Drivers are reporting: beadon@semiauto:~$ nvidia-smi Mon Jul 10 20:35:25 2023 +---+ | NVIDIA-SMI 535.54.03 Driver Version: 535.54.03CUDA Version: 12.2 | |-+--+--+ | GPU Name Persistence-M | Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |=+==+==| | 0 NVIDIA GeForce GTX 1650Off | :52:00.0 On | N/A | | 0% 33CP8 N/A / 85W | 99MiB / 4096MiB | 0% Default | | | | N/A | +-+--+--+ +---+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |===| |0 N/A N/A 2341 G /usr/bin/gnome-shell 1MiB | +---+ Performing an strace I am seeing that the gnome-shell is **very** frequently hitting : EAGAIN (Resource temporarily unavailable) It's not clear to me what is causing this. strace on the 33 threads included for reference. To show different behaviors, clicks, movement of windows, typing in a terminal, as running glxgears to show(get) the refresh rate of 5 frames per second. Is there some kind of heavy CPU-based communication happening for gnome-shell ? I am seeing the CPU usage spike to 90+% when simple movements are done on screen. However, the nvidia-smi tools reports that it truly is attached to the right GPU, the PID is correct. Please see the strace for further information. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.2-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 10 20:40:20 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-09 (182 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-04-26 (75 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026790] [NEW] Slow refresh rate (5-6hz) on Display managed by gnome-shell
Public bug reported: NVIDIA GPU sending out frames to an LG Electronics 27" display. At the moment, just a single display. The NVIDIA GPU is available across a Thunderbolt 3 link. Here is what the Nvidia Drivers are reporting: beadon@semiauto:~$ nvidia-smi Mon Jul 10 20:35:25 2023 +---+ | NVIDIA-SMI 535.54.03 Driver Version: 535.54.03CUDA Version: 12.2 | |-+--+--+ | GPU Name Persistence-M | Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |=+==+==| | 0 NVIDIA GeForce GTX 1650Off | :52:00.0 On | N/A | | 0% 33CP8 N/A / 85W | 99MiB / 4096MiB | 0% Default | | | | N/A | +-+--+--+ +---+ | Processes: | | GPU GI CIPID Type Process name GPU Memory | |ID ID Usage | |===| |0 N/A N/A 2341 G /usr/bin/gnome-shell 1MiB | +---+ Performing an strace I am seeing that the gnome-shell is **very** frequently hitting : EAGAIN (Resource temporarily unavailable) It's not clear to me what is causing this. strace on the 33 threads included for reference. To show different behaviors, clicks, movement of windows, typing in a terminal, as running glxgears to show(get) the refresh rate of 5 frames per second. Is there some kind of heavy CPU-based communication happening for gnome- shell ? I am seeing the CPU usage spike to 90+% when simple movements are done on screen. However, the nvidia-smi tools reports that it truly is attached to the right GPU, the PID is correct. Please see the strace for further information. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.2-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 10 20:40:20 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-09 (182 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-04-26 (75 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session ** Attachment added: "gnome-shell-strace---slow-performance--on_gpu" https://bugs.launchpad.net/bugs/2026790/+attachment/5685326/+files/gnome-shell-strace---slow-performance--on_gpu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2026790 Title: Slow refresh rate (5-6hz) on Display managed by gnome-shell Status in gnome-shell package in Ubuntu: New Bug description: NVIDIA GPU sending out frames to an LG Electronics 27" display. At the moment, just a single display. The NVIDIA GPU is available across a Thunderbolt 3 link. Here is what the Nvidia Drivers are reporting: beadon@semiauto:~$ nvidia-smi Mon Jul 10 20:35:25 2023 +---+ | NVIDIA-SMI 535.54.03 Driver Version: 535.54.03CUDA Version: 12.2 | |-+--+--+ | GPU Name Persistence-M | Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. | | | | MIG M. |
[Desktop-packages] [Bug 2026789] Re: Xorg display freeze when using gnome settings " display" to enable/disable displays on eGPU
Were you using Wayland when the freeze happened? Next time it happens, please reboot and then run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Tags added: hybrid multigpu multimonitor nvidia ** Package changed: ubuntu => nvidia-graphics-drivers-535 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2026789 Title: Xorg display freeze when using gnome settings " display" to enable/disable displays on eGPU Status in nvidia-graphics-drivers-535 package in Ubuntu: Incomplete Bug description: When using the Ubuntu settings app to change displays I was enabling and disabling displays to see if I could replicate a problem. It appears that the drivers / setup are OK with 2x displays, but things start to fall apart when there are 3x displays. 2x displys managed by NVIDIA displayport connection, and 1x display managed by the Intel Iris GPU. I have noticed that windows appear to move between displays, so I think there is a problem with how the displays and the windows are arranged. Attached are as many logs as I can find for this problem. Notably, I am receiving errors in my local terminal when reporting this bug: [15578:15578:0710/200056.340294:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times! [15578:15578:0710/200056.356275:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times! [15578:15578:0710/200056.357312:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times! [15529:15529:0710/200138.416553:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not implemented This appears to be related to DRM ?? Tehese messages occured as I enabled / disabled the displays on displayport: [Mon Jul 10 19:53:29 2023] [drm] [nvidia-drm] [GPU ID 0x5200] Framebuffer memory not appropriate for scanout [Mon Jul 10 19:53:29 2023] [drm] [nvidia-drm] [GPU ID 0x5200] Framebuffer memory not appropriate for scanout [Mon Jul 10 19:53:41 2023] [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x5200] Failed to map NvKmsKapiMemory 0xfc099386 [Mon Jul 10 19:54:23 2023] [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x5200] Failed to map NvKmsKapiMemory 0xcd359766 [Mon Jul 10 19:54:23 2023] [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x5200] Failed to map NvKmsKapiMemory 0x40936ab7 These messages appeard when I started the gnome display manager : Mon Jul 10 19:46:16 2023] rfkill: input handler enabled [Mon Jul 10 19:46:17 2023] usb 2-2.2: current rate 16000 is different from the runtime rate 48000 [Mon Jul 10 19:46:17 2023] usb 2-2.2: current rate 16000 is different from the runtime rate 48000 [Mon Jul 10 19:46:17 2023] usb 2-2.2: current rate 16000 is different from the runtime rate 48000 [Mon Jul 10 19:46:17 2023] [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x5200] Failed to map NvKmsKapiMemory 0xf989da34 [Mon Jul 10 19:46:17 2023] [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x5200] Failed to map NvKmsKapiMemory 0x32149488 [Mon Jul 10 19:46:18 2023] rfkill: input handler disabled [Mon Jul 10 19:46:25 2023] bijiben-shell-s[3102]: segfault at 7f9c05be1b13 ip 7f9c1bb4e5a1 sp 7fff6f49e438 error 4 in libgobject-2.0.so.0.7600.1[7f9c1bb24000+34000] likely on CPU 6 (core 2, socket 0) [Mon Jul 10 19:46:25 2023] Code: c0 0f 95 c0 48 83 c4 08 0f b6 c0 c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 48 85 ff 74 4f 48 8b 07 48 85 c0 74 47 <48> 8b 00 48 3d fc 03 00 00 76 1c 48 83 e0 fc 0f b6 50 14 48 39 74 [Mon Jul 10 19:46:26 2023] bijiben-shell-s[3224]: segfault at 7fcb58c86283 ip 7fccc790c5a1 sp 7ffd276291d8 error 4 in libgobject-2.0.so.0.7600.1[7fccc78e2000+34000] likely on CPU 2 (core 2, socket 0) [Mon Jul 10 19:46:26 2023] Code: c0 0f 95 c0 48 83 c4 08 0f b6 c0 c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 48 85 ff 74 4f 48 8b 07 48 85 c0 74 47 <48> 8b 00 48 3d fc 03 00 00 76 1c 48 83 e0 fc 0f b6 50 14 48 39 74 [Mon Jul 10 19:46:27 2023] bijiben-shell-s[3278]: segfault at 7f33cc004 ip 7f33f16425a1 sp 7ffd563f0fb8 error 4 in libgobject-2.0.so.0.7600.1[7f33f1618000+34000] likely on CPU 0 (core 0, socket 0) [Mon Jul 10 19:46:27 2023] Code: c0 0f 95 c0 48 83 c4 08 0f b6 c0 c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 48 85 ff 74 4f 48 8b 07 48 85 c0 74 47 <48> 8b 00 48 3d
[Desktop-packages] [Bug 2026789] [NEW] Xorg display freeze when using gnome settings " display" to enable/disable displays on eGPU
Public bug reported: When using the Ubuntu settings app to change displays I was enabling and disabling displays to see if I could replicate a problem. It appears that the drivers / setup are OK with 2x displays, but things start to fall apart when there are 3x displays. 2x displys managed by NVIDIA displayport connection, and 1x display managed by the Intel Iris GPU. I have noticed that windows appear to move between displays, so I think there is a problem with how the displays and the windows are arranged. Attached are as many logs as I can find for this problem. Notably, I am receiving errors in my local terminal when reporting this bug: [15578:15578:0710/200056.340294:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times! [15578:15578:0710/200056.356275:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times! [15578:15578:0710/200056.357312:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times! [15529:15529:0710/200138.416553:ERROR:object_proxy.cc(590)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not implemented This appears to be related to DRM ?? Tehese messages occured as I enabled / disabled the displays on displayport: [Mon Jul 10 19:53:29 2023] [drm] [nvidia-drm] [GPU ID 0x5200] Framebuffer memory not appropriate for scanout [Mon Jul 10 19:53:29 2023] [drm] [nvidia-drm] [GPU ID 0x5200] Framebuffer memory not appropriate for scanout [Mon Jul 10 19:53:41 2023] [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x5200] Failed to map NvKmsKapiMemory 0xfc099386 [Mon Jul 10 19:54:23 2023] [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x5200] Failed to map NvKmsKapiMemory 0xcd359766 [Mon Jul 10 19:54:23 2023] [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x5200] Failed to map NvKmsKapiMemory 0x40936ab7 These messages appeard when I started the gnome display manager : Mon Jul 10 19:46:16 2023] rfkill: input handler enabled [Mon Jul 10 19:46:17 2023] usb 2-2.2: current rate 16000 is different from the runtime rate 48000 [Mon Jul 10 19:46:17 2023] usb 2-2.2: current rate 16000 is different from the runtime rate 48000 [Mon Jul 10 19:46:17 2023] usb 2-2.2: current rate 16000 is different from the runtime rate 48000 [Mon Jul 10 19:46:17 2023] [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x5200] Failed to map NvKmsKapiMemory 0xf989da34 [Mon Jul 10 19:46:17 2023] [drm:__nv_drm_gem_nvkms_map [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x5200] Failed to map NvKmsKapiMemory 0x32149488 [Mon Jul 10 19:46:18 2023] rfkill: input handler disabled [Mon Jul 10 19:46:25 2023] bijiben-shell-s[3102]: segfault at 7f9c05be1b13 ip 7f9c1bb4e5a1 sp 7fff6f49e438 error 4 in libgobject-2.0.so.0.7600.1[7f9c1bb24000+34000] likely on CPU 6 (core 2, socket 0) [Mon Jul 10 19:46:25 2023] Code: c0 0f 95 c0 48 83 c4 08 0f b6 c0 c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 48 85 ff 74 4f 48 8b 07 48 85 c0 74 47 <48> 8b 00 48 3d fc 03 00 00 76 1c 48 83 e0 fc 0f b6 50 14 48 39 74 [Mon Jul 10 19:46:26 2023] bijiben-shell-s[3224]: segfault at 7fcb58c86283 ip 7fccc790c5a1 sp 7ffd276291d8 error 4 in libgobject-2.0.so.0.7600.1[7fccc78e2000+34000] likely on CPU 2 (core 2, socket 0) [Mon Jul 10 19:46:26 2023] Code: c0 0f 95 c0 48 83 c4 08 0f b6 c0 c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 48 85 ff 74 4f 48 8b 07 48 85 c0 74 47 <48> 8b 00 48 3d fc 03 00 00 76 1c 48 83 e0 fc 0f b6 50 14 48 39 74 [Mon Jul 10 19:46:27 2023] bijiben-shell-s[3278]: segfault at 7f33cc004 ip 7f33f16425a1 sp 7ffd563f0fb8 error 4 in libgobject-2.0.so.0.7600.1[7f33f1618000+34000] likely on CPU 0 (core 0, socket 0) [Mon Jul 10 19:46:27 2023] Code: c0 0f 95 c0 48 83 c4 08 0f b6 c0 c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 48 85 ff 74 4f 48 8b 07 48 85 c0 74 47 <48> 8b 00 48 3d fc 03 00 00 76 1c 48 83 e0 fc 0f b6 50 14 48 39 74 [Mon Jul 10 19:46:28 2023] bijiben-shell-s[]: segfault at 7f5bedc1f1b1 ip 7f5c3a6025a1 sp 7ffdba3e2308 error 4 in libgobject-2.0.so.0.7600.1[7f5c3a5d8000+34000] likely on CPU 0 (core 0, socket 0) [Mon Jul 10 19:46:28 2023] Code: c0 0f 95 c0 48 83 c4 08 0f b6 c0 c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 f3 0f 1e fa 48 85 ff 74 4f 48 8b 07 48 85 c0 74 47 <48> 8b 00 48 3d fc 03 00 00 76 1c 48 83 e0 fc 0f b6 50 14 48 39 74 [Mon Jul 10 19:46:29 2023] bijiben-shell-s[3384]: segfault at 7f58ddf0b019 ip 7f5f493745a1 sp 7ffc9b25f038 error 4 in libgobject-2.0.so.0.7600.1[7f5f4934a000+34000] likely on CPU 6 (core 2, socket 0) [Mon Jul 10 19:46:29 2023] Code: c0 0f 95 c0 48 83 c4 08 0f b6 c0 c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90
[Desktop-packages] [Bug 2026194] Re: When clicking on some maximized or tiled windows, focus on roughly the lower quarter falls to the window behind
One thing I've found is this is a high frequency occurrence with IntelliJ. I have not seen this issue with the snap versions of Sublime Text or Firefox. I did experience the issue in the snap version of GIMP the one time I had it open. Another interesting effect is that I am unable to resize the window in the lower corners, even if all the elements within the window are otherwise behaving normally. This is not true of Firefox or Sublime. In addition, Sublime and Firefox render shadows outside their window borders, whereas the IntelliJ window does not. I have no idea if any of this is related. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2026194 Title: When clicking on some maximized or tiled windows, focus on roughly the lower quarter falls to the window behind Status in gnome-shell package in Ubuntu: New Bug description: Initially I thought this was an issue with IntelliJ and filed a bug there: https://youtrack.jetbrains.com/issue/IDEA-323780/Maximizing-the-the-window-sometimes-causes-clicks-on-a-lower-fraction-to-pass-through-to-the-window-behind But when I had the same issue with GIMP, I realized it's an Ubuntu or GNOME issue instead. I am assuming this is a gnome-shell problem. Every once in a while, when I maximize or tile (Win+Right) the IntelliJ window, a bottom fraction of the window (somewhere around a quarter) becomes impossible to interact with, with the mouse. Clicking in that lower area will give focus to the thing behind IntelliJ, and if it's a window, raise it to the foreground. if I restore the window so that it is not maximized, the entire window is interactive with the mouse once again. This also happened with GIMP. The attached "Screencast" is a recording. I had to crop it to hide personal information. The attached screenshot shows the state of my screen so you have context, with a bright green color used to replace personal information. For the first 10s of the recording, I simply moused over to show how the cursor changes around a quarter from the bottom of the screen. For the next 10s, I left click, then move, then left click, then move, until focus changes to Sublime, the window behind IntelliJ. For the remainder of the video I show that right-clicking and mousing over works fine on the top three quarters, until I reach the bottom again, and then the right click is sent to Sublime. Ubuntu 23.04 gnome-shell version 44.2-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.2-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 5 12:05:46 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-19 (289 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=screen-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026255] Re: New windows have confused sizing when monitors are set to different scaling factors
Thanks. The issue sounds like it's in mutter's constraints logic so please report it at: https://gitlab.gnome.org/GNOME/mutter/-/issues -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2026255 Title: New windows have confused sizing when monitors are set to different scaling factors Status in mutter package in Ubuntu: New Bug description: I have 3 monitors, two QHD monitors and the screen of the laptop attached. I'm using Gnome-shell with the extensions disabled. If a window starts maximized it only takes a portion of the screen, if a window starts unmaximized it automatically doubles the size when it loses the focus. I have attached a small video of the behavior of the middle QHD monitor. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.2-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 6 09:35:26 2023 DisplayManager: gdm3 InstallationDate: Installed on 2021-06-21 (744 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 44.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-12 (55 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2026255/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026754] Re: [amdgpu][nvidia] HDMI picture not updating automatically, but only on mouse move.
Please also run: grep . /sys/class/drm/*/status > outputs.txt and attach the resulting text file here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2026754 Title: [amdgpu][nvidia] HDMI picture not updating automatically, but only on mouse move. Status in nvidia-graphics-drivers-535 package in Ubuntu: New Status in xorg-server package in Ubuntu: Incomplete Bug description: I use Asus FA507XI laptop with AMD 7940HS and NVIDIA RTX 4070. When using the second display via HDMI its picture not updating automatically, but only on mouse move. Additionally brightness control is not visible, so I can't change brightness. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.4.0-060400-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.54.03 Tue Jun 6 22:20:39 UTC 2023 GCC version: gcc version 12.1.0 (Ubuntu 12.1.0-2ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 10 18:22:48 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/535.54.03, 6.4.0-060400-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:2860] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:23bd] Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:23bd] InstallationDate: Installed on 2023-06-14 (25 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming A15 FA507XI_FA507XI ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.4.0-060400-generic root=UUID=83cb4370-0eb1-47b5-8095-f0cc24cbfd0e ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2023 dmi.bios.release: 5.29 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: FA507XI.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA507XI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.4 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFA507XI.307:bd06/14/2023:br5.29:efr3.4:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingA15FA507XI_FA507XI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA507XI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ASUS TUF Gaming A15 dmi.product.name: ASUS TUF Gaming A15 FA507XI_FA507XI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2026754/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026754] Re: Xorg freeze
Thanks for the bug report. The attached Xorg logs seem to be old, from last month. Please run this command to collect a fresh log when the problem is happening: journalctl -b0 > journal.txt and attach the resulting text file here. ** Tags added: amdgpu hybrid multigpu multimonitor nvidia ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Summary changed: - Xorg freeze + [amdgpu][nvidia] HDMI picture not updating automatically, but only on mouse move. ** Also affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2026754 Title: [amdgpu][nvidia] HDMI picture not updating automatically, but only on mouse move. Status in nvidia-graphics-drivers-535 package in Ubuntu: New Status in xorg-server package in Ubuntu: Incomplete Bug description: I use Asus FA507XI laptop with AMD 7940HS and NVIDIA RTX 4070. When using the second display via HDMI its picture not updating automatically, but only on mouse move. Additionally brightness control is not visible, so I can't change brightness. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.4.0-060400-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.54.03 Tue Jun 6 22:20:39 UTC 2023 GCC version: gcc version 12.1.0 (Ubuntu 12.1.0-2ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 10 18:22:48 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/535.54.03, 6.4.0-060400-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:2860] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:23bd] Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:23bd] InstallationDate: Installed on 2023-06-14 (25 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming A15 FA507XI_FA507XI ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.4.0-060400-generic root=UUID=83cb4370-0eb1-47b5-8095-f0cc24cbfd0e ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2023 dmi.bios.release: 5.29 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: FA507XI.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA507XI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.4 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFA507XI.307:bd06/14/2023:br5.29:efr3.4:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingA15FA507XI_FA507XI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA507XI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ASUS TUF Gaming A15 dmi.product.name: ASUS TUF Gaming A15 FA507XI_FA507XI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to:
[Desktop-packages] [Bug 2026727] Re: Clicking on a notification no longer raises window in LTS 22.04.3
Please test without these extensions: 'gsconn...@andyholmes.github.io', 'user-th...@gnome-shell-extensions.gcampax.github.com', 'always-indica...@martin.zurowietz.de' ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2026727 Title: Clicking on a notification no longer raises window in LTS 22.04.3 Status in gnome-shell package in Ubuntu: Incomplete Bug description: As part of the LTS 22.04.3 release many gnome package updates are available in the 'proposed' repository. When checking these on a test machine I noticed that the window raise behavior when clicking on notifications has regressed for some applications. In 22.04.2 clicking on a notification in gnome shell would raise the application window and focus the inbox or chat channel the message was received in. In the 22.04.3 proposed packages this is still the case for e.g. Thunderbird, but for other applications such as 'slack' and 'signal' clicking on a new message notification no longer raises the application window. Although not a major bug, it's quite annoying as it breaks the workflow and means extra work in finding the application and the channel that the message arrived at. Due to the many package updates it's not clear to me which update broke the behavior (maybe mutter or gnome-shell) but filing it under shell because of the notification area issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-77.84-generic 5.15.108 Uname: Linux 5.15.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 10 08:47:24 2023 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-02 (1102 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-11-19 (232 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026733] Re: EXT4-fs error
Please clarify what the problem is you would like to report. Which log message are you referring to? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2026733 Title: EXT4-fs error Status in Ubuntu: Incomplete Bug description: Jul 10 19:23:10 anonymous kernel: ACPI Error: Aborting method \_GPE._L69 due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Jul 10 19:23:12 anonymous systemd[1]: Started Process error reports when automatic reporting is enabled (file watch). Jul 10 19:23:12 anonymous systemd[1]: Started Process error reports when automatic reporting is enabled (timer based). Jul 10 19:23:13 anonymous systemd[1]: Starting Process error reports when automatic reporting is enabled... Jul 10 19:23:13 anonymous systemd[1]: Finished Process error reports when automatic reporting is enabled. Jul 10 19:23:13 anonymous containerd[900]: time="2023-07-10T19:23:13.470289148+05:30" level=info msg="skip loading plugin \"io.containerd.snapshotter.v1.aufs\"..." error="aufs is not supported (modprobe aufs failed: exit status 1 \"modprobe: FATAL: Module aufs not found in directory /lib/modules/5.19.0-46-generic\\n\"): skip plugin" type=io.containerd.snapshotter.v1 Jul 10 19:23:13 anonymous containerd[900]: time="2023-07-10T19:23:13.470922616+05:30" level=info msg="skip loading plugin \"io.containerd.snapshotter.v1.btrfs\"..." error="path /var/lib/containerd/io.containerd.snapshotter.v1.btrfs (ext4) must be a btrfs filesystem to be used with the btrfs snapshotter: skip plugin" type=io.containerd.snapshotter.v1 Jul 10 19:23:13 anonymous containerd[900]: time="2023-07-10T19:23:13.471094626+05:30" level=warning msg="failed to load plugin io.containerd.snapshotter.v1.devmapper" error="devmapper not configured" Jul 10 19:23:13 anonymous containerd[900]: time="2023-07-10T19:23:13.473855132+05:30" level=info msg="skip loading plugin \"io.containerd.snapshotter.v1.zfs\"..." error="path /var/lib/containerd/io.containerd.snapshotter.v1.zfs must be a zfs filesystem to be used with the zfs snapshotter: skip plugin" type=io.containerd.snapshotter.v1 Jul 10 19:23:13 anonymous containerd[900]: time="2023-07-10T19:23:13.474029763+05:30" level=warning msg="could not use snapshotter devmapper in metadata plugin" error="devmapper not configured" Jul 10 19:23:13 anonymous containerd[900]: time="2023-07-10T19:23:13.480101696+05:30" level=info msg="skip loading plugin \"io.containerd.tracing.processor.v1.otlp\"..." error="no OpenTelemetry endpoint: skip plugin" type=io.containerd.tracing.processor.v1 Jul 10 19:23:13 anonymous containerd[900]: time="2023-07-10T19:23:13.480277677+05:30" level=error msg="failed to initialize a tracing processor \"otlp\"" error="no OpenTelemetry endpoint: skip plugin" Jul 10 19:23:13 anonymous kernel: pcieport :00:1c.5: AER: Corrected error received: :00:1c.5 Jul 10 19:23:13 anonymous kernel: pcieport :00:1c.5: device [8086:9d15] error status/mask=0001/2000 Jul 10 19:23:13 anonymous gnome-session[1102]: gnome-session-binary[1102]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Jul 10 19:23:13 anonymous gnome-session-binary[1102]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Jul 10 19:23:13 anonymous gnome-session[1102]: gnome-session-binary[1102]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Jul 10 19:23:13 anonymous gnome-session-binary[1102]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Jul 10 19:23:15 anonymous canonical-livepatch.canonical-livepatchd[879]: Task "refresh" returned an error: livepatch check failed: POST request to "https://livepatch.canonical.com/v1/client/69544c7dfaeb49e69a97beae74302b02/updates; failed, retrying in 30s. Jul 10 19:23:40 anonymous snap-store[2411]: not handling error failed for action refresh: E: Failed to fetch https://packagecloud.io/slacktechnologies/slack/debian/dists/jessie/InRelease Jul 10 19:23:42 anonymous snap-store[2411]: not handling error failed for action refresh: E: Failed to fetch http://in.archive.ubuntu.com/ubuntu/dists/jammy/InRelease Jul 10 19:24:23 anonymous google-chrome.desktop[8732]: libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) Jul 10 19:25:04 anonymous kernel: pcieport :00:1c.5: AER: Corrected error received: :00:1c.5 Jul 10 19:25:04 anonymous kernel: pcieport :00:1c.5: device [8086:9d15] error status/mask=0001/2000 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux
[Desktop-packages] [Bug 1966167] Re: Ubuntu Dock icons not clickable at the edge of the screen
It's committed to the git branch 'ubuntu-dock-jammy' but not in proposed yet. The desktop team policy of saying 'Fix Committed' before anything is even in proposed was started by Seb. I wouldn't mind if we revisited that though because it does confuse other teams and even ourselves. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1966167 Title: Ubuntu Dock icons not clickable at the edge of the screen Status in Dash to dock: New Status in Yaru Theme: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Committed Status in yaru-theme source package in Jammy: Fix Committed Bug description: [ Impact ] If you go to the bottom left corner of the dock and click, the All Apps button doesn't get triggered or highlighted. Check attached video for details. [ Test case ] For verifying yaru-theme, in the Ubuntu session: 1. Move the pointer to the edge of the screen where the AppIcons button is visible (bottom-left corner by default) 2. The button should be highlighted and clicking it should open the applications grid [ Regression potential ] - The dock margins are wrong or icons are not clickable in their edges - There's no not-reactive space between the activity button and the first icon --- Ubuntu 21.10. Live mode. 1920x1080 screen. To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1966167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 189517] Re: pkexec needs ability to retain user HOME and possibly other environment
my fedora computer has pkexec version 121 which has the --keep-cwd option. if ubuntu would update pkexec i'm guessing it would have that option too. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/189517 Title: pkexec needs ability to retain user HOME and possibly other environment Status in gparted package in Ubuntu: Invalid Status in policykit-1 package in Ubuntu: Confirmed Bug description: Launching gui applications with pkexec strips their environment bare and points the home directory to /root, causing the gnome file dialog to behave badly. It needs a way to preserve the user home the way sudo and gksu do. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/189517/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026611] Re: package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade: installed nvidia-340 package post-installation script subprocess returned error exit status
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/2026611 Title: package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade: installed nvidia-340 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.40.0+dfsg-3ubuntu0.4) ... Processing triggers for sgml-base (1.29.1) ... Errors were encountered while processing: nvidia-340 Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 4.15.0-213.224-generic 4.15.18 Uname: Linux 4.15.0-213-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jul 8 00:47:33 2023 ErrorMessage: installed nvidia-340 package post-installation script subprocess returned error exit status 10 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 340.108-0ubuntu5.20.04.2 failed to install/upgrade: installed nvidia-340 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to focal on 2023-07-08 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/2026611/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2025537] Re: chrome Check failed
*** This bug is a duplicate of bug 2017980 *** https://bugs.launchpad.net/bugs/2017980 @novhak Here is the output of "LC_ALL=C apt list --installed 'linux-*'” Listing... Done linux-base/jammy,jammy,now 4.5ubuntu9 all [installed,automatic] linux-firmware/jammy-updates,jammy-updates,jammy-security,jammy-security,now 20220329.git681281e4-0ubuntu3.14 all [installed,automatic] linux-generic-hwe-22.04/jammy-updates,jammy-security,now 5.19.0.46.47~22.04.21 amd64 [installed] linux-headers-5.19.0-46-generic/jammy-updates,jammy-security,now 5.19.0-46.47~22.04.1 amd64 [installed,automatic] linux-headers-generic-hwe-22.04/jammy-updates,jammy-security,now 5.19.0.46.47~22.04.21 amd64 [installed,automatic] linux-hwe-5.19-headers-5.19.0-46/jammy-updates,jammy-updates,jammy-security,jammy-security,now 5.19.0-46.47~22.04.1 all [installed,automatic] linux-image-5.19.0-1010-nvidia-lowlatency/jammy-updates,jammy-security,now 5.19.0-1010.10 amd64 [installed,automatic] linux-image-5.19.0-46-generic/jammy-updates,jammy-security,now 5.19.0-46.47~22.04.1 amd64 [installed,automatic] linux-image-generic-hwe-22.04/jammy-updates,jammy-security,now 5.19.0.46.47~22.04.21 amd64 [installed,automatic] linux-libc-dev/jammy-updates,jammy-security,now 5.15.0-76.83 amd64 [installed,automatic] linux-modules-5.19.0-1010-nvidia-lowlatency/jammy-updates,jammy-security,now 5.19.0-1010.10 amd64 [installed,automatic] linux-modules-5.19.0-46-generic/jammy-updates,jammy-security,now 5.19.0-46.47~22.04.1 amd64 [installed,automatic] linux-modules-extra-5.19.0-46-generic/jammy-updates,jammy-security,now 5.19.0-46.47~22.04.1 amd64 [installed,automatic] linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency/jammy-updates,jammy-security,now 5.19.0-1010.10 amd64 [installed,automatic] linux-modules-nvidia-510-generic-hwe-22.04/jammy-updates,jammy-security,now 5.19.0-46.47~22.04.1+5 amd64 [installed] linux-modules-nvidia-510-nvidia-lowlatency-edge/jammy-updates,jammy-security,now 5.19.0-1010.10 amd64 [installed,auto-removable] linux-modules-nvidia-525-5.19.0-46-generic/jammy-updates,jammy-security,now 5.19.0-46.47~22.04.1+5 amd64 [installed,automatic] linux-modules-nvidia-525-generic-hwe-22.04/jammy-updates,jammy-security,now 5.19.0-46.47~22.04.1+5 amd64 [installed,automatic] linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency/jammy-updates,jammy-security,now 5.19.0-1010.10 amd64 [installed,automatic] linux-objects-nvidia-525-5.19.0-46-generic/jammy-updates,jammy-security,now 5.19.0-46.47~22.04.1+5 amd64 [installed,automatic] linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency/jammy-updates,jammy-security,now 5.19.0-1010.10 amd64 [installed,automatic] linux-signatures-nvidia-5.19.0-46-generic/jammy-updates,jammy-security,now 5.19.0-46.47~22.04.1+5 amd64 [installed,automatic] linux-sound-base/jammy,jammy,now 1.0.25+dfsg-0ubuntu7 all [installed,automatic] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2025537 Title: chrome Check failed Status in chromium-browser package in Ubuntu: Incomplete Bug description: local_slava@worksystem:~$ google-chrome [19394:19394:0701/201749.072306:FATAL:credentials.cc(127)] Check failed: . : Отказано в доступе (13) Trace/breakpoint trap (core dumped) How fix this? After update ubuntu... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2025537/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026644] Re: Unaware of a problem.
*** This bug is a duplicate of bug 2000858 *** https://bugs.launchpad.net/bugs/2000858 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2000858, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2026644/+attachment/5684912/+files/CoreDump.gz ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2026644/+attachment/5684914/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2026644/+attachment/5684915/+files/ProcStatus.txt ** This bug has been marked a duplicate of private bug 2000858 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/2026644 Title: Unaware of a problem. Status in xdg-desktop-portal package in Ubuntu: New Bug description: not sure why it wants to report. not SEEING any issues. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: xdg-desktop-portal 1.16.0-2ubuntu1 Uname: Linux 6.3.0-7-generic x86_64 Architecture: amd64 CurrentDesktop: KDE Date: Sat Jul 8 20:59:58 2023 ExecutablePath: /usr/libexec/xdg-desktop-portal ExecutableTimestamp: 1674671583 ProcCmdline: /usr/libexec/xdg-desktop-portal ProcCwd: /home/etctweak ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 11 SourcePackage: xdg-desktop-portal UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/2026644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026733] Re: EXT4-fs error
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2026733 Title: EXT4-fs error Status in xorg package in Ubuntu: New Bug description: Jul 10 19:23:10 anonymous kernel: ACPI Error: Aborting method \_GPE._L69 due to previous error (AE_NOT_FOUND) (20220331/psparse-529) Jul 10 19:23:12 anonymous systemd[1]: Started Process error reports when automatic reporting is enabled (file watch). Jul 10 19:23:12 anonymous systemd[1]: Started Process error reports when automatic reporting is enabled (timer based). Jul 10 19:23:13 anonymous systemd[1]: Starting Process error reports when automatic reporting is enabled... Jul 10 19:23:13 anonymous systemd[1]: Finished Process error reports when automatic reporting is enabled. Jul 10 19:23:13 anonymous containerd[900]: time="2023-07-10T19:23:13.470289148+05:30" level=info msg="skip loading plugin \"io.containerd.snapshotter.v1.aufs\"..." error="aufs is not supported (modprobe aufs failed: exit status 1 \"modprobe: FATAL: Module aufs not found in directory /lib/modules/5.19.0-46-generic\\n\"): skip plugin" type=io.containerd.snapshotter.v1 Jul 10 19:23:13 anonymous containerd[900]: time="2023-07-10T19:23:13.470922616+05:30" level=info msg="skip loading plugin \"io.containerd.snapshotter.v1.btrfs\"..." error="path /var/lib/containerd/io.containerd.snapshotter.v1.btrfs (ext4) must be a btrfs filesystem to be used with the btrfs snapshotter: skip plugin" type=io.containerd.snapshotter.v1 Jul 10 19:23:13 anonymous containerd[900]: time="2023-07-10T19:23:13.471094626+05:30" level=warning msg="failed to load plugin io.containerd.snapshotter.v1.devmapper" error="devmapper not configured" Jul 10 19:23:13 anonymous containerd[900]: time="2023-07-10T19:23:13.473855132+05:30" level=info msg="skip loading plugin \"io.containerd.snapshotter.v1.zfs\"..." error="path /var/lib/containerd/io.containerd.snapshotter.v1.zfs must be a zfs filesystem to be used with the zfs snapshotter: skip plugin" type=io.containerd.snapshotter.v1 Jul 10 19:23:13 anonymous containerd[900]: time="2023-07-10T19:23:13.474029763+05:30" level=warning msg="could not use snapshotter devmapper in metadata plugin" error="devmapper not configured" Jul 10 19:23:13 anonymous containerd[900]: time="2023-07-10T19:23:13.480101696+05:30" level=info msg="skip loading plugin \"io.containerd.tracing.processor.v1.otlp\"..." error="no OpenTelemetry endpoint: skip plugin" type=io.containerd.tracing.processor.v1 Jul 10 19:23:13 anonymous containerd[900]: time="2023-07-10T19:23:13.480277677+05:30" level=error msg="failed to initialize a tracing processor \"otlp\"" error="no OpenTelemetry endpoint: skip plugin" Jul 10 19:23:13 anonymous kernel: pcieport :00:1c.5: AER: Corrected error received: :00:1c.5 Jul 10 19:23:13 anonymous kernel: pcieport :00:1c.5: device [8086:9d15] error status/mask=0001/2000 Jul 10 19:23:13 anonymous gnome-session[1102]: gnome-session-binary[1102]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Jul 10 19:23:13 anonymous gnome-session-binary[1102]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Jul 10 19:23:13 anonymous gnome-session[1102]: gnome-session-binary[1102]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Jul 10 19:23:13 anonymous gnome-session-binary[1102]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Jul 10 19:23:15 anonymous canonical-livepatch.canonical-livepatchd[879]: Task "refresh" returned an error: livepatch check failed: POST request to "https://livepatch.canonical.com/v1/client/69544c7dfaeb49e69a97beae74302b02/updates; failed, retrying in 30s. Jul 10 19:23:40 anonymous snap-store[2411]: not handling error failed for action refresh: E: Failed to fetch https://packagecloud.io/slacktechnologies/slack/debian/dists/jessie/InRelease Jul 10 19:23:42 anonymous snap-store[2411]: not handling error failed for action refresh: E: Failed to fetch http://in.archive.ubuntu.com/ubuntu/dists/jammy/InRelease Jul 10 19:24:23 anonymous google-chrome.desktop[8732]: libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) Jul 10 19:25:04 anonymous kernel: pcieport :00:1c.5: AER: Corrected error received: :00:1c.5 Jul 10 19:25:04 anonymous kernel: pcieport :00:1c.5: device [8086:9d15] error status/mask=0001/2000 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
[Desktop-packages] [Bug 2026754] [NEW] Xorg freeze
Public bug reported: I use Asus FA507XI laptop with AMD 7940HS and NVIDIA RTX 4070. When using the second display via HDMI its picture not updating automatically, but only on mouse move. Additionally brightness control is not visible, so I can't change brightness. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.4.0-060400-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.54.03 Tue Jun 6 22:20:39 UTC 2023 GCC version: gcc version 12.1.0 (Ubuntu 12.1.0-2ubuntu1~22.04) ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 10 18:22:48 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: nvidia/535.54.03, 6.4.0-060400-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:2860] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:23bd] Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:15bf] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:23bd] InstallationDate: Installed on 2023-06-14 (25 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) MachineType: ASUSTeK COMPUTER INC. ASUS TUF Gaming A15 FA507XI_FA507XI ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.4.0-060400-generic root=UUID=83cb4370-0eb1-47b5-8095-f0cc24cbfd0e ro quiet splash acpi_backlight=vendor vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2023 dmi.bios.release: 5.29 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: FA507XI.307 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA507XI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.4 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrFA507XI.307:bd06/14/2023:br5.29:efr3.4:svnASUSTeKCOMPUTERINC.:pnASUSTUFGamingA15FA507XI_FA507XI:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA507XI:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ASUS TUF Gaming A15 dmi.product.name: ASUS TUF Gaming A15 FA507XI_FA507XI dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug false-gpu-hang freeze jammy third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2026754 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: I use Asus FA507XI laptop with AMD 7940HS and NVIDIA RTX 4070. When using the second display via HDMI its picture not updating automatically, but only on mouse move. Additionally brightness control is not visible, so I can't change brightness. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 Uname: Linux 6.4.0-060400-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX
[Desktop-packages] [Bug 2025651] Re: default Japanese font in snap apps is ugly
Additional observation: If I refresh into FF latest/stable, the undesired line /etc/fonts/conf.d gets written into ~/snap/firefox/current/.config/fontconfig/fonts.conf. I suppose the reason is that the snap from that channel is linked to gnome-3-38-2004 which has not (yet) been updated in this respect. Consequently the fix of this bug will reach all users only after: 1. the change of gnome-42-2204 has made it to latest/stable, and 2. the FF snap in latest/stable/ubuntu-23.04 is updated to a new revision. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2025651 Title: default Japanese font in snap apps is ugly Status in Snappy: Fix Committed Status in language-selector package in Ubuntu: Invalid Bug description: Japanese fonts in snap packages such as Firefox use glyphs from Chinese fonts. non-snap packages are fine. This is derived from the following ticket: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076 How to reproduce: 1. Install lunar or mantic with Japanese language pack 2. Enable Japanese locale 3. Start Firefox 4. Type or Copy "刃" to address field and type enter 5. Check glyph of "刃" Expected result: The following Japanese glyph is displayed: https://glyphwiki.org/wiki/u5203 Actual result: The following Chinese? glyph is displayed: https://glyphwiki.org/wiki/zihai-018904 Others: * Ubuntu 22.04 LTS not affected, works fine. * Fixed if you remove fonts-droid-fallback package. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2025651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.
@Nathan Thank you for the clarity on the Core20 vs Core22, however, I will still maintain that had this latest Chromium SNAP been built on Core20, as has seemingly been until now, we wouldn't be having this dialog. When Chromium has been built against Core20, I've been able to call chromium headless from Apache via: /snap/chromium/current/usr/lib/chromium-browser/chrome ... and it hasn't mattered which "build" the ../current/... pointed to. For me, Chromium built on Core22 is what "broke" my setup. Again, I appreciate the stable/core20 build, and will have to commit to within 30 days: a) Upgrade our production environments to Ubuntu 22.04 b) Stop using Ubuntu altogether, and go with straight-Debian, so "apt install chromium-browser" actually installs the Debian package, not force install a SNAP (comment for future readers, not trying to argue that APT pushes the SNAP installs for Chromium on Ubuntu) c) find an alternative way to generate PDF from HTML reports -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2026200 Title: Snap update broke launching and printing on 20.04 Ubuntu. Status in chromium-browser package in Ubuntu: Invalid Status in cups package in Ubuntu: Incomplete Bug description: Two deployed ubuntu images, 20.04 and 22.04. Both images are fully updated. Issue appears to only impact 20.04. chrome snap version 2529 Launching chrome from menu shortcut that is managed by the snap works and it using this location /snap/bin/chromium Launching chrome from desktop shortcut that I manage on 20.04 fails - /snap/chromium/current/usr/lib/chromium-browser/chrome Updating the desktop shortcut with this location on 20.04 works - /snap/bin/chromium Try and print from the browser, print dialog in chrome does not list any system printers, only shows PDF. Doing the same on 22.04 image, I get a list of printers. CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No such file or directory" I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 100% failure rate on 20.04. I get this error when running chrome from cli from this path on 20.04 /snap/chromium/current/usr/lib/chromium-browser which points to 2529 snap image. /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026194] Re: When clicking on some maximized or tiled windows, focus on roughly the lower quarter falls to the window behind
Interestingly, this also happened once where the right quarter was clicking through as well. I noticed this when trying to interact with the title bar buttons (minimize, restore, close) and I ended up clicking the title bar buttons of the window behind. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2026194 Title: When clicking on some maximized or tiled windows, focus on roughly the lower quarter falls to the window behind Status in gnome-shell package in Ubuntu: New Bug description: Initially I thought this was an issue with IntelliJ and filed a bug there: https://youtrack.jetbrains.com/issue/IDEA-323780/Maximizing-the-the-window-sometimes-causes-clicks-on-a-lower-fraction-to-pass-through-to-the-window-behind But when I had the same issue with GIMP, I realized it's an Ubuntu or GNOME issue instead. I am assuming this is a gnome-shell problem. Every once in a while, when I maximize or tile (Win+Right) the IntelliJ window, a bottom fraction of the window (somewhere around a quarter) becomes impossible to interact with, with the mouse. Clicking in that lower area will give focus to the thing behind IntelliJ, and if it's a window, raise it to the foreground. if I restore the window so that it is not maximized, the entire window is interactive with the mouse once again. This also happened with GIMP. The attached "Screencast" is a recording. I had to crop it to hide personal information. The attached screenshot shows the state of my screen so you have context, with a bright green color used to replace personal information. For the first 10s of the recording, I simply moused over to show how the cursor changes around a quarter from the bottom of the screen. For the next 10s, I left click, then move, then left click, then move, until focus changes to Sublime, the window behind IntelliJ. For the remainder of the video I show that right-clicking and mousing over works fine on the top three quarters, until I reach the bottom again, and then the right click is sent to Sublime. Ubuntu 23.04 gnome-shell version 44.2-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.2-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 5 12:05:46 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-19 (289 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=screen-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.
> (I still maintain that if Ubuntu 20.04 LTS is supported until April > 2025, and its base SNAP is core20, it is not appropriate (if, only > because of my biased opinion) to build snaps on core22, which, you > admit, is the base snap core for Ubuntu 22.04) I think there is a misunderstanding here. Snaps for core22 can run in any series, be it 18.04, 20.04, 22.04 etc., otherwise it would really mean that for each series XX we would have to use the corresponding coreXX. They can only run in any series because they are not run directly as a binary that sees the host libraries, but rather uses snap confinment. So if your base is 20.04, a snap based on core22 works nonetheless, because it's seeing the libraries provided by core22 instead of your host system. That is _exactly_ what is sidestepped once you run it with the /snap/chromium/current/usr/lib/chromium-browser/chrome instead of the normal /snap/bin/chromium, namely the snap runs unconfined an thus uses the system libraries, which may be (and in the present case is) different than what it was linked it during its build, justifying the errors you see. > Do you have any sense of "how long" the stable/core20 channel will be > available? > > I am grateful for the stable/core20 build as of now, but need to plan to > either migrate to Ubuntu 22.04 (or later) or off Ubuntu altogether By default it's 30 days after launch, I'm happy to keep it alive for longer though if it will help, just note it is frozen, it will not be maintained, so new CVEs in Chromium or any of its dependent libraries won't be addressed and so on. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2026200 Title: Snap update broke launching and printing on 20.04 Ubuntu. Status in chromium-browser package in Ubuntu: Invalid Status in cups package in Ubuntu: Incomplete Bug description: Two deployed ubuntu images, 20.04 and 22.04. Both images are fully updated. Issue appears to only impact 20.04. chrome snap version 2529 Launching chrome from menu shortcut that is managed by the snap works and it using this location /snap/bin/chromium Launching chrome from desktop shortcut that I manage on 20.04 fails - /snap/chromium/current/usr/lib/chromium-browser/chrome Updating the desktop shortcut with this location on 20.04 works - /snap/bin/chromium Try and print from the browser, print dialog in chrome does not list any system printers, only shows PDF. Doing the same on 22.04 image, I get a list of printers. CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No such file or directory" I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 100% failure rate on 20.04. I get this error when running chrome from cli from this path on 20.04 /snap/chromium/current/usr/lib/chromium-browser which points to 2529 snap image. /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.
-- Nathan The symlink I'm referring to is the *current* in this path: /snap/chromium/**current**/usr/lib/chromium-browser/chrome ... which is a symlink to build 2529 or, now I have 2497 (I still maintain that if Ubuntu 20.04 LTS is supported until April 2025, and its base SNAP is core20, it is not appropriate (if, only because of my biased opinion) to build snaps on core22, which, you admit, is the base snap core for Ubuntu 22.04) Do you have any sense of "how long" the stable/core20 channel will be available? I am grateful for the stable/core20 build as of now, but need to plan to either migrate to Ubuntu 22.04 (or later) or off Ubuntu altogether -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2026200 Title: Snap update broke launching and printing on 20.04 Ubuntu. Status in chromium-browser package in Ubuntu: Invalid Status in cups package in Ubuntu: Incomplete Bug description: Two deployed ubuntu images, 20.04 and 22.04. Both images are fully updated. Issue appears to only impact 20.04. chrome snap version 2529 Launching chrome from menu shortcut that is managed by the snap works and it using this location /snap/bin/chromium Launching chrome from desktop shortcut that I manage on 20.04 fails - /snap/chromium/current/usr/lib/chromium-browser/chrome Updating the desktop shortcut with this location on 20.04 works - /snap/bin/chromium Try and print from the browser, print dialog in chrome does not list any system printers, only shows PDF. Doing the same on 22.04 image, I get a list of printers. CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No such file or directory" I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 100% failure rate on 20.04. I get this error when running chrome from cli from this path on 20.04 /snap/chromium/current/usr/lib/chromium-browser which points to 2529 snap image. /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023913] Update Released
The verification of the Stable Release Update for gnome-shell has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2023913 Title: Release gnome-shell 42.9 to Jammy Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.9/NEWS The overall GNOME project considers GNOME 42 to be end of life now and there are no more scheduled releases for GNOME Shell 42 after 42.9 The current version of GNOME Shell in Jammy is 42.5. Test Case - Complete all the non-optional test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- This update requires mutter 42.9 (LP: #1998286). This was done with bumped dependencies in debian/control. gnome-shell 42.9 could be run with mutter 42.5, but mixing different versions of mutter & gnome-shell is not supported upstream. WARNING --- Because of an apt phasing issue (LP: #2025462), gnome-shell 42.9 must NOT be released to updates until mutter 42.9 has been released to jammy-updates and has fully phased. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2023913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023913] Re: Release gnome-shell 42.9 to Jammy
This bug was fixed in the package gnome-shell - 42.9-0ubuntu2 --- gnome-shell (42.9-0ubuntu2) jammy; urgency=medium * New upstream release (LP: #2023913) * debian/control.in: Bump minimum mutter to 42.9 -- Jeremy Bícha Wed, 14 Jun 2023 15:35:33 -0400 ** Changed in: gnome-shell (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2023913 Title: Release gnome-shell 42.9 to Jammy Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Bug description: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.9/NEWS The overall GNOME project considers GNOME 42 to be end of life now and there are no more scheduled releases for GNOME Shell 42 after 42.9 The current version of GNOME Shell in Jammy is 42.5. Test Case - Complete all the non-optional test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- This update requires mutter 42.9 (LP: #1998286). This was done with bumped dependencies in debian/control. gnome-shell 42.9 could be run with mutter 42.5, but mixing different versions of mutter & gnome-shell is not supported upstream. WARNING --- Because of an apt phasing issue (LP: #2025462), gnome-shell 42.9 must NOT be released to updates until mutter 42.9 has been released to jammy-updates and has fully phased. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2023913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026230] Re: libnetplan integration breaks "cloned-mac-address" special values
Merged upstream. Will be part of the next Netplan release. ** Also affects: netplan Importance: Undecided Status: New ** Changed in: netplan Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2026230 Title: libnetplan integration breaks "cloned-mac-address" special values Status in netplan: Fix Committed Status in netplan.io package in Ubuntu: In Progress Status in network-manager package in Ubuntu: Invalid Bug description: I received an error from apport about a programme not working. I collected the data to submit. Hope this helps. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: network-manager 1.42.6-2ubuntu1 Uname: Linux 6.2.0-24-generic x86_64 Architecture: amd64 Date: Wed Jul 5 23:11:14 2023 ExecutablePath: /usr/sbin/NetworkManager ExecutableTimestamp: 1687429583 ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) Signal: 6 SourcePackage: network-manager UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2026230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026727] [NEW] Clicking on a notification no longer raises window in LTS 22.04.3
Public bug reported: As part of the LTS 22.04.3 release many gnome package updates are available in the 'proposed' repository. When checking these on a test machine I noticed that the window raise behavior when clicking on notifications has regressed for some applications. In 22.04.2 clicking on a notification in gnome shell would raise the application window and focus the inbox or chat channel the message was received in. In the 22.04.3 proposed packages this is still the case for e.g. Thunderbird, but for other applications such as 'slack' and 'signal' clicking on a new message notification no longer raises the application window. Although not a major bug, it's quite annoying as it breaks the workflow and means extra work in finding the application and the channel that the message arrived at. Due to the many package updates it's not clear to me which update broke the behavior (maybe mutter or gnome-shell) but filing it under shell because of the notification area issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-77.84-generic 5.15.108 Uname: Linux 5.15.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 10 08:47:24 2023 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-02 (1102 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-11-19 (232 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy package-from-proposed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2026727 Title: Clicking on a notification no longer raises window in LTS 22.04.3 Status in gnome-shell package in Ubuntu: New Bug description: As part of the LTS 22.04.3 release many gnome package updates are available in the 'proposed' repository. When checking these on a test machine I noticed that the window raise behavior when clicking on notifications has regressed for some applications. In 22.04.2 clicking on a notification in gnome shell would raise the application window and focus the inbox or chat channel the message was received in. In the 22.04.3 proposed packages this is still the case for e.g. Thunderbird, but for other applications such as 'slack' and 'signal' clicking on a new message notification no longer raises the application window. Although not a major bug, it's quite annoying as it breaks the workflow and means extra work in finding the application and the channel that the message arrived at. Due to the many package updates it's not clear to me which update broke the behavior (maybe mutter or gnome-shell) but filing it under shell because of the notification area issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-77.84-generic 5.15.108 Uname: Linux 5.15.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 10 08:47:24 2023 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-02 (1102 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-11-19 (232 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026727/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023913] Re: Release gnome-shell 42.9 to Jammy
I have dropped the block-proposed-jammy tag since Mutter 42.9 is in jammy-updates and has fully phased. I installed gnome-shell 42.9-0ubuntu2 on Ubuntu 22.04 LTS and successfully completed all 3 test cases. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2023913 Title: Release gnome-shell 42.9 to Jammy Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.9/NEWS The overall GNOME project considers GNOME 42 to be end of life now and there are no more scheduled releases for GNOME Shell 42 after 42.9 The current version of GNOME Shell in Jammy is 42.5. Test Case - Complete all the non-optional test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- This update requires mutter 42.9 (LP: #1998286). This was done with bumped dependencies in debian/control. gnome-shell 42.9 could be run with mutter 42.5, but mixing different versions of mutter & gnome-shell is not supported upstream. WARNING --- Because of an apt phasing issue (LP: #2025462), gnome-shell 42.9 must NOT be released to updates until mutter 42.9 has been released to jammy-updates and has fully phased. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2023913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026230] Re: libnetplan integration breaks "cloned-mac-address" special values
** Summary changed: - error when setting up after upgrading + libnetplan integration breaks "cloned-mac-address" special values -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2026230 Title: libnetplan integration breaks "cloned-mac-address" special values Status in netplan.io package in Ubuntu: In Progress Status in network-manager package in Ubuntu: Invalid Bug description: I received an error from apport about a programme not working. I collected the data to submit. Hope this helps. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: network-manager 1.42.6-2ubuntu1 Uname: Linux 6.2.0-24-generic x86_64 Architecture: amd64 Date: Wed Jul 5 23:11:14 2023 ExecutablePath: /usr/sbin/NetworkManager ExecutableTimestamp: 1687429583 ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) Signal: 6 SourcePackage: network-manager UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2026230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023913] Re: Release gnome-shell 42.9 to Jammy
** Tags removed: block-proposed-jammy verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2023913 Title: Release gnome-shell 42.9 to Jammy Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.9/NEWS The overall GNOME project considers GNOME 42 to be end of life now and there are no more scheduled releases for GNOME Shell 42 after 42.9 The current version of GNOME Shell in Jammy is 42.5. Test Case - Complete all the non-optional test cases at https://wiki.ubuntu.com/DesktopTeam/TestPlans/GNOMEShell What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- This update requires mutter 42.9 (LP: #1998286). This was done with bumped dependencies in debian/control. gnome-shell 42.9 could be run with mutter 42.5, but mixing different versions of mutter & gnome-shell is not supported upstream. WARNING --- Because of an apt phasing issue (LP: #2025462), gnome-shell 42.9 must NOT be released to updates until mutter 42.9 has been released to jammy-updates and has fully phased. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2023913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2025651] Re: default Japanese font in snap apps is ugly
~/snap/firefox/current/.config/fontconfig/fonts.conf was updated "automatically" on my mantic installation. Not sure which combo of circumstances made it happen, but I have core22 from the latest/candidate channel. Then I refreshed firefox (switched form latest/stable to latest/stable/ubuntu-23.10) so the revision was changed (from 2880 to 2851), and then when launching FF the fonts.conf file in question was updated as desired. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2025651 Title: default Japanese font in snap apps is ugly Status in Snappy: Fix Committed Status in language-selector package in Ubuntu: Invalid Bug description: Japanese fonts in snap packages such as Firefox use glyphs from Chinese fonts. non-snap packages are fine. This is derived from the following ticket: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076 How to reproduce: 1. Install lunar or mantic with Japanese language pack 2. Enable Japanese locale 3. Start Firefox 4. Type or Copy "刃" to address field and type enter 5. Check glyph of "刃" Expected result: The following Japanese glyph is displayed: https://glyphwiki.org/wiki/u5203 Actual result: The following Chinese? glyph is displayed: https://glyphwiki.org/wiki/zihai-018904 Others: * Ubuntu 22.04 LTS not affected, works fine. * Fixed if you remove fonts-droid-fallback package. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2025651/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934185] Re: Ubuntu Dock popup menu in top left corner of the screen and won't go away
** Changed in: dash-to-dock Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1934185 Title: Ubuntu Dock popup menu in top left corner of the screen and won't go away Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Every so often, typically when I'm using Thunderbird, I attempt to use the dock context menu to create a new window or something like that, and the "New Window" popup comes up, but does not work. Attempts to click on it have no effect. I cannot make the popup go away, other than by logging out and logging back in again (or rebooting). I did not observe this problem until I installed Ubuntu 21.04, so I expect it's a glitch that is new to this release. See attached screenshot for an example of the popup that won't go away. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gdm3 3.38.2.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jun 30 10:57:22 2021 InstallationDate: Installed on 2018-08-03 (1062 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to hirsute on 2021-06-03 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1934185/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966167] Re: Ubuntu Dock icons not clickable at the edge of the screen
I see this bug also affects gnome-shell-extension-ubuntu-dock, but in jammy-proposed I only see yaru-theme. Is the gnome-shell-extension- ubuntu-dock package needed for this to go forward? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1966167 Title: Ubuntu Dock icons not clickable at the edge of the screen Status in Dash to dock: New Status in Yaru Theme: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Committed Status in yaru-theme source package in Jammy: Fix Committed Bug description: [ Impact ] If you go to the bottom left corner of the dock and click, the All Apps button doesn't get triggered or highlighted. Check attached video for details. [ Test case ] For verifying yaru-theme, in the Ubuntu session: 1. Move the pointer to the edge of the screen where the AppIcons button is visible (bottom-left corner by default) 2. The button should be highlighted and clicking it should open the applications grid [ Regression potential ] - The dock margins are wrong or icons are not clickable in their edges - There's no not-reactive space between the activity button and the first icon --- Ubuntu 21.10. Live mode. 1920x1080 screen. To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1966167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023923] Re: Update gnome-desktop to 42.9
This bug was fixed in the package gnome-desktop - 42.9-0ubuntu1 --- gnome-desktop (42.9-0ubuntu1) jammy; urgency=medium * New upstream release (LP: #2023923) * Cherry-pick German translation update from 42.10 -- Jeremy Bícha Wed, 14 Jun 2023 16:42:33 -0400 ** Changed in: gnome-desktop (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2023923 Title: Update gnome-desktop to 42.9 Status in gnome-desktop package in Ubuntu: Fix Released Status in gnome-desktop source package in Jammy: Fix Released Bug description: Impact -- The only thing this update does is update the GNOME version number shown in the GNOME Settings > About dialog from 42.5 to 42.9 That's desired because we will include GNOME Shell 42.9 and people assume the version shown here is the version of GNOME Shell. There is a gnome-desktop 42.10 because the final official release of GNOME 42 was 42.10 but GNOME Shell skipped a release earlier so the versions aren't in sync. This update also cherry-picks one change from 42.10 to update the German translation. Because we use Ubuntu language packs, the new translation won't actually be used until the next language pack update, which is expected shortly before the Ubuntu 22.04.3 LTS release. Test Case - Install the updated packages Open the Settings app. Scroll down in the left sidebar and click About The GNOME Version should be 42.9 What Could Go Wrong --- Because this is part of core GNOME, it falls under the microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- GNOME 43 used GNOME Shell to display the version number so this kind of SRU is no longer needed after Ubuntu 22.04 LTS. GNOME 45 will simplify the version string to no longer report the minor version number (42 instead of 42.9) because GNOME Shell frequently is not released on exactly the same schedule as the overall GNOME project. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/2023923/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991022] Re: [SRU] Service activation via Systemd socket
This bug was fixed in the package speech-dispatcher - 0.11.1-1ubuntu3 --- speech-dispatcher (0.11.1-1ubuntu3) jammy; urgency=medium * patches/systemd-socket-activation: Added. - Enables activating Speech Dispatcher via a Systemd socket, it's needed for confined clients to be able to activate the service (LP: #1991022). [ Sebastien Bacher] * debian/control: - Build-Depends on libsystemd-dev * debian/speech-dispatcher.install: - install the new systemd units -- Nathan Pratta Teodosio Tue, 23 May 2023 09:29:24 +0200 ** Changed in: speech-dispatcher (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1991022 Title: [SRU] Service activation via Systemd socket Status in speech-dispatcher package in Ubuntu: Fix Released Status in speech-dispatcher source package in Jammy: Fix Released Status in speech-dispatcher source package in Kinetic: Fix Released Status in speech-dispatcher source package in Lunar: Fix Released Bug description: [Description] Systemd socket activation for Speech Dispatcher. - Creates the speech-dispatcher.socket; - Modifies the server so that it can detect it was automatically launched by that socket activation; and - Modifies the Autotools files accordingly. [Impact] Its relevance is described in [1], of which I quote the essential parts [my notes in brackets]: > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle it inside of the sandbox, so that each application has its own "private" instance of Speech Dispatcher running. This works more or less, but it has the downside that speech dispatcher cannot coordinate simultaneous messages from multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same time, the text reading overlaps. > > In order to solve this issue, I would really like to give sandboxed apps access to the Speech Dispatcher instance of the host. That can be done by implementing the action of the speech dispatcher service via a Systemd socket: > The only issue I see is having it auto launch. I think it would probably be a good step forward for speech-dispatcher to be auto launched by a systemd socket like other daemons already do on demand. That way the host speech-dispatcher with it's configuration would be used by all snaps, [Additional information] The changes are already merged upstream[21][22][23], but still not released. I have built and installed the package in Mantic and verified that running spd-say from inside a snap causes the host's dispatcher to spawn and emit sound — see 'Test case' for more details. This has also been verified in Jammy by Lissyx[31][32] and there is a merge proposal[4] for the Firefox snap that assumes the incorporation of this delta in speech-dispatcher. Note: Either the installed socket needs to be started manually to function correctly or the session must be restarted or the system needs to be rebooted. [Test case] Install the proposed speech-dispatcher and the snap[5] containing spd- say. Restart the user session so the new systemd unit gets activated. Then, snap run --shell geheim $ XDG_RUNTIME_DIR=/run/user/1000 spd-say hi should say "hi" through your loudspeakers. If you have no loudspeakers or if you are testing in a virtual machine, you can use Pavucontrol to verify that the dummy output device meter shows activity right after you issue the last command. [Regression potential] If the socket communication were not working (e.g. connection refused), then this would result in text-to-speech failing, even for a not sandboxed program. Do note, however, that if the socket were not available for whatever reason (e.g. the user didn't start it manually nor rebooted), then the sd_listen_fds(0) >= 1 test would be false and no regression would be observed, as then the program would fallback to its usual operation. [1] https://github.com/brailcom/speechd/issues/335 [21] https://github.com/brailcom/speechd/pull/763 [22] https://github.com/brailcom/speechd/pull/776 [23] https://github.com/brailcom/speechd/pull/817 [31] https://irclogs.ubuntu.com/2023/05/17/%23ubuntu-desktop.html [32] https://bugzilla.mozilla.org/show_bug.cgi?id=1729750#c23 [4] https://github.com/canonical/firefox-snap/pull/12 [5] https://launchpad.net/~nteodosio/+snap/test-speechd/+build/2103550 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1991022/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012978] Re: Memory leak
This bug was fixed in the package gjs - 1.72.4-0ubuntu0.22.04.1
---
gjs (1.72.4-0ubuntu0.22.04.1) jammy; urgency=medium
* New upstream stable release (LP: #2023572)
* debian/patches: Drop, they've been all applied upstream
gjs (1.72.3-0ubuntu0.22.04.1) jammy; urgency=medium
* New upstream release (LP: #2023572):
* debian/patches: Refresh teardown patch, replacing it with the one landed
upstream (LP: #1974293)
* debian/patches: Cherry-pick upstream fixes to address various memory leaks
(LP: #2012978)
-- Marco Trevisan (Treviño) Thu, 15 Jun 2023
17:23:40 +0200
** Changed in: gjs (Ubuntu Jammy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/2012978
Title:
Memory leak
Status in gjs package in Ubuntu:
Fix Released
Status in gjs source package in Jammy:
Fix Released
Status in gjs source package in Kinetic:
Won't Fix
Bug description:
[ Impact ]
High Memory Usage 3.1gb in 2h after reboot
[ Test case ]
Run:
env G_SLICE=always-malloc valgrind --leak-check=full \
--suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
gjs -c "const GLib=imports.gi['GLib'];function leak(){const
l=GLib.Variant['new']('i',1)};leak();imports.system.gc();"
No leak should be detected
Running more installed tests under valgrind should output no leaks
(unless those caused by gobject-introspection):
sudo apt install gjs-tests
env GJS_DEBUG_TOPICS= valgrind --leak-check=full \
--suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
/usr/libexec/installed-tests/gjs/minijasmine \
/usr/libexec/installed-tests/gjs/js/testGIMarshalling.js
There may be only two leaks caused by
gi_marshalling_tests_garray_boxed_struct_full_return and a gbytes one
after a ObjectInstance::prop_setter_impl call (these are leaks in the
test library that are expected with gobject-introspection 42, but
fixed in later versions).
env GJS_DEBUG_TOPICS= valgrind --leak-check=full \
--suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
/usr/libexec/installed-tests/gjs/minijasmine \
/usr/libexec/installed-tests/gjs/js/testRegress.js
No leak expected
[ Regression potential ]
Gjs applications (including gnome Shell) using GVariant may misbehave
---
ProblemType: BugDistroRelease: Ubuntu 22.04
Package: gnome-shell 42.5-0ubuntu1
Uname: Linux 6.2.8-060208-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 27 22:46:07 2023
DisplayManager: gdm3
InstallationDate: Installed on 2022-03-25 (366 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
RelatedPackageVersions: mutter-common 42.5-0ubuntu1SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-09-03 (205 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023548] Re: Update libadwaita to 1.1.7
This bug was fixed in the package libadwaita-1 - 1.1.7-0ubuntu0.22.04.1 --- libadwaita-1 (1.1.7-0ubuntu0.22.04.1) jammy; urgency=medium * New upstream release (LP: #2023548) -- Marco Trevisan (Treviño) Mon, 12 Jun 2023 15:07:03 +0200 ** Changed in: libadwaita-1 (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libadwaita-1 in Ubuntu. https://bugs.launchpad.net/bugs/2023548 Title: Update libadwaita to 1.1.7 Status in libadwaita-1 package in Ubuntu: Fix Released Status in libadwaita-1 source package in Jammy: Fix Released Bug description: Impact -- 1. There is a new release in the stable 1.1 series. https://gitlab.gnome.org/GNOME/libadwaita/-/blob/1.1.7/NEWS Test Case 1 --- After installing the update, install gnome-text-editor or gnome-shell-extension-manager or file and run them. Ensure that the apps run and that the on/off switches, checkboxes, and other visual elements still display correctly. In gnome-control-center click Appearance in the sidebar. Verify that switching the style between Light and Dark works correctly. Also choose a different accent color and verify that elements like folder icons in Nautilus and on/off switches have correctly adopted the accent color you chose. Test Case 2 --- Run adwaita-1-demo run the style classes demo check that all elements are properly visible and check that link color has enough contrast with background. What Could Go Wrong --- libadwaita is an addon library to GTK4 to allow apps to easily use more of the GNOME style and allow for widgets to be added and improved faster than in the normal GTK development cycle. libadwaita is included in all Ubuntu desktop flavors except for Kubuntu & Lubuntu. Few default Ubuntu desktop in 22.04 use libadwaita, but they do all the snaps using desktop portals file UI elements or GNOME Shell extensions settings. As a component of GNOME core, there is a micro-release exception for libadwaita. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libadwaita-1/+bug/2023548/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023572] Re: SRU gjs 1.72.4 to jammy
This bug was fixed in the package gjs - 1.72.4-0ubuntu0.22.04.1 --- gjs (1.72.4-0ubuntu0.22.04.1) jammy; urgency=medium * New upstream stable release (LP: #2023572) * debian/patches: Drop, they've been all applied upstream gjs (1.72.3-0ubuntu0.22.04.1) jammy; urgency=medium * New upstream release (LP: #2023572): * debian/patches: Refresh teardown patch, replacing it with the one landed upstream (LP: #1974293) * debian/patches: Cherry-pick upstream fixes to address various memory leaks (LP: #2012978) -- Marco Trevisan (Treviño) Thu, 15 Jun 2023 17:23:40 +0200 ** Changed in: gjs (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2023572 Title: SRU gjs 1.72.4 to jammy Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Released Bug description: [ Impact ] That's the GNOME 42 stable update, including some fixes: https://gitlab.gnome.org/GNOME/gjs/-/commits/1.72.4 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME The test plan that will be used is documented at https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs [ Regression potential ] Gjs is fundamental part of the ubuntu desktop, so any failure of it may cause the desktop not even to boot (because it's being used by gdm too). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023572/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2012978] Update Released
The verification of the Stable Release Update for gjs has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/2012978
Title:
Memory leak
Status in gjs package in Ubuntu:
Fix Released
Status in gjs source package in Jammy:
Fix Released
Status in gjs source package in Kinetic:
Won't Fix
Bug description:
[ Impact ]
High Memory Usage 3.1gb in 2h after reboot
[ Test case ]
Run:
env G_SLICE=always-malloc valgrind --leak-check=full \
--suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
gjs -c "const GLib=imports.gi['GLib'];function leak(){const
l=GLib.Variant['new']('i',1)};leak();imports.system.gc();"
No leak should be detected
Running more installed tests under valgrind should output no leaks
(unless those caused by gobject-introspection):
sudo apt install gjs-tests
env GJS_DEBUG_TOPICS= valgrind --leak-check=full \
--suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
/usr/libexec/installed-tests/gjs/minijasmine \
/usr/libexec/installed-tests/gjs/js/testGIMarshalling.js
There may be only two leaks caused by
gi_marshalling_tests_garray_boxed_struct_full_return and a gbytes one
after a ObjectInstance::prop_setter_impl call (these are leaks in the
test library that are expected with gobject-introspection 42, but
fixed in later versions).
env GJS_DEBUG_TOPICS= valgrind --leak-check=full \
--suppressions=/usr/share/glib-2.0/valgrind/glib.supp \
/usr/libexec/installed-tests/gjs/minijasmine \
/usr/libexec/installed-tests/gjs/js/testRegress.js
No leak expected
[ Regression potential ]
Gjs applications (including gnome Shell) using GVariant may misbehave
---
ProblemType: BugDistroRelease: Ubuntu 22.04
Package: gnome-shell 42.5-0ubuntu1
Uname: Linux 6.2.8-060208-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 27 22:46:07 2023
DisplayManager: gdm3
InstallationDate: Installed on 2022-03-25 (366 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
RelatedPackageVersions: mutter-common 42.5-0ubuntu1SourcePackage: gnome-shell
UpgradeStatus: Upgraded to jammy on 2022-09-03 (205 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2012978/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023572] Update Released
The verification of the Stable Release Update for gjs has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2023572 Title: SRU gjs 1.72.4 to jammy Status in gjs package in Ubuntu: Fix Released Status in gjs source package in Jammy: Fix Released Bug description: [ Impact ] That's the GNOME 42 stable update, including some fixes: https://gitlab.gnome.org/GNOME/gjs/-/commits/1.72.4 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME The test plan that will be used is documented at https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs [ Regression potential ] Gjs is fundamental part of the ubuntu desktop, so any failure of it may cause the desktop not even to boot (because it's being used by gdm too). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023572/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2025538] Re: Unrequested kernel update
** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Status: Triaged => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu) Status: Confirmed => Triaged ** Changed in: ubuntu-drivers-common (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-drivers-common (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2025538 Title: Unrequested kernel update Status in linux-restricted-modules package in Ubuntu: Triaged Status in linux-signed-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: In Progress Status in ubuntu-drivers-common package in Ubuntu: Triaged Bug description: Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was informed that new packages are available and I just hit update. This caused my system running 5.15.0-76-generic to be switched to 5.19.0-1010-nvidia-lowlatency. I noted this as I was now running into bugs like https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2017980 The update was, as stated in history.log: Start-Date: 2023-07-01 00:25:40 Commandline: packagekit role='update-packages' Requested-By: cm (1000) Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, automatic) Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2) => This simple update was changing my kernel from 5.15 to 5.19 without a request from my side ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10 ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17 Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 1 21:16:09 2023 InstallationDate: Installed on 2018-10-10 (1724 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-signed-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2025538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991022] Re: [SRU] Service activation via Systemd socket
This bug was fixed in the package speech-dispatcher - 0.11.3-1ubuntu1.1 --- speech-dispatcher (0.11.3-1ubuntu1.1) kinetic; urgency=medium * patches/systemd-socket-activation: Added. - Enables activating Speech Dispatcher via a Systemd socket, it's needed for confined clients to be able to activate the service (LP: #1991022). [ Sebastien Bacher] * debian/control: - Build-Depends on libsystemd-dev * debian/speech-dispatcher.install: - install the new systemd units -- Nathan Pratta Teodosio Tue, 23 May 2023 08:59:41 +0200 ** Changed in: speech-dispatcher (Ubuntu Kinetic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1991022 Title: [SRU] Service activation via Systemd socket Status in speech-dispatcher package in Ubuntu: Fix Released Status in speech-dispatcher source package in Jammy: Fix Committed Status in speech-dispatcher source package in Kinetic: Fix Released Status in speech-dispatcher source package in Lunar: Fix Released Bug description: [Description] Systemd socket activation for Speech Dispatcher. - Creates the speech-dispatcher.socket; - Modifies the server so that it can detect it was automatically launched by that socket activation; and - Modifies the Autotools files accordingly. [Impact] Its relevance is described in [1], of which I quote the essential parts [my notes in brackets]: > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle it inside of the sandbox, so that each application has its own "private" instance of Speech Dispatcher running. This works more or less, but it has the downside that speech dispatcher cannot coordinate simultaneous messages from multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same time, the text reading overlaps. > > In order to solve this issue, I would really like to give sandboxed apps access to the Speech Dispatcher instance of the host. That can be done by implementing the action of the speech dispatcher service via a Systemd socket: > The only issue I see is having it auto launch. I think it would probably be a good step forward for speech-dispatcher to be auto launched by a systemd socket like other daemons already do on demand. That way the host speech-dispatcher with it's configuration would be used by all snaps, [Additional information] The changes are already merged upstream[21][22][23], but still not released. I have built and installed the package in Mantic and verified that running spd-say from inside a snap causes the host's dispatcher to spawn and emit sound — see 'Test case' for more details. This has also been verified in Jammy by Lissyx[31][32] and there is a merge proposal[4] for the Firefox snap that assumes the incorporation of this delta in speech-dispatcher. Note: Either the installed socket needs to be started manually to function correctly or the session must be restarted or the system needs to be rebooted. [Test case] Install the proposed speech-dispatcher and the snap[5] containing spd- say. Restart the user session so the new systemd unit gets activated. Then, snap run --shell geheim $ XDG_RUNTIME_DIR=/run/user/1000 spd-say hi should say "hi" through your loudspeakers. If you have no loudspeakers or if you are testing in a virtual machine, you can use Pavucontrol to verify that the dummy output device meter shows activity right after you issue the last command. [Regression potential] If the socket communication were not working (e.g. connection refused), then this would result in text-to-speech failing, even for a not sandboxed program. Do note, however, that if the socket were not available for whatever reason (e.g. the user didn't start it manually nor rebooted), then the sd_listen_fds(0) >= 1 test would be false and no regression would be observed, as then the program would fallback to its usual operation. [1] https://github.com/brailcom/speechd/issues/335 [21] https://github.com/brailcom/speechd/pull/763 [22] https://github.com/brailcom/speechd/pull/776 [23] https://github.com/brailcom/speechd/pull/817 [31] https://irclogs.ubuntu.com/2023/05/17/%23ubuntu-desktop.html [32] https://bugzilla.mozilla.org/show_bug.cgi?id=1729750#c23 [4] https://github.com/canonical/firefox-snap/pull/12 [5] https://launchpad.net/~nteodosio/+snap/test-speechd/+build/2103550 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1991022/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026719] Re: Low Volume 22.04 Realtek ALC285 HP Pavilion 15-ec2xxx
The laptop comes with a Ryzen 5600H processor and Nvidia GeForce GTX 1650 graphics card. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2026719 Title: Low Volume 22.04 Realtek ALC285 HP Pavilion 15-ec2xxx Status in alsa-driver package in Ubuntu: New Bug description: I have dual boot Windows 10, volume is high even at 50%. The same YouTube video, VLC player, Rhythmbox have poor audio volume even at 100%. Relying on Bluetooth speakers for some media. I tried various GUI tools, alsa-mixer. The volume is 100%. Looks like something to do with the driver level or ALSA. When I used alsamixer in the Terminal, I got this ( screenshot attached ) The issue is the same with internal speakers mainly. But my Bluetooth speakers also give more sound on Windows 10. Description: Ubuntu 22.04.2 LTS Release: 22.04 Please let me know if you need any other info. My laptop is a 2 year old HP Pavilion 15-ec2xxx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2026719/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2021948] Update Released
The verification of the Stable Release Update for mesa has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2021948 Title: New bugfix release 23.0.4 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Committed Status in mesa source package in Lunar: Fix Released Bug description: [Impact] This is the last point-release of the 23.0.x-series, we should put it in lunar so latest bugfixes would get there, and in jammy for 22.04.3 image. We'll include an additional bugfix (a revert) to fix GPU hangs on some AMD gpu's running certain games. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2021948/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2021948] Re: New bugfix release 23.0.4
This bug was fixed in the package mesa - 23.0.4-0ubuntu1~23.04.1 --- mesa (23.0.4-0ubuntu1~23.04.1) lunar; urgency=medium * New upstream release. (LP: #2021948) - add a revert for amdgpu which missed 23.0.x branch -- Timo Aaltonen Fri, 09 Jun 2023 12:53:37 +0300 ** Changed in: mesa (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2021948 Title: New bugfix release 23.0.4 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Committed Status in mesa source package in Lunar: Fix Released Bug description: [Impact] This is the last point-release of the 23.0.x-series, we should put it in lunar so latest bugfixes would get there, and in jammy for 22.04.3 image. We'll include an additional bugfix (a revert) to fix GPU hangs on some AMD gpu's running certain games. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2021948/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2025538] Re: Unrequested kernel update
** Also affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided => High ** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2025538 Title: Unrequested kernel update Status in linux-restricted-modules package in Ubuntu: Triaged Status in linux-signed-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Triaged Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was informed that new packages are available and I just hit update. This caused my system running 5.15.0-76-generic to be switched to 5.19.0-1010-nvidia-lowlatency. I noted this as I was now running into bugs like https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2017980 The update was, as stated in history.log: Start-Date: 2023-07-01 00:25:40 Commandline: packagekit role='update-packages' Requested-By: cm (1000) Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, automatic) Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2) => This simple update was changing my kernel from 5.15 to 5.19 without a request from my side ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10 ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17 Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 1 21:16:09 2023 InstallationDate: Installed on 2018-10-10 (1724 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-signed-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2025538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991022] Update Released
The verification of the Stable Release Update for speech-dispatcher has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1991022 Title: [SRU] Service activation via Systemd socket Status in speech-dispatcher package in Ubuntu: Fix Released Status in speech-dispatcher source package in Jammy: Fix Committed Status in speech-dispatcher source package in Kinetic: Fix Committed Status in speech-dispatcher source package in Lunar: Fix Released Bug description: [Description] Systemd socket activation for Speech Dispatcher. - Creates the speech-dispatcher.socket; - Modifies the server so that it can detect it was automatically launched by that socket activation; and - Modifies the Autotools files accordingly. [Impact] Its relevance is described in [1], of which I quote the essential parts [my notes in brackets]: > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle it inside of the sandbox, so that each application has its own "private" instance of Speech Dispatcher running. This works more or less, but it has the downside that speech dispatcher cannot coordinate simultaneous messages from multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same time, the text reading overlaps. > > In order to solve this issue, I would really like to give sandboxed apps access to the Speech Dispatcher instance of the host. That can be done by implementing the action of the speech dispatcher service via a Systemd socket: > The only issue I see is having it auto launch. I think it would probably be a good step forward for speech-dispatcher to be auto launched by a systemd socket like other daemons already do on demand. That way the host speech-dispatcher with it's configuration would be used by all snaps, [Additional information] The changes are already merged upstream[21][22][23], but still not released. I have built and installed the package in Mantic and verified that running spd-say from inside a snap causes the host's dispatcher to spawn and emit sound — see 'Test case' for more details. This has also been verified in Jammy by Lissyx[31][32] and there is a merge proposal[4] for the Firefox snap that assumes the incorporation of this delta in speech-dispatcher. Note: Either the installed socket needs to be started manually to function correctly or the session must be restarted or the system needs to be rebooted. [Test case] Install the proposed speech-dispatcher and the snap[5] containing spd- say. Restart the user session so the new systemd unit gets activated. Then, snap run --shell geheim $ XDG_RUNTIME_DIR=/run/user/1000 spd-say hi should say "hi" through your loudspeakers. If you have no loudspeakers or if you are testing in a virtual machine, you can use Pavucontrol to verify that the dummy output device meter shows activity right after you issue the last command. [Regression potential] If the socket communication were not working (e.g. connection refused), then this would result in text-to-speech failing, even for a not sandboxed program. Do note, however, that if the socket were not available for whatever reason (e.g. the user didn't start it manually nor rebooted), then the sd_listen_fds(0) >= 1 test would be false and no regression would be observed, as then the program would fallback to its usual operation. [1] https://github.com/brailcom/speechd/issues/335 [21] https://github.com/brailcom/speechd/pull/763 [22] https://github.com/brailcom/speechd/pull/776 [23] https://github.com/brailcom/speechd/pull/817 [31] https://irclogs.ubuntu.com/2023/05/17/%23ubuntu-desktop.html [32] https://bugzilla.mozilla.org/show_bug.cgi?id=1729750#c23 [4] https://github.com/canonical/firefox-snap/pull/12 [5] https://launchpad.net/~nteodosio/+snap/test-speechd/+build/2103550 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1991022/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1991022] Re: [SRU] Service activation via Systemd socket
This bug was fixed in the package speech-dispatcher - 0.11.4-2ubuntu0.1 --- speech-dispatcher (0.11.4-2ubuntu0.1) lunar; urgency=medium * patches/systemd-socket-activation: Added. - Enables activating Speech Dispatcher via a Systemd socket, it's needed for confined clients to be able to activate the service (LP: #1991022). [ Sebastien Bacher] * debian/control: - Build-Depends on libsystemd-dev * debian/speech-dispatcher.install: - install the new systemd units -- Nathan Pratta Teodosio Wed, 10 May 2023 08:40:27 +0200 ** Changed in: speech-dispatcher (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1991022 Title: [SRU] Service activation via Systemd socket Status in speech-dispatcher package in Ubuntu: Fix Released Status in speech-dispatcher source package in Jammy: Fix Committed Status in speech-dispatcher source package in Kinetic: Fix Committed Status in speech-dispatcher source package in Lunar: Fix Released Bug description: [Description] Systemd socket activation for Speech Dispatcher. - Creates the speech-dispatcher.socket; - Modifies the server so that it can detect it was automatically launched by that socket activation; and - Modifies the Autotools files accordingly. [Impact] Its relevance is described in [1], of which I quote the essential parts [my notes in brackets]: > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle it inside of the sandbox, so that each application has its own "private" instance of Speech Dispatcher running. This works more or less, but it has the downside that speech dispatcher cannot coordinate simultaneous messages from multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same time, the text reading overlaps. > > In order to solve this issue, I would really like to give sandboxed apps access to the Speech Dispatcher instance of the host. That can be done by implementing the action of the speech dispatcher service via a Systemd socket: > The only issue I see is having it auto launch. I think it would probably be a good step forward for speech-dispatcher to be auto launched by a systemd socket like other daemons already do on demand. That way the host speech-dispatcher with it's configuration would be used by all snaps, [Additional information] The changes are already merged upstream[21][22][23], but still not released. I have built and installed the package in Mantic and verified that running spd-say from inside a snap causes the host's dispatcher to spawn and emit sound — see 'Test case' for more details. This has also been verified in Jammy by Lissyx[31][32] and there is a merge proposal[4] for the Firefox snap that assumes the incorporation of this delta in speech-dispatcher. Note: Either the installed socket needs to be started manually to function correctly or the session must be restarted or the system needs to be rebooted. [Test case] Install the proposed speech-dispatcher and the snap[5] containing spd- say. Restart the user session so the new systemd unit gets activated. Then, snap run --shell geheim $ XDG_RUNTIME_DIR=/run/user/1000 spd-say hi should say "hi" through your loudspeakers. If you have no loudspeakers or if you are testing in a virtual machine, you can use Pavucontrol to verify that the dummy output device meter shows activity right after you issue the last command. [Regression potential] If the socket communication were not working (e.g. connection refused), then this would result in text-to-speech failing, even for a not sandboxed program. Do note, however, that if the socket were not available for whatever reason (e.g. the user didn't start it manually nor rebooted), then the sd_listen_fds(0) >= 1 test would be false and no regression would be observed, as then the program would fallback to its usual operation. [1] https://github.com/brailcom/speechd/issues/335 [21] https://github.com/brailcom/speechd/pull/763 [22] https://github.com/brailcom/speechd/pull/776 [23] https://github.com/brailcom/speechd/pull/817 [31] https://irclogs.ubuntu.com/2023/05/17/%23ubuntu-desktop.html [32] https://bugzilla.mozilla.org/show_bug.cgi?id=1729750#c23 [4] https://github.com/canonical/firefox-snap/pull/12 [5] https://launchpad.net/~nteodosio/+snap/test-speechd/+build/2103550 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1991022/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026719] [NEW] Low Volume 22.04 Realtek ALC285 HP Pavilion 15-ec2xxx
Public bug reported: I have dual boot Windows 10, volume is high even at 50%. The same YouTube video, VLC player, Rhythmbox have poor audio volume even at 100%. Relying on Bluetooth speakers for some media. I tried various GUI tools, alsa-mixer. The volume is 100%. Looks like something to do with the driver level or ALSA. When I used alsamixer in the Terminal, I got this ( screenshot attached ) The issue is the same with internal speakers mainly. But my Bluetooth speakers also give more sound on Windows 10. Description:Ubuntu 22.04.2 LTS Release:22.04 Please let me know if you need any other info. My laptop is a 2 year old HP Pavilion 15-ec2xxx ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: alc285 realtek ** Attachment added: "alsamixer output" https://bugs.launchpad.net/bugs/2026719/+attachment/5685137/+files/Screenshot%20from%202023-07-10%2016-07-48.png ** Summary changed: - Low Volume 22.04 Relatek ALC285 HP Pavilion 15-ec2xxx + Low Volume 22.04 Realtek ALC285 HP Pavilion 15-ec2xxx -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2026719 Title: Low Volume 22.04 Realtek ALC285 HP Pavilion 15-ec2xxx Status in alsa-driver package in Ubuntu: New Bug description: I have dual boot Windows 10, volume is high even at 50%. The same YouTube video, VLC player, Rhythmbox have poor audio volume even at 100%. Relying on Bluetooth speakers for some media. I tried various GUI tools, alsa-mixer. The volume is 100%. Looks like something to do with the driver level or ALSA. When I used alsamixer in the Terminal, I got this ( screenshot attached ) The issue is the same with internal speakers mainly. But my Bluetooth speakers also give more sound on Windows 10. Description: Ubuntu 22.04.2 LTS Release: 22.04 Please let me know if you need any other info. My laptop is a 2 year old HP Pavilion 15-ec2xxx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2026719/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2025538] Re: Unrequested kernel update
First of all, sorry for the inconvenience. The problem was caused by some missing dependencies which were not yet available in the archive. We are going to look into ways to make the update process more robust. Thank you for reporting the problem. ** Also affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-restricted-modules (Ubuntu) Status: New => Triaged ** Changed in: linux-restricted-modules (Ubuntu) Importance: Undecided => High ** Changed in: linux-restricted-modules (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2025538 Title: Unrequested kernel update Status in linux-restricted-modules package in Ubuntu: Triaged Status in linux-signed-nvidia-5.19 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was informed that new packages are available and I just hit update. This caused my system running 5.15.0-76-generic to be switched to 5.19.0-1010-nvidia-lowlatency. I noted this as I was now running into bugs like https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2017980 The update was, as stated in history.log: Start-Date: 2023-07-01 00:25:40 Commandline: packagekit role='update-packages' Requested-By: cm (1000) Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, automatic) Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2) => This simple update was changing my kernel from 5.15 to 5.19 without a request from my side ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10 ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17 Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 1 21:16:09 2023 InstallationDate: Installed on 2018-10-10 (1724 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-signed-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2025538/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987159] Re: Drop VNC support from GNOME Remote Desktop in Kinetic
> I am struggling to find any use cases where GNOME's VNC should be preferred to RDP. 1) Teacher screen broadcasting to students. There, a shared VNC session is much easier to setup and performs better than separate RDP sessions. Additionally, encrypting e.g. 10 RDP streams comes with significant CPU strain, which is unnecessary in this use case. 2) The remote support use case. To help a remote user behind NAT, I only need to ask them to run `x11vnc -connect my-ip`. On my side, `vncviewer -listen` accepts the request for help. GNOME VNC could easily support that. But there's no `xfreerdp -listen` option in the RDP protocol. So in the RDP solution, the very frequent and significant "remote support" use case is completely ignored and we need to switch to teamviewer or anydesk instead. It's understandable though that if upstream GNOME neglects VNC, downstream Ubuntu will also do the same. And such decisions are why there's a growing list of users that can't use GNOME at all anymore... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1987159 Title: Drop VNC support from GNOME Remote Desktop in Kinetic Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-remote-desktop package in Ubuntu: Fix Released Bug description: RDP has significantly improved privacy and performance compared to VNC. I am struggling to find any use cases where GNOME's VNC should be preferred to RDP. GNOME is so far unwilling to provide full VNC options in the GNOME Settings app. The VNC feature was labeled as Legacy in Ubuntu 22.04 LTS. There is value in only providing a single remote desktop method by default that works well. gnome-remote-desktop 43 by default only builds the RDP provider and so far I haven't seen complaints about that. Therefore, I think we should drop the VNC feature for Ubuntu 22.10. Otherwise, we need to: 1. enable VNC in gnome-remote-desktop 43 2. Update the VNC patch in gnome-control-center 43 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1987159/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2016990] Re: Irregular frame rate in some fullscreen games
** Changed in: mutter (Ubuntu Lunar) Status: In Progress => Fix Committed ** Changed in: mutter (Ubuntu Lunar) Assignee: (unassigned) => Jeremy Bícha (jbicha) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2016990 Title: Irregular frame rate in some fullscreen games Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Won't Fix Status in mutter source package in Lunar: Fix Committed Status in mutter source package in Mantic: Fix Released Bug description: [ Impact ] I'm having a strange issue with the game Path of Exile (free). With Ubuntu Wayland session, vsync on, I get very irregular frame rates, it jumps around 40 fps. If I switch to Plasma Wayland the game is very smooth 60 fps. I'm running the game from Steam with Proton. I've tried Proton Experimental and Proton 8.0 so far, no difference. The game uses Vulkan so I guess it's being allowed to set up all the swap and presentation stuff pretty much itself... ? MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING=1 doesn't help Mutter so it's not strictly related to triple buffering, which makes sense since it's a full screen game anyway. [ Test Plan ] None known, other than the OP to run the game. [ Where problems could occur ] In rendering performance of fullscreen apps/games. [ Workaround ] Add this to /etc/environment: CLUTTER_PAINT=disable-dynamic-max-render-time [ Other Info ] Kernel: 6.2.0-1003-lowlatency GPU: Radeon 6800 XT CPU: Ryzen 9 5900X To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2016990/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2023766] Re: Mouse cursor stutters over GUI elements that are animated
** Changed in: mutter (Ubuntu Lunar) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2023766 Title: Mouse cursor stutters over GUI elements that are animated Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: In Progress Status in mutter source package in Lunar: Fix Committed Status in mutter source package in Mantic: Fix Released Bug description: [ Impact ] Mouse cursor stutters over GUI elements that are animated, such as GTK apps, web pages and shell elements. [ Test Plan ] 1. Open Settings. 2. Move the cursor up/down over an empty area of the desktop. 3. Move the cursor up/down over the list pane on the left side of the Settings window. Expect: No difference in cursor smoothness whether the window below is animating in response to movement or not. [ Where problems could occur ] In frame scheduling, so the risk is more stuttering or screen freezes. [ Workaround ] Add this to /etc/environment: CLUTTER_PAINT=disable-dynamic-max-render-time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023766/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026255] Re: New windows have weird behavior on the desktop
** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Status: Incomplete => New ** Summary changed: - New windows have weird behavior on the desktop + New windows have confused sizing when monitors are set to different scaling factors ** Tags added: multimonitor -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2026255 Title: New windows have confused sizing when monitors are set to different scaling factors Status in mutter package in Ubuntu: New Bug description: I have 3 monitors, two QHD monitors and the screen of the laptop attached. I'm using Gnome-shell with the extensions disabled. If a window starts maximized it only takes a portion of the screen, if a window starts unmaximized it automatically doubles the size when it loses the focus. I have attached a small video of the behavior of the middle QHD monitor. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.2-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 6 09:35:26 2023 DisplayManager: gdm3 InstallationDate: Installed on 2021-06-21 (744 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 44.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-12 (55 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2026255/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2020049] Re: gnome-shell crashed with SIGSEGV in clutter_stage_view_get_onscreen() from meta_stage_impl_add_onscreen_frame_info() from add_onscreen_frame_info() from post_finis
It's in proposed: https://launchpad.net/ubuntu/+source/mutter/44.3-0ubuntu1 ** Changed in: mutter (Ubuntu Lunar) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2020049 Title: gnome-shell crashed with SIGSEGV in clutter_stage_view_get_onscreen() from meta_stage_impl_add_onscreen_frame_info() from add_onscreen_frame_info() from post_finish_frame() from try_post_latest_swap() Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Status in mutter source package in Mantic: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/c675f1d61cef940571272d7e655162f1b1cddab1 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026255] Re: New windows have weird behavior on the desktop
> Does the problem go away if you set both monitors to the same scale? Indeed, if I set the 3 screens at the same scale (ie 200%) the problem goes away. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2026255 Title: New windows have weird behavior on the desktop Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have 3 monitors, two QHD monitors and the screen of the laptop attached. I'm using Gnome-shell with the extensions disabled. If a window starts maximized it only takes a portion of the screen, if a window starts unmaximized it automatically doubles the size when it loses the focus. I have attached a small video of the behavior of the middle QHD monitor. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.2-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 6 09:35:26 2023 DisplayManager: gdm3 InstallationDate: Installed on 2021-06-21 (744 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 44.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-05-12 (55 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026255/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026630] Re: gnome-shell brings down all running applications when crashing on wayland
** Changed in: gnome-shell Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2026630 Title: gnome-shell brings down all running applications when crashing on wayland Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell package in Fedora: Unknown Bug description: If gnome-shell experiences a problem when running in a Wayland session, it will terminate all graphical applications running via that session. When running via Xorg, this will not occur, with the added feature that gnome-session may also be restarted manually via alt+f2 and 'r'. This creates a single point of failure within the entire desktop session, and I have personally experienced this and lost work on a clean install with no extra GNOME extensions. Addressing this would contribute greatly to Ubuntu's overall reliability and stability as a desktop OS. This issue has been raised elsewhere for Fedora at: https://bugzilla.redhat.com/show_bug.cgi?id=1367666 There is an upstream bug filed at: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5634 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2026630/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1934185] Re: Ubuntu Dock popup menu in top left corner of the screen and won't go away
** Bug watch added: github.com/micheleg/dash-to-dock/issues #2055 https://github.com/micheleg/dash-to-dock/issues/2055 ** Also affects: dash-to-dock via https://github.com/micheleg/dash-to-dock/issues/2055 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1934185 Title: Ubuntu Dock popup menu in top left corner of the screen and won't go away Status in Dash to dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Every so often, typically when I'm using Thunderbird, I attempt to use the dock context menu to create a new window or something like that, and the "New Window" popup comes up, but does not work. Attempts to click on it have no effect. I cannot make the popup go away, other than by logging out and logging back in again (or rebooting). I did not observe this problem until I installed Ubuntu 21.04, so I expect it's a glitch that is new to this release. See attached screenshot for an example of the popup that won't go away. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gdm3 3.38.2.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jun 30 10:57:22 2021 InstallationDate: Installed on 2018-08-03 (1062 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gdm3 UpgradeStatus: Upgraded to hirsute on 2021-06-03 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1934185/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026649] Re: Gnome shell hangs and no response while Google chrome restore last session and stop responding.
Thanks for the bug report. Your log seems to be full of the same recurring gnome-shell log message so please start by deleting all local unsupported extensions: cd ~/.local/share/gnome-shell/ rm -rf extensions and then log in again. If the problem keeps happening after that then please consider using less than "1000+ tabs" because likely they are using up all of your hardware resources. ** Package changed: gnome-shell (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2026649 Title: Gnome shell hangs and no response while Google chrome restore last session and stop responding. Status in Ubuntu: Incomplete Bug description: While Google Chrome tries to restore last session (with 1000+ tabs) and a lot of "not responding" windows popped up, gnome desktop stopped responding. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.5-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown Date: Sun Jul 9 23:00:18 2023 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-07 (1431 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) RelatedPackageVersions: mutter-common 42.9-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-08-15 (327 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2026649/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 2025916] Re: command-chain ... not found
That is currently a Snap shortcoming, there is no dependency enforcement like in Apt. So in general you'd really have to ask. :/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2025916 Title: command-chain ... not found Status in chromium-browser package in Ubuntu: Incomplete Bug description: (I'm not familiar with snap, was migrated to it by *buntu for chromium-browser) Received the usual, well-know notification of having to snap refresh, some time given ... Closed chromium and issue the usual 'sudo snap refresh'. It went through, without any error indication. Restarting chromium failed, on the command line with $ chromium-browser Content snap command-chain for /snap/chromium/2529/gnome-platform/command-chain/desktop-launch not found: ensure slot is connected Using Firefox, after some Google I found and tried $ sudo apt install snap --reinstall ... The following NEW packages will be installed: snap And, no, I did not uninstall it. This is my work laptop, and I do only the basic and necessary system administration on it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2025916/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026650] Re: X11 directory is duplicated under /bin
This is likely for compatibility. /usr/bin/ is the same (/bin is a symlink to it) so there might be old software expecting /usr/bin/X11/... ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2026650 Title: X11 directory is duplicated under /bin Status in xorg package in Ubuntu: Opinion Bug description: The directory "/bin/X11" appears to be duplicated multiple directory levels deep. For instance, I type "cd /bin/X11/X11/X11/X11/X11". Then type the pwd command and I am six directories deep in yet another X11 directory. /bin/X11/X11/X11/X11/X11 Since it doesn't appear to have an effect on disk space, I typed "ls -ld X11" and it shows it's a link to ".", the current directory. output of "ls -ld X11" is: lrwxrwxrwx 1 root root 1 Jan 29 02:30 X11 -> . Clearly some process is creating or did create these symbolic links to the current directory. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Sun Jul 9 11:27:06 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:224b] InstallationDate: Installed on 2023-01-29 (161 days ago) InstallationMedia: Xubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) LightdmDisplayLog: (EE) event18 - MX Keys Mini Keyboard: client bug: event processing lagging behind by 41ms, your system is too slow (EE) event18 - MX Keys Mini Keyboard: client bug: event processing lagging behind by 30ms, your system is too slow MachineType: LENOVO 20JTS0G900 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-76-generic root=UUID=f4ee708b-3dfb-4d35-9101-0194dfc66e58 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2019 dmi.bios.release: 1.33 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET54W (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 20JTS0G900 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrN1WET54W(1.33):bd04/17/2019:br1.33:efr1.20:svnLENOVO:pn20JTS0G900:pvrThinkPadT470sW10DG:rvnLENOVO:rn20JTS0G900:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20JT_BU_Think_FM_ThinkPadT470sW10DG: dmi.product.family: ThinkPad T470s W10DG dmi.product.name: 20JTS0G900 dmi.product.sku: LENOVO_MT_20JT_BU_Think_FM_ThinkPad T470s W10DG dmi.product.version: ThinkPad T470s W10DG dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.0.20230414.1+2061~u22.04 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2026650/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.
-- Michaelus > you're saying invoking chromium via a fully qualified, real-path, with a SNAP-created symbolic link to a actual build directory, is a "unsupported setup" ? Yes, running a snap via /snap/chromium/current/usr/lib/chromium- browser/chrome is unsupported. (I don't know how you conclude that is a "symbolic link to a build directory" though.) -- Marcus I'm glad you solved all the issues that this update gave rise to and shared your solution with chromedriver. For what it's worth, yes, were you to find a problem with it, you would file a bug for chromium-browser. Thank you too for your superb cooperation and responsiveness. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2026200 Title: Snap update broke launching and printing on 20.04 Ubuntu. Status in chromium-browser package in Ubuntu: Invalid Status in cups package in Ubuntu: Incomplete Bug description: Two deployed ubuntu images, 20.04 and 22.04. Both images are fully updated. Issue appears to only impact 20.04. chrome snap version 2529 Launching chrome from menu shortcut that is managed by the snap works and it using this location /snap/bin/chromium Launching chrome from desktop shortcut that I manage on 20.04 fails - /snap/chromium/current/usr/lib/chromium-browser/chrome Updating the desktop shortcut with this location on 20.04 works - /snap/bin/chromium Try and print from the browser, print dialog in chrome does not list any system printers, only shows PDF. Doing the same on 22.04 image, I get a list of printers. CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No such file or directory" I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 100% failure rate on 20.04. I get this error when running chrome from cli from this path on 20.04 /snap/chromium/current/usr/lib/chromium-browser which points to 2529 snap image. /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026630] Re: gnome-shell brings down all running applications when crashing on wayland
I don't expect GNOME to implement this any time soon. In the meantime it's worth noting most people either don't experience regular crashes, or will only experience one recurring crash that causes them the most grief. So please remember to report all crashes you experience by: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment So that we can fix them properly. ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Wishlist ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5634 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5634 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5634 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged ** Bug watch added: Red Hat Bugzilla #1367666 https://bugzilla.redhat.com/show_bug.cgi?id=1367666 ** Also affects: gnome-shell (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1367666 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2026630 Title: gnome-shell brings down all running applications when crashing on wayland Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell package in Fedora: Unknown Bug description: If gnome-shell experiences a problem when running in a Wayland session, it will terminate all graphical applications running via that session. When running via Xorg, this will not occur, with the added feature that gnome-session may also be restarted manually via alt+f2 and 'r'. This creates a single point of failure within the entire desktop session, and I have personally experienced this and lost work on a clean install with no extra GNOME extensions. Addressing this would contribute greatly to Ubuntu's overall reliability and stability as a desktop OS. This issue has been raised elsewhere for Fedora at: https://bugzilla.redhat.com/show_bug.cgi?id=1367666 There is an upstream bug filed at: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5634 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2026630/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
