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 46450 - Erase Emblem is confused as a regular emblem
Erase Emblem is confused as a regular emblem
Status: RESOLVED DUPLICATE of bug 45114
Product: nautilus
Classification: Core
Component: [obsolete] Backgrounds Emblems and Themes
0.x.x [obsolete]
Other Linux
: Normal enhancement
: 1.0.x
Assigned To: Andy Hertzfeld
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2001-02-08 18:07 UTC by Alec Peden
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Alec Peden 2001-09-10 00:59:12 UTC
I personally find the Erase Emblem in the Edit > Backgrounds and Emblems to be
confusing as to what it is. The way it is displayed now, it looks just like any
normal emblem that i can assign to files. There is nothing to distint it from
regular emblems. I had to ask in #nautilus what it was for because there is no
way for a user to know it is there to remove existing file emblems. I also can
not find anything in the Help about this either.



------- Additional Comments From sullivan@eazel.com 2001-02-08 13:49:55 ----

See also related bug 46282. Addressing bug 46282 might improve this well enough to
call it FIXED. Also, the on-line help will mention the erase emblem, though it
doesn't yet (this specific issue came up in an on-line help review yesterday).



------- Additional Comments From ramiro@fateware.com 2001-02-10 15:02:35 ----

I fixed 6282.



------- Additional Comments From eli@eazel.com 2001-03-26 11:11:12 ----

QA Assigning to self.



------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-09-09 20:59 -------
Comment 1 Chris Lyttle 2001-10-10 07:23:09 UTC
This is in the help. Fixed?
Comment 2 Dave Bordoley [Not Reading Bug Mail] 2002-05-25 17:43:02 UTC

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