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 140255 - gEdit crash on exit
gEdit crash on exit
Status: RESOLVED DUPLICATE of bug 135298
Product: gedit
Classification: Applications
Component: general
0.5.1
Other other
: Normal normal
: ---
Assigned To: Gedit maintainers
Paolo Maggi
Depends on:
Blocks:
 
 
Reported: 2004-04-17 03:03 UTC by acidmax
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4



Description acidmax 2004-04-16 13:03:42 UTC
Distribution: Unknown
Package: gedit
Severity: normal
Version: GNOME2.4.1 2.4.1
Gnome-Distributor: FreeBSD GNOME Project
Synopsis: gEdit crash on exit
Bugzilla-Product: gedit
Bugzilla-Component: general
Bugzilla-Version: 2.4.1
BugBuddy-GnomeVersion: 2.0 (2.4.0.1)
Description:
Description of the crash:
gEdit crashes on exit.

Steps to reproduce the crash:
1. 
2. 
3. 

Expected Results:


How often does this happen?
At each exit.

Additional Information:



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)...
[Switching to Process 72816, Thread 1]
0x290e022f in poll () from /lib/libc.so.5

Thread 1 (Process 72816, Thread 1)

  • #0 poll
    from /lib/libc.so.5
  • #1 _thread_kern_sched_state_unlock
    from /usr/lib/libc_r.so.5
  • #2 _thread_kern_scheduler
    from /usr/lib/libc_r.so.5




------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-04-16 23:03 -------


Unknown version 2.4.1 in product gedit. Setting version to "0.5.1".
Unknown platform unknown. Setting to default platform "Other".
Unknown milestone "unknown" in product "gedit".
   Setting to default milestone for this product, '---'
The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was acidmax@mail.bg.
Setting to default status "UNCONFIRMED".
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.

Comment 1 Paolo Maggi 2004-04-28 13:56:59 UTC

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