After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 124219 - gnome-terminal crashed (no transparent backgrounds involved)
gnome-terminal crashed (no transparent backgrounds involved)
Status: RESOLVED DUPLICATE of bug 94509
Product: gnome-terminal
Classification: Core
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-10-09 16:36 UTC by david.cook+gbg
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description david.cook+gbg 2003-10-09 15:35:57 UTC 
Package: gnome-terminal
Severity: normal
Version: 2.0.1
Synopsis: gnome-terminal crashed (no transparent backgrounds involved)
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.0.3)

Description:
Description of Problem:

Note:  This "Bug Buddy" shows a known bug relating to gnome-terminal with transparent backgrounds.
I do not have any transparent backgrounds, so I consider my occurrence a different bug (could be wrong, of course)


I had 11 gnome-terminal windows open, spread across 5 desktops (running
GNOME, metacity window manager, various other apps).
Two windows were running mutt, one had trn.  gnome-terminal crashed
(taking out all of my windows - back to xterms for me !).  
The only action I can think of that may be related to the crash - I
resized one of the windows running mutt while downloading
a large amount of mail - mutt would have been sent a SIGWINCH, but it
looks like it doesn't respond to it until after it has finished
downloading messages.  I was on a different desktop to the mutt window
at the time of the crash, so I don't know if mutt resized
successfully or not.

Steps to reproduce the problem:
1. 
2. 
3. 

Actual Results:


Expected Results:


How often does this happen?
Twice in recent time, in both cases with multiple windows spread across
multiple desktops.


Additional Information:




Debugging Information:

Backtrace was generated from '/usr/bin/gnome-terminal'

(no debugging symbols found)...[New Thread 8192 (LWP 6706)]
0x420ae169 in wait4 () from /lib/i686/libc.so.6

+ Trace 40728

Thread 1 (Thread 8192 (LWP 6706))

  • #0 wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 waitpid
    from /lib/i686/libpthread.so.0
  • #3 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #4 __pthread_sighandler
    from /lib/i686/libpthread.so.0
  • #5 <signal handler called>
  • #6 kill
    from /lib/i686/libc.so.6
  • #7 raise
    from /lib/i686/libpthread.so.0
  • #8 abort
    from /lib/i686/libc.so.6
  • #9 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #10 g_log
    from /usr/lib/libglib-2.0.so.0
  • #11 vte_terminal_ensure_cursor
    from /usr/lib/libvte.so.2
  • #12 vte_terminal_insert_char
    from /usr/lib/libvte.so.2
  • #13 vte_terminal_process_incoming
    from /usr/lib/libvte.so.2
  • #14 g_idle_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #15 g_main_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #16 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #17 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #18 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #19 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 main
  • #21 __libc_start_main
    from /lib/i686/libc.so.6
  • #0 wait4
    from /lib/i686/libc.so.6 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-10-09 11:35 -------

The original reporter (david.cook+gbg@pobox.com) 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, gnome-terminal-maint@bugzilla.gnome.org.
Comment 1 Mariano Suárez-Alvarez 2003-10-09 15:41:31 UTC 

*** This bug has been marked as a duplicate of 94509 ***