Bus::open: Can not get ibus-daemon's address.

[bonkers]

I get this error pretty much on any cli operation I do along with a few others. I will present a scenario for you girls and guys to show my .

Step 1. I run dolphin as root >

rafal@rafal-desktop:~$ sudo -s -H
[sudo] password for rafal: 
root@rafal-desktop:/home/rafal# dolphin
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kbuildsycoca4 running...
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /root/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address. 
IBusInputContext::createInputContext: no connection to ibus-daemon 
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /root/.kde/share/config/activitymanager-pluginsrc
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
QSqlQuery::prepare: database not open
dolphin(2904) KSambaSharePrivate::findSmbConf: KSambaShare: Could not find smb.conf! 
kio_timeline(2993): Xapian Database does not exist at  "/root/.local/share/baloo/email/" 
kio_timeline(2993): Xapian Database does not exist at  "/root/.local/share/baloo/file/" 
kio_timeline(2993): Xapian Database does not exist at  "/root/.local/share/baloo/notes/" 
kio_timeline(2993): Xapian Database does not exist at  "/root/.local/share/baloo/contacts/" 
kio_timeline(2993): Xapian Database does not exist at  "/root/.local/share/baloo/calendars/" 
kio_baloosearch(3005): Xapian Database does not exist at  "/root/.local/share/baloo/email/" 
kio_baloosearch(3005): Xapian Database does not exist at  "/root/.local/share/baloo/file/" 
kio_baloosearch(3005): Xapian Database does not exist at  "/root/.local/share/baloo/notes/" 
kio_baloosearch(3005): Xapian Database does not exist at  "/root/.local/share/baloo/contacts/" 
kio_baloosearch(3005): Xapian Database does not exist at  "/root/.local/share/baloo/calendars/" 
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /root/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address. 
IBusInputContext::createInputContext: no connection to ibus-daemon 
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /root/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address. 
IBusInputContext::createInputContext: no connection to ibus-daemon 
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /root/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address. 
IBusInputContext::createInputContext: no connection to ibus-daemon 
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /root/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address. 
IBusInputContext::createInputContext: no connection to ibus-daemon

Once dolphin is open let's go look at some random .txt file for the fun of it. I decided to pick

/var/run/resolvconf/interface/NetworkManager , which is a .txt file. Inside it I find

search 8.8.8.8 8.8.4.4
nameserver 127.0.1.1

By the way, is that how this file should look? Anyway, what is what all those QDBus and IBus errors? Can this be somehow resolved?

[claydoh]

1. Don't run gui applications using sudo, use kdesudo, unless you want to have file ownerships change on your user files and configs, and limit those that you need to run as an Admin to a file manager and text editor. The vast majority of graphical program will have a proper password prompt when Admin permissions are needed.
2. Also, a portion of the terminal output you see here is directly from using sudo when running dolphin
3. Don't run gui applications using sudo, use kdesudo
4. Much of a terminal output when running a gui program is purely informational - unless you actually see the word "error", there is little to worry about, unless you are a developer (I thought there was a way to change the mostly useless parts of the output being displayed, but I have not yet found it)
5. Don't run gui applications using sudo, use kdesudo
6. ibus-daemon is a thing used to allow multilingual support (mainly Asian language). Programs are simply looking for ibus, not finding it, and moving on (see #3 )
7. Don't run gui applications using sudo, use kdesudo
8. The output you are seeing is normal, you are ok here, except:
9. Don't run gui applications using sudo, use kdesudo
10. If you want, you can run a gui program from krunner (alt-f2) using kdesudo dolphin and not see any extraneous output at all.
11. Don't run gui applications using sudo, use kdesudo

[bonkers]

Alright, I took your advice, and still I get strange output, if you have any more patience with me, could you please help, I am at a loss here.

rafal@rafal-desktop:~$ kdesudo dolphin
Bus::open: Can not get ibus-daemon's address. 
IBusInputContext::createInputContext: no connection to ibus-daemon 
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
kbuildsycoca4 running...
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /root/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address. 
IBusInputContext::createInputContext: no connection to ibus-daemon 
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave.
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /root/.kde/share/config/activitymanager-pluginsrc
Object::connect: No such signal org::freedesktop::UPower::DeviceAdded(QDBusObjectPath)
Object::connect: No such signal org::freedesktop::UPower::DeviceRemoved(QDBusObjectPath)

[Snowhog]

You always see this type of output when launching a graphical application from console. You got prompted for your password, yes, and then afterwards, Dolphin launched?

[SteveRiley]

Yeah but look at all that crap...some are warning messages, some are bugs. Like LibreOffice's malformed .desktop desktop files. Running GUI applications from a console is an easy debugging step that seems to elude many developers.

[paigestormblade]

Adding Convo, on subject is all

im not much of the dolphin, im used to the preview when you hover mouse over the items. i did use the file explore i think thats the name,

i felt it was more easier to work with for preview, im in a band and i like to hear files before i open them, but always having to right click to hear it so the one click don't open it, "yea i know i can change it but i like the one click open", but i hate how the browser is, it don't let you preview on all parts only some like when you open from program to import or open, really i may be wrong but i remember tying too open a file and couldn't see preview, i had to reopen the dolphin, just to see the item i wanted was the correct one i wanted to import or open ,

but hey all i started using kububtu at birth left linux land for a bit due to a illness i used to be a distributor for ku, wanted all my family on got sick of rip off microsoft.

but glad to be back on linux love it never trust windows it will steal ya key and lagg like a mother lol hehe

ku on my beast of a desktop well ahm 2011 it was, lol amd nvidia 630 2gb vid but really bad on the video, always lagging, the last update screwed it up i did find though using nvidia's files will lfix the discriipter pipe error but i do stress, remove that up date it rams the heck of of the settings makes it a lower frps. i feel the ku amd runs better on an Intel really for some reason, might be the vido card issue for why i feel that way , but just adding some convo

[claydoh]

i used to be a distributor for ku

Huh?

[paigestormblade]

kubuntu oie offered first timmer reseller pc builders

Huh?

first timmer reseller pc builders to sell pc with kubuntu years ago is what i meant i say ku for short