[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Problem scanning with Kooka/Epson Perfection 2400
From:       "Steven P. Ulrick" <ulrick2 () faith4miracle ! org>
Date:       2004-11-10 11:38:03
Message-ID: 200411100538.03435.ulrick2 () faith4miracle ! org
[Download RAW message or body]

Hello, Everyone
This is a problem that I had been having for some time using Kooka from CVS 
HEAD on Fedora Core 2.  I have sent two previous messages (one might not have 
made it to the list) on this to the list with no response.  So, since I have 
new information on this problem, here we go :)
My current system profile:
Operating system: Fedora Core 3
Installation type: Full install (I did not Upgrade from a previous version.  
Reformatted the harddrive, etc.)  I chose to install Every package possible.
Installation status: all official updates installed.
QT version: 3.3.3, from a tarball I got from Trolltech.com
KDE version: CVS HEAD
Method of using these non-default versions of QT and KDE: the appropriate path 
is exported to in my /home/steve/.bash_profile file.  I Did Not overwrite the 
versions of KDE and QT that come with Fedora Core 3.
Exact commands that I use to export the appropriate QT and KDE paths:
QTDIR=/usr/local/qt-src
PATH=$QTDIR/bin:$PATH
MANPATH=$QTDIR/doc/man:$MANPATH
LD_LIBRARY_PATH=$QTDIR/lib:$LD_LIBRARY_PATH
export QTDIR PATH MANPATH LD_LIBRARY_PATH

KDEDIR=/usr/local/kde-cvs
PATH=$KDEDIR/bin:$PATH
LD_LIBRARY_PATH=$KDEDIR/lib:$LD_LIBRARY_PATH
LIBRARY_PATH=$LD_LIBRARY_PATH
export KDEDIR PATH LD_LIBRARY_PATH LIBRARY_PATH

My reasons for suspecting that the scanner itself works perfectly:
I can scan successfully using Xsane logged in as any user that has permissions 
to use the scanner.  I can also scan using the version of Kooka that comes 
with Fedora Core 3, If and Only If, I am logged in as a user that Does Not 
have the above quoted "export" commands in his .bash_profile.

The problem goes as follows:
Anyone logged in as a user that contains the "export" commands quoted above in 
their .bash_profile, assuming that they have permissions to use the scanner, 
get the appearance of scanning an image, but no image is actually displayed 
in the gallery or in the preview pane, and no image is saved in 
"~/.kde/share/apps/ScanImages"  No error messages of any kind.  No apparent 
reasons for failure, and no apparent reasons to suspect that anything was 
scanned.
BUT, if I create a user account that does not export using the above quoted 
commands, and if I run the FC3 version of Kooka (0.44), scanning works 
exactly as expected.  Same scanner, everything is the same except the QT/KDE 
path that is used.
In case anyone asks the perfectly reasonable question, "Why do you think this 
is a KDE issue, and not a Fedora Core 3 issue?"  I would respond that when I 
got this scanner, using it with KDE from CVS HEAD on Fedora Core 2, with the 
same "export" commands as quoted above in my .bash_profile, as long as I had 
permission to use the scanner, everything worked as expected.

Here are links to the two previous emails that I sent to this list on this 
subject.  The only important difference between the emails contained at the 
link above is that they refer to our OS as Fedora Core 2.  This is no longer 
the case, since we are now running FC3.  These might be helpful, since they 
contains screen shots that show what I am trying to explain.
http://lists.kde.org/?l=kde-devel&m=109911659605786&w=2
http://lists.kde.org/?l=kde-devel&m=109973343532097&w=2

Here is a link to a tarball containing two straces.  One of them is from an 
account that exports to KDE from CVS HEAD, and one of them is from an account 
that uses the KDE that comes with Fedora Core 3.  The files inside of the 
tarball are labeled appropriately:
http://www.faith4miracle.org/strace-kooka.tar.bz2

Here is a link to a tarball containing the output that was produced when I ran 
the various versions of Kooka referred to above from a terminal window:
http://www.faith4miracle.org/TerminalOutput-Kooka.tar

In closing, if all you can tell me is that this is not a KDE problem, and why 
it is not, that would be cool.  That way I can begin this thread on the 
Fedora-devel list.  I know that I could do my scanning using Xsane, but I am a 
big KDE fan, so I would prefer to use the fruits of your current labor.

Have a Great Day
Steven P. Ulrick
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]