gecko can't run

[allisfree]

It always crash when I run wine iexplore www.winehq.org. I have tried to remove ~/.wine

Then, I remove .xinitrc, run xinit, run wine iexplore www.winehq.org, everything is fine.

Does the wine have a dependency on KDE?

Where to paste the debug logs? WINEDEBUG=+relay,+seh,+tid wine iexplore www.winehq.org &>winebug.log The log seems increase for ever. So I kill the command. Although the log is 51M.

[doh123]

what the heck is in your .xinitrc thats breaking wine?

[DaVince]

Does the wine have a dependency on KDE?

No, nor does it have one to Gnome.

[allisfree]

I have another system installed on an usb drive, with the same .xinitrc, the same desktop environment KDE (but usb system have a full installation).

the wine gecko on my usb system works fine. I can chroot in usb system on the previous normal system, and it works fine too.

So I guess some dependency is broken.

p.s. wine works fine except gecko on my normal system

[James McKenzie]

allisfree wrote:

I have another system installed on an usb drive, with the same .xinitrc, the same desktop environment KDE (but usb system have a full installation).

the wine gecko on my usb system works fine. I can chroot

This is extremely dangerous if you are chrooting to the root user. Wine
should not be run as root unless you have a special reason to do so.

in usb system on the previous normal system, and it works fine too.

So I guess some dependency is broken.

p.s. wine works fine except gecko on my normal system

Did you originally run Wine as root? This looks like a dependency
problem, not a Wine one.

James McKenzie

[allisfree]

This is extremely dangerous if you are chrooting to the root user. Wine
should not be run as root unless you have a special reason to do so.

I use:

Code: Select all

sudo chroot --userspec=foo:foo .

This looks like a dependency
problem, not a Wine one.

I can't find what the wine dependent on? Any suggestion is welcome

[James McKenzie]

allisfree wrote:

James McKenzie wrote:

This is extremely dangerous if you are chrooting to the root user. Wine
should not be run as root unless you have a special reason to do so.

I use:
Code:
sudo chroot --userspec=foo:foo .

Ok, as long as Foo is not a privileged user..

James McKenzie wrote:

This looks like a dependency
problem, not a Wine one.

I can't find what the wine dependent on? Any suggestion is welcome

Clarification: This looks like an OPERATING SYSTEM dependency. Wine
only runs in user space and can only do what you tell it to do...

James McKenzie

[allisfree]

The problem has been resolved. Just change the LC_CTYPE from zh_CN.utf8 to en_US.utf8