[systemd] Let services wait until X is started [solved]

Hi there,
I have a quick question. I have some services that I would like to start once X is started. Is the only way to currently achieve this by using a display manager (graphical.target)?
Thanks ahead!
Last edited by orschiro (2014-06-22 11:42:50)

The problem is the login sessions...
I don't use systemd user sessions (actively) but this looks like something that could probably do what you want: https://wiki.archlinux.org/index.php/Sy … ay_manager
Last edited by rebootl (2014-06-21 12:06:54)

Similar Messages

Systemd vboxweb.service mod when needing to start as non-root user

Hi,
Don't know if this will help anyone, but here goes,
I wanted the systemd service unit to run using my local account but to get this to work, I had to do the following:
1. Create a file called vboxweb_mod.conf in /etc/tmpfiles.d with the below inside it (replace <user> <group> with your username and group you want vboxweb started with.)
D /run/vboxweb 0755 <user> <group>
2. Create /etc/systemd/system/vboxweb_mod.service to look like this: (replace <user> <group> with your username and group you want vboxweb started with.)
[Unit]
Description=VirtualBox Web Service
After=network.target
[Service]
Type=forking
PIDFile=/run/vboxweb/vboxweb.pid
ExecStart=/usr/bin/vboxwebsrv --pidfile /run/vboxweb/vboxweb.pid --background
User=<user>
Group=<group>
[Install]
WantedBy=multi-user.target
3. Issue command
#systemctl enable vboxweb_mod.service
4. Either reboot or issue command
#systemctl start vboxweb_mod.service
Hope this helps someone out. (I had to do something similar to get sabnzbd running correctly as a systemd service. :-))

Thanks, you helped me. I had gotten hung up on '--user = <vboxuser>' in the ExecStart line, which works for one of my other services, but not this one.

Cannot start systemd-logind.service when booting.

The boot sequence had a logind.service fail, and then was stuck when trying to open the Gnome Display Manager. The output was:
Starting Login Service...
[FAILED] Failed to start Login Service.
See "systemctl status systemd-logind.service" for details.
Stopping Login Service...
[ OK ] Stopped Login Service.
Starting Login Service...
[FAILED] Failed to start Login Service.
See "systemctl status systemd-logind.service" for
Stopping Login Service...
[ OK ] Stopped Login Service.
Starting Login Service...
[FAILED] Failed to start Login Service.
See "systemctl status systemd-logind.service" for details.
[ OK ] Started dhcpd on enp4s0.
[ OK ] Reached target Network.
Starting Network Time Service...
[ OK ] Started Network Time Service.
[ OK ] Reached target Multi-User System.
[FAILED] Failed to start GNOME Display Manager.
See "systemctl status gdm.service" for details.
[ OK ] Reached target Graphical Interface.
I have disabled the gdm.service using an installation disk with chroot in order to login, and after the restart I tried `sudo systemctl status systemd-logind.service`. The output is:
● systemd-logind.service - Login Service
Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static; vendor preset: disabled)
Active: failed (Result: start-limit) since 月 2015-04-06 17:59:52 JST; 56s ago
Docs: man:systemd-logind.service(8)
man:logind.conf(5)
http://www.freedesktop.org/wiki/Software/systemd/logind
http://www.freedesktop.org/wiki/Software/systemd/multiseat
Process: 249 ExecStart=/usr/lib/systemd/systemd-logind (code=exited, status=1/FAILURE)
Main PID: 249 (code=exited, status=1/FAILURE)
Status: "Shutting down..."
4月 06 17:59:52 masasin-arch systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
4月 06 17:59:52 masasin-arch systemd[1]: Stopping Login Service...
4月 06 17:59:52 masasin-arch systemd[1]: Starting Login Service...
4月 06 17:59:52 masasin-arch systemd[1]: start request repeated too quickly for systemd-logind.service
4月 06 17:59:52 masasin-arch systemd[1]: Failed to start Login Service.
4月 06 17:59:52 masasin-arch systemd[1]: Unit systemd-logind.service entered failed state.
4月 06 17:59:52 masasin-arch systemd[1]: systemd-logind.service failed.
At the moment, I cannot get into any graphical environments, but I do have access to the shell.
Let me know if you need more information.

