run crashed with SIGSEGV in dbusmenu_menuitem_get_id()

Bug #729671 reported by Alex Vaystikh
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
libdbusmenu (Ubuntu)
Invalid
Low
Unassigned
lottanzb (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: lottanzb

LottaNZB crashed

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: lottanzb 0.6-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sat Mar 5 16:50:24 2011
ExecutablePath: /usr/share/lottanzb/run
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/lottanzb
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
 LANGUAGE=en_US:en
SegvAnalysis:
 Segfault happened at: 0x7f29cbcd2732 <dbusmenu_menuitem_get_id+18>: mov (%rbx),%rdx
 PC (0x7f29cbcd2732) ok
 source "(%rbx)" (0x64656c62616e65) not located in a known VMA region (needed readable region)!
 destination "%rdx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: lottanzb
StacktraceTop:
 dbusmenu_menuitem_get_id () from /usr/lib/libdbusmenu-glib.so.3
 ?? () from /usr/lib/libdbusmenu-glib.so.3
 g_main_context_dispatch () from /lib/libglib-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0
 g_main_loop_run () from /lib/libglib-2.0.so.0
Title: run crashed with SIGSEGV in dbusmenu_menuitem_get_id()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Alex Vaystikh (bornio) wrote :
Revision history for this message
Severin H (severinh) wrote :

Thanks for taking the time to report this bug. Can this crashed be reproduced, or was it just a one-time hitch? I'm quite certain that the crash isn't due to LottaNZB, but libdbusmenu, which makes the global menu in Ubuntu 11.04 possible.

Changed in lottanzb (Ubuntu):
status: New → Invalid
Revision history for this message
Severin H (severinh) wrote :

Still, it would be interesting to know more about the crash. For instance, were you doing something specific (in LottaNZB) when it happened?

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in libdbusmenu (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

Changed in libdbusmenu (Ubuntu):
status: Incomplete → Invalid
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.