Crash when Options --> View --> File List

Eclipse · Post by **Eclipse** » Tue Oct 17, 2006 1:46 pm

As the subject of this thread suggest I'm having this crash every time I select that option.
I'm running SUSE Linux, XnView v.1.70

The following is the output from shell ( Error detected appears when I hit File List):

Code: Select all

 $>xnview
** XnView v1.70 Copyright 1991-2005 Pierre-E Gougelet (Sep  6 2005/13:16:40) **
        Version for Linux x86/Motif (All rights reserved)
** This is freeware software (for non commercial use)

     Type xnview -help, for more information
Warning:
    Name: textDir
    Class: XmTextField
    Character '\57' not supported in font.  Discarded.

Warning:
    Name: textDir
    Class: XmTextField
    Character '\150' not supported in font.  Discarded.

Warning:
    Name: textDir
    Class: XmTextField
    Character '\157' not supported in font.  Discarded.

Warning:
    Name: textDir
    Class: XmTextField
    Character '\155' not supported in font.  Discarded.

Warning:
    Name: textDir
    Class: XmTextField
    Character '\145' not supported in font.  Discarded.

Warning:
    Name: textDir
    Class: XmTextField
    Character '\57' not supported in font.  Discarded.

Warning:
    Name: textDir
    Class: XmTextField
    Character '\160' not supported in font.  Discarded.

Warning:
    Name: textDir
    Class: XmTextField
    Character '\141' not supported in font.  Discarded.

Warning:
    Name: textDir
    Class: XmTextField
    Character '\160' not supported in font.  Discarded.

Warning:
    Name: textDir
    Class: XmTextField
    Character '\160' not supported in font.  Discarded.

Warning:
    Name: textDir
    Class: XmTextField
    Character '\141' not supported in font.  Discarded.

Warning:
    Name: textDir
    Class: XmTextField
    Character '\147' not supported in font.  Discarded.

Warning:
    Name: textDir
    Class: XmTextField
    Character '\145' not supported in font.  Discarded.

Warning:
    Name: textDir
    Class: XmTextField
    Character '\156' not supported in font.  Discarded.

Warning:
    Name: textDir
    Class: XmTextField
    Character '\157' not supported in font.  Discarded.

Warning:
    Name: textDir
    Class: XmTextField
    Character '\57' not supported in font.  Discarded.

Warning:
    Name: textDir
    Class: XmTextField
    Character '\111' not supported in font.  Discarded.

Warning:
    Name: textDir
    Class: XmTextField
    Character '\115' not supported in font.  Discarded.

Warning:
    Name: textDir
    Class: XmTextField
    Character '\115' not supported in font.  Discarded.

Warning:
    Name: textDir
    Class: XmTextField
    Character '\101' not supported in font.  Discarded.

Warning:
    Name: textDir
    Class: XmTextField
    Character '\107' not supported in font.  Discarded.

Warning:
    Name: textDir
    Class: XmTextField
    Character '\111' not supported in font.  Discarded.

Warning:
    Name: textDir
    Class: XmTextField
    Character '\116' not supported in font.  Discarded.

Warning:
    Name: textDir
    Class: XmTextField
    Character '\111' not supported in font.  Discarded.

Warning:
    Name: textDir
    Class: XmTextField
    Character '\57' not supported in font.  Discarded.

****** Error detected ******

BTW this software Rocks! I just discovered it and I think it's going to be my favourite for a long while...

WDef · Post by **WDef** » Sun Oct 29, 2006 1:19 pm

Unfortunately we're having this problem using the RedHat static xnview binary on Damnsmalllinux, too.

strace -fivp says there is a segfault.

With the -c option there appears to eb a problem reading/accessing something.

This internet cafe's pc is infected with malware preventing pasting into firefox, otherwise I'd paste the output.

WDef · Post by **WDef** » Sun Oct 29, 2006 1:23 pm

My apologies for the multiple posts! - it didn't appear to be posting at all - said "error - timed out - debug mode" - so I kept trying to post. When I revisited the site ....

WDef · Post by **WDef** » Mon Oct 30, 2006 9:32 am

Here's what gdb says:

Code: Select all

<snip>
(no debugging symbols found)...
Program received signal SIGSEGV, Segmentation fault.
0x4002c160 in XtWidgetToApplicationContext () from /usr/X11R6/lib/libXt.so.6
(gdb)

Post by **xnview** » Wed Nov 01, 2006 2:36 pm

WDef wrote:Unfortunately we're having this problem using the RedHat static xnview binary on Damnsmalllinux, too.

Ok, i'll check on damnsmalllinux. And which version of Suse do you have?

WDef · Post by **WDef** » Thu Nov 02, 2006 11:47 am

Thanks Pierre! Great the way you get on the case so quickly.

I'm just wildly (probably foolishly!) guessing but is it possible that:

1. Function XtWidgetToApplicationContext () is been handed an incorrect argument for some reason? Or:

2. There's a problem with Motif and libXt. Googling I found examples of similar(?) problems in other applications where motif had been statically compiled in - led to some kind of clash between libXt versions I think.

Eclipse · Post by **Eclipse** » Wed Dec 13, 2006 11:44 am

xnview wrote:
WDef wrote:Unfortunately we're having this problem using the RedHat static xnview binary on Damnsmalllinux, too.
Ok, i'll check on damnsmalllinux. And which version of Suse do you have?

The SUSE I used was a 9.1 pro

WDef · Post by **WDef** » Sun Jan 14, 2007 2:22 pm

Any news on this?

duke74 · Post by **duke74** » Wed Oct 10, 2007 1:30 pm

hi also have problem with xnview 1.70 static rh6 vers. on this issue
possible workaround to manually edit ~/.xnviewrc
for unavailable options and stay clear of view /file list
my test system Mandrake 10.0 community

however, after instaling Openmotif 2.2.2 binary from
http://www.motifzone.net/index.php
find out that XnView-openmotif2.2.i386.rpm
(that is version 1.68 ) is working on this issue
dont know about other issues

is it possible to add XnView-openmotif for v1.70?
(at least temporarily,awaiting impatiently for new 1.90

)