Bug 37123 - ksysv crashed each time it's run
Summary: ksysv crashed each time it's run
Status: RESOLVED DUPLICATE of bug 81927
Alias: None
Product: ksysv
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Mandrake RPMs Other
: NOR crash
Target Milestone: ---
Assignee: Niels Reedijk
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-01-14 16:33 UTC by kinpoonc
Modified: 2006-05-23 17:55 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kinpoonc 2002-01-14 16:20:42 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           ksysv
Version:           KDE 2.2.1 
Severity:          normal
Installed from:    Mandrake RPMs
Compiler:          Not Specified
OS:                Not Specified
OS/Compiler notes: Not Specified

Whenever I run ksysv (KDE 2.2.1 or 2.2.2) it crashes out.  This is what appears when it's run within terminal mode: -
[chankp@m81 chankp]$ 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).

KCrash: crashing.... crashRecursionCounter = 2
KCrash: Application Name = ksysv path = <unknown> pid = 3396
ERROR: KUniqueApplication: DCOP communication error!

I'm not sure if this is peculiar to Mandrake 8.1 as I do not have other distributions.  Thank you.


(Submitted via bugs.kde.org)
Comment 1 Shane Shields 2002-02-11 20:35:49 UTC
hi
i just want to add that i have exactly the same problem on a linux from 
scratch system compiled from source with kde 2.2.2 compiled from source.
i get the same message when run from konsole. if you delete the ksysvrc the 
configuration section works until you try to start ksysv proper which then 
shows a nice crash screen. ksysv used to work then started with an 
intermittent crash then continuous crash (all on startup). tried recompiling 
and installing (thought maybe had something to do with strip) but no different

best regards
Shane Shields
locutus@all.at

ps. i rate this bug as severe (i like ksysv) :-)
-- 
To drink the WINE of success you must first seek the sayings of source

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
Comment 2 Oliver Dinkel 2002-03-31 10:14:39 UTC
Hi
ksysv is still crashing. Here  is the shell output:

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

kio (KDirWatch): Available methods: Stat
kio (KDirWatch): Added Dir /etc/init.d [KDirWatch-1]
kio (KDirWatch): Global Poll Freq is now 500 msec
kio (KDirWatch):  Started Polling Timer freq 500
kio (KDirWatch):  Setup Stat (freq 500) for /etc/init.d
KCrash: crashing.... crashRecursionCounter =3D 2
KCrash: Application Name =3D ksysv path =3D <unknown> pid =3D 30071
ERROR: KUniqueApplication: DCOP communication error!

Perhaps the problem is the new directory structure wich some
distributions introduced:

Scripts: /etc/init.d
Links: /etc/init.d/rcX.d

With best regards
Oliver
--=20
Oliver Dinkel
ODIN - Informatik
http://www.olidin.ch
Comment 3 Basd 2002-05-20 23:10:00 UTC
I can't use ksysv because it crashes on start up.  On only one 
occasion it asked me for the distribution I use said I had 
successfully configured ksysv and then it crashed. 

The error codes are the same as those submitted by others.  I am 
running Mandrake 8.2.

However I can add this comment -- the crash may be cause because the 
files read by ksysv are corrupted.  The reason I want to run it is 
that I receive two error msgs when I boot.  The first says something 
like "rc.sysinit : test : too many arguments.

The second says "-bg not found."

I think these have something to do with the "setserial" rpm.  The 
first error emerged after I installed "setserial" and the second 
emerged after I >removed< "setserial" hoping to cure the first error.

I can't figure out what the problem is.  All of the files that would 
seem to me to be relevant have "last modified" dates earlier than 
when the problem first started happening.

The error messages occur at the very beginning of the rc.sysinit 
processing and do not appear to cause any problems.
Comment 4 Craig Genner 2003-01-05 13:23:04 UTC
Had no problems with Mandrake 7.1 and Ksysv, but every Mandrake version since
then Ksysv just crashes.  This happens no matter which user you try and run it
as.  When running for the first time it asks for your distro, Chosing Mandrake
as the distro and then finishing the wizard it crashes.  Starting Ksysv later
misses out the wizard and just crashes.

Error messages when run from the shell produces the following messages:

[root@laptop tmp]# 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).

DCOPServer up and running.
KCrash: crashing.... crashRecursionCounter = 2
KCrash: Application Name = ksysv path = <unknown> pid = 3106
DCOP aborting call from 'anonymous-3105' to 'ksysv'
ERROR: KUniqueApplication: DCOP communication error!
[root@laptop tmp]# Mutex destroy failure: Device or resource busy
kdeinit: Fatal IO error: client killed
kdeinit: sending SIGHUP to children.
kdeinit: sending SIGTERM to children.
kdeinit: Exit.

This happens on any computer Mandrake that I have seen.
Comment 5 Charles Chambers 2003-01-16 14:08:04 UTC
This is the graphical output when it's run and crashes.  I'm running Mandrake
9.0 and 3.0.5 of KDE (just updated yesterday).

(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)...
(no debugging symbols found)...(no debugging symbols found)...
0x410c9739 in wait4 () from /lib/i686/libc.so.6
#0  0x410c9739 in wait4 () from /lib/i686/libc.so.6
#1  0x41146340 in sys_sigabbrev () from /lib/i686/libc.so.6
#2  0x40eeaa73 in waitpid () from /lib/i686/libpthread.so.0
#3  0x40685195 in KCrash::defaultCrashHandler(int) ()
   from /usr/lib/libkdecore.so.4
Comment 6 vatbier 2003-09-28 23:51:04 UTC
I have Mandrake Linux 9.1: KDE3.1 
kdeadmin-3.1-8mdk 
SysV-Init Editor crashes everytime in ML9.1 only with this error message 
	ERROR: KUniqueApplication: DCOP communication error! 
I remember having this problem also in ML8.2, but then some 
day SysV-Init Editor in ML8.2 started working and still works 
without problem in ML8.2. 
But in ML9.1 the problem is persistent. 
Comment 7 Dirk Mueller 2006-05-23 17:55:47 UTC

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