On Sun, 22 May 2011 06:09:58 +0200 Michael Biebl <[email protected]> wrote:
> Can you describe in more detail, what you were doing.
Nothing special that comes to mind. On my system the bug is consistently
reproducible.
> Is systemd running?
It is:
% ps -A | grep systemd
1 ? 00:00:01 systemd
> Did you run systemadm as root/regular user?
Yes, but it's the same error both ways.
> Does systemctl dump work?
As 'root', yes:
# show numbered tail & head of output
% systemctl dump | nl | pee head tail ; echo
1 -> Unit powertweakd.service:
2 Description: LSB: Start powertweak daemon.
3 Instance: n/a
4 Unit Load State: loaded
5 Unit Active State: active
6 Inactive Exit Timestamp: Fri, 20 May 2011 07:24:54 -0400
7 Active Enter Timestamp: Fri, 20 May 2011 07:24:55 -0400
8 Active Exit Timestamp: n/a
9 Inactive Enter Timestamp: n/a
10 GC Check Good: yes
234 References: syslog.target
235 References: local-fs.target
236 References: basic.target
237 References: shutdown.target
238 ReferencedBy: multi-user.target
239 StopWhenUnneeded: no
240 RefuseManualStart: no
241 RefuseManualStop: no
242 DefaultDependencies: yes
243 ControlGroup: cpu:/sy
As a user no:
% systemctl dump ; echo $?
Failed to get D-Bus connection: Failed to connect to socket
/var/run/dbus/system_bus_socket: No such file or directory
1
Attached is the output of:
strace -o /tmp/systemadm.strace systemadm
HTH...
systemadm.strace.gz
Description: Binary data
