Bug 271266 - Amarok crashes on "Search text Selection" using double click
Summary: Amarok crashes on "Search text Selection" using double click
Status: RESOLVED DUPLICATE of bug 264984
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 2.4.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: 2.4.1
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-19 05:13 UTC by Mohd Asif Ali Rizwaan
Modified: 2011-05-01 22:56 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
amarok backtrace, just typing asdfasdf and backspace on jamendo search (18.21 KB, application/octet-stream)
2011-04-30 23:06 UTC, Mohd Asif Ali Rizwaan 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Mohd Asif Ali Rizwaan 2011-04-19 05:13:35 UTC 
Version:           2.4.0 (using KDE 4.6.2) 
OS:                Linux

I double click on text to select and overwrite it.

So, Amarok's Internet->jamendo.com->Search field has this bug (also applicable to magnatune.com) when we type say 'asdf' and 'double-triple-click' on the word to 'select it' amarok crashes in a few seconds.

Reproducible: Always

Steps to Reproduce:
1. type some text on jamendo search area; 
2. keep on clicking and selecting it; 


Actual Results:  
3. amarok crashes

Expected Results:  
No crash and search result

OS: Linux (i686) release 2.6.38-8-generic
Compiler: cc
Comment 1 Myriam Schweingruber 2011-04-19 15:36:45 UTC 
We need a backtrace for this crash, see also http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Comment 2 Mohd Asif Ali Rizwaan 2011-04-30 23:06:58 UTC 
Created attachment 59468 [details]
amarok backtrace, just typing asdfasdf and backspace on jamendo search
Comment 3 Myriam Schweingruber 2011-05-01 22:56:55 UTC 
Backtrace from comment #2:

Thread 4 (Thread 0xa476eb70 (LWP 6017)):
[KCrash Handler]
#7  0x0111f1bd in Collections::ServiceSqlQueryMaker::handleResult (this=0x957cba8, result=...) at ../../src/services/ServiceSqlQueryMaker.cpp:639
#8  0x01120fa5 in ServiceSqlWorkerThread::run (this=0xa3e03378) at ../../src/services/ServiceSqlQueryMaker.cpp:58
#9  0x0077e7f4 in ThreadWeaver::JobRunHelper::runTheJob (this=0xa476e20c, th=0x9793630, job=0xa3e03378) at ../../../threadweaver/Weaver/Job.cpp:106
#10 0x0077e941 in ThreadWeaver::Job::execute (this=0xa3e03378, th=0x9793630) at ../../../threadweaver/Weaver/Job.cpp:135
#11 0x0077df6a in ThreadWeaver::ThreadRunHelper::run (this=0xa476e294, parent=0x962f750, th=0x9793630) at ../../../threadweaver/Weaver/Thread.cpp:95
#12 0x0077e05b in ThreadWeaver::Thread::run (this=0x9793630) at ../../../threadweaver/Weaver/Thread.cpp:142
#13 0x028a8da2 in QThreadPrivate::start (arg=0x9793630) at thread/qthread_unix.cpp:320
#14 0x0784ce99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#15 0x005f673e in clone () from /lib/i386-linux-gnu/libc.so.6

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