https://bugs.kde.org/show_bug.cgi?id=425958
Hamidreza Jafari changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=425958
--- Comment #7 from Nate Graham ---
So it's working now?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=425958
--- Comment #6 from Hamidreza Jafari ---
It is now possible to scan full flatbed i.e. A3 with one of the found devices.
Actually as mentioned by one of the maintainers one actual device is viewed by
two different protocols each with different
https://bugs.kde.org/show_bug.cgi?id=425958
--- Comment #5 from Bug Janitor Service ---
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
https://bugs.kde.org/show_bug.cgi?id=425958
2wxsy5823...@opayq.com changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=425958
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=425958
--- Comment #3 from Kåre Särs ---
Thanks for the report.
Did you get the device to work?
It seems that the device supports two scanning protocols and when the sane
library searches for scanners it finds both and does not know that it is the
same
https://bugs.kde.org/show_bug.cgi?id=425958
--- Comment #2 from Hamidreza Jafari ---
Yes, some people have been so mean and greedy. They fail to see the bug picture
and subsequently suffer from their ignorance. Software engineers have a better
understanding of the world I believe. It says
https://bugs.kde.org/show_bug.cgi?id=425958
Maksym Hazevych changed:
What|Removed |Added
CC||dpa...@protonmail.com
--- Comment #1 from
