** Changed in: oem-priority
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/2087831
Title:
[SRU] On a laptop with NVIDIA graphics and touch
I filed a Salsa MR for noble (as mutter in noble does not have SRU
exception), and we should be waiting for next point release of GNOME 47
for fixing the issue in plucky:
https://salsa.debian.org/gnome-team/mutter/-/merge_requests/138
** Description changed:
+ [ Impact ]
+
+ * When user using
** Summary changed:
- On a laptop with NVIDIA graphics and touchscreen, touchscreen gets disabled
after resume from suspend in Xorg session
+ [SRU] On a laptop with NVIDIA graphics and touchscreen, touchscreen gets
disabled after resume from suspend in Xorg session
--
You received this bug not
** Tags added: jira-somerville-1469 oem-priority
--
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/1853094
Title:
[modeset] Screen tearing when using multiple monitors
To manage notificatio
MR proposed: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4188
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/2087831
Title:
On a laptop with NVIDIA graphics and
** Changed in: mutter (Ubuntu)
Status: New => In Progress
** Changed in: oem-priority
Status: New => In Progress
** Changed in: oem-priority
Assignee: (unassigned) => Yao Wei (medicalwei)
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Yao Wei
** No longer affects: nvidia-graphics-drivers-550 (Ubuntu)
** No longer affects: gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/2087831
Title:
On a l
** Changed in: xserver-xorg-input-libinput (Ubuntu)
Status: New => Invalid
** Changed in: nvidia-graphics-drivers-550 (Ubuntu)
Status: New => Invalid
** Changed in: gnome-shell (Ubuntu)
Status: New => Invalid
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3834
Note about enabling/disabling input on Mutter side, it is under
`mutter/src/backends/meta-input-
mapper.c:input_mapper_power_save_mode_changed_cb`
I will start tracing from there and see whether there's changes between
GNOME versions.
--
You received this bug notification because you are a membe
On Ubuntu 23.10 VNP, could you confirm that NVIDIA driver is installed in the
system?
They might be running on Nouveau especially the apt repository for 23.10 is now
unavailable.
I can reproduce the issue on 23.10 after changing sources to old-
releases.ubuntu.com, then install NVIDIA driver usi
This issue can be linked to Bug #1952823 for NVIDIA driver, except the
different version.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/2087831
Title:
touchscreen has no
** Also affects: nvidia-graphics-drivers-550 (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- touchscreen has no response after resume from suspend in Xorg session
+ On a laptop with NVIDIA graphics and touchscreen, touchscreen gets disabled
after resume from suspend in
We found out that the touchscreen is disabled by libinput after suspend/resume:
Check the following properties (the touchscreen is id=10 for our DUT, see
`xinput list`)
before suspend:
$ xinput list-props 10
Device 'CUST:00 0EEF:C003':
[...snip...]
libinput Send Events Mode En
** Changed in: oem-priority
Status: Fix Committed => Fix Released
--
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 n
Trying to test with vanilla Xorg by stopping gdm3 and using Xorg by
itself:
0. Install xterm since we are going to use it later.
1. Switch to tty3 by using Ctrl-Alt-F3
sudo systemctl stop gdm3
sudo Xorg &
DISPLAY=:0 xterm
2. Switch to blank Xorg session using Ctrl-Alt-F1, then in xterm run xev
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
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
** 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 sus
** 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 af
** 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-s
** 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/xo
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 resolv
** 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 subscribe
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/12
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
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
** 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.
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
*** 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 subsc
29 matches
Mail list logo
