[Ubuntu-x-swat] [Bug 1993621] Re: Force update keyboard LEDs after calling EnableDevice to fix its hardware state after VT switching
This issue is also verified on 2:21.1.4-2ubuntu1.6 on kinetic ** Tags removed: verification-needed-kinetic ** Tags added: verification-done-kinetic -- 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
This issue is verified on 2:21.1.3-2ubuntu2.8 on jammy, that switching from text terminal to X session the keyboard LED status would recover. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- 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
** 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 onto an GNOME session (KDE Kwin worked this issue around) + 1. Log onto an GNOME Xorg 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 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). -- 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 1993621] Re: Switching virtual terminals [Ctrl-Alt-F1 - F7] to a X session turns off keyboard LEDs
Related MP for this issue, however the MP does not fix the issue, and we are proposing a similar patch: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/764 ** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1234 https://gitlab.freedesktop.org/xorg/xserver/-/issues/1234 ** Also affects: xorg-server via https://gitlab.freedesktop.org/xorg/xserver/-/issues/1234 Importance: Unknown Status: Unknown -- 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: Switching virtual terminals [Ctrl-Alt-F1 - F7] to a X session turns off keyboard LEDs 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] [NEW] Switching virtual terminals [Ctrl-Alt-F1 - F7] to a X session turns off keyboard LEDs
Public bug reported: 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). ** Affects: oem-priority Importance: Undecided Status: New ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1991265 somerville ** Description changed: - Hi, + 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), that - 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). ** Tags added: oem-priority originate-from-1991265 somerville -- 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: Switching virtual terminals [Ctrl-Alt-F1 - F7] to a X session turns off keyboard LEDs 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 1990456] Re: xorg reports bogus 1600x1024 resolution
Before installing xorg-server 2:21.1.3-2ubuntu2.2, xrandr gives 1600x1024 resolution which was not able to use on the test unit. After upgrading to xorg-server 2:21.1.3-2ubuntu2.2 from jammy-proposed, that resolution is removed from xrandr. ubuntu@ubuntu:~$ DISPLAY=:0 xrandr Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 16384 x 16384 eDP-1 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 344mm x 215mm 1920x1200 60.03*+ 59.8859.95 1920x1080 60.0159.9759.9659.93 1600x1200 60.00 1680x1050 59.9559.88 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1280x800 59.9959.9759.8159.91 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 700x525 59.98 800x450 59.9559.82 640x512 60.02 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 640x400 59.8859.98 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1 disconnected (normal left inverted right x axis y axis) DP-1 disconnected (normal left inverted right x axis y axis) DP-2 disconnected (normal left inverted right x axis y axis) ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- 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/1990456 Title: xorg reports bogus 1600x1024 resolution To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990456/+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 1990456] Re: xorg reports bogus 1600x1024 resolution
** Description changed: xorg reports 1600x1024 bogus resolution [ Impact ] - * User of NVIDIA GPU is able to switch to 1600x1024 resolution but + * User of NVIDIA GPU is able to switch to 1600x1024 resolution but cannot display anything under the resolution [ Test Plan ] - 1. Find a test unit with NVIDIA GPU, or anything but using Xorg mode to enter desktop + 1. Find a test unit with NVIDIA GPU, or anything but use Xorg mode to enter the desktop 2. Type `xrandr` in terminal Expected: The resolution 1600x1024 should not appear if the display does not support it. Actual: The resolution 1600x1024 appears. [ Where problems could occur ] - * Lack of extra modes that the display might actually support. + * Lack of extra modes that the display might actually support. -- 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/1990456 Title: xorg reports bogus 1600x1024 resolution To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990456/+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 1990456] [NEW] xorg reports bogus 1600x1024 resolution
Public bug reported: xorg reports 1600x1024 bogus resolution [ Impact ] * User of NVIDIA GPU is able to switch to 1600x1024 resolution but cannot display anything under the resolution [ Test Plan ] 1. Find a test unit with NVIDIA GPU, or anything but using Xorg mode to enter desktop 2. Type `xrandr` in terminal Expected: The resolution 1600x1024 should not appear if the display does not support it. Actual: The resolution 1600x1024 appears. [ Where problems could occur ] * Lack of extra modes that the display might actually support. ** Affects: oem-priority Importance: Undecided Status: New ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1974165 somerville ** Tags added: oem-priority originate-from-1974165 somerville -- 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/1990456 Title: xorg reports bogus 1600x1024 resolution To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990456/+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 1176803] Re: fglrx-* shouldn't conflict with nvidia-*
*** This bug is a duplicate of bug 1071389 *** https://bugs.launchpad.net/bugs/1071389 ** This bug has been marked a duplicate of bug 1071389 nvidia-current conflicts with fglrx (both cards present) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1176803 Title: fglrx-* shouldn't conflict with nvidia-* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fglrx-installer/+bug/1176803/+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
