Bug 1880773 - KDE desktop does not run anymore in tiger-vncserver (black screen)
Summary: KDE desktop does not run anymore in tiger-vncserver (black screen)
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: tigervnc
Version: 32
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Jan Grulich
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-19 20:50 UTC by George Petasis
Modified: 2020-09-21 19:59 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-09-21 19:59:29 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description George Petasis 2020-09-19 20:50:44 UTC
Description of problem:
After the update to 1.11.0-1.fc32 and following the instructions on https://src.fedoraproject.org/rpms/tigervnc/blob/master/f/HOWTO.md, my desktop is still not running. I have specified "session=plasma" in my vnc config, but I only get a black screen (i.e. no window manager is running).


Version-Release number of selected component (if applicable):
Fedora 32, tiger-vncserver 1.11.0-1.fc32

How reproducible:
Start a KDE session under vnc server


Steps to Reproduce:
1. Put "session=plasma" in your .vnc/config
2. Start tiger-vncserver
3.

Actual results:
Black screen

Expected results:
A KDE desktop

Additional info:

Comment 1 Jan Grulich 2020-09-21 06:41:49 UTC
Do you start the server for a user who is already logged in graphically? Do you see anything in the logs in $HOME/.vnc? Or when you run "systemctl status service_name"?

Comment 2 Jan Grulich 2020-09-21 07:22:35 UTC
I tested it, created a new user, ran "vncpasswd" to set a password and configured /etc/tigervnc/vncserver-config-defaults with "session=plasma". After starting a VNC server I could connect and saw Plasma desktop.

Comment 3 George Petasis 2020-09-21 19:59:29 UTC
After re-trying today, I also get a KDE desktop.
Perhaps due to the updates installed today?

But I cannot reproduce it anymore.
I am going to close this bug.


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