I ran
journalctl -b -u systemd-logind
right after a reboot, and the output is as follows:
-- Logs begin at 水 2013-08-21 08:01:49 JST, end at 水 2015-04-08 18:26:45 JST. --
4月 08 18:26:14 masasin-arch systemd[1]: Starting Login Service...
4月 08 18:26:14 masasin-arch systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
4月 08 18:26:14 masasin-arch systemd[1]: Failed to start Login Service.
4月 08 18:26:14 masasin-arch systemd[1]: Unit systemd-logind.service entered failed state.
4月 08 18:26:14 masasin-arch systemd[1]: Unit systemd-logind.service failed.
4月 08 18:26:14 masasin-arch systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
4月 08 18:26:14 masasin-arch systemd[1]: Stopping Login Service...
4月 08 18:26:14 masasin-arch systemd[1]: Starting Login Service...
4月 08 18:26:15 masasin-arch systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
4月 08 18:26:15 masasin-arch systemd[1]: Failed to start Login Service.
4月 08 18:26:15 masasin-arch systemd[1]: Unit systemd-logind.service entered failed state.
4月 08 18:26:15 masasin-arch systemd[1]: Unit systemd-logind.service failed.
4月 08 18:26:15 masasin-arch systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
4月 08 18:26:15 masasin-arch systemd[1]: Stopping Login Service...
4月 08 18:26:15 masasin-arch systemd[1]: Starting Login Service...
4月 08 18:26:15 masasin-arch systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
4月 08 18:26:15 masasin-arch systemd[1]: Failed to start Login Service.
4月 08 18:26:15 masasin-arch systemd[1]: Unit systemd-logind.service entered failed state.
4月 08 18:26:15 masasin-arch systemd[1]: Unit systemd-logind.service failed.
4月 08 18:26:15 masasin-arch systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
4月 08 18:26:15 masasin-arch systemd[1]: Stopping Login Service...
4月 08 18:26:15 masasin-arch systemd[1]: Starting Login Service...
4月 08 18:26:15 masasin-arch systemd-logind[257]: Failed to connect to system bus: No such file or directory
4月 08 18:26:15 masasin-arch systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
4月 08 18:26:15 masasin-arch systemd[1]: Failed to start Login Service.
4月 08 18:26:15 masasin-arch systemd[1]: Unit systemd-logind.service entered failed state.
4月 08 18:26:15 masasin-arch systemd[1]: Unit systemd-logind.service failed.
4月 08 18:26:15 masasin-arch systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
4月 08 18:26:15 masasin-arch systemd[1]: Stopping Login Service...
4月 08 18:26:15 masasin-arch systemd[1]: Starting Login Service...
4月 08 18:26:15 masasin-arch systemd-logind[257]: Failed to connect to system bus: No such file or directory
4月 08 18:26:15 masasin-arch systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
4月 08 18:26:15 masasin-arch systemd[1]: Failed to start Login Service.
4月 08 18:26:15 masasin-arch systemd[1]: Unit systemd-logind.service entered failed state.
4月 08 18:26:15 masasin-arch systemd[1]: Unit systemd-logind.service failed.
4月 08 18:26:15 masasin-arch systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
4月 08 18:26:15 masasin-arch systemd[1]: Stopping Login Service...
4月 08 18:26:15 masasin-arch systemd[1]: Starting Login Service...
4月 08 18:26:15 masasin-arch systemd[1]: start request repeated too quickly for systemd-logind.service
4月 08 18:26:15 masasin-arch systemd[1]: Failed to start Login Service.
4月 08 18:26:15 masasin-arch systemd[1]: Unit systemd-logind.service entered failed state.
4月 08 18:26:15 masasin-arch systemd[1]: Unit systemd-logind.service failed.

[SOLVED] Trouble with running systemd user service on login

I'm trying to get emacs to run as a systemd/user service so that it will start up faster, as suggested in the wiki article, but I'm having some problems.
I can't get the service to run as soon as I log in. I can run the service with
systemctl --user start emacs
and it will run for the rest of my session, but if I try to run
systemctl --user enable emacs
I get the following error:
The unit files have no [Install] section. They are not meant to be enabled
using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
I ran
systemctl --user is-enabled emacs
and that returned
static
but I'm not sure what that means. Any help would be greatly appreciated.
Last edited by whitebrice (2014-06-28 17:20:13)

Are you sure there isn't a typo in your unit file? The example you linked to in the wiki does have an [Install] section.
Post your ~/.config/systemd/user/emacs.service file here so we can take a look.

[solved] What makes systemd-logind.service fail?

