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 110361 - Gnome help crash
Gnome help crash
Status: RESOLVED DUPLICATE of bug 94509
Product: gnome-terminal
Classification: Core
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: Havoc Pennington
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-04-09 06:38 UTC by tcutler1a
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description tcutler1a 2003-04-09 06:37:18 UTC 
Package: acme
Severity: normal
Version: 2.0.1
Synopsis: Gnome help crash
Bugzilla-Product: acme
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.0.3)

Description:
Description of Problem:


Steps to reproduce the problem:
1. launched help
2. select man pages from home page
3. select fetchmail and process hangs

Actual Results:
hangs and then crashes help window after a minute or so of fully
occupying the CPU

Expected Results:
the man page

How often does this happen?
first time I've seen it. It's bad when "Help" crashes.

Additional Information:




Debugging Information:

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

(no debugging symbols found)...0x408f5587 in waitpid ()
   from /lib/libpthread.so.0

+ Trace 35751

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 __pthread_clock_settime
    from /lib/libpthread.so.0
  • #3 killpg
    from /lib/libc.so.6
  • #4 raise
    from /lib/libc.so.6
  • #5 abort
    from /lib/libc.so.6
  • #6 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #7 g_log
    from /usr/lib/libglib-2.0.so.0
  • #8 vte_terminal_ensure_cursor
    from /usr/lib/libvte.so.2
  • #9 vte_sequence_handler_ce
    from /usr/lib/libvte.so.2
  • #10 vte_terminal_handle_sequence
    from /usr/lib/libvte.so.2
  • #11 vte_terminal_process_incoming
    from /usr/lib/libvte.so.2
  • #12 g_idle_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #14 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #15 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #16 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #17 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 main
  • #19 __libc_start_main
    from /lib/libc.so.6 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-04-09 02:37 -------

The original reporter (tcutler1a@cox.net) 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, hadess@hadess.net.
Comment 1 John Fleck 2003-04-09 14:31:44 UTC 
I'm confused about the steps to trigger this and the apps involved.
The stack trace is clearly the terminal, caused by vte, and should be
fixed in more recent versions. Please upgrade and report back if you
still have the problem.
Thanks

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