[Ubuntu-x-swat] [Bug 2006744] Re: libgl1-mesa-dri 22.3.4-1ubuntu1 vs libgl1-amber-dri 21.3.7-0ubuntu1 file conflict
"more than half a year ago" seems a bit too much, as the gallium i915 was enabled in Debian in December, and was uploaded to lunar two weeks ago.. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa-amber in Ubuntu. https://bugs.launchpad.net/bugs/2006744 Title: libgl1-mesa-dri 22.3.4-1ubuntu1 vs libgl1-amber-dri 21.3.7-0ubuntu1 file conflict To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa-amber/+bug/2006744/+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 1993621] Re: Force update keyboard LEDs after calling EnableDevice to fix its hardware state after VT switching
** Also affects: xorg-server (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1993621 Title: Force update keyboard LEDs after calling EnableDevice to fix its hardware state after VT switching To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1993621/+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 1993621] Re: Force update keyboard LEDs after calling EnableDevice to fix its hardware state after VT switching
** Changed in: xorg-server (Ubuntu) Assignee: (unassigned) => Yao Wei (medicalwei) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1993621 Title: Force update keyboard LEDs after calling EnableDevice to fix its hardware state after VT switching To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1993621/+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 1993621] Re: Force update keyboard LEDs after calling EnableDevice to fix its hardware state after VT switching
** Patch added: "xorg-server_21.1.4-2ubuntu1.6.debdiff" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1993621/+attachment/5648816/+files/xorg-server_21.1.4-2ubuntu1.6.debdiff -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1993621 Title: Force update keyboard LEDs after calling EnableDevice to fix its hardware state after VT switching To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1993621/+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 1993621] Re: Force update keyboard LEDs after calling EnableDevice to fix its hardware state after VT switching
** Patch added: "xorg-server_21.1.3-2ubuntu2.8.debdiff" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1993621/+attachment/5648799/+files/xorg-server_21.1.3-2ubuntu2.8.debdiff ** Patch removed: "xorg-server_21.1.3-2ubuntu2.8.debdiff" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1993621/+attachment/5648795/+files/xorg-server_21.1.3-2ubuntu2.8.debdiff -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1993621 Title: Force update keyboard LEDs after calling EnableDevice to fix its hardware state after VT switching To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1993621/+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 1993621] Re: Force update keyboard LEDs after calling EnableDevice to fix its state after VT switching
Attached is the debdiff for the following Merge Request merged upstream: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/1070 Please review ** Description changed: + [ Impact ] + + * This change will force update keyboard LED status after calling + EnableDevice, in order to resolve LED status not syncing after switching + VT to a X session. + + * This also fixes the issue with NVIDIA driver and Xorg, that after + resuming from suspend the keyboard LED is always off. + + [ Test Plan ] + + 1. Log on a X session desktop (GNOME Xorg for example) + + 2. Turn on NumLock on the keyboard + + 3. Use Ctrl-Alt-F3 to switch to a text console, then Ctrl-Alt-F2 to + switch back to desktop + + NumLock LED should be on after switching back to the desktop + + [ Where problems could occur ] + + * The changes are to push status to the device when enabling it + regardless of actual keyboard state change, therefore switching between + VTs and adding/removing keyboard/mouse/xinput devices should be affected + by this change. + + [ Original Report ] + Switching virtual terminals [Ctrl-Alt-F1 - F7] to a X session turns off keyboard LEDs. This issue is reproducible on 2:21.1.3-2ubuntu2.1 (on 22.04) To reproduce: 1. Log on a X session desktop (GNOME Xorg for example) 2. Turn on NumLock 3. Use Ctrl-Alt-F3 to switch to a text console, then Ctrl-Alt-F2 to switch back to desktop Expected: NumLock LED should be on Actual: NumLock LED is off, but functions like NumLock is on. If NumLock is pressed the LED turns off as well as the function. If CapsLock is pressed the LED states sync back (LED turns back on). ** Description changed: [ Impact ] - * This change will force update keyboard LED status after calling + * This change will force update keyboard LED status after calling EnableDevice, in order to resolve LED status not syncing after switching VT to a X session. - * This also fixes the issue with NVIDIA driver and Xorg, that after + * This also fixes the issue with NVIDIA driver and Xorg, that after resuming from suspend the keyboard LED is always off. [ Test Plan ] - 1. Log on a X session desktop (GNOME Xorg for example) + 1. Log onto an GNOME session (KDE Kwin worked this issue around) 2. Turn on NumLock on the keyboard 3. Use Ctrl-Alt-F3 to switch to a text console, then Ctrl-Alt-F2 to switch back to desktop NumLock LED should be on after switching back to the desktop [ Where problems could occur ] - * The changes are to push status to the device when enabling it + * The changes are to push status to the device when enabling it regardless of actual keyboard state change, therefore switching between VTs and adding/removing keyboard/mouse/xinput devices should be affected by this change. [ Original Report ] Switching virtual terminals [Ctrl-Alt-F1 - F7] to a X session turns off keyboard LEDs. This issue is reproducible on 2:21.1.3-2ubuntu2.1 (on 22.04) To reproduce: 1. Log on a X session desktop (GNOME Xorg for example) 2. Turn on NumLock 3. Use Ctrl-Alt-F3 to switch to a text console, then Ctrl-Alt-F2 to switch back to desktop Expected: NumLock LED should be on Actual: NumLock LED is off, but functions like NumLock is on. If NumLock is pressed the LED turns off as well as the function. If CapsLock is pressed the LED states sync back (LED turns back on). ** Patch added: "xorg-server_21.1.3-2ubuntu2.8.debdiff" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1993621/+attachment/5648795/+files/xorg-server_21.1.3-2ubuntu2.8.debdiff ** Summary changed: - Force update keyboard LEDs after calling EnableDevice to fix its state after VT switching + Force update keyboard LEDs after calling EnableDevice to fix its hardware state after VT switching -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1993621 Title: Force update keyboard LEDs after calling EnableDevice to fix its hardware state after VT switching To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1993621/+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 1993621] Re: Force update keyboard LEDs after calling EnableDevice to fix its state after VT switching
** Summary changed: - Switching virtual terminals [Ctrl-Alt-F1 - F7] to a X session turns off keyboard LEDs + Force update keyboard LEDs after calling EnableDevice to fix its state after VT switching -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1993621 Title: Force update keyboard LEDs after calling EnableDevice to fix its state after VT switching To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1993621/+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 2006744] Re: libgl1-mesa-dri 22.3.4-1ubuntu1 vs libgl1-amber-dri 21.3.7-0ubuntu1 file conflict
I just ran into this bug today, and a Google search shows that it has been affecting many distros based on Ubuntu starting more than half year ago and many users complained about it without real solutions. Hope it can be fixed ASAP. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa-amber in Ubuntu. https://bugs.launchpad.net/bugs/2006744 Title: libgl1-mesa-dri 22.3.4-1ubuntu1 vs libgl1-amber-dri 21.3.7-0ubuntu1 file conflict To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa-amber/+bug/2006744/+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 2006744] Re: libgl1-mesa-dri 22.3.4-1ubuntu1 vs libgl1-amber-dri 21.3.7-0ubuntu1 file conflict
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa-amber (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa-amber in Ubuntu. https://bugs.launchpad.net/bugs/2006744 Title: libgl1-mesa-dri 22.3.4-1ubuntu1 vs libgl1-amber-dri 21.3.7-0ubuntu1 file conflict To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa-amber/+bug/2006744/+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 2006695] Re: nvidia-graphics-drivers-390 fails to build with kernel 6.1 in lunar
@Simon, those were old releases failing. I have just uploaded the correct releases, so that they are in sync with the other Ubuntu releases. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2006695 Title: nvidia-graphics-drivers-390 fails to build with kernel 6.1 in lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2006695/+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 2006695] Re: nvidia-graphics-drivers-390 fails to build with kernel 6.1 in lunar
I'm seeing the exact same error on 450-server, 470-server, 510-server and 515-server in the glibc autopkgtests https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/amd64/n/nvidia-graphics- drivers-450-server/20230217_153300_3ba46@/log.gz There's also other failures on 470, 510 and 515 that might or might not be related? https://people.canonical.com/~ubuntu-archive/proposed- migration/update_excuses.html#glibc (you might have to scroll down a bit :) ) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2006695 Title: nvidia-graphics-drivers-390 fails to build with kernel 6.1 in lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2006695/+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 2007830] Re: Display issue after boot - secondary screen not working since last kernel upgrade
Thanks for the bug report. It looks like Nvidia is your primary GPU and that driver is working fine. If you have any monitors not working then they might be connected to the Intel GPU. Your Intel graphics driver is reporting some unusual kernel errors I've never seen before but they sound related. It also looks like your BIOS has hidden/disabled the Intel GPU completely. So this is really only a bug if the secondary monitor is connected to the Nvidia GPU. Please run these commands: grep . /sys/class/drm/*/status > drmconn.txt journalctl -b0 > journal.txt and attach the resulting text files here. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Tags added: i915 multigpu nvidia -- 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/2007830 Title: Display issue after boot - secondary screen not working since last kernel upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2007830/+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 2007830] [NEW] Display issue after boot - secondary screen not working since last kernel upgrade
Public bug reported: Display on the second screen does not work since last kernel upgrade. It works using the previous one. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17 Uname: Linux 5.19.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 525.78.01 Mon Dec 26 05:58:42 UTC 2022 GCC version: gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1) ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 20 10:16:57 2023 DistUpgraded: 2022-10-21 09:45:54,530 DEBUG icon theme changed, re-reading DistroCodename: kinetic DistroVariant: ubuntu DkmsStatus: nvidia/525.78.01, 5.19.0-31-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Dell HD Graphics 630 [1028:0774] NVIDIA Corporation GP104BM [GeForce GTX 1080 Mobile] [10de:1be0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GeForce GTX 1080 Max-Q [1028:07c0] InstallationDate: Installed on 2022-10-12 (130 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Alienware Alienware 15 R3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-31-generic root=/dev/mapper/vgubuntu-root ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to kinetic on 2022-10-21 (122 days ago) dmi.bios.date: 07/21/2020 dmi.bios.release: 1.10 dmi.bios.vendor: Alienware dmi.bios.version: 1.10.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.10.0:bd07/21/2020:br1.10:svnAlienware:pnAlienware15R3:pvr1.10.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:sku0774: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.sku: 0774 dmi.product.version: 1.10.0 dmi.sys.vendor: Alienware version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.5 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 kinetic ubuntu -- 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/2007830 Title: Display issue after boot - secondary screen not working since last kernel upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2007830/+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
