I did some work, made a python script to run gnome-do from startup applications in debug mode and capture the output. I will post the script, and the two output files I obtained.
First, gnome-do-output-autostart, is the debug output from starting gnome-do from the python script auto-started. Second, gnome-do-output-terminal, is the debug output from starting gnome-do from the terminal "gnome-do --debug >> gnome-do-output- terminal" In both the auto-started output and terminal started output no reference to opening the home folder is present, even though there are reference to opening the Music folder and the enhickman folder (myuser's homefolder). Which brings me to my second point, When auto-starting: I can not open the home folder through the home folder dialog (typing 'home' then 'ENTER') But I can open the home folder by explicitly choosing the enhickman folder (typing 'enhi' then 'ENTER') When starting from the terminal: I can open the user home folder both ways that is (typing 'home' then pressing 'ENTER' or typing 'enhi' then pressing 'ENTER') So gnome-do can open the home folder from autostart just not from the 'Home Folder' menu item. lastly to understand the gnome-do output files it should be known that in both I did 3 things in this order 1: Open music folder (typing 'music' then pressing 'ENTER') 2: Open home folder (typing 'home' then pressing 'ENTER') 3: Open home folder (typing 'enhi' then pressing 'ENTER') As stated before there is no mention of opening anything in either output file during the time that I attempted to open the home folder as in (2: from above) even though the Home Folder menu item is successfully opened when gnome-do is started from terminal and Home Folder menu item fails to open when gnome-do is auto-started. ** Attachment added: "python script to start gnome-do I used chmod 755 on it and add 'python /home/enhickman/gnome-do.py' to auto started applications" http://launchpadlibrarian.net/48574199/gnome-do.py -- Gnome-do fails to open Home folder https://bugs.launchpad.net/bugs/576731 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs