simple-scan crashed with SIGSEGV in __strcasecmp_nonascii()

StacktraceTop:
 __strcasecmp_nonascii (s1=0x8e0c586 "/usb/Photosmart_C4200_series?serial=MY798KP16D04VP", s2=0x0) at ../string/strcasecmp.c:65
 hpaioFindScanner (name=0x8e0c586 "/usb/Photosmart_C4200_series?serial=MY798KP16D04VP") at scan/sane/hpaio.c:320
 sane_hpaio_open (devicename=0x8e0c586 "/usb/Photosmart_C4200_series?serial=MY798KP16D04VP", pHandle=0xb067c0a4) at scan/sane/hpaio.c:1687
 sane_dll_open (full_name=<optimized out>, meta_handle=0xb067c198) at dll.c:1198
 sane_open (name=0x8e0c580 "hpaio:/usb/Photosmart_C4200_series?serial=MY798KP16D04VP", h=0xb067c198) at dll-s.c:23

Hi there,

thank you for filing this bug and showing your interest in Simple Scan!

This seems to be a Hardware Issue, i.e. Simple Scan does not support
your scanner perfectly -- or possibly not at all.

Unfortunately such problems happen more often then they should, and while it might indeed be a problem with Simple Scan, in our experience, most of the time it is not.
This is why we prepared a check-list at [1] that will let you find out whether or not it really is a problem with Simple Scan and what your options are in either case.

Please read that list and tell us how you decided to proceed. I will set
this bug to "Incomplete", so a friendly robot will expire this bug in 60
days if you do not respond. However, we would really prefer to hear back
from you!

Best Regards
Michael

[1] https://help.ubuntu.com/community/SimpleScanHardwareIssues

My scanner works fine with both simple-scan and xsane, and there were almost no issues for 2 years of using it with both these apps.

As far as I can remember this happened when I closed the properties dialog. I can't reproduce it now, and I think this bug is not applicable to xsane.

UpgradeStatus: Upgraded to precise on 2012-02-10 (0 days ago)
is this correct?

Can this issue be reproduced every time?

If I look at this:
StacktraceTop:
 __strcasecmp_nonascii (s1=0x8e0c586 "/usb/Photosmart_C4200_series?serial=MY798KP16D04VP", s2=0x0) at ../string/strcasecmp.c:65
 sane_hpaio_open () from /usr/lib/sane/libsane-hpaio.so.1
 sane_dll_open () from /usr/lib/i386-linux-gnu/libsane.so.1
 sane_open () from /usr/lib/i386-linux-gnu/libsane.so.1
 ?? ()

it seems to be related to some hardware-related operation.
Unfortunately we currently do not have the manpower to look into sporadic hardware-related issues.

Yes, that's correct.

I tried to reproduce it, and there was a crash, but it seems to be different from this one, and I reported it as bug 930914.
I will let you know when I'll manage to reproduce exactly the same issue.

The scanner driver might be corrupting the adress space, leading to arbitrary crashes, so reporting more and more issues will probably not help. More interesting is the system behind it:

- can you try do do the same steps, say ten times. if it crashes all the time with the same message: thats noteworthy. if it crashes all the time with different messages: thats noteworthy. if it crashes sometimes: thats noteworthy but probably the least helpful.

- can you install an old version of hplip and try again?

- can you install xsane and try that?

Thanks & Best Regards!

Sorry for the delay. Here are my testing results:

- I keep getting crashes when I play with unplugging cable — these crashes include bug 930914, bug 902830 (this is one that I can reproduce for sure, steps are given) and some other (stack traces always include sane_hpaio_close());
- I never got this particular crash again;
- These crashes (or at least bug 902830) occur with hplip from oneiric-updates but installed on precise, currently I can't test it on a pure oneiric system;
- XSane never crashed in my tests, however it displays an error message when I try to follow the steps from bug 930914.

Sorry, please replace s/bug 902830/bug 934194/g in my previous message. Bug 902830 is one that I reported two months ago, it's similar to the newly reported one and may be also helpful for you...

what error message does xsane display?

Here it is.

this is most certainly an issue in the backend and not related to anything simple-scan does.

as noted in https://help.ubuntu.com/community/SimpleScanHardwareIssues the simple-scan team does not have ressources to debug issues in the backends. scanning must mork with scanimage and/or xsane before we can continue. feel free to raise this issue with the hplip and/or sane-backends developers. you can either file this bug against those packages or contact them via other means, e.g. mailing lists.

i will close the ticket for simple-scan as we cannot do anything here...

Can someone at HP check the HPAIO scanner driver? Thanks.