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 375011 - crash in Text Editor: I was opening a text mai...
crash in Text Editor: I was opening a text mai...
Status: RESOLVED DUPLICATE of bug 351704
Product: gedit
Classification: Applications
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Gedit maintainers
Gedit maintainers
: 377184 387643 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-11-14 07:21 UTC by s_pliz
Modified: 2007-01-10 11:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description s_pliz 2006-11-14 07:21:16 UTC 
Version: 2.16.1

What were you doing when the application crashed?
I was opening a text mail attachement found by beagle from the beagle window. 


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 62242816 vsize: 0 resident: 62242816 share: 0 rss: 8876032 rss_rlim: 0
CPU usage: start_time: 1163488711 rtime: 0 utime: 23 stime: 0 cutime:18 cstime: 0 timeout: 5 it_real_value: 0 frequency: 0

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1227650880 (LWP 9973)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 86291

Thread 1 (Thread -1227650880 (LWP 9973))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 gtk_recent_info_get_short_name
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 gtk_recent_info_get_display_name
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 update_recent_files_menu
    at gedit-window.c line 1133
  • #13 gedit_window_init
    at gedit-window.c line 1335
  • #14 g_type_create_instance
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_object_set
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_object_new_valist
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_object_new
    from /usr/lib/libgobject-2.0.so.0
  • #19 gedit_app_create_window_real
    at gedit-app.c line 255
  • #20 gedit_app_create_window
    at gedit-app.c line 337
  • #21 main
    at gedit.c line 536
  • #0 __kernel_vsyscall 






Comment 1


Susana





          2006-11-20 00:52:02 UTC
        



*** Bug 377184 has been marked as a duplicate of this bug. ***






Comment 2


Christian Kirbach





          2006-12-19 20:40:43 UTC
        



*** Bug 387643 has been marked as a duplicate of this bug. ***






Comment 3


Christian Kirbach





          2006-12-19 20:42:10 UTC
        



Thanks for taking the time to report this bug.

the initial trace looks good, but misses some information.


Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

please install the gtk+ and glib debug packages and repost the trace (do not submit it again, if possible)






Comment 4


Paolo Maggi





          2007-01-10 11:23:37 UTC
        




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