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 300426 - gnome-terminal crashes when LANG=ko_KR.UTF-8 and LC_CTYPE=ko_KR.EUC-KR
gnome-terminal crashes when LANG=ko_KR.UTF-8 and LC_CTYPE=ko_KR.EUC-KR
Status: RESOLVED DUPLICATE of bug 157945
Product: gnome-terminal
Classification: Core
Component: general
2.10.x
Other other
: High critical
: ---
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-04-13 05:04 UTC by Eungkyu Song
Modified: 2005-04-27 14:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Description Eungkyu Song 2005-04-13 05:04:12 UTC 
Distribution: Debian 3.1
Package: gnome-terminal
Severity: normal
Version: GNOME2.10.0 2.10.0
Gnome-Distributor: Ubuntu
Synopsis: gnome-terminal crashes when LANG=ko_KR.UTF-8 and LC_CTYPE=ko_KR.EUC-KR
Bugzilla-Product: gnome-terminal
Bugzilla-Component: general
Bugzilla-Version: 2.10.0
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:
I'm using LANG=ko_KR.UTF-8 desktop. To use EUC-KR encoding terminal, I
launch gnome-terminal by following script:

export LC_CTYPE=ko_KR.EUC-KR
exec gnome-terminal

In this situation, when korean character is in terminal, gnome-terminal
always crashes by clicking terminal screen. 

Steps to reproduce the crash:
1. In ko_KR.UTF-8 desktop, run export LC_CTYPE=ko_KR.EUC-KR;
gnome-terminal --disable-factory
2. display some korean character in terminal screen
3. click terminal screen (near korean character)

Expected Results:

does not crash

How often does this happen?

always

Additional Information:

i'm using ubuntu linux 5.04


Debugging Information:

Backtrace was generated from
'/home/eungkyu/software/ubuntu/gnome-terminal/gnome-terminal-2.10.0/src/gnome-terminal'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1222672256 (LWP 6807)]
[New Thread -1256887376 (LWP 6810)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 58106

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 re_exec
    from /lib/tls/i686/cmov/libc.so.6
  • #5 re_exec
    from /lib/tls/i686/cmov/libc.so.6
  • #6 re_exec
    from /lib/tls/i686/cmov/libc.so.6
  • #7 re_exec
    from /lib/tls/i686/cmov/libc.so.6
  • #8 re_exec
    from /lib/tls/i686/cmov/libc.so.6
  • #9 re_exec
    from /lib/tls/i686/cmov/libc.so.6
  • #10 regexec
    from /lib/tls/i686/cmov/libc.so.6
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 _vte_regex_exec
    at vteregex.c line 252 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-04-13 01:04 -------


Unknown version 2.10.0 in product gnome-terminal.  Setting version to "2.10.x".
Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gnome-terminal".
   Setting to default milestone for this product, '---'
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Comment 1 Elijah Newren 2005-04-13 17:08:46 UTC 
Looks like the stack trace in bug 157945, if so, then perhaps we have a way to
reproduce the crash finally.  Reporter: could you provide a stack trace with
debugging symbols so we can verify whether these are the same bugs?  Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Comment 2 Eungkyu Song 2005-04-14 16:30:49 UTC 
This is new stack trace with debugging information.

+ Trace 58180

Thread 1 (Thread -1222676352 (LWP 10693))

  • #0 find_collation_sequence_value
    from /lib/tls/i686/cmov/libc.so.6
  • #1 check_node_accept_bytes
    from /lib/tls/i686/cmov/libc.so.6
  • #2 transit_state_mb
    from /lib/tls/i686/cmov/libc.so.6
  • #3 transit_state
    from /lib/tls/i686/cmov/libc.so.6
  • #4 check_matching
    from /lib/tls/i686/cmov/libc.so.6
  • #5 re_search_internal
    from /lib/tls/i686/cmov/libc.so.6
  • #6 regexec
    from /lib/tls/i686/cmov/libc.so.6
  • #7 _vte_regex_exec
    at vteregex.c line 252
  • #8 vte_terminal_match_check_internal
    at vte.c line 1682
  • #9 vte_terminal_match_check
    at vte.c line 1797
  • #10 terminal_widget_check_match
    at terminal-widget-vte.c line 195
  • #11 terminal_screen_button_press_event
    at terminal-screen.c line 1657
  • #12 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 83
  • #13 IA__g_closure_invoke
    at gclosure.c line 437
  • #14 signal_emit_unlocked_R
    at gsignal.c line 2485
  • #15 IA__g_signal_emit_valist
    at gsignal.c line 2254
  • #16 IA__g_signal_emit
    at gsignal.c line 2288
  • #17 gtk_widget_event_internal
    at gtkwidget.c line 3631
  • #18 IA__gtk_propagate_event
    at gtkmain.c line 2145
  • #19 IA__gtk_main_do_event
    at gtkmain.c line 1383
  • #20 gdk_event_dispatch
    at gdkevents-x11.c line 2220
  • #21 g_main_dispatch
    at gmain.c line 1947
  • #22 IA__g_main_context_dispatch
    at gmain.c line 2497
  • #23 g_main_context_iterate
    at gmain.c line 2578
  • #24 IA__g_main_loop_run
    at gmain.c line 2782
  • #25 IA__gtk_main
    at gtkmain.c line 963
  • #26 main
    at terminal.c line 1770 






Comment 3


Kjartan Maraas





          2005-04-27 14:21:58 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 157945 ***