Do

Home plug in not working when gnome-do is started at login

Bug #366590 reported by Gorgonilla
This bug report is a duplicate of:  Bug #290136: Post Intrepid. Can't open Home folder. Edit Remove
2
Affects Status Importance Assigned to Milestone
Do
New
Undecided
Unassigned
Do Plugins
Invalid
Low
Unassigned

Bug Description

If you set gnome-do to automatically start up at login and then type "home" the cursor shows the beam for few seconds and nothing happens.
If you close gnome-do and start it manually, by typing "home" it opens nautilus at your home folder as supposed to do.
In my opinion it looks like that when started at login, the process belongs to system and, since "home" is a user related folder, the plug in cannot find it. If you start it manually, the process belong to the user and perhaps the plug-in can find "home" straight ahead.
This is an annoying bug since it's good to have gnome-do at startup but it's also very useful just to type "home" and have your home folder displayed automatically

Revision history for this message
Chris S. (cszikszoy) wrote :

This is actually a problem with do-core, and not related to plugins. Do ends up starting faster than the env variable for home is set, which is why it works fine after you quit and restart.

Changed in do-plugins:
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Gorgonilla (lviggiani) wrote : Re: [Bug 366590] Re: Home plug in not working when gnome-do is started at login

Thanks for the information.
Any idea about when this bug will be solved?

On Sat, 2009-04-25 at 10:44 +0000, Chris S. wrote:

> This is actually a problem with do-core, and not related to plugins. Do
> ends up starting faster than the env variable for home is set, which is
> why it works fine after you quit and restart.
>
> ** Changed in: do-plugins
> Importance: Undecided => Low
>
> ** Changed in: do-plugins
> Status: New => Confirmed
>

Changed in do-plugins:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.