please use code tags.you may want to use this service file instead:[Unit]
Description=i3lock
Before=sleep.target
[Service]
User=<user>
Type=forking
Environment=DISPLAY=:0
ExecStart=/usr/bin/i3lock -c 000000
[Install]
WantedBy=sleep.targetsystemctl enable i3lock.service
65kid
https://bbs.archlinux.org/profile.php?id=45818
2012-10-04T13:58:35Z
These are not really "errors", systemd just complains because these units are referenced by other units (by After/Before, as you said), but don't actually exist. This is nothing to worry about, which is also why you don't even see those unless you pass "--all" to systemctl. The runlevel targets are probably just leftovers from the sysvinit compatibility.
Before I ran that command I ran ls -l /etc/systemd/system/display-manager.service and got the outputlrwxrwxrwx 1 root root 35 Oct 14 02:20 /etc/systemd/system/display-manager.service -> /usr/lib/systemd/system/kdm.serviceSo it looks like the symlink was already created when I ran systemctl enableI tried to create it again anyway though and it just returned "ln: failed to create symbolic li
yes, they are automatically started on boot/shutdown.
65kid
https://bbs.archlinux.org/profile.php?id=45818
2012-11-16T12:18:51Z
that's weird, never seen this. Remove the "quiet" parameter from your kernel command line so you can see where it actually hangs.Only other thing I can think of is to disable one service after the other one by one to see which one causes this.
65kid
https://bbs.archlinux.org/profile.php?id=45818
2013-05-05T10:18:31Z
systemctl status gdm.service output:gdm.service - Gnome Display Manager
Loaded: loaded (/usr/lib/systemd/system/gdm.service; disabled)
Active: inactive (dead)
CGroup: name=systemd:/system/gdm.service
gabe.benson
https://bbs.archlinux.org/profile.php?id=51378
2012-10-03T20:57:24Z
the mysql service file and mysql-post script from the Systemd/Services wiki page have been moved to the package and you created them manually before, that's why you get this error.
You may have to set another profile for your card. in pavucontrol this is under "configuration", I'm sure the gnome settings have it somewhere as well.
65kid
https://bbs.archlinux.org/profile.php?id=45818
2012-12-15T17:57:42Z
are you sure that it is actually fsck taking so long and not something else in the background?post your fstab and the following:systemd-analyze blame
65kid
https://bbs.archlinux.org/profile.php?id=45818
2013-05-05T15:25:57Z
Email this page
