[Ubuntu-x-swat] [Bug 2003031] Re: gjs crash crashes gnome session
Thanks for the bug report. The biggest issue here seems to be a kernel crash: Jan 16 19:40:28 semiauto kernel: [84513.834489] adding CRTC not allowed without modesets: requested 0x4, affected 0x7 Jan 16 19:40:28 semiauto kernel: [84513.834564] WARNING: CPU: 4 PID: 2041 at drivers/gpu/drm/drm_atomic.c:1403 drm_atomic_check_only+0x40c/0x450 [drm] But it sounds like the kernel is complaining that gnome-shell is to blame. To work around that, please try adding: MUTTER_DEBUG_FORCE_KMS_MODE=simple to /etc/environment and then reboot. But there are three different crashes here and we need separate bugs opened for each. The other two crashes are of 'gjs-console' and I can see 'gnome-shell' also crashed according to the log. Please open new bugs about each of those by following https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Summary changed: - gjs crash crashes gnome session + gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7" ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #6728 https://gitlab.freedesktop.org/drm/intel/-/issues/6728 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2003031 Title: gnome-shell crashes in the kernel at drm_atomic_check_only and the kernel says "adding CRTC not allowed without modesets: requested 0x4, affected 0x7" To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2003031/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1998950] Re: GPU hang on Alder Lake laptop
Hmm perhaps bug 2001914 needs revisiting though (22.04) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1998950 Title: GPU hang on Alder Lake laptop To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1998950/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1998950] Re: GPU hang on Alder Lake laptop
Thanks. I did have a configuration in which I could reproduce this recently so myself or someone else should look at confirming it's really fixed. I wasn't too worried about this bug though because: * It never happens on 22.04 * 23.04 will get kernels 6.1 and 6.2 in the coming months ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: mesa (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1998950 Title: GPU hang on Alder Lake laptop To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1998950/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2003031] [NEW] gjs crash crashes gnome session
Public bug reported: GJS crashes - here's the crashdump. I saw the crash occur after a screensaver had been running, and the screens had gone blank. I assume this means they were turned off by the sleep timer. When I worke the machine, I was presented with a prompt, I *quickly* entered my login credentials and momentarily saw the desktop and all open programs on it. Then, the screens (3) flickered and I saw the login prompt again. I logged in (again), and all applications had been shut down. I checked /var/log/syslog and saw the following details -- see (log). Uploaded file, and the crashdump. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 16 20:52:55 2023 DistUpgraded: 2023-01-14 21:42:30,924 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: 8812au/5.6.4.2_35491.20191025, 5.15.0-58-generic, x86_64: installed 8812au/5.6.4.2_35491.20191025, 5.19.0-29-generic, x86_64: installed nvidia/470.161.03, 5.19.0-29-generic, x86_64: installed virtualbox/6.1.38, 5.15.0-58-generic, x86_64: installed virtualbox/6.1.38, 5.19.0-29-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Lenovo TigerLake-LP GT2 [Iris Xe Graphics] [17aa:22d4] InstallationDate: Installed on 2023-01-09 (7 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: LENOVO 20XY0027US ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1cae8af8-977f-4853-9106-9169f34c4bc2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to kinetic on 2023-01-15 (1 days ago) dmi.bios.date: 07/27/2022 dmi.bios.release: 1.55 dmi.bios.vendor: LENOVO dmi.bios.version: N32ET79W (1.55 ) dmi.board.asset.tag: Not Available dmi.board.name: 20XY0027US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.33 dmi.modalias: dmi:bvnLENOVO:bvrN32ET79W(1.55):bd07/27/2022:br1.55:efr1.33:svnLENOVO:pn20XY0027US:pvrThinkPadX1YogaGen6:rvnLENOVO:rn20XY0027US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:skuLENOVO_MT_20XY_BU_Think_FM_ThinkPadX1YogaGen6: dmi.product.family: ThinkPad X1 Yoga Gen 6 dmi.product.name: 20XY0027US dmi.product.sku: LENOVO_MT_20XY_BU_Think_FM_ThinkPad X1 Yoga Gen 6 dmi.product.version: ThinkPad X1 Yoga Gen 6 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash kinetic third-party-packages ubuntu wayland-session ** Attachment added: "this is the crashdump for this bug report, 'log' is the syslog details at the same time." https://bugs.launchpad.net/bugs/2003031/+attachment/5641786/+files/gjs-crash-report.tar.gz -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/2003031 Title: gjs crash crashes gnome session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2003031/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2003004] Re: Cannot write X config due to missing u+x permissions on nvidia-polkit
** Also affects: nvidia-drivers-ubuntu Importance: Undecided Status: New ** Also affects: hundredpapercuts Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/2003004 Title: Cannot write X config due to missing u+x permissions on nvidia-polkit To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/2003004/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2003004] [NEW] Cannot write X config due to missing u+x permissions on nvidia-polkit
Public bug reported: Despite being this similar to an old bug 1625119, which was on a now unsupported release, I asked on #ubuntu whether I should go for a new bug and was directed to file this as a new bug. I have an Asus NVidia RTX 3060. I am running: Description:Ubuntu 22.04.1 LTS Release:22.04 a supported release, and found a solution on that release. I am using a fully patched system with nvidia-settings 510.47.03-0ubuntu1. I expected, when running nvidia-settings as root, when I clicked on the button to write out the settings I just configured to /etc/X11/xorg.conf for that to work. It does not with permission denied. The tools needs to be able to write /etc/X11/xorg.conf when root requests it. I tracked this down to a missing permission on /usr/share/screen- resolution-extra/nvidia-polkit which had permissions 644 on my system. The following change fixed this for me: chmod u+x /usr/share/screen-resolution-extra/nvidia-polkit I found many users online with similar issues in forums. Please update the package to implement the equivalent and close this. FYI end user configuration without root has improved significantly since 16.04 such that it would be reasonable in my honest opinion to also close 1625119 as fixed in 22.04 once this is done. It is fixed as well as security allows. It is reasonable from my point of view for security reasons to need root to change such a critical file as /etc/X11/xorg.conf. ** Affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New ** Description changed: - Despite this similar to an old bug 1625119 I asked on #ubuntu whether I - should go for a new bug and was directed to file this as a new bug. + Despite being this similar to an old bug 1625119, which was on a now + unsupported release, I asked on #ubuntu whether I should go for a new + bug and was directed to file this as a new bug. I have an Asus NVidia RTX 3060. I am running: Description: Ubuntu 22.04.1 LTS Release: 22.04 a supported release, and found a solution on that release. I am using a fully patched system with nvidia-settings 510.47.03-0ubuntu1. I expected, when running as root, when I clicked on the button to write out the settings I just configured in nvidia-settings to /etc/X11/xorg.conf for that to work. It does not with permission denied. It needs to be able to write /etc/X11/xorg.conf when running as root when the user requests it. Attempting to run nvidia-settings as root it cannot write to that configuration file. I tracked this down to a missing permission on /usr/share/screen- resolution-extra/nvidia-polkit which was 644 on my system. The following change fixed this for me: chmod u+x /usr/share/screen-resolution-extra/nvidia-polkit I found many users online with similar issues in forums. Please update the package to implement the equivalent and close this. FYI end user configuration without root has improved significantly since 16.04 such that it would be reasonable in my honest opinion to close 1625119 as fixed in 22.04 once this is done. It is also reasonable from my point of view for security reasons to need root to change such a critical file as /etc/X11/xorg.conf. ** Description changed: Despite being this similar to an old bug 1625119, which was on a now unsupported release, I asked on #ubuntu whether I should go for a new bug and was directed to file this as a new bug. I have an Asus NVidia RTX 3060. I am running: Description: Ubuntu 22.04.1 LTS Release: 22.04 a supported release, and found a solution on that release. I am using a fully patched system with nvidia-settings 510.47.03-0ubuntu1. - I expected, when running as root, when I clicked on the button to write - out the settings I just configured in nvidia-settings to - /etc/X11/xorg.conf for that to work. It does not with permission denied. + I expected, when running nvidia-settings as root, when I clicked on the + button to write out the settings I just configured to /etc/X11/xorg.conf + for that to work. It does not with permission denied. - It needs to be able to write /etc/X11/xorg.conf when running as root when the user requests it. - Attempting to run nvidia-settings as root it cannot write to that configuration file. + The tools needs to be able to write /etc/X11/xorg.conf when root + requests it. I tracked this down to a missing permission on /usr/share/screen- - resolution-extra/nvidia-polkit which was 644 on my system. + resolution-extra/nvidia-polkit which had permissions 644 on my system. The following change fixed this for me: chmod u+x /usr/share/screen-resolution-extra/nvidia-polkit I found many users online with similar issues in forums. Please update the package to implement the equivalent and close this. FYI end user configuration without root has improved significantly since - 16.04 such that it would be reasonable in my
[Ubuntu-x-swat] [Bug 1998950] Re: GPU hang on Alder Lake laptop
I don't see this happening anymore as of the release of linux- image-5.19.0-28-generic. Neither the -28 nor the -29 kernel seem to cause this to happen anymore, so I suspect this can probably be closed. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1998950 Title: GPU hang on Alder Lake laptop To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1998950/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1625119] Re: Nvidia settings can't be saved
16.04 is old at this point. I had a similar problem with Ubuntu 22.04, which should be currently supported, and found a solution on that release. I am using a fully patched system with nvidia-settings 510.47.03-0ubuntu1. It needs to be able to write /etc/X11/xorg.conf when running as root when the user requests it. Attempting to run nvidia-settings as root it cannot write to that configuration file. The following change fixed this for me: chmod u+x /usr/share/screen-resolution-extra/nvidia-polkit Please update the package to implement the equivalent and close this. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1625119 Title: Nvidia settings can't be saved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1625119/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1625119] Re: Nvidia settings can't be saved
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-settings (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1625119 Title: Nvidia settings can't be saved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1625119/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1971712] Re: Add support for Intel DG2
and is there now -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1971712 Title: Add support for Intel DG2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971712/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1991761] Re: Backport packages for 22.04.2 HWE stack
** Changed in: spirv-llvm-translator-14 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1991761 Title: Backport packages for 22.04.2 HWE stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1991761/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2002609] Re: [SRU] Disable pressure for not detecting contact size
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/2002609 Title: [SRU] Disable pressure for not detecting contact size To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2002609/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
