Reply to topic

System tray icons expand and icons change when using xkill

User avatar latebeat
Registered Member
Posts
70
Karma
0
Hey guys,

from time to time some pop-up windows will refuse to close even I press the close button so I revoke the xkill in order to force them to close. One example is the new display configuration pop-up when I attach an external monitor to my laptop. So, xkill works and the window is closed that is non-responsive however I'm noticing a very strange behavior every time I'm using xkill to kill something that has to do with kde (for example I if I kill chrome I don't get this behavior.)

All my system tray icons are expanded from and the icons are changed. What I mean is that they don't follow the theming of the desktop theme any more (eg. air or aya). The individual icons are following the icon theme applied to my desktop.

It's easier if I just show you so please have a look:

normal tray:
https://www.dropbox.com/s/ccjl34e15h60t ... licons.png

after any xkill:
https://www.dropbox.com/s/g3rfpm9b4yvzc ... dicons.png

See the difference in kopete, ktorrent or the printer queue for example? The icons change from the aya desktop theme to the icons used for the actual application provided by the icon theme. To be honest I'd rather have 1 set of consistent icons like these provided by the icon theme, however I'd like go find out why this is happening.

Also the only way to recover is to log out. Restarting the plasma desktop doesn't solve it.

any thoughts on this ?

thank you,
User avatar einar
Administrator
Posts
2269
Karma
5
OS
This happens when you kill the KDE daemon, kded4. It is responsible for a lot of tasks, including the new systray protocol: that's why the systray expands after it is killed, because it falls back to XEmbed.

Out of curiosity, what are the programs you're killing?


"Violence is the last refuge of the incompetent."
Image
Plasma FAQ maintainer - Plasma programming with Python
User avatar latebeat
Registered Member
Posts
70
Karma
0
einar wrote:This happens when you kill the KDE daemon, kded4. It is responsible for a lot of tasks, including the new systray protocol: that's why the systray expands after it is killed, because it falls back to XEmbed.

Out of curiosity, what are the programs you're killing?


Thank you for the reply,
so that's what it is!

Sometimes when I dock and undock my laptop the new display notification is non-responsive. Doesn't happen all the time.
Image
I didn't know how to kill that window so I used xkill


So XEmbed follows the program icons but not kded4?
Isn't that kinda backwards? I kinda liked the consistency.
User avatar bcooksley
Administrator
Posts
18586
Karma
83
OS
With XEmbed, the applications themselves are responsible for everything - including the drawing of their own icons. This makes it difficult for Plasma to know anything more about them other than that they are a square of a certain dimension which must be rendered.

The new protocol allows the application to provide a wealth of information to Plasma, which it then uses to render the visualisation itself - which is why the application icons under the new protocol are different. To help ensure multiple System Tray applets can be used (among other things) kded4 is responsible for mediating information between Plasma and the applications.


System Settings and Device Actions KCM maintainer
Image
User avatar latebeat
Registered Member
Posts
70
Karma
0
bcooksley wrote:With XEmbed, the applications themselves are responsible for everything - including the drawing of their own icons. This makes it difficult for Plasma to know anything more about them other than that they are a square of a certain dimension which must be rendered.

The new protocol allows the application to provide a wealth of information to Plasma, which it then uses to render the visualisation itself - which is why the application icons under the new protocol are different. To help ensure multiple System Tray applets can be used (among other things) kded4 is responsible for mediating information between Plasma and the applications.



Ok, I see. Thanks for the concise and clear explanation.
User avatar einar
Administrator
Posts
2269
Karma
5
OS
And you're killing kded4, because one of the modules it has is to handle (poorly, unfortunately) screen events.


"Violence is the last refuge of the incompetent."
Image
Plasma FAQ maintainer - Plasma programming with Python

 
Reply to topic

Bookmarks



Who is online

Registered users: alake, Baidu [Spider], Bing [Bot], boudewijn, colomar, edmael, Exabot [Bot], garthecho, Google [Bot], google01103, Hans, jitseniesen, ken300, koriun, mayankasthana, mgraesslin, mixoff, mmistretta, pedrorodriguez, scummos, SeaJey, SecretCode, Sentynel, Sogou [Bot], urgo, Yahoo [Bot]