https://bugs.kde.org/show_bug.cgi?id=513047
Bug ID: 513047
Summary: Skanpage doesn't remember scanner options due to
unstable naming
Classification: Applications
Product: Skanpage
Version First 25.08.3
Reported In:
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
SUMMARY
Skanpage forgets scanner configuration upon power cycling a scanner.
STEPS TO REPRODUCE
1. Plug in a scanner
2. Configure the scanner options in Skanpage
3. Power cycle/unplug and replug the scanner
4. Reselect scanner in Skanpage (or close and reopen Skanpage)
OBSERVED RESULT
The scanner options have been reset.
EXPECTED RESULT
The scanner options should be preserved.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.1
ADDITIONAL INFORMATION
By looking in `~/.local/state/skanpagestaterc` I've noticed that ID the
settings are saved under is based on the USB device id. In my case that is
`avision:libusb:005:011`.
Every time I power cycle/replug the scanner, its USB device ID increments by
one, why I currently have a lot of configured devices named
[Options For avision:libusb:005:007]
[Options For avision:libusb:005:008]
[Options For avision:libusb:005:010]
[Options For avision:libusb:005:011]
[Options For avision:libusb:005:051]
all for the same scanner.
Looking at
https://invent.kde.org/utilities/skanpage/-/blob/master/src/Skanpage.cpp
i found that `void Skanpage::saveScannerOptions()` and `void
Skanpage::loadScannerOptions()` uses `d->m_ksaneInterface.deviceName()` to
determine the device name, but it should probably use `d->m_deviceVendor()` and
`d->m_deviceModel()` instead.
--
You are receiving this mail because:
You are watching all bug changes.
