This bug was fixed in the package libcanberra - 0.30-10ubuntu1
---
libcanberra (0.30-10ubuntu1) jammy; urgency=medium
* Merge with debian, remaining changes:
- Disable login sound by default and hide sound from startup applications
- Install the gtk plugin in the
** Changed in: gnome-shell (Ubuntu)
Status: Triaged => Won't Fix
** Changed in: libcanberra (Ubuntu)
Status: Triaged => Fix Committed
** Changed in: libcanberra (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
--
You received this bug notification because
This is the root issue: https://gitlab.gnome.org/GNOME/glib/-/issues/389
** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #389
https://gitlab.gnome.org/GNOME/glib/-/issues/389
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
If the solution is to remove libcanberra-gtk3-module and since it hasn't
been touched since 2012, do we need to provide it at all?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949200
Title:
** Tags added: dt-303
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949200
Title:
gnome-shell crashed with SIGTRAP from error "Can't create a
GtkStyleContext without a display connection" in
** Description changed:
GNOME Shell isn't meant to use GTK at all, but it's repeatedly crashing
in GTK since the introduction of GNOME 40.
https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0
** Description changed:
GNOME Shell isn't meant to use GTK at all, but it's repeatedly crashing
in GTK since the introduction of GNOME 40.
https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0
Confirmed! The workaround/fix is:
sudo apt remove libcanberra-gtk3-module
Also I can't find an active bug tracker for libcanberra and its last
release was in 2012.
** Package changed: gtk+3.0 (Ubuntu) => ubuntu
** Package changed: ubuntu => libcanberra (Ubuntu)
--
You received this bug
Removed appindicator task because I've confirmed it happens without any
extensions loaded (duplicate bug 1966862).
** No longer affects: gnome-shell-extension-appindicator (Ubuntu)
** Description changed:
GNOME Shell isn't meant to use GTK at all, but it's repeatedly crashing
in GTK since
Seems like killing your Xwayland process is an easy way to reproduce
this crash.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949200
Title:
gnome-shell crashed with SIGTRAP from error "Can't
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell-extension-appindicator (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Seems my development (impish) machine encountered the crash only once,
yesterday, and logged:
Nov 02 13:40:39 kab gnome-shell[1614]: Connection to xwayland lost
Nov 02 13:40:39 kab pulseaudio[1472]: X11 I/O error handler called
Nov 02 13:40:39 kab pulseaudio[1472]: X11 I/O error exit handler
Interestingly, the source of this particular crash is canberra-gtk-
module.c from libcanberra 0.30. That's the latest version but it's also
from 2012 so Wayland support might not be great. It appears you can
safely just uninstall it:
sudo apt remove libcanberra-gtk3-module
so I wonder if
** Description changed:
GNOME Shell isn't meant to use GTK at all, but it's repeatedly crashing
- in GTK.
+ in GTK since the introduction of GNOME 40.
https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0
If we could then it would be nice to mitigate this by simply ensuring
GTK in the gnome-shell process can find the Wayland server automatically
instead of X11. Because if we don't find a blanket solution like that
then we'll keep getting similar gnome-shell crash reports.
** Also affects: gtk+3.0
Like the similar upstream bug
https://gitlab.gnome.org/GNOME/mutter/-/issues/1475, this appears to be
caused by the intersection of:
(a) GTK being used in the gnome-shell process (usually by extensions);
and
(b) The absence of an Xserver for GTK to connect to (Xwayland is only
started
** Tags added: impish
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949200
Title:
gnome-shell crashed with SIGTRAP from error "Can't create a
GtkStyleContext without a display connection" in
The instruction addresses (modulo 16 at least) seem to match up too well
to be a coincidence so I believe this is:
https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0
https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844
** Summary changed:
- gnome-shell crashed with signal 5 error "Can't create a GtkStyleContext
without a display connection" in gtk_style_context_init
+ gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext
without a display connection" in gtk_style_context_init
--
You
19 matches
Mail list logo
