https://bugs.kde.org/show_bug.cgi?id=370972
Kåre Särs changed:
What|Removed |Added
CC||linuxdav...@gmail.com
--- Comment #46 from Kåre Sär
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #45 from Kåre Särs ---
Hi,
At least there was one bug in libksane! This should now be fixed. libksane
could not handle asymmetrical gamma-tables. So it looks like the problem was
_not_ in the niash backend after all... I'm not able to fully
https://bugs.kde.org/show_bug.cgi?id=370972
Kåre Särs changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Version Fixed In|
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #43 from Kåre Särs ---
I have now checked the code in niash and found that the gamma-table in niash is
4096 entries with the range 0-255. Libksane has so far expected that the number
of entries is the same as the maximum value. This has to b
https://bugs.kde.org/show_bug.cgi?id=370972
Kåre Särs changed:
What|Removed |Added
Ever confirmed|0 |1
Resolution|WAITINGFORINFO |-
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #41 from Christoph Feck ---
What is the status of this bug? It is unclear what additional information is
needed.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #40 from Ilario Gottardello ---
Kåre, you're right!! Changing gamma value trigger the corruption even starting
from a clean state!!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #39 from Ilario Gottardello ---
Created attachment 114126
--> https://bugs.kde.org/attachment.cgi?id=114126&action=edit
output log (lvel 255) from clean start but changing gamma value
--
You are receiving this mail because:
You are watch
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #38 from Ilario Gottardello ---
Created attachment 114125
--> https://bugs.kde.org/attachment.cgi?id=114125&action=edit
output log (lvel 255) from clean start
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #37 from Kåre Särs ---
Thanks for the logs.
Unfortunately in that log level I could not find anything strange except
for the gamma table that seems to be 64 16bit entries.
I wonder what happens if you remove the rc file and alter the g
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #36 from Ilario Gottardello ---
These are two executions of skanlite, the first with the rc file and the second
one without it:
[niash] sane_get_option_descriptor 6
[niash] sane_control_option: option 6, action 0
[niash] sane_control_optio
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #35 from Marc Collin ---
with tumbleweed I get
SANE_DEBUG_NIASH=16 skanlite
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-postgres'
qt.qpa.screen: QXcbConnection: Could not connect to display
Could not connect to any
https://bugs.kde.org/show_bug.cgi?id=370972
Kåre Särs changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #33 from Ilario Gottardello ---
(In reply to George Seaton from comment #32)
> Removing the Skanliterc in SL7 fixes the broken colour image for me in SL7
> (RHEL7).
> If I then restart skanlite then I get the broken colour image preview agai
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #32 from George Seaton ---
Removing the Skanliterc in SL7 fixes the broken colour image for me in SL7
(RHEL7).
If I then restart skanlite then I get the broken colour image preview again.
Looks like it has to be deleted every time.
The skan
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #31 from Kåre Särs ---
Thanks for the update!
So if you now close Skanlite and start again does it still work or do you have
to remove the rc file every time for it to work?
And if it continues to work how does the rc file look now?
Regar
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #30 from Ilario Gottardello ---
It works Removing the skanliterc file fixed the issue!! I really
don't understand why, it doesn't contain odd things.. but, now it works :)
--
You are receiving this mail because:
You are watchin
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #29 from Ilario Gottardello ---
Created attachment 114061
--> https://bugs.kde.org/attachment.cgi?id=114061&action=edit
Skanlite: rc file
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #28 from Ilario Gottardello ---
Created attachment 114060
--> https://bugs.kde.org/attachment.cgi?id=114060&action=edit
Skanlite: options and preview
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #27 from Ilario Gottardello ---
Created attachment 114059
--> https://bugs.kde.org/attachment.cgi?id=114059&action=edit
Digikam: options and preview
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370972
Marc Collin changed:
What|Removed |Added
CC||coll...@laboiteaprog.com
--- Comment #26 from Mar
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #25 from Kåre Särs ---
I have now investigated my HP Deskjet scanner problem and it turned out to be a
bug in the backend. The backend returned bytes_per_line == pixels_per_line even
if the image is encoded one bit (not byte) per pixel.
I h
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #24 from Marc ---
I still have the problem, I can provide you information you will ask tonigh
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #23 from Maik Qualmann ---
I am currently unable to reproduce problems with Skanlite and my Epson scanner.
All scan options work as expected, also line-art.
Maik
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #22 from Kåre Särs ---
I actually tested the "line-art" option on a HP printer/scanner and yes there
is something wrong with converting "line-art" data to a QImage. The preview
looks OK tho... Now that I have a HP scanner I can at least chec
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #21 from Ilario Gottardello ---
Kåre, Maik,
if you need some test with the HP ScanJet I am willing to help. Are the options
screenshots still needed?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #20 from Maik Qualmann ---
You're right, the preview must come from the KSaneWidget. We use the libksane
from the system, if it is not available, we compile an internal one from
git/master. I'll check it tonight and see if I can reproduce th
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #19 from Kåre Särs ---
Hi Maik,
Do you mean that Digikam just doesn't use the KSaneWidget::toQImage() or that
it doesn't use vanilla libksane?
The thing is that the preview window should be identical in both applications
if vanilla libksa
https://bugs.kde.org/show_bug.cgi?id=370972
Maik Qualmann changed:
What|Removed |Added
CC||metzping...@gmail.com
--- Comment #18 from Maik
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #17 from Kåre Särs ---
Thanks for the update and the screen-shots.
Could you also take screen-shots of the "Scanner Specific" options in Skanlite
and Digikam?
I suspect that the problem might be that Skanlite uses different default values
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #16 from Ilario Gottardello ---
Created attachment 113972
--> https://bugs.kde.org/attachment.cgi?id=113972&action=edit
Digikam window
This is the digikam window (with no document on the scanner, but it works well)
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #15 from Ilario Gottardello ---
Created attachment 113971
--> https://bugs.kde.org/attachment.cgi?id=113971&action=edit
Skanlite window
This is what I get from a preview from the scanner
--
You are receiving this mail because:
You are w
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #14 from Ilario Gottardello ---
(In reply to Kåre Särs from comment #11)
> Ilario,
>
> Can you try with different settings: color mode, color depth, resolution,
> gamma,...
>
> This is probably a scanner specific problem with the backend(d
https://bugs.kde.org/show_bug.cgi?id=370972
George Seaton changed:
What|Removed |Added
CC||george.sea...@iinet.net.au
--- Comment #13 from
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #12 from Ilario Gottardello ---
Tried with varing combinations of options, still same result: the image is
garbled
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #11 from Kåre Särs ---
Ilario,
Can you try with different settings: color mode, color depth, resolution,
gamma,...
This is probably a scanner specific problem with the backend(driver) and how it
works with Skanlite.
/Kåre
--
You are rec
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #10 from Ilario Gottardello ---
Kåre,
unfortunately it doesn't change anything
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #9 from Kåre Särs ---
Sorry Marc for not answering earlier.
Could you try resetting the scanner options to their default values?
Go to "Settings" (Configuration) and click on the "Revert scanner options to
default values"
/Kåre
--
You a
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #8 from Ilario Gottardello ---
forgot to say that I use Ubuntu Neon and skanlite is at version
2.0.1-0neon+16.04+xenial+bu amd64
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370972
Ilario Gottardello changed:
What|Removed |Added
CC||ilario.gottarde...@gmail.co
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #6 from Marc ---
Created attachment 101675
--> https://bugs.kde.org/attachment.cgi?id=101675&action=edit
scan like specific option
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #5 from Marc ---
Created attachment 101674
--> https://bugs.kde.org/attachment.cgi?id=101674&action=edit
scan lite basic option
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #4 from Kåre Särs ---
The thing is that Digikam and Showfoto use the same library as Skanlite...
Can you attach a screen-shot of the settings? Both "Basic Options" and "Scanner
Specific Options"?
--
You are receiving this mail because:
Yo
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #3 from Marc ---
i use hp scanjet 3300c
get same result with grey or color mode
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #2 from Kåre Särs ---
Thanks for the report!
I wonder if you are scanning in 8 or 16 bits per color mode? It looks a bit
like it could be a byte order problem.
What scanner are you using and are you using 16 bits / color mode?
Regards,
https://bugs.kde.org/show_bug.cgi?id=370972
--- Comment #1 from Marc ---
Created attachment 101593
--> https://bugs.kde.org/attachment.cgi?id=101593&action=edit
scanned image with skanlite
scanned image with skanlite
--
You are receiving this mail because:
You are watching all bug changes.
46 matches
Mail list logo