Bug 1539131 - Vncserver can not start Xsession without native Xsession running
Summary: Vncserver can not start Xsession without native Xsession running
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: tigervnc
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Jan Grulich
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-26 18:25 UTC by Knud Christiansen
Modified: 2018-07-15 14:48 UTC (History)
4 users (show)

Fixed In Version: tigervnc-1.8.0-10.fc27
Clone Of:
Environment:
Last Closed: 2018-06-16 19:32:53 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Vnc log (997 bytes, text/plain)
2018-01-26 18:25 UTC, Knud Christiansen
no flags Details

Description Knud Christiansen 2018-01-26 18:25:59 UTC
Created attachment 1386630 [details]
Vnc log

Description of problem:


Version-Release number of selected component (if applicable):
Tigervnc 1.8.0-5.fc26

How reproducible:
always

Steps to Reproduce:
1.Install Tigervnc
2.Enable a user vncserver by copy vncserver@:x.service and adjust
3.systemctl enabl and start vncserver@:x and reboot

Actual results:
connecting to vncserver gives black screen with mouse pointer

Expected results:
Vnc screen

Additional info:
1.doing the same with root user does work

2. Log in with that user local access and restart vncserver@:x, afterwards you can log out
Then remote vnc access works

Happends also in F27

Comment 1 Fedora End Of Life 2018-05-03 08:21:03 UTC
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 Fedora Update System 2018-06-13 11:50:46 UTC
tigervnc-1.8.0-10.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2018-817f36c368

Comment 3 Fedora Update System 2018-06-14 13:48:28 UTC
tigervnc-1.8.0-10.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2018-817f36c368

Comment 4 Fedora Update System 2018-06-16 19:32:53 UTC
tigervnc-1.8.0-10.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report.

Comment 5 Knud Christiansen 2018-07-15 14:48:44 UTC
Problem still persists 

fc27 kernel 4.17.5-100

tigervnc-1.8.0-10 x86_64


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