From: Chris Marusich <cmmarusich@gmail.com>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Programs like pcmanfm, evince, ... don't connect to dbus unless run with dbus-launch
Date: Wed, 01 Aug 2018 22:52:51 -0700 [thread overview]
Message-ID: <87wot9co24.fsf@gmail.com> (raw)
In-Reply-To: <20180731235419.7b824b45@scratchpost.org> (Danny Milosavljevic's message of "Tue, 31 Jul 2018 23:54:19 +0200")
[-- Attachment #1: Type: text/plain, Size: 906 bytes --]
Danny Milosavljevic <dannym@scratchpost.org> writes:
> dbus is an object-oriented inter-process-communication mechanism.
Wow, awesome overview! Thank you for taking the time to explain it.
I've always wondered how it was supposed to fit together.
> I wonder why it works with the GNOME desktop. Does it really?
What is "it"? What works with GNOME desktop, which you expect does not?
I use GNOME on GuixSD. For what it's worth, after I've logged into my
GNOME session, if I open up a GNOME Terminal, run "dbus-monitor", and
then launch Evince (from the application search menu), I do see a flurry
of activity related to Evince, so I think it's connecting to the session
bus (dbus-monitor monitors the session bus by default, apparently).
Regarding the lack of a "back" button in Evince, I do see one, and it
does seem to work. The button looks like a "<" symbol.
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-08-02 5:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 15:10 Programs like pcmanfm, evince, ... don't connect to dbus unless run with dbus-launch Brendan Tildesley
2018-07-28 19:40 ` Nils Gillmann
2018-07-31 21:54 ` Danny Milosavljevic
2018-08-02 5:52 ` Chris Marusich [this message]
2018-08-02 6:21 ` Brendan Tildesley
2018-08-05 0:23 ` Danny Milosavljevic
2018-08-05 0:30 ` Danny Milosavljevic
2018-08-05 11:57 ` Brendan Tildesley
2018-08-12 22:09 ` Danny Milosavljevic
2018-11-12 10:57 ` Brendan Tildesley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wot9co24.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.