Hi everyone, I brought this bug to Robert Ancell's attention. Good thing: he looked into it. Bad thing: he could not reproduce/debug the issue.
Robert believes this happens due to a corrupted adress space, caused by a bad scanner driver running in the same adress space as Simple Scan. I do not think Robert is right, and that maybe some size control information (image size or the like) returned by the scanner is incorrect, but the adress space itself is intact, because a) the pixel data is good enough to be displayed, so it should be good enough to be saved b) there are not random crashes, but it happens deterministically when saving a PDF So, to see who is right we need the following: - A description in your own words what exacly you do to recreate (not: "me too") and if it happens in 100% of the cases or just sometimes/most of the times/rarely/... - Make, Model and ID (as listed by lsusb) of the scanner - An apport report might be useful. Enable apport: https://wiki.ubuntu.com/Apport then make the problem happen and report the issue via apport. Include make, model and id in the description and CLEARLY STATE that is a reproduction of this bug, #664608 You might need to change the issue from "private" to "public" visibility so we can see it. - If someone who can recreate -- and has the necessary skills -- could poke around a bit with gdb that might help... Best Regards Michael -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/664608 Title: simple-scan crashes when saving to PDF To manage notifications about this bug go to: https://bugs.launchpad.net/simple-scan/+bug/664608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
