Back to bug 1673073

Who When What Removed Added
Joe Wright 2019-02-06 15:43:28 UTC CC alanm, amike, mkolbas
Tomas Pelka 2019-02-06 15:52:59 UTC CC jkoten, tpelka
Blocks 1635157
Joe Wright 2019-02-06 16:11:28 UTC CC botsch
Vladimir Benes 2019-02-08 09:47:12 UTC CC jwright, vbenes
Flags needinfo?(jwright)
Chris Van Hoof 2019-02-20 14:22:37 UTC CC vanhoof
Tomas Pelka 2019-02-21 10:04:50 UTC Blocks 1678350
Tomas Pelka 2019-02-21 10:13:24 UTC Blocks 1635157
Joe Wright 2019-02-26 20:15:10 UTC Flags needinfo?(jwright)
Joe Wright 2019-02-26 20:17:49 UTC Link ID Red Hat Knowledge Base (Solution) 3943481
Peter Hutterer 2019-03-12 02:28:21 UTC Status NEW CLOSED
CC peter.hutterer
Resolution --- WONTFIX
Pool ID 110 0
Last Closed 2019-03-12 02:28:21 UTC
Olivier Fourdan 2019-03-21 09:09:47 UTC CC ofourdan
Tomas Pelka 2019-05-06 06:30:22 UTC Doc Type If docs needed, set a value Known Issue
Jeff Fearn 🐞 2019-05-22 04:57:44 UTC Pool ID sst_graphics_infrastructure_rhel_8
Lucie Vařáková 2019-06-13 11:49:23 UTC CC lmanasko
Docs Contact lmanasko
Lucie Vařáková 2019-07-02 09:57:12 UTC CC ajax
Flags needinfo?(ajax)
Adam Jackson 2019-07-23 15:44:32 UTC Doc Text Cause: 'sudo' does not preserve the user's environment in the spawned subprocess, including information about how to connect to the graphical display.

Consequence: Graphical applications may fail to launch with an error saying "No protocol specified" or "connection refused".

Workaround (if any): Export the user's environment to the subprocess by running "sudo -E" instead of plain "sudo".

Result: Graphical applications can run as a privileged user.
Flags needinfo?(ajax)
Lucie Vařáková 2019-09-30 07:33:20 UTC Docs Contact lmanasko ajamaiya
Abhimanyu Jamaiyar 2019-10-17 07:56:53 UTC Doc Text Cause: 'sudo' does not preserve the user's environment in the spawned subprocess, including information about how to connect to the graphical display.

Consequence: Graphical applications may fail to launch with an error saying "No protocol specified" or "connection refused".

Workaround (if any): Export the user's environment to the subprocess by running "sudo -E" instead of plain "sudo".

Result: Graphical applications can run as a privileged user.
.The `sudo` command is unable to connect to the graphical display

The `sudo` command is not able to preserve information about connecting to the graphical display. As a result, `sudo` is unable to launch graphical applications and the following error messages appear:

`No protocol specified`
or
`Connection refused`

To work around this problem, run `sudo-E` to export the user’s environment to a subprocess. It will run graphical applications as a privileged user.
Flags needinfo?(ajax)
Abhimanyu Jamaiyar 2019-11-01 10:49:59 UTC Flags needinfo?(ajax)
Lucie Vařáková 2020-04-16 15:23:24 UTC Docs Contact ajamaiya lvaleeva
Levi 2020-04-20 05:59:49 UTC Flags needinfo?(ajax)
Levi 2020-04-20 14:31:09 UTC Doc Text .The `sudo` command is unable to connect to the graphical display

The `sudo` command is not able to preserve information about connecting to the graphical display. As a result, `sudo` is unable to launch graphical applications and the following error messages appear:

`No protocol specified`
or
`Connection refused`

To work around this problem, run `sudo-E` to export the user’s environment to a subprocess. It will run graphical applications as a privileged user.
.Unable to run graphical applications using `sudo` command

When trying to run graphical applications as a user with elevated privileges, the application fails to open with an error message due to Xwayland being restricted by the Xauthority file to use regular user credentials for authentication.

To work around this problem, use the `sudo-E` command to run graphical applications as a `root` user.
Levi 2020-04-20 14:32:37 UTC Doc Text .Unable to run graphical applications using `sudo` command

When trying to run graphical applications as a user with elevated privileges, the application fails to open with an error message due to Xwayland being restricted by the Xauthority file to use regular user credentials for authentication.

To work around this problem, use the `sudo-E` command to run graphical applications as a `root` user.
.Unable to run graphical applications using `sudo` command

When trying to run graphical applications as a user with elevated privileges, the application fails to open with an error message due to Xwayland being restricted by the Xauthority file to use regular user credentials for authentication.

To work around this problem, use the `sudo -E` command to run graphical applications as a `root` user.
Adam Jackson 2020-04-20 15:46:42 UTC Flags needinfo?(ajax)
Levi 2020-04-20 16:08:58 UTC Doc Text .Unable to run graphical applications using `sudo` command

When trying to run graphical applications as a user with elevated privileges, the application fails to open with an error message due to Xwayland being restricted by the Xauthority file to use regular user credentials for authentication.

To work around this problem, use the `sudo -E` command to run graphical applications as a `root` user.
.Unable to run graphical applications using `sudo` command

When trying to run graphical applications as a user with elevated privileges, the application fails to open with an error message. The failure happens because `Xwayland` is restricted by the `Xauthority` file to use regular user credentials for authentication.

To work around this problem, use the `sudo -E` command to run graphical applications as a `root` user.
Flags needinfo?(ajax) needinfo?(ajax)
Lucie Vařáková 2020-06-10 15:00:01 UTC CC lvaleeva
Flags needinfo?(lvaleeva)
Levi 2020-06-10 15:59:34 UTC Flags needinfo?(lvaleeva)
Yuki Okada 2020-07-29 00:55:20 UTC CC yuokada
Lucie Vařáková 2021-01-20 12:00:50 UTC CC lmanasko
Flags needinfo?(lvaleeva)
Levi 2021-01-25 09:06:34 UTC Flags needinfo?(lvaleeva)
Pasi Karkkainen 2022-11-09 15:34:47 UTC CC pasik
Davis Johnston 2023-07-15 07:22:49 UTC CC amayahaley23
Jonathan Wakely 2023-07-17 14:58:01 UTC Comment 17 Tag spam

Back to bug 1673073