GrapefruiTgirl

[Log in to get rid of this advertisement]

Well I have marked this thread as "UNsolved".

This crap persists. I just wiped /tmp again, no luck. For the life of me I cannot start a root konqueror right now.
I just rebooted, to no avail.

I cannot WAIT until KDE4 (read: it's background processes, as I'm using XFCE again) is at least as usable as KDE-3.5.4 was.

too many freakin' daemons running around, none of them with their &%$#*@ heads on right.

I've reloaded messagebus, restarted kdeinit & kdeinit4, kill -HUP kdesud.. Can't just su to root and start Konqueror directly, because it complains about $DISPLAY not being set. If I set $DISPLAY, it tells me it can't connect to X server on $DISPLAY and the odd time it pretends it's gonna 'connect', it quits, telling me DCOP_server session is missing. Can't win here.

gankoji

the only way you can do that is if you run konsole or some other terminal emulator from within your current X session. so if you are on your XFCE desktop, hit alt+F2 and type konsole (or maybe xterm if you feel like not using kde's crap). then su, then konqueror. should do the trick!

GrapefruiTgirl

Nope -- did exactly as you suggested:

Alt+F2 > `konsole` > `kdesu ...` = failed
Alt+F2 > `kdesu ...` = failed
Alt+F2 > `xterm` > `kdesu ...` = failed
Alt+F2 > `xterm` > `konqueror ...` = failed

Generally, I'd like to think that by this long investigating a proble,, I'd have a reasonably good idea where the problem is occurring, but I'm stumped -- especially with the inconsistencies of it working on occasion, but not usually.

Thanks for the added input, gankoji!

Sasha

GrapefruiTgirl

The above is among the changes in the -current tree's latest changes/additions. While I haven't a clue why nobody else seems to be having this trouble, **maybe** that patch will do something

Maybe I need to wipe the partition, and reinstall the whole thing again, instead of upgrading.. That should fix it if this is due to screwy configuration, package overlap, or similar oddities.

Sasha

matti3

dude, thanks a ton! I was having kdesu troubles and that did the trick!

GrapefruiTgirl

matti,

let us know if your troubles stay gone for good; mine are still here, and sadly, I've just adapted to them :\

1) kdesu
2) hit enter a couple times
3) enter password, get rejected, close dialog box
4) kdesu
5) hit enter at least once with no password
6) enter password, get accepted, hope application starts
7) if application didn't start, return to (4) and repeat

matti3

hi,

i'm afraid i won't be of much help. I stumbled upon this thread through a google search on how to solve kdesu trouble. I guess my case is totally different (I even didn't fully get your problem as it seems to be detailed on other forum posts), but it happened to be solved through the advise found in this thread. sorry to disappoint you, my problem is fully solved, but it was probably not really related to yours. When I launched kdesu, simply nothing happened. that was my problem now everything still works after removing the /tmp files.

cheers
matthias

GrapefruiTgirl

Since fully re-installing virtually my entire system on top of itself in one shot, rather than running the previously rsynced situation I had been running during the process of upgrading & testing -current, I can now confirm that `kdesu` is working as it should

So, I must have had some slight mess with some packages or libs, perhaps due to slight overlap/underlap of packages while maintaining the system via rsync. Don't really know for sure, but it's now working!

I wish to thank everyone who contributed thoughts and information during the course of this thread: Thanks!

Cheers!
Sasha

matti3

lol, I'm glad for you, congrats! =)