Bug 155730 - aMSN trayicon not in traydock
Summary: aMSN trayicon not in traydock
Status: RESOLVED INTENTIONAL
Alias: None
Product: plasma4
Classification: Plasma
Component: widget-systemtray (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
: 165057 (view as bug list)
Depends on:
Blocks:
 
Reported: 2008-01-14 10:53 UTC by Jesús Vidal
Modified: 2008-08-18 01:07 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Jesús Vidal 2008-01-14 10:53:36 UTC 
Version:            (using KDE KDE 4.0.0)
Installed from:    Ubuntu Packages
OS:                Linux

amsn trayicon doesn't put on the new systemtray on KDE 4.0.0
Instead of that, it creates a new miniwindow on desktop with amsn trayicon.

See this screenshot: http://webs.ono.com/jesusvpct/amsn_systray_kde4.png
Comment 1 S. Burmeister 2008-01-14 12:34:51 UTC 
Do you get any windows telling you that it could not connect to klauncher?
Comment 2 Jesús Vidal 2008-01-14 13:15:25 UTC 
No, i don't see any window saying that...
Comment 3 Gabriel C 2008-01-14 14:10:17 UTC 
I can confirm that.
Comment 4 Lubos Lunak 2008-01-15 11:56:48 UTC 
You need to report to amsn developers. Instead of always using the fd.o tray spec, it has a special case for KDE that uses the obsolete KDE tray mechanism that is not supported by KDE4.
Comment 5 Jesús Vidal 2008-01-15 12:40:46 UTC 
Sorry, but i first posted on aMSN forum and they say that they uses freedesktop implementation, so it should be KDE problem.

See this link: http://www.amsn-project.net/forums/viewtopic.php?t=4665
Comment 6 Lubos Lunak 2008-01-15 13:48:13 UTC 
Well, then I can read their source better then them.
Comment 7 Youness Alaoui 2008-02-20 05:09:03 UTC 
Hi,

I'm an aMSN developer. Yes, I noticed there's a special case for KDE which uses something different. I'd like to know what you think about that, since I'm not familiar with that code at all (and I don't think the original author is anywhere around..) 

I guess that special case was because the fd.o spec was not working in some earlier versions of KDE, do you know for which versions of KDE, aMSN's tray will break if we remove the special case? Is it for a really old KDE release? Also, is there a way to use both the fd.o spec and the KDE workaround, this way KDE4 will work, the broken KDE version will also work, but what about the versions in between that support both the fd.o spec and the obsolete KDE tray mechanism ? Will they be affected ? 

Thanks for your time!
KaKaRoTo
Comment 8 Lubos Lunak 2008-02-22 22:32:31 UTC 
The first commit with support for XDG systray is dated September 2002, so it should be supported since KDE3.1. In case you want to support even older versions, you can check whether XDG systray exists and only fall back if not - the check for the XDG tray is simply checking whether its manager selection (_NET_SYSTEM_TRAY_Sn) is held, it otherwise wouldn't work anyway after all.
Comment 9 Diego 2008-02-28 19:17:10 UTC 
Fixed upstream. Thanks.
Comment 10 Christophe Marin 2008-06-27 12:03:18 UTC 
*** Bug 165057 has been marked as a duplicate of this bug. ***
Comment 11 Jay LaCroix 2008-08-18 01:07:13 UTC 
I still have this problem with Amarok and several other applications. Amarok is the main one, I do get a message about it not being able to communicate with klauncher. I'm using KDE 4.1. So it looks like this isn't resolved. :(