When I run the winecfg command, (after installing wine) either from the menu or by a command in Terminal after a few seconds the whole PC freezes and has to be rebooted to continue.
I am running the latest Ububntu version with a reasonable spec PC. I have fully renistalled Ubuntu and also removed and reinstalled wine several times. Having searched this forum the only mention of a similar problem is quoted below. I am new to linux and wine but fairly knowlegable on PCs.
Any ideas?
Quote
'Running winecfg seems to hang or complain about files when I click the audio tab
The hang is caused by the "NAS" sound driver. This causes it to pause for a while but it should respond eventually. The only way to get around this is to remove NAS from your system and/or build Wine without NAS support in the first place. If you see messages about JACK in the terminal they can be ignored unless you intend to use the JACK driver. If you wish to use the JACK driver then you need to install JACK's libraries onto your machine before JACK will work.'
Configuring wine
-
Paul Johnson
Configuring wine
On Tuesday 11 March 2008 07:54:02 am les wilde wrote:
your graphics drivers and GL library are properly installed?
--
Paul Johnson
[email protected]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://www.winehq.org/pipermail/wine-us ... chment.pgp
Sounds more indicative of a video problem from my experience. Are you sureWhen I run the winecfg command, (after installing wine) either from the
menu or by a command in Terminal after a few seconds the whole PC freezes
and has to be rebooted to continue. I am running the latest Ububntu version
with a reasonable spec PC. I have fully renistalled Ubuntu and also removed
and reinstalled wine several times. Having searched this forum the only
mention of a similar problem is quoted below. I am new to linux and wine
but fairly knowlegable on PCs. Any ideas?
your graphics drivers and GL library are properly installed?
--
Paul Johnson
[email protected]
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url : http://www.winehq.org/pipermail/wine-us ... chment.pgp
-
Dan Kegel
Configuring wine
On Tue, Mar 11, 2008 at 7:54 AM, les wilde <[email protected]> wrote:
What graphics card do you have? What drivers?
You probably are using an Nvidia graphics card, and
have a mismatch between your Nvidia graphics drivers
and the kernel. Try reinstalling the Nvidia drivers.
Let us know what happens.
- Dan
Does the command 'glxgears' also lock up the system?When I run the winecfg command, ... after a few seconds the
whole PC freezes and has to be rebooted to continue.
I am running the latest Ububntu version with a reasonable spec PC.
I have fully renistalled Ubuntu and also removed and reinstalled wine several times.
What graphics card do you have? What drivers?
You probably are using an Nvidia graphics card, and
have a mismatch between your Nvidia graphics drivers
and the kernel. Try reinstalling the Nvidia drivers.
Let us know what happens.
- Dan
I had this exact same problem. Believe it or not, it actually turned out to be my sound card. I was using a Dynex 5.1 PCI sound card. I cannot remember off hand what driver that uses in Ubuntu.
Taking out the sound card caused winecfg to complete normally and then I could put the sound card back in and use wine (as long as I didn't go to the sound settings in winecfg, as that would lock up the whole system again).
I ended up just buying a different sound card.
Taking out the sound card caused winecfg to complete normally and then I could put the sound card back in and use wine (as long as I didn't go to the sound settings in winecfg, as that would lock up the whole system again).
I ended up just buying a different sound card.
wine config
Thanks for the replies
The PC has on board sound and graphics cards
I have disabled the sound card in bios but the problem still occurs
I have tried running 'glxgears' and that works fine with no problems
A little baffling!!!
Just a note
when I run wine config it takes about 3 or 4 seconds before it locks up. The hard drive still wurrs on for 10 to 15 seconds.
Ubuntu is installed as the only operating system on a 4 year old 20g hard drive.
I do not know where to go from here???
The PC has on board sound and graphics cards
I have disabled the sound card in bios but the problem still occurs
I have tried running 'glxgears' and that works fine with no problems
A little baffling!!!
Just a note
when I run wine config it takes about 3 or 4 seconds before it locks up. The hard drive still wurrs on for 10 to 15 seconds.
Ubuntu is installed as the only operating system on a 4 year old 20g hard drive.
I do not know where to go from here???
-
Mark Knecht
Configuring wine
On Tue, Mar 11, 2008 at 7:54 AM, les wilde <[email protected]> wrote:
1) completely removed NAS from your system.
2) Built wine from WineHQ.org source tarball with NAS disabled.
In my experience the Jack sound stuff is a non-issue if you're not
running the Jack server.
Hope this helps,
Mark
Have you done what the message above called for?When I run the winecfg command, (after installing wine) either from the menu or by a command in Terminal after a few seconds the whole PC freezes and has to be rebooted to continue.
I am running the latest Ububntu version with a reasonable spec PC. I have fully renistalled Ubuntu and also removed and reinstalled wine several times. Having searched this forum the only mention of a similar problem is quoted below. I am new to linux and wine but fairly knowlegable on PCs.
Any ideas?
Quote
'Running winecfg seems to hang or complain about files when I click the audio tab
The hang is caused by the "NAS" sound driver. This causes it to pause for a while but it should respond eventually. The only way to get around this is to remove NAS from your system and/or build Wine without NAS support in the first place. If you see messages about JACK in the terminal they can be ignored unless you intend to use the JACK driver. If you wish to use the JACK driver then you need to install JACK's libraries onto your machine before JACK will work.'
1) completely removed NAS from your system.
2) Built wine from WineHQ.org source tarball with NAS disabled.
In my experience the Jack sound stuff is a non-issue if you're not
running the Jack server.
Hope this helps,
Mark
wine config
Mark
Thanks for the reply
AS mentioned in my original post I am a Linux novice. Hence removing NAS would be something i would need help and instruction to do.
PLease feel free to reply with instructions or give me a link to where I may find them.
Other than that I will be changing the hard drive set up over the next few days to see if that makes a difference
Thanks for the reply
AS mentioned in my original post I am a Linux novice. Hence removing NAS would be something i would need help and instruction to do.
PLease feel free to reply with instructions or give me a link to where I may find them.
Other than that I will be changing the hard drive set up over the next few days to see if that makes a difference
-
Mark Knecht
Configuring wine
On Wed, Mar 12, 2008 at 1:04 AM, les wilde <[email protected]> wrote:
specific solution. I'm not going to help with that. Building Wine
without NAS support is a Wine solution. you are on the right list to
get help with that.
Basically what you need to do is go to the WineHQ.org web site and
download the newest tarball. You will build a local/personal copy of
wine without NAS support and see if it helps. If it does then great.
you have a short term solution anyway.
Building Wine is relatively easy. Probably takes less than an hour on
most machines. Ask for help here when you've read the instructions but
off the top of my head there are probably only about 4 commands you
need to execute to do it.
Time to start learning! Instructions at
http://www.winehq.org//site/docs/wineus ... ine-source
You do NOT need to uninstall wine from your system to build a local
copy for testing.
Cheers,
Mark
The original message gave you two options. Removing NAS is a distroMark
Thanks for the reply
AS mentioned in my original post I am a Linux novice. Hence removing NAS would be something i would need help and instruction to do.
PLease feel free to reply with instructions or give me a link to where I may find them.
Other than that I will be changing the hard drive set up over the next few days to see if that makes a difference
specific solution. I'm not going to help with that. Building Wine
without NAS support is a Wine solution. you are on the right list to
get help with that.
Basically what you need to do is go to the WineHQ.org web site and
download the newest tarball. You will build a local/personal copy of
wine without NAS support and see if it helps. If it does then great.
you have a short term solution anyway.
Building Wine is relatively easy. Probably takes less than an hour on
most machines. Ask for help here when you've read the instructions but
off the top of my head there are probably only about 4 commands you
need to execute to do it.
Time to start learning! Instructions at
http://www.winehq.org//site/docs/wineus ... ine-source
You do NOT need to uninstall wine from your system to build a local
copy for testing.
Cheers,
Mark
wine config
javascript:emoticon(':D')
Thanks for all who replied
It seemed like it was going to be a hardware fault, and it was!!
I tried the same hard drive in another machine and after reinstalling Ubuntu and the installing wine the config command worked as it should with no lockups.
I will try the original machine again when I gat the time changing video and sound cards to see where exactly the fault was.
At least I have an answer
Thanks again
Thanks for all who replied
It seemed like it was going to be a hardware fault, and it was!!
I tried the same hard drive in another machine and after reinstalling Ubuntu and the installing wine the config command worked as it should with no lockups.
I will try the original machine again when I gat the time changing video and sound cards to see where exactly the fault was.
At least I have an answer
Thanks again