After last update made yesterday I was unable to reboot. With the help of an installation cd and chrooting I disabled my graphical login manager lxdm which, when started, seems to do nothing and the system is stuck.
Without lxdm service enabled, I can start xfce4 with
startxfce4
from commandline and everything seems to run fine.
But the booting process gives me several messages telling that the service systemd-logind failed. Apart from the virtual console created while booting and the one running X11 there is no other one (no login prompt when pressing strg+alt f3 e.g.)
[root@amd64-archlinux ~]# systemctl status systemd-logind
● systemd-logind.service - Login Service
Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static)
Active: failed (Result: start-limit) since Sun 2014-06-08 19:09:24 CEST; 5min ago
Docs: man:systemd-logind.service(8)
man:logind.conf(5)
http://www.freedesktop.org/wiki/Software/systemd/logind
http://www.freedesktop.org/wiki/Software/systemd/multiseat
Process: 336 ExecStart=/usr/lib/systemd/systemd-logind (code=exited, status=1/FAILURE)
Main PID: 336 (code=exited, status=1/FAILURE)
Status: "Shutting down..."
Jun 08 19:09:24 amd64-archlinux systemd[1]: Failed to start Login Service.
Jun 08 19:09:24 amd64-archlinux systemd[1]: Unit systemd-logind.service entered failed state.
Jun 08 19:09:24 amd64-archlinux systemd[1]: systemd-logind.service has no holdoff time, scheduling restart.
Jun 08 19:09:24 amd64-archlinux systemd[1]: Stopping Login Service...
Jun 08 19:09:24 amd64-archlinux systemd[1]: Starting Login Service...
Jun 08 19:09:24 amd64-archlinux systemd[1]: systemd-logind.service start request repeated too quickly, refusing to start.
Jun 08 19:09:24 amd64-archlinux systemd[1]: Failed to start Login Service.
Jun 08 19:09:24 amd64-archlinux systemd[1]: Unit systemd-logind.service entered failed state.
Has anyone an idea where to lead me?
Last edited by bernd_b (2014-06-09 11:20:21)

I don't know if I got you point - but here is a try:
I am running X11 started manually with "startxfce4". So firing up a konsole in X11 I do and get
root@amd64-archlinux pkg]# systemctl stop systemd-logind
[root@amd64-archlinux pkg]# systemctl start systemd-logind
Job for systemd-logind.service failed. See 'systemctl status systemd-logind.service' and 'journalctl -xn' for details.
journalctl -xn:
-- Unit systemd-logind.service has begun shutting down.
Jun 08 21:38:18 amd64-archlinux systemd[1]: Starting Login Service...
-- Subject: Unit systemd-logind.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-logind.service has begun starting up.
Jun 08 21:38:18 amd64-archlinux systemd[1]: systemd-logind.service start request repeated too quickly, refusing to start.
Jun 08 21:38:18 amd64-archlinux systemd[1]: Failed to start Login Service.
-- Subject: Unit systemd-logind.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Unit systemd-logind.service has failed.
-- The result is failed.
I ran the service directly I get:
[root@amd64-archlinux pkg]# /usr/lib/systemd/systemd-logind
Failed to connect to system bus: No such file or directory
Failed to fully start up daemon: No such file or directory
What I figured out so far is this in addition:
- krusader does not start- there is no response or message in the konsole when firing up this application.
- I can only mount nfs-shares with the option "-o nolock" otherwise I get, e.g.
mount.nfs: rpc.statd is not running but is required for remote locking.
mount.nfs: Either use '-o nolock' to keep locks local, or start statd.
mount.nfs: an incorrect mount option was specified
Last edited by bernd_b (2014-06-08 19:48:43)

I am trying to authorise my new macbook air and it won't let me. I try to de-authorise all the other computers and it says I can only do this once a year and have to wait until the 7th Feb. It does not give me an option to authorise this computer

I am trying to authorise my new macbook air for i-tunes and it won't let me. I try to de-authorise all the other computers and it says I can only do this once a year and have to wait until the 7th Feb. It does not give me an option to authorise this computer

Always remember to 'de-authorize' you computer when selling or sending for service. If sending for repairs you might not get the same mother board or HD back and some how this counts as an authorized computer against your count.
MJ

Need to deauthorize again. but systems says I have to wait until february. need to do it now. Spent tons of cash with Apple and need extra special service please

need to deauthorize again. but systems says I have to wait until february. need to do it now. Spent tons of cash with Apple and need extra special service please

You can still deauthorize an individual computer from the iTunes Menus.
You can de-authorize only once a year 'all' computers from your iTunes account page.
MJ

[SOLVED] systemd adsl service does not start

After the today's upgrade of my system I get lines like this in my journal, as the adsl service does not want to start.
# router systemd[522]: Failed at step EXEC spawning /usr/sbin/pppoe-start: No such file or directory
The problem is, that pppoe-start is in /usr/bin/ and not in /usr/sbin. According to pacman (pacman-Ql rp-pppoe) /usr/bin/ is the correct location.
I really don't know, why systemd is trying to launch it, because even the service file (/usr/lib/systemd/system/adsl.service) points to the correct location.
[Unit]
Description=ADSL Deamon
[Service]
Type=forking
ExecStart=/usr/bin/pppoe-start
ExecStop=/usr/bin/pppoe-stop
[Install]
WantedBy=multi-user.target
The service is launching and stopping with pppoe-start and pppoe-stop.
When launched, it also shuts down fine when stopping it by
systemctl stop adsl
Why the hell is it trying to launch from /usr/sbin/?
Last edited by scar (2013-06-04 13:07:23)

