** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1977634
Title:
Cursor jumps around when reading / editing in
If it looks correct in GNOME then please briefly log into GNOME and run:
xrandr --verbose > gnome-xrandr.txt
and attach the resulting text file here.
Also if KDE has any monitor colour profile settings then try toggling
those.
** Summary changed:
- Notebook screen the look is "matte"
+
Could you test with a different mouse and different keyboard briefly?
Does the bug still occur?
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
** Changed in: mutter (Ubuntu)
Status: Incomplete => New
** Summary changed:
- Weather widgets appear in the wrong position in a Wayland session
+ my-weather-indicator widgets appear in the wrong position in a Wayland session
** Changed in: mutter (Ubuntu)
Importance: Undecided => Low
I can't see anything that would cause this behaviour... Does the same
occur on any other machine? And does the machine have more than one
keyboard?
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
Let's ignore comment #9 because it only affects my desktop with a 27" 4K
monitor. The original laptop this bug was about still works with the
latest proposed fix (which will be rolled into bug 1970069).
--
You received this bug notification because you are a member of Desktop
Packages, which is
*** This bug is a duplicate of bug 2055176 ***
https://bugs.launchpad.net/bugs/2055176
It looks like your system experienced another issue too: sublime_text
used over 40GB of RAM today around 4:01pm, before that caused other
parts of the system to fail and the kernel stepped in and killed
** Changed in: xwayland (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xwayland in Ubuntu.
https://bugs.launchpad.net/bugs/2055176
Title:
Xwayland crashed with SIGSEGV in ProcXTestFakeInput()
*** This bug is a duplicate of bug 2055176 ***
https://bugs.launchpad.net/bugs/2055176
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 2055176, so it is being marked as such. Please
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1977634
When reporting bugs in the future please use apport by using 'ubuntu-
** Changed in: plymouth (Ubuntu)
Status: Won't Fix => In Progress
** Changed in: plymouth (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to plymouth in Ubuntu.
** Changed in: mutter (Ubuntu)
Status: In Progress => Fix Committed
** Tags added: fixed-in-mutter-46.0 fixed-upstream
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2058005
Thanks for the bug report.
Please:
1. Delete any local extensions:
cd ~/.local/share/gnome-shell/
rm -rf extensions
2. Log out and in again.
3. When the problem starts happening run:
journalctl -b0 > journal.txt
ps auxw > ps.txt
4. Attach the resulting text files here.
**
Thanks. You reported the original bug from a Wayland session. Please try
logging out and then selecting the Xorg session on the login screen.
Does the bug still occur?
I suspect that's the main issue here. Not the presence of nvdia-
driver-470 directly, but it will change what default session
No it's not released yet.
** Changed in: tracker-miners (Ubuntu)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tracker-miners in Ubuntu.
https://bugs.launchpad.net/bugs/2055761
Title:
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Also sorry for the two year delay in this case... 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 >
And now there's a new cause of this bug. If I simplify the framebuffer
drivers installed in initrd then it causes i915 to take 10 seconds to
start, whereas Plymouth stopped waiting for it at the 8 second mark and
so fell back to using SimpleDRM.
--
You received this bug notification because you
Plymouth would still need patching in order to optimize the drm modules
in debian/local/plymouth.hook
** Changed in: plymouth (Ubuntu)
Status: Invalid => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to plymouth in
)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => Low
** Changed in: initramfs-tools (Ubuntu)
Status: New => In
Public bug reported:
There is black flicker on some systems between the login screen and
desktop startup.
A fix is in progress:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3659
** Affects: mutter (Ubuntu)
Importance: Low
Status: In Progress
** Tags: flickerfreeboot
I was wrong. You only get the wrong scale in Plymouth if you blacklist
your native DRM driver as I had for testing. Otherwise Plymouth will
wait for a preferred driver instead of using SimpleDRM immediately.
So bug 2054769 is still fixed by the patch in comment #5.
--
You received this bug
*** This bug is a duplicate of bug 2056506 ***
https://bugs.launchpad.net/bugs/2056506
I'm guessing the crash was bug 2056506 and you just received the fix.
"@^@^@^@^@" is not related - I think that comes from special keys being
(incorrectly) handled by the system console. You can log a new
** Tags removed: hirsute
** Tags added: mantic
** Changed in: gnome-shell (Ubuntu)
Status: Won't Fix => Confirmed
** Changed in: mutter (Ubuntu)
Status: Won't Fix => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
*** 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
Thanks for the bug report. Please attach a screenshot of the problem and
also run this command to automatically gather more system information:
apport-collect 2057964
** Package changed: xorg-server (Ubuntu) => gnome-shell-extension-appindicator
(Ubuntu)
** Tags added: jammy nvidia
**
The log message in comment #19 is being tracked in bug 1968910.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/2056506
Title:
ubuntu-dock 89 crashes on
Since this bug has expired it would be useful to get a fresh bug report.
Please run:
ubuntu-bug gnome-shell
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1761382
Title:
Unable to
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2055519
Title:
Mutter rebuilds on jammy fail test:
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2055530
Title:
Mutter (sometimes) fails to build with [fatal
Verified fixed on jammy using mutter version 42.9-0ubuntu7 and the test
plan in the bug description.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification
Building 42.9-0ubuntu7 succeeded on all architectures.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
Building 42.9-0ubuntu7 succeeded on all architectures.
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
If by "yes" in comment #1 you mean the same issue occurs with wired,
then it sounds like there are two separate bugs. Because in comment #2
it sounds like PulseAudio's Bluetooth support was the original problem.
And I know other people have reported the same. It's unfortunate that
Ubuntu 22.04 was
** Bug watch added: Debian Bug tracker #1064123
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064123
** Also affects: mesa (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064123
Importance: Unknown
Status: Unknown
--
You received this bug notification
It looks like this will need fixing again in future :(
While working on bug 1970069 I've found simpledrm causes Plymouth to
choose a different default scale again.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
This appears to be the most common (and currently only) recurring gnome-
shell crash being reported in Noble:
https://errors.ubuntu.com/problem/bf714caff944bed915a3c4321664107c65547d1f
Although you have to dig into the individual reports and check their
journals to confirm they're bug 2054761.
Thanks for the bug report. Does the same problem occur with wired
headphones/speakers?
** Package changed: gnome-shell (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is
Thanks for the bug report. This is a common problem and is almost always
due to a bad connection or low quality cable. Please try unplugging and
replugging the cable at both ends. If that doesn't solve it then please
try a different cable. For better performance and reliability on a
Lenovo G50-70,
https://github.com/micheleg/dash-to-
dock/commit/255ef10db9c330643188faca5ea82093f7ad0bb0
** Summary changed:
- GNOME Shell crashes with signal 6 when right clicking on the dock
[clutter_actor_dispose: assertion failed: (priv->parent == NULL)]
+ ubuntu-dock 89 crashes on gnome-shell 45 with
The dock fix isn't actually a fix, it's just a workaround:
https://github.com/micheleg/dash-to-dock/commit/46b81aeb4bf18d2f8a75fbf2d0ef6c047f3711f2
I expect that if we can get a proper fix into gnome-shell then the
workaround can be removed.
--
You received this bug notification because you are
*** This bug is a duplicate of bug 2056506 ***
https://bugs.launchpad.net/bugs/2056506
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 2056506, so it is being marked as such. Please
The same extension that crashes on gnome-shell 45 seems to work reliably
on gnome-shell 46 built from upstream main.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => High
** Changed in:
OK windowPreview.js isn't the only place it can happen. The logs in
comments #2 and #3 show it happening in popupMenu.js too.
** Summary changed:
- GNOME Shell crashes when I close any application by right click in the dock
[clutter_actor_dispose: assertion failed: (priv->parent == NULL) from
I managed to get the same crash by right clicking on the dock and not
trying to close anything:
gnome-shell[3416]:
Clutter:ERROR:../clutter/clutter/clutter-actor.c:5476:clutter_actor_dispose:
assertion failed: (priv->parent == NULL)
gnome-shell[3416]: Bail out!
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #7472
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7472
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7472
Importance: Unknown
Status: Unknown
--
You received this bug
Next time this happens, please reboot and then run:
journalctl -b-1 > prevboot.txt
and attach the resulting text file here. Most likely it is bug 2056506.
** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu)
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Incomplete
--
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
** Summary changed:
- Mouse toggle in the screenshot/screencast dialog is hard to discover that
it's a button
+ Mouse pointer toggle in the screenshot/screencast dialog is hard to discover
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Tracking in https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6847
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #6847
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6847
** Changed in: gnome-shell (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-shell
This looks like just bad UI design. The option to include the pointer
already exists but it's disabled by default and not obvious because the
button looks exactly like the mouse pointer itself (bottom right of the
dialog). Please select that option in the screen recorder dialog before
starting the
*** This bug is a duplicate of bug 2056506 ***
https://bugs.launchpad.net/bugs/2056506
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 2056506, so it is being marked as such. Please
Please check the headphone is in pairing mode, and try pairing something
else like a mouse if you can.
I can see only one other bug with the same Bluetooth chip having similar
issues: bug 1887968
** Summary changed:
- i could not able to connect my bluetooth headphone or for context any
This suggests the menu is an override-redirect X11 window, so perhaps
appearing on all workspaces is 'correct' and it is a bug in Firefox.
Please also try logging into a Wayland session.
** Package changed: xorg (Ubuntu) => firefox (Ubuntu)
** Changed in: firefox (Ubuntu)
Status: New =>
** Tags removed: kinetic lunar rls-ll-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1961508
Title:
Dock displaying over window after resuming from
*** 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
Although https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6868 looks
the same, it would have to have the same caller as this bug (ubuntu-
d...@ubuntu.com/windowPreview.js:642)
** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-
ubuntu-dock (Ubuntu)
** Changed in:
https://salsa.debian.org/gnome-
team/mutter/-/commit/edfd49ea2224aa9d5fbe4ed32c2ab40443046fc5
** Changed in: mutter (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://salsa.debian.org/gnome-
team/mutter/-/commit/7f3b3fa18bca658cbc6c7fa98295b169c8f38793
** Changed in: mutter (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
** Changed in: initramfs-tools (Ubuntu)
Status: Opinion => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/1970069
Title:
Annoying boot messages interfering with splash
Thank you for reporting this bug to Ubuntu.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.
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.
Public bug reported:
Plymouth's hidden console contains squares instead of bold text on live
session shutdown.
You can see it by pressing Escape instead of Enter.
It seems somewhat related to the fix for bug 1942987, which only
preloads non-bold text for the live session shutdown splash.
**
Also everything is back in git again:
https://salsa.debian.org/ubuntu-dev-team/plymouth/-/commits/ubuntu/main
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2054769
Title:
Boot
Here's the fix for Noble.
** Patch added: "plymouth_24.004.60-1ubuntu5.debdiff"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2054769/+attachment/5753977/+files/plymouth_24.004.60-1ubuntu5.debdiff
--
You received this bug notification because you are a member of Desktop
Packages,
** Changed in: plymouth (Ubuntu)
Status: Fix Committed => In Progress
** Tags added: mantic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2054769
Title:
Boot animation and
Indeed this doesn't seem to have happened since 2020.
** No longer affects: mutter (Ubuntu)
** No longer affects: plasma-desktop (Ubuntu)
** Changed in: gdm3 (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You
That's very unusual. Please start by deleting any local extensions:
cd ~/.local/share/gnome-shell/
rm -rf extensions
and then log in again.
If the bug still occurs after that then please follow these steps:
1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 >
Kai-Heng Feng, please remember to verify mantic.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2051074
Title:
Mirror mode doesn't work when panel only supports one refresh rate
That failing test case:
1180s # FAIL: mutter-13/minimized.test (Child process exited with code
133)
is known to be flaky. I've seen it fail on unrelated changes upstream.
And it is indeed unrelated to these changes.
The rebuild has now succeeded:
That failing test case:
1180s # FAIL: mutter-13/minimized.test (Child process exited with code
133)
is known to be flaky. I've seen it fail on unrelated changes upstream.
And it is indeed unrelated to these changes.
The rebuild has now succeeded:
I encountered the same kind of corruption on AMD graphics last night.
Using Firefox on Wayland in Ubuntu 24.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
https://bugs.launchpad.net/bugs/2055351
** Also affects: xorg-server (Ubuntu Noble)
Importance: Medium
Status: Triaged
** Also affects: xorg-server (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: xorg-server (Ubuntu Jammy)
Status: New => In Progress
** Changed in: xorg-server (Ubuntu Noble)
I've analysed a couple of Noble systems today and don't think initramfs-
tools needs improving (although it might not hurt). On both systems,
plymouth-start was within 1 second of simpledrm starting (same
timestamp), but the bug still occurs. The reasons are:
1. One system actually experiences
** Changed in: mutter (Ubuntu)
Importance: High => Medium
** Changed in: mutter (Ubuntu Jammy)
Importance: High => Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2055519
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => Medium
** Changed in: initramfs
Similar, yes. But we can't treat them as the same bug when one was
declared fixed in Firefox in September 2023, and the other declared a
problem in Firefox in February 2024.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
The fix is also missing from Noble so please start with Noble.
** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1387
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1387
** Also affects: xorg-server via
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1387
This might be helpful:
https://support.mozilla.org/en-US/kb/firefox-uses-too-much-memory-or-
cpu-resources
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/2056197
Title:
Desktop
Perfect, thanks. That log shows clearly that the kernel ran out of
memory, and the main causes are:
1. Firefox
2. Thunderbird
3. Teams
4. GNOME Shell
It seems to be only one Firefox tab causing most of the problem (10
gigabytes).
** Package changed: ubuntu => firefox (Ubuntu)
** Changed in:
Tracking upstream in: https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/5316
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Triaged
** Tags added: visual-quality
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5316
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5316
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5316
Importance: Unknown
Status: Unknown
** Changed in: gnome-shell
We can't track Archlinux bugs here.
Everyone please check your xwayland package versions because bug 2055176
may have affected Noble until recently, and still does affect Mantic.
You need xwayland >= 23.2.4 to fix that.
--
You received this bug notification because you are a member of Desktop
The HDMI port on that laptop is only 1.4b so probably cannot support the
monitor. Yes please do use USB-C for external monitors if you can.
** Changed in: mutter (Ubuntu)
Status: Expired => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which
** Also affects: xwayland (Ubuntu)
Importance: Undecided
Status: New
** Also affects: xorg-server via
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1648
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Does the problem occur if Firefox is never opened?
Do you find any files in /var/crash ?
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Thanks for the bug report. It sounds like Firefox is the issue here, but
to be sure please run 'top' in a Terminal window to confirm it is
Firefox using all the CPU.
Also be careful to avoid having too many tabs open, because modern web
browsers can easily use all the system resources if there
Thanks for the additional information. It looks like we have a better
idea of the crash location now:
?? ()
ProcXTestFakeInput (client=) at ../Xext/xtest.c:440
Dispatch () at ../dix/dispatch.c:545
dix_main (envp=, argv=, argc=) at
../dix/main.c:271
main (argc=, argv=, envp=) at
Found it:
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1574
The first fix went into Xwayland 23.2.1 but that also needed fixing in
23.2.4.
** Changed in: xwayland (Ubuntu)
Status: Incomplete => New
** Changed in: xwayland (Ubuntu)
Status: New => Fix Released
** Tags
Please open the Additional Drivers app and use it to install an Nvidia
driver. Then reboot and tell us if the problem persists.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
** Summary changed:
- Xorg freeze
+ Freeze
--
You received this
This sounds like a per-application bug, but also something we would like
gnome-font-viewer to handle.
** Changed in: xorg (Ubuntu)
Importance: Undecided => Low
** Summary changed:
- Choosing font
+ Apps can't handle tens of thousands of fonts installed at once
** Package changed: xorg
Please attach the video again with a filename using Latin characters
only. Launchpad can't handle other character sets :(
Please also execute the following command only once, as it will
automatically gather debugging information, in a terminal:
apport-collect 2055762
When reporting bugs in
** Tags added: mantic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/2055783
Title:
"Unnamed" actions on Rhythmbox's icon right-click menu
Status in rhythmbox package in Ubuntu:
Also tracking in
https://errors.ubuntu.com/problem/83ecd6e2e63698177b9836166fc3a22637158935
** Changed in: totem (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
*** This bug is a duplicate of bug 2055692 ***
https://bugs.launchpad.net/bugs/2055692
** This bug has been marked a duplicate of bug 2055692
crash: malloc(): corrupted top size
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
The fix is trivial:
https://gitlab.gnome.org/GNOME/tracker-miners/-/merge_requests/511
But it begs the question: Why do we keep having to fix these crashes one
by one over such a long period of time?
** Tags added: rls-nn-incoming
** Changed in: tracker-miners (Ubuntu)
Milestone: None =>
** Summary changed:
- Large Performance Regression in gnome-shell from Ubuntu Jammy to Ubuntu Noble
+ Large Performance Regression in fullscreen windows from Ubuntu Jammy to
Ubuntu Noble
** No longer affects: gnome-shell (Ubuntu)
** Also affects: mutter via
Unless your log mentions "clutter_actor_get_real_resource_scale" or
"guessed_scale", I fear most people will land here by accident. The
reason seems to be that our bots don't adequately distinguish between
different assertion failures, which is bug 1982283.
The log in comment #20 doesn't even
Please put that in a new bug so we don't confuse this 12 year old bug.
** No longer affects: gnome-desktop (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/1048163
Title:
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Invalid
** Summary changed:
- Desktop freeze while navigating the Dash
+ Desktop freeze while navigating the Dash (if the gsconnect extension is
installed)
--
You received this bug notification because you are a member of
This bug is closed. But also please refrain from reporting multiple
different issues at the same time.
The current problem with a blank window is being tracked in:
https://github.com/canonical/ubuntu-desktop-installer/issues/2418
For everything else, please open new bugs.
** Bug watch added:
401 - 500 of 31942 matches
Mail list logo
