Bug 754259 - Example systemd service script does not run vncserver in login shell
Summary: Example systemd service script does not run vncserver in login shell
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: tigervnc
Version: 16
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Adam Tkac
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-15 20:58 UTC by Orion Poplawski
Modified: 2013-04-30 23:50 UTC (History)
3 users (show)

Fixed In Version: tigervnc-1.1.0-3.fc16
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-02 21:26:50 UTC
Type: ---


Attachments (Terms of Use)

Description Orion Poplawski 2011-11-15 20:58:24 UTC
Description of problem:

The example systemd service script does not run vncserver in login shell.  This can cause a lot of problems for the session started.  I would suggest:

ExecStart=/sbin/runuser -l <USER> -c "/usr/bin/vncserver -nolisten tcp %i"

and no User= line.  Unless it seems worthwhile to add login shell capability to systemd.

Version-Release number of selected component (if applicable):
tigervnc-server-1.1.0-2.fc16.x86_64

Comment 1 Fedora Update System 2011-11-22 14:27:42 UTC
tigervnc-1.1.0-3.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/tigervnc-1.1.0-3.fc16

Comment 2 Fedora Update System 2011-11-23 00:54:30 UTC
Package tigervnc-1.1.0-3.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing tigervnc-1.1.0-3.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2011-16244/tigervnc-1.1.0-3.fc16
then log in and leave karma (feedback).

Comment 3 Fedora Update System 2011-12-02 21:26:50 UTC
tigervnc-1.1.0-3.fc16 has been pushed to the Fedora 16 stable repository.  If problems still persist, please make note of it in this bug report.


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