It goes definitely against any logic.
The service file looks good, but I've copied it to /usr/lib/systemd/system/bdsl.service. Same contents - and the new one launches succesfully.
I've deleted the original ...adsl.service file, verified that it disappeared, copied it back from the new bdsl.service file, and it still does not launch.
[EDIT]
I've erased the drive, restored the system from a 1 week old backup, started it - everything worked. Then I'v updated the whole system, including the rp-pppoe package, and the adsl service is failing again.
Downgrading solves the problem. Should I file a bug report?
Last edited by scar (2013-06-01 10:14:41)

Return Code value using 'starting new task' and 'wait until'

I'm having a minor issue with some return code values in my ABAP.
This is what part of it used to look like before I modified it:
With Code in version 1, the sy-subrc was not always zero, sometimes it would be 4.
That was fine, and my abap would do something based on the non-zero RC.
had a need to implement an RFC timeout, the only way I could see to do it was to use 'starting new task' etc as seen in Version 2.
However, with my changes, sy-subrc is always zero.
The ABAP runs fine but I know that sy-subrc should sometimes be 4, even when it returns within the allotted 60 seconds.
Maybe I've coded it incorrectly.
Can someone point me in the right direction?
#>> Start of VERSION 1
call function 'MY_FUNCTION_MODULE'
       destination RFCDEST
       tables
            orders_list          = t_orders_packet
            apo_orders_list      = t_apo_orders
            apo_resources        = t_apo_resources
       exceptions
            COMMUNICATION_FAILURE    = 1 MESSAGE MSG_TEXT
            SYSTEM_FAILURE           = 2 MESSAGE MSG_TEXT
            NO_ORDERS_SUPPLIED       = 3
            NO_PEGGED_ORDERS_FOUND   = 4
            ORDERID_CONVERSION_ERROR = 5
            OTHERS                   = 6.
if sy-subrc is initial.
* do some stuff as RC was 0
else.
* log non-zero return code etc
endif.
* << End of Version 1

And now Version 2.
I didn't put this into the 1st post as the formatting goes bonkers.
#>> Start of VERSION 2
call function 'MY_FUNCTION_MODULE'
       destination RFCDEST
       starting new task 'taskname'
       performing receive_result on end of task
       tables
            orders_list          = t_orders_packet
            apo_orders_list      = t_apo_orders
            apo_resources        = t_apo_resources
       exceptions
            COMMUNICATION_FAILURE    = 1 MESSAGE MSG_TEXT
            SYSTEM_FAILURE           = 2 MESSAGE MSG_TEXT
            NO_ORDERS_SUPPLIED       = 3
            NO_PEGGED_ORDERS_FOUND   = 4
            ORDERID_CONVERSION_ERROR = 5
            OTHERS                   = 6.
WAIT UNTIL results_received = 'X' UP TO 60 SECONDS.
if sy-subrc is initial.   << Now this is always ZERO
* do some stuff as RC was 0
else.
* log non-zero return code etc
endif.
FORM receive_result USING iv_taskname.
RECEIVE RESULTS FROM FUNCTION 'MY_FUNCTION_MODULE'
       tables
            orders_list          = t_orders_packet
            apo_orders_list      = t_apo_orders
            apo_resources        = t_apo_resources
       exceptions
            COMMUNICATION_FAILURE    = 1 MESSAGE MSG_TEXT
            SYSTEM_FAILURE           = 2 MESSAGE MSG_TEXT
            NO_ORDERS_SUPPLIED       = 3
            NO_PEGGED_ORDERS_FOUND   = 4
            ORDERID_CONVERSION_ERROR = 5
            OTHERS                   = 6.
results_received = 'X'.
endform.                    "receive_result
* < End of Version 2

Systemd logind.service reports an error: Failed to start login service

