Bug 128825 - TPU options incomplete in the kooka front-end for Epson Perfection 2400 Photo
Summary: TPU options incomplete in the kooka front-end for Epson Perfection 2400 Photo
Status: RESOLVED WORKSFORME
Alias: None
Product: kooka
Classification: Applications
Component: general (other bugs)
Version First Reported In: 0.44
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Klaas Freitag
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-08 14:18 UTC by Heribert
Modified: 2023-01-05 05:26 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Heribert 2006-06-08 14:18:47 UTC
Version:           0.44 (using KDE KDE 3.5.1)
Installed from:    SuSE RPMs
Compiler:           SuSE 10.1
OS:                Linux

OS: SuSE 10.1 RC3
Scanner: Epson Perfection 2400 Photo
Scanner installation by means of SuSE's YAST was without problems. Scanner and USB connection were recognized without problems. Scanning on flatbed base is fine.
The TPU choice is obviously imperfect:
The kooka-frontend is missing an option for scanning negative photos by using the TPU of the Epson Perfection 2400 Photo. The TPU-frame is scanned as a whole, negative pictures are not converted, pictures in the frame are not scanned separately. The scanresult is a vertical black bar (the TPU) containing the diapositive respectively the negative pictures.
Comment 1 Andrew Crouthamel 2018-11-02 04:19:10 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-16 02:36:38 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version?

Thank you for helping us make KDE software even better for everyone!
Comment 3 Justin Zobel 2022-12-06 00:57:07 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Bug Janitor Service 2022-12-21 05:17: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 5 Bug Janitor Service 2023-01-05 05:26:45 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!