Bug 86356

Summary:	SysV Crashes at startup of the program
Product:	[Unmaintained] ksysv	Reporter:	Nathaniel Dube <AvatarofVirgo>
Component:	general	Assignee:	Niels Sascha Reedijk <niels.reedijk>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	gwolgemu
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Nathaniel Dube 2004-07-31 22:58:28 UTC

Version:           SysV 2.85-20 i586 (using KDE KDE 3.2.3)
Installed from:    SuSE RPMs
Compiler:          gcc 3.3.3-41 i586, gcc-c++ 3.3.3-41 i586 and libgcc 3.3.3-41 i586 
OS:                Linux

I have ever thing in Linux with the latest versions and up to date with all patches.  When I click on SysV from the start menu it crashes on startup all I get is the Backtrace crap.  Here's all the errors I can collect...

(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)...[Thread debugging using libthread_db enabled]
[New Thread 1095742816 (LWP 8520)]
(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)...0xffffe410 in ?? ()
#0  0xffffe410 in ?? ()
#1  0xbfffeb5c in ?? ()
#2  0x00000000 in ?? ()
#3  0x00000000 in ?? ()
#4  0x4129ce63 in __waitpid_nocancel () from /lib/tls/libpthread.so.0
#5  0x40832d82 in KCrash::defaultCrashHandler ()
   from /opt/kde3/lib/libkdecore.so.4
#6  <signal handler called>
#7  0x08071ce2 in ksv::hostname ()
#8  0x08078101 in KSVTopLevel::setCaption ()
#9  0x0808f65a in KSVTopLevel::KSVTopLevel ()
#10 0x08090723 in main ()

And also here's an error when I tried the sysv command in Konsole...

linux:~ # ksysv
SysV-Init Editor 1.3.8 Developer Version Copyright  1997-2000 Peter Putzer.
All rights reserved. Released under the GNU General Public License (GPL).

ERROR: Communication problem with ksysv, it probably crashed.
linux:~ # KCrash: Application 'ksysv' crashing...

linux:~ #

Comment 1 Steven P. Ulrick 2004-08-12 09:35:57 UTC

I get the exact same error in Konsole that Nathaniel got when I try to run ksysv from a terminal window.
I do get (I assume) some useful information from the backtrace:
Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -168581792 (LWP 4578)]
[KCrash handler]
#4  0x0808229f in ksv::hostname () at ksysv/ksv_core.cpp:106
#5  0x0807dae5 in KSVTopLevel::setCaption (this=0x8ff3740, changed=false)
    at ksysv/TopWidget.cpp:961
#6  0x0807a5ee in KSVTopLevel (this=0x8ff3740) at ksysv/TopWidget.cpp:135
#7  0x0806352e in main (argc=1, argv=0xfeeeb3e4) at ksysv/main.cpp:97

Numbers 1 through 3 are missing because of a bug(?) on another KDE component that I NEED to report :)

I am running Fedora Core 2.  All official updates installed.
Our KDE is from CVS HEAD, updated less than an hour ago.
Our QT is from TrollTech's 3.3.2 tarball.

If there is anything else I can do for you on this, please let me know :)

Comment 2 Dirk Mueller 2006-05-23 17:52:53 UTC

*** Bug 78773 has been marked as a duplicate of this bug. ***

Comment 3 Dirk Mueller 2006-05-23 17:54:19 UTC


*** This bug has been marked as a duplicate of 81927 ***