Bug 392279

Summary:	Gnome shell refuses to start with Alternative Status Indicator Extension enabled - SIGTRAP
Product:	Gentoo Linux	Reporter:	Justin Lecher (RETIRED) <jlec>
Component:	Current packages	Assignee:	Gentoo Linux Gnome Desktop Team <gnome>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
URL:	https://bugzilla.gnome.org/show_bug.cgi?id=660520
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	xsession-errors backtrace

Description Justin Lecher (RETIRED) gentoo-dev

2011-11-28 14:17:24 UTC

No error which I can provide, simply the "oops somthing went wrong" window came up. How do I debug this?

Comment 1 Justin Lecher (RETIRED) gentoo-dev

2011-11-28 14:17:52 UTC

Created attachment 294065 [details]
xsession-errors

xsession-errors

Comment 2 Justin Lecher (RETIRED) gentoo-dev

2011-11-28 14:18:52 UTC

Also tried with a complete black account. Same there

Comment 3 Alexandre Rostovtsev (RETIRED) gentoo-dev

2011-11-28 18:50:41 UTC

There is no "alternative status indicator" extenstion in portage.

Perhaps you mean "alternative status menu" or "monitor status indicator"?

Comment 4 Justin Lecher (RETIRED) gentoo-dev

2011-11-28 20:00:59 UTC

alternative status menu
The one with the shutdown menu entry.

Comment 5 Alexandre Rostovtsev (RETIRED) gentoo-dev

2011-12-04 00:48:18 UTC

> (In reply to comment #0)
> How do I debug this?

First, check whether the alternative status menu extension really is at fault. See if you still get the crash if you move /usr/share/gnome-shell/extensions/alternative-status-menu@gnome-shell-extensions.gnome.org/ out of /usr/share/gnome-shell.

If gnome-shell is segfaulting (which it probably is, judging by the log) probably the easiest way to get the backtrace is using abrt. Emerge app-admin/abrt, /etc/init.d/abrt start, run abrt-cli or abrt-gui, tell it to analyze the crash with gdb to get a backtrace. You will get a file called "backtrace" in /var/spool/abrt/ccpp-*/ or ~/.abrt/spool/ccpp-*/ (depending on what options you choose).

Alternatively, you can follow the guide at https://live.gnome.org/GnomeShell/Debugging

Comment 6 Alexandre Rostovtsev (RETIRED) gentoo-dev

2011-12-04 00:50:12 UTC

(In reply to comment #5)
> Emerge app-admin/abrt, /etc/init.d/abrt start, run abrt-cli or abrt-gui

Should be "/etc/init.d/abrt start, make gnome-shell crash, then run abrt-cli or abrt-gui"

Comment 7 Justin Lecher (RETIRED) gentoo-dev

2011-12-05 15:32:18 UTC

Created attachment 294869 [details]
backtrace

abrt bt

Comment 8 Pacho Ramos gentoo-dev

2011-12-08 11:13:45 UTC

(In reply to comment #4)
> alternative status menu
> The one with the shutdown menu entry.

Some changes were applied by upstream that should solve this issue:
http://git.gnome.org/browse/gnome-shell-extensions/log/?h=gnome-3-2

Comment 9 Justin Lecher (RETIRED) gentoo-dev

2011-12-08 11:55:11 UTC

I will test that on monday.

Comment 10 Alexandre Rostovtsev (RETIRED) gentoo-dev

2011-12-11 23:47:19 UTC

I have added a gnome-shell-extensions-3.2.2 ebuild that includes the upstream patches that should fix this crash. Please test.

>*gnome-shell-extensions-3.2.2 (11 Dec 2011)
> 
>  11 Dec 2011; Alexandre Rostovtsev <tetromino@gentoo.org>
>  gnome-shell-extensions-3.2.0-r2.ebuild, +gnome-shell-extensions-3.2.2.ebuild:
>  Bump to 3.2.2 + latest upstream patches. Notable changes: systemMonitor and
>  alternate-tab bugfixes, azerty keyboard compatibility, fixes for
>  alternative-status-menu crashes (should fix bug #392279 reported by jlec).
>  Note that extension IDs in this version have changed; as a result, extensions
>  may have become auto-disabled, and you will need to re-enable them.

Comment 11 Justin Lecher (RETIRED) gentoo-dev

2011-12-12 07:37:36 UTC

Fixed in this version (3.2.2)