I currently get this bug about 3 in four times when starting up my computer. The fourth time I am even more unfortunate and end up with the 90% CPU bug which could prove disastrous if I am not present at the time to kill the CPU-greedy process (https://bugs.launchpad.net/do/+bug/395190).
Basically, Do.exe does not crash but the gnome-do process is not running when this problem occurs. To open a new instance of gnome-do manually, I first have to kill the Do.exe process in task manager and then open gnome-do again. Interestingly, this problem only ever occurs when Gnome-Do is opened on startup.
In .xsession-errors I am seeing the following:
(Do:4543): Wnck-CRITICAL **: wnck_set_client_type got called multiple times.
I have now setup gnome-do to run with the debug flags at startup and see if I can pick up any more error information about this (or other) bugs - hopefully I can report back soon.
I currently get this bug about 3 in four times when starting up my computer. The fourth time I am even more unfortunate and end up with the 90% CPU bug which could prove disastrous if I am not present at the time to kill the CPU-greedy process (https:/ /bugs.launchpad .net/do/ +bug/395190).
Basically, Do.exe does not crash but the gnome-do process is not running when this problem occurs. To open a new instance of gnome-do manually, I first have to kill the Do.exe process in task manager and then open gnome-do again. Interestingly, this problem only ever occurs when Gnome-Do is opened on startup.
In .xsession-errors I am seeing the following: client_ type got called multiple times.
(Do:4543): Wnck-CRITICAL **: wnck_set_
I have now setup gnome-do to run with the debug flags at startup and see if I can pick up any more error information about this (or other) bugs - hopefully I can report back soon.