Bug 1212280 - [doc] VNC session initiated using vncserver
Summary: [doc] VNC session initiated using vncserver
Status: RESOLVED FIXED
: 1215105 (view as bug list)
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: Documentation (show other bugs)
Version: Leap 15.5
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Tomáš Bažant
QA Contact: Frank Sundermeyer
URL:
Whiteboard: https://jira.suse.com/browse/DOCTEAM-...
Keywords:
Depends on:
Blocks:
 
Reported: 2023-06-13 15:13 UTC by Fergal Mc Carthy
Modified: 2023-09-13 12:25 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Fergal Mc Carthy 2023-06-13 15:13:47 UTC 
VNC session initiated using vncserver:

https://doc.opensuse.org/documentation/leap/reference/single-html/book-reference/index.html#vnc-persistent-vncserver

There doesn't appear to be a vncserver command available in the Leap 15.5 packages:

% cnf vncserver
 vncserver: command not found
% zypper se --provides /usr/bin/vncserver
Loading repository data...
Reading installed packages...
No matching items found.

I upgraded my Leap 15.4 system (which had a working VNC Server environment) to Leap 15.5.

After doing so I was unable to start the vncserver like I normally do because there was no vncserver command installed.
Comment 1 Fergal Mc Carthy 2023-06-13 15:58:21 UTC 
Looks like the standalone server has been removed from tigervnc per https://github.com/TigerVNC/tigervnc/issues/1193

Instead we can start user specific standalone sessions using vncsession, e.g.

% sudo vncsession ${USER} :${VNC_DISPLAY_NUMBER}

However this does require that the vncsession command is run with root privileges, e.g. via the sudo command as shown above.
Comment 2 Tomáš Bažant 2023-06-27 13:25:12 UTC 
Thank you for reporting this bug!
It is being tracked and processed as part of our queue.
Comment 3 Tomáš Bažant 2023-09-13 07:18:51 UTC 
*** Bug 1215105 has been marked as a duplicate of this bug. ***