[Desktop-packages] [Bug 1924689] Re: Window border corruption after changing display scale between 100% and 200% in Xorg
Dan - I tend to agree with you having seen this with my own eyes. -- 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/1924689 Title: Window border corruption after changing display scale between 100% and 200% in Xorg Status in Mutter: New Status in OEM Priority Project: New Status in mutter package in Ubuntu: Triaged Bug description: Ubuntu release: Ubuntu 20.04.2 LTS Issue description: When the gnome-initial-setup launched, if user changes the scale 200 -> 400 or 100 -> 200. There is some garbage on the edge of the window. The issue is not seen if we login in wayland session. A video is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1924689/+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 2028199] [NEW] GPU disconnect, then minutes later Xorg display lockup
Public bug reported: It appears that occassionally my external GPU 'falls off' the bus, it's listed as not primary, so should not be an issue. However, a few minutes (usually) after this occurs, the Xorg server or window manager completely locks up in strange ways. For example - the mouse can move across the multiple monitors, but no clicks are registered. similarly, no keyboard keypresses result in any change in the UI. However, applications happily run in the background - videoconference meetings using the audio mic and speakers continue to operate , and the machine stays online. This leads me to believe there is some problem with Xorg capturing the Human interface devices and passing these to the correct applications, and then updating the displays. I don't know how to trigger this behavior reliably, but I am getting closer to tracking down how it occurs. I hoped you might be able to shed some light as to why this might be happening and how to resolve it. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-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..52.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.2.0 (Ubuntu 12.2.0-17ubuntu1) ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 19 14:33:01 2023 DistUpgraded: 2023-04-26 15:38:23,675 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. TU117 [GeForce GTX 1650] [3842:1257] InstallationDate: Installed on 2023-01-09 (191 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to lunar on 2023-04-26 (84 days ago) dmi.bios.date: 06/12/2023 dmi.bios.release: 1.61 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET85W (1.61 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.34 dmi.modalias: dmi:bvnLENOVO:bvrN32ET85W(1.61):bd06/12/2023:br1.61:efr1.34:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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 lunar 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/2028199 Title: GPU disconnect, then minutes later Xorg display lockup Status in xorg package in Ubuntu: New Bug description: It appears that occassionally my external GPU 'falls off' the bus, it's listed as not primary, so should not be an issue. How
[Desktop-packages] [Bug 2026790] Re: Slow refresh rate (5-6hz) on Display managed by gnome-shell
*** This bug is a duplicate of bug 1970291 *** https://bugs.launchpad.net/bugs/1970291 Sure,I get it. The work around of using Xorg does not resolve the issue on this setup, Wayland and Xorg both suffer different problems. Just wanted to call that out! Simple open questions: 1. The NVIDIA DRM component here appears to be a culprit. Can I disable it ? Is there an open source driver that performs better than NVIDIA's proprietary driver here in this configuration you have run across ? 2. Exercising the NVIDIA GPU by using a VM (VirtualBox) was used as a method to troubleshoot and use it in a real world scenario. It may have run afoul of other bugs. Is there a better way to exercise the NVIDIA GPU and/or the Intel GPU and stay within the context of this ticket ? 3. gdm failing(?) to start when the NVIDIA GPU is set as PRIME, preventing GUI login seems like a bug. Would you like an Xorg(?) bug ticket for this ? 4. Please be advised, selecting Xorg as a server from the gdm login screen was never an option for me. Should I be concerned that a version or code difference here is leading us to different results ? 5. split_lock detection has knock-on effects due to the delay introduced, this was only highlighted by kernel logs using the the VirtualBox implementation when I began to exercise the GPU. Can we safely rule out split_lock's for this ticket ? Or is it worth troubleshooting further in the event I am experiencing the effects, but they're simply not getting reliably *detected* by the Tiger Lake or split_lock kernel logic ? Thanks. -- 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 Status in nvidia-graphics-drivers-535 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.
[Desktop-packages] [Bug 2026790] Re: Slow refresh rate (5-6hz) on Display managed by gnome-shell
*** This bug is a duplicate of bug 1970291 *** https://bugs.launchpad.net/bugs/1970291 Appears to be a red herring, VirtualBox apparently experiences random guest crashes when split lock detection is enabled on the Host OS. ( I am able to verify this ) Reference: "Random crashes with Windows 10 guest operating system with Intel Tiger Lake chipset" CPU is : https://ark.intel.com/content/www/us/en/ark/products/208664/intel-core-i71185g7-processor-12m-cache-up-to-4-80-ghz-with-ipu.html 11th Gen Intel(R) Core(TM) i7-1185G7 @ 3.00GHz (yes, it's Tiger Lake). The reference in the VirtualBox ticketing system seems to have been deleted, it appears that VirtualBox is using split locking. Reference to the much longer discussion of what this is and how it's impacting systems is here : https://lwn.net/Articles/911219/ seems there's a penalty applied when the code is doing split locking. This is a tunable. Deeper discussion of how Intel and the Linux kernel team were involved is here: https://www.virtualbox.org/ticket/20180?cversion=0&cnum_hist=4 Here are the errors again for the split lock, note the gnome-shell errors just before : 2023-07-11T16:01:26.427798-07:00 semiauto gnome-character[5478]: JS LOG: Characters Application exiting 2023-07-11T16:01:29.507946-07:00 semiauto gnome-shell[2700]: Can't update stage views actor [:0x55c018ffa2a0] is on because it needs an allocation. 2023-07-11T16:01:29.508086-07:00 semiauto gnome-shell[2700]: Can't update stage views actor [:0x55c01daf3ce0] is on because it needs an allocation. 2023-07-11T16:01:29.601935-07:00 semiauto gnome-shell[2700]: Can't update stage views actor [:0x55c01ab19670] is on because it needs an allocation. 2023-07-11T16:01:29.602058-07:00 semiauto gnome-shell[2700]: Can't update stage views actor [:0x55c018212df0] is on because it needs an allocation. 2023-07-11T16:01:37.587046-07:00 semiauto kernel: [ 2385.543465] x86/split lock detection: #AC: EMT-0/5871 took a split_lock trap at address: 0x7fd78aa96453 2023-07-11T16:01:38.079070-07:00 semiauto kernel: [ 2386.033592] x86/split lock detection: #AC: EMT-1/5872 took a split_lock trap at address: 0x7fd78aa96453 2023-07-11T16:01:39.723080-07:00 semiauto kernel: [ 2387.676986] x86/split lock detection: #AC: EMT-2/5873 took a split_lock trap at address: 0x7fd78aa96453 2023-07-11T16:01:45.484475-07:00 semiauto systemd[1]: systemd-timedated.service: Deactivated successfully. 2023-07-11T16:02:22.331078-07:00 semiauto kernel: [ 2430.285901] pcieport :00:07.2: pciehp: Slot(0-1): Link Down 2023-07-11T16:02:22.331102-07:00 semiauto kernel: [ 2430.285908] pcieport :00:07.2: pciehp: Slot(0-1): Card not present The split lock penalty triggered by VirtualBox seems to trip some kind of timer which causes the link to the eGPU to be reset. Which then of course causes all kinds of havoc on the system. Further logs ; 2023-07-11T16:07:55.895042-07:00 semiauto kernel: [ 2763.846900] thunderbolt :00:0d.2: failed to send driver ready to ICM So -- long way around , there are a lot of things interacting in here. I am unsure how to get a pure Xorg work-around in place to use the extra GPU. I am also a little concerned that any application doing split locking and having the kernel penalty imposed will cause this setup to crash because of link detection. Unsure where to go next, I suppose I'll try split lock disabling .. ** Bug watch added: Virtualbox Trac #20180 http://www.virtualbox.org/ticket/20180 -- 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 Status in nvidia-graphics-drivers-535 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
[Desktop-packages] [Bug 2026790] Re: Slow refresh rate (5-6hz) on Display managed by gnome-shell
*** This bug is a duplicate of bug 1970291 *** https://bugs.launchpad.net/bugs/1970291 Notably, when I "enable 3d" with a windows 10 guest on VirtualBox, I can see the GPU being actively used! Now, if there was only a way to use it with Xorg on the Host machine, not just the guest. -- 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 Status in nvidia-graphics-drivers-535 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
*** This bug is a duplicate of bug 1970291 *** https://bugs.launchpad.net/bugs/1970291 setting the PRIME profile back into place for NVIDIA. This causes the gdm issues, I suspect because this promotes the eGPU to primary and there is some kind of resource sharing problem. So, the way it MUST be configured is "ON DEMAND" PRIME -- which allows the eGPU to be detected, and allows logins to occur with Xorg. However, I am almost sure that this means most rendering is done via the Intel GPU, and not the NVIDIA GPU. I can see this lack of utilization by using nvidia-settings, I see the GPU utilization is 0%. It now has me curious if there is an intel-gpu-equivalent utilization tool? -- 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 Status in nvidia-graphics-drivers-535 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
[Desktop-packages] [Bug 2026790] Re: Slow refresh rate (5-6hz) on Display managed by gnome-shell
*** This bug is a duplicate of bug 1970291 *** https://bugs.launchpad.net/bugs/1970291 This may be unrelated -- but I am also seeing "x86/split lock detection" errors. Is this just a red herring ? Only seeing these when using the VirtualBox to drive the GPU. [Tue Jul 11 14:50:44 2023] usb 2-2.2: current rate 16000 is different from the runtime rate 48000 [Tue Jul 11 14:50:44 2023] usb 2-2.2: current rate 16000 is different from the runtime rate 48000 [Tue Jul 11 14:50:44 2023] usb 2-2.2: current rate 16000 is different from the runtime rate 48000 [Tue Jul 11 14:50:45 2023] Bluetooth: RFCOMM TTY layer initialized [Tue Jul 11 14:50:45 2023] Bluetooth: RFCOMM socket layer initialized [Tue Jul 11 14:50:45 2023] Bluetooth: RFCOMM ver 1.11 [Tue Jul 11 14:50:47 2023] thunderbolt 1-1: new device found, vendor=0x127 device=0x2 [Tue Jul 11 14:50:47 2023] thunderbolt 1-1: Razer Core X Chroma [Tue Jul 11 14:50:48 2023] rfkill: input handler disabled [Tue Jul 11 14:50:53 2023] thunderbolt 1-101: new device found, vendor=0x127 device=0x3 [Tue Jul 11 14:50:53 2023] thunderbolt 1-101: Razer Core X Chroma [Tue Jul 11 14:50:54 2023] rfkill: input handler enabled [Tue Jul 11 14:50:54 2023] usb 2-2.2: current rate 16000 is different from the runtime rate 48000 [Tue Jul 11 14:50:54 2023] usb 2-2.2: current rate 16000 is different from the runtime rate 48000 [Tue Jul 11 14:50:54 2023] usb 2-2.2: current rate 16000 is different from the runtime rate 48000 [Tue Jul 11 14:50:59 2023] rfkill: input handler disabled [Tue Jul 11 14:56:33 2023] SUPR0GipMap: fGetGipCpu=0x1b [Tue Jul 11 14:56:33 2023] vboxdrv: VMMR0.r0 [Tue Jul 11 14:56:33 2023] vboxdrv: VBoxDDR0.r0 [Tue Jul 11 14:56:41 2023] x86/split lock detection: #AC: EMT-1/4206 took a split_lock trap at address: 0x7f698f296453 [Tue Jul 11 14:57:03 2023] x86/split lock detection: #AC: EMT-2/4207 took a split_lock trap at address: 0x7f698f296453 [Tue Jul 11 14:57:03 2023] x86/split lock detection: #AC: EMT-0/4205 took a split_lock trap at address: 0x7f698f296453 Unsure why there is a magic address space number there: 0x7f698f296453 -- 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 Status in nvidia-graphics-drivers-535 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 so
[Desktop-packages] [Bug 2026790] Re: Slow refresh rate (5-6hz) on Display managed by gnome-shell
*** This bug is a duplicate of bug 1970291 *** https://bugs.launchpad.net/bugs/1970291 ok, SUPER interesting -- when I force the intel profile to be PRIME, then I can safely boot with the enclosure attached(!), the systems gets through gdm, and I can login no problem. I suspect there is a driver problem we are chasing, and PRIME was just selecting the NVIDIA GPU for some reason and flailing ..' Hmm running into a bit of a snag : beadon@semiauto:~$ sudo nvidia-settings [sudo] password for beadon: ERROR: NVIDIA driver is not loaded (nvidia-settings:3802): GLib-GObject-CRITICAL **: 14:38:11.591: g_object_unref: assertion 'G_IS_OBJECT (object)' failed ** (nvidia-settings:3802): CRITICAL **: 14:38:11.592: ctk_powermode_new: assertion '(ctrl_target != NULL) && (ctrl_target->h != NULL)' failed ERROR: nvidia-settings could not find the registry key file or the X server is not accessible. This file should have been installed along with this driver at /usr/share/nvidia/nvidia-application-profiles-key-documentation. The application profiles will continue to work, but values cannot be prepopulated or validated, and will not be listed in the help text. Please see the README for possible values and descriptions. ** Message: 14:38:11.616: PRIME: Requires offloading ** Message: 14:38:11.616: PRIME: is it supported? yes ** Message: 14:38:11.637: PRIME: Usage: /usr/bin/prime-select nvidia|intel|on-demand|query ** Message: 14:38:11.637: PRIME: on-demand mode: "1" ** Message: 14:38:11.637: PRIME: is "on-demand" mode supported? yes -- 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 Status in nvidia-graphics-drivers-535 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 N
[Desktop-packages] [Bug 2026790] Re: Slow refresh rate (5-6hz) on Display managed by gnome-shell
*** This bug is a duplicate of bug 1970291 *** https://bugs.launchpad.net/bugs/1970291 Then onto check why the GPU is not even being detected ... beadon@semiauto:~$ sudo nvidia-smi NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. beadon@semiauto:~$ dkms status 8812au/5.6.4.2_35491.20191025, 6.2.0-23-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 6.2.0-24-generic, x86_64: installed nvidia/535.54.03, 6.2.0-24-generic, x86_64: installed virtualbox/7.0.6, 6.2.0-23-generic, x86_64: installed virtualbox/7.0.6, 6.2.0-24-generic, x86_64: installed beadon@semiauto:~$ dpkg-reconfigure nvidia-dkms /usr/sbin/dpkg-reconfigure must be run as root beadon@semiauto:~$ sudo dpkg-reconfigure nvidia-dkms-535 Removing all DKMS Modules Done. update-initramfs: deferring update (trigger activated) INFO:Enable nvidia DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/lenovo_thinkpad DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/put_your_quirks_here DEBUG:Parsing /usr/share/ubuntu-drivers-common/quirks/dell_latitude Loading new nvidia-535.54.03 DKMS files... Building for 6.2.0-24-generic Building for architecture x86_64 Building initial module for 6.2.0-24-generic Done. nvidia.ko: Running module version sanity check. Module version 535.54.03 for nvidia.ko exactly matches what is already found in kernel 6.2.0-24-generic. DKMS will not replace this module. You may override by specifying --force. nvidia-modeset.ko: Running module version sanity check. Module version 535.54.03 for nvidia-modeset.ko exactly matches what is already found in kernel 6.2.0-24-generic. DKMS will not replace this module. You may override by specifying --force. nvidia-drm.ko: Running module version sanity check. Module version 535.54.03 for nvidia-drm.ko exactly matches what is already found in kernel 6.2.0-24-generic. DKMS will not replace this module. You may override by specifying --force. nvidia-uvm.ko: Running module version sanity check. Module version 535.54.03 for nvidia-uvm.ko exactly matches what is already found in kernel 6.2.0-24-generic. DKMS will not replace this module. You may override by specifying --force. nvidia-peermem.ko: Running module version sanity check. Module version 535.54.03 for nvidia-peermem.ko exactly matches what is already found in kernel 6.2.0-24-generic. DKMS will not replace this module. You may override by specifying --force. depmod... Processing triggers for initramfs-tools (0.142ubuntu2) ... update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic hmm, modules are in place .. -- 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 Status in nvidia-graphics-drivers-535 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
[Desktop-packages] [Bug 2026790] Re: Slow refresh rate (5-6hz) on Display managed by gnome-shell
*** This bug is a duplicate of bug 1970291 *** https://bugs.launchpad.net/bugs/1970291 I am also seeing a couple things like this .. options nvidia-drm modeset=1 Perhaps this is a path I need to take and specify PRIME vs non-prime ? https://forums.developer.nvidia.com/t/prime-and-prime-synchronization/44423 -- 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 Status in nvidia-graphics-drivers-535 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
*** This bug is a duplicate of bug 1970291 *** https://bugs.launchpad.net/bugs/1970291 worse still , now I cannot get a gdm login unless I disconnect the USB-C eGPU (this NVIDIA GPU enclosure). I am reading up further on "prime" and "reverse prime" GPUs. The behavior here may be similar: https://forums.developer.nvidia.com/t/failed-to-lookup-gem-object-for-mapping/186526 Here is a log of the connect/disconnect (see attached log). ** Attachment added: "dmesg-output-no-gdm-at-boot-when-usb-c-connected--see-functional-boot-here" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026790/+attachment/5685463/+files/dmesg-output-no-gdm-at-boot-when-usb-c-connected--see-functional-boot-here -- 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 Status in nvidia-graphics-drivers-535 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://l
[Desktop-packages] [Bug 2026790] Re: Slow refresh rate (5-6hz) on Display managed by gnome-shell
*** This bug is a duplicate of bug 1970291 *** https://bugs.launchpad.net/bugs/1970291 Notably -- there seems to be a known issue with DisplayPort connectivity 1.3 and 1.4 and NVIDIA GPUs recently. I am seeing a firmware update issued by NVIDIA on June 26 2023 for SOME NVIDIA chipsets: https://www.nvidia.com/en-us/drivers/nv-uefi-update-x64/ The GTX 1650 chipset does not appear to be impacted. -- 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 Status in nvidia-graphics-drivers-535 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
*** This bug is a duplicate of bug 1970291 *** https://bugs.launchpad.net/bugs/1970291 As expected I am using Xorg now, beadon@semiauto:~$ echo $XDG_SESSION_TYPE x11 -- 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 Status in nvidia-graphics-drivers-535 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
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. | | |
[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 2023667] [NEW] bijiben-shell (gnome? xorg?) using libgobject-2.0.so crashes causing unknown issues.
Public bug reported: Tracking this error reported in [Mon Jun 12 18:08:47 2023] show_signal_msg: 18 callbacks suppressed [Mon Jun 12 18:08:47 2023] bijiben-shell-s[13881]: segfault at 7ff68b155ba2 ip 7ff188e135a1 sp 7ffdf5331d38 error 4 in libgobject-2.0.so.0.7600.1[7ff188de9000+34000] likely on CPU 6 (core 2, socket 0) [Mon Jun 12 18:08:47 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 Jun 12 18:08:48 2023] bijiben-shell-s[14125]: segfault at 7fee129f1460 ip 7fea113305a1 sp 7ffd63ec4f18 error 4 in libgobject-2.0.so.0.7600.1[7fea11306000+34000] likely on CPU 0 (core 0, socket 0) [Mon Jun 12 18:08:48 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 Jun 12 18:08:48 2023] bijiben-shell-s[14163]: segfault at 560d0014 ip 7fa3b3c245b0 sp 7ffc0fb46cf8 error 4 in libgobject-2.0.so.0.7600.1[7fa3b3bfa000+34000] likely on CPU 7 (core 3, socket 0) [Mon Jun 12 18:08:48 2023] Code: 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 d0 48 0f 94 c2 0f b6 d2 89 d0 c3 66 0f 1f 44 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..52.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 525.105.17 Tue Mar 28 18:02:59 UTC 2023 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-17ubuntu1) ApportVersion: 2.26.1-0ubuntu2 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: Tue Jun 13 10:26:09 2023 DistUpgraded: 2023-04-26 15:38:23,675 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. TU117 [GeForce GTX 1650] [3842:1257] InstallationDate: Installed on 2023-01-09 (155 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-26 (47 days ago) dmi.bios.date: 04/05/2023 dmi.bios.release: 1.60 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET84W (1.60 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET84W(1.60):bd04/05/2023:br1.60:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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
[Desktop-packages] [Bug 2016046] [NEW] connecting to samba fileshare fails if smb1(now deprecated) is not supported by the server
Public bug reported: When connecting with Nautilus to "smb://hostname.lan/" note - not the full path to the samba share, and this is a resolvable ".lan" name handled by the local DNS server - then gvfsd fails, and doesn't send a proper error back to nautilus. This display in Nautilus is simply "Folder is empty" Apr 12 19:31:31 semiauto dbus-daemon[729]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.1635' (uid=1000 pid=381751 comm="/usr/bin/nautilus --gapplication-service" label="unconfined") Apr 12 19:31:31 semiauto gnome-shell[1916]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Apr 12 19:31:31 semiauto systemd[1]: Starting Hostname Service... Apr 12 19:31:31 semiauto dbus-daemon[729]: [system] Successfully activated service 'org.freedesktop.hostname1' Apr 12 19:31:31 semiauto systemd[1]: Started Hostname Service. Apr 12 19:31:42 semiauto nautilus[381751]: GtkText - did not receive a focus-out event.#012If you handle this event, you must return#012GDK_EVENT_PROPAGATE so the default handler#012gets the event as well Apr 12 19:31:42 semiauto gvfsd[171389]: smbXcli_negprot_smb1_done: No compatible protocol selected by server. Apr 12 19:32:01 semiauto systemd[1]: systemd-hostnamed.service: Deactivated successfully. Since the client forces the server to use NT1 protocols, and the server is configured to NOT permit this, then hte client connection fails - ungracefully. The solution is a few parts : 1. Negotatiate up to higher levels of encryption during connection time. 2. Gracefully provide a message back to nautilus that there is an error in connecting for X or Y reason (encryption related, specific to connection to this server ) It appears that this has been a known problem now for a few years, here is a reference to it in 2021 (but in Linux Mint): https://forums.linuxmint.com/viewtopic.php?t=363511 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gvfs 1.48.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Apr 12 19:26:46 2023 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gvfs UpgradeStatus: Upgraded to jammy on 2022-11-22 (141 days ago) ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/2016046 Title: connecting to samba fileshare fails if smb1(now deprecated) is not supported by the server Status in gvfs package in Ubuntu: New Bug description: When connecting with Nautilus to "smb://hostname.lan/" note - not the full path to the samba share, and this is a resolvable ".lan" name handled by the local DNS server - then gvfsd fails, and doesn't send a proper error back to nautilus. This display in Nautilus is simply "Folder is empty" Apr 12 19:31:31 semiauto dbus-daemon[729]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.1635' (uid=1000 pid=381751 comm="/usr/bin/nautilus --gapplication-service" label="unconfined") Apr 12 19:31:31 semiauto gnome-shell[1916]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Apr 12 19:31:31 semiauto systemd[1]: Starting Hostname Service... Apr 12 19:31:31 semiauto dbus-daemon[729]: [system] Successfully activated service 'org.freedesktop.hostname1' Apr 12 19:31:31 semiauto systemd[1]: Started Hostname Service. Apr 12 19:31:42 semiauto nautilus[381751]: GtkText - did not receive a focus-out event.#012If you handle this event, you must return#012GDK_EVENT_PROPAGATE so the default handler#012gets the event as well Apr 12 19:31:42 semiauto gvfsd[171389]: smbXcli_negprot_smb1_done: No compatible protocol selected by server. Apr 12 19:32:01 semiauto systemd[1]: systemd-hostnamed.service: Deactivated successfully. Since the client forces the server to use NT1 protocols, and the server is configured to NOT permit this, then hte client connection fails - ungracefully. The solution is a few parts : 1. Negotatiate up to higher levels of encryption during connection time. 2. Gracefully provide a message back to nautilus that there is an error in connecting for X or Y reason (encryption related, specific to connection to this server ) It appears that this has been a known problem now for a few years, here is a reference to it in 2021 (but in Linux Mint): https://forums.linuxmint.com/viewtopic.php?t=363511 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gvfs 1.48.2
[Desktop-packages] [Bug 2012288] Re: Ubuntu Gnome Settings / Chrome / CUPS (printing) communications
Update, I found that CUPS was failing to be modified by the gnome(?)
user interface component.
apparmor is getting in the way, "protecting" cupsd.
To fix this, install the apparmor utilities:
sudo apt-get install apparmor-utils
Then set apparmor to complain about cupsd, instead of blocking access:
sudo aa-complain cupsd
You can now print. I hope this helps someone else too. This was quite
difficult to troubleshoot.
ar 24 16:10:45 semiauto google-chrome.desktop[216920]:
[216913:216943:0324/161045.967690:ERROR:connection_factory_impl.cc(428)] Failed
to connect to MCS endpoint with error -105
Mar 24 16:10:46 semiauto google-chrome.desktop[216920]:
[216913:216913:0324/161046.442656:ERROR:device_event_log_impl.cc(222)]
[16:10:46.442] Printer: local_printer_handler_default.cc:167 Failure
enumerating local printers, result: kFailed
Mar 24 16:10:46 semiauto google-chrome.desktop[216920]: Warning: disabling flag
--expose_wasm due to conflicting flags
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]:
/usr/share/system-config-printer/system-config-printer.py:325:
DeprecationWarning: Gtk.ActionGroup.list_actions is deprecated
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]: for action in
printer_manager_action_group.list_actions ():
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]:
/usr/share/system-config-printer/system-config-printer.py:326:
DeprecationWarning: Gtk.Action.set_sensitive is deprecated
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]: action.set_sensitive
(False)
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]:
/usr/share/system-config-printer/system-config-printer.py:334:
DeprecationWarning: Gtk.ActionGroup.get_action is deprecated
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]: act =
printer_manager_action_group.get_action (action)
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]:
/usr/share/system-config-printer/system-config-printer.py:364:
DeprecationWarning: Gtk.UIManager.ensure_update is deprecated
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]:
self.ui_manager.ensure_update ()
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]:
/usr/share/system-config-printer/system-config-printer.py:365:
DeprecationWarning: Gtk.UIManager.get_accel_group is deprecated
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]:
self.PrintersWindow.add_accel_group (self.ui_manager.get_accel_group ())
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]:
/usr/share/system-config-printer/system-config-printer.py:374:
DeprecationWarning: Gtk.UIManager.get_action is deprecated
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]: action =
self.ui_manager.get_action ("/new-printer")
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]:
/usr/share/system-config-printer/system-config-printer.py:375:
DeprecationWarning: Gtk.Action.create_menu_item is deprecated
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]: newprinteritem =
action.create_menu_item ()
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]:
/usr/share/system-config-printer/system-config-printer.py:673:
DeprecationWarning: Gtk.Action.get_proxies is deprecated
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]: for widget in
action.get_proxies ():
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]:
/usr/share/system-config-printer/system-config-printer.py:2253:
DeprecationWarning: Gdk.threads_enter is deprecated
Mar 24 16:10:51 semiauto google-chrome.desktop[216920]: Gdk.threads_enter ()
Mar 24 16:10:51 semiauto dbus-daemon[764]: [system] Activating via systemd:
service name='org.freedesktop.hostname1'
unit='dbus-org.freedesktop.hostname1.service' requested by ':1.1686' (uid=1000
pid=395280 comm="/usr/bin/python3 /usr/share/system-config-printer/"
label="unconfined")
Mar 24 16:10:51 semiauto systemd[1]: Starting Hostname Service...
Mar 24 16:10:51 semiauto dbus-daemon[764]: [system] Successfully activated
service 'org.freedesktop.hostname1'
Mar 24 16:10:51 semiauto systemd[1]: Started Hostname Service.
Mar 24 16:10:53 semiauto kernel: [663246.142511] serial :00:16.3: LSR
safety check engaged!
Mar 24 16:10:53 semiauto kernel: [663246.142539] audit: type=1400
audit(1679688653.733:100): apparmor="DENIED" operation="capable" class="cap"
profile="/usr/sbin/cupsd" pid=395323 comm="serial" capability=21
capname="sys_admin"
Here were a few other telling messages:
Mar 24 16:13:14 semiauto kernel: [663387.182005] audit: type=1400
audit(1679688794.769:101): apparmor="DENIED" operation="file_lock" class="file"
profile="/usr/sbin/cupsd" name="/run/utmp" pid=287961 comm="cupsd"
requested_mask="k" denied_mask="k" fsuid=0 ouid=0
Mar 24 16:13:17 semiauto kernel: [663389.718118] audit: type=1400
audit(1679688797.305:102): apparmor="DENIED" operation="file_lock" class="file"
profile="/usr/sbin/cupsd" name="/run/utmp" pid=287961 comm="cupsd"
requested_mask="k" denied_mask="k" fsuid=0 ouid=0
Mar 24 16:13:24 semiauto k
[Desktop-packages] [Bug 2012288] Re: Ubuntu Gnome Settings / Chrome / CUPS (printing) communications
If not already clear, I cannot print properly -- this setuo is somehow preventing it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2012288 Title: Ubuntu Gnome Settings / Chrome / CUPS (printing) communications Status in cups package in Ubuntu: New Bug description: I am trying to print. Context :: printer - The network printer I have "HP LaserJet Professional M1217nfw MFP" announces itself via Bonjour, supports SLP Config, LPD Printing and WS-Discovery. The printer is wired to ethernet, and receives it's IP address in IPV4 and IPV6 from the router, set statically at the router. Client - The client machine, Ubuntu 22.10 , is either on wireless (192.168.2.X - DHCP assigned randomly) or wired ethernet (192.168.2.Y - DHCP assigned statically). Sometimes the machine has both interfaces as well as receiving IPV6 addresses for both of these interfaces. It's unclear how printing occurs for discovery, but for comparison - Android "just works", iPhone "just works" , and Windows 10 "just works". Only Ubuntu is the outlier here. When printing a PDF from Chrome, I see there is a mismatch between the printers that Chrome sees, and the printers that are registered with the gnome(?) printers configuration settings. This leads me to believe that these 2 parts of printing are not in sync with one another(!!). Additional, possibly related behavior: When I remove all printers listed. And simply watch the Gnome(?) Printers settings section then a new printer is added automatically exactly this text, yes the duplicate 'HP': "HP HP Laserjet Professional M1217nfw MFP, driverless". This may be a cause of issues since I have not configured an additional printer, yet it appears. When I DO attempt to print to this auto-added printer I receive a vague error after some kind of timeout "Stopped Please restart when the problem is resolved" --- what problem ? What is causing the issue ? This error does not help identify the issue. Can you help me understand what is happening here and how this can be resolved ? If auto-adding a printer is going to magically work , then please include detailed, actionable error messages. Attached -- screenshot of printer subsystems mismatch. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.mig: 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 525.85.05 Sat Jan 14 00:49:50 UTC 2023 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 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 Mar 20 11:54:41 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.19.0-31-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-35-generic, x86_64: installed nvidia/525.85.05, 5.19.0-35-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-31-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (70 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-01-15 (64 days ago) dmi.bios.date: 02/09/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET83W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dm
[Desktop-packages] [Bug 2012288] [NEW] Ubuntu Gnome Settings / Chrome / CUPS (printing) communications
Public bug reported: I am trying to print. Context :: printer - The network printer I have "HP LaserJet Professional M1217nfw MFP" announces itself via Bonjour, supports SLP Config, LPD Printing and WS-Discovery. The printer is wired to ethernet, and receives it's IP address in IPV4 and IPV6 from the router, set statically at the router. Client - The client machine, Ubuntu 22.10 , is either on wireless (192.168.2.X - DHCP assigned randomly) or wired ethernet (192.168.2.Y - DHCP assigned statically). Sometimes the machine has both interfaces as well as receiving IPV6 addresses for both of these interfaces. It's unclear how printing occurs for discovery, but for comparison - Android "just works", iPhone "just works" , and Windows 10 "just works". Only Ubuntu is the outlier here. When printing a PDF from Chrome, I see there is a mismatch between the printers that Chrome sees, and the printers that are registered with the gnome(?) printers configuration settings. This leads me to believe that these 2 parts of printing are not in sync with one another(!!). Additional, possibly related behavior: When I remove all printers listed. And simply watch the Gnome(?) Printers settings section then a new printer is added automatically exactly this text, yes the duplicate 'HP': "HP HP Laserjet Professional M1217nfw MFP, driverless". This may be a cause of issues since I have not configured an additional printer, yet it appears. When I DO attempt to print to this auto-added printer I receive a vague error after some kind of timeout "Stopped Please restart when the problem is resolved" --- what problem ? What is causing the issue ? This error does not help identify the issue. Can you help me understand what is happening here and how this can be resolved ? If auto-adding a printer is going to magically work , then please include detailed, actionable error messages. Attached -- screenshot of printer subsystems mismatch. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.mig: 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 525.85.05 Sat Jan 14 00:49:50 UTC 2023 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 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 Mar 20 11:54:41 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.19.0-31-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-35-generic, x86_64: installed nvidia/525.85.05, 5.19.0-35-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-31-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-35-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (70 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-01-15 (64 days ago) dmi.bios.date: 02/09/2023 dmi.bios.release: 1.59 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET83W (1.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET83W(1.59):bd02/09/2023:br1.59:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO nvidia-settings: ERROR: An internal driver
[Desktop-packages] [Bug 2006070] Re: incredibly high memory usage
Ok, somewhat good news. I have been watching the memory usage on the machine as many applications start / stop , and am tracking the growth and management. A tool to tweak the behavior --- One system parameter I had tweaked before reporting this issue was vm.swappiness , I had moved this down to 30, mostly because I'd like to get the best performance, while avoiding the use of swap space. it had the intened effect, while using almost all available memory - generally a good thing (why have all this memory if you're not using it, right?). Now, i've moved this back up to 60 (which I believe is the default for the kernel options). In response I am seeing better free-memory management from the kernel. The downside is that I am absolutely seeing lower performance on and across web-pages and other applications as swap is used a bit more. The difference is measured in fractions of a second, I could measure the difference but I'm not sure if this audience would like to see those details (let me know if this is interesting). For those at home -- edit: /etc/sysctl.conf, modify or add the parameter 'vm.swappiness = 60' and then on your terminal run 'sysctl -p'. I mention this on this bug thread because this parameter directly effects the OOM killer behavior because the OOM killer appears to be swapiness un-aware, and this is also the underlying behavior modifier for the Chrome threads, and the Flatpak or gnome-software threads as they grow in size. I will continue to monitor for gnome-software threads and memory usage, but this means the heavier memory usage is effectively hidden by worse offenders (chrome likely being one of the heaviest users for us all). On Chrome -- Since Chrome is doing so much lately to manage their own threads, I hope this kerenel tuning parameter is kept in mind for memory management, it could save the team a lot of time building their own memory management utility/toolchain. There might even be some kind of alert / capability for the kernel to respond differently to certain applications depending on how aggressive they would like their own userspace managed. (Kerenel development feature!) One gnome-software -- I will keep tabs on the Flatpak memory usage. In the mean time I have disabled snapd entirely. I don't wish to manage my applications like this. Apt is about as far as I want to go now, the interactions of many different pakage managers adds a lot of complexity. I want to incentivize application develoeprs to use as few packaging systems as possible. It's getting quite bad out there - there's are now whole businesses that have sprung up to convert the same binaries into different packaging formats and their dependencies. It's really got to stop, it's such a waste of time and resources to 're-invent the wheel'. On the root cause -- I would much prefer that we encourage developers to build statically compiled binaries, rather than build containers upon containers to manage what I see as effectively a problem stemming from resource sharing linked to library (mis)management. I hope this is helpful to development here and across kernel development. I will continue to provide meaningful feedback as much as possible. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2006070 Title: incredibly high memory usage Status in GNOME Software: Unknown Status in gnome-software package in Ubuntu: Incomplete Bug description: Please describe the issue you’re experiencing: gnome-software is consuming 6+ GB of RAM on my machine. This is unacceptable and is affecting all other applications. Error message appearing in /var/log/syslog N/A -- other processes are fighting for memory, and OOM killer is more active. What Linux distribution are you using, and what kind of package (RPM, deb, flatpak, etc.) are you experiencing the problem with? Ubuntu 22.10 apt flatpak I don't know how to replicate this issue, however it does appear to be a problem retaining memory. See LSOF report below, software is gnome-software 43.0 ``` sudo lsof -p 750448 -n > ~/ramusage.txt cat ramusage.txt | perl -lane 'print "$F[6] $F[0] $F[1] $F[2] $F[3] $F[4] $F[5] $F[7] $F[8] $F[9] $F[10]"' | sort -rn > sorted-report.txt ``` Top 10 filehandles are holding onto something like 6GB of RAM?! What's going on here ? (open filehandles, sorted by bytes): ``` 1 157191688 gnome-sof 750448 beadon 11u netlink 0t0 ROUTE 2 103546882 gnome-sof 750448 beadon DEL REG 259,2 /usr/share/icons/hicolor/icon-theme.cache 3 103022860 gnome-sof 750448 beadon DEL REG 259,2 /usr/share/glib-2.0/schemas/gschemas.compiled 4 61210892 gnome-sof 750448 beadon DEL REG 259,2 /var/lib/flatpak/exports/s
[Desktop-packages] [Bug 2006070] Re: incredibly high memory usage
Yes, I killed the process as it approached 6GB after I filed this report. I will report back with the growth over the next few days. I suspect it occured when I switched between different wireless networks and physical locations, but I would need to run a series of tests to conslude this for certain. I also find Chrome's dramatic consumption of memory to be unnecessary, but this is another task to trace For the moment, I still am focused on gnome-software. For reference I am finding 2-older reports of a memory leak in gnome-software, but these too seemed to have died out as the reporter eventually stopped responding (they're a year old or more). These might be related. reference: https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1590 https://gitlab.gnome.org/GNOME/gnome-software/-/issues/941 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-software/-/issues #1590 https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1590 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-software/-/issues #941 https://gitlab.gnome.org/GNOME/gnome-software/-/issues/941 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2006070 Title: incredibly high memory usage Status in GNOME Software: Unknown Status in gnome-software package in Ubuntu: Incomplete Bug description: Please describe the issue you’re experiencing: gnome-software is consuming 6+ GB of RAM on my machine. This is unacceptable and is affecting all other applications. Error message appearing in /var/log/syslog N/A -- other processes are fighting for memory, and OOM killer is more active. What Linux distribution are you using, and what kind of package (RPM, deb, flatpak, etc.) are you experiencing the problem with? Ubuntu 22.10 apt flatpak I don't know how to replicate this issue, however it does appear to be a problem retaining memory. See LSOF report below, software is gnome-software 43.0 ``` sudo lsof -p 750448 -n > ~/ramusage.txt cat ramusage.txt | perl -lane 'print "$F[6] $F[0] $F[1] $F[2] $F[3] $F[4] $F[5] $F[7] $F[8] $F[9] $F[10]"' | sort -rn > sorted-report.txt ``` Top 10 filehandles are holding onto something like 6GB of RAM?! What's going on here ? (open filehandles, sorted by bytes): ``` 1 157191688 gnome-sof 750448 beadon 11u netlink 0t0 ROUTE 2 103546882 gnome-sof 750448 beadon DEL REG 259,2 /usr/share/icons/hicolor/icon-theme.cache 3 103022860 gnome-sof 750448 beadon DEL REG 259,2 /usr/share/glib-2.0/schemas/gschemas.compiled 4 61210892 gnome-sof 750448 beadon DEL REG 259,2 /var/lib/flatpak/exports/share/icons/hicolor/icon-theme.cache 5 60828700 gnome-sof 750448 beadon DEL REG 259,2 /var/cache/fontconfig/2bd0278d-49c2-4c8c-9eea-32d695b22756-le64.cache-7 6 30430848 gnome-sof 750448 beadon mem REG 259,2 101455545 /usr/lib/x86_64-linux-gnu/libicudata.so.71.1 7 14516125 gnome-sof 750448 beadon mem REG 259,2 97416011 /home/beadon/.cache/gnome-software/flatpak-system-default/components.xmlb 8 11308392 gnome-sof 750448 beadon mem REG 259,2 101450031 /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0 9 8254320 gnome-sof 750448 beadon mem REG 259,2 101450280 /usr/lib/x86_64-linux-gnu/libgtk-4.so.1.800.1 10 7599984 gnome-sof 750448 beadon 475u REG 259,2 60821438 /var/tmp/#60821438 (deleted) 11 7582821 gnome-sof 750448 beadon 476u REG 259,2 60821485 /var/tmp/#60821485 (deleted) 12 6733824 gnome-sof 750448 beadon 478u REG 259,2 60821699 /var/tmp/#60821699 (deleted) 13 5966212 gnome-sof 750448 beadon mem REG 259,2 97419097 /home/beadon/.cache/gnome-software/appstream/components.xmlb 14 5712208 gnome-sof 750448 beadon mem REG 259,2 101450114 /usr/lib/locale/locale-archive 15 5681431 gnome-sof 750448 beadon 477u REG 259,2 60821584 /var/tmp/#60821584 (deleted) 16 5469177 gnome-sof 750448 beadon 482u REG 259,2 60817847 /var/tmp/#60817847 (deleted) 17 5406720 gnome-sof 750448 beadon 479u REG 259,2 60821593 /var/tmp/#60821593 (deleted) 18 5341166 gnome-sof 750448 beadon 493u REG 259,2 60821670 /var/tmp/#60821670 (deleted) 19 4616704 gnome-sof 750448 beadon 206u REG 259,2 60819152 /var/tmp/#60819152 (deleted) 20 4519958 gnome-sof 750448 beadon 497u REG 259,2 60821824 /var/tmp/#60821824 (deleted) ``` Details: [sorted-report.txt](/uploads/43c17fb8547366c33c3e49931a5a07b7/sorted-report.txt) ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 5 20:06:15 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running
[Desktop-packages] [Bug 2006070] Re: incredibly high memory usage
Ok, one better, sorted results (lots of chrome tabs appear, fyi). ps auxw --sort -rss > psall.txt See attached file, since gnome-software has restarted, in 1 day it's up to 501+MB and written ~1.9GB to disk (why??). ** Attachment added: "psall.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2006070/+attachment/5645104/+files/psall.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2006070 Title: incredibly high memory usage Status in GNOME Software: Unknown Status in gnome-software package in Ubuntu: Incomplete Bug description: Please describe the issue you’re experiencing: gnome-software is consuming 6+ GB of RAM on my machine. This is unacceptable and is affecting all other applications. Error message appearing in /var/log/syslog N/A -- other processes are fighting for memory, and OOM killer is more active. What Linux distribution are you using, and what kind of package (RPM, deb, flatpak, etc.) are you experiencing the problem with? Ubuntu 22.10 apt flatpak I don't know how to replicate this issue, however it does appear to be a problem retaining memory. See LSOF report below, software is gnome-software 43.0 ``` sudo lsof -p 750448 -n > ~/ramusage.txt cat ramusage.txt | perl -lane 'print "$F[6] $F[0] $F[1] $F[2] $F[3] $F[4] $F[5] $F[7] $F[8] $F[9] $F[10]"' | sort -rn > sorted-report.txt ``` Top 10 filehandles are holding onto something like 6GB of RAM?! What's going on here ? (open filehandles, sorted by bytes): ``` 1 157191688 gnome-sof 750448 beadon 11u netlink 0t0 ROUTE 2 103546882 gnome-sof 750448 beadon DEL REG 259,2 /usr/share/icons/hicolor/icon-theme.cache 3 103022860 gnome-sof 750448 beadon DEL REG 259,2 /usr/share/glib-2.0/schemas/gschemas.compiled 4 61210892 gnome-sof 750448 beadon DEL REG 259,2 /var/lib/flatpak/exports/share/icons/hicolor/icon-theme.cache 5 60828700 gnome-sof 750448 beadon DEL REG 259,2 /var/cache/fontconfig/2bd0278d-49c2-4c8c-9eea-32d695b22756-le64.cache-7 6 30430848 gnome-sof 750448 beadon mem REG 259,2 101455545 /usr/lib/x86_64-linux-gnu/libicudata.so.71.1 7 14516125 gnome-sof 750448 beadon mem REG 259,2 97416011 /home/beadon/.cache/gnome-software/flatpak-system-default/components.xmlb 8 11308392 gnome-sof 750448 beadon mem REG 259,2 101450031 /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0 9 8254320 gnome-sof 750448 beadon mem REG 259,2 101450280 /usr/lib/x86_64-linux-gnu/libgtk-4.so.1.800.1 10 7599984 gnome-sof 750448 beadon 475u REG 259,2 60821438 /var/tmp/#60821438 (deleted) 11 7582821 gnome-sof 750448 beadon 476u REG 259,2 60821485 /var/tmp/#60821485 (deleted) 12 6733824 gnome-sof 750448 beadon 478u REG 259,2 60821699 /var/tmp/#60821699 (deleted) 13 5966212 gnome-sof 750448 beadon mem REG 259,2 97419097 /home/beadon/.cache/gnome-software/appstream/components.xmlb 14 5712208 gnome-sof 750448 beadon mem REG 259,2 101450114 /usr/lib/locale/locale-archive 15 5681431 gnome-sof 750448 beadon 477u REG 259,2 60821584 /var/tmp/#60821584 (deleted) 16 5469177 gnome-sof 750448 beadon 482u REG 259,2 60817847 /var/tmp/#60817847 (deleted) 17 5406720 gnome-sof 750448 beadon 479u REG 259,2 60821593 /var/tmp/#60821593 (deleted) 18 5341166 gnome-sof 750448 beadon 493u REG 259,2 60821670 /var/tmp/#60821670 (deleted) 19 4616704 gnome-sof 750448 beadon 206u REG 259,2 60819152 /var/tmp/#60819152 (deleted) 20 4519958 gnome-sof 750448 beadon 497u REG 259,2 60821824 /var/tmp/#60821824 (deleted) ``` Details: [sorted-report.txt](/uploads/43c17fb8547366c33c3e49931a5a07b7/sorted-report.txt) ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 5 20:06:15 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/525.78.01, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] Installatio
[Desktop-packages] [Bug 2006070] Re: incredibly high memory usage
shoot -- can a maintainer please help me attach this to the right poject
? This is not Xorg specific.
--
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/2006070
Title:
incredibly high memory usage
Status in X.Org X server:
Unknown
Status in xorg package in Ubuntu:
New
Bug description:
Please describe the issue you’re experiencing:
gnome-software is consuming 6+ GB of RAM on my machine. This is unacceptable
and is affecting all other applications.
Error message appearing in /var/log/syslog
N/A -- other processes are fighting for memory, and OOM killer is more active.
What Linux distribution are you using, and what kind of package (RPM, deb,
flatpak, etc.) are you experiencing the problem with?
Ubuntu 22.10
apt
flatpak
I don't know how to replicate this issue, however it does appear to be a
problem retaining memory. See LSOF report below, software is gnome-software
43.0
```
sudo lsof -p 750448 -n > ~/ramusage.txt
cat ramusage.txt | perl -lane 'print "$F[6] $F[0] $F[1] $F[2] $F[3] $F[4]
$F[5] $F[7] $F[8] $F[9] $F[10]"' | sort -rn > sorted-report.txt
```
Top 10 filehandles are holding onto something like 6GB of RAM?! What's going
on here ?
(open filehandles, sorted by bytes):
```
1 157191688 gnome-sof 750448 beadon 11u netlink 0t0 ROUTE
2 103546882 gnome-sof 750448 beadon DEL REG 259,2
/usr/share/icons/hicolor/icon-theme.cache
3 103022860 gnome-sof 750448 beadon DEL REG 259,2
/usr/share/glib-2.0/schemas/gschemas.compiled
4 61210892 gnome-sof 750448 beadon DEL REG 259,2
/var/lib/flatpak/exports/share/icons/hicolor/icon-theme.cache
5 60828700 gnome-sof 750448 beadon DEL REG 259,2
/var/cache/fontconfig/2bd0278d-49c2-4c8c-9eea-32d695b22756-le64.cache-7
6 30430848 gnome-sof 750448 beadon mem REG 259,2 101455545
/usr/lib/x86_64-linux-gnu/libicudata.so.71.1
7 14516125 gnome-sof 750448 beadon mem REG 259,2 97416011
/home/beadon/.cache/gnome-software/flatpak-system-default/components.xmlb
8 11308392 gnome-sof 750448 beadon mem REG 259,2 101450031
/usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0
9 8254320 gnome-sof 750448 beadon mem REG 259,2 101450280
/usr/lib/x86_64-linux-gnu/libgtk-4.so.1.800.1
10 7599984 gnome-sof 750448 beadon 475u REG 259,2 60821438
/var/tmp/#60821438 (deleted)
11 7582821 gnome-sof 750448 beadon 476u REG 259,2 60821485
/var/tmp/#60821485 (deleted)
12 6733824 gnome-sof 750448 beadon 478u REG 259,2 60821699
/var/tmp/#60821699 (deleted)
13 5966212 gnome-sof 750448 beadon mem REG 259,2 97419097
/home/beadon/.cache/gnome-software/appstream/components.xmlb
14 5712208 gnome-sof 750448 beadon mem REG 259,2 101450114
/usr/lib/locale/locale-archive
15 5681431 gnome-sof 750448 beadon 477u REG 259,2 60821584
/var/tmp/#60821584 (deleted)
16 5469177 gnome-sof 750448 beadon 482u REG 259,2 60817847
/var/tmp/#60817847 (deleted)
17 5406720 gnome-sof 750448 beadon 479u REG 259,2 60821593
/var/tmp/#60821593 (deleted)
18 5341166 gnome-sof 750448 beadon 493u REG 259,2 60821670
/var/tmp/#60821670 (deleted)
19 4616704 gnome-sof 750448 beadon 206u REG 259,2 60819152
/var/tmp/#60819152 (deleted)
20 4519958 gnome-sof 750448 beadon 497u REG 259,2 60821824
/var/tmp/#60821824 (deleted)
```
Details:
[sorted-report.txt](/uploads/43c17fb8547366c33c3e49931a5a07b7/sorted-report.txt)
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
BootLog:
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Feb 5 20:06:15 2023
DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript:
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: kinetic
DistroVariant: ubuntu
DkmsStatus:
8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed
8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed
nvidia/525.78.01, 5.19.0-29-generic, x86_64: installed
virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed
virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01)
(prog-if 00 [VGA controller])
Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4]
InstallationDate: Installed on 2023-01-09 (27 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64
(20220809.1)
MachineType: LENOVO 20XY0027US
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLin
[Desktop-packages] [Bug 2006070] Re: incredibly high memory usage
sorted report. ** Attachment added: "unsorted memory usage report." https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2006070/+attachment/5645006/+files/ramusage.txt ** Also affects: xorg-server via https://gitlab.gnome.org/GNOME/gnome-software/-/issues/2064 Importance: Unknown Status: Unknown -- 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/2006070 Title: incredibly high memory usage Status in X.Org X server: Unknown Status in xorg package in Ubuntu: New Bug description: Please describe the issue you’re experiencing: gnome-software is consuming 6+ GB of RAM on my machine. This is unacceptable and is affecting all other applications. Error message appearing in /var/log/syslog N/A -- other processes are fighting for memory, and OOM killer is more active. What Linux distribution are you using, and what kind of package (RPM, deb, flatpak, etc.) are you experiencing the problem with? Ubuntu 22.10 apt flatpak I don't know how to replicate this issue, however it does appear to be a problem retaining memory. See LSOF report below, software is gnome-software 43.0 ``` sudo lsof -p 750448 -n > ~/ramusage.txt cat ramusage.txt | perl -lane 'print "$F[6] $F[0] $F[1] $F[2] $F[3] $F[4] $F[5] $F[7] $F[8] $F[9] $F[10]"' | sort -rn > sorted-report.txt ``` Top 10 filehandles are holding onto something like 6GB of RAM?! What's going on here ? (open filehandles, sorted by bytes): ``` 1 157191688 gnome-sof 750448 beadon 11u netlink 0t0 ROUTE 2 103546882 gnome-sof 750448 beadon DEL REG 259,2 /usr/share/icons/hicolor/icon-theme.cache 3 103022860 gnome-sof 750448 beadon DEL REG 259,2 /usr/share/glib-2.0/schemas/gschemas.compiled 4 61210892 gnome-sof 750448 beadon DEL REG 259,2 /var/lib/flatpak/exports/share/icons/hicolor/icon-theme.cache 5 60828700 gnome-sof 750448 beadon DEL REG 259,2 /var/cache/fontconfig/2bd0278d-49c2-4c8c-9eea-32d695b22756-le64.cache-7 6 30430848 gnome-sof 750448 beadon mem REG 259,2 101455545 /usr/lib/x86_64-linux-gnu/libicudata.so.71.1 7 14516125 gnome-sof 750448 beadon mem REG 259,2 97416011 /home/beadon/.cache/gnome-software/flatpak-system-default/components.xmlb 8 11308392 gnome-sof 750448 beadon mem REG 259,2 101450031 /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0 9 8254320 gnome-sof 750448 beadon mem REG 259,2 101450280 /usr/lib/x86_64-linux-gnu/libgtk-4.so.1.800.1 10 7599984 gnome-sof 750448 beadon 475u REG 259,2 60821438 /var/tmp/#60821438 (deleted) 11 7582821 gnome-sof 750448 beadon 476u REG 259,2 60821485 /var/tmp/#60821485 (deleted) 12 6733824 gnome-sof 750448 beadon 478u REG 259,2 60821699 /var/tmp/#60821699 (deleted) 13 5966212 gnome-sof 750448 beadon mem REG 259,2 97419097 /home/beadon/.cache/gnome-software/appstream/components.xmlb 14 5712208 gnome-sof 750448 beadon mem REG 259,2 101450114 /usr/lib/locale/locale-archive 15 5681431 gnome-sof 750448 beadon 477u REG 259,2 60821584 /var/tmp/#60821584 (deleted) 16 5469177 gnome-sof 750448 beadon 482u REG 259,2 60817847 /var/tmp/#60817847 (deleted) 17 5406720 gnome-sof 750448 beadon 479u REG 259,2 60821593 /var/tmp/#60821593 (deleted) 18 5341166 gnome-sof 750448 beadon 493u REG 259,2 60821670 /var/tmp/#60821670 (deleted) 19 4616704 gnome-sof 750448 beadon 206u REG 259,2 60819152 /var/tmp/#60819152 (deleted) 20 4519958 gnome-sof 750448 beadon 497u REG 259,2 60821824 /var/tmp/#60821824 (deleted) ``` Details: [sorted-report.txt](/uploads/43c17fb8547366c33c3e49931a5a07b7/sorted-report.txt) ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 5 20:06:15 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/525.78.01, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (27 days ago) InstallationMedia: Ubuntu 22
[Desktop-packages] [Bug 2006070] Re: incredibly high memory usage
process has since been killed -- however I hav statistics posted here : https://gitlab.gnome.org/GNOME/gnome-software/-/issues/2064 Additional files and memory usage from LSOF report attached. ** Attachment added: "ramusage.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2006070/+attachment/5645005/+files/ramusage.txt -- 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/2006070 Title: incredibly high memory usage Status in X.Org X server: Unknown Status in xorg package in Ubuntu: New Bug description: Please describe the issue you’re experiencing: gnome-software is consuming 6+ GB of RAM on my machine. This is unacceptable and is affecting all other applications. Error message appearing in /var/log/syslog N/A -- other processes are fighting for memory, and OOM killer is more active. What Linux distribution are you using, and what kind of package (RPM, deb, flatpak, etc.) are you experiencing the problem with? Ubuntu 22.10 apt flatpak I don't know how to replicate this issue, however it does appear to be a problem retaining memory. See LSOF report below, software is gnome-software 43.0 ``` sudo lsof -p 750448 -n > ~/ramusage.txt cat ramusage.txt | perl -lane 'print "$F[6] $F[0] $F[1] $F[2] $F[3] $F[4] $F[5] $F[7] $F[8] $F[9] $F[10]"' | sort -rn > sorted-report.txt ``` Top 10 filehandles are holding onto something like 6GB of RAM?! What's going on here ? (open filehandles, sorted by bytes): ``` 1 157191688 gnome-sof 750448 beadon 11u netlink 0t0 ROUTE 2 103546882 gnome-sof 750448 beadon DEL REG 259,2 /usr/share/icons/hicolor/icon-theme.cache 3 103022860 gnome-sof 750448 beadon DEL REG 259,2 /usr/share/glib-2.0/schemas/gschemas.compiled 4 61210892 gnome-sof 750448 beadon DEL REG 259,2 /var/lib/flatpak/exports/share/icons/hicolor/icon-theme.cache 5 60828700 gnome-sof 750448 beadon DEL REG 259,2 /var/cache/fontconfig/2bd0278d-49c2-4c8c-9eea-32d695b22756-le64.cache-7 6 30430848 gnome-sof 750448 beadon mem REG 259,2 101455545 /usr/lib/x86_64-linux-gnu/libicudata.so.71.1 7 14516125 gnome-sof 750448 beadon mem REG 259,2 97416011 /home/beadon/.cache/gnome-software/flatpak-system-default/components.xmlb 8 11308392 gnome-sof 750448 beadon mem REG 259,2 101450031 /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0 9 8254320 gnome-sof 750448 beadon mem REG 259,2 101450280 /usr/lib/x86_64-linux-gnu/libgtk-4.so.1.800.1 10 7599984 gnome-sof 750448 beadon 475u REG 259,2 60821438 /var/tmp/#60821438 (deleted) 11 7582821 gnome-sof 750448 beadon 476u REG 259,2 60821485 /var/tmp/#60821485 (deleted) 12 6733824 gnome-sof 750448 beadon 478u REG 259,2 60821699 /var/tmp/#60821699 (deleted) 13 5966212 gnome-sof 750448 beadon mem REG 259,2 97419097 /home/beadon/.cache/gnome-software/appstream/components.xmlb 14 5712208 gnome-sof 750448 beadon mem REG 259,2 101450114 /usr/lib/locale/locale-archive 15 5681431 gnome-sof 750448 beadon 477u REG 259,2 60821584 /var/tmp/#60821584 (deleted) 16 5469177 gnome-sof 750448 beadon 482u REG 259,2 60817847 /var/tmp/#60817847 (deleted) 17 5406720 gnome-sof 750448 beadon 479u REG 259,2 60821593 /var/tmp/#60821593 (deleted) 18 5341166 gnome-sof 750448 beadon 493u REG 259,2 60821670 /var/tmp/#60821670 (deleted) 19 4616704 gnome-sof 750448 beadon 206u REG 259,2 60819152 /var/tmp/#60819152 (deleted) 20 4519958 gnome-sof 750448 beadon 497u REG 259,2 60821824 /var/tmp/#60821824 (deleted) ``` Details: [sorted-report.txt](/uploads/43c17fb8547366c33c3e49931a5a07b7/sorted-report.txt) ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 5 20:06:15 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/525.78.01, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (27 days ago) InstallationMed
[Desktop-packages] [Bug 2006070] [NEW] incredibly high memory usage
Public bug reported: Please describe the issue you’re experiencing: gnome-software is consuming 6+ GB of RAM on my machine. This is unacceptable and is affecting all other applications. Error message appearing in /var/log/syslog N/A -- other processes are fighting for memory, and OOM killer is more active. What Linux distribution are you using, and what kind of package (RPM, deb, flatpak, etc.) are you experiencing the problem with? Ubuntu 22.10 apt flatpak I don't know how to replicate this issue, however it does appear to be a problem retaining memory. See LSOF report below, software is gnome-software 43.0 ``` sudo lsof -p 750448 -n > ~/ramusage.txt cat ramusage.txt | perl -lane 'print "$F[6] $F[0] $F[1] $F[2] $F[3] $F[4] $F[5] $F[7] $F[8] $F[9] $F[10]"' | sort -rn > sorted-report.txt ``` Top 10 filehandles are holding onto something like 6GB of RAM?! What's going on here ? (open filehandles, sorted by bytes): ``` 1 157191688 gnome-sof 750448 beadon 11u netlink 0t0 ROUTE 2 103546882 gnome-sof 750448 beadon DEL REG 259,2 /usr/share/icons/hicolor/icon-theme.cache 3 103022860 gnome-sof 750448 beadon DEL REG 259,2 /usr/share/glib-2.0/schemas/gschemas.compiled 4 61210892 gnome-sof 750448 beadon DEL REG 259,2 /var/lib/flatpak/exports/share/icons/hicolor/icon-theme.cache 5 60828700 gnome-sof 750448 beadon DEL REG 259,2 /var/cache/fontconfig/2bd0278d-49c2-4c8c-9eea-32d695b22756-le64.cache-7 6 30430848 gnome-sof 750448 beadon mem REG 259,2 101455545 /usr/lib/x86_64-linux-gnu/libicudata.so.71.1 7 14516125 gnome-sof 750448 beadon mem REG 259,2 97416011 /home/beadon/.cache/gnome-software/flatpak-system-default/components.xmlb 8 11308392 gnome-sof 750448 beadon mem REG 259,2 101450031 /usr/lib/x86_64-linux-gnu/librsvg-2.so.2.48.0 9 8254320 gnome-sof 750448 beadon mem REG 259,2 101450280 /usr/lib/x86_64-linux-gnu/libgtk-4.so.1.800.1 10 7599984 gnome-sof 750448 beadon 475u REG 259,2 60821438 /var/tmp/#60821438 (deleted) 11 7582821 gnome-sof 750448 beadon 476u REG 259,2 60821485 /var/tmp/#60821485 (deleted) 12 6733824 gnome-sof 750448 beadon 478u REG 259,2 60821699 /var/tmp/#60821699 (deleted) 13 5966212 gnome-sof 750448 beadon mem REG 259,2 97419097 /home/beadon/.cache/gnome-software/appstream/components.xmlb 14 5712208 gnome-sof 750448 beadon mem REG 259,2 101450114 /usr/lib/locale/locale-archive 15 5681431 gnome-sof 750448 beadon 477u REG 259,2 60821584 /var/tmp/#60821584 (deleted) 16 5469177 gnome-sof 750448 beadon 482u REG 259,2 60817847 /var/tmp/#60817847 (deleted) 17 5406720 gnome-sof 750448 beadon 479u REG 259,2 60821593 /var/tmp/#60821593 (deleted) 18 5341166 gnome-sof 750448 beadon 493u REG 259,2 60821670 /var/tmp/#60821670 (deleted) 19 4616704 gnome-sof 750448 beadon 206u REG 259,2 60819152 /var/tmp/#60819152 (deleted) 20 4519958 gnome-sof 750448 beadon 497u REG 259,2 60821824 /var/tmp/#60821824 (deleted) ``` Details: [sorted-report.txt](/uploads/43c17fb8547366c33c3e49931a5a07b7/sorted-report.txt) ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Feb 5 20:06:15 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/525.78.01, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (27 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-01-15 (21 days ago) dmi.bios.date: 12/05/2022 dmi.bios.release: 1.58 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET82W (1.58 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO
[Desktop-packages] [Bug 2003790] [NEW] After successful pairing new bluetooth headphones + mix - sound crash
Public bug reported: Bluetooth pairing reports established using bluetoothctl, but the sound device is not available on the Ubuntu device(?settings) manager. Only the existing speakers (non buetooth) are showing as sound outputs (sinks). Bluetooth data: beadon@semiauto:~$ bluetoothctl Agent registered [CHG] Controller 28:DF:EB:B6:9B:66 Pairable: yes [Shure TW1]# show Controller 28:DF:EB:B6:9B:66 (public) Name: semiauto Alias: semiauto Class: 0x007c Powered: yes Discoverable: no DiscoverableTimeout: 0x00b4 Pairable: yes UUID: Message Notification Se.. (1133--1000-8000-00805f9b34fb) UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb) UUID: OBEX Object Push (1105--1000-8000-00805f9b34fb) UUID: Message Access Server (1132--1000-8000-00805f9b34fb) UUID: PnP Information (1200--1000-8000-00805f9b34fb) UUID: IrMC Sync (1104--1000-8000-00805f9b34fb) UUID: Vendor specific (5005--1000-8000-0002ee01) UUID: Headset (1108--1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb) UUID: Phonebook Access Server (112f--1000-8000-00805f9b34fb) UUID: Audio Sink(110b--1000-8000-00805f9b34fb) UUID: Device Information(180a--1000-8000-00805f9b34fb) UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb) UUID: Handsfree Audio Gateway (111f--1000-8000-00805f9b34fb) UUID: Audio Source (110a--1000-8000-00805f9b34fb) UUID: OBEX File Transfer(1106--1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0541 Discovering: no Roles: central Roles: peripheral Advertising Features: ActiveInstances: 0x00 (0) SupportedInstances: 0x0c (12) SupportedIncludes: tx-power SupportedIncludes: appearance SupportedIncludes: local-name SupportedSecondaryChannels: 1M SupportedSecondaryChannels: 2M SupportedSecondaryChannels: Coded Headphones: disable bluetooth, enable bluetooth, attempt connection. Bluetooth device is connected to another device (Android phone). Expected behavior is to disconnect the existing connection to the phone and pair only with the laptop. an 24 09:31:07 semiauto systemd[1]: Stopped target Bluetooth Support. Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/sbc_xq Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/aptx_ll_1 Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/aptx_ll_0 Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1 Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0 Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/faststream Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/faststream_duplex Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSink/opus_05 Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/opus_05 Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/opus_05_51 Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/opus_05_71 Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSink/opus_05_duplex Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/opus_05_duplex Jan 24 09:31:07 semiauto bluetoothd[868]: Endpoint unregistered: sender=:1.111 path=/MediaEndpoint/A2DPSource/opus_05_pro Jan 24 09:31:07 semiauto systemd[1]: Started Load/Save RF Kill Switch Status. Jan 24 09:31:12 semiauto systemd[1]: systemd-rfkill.service: Deactivated successfully. Jan 24 09:31:20 semiauto systemd[1]: Starting Load/Save RF Kill Switch Status... Jan 24 09:31:20 semiauto systemd[1]: Started Load/Save RF Kill Switch Status. Jan 24 09:31:20 semiauto kernel: [66926.266001] usb 3-10: new full-speed USB device number 15 using xhci_hcd Jan 24 09:31:20 semiauto kernel: [66926.416144] usb 3-10: New USB device found, idVendor=8087, idProduct=0026, bcdDevice= 0.02 Jan 24 09:31:20 semiauto
[Desktop-packages] [Bug 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"
I have blacklisted this now using: sudo vim /etc/modprobe.d/blacklist-nouveau.conf adding: blacklist nouveau options nouveau modeset=0 -- 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/2003031 Title: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7" Status in Linux: Unknown Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: GJS crashes - here's the crashdump. I saw the crash occur after a screensaver had been running, and the screens had gone blank. I assume this means they were turned off by the sleep timer. When I worke the machine, I was presented with a prompt, I *quickly* entered my login credentials and momentarily saw the desktop and all open programs on it. Then, the screens (3) flickered and I saw the login prompt again. I logged in (again), and all applications had been shut down. I checked /var/log/syslog and saw the following details -- see (log). Uploaded file, and the crashdump. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:52:55 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago) dmi.bios.date: 07/27/2022 dmi.bios.release: 1.55 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET79W (1.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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/linux/+bug/2003031/+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 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"
Should I open this as a different issue with the Core X Chroma Thunderbolt 3 enclosure ? It's very similar. -- 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/2003031 Title: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7" Status in Linux: Unknown Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: GJS crashes - here's the crashdump. I saw the crash occur after a screensaver had been running, and the screens had gone blank. I assume this means they were turned off by the sleep timer. When I worke the machine, I was presented with a prompt, I *quickly* entered my login credentials and momentarily saw the desktop and all open programs on it. Then, the screens (3) flickered and I saw the login prompt again. I logged in (again), and all applications had been shut down. I checked /var/log/syslog and saw the following details -- see (log). Uploaded file, and the crashdump. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:52:55 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago) dmi.bios.date: 07/27/2022 dmi.bios.release: 1.55 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET79W (1.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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/linux/+bug/2003031/+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 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"
Ok, I am getting a slightly different, but perhaps related problem with another USB-C / eGPU encapsulation (PCIE tunneles over USB-C basically) device. I've done some testing with the Razer Core X Chroma, a USB-C connected Thunderbolt 3 eGPU enclosure. Reference to hardware is here : https://www.razer.com/gaming-egpus/Razer-Core-X/RC21-01430100-R3U1 I have 2x displays now connected to the internal PCIE nVidia TU117 [GeForce GTX 1650] loaded in the unit. The BIOS seems to work fine, , but when I get to the gnome login screen things hang. I am narrowing it down, but just like the display blanking on the Intel based on cursor location, I am seeing the same behavior with this enclosure - if at boot time the enclosure is connected, then the displays will lock up. If, I move the mouse to the right edge of the screen , the desktop will also lock up. Attached are the logs of the attachment, then detachment of this enclosure. Note that on re-attaching the enclosure the USB devices which previously worked fine attached to the enclosure no longer function (perhaps not deregistered properly?). Details for HW info beadon@semiauto:~$ hwinfo --gfxcard --short graphics card: nVidia TU117 [GeForce GTX 1650] Intel TigerLake-LP GT2 [Iris Xe Graphics] Primary display adapter: #26 ** Attachment added: "log-for-chroma.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2003031/+attachment/5642118/+files/log-for-chroma.txt -- 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/2003031 Title: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7" Status in Linux: Unknown Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: GJS crashes - here's the crashdump. I saw the crash occur after a screensaver had been running, and the screens had gone blank. I assume this means they were turned off by the sleep timer. When I worke the machine, I was presented with a prompt, I *quickly* entered my login credentials and momentarily saw the desktop and all open programs on it. Then, the screens (3) flickered and I saw the login prompt again. I logged in (again), and all applications had been shut down. I checked /var/log/syslog and saw the following details -- see (log). Uploaded file, and the crashdump. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:52:55 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago) dmi.bios.date: 07/27/2022 dmi.bios.release: 1.55 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET79W (1.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:c
[Desktop-packages] [Bug 2003136] Re: video corruption when using gnome-display settings
attached file. Timeout was received for the file upload. Attaching a vimeo link instead. https://vimeo.com/790229569 ** Attachment added: "PXL_20230117_224753761.mp4" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2003136/+attachment/5642093/+files/PXL_20230117_224753761.mp4 -- 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/2003136 Title: video corruption when using gnome-display settings Status in xorg package in Ubuntu: New Bug description: I might need help routing this to the correct project. gnome-display-properties I believe is the application in foreground. I was using it normally, then switched the screen resolution scale to 100% (down from 200%). I had a Chrome window open which now had the inner icons shrunk, but not the boundaries of the window. So I moved the chrome window around, and noticed this corruption / tearing. The video is interesting because I believe it is telling us that the boundaries of the window are not (re?)set properly for the gnome- display-properties when display scale is applied. Is this what you see in the video too ? ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..52.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 470.161.03 Wed Oct 19 00:10:36 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 17:49:57 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. TU117 [GeForce GTX 1650] [3842:1257] InstallationDate: Installed on 2023-01-09 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-01-15 (2 days ago) dmi.bios.date: 12/05/2022 dmi.bios.release: 1.58 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET82W (1.58 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET82W(1.58):bd12/05/2022:br1.58:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouve
[Desktop-packages] [Bug 1870597] Re: libinput says "your system is too slow"
I am seeing this issue in Ubuntu 22.10 , specifically for a Razer Deathadder mouse : Jan 17 17:59:28 semiauto /usr/libexec/gdm-x-session[2147]: (EE) event20 - Razer Razer DeathAdder: client bug: event processing lagging behind by 24ms, your system is too slow Which information do you need to troubleshoot further ? -- 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/1870597 Title: libinput says "your system is too slow" Status in GNOME Shell: Fix Released Status in libinput: Fix Released Status in Linux: Confirmed Status in libinput package in Ubuntu: Fix Committed Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Status in xorg-server package in Ubuntu: Confirmed Bug description: During the freeze, the output of the install had a message from "gdm- x-session" saying "your system is too slow". To reproduce: 1. Launch the Ubuntu installer 2. Begin the installation process 3. When the installation process begins, move the cursor around 4. Notice how the PC freezes and drops mouse events Description: Ubuntu Focal Fossa (development branch) Release: 20.04 gnome-shell: Installed: 3.36.0-2ubuntu2 Candidate: 3.36.0-2ubuntu2 Version table: *** 3.36.0-2ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CasperVersion: 1.442 Date: Fri Apr 3 14:24:21 2020 DisplayManager: gdm3 GsettingsChanges: LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1870597/+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 2003136] [NEW] video corruption when using gnome-display settings
Public bug reported: I might need help routing this to the correct project. gnome-display-properties I believe is the application in foreground. I was using it normally, then switched the screen resolution scale to 100% (down from 200%). I had a Chrome window open which now had the inner icons shrunk, but not the boundaries of the window. So I moved the chrome window around, and noticed this corruption / tearing. The video is interesting because I believe it is telling us that the boundaries of the window are not (re?)set properly for the gnome- display-properties when display scale is applied. Is this what you see in the video too ? ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..52.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 470.161.03 Wed Oct 19 00:10:36 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 17 17:49:57 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. TU117 [GeForce GTX 1650] [3842:1257] InstallationDate: Installed on 2023-01-09 (8 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2023-01-15 (2 days ago) dmi.bios.date: 12/05/2022 dmi.bios.release: 1.58 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET82W (1.58 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET82W(1.58):bd12/05/2022:br1.58:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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 corruption kinetic 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/2003136 Title: video corruption when using gnome-display settings Status in xorg package in Ubuntu: New Bug description: I might need help routing this to the correct project. gnome-display-properties I believe is the application in foreground. I was using it normally, then switched the screen resolution scale to 100% (down from 200%). I had a Chrome window open which now had the inner icons shru
[Desktop-packages] [Bug 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"
I have applied the workaround for mutter : MUTTER_DEBUG_FORCE_KMS_MODE=simple I am seeing no further logs at the moment. I will continue to monitor for issues. To address any low-level issues I also have applied the system firmware update, available via ISO from the Lenovo support site "n32ur20w.iso". the release date on this was Jan 02 , 2023, so only about 2 weeks ago. I expect the issue to re-occur. Reference for anyone following along at home : https://pcsupport.lenovo.com/us/en/products/laptops-and- netbooks/thinkpad-x-series-laptops/thinkpad-x1-yoga-6th-gen- type-20xy-20y0/20xy/20xy0027us/downloads/driver- list/component?name=BIOS%2FUEFI Release notes for this firmware update included here too : ** Attachment added: "n32ur20w.txt" https://bugs.launchpad.net/linux/+bug/2003031/+attachment/5642055/+files/n32ur20w.txt -- 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/2003031 Title: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7" Status in Linux: Unknown Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: GJS crashes - here's the crashdump. I saw the crash occur after a screensaver had been running, and the screens had gone blank. I assume this means they were turned off by the sleep timer. When I worke the machine, I was presented with a prompt, I *quickly* entered my login credentials and momentarily saw the desktop and all open programs on it. Then, the screens (3) flickered and I saw the login prompt again. I logged in (again), and all applications had been shut down. I checked /var/log/syslog and saw the following details -- see (log). Uploaded file, and the crashdump. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:52:55 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago) dmi.bios.date: 07/27/2022 dmi.bios.release: 1.55 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET79W (1.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nou
[Desktop-packages] [Bug 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"
Yes, there is a USB-C "port extender" (dock) attached to this Lenovo laptop. The model is the MUC-0501B. It is this exact device : https://amzn.to/3XA5u5N -- "USB C Adapters for MacBook Pro/Air,Mac Dongle with 3 USB Port,USB C to HDMI, USB C to RJ45 Ethernet,MOKiN 9 in 1 USB C to HDMI Adapter,100W Pd Charging, USB C to SD/TF Card Reader USB C Hub". I also have noticed occassional flickering. What's interesting is that either the display controlled via this, or via the direct HDMI port will "drop out" for a second or 2 when the mouse moves between the screens. If I move the mouse back to the alternate screen, the display comes back. ** Attachment added: "video of a related(?) problem." https://bugs.launchpad.net/linux/+bug/2003031/+attachment/5642054/+files/PXL_20230117_204102229.mp4 -- 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/2003031 Title: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7" Status in Linux: Unknown Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: GJS crashes - here's the crashdump. I saw the crash occur after a screensaver had been running, and the screens had gone blank. I assume this means they were turned off by the sleep timer. When I worke the machine, I was presented with a prompt, I *quickly* entered my login credentials and momentarily saw the desktop and all open programs on it. Then, the screens (3) flickered and I saw the login prompt again. I logged in (again), and all applications had been shut down. I checked /var/log/syslog and saw the following details -- see (log). Uploaded file, and the crashdump. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:52:55 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago) dmi.bios.date: 07/27/2022 dmi.bios.release: 1.55 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET79W (1.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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-
[Desktop-packages] [Bug 2003031] Re: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7"
Spelling error : "When I woke the machine..." -- 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/2003031 Title: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7" Status in Linux: Unknown Status in linux package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: GJS crashes - here's the crashdump. I saw the crash occur after a screensaver had been running, and the screens had gone blank. I assume this means they were turned off by the sleep timer. When I worke the machine, I was presented with a prompt, I *quickly* entered my login credentials and momentarily saw the desktop and all open programs on it. Then, the screens (3) flickered and I saw the login prompt again. I logged in (again), and all applications had been shut down. I checked /var/log/syslog and saw the following details -- see (log). Uploaded file, and the crashdump. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:52:55 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago) dmi.bios.date: 07/27/2022 dmi.bios.release: 1.55 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET79W (1.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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/linux/+bug/2003031/+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 2003031] [NEW] gjs crash crashes gnome session
Public bug reported: GJS crashes - here's the crashdump. I saw the crash occur after a screensaver had been running, and the screens had gone blank. I assume this means they were turned off by the sleep timer. When I worke the machine, I was presented with a prompt, I *quickly* entered my login credentials and momentarily saw the desktop and all open programs on it. Then, the screens (3) flickered and I saw the login prompt again. I logged in (again), and all applications had been shut down. I checked /var/log/syslog and saw the following details -- see (log). Uploaded file, and the crashdump. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:52:55 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago) dmi.bios.date: 07/27/2022 dmi.bios.release: 1.55 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET79W (1.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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 crash kinetic third-party-packages ubuntu wayland-session ** Attachment added: "this is the crashdump for this bug report, 'log' is the syslog details at the same time." https://bugs.launchpad.net/bugs/2003031/+attachment/5641786/+files/gjs-crash-report.tar.gz -- 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/2003031 Title: gjs crash crashes gnome session Status in xorg package in Ubuntu: New Bug description: GJS crashes - here's the crashdump. I saw the crash occur after a screensaver had been running, and the screens had gone blank. I assume this means they were turned off by the sleep timer. When I worke the machine, I was presented with a prompt, I *quickly* entered my login credentials and momentarily saw the desktop and all open programs on it. Then, the screens (3) flickered and I saw the login prompt again. I logged in (again), and all applications had been shut down. I checked /var/log/syslog and saw the following details -- see (log). Uploaded file, and the crashdump. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Unam
