Latest updates failures [Solved]

[NoSavy]

OK. Have tried reinstalling a host of files, D-bus,dolphin.etc. and no joy.
If I use dolphin as user I can open a lot of the files in the root directories /etc/ /usr etc. but obviously they are not editable.
From this I assume it must be a permission problem of sorts.

I will try 'genfools' suggestion this evening.

NS.

[NoSavy]

Tried genfools' suggestion and still not working.

It's obviously a kde thing! because if I open pc-manfm file manager and then open a folder as root I can then click on a file and it opens for editing.

Have tried a lot of other things and no go. Any more suggestions please. I also notice that after the first attempt to open a file the D-bus-daemon hogs the CPU with excessive use and massive temperature rise until I kill it.

Thanks,

NS.

Edit. DOES THIS HELP ANYBODY.
I open a konsole as user, change to root with su command, enter "export $(dbus-launch)" then "dolphin". Dolphin then opens OK as root and the files open and are editable.
NS.

[NoSavy]

Bump: Has nobody any ideas on this, please.?

NS.

[NoSavy]

Fitzcarraldo, you have offered good help in the past and I now see you referred to as "The 1337357 Gentoo Wizard".
Please, have you or anyone any suggestions on my problem, as in original post.
"Unable to open file files in root dolphin."

I can:- Open a konsole as user, change to root with su command, enter "export $(dbus-launch)" then "dolphin". Dolphin then opens OK as root and the files open and are editable.

Attempting from a normal dolphin causes the dbus-daemon to hog the processor and not free itself until I kill it, then other root apps fail.ie konsole.

Questions!

Can I remove purge all dbus files and reinstall from a console before entering KDE? --- if so how?
Can I remove and purge and reinstall console kit before entering KDE? --- if so how?

Failing these last ideas I might have to do a fresh install. Final question is, are daily ISO's still available upto date.

Hoping and thanks for reading.

NS.

[sabayonino]

like we wrote ...

use kdesu or sudo

Open a text file with kwrite...

Code: Select all

kdesu kwrite /path/file/text/to/open

Open Dolphin

Code: Select all

kdesu dolphin

View a pdf as root (it's stupid I Know...)

Code: Select all

kdesu okular /path/to/pdf/file

etc...

you can run any applications with kdesu/sudo command

I know . you would like to open averything using dolphin but you can't

[Fitzcarraldo]

I haven't had time to upgrade to KDE 4.6.2 yet (I'm still using KDE 4.6.1) but, when I launch Dolphin using kdesu dolphin from a Konsole window and browse to /var/log/ and click on any log file, the log file opens in KWrite. So, if that is not happening in KDE 4.6.2, it's either a functional change by the KDE developers or there is some other issue. I'm very busy at the moment, but I'll try to upgrade in the new few days and see what happens on my main laptop (Portage only). (And, NoSavy, I'm most certainly not "The 1337357 Gentoo Wizard". I might be "The 1337357 Google Wizard", though, as I do have a remarkable Google-fu. )

[NoSavy]

Thanks Fitzcarraldo, much appreciated.

You have it exactly.
(when I launch Dolphin using kdesu dolphin from a Konsole window and browse to /var/log/ and click on any log file, the log file opens in KWrite) That is what always worked prior to the update but fails since the update with the errors mentioned.
I will wait awhile to see if it can be solved.

Thanks Sabayonino,
But using your method kdesu kwrite /path/file/text/to/open does not work. I know it should, but it doesn't.

WHY does the dbus-daemon hog the processor, that is the real question? It shouldn't. It never did.

Thanks again.
NS.

[sabayonino]

Thanks Fitzcarraldo, much appreciated.



WHY does the dbus-daemon hog the processor, that is the real question? It shouldn't. It never did.

Thanks again.
NS.

I think that is security reason to deny any root operations using "X"-applications ... or some configuration broken in your system ... I don't know

In my sabayon and gentoo kdesu-->dolphin-->click-text-file-->kwrite show me contents

for me it works

[NoSavy]

For curiosity I logged into my 32bit Sabayon which was working perfectly with KDE 4.5
I then ran the update procedure to get it up todate with KDE 4.6.2

