View Single Post
Old 02-21-2019, 08:27 PM   #20
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
Huh. lipc is talking over dbus, of course, so, that at least makes a tiny bit of sense, but, still, that's weird .

It's probably handled by one of the upstart jobs, but it might be a fairly early boot stuff, so it might take down the full framework with it (meaning you'll have to sit through the ~50s framework startup, even a "warm" restart like that).

EDIT: Yep, and it's aptly named "dbus" ;D.

And it will indeed take X down with it, which in turn brings down lab126_gui .

EDITē: Assuming your profile is accurate, of course, as upstart is FW 5.x only. Earlier iterations used old-school SysV init scripts and runlevels.

Last edited by NiLuJe; 02-21-2019 at 08:33 PM.
NiLuJe is offline   Reply With Quote