exaile.py crashed with SIGSEGV in dbus_timeout_handle()

Bug #349476 reported by Copernicvs
30
This bug affects 1 person
Affects Status Importance Assigned to Milestone
exaile (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: exaile

jaunty 2.6.28.11
exaile 0.2.14
trying to switch between songs caused a crash

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/exaile/exaile.py
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: exaile 0.2.14-0ubuntu2
ProcCmdline: python /usr/lib/exaile/exaile.py
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_HK.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: exaile
StacktraceTop:
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 ?? () from /lib/libdbus-1.so.3
 dbus_timeout_handle () from /lib/libdbus-1.so.3
 ?? () from /usr/lib/libdbus-glib-1.so.2
Title: exaile.py crashed with SIGSEGV in dbus_timeout_handle()
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev video

Revision history for this message
Copernicvs (kornenator) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:_dbus_connection_lock (connection=0x0) at dbus-connection.c:355
_dbus_pending_call_get_connection_and_lock (
reply_handler_timeout (data=0x8f7b5a8)
dbus_timeout_handle (timeout=0xa6df458)
timeout_handler_dispatch (data=0xa6a87b0)

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in exaile:
importance: Undecided → Medium
Revision history for this message
Andrew Starr-Bochicchio (andrewsomething) wrote :

The Exaile 0.3.x series is a complete rewrite. Ubuntu 9.10 released with version 0.3.0.1, and the current development version of Ubuntu Lucid includes Exaile 0.3.1.0. I can not reproduce this issue, and it has most likely been fixed upstream. Has anyone experienced this issue with Exaile > 0.3.0.1?

Thanks for taking the time to report this bug and helping to make Ubuntu better!

visibility: private → public
Changed in exaile (Ubuntu):
status: New → Incomplete
Revision history for this message
Andrew Starr-Bochicchio (andrewsomething) wrote :

Thank you for the bug report. It has not been updated after a request for more information in the last 30 days, for this reason we are closing the report. Feel free to reopen it in the future if you have more information and if this is still an issue.

Changed in exaile (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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