unity-panel-service crashed with SIGSEGV in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
This doesn't happen every time, but occurs often.
To reproduce:
1) Hit Alt-F10 to access the top-level menus with the keyboard.
2) Navigate left several times with the left arrow (wrap around the edge of the screen to come around the other side) .
3) I'm trying to get to the volume icon, but it won't go past the date.
4) A few moments later, the crash happens.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: unity-services 7.2.2+14.
ProcVersionSign
Uname: Linux 3.13.0-36-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.4
Architecture: amd64
CompizPlugins: No value set for `/apps/
CrashCounter: 1
CurrentDesktop: Unity
Date: Thu Oct 2 09:18:49 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/
ProcCmdline: /usr/lib/
ProcEnviron:
PATH=(custom, no user)
LANGUAGE=en_CA:en
XDG_RUNTIME_
LANG=en_CA.UTF-8
SHELL=/bin/zsh
SegvAnalysis:
Segfault happened at: 0x7fb36626c766: mov 0x10(%rdx),%ecx
PC (0x7fb36626c766) 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/
?? () from /usr/lib/
g_closure_invoke () from /usr/lib/
?? () from /usr/lib/
g_signal_
Title: unity-panel-service crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to trusty on 2014-05-20 (135 days ago)
UserGroups: adm cdrom dip lp lpadmin plugdev sambashare staff sudo
upstart.
(unity-
(unity-
(unity-
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1350821, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.