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 423152 - crash in Text Editor: I ran the "gedit" comman...
crash in Text Editor: I ran the "gedit" comman...
Status: RESOLVED DUPLICATE of bug 363437
Product: gedit
Classification: Applications
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2007-03-26 23:32 UTC by snk
Modified: 2007-03-27 02:31 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description snk 2007-03-26 23:32:43 UTC 
Version: 2.16.1

What were you doing when the application crashed?
I ran the "gedit" command in a terminal and pressed ENTER.

Next thing that happens is that I see this "Bug Buddy" Bug Reporting Tool appears, asking me what I was doing when the application crashed.

Well, the application never had a chance to start in the first place; it crashed instantaneously.


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

Memory status: size: 30830592 vsize: 0 resident: 30830592 share: 0 rss: 8671232 rss_rlim: 0
CPU usage: start_time: 1174951869 rtime: 0 utime: 15 stime: 0 cutime:13 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0

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

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

+ Trace 122474

Thread 1 (Thread -1227295056 (LWP 25316))

  • #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 _gedit_window_move_tab_to_new_window
  • #13 _gedit_window_move_tab_to_new_window
  • #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 bacon_message_connection_new
  • #20 gedit_app_create_window
  • #21 main
  • #0 __kernel_vsyscall 






Comment 1


Pedro Villavicencio





          2007-03-27 02:31:32 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 363437 ***