I wonder if anyone else has had difficulties getting Kooka to recognize a Mustek 1200 scanner while logged in as a normal user. It works fine while logged in as root showing all the buttons but greys out the scan and scan preview buttons as user. Xsane works fine as both root and user.

I am running Suse 9.2 and have had kooka work fine in my other PC without all the gremlins. Strangely although packaged as a Scanexpress 1200 UP, Scanimage -L reports it as a Mustek Bearpaw 1200CU and I post the /sbin/lsusb information below which reports something completely different (as reported by Yast2):-
/sbin/lsusb
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 004: ID 043d:0078 Lexmark International, Inc.
Bus 001 Device 003: ID 05d8:4002 Ultima Electronics Corp. Artec Ultima 2000 (GT6801 based)/Lifetec LT9385 Scanner

(The lexmark printer is the next problem to work on...it does work on the other PC after much hair pulling and tooth gnashing)

Any hints would be greatly appreciated.

Many thanks
Andrew Johnson

After much googling I have discovered that it is a permissions thing.
After firing up both xsane and kooka from a user shell I discovered that:-
xsane works without a glitch
kooka however brought the following dialogue


ajohnson@eccles:~> kooka
QLayout: Adding QComboBox/PREVIEWFORMATCOMBO (child of QVButtonGroup/unnamed) to layout for Previewer/unnamed
libkscan: WARNING: Trying to copy a not healthy option (no name nor desc)
libkscan: WARNING: Trying to copy a not healthy option (no name nor desc)
QObject::connect: Cannot connect (null)::guiChange(KScanOption*) to ScanParams::slOptionNotify(KScanOption*)

Thanks for reading my plea anyway.
Andrew Johnson



p.s. Lexmark printer went in like a dream on this machine, now I know how

While not a clean fix, I discovered that for some reason starting kooka up from my home folder caused these problems.
DOGH!

Starting it from where it is installed in /opt/kde3/bin/ resolved the problems.

I have altered Kmenu accordingly. Now to go and read up more 'howto' s.

atj1 - congrats on solving the problem and many thanks for posting back with the solution that worked for you. This kind of post will be very helpful to future readers who may be encountering the same problem. Well done -- J.W.

Welcome to LQ!