"Run in Wine configuration" destructively alters Nautilus environment variables

Bug #522205 reported by marzojr
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Vineyard
Fix Released
Medium
Christian Dannie Storgaard

Bug Description

This problem is more easily seen in conjunction with the nautilus-open-terminal package, but it also affects other software; Nautilus itself is unaffected.

How to reproduce: assuming nautilus-open-terminal is installed:
- Open any folder and select "open in terminal" from right-click menu.
- Run `echo $HOME` in the new terminal; expected output is the user's home directory.
- Select a Windows exe and open it in an alternate Wine configuration (an otherwise empty bottle -- other than the default -- is enough); then close this application.
- Open a new terminal from the right click menu and run `echo $HOME`. The output will be the .winebottle/bottle-* of the configuration. Similarly, "~/" will expand to this same directory.

This persists across Nautilus sessions, although I haven't tried restarting Gnome to see if it persists. The only way to fix this is to run a Windows exe in the default Wine configuration, at which point everything goes back to normal. As stated above, this doesn't affect Nautilus itself, only the programs it runs; and not all programs are sensitive to it.

The expected behavior would be for the environment to be cleaned up afterwards.

Changed in vineyard:
importance: Undecided → Medium
assignee: nobody → Christian Dannie Storgaard (cybolic)
milestone: none → 1.4.2
Revision history for this message
Christian Dannie Storgaard (cybolic) wrote :

This is fixed in trunk. Vineyard (python-wine) now uses a copy of the environment for every sub-process call.

Changed in vineyard:
status: New → Fix Committed
Revision history for this message
Abdusamed Ahmed (sir508) wrote :

This bug was causing Nautilus to freeze for me. It was triggering what this bugs says which was exactly what was happening to me
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/611468

I had to do something close to this http://ubuntuforums.org/showthread.php?t=514081

I had to delete the vineyard configuration file manually. There were I think five or four python extension/scripts for nautilus. I can say confidently that they were pretty buggy. I later decided for complete removal of this program for safety.

Revision history for this message
Abdusamed Ahmed (sir508) wrote :

I'm on lucid 10.04.1 with Nautilus being updated via it's ppa...

Changed in vineyard:
status: Fix Committed → Fix Released
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.