[apport] amarokapp crashed with SIGSEGV in KInstance::dirs()

Bug #93398 reported by tdn
2
Affects Status Importance Assigned to Milestone
amarok (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: amarok

It crashed while I was rescanning my collection.
Maybe something with tag reading?

ProblemType: Crash
Architecture: i386
Date: Sat Mar 17 23:22:07 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/amarokapp
Package: amarok 2:1.4.5-0ubuntu6
PackageArchitecture: i386
ProcCmdline: amarokapp
ProcCwd: /home/tdn
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_DK.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: amarok
StacktraceTop:
 KInstance::dirs () from /usr/lib/libkdecore.so.4
 KGlobal::dirs () from /usr/lib/libkdecore.so.4
 KConfigBackEnd::changeFileName ()
 KConfigBackEnd::KConfigBackEnd ()
 KConfig::KConfig () from /usr/lib/libkdecore.so.4
Uname: Linux homer 2.6.20-11-generic #2 SMP Thu Mar 15 08:03:07 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
tdn (spam-thomasdamgaard) wrote :
Changed in amarok:
importance: Undecided → Medium
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:KGlobal::dirs () at /build/buildd/kdelibs-3.5.6/./kdecore/kglobal.cpp:58
KConfigBackEnd::changeFileName (this=0x9842898, _fileName=@0xbfdffb5c, _resType=0xb735a8f5 "config", _useKDEGlobals=true)
KConfigBackEnd (this=0x9842898, _config=0x825ad98, _fileName=@0xbfdffb5c, _resType=0xb735a8f5 "config", _useKDEGlobals=true)
KConfig (this=0x825ad98, fileName=@0xbfdffb5c, bReadOnly=false, bUseKderc=true, resType=0xb735a8f5 "config")

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug

Changed in amarok:
status: Unconfirmed → Confirmed
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.