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 496372 - crash in Text Editor: Japanaese (UTF-8) homewo...
crash in Text Editor: Japanaese (UTF-8) homewo...
Status: RESOLVED DUPLICATE of bug 488564
Product: gedit
Classification: Applications
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-13 08:38 UTC by drmark
Modified: 2007-11-16 13:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description drmark 2007-11-13 08:38:52 UTC 
Version: 2.20.0

What were you doing when the application crashed?
Japanaese (UTF-8) homework.Prior to the crash, it was doing the thing where every few seconds it stops responding. The actual trigger came shortly after a 'print'.


Distribution:                   Solaris Express Community Edition snv_75a X86
Gnome Release: 2.20.0 2007-09-24 (Sun Microsystems, Inc.)
BugBuddy Version: 2.20.0

X Vendor: Sun Microsystems, Inc.
X Vendor Release: 10300000
Selinux: No
Accessibility: Enabled
GTK+ Theme: nimbus
Icon Theme: nimbus

Memory status: size: 193241088 vsize: 193241088 resident: 53440512 share: 2039808 rss: 53440512 rss_rlim: 0
CPU usage: start_time: 0 rtime: 1592 utime: 12986072 stime: 2935510 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gedit'

(no debugging symbols found)
sol-thread active.
Retry #1:
Retry #2:
Retry #3:
Retry #4:
[New LWP    1        ]
[New Thread 1 (LWP 1)]

+ Trace 177367

Thread 1 (LWP 1)

  • #0 _waitid
    from /lib/libc.so.1
  • #1 _waitpid
    from /lib/libc.so.1
  • #2 waitpid_cancel
    from /lib/libc.so.1
  • #3 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #5 __1cNrun_bug_buddy6Fpkclp0_b_
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 __1cMcheck_if_gdb6Fpv_b_
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #7 _ex_text0
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #8 __sighndlr
    from /lib/libc.so.1
  • #9 call_user_handler
    from /lib/libc.so.1
  • #10 <signal handler called>
  • #11 countbytes
    from /lib/libc.so.1
  • #12 _ndoprnt
    from /lib/libc.so.1
  • #13 vsnprintf
    from /lib/libc.so.1
  • #14 g_printf_string_upper_bound
    from /usr/lib/libglib-2.0.so.0
  • #15 g_vasprintf
    from /usr/lib/libglib-2.0.so.0
  • #16 g_strdup_vprintf
    from /usr/lib/libglib-2.0.so.0
  • #17 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #18 g_log
    from /usr/lib/libglib-2.0.so.0
  • #19 g_type_check_instance_cast
    from /usr/lib/libgobject-2.0.so.0
  • #20 update_preview
    from /usr/lib/libgnomeprintui-2-2.so.0
  • #21 g_idle_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #22 g_main_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #23 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #24 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #25 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #26 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 main 

Thread 1 (LWP    1        ):
#-1 0xfef02897 in _waitid () from /lib/libc.so.1
No symbol table info available.
#-1 0xfef02897 in _waitid () from /lib/libc.so.1
Output of custom script "/usr/lib/gedit-2/gedit-bugreport.sh":




----------- .xsession-errors (23672354 sec old) ---------------------
the window manager.
The application 'gnome-terminal' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
The application 'evolution-2.8' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
should_show_acls (window) 0
should_show_acls (window) 0
should_show_acls (window) 0
should_show_acls (window) 1
all_can_get_acl: 1 : YES
The application 'services-admin' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
--------------------------------------------------
Comment 1 palfrey 2007-11-16 13:22:33 UTC 
Thanks for taking the time to report this bug.
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 in order to help the developers?


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