Bug 1220031

Summary: geeqie crashes out of the box
Product: [openSUSE] openSUSE Tumbleweed Reporter: Michael Behrens <micha.bee>
Component: X11 ApplicationsAssignee: Michael Vetter <mvetter>
Status: RESOLVED FIXED QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: mvetter, tux93
Version: Current   
Target Milestone: ---   
Hardware: x86-64   
OS: openSUSE Tumbleweed   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Michael Behrens 2024-02-17 21:24:47 UTC
Fresh installation from openSUSE-Tumbleweed-DVD-x86_64-Snapshot20240214-Media.iso , 'zypper dup' just a few minutes ago.

geeqie, when started for the first time, crashes, when I try to configure it.

 * no ~/.config/geeqie directory initially 
 * no images to load initially 
 * crashes regardless of DE (Mate, Plasma) or WM (ivewm, fvwm2), or X11
   redirection over ssh

To crash:

 * start geeqie from menu or from xterm
 * right click on thumbnail pane, click 'Images as Icons'
 - or - 
 * right click in directory listing pane, click 'View as Tree'
 - or - 
 * right click in image pane, click 'Hide file list'

 Maybe crashes occur on other right clicks too, but not all. For example
 deselecting 'Show Filename Text' in thumbnail pane is working without crashing.

Output in xterm
---------------------------------------------------------
$ geeqie 
Geeqie fatal error
Signal: Invalid memory reference
Code: Invalid permissions
Address: 0x0
geeqie(+0xdcb39)[0x55ca62d1ab39]
/lib64/libc.so.6(+0x41240)[0x7fca1b841240]
/lib64/libgtk-3.so.0(gtk_widget_get_parent+0x19)[0x7fca1d740509]
/lib64/libgtk-3.so.0(+0x1f8453)[0x7fca1d5f8453]
/lib64/libgtk-3.so.0(gtk_main_do_event+0x986)[0x7fca1d5f8f66]
/lib64/libgdk-3.so.0(+0x39267)[0x7fca1dc54267]
/lib64/libgdk-3.so.0(+0x8e252)[0x7fca1dca9252]
/lib64/libglib-2.0.so.0(+0x5bf30)[0x7fca1cf22f30]
/lib64/libglib-2.0.so.0(+0x5db58)[0x7fca1cf24b58]
/lib64/libglib-2.0.so.0(g_main_loop_run+0x6f)[0x7fca1cf2542f]
/lib64/libgtk-3.so.0(gtk_main+0x9d)[0x7fca1d5f6a9d]
geeqie(+0x75f95)[0x55ca62cb3f95]
/lib64/libc.so.6(+0x2a1f0)[0x7fca1b82a1f0]
/lib64/libc.so.6(__libc_start_main+0x8b)[0x7fca1b82a2b9]
geeqie(+0x77d55)[0x55ca62cb5d55]
---------------------------------------------------------

To "View images as Icons", the hotkey Ctrl-I is working. For testing, I then use a directory with ~2000 JPG images. As long as thumbnails are shown with file names, geeqie seems to work now. But then

 * right click on thumbnail pane, deselect 'Show Filename Text', filenames
   disappear
 * clicking on thumbnails then crashes geeqie after some (1..3) successful 
   clicks
 - or -
 * single click on a thumbnail, the move the mouse pointer to image pane, 
   geeqie crashes.


Output on xterm:
---------------------------------------------------------
Geeqie fatal error
Signal: Invalid memory reference
Code: Invalid permissions
Address: 0x0
geeqie(+0xdcb39)[0x5576de0efb39]
/lib64/libc.so.6(+0x41240)[0x7f23d7c41240]
/lib64/libgtk-3.so.0(+0x3464d2)[0x7f23d99464d2]
/lib64/libgtk-3.so.0(+0x356b9a)[0x7f23d9956b9a]
/lib64/libgobject-2.0.so.0(g_object_unref+0x164)[0x7f23d9294894]
geeqie(+0x13974a)[0x5576de14c74a]
/lib64/libgtk-3.so.0(+0xa2068)[0x7f23d96a2068]
/lib64/libgobject-2.0.so.0(g_closure_invoke+0x138)[0x7f23d928f468]
/lib64/libgobject-2.0.so.0(+0x2a61c)[0x7f23d92a261c]
/lib64/libgobject-2.0.so.0(+0x2b86a)[0x7f23d92a386a]
/lib64/libgobject-2.0.so.0(g_signal_emit_valist+0x32)[0x7f23d92a9ce2]
/lib64/libgobject-2.0.so.0(g_signal_emit+0x8f)[0x7f23d92a9d8f]
/lib64/libgtk-3.so.0(+0x34fca4)[0x7f23d994fca4]
/lib64/libgtk-3.so.0(+0x1f848e)[0x7f23d97f848e]
/lib64/libgtk-3.so.0(gtk_main_do_event+0x986)[0x7f23d97f8f66]
/lib64/libgdk-3.so.0(+0x39267)[0x7f23d9ebb267]
/lib64/libgdk-3.so.0(+0x8e252)[0x7f23d9f10252]
/lib64/libglib-2.0.so.0(+0x5bf30)[0x7f23d918bf30]
/lib64/libglib-2.0.so.0(+0x5db58)[0x7f23d918db58]
/lib64/libglib-2.0.so.0(g_main_loop_run+0x6f)[0x7f23d918e42f]
/lib64/libgtk-3.so.0(gtk_main+0x9d)[0x7f23d97f6a9d]
geeqie(+0x75f95)[0x5576de088f95]
/lib64/libc.so.6(+0x2a1f0)[0x7f23d7c2a1f0]
/lib64/libc.so.6(__libc_start_main+0x8b)[0x7f23d7c2a2b9]
geeqie(+0x77d55)[0x5576de08ad55]
---------------------------------------------------------

