This is a long tale - most of which is probably not relevant. 1) I installed wine on Fedora 17 and encountered a problem which turned out to be because wine now includes 64-bit EXE execution capabilities. I therefore deleted .wine, and set up a wineprefix restricted to 32 bits - as advised here. This worked nicely. 2) At some point I accidentally ran wine as super user :( 3) I wanted to add a drive to wine so I ran winecfg, which gave the message L"C:\\windows\\system32\\wineboot.exe" although the GUI then appeared. 4) When I clicked on the Drives tab, I got the message: Failed to connect to the mount manager. I tried deleting .wine, uninstalling wine and reinstalling, but I can't fix winecfg Can anyone help me to get winecfg working, or maybe point out a file where the drive information is stored? Also, if wine is not to be used as super user, why doesn't it check for that eventuality and stop with an error message before any damage is done? David
David Bailey wrote:> 2) At some point I accidentally ran wine as super user :(http://wiki.winehq.org/FAQ#head-8b89c928ce782c014b8b312469223296093e1484> 4) When I clicked on the Drives tab, I got the message: Failed to connect to the mount manager.Sounds like you didn't install all the necessary 32 bit parts of Wine. I believe Fedora splits Wine into lots of different packages; make sure you have all the ones you need.> Also, if wine is not to be used as super user, why doesn't it check for that eventuality and stop with an error message before any damage is done? >It's not recommended, but ultimately it's the user's choice.
The "wine" metapackage installs all the required subpackages. It exists in both 64 and 32 bits versions. David Bailey wrote:> > dimesio wrote: > > > > Sounds like you didn't install all the necessary 32 bit parts of Wine. I believe Fedora splits Wine into lots of different packages; make sure you have all the ones you need. > > > > > Do you know where to find this list - or better, which one contains wineboot.exe . > > Clearly the downside to spitting wine into many packages, is that it is messy to completely reinstall. > > > > > It's not recommended, but ultimately it's the user's choice. > > > Still it would be nice if you got an error message unless you configured it otherwise. > > David
Martin Gregorie wrote:> On Mon, 2012-06-18 at 15:37 -0500, David Bailey wrote: > > > > I don't really understand, surely the very first line of wine's main() > > could contain a test for super user - just attempt to make a directory > > inside /etc - should do, but I am sure their are neater methods. > > > > > There's a much easier way: > > if (strcmp(getenv("USER"), "root") == 0) > if (!run_as_root_ok) > { > fprintf(stderr, "Error: wine is being run as root\n"); > exit(EACCESS); > } > > > MartinWell yes - though I would prefer a dialog box - wine tends to spew out quite a few errors to the console even for working code - they tend to get ignored, and the program might not be interactive. The point is, even when you know about the problem, it is so easy to make a mistake. For example, I use Notepad++ under wine, so I am invoking wine all the time. David
You both might want to add comments to http://bugs.winehq.org/show_bug.cgi?id=17337.
On Mon, 2012-06-18 at 19:19 -0500, dimesio wrote:> You both might want to add comments to http://bugs.winehq.org/show_bug.cgi?id=17337. >Done. Martin