** No longer affects: mutter
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Invalid
** Changed in: mutter (Ubuntu)
Status: Confirmed => Invalid
** Changed in: mutter (Ubuntu)
Milestone: noble-updates => None
** Changed in: gnome-shell (Ubuntu)
Milestone:
I believe I figured out what is happening here. In systemd v250, systemd
user managers began interpreting the signal RTMIN+25 as a command to
daemon-reexec. This was done so that:
systemctl kill --kill-whom='main' --signal='SIGRTMIN+25'
'user@*.service'
could be used as a way to reexec all user
** Also affects: systemd (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/2054761
Title:
gnome-shell crashed with signal 5: Settings schema
** Tags added: rls-nn-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054761
Title:
gnome-shell crashed with signal 5: Settings schema
'org.gnome.mutter.wayland' does not contain a key
I have now reproduced the original issue twice:
Settings schema 'org.gnome.mutter.wayland' does not contain a key
named 'xwayland-allow-byte-swapped-clients'
What happened was that gnome-shell 42.9 got SIGKILL'd (along with all
other user processes). And after that the system tries to restart
When trying to reproduce this bug I am seeing fatal errors failing to
find schema 'org.gnome.desktop.peripherals.pointingstick'. Even though
it is installed.
I suspect bug 2065587 is the same issue but am yet to confirm a working
fix.
--
You received this bug notification because you are a
Note to self: Check if bug 2065587 is related.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054761
Title:
gnome-shell crashed with signal 5: Settings schema
'org.gnome.mutter.wayland' does not
** Changed in: mutter (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.
https://bugs.launchpad.net/bugs/2054761
Title:
gnome-shell crashed with signal 5: Settings
Bumping importance since this is officially a blocker:
https://discourse.ubuntu.com/t/noble-numbat-24-04-release-status-tracking/44043
** Changed in: gnome-shell (Ubuntu)
Importance: Medium => High
** Changed in: mutter (Ubuntu)
Importance: Medium => High
** Changed in: mutter (Ubuntu)
** Description changed:
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'
With the latest upload of mutter (46.0-1ubuntu7), we still have `gnome-
shell` crashes during Jammy to Noble upgrades.
Here is a recent oops:
https://errors.ubuntu.com/oops/0ec860d4-fd60-11ee-9dae-fa163ec44ecd
Let me know if you need anything else.
--
You received this bug notification because
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/2054761
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Maybe fixing bug 2060423 would also help here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054761
Title:
gnome-shell crashed with signal 5: Settings schema
'org.gnome.mutter.wayland' does not
** 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/2054761
Title:
gnome-shell crashed with signal 5: Settings schema
'org.gnome.mutter.wayland' does not contain a key named
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.
15 matches
Mail list logo