run crashed with SIGSEGV in dbusmenu_menuitem_get_id()
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
ProcVersionSign
Uname: Linux 2.6.38-5-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Sat Mar 5 16:50:24 2011
ExecutablePath: /usr/share/
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
InterpreterPath: /usr/bin/python2.7
PackageArchitec
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_
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_
?? () from /usr/lib/
g_main_
?? () from /lib/libglib-
g_main_loop_run () from /lib/libglib-
Title: run crashed with SIGSEGV in dbusmenu_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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.