Ubuntu
gnome-terminal package

  1. Bug #436188
  2. Comment #26

Comment 26 for bug 436188

Revision history for this message
In , Bevis (bevis-redhat-bugs) wrote :

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
**
ERROR:terminal-app.c:1525:terminal_app_init: assertion failed: (app->default_profile_id != NULL)
*** 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):
gnome-terminal-2.24.1-2.fc10.x86_64

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.