FEDORA-2020-98137c59f8 created by jgrulich a month ago for Fedora 32
testing

Provide vncserver from older releases so users can keep using it, however it will also notify about its upcoming removal and users are advised to read HOWTO.md documentation file.

How to install

sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-98137c59f8

This update has been submitted for testing by jgrulich.

a month ago

This update's test gating status has been changed to 'ignored'.

a month ago

This update's test gating status has been changed to 'waiting'.

a month ago

jgrulich edited this update.

a month ago

This update's test gating status has been changed to 'ignored'.

a month ago

jgrulich edited this update.

a month ago

This update has been pushed to testing.

a month ago
User Icon pwalter commented & provided feedback a month ago
karma

Works

User Icon cserpentis commented & provided feedback a month ago
karma

works for me

This update can be pushed to stable now if the maintainer wishes

a month ago

jgrulich edited this update.

New build(s):

  • tigervnc-1.11.0-3.fc32

Removed build(s):

  • tigervnc-1.11.0-2.fc32

Karma has been reset.

a month ago

This update has been submitted for testing by jgrulich.

a month ago

jgrulich edited this update.

New build(s):

  • tigervnc-1.11.0-4.fc32

Removed build(s):

  • tigervnc-1.11.0-3.fc32

Karma has been reset.

a month ago

This update has been pushed to testing.

a month ago
User Icon srking commented & provided feedback a month ago
karma

Applied patch as directed on F32. Executing /usr/bin/vncserver gives:

Please read /usr/share/doc/tigervnc/HOWTO.md for more information.

However, /usr/share/doc/tigervnc/HOWTO.md was not installed.

Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.

a month ago

jgrulich edited this update.

New build(s):

  • tigervnc-1.11.0-5.fc32

Removed build(s):

  • tigervnc-1.11.0-4.fc32

Karma has been reset.

a month ago

This update has been submitted for testing by jgrulich.

a month ago
User Icon thomasb commented & provided feedback 3 weeks ago
karma

I get the same problem as srking reported (the HOWTO.md is not there).

Also, I can not install a vncserver@:x service with selinux enforcing enabled. I tried generating policy packages but have not been successfull so far.

Note hat running

/usr/libexec/vncsession-start :1

as root in a bash shell works fine (and this is what the vncserver@.service skript does).

Here is what audit.log looks like from vncsession-start (working): type=USER_ROLE_CHANGE msg=audit(1600934142.019:26025): pid=1438766 uid=0 auid=1449 ses=156 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='pam: default-context=unconfined_u:unconfined_r:unconfined_t:s0 selected-context=unconfined_u:unconfined_r:unconfined_t:s0 exe="/usr/sbin/vncsession" hostname=203.0.113.20 addr=203.0.113.20 terminal=? res=success'UID="root" AUID="thomasb" type=USER_START msg=audit(1600934142.037:26026): pid=1438766 uid=0 auid=1449 ses=156 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=PAM:session_open grantors=pam_selinux,pam_loginuid,pam_selinux,pam_namespace,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="thomasb" exe="/usr/sbin/vncsession" hostname=203.0.113.20 addr=203.0.113.20 terminal=? res=success'UID="root" AUID="thomasb"

Here is what I get from a "systemctl start vncserver@:1" after removing some type enforcement errors already. Note the SERVICE_START immediately followed by USER_END I don't understand why the same session is immediately ending here.

type=LOGIN msg=audit(1600934244.462:26028): pid=1439745 uid=0 subj=system_u:system_r:vnc_session_t:s0 old-auid=4294967295 auid=1449 tty=(none) old-ses=4294967295 ses=175 res=1UID="root" OLD-AUID="unset" AUID="thomasb" type=USER_ROLE_CHANGE msg=audit(1600934244.463:26029): pid=1439745 uid=0 auid=1449 ses=175 subj=system_u:system_r:vnc_session_t:s0 msg='pam: default-context=unconfined_u:unconfined_r:unconfined_t:s0 selected-context=unconfined_u:unconfined_r:unconfined_t:s0 exe="/usr/sbin/vncsession" hostname=203.0.113.20 addr=203.0.113.20 terminal=? res=success'UID="root" AUID="thomasb" type=USER_START msg=audit(1600934244.486:26030): pid=1439745 uid=0 auid=1449 ses=175 subj=system_u:system_r:vnc_session_t:s0 msg='op=PAM:session_open grantors=pam_selinux,pam_loginuid,pam_selinux,pam_namespace,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="thomasb" exe="/usr/sbin/vncsession" hostname=203.0.113.20 addr=203.0.113.20 terminal=? res=success'UID="root" AUID="thomasb" type=SERVICE_START msg=audit(1600934244.488:26031): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=vncserver@:1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'UID="root" AUID="unset" type=USER_END msg=audit(1600934244.493:26032): pid=1439745 uid=0 auid=1449 ses=175 subj=system_u:system_r:vnc_session_t:s0 msg='op=PAM:session_close grantors=pam_selinux,pam_loginuid,pam_selinux,pam_namespace,pam_keyinit,pam_limits,pam_systemd,pam_unix acct="thomasb" exe="/usr/sbin/vncsession" hostname=203.0.113.20 addr=203.0.113.20 terminal=? res=success'UID="root" AUID="thomasb" type=SERVICE_STOP msg=audit(1600934244.494:26033): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=vncserver@:1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'UID="root" AUID="unset"

User Icon jgrulich commented & provided feedback 3 weeks ago

The HOWTO.md should be in tigervnc-1.11.0-5.fc32 build. Also try to run restorecon -RFv /home/<USER>/.vnc for the user which doesn't work for you.

User Icon thomasb commented & provided feedback 3 weeks ago

Thx for the howto.

Regarding the selinux: That was indeed the problem. The rules that are installed with tigervnc seem to apply only to paths of the form given above, ie user home directories need to be under /home.

On my system they aren't - some local user's home dirs are there but most are nfs mounts under /user/<USER>/

Would it be possible to make the rule more flexible?

Or maybe the rule is actually OK, and my system is not set up correctly. I found the option "usepasswd" in /etc/selinux/semanage.conf and changed it to true, however is made no immediate difference (the restorecon still does nothing to user homedirs under /user/)

This update has been pushed to testing.

3 weeks ago
User Icon srking commented & provided feedback 3 weeks ago
karma

Works for me.

jgrulich edited this update.

New build(s):

  • tigervnc-1.11.0-6.fc32

Removed build(s):

  • tigervnc-1.11.0-5.fc32

Karma has been reset.

3 weeks ago

This update has been submitted for testing by jgrulich.

3 weeks ago

This update has been pushed to testing.

3 weeks ago
User Icon filiperosset commented & provided feedback 2 weeks ago
karma

no regressions noted

This update can be pushed to stable now if the maintainer wishes

2 weeks ago

Please login to add feedback.

Metadata
Type
bugfix
Karma
1
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
disabled
Stable by Time
disabled
Dates
submitted
a month ago
in testing
3 weeks ago
modified
3 weeks ago
BZ#1865580 tigervnc: FTBFS in Fedora rawhide/f33
0
0
BZ#1877158 tigervnc-1.11.0 is available
0
0
BZ#1879739 Add a /usr/bin/vncserver script that points users to new instructions
0
0
BZ#1880131 tigervnc-server-module overrides my /etc/X11/xorg.conf.d/10-libvnc.conf
0
0
BZ#1881752 dnf install tigervnc-server does not install /usr/bin/vncserver. Reports "Failed to preset unit: Unit file xvnc.service does not exist"
0
0
BZ#1883027 vncserver has been replaced by a systemd unit
0
0

Automated Test Results