Bug 400262 – crash in Terminal: Revisaba el correo elect...

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 400262 - crash in Terminal: Revisaba el correo elect...


Summary:	crash in Terminal: Revisaba el correo elect...


Status:	RESOLVED DUPLICATE of bug 348979

Product:	gnome-terminal
Classification:	Core
Component:	general
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	GNOME Terminal Maintainers
QA Contact:	GNOME Terminal Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-01-24 16:25 UTC by alpachex
Modified:	2007-01-24 18:43 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description alpachex 2007-01-24 16:25:55 UTC

Version: 2.16.0

What were you doing when the application crashed?
Revisaba el correo electronico


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 327053312 vsize: 327053312 resident: 22757376 share: 9691136 rss: 22757376 rss_rlim: -1
CPU usage: start_time: 1169576426 rtime: 6028 utime: 5358 stime: 670 cutime:294 cstime: 542 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496349664 (LWP 9772)]
[New Thread 1084229952 (LWP 9776)]
(no debugging symbols found)
0x0000003610a0d96f in waitpid () from /lib64/libpthread.so.0

+ Trace 104889

Thread 1 (Thread 46912496349664 (LWP 9772))

#0 waitpid
from /lib64/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 g_type_check_is_value_type
from /lib64/libgobject-2.0.so.0
#4 g_value_type_compatible
from /lib64/libgobject-2.0.so.0
#5 g_object_class_override_property
from /lib64/libgobject-2.0.so.0
#6 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#7 g_signal_emit
from /lib64/libgobject-2.0.so.0
#8 gtk_widget_set_usize
from /usr/lib64/libgtk-x11-2.0.so.0
#9 gtk_widget_set_usize
from /usr/lib64/libgtk-x11-2.0.so.0
#10 gtk_box_pack_start_defaults
from /usr/lib64/libgtk-x11-2.0.so.0
#11 gtk_notebook_popup_enable
from /usr/lib64/libgtk-x11-2.0.so.0
#12 gtk_box_pack_start_defaults
from /usr/lib64/libgtk-x11-2.0.so.0
#13 gtk_rc_get_module_dir
from /usr/lib64/libgtk-x11-2.0.so.0
#14 gtk_icon_info_get_type
from /usr/lib64/libgtk-x11-2.0.so.0
#15 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#16 g_main_context_check
from /lib64/libglib-2.0.so.0
#17 g_main_loop_run
from /lib64/libglib-2.0.so.0
#18 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#19 g_cclosure_marshal_VOID__OBJECT
#20 __libc_start_main
from /lib64/libc.so.6
#21 g_cclosure_marshal_VOID__OBJECT
#22 ??
#23 ??
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 palfrey 2007-01-24 18:43:58 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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