"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/bu
** 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 Ubun
** 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 call
** 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
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 o
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/200674
@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.launc
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
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
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
No
13 matches
Mail list logo
