FS#13131 - gnome-do forgets settings upon rebbot/re-login: no docky until "killall gnome-do && gnome-do"

Attached to Project: Community Packages
Opened by Freek (teek) - Friday, 06 February 2009, 00:58 GMT
Last edited by Allan McRae (Allan) - Saturday, 14 March 2009, 10:48 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Allan McRae (Allan)
Architecture i686
Severity Low
Priority Normal
Reported Version None
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:

gnome-do-0.8.0-2 upon new login or reboot forgets all its settings. This means, I'm presented with the default theme when I summon gnome-do after login and there is not Docky even though I set Docky as the theme. When I klik the tray icon and click settings it tells me the current theme is docky however the docky only appears when I "killall gnome-do && gnome-do &".

Additional info:
* package version(s)

gnome-do-0.8.0-2

* config and/or log files etc.


Steps to reproduce:

Tell gnome-do te auto-start, set theme to docky and reboot, see if you get the docky.
This task depends upon

Closed by  Allan McRae (Allan)
Saturday, 14 March 2009, 10:48 GMT
Reason for closing:  Fixed
Additional comments about closing:  post_install message added
Comment by Timm (gummibaerchen) - Friday, 06 February 2009, 13:06 GMT
I have GNOME Do in autostart and Docky comes up fine everytime.

Have you checked how your autostart command looks like? Maybe it has a command-line option appended? (From using previous versions?)
Comment by Freek (teek) - Friday, 06 February 2009, 15:39 GMT
Hey Timm, thanx for replying, I removed the autostart entry from the gnome session menu and added it again using the gnome-do option "start at login" => no difference. It just says "gnome-do" as the command. I do login automatically, but that can't be it, can it? Are you using the testing repo? I don't, do we have the same version?
Comment by Timm (gummibaerchen) - Friday, 06 February 2009, 15:48 GMT
No, I am not using testing.

My start command is also just "gnome-do", not sure why it does not work for you though.
Comment by Freek (teek) - Friday, 06 February 2009, 16:13 GMT
Hmmm, strange, something with my settings then... I use compiz, gnome, intel graphics... I really can't think of anything actually. Well, I'll just wait for the next version or try the aur one for now.

Thanx for the help, anyways.
Comment by Timm (gummibaerchen) - Friday, 06 February 2009, 19:35 GMT
compiz might call some trouble here.

iirc I read about some troubles in various blogs concerning compiz+Do.

Maybe just try with Metacity?
Comment by Freek (teek) - Saturday, 07 February 2009, 14:50 GMT
It's the same with metacity :(
Comment by Freek (teek) - Saturday, 07 February 2009, 15:52 GMT
It's the same with metacity :(
Comment by Freek (teek) - Saturday, 07 February 2009, 15:53 GMT
I did set my system to 120 dpi?
Comment by Freek (teek) - Saturday, 07 February 2009, 15:57 GMT
I did set my system to 120dpi...?
Comment by filippo colombo (ombra85) - Sunday, 08 February 2009, 14:03 GMT
I have the same problem with gnome-do.
I use compiz.
Comment by Freek (teek) - Sunday, 15 February 2009, 11:15 GMT
then vote for it :)
Comment by paralityk (Paralityk) - Monday, 16 February 2009, 18:01 GMT
Hymm how about, removing gnome-do, deleting settings, and installing it again? (I assume that you have ppa set up)

sudo killall gnome-do
sudo pacman -R gnome-do
rm -r ~/.gconf/apps/gnome-do
rm -r ~/.local/share/gnome-do
sudo pacman -S gnome-do

Edit: using pacman instead of apt-get - Allan
Comment by Freek (teek) - Tuesday, 17 February 2009, 23:36 GMT
Tried that (using pacman :)) no luck... theme is still docky but no dock and standard theme.
Thanx for the suggestion though.
Comment by paralityk (Paralityk) - Wednesday, 18 February 2009, 15:20 GMT
Oh sry for the apt-get part... I'm having the same problem on Ubuntu 8.10 x86 :)
Comment by Timm (gummibaerchen) - Wednesday, 18 February 2009, 15:26 GMT
What may this tell us?

Upstream bug ;)

So it's probably already file (multiple times) on launchpad.
Comment by paralityk (Paralityk) - Wednesday, 18 February 2009, 16:09 GMT
"So it's probably already file (multiple times) on launchpad."
Actually I found only one file ;)
https://bugs.launchpad.net/do/+bug/324332
As it says it's probably because of gnome-do starting before compiz, not detecting compositing and reverting skin to classic :)
Comment by Freek (teek) - Wednesday, 18 February 2009, 16:49 GMT
That sounds very logical and it explains why it does work when you kill and restart of just start manually. It does seem like the gnome-do people are not likely to fix this soon... I think the start up script with a "wait" in it is for now the only option, too bad... But thanx for the info!
Comment by Freek (teek) - Wednesday, 18 February 2009, 21:49 GMT
Solved it by adding "sleep 5" as the first line of /usr/bin/gnome-do
Now it looks like this:

#!/bin/sh

# added this sleep line so gnome-do waits for compiz to load.
sleep 5

SCRIPT_PATH=`dirname $0`
SCRIPT_PATH=`cd $SCRIPT_PATH; pwd`

if [ "x$SCRI ...

and so on.

Thanx for all your help guys!

(for those who don't know, sleep freezes the script for 5 sec.)
Comment by Freek (teek) - Wednesday, 18 February 2009, 22:22 GMT
Actually, make that "sleep 12" 5 was only enough after a relogin, upon reboot it takes much longer to load compiz. But this depends entirely on your system off course.
Comment by Allan McRae (Allan) - Sunday, 22 February 2009, 10:15 GMT
Can anyone else confirm this "fix". I could add a post_install message about waiting to launch gnome_do as a "fix" for the time being.
Comment by paralityk (Paralityk) - Sunday, 22 February 2009, 14:41 GMT
Freek's fix works, i put 3 seconds :)
Comment by filippo colombo (ombra85) - Sunday, 22 February 2009, 18:51 GMT
I put 5 seconds and it works.
Comment by Allan McRae (Allan) - Saturday, 14 March 2009, 10:48 GMT
added the post install message in gnome-do 0.8.1-1

Loading...