When I try to gedit some files, then I received these from the terminal window. There is already one post about this: Gtk-WARNING : Calling Inhibit failed
But it is not solved. How can I solve it ? 
-
I'd very much like to know how to stop gtk warnings from all apps entirely.– jozxyqkFeb 15, 2014 at 2:52
-
1Possible duplicate of Why are there so many console messages from GTK+ applications?– mchidApr 26, 2016 at 9:20
Add a comment
|
3 Answers
To solve
IBUS-WARNING **: The owner of /home/myPC/.config/ibus/bus is not root!
use gksudo or gksuinstead of sudo to open the file,
gksudo gedit php.ini
or
gksu gedit php.ini
The next error
(gedit:12512): Gtk-WARNING **: Calling Inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
can be solved by updating gir1.2-gtksource-3.0
sudo apt-get install gir1.2-gtksource-3.0
-
10Lubuntu 14.04 comes with gir1.2-gtksource-3.0 but I still get the "Calling Inhibit failed" warning from Gedit 3.10.4. Apr 22, 2014 at 12:10
-
-
"Calling inhibit failed" still happens on 14.04.3 LTS
apt-get dist-upgraded on January 2016. The suggestedapt-get install gir1.2-gtksource-3.0is not necessary because the system would already be up to date.– H2ONaClJan 2, 2016 at 5:44 -
Three comments above still valid under 16.04.2 LTS on July 30, 2017. Jul 30, 2017 at 19:35
There is another way to not deal with such warnings. Use graphical frontend for sudo/su - gksu (in case of gnome) for running GUI programs as root. Gtk-WARNING : Calling Inhibit failed
-
The "calling inhibit failed" warning still happens if you use
gksudo geditwhich I understand is the same asgksu gediton some systems.– H2ONaClJan 2, 2016 at 5:38
When starting an application from the command line, you can avoid verbose output in the terminal after starting the application by using the NOHUP flag before the command and an ampersand following the command.
For example, in this instance you would use:
nohup gedit &
or
nohup gedit
If you need sudo permission, you should use sudo -i instead of sudo to prevent other problems like so:
nohup sudo -i
