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 601584 - crash in Terminal: ouch setting vt100 crash...
crash in Terminal: ouch setting vt100 crash...
Status: RESOLVED DUPLICATE of bug 596460
Product: gnome-terminal
Classification: Core
Component: BugBuddyBugs
2.28.x
Other All
: Normal critical
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-11-11 17:41 UTC by slava
Modified: 2009-11-11 18:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description slava 2009-11-11 17:41:11 UTC
Version: 2.28.0

What were you doing when the application crashed?
ouch setting vt100 crashed all terms!!!


Distribution:                        OpenSolaris Development snv_126 X86
Gnome Release: 2.28.0 2009-10-13 (Sun Microsystems, Inc.)
BugBuddy Version: 2.28.0

X Vendor: Sun Microsystems, Inc.
X Vendor Release: 10605000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mist
Icon Theme: Mist
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 102014976 vsize: 102014976 resident: 24502272 share: 786432 rss: 24502272 rss_rlim: 0
CPU usage: start_time: 1257640835 rtime: 20295 utime: 169278667 stime: 33671818 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

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

1203:	gnome-terminal --sm-client-id 10154a5b4db0662b6a1253828620411216000000
-----------------  lwp# 1 / thread# 1  --------------------
 feef3d35 waitid   (0, e34, 8046fe0, 3)
 feea3305 waitpid  (e34, 804709c, 0, fed5b60d) + 65
 fed5ba14 g_spawn_sync (0, 86bd7b0, 0, 4, 0, 0) + 418
 fed5be28 g_spawn_command_line_sync (85eb7b8, 0, 0, 0, 80471bc) + 5c
 fdb81e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58b8, 4b3, 0, fdb81ff2) + f3
 fdb820d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 8047244, feeee735, b, 0) + 12e
 fdb81a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 80472f8, fecc2a00, fef81000, 80472b4) + 64
 feeee735 __sighndlr (b, 0, 80472f8, fdb81a30) + 15
 feee15ef call_user_handler (b) + 2af
 feee181f sigacthandler (b, 0, 80472f8) + df
 --- called from signal handler with signal 11 (SIGSEGV) ---
 fd85ce63 _vte_terminal_ring_append (8676720, 0, 50, fd87f706) + 1f
 fd87f81d vte_sequence_handler_cd (8676618, 0, 80475a8, fd882112) + 125
 fd882178 vte_sequence_handler_erase_in_display (8676618, 822e100, f, fd88376a) + 74
 fd883895 _vte_terminal_handle_sequence (8676618, 80d7b10, 506, 822e100) + 139
 fd862d99 vte_terminal_process_incoming (8676618, 0) + 405
 fd87481c time_process_incoming (8676618, 1, 8676618, fd8748ae) + 2c
 fd874a4c process_timeout (0, fedcc460, 8047748, fed26c71) + 1ac
 fed26c87 g_timeout_dispatch (8369740, fd8748a0, 0, 80477c0) + 23
 fed24eee g_main_context_dispatch (80c2638, 0, 8650408, 1c) + 262
 fed2559f g_main_context_iterate (80c2638, 1, 1, 80a6858) + 483
 fed25bc9 g_main_loop_run (82227e8, 82227e8, 80a9800, fe37e726) + 1dd
 fe37e7cf gtk_main (3, 0, 80c4374, feffb804, 80479a0, fefdcf48) + b7
 0806b594 main     (1, 80479f8, 8047a08, 80479ec) + 944
 080677fd _start   (3, 8047b0c, 0, 0, 0, 8047b5b) + 7d
-----------------  lwp# 2 / thread# 2  --------------------
 feef34d5 read     (15, f8aeef50, 14)
 fed270c1 child_watch_helper_thread (0, 8233b08, 200, fed4d1de) + 29
 fed4d303 g_thread_create_proxy (8233b08, fef81000, f8aeefe8, feeee36e) + 133
 feeee3c3 _thrp_setup (fdcf0a00) + 9b
 feeee650 _lwp_start (fdcf0a00, 0, 0, 0, 0, 0)


----------- .xsession-errors (308277 sec old) ---------------------
xscreensaver: 23:01:17: screen 0/0: 0xb0, 0x0, 0x2000001
##############################################################################
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  12 (X_ConfigureWindow)
  Serial number of failed request:  105646
  Current serial number in output stream:  105646
##############################################################################
    If at all possible, please re-run xscreensaver with the command
    line arguments `-sync -verbose -no-capture', and reproduce this
    
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Christian Persch 2009-11-11 18:30:10 UTC

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