<html>
    <head>
      <base href="https://bugs.freedesktop.org/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Priority</th>
          <td>medium
          </td>
        </tr>

        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW --- - commit 7708588119 broke logind DBus API"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=67131">67131</a>
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>systemd-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>commit 7708588119 broke logind DBus API
          </td>
        </tr>

        <tr>
          <th>QA Contact</th>
          <td>systemd-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>normal
          </td>
        </tr>

        <tr>
          <th>Classification</th>
          <td>Unclassified
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>michael+freedesktop@stapelberg.de
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>Other
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>general
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>systemd
          </td>
        </tr></table>
      <p>
        <div>
        <pre>In <a href="http://bugs.debian.org/717403">http://bugs.debian.org/717403</a> we recently noticed that libpam-systemd 204
cannot talk to systemd 44.

I tracked this down to this commit, which introduced a new reply element:

commit 770858811930c0658b189d980159ea1ac5663467
Author: Lennart Poettering <<a href="mailto:lennart@poettering.net">lennart@poettering.net</a>>
Date:   Tue Oct 16 19:21:21 2012 +0200

    logind: only release logind session from the PAM module if the same module
instance actually created it

I am not 100% sure if this reply is covered by
<a href="http://www.freedesktop.org/wiki/Software/systemd/InterfacePortabilityAndStabilityChart/">http://www.freedesktop.org/wiki/Software/systemd/InterfacePortabilityAndStabilityChart/</a>

Could you clarify how updates from 44 to 204 are supposed to work? Do we _need_
to restart systemd-logind or could you fix libpam-systemd to work with older
versions of systemd-logind, albeit not perfectly (it sounds like the commit is
a bugfix)?

Thanks.</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are the QA Contact for the bug.</li>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>