<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="https://dev1galaxy.org/extern.php?action=feed&amp;tid=6591&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / KDE login oddity]]></title>
		<link>https://dev1galaxy.org/viewtopic.php?id=6591</link>
		<description><![CDATA[The most recent posts in KDE login oddity.]]></description>
		<lastBuildDate>Sun, 05 May 2024 23:20:05 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: KDE login oddity]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=49822#p49822</link>
			<description><![CDATA[<p>Hi, it&#039;s probably waiting for network shares, time (ntp) and dhcp. Kde is a networking office environment... imo</p><p>I don&#039;t have your problem, It could be that I turn off all services non-related to a single pc.</p>]]></description>
			<author><![CDATA[dummy@example.com (GlennW)]]></author>
			<pubDate>Sun, 05 May 2024 23:20:05 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=49822#p49822</guid>
		</item>
		<item>
			<title><![CDATA[KDE login oddity]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=49818#p49818</link>
			<description><![CDATA[<p>am running daedalus+KDE and there is an odd behavior i would like<br />to understand better.</p><p>the KDE login screen has several &#039;buttons&#039; in addition to the password-box:<br />&#160; &#160;sleep, hibernate, restart, shutdown</p><p>these buttons are non-functional on my computer but are working in a QEMU<br />VM (daedalus+KDE)</p><p>KDE login uses sddm (and sddm-helper)</p><p>i am guessing this problem has something to do with init (boot-time). so,<br />testing this idea, i added a delay to /etc/init.d/sddm just before the<br />&quot;call do_start_cmd&quot;</p><p>after adding this delay the login-screen buttons became functional.</p><p>testing on this computer shows i need approx 250 millisecond delay to get<br />these buttons to become functional. 200 milliseconds is not enough.</p><p>i would like to know how to determine what sddm is waiting on. how does one<br />debug timing-related issues like this?</p>]]></description>
			<author><![CDATA[dummy@example.com (grunchy)]]></author>
			<pubDate>Sun, 05 May 2024 21:24:09 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=49818#p49818</guid>
		</item>
	</channel>
</rss>
