Bug 359351 - skanlite should display a progress bar when uploading firmware (Usability bug)
Summary: skanlite should display a progress bar when uploading firmware (Usability bug)
Status: RESOLVED WORKSFORME
Alias: None
Product: Skanlite
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Kåre Särs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-13 13:54 UTC by Arek Guzinski
Modified: 2020-12-25 04:34 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arek Guzinski 2016-02-13 13:54:15 UTC
I have an Epson Perfection 660 scanner, which needs its firmware uploaded every time before scanning.
When i start skanlite, a window pops up for maybe 0.5 seconds, then vanishes. After that nothing visible happens for a minute or two. Then the Skanlite window appears and everything works.

Now i know, the firware is being uploaded and i just need to wait a bit, but a new user would think that the application crashed.

Reproducible: Always
Comment 1 Kåre Särs 2016-02-13 14:03:41 UTC
Thanks for the report.

I was not aware of this problem. I have never seen that before. How does scanimage/xsane/... handle the situation?
Comment 2 Arek Guzinski 2016-02-13 14:53:52 UTC
Well, lets see...

xsane: same as skanlite :/

what i didn't notice before is that all three applications print the following 2 lines to stderr (which also answers the question how scanimage handles this): 
[snapscan] Scanner warming up - waiting 31 seconds.
[snapscan] Scanner warming up - waiting 31 seconds.

well, maybe i was wrong after all and the firmware isn't the reason - does not change the UI-issue though.
Comment 3 Justin Zobel 2020-11-24 05:36:40 UTC
Arek, thanks for the report. My scanner doesn't do firmware uploads so I have been unable to test this.

Can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I've set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved" when you respond, thanks.
Comment 4 Arek Guzinski 2020-11-25 07:22:28 UTC
Nice to see the old bugs still get attention...
Unfortunately I cannot test this, as I don't have a scanner anymore.
Comment 5 Bug Janitor Service 2020-12-10 04:34:34 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2020-12-25 04:34:24 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!