Now I cannot open files in root Dolphin. EXACTLY the same problems as detailed in my other posts, including the dbus-daemon hogging the CPU.
So upgrading a 64bit system and a 32bit system to KDE 4.62 borks something to do with DBUS.

It's not a KDE 4.6.2 feature as it is working on other systems running 4.6.2

Surely it can't be me. !!!

NS.

[Fitzcarraldo]

Just finished upgrading from KDE 4.6.1 to 4.6.2 via Portage (232 packages merged in 3 hours 25 minutes) and it works OK. I can launch Dolphin as root by using kdesu dolphin, and when I browse to /var/log/ and click on one of the log files it opens in KWrite.

This is what I see in a Konsole when I run kdesu dolphin from the command line:

Code: Select all

$ kdesu dolphin
kdesu(8672)/kdesu (kdelibs) KDESu::PtyProcess::exec: [ /var/tmp/portage/kde-base/kdelibs-4.6.2-r2/work/kdelibs-4.6.2/kdesu/process.cpp : 293 ]  Running "/bin/su"
kdesu(8672)/kdesu (kdelibs) KDESu::SuProcess::ConverseSU: [ /var/tmp/portage/kde-base/kdelibs-4.6.2-r2/work/kdelibs-4.6.2/kdesu/su.cpp : 259 ]  Read line "Password: "
kdesu(8672)/kdesu (kdelibs) KDESu::PtyProcess::exec: [ /var/tmp/portage/kde-base/kdelibs-4.6.2-r2/work/kdelibs-4.6.2/kdesu/process.cpp : 293 ]  Running "/bin/su"
kdesu(8672)/kdesu (kdelibs) KDESu::SuProcess::ConverseSU: [ /var/tmp/portage/kde-base/kdelibs-4.6.2-r2/work/kdelibs-4.6.2/kdesu/su.cpp : 259 ]  Read line "Password: "
kdesu(8672)/kdesu (kdelibs) KDESu::PtyProcess::WaitSlave: [ /var/tmp/portage/kde-base/kdelibs-4.6.2-r2/work/kdelibs-4.6.2/kdesu/process.cpp : 379 ]  Child pid 8677
kdesu(8672)/kdesu (kdelibs) KDESu::SuProcess::ConverseSU: [ /var/tmp/portage/kde-base/kdelibs-4.6.2-r2/work/kdelibs-4.6.2/kdesu/su.cpp : 259 ]  Read line ""
kdesu(8672)/kdesu (kdelibs) KDESu::SuProcess::ConverseSU: [ /var/tmp/portage/kde-base/kdelibs-4.6.2-r2/work/kdelibs-4.6.2/kdesu/su.cpp : 259 ]  Read line "kdesu_stub"
kdesu(8672)/kdesu (kdelibs) KDESu::PtyProcess::exec: [ /var/tmp/portage/kde-base/kdelibs-4.6.2-r2/work/kdelibs-4.6.2/kdesu/process.cpp : 293 ]  Running "/bin/su"
kdesu(8672)/kdesu (kdelibs) KDESu::SuProcess::ConverseSU: [ /var/tmp/portage/kde-base/kdelibs-4.6.2-r2/work/kdelibs-4.6.2/kdesu/su.cpp : 259 ]  Read line "Password: "
kdesu(8672)/kdesu (kdelibs) KDESu::PtyProcess::WaitSlave: [ /var/tmp/portage/kde-base/kdelibs-4.6.2-r2/work/kdelibs-4.6.2/kdesu/process.cpp : 379 ]  Child pid 8682
kdesu(8672)/kdesu (kdelibs) KDESu::SuProcess::ConverseSU: [ /var/tmp/portage/kde-base/kdelibs-4.6.2-r2/work/kdelibs-4.6.2/kdesu/su.cpp : 259 ]  Read line ""
kdesu(8672)/kdesu (kdelibs) KDESu::SuProcess::ConverseSU: [ /var/tmp/portage/kde-base/kdelibs-4.6.2-r2/work/kdelibs-4.6.2/kdesu/su.cpp : 259 ]  Read line "kdesu_stub"

I suggest you file a bug report in the SL Bugzilla, NoSavy, because it looks like your problem may be specific to the Entropy packages environment. However, if sabayonino also uses Entropy, rather than Portage, in his SL installation then that may not be the case.