Icon stays though application was closed

[Raphael Groner]

The icon is still active when the docked application was closed via the context menu item. It disappears finally when the user selects "undock".
Please fix to remove the icon when the application is not running any more.

[Raphael (raphael-redhat-bugs)]

Description of problem:
The icon is still active when the docked application was closed via the context menu item. It disappears finally when the user selects "undock".
Please fix to remove the icon when the application is not running any more.
For instance, this happens with Geary.

Version-Release number of selected component (if applicable):
kdocker-4.8-1.fc21.x86_64
geary-0.8.3-1.fc21.x86_64

How reproducible:
yes

Steps to Reproduce:
1. start Geary
2. start kdocker and click into Geary main window
3. select "close" from the systray icon menu entry

Actual results:
icon is still visible in systray

Expected results:
icon disappears

Additional info:

[John Schember (user-none)]

Works for me. This was reported as a fedora bug. Build directly from source and I will look into it but if the issue is specific to fedora and my building on Ubuntu works then this has nothing to do work KDocker and is a bug in fedora.

[Rex Dieter (rdieter)]

When you say "Works for me", what environment were you using? Ubuntu Unity? Other?

[Rex (rex-redhat-bugs)]

Problem as described not reproducible on fedora 20 in kde4 (with local kdocker build)

[John Schember (user-none)]

> When you say "Works for me", what environment were you using? Ubuntu Unity? Other?

Ubuntu. It has been tested with both Gnome and KDE. The latest version was released in 2012 and no one else has had or reported any such issue.

Also, try with another application such as gedit. If that application works properly then it is most likely due to an interaction with geary (which was left out of this bug report and only mentioned in the Fedora report). If KDocker works properly with other applications then this points to the fact that this is not an issue with KDocker but an issue with geary and it not closing (or sending the closed XWindows signals properly.

Further make sure you are using version 4.8 of KDocker as many distros package earlier versions that have know bugs that were fixed in later versions.

I'll also add that KDocker relies on Xorg's XWindows implementation. If Fedora has moved to Wayland with XLib it's compatibility layer this is not supported or tested at all. That would indicate a bug in Wayland's Xlib compatibility layer.

Until each of the above can be proven as not the cause I'm not willing to look into this.

[Raphael (raphael-redhat-bugs)]

Umm, it is *not* reproducible in the following combination: Fedora 21, Cinnamon session, Brasero is kdocked. Brasero gets automatically undocked (main window is shown shortly) and closed immediately.

Maybe blame lxqt then? Geary is also based on gtk3 as brasero is. Upstream can not reproduce in both KDE and GNOME, too.

[Raphael Groner (projects-rg)]

Umm, it is *not* reproducible in the following combination: Fedora 21, Cinnamon session, Brasero is kdocked. Brasero gets automatically undocked (main window is shown shortly) and closed immediately.

[John Schember (user-none)]

Then this is an issue with geary not properly closing. KDocker undocks when it receives the signal that the application has been closed.

[Raphael (raphael-redhat-bugs)]

Reassigning to geary. Upstream writes:

Then this is an issue with geary not properly closing. KDocker undocks
when it receives the signal that the application has been closed.

[Raphael (raphael-redhat-bugs)]

Reassigning back as stated in comment #3 and nothing happened since ages. I'm going to invest.