[Desktop-packages] [Bug 2037641] Re: amdgpu: [gfxhub0] no-retry page fault
The process is Intellij IDEA, running on Java 17 in Xwayland. -- 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/2037641 Title: amdgpu: [gfxhub0] no-retry page fault Status in linux package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Bug description: Whenever I use Intellij IDEA, after a couple of minutes the screen locks up and pretty much renders the machine unusable. I can still ssh to it, but the UI is pretty much gone and doesn't respond to Ctrl+Alt+F* keys. The setup: the machine is connected to an external monitor via USB-C. Running kernel 6.5 on Ubuntu 23.10. There's the following in kern.log: ``` 2023-09-28T13:58:23.077679+03:00 mavi-ThinkPad-T14s kernel: [ 422.206433] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077694+03:00 mavi-ThinkPad-T14s kernel: [ 422.206450] amdgpu :06:00.0: amdgpu: in page starting at address 0xb15852923000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077695+03:00 mavi-ThinkPad-T14s kernel: [ 422.206460] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077696+03:00 mavi-ThinkPad-T14s kernel: [ 422.206466] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077698+03:00 mavi-ThinkPad-T14s kernel: [ 422.206471] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206476] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206481] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077700+03:00 mavi-ThinkPad-T14s kernel: [ 422.206485] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206490] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206497] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077702+03:00 mavi-ThinkPad-T14s kernel: [ 422.206506] amdgpu :06:00.0: amdgpu: in page starting at address 0xb07248096000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077703+03:00 mavi-ThinkPad-T14s kernel: [ 422.206514] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206519] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206524] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206528] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206533] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077706+03:00 mavi-ThinkPad-T14s kernel: [ 422.206538] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077707+03:00 mavi-ThinkPad-T14s kernel: [ 422.206542] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077708+03:00 mavi-ThinkPad-T14s kernel: [ 422.206549] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077709+03:00 mavi-ThinkPad-T14s kernel: [ 422.206556] amdgpu :06:00.0: amdgpu: in page starting at address 0xaf8c3d808000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206564] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206569] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077711+03:00 mavi-ThinkPad-T14s kernel: [ 422.206574] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206578] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206583] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077713+03:00 mavi-ThinkPad-T14s kernel: [ 422.206588] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077713+03:00 mavi-ThinkPad-T14s kernel: [ 422.206592] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077726+03:00 mavi-ThinkPad-T14s kernel: [ 422.206597]
[Desktop-packages] [Bug 2037641] Re: amdgpu: [gfxhub0] no-retry page fault
Unfortunately the problem is still reproducible even with the newest mesa, even though it looks like it's much less frequent. Yesterday evening I got another crash, with mesa 23.2.1-1ubuntu2: ``` 2023-10-04T22:33:15.415854+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119146] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:4 pasid:32770, for process Xwayland pid 4940 thread Xwayland:cs0 pid 5015) 2023-10-04T22:33:15.415871+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119168] amdgpu :06:00.0: amdgpu: in page starting at address 0xe5ea2326e000 from IH client 0x1b (UTCL2) 2023-10-04T22:33:15.415873+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119180] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00400430 2023-10-04T22:33:15.415874+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119187] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-10-04T22:33:15.415875+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119194] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x0 2023-10-04T22:33:15.415876+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119200] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-10-04T22:33:15.415878+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119206] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-10-04T22:33:15.415878+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119212] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-10-04T22:33:15.415879+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119218] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-10-04T22:33:15.415881+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119750] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:4 pasid:32770, for process Xwayland pid 4940 thread Xwayland:cs0 pid 5015) 2023-10-04T22:33:15.415881+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119768] amdgpu :06:00.0: amdgpu: in page starting at address 0xe5ea2326f000 from IH client 0x1b (UTCL2) 2023-10-04T22:33:15.415883+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119780] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00400430 2023-10-04T22:33:15.415884+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119787] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-10-04T22:33:15.415885+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119793] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x0 2023-10-04T22:33:15.415885+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119800] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-10-04T22:33:15.415886+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119806] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-10-04T22:33:15.415887+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119812] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-10-04T22:33:15.415888+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119818] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-10-04T22:33:25.115577+03:00 mavi-ThinkPad-T14s kernel: [ 1085.820288] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_low timeout, signaled seq=75561, emitted seq=75563 2023-10-04T22:33:25.115600+03:00 mavi-ThinkPad-T14s kernel: [ 1085.821169] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xwayland pid 4940 thread Xwayland:cs0 pid 5015 2023-10-04T22:33:25.115602+03:00 mavi-ThinkPad-T14s kernel: [ 1085.822031] amdgpu :06:00.0: amdgpu: GPU reset begin! 2023-10-04T22:33:25.347547+03:00 mavi-ThinkPad-T14s kernel: [ 1086.052065] [drm] psp gfx command UNLOAD_TA(0x2) failed and response status is (0x117) 2023-10-04T22:33:25.375820+03:00 mavi-ThinkPad-T14s kernel: [ 1086.078048] amdgpu :06:00.0: amdgpu: MODE2 reset 2023-10-04T22:33:25.375835+03:00 mavi-ThinkPad-T14s kernel: [ 1086.078296] amdgpu :06:00.0: amdgpu: GPU reset succeeded, trying to resume 2023-10-04T22:33:25.375837+03:00 mavi-ThinkPad-T14s kernel: [ 1086.078498] [drm] PCIE GART of 1024M enabled. 2023-10-04T22:33:25.375838+03:00 mavi-ThinkPad-T14s kernel: [ 1086.078503] [drm] PTB located at 0x00F43FC0 2023-10-04T22:33:25.375839+03:00 mavi-ThinkPad-T14s kernel: [ 1086.078625] [drm] PSP is resuming... 2023-10-04T22:33:26.075542+03:00 mavi-ThinkPad-T14s kernel: [ 1086.780162] [drm] reserve 0x40 from 0xf43f80 for PSP TMR 2023-10-04T22:33:26.363527+03:00 mavi-ThinkPad-T14s kernel: [ 1087.066834] amdgpu :06:00.0: amdgpu: RAS: optional ras ta ucode is not available 2023-10-04T22:33:26.375796+03:00 mavi-ThinkPad-T14s kernel: [ 1087.078189] amdgpu :06:00.0: amdgpu: RAP: optional rap ta ucode is not available 2023-10-04T22:33:26.375806+03:00 mavi-ThinkPad-T14s kernel: [ 1087.078196] amdgpu :06:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available 2023-10-04T22:33:26.375808+03:00 mavi-ThinkPad-T14s kernel: [ 1087.078204] amdgpu :06:00.0: amdgpu: SMU is resuming... 2023-10-04T22:33:26.375809+03:00 mavi-ThinkPad-T14s kernel: [ 1087.079063] amdgpu :06:00.0: amdgpu: SMU is resumed
[Desktop-packages] [Bug 1970389] Re: [nvidia] Janky text entry and frames appear out of order in Xwayland apps
** Changed in: xwayland (Ubuntu) Milestone: jammy-updates => None ** Changed in: xwayland (Ubuntu) Status: Confirmed => Triaged -- 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/1970389 Title: [nvidia] Janky text entry and frames appear out of order in Xwayland apps Status in X.Org X server: New Status in xwayland package in Ubuntu: Triaged Bug description: When writing into text fields in some applications (Firefox, VS Code) on Jammy in a GNOME / Wayland session, I can see an effect best described as the glyphs appearing / disappearing sometimes repeatedly. I have attached a recording from my phone (since attempting to record a screencast fails). This doesn't happen always, and it appear somehow sensitive to some environmental condition (load?) since for example when I'm on a video call, the effect seems to not be happening so often. I have also experienced a few instances of a currently not-focused window disappearing (seeing through to a window that is below that window), but cannot reproduce that reliably. I have the NVIDIA driver 510 in use, RTX3090-only 16-core Zen1 Threadripper system with no integrated GPU. No similar effects visible when in a GNOME / Xorg session. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 12:17:02 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-11-08 (168 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-22 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1970389/+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 1978905] Re: Reverse PRIME support for Wayland (Nvidia as primary GPU outputting to Intel GPU display ports)
** No longer affects: nvidia-graphics-drivers-510 (Ubuntu) -- 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/1978905 Title: Reverse PRIME support for Wayland (Nvidia as primary GPU outputting to Intel GPU display ports) Status in Mutter: New Status in mutter package in Ubuntu: Triaged Bug description: Reverse PRIME support for Wayland (Nvidia as primary GPU outputting to Intel GPU display ports) This is different to the usual dual GPU setup where Intel is primary and Nvidia is secondary. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1978905/+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 2016933] Re: X-Plane 11 doesn't start on Wayland if offloaded to the discrete Nvidia GPU
** No longer affects: nvidia-graphics-drivers-530 (Ubuntu) -- 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/2016933 Title: X-Plane 11 doesn't start on Wayland if offloaded to the discrete Nvidia GPU Status in xwayland package in Ubuntu: New Bug description: On Wayland only, offloading works for `glxinfo` but cannot run 3D app like X-Plane 11: $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia glxinfo | grep "OpenGL vendor string" OpenGL vendor string: NVIDIA Corporation $ __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia ./X-Plane\ 11/X-Plane-x86_64 Whoah -- no matter how hard I tried, I failed to get a GLX visual. Something's seriously wonky on your machine. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nvidia-driver-530 (not installed) ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Apr 19 04:30:34 2023 InstallationDate: Installed on 2023-01-04 (104 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) SourcePackage: nvidia-graphics-drivers-530 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/2016933/+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 1967707] Re: Nvidia Wayland sessions sometimes flood the log with "clutter_frame_clock_notify_presented: code should not be reached"
** 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/1967707 Title: Nvidia Wayland sessions sometimes flood the log with "clutter_frame_clock_notify_presented: code should not be reached" Status in Mutter: New Status in mutter package in Ubuntu: In Progress Bug description: Nvidia Wayland sessions sometimes flood the log with: [ 13.105877] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.106163] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.112490] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.125302] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached [ 13.142242] computer gnome-shell[1264]: (../clutter/clutter/clutter-frame-clock.c:332):clutter_frame_clock_notify_presented: code should not be reached I've been seeing the issue for months although it only seems to happen *after* something has gone wrong in mutter. Not by default. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1967707/+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 1968610] Re: Chromium/Brave snap doesn't launch correctly Ubuntu 22.04 on Wayland, Nvidia
*** This bug is a duplicate of bug 1967488 *** https://bugs.launchpad.net/bugs/1967488 Let's merge this into 1967488, I think it's been resolved recently. ** This bug has been marked a duplicate of bug 1967488 Chromium stable snap don't work on Wayland (NVIDIA 510.60.02 driver) -- 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/1968610 Title: Chromium/Brave snap doesn't launch correctly Ubuntu 22.04 on Wayland, Nvidia Status in chromium-browser package in Ubuntu: Confirmed Bug description: When launching Chromium as a snap on Ubuntu 22.04, it will not open properly and will open the browser with only the titlebar and a transparent window. I am using an Nvidia Graphics card with the 510.60.02 Nvidia proprietary drivers. Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Chromium Version: 100.0.4896.75 2022-04-07 When running "snap run chromium" in the terminal, the following output happens. Attached screenshot of result. nyaa@nyaa-desktop:~$ snap run chromium Gtk-Message: 13:42:20.777: Failed to load module "canberra-gtk-module" Gtk-Message: 13:42:20.778: Failed to load module "canberra-gtk-module" MESA-LOADER: failed to retrieve device information MESA-LOADER: failed to open nvidia-drm: /snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri/nvidia-drm_dri.so: cannot open shared object file: Permission denied (search paths /snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri) failed to load driver: nvidia-drm MESA-LOADER: failed to open kms_swrast: /snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri/kms_swrast_dri.so: cannot open shared object file: Permission denied (search paths /snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri) failed to load driver: kms_swrast MESA-LOADER: failed to open swrast: /snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri/swrast_dri.so: cannot open shared object file: Permission denied (search paths /snap/chromium/1957/gnome-platform/usr/lib/x86_64-linux-gnu/dri) failed to load swrast driver [9358:9478:0411/134223.111306:ERROR:udev_watcher.cc(98)] Failed to begin udev enumeration. Edit: I have recently tested this more, and I've isolated it to Wayland and the snap version of Chromium. On X, the chromium snap runs correctly. When I run Chromium as a binary from the Chromium website, the issue doesn't occur on Wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1968610/+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 1970389] Re: [nvidia] Janky text entry and frames appear out of order in Xwayland apps
** No longer affects: nvidia-graphics-drivers-510 (Ubuntu) ** No longer affects: nvidia-graphics-drivers-525 (Ubuntu) ** No longer affects: nvidia-graphics-drivers-535 (Ubuntu) -- 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/1970389 Title: [nvidia] Janky text entry and frames appear out of order in Xwayland apps Status in X.Org X server: New Status in xwayland package in Ubuntu: Triaged Bug description: When writing into text fields in some applications (Firefox, VS Code) on Jammy in a GNOME / Wayland session, I can see an effect best described as the glyphs appearing / disappearing sometimes repeatedly. I have attached a recording from my phone (since attempting to record a screencast fails). This doesn't happen always, and it appear somehow sensitive to some environmental condition (load?) since for example when I'm on a video call, the effect seems to not be happening so often. I have also experienced a few instances of a currently not-focused window disappearing (seeing through to a window that is below that window), but cannot reproduce that reliably. I have the NVIDIA driver 510 in use, RTX3090-only 16-core Zen1 Threadripper system with no integrated GPU. No similar effects visible when in a GNOME / Xorg session. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 12:17:02 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-11-08 (168 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-22 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1970389/+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 1990341] Re: [SRU] Support to install nvidia driver by allowing list
Install jammy iso ubuntu-22.04.3-desktop-amd64.iso into Dell Precision 7680. Then install ubuntu-drivers-common 1:0.9.6.2~0.22.04.6 from proposed channel. ubuntu@ubuntu-Precision-7680:~$ ubuntu-drivers list ubuntu@ubuntu-Precision-7680:~$ sudo cp /tmp/custom_supported_gpus.json /etc ubuntu@ubuntu-Precision-7680:~$ cat /etc/custom_supported_gpus.json { "chips": [ { "devid": "0x28B9", "name": "TEST 28B9", "branch": "535.113", "features": [ "runtimepm" ] } ] } ubuntu@ubuntu-Precision-7680:~$ ubuntu-drivers list nvidia-driver-535, (kernel modules provided by linux-modules-nvidia-535-generic-hwe-22.04) System can use ubuntu-drivers to list package by adding customized JSON file. With command ubuntu-drivers install, Nvidia related packages can be added. After system reboot, Nvidia GPU work as expected. ** Tags removed: verification-failed-jammy verification-needed ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1990341 Title: [SRU] Support to install nvidia driver by allowing list Status in OEM Priority Project: Triaged Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: Confirmed Status in ubuntu-drivers-common source package in Lunar: Fix Committed Bug description: [ Impact ] * In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for production. In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a specific nvidia version to development/production. NVIDIA and OEN/ODM will announce the next generation combination at the same time usually when the factory ready to ship the product. We made Ubuntu as a leading distribution supports many cutting edge devices, it's time to have an official way to make the nvidia installation consistent in unannounced (yet) nvidia devices to support OEM/ODM factory shipment for our growing counterparts. [ Test Plan ] * Steps to make sure it works: 1. pick a cutting edge nvidia graphic. 2. remove nv-525 from the pool by removing restricted in jammy-updates and jammy-security 3. check the nv support status: ``` $ ubuntu-drivers list oem-fix-gfx-nvidia-ondemandmode libfprint-2-tod1-broadcom oem-somerville-cinccino-meta ``` 4. modify custom file ``` $ cat /etc/custom_supported_gpus.json { "chips": [ { "devid": "0x24BA", "name": "TEST 24BA", "branch": "580.1234", "features": [ "runtimepm" ] }, { "devid": "0x25BC", "name": "TEST 25BC", "branch": "510", "features": [ "runtimepm" ] } ] } ``` 5. make sure the hook works ``` $ ubuntu-drivers list nvidia-driver-510, (kernel modules provided by nvidia-dkms-510) oem-fix-gfx-nvidia-ondemandmode libfprint-2-tod1-broadcom oem-somerville-cinccino-meta [ Where problems could occur ] * This feature only impact target system has a custom file "/etc/custom_supported_gpus.json". And it won't generate automatically which should not impact normal users [ Other Info ] * the patches are picked from - https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3 - https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115 - https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b. * Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990341/+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 1990341] Re: [SRU] Support to install nvidia driver by allowing list
Install lunar iso into Dell Precision 7680. Then install ubuntu-drivers- common 1:0.9.7.1.2 from proposed channel. ubuntu@ubuntu-Precision-7680:~$ ubuntu-drivers list ubuntu@ubuntu-Precision-7680:~$ sudo cp /tmp/custom_supported_gpus.json /etc ubuntu@ubuntu-Precision-7680:~$ cat /etc/custom_supported_gpus.json { "chips": [ { "devid": "0x28B9", "name": "TEST 28B9", "branch": "535.113", "features": [ "runtimepm" ] } ] } ubuntu@ubuntu-Precision-7680:~$ ubuntu-drivers list nvidia-driver-535, (kernel modules provided by linux-modules-nvidia-535-generic-hwe-22.04) System can use ubuntu-drivers to list package by adding customized JSON file. With command ubuntu-drivers install, Nvidia related driver can be added. And GPU works. ** Tags removed: verification-needed-lunar ** Tags added: verification-done-lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1990341 Title: [SRU] Support to install nvidia driver by allowing list Status in OEM Priority Project: Triaged Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: Confirmed Status in ubuntu-drivers-common source package in Lunar: Fix Committed Bug description: [ Impact ] * In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for production. In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a specific nvidia version to development/production. NVIDIA and OEN/ODM will announce the next generation combination at the same time usually when the factory ready to ship the product. We made Ubuntu as a leading distribution supports many cutting edge devices, it's time to have an official way to make the nvidia installation consistent in unannounced (yet) nvidia devices to support OEM/ODM factory shipment for our growing counterparts. [ Test Plan ] * Steps to make sure it works: 1. pick a cutting edge nvidia graphic. 2. remove nv-525 from the pool by removing restricted in jammy-updates and jammy-security 3. check the nv support status: ``` $ ubuntu-drivers list oem-fix-gfx-nvidia-ondemandmode libfprint-2-tod1-broadcom oem-somerville-cinccino-meta ``` 4. modify custom file ``` $ cat /etc/custom_supported_gpus.json { "chips": [ { "devid": "0x24BA", "name": "TEST 24BA", "branch": "580.1234", "features": [ "runtimepm" ] }, { "devid": "0x25BC", "name": "TEST 25BC", "branch": "510", "features": [ "runtimepm" ] } ] } ``` 5. make sure the hook works ``` $ ubuntu-drivers list nvidia-driver-510, (kernel modules provided by nvidia-dkms-510) oem-fix-gfx-nvidia-ondemandmode libfprint-2-tod1-broadcom oem-somerville-cinccino-meta [ Where problems could occur ] * This feature only impact target system has a custom file "/etc/custom_supported_gpus.json". And it won't generate automatically which should not impact normal users [ Other Info ] * the patches are picked from - https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3 - https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115 - https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b. * Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990341/+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 2038436] Re: System doesnt recognize second monitor
Thanks for the bug report. Please run the following commands: sudo apt install drm-info drm_info > drminfo.txt grep . /sys/class/drm/*/status > connections.txt and then attach the two resulting text files here. ** Tags added: multimonitor ** 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/2038436 Title: System doesnt recognize second monitor Status in Ubuntu: Incomplete Bug description: I am using an old monitor which using a DVI connectors but I used a DVI to HDMI adapter which works fine on Windows operating system... My monitor is HP W2072a... I hope with the information provided helps... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-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: Wed Oct 4 21:17:37 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Device [1b50:1018] InstallationDate: Installed on 2023-09-30 (3 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: ILLEGEAR SDN BHD ATOMIC 16 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=e60cc65c-b597-415b-b294-3cb6a76ecbd0 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2022 dmi.bios.release: 0.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Q3AIL.02 dmi.board.asset.tag: Default string be filled by O.E.M dmi.board.name: ATOMIC dmi.board.vendor: ILLEGEAR SDN BHD dmi.board.version: Default string be filled by O.E.M dmi.chassis.asset.tag: Default string be filled by O.E.M dmi.chassis.type: 9 dmi.chassis.vendor: Default string be filled by O.E.M dmi.chassis.version: Default string be filled by O.E.M dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrQ3AIL.02:bd07/26/2022:br0.2:svnILLEGEARSDNBHD:pnATOMIC16:pvrDefaultstringbefilledbyO.E.M:rvnILLEGEARSDNBHD:rnATOMIC:rvrDefaultstringbefilledbyO.E.M:cvnDefaultstringbefilledbyO.E.M:ct9:cvrDefaultstringbefilledbyO.E.M:skuATOMIC16-ADL1: dmi.product.family: ATOMIC dmi.product.name: ATOMIC 16 dmi.product.sku: ATOMIC16-ADL1 dmi.product.version: Default string be filled by O.E.M dmi.sys.vendor: ILLEGEAR SDN BHD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2038436/+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 2034664] Re: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
I know... $ grep -r Meta.Rectangle /usr/share/gnome-shell/extensions/ /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/appIcons.js: const rect = new Meta.Rectangle(); -- 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/2034664 Title: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Status in gnome-shell-extension-tiling-assistant package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Committed Bug description: The gnome-shell 45.rc log fills with: Meta.Rectangle is deprecated, use Mtk.Rectangle instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+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 1872268] Re: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders (when ubuntu-dock is loaded)
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Focal) Assignee: Daniel van Vugt (vanvugt) => (unassigned) -- 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/1872268 Title: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders (when ubuntu-dock is loaded) Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Focal: Confirmed Status in gnome-shell-extension-ubuntu-dock source package in Groovy: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Hirsute: Invalid Bug description: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Bug: Gnome shell while opening app drawer, clicking on an app folder and clicking on the blank area freezes gnome shell and it makes the session completely unusable and non recoverable. How to reproduce: 1- Click 9 dots on bottom corner of dash (the app launcher button), wait for the app grid to show up. 2- Click on an app folder to open it. 3- Click on the blank area outside of the opened folder dialog. 4- Gnome shell gets freezes and never come back from this state, on both wayland session and x11 session. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 12:00:13 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) RelatedPackageVersions: mutter-common 3.36.1-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/1872268/+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 2037307] Re: Dragging the top activities/time bar freezes GNOME completely (Xorg session)
This issue also occurs semi-randomly when making normal touchscreen motions. For instance, sometimes I'll be scrolling through a webpage, the suddenly Firefox will un-maximize itself (turning into a normal window), and the cursor will get locked into the drag state. As per this issue, the system is then rendered inoperative until I kill Firefox (the active window). This however, is not consistently reproducible, where as dragging from the top bar will cause the issue 100% of the time. It is by no means uncommon though, it is actually quite annoying to have my entire system freeze up semi-regularly and require me to manually restart Firefox (in fact, it happened while writing this comment). I have also done some more testing. - Minimizing the active window (using wmctrl) from a virtual console does not solve the issue. - Starting a new window from a virtual console does not solve the issue. - Consistently, the only way to resolve this issue is the kill the active program. -- 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/2037307 Title: Dragging the top activities/time bar freezes GNOME completely (Xorg session) Status in gnome-shell package in Ubuntu: New Bug description: If you use a touchscreen and drag a finger down on the very top bar (with the time and the former activities button), GNOME will completely freeze. The mouse cursor will be locked in the "drag" state. All keyboard input (including Alt-F2) will be ignored. The only way to escape this state is to switch into a virtual console and kill the current program. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 25 12:33:44 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-02 (55 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-23 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037307/+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 2038313] Re: upscayl software do not work
Please report the bug to Upscayl. Although it is possible the cause is the driver issue here so I'll make that more clear in the bug title... ** Summary changed: - upscayl software do not work + MESA-INTEL: warning: Haswell Vulkan support is incomplete ** Changed in: mesa (Ubuntu) Status: Incomplete => New -- 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/2038313 Title: MESA-INTEL: warning: Haswell Vulkan support is incomplete Status in mesa package in Ubuntu: New Bug description: upscayl software do not work BACKEND REPORTED: Selected File Path: /home/anders/Downloads/1695568515335.png Selected Image Path: /home/anders/Downloads/1695568515335.png Selected Image Directory: /home/anders/Downloads imagePath: /home/anders/Downloads/1695568515335.png Extension: png Resetting Upscaled Image Path UPSCAYL BACKEND REPORTED: Updating Overwrite: false BACKEND REPORTED: ✅ Upscayl Variables: [object Object] BACKEND REPORTED: Upscayl Command: -i,/home/anders/Downloads/1695568515335.png,-o,/home/anders/Downloads/1695568515335_upscayl_4x_ultrasharp.png,-s,4,-m,/tmp/.mount_upscaygPuzIl/resources/models,-n,ultrasharp,,,-f,png BACKEND REPORTED: Updating Child Processes: [object Object] BACKEND REPORTED: Updating Stopped: false BACKEND REPORTED: image upscayl: MESA-INTEL: warning: Haswell Vulkan support is incomplete UPSCAYL_PROGRESS: MESA-INTEL: warning: Haswell Vulkan support is incomplete BACKEND REPORTED: image upscayl: [0 Intel(R) HD Graphics 4600 (HSW GT2)] queueC=0[1] queueG=0[1] queueT=0[1] [0 Intel(R) HD Graphics 4600 (HSW GT2)] bugsbn1=0 bugbilz=0 bugcopc=0 bugihfa=0 [0 Intel(R) HD Graphics 4600 (HSW GT2)] fp16-p/s/a=1/0/0 int8-p/s/a=1/0/0 [0 Intel(R) HD Graphics 4600 (HSW GT2)] subgroup=32 basic=1 vote=1 ballot=1 shuffle=1 [1 llvmpipe (LLVM 15.0.7, 256 bits)] queueC=0[1] queueG=0[1] queueT=0[1] [1 llvmpipe (LLVM 15.0.7, 256 bits)] bugsbn1=0 bugbilz=0 bugcopc=0 bugihfa=0 [1 llvmpipe (LLVM 15.0.7, 256 bits)] fp16-p/s/a=1/1/1 int8-p/s/a=1/1/1 [1 llvmpipe (LLVM 15.0.7, 256 bits)] subgroup=8 basic=1 vote=1 ballot=1 shuffle=1 UPSCAYL_PROGRESS: [0 Intel(R) HD Graphics 4600 (HSW GT2)] queueC=0[1] queueG=0[1] queueT=0[1] [0 Intel(R) HD Graphics 4600 (HSW GT2)] bugsbn1=0 bugbilz=0 bugcopc=0 bugihfa=0 [0 Intel(R) HD Graphics 4600 (HSW GT2)] fp16-p/s/a=1/0/0 int8-p/s/a=1/0/0 [0 Intel(R) HD Graphics 4600 (HSW GT2)] subgroup=32 basic=1 vote=1 ballot=1 shuffle=1 [1 llvmpipe (LLVM 15.0.7, 256 bits)] queueC=0[1] queueG=0[1] queueT=0[1] [1 llvmpipe (LLVM 15.0.7, 256 bits)] bugsbn1=0 bugbilz=0 bugcopc=0 bugihfa=0 [1 llvmpipe (LLVM 15.0.7, 256 bits)] fp16-p/s/a=1/1/1 int8-p/s/a=1/1/1 [1 llvmpipe (LLVM 15.0.7, 256 bits)] subgroup=8 basic=1 vote=1 ballot=1 shuffle=1 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 3 14:45:19 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. 4th Gen Core Processor Integrated Graphics Controller [10cf:17af] InstallationDate: Installed on 2023-09-06 (26 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 1c4f:0034 SiGma Micro XM102K Optical Wheel Mouse Bus 001 Device 002: ID 8087:07dc Intel Corp. Bluetooth wireless interface 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, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M |__ Port 8: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M |__ Port 8: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 9: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: FUJITSU LIFEBOOK E554 ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=cdedb299-9f30-4ac9-aec9-82dafceeaf91 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/27/2017
[Desktop-packages] [Bug 2038435] Re: gnome-shell-extension-ubuntu-dock freezes ubuntu 20.04 when i return from the folder on the dock
*** This bug is a duplicate of bug 1872268 *** https://bugs.launchpad.net/bugs/1872268 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 1872268, 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 1872268 Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders (when ubuntu-dock is loaded) -- 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/2038435 Title: gnome-shell-extension-ubuntu-dock freezes ubuntu 20.04 when i return from the folder on the dock Status in gnome-shell package in Ubuntu: New Bug description: It's unfortunate problem that i am experiencing with the Ubuntu Dock causing my system to freeze that requires a reboot to the system and the icons seem to be small in my screen internal "1366x768" and external "1680x1050" . these problems cause me when i open the a folder in the dock launcher of ubuntu in folder named by developing apps that contains my working programs and with a small icons that makes me have a dificulties in eyes with size 16x16 in both displays external and internal solve this problems ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-84.93~20.04.1-generic 5.15.116 Uname: Linux 5.15.0-84-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 4 15:55:35 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-10-03 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 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/2038435/+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 2037503] Re: [jammy]backport #1453 from upstream
Could you give a more specific example? Do you mean that gamer are likely to want another profile than 'performance' which isn't available/known by the GNOME settings? -- 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/2037503 Title: [jammy]backport #1453 from upstream Status in gnome-control-center package in Ubuntu: Incomplete Status in gnome-control-center package in Debian: New Bug description: In some cases, it was possible for a profile to be set (directly, or through a hold) even though it wasn't supported. Don't assert in those cases. The bug in question makes the gnome-control-center crash if an unsupported power profile is set using, say, powerprofilesctl. Should be trivial to cherry-pick without breaking other components. https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1453 I had to wait for this long because I expected a 42.x backport in the backports repository of .1 release, but no one bothered to do such a backport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037503/+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 2037672] Re: amdgpu: [gfxhub] page fault when switching a video to or from fullscreen
Also - can you still repro with mesa 23.2.1-1ubuntu2? This just landed right after you reported this issue. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: mesa (Ubuntu) Status: Confirmed => Incomplete -- 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/2037672 Title: amdgpu: [gfxhub] page fault when switching a video to or from fullscreen Status in linux package in Ubuntu: Invalid Status in mesa package in Ubuntu: Incomplete Bug description: Hi, Switching a video to or from fullscreen freezes the screen for around 10 seconds. This happens with Totem as well as VLC so its not related to a specific app. Additional observations: - The issue seems to be connected to the video's bitrate. With low bitrate videos I cannot trigger the freeze. However, videos with high bandwidth trigger the freeze reliably. Specs: Ubuntu 23.10 up to date as of 28.09.2023 AMD Ryzen 7 PRO 6850U Kernel 6.5.0-5-generic Grub configured with: amdgpu.vm_update_mode=3 Syslog shows: 2023-09-28T20:02:29.803955+02:00 kernel: [27003.800898] amdgpu :04:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:24 vmid:2 pasid:32771, for process Xwayland pid 2113 thread Xwayland:cs0 pid 2311) 2023-09-28T20:02:39.975854+02:00 kernel: [27013.972772] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, but soft recovered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037672/+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 2017756] Re: Pipewire-pulse consuming huge amounts of memory
** Changed in: pipewire Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/2017756 Title: Pipewire-pulse consuming huge amounts of memory Status in PipeWire: Fix Released Status in pipewire package in Ubuntu: Confirmed Bug description: I noticed my RAM usage was high. pipewire-pulse is the highest user of RAM on my system. The system has been up for four days. I have used all manner of audio applications in that time, including Slack huddle, Zoom, mpv, VLC and Microsoft Edge (YouTube, Netflix) and Kdenlive. alan@ziggy:~$ pactl stat Currently in use: 7865827 blocks containing 2.1 GiB bytes total. Allocated during whole lifetime: 42983702 blocks containing 3.6 GiB bytes total. Sample cache size: 275.2 KiB alan@ziggy:~$ sudo python3 bin/ps_mem.py | tail 207.7 MiB + 419.6 MiB = 627.2 MiB gnome-shell 227.3 MiB + 455.3 MiB = 682.7 MiB syncthing (2) 385.4 MiB + 855.8 MiB = 1.2 GiB slack (8) 409.5 MiB + 928.5 MiB = 1.3 GiB Discord (8) 4.2 GiB + 8.9 GiB = 13.1 GiB msedge [updated] (45) 14.1 GiB + 28.2 GiB = 42.3 GiB pipewire-pulse - 62.7 GiB = ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: pipewire-pulse 0.3.65-3 Uname: Linux 6.2.2-060202-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 26 10:24:47 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20220803-89+sutton-focal-amd64+X02 InstallationDate: Installed on 2022-08-05 (263 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20220803-13:42 SourcePackage: pipewire UpgradeStatus: Upgraded to lunar on 2023-01-02 (113 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/pipewire/+bug/2017756/+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 2023322] Re: Unable to setup Google Online Accounts with Nvidia drivers
** Changed in: webkit2gtk (Ubuntu) Status: Incomplete => In Progress -- 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/2023322 Title: Unable to setup Google Online Accounts with Nvidia drivers Status in Webkit: Confirmed Status in gnome-control-center package in Ubuntu: Triaged Status in gnome-online-accounts package in Ubuntu: Triaged Status in webkit2gtk package in Ubuntu: In Progress Status in yelp package in Ubuntu: Triaged Status in webkit2gtk package in Debian: Confirmed Bug description: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for user root Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 (core 2, socket 0) Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 0x55bd22ad9ab2. Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3a006dc. Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - Cleanup of Temporary Directories. Jun 08 11:17:42 CCW-HAL systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully. Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a029e2 for 0x3a029f0 window override-redirect is an override-redirect window and this is not correct
[Desktop-packages] [Bug 2031340] Re: slic3r-prusa autopkgtest flaky
Just adding that I tried rebuilding the package and tests are still failing 2.6.1+dfsg-3 https://launchpad.net/~mitchdz/+archive/ubuntu/slic3r-prusa- mantic/+builds?build_text=_state=all -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2031340 Title: slic3r-prusa autopkgtest flaky Status in fontconfig package in Ubuntu: Fix Released Status in gmp package in Ubuntu: Fix Released Status in nlopt package in Ubuntu: Fix Released Status in slic3r-prusa package in Ubuntu: New Bug description: autopkgtest was added to slic3r-prusa as late as last April. They have never let version 2.6.0 of slic3r-prusa migrate to Debian testing, and seemingly need more work. slic3r-prusa 2.6.0+dfsg-2 was uploaded to unstable on July 27 but hasn't migrated to testing yet due to failing autopkgtest. In Ubuntu the flaky tests currently prevent fontconfig and nlopt (in addition to slic3r-prusa itself) from migrating to mantic-release. Probably some kind of hint is motivated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2031340/+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 2034664] Re: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
I still have the problem corrado@corrado-n17-mm-1004:~$ apt policy gnome-shell-extension-tiling-assistant gnome-shell-extension-tiling-assistant: Installed: (none) Candidate: (none) Version table: corrado@corrado-n17-mm-1004:~$ apt policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 87ubuntu1 Candidate: 87ubuntu1 Version table: *** 87ubuntu1 500 500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu mantic/main i386 Packages 100 /var/lib/dpkg/status corrado@corrado-n17-mm-1004:~$ -- 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/2034664 Title: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Status in gnome-shell-extension-tiling-assistant package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Committed Bug description: The gnome-shell 45.rc log fills with: Meta.Rectangle is deprecated, use Mtk.Rectangle instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+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 2038435] Re: gnome-shell-extension-ubuntu-dock freezes ubuntu 20.04 when i return from the folder on the dock
** Description changed: - It's unfortunate that i am experiencing this issue with the Ubuntu Dock - causing my system to freeze and require a reboot. this problem cause me - when i open the a folder in the dock launcher of ubuntu in folder named - byy developing apps that contains my working programs it causes the - problem - + It's unfortunate problem that i am experiencing with the Ubuntu Dock causing my system to freeze that requires a reboot to the system and the icons seem to be small in my screen internal "1366x768" and external "1680x1050" . these problems cause me when i open the a folder in the dock launcher of ubuntu in folder named by developing apps that contains my working programs and with a small icons that makes me have a dificulties in eyes with size 16x16 + solve this problems ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-84.93~20.04.1-generic 5.15.116 Uname: Linux 5.15.0-84-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 4 15:55:35 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-10-03 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: - It's unfortunate problem that i am experiencing with the Ubuntu Dock causing my system to freeze that requires a reboot to the system and the icons seem to be small in my screen internal "1366x768" and external "1680x1050" . these problems cause me when i open the a folder in the dock launcher of ubuntu in folder named by developing apps that contains my working programs and with a small icons that makes me have a dificulties in eyes with size 16x16 - solve this problems + It's unfortunate problem that i am experiencing with the Ubuntu Dock causing my system to freeze that requires a reboot to the system and the icons seem to be small in my screen internal "1366x768" and external "1680x1050" . these problems cause me when i open the a folder in the dock launcher of ubuntu in folder named by developing apps that contains my working programs and with a small icons that makes me have a dificulties in eyes with size 16x16 in both displays external and internal + solve this problems ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-84.93~20.04.1-generic 5.15.116 Uname: Linux 5.15.0-84-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 4 15:55:35 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-10-03 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 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/2038435 Title: gnome-shell-extension-ubuntu-dock freezes ubuntu 20.04 when i return from the folder on the dock Status in gnome-shell package in Ubuntu: New Bug description: It's unfortunate problem that i am experiencing with the Ubuntu Dock causing my system to freeze that requires a reboot to the system and the icons seem to be small in my screen internal "1366x768" and external "1680x1050" . these problems cause me when i open the a folder in the dock launcher of ubuntu in folder named by developing apps that contains my working programs and with a small icons that makes me have a dificulties in eyes with size 16x16 in both displays external and internal solve this problems ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-84.93~20.04.1-generic 5.15.116 Uname: Linux 5.15.0-84-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 4 15:55:35 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-10-03 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron:
[Desktop-packages] [Bug 2038452] [NEW] /usr/bin/rungs missing (essential to tex4ht)
Public bug reported: I can no longer run htlatex, receiving the following error messages: --- Warning --- System return: 32512 System call: rungs -q -dNOPAUSE -dBATCH -dusecropbox -sDEVICE=pngalpha -r300 -sOutputFile="fig//expand-.png" "fig//expand.pdf" sh: 1: rungs: not found It appears as though /usr/bin/rungs is not include in the lunar package, despite being there in previous iterations: https://packages.ubuntu.com/search?suite=kinetic=any=exactfilename=contents=rungs ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: texlive-base 2022.20230122-2 ProcVersionSignature: Ubuntu 6.2.0-26.26-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Oct 4 17:27:47 2023 InstallationDate: Installed on 2018-01-05 (2098 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: texlive-base UpgradeStatus: Upgraded to lunar on 2023-04-27 (160 days ago) ** Affects: texlive-base (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texlive-base in Ubuntu. https://bugs.launchpad.net/bugs/2038452 Title: /usr/bin/rungs missing (essential to tex4ht) Status in texlive-base package in Ubuntu: New Bug description: I can no longer run htlatex, receiving the following error messages: --- Warning --- System return: 32512 System call: rungs -q -dNOPAUSE -dBATCH -dusecropbox -sDEVICE=pngalpha -r300 -sOutputFile="fig//expand-.png" "fig//expand.pdf" sh: 1: rungs: not found It appears as though /usr/bin/rungs is not include in the lunar package, despite being there in previous iterations: https://packages.ubuntu.com/search?suite=kinetic=any=exactfilename=contents=rungs ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: texlive-base 2022.20230122-2 ProcVersionSignature: Ubuntu 6.2.0-26.26-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Oct 4 17:27:47 2023 InstallationDate: Installed on 2018-01-05 (2098 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: texlive-base UpgradeStatus: Upgraded to lunar on 2023-04-27 (160 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/2038452/+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 2036440] Re: Choosing "Try Ubuntu" on daily-legacy image produced a crash
I confirm that the crash did not occur with the latest daily-legacy image, thanks! ubuntu@ubuntu:~$ cat /media/cdrom/.disk/info Ubuntu Legacy 23.10 "Mantic Minotaur" - Daily amd64 (20231004)ubuntu@ubuntu:~$ ubuntu@ubuntu:~$ apt-cache policy gnome-shell gnome-shell: Installed: 45.0-1ubuntu2 Candidate: 45.0-1ubuntu2 Version table: *** 45.0-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status ubuntu@ubuntu:~$ ls /var/crash ubuntu@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/2036440 Title: Choosing "Try Ubuntu" on daily-legacy image produced a crash Status in gnome-shell package in Ubuntu: Fix Released Bug description: I was booting up a daily-legacy image from 20230918 and received a crash report after choosing "Try Ubuntu". ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~rc-0ubuntu3 Uname: Linux 6.5.0-5-generic x86_64 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 18 15:20:58 2023 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1694375959 ProcCmdline: gnome-shell --sm-disable --mode=ubiquity ProcCwd: /home/ubuntu ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= Signal: 6 SourcePackage: gnome-shell UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2036440/+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 2037503] Re: [jammy]backport #1453 from upstream
> The fact that we didn't see reports about it until now is also an indication that it's not a common problem Hard to encounter by a casual office user, but power users, overclockers and high performance gamers are very likely to encounter this bug ("performance" profile is conditionally hidden by the gnome-control- center but the test hiding it does not always work correctly, sometimes it is hidden even when it is actually available by the hardware, such as I encountered in my Zen 3 processor). -- 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/2037503 Title: [jammy]backport #1453 from upstream Status in gnome-control-center package in Ubuntu: Incomplete Status in gnome-control-center package in Debian: New Bug description: In some cases, it was possible for a profile to be set (directly, or through a hold) even though it wasn't supported. Don't assert in those cases. The bug in question makes the gnome-control-center crash if an unsupported power profile is set using, say, powerprofilesctl. Should be trivial to cherry-pick without breaking other components. https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1453 I had to wait for this long because I expected a 42.x backport in the backports repository of .1 release, but no one bothered to do such a backport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037503/+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 2037503] Re: [jammy]backport #1453 from upstream
> Could you provide some details on how you set a profile which isn't available? I invoked powerprofilectl and "fixed" the performance profile using that. And then gnome-control-center would throw a fatal assertion failure (UI cannot open, basically total non-function of the app), and stop working. If the profile setting is rolled back using the same powerprofilectl, it can be opened again. The patch from upstream converts this error into a logged non-fatal warning. -- 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/2037503 Title: [jammy]backport #1453 from upstream Status in gnome-control-center package in Ubuntu: Incomplete Status in gnome-control-center package in Debian: New Bug description: In some cases, it was possible for a profile to be set (directly, or through a hold) even though it wasn't supported. Don't assert in those cases. The bug in question makes the gnome-control-center crash if an unsupported power profile is set using, say, powerprofilesctl. Should be trivial to cherry-pick without breaking other components. https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1453 I had to wait for this long because I expected a 42.x backport in the backports repository of .1 release, but no one bothered to do such a backport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037503/+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 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
Updated from related card - https://github.com/thesofproject/linux/issues/4055 ** Bug watch added: github.com/thesofproject/linux/issues #4055 https://github.com/thesofproject/linux/issues/4055 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2011385 Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: only bluetooth can work,im sungsang book2 pro ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 13 15:41:47 2023 InstallationDate: Installed on 2023-03-08 (4 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: wang 1658 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P08RGF.054.220817.ZQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NT950XEW-A51AS dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLFREEDOS-C00-R000-S+1.0. dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF: dmi.product.family: Galaxy Book2 Pro dmi.product.name: 950XED dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF dmi.product.version: P08RGF dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 2038439] [NEW] Update network-manager to 1.44.2
Public bug reported: New upstream bugfix release in the stable 1.44 series https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/compare/1.44.0...1.44.2 ** Affects: network-manager (Ubuntu) Importance: Undecided Assignee: Jeremy Bícha (jbicha) Status: In Progress ** Tags: mantic upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2038439 Title: Update network-manager to 1.44.2 Status in network-manager package in Ubuntu: In Progress Bug description: New upstream bugfix release in the stable 1.44 series https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/compare/1.44.0...1.44.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2038439/+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 2038436] [NEW] System doesnt recognize second monitor
Public bug reported: I am using an old monitor which using a DVI connectors but I used a DVI to HDMI adapter which works fine on Windows operating system... My monitor is HP W2072a... I hope with the information provided helps... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-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: Wed Oct 4 21:17:37 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Device [1b50:1018] InstallationDate: Installed on 2023-09-30 (3 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: ILLEGEAR SDN BHD ATOMIC 16 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=e60cc65c-b597-415b-b294-3cb6a76ecbd0 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2022 dmi.bios.release: 0.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Q3AIL.02 dmi.board.asset.tag: Default string be filled by O.E.M dmi.board.name: ATOMIC dmi.board.vendor: ILLEGEAR SDN BHD dmi.board.version: Default string be filled by O.E.M dmi.chassis.asset.tag: Default string be filled by O.E.M dmi.chassis.type: 9 dmi.chassis.vendor: Default string be filled by O.E.M dmi.chassis.version: Default string be filled by O.E.M dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrQ3AIL.02:bd07/26/2022:br0.2:svnILLEGEARSDNBHD:pnATOMIC16:pvrDefaultstringbefilledbyO.E.M:rvnILLEGEARSDNBHD:rnATOMIC:rvrDefaultstringbefilledbyO.E.M:cvnDefaultstringbefilledbyO.E.M:ct9:cvrDefaultstringbefilledbyO.E.M:skuATOMIC16-ADL1: dmi.product.family: ATOMIC dmi.product.name: ATOMIC 16 dmi.product.sku: ATOMIC16-ADL1 dmi.product.version: Default string be filled by O.E.M dmi.sys.vendor: ILLEGEAR SDN BHD version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- 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/2038436 Title: System doesnt recognize second monitor Status in xorg package in Ubuntu: New Bug description: I am using an old monitor which using a DVI connectors but I used a DVI to HDMI adapter which works fine on Windows operating system... My monitor is HP W2072a... I hope with the information provided helps... ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-34.34~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-34-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: Wed Oct 4 21:17:37 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Device [1b50:1018] InstallationDate: Installed on 2023-09-30 (3 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: ILLEGEAR SDN BHD ATOMIC 16 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-34-generic root=UUID=e60cc65c-b597-415b-b294-3cb6a76ecbd0 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/26/2022 dmi.bios.release: 0.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Q3AIL.02 dmi.board.asset.tag: Default string be filled by O.E.M dmi.board.name: ATOMIC dmi.board.vendor: ILLEGEAR SDN BHD dmi.board.version: Default string be filled by O.E.M dmi.chassis.asset.tag: Default string be filled by O.E.M dmi.chassis.type: 9 dmi.chassis.vendor: Default string be
[Desktop-packages] [Bug 2038435] [NEW] gnome-shell-extension-ubuntu-dock freezes ubuntu 20.04 when i return from the folder on the dock
Public bug reported: It's unfortunate that i am experiencing this issue with the Ubuntu Dock causing my system to freeze and require a reboot. this problem cause me when i open the a folder in the dock launcher of ubuntu in folder named byy developing apps that contains my working programs it causes the problem ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-84.93~20.04.1-generic 5.15.116 Uname: Linux 5.15.0-84-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 4 15:55:35 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-10-03 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/2038435 Title: gnome-shell-extension-ubuntu-dock freezes ubuntu 20.04 when i return from the folder on the dock Status in gnome-shell package in Ubuntu: New Bug description: It's unfortunate that i am experiencing this issue with the Ubuntu Dock causing my system to freeze and require a reboot. this problem cause me when i open the a folder in the dock launcher of ubuntu in folder named byy developing apps that contains my working programs it causes the problem ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.9-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.15.0-84.93~20.04.1-generic 5.15.116 Uname: Linux 5.15.0-84-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 4 15:55:35 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-10-03 (0 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.9-0ubuntu0.20.04.2 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/2038435/+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 2037497]
*** Bug 2241332 has been marked as a duplicate of this bug. *** -- 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/2037497 Title: gnome-shell crashed with SIGSEGV at NULL from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage() Status in Mesa: New Status in Mutter: Fix Released Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in mesa package in Fedora: Confirmed Bug description: crash after update wayland session is not accessible anymore ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 05:52:26 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-26 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Beta amd64 (20230924) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.0-2ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-cogl-13.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-13.so.0 Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2037497/+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 2037569] Re: udev issues with mantic beta
** Tags added: architecture-s39064 bugnameltc-203787 severity-high targetmilestone-inin--- -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libblockdev in Ubuntu. https://bugs.launchpad.net/bugs/2037569 Title: udev issues with mantic beta Status in Ubuntu on IBM z Systems: Fix Released Status in libblockdev package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Status in udisks2 package in Ubuntu: Fix Released Bug description: While installing mantic beta (on s390x, LPAR and z/VM - but this might not be architecture specific) I faced issues with udev. In my installation I've updated the installer to "edge/lp-2009141" (subiquity 22.02.2+git1762.1b1ee6f4 5164). During my installations I first noticed bad response times in case of dealing with devices (like enabling new devices with chzdev). chzdev is used during the installation, hence the installation procedure is also affected by this. (I mainly notice this issue in case of DASD ECKD disk enablements.) But even after after a successful (but due to this issue less snappier) installation, means after the post-install reboot, in the installed system I can find several udev related processes, like: 69448 root 20 0 31280 11944 2560 S 39.2 0.0 2:51.67 (udev-worker) 509 root 20 0 31276 13812 4600 S 20.6 0.0 2:07.76 systemd-udevd 893 root 20 0 469016 13544 10496 R 17.3 0.0 1:43.53 udisksd 1 root 20 0 168664 12748 8396 S 16.3 0.0 1:40.47 systemd which is not only unusual, but (as one can see) they consume quite some resources. Even the remote ssh into that system is impacted by this high load. So far I only see this in mantic. I tried 20.04.3 as well as lunar, but both do not seem to be affected by this udev problem. I neither face the bad response on device enablement, nor can see any udev related processes still running after post-install-reboot in the installed system. (Sometimes I could also see a growing log file 'syslog'). I cannot say yet what is causing this, but since I see 'systemd-udevd' as prominent process in top, I'll first of all mark this as affecting systemd-udevd (or systemd). I've attached the outcome of some more investigations I did ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+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 2037569] Re: udev issues with mantic beta
Hi Dan, I've took the manytic daily from yesterday (Oct 3rd) and checked if the updated udisks2 package is in - which is the case - and gave it a try. I did multiple different installations - all with DASDs, on LPAR and on z/VM. Installations with a single DASD or with multiple DASDs (even combining them to a bigger disk using LVM), and I didn't faced udev issues anymore. I checked with top during the installation as well as after the post-install reboot was completed -- all good. So many thanks for your fix and upload on this (and Seb's review) ! ** Changed in: ubuntu-z-systems Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libblockdev in Ubuntu. https://bugs.launchpad.net/bugs/2037569 Title: udev issues with mantic beta Status in Ubuntu on IBM z Systems: Fix Released Status in libblockdev package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Status in udisks2 package in Ubuntu: Fix Released Bug description: While installing mantic beta (on s390x, LPAR and z/VM - but this might not be architecture specific) I faced issues with udev. In my installation I've updated the installer to "edge/lp-2009141" (subiquity 22.02.2+git1762.1b1ee6f4 5164). During my installations I first noticed bad response times in case of dealing with devices (like enabling new devices with chzdev). chzdev is used during the installation, hence the installation procedure is also affected by this. (I mainly notice this issue in case of DASD ECKD disk enablements.) But even after after a successful (but due to this issue less snappier) installation, means after the post-install reboot, in the installed system I can find several udev related processes, like: 69448 root 20 0 31280 11944 2560 S 39.2 0.0 2:51.67 (udev-worker) 509 root 20 0 31276 13812 4600 S 20.6 0.0 2:07.76 systemd-udevd 893 root 20 0 469016 13544 10496 R 17.3 0.0 1:43.53 udisksd 1 root 20 0 168664 12748 8396 S 16.3 0.0 1:40.47 systemd which is not only unusual, but (as one can see) they consume quite some resources. Even the remote ssh into that system is impacted by this high load. So far I only see this in mantic. I tried 20.04.3 as well as lunar, but both do not seem to be affected by this udev problem. I neither face the bad response on device enablement, nor can see any udev related processes still running after post-install-reboot in the installed system. (Sometimes I could also see a growing log file 'syslog'). I cannot say yet what is causing this, but since I see 'systemd-udevd' as prominent process in top, I'll first of all mark this as affecting systemd-udevd (or systemd). I've attached the outcome of some more investigations I did ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2037569/+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 2037641] Re: amdgpu: [gfxhub0] no-retry page fault
I'd say that's very likely. That mesa upgrade just landed in the archive a few days ago and the trace you reported looks more like how a mesa bug manifests. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: mesa (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2037641 Title: amdgpu: [gfxhub0] no-retry page fault Status in linux package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Bug description: Whenever I use Intellij IDEA, after a couple of minutes the screen locks up and pretty much renders the machine unusable. I can still ssh to it, but the UI is pretty much gone and doesn't respond to Ctrl+Alt+F* keys. The setup: the machine is connected to an external monitor via USB-C. Running kernel 6.5 on Ubuntu 23.10. There's the following in kern.log: ``` 2023-09-28T13:58:23.077679+03:00 mavi-ThinkPad-T14s kernel: [ 422.206433] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077694+03:00 mavi-ThinkPad-T14s kernel: [ 422.206450] amdgpu :06:00.0: amdgpu: in page starting at address 0xb15852923000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077695+03:00 mavi-ThinkPad-T14s kernel: [ 422.206460] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077696+03:00 mavi-ThinkPad-T14s kernel: [ 422.206466] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077698+03:00 mavi-ThinkPad-T14s kernel: [ 422.206471] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206476] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206481] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077700+03:00 mavi-ThinkPad-T14s kernel: [ 422.206485] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206490] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206497] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077702+03:00 mavi-ThinkPad-T14s kernel: [ 422.206506] amdgpu :06:00.0: amdgpu: in page starting at address 0xb07248096000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077703+03:00 mavi-ThinkPad-T14s kernel: [ 422.206514] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206519] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206524] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206528] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206533] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077706+03:00 mavi-ThinkPad-T14s kernel: [ 422.206538] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077707+03:00 mavi-ThinkPad-T14s kernel: [ 422.206542] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077708+03:00 mavi-ThinkPad-T14s kernel: [ 422.206549] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077709+03:00 mavi-ThinkPad-T14s kernel: [ 422.206556] amdgpu :06:00.0: amdgpu: in page starting at address 0xaf8c3d808000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206564] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206569] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077711+03:00 mavi-ThinkPad-T14s kernel: [ 422.206574] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206578] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206583] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077713+03:00 mavi-ThinkPad-T14s kernel: [ 422.206588] amdgpu :06:00.0: amdgpu:
[Desktop-packages] [Bug 2037641] Re: amdgpu: [gfxhub0] no-retry page fault
Thanks Mario! I checked, and I have the newest mesa: ``` $ apt search mesa-vdpau Sorting... Done Full Text Search... Done mesa-vdpau-drivers/mantic,now 23.2.1-1ubuntu2 amd64 [installed,automatic] Mesa VDPAU video acceleration drivers ``` Funny thing is that the bug is no longer reproducible - everything is working properly, yay! Could it be that mesa was upgraded a couple of days ago, resolving the issue? Anyways, the issue looks to be fixed now. Thanks again! -- 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/2037641 Title: amdgpu: [gfxhub0] no-retry page fault Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Bug description: Whenever I use Intellij IDEA, after a couple of minutes the screen locks up and pretty much renders the machine unusable. I can still ssh to it, but the UI is pretty much gone and doesn't respond to Ctrl+Alt+F* keys. The setup: the machine is connected to an external monitor via USB-C. Running kernel 6.5 on Ubuntu 23.10. There's the following in kern.log: ``` 2023-09-28T13:58:23.077679+03:00 mavi-ThinkPad-T14s kernel: [ 422.206433] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077694+03:00 mavi-ThinkPad-T14s kernel: [ 422.206450] amdgpu :06:00.0: amdgpu: in page starting at address 0xb15852923000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077695+03:00 mavi-ThinkPad-T14s kernel: [ 422.206460] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077696+03:00 mavi-ThinkPad-T14s kernel: [ 422.206466] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077698+03:00 mavi-ThinkPad-T14s kernel: [ 422.206471] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206476] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206481] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077700+03:00 mavi-ThinkPad-T14s kernel: [ 422.206485] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206490] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206497] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077702+03:00 mavi-ThinkPad-T14s kernel: [ 422.206506] amdgpu :06:00.0: amdgpu: in page starting at address 0xb07248096000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077703+03:00 mavi-ThinkPad-T14s kernel: [ 422.206514] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206519] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206524] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206528] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206533] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077706+03:00 mavi-ThinkPad-T14s kernel: [ 422.206538] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077707+03:00 mavi-ThinkPad-T14s kernel: [ 422.206542] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077708+03:00 mavi-ThinkPad-T14s kernel: [ 422.206549] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077709+03:00 mavi-ThinkPad-T14s kernel: [ 422.206556] amdgpu :06:00.0: amdgpu: in page starting at address 0xaf8c3d808000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206564] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206569] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077711+03:00 mavi-ThinkPad-T14s kernel: [ 422.206574] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206578] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206583]
[Desktop-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
** Changed in: mutter (Ubuntu Mantic) Milestone: None => ubuntu-23.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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: New Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Status in linux source package in Mantic: Confirmed Status in mutter source package in Mantic: In Progress Bug description: [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Original Description] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 2038313] Re: upscayl software do not work
Hi, error message in picture attached. Best regards, Anders bodin On Wed, 4 Oct 2023 at 07:40, Daniel van Vugt <2038...@bugs.launchpad.net> wrote: > I don't know if this counts as "do not work", but it seems clear that > Mesa's Vulkan driver for Haswell is incomplete and it's fallen back to > LLVM (software rendering). That should "work" very slowly still. Was > there actually any error? > > Also this change to your system is not supported by Ubuntu: > > libvulkan1 1.3.261.0~rc1-1lunarg22.04-1 [origin: vulkan.lunarg.com] > > > ** Package changed: xorg (Ubuntu) => mesa (Ubuntu) > > ** Changed in: mesa (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2038313 > > Title: > upscayl software do not work > > Status in mesa package in Ubuntu: > Incomplete > > Bug description: > upscayl software do not work > > BACKEND REPORTED: Selected File Path: > /home/anders/Downloads/1695568515335.png > Selected Image Path: /home/anders/Downloads/1695568515335.png > Selected Image Directory: /home/anders/Downloads > imagePath: /home/anders/Downloads/1695568515335.png > Extension: png > Resetting Upscaled Image Path > UPSCAYL > BACKEND REPORTED: Updating Overwrite: false > BACKEND REPORTED: ✅ Upscayl Variables: [object Object] > BACKEND REPORTED: Upscayl Command: > -i,/home/anders/Downloads/1695568515335.png,-o,/home/anders/Downloads/1695568515335_upscayl_4x_ultrasharp.png,-s,4,-m,/tmp/.mount_upscaygPuzIl/resources/models,-n,ultrasharp,,,-f,png > BACKEND REPORTED: Updating Child Processes: [object Object] > BACKEND REPORTED: Updating Stopped: false > BACKEND REPORTED: image upscayl: MESA-INTEL: warning: Haswell > Vulkan support is incomplete > > UPSCAYL_PROGRESS: MESA-INTEL: warning: Haswell Vulkan support is > incomplete > > BACKEND REPORTED: image upscayl: [0 Intel(R) HD Graphics 4600 (HSW > GT2)] queueC=0[1] queueG=0[1] queueT=0[1] > [0 Intel(R) HD Graphics 4600 (HSW GT2)] bugsbn1=0 bugbilz=0 > bugcopc=0 bugihfa=0 > [0 Intel(R) HD Graphics 4600 (HSW GT2)] fp16-p/s/a=1/0/0 > int8-p/s/a=1/0/0 > [0 Intel(R) HD Graphics 4600 (HSW GT2)] subgroup=32 basic=1 vote=1 > ballot=1 shuffle=1 > [1 llvmpipe (LLVM 15.0.7, 256 bits)] queueC=0[1] queueG=0[1] > queueT=0[1] > [1 llvmpipe (LLVM 15.0.7, 256 bits)] bugsbn1=0 bugbilz=0 bugcopc=0 > bugihfa=0 > [1 llvmpipe (LLVM 15.0.7, 256 bits)] fp16-p/s/a=1/1/1 int8-p/s/a=1/1/1 > [1 llvmpipe (LLVM 15.0.7, 256 bits)] subgroup=8 basic=1 vote=1 > ballot=1 shuffle=1 > > UPSCAYL_PROGRESS: [0 Intel(R) HD Graphics 4600 (HSW GT2)] > queueC=0[1] queueG=0[1] queueT=0[1] > [0 Intel(R) HD Graphics 4600 (HSW GT2)] bugsbn1=0 bugbilz=0 > bugcopc=0 bugihfa=0 > [0 Intel(R) HD Graphics 4600 (HSW GT2)] fp16-p/s/a=1/0/0 > int8-p/s/a=1/0/0 > [0 Intel(R) HD Graphics 4600 (HSW GT2)] subgroup=32 basic=1 vote=1 > ballot=1 shuffle=1 > [1 llvmpipe (LLVM 15.0.7, 256 bits)] queueC=0[1] queueG=0[1] > queueT=0[1] > [1 llvmpipe (LLVM 15.0.7, 256 bits)] bugsbn1=0 bugbilz=0 bugcopc=0 > bugihfa=0 > [1 llvmpipe (LLVM 15.0.7, 256 bits)] fp16-p/s/a=1/1/1 int8-p/s/a=1/1/1 > [1 llvmpipe (LLVM 15.0.7, 256 bits)] subgroup=8 basic=1 vote=1 > ballot=1 shuffle=1 > > ProblemType: Bug > DistroRelease: Ubuntu 23.04 > Package: xorg 1:7.7+23ubuntu2 > ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 > Uname: Linux 6.2.0-33-generic x86_64 > ApportVersion: 2.26.1-0ubuntu2 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: unknown > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Tue Oct 3 14:45:19 2023 > DistUpgraded: Fresh install > DistroCodename: lunar > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes > GraphicsCard: >Intel Corporation 4th Gen Core Processor Integrated Graphics Controller > [8086:0416] (rev 06) (prog-if 00 [VGA controller]) > Subsystem: Fujitsu Limited. 4th Gen Core Processor Integrated > Graphics Controller [10cf:17af] > InstallationDate: Installed on 2023-09-06 (26 days ago) > InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 > (20230418) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 005: ID 1c4f:0034 SiGma Micro XM102K Optical Wheel Mouse >Bus 001 Device 002: ID 8087:07dc Intel Corp. Bluetooth wireless > interface >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, 5000M >/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M >|__ Port 8: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M >|__ Port 8: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M >|__ Port 9: Dev 5, If 0, Class=Human Interface
[Desktop-packages] [Bug 1862764] Re: add-apt-repository should use signed-by
This has been fixed a couple of months ago for PPAs and I think other shortcuts; they now use deb822 .sources files with Signed-By parameter. ** Changed in: software-properties (Ubuntu) Status: Confirmed => Fix Released ** Changed in: python-apt (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1862764 Title: add-apt-repository should use signed-by Status in python-apt package in Ubuntu: Fix Released Status in software-properties package in Ubuntu: Fix Released Status in software-properties package in Debian: New Bug description: add-apt-repository should use signed-by apt sources.list syntax supports limiting which keys are used to sign a given repo. It would be nice for add-apt-repository to import the key somewhere else but trusted.gpg.d and then specify path to it, using the "signed- by" field. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: software-properties-common 0.98.6 ProcVersionSignature: Ubuntu 5.4.0-1002.4-oem 5.4.8 Uname: Linux 5.4.0-1002-oem x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 11 12:01:49 2020 InstallationDate: Installed on 2016-01-26 (1477 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160125) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: software-properties UpgradeStatus: Upgraded to focal on 2019-01-15 (391 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-01-10T16:24:15.968394 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1862764/+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 2031872] Re: Support Elan fp device [04F3:0C99]
This bug was fixed in the package libfprint - 1:1.94.3+tod1-0ubuntu2~22.04.06 --- libfprint (1:1.94.3+tod1-0ubuntu2~22.04.06) jammy; urgency=medium [ Dirk Su ] * d/p/goodixmoc-Add-PID-0x633C.patch (LP: #2034121) [ Andy Chi ] * d/p/synaptics-fix-enroll_identify-problem-after-user-reset-da.patch (LP: #2034481) [ Marco Trevisan (Treviño) ] * debian/patches: Refresh libfprint (1:1.94.3+tod1-0ubuntu2~22.04.05) jammy; urgency=medium [ Yao Wei (魏銘廷) ] * d/p/elanmoc-add-PID-0x0c99.patch, d/p/elanmoc-enroll-time-update.patch: - Add support for PID 0c99 elan fingerprint device (LP: #2031872) -- Marco Trevisan (Treviño) Thu, 07 Sep 2023 17:20:37 +0200 ** Changed in: libfprint (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/2031872 Title: Support Elan fp device [04F3:0C99] Status in OEM Priority Project: New Status in libfprint package in Ubuntu: Fix Released Status in libfprint source package in Jammy: Fix Released Status in libfprint source package in Lunar: New Bug description: This patch is upstreamed: - https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/437 Note that part of the patch requires the changeset from: - https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/374 so that the enroll time can be different between devices. [Impact] * Support Elan [04f3:0c99] fingerprint component. [Test Plan] * Find a machine with this fingerprint device * Find a machine with other fingerprint device (e.g. 04f3:0c82) * Launch `settings` and enable `Fingerprint Login` * Enroll finger and then logout on both DUTs. * Login system with enrolled finger on both DUTs. [Where problems could occur] * The patch also includes part required for [04f3:0c8c] and [04f3:0c8d], but the support for these devices are removed. If needed we can add support for these two devices in this patchset. * The impact will be [04f3:0c99] will be supported. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2031872/+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 2034121] Re: Support goodix fingerprint [27c6:633C]
This bug was fixed in the package libfprint - 1:1.94.3+tod1-0ubuntu2~22.04.06 --- libfprint (1:1.94.3+tod1-0ubuntu2~22.04.06) jammy; urgency=medium [ Dirk Su ] * d/p/goodixmoc-Add-PID-0x633C.patch (LP: #2034121) [ Andy Chi ] * d/p/synaptics-fix-enroll_identify-problem-after-user-reset-da.patch (LP: #2034481) [ Marco Trevisan (Treviño) ] * debian/patches: Refresh libfprint (1:1.94.3+tod1-0ubuntu2~22.04.05) jammy; urgency=medium [ Yao Wei (魏銘廷) ] * d/p/elanmoc-add-PID-0x0c99.patch, d/p/elanmoc-enroll-time-update.patch: - Add support for PID 0c99 elan fingerprint device (LP: #2031872) -- Marco Trevisan (Treviño) Thu, 07 Sep 2023 17:20:37 +0200 ** Changed in: libfprint (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/2034121 Title: Support goodix fingerprint [27c6:633C] Status in OEM Priority Project: New Status in libfprint package in Ubuntu: Fix Released Status in libfprint source package in Jammy: Fix Released Status in libfprint source package in Lunar: Confirmed Bug description: [27c6:633C] include in https://salsa.debian.org/ubuntu-dev- team/libfprint/-/commit/96645eaa7ae99a12e08b65e24a8610a3c57a92b3 [Impact] * Support goodix [27c6:633C] fingerprint component. [Test Plan] * Find a machine with this fingerprint device * Launch `settings` and enable `Fingerprint Login` * Enroll finger and then logout * Login system with enrolled finger [Where problems could occur] * The patch add new ids to id_table. Should not affect previous supported device. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034121/+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 2034481] Re: Cannot verify fingerprint if the storage is empty (Synaptics)
This bug was fixed in the package libfprint - 1:1.94.3+tod1-0ubuntu2~22.04.06 --- libfprint (1:1.94.3+tod1-0ubuntu2~22.04.06) jammy; urgency=medium [ Dirk Su ] * d/p/goodixmoc-Add-PID-0x633C.patch (LP: #2034121) [ Andy Chi ] * d/p/synaptics-fix-enroll_identify-problem-after-user-reset-da.patch (LP: #2034481) [ Marco Trevisan (Treviño) ] * debian/patches: Refresh libfprint (1:1.94.3+tod1-0ubuntu2~22.04.05) jammy; urgency=medium [ Yao Wei (魏銘廷) ] * d/p/elanmoc-add-PID-0x0c99.patch, d/p/elanmoc-enroll-time-update.patch: - Add support for PID 0c99 elan fingerprint device (LP: #2031872) -- Marco Trevisan (Treviño) Thu, 07 Sep 2023 17:20:37 +0200 ** Changed in: libfprint (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/2034481 Title: Cannot verify fingerprint if the storage is empty (Synaptics) Status in OEM Priority Project: Fix Committed Status in libfprint package in Ubuntu: Fix Released Status in libfprint source package in Jammy: Fix Released Status in libfprint source package in Lunar: Confirmed Status in libfprint source package in Mantic: Fix Released Bug description: This patch is upstreamed: - https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/433 [Impact] * HP laptops provide clear fingerprint from BIOS, user can enroll finger on Synaptics device after clear from BIOS. [Test Plan] * Enroll one random finger * Reboot and enter BIOS to reset fingerprint device (HP laptops) * Boot into system and re-enroll the finger * Login system with enrolled finger [Where problems could occur] * The patch only fix the issue with clear fingerprint from BIOS on Synaptics device, won't impact other vendor. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034481/+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 2028082] Re: Update glib to 2.76.4
Hello Jeremy, or anyone else affected, Accepted glib2.0 into lunar-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.76.4-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- lunar to verification-done-lunar. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-lunar. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: glib2.0 (Ubuntu Lunar) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2028082 Title: Update glib to 2.76.4 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Lunar: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 2.76 series The current release in Ubuntu 23.04 is 2.76.1 https://gitlab.gnome.org/GNOME/glib/-/blob/2.76.4/NEWS Test Case 1 --- glib has an extensive test suite. Failing tests will fail the build. This update will also trigger a lot of autopkgtests. Ensure that there aren't autopkgtest regressions triggered by this update and that the builds complete successfully Test Case 2 --- Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like the terminal, the file browser and epiphany-browser What Could Go Wrong --- This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Other Info -- The upstream gnome-remote-desktop maintainer requested that we do this update to fix a frequent gnome-remote-desktop crash that shows on errors.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2028082/+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 1798450] Re: [snap] File dialogs show snap's home directory instead of user's
As said in #12 this should be fixed by now. If not, please state if this is observed in both programs (Libreoffice and Chromium) or only one of them or a different one, and also attach the output of apt list --installed | grep desktop-portal ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Incomplete ** Changed in: libreoffice (Ubuntu) Status: Confirmed => Incomplete -- 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/1798450 Title: [snap] File dialogs show snap's home directory instead of user's Status in chromium-browser package in Ubuntu: Incomplete Status in libreoffice package in Ubuntu: Incomplete Bug description: How to reproduce: - Find a web page that has a file chooser, e.g. https://developer.mozilla.org/docs/Web/HTML/Element/input/file - Click the "Choose File" button - Click "Home" if you didn't start here - See that Chromium uses `/home/$USER/snap/chromium/500` as the home folder Expected behavior: The file picker should use the user's home folder, not the snap's, because everything else would be confusing for end users. Versions: snap2.35.4+18.10 snapd 2.35.4+18.10 series 16 ubuntu 18.10 kernel 4.18.11-surface-linux-surface Chromium 70.0.3538.67 snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1798450/+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 2037235] Re: 45.0: vsync broken in many games, with dual monitors
** Changed in: mutter (Ubuntu) Status: Incomplete => Fix Committed ** Tags added: fixed-in-mutter-45.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/2037235 Title: 45.0: vsync broken in many games, with dual monitors Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Bug description: I put all the details upstream: https://gitlab.gnome.org/GNOME/mutter/-/issues/3035 Affected version Ubuntu 23.10, Wayland session Regression between 45.rc and 45.0. Dual 4K monitors, 100% desktop scaling. Bug summary The framerate goes way over vsync even with Sync to vsync set in all games tested so far. Steps to reproduce I compiled vanilla Mutter from source and bisected it to dfd58ca8 !3259 (merged) , reverting that on top of main fixes the problem again. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2037235/+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 2038409] [NEW] package gdm3 42.0-1ubuntu7.22.04.3 failed to install/upgrade: installed gdm3 package pre-removal script subprocess returned error exit status 5
Public bug reported: I had an issue with on-board amd graphic which Ubuntu was not able to use the graphic properly for two monitors and couldn't provide a high resolution for those monitors. I changed GRUB_CMDLINE_LINUX_DEFAULT value in /etc/default/grub file to: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash amdgpu.sg_display=0" and it solved my graphic issue. Description:Ubuntu 22.04.3 LTS Release:22.04 CPU: amd rayzen 9 7950x 16-core processor RAM: 64GB motherboard: ASUS TUF GAMING X670E-PLUS ProblemType: Package DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7.22.04.3 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Sep 25 18:26:48 2023 ErrorMessage: installed gdm3 package pre-removal script subprocess returned error exit status 5 InstallationDate: Installed on 2023-09-08 (25 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.12, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: gdm3 Title: package gdm3 42.0-1ubuntu7.22.04.3 failed to install/upgrade: installed gdm3 package pre-removal script subprocess returned error exit status 5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy third-party-packages -- 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/2038409 Title: package gdm3 42.0-1ubuntu7.22.04.3 failed to install/upgrade: installed gdm3 package pre-removal script subprocess returned error exit status 5 Status in gdm3 package in Ubuntu: New Bug description: I had an issue with on-board amd graphic which Ubuntu was not able to use the graphic properly for two monitors and couldn't provide a high resolution for those monitors. I changed GRUB_CMDLINE_LINUX_DEFAULT value in /etc/default/grub file to: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash amdgpu.sg_display=0" and it solved my graphic issue. Description: Ubuntu 22.04.3 LTS Release: 22.04 CPU: amd rayzen 9 7950x 16-core processor RAM: 64GB motherboard: ASUS TUF GAMING X670E-PLUS ProblemType: Package DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7.22.04.3 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Sep 25 18:26:48 2023 ErrorMessage: installed gdm3 package pre-removal script subprocess returned error exit status 5 InstallationDate: Installed on 2023-09-08 (25 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: /usr/bin/python3.10, Python 3.10.12, python-is-python3, 3.9.2-2 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: gdm3 Title: package gdm3 42.0-1ubuntu7.22.04.3 failed to install/upgrade: installed gdm3 package pre-removal script subprocess returned error exit status 5 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2038409/+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