Error in Connecting to VNC Server Using SSH #25

Open
opened 2024-05-31 13:16:12 +00:00 by pbokoc · 1 comment
pbokoc commented 2024-05-31 13:16:12 +00:00 (Migrated from gitlab.com)

(Migrated from https://bugzilla.redhat.com/show_bug.cgi?id=1412493)

Description of problem:
The current Fedora 25 systemd will error if you start a unit with the line
"ExecStart=/sbin/runuser -l user -c "/usr/bin/vncserver -localhost %i"" when you have edited the user details.

Version-Release number of selected component (if applicable):
Draft Fedora 25 Administrators Guide Edition 1

How reproducible:
Every time

Steps to Reproduce:

  1. Implement a vncserver as detailed in https://docs.fedoraproject.org/en-US/Fedora/25/html/System_Administrators_Guide/ch-TigerVNC.html
  2. Edit the respective /etc/systemd/system/vncserver@.service file by replacing the user details
  3. Start the server using "systemctl start vncserver@:1.server" or as a no root user "sudo systemctl start vncserver@:1.server" and it fails

Actual results:
/sbin/runuser can only be run by root

Expected results:
vnc server starts

Additional info:
I think the problem is created as the vncserver@.service file set the process owner as defined in the line "User=". When I have set that to a non-root user name the file errors.

The standard file line "ExecStart=/usr/bin/vncserver %i" works fine. The errata seems to be a hangover from the old file structure.

(Migrated from https://bugzilla.redhat.com/show_bug.cgi?id=1412493) Description of problem: The current Fedora 25 systemd will error if you start a unit with the line "ExecStart=/sbin/runuser -l user -c "/usr/bin/vncserver -localhost %i"" when you have edited the user details. Version-Release number of selected component (if applicable): Draft Fedora 25 Administrators Guide Edition 1 How reproducible: Every time Steps to Reproduce: 1. Implement a vncserver as detailed in https://docs.fedoraproject.org/en-US/Fedora/25/html/System_Administrators_Guide/ch-TigerVNC.html 2. Edit the respective /etc/systemd/system/vncserver@.service file by replacing the user details 3. Start the server using "systemctl start vncserver@:1.server" or as a no root user "sudo systemctl start vncserver@:1.server" and it fails Actual results: /sbin/runuser can only be run by root Expected results: vnc server starts Additional info: I think the problem is created as the vncserver@.service file set the process owner as defined in the line "User=<USER>". When I have set that to a non-root user name the file errors. The standard file line "ExecStart=/usr/bin/vncserver %i" works fine. The errata seems to be a hangover from the old file structure.
vgaetera commented 2024-10-25 04:09:57 +00:00 (Migrated from gitlab.com)

mentioned in merge request !53

mentioned in merge request !53
Commenting is not possible because the repository is archived.
No labels
No milestone
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
docs-archive/sysadmin-guide#25
No description provided.