Summary: | aMSN trayicon not in traydock | ||
---|---|---|---|
Product: | [Unmaintained] plasma4 | Reporter: | Jesús Vidal <jesusvpct> |
Component: | widget-systemtray | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | normal | CC: | crazy, jay, kakaroto, l.lunak, postmaster |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Jesús Vidal
2008-01-14 10:53:36 UTC
Do you get any windows telling you that it could not connect to klauncher? No, i don't see any window saying that... I can confirm that. 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. 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 Well, then I can read their source better then them. 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 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. Fixed upstream. Thanks. *** Bug 165057 has been marked as a duplicate of this bug. *** 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. :( |