I think the nvidia-uvm kernel module is quite happily going out of
bounds :)
UBSAN: array-index-out-of-bounds
What made the screen go black over a minute later might have been
amdgpu's fault:
[ 99.419092] WARNING: CPU: 9 PID: 253 at
** Changed in: mutter (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069565
Title:
gnome-shell crashed with SIGSEGV in meta_drm_buffer_get_width() from
Thanks for the bug report. Next time the machine resets, let it boot up
again and then run:
journalctl -b-1 > prevboot.txt
and attach the resulting text file here.
** Package changed: gnome-shell (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received
Please also attach a copy of the log file showing that message. If it
was on screen then please attach a screenshot or photo.
** Package changed: bluez (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of
"Connection Failed. Activation of network connection failed." seems to
be related to wifi. Is the Bluetooth dongle also adding wifi?
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the bug report. Please start by removing any locally
installed extensions:
cd ~/.local/share/gnome-shell/
rm -rf extensions
and then log in again. If the problem persists after that then while it
is happening please run:
journalctl -b0 > journal.txt
ps -e -o pid,pcpu,comm
No, #46 was bug 2069477
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060268
Title:
Phantom "Unknown Display" shown in Settings after installing the
Nvidia driver
To manage notifications about
It looks like the log message most related to this crash in the
automated crash reports is:
meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB2WithModifiers
failed: Invalid argument
** Summary changed:
-
One of them was a kernel crash in the nvidia module, followed by:
meta_drm_buffer_gbm_new_lock_front failed: drmModeAddFB failed: Invalid
argument
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
--
You received this bug notification because
Tracking in:
https://errors.ubuntu.com/problem/6663c45a624f39b5e10436ce7378696b80c446e1
** Tags added: jammy
** Summary changed:
- gnome-shell-portal-helper crashed with SIGTRAP in waitUntilSyncedOrDie() from
WebKit::XDGDBusProxy::launch()
+ gnome-shell-portal-helper crashed with SIGTRAP in
** Summary changed:
- /usr/bin/gnome-shell:5:meta_wayland_compositor_new:meta_context_start:main
+ gnome-shell crashed with SIGTRAP in meta_wayland_compositor_new() from
meta_context_start() from main()
** Summary changed:
- gnome-shell crashed with SIGTRAP in meta_wayland_compositor_new()
*** This bug is a duplicate of bug 2051574 ***
https://bugs.launchpad.net/bugs/2051574
** This bug has been marked a duplicate of bug 2051574
gnome-shell-portal-helper crashed with SIGTRAP in waitUntilSyncedOrDie()
from WebKit::XDGDBusProxy::launch()
--
You received this bug
Tracking in:
https://errors.ubuntu.com/problem/d8b3d07c144e0281e9277b403a13025df9890464
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2039340
Title:
gnome-shell (login screen) crashes with SIGSEGV
crashed with SIGSEGV in st_theme_node_lookup_shadow() from
st_theme_node_get_box_shadow() from st_theme_node_get_paint_box() from
st_theme_node_transition_get_paint_box() from st_widget_get_paint_volume()
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanv
*** This bug is a duplicate of bug 2039340 ***
https://bugs.launchpad.net/bugs/2039340
** This bug has been marked a duplicate of bug 2039340
gnome-shell (login screen) crashes with SIGSEGV in
__GI_getenv("EXPAT_ACCOUNTING_DEBUG")
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 2037055 ***
https://bugs.launchpad.net/bugs/2037055
** This bug has been marked a duplicate of bug 2037055
gnome-shell crashed with SIGABRT:
ERROR:../src/shell-app.c:1644:shell_app_dispose: assertion failed: (app->state
== SHELL_APP_STATE_STOPPED)
--
The lock/unlock sequence can be broken by buggy gnome-shell extensions
crashing when they get told to deactivate/reactivate, so please start by
removing any local extensions:
cd ~/.local/share/gnome-shell/
rm -rf extensions
and then log in again.
** Package changed: xorg (Ubuntu) =>
*** This bug is a duplicate of bug 2062377 ***
https://bugs.launchpad.net/bugs/2062377
Due to the delayed nature of X errors, they could both be the same bug
2062377. It's possible that's the only real crash here.
--
You received this bug notification because you are a member of Ubuntu
** Changed in: mutter (Ubuntu)
Status: In Progress => Fix Committed
** Tags added: fixed-in-mutter-47 fixed-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967707
Title:
Nvidia
*** This bug is a duplicate of bug 2062377 ***
https://bugs.launchpad.net/bugs/2062377
There are two separate issues here, and both seem to result in an int3:
[ 14.366966] simple-framebuffer simple-framebuffer.0: swiotlb buffer is full
(sz: 770048 bytes), total 32768 (slots), used 288
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069477
Title:
gnome-shell crashes (traps) with int3 on launch using nvidia
proprietary drivers
To manage notifications about this bug go to:
** Summary changed:
- Random flickering with Intel i915 on Linux 6.8 (Ubuntu 24.04)
+ Random flickering with Intel i915 (Gen9 GPUs) on Linux 6.8 (Ubuntu 24.04)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Please continue to use the workaround mentioned in the Bug Description
above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061079
Title:
GTK-ngl (new default backend) rendering issues with the
That looks like bug 2054401 but I'm not sure how that happened because
Ubuntu 24.04 does not contain the 545 driver anymore:
https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-545
Also the 'oibaf' PPA is mentioned here, which is not part of Ubuntu and
not supported. It's highly likely
This is happening in 24.04/24.10 now due to bug 2060268, so please see
the workarounds in that bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967707
Title:
Nvidia Wayland sessions sometimes
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
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Changed in: mutter (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067143
Title:
[i915]
AIUI this will only happen if there's an external monitor plugged into
the discrete GPU using nouveau. That's common, but hopefully less common
than hybrid laptops without an external monitor connected.
So as a workaround you should be able to:
1. Unplug the monitor.
2. Log in using the laptop
** Changed in: mutter (Ubuntu)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2052913
Title:
[Xorg] Large performance regression in fullscreen windows
To
*** This bug is a duplicate of bug 1961508 ***
https://bugs.launchpad.net/bugs/1961508
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 1961508, so it is being marked as such. Please
I'm not sure what you're trying to describe in "nvidia driver aint
updating".
I can see that you have a GeForce 940M and driver version 470 installed.
But that GPU can support the latest drivers so I would recommend using
the 'Additional Drivers' app to uninstall the current Nvidia driver and
** Summary changed:
- Gnome black screen at boot
+ Gnome black screen at boot (QXL + Nvidia hybrid VM)
** Package changed: ubuntu => xserver-xorg-video-qxl (Ubuntu)
** Changed in: xserver-xorg-video-qxl (Ubuntu)
Status: Incomplete => New
** Also affects: nvidia-graphics-drivers-535
** Changed in: mutter (Ubuntu Oracular)
Milestone: None => ubuntu-24.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2050865
Title:
GNOME Wayland session crashes with
It will be mentioned here when we know. You can also subscribe to bug
2068598 and/or https://discourse.ubuntu.com/t/mutter-gnome-shell-are-no-
longer-covered-by-the-gnome-mre/45218
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Package changed: ubuntu => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068804
Title:
very very very slow even
** Changed in: xwayland (Ubuntu Oracular)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970389
Title:
[nvidia] Janky text entry and frames appear out of
My laptop NVMe was experiencing different errors to yours. Mine was more
obviously a hardware failure.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068804
Title:
very very very slow even though a
Tested on Oracular finally (Nvidia 535). It's a lot better but still not
perfect. Frames don't seem to be out of order anymore but there is an
annoying lag when typing text in Google Chrome for example. I'm not sure
that's still this same bug but it might explain why the upstream bug
If nothing else, you know that booting Ubuntu from USB or from an SD
card is one way to remove the NVMe from the equation when testing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068804
Title:
I feel that photo kind of proves my point about how uncommon the
situation is. Not invalid, just uncommon.
I also wonder if you could trick the laptop into using the external
monitor as primary? Maybe if you can configure the BIOS to turn the
machine on in response to USB keyboard/mice while the
The fact that Windows survives drive errors better than Linux isn't
really surprising and doesn't prove anything on its own. But it might be
useful to run some testing tools on the drive from within Windows in
that case.
--
You received this bug notification because you are a member of Ubuntu
OK well it sounds like an NVMe hardware failure to me. That might be the
drive, might be the motherboard, or it might just be a software bug. I'm
not totally sure. But the freezes and behaviour you describe fit
perfectly with an NVMe failure. I had one on a laptop of my own a few
weeks ago and the
I would be very surprised if 'qxl' could act as the primary GPU when the
secondary is 'nvidia', but let's see...
In the VM, please switch to a VT, log in and run:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
and then attach the resulting text files here.
** Package
Looking at src/core/window.c in Mutter makes me think Mutter is more
likely to blame. And there is also an upstream bug:
https://gitlab.gnome.org/GNOME/mutter/-/issues/3224
** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu)
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues
Yes a separate bug for the black screen sounds sensible.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068908
Title:
VM guest resolution is not saved anymore
To manage notifications about this
Not just Skylake. The duplicates I'm seeing reported from Noble machines
are from Comet Lake and Kaby Lake. So all Intel "Gen9" GPUs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062951
Title:
*** 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
** Changed in: mutter (Ubuntu Noble)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: mutter (Ubuntu Noble)
Status: New => Triaged
** Changed in: mutter (Ubuntu Oracular)
Milestone: None => ubuntu-24.10
** Tags added: fixed-in-mutter-46.1 fixed-upstream
Seems to be because the Nvidia 470 kernel driver does not support your
GT 730 GPU:
[5.887374] NVRM: The NVIDIA GeForce GT 730 GPU installed in this system is
NVRM: supported through the NVIDIA 390.xx Legacy drivers. Please
NVRM: visit
The (bottom of the) log in comment #5 shows it's the kernel hanging.
** Package changed: ubuntu => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Summary changed:
- whole system hangs
+ whole system hangs [kernel: watchdog: BUG: soft lockup - CPU#n stuck]
--
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069146
Title:
After performing a search in the Activities Overview, the icons
exhibit
No. Default Ubuntu with GNOME should not have that bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068908
Title:
VM guest resolution is not saved anymore
To manage notifications about this bug
The boot time slowness looks related to hardware errors on the boot
drive:
Jun 12 22:55:56 ee-Z790-Steel-Legend-WiFi smartd[2365]: Device: /dev/nvme0,
KINGSTON SKC3000S1024G, S/N:50026B7686280109, FW:EIFK31.6, 1.02 TB
...
Jun 12 22:55:58 ee-Z790-Steel-Legend-WiFi smartd[2365]: Device:
The issue will occur with all GPU types. All DRM drivers that support
multiple monitors.
But I'd argue it's not a problem at all. Not wanting to have the boot
display in view when you power on the machine is so uncommon that I feel
the medicine would be worse than the disease. Just apply the
The hardware isn't relevant here. This issue is due to the combination
of the two software factors listed in comment #6. And neither of those
are bugs.
Still, to work around it you should just be able to run:
gsettings set org.gnome.desktop.interface font-antialiasing
'grayscale'
and log in
*** This bug is a duplicate of bug 1717878 ***
https://bugs.launchpad.net/bugs/1717878
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 1717878, so it is being marked as such. Please
Cool, though it's not a complete solution for all apps:
https://src.fedoraproject.org/rpms/mutter/blob/main/f/0001-place-Always-
center-initial-setup-fedora-welcome.patch
I think it should be easy to write a complete solution that just ignores
DESKTOP windows in the placement rules. Assuming
I had intentionally omitted Noble because it's not yet clear if it will
get the full 46.2 due to the 46.1 issue... But I guess even releasing a
cut down version would still be tracked here.
** Changed in: mutter (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => Jeremy Bícha (jbicha)
--
** Changed in: intel-vaapi-driver (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2058143
Title:
Decoding glitchy on GM45 - MR has been pending
The scripts for automatically deciding what goes into the initrd can be
found in /usr/share/initramfs-tools/hooks/ and initramfs-tools in
general could certainly be made more user-friendly...
In the end the foundations/kernel teams will decide what goes in and
what doesn't. I just have a
Assuming this is https://gitlab.gnome.org/GNOME/mutter/-/issues/3372,
then it's really in upstream release 46.2. So see bug 2068598.
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/3372
Importance: Unknown
Status: Unknown
--
You received this bug
Actually the fix for https://gitlab.gnome.org/GNOME/mutter/-/issues/3372
is not in 46.1-2ubuntu1, so that's not the right upstream link.
There are some other crashes fixed in 46.1 so please follow the steps in
comment #1 to identify which crash it is.
** No longer affects: mutter
--
You
Yeah that's not what a proper fix would do, it's just a workaround.
You can work around that new issue by adding 'amdgpu' or 'i915' to
'/etc/initramfs-tools/modules' and then run:
sudo update-initramfs -k all -u
or get the system to automatically insert all the modules you're
currently using
Yes it's been done before. I think the Nvidia drivers still do it
because they're designed for older kernel builds that don't have
SimpleDRM included.
But "needed" is a strong word in this case. It's unusual that you
wouldn't be able to see the primary boot display at boot time. So in
that case I
Verified fixed on a Raspberry Pi 400 using version
2.44.2-0ubuntu0.24.04.2
** Tags removed: verification-needed-noble
** Tags added: verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Verified fixed on a Raspberry Pi 400 using version
2.44.2-0ubuntu0.24.04.2
** Tags removed: verification-needed-noble
** Tags added: verification-done-noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: nvidia-graphics-drivers-470 (Ubuntu Noble)
Status: New => Fix Committed
** Changed in: nvidia-graphics-drivers-470 (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in: nvidia-graphics-drivers-470 (Ubuntu Focal)
Status: New => Fix Committed
--
You
Maybe this is now "Won't Fix" in favour of bug 2067597?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066044
Title:
New upstream release 535.179
To manage notifications about this bug go to:
Looks like this bug has only ever been observed with AMD CPUs, which
might be a factor.
Also I wonder if the Nvidia driver misconfiguration might be caused by
third party software like Steam?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
In case the problem is bug 2062426, please try the workarounds from bug
2060268. If that does not solve it then please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.
2. Look in /var/crash
The accented text colour is due to one or two factors:
1. Lossy video encoding (we're not going to change that)
2. GTK3 apps (including Desktop Icons NG) still use RGB font
antialiasing, which is no longer present in GTK4 apps. You can remove
that by running:
gsettings set
If you have a VM running KDE or LXQt and it boots to a black screen then
see bug 2063143.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068908
Title:
VM guest resolution is not saved anymore
To
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: simpledrm
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069039
Title:
Disk password prompt isn't shown in external monitor
To manage notifications about this bug go to:
This is probably a "Won't Fix" but I'll give others time to chime in and
correct me...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069039
Title:
Disk password prompt isn't shown in external
Timo is right I think. Secondary monitors will only wake up after:
1. The native kernel DRM graphics driver is loaded.
2. Plymouth detects the new driver and switches to it.
And the native kernel DRM graphics drivers seem to be loading slightly
later now that we have kicked them out of the
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: xwayland (Ubuntu Oracular)
Importance: High
Status: Triaged
** Also affects: mutter (Ubuntu Noble)
Just tested again. Switching back to Nvidia 535.171.04-0ubuntu2 on Noble
I don't get any crashes in GNOME apps. Definitely using Wayland. They
all just work.
I wonder why it works for some people but not others. Maybe the driver
installation method? I ended up installing my driver using 'sudo apt
*** This bug is a duplicate of bug 2063827 ***
https://bugs.launchpad.net/bugs/2063827
** This bug has been marked a duplicate of bug 2063827
Gnome apps segfault in Nvidia Wayland sessions on Noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I was expecting the Ubuntu desktop but also without this bug :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068908
Title:
VM guest resolution is not saved anymore
To manage notifications about
Florian, please use bug 2062951 instead.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066268
Title:
Sometimes screen flashes black, probably a driver issue?
To manage notifications about this
That sounds like a whole new bug. Try rebooting and be sure to select
'Ubuntu' before logging in again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068908
Title:
VM guest resolution is not saved
No please don't delete card1.
Try logging out and then on the login screen choose 'Ubuntu on Xorg'
from the menu in the bottom right corner. Then log in again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: mutter (Ubuntu)
Assignee: Jeremy Bícha (jbicha) => Daniel van Vugt (vanvugt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068598
Title:
Mutter release 46.2
To man
It looks like you're using Xorg so that should be handling the cursor
movement independently of gnome-shell. Is it really just gnome-shell
using high CPU?
Please try:
gnome-extensions disable d...@rastersoft.com
** Summary changed:
- gnome-shell using more than 50% of CPU by simply moving
** Tags added: flicker i915 mantic noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062951
Title:
Random flickering with Intel i915 on Linux 6.8 (Ubuntu 24.04)
To manage notifications about
Does it sound like bug 2064177? Are you using Xorg or autologin?
Can you attach a screenshot?
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
*** 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
"Scale Display: Always + Auto resize VM with window" sounds like a
feature of the hypervisor. Which hypervisor are you using?
Usually to resize a VM dynamically it either uses;
(a) A custom Xorg driver in the guest (but you're not using Xorg); or
(b) Virtually hotplugging the virtual monitor
Are there multiple card devices in /dev/dri/ ? If so then please try:
sudo rm /dev/dri/card0
and log in again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068908
Title:
VM guest resolution
** Summary changed:
- Resolution is not saved anymore
+ VM guest resolution is not saved anymore
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068908
Title:
VM guest resolution is not saved
** Tags added: jammy
** Summary changed:
- Desktop icons in Mantic doesn't honor dock margins in Jammy
+ Desktop icons from Mantic doesn't honor dock margins in Jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Looks like there's one root cause in mesa/egl-wayland/GNOME causing that
Zink error and the original crash here. Because I don't think(?) Nvidia
should be trying to use Zink, and if it didn't then the original crash
also would not happen.
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 2026194 ***
https://bugs.launchpad.net/bugs/2026194
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 2026194, so it is being marked as such. Please
See also bug 2067872.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063827
Title:
Gnome apps segfault in Nvidia Wayland sessions on Noble
To manage notifications about this bug go to:
Actually there is more relevant detail here so let's keep this one.
** This bug is no longer a duplicate of bug 2067872
Gnome apps segfault in Nvidia Wayland session (noble)
** Summary changed:
- Gnome Control Center fails to open on Wayland
+ Gnome apps segfault in Nvidia Wayland sessions
Sorry I didn't see this bug earlier. For now I'm going to group it with
bug 2067872 because that one is more generic and has more relevant
links.
** This bug has been marked a duplicate of bug 2067872
Gnome apps segfault in Nvidia Wayland session (noble)
--
You received this bug
That last issue is bug 1876632.
** Tags added: noble nvidia nvidia-wayland
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063827
Title:
Gnome apps segfault in Nvidia Wayland sessions on Noble
To
*** This bug is a duplicate of bug 2063827 ***
https://bugs.launchpad.net/bugs/2063827
Also reported in bug 2063827
** Changed in: egl-wayland (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
Status: Incomplete => Confirmed
** This
*** This bug is a duplicate of bug 2063827 ***
https://bugs.launchpad.net/bugs/2063827
** This bug is no longer a duplicate of bug 2067872
Gnome apps segfault in Nvidia Wayland session (noble)
** This bug has been marked a duplicate of bug 2063827
Gnome Control Center fails to open on
401 - 500 of 52984 matches
Mail list logo
