infinite loop when scanning at 2400 dpi

[Saivann Carignan]

When trying to scan with my HP Photosmart C6180 at 2400 dpi, simple-scan 0.99 don't show scan preview progress and it enters in a infinite loop in which the scanner continuously (re)scan the same little area while simple-scan keeps echoing the same 5 debug outputs in terminal, many time per second :

(simple-scan:29582): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `GDK_IS_PIXBUF (pixbuf)' failed

(simple-scan:29582): GdkPixbuf-CRITICAL **: gdk_pixbuf_new: assertion `width > 0' failed

(simple-scan:29582): GdkPixbuf-CRITICAL **: gdk_pixbuf_fill: assertion `GDK_IS_PIXBUF (pixbuf)' failed

(simple-scan:29582): GdkPixbuf-CRITICAL **: gdk_pixbuf_copy_area: assertion `src_pixbuf != NULL' failed

(simple-scan:29582): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

I'm attaching --debug log, with 7Mb of repeating debug lines manually removed by myself.

Scanning at 2400 dpi with xsane works correctly with the same scanner.

[Saivann Carignan (oxmosys)]

This is weird, simple scan does not hit this bug at 2400dpi with my Brother MFC 420CN.

In short :

HP Photosmart C6180, 2400dpi, xsane : works
Brother MFC-420CN, 2400dpi, simple-scan : works
HP Photosmart C6180, 2400dpi, simple-scan : fails

[Michael Nagel (nailor)]

Is this still an issue?

[Saivann Carignan (oxmosys)]

simple-scan 3.2.1-0ubuntu1~oneiric1 now crashes right before it starts to scan when trying to scan at 2400dpi.

In the case of xsane, it succesfully scans the picture and produce a valid file. However, the usual progress bar shows nothing from the beginning until the end.

[Michael Nagel (nailor)]

Lower resolutions work with simple-scan, right?
Could you enable apport and report the crash? Please refer to this bug in the newly created one.

Thanks!

[Saivann Carignan (oxmosys)]

Absolutely, simple-scan works with lower resolutions.

Well I enabled apport in /etc/default/apport and restarted it (/etc/init.d/apport restart), however, it does not launch when simple-scan crashes with core dumped. Any idea? I can launch ubuntu-bugs simple-scan but I'm not certain you will get all you need.

Thanks!

[Michael Nagel (nailor)]

I think it will probably lack the actual core dump + possible retrace.
Could you ask on IRC #ubuntu or #ubuntu-bugs if someone knows why it does not get triggered for you?

Thanks!

[Saivann Carignan (oxmosys)]

I found why it does not work, the crash log already existed in /var/crash, so apport did nothing until I emptied that folder.

I've now created bug #931689 with all you asked. Thanks!

[Michael Nagel (nailor)]

are you sure about that number and if yes is it public?

[Saivann Carignan (oxmosys)]

It is indeed private, I though you had access to these. I just subscribed you. I didn't review the files yet to verify if they could contain private informations. Will do.

[Saivann Carignan (oxmosys)]

If you don't need to CoreDump.gz file, you can remove it and make the bug public. Otherwise, https://wiki.ubuntu.com/Bugs/HowToTriage says it should stay private.

[Michael Nagel (nailor)]

lets focus on the other bug