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 308950 - stron crash of terminals during calculation
stron crash of terminals during calculation
Status: RESOLVED DUPLICATE of bug 167202
Product: gnome-terminal
Classification: Core
Component: general
2.7.x
Other other
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-06-24 17:51 UTC by boudifa
Modified: 2005-06-25 18:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.7/2.8



Description boudifa 2005-06-24 17:51:18 UTC
Distribution: Red Hat Enterprise Linux AS release 4 (Nahant)
Package: gnome-utils
Severity: normal
Version: GNOME2.8.0 2.7.3
Gnome-Distributor: Red Hat, Inc
Synopsis: stron crash of terminals during calculation
Bugzilla-Product: gnome-utils
Bugzilla-Component: gdict
Bugzilla-Version: 2.7.3
BugBuddy-GnomeVersion: 2.0 (2.8.0)
Description:
Description of the crash:


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

Expected Results:


How often does this happen?


Additional Information:



Debugging Information:

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

(no debugging symbols found)...Using host libthread_db library
"/lib64/tls/libthread_db.so.1".
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...[Thread debugging using libthread_db enabled]
[New Thread 182894280000 (LWP 28432)]
[New Thread 1084229984 (LWP 28435)]
[Thread debugging using libthread_db enabled]
[New Thread 182894280000 (LWP 28432)]
[New Thread 1084229984 (LWP 28435)]
[Thread debugging using libthread_db enabled]
[New Thread 182894280000 (LWP 28432)]
[New Thread 1084229984 (LWP 28435)]
(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)...0x0000003a4650c02a in waitpid ()
from /lib64/tls/libpthread.so.0

Thread 1 (Thread 182894280000 (LWP 28432))

  • #0 waitpid
    from /lib64/tls/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 gtk_widget_set_sensitive
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #4 terminal_screen_get_text_selected
  • #5 terminal_screen_get_text_selected
  • #6 gtk_marshal_VOID__UINT_STRING
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #7 g_closure_invoke
    from /usr/lib64/libgobject-2.0.so.0
  • #8 g_signal_has_handler_pending
    from /usr/lib64/libgobject-2.0.so.0
  • #9 g_signal_emit_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #10 g_signal_emit
    from /usr/lib64/libgobject-2.0.so.0
  • #11 gtk_widget_activate
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #12 gtk_propagate_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #13 gtk_main_do_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #14 gdk_event_get_graphics_expose
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #15 g_main_context_dispatch
    from /usr/lib64/libglib-2.0.so.0
  • #16 g_main_context_acquire
    from /usr/lib64/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /usr/lib64/libglib-2.0.so.0
  • #18 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #19 main




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-06-24 17:51 UTC -------


Bugreport moved from gnome-utils / gdict
  to gnome-terminal / general
Unknown version 2.7.3 in product gnome-terminal.  Setting version to "2.7.x".
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was boudifa@utt.fr.

Comment 1 Michele Baldessari 2005-06-25 18:54:25 UTC

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