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 435416 - crash in Text Editor:
crash in Text Editor:
Status: RESOLVED DUPLICATE of bug 346444
Product: gedit
Classification: Applications
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2007-05-03 06:21 UTC by sandpear
Modified: 2007-05-30 06:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description sandpear 2007-05-03 06:21:41 UTC
Version: 2.18.1

What were you doing when the application crashed?



Distribution: Unknown
Gnome Release: 2.18.1 2007-04-16 (FreeBSD GNOME Project)
BugBuddy Version: 2.18.1

System: FreeBSD 6.2-STABLE FreeBSD 6.2-STABLE #1: Sun Apr  1 18:26:33 JST 2007     root@kocab.sandpear.ddo.jp:/usr/obj/usr/src/sys/GENERIC i386
X Vendor: The X.Org Foundation
X Vendor Release: 60899903
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 42768 vsize: 42768 resident: 24492 share: 39597478 rss: 24492 rss_rlim: 6123
CPU usage: start_time: 0 rtime: 665 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 133

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

(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[New LWP 100097]
(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Switching to LWP 100097]
0x290f44e9 in wait4 () from /lib/libc.so.6

Thread 1 (LWP 100097)

  • #0 wait4
    from /lib/libc.so.6
  • #1 waitpid
    from /lib/libc.so.6
  • #2 waitpid
    from /lib/libpthread.so.2
  • #3 libgnomeui_module_info_get
    from /usr/local/lib/libgnomeui-2.so.0
  • #4 sigaction
    from /lib/libpthread.so.2
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 sigaction
    from /lib/libpthread.so.2
  • #11 _fini
    from /usr/local/lib/gtk-2.0/2.10.0/loaders/svg_loader.so
  • #12 ??
  • #13 ??
    from /libexec/ld-elf.so.1
  • #14 ??
  • #15 elf_hash
    from /libexec/ld-elf.so.1
  • #16 elf_hash
    from /libexec/ld-elf.so.1
  • #17 __cxa_finalize
    from /lib/libc.so.6
  • #18 exit
    from /lib/libc.so.6
  • #19 _start
  • #20 ??
Output of custom script "/usr/local/lib/gedit-2/gedit-bugreport.sh":
Active plugins:

No plugin installed in $HOME.

Module versions:
  -                       2.12.11
  -                       2.10.11
  -                       1.8.5
  -                       2.18.1
  -                       2.6.0
  -                       2.18.0
  -                       2.18.1
  -                       2.12.3
  -                       2.10.4
  -                       2.18.2
  -                       2.18.0
  -                       1.3.0
  -                       0.58

Python module versions:
  - python                2.4.4
  - pygtk                 2.10.4 (GTK+ 2.10.11)
  - gnome-python          2.18.2





----------- .xsession-errors ---------------------
[DEBUG]: Unable to connect to Tomboy remote control: Unable to open the system message bus.
[DEBUG]: Unable to connect to Tomboy remote control: Unable to open the system message bus.
GTK Accessibility Module initialized
Bonobo accessibility support initialized
(gedit:836): Gnome-CRITICAL **: gnome_program_get_app_version: assertion `program != NULL' failed
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
This libgtop was compiled on FreeBSD 6.2-RELEASE i386
If you see strange problems caused by it,
you should recompile libgtop and dependent applications
warning: Unable to get location for thread creation breakpoint: generic error
--------------------------------------------------
Comment 1 palfrey 2007-05-03 12:46:10 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 Baptiste Mille-Mathias 2007-05-30 06:35:28 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 346444 ***