wine freezes ubuntu

[mikejs...@gmail.com]

Ahhhh, i am new at this so bear with me...

ok i can't get wine to work.

i am able to install wine fine. but when i try to run winecfg or
winedbg or basically anything related to wine my computer lockes up
and i have to do a manual reboot.
each time i try and run winecfg it creates a .wine-XXXXX folder with
the normal dosdevices and drive_c folders. where XXXXX seems to be
random letters and numbers.

i am running ubuntu 7.04
nvidia geforce 6200

any help would be great.

mike

[DanKegel]

On Apr 28, 2:25 pm, mikejschm...@gmail.com wrote:
> i am able to install wine fine. but when i try to run winecfg or
> winedbg or basically anything related to wine my computer lockes up
> and i have to do a manual reboot.

Then you have an X driver problem (or possibly a hardware problem).
As long as you're not running Wine as root, it *cannot*
lock up a properly working system.

> each time i try and run winecfg it creates a .wine-XXXXX folder with
> the normal dosdevices and drive_c folders. where XXXXX seems to be
> random letters and numbers.

That's normal. The funky name gets renamed to .wine as soon as it's
complete.

> i am running ubuntu 7.04
> nvidia geforce 6200

Does glxgears also crash your system?
- Dan

[mikejs...@gmail.com]

> Does glxgears also crash your system?
> - Dan

thanks for the reply.

glxgears does not lock up my system.

am i the only one who has this problem?

any other ideas?

mike

[jan]

I have had the problem with winecfg not completing for since about version
0.9.29ish, or when I replaced FC5 with FC6. Have been too busy to look
carefully. Deleting the winexxx folder, killing all wine processes and
retrying has not helped.

Recently, when wine-0.9.35-1.fc6 arived I was delighted to find that
winecfg completed, and I was able to re-install my main application,
Watchtower Library. This now runs well, but for one odd problem with
keyboard input:

I use scim for Chinese input. While running the Watchtower application the
keyboard appears to freeze. This is relieved by selecting English from the
scim task menu. This may happen frequently during program operation.

Will have to finish later, as I just tried to verify the above, but the
application executable seems to have gone missing, and winefile will not
launch either. I did just play with scim?!

Jan Coombs.
--

[jhan...@gmail.com]

On Apr 29, 5:28 pm, mikejschm...@gmail.com wrote:
> glxgears does not lock up my system.
>
> am i the only one who has this problem?
>
> any other ideas?

It can be difficult to determine what is going on when the system
becomes non-responsive. It can be a hardware lockup, kernel/video
problem, X server, or just wine hogging the CPU. The next time it
happens, try toggling the Num Lock or Caps Lock key and see if the
keyboard LEDs change. If they do then try switching to a different
terminal (Ctrl-Alt-F1). If nothing works, try a different PC or
different distro. Another option is to set up a SSH server or a
serial console which will give you access even if the X server has the
keyboard locked: http://www.howtoforge.com/setting_up_a_serial_console

[mikejs...@gmail.com]

> It can be difficult to determine what is going on when the system
> becomes non-responsive. It can be a hardware lockup, kernel/video
> problem, X server, or just wine hogging the CPU. The next time it
> happens, try toggling the Num Lock or Caps Lock key and see if the
> keyboard LEDs change. If they do then try switching to a different
> terminal (Ctrl-Alt-F1). If nothing works, try a different PC or
> different distro. Another option is to set up a SSH server or a
> serial console which will give you access even if the X server has the
> keyboard locked: http://www.howtoforge.com/setting_up_a_serial_console

the caps lock and num lock are not responsive. switching terminals
also doesn't work.

when i first built this computer and installed dapper drake wine
worked fine. but something happened, i was guessing that i just
messed it up not knowing what i was doing, and then wine would not
work anymore. i was hopeing with this fresh install of feisty fawn
that all would be well again, but still wine would still not work.

is there some kind of error report or log that can give me more
information? i have looked at the /var/log/messages and the only
thing close to the time of lock up is something about an incorrect key
mapping or something.

thanks again for any help

mike

[jhan...@gmail.com]

On Apr 30, 4:54 pm, mikejschm...@gmail.com wrote:
> is there some kind of error report or log that can give me more
> information? i have looked at the /var/log/messages and the only
> thing close to the time of lock up is something about an incorrect key
> mapping or something.

Try:
~/.xsession-errors
/var/log/Xorg.0.log
or just run it from a terminal window and watch the output. There are
also environment variables that control how much debugging info Wine
outputs:
http://www.winehq.com/site/docs/wineusr-guide/x543

[kuartel...@gmail.com]

Hi. I have exactly the same problem. My system is working with the
latest Ubuntu and Wine. With the previous distro of Ubuntu the
same....
The computer:
- AMD Athlon(tm) 64 Processor 3500+ AM2 Socket
- 1Gb DDR2
- 2 sound cards (Onboard VIA and PCI mAudio Audiophile 192)
- 2 s-ata harddisks & 1 IDE harddisk
- ATI X1300XT PCIe with 3D hardware acceleration enabled (ATI driver)
- Ubuntu Feisy Fawn 32Bit

I think my problem are the 2 sound cards, sometimes when i boot up,
the primary card is the mAudio and other times the VIA. Maybe its an
ALSA configuration problem.