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 561663 - gnome-terminal crashes when gconf isn't set up correctly
gnome-terminal crashes when gconf isn't set up correctly
Status: RESOLVED FIXED
Product: gnome-terminal
Classification: Core
Component: general
unspecified
Other Linux
: Normal minor
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
fixed-2-24
: 558228 559451 559465 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-11-20 11:42 UTC by Pedro Villavicencio
Modified: 2009-04-25 23:31 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Pedro Villavicencio 2008-11-20 11:42:01 UTC
this report has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/gnome-terminal/+bug/298426

"Since upgrading to 2.24, I am unable to start gnome-terminal from my local pc via ssh

Basically, gnome-terminal does a fatal exit with the following error message:

$ ssh -Y user@host.local gnome-terminal
user@host.local's password:
**
ERROR:terminal-app.c:1525:terminal_app_init: assertion failed: (app->default_profile_id != NULL)
"

backtrace says:

"#0 0x00007f22b70df9c0 in abort () from /lib/libc.so.6
  • #1 g_assertion_message
    from /usr/lib/libglib-2.0.so.0
  • #2 g_assertion_message_expr
    from /usr/lib/libglib-2.0.so.0
  • #3 terminal_app_init
    at terminal-app.c line 1525
  • #4 g_type_create_instance
    from /usr/lib/libgobject-2.0.so.0
  • #5 ??
    from /usr/lib/libgobject-2.0.so.0
  • #6 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #9 terminal_app_initialize
    at terminal-app.c line 1708
  • #10 main
    at terminal.c line 1242

Comment 1 Christian Persch 2008-11-20 12:05:14 UTC
I bet you do have

GConf Error: Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://www.gnome.org/projects/gconf/ for information.

in your ~/.xsession-errors.

The cause is that since 2.24, gconf uses dbus to locate the gconfd server. On the remote end, no dbus session bus is running and/or the dbus session bus address env var isn't set.
Comment 2 Christian Persch 2008-11-20 12:06:20 UTC
*** Bug 559465 has been marked as a duplicate of this bug. ***
Comment 3 Christian Persch 2008-11-20 12:06:32 UTC
*** Bug 559451 has been marked as a duplicate of this bug. ***
Comment 4 Christian Persch 2008-11-20 12:10:07 UTC
*** Bug 558228 has been marked as a duplicate of this bug. ***
Comment 5 Brian J. Murrell 2008-11-28 15:14:48 UTC
(In reply to comment #1)
> 
> The cause is that since 2.24, gconf uses dbus to locate the gconfd server. On
> the remote end, no dbus session bus is running and/or the dbus session bus
> address env var isn't set.

OK.  So what it the solution for the simple and common case of:

ssh -X remote gnome-terminal

then?
Comment 6 Markus Kanet 2008-12-13 07:31:07 UTC
I think i have a similar problem:
Installed GNOME 2.24.2 on Slackware 12.2. I am logged in as normal user and tried the following command:

gksu --sudo-mode --user root /usr/bin/gnome-terminal

I then get the following crash report:

Distribution: Slackware Slackware 12.2.0
Gnome Release: 2.24.2
BugBuddy Version: 2.24.2

System: Linux 2.6.27.7-smp #2 SMP Thu Nov 20 22:32:43 CST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10502000
Selinux: No
Accessibility: Disabled
GTK+ Theme: (null)
Icon Theme: (null)

Memory status: size: 24817664 vsize: 24817664 resident: 8929280 share: 7331840 rss: 8929280 rss_rlim: 18446744073709551615
CPU usage: start_time: 1229152317 rtime: 12 utime: 10 stime: 2 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-terminal'

[Thread debugging using libthread_db enabled]
[New Thread 0xb6d74700 (LWP 2973)]
0xb793214e in __waitpid_nocancel () from /lib/libpthread.so.0

Thread 1 (Thread 0xb6d74700 (LWP 2973))

  • #0 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 run_bug_buddy
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 bugbuddy_segv_handle
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 raise
    from /lib/libc.so.6
  • #7 abort
    from /lib/libc.so.6
  • #8 g_assertion_message
    from /usr/lib/libglib-2.0.so.0
  • #9 g_assertion_message_expr
    from /usr/lib/libglib-2.0.so.0
  • #10 terminal_app_init
  • #11 g_type_create_instance
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_object_constructor
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #16 terminal_app_initialize
  • #17 main
  • #0 __waitpid_nocancel
    from /lib/libpthread.so.0


----------- .xsession-errors (39 sec old) ---------------------
[01mSystem Tray Status Service ver. 2.0[0m
Copyright (c) 2001-8 Hewlett-Packard Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.
Got accel 65481, 0, 0
Got keycode 96
Got modmask 0
Got Event! 33, -1
Got Event! 33, -1
Got Event! 33, -1
(gnome-keyring-daemon-wrapper:2584): EggSMClient-WARNING **: Received XSMP SaveYourself message in state save-yourself-done: client or server error
--------------------------------------------------



Here is some output from .xsession-errors:

RROR:terminal-app.c:1525:terminal_app_init: assertion failed: (app->default_profile_id != NULL)
SSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSSFenstermanager-Warnung:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c00087 ()
Fenstermanager-Warnung:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Fenstermanager-Warnung:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2c00087 ()
Fenstermanager-Warnung:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.


If i start a gnome-terminal as normal user and then run the gksu-command again then gnome-terminal does open but without being root.

When using terminal from xfce4 instead of gnome-terminal everything works like expected (getting a terminal with being root).

Markus
Comment 7 Christian Persch 2008-12-13 12:48:32 UTC
See bug 555745 and https://bugs.freedesktop.org/show_bug.cgi?id=17970 . 
Comment 8 Christian Persch 2008-12-15 18:41:39 UTC
The crash has been fixed; I'll open a new bug about what to do when gconf doesn't work.
Comment 9 Maxim Levitsky 2009-04-25 20:44:56 UTC
The fix for that bug made me be unable to start gnome-terminal.

If I manually revert:

  /* If the gconf daemon isn't available (e.g. because there's no dbus
   * session bus running), we'd crash later on. Tell the user about it
   * now, and exit. See bug #561663.
   */
  /*if (!gconf_ping_daemon ())
    {
      g_printerr ("Failed to contact the GConf daemon; exiting.\n");
      exit (1);
    }*/

Then it works just fine.

Comment 10 Christian Persch 2009-04-25 21:13:52 UTC
Bug 564649 has been filed to fix this problem. (Please don't add comments to closed bugs, they'll get lost. Don't re-open this bug, either.)
Comment 11 Maxim Levitsky 2009-04-25 23:31:36 UTC
No problem