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

[Lafa]

Binary package hint: amarok

I just installed the latest updates 2007-02-23. and reboot the system and amorak crashed at start up.

ProblemType: Crash
Date: Fri Feb 23 17:51:15 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/amarokapp
Package: amarok 2:1.4.5-0ubuntu5
ProcCmdline: amarokapp -session 1010413913a144000117098946900000053880018_1172200108_71637
ProcCwd: /home/lafa
ProcEnviron:
 PATH=/home/lafa/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.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 lafa-desktop 2.6.20-8-generic #2 SMP Tue Feb 13 05:18:42 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Lafa (luis-alves)]

the second time i started amarok, it worked fine.

[Andrew Hunter (rexbron)]

I can confirm this bug.

[Andrew Ash (ash211)]

Andrew and Lafa,

Can you device a series of steps that can consistently reproduce this crash?

I've also marked a couple other bug reports with identical stack traces as this one as dupes.

[Lafa (luis-alves)]

On Saturday 10 March 2007, Andrew Ash wrote:
> Andrew and Lafa,
>
> Can you device a series of steps that can consistently reproduce this
> crash?
>
> I've also marked a couple other bug reports with identical stack traces
> as this one as dupes.
>
> ** Changed in: amarok (Ubuntu)
> Assignee: (unassigned) => Andrew Ash
> Status: Confirmed => Needs Info
>

I tried, is not reproducable.

[Brian Murray (brian-murray)]

StacktraceTop:QComLibrary::createInstanceInternal (this=0xb3d00010)
DCOPProcessMessage (iceConn=0x80c80b8, clientObject=0x80cd770, opcode=3,
KDE_IceProcessMessages (iceConn=0x80c80b8, replyWait=0xbfd86318,
DCOPClient::callInternal (this=0x80cbfb0, remApp=@0xbfd86550,
DCOPClient::callInternal (this=0x80cbfb0, remApp=@0xbfd86550,

[Andrew Hunter (rexbron)]

There seem to be a lot of Amarok bugs that just happen. Also, with the addition of apport, many bugs/crashes that went unreported are now be discovered.

Most of the Amarok crashes I experience seem to be at start up or after a long period of inactivity and occur (seemely) randomly.

[Andrew Ash (ash211)]

I'm confirming. Seems there are enough duplicates to ensure it's not a chance occurrence.

[AaronPeterson (alpeterson)]

Thank you!

[Apport retracing service (apport)]

StacktraceTop:operator>> (s=@0xbfd86180, str=@0x81ed420) at tools/qcstring.cpp:2314
DCOPProcessMessage (iceConn=0x80c80b8, clientObject=0x80cd770, opcode=3, length=40, replyWait=0xbfd878e8, replyWaitRet=0xbfd86214)
KDE_IceProcessMessages (iceConn=0x80c80b8, replyWait=0xbfd86318, replyReadyRet=0xbfd86368) at /build/buildd/kdelibs-3.5.6/./dcop/KDE-ICE/process.c:326
DCOPClient::callInternal (this=0x80cbfb0, remApp=@0xbfd86550, remObjId=@0xbfd86550, remFun=@0xbfd86604, data=@0xbfd86568, replyStruct=0xbfd863c4,
DCOPClient::callInternal (this=0x80cbfb0, remApp=@0xbfd86550, remObjId=@0xbfd86550, remFun=@0xbfd86604, data=@0xbfd86568, replyType=@0xbfd86560,

[Wouter Horré (wouterh)]

I suffer from the same problem (which I already reported in bug #92321, probably also a duplicate of this bug). The crash happens always when amarok is started at KDE startup (because it was running when KDE was shut down). This makes it difficult to produce a good backtrace.

[Stefan Sieber (stesieber)]

I can confirm this bug.
I`d really like to attach the stack trace, but unfortunately I lost it somewhere in the 'report new bug' process :(

[Wouter Horré (wouterh)]

I could not figure out how to attach the report of apport to an existing bug, so I reported it as a new bug (bug 117348) and marked it as a duplicate of this one: https://bugs.launchpad.net/ubuntu/+source/amarok/+bug/117348

[Apport retracing service (apport)]

StacktraceTop:QCString::resize (this=0xbfd86180, len=136238112) at tools/qcstring.cpp:837
DCOPProcessMessage (iceConn=0x80c80b8, clientObject=0x80cd770, opcode=3, length=40, replyWait=0xbfd878e8, replyWaitRet=0xbfd86214)
KDE_IceProcessMessages (iceConn=0x80c80b8, replyWait=0xbfd86318, replyReadyRet=0xbfd86368) at /build/buildd/kdelibs-3.5.6/./dcop/KDE-ICE/process.c:326
DCOPClient::callInternal (this=0x80cbfb0, remApp=@0xbfd86550, remObjId=@0xbfd86550, remFun=@0xbfd86604, data=@0xbfd86568, replyStruct=0xbfd863c4,
DCOPClient::callInternal (this=0x80cbfb0, remApp=@0xbfd86550, remObjId=@0xbfd86550, remFun=@0xbfd86604, data=@0xbfd86568, replyType=@0xbfd86560,

[Justin (justin-moser)]

any update? i have this same problem.

i'm using the version from medibuntu, as well as libxine1-ffmpeg (for mp3 support) and the abominable w32codecs

[Dirk Desmet (desmet-dga)]

This is a mail for christian Reis

This are the mails that i don t wanne receive from the Ubuntue operating
system

-----Oorspronkelijk bericht-----
Van: <email address hidden> [mailto:<email address hidden>] Namens Justin
Verzonden: donderdag 21 juni 2007 1:34
Aan: <email address hidden>
Onderwerp: [Bug 87469] Re: MASTER [apport] amarokapp crashed with SIGSEGV
inoperator>>()

any update? i have this same problem.

i'm using the version from medibuntu, as well as libxine1-ffmpeg (for
mp3 support) and the abominable w32codecs

--
MASTER [apport] amarokapp crashed with SIGSEGV in operator>>()
https://bugs.launchpad.net/bugs/87469
You received this bug notification because you are a direct subscriber of a
duplicate bug.

[advanracing62 (advanracing62)]

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232779056 (LWP 20108)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6 0xb6666a0b in KAudioManagerPlay::KAudioManagerPlay ()
   from /usr/lib/libartskde.so.1
#7 0xb6729893 in KNotify::restartedArtsd () from /usr/lib/kde3/knotify.so
#8 0xb672b96d in KNotify::KNotify () from /usr/lib/kde3/knotify.so
#9 0xb672c1aa in kdemain () from /usr/lib/kde3/knotify.so
#10 0x0804e67f in ?? ()
#11 0x00000001 in ?? ()
#12 0x08087a50 in ?? ()
#13 0x00000001 in ?? ()
#14 0x00000000 in ?? ()

attempting to delete track from Ipod- updates are current.

[Timo Jyrinki (timo-jyrinki)]

Please someone test with this Ubuntu 8.04 and mark this as fixed if it's fixed.

[Jonathan Thomas (echidnaman)]

This bug is quite likely not a problem with Amarok 2, most of which has been completely rewritten. As such I am closing this bug as fixed.