Summary: | libksane crashed while importing images via the scanner | ||
---|---|---|---|
Product: | [Frameworks and Libraries] libksane | Reporter: | maurocafiero |
Component: | general | Assignee: | Kåre Särs <kare.sars> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | caulier.gilles |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 3.0.0 | |
Sentry Crash Report: |
Description
maurocafiero
2011-03-12 11:55:32 UTC
Please write in English, otherwise no one will understand you. (In reply to comment #1) > Please write in English, otherwise no one will understand you. Sorry.the examples of bug descriptions are in italian in my installation, so I have supposed I can write in italian language. However,I was importing some photos by scanner when digikam crashed. Digikam crashed creating the preview of the second photo. At restart, digiKam has worked fine and I could continue the import without any crash thanks (In reply to comment #2) > (In reply to comment #1) > > Please write in English, otherwise no one will understand you. > > Sorry.the examples of bug descriptions are in italian in my installation, so I > have supposed I can write in italian language. No problem :-) Andi, it's a libksane issue... Gilles Caulier Hi, Strange if it was in the middle of a preview... the crash is in createOptInterface which is called by open device. Unfortunately the variables that could give me some hints of what is wrong are optimized out :( Is this crash repeatable? Gilles: I wonder about the multiple: "Backtrace stopped: previous frame identical to this frame (corrupt stack?)" Could that have something to do with it? Kåre If crash is due to a memory leak, valgrind can help a little bit. Else, trying to get another backtrace in same condition can give more info. Of course all must be compiled with full debug info. If crash is due to a shared lib like libsane, without debug info, no more details can be get by crash handler Gilles Caulier The duplication is probably the other way around ... but it should be fixed :) *** This bug has been marked as a duplicate of bug 314117 *** |