FS#44586 - [simple-scan] Application hangs on close
Attached to Project:
Community Packages
Opened by Yochai Gal (yochaigal) - Wednesday, 15 April 2015, 01:43 GMT
Last edited by Balló György (City-busz) - Wednesday, 24 January 2018, 19:42 GMT
Opened by Yochai Gal (yochaigal) - Wednesday, 15 April 2015, 01:43 GMT
Last edited by Balló György (City-busz) - Wednesday, 24 January 2018, 19:42 GMT
|
Details
Description:
Simple Scan works just fine, but when I try to quit (either from the menu or from the window-close "X" button) it freezes. I have to kill the PID or ctrl+c in terminal. Running in debug mode reads: [+0.04s] DEBUG: ui.vala:1878: Loading state from /home/yochai/.cache/simple-scan/state [+0.04s] DEBUG: ui.vala:1859: Restoring window to 813x1047 pixels [+0.04s] DEBUG: autosave-manager.vala:64: Loading autosave information [+0.04s] DEBUG: autosave-manager.vala:259: Waiting to autosave... [+0.10s] DEBUG: scanner.vala:1446: sane_init () -> SANE_STATUS_GOOD [+0.10s] DEBUG: scanner.vala:1452: SANE version 1.0.24 [+0.10s] DEBUG: scanner.vala:1513: Requesting redetection of scan devices [+0.10s] DEBUG: scanner.vala:802: Processing request [+0.14s] DEBUG: autosave-manager.vala:281: Autosaving book information [+0.21s] DEBUG: ui.vala:1969: Saving state to /home/yochai/.cache/simple-scan/state [+2.98s] DEBUG: autosave-manager.vala:195: Deleting autosave records [+2.98s] DEBUG: scanner.vala:1586: Stopping scan thread Additional info: * package version(s) * config and/or log files etc. Version 3.14.2 (community) XFCE with many GNOME packages Steps to reproduce: Launch simple-scan. Try and exit. |
This task depends upon
Closed by Balló György (City-busz)
Wednesday, 24 January 2018, 19:42 GMT
Reason for closing: Upstream
Wednesday, 24 January 2018, 19:42 GMT
Reason for closing: Upstream
Comment by
Balló György (City-busz) -
Wednesday, 24 January 2018, 05:32 GMT
Comment by
Balló György (City-busz) -
Wednesday, 24 January 2018, 19:41 GMT
Could you still reproduce it with the latest version (3.26.3-1)?
It's a very old report, and the upstream code changed a lot, so I
assumed that it's fixed. If not, then please report it to the
upstream developers.