gnome-terminal assert failure: ERROR:terminal-app.c:1444:terminal_app_init: assertion failed: (app->default_profile_id != NULL)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-terminal (Debian) |
Fix Released
|
Unknown
|
|||
gnome-terminal (Fedora) |
Won't Fix
|
Medium
|
|||
gnome-terminal (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: gnome-terminal
this bug just popped up when i was launching a terminal window
ProblemType: Crash
Architecture: i386
AssertionMessage: ERROR:terminal-
Date: Thu Sep 24 16:14:59 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/
Package: gnome-terminal 2.28.0-0ubuntu1
ProcCmdline: gnome-terminal
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
Signal: 6
SourcePackage: gnome-terminal
StacktraceTop:
__kernel_vsyscall ()
raise () from /lib/tls/
abort () from /lib/tls/
g_assertion_
g_assertion_
Tags: ubuntu-unr
Title: gnome-terminal assert failure: ERROR:terminal-
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
Changed in gnome-terminal (Debian): | |
status: | Unknown → New |
Changed in gnome-terminal (Fedora): | |
status: | Unknown → Confirmed |
Changed in gnome-terminal (Ubuntu): | |
status: | Confirmed → Triaged |
Changed in gnome-terminal (Debian): | |
status: | New → Fix Released |
Changed in gnome-terminal (Fedora): | |
importance: | Unknown → Medium |
status: | Confirmed → Won't Fix |
Description of problem:
When starting a gnome-terminal on a remote host with all X11/TCP infrastructure code including CORBA via IPv4 enabled (other apps work fine), the gnome-terminal gets a glibc double free error and crashes...
rsh willow gnome-terminal --display $DISPLAY app.c:1525: terminal_ app_init: assertion failed: (app->default_ profile_ id != NULL)
**
ERROR:terminal-
*** glibc detected *** gnome-terminal: double free or corruption (out): 0x000000000178c0e0 ***
and then hangs...
Other X applications work fine.
Version-Release number of selected component (if applicable): 2.24.1- 2.fc10. x86_64
gnome-terminal-
How reproducible:
every time
Steps to Reproduce:
1. Enable X11/TCP mode and xauth on NFS - restart GDM/X server
2. Enable ORBIOPIPv4 in /etc/orbitrc
3. Login into GNOME session on Workstation
4. xauth list - take value and xauth -f .Xauthority add with the
details
5. Enable rsh-server on the file server machine on the local network
6. Test rsh is working (.rhosts etc)
7. Run: rsh fileserver gnome-terminal --display $DISPLAY
Actual results:
Gnome terminal crashes with assertion failure.
Expected results:
Gnome terminal starts on fileserver displaying via X11/TCP
Additional info:
Local network is secure - TCP/X11 tunnelling and SSH is totally unnecessary and over the top and produces significant latency and consumes ptys.