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 139741 - gnome-terminal crashes while inserting text
gnome-terminal crashes while inserting text
Status: RESOLVED DUPLICATE of bug 139030
Product: gnome-terminal
Classification: Core
Component: general
2.6.x
Other Linux
: Normal major
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2004-04-11 19:30 UTC by kir
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description kir 2004-04-11 19:30:19 UTC
gnome-terminal crashes while trying to insert big amount of text from clipboard.
This bug was already filed by me to redhat's bugzilla: see
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=119099


The bug is easy to reproduce
----------------------------
1. Open http://slashdot.org/ (or http://freshmeat.net/) in Mozilla.
Press Ctrl-A to select all text and copy it to clipboard.
2. Open xterm, type in export LANG=ru_RU.KOI8-R
2. Run gnome-terminal from xterm, type vim xxxx (where xxxx is
non-existing file name), press i to enter insert mode in vim.
3. Click Shift+Middle_Mouse_Button in gnome-terminal to insert the
text from clipboard. Nothing happens, gnome-terminal just issues a
warning about invalid UTF-8 string. Click Shift+MidButton again. See app segfault.


Versions of applicable software
-------------------------------
[kir@kir kir]$  rpm -q glib2 gtk2 atk pango glibc gnome-terminal glibc
glib2-2.4.0-1
gtk2-2.4.0-1
atk-1.6.0-1
pango-1.4.0-1
glibc-2.3.3-17
gnome-terminal-2.6.0-1
glibc-2.3.3-17


Below is the full backtrace; feel free to ask more info.

Debugging session
-----------------
$ gdb gnome-terminal
GNU gdb Red Hat Linux (5.3post-0.20021129.18rh)
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i386-asplinux-linux-gnu"...
(no debugging symbols found)...
(gdb) r
Starting program: /usr/bin/gnome-terminal 
[New Thread 1089147584 (LWP 5626)]

==== this happens after the first attempt to insert text from slashdot ====

** (gnome-terminal:5626): WARNING **: [Invalid UTF-8]
\xd2\xcf\xc9\xc9\xda\xcf\xdb\xcc\xc1 \xcf\xdb\xc9\xc2\xcb\xc1 (Invalid or
incomplete multibyte or wide character) \xd0\xd2\xc9
\xd0\xd2\xc5\xcf\xc2\xd2\xc1\xda\xcf\xd7\xc1\xce\xc9\xc9
\xc4\xc1\xce\xce\xd9\xc8 \xcf\xd4 \xd0\xcf\xd4\xcf\xcd\xcb\xc1,
\xcf\xd4\xc2\xd2\xc1\xd3\xd9\xd7\xc1\xc5\xd4\xd3\xd1.

==== and this is after the second attempt ====

(process:5626): GLib-CRITICAL (recursed) **: file gstring.c: line 672
(g_string_erase): assertion `pos >= 0' failed
aborting...

Program received signal SIGABRT, Aborted.

Thread 1089147584 (LWP 5626)

  • #0 ??
  • #1 abort
    at ../sysdeps/generic/abort.c line 88
  • #2 g_logv
  • #3 g_log
    at gmessages.c line 541
  • #4 g_string_erase
    at gstring.c line 682
  • #5 escape_string
    at gmessages.c line 795
  • #6 g_log_default_handler
  • #7 g_logv
  • #8 g_log
  • #9 vte_terminal_send
    at vte.c line 7566
  • #10 vte_terminal_feed_child
    at vte.c line 7676
  • #11 vte_terminal_paste_cb
    at vte.c line 8403
  • #12 request_text_received_func
    at gtkclipboard.c line 805
  • #13 selection_received
    at gtkclipboard.c line 717
  • #14 _gtk_marshal_VOID__BOXED_UINT
    at gtkmarshalers.c line 1180
  • #15 g_closure_invoke
    at gclosure.c line 437
  • #16 signal_emit_unlocked_R
    at gsignal.c line 2436
  • #17 g_signal_emit_valist
    at gsignal.c line 2195
  • #18 g_signal_emit_by_name
    at gsignal.c line 2263
  • #19 gtk_selection_retrieval_report
    at gtkselection.c line 1804
  • #20 _gtk_selection_property_notify
    at gtkselection.c line 1688
  • #21 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 82
  • #22 g_type_class_meta_marshal
    at gclosure.c line 514
  • #23 g_closure_invoke
    at gclosure.c line 437
  • #24 signal_emit_unlocked_R
    at gsignal.c line 2474
  • #25 g_signal_emit_valist
  • #26 g_signal_emit
  • #27 gtk_widget_event_internal
    at gtkwidget.c line 3563
  • #28 gtk_main_do_event
    at gtkmain.c line 1605
  • #29 gdk_event_dispatch
    at gdkevents-x11.c line 2133
  • #30 g_main_dispatch
    at gmain.c line 1895
  • #31 g_main_context_dispatch
    at gmain.c line 2441
  • #32 g_main_context_iterate
    at gmain.c line 2522
  • #33 g_main_loop_run
    at gmain.c line 2726
  • #34 gtk_main
    at gtkmain.c line 1172
  • #35 main
    at terminal.c line 1669
  • #36 __libc_start_main
    at ../sysdeps/generic/libc-start.c line 209

Comment 1 Mariano Suárez-Alvarez 2004-04-11 20:22:05 UTC
This is due to 139030, and what you are seeing is essentially the same problem
as in bug 139441.

Thanks for reporting the bug.

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