$ rpm -qi geeqie
Name        : geeqie
Version     : 2.2
Release     : 1.2
Architecture: x86_64
Install Date: Fr 16 Feb 2024 11:59:45 CET
Group       : Productivity/Graphics/Viewers
Size        : 3923732
License     : GPL-2.0-or-later
Signature   : RSA/SHA512, Sa 03 Feb 2024 01:13:42 CET, Key ID 35a2f86e29b700a4
Source RPM  : geeqie-2.2-1.2.src.rpm
Build Date  : Sa 03 Feb 2024 01:12:58 CET
Build Host  : i04-ch4d
Packager    : https://bugs.opensuse.org
Vendor      : openSUSE
URL         : http://www.geeqie.org
Summary     : Lightweight Gtk+ based image viewer
Description :
Geeqie is a lightweight image viewer for Linux, BSDs and compatibles.
Distribution: openSUSE Tumbleweed
Comment 1 Michael Behrens 2024-02-19 10:06:45 UTC
There are two new bug reports about similar crashes on the github page of geeqie:

https://github.com/BestImageViewer/geeqie/issues/1248
https://github.com/BestImageViewer/geeqie/issues/1250
Comment 2 Michael Behrens 2024-03-01 10:42:23 UTC
Meanwhiel this bug report on the geeqie github site

  https://github.com/BestImageViewer/geeqie/issues/1248

has been closed as 'completed'.
Comment 3 Michael Vetter 2024-03-01 11:03:35 UTC
I created SR#1153894 which backports two fixes for:
* https://github.com/BestImageViewer/geeqie/issues/1242
* https://github.com/BestImageViewer/geeqie/issues/1248

https://github.com/BestImageViewer/geeqie/issues/1250 doesn't have a fix from upstream yet.

My package is available at:
https://build.opensuse.org/package/show/home:jubalh:branches:GNOME:Apps/geeqie

You can install it from there and test (and give feedback) until the submit request is accepted.

If this solves your bug I would suggest to create a new report for https://github.com/BestImageViewer/geeqie/issues/1250 later in case this is critical for you.
Comment 4 Michael Behrens 2024-03-01 15:03:31 UTC
(In reply to Michael Vetter from comment #3)
> ...
> My package is available at:
> https://build.opensuse.org/package/show/home:jubalh:branches:GNOME:Apps/
> geeqie
> ...

Hello Michael,

did that link disappear? My browser gets always redirected to the bugzilla main page (https://bugzilla.opensuse.org/) with error message 'Project not found: home:jubalh:branches:GNOME:Apps' when clicking on it, regardless whether I'm logged in or not.

Kind Regards
Michael
Comment 5 Michael Vetter 2024-03-01 15:05:12 UTC
(In reply to Michael Behrens from comment #4)
> (In reply to Michael Vetter from comment #3)
> > ...
> > My package is available at:
> > https://build.opensuse.org/package/show/home:jubalh:branches:GNOME:Apps/
> > geeqie
> > ...
> 
> Hello Michael,
> 
> did that link disappear? My browser gets always redirected to the bugzilla
> main page (https://bugzilla.opensuse.org/) with error message 'Project not
> found: home:jubalh:branches:GNOME:Apps' when clicking on it, regardless
> whether I'm logged in or not.

Sorry I should have marked the project to stay :)
The submission has already been accepted to the devel project. It is now in https://build.opensuse.org/package/show/GNOME:Apps/geeqie and will in a few days be available in Tumbleweed. You can also wait until that time and then give feedback.
Comment 6 Michael Behrens 2024-03-06 08:59:57 UTC
(In reply to Michael Vetter from comment #5)

Hello Michael,

I just tried the actual tumbleweed update with geeqie-2.2-2.1.x86_64 built on Sa 02 Mär 2024 01:16:21 CET.

The crashes described don't happen anymore, thank you very much! From my point of view this bugreport is resolved.

There are some other quirks but I'm not sure whether they depend on my configuration. Once I find out, what would be better: to report them here in bugzilla or to report them to the geeqie github? 

Kind Regards
Michael
Comment 7 Michael Vetter 2024-03-06 09:49:23 UTC
(In reply to Michael Behrens from comment #6)
> There are some other quirks but I'm not sure whether they depend on my
> configuration. Once I find out, what would be better: to report them here in
> bugzilla or to report them to the geeqie github? 

It would be better to report them on upstream GitHub. Then the developers of geeqie directly see what's wrong with their software, can fix it and create a new release. Or we can backport some of their fixes in case its urgent bugs.