![]() They are of the opinion that the GUI is effectively "easy mode", and root access is effectively not "easy mode." If you want root, go to the terminal and use it there. This echoes the sentiment of the Ubuntu developers and is not a bug. In this mode, the menu will be embedded into gedit's window directly, because we still can't get a link to DBus/Ayatana. You can get around the lack of a menu by using sudo's -E flag, but that will still cause DBus/DConf/whatever to be annoyed at you. In short, the system is trying to create menu objects for/owned by the root user, which causes things to decidedly break. Your menubar being gone is more or less a side effect of how Ayatana's menu system works. However, this still won't work for a number of reasons. If you really need gedit to have its own configuration in the /root folder, launch it like so: sudo -i gedit In short, everything gedit and most other applications do not do. Similarly, they're also specially designed to use root effectively and in a way that won't break things. For example, any part of the Ubuntu control panel that requests root is generally safe, but only because it only keeps the privileges for as long as it needs to, at which point it will immediately dump them back to normal mode. ![]() Now, there are some exceptions to the above rule. DO NOT USE GRAPHICAL APPLICATIONS AS ROOT! ![]() Note the bug report was filed over a year ago and over that time it only effects 18 people. No indication is given for when the fix will be upstream nor if the functionality will be implemented or the error messages will simply disappear. On this bug report there is a commitment to fix these distracting messages as of June 5, 2017. ** (gedit:13003): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-position not supported ** (gedit:13003): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-encoding not supported ** (gedit:13003): WARNING **: Set document metadata failed: Setting attribute metadata::gedit-spell-enabled not supported JUpdate Here are a list of errors you get when using pkexec gedit: (gedit:13003): Gtk-WARNING **: Calling Inhibit failed: GDBus.Error.ServiceUnknown: The name was not provided by any. I'm in the minority using the first method but I believe it will become the standard in Ubuntu 17.04. NOTE: by sudo powers you can google pkexec gedit 3.5k hits, gksu gedit 40k hits or sudo gedit 500k hits. Will there be other benefits with Nautilus and other Gnome derivative Ubuntu applications? Will this also make the annoying error messages go away whenever I use sudo, gksu or pkexec as a regular user with elevated privileges to gedit ? If I create user ID root and sign in once and call gedit will it create the necessary user configuration files that might fix this? When using sudo powers and calling gedit the top level menu with File Edit View Search Tools Documents Help is missing.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |