Bug 81177 - Kooka crashes after selecting which SANE device to use.
Summary: Kooka crashes after selecting which SANE device to use.
Status: RESOLVED FIXED
Alias: None
Product: kooka
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: RedHat Enterprise Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Klaas Freitag
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-09 08:26 UTC by Jason Hecker
Modified: 2008-03-10 20:04 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jason Hecker 2004-05-09 08:26:06 UTC
Version:           0.42 (using KDE KDE 3.2.2)
Installed from:    RedHat RPMs
Compiler:           Whatever was used to compile FC1 KDE3.2.2 RPMs on KDE's site.
OS:          Linux

In FC1 with the KDE compiled RPMs (v3.2.2) Kooka (0.42) crashes with SIGNAL 11 after choosing which SANE device to use.  SANE is v1.0.12.

Here's some useless debug info:

This backtrace appears to be useless.
This is probably because your packages are built in a way which prevents creating of proper backtraces, or the stack frame was seriously corrupted in the crash.

(no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[Thread debugging using libthread_db enabled]
[New Thread -1084655968 (LWP 6037)]
(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
0x0077bc32 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#0  0x0077bc32 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1  0x0076bb03 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
#2  0x00292dc4 in KCrash::defaultCrashHandler(int) ()
   from /usr/lib/libkdecore.so.4
Comment 1 Klaas Freitag 2004-05-10 10:53:25 UTC
Sorry, but you have to admit that this does not provide any usefull information for me. Please try to encourage RedHat to provide a debug version and try again to produce a proper backtrace.
Moreover, which scanner/sane-backend do you use? Is your scanner working properly with xscanimage?

Comment 2 Jason Hecker 2004-05-12 11:06:40 UTC
Hi,

I put the versions of SANE in the comments.  The scanner is a Canon 620P.  I 
can scan fine with xsane.  The KDE 3.2.2 RPM's were provided by KDE.org.  
I'll leave it for now as I just want to do some photo scanning at some point 
so it's not urgent.  Fedora Core 2 is out next week so I'll try Kooka out 
again and see what happens.

Tschuess,
Jason

On Mon, 10 May 2004 18:53, Klaas Freitag wrote:
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>
> http://bugs.kde.org/show_bug.cgi?id=81177
>
>
>
>
> ------- Additional Comments From freitag suse de  2004-05-10 10:53 -------
> Sorry, but you have to admit that this does not provide any usefull
> information for me. Please try to encourage RedHat to provide a debug
> version and try again to produce a proper backtrace. Moreover, which
> scanner/sane-backend do you use? Is your scanner working properly with
> xscanimage?

Comment 3 Mikal Krogstad 2004-09-05 18:54:25 UTC
I have the same problem with a Canon FB330P (canon_pp, using parallel port). KDE 3.3, Sane 1.0.14 (Both Arch Linux packages) on kernel 2.6.8.1.  
Parallel devices in general are a bit tricky to get working, so the scanner software either need to run as root (No fun), use libieee1284 (Not working, and dunno where to start looking why) or run against saned. 
If I run Kooka as root (WITHOUT saned running), it works fine directly against the parport, but it is a bit more hassle than just clicking the Kooka icon (I could prob make a small script that uses sudo, but still). So, I want to run saned. It starts fine from xinetd, and xsane has no problems using it. But when starting Kooka: 

(allanon@seier ~) 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*)
KCrash: Application 'kooka' crashing...

I hope the backtrace can be used:

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 2449)]
[KCrash handler]
#5  0x416cd86b in strlen () from /lib/libc.so.6
#6  0x42656bdd in do_authorization () from /usr/lib/sane/libsane-net.so.1
#7  0x426582e6 in sane_net_control_option ()
   from /usr/lib/sane/libsane-net.so.1
#8  0x40209dba in sane_dll_control_option () from /usr/lib/libsane.so.1
#9  0x4020a109 in sane_control_option () from /usr/lib/libsane.so.1
#10 0x401e090b in KScanOption::slReload () from /opt/kde/lib/libkscan.so.1
#11 0x401d783f in KScanDevice::slReloadAll () from /opt/kde/lib/libkscan.so.1
#12 0x401ebd89 in ScanParams::connectDevice () from /opt/kde/lib/libkscan.so.1
#13 0x08068d63 in KParts::DockMainWindow::metaObject ()
#14 0x08069fc1 in KParts::DockMainWindow::metaObject ()
#15 0x08065745 in endl ()
#16 0x08063909 in ?? ()
#17 0x08167178 in ?? ()
#18 0xbffff7b0 in ?? ()
#19 0x0809884b in vtable for QPtrList<char> ()
#20 0x00000000 in ?? ()
#21 0x00000000 in ?? ()
#22 0x00000001 in ?? ()
#23 0x0809369d in typeinfo name for QGList ()
#24 0x00000000 in ?? ()
#25 0x08093688 in typeinfo name for QGList ()
#26 0x08093663 in typeinfo name for QGList ()
#27 0x40a5b8c1 in mALLOc () from /opt/kde/lib/libkdecore.so.4
#28 0x4166ebef in __libc_start_main () from /lib/libc.so.6
#29 0x08063661 in ?? ()
Comment 4 Mikal Krogstad 2004-12-15 14:28:22 UTC
Still present in KDE 3.3.2/Kernel 2.6.9.
Comment 5 Jonathan Marten 2008-01-22 19:36:32 UTC
Please check whether this is still a problem with a recent version of KDE, for example 3.5.8 (unfortunately no Kooka in 4.0).
Comment 6 Jason Hecker 2008-01-23 10:28:45 UTC
Kubuntu 7.10 with Kooka 0.44 doesn't seem to exhibit this behaviour.  The only SANE device I have now is a DVT-T card (BT878 type device).
Comment 7 Jonathan Marten 2008-03-10 20:03:19 UTC
For lack of saned authentication see bug 146874.

Closing as user confirms not happening now, see bug referenced above for feature wish.
Comment 8 Jonathan Marten 2008-03-10 20:04:12 UTC
*** Bug has been marked as fixed ***.