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 121735 - Unknown gnome-terminal problem
Unknown gnome-terminal problem
Status: RESOLVED DUPLICATE of bug 107007
Product: gnome-terminal
Classification: Core
Component: general
unspecified
Other other
: Normal normal
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
: 123656 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-09-08 03:30 UTC by K.S. Bhaskar
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description K.S. Bhaskar 2003-09-08 03:30:56 UTC
Package: gnome-terminal
Severity: normal
Version: 2.2.1
Synopsis: Unknown gnome-terminal problem
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:

I was using evolution with the Exchange connector when I received a
dialog box with the error that gnome-terminal had crashed.  This
happened competely at random, at a time when I was not even aware that I
was running gnome-terminal.

Steps to reproduce the problem:
1. Use evolution, compose a message, type in it
2. 
3. 

Actual Results:

Dialog box that gnome-terminal has crashed.

Expected Results:

Continued typing in to evolution

How often does this happen?

Happened just once.

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)...[New Thread 1087430112 (LWP 2950)]
0xffffe002 in ?? ()

Thread 1 (Thread 1087430112 (LWP 2950))

  • #0 ??
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 gtk_widget_get_toplevel
    from /usr/lib/libgtk-x11-2.0.so.0
  • #4 gtk_false
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #7 g_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #11 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 main
  • #13 __libc_start_main
    from /lib/tls/libc.so.6
  • #0 ??


***************************************************************************
This electronic mail transmission contains confidential and/or privileged
information intended only for the person(s) named.  Any use, distribution,
copying or disclosure by another person is strictly prohibited.
***************************************************************************
7/9/2003




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-09-07 23:30 -------

The original reporter (k.bhaskar@sanchez.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 K.S. Bhaskar 2003-09-08 13:20:20 UTC
I apologize for some incorreect information in the submission.  I
*did* have a gnome-terminal session which I had used to start a VPN
client and then forgotten about.  However, the fact remains that I was
not doing anything at the session when it crashed.

-- Bhaskar
Comment 2 Vincent Untz 2003-09-30 10:33:29 UTC
You need to update GTK+ to 2.2.3.

*** This bug has been marked as a duplicate of 107007 ***
Comment 3 Mariano Suárez-Alvarez 2003-10-01 20:37:28 UTC
*** Bug 123656 has been marked as a duplicate of this bug. ***