[Desktop-packages] [Bug 2064213] [NEW] Release BlueZ 5.75 to Oracular
Public bug reported: Release BlueZ 5.75 to Oracular: https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.75.tar.xz ** Affects: bluez (Ubuntu) Importance: Medium Assignee: Daniel van Vugt (vanvugt) Status: Triaged ** Tags: oracular ** Changed in: bluez (Ubuntu) Milestone: None => ubuntu-24.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2064213 Title: Release BlueZ 5.75 to Oracular Status in bluez package in Ubuntu: Triaged Bug description: Release BlueZ 5.75 to Oracular: https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.75.tar.xz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2064213/+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 2037015] Re: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install
Here's the fix for Oracular. ** Changed in: mesa (Ubuntu) Status: Confirmed => Won't Fix ** Patch added: "webkit2gtk_2.44.0-2ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2037015/+attachment/5772919/+files/webkit2gtk_2.44.0-2ubuntu1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037015 Title: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install Status in Webkit: Confirmed Status in mesa package in Ubuntu: Won't Fix Status in webkit2gtk package in Ubuntu: In Progress Bug description: [ Impact ] Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install. [ Test Plan ] 1. Log into a Xorg session on a Raspberry Pi 4/400. 2. Open the default Help app by clicking the question mark icon in the dock or by running 'yelp'. 3. Verify it didn't crash and the window contents are not corrupt. [ Where problems could occur ] The fix is limited to webkit2gtk so can only affect apps such as yelp or the Raspberry Pi installer. [ Other Info ] During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2037015/+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 2062146] Re: Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile
** Changed in: mesa (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2062146 Title: Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile Status in Mesa: New Status in mesa package in Ubuntu: Won't Fix Status in webkit2gtk package in Ubuntu: In Progress Bug description: MiniBrowser crashed immediately on Raspberry Pi 400. ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: libwebkit2gtk-4.1-0 2.44.0-2 ProcVersionSignature: Ubuntu 6.8.0-1002.2-raspi 6.8.1 Uname: Linux 6.8.0-1002-raspi aarch64 ApportVersion: 2.28.0-0ubuntu1 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 17:32:12 2024 ExecutablePath: /usr/lib/aarch64-linux-gnu/webkit2gtk-4.1/MiniBrowser JournalErrors: -- No entries -- ProcCmdline: ./MiniBrowser ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= Signal: 11 SignalName: SIGSEGV SourcePackage: webkit2gtk StacktraceTop: ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /lib/aarch64-linux-gnu/libgbm.so.1 ?? () from /lib/aarch64-linux-gnu/libwebkit2gtk-4.1.so.0 Title: MiniBrowser crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2062146/+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 2064099] Re: Quickly switching right and left clicks freezes Nautilus
** Changed in: mutter (Ubuntu) Status: Incomplete => New ** Changed in: nautilus (Ubuntu) Status: Incomplete => New -- 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/2064099 Title: Quickly switching right and left clicks freezes Nautilus Status in mutter package in Ubuntu: New Status in nautilus package in Ubuntu: New Bug description: 1. Open Nautilus. 2. Try to right click and left click randomly and quickly. This behavior will freeze Nautilus until you must kill it and it happens every time you do this, and you cannot even move it's window. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 12:42:46 2024 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small-plus'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' InstallationDate: Installed on 2024-03-22 (38 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: nautilus UpgradeStatus: Upgraded to noble on 2024-04-11 (18 days ago) usr_lib_nautilus: file-roller 44.1-1 nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2064099/+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 2064205] [NEW] Optimize cross-GPU multi-monitor syncs
Public bug reported: Optimize cross-GPU multi-monitor syncs still slowing down Nvidia secondary GPUs on Wayland per: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3304#note_1860864 ** Affects: mutter (Ubuntu) Importance: Wishlist Assignee: Daniel van Vugt (vanvugt) Status: Triaged ** Tags: hybrid multigpu multimonitor nvidia nvidia-wayland performance wayland wayland-session ** Tags added: nvidia-wayland ** Changed in: mutter (Ubuntu) Milestone: None => ubuntu-24.10 -- 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/2064205 Title: Optimize cross-GPU multi-monitor syncs Status in mutter package in Ubuntu: Triaged Bug description: Optimize cross-GPU multi-monitor syncs still slowing down Nvidia secondary GPUs on Wayland per: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3304#note_1860864 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2064205/+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 2064196] Re: Can't change display position to "right of"
The xrandr output looks correct but the attached MonitorsUser.xml.txt looks suspicious in that it confirms the monitors don't have any separate positional information. If deleting monitors.xml didn't work then next please try: 1. sudo rm /dev/dri/card0 # (should be the "Unknown Display") 2. rm ~/.config/monitors.xml 3. Log in again. If that works then the issue is just bug 2060268. And unfortunately deleting /dev/dri/card0 will only last until the next reboot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2064196 Title: Can't change display position to "right of" Status in gnome-control-center package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Bug description: I have two monitors (Iiyama and Philips). In 22.04 I had two separate pulpits on each monitors. Currently in "Settings -> Displays" I can set it to "duplicate" or "joined". joined option is inconvenient because, every window I open is by default in the center of the gap between two monitors. I'am able to change it manually via nvidia-settings but it isn't persistent. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.239.06 Sat Feb 3 06:03:07 UTC 2024 GCC version: ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 08:05:32 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GK106 [GeForce GTX 660] [1458:354e] InstallationDate: Installed on 2024-04-28 (2 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: MSI MS-7758 ProcEnviron: LANG=pl_PL.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=e678c4a6-a42f-4ef2-a6c8-9187e5d5ab0a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.13:bd03/07/2014:br4.6:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7758 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2064196/+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 2052913] Re: [Xorg] Large performance regression in fullscreen windows
** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu) Status: Confirmed => Triaged -- 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/2052913 Title: [Xorg] Large performance regression in fullscreen windows Status in Mutter: New Status in mutter package in Ubuntu: Triaged Bug description: Test system: ARM64 Ubuntu Jammy (gnome-shell 42.9-0ubuntu2) and Ubuntu Noble (gnome-shell 45.3-1ubuntu1) Default Ubuntu GNOME desktop environment used with no user added extensions. GPU driverstack identical between the two distros (eliminated as a variable). Linux kernel identical between distros (eliminated as a variable) CPU, GPU, and RAM clocks pinned to max. Test case: Minecraft Java Edition (shared drive with identical setup between Ubuntu versions). Fullscreen 1080p. Xorg display server. FPS (uncapped): Ubuntu Jammy: 177fps Ubuntu Noble: 140fps Observations: Ubuntu Jammy: gnome-shell process cpu% when camera is still: 0-1% gnome-shell process cpu% when camera is moving: 10-20% Memory Bandwidth (CPU and GPU shared): 40% Ubuntu Noble: gnome-shell process cpu% when camera is still: 20-55% gnome-shell process cpu% when camera is moving: 30-55% Memory Bandwidth (CPU and GPU shared): 50% In both cases GPU utilization is observed to be near 100%. So in summary, large performance regression regression which appears to be due to gnome-shell. There is nearly no gnome-shell cpu% usage on ubuntu jammy when there the camera is still (even with a fps graph drawn onscreen) in stark contrast to ubuntu noble. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2052913/+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 2064196] Re: Can't change display position to "right of"
Did you log in again after deleting the file? Is one of the two different names "Unknown Display"? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2064196 Title: Can't change display position to "right of" Status in gnome-control-center package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Bug description: I have two monitors (Iiyama and Philips). In 22.04 I had two separate pulpits on each monitors. Currently in "Settings -> Displays" I can set it to "duplicate" or "joined". joined option is inconvenient because, every window I open is by default in the center of the gap between two monitors. I'am able to change it manually via nvidia-settings but it isn't persistent. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.239.06 Sat Feb 3 06:03:07 UTC 2024 GCC version: ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 08:05:32 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GK106 [GeForce GTX 660] [1458:354e] InstallationDate: Installed on 2024-04-28 (2 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: MSI MS-7758 ProcEnviron: LANG=pl_PL.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=e678c4a6-a42f-4ef2-a6c8-9187e5d5ab0a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.13:bd03/07/2014:br4.6:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7758 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2064196/+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 2038801] Re: Secondary GPU frame rates are held back by dynamic-max-render-time
** Description changed: + [ Impact ] + Secondary GPU frame rates are held back by dynamic-max-render-time as shown on this amdgpu setup connected to a 60 Hz monitor: main: 30 FPS main + CLUTTER_PAINT=disable-dynamic-max-render-time: 60 FPS https://gitlab.gnome.org/GNOME/mutter/-/issues/3070 + + [ Test Plan ] + + This is imprecise because many machines won't exhibit a measurable + difference... + + 1. Set up a dual GPU machine with dual monitors using an open source + driver such as amdgpu or nouveau. If you are using Mutter 46 or later + then the closed source Nvidia driver may also be used in theory. + + 2. In a Wayland session, check that the frame rate being achieved on the + monitor connected to the secondary GPU is at least that of the refresh + rate. + + 3. Add CLUTTER_PAINT=disable-dynamic-max-render-time to /etc/environment + and reboot. + + 4. In a Wayland session, check that the frame rate on the monitor + connected to the secondary GPU has not changed (didn't get better) after + the environment change. + + 5. Remove the change from /etc/environment. + + [ Where problems could occur ] + + Anywhere in frame scheduling and frame rate performance, since that is + what changed. + + [ Other Info ] -- 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/2038801 Title: Secondary GPU frame rates are held back by dynamic-max-render-time Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Bug description: [ Impact ] Secondary GPU frame rates are held back by dynamic-max-render-time as shown on this amdgpu setup connected to a 60 Hz monitor: main: 30 FPS main + CLUTTER_PAINT=disable-dynamic-max-render-time: 60 FPS https://gitlab.gnome.org/GNOME/mutter/-/issues/3070 [ Test Plan ] This is imprecise because many machines won't exhibit a measurable difference... 1. Set up a dual GPU machine with dual monitors using an open source driver such as amdgpu or nouveau. If you are using Mutter 46 or later then the closed source Nvidia driver may also be used in theory. 2. In a Wayland session, check that the frame rate being achieved on the monitor connected to the secondary GPU is at least that of the refresh rate. 3. Add CLUTTER_PAINT=disable-dynamic-max-render-time to /etc/environment and reboot. 4. In a Wayland session, check that the frame rate on the monitor connected to the secondary GPU has not changed (didn't get better) after the environment change. 5. Remove the change from /etc/environment. [ Where problems could occur ] Anywhere in frame scheduling and frame rate performance, since that is what changed. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2038801/+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 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)
** Description changed: + [ Impact ] + + GNOME Wayland session crashes with + libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: + assertion failed: (logical_monitor) + + [ Test Plan ] + + This needs more detail and community help... + + 1. On a machine that was previously affected by the crash, disconnect + the HDMI cable. + + Expect: The shell has not crashed and continues to function. + + [ Where problems could occur ] + + Potentially anywhere in Gnome Shell. Judging by the fix it relates to + automatic window placement when monitors are added and removed. + + [ Original description ] + I am observing multiple issues with external monitor in a hybrid system (laptop) with Intel GPU and NVIDIA GPU in a Gnome session: - Disconnecting HDMI cable crashes the desktop to login screen The HDMI port is connected to NVIDIA. I use the latest updates and drivers of 22.04 LTS. I am not sure how to auto-report this with ubuntu-bug. The system is similar to this report: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291 -- 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/2050865 Title: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) Status in Gnome Shell Extension Tiling Assistant: New Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Bug description: [ Impact ] GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) [ Test Plan ] This needs more detail and community help... 1. On a machine that was previously affected by the crash, disconnect the HDMI cable. Expect: The shell has not crashed and continues to function. [ Where problems could occur ] Potentially anywhere in Gnome Shell. Judging by the fix it relates to automatic window placement when monitors are added and removed. [ Original description ] I am observing multiple issues with external monitor in a hybrid system (laptop) with Intel GPU and NVIDIA GPU in a Gnome session: - Disconnecting HDMI cable crashes the desktop to login screen The HDMI port is connected to NVIDIA. I use the latest updates and drivers of 22.04 LTS. I am not sure how to auto-report this with ubuntu-bug. The system is similar to this report: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-tiling-assistant/+bug/2050865/+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 2039543] Re: Miss placed Hexchat icon when switching workspaces
Fixed in https://gitlab.gnome.org/GNOME/gnome- shell/-/merge_requests/3285 ** Tags added: fixed-in-gnome-shell-46.2 fixed-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2039543 Title: Miss placed Hexchat icon when switching workspaces Status in Ubuntu AppIndicators: New Status in gnome-shell package in Ubuntu: Fix Committed Status in gnome-shell-extension-appindicator package in Ubuntu: Won't Fix Bug description: While switching workspaces, Hexchat icon in the app indicator appears bigger than the normal and in a wrong position then disappears. Please check the attached screen cast for details. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-appindicator 57-1 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 11:17:05 2023 InstallationDate: Installed on 2023-10-12 (5 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2039543/+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 2061739] Re: crash in meta_wayland_transaction_commit
** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3462 https://gitlab.gnome.org/GNOME/mutter/-/issues/3462 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/3462 Importance: Unknown Status: Unknown -- 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/2061739 Title: crash in meta_wayland_transaction_commit Status in Mutter: Unknown Status in mutter package in Ubuntu: New Bug description: Hi, The system is Ubuntu Noble with a regular daily updates. This happens many times since few days ago but not clear at all how to reproduce it. Regards, Patrice ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu4 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Tue Apr 16 09:26:16 2024 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2019-05-24 (1789 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 46.0-1ubuntu6 SourcePackage: gnome-shell UpgradeStatus: Upgraded to noble on 2019-05-28 (1785 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2061739/+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 2064196] Re: Can't change display position to "right of"
If you delete ~/.config/monitors.xml and log in again, can you configure the monitors correctly after that? ** Tags added: multimonitor nvidia ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2064196 Title: Can't change display position to "right of" Status in gnome-control-center package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Bug description: I have two monitors (Iiyama and Philips). In 22.04 I had two separate pulpits on each monitors. Currently in "Settings -> Displays" I can set it to "duplicate" or "joined". joined option is inconvenient because, every window I open is by default in the center of the gap between two monitors. I'am able to change it manually via nvidia-settings but it isn't persistent. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.239.06 Sat Feb 3 06:03:07 UTC 2024 GCC version: ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 08:05:32 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GK106 [GeForce GTX 660] [1458:354e] InstallationDate: Installed on 2024-04-28 (2 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: MSI MS-7758 ProcEnviron: LANG=pl_PL.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=e678c4a6-a42f-4ef2-a6c8-9187e5d5ab0a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.13:bd03/07/2014:br4.6:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7758 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2064196/+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 2064196] Re: Can't change display position to "right of"
Are you sure Settings is showing both Iiyama and Philips or is it perhaps showing one of them twice? (bug 2060268) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2064196 Title: Can't change display position to "right of" Status in gnome-control-center package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Bug description: I have two monitors (Iiyama and Philips). In 22.04 I had two separate pulpits on each monitors. Currently in "Settings -> Displays" I can set it to "duplicate" or "joined". joined option is inconvenient because, every window I open is by default in the center of the gap between two monitors. I'am able to change it manually via nvidia-settings but it isn't persistent. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.239.06 Sat Feb 3 06:03:07 UTC 2024 GCC version: ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 08:05:32 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GK106 [GeForce GTX 660] [1458:354e] InstallationDate: Installed on 2024-04-28 (2 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: MSI MS-7758 ProcEnviron: LANG=pl_PL.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=e678c4a6-a42f-4ef2-a6c8-9187e5d5ab0a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.13:bd03/07/2014:br4.6:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7758 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2064196/+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 2064196] Re: Can't change display position to "right of"
I wonder if this is due to bug 2060268... ** Package changed: xorg (Ubuntu) => gnome-control-center (Ubuntu) ** Also affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2064196 Title: Can't change display position to "right of" Status in gnome-control-center package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-470 package in Ubuntu: Incomplete Bug description: I have two monitors (Iiyama and Philips). In 22.04 I had two separate pulpits on each monitors. Currently in "Settings -> Displays" I can set it to "duplicate" or "joined". joined option is inconvenient because, every window I open is by default in the center of the gap between two monitors. I'am able to change it manually via nvidia-settings but it isn't persistent. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.239.06 Sat Feb 3 06:03:07 UTC 2024 GCC version: ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 08:05:32 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GK106 [GeForce GTX 660] [1458:354e] InstallationDate: Installed on 2024-04-28 (2 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: MSI MS-7758 ProcEnviron: LANG=pl_PL.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=e678c4a6-a42f-4ef2-a6c8-9187e5d5ab0a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/07/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G43 (MS-7758) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.13:bd03/07/2014:br4.6:svnMSI:pnMS-7758:pvr1.0:rvnMSI:rnZ77A-G43(MS-7758):rvr1.0:cvnMSI:ct3:cvr1.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7758 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2064196/+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 2064177] Re: Window borders and shadows missing from GTK3 dialogs
** Summary changed: - Window borders and shadows missing from GTK dialogs + Window borders and shadows missing from GTK3 dialogs ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: gtk+3.0 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/2064177 Title: Window borders and shadows missing from GTK3 dialogs Status in gnome-shell package in Ubuntu: Incomplete Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: I have a fresh Ubuntu 24.04 instalation and some of the windows have a few problems. Some are probably caused by theming, as the windows' borders (or their color) makes them impossible to discern from the background windows. Just earlier I discovered another bug, related to detecting the click and window I clicked. I am trying to see the sub-content of a software update but the system reacts as I clicked the window below. In the recording you can see this happening both with the Terminal and with Firefox. I have plenty of screenshots and also a screen recording that show the bugs. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 00:37:47 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-04-26 (3 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) RelatedPackageVersions: mutter-common 46.0-1ubuntu9 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2064177/+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 2064177] Re: Window borders and shadows missing from GTK dialogs
Thanks for the bug report. Firstly please open a separate bug about the clicking issue (although it sounds related to bug 2063831). We need each bug report to only describe one problem. For the window borders issue please try: 1. Deleting all local extensions: cd ~/.local/share/gnome-shell/ rm -rf extensions and then log in again. 2. If the problem still isn't solved then try resetting to system default settings: dconf reset -f / and then log in again. 3. If the problem still isn't solved then please run: journalctl -b0 > journal.txt dconf dump / > dconfchanges.txt and attach the resulting text files here. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2064177 Title: Window borders and shadows missing from GTK dialogs Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have a fresh Ubuntu 24.04 instalation and some of the windows have a few problems. Some are probably caused by theming, as the windows' borders (or their color) makes them impossible to discern from the background windows. Just earlier I discovered another bug, related to detecting the click and window I clicked. I am trying to see the sub-content of a software update but the system reacts as I clicked the window below. In the recording you can see this happening both with the Terminal and with Firefox. I have plenty of screenshots and also a screen recording that show the bugs. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 00:37:47 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-04-26 (3 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) RelatedPackageVersions: mutter-common 46.0-1ubuntu9 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2064177/+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 2064177] Re: Window borders and shadows missing from GTK dialogs
** Summary changed: - No windows margins, problems with detecting windows on clicks + Window borders and shadows missing from GTK dialogs -- 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/2064177 Title: Window borders and shadows missing from GTK dialogs Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have a fresh Ubuntu 24.04 instalation and some of the windows have a few problems. Some are probably caused by theming, as the windows' borders (or their color) makes them impossible to discern from the background windows. Just earlier I discovered another bug, related to detecting the click and window I clicked. I am trying to see the sub-content of a software update but the system reacts as I clicked the window below. In the recording you can see this happening both with the Terminal and with Firefox. I have plenty of screenshots and also a screen recording that show the bugs. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 30 00:37:47 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-04-26 (3 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) RelatedPackageVersions: mutter-common 46.0-1ubuntu9 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2064177/+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 2064146] Re: Screen shows orange snap to place wrongly
*** This bug is a duplicate of bug 2063970 *** https://bugs.launchpad.net/bugs/2063970 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2063970, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => gnome-shell-extension-tiling- assistant (Ubuntu) ** This bug has been marked a duplicate of bug 2063970 Enhanced tiling orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment. -- 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/2064146 Title: Screen shows orange snap to place wrongly Status in gnome-shell-extension-tiling-assistant package in Ubuntu: New Bug description: I have "Active screen edge" -feature enabled. First bug: I had 2 instances of transparent orange snap to place appear for no reason in a strange place. Second bug: I have transparent orange snap to place appear twice when trying to snap window to left, top and right. Bottom appears only once correctly. The animation is also shown twice. Screen capture is not possible during this window snap so I took photos on phone. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 19:51:51 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo CometLake-U GT2 [UHD Graphics] [17aa:22be] InstallationDate: Installed on 2024-04-29 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: LENOVO 20UBCTO1WW 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.8.0-31-generic root=UUID=ef15c653-655e-4eb6-8f55-41ec14bbdb78 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2023 dmi.bios.release: 1.33 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET43W (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UBCTO1WW 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.15 dmi.modalias: dmi:bvnLENOVO:bvrN2WET43W(1.33):bd11/06/2023:br1.33:efr1.15:svnLENOVO:pn20UBCTO1WW:pvrThinkPadX1YogaGen5:rvnLENOVO:rn20UBCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20UB_BU_Think_FM_ThinkPadX1YogaGen5: dmi.product.family: ThinkPad X1 Yoga Gen 5 dmi.product.name: 20UBCTO1WW dmi.product.sku: LENOVO_MT_20UB_BU_Think_FM_ThinkPad X1 Yoga Gen 5 dmi.product.version: ThinkPad X1 Yoga Gen 5 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2064146/+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 2064169] Re: Keyboard shortcuts
When the problem is happening please run: gsettings list-recursively | grep keybindings > keybindings.txt and attach the resulting text file here. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2064169 Title: Keyboard shortcuts Status in gnome-shell package in Ubuntu: Incomplete Bug description: I don't know if the section is correct, but when using the ubuntu keyboard shortcuts I added. Increase sound volume, when you put the super+up on, it ends up doing the behavior of another one that I had already removed to give way to this new one I made. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.171.04 Tue Mar 19 20:30:00 UTC 2024 GCC version: ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 17:28:25 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:0781] Subsystem: Dell GM108M [GeForce 940MX] [1028:0781] InstallationDate: Installed on 2024-04-28 (2 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Dell Inc. Inspiron 7460 ProcEnviron: LANG=pt_BR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=ddb1ca08-8d86-4cc1-a5ef-6f59217ebac6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0JXYRN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd07/23/2021:br1.15:svnDellInc.:pnInspiron7460:pvr:rvnDellInc.:rn0JXYRN:rvrA00:cvnDellInc.:ct10:cvr:sku0781: dmi.product.family: Inspiron dmi.product.name: Inspiron 7460 dmi.product.sku: 0781 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2064169/+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 2064099] Re: Quickly switching right and left clicks freezes Nautilus
Please try: gnome-extensions disable d...@rastersoft.com Does that avoid the bug? If not then next time it happens please open a Terminal and run: journalctl -b0 > journal.txt and attach the resulting text file here. ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- 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/2064099 Title: Quickly switching right and left clicks freezes Nautilus Status in mutter package in Ubuntu: Incomplete Status in nautilus package in Ubuntu: Incomplete Bug description: 1. Open Nautilus. 2. Try to right click and left click randomly and quickly. This behavior will freeze Nautilus until you must kill it and it happens every time you do this, and you cannot even move it's window. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 29 12:42:46 2024 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small-plus'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' InstallationDate: Installed on 2024-03-22 (38 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: nautilus UpgradeStatus: Upgraded to noble on 2024-04-11 (18 days ago) usr_lib_nautilus: file-roller 44.1-1 nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2064099/+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 2063831] Re: Clicking on bottom half of applications switches to background application
A fix is on the way: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3720 ** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Changed in: mutter (Ubuntu) Status: Confirmed => In Progress -- 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/2063831 Title: Clicking on bottom half of applications switches to background application Status in Mutter: New Status in mutter package in Ubuntu: In Progress Bug description: Basicly having more that 1 GUI application running in full screen and clicking bottom half of the currently opened GUI application will make the other application come to the foreground Eg: Google Chrome & Eclipse IDE are both in fullscreen, - Clicking On Eclipse IDE bottom half of the app window will get chrome to display infront of Eclipse, Eg2: Terminal and DBeaver are both in fullscreen, - Clicking On DBeaver bottom half of the app window will get Termial to display infront of DBeaver, ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.171.04 Tue Mar 19 20:30:00 UTC 2024 GCC version: ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 15:07:41 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Alder Lake-P GT2 [Iris Xe Graphics] [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Alder Lake-P GT2 [Iris Xe Graphics] [1462:1331] Subsystem: Micro-Star International Co., Ltd. [MSI] GA107M [GeForce RTX 3050 Ti Mobile] [1462:135d] InstallationDate: Installed on 2024-04-25 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Micro-Star International Co., Ltd. Katana GF66 12UD 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.8.0-31-generic root=UUID=7c59c657-2812-4b59-8441-927f4302e8fc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2022 dmi.bios.release: 1.12 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E1584IMS.10C dmi.board.asset.tag: Default string dmi.board.name: MS-1584 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE1584IMS.10C:bd05/05/2022:br1.12:svnMicro-StarInternationalCo.,Ltd.:pnKatanaGF6612UD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1584:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku1584.1: dmi.product.family: GF dmi.product.name: Katana GF66 12UD dmi.product.sku: 1584.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 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/mutter/+bug/2063831/+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 2056506] Re: ubuntu-dock 89 crashes on gnome-shell 45 with signal 6 when right clicking on the dock [clutter_actor_dispose: assertion failed: (priv->parent == NULL)]
The log in comment #23 looks like bug 1845281 which was declared fixed a few years ago so please open a new bug for it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2056506 Title: ubuntu-dock 89 crashes on gnome-shell 45 with signal 6 when right clicking on the dock [clutter_actor_dispose: assertion failed: (priv->parent == NULL)] Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Bug description: I'm using Noble for sometime and I'm having a very annoying and odd problem: everytime I close an application on x11 (Wayland doesn't work any better) clicking with the right button in the dock and choosing "Quit" I got that screen saying that something went wrong and I need to close the session and start over. Please, let me know what logs do you need. I couldn't find any meaningful information by myself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/2056506/+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 2012388] Re: X11 window (usually AnyDesk) at top-right of the screen is invisible and steals mouse clicks
Marco says he has tracked the issue back to gnome-shell itself. ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2012388 Title: X11 window (usually AnyDesk) at top-right of the screen is invisible and steals mouse clicks Status in Ubuntu AppIndicators: Unknown Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell-extension-appindicator package in Ubuntu: Triaged Bug description: Hardware Model: Dell Inc. Inspiron 16 Plus 7620 Firmware version: 1.5.1 CPU i7-12700H x20 GPU: Nvidia RTX3060 / MaxQ GPU: Intel Alder Lake-P Release: Lunar Lobster Architecture: AMD64 Kernel: 6.1.0-16-generic GNOME version: 44.rc Using Latest daily image of Ubuntu Lunar Lobster, I noticed an issue with window focus when windows are placed under the top-right system tray. Since it is hard to explain, I am attaching a screenshot. I am unable to click or interact with anything in the area within green rectangle. Applications affected: - Firefox (snap) - Chromium (snap) - Vivaldi Browser (deb) - Mattermost (snap) ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44~rc-1ubuntu2 ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6 Uname: Linux 6.1.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 21 20:35:05 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-01-23 (56 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) RelatedPackageVersions: mutter-common 44~rc-1ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-03-02 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2012388/+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 2007742] Re: Can't update stage views actor (regarding MetaWindowGroup, MetaWindowActorX11, MetaSurfaceActorX11)
** Tags added: noble -- 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/2007742 Title: Can't update stage views actor (regarding MetaWindowGroup, MetaWindowActorX11, MetaSurfaceActorX11) Status in GNOME Shell: New Status in Mutter: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: These messages repeat: [ 105.711276] ingenika gnome-shell[2919]: Can't update stage views actor [:0x55bba91da500] is on because it needs an allocation. [ 105.711772] ingenika gnome-shell[2919]: Can't update stage views actor [:0x55bbac95c330] is on because it needs an allocation. [ 105.711903] ingenika gnome-shell[2919]: Can't update stage views actor [:0x55bbae726860] is on because it needs an allocation. --- ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: gnome-shell 43.1-0ubuntu1 Uname: Linux 6.1.11-060111-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Feb 17 21:54:39 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-22 (179 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 43.0-1ubuntu4 SourcePackage: gnome-shell UpgradeStatus: Upgraded to kinetic on 2023-02-08 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2007742/+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 2064118] Re: Latest Chrome update breaks and froze interfaze in Ubuntu and wont open
But i just managed to fixit was something with wayland enabled -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2064118 Title: Latest Chrome update breaks and froze interfaze in Ubuntu and wont open Status in chromium-browser package in Ubuntu: Invalid Bug description: Latest Chrome Update has broken Chrome for Ubuntu 22.04.4 LTS Release: 22.04 When I click on the Chrome Icon it just indicates a loading Icon and break functionality of the whole interface, I need to Quit Chrome to be able to use any app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2064118/+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 2064118] Re: Latest Chrome update breaks and froze interfaze in Ubuntu and wont open
Chrome for ubuntu is chromium based -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2064118 Title: Latest Chrome update breaks and froze interfaze in Ubuntu and wont open Status in chromium-browser package in Ubuntu: Invalid Bug description: Latest Chrome Update has broken Chrome for Ubuntu 22.04.4 LTS Release: 22.04 When I click on the Chrome Icon it just indicates a loading Icon and break functionality of the whole interface, I need to Quit Chrome to be able to use any app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2064118/+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 2064118] [NEW] Latest Chrome update breaks and froze interfaze in Ubuntu and wont open
Public bug reported: Latest Chrome Update has broken Chrome for Ubuntu 22.04.4 LTS Release:22.04 When I click on the Chrome Icon it just indicates a loading Icon and break functionality of the whole interface, I need to Quit Chrome to be able to use any app. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2064118 Title: Latest Chrome update breaks and froze interfaze in Ubuntu and wont open Status in chromium-browser package in Ubuntu: New Bug description: Latest Chrome Update has broken Chrome for Ubuntu 22.04.4 LTS Release: 22.04 When I click on the Chrome Icon it just indicates a loading Icon and break functionality of the whole interface, I need to Quit Chrome to be able to use any app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2064118/+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 1967488] Re: [nvidia] Chromium stable snap doesn't display anything on Wayland with Nvidia as primary GPU
I've seen a suggestion this bug might have been fixed for a few months... until bug 2063049 happened. So let's wait for that fix first. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1967488 Title: [nvidia] Chromium stable snap doesn't display anything on Wayland with Nvidia as primary GPU Status in chromium-browser package in Ubuntu: Triaged Bug description: Hi I'm testing the Ubuntu 22.04 beta with wayland and when I try to open the Chromium browser (stable snap package), only see a black/transparent window. If I switch from Wayland to Xorg, everything is normal again. I tried to delete the profile folder , but I have the same result. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1967488/+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 2062377] Re: Ubuntu 24.04: gnome-shell crashes on Xorg if a legacy X11 cursor theme is selected
Please only use CSS cursor themes (like Yaru or Adwaita) until this bug is fixed. -- 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/2062377 Title: Ubuntu 24.04: gnome-shell crashes on Xorg if a legacy X11 cursor theme is selected Status in Mutter: New Status in mutter package in Ubuntu: In Progress Bug description: 1)Go to xorg 2)Download Gnome Tweak Tool 3)Select DMZ-white 4)crash from the system ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.161.07 Sat Feb 17 22:55:48 UTC 2024 GCC version: ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 17:38:02 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Acer Incorporated [ALI] GA107M [GeForce RTX 3050 Ti Mobile] [1025:1524] Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Lucienne [1025:1524] InstallationDate: Installed on 2024-04-17 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417.2) MachineType: Acer Aspire A715-42G ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic root=UUID=12cf9ac8-f034-465e-92e4-0c64e47e2350 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Azalea_CAS dmi.board.vendor: LN dmi.board.version: V1.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd02/19/2021:br1.2:efr1.2:svnAcer:pnAspireA715-42G:pvrV1.02:rvnLN:rnAzalea_CAS:rvrV1.02:cvnAcer:ct10:cvrV1.02:sku: dmi.product.family: Aspire 7 dmi.product.name: Aspire A715-42G dmi.product.sku: dmi.product.version: V1.02 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 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/mutter/+bug/2062377/+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 2064037] Re: GDM session crashes after returning from a screen-off.
The only crash-like problem I can see in those logs is: simple-framebuffer simple-framebuffer.0: drm_WARN_ON(map->is_iomem) which seems to be non-fatal for the Xorg process that triggered it. The cause of that issue is also bug 2060268, but that too is not a crash. So please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: gdm3 (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2064037 Title: GDM session crashes after returning from a screen-off. Status in Ubuntu: Incomplete Bug description: I've written an AskUbuntu question about this: https://askubuntu.com/questions/1511958/screen-lock-keeps-occuring- on-24-04-even-though-i-believe-ive-disabled-it/1512075#1512075 Originally I thought it was gnome not respecting my setting to prevent locking the screen after idling, but after discussing the issue on matrix (https://matrix.to/#/!EJhpCQHHqqcNicfiql:xentonix.net/$kPbn- fqDZgoG4s6PyQfki8tcSKJUpGH9QrXZSSV_vKY?via=decred.org=matrix.org=ubuntu.com) I think it is actually just a gdm or gnome-shell crash that happens when the PC idles, the screen turns off, and then I wake it. To summarize the symptom. I have the PC set to disable the screen after being idle for 5 minutes. I also set it such that it should not lock the session when this happens. (I want to turn on the screen and get right back to where I was without password overhead). What I've observed is that when I give the idle PC keyboard input, it wakes to a login screen, and when I login my windows from the previous session are completely gone (although tmux sessions are still alive). I've attached a relevant section of `journalctl --user` from around the time when I last tried to interact with the idle PC. I believe the "wake" event happens at `Apr 28 13:42:43` at which point we start seeing whoopsie messages: ``` Apr 28 13:42:44 toothbrush systemd[1]: Started whoopsie.service - crash report submission. ``` And then what looks like logs indicating that I was logged out and the previous session was ended: ``` Apr 28 13:42:56 toothbrush systemd[1]: run-user-1000-gvfs.mount: Deactivated successfully. Apr 28 13:42:57 toothbrush gdm-password][60731]: pam_unix(gdm-password:session): session closed for user joncrall Apr 28 13:42:57 toothbrush systemd[1]: session-61.scope: Deactivated successfully. Apr 28 13:42:57 toothbrush systemd[1]: session-61.scope: Consumed 12min 9.467s CPU time. Apr 28 13:42:57 toothbrush systemd-logind[1790]: Session 61 logged out. Waiting for processes to exit. Apr 28 13:42:57 toothbrush systemd-logind[1790]: Removed session 61. ``` The time from `13:42:44` to `13:43:07` where I get: ``` Apr 28 13:43:07 toothbrush systemd-logind[1790]: New session 221 of user joncrall. Apr 28 13:43:07 toothbrush systemd[1]: Started session-221.scope - Session 221 of User joncrall. ``` seems about right, because it takes a few seconds to go from de-idling the machine to seeing any sort of display. System Information: No LSB modules are available. Description: Ubuntu 24.04 LTS Release: 24.04 # System Details Report --- ## Report details - **Date generated:** 2024-04-28 15:17:36 ## Hardware Information: - **Hardware Model:** ASUS ROG STRIX Z590-E GAMING WIFI - **Memory:** 128.0 GiB - **Processor:** 11th Gen Intel® Core™ i9-11900K × 16 - **Graphics:**NVIDIA GeForce RTX™ 3090 - **Graphics 1:** NVIDIA GeForce RTX™ 3090 - **Disk Capacity:** 45.0 TB ## Software Information: - **Firmware Version:**0232 - **OS Name:** Ubuntu 24.04 LTS - **OS Build:**(null) - **OS Type:** 64-bit - **GNOME Version:** 46 - **Windowing System:**X11 - **Kernel Version:** Linux 6.8.0-31-generic Nvidia versions: NVIDIA-SMI 535.171.04 Driver Version:
[Desktop-packages] [Bug 2064017] Re: Xserver Display flickers when mouse pointer is inside narrow horizontal range band (kernel related)
Please try adding kernel parameter: i915.enable_psr=0 ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2064017 Title: Xserver Display flickers when mouse pointer is inside narrow horizontal range band (kernel related) Status in linux package in Ubuntu: Incomplete Bug description: My machine information is following : HP EliteBook 840 G3 Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520] xrandr -q active mode on laptop display : 1368x768 60.01 Tried using 6.8.8-060808 kernel (instead of the lubuntu 24.04 default shipped kernel 6.8.0-31), same issue. Rolling back the kernel to 6.7 fixed the problem,maybe there were some video driver changes from kernel 6.7 to 6.8 ? While using the 6.8 kernel I did some experiments: disabled picom in startup , no effect Tried changing display resolution, just moves vertical position of band. (at the above resolution 1368x768 vertical mouse pointer flicker range is around 640 ( measured running watch -t -n 0.0001 xdotool getmouselocation from a bash terminal) Tried moving refresh rate slightly around 60 Hz by creating a new modeline using cvt tool and adding new mode with xrandr, no effect. tried connecting external display on laptop VGA port and duplicating screen and the issue seems to disappear. tried capturing a video of the desktop using ffmpeg with x11grab, but it does not show the issue. I attached a short video of the laptop display flicker I recorded using my phone ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: LXQt Date: Sun Apr 28 09:44:42 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company EliteBook 840 G3 [103c:8079] InstallationDate: Installed on 2024-04-25 (3 days ago) InstallationMedia: Lubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240425.1) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID :3825 USB OPTICAL MOUSE Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 004: ID 05c8:0383 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP HD Camera Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: HP HP EliteBook 840 G3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=c323b5e4-1a45-4ce4-9f8d-c4f7f9c60388 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2019 dmi.bios.release: 1.42 dmi.bios.vendor: HP dmi.bios.version: N75 Ver. 01.42 dmi.board.name: 8079 dmi.board.vendor: HP dmi.board.version: KBC Version 85.78 dmi.chassis.asset.tag: 5CG7042V5J dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 133.120 dmi.modalias: dmi:bvnHP:bvrN75Ver.01.42:bd08/19/2019:br1.42:efr133.120:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.78:cvnHP:ct10:cvr:skuZ2A57UT#ABA: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 840 G3 dmi.product.sku: Z2A57UT#ABA dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2064017/+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 2063383] Re: [SRU] Ubuntu Unity takes 90 seconds to log out
** Tags added: noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/2063383 Title: [SRU] Ubuntu Unity takes 90 seconds to log out Status in gnome-session package in Ubuntu: Confirmed Status in gnome-session source package in Noble: Confirmed Bug description: [ Impact ] Ubuntu Unity reliably takes 90 seconds to log out. This is due to the user-level gnome-session.service systemd unit not properly terminating gnome-session on logout. An attempt is made to send SIGTERM to the process, which gnome-session does not care about. Instead, gnome-session-quit should be invoked when the systemd unit shuts down, which acts effectively and immediately. [ Test Plan ] Actual behavior: 1. Log in to a Unity session on Ubuntu Unity 24.04. 2. Log out of Ubuntu Unity. 3. Observe that only the wallpaper is shown for 90 seconds prior to the login manager showing again. Expected behavior: 1. Log in to a Unity session on Ubuntu Unity 24.04. 2. Log out of Ubuntu Unity. 3. Observe that logging out takes a few seconds at most, and you are able to log back in as the same user, or a different one. [ Where problems could occur ] If the gnome-session or gnome-session-quit binaries change the arguments they accept by default, log in and log out functionality on Unity sessions are likely to break. Additionally, if lightdm or systemd changes in a non-reverse- compatible way, this increases the chance of a user-facing regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/2063383/+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 2060665] Re: Unable to click on top left screen
Sounds like bug 2059819 so we can wait and see if that fixes this too. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2060665 Title: Unable to click on top left screen Status in gnome-shell package in Ubuntu: New Bug description: Random after some time, the top left of the screen can't be clicked (not even the mouse move event are dispatched to the window) Using the Wayland (Alt + F2) "lg" show that a transparent box (385 width x 56 height) is over, unable to close it [0x6204284ebac0 StLabel.message-title:insensitive first-child("Some window title")] It seems to be a notification window or something, and it's blocked here. The only way to fix it is to close the session, killing everything --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-01-01 (846 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell 42.9-0ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 RelatedPackageVersions: mutter-common 42.9-0ubuntu7 Tags: third-party-packages wayland-session jammy Uname: Linux 6.5.0-28-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-05-01 (726 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2060665/+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 2061242] Re: gnome-shell crashes randomly
*** This bug is a duplicate of bug 2050865 *** https://bugs.launchpad.net/bugs/2050865 I can tell from the log that it's bug 2050865 which should be fix- released within weeks. ** This bug has been marked a duplicate of bug 2050865 GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2061242 Title: gnome-shell crashes randomly Status in gnome-shell package in Ubuntu: Invalid Bug description: Don't yet understand what triggers it, maybe monitor connect/disconnect. ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu4 Uname: Linux 6.9.0-rc2 x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 20:29:01 2024 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2024-02-14 (60 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240212) ProcAttrCurrent: Error: [Errno 22] Invalid argument ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 46.0-1ubuntu6 Signal: 6 SignalName: SIGABRT SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker libvirt lpadmin ollama plugdev sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2061242/+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 2059819] Re: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen
** Tags added: noble ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2059819 Title: Regression: Jammy to Noble, right clicking on some icons shows dropdown on left side of screen Status in Ubuntu AppIndicators: Fix Released Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extension-appindicator package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: In ubuntu jammy and previous releases, right clicking on appindicator icons brings up the menu below the appindicator with appropriate gnome theming. In ubuntu noble, right clicking on some appindicator icons (example: barrier) results in the menu appearing on the left side of the screen without proper theming. See attached image. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2059819/+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 1971434] Re: Display powersave only blanks, but does not turn off
** Tags added: mantic noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1971434 Title: Display powersave only blanks, but does not turn off Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Recently upgraded to Ubuntu 22.04, and it seems like the power-saving feature in Gnome 42 does not actually turn off the screen(s) after X minutes, but just blanks them. When I manually run `xset dpms force off`, they do properly turn off and go to powersave mode. 1) Description: Ubuntu 22.04 LTS Release: 22.04 2) gnome-settings-daemon: Installed: 42.1-1ubuntu2 Candidate: 42.1-1ubuntu2 3) In Settings -> Power -> Screen Blank, set the inactivity period to 5 minutes. After 5 minutes, the screens should turn off. 4) Screens go black, but remain active and consume (too much) power. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-07-04 (667 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: gnome-settings-daemon 42.1-1ubuntu2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-30 (3 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers video wireshark _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1971434/+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 1986451] Re: Can't click context menu items when they cover the dock (in a Xorg session)
** Tags added: noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1986451 Title: Can't click context menu items when they cover the dock (in a Xorg session) Status in Dash to dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: ubuntu dock in bottom position won't let me click on button (convert java file to Kotlin file) in android studio, but in the left position everything works correctly. That is, if the menu android studio overlaps the ubuntu dock, then the menu buttons will not be pressed. https://youtu.be/KsOVG7Uucow ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 515.65.01 Wed Jul 20 14:00:58 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None Date: Sun Aug 14 10:52:56 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: openrazer-driver/3.4.0, 5.15.0-43-generic, x86_64: installed openrazer-driver/3.4.0, 5.15.0-46-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Xiaomi UHD Graphics 620 [1d72:1701] Subsystem: Xiaomi Mi Notebook Pro [GeForce MX150] [1d72:1701] InstallationDate: Installed on 2022-07-13 (31 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Timi TM1701 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=7c5eaac1-9b38-4169-8a20-0fef5e97c644 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/02/2018 dmi.bios.release: 106.121 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: XMAKB5R0P0603 dmi.board.asset.tag: Any dmi.board.name: TM1701 dmi.board.vendor: Timi dmi.board.version: MP dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Timi dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 0.3 dmi.modalias: dmi:bvnINSYDECorp.:bvrXMAKB5R0P0603:bd02/02/2018:br106.121:efr0.3:svnTimi:pnTM1701:pvr:rvnTimi:rnTM1701:rvrMP:cvnTimi:ct10:cvrChassisVersion:sku: dmi.product.family: Timibook dmi.product.name: TM1701 dmi.sys.vendor: Timi version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1986451/+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 2019906] Re: 24.04 : condensed, bold and black fonts can't be used for interface and title bar
** Tags removed: lunar -- 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/2019906 Title: 24.04 : condensed, bold and black fonts can't be used for interface and title bar Status in budgie-desktop package in Ubuntu: Confirmed Status in fonts-ubuntu package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Hi, fresh lunar lobster installation here, from legacy iso image ( ubiquity installer. ) As I usually do, I tried to change the font for interface, as I much prefer « condensed » fonts rather than large, round, regular ones. In 20.04 or 22.04 or 22.10 gnome-tweaks allowed to do that. Today in 24.04 ( and since 23.04 ) it only changes font in gnome-shell ( top panel, activities and app's views ) but not in other app's, not in the whole interface as it used to do. In dconf-editor I did not find entries regarding « global » interface font. Is this intended behavior ? Ability to change font type and size is also a matter of accessibility. For references : ⋅ https://askubuntu.com/questions/1468338/23-04-how-change-font-in-interface-gnome-shell-window-title-bar ⋅ https://forum.ubuntu-fr.org/viewtopic.php?id=2079313 This affects many users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/2019906/+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 2039543] Re: Miss placed Hexchat icon when switching workspaces
** Tags added: noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2039543 Title: Miss placed Hexchat icon when switching workspaces Status in Ubuntu AppIndicators: New Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extension-appindicator package in Ubuntu: Won't Fix Bug description: While switching workspaces, Hexchat icon in the app indicator appears bigger than the normal and in a wrong position then disappears. Please check the attached screen cast for details. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell-extension-appindicator 57-1 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 17 11:17:05 2023 InstallationDate: Installed on 2023-10-12 (5 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-appindicator/+bug/2039543/+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 1423773] Re: [memory leak] Gnome-Shell don't free ram when changing the wallpaper
It think it ended up being refixed in 91ce5ca960879dbe810cde43265d00b5c6446a1a but still fix released in gnome-shell 43.0. ** Changed in: mutter (Ubuntu) Status: Incomplete => Fix Released ** Project changed: gnome-shell => mutter ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5807 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5807 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5807 Importance: Unknown Status: Unknown ** Package changed: mutter (Ubuntu) => gnome-shell (Ubuntu) -- 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/1423773 Title: [memory leak] Gnome-Shell don't free ram when changing the wallpaper Status in GNOME Shell: Unknown Status in Mutter: New Status in gnome-shell package in Ubuntu: Fix Released Bug description: Sorry for my bad english, here is the link to see the error by yourself: https://www.youtube.com/watch?v=O53tt-6v81Y=youtu.be To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1423773/+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 1969140] Re: Window minimize animation flickers and appears in the wrong place
** Tags added: noble -- 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/1969140 Title: Window minimize animation flickers and appears in the wrong place Status in Dash to dock: New Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: Graphical glitches appears while minimizing or maximizing apps in x11 session randomly, screencast below ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Apr 14 17:07:49 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-04-12 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220409) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1969140/+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 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)
** Changed in: mutter Status: Fix Released => Unknown ** Changed in: mutter Remote watch: gitlab.gnome.org/GNOME/mutter/-/issues #2846 => gitlab.gnome.org/GNOME/mutter/-/issues #3402 ** Changed in: mutter (Ubuntu) Status: Confirmed => Fix Committed ** Tags added: fixed-in-mutter-46.1 fixed-upstream -- 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/2050865 Title: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) Status in Gnome Shell Extension Tiling Assistant: New Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Committed Bug description: I am observing multiple issues with external monitor in a hybrid system (laptop) with Intel GPU and NVIDIA GPU in a Gnome session: - Disconnecting HDMI cable crashes the desktop to login screen The HDMI port is connected to NVIDIA. I use the latest updates and drivers of 22.04 LTS. I am not sure how to auto-report this with ubuntu-bug. The system is similar to this report: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-tiling-assistant/+bug/2050865/+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 2061079] Re: GTK-ngl (new default backend) rendering issues with the nvidia 470 driver
** Description changed: [ Impact ] When the Nvidia 470 driver is used GTK 4 fails to render most text labels. [ Workaround ] Install a newer Nvidia driver using the 'Additional Drivers' app if you - can. Otherwise add GSK_RENDERER=gl to /etc/environment and reboot. + can. Otherwise add GSK_RENDERER=gl (or GSK_RENDERER=vulkan) to + /etc/environment and reboot. [ Test Plan ] 1. Install the Nvidia 470 driver on a system that supports it, being careful to ensure that Nvidia is the PRIMARY GPU of the system. So usually a desktop. 2. Open the Settings app and verify that all the icons in the side menu are visible. 3. Open Nautilus and verify that no file icons are missing their text labels. [ Where problems could occur ] Anywhere else in the rendering of GTK 4 apps. [ Additional information ] With nvidia driver, all GTK4 applications have label rendering issues. They are not refresh until passing the cursor over them, giving blank windows. The corner are white and not themed. Passing from one app scren to another one reproduces the issue. gnome-control-center or files, for instance, are blank by default. As suggested by seb128, exporting GSK_RENDERER=gl fixes the issue. Related upstream bugs and discussions are: - https://blog.gtk.org/2024/01/28/new-renderers-for-gtk/ - https://gitlab.gnome.org/GNOME/gtk/-/issues/6574 - https://gitlab.gnome.org/GNOME/gtk/-/issues/6411 - https://gitlab.gnome.org/GNOME/gtk/-/issues/6542 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libgtk-4-1 4.14.1+ds-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 12 09:47:05 2024 InstallationDate: Installed on 2020-04-24 (1449 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gtk4 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2061079 Title: GTK-ngl (new default backend) rendering issues with the nvidia 470 driver Status in GTK+: New Status in gtk4 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-535 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-545 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-550 package in Ubuntu: Fix Released Bug description: [ Impact ] When the Nvidia 470 driver is used GTK 4 fails to render most text labels. [ Workaround ] Install a newer Nvidia driver using the 'Additional Drivers' app if you can. Otherwise add GSK_RENDERER=gl (or GSK_RENDERER=vulkan) to /etc/environment and reboot. [ Test Plan ] 1. Install the Nvidia 470 driver on a system that supports it, being careful to ensure that Nvidia is the PRIMARY GPU of the system. So usually a desktop. 2. Open the Settings app and verify that all the icons in the side menu are visible. 3. Open Nautilus and verify that no file icons are missing their text labels. [ Where problems could occur ] Anywhere else in the rendering of GTK 4 apps. [ Additional information ] With nvidia driver, all GTK4 applications have label rendering issues. They are not refresh until passing the cursor over them, giving blank windows. The corner are white and not themed. Passing from one app scren to another one reproduces the issue. gnome-control-center or files, for instance, are blank by default. As suggested by seb128, exporting GSK_RENDERER=gl fixes the issue. Related upstream bugs and discussions are: - https://blog.gtk.org/2024/01/28/new-renderers-for-gtk/ - https://gitlab.gnome.org/GNOME/gtk/-/issues/6574 - https://gitlab.gnome.org/GNOME/gtk/-/issues/6411 - https://gitlab.gnome.org/GNOME/gtk/-/issues/6542 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: libgtk-4-1 4.14.1+ds-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 12 09:47:05 2024 InstallationDate: Installed on 2020-04-24 (1449 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gtk4
[Desktop-packages] [Bug 2063949] Re: Snap won't work/start
If you are using Chromium 124 then please see bug 2063049. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2063949 Title: Snap won't work/start Status in chromium-browser package in Ubuntu: Won't Fix Bug description: Other snaps work fine with encrypted home folder of my Ubuntu 16.04.7 O.S. But chromium snap won't work or start , with the following error output ; ``` update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/local/share/doc /usr/local/share/doc none bind,ro 0 0): cannot open directory "/usr/local/share": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none bind,ro 0 0): cannot open directory "/var/lib/snapd": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0): cannot open directory "/var/lib/snapd": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/javascript/jquery /usr/share/javascript/jquery none bind,ro 0 0): cannot open directory "/var/lib/snapd": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/javascript/sphinxdoc /usr/share/javascript/sphinxdoc none bind,ro 0 0): cannot open directory "/var/lib/snapd": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help none bind,ro 0 0): cannot open directory "/var/lib/snapd": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/sphinx_rtd_theme /usr/share/sphinx_rtd_theme none bind,ro 0 0): cannot open directory "/var/lib/snapd": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot open directory "/var/lib/snapd": permission denied cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist-dir=$HOME 0 0): cannot use invalid home directory "/home/sam": permission denied snap-update-ns failed with code 1 ``` Other snaps work fine. Snap version & info ; ``` snap2.62 snapd 2.62 series 16 ubuntu 16.04 kernel 4.15.0-224-generic ``` * Have encrypted home folder. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063949/+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 2063949] Re: Snap won't work/start
Free support for Ubuntu 16.04.7 ended in 2021. Please upgrade to a newer version of Ubuntu. https://wiki.ubuntu.com/Releases ** Tags added: xenial ** Changed in: chromium-browser (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2063949 Title: Snap won't work/start Status in chromium-browser package in Ubuntu: Won't Fix Bug description: Other snaps work fine with encrypted home folder of my Ubuntu 16.04.7 O.S. But chromium snap won't work or start , with the following error output ; ``` update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/local/share/doc /usr/local/share/doc none bind,ro 0 0): cannot open directory "/usr/local/share": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none bind,ro 0 0): cannot open directory "/var/lib/snapd": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gtk-doc /usr/share/gtk-doc none bind,ro 0 0): cannot open directory "/var/lib/snapd": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/javascript/jquery /usr/share/javascript/jquery none bind,ro 0 0): cannot open directory "/var/lib/snapd": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/javascript/sphinxdoc /usr/share/javascript/sphinxdoc none bind,ro 0 0): cannot open directory "/var/lib/snapd": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help none bind,ro 0 0): cannot open directory "/var/lib/snapd": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/sphinx_rtd_theme /usr/share/sphinx_rtd_theme none bind,ro 0 0): cannot open directory "/var/lib/snapd": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot open directory "/var/lib/snapd": permission denied cannot update snap namespace: cannot expand mount entry (none $HOME/.local/share none x-snapd.kind=ensure-dir,x-snapd.must-exist-dir=$HOME 0 0): cannot use invalid home directory "/home/sam": permission denied snap-update-ns failed with code 1 ``` Other snaps work fine. Snap version & info ; ``` snap2.62 snapd 2.62 series 16 ubuntu 16.04 kernel 4.15.0-224-generic ``` * Have encrypted home folder. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063949/+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 2061118] Re: Rendering issues in virtual machines (GTK ngl backend)
Users of the Nvidia 470 driver please see bug 2061079. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2061118 Title: Rendering issues in virtual machines (GTK ngl backend) Status in GTK+: New Status in Mesa: New Status in gtk4 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Triaged Status in gtk4 source package in Noble: Confirmed Status in mesa source package in Noble: Triaged Bug description: Build: Noble Daily Current from 12th April Host OS: Windows 11 VM App: VMWare Workstation 17 Player Issue: During installation there is continuous black flickering artefacts throughout the flow. Installation completed successfully, got to GDM, logged in but desktop screen is black and then locks up the whole application, cannot shutdown or interact with Player and need to hard kill from task manager. The issue appears does not appear with Mantic with the exact same machine configuration and appears to be an issue with GPU, my host machine is running an NVIDIA 4070ti with the latest windows drivers. On reboot some elements of the desktop are visible but cannot be interacted with without further lockups. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+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 2061118] Re: Rendering issues in virtual machines (GTK ngl backend)
Bug 2061079 being so similar makes me think long term we will find that GTK4 is doing something wrong. We just don't know what it's doing wrong yet. ** Changed in: gtk4 (Ubuntu Noble) Status: Invalid => Confirmed ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #11008 https://gitlab.freedesktop.org/mesa/mesa/-/issues/11008 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2061118 Title: Rendering issues in virtual machines (GTK ngl backend) Status in GTK+: New Status in Mesa: New Status in gtk4 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Triaged Status in gtk4 source package in Noble: Confirmed Status in mesa source package in Noble: Triaged Bug description: Build: Noble Daily Current from 12th April Host OS: Windows 11 VM App: VMWare Workstation 17 Player Issue: During installation there is continuous black flickering artefacts throughout the flow. Installation completed successfully, got to GDM, logged in but desktop screen is black and then locks up the whole application, cannot shutdown or interact with Player and need to hard kill from task manager. The issue appears does not appear with Mantic with the exact same machine configuration and appears to be an issue with GPU, my host machine is running an NVIDIA 4070ti with the latest windows drivers. On reboot some elements of the desktop are visible but cannot be interacted with without further lockups. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+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 2061118] Re: Rendering issues in virtual machines (GTK ngl backend)
Generalised to cover non-VMware (bug 2063923). ** Summary changed: - Rendering issues in vmware with 3d on (GTK ngl backend) + Rendering issues in virtual machines (GTK ngl backend) ** Tags added: noble vmwgfx -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2061118 Title: Rendering issues in virtual machines (GTK ngl backend) Status in GTK+: New Status in Mesa: New Status in gtk4 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Triaged Status in gtk4 source package in Noble: Confirmed Status in mesa source package in Noble: Triaged Bug description: Build: Noble Daily Current from 12th April Host OS: Windows 11 VM App: VMWare Workstation 17 Player Issue: During installation there is continuous black flickering artefacts throughout the flow. Installation completed successfully, got to GDM, logged in but desktop screen is black and then locks up the whole application, cannot shutdown or interact with Player and need to hard kill from task manager. The issue appears does not appear with Mantic with the exact same machine configuration and appears to be an issue with GPU, my host machine is running an NVIDIA 4070ti with the latest windows drivers. On reboot some elements of the desktop are visible but cannot be interacted with without further lockups. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+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 2037015] Re: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install
The crash (bug 2062146) is now awkwardly entangled with this bug. It occurs at the same time as, or usually instead of corruption. Bisected in Mesa: https://gitlab.freedesktop.org/mesa/mesa/-/issues/11033#note_2385595 Prior to that regression, I still believe the corruption probably started around: https://github.com/WebKit/WebKit/commit/8b0ce3683045d93cd365e91a4299f7e9babfc126 If you need a workaround for both issues then the best I have found is environment: WEBKIT_DMABUF_RENDERER_FORCE_SHM=1 ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #11033 https://gitlab.freedesktop.org/mesa/mesa/-/issues/11033 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037015 Title: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install Status in Webkit: Confirmed Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: In Progress Bug description: [ Impact ] Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install. [ Test Plan ] 1. Log into a Xorg session on a Raspberry Pi 4/400. 2. Open the default Help app by clicking the question mark icon in the dock or by running 'yelp'. 3. Verify it didn't crash and the window contents are not corrupt. [ Where problems could occur ] The fix is limited to webkit2gtk so can only affect apps such as yelp or the Raspberry Pi installer. [ Other Info ] During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2037015/+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 2062146] Re: Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile
** No longer affects: yelp (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/2062146 Title: Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile Status in Mesa: New Status in mesa package in Ubuntu: Triaged Status in webkit2gtk package in Ubuntu: In Progress Bug description: MiniBrowser crashed immediately on Raspberry Pi 400. ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: libwebkit2gtk-4.1-0 2.44.0-2 ProcVersionSignature: Ubuntu 6.8.0-1002.2-raspi 6.8.1 Uname: Linux 6.8.0-1002-raspi aarch64 ApportVersion: 2.28.0-0ubuntu1 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 17:32:12 2024 ExecutablePath: /usr/lib/aarch64-linux-gnu/webkit2gtk-4.1/MiniBrowser JournalErrors: -- No entries -- ProcCmdline: ./MiniBrowser ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= Signal: 11 SignalName: SIGSEGV SourcePackage: webkit2gtk StacktraceTop: ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /lib/aarch64-linux-gnu/libgbm.so.1 ?? () from /lib/aarch64-linux-gnu/libwebkit2gtk-4.1.so.0 Title: MiniBrowser crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2062146/+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 2061118] Re: Rendering issues in virtual machines (GTK ngl backend)
Also tracking in https://gitlab.freedesktop.org/mesa/mesa/-/issues/11008 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2061118 Title: Rendering issues in virtual machines (GTK ngl backend) Status in GTK+: New Status in Mesa: New Status in gtk4 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Triaged Status in gtk4 source package in Noble: Confirmed Status in mesa source package in Noble: Triaged Bug description: Build: Noble Daily Current from 12th April Host OS: Windows 11 VM App: VMWare Workstation 17 Player Issue: During installation there is continuous black flickering artefacts throughout the flow. Installation completed successfully, got to GDM, logged in but desktop screen is black and then locks up the whole application, cannot shutdown or interact with Player and need to hard kill from task manager. The issue appears does not appear with Mantic with the exact same machine configuration and appears to be an issue with GPU, my host machine is running an NVIDIA 4070ti with the latest windows drivers. On reboot some elements of the desktop are visible but cannot be interacted with without further lockups. To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/2061118/+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 2063923] Re: Graphic shows strange
*** This bug is a duplicate of bug 2061118 *** https://bugs.launchpad.net/bugs/2061118 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2061118, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => gtk4 (Ubuntu) ** This bug has been marked a duplicate of bug 2061118 Rendering issues in virtual machines (GTK ngl backend) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2063923 Title: Graphic shows strange Status in gtk4 package in Ubuntu: New Bug description: In Ubuntu 24.04 LTS, GNOME Applications are written in Flutter, but it doesn't look proper. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 27 16:32:00 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Red Hat, Inc. Virtio 1.0 GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Virtio 1.0 GPU [1af4:1100] InstallationDate: Installed on 2024-04-27 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU Tablet Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Lsusb-t: /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/15p, 480M |__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 480M /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/15p, 5000M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) 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.8.0-31-generic root=UUID=e54ffc83-f536-4520-a7c1-9f8dc8cca485 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2015 dmi.bios.release: 0.0 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-6.2 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-6.2:cvnQEMU:ct1:cvrpc-q35-6.2:sku: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-6.2 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2063923/+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 2063341] Re: gnome-shell crashed with SIGSEGV in wl_closure_invoke() from wl_client_connection_data() from wl_event_loop_dispatch() from wayland_event_source_dispatch() from g_
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2063341 Title: gnome-shell crashed with SIGSEGV in wl_closure_invoke() from wl_client_connection_data() from wl_event_loop_dispatch() from wayland_event_source_dispatch() from g_main_dispatch() Status in gnome-shell package in Ubuntu: New Bug description: https://errors.ubuntu.com/problem/c0af8821f546cdeb71cd1cdaf36e979eba58dd60 I've been using Ubuntu for almost 2 years and it's been working fine. I use a KVM switch (built in Benq monitor) all the time. Since last month Ubuntu randomly crashes when I switch back to it. Or it could be wake up/suspend, I can't see when it exactly happens, it's just logging screen after crash. I am running: openVPN, firefox (dozen tabs), chrome (ms teams), slack, postman, 3x Intellij IDEA, VS Code System logs don't show anything meaningful to me or Google and I don't know how to get a clue as to what's going on. I suspect a new version of MS Teams that was introduced a few weeks ago. Please help me I cannot reproduce the crash or find anything on the web about it. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 15:59:03 2024 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-31 (601 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.9-0ubuntu7 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063341/+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 2063869] Re: Missing default cursor
** Tags added: cursor -- 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/2063869 Title: Missing default cursor Status in Mutter: New Status in dmz-cursor-theme package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: In Progress Bug description: After upgrading from Ubuntu 23.10 to 24.04, the DMZ-White mouse pointer works correctly when the pointer is over a window, but shows a pale grey square when over the desktop or Ubuntu top bar. This appears to happen because the /usr/share/icons/DMZ-White/cursors/default file (or symlink) is missing. Doing the following appears to fix the problem: 1. cd /usr/share/icons/DMZ-White/cursors 2. ln -s left_ptr default 3. In gnome-tweaks change to some other mouse pointer. 4. In gnome-tweaks change back to DMZ-White. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: dmz-cursor-theme 0.4.5ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 18:39:40 2024 Dependencies: InstallationDate: Installed on 2020-07-14 (1382 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: dmz-cursor-theme UpgradeStatus: Upgraded to noble on 2024-04-11 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2063869/+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 2063970] Re: Enhanced tiling orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment.
** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- tiling-assistant (Ubuntu) -- 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/2063970 Title: Enhanced tiling orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment. Status in gnome-shell-extension-tiling-assistant package in Ubuntu: New Bug description: I've got a fresh install of the first 24.04 release, and I'm seeing strange behavior related to super+arrow keys and the enhanced tiling. I've disabled tiling popups and tiling groups, but I like the quad blocks. The issue is when I'm moving around windows, sometimes the orange shading that indicates what a window will resize to will persist even after I'm done with the adjustment. I'm not sure how to reproduce yet, but it's happened several times. Not sure if I'll be able to take a screenshot or not. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-shell 46.0-0ubuntu5 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 27 16:06:49 2024 DisplayManager: gdm3 InstallationDate: Installed on 2024-04-25 (2 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) RelatedPackageVersions: mutter-common 46.0-1ubuntu9 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2063970/+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 2062377] Re: Ubuntu 24.04: gnome-shell crashes on Xorg if a legacy X11 cursor theme is selected
** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/3454 Importance: Unknown Status: Unknown -- 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/2062377 Title: Ubuntu 24.04: gnome-shell crashes on Xorg if a legacy X11 cursor theme is selected Status in Mutter: Unknown Status in mutter package in Ubuntu: In Progress Bug description: 1)Go to xorg 2)Download Gnome Tweak Tool 3)Select DMZ-white 4)crash from the system ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.161.07 Sat Feb 17 22:55:48 UTC 2024 GCC version: ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 17:38:02 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Acer Incorporated [ALI] GA107M [GeForce RTX 3050 Ti Mobile] [1025:1524] Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Lucienne [1025:1524] InstallationDate: Installed on 2024-04-17 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417.2) MachineType: Acer Aspire A715-42G ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic root=UUID=12cf9ac8-f034-465e-92e4-0c64e47e2350 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Azalea_CAS dmi.board.vendor: LN dmi.board.version: V1.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd02/19/2021:br1.2:efr1.2:svnAcer:pnAspireA715-42G:pvrV1.02:rvnLN:rnAzalea_CAS:rvrV1.02:cvnAcer:ct10:cvrV1.02:sku: dmi.product.family: Aspire 7 dmi.product.name: Aspire A715-42G dmi.product.sku: dmi.product.version: V1.02 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 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/mutter/+bug/2062377/+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 2063869] Re: Missing default cursor
Tracking in https://gitlab.gnome.org/GNOME/mutter/-/issues/3184 the proposed fix is https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3718 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3184 https://gitlab.gnome.org/GNOME/mutter/-/issues/3184 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/3184 Importance: Unknown Status: Unknown ** Changed in: dmz-cursor-theme (Ubuntu) Status: New => Won't Fix ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu) Status: New => In Progress ** Changed in: mutter (Ubuntu) Milestone: None => noble-updates -- 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/2063869 Title: Missing default cursor Status in Mutter: Unknown Status in dmz-cursor-theme package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: In Progress Bug description: After upgrading from Ubuntu 23.10 to 24.04, the DMZ-White mouse pointer works correctly when the pointer is over a window, but shows a pale grey square when over the desktop or Ubuntu top bar. This appears to happen because the /usr/share/icons/DMZ-White/cursors/default file (or symlink) is missing. Doing the following appears to fix the problem: 1. cd /usr/share/icons/DMZ-White/cursors 2. ln -s left_ptr default 3. In gnome-tweaks change to some other mouse pointer. 4. In gnome-tweaks change back to DMZ-White. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: dmz-cursor-theme 0.4.5ubuntu1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 18:39:40 2024 Dependencies: InstallationDate: Installed on 2020-07-14 (1382 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: dmz-cursor-theme UpgradeStatus: Upgraded to noble on 2024-04-11 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2063869/+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 2063501] Re: gnome-shell crashed with assertion failure "libmutter:ERROR:../src/core/window.c:5869:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_mon
*** This bug is a duplicate of bug 2050865 *** https://bugs.launchpad.net/bugs/2050865 If you can find any crash files from Xwayland in /var/crash then please open a new bug for that. -- 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/2063501 Title: gnome-shell crashed with assertion failure "libmutter:ERROR:../src/core/window.c:5869:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)" Status in gnome-shell package in Ubuntu: New Bug description: # journalctl _COMM=gnome-shell --since="20 minutes ago" -p warning Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: JS ERROR: TypeError: this._settings is null getInt@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/common.js:136:9 _onMoving@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/moveHandler.js:361:38 @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:11 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:32 hostname gnome-shell[190040]: Gio.UnixInputStream has been moved to a separate platform-specific library. Please update your code to use GioUn> 0 inhibit() ["resource:///org/gnome/shell/misc/loginManager.js":209:8] 1 InterpretGeneratorResume() ["self-hosted":1461:33] 2 AsyncFunctionNext() ["self-hosted":852:26] 3 anonymous() ["resource:///org/gnome/shell/ui/init.js":21:19] Apr 25 23:36:33 hostname gnome-shell[188828]: Connection to xwayland lost Apr 25 23:36:33 hostname gnome-shell[188828]: Xwayland terminated, exiting since it was mandatory Apr 25 23:36:33 hostname gnome-shell[188828]: JS ERROR: Gio.IOErrorEnum: Xwayland exited unexpectedly @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:40 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Apr 25 23:36:54 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xwayland 2:23.2.6-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 23:45:31 2024 InstallationDate: Installed on 2024-03-22 (34 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: xwayland UpgradeStatus: Upgraded to noble on 2024-04-11 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063501/+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 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)
This might actually be https://gitlab.gnome.org/GNOME/mutter/-/issues/3402 which is fixed in mutter 46.1 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3402 https://gitlab.gnome.org/GNOME/mutter/-/issues/3402 -- 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/2050865 Title: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) Status in Gnome Shell Extension Tiling Assistant: New Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: I am observing multiple issues with external monitor in a hybrid system (laptop) with Intel GPU and NVIDIA GPU in a Gnome session: - Disconnecting HDMI cable crashes the desktop to login screen The HDMI port is connected to NVIDIA. I use the latest updates and drivers of 22.04 LTS. I am not sure how to auto-report this with ubuntu-bug. The system is similar to this report: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-tiling-assistant/+bug/2050865/+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 2063501] Re: gnome-shell crashed with assertion failure "libmutter:ERROR:../src/core/window.c:5869:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_mon
*** This bug is a duplicate of bug 2050865 *** https://bugs.launchpad.net/bugs/2050865 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2050865, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 2050865 GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2063501 Title: gnome-shell crashed with assertion failure "libmutter:ERROR:../src/core/window.c:5869:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)" Status in gnome-shell package in Ubuntu: New Bug description: # journalctl _COMM=gnome-shell --since="20 minutes ago" -p warning Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: JS ERROR: TypeError: this._settings is null getInt@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/common.js:136:9 _onMoving@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/moveHandler.js:361:38 @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:11 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:32 hostname gnome-shell[190040]: Gio.UnixInputStream has been moved to a separate platform-specific library. Please update your code to use GioUn> 0 inhibit() ["resource:///org/gnome/shell/misc/loginManager.js":209:8] 1 InterpretGeneratorResume() ["self-hosted":1461:33] 2 AsyncFunctionNext() ["self-hosted":852:26] 3 anonymous() ["resource:///org/gnome/shell/ui/init.js":21:19] Apr 25 23:36:33 hostname gnome-shell[188828]: Connection to xwayland lost Apr 25 23:36:33 hostname gnome-shell[188828]: Xwayland terminated, exiting since it was mandatory Apr 25 23:36:33 hostname gnome-shell[188828]: JS ERROR: Gio.IOErrorEnum: Xwayland exited unexpectedly @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:40 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Apr 25 23:36:54 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xwayland 2:23.2.6-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 23:45:31 2024 InstallationDate: Installed on
[Desktop-packages] [Bug 2063501] Re: gnome-shell crashed with assertion failure "meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l>"
*** This bug is a duplicate of bug 2050865 *** https://bugs.launchpad.net/bugs/2050865 I am seeing three different gnome-shell crashes here: * Signal 6: Assertion in meta_window_get_work_area_for_logical_monitor * Signal 11: Reason unknown. No crash report. * Shutdown due to Xwayland crashing. Also the only reason for Xwayland crashing I can see is related to nouveau. So please use the 'Additional Drivers' app to install an official Nvidia driver. Though that will force you to use Xorg instead of Wayland. ** Summary changed: - gnome-shell crashed with assertion failure "meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l>" + gnome-shell crashed with assertion failure "libmutter:ERROR:../src/core/window.c:5869:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2063501 Title: gnome-shell crashed with assertion failure "libmutter:ERROR:../src/core/window.c:5869:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)" Status in gnome-shell package in Ubuntu: New Bug description: # journalctl _COMM=gnome-shell --since="20 minutes ago" -p warning Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: JS ERROR: TypeError: this._settings is null getInt@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/common.js:136:9 _onMoving@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/moveHandler.js:361:38 @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:11 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:32 hostname gnome-shell[190040]: Gio.UnixInputStream has been moved to a separate platform-specific library. Please update your code to use GioUn> 0 inhibit() ["resource:///org/gnome/shell/misc/loginManager.js":209:8] 1 InterpretGeneratorResume() ["self-hosted":1461:33] 2 AsyncFunctionNext() ["self-hosted":852:26] 3 anonymous() ["resource:///org/gnome/shell/ui/init.js":21:19] Apr 25 23:36:33 hostname gnome-shell[188828]: Connection to xwayland lost Apr 25 23:36:33 hostname gnome-shell[188828]: Xwayland terminated, exiting since it was mandatory Apr 25 23:36:33 hostname gnome-shell[188828]: JS ERROR: Gio.IOErrorEnum: Xwayland exited unexpectedly @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:40 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Apr 25 23:36:54 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xwayland 2:23.2.6-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop:
[Desktop-packages] [Bug 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)
** Summary changed: - GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:6377:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) + GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) -- 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/2050865 Title: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:...:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) Status in Gnome Shell Extension Tiling Assistant: New Status in Mutter: New Status in mutter package in Ubuntu: Confirmed Bug description: I am observing multiple issues with external monitor in a hybrid system (laptop) with Intel GPU and NVIDIA GPU in a Gnome session: - Disconnecting HDMI cable crashes the desktop to login screen The HDMI port is connected to NVIDIA. I use the latest updates and drivers of 22.04 LTS. I am not sure how to auto-report this with ubuntu-bug. The system is similar to this report: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-tiling-assistant/+bug/2050865/+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 2050865] Re: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:6377:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor)
** Tags added: noble -- 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/2050865 Title: GNOME Wayland session crashes with libmutter:ERROR:../src/core/window.c:6377:meta_window_get_work_area_for_logical_monitor: assertion failed: (logical_monitor) Status in Gnome Shell Extension Tiling Assistant: New Status in Mutter: New Status in mutter package in Ubuntu: New Bug description: I am observing multiple issues with external monitor in a hybrid system (laptop) with Intel GPU and NVIDIA GPU in a Gnome session: - Disconnecting HDMI cable crashes the desktop to login screen The HDMI port is connected to NVIDIA. I use the latest updates and drivers of 22.04 LTS. I am not sure how to auto-report this with ubuntu-bug. The system is similar to this report: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-tiling-assistant/+bug/2050865/+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 2023647] Re: [amdgpu] Screens go into flicker cycle after going blank with external monitor(s)
Thank you for reporting this bug to Ubuntu. Ubuntu 23.04 (lunar) reached end-of-life on January 25, 2024. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it anymore. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: mutter (Ubuntu) Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- 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/2023647 Title: [amdgpu] Screens go into flicker cycle after going blank with external monitor(s) Status in Mutter: New Status in linux package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Won't Fix Bug description: This happens whenever screen goes blank after inactivity with external monitors. When there is only one external monitor after few cycles the system recovers from the bug. When there are more than one monitors the system almost never recovers until unplugging extra monitor, as shown in video: https://photos.app.goo.gl/td6coEKFQd3DKe9C7 Happens on desktop and login screen. The same result with Wayland and X11. Does not depend on size of the monitor, cable (HDMI or USB-C) or is it connected via USB-C hub or directly. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 13 12:36:44 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-04-13 (60 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 44.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to lunar on 2023-04-21 (52 days ago) --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2023-04-13 (131 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Dell Inc. Inspiron 5415 Package: mutter ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-27.28-generic 6.2.15 RelatedPackageVersions: linux-restricted-modules-6.2.0-27-generic N/A linux-backports-modules-6.2.0-27-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.5 Tags: lunar Uname: Linux 6.2.0-27-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-04-21 (122 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 02/13/2023 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0WKFHK dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.15.0 dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd02/13/2023:br1.15:svnDellInc.:pnInspiron5415:pvr1.15.0:rvnDellInc.:rn0WKFHK:rvrA00:cvnDellInc.:ct10:cvr1.15.0:sku0A77: dmi.product.family: Inspiron dmi.product.name: Inspiron 5415 dmi.product.sku: 0A77 dmi.product.version: 1.15.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2023647/+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 2063501] Re: gnome-shell crashed with assertion failure "meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l>"
** Summary changed: - Sometimes gnome-shell crash upon unlocking session from suspension + gnome-shell crashed with assertion failure "meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l>" ** No longer affects: xwayland (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2063501 Title: gnome-shell crashed with assertion failure "meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l>" Status in gnome-shell package in Ubuntu: New Bug description: # journalctl _COMM=gnome-shell --since="20 minutes ago" -p warning Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: JS ERROR: TypeError: this._settings is null getInt@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/common.js:136:9 _onMoving@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/moveHandler.js:361:38 @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:11 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:32 hostname gnome-shell[190040]: Gio.UnixInputStream has been moved to a separate platform-specific library. Please update your code to use GioUn> 0 inhibit() ["resource:///org/gnome/shell/misc/loginManager.js":209:8] 1 InterpretGeneratorResume() ["self-hosted":1461:33] 2 AsyncFunctionNext() ["self-hosted":852:26] 3 anonymous() ["resource:///org/gnome/shell/ui/init.js":21:19] Apr 25 23:36:33 hostname gnome-shell[188828]: Connection to xwayland lost Apr 25 23:36:33 hostname gnome-shell[188828]: Xwayland terminated, exiting since it was mandatory Apr 25 23:36:33 hostname gnome-shell[188828]: JS ERROR: Gio.IOErrorEnum: Xwayland exited unexpectedly @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:40 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Apr 25 23:36:54 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xwayland 2:23.2.6-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 23:45:31 2024 InstallationDate: Installed on 2024-03-22 (34 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) SourcePackage: xwayland UpgradeStatus: Upgraded to noble on 2024-04-11 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063501/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 2063341] Re: gnome-shell crashed with SIGSEGV in wl_closure_invoke() from wl_client_connection_data() from wl_event_loop_dispatch() from wayland_event_source_dispatch() from g_
Tracking in: https://errors.ubuntu.com/problem/c0af8821f546cdeb71cd1cdaf36e979eba58dd60 ** Summary changed: - gnome-shell crashed with SIGSEGV + gnome-shell crashed with SIGSEGV in wl_closure_invoke() from wl_client_connection_data() from wl_event_loop_dispatch() from wayland_event_source_dispatch() from g_main_dispatch() ** Description changed: + https://errors.ubuntu.com/problem/c0af8821f546cdeb71cd1cdaf36e979eba58dd60 + I've been using Ubuntu for almost 2 years and it's been working fine. I use a KVM switch (built in Benq monitor) all the time. Since last month Ubuntu randomly crashes when I switch back to it. Or it could be wake up/suspend, I can't see when it exactly happens, it's just logging screen after crash. I am running: openVPN, firefox (dozen tabs), chrome (ms teams), slack, postman, 3x Intellij IDEA, VS Code System logs don't show anything meaningful to me or Google and I don't know how to get a clue as to what's going on. I suspect a new version of MS Teams that was introduced a few weeks ago. - Please help me + Please help me I cannot reproduce the crash or find anything on the web about it. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 15:59:03 2024 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-31 (601 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.9-0ubuntu7 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- 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/2063341 Title: gnome-shell crashed with SIGSEGV in wl_closure_invoke() from wl_client_connection_data() from wl_event_loop_dispatch() from wayland_event_source_dispatch() from g_main_dispatch() Status in gnome-shell package in Ubuntu: Incomplete Bug description: https://errors.ubuntu.com/problem/c0af8821f546cdeb71cd1cdaf36e979eba58dd60 I've been using Ubuntu for almost 2 years and it's been working fine. I use a KVM switch (built in Benq monitor) all the time. Since last month Ubuntu randomly crashes when I switch back to it. Or it could be wake up/suspend, I can't see when it exactly happens, it's just logging screen after crash. I am running: openVPN, firefox (dozen tabs), chrome (ms teams), slack, postman, 3x Intellij IDEA, VS Code System logs don't show anything meaningful to me or Google and I don't know how to get a clue as to what's going on. I suspect a new version of MS Teams that was introduced a few weeks ago. Please help me I cannot reproduce the crash or find anything on the web about it. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 15:59:03 2024 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-31 (601 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.9-0ubuntu7 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063341/+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 2063904] Re: gnome-shell crashed with SIGSEGV in wl_closure_invoke() from wl_client_connection_data() from wl_event_loop_dispatch() from wayland_event_source_dispatch() from g_
*** This bug is a duplicate of bug 2063341 *** https://bugs.launchpad.net/bugs/2063341 ** Summary changed: - /usr/bin/gnome-shell:11:wl_closure_invoke:wl_client_connection_data:wl_event_loop_dispatch:wayland_event_source_dispatch:g_main_dispatch + gnome-shell crashed with SIGSEGV in wl_closure_invoke() from wl_client_connection_data() from wl_event_loop_dispatch() from wayland_event_source_dispatch() from g_main_dispatch() ** This bug has been marked a duplicate of bug 2063341 gnome-shell crashed with SIGSEGV in wl_closure_invoke() from wl_client_connection_data() from wl_event_loop_dispatch() from wayland_event_source_dispatch() from g_main_dispatch() -- 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/2063904 Title: gnome-shell crashed with SIGSEGV in wl_closure_invoke() from wl_client_connection_data() from wl_event_loop_dispatch() from wayland_event_source_dispatch() from g_main_dispatch() Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.9-0ubuntu2, the problem page at https://errors.ubuntu.com/problem/c0af8821f546cdeb71cd1cdaf36e979eba58dd60 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063904/+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 2063536] Re: flickering screen
I can see 'gjs' crashing constantly so please try: gnome-extensions disable d...@rastersoft.com If that doesn't fix it then please provide a video of the problem. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2063536 Title: flickering screen Status in Ubuntu: Incomplete Bug description: automatically refresh and hang ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 08:44:25 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: rtbth/3.9.8, 6.5.0-27-generic, x86_64: installed rtbth/3.9.8, 6.5.0-28-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc5] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] CometLake-S GT2 [UHD Graphics 630] [1462:7d82] InstallationDate: Installed on 2024-04-16 (9 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 003: ID 1a2c:0e24 China Resource Semico Co., Ltd USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 2M/x2 /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 9: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 10: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 10: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: Micro-Star International Co., Ltd. MS-7D82 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic root=UUID=5d5b2975-ec40-4c41-919c-f0c2ecc1a822 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/24/2022 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 1.22 dmi.board.asset.tag: Default string dmi.board.name: PRO H410M-B(MS-7D82) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.22:bd03/24/2022:br5.19:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D82:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROH410M-B(MS-7D82):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D82 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2063536/+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 2063831] Re: Clicking on bottom half of applications switches to background application
** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Tags added: focus -- 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/2063831 Title: Clicking on bottom half of applications switches to background application Status in mutter package in Ubuntu: New Bug description: Basicly having more that 1 GUI application running in full screen and clicking bottom half of the currently opened GUI application will make the other application come to the foreground Eg: Google Chrome & Eclipse IDE are both in fullscreen, - Clicking On Eclipse IDE bottom half of the app window will get chrome to display infront of Eclipse, Eg2: Terminal and DBeaver are both in fullscreen, - Clicking On DBeaver bottom half of the app window will get Termial to display infront of Eclipse, ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.171.04 Tue Mar 19 20:30:00 UTC 2024 GCC version: ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 15:07:41 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Alder Lake-P GT2 [Iris Xe Graphics] [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Alder Lake-P GT2 [Iris Xe Graphics] [1462:1331] Subsystem: Micro-Star International Co., Ltd. [MSI] GA107M [GeForce RTX 3050 Ti Mobile] [1462:135d] InstallationDate: Installed on 2024-04-25 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) MachineType: Micro-Star International Co., Ltd. Katana GF66 12UD 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.8.0-31-generic root=UUID=7c59c657-2812-4b59-8441-927f4302e8fc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/05/2022 dmi.bios.release: 1.12 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E1584IMS.10C dmi.board.asset.tag: Default string dmi.board.name: MS-1584 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE1584IMS.10C:bd05/05/2022:br1.12:svnMicro-StarInternationalCo.,Ltd.:pnKatanaGF6612UD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1584:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku1584.1: dmi.product.family: GF dmi.product.name: Katana GF66 12UD dmi.product.sku: 1584.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2063831/+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 2062177] Re: Remmina crashes after RDP connection
I was able to make remnina works using the snap version. If anyone wants to import all of its conections can do it moving the files here: ~/snap/remmina/current/.local/share/remmina/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/2062177 Title: Remmina crashes after RDP connection Status in remmina package in Ubuntu: Fix Committed Bug description: * Impact When connecting with RDP Remmina crashes. It's due to an invalid API use in remmina and stricter checking in the most recent freerdp3 version which makes it error out now. * Test case Try to connect to a RDP server using remmina, it shouldn't crash * Regression potential The change is fixing an incorrect API use in the RDP plugin around color check, if there is an issue it will be in the RDP support, probably around colors handling -- Syslog show the following: 2024-04-18T13:49:02.969819+02:00 localhost dbus-daemon[3214]: [session uid=1001 pid=3214] Successfully activated service 'org.gnome.seahorse.Application' 2024-04-18T13:49:03.655883+02:00 localhost systemd[3176]: Started app-gnome-org.remmina.Remmina-53436.scope - Application launched by gnome-shell. 2024-04-18T13:49:03.656884+02:00 localhost remmina[53441]: Remmina does not log all output statements. Turn on more verbose output by using "G_MESSAGES_DEBUG=remmina" as an environment variable.#012More info available on the Remmina wiki at:#012https://gitlab.com/Remmina/Remmina/-/wikis/Usage/Remmina-debugging 2024-04-18T13:49:03.766401+02:00 localhost remmina[53441]: gtk_menu_attach_to_widget(): menu already attached to GtkMenuItem 2024-04-18T13:49:13.851397+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [ERROR][com.freerdp.common.settings] - [freerdp_settings_get_bool]: Invalid key index 0 [FreeRDP_instance|FREERDP_SETTINGS_TYPE_POINTER] 2024-04-18T13:49:13.851716+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_int_assert]: FALSE [obj-x86_64-linux-gnu/libfreerdp/CMakeFiles/freerdp.dir/compiler_depend.ts:freerdp_settings_get_bool:637] 2024-04-18T13:49:13.851760+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 0: dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x70e694e2b000], dli_sname=winpr_backtrace [0x70e694e97660] 2024-04-18T13:49:13.851791+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 1: dli_fname=/lib/x86_64-linux-gnu/libwinpr3.so.3 [0x70e694e2b000], dli_sname=winpr_log_backtrace_ex [0x70e694e9f150] 2024-04-18T13:49:13.851803+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 2: dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x70e69420], dli_sname=(null) [(nil)] 2024-04-18T13:49:13.851815+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 3: dli_fname=/lib/x86_64-linux-gnu/libfreerdp3.so.3 [0x70e69420], dli_sname=freerdp_settings_get_bool [0x70e6942658a0] 2024-04-18T13:49:13.851827+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 4: dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so [0x70e6958dd000], dli_sname=(null) [(nil)] 2024-04-18T13:49:13.851839+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 5: dli_fname=/usr/lib/x86_64-linux-gnu/remmina/plugins/remmina-plugin-rdp.so [0x70e6958dd000], dli_sname=(null) [(nil)] 2024-04-18T13:49:13.851851+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 6: dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x70e69940], dli_sname=(null) [(nil)] 2024-04-18T13:49:13.851873+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 7: dli_fname=/usr/bin/../lib/x86_64-linux-gnu/libc.so.6 [0x70e69940], dli_sname=(null) [(nil)] 2024-04-18T13:49:13.851885+02:00 localhost org.remmina.Remmina.desktop[53441]: [13:49:13:572] [53441:d116] [FATAL][com.freerdp.winpr.assert] - [winpr_log_backtrace_ex]: 8: unresolvable, address=(nil) 2024-04-18T13:49:14.938231+02:00 localhost org.remmina.Remmina.desktop[53436]: /usr/bin/remmina-file-wrapper: line 37: 53441 Aborted (core dumped) "$REMMINA"
[Desktop-packages] [Bug 2060400] Re: Remmina crashes instantly when trying to open a remote session
bluppfisk (bluppfisk) i was be able to import all my conections of remmina in the snap version. I copy the conection files to the snap configuration folder: ~/snap/remmina/current/.local/share/remmina/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/2060400 Title: Remmina crashes instantly when trying to open a remote session Status in remmina package in Ubuntu: Confirmed Bug description: I've been testing Noble for a couple of weeks and Remmina has not been working. Fully upto date with regards to updates now and it's still crashing. The initial windows comes up allowing you to select a session. The various preference dialogues seem to work but as soon as you try to initiate a remote session it crashes instantly. No crash is shown on the command line. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: remmina 1.4.35+dfsg-0ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 7 20:17:02 2024 InstallationDate: Installed on 2024-03-25 (13 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240323) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: remmina UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/2060400/+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 2063153] Re: Incorrect display Graphics Card in System -> system details
** Tags added: noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2063153 Title: Incorrect display Graphics Card in System -> system details Status in gnome-control-center package in Ubuntu: New Bug description: NVIDIA GeForce RTX 3050 Ti Mobile should be displayed here To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2063153/+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 2063476] Re: libwebkit2gtk-4.0.so.37: undefined symbol: gbm_bo_create_with_modifiers2
** Tags added: xilinx ** Summary changed: - libwebkit2gtk-4.0.so.37: undefined symbol: gbm_bo_create_with_modifiers2 + Xilinx: libwebkit2gtk-4.0.so.37: undefined symbol: gbm_bo_create_with_modifiers2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2063476 Title: Xilinx: libwebkit2gtk-4.0.so.37: undefined symbol: gbm_bo_create_with_modifiers2 Status in gnome-control-center package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Bug description: Cannot run gnome-control-center due to missing symbol lookup. Please see the output of the console: ``` ubuntu@kria:~$ gnome-control-center -h gnome-control-center: symbol lookup error: /lib/aarch64-linux-gnu/libwebkit2gtk-4.0.so.37: undefined symbol: gbm_bo_create_with_modifiers2 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.8 ProcVersionSignature: Ubuntu 5.15.0-1027.31-xilinx-zynqmp 5.15.136 Uname: Linux 5.15.0-1027-xilinx-zynqmp aarch64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: nocloud CloudName: unknown CloudPlatform: nocloud CloudSubPlatform: config-disk (/dev/mmcblk1p1) Date: Thu Apr 25 16:57:26 2024 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2063476/+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 2063521] Re: nautilus uninstalled after installing fuse for Appimages
Looks like fuse3 is more likely the cause because fuse3 declares "Breaks: fuse". ** Package changed: nautilus (Ubuntu) => fuse3 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2063521 Title: nautilus uninstalled after installing fuse for Appimages Status in fuse3 package in Ubuntu: New Bug description: I was setting up a new install of Ubuntu 24.04 and installed fuse for a few Appimages I use and noticed that nautilus had been removed. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:46.0-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 26 13:20:35 2024 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small-plus'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' InstallationDate: Installed on 2024-04-26 (0 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: nautilus-extension-gnome-terminal 3.52.0-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse3/+bug/2063521/+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 2063452] Re: Xorg freeze
It looks like the kernel ran out of memory and the main culprit is a 'java' process. This is not an Ubuntu bug. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- 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/2063452 Title: Xorg freeze Status in Ubuntu: Invalid Bug description: My Ubuntu system crashes every time I use an application. It freezes, and I have to force the system to shut down in order to restart it for use, but the problem persists.Please help me ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 13:40:11 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation TigerLake-H GT1 [UHD Graphics] [8086:9a68] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] TigerLake-H GT1 [UHD Graphics] [1462:12eb] Subsystem: Micro-Star International Co., Ltd. [MSI] GA107M [GeForce RTX 3050 Mobile] [1462:12eb] InstallationDate: Installed on 2023-12-01 (145 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Micro-Star International Co., Ltd. Katana GF76 11UC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic root=UUID=0cd75e64-7400-4f1e-bbce-c9c2c1a67e8a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2021 dmi.bios.release: 3.14 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E17L2IMS.30E dmi.board.asset.tag: Default string dmi.board.name: MS-17L2 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE17L2IMS.30E:bd10/15/2021:br3.14:svnMicro-StarInternationalCo.,Ltd.:pnKatanaGF7611UC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17L2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17L2.3: dmi.product.family: GF dmi.product.name: Katana GF76 11UC dmi.product.sku: 17L2.3 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.10 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2063452/+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 2063503] Re: NVidia drivers won't install completely
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-550 (Ubuntu) ** Also affects: nvidia-graphics-drivers-545 (Ubuntu) Importance: Undecided Status: New -- 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/2063503 Title: NVidia drivers won't install completely Status in nvidia-graphics-drivers-545 package in Ubuntu: New Status in nvidia-graphics-drivers-550 package in Ubuntu: New Bug description: ll versions of the nvidia driver fail to install no matter what. Including the one downloaded from Nvidia. It doesn't matter the version. :~$ sudo apt install nvidia-driver-550 [sudo] password for jim: Reading package lists... Done Building dependency tree... Done Reading state information... Done The following package was automatically installed and is no longer required: nvidia-firmware-545-545.29.06 Use 'sudo apt autoremove' to remove it. The following additional packages will be installed: libnvidia-cfg1-550 libnvidia-common-550 libnvidia-compute-550 libnvidia-compute-550:i386 libnvidia-decode-550 libnvidia-decode-550:i386 libnvidia-encode-550 libnvidia-encode-550:i386 libnvidia-extra-550 libnvidia-fbc1-550 libnvidia-fbc1-550:i386 libnvidia-gl-550 libnvidia-gl-550:i386 nvidia-compute-utils-550 nvidia-dkms-550 nvidia-firmware-550-550.67 nvidia-kernel-common-550 nvidia-kernel-source-550 nvidia-utils-550 xserver-xorg-video-nvidia-550 The following packages will be REMOVED: libnvidia-cfg1-545 libnvidia-common-545 libnvidia-compute-545 libnvidia-compute-545:i386 libnvidia-decode-545 libnvidia-decode-545:i386 libnvidia-encode-545 libnvidia-encode-545:i386 libnvidia-extra-545 libnvidia-fbc1-545 libnvidia-fbc1-545:i386 libnvidia-gl-545 libnvidia-gl-545:i386 nvidia-compute-utils-545 nvidia-dkms-545 nvidia-driver-545 nvidia-kernel-common-545 nvidia-kernel-source-545 nvidia-utils-545 xserver-xorg-video-nvidia-545 The following NEW packages will be installed: libnvidia-cfg1-550 libnvidia-common-550 libnvidia-compute-550 libnvidia-compute-550:i386 libnvidia-decode-550 libnvidia-decode-550:i386 libnvidia-encode-550 libnvidia-encode-550:i386 libnvidia-extra-550 libnvidia-fbc1-550 libnvidia-fbc1-550:i386 libnvidia-gl-550 libnvidia-gl-550:i386 nvidia-compute-utils-550 nvidia-dkms-550 nvidia-driver-550 nvidia-firmware-550-550.67 nvidia-kernel-common-550 nvidia-kernel-source-550 nvidia-utils-550 xserver-xorg-video-nvidia-550 0 upgraded, 21 newly installed, 20 to remove and 15 not upgraded. 2 not fully installed or removed. Need to get 360 MB of archives. After this operation, 14.7 MB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://archive.ubuntu.com/ubuntu noble/multiverse amd64 nvidia-dkms-550 amd64 550.67-0ubuntu3 [35.8 kB] Get:2 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-cfg1-550 amd64 550.67-0ubuntu3 [155 kB] Get:3 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-common-550 all 550.67-0ubuntu3 [14.8 kB] Get:4 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-compute-550 amd64 550.67-0ubuntu3 [41.3 MB] Get:5 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-compute-550 i386 550.67-0ubuntu3 [41.2 MB] Get:6 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-decode-550 amd64 550.67-0ubuntu3 [2,028 kB] Get:7 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-decode-550 i386 550.67-0ubuntu3 [2,470 kB] Get:8 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-encode-550 i386 550.67-0ubuntu3 [115 kB] Get:9 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-encode-550 amd64 550.67-0ubuntu3 [105 kB] Get:10 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-extra-550 amd64 550.67-0ubuntu3 [72.9 kB] Get:11 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-fbc1-550 amd64 550.67-0ubuntu3 [56.4 kB] Get:12 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-fbc1-550 i386 550.67-0ubuntu3 [61.9 kB] Get:13 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 libnvidia-gl-550 amd64 550.67-0ubuntu3 [155 MB] Get:14 http://ca.archive.ubuntu.com/ubuntu noble/restricted i386 libnvidia-gl-550 i386 550.67-0ubuntu3 [33.8 MB] Get:15 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-compute-utils-550 amd64 550.67-0ubuntu3 [123 kB] Get:16 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-kernel-source-550 amd64 550.67-0ubuntu3 [41.7 MB] Get:17 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-firmware-550-550.67 amd64 550.67-0ubuntu3 [38.1 MB] Get:18 http://ca.archive.ubuntu.com/ubuntu noble/restricted amd64 nvidia-kernel-common-550 amd64 550.67-0ubuntu3
[Desktop-packages] [Bug 2063501] Re: Sometimes gnome-shell crash upon unlocking session from suspension
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Run these commands: journalctl -b0 > journal.txt journalctl -b-1 > prevjournal.txt and attach the resulting text files here. 2. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Changed in: xwayland (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/2063501 Title: Sometimes gnome-shell crash upon unlocking session from suspension Status in gnome-shell package in Ubuntu: Incomplete Status in xwayland package in Ubuntu: Incomplete Bug description: # journalctl _COMM=gnome-shell --since="20 minutes ago" -p warning Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:04 hostname gnome-shell[3682]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed Apr 25 23:36:04 hostname gnome-shell[3682]: JS ERROR: TypeError: this._settings is null getInt@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/common.js:136:9 _onMoving@file:///usr/share/gnome-shell/extensions/tiling-assist...@ubuntu.com/src/extension/moveHandler.js:361:38 @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:11 hostname gnome-shell[3682]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->l> Apr 25 23:36:32 hostname gnome-shell[190040]: Gio.UnixInputStream has been moved to a separate platform-specific library. Please update your code to use GioUn> 0 inhibit() ["resource:///org/gnome/shell/misc/loginManager.js":209:8] 1 InterpretGeneratorResume() ["self-hosted":1461:33] 2 AsyncFunctionNext() ["self-hosted":852:26] 3 anonymous() ["resource:///org/gnome/shell/ui/init.js":21:19] Apr 25 23:36:33 hostname gnome-shell[188828]: Connection to xwayland lost Apr 25 23:36:33 hostname gnome-shell[188828]: Xwayland terminated, exiting since it was mandatory Apr 25 23:36:33 hostname gnome-shell[188828]: JS ERROR: Gio.IOErrorEnum: Xwayland exited unexpectedly @resource:///org/gnome/shell/ui/init.js:21:20 Apr 25 23:36:40 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed Apr 25 23:36:54 hostname gnome-shell[190040]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xwayland 2:23.2.6-1 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2
[Desktop-packages] [Bug 2063049] Re: Google Chrome and Chromium 124 have a transparent window on Wayland
Tracking upstream in: https://issues.chromium.org/issues/329678163 ** Summary changed: - chromium snap doesnt launch properly on 24.04 + Google Chrome and Chromium 124 have a transparent window on Wayland ** Bug watch added: issues.chromium.org/issues #329678163 https://issues.chromium.org/issues/329678163 ** Also affects: chromium-browser via https://issues.chromium.org/issues/329678163 Importance: Unknown Status: Unknown ** Tags added: jammy ** Changed in: chromium-browser (Ubuntu) Importance: Undecided => Critical ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2063049 Title: Google Chrome and Chromium 124 have a transparent window on Wayland Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Triaged Bug description: chromium snap only launches with titlebar and transparent window after recent snap update on wayland and intel grafics. Adding --ozone-platform=wayland fixes the issue for me. (workaround from bug #1968610) ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: chromium-browser 2:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1 Uname: Linux 6.8.0-28-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: sway Date: Sun Apr 21 20:25:30 2024 DiskUsage: FilesystemType Size Used Avail Use% Mounted on rpool/ROOT/ubuntu_gk6kaa zfs 50G 7,7G 42G 16% / tmpfs tmpfs 16G 128M 16G 1% /dev/shm rpool/USERDATA/k1l_0tberh zfs437G 396G 42G 91% /home/k1l InstallationDate: Installed on 2022-03-24 (760 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321) ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= Snap.Changes: ID Status Spawn Ready Summary 635 Done2024-04-21T00:51:33+02:00 2024-04-21T00:52:11+02:00 Snap "chromium" aktualisieren Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60 (8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798}) Snap.ChromiumVersion: Chromium 124.0.6367.60 snap SourcePackage: chromium-browser UpgradeStatus: Upgraded to noble on 2024-03-25 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/2063049/+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 2063304] Re: chromium 124.0.6367.60 fails to draw its window
*** This bug is a duplicate of bug 2063049 *** https://bugs.launchpad.net/bugs/2063049 ** This bug has been marked a duplicate of bug 2063049 Google Chrome and Chromium 124 have a transparent window on Wayland -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2063304 Title: chromium 124.0.6367.60 fails to draw its window Status in chromium-browser package in Ubuntu: Confirmed Bug description: Since the last snap update to 124.0.6367.60, I cannot use chromium. It launches fine, but the window itself is fully transparent (e.g. triggering the Overview makes it look like a piece of my wallpaper). I have Intel graphics and use a Wayland session on Ubuntu 23.10. At first I thought I was experiencing bug 1967488, but the more I looked at it, the less sure I was (no Nvidia here, no issues with older snap versions, no KMS errors in journalctl), so I'm filing a new one. --- ProblemType: Bug ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p5 ext4 732G 483G 212G 70% / tmpfs tmpfs 7,7G 75M 7,6G 1% /dev/shm /dev/nvme0n1p5 ext4 732G 483G 212G 70% / DistroRelease: Ubuntu 23.10 EcryptfsInUse: Yes InstallationDate: Installed on 2019-06-12 (1777 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: chromium-browser 1:85.0.4183.83-0ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13 Snap.Changes: ID Status Spawn Ready Summary 824 Done2024-04-23T20:13:38+03:00 2024-04-23T20:28:35+03:00 Auto-refresh snap "chromium" Snap.ChromeDriverVersion: ChromeDriver 124.0.6367.60 (8771130bd84f76d855ae42fbe02752b03e352f17-refs/branch-heads/6367@{#798}) Snap.ChromiumVersion: Chromium 124.0.6367.60 snap Tags: mantic wayland-session Uname: Linux 6.5.0-28-generic x86_64 UpgradeStatus: Upgraded to mantic on 2023-10-13 (194 days ago) UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2063304/+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 2063336] Re: All Chromium based applications fail to render on Wayland
*** This bug is a duplicate of bug 2063049 *** https://bugs.launchpad.net/bugs/2063049 Since this isn't the first report of the problem, and is also confused by separate Nvidia issues, let's use bug 2063049 instead. ** Changed in: chromium-browser (Ubuntu) Milestone: ubuntu-24.04 => None ** This bug has been marked a duplicate of bug 2063049 Google Chrome and Chromium 124 have a transparent window on Wayland -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2063336 Title: All Chromium based applications fail to render on Wayland Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Confirmed Bug description: Most of the time (3/4 desktop sessions attempted) all Chromium based applications I have tested (Chromium, VS Code, Mattermost) fail to render themselves, on actual display panel presenting random garbage, and when screenshotted, showing supposedly transparent pixels. I have also recorded an example video I can share in case this is of use (attached the screenshot with the video). ProblemType: Bug DistroRelease: Ubuntu 24.04 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 16:21:15 2024 InstallationDate: Installed on 2021-11-08 (898 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Snap: chromium 124.0.6367.60 (latest/stable) SnapChanges: no changes found SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to noble on 2024-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/2063336/+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 2063341] Re: gnome-shell crashed with SIGSEGV
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Run these commands: journalctl -b0 > journal.txt journalctl -b-1 > prevjournal.txt and attach the resulting text files here. 2. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Summary changed: - Ubuntu crashesh after KVM swicth back/wake up/suspend + gnome-shell crashed with SIGSEGV ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2063341 Title: gnome-shell crashed with SIGSEGV Status in gnome-shell package in Ubuntu: Incomplete Bug description: I've been using Ubuntu for almost 2 years and it's been working fine. I use a KVM switch (built in Benq monitor) all the time. Since last month Ubuntu randomly crashes when I switch back to it. Or it could be wake up/suspend, I can't see when it exactly happens, it's just logging screen after crash. I am running: openVPN, firefox (dozen tabs), chrome (ms teams), slack, postman, 3x Intellij IDEA, VS Code System logs don't show anything meaningful to me or Google and I don't know how to get a clue as to what's going on. I suspect a new version of MS Teams that was introduced a few weeks ago. Please help me I cannot reproduce the crash or find anything on the web about it. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 15:59:03 2024 DisplayManager: gdm3 InstallationDate: Installed on 2022-08-31 (601 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.9-0ubuntu7 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2063341/+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 2063336] Re: All Chromium based applications fail to render on Wayland
Sounds like bug 1967488 might've got fixed in the past few months (which would be great news), worked for a while and then https://issues.chromium.org/issues/329678163 hit which affects all GPUs and OS releases. Also the glitchy rendering after typing is bug 1970389 (if not bug 2059847 on Xorg), but after that I have no more bad news because those are all the blockers for Wayland on Nvidia: https://bugs.launchpad.net/ubuntu/+bugs?field.tag=nvidia-wayland -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2063336 Title: All Chromium based applications fail to render on Wayland Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Confirmed Bug description: Most of the time (3/4 desktop sessions attempted) all Chromium based applications I have tested (Chromium, VS Code, Mattermost) fail to render themselves, on actual display panel presenting random garbage, and when screenshotted, showing supposedly transparent pixels. I have also recorded an example video I can share in case this is of use (attached the screenshot with the video). ProblemType: Bug DistroRelease: Ubuntu 24.04 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 16:21:15 2024 InstallationDate: Installed on 2021-11-08 (898 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Snap: chromium 124.0.6367.60 (latest/stable) SnapChanges: no changes found SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to noble on 2024-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/2063336/+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 2063336] Re: All Chromium based applications fail to render (dual NVIDIA GPU system)
Fixed upstream today? https://issues.chromium.org/issues/329678163 ** Also affects: chromium-browser via https://issues.chromium.org/issues/329678163 Importance: Unknown Status: Unknown ** Summary changed: - All Chromium based applications fail to render (dual NVIDIA GPU system) + All Chromium based applications fail to render on Wayland -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2063336 Title: All Chromium based applications fail to render on Wayland Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Confirmed Bug description: I am noticing two - Most of the time (3/4 desktop sessions attempted) all Chromium based applications I have tested (Chromium, VS Code, Mattermost) fail to render themselves, on actual display panel presenting random garbage, and when screenshotted, showing supposedly showing transparent pixels. I have also recorded an example video I can share in case this is of use (attached the screenshot with the video). ProblemType: Bug DistroRelease: Ubuntu 24.04 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 16:21:15 2024 InstallationDate: Installed on 2021-11-08 (898 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Snap: chromium 124.0.6367.60 (latest/stable) SnapChanges: no changes found SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to noble on 2024-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/2063336/+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 2063336] Re: All Chromium based applications fail to render (dual NVIDIA GPU system)
If you're using Nvidia as the primary GPU though, it was never working according to bug 1967488. ** Bug watch added: issues.chromium.org/issues #329678163 https://issues.chromium.org/issues/329678163 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2063336 Title: All Chromium based applications fail to render on Wayland Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Confirmed Bug description: I am noticing two - Most of the time (3/4 desktop sessions attempted) all Chromium based applications I have tested (Chromium, VS Code, Mattermost) fail to render themselves, on actual display panel presenting random garbage, and when screenshotted, showing supposedly showing transparent pixels. I have also recorded an example video I can share in case this is of use (attached the screenshot with the video). ProblemType: Bug DistroRelease: Ubuntu 24.04 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 16:21:15 2024 InstallationDate: Installed on 2021-11-08 (898 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Snap: chromium 124.0.6367.60 (latest/stable) SnapChanges: no changes found SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to noble on 2024-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/2063336/+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 2063336] Re: All Chromium based applications fail to render (dual NVIDIA GPU system)
It's a Chromium bug. Same is happening with Google Chrome on jammy with Intel graphics. Workaround: google-chrome --ozone-platform=x11 ** Changed in: ubuntu Status: New => Invalid ** Package changed: ubuntu => chromium-browser (Ubuntu) ** Changed in: chromium-browser (Ubuntu) Status: Invalid => Confirmed ** Tags added: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2063336 Title: All Chromium based applications fail to render on Wayland Status in Chromium Browser: Unknown Status in chromium-browser package in Ubuntu: Confirmed Bug description: I am noticing two - Most of the time (3/4 desktop sessions attempted) all Chromium based applications I have tested (Chromium, VS Code, Mattermost) fail to render themselves, on actual display panel presenting random garbage, and when screenshotted, showing supposedly showing transparent pixels. I have also recorded an example video I can share in case this is of use (attached the screenshot with the video). ProblemType: Bug DistroRelease: Ubuntu 24.04 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: zfs nvidia_modeset nvidia ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 16:21:15 2024 InstallationDate: Installed on 2021-11-08 (898 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Snap: chromium 124.0.6367.60 (latest/stable) SnapChanges: no changes found SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to noble on 2024-04-24 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/2063336/+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 1926863] Re: gjs process (desktop-icons-ng extension) eats all available RAM and Freezes Computer
Thank you for reporting this bug to Ubuntu. Ubuntu 23.04 (lunar) reached end-of-life on January 25, 2024. Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it anymore. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. https://bugs.launchpad.net/bugs/1926863 Title: gjs process (desktop-icons-ng extension) eats all available RAM and Freezes Computer Status in Gnome Shell Extension Desktop Icons Ng: New Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Won't Fix Bug description: Title sums it up. Just upgraded to 21.04 from 20.10, and gjs has now three times eaten all memory and frozen the everything solid. Some sort of massive memory leak. I caught a screenshot of it doing it, ticks up about 1/10th GB every few seconds until computer goes bye-bye. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gjs 1.67.2-2ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 1 19:22:11 2021 InstallationDate: Installed on 2020-05-07 (359 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gjs UpgradeStatus: Upgraded to hirsute on 2021-05-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1926863/+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 2063312] Re: gjs error restart show icon desktop
This is recurring in the log. I wonder if there are more Desktop files than it can handle: [ 4576.663765] u-hcm-dkp-026 gnome-shell[2229]: DING: (gjs:23000): GLib-ERROR **: 08:05:34.803: Creating pipes for GWakeup: Too many open files [ 4579.212965] u-hcm-dkp-026 gnome-shell[2229]: DING: Detected async api for thumbnails [ 4579.267543] u-hcm-dkp-026 gnome-shell[2229]: DING: GNOME nautilus 42.6 [ 4581.476956] u-hcm-dkp-026 gnome-shell[2229]: DING: (gjs:23081): GLib-ERROR **: 08:05:39.617: Creating pipes for GWakeup: Too many open files [ 4583.855992] u-hcm-dkp-026 gnome-shell[2229]: DING: Detected async api for thumbnails [ 4583.910279] u-hcm-dkp-026 gnome-shell[2229]: DING: GNOME nautilus 42.6 [ 4591.667699] u-hcm-dkp-026 gnome-shell[2229]: DING: (gjs:23118): GLib-ERROR **: 08:05:49.807: Creating pipes for GWakeup: Too many open files [ 4594.203465] u-hcm-dkp-026 gnome-shell[2229]: DING: Detected async api for thumbnails [ 4594.274686] u-hcm-dkp-026 gnome-shell[2229]: DING: GNOME nautilus 42.6 ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- desktop-icons-ng (Ubuntu) -- 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/2063312 Title: gjs error restart show icon desktop Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Bug description: There is a bug when I start my computer. After 2 seconds, the icon on the desktop is not show and shows again. I checked the CPU% processes is max in CPU 3 over 100%. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 15:16:23 2024 DisplayManager: gdm3 InstallationDate: Installed on 2023-03-28 (392 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RelatedPackageVersions: mutter-common 42.9-0ubuntu7 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/2063312/+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 2037015] Re: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install
** Description changed: + [ Impact ] + + Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as + during install. + + [ Test Plan ] + + 1. Open the default Help app by clicking the question mark icon in the + dock or by running 'yelp'. + + 2. Verify it didn't crash and the window contents are not corrupt. + + [ Where problems could occur ] + + The fix is limited to webkit2gtk so can only affect apps such as yelp or + the Raspberry Pi installer. + + [ Other Info ] + During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. ** Description changed: [ Impact ] Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install. [ Test Plan ] - 1. Open the default Help app by clicking the question mark icon in the + 1. Log into a Xorg session on a Raspberry Pi 4/400. + + 2. Open the default Help app by clicking the question mark icon in the dock or by running 'yelp'. - 2. Verify it didn't crash and the window contents are not corrupt. + 3. Verify it didn't crash and the window contents are not corrupt. [ Where problems could occur ] The fix is limited to webkit2gtk so can only affect apps such as yelp or the Raspberry Pi installer. [ Other Info ] During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2037015 Title: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install Status in Webkit: Confirmed Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: In Progress Bug description: [ Impact ] Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install. [ Test Plan ] 1. Log into a Xorg session on a Raspberry Pi 4/400. 2. Open the default Help app by clicking the question mark icon in the dock or by running 'yelp'. 3. Verify it didn't crash and the window contents are not corrupt. [ Where problems could occur ] The fix is limited to webkit2gtk so can only affect apps such as yelp or the Raspberry Pi installer. [ Other Info ] During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2037015/+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 2037015] Re: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install
Confirmed this fix is now working: https://salsa.debian.org/webkit-team/webkit/-/merge_requests/20 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2037015 Title: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install Status in Webkit: Confirmed Status in mesa package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: In Progress Bug description: [ Impact ] Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install. [ Test Plan ] 1. Log into a Xorg session on a Raspberry Pi 4/400. 2. Open the default Help app by clicking the question mark icon in the dock or by running 'yelp'. 3. Verify it didn't crash and the window contents are not corrupt. [ Where problems could occur ] The fix is limited to webkit2gtk so can only affect apps such as yelp or the Raspberry Pi installer. [ Other Info ] During the initial configuration of the Ubuntu Desktop for Raspberry Pi (the oem-config process, derived from ubiquity), on the Mantic beta images, after the various pages of information have been filled out and the process moves onto configuration, the "slide deck" that is usually displayed during the process appeared corrupted as if a horizontal stride were incorrectly set somewhere. I'm attached a photo of the screen (as, while I could take a screenshot during the process, it evidently wasn't saved somewhere persistent). I originally thought this might be a regression of LP: #1924251 as the corruption in the window looks very similar (incorrect horizontal stride causing "banding"), but I tested the embedded browser (via the help system) after completing setup and it worked perfectly so that's *probably* unrelated. To manage notifications about this bug go to: https://bugs.launchpad.net/webkit/+bug/2037015/+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 1967488] Re: [nvidia] Chromium stable snap doesn't display anything on Wayland with Nvidia as primary GPU
That's a Chromium/Chrome regression and is not related to this Nvidia bug at all. Still, you can work around it with: google-chrome --ozone-platform=x11 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1967488 Title: [nvidia] Chromium stable snap doesn't display anything on Wayland with Nvidia as primary GPU Status in chromium-browser package in Ubuntu: Triaged Bug description: Hi I'm testing the Ubuntu 22.04 beta with wayland and when I try to open the Chromium browser (stable snap package), only see a black/transparent window. If I switch from Wayland to Xorg, everything is normal again. I tried to delete the profile folder , but I have the same result. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1967488/+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 2062146] Re: Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile
** Changed in: mesa (Ubuntu) Status: Invalid => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/2062146 Title: Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile Status in Mesa: New Status in mesa package in Ubuntu: Triaged Status in webkit2gtk package in Ubuntu: In Progress Status in yelp package in Ubuntu: New Bug description: MiniBrowser crashed immediately on Raspberry Pi 400. ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: libwebkit2gtk-4.1-0 2.44.0-2 ProcVersionSignature: Ubuntu 6.8.0-1002.2-raspi 6.8.1 Uname: Linux 6.8.0-1002-raspi aarch64 ApportVersion: 2.28.0-0ubuntu1 Architecture: arm64 CasperMD5CheckResult: unknown CloudArchitecture: aarch64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 17:32:12 2024 ExecutablePath: /usr/lib/aarch64-linux-gnu/webkit2gtk-4.1/MiniBrowser JournalErrors: -- No entries -- ProcCmdline: ./MiniBrowser ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= Signal: 11 SignalName: SIGSEGV SourcePackage: webkit2gtk StacktraceTop: ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so ?? () from /lib/aarch64-linux-gnu/libgbm.so.1 ?? () from /lib/aarch64-linux-gnu/libwebkit2gtk-4.1.so.0 Title: MiniBrowser crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2062146/+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 2061856] Re: Apps are closing immediately instead of launching
** Package changed: xorg (Ubuntu) => 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/2061856 Title: Apps are closing immediately instead of launching Status in Ubuntu: Incomplete Bug description: Ola Bomdia Eu estou com um problema no terminal shell do ubuntu ele esta fechando assim que clico para abrir elefecha automaticamente ja tentetei usar outro terminal e tambem faz a mesma coisa eu tenho o fish instalado tambem mas esta fazendo a mesma coisa fechando automaticamente, o unico que funciona e o terminal do vscode. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-213.224-generic 4.15.18 Uname: Linux 4.15.0-213-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.29 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Apr 16 12:04:00 2024 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 12) (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems Core Processor Integrated Graphics Controller [1019:1324] InstallationDate: Installed on 2023-07-23 (267 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170215.2) Lsusb: Bus 002 Device 006: ID 04f3:0210 Elan Microelectronics Corp. Optical Mouse Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MEGAWARE H55H-CM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-213-generic root=UUID=3cfdb2f5-e8ec-4728-844a-29c984321037 ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MW-H55H-CM dmi.board.vendor: MEGAWARE dmi.board.version: 1.0 dmi.chassis.asset.tag: M0418501001 dmi.chassis.type: 3 dmi.chassis.vendor: MEGAWARE dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/18/2010:svnMEGAWARE:pnH55H-CM:pvrMEGAWARE:rvnMEGAWARE:rnMW-H55H-CM:rvr1.0:cvnMEGAWARE:ct3:cvr1.0: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: H55H-CM dmi.product.version: MEGAWARE dmi.sys.vendor: MEGAWARE version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.15 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Apr 4 13:22:01 2024 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputPS/2+USB Mouse MOUSE, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2061856/+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 2063228] Re: screen sometimes blinking
Please try adding a kernel parameter: i915.enable_psr=0 ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2063228 Title: screen sometimes blinking Status in linux package in Ubuntu: Incomplete Bug description: My screen sometimes starts flashing strongly. I move the mouse cursor, it stops. I put the cursor back in its place, it starts again. I notice this with Firefox because I use it a lot, I don't know if this happens with other software. I'm under wayland (xwayland?) Description: Ubuntu 24.04 LTS Release: 24.04 ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 18:57:50 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620] [103c:84bb] InstallationDate: Installed on 2024-04-07 (16 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.2) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 003: ID 04ca:707f Lite-On Technology Corp. HP Wide Vision HD Camera Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 4.2 Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub MachineType: HP HP Pavilion Laptop 14-ce2xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=51f857d1-b81e-42fb-b485-6d1bf22759e4 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/23/2022 dmi.bios.release: 15.27 dmi.bios.vendor: Insyde dmi.bios.version: F.27 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84BB dmi.board.vendor: HP dmi.board.version: 15.32 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 15.32 dmi.modalias: dmi:bvnInsyde:bvrF.27:bd11/23/2022:br15.27:efr15.32:svnHP:pnHPPavilionLaptop14-ce2xxx:pvrType1ProductConfigId:rvnHP:rn84BB:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku8KZ34EA#ABF: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 14-ce2xxx dmi.product.sku: 8KZ34EA#ABF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063228/+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 2060391] Re: gnome desktop cannot start as mutter fails to find drmModeCloseFB
Invalid - please uninstall /opt/amdgpu/... which presumably is not from Ubuntu. ** Package changed: mutter (Ubuntu) => ubuntu ** Changed in: ubuntu Status: Incomplete => Invalid ** Summary changed: - gnome desktop cannot start as mutter fails to find drmModeCloseFB + gnome desktop cannot start as mutter fails to find drmModeCloseFB (when the 3rd party amdgpu driver is installed) -- 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/2060391 Title: gnome desktop cannot start as mutter fails to find drmModeCloseFB (when the 3rd party amdgpu driver is installed) Status in Ubuntu: Invalid Bug description: mutter: symbol lookup error: /lib/x86_64-linux-gnu/libmutter-14.so.0: undefined symbol: drmModeCloseFB Package libdrm2: i 2.4.120-2 noble 500 Package libdrm2:i386: i 2.4.120-2 noble 500 Package libmutter-14-0: i 46.0-1ubuntu6 noble 500 Package mutter: i 46.0-1ubuntu6 noble 500 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2060391/+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 2063222] Re: Ghost "unknown display" since upgrading to 24.04 beta
*** This bug is a duplicate of bug 2060268 *** https://bugs.launchpad.net/bugs/2060268 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 2060268, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-535 (Ubuntu) ** This bug has been marked a duplicate of bug 2060268 Phantom monitor (simpledrm) shown in Settings after installing the Nvidia driver -- 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/2063222 Title: Ghost "unknown display" since upgrading to 24.04 beta Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: X11 GNOME NVIDIA 4080 with their driver -> GNOME settings has a "ghost" display called "Unknown Display", its resolution is 1024 x 768 I only have one display attached - a 4K 27" DELL plugged into the NVIDIA ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.171.04 Tue Mar 19 20:30:00 UTC 2024 GCC version: gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu4) ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 08:55:55 2024 DistUpgraded: 2024-04-14 17:14:28,561 DEBUG migrateToDeb822Sources() DistroCodename: noble DistroVariant: ubuntu DkmsStatus: nvidia/535.171.04, 6.8.0-28-generic, x86_64: installed nvidia/535.171.04, 6.8.0-31-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Subsystem: Micro-Star International Co., Ltd. [MSI] AlderLake-S GT1 [1462:7d25] NVIDIA Corporation AD103 [GeForce RTX 4080] [10de:2704] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] AD103 [GeForce RTX 4080] [1462:5111] InstallationDate: Installed on 2022-04-30 (724 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Micro-Star International Co., Ltd. MS-7D25 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: root=UUID=43e064ac-5857-4c85-b15d-1dd96cdad27b ro quiet splash vt.handoff=7 initrd=boot\initrd.img-6.8.0-31-generic SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to noble on 2024-04-15 (9 days ago) dmi.bios.date: 11/13/2023 dmi.bios.release: 5.27 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: A.F0 dmi.board.asset.tag: Default string dmi.board.name: PRO Z690-A WIFI (MS-7D25) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.F0:bd11/13/2023:br5.27:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D25:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-AWIFI(MS-7D25):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuDefaultstring: dmi.product.family: Default string dmi.product.name: MS-7D25 dmi.product.sku: Default string dmi.product.version: 2.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau:
[Desktop-packages] [Bug 2062377] Re: Ubuntu 24.04: gnome-shell crashes on Xorg if a legacy X11 cursor theme is selected
In progress: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3718 -- 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/2062377 Title: Ubuntu 24.04: gnome-shell crashes on Xorg if a legacy X11 cursor theme is selected Status in mutter package in Ubuntu: In Progress Bug description: 1)Go to xorg 2)Download Gnome Tweak Tool 3)Select DMZ-white 4)crash from the system ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.161.07 Sat Feb 17 22:55:48 UTC 2024 GCC version: ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 17:38:02 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Acer Incorporated [ALI] GA107M [GeForce RTX 3050 Ti Mobile] [1025:1524] Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Lucienne [1025:1524] InstallationDate: Installed on 2024-04-17 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417.2) MachineType: Acer Aspire A715-42G ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic root=UUID=12cf9ac8-f034-465e-92e4-0c64e47e2350 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Azalea_CAS dmi.board.vendor: LN dmi.board.version: V1.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd02/19/2021:br1.2:efr1.2:svnAcer:pnAspireA715-42G:pvrV1.02:rvnLN:rnAzalea_CAS:rvrV1.02:cvnAcer:ct10:cvrV1.02:sku: dmi.product.family: Aspire 7 dmi.product.name: Aspire A715-42G dmi.product.sku: dmi.product.version: V1.02 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2062377/+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 2063147] Re: No lower VRR range for display shown in Settings
** Summary changed: - No lower VRR range for display + No lower VRR range for display shown in Settings ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/3434 Importance: Unknown Status: Unknown ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu) Status: Incomplete => Triaged -- 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/2063147 Title: No lower VRR range for display shown in Settings Status in Mutter: Unknown Status in mutter package in Ubuntu: Triaged Bug description: Description: Ubuntu Noble Numbat (development branch) Release: 24.04 Package: mutter Version: 46.0-1ubuntu9 mutter is built without libdisplay-info and this is required for having lower VRR range for display. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2063147/+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 2062377] Re: Ubuntu 24.04: gnome-shell crashes on Xorg if a legacy X11 cursor theme is selected
** Changed in: mutter (Ubuntu) Status: Triaged => In Progress -- 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/2062377 Title: Ubuntu 24.04: gnome-shell crashes on Xorg if a legacy X11 cursor theme is selected Status in mutter package in Ubuntu: In Progress Bug description: 1)Go to xorg 2)Download Gnome Tweak Tool 3)Select DMZ-white 4)crash from the system ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.161.07 Sat Feb 17 22:55:48 UTC 2024 GCC version: ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 17:38:02 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Acer Incorporated [ALI] GA107M [GeForce RTX 3050 Ti Mobile] [1025:1524] Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Lucienne [1025:1524] InstallationDate: Installed on 2024-04-17 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417.2) MachineType: Acer Aspire A715-42G ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic root=UUID=12cf9ac8-f034-465e-92e4-0c64e47e2350 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Azalea_CAS dmi.board.vendor: LN dmi.board.version: V1.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd02/19/2021:br1.2:efr1.2:svnAcer:pnAspireA715-42G:pvrV1.02:rvnLN:rnAzalea_CAS:rvrV1.02:cvnAcer:ct10:cvrV1.02:sku: dmi.product.family: Aspire 7 dmi.product.name: Aspire A715-42G dmi.product.sku: dmi.product.version: V1.02 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2062377/+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 2062377] Re: Ubuntu 24.04: gnome-shell crashes on Xorg if a legacy X11 cursor theme is selected
Confirmed: #6 0x7da91c9077fb in _XError () at /lib/x86_64-linux-gnu/libX11.so.6 #7 0x7da91c90790f in ??? () at /lib/x86_64-linux-gnu/libX11.so.6 #8 0x7da91c9079cd in ??? () at /lib/x86_64-linux-gnu/libX11.so.6 #9 0x7da91c90971d in _XReply () at /lib/x86_64-linux-gnu/libX11.so.6 #10 0x7da91c909aa5 in XSync () at /lib/x86_64-linux-gnu/libX11.so.6 #11 0x7da91c909b3f in ??? () at /lib/x86_64-linux-gnu/libX11.so.6 #12 0x7da91c8e0b2d in XFreeCursor () at /lib/x86_64-linux-gnu/libX11.so.6 #13 0x7da91cf73c85 in meta_cursor_renderer_x11_update_cursor (renderer=0x5f58cdeed1a0, cursor_sprite=0x5f58cdc29790) at ../src/backends/x11/meta-cursor-renderer-x11.c:113 #14 0x7da91cec592f in meta_cursor_renderer_update_cursor (renderer=0x5f58cdeed1a0, cursor_sprite=0x5f58cdc29790) at ../src/backends/meta-cursor-renderer.c:425 #15 0x7da91cec5a3c in meta_cursor_renderer_force_update (renderer=0x5f58cdeed1a0) at ../src/backends/meta-cursor-renderer.c:460 #16 0x7da91cf7121e in meta_backend_x11_reload_cursor (x11=0x5f58cdc05470) at ../src/backends/x11/meta-backend-x11.c:1121 #17 0x7da91cfa0754 in update_cursor_theme (x11_display=0x5f58cdfd9b30) at ../src/x11/meta-x11-display.c:1757 #18 0x7da91dbb86bd in ??? () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 #19 0x7da91dbb87c1 in g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.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/2062377 Title: Ubuntu 24.04: gnome-shell crashes on Xorg if a legacy X11 cursor theme is selected Status in mutter package in Ubuntu: In Progress Bug description: 1)Go to xorg 2)Download Gnome Tweak Tool 3)Select DMZ-white 4)crash from the system ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.161.07 Sat Feb 17 22:55:48 UTC 2024 GCC version: ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 18 17:38:02 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Acer Incorporated [ALI] GA107M [GeForce RTX 3050 Ti Mobile] [1025:1524] Advanced Micro Devices, Inc. [AMD/ATI] Lucienne [1002:164c] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Lucienne [1025:1524] InstallationDate: Installed on 2024-04-17 (1 days ago) InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240417.2) MachineType: Acer Aspire A715-42G ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic root=UUID=12cf9ac8-f034-465e-92e4-0c64e47e2350 ro quiet splash vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Azalea_CAS dmi.board.vendor: LN dmi.board.version: V1.02 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd02/19/2021:br1.2:efr1.2:svnAcer:pnAspireA715-42G:pvrV1.02:rvnLN:rnAzalea_CAS:rvrV1.02:cvnAcer:ct10:cvrV1.02:sku: dmi.product.family: Aspire 7 dmi.product.name: Aspire A715-42G dmi.product.sku: dmi.product.version: V1.02 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1