Sudo gedit error

Question

** (gedit:8315): CRITICAL **: file log.c: line 980: unexpected error: Error calling StartServiceByName for org.gnome.zeitgeist.Engine: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/bin/zeitgeist-daemon exited with status 1 (g-dbus-error-quark, 25)

It works alright if I do gksu gedit.

Don't open gui application through sudo. – Avinash Raj Jun 01 '14 at 05:10 — Avinash Raj, Jun 01 '14 at 05:10
Use nano or vim for such tasks. – LiveWireBT Jun 01 '14 at 12:33 — LiveWireBT, Jun 01 '14 at 12:33

score 5 · Answer 1 · edited Apr 13 '17 at 12:23

5

First you should read this Why should users never use normal sudo to start graphical applications?

But you should be able to start gedit using sudo -H gedit

While searching I found similar problem reported here.

A bug is reported there "Ubuntu 13.10 "gedit" fails every time unless user removes zeitgeist directory."

So running this command

rm ~/.local/share/zeitgeist -R

seems to solve the issue.

edited Apr 13 '17 at 12:23

Community

1

answered Jun 01 '14 at 06:38

Bibi424

618
6
13

I confirmed this worked for me on Ubuntu 14.04. I was not using "sudo", just trying to lauch gedit. – Mark Stosberg Aug 15 '14 at 16:50

Pandya · Answer 2 · 2014-06-01T08:28:18.580

gksu is a frontend to su and gksudo is a frontend to sudo. Their primary purpose is to run graphical commands that need root without the need to run an X terminal emulator and using su directly.

To open GUI application from terminal use gksu or gksudo as following:

gksudo gedit

If gksu not installed then first install by sudo apt-get install gksu.

However It is recommended to run command-line as root and Don't run GUI apps as root.

Sudo gedit error

2 Answers2