#43448 closed defect (invalid)
gedit @3.12.1_0+python33 Gtk-WARNING
| Reported by: | pier1994@… | Owned by: | dbevans (David B. Evans) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | ||
| Port: | gedit |
Description
Yesterday i ran the selfupdate and the upgrade for outdated ports, then every time i tried to run gedit (gedit or gedit &) and modify a file (also without saving or creating it if it's a new file) i get this warning:
(gedit:37297): Gtk-WARNING **: Calling Inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
and the terminal becomes unusable until I exit gedit and press ^C .
I'm on a macbook pro retina 15 with OSX 10.9.2, MacPorts 2.2.1 XQuartz 2.7.5 and Xcode 5.1.1.
Thank you!
Change History (4)
comment:1 follow-up: 2 Changed 10 years ago by dbevans (David B. Evans)
| Keywords: | gtk gdbus gedit removed |
|---|---|
| Owner: | changed from macports-tickets@… to devans@… |
| Status: | new → assigned |
| Version: | 2.2.1 |
comment:2 Changed 10 years ago by pier1994@…
Replying to devans@…:
Please CC maintainer when submitting a ticket.
Sorry, i'm quite new here. Thank you for the advice!
comment:3 Changed 10 years ago by dbevans (David B. Evans)
| Resolution: | → invalid |
|---|---|
| Status: | assigned → closed |
The warning message is due to the fact that gnome-session is not running (optional) and is not a problem.
Concerning the terminal, if you start gedit from the command line like this
$ gedit
the program is running in the foreground and the terminal will be busy until the program exits.
If you run the program in the background
$ gedit &
then the terminal will not block but you will still see the warning output from the program. If this happens, entering CR should show you the command line prompt again.
If you don't want to be bothered by the warning messages you can start gedit with this command
$ gedit >& /dev/null &
The gedit program itself works fine for me. So closing this ticket as invalid (not a bug).
comment:4 Changed 10 years ago by pier1994@…
Ok, thank you for the tips. I thought that the fact that the warning started to appear only after the upgrade could be a problem. For what concerns the gnome-session, i tried to launch gedit after running it ( i set it up as the GNOME page on the site suggests) and the warning still comes out, but that's not a problem if i'll direct the std error output to /dev/null.
Thank you very much for the answer and your work!
Please CC maintainer when submitting a ticket.