On Mon, 16.02.15 11:14, Simon McVittie (simon.mcvit...@collabora.co.uk) wrote:
No, mine /etc/X11/xinitrc.d is Simon's /etc/X11/Xsession.d and similar
setups. It's apparently a distro-specific path.
Yes. I think /etc/X11/xinitrc.d is what Red Hat and its derivatives use.
Xsession.d is used
On 2015-02-16 at 11:14 +, Simon McVittie wrote:
On 14/02/15 18:26, Ivan Shapovalov wrote:
Yes, the per-session bus is there, but it is not used at all for
communication with per-user systemd instance.
I do want this to work, and I'm working on making it happen. It works on
my Debian
On 14/02/15 18:26, Ivan Shapovalov wrote:
Yes, the per-session bus is there, but it is not used at all for
communication with per-user systemd instance.
I do want this to work, and I'm working on making it happen. It works on
my Debian system, with the patched dbus that I recently uploaded to
On 2015-02-14 at 00:17 -0800, Alison Chaiken wrote:
Inside a Fedora 21 Qemu, I made a dead-simple 'gnome-weather.service'
and experimented with moving it in between system and user directories
in systemd 215.
Case 0: With /etc/systemd/system/gnome-weather.service, starts
normally with
Thanks very much, Ivan, for the detailed explanation.
I asked:
Question: What does the error message 'Process
org.freedesktop.systemd1 exited with status 1' mean?
Ivan:
this is a sign of that the systemd user instance (`systemd --user`)
isn't running. More specifically, the systemd user
On Sat, Feb 14, 2015 at 7:36 PM, Alison Chaiken ali...@she-devel.com
wrote:
Thanks very much, Ivan, for the detailed explanation.
I asked:
Question: What does the error message 'Process
org.freedesktop.systemd1 exited with status 1' mean?
Ivan:
this is a sign of that the systemd user
Mantas offers:
I think the idea was that the user instance would be started automatically
when the user first logged in.
(Which it is, at least on Arch: logind starts user@1000.service for me as
soon as pam_systemd tells it that I've logged in.
Some distros break it, either intentionally or
On Sat, Feb 14, 2015 at 9:37 PM, Alison Chaiken ali...@she-devel.com
wrote:
Mantas:
It's not broken on stock systemd. As long as your `systemd --user`
instance
is running, systemctl can contact it directly over the
$XDG_RUNTIME_DIR/systemd/private socket, so there's no hard dependency
on
On Sat, Feb 14, 2015 at 10:20 PM, Alison Chaiken ali...@she-devel.com
wrote:
Ivan writes:
So, I suppose, your `systemd --user` just fails to start somewhy, and
you are getting that cryptic error message because systemctl can't find
systemd on either of the buses.
Ah, after restarting the
Ivan writes:
So, I suppose, your `systemd --user` just fails to start somewhy, and
you are getting that cryptic error message because systemctl can't find
systemd on either of the buses.
Ah, after restarting the Qemu, I see in the journal:
Feb 13 22:09:06 fedora21.exerciseforthereader.org
Inside a Fedora 21 Qemu, I made a dead-simple 'gnome-weather.service'
and experimented with moving it in between system and user directories
in systemd 215.
Case 0: With /etc/systemd/system/gnome-weather.service, starts
normally with 'systemctl start gnome-weather'
Case 1: With
11 matches
Mail list logo
