This sounds like a per-application bug, but also something we would like
gnome-font-viewer to handle.
** Changed in: xorg (Ubuntu)
Importance: Undecided => Low
** Summary changed:
- Choosing font
+ Apps can't handle tens of thousands of fonts installed at once
** Package changed: xorg
This bug is closed. But also please refrain from reporting multiple
different issues at the same time.
The current problem with a blank window is being tracked in:
https://github.com/canonical/ubuntu-desktop-installer/issues/2418
For everything else, please open new bugs.
** Bug watch added:
mesa (24.0.2-1ubuntu1) noble; urgency=medium
* Merge from Debian.
* radeon-fix-gnome-shell-crash.diff: Fix a regression crashing
gnome-shell. (LP: #2054851)
-- Timo Aaltonen Thu, 29 Feb 2024 09:40:21 +0200
** Changed in: mesa (Ubuntu)
Status: Confirmed => Fix Committed
**
Bug 2016925 suggests the problem went away in Ubuntu 23.10
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => New
** Tags added: amdgpu
** Summary changed:
- firefox screen corruption on Athlon 200GE after fresh installation of 22.04.4
+ [amdgpu] Firefox screen corruption on
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 2055351
When reporting bugs in the future please use apport by using 'ubuntu-
The bucket is new for 2:23.2.0-1ubuntu0.4 anyway. If the crash also
happened before then and just landed in a different bucket then it
wouldn't be a regression-update.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xwayland in Ubuntu.
The crash is:
https://errors.ubuntu.com/oops/db625975-d614-11ee-ba81-fa163e171f02
which redirects to:
https://errors.ubuntu.com/bucket/?id=failed%3A/usr/bin/Xwayland%3A6%3A/usr/lib/x86_64-linux-
gnu/libc.so.6%2B1c8e6%3A/usr/lib/x86_64-linux-
Please don't attach crash files to bugs because it's a security risk for
yourself. Instead run:
ubuntu-bug /var/crash/YOURFILE.crash
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Invalid
** Attachment removed: "_usr_bin_nautilus.1000.crash"
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
Thanks for the bug report.
Each time you experience a failed boot followed by a successful boot
please run:
journalctl -b-1 > failedboot.txt
And each time you experience a slow boot please run:
journalctl -b0 > slowboot.txt
and attach the resulting text files here.
** Summary changed:
There are lots of amdgpu errors in your system log, so let's start
there.
** Tags added: amdgpu
** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
** Tags added: bionic jammy mantic noble
** Summary changed:
- Xorg crashed with assertion failure (usually in a VM) at [privates.h:121/122:
dixGetPrivateAddr: Assertion `key->initialized' failed] and call stack comes
from DRIMoveBuffersHelper
+ Xorg crashed with assertion failure (usually in
*** This bug is a duplicate of bug 1861609 ***
https://bugs.launchpad.net/bugs/1861609
** This bug has been marked a duplicate of bug 1861609
Xorg crashed with assertion failure (usually in a VM) at
[privates.h:121/122: dixGetPrivateAddr: Assertion `key->initialized' failed]
and call
*** This bug is a duplicate of bug 1861609 ***
https://bugs.launchpad.net/bugs/1861609
** This bug has been marked a duplicate of bug 1861609
Xorg crashed with assertion failure (usually in a VM) at
[privates.h:121/122: dixGetPrivateAddr: Assertion `key->initialized' failed]
and call
CurrentDmesg.txt shows the Nvidia kernel driver crashing, which is
probably not helpful. But also...
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these
** Summary changed:
- gnome-shell crashed with SIGSEGV in radeon_bo_reference()
+ gnome-shell (and Xorg) crashes with SIGSEGV in radeon_bo_reference()
** Tags added: rls-nn-incoming
** Summary changed:
- gnome-shell (and Xorg) crashes with SIGSEGV in radeon_bo_reference()
+ [radeon]
*** This bug is a duplicate of bug 2054851 ***
https://bugs.launchpad.net/bugs/2054851
Yes the addresses in your crash match those of bug 2054851.
[ 149.655] (EE) 2: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
(radeon_drm_winsys_create+0x27e5) [0x7a53429ea2e5]
[ 149.658] (EE) 3:
*** This bug is a duplicate of bug 2054851 ***
https://bugs.launchpad.net/bugs/2054851
The log in comment #1 shows Xorg crashing in radeonsi_dri.so, so this
might be bug 2054851. But also...
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like
On another occasion your shell seems to have been killed without
crashing:
Feb 24 14:34:17 systemd[3625]: org.gnome.Shell@wayland.service: Main
process exited, code=killed, status=9/KILL
This can happen as a result of the real-time thread used in mutter. To
work around it I think you can just
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
** Package changed: xorg (Ubuntu) => gnome-remote-desktop (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/2054859
Title:
VNC connection issues with 22.04
To manage notifications about
*** This bug is a duplicate of bug 1922047 ***
https://bugs.launchpad.net/bugs/1922047
Yes input is scaled with the display scale in Wayland, but not Xorg.
That's a feature, but also annoying at times. I think this issue has
been logged before but I can't find the right bug, only bug 1902436.
*** This bug is a duplicate of bug 2054121 ***
https://bugs.launchpad.net/bugs/2054121
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2054121, so it is being marked as such. Please
Tracking upstream in:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/10613
** Information type changed from Private to Public
** Summary changed:
- gnome-shell crashed with SIGSEGV
+ gnome-shell crashed with SIGSEGV in radeon_bo_reference()
** Package changed: gnome-shell (Ubuntu) => mesa
*** This bug is a duplicate of bug 2054121 ***
https://bugs.launchpad.net/bugs/2054121
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2054121, so it is being marked as such. Please
Next time the problem happens please:
1. Reboot.
2. Run:
journalctl -b-1 > prevboot.txt
3. Attach the resulting text file here.
** Summary changed:
- Xorg freeze
+ Xorg freeze: i915 flips and commits are timing out
** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu)
** Changed
Same for Weston 13.0. But since it's Nvidia asking, maybe we can help
some other way?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/2053235
Title:
Upgrade libwayland to 1.22.0
To manage
*** This bug is a duplicate of bug 2037015 ***
https://bugs.launchpad.net/bugs/2037015
If it's just appeared in 22.04.4 then Mesa might be to blame, but this looks
more likely:
https://launchpad.net/ubuntu/+source/webkit2gtk/2.42.5-0ubuntu0.22.04.2
--
You received this bug notification
Same issue in Yelp (the Help app) when in Xorg sessions. So I think this
is a webkit2gtk bug that only manifests on Xorg (like our installer/live
sessions).
Also I have removed the series targets because they were getting
cluttered and likely targeting the wrong package anyway.
** Also affects:
*** This bug is a duplicate of bug 2037015 ***
https://bugs.launchpad.net/bugs/2037015
** This bug has been marked a duplicate of bug 2037015
Screen corruption of slides during install on Raspberry Pi 4
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Maybe it's Mesa's fault. Yelp crashes in:
??? () at /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so
??? () at /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so
??? () at /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so
??? () at /lib/aarch64-linux-gnu/libgbm.so.1
??? () at
Thanks for your testing.
** No longer affects: xserver-xorg-video-amdgpu (Ubuntu)
** Summary changed:
- System starts, but monitor on HDMI has no signal in 6.5 (but 6.2 works)
+ [amdgpu] No signal on one monitor in kernel 6.5 (but 6.2 works)
** Changed in: linux-hwe-6.5 (Ubuntu)
Status:
** Package changed: xorg (Ubuntu) => gnome-control-center (Ubuntu)
** Summary changed:
- GNOME setting GUI bug
+ Sound settings flicker heavily when choosing output
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Can you test some other desktop environment like GNOME? And try Wayland?
At the moment all I can see is that Xorg thinks both monitors are
working. So the bug may be Xorg, the amdgpu Xorg driver, XFCE, or the
kernel.
** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu)
**
I wonder if the Belkin docking station has enough bandwidth to drive
multiple monitors simultaneously. Have you tried unplugging everything
from the dock and just plugging in a monitor to the DisplayPort alone?
Also next time the bug occurs, please run:
journalctl -b0 > journal.txt
and attach
Thanks for the bug report. I can't yet see any cause for the freezes.
Next time it happens please:
1. Note the exact time and date of the freeze.
2. Reboot.
3. Run: journalctl -b-1 > prevboot.txt
4. Attach the resulting text file here along with a note telling us the
exact time and date of the
*** This bug is a duplicate of bug 2054221 ***
https://bugs.launchpad.net/bugs/2054221
** This bug has been marked a duplicate of bug 2054221
GNOME setting GUI bug
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
** Summary changed:
- Upgrade libwayland on ubuntu 22.04.3 LTS
+ Upgrade libwayland to 1.22.0
** Also affects: wayland (Ubuntu Noble)
Importance: Undecided
Status: Invalid
** Also affects: wayland (Ubuntu Mantic)
Importance: Undecided
Status: New
** Changed in: wayland
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/2053235
Title:
Upgrade libwayland on ubuntu 22.04.3 LTS
To manage notifications about this bug go to:
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-535
(Ubuntu)
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Second (external) monitor not active after screen lock
+ [nvidia] Second (external) monitor not active after screen lock
** Package changed: xserver-xorg-video-nouveau (Ubuntu) => mutter
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-nouveau in Ubuntu.
https://bugs.launchpad.net/bugs/2048797
Title:
Screen Sharing no longer works
Thanks for the bug report. Please start by removing any local
extensions:
cd ~/.local/share/gnome-shell/
rm -rf extensions
and then log in again.
If the problem still happens then while it is happening please run:
journalctl -b0 > journal.txt
and attach the resulting text file here.
Your "13th Gen Intel(R) Core(TM) i7-13700" is too new for such an old
Linux kernel to support the graphics outputs correctly. Please install a
newer Ubuntu release such as 22.04.3:
https://ubuntu.com/download/desktop
** Package changed: xorg (Ubuntu) => linux-hwe-5.15 (Ubuntu)
** Also affects:
* What web browser are you using?
* What is the name of the process using the most CPU?
* Maybe unrelated, but your '88x2bu' kernel driver (for USB wifi) seems
to be crashing.
* Please be sure to only use the 'Additional Drivers' app to install
Nvidia drivers because it looks like you might
I think the crossed circle means you're hitting a special key on the
keyboard that is assigned to some on-screen display (OSD) function.
Please try to identify which key or key combo is causing it. You might
also be able to avoid the problem by enabling or disabling the
keyboard's Fn-lock (which
Please check that this isn't being caused by local extensions. You can
remove them by running:
cd ~/.local/share/gnome-shell/
rm -rf extensions
and then log in again. If the problem persists after that then please
run:
gnome-extensions list --enabled > extensions.txt
and attach the
It looks like the 'modesetting' Xorg driver is at fault, if we trust the
log message suggesting /dev/dri/card0 exists. Please run:
sudo apt install drm-info
sudo drm_info > drminfo.txt
and then attach the resulting text file here.
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Tags added: amdgpu
** Tags added: flicker suspend-resume
** Summary changed:
- After screen turns off and you turn it back on, weird corruption
+ [amdgpu] After screen turns off and you turn it back on, weird corruption
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received
The "ppa10" version of that package does not appear to be an Ubuntu
release so please report the problem to the PPA owner if it only occurs
with that version.
** Tags added: jammy
** Changed in: xorg-server (Ubuntu)
Status: New => Invalid
--
You received this bug notification because
Thanks for the bug report. It appears the graphics driver and Xorg are
working correctly here. And certainly I would not expect all modern
games to maintain 60 FPS on the integrated GPU of an Intel i3-1115G4.
As for the blurry HDMI output, the Samsung un32t4300 is limited to
1366x768 so a little
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
--
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/2051694
Title:
Regression: Kubuntu 22.04 LTS overrides Xorg.conf-specified
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
Please check to see if the kernel is getting the button events:
sudo apt install evtest
sudo evtest
** Package changed: xorg (Ubuntu) => linux-raspi (Ubuntu)
** Changed in: linux-raspi (Ubuntu)
Status: New => Incomplete
** Package changed: linux-raspi (Ubuntu) => linux (Ubuntu)
**
> Display resolution stuck at 800x600 after using nomodeset in grub.
> But my Dell monitor has 1600x900 resolution.
This is correct behaviour. "nomodeset" means to disable the graphics
driver and to disable high resolution support.
** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu)
**
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
If you already had multiple keyboards associated with the machine then
this sounds like bug 108. Please try removing all but one keyboard
from the system.
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Status: New => Incomplete
** Summary changed:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
*** This bug is a duplicate of bug 2050954 ***
https://bugs.launchpad.net/bugs/2050954
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2050954, so it is being marked as such. Please
Thanks for the bug report. Next time the problem happens please:
1. Reboot.
2. Run:
journalctl -b-1 > prevboot.txt
3. Attach the resulting text file here.
** Summary changed:
- Xorg freeze
+ consistently fails to resume from suspend
** Package changed: xorg (Ubuntu) => ubuntu
**
** Summary changed:
- brightness
+ [HP EliteBook 8560w] Can't change screen brightness
** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
If it's software at all then this would be a kernel bug. But I suspect
the issue is more likely hardware since 1920x1080 @60Hz is pushing the
limits of analog VGA. Anything less than a perfect cable with perfect
connections and I'd expect display glitches like this.
Personally I'd recommend
** Summary changed:
- Can't change screen brightness
+ [HP Victus 15-fb0xxx] Can't change screen brightness
** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
** Summary changed:
- display backlight
+ [Acer eMachines D725] Display backlight
** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
I can't seem to reproduce any such issue with 2024-01-17 here.
Please log a new bug, although it might be bug 2049617 as mentioned in
https://discourse.ubuntu.com/t/help-with-edubuntu-desktop-
installer/41683
--
You received this bug notification because you are a member of Ubuntu-X,
which is
Thanks for the bug report. It looks like the i915 kernel graphics driver
is crashing a lot, which may or may not be related. Please run these
commands in a Terminal:
sudo apt install mesa-utils
glxinfo > glxinfo.txt
and attach the resulting text file here.
** Package changed: xorg (Ubuntu)
Thanks for the bug report. It appears you no longer have an nvidia
kernel driver for the current kernel version. I'm also not sure if such
a newer kernel can be supported by the old nvidia 390 driver.
This might just be bug 1975650 so please try reinstalling the driver
using the 'Additional
Thanks for the bug report. I've watched the attached screencast a few
times and can't see any artifacts in it. This is unsurprising given how
screen recording works. You will probably need to take a video of the
screen externally, like with a phone.
** Summary changed:
- screen artifacts
Thanks, yes any failure to install now needs a separate bug report.
--
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/2043915
Title:
Booting into live session results in try/install page white
Confirmed fix released in https://cdimage.ubuntu.com/daily-
live/20240116/
--
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/2043915
Title:
Booting into live session results in try/install page
** Changed in: mesa (Ubuntu)
Status: Fix Committed => Fix Released
--
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/2043915
Title:
Booting into live session results in try/install page
Xorg itself doesn't paint anything, it will start with a black window.
So it's likely to be a Xubuntu bug. Since it can't be reproduced then
let's leave it Incomplete and it will close automatically after two
months of inactivity.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
This is being tracked upstream in:
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/158
** Bug watch added: gitlab.freedesktop.org/wayland/wayland-protocols/-/issues
#158
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/158
** Changed in: wayland (Ubuntu)
This appears to be a networking or server problem, so likely isn't a bug
we need to track here.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
** Tags added: amdgpu
** Summary changed:
- Video does not output to second monitor
+ [amdgpu] Video does not output to second monitor
** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
The version of Mesa installed: 24.0.0.20231114.1-2088~22.04 is not
supported or provided by Ubuntu. We cannot fix any bugs it causes.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Invalid
--
You received this bug notification because you are a member
See also bug 2049016.
--
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/1922414
Title:
Xorg scripts fail with "has_option: command not found"
To manage notifications about this bug go to:
** Summary changed:
- ssh-agent fails to start (has_option: command not found)
+ Xorg scripts fail with "has_option: command not found"
--
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/1922414
>From what I read of overnight discussions, it is believed that Mesa
23.3.3 has a fix. Looks like some kind of GLX protocol breakage happened
in 23.3.0?
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mesa (Ubuntu)
Status: New => Fix Committed
--
** Changed in: mesa (Ubuntu)
Status: Fix Committed => Fix Released
** Tags removed: fixed-in-mesa-23.3
** Tags added: fixed-in-mesa-23.3.0
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
Please report the bug at:
https://gitlab.gnome.org/GNOME/mutter/-/issues
** Package changed: xserver-xorg-input-libinput (Ubuntu) => mutter
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-libinput in Ubuntu.
** Summary changed:
- Screen crashes in a wierd way
+ [amdgpu] Screen crashes in a weird way
** Tags added: amdgpu
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
** No longer affects: xorg-server (Ubuntu)
--
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/2046224
Title:
[amdgpu] Resolutions lower than max results in corrupted screen
To manage
What is the make and model of the machine? It seems to identify itself
as "Default string".
** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu)
** Changed in: linux-hwe-6.2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
** Summary changed:
- Screen brightness
+ [Lenovo IdeaPad Z500] Screen brightness
** Summary changed:
- [Lenovo IdeaPad Z500] Screen brightness
+ [Lenovo IdeaPad Z500] Brightness of the screen is down to minimum and I can't
change it
** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu)
Only the kernel can crash that hard, so reassigning there.
** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (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/2047388
Title:
System
** Tags added: amdgpu
** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu)
** Summary changed:
- [drm] *ERROR* flip_done timed out
+ [amdgpu][drm] *ERROR* flip_done timed out
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in
Do you have an external monitor plugged in when the bug occurs?
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Tags added: hybrid i915 multigpu nvidia
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Indeed the kernel seems to be crashing in drm graphics code so I'd
recommend trying some newer kernels such as
https://kernel.ubuntu.com/mainline/?C=M;O=D
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Tags added: amdgpu dock multimonitor
--
You received this bug notification because
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
Does "screen is too bright" mean the backlight brightness can't be
adjusted?
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Please don't use xserver-xorg-video-intel because it's buggy and
deprecated. The default Xorg driver ('modesetting') is the correct
driver.
I will make this bug about the screen being too bright. If you want to
discuss "3rd class video quality" then please open a new bug for that...
** Summary
On laptop screens, non-max resolutions are faked. They should work
obviously, but it's up to the display server and kernel driver to fake
it properly.
Do you experience the same issue in a Wayland session?
** Tags added: amdgpu
** Summary changed:
- Resolutions lower than max results in
The attached files show that the kernel does indeed have an 'nvidia'
driver but it's not being used for some reason. And Xorg, as of Dec 11
at least, does not have any knowledge of an Nvidia card.
Please run:
lspci -k > lspci.txt
journalctl -b0 > journal.txt
and attach the resulting text
It doesn't look like you have a working Nvidia driver installed. Please
try using the 'Additional Drivers' app to install an Nvidia driver.
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
** Tags added: multimonitor
This is a feature of most terminals and editors. If you're typing then
they expect that hiding the mouse cursor is helpful to not cover any
text.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Invalid
--
You received this bug notification because you
PPAs are not supported, but also the 390 driver is not supported by any
Ubuntu release after 23.04 (which explains why you're using a PPA).
If you require Nvidia driver 390 then please stick to Ubuntu 22.04 where
it is formally supported until April 2032.
** No longer affects: xorg (Ubuntu)
**
It looks like kwin didn't crash until after the kernel errors started so
let's make this about the kernel errors.
** Summary changed:
- Graphics card driver crash
+ [A770] Graphics card driver crash
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Summary changed:
- [A770] Graphics card
101 - 200 of 9936 matches
Mail list logo
