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:
I was wrong. Kernel 6.8 is now exhibiting the same bug.
** Changed in: linux (Ubuntu)
Status: Fix Released => Opinion
--
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/2040977
Kernel 6.8 has fixed it for all machines tested so far.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Summary changed:
- [X1 Carbon 10 OLED] Mouse cursor stutters if nothing else is animating on
screen
+ Mouse cursor stutters if nothing else is animating on screen
** Tags added: noble
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
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 2055779
When reporting bugs in the future please use apport by using 'ubuntu-
Public bug reported:
This is from https://askubuntu.com/q/1506260/1004020 .
I'm using Rhythmbox 3.4.7 and as you can see on the picture bellow, there are
some Unnamed options on Rhythmbox's icon right-click menu:
I've tried to copy org.gnome.Rhythmbox.desktop and
Jammy fix for bug 2055519 and bug 2055530
** Patch added: "mutter_42.9-0ubuntu7.debdiff"
https://bugs.launchpad.net/mutter/+bug/2055519/+attachment/5751422/+files/mutter_42.9-0ubuntu7.debdiff
** Changed in: mutter (Ubuntu Jammy)
Status: Fix Committed => In Progress
--
You received
Debdiff proposed in
https://bugs.launchpad.net/mutter/+bug/2055519/comments/3
** Changed in: mutter (Ubuntu Jammy)
Status: Fix Committed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
** Tags added: fixed-in-mutter-45.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/2055530
Title:
Mutter (sometimes) fails to build with [fatal error: meta/meta-enum-
** Tags added: fixed-in-mutter-43.8 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/2055519
Title:
Mutter rebuilds on jammy fail test: mutter:cogl+cogl/conform /
Proposed fixes for the Jammy build failures:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2054510/comments/11
No we didn't cause them :)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
(msg)
AssertionError: 134 != 0
――
27/113 mutter:cogl+cogl/conform / framebuffer-get-bits
FAIL 0.83s exit status 1
-
- [ Test Plan ]
-
- Build mutter
tronger dependencies.
+
+ [ Test Plan ]
+
+ Build mutter.
+
+ [ Where problems could occur ]
+
+ More build failures or accidentally depending on meson features that
+ don't exist in jammy.
+
+ [ Other Info ]
** Changed in: mutter (Ubuntu)
Assignee: Daniel van Vugt (vanvugt) => (unassi
Here's the fixes for jammy build failures in 42.9-0ubuntu6
** Patch added: "mutter_42.9-0ubuntu7.debdiff"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2054510/+attachment/5751114/+files/mutter_42.9-0ubuntu7.debdiff
--
You received this bug notification because you are a member of
https://salsa.debian.org/gnome-
team/mutter/-/commit/9d01e79fa5c26356254df8392ccb5326c8e52637
** Changed in: mutter (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in
Status: Unknown
** Changed in: mutter (Ubuntu)
Status: In Progress => Fix Released
** Also affects: mutter (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: mutter (Ubuntu Jammy)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in:
https://salsa.debian.org/gnome-
team/mutter/-/commit/65b84bfc8a351d39b777e3821559a69d229af68a
** Changed in: mutter (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in
mmy)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: mutter (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: mutter (Ubuntu Jammy)
Status: New => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which i
old issue that you can hit at random in highly parallel
builds. Because meta-enum-types.h is auto-generated its consumers need
to declare stronger dependencies.
** Affects: mutter (Ubuntu)
Importance: Medium
Assignee: Daniel van Vugt (vanvugt)
Status: In Progress
** Tags: jammy
Verified fixed on Mantic using Mutter version 45.2-0ubuntu4.
** Description changed:
[ Impact ]
When using software rendering on Xorg (so usually just in VMs), some
parts of app windows may fail to redraw.
https://gitlab.gnome.org/GNOME/mutter/-/issues/2880
[ Test Plan ]
Oh I see the issue with 'meta-enum-types.h'. It's generated at build
time and most likely someone forgot to declare dependencies on that. So
at random times, depending on how parallel your build is, it might not
be built before it gets included.
--
You received this bug notification because you
mesa (24.0.2-1ubuntu1) noble; urgency=medium
* Merge from Debian.
* radeon-fix-gnome-shell-crash.diff: Fix a regression crashing
gnome-shell. (LP: #2054851)
-- Timo Aaltonen Thu, 29 Feb 2024 09:40:21 +0200
** Changed in: mesa (Ubuntu)
Status: Confirmed => Fix Committed
**
Mantic built OK, except on arm64 and armhf due to known flaky tests. We
can try rebuilding for those.
Jammy failed to build mostly due to a new bug 2055519 (unrelated to our
changes). So we should add a fix for that and roll a new version. amd64
also failed with "fatal error:
Mantic built OK, except on arm64 and armhf due to known flaky tests. We
can try rebuilding for those.
Jammy failed to build mostly due to a new bug 2055519 (unrelated to our
changes). So we should add a fix for that and roll a new version. amd64
also failed with "fatal error:
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: mutter (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
Public bug reported:
27/113 mutter:cogl+cogl/conform / framebuffer-get-bits
RUNNING
>>> RUN_TESTS_QUIET=1
>>>
Stange. Jammy is failing to build for a reason unrelated to anything
that has changed since the last update:
In file included from ../src/backends/meta-backend-private.h:39,
from ../src/backends/x11/meta-backend-x11.h:31,
from
** Changed in: yaru-theme (Ubuntu)
Status: In Progress => Fix Committed
--
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/2036388
Title:
Login screen grey background flickers
Yaru fix proposed: https://github.com/ubuntu/yaru/pull/4050
** Changed in: yaru-theme (Ubuntu)
Status: Triaged => In Progress
** Changed in: yaru-theme (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
--
You received this bug notification because you are a
** Bug watch added: github.com/ubuntu/yaru/issues #4020
https://github.com/ubuntu/yaru/issues/4020
** Changed in: yaru
Status: Fix Released => Unknown
** Changed in: yaru
Remote watch: github.com/ubuntu/yaru/issues #4019 =>
github.com/ubuntu/yaru/issues #4020
--
You received this
** Bug watch added: github.com/ubuntu/yaru/issues #4048
https://github.com/ubuntu/yaru/issues/4048
** Also affects: yaru via
https://github.com/ubuntu/yaru/issues/4048
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
** Changed in: gnome-shell (Ubuntu)
Status: In Progress => Fix Committed
--
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/2036388
Title:
Login screen grey background
Bug 2016925 suggests the problem went away in Ubuntu 23.10
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => New
** Tags added: amdgpu
** Summary changed:
- firefox screen corruption on Athlon 200GE after fresh installation of 22.04.4
+ [amdgpu] Firefox screen corruption on
** 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/2051383
Title:
gnome-shell high CPU utilization when moving a
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 2055351
When reporting bugs in the future please use apport by using 'ubuntu-
The 'gsconnect' extension in particular is known to cause a lot of bugs
so please be sure to remove that.
--
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/2055281
Title:
Desktop
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?
** Changed in: gnome-shell (Ubuntu)
Status: New => Incomplete
--
You received this bug notification
This bug is currently hidden behind bug 1970069, but I do remember this
one. And it still happens on a small minority of machines. It would
happen for everyone if we fixed bug 1970069.
** Also affects: plymouth (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
The bucket is new for 2:23.2.0-1ubuntu0.4 anyway. If the crash also
happened before then and just landed in a different bucket then it
wouldn't be a regression-update.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xwayland in Ubuntu.
The crash is:
https://errors.ubuntu.com/oops/db625975-d614-11ee-ba81-fa163e171f02
which redirects to:
https://errors.ubuntu.com/bucket/?id=failed%3A/usr/bin/Xwayland%3A6%3A/usr/lib/x86_64-linux-
gnu/libc.so.6%2B1c8e6%3A/usr/lib/x86_64-linux-
Please don't attach crash files to bugs because it's a security risk for
yourself. Instead run:
ubuntu-bug /var/crash/YOURFILE.crash
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Invalid
** Attachment removed: "_usr_bin_nautilus.1000.crash"
** Changed in: systemd (Ubuntu)
Status: Won't Fix => In Progress
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: systemd (Ubuntu)
Importance: Low => Medium
--
You received this bug notification because you are
I think some of the warnings are valid, but not all. What regular
expression standard is being followed? If it's POSIX then valid values
for QUOTED_CHAR are documented in
https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap09.html
--
You received this bug notification because you
*** This bug is a duplicate of bug 2054869 ***
https://bugs.launchpad.net/bugs/2054869
** This bug has been marked a duplicate of bug 2054869
Lot of SyntaxWarning messages during install
--
You received this bug notification because you are a member of Desktop
Packages, which is
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
Thanks for the bug report.
Each time you experience a failed boot followed by a successful boot
please run:
journalctl -b-1 > failedboot.txt
And each time you experience a slow boot please run:
journalctl -b0 > slowboot.txt
and attach the resulting text files here.
** Summary changed:
Thanks, yes I'm aware Desktop Icons NG is part of the problem here. I
thought we already had a bug to track that but I can't find it so will
include that here.
** Also affects: gnome-shell-extension-desktop-icons-ng (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
Not sure if that helps but before attempting any of this, plugging the
scanner in shows:
[380225.458610] usb 1-6: new high-speed USB device number 11 using xhci_hcd
[380225.627807] usb 1-6: New USB device found, idVendor=04b8, idProduct=012d,
bcdDevice= 1.00
[380225.627823] usb 1-6: New USB
It seems this as stopped working.
I am still using 23.10 fully patched and I have done as before:
1. purged simple-scan
2. reinstalled
https://launchpad.net/ubuntu/+source/simple-scan/44.0-0ubuntu1/+build/25938600/+files/simple-scan_44.0-0ubuntu1_amd64.deb
<- this fixed the UI link not working
If you run 'sudo evtest', select the mouse and then wiggle it, what kind
of output do you see?
--
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/2051383
Title:
gnome-shell high CPU
** Bug watch added: gitlab.freedesktop.org/plymouth/plymouth/-/issues #241
https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/241
** Also affects: plymouth via
https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/241
Importance: Unknown
Status: Unknown
** Changed in:
This is strange. I've been profiling gnome-shell 42 on jammy and gnome-
shell 46 on noble. Neither have the bug, at least not with my lowly
1000Hz mice (which seems to be the same polling rate as the Razer
DeathAdder V2).
The profile in comment #18 is intriguing because it very clearly shows
Fix proposed:
https://gitlab.freedesktop.org/plymouth/plymouth/-/merge_requests/307
--
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 login screen use
There are lots of amdgpu errors in your system log, so let's start
there.
** Tags added: amdgpu
** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace).
This might be caused by some outdated packages which were installed on
** Tags added: bionic jammy mantic noble
** Summary changed:
- Xorg crashed with assertion failure (usually in a VM) at [privates.h:121/122:
dixGetPrivateAddr: Assertion `key->initialized' failed] and call stack comes
from DRIMoveBuffersHelper
+ Xorg crashed with assertion failure (usually in
*** This bug is a duplicate of bug 1861609 ***
https://bugs.launchpad.net/bugs/1861609
** This bug has been marked a duplicate of bug 1861609
Xorg crashed with assertion failure (usually in a VM) at
[privates.h:121/122: dixGetPrivateAddr: Assertion `key->initialized' failed]
and call
*** This bug is a duplicate of bug 1861609 ***
https://bugs.launchpad.net/bugs/1861609
** This bug has been marked a duplicate of bug 1861609
Xorg crashed with assertion failure (usually in a VM) at
[privates.h:121/122: dixGetPrivateAddr: Assertion `key->initialized' failed]
and call
Turns out we don't need to change mutter at all. I just failed to
understand its complicated scale selection rules. I've proposed a
simplification to mutter anyway:
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3616
but it's no longer required to fix this bug.
** Changed in: mutter
** Changed in: plymouth (Ubuntu)
Status: Opinion => In Progress
--
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 login screen use different
It looks like plymouth's threshold for scale 200% is 192 DPI. And gnome-
shell's threshold is 135 DPI. Since my laptop with the bug is 201 DPI it
should be scale 200% for both mutter and plymouth. I think there's a
simple math error in mutter though, leading to 100% being chosen instead
of 200%.
** Changed in: plymouth (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
CurrentDmesg.txt shows the Nvidia kernel driver crashing, which is
probably not helpful. But also...
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
** Summary changed:
- gnome-shell crashed with SIGSEGV in radeon_bo_reference()
+ gnome-shell (and Xorg) crashes with SIGSEGV in radeon_bo_reference()
** Tags added: rls-nn-incoming
** Summary changed:
- gnome-shell (and Xorg) crashes with SIGSEGV in radeon_bo_reference()
+ [radeon]
*** This bug is a duplicate of bug 2054851 ***
https://bugs.launchpad.net/bugs/2054851
Yes the addresses in your crash match those of bug 2054851.
[ 149.655] (EE) 2: /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
(radeon_drm_winsys_create+0x27e5) [0x7a53429ea2e5]
[ 149.658] (EE) 3:
*** This bug is a duplicate of bug 2054851 ***
https://bugs.launchpad.net/bugs/2054851
The log in comment #1 shows Xorg crashing in radeonsi_dri.so, so this
might be bug 2054851. But also...
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like
On another occasion your shell seems to have been killed without
crashing:
Feb 24 14:34:17 systemd[3625]: org.gnome.Shell@wayland.service: Main
process exited, code=killed, status=9/KILL
This can happen as a result of the real-time thread used in mutter. To
work around it I think you can just
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
** Package changed: xorg (Ubuntu) => gnome-remote-desktop (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-remote-desktop in Ubuntu.
https://bugs.launchpad.net/bugs/2054859
Title:
VNC connection issues with 22.04
Status
** Tags added: noble
--
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/1922047
Title:
Touchpad scrolling is too fast
Status in Mozilla Firefox:
Fix Released
Status in GTK+:
Fix
*** This bug is a duplicate of bug 1922047 ***
https://bugs.launchpad.net/bugs/1922047
Yes input is scaled with the display scale in Wayland, but not Xorg.
That's a feature, but also annoying at times. I think this issue has
been logged before but I can't find the right bug, only bug 1902436.
Tracking upstream in:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/10613
** Information type changed from Private to Public
** Summary changed:
- gnome-shell crashed with SIGSEGV
+ gnome-shell crashed with SIGSEGV in radeon_bo_reference()
** Package changed: gnome-shell (Ubuntu) => mesa
*** This bug is a duplicate of bug 2054121 ***
https://bugs.launchpad.net/bugs/2054121
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 2054121, so it is being marked as such. Please
*** This bug is a duplicate of bug 2054121 ***
https://bugs.launchpad.net/bugs/2054121
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 2054121, so it is being marked as such. Please
This bug is closed. Please use bug 1961508 instead.
--
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/1917939
Title:
Windows maximise underneath dock after
Looks like Yaru would need the same fix.
** Also affects: yaru-theme (Ubuntu)
Importance: Undecided
Status: New
** Changed in: yaru-theme (Ubuntu)
Importance: Undecided => Low
** Changed in: yaru-theme (Ubuntu)
Status: New => Triaged
--
You received this bug notification
Fix proposed: https://gitlab.gnome.org/GNOME/gnome-
shell/-/merge_requests/3207
--
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/2036388
Title:
Login screen grey background
The issue in comments #7 and #8 is being tracked separately in bug
2054769.
--
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/1872594
Title:
Ubuntu logo shifts vertically when the
See also bug 1872594.
** Changed in: mutter (Ubuntu)
Importance: Undecided => Low
** Changed in: mutter (Ubuntu)
Status: New => Triaged
** Changed in: plymouth (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Desktop
Packages,
Public bug reported:
Boot animation and login screen use different display scales, on some
(not many) machines.
For example on a Microsoft Surface Laptop 4, Plymouth seems to use scale
2 for the boot screen while GNOME selects scale 1 for the login screen.
This means the Ubuntu logo shrinks.
That's weird. The crash came from a system that already had mutter 45 in
the process of upgrading (bug 2054319). Given the fix already existed in
the new binary, I'm not sure what we could do to stop the old binary
from crashing. Maybe more gentle upgrades somehow?
** Tags removed:
Also the missing key was introduced in mutter-common version 44.0. It
sounds like it must have been installed at the time of the crash, but
not compiled yet?
** Changed in: mutter (Ubuntu)
Status: Fix Released => Incomplete
--
You received this bug notification because you are a member
The tracker-extract crash may be bug 1990630 or bug 1962585, because it
looks like both fixes haven't made it into jammy yet. But also this bug
list probably needs some maintenance:
https://bugs.launchpad.net/ubuntu/+source/tracker-miners
The gnome-shell crash is now tracked in bug 2054761.
--
Fix released in mutter 45.0.
** Tags added: rls-jj-incoming
--
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/2054761
Title:
gnome-shell crashed with signal 5: Settings schema
Public bug reported:
Feb 21 21:39:12 autopkgtest gnome-shell[17945]: Settings schema
'org.gnome.mutter.wayland' does not contain a key named
'xwayland-allow-byte-swapped-clients'
Feb 21 21:39:12 autopkgtest gnome-session-binary[17908]: WARNING: Application
'org.gnome.Shell.desktop' killed by
by Daniel T (thanks BTW),
it does now get a "Start" button, but after clicking it, the color patch
remains white, and it errors out with "internal error".
See the following information from the terminal, and syslog.
```
al@al-Inspiron-7700-AIO:~/Desktop$ sh askubuntu_color_calib
I sent a MR to https://gitlab.gnome.org/GNOME/gnome-control-
center/-/merge_requests/2311 .
My fix still needs to be tested (I don't have a colorimeter), then
backported.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
501 - 600 of 35600 matches
Mail list logo
