unity-panel-service crashed with SIGSEGV in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
To reproduce it, I:
1) Hit Alt-F10 to access the top panel.
2) Use the left arrow key to move left through the menus.
3) After wrapping around the left side of the screen, and passing the power icon, it is sometimes not possible to pass the date widget. When this happens, a crash occurs a few seconds later.
I often run into this when I'm trying to enable or disable the VPN in the network menu.
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: unity-services 7.3.1+14.
ProcVersionSign
Uname: Linux 3.16.0-24-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CompizPlugins: No value set for `/apps/
CrashCounter: 1
CurrentDesktop: Unity
Date: Fri Nov 21 16:43:46 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: 0x7f1529e5d766: mov 0x10(%rdx),%ecx
PC (0x7f1529e5d766) 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 utopic on 2014-11-11 (12 days ago)
UserGroups: adm cdrom dip lp lpadmin plugdev sambashare staff sudo whoopsie
upstart.
(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.