On Tue, May 13, 2014 at 11:57 PM, Ismael Bouya
wrote:
> Hi,
>
> I don't know if it's necessary to send the request upstream for the moment:
> They are busy moving things to kdbus (which is the kernel implementation of
> dbus, and not "KDE-dbus" as I thought initially).
Anyway, I finally managed t
> I don't say of course that you shouldn't do it, just keep in mind that
> it's not equivalent :p
I know, thanks, I already had similar problems with gpg-agent. I solved this
problem with `After=gpg-agent.service` in tmux.service. It's not perfect, but it
seems to work.
(Wed, May 14, 2014 at 09:45:40AM +0200) Yamakaky :
> Now I understand why sometimes I have two dbus daemons, thanks ! It's because
> I
> manage tmux with systemd --user, and $DBUS is set by my xorg session not
> managed
> by systemd.
Watch out about that. It's tempting to have your tmux managed
Now I understand why sometimes I have two dbus daemons, thanks ! It's because I
manage tmux with systemd --user, and $DBUS is set by my xorg session not managed
by systemd.
In fact, why isn't there a user unit for dbus by default ?
On Tue, May 13, 2014 at 3:04 AM, Ismael Bouya
wrote:
>
> [snip-explanation]
> --
> Ismael
>
Thank you, Ismael. I've not yet implemented what you've suggested (been a
bit busy), but I'll report back once I get the time to play with my laptop.
I'm certain it works, as your explanation makes a lot o
Hi,
I don't know if it's necessary to send the request upstream for the moment:
They are busy moving things to kdbus (which is the kernel implementation of
dbus, and not "KDE-dbus" as I thought initially).
Things are actually slightly messed up currently (that's my opinion, when I
spent time read
On Mon, May 12, 2014 at 8:04 PM, Ismael Bouya
wrote:
> For me it works both with user and system.
>
> [skip instructions]
>
> (Note that your shell doesn't have to know the DBUS_SESSION_BUS_ADDRESS
> variable)
Thank you!! I have followed your instructions and it actually works,
although I have to
(Mon, May 12, 2014 at 11:23:33PM +0900) Savyasachee Jha :
> Well, I just tried this out on my laptop, and it gives two different error
> messages.
>
> $ sysytemd-run --user /usr/bin/ls
> Failed to create message: Input/output error
>
> $ sudo systemd-run --user /usr/bin/ls
> Failed to create bus
On Mon, May 12, 2014 at 11:17 PM, Rodrigo Rivas wrote:
> Hello, list!
>
> This is an issue that has been nagging me for a while, and I thought
> that it was something I did to my machine, until I tested it in
> another Arch installation, and it is all the same.
>
> The problem is when I run for e
9 matches
Mail list logo
