On 2018-06-30 13:55:18 (+0200), Tinu Weber wrote:
> On Sat, Jun 30, 2018 at 13:34:11 +0200, Bjoern Franke wrote:
> > > Are you truly logged in as this second user for whom it does not work,
> > > or just su(1)'d, etc?
> >
> > Erm, just used "sudo -u user2 -s" to login as user2. I assumed spawning
On Sat, Jun 30, 2018 at 13:34:11 +0200, Bjoern Franke wrote:
> > Are you truly logged in as this second user for whom it does not work,
> > or just su(1)'d, etc?
>
> Erm, just used "sudo -u user2 -s" to login as user2. I assumed spawning
> an own zsh as user2 would do the right thing.
-s only
Hi Bjoern,
> > Are you truly logged in as this second user for whom it does not
> > work, or just su(1)'d, etc?
>
> Erm, just used "sudo -u user2 -s" to login as user2. I assumed
> spawning an own zsh as user2 would do the right thing.
It doesn't here. As UID 1000 logged into an XFCE desktop
Hi Ralph,
>
> Are you truly logged in as this second user for whom it does not work,
> or just su(1)'d, etc?
Erm, just used "sudo -u user2 -s" to login as user2. I assumed spawning
an own zsh as user2 would do the right thing.
> My guess is there's a user.service running for the user ID where
Hi Bjoern,
> > I'm trying to create a systemd timer for a user to run duply daily.
> > For one user the enabled worked fine, but another one:
> >
> > systemctl --user enable backup.timer
> > Failed to connect to bus: No such file or directory
Are you truly logged in as this second user
On 27 June 2018 at 08:26, Bjoern Franke wrote:
> Hi,
>
> I'm trying to create a systemd timer for a user to run duply daily. For
> one user the enabled worked fine, but another one:
>
> systemctl --user enable backup.timer
> Failed to connect to bus: No such file or directory
>
> I have no clue
Hi,
> Good,
>
> Each user + the system has his own dbus. Normally, you should have
> dbus.service and dbus.socket units somewhere (/usr/lib/systemd/user
> and/or /etc/systemd/user and/or .config/systemd/user)
>
> If it works correctly for one of the users, then probably
> /usr/lib/systemd/user
> systemctl --user status has the same error. How do I start dbus for the
> second user? systemctl enable --user dbus fails due the same error, and
> system's dbus is running.
Good,
Each user + the system has his own dbus. Normally, you should have
dbus.service and dbus.socket units somewhere
Hi Ismael,
thanks for your both hints.
>
> The two clues I have according to your error are
> - Is .config/systemd/user created? (Maybe it has to be created manually)
Yes, I've dropped there the timer and service file.
> - Does the second user have dbus started correctly? (for instance, does
Hi Bjoern,
> I'm trying to create a systemd timer for a user to run duply daily. For
> one user the enabled worked fine, but another one:
>
> systemctl --user enable backup.timer
> Failed to connect to bus: No such file or directory
>
> I have no clue why this happens, systemctl daemon-reload
Hi,
I'm trying to create a systemd timer for a user to run duply daily. For
one user the enabled worked fine, but another one:
systemctl --user enable backup.timer
Failed to connect to bus: No such file or directory
I have no clue why this happens, systemctl daemon-reload (also with
--user) did
11 matches
Mail list logo
