Wine Segmentation fault

albundy · Post by **albundy** » Thu Oct 15, 2009 9:34 am

Hello,

I use ubuntu 9.04 and I have freshly installed wine from depot :
deb http://wine.budgetdedicated.com/apt jaunty main
Unfortunatelly, I can't do anything with it, because, when I run wine or winecfg, I have "Segmentation fault" directly without other message...
Is there a log file or something else which could help me to determine wher is my problem ?

albundy · Post by **albundy** » Thu Oct 15, 2009 1:17 pm

I use the version wine 1.1.31, no one could tell me some basics commands to check if something could be missing ... ?

Code: Select all

user@mypc:~$ winecfg
Segmentation fault

I have nothing at all to work on ....
Please help.

albundy · Post by **albundy** » Thu Oct 15, 2009 2:23 pm

And with this, anyone could help ?

Code: Select all

user@mypc:~$ ldd /usr/bin/wine
	linux-gate.so.1 =>  (0xb80b4000)
	libwine.so.1 => /usr/bin/../lib/libwine.so.1 (0xb7f76000)
	libpthread.so.0 => /lib/tls/i686/cmov/libpthread.so.0 (0xb7f4e000)
	libc.so.6 => /lib/tls/i686/cmov/libc.so.6 (0xb7dea000)
	libdl.so.2 => /lib/tls/i686/cmov/libdl.so.2 (0xb7de6000)
	/lib/ld-linux.so.2 (0xb80b5000)

vitamin · Post by **vitamin** » Thu Oct 15, 2009 10:07 pm

albundy wrote:user@mypc:~$ winecfg
Segmentation fault

Reinstall Wine (completely remove it first). Reinstall video drivers.

albundy · Post by **albundy** » Fri Oct 16, 2009 3:43 am

Well, I have reinstalled it many times, and for my driver, I use the intel one adapted for my computer.

vitamin · Post by **vitamin** » Fri Oct 16, 2009 8:25 am

albundy wrote:Well, I have reinstalled it many times, and for my driver, I use the intel one adapted for my computer.

Then let it dump the core (ulimit -c unlimited). Run gdb with that core file and post the backtrace here.

albundy · Post by **albundy** » Fri Oct 16, 2009 6:28 pm

Hello,

here the requested informations :

Code: Select all

user@mypc:~$ winecfg
Segmentation fault (core dumped)

user@mypc:~$ gdb -core core
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
(no debugging symbols found)
Core was generated by `/usr/bin/wine-preloader /usr/bin/wine winecfg.exe'.
Program terminated with signal 11, Segmentation fault.
[New process 23096]
#0  0x7c000690 in ?? ()

Any idea with this ?

vitamin · Post by **vitamin** » Fri Oct 16, 2009 10:32 pm

albundy wrote:#0 0x7c000690 in ?? ()

Back trace would be helpful - "bt".

hirato · Post by **hirato** » Fri Oct 16, 2009 11:10 pm

(no debugging symbols found)

backtraces won't help much.

that's unless he installs a wine-dbg package (if one exists), or compiles wine from source himself (which as far as I know, compiles with debug symbols)

vitamin · Post by **vitamin** » Sat Oct 17, 2009 10:31 am

hirato wrote:
(no debugging symbols found)
backtraces won't help much.

Not a fact. In most cases this kind of crash was somewhere outside of Wine.

dimebar · Post by **dimebar** » Tue Oct 20, 2009 6:18 pm

I have also had this segmentation fault problem on Ubuntu Jaunty and it was a real showstopper. Even building the latest Wine from source didn't help. I have followed the instructions to generate a stack trace, but gdb seems unable to read the core file, and just tells me that no backtrace is available.

I finally figured out that this started happening when the kernel was upgraded to 2.6.28-15-generic. I rebooted back into kernel 2.6.28-14-generic and I can finally run Wine again. I hope this work-around helps anyone with a similar problem.

vitamin · Post by **vitamin** » Tue Oct 20, 2009 11:24 pm

dimebar wrote:I finally figured out that this started happening when the kernel was upgraded to 2.6.28-15-generic. I rebooted back into kernel 2.6.28-14-generic and I can finally run Wine again. I hope this work-around helps anyone with a similar problem.

Also check this thread: http://forum.winehq.org/viewtopic.php?t=6497