[apport] amarokapp crashed with SIGSEGV in operator>>()

Bug #109587 reported by boril
4
Affects Status Importance Assigned to Milestone
amarok (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: amarok

 I do the same as in the 89242 bug. Also the Konqeror is unstable and I do not use it for browsing

ProblemType: Crash
Architecture: i386
Date: Tue Apr 24 08:37:17 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/amarokapp
Package: amarok 2:1.4.5-0ubuntu7
PackageArchitecture: i386
ProcCmdline: amarokapp -session 10d9e9d775000117571350800000051230022_1177278438_543655
ProcCwd: /home/boril
ProcEnviron:
 LANGUAGE=bg_BG:bg:en_GB:en
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games:/home/boril/.local/bin:/home/boril/.kde//bin
 LANG=bg_BG.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: amarok
StacktraceTop:
 operator>> () from /usr/lib/libqt-mt.so.3
 ?? () from /usr/lib/libDCOP.so.4
 ?? ()
 ?? ()
 ?? ()
Uname: Linux kubuntu 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

Revision history for this message
boril (boril-gourinov) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:operator>> (s=@0xbf81f690, str=@0x81eadc0) at tools/qcstring.cpp:2314
DCOPProcessMessage (iceConn=0x80c6ee0, clientObject=0x80c6470, opcode=3, length=40, replyWait=0xbf820df8, replyWaitRet=0xbf81f724)
KDE_IceProcessMessages (iceConn=0x80c6ee0, replyWait=0xbf81f828, replyReadyRet=0xbf81f878) at /build/buildd/kdelibs-3.5.6/./dcop/KDE-ICE/process.c:326
DCOPClient::callInternal (this=0x80cdfe0, remApp=@0xbf81fa60, remObjId=@0xbf81fa60, remFun=@0xbf81fb14, data=@0xbf81fa78, replyStruct=0xbf81f8d4,
DCOPClient::callInternal (this=0x80cdfe0, remApp=@0xbf81fa60, remObjId=@0xbf81fa60, remFun=@0xbf81fb14, data=@0xbf81fa78, replyType=@0xbf81fa70,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in amarok:
importance: Undecided → Medium
status: Unconfirmed → Confirmed
Revision history for this message
Andrew Ash (ash211) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 87469 and is being marked as such. Please feel free to report any other bugs you may find.

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.