Bug 15838 - amarok analyzer plugin kills amarok, is enabled automatically by gstreamer backend
Summary: amarok analyzer plugin kills amarok, is enabled automatically by gstreamer ba...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Juan Luis Baptiste
QA Contact:
URL:
Whiteboard: MGA5TOO, MGA4TOO
Keywords: UPSTREAM
Depends on:
Blocks:
 
Reported: 2015-05-04 01:24 CEST by David Walser
Modified: 2020-05-02 09:23 CEST (History)
3 users (show)

See Also:
Source RPM: amarok-2.8.0-5.mga5.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description David Walser 2015-05-04 01:24:35 CEST 
While trying to reproduce Bug 9926 in Mageia 4 and Cauldron VMs, switching to the Gstreamer Phonon backend made Amarok unusable.  If I'd click the system tray icon, it would crash while trying to show the Amarok UI.  drkonqi would also fail to launch, making it impossible to get any useful debugging info.

This is reproducible in this VM, although it wasn't on a Cauldron machine at work.  I traced the change in the Amarok settings that causes the crash to this:
--- good/.kde4/share/config/amarok_homerc       2015-05-03 18:57:09.000000000 -0400
+++ bad/.kde4/share/config/amarok_homerc        2015-05-03 18:59:54.000000000 -0400
@@ -90,7 +90,7 @@ ForegroundVisited[$d]
 
 [Containment 0]
 firstShowingApplet=0
-plugins=currenttrack,lyrics,wikipedia
+plugins=currenttrack,analyzer,lyrics,wikipedia
 
 [Directories-default]
 prefixes[$d]


With the analyzer plugin enabled, the crash happens no matter which backend you're using.  Removing that from the config allows it to work fine again, with either backend.  Switching back to the VLC backend does not cause it to be added to the config.

Reproducible: 

Steps to Reproduce:
David Walser 2015-05-04 01:24:56 CEST

CC: (none) => lmenut, mageia
Whiteboard: (none) => MGA4TOO

Comment 1 Nicolas Lécureuil 2015-05-04 08:49:37 CEST 
fixed on svn

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

Comment 2 David Walser 2015-05-04 12:56:25 CEST 
Fix not pushed yet, Mageia 4 also affected.  Reopening.

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

Comment 3 Nicolas Lécureuil 2015-05-04 13:28:03 CEST 
i fix for mga4 today
Comment 4 David Walser 2015-05-04 22:43:06 CEST 
I added the same patch on Mageia 4 as is in Cauldron, and unfortunately, it doesn't fix it.  Switching to gstreamer still adds analyzer to the config and kills Amarok.
Comment 5 Otto Leipälä 2015-05-05 08:44:13 CEST 
Seems to be noticed in upstream too.
https://bugs.kde.org/show_bug.cgi?id=320992

CC: (none) => ozkyster

Samuel Verschelde 2015-05-05 09:11:04 CEST

Keywords: (none) => UPSTREAM

Samuel Verschelde 2015-05-31 21:39:40 CEST

Whiteboard: MGA4TOO => MGA4TOO MGA5TOO

Comment 6 Nicolas Lécureuil 2015-06-01 07:14:47 CEST 
this is fixed in mga5

Whiteboard: MGA4TOO MGA5TOO => MGA4TOO

Comment 7 Samuel Verschelde 2015-06-01 09:08:39 CEST 
(In reply to Nicolas Lécureuil from comment #6)
> this is fixed in mga5

Setting version accordingly then.

Version: Cauldron => 4
Whiteboard: MGA4TOO => (none)

Comment 8 David Walser 2015-06-01 12:14:51 CEST 
This was never actually fixed anywhere.

Whiteboard: (none) => MGA5TOO, MGA4TOO
Version: 4 => Cauldron

Luc Menut 2016-08-25 16:42:54 CEST

CC: lmenut => (none)

Comment 9 David GEIGER 2020-05-02 09:23:25 CEST 
Closing of this bug as old!

Status: REOPENED => RESOLVED
Resolution: (none) => OLD
CC: (none) => geiger.david68210
Note You need to log in before you can comment on or make changes to this bug.