Bug 45883 - kdesu konqueror fails kde 3.0.2
Summary: kdesu konqueror fails kde 3.0.2
Status: RESOLVED DUPLICATE of bug 51381
Alias: None
Product: kdesu
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdesu bugs tracker
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-07-29 00:18 UTC by salmankhilji
Modified: 2008-06-18 23:00 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description salmankhilji 2002-07-29 00:03:35 UTC
(*** This bug was imported into bugs.kde.org ***)

Package:           konqueror
Version:           KDE 3.0.2 
Severity:          normal
Installed from:    SuSE RPMs
Compiler:          gcc 2.95.3
OS:                Linux
OS/Compiler notes: SuSE provided rpms

Someone suggested to me that I file a new bug report for this.  So here it goes again.  BTW I know of at least one more guy on the SuSE mailing list who had this problem and went back to usign SuSE 7.3 with the older versio of KDE.

This problem was report earlier but was closed without being resolved.  
I have KDE 3.0.2 and I still have this problem.  Basically I do kdesu 
konqueror----enter my password---but nothing happens.

This problem creeped up recently in my system---after trying to 
install and uninstall Ratinal Rose for Linux and wiping out everything in 
/tmp folder.  I let KDE recreate mcop* kde* directories in /tmp.  I never 
had this problem with version 3.0 or 3.0.1.  I you cannot recreate this 
problem wipe out everything in /tmp and let KDE recreate some required 
folders in /tmp automatically.

NOTE:  This problem occurs only with kdesu konqueror....other 
applicatios like kdesu xemacs work just fine.

I tried using sux and no luck.  Here is the output from sux

skhilji@linux:~ sux
Password:
linux:/home/skhilji # /opt/kde3/bin/konqueror
DCOPServer up and running.
mcop warning: user defined signal handler found for SIG_PIPE 
overriding
/tmp/mcop-skhilji is not owned by user
linux:/home/skhilji # 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.
sh: dcopserver_shutdown: command not found

linux:/home/skhilji #







Now try it with kdesu -t konqueror:

skhilji@linux:~ kdesu -t konqueror
PATH 
:/sbin:/usr/sbin:/usr/local/bin:/usr/bin:/usr/X11R6/bin:/bin:/usr/games:/opt/gnome/bin:/opt/kde3/bin:/opt/kde2/bin:/usr/lib/java/bin:/opt/gnome/bin:/usr/lib/qt-3.0.3/bin:/opt/Komodo-1.2
 before forking
_IceTrans
Open: Unable to Parse address none
Session management error: Could not open network socket

DCOPServer up and running.
_IceTransOpen: Unable to Parse address none
Session management error: Could not open network socket
mcop warning: user defined signal handler found for SIG_PIPE 
overriding

/tmp/mcop-skhilji is not owned by user
skhilji@linux:~



I once deleted the /tmp/mcop-skhilji directory.  This seemed to fix 
the problem.  But when I restarted KDE I got errors about the sound/arts 
stuff not found.  After KDE recreated /tmp/mcop-skhilji automatically 
I again was never able to do kdesu konqueror anymore.






(Submitted via bugs.kde.org)
Comment 1 Maurizio Avogadro Di Cerrione 2002-08-13 23:57:16 UTC
It seems that setting the env variable LOGNAME to root solves this 
issue. I also had the same problem: KDE 3.0.2 since I cleaned my /tmp 
directory by removing kde-*/ ksocket-*/ mcop-*/ and .ICE-unix/ I 
couldn't start kdesu konqueror anymore.

Now I'm starting 'kdesu konqueror-root' where 'konqueror-root' is a 
script as follows:

#!/bin/bash
export KDEHOME=/root/.kde3
export USER=root
export BASH_ENV=/root/.bashrc
export GTK_RC_FILES=/etc/gtk/gtkrc:/root/.gtkrc:/root/.gtkrc-kde
export GS_LIB=/root/.kde3/share/fonts
export LOGNAME=root # <-- THIS IS WHAT IS REALLY NEEDED!
exec /opt/kde3/bin/konqueror 2>/dev/null >/dev/null

I specified all the other variables because I noticed that some apps 
started by kdesu were chowning the settings in my ~/.kde3/share/config 
directory so that they couldn't read and modify their own settings when 
I tried to run them as user (i.e: kppp started with only the button 
"cancel" active kedit didn't start at all).

Hope this will be useful.

Bye - Mau
Comment 2 salmankhilji 2003-07-22 02:59:23 UTC
Subject: Re:  kdesu konqueror fails kde 3.0.2         

This bug has been fixed in KDE 3.1.1.

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

Comment 3 Maksim Orlovich 2003-07-22 03:46:33 UTC
Indeed, thank you for noting. #51381 has the patch, closing info, etc., so I'll 
merge this into there. 
 

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