<p dir="ltr">Don't have my laptop in front of me to confirm but my guess is no. Moving away from Xembed and dropping support for it in a too-be-decided future version of the desktop environments was announced in 2011 with the advent of Status Notifiers and libappindicator. </p>
<div class="gmail_quote">On Jul 24, 2015 01:12, "Reindl Harald" <<a href="mailto:h.reindl@thelounge.net">h.reindl@thelounge.net</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">does the same application work on the Fedora default desktop (GNOME)?<br>
if the answer is yes KDE is to blame, period<br>
<br>
Am 24.07.2015 um 06:59 schrieb Eric Griffith:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Reindl, I bash on a lot of design decision from the KDE and GNOME camps<br>
alike, but this wasn't one of them. Xembed had to go, it was a design<br>
nightmare. As far as who's fault it is.. I really gotta go with the apps<br>
on this one. They had four -years- of warning that the "traditional"<br>
xembed way of sys tray icons was going away eventually. If they couldnt<br>
find time to port over to Status Notifiers / App Indicators by then that<br>
that's their problem / or the project is dead anyway.<br>
<br>
On Fri, Jul 24, 2015 at 12:44 AM, Reindl Harald <<a href="mailto:h.reindl@thelounge.net" target="_blank">h.reindl@thelounge.net</a><br>
<mailto:<a href="mailto:h.reindl@thelounge.net" target="_blank">h.reindl@thelounge.net</a>>> wrote:<br>
<br>
<br>
Am 24.07.2015 um 03:16 schrieb Markus Slopianka:<br>
<br>
On Thursday 23 July 2015 13:32:58 Emilio Recio wrote:<br>
<br>
Does anyone know of an app that can implement xembed feature?<br>
<br>
<br>
<a href="http://blog.martin-graesslin.com/blog/2014/06/where-are-my-systray-icons/" rel="noreferrer" target="_blank">http://blog.martin-graesslin.com/blog/2014/06/where-are-my-systray-icons/</a><br>
<br>
<br>
Pidgin<br>
<br>
<br>
<a href="https://copr.fedoraproject.org/coprs/rvokal/pidgin-indicator/" rel="noreferrer" target="_blank">https://copr.fedoraproject.org/coprs/rvokal/pidgin-indicator/</a><br>
<br>
<br>
This is a major fail for KDE, IMNSHO.<br>
<br>
<br>
Wrong. It's a major fail for your applications<br>
<br>
<br>
strange attitude - if *non-kde* apps have problems with the systray<br>
and did not before KDE5 it's hardly a failure of the application,<br>
it's *again* a incompatible and ignorant regression as it happens<br>
every few years so that i even start asking myself "am i right in my<br>
mind to use linux desktop"<br>
<br>
"fail for your applications" - WTF - the world of application<br>
developers don't turn around KDE and broken desktops, i heard the<br>
same b**** with the over a year flickering control bar with KDE 4.0<br>
in combination with nvidia cards - the same - it worked befor<br>
KDE3->KDE4, so KDE is the problem and not the card and it's the job<br>
of a developer to handle it if it has worked before AND NO "it's<br>
free" don't justify carelessly while whine every year why linux<br>
desktops are a niche and how to change that<br>
<br>
if developers like linux desktops no longer be a niche the just need<br>
to stop user visible major changes and breaking things which worked<br>
and are in use - that's it, no Fedora.next, just don't break the<br>
user expierience once per year and you will stop lose existing ones<br>
and get new ones which no longer need to fear that their workflow<br>
get broken again and again<br>
</blockquote>
<br>
<br>_______________________________________________<br>
kde mailing list<br>
<a href="mailto:kde@lists.fedoraproject.org">kde@lists.fedoraproject.org</a><br>
<a href="https://admin.fedoraproject.org/mailman/listinfo/kde" rel="noreferrer" target="_blank">https://admin.fedoraproject.org/mailman/listinfo/kde</a><br>
New to KDE4? - get help from <a href="http://userbase.kde.org" rel="noreferrer" target="_blank">http://userbase.kde.org</a><br></blockquote></div>