[SOLVED] "systemctl poweroff" permissions error

Snark1994 · 2012-11-12 23:57:17

Hiya,

Previously I could run

systemctl poweroff

and it would shut down the system without prompting for root password as long as no-one else was logged in. Now I get:

[joshua:~ o]$ systemctl poweroff
Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)
Failed to issue method call: Connection was disconnected before a reply was received
Failed to add match: Connection is closed
Could not watch jobs: Input/output error
[joshua:~ x]$

journalctl tells me:

Nov 12 23:54:10 joshua-desktop dbus-daemon[7322]: dbus[7322]: [system] Activating systemd to hand-off: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Nov 12 23:54:10 joshua-desktop dbus[7322]: [system] Activating systemd to hand-off: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Nov 12 23:54:27 joshua-desktop systemd[1]: systemd-logind.service operation timed out. Terminating.
Nov 12 23:54:27 joshua-desktop systemd[1]: Failed to start Login Service.
Nov 12 23:54:27 joshua-desktop systemd[1]: Unit systemd-logind.service entered failed state
Nov 12 23:54:27 joshua-desktop systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
Nov 12 23:54:27 joshua-desktop systemd[1]: Stopping Login Service...
Nov 12 23:54:27 joshua-desktop systemd[1]: Starting Login Service...
Nov 12 23:54:27 joshua-desktop systemd-logind[7569]: New seat seat0.
Nov 12 23:54:27 joshua-desktop systemd-logind[7569]: Watching system buttons on /dev/input/event4 (Power Button)
Nov 12 23:54:27 joshua-desktop systemd-logind[7569]: Watching system buttons on /dev/input/event3 (Power Button)
Nov 12 23:54:27 joshua-desktop systemd-logind[7569]: New session 1 of user joshua.
Nov 12 23:54:27 joshua-desktop systemd-logind[7569]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display.
Nov 12 23:54:35 joshua-desktop dbus-daemon[7322]: dbus[7322]: [system] Failed to activate service 'org.freedesktop.PolicyKit1': timed out
Nov 12 23:54:35 joshua-desktop dbus-daemon[7322]: dbus[7322]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Nov 12 23:54:35 joshua-desktop dbus[7322]: [system] Failed to activate service 'org.freedesktop.PolicyKit1': timed out
Nov 12 23:54:35 joshua-desktop dbus[7322]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Nov 12 23:54:37 joshua-desktop sudo[7587]: joshua : TTY=pts/0 ; PWD=/etc/systemd ; USER=root ; COMMAND=/usr/bin/journalctl
Nov 12 23:54:37 joshua-desktop sudo[7587]: pam_unix(sudo:session): session opened for user root by (uid=0)

so it looks like it's some problem with systemd-logind.service:

[joshua:/etc/systemd x]$ sudo systemctl status systemd-logind.service
systemd-logind.service - Login Service
	  Loaded: loaded (/usr/lib/systemd/system/systemd-logind.service; static)
	  Active: activating (start) since Mon, 2012-11-12 23:54:27 GMT; 1min 28s ago
	    Docs: man:systemd-logind.service(8)
	          man:logind.conf(5)
	          [url]http://www.freedesktop.org/wiki/Software/systemd/multiseat[/url]
	Main PID: 7569 (systemd-logind)
	  CGroup: name=systemd:/system/systemd-logind.service
		  └ 7569 /usr/lib/systemd/systemd-logind

Nov 12 23:54:27 joshua-desktop systemd[1]: Unit systemd-logind.service entered failed state
Nov 12 23:54:27 joshua-desktop systemd[1]: Stopping Login Service...
Nov 12 23:54:27 joshua-desktop systemd[1]: Starting Login Service...
Nov 12 23:54:27 joshua-desktop systemd-logind[7569]: New seat seat0.
Nov 12 23:54:27 joshua-desktop systemd-logind[7569]: Watching system buttons on /dev/input/event4 (Power Button)
Nov 12 23:54:27 joshua-desktop systemd-logind[7569]: Watching system buttons on /dev/input/event3 (Power Button)
Nov 12 23:54:27 joshua-desktop systemd-logind[7569]: New session 1 of user joshua.
Nov 12 23:54:27 joshua-desktop systemd-logind[7569]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display.

And /etc/systemd/logind.conf says:

#  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

Anyone got any ideas? Thanks in advance!

Last edited by Snark1994 (2012-11-18 22:41:06)

teateawhy · 2012-11-13 16:13:04

Check if your session is registered as active with loginctl show-session an if there are multiple sessions.

