** Description changed:
+ [ Impact ]
+
+ Clicking on some maximized or fullscreen windows may not respond and the
+ clicks fall through to the window behind.
+
+ [ Test Plan ]
+
+ Someone please fill this in with instructions that reference easily
+ available software in Ubuntu.
+
+ [ Where
** Description changed:
+ [ Impact ]
+
+ Wayland sessions log in to a black screen, if a secondary GPU exists
+ that's using the nouveau driver and has a secondary monitor plugged into
+ it.
+
+ [ Test Plan ]
+
+ 0. Find a machine with hybrid graphics: Intel integrated, Nvidia discrete.
+ 1.
** Description changed:
+ [ Impact ]
+
+ gnome-shell occasionally crashes in meta_wayland_transaction_commit.
+
+ [ Test Plan ]
+
+ Unknown. Requires user verification.
+
+ [ Where problems could occur ]
+
+ Anywhere in screen contents correctness or graphics performance in
+ Wayland
** Description changed:
+ [ Impact ]
+
Since installing Ubuntu 24.04, every now and then Night Light gets stuck
when my screen is locked at night and I unlock it in the morning. The
screen is then very orange (more so than normally is the case with Night
Light), and disabling it with the
nce: Undecided => High
** Changed in: mutter (Ubuntu Noble)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: mutter (Ubuntu Noble)
Milestone: None => ubuntu-24.04.1
** Changed in: mutter (Ubuntu Oracular)
Milestone: None => ubuntu-24.10
--
You re
nce: Undecided => Medium
** Changed in: mutter (Ubuntu Noble)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: mutter (Ubuntu Noble)
Milestone: None => ubuntu-24.04.1
** Changed in: mutter (Ubuntu Oracular)
Milestone: None => ubuntu-24.10
--
You re
** Changed in: mutter (Ubuntu Noble)
Milestone: None => ubuntu-24.04.1
--
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
** Changed in: mutter (Ubuntu Oracular)
Milestone: None => ubuntu-24.10
** Changed in: mutter (Ubuntu Noble)
Milestone: None => ubuntu-24.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: mutter (Ubuntu Oracular)
Milestone: None => ubuntu-24.10
** Changed in: mutter (Ubuntu Noble)
Milestone: None => ubuntu-24.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: mutter (Ubuntu Noble)
Milestone: None => ubuntu-24.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066931
Title:
Primary GPU displays nothing if the secondary GPU is using
According to your Xrandr.txt, the lowest possible value is 8 for you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069741
Title:
[amdgpu] Screen is flickering
To manage notifications about this
It's different for each kernel driver. This works on Intel for me:
sudo apt install drm-info
sudo drm_info | grep bpc
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069741
Title:
[amdgpu]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069741
Title:
[amdgpu] Screen is flickering
To manage notifications about this bug go to:
The 8350U has a Gen9 GPU:
https://en.wikipedia.org/wiki/List_of_Intel_graphics_processing_units#Gen9
Blame Intel for using confusing terminology where their CPU generation
number has no relationship to the GPU generation number.
--
You received this bug notification because you are a member of
You can find more amd64 debs in:
https://kernel.ubuntu.com/mainline/v6.8.12/amd64/
https://kernel.ubuntu.com/mainline/v6.9.3/amd64/
And yes you can force a lower bandwidth signal with something as simple
as:
xrandr --output DVI-D-0 --set 'max bpc' 8
--
You received this bug notification
*** This bug is a duplicate of bug 2012388 ***
https://bugs.launchpad.net/bugs/2012388
The top-right corner issue is bug 2012388. I don't know exactly when
that fix will reach noble.
** This bug has been marked a duplicate of bug 2012388
X11 window (usually AnyDesk) at top-right of the
See also https://gitlab.gnome.org/GNOME/mutter/-/issues/3536
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3536
https://gitlab.gnome.org/GNOME/mutter/-/issues/3536
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Display cables matter a lot because they have to transmit gigabits per
second and small imperfections can interrupt that randomly, leading to a
temporarily black screen.
The reason a cable might work on Windows but not Linux could be slightly
different signalling, if for example Windows is using
Since it involves installing a lot of packages repeatedly and you don't
sound confident, I will no longer recommend trying other kernels.
Other than that, I can only suggest trying a newer HDMI (or DVI?) cable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Thanks. The only message I can see that might be related is:
kernel: amdgpu :03:00.0: amdgpu: Disabling VM faults because of
PRT request!
which some googling suggests is caused by the GPU being under load.
Certainly Steam was running at the time.
It might pay to try some older and newer
** Changed in: mutter (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/2069361
Title:
Google Chrome does not tile correctly
To manage notifications about
If you add GSK_RENDERER=gl to /etc/environment and reboot, does it
improve the situation?
--
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
That package, and other graphics packages you have installed, do not
appear to be from Ubuntu. So we cannot support it here.
Given you have such new hardware and an old Ubuntu release which doesn't
seem to recognise your GPU, I strongly recommend installing Ubuntu 24.04
or 22.04 instead. You will
I just hit this on logout in Oracular. Prior to the crash I had been
toggling the tiling extension and stress testing tiling using Google
Chrome (as is also mentioned in https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/7045).
** Tags added: noble oracular
--
You received this bug
Please go to chrome://flags/#ozone-platform-hint and set it to Wayland,
then restart the browser. Does that fix the bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069361
Title:
Google Chrome
I'm not aware of any Ubuntu-specifics that might cause this. I would
suggest:
1. Testing the 46.0 upstream tag to see if it's just that Ubuntu hasn't
released the fix yet; and
2. If 46.0 upstream did not have the bug (meaning it can't be bisected),
then report an upstream bug anyway since they
** Tags added: noble
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069766
Title:
Window receives old size in fullscreen configuration event
To manage notifications about this bug go to:
** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu)
Assignee: (unassigned) => Sergio Costas (rastersoft-gmail)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067831
Title:
can't use
** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu)
Status: Confirmed => Fix Committed
** Tags added: fixed-in-ding-47.0.11 fixed-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: mutter (Ubuntu)
Status: New => Invalid
** Package changed: mesa (Ubuntu) => linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068567
Title:
Irregular frame rate
See also bug 2069720.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2067831
Title:
can't use arrows when renaming on the desktop
To manage notifications about this bug go to:
Next time the problem happens, please run:
journalctl -b0 > journal.txt
and attach the resulting text file here.
** Summary changed:
- Screen is flickering
+ [amdgpu] Screen is flickering
** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu)
** Tags added: amdgpu
**
See also bug 2067831
** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-
desktop-icons-ng (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069720
Title:
Summary: "Unexpected
Some log snippets from Ubuntu crash reports:
---
org.gnome.Shell.PortalHelper[3349]: bwrap: setting up uid map: Permission denied
gnome-shell-por[3215]: Failed to fully launch dbus-proxy: Sub processo terminou
com o código 1
---
org.gnome.Shell.PortalHelper[139725]: bwrap: setting up uid map:
What is the scaling factor of the display in settings?
** Summary changed:
- Chrome does not tile correctly after disabling enhanced tiling
+ Google Chrome does not tile correctly
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It doesn't affect me, but currently 28 other people are saying it
affects them so I'm sure someone can try that.
--
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
** Changed in: mutter (Ubuntu)
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/1967707
Title:
Nvidia Wayland sessions sometimes flood the log with
** Also affects: mutter (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: mutter (Ubuntu Oracular)
Importance: Medium
Assignee: Daniel van Vugt (vanvugt)
Status: Fix Committed
** Changed in: mutter (Ubuntu Noble)
Assignee: (unassigned) => Daniel
: mutter (Ubuntu Oracular)
Importance: Medium
Assignee: Daniel van Vugt (vanvugt)
Status: Fix Committed
** Changed in: mutter (Ubuntu Noble)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: mutter (Ubuntu Noble)
Importance: Undecided => Medium
** C
** Bug watch added: github.com/micheleg/dash-to-dock/issues #2179
https://github.com/micheleg/dash-to-dock/issues/2179
** Also affects: dash-to-dock via
https://github.com/micheleg/dash-to-dock/issues/2179
Importance: Unknown
Status: Unknown
--
You received this bug notification
A bunch of ways it can happen according to the crash reports:
---
kernel: INFO: task kworker/u65:1:1093 blocked for more than 491 seconds.
kernel: Tainted: G W 6.8.0-35-generic #35-Ubuntu
kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
gnome-shell[2744]: Failed
Mistyped again, assuming you plan on upgrading to 24.04 :)
** Tags added: mantic
** Changed in: bluez (Ubuntu)
Status: Won't Fix => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm guessing >=555 is fine, any time before Oracular.
--
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 order in Xwayland
apps
To
Are you using a text scaling factor, or a display scaling factor above
100%? Sounds like https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/7727
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #7727
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7727
** Changed in:
As I suspected, we're missing the third piece of the puzzle: Nvidia
driver 555
** Changed in: xwayland (Ubuntu Oracular)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The nvidia-graphics-drivers task here represents the missing 555 driver.
** Changed in: nvidia-graphics-drivers (Ubuntu Oracular)
Importance: Undecided => Medium
** Changed in: nvidia-graphics-drivers (Ubuntu Oracular)
Status: New => Triaged
** Changed in: nvidia-graphics-drivers
It appears VSCode and MSEdge are to blame, using most/all of your CPU:
PID %CPU COMMAND
20171 232 code
20945 139 code
21394 101 code
21363 90.6 code
20142 38.4 code
8526 16.2 msedge
8100 13.0 msedge
21395 11.2 code
** Package changed: gnome-shell (Ubuntu) => ubuntu
**
Thank you for reporting this bug to Ubuntu.
Ubuntu 22.10 (kinetic) reached end-of-life on July 20, 2023.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be
** Changed in: mutter (Ubuntu)
Status: In Progress => Fix Committed
** Tags added: fixed-in-mutter-47 fixed-upstream
** Changed in: mutter (Ubuntu)
Milestone: noble-updates => ubuntu-24.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: mutter (Ubuntu)
Status: In Progress => Fix Committed
** Tags added: fixed-in-mutter-47 fixed-upstream
** Changed in: mutter (Ubuntu)
Milestone: noble-updates => ubuntu-24.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Sounds like the original problem is fix now.
The Huawei appearing in the list as "Not Set Up" is correct. That means
it exists but is not connected to the PC. You will find all Bluetooth
devices near the PC will appear in that list even if unused.
** Changed in: ubuntu
Status: Incomplete
Work in progress:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3817
--
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
** Changed in: mutter (Ubuntu)
Status: New => In Progress
** Tags added: hybrid multigpu
** Tags added: udeng-3252
--
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
** Also affects: gnome-shell (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: gnome-shell (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: gnome-shell (Ubuntu Oracular)
Importance: Undecided
Assignee: Daniel van Vugt (vanvugt
*** This bug is a duplicate of bug 2069559 ***
https://bugs.launchpad.net/bugs/2069559
** This bug has been marked a duplicate of bug 2069559
gnome-shell crashed with SIGSEGV in st_theme_node_lookup_shadow() from
st_theme_node_get_box_shadow() from st_theme_node_get_paint_box() from
The PC is connecting to a Galaxy A14 phone via Bluetooth and it's the
phone offering internet connection sharing, which also isn't working.
Maybe try disabling internet connection sharing on the phone, or just
don't connect the phone to the PC via Bluetooth.
--
You received this bug notification
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
1 - 100 of 52640 matches
Mail list logo
