Ask your questions here.
Post a reply
figlfdev

- figlfdev
- Posts: 116
- Joined: Tue May 31, 2016 6:23 pm

## dbus-launch

Tue Oct 25, 2016 5:57 am

its just weird and un-linux-like when things keep popping up out of nowhere without any known reason.
so it was before jessie was "stable," and systemd came in-- suddenly rc.local isnt running at boot. boy was that a lot of fun to find out about. and here we are.
similarly fun, i remove machine-id and atril no longer works. wow, i cant imagine how the pdf reader needs a f***ing uuid for my machine to work.
this is not good stuff. there used to be workarounds that had logic to them, and werent bizarre. even when you didnt know why they worked, you were (correctly) sure there was at least a decent (usually explainable) reason.
ive got tons of dbus-launch processes! i dont know why, ive got a week of uptime on this laptop (rare these days, trying out my own isos) and here they are, all of a sudden. scroogle tells me that init is calling them. very cool-- why?
if i go to read about this crap, it wants me to learn the entire subsystem, rather than just tell me what-the-f*** its for.
dbus-launch obviously launches stuff blah blah blah dbus-- a system for passing messages between--
nevermind that, why do i have all these processes?
blah blah blah init,
blah blah blah system messages,
blah blah blah this is too much like having systemd installed.
its a lot of opaque horsesh** for no given reason.
but if anyone has a guess why after 8 days of not having lots of dbus-launch processes open, now there are (actually i closed them, to find out if they would even close) id love to hear about it. whatever it is, it seems to be "launching" things with small numbers of hexadecimal digits.
hooray, things arent this opaque since ibm bios codes. "keyboard error? no... FFFF:0101" i mean who cares what a keyboard error is, anyway? let them narrow it down through trial and error.
now i do have a way of answering my own question, which is why you dont find me asking this stuff very often:
first, i remove /usr/bin/dbus-launch ...then, i find out what doesnt work. if everything works, i dont need it. if something doesnt work: hey! thats what its for!
in case you didnt notice: this is the year of the linux desktop.
you know it is, because this is the year that everything important bows to that silly f***ing crap instead.
thwak

- thwak
- Posts: 174
- Joined: Tue Nov 20, 2012 3:58 am

## Re: dbus-launch

Tue Oct 25, 2016 5:32 pm

https://dbus.freedesktop.org/doc/dbus-launch.1.html
scroll to bottom of manpage and read the sentence in "Notes" section
Where are all those instances coming from all of a sudden?
You mentioned a week-long session. Consider: How many times throughout the week did you launch stuffs via runner (gexec, whiskermenu, gksu, xfce4-appfinder) and/or launched a terminal emulator instance ~~ operations which may have spawned non-terminating instances of dbus-launch.
Run "htop" and F6 sort the output by pid. Scroll back-n-fro through the running processes and note where (after what, before what) each dbus-launch instance was initiated. This will help you figure out where they are "coming from". Also, the rightmost column should (does here) show the full commandline for each entry.
thwak

- thwak
- Posts: 174
- Joined: Tue Nov 20, 2012 3:58 am

## Re: dbus-launch

Tue Oct 25, 2016 5:47 pm

We've already danced the uuid (dbus-uuidgen) dance.
I don't understand why you're still pissing with, wrestling with, fussing over that.
Deleting machine-id via a line in shutdown script is an easy workable option.
figlfdev

- figlfdev
- Posts: 116
- Joined: Tue May 31, 2016 6:23 pm

## Re: dbus-launch

Wed Oct 26, 2016 12:27 am

> thwak wrote:We've already danced the uuid (dbus-uuidgen) dance.
> I don't understand why you're still pissing with, wrestling with, fussing over that.

no, you dont... and its like when people dont understand why its unacceptable to require libsystemd in things that arent related to systemd. i dont even require you to understand it. but of course youre welcome to, or not.

> Deleting machine-id via a line in shutdown script is an easy workable option.

for you-- that solution makes you happy. i consider a pdf viewer broken if it requires machine-id to exist. and i delete it on boot, which makes it easier to find out whats broken without it. (and yes-- i want to know what needs it.)
per your reply, i think the instances either have something to do with evince, or have something to do with opening a term window that i dont usually open-- the one from xfce or something. those are the most likely culprits, thanks.
Post a reply
Jump to:

Powered by phpBB © phpBB Group.

phpBB Mobile / SEO by Artodia.