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 474731 - crash in Text Editor: nothing
crash in Text Editor: nothing
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-09-08 01:17 UTC by skysoundcn
Modified: 2007-12-25 11:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description skysoundcn 2007-09-08 01:17:10 UTC
Version: 2.18.2

What were you doing when the application crashed?
nothing


Distribution: Unknown
Gnome Release: 2.18.3 2007-08-29 (FreeBSD GNOME Project)
BugBuddy Version: 2.18.1

System: FreeBSD 6.2-RELEASE FreeBSD 6.2-RELEASE #0: Fri Jan 12 10:40:27 UTC 2007     root@dessler.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 32768 vsize: 32768 resident: 21508 share: 29823708 rss: 21508 rss_rlim: 5377
CPU usage: start_time: 0 rtime: 266 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)...(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)...[Switching to LWP 100097]
0x2914e6cd 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 tls_dtv_generation
    from /libexec/ld-elf.so.1
  • #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.13
  -                       2.10.14
  -                       1.8.5
  -                       2.18.1
  -                       2.6.2
  -                       2.18.0
  -                       2.18.1
  -                       2.12.3
  -                       2.10.6
  -                       2.18.2
  -                       2.18.0
  -                       1.3.0
  -                       1.3

Python module versions:
  - python                2.5.1
  - pygtk                 2.10.6 (GTK+ 2.10.14)
  - gnome-python          2.18.2





----------- .xsession-errors (6 sec old) ---------------------
Shutting down gnome-mount extension
(nautilus:873): Liboobs-WARNING **: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
seahorse nautilus module initialized
Launching a SCIM daemon with Socket FrontEnd...
Loading simple Config module ...
Creating backend ...
Loading socket FrontEnd module ...
Starting SCIM as daemon ...
GTK Panel of SCIM 1.4.7
(gedit:1052): Gnome-CRITICAL **: gnome_program_get_app_version: assertion `program != NULL' failed
warning: Unable to get location for thread creation breakpoint: generic error
--------------------------------------------------
Comment 1 Luis Medinas 2007-09-08 02:20:07 UTC
Thanks for taking the time to report this bug.
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a description of how to reproduce this bug.

You'll also need to add a stack trace; please see http://live.gnome.org/GettingTraces for more information about how to do so. Thanks in advance!
Comment 2 palfrey 2007-10-30 11:35:21 UTC
Possible duplicate of Bug 346444?
Comment 3 Teppo Turtiainen 2007-12-25 11:40:30 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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