GNOME issues
https://gitlab.gnome.org/groups/GNOME/-/issues
2021-06-10T14:17:58Z
https://gitlab.gnome.org/GNOME/vte/-/issues/1733
crash in Terminal: i was remotely logged on...
2021-06-10T14:17:58Z
Bugzilla
crash in Terminal: i was remotely logged on...
## Submitted by nic..@..il.com
**[Link to original bug (#600598)](https://bugzilla.gnome.org/show_bug.cgi?id=600598)**
## Description
Version: 2.28.0
What were you doing when the application crashed?
i was remotely logged onto a ma...
## Submitted by nic..@..il.com
**[Link to original bug (#600598)](https://bugzilla.gnome.org/show_bug.cgi?id=600598)**
## Description
Version: 2.28.0
What were you doing when the application crashed?
i was remotely logged onto a mac mini su ing to root and then doing visudo when the bloody terminal died! wtf!!!!
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: SlicknesS-black
Icon Theme: black-white_2-Style
GTK+ Modules: canberra-gtk-module, gnomebreakpad
Memory status: size: 100937728 vsize: 100937728 resident: 23523328 share: 3014656 rss: 23523328 rss_rlim: 0
CPU usage: start_time: 1257281303 rtime: 197 utime: 1562604 stime: 408504 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0
Backtrace was generated from '/usr/bin/gnome-terminal'
1668: gnome-terminal
----------------- lwp# 1 / thread# 1 --------------------
feef3d35 waitid (0, 1285, 8046fe0, 3)
feea3305 waitpid (1285, 804709c, 0, fed5b60d) + 65
fed5ba14 g_spawn_sync (0, 82ba480, 0, 4, 0, 0) + 418
fed5be28 g_spawn_command_line_sync (8109238, 0, 0, 0, 80471bc) + 5c
fdb21e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58a0, 684, 0, fdb21ff2) + f3
fdb220d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 8047244, feeee735, b, 0) + 12e
fdb21a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 80472f8, fecc2a00, fef81000, 80472b4) + 64
feeee735 __sighndlr (b, 0, 80472f8, fdb21a30) + 15
feee15ef call_user_handler (b) + 2af
feee181f sigacthandler (b, 0, 80472f8) + df
--- called from signal handler with signal 11 (SIGSEGV) ---
fd7ece63 _vte_terminal_ring_append (82b5908, 0, b4, fd80f706) + 1f
fd80f81d vte_sequence_handler_cd (82b5800, 0, 80475a8, fd812112) + 125
fd812178 vte_sequence_handler_erase_in_display (82b5800, 82cf510, f, fd81376a) + 74
fd813895 _vte_terminal_handle_sequence (82b5800, 81c2df0, 50a, 82cf510) + 139
fd7f2d99 vte_terminal_process_incoming (82b5800, 0) + 405
fd80481c time_process_incoming (82b5800, 1, 82b5800, fd804c62) + 2c
fd804dd3 update_repeat_timeout (0, fedcc460, 8047748, fed26c71) + 17f
fed26c87 g_timeout_dispatch (82affb0, fd804c54, 0, 80477c0) + 23
fed24eee g_main_context_dispatch (80cfda8, c8, 81d8b30, c) + 262
fed2559f g_main_context_iterate (80cfda8, 1, 1, 80a6858) + 483
fed25bc9 g_main_loop_run (823d7c8, 823d7c8, 80a9800, fe37e726) + 1dd
fe37e7cf gtk_main (fefd4e56, 0, 8100c04, feffb804, 80479a0, fefdcf48) + b7
0806b594 main (1, 80479fc, 8047a04, feffb804) + 944
080677fd _start (1, 8047b0c, 0, 8047b1b, 8047b62, 8047ba6) + 7d
----------------- lwp# 2 / thread# 2 --------------------
feef34d5 read (15, f8a4ef50, 14)
fed270c1 child_watch_helper_thread (0, 80b3768, 200, fed4d1de) + 29
fed4d303 g_thread_create_proxy (80b3768, fef81000, f8a4efe8, feeee36e) + 133
feeee3c3 _thrp_setup (fdcc0a00) + 9b
feeee650 _lwp_start (fdcc0a00, 0, 0, 0, 0, 0)
----------- .xsession-errors ---------------------
(nautilus:1119): Gtk-CRITICAL **: file gtkuimanager.c: line 1958: assertion `GTK_IS_MENU_SHELL (menushell)' failed
(nautilus:1119): Gtk-WARNING **: About JDS: missing action About JDS
(nautilus:1119): Gtk-WARNING **: Go to Burn CD: missing action Go to Burn CD
(nautilus:1119): Gtk-CRITICAL **: file gtkwidget.c: line 6112: assertion `GTK_IS_WIDGET (widget)' failed
(nautilus:1119): Gtk-CRITICAL **: file gtkuimanager.c: line 1958: assertion `GTK_IS_MENU_SHELL (menushell)' failed
(nautilus:1119): Gtk-WARNING **: About JDS: missing action About JDS
(gnome-terminal:4721): Gtk-WARNING **: Unable to locate theme engine in module_path: "ubuntulooks",
(bug-buddy:4741): Gtk-WARNING **: Unable to locate theme engine in module_path: "ubuntulooks",
--------------------------------------------------
Version: 0.22.x
Resolution: RESOLVED DUPLICATE
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/1307
Crash when used the menu oprion Edit->Copy
2021-06-10T14:17:56Z
Bugzilla
Crash when used the menu oprion Edit->Copy
## Submitted by pep..@..sa.net
Assigned to **Havoc Pennington**
**[Link to original bug (#75524)](https://bugzilla.gnome.org/show_bug.cgi?id=75524)**
## Description
Package: gnome-terminal
Severity: major
Version: 1.4.0.6
Synopsis...
## Submitted by pep..@..sa.net
Assigned to **Havoc Pennington**
**[Link to original bug (#75524)](https://bugzilla.gnome.org/show_bug.cgi?id=75524)**
## Description
Package: gnome-terminal
Severity: major
Version: 1.4.0.6
Synopsis: Crash when used the menu oprion Edit->Copy
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
Description:
Always when I select a text area on gnome-terminal and go to "Edit" menu
and choose "Copy" option, it crashes with a segfault.
Debugging Information:
(no debugging symbols found)...0x406473a9 in wait4 () from /lib/libc.so.6
```
`#0` 0x406473a9 in wait4 () from /lib/libc.so.6
`#1` 0x406c4a54 in __check_rhosts_file () from /lib/libc.so.6
`#2` 0x402fb7e6 in gnome_segv_handle (signum=11) at gnome-init.c:664
`#3` 0x405ba9f8 in killpg () from /lib/libc.so.6
`#4` 0x40582f56 in g_strndup (str=0x1 <Address 0x1 out of bounds>, n=135164064)
at gstrfuncs.c:122
`#5` 0x08051381 in toggle_menubar_cmd ()
`#6` 0x40440fe7 in gtk_marshal_NONE__NONE (object=0x80cd890,
func=0x8051318 <toggle_menubar_cmd+840>, func_data=0x80b76d8,
args=0xbfffe170) at gtkmarshal.c:312
`#7` 0x40470706 in gtk_handlers_run (handlers=0x8066048, signal=0xbfffe110,
object=0x80cd890, params=0xbfffe170, after=0) at gtksignal.c:1917
`#8` 0x4046fb57 in gtk_signal_real_emit (object=0x80cd890, signal_id=86,
params=0xbfffe170) at gtksignal.c:1477
`#9` 0x4046dbcc in gtk_signal_emit (object=0x80cd890, signal_id=86)
at gtksignal.c:552
`#10` 0x404a51bc in gtk_widget_activate (widget=0x80cd890) at gtkwidget.c:2890
`#11` 0x4044932d in gtk_menu_shell_activate_item (menu_shell=0x80cee30,
menu_item=0x80cd890, force_deactivate=1) at gtkmenushell.c:859
`#12` 0x404485bd in gtk_menu_shell_button_release (widget=0x80cee30,
event=0x80e52f8) at gtkmenushell.c:486
`#13` 0x40440dbd in gtk_marshal_BOOL__POINTER (object=0x80cee30,
func=0x40448430 <gtk_menu_shell_button_release>, func_data=0x0,
args=0xbfffe540) at gtkmarshal.c:28
`#14` 0x4046fb97 in gtk_signal_real_emit (object=0x80cee30, signal_id=27,
params=0xbfffe540) at gtksignal.c:1492
`#15` 0x4046dbcc in gtk_signal_emit (object=0x80cee30, signal_id=27)
at gtksignal.c:552
`#16` 0x404a5084 in gtk_widget_event (widget=0x80cee30, event=0x80e52f8)
at gtkwidget.c:2864
`#17` 0x40440d34 in gtk_propagate_event (widget=0x80cd890, event=0x80e52f8)
at gtkmain.c:1378
`#18` 0x4043fef1 in gtk_main_do_event (event=0x80e52f8) at gtkmain.c:818
`#19` 0x404fa16b in gdk_event_dispatch (source_data=0x0,
current_time=0xbfffe910, user_data=0x0) at gdkevents.c:2139
`#20` 0x4057a055 in g_main_dispatch (dispatch_time=0xbfffe910) at gmain.c:656
`#21` 0x4057a659 in g_main_iterate (block=1, dispatch=1) at gmain.c:877
`#22` 0x4057a7e8 in g_main_run (loop=0x80acc10) at gmain.c:935
`#23` 0x4043f7f7 in gtk_main () at gtkmain.c:524
`#24` 0x08053e91 in new_terminal_for_client ()
`#25` 0x08053ec3 in main ()
`#26` 0x405a86f7 in __libc_start_main () from /lib/libc.so.6
`#0` 0x406473a9 in wait4 () from /lib/libc.so.6
No symbol table info available.
`#1` 0x406c4a54 in __check_rhosts_file () from /lib/libc.so.6
No symbol table info available.
`#2` 0x402fb7e6 in gnome_segv_handle (signum=11) at gnome-init.c:664
in gnome-init.c
estatus = 0
in_segv = 1
pid = 0
`#3` 0x405ba9f8 in killpg () from /lib/libc.so.6
No symbol table info available.
`#4` 0x40582f56 in g_strndup (str=0x1 <Address 0x1 out of bounds>, n=135164064)
at gstrfuncs.c:122
in gstrfuncs.c
n = 33791016
new_str = (gchar *) 0x80e70a0 "0"
`#5` 0x08051381 in toggle_menubar_cmd ()
No symbol table info available.
`#6` 0x40440fe7 in gtk_marshal_NONE__NONE (object=0x80cd890,
func=0x8051318 <toggle_menubar_cmd+840>, func_data=0x80b76d8,
args=0xbfffe170) at gtkmarshal.c:312
in gtkmarshal.c
No locals.
`#7` 0x40470706 in gtk_handlers_run (handlers=0x8066048, signal=0xbfffe110,
object=0x80cd890, params=0xbfffe170, after=0) at gtksignal.c:1917
in gtksignal.c
handlers = (GtkHandler *) 0x404e0434
handlers_next = (GtkHandler *) 0x0
```
------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-03-19 18:33 -------
The original reporter (pepe@usa.net) 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, hp@redhat.com.
Resolution: RESOLVED DUPLICATE
https://gitlab.gnome.org/GNOME/vte/-/issues/1732
crash in Terminal: vi of a text file
2021-06-10T14:17:55Z
Bugzilla
crash in Terminal: vi of a text file
## Submitted by nic..@..il.com
**[Link to original bug (#600577)](https://bugzilla.gnome.org/show_bug.cgi?id=600577)**
## Description
Version: 2.28.0
What were you doing when the application crashed?
vi of a text file
Distributi...
## Submitted by nic..@..il.com
**[Link to original bug (#600577)](https://bugzilla.gnome.org/show_bug.cgi?id=600577)**
## Description
Version: 2.28.0
What were you doing when the application crashed?
vi of a text file
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: dark-nimbus
Icon Theme: nimbus
GTK+ Modules: canberra-gtk-module, gnomebreakpad
Memory status: size: 150757376 vsize: 150757376 resident: 24657920 share: 2961408 rss: 24657920 rss_rlim: 0
CPU usage: start_time: 1257270220 rtime: 149 utime: 1198609 stime: 295806 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0
Backtrace was generated from '/usr/bin/gnome-terminal'
1279: gnome-terminal
----------------- lwp# 1 / thread# 1 --------------------
feef3d35 waitid (0, 543, 8046fe0, 3)
feea3305 waitpid (543, 804709c, 0, fed5b60d) + 65
fed5ba14 g_spawn_sync (0, 825dc60, 0, 4, 0, 0) + 418
fed5be28 g_spawn_command_line_sync (81def88, 0, 0, 0, 80471bc) + 5c
fdb21e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58a0, 4ff, 0, fdb21ff2) + f3
fdb220d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 8047244, feeee735, b, 0) + 12e
fdb21a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 80472f8, fecc2a00, fef81000, 80472b4) + 64
feeee735 __sighndlr (b, 0, 80472f8, fdb21a30) + 15
feee15ef call_user_handler (b) + 2af
feee181f sigacthandler (b, 0, 80472f8) + df
--- called from signal handler with signal 11 (SIGSEGV) ---
fd80ce63 _vte_terminal_ring_append (825c740, 0, b3, fd82f706) + 1f
fd82f81d vte_sequence_handler_cd (825c638, 0, 80475a8, fd832112) + 125
fd832178 vte_sequence_handler_erase_in_display (825c638, 8261750, f, fd83376a) + 74
fd833895 _vte_terminal_handle_sequence (825c638, 81cae68, 507, 8261750) + 139
fd812d99 vte_terminal_process_incoming (825c638, 0) + 405
fd82481c time_process_incoming (825c638, 1, 825c638, fd8248ae) + 2c
fd824a4c process_timeout (0, fedcc460, 8047748, fed26c71) + 1ac
fed26c87 g_timeout_dispatch (828e1b0, fd8248a0, 0, 80477c0) + 23
fed24eee g_main_context_dispatch (80cf750, 0, 8279e20, c) + 262
fed2559f g_main_context_iterate (80cf750, 1, 1, 80a6858) + 483
fed25bc9 g_main_loop_run (82498a0, 82498a0, 80a9800, fe37e726) + 1dd
fe37e7cf gtk_main (8047900, 0, 80aa2e4, feffb804, 80479a0, fefdcf48) + b7
0806b594 main (1, 8047a00, 8047a08, 80479bc) + 944
080677fd _start (1, 8047b10, 0, 8047b1f, 8047b65, 8047ba9) + 7d
----------------- lwp# 2 / thread# 2 --------------------
feef34d5 read (15, f5b5ef50, 14)
fed270c1 child_watch_helper_thread (0, 824d028, 200, fed4d1de) + 29
fed4d303 g_thread_create_proxy (824d028, fef81000, f5b5efe8, feeee36e) + 133
feeee3c3 _thrp_setup (fdcc0a00) + 9b
feeee650 _lwp_start (fdcc0a00, 0, 0, 0, 0, 0)
----------- .xsession-errors (267 sec old) ---------------------
(nautilus:1130): Gtk-WARNING **: About JDS: missing action About JDS
(nautilus:1130): Gtk-WARNING **: Go to Burn CD: missing action Go to Burn CD
(nautilus:1130): Gtk-CRITICAL **: file gtkwidget.c: line 6112: assertion `GTK_IS_WIDGET (widget)' failed
(nautilus:1130): Gtk-CRITICAL **: file gtkuimanager.c: line 1958: assertion `GTK_IS_MENU_SHELL (menushell)' failed
(nautilus:1130): Gtk-WARNING **: About JDS: missing action About JDS
Client shut down the connection owned by im_id(1).
Client shut down the connection owned by im_id(1).
Client shut down the connection owned by im_id(1).
nsHeaderInfo: registerSelf called!
nsHeaderInfo: registerSelf called!
--------------------------------------------------
Version: 0.22.x
Resolution: RESOLVED DUPLICATE
https://gitlab.gnome.org/GNOME/vte/-/issues/1731
crash in Terminal: vi /etc/hosts
2021-06-10T14:17:53Z
Bugzilla
crash in Terminal: vi /etc/hosts
## Submitted by nic..@..il.com
**[Link to original bug (#600436)](https://bugzilla.gnome.org/show_bug.cgi?id=600436)**
## Description
Version: 2.28.0
What were you doing when the application crashed?
vi /etc/hosts
Distribution: ...
## Submitted by nic..@..il.com
**[Link to original bug (#600436)](https://bugzilla.gnome.org/show_bug.cgi?id=600436)**
## Description
Version: 2.28.0
What were you doing when the application crashed?
vi /etc/hosts
Distribution: OpenSolaris Development snv_125 X86
Gnome Release: 2.28.0 2009-09-29 (Sun Microsystems, Inc.)
BugBuddy Version: 2.28.0
X Vendor: Sun Microsystems, Inc.
X Vendor Release: 10603000
Selinux: No
Accessibility: Disabled
GTK+ Theme: dark-nimbus
Icon Theme: nimbus
GTK+ Modules: canberra-gtk-module, gnomebreakpad
Memory status: size: 146755584 vsize: 146755584 resident: 20094976 share: 1675264 rss: 20094976 rss_rlim: 0
CPU usage: start_time: 1257175567 rtime: 21 utime: 164333 stime: 49992 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0
Backtrace was generated from '/usr/bin/gnome-terminal'
11796: gnome-terminal
----------------- lwp# 1 / thread# 1 --------------------
feef3e25 waitid (0, 2e24, 8046fe0, 3)
feea3305 waitpid (2e24, 804709c, 0, fed5b60d) + 65
fed5ba14 g_spawn_sync (0, 82808f0, 0, 4, 0, 0) + 418
fed5be28 g_spawn_command_line_sync (825de60, 0, 0, 0, 80471bc) + 5c
fdaf1e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58a0, 2e14, 0, fdaf1ff2) + f3
fdaf20d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 8047244, feeee825, b, 0) + 12e
fdaf1a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 80472f8, fecc2a00, fef81000, 80472b4) + 64
feeee825 __sighndlr (b, 0, 80472f8, fdaf1a30) + 15
feee15ef call_user_handler (b) + 2af
feee181f sigacthandler (b, 0, 80472f8) + df
--- called from signal handler with signal 11 (SIGSEGV) ---
fd7fce63 _vte_terminal_ring_append (81d4868, 0, 50, fd81f706) + 1f
fd81f81d vte_sequence_handler_cd (81d4760, 0, 80475a8, fd822112) + 125
fd822178 vte_sequence_handler_erase_in_display (81d4760, 827bb30, f, fd82376a) + 74
fd823895 _vte_terminal_handle_sequence (81d4760, 81d0eb0, 507, 827bb30) + 139
fd802d99 vte_terminal_process_incoming (81d4760, 0) + 405
fd81481c time_process_incoming (81d4760, 1, 81d4760, fd814ef6) + 2c
fd81509b update_timeout (0, fedcc460, 8047748, fed26c71) + 1b3
fed26c87 g_timeout_dispatch (827b5b0, fd814ee8, 0, 80477c0) + 23
fed24eee g_main_context_dispatch (80cbe38, 78, 81146f8, a) + 262
fed2559f g_main_context_iterate (80cbe38, 1, 1, 80a6858) + 483
fed25bc9 g_main_loop_run (825a488, 825a488, 80a9800, fe37e73a) + 1dd
fe37e7e3 gtk_main (3, 0, 80aa0fc, feffb804, 80479a0, fefdcf48) + b7
0806b594 main (1, 80479f8, 8047a00, 80479ec) + 944
080677fd _start (1, 8047b08, 0, 8047b17, 8047b63, 8047ba7) + 7d
----------------- lwp# 2 / thread# 2 --------------------
feef35c5 read (15, f5cbef50, 14)
fed270c1 child_watch_helper_thread (0, 8254a88, 200, fed4d1de) + 29
fed4d303 g_thread_create_proxy (8254a88, fef81000, f5cbefe8, feeee45e) + 133
feeee4b3 _thrp_setup (fdcb0a00) + 9b
feeee740 _lwp_start (fdcb0a00, 0, 0, 0, 0, 0)
----------- .xsession-errors (630102 sec old) ---------------------
** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 528: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 542: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 556: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 570: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 556: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 570: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 528: assertion `monitor >= 0 &
...Too much output, ignoring rest...
--------------------------------------------------
Version: 0.22.x
Resolution: RESOLVED DUPLICATE
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/1306
Doesn't handle background color/image/reset drops from nautilus.
2021-06-10T14:17:53Z
Bugzilla
Doesn't handle background color/image/reset drops from nautilus.
## Submitted by Alexander Larsson `@alexl`
Assigned to **Havoc Pennington**
**[Link to original bug (#75520)](https://bugzilla.gnome.org/show_bug.cgi?id=75520)**
## Description
Doesn't handle background color/image/reset drops fro...
## Submitted by Alexander Larsson `@alexl`
Assigned to **Havoc Pennington**
**[Link to original bug (#75520)](https://bugzilla.gnome.org/show_bug.cgi?id=75520)**
## Description
Doesn't handle background color/image/reset drops from nautilus.
Version: 1.9.x
Resolution: RESOLVED FIXED
2.0.0
https://gitlab.gnome.org/GNOME/vte/-/issues/1730
crash in Terminal: sudo vi /etc/hosts and t...
2021-06-10T14:17:50Z
Bugzilla
crash in Terminal: sudo vi /etc/hosts and t...
## Submitted by nic..@..il.com
**[Link to original bug (#600435)](https://bugzilla.gnome.org/show_bug.cgi?id=600435)**
## Description
Version: 2.28.0
What were you doing when the application crashed?
sudo vi /etc/hosts and then a b...
## Submitted by nic..@..il.com
**[Link to original bug (#600435)](https://bugzilla.gnome.org/show_bug.cgi?id=600435)**
## Description
Version: 2.28.0
What were you doing when the application crashed?
sudo vi /etc/hosts and then a bug report showed up!
Distribution: OpenSolaris Development snv_125 X86
Gnome Release: 2.28.0 2009-09-29 (Sun Microsystems, Inc.)
BugBuddy Version: 2.28.0
X Vendor: Sun Microsystems, Inc.
X Vendor Release: 10603000
Selinux: No
Accessibility: Disabled
GTK+ Theme: dark-nimbus
Icon Theme: nimbus
GTK+ Modules: canberra-gtk-module, gnomebreakpad
Memory status: size: 161087488 vsize: 161087488 resident: 32215040 share: 0 rss: 32215040 rss_rlim: 0
CPU usage: start_time: 1256545815 rtime: 52853 utime: 378354055 stime: 150182065 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0
Backtrace was generated from '/usr/bin/gnome-terminal'
3857: gnome-terminal
----------------- lwp# 1 / thread# 1 --------------------
feef3e25 waitid (0, 2df2, 8046fe0, 3)
feea3305 waitpid (2df2, 804709c, 0, fed5b60d) + 65
fed5ba14 g_spawn_sync (0, 8ef9328, 0, 4, 0, 0) + 418
fed5be28 g_spawn_command_line_sync (8e0dfc8, 0, 0, 0, 80471bc) + 5c
fdaf1e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58a0, f11, 0, fdaf1ff2) + f3
fdaf20d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 8047244, feeee825, b, 0) + 12e
fdaf1a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 80472f8, fecc2a00, fef81000, 80472b4) + 64
feeee825 __sighndlr (b, 0, 80472f8, fdaf1a30) + 15
feee15ef call_user_handler (b) + 2af
feee181f sigacthandler (b, 0, 80472f8) + df
--- called from signal handler with signal 11 (SIGSEGV) ---
fd7ece63 _vte_terminal_ring_append (8e4ef10, 0, 50, fd80f706) + 1f
fd80f81d vte_sequence_handler_cd (8e4ee08, 0, 80475a8, fd812112) + 125
fd812178 vte_sequence_handler_erase_in_display (8e4ee08, 8175780, f, fd81376a) + 74
fd813895 _vte_terminal_handle_sequence (8e4ee08, 81d16b0, 507, 8175780) + 139
fd7f2d99 vte_terminal_process_incoming (8e4ee08, 0) + 405
fd80481c time_process_incoming (8e4ee08, 1, 8e4ee08, fd8048ae) + 2c
fd804a4c process_timeout (0, fedcc460, 8047748, fed26c71) + 1ac
fed26c87 g_timeout_dispatch (89953b0, fd8048a0, 0, 80477c0) + 23
fed24eee g_main_context_dispatch (80cbe38, 0, 8e54008, a) + 262
fed2559f g_main_context_iterate (80cbe38, 1, 1, 80a6858) + 483
fed25bc9 g_main_loop_run (825a978, 825a978, 80a9800, fe37e73a) + 1dd
fe37e7e3 gtk_main (fefd4e56, 0, 80aa0f4, feffb804, 80479a0, fefdcf48) + b7
0806b594 main (1, 80479fc, 8047a04, feffb804) + 944
080677fd _start (1, 8047b0c, 0, 8047b1b, 8047b63, 8047ba7) + 7d
----------------- lwp# 2 / thread# 2 --------------------
feef35c5 read (15, f5caef50, 14)
fed270c1 child_watch_helper_thread (0, 8254fc8, 200, fed4d1de) + 29
fed4d303 g_thread_create_proxy (8254fc8, fef81000, f5caefe8, feeee45e) + 133
feeee4b3 _thrp_setup (fdcb0a00) + 9b
feeee740 _lwp_start (fdcb0a00, 0, 0, 0, 0, 0)
---- Critical and fatal warnings logged during execution ----
** Gtk **: file gtkwidget.c: line 7009: assertion `stock_id != NULL' failed
** Gtk **: file gtkwidget.c: line 7009: assertion `stock_id != NULL' failed
** Gtk **: file gtkwidget.c: line 7009: assertion `stock_id != NULL' failed
** Gtk **: file gtkwidget.c: line 7009: assertion `stock_id != NULL' failed
** Gtk **: file gtkwidget.c: line 7009: assertion `stock_id != NULL' failed
----------- .xsession-errors (630060 sec old) ---------------------
** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 528: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 542: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 556: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 570: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 556: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 570: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 528: assertion `monitor >= 0 &
...Too much output, ignoring rest...
--------------------------------------------------
Version: 0.22.x
Resolution: RESOLVED DUPLICATE
https://gitlab.gnome.org/GNOME/vte/-/issues/1729
Jerky input after kernel update
2021-06-10T14:17:48Z
Bugzilla
Jerky input after kernel update
## Submitted by Oleg Andreev
**[Link to original bug (#600414)](https://bugzilla.gnome.org/show_bug.cgi?id=600414)**
## Description
I recently updated Linux kernel from 2.6.28 to 2.6.31 and now all vte-based applications (including ...
## Submitted by Oleg Andreev
**[Link to original bug (#600414)](https://bugzilla.gnome.org/show_bug.cgi?id=600414)**
## Description
I recently updated Linux kernel from 2.6.28 to 2.6.31 and now all vte-based applications (including test application "vte", located in source package) react strangely to any user input.
To reproduce:
1. Run vte-based application on Linux-based system with kernel 2.6.31 (maybe, older kernels will be ok too).
2. Set your keyboard repeat rate to 30 (e.g. xset r rate 250 30).
3. Press and hold one key (e.g. 'q').
You will see, that the resulting output will be very jerky, sometimes two symbols will appear at once, sometimes there will be a noticeable lag between them. Booting the same system with 2.6.28 kernel results in smooth performance, no lags noticed.
I am a really amateur developer, but I tried to find out a bit on this bug and it seems, that this bug is triggered by scheduler/tty rewrite in recent kernels.
I really do not understand very much the difference between process_timeout/update_timeout/update_repeat_timeout, so correct me if I am wrong.
1. After receiving keypress event, vte write the corresponding data in the pty via vte_terminal_send.
2. After a time, pty responds with 'data available' signal and therefore vte_terminal_io_read function is run.
3. Either process_timeout, update_timeout or update_repeat_timeout is called after some time (I do not really understand the difference between those three), repainting the screen.
The problem arises in the fact, that the time between steps 1 and 2 is rather random (from 5 to 30 ms on my machine) and then, the time between step 2 and 3 also varies from 0 to 30 ms, therefore input character can appear on screen anytime between 5 to 60 ms after the user presses the key, resulting in the lag.
Setting the corresponding constants for timeouts (VTE_DISPLAY_TIMEOUT, VTE_UPDATE_TIMEOUT, VTE_UPDATE_REPEAT_TIMEOUT) to 5ms in vte-private.h removes the bug completely.
I have a side question. VTE_DISPLAY_TIMEOUT (the interval for process_timeout handler) is set to 10 ms by default, but the real interval between calls to process_timeout are no less than 60 ms. Is this the desired behaviour?
Sorry, if my explanations are a bit hard to understand, but I do not have enough time to investigate this behaviour further.
I would really appreciate any feedback.
Resolution: RESOLVED INCOMPLETE
https://gitlab.gnome.org/GNOME/vte/-/issues/1728
crash in Terminal: Started zsh as an ordina...
2021-06-10T14:17:44Z
Bugzilla
crash in Terminal: Started zsh as an ordina...
## Submitted by tho..@..hax.se
**[Link to original bug (#600406)](https://bugzilla.gnome.org/show_bug.cgi?id=600406)**
## Description
Version: 2.28.0
What were you doing when the application crashed?
Started zsh as an ordinary user...
## Submitted by tho..@..hax.se
**[Link to original bug (#600406)](https://bugzilla.gnome.org/show_bug.cgi?id=600406)**
## Description
Version: 2.28.0
What were you doing when the application crashed?
Started zsh as an ordinary user
Distribution: Solaris Express Community Edition snv_126 X86
Gnome Release: 2.28.0 2009-10-12 (Sun Microsystems, Inc.)
BugBuddy Version: 2.28.0
X Vendor: Sun Microsystems, Inc.
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: nimbus
Icon Theme: nimbus
GTK+ Modules: canberra-gtk-module, gnomebreakpad
Memory status: size: 92811264 vsize: 92811264 resident: 21180416 share: 4751360 rss: 21180416 rss_rlim: 0
CPU usage: start_time: 1257164171 rtime: 25 utime: 214604 stime: 41634 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0
Backtrace was generated from '/usr/bin/gnome-terminal'
11690: gnome-terminal
----------------- lwp# 1 / thread# 1 --------------------
feef3d35 waitid (0, 2db3, 8046530, 3)
feea3305 waitpid (2db3, 80465ec, 0, fed5b60d) + 65
fed5ba14 g_spawn_sync (0, 82a2628, 0, 4, 0, 0) + 418
fed5be28 g_spawn_command_line_sync (82a4130, 0, 0, 0, 804670c) + 5c
fdfc1e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a5978, 2daa, 0, fdfc1ff2) + f3
fdfc20d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 8046794, feeee735, b, 0) + 12e
fdfc1a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 8046848, fecc2a00, fef81000, 8046804) + 64
feeee735 __sighndlr (b, 0, 8046848, fdfc1a30) + 15
feee15ef call_user_handler (b) + 2af
feee181f sigacthandler (b, 0, 8046848) + df
--- called from signal handler with signal 11 (SIGSEGV) ---
fdcace63 _vte_terminal_ring_append (81cf508, 0, 50, fdccf706) + 1f
fdccf81d vte_sequence_handler_cd (81cf400, 0, 8046af8, fdcd2112) + 125
fdcd2178 vte_sequence_handler_erase_in_display (81cf400, 829ef60, f, fdcd376a) + 74
fdcd3895 _vte_terminal_handle_sequence (81cf400, 81cac78, 512, 829ef60) + 139
fdcb2d99 vte_terminal_process_incoming (81cf400, 0) + 405
fdcc481c time_process_incoming (81cf400, 1, 81cf400, fdcc48ae) + 2c
fdcc4a4c process_timeout (0, fedcc460, 8046c98, fed26c71) + 1ac
fed26c87 g_timeout_dispatch (8297518, fdcc48a0, 0, 8046d10) + 23
fed24eee g_main_context_dispatch (80cac70, 0, 8290448, b) + 262
fed2559f g_main_context_iterate (80cac70, 1, 1, 80a6a28) + 483
fed25bc9 g_main_loop_run (8283188, 8283188, 80a9c00, fe97e726) + 1dd
fe97e7cf gtk_main (3, 0, 80a98bc, feffb804, 8046ef0, fefdcf48) + b7
0806b594 main (1, 8046f48, 8046f50, 8046f3c) + 944
080677fd _start (1, 80470c4, 0, 80470d3, 804711d, 8047158) + 7d
----------------- lwp# 2 / thread# 2 --------------------
feef34d5 read (14, f910ef50, 14)
fed270c1 child_watch_helper_thread (0, 80b3468, 200, fed4d1de) + 29
fed4d303 g_thread_create_proxy (80b3468, fef81000, f910efe8, feeee36e) + 133
feeee3c3 _thrp_setup (fe180a00) + 9b
feeee650 _lwp_start (fe180a00, 0, 0, 0, 0, 0)
----------- .xsession-errors (924466 sec old) ---------------------
(nautilus:12124): Gtk-WARNING **: About JDS: missing action About JDS
Client shut down the connection owned by im_id(1).
Client shut down the connection owned by im_id(1).
(nautilus:12124): Gtk-WARNING **: Go to Burn CD: missing action Go to Burn CD
(nautilus:12124): Gtk-CRITICAL **: file gtkwidget.c: line 6112: assertion `GTK_IS_WIDGET (widget)' failed
(nautilus:12124): Gtk-CRITICAL **: file gtkuimanager.c: line 1958: assertion `GTK_IS_MENU_SHELL (menushell)' failed
(nautilus:12124): Gtk-WARNING **: About JDS: missing action About JDS
Client shut down the connection owned by im_id(1).
Client shut down the connection owned by im_id(1).
** (gnome-power-manager:12152): WARNING **: ERROR: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the
--------------------------------------------------
Version: 0.22.x
Resolution: RESOLVED DUPLICATE
https://gitlab.gnome.org/GNOME/vte/-/issues/1727
crash in Terminal: Opening gnome-terminal i...
2021-06-10T14:17:42Z
Bugzilla
crash in Terminal: Opening gnome-terminal i...
## Submitted by zhw..@..il.com
**[Link to original bug (#600229)](https://bugzilla.gnome.org/show_bug.cgi?id=600229)**
## Description
Version: 2.28.0
What were you doing when the application crashed?
Opening gnome-terminal immediat...
## Submitted by zhw..@..il.com
**[Link to original bug (#600229)](https://bugzilla.gnome.org/show_bug.cgi?id=600229)**
## Description
Version: 2.28.0
What were you doing when the application crashed?
Opening gnome-terminal immediately after updating OS
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: dark-nimbus
Icon Theme: nimbus
GTK+ Modules: canberra-gtk-module, gnomebreakpad
Memory status: size: 145014784 vsize: 145014784 resident: 21037056 share: 2347008 rss: 21037056 rss_rlim: 0
CPU usage: start_time: 1257000683 rtime: 22 utime: 187295 stime: 34797 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0
Backtrace was generated from '/usr/bin/gnome-terminal'
4281: /usr/bin/gnome-terminal -x /bin/sh -c cd '/export/home/zi' && exec $SH
----------------- lwp# 1 / thread# 1 --------------------
feef3287 waitid (0, 10bf, 8047010, 3)
feea32f5 waitpid (10bf, 80470cc, 0, fed5b60d) + 65
fed5ba14 g_spawn_sync (0, 811f880, 0, 4, 0, 0) + 418
fed5be28 g_spawn_command_line_sync (81250e0, 0, 0, 0, 80471ec) + 5c
fdae1e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58e8, 10b9, 0, fdae1ff2) + f3
fdae20d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 8047274, feeee715, b, 0) + 12e
fdae1a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 8047328, fecc2a00, fef81000, 80472e4) + 64
feeee715 __sighndlr (b, 0, 8047328, fdae1a30) + 15
feee15df call_user_handler (b) + 2af
feee180f sigacthandler (b, 0, 8047328) + df
--- called from signal handler with signal 11 (SIGSEGV) ---
fd7dce63 _vte_terminal_ring_append (81c68f0, 0, 50, fd7ff706) + 1f
fd7ff81d vte_sequence_handler_cd (81c67e8, 0, 80475d8, fd802112) + 125
fd802178 vte_sequence_handler_erase_in_display (81c67e8, 8158ed0, f, fd80376a) + 74
fd803895 _vte_terminal_handle_sequence (81c67e8, 81cd6a8, 507, 8158ed0) + 139
fd7e2d99 vte_terminal_process_incoming (81c67e8, 0) + 405
fd7f481c time_process_incoming (81c67e8, 1, 81c67e8, fd7f48ae) + 2c
fd7f4a4c process_timeout (0, fedcc460, 8047778, fed26c71) + 1ac
fed26c87 g_timeout_dispatch (8113fd0, fd7f48a0, 0, 80477f0) + 23
fed24eee g_main_context_dispatch (80d1538, 0, 81a77f8, b) + 262
fed2559f g_main_context_iterate (80d1538, 1, 1, 80a6858) + 483
fed25bc9 g_main_loop_run (80a5798, 80a5798, 80a9800, fe37e726) + 1dd
fe37e7cf gtk_main (fefd4e56, 0, 810f014, feffb804, 80479d0, fefdcf48) + b7
0806b594 main (1, 8047a2c, 8047a44, feffb804) + 944
080677fd _start (5, 8047b48, 8047b60, 8047b63, 8047b6b, 8047b6e) + 7d
----------------- lwp# 2 / thread# 2 --------------------
feef2db7 read (15, f5caef50, 14)
fed270c1 child_watch_helper_thread (0, 80b3708, 200, fed4d1de) + 29
fed4d303 g_thread_create_proxy (80b3708, fef81000, f5caefe8, feeee35e) + 133
feeee3b3 _thrp_setup (fdca0a00) + 9b
feeee640 _lwp_start (fdca0a00, 0, 0, 0, 0, 0)
----------- .xsession-errors (13 sec old) ---------------------
(nautilus:4172): Gtk-CRITICAL **: file gtknotebook.c: line 6894: assertion `GTK_IS_WIDGET (child)' failed
** (nautilus:4172): CRITICAL **: file nautilus-notebook.c: line 271: assertion `GTK_IS_WIDGET (tab_label)' failed
(nautilus:4172): Gtk-WARNING **: Go to Burn CD: missing action Go to Burn CD
(nautilus:4172): Gtk-CRITICAL **: file gtkwidget.c: line 6112: assertion `GTK_IS_WIDGET (widget)' failed
(nautilus:4172): Gtk-CRITICAL **: file gtkuimanager.c: line 1958: assertion `GTK_IS_MENU_SHELL (menushell)' failed
(nautilus:4172): Gtk-WARNING **: About JDS: missing action About JDS
Client shut down the connection owned by im_id(1).
Client shut down the connection owned by im_id(1).
Client shut down the connection owned by im_id(1).
Client shut down the connection owned by im_id(1).
--------------------------------------------------
Version: 0.22.x
Resolution: RESOLVED DUPLICATE
https://gitlab.gnome.org/GNOME/vte/-/issues/1726
crash in Terminal: started ssh session
2021-06-10T14:17:39Z
Bugzilla
crash in Terminal: started ssh session
## Submitted by Alex
**[Link to original bug (#599898)](https://bugzilla.gnome.org/show_bug.cgi?id=599898)**
## Description
Version: 2.28.0
What were you doing when the application crashed?
started ssh session
Distribution: ...
## Submitted by Alex
**[Link to original bug (#599898)](https://bugzilla.gnome.org/show_bug.cgi?id=599898)**
## Description
Version: 2.28.0
What were you doing when the application crashed?
started ssh session
Distribution: Solaris Express Community Edition snv_126 X86
Gnome Release: 2.28.0 2009-10-12 (Sun Microsystems, Inc.)
BugBuddy Version: 2.28.0
X Vendor: Sun Microsystems, Inc.
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Simple
Icon Theme: Mist
GTK+ Modules: canberra-gtk-module, gnomebreakpad
Memory status: size: 49418240 vsize: 49418240 resident: 24920064 share: 4243456 rss: 24920064 rss_rlim: 0
CPU usage: start_time: 1256527382 rtime: 5919 utime: 47513986 stime: 11676256 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0
Backtrace was generated from '/usr/bin/gnome-terminal'
6707: gnome-terminal --sm-client-id 10d68f4468c79083d01246587520553780000000
----------------- lwp# 1 / thread# 1 --------------------
feef3d35 waitid (0, 6871, 80463b0, 3)
feea3305 waitpid (6871, 804646c, 0, fed5b60d) + 65
fed5ba14 g_spawn_sync (0, 822cf38, 0, 4, 0, 0) + 418
fed5be28 g_spawn_command_line_sync (83ffa30, 0, 0, 0, 804658c) + 5c
fdac1e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58a0, 1a33, 0, fdac1ff2) + f3
fdac20d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 8046614, feeee735, b, 0) + 12e
fdac1a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 80466c8, fecc2a00, fef81000, 8046684) + 64
feeee735 __sighndlr (b, 0, 80466c8, fdac1a30) + 15
feee15ef call_user_handler (b) + 2af
feee181f sigacthandler (b, 0, 80466c8) + df
--- called from signal handler with signal 11 (SIGSEGV) ---
fd78ce63 _vte_terminal_ring_append (83ac0c8, 0, 6a, fd7af706) + 1f
fd7af81d vte_sequence_handler_cd (83abfc0, 0, 8046978, fd7b2112) + 125
fd7b2178 vte_sequence_handler_erase_in_display (83abfc0, 82c4850, f, fd7b376a) + 74
fd7b3895 _vte_terminal_handle_sequence (83abfc0, 8197dd0, 501, 82c4850) + 139
fd792d99 vte_terminal_process_incoming (83abfc0, 0) + 405
fd7a481c time_process_incoming (83abfc0, 1, 83abfc0, fd7a48ae) + 2c
fd7a4a4c process_timeout (0, fedcc460, 8046b18, fed26c71) + 1ac
fed26c87 g_timeout_dispatch (8276b00, fd7a48a0, 0, 8046b90) + 23
fed24eee g_main_context_dispatch (80c9b80, 0, 82fa908, a) + 262
fed2559f g_main_context_iterate (80c9b80, 1, 1, 80a6858) + 483
fed25bc9 g_main_loop_run (823f3d8, 823f3d8, 80a9800, fe37e726) + 1dd
fe37e7cf gtk_main (3, 0, 80e5c54, feffb804, 8046d70, fefdcf48) + b7
0806b594 main (1, 8046dc8, 8046dd8, 8046dbc) + 944
080677fd _start (3, 8046f34, 0, 0, 0, 8046f83) + 7d
----------------- lwp# 2 / thread# 2 --------------------
feef34d5 read (14, fbbcef50, 14)
fed270c1 child_watch_helper_thread (0, 82479b8, 200, fed4d1de) + 29
fed4d303 g_thread_create_proxy (82479b8, fef81000, fbbcefe8, feeee36e) + 133
feeee3c3 _thrp_setup (fdc60a00) + 9b
feeee650 _lwp_start (fdc60a00, 0, 0, 0, 0, 0)
Version: 0.22.x
Resolution: RESOLVED DUPLICATE
https://gitlab.gnome.org/GNOME/vte/-/issues/1725
^C/^Z keybindings don`t work with non-latin keymap as main
2021-06-10T14:17:37Z
Bugzilla
^C/^Z keybindings don`t work with non-latin keymap as main
## Submitted by Paul 'VeGeek' Lubetsky
**[Link to original bug (#599894)](https://bugzilla.gnome.org/show_bug.cgi?id=599894)**
## Description
^C/^Z keybindings are necessary for the normal terminal usage. But when the first xkb grou...
## Submitted by Paul 'VeGeek' Lubetsky
**[Link to original bug (#599894)](https://bugzilla.gnome.org/show_bug.cgi?id=599894)**
## Description
^C/^Z keybindings are necessary for the normal terminal usage. But when the first xkb group doesn`t include latin symbols, they simply stop working.
Example: do
setxkbmap us,ru -option grp:caps_toggle /* works nice */
setxkbmap ru,us -option grp:caps_toggle /* we get "яс" symbols instead of sending SIGINT and SIGSTOP */
rxvt/xterm/konsole work well. Other gtk-based applications also handle these keybindings well.
Version: 0.20.x
Resolution: RESOLVED DUPLICATE
https://gitlab.gnome.org/GNOME/vte/-/issues/1724
crash in Terminal:
2021-06-10T14:17:35Z
Bugzilla
crash in Terminal:
## Submitted by gio..@..pmn.it
**[Link to original bug (#599798)](https://bugzilla.gnome.org/show_bug.cgi?id=599798)**
## Description
Version: 2.28.0
What were you doing when the application crashed?
Distribution: ...
## Submitted by gio..@..pmn.it
**[Link to original bug (#599798)](https://bugzilla.gnome.org/show_bug.cgi?id=599798)**
## Description
Version: 2.28.0
What were you doing when the application crashed?
Distribution: OpenSolaris Development snv_125 X86
Gnome Release: 2.28.0 2009-09-29 (Sun Microsystems, Inc.)
BugBuddy Version: 2.28.0
X Vendor: Sun Microsystems, Inc.
X Vendor Release: 10603000
Selinux: No
Accessibility: Disabled
GTK+ Theme: nimbus
Icon Theme: nimbus
GTK+ Modules: canberra-gtk-module, gnomebreakpad
Memory status: size: 104898560 vsize: 104898560 resident: 20254720 share: 884736 rss: 20254720 rss_rlim: 0
CPU usage: start_time: 1256659824 rtime: 27 utime: 219015 stime: 53168 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0
Backtrace was generated from '/usr/bin/gnome-terminal'
1005: gnome-terminal
----------------- lwp# 1 / thread# 1 --------------------
feef3e25 waitid (0, 3f4, 8046fe0, 3)
feea3305 waitpid (3f4, 804709c, 0, fed5b60d) + 65
fed5ba14 g_spawn_sync (0, 8270f60, 0, 4, 0, 0) + 418
fed5be28 g_spawn_command_line_sync (81231a0, 0, 0, 0, 80471bc) + 5c
fdaf1e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58a0, 3ed, 0, fdaf1ff2) + f3
fdaf20d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 8047244, feeee825, b, 0) + 12e
fdaf1a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 80472f8, fecc2a00, fef81000, 80472b4) + 64
feeee825 __sighndlr (b, 0, 80472f8, fdaf1a30) + 15
feee15ef call_user_handler (b) + 2af
feee181f sigacthandler (b, 0, 80472f8) + df
--- called from signal handler with signal 11 (SIGSEGV) ---
fd7ece63 _vte_terminal_ring_append (81c4af0, 0, 50, fd80f706) + 1f
fd80f81d vte_sequence_handler_cd (81c49e8, 0, 8274d4c, fd812112) + 125
fd812178 vte_sequence_handler_erase_in_display (81c49e8, 0, f, fd81376a) + 74
fd813895 _vte_terminal_handle_sequence (81c49e8, 81c1e50, 50b, 0) + 139
fd7f2d99 vte_terminal_process_incoming (81c49e8, 0) + 405
fd80481c time_process_incoming (81c49e8, 1, 81c49e8, fd8048ae) + 2c
fd804a4c process_timeout (0, fedcc460, 8047748, fed26c71) + 1ac
fed26c87 g_timeout_dispatch (82512c0, fd8048a0, 0, 80477c0) + 23
fed24eee g_main_context_dispatch (80d1b50, 0, 81bffa0, b) + 262
fed2559f g_main_context_iterate (80d1b50, 1, 1, 80a6858) + 483
fed25bc9 g_main_loop_run (824a2a0, 824a2a0, 80a9800, fe37e73a) + 1dd
fe37e7e3 gtk_main (feffb804, 0, 80aa0f4, feffb804, 80479a0, fefdcf48) + b7
0806b594 main (1, 80479f4, 80479fc, 806779f) + 944
080677fd _start (1, 8047b08, 0, 8047b17, 8047b60, 8047ba2) + 7d
----------------- lwp# 2 / thread# 2 --------------------
feef35c5 read (15, f848ef50, 14)
fed270c1 child_watch_helper_thread (0, 80b3680, 200, fed4d1de) + 29
fed4d303 g_thread_create_proxy (80b3680, fef81000, f848efe8, feeee45e) + 133
feeee4b3 _thrp_setup (fdcb0a00) + 9b
feeee740 _lwp_start (fdcb0a00, 0, 0, 0, 0, 0)
----------- .xsession-errors (887 sec old) ---------------------
Client shut down the connection owned by im_id(1).
Client shut down the connection owned by im_id(1).
Client shut down the connection owned by im_id(1).
Client shut down the connection owned by im_id(1).
** (evolution:804): WARNING **: bbdb: failed to open addressbook: EBookStatus returned 20
Client shut down the connection owned by im_id(1).
Client shut down the connection owned by im_id(1).
Client shut down the connection owned by im_id(1).
Client shut down the connection owned by im_id(1).
Client shut down the connection owned by im_id(1).
Client shut down the connection owned by im_id(1).
Client shut down the connection owned by im_id(1).
Client shut down the connection owned by im_id(1).
--------------------------------------------------
Version: 0.22.x
Resolution: RESOLVED DUPLICATE
https://gitlab.gnome.org/GNOME/vte/-/issues/1723
crash in Terminal: during the failure I max...
2021-06-10T14:17:32Z
Bugzilla
crash in Terminal: during the failure I max...
## Submitted by jyr..@..uik.eu
**[Link to original bug (#599760)](https://bugzilla.gnome.org/show_bug.cgi?id=599760)**
## Description
Version: 2.28.0
What were you doing when the application crashed?
during the failure I maximised ...
## Submitted by jyr..@..uik.eu
**[Link to original bug (#599760)](https://bugzilla.gnome.org/show_bug.cgi?id=599760)**
## Description
Version: 2.28.0
What were you doing when the application crashed?
during the failure I maximised the Terminal's window.
Distribution: Solaris Express Community Edition snv_125 X86
Gnome Release: 2.28.0 2009-09-28 (Sun Microsystems, Inc.)
BugBuddy Version: 2.28.0
X Vendor: Sun Microsystems, Inc.
X Vendor Release: 10603000
Selinux: No
Accessibility: Disabled
GTK+ Theme: nimbus
Icon Theme: nimbus
GTK+ Modules: canberra-gtk-module, gnomebreakpad
Memory status: size: 149417984 vsize: 149417984 resident: 22327296 share: 2809856 rss: 22327296 rss_rlim: 0
CPU usage: start_time: 1256628943 rtime: 329 utime: 2881594 stime: 414574 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0
Backtrace was generated from '/usr/bin/gnome-terminal'
2333: gnome-terminal
----------------- lwp# 1 / thread# 1 --------------------
feef3e25 waitid (0, 1e5f, 80470a0, 3)
feea3305 waitpid (1e5f, 804715c, 0, fed5b60d) + 65
fed5ba14 g_spawn_sync (0, 82fe2f0, 0, 4, 0, 0) + 418
fed5be28 g_spawn_command_line_sync (82713c8, 0, 0, 0, 804727c) + 5c
fdae1e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58a0, 91d, 0, fdae1ff2) + f3
fdae20d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 8047304, feeee825, b, 0) + 12e
fdae1a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 80473b8, fecc2a00, fef81000, 8047374) + 64
feeee825 __sighndlr (b, 0, 80473b8, fdae1a30) + 15
feee15ef call_user_handler (b) + 2af
feee181f sigacthandler (b, 0, 80473b8) + df
--- called from signal handler with signal 11 (SIGSEGV) ---
fd7cce63 _vte_terminal_ring_append (82f7108, 0, b1, fd7ef706) + 1f
fd7ef81d vte_sequence_handler_cd (82f7000, 0, 8047648, fd7f2112) + 125
fd7f2178 vte_sequence_handler_erase_in_display (82f7000, 826be10, f, fd7f376a) + 74
fd7f3895 _vte_terminal_handle_sequence (82f7000, 81d0370, 50b, 826be10) + 139
fd7d2d99 vte_terminal_process_incoming (82f7000, 0) + 405
fd7e481c time_process_incoming (82f7000, 1, 82f7000, fd7e4ef6) + 2c
fd7e509b update_timeout (0, fedcc460, 8047808, fed26c71) + 1b3
fed26c87 g_timeout_dispatch (8284e28, fd7e4ee8, 0, 8047880) + 23
fed24eee g_main_context_dispatch (80d0750, 78, 825a3b8, c) + 262
fed2559f g_main_context_iterate (80d0750, 1, 1, 80a6858) + 483
fed25bc9 g_main_loop_run (825c5d0, 825c5d0, 80a9800, fe37e73a) + 1dd
fe37e7e3 gtk_main (80479c0, 0, 80aa144, feffb804, 8047a60, fefdcf48) + b7
0806b594 main (1, 8047ac0, 8047ac8, 8047a7c) + 944
080677fd _start (1, 8047bbc, 0, 8047bcb, 8047c14, 8047c54) + 7d
----------------- lwp# 2 / thread# 2 --------------------
feef35c5 read (15, f7dfef50, 14)
fed270c1 child_watch_helper_thread (0, 8248968, 200, fed4d1de) + 29
fed4d303 g_thread_create_proxy (8248968, fef81000, f7dfefe8, feeee45e) + 133
feeee4b3 _thrp_setup (fdc90a00) + 9b
feeee740 _lwp_start (fdc90a00, 0, 0, 0, 0, 0)
----------- .xsession-errors (27 sec old) ---------------------
(nautilus:2013): libgnomevfs-CRITICAL **: file gnome-vfs-uri.c: line 1346: assertion `uri != NULL' failed
(nautilus:2013): libgnomevfs-CRITICAL **: file gnome-vfs-uri.c: line 1018: assertion `uri != NULL' failed
(nautilus:2013): Gtk-WARNING **: Go to Burn CD: missing action Go to Burn CD
(nautilus:2013): Gtk-CRITICAL **: file gtkwidget.c: line 6112: assertion `GTK_IS_WIDGET (widget)' failed
(nautilus:2013): Gtk-CRITICAL **: file gtkuimanager.c: line 1958: assertion `GTK_IS_MENU_SHELL (menushell)' failed
(nautilus:2013): Gtk-WARNING **: About JDS: missing action About JDS
Failed to initialize GEM. Falling back to classic.
(soffice:7405): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
Aknahalduri hoiatus: from event callback
--------------------------------------------------
Version: 0.22.x
Resolution: RESOLVED DUPLICATE
https://gitlab.gnome.org/GNOME/vte/-/issues/1722
CTRL-Home, CTRL-End simply sends Home and End to apps
2021-06-10T14:17:30Z
Bugzilla
CTRL-Home, CTRL-End simply sends Home and End to apps
## Submitted by Peter Valdemar Mørch
**[Link to original bug (#599634)](https://bugzilla.gnome.org/show_bug.cgi?id=599634)**
## Description
In "vim" and "emacs -nw" hitting CTRL-Home and CTRL-End sends the exact same bytes[1] as hit...
## Submitted by Peter Valdemar Mørch
**[Link to original bug (#599634)](https://bugzilla.gnome.org/show_bug.cgi?id=599634)**
## Description
In "vim" and "emacs -nw" hitting CTRL-Home and CTRL-End sends the exact same bytes[1] as hitting Home and End respectively to apps. Therefore, CTRL-Home and CTRL-End don't work in neither vim nor "emacs -nw" under gnome-terminal. They work fine under xterm.
Using the short perl snippet below[2], gnome-terminal produces this same output hitting either Home or CTRL-Home:
Decimal: 27 Hex: 1b
Decimal: 79 Hex: 4f
Decimal: 72 Hex: 48
xterm produces this output when I hit CTRL-Home:
Decimal: 27 Hex: 1b
Decimal: 91 Hex: 5b
Decimal: 49 Hex: 31
Decimal: 59 Hex: 3b
Decimal: 53 Hex: 35
Decimal: 72 Hex: 48
But xterm produces this output when I hit "just" Home:
Decimal: 27 Hex: 1b
Decimal: 91 Hex: 5b
Decimal: 72 Hex: 48
I don't know much about terminals, but I'm surprised that xterm and gnome-terminal send different things for just "Home". I'm also surprised that gnome-terminal sends the same things for both "Home" and "CTRL-Home". I expected gnome-terminal behavior to mimic xterm since TERM=xterm in both. But hey, I know so little about terminals, termcap etc.
I'm using a danish keyboard but have also tried reconfiguring to use a US keyboard. Same behavior.
Running up-to-date ubuntu jaunty with these versions:
vte: 1:0.20.0-0ubuntu2
gnome-terminal: 2.26.0-0ubuntu2.1
Looking through past bugs I found [bug 375112](https://bugzilla.gnome.org/show_bug.cgi?id=375112) : "ctrl-key combinations yielding just key", but the patch in there was already applied in my vte version. So that isn't it. (The explanation doesn't quite fit either)
I took the liberty of choosing a "major" severity, since it seems to me that CTRL-Home and CTRL-End is broken.
[1] I'm not sure what the "things" are called: "chars", "bytes", "keycodes" - terminal terminology is confusing to me
[2]
#!/usr/bin/perl -w
use Term::ReadKey;
ReadMode('cbreak');
print "Press keys to see their ASCII values. Use Ctrl-C to quit.\n";
while (1) {
$char = ReadKey(0);
last unless defined $char;
printf(" Decimal: %d\tHex: %x\n", ord($char), ord($char));
}
ReadMode('normal');
Version: 0.20.x
Resolution: RESOLVED DUPLICATE
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/1305
tab position setting?
2021-06-10T14:17:50Z
Bugzilla
tab position setting?
## Submitted by kz
**[Link to original bug (#75420)](https://bugzilla.gnome.org/show_bug.cgi?id=75420)**
## Description
Package: gnome-terminal
Severity: enhancement
Version: 1.9.1
Synopsis: tab position setting?
Bugzilla-Product: g...
## Submitted by kz
**[Link to original bug (#75420)](https://bugzilla.gnome.org/show_bug.cgi?id=75420)**
## Description
Package: gnome-terminal
Severity: enhancement
Version: 1.9.1
Synopsis: tab position setting?
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
Description:
now gnome-terminal seems to only top-tab.
what about to give options, like other tab-based apps?
------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-03-19 05:58 -------
Reassigning to the default owner of the component, hp@redhat.com.
Resolution: RESOLVED FIXED
https://gitlab.gnome.org/GNOME/vte/-/issues/1721
crash in Terminal: vi .bashrc
2021-06-10T14:17:26Z
Bugzilla
crash in Terminal: vi .bashrc
## Submitted by nic..@..il.com
**[Link to original bug (#599625)](https://bugzilla.gnome.org/show_bug.cgi?id=599625)**
## Description
Version: 2.28.0
What were you doing when the application crashed?
vi .bashrc
Distribution: ...
## Submitted by nic..@..il.com
**[Link to original bug (#599625)](https://bugzilla.gnome.org/show_bug.cgi?id=599625)**
## Description
Version: 2.28.0
What were you doing when the application crashed?
vi .bashrc
Distribution: OpenSolaris Development snv_125 X86
Gnome Release: 2.28.0 2009-09-29 (Sun Microsystems, Inc.)
BugBuddy Version: 2.28.0
X Vendor: Sun Microsystems, Inc.
X Vendor Release: 10603000
Selinux: No
Accessibility: Disabled
GTK+ Theme: dark-nimbus
Icon Theme: nimbus
GTK+ Modules: canberra-gtk-module, gnomebreakpad
Memory status: size: 146829312 vsize: 146829312 resident: 20668416 share: 1675264 rss: 20668416 rss_rlim: 0
CPU usage: start_time: 1256545799 rtime: 19 utime: 153099 stime: 40474 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0
Backtrace was generated from '/usr/bin/gnome-terminal'
3776: gnome-terminal
----------------- lwp# 1 / thread# 1 --------------------
feef3e25 waitid (0, f08, 8046fe0, 3)
feea3305 waitpid (f08, 804709c, 0, fed5b60d) + 65
fed5ba14 g_spawn_sync (0, 82948d8, 0, 4, 0, 0) + 418
fed5be28 g_spawn_command_line_sync (8266700, 0, 0, 0, 80471bc) + 5c
fdaf1e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58a0, ec0, 0, fdaf1ff2) + f3
fdaf20d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 8047244, feeee825, b, 0) + 12e
fdaf1a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 80472f8, fecc2a00, fef81000, 80472b4) + 64
feeee825 __sighndlr (b, 0, 80472f8, fdaf1a30) + 15
feee15ef call_user_handler (b) + 2af
feee181f sigacthandler (b, 0, 80472f8) + df
--- called from signal handler with signal 11 (SIGSEGV) ---
fd7fce63 _vte_terminal_ring_append (81d4ce0, 0, 50, fd81f706) + 1f
fd81f81d vte_sequence_handler_cd (81d4bd8, 0, 80475a8, fd822112) + 125
fd822178 vte_sequence_handler_erase_in_display (81d4bd8, 82901c0, f, fd82376a) + 74
fd823895 _vte_terminal_handle_sequence (81d4bd8, 81d16b0, 507, 82901c0) + 139
fd802d99 vte_terminal_process_incoming (81d4bd8, 0) + 405
fd81481c time_process_incoming (81d4bd8, 1, 81d4bd8, fd814ef6) + 2c
fd81509b update_timeout (0, fedcc460, 8047748, fed26c71) + 1b3
fed26c87 g_timeout_dispatch (8114e70, fd814ee8, 0, 80477c0) + 23
fed24eee g_main_context_dispatch (80cbe38, 78, 8113048, a) + 262
fed2559f g_main_context_iterate (80cbe38, 1, 1, 80a6858) + 483
fed25bc9 g_main_loop_run (825a508, 825a508, 80a9800, fe37e73a) + 1dd
fe37e7e3 gtk_main (fefd4e56, 0, 80aa0f4, feffb804, 80479a0, fefdcf48) + b7
0806b594 main (1, 80479fc, 8047a04, feffb804) + 944
080677fd _start (1, 8047b0c, 0, 8047b1b, 8047b63, 8047ba7) + 7d
----------------- lwp# 2 / thread# 2 --------------------
feef35c5 read (15, f5cbef50, 14)
fed270c1 child_watch_helper_thread (0, 8254b58, 200, fed4d1de) + 29
fed4d303 g_thread_create_proxy (8254b58, fef81000, f5cbefe8, feeee45e) + 133
feeee4b3 _thrp_setup (fdcb0a00) + 9b
feeee740 _lwp_start (fdcb0a00, 0, 0, 0, 0, 0)
----------- .xsession-errors (331 sec old) ---------------------
** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 528: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 542: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 556: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 570: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 556: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 570: assertion `monitor >= 0 && monitor < monitors [n_screen]' failed
** (gnome-panel:3533): CRITICAL **: file panel-multiscreen.c: line 528: assertion `monitor >= 0 &
...Too much output, ignoring rest...
--------------------------------------------------
Version: 0.22.x
Resolution: RESOLVED DUPLICATE
https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/1304
Copying in gnome-terminal causes a crash
2021-06-10T14:17:26Z
Bugzilla
Copying in gnome-terminal causes a crash
## Submitted by gfo..@..sf.edu
Assigned to **Havoc Pennington**
**[Link to original bug (#75278)](https://bugzilla.gnome.org/show_bug.cgi?id=75278)**
## Description
Package: gnome-terminal
Severity: major
Version: 1.4.0.6
Synopsis...
## Submitted by gfo..@..sf.edu
Assigned to **Havoc Pennington**
**[Link to original bug (#75278)](https://bugzilla.gnome.org/show_bug.cgi?id=75278)**
## Description
Package: gnome-terminal
Severity: major
Version: 1.4.0.6
Synopsis: Copying in gnome-terminal causes a crash
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
Description:
Highlighting text and then attempting to copy it using the switch on the
menu -- it crashes doing this every time I try it!
Debugging Information:
(no debugging symbols found)...0x40643e29 in __wait4 () from /lib/libc.so.6
```
`#0` 0x40643e29 in __wait4 () from /lib/libc.so.6
`#1` 0x406c0050 in __DTOR_END__ () from /lib/libc.so.6
`#2` 0x403007e6 in gnome_segv_handle (signum=11) at gnome-init.c:664
`#3` <signal handler called>
`#4` strncpy (s1=0x407a0008 "", s2=0x1 <Address 0x1 out of bounds>, n=134989600)
at ../sysdeps/generic/strncpy.c:41
`#5` 0x40586f56 in g_strndup (str=0x1 <Address 0x1 out of bounds>, n=134989600)
at gstrfuncs.c:122
`#6` 0x08051381 in toggle_menubar_cmd ()
`#7` 0x40444fe7 in gtk_marshal_NONE__NONE (object=0x80a2770,
func=0x8051318 <toggle_menubar_cmd+840>, func_data=0x808b550,
args=0xbfffe980) at gtkmarshal.c:312
`#8` 0x40474706 in gtk_handlers_run (handlers=0x8065090, signal=0xbfffe920,
object=0x80a2770, params=0xbfffe980, after=0) at gtksignal.c:1917
`#9` 0x40473b57 in gtk_signal_real_emit (object=0x80a2770, signal_id=86,
params=0xbfffe980) at gtksignal.c:1477
`#10` 0x40471bcc in gtk_signal_emit (object=0x80a2770, signal_id=86)
at gtksignal.c:552
`#11` 0x404a91bc in gtk_widget_activate (widget=0x80a2770) at gtkwidget.c:2890
`#12` 0x4044d32d in gtk_menu_shell_activate_item (menu_shell=0x80a2678,
menu_item=0x80a2770, force_deactivate=1) at gtkmenushell.c:859
`#13` 0x4044c5bd in gtk_menu_shell_button_release (widget=0x80a2678,
event=0x80ba2e0) at gtkmenushell.c:486
`#14` 0x40444dbd in gtk_marshal_BOOL__POINTER (object=0x80a2678,
func=0x4044c430 <gtk_menu_shell_button_release>, func_data=0x0,
args=0xbfffed50) at gtkmarshal.c:28
`#15` 0x40473b97 in gtk_signal_real_emit (object=0x80a2678, signal_id=27,
params=0xbfffed50) at gtksignal.c:1492
`#16` 0x40471bcc in gtk_signal_emit (object=0x80a2678, signal_id=27)
at gtksignal.c:552
`#17` 0x404a9084 in gtk_widget_event (widget=0x80a2678, event=0x80ba2e0)
at gtkwidget.c:2864
`#18` 0x40444d34 in gtk_propagate_event (widget=0x80a2770, event=0x80ba2e0)
at gtkmain.c:1378
`#19` 0x40443ef1 in gtk_main_do_event (event=0x80ba2e0) at gtkmain.c:818
`#20` 0x404ff16b in gdk_event_dispatch (source_data=0x0,
current_time=0xbffff120, user_data=0x0) at gdkevents.c:2139
`#21` 0x4057e055 in g_main_dispatch (dispatch_time=0xbffff120) at gmain.c:656
`#22` 0x4057e659 in g_main_iterate (block=1, dispatch=1) at gmain.c:877
`#23` 0x4057e7e8 in g_main_run (loop=0x807beb8) at gmain.c:935
`#24` 0x404437f7 in gtk_main () at gtkmain.c:524
`#25` 0x08053e91 in new_terminal_for_client ()
`#26` 0x08053ec3 in main ()
`#27` 0x405ac306 in __libc_start_main (main=0x8053e9c <main>, argc=3,
ubp_av=0xbffff274, init=0x804c6e0 <_init>, fini=0x8054980 <_fini>,
rtld_fini=0x4000d2dc <_dl_fini>, stack_end=0xbffff26c)
at ../sysdeps/generic/libc-start.c:129
`#0` 0x40643e29 in __wait4 () from /lib/libc.so.6
No locals.
`#1` 0x406c0050 in __DTOR_END__ () from /lib/libc.so.6
No symbol table info available.
`#2` 0x403007e6 in gnome_segv_handle (signum=11) at gnome-init.c:664
in gnome-init.c
estatus = 0
in_segv = 1
pid = 0
`#3` <signal handler called>
No locals.
`#4` strncpy (s1=0x407a0008 "", s2=0x1 <Address 0x1 out of bounds>, n=134989600)
at ../sysdeps/generic/strncpy.c:41
in ../sysdeps/generic/strncpy.c
n4 = 33747400
s1 = 0x0
s2 = 0xbfffe510 ""
n = 134989600
c = 0 '\000'
s = 0x407a0008 ""
s = 0x407a0008 ""
`#5` 0x40586f56 in g_strndup (str=0x1 <Address 0x1 out of bounds>, n=134989600)
at gstrfuncs.c:122
in gstrfuncs.c
n = 134989600
new_str = (gchar *) 0x407a0008 ""
`#6` 0x08051381 in toggle_menubar_cmd ()
No symbol table info available.
`#7` 0x40444fe7 in gtk_marshal_NONE__NONE (object=0x80a2770,
func=0x8051318 <toggle_menubar_cmd+840>, func_data=0x808b550,
args=0xbfffe980) at gtkmarshal.c:312
in gtkmarshal.c
No locals.
```
------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-03-18 09:02 -------
The original reporter (gfox@chuma1.cas.usf.edu) 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, hp@redhat.com.
Resolution: RESOLVED DUPLICATE
https://gitlab.gnome.org/GNOME/vte/-/issues/1720
crash in Terminal: sigh, I hope someone can...
2021-06-10T14:17:23Z
Bugzilla
crash in Terminal: sigh, I hope someone can...
## Submitted by che..@..un.com
**[Link to original bug (#599616)](https://bugzilla.gnome.org/show_bug.cgi?id=599616)**
## Description
Version: 2.28.0
What were you doing when the application crashed?
sigh, I hope someone can read t...
## Submitted by che..@..un.com
**[Link to original bug (#599616)](https://bugzilla.gnome.org/show_bug.cgi?id=599616)**
## Description
Version: 2.28.0
What were you doing when the application crashed?
sigh, I hope someone can read this. I was just switching between different tabs and doing very normal typing in the terminal window. It's very bad. Can anyone point me to the stable version?
Distribution: Solaris Express Community Edition snv_126 X86
Gnome Release: 2.28.0 2009-10-12 (Sun Microsystems, Inc.)
BugBuddy Version: 2.28.0
X Vendor: Sun Microsystems, Inc.
X Vendor Release: 10605000
Selinux: No
Accessibility: Disabled
GTK+ Theme: nimbus
Icon Theme: nimbus
GTK+ Modules: canberra-gtk-module, gnomebreakpad
Memory status: size: 178339840 vsize: 178339840 resident: 28135424 share: 798720 rss: 28135424 rss_rlim: 0
CPU usage: start_time: 1256276428 rtime: 5694 utime: 39579451 stime: 17368079 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0
Backtrace was generated from '/usr/bin/gnome-terminal'
5528: /usr/bin/gnome-terminal -x /bin/sh -c cd '/home/lc152243' && exec $SHE
----------------- lwp# 1 / thread# 1 --------------------
feef3287 waitid (0, 32c6, 80462a0, 3)
feea32f5 waitpid (32c6, 804635c, 0, fed5b60d) + 65
fed5ba14 g_spawn_sync (0, 83268b8, 0, 4, 0, 0) + 418
fed5be28 g_spawn_command_line_sync (83b8680, 0, 0, 0, 804647c) + 5c
fdd21e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58e8, 1598, 0, fdd21ff2) + f3
fdd220d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 8046504, feeee715, b, 0) + 12e
fdd21a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 80465b8, fecc2a00, fef81000, 8046574) + 64
feeee715 __sighndlr (b, 0, 80465b8, fdd21a30) + 15
feee15df call_user_handler (b) + 2af
feee180f sigacthandler (b, 0, 80465b8) + df
--- called from signal handler with signal 11 (SIGSEGV) ---
fda0ce63 _vte_terminal_ring_append (83459e0, 0, 59, fda2f706) + 1f
fda2f81d vte_sequence_handler_cd (83458d8, 0, 3a, fda32112) + 125
fda32178 vte_sequence_handler_erase_in_display (83458d8, 8353b30, f, fda3376a) + 74
fda33895 _vte_terminal_handle_sequence (83458d8, 81d2fb0, 50e, 8353b30) + 139
fda12d99 vte_terminal_process_incoming (83458d8, 0) + 405
fda2481c time_process_incoming (83458d8, 1, 83458d8, fda248ae) + 2c
fda24a4c process_timeout (0, fedcc460, 8046a08, fed26c71) + 1ac
fed26c87 g_timeout_dispatch (82ec1b0, fda248a0, 0, 8046a80) + 23
fed24eee g_main_context_dispatch (80c6d58, 0, 8544608, b) + 262
fed2559f g_main_context_iterate (80c6d58, 1, 1, 80a6858) + 483
fed25bc9 g_main_loop_run (80a5798, 80a5798, 80a8c00, fe57e726) + 1dd
fe57e7cf gtk_main (8046bc0, 0, 810ef3c, feffb804, 8046c60, fefdcf48) + b7
0806b594 main (1, 8046cc0, 8046cd8, 8046c7c) + 944
080677fd _start (5, 8046e0c, 8046e24, 8046e27, 8046e2f, 8046e32) + 7d
----------------- lwp# 2 / thread# 2 --------------------
feef2db7 read (15, f4ceef50, 14)
fed270c1 child_watch_helper_thread (0, 80b39a8, 200, fed4d1de) + 29
fed4d303 g_thread_create_proxy (80b39a8, fef81000, f4ceefe8, feeee35e) + 133
feeee3b3 _thrp_setup (fdee0a00) + 9b
feeee640 _lwp_start (fdee0a00, 0, 0, 0, 0, 0)
Version: 0.22.x
Resolution: RESOLVED DUPLICATE
https://gitlab.gnome.org/GNOME/vte/-/issues/1719
crash in Terminal: setting term vt100
2021-06-10T14:17:21Z
Bugzilla
crash in Terminal: setting term vt100
## Submitted by sla..@..dp.org
**[Link to original bug (#599450)](https://bugzilla.gnome.org/show_bug.cgi?id=599450)**
## Description
Version: 2.28.0
What were you doing when the application crashed?
setting term vt100
Distributi...
## Submitted by sla..@..dp.org
**[Link to original bug (#599450)](https://bugzilla.gnome.org/show_bug.cgi?id=599450)**
## Description
Version: 2.28.0
What were you doing when the application crashed?
setting term vt100
Distribution: OpenSolaris Development snv_125 X86
Gnome Release: 2.28.0 2009-09-29 (Sun Microsystems, Inc.)
BugBuddy Version: 2.28.0
X Vendor: Sun Microsystems, Inc.
X Vendor Release: 10603000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mist
Icon Theme: Mist
GTK+ Modules: canberra-gtk-module, gnomebreakpad
Memory status: size: 106041344 vsize: 106041344 resident: 28356608 share: 2781184 rss: 28356608 rss_rlim: 0
CPU usage: start_time: 1256324963 rtime: 11857 utime: 72304960 stime: 46267831 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0
Backtrace was generated from '/usr/bin/gnome-terminal'
1617: gnome-terminal
----------------- lwp# 1 / thread# 1 --------------------
feef3e25 waitid (0, 823, 8047070, 3)
feea3305 waitpid (823, 804712c, 0, fed5b60d) + 65
fed5ba14 g_spawn_sync (0, 87fde88, 0, 4, 0, 0) + 418
fed5be28 g_spawn_command_line_sync (87fbe38, 0, 0, 0, 804724c) + 5c
fdb81e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80a58a0, 651, 0, fdb81ff2) + f3
fdb820d6 __1cMcheck_if_gdb6F_v_ (fef81000, fef81000, 80472d4, feeee825, b, 0) + 12e
fdb81a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 8047388, fecc2a00, fef81000, 8047344) + 64
feeee825 __sighndlr (b, 0, 8047388, fdb81a30) + 15
feee15ef call_user_handler (b) + 2af
feee181f sigacthandler (b, 0, 8047388) + df
--- called from signal handler with signal 11 (SIGSEGV) ---
fd86ce63 _vte_terminal_ring_append (852db10, 0, 50, fd88f706) + 1f
fd88f81d vte_sequence_handler_cd (852da08, 0, 8047638, fd892112) + 125
fd892178 vte_sequence_handler_erase_in_display (852da08, 83b8740, f, fd89376a) + 74
fd893895 _vte_terminal_handle_sequence (852da08, 80d7b30, 506, 83b8740) + 139
fd872d99 vte_terminal_process_incoming (852da08, 0) + 405
fd88481c time_process_incoming (852da08, 1, 852da08, fd8848ae) + 2c
fd884a4c process_timeout (0, fedcc460, 80477d8, fed26c71) + 1ac
fed26c87 g_timeout_dispatch (87fe8b0, fd8848a0, 0, 8047850) + 23
fed24eee g_main_context_dispatch (80c26a8, 0, 8506f08, 1d) + 262
fed2559f g_main_context_iterate (80c26a8, 1, 1, 80a6858) + 483
fed25bc9 g_main_loop_run (8226d80, 8226d80, 80a9800, fe37e73a) + 1dd
fe37e7e3 gtk_main (feffb804, 0, 80c4314, feffb804, 8047a30, fefdcf48) + b7
0806b594 main (1, 8047a84, 8047a8c, 806779f) + 944
080677fd _start (1, 8047b8c, 0, 8047b9b, 8047be2, 8047c23) + 7d
----------------- lwp# 2 / thread# 2 --------------------
feef35c5 read (15, f8b1ef50, 14)
fed270c1 child_watch_helper_thread (0, 8230610, 200, fed4d1de) + 29
fed4d303 g_thread_create_proxy (8230610, fef81000, f8b1efe8, feeee45e) + 133
feeee4b3 _thrp_setup (fdcf0a00) + 9b
feeee740 _lwp_start (fdcf0a00, 0, 0, 0, 0, 0)
----------- .xsession-errors (72531 sec old) ---------------------
(firefox-bin:990): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:990): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:990): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:990): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:990): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:990): Gdk-WARNING **: XID collision, trouble ahead
(firefox-bin:990): Gdk-WARNING **: XID collision, trouble ahead
...Too much output, ignoring rest...
--------------------------------------------------
Version: 0.22.x
Resolution: RESOLVED DUPLICATE
https://gitlab.gnome.org/GNOME/vte/-/issues/1718
Scrollback index type mess
2021-06-10T14:17:18Z
Bugzilla
Scrollback index type mess
## Submitted by Behdad Esfahbod `@behdad`
**[Link to original bug (#599444)](https://bugzilla.gnome.org/show_bug.cgi?id=599444)**
## Description
The deltas used to be glong. I changed them to guint. The API still has glong, so we ...
## Submitted by Behdad Esfahbod `@behdad`
**[Link to original bug (#599444)](https://bugzilla.gnome.org/show_bug.cgi?id=599444)**
## Description
The deltas used to be glong. I changed them to guint. The API still has glong, so we can get overflows, etc. All should be changed to gulong instead.
Resolution: RESOLVED FIXED