Bug 1480847 - VNC crashes after some minutes of successful connection
Summary: VNC crashes after some minutes of successful connection
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 26
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-08-12 10:16 UTC by slartibart70
Modified: 2018-05-29 12:26 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-05-29 12:26:14 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
vnc and journal logs (31.25 KB, application/x-7z-compressed)
2017-08-12 10:19 UTC, slartibart70
no flags Details

Description slartibart70 2017-08-12 10:16:10 UTC
Hi,

i have configured tigervnc-server on my fedora26-xeon server machine, i run it using 
systemctl start vncserver@:1.service
and the vnc session (plasma5) will initalize correclty. Connection via vncviewer is possible and shows the plasma/fc26 desktop. After approx. 1 minute, the server-vnc process crashes and obviously kills my connection.

In the vnc log i see:

Failed to import environment: Process org.freedesktop.systemd1 exited with status 1
startkde: Starting up...

vmware-user: could not open /proc/fs/vmblock/dev

** (process:2177): CRITICAL **: polkit_agent_listener_register_with_options: assertion 'POLKIT_IS_SUBJECT (subject)' failed

(process:2177): GLib-GObject-CRITICAL **: g_object_unref: assertion 'G_IS_OBJECT (object)' failed

in journal i find:

Aug 12 11:57:42 t410 kdeinit5[2108]: The X11 connection broke: I/O error (code 1)
Aug 12 11:57:42 t410 ksmserver[2125]: QProcess: Destroyed while process ("kwin_x11") is still running.
Aug 12 11:57:42 t410 ksmserver[2125]: QProcess: Destroyed while process ("/usr/libexec/kdeconnectd") is still running.
Aug 12 11:57:42 t410 ksmserver[2125]: ksmserver: autostart service ("") finished with exit code  15
Aug 12 11:57:42 t410 ksmserver[2125]: QProcess: Destroyed while process ("/usr/bin/krunner") is still running.
Aug 12 11:57:42 t410 drkonqi[2859]: QXcbConnection: Could not connect to display :1
Aug 12 11:57:42 t410 audit[2859]: ANOM_ABEND auid=4294967295 uid=10001 gid=10001 ses=4294967295 subj=system_u:system_r:unconfined_service_t:s0 pid=2859 
Aug 12 11:57:42 t410 systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Aug 12 11:57:42 t410 systemd[1]: Started Process Core Dump (PID 2860/UID 0).

Any idea how to address this problem?
(btw, it was working successfully in previous fedora version using same configuration/hardware)

Please find logs attached to this report

Comment 1 slartibart70 2017-08-12 10:19:49 UTC
Created attachment 1312395 [details]
vnc and journal logs

Comment 2 slartibart70 2017-08-12 11:31:48 UTC
I think i found the problem: se-linux (again...:-))))

I created this rule:

# cat my-systemd.te 

module my-systemd 1.0;

require {
        type user_home_t;
        type init_t;
        class file { open read unlink };
}

#============= init_t ==============
allow init_t user_home_t:file { open read unlink };


and now it works
Would you please check if this rule needs to be added to the default vnc rules?

Comment 3 slartibart70 2017-08-16 07:33:48 UTC
modified component of this report

Comment 4 Fedora End Of Life 2018-05-03 08:06:11 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 5 Fedora End Of Life 2018-05-29 12:26:14 UTC
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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