{"id":276,"date":"2015-06-08T15:03:13","date_gmt":"2015-06-08T15:03:13","guid":{"rendered":"http:\/\/www.micha.name\/blog\/?p=276"},"modified":"2015-06-08T15:11:14","modified_gmt":"2015-06-08T15:11:14","slug":"debian-issues-after-upgrade-to-systemd","status":"publish","type":"post","link":"https:\/\/www.micha.name\/blog\/2015\/06\/08\/debian-issues-after-upgrade-to-systemd\/","title":{"rendered":"Debian &#8211; issues after &#8220;upgrade&#8221; to systemd"},"content":{"rendered":"<p>So I&#8217;ve been tearing my hair out for quite a while now after Debian changed from sysv to systemd as the init system.<\/p>\n<p>After some update or other, my laptop&#8217;s internal mouse and keyboard would not work under X. In a terminal they worked fine, as did external USB devices. This breakage took a while to track down to Debian having installed systemd automatically.  I &#8220;fixed&#8221; this by reverting to sysv.<\/p>\n<p>However, under sysv init, KDE&#8217;s Dolphin could no longer mount devices; permission errors. I tried many solutions to fix this all to no avail (*). Using udiskctrl I could mount devices manually, but that&#8217;s a bit of a pain. Clearly I needed to move to systemd, where the permission problems did not exist.<\/p>\n<p>After various online searches I finally hit on the real culprit: I had mounted \/var\/run and \/var\/lock as tmpfs to save the SSD on my new laptop, many moons ago. At some point, Debian changed these directories to be symlinks to locations which are already tmpfs-mounts, and hence my local manual configuration overrode those mounts, breaking systemd in various interesting ways.<\/p>\n<p>The following bug-report finally got me on the right tracK:<br \/>\nhttps:\/\/bugs.debian.org\/cgi-bin\/bugreport.cgi?bug=761076<\/p>\n<p>So I removed the offending lines in \/etc\/fstab, rebooted, and systemd is happy.<\/p>\n<p>Search Terms:<br \/>\n&#8220;Failed to get D-Bus connection&#8221;<br \/>\n&#8220;Failed to get D-Bus connection: No such file or directory&#8221;<br \/>\n&#8220;systemd laptop keyboard not working&#8221;<br \/>\n&#8220;systemd-journald: Received SIGTERM from PID 1 (systemd)&#8221;<\/p>\n<p>(*)UPDATE: this is a separate issue; yet to be resolved. I thought this worked when I booted under systemd, but it doesn&#8217;t.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Debian: ensure \/var\/run and \/var\/lock are symlinks and not directly mounted, or systemd will break in many interesting ways.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[11,56,29],"tags":[],"_links":{"self":[{"href":"https:\/\/www.micha.name\/blog\/wp-json\/wp\/v2\/posts\/276"}],"collection":[{"href":"https:\/\/www.micha.name\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.micha.name\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.micha.name\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.micha.name\/blog\/wp-json\/wp\/v2\/comments?post=276"}],"version-history":[{"count":2,"href":"https:\/\/www.micha.name\/blog\/wp-json\/wp\/v2\/posts\/276\/revisions"}],"predecessor-version":[{"id":278,"href":"https:\/\/www.micha.name\/blog\/wp-json\/wp\/v2\/posts\/276\/revisions\/278"}],"wp:attachment":[{"href":"https:\/\/www.micha.name\/blog\/wp-json\/wp\/v2\/media?parent=276"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.micha.name\/blog\/wp-json\/wp\/v2\/categories?post=276"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.micha.name\/blog\/wp-json\/wp\/v2\/tags?post=276"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}