<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="http://dev1galaxy.org/extern.php?action=feed&amp;tid=4941&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / Runit: dbus runscript broken]]></title>
		<link>http://dev1galaxy.org/viewtopic.php?id=4941</link>
		<description><![CDATA[The most recent posts in Runit: dbus runscript broken.]]></description>
		<lastBuildDate>Fri, 18 Mar 2022 09:09:45 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: Runit: dbus runscript broken]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=35268#p35268</link>
			<description><![CDATA[<p>no problems with openbox either, but changed runscript as proposed, no actual difference noticed. everything works as it did before.</p>]]></description>
			<author><![CDATA[dummy@example.com (xinomilo)]]></author>
			<pubDate>Fri, 18 Mar 2022 09:09:45 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=35268#p35268</guid>
		</item>
		<item>
			<title><![CDATA[Re: Runit: dbus runscript broken]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=35205#p35205</link>
			<description><![CDATA[<p>same with @fsmithred, unable to reproduce.<br />currently running lightdm &amp; MATE on devuan ceres (sid), but mostly work with openbox.<br />dbus 1.14.0-1devuan1<br />runit 2.1.2-45<br />will also try with the suggested line on next reboot.</p>]]></description>
			<author><![CDATA[dummy@example.com (xinomilo)]]></author>
			<pubDate>Mon, 14 Mar 2022 18:03:19 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=35205#p35205</guid>
		</item>
		<item>
			<title><![CDATA[Re: Runit: dbus runscript broken]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=35204#p35204</link>
			<description><![CDATA[<p>Hi,</p><p>I&#039;m still affected in Debian, not sure exactly if it&#039;s a change in dbus or something else. Devuan is rebuilding dbus without systemd bits, so maybe that&#039;s why it&#039;s not affected? (just a wild guess)<br />In any case dbus is dropping privileges and run with the messagebus by itself, so the &#039;chpst -umessagebus&#039; is useless, but as long as it doesn&#039;t cause harm..</p><div class="quotebox"><blockquote><div><p>Running xfce with lightdm here. What would you like me to check?</p></div></blockquote></div><p>I&#039;m with slim and LxQT. Not sure, as long as nobody complains, I&#039;ll just leave a warning here in case with a future upgrade things start to break.</p><p>Thanks<br />Lorenzo</p>]]></description>
			<author><![CDATA[dummy@example.com (Lorenzo)]]></author>
			<pubDate>Mon, 14 Mar 2022 17:04:04 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=35204#p35204</guid>
		</item>
		<item>
			<title><![CDATA[Re: Runit: dbus runscript broken]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=35203#p35203</link>
			<description><![CDATA[<p>I am unable to reproduce the problem. I just upgraded my daedalus with runit. The dbus version went from 1.12.something+devuan3 to 1.14.0-1devuan1, and my desktop still comes up after a reboot. Looks like it&#039;s all working ok.</p><p>This line is still present in the runscript:</p><div class="codebox"><pre><code>exec chpst -umessagebus dbus-daemon --system --nofork --nopidfile</code></pre></div><p>Running xfce with lightdm here. What would you like me to check?</p>]]></description>
			<author><![CDATA[dummy@example.com (fsmithred)]]></author>
			<pubDate>Mon, 14 Mar 2022 16:13:24 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=35203#p35203</guid>
		</item>
		<item>
			<title><![CDATA[Runit: dbus runscript broken]]></title>
			<link>http://dev1galaxy.org/viewtopic.php?pid=35185#p35185</link>
			<description><![CDATA[<p>Hi all,</p><p>Just a warning to runit init users, that the dbus runscript that I provided on this forum is now broken on Debian (at least for me) and I suspect the change will hit Devuan soon: synthoms are that dbus fails to start and everything that depends on it is broken (so your DE, login manager and other dbus services too will malfunction)</p><p>in short, if you are using a dbus runscript that has an exec line like</p><div class="codebox"><pre><code>exec chpst -umessagebus dbus-daemon --system --nofork --nopidfile</code></pre></div><p>I suggest to change it to</p><div class="codebox"><pre><code>exec dbus-daemon --system --nofork --nopidfile</code></pre></div><p>Using chpst seem to break recent version of dbus as it can&#039;t access to its own socket.<br />Dbus is able to drop privileges by itself.</p><p>Lorenzo</p>]]></description>
			<author><![CDATA[dummy@example.com (Lorenzo)]]></author>
			<pubDate>Sun, 13 Mar 2022 23:23:07 +0000</pubDate>
			<guid>http://dev1galaxy.org/viewtopic.php?pid=35185#p35185</guid>
		</item>
	</channel>
</rss>
