Thank you very much. From my point of view this sounds as if there is a small but crucial difference between:
A: - close simple scan - start simple scan B: - click "new document" in simple scan these should be functionally equivalent (with some potential optimization in approach B). in reality they are not, and that is the problem. where could it fail: - internal state of the scanner could be invalid after running the commands from approach B - state of simple scan could be invalid after running the commands from approach B, this could especially affect buffers (freed them and kept dangling pointers, ...) I will ask Robert to double check this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/843361 Title: simple-scan crashed with SIGSEGV in g_closure_invoke() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/843361/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
