Suse 7.1 kernel 2.4.17 kde 2.2.2 XF86 4.2 Small problem. I keep breaking Klauncher forcing me to log out then back in to KDE. For example Kwintv (rpm from suse) asks to be suid root. But causes this. gringo@gringo:~ $kwintv The KDE libraries are not designed to run with suid privileges. gringo@gringo:~ $kdeinit: Fatal IO error: client killed kdeinit: sending SIGHUP to children. KLauncher: Exiting on signal 1 kdeinit: sending SIGTERM to children. kdeinit: Exit. It does not like to be run as User. However it will work with sux -but also breaks klauncher. As user I get kv4lsetup: You should install me suid root, I need root priviliges for the VIDIOCSFBUF ioctl. Warning: kwintv: kv4lsetup had some trouble, trying to continue anyway. Is there a way of restoring klauncher ? If I stop and start klauncer it has no affect. The usual message is "klauncher could not be reached via DCOP" I have a similar problem with kfontinsall Brian Marr
On Wed, 17 Apr 2002, Brian Marr wrote:
Is there a way of restoring klauncher ? If I stop and start klauncer it has no affect.
run kdeinit for that.
The usual message is "klauncher could not be reached via DCOP"
I have a similar problem with kfontinsall
To run KDE 2 apps under KDE 3 you need the kde2-compat package. But you have no KDE 2 desktop afterwards anymore. bye adrian ********************************************************************** Adrian Schroeter SuSE AG, Deutschherrnstr. 15-19, 90429 Nuernberg, Germany email: adrian@suse.de (1382 mails already received today.)
* Adrian Schroeter (adrian@suse.de) [020416 14:33]: ::On Wed, 17 Apr 2002, Brian Marr wrote: ::> Is there a way of restoring klauncher ? If I stop and start klauncer it has ::> no affect. :: ::run kdeinit for that. :: ::> The usual message is "klauncher could not be reached via DCOP" ::> ::> I have a similar problem with kfontinsall :: ::To run KDE 2 apps under KDE 3 you need the kde2-compat package. But you ::have no KDE 2 desktop afterwards anymore. This is odd. I use Licq, Kinkatta and a few other apps under KDE3 from KDE2, but I don't have the compat RPM installed. I'm using the pkgs that were first released on ftp.kde.org. Are these two apps not concidered true KDE apps..just QT apps? -=Ben --=====-----=====-- mailto:ben@whack.org --=====-- "I've never been quarantined. But the more I look around the more I think it might not be a bad thing." -GC --=====-----=====--
Hi Ben, :) On Tue, 16 Apr 2002, Ben Rosenberg wrote:
* Adrian Schroeter (adrian@suse.de) [020416 14:33]: ::On Wed, 17 Apr 2002, Brian Marr wrote: ::> Is there a way of restoring klauncher ? If I stop and start klauncer it has ::> no affect. :: ::run kdeinit for that. :: ::> The usual message is "klauncher could not be reached via DCOP" ::> ::> I have a similar problem with kfontinsall :: ::To run KDE 2 apps under KDE 3 you need the kde2-compat package. But you ::have no KDE 2 desktop afterwards anymore.
This is odd. I use Licq, Kinkatta and a few other apps under KDE3 from KDE2, but I don't have the compat RPM installed. I'm using the pkgs that were first released on ftp.kde.org.
Are these two apps not concidered true KDE apps..just QT apps?
Well, it can work, if you really started kdeinit & dcopserver from KDE 3 before (happened during the KDE start, but you are in trouble, if you start first a KDE 2 application under any other windowmanager and start a KDE 3 application afterwards) and the KDE 2 application does not miss any extra data (since it uses /opt/kde3/share/apps and not /opt/kde2/share/apps/) And kdesu can lead into a kdeinit suicide (happened here I guess). So it might work, but it is definitive not sure for all apps or enviroments. bye adrian ********************************************************************** Adrian Schroeter SuSE AG, Deutschherrnstr. 15-19, 90429 Nuernberg, Germany email: adrian@suse.de (1395 mails already received today.)
* Adrian Schroeter (adrian@suse.de) [020416 15:00]: :: ::Well, it can work, if you really started kdeinit & dcopserver from KDE 3 ::before (happened during the KDE start, but you are in trouble, if you ::start first a KDE 2 application under any other windowmanager and start a ::KDE 3 application afterwards) and the KDE 2 application does not miss any ::extra data (since it uses /opt/kde3/share/apps and not /opt/kde2/share/apps/) ::And kdesu can lead into a kdeinit suicide (happened here I guess). :: ::So it might work, but it is definitive not sure for all apps or ::enviroments. Ahhh..I get it. Yep. It's happened to me then. I was in KDE3 and started Kups to add a new printer to my workstation in the office and BAM! nothing KDE3 would start after that. I got errors in the KControl Centre and in Konq. I had to exit from KDE3 and restart. Now I know what the deal is. Interesting. Thanks! -=Ben --=====-----=====-- mailto:ben@whack.org --=====-- "I've never been quarantined. But the more I look around the more I think it might not be a bad thing." -GC --=====-----=====--
participants (3)
-
Adrian Schroeter -
Ben Rosenberg -
Brian Marr