Clicking on "Browse C: Drive" in Dash does not bring wine c: drive if wine has not run a program yet.

Bug #875943 reported by Satchit Bhogle
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
wine1.4 (Ubuntu)
Triaged
Wishlist
Unassigned

Bug Description

OS: Ubuntu 11.10 Oneiric stable
Application: wine1.3 1.3.28-0ubuntu1

Clicking on Browse C: Drive dismisses the Dash, but does nothing thereafter. Tested both when there is an instance of Nautilus running and otherwise. The menu entry used to work in previous versions of Ubuntu: Lucid, Maverick and Natty.

Revision history for this message
Satchit Bhogle (satchitb) wrote :

A quick check reveals no ~/.wine folder exists, despite having installed wine. Should I have had installed or run some Windows program for this to appear?

Revision history for this message
Scott Ritchie (scottritchie) wrote :

Yes, you won't have a C:\ drive until Wine creates one, and it won't do that until it's run on something. I agree that it's slightly confusing to have such a launcher unhidden when it won't work, though.

affects: wine (Ubuntu) → wine1.4 (Ubuntu)
Changed in wine1.4 (Ubuntu):
importance: Undecided → Wishlist
status: New → Triaged
summary: - Clicking on "Browse C: Drive" in Dash does not bring wine c: drive
+ Clicking on "Browse C: Drive" in Dash does not bring wine c: drive if
+ wine has not run a program yet.
Revision history for this message
micove (micove) wrote :

Adding a

"wineboot -i"

In wine1.4.postinst should do the trick. It will create a .wine if there is none and basically do nothing if there is one.

It works with or without X11 running since I always use it when installing from a minimal/netboot iso.

The only issue it may cause is scaring users with the gazillions of "fixme" messages that wine throws normally if it has to create the .wine folder.

Revision history for this message
Scott Ritchie (scottritchie) wrote :

We don't want to create an empty wine directory for no reason just to make it browseable. There are legitimate use cases for having Wine installed but not having ~/.wine (eg, you only use it to run an App depending on Wine that uses its own prefix)

Regardless putting that sort of logic in the maintainer script is forbidden, since it would mess with a user folder (and only one user too).

IMO what's needed here is for the desktop OS to be able to hide the browse C drive launcher if it doesn't actually point to anything. In the past I've advocated Gnome for instance use a bookmark to ~/.wine/drive_c/, which would in turn autohide, but upstream didn't want to do it. It might be an option for us though.

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.