Snark1994 · 2012-11-13 16:31:52

Yes and no respectively:

[joshua:~ x]$ loginctl list-sessions
   SESSION        UID USER             SEAT            
         1       1000 joshua           seat0           

1 sessions listed.

[joshua:~ o]$ loginctl show-session 1
Id=1
Timestamp=Tue, 2012-11-13 16:29:21 GMT
TimestampMonotonic=25663662522
DefaultControlGroup=name=systemd:/user/joshua/1
VTNr=7
Display=:0.0
Remote=no
RemoteUser=root
Service=slim
Leader=274
Audit=1
Type=x11
Class=user
Active=yes
State=active
KillProcesses=no
IdleHint=no
IdleSinceHint=0
IdleSinceHintMonotonic=0
Name=joshua

Any more ideas?

Last edited by Snark1994 (2012-11-13 16:32:16)

bgc1954 · 2012-11-13 17:25:20

I've seen recently that slim seems to be having issues with logind and systemd. If you logout and log back in and loginctl list-sessions you'll likely see two sessions listed. Slim seems to be having problems dealing with sessions properly. My only suggestion would be to try xdm instead as it doesn't appear to have these issues. It's still lightweight and doesn't have the recurring problems slim seems to have. My only suggestion. Sorry.

Snark1994 · 2012-11-13 17:38:46

Ah, okay. No problems then, I'll just change to xdm.

I can confirm the two session symptom. Do we know if this is a slim bug, or an Arch bug? And if the former, has someone reported it?

Thanks!

bgc1954 · 2012-11-13 17:48:58

There are a couple of bugs filed against slim concerning systemd. FS#32380 is relevant in that if slim doesn't finish exiting processes, the sessions don't get closed so it looks like it's already being handled.

BTW, straight xorg-xdm is butt ugly. xdm-archinux in community is a big improvement. It also adds reboot and poweroff buttons.

Last edited by bgc1954 (2012-11-13 17:50:08)

Snark1994 · 2012-11-14 00:26:58

Okay, actually that doesn't fix the problem... Even with XDM I get the same "Error getting authority: blah blah" error that I quoted in my first post. "list-sessions"/"show-session" show 1 user and Active=yes respectively...

Any more ideas?

bgc1954 · 2012-11-16 16:48:22

Maybe a shot in the dark but you do have systemd-sysvcompat installed? And there's nothing still trying to use consolekit in your .xinitrc? How about systemctl status polkit.service?

Snark1994 · 2012-11-16 17:23:57

Yes, I've got systemd-sysvcompat installed.

And there's nothing still trying to use consolekit in your .xinitrc?

How would I work that out? Or is it just a case of looking at the docs for each programme?

And:

[joshua:~ x]$ sudo systemctl status polkit.service
polkit.service - Authorization Manager
	  Loaded: loaded (/usr/lib/systemd/system/polkit.service; static)
	  Active: inactive (dead)
	    Docs: man:polkit(8)
	  CGroup: name=systemd:/system/polkit.service

Am I correct in thinking that "inactive (dead)" is a bad sign?

[joshua:~ o]$ sudo journalctl _SYSTEMD_UNIT=polkit.service
-- Logs begin at Sun, 2012-10-21 10:35:29 BST, end at Mon, 2012-11-12 22:50:38 GMT. --
[joshua:~ o]$

Last edited by Snark1994 (2012-11-16 17:24:27)

bgc1954 · 2012-11-16 18:00:31

AS far as your .xinitrc, I just meant that have you got a simple "exec windowmanager" containing no dbus-launch or ck-session-launch entries. Several suggestions to launch dbus, etc. is to copy /etc/skel/.xinitrc to ~/.xinitrc and modify to launch your wm.

Yes, having a dead polkit.service will cause you just the problems you're describing. There are a few threads on this in the forum but I can't think of one off the top of my head so maybe a forum search on polkit.service will find you what you're looking for.

Snark1994 · 2012-11-16 23:43:45

I couldn't find any threads with solutions, either on google or using forum search... However, if I try to run polkitd manually I get:

[joshua:~ o]$ sudo /usr/lib/polkit-1/polkitd
Successfully changed to user polkitd
Error getting system bus: Could not connect: No such file or directory
** (polkitd:6417): WARNING **: Error getting system bus: Could not connect: No such file or directory
23:42:03.803: Loading rules from directory /etc/polkit-1/rules.d
23:42:03.803: Loading rules from directory /usr/share/polkit-1/rules.d
23:42:03.803: Finished loading, compiling and executing 1 rules
Entering main event loop
23:42:03.804: Lost the name org.freedesktop.PolicyKit1 - exiting
Shutting down
Exiting with code 0

