|
Bugzilla – Full Text Bug Listing |
| Summary: | [doc] VNC session initiated using vncserver | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Fergal Mc Carthy <fmccarthy> |
| Component: | Documentation | Assignee: | Tomáš Bažant <tbazant> |
| Status: | RESOLVED FIXED | QA Contact: | Frank Sundermeyer <fs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | ext.josef.prazak, tbazant |
| Version: | Leap 15.5 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | https://jira.suse.com/browse/DOCTEAM-1028 | ||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Fergal Mc Carthy
2023-06-13 15:13:47 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. Thank you for reporting this bug! It is being tracked and processed as part of our queue. *** Bug 1215105 has been marked as a duplicate of this bug. *** |