Launchpad has imported 10 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=473566.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2008-11-29T11:50:56+00:00 Bevis 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- terminal/+bug/436188/comments/0 ------------------------------------------------------------------------ On 2008-11-30T10:06:50+00:00 Bevis wrote: This also happens if you login via ssh and try to start gnome-terminal from the command line like so: willow% gnome-terminal --display cyane:0 & [1] 13791 willow% ** ERROR:terminal-app.c:1525:terminal_app_init: assertion failed: (app->default_profile_id != NULL) [1] Abort gnome-terminal --display cyane:0 willow% Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- terminal/+bug/436188/comments/1 ------------------------------------------------------------------------ On 2009-01-21T18:30:25+00:00 George wrote: I'm getting the same failure when starting gnome-terminal from the GNOME panel or command line of an existing gnome-terminal. I have no idea why I was able to start gnome-terminals then it stopped. I've seen this in several login sessions. I've had to put xterm on the panel as a backup. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- terminal/+bug/436188/comments/2 ------------------------------------------------------------------------ On 2009-09-28T13:33:08+00:00 Paul wrote: https://launchpad.net/bugs/436188 + dups, although this was allegedly fixed before at https://launchpad.net/bugs/298426 Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- terminal/+bug/436188/comments/9 ------------------------------------------------------------------------ On 2009-11-18T09:04:04+00:00 Bug wrote: This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- terminal/+bug/436188/comments/17 ------------------------------------------------------------------------ On 2009-11-18T13:50:08+00:00 Paul wrote: AFAIK, this is still current; it is in the other distros above. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- terminal/+bug/436188/comments/18 ------------------------------------------------------------------------ On 2009-11-18T14:02:51+00:00 Bevis wrote: Yes, this is still a problem with Fedora 11. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- terminal/+bug/436188/comments/19 ------------------------------------------------------------------------ On 2009-11-18T14:03:39+00:00 Bevis wrote: Looks like I have managed to change the release to Fedora 11, so the bug won't get automatically closed. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- terminal/+bug/436188/comments/20 ------------------------------------------------------------------------ On 2010-04-27T12:24:02+00:00 Bug wrote: This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- terminal/+bug/436188/comments/31 ------------------------------------------------------------------------ On 2010-06-28T10:51:02+00:00 Bug wrote: Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome- terminal/+bug/436188/comments/32 ** Changed in: gnome-terminal (Fedora) Status: Confirmed => Won't Fix ** Changed in: gnome-terminal (Fedora) Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/436188 Title: gnome-terminal assert failure: ERROR:terminal- app.c:1444:terminal_app_init: assertion failed: (app->default_profile_id != NULL) Status in gnome-terminal package in Ubuntu: Incomplete Status in gnome-terminal package in Debian: Fix Released Status in gnome-terminal package in Fedora: Won't Fix 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-app.c:1444:terminal_app_init: assertion failed: (app->default_profile_id != NULL) Date: Thu Sep 24 16:14:59 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/gnome-terminal Package: gnome-terminal 2.28.0-0ubuntu1 ProcCmdline: gnome-terminal ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-10.35-generic Signal: 6 SourcePackage: gnome-terminal StacktraceTop: __kernel_vsyscall () raise () from /lib/tls/i686/cmov/libc.so.6 abort () from /lib/tls/i686/cmov/libc.so.6 g_assertion_message () from /usr/lib/libglib-2.0.so.0 g_assertion_message_expr () from /usr/lib/libglib-2.0.so.0 Tags: ubuntu-unr Title: gnome-terminal assert failure: ERROR:terminal-app.c:1444:terminal_app_init: assertion failed: (app->default_profile_id != NULL) Uname: Linux 2.6.31-10-generic i686 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/436188/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
