dbus session bus initialization under openbox minimal desktopHow can I run Openbox using the GNOME/Openbox session?How to read dbus-monitor output?Access dbus session bus from upstart script“OnlyShowIn” and “NotShowIn” not being obeyed in Openbox session?Openbox: desktop, autostart, new aplications installation issue“Failed to start session” OpenboxOpenbox configuration issueDropbox icon not working - Unable to create ~/.dbus/session-busControlling multiple instances of same application with dbus?Add a desktop icon in OpenBox
New order #4: World
Why is my log file so massive? 22gb. I am running log backups
Is ipsum/ipsa/ipse a third person pronoun, or can it serve other functions?
Does a dangling wire really electrocute me if I'm standing in water?
Is it wise to hold on to stock that has plummeted and then stabilized?
Ideas for 3rd eye abilities
Why doesn't a const reference extend the life of a temporary object passed via a function?
Pristine Bit Checking
Does the average primeness of natural numbers tend to zero?
Information to fellow intern about hiring?
Is every set a filtered colimit of finite sets?
Are cabin dividers used to "hide" the flex of the airplane?
Why do we use polarized capacitors?
I’m planning on buying a laser printer but concerned about the life cycle of toner in the machine
What happens when a metallic dragon and a chromatic dragon mate?
Are objects structures and/or vice versa?
"My colleague's body is amazing"
What are the advantages and disadvantages of running one shots compared to campaigns?
Patience, young "Padovan"
Could a US political party gain complete control over the government by removing checks & balances?
What does "enim et" mean?
Typesetting a double Over Dot on top of a symbol
Finding files for which a command fails
How could a lack of term limits lead to a "dictatorship?"
dbus session bus initialization under openbox minimal desktop
How can I run Openbox using the GNOME/Openbox session?How to read dbus-monitor output?Access dbus session bus from upstart script“OnlyShowIn” and “NotShowIn” not being obeyed in Openbox session?Openbox: desktop, autostart, new aplications installation issue“Failed to start session” OpenboxOpenbox configuration issueDropbox icon not working - Unable to create ~/.dbus/session-busControlling multiple instances of same application with dbus?Add a desktop icon in OpenBox
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
everyone. Looking for some help understanding dbus in an effort to better understand what I need to do to run a minimal desktop (openbox in this case).
Goal:
Find out if openbox/dbus behavior is expected, and learn a bit more about how dbus works.
Scenario:
Clean install of Ubuntu Mate 18.10, then I installed Openbox and selected it from the LightDM Greeter, thus kicking off the openbox-session script, not just raw openbox. I observed that the tint2 systray did load but when I ran (for instance) nm_applet, the icon wouldn't show up. I did however find that when I ran nm_applet via sudo nm_applet
or dbus-launch nm_applet
then its icon did show up.
That's not ideal and I needed to get a session bus going that all of my session processes could use. Digging around I eventually wound up at Gentoo's wiki page for Openbox: https://wiki.gentoo.org/wiki/Openbox
It specified that in openbox's 'environment' file, one should put the following (among another couple of things that were suggested):
if which dbus-launch >/dev/null && test -z "$DBUS_SESSION_BUS_ADDRESS"; then
eval `dbus-launch --sh-syntax --exit-with-session`
fi
which I tried. Then when I started up Openbox, manually started nm_applet (without root and without dbus-launch) then its icon DID appear in systray.
The part I need help with:
I observed though (having tried it several times on several machines) that the first time that 'environment' file is used where the dbus-launch command is eval'd was the only time that it seemed to be required. On subsequent boots where I just let it use an entirely empty 'environment' file, nm_applet (and other applets - bluetooth, keepass, etc) still had their icons in the systray.
So... is that normal or expected? I've got a very flimsy grasp on dbus and how it works and I can't fathom why subsequent loads WITHOUT that eval'd dbus-launch line would still allow systray and applets to communicate across the session bus. It feels to me like the session bus wasn't "initialized" or something until after the first time that line ran, and thereafter something was cached somewhere to allow that session bus to continue to function as normal...
dbus openbox
New contributor
add a comment |
everyone. Looking for some help understanding dbus in an effort to better understand what I need to do to run a minimal desktop (openbox in this case).
Goal:
Find out if openbox/dbus behavior is expected, and learn a bit more about how dbus works.
Scenario:
Clean install of Ubuntu Mate 18.10, then I installed Openbox and selected it from the LightDM Greeter, thus kicking off the openbox-session script, not just raw openbox. I observed that the tint2 systray did load but when I ran (for instance) nm_applet, the icon wouldn't show up. I did however find that when I ran nm_applet via sudo nm_applet
or dbus-launch nm_applet
then its icon did show up.
That's not ideal and I needed to get a session bus going that all of my session processes could use. Digging around I eventually wound up at Gentoo's wiki page for Openbox: https://wiki.gentoo.org/wiki/Openbox
It specified that in openbox's 'environment' file, one should put the following (among another couple of things that were suggested):
if which dbus-launch >/dev/null && test -z "$DBUS_SESSION_BUS_ADDRESS"; then
eval `dbus-launch --sh-syntax --exit-with-session`
fi
which I tried. Then when I started up Openbox, manually started nm_applet (without root and without dbus-launch) then its icon DID appear in systray.
The part I need help with:
I observed though (having tried it several times on several machines) that the first time that 'environment' file is used where the dbus-launch command is eval'd was the only time that it seemed to be required. On subsequent boots where I just let it use an entirely empty 'environment' file, nm_applet (and other applets - bluetooth, keepass, etc) still had their icons in the systray.
So... is that normal or expected? I've got a very flimsy grasp on dbus and how it works and I can't fathom why subsequent loads WITHOUT that eval'd dbus-launch line would still allow systray and applets to communicate across the session bus. It feels to me like the session bus wasn't "initialized" or something until after the first time that line ran, and thereafter something was cached somewhere to allow that session bus to continue to function as normal...
dbus openbox
New contributor
add a comment |
everyone. Looking for some help understanding dbus in an effort to better understand what I need to do to run a minimal desktop (openbox in this case).
Goal:
Find out if openbox/dbus behavior is expected, and learn a bit more about how dbus works.
Scenario:
Clean install of Ubuntu Mate 18.10, then I installed Openbox and selected it from the LightDM Greeter, thus kicking off the openbox-session script, not just raw openbox. I observed that the tint2 systray did load but when I ran (for instance) nm_applet, the icon wouldn't show up. I did however find that when I ran nm_applet via sudo nm_applet
or dbus-launch nm_applet
then its icon did show up.
That's not ideal and I needed to get a session bus going that all of my session processes could use. Digging around I eventually wound up at Gentoo's wiki page for Openbox: https://wiki.gentoo.org/wiki/Openbox
It specified that in openbox's 'environment' file, one should put the following (among another couple of things that were suggested):
if which dbus-launch >/dev/null && test -z "$DBUS_SESSION_BUS_ADDRESS"; then
eval `dbus-launch --sh-syntax --exit-with-session`
fi
which I tried. Then when I started up Openbox, manually started nm_applet (without root and without dbus-launch) then its icon DID appear in systray.
The part I need help with:
I observed though (having tried it several times on several machines) that the first time that 'environment' file is used where the dbus-launch command is eval'd was the only time that it seemed to be required. On subsequent boots where I just let it use an entirely empty 'environment' file, nm_applet (and other applets - bluetooth, keepass, etc) still had their icons in the systray.
So... is that normal or expected? I've got a very flimsy grasp on dbus and how it works and I can't fathom why subsequent loads WITHOUT that eval'd dbus-launch line would still allow systray and applets to communicate across the session bus. It feels to me like the session bus wasn't "initialized" or something until after the first time that line ran, and thereafter something was cached somewhere to allow that session bus to continue to function as normal...
dbus openbox
New contributor
everyone. Looking for some help understanding dbus in an effort to better understand what I need to do to run a minimal desktop (openbox in this case).
Goal:
Find out if openbox/dbus behavior is expected, and learn a bit more about how dbus works.
Scenario:
Clean install of Ubuntu Mate 18.10, then I installed Openbox and selected it from the LightDM Greeter, thus kicking off the openbox-session script, not just raw openbox. I observed that the tint2 systray did load but when I ran (for instance) nm_applet, the icon wouldn't show up. I did however find that when I ran nm_applet via sudo nm_applet
or dbus-launch nm_applet
then its icon did show up.
That's not ideal and I needed to get a session bus going that all of my session processes could use. Digging around I eventually wound up at Gentoo's wiki page for Openbox: https://wiki.gentoo.org/wiki/Openbox
It specified that in openbox's 'environment' file, one should put the following (among another couple of things that were suggested):
if which dbus-launch >/dev/null && test -z "$DBUS_SESSION_BUS_ADDRESS"; then
eval `dbus-launch --sh-syntax --exit-with-session`
fi
which I tried. Then when I started up Openbox, manually started nm_applet (without root and without dbus-launch) then its icon DID appear in systray.
The part I need help with:
I observed though (having tried it several times on several machines) that the first time that 'environment' file is used where the dbus-launch command is eval'd was the only time that it seemed to be required. On subsequent boots where I just let it use an entirely empty 'environment' file, nm_applet (and other applets - bluetooth, keepass, etc) still had their icons in the systray.
So... is that normal or expected? I've got a very flimsy grasp on dbus and how it works and I can't fathom why subsequent loads WITHOUT that eval'd dbus-launch line would still allow systray and applets to communicate across the session bus. It feels to me like the session bus wasn't "initialized" or something until after the first time that line ran, and thereafter something was cached somewhere to allow that session bus to continue to function as normal...
dbus openbox
dbus openbox
New contributor
New contributor
New contributor
asked 4 hours ago
scooterx3scooterx3
1
1
New contributor
New contributor
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
scooterx3 is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1132293%2fdbus-session-bus-initialization-under-openbox-minimal-desktop%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
scooterx3 is a new contributor. Be nice, and check out our Code of Conduct.
scooterx3 is a new contributor. Be nice, and check out our Code of Conduct.
scooterx3 is a new contributor. Be nice, and check out our Code of Conduct.
scooterx3 is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1132293%2fdbus-session-bus-initialization-under-openbox-minimal-desktop%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown