Bug 1255556

Summary: state of bookmarks is not unset when the bookmark is removed
Product: Red Hat Enterprise Linux 7 Reporter: Matěj Cepl <mcepl>
Component: geditAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.2CC: mclasen, tpelka
Target Milestone: rcKeywords: Patch
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gedit-3.14.3-15.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-04 06:18:59 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:
Attachments:
Description Flags
suggested patch none

Description Matěj Cepl 2015-08-20 23:47:28 UTC
1. Open a file in gedit with a bookmark (set via bookmarks plugin from the gedit-plugins).

2. Ctrl-B and Ctrl-Alt-B (jump to the bookmark and flip it off)

3. Change file and save

4. Reopen the file

Expected: no bookmark is present

Observed: the old bookmark is still at the place

When looking at the metadata with

    gvfs-info filename|grep metadata::gedit-bookmarks:

I can still see that the bookmark is saved in metadata::gedit

Comment 3 Matěj Cepl 2016-01-22 16:23:51 UTC
This has been resolved (according to the upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=753900 and my experience) in 3.14.4 which is a maintenance release.

Comment 4 Matěj Cepl 2016-01-24 17:38:18 UTC
Created attachment 1117638 [details]
suggested patch

Comment 5 Matthias Clasen 2016-01-28 14:09:47 UTC
thanks for the patch

Comment 9 errata-xmlrpc 2016-11-04 06:18:59 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2424.html