Bug 477963 – crash in Terminal: changed font antialiasin...

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 477963 - crash in Terminal: changed font antialiasin...


Summary:	crash in Terminal: changed font antialiasin...


Status:	RESOLVED DUPLICATE of bug 389538

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-09-18 07:08 UTC by dliakh
Modified:	2007-09-18 09:58 UTC

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

Description dliakh 2007-09-18 07:08:45 UTC

Version: 2.16.0

What were you doing when the application crashed?
changed font antialiasing mode


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:37:32 EDT 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled

Memory status: size: 148914176 vsize: 0 resident: 148914176 share: 0 rss: 13955072 rss_rlim: 0
CPU usage: start_time: 1188281495 rtime: 0 utime: 33558232 stime: 0 cutime:22284661 cstime: 0 timeout: 11273571 it_real_value: 0 frequency: 12379

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
0x00301402 in __kernel_vsyscall ()

+ Trace 163694

#0 __kernel_vsyscall
#1 wait
from /lib/libpthread.so.0
#2 <signal handler called>
#3 vte_terminal_accessible_new
from /usr/lib/libvte.so.9
#4 vte_terminal_set_font_full
from /usr/lib/libvte.so.9
#5 vte_terminal_set_font_full
from /usr/lib/libvte.so.9
#6 g_cclosure_marshal_VOID__PARAM
from /lib/libgobject-2.0.so.0
#7 g_closure_invoke
from /lib/libgobject-2.0.so.0
#8 g_signal_override_class_closure
from /lib/libgobject-2.0.so.0
#9 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#10 g_signal_emit
from /lib/libgobject-2.0.so.0
#11 g_object_class_override_property
from /lib/libgobject-2.0.so.0
#12 g_enum_register_static
from /lib/libgobject-2.0.so.0
#13 g_object_notify
from /lib/libgobject-2.0.so.0
#14 gtk_settings_get_for_screen
from /usr/lib/libgtk-x11-2.0.so.0
#15 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#16 gdk_add_client_message_filter
from /usr/lib/libgdk-x11-2.0.so.0
#17 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#18 g_main_context_check
from /lib/libglib-2.0.so.0
#19 g_main_loop_run
from /lib/libglib-2.0.so.0
#20 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#21 g_cclosure_marshal_VOID__OBJECT
#22 __gconv_read_conf
from /lib/libc.so.6
#23 g_cclosure_marshal_VOID__OBJECT



----------- .xsession-errors ---------------------
warning: Cannot initialize thread debugging library: unknown thread_db error '22'
warning: Cannot initialize thread debugging library: unknown thread_db error '22'
warning: Cannot initialize thread debugging library: unknown thread_db error '22'
warning: Cannot initialize thread debugging library: unknown thread_db error '22'
warning: Cannot initialize thread debugging library: unknown thread_db error '22'
warning: Cannot initialize thread debugging library: unknown thread_db error '22'
warning: Cannot initialize thread debugging library: unknown thread_db error '22'
warning: Cannot initialize thread debugging library: unknown thread_db error '22'
--------------------------------------------------

Comment 1 Cosimo Cecchi 2007-09-18 09:58:29 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 389538 ***