Thanks for the bug report. As far as I can tell, the system is trying to
use Xorg by default because Nvidia is the primary GPU(?), but the Nvidia
Xorg driver is not properly installed (according to the Xorg log it's
not present).
Please try using the 'Additional Drivers' app to reinstall an Nvidia
Thanks for the bug report. It looks like a poor HDMI connection so
please try a different cable.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Nvidia 560/565 are not supported on Ubuntu 24.04. Please try opening the
'Additional Drivers' app and install a supported Nvidia driver such as
535 or 550.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification b
** This bug is no longer a duplicate of bug 2083650
Windows blinks after return from display off
--
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/2086239
Title:
Display blinks after return from
*** This bug is a duplicate of bug 2083650 ***
https://bugs.launchpad.net/bugs/2083650
** This bug has been marked a duplicate of bug 2083650
Windows blinks after return from display off
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xor
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
an
** Summary changed:
- [Dell Inspiron 3505] touchscreen not working
+ [Dell Inspiron 3505] touchscreen not working in Xorg sessions
** No longer affects: linux (Ubuntu)
** Changed in: xserver-xorg-input-libinput (Ubuntu)
Status: Incomplete => New
--
You received this bug notification bec
Please try logging into a Wayland session using the menu button on the
login screen. It will be called either 'Ubuntu on Wayland' or just
'Ubuntu'. Does the touchscreen work in a Wayland session?
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New
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
an
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
an
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
an
It's worth noting the Nvidia driver isn't loading, or isn't installed
properly. But also that might not be related to this bug.
** Summary changed:
- my brightness control from the drop down menu on the top right section of the
screen does not reduce the brightness at all. screen is always at f
*** This bug is a duplicate of bug 1924689 ***
https://bugs.launchpad.net/bugs/1924689
Thanks for the bug report. It is a known limitation that Xorg sessions
cannot set different displays to different scaling factors.
As for "window freezes and creates graphical irregularites", that is bug
19
*** This bug is a duplicate of bug 2085750 ***
https://bugs.launchpad.net/bugs/2085750
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 2085750, so it is being marked as such. Please look
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
an
Please attach a screenshot of the problem so we can better understand
it.
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscrib
Please explain in more detail what kind of problem you are facing.
Ideally with screenshots or photos.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscrib
Assigning to the kernel because:
* It controls the backlight; and
* The attached logs show repeated kernel errors in i915.
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Summary changed:
- Screen turning on and off
+ [i915] Screen turning on and off
--
You received this bug notificat
Thanks for the bug report. Next time the problem happens, as soon as it
recovers please run:
journalctl -b0 > journal.txt
and attach the resulting text file here.
** Summary changed:
- Xorg freeze
+ Freeze
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
** Changed in: gnome-shell
** Package changed: xorg (Ubuntu) => kwin (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/2085519
Title:
Performance regression in KDE Plasma 6.1.5 after upgrading to Kubuntu
24.10
To
Please also try this as a workaround in /etc/environment:
MUTTER_DEBUG_KMS_THREAD_TYPE=user
and reboot.
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Status: New => Incomplete
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
Yo
The EDID issue is possibly unrelated.
gnome-shell gets SIGKILL'd if its realtime thread uses too much CPU
during startup. This may be mutter's fault like in bug 2077216, or it
may be due to an i915 bug alluded to above.
First we would like to know if the fix for bug 2077216 helps, so please
try 2
** Package changed: xorg (Ubuntu) => clamtk (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/2085395
Title:
Clam TK won't update
To manage notifications about this bug go to:
https://bug
** Package changed: xorg (Ubuntu) => gnome-shell-extension-appindicator
(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/2085020
Title:
Wrong tray icon size on Java Apps (Ubuntu 24.10 and
** Summary changed:
- Bildschirm bleibt schwarz/flackert im Vollbildmodus
+ [amdgpu] Bildschirm bleibt schwarz/flackert im Vollbildmodus
** Tags added: amdgpu black-screen
** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu)
** Also affects: kwin (Ubuntu)
Importance: Undec
** Package changed: xorg (Ubuntu) => kwin (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/2085019
Title:
Java apps that uses tray icon are broken in KDE (Ubuntu 24.10)
To manage notific
** Changed in: xdiagnose (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xdiagnose in Ubuntu.
https://bugs.launchpad.net/bugs/2084825
Title:
xdiagnose package failure
To manage notifications about thi
It appears xdiagnose is not a standard part of Ubuntu (not usually
installed). Do you have a log file showing the error?
** Package changed: xorg (Ubuntu) => xdiagnose (Ubuntu)
** Changed in: xdiagnose (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you a
This does not sound related to #2065081 and #2065122 because those seem
to be Nvidia Xorg driver bugs. You have neither Nvidia or Xorg here.
Please elaborate on what kind of problem you are experiencing.
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Changed in: mutter (Ubuntu)
Thanks. Those logs show kernel crashes in the i915 driver. But there's
still a chance it could be the Nvidia driver's fault.
Since you're using X11 there's actually no way gnome-shell/mutter could
cause a single display to freeze because X11 forces us to redraw them
all at the same time in a singl
Normally we would say this is a model-specific bug. But I've actually
seen it happen on two laptops of my own. In my case the screen
brightness becomes uncontrollable sometimes after suspend/resume.
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Also affects: gnome-settings-daemon (Ubun
Please report the issue upstream so that all the GNOME developers can see it:
https://gitlab.gnome.org/GNOME/mutter/-/issues
** Package changed: wayland (Ubuntu) => mutter (Ubuntu)
** Tags added: oracular regression-release
--
You received this bug notification because you are a member of Ubunt
Adding a gtk4 task because the same issue was reported in Nautilus too.
** Also affects: gtk4 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-560 in Ubuntu.
https://bug
Next time the problem occurs, please run:
journalctl -b0 > journal.txt
and attach the resulting text file here.
** Tags added: multimonitor nvidia
** Tags added: hybrid i915 multigpu
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Also affects: nvidia-graphics-drivers-550 (Ubuntu)
Are you sure you're seeing the bug in Nautilus? Or is it just the shell?
Either way I would like to group this with bug 1876632.
** Package changed: xorg (Ubuntu) => nautilus (Ubuntu)
** Changed in: nautilus (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because
** Summary changed:
- [nvidia] Corrupted/missing shell textures when switching users, switching VTs
or resuming from suspend
+ [nvidia] Corrupted/missing textures when switching users, switching VTs or
resuming from suspend
--
You received this bug notification because you are a member of Ubun
** 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/2084357
Title:
Flashing "Could not switch the monitor configuration" on GUI start
To manage noti
** Package changed: xorg (Ubuntu) => kwin (Ubuntu)
** Summary changed:
- Xorg freeze
+ System hangs after login with plasma wayland session
--
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/2084375
*** This bug is a duplicate of bug 1971434 ***
https://bugs.launchpad.net/bugs/1971434
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 1971434, so it is being marked as such. Please look
** Package changed: xserver-xorg-video-vmware (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 xserver-xorg-video-vmware in Ubuntu.
https://bugs.launchpad.net/bugs/2084090
Ti
** No longer affects: xserver-xorg-input-libinput (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-vmware in Ubuntu.
https://bugs.launchpad.net/bugs/2084090
Title:
XWarpPointer doesn't work in virtual machines (anymo
** Package changed: xorg-server (Ubuntu) => xserver-xorg-video-vmware
(Ubuntu)
** Changed in: xserver-xorg-video-vmware (Ubuntu)
Status: Incomplete => New
** No longer affects: xorg (Ubuntu)
** No longer affects: libx11 (Ubuntu)
** Also affects: xserver-xorg-input-libinput (Ubuntu)
Im
Relative mode sounds correct. Did it fix the bug?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/2084090
Title:
XWarpPointer doesn't work on Ubuntu 24.04 GNOME X11
To manage notifications abo
Please remove both 'QEMU QEMU USB Tablet' and 'spice vdagent tablet'
from the virtual machine and try again.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/2084090
Title:
XWarpPointer doesn't
Try configuring the VM to not emulate a tablet. This will mean you can
no longer seamlessly move the cursor into and out of the VM but instead
will need to capture the pointer in the VM window.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx
I would expect it to fail in some VMs because they usually emulate
tablets for input. So the guest has no control over the host cursor
position in that case.
Can anyone reproduce it without a VM?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to l
Which driver does the Xorg log report in use? If not sure then please
run:
journalctl -b0 /usr/lib/xorg/Xorg > xorglog.txt
and attach the output here.
** Changed in: libx11 (Ubuntu)
Status: New => Incomplete
** Changed in: xorg (Ubuntu)
Status: Confirmed => Incomplete
** Chang
Yes I was thinking it might be the DIX's fault, platform-specific.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libx11 in Ubuntu.
https://bugs.launchpad.net/bugs/2084090
Title:
XWarpPointer doesn't work on Ubuntu 24.04 GNOME X11
To manage
Please report the issue to the Xorg developers at
https://gitlab.freedesktop.org/xorg/xserver/-/issues and then tell us
the new issue ID.
** Tags added: arm64 noble
** Also affects: libx11 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: xorg-server (Ubuntu)
Importance: U
kernel: qxl :00:01.0: object_init failed for (8298496, 0x0001)
kernel: [drm:qxl_alloc_bo_reserved [qxl]] *ERROR* failed to allocate VRAM BO
Looks like either a kernel bug in qxl or just the VM has not been
allocated enough virtual video memory.
** Tags added: qxl
** Package changed: xorg
*** This bug is a duplicate of bug 2064177 ***
https://bugs.launchpad.net/bugs/2064177
Yes it sounds like bug 2064177.
** This bug has been marked a duplicate of bug 2064177
Window borders and shadows missing from GTK3 dialogs (if autologin is
enabled and Xorg is used)
--
You received t
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #3437
https://gitlab.freedesktop.org/drm/amd/-/issues/3437
** Also affects: linux via
https://gitlab.freedesktop.org/drm/amd/-/issues/3437
Importance: Unknown
Status: Unknown
--
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
an
Thanks for the bug report. While the problem is happening please run:
journalctl -b0 > journal.txt
and attach the resulting text file here.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you a
Looks like the problem may be with the Flutter layer. What other apps
are affected?
I'm wondering if Flutter apps need a custom Nvidia sleep workaround like
bug 1876632 is about. Although that would only matter if they're using
the discrete GPU by default, and they shouldn't be.
** Package change
** No longer affects: ubuntu-gnome
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1588009
Title:
"libinput bug: timer offset negative" keeps coming up in syslog
To manage notifications abou
It’s also possible to fix in mutter/gnome-shell without changing
drivers. We just need more things connected to the gl-video-memory-
purged signal.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-560 in Ubuntu.
https://bug
** Package changed: xorg (Ubuntu) => gnome-settings-daemon (Ubuntu)
** Also affects: gnome-session (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bu
** Description changed:
- I've just tried the Nvidia-560 driver for the first time and am seeing
- very poor performance in Wayland sessions. Just tapping the Super key I
- can see animations stuttering.
+ On a desktop with a single Nvidia GPU and single monitor, desktop
+ performance is poor in W
Alright we can ignore the benchmark results [1].
And let's not focus on 550-560 performance differences anymore. We know
the main performance problem in 560 by a long way and it will either
require a new driver (that is probably not "560") [2], or a redesign of
triple buffering [3].
So this is no
** No longer affects: linux (Ubuntu)
** No longer affects: nvidia-graphics-drivers-535 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-560 in Ubuntu.
https://bugs.launchpad.net/bugs/2081140
Title:
[regression]
I can't reproduce the explanation in comment #16 for nvidia-550 being
faster than nvidia-560 (at least on Turing). Though it sounds like [1],
that doesn't seem to affect the shell performance itself.
We've verified that most of the shell's performance problem comes down
to an architectural differe
And then I changed my mind... The gtk4 change is a workaround, so some
other task should stay open.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-560 in Ubuntu.
https://bugs.launchpad.net/bugs/2081291
Title:
gnome app
We don't need to keep the Nvidia driver task open. The bug is always
open to new comments and changes even when it's "closed".
** Also affects: gtk4 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: gtk4 (Ubuntu)
Status: New => Fix Released
--
You received this bug noti
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
an
*** This bug is a duplicate of bug 2062951 ***
https://bugs.launchpad.net/bugs/2062951
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 2062951, so it is being marked as such. Please look
Actually I don't think this is unique to 560:
> 2. nvidia-560 spends way too much of gnome-shell's real time (60%)
inside gbm_surface_lock_front_buffer (called by lock_front_buffer).
It looks like 550 was doing the same.
But gnome-shell on nvidia-550 did consistently profile differently to
560.
Using kernel 6.11 I consistently get results like these from
glmark2-wayland:
nouveau...: ~1000 FPS
nvidia-550: ~8000 FPS
nvidia-560: ~2000-4000 FPS
but I can solve most of it with env __NV_DISABLE_EXPLICIT_SYNC=1
glmark2-wayland:
nvidia-560: ~7000 FPS
Though applying the same variable
** Summary changed:
- [regression] Poor performance in Nvidia Wayland sessions
+ [regression] Poor performance in Nvidia-560 Wayland sessions
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-560 in Ubuntu.
https://bugs.lau
** Changed in: mutter (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-560 in Ubuntu.
https://bugs.launchpad.net/bugs/2081140
Title:
[regression] Poor performance in Nvidia Wayland
Thanks for the bug report. Please try adding this kernel parameter:
i915.enable_psr=0
** 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 subscr
*** This bug is a duplicate of bug 1965563 ***
https://bugs.launchpad.net/bugs/1965563
drmuelr, it sounds like bug 2080498 is part of your problem.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to egl-wayland in Ubuntu.
https://bugs.launchpad
*** This bug is a duplicate of bug 2062951 ***
https://bugs.launchpad.net/bugs/2062951
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 2062951, so it is being marked as such. Please look
Bug 2082017 sounds relevant.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to nvidia-graphics-drivers-560 in Ubuntu.
https://bugs.launchpad.net/bugs/2081291
Title:
gnome applications crash on startup with nvidia-driver-560: Error 71
(Protocol
Though this kernel message is unusual and might be related:
i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun: transcoder,
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because
Thanks for the bug report. Please try adding this kernel parameter:
i915.enable_psr=0
--
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/2081250
Title:
Dual Monitor - Builtin Screen shake
To man
It looks like 'vmmon' (part of VMware) is causing frequent kernel
errors. What makes you say this is related to ACPI?
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member
Thanks for the bug report. There doesn't seem to be any Nvidia driver
loaded, which is at least one explanation for not being able to control
the monitor.
Please open the 'Additional Drivers' app and use it to install an Nvidia
driver. If you have already done that then see bug 1975650.
** Packag
Reopened in bug 2081291(?)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to egl-wayland in Ubuntu.
https://bugs.launchpad.net/bugs/1965563
Title:
GNOME apps crash with "Protocol error" in NVIDIA Wayland sessions
To manage notifications about t
See also bug 2080361.
** Summary changed:
- I have random log out
+ gnome-shell: Xwayland terminated, exiting since it was mandatory
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xwayland in Ubuntu.
https://bugs.launchpad.net/bugs/2080966
T
See also bug 2080966.
** Summary changed:
- Ubuntu 24.04.1 LTS Wayland crashes
+ gnome-shell: Xwayland terminated, exiting since it was mandatory
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xwayland in Ubuntu.
https://bugs.launchpad.net/bug
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
an
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
an
If Xwayland isn't leaving core files (which would show up as crash files
in /var/crash) then it might be inheriting Xorg's built-in crash
handler, logging the stack trace to *somewhere* and that never makes it
to the system journal.
--
You received this bug notification because you are a member o
Dropped the 'regression-update' tag because this bug really has existed
forever. The only regression-update is bug 2080498.
** Tags removed: regression-update
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to egl-wayland in Ubuntu.
https://bugs.la
This gnome-shell suicide is the only explanation I can see:
Sep 18 15:01:22 shanu-Inspiron-15-3511 gnome-shell[16721]: Connection to
xwayland lost
Sep 18 15:01:22 shanu-Inspiron-15-3511 gnome-shell[16721]: Xwayland terminated,
exiting since it was mandatory
Sep 18 15:01:22 shanu-Inspiron-15-3511
> Alessandro informs me that this was caused by some combination of kernel
> 6.8.0 and a
> nvidia-driver-550 update, so tagging regression-update, and I'll review the
> proposed fix next.
The regression-update is probably better tracked in bug 2080498.
--
You received this bug notification bec
In theory this is fix released now that Oracular has Nvidia-560. I can't
totally confirm it though, because once again Chrome has regressed to
not having any hardware acceleration enabled. But let's keep that
separate...
** Also affects: nvidia-graphics-drivers-560 (Ubuntu)
Importance: Undecid
Still happening in Oracular (bug 2080909)
** Changed in: xorg-server (Ubuntu)
Status: Fix Released => Confirmed
--
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/1811023
Title:
Xorg
I don't see any random logouts in the attached logs. Let's treat it as a
crash anyway...
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
It sounds like you're reporting multiple unrelated issues here. Please
be careful to only report one issue per bug report.
* kernel: ACPI Error: are BIOS bugs and can be safely ignored in most
cases. Also Ubuntu can't fix those.
* Random log out: Sounds like the biggest issue so let's focus on th
Thank you for reporting this bug to Ubuntu.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it
Assuming the bug is in journal-1.txt, it looks like the nouveau kernel
graphics driver that's crashing. To solve that I suggest installing an
official Nvidia driver from the 'Additional Drivers' app.
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Summary changed:
- Xorg freeze
+ [nouvea
** Package changed: xorg (Ubuntu) => libreoffice (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/2080806
Title:
wrong font size is displaying on editing
To manage notifications about th
Reverting to mirror mode suggests the system doesn't recognise the new
config on wakeup as being equal to the old config before sleeping.
One of your configurations in ~/.config/monitors.xml seems to contain a
disabled "unknown" monitor which likely was bug 2060268. So I suggest:
1. Make sure you
** Tags added: multimonitor 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/2080782
Title:
Problems when my computer monitors go to sleep
To manage notifications about this bug go to:
htt
Thanks. Please proceed to steps 2 and 3 in comment #2.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xwayland in Ubuntu.
https://bugs.launchpad.net/bugs/2080361
Title:
Ubuntu 24.04.1 LTS Wayland crashes
To manage notifications about this bu
Next steps:
1. Add SRU documentation (https://canonical-sru-docs.readthedocs-
hosted.com/en/latest/reference/bug-template/)
2. Subscribe ubuntu-sponsors
** Changed in: egl-wayland (Ubuntu Jammy)
Importance: Critical => High
** Changed in: egl-wayland (Ubuntu Jammy)
Status: Triaged =>
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Medium
** Changed in: switcheroo-control (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to egl-wayland in Ubuntu.
https://bugs.launchpad.ne
** Also affects: egl-wayland (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to egl-wayland in Ubuntu.
https://bugs.launchpad.net/bugs/2080282
Title:
Apps run on the discrete Nvidia GPU by defa
1 - 100 of 1092 matches
Mail list logo
