Are you launching nm-applet from anywhere else (.xinitrc, xfce application autostart, etc.)? That would cause the issue you are having.
nixpunk
https://bbs.archlinux.org/profile.php?id=31325
2012-09-11T17:37:04Z
hi guys,i got it: https://www.archlinux.org/news/consolek … by-logind/my system worked in a initscripts/systemd mix. i already configured the DAEMONS...etc.
Check if the UUID from the fstab is right:$ lsblk -fIf it's not, maybe see: https://wiki.archlinux.org/index.php/Fstab#Swap_UUID
DSpider
https://bbs.archlinux.org/profile.php?id=28388
2012-09-08T07:50:01Z
This is not a issue anymore as I switched to systemd permantly
zann
https://bbs.archlinux.org/profile.php?id=59802
2012-08-31T16:58:32Z
I have already commented out the removable media from my fstab.I know and understand how to mount them, so there is no problem there.My question is, why systemd fails to boot and not timeout when trying to mount them.They arent on the pc at the moment, so systemd should timeout and continue to boot.Can be a bug on systemd or something like that ?
ebal
https://bbs.archlinux.org/profile.php
@steelman - Thx for that suggestion and for taking the time to explain the additional options. Seems to have solved this issue for me:% systemd-analyze blame
8734ms mnt-media.mount
1903ms systemd-vconsole-setup.service
1111ms systemd-remount-fs.service
...% grep nfs /etc/fstab
mars:/media /mnt/media nfs4 rsize=8192,wsize=8192,timeo=14,intr 0 0
graysky
https://bbs.archlinux
I recently moved /var to a new partition and have noticed this error in journalctl logDec 05 07:48:00 archlinux systemd[1]: Started Console System Shutdown Logging.
Dec 05 07:48:00 archlinux systemd[1]: var.mount mount process exited, code=exited status=32
Dec 05 07:48:00 archlinux systemd[1]: Failed unmounting /var.I added an entry in fstab for /var/dev/sda4 /var ext4 defaults,noatime,discard 0
For me it's the same issue, too. (On my machine are two devices left mounted, though.) I've had this problem ever since switching to systemd. Until now I didn't experience bad consequences...
ball
https://bbs.archlinux.org/profile.php?id=55402
2012-11-28T10:55:46Z
Everything that you see during boot up is in systemd's journal, so don't worry about it scrolling too fast. The error messages there should be enough for you to sort it out.FWIW my NFS shares work fine under systemd, and I'm also using netcfg with static ip.
tomk
https://bbs.archlinux.org/profile.php?id=1822
2012-09-04T10:19:04Z