Bug 2106704 also mentions a 30 second delay in suspending.
** Tags added: suspend suspend-resume
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106697
Title:
Suspend waits 30 seconds
To manage not
This is probably a hardware problem. Please try:
1. Not using your monitor as a USB hub (in case you are); and
2. An external USB DAC for audio.
** Summary changed:
- I think i have a problem with video driver!
+ Scratching sound in audio output when mouse moves
** Package changed: xorg (Ubunt
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
bmaupin, can you please install the libmutter debug package:
https://launchpad.net/ubuntu/+source/mutter/46.2-1ubuntu0.24.04.6/+build/30368488/+files/libmutter-14-0-dbgsym_46.2-1ubuntu0.24.04.6_amd64.ddeb
(assuming you still use version 46.2-1ubuntu0.24.04.6) and then try
again?
--
You received
Thanks.
https://errors.ubuntu.com/oops/8dffea99-154c-11f0-b404-fa163ec8ca8c is
more like what I was expecting; gnome-shell is blocked in some X11 call
waiting on a reply from the server that never comes.
The lack of debug symbols means I can't see enough detail. But it looks
like the important par
It might be a distant relation of another damage tracking bug:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7858
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #7858
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7858
** Changed in: gnome-shell (Ubuntu)
Stat
** Changed in: mutter (Ubuntu)
Status: Confirmed => Fix Committed
** Tags added: fixed-in-mutter-48.2 fixed-upstream
** Tags removed: fixed-in-mutter-48.2
** Tags added: fixed-in-mutter-49
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Great! Just confirming the desktop can work in theory.
Next please:
1. Add MUTTER_DEBUG=kms to /etc/environment and reboot (without
nomodeset) so as to reproduce the problem.
2. Log in and wait at least 60 seconds on the back screen.
3. Collect a system log, either by switching VTs (Ctrl+Alt+F4
https://launchpad.net/ubuntu/+source/mesa/25.0.3-1ubuntu2
** Changed in: mesa (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/2101817
Title:
gnom
** Tags removed: desktop-needs-sru
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2093237
Title:
gnome-shell crashed with SIGSEGV in meta_window_foreach_transient()
from meta_window_has_modals() fr
** Tags removed: desktop-needs-sru
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2097415
Title:
Ubuntu 24.04, mutter: drag and drop does not work between x11 and
wayland applications
To manage no
** Tags removed: desktop-needs-sru
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2099879
Title:
Transparent dialogs in IntelliJ IDEA with Mutter and nVidia
To manage notifications about this bug go
That sounds consistent with gnome-shell being frozen so we should
continue with the steps in comment #68.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089709
Title:
Ubuntu 24.04 (X11) sometimes lo
It sounds like a kernel issue to me:
[4.651068] xe :00:02.0: Your graphics device 7d55 is not officially
supported
by xe driver in this kernel version. To force Xe probe,
use xe.force_probe='7d55' and i915.force_probe='!7d55'
module parameters
** Changed in: gnome-control-center (Ubuntu)
Status: Triaged => 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/2106567
Title:
gnome-control-center crashed with SIGTRAP in
g_setti
That's correct. At least it's just a warning now instead of a crash.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106567
Title:
gnome-control-center crashed with SIGTRAP in
g_settings_schema_get
That looks like the wrong crash again, but this time I can't tell why.
Maybe gnome-shell is trying to catch the first SIGABRT but then dying
with SIGSEGV in its own handlers. I'll need to choose a different signal
that gnome-shell doesn't catch itself... Maybe try:
killall -QUIT gnome-shell
The
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: mutter (Ubuntu)
Milestone: None => ubuntu-25.04
** Tags added: udeng-6674
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags added: udeng-6673
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106567
Title:
gnome-control-center crashed with SIGTRAP in
g_settings_schema_get_value() from g_settings_schema_key_init()
** Changed in: gnome-control-center (Ubuntu)
Importance: High => Medium
** Changed in: gnome-control-center (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Next time the problem happens, please immediately open a terminal and
run:
journalctl -b0 /usr/bin/gnome-shell > gslog.txt
and attach the resulting text file here.
** Tags added: suspend-resume
** Changed in: mutter (Ubuntu)
Status: New => Incomplete
--
You received this bug notific
** Summary changed:
-
/usr/bin/gnome-control-center:5:g_settings_schema_get_value:g_settings_schema_key_init:g_settings_get_user_value:update_yaru_accent_settings:g_closure_invoke
+ gnome-control-center crashed with SIGTRAP in g_settings_schema_get_value()
from g_settings_schema_key_init() from
> Configure the monitor (in its own menus) to not auto-switch inputs.
This means go into the monitor's on-screen menu and look at input
selection. Make sure it's not configured to automatically switch inputs,
but instead fixed on a single input port.
--
You received this bug notification because
*** This bug is a duplicate of bug 2106567 ***
https://bugs.launchpad.net/bugs/2106567
** Summary changed:
- gnome-control-center crashed with SIGTRAP in g_settings_get_user_value()
+ gnome-control-center crashed with SIGTRAP in g_settings_get_user_value()
[ERROR: Settings schema 'org.gnome.
It might have been OK because usually shorter is better. Shorter cables
have less signal degradation and maintain higher bandwidth more
reliably.
I recently experimented with a 4K@240Hz monitor and found [a very short
cable](https://www.amazon.com.au/dp/B0D815GV9K) was able to maintain a
stable hi
Looking at
https://errors.ubuntu.com/oops/b3d821a0-143f-11f0-8694-fa163ec44ecd from
comment #64 it appears I gave bad advice with "USR1". We need a signal
whose default action is to dump core, so please try this instead next
time the problem happens:
Switch to a VT and the force gnome-shell to dum
Yes if it was an external monitor then we'd call it a manufacturing
defect, but as an internal laptop panel the problem is slightly more
common. But still, it shouldn't prevent common display modes from
working.
Next please try adding this kernel parameter:
nomodeset
** Summary changed:
- Sy
OK, thanks for the update.
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Invalid
** Package changed: xorg-server (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/21
This is related to events coming from one or more monitors, which the
system might treat as a reason to wake up. Sometimes a monitor will
add/remove audio support, or disconnect entirely, when going to sleep.
And that can give the OS the impression that something important is
happening which should
** Description changed:
[Impact]
The Nvidia driver corrupts and/or forgets its textures when resuming
from suspend, by design. Documented here:
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt
*NOTE* that this is actually not a common p
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3924
https://gitlab.gnome.org/GNOME/mutter/-/issues/3924
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/3924
Importance: Unknown
Status: Unknown
** Tags added: fixed-in-mutter-48.rc fixed-upstr
There is a third option and it really is what this "ubuntu" bug is meant
to track: Enable Imagination/PVR support for Mesa version 25.x in Ubuntu
25.10.
I can see we have the source code already:
https://salsa.debian.org/xorg-team/lib/mesa/-/tree/ubuntu/src/imagination
So it might just be a matte
Though you already said it works fine in Xorg. Are you sure you retested
in a Wayland session?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106284
Title:
Path of Titans game mouse pan broken since
It's also possible you're only just noticing the effects of the kernel
update you installed on 1 April, or even of some update to the game
itself.
** Changed in: xorg-server (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106284
Title:
Path of Titans game mouse pan broken since -1ubuntu1.3 security update
To manage notifications about th
It sounds like you are still using Ubuntu 22.04. Although we would
rather you used Ubuntu 24.04, the very old version of Mesa they are
offering may not work in 24.04.
I think you have two options:
(a) Use Ubuntu 22.04 and force install ALL the Mesa 22.3.5 packages from
Imagination (at the same ti
It sounds like the dock and the number of monitors are the two main
issues.
* Your laptop's USB-C port only supports DP1.4, so is limited to HBR3
which can drive the Samsung G9 at 120Hz true colour (or 97Hz in deep
colour/HDR) under ideal conditions with a perfect cable, but will have
no additiona
I understand the frustration with how random the issue is, I've been
there before. I can only recommend:
* Avoid docks if you need to drive high bandwidth displays.
* Have other brands of cables on hand to try. Including a direct USB-C to
DisplayPort cable.
* Try fewer monitors.
You should be ab
** No longer affects: gnome-shell
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2102063
Title:
gnome-shell crashed with SIGSEGV in
_cogl_pipeline_layer_numbers_equal() from
compare_entry_layer_n
If one of the monitors remains black, you may have to tell it to change
input (to HDMI).
If one of the monitors is flashing, that usually means you've run out of
bandwidth but it was noticed too late. So try fewer monitors or a
different cable.
--
You received this bug notification because you a
** Summary changed:
-
/usr/bin/gnome-shell:11:_cogl_pipeline_layer_get_authority:_cogl_pipeline_layer_get_unit_index:_cogl_pipeline_update_layers_cache:_cogl_pipeline_foreach_layer_internal:_cogl_pipeline_get_layer_info
+ gnome-shell crashed with SIGSEGV in _cogl_pipeline_layer_get_authority() fr
** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues #595
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/595
** Also affects: gnome-settings-daemon via
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/595
Importance: Unknown
Status:
** Package changed: ubuntu => linux-hwe-6.11 (Ubuntu)
** Changed in: linux-hwe-6.11 (Ubuntu)
Status: Invalid => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106371
Title:
32:9 reso
Did it leave a .uploaded file behind? If so then what's in that?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089709
Title:
Ubuntu 24.04 (X11) sometimes logs in to a black screen with only an X
Thank you for reporting this bug to Ubuntu.
Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
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 anymore. But
OK, the EDID problem is too significant to not be a factor here. It
means the display is not connected properly or is faulty. So gnome-shell
can start up but it might treat the machine as having no display
connected. Although in theory it should just treat the display as
connected but low resolutio
If I could reproduce it myself then I would probably look at making
Mutter ignore all monitor events for a second or two after it has been
told to go to sleep. But if I can't reproduce the bug then I can't test
fixes for it.
--
You received this bug notification because you are a member of Ubuntu
You need to use USR1, not USR.
Also I get the impression this machine is not up to date, which might
cause crash reports to be rejected. Please do this first:
sudo apt update
sudo apt full-upgrade
and then reboot. Then reproduce the bug and try to capture a crash.
--
You received this bug
** Package changed: xorg (Ubuntu) => mate-desktop (Ubuntu)
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106417
Title:
t
When was the last update on the machine prior to 2025-04-03 16:48:02?
And what did it contain?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106284
Title:
Path of Titans game mouse pan broken since
That's a new one.
The first thing I notice is that this is an Intel Lunar Lake chip
running a relatively old 6.11 kernel. Even with kernel 6.14, Lunar Lake
has been a bit buggy recently... Please try adding a kernel parameter:
xe.enable_psr=0
** Package changed: xorg (Ubuntu) => gnome-shell (U
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Won't Fix
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106
** Tags added: oracular
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083772
Title:
System gets blank/black screen after login
To manage notifications about this bug go to:
https://bugs.launchpad.
** Changed in: gnome-shell (Ubuntu)
Milestone: None => plucky-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1991001
Title:
Can't move (or see) the mouse cursor during desktop zoom
To ma
This probably is not a software bug...
https://discourse.ubuntu.com/t/the-display-bug-we-cant-fix/57434
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
That machine hasn't reported any crashes since 2023(!?). Maybe give it
some time for processing and the new one will show up tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089709
Title:
Ub
It looks like you might be daisy chaining the two external monitors(?).
So if you can't easily get new cabling then just plugging in one monitor
at a time would be the next best thing to try.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Please upload the crash file using the 'ubuntu-bug' or 'apport-cli'
tools. We can't read crash files manually.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089709
Title:
Ubuntu 24.04 (X11) sometim
No I mean to the second, and date.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083772
Title:
System gets blank/black screen after login
To manage notifications about this bug go to:
https://bugs
** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-
ubuntu-dock (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106321
Title:
Can not open usb storage from dock icon
To manag
Thanks for the bug report. Please start by deleting any local
extensions:
cd ~/.local/share/gnome-shell/
rm -rf extensions
and then log in again. Does the problem still occur after that?
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
If the bug only occurs in Wayland/Xwayland then I'm not sure how 'xorg'
or 'xorg-server' are relevant. More likely some other package got
updated. Perhaps
https://launchpad.net/ubuntu/+source/xwayland/2:23.2.6-1ubuntu0.5 ?
** Package changed: xorg (Ubuntu) => ubuntu
--
You received this bug noti
See also bug 2106273
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971558
Title:
dropbox menu icon often replaced with three dots under Jammy
To manage notifications about this bug go to:
https://
It looks like bug 1971558.
** Summary changed:
- In the Gnome panel Telegram and another app are shown wrongly
+ In the indicators panel Telegram and another app are shown wrongly
** Package changed: gnome-session (Ubuntu) => gnome-shell-extension-
appindicator (Ubuntu)
--
You received this bu
The biggest problem I can see here is gnome-shell crashing with "XIO:
fatal IO error 4". So please add MUTTER_SYNC=1 to /etc/environment and
reboot. Then next time the problem occurs, please:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID
** Summary changed:
- I can not login in
+ I can not log in again after logging out [Xorg]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106224
Title:
I can not log in again after logging out [Xor
Three issues there:
1. The i915 kernel driver is crashing(?) on startup (I've seen this in
another bug report too):
i915 :00:02.0: [drm] Port B asks to use VBT vswing/preemph tables
2. The Bluetooth kernel driver is taking 20-30 seconds to start up
(download firmware?).
3. Again "nvidia:
** Bug watch added: gitlab.gnome.org/GNOME/totem/-/issues #204
https://gitlab.gnome.org/GNOME/totem/-/issues/204
** Also affects: totem via
https://gitlab.gnome.org/GNOME/totem/-/issues/204
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are
Please also run:
lspci -k > lspci.txt
journalctl -b0 > journal.txt
grep . /sys/class/drm/*/modes > modes.txt
and attach the resulting text files here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/b
Thanks for the bug report. Please run this command to gather additional
information about the system:
apport-collect 2100990
** Package changed: gnome-control-center (Ubuntu) => gnome-shell
(Ubuntu)
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug
Interesting when you log into gnome-shell on Xorg that the Xorg server
then reports all its input devices are being removed(!). So it sounds
like either a VT switch is happening at the wrong time (after the gnome-
shell user session has started), or that gnome-shell is frozen, or both.
This might a
https://lore.kernel.org/lkml/20250404090108.211-1-juerg.haefli...@canonical.com/
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Jürg Häfl
Please turn the proposed fix into a merge request at:
https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests
** Changed in: gnome-shell (Ubuntu)
Assignee: (unassigned) => Jérôme Brenier (jbre)
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => In Progress
--
You received
Noble was merged (but not yet uploaded or released). Before we proceed
though, it looks like Oracular is missing a fix.
** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu Noble)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member
It looks like the kernel can't detect the monitor resolution over the
VGA cable. Please try a digital cable if you can, like DisplayPort or
HDMI.
** Summary changed:
- Can't Change Resolution To 1920*1080
+ i915+VGA: Can't Change Resolution To 1920*1080
** Package changed: xorg (Ubuntu) => linux
** Summary changed:
- Gnome 48 - unable to change power mode
+ Gnome 48 - unable to change power mode, stuck in Performance mode when on AC
power
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106268
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
Tracking in: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5781
But see also:
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6770
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/1312
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5781
https://gitlab.gnome.org/G
** Tags added: 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/1876632
Title:
[nvidia] Corrupted/missing textures when switching users, switching
VTs or resuming from suspend
To mana
No, I've updated the release notes now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2081140
Title:
Poor desktop frame rate in Nvidia Wayland sessions
To manage notifications about this bug go to:
No it shouldn't. Looks like a bunch of copy and paste from 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/2064205
Title:
Optimize cross-GPU multi-monitor syncs
To manage notifications about t
** Changed in: gtk4 (Ubuntu)
Milestone: ubuntu-25.04-beta => None
** Changed in: mesa (Ubuntu)
Milestone: ubuntu-25.04-beta => None
** Changed in: gtk4 (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: mesa (Ubuntu)
Status: Triaged => Incomplete
--
You received this
The issue might be caused by a faulty USB hub. Although in an ideal
world, the Linux kernel wouldn't hang so much of the system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2104949
Title:
[Asus Pr
** Description changed:
+ https://errors.ubuntu.com/problem/8d91218b809bc23879a6325c4eba1c9d4729cd0d
+ https://errors.ubuntu.com/problem/6dd9b56f7dca6ce92e88daa30d67bef17aca57ab
+
I got errors instead of the plymouth splash screen related to libply.
Unfortunately I couldn't find the logs for t
** Tags removed: desktop-needs-sru
--
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 crashes on startup with SIGSEGV in
__GI_getenv("EXPAT_ACCOUNTING_DEBUG") from getDebugLe
This is because you're missing a kernel graphics driver again...
Please try booting from a real USB drive.
** Package changed: gnome-shell (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
IIRC, I do not have upload rights to Plymouth. Can someone please just
cherry-pick the relevant fixes for Plucky?
1.
https://gitlab.freedesktop.org/plymouth/plymouth/-/commit/63597f92d108237a3ab7d2343a602a95e4e5
2.
https://gitlab.freedesktop.org/plymouth/plymouth/-/commit/5c10072a978dd756655
** Changed in: firefox (Ubuntu)
Importance: High => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2103980
Title:
Firefox is slow and using software rendering on Intel Lunar Lake
To manage
** Changed in: mutter (Ubuntu)
Milestone: ubuntu-25.04 => plucky-updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2102064
Title:
gnome-shell crashed with SIGSEGV in
_cogl_pipeline_fragmen
This usually means the last session crashed during logout, which you
don't really notice at the time.
Most likely it will be bug 2099658, but there's not enough information to prove
it yet. Try steps 2-3:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
Uploaded:
https://launchpadlibrarian.net/786165601/mutter_48.1-1ubuntu2_source.changes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2106097
Title:
Mouse cursors don't animate in Mutter 48.1
To man
Can you confirm the exact date and time the screen last went black?
** Changed in: gnome-shell (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/2083772
Title:
The new plan for 25.10:
1. https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/290, for
cleanliness and to get
https://gitlab.freedesktop.org/plymouth/plymouth/-/merge_requests/323
included.
2. Ubuntu to use plymouth.use-simpledrm by default.
** Bug watch added: gitlab.freedesktop.org/plym
It appears you have recurring kernel hangs in "typec_ucsi". Unplugging
any USB-C cables might solve it.
** Package changed: mutter (Ubuntu) => linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: Incomplete => New
** Summary changed:
- Computer freezes and will not respond to key comman
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 keep using 'nvidia-
drm.modeset=0' and follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
** Changed in: mesa (Ubuntu)
Importance: Undecided => Critical
** Changed in: mesa (Ubuntu)
Milestone: None => ubuntu-25.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2101817
Title:
gnome
** Summary changed:
- screen corruption (hint text and launched icons bleed through desktop and all
applications)
+ Hint text and launched icons bleed through desktop and all applications
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
It appears Xorg sessions are good at avoiding this bug now. The only
problem you might encounter is if you log out, because in Ubuntu 24.10
and later the login screen doesn't use Xorg so will be just as broken as
a Wayland session. To avoid the problem in both cases you can uncomment
'WaylandEnable
Crash IDs are 36-character UUIDs. I'm not sure what the number in
comment #4 represents.
Alternatively you can share the user ID mentioned in comment #5 so we
can find your crash IDs ourselves.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This bug should now track the release status of:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4015 and
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4027
** Tags added: multimonitor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
1 - 100 of 4429 matches
Mail list logo
