Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (6 frames)
#1 sane_dll_close at dll.c:1223
#2 sane_close at dll-s.c:78
#3 xsane_quit at ../../src/xsane.c:2388
#4 xsane_quit_handler at ../../src/xsane.c:2303
#6 poll at ../sysdeps/unix/syscall-template.S:81
#8 linux_udev_event_thread_main at os/linux_udev.c:175
Created attachment 871713 [details]
Created attachment 871714 [details]
Created attachment 871715 [details]
Created attachment 871716 [details]
Created attachment 871717 [details]
Created attachment 871718 [details]
Created attachment 871719 [details]
Created attachment 871720 [details]
Created attachment 871721 [details]
Created attachment 871722 [details]
Created attachment 871723 [details]
I think the problem is that xsane does signal handling the wrong way, and the crash is a result of the signal handler being called for a second time while the first invocation is not yet done. I have a patch that fixes this, it basically splits the signal handler in two parts, the "top half" just writes a character into a pipe when a signal arrives, this gets picked up by the "bottom half" which is services through the normal event loop (and therefore may call non-reentrant functions and so forth).
xsane-0.999-10.fc20 has been submitted as an update for Fedora 20.
xsane-0.999-10.fc19 has been submitted as an update for Fedora 19.
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing xsane-0.999-10.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
xsane-0.999-12.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
xsane-0.999-12.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.