FS#42425 - [lxsession] no session for pid xxxxx when vncserver service is started
Attached to Project:
Community Packages
Opened by John (graysky) - Friday, 17 October 2014, 21:01 GMT
Last edited by Balló György (City-busz) - Friday, 07 November 2014, 11:04 GMT
Opened by John (graysky) - Friday, 17 October 2014, 21:01 GMT
Last edited by Balló György (City-busz) - Friday, 07 November 2014, 11:04 GMT
|
Details
Since updating to 1:0.5.0-1, starting an lxde-session via
systemd service calling vnc (tigervnc) causes an error upon
startup that reads, "Error: No session for pid xxxxx." When
I `ps aux | grep xxxxx` the offending pid belongs to
lxpolkit. For example:
% ps aux | grep 30426 facade 30426 0.1 0.4 252236 18012 ? Sl 16:40 0:00 lxpolkit There is nothing relevant in ~/.vnc/hostname:1.log but this is reproducible on several machines. Additional info: * package version(s) 1:0.5.0-1 Steps to reproduce: 1) install tigervnc and lxde 2) create ~/.vnc/xstartup that contains a single line that reads: exec startlxde 3) cp /usr/lib/systemd/system/vncserver.service /etc/systemd/system/vncserver@:1.service 4) configure this file setting up the user to run vncsession 5) configure a passwd for vnc (first time run only) via `vncserver :1` and then kill the server `vncserver -kill :1` 6) start the systemd service to observe the error |
This task depends upon
Closed by Balló György (City-busz)
Friday, 07 November 2014, 11:04 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#42703
Friday, 07 November 2014, 11:04 GMT
Reason for closing: Duplicate
Additional comments about closing:
BOTH changes were necessary for me -- both the PAMName directive and changing the service to be non-forking. Neither by itself was effective.
YMMV.
FS#42703. Thank you, necopinus.