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
** Package changed: simple-scan (Ubuntu) = hplip (Ubuntu)
** Changed in: hplip (Ubuntu)
Status: Invalid = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/930275
Title:
simple-scan crashed
Can someone at HP check the HPAIO scanner driver? Thanks.
** Also affects: hplip
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/930275
Title:
simple-scan
Here it is.
** Attachment added: Screenshot of XSane error message
https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/930275/+attachment/3040406/+files/xsane-error.png
** Changed in: simple-scan (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because
what error message does xsane display?
** Changed in: simple-scan (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/930275
Title:
simple-scan crashed with
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
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...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
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.
** Changed
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
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.
--
You received this bug notification because you are a member of Ubuntu
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
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
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/930275
Title:
simple-scan crashed with SIGSEGV in __strcasecmp_nonascii()
To manage notifications about this bug go
13 matches
Mail list logo
