unity-panel-service crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()

[Edward Donovan]

I tried to open the panel menus. Probably by keyboard first. The panel froze & crashed. No unusual circumstances that I noticed.

I don't know if this will be relevant, but: since recently trying KDE packages on this machine, KDE's settings seemed to have fouled up Unity's, when I returned. Many of the indicator icons were wrong or missing. Attempts to clear the settings, remove KDE packages, and restart, didn't make any difference. But after this crash, weeks later, the usual icons were finally restored. Seems strange.

Thanks.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: unity-services 7.1.2+13.10.20131014.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.11.0-18.32-generic 3.11.10.4
Uname: Linux 3.11.0-18-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
Date: Sat Mar 1 00:14:03 2014
ExecutablePath: /usr/lib/unity/unity-panel-service
MarkForUpload: True
ProcCmdline: /usr/lib/unity/unity-panel-service
ProcEnviron:
 PATH=(custom, no user)
 LANGUAGE=en_US
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f8097fa93a6: mov 0x10(%rdx),%ecx
 PC (0x7f8097fa93a6) ok
 source "0x10(%rdx)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libido3-0.1.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: unity-panel-service crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to saucy on 2014-01-16 (43 days ago)
UserGroups: adm cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo wireshark

[Edward Donovan (edward.donovan)]

I have continued to get this crash, periodically. I think the circumstance that triggers it is, generally at least:

1. opening the app menus in the panel via keyboard shortcuts, then
2. hitting left-arrow to wrap around and access the indicator menus

Doing the above does not reproduce the crash every time.

I have not seen it happen, I think, when I hit right-arrow, to start on the leftmost indicator applet. Just the left-to-wrap-right move. The indicator-session opens, and often the menu stays stuck open for a while.

Incidentally, this behavior is a workaround for the loss of HUD access to indicator menus. (I suppose it may be what I did before the HUD arrived; I don't remember clearly.)

Thanks, Marco!

[Edward Donovan (edward.donovan)]

Hm, to clarity:

"The indicator-session opens, and often the menu stays stuck open for a while."...as the panel crashes. That's how I first know the crash has happened again

What I wanted to convey was that the rightmost indicator menu opens, and then the crash freezes it; my continued right-arrow inpuds. Not every time. Whether that means that particular indicator is involved, or the next one, date/time, that never opens--or whether that means anything--I am not knowledgeable enough to say.

Thank you.

[Marco Trevisan (Treviño) (3v1n0)]

Unfortunately the stack trace doesn't say much... Would you be able to install the unity debug symbols and then attach to the process with gdb [1] to get something more useful?

[1] https://wiki.ubuntu.com/Unity/FilingBugs#Getting_a_stack_trace

[Launchpad Janitor (janitor)]

[Expired for Unity because there has been no activity for 60 days.]

[Launchpad Janitor (janitor)]

[Expired for unity (Ubuntu) because there has been no activity for 60 days.]