Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1265541 - Gedit "save changes" dialog is empty
Summary: Gedit "save changes" dialog is empty
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gedit
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: F23FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2015-09-23 08:18 UTC by Lukas Brabec
Modified: 2015-09-26 01:02 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-26 01:02:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screenshot of gedit (655.80 KB, image/png)
2015-09-23 08:18 UTC, Lukas Brabec
no flags Details

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. :)


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