...so it sounds like polkitd has problems independent of systemd. http://lists.freedesktop.org/archives/p … 00367.html references the same problem, but the file /opt/var/run/dbus/system_bus_socket doesn't exist for me...

cfr · 2012-11-17 01:44:42

Does /var/run/dbus/system_bus_socket?

Snark1994 · 2012-11-17 09:44:28

Nope, don't even have a /var/run/dbus directory.

I have /usr/lib/systemd/system/dbus.socket but according to "locate", no files named "system-bus-socket" in the filesystem ( also ran "find /var -iname 'system-bus-socket'" just in case, but no luck there either).

I found http://lists.freedesktop.org/archives/d … 09206.html: I don't have messagebus user/group, but I do have dbus user/group. Is this the source of my problem, do you think?

[EDIT]Nope, I added a messagebus user and group and the problem persists...[/EDIT]

Last edited by Snark1994 (2012-11-17 15:53:25)

Snark1994 · 2012-11-17 16:04:23

Hm, I'm getting closer - I've found system-bus-socket, it was in /run/dbus. I didn't even know I had a top-level /run directory... However, running:

DBUS_SYSTEM_BUS_ADDRESS=unix:path=/run/dbus/system_bus_socket

doesn't help at all.

Also, I note that in /etc/dbus-1/system.conf has

<listen>unix:path=/run/dbus/system_bus_socket</listen>

in it.

Any ideas?

bgc1954 · 2012-11-17 18:23:27

Have you tried

# systemctl list-units

to check the status of dbus. Did you try and copy /etc/skel/.xinitrc to your home directory like I suggested before? It looks like dbus isn't running or responding properly for some reason. I think I read somewhere that someone was still using dbus-launch in his .xinitrc and it worked for him.

As far as groups are concerned the systemd wiki claims you don't need to be in groups in most cases.

Snark1994 · 2012-11-17 19:27:30

[joshua:~ o]$ sudo systemctl list-units --no-pager | grep dbus 
zsh: correct 'dbus' to '.dbus' [nyae]? n 
dbus.service                                                                                     loaded active     running         D-Bus System Message Bus 
dbus.socket                                                                                      loaded active     running         D-Bus System Message Bus Socket 
[joshua:~ o]$ diff -u {/etc/skel/,}.xinitrc 
--- /etc/skel/.xinitrc  2011-03-10 19:03:55.000000000 +0000 
+++ .xinitrc    2012-09-29 15:28:27.425170931 +0100 
@@ -11,7 +11,23 @@ 
   unset f 
 fi 
  
-# exec gnome-session 
-# exec startkde 
-# exec startxfce4 
-# ...or the Window Manager of your choice 
+trayer --edge top --align left --SetDockType true --SetPartialStrut true --expand true --widthtype pixel --width 101 --transparent true --tint 0x002b36 --height 12 --margin 922 & 
+xautolock -time 30 -locker "sudo pm-suspend" & #suspends to RAM after 30 mins of inactivity 
+ 
+setxkbmap -option compose:ralt 
+setxkbmap -option terminate:ctrl_alt_bksp 
+xmodmap -e "keysym Num_Lock = Num_Lock Pointer_EnableKeys" 
+xhost local:boinc # allows boinc to use GPU for calculations 
+xsetroot -solid "#002b36" 
+xrdb -merge ~/.Xresources 
+ 
+xscreensaver -no-splash & 
+conky & 
+dropbox start & 
+ 
+(logtime "START anki"; anki) & 
+urxvt -e sh -c "sudo pacman -Syu; echo -e \"\nFinished.\"; read; weather; read; tdl list; read; sudo backup daily; read" & 
+ 
+#(sleep 120; transmission-gtk) & 
+ 
+exec xmonad 
[joshua:~ x]$

I haven't,, but as you can see I have nothing the /etc/skel/.xinitrc doesn't have...

I also tried swapping the last line for

dbus-launch --exit-with-session xmonad

but to no avail (exactly the same symptoms when trying to start polkitd manually, or trying to systemctl poweroff without root priveliges).

bgc1954 · 2012-11-17 21:33:59

