You have been subscribed to a public bug: Package: xsane Version: 0.997-2ubuntu3
I have reported the following bug to the XSane bug tracker at https://alioth.debian.org/tracker/index.php?func=detail&aid=313503 and on Debian BTS (http://bugs.debian.org/cgi- bin/bugreport.cgi?bug=655456#5) but it was suggested that I also report it here as the upstream project has not made a release in over a year. ---- When scanning to the viewing window then saving a file, changes to the file type cause the filename to fill with spurious characters, the system to report an 'Invalid file name' then 'A fatal error occured while running the scanning application'. Environment: XSane 0.997 on Ubuntu 10.10. Issue can be duplicated as follows: * Start XSane. * In main control window select Type as 'JPEG'. * In main control window select Target as 'Viewer'. * Carry out scan, setting other options if necessary. * The Viewer window should open. * Select File->Save image. * In the Type drop-down chooser, select 'PDF'. Observe that the Name textbox changes appropriately. * In the Type drop-down chooser select 'by ext'. Observer that the non-printable text is entered into the Name textbox. Of course, as a workaround it is possible to manually remove the non- printable text and enter a new filename in the Name textbox. ---- The problem was traced to xsane 0.997 source code, file: xsane-back- gtk.c, function: xsane_back_gtk_filetype2_callback. Code in this function will determine the new name for a file when a file extension is chosen from the Type drop-drown chooser. When 'by ext' is chosen no code is executed to populate the string pointed to by the filename, leaving uninitialised memory at this location. The uninitialised memory is later copied back to the UI. The attached patch against XSane 0.998 (http://www.xsane.org/download/xsane-0.998.tar.gz) resolves this issue. ** Affects: xsane (Ubuntu) Importance: Undecided Status: New ** Tags: patch -- Corrupt filename created when saving from XSane scan viewer https://bugs.launchpad.net/bugs/914711 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
