gwibber crashed with SIGSEGV in watch_submenu()

Bug #803714 reported by Fabio Duran Verdugo
108
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
New
Medium
Unassigned

Bug Description

Just open gwibber.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: gwibber 3.1.0-0ubuntu2 [modified: usr/share/doc/gwibber/changelog.Debian.gz]
ProcVersionSignature: Ubuntu 3.0-2.3-generic 3.0.0-rc4
Uname: Linux 3.0-2-generic i686
Architecture: i386
Date: Wed Jun 29 22:00:14 2011
ExecutablePath: /usr/bin/gwibber
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110426)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gwibber
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LC_MESSAGES=en_US.utf8
 LANG=es_CL.utf8
 LANGUAGE=en_US:en
SegvAnalysis:
 Segfault happened at: 0x140a94a <watch_submenu+58>: mov %edi,0xc(%eax)
 PC (0x0140a94a) 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=0xa4e5480) at /build/buildd/libdbusmenu-0.4.3/./libdbusmenu-gtk/parser.c:278
 parse_menu_structure_helper (widget=0xa4e5480, recurse=0xbfd1b5b8) at /build/buildd/libdbusmenu-0.4.3/./libdbusmenu-gtk/parser.c:340
 dbusmenu_gtk_parse_menu_structure (widget=0xa4e5480) 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 vboxusers

visibility: private → public
Revision history for this message
Victor Vargas (kamus) wrote :

this issue seems like a duplicate of bug 803667

visibility: public → private
Changed in gwibber (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Fabio Duran Verdugo (fabioduran) wrote :

Kamus I can't see this bug, I get this message:
Lost something?
There’s no page with this address in Launchpad.
If you got here from a link elsewhere on Launchpad, sorry about that. We’ve recorded the problem, and we’ll fix it as soon as we can.
Otherwise, complain to the maintainers of the page that linked here.
If this is blocking your work, let us know by asking a question at Launchpad Support. Include the error ID OOPS-2008CP7 in your message.

visibility: private → public
Revision history for this message
Victor Vargas (kamus) wrote :

Sorry Fabio, that report is marked as private in this moment because the retracer has not finished his work, yet.

Revision history for this message
Fabio Duran Verdugo (fabioduran) wrote :

Kamus, but my trace is good, is not the same?

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.

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.