A while ago I seem to remember having issues with polkit and someone suggested reinstalling on another post. When I tried, I found that polkit didn't install properly as there was a goup id number conflict. It turned out I had an old install of gdm and it ws using the same group id that polkit was trying to use during install. After I got rid of gdm and did a reinstall of polkit, it worked properly. Just a shot in the dark really. See https://bbs.archlinux.org/viewtopic.php?pid=1187801

Last edited by bgc1954 (2012-11-18 16:02:58)

cfr · 2012-11-18 00:50:31

You said that you have /run/dbus but not /var/run/dbus?

There's your problem. (Well, one of them, anyway.)

/var/run should be a symlink to /run.

If that is not the case on your machine, either your system is rather out of date or something has gone rather wrong somewhere.

Snark1994 · 2012-11-18 17:28:25

Aha! cfr has it. Perhaps I messed up https://www.archlinux.org/news/filesyst … equired-1/. (or it became messed up when I removed initscripts? Dunno.)

I've rectified the situation, and polkitd starts correctly. I'll reboot now and see if the problem's fixed...

Last edited by Snark1994 (2012-11-18 22:40:35)

Snark1994 · 2012-11-18 22:40:40

Yes, that fixed the problem. Thank you very much everyone for your help, and especially cfr for the solution. Diolch yn fawr!

cfr · 2012-11-19 00:17:49

Croeso!

PolePosition · 2012-12-31 23:49:56

Hello,

I have the same problem.

[root@zoulou run]# pwd
/var/run
[root@zoulou run]# ls
[root@zoulou run]# cd /run/dbus/
[root@zoulou dbus]# ls
system_bus_socket
[root@zoulou dbus]# ls -lha
total 0
drwxr-xr-x 2 root root 60 Jan 1 00:04 .
drwxr-xr-x 17 root root 400 Jan 1 00:04 ..
srw-rw-rw- 1 root root 0 Jan 1 00:04 system_bus_socket
[root@zoulou dbus]# file system_bus_socket
system_bus_socket: socket
[root@zoulou dbus]#

But I have installed Arch let's say... two months ago so I have a complete-full systemd "compliant OS.
It was working fine until this evening, I was just googling and reading newspaper and sudenly Conky display a log of messages from /var/log/messages.log !

My Arch is up to date.
I have tried to restart a couple of time but nothing change.

Do you have an idea ?

Dec 31 21:10:20 zoulou dbus-daemon[945]: dbus[945]: [system] Activating systemd to hand-off: service name='org.freedesktop.UPower' unit='upower.service'
Dec 31 21:10:20 zoulou dbus[945]: [system] Activating systemd to hand-off: service name='org.freedesktop.UPower' unit='upower.service'
Dec 31 21:10:45 zoulou dbus-daemon[945]: dbus[945]: [system] Failed to activate service 'org.freedesktop.UPower': timed out
Dec 31 21:10:45 zoulou dbus[945]: [system] Failed to activate service 'org.freedesktop.UPower': timed out
Dec 31 21:10:45 zoulou dbus[945]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Dec 31 21:10:45 zoulou dbus-daemon[945]: dbus[945]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Dec 31 21:10:45 zoulou dbus-daemon[945]: process 945: arguments to dbus_message_set_reply_serial() were incorrect, assertion "reply_serial != 0" failed in file dbus-message.c line 1070.
Dec 31 21:10:45 zoulou dbus-daemon[945]: This is normally a bug in some application using the D-Bus library.
Dec 31 21:10:45 zoulou dbus-daemon[945]: D-Bus not built with -rdynamic so unable to print a backtrace
Dec 31 21:10:45 zoulou systemd[1]: dbus.service: main process exited, code=killed, status=6/ABRT
Dec 31 21:10:45 zoulou systemd[1]: Unit dbus.service entered failed state
Dec 31 21:10:45 zoulou systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
Dec 31 21:10:45 zoulou systemd[1]: Unit systemd-logind.service entered failed state
Dec 31 21:10:45 zoulou systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
Dec 31 21:10:45 zoulou systemd[1]: Stopping Login Service...
Dec 31 21:10:45 zoulou systemd[1]: Starting Login Service...
Dec 31 21:10:45 zoulou systemd[1]: Starting D-Bus System Message Bus...
Dec 31 21:10:45 zoulou systemd[1]: Started D-Bus System Message Bus.
Dec 31 21:10:45 zoulou systemd[1]: Failed to open private bus connection: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
Dec 31 21:10:47 zoulou dbus-daemon[954]: dbus[954]: [system] Activating systemd to hand-off: service name='org.freedesktop.UPower' unit='upower.service'
Dec 31 21:10:47 zoulou dbus[954]: [system] Activating systemd to hand-off: service name='org.freedesktop.UPower' unit='upower.service'
Dec 31 21:11:12 zoulou dbus-daemon[954]: dbus[954]: [system] Failed to activate service 'org.freedesktop.UPower': timed out
Dec 31 21:11:12 zoulou dbus[954]: [system] Failed to activate service 'org.freedesktop.UPower': timed out
Dec 31 21:11:12 zoulou dbus[954]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Dec 31 21:11:12 zoulou dbus-daemon[954]: dbus[954]: [system] Failed to activate service 'org.freedesktop.systemd1': timed out
Dec 31 21:11:12 zoulou dbus-daemon[954]: process 954: arguments to dbus_message_set_reply_serial() were incorrect, assertion "reply_serial != 0" failed in file dbus-message.c line 1070.
Dec 31 21:11:12 zoulou dbus-daemon[954]: This is normally a bug in some application using the D-Bus library.
Dec 31 21:11:12 zoulou dbus-daemon[954]: D-Bus not built with -rdynamic so unable to print a backtrace
Dec 31 21:11:12 zoulou systemd[1]: dbus.service: main process exited, code=killed, status=6/ABRT
Dec 31 21:11:12 zoulou systemd[1]: Unit dbus.service entered failed state
Dec 31 21:11:12 zoulou systemd[1]: systemd-logind.service: main process exited, code=exited, status=1/FAILURE
Dec 31 21:11:12 zoulou systemd[1]: Unit systemd-logind.service entered failed state
Dec 31 21:11:12 zoulou systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
[root@zoulou dbus]#

