Problems at use | Problèmes à l'utilisation
Subscription date : 31 July 2013
Messages : 11
|
More of a heads up for other users than an actual problem.
I was getting repeat tray icons (as in the dock icons that stay always visible) and also draw issues on the effects when moving the mouse over icons (as in, displaying in the wrong place and effects shadows).
It turned out I was running 2 instances of Cairo Dock, so one was covering the other, and as I made changes to one, it was drawing icons in a different place to the 'ghost' instance.
So, if you get those kind of troubles, try quitting cairo-dock (which was when I discovered I had 2). |
Subscription date : 26 October 2008
Messages : 1904
|
Thanks for the heads up. It is quite a common problem.
Maybe something could be done to not have those kinds of problems @Fabounet |
Subscription date : 31 July 2013
Messages : 11
|
The obvious solution would be to prevent 2 instances... however some users may want to docks, so that's not ideal. |
Subscription date : 26 October 2008
Messages : 1904
|
Yes a lot of us now are using the dock only.  No more unity etc...
So maybe there should be a warning when two instances are going to be put at the same place. |
|
matttbe, Saturday 17 August 2013 à 00:41
|
|
Subscription date : 24 January 2009
Messages : 12573
|
Yes, it can be annoying.
@fabounet: maybe we can check if two instances uses the same config dir?
E.g. by adding a file (or use a config file) when starting the dock and removing it at the end (we can add it in the /tmp dir (e.g. /tmp/cairo-dock/$CONFIG_DIR => /tmp/home/$USER/.config/cairo-dock) in order to be sure that this file is removed at the end). If this file already exists when starting the dock and if there is another process named "cairo-dock" (and launched by user), we don't launch it twice (and we can display a warning in the terminal). |
|
fabounet, Thursday 22 August 2013 à 15:37
|
|
Subscription date : 30 November 2007
Messages : 17118
|
yep we could but then (when using 2 docks) if one of the dock crashes, it won't restart (because the file will stay)
and just writing the PID in the file and checking if this PID is alive might not be enough, because when restarting after a crash the PID is still present
using Dbus can do the trick I guess
but then the user misses the real problem, which is that a program is launched for nothing and slows down the startup |
|
matttbe, Thursday 22 August 2013 à 16:19
|
|
Subscription date : 24 January 2009
Messages : 12573
|
because when restarting after a crash the PID is still present If there is a crash, the PID is killed except if the signal is intercepted by the dock. And if the dock try to restart itself, we can detect that 
Or using DBus, good idea!
but then the user misses the real problem, which is that a program is launched for nothing and slows down the startup We can also display a warning message to inform that two dock are using the same config dir and add a link to our wiki page or something like that. |
Problems at use | Problèmes à l'utilisation
|
English
Online users :