After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 782845 - accidently placed a file in the bookmarks area; is now ''stuck'' there forever (can't be removed anymore)
accidently placed a file in the bookmarks area; is now ''stuck'' there foreve...
Status: RESOLVED DUPLICATE of bug 762252
Product: gtk+
Classification: Platform
Component: Widget: GtkFileChooser
2.24.x
Other Windows
: Normal normal
: ---
Assigned To: gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2017-05-19 22:04 UTC by Bernard
Modified: 2017-08-18 19:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Bernard 2017-05-19 22:04:41 UTC 
Hi there,

A student of mine (on Udemy.com) accidently placed (dragged) a file in the bookmarks area; and it can't be removed anymore. I have recreated this error myself (in Gimp 2.8.22), and indeed the blue minus sign has no effect on the file (nor right-clicking on the file).
I would also remove it manually, but in the .gimp-2.8 folder I can't find a file about it. Is there a 'bookmarkrc' file, or 'saverc' file where I can remove bookmarks manually?

Thanx in advance for your answer and help!

Sincerely,
Bernard 't Hooft
(Gimp instructor on Udemy)
Comment 1 Michael Natterer 2017-05-20 09:08:47 UTC 
Indeed, confirming. On GTK+ 3.x the file can at least be removed again
using the right-click menu, but on GTK+ 2.24 it's stuck forever.

As a workaround, find the file .gtk-bookmarks somewhere in your
user profile folder, and remove the entry manually, it's a simple
text file.
Comment 2 Bernard 2017-05-20 12:27:43 UTC 
Hi Michael,

Thank you for your quick reply, and the easy solution!

Bernard.
Comment 3 Daniel Boles 2017-08-14 23:03:10 UTC 

*** This bug has been marked as a duplicate of bug 721321 ***
Comment 4 Daniel Boles 2017-08-18 19:22:41 UTC 

*** This bug has been marked as a duplicate of bug 762252 ***