Bug 1081786 - After update systemd user sessions stopped working "Failed to issue method call: Process /bin/false exited with status 1"
Summary: After update systemd user sessions stopped working "Failed to issue method ca...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-28 01:02 UTC by Jon Dufresne
Modified: 2015-04-05 16:09 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-04-05 16:09:48 UTC
Type: Bug
Embargoed:
cwawak: needinfo-


Attachments (Terms of Use)

Description Jon Dufresne 2014-03-28 01:02:36 UTC
Description of problem:

After a recent update, my systemd user sessions fails to start units. Any attempt to use "systemctl --user" prints the error:

Failed to issue method call: Process /bin/false exited with status 1

Before the update, my systemd user sessions units were working as expected.

I'd be happy to provide any additional information.

Version-Release number of selected component (if applicable):

$ rpm -qa \*systemd\*
systemd-python3-208-15.fc20.x86_64
systemd-journal-gateway-208-15.fc20.x86_64
systemd-python-208-15.fc20.x86_64
systemd-208-15.fc20.x86_64
systemd-libs-208-15.fc20.x86_64


$ systemctl --user restart emacs.service
Failed to issue method call: Process /bin/false exited with status 1


$ cat ~/.config/systemd/user/emacs.service 
[Unit]
Description=Emacs: the extensible, self-documenting text editor

[Service]
Type=forking
ExecStart=/usr/bin/emacs --daemon
ExecStop=/usr/bin/emacsclient --eval "(kill-emacs)"
Restart=on-failure

[Install]
WantedBy=default.target

Comment 1 Christopher Wawak 2014-08-13 17:38:36 UTC
Running into this on F20 as well.

$ rpm -qa \*systemd\*
systemd-python-208-21.fc20.x86_64
systemd-208-21.fc20.x86_64
systemd-python3-208-21.fc20.x86_64
systemd-libs-208-21.fc20.x86_64

$ systemctl --user list-units 
Failed to issue method call: Process /bin/false exited with status 1

Is there anything additional that I could be doing to troubleshoot this?

Comment 2 Osamu Nagano 2014-08-25 06:40:13 UTC
The same on RHEL 7 too.

$ systemctl --user list-units
Failed to issue method call: Process /bin/false exited with status 1

$ rpm -qa \*systemd\*
systemd-libs-208-11.el7_0.2.x86_64
systemd-sysv-208-11.el7_0.2.x86_64
systemd-python-208-11.el7_0.2.x86_64
systemd-208-11.el7_0.2.x86_64

Comment 3 Denis 2014-09-12 10:47:03 UTC
Same problem on Fedora 20

$ systemctl --user list-units 
Failed to issue method call: Process /bin/false exited with status 1

$ rpm -qa \*systemd\*
systemd-208-21.fc20.x86_64
wine-systemd-1.7.25-1.fc20.noarch
systemd-libs-208-21.fc20.i686
systemd-libs-208-21.fc20.x86_64

Comment 4 Jan Synacek 2014-10-15 09:09:51 UTC
Any chance that setenforce 0 fixes the problem?

Comment 5 Denis 2014-10-15 09:19:14 UTC
(In reply to Jan Synacek from comment #4)
> Any chance that setenforce 0 fixes the problem?

It's not working

$ sudo setenforce 0
$ systemctl --user list-units 
Failed to issue method call: Process /bin/false exited with status 1

Comment 6 Jon Dufresne 2015-04-05 16:09:48 UTC
After many systemd updates and upgrading to F21, I no longer receive this error message. I'm left to assume it was fixed somewhere along the way.


Note You need to log in before you can comment on or make changes to this bug.