[Desktop-packages] [Bug 1997142] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1997142/+attachment/5631554/+files/monitors.xml.txt ** Description changed: When using a Wayland session with kernel 5.15.0-53-generic gnome-shell may sometimes crash and restart. This happened to me when using a chromium-based browser (Brave). ➜ ~ uname -r 5.15.0-53-generic - ➜ ~ printenv XDG_SESSION_TYPE + ➜ ~ printenv XDG_SESSION_TYPE wayland The issue does not happen on the previous version of the kernel which is - 5.15.0-52-generic. + 5.15.0-52-generic or on the 5.15.0-53-generic kernel when using an X11 + session. apt policy brave-browser brave-browser: - Installed: 1.45.127 - Candidate: 1.45.127 - --- + Installed: 1.45.127 + Candidate: 1.45.127 + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-01-08 (679 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 42.5-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: mutter-common 42.5-0ubuntu1 Tags: jammy wayland-session Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (211 days ago) UserGroups: adm cdrom cvdnetwork dialout dip kvm libvirt lpadmin lxd plugdev render sambashare sudo video _MarkForUpload: True -- 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/1997142 Title: gnome-shell (wayland session) crashes on kernel 5.15.0-53-generic when some applications are started Status in gnome-shell package in Ubuntu: New Bug description: When using a Wayland session with kernel 5.15.0-53-generic gnome-shell may sometimes crash and restart. This happened to me when using a chromium-based browser (Brave). ➜ ~ uname -r 5.15.0-53-generic ➜ ~ printenv XDG_SESSION_TYPE wayland The issue does not happen on the previous version of the kernel which is 5.15.0-52-generic or on the 5.15.0-53-generic kernel when using an X11 session. apt policy brave-browser brave-browser: Installed: 1.45.127 Candidate: 1.45.127 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-01-08 (679 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 42.5-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: mutter-common 42.5-0ubuntu1 Tags: jammy wayland-session Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (211 days ago) UserGroups: adm cdrom cvdnetwork dialout dip kvm libvirt lpadmin lxd plugdev render sambashare sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1997142/+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 1997142] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1997142/+attachment/5631553/+files/ShellJournal.txt -- 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/1997142 Title: gnome-shell (wayland session) crashes on kernel 5.15.0-53-generic when some applications are started Status in gnome-shell package in Ubuntu: New Bug description: When using a Wayland session with kernel 5.15.0-53-generic gnome-shell may sometimes crash and restart. This happened to me when using a chromium-based browser (Brave). ➜ ~ uname -r 5.15.0-53-generic ➜ ~ printenv XDG_SESSION_TYPE wayland The issue does not happen on the previous version of the kernel which is 5.15.0-52-generic or on the 5.15.0-53-generic kernel when using an X11 session. apt policy brave-browser brave-browser: Installed: 1.45.127 Candidate: 1.45.127 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-01-08 (679 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 42.5-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: mutter-common 42.5-0ubuntu1 Tags: jammy wayland-session Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (211 days ago) UserGroups: adm cdrom cvdnetwork dialout dip kvm libvirt lpadmin lxd plugdev render sambashare sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1997142/+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 1997142] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1997142/+attachment/5631552/+files/ProcEnviron.txt -- 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/1997142 Title: gnome-shell (wayland session) crashes on kernel 5.15.0-53-generic when some applications are started Status in gnome-shell package in Ubuntu: New Bug description: When using a Wayland session with kernel 5.15.0-53-generic gnome-shell may sometimes crash and restart. This happened to me when using a chromium-based browser (Brave). ➜ ~ uname -r 5.15.0-53-generic ➜ ~ printenv XDG_SESSION_TYPE wayland The issue does not happen on the previous version of the kernel which is 5.15.0-52-generic or on the 5.15.0-53-generic kernel when using an X11 session. apt policy brave-browser brave-browser: Installed: 1.45.127 Candidate: 1.45.127 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-01-08 (679 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 42.5-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: mutter-common 42.5-0ubuntu1 Tags: jammy wayland-session Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (211 days ago) UserGroups: adm cdrom cvdnetwork dialout dip kvm libvirt lpadmin lxd plugdev render sambashare sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1997142/+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 1997142] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1997142/+attachment/5631549/+files/Dependencies.txt -- 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/1997142 Title: gnome-shell (wayland session) crashes on kernel 5.15.0-53-generic when some applications are started Status in gnome-shell package in Ubuntu: New Bug description: When using a Wayland session with kernel 5.15.0-53-generic gnome-shell may sometimes crash and restart. This happened to me when using a chromium-based browser (Brave). ➜ ~ uname -r 5.15.0-53-generic ➜ ~ printenv XDG_SESSION_TYPE wayland The issue does not happen on the previous version of the kernel which is 5.15.0-52-generic or on the 5.15.0-53-generic kernel when using an X11 session. apt policy brave-browser brave-browser: Installed: 1.45.127 Candidate: 1.45.127 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-01-08 (679 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 42.5-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: mutter-common 42.5-0ubuntu1 Tags: jammy wayland-session Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (211 days ago) UserGroups: adm cdrom cvdnetwork dialout dip kvm libvirt lpadmin lxd plugdev render sambashare sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1997142/+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 1997142] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1997142/+attachment/5631551/+files/ProcCpuinfoMinimal.txt -- 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/1997142 Title: gnome-shell (wayland session) crashes on kernel 5.15.0-53-generic when some applications are started Status in gnome-shell package in Ubuntu: New Bug description: When using a Wayland session with kernel 5.15.0-53-generic gnome-shell may sometimes crash and restart. This happened to me when using a chromium-based browser (Brave). ➜ ~ uname -r 5.15.0-53-generic ➜ ~ printenv XDG_SESSION_TYPE wayland The issue does not happen on the previous version of the kernel which is 5.15.0-52-generic or on the 5.15.0-53-generic kernel when using an X11 session. apt policy brave-browser brave-browser: Installed: 1.45.127 Candidate: 1.45.127 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-01-08 (679 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 42.5-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: mutter-common 42.5-0ubuntu1 Tags: jammy wayland-session Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (211 days ago) UserGroups: adm cdrom cvdnetwork dialout dip kvm libvirt lpadmin lxd plugdev render sambashare sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1997142/+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 1997142] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1997142/+attachment/5631550/+files/GsettingsChanges.txt -- 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/1997142 Title: gnome-shell (wayland session) crashes on kernel 5.15.0-53-generic when some applications are started Status in gnome-shell package in Ubuntu: New Bug description: When using a Wayland session with kernel 5.15.0-53-generic gnome-shell may sometimes crash and restart. This happened to me when using a chromium-based browser (Brave). ➜ ~ uname -r 5.15.0-53-generic ➜ ~ printenv XDG_SESSION_TYPE wayland The issue does not happen on the previous version of the kernel which is 5.15.0-52-generic or on the 5.15.0-53-generic kernel when using an X11 session. apt policy brave-browser brave-browser: Installed: 1.45.127 Candidate: 1.45.127 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-01-08 (679 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 42.5-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: mutter-common 42.5-0ubuntu1 Tags: jammy wayland-session Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (211 days ago) UserGroups: adm cdrom cvdnetwork dialout dip kvm libvirt lpadmin lxd plugdev render sambashare sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1997142/+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 1997142] [NEW] gnome-shell (wayland session) crashes on kernel 5.15.0-53-generic when some applications are started
Public bug reported: When using a Wayland session with kernel 5.15.0-53-generic gnome-shell may sometimes crash and restart. This happened to me when using a chromium-based browser (Brave). ➜ ~ uname -r 5.15.0-53-generic ➜ ~ printenv XDG_SESSION_TYPE wayland The issue does not happen on the previous version of the kernel which is 5.15.0-52-generic or on the 5.15.0-53-generic kernel when using an X11 session. apt policy brave-browser brave-browser: Installed: 1.45.127 Candidate: 1.45.127 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-01-08 (679 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 42.5-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: mutter-common 42.5-0ubuntu1 Tags: jammy wayland-session Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (211 days ago) UserGroups: adm cdrom cvdnetwork dialout dip kvm libvirt lpadmin lxd plugdev render sambashare sudo video _MarkForUpload: True ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected jammy wayland-session ** Tags added: apport-collected jammy wayland-session ** Description changed: When using a Wayland session with kernel 5.15.0-53-generic gnome-shell may sometimes crash and restart. This happened to me when using a chromium-based browser (Brave). ➜ ~ uname -r 5.15.0-53-generic ➜ ~ printenv XDG_SESSION_TYPE wayland The issue does not happen on the previous version of the kernel which is 5.15.0-52-generic. apt policy brave-browser brave-browser: Installed: 1.45.127 Candidate: 1.45.127 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2021-01-08 (679 days ago) + InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: gnome-shell 42.5-0ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 + RelatedPackageVersions: mutter-common 42.5-0ubuntu1 + Tags: jammy wayland-session + Uname: Linux 5.15.0-53-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-04-21 (211 days ago) + UserGroups: adm cdrom cvdnetwork dialout dip kvm libvirt lpadmin lxd plugdev render sambashare sudo video + _MarkForUpload: True -- 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/1997142 Title: gnome-shell (wayland session) crashes on kernel 5.15.0-53-generic when some applications are started Status in gnome-shell package in Ubuntu: New Bug description: When using a Wayland session with kernel 5.15.0-53-generic gnome-shell may sometimes crash and restart. This happened to me when using a chromium-based browser (Brave). ➜ ~ uname -r 5.15.0-53-generic ➜ ~ printenv XDG_SESSION_TYPE wayland The issue does not happen on the previous version of the kernel which is 5.15.0-52-generic or on the 5.15.0-53-generic kernel when using an X11 session. apt policy brave-browser brave-browser: Installed: 1.45.127 Candidate: 1.45.127 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-01-08 (679 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 42.5-0ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: mutter-common 42.5-0ubuntu1 Tags: jammy wayland-session Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-21 (211 days ago) UserGroups: adm cdrom cvdnetwork dialout dip kvm libvirt lpadmin lxd plugdev render sambashare sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1997142/+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 1995207] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1995207/+attachment/5627853/+files/ProcEnviron.txt -- 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/1995207 Title: [22.10] gnome-shell: page allocation failure Status in gnome-shell package in Ubuntu: New Bug description: Gnome shell crashed while I was doing web browsing. A crash report was also submitted via apport. This is a fresh install of Ubuntu 22.10. ~$ uname -r 5.19.0-23-generic HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD Radeon RX 6500M discrete card (AMD SmartShift). $ lspci -n -s 03:00.0 03:00.0 0380: 1002:743f (rev c3) $ lspci -n -s 67:00.0 67:00.0 0300: 1002:1681 (rev 12) 03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400 / 6500 XT] (rev c3) 67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] (rev 12) $ printenv XDG_SESSION_TYPE wayland oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), nodemask=(null),cpuset=/,mems_allowed=0 oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 5.19.0-23-generic #24-Ubuntu oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS N3GET42W (1.22 ) 09/06/2022 oct 30 13:36:19 z16 kernel: Call Trace: oct 30 13:36:19 z16 kernel: oct 30 13:36:19 z16 kernel: show_stack+0x4e/0x61 oct 30 13:36:19 z16 kernel: dump_stack_lvl+0x4a/0x6d oct 30 13:36:19 z16 kernel: dump_stack+0x10/0x18 oct 30 13:36:19 z16 kernel: warn_alloc+0x164/0x190 oct 30 13:36:19 z16 kernel: __alloc_pages_slowpath.constprop.0+0x975/0x9b0 oct 30 13:36:19 z16 kernel: __alloc_pages+0x31d/0x350 oct 30 13:36:19 z16 kernel: alloc_pages+0x90/0x1c0 oct 30 13:36:19 z16 kernel: ttm_pool_alloc+0x395/0x580 [ttm] oct 30 13:36:19 z16 kernel: amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu] oct 30 13:36:19 z16 kernel: ttm_tt_populate+0xbc/0x1a0 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_handle_move_mem+0x21a/0x280 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_validate+0xf8/0x130 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_init_reserved+0x18d/0x260 [ttm] oct 30 13:36:19 z16 kernel: amdgpu_bo_create+0x1d0/0x4b0 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_bo_create_user+0x40/0x70 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_gem_force_release+0x190/0x190 [amdgpu] oct 30 13:36:19 z16 kernel: drm_ioctl_kernel+0xd6/0x180 [drm] oct 30 13:36:19 z16 kernel: drm_ioctl+0x29d/0x4d0 [drm] oct 30 13:36:19 z16 kernel: ? amdgpu_gem_force_release+0x190/0x190 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_drm_ioctl+0x4e/0x90 [amdgpu] oct 30 13:36:19 z16 kernel: __x64_sys_ioctl+0xa0/0xe0 oct 30 13:36:19 z16 kernel: do_syscall_64+0x5b/0x90 oct 30 13:36:19 z16 kernel: ? do_user_addr_fault+0x1df/0x680 oct 30 13:36:19 z16 kernel: ? do_syscall_64+0x67/0x90 oct 30 13:36:19 z16 kernel: ? exit_to_user_mode_prepare+0x30/0xb0 oct 30 13:36:19 z16 kernel: ? irqentry_exit_to_user_mode+0x9/0x20 oct 30 13:36:19 z16 kernel: ? irqentry_exit+0x43/0x50 oct 30 13:36:19 z16 kernel: ? exc_page_fault+0x91/0x1b0 oct 30 13:36:19 z16 kernel: entry_SYSCALL_64_after_hwframe+0x63/0xcd oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 ORIG_RAX: 0010 oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 7fc5dcd12d8f oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 0011 oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 7fc5dcdf6ec0 oct 30 13:36:19 z16 kernel: R10: R11: 0246 R12: c0206440 oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 0013 oct 30 13:36:19 z16 kernel: oct 30 13:36:19 z16 kernel: Mem-Info: oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 isolated_anon:0 active_file:448331 inactive_file:919182 isolated_file:0 unevictable:214 dirty:247 writeback:2 slab_reclaimable:41947 slab_unreclaimable:65287
[Desktop-packages] [Bug 1995207] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1995207/+attachment/5627854/+files/ShellJournal.txt -- 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/1995207 Title: [22.10] gnome-shell: page allocation failure Status in gnome-shell package in Ubuntu: New Bug description: Gnome shell crashed while I was doing web browsing. A crash report was also submitted via apport. This is a fresh install of Ubuntu 22.10. ~$ uname -r 5.19.0-23-generic HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD Radeon RX 6500M discrete card (AMD SmartShift). $ lspci -n -s 03:00.0 03:00.0 0380: 1002:743f (rev c3) $ lspci -n -s 67:00.0 67:00.0 0300: 1002:1681 (rev 12) 03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400 / 6500 XT] (rev c3) 67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] (rev 12) $ printenv XDG_SESSION_TYPE wayland oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), nodemask=(null),cpuset=/,mems_allowed=0 oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 5.19.0-23-generic #24-Ubuntu oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS N3GET42W (1.22 ) 09/06/2022 oct 30 13:36:19 z16 kernel: Call Trace: oct 30 13:36:19 z16 kernel: oct 30 13:36:19 z16 kernel: show_stack+0x4e/0x61 oct 30 13:36:19 z16 kernel: dump_stack_lvl+0x4a/0x6d oct 30 13:36:19 z16 kernel: dump_stack+0x10/0x18 oct 30 13:36:19 z16 kernel: warn_alloc+0x164/0x190 oct 30 13:36:19 z16 kernel: __alloc_pages_slowpath.constprop.0+0x975/0x9b0 oct 30 13:36:19 z16 kernel: __alloc_pages+0x31d/0x350 oct 30 13:36:19 z16 kernel: alloc_pages+0x90/0x1c0 oct 30 13:36:19 z16 kernel: ttm_pool_alloc+0x395/0x580 [ttm] oct 30 13:36:19 z16 kernel: amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu] oct 30 13:36:19 z16 kernel: ttm_tt_populate+0xbc/0x1a0 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_handle_move_mem+0x21a/0x280 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_validate+0xf8/0x130 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_init_reserved+0x18d/0x260 [ttm] oct 30 13:36:19 z16 kernel: amdgpu_bo_create+0x1d0/0x4b0 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_bo_create_user+0x40/0x70 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_gem_force_release+0x190/0x190 [amdgpu] oct 30 13:36:19 z16 kernel: drm_ioctl_kernel+0xd6/0x180 [drm] oct 30 13:36:19 z16 kernel: drm_ioctl+0x29d/0x4d0 [drm] oct 30 13:36:19 z16 kernel: ? amdgpu_gem_force_release+0x190/0x190 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_drm_ioctl+0x4e/0x90 [amdgpu] oct 30 13:36:19 z16 kernel: __x64_sys_ioctl+0xa0/0xe0 oct 30 13:36:19 z16 kernel: do_syscall_64+0x5b/0x90 oct 30 13:36:19 z16 kernel: ? do_user_addr_fault+0x1df/0x680 oct 30 13:36:19 z16 kernel: ? do_syscall_64+0x67/0x90 oct 30 13:36:19 z16 kernel: ? exit_to_user_mode_prepare+0x30/0xb0 oct 30 13:36:19 z16 kernel: ? irqentry_exit_to_user_mode+0x9/0x20 oct 30 13:36:19 z16 kernel: ? irqentry_exit+0x43/0x50 oct 30 13:36:19 z16 kernel: ? exc_page_fault+0x91/0x1b0 oct 30 13:36:19 z16 kernel: entry_SYSCALL_64_after_hwframe+0x63/0xcd oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 ORIG_RAX: 0010 oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 7fc5dcd12d8f oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 0011 oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 7fc5dcdf6ec0 oct 30 13:36:19 z16 kernel: R10: R11: 0246 R12: c0206440 oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 0013 oct 30 13:36:19 z16 kernel: oct 30 13:36:19 z16 kernel: Mem-Info: oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 isolated_anon:0 active_file:448331 inactive_file:919182 isolated_file:0 unevictable:214 dirty:247 writeback:2 slab_reclaimable:41947 slab_unreclaimable:65287
[Desktop-packages] [Bug 1995207] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1995207/+attachment/5627851/+files/GsettingsChanges.txt -- 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/1995207 Title: [22.10] gnome-shell: page allocation failure Status in gnome-shell package in Ubuntu: New Bug description: Gnome shell crashed while I was doing web browsing. A crash report was also submitted via apport. This is a fresh install of Ubuntu 22.10. ~$ uname -r 5.19.0-23-generic HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD Radeon RX 6500M discrete card (AMD SmartShift). $ lspci -n -s 03:00.0 03:00.0 0380: 1002:743f (rev c3) $ lspci -n -s 67:00.0 67:00.0 0300: 1002:1681 (rev 12) 03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400 / 6500 XT] (rev c3) 67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] (rev 12) $ printenv XDG_SESSION_TYPE wayland oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), nodemask=(null),cpuset=/,mems_allowed=0 oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 5.19.0-23-generic #24-Ubuntu oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS N3GET42W (1.22 ) 09/06/2022 oct 30 13:36:19 z16 kernel: Call Trace: oct 30 13:36:19 z16 kernel: oct 30 13:36:19 z16 kernel: show_stack+0x4e/0x61 oct 30 13:36:19 z16 kernel: dump_stack_lvl+0x4a/0x6d oct 30 13:36:19 z16 kernel: dump_stack+0x10/0x18 oct 30 13:36:19 z16 kernel: warn_alloc+0x164/0x190 oct 30 13:36:19 z16 kernel: __alloc_pages_slowpath.constprop.0+0x975/0x9b0 oct 30 13:36:19 z16 kernel: __alloc_pages+0x31d/0x350 oct 30 13:36:19 z16 kernel: alloc_pages+0x90/0x1c0 oct 30 13:36:19 z16 kernel: ttm_pool_alloc+0x395/0x580 [ttm] oct 30 13:36:19 z16 kernel: amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu] oct 30 13:36:19 z16 kernel: ttm_tt_populate+0xbc/0x1a0 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_handle_move_mem+0x21a/0x280 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_validate+0xf8/0x130 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_init_reserved+0x18d/0x260 [ttm] oct 30 13:36:19 z16 kernel: amdgpu_bo_create+0x1d0/0x4b0 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_bo_create_user+0x40/0x70 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_gem_force_release+0x190/0x190 [amdgpu] oct 30 13:36:19 z16 kernel: drm_ioctl_kernel+0xd6/0x180 [drm] oct 30 13:36:19 z16 kernel: drm_ioctl+0x29d/0x4d0 [drm] oct 30 13:36:19 z16 kernel: ? amdgpu_gem_force_release+0x190/0x190 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_drm_ioctl+0x4e/0x90 [amdgpu] oct 30 13:36:19 z16 kernel: __x64_sys_ioctl+0xa0/0xe0 oct 30 13:36:19 z16 kernel: do_syscall_64+0x5b/0x90 oct 30 13:36:19 z16 kernel: ? do_user_addr_fault+0x1df/0x680 oct 30 13:36:19 z16 kernel: ? do_syscall_64+0x67/0x90 oct 30 13:36:19 z16 kernel: ? exit_to_user_mode_prepare+0x30/0xb0 oct 30 13:36:19 z16 kernel: ? irqentry_exit_to_user_mode+0x9/0x20 oct 30 13:36:19 z16 kernel: ? irqentry_exit+0x43/0x50 oct 30 13:36:19 z16 kernel: ? exc_page_fault+0x91/0x1b0 oct 30 13:36:19 z16 kernel: entry_SYSCALL_64_after_hwframe+0x63/0xcd oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 ORIG_RAX: 0010 oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 7fc5dcd12d8f oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 0011 oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 7fc5dcdf6ec0 oct 30 13:36:19 z16 kernel: R10: R11: 0246 R12: c0206440 oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 0013 oct 30 13:36:19 z16 kernel: oct 30 13:36:19 z16 kernel: Mem-Info: oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 isolated_anon:0 active_file:448331 inactive_file:919182 isolated_file:0 unevictable:214 dirty:247 writeback:2 slab_reclaimable:41947 slab_unreclaimable:65287
[Desktop-packages] [Bug 1995207] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1995207/+attachment/5627852/+files/ProcCpuinfoMinimal.txt -- 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/1995207 Title: [22.10] gnome-shell: page allocation failure Status in gnome-shell package in Ubuntu: New Bug description: Gnome shell crashed while I was doing web browsing. A crash report was also submitted via apport. This is a fresh install of Ubuntu 22.10. ~$ uname -r 5.19.0-23-generic HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD Radeon RX 6500M discrete card (AMD SmartShift). $ lspci -n -s 03:00.0 03:00.0 0380: 1002:743f (rev c3) $ lspci -n -s 67:00.0 67:00.0 0300: 1002:1681 (rev 12) 03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400 / 6500 XT] (rev c3) 67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] (rev 12) $ printenv XDG_SESSION_TYPE wayland oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), nodemask=(null),cpuset=/,mems_allowed=0 oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 5.19.0-23-generic #24-Ubuntu oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS N3GET42W (1.22 ) 09/06/2022 oct 30 13:36:19 z16 kernel: Call Trace: oct 30 13:36:19 z16 kernel: oct 30 13:36:19 z16 kernel: show_stack+0x4e/0x61 oct 30 13:36:19 z16 kernel: dump_stack_lvl+0x4a/0x6d oct 30 13:36:19 z16 kernel: dump_stack+0x10/0x18 oct 30 13:36:19 z16 kernel: warn_alloc+0x164/0x190 oct 30 13:36:19 z16 kernel: __alloc_pages_slowpath.constprop.0+0x975/0x9b0 oct 30 13:36:19 z16 kernel: __alloc_pages+0x31d/0x350 oct 30 13:36:19 z16 kernel: alloc_pages+0x90/0x1c0 oct 30 13:36:19 z16 kernel: ttm_pool_alloc+0x395/0x580 [ttm] oct 30 13:36:19 z16 kernel: amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu] oct 30 13:36:19 z16 kernel: ttm_tt_populate+0xbc/0x1a0 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_handle_move_mem+0x21a/0x280 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_validate+0xf8/0x130 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_init_reserved+0x18d/0x260 [ttm] oct 30 13:36:19 z16 kernel: amdgpu_bo_create+0x1d0/0x4b0 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_bo_create_user+0x40/0x70 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_gem_force_release+0x190/0x190 [amdgpu] oct 30 13:36:19 z16 kernel: drm_ioctl_kernel+0xd6/0x180 [drm] oct 30 13:36:19 z16 kernel: drm_ioctl+0x29d/0x4d0 [drm] oct 30 13:36:19 z16 kernel: ? amdgpu_gem_force_release+0x190/0x190 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_drm_ioctl+0x4e/0x90 [amdgpu] oct 30 13:36:19 z16 kernel: __x64_sys_ioctl+0xa0/0xe0 oct 30 13:36:19 z16 kernel: do_syscall_64+0x5b/0x90 oct 30 13:36:19 z16 kernel: ? do_user_addr_fault+0x1df/0x680 oct 30 13:36:19 z16 kernel: ? do_syscall_64+0x67/0x90 oct 30 13:36:19 z16 kernel: ? exit_to_user_mode_prepare+0x30/0xb0 oct 30 13:36:19 z16 kernel: ? irqentry_exit_to_user_mode+0x9/0x20 oct 30 13:36:19 z16 kernel: ? irqentry_exit+0x43/0x50 oct 30 13:36:19 z16 kernel: ? exc_page_fault+0x91/0x1b0 oct 30 13:36:19 z16 kernel: entry_SYSCALL_64_after_hwframe+0x63/0xcd oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 ORIG_RAX: 0010 oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 7fc5dcd12d8f oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 0011 oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 7fc5dcdf6ec0 oct 30 13:36:19 z16 kernel: R10: R11: 0246 R12: c0206440 oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 0013 oct 30 13:36:19 z16 kernel: oct 30 13:36:19 z16 kernel: Mem-Info: oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 isolated_anon:0 active_file:448331 inactive_file:919182 isolated_file:0 unevictable:214 dirty:247 writeback:2 slab_reclaimable:41947 slab_unreclaimable:65287
[Desktop-packages] [Bug 1995207] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1995207/+attachment/5627850/+files/Dependencies.txt -- 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/1995207 Title: [22.10] gnome-shell: page allocation failure Status in gnome-shell package in Ubuntu: New Bug description: Gnome shell crashed while I was doing web browsing. A crash report was also submitted via apport. This is a fresh install of Ubuntu 22.10. ~$ uname -r 5.19.0-23-generic HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD Radeon RX 6500M discrete card (AMD SmartShift). $ lspci -n -s 03:00.0 03:00.0 0380: 1002:743f (rev c3) $ lspci -n -s 67:00.0 67:00.0 0300: 1002:1681 (rev 12) 03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400 / 6500 XT] (rev c3) 67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] (rev 12) $ printenv XDG_SESSION_TYPE wayland oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), nodemask=(null),cpuset=/,mems_allowed=0 oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 5.19.0-23-generic #24-Ubuntu oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS N3GET42W (1.22 ) 09/06/2022 oct 30 13:36:19 z16 kernel: Call Trace: oct 30 13:36:19 z16 kernel: oct 30 13:36:19 z16 kernel: show_stack+0x4e/0x61 oct 30 13:36:19 z16 kernel: dump_stack_lvl+0x4a/0x6d oct 30 13:36:19 z16 kernel: dump_stack+0x10/0x18 oct 30 13:36:19 z16 kernel: warn_alloc+0x164/0x190 oct 30 13:36:19 z16 kernel: __alloc_pages_slowpath.constprop.0+0x975/0x9b0 oct 30 13:36:19 z16 kernel: __alloc_pages+0x31d/0x350 oct 30 13:36:19 z16 kernel: alloc_pages+0x90/0x1c0 oct 30 13:36:19 z16 kernel: ttm_pool_alloc+0x395/0x580 [ttm] oct 30 13:36:19 z16 kernel: amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu] oct 30 13:36:19 z16 kernel: ttm_tt_populate+0xbc/0x1a0 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_handle_move_mem+0x21a/0x280 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_validate+0xf8/0x130 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_init_reserved+0x18d/0x260 [ttm] oct 30 13:36:19 z16 kernel: amdgpu_bo_create+0x1d0/0x4b0 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_bo_create_user+0x40/0x70 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_gem_force_release+0x190/0x190 [amdgpu] oct 30 13:36:19 z16 kernel: drm_ioctl_kernel+0xd6/0x180 [drm] oct 30 13:36:19 z16 kernel: drm_ioctl+0x29d/0x4d0 [drm] oct 30 13:36:19 z16 kernel: ? amdgpu_gem_force_release+0x190/0x190 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_drm_ioctl+0x4e/0x90 [amdgpu] oct 30 13:36:19 z16 kernel: __x64_sys_ioctl+0xa0/0xe0 oct 30 13:36:19 z16 kernel: do_syscall_64+0x5b/0x90 oct 30 13:36:19 z16 kernel: ? do_user_addr_fault+0x1df/0x680 oct 30 13:36:19 z16 kernel: ? do_syscall_64+0x67/0x90 oct 30 13:36:19 z16 kernel: ? exit_to_user_mode_prepare+0x30/0xb0 oct 30 13:36:19 z16 kernel: ? irqentry_exit_to_user_mode+0x9/0x20 oct 30 13:36:19 z16 kernel: ? irqentry_exit+0x43/0x50 oct 30 13:36:19 z16 kernel: ? exc_page_fault+0x91/0x1b0 oct 30 13:36:19 z16 kernel: entry_SYSCALL_64_after_hwframe+0x63/0xcd oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 ORIG_RAX: 0010 oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 7fc5dcd12d8f oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 0011 oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 7fc5dcdf6ec0 oct 30 13:36:19 z16 kernel: R10: R11: 0246 R12: c0206440 oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 0013 oct 30 13:36:19 z16 kernel: oct 30 13:36:19 z16 kernel: Mem-Info: oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 isolated_anon:0 active_file:448331 inactive_file:919182 isolated_file:0 unevictable:214 dirty:247 writeback:2 slab_reclaimable:41947 slab_unreclaimable:65287
[Desktop-packages] [Bug 1995207] [NEW] [22.10] gnome-shell: page allocation failure
Public bug reported: Gnome shell crashed while I was doing web browsing. A crash report was also submitted via apport. This is a fresh install of Ubuntu 22.10. ~$ uname -r 5.19.0-23-generic HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD Radeon RX 6500M discrete card (AMD SmartShift). $ lspci -n -s 03:00.0 03:00.0 0380: 1002:743f (rev c3) $ lspci -n -s 67:00.0 67:00.0 0300: 1002:1681 (rev 12) 03:00.0 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400 / 6500 XT] (rev c3) 67:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt [Radeon 680M] (rev 12) $ printenv XDG_SESSION_TYPE wayland oct 30 13:36:19 z16 kernel: gnome-shell: page allocation failure: order:0, mode:0x104dc4(GFP_USER|GFP_DMA32|__GFP_RETRY_MAYFAIL|__GFP_ZERO), nodemask=(null),cpuset=/,mems_allowed=0 oct 30 13:36:19 z16 kernel: CPU: 1 PID: 2446 Comm: gnome-shell Not tainted 5.19.0-23-generic #24-Ubuntu oct 30 13:36:19 z16 kernel: Hardware name: LENOVO 21D4000HUS/21D4000HUS, BIOS N3GET42W (1.22 ) 09/06/2022 oct 30 13:36:19 z16 kernel: Call Trace: oct 30 13:36:19 z16 kernel: oct 30 13:36:19 z16 kernel: show_stack+0x4e/0x61 oct 30 13:36:19 z16 kernel: dump_stack_lvl+0x4a/0x6d oct 30 13:36:19 z16 kernel: dump_stack+0x10/0x18 oct 30 13:36:19 z16 kernel: warn_alloc+0x164/0x190 oct 30 13:36:19 z16 kernel: __alloc_pages_slowpath.constprop.0+0x975/0x9b0 oct 30 13:36:19 z16 kernel: __alloc_pages+0x31d/0x350 oct 30 13:36:19 z16 kernel: alloc_pages+0x90/0x1c0 oct 30 13:36:19 z16 kernel: ttm_pool_alloc+0x395/0x580 [ttm] oct 30 13:36:19 z16 kernel: amdgpu_ttm_tt_populate+0x42/0xa0 [amdgpu] oct 30 13:36:19 z16 kernel: ttm_tt_populate+0xbc/0x1a0 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_handle_move_mem+0x21a/0x280 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_validate+0xf8/0x130 [ttm] oct 30 13:36:19 z16 kernel: ttm_bo_init_reserved+0x18d/0x260 [ttm] oct 30 13:36:19 z16 kernel: amdgpu_bo_create+0x1d0/0x4b0 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_bo_create_user+0x40/0x70 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_gem_create_ioctl+0x155/0x3c0 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_bo_vm_destroy+0x80/0x80 [amdgpu] oct 30 13:36:19 z16 kernel: ? amdgpu_gem_force_release+0x190/0x190 [amdgpu] oct 30 13:36:19 z16 kernel: drm_ioctl_kernel+0xd6/0x180 [drm] oct 30 13:36:19 z16 kernel: drm_ioctl+0x29d/0x4d0 [drm] oct 30 13:36:19 z16 kernel: ? amdgpu_gem_force_release+0x190/0x190 [amdgpu] oct 30 13:36:19 z16 kernel: amdgpu_drm_ioctl+0x4e/0x90 [amdgpu] oct 30 13:36:19 z16 kernel: __x64_sys_ioctl+0xa0/0xe0 oct 30 13:36:19 z16 kernel: do_syscall_64+0x5b/0x90 oct 30 13:36:19 z16 kernel: ? do_user_addr_fault+0x1df/0x680 oct 30 13:36:19 z16 kernel: ? do_syscall_64+0x67/0x90 oct 30 13:36:19 z16 kernel: ? exit_to_user_mode_prepare+0x30/0xb0 oct 30 13:36:19 z16 kernel: ? irqentry_exit_to_user_mode+0x9/0x20 oct 30 13:36:19 z16 kernel: ? irqentry_exit+0x43/0x50 oct 30 13:36:19 z16 kernel: ? exc_page_fault+0x91/0x1b0 oct 30 13:36:19 z16 kernel: entry_SYSCALL_64_after_hwframe+0x63/0xcd oct 30 13:36:19 z16 kernel: RIP: 0033:0x7fc5dcd12d8f oct 30 13:36:19 z16 kernel: Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10 00 00 00 48 89 44 24 08 48 8d 44 24 20 48 89 44 24 10 b8 10 00 00 00 0f 05 <89> c2 3d 00 f0 ff ff 77 18 48 8b 44 24 18 64 48 2b 04 25 28 00 00 oct 30 13:36:19 z16 kernel: RSP: 002b:7fff03e93c60 EFLAGS: 0246 ORIG_RAX: 0010 oct 30 13:36:19 z16 kernel: RAX: ffda RBX: 55645821ecf0 RCX: 7fc5dcd12d8f oct 30 13:36:19 z16 kernel: RDX: 7fff03e93d00 RSI: c0206440 RDI: 0011 oct 30 13:36:19 z16 kernel: RBP: 7fff03e93d00 R08: 5564562407e0 R09: 7fc5dcdf6ec0 oct 30 13:36:19 z16 kernel: R10: R11: 0246 R12: c0206440 oct 30 13:36:19 z16 kernel: R13: 0011 R14: 02298000 R15: 0013 oct 30 13:36:19 z16 kernel: oct 30 13:36:19 z16 kernel: Mem-Info: oct 30 13:36:19 z16 kernel: active_anon:1358 inactive_anon:955291 isolated_anon:0 active_file:448331 inactive_file:919182 isolated_file:0 unevictable:214 dirty:247 writeback:2 slab_reclaimable:41947 slab_unreclaimable:65287 mapped:352660 shmem:166458 pagetables:11885 bounce:0 kernel_misc_reclaimable:0 free:5048298 free_pcp:2656 free_cma:0 oct 30 13:36:19 z16 kernel: Node 0 active_anon:5432kB inactive_anon:3821164kB active_file:1793324kB inactive_file:3676728kB unevictable:856kB isolated(anon):0kB isolated(file):0kB mapped:1410640kB dirty:988kB writeback:8kB shmem:665832kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 0kB writeback_tmp:0kB kernel_stack:24076kB pagetables:47540kB
[Desktop-packages] [Bug 1863142] Re: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenSetCursor(pCurs=NULL)
I no longer get that issue with latest updates for Focal so something must have fixed it. Setting to incomplete. ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: Confirmed => Incomplete ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: Confirmed => Incomplete ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1863142 Title: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenSetCursor(pCurs=NULL) Status in nvidia-graphics-drivers package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440 package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: https://errors.ubuntu.com/problem/ea7655e8bec62deae73df2b30259cb413e61bef9 --- I observed the following on Eoan as well with nvidia drivers older than 440. 1) a windows 10 VM running in a qemu-kvm VM: pc-q35-3.1 machine type, QXL + SPICE: 2) When a host is booted with `prime-select intel` observing guest video output works fine with both virt-viewer (over SPICE) and remmina (over RDP); 3) With `prime-select nvidia` Xorg crashes as described in https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1862895 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.59 Thu Jan 30 01:00:41 UTC 2020 GCC version: gcc version 9.2.1 20200203 (Ubuntu 9.2.1-28ubuntu1) ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: ubuntu:GNOME Date: Thu Feb 13 20:16:07 2020 DistUpgraded: 2020-02-09 15:34:46,903 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 20.01.00, 5.3.0-29-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms, 20.01.00, 5.4.0-12-generic, x86_64: installed (WARNING! Diff between built and installed module!) nvidia, 440.59, 5.4.0-12-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg ExecutableTimestamp: 1579009393 GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. HD Graphics 630 [1a58:6755] NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. GP106M [GeForce GTX 1060 Mobile] [1a58:6755] InstallationDate: Installed on 2018-05-13 (641 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Razer Blade ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcCwd: /home/dima ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic root=UUID=8c1115d9-2cee-41a9-864f-d4e57d662706 ro rootflags=subvol=@ button.lid_init_state=open amdgpu.dpm=1 amdgpu.ppfeaturemask=0x Signal: 6 SourcePackage: nvidia-graphics-drivers StacktraceTop: System () () () () () at /lib/x86_64-linux-gnu/libpthread.so.0 Title: Xorg crashed with SIGABRT in System() UpgradeStatus: Upgraded to focal on 2020-02-09 (4 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd microk8s plugdev sambashare sudo dmi.bios.date: 02/22/2018 dmi.bios.vendor: Razer dmi.bios.version: 4.02 dmi.board.name: Razer dmi.board.vendor: Razer dmi.chassis.type: 9 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr4.02:bd02/22/2018:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr: dmi.product.family: 1A586755 dmi.product.name: Blade dmi.product.sku: RZ09-01953E72 dmi.product.version: 6.06 dmi.sys.vendor: Razer separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.3.3-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.3.3-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1
[Desktop-packages] [Bug 1863142] Re: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenSetCursor(pCurs=NULL)
Found another way to trigger this problem by opening up various documents in libreoffice and using zoom back and forth (also happens sometimes when comments are created). https://errors.ubuntu.com/oops/a906d424-6cc2-11ea-aa90-fa163e983629 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1863142 Title: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenSetCursor(pCurs=NULL) Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/ea7655e8bec62deae73df2b30259cb413e61bef9 --- I observed the following on Eoan as well with nvidia drivers older than 440. 1) a windows 10 VM running in a qemu-kvm VM: pc-q35-3.1 machine type, QXL + SPICE: 2) When a host is booted with `prime-select intel` observing guest video output works fine with both virt-viewer (over SPICE) and remmina (over RDP); 3) With `prime-select nvidia` Xorg crashes as described in https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1862895 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.59 Thu Jan 30 01:00:41 UTC 2020 GCC version: gcc version 9.2.1 20200203 (Ubuntu 9.2.1-28ubuntu1) ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: ubuntu:GNOME Date: Thu Feb 13 20:16:07 2020 DistUpgraded: 2020-02-09 15:34:46,903 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 20.01.00, 5.3.0-29-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms, 20.01.00, 5.4.0-12-generic, x86_64: installed (WARNING! Diff between built and installed module!) nvidia, 440.59, 5.4.0-12-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg ExecutableTimestamp: 1579009393 GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. HD Graphics 630 [1a58:6755] NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. GP106M [GeForce GTX 1060 Mobile] [1a58:6755] InstallationDate: Installed on 2018-05-13 (641 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Razer Blade ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcCwd: /home/dima ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic root=UUID=8c1115d9-2cee-41a9-864f-d4e57d662706 ro rootflags=subvol=@ button.lid_init_state=open amdgpu.dpm=1 amdgpu.ppfeaturemask=0x Signal: 6 SourcePackage: nvidia-graphics-drivers StacktraceTop: System () () () () () at /lib/x86_64-linux-gnu/libpthread.so.0 Title: Xorg crashed with SIGABRT in System() UpgradeStatus: Upgraded to focal on 2020-02-09 (4 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd microk8s plugdev sambashare sudo dmi.bios.date: 02/22/2018 dmi.bios.vendor: Razer dmi.bios.version: 4.02 dmi.board.name: Razer dmi.board.vendor: Razer dmi.chassis.type: 9 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr4.02:bd02/22/2018:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr: dmi.product.family: 1A586755 dmi.product.name: Blade dmi.product.sku: RZ09-01953E72 dmi.product.version: 6.06 dmi.sys.vendor: Razer separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.3.3-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.3.3-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
[Desktop-packages] [Bug 1848326] Re: [cosmic+] error booting with prime-select intel: prime-select does not update initramfs to blacklist nvidia modules
albertomilone, looks good to me. I tried switching from nvidia to intel and back rebooting on each attempt and haven't managed to reproduce the issue. Looks like reordering udev rules and/or adding another device class in your change helped (thanks a lot!). I don't see an nvidia device in lspci output as well after rebooting with `prime-select intel` done: ➜ ~ lspci | grep -i nvidia ➜ ~ ➜ ~ lspci | grep -i VGA 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) /lib/udev/rules.d/50-pm-nvidia.rules https://paste.ubuntu.com/p/2WScDVDQPq/ cat /lib/udev/rules.d/61-gdm.rules https://paste.ubuntu.com/p/5K6hgKmrG2/ # that's for nvidiafb which is normal and comes from the kmod package ➜ ~ grep -RiP nvidia /etc/modprobe.d /etc/modprobe.d/blacklist-framebuffer.conf:blacklist nvidiafb ➜ ~ uname -r 5.4.0-14-generic ➜ ~ dpkg -l | grep -P 'nvidia-prime|nvidia-driver|Xorg|gdm3' ii gdm3 3.34.1-1ubuntu1 amd64GNOME Display Manager ii nvidia-driver-440 440.59-0ubuntu2 amd64NVIDIA driver metapackage ii nvidia-prime 0.8.14 all Tools to enable NVIDIA's Prime ii xserver-xorg-core 2:1.20.7-2ubuntu1 amd64Xorg X server - core server ii xserver-xorg-legacy 2:1.20.7-2ubuntu1 amd64setuid root Xorg server wrapper ii xserver-xorg-video-nvidia-440 440.59-0ubuntu2 amd64NVIDIA binary Xorg driver -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1848326 Title: [cosmic+] error booting with prime-select intel: prime-select does not update initramfs to blacklist nvidia modules Status in nvidia-prime package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in nvidia-prime source package in Bionic: Triaged Status in ubuntu-drivers-common source package in Bionic: Triaged Status in nvidia-prime source package in Eoan: Triaged Status in ubuntu-drivers-common source package in Eoan: Triaged Bug description: when I try to boot with the iGPU selected, DE won't boot, with nvidia selected, everithing is fine. I tried uninstalling nvidia driver and it allowed my to access without any problems and intel is working fine ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-prime 0.8.13 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 16 12:41:26 2019 Dependencies: InstallationDate: Installed on 2019-09-25 (20 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190925) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/+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 1848326] Re: [cosmic+] error booting with prime-select intel: prime-select does not update initramfs to blacklist nvidia modules
I'm on focal now, just got the updated packages. I will give it a try soon. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1848326 Title: [cosmic+] error booting with prime-select intel: prime-select does not update initramfs to blacklist nvidia modules Status in nvidia-prime package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in nvidia-prime source package in Bionic: Triaged Status in ubuntu-drivers-common source package in Bionic: Triaged Status in nvidia-prime source package in Eoan: Triaged Status in ubuntu-drivers-common source package in Eoan: Triaged Bug description: when I try to boot with the iGPU selected, DE won't boot, with nvidia selected, everithing is fine. I tried uninstalling nvidia driver and it allowed my to access without any problems and intel is working fine ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-prime 0.8.13 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 16 12:41:26 2019 Dependencies: InstallationDate: Installed on 2019-09-25 (20 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190925) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/+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 1848326] Re: [cosmic+] error booting with prime-select intel: prime-select does not update initramfs to blacklist nvidia modules
Thanks, will help you with testing for sure. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1848326 Title: [cosmic+] error booting with prime-select intel: prime-select does not update initramfs to blacklist nvidia modules Status in nvidia-prime package in Ubuntu: In Progress Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in nvidia-prime source package in Bionic: Triaged Status in ubuntu-drivers-common source package in Bionic: Triaged Status in nvidia-prime source package in Eoan: Triaged Status in ubuntu-drivers-common source package in Eoan: Triaged Bug description: when I try to boot with the iGPU selected, DE won't boot, with nvidia selected, everithing is fine. I tried uninstalling nvidia driver and it allowed my to access without any problems and intel is working fine ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-prime 0.8.13 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 16 12:41:26 2019 Dependencies: InstallationDate: Installed on 2019-09-25 (20 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190925) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/+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 1863142] Re: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenSetCursor(pCurs=NULL)
Happened to me when using virt-viewer and connecting to an Ubuntu 18.04 VM via SPICE as well so this isn't specific to a guest VM it seems. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1863142 Title: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenSetCursor(pCurs=NULL) Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/ea7655e8bec62deae73df2b30259cb413e61bef9 --- I observed the following on Eoan as well with nvidia drivers older than 440. 1) a windows 10 VM running in a qemu-kvm VM: pc-q35-3.1 machine type, QXL + SPICE: 2) When a host is booted with `prime-select intel` observing guest video output works fine with both virt-viewer (over SPICE) and remmina (over RDP); 3) With `prime-select nvidia` Xorg crashes as described in https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1862895 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.59 Thu Jan 30 01:00:41 UTC 2020 GCC version: gcc version 9.2.1 20200203 (Ubuntu 9.2.1-28ubuntu1) ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: ubuntu:GNOME Date: Thu Feb 13 20:16:07 2020 DistUpgraded: 2020-02-09 15:34:46,903 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 20.01.00, 5.3.0-29-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms, 20.01.00, 5.4.0-12-generic, x86_64: installed (WARNING! Diff between built and installed module!) nvidia, 440.59, 5.4.0-12-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg ExecutableTimestamp: 1579009393 GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. HD Graphics 630 [1a58:6755] NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Razer USA Ltd. GP106M [GeForce GTX 1060 Mobile] [1a58:6755] InstallationDate: Installed on 2018-05-13 (641 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Razer Blade ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcCwd: /home/dima ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-12-generic root=UUID=8c1115d9-2cee-41a9-864f-d4e57d662706 ro rootflags=subvol=@ button.lid_init_state=open amdgpu.dpm=1 amdgpu.ppfeaturemask=0x Signal: 6 SourcePackage: nvidia-graphics-drivers StacktraceTop: System () () () () () at /lib/x86_64-linux-gnu/libpthread.so.0 Title: Xorg crashed with SIGABRT in System() UpgradeStatus: Upgraded to focal on 2020-02-09 (4 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd microk8s plugdev sambashare sudo dmi.bios.date: 02/22/2018 dmi.bios.vendor: Razer dmi.bios.version: 4.02 dmi.board.name: Razer dmi.board.vendor: Razer dmi.chassis.type: 9 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr4.02:bd02/22/2018:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr: dmi.product.family: 1A586755 dmi.product.name: Blade dmi.product.sku: RZ09-01953E72 dmi.product.version: 6.06 dmi.sys.vendor: Razer separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 19.3.3-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.3.3-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau:
[Desktop-packages] [Bug 1862895] Re: [focal][nvidia][gdm3] Xorg crashes when virt-viewer or remmina are used to connect to a windows10 VM
Hi Daniel, I submitted a new crash dump via `ubuntu-bug`: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1863142 I'm going to set the status for this one to "New" as I provided the info but maybe it should be duplicated to the new bug. ** Changed in: xorg-server (Ubuntu) Status: Incomplete => New ** Changed in: gdm3 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1862895 Title: [focal][nvidia][gdm3] Xorg crashes when virt-viewer or remmina are used to connect to a windows10 VM Status in gdm3 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: I observed the following on Eoan as well with nvidia drivers older than 440. 1) a windows 10 VM running in a qemu-kvm VM: pc-q35-3.1 machine type, QXL + SPICE: 2) When a host is booted with `prime-select intel` observing guest video output works fine with both virt-viewer (over SPICE) and remmina (over RDP); 3) With `prime-select nvidia` Remmina: Feb 12 10:15:22 blade gnome-shell[13670]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2a7 Feb 12 10:15:29 blade org.remmina.Remmina.desktop[14229]: [10:15:29:144] [14229:14825] [ERROR][com.winpr.timezone] - Unable to get current timezone rule Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Backtrace: Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x55685152bd2c] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f482176559f] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 2: /usr/lib/xorg/Xorg (RamDacHandleColormaps+0x317) [0x55685144a347] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 3: /usr/lib/xorg/Xorg (AddTraps+0x5ab5) [0x5568514a90d5] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 4: /usr/lib/xorg/Xorg (ResizeVisualArray+0x25d) [0x5568513be1dd] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 5: /usr/lib/xorg/Xorg (AllocARGBCursor+0x198) [0x5568513be478] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 6: /usr/lib/xorg/Xorg (AddTraps+0x2303) [0x5568514a1d23] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 7: /usr/lib/xorg/Xorg (SendErrorToClient+0x354) [0x5568513caf44] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 8: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5568513cefd4] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7f48215841e3] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 10: /usr/lib/xorg/Xorg (_start+0x2e) [0x5568513b8a3e] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Segmentation fault at address 0x0 Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: Fatal server error: Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Caught signal 11 (Segmentation fault). Server aborting Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: Please consult the The X.Org Foundation support Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: #011 at http://wiki.x.org Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: for help. Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Please also check the log file at "/home/dima/.local/share/xorg/Xorg.1.log" for additional information. Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:30 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Server terminated with error (1). Closing log file. Feb 12 10:15:30 blade remmina[14229]: org.remmina.Remmina: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Feb 12 10:15:30 blade gnome-calendar[14118]: gnome-calendar: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. virt-viewer: Feb 12 10:02:09 blade systemd[4463]: Started /usr/bin/virt-viewer -c qemu:///system. Feb 12 10:02:09 blade systemd[1]: Starting Daily apt download activities... Feb 12 10:02:10 blade systemd-resolved[1782]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Feb 12 10:02:10 blade systemd-resolved[1782]: message repeated 3 times: [ Server returned
[Desktop-packages] [Bug 1862895] [NEW] [focal][nvidia][gdm3] Xorg crashes when virt-viewer or remmina are used to connect to a windows10 VM
Public bug reported: I observed the following on Eoan as well with nvidia drivers older than 440. 1) a windows 10 VM running in a qemu-kvm VM: pc-q35-3.1 machine type, QXL + SPICE: 2) When a host is booted with `prime-select intel` observing guest video output works fine with both virt-viewer (over SPICE) and remmina (over RDP); 3) With `prime-select nvidia` Remmina: Feb 12 10:15:22 blade gnome-shell[13670]: Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2a7 Feb 12 10:15:29 blade org.remmina.Remmina.desktop[14229]: [10:15:29:144] [14229:14825] [ERROR][com.winpr.timezone] - Unable to get current timezone rule Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Backtrace: Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x55685152bd2c] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f482176559f] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 2: /usr/lib/xorg/Xorg (RamDacHandleColormaps+0x317) [0x55685144a347] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 3: /usr/lib/xorg/Xorg (AddTraps+0x5ab5) [0x5568514a90d5] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 4: /usr/lib/xorg/Xorg (ResizeVisualArray+0x25d) [0x5568513be1dd] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 5: /usr/lib/xorg/Xorg (AllocARGBCursor+0x198) [0x5568513be478] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 6: /usr/lib/xorg/Xorg (AddTraps+0x2303) [0x5568514a1d23] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 7: /usr/lib/xorg/Xorg (SendErrorToClient+0x354) [0x5568513caf44] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 8: /usr/lib/xorg/Xorg (InitFonts+0x3b4) [0x5568513cefd4] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7f48215841e3] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) 10: /usr/lib/xorg/Xorg (_start+0x2e) [0x5568513b8a3e] Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Segmentation fault at address 0x0 Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: Fatal server error: Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Caught signal 11 (Segmentation fault). Server aborting Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: Please consult the The X.Org Foundation support Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: #011 at http://wiki.x.org Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: for help. Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Please also check the log file at "/home/dima/.local/share/xorg/Xorg.1.log" for additional information. Feb 12 10:15:29 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Feb 12 10:15:30 blade /usr/lib/gdm3/gdm-x-session[13413]: (EE) Server terminated with error (1). Closing log file. Feb 12 10:15:30 blade remmina[14229]: org.remmina.Remmina: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Feb 12 10:15:30 blade gnome-calendar[14118]: gnome-calendar: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. virt-viewer: Feb 12 10:02:09 blade systemd[4463]: Started /usr/bin/virt-viewer -c qemu:///system. Feb 12 10:02:09 blade systemd[1]: Starting Daily apt download activities... Feb 12 10:02:10 blade systemd-resolved[1782]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Feb 12 10:02:10 blade systemd-resolved[1782]: message repeated 3 times: [ Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.] Feb 12 10:02:11 blade apt-get: Libgcrypt warning: missing initialization - please fix the application Feb 12 10:02:12 blade /unattended-upgrade: Not running on this development release before 2020-04-01 Feb 12 10:02:12 blade systemd[1]: apt-daily.service: Succeeded. Feb 12 10:02:12 blade systemd[1]: Started Daily apt download activities. Feb 12 10:02:12 blade evolution-alarm[7943]: evolution-alarm-notify: Fatal IO error 11 (Resource temporarily unavailable) on X server :1. Feb 12 10:02:12 blade pulseaudio[7212]: X connection to :1 broken (explicit kill or server shutdown). Feb 12 10:02:12 blade at-spi-bus-launcher[7657]: X connection to :1 broken (explicit kill or server shutdown). Feb 12 10:02:12 blade kdeconnectd[7947]:
[Desktop-packages] [Bug 1862531] Re: [focal] Wayland session is not available when a laptop has an Nvidia card an Intel card is in use
I see, thanks for the clarification. I will need to read through other cases as well. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1862531 Title: [focal] Wayland session is not available when a laptop has an Nvidia card an Intel card is in use Status in gdm3 package in Ubuntu: Incomplete Status in nvidia-prime package in Ubuntu: Invalid Bug description: A Wayland session present at /usr/share/wayland-sessions/ubuntu- wayland.desktop is not displayed at the login screen when a system has an iGPU (Intel) and dGPU (Nvidia) and Intel iGPU is used: prime-select query intel Only sessions at /usr/share/xsessions are present. ➜ ~ ls /usr/share/xsessions remmina-gnome.desktop ubuntu.desktop ➜ ~ ls /usr/share/wayland-sessions ubuntu-wayland.desktop The root cause is the existence of a udev rule in 61-gdm.rules that runs gdm-disable-wayland when an nvidia driver is loaded in combination with LP: #1848326 (see this comment specifically https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/comments/7). dpkg -S /lib/udev/rules.d/61-gdm.rules gdm3: /lib/udev/rules.d/61-gdm.rules grep nvidia /lib/udev/rules.d/61-gdm.rules # disable Wayland when using the proprietary nvidia driver DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland" When I comment it out and reboot, I get the right menu entry and am able to observe the right session type: ➜ ~ grep nvidia /lib/udev/rules.d/61-gdm.rules # disable Wayland when using the proprietary nvidia driver #DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland" ➜ ~ loginctl SESSION UID USER SEAT TTY 2 1000 dima seat0 tty2 1 sessions listed. ➜ ~ loginctl show-session 2 -p Type Type=wayland System info: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Codename: focal ➜ ~ dpkg -l | grep gdm3 ii gdm3 3.34.1-1ubuntu1 amd64GNOME Display Manager ➜ ~ dpkg -l | grep nvidia-prime ii nvidia-prime 0.8.13 all Tools to enable NVIDIA's Prime ➜ ~ dpkg -l | grep nvidia-driver ii nvidia-driver-440 440.59-0ubuntu1 amd64NVIDIA driver metapackage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862531/+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 1862531] Re: [focal] Wayland session is not available when a laptop has an Nvidia card an Intel card is in use
Hi Daniel, thank you for the quick response and prior work. I think the upstream check for the nvidia driver in 61-gdm.rules is too broad to be useful as the nvidia driver might be loaded for other reasons (e.g. CUDA usage or hw accelerated video encoding/decoding while nvidia-drm.ko is blacklisted) so I believe I can come up with an issue upstream. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1862531 Title: [focal] Wayland session is not available when a laptop has an Nvidia card an Intel card is in use Status in gdm3 package in Ubuntu: Incomplete Status in nvidia-prime package in Ubuntu: Invalid Bug description: A Wayland session present at /usr/share/wayland-sessions/ubuntu- wayland.desktop is not displayed at the login screen when a system has an iGPU (Intel) and dGPU (Nvidia) and Intel iGPU is used: prime-select query intel Only sessions at /usr/share/xsessions are present. ➜ ~ ls /usr/share/xsessions remmina-gnome.desktop ubuntu.desktop ➜ ~ ls /usr/share/wayland-sessions ubuntu-wayland.desktop The root cause is the existence of a udev rule in 61-gdm.rules that runs gdm-disable-wayland when an nvidia driver is loaded in combination with LP: #1848326 (see this comment specifically https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/comments/7). dpkg -S /lib/udev/rules.d/61-gdm.rules gdm3: /lib/udev/rules.d/61-gdm.rules grep nvidia /lib/udev/rules.d/61-gdm.rules # disable Wayland when using the proprietary nvidia driver DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland" When I comment it out and reboot, I get the right menu entry and am able to observe the right session type: ➜ ~ grep nvidia /lib/udev/rules.d/61-gdm.rules # disable Wayland when using the proprietary nvidia driver #DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland" ➜ ~ loginctl SESSION UID USER SEAT TTY 2 1000 dima seat0 tty2 1 sessions listed. ➜ ~ loginctl show-session 2 -p Type Type=wayland System info: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Codename: focal ➜ ~ dpkg -l | grep gdm3 ii gdm3 3.34.1-1ubuntu1 amd64GNOME Display Manager ➜ ~ dpkg -l | grep nvidia-prime ii nvidia-prime 0.8.13 all Tools to enable NVIDIA's Prime ➜ ~ dpkg -l | grep nvidia-driver ii nvidia-driver-440 440.59-0ubuntu1 amd64NVIDIA driver metapackage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862531/+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 1848326] Re: [cosmic+] error booting with prime-select intel: prime-select does not update initramfs to blacklist nvidia modules
** Tags added: champagne -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1848326 Title: [cosmic+] error booting with prime-select intel: prime-select does not update initramfs to blacklist nvidia modules Status in nvidia-prime package in Ubuntu: Confirmed Bug description: when I try to boot with the iGPU selected, DE won't boot, with nvidia selected, everithing is fine. I tried uninstalling nvidia driver and it allowed my to access without any problems and intel is working fine ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-prime 0.8.13 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 16 12:41:26 2019 Dependencies: InstallationDate: Installed on 2019-09-25 (20 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190925) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/+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 1862531] [NEW] [focal] Wayland session is not available when a laptop has an Nvidia card an Intel card is in use
Public bug reported: A Wayland session present at /usr/share/wayland-sessions/ubuntu- wayland.desktop is not displayed at the login screen when a system has an iGPU (Intel) and dGPU (Nvidia) and Intel iGPU is used: prime-select query intel Only sessions at /usr/share/xsessions are present. ➜ ~ ls /usr/share/xsessions remmina-gnome.desktop ubuntu.desktop ➜ ~ ls /usr/share/wayland-sessions ubuntu-wayland.desktop The root cause is the existence of a udev rule in 61-gdm.rules that runs gdm-disable-wayland when an nvidia driver is loaded in combination with LP: #1848326 (see this comment specifically https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/comments/7). dpkg -S /lib/udev/rules.d/61-gdm.rules gdm3: /lib/udev/rules.d/61-gdm.rules grep nvidia /lib/udev/rules.d/61-gdm.rules # disable Wayland when using the proprietary nvidia driver DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland" When I comment it out and reboot, I get the right menu entry and am able to observe the right session type: ➜ ~ grep nvidia /lib/udev/rules.d/61-gdm.rules # disable Wayland when using the proprietary nvidia driver #DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland" ➜ ~ loginctl SESSION UID USER SEAT TTY 2 1000 dima seat0 tty2 1 sessions listed. ➜ ~ loginctl show-session 2 -p Type Type=wayland System info: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal ➜ ~ dpkg -l | grep gdm3 ii gdm3 3.34.1-1ubuntu1 amd64GNOME Display Manager ➜ ~ dpkg -l | grep nvidia-prime ii nvidia-prime 0.8.13 all Tools to enable NVIDIA's Prime ➜ ~ dpkg -l | grep nvidia-driver ii nvidia-driver-440 440.59-0ubuntu1 amd64NVIDIA driver metapackage ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Tags: champagne ** Also affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Wayland session is not available when a laptop has an Nvidia card an Intel card is in use + [focal] Wayland session is not available when a laptop has an Nvidia card an Intel card is in use -- 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/1862531 Title: [focal] Wayland session is not available when a laptop has an Nvidia card an Intel card is in use Status in gdm3 package in Ubuntu: New Status in nvidia-prime package in Ubuntu: New Bug description: A Wayland session present at /usr/share/wayland-sessions/ubuntu- wayland.desktop is not displayed at the login screen when a system has an iGPU (Intel) and dGPU (Nvidia) and Intel iGPU is used: prime-select query intel Only sessions at /usr/share/xsessions are present. ➜ ~ ls /usr/share/xsessions remmina-gnome.desktop ubuntu.desktop ➜ ~ ls /usr/share/wayland-sessions ubuntu-wayland.desktop The root cause is the existence of a udev rule in 61-gdm.rules that runs gdm-disable-wayland when an nvidia driver is loaded in combination with LP: #1848326 (see this comment specifically https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/comments/7). dpkg -S /lib/udev/rules.d/61-gdm.rules gdm3: /lib/udev/rules.d/61-gdm.rules grep nvidia /lib/udev/rules.d/61-gdm.rules # disable Wayland when using the proprietary nvidia driver DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland" When I comment it out and reboot, I get the right menu entry and am able to observe the right session type: ➜ ~ grep nvidia /lib/udev/rules.d/61-gdm.rules # disable Wayland when using the proprietary nvidia driver #DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland" ➜ ~ loginctl SESSION UID USER SEAT TTY 2 1000 dima seat0 tty2 1 sessions listed. ➜ ~ loginctl show-session 2 -p Type Type=wayland System info: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Codename: focal ➜ ~ dpkg -l | grep gdm3 ii gdm3 3.34.1-1ubuntu1 amd64GNOME Display Manager ➜ ~ dpkg -l | grep nvidia-prime ii nvidia-prime 0.8.13 all Tools to enable NVIDIA's Prime ➜ ~ dpkg -l | grep nvidia-driver ii nvidia-driver-440
[Desktop-packages] [Bug 1848326] Re: [cosmic+] error booting with prime-select intel: prime-select does not update initramfs to blacklist nvidia modules
Based on a discussion with ~albertomilone, powering down the NVIDIA GPU
while keeping the modules loaded is the way to go long-term as opposed
to blacklisting the modules.
The power management feature is described here (requires Turing GPUs and above):
http://us.download.nvidia.com/XFree86/Linux-x86_64/440.44/README/dynamicpowermanagement.html
My GPU is pre-Turing (Pascal, 1060m), however, powering off is not where
the problem is.
Running `prime-select intel` creates /lib/udev/rules.d/80-pm-
nvidia.rules which contains the following line to unbind an NVIDIA GPU
device from its driver:
https://github.com/tseliot/nvidia-prime/blob/cf757cc9585dfc032930379fc81effb3a3d59606/prime-select#L164-L165
ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x10de",
ATTR{class}=="0x03", ATTR{remove}="1"
If I comment it out, I can boot just fine with my iGPU after running
`prime-select intel`. The resulting 80-pm-nvidia.rules file looks like
this: https://paste.ubuntu.com/p/HX6t9y8BPg/
Just commenting out the power management lines while leaving the
unbinding in-place results in the same issue (80-pm-nvidia.rules:
https://paste.ubuntu.com/p/mTdXbZZk8H/).
The unbinding operation hangs which results in something like this even
before X11 or gdm3 are attempted to be started:
[ 15.683190] nvidia-uvm: Loaded the UVM driver, major device number 511.
[ 15.824882] NVRM: Attempting to remove minor device 0 with non-zero usage
count!
[ 15.824903] [ cut here ]
[ 15.825082] WARNING: CPU: 0 PID: 759 at
/var/lib/dkms/nvidia/440.59/build/nvidia/nv-pci.c:577 nv_pci_remove+0x338/0x360
[nvidia]
# ...
[ 15.825330] ---[ end trace 353e142c2126a8a0 ]---
# ...
[ 242.649248] INFO: task nvidia-persiste:1876 blocked for more than 120
seconds.
[ 242.649931] Tainted: PW O 5.4.0-12-generic #15-Ubuntu
[ 242.650618] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[ 242.651319] nvidia-persiste D0 1876 1 0x0004
Eventually it fails with a timeout:
systemd[1]: nvidia-persistenced.service: start operation timed out. Terminating.
systemd[1]: nvidia-persistenced.service: Failed with result 'timeout'.
systemd[1]: Failed to start NVIDIA Persistence Daemon.
Masking nvidia-persistenced via `sudo systemctl mask nvidia-
persistenced` and rebooting shows that systemd-udevd and rmmod hang as
well:
Feb 9 17:18:43 blade systemd-udevd[717]: :01:00.0: Worker [756] processing
SEQNUM=4430 is taking a long time
Feb 9 17:18:43 blade systemd-udevd[717]: :01:00.1: Worker [746] processing
SEQNUM=4440 is taking a long time
Feb 9 17:20:43 blade systemd-udevd[717]: :01:00.1: Worker [746] processing
SEQNUM=4440 killed
Feb 9 17:20:43 blade systemd-udevd[717]: :01:00.0: Worker [756] processing
SEQNUM=4430 killed
Feb 9 17:21:31 blade kernel: [ 242.818665] INFO: task systemd-udevd:746
blocked for more than 120 seconds.
Feb 9 17:21:31 blade kernel: [ 242.819381] Tainted: PW O
5.4.0-12-generic #15-Ubuntu
Feb 9 17:21:31 blade kernel: [ 242.820075] "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 9 17:21:31 blade kernel: [ 242.820797] systemd-udevd D0 746
717 0x0324
# ...
Feb 9 17:21:31 blade kernel: [ 242.823033] rmmod D0 1939
1937 0x4000
Feb 9 17:21:31 blade kernel: [ 242.823034] Call Trace:
# ...
Feb 9 17:21:31 blade kernel: [ 242.823783] nvkms_close_gpu+0x50/0x80
[nvidia_modeset]
Feb 9 17:21:31 blade kernel: [ 242.823793] _nv002598kms+0x14d/0x170
[nvidia_modeset]
# ...
Feb 9 17:21:31 blade kernel: [ 242.823893] ? nv_linux_drm_exit+0x9/0x768
[nvidia_drm]
Feb 9 17:21:31 blade kernel: [ 242.823897] ?
__x64_sys_delete_module+0x147/0x290
# ...
** Attachment added: "syslog-nvidia-persistenced-hang.txt"
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/+attachment/5326678/+files/syslog-nvidia-persistenced-hang.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1848326
Title:
[cosmic+] error booting with prime-select intel: prime-select does not
update initramfs to blacklist nvidia modules
Status in nvidia-prime package in Ubuntu:
Confirmed
Bug description:
when I try to boot with the iGPU selected, DE won't boot, with nvidia
selected, everithing is fine.
I tried uninstalling nvidia driver and it allowed my to access without any
problems and intel is working fine
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: nvidia-prime 0.8.13
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Oct 16 12:41:26 2019
Dependencies:
InstallationDate: Installed on 2019-09-25 (20 days ago)
[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.
** Tags added: champagne -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support. Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Triaged Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838151/+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 1853420] Re: [19.10][snap][beta] Switching an input method via ibus does not affect input in chromium
Tried rev 951 now and I cannot reproduce the same behavior anymore. ➜ ~ snap refresh chromium --beta Download snap "chromium" (951) from channel "beta" 77% 251kBDownloadchromium (beta) 79.0.3945.45 from Canonical✓ refreshed I'll set it to incomplete for now and see if I encounter it again (if not, I'll just let it expire). ** Changed in: chromium-browser (Ubuntu) Status: New => 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/1853420 Title: [19.10][snap][beta] Switching an input method via ibus does not affect input in chromium Status in chromium-browser package in Ubuntu: Incomplete Bug description: Unable to switch an input method from English in chromium by changing it via ibus. ➜ ~ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 19.10 Release: 19.10 Codename: eoan ➜ ~ snap list chromium Name Version Rev Tracking Publisher Notes chromium 79.0.3945.29 939 beta canonical✓ - # when switching the input method switching languages journalctl -f ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). ноя 21 10:37:15 blade gnome-shell[7048]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed # when chromium is launched: journalctl -f ноя 21 10:37:41 blade chrome[13667]: Failed to load module "canberra-gtk-module" ноя 21 10:37:41 blade chrome[13667]: Failed to load module "canberra-gtk-module" ноя 21 10:37:41 blade audit[2323]: USER_AVC pid=2323 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=13667 label="snap.chromium.chromium" peer_pid=2354 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?' ноя 21 10:37:41 blade kernel: audit: type=1107 audit(1574321861.798:169): pid=2323 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=13667 label="snap.chromium.chromium" peer_pid=2354 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?' ноя 21 10:37:41 blade chromium_chromium.desktop[7048]: [13821:13821:1121/103741.914544:ERROR:sandbox_linux.cc(372)] InitializeSandbox() called with multiple threads in process gpu-process. ноя 21 10:37:41 blade gnome-keyring-daemon[6123]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered ноя 21 10:37:42 blade audit[13667]: AVC apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/sys_vendor" pid=13667 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 ноя 21 10:37:42 blade audit[13667]: AVC apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/product_name" pid=13667 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 ноя 21 10:37:42 blade kernel: audit: type=1400 audit(1574321862.026:170): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/sys_vendor" pid=13667 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 ноя 21 10:37:42 blade kernel:
[Desktop-packages] [Bug 1853420] Re: [19.10][snap][beta] Switching an input method via ibus does not affect input in chromium
English (US) to Russian: en -> ru. ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1853420 Title: [19.10][snap][beta] Switching an input method via ibus does not affect input in chromium Status in chromium-browser package in Ubuntu: New Bug description: Unable to switch an input method from English in chromium by changing it via ibus. ➜ ~ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 19.10 Release: 19.10 Codename: eoan ➜ ~ snap list chromium Name Version Rev Tracking Publisher Notes chromium 79.0.3945.29 939 beta canonical✓ - # when switching the input method switching languages journalctl -f ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). ноя 21 10:37:15 blade gnome-shell[7048]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed # when chromium is launched: journalctl -f ноя 21 10:37:41 blade chrome[13667]: Failed to load module "canberra-gtk-module" ноя 21 10:37:41 blade chrome[13667]: Failed to load module "canberra-gtk-module" ноя 21 10:37:41 blade audit[2323]: USER_AVC pid=2323 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=13667 label="snap.chromium.chromium" peer_pid=2354 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?' ноя 21 10:37:41 blade kernel: audit: type=1107 audit(1574321861.798:169): pid=2323 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=13667 label="snap.chromium.chromium" peer_pid=2354 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?' ноя 21 10:37:41 blade chromium_chromium.desktop[7048]: [13821:13821:1121/103741.914544:ERROR:sandbox_linux.cc(372)] InitializeSandbox() called with multiple threads in process gpu-process. ноя 21 10:37:41 blade gnome-keyring-daemon[6123]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered ноя 21 10:37:42 blade audit[13667]: AVC apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/sys_vendor" pid=13667 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 ноя 21 10:37:42 blade audit[13667]: AVC apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/product_name" pid=13667 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 ноя 21 10:37:42 blade kernel: audit: type=1400 audit(1574321862.026:170): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/sys_vendor" pid=13667 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 ноя 21 10:37:42 blade kernel: audit: type=1400 audit(1574321862.026:171): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/product_name" pid=13667 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 ноя 21 10:37:42 blade gnome-keyring-daemon[6123]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered
[Desktop-packages] [Bug 1848326] Re: error booting with prime-select intel
Managed to reproduce it: 1) switched to nvidia; 2) worked for a while with it for a while with 5.3.0-19-generic; 3) got a kernel update to 5.3.0-23-generic; 4) switched to intel; 5) reproduced the problem. What I found is: 1) /lib/modprobe.d/blacklist-nvidia.conf gets created if you switch to "intel"; 2) blacklist-nvidia.conf wasn't in initramfs for the new kernel: lsinitramfs initrd.img-5.3.0-19-generic | grep blacklist-nvidia.conf ; echo $? usr/lib/modprobe.d/blacklist-nvidia.conf 0 lsinitramfs initrd.img-5.3.0-23-generic | grep blacklist-nvidia.conf ; echo $? 1 3) running `updateinitramfs -u` fixes it. >From what I can see: * updateinitramfs works correctly and the blacklist file gets created correctly as well so long as "intel" is selected; * If a kernel is upgraded while the profile is set to "nvidia" though, /lib/modprobe.d/blacklist-nvidia.conf is (correctly) not there so any initramfs generation or updates do not include it; * So when `prime-select intel` is done on a system that got upgraded with `prime-select query -> nvidia`, there is nothing to update initramfs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1848326 Title: [cosmic+] error booting with prime-select intel: prime-select does not update initramfs to blacklist nvidia modules Status in nvidia-prime package in Ubuntu: Confirmed Bug description: when I try to boot with the iGPU selected, DE won't boot, with nvidia selected, everithing is fine. I tried uninstalling nvidia driver and it allowed my to access without any problems and intel is working fine ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-prime 0.8.13 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 16 12:41:26 2019 Dependencies: InstallationDate: Installed on 2019-09-25 (20 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190925) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/+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 1848326] Re: error booting with prime-select intel
updateinitramfs used to be run previously, however, this was removed at some point (introduced into the distro in Cosmic/18.10): https://github.com/tseliot/nvidia- prime/commit/7595f47b84f713dc969440e31d0e53708fddd71f https://git.launchpad.net/~usd-import-team/ubuntu/+source/nvidia- prime/commit/?id=1180051b7a3f59cafc2c56a02fe9b0a8b8991273 I think this functionality needs to be brought back to fix this bug. ** Summary changed: - error booting with prime-select intel + [cosmic+] error booting with prime-select intel: prime-select does not update initramfs to blacklist nvidia modules -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1848326 Title: [cosmic+] error booting with prime-select intel: prime-select does not update initramfs to blacklist nvidia modules Status in nvidia-prime package in Ubuntu: Confirmed Bug description: when I try to boot with the iGPU selected, DE won't boot, with nvidia selected, everithing is fine. I tried uninstalling nvidia driver and it allowed my to access without any problems and intel is working fine ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-prime 0.8.13 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 16 12:41:26 2019 Dependencies: InstallationDate: Installed on 2019-09-25 (20 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190925) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/+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 1853420] [NEW] [19.10][snap][beta] Switching an input method via ibus does not affect input in chromium
Public bug reported: Unable to switch an input method from English in chromium by changing it via ibus. ➜ ~ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 19.10 Release:19.10 Codename: eoan ➜ ~ snap list chromium Name Version Rev Tracking Publisher Notes chromium 79.0.3945.29 939 beta canonical✓ - # when switching the input method switching languages journalctl -f ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). ноя 21 10:37:15 blade gnome-shell[7048]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). ноя 21 10:37:15 blade gnome-shell[7048]: _clutter_stage_queue_event: assertion 'CLUTTER_IS_STAGE (stage)' failed # when chromium is launched: journalctl -f ноя 21 10:37:41 blade chrome[13667]: Failed to load module "canberra-gtk-module" ноя 21 10:37:41 blade chrome[13667]: Failed to load module "canberra-gtk-module" ноя 21 10:37:41 blade audit[2323]: USER_AVC pid=2323 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=13667 label="snap.chromium.chromium" peer_pid=2354 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?' ноя 21 10:37:41 blade kernel: audit: type=1107 audit(1574321861.798:169): pid=2323 uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=13667 label="snap.chromium.chromium" peer_pid=2354 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=103 hostname=? addr=? terminal=?' ноя 21 10:37:41 blade chromium_chromium.desktop[7048]: [13821:13821:1121/103741.914544:ERROR:sandbox_linux.cc(372)] InitializeSandbox() called with multiple threads in process gpu-process. ноя 21 10:37:41 blade gnome-keyring-daemon[6123]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered ноя 21 10:37:42 blade audit[13667]: AVC apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/sys_vendor" pid=13667 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 ноя 21 10:37:42 blade audit[13667]: AVC apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/product_name" pid=13667 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 ноя 21 10:37:42 blade kernel: audit: type=1400 audit(1574321862.026:170): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/sys_vendor" pid=13667 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 ноя 21 10:37:42 blade kernel: audit: type=1400 audit(1574321862.026:171): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/sys/devices/virtual/dmi/id/product_name" pid=13667 comm="ThreadPoolForeg" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 ноя 21 10:37:42 blade gnome-keyring-daemon[6123]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered ноя 21 10:37:42 blade audit[13667]: AVC apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/var/lib/snapd/desktop/icons/" pid=13667 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 ноя 21 10:37:42 blade kernel: audit: type=1400 audit(1574321862.206:172): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/var/lib/snapd/desktop/icons/" pid=13667 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 ноя 21 10:37:42 blade
[Desktop-packages] [Bug 1848326] Re: error booting with prime-select intel
If anybody still has a reproducer, it would be useful to set a trace
point like this:
sudo vim /usr/bin/prime-select
# ...
import pdb
pdb.set_trace()
if profile == 'nvidia':
# Always allow enabling nvidia
# (No need to check if nvidia is available)
self._enable_nvidia()
elif profile == "on-demand":
self._disable_nvidia(keep_nvidia_modules=True)
else:
# Make sure that the installed packages support PRIME
#if not self._supports_prime():
#sys.stderr.write('Error: the installed packages do not support
PRIME\n')
#return False
self._disable_nvidia()
# ...
and see if _disable_nvidia is entered when `prime-select intel` is
invoked while `prime-select query` shows "nvidia" or "on-demand".
Before I removed the driver and the nvidia-prime package, I could switch
the profile back and forth using `prime-select intel` and `prime-select
nvidia` without any positive effect so it would be useful to find out
why.
The code only depends on the target profile specified via command line
and the current profile (read from /etc/prime-discrete) so I don't have
any guesses yet:
https://github.com/tseliot/nvidia-
prime/blob/cf757cc9585dfc032930379fc81effb3a3d59606/prime-
select#L114-L143
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1848326
Title:
error booting with prime-select intel
Status in nvidia-prime package in Ubuntu:
Confirmed
Bug description:
when I try to boot with the iGPU selected, DE won't boot, with nvidia
selected, everithing is fine.
I tried uninstalling nvidia driver and it allowed my to access without any
problems and intel is working fine
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: nvidia-prime 0.8.13
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Oct 16 12:41:26 2019
Dependencies:
InstallationDate: Installed on 2019-09-25 (20 days ago)
InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190925)
PackageArchitecture: all
SourcePackage: nvidia-prime
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/+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 1848326] Re: error booting with prime-select intel
I had the same problem (the system got upgraded from 19.04 to 19.10, nvidia-430 driver). I noticed that nvidia drivers were loaded in the rescue mode - so they were likely not blacklisted properly. When I did not enter the rescue mode I had the following message displayed: "A start job is running for udev Wait for Complete Device Initialization (1min 3s/ 3min) /var/lib/gdm3/.local/share/xorg/Xorg.0.log contained the following (see the full file attached): [47.771] (==) ModulePath set to "/usr/lib/xorg/modules" [47.771] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. # ... [47.778]loading driver: nvidia [47.882] (==) Matched nvidia as autoconfigured driver 0 [47.882] (==) Matched nouveau as autoconfigured driver 1 [47.882] (==) Matched modesetting as autoconfigured driver 2 [47.882] (==) Matched fbdev as autoconfigured driver 3 [47.882] (==) Matched vesa as autoconfigured driver 4 [47.882] (==) Assigned the driver to the xf86ConfigLayout [47.882] (II) LoadModule: "nvidia" # ... [48.142] (II) Unloading vesa [48.142] (EE) modeset(G0): drmSetMaster failed: Permission denied [48.142] (EE) Fatal server error: [48.142] (EE) AddScreen/ScreenInit failed for gpu driver 0 -1 I removed the nvidia driver and got the system to the working state again and then installed it from scratch. Then I set up a trace point in prime-select here: https://github.com/tseliot/nvidia-prime/blob/cf757cc9585dfc032930379fc81effb3a3d59606/prime-select#L126-L138 Tracing showed that /lib/modprobe.d/blacklist-nvidia.conf and /lib/udev/rules.d/80-pm-nvidia.rules were created correctly this time: https://paste.ubuntu.com/p/2Dp5jgFQty/ cat /lib/modprobe.d/blacklist-nvidia.conf # Do not modify # This file was generated by nvidia-prime blacklist nvidia blacklist nvidia-drm blacklist nvidia-modeset alias nvidia off alias nvidia-drm off alias nvidia-modeset off I could then successfully reboot without hacking. ** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/+attachment/5302704/+files/Xorg.0.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1848326 Title: error booting with prime-select intel Status in nvidia-prime package in Ubuntu: Confirmed Bug description: when I try to boot with the iGPU selected, DE won't boot, with nvidia selected, everithing is fine. I tried uninstalling nvidia driver and it allowed my to access without any problems and intel is working fine ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-prime 0.8.13 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Wed Oct 16 12:41:26 2019 Dependencies: InstallationDate: Installed on 2019-09-25 (20 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190925) PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1848326/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
On 19.04 I can see the following (correct) behavior. With VPN (turned on via NetworkManager): # note: no "global" DNS servers have been configured by hand through systemd-resolved conf using "DNS=" directive systemd-resolved --status # ... Link 15 (tun0) Current Scopes: DNS DefaultRoute setting: yes LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Current DNS Server: DNS Servers: DNS Domain: ~. Link 2 (wlp59s0) Current Scopes: DNS DefaultRoute setting: yes LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Current DNS Server: DNS Servers: DNS Domain: deadbeefcafe Without VPN: systemd-resolved --status # ... Link 2 (wlp59s0) Current Scopes: DNS DefaultRoute setting: yes LLMNR setting: yes MulticastDNS setting: no DNSOverTLS setting: no DNSSEC setting: no DNSSEC supported: no Current DNS Server: DNS Servers: DNS Domain: ~. deadbeefcafe "~." configuration goes to the tun0 interface once VPN is enabled and is removed from the physical interface. In this example it means that DHCP-advertised local DNS servers will be used for deadbeefcafe domain only and everything else will go through the DNS servers of a VPN service. Clarifications on how "~." affects DNS request routing: https://github.com/systemd/systemd/blame/v240/src/resolve/resolved-dns-scope.c#L1411-L1418 * "~." really trumps everything and clearly indicates that this interface shall receive all * traffic it can get. */ http://manpages.ubuntu.com/manpages/disco/man5/resolved.conf.5.html#options https://www.freedesktop.org/software/systemd/man/resolved.conf.html#Domains= Packages: ii network-manager 1.16.0-0ubuntu2 amd64network management framework (daemon and userspace tools) ii network-manager-config-connectivity-ubuntu1.16.0-0ubuntu2 all NetworkManager configuration to enable connectivity checking ii network-manager-gnome 1.8.20-1ubuntu1 amd64network management framework (GNOME frontend) ii network-manager-openvpn 1.8.10-1 amd64network management framework (OpenVPN plugin core) ii network-manager-openvpn-gnome 1.8.10-1 amd64network management framework (OpenVPN plugin GNOME GUI) ii netplan.io0.97-0ubuntu1~19.04.1 amd64YAML network configuration abstraction for various backends ii systemd 240-6ubuntu5.3 amd64system and service manager I have also captured DNS packets on all interfaces via Wireshark and confirmed that DNS requests go to the correct DNS servers on 19.04. -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Won't Fix Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled)
[Desktop-packages] [Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69
Had this with nvidia graphics drivers after installing and then removing proprietary drivers downloaded from nvidia website. I could not log in at all at first boot. If you see nvidia modules loaded, make sure that you select an xorg session on the login screen (not wayland) if you this control presented to you. lsmod| grep nvidia nvidia_uvm794624 0 nvidia_drm 40960 13 nvidia_modeset 1040384 1 nvidia_drm nvidia 17285120 653 nvidia_uvm,nvidia_modeset ipmi_msghandler 102400 2 ipmi_devintf,nvidia drm_kms_helper172032 2 nvidia_drm,i915 drm 458752 13 drm_kms_helper,nvidia_drm,i915 Alternatively, just set WaylandEnable to false (and restart gdm). cat /etc/gdm3/custom.conf # ... [daemon] # Uncoment the line below to force the login screen to use Xorg WaylandEnable=false # ... I also suspect that /etc/X11/xorg.conf generated by nvidia-xconfig (which I ran during driver installation from the website) was causing issues. Steps I performed from a VT session: 1) sudo apt purge 'nvidia*' 2) reboot 3) sudo rm /etc/X11/xorg.conf 4) sudo apt install nvidia-driver- nvidia-dkms- nvidia-settings nvidia-prime 5) reboot I also have 11-nvidia-prime.conf file at /usr/share/X11/xorg.conf.d which is generated by ubuntu-drivers-common: cat /usr/share/X11/xorg.conf.d/11-nvidia-prime.conf # DO NOT EDIT. AUTOMATICALLY GENERATED BY gpu-manager Section "OutputClass" Identifier "Nvidia Prime" MatchDriver "nvidia-drm" Driver "nvidia" Option "AllowEmptyInitialConfiguration" Option "IgnoreDisplayDevices" "CRT" Option "PrimaryGPU" "Yes" ModulePath "/x86_64-linux-gnu/nvidia/xorg" EndSection dpkg -l | grep ubuntu-drivers-common ii ubuntu-drivers-common 1:0.5.2.2 https://github.com/tseliot/ubuntu-drivers- common/blob/bionic/share/hybrid/gpu-manager.c#L1359-L1375 ** Attachment added: "nvidia-x-server-settings-graphics-ppa-415-hwe-4.18-bionic.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1785964/+attachment/5239177/+files/nvidia-x-server-settings-graphics-ppa-415-hwe-4.18-bionic.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1785964 Title: Unable to unlock the desktop session: systemd-logind: got pause for 13:69 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Confirmed Bug description: When this issue happens, you won't be able to unlock your desktop session (VT works fine). This happened twice today for me, one is after a suspend, one is just a screen lock. Not sure what is the trigger yet. Syndrome: On the login screen after typing the correct password, you will see a small circle keep spinning and that's it. I need to restart my computer to get it back to normal. In the syslog this error message looks fishy: Aug 8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' failed This is part of the syslog fetching from a VT after a GUI unlock attempt (session 24 is the desktop login attempt): Aug 8 10:44:42 Leggiero systemd[1]: Started Session 24 of user sam. Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 226:0 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) AIGLX: Resuming AIGLX clients after VT switch Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): EDID vendor "AUO", prod id 4204 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Printing DDC gathered Modelines: Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Modeline "1366x768"x0.0 76.20 1366 1404 1426 1590 768 771 777 798 +hsync -vsync (47.9 kHz eP) Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Modeline "1366x768"x0.0 76.20 1366 1404 1426 1988 768 771 777 798 +hsync -vsync (38.3 kHz e) Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:78 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - Dell WMI hotkeys: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - Dell WMI hotkeys: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:66 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2 - Sleep Button: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2 - Sleep Button: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:79 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - Integrated_Webcam_HD: Integrate: is tagged by udev as: Keyboard
[Desktop-packages] [Bug 1785964] Re: Unable to unlock the desktop session: systemd-logind: got pause for 13:69
nvidia-xconfig -generated xorg.conf looked like this https://paste.ubuntu.com/p/4hRVzHmbJV/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1785964 Title: Unable to unlock the desktop session: systemd-logind: got pause for 13:69 Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Confirmed Bug description: When this issue happens, you won't be able to unlock your desktop session (VT works fine). This happened twice today for me, one is after a suspend, one is just a screen lock. Not sure what is the trigger yet. Syndrome: On the login screen after typing the correct password, you will see a small circle keep spinning and that's it. I need to restart my computer to get it back to normal. In the syslog this error message looks fishy: Aug 8 10:44:57 Leggiero gnome-shell[2118]: g_array_unref: assertion 'array' failed This is part of the syslog fetching from a VT after a GUI unlock attempt (session 24 is the desktop login attempt): Aug 8 10:44:42 Leggiero systemd[1]: Started Session 24 of user sam. Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 226:0 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) AIGLX: Resuming AIGLX clients after VT switch Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): EDID vendor "AUO", prod id 4204 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Printing DDC gathered Modelines: Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Modeline "1366x768"x0.0 76.20 1366 1404 1426 1590 768 771 777 798 +hsync -vsync (47.9 kHz eP) Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) modeset(0): Modeline "1366x768"x0.0 76.20 1366 1404 1426 1988 768 771 777 798 +hsync -vsync (38.3 kHz e) Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:78 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - Dell WMI hotkeys: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event14 - Dell WMI hotkeys: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:66 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2 - Sleep Button: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event2 - Sleep Button: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:79 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - Integrated_Webcam_HD: Integrate: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event15 - Integrated_Webcam_HD: Integrate: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:68 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4 - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event4 - AT Translated Set 2 keyboard: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:67 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3 - Power Button: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event3 - Power Button: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:71 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7 - AlpsPS/2 ALPS GlidePoint: is tagged by udev as: Touchpad Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event7 - AlpsPS/2 ALPS GlidePoint: device is a touchpad Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:72 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8 - DELL Wireless hotkeys: is tagged by udev as: Keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event8 - DELL Wireless hotkeys: device is a keyboard Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) libinput: PixArt Microsoft USB Optical Mouse: SetProperty on 286 called but device is disabled. Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: This driver cannot change properties on a disabled device Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) systemd-logind: got resume for 13:65 Aug 8 10:44:55 Leggiero /usr/lib/gdm3/gdm-x-session[1977]: (II) event1 - Power Button: is
[Desktop-packages] [Bug 1790624] [NEW] rhythmbox periodically hangs during playback via SFTP
Public bug reported: Scenario: a server is available via LAN from which content is played back via SFTP (ssh, gvfs). After some time (could be an hour) rhythmbox hangs and a window comes up suggesting that you can either wait or terminate rhythmbox. There are no network interruptions that would cause something like this (the issue comes up quite frequently) and plus I do not see any of the threads to be in the D state. strace shows that there is a futex wait for some condition. ps: redacted 20291 3.3 1.0 1989228 173472 tty2 Sl+ 12:14 4:49 rhythmbox ➜ ~ ps -T -o pid,tid,class,rtprio,ni,pri,psr,pcpu,stat,wchan:14,comm -p 20291 PID TID CLS RTPRIO NI PRI PSR %CPU STAT WCHAN COMMAND 20291 20291 TS - 0 19 6 0.9 Sl+ futex_wait_que rhythmbox 20291 20294 TS - 0 19 6 0.0 Sl+ poll_schedule_ gmain 20291 20295 TS - 0 19 7 0.0 Sl+ poll_schedule_ gdbus 20291 20296 TS - 0 19 7 0.0 Sl+ poll_schedule_ dconf worker 20291 20298 TS - 0 19 2 0.2 Sl+ futex_wait_que typefind:sink 20291 20306 TS - 0 19 5 0.0 Sl+ futex_wait_que rhythmdb-thread 20291 20344 TS - 0 19 4 0.1 Sl+ futex_wait_que id3demux167:sin 20291 20346 TS - 0 19 7 0.1 Sl+ poll_schedule_ mpegaudioparse1 20291 20392 TS - 0 19 4 0.2 Sl+ futex_wait_que mpegaudioparse1 20291 20393 TS - 0 19 4 0.0 Sl+ futex_wait_que id3demux168:sin 20291 12125 TS - 0 19 4 0.0 Sl+ futex_wait_que typefind:sink sudo strace -f -p 20291 strace: Process 20291 attached with 11 threads [pid 12125] futex(0x55eacb8dc778, FUTEX_WAIT_PRIVATE, 1, NULL [pid 20393] futex(0x7fe7201320b8, FUTEX_WAIT_PRIVATE, 1, NULL [pid 20392] futex(0x7fe6f4013538, FUTEX_WAIT_PRIVATE, 1, NULL [pid 20346] restart_syscall(<... resuming interrupted poll ...> [pid 20344] futex(0x7fe6f0004898, FUTEX_WAIT_PRIVATE, 1, NULL [pid 20306] futex(0x55eacab00580, FUTEX_WAIT_PRIVATE, 2, NULL [pid 20298] futex(0x55eacb8dcf58, FUTEX_WAIT_PRIVATE, 1, NULL [pid 20296] restart_syscall(<... resuming interrupted poll ...> [pid 20295] restart_syscall(<... resuming interrupted poll ...> [pid 20294] restart_syscall(<... resuming interrupted poll ...> [pid 20291] futex(0x55eacf0ea9a0, FUTEX_WAIT_PRIVATE, 2, NULL # after killing via the GUI button [pid 20344] <... futex resumed> ) = ? ERESTARTSYS (To be restarted if SA_RESTART is set) [pid 12125] <... futex resumed>)= ? [pid 20393] <... futex resumed>)= ? [pid 20392] <... futex resumed>)= ? [pid 12125] +++ killed by SIGKILL +++ [pid 20393] +++ killed by SIGKILL +++ [pid 20392] +++ killed by SIGKILL +++ [pid 20346] <... restart_syscall resumed>) = ? [pid 20344] +++ killed by SIGKILL +++ [pid 20346] +++ killed by SIGKILL +++ [pid 20306] <... futex resumed>)= ? [pid 20296] <... restart_syscall resumed>) = ? [pid 20295] <... restart_syscall resumed>) = ? [pid 20306] +++ killed by SIGKILL +++ [pid 20296] +++ killed by SIGKILL +++ [pid 20298] <... futex resumed>)= ? [pid 20295] +++ killed by SIGKILL +++ [pid 20298] +++ killed by SIGKILL +++ [pid 20294] <... restart_syscall resumed>) = ? [pid 20291] <... futex resumed>)= ? [pid 20294] +++ killed by SIGKILL +++ +++ killed by SIGKILL +++ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: rhythmbox 3.4.2-4ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Sep 4 14:44:50 2018 InstallationDate: Installed on 2018-07-12 (53 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1790624 Title: rhythmbox periodically hangs during playback via SFTP Status in rhythmbox package in Ubuntu: New Bug description: Scenario: a server is available via LAN from which content is played back via SFTP (ssh, gvfs). After some time (could be an hour) rhythmbox hangs and a window comes up suggesting that you can either wait or terminate rhythmbox. There are no network interruptions that would cause something like this (the issue comes up quite frequently) and plus I do not see any of the threads to be in the D state. strace shows that there is a futex wait for some condition. ps: redacted 20291 3.3 1.0 1989228 173472 tty2 Sl+ 12:14 4:49 rhythmbox ➜ ~ ps -T -o pid,tid,class,rtprio,ni,pri,psr,pcpu,stat,wchan:14,comm -p 20291 PID TID CLS RTPRIO NI PRI PSR %CPU STAT WCHAN COMMAND 20291 20291
[Desktop-packages] [Bug 1764137] Re: [bionic][beta][nvidia] gnome-shell high CPU utilization when using Nvidia driver
A bit odd that I cannot reproduce this on a fresh 18.04 installation on the same system. https://paste.ubuntu.com/p/PqYBPfvvKr/ -- 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/1764137 Title: [bionic][beta][nvidia] gnome-shell high CPU utilization when using Nvidia driver Status in Mutter: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I am experiencing 60% - 200% CPU utilization after an upgrade from ubuntu artful to bionic. Pretty much any drawing results in a sluggish behavior due to high CPU utilization. The same combination of kernel/drivers did not result in the issue on 17.10 so gnome-shell seems a good candidate to blame. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 Uname: Linux 4.16.0-041600-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 15 16:53:34 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-02-27 (412 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-15 (0 days ago) --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-02-27 (412 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux-image-4.16.0-041600-generic 4.16.0-041600.201804012230 [origin: unknown] PackageArchitecture: amd64 Tags: third-party-packages bionic Uname: Linux 4.16.0-041600-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to bionic on 2018-04-15 (0 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo systemd-journal ubridge _MarkForUpload: True ➜ ~ dpkg -l | grep -P 'ii.*?nvidia' ii nvidia-390 390.48-0ubuntu0~gpu17.10.2 amd64 NVIDIA binary driver - version 390.48 ii nvidia-opencl-icd-390 390.48-0ubuntu0~gpu17.10.2 amd64 NVIDIA OpenCL ICD ii nvidia-prime0.8.7 all Tools to enable NVIDIA's Prime ii nvidia-settings 396.18-0ubuntu0~gpu17.10.1 amd64 Tool for configuring the NVIDIA graphics driver To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1764137/+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 1764137] Re: [bionic][beta][nvidia] gnome-shell high CPU utilization when using Nvidia driver
Also, the setup in comment #7 was tested with 4.17-rc4 and 4.17-rc5. -- 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/1764137 Title: [bionic][beta][nvidia] gnome-shell high CPU utilization when using Nvidia driver Status in Mutter: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I am experiencing 60% - 200% CPU utilization after an upgrade from ubuntu artful to bionic. Pretty much any drawing results in a sluggish behavior due to high CPU utilization. The same combination of kernel/drivers did not result in the issue on 17.10 so gnome-shell seems a good candidate to blame. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 Uname: Linux 4.16.0-041600-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 15 16:53:34 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-02-27 (412 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-15 (0 days ago) --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-02-27 (412 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux-image-4.16.0-041600-generic 4.16.0-041600.201804012230 [origin: unknown] PackageArchitecture: amd64 Tags: third-party-packages bionic Uname: Linux 4.16.0-041600-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to bionic on 2018-04-15 (0 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo systemd-journal ubridge _MarkForUpload: True ➜ ~ dpkg -l | grep -P 'ii.*?nvidia' ii nvidia-390 390.48-0ubuntu0~gpu17.10.2 amd64 NVIDIA binary driver - version 390.48 ii nvidia-opencl-icd-390 390.48-0ubuntu0~gpu17.10.2 amd64 NVIDIA OpenCL ICD ii nvidia-prime0.8.7 all Tools to enable NVIDIA's Prime ii nvidia-settings 396.18-0ubuntu0~gpu17.10.1 amd64 Tool for configuring the NVIDIA graphics driver To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1764137/+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 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
I can confirm that the package version from bionic-proposed solves the
problem.
During an installation I used Dell 2715Q with settings as in the
screenshot attached (single monitor mode, 200% scaling).
# the updated package
apt policy ubiquity
ubiquity:
Installed: 18.04.14.1
Candidate: 18.04.14.1
Version table:
*** 18.04.14.1 500
500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages
100 /var/lib/dpkg/status
18.04.14 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
Before adding "deb http://archive.ubuntu.com/ubuntu/ bionic-proposed
main restricted" to sources.list and doing `apt install ubiquity` I had
this in syslog:
ay 13 12:39:12 ubuntu ubiquity: W: --force-yes is deprecated, use one of the
options starting with --allow instead.
May 13 12:39:12 ubuntu ubiquity[4617]: debconffilter_done: ubi-usersetup
(current: ubi-usersetup)
May 13 12:39:12 ubuntu ubiquity[4617]: Step_before = stepUserInfo
May 13 12:39:12 ubuntu kernel: [ 249.861407] do_trap: 40 callbacks suppressed
May 13 12:39:12 ubuntu kernel: [ 249.861410] traps: ubiquity[4617] trap int3
ip:7fc1a36cdc41 sp:7ffe6a90a760 error:0 in
libglib-2.0.so.0.5600.1[7fc1a367c000+113000]
May 13 12:39:21 ubuntu update-notifier[4223]: GtkDialog mapped without a
transient parent. This is discouraged.
May 13 12:39:22 ubuntu /install.py: Exception during installation:
May 13 12:39:22 ubuntu /install.py: Traceback (most recent call last):
May 13 12:39:22 ubuntu /install.py: File "/usr/share/ubiquity/install.py",
line 765, in
May 13 12:39:22 ubuntu /install.py: install.run()
May 13 12:39:22 ubuntu /install.py: File "/usr/share/ubiquity/install.py",
line 135, in run
May 13 12:39:22 ubuntu /install.py: self.copy_all()
May 13 12:39:22 ubuntu /install.py: File "/usr/share/ubiquity/install.py",
line 513, in copy_all
May 13 12:39:22 ubuntu /install.py: self.db.progress('SET', 10 +
copy_progress)
May 13 12:39:22 ubuntu /install.py: File
"/usr/lib/python3/dist-packages/debconf.py", line 83, in
May 13 12:39:22 ubuntu /install.py: lambda *args, **kw:
self.command(command, *args, **kw))
May 13 12:39:22 ubuntu /install.py: File
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
May 13 12:39:22 ubuntu /install.py: status = int(status)
May 13 12:39:22 ubuntu /install.py: ValueError: invalid literal for int() with
base 10: ''
After the update a newly started installation went just fine.
** Attachment added: "displays-dell2715q.png"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1751252/+attachment/5138751/+files/displays-dell2715q.png
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cairo in Ubuntu.
https://bugs.launchpad.net/bugs/1751252
Title:
[regression] ubiquity crashed in debconf.py:104 with ValueError:
invalid literal for int() with base 10: ''
Status in cairo:
Confirmed
Status in OEM Priority Project:
Triaged
Status in cairo package in Ubuntu:
In Progress
Status in ubiquity package in Ubuntu:
Fix Released
Status in cairo source package in Bionic:
In Progress
Status in ubiquity source package in Bionic:
Fix Committed
Bug description:
* Impact
The Ubuntu installer crashes on some machines (seems more often on hiDPI
machines (QHD/UHD etc)).
* Test case
Try installing Ubuntu on an hidpi machine, it should complete installation
instead of crashing.
* Regression potential
The fix in ubiquity touches the code handle uid drop/privilege, that can have
unexpected side effects so we need proper/complete testing of the installer
--
Update: Actually the crash occurs on slow-ish systems due to a race
condition. It's not strictly only hi-DPI machines - that's just the
most common place it is experienced.
---
https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524
---
WORKAROUND:
1. Boot into the live session.
2. Settings > Devices > Displays > Scale = 100%
3. Click Apply.
4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".
---
Crashed in a VM in the middle of installation. The host is Bionic up
to date.
From the journal
Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3
ip:7f5a76936961 sp:7ffde5090c50 error:0 in
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
Feb 23 12:52:41 ubuntu /install.py[6858]: File
[Desktop-packages] [Bug 1764137] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1764137/+attachment/5116800/+files/ProcCpuinfoMinimal.txt -- 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/1764137 Title: [bionic][beta][nvidia] gnome-shell high cpu utilization Status in gnome-shell package in Ubuntu: New Bug description: I am experiencing 60% - 200% CPU utilization after an upgrade from ubuntu artful to bionic. Pretty much any drawing results in a sluggish behavior due to high CPU utilization. The same combination of kernel/drivers did not result in the issue on 17.10 so gnome-shell seems a good candidate to blame. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 Uname: Linux 4.16.0-041600-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 15 16:53:34 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-02-27 (412 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-15 (0 days ago) --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-02-27 (412 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux-image-4.16.0-041600-generic 4.16.0-041600.201804012230 [origin: unknown] PackageArchitecture: amd64 Tags: third-party-packages bionic Uname: Linux 4.16.0-041600-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to bionic on 2018-04-15 (0 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo systemd-journal ubridge _MarkForUpload: True ➜ ~ dpkg -l | grep -P 'ii.*?nvidia' ii nvidia-390 390.48-0ubuntu0~gpu17.10.2 amd64 NVIDIA binary driver - version 390.48 ii nvidia-opencl-icd-390 390.48-0ubuntu0~gpu17.10.2 amd64 NVIDIA OpenCL ICD ii nvidia-prime0.8.7 all Tools to enable NVIDIA's Prime ii nvidia-settings 396.18-0ubuntu0~gpu17.10.1 amd64 Tool for configuring the NVIDIA graphics driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764137/+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 1764137] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1764137/+attachment/5116801/+files/ProcEnviron.txt ** Description changed: I am experiencing 60% - 200% CPU utilization after an upgrade from ubuntu artful to bionic. Pretty much any drawing results in a sluggish behavior due to high CPU utilization. The same combination of kernel/drivers did not result in the issue on 17.10 so gnome-shell seems a good candidate to blame. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 Uname: Linux 4.16.0-041600-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 15 16:53:34 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-02-27 (412 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-15 (0 days ago) - --- + --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-02-27 (412 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux-image-4.16.0-041600-generic 4.16.0-041600.201804012230 [origin: unknown] PackageArchitecture: amd64 Tags: third-party-packages bionic Uname: Linux 4.16.0-041600-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to bionic on 2018-04-15 (0 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo systemd-journal ubridge _MarkForUpload: True + + ➜ ~ dpkg -l | grep -P 'ii.*?nvidia' + ii nvidia-390 390.48-0ubuntu0~gpu17.10.2 amd64 NVIDIA binary driver - version 390.48 + ii nvidia-opencl-icd-390 390.48-0ubuntu0~gpu17.10.2 amd64 NVIDIA OpenCL ICD + ii nvidia-prime0.8.7 all Tools to enable NVIDIA's Prime + ii nvidia-settings 396.18-0ubuntu0~gpu17.10.1 amd64 Tool for configuring the NVIDIA graphics driver -- 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/1764137 Title: [bionic][beta][nvidia] gnome-shell high cpu utilization Status in gnome-shell package in Ubuntu: New Bug description: I am experiencing 60% - 200% CPU utilization after an upgrade from ubuntu artful to bionic. Pretty much any drawing results in a sluggish behavior due to high CPU utilization. The same combination of kernel/drivers did not result in the issue on 17.10 so gnome-shell seems a good candidate to blame. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 Uname: Linux 4.16.0-041600-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 15 16:53:34 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-02-27 (412 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-15 (0 days ago) --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-02-27 (412 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux-image-4.16.0-041600-generic 4.16.0-041600.201804012230 [origin: unknown] PackageArchitecture: amd64 Tags: third-party-packages bionic Uname: Linux 4.16.0-041600-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to bionic on 2018-04-15 (0 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo systemd-journal ubridge _MarkForUpload: True ➜ ~ dpkg -l | grep -P 'ii.*?nvidia' ii nvidia-390 390.48-0ubuntu0~gpu17.10.2 amd64 NVIDIA binary driver - version 390.48 ii nvidia-opencl-icd-390 390.48-0ubuntu0~gpu17.10.2
[Desktop-packages] [Bug 1764137] Re: [bionic][beta][nvidia] gnome-shell high cpu utilization
apport information ** Tags added: apport-collected ** Description changed: I am experiencing 60% - 200% CPU utilization after an upgrade from ubuntu artful to bionic. Pretty much any drawing results in a sluggish behavior due to high CPU utilization. The same combination of kernel/drivers did not result in the issue on 17.10 so gnome-shell seems a good candidate to blame. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 Uname: Linux 4.16.0-041600-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 15 16:53:34 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-02-27 (412 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-15 (0 days ago) + --- + ApportVersion: 2.20.9-0ubuntu4 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2017-02-27 (412 days ago) + InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) + NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia + Package: linux-image-4.16.0-041600-generic 4.16.0-041600.201804012230 [origin: unknown] + PackageArchitecture: amd64 + Tags: third-party-packages bionic + Uname: Linux 4.16.0-041600-generic x86_64 + UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. + UpgradeStatus: Upgraded to bionic on 2018-04-15 (0 days ago) + UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo systemd-journal ubridge + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1764137/+attachment/5116799/+files/Dependencies.txt -- 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/1764137 Title: [bionic][beta][nvidia] gnome-shell high cpu utilization Status in gnome-shell package in Ubuntu: New Bug description: I am experiencing 60% - 200% CPU utilization after an upgrade from ubuntu artful to bionic. Pretty much any drawing results in a sluggish behavior due to high CPU utilization. The same combination of kernel/drivers did not result in the issue on 17.10 so gnome-shell seems a good candidate to blame. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 Uname: Linux 4.16.0-041600-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 15 16:53:34 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-02-27 (412 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-15 (0 days ago) --- ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-02-27 (412 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux-image-4.16.0-041600-generic 4.16.0-041600.201804012230 [origin: unknown] PackageArchitecture: amd64 Tags: third-party-packages bionic Uname: Linux 4.16.0-041600-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: Upgraded to bionic on 2018-04-15 (0 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo systemd-journal ubridge _MarkForUpload: True ➜ ~ dpkg -l | grep -P 'ii.*?nvidia' ii nvidia-390 390.48-0ubuntu0~gpu17.10.2 amd64 NVIDIA binary driver - version 390.48 ii nvidia-opencl-icd-390 390.48-0ubuntu0~gpu17.10.2 amd64 NVIDIA OpenCL ICD ii nvidia-prime0.8.7 all Tools to enable NVIDIA's Prime ii nvidia-settings 396.18-0ubuntu0~gpu17.10.1 amd64 Tool for configuring the NVIDIA graphics driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1764137] [NEW] [bionic][beta][nvidia] gnome-shell high cpu utilization
Public bug reported: I am experiencing 60% - 200% CPU utilization after an upgrade from ubuntu artful to bionic. Pretty much any drawing results in a sluggish behavior due to high CPU utilization. The same combination of kernel/drivers did not result in the issue on 17.10 so gnome-shell seems a good candidate to blame. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 Uname: Linux 4.16.0-041600-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 15 16:53:34 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-02-27 (412 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-15 (0 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- 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/1764137 Title: [bionic][beta][nvidia] gnome-shell high cpu utilization Status in gnome-shell package in Ubuntu: New Bug description: I am experiencing 60% - 200% CPU utilization after an upgrade from ubuntu artful to bionic. Pretty much any drawing results in a sluggish behavior due to high CPU utilization. The same combination of kernel/drivers did not result in the issue on 17.10 so gnome-shell seems a good candidate to blame. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu5 Uname: Linux 4.16.0-041600-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 15 16:53:34 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-02-27 (412 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-15 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1764137/+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 1738859] Re: hotkeys do not work when xkbmap uses a regional layout instead of en_US, gnome input source is ignored
Alright, it seems that the problem was in "layout: ru,us,us". When I
switched to "layout: us" my gnome settings stopped affecting input so I
switched it to the following:
➜ ~ sudo setxkbmap -option grp:alt_shift_toggle us,ru
➜ ~ setxkbmap -query
rules: evdev
model: pc105
layout: us,ru
options:grp:alt_shift_toggle,grp_led:scroll
With "us,ru" layout both switching in gnome works AND shortcuts in inkscape.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1738859
Title:
hotkeys do not work when xkbmap uses a regional layout instead of
en_US, gnome input source is ignored
Status in inkscape package in Ubuntu:
New
Bug description:
Symptom: hotkeys do not work at all. It seems to only affect letters
themselves while Ctrl, Shift or Alt are interpreted (as shown in a bar
at the bottom of the UI).
➜ ~ echo $XDG_SESSION_DESKTOP
ubuntu-xorg
I do have two keyboard layouts enabled, however, I used en_US in Gnome
while trying to trigger any hotkey actions.
# the first one is the one used currently as this is an MRU list
➜ ~ gsettings get org.gnome.desktop.input-sources mru-sources
[('xkb', 'us'), ('xkb', 'ru')]
The default Inkscape hotkey file is used, so, for example, undo should work
just fine but it doesn't:
/usr/share/inkscape/keys/default.xml
...
I sniffed around little bit and found out that XKB layout was set to
'ru':
➜ ~ setxkbmap -query
rules: evdev
model: pc105
layout: ru,us,us
variant:,,
options:grp:alt_shift_toggle,grp_led:scroll
After changing that to 'us' via setxkbmap shortcuts immediately
started to work (without inkscape restart):
➜ ~ sudo setxkbmap -option grp:alt_shift_toggle us
➜ ~ setxkbmap -query
rules: evdev
model: pc105
layout: us
options:grp:alt_shift_toggle,grp_led:scroll
Doing this via CLI, however, somehow breaks switching language in
gnome itself (changes are present in the MRU list but input is
localized and is not switched).
The only suspicious message I found in syslog after that was this:
Dec 18 21:42:34 blade /usr/lib/gdm3/gdm-x-session[8236]: The XKEYBOARD keymap
compiler (xkbcomp) reports:
Dec 18 21:42:34 blade /usr/lib/gdm3/gdm-x-session[8236]: > Error:
Can't find file "" for symbols include
Dec 18 21:42:34 blade /usr/lib/gdm3/gdm-x-session[8236]: >
Exiting
Dec 18 21:42:34 blade /usr/lib/gdm3/gdm-x-session[8236]: >
Abandoning symbols file "default"
Dec 18 21:42:34 blade /usr/lib/gdm3/gdm-x-session[8236]: Errors from xkbcomp
are not fatal to the X server
Dec 18 21:42:34 blade /usr/lib/gdm3/gdm-x-session[8236]: (EE) Error loading
keymap /tmp/server-1.xkm
Dec 18 21:42:37 blade /usr/lib/gdm3/gdm-x-session[8236]: The XKEYBOARD keymap
compiler (xkbcomp) reports:
Dec 18 21:42:37 blade /usr/lib/gdm3/gdm-x-session[8236]: > Error:
Can't find file "" for symbols include
Dec 18 21:42:37 blade /usr/lib/gdm3/gdm-x-session[8236]: >
Exiting
Dec 18 21:42:37 blade /usr/lib/gdm3/gdm-x-session[8236]: >
Abandoning symbols file "default"
Dec 18 21:42:37 blade /usr/lib/gdm3/gdm-x-session[8236]: Errors from xkbcomp
are not fatal to the X server
Dec 18 21:42:37 blade /usr/lib/gdm3/gdm-x-session[8236]: (EE) Error loading
keymap /tmp/server-1.xkm
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: inkscape 0.92.2-1build1
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 18 21:24:39 2017
InstallationDate: Installed on 2017-02-27 (294 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
SourcePackage: inkscape
UpgradeStatus: Upgraded to artful on 2017-09-13 (95 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/inkscape/+bug/1738859/+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 1738859] [NEW] hotkeys do not work when xkbmap uses a regional layout instead of en_US, gnome input source is ignored
Public bug reported:
Symptom: hotkeys do not work at all. It seems to only affect letters
themselves while Ctrl, Shift or Alt are interpreted (as shown in a bar
at the bottom of the UI).
➜ ~ echo $XDG_SESSION_DESKTOP
ubuntu-xorg
I do have two keyboard layouts enabled, however, I used en_US in Gnome
while trying to trigger any hotkey actions.
# the first one is the one used currently as this is an MRU list
➜ ~ gsettings get org.gnome.desktop.input-sources mru-sources
[('xkb', 'us'), ('xkb', 'ru')]
The default Inkscape hotkey file is used, so, for example, undo should work
just fine but it doesn't:
/usr/share/inkscape/keys/default.xml
...
I sniffed around little bit and found out that XKB layout was set to
'ru':
➜ ~ setxkbmap -query
rules: evdev
model: pc105
layout: ru,us,us
variant:,,
options:grp:alt_shift_toggle,grp_led:scroll
After changing that to 'us' via setxkbmap shortcuts immediately started
to work (without inkscape restart):
➜ ~ sudo setxkbmap -option grp:alt_shift_toggle us
➜ ~ setxkbmap -query
rules: evdev
model: pc105
layout: us
options:grp:alt_shift_toggle,grp_led:scroll
Doing this via CLI, however, somehow breaks switching language in gnome
itself (changes are present in the MRU list but input is localized and
is not switched).
The only suspicious message I found in syslog after that was this:
Dec 18 21:42:34 blade /usr/lib/gdm3/gdm-x-session[8236]: The XKEYBOARD keymap
compiler (xkbcomp) reports:
Dec 18 21:42:34 blade /usr/lib/gdm3/gdm-x-session[8236]: > Error:
Can't find file "" for symbols include
Dec 18 21:42:34 blade /usr/lib/gdm3/gdm-x-session[8236]: >
Exiting
Dec 18 21:42:34 blade /usr/lib/gdm3/gdm-x-session[8236]: >
Abandoning symbols file "default"
Dec 18 21:42:34 blade /usr/lib/gdm3/gdm-x-session[8236]: Errors from xkbcomp
are not fatal to the X server
Dec 18 21:42:34 blade /usr/lib/gdm3/gdm-x-session[8236]: (EE) Error loading
keymap /tmp/server-1.xkm
Dec 18 21:42:37 blade /usr/lib/gdm3/gdm-x-session[8236]: The XKEYBOARD keymap
compiler (xkbcomp) reports:
Dec 18 21:42:37 blade /usr/lib/gdm3/gdm-x-session[8236]: > Error:
Can't find file "" for symbols include
Dec 18 21:42:37 blade /usr/lib/gdm3/gdm-x-session[8236]: >
Exiting
Dec 18 21:42:37 blade /usr/lib/gdm3/gdm-x-session[8236]: >
Abandoning symbols file "default"
Dec 18 21:42:37 blade /usr/lib/gdm3/gdm-x-session[8236]: Errors from xkbcomp
are not fatal to the X server
Dec 18 21:42:37 blade /usr/lib/gdm3/gdm-x-session[8236]: (EE) Error loading
keymap /tmp/server-1.xkm
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: inkscape 0.92.2-1build1
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 18 21:24:39 2017
InstallationDate: Installed on 2017-02-27 (294 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227)
SourcePackage: inkscape
UpgradeStatus: Upgraded to artful on 2017-09-13 (95 days ago)
** Affects: inkscape (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug artful
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1738859
Title:
hotkeys do not work when xkbmap uses a regional layout instead of
en_US, gnome input source is ignored
Status in inkscape package in Ubuntu:
New
Bug description:
Symptom: hotkeys do not work at all. It seems to only affect letters
themselves while Ctrl, Shift or Alt are interpreted (as shown in a bar
at the bottom of the UI).
➜ ~ echo $XDG_SESSION_DESKTOP
ubuntu-xorg
I do have two keyboard layouts enabled, however, I used en_US in Gnome
while trying to trigger any hotkey actions.
# the first one is the one used currently as this is an MRU list
➜ ~ gsettings get org.gnome.desktop.input-sources mru-sources
[('xkb', 'us'), ('xkb', 'ru')]
The default Inkscape hotkey file is used, so, for example, undo should work
just fine but it doesn't:
/usr/share/inkscape/keys/default.xml
...
I sniffed around little bit and found out that XKB layout was set to
'ru':
➜ ~ setxkbmap -query
rules: evdev
model: pc105
layout: ru,us,us
variant:,,
options:grp:alt_shift_toggle,grp_led:scroll
After changing that to 'us' via setxkbmap shortcuts immediately
started to work (without inkscape restart):
➜ ~ sudo setxkbmap -option grp:alt_shift_toggle us
➜ ~ setxkbmap -query
rules:
[Desktop-packages] [Bug 1716341] Re: Settings for external monitor are deleted after reboot, suspension, log out
Chris, out of curiosity, do you have a dual-monitor setup? https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726538 For me it works fine with a laptop monitor disabled + single monitor as a primary. -- 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/1716341 Title: Settings for external monitor are deleted after reboot, suspension, log out Status in gnome-control-center: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Artful: Fix Released Bug description: New Gnome Settings on Ubuntu 17.10 Settings for external monitor are working but after reboot/suspension /log-out log-in, the system will not remember the setup. Example: 1- open Gnome Settings and select "Devices → Displays" 2- set the external monitor as "Single Display" and click on "Apply" 3- log-out After log-in the laptop monitor will be set as default instead of the external monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1716341/+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 1716341] Re: Settings for external monitor are deleted after reboot, suspension, log out
Hmm, for my installation upgraded from 17.04 it got fixed - I no longer experience the issue. -- 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/1716341 Title: Settings for external monitor are deleted after reboot, suspension, log out Status in gnome-control-center: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Artful: Fix Released Bug description: New Gnome Settings on Ubuntu 17.10 Settings for external monitor are working but after reboot/suspension /log-out log-in, the system will not remember the setup. Example: 1- open Gnome Settings and select "Devices → Displays" 2- set the external monitor as "Single Display" and click on "Apply" 3- log-out After log-in the laptop monitor will be set as default instead of the external monitor. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1716341/+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 1723678] [NEW] Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. | This was previously supported, but is not correct according to the ES6 stand
Public bug reported: On-boot message in the log: окт 15 01:50:32 blade gnome-shell[6314]: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 02:05:17 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-02-27 (229 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-13 (31 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- 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/1723678 Title: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. | This was previously supported, but is not correct according to the ES6 standard. Status in gnome-shell package in Ubuntu: New Bug description: On-boot message in the log: окт 15 01:50:32 blade gnome-shell[6314]: Some code accessed the property 'discreteGpuAvailable' on the module 'appDisplay'. That property was defined with 'let' or 'const' inside the module. This was previously supported, but is not correct according to the ES6 standard. Any symbols to be exported from a module must be defined with 'var'. The property access will work as previously for the time being, but please fix your code anyway. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 02:05:17 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-02-27 (229 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-13 (31 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723678/+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 1722000] Re: gnome shell crashes after display config is changed to only show on a secondary monitor
This used to work before recent a update of several distro packages. Currently settings are not applied and everything falls back to "Join displays" instead of "Single Display". --- After debugging that a little bit more I can see that the bug is not triggered if I do not change scaling from 100% to 200% at the same time. The primary laptop display goes offline and I only have a secondary running. If I try to go from "Scaling: 100%" to 200%, I immediately get the problematic behavior. ➜ ~ echo $XDG_SESSION_DESKTOP ubuntu-xorg This is what goes to syslog right after I press a button to change scaling to 200%. http://paste.ubuntu.com/25694579/ ** Summary changed: - gnome shell crashes after display config is changed to only show on a secondary monitor + gnome shell crashes after scaling is changed from 100% to 200% (segfault at 8 ip 7f22c7bdf877 sp 7ffde76cadf0 error 4 in libmutter-1.so.0.0.0[7f22c7b36000+141000]) -- 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/1722000 Title: gnome shell crashes after scaling is changed from 100% to 200% (segfault at 8 ip 7f22c7bdf877 sp 7ffde76cadf0 error 4 in libmutter-1.so.0.0.0[7f22c7b36000+141000]) Status in gnome-shell package in Ubuntu: New Bug description: Attached screenshots for "before applying" and after. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 7 21:57:36 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-02-27 (222 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-13 (23 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722000/+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 1722000] Re: gnome shell crashes after display config is changed to only show on a secondary monitor
** Attachment added: "After" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722000/+attachment/4964664/+files/after.png -- 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/1722000 Title: gnome shell crashes after scaling is changed from 100% to 200% (segfault at 8 ip 7f22c7bdf877 sp 7ffde76cadf0 error 4 in libmutter-1.so.0.0.0[7f22c7b36000+141000]) Status in gnome-shell package in Ubuntu: New Bug description: Attached screenshots for "before applying" and after. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 7 21:57:36 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-02-27 (222 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-13 (23 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722000/+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 1722000] Re: gnome shell crashes after display config is changed to only show on a secondary monitor
This used to work before recent a update of several distro packages. Currently settings are not applied and everything falls back to "Join displays" instead of "Single Display" -- 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/1722000 Title: gnome shell crashes after scaling is changed from 100% to 200% (segfault at 8 ip 7f22c7bdf877 sp 7ffde76cadf0 error 4 in libmutter-1.so.0.0.0[7f22c7b36000+141000]) Status in gnome-shell package in Ubuntu: New Bug description: Attached screenshots for "before applying" and after. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 7 21:57:36 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-02-27 (222 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-13 (23 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722000/+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 1722000] [NEW] gnome shell crashes after scaling is changed from 100% to 200% (segfault at 8 ip 00007f22c7bdf877 sp 00007ffde76cadf0 error 4 in libmutter-1.so.0.0.0[7f22c7b3600
Public bug reported: Attached screenshots for "before applying" and after. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 7 21:57:36 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-02-27 (222 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-13 (23 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Attachment added: "before-applying.png" https://bugs.launchpad.net/bugs/1722000/+attachment/4964658/+files/before-applying.png -- 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/1722000 Title: gnome shell crashes after scaling is changed from 100% to 200% (segfault at 8 ip 7f22c7bdf877 sp 7ffde76cadf0 error 4 in libmutter-1.so.0.0.0[7f22c7b36000+141000]) Status in gnome-shell package in Ubuntu: New Bug description: Attached screenshots for "before applying" and after. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 7 21:57:36 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-02-27 (222 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170227) SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-09-13 (23 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722000/+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 1712520] [NEW] [17.04][gnome] screen hanged after meld launched via terminal was put to sleep by C-z: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
Public bug reported: Surprisingly, when I launched meld as a difftool and later suspended it my session got frozen: my mouse was moving but clicks and keyboard presses did not have any effect, there was an empty rectangle on my screen on top of one of the windows. The only thing I could do was to switch to a different VT and take a look at what's going on. Actions: git difftool master tests/basic_deployment.py This message is displayed because 'diff.tool' is not configured. See 'git difftool --tool-help' or 'git help config' for more details. 'git difftool' will now attempt to use one of the following tools: meld opendiff kdiff3 tkdiff xxdiff kompare gvimdiff diffuse diffmerge ecmerge p4merge araxis bc codecompare emerge vimdiff Viewing (1/1): 'tests/basic_deployment.py' Launch 'meld' [Y/n]? y ^Z [1] + 16839 suspended git difftool master tests/basic_deployment.py lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 17.04 Release:17.04 Codename: zesty dpkg -l 'gnome-session' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version ArchitectureDescription +++-=-===-===- ii gnome-session 3.24.0-0ubuntu1 amd64 GNOME Session Manager - GNOME 3 session ➜ ~ dpkg -l 'libgtk*' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version ArchitectureDescription +++-=-===-===- ii libgtk-3-0:amd64 3.22.11-0ubuntu3 amd64 GTK+ graphical user interface library ii libgtk-3-bin 3.22.11-0ubuntu3 amd64 programs for the GTK+ graphical user interface library ii libgtk-3-common 3.22.11-0ubuntu3 all common files for the GTK+ graphical user interface library un libgtk-vnc-1.0-0 (no description available) ii libgtk-vnc-2.0-0:amd640.6.0-3 amd64 VNC viewer widget for GTK+3 (runtime libraries) ii libgtk2-perl 2:1.2499-1 amd64 Perl interface to the 2.x series of the Gimp Toolkit library un libgtk2-perl-doc (no description available) ii libgtk2.0-0:amd64 2.24.31-1ubuntu1.1 amd64 GTK+ graphical user interface library ii libgtk2.0-bin 2.24.31-1ubuntu1.1 amd64 programs for the GTK+ graphical user interface library ii libgtk2.0-common 2.24.31-1ubuntu1.1 all common files for the GTK+ graphical user interface library ii libgtkglext1:amd641.2.0-6 amd64 OpenGL Extension to GTK+ (shared libraries) un libgtkmm-2.4-1c2a (no description available) ii libgtkmm-2.4-1v5:amd641:2.24.5-1 amd64 C++ wrappers for GTK+ (shared libraries) un libgtkmm-3.0-1 (no description available) ii libgtkmm-3.0-1v5:amd643.22.0-1 amd64 C++ wrappers for GTK+ (shared libraries) ii libgtksourceview-3.0-1:amd64 3.24.0-0ubuntu1 amd64 shared libraries for the GTK+ syntax highlighting widget ii
[Desktop-packages] [Bug 1684100] Re: TP-LINK TL-WN722N 150MBPS not working on Ubuntu 17.04. Worked fine on 16.10
Worked for me: cat /etc/NetworkManager/conf.d/tl-wn722n.conf [device] match-device=wlx18a6f719681b wifi.scan-rand-mac-address=0 Thanks for starting this thread. -- 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/1684100 Title: TP-LINK TL-WN722N 150MBPS not working on Ubuntu 17.04. Worked fine on 16.10 Status in network-manager package in Ubuntu: Confirmed Bug description: TP-LINK TL-WN722N 150MBPS not working on Ubuntu 17.04. Worked fine on 16.10 sudo apt-get update; sudo apt-get install usbutils pciutils hwinfo grep rfkill; sudo lshw -C network; rfkill list; sudo iwlist scan | grep -Ei 'chan|ssid'; cat /etc/network/interfaces; cat /etc/lsb-release; lspci -nnk | grep -iA2 net; lsusb; nmcli nm status; sudo lshw -short; uname -a; sudo updatedb; dmesg | grep -E '02:00|80211|acx|at76|ath|b43|bcm|brcm|CX|eth|ipw|ireless|irmware|isl|lbtf|orinoco|ndiswrapper|NPE|ound|p54|prism|rror|rtl|RTL|rt2|RT2|rt3|RT3|rt5|RT5|rt6|RT6|rt7|RT7|usb|witch|wl';sudo dmidecode|grep -E 'anufact|roduct|erial|elease'; iwconfig; grep -E '80211|acx|at76|ath|b43|bcm|brcm|CX|eth|ipw|irmware|isl|lbtf|orinoco|ndiswrapper|NPE|p54|prism|rtl|rt2|rt3|rt6|rt7|wmi|witch|wl' /etc/modprobe.d/*; cat /var/lib/NetworkManager/NetworkManager.state; sudo hwinfo --netcard ; ps -aux|grep -E 'wpa|icd|etwork'; netstat -rn ; cat /etc/resolv.conf; ls -lia /boot; grep tmpfs /etc/fstab; ubuntu-support-status; sudo update-pciids; sudo update-usbids; sudo lsmod Get:1 http://security.ubuntu.com/ubuntu zesty-security InRelease [89.2 kB] Get:2 http://gb.archive.ubuntu.com/ubuntu zesty InRelease [243 kB] Get:3 http://gb.archive.ubuntu.com/ubuntu zesty-updates InRelease [89.2 kB] Hit:4 http://gb.archive.ubuntu.com/ubuntu zesty-backports InRelease Fetched 421 kB in 0s (873 kB/s) Reading package lists... Done Reading package lists... Done Building dependency tree Reading state information... Done grep is already the newest version (2.27-2). pciutils is already the newest version (1:3.3.1-1.1ubuntu9). pciutils set to manually installed. rfkill is already the newest version (0.5-1ubuntu3). rfkill set to manually installed. usbutils is already the newest version (1:007-4). usbutils set to manually installed. The following additional packages will be installed: libhd21 libx86emu1 The following NEW packages will be installed hwinfo libhd21 libx86emu1 0 to upgrade, 3 to newly install, 0 to remove and 0 not to upgrade. Need to get 754 kB of archives. After this operation, 3,261 kB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://gb.archive.ubuntu.com/ubuntu zesty/universe amd64 libx86emu1 amd64 1.11-2 [47.8 kB] Get:2 http://gb.archive.ubuntu.com/ubuntu zesty/universe amd64 libhd21 amd64 21.38-1 [688 kB] Get:3 http://gb.archive.ubuntu.com/ubuntu zesty/universe amd64 hwinfo amd64 21.38-1 [17.7 kB] Fetched 754 kB in 0s (2,074 kB/s) Selecting previously unselected package libx86emu1:amd64. (Reading database ... 177811 files and directories currently installed.) Preparing to unpack .../libx86emu1_1.11-2_amd64.deb ... Unpacking libx86emu1:amd64 (1.11-2) ... Selecting previously unselected package libhd21:amd64. Preparing to unpack .../libhd21_21.38-1_amd64.deb ... Unpacking libhd21:amd64 (21.38-1) ... Selecting previously unselected package hwinfo. Preparing to unpack .../hwinfo_21.38-1_amd64.deb ... Unpacking hwinfo (21.38-1) ... Setting up libx86emu1:amd64 (1.11-2) ... Processing triggers for libc-bin (2.24-9ubuntu2) ... Processing triggers for man-db (2.7.6.1-2) ... Setting up libhd21:amd64 (21.38-1) ... Setting up hwinfo (21.38-1) ... Processing triggers for libc-bin (2.24-9ubuntu2) ... *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:04:00.0 logical name: enp4s0 version: 06 serial: f4:6d:04:90:cb:7a size: 10Mbit/s capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl_nic/rtl8168e-2.fw latency=0 link=no multicast=yes port=MII speed=10Mbit/s resources: irq:31 ioport:c000(size=256) memory:f0004000-f0004fff memory:f000-f0003fff *-network:0 description: Wireless interface physical id: 3 bus info: usb@2:1.7 logical name: wlxf81a6721bb82 serial: 56:3e:54:48:50:00 capabilities: ethernet
