| Summary: | Skanlite crashes (segfaults) after start [even when no Scanner is connected, but also with connected scanner] | ||
|---|---|---|---|
| Product: | [Applications] Skanlite | Reporter: | obkdebugs2026 |
| Component: | general | Assignee: | Kåre Särs <kare.sars> |
| Status: | REPORTED --- | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version First Reported In: | 25.12.2 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | backtrace.txt original (no linenumbers added) | ||
|
Description
obkdebugs2026
2026-02-08 22:28:53 UTC
CORRECTION: skanlite crashes always, even with connected scanner. The information, that skanlite works with connected scanner was from remembering some days ago, that it worked. (I started skanlite for some other reason, not to scan something, when I encountered the crash.) So the "it works with scanner" was from before 2026-02-06, when the package 25.12.2-1 was installed. This implies that the bug is new, coming in with the new package. At the time, when skanlite was working, but showed the Webcam instead of the Scanner as Default, the order in the Menue was: 1.: Webcam 2.: Scanner Or counted from 0: 0: Webcam 1: Scanner I had to select the scanner by hand via the menue. Without looking at the Code, I would guess, the crash might be an off-by-one-problem. Shift the two entries in the list, so that only the Scanner appears in the list (index >= 0). Index of Webcam is then <0, more explicitly -1 in this case. Then setting the Webcam as Default without checking on Index >=0 would use -1 as an array index. Just a guess, but maybe a hint. Thanks for the report! From the crash log I can see that Skanlite is trying to open "genesys:libusb:003:010" I'm suspecting that the "try to open the previous scanner" somehow messes things up. Can you attach your .config/skanliterc here and then try to remove the file and restart? (In reply to Kåre Särs from comment #3) > Thanks for the report! > > From the crash log I can see that Skanlite is trying to open > "genesys:libusb:003:010" > > I'm suspecting that the "try to open the previous scanner" somehow messes > things up. Can you attach your .config/skanliterc here and then try to > remove the file and restart? I guess the skanliterc file has been changed in the meantime, when trying again to start skanlite. Also I don't see any device settings there... I see no attach-button, so I paste it here: ------ [General] DisableAutoSelection=false PreviewDPI=100 SetPreviewDPI=false [Image Saving] ImgFormat=image/png ImgQuality=90 Location=file:///home/USERDIR/datastore/scans NamePrefix=Bild- NumberStartsFrom=29 SaveMode=0 SetQuality=false ShowBeforeSave=true ------ After removing the rc-file and starting skanlite again, it crashes again (as I expected). When I use the -d Option and set it to the string that I get from lsusb for the Scanner, then skanlite opens the selection window for devices, but does not select the scanner. The webcam (first position) is selected by default. If I use this device to scan, I get a crash. Trying again with -d and the same string for the scanner, but this time selecting the Scanner from the Menue, then the Scanning-munue opens and I can scan from the Scanner. And if I afterwards press "Reselect scanner device" and select the Webcam, I can use it too. So with this trick I can scan from Scanner as well as Webcam, but have some strange workflow to work around the bug. ------- wtf ------- After I tried this some times, I could start skanlite without command line arguments and the Scan-Menue starts directly - without the extra menue that asks for Device selection. A new .config/skanliterc has been created after I configured a little bid, and it looks like this: ------ [Image Saving] NumberStartsFrom=1 ------ After removing it, crash again. Copying the rc-settings back to the rc-file, still crashing, until using -d switch again. Even any non-empty string seems to avoid the crash at that point. And after this has been used crashfree going directly into the Scan-Menue. Removed the rc-file again, but this time no crash. So, the crash is not always reproducible! |