Description of problem: I scanned in a doc from a USB connected Canon MP-830, when I went to save - click on save button - the application crashed. Version-Release number of selected component: simple-scan-3.10.2-1.fc20 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/bin/simple-scan crash_function: gdk_property_change executable: /usr/bin/simple-scan kernel: 3.13.6-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gdk_property_change at gdkwindow.c:10631 #1 _gtk_selection_request at gtkselection.c:2453 #2 _gtk_marshal_BOOLEAN__BOXEDv at gtkmarshalers.c:130 #3 _g_closure_invoke_va at gclosure.c:840 #6 gtk_widget_event_internal at gtkwidget.c:7168 #7 gtk_widget_event at gtkwidget.c:6830 #8 gtk_main_do_event at gtkmain.c:1657 #14 gtk_dialog_run at gtkdialog.c:1075 #15 user_interface_choose_file_location at /home/bob/bzr/simple-scan/3.10/src/ui.vala:453 #16 user_interface_save_document at /home/bob/bzr/simple-scan/3.10/src/ui.vala:486
Created attachment 883639 [details] File: backtrace
Created attachment 883640 [details] File: cgroup
Created attachment 883641 [details] File: core_backtrace
Created attachment 883642 [details] File: dso_list
Created attachment 883643 [details] File: environ
Created attachment 883644 [details] File: exploitable
Created attachment 883645 [details] File: limits
Created attachment 883646 [details] File: maps
Created attachment 883647 [details] File: open_fds
Created attachment 883648 [details] File: proc_pid_status
Created attachment 883649 [details] File: var_log_messages
Can you reproduce this every time you try to save a scan? Did you select an image format in the save dialogue, or did you keep the default?
it crashed on me 2-3 times over the last 2 weeks, when i would scan and then click on the save button. i just did a yum update and am not sure if simple-scan was updated, but know after the bugzilla update and your request - i have now scanned in 3 items and saved them with no issues. thanks.
I have filed an upstream bug about the crash: https://bugs.launchpad.net/simple-scan/+bug/1303887 Could you please attach a debug log at Launchpad (or attach it here, and I can forward it), which you can get from running: simple-scan --debug > simple-scan.log 2>&1 in a terminal? Unfortunately, as the bug is not easy to reproduce, I would ask that you start Simple Scan with that command until you can trigger a crash. Simple Scan 3.10.2 was pushed to updates in Fedora 20 a few weeks ago: https://admin.fedoraproject.org/updates/FEDORA-2014-3721/simple-scan-3.10.2-1.fc20 The autosaving feature was rewritten, so this crash could potentially be related.
this appears to be fixed - i have tested and the saving feature is now workign for me in version: simple-scan-3.10.3-1.fc20.x86_64
Thanks for testing the latest version. The changes in 3.10.3 touched some file saving code, so maybe that fixed this bug as a side effect.