Quick and fairly simple quesiton that I'm afraid may not have a simple answer.

Is using the "kdesudo" command to open a gui application safe to use, or will it cause problems? The reason I ask is because of all the terminal output which occurs after using this command.
for instance, here is just a small sample of what the terminal gives after receiving "kdesudo dolphin"

Code: Select all

 person@computer:~$ kdesudo dolphin
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
"/org/freedesktop/UDisks2/drives/HL_DT_ST_DVDRAM_GSA_U20N_M12988H0802" : property "Drive" does not exist
"/org/freedesktop/UDisks2/drives/HGST_HTS725050A7E630_TF0500Y9KLEGWC" : property "Drive" does not exist
"/org/freedesktop/UDisks2/drives/HGST_HTS725050A7E630_TF0500Y9KLEGWC" : property "DeviceNumber" does not exist
"/org/freedesktop/UDisks2/drives/HGST_HTS725050A7E630_TF0500Y9KLEGWC" : property "Device" does not exist
dolphin(10311) KSambaSharePrivate::findSmbConf: KSambaShare: Could not find smb.conf!
dolphin(10311)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(10311)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
qdolphin(10311)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(10311)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(10311)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(10311)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(10311)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
dolphin(10311)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:


None of this seems to indicate immediate danger to me, but I'm self-admitedly NOT anything, even remotely resembling, a linux expert. Even if this particular info isn't troubling, I've seen quite a variety of different messages put out after using the kdesudo command.

Can using kdesudo cause problems down the line? Are there specific situaitons it should/should not be used for? Thanks in advance for any info or advice!

This output is harmless and you can ignore it. Using kdesu to run programs as root is about as "unsafe" as running applications as root inherently is

Greetings

make sure you use kdesu and not sudo, as you might get file permission problems

Thanks for the replies! I really appreciate a nice definitive answer

It must be my OCD tendencies.. but is there a good resource I where could I learn more about what these messages mean, and how I could possibly get rid of/solve some of them?

I'm afraid i'm not aware of any resource - whether a message has any meaning will depend on what it is. Most warning messages tend to be worded as such though. In terms of getting rid of some of them, you can use "kdebugdialog" to silence most of the debug output (unfortunately not all output is classified correctly, and some doesn't go via the system which allows it to be silenced).

Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
failed connection to a signal, see http://qt-project.org/doc/qt-5.0/qtcore ... ml#connect

"/org/freedesktop/UDisks2/drives/HL_DT_ST_DVDRAM_GSA_U20N_M12988H0802" : property "Drive" does not exist
"/org/freedesktop/UDisks2/drives/HGST_HTS725050A7E630_TF0500Y9KLEGWC" : property "Drive" does not exist
"/org/freedesktop/UDisks2/drives/HGST_HTS725050A7E630_TF0500Y9KLEGWC" : property "DeviceNumber" does not exist
"/org/freedesktop/UDisks2/drives/HGST_HTS725050A7E630_TF0500Y9KLEGWC" : property "Device" does not exist
don't know, maybe solid or something missing some metadata on hard disk drives

dolphin(10311) KSambaSharePrivate::findSmbConf: KSambaShare: Could not find smb.conf!
missing config file for Samba -- just a debug message probably telling defaults are used instead

dolphin(10311)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig:
a message indicating that a configuration was flushed to the config file

So, all sort of irrelevant except maybe the first two, which indicate a bug in some program.