wine users - Mar 2009 - Esword just started crashing with segmentation fault

Hi all,

Been using Esword for months on a self-compiled wine (the self-compilation was
for WC3 hosting, but that's another story). Just today I tried to start it
up as usual and it flashed the main window and crashed. Running the command from
the terminal just gives me the cryptic 'segmentation fault' error.

I've tried upgrading Wine to 1.15 and 1.16 both, as well as a downgrade to
1.01 (official version in Ubuntu repos). The error does not occur for any other
apps on whichever version of Wine (I run various games as well as Esword on
Wine), only Esword. I was using Esword 7.9.8, version 8.0.6 gives exactly the
same error, even when installed from scratch.

Recent changes I've made include changing my compiz setup (I disabled compiz
to be sure that's not the case, the problem still happens) and editing my
conky scripts. No major system updates (Intrepid updates have slowed to almost
none).

My system is:-
Intrepid Ibex Ubuntu 8.10 amd64
Wine versions - various, as mentioned above
Steps to reproduce - if you have my system, just install based with riched20 and
oleaut32 native, that's the settings that have always worked for me for
Esword.

Please advise on what else I can do for trouble-shooting. I did not set the
WINEDEBUG variable, so I have a couple of fixme's, but those have not
changed from before when Esword was previously working.

lostandfound wrote:
> Please advise on what else I can do for trouble-shooting. I did not set the
WINEDEBUG variable, so I have a couple of fixme's, but those have not
changed from before when Esword was previously working.

Ah, been messing around with it and found something VERY peculiar (this is after
maybe 7 re-installs of the software). Basically, if I run


Code:
env WINEPREFIX=/home/data/wine/esword wine "C:\Program
Files\e-Sword\e-Sword.exe"



from the terminal, I get a segmentation fault. Similar result if I run it from
my dock, cairo-dock. BUT, if I have a launcher (e-Sword.desktop) containing that
very same line, then I do not get the segmentation fault.

Very peculiar behaviour. I believe its to do with bash or my env settings, but
have no idea how to test that out. Recommendations, please

lostandfound <wineforum-user at winehq.org> wrote on Mar
1st:
>
>lostandfound wrote:
>> Please advise on what else I can do for trouble-shooting. I did not set
the WINEDEBUG variable, so I have a couple of fixme's, but those have not
changed from before when Esword was previously working.
>
>
>Ah, been messing around with it and found something VERY peculiar (this is
after maybe 7 re-installs of the software). Basically, if I run
>
>
>Code:
>env WINEPREFIX=/home/data/wine/esword wine "C:\Program
Files\e-Sword\e-Sword.exe"
>
I will verify this.  Can you file a bug report and provide the issue number.  I
plan on using this program today.

You could run a regresstion test, but I can assist as well.

James McKenzie
Maintainer: e-Sword program.

lostandfound wrote:
> from the terminal, I get a segmentation fault. Similar result if I run it
from my dock, cairo-dock. BUT, if I have a launcher (e-Sword.desktop) containing
that very same line, then I do not get the segmentation fault.
Did you 'cd' into work directory when you run the program in the
terminal?

vitamin <wineforum-user at winehq.org> wrote on March
1st:
>
>lostandfound wrote:
>> from the terminal, I get a segmentation fault. Similar result if I run
it from my dock, cairo-dock. BUT, if I have a launcher (e-Sword.desktop)
containing that very same line, then I do not get the segmentation fault.
>
>Did you 'cd' into work directory when you run the program in the
terminal?
>
Vitamin:

I attempted to reproduce this with a copy of Wine for MacOSX built using Mike
Kronenberg's scripts at version 1.1.16 and could not if I changed
directories to the installation directory.  I even ran the upgrade script to
bring the program to version 8.06 without any errors.

James McKenzie

James McKenzie wrote:
> vitamin wrote:
> 
> > lostandfound wrote:
> > 
> > 
> > > from the terminal, I get a segmentation fault. Similar result if
I run it from my dock, cairo-dock. BUT, if I have a launcher (e-Sword.desktop)
containing that very same line, then I do not get the segmentation fault.
> > > 
> > > 
> > 
> > Did you 'cd' into work directory when you run the program in
the terminal?
> > 
> > 
> > 
> Just as a follow up to my last message, e-Sword runs here on a Wine
> 1.1.16 build based upon Mike Kronenberg's build environment.
> 
> James McKenzie

Hi, I'm sorry it took so long to get back here. After more examination, I
found that this only occured when running within the gnome-terminal environment.
xterm worked fine, as did alt-F2 and calling my script. It does not, at this
point, seem a Wine bug due to that. I have installed Ubuntu Jaunty and this
problem does not occur there, so there's something unique about my Intrepid
64bit install that caused the segmentation faults.

lostandfound <wineforum-user at winehq.org> wrote on March
9th:
>
>James McKenzie wrote:
>> vitamin wrote:
>> 
>> > lostandfound wrote:
>> > 
>> > 
>> > > from the terminal, I get a segmentation fault. Similar result
if I run it from my dock, cairo-dock. BUT, if I have a launcher
(e-Sword.desktop) containing that very same line, then I do not get the
segmentation fault.
>> > > 
>> > > 
>> > 
>> > Did you 'cd' into work directory when you run the program
in the terminal?
>> > 
>> > 
>> > 
>> Just as a follow up to my last message, e-Sword runs here on a Wine
>> 1.1.16 build based upon Mike Kronenberg's build environment.
>> 
>> James McKenzie
>
>
>Hi, I'm sorry it took so long to get back here. After more examination,
I found that this only occured when running within the gnome-terminal
environment. xterm worked fine, as did alt-F2 and calling my script. It does
not, at this point, seem a Wine bug due to that. I have installed Ubuntu Jaunty
and this problem does not occur there, so there's something unique about my
Intrepid 64bit install that caused the segmentation faults.
>
Thank you for the update on this issue.  

James McKenzie