Version-Release number of selected component: simple-scan-3.8.0-1.fc19 Additional info: reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: simple-scan crash_function: sanei_genesys_generate_gamma_buffer executable: /usr/bin/simple-scan kernel: 3.12.6-200.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1001 var_log_messages: Jan 10 10:49:29 kupa153 abrt-hook-ccpp[6130]: Saved core dump of pid 6039 (/usr/bin/simple-scan) to /var/tmp/abrt/ccpp-2014-01-10-10:49:26-6039 (80424960 bytes) Truncated backtrace: Thread no. 1 (7 frames) #0 sanei_genesys_generate_gamma_buffer at genesys_low.c:1235 #1 gl646_send_gamma_table at genesys_gl646.c:3642 #2 sane_genesys_start at genesys.c:4032 #3 scanner_do_start at scanner.c:7040 #4 scanner_scan_thread at scanner.c:8056 #5 _scanner_scan_thread_gthread_func at scanner.c:8080 #6 g_thread_proxy at gthread.c:798
Created attachment 894194 [details] File: backtrace
Created attachment 894195 [details] File: cgroup
Created attachment 894196 [details] File: core_backtrace
Created attachment 894197 [details] File: dso_list
Created attachment 894198 [details] File: environ
Created attachment 894199 [details] File: exploitable
Created attachment 894200 [details] File: limits
Created attachment 894201 [details] File: maps
Created attachment 894202 [details] File: open_fds
Created attachment 894203 [details] File: proc_pid_status
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?
*** Bug 1123563 has been marked as a duplicate of this bug. ***
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days