Description of problem: testing a gt68xx scanner Version-Release number of selected component: xsane-0.998-12.fc17 Additional info: backtrace_rating: 4 cmdline: xsane crash_function: preview_display_valid executable: /usr/bin/xsane kernel: 3.8.11-100.fc17.i686.PAE uid: 1000 ureports_counter: 1 xsession_errors: Truncated backtrace: Thread no. 1 (10 frames) #0 preview_display_valid at ../../src/xsane-preview.c:7561 #1 xsane_update_param at ../../src/xsane-front-gtk.c:1731 #2 preview_establish_selection at ../../src/xsane-preview.c:755 #3 preview_update_surface at ../../src/xsane-preview.c:4883 #4 preview_scan_done at ../../src/xsane-preview.c:1871 #5 preview_destroy at ../../src/xsane-preview.c:5227 #6 xsane_quit at ../../src/xsane.c:2370 #7 xsane_scan_win_delete at ../../src/xsane.c:2519 #8 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86 #13 gtk_widget_event_internal at gtkwidget.c:5017
Created attachment 748768 [details] File: backtrace
Created attachment 748769 [details] File: cgroup
Created attachment 748770 [details] File: core_backtrace
Created attachment 748771 [details] File: dso_list
Created attachment 748772 [details] File: environ
Created attachment 748773 [details] File: limits
Created attachment 748774 [details] File: maps
Created attachment 748775 [details] File: open_fds
Created attachment 748780 [details] File: proc_pid_status
Created attachment 748784 [details] File: smolt_data
Created attachment 748786 [details] File: var_log_messages
It looks as if while trying to destroy the preview object when quitting xsane, it tries to use it despite it being set to NULL already. Can you reproduce this issue reliably?
Just to add to how it happened: - minimized preview window after clicking "acquire preview"; - allowed some time to acquire, but not enough to actually acquire the whole preview; - restored preview window, it was all blank (no buttons, no text, no image); - because I could not restore the preview window properly I've closed it; - reopened a new preview window, but it was still blank; - closed xsane, it crashed. I no longer have the scanner attached, but it happened also on Fedora 16, and on another PC with Fedora 17. Scanner was the same.
xsane-0.998-21.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/xsane-0.998-21.fc18
xsane-0.998-21.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/xsane-0.998-21.fc17
xsane-0.998-21.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/xsane-0.998-21.fc19
Package xsane-0.998-21.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing xsane-0.998-21.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-8453/xsane-0.998-21.fc19 then log in and leave karma (feedback).
xsane-0.998-21.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
xsane-0.998-21.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
xsane-0.998-21.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.