Re: kdekillall command
[Rene Horn] > The kdekillall command requires gawk to work, so perhaps it's a good > idea to make it dependent on this package? Did you submit this to bugs.debian.org? I believe it is a better place to report it than debian-kde, to make sure no one forgets it.
Re: KDE startup hangs and 'commits suicide'
On Sat, 2002-03-16 at 21:36, Steffen Evers wrote: > Hi! > > After updateing a woody machine my KDE does not work any longer. > > It hangs on the second phase (system services) during init and dies > finally with the following error message in the .xsession_errors file: > > kdeinit: Shutting down running client. > - > It looks like dcopserver is already running. If you are sure > that it is not already running, remove /root/.DCOPserver_ocean_:0 > and start dcopserver again. > - > > @[EMAIL PROTECTED]@ > [...] > [EMAIL PROTECTED]@[EMAIL PROTECTED] > (KLauncher): ERROR: KLauncher: KDEInit communication error! Commiting > suicide! > > > Any hints? > > Bye, Steffen > > I have exactly the same problem but I think it can be due to a more general problem because some other window managers(like sawfish) fail also to load. Fabian
Re: Knode will only start if I su to root
Hi, > I'm running KDE on an up-to-date Woody system and while all other KDE > applications are running fine, KNode will only start if I su to root > and launch it from a terminal window. Maybe there is another (old) KNode process running. Try "ps aux ¦ grep knode" to find out if KNode runs. If yes, then kill the process and try to start KNode again. Greetings Reto
Re: KDE startup hangs and 'commits suicide'
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi > > I have exactly the same problem but I think it can be due to a more > general problem because some other window managers(like sawfish) > fail also to load. > > Fabian You may check if the loopback device (lo) is up. That was my problem some weeks ago. I forgot to set it auto in less /etc/network/interfaces. It used to work that way long time, but on one point the wrong behavior (lo was start although not set to auto) changed, but that was causing the problem. Maybe one can add ifup lo to the kde-startupscript. dcop seems to need the loopback interface. Hendrik - -- PGP ID 21F0AC0265C92061 -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.3 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8lLp7IfCsAmXJIGERAnIVAJ4+2/xEWYH0WznqzJruHZg0Df+QkgCgguGA WSaIOg+dMYdXPrv7h6hOsJc= =75hJ -END PGP SIGNATURE-
Re: KDE startup hangs and 'commits suicide'
HI > That was my problem some weeks ago. I forgot to set it auto in less > /etc/network/interfaces. It used to work that way long time, but on > one point the wrong behavior (lo was start although not set to auto) > changed, but that was causing the problem. > > Maybe one can add > > ifup lo > > to the kde-startupscript. dcop seems to need the loopback interface. > > Hendrik > > It works ! Thanks a lot. Fabian
Re: KDE startup hangs and 'commits suicide'
[Fabian Dortu] >> Maybe one can add >> >> ifup lo >> >> to the kde-startupscript. dcop seems to need the loopback interface. [...] > > It works ! Thanks a lot. If this is a fresh install, you have probably been bitten by the bug in the install system failing to configure the loopback interface. The correct fix is probably to add the following to /etc/network/interfaces: # The loopback interface auto lo iface lo inet loopback It should have been added by the install program, but sometimes it failed to do so. The bug is believed fixed in the latest source.
Re: Kde with obj prelink
A Dissabte 16 Març 2002 16:18, Jean-Michel Kelbert va escriure: I compiled all the KDE 2.2.2 on a Debian woody with objprelink two weeks ago. The result was that when KDE starts all segfaults. From icewm the only application than run without any problems was konsole, konq starts very fast and their performance was great but crash when it want to display a file, the sidebar, etc. The result was unusable. The problem could be with binutils. According with Linux From Scratch: "You'll need the latest version of binutils (2.11.2 at this point), and if any of glibc, gcc or binutils were compiled with optimizations there is a chance that everything you prelink will segfault when run. Prelinking failed for me on my LFS 2.4.3 system where those were built with optimizations; on a LFS 3.0 system where glibc, gcc and binutils were compiled with no optimizations and everything else was built -O3 -march=i386 -mcpu=i686, prelinking worked fine. Proceed with caution."
Re: KDE startup hangs and 'commits suicide'
On Sun, Mar 17, 2002 at 20:22, Petter Reinholdtsen wrote: > [Fabian Dortu] > >> Maybe one can add > >> > >> ifup lo > >> > >> to the kde-startupscript. dcop seems to need the loopback interface. > [...] > > > > It works ! Thanks a lot. > > If this is a fresh install, you have probably been bitten by the bug > in the install system failing to configure the loopback interface. > > The correct fix is probably to add the following to > /etc/network/interfaces: > > # The loopback interface > auto lo > iface lo inet loopback > > It should have been added by the install program, but sometimes it > failed to do so. The bug is believed fixed in the latest source. Thanks to all of you!!! That was the problem with my machine as well. After correcting the interfaces file everything is fine again. Strange thing, as the KDE version before the update (2.2.1?) worked without the loopback device. I guess, there will be some more users with this problem ... Bye, Steffen
Kamera + USB permissions
I just tried Kamera after quite a long time and it actually worked. Thank you! It isn't, however, very feasible to use because the device file is owned by root: you always have to change its permissions manually before starting Kamera as a non-root user. I found a small daemon called usb-perms (and packaged it into a .deb as an excercise) that can change them automatically whenever a device is plugged in, but started wondering if there is a more standard way of making Kamera usable in the user-land? - Jarno
