gnome-terminal causes Xorg to close on livecd

[Haggai Eran]

Binary package hint: gnome-terminal

I'm running Lucid Alpha 3 from a USB stick. After the computer boots, I tried running gnome-terminal from the Alt-F2 run dialog. It immiediatly caused the X server to close. A few seconds later a new X server starts, and on that one I had no trouble running gnome-terminal.

I'm attaching the xserver log.

ProblemType: Bug
Architecture: amd64
Date: Fri Mar 5 07:51:04 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/gnome-terminal
LiveMediaBuild: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100224.1)
NonfreeKernelModules: nvidia
Package: gnome-terminal 2.29.6-0ubuntu1
ProcEnviron:
 LANG=he_IL.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
SourcePackage: gnome-terminal
Uname: Linux 2.6.32-14-generic x86_64
XsessionErrors:
 (bluetooth-applet:4471): Gtk-CRITICAL **: gtk_action_set_sensitive: assertion `GTK_IS_ACTION (action)' failed
 (polkit-gnome-authentication-agent-1:4476): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-terminal:4585): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed

[Pedro Villavicencio (pedro)]

As per the logs:

Backtrace:
0: /usr/bin/X (xorg_backtrace+0x28) [0x4a2528]
1: /usr/bin/X (0x400000+0x6522d) [0x46522d]
2: /lib/libpthread.so.0 (0x7f2f9fa5e000+0xf780) [0x7f2f9fa6d780]
3: /lib/libc.so.6 (__select+0x13) [0x7f2f9e818be3]
4: /usr/bin/X (WaitForSomething+0x1ba) [0x45f5fa]
5: /usr/bin/X (0x400000+0x308d2) [0x4308d2]
6: /usr/bin/X (0x400000+0x2614a) [0x42614a]
7: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7f2f9e75ac4d]
8: /usr/bin/X (0x400000+0x25cf9) [0x425cf9]

Please read https://wiki.ubuntu.com/X/Backtracing to get a more complete backtrace. thanks.

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.