<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Desktop on &gt; Cabronerias de Matu</title>
    <link>https://blog.cabroneria.com/categories/desktop/</link>
    <description>Recent content in Desktop on &gt; Cabronerias de Matu</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 17 May 2026 00:00:00 -0400</lastBuildDate>
    <atom:link href="https://blog.cabroneria.com/categories/desktop/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>FreeBSD 15.1 : Running Plasma Wayland without SDDM</title>
      <link>https://blog.cabroneria.com/post/0009_freebsd15.1_wayland_no_sddm/</link>
      <pubDate>Sun, 17 May 2026 00:00:00 -0400</pubDate>
      <guid>https://blog.cabroneria.com/post/0009_freebsd15.1_wayland_no_sddm/</guid>
      <description>&lt;h2 id=&#34;problem&#34;&gt;Problem&lt;/h2&gt;&#xA;&lt;p&gt;After upgrading to FreeBSD &lt;code&gt;15.1-BETA3&lt;/code&gt; and getting &lt;code&gt;DRM 6.12&lt;/code&gt; working see:&lt;a href=&#34;https://blog.cabroneria.com/bits/0014_freebsd-15.1-drm-i915-runbook/&#34;&gt;freebsd-15.1-drm-i915-runbook.md&lt;/a&gt;, Plasma Wayland would not start through SDDM. Logging in via SDDM&amp;rsquo;s greeter bounced back to the login screen with no error output. &lt;code&gt;wayland-session.log&lt;/code&gt; was empty. XFCE (X11) worked fine through SDDM.&lt;/p&gt;&#xA;&lt;h2 id=&#34;root-cause&#34;&gt;Root Cause&lt;/h2&gt;&#xA;&lt;p&gt;Session activation failed in this configuration. &lt;code&gt;ck-list-sessions&lt;/code&gt; showed:&lt;/p&gt;&#xA;&lt;pre tabindex=&#34;0&#34;&gt;&lt;code&gt;$ ck-list-sessions | grep active&#xA;        active = FALSE&#xA;&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;When a session is not marked active, kwin_wayland cannot acquire DRM device access : &lt;code&gt;/dev/dri/*&lt;/code&gt; access fails, libseat/seatd integration may not work, and the Wayland compositor exits immediately, often with no log output. This matches the symptom exactly.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
