Bug 136020 - amarok crashes when action performed finishes after modal amazon dialog
Summary: amarok crashes when action performed finishes after modal amazon dialog
Status: RESOLVED DUPLICATE of bug 122002
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Slackware Linux
: NOR crash
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-20 15:02 UTC by richlv
Modified: 2006-10-22 11:57 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description richlv 2006-10-20 15:02:45 UTC
Version:           svn 597347 (using KDE KDE 3.5.4)
Installed from:    Slackware Packages
OS:                Linux

have context browser open. edit tags for any one track (from playlist or whatever).
right click an album cover in the context browser, choose 'fetch from amazon.com'.
while the cover is still downloading, select any text in the tag dialog, drag it.
when results appear, drop the text in any appropriate field in the opened tag editor.

amarok crashes.

unfortunately, amarokapp is left in defunct state and gdb can't attach to it, but when i run 'gbb amarokapp' it silently closes, so i can not obtain backtrace.

i also suspected musicbrainz result window to do the same thing, but it seems to drop the text where intended & not crash.
Comment 1 Lorenz Röhrl 2006-10-20 15:09:38 UTC
Jup, i got that too. Dropping the text on the coverfetching-dialog makes amarok crash too.

Here is what i get through gdb: 

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1257064752 (LWP 10836)]
0xb664e690 in qt_tryModalHelper () from /usr/qt/3/lib/libqt-mt.so.3
(gdb) bt
#0  0xb664e690 in qt_tryModalHelper () from /usr/qt/3/lib/libqt-mt.so.3
#1  0xb65d8627 in qt_try_modal () from /usr/qt/3/lib/libqt-mt.so.3
#2  0xb6d5830b in KAccelEventHandler::x11Event () from /usr/kde/3.5/lib/libkdecore.so.4
#3  0x08a27640 in ?? ()
#4  0xbfd216b0 in ?? ()
#5  0x00000000 in ?? ()
Comment 2 Alexandre Oliveira 2006-10-22 11:57:20 UTC

*** This bug has been marked as a duplicate of 122002 ***