Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 582786

Summary: gnome-base/gnome-shell-3.18.5 and co. stabilization request (list in comment #1)
Product: Gentoo Linux Reporter: Stefan Langenmaier <stefan.langenmaier+gentoo>
Component: [OLD] GNOMEAssignee: Gentoo Linux Gnome Desktop Team <gnome>
Status: RESOLVED DUPLICATE    
Severity: normal CC: amd64, x86
Priority: Normal Keywords: STABLEREQ
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: emerge --info

Description Stefan Langenmaier 2016-05-11 20:51:48 UTC
Created attachment 434006 [details]
emerge --info

My gnome-shell was segfaulting when I was changing my wifi AP.

In the output of dmesg I had something similar to:
gnome-shell: segfault in libglib-2.0.so.0.4600.2

I found the following two upstream bugs:
* https://bugzilla.gnome.org/show_bug.cgi?id=760924
* https://bugzilla.gnome.org/show_bug.cgi?id=759708

I was able to resolve the issue by downgrading app-crypt/libsecret to version 0.18.3.

And after I had rebuilt gnome-shell with the patch from [1] I was also able to use the current stable version of app-crypt/libsecret 0.18.4


[1] : https://git.gnome.org/browse/gnome-shell/diff/?id=021cecbce289f1d9c68a156d5b8dd204a73bc715
Comment 1 Pacho Ramos gentoo-dev 2016-05-18 10:59:33 UTC
This is a dupe of bug 576262... we should stabilize newer gnome-shell, please check if this is solved with:
gnome-base/gnome-shell-3.18.5
x11-wm/mutter-3.18.4
gnome-base/gdm-3.18.3
app-crypt/libsecret-0.18.5
Comment 2 Stefan Langenmaier 2016-05-20 13:48:39 UTC
With the mentioned packages installed (and no additional patch)
> gnome-base/gnome-shell-3.18.5
> x11-wm/mutter-3.18.4
> gnome-base/gdm-3.18.3
> app-crypt/libsecret-0.18.5

I haven't seen the segfault so far. For me this is resolved with an update.
Comment 3 Pacho Ramos gentoo-dev 2016-05-21 12:16:27 UTC
CCing arches then
Comment 4 Pacho Ramos gentoo-dev 2016-05-30 10:30:55 UTC

*** This bug has been marked as a duplicate of bug 584468 ***