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 125816 - gnome terminal crash code 1111
gnome terminal crash code 1111
Status: RESOLVED DUPLICATE of bug 105745
Product: gnome-terminal
Classification: Core
Component: general
unspecified
Other other
: High critical
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
: 128082 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-10-30 01:53 UTC by rbh00
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.1/2.2



Description rbh00 2003-10-30 01:53:43 UTC
Package: gnome-terminal
Severity: normal
Version: 2.2.1
Synopsis: gnome terminal crash code 1111
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:
I got an Error box with the partial text as in Summary.  Unfortunately
the box doesn't rewrite when uncovered whilst I am in this Bug
Description box, or I'd tell you more.  Too bad, guess that's another
bug, huh?

As I recall, I'd moved from area 12 (I maintain 12 desktops), which
contained xchat, to area 8, which contained Mozilla Firebird.  Both
these application instances remain alive and well in their respective
desktops (== areas, i mean the same thing, by "desktop" and "area").

On further examination it appears my desktops 1 and 2 are dead.  They
were running Hercules, a hardware emulator for the IBM S/390 mainframe;
I'd left them running for weeks on end with no use of them.  I bet an
out-of-memory condition occurred.  (checks /var/log/messages -- nothing)
(checks home directory -- nothing)

Steps to reproduce the problem:
1. Sorry, I'd have to try running hercules again for a few weeks
2. 
3. 

Actual Results:


Expected Results:


How often does this happen?
Once only.

Additional Information:
It'd be nice if I could refer to the "Error" box contents while filling
this form out.  But (1) I already mentioned that and (2) for all I know,
you've captured its contents as an automatic part of this procedure.

(Later that same day ...)  ah, yes, I see you have.

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)...[New
Thread 16384 (LWP 1111)]

(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)...
0x40a180c7 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 16384 (LWP 1111))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 __pthread_sighandler
    from /lib/libpthread.so.0
  • #3 <signal handler called>
  • #4 g_object_unref
    from /usr/lib/libgobject-2.0.so.0
  • #5 expose_serial_predicate
    from /usr/lib/libgdk-x11-2.0.so.0
  • #6 _gdk_window_process_expose
    from /usr/lib/libgdk-x11-2.0.so.0
  • #7 gdk_add_client_message_filter
    from /usr/lib/libgdk-x11-2.0.so.0
  • #8 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #9 _gdk_events_queue
    from /usr/lib/libgdk-x11-2.0.so.0
  • #10 g_get_current_time
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #14 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 main
  • #16 __libc_start_main
    from /lib/libc.so.6
  • #0 waitpid
    from /lib/libpthread.so.0




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-10-29 20:53 -------

The original reporter (rbh00@utsglobal.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 Olav Vitters 2003-11-01 21:14:53 UTC
Thanks for the bug report. This particular bug has already been
reported into our bug tracking system, but please feel free to report
any further bugs you find.

*** This bug has been marked as a duplicate of 105745 ***
Comment 2 Olav Vitters 2003-11-01 21:22:02 UTC
Did not look close enough. reopening.
Comment 3 Heath Harrelson 2003-12-04 00:54:22 UTC
*** Bug 128082 has been marked as a duplicate of this bug. ***
Comment 4 Heath Harrelson 2003-12-04 01:01:03 UTC
Bug #128082 describes a crash under similar circumstances (crash upon
redraw after switching from a different workspace), and the trace is
nearly identical.  Setting appropriate Priority/Severity and confirming. 
Comment 5 Mariano Suárez-Alvarez 2004-01-22 05:53:01 UTC
This does not look like something in gnome-terminal, butmaybe gtk
people can see better?
Comment 6 Owen Taylor 2004-01-22 16:56:54 UTC
Why don't you think it is a dup of bug 105745?
Comment 7 Mariano Suárez-Alvarez 2004-05-06 04:40:55 UTC

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