Samsung SCX-4521F finds scanner, but crash on launch glibc detected *** scanimage: double free or corruption

[Scott]

Sane finds the scanner, but crashes even as root "glibc detected *** scanimage: double free or corruption" when attempting to open USB scanner on multifunction (print/scan/copy/fax) Samsung SCX-4521F.

Using Intrepid AMD64.
Sane 1.0.14-6

Printer works fine after installing package from Samsung, trying to open scanner with Samsung software also results in crash.

sudo sane-find-scanner

  # sane-find-scanner will now attempt to detect your scanner. If the
  # result is different from what you expected, first make sure your
  # scanner is powered up and properly connected to your computer.

  # No SCSI scanners found. If you expected something different, make sure that
  # you have loaded a kernel SCSI driver for your SCSI adapter.

found USB scanner (vendor=0x04e8 [Samsung], product=0x3419 [SCX-4x21 Series]) at libusb:001:004
  # Your USB scanner was (probably) detected. It may or may not be supported by
  # SANE. Try scanimage -L and read the backend's manpage.

  # Not checking for parallel port scanners.

  # Most Scanners connected to the parallel port or other proprietary ports
  # can't be detected by this program.
scott@Phoenix:~$ sudo scanimage -L
*** glibc detected *** scanimage: double free or corruption (!prev): 0x00000000023b7b70 ***

[Scott (halo-prints)]

Found after reinstalling using Samsung's software, I paid more attention to group policies during setup. Scanner works ok

[Rolf Leggewie (r0lf)]

Scott, thank you for your report and please apologize the long delay in response. Do you still experience this in precise or a later release?

[Rolf Leggewie (r0lf)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!