GNOME Bugzilla – Bug 103956
crash using via vnc
Last modified: 2009-08-15 18:40:50 UTC
Package: gnome-terminal Severity: major Version: 2.1.4 Synopsis: crash using via vnc Bugzilla-Product: gnome-terminal Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.1.90) Description: Description of Problem: I get a crash of gnome-terminal using is via vnc connection with metacity as wm Steps to reproduce the problem: 1. get debian unstable 2. use metacity as wm 3. connect remotly via vnc (tighvnc (server) , vnc (client)) Actual Results: crahs Expected Results: run correctly How often does this happen? often Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-terminal' (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 10117)] (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...0x40b4da39 in wait4 () from /lib/libc.so.6
+ Trace 32931
Thread 1 (Thread 16384 (LWP 10117))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-01-20 04:46 ------- The original reporter (alessiodessi@tiscali.it) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, hp@redhat.com.
Appears to be a unique stack trace, according to the simple-dup-finder. Marking priority->high & severity->critical (it's a crasher), setting version->2.1.x, adding the GNOMEVER2.1 keyword, and marking as new.
*** Bug 104217 has been marked as a duplicate of this bug. ***
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=80414 gnome-terminal fails with any X server that lacks XRENDER, including Xvnc, Solaris openwin, X-Win32 5.0, and many LTSP clients. These X servers are very widespread and in most cases cannot be upgraded. I would consider this bug to be a critical or even blocker for Gnome 2.2
*** Bug 106589 has been marked as a duplicate of this bug. ***
Does this behave as an out-of-memory crash (i.e., if you run "top" in an Xterm, using "m" to sort by memory use, does gnome-terminal grow very quickly and then exit), or something else? If it's an out-of-memory crash, then it's probably http://fontconfig.org/cgi-bin/bugzilla/show_bug.cgi?id=26
*** Bug 108895 has been marked as a duplicate of this bug. ***
*** Bug 111045 has been marked as a duplicate of this bug. ***
Please respond to the question Nalin asked.
No feedback and no new duplicates in a while. Closing. Feel free to reopen if you have new information.