budgie-wm crashes immediately when mutter-common has been upgraded to version 46.0

Bug #2058847 reported by scottfk
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
magpie (Ubuntu)
Fix Released
Undecided
Unassigned
mutter (Ubuntu)
New
Undecided
Unassigned

Bug Description

mutter-common 46.0 packages remove the org.gnome.mutter.x11 gconf schema. This causes budgie-wm to crash immediately on login.

Downgrading to 45.3 fixes everything.

$ apt policy mutter-common
mutter-common:
  Installed: 45.3-1ubuntu1
  Candidate: 46.0-1ubuntu1
  Version table:
     46.0-1ubuntu1 500
        500 http://ch.archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages
        500 http://ch.archive.ubuntu.com/ubuntu noble-proposed/main i386 Packages
 *** 45.3-1ubuntu1 500
        500 http://ch.archive.ubuntu.com/ubuntu noble/main amd64 Packages
        500 http://ch.archive.ubuntu.com/ubuntu noble/main i386 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: budgie-core 10.9.1-3ubuntu1
Uname: Linux 6.8.1-060801-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: Budgie:GNOME
Date: Sun Mar 24 16:00:24 2024
InstallationDate: Installed on 2022-03-19 (736 days ago)
InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Release amd64 (20211012)
SourcePackage: budgie-desktop
UpgradeStatus: Upgraded to noble on 2023-11-03 (142 days ago)

CVE References

Revision history for this message
scottfk (scottfk) wrote :
Revision history for this message
fossfreedom (fossfreedom) wrote :

This is because magpie has a dependency on mutter-common.

The schema comes from the mutter ubuntu x11 patch which has been temporarily disabled

https://launchpad.net/ubuntu/+source/mutter/+changelog

Once it has been readded then things will work correctly

Changed in budgie-desktop (Ubuntu):
status: New → Triaged
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

There's also a Noble dist upgrade problem with schemas being tracked in bug 2054761. Keep it in mind in case there's any overlap between the bugs.

Revision history for this message
scottfk (scottfk) wrote :

FYI: Still missing from the latest and greatest mutter-common:

$ sudo apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
  mutter-common
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 47.2 kB of archives.
After this operation, 4,096 B disk space will be freed.
Do you want to continue? [Y/n]
Get:1 http://ch.archive.ubuntu.com/ubuntu noble-proposed/main amd64 mutter-common all 46.0-1ubuntu3 [47.2 kB]
Fetched 47.2 kB in 0s (1,005 kB/s)
(Reading database ... 886859 files and directories currently installed.)
Preparing to unpack .../mutter-common_46.0-1ubuntu3_all.deb ...
Unpacking mutter-common (46.0-1ubuntu3) over (45.3-1ubuntu1) ...
Setting up mutter-common (46.0-1ubuntu3) ...
Processing triggers for libglib2.0-0t64:i386 (2.79.3-3ubuntu5) ...
Processing triggers for man-db (2.12.0-3build4) ...
Processing triggers for libglib2.0-0t64:amd64 (2.79.3-3ubuntu5) ...

$ ls -l /usr/share/glib-2.0/schemas/org.gnome.mutter.x11.gschema.xml
ls: cannot access '/usr/share/glib-2.0/schemas/org.gnome.mutter.x11.gschema.xml': No such file or directory

$ dpkg-query -S org.gnome.mutter.x11
dpkg-query: no path found matching pattern *org.gnome.mutter.x11*

no longer affects: budgie-desktop (Ubuntu)
Changed in magpie (Ubuntu):
status: New → Triaged
Revision history for this message
scottfk (scottfk) wrote :

All good now:

$ ls -l /usr/share/glib-2.0/schemas/org.gnome.mutter.x11.gschema.xml
-rw-r--r-- 1 root root 1117 Mar 31 01:09 /usr/share/glib-2.0/schemas/org.gnome.mutter.x11.gschema.xml

$ dpkg-query -S org.gnome.mutter.x11
magpie-common: /usr/share/glib-2.0/schemas/org.gnome.mutter.x11.gschema.xml

Revision history for this message
scottfk (scottfk) wrote :

$ apt policy mutter-common magpie-common
mutter-common:
  Installed: 46.0-1ubuntu6
  Candidate: 46.0-1ubuntu6
  Version table:
 *** 46.0-1ubuntu6 500
        500 http://ch.archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages
        500 http://ch.archive.ubuntu.com/ubuntu noble-proposed/main i386 Packages
        100 /var/lib/dpkg/status
     46.0-1ubuntu3 500
        500 http://ch.archive.ubuntu.com/ubuntu noble-proposed/main amd64 Packages
        500 http://ch.archive.ubuntu.com/ubuntu noble-proposed/main i386 Packages
     45.3-1ubuntu1 500
        500 http://ch.archive.ubuntu.com/ubuntu noble/main amd64 Packages
        500 http://ch.archive.ubuntu.com/ubuntu noble/main i386 Packages
        500 http://ch.archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages
        500 http://ch.archive.ubuntu.com/ubuntu noble-updates/main i386 Packages
magpie-common:
  Installed: 0.9.3-0ubuntu7
  Candidate: 0.9.3-0ubuntu7
  Version table:
 *** 0.9.3-0ubuntu7 500
        500 http://ch.archive.ubuntu.com/ubuntu noble-proposed/universe amd64 Packages
        500 http://ch.archive.ubuntu.com/ubuntu noble-proposed/universe i386 Packages
        100 /var/lib/dpkg/status
     0.9.3-0ubuntu6 500
        500 http://ch.archive.ubuntu.com/ubuntu noble-proposed/universe amd64 Packages
        500 http://ch.archive.ubuntu.com/ubuntu noble-proposed/universe i386 Packages
     0.9.3-0ubuntu5 500
        500 http://ch.archive.ubuntu.com/ubuntu noble/universe amd64 Packages
        500 http://ch.archive.ubuntu.com/ubuntu noble/universe i386 Packages
     0.9.3-0ubuntu1 500
        500 http://ch.archive.ubuntu.com/ubuntu noble-updates/universe amd64 Packages
        500 http://ch.archive.ubuntu.com/ubuntu noble-updates/universe i386 Packages

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package magpie - 0.9.3-0ubuntu7

---------------
magpie (0.9.3-0ubuntu7) noble; urgency=medium

  * No-change rebuild for CVE-2024-3094

 -- Steve Langasek <email address hidden> Sun, 31 Mar 2024 00:09:41 +0000

Changed in magpie (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.