<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Dbus on Enconn</title>
    <link>https://enconn.fr/tags/dbus/</link>
    <description>Recent content in Dbus on Enconn</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <managingEditor>contact@enconn.fr (Sébastien Blin)</managingEditor>
    <webMaster>contact@enconn.fr (Sébastien Blin)</webMaster>
    <lastBuildDate>Tue, 20 Aug 2019 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://enconn.fr/tags/dbus/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Dbus on a server</title>
      <link>https://enconn.fr/blog/dbus-on-a-server/</link>
      <pubDate>Tue, 20 Aug 2019 00:00:00 +0000</pubDate><author>contact@enconn.fr (Sébastien Blin)</author>
      <guid>https://enconn.fr/blog/dbus-on-a-server/</guid>
      <description>&lt;p&gt;Some time ago, I had to run a script to test an application by sending dbus calls. The script was working great, until I moved it on a server with no graphical session. I ran the script as a System V init script, but you can encounter the same problem in a terminal or in a cron. The thing is that a dbus session is generally managed by KDE, Gnome or your graphical session.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
