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:
Created attachment 4519 [details] screenshot of process list
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.
Keywords: (none) => TriagedAssignee: bugsquad => juan.baptiste
collection is now working again there was an update of mysql (mariadb embedded) so maybe the failure was related to this package... thank you!
sorry, thought problem has been solved, but it occured again :-(
after changing the video driver from properitary nvidia to nouveau, the collection scanner works perfectly. (see also kwrite launch bug 11946)
So is this resolved ?
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... :-(
Looks like the nvidia + KDE bug we had at Mageia 4's very beginning. It's fixed then AFAIK.
Status: NEW => RESOLVEDResolution: (none) => FIXED