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 122744 - gedit segfaults when exiting
gedit segfaults when exiting
Status: RESOLVED DUPLICATE of bug 110280
Product: gedit
Classification: Applications
Component: general
unspecified
Other other
: High critical
: ---
Assigned To: Gedit maintainers
gedit QA volunteers
Depends on:
Blocks:
 
 
Reported: 2003-09-19 15:32 UTC by volswagn
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.1/2.2



Description volswagn 2003-09-19 15:32:54 UTC
Package: gedit
Severity: normal
Version: GNOME2.2.2 2.2.1
os_details: FreeBSD GNOME Project
Synopsis: gedit segfaults when exiting
Bugzilla-Product: gedit
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)
Description:
Description of Problem:
After using File->Quit, gedit segfault notification appears	

Steps to reproduce the problem:
1. Open gedit
2. Use quit from gedit menu
3. 

Actual Results: segfault


Expected Results: clean close


How often does this happen? every time


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 839, Thread 1]
0x2904e883 in poll () from /usr/lib/libc.so.5

Thread 1 (Process 839, Thread 1)

  • #0 poll
    from /usr/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 2003-09-19 11:32 -------

The original reporter (volswagn@msn.com) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, maggi@athena.polito.it.

Comment 1 Paolo Maggi 2003-09-29 16:26:10 UTC
*** This bug has been marked as a duplicate of 110280 ***