This bug was fixed in the package gnome-shell - 3.28.1-0ubuntu1
---
gnome-shell (3.28.1-0ubuntu1) bionic; urgency=medium
[ Jeremy Bicha ]
* New upstream release
* Drop obsolete patches:
- 27-nm-libexec-path.patch
- fix-wayland-vbox-crash.patch
[ Marco Trevisan (Treviñ
** Changed in: gnome-shell
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1723378
Title:
gnome-shell crashed with SIGTRAP in g_malloc0(
** Changed in: gnome-shell
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1723378
Title:
gnome-shell crashed with SIGTRAP in g_malloc0() fro
** Changed in: gnome-shell
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1723378
Title:
gnome-shell crashed with SIGTRAP in g_malloc0() fro
Right... But only because the code path changed there... And it's *very
likely* due to commit 7015bb2 (but event the apparently right 7f381dd
could have something related), however the code there was just wrong
anyway... So better to fix that uncommit something that could still
crash in other cases
Worth noting this crash is new in 3.26.1 ...
https://errors.ubuntu.com/problem/39ad471656564025f5de8136fcb05bccd9c3e8c7
There are no reports of it prior to 3.26.1
** Tags added: regression-release
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is s
hackel, I agree Launchpad could be made more intelligent. If you like
you can log an enhancement request here:
https://bugs.launchpad.net/launchpad/+filebug
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https:/
The fix is ongoing, thanks
For future cases, in order to provide debug infos, just read this
https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces/Details
#Obtaining_a_stack_and_JS_trace_using_GDB_for_an_already_running_gnome-
shell
Thanks
--
You received this bug notification
I just want to point out that when following the apport bug reporting
process, it initially pulls up a list of existing bugs by searching for
the subject "gnome-shell crashed with signal 5 in g_malloc0()", and this
bug does not show up in that list. In fact, the most recent bug in that
list is fro
** Changed in: gnome-shell
Status: Unknown => Confirmed
** Changed in: gnome-shell
Importance: Unknown => High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1723378
T
Similar upstream bug is also
https://bugzilla.gnome.org/show_bug.cgi?id=788908 (could be the same
root cause)
** Bug watch added: GNOME Bug Tracker #788627
https://bugzilla.gnome.org/show_bug.cgi?id=788627
** Also affects: gnome-shell via
https://bugzilla.gnome.org/show_bug.cgi?id=788627
** Summary changed:
-
/usr/bin/gnome-shell:5:g_malloc0:blur_pixels:_st_create_shadow_pipeline:_st_create_shadow_pipeline_from_actor:st_icon_update_shadow_pipeline
+ gnome-shell crashed with SIGTRAP in g_malloc0() from blur_pixels() from
_st_create_shadow_pipeline() from _st_create_shadow_pipelin
12 matches
Mail list logo