Bug 1265541

Summary: Gedit "save changes" dialog is empty
Product: [Fedora] Fedora Reporter: Lukas Brabec <lbrabec>
Component: geditAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: juloml, lbrabec, mcatanzaro+wrong-account-do-not-cc, robatino, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-09-26 01:02:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1170821    
Attachments:
Description Flags
screenshot of gedit none

Description Lukas Brabec 2015-09-23 08:18:17 UTC
Created attachment 1076118 [details]
screenshot of gedit

On Fedora 23, when user types text in gedit and tries to close it, the dialog that prompts user whether the changes should be saved is empty. 

Version-Release number of selected component (if applicable):
gedit-3.17.92-1.fc23.x86_64


Steps to Reproduce:
1. open gedit
2. type something
3. try to close it

Actual results:
"save changes" dialog is empty, gedit cannot be closed


Expected results:
dialog should contain buttons for "save", "don't save" and "cancel"

Comment 1 Fedora Blocker Bugs Application 2015-09-23 08:27:21 UTC
Proposed as a Blocker for 23-final by Fedora user lbrabec using the blocker tracking app because:

 Proposing as final blocker due to violation of final criterion:
Default application functionality
All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test.

Comment 3 Michael Catanzaro 2015-09-26 01:02:01 UTC
Indeed, should be fixed in stable already. :)