unity-panel-service crashed with SIGSEGV in g_variant_new_tuple()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
indicator-appmenu (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I've lost keyboard functionality on the desktop since yesterday. That is, i can't use any keyboard shortcut from the desktop, as would be Super Key for calling the Unity dashbar, alt+f2 for running arbitrary commands, and so on. The only ones that seem to work are ctrl+alt+del and ctrl+fX.
The shortcut keys DO work, however, when ANY application is running and has focus. For example, if i do a ctrl+alt+del, a little popup window appears, informing that the system will restart in 60 seconds. When that window is showing, y can use all the keyboard shortcuts. So, y do ctrl+alt+del to be able to switch desktops, for example, or running applications.
Then, when i run an application (tipically gnome-terminal), unity-panel-service crashes.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: indicator-appmenu 0.3.92-0ubuntu2
ProcVersionSign
Uname: Linux 3.2.0-18-
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Wed Mar 14 12:51:04 2012
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu-Netbook 10.04 "Lucid Lynx" - Release i386 (20100429.4)
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0xb6d88d54: testb $0x4,0x10(%eax)
PC (0xb6d88d54) ok
source "$0x4" ok
destination "0x10(%eax)" (0x00000010) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: indicator-appmenu
StacktraceTop:
?? () from /lib/i386-
g_variant_
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /lib/i386-
Title: unity-panel-service crashed with SIGSEGV in g_variant_
UpgradeStatus: Upgraded to precise on 2012-03-05 (8 days ago)
UserGroups: adm admin audio cdrom dialout lpadmin plugdev sambashare
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 #954645, 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.