Description of problem: Moved file currently opened by this app to another directory. Probably unretaled. Version-Release number of selected component: geeqie-1.2-0.1.20141130gita1afabd.fc22 Additional info: reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: geeqie --blank crash_function: image_read_ahead_done_cb executable: /usr/bin/geeqie global_pid: 2675 kernel: 4.0.3-300.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #0 image_read_ahead_done_cb at image.c:480 #1 _g_closure_invoke_va at gclosure.c:831 #4 image_loader_emit_done_cb at image-load.c:273 #9 gtk_main at gtkmain.c:1268
Created attachment 1027647 [details] File: backtrace
Created attachment 1027648 [details] File: cgroup
Created attachment 1027649 [details] File: core_backtrace
Created attachment 1027650 [details] File: dso_list
Created attachment 1027651 [details] File: environ
Created attachment 1027652 [details] File: limits
Created attachment 1027653 [details] File: maps
Created attachment 1027654 [details] File: mountinfo
Created attachment 1027655 [details] File: namespaces
Created attachment 1027656 [details] File: open_fds
Created attachment 1027657 [details] File: proc_pid_status
Created attachment 1027658 [details] File: var_log_messages
to reproduce: quickly keep pressing f (fullscreen) and page down (next file) keys. attached patch is a kind of workaround, I did not inspect further is this threading issue etc
Created attachment 1060482 [details] check for NULL
I've forwarded this to geeqie-devel@SF list. Often such NULL-ptr checks only fix symptoms, not the cause of it. What happens now if running into the error-condition while trying to load a valid file? I mean, it crashes for *valid* files because of some race-condition in rare cases (with your steps on how to reproduce it I've had to press F and PageDown dozens of times). Why would anything trigger this read-ahead callback with a NULL pointer? The source also does it upon error condition. So, the problem is elsewhere IMO.
Yes, it was fix for a symptom ("a kind of workaround"), I am letting other people spend time fixing the cause.
As a work-around, did you try "[ ] Preload next image" in general preferences?
I tried now. It seems to prevent the segfault from occurring.
geeqie-1.2-0.2.20150812git2b87884.fc22.1 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/geeqie-1.2-0.2.20150812git2b87884.fc22.1
Package geeqie-1.2-0.2.20150812git2b87884.fc22.1: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing geeqie-1.2-0.2.20150812git2b87884.fc22.1' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-13395/geeqie-1.2-0.2.20150812git2b87884.fc22.1 then log in and leave karma (feedback).
geeqie-1.2-0.6.20150812git2b87884.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-14376
geeqie-1.2-0.6.20150812git2b87884.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update geeqie'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-14376
geeqie-1.2-0.6.20150812git2b87884.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
geeqie-1.2-0.2.20150812git2b87884.fc22.1 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.