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 381369 - crash in Text Editor: I was only editing a php...
crash in Text Editor: I was only editing a php...
Status: RESOLVED DUPLICATE of bug 363172
Product: gedit
Classification: Applications
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Gedit maintainers
Gedit maintainers
: 397344 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-12-01 18:45 UTC by peppo_crucco
Modified: 2007-03-24 11:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description peppo_crucco 2006-12-01 18:45:43 UTC 
Version: 2.16.1

What were you doing when the application crashed?
I was only editing a php-html site

It's the first time!


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

Memory status: size: 244285440 vsize: 244285440 resident: 39804928 share: 17711104 rss: 39804928 rss_rlim: -1
CPU usage: start_time: 1164979928 rtime: 7915 utime: 7525 stime: 390 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47213112518096 (LWP 7595)]
(no debugging symbols found)
0x00002af0a32f9eef in waitpid () from /lib/libpthread.so.0

+ Trace 90894

Thread 1 (Thread 47213112518096 (LWP 7595))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 gnome_gtk_module_info_get
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 raise
    from /lib/libc.so.6
  • #4 abort
    from /lib/libc.so.6
  • #5 g_logv
    from /usr/lib64/libglib-2.0.so.0
  • #6 g_log
    from /usr/lib64/libglib-2.0.so.0
  • #7 g_assert_warning
    from /usr/lib64/libglib-2.0.so.0
  • #8 _gtk_text_btree_tag
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #9 g_closure_invoke
    from /usr/lib64/libgobject-2.0.so.0
  • #10 g_signal_chain_from_overridden
    from /usr/lib64/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /usr/lib64/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /usr/lib64/libgobject-2.0.so.0
  • #13 _gtk_text_buffer_notify_will_remove_tag
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #14 ??
    from /usr/lib64/libgtksourceview-1.0.so.0
  • #15 gtk_source_buffer_can_undo
    from /usr/lib64/libgtksourceview-1.0.so.0
  • #16 _gtk_source_buffer_highlight_region
    from /usr/lib64/libgtksourceview-1.0.so.0
  • #17 g_main_context_dispatch
    from /usr/lib64/libglib-2.0.so.0
  • #18 g_main_context_check
    from /usr/lib64/libglib-2.0.so.0
  • #19 g_main_loop_run
    from /usr/lib64/libglib-2.0.so.0
  • #20 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #21 main
  • #0 waitpid
    from /lib/libpthread.so.0 






Comment 1


Pedro de Medeiros





          2007-01-04 11:55:40 UTC
        



Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. 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!







Comment 2


palfrey





          2007-01-16 22:46:50 UTC
        



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






Comment 3


Paolo Maggi





          2007-03-24 11:02:27 UTC
        




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