After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 655126 - Gnome terminal has poor error message when passed a bad filename
Gnome terminal has poor error message when passed a bad filename
Status: RESOLVED FIXED
Product: gnome-terminal
Classification: Core
Component: general
unspecified
Other Linux
: Low trivial
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
[fixed-gsettings]
Depends on:
Blocks:
 
 
Reported: 2011-07-22 14:35 UTC by Marc O'Morain
Modified: 2012-05-03 19:07 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Marc O'Morain 2011-07-22 14:35:30 UTC
When I try to load a gnome terminal session the program terminates immediately with a poor error message when the config file is not found.

I took me a while to debug what was going on. The error message is this:

marc@rodimus ~ $ gnome-terminal --load-config=marc
Failed to forward arguments: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code4: No such file or directory

gnome-terminal --version
GNOME Terminal 2.32.1
Comment 1 Marc O'Morain 2011-07-22 14:36:40 UTC
Edit poo => poor (unfortunate typo!)
Comment 2 Christian Persch 2011-07-26 12:08:09 UTC
Hmm. This is because this error domain isn't registered with gdbus. IMHO gdbus should register all gio error domains, or gio should expose a function doing so. -> gio
Comment 3 David Zeuthen (not reading bugmail) 2011-07-26 13:39:54 UTC
(In reply to comment #2)
> Hmm. This is because this error domain isn't registered with gdbus. IMHO gdbus
> should register all gio error domains, or gio should expose a function doing
> so. -> gio

No. We already provide transparent GError support without registering errors, see

 http://developer.gnome.org/gio/unstable/GDBusError.html#GDBusError.description

The problem is that you are not using it right - in particular you need to use g_dbus_error_strip_remote_error() before presenting any GError set by a GDBus routine.
Comment 4 Christian Persch 2011-07-26 13:48:46 UTC
Oh, ok. Thanks for the hint!
Comment 5 Christian Persch 2012-05-03 19:07:07 UTC
Fixed on master.