gwibber crashed with SIGSEGV in watch_submenu()

Bug #805718 reported by Jean-Baptiste Lallement
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
New
Undecided
Unassigned

Bug Description

I clicked on the broadcast item of the message indicator, changed from twitter to identi.ca, clicked on add and then closed the configuration dialog.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gwibber 3.1.0-0ubuntu2 [modified: usr/share/doc/gwibber/changelog.Debian.gz]
ProcVersionSignature: Ubuntu 3.0-3.4-generic 3.0.0-rc5
Uname: Linux 3.0-3-generic i686
Architecture: i386
Date: Tue Jul 5 00:16:29 2011
ExecutablePath: /usr/bin/gwibber
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110209)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x130194a <watch_submenu+58>: mov %edi,0xc(%eax)
 PC (0x0130194a) 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:
 watch_submenu (mi=0x0, menu=0xa076468) at /build/buildd/libdbusmenu-0.4.3/./libdbusmenu-gtk/parser.c:278
 parse_menu_structure_helper (widget=0xa076468, recurse=0xbffd4778) at /build/buildd/libdbusmenu-0.4.3/./libdbusmenu-gtk/parser.c:340
 dbusmenu_gtk_parse_menu_structure (widget=0xa076468) at /build/buildd/libdbusmenu-0.4.3/./libdbusmenu-gtk/parser.c:122
 app_indicator_set_menu () from /usr/lib/libappindicator.so.1
 ?? () from /usr/lib/python2.7/dist-packages/appindicator/_appindicator.so
Title: gwibber crashed with SIGSEGV in watch_submenu()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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.

visibility: private → public
tags: removed: need-i386-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.