Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 622275 - gedit crashes when launching second one
gedit crashes when launching second one
Status: CLOSED DUPLICATE of bug 621267
Product: Fedora
Classification: Fedora
Component: gedit (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-08-08 10:50 EDT by Mamoru TASAKA
Modified: 2010-08-09 12:38 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-08-09 12:16:41 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
gdb log when second gedit crashes (8.12 KB, text/plain)
2010-08-08 10:50 EDT, Mamoru TASAKA
no flags Details
gdb log, glib2 upgraded to 2.25.13 (8.00 KB, text/plain)
2010-08-08 10:58 EDT, Mamoru TASAKA
no flags Details

  None (edit)
Description Mamoru TASAKA 2010-08-08 10:50:37 EDT
Created attachment 437449 [details]
gdb log when second gedit crashes

Description of problem:
- Open gnome-terminal
- type $ gedit &
  Then one gedit launches
- Now type $ gedit

Then second one crashes with segv

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. See above
Actual results:
gdb log attached

Expected results:
Second gedit should not crash

Additional info:
Downgrading glib2 to 2.25.11 solves this issue
Comment 1 Mamoru TASAKA 2010-08-08 10:58:35 EDT
Created attachment 437451 [details]
gdb log, glib2 upgraded to 2.25.13

glib2 is upgraded to 2.25.13, still seeing the same issue
Comment 2 Adam Williamson 2010-08-09 12:16:41 EDT
I have this too and have filed it via abrt.

Fedora Bugzappers volunteer triage team

*** This bug has been marked as a duplicate of bug 621267 ***
Comment 3 Matthias Clasen 2010-08-09 12:38:41 EDT
I assume this is fixed by dconf 0.5.

Note You need to log in before you can comment on or make changes to this bug.