Wine hangs on "wine: creating configuration directory"
 

I've installed the newest version of wine via yum.

If I try to run winecfg from the command line I get:

wine: creating configuration directory '/home/tnunamak/.wine'...

Then it hangs.

Same thing happens if I'm trying to run an app or the filesystem browser. In case it's relevant, I'm running the 64 bit version of Fedora 6, and wine was working great a few days ago on another installation on the same computer.

Any ideas?

bump......

If you're running wine from rpm it's pre-built. Should be no problems, unless maybe SELinux is cutting in. Check the output of /var/log/messages for AVC Denials.

yum provides setroubleshooter

Very strange, I've reinstalled a few times and suddenly it worked this time.

Wine does NOT work on fedora core 6
 

I've been on the wine HQ site, and they mention the problem of fedora 6 and wine. So far, no fix. It was thought that SElinux was the problem.

On mine, winecfg works to a certain point, and then crashes. On reinstall and run number 6, I get:

Warning: the specified Windows directory L"c:\\windows" is not accessible.
Warning: the specified System directory L"c:\\windows\\system32" is not accessible.
Warning: could not find DOS drive for current working directory '/home/harold', starting in the Windows directory.
fixme:midi:OSS_MidiInit Synthesizer supports MIDI in. Not yet supported.

I don't have a midi, and it is NOT enabled on my system. But run it as root, or as user, and no dice.
Any Ideas anyone?

:confused:

Right. The compiled versions of wine do not work correctly but RPM packages do.

Running wine from the build folder also works, providing you chcon -t textrel_shlib_t all the executables in there. SELinux will deny wine-preloader from preloading from the user's home directory, but it will work (despite wine-preloader generating LOTS of AVC denials). When wine is installed via `make install` the preloader is allowed to run but now wine fails to run some apps, this time without the SELinux errors. Wine-preloader starts silently messing thigs up. I'm sure this preloader problem is going to generate a lot of nasty unnecessary application-specific buzilla traffic.

RPM packages work fine, however, as do custom RPMs built according to the instructions on the rpm dev site or the condensed version on The Nerd Show. So... something in the rpm build process or spec file, possibly the extra configure option --disalbe-static, is fixing whatever preloader/SELinux problem Fedora Core 6 has...

The errors you are getting with c:\\windows not accessible can be corrected by putting a link back to ~/.wine/drive_c/windows from your current drive c: folder or by backing up and re-creating your .wine folder:

cd
mv .wine .wineold
wineprefixcreate

Wine hangs on "wine: creating configuration directory
 

Okay, I've tried install with rpm and compiled in. No luck there. Removed all the old wine files, turned off selinux and tried again.
Still does not work. When I enter "winecfg" thru the console, this is what I get happening:

root@xxxxx~/.wine: creating configuration directory '/root/.wine'...
fixme:midi:OSS_MidiInit Synthesizer supports MIDI in. Not yet supported.
Failed to open the service control manager.

This is what I get on Fedora 6. version 2.6.18-1.2849.fc6. No luck on using wine as user or root.
But still I try.:confused:

Wine does NOT work on fedora core 6
 

Problem then. No AVC Denials in /var/log/messages, and it was installed from the fedora 6 rpm's of wine.

So used RPMs for Fedora Core 6, but no luck. Also tried from source code, again, no luck.
:confused:

Those error messages are normal. You should get a nice little winecfg window in a few minutes, after it creates a new .wine folder. Perhaps you have messed up the permissions in your home folder. No matter, remove the old .wine and re-run winecfg.

If you upgraded to FC6 from FC5, your yum is out of date:

Go into the /etc/yum.repos.d and edit the repos, enable only core, extras and updates.

yum clean all
yum update yum

Yum is now fixed up, just like as if you installed fresh...

Optionally go to http://livna.org and download their rpm for "using livna"

OK

Remove the old wine and install wine through yum, e.g.
yum remove wine*

or the more dangerous command:
rpm -qa |grep wine |xargs rpm -e

and then
yum update -y


Now...

yum install wine* -y

All correct and good to go. Fedora is just a collection of files. If this doesn't work, maybe you got hardware issues...

Some useful links for debugging rpm-based systems:
Maximum RPM Chapter 6 (should probably read the whole thing someday)
http://www.rpm.org/max-rpm-snapshot/...ERIFY-A-OPTION

man rpm
man yum

Oh, and don't run wine as root.

Wine hangs on "wine: creating configuration directory
 

Okay, still does not work. WINE did work PERFECTLY on Fedora Core 5. So I don't know what hardware issues that I could possibly have. Even a clean install of fedora 6 did not change things. WINE just does not seem to install correctly or even work.

Sorry.
:confused: