Bug 54579 - Kappfinder starts correctly. when scan is started the program crashes.
Summary: Kappfinder starts correctly. when scan is started the program crashes.
Status: RESOLVED FIXED
Alias: None
Product: kappfinder
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Mandrake RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Matthias Hoelzer-Kluepfel
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-13 00:10 UTC by michael napier
Modified: 2003-03-23 16:34 UTC (History)
0 users

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


Attachments
backtrace from crash of kappfinder (1.29 KB, text/plain)
2003-03-03 16:51 UTC, Steve
Details

Note You need to log in before you can comment on or make changes to this bug.
Description michael napier 2003-02-13 00:10:32 UTC
Version:           unknown (using KDE 3.1.0)
Installed from:    Mandrake Linux Cooker i586 - Cooker
Compiler:          gcc version 3.2.1 (Mandrake Linux 9.1 3.2.1-5mdk)
OS:          Linux (i686) release 2.4.21pre4-1mdk

Kappfinder starts correctly. when scan is started the program crashes. This behaviour occurs as a regular user and as root.

backtrace:


(no debugging symbols found)...[New Thread 16384 (LWP 27807)]
(no debugging symbols found)...0x420ad539 in wait4 () from /lib/i686/libc.so.6
#0  0x420ad539 in wait4 () from /lib/i686/libc.so.6
#1  0x4212d910 in sys_sigabbrev () from /lib/i686/libc.so.6
#2  0x40eb7fc3 in waitpid () from /lib/i686/libpthread.so.0
#3  0x405f87eb in KCrash::defaultCrashHandler(int) ()
   from /usr/lib/libkdecore.so.4
#4  0x0804fa67 in QWidget::windowActivationChange(bool) ()
#5  0x0805035c in QWidget::windowActivationChange(bool) ()
#6  0x4098034b in QObject::activate_signal(QConnectionList*, QUObject*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
Comment 1 Steve 2003-03-03 16:51:24 UTC
Created attachment 1091 [details]
backtrace from crash of kappfinder
Comment 2 Tobias Koenig 2003-03-07 20:46:51 UTC
Hi Michael, 
 
concerning the backtrace, it doesn't look like a bug in the program, but 
a bug in some libs (maybe qt). 
Could you use strace to check what files are accessed before the segfault 
appears? 
 
Ciao, 
Tobias 
Comment 3 Charles 2003-03-09 21:22:10 UTC
Happens to me on Debian woody too.  here's the backtrace from the crash handler:

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...0x40e97a59 in wait4 () from /lib/libc.so.6
#0  0x40e97a59 in wait4 () from /lib/libc.so.6
#1  0x40f0ee48 in __check_rhosts_file () from /lib/libc.so.6
#2  0x40d5a453 in waitpid () from /lib/libpthread.so.0
#3  0x405246ea in KCrash::defaultCrashHandler () from /usr/lib/libkdecore.so.4
#4  0x40d57f54 in pthread_sighandler () from /lib/libpthread.so.0
#5  0x40e206b8 in sigaction () from /lib/libc.so.6
#6  0x0804f138 in KDialog::marginHint ()
#7  0x0804f85a in KDialog::marginHint ()
#8  0x40856ef9 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#9  0x40856e3e in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#10 0x40abecf0 in QButton::clicked () from /usr/lib/libqt-mt.so.3

incidentally, this is the second time in the last week I've installed Debian
woody on my computer.  The first time around, kappfinder worked.  The second
time, and I'm not aware of having done anything different, it starts crashing on
scan. 
Comment 4 michael napier 2003-03-11 06:38:29 UTC
Subject: Re:  Kappfinder starts correctly. when scan is started the program crashes.         

Tobias, since the new releae this bug has been resolved. I tried to
enter that info in the bug tool but it says I don't have permission.
sorry.

--- Tobias K
Comment 5 Tobias Koenig 2003-03-23 16:34:11 UTC
Hi Michael, 
 
so I'll close the bug report now, thank you for your help. 
 
Ciao, 
Tobias