[Skanlite] [Bug 429260] Very slow UI
https://bugs.kde.org/show_bug.cgi?id=429260 cactus changed: What|Removed |Added CC||beeboon2...@yahoo.fr --- Comment #6 from cactus --- Hello all, Skanlite is very very slw through LAN connection, it freezes approx. 1 minute at each UI change (changing a parameter through the UI like opening a scrolling menu, change tab...). Sometimes, it crashes completely. Note that Skanlite works perfectly through USB. I can use Simple-Scan instead, which works perfectly with LAN connection, but I would prefer Skanlite because of its advanced functions. I don't know what information or log you need to investigate, I keep this thread open in my browser to answer quite quickly. My Hardware (even I don't think it is the cause) : Canon MG3650, connected on a Raspberry Pi, which works perfectly on all configurations (Linux & Windows), excepting Skanlite over LAN. Thanks for your help ! ;) -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 429260] Very slow UI
https://bugs.kde.org/show_bug.cgi?id=429260 --- Comment #8 from cactus --- (In reply to Bug Janitor Service from comment #7) > A possibly relevant merge request was started @ > https://invent.kde.org/graphics/libksane/-/merge_requests/53 I disagree, pixma network backend works perfectly with simple-scan ! -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 429260] Very slow UI
https://bugs.kde.org/show_bug.cgi?id=429260 --- Comment #10 from cactus --- (In reply to Kåre Särs from comment #9) > Note: We are _not_ disabling the backend, just the one feature of polling of > the read-only options (like detecting a button being pressed on the > scanner). Since Simple-scan does not seem to support that feature, it does > not get bitten by it's problems either. Once this feature is disabled the > scanning should be fine again. > > So basically we disable just that one feature that does not work. The new > (sad) thing here is that this is the first time that we check what backend > is in use, in stead of being generic. OK, I apologize, I didn't understand that way. I hope it will solve the problem ! ;) Thank you ! -- You are receiving this mail because: You are watching all bug changes.
