Description of problem: Just try to scan a document Version-Release number of selected component: simple-scan-3.10.2-1.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/simple-scan crash_function: sanei_constrain_value executable: /usr/bin/simple-scan kernel: 3.14.2-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (7 frames) #0 sanei_constrain_value at sanei_constrain_value.c:230 #1 sane_hp3500_control_option at hp3500.c:561 #2 scanner_set_option_to_max at /home/bob/bzr/simple-scan/3.10/src/scanner.vala:529 #3 scanner_do_get_option at /home/bob/bzr/simple-scan/3.10/src/scanner.vala:1078 #4 scanner_scan_thread at /home/bob/bzr/simple-scan/3.10/src/scanner.vala:1475 #5 _scanner_scan_thread_gthread_func at scanner.c:12474 #6 g_thread_proxy at gthread.c:798
Created attachment 894120 [details] File: backtrace
Created attachment 894121 [details] File: cgroup
Created attachment 894122 [details] File: core_backtrace
Created attachment 894123 [details] File: dso_list
Created attachment 894124 [details] File: environ
Created attachment 894125 [details] File: exploitable
Created attachment 894126 [details] File: limits
Created attachment 894127 [details] File: maps
Created attachment 894128 [details] File: open_fds
Created attachment 894129 [details] File: proc_pid_status
Created attachment 894130 [details] File: var_log_messages
This sort of crash generally indicates a problem with the SANE backend. Is the crash reproducible? If so, can you try scanning with XSane and report if that works or crashes?
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
As this Bug was reported on EOL nothing else is required