Bug 13507

Summary:	Closing gedit asks to save but doesn't
Product:	Mageia	Reporter:	Dick Gevers <dvgevers>
Component:	RPM Packages	Assignee:	Olav Vitters <olav>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	gedit-3.12.2-3.mga5	CVE:
Status comment:

Description Dick Gevers 2014-06-10 11:35:39 CEST

Description of problem:

Open a file with gedit and make some changes.

Close the application and it asks whether ot not to save the file.

Click save and open the file again: the result is that the previous changes had not been saved - the file is the same as before all of the above.

On the other hand, if the "save" button is pressed, the changes made are saved correctly.



How reproducible:

As above, only since update to 3.12.2-3



Reproducible: 

Steps to Reproduce:

Comment 1 Manuel Hiebel 2014-06-12 00:48:37 CEST

bug reported upstream ?

Assignee: bugsquad => olav

Comment 2 Dick Gevers 2014-06-12 11:15:26 CEST

I could, but I have a gut feeling this might be Cauldron specific ?

Comment 3 Olav Vitters 2014-06-15 03:34:19 CEST

Please report upstream against gtk+. See https://bugzilla.gnome.org/enter_bug.cgi?product=gtk%2B. I've just submitted a -4mga update which fixed another bug, would appreciate if you tested with that version.

Comment 4 Olav Vitters 2014-06-15 03:41:45 CEST

I looked at the patches for Fedora and added the likely cause. Please check -5mga instead, pretty sure that patch will fix this bug.

Comment 5 Dick Gevers 2014-06-16 21:02:24 CEST

I am not seeing either -4.mga5 or -5.mga5 in any repository ?!

Comment 6 Olav Vitters 2014-06-16 23:25:20 CEST

$ urpmq -yf gtk+3.0
gtk+3.0-3.13.2-5.mga5.x86_64
gtk+3.0-debuginfo-3.13.2-5.mga5.x86_64
lib64gtk+3.0-devel-3.13.2-5.mga5.x86_64
libgtk+3.0-devel-3.13.2-5.mga5.i586

Suggest to use http://ftp.acc.umu.se/mirror/mageia/

Comment 7 Dick Gevers 2014-06-17 12:31:06 CEST

Aha. Thought you were patching gedit package. 

Yes. Bug appears to be fixed now. Thanks.

Status: NEW => RESOLVED
Resolution: (none) => FIXED