gwibber crashed with SIGSEGV in dbusmenu_gtk_parse_menu_structure()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gwibber (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This bug appears when I want open gwibber
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gwibber 3.1.0-0ubuntu2 [modified: usr/share/
ProcVersionSign
Uname: Linux 3.0-3-generic i686
Architecture: i386
Date: Tue Jul 5 10:00:53 2011
ExecutablePath: /usr/bin/gwibber
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=fr_FR.UTF-8
SegvAnalysis:
Segfault happened at: 0x616a94a: mov %edi,0xc(%eax)
PC (0x0616a94a) ok
source "%edi" ok
destination "0xc(%eax)" (0x0000000c) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gwibber
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
dbusmenu_
app_indicator_
?? () from /usr/lib/
Title: gwibber crashed with SIGSEGV in dbusmenu_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #803667, 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.