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 482276 - crash in Text Editor: Pasting
crash in Text Editor: Pasting
Status: RESOLVED DUPLICATE of bug 344826
Product: gedit
Classification: Applications
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2007-10-01 15:38 UTC by max
Modified: 2007-10-06 13:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description max 2007-10-01 15:38:57 UTC 
Version: 2.16.0

What were you doing when the application crashed?
Pasting


Distribution: Red Hat Enterprise Linux Server release 5 (Tikanga)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 393527296 vsize: 393527296 resident: 26808320 share: 14893056 rss: 26808320 rss_rlim: -1
CPU usage: start_time: 1191253040 rtime: 96 utime: 86 stime: 10 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496363280 (LWP 22056)]
(no debugging symbols found)
0x0000003c8b60d895 in waitpid () from /lib64/libpthread.so.0

+ Trace 166879

Thread 1 (Thread 46912496363280 (LWP 22056))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib64/libc.so.6
  • #4 abort
    from /lib64/libc.so.6
  • #5 g_logv
    from /lib64/libglib-2.0.so.0
  • #6 g_log
    from /lib64/libglib-2.0.so.0
  • #7 g_assert_warning
    from /lib64/libglib-2.0.so.0
  • #8 gtk_text_view_new_with_buffer
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #9 gtk_text_view_new_with_buffer
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #10 gtk_source_view_get_show_line_numbers
    from /usr/lib64/libgtksourceview-1.0.so.0
  • #11 gtk_marshal_BOOLEAN__VOID
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #12 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #13 g_signal_override_class_closure
    from /lib64/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #16 gtk_widget_get_default_style
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #17 gtk_propagate_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #18 gtk_main_do_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #19 gdk_add_client_message_filter
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #20 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #21 g_main_context_check
    from /lib64/libglib-2.0.so.0
  • #22 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #23 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #24 main
  • #0 waitpid
    from /lib64/libpthread.so.0 






Comment 1


Susana





          2007-10-06 13:56:52 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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