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 347549 - gEdit crashes on exit, every time.
gEdit crashes on exit, every time.
Status: RESOLVED DUPLICATE of bug 346444
Product: gedit
Classification: Applications
Component: general
unspecified
Other other
: High critical
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2006-07-14 20:01 UTC by a9909
Modified: 2006-07-14 22:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description a9909 2006-07-14 20:01:47 UTC
Distribution: Unknown
Package: gedit
Severity: Normal
Version: GNOME2.14.2 (null)
Gnome-Distributor: FreeBSD GNOME Project
Synopsis: gEdit crashes on exit, every time.
Bugzilla-Product: gedit
Bugzilla-Component: general
Bugzilla-Version: (null)
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:
Every time I exit gEdit, it crashes, and the pre-BugBuddy dialog comes
up.

Steps to reproduce the crash:
1. Start gedit
2. Click Exit button, or go File - Quit.
3. Window disappears, crash dialog comes up.

Expected Results:
1. Window disappears, crash dialog doesn't come up.

How often does this happen?
100% of the time.

Additional Information:
version 2.14.3 ... I could use --disable-crash-dialog, I suppose, but it
would obviously be better if the program just didn't crash. :) I suppose it could be a library issue rather than a code issue, let me know if that's the case. Thanks.


Debugging Information:

Backtrace was generated from '/usr/X11R6/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)...[New LWP 100134]
(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)...[Switching to LWP 100134]
0x2905dbd9 in wait4 () from /lib/libc.so.6

Thread 1 (LWP 100134)

  • #0 wait4
    from /lib/libc.so.6
  • #1 waitpid
    from /lib/libc.so.6
  • #2 waitpid
    from /usr/lib/libpthread.so.2
  • #3 libgnomeui_module_info_get
    from /usr/X11R6/lib/libgnomeui-2.so.0
  • #4 sigaction
    from /usr/lib/libpthread.so.2
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 sigaction
    from /usr/lib/libpthread.so.2
  • #11 abort
    from /lib/libc.so.6
  • #12 __deregister_frame_info_bases
    from /usr/lib/libstdc++.so.5
  • #13 __deregister_frame_info
    from /usr/lib/libstdc++.so.5
  • #14 __do_global_dtors_aux
    from /usr/X11R6/lib/gnome-vfs-2.0/modules/libfile.so
  • #15 _fini
    from /usr/X11R6/lib/gnome-vfs-2.0/modules/libfile.so
  • #16 tls_dtv_generation
    from /libexec/ld-elf.so.1
  • #17 ??
    from /libexec/ld-elf.so.1
  • #18 ??
  • #19 elf_hash
    from /libexec/ld-elf.so.1
  • #20 elf_hash
    from /libexec/ld-elf.so.1
  • #21 __cxa_finalize
    from /lib/libc.so.6
  • #22 exit
    from /lib/libc.so.6
  • #23 _start
  • #24 ??




------- Bug created by bug-buddy at 2006-07-14 20:01 -------


Unknown version (null) in product gedit.  Setting version to "unspecified".

Comment 1 Sergej Kotliar 2006-07-14 22:44:18 UTC
Thanks for the bug report. 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?


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