Find the answer to your Linux question:
Page 2 of 2 FirstFirst 1 2
Results 11 to 12 of 12
Thankyou very much. Did the lastest steps and had no reply from the non-verbose. When I typed "type wine" it came up with the directery. However when i tried typing ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #11
    Just Joined!
    Join Date
    Jul 2006
    Posts
    9

    Thankyou very much.

    Did the lastest steps and had no reply from the non-verbose. When I typed "type wine" it came up with the directery.

    However when i tried typing in the command wine program.exe it comes up with a segmentation fault

    e.g anyone@hall:~/mohaa> wine progman
    Segmentation fault

  2. #12
    Linux Enthusiast KenJackson's Avatar
    Join Date
    Jun 2006
    Location
    Maryland, USA
    Posts
    510
    I'm starting to run out of ideas.

    Often when you get a segmentation fault, it's because an old library file is being mistaken for the right one. I wonder if you have any older files from that previous wine installation. You could search for files ending in .dll.so like this:
    $ find ~/ -name \*.dll.so
    $ find /usr -name \*.dll.so | grep -v '^/usr/lib/wine/'

    That's a big search that could take a couple minutes. Also, maybe there are some real Windows .dll files that are competing with the Wine files.

    If that doesn't turn anything up, you could try this:
    $ strace wine progman

    The strace program spews a huge volume of debug stuff to the screen, but hopefully the last thing it shows you before it crashes will be helpful--like accesing some file it shouldn't be.

Page 2 of 2 FirstFirst 1 2

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •