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 609431 - "(as superuser)" appended to titles of windows owned by root is not essential
"(as superuser)" appended to titles of windows owned by root is not essential
Status: RESOLVED OBSOLETE
Product: metacity
Classification: Other
Component: general
2.28.x
Other Linux
: Normal minor
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks:
 
 
Reported: 2010-02-09 14:53 UTC by Vish
Modified: 2020-11-06 20:06 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Vish 2010-02-09 14:53:46 UTC
Bug first reported in launchpad >
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/519035

In Lucid, the string " (as superuser)" is appended to titles of windows owned by root. I understand that this may be a useful feature for technical users, but it is tech-speak and not useful for the average user.

The only argument I can think of for adding this string is the following:

  1. Users sometimes accidentally harm their system/data when they interact with windows running as root.
  2. Adding "(as superuser)" to window titles will make users aware when windows are running as root.
  3. Users understand the consequences of running a window as root and will modify their behavior to take extra care.
  ---
  4. Users will not accidentally harm their system/data.

I think premise 2 is false because users often do not read title bars and "superuser" is tech-speak (as is "root" or "administrator" or any similar string). I also think premise 3 is false because the class of users that will make catastrophic errors by interacting with windows as root is not a class of users that understands the consequences...

This string should be removed because it is tech-speak and ineffectual.
Comment 1 Thomas Thurman 2010-02-09 15:10:00 UTC
See also this Metacity blog post:
http://blogs.gnome.org/metacity/2010/02/08/as-superuser-considered-harmful/
Comment 2 Baybal Ni 2010-02-24 06:15:27 UTC
I don't think that this solution can be helpful. I think metacity just should implement root notification in less intrusive way like painting window red. And to suppress it just add a command line argument.
Comment 3 Didier Roche 2010-03-24 14:31:23 UTC
For your information, after a discussion with cjwatson and seb128, we decided (at least temporally) to disable the feature for now in lucid.
As Thomas pointed in the Metacity blog post, the situation is not quite good for traditional user (non technical one) and also the difference between metacity having this and compiz not having it make the situation unclear (even if it should be trivial to implement the same in compiz).
(I basically distro-patch revert of http://git.gnome.org/browse/metacity/commit/?id=ab6aa5463ffdd5cfaf729eb1f5407be749ba1090 without the typo fixes ;))

Even if https://bugzilla.gnome.org/show_bug.cgi?id=605137 is good for making some kind of black list/white list, it doesn't covered the underlying problem.

I'll be happy to work on that and speak about it in guadec (maybe another way, to warn the user and make it more obvious?).
Comment 4 André Klapper 2020-11-06 20:06:28 UTC
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years.

If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/metacity/-/issues/

Thank you for reporting this issue and we are sorry it could not be fixed.