Bug 1266792 - Graphical applications as root don't work
Summary: Graphical applications as root don't work
Status: CLOSED DUPLICATE of bug 1274451
Alias: None
Product: Fedora
Classification: Fedora
Component: wayland
Version: 23
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: WaylandRelated 1266771
TreeView+ depends on / blocked
Reported: 2015-09-27 23:45 UTC by František Zatloukal
Modified: 2015-11-26 18:14 UTC (History)
5 users (show)

Clone Of:
Last Closed: 2015-11-26 18:14:29 UTC

Attachments (Terms of Use)

Description František Zatloukal 2015-09-27 23:45:00 UTC
Description of problem:
Graphical applications (both native Wayland and XWayland) don't work if launched as root.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Run any graphical app as root (sudo appname) when running on Wayland

Actual results:
Fails with "No protocol specified" and some other app-specific messages.

Expected results:
Graphical apps should work even when launched as root.

Additional info:
I hope I've selected the right package to report against (I am little unsure), if no, let me know and I'll report it to right place.

Comment 1 Christian Stadelmann 2015-09-29 21:08:39 UTC
I don't know whether this is intended, but I think it is a feature. The rule is: "Never start GUI applications as root with sudo". For reasons why see https://help.ubuntu.com/community/RootSudo#Graphical_sudo , https://askubuntu.com/questions/270006/why-user-should-never-use-normal-sudo-to-start-graphical-application

Have you tried policykit? See `man pkexec`.

Comment 2 František Zatloukal 2015-10-04 20:54:12 UTC
Thanks for your reply.

pkexec doesn't work (server init failed in gedit, other non-gnome apps have their specific errors).

Comment 3 Kamil Páral 2015-11-26 18:14:29 UTC
I believe this is the same as bug 1274451.

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

Note You need to log in before you can comment on or make changes to this bug.