Wine is freezing

[simetri]

I have Opensuse 11.0. Using icewm. When I run winecfg or any windows application it freezes in 1 minutes. Why?

PS: Computer is not freezing.

[oiaohm]

lack of details. Distribution names mean nothing to us.

wine --version on a terminal will give you the wine version.

older winecfg programs had a locking problem with itself. First run of the day of wine also indexes fonts that can take a while.

Basically that is the common cause of 1 min wait. Without version of wine cannot really list any of the others.

[simetri]

lack of details. Distribution names mean nothing to us.

wine --version on a terminal will give you the wine version.

older winecfg programs had a locking problem with itself. First run of the day of wine also indexes fonts that can take a while.

Basically that is the common cause of 1 min wait. Without version of wine cannot really list any of the others.

I tried version 1.1.37, 1.1.38 and 1.1.39.

[tpreitzel]

This problem certainly sounds like a driver problem that I'm having with AverTv's averusbh82d.ko driver. Whenever I run winecfg (audio section only), the computer would freeze within about 30-45 seconds.

So, if you don't use an AverTV card, you still need to look for a driver causing the problem. This latter process can take some time.

Good luck.

[simetri]

This problem certainly sounds like a driver problem that I'm having with AverTv's averusbh82d.ko driver. Whenever I run winecfg (audio section only), the computer would freeze within about 30-45 seconds.

So, if you don't use an AverTV card, you still need to look for a driver causing the problem. This latter process can take some time.

Good luck.

How can I understand which driver does this?

By the way, my computer is not freezing. Only wine freezes.

[simetri]

And I forgot something to write. My computer is a VPS. Doesn't have TVTunner or soundcard on it.

[oiaohm]

simetri winecfg itself is mostly single threaded. So while it waiting for hardware detects to report back it pauses. Yes it really should say its busy.

Really winecfg is not a good application to test for freesing with. It design it is likely todo it.

wine notepad is normally only hit by startup freeses. Yes most of those are known things like font indexing.

simetri locating freesing itself has many causes. compiz running is also known to disrupt inputs and can cause feasing. Same with pulseaudio running even if you have no sound card. To be correct pulseaudio is more likely to cause wine to stall if it has no sound card.

This is the problem stack of causes what one is it.

[tpreitzel]

And I forgot something to write. My computer is a VPS. Doesn't have TVTunner or soundcard on it.

Ok, I evidently missed the fact that the computer itself wasn't freezing, just WINE. In your case, I don't know the cause.

HOWEVER, IF in the future one sees the computer itself freeze, not just WINE, then the scenario is likely a driver. Isolating the offending driver simply means painstakingly removing the hardware and its concomitant driver until the freeze disappears.

Good luck with the problem and hopefully someone else can point you in the right direction.

[Usurp]

And I forgot something to write. My computer is a VPS. Doesn't have TVTunner or soundcard on it.

You don't have a network printer installed that is unreachable now, do you ?

[simetri]

simetri winecfg itself is mostly single threaded. So while it waiting for hardware detects to report back it pauses. Yes it really should say its busy.

Really winecfg is not a good application to test for freesing with. It design it is likely todo it.

wine notepad is normally only hit by startup freeses. Yes most of those are known things like font indexing.

simetri locating freesing itself has many causes. compiz running is also known to disrupt inputs and can cause feasing. Same with pulseaudio running even if you have no sound card. To be correct pulseaudio is more likely to cause wine to stall if it has no sound card.

This is the problem stack of causes what one is it.

What do you suggest to me?

[dimesio]

What do you suggest to me?

Post terminal output.

[simetri]

What do you suggest to me?

Post terminal output.

I'm not a *nix professional. Can you describe me how to do it?

[dimesio]

I'm not a *nix professional. Can you describe me how to do it?

Open a terminal, type winecfg at the prompt, and hit enter. Post whatever messages appear.

[John Drescher]

On Mon, Mar 1, 2010 at 9:40 PM, simetri <[email protected]> wrote:

dimesio wrote:

simetri wrote:

What do you suggest to me?

Post terminal output.

I'm not a *nix professional. Can you describe me how to do it?

http://wiki.winehq.org/FAQ#head-13df66c ... 1479c880f5

John

[simetri]

I'm not a *nix professional. Can you describe me how to do it?

Open a terminal, type winecfg at the prompt, and hit enter. Post whatever messages appear.

Nothing happened. Only wincfg frozen.

[simetri]

http://wiki.winehq.org/FAQ#head-13df66c ... 1479c880f5

John

What I did is;

cd ~/.wine/drive_c/windows
wine notepad.exe &> log.txt

Notepad run 15 seconds. Then frozen. log.txt was empty.

[vitamin]

Notepad run 15 seconds. Then frozen. log.txt was empty

Then run this:

Code: Select all

wine winedbg notepad
....
Wine-dbg>cont

When notepad freezes press [ctrl]+[c] then type:

Code: Select all

Wine-dbg>bt all

Post _complete_ output to pastebin and link here.

[simetri]

Notepad run 15 seconds. Then frozen. log.txt was empty

Then run this:

Code: Select all

wine winedbg notepad
....
Wine-dbg>cont

When notepad freezes press [ctrl]+[c] then type:

Code: Select all

Wine-dbg>bt all

Post _complete_ output to pastebin and link here.

wine winedbg notepad
....
Wine-dbg>cont

was ok but after notepad freezing, when I do [ctrl]+[c] it drops to shell not Wine-dbg>

So I couldn't do "bt all".

[vitamin]

was ok but after notepad freezing, when I do [ctrl]+[c] it drops to shell not Wine-dbg>

What version of Wine are you using? Where did you get it from and how did you installed it?

[simetri]

was ok but after notepad freezing, when I do [ctrl]+[c] it drops to shell not Wine-dbg>

What version of Wine are you using? Where did you get it from and how did you installed it?

Opensuse repository

Code: Select all

"http://download.opensuse.org/repositories/Emulators:/Wine/openSUSE_11.0/"

[vitamin]

Opensuse repository

Code: Select all

"http://download.opensuse.org/repositories/Emulators:/Wine/openSUSE_11.0/"

Don't use that one. It has bug in the package - it creates 64-bit Wine:

Code: Select all

./configure ... --enable-win64

That's not what you want to run windows programs.

[simetri]

Opensuse repository

Code: Select all

"http://download.opensuse.org/repositories/Emulators:/Wine/openSUSE_11.0/"

Don't use that one. It has bug in the package - it creates 64-bit Wine:

Code: Select all

./configure ... --enable-win64

That's not what you want to run windows programs.

What do you suggest? Compiling from source?

[simetri]

I download version 1.1.40 from winehq.org as a source. I extract and compile from the source. It still runs 15-20 seconds than notepad freezes to eternity.
Why?

[oiaohm]

You did do wine --version to make sure you have 1.1.40 not still having the the old instal 1.1.39

[simetri]

You did do wine --version to make sure you have 1.1.40 not still having the the old instal 1.1.39

I checked from both consol "wine --version" and "winecfg about" page

Both says
wine-1.1.40