quodlibet crashed with SIGSEGV in udev_list_entry_get_name()

Bug #657192 reported by Steve Langasek
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
quodlibet (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: quodlibet

quodlibet doesn't seem to like udev events very much.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: quodlibet 2.2.1-1
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Fri Oct 8 21:54:08 2010
ExecutablePath: /usr/bin/quodlibet
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
InterpreterPath: /usr/bin/python2.6
PackageArchitecture: all
ProcCmdline: python /usr/bin/quodlibet --sm-config-prefix /quodlibet-gurn11/ --sm-client-id 104796b5ad48e316ed128637910481315900000027200067 --screen 0
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fb55dcdb455 <udev_list_entry_get_name+7>: mov 0x20(%rdi),%rax
 PC (0x7fb55dcdb455) ok
 source "0x20(%rdi)" (0x480239c0) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: quodlibet
StacktraceTop:
 udev_list_entry_get_name () from /lib/libudev.so.0
 ffi_call_unix64 () from /usr/lib/python2.6/lib-dynload/_ctypes.so
 ffi_call () from /usr/lib/python2.6/lib-dynload/_ctypes.so
 _CallProc () from /usr/lib/python2.6/lib-dynload/_ctypes.so
 ?? () from /usr/lib/python2.6/lib-dynload/_ctypes.so
Title: quodlibet crashed with SIGSEGV in udev_list_entry_get_name()
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare src

Revision history for this message
Steve Langasek (vorlon) wrote :
Revision history for this message
Christoph Reiter (lazka) wrote :

That's fixed in 2.3 which is in Ubuntu now.

Changed in quodlibet (Ubuntu):
status: New → Fix Released
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.