Bug 177599

Summary:	Now listen plugin does not work with Amarok2
Product:	[Applications] kopete	Reporter:	Alin M Elena <alinm.elena>
Component:	Now Listening Plugin	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	fedora, xadolax
Priority:	NOR
Version:	0.60.81
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:

Description Alin M Elena 2008-12-12 16:39:02 UTC

Version:           0.60.81 (using 4.1.82 (KDE 4.1.82 (KDE 4.2 >= 20081204)) "release 3.2", KDE:KDE4:UNSTABLE:Desktop / openSUSE_11.1)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.27.7-4-default

Now listen plugin does not work with Amarok2. No status is changed, no /media provides 
Now Listening for Kopete - it would tell you what I am listening to, if I was listening to something on a supported media player.

Alin

Comment 1 Adam Fowler 2008-12-20 21:37:55 UTC

I have the latest version of AmaroK 2 and Kopete.  And, I too get this bug. 

I ran both Kopete and AmaroK 2 as root in terminals.

When I type "/media" into Kopete, I get the "Now listening for Kopete- I would tell you what I'm listening to.  Blahblahblah"

And on terminal.  I get the error "Mysql database not open"  Or something along those lines (I'm sorry, I'm not on the computer with the issue right now)  However, it takes on average about 3 minutes for that error to appear after I type "/media"  and after it appears the first time.  I get it instantly everytime after that.  (The 3 minute wait MAY be because i'm on dial-up.  I'm not sure.)


Thank you very much.

Comment 2 Eelko Berkenpies 2009-09-13 09:24:51 UTC

I cannot confirm this for Fedora 11 / KDE 4.3.1 / Amarok 2.2-GIT. Kopete knows exactly what I'm playing when the Advertising Mode is set to "Show the music you are listening to in place of your status message", "Append to your status message" and by "Typing /media in the chat window area".

Comment 3 Myriam Schweingruber 2009-11-30 12:57:12 UTC


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