Bug 11742

Summary:	amarok collection stops working after doing some changes in collection
Product:	Mageia	Reporter:	Florian Bauer <alfaflo>
Component:	RPM Packages	Assignee:	Juan Luis Baptiste <juan.baptiste>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	Keywords:	Triaged
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	amarok-2.8.0-2.mga4.src.rpm	CVE:
Status comment:
Attachments:	screenshot of process list

Description Florian Bauer 2013-11-23 09:10:34 CET

Description of problem:

MGA 4 beta 1:

After Amarok creates a new collection I mostly do some re-organisation in collection browser.
After doing 4-5 changes the collection browser stops working.
When I take a look in running processes I can see that amarok created some "zombie processes" called "amarokcollectio".
The collection browser stops working after 3rd zombie process occurs. 

I've already tried a clean amarok "profile" by deleting amarok settings in .kde4/... without success.

Reproducible: 

Steps to Reproduce:

Comment 1 Florian Bauer 2013-11-23 09:11:04 CET

Created attachment 4519 [details]
screenshot of process list

Comment 2 Florian Bauer 2013-11-24 10:41:57 CET

update: every action which results in an update of the collection creates described "zombie" processes. After 3 "Zombies" the collection browser stops working and Amarok is unusable at this point.

Manuel Hiebel 2013-11-24 16:54:54 CET

Keywords: (none) => Triaged
Assignee: bugsquad => juan.baptiste

Comment 3 Florian Bauer 2013-11-27 20:11:51 CET

collection is now working again
there was an update of mysql (mariadb embedded) so maybe the failure was related to this package...

thank you!

Comment 4 Florian Bauer 2013-12-05 18:19:05 CET

sorry, thought problem has been solved, but it occured again :-(

Comment 5 Florian Bauer 2013-12-24 10:17:16 CET

after changing the video driver from properitary nvidia to nouveau, the collection scanner works perfectly.
(see also kwrite launch bug 11946)

Comment 6 Juan Luis Baptiste 2013-12-26 20:13:49 CET

So is this resolved ?

Comment 7 Florian Bauer 2013-12-26 21:12:03 CET

no, sorry. as "nouveau" is no (full) alternative to the binary blob...
or in other words: when I switch back to nvidia proprietary driver, the failure is back.
so at least on my machine, the failure is 100% reproducible and I found no solution (deleting amarok folders; new install; switching from embedded database to mysql database; compiling amarok from source)
the only "workaround" what I've found is to switch to nouveau but that means to have (at least on my laptop) no vdpau and less 3D performance... :-(

Comment 8 Samuel Verschelde 2015-04-23 12:37:14 CEST

Looks like the nvidia + KDE bug we had at Mageia 4's very beginning. It's fixed then AFAIK.

Status: NEW => RESOLVED
Resolution: (none) => FIXED