Hello,
I found this error in /var/log/errors.log and /var/log/daemon.log although my system functions normally.
It's been written there every 90 seconds!!!!:
Dec 19 23:52:59 localhost systemd[1]: Failed to start Login Service.
Dec 19 23:54:29 localhost systemd[1]: Failed to start Login Service.
Dec 19 23:55:59 localhost systemd[1]: Failed to start Login Service.
Dec 19 23:57:29 localhost systemd[1]: Failed to start Login Service.
Dec 19 23:58:59 localhost systemd[1]: Failed to start Login Service.
the process: systemd-logind.service seems to be working fine:
[xxx@archbox ~]$ sudo systemctl status systemd-logind.service
[sudo] password for xxx:
systemd-logind.service - Login Service
Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static)
Active: activating (start) since Wed, 2012-12-19 23:49:59 CET; 49s ago
Docs: man:systemd-logind.service(8)
man:logind.conf(5)
http://www.freedesktop.org/wiki/Software/systemd/multiseat
Main PID: 11822 (systemd-logind)
CGroup: name=systemd:/system/systemd-logind.service
└─11822 /usr/lib/systemd/systemd-logind
Dec 19 23:49:59 archbox systemd[1]: Starting Login Service...
Dec 19 23:49:59 archbox systemd-logind[11822]: New seat seat0.
Dec 19 23:49:59 archbox systemd-logind[11822]: Watching system buttons on /dev/input/event6 (P...on)
Dec 19 23:49:59 archbox systemd-logind[11822]: Watching system buttons on /dev/input/event7 (V...us)
Dec 19 23:49:59 archbox systemd-logind[11822]: Watching system buttons on /dev/input/event4 (L...ch)
Dec 19 23:49:59 archbox systemd-logind[11822]: Watching system buttons on /dev/input/event5 (S...on)
Dec 19 23:49:59 archbox systemd-logind[11822]: Watching system buttons on /dev/input/event3 (T...ns)
Dec 19 23:49:59 archbox systemd-logind[11822]: New session 1 of user xxx.
Dec 19 23:49:59 archbox systemd-logind[11822]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-...ay.
and journalctl _PID=11822 returns:
Dec 19 23:38:01 archbox sudo[21335]: xxx : TTY=pts/1 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/
Dec 19 23:38:01 archbox sudo[21335]: pam_unix(sudo:session): session opened for user root by xxx(uid
Dec 19 23:38:01 archbox sudo[21335]: pam_unix(sudo:session): session closed for user root
Dec 19 23:38:44 archbox sudo[22682]: xxx : TTY=pts/1 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/
Dec 19 23:38:44 archbox sudo[22682]: pam_unix(sudo:session): session opened for user root by xxx(uid
Dec 19 23:38:44 archbox sudo[22682]: pam_unix(sudo:session): session closed for user root
Dec 19 23:39:10 archbox sudo[23516]: xxx : TTY=pts/1 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/
Dec 19 23:39:10 archbox sudo[23516]: pam_unix(sudo:session): session opened for user root by xxx(uid
Dec 19 23:39:29 archbox systemd[1]: systemd-logind.service operation timed out. Terminating.
Dec 19 23:39:29 archbox systemd[1]: Failed to start Login Service.
Dec 19 23:39:29 archbox systemd[1]: Unit systemd-logind.service entered failed state
Dec 19 23:39:29 archbox systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
Dec 19 23:39:29 archbox systemd[1]: Stopping Login Service...
Dec 19 23:39:29 archbox systemd[1]: Starting Login Service...
Dec 19 23:39:29 archbox systemd-logind[24096]: New seat seat0.
Dec 19 23:39:29 archbox systemd-logind[24096]: Watching system buttons on /dev/input/event6 (Power B
Dec 19 23:39:29 archbox systemd-logind[24096]: Watching system buttons on /dev/input/event7 (Video B
Dec 19 23:39:29 archbox systemd-logind[24096]: Watching system buttons on /dev/input/event4 (Lid Swi
Dec 19 23:39:29 archbox systemd-logind[24096]: Watching system buttons on /dev/input/event5 (Sleep B
Dec 19 23:39:29 archbox systemd-logind[24096]: Watching system buttons on /dev/input/event3 (ThinkPa
Dec 19 23:39:29 archbox systemd-logind[24096]: New session 1 of user xxx.
Dec 19 23:39:29 archbox systemd-logind[24096]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-displa
Dec 19 23:39:30 archbox sudo[23516]: pam_unix(sudo:session): session closed for user root
Dec 19 23:40:08 archbox sudo[25314]: xxx : TTY=pts/1 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/
Dec 19 23:40:08 archbox sudo[25314]: pam_unix(sudo:session): session opened for user root by xxx(uid
Dec 19 23:40:09 archbox sudo[25314]: pam_unix(sudo:session): session closed for user root
Dec 19 23:40:43 archbox slim[641]: error 8: BadMatch (invalid parameter attributes) request 142 mino
Dec 19 23:40:43 archbox slim[641]: error 9: BadDrawable (invalid Pixmap or Window parameter) request
Dec 19 23:40:43 archbox slim[641]: error 4: BadPixmap (invalid Pixmap parameter) request 54 minor 0
Dec 19 23:40:56 archbox sudo[26739]: xxx : TTY=pts/0 ; PWD=/home/xxx ; USER=root ; COMMAND=/usr/bin/
Dec 19 23:40:56 archbox sudo[26739]: pam_unix(sudo:session): session opened for user root by xxx(uid
Dec 19 23:40:59 archbox systemd[1]: systemd-logind.service operation timed out. Terminating.
Dec 19 23:40:59 archbox systemd[1]: Failed to start Login Service.
Dec 19 23:40:59 archbox systemd[1]: Unit systemd-logind.service entered failed state
Dec 19 23:40:59 archbox systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
Dec 19 23:40:59 archbox systemd[1]: Stopping Login Service...
Dec 19 23:40:59 archbox systemd[1]: Starting Login Service...
Dec 19 23:40:59 archbox systemd-logind[26935]: New seat seat0.
Dec 19 23:40:59 archbox systemd-logind[26935]: Watching system buttons on /dev/input/event6 (Power B
Dec 19 23:40:59 archbox systemd-logind[26935]: Watching system buttons on /dev/input/event7 (Video B
Dec 19 23:40:59 archbox systemd-logind[26935]: Watching system buttons on /dev/input/event4 (Lid Swi
Dec 19 23:40:59 archbox systemd-logind[26935]: Watching system buttons on /dev/input/event5 (Sleep B
Dec 19 23:40:59 archbox systemd-logind[26935]: Watching system buttons on /dev/input/event3 (ThinkPa
Dec 19 23:40:59 archbox systemd-logind[26935]: New session 1 of user xxx.
Dec 19 23:40:59 archbox systemd-logind[26935]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-displa
Updating system with pacman didn't solve it.
Did I miss something out while migrating to systemd, is it a problem with SLiM or user session maybe ? Do you guys have any ideas where to start ? Thanks.
Last edited by nastycino (2012-12-30 17:46:43)

My /etc/systemd/logind.conf:
# This file is part of systemd.
# systemd is free software; you can redistribute it and/or modify it
# under the terms of the GNU Lesser General Public License as published by
# the Free Software Foundation; either version 2.1 of the License, or
# (at your option) any later version.
# See logind.conf(5) for details
[Login]
#NAutoVTs=6
#ReserveVT=6
#KillUserProcesses=no
#KillOnlyUsers=
#KillExcludeUsers=root
#Controllers=
#ResetControllers=cpu
#InhibitDelayMaxSec=5
HandlePowerKey=poweroff
HandleSuspendKey=suspend
HandleHibernateKey=hibernate
HandleLidSwitch=suspend
#PowerKeyIgnoreInhibited=no
#SuspendKeyIgnoreInhibited=no
#HibernateKeyIgnoreInhibited=no
#LidSwitchIgnoreInhibited=yes
Is there any way of reinstalling parts of systemd like logind.service?

Systemd-hostnamed.service fails to start

I'm finding the systemd-hostnamed.service isnt working
$ sudo systemctl --state=failed
[sudo] password for kevdog:
UNIT LOAD ACTIVE SUB DESCRIPTION
● systemd-hostnamed.service loaded failed failed Hostname Service
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
$ sudo systemctl status systemd-hostnamed.service
● systemd-hostnamed.service - Hostname Service
Loaded: loaded (/usr/lib/systemd/system/systemd-hostnamed.service; static)
Active: failed (Result: timeout) since Tue 2014-12-16 23:11:36 CST; 10min ago
Docs: man:systemd-hostnamed.service(8)
man:hostname(5)
man:machine-info(5)
http://www.freedesktop.org/wiki/Software/systemd/hostnamed
Main PID: 4584
Dec 16 23:08:35 orphan systemd[1]: systemd-hostnamed.service start operation timed out. Terminating.
Dec 16 23:10:06 orphan systemd[1]: systemd-hostnamed.service stop-final-sigterm timed out. Killing.
Dec 16 23:11:36 orphan systemd[1]: systemd-hostnamed.service still around after final SIGKILL. Entering failed mode.
Dec 16 23:11:36 orphan systemd[1]: Failed to start Hostname Service.
Dec 16 23:11:36 orphan systemd[1]: Unit systemd-hostnamed.service entered failed state.
Dec 16 23:11:36 orphan systemd[1]: systemd-hostnamed.service failed.
I found this addressed in this topic:
https://github.com/ev3dev/ev3dev/issues/189
Within this page they state:
Confirmed that removing PrivateNetwork=yes from the service file works as a workaround. Maybe need to enable CONFIG_NAMESPACES=y and CONFIG_NET_NS=y kernel modules
I removed the PrivateNetwork=yes from the service file, however this didn't seem to work. I did not enable the kernel modules. I am currently running the following kernel: 3.17.6-1-ARCH
Thanks

I'm finding the systemd-hostnamed.service isnt working
$ sudo systemctl --state=failed
[sudo] password for kevdog:
UNIT LOAD ACTIVE SUB DESCRIPTION
● systemd-hostnamed.service loaded failed failed Hostname Service
LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
1 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
$ sudo systemctl status systemd-hostnamed.service
● systemd-hostnamed.service - Hostname Service
Loaded: loaded (/usr/lib/systemd/system/systemd-hostnamed.service; static)
Active: failed (Result: timeout) since Tue 2014-12-16 23:11:36 CST; 10min ago
Docs: man:systemd-hostnamed.service(8)
man:hostname(5)
man:machine-info(5)
http://www.freedesktop.org/wiki/Software/systemd/hostnamed
Main PID: 4584
Dec 16 23:08:35 orphan systemd[1]: systemd-hostnamed.service start operation timed out. Terminating.
Dec 16 23:10:06 orphan systemd[1]: systemd-hostnamed.service stop-final-sigterm timed out. Killing.
Dec 16 23:11:36 orphan systemd[1]: systemd-hostnamed.service still around after final SIGKILL. Entering failed mode.
Dec 16 23:11:36 orphan systemd[1]: Failed to start Hostname Service.
Dec 16 23:11:36 orphan systemd[1]: Unit systemd-hostnamed.service entered failed state.
Dec 16 23:11:36 orphan systemd[1]: systemd-hostnamed.service failed.
I found this addressed in this topic:
https://github.com/ev3dev/ev3dev/issues/189
Within this page they state:
Confirmed that removing PrivateNetwork=yes from the service file works as a workaround. Maybe need to enable CONFIG_NAMESPACES=y and CONFIG_NET_NS=y kernel modules
I removed the PrivateNetwork=yes from the service file, however this didn't seem to work. I did not enable the kernel modules. I am currently running the following kernel: 3.17.6-1-ARCH
Thanks

Why does adobe premier elements render my video everytime i change something in it even when i have lots more of the video to edit? other editing software only seems to render at the start then lets you edit until your ready to save at the end. Constant

why does adobe premier elements render my video everytime i change something in it even when i have lots more of the video to edit? other editing software only seems to render at the start then lets you edit until your ready to save at the end. Constant rendering means its almost impossible to edit anything. Please help.

H TheGamer
What version of Premiere Elements and on what computer operating system is it running? It will not influence my answer but will give me information in case I need to get into version specifics to detail my answer further.
Timeline rendering is a preview matter. It does not fix anything, but it is your window of opportunity to catch of problem sooner than latter. If the Timeline rendering indicator displays orange (11 or higher) for the line above the Timeline content, that is the project telling you that you are not getting the best possible preview of the playback of that content in the Edit area monitor. And, every time you edit a file, you have altered the file from the time before. So, if you want to see the best possible for what you now have, you Timeline render. This is particularly helpful when you are dealing with titles, effects, transitions, and non native formats. You cannot turn off the Timeline render indicator system, at least none that I have ever found nor seen reported. You can do selective Timeline rendering by having the gray tabs of the Work Area Bar span only the Timeline segment that you want Timeline rendered.
Consequently, you either ignore the Timeline render indicator system, move on in the project, and take your chances in the outcome or you Timeline render to get your best possible preview if the Timeline render indicator is suggesting that you do so.
I am not approving or disapproving of this project feature, just commenting on the what is.
This is not Adobe. Rather user to user. If you want to have your voice heard at Adobe, you might consider filing an Adobe Feature Request Bug Report Form.
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform
Please consider.
ATR
Add On...it is also possible to do Timeline rendering in a project, save close the project, and reopen it to find your previously "green" lined content now "orange", indicating unrendered. Yet the preview files generated originally by Timeline rendering are still existing in their hard drive save location. That is another story for other time.

Code to wait until one event is finished before starting another?

Hi all,
Coding isn't my strong point but I have a basic understanding of how functions etc work.
I've been learning about referencing symbol timelines with the awesome tutorial from the Adobe Blog, included below.
http://blogs.adobe.com/edge/2012/07/18/tutorial-leveraging-independent-symbol-timelines/
I've been able to get my symbol to play from a certain part of it's timeline depending on whether the mouse is rolling in or out but now I'm a little bit stuck.
The mouseover event triggers an animation and the mouseout triggers another animation that starts from the same frame that the mouseover animation ends with.
The problem is this. If I move the mouse quickly over the buttons, the first animation will play halfway through and when the mouseout triggers the second animation, the first animation will seemingly "skip" to the ending and move straight to the first frame of the second animation.
I know enough to code it so that the second animation will check if the first animation is still playing before starting by using an else/if statement. Using this method I only know how to skip the second animation if the first is playing but that isn't really what I'm looking to do.
Here comes the question; can anyone explain to me how to create a wait loop in Edge Animate?
When I say wait loop, I am talking about code that will check a variable and perform an action if the variable is true OR loop back to the start of the function if the variable is false (to check the variable again).
The behavior I am trying to achieve is somewhat like queuing the second animation so that it will "wait" until the first animation is played before beginning the second animation.
Any ideas?

Ok Mr Doon,
Clearly, I read to quickly
The behavior I am trying to achieve is somewhat like queuing the second animation so that it will "wait" until the first animation is played before beginning the second animation.
So, say the anima symbol is a 2s animation and has autoPlay set to false. There are two instances anima-1 and anima-2 on stage.
The event handler anima-1.mouseover starts the first animation :
We select Stage in the code panel and place before the first Symbol.bind… the declaration for two symbol (stage) variables :
Inside the anima timeline, click the top left bullet+curly brackets icon and select complete : when the animation is complete, we set the boolean variable (what is not very clean here is that this is done for the two instances anima-1 and anima-2) :
The event handler anima-2.mouseover starts the wait loop, by calling a function defined at the stage level :
More precisely, the function is defined in the document.compositionready handler. It defines (and stores in variable waitLoop in order to be able to remove when finished) an interval, that is the repeated call, every 10 ms, of an inner anonymous function.
The latter simply tests the boolean and when its true
- starts the second animation ;
- clears the interval.
You can download the example here : https://www.box.com/s/6yxjfmrqd0b5zbhmd3lx
You can hover over the left rounded rectangle, and immediately after over the second one. Subsequent rollovers are not handled, but it gives you a possible logic to adapt to your particuliar problem (that I still do not understand completely : it's hard without seeing).
Gil

When i try to close my iPhoto app on my air it continuously says wait until import is finished and it won't let me exit the app, what can i do to close it?

when i try to close my iPhoto app on my air it continuously says wait until import is finished and it won't let me exit the app and i cant even turn off my laptop, what can i do to close it?

Welcome to Apple Support Communities
Press Alt, Command and Esc keys or go to  > Force Quit, choose iPhoto and force close it.

[Solved] systemd does not wait for the unit to finish

My problem is described in the title. I have made a test by enabling the following unit:
[Unit]
Description=/etc/rc.local Compatibility
[Service]
Type=forking
ExecStart=/bin/sleep 1000
TimeoutSec=0
RemainAfterExit=yes
After=network.target
[Install]
WantedBy=multi-user.target
The unit is well started (a process sleep 1000 exists). But with a type=forking, systemd is supposed to hang in this case. Instead, the graphical.target is launched, systemctl list-units mention it as dead, but the display manager is started before the sleep 1000 completes. Ho can I force systemd to wait?
Last edited by olive (2015-03-16 16:49:34)

olive, now you're making even less sense. I didn't say the sleep example was stupid and I didn't question your reasons for doing/wanting this.
I suggested you add "Before=display-manager.service" and you respond "I added Before=graphical.target and it didn't change anything."
I also tried to explain why systemd has no reason to delay the display-manager.service. You could have asked for further clarification, as berbae has now done. Let's try a longer explanation.
Service startup
Services can be started in different ways, as configured with Type=. This determines when a service is considered "started" (or when the service's start-up is considered finished). When a service reaches this state (some time after being started), units that are supposed to start After= this service will be started (and no sooner).
With simple systemd has no further information about the start-up process. It launches whatever you specify in ExecStart and this is the main process that continues to run till the service stops. systemd assumes this type of service is started immediately. All the other types have some way for the process to indicate to systemd (either directly or indirectly) when it has finished starting.
Actually oneshot is also a bit special and that is where RemainAfterExit comes in. For oneshot, systemd waits for the process to exit before it starts any follow-up units (and with multiple ExecStarts I assume it waits for all of them). So that automatically leads to the scheme in berbae's last post. However, with RemainAfterExit, the unit remains active even though the process has exited, so this makes it look more like "normal" service with
begin of unit/startup ---- end of startup ------ end of unit
This is the relevant behavior for this thread. First sleep starts, then after 1000 seconds, start-up finishes and follow-up units will be started. Then either the unit dies, or (with RemainAfterExit) it stays "active".
The man page describes how "end of startup" is determined for each Type.
Targets
Targets are meant to group units together, to provide synchronization points (and replace runlevels). When you start a target, all its units will be started (in parallel if possible). The man page says:
Unless DefaultDependencies= is set to false, target units will
implicitly complement all configured dependencies of type Wants=,
Requires=, RequiresOverridable= with dependencies of type After= if the
units in question also have DefaultDependencies=true.
This means that (by default) when a target is requested, all it units are started first. Only after all units have finished starting, the target itself will be started (and since the target doesn't do anything by itself, this startup is basically instantaneous). Without this dependency, the order between the target and its units is unspecified, so in theory the target could finish starting immediately while its units are still being started.
Back to olive
graphical.target has these DefaultDependencies, so it is not started until all its units (like display-manager.service) and other After= dependencies (like multi-user.target) have finished starting. Your sleep service has to be started before multi-user.target starts (again due to default target dependencies). So first display-manager and the sleep service are started and after 1000 seconds, the sleep service finishes starting and then (assuming all other dependencies were quicker) multi-user.target is started and graphical.target as well (assuming display-manager didn't need 1000 seconds).
If you want display-manager.service after the sleep service, add a Before/After line to specify that (this was your original goal and my suggestion).
olive wrote wrote:However, units that are parts of the graphical target are still launched before the graphical target become active. I am still unable to completely delay the starts of the graphical target before a specific unit completes.
It should be clear now how this works. "units that are part of the graphical target" can only mean "units that are wanted/required by the graphical target" but that is basically all the units that are started when you boot your system, because multi-user.target is a part of graphical.target. And your sleep service is a part of multi-user.target, so in fact you're saying you want to delay starting the sleep service until the sleep service completes
What you probably intended was to delay all units that are a part of graphical.target but not of multi-user.target until after the sleep service. I can't think of an easy (or even good) way to do this and this post is already too long, so I'll table that for now.

[systemd] Let services wait until X is started [solved]

Similar Messages

Maybe you are looking for