#1027753 geeqie crashes on ssh-forwared remote X

Package:
geeqie
Source:
geeqie
Description:
image viewer using GTK+
Submitter:
Lars Rohwedder
Date:
2023-01-26 22:39:02 UTC
Severity:
normal
Tags:
#1027753#5
Date:
2023-01-02 19:44:32 UTC
From:
To:
When I try to run "geeqie" via remote X (via "ssh -v -Y", that's why
I got the debug output from ssh, too) I got this error messages
to the console and geeqie seems to crash immediately:
----<snip>----
$ geeqie
debug1: client_input_channel_open: ctype x11 rchan 3 win 65536 max 16384
debug1: client_request_x11: request from ::1 46680
debug1: x11_connect_display: $DISPLAY is launchd
debug1: channel 1: new [x11]
debug1: confirm x11
debug1: client_input_channel_open: ctype x11 rchan 4 win 65536 max 16384
debug1: client_request_x11: request from ::1 46696
debug1: x11_connect_display: $DISPLAY is launchd
debug1: channel 2: new [x11]
debug1: confirm x11
debug1: channel 2: FORCE input drain
debug1: channel 2: free: x11, nchannels 3
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
debug1: channel 1: FORCE input drain
Segmentation fault
----<snap>----

Running geeqie in a local terminal it runs fine.

Geeqie in Debian 9 and 10 worked properly, locally and via ssh-tunneled remote X.
#1027753#10
Date:
2023-01-02 20:10:09 UTC
From:
To:
Thanks for your report - Could you please try to run geeqie with the command

LIBGL_ALWAYS_INDIRECT=1 geeqie

and report back here?

If that doesn't work, try to run geeqie with

geeqie --disable-clutter

- this is the geeqie bug https://github.com/BestImageViewer/geeqie/issues/829

Already fixed in later versions.

/Andreas Rönnquist
gusnan@debian.org
#1027753#15
Date:
2023-01-02 21:44:41 UTC
From:
To:
Am 02.01.23 um 21:10 schrieb Andreas Rönnquist:

Same result:

----<snip>----
$ LIBGL_ALWAYS_INDIRECT=1 geeqie
debug1: client_input_channel_open: ctype x11 rchan 3 win 65536 max 16384
debug1: client_request_x11: request from ::1 58284
debug1: x11_connect_display: $DISPLAY is launchd
debug1: channel 1: new [x11]
debug1: confirm x11
debug1: client_input_channel_open: ctype x11 rchan 4 win 65536 max 16384
debug1: client_request_x11: request from ::1 58294
debug1: x11_connect_display: $DISPLAY is launchd
debug1: channel 2: new [x11]
debug1: confirm x11
debug1: channel 2: FORCE input drain
debug1: channel 2: free: x11, nchannels 3
debug1: channel 1: FORCE input drain
Segmentation fault----<snap>----
 >

Whatever this option does, but geeqie works fine with this parameter. :-D

Thank you so far! :-)

Lars R.
#1027753#20
Date:
2023-01-17 19:36:43 UTC
From:
To:
Closing bug - I consider it solved by using a program argument that is
only needed in some circumstances. If you think otherwise, feel free to
re-open the bug.
#1027753#25
Date:
2023-01-18 07:47:27 UTC
From:
To:
The bug itself is _not_ fixed. The command-line option is just a
workaround, so geeqie is usable again, but it (or one of the used
libraries) still contains the bug.

So the severity might be lower and might be moved to the causing
library, but a segfault is still a thing that should be fixed. Don't you
think so?

Lars R.
#1027753#36
Date:
2023-01-26 22:36:31 UTC
From:
To:
As you might have seen I have posted a suggested fix to the release
team - which means it is now in the release teams hands, and up to them
if they allow the fix in Bullseye or not.

See
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1029142

for the details.