Bug 313732 – gnome-terminal crashs

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 313732 - gnome-terminal crashs


Summary:	gnome-terminal crashs


Status:	RESOLVED DUPLICATE of bug 161843

Product:	gnome-terminal
Classification:	Core
Component:	general
Version:	2.10.x
Hardware:	Other other

Importance:	Normal normal
Target Milestone:	---
Assigned To:	GNOME Terminal Maintainers
QA Contact:	GNOME Terminal Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2005-08-17 16:03 UTC by Thomas Steudten
Modified:	2005-08-18 13:29 UTC

See Also:
GNOME target:	---
GNOME version:	2.9/2.10

Description Thomas Steudten 2005-08-17 16:03:30 UTC

Distribution: Fedora Core release 4 (Stentz)
Package: gnome-terminal
Severity: normal
Version: GNOME2.10.0 2.10.0
Gnome-Distributor: Red Hat, Inc
Synopsis: gnome-terminal crashs
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
Bugzilla-Version: 2.10.0
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:
gnome-terminal crashs

Steps to reproduce the crash:
1. open one gnome-terminal
2. start "gnome-terminal -e top -t top &" and "gnome-terminal -e top -e
slabtop" &
3. Resize font of the two terminal with "ctrl-MINUS" 
4. in the 1. terminal enter: gnome-session-save -> crash.

Expected Results: No crash


How often does this happen? reproducible


Additional Information:



Debugging Information:

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)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208224064 (LWP 22822)]
[New Thread -1218954320 (LWP 22827)]
(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)
0x00466402 in ?? ()

+ Trace 62501

Thread 1 (Thread -1208224064 (LWP 22822))

#0 ??
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 vfprintf
from /lib/libc.so.6
#5 vasprintf
from /lib/libc.so.6
#6 g_vasprintf
from /usr/lib/libglib-2.0.so.0
#7 g_strdup_vprintf
from /usr/lib/libglib-2.0.so.0
#8 g_print
from /usr/lib/libglib-2.0.so.0
#9 terminal_app_edit_encodings
#10 _gnome_marshal_BOOLEAN__INT_ENUM_BOOLEAN_ENUM_BOOLEAN
from /usr/lib/libgnomeui-2.so.0
#11 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_stop_emission
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#15 gnome_client_get_config_prefix
from /usr/lib/libgnomeui-2.so.0
#16 _SmcProcessMessage
from /usr/X11R6/lib/libSM.so.6
#17 IceProcessMessages
from /usr/X11R6/lib/libICE.so.6
#18 gnome_href_set_label
from /usr/lib/libgnomeui-2.so.0
#19 g_vasprintf
from /usr/lib/libglib-2.0.so.0
#20 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#21 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#22 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#23 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#24 main





------- Bug moved to this database by unknown@gnome.bugs 2005-08-17 16:03 UTC -------


Unknown version 2.10.0 in product gnome-terminal.  Setting version to "2.10.x".
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@gnome.bugs.
   Previous reporter was thomas@steudten.com.

Comment 1 Guillaume Desmottes 2005-08-18 13:29:24 UTC

Thanks for the bug report. 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?

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