PolePosition · 2012-12-31 23:56:13

Hi again,

Everything is okay now.
Why on Earth this problem sudendly occured ?

I have done :

[root@zoulou bastien]# pacman-color -S filesystem
warning: filesystem-2012.12-1 is up to date -- reinstalling

Now I have :

[root@zoulou run]# cd /var/run
[root@zoulou run]# ls
console dbus initramfs lirc lock log lvm mdadm mount network nscd pm-utils syslog-ng.ctl syslog-ng.pid systemd udev user utmp uuidd
[root@zoulou run]#

And the log file :

Jan 1 00:51:38 zoulou systemd[1]: Unit systemd-logind.service entered failed state
Jan 1 00:51:38 zoulou systemd[1]: systemd-logind.service holdoff time over, scheduling restart.
Jan 1 00:51:38 zoulou systemd[1]: Stopping Login Service...
Jan 1 00:51:38 zoulou systemd[1]: Starting Login Service...
Jan 1 00:51:38 zoulou systemd[1]: Starting D-Bus System Message Bus...
Jan 1 00:51:38 zoulou systemd[1]: Started D-Bus System Message Bus.
Jan 1 00:51:38 zoulou systemd[1]: Started Login Service.
Jan 1 00:51:40 zoulou dbus-daemon[2930]: dbus[2930]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
Jan 1 00:51:40 zoulou dbus[2930]: [system] Activating via systemd: service name='org.freedesktop.UPower' unit='upower.service'
Jan 1 00:51:40 zoulou systemd[1]: Starting Daemon for power management...
Jan 1 00:51:40 zoulou dbus-daemon[2930]: dbus[2930]: [system] Successfully activated service 'org.freedesktop.UPower'
Jan 1 00:51:40 zoulou dbus[2930]: [system] Successfully activated service 'org.freedesktop.UPower'
Jan 1 00:51:40 zoulou systemd[1]: Started Daemon for power management.
Jan 1 00:51:40 zoulou dbus-daemon[2930]: dbus[2930]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Jan 1 00:51:40 zoulou dbus[2930]: [system] Activating via systemd: service name='org.freedesktop.PolicyKit1' unit='polkit.service'
Jan 1 00:51:40 zoulou systemd[1]: Starting Authorization Manager...
Jan 1 00:51:40 zoulou polkitd[2938]: Started polkitd version 0.107
Jan 1 00:51:40 zoulou dbus-daemon[2930]: dbus[2930]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Jan 1 00:51:40 zoulou dbus[2930]: [system] Successfully activated service 'org.freedesktop.PolicyKit1'
Jan 1 00:51:40 zoulou systemd[1]: Started Authorization Manager.
Jan 1 00:51:40 zoulou kernel: [ 2815.729436] EXT4-fs (dm-0): re-mounted. Opts: discard,commit=0
Jan 1 00:51:40 zoulou kernel: [ 2815.732372] EXT4-fs (sda1): re-mounted. Opts: discard,commit=0
Jan 1 00:51:40 zoulou kernel: [ 2815.733673] EXT4-fs (dm-1): re-mounted. Opts: discard,commit=0
Jan 1 00:51:40 zoulou kernel: [ 2815.735586] EXT4-fs (dm-3): re-mounted. Opts: stripe=256,data=ordered,commit=0

Snark1994 · 2013-01-01 10:12:31

From these lines in your first post:

[root@zoulou run]# pwd
/var/run
[root@zoulou run]# ls
[root@zoulou run]# cd /run/dbus/
[root@zoulou dbus]#

It sounds like you had the same problem as I did: /var/run wasn't symlinked to /run. Run

ls -ld /var/run /run

to check and you should get something like

drwxr-xr-x 21 root root 520 Jan  1 10:05 /run
lrwxrwxrwx  1 root root   6 Dec  4 01:02 /var/run -> ../run

Regards,

Last edited by Snark1994 (2013-01-01 10:12:58)

PolePosition · 2013-01-01 12:58:43

Hello,

Happy new year, by the way !

Nope exactly the same :

[root@zoulou dbus]# ls -ld /var/run/ /run/
drwxr-xr-x 19 root root 440 Jan 1 09:57 /run/
drwxr-xr-x 19 root root 440 Jan 1 09:57 /var/run/
[root@zoulou dbus]# pacman-color -S filesystem
warning: filesystem-2012.12-1 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
.
.
.
[root@zoulou dbus]# ls -ld /var/run/ /run/
drwxr-xr-x 19 root root 440 Jan 1 09:57 /run/
drwxr-xr-x 19 root root 440 Jan 1 09:57 /var/run/
[root@zoulou dbus]#

Strange. I can create the simlink by myself, but :

- first, I do not get any error so should I change something if everything is right ?
- second, I would like to understand why the problem occured...

Regards and happy new year again,
Bastien

Arch Linux

#1 2012-11-12 23:57:17

[SOLVED] "systemctl poweroff" permissions error

#2 2012-11-13 16:13:04

Re: [SOLVED] "systemctl poweroff" permissions error

#3 2012-11-13 16:31:52

Re: [SOLVED] "systemctl poweroff" permissions error

#4 2012-11-13 17:25:20

Re: [SOLVED] "systemctl poweroff" permissions error

#5 2012-11-13 17:38:46

Re: [SOLVED] "systemctl poweroff" permissions error

#6 2012-11-13 17:48:58

Re: [SOLVED] "systemctl poweroff" permissions error

#7 2012-11-14 00:26:58

Re: [SOLVED] "systemctl poweroff" permissions error

#8 2012-11-16 16:48:22

Re: [SOLVED] "systemctl poweroff" permissions error

#9 2012-11-16 17:23:57

Re: [SOLVED] "systemctl poweroff" permissions error

#10 2012-11-16 18:00:31

Re: [SOLVED] "systemctl poweroff" permissions error

#11 2012-11-16 23:43:45

Re: [SOLVED] "systemctl poweroff" permissions error

#12 2012-11-17 01:44:42

Re: [SOLVED] "systemctl poweroff" permissions error

#13 2012-11-17 09:44:28

Re: [SOLVED] "systemctl poweroff" permissions error

#14 2012-11-17 16:04:23

Re: [SOLVED] "systemctl poweroff" permissions error

#15 2012-11-17 18:23:27

Re: [SOLVED] "systemctl poweroff" permissions error

#16 2012-11-17 19:27:30

Re: [SOLVED] "systemctl poweroff" permissions error

#17 2012-11-17 21:33:59

Re: [SOLVED] "systemctl poweroff" permissions error

#18 2012-11-18 00:50:31

Re: [SOLVED] "systemctl poweroff" permissions error

#19 2012-11-18 17:28:25

Re: [SOLVED] "systemctl poweroff" permissions error

#20 2012-11-18 22:40:40

Re: [SOLVED] "systemctl poweroff" permissions error

#21 2012-11-19 00:17:49

Re: [SOLVED] "systemctl poweroff" permissions error

#22 2012-12-31 23:49:56

Re: [SOLVED] "systemctl poweroff" permissions error

#23 2012-12-31 23:56:13

Re: [SOLVED] "systemctl poweroff" permissions error

#24 2013-01-01 10:12:31

Re: [SOLVED] "systemctl poweroff" permissions error

#25 2013-01-01 12:58:43

Re: [SOLVED] "systemctl poweroff" permissions error

Board footer