(gedit:3366): IBUS-WARNING **: The owner of ~/.config/ibus/bus is not root!

[dino99]

This is "Won't Fix" because it is the symptom of a user error.

As indicated repeatedly in the comments below, you should not use "sudo gedit" (or if you do, you should be able to live with this error message).

The proper way to run a GUI tool with elevated privileges is with sudo -i or gksudo.

Original problem description follows.

--------------------------------------------

RR i386 logged as gnome-classic (fallback)

Seen that error for the first time while using a terminal:

oem@oem-desktop:~$ sudo gedit /etc/default/grub

(gedit:3366): IBUS-WARNING **: The owner of /home/oem/.config/ibus/bus is not root!

That one is own by "Me" (screenshot joined)

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: ibus 1.4.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-6.13-generic 3.8.0-rc7
Uname: Linux 3.8.0-6-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.8-0ubuntu4
Architecture: i386
Date: Fri Feb 15 08:33:36 2013
MarkForUpload: True
SourcePackage: ibus
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[microsome (mpkummer)]

Got the same error message opening fstab as root.

[Nikki1993 (nikki-icekronik)]

I don't think this bug related to Gedit, more like an iBus problem. I get this issue every time I am trying to start application with "sudo".

[Nikki1993 (nikki-icekronik)]

Ops, sorry my bad. I read header title but not to what package bug assigned to :)

[microsome (mpkummer)]

I deleted the folder /home/[user]/.config/ibus/bus and the problem was gone!

[Mauro (jasmines)]

Great! Worked here too!

[microsome (mpkummer)]

Just as an add-on: the folder is afterwards generated again with root privileges.

[Kyle Coots (kylecoots83)]

Had the same issue after updating from 12.10 x64 to 13.04 x64.
Distributor ID: Ubuntu
Description: Ubuntu 13.04
Release: 13.04
Codename: raring

The solution given by @microsome above worked, thanks!

[Mauro (jasmines)]

Not a solution, because if you run gedit from terminal with your user (not with sudo), you get:

IBUS-WARNING **: The owner of /home/[user]/.config/ibus/bus is not [user]!

[markling (markling)]

Please also see my ubuntu-bug report for gedit here: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1189095

Issue occured for me in very specific circumstances: attempt to run two sudo gedit commands running simultaneously. The second failed with the error: (gedit:3214): IBUS-WARNING **: The owner of /home/username/.config/ibus/bus is not root!

It failed in the sense that gedit did not open.

It may have been significant that a related command was already running in another terminal (xfce4-terminal 0.6.1) window: sudo iptables -L > iptables_rules_.txt

This comand takes a while to chug through its output. So gedit, or whatver, was already occupied.

While that was happening, I had issued another sudo gedit command in another terminal window: sudo gedit /etc/firewall.bash

It was that comand reported the above-quoted error.

The failed sudo gedit command was resissued after the first had finished. Gedit opened the (new) file this time. It appeared, in other words, to have worked. It nevertheless repeated the error: "(gedit:3301): IBUS-WARNING **: The owner of /home/username/.config/ibus/bus is not root!". The file meanwhile, was edited and saved without a problem.

Xubuntu 13.04 i686

[Ma Hsiao-chun (mahsiaochun)]

The reason for this bug is that when you start gedit or so IM module from IBus got loaded. As you do "sudo", the user of IM module would be "root".

However, the ibus-daemon is started by the normal user in most cases, which would create ~/.config/ibus/bus if it doesn't exists.

IIRC, this is the limitation of current D-Bus technology that two processes having different user (uid) cannot communicate. The warning is just the superfacial representation of it.

[Musa Ibraheem (musa-ibraheem)]

The package "gksu" wasn't a default part of my 13.04 installation, to my surprise. Once I installed it, this problem went away. "dpkg" really seems to have some strange settings in this version of Ubuntu.

[Drew Trott (druid-well)]

I'm getting this error when running gedit as sudo, but as far as I can tell the error doesn't affect functionality. That is, gedit seems to work normally; the file is successfully opened, modified, and saved.

[Ｖ字龍(Vdragon) (vdragon)]

I don't this it is an issue, you **should** execute any application which will write files in your home directory by sudo -i/gksudo/kdesudo

Running <application name> as root with HOME environmental variable still points to your own HOME directory will make <application name> create files in your home directory which, of course can't be modified later if you run <application name> by YOURSELF and cause problem.

The problem, in particular, you may break your application or even the entire X session!

[Ｖ字龍(Vdragon) (vdragon)]

Fix typos, ambiguous text in #15
>>>>
I don't think it is an issue, you **should** execute any application which will write files in your home directory by sudo -i/gksudo/kdesudo

Running <application name> as root with HOME environmental variable still points to your own HOME directory will make <application name> create files **as root:root** in your home directory which, of course can't be properly accessed later if you run <application name> by YOURSELF and cause problem.

The problem, including but not limited to, you may break your application or even the entire X session!
<<<<

[Baditaflorin (baditaflorin)]

THe same in Ubuntu 13.10

sudo gedit /etc/sysctl.d/10-console-messages.conf

(gedit:3237): IBUS-WARNING **: The owner of /home/vivi/.config/ibus/bus is not root!

Everythings works, just that i get this message

[Aron Xu (happyaron)]

This isn't a bug, the behavior is expected as the GTK+ application is launched with root privilege but the session is run using another user. So it warns that the owner of ibus's configuration file isn't root, and it's only a warning.

[efonde (efonde)]

I'll presume it is safe to ignore the warning.
I get this warning if I run with "sudo" command but not with "gksu" command.

[manish (computronicsgorai)]

IBUS-WARNING **: The owner of /home/oem/.config/ibus/bus is not root! appear

[GeeMac (htpc2013)]

I hate to open an old wound, but..... This dates back to 2013-02-15.

(nautilus:5021): IBUS-WARNING **: The owner of /home/gee/.config/ibus/bus is not root!

(leafpad:8077): IBUS-WARNING **: The owner of /home/gee/.config/ibus/bus is not root!

(gedit:8112): IBUS-WARNING **: The owner of /home/gee/.config/ibus/bus is not root!

(medit:8161): IBUS-WARNING **: The owner of /home/gee/.config/ibus/bus is not root!

I would think that the easiest thing to do is to just prevent the warning from coming up at all since it is not a major issue.
Maybe easier said then done for a person that is not a Dev.
I was seeing this here quite a bit after I upgraded from 12.04 Quantal to 14.04 Trusty. I Googled the issue and here I am.

Folks when your opening a graphical interface such as the above, use "gksudo" instead of "sudo".

TC, Peace Out...

Before I forget....

Do you think that "Won't Fix" is going to float well with the standard users? That's just not right.

That is like someone that is suicidal; calling the suicide hotline, the call councillor picks up and then says "Please Hold"

Then the music on hold just happens to be, Eddie Van Halen's song "Jump"

[WinEunuchs2Unix (ricklee518)]

Van Halen's "Maxwell Jump" song is appreciated in comment #21.

I too received this error today. I was guilty of running two terminal sessions a day or two ago and I am guilty of using "gedit" one time and "sudo gedit" another time on the same file if permission is denied the first time.

Ubuntu 14.04 LTS, Kernel 3.15.6-blah blah-generic.

[Luis (xththx)]

I solved it.

gksudo nautilus

go to

~/.config/ibus/bus

Set up the owner, group as my user.

Propietary - (user)
Access - Create and delete
Group - (user)
Access - Access to files
others - Access to files

After that. The message disappeared.

The error is regards to opening graphical applications with sudo. To avoid this error in the future, just replace it with gksudo.

Regards.

Regards