Package: consolekit
Version: 0.4.5-1
Severity: normal

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these lines ***

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Jan De Luyck <bugs+deb...@kcore.org>
To: Debian Bug Tracking System <sub...@bugs.debian.org>
Subject: consolekit: multiseat results in inactive sessions
Bcc: Jan De Luyck <bugs+deb...@kcore.org>

Package: consolekit
Version: 0.4.5-1
Severity: normal

Dear Maintainer,

I've got Debian Sid configured in a multiseat situation, with 2 
gpu's/screens/mice/keyboards.
This setup works.

DE of choice is XFCE.
Login manager is lightdm

When one user logs in, consolekit correctly tags the session as local and 
active:
Session3:
        unix-user = '1001'
        realname = 'User1'
        seat = 'Seat1'
        session-type = ''
        active = TRUE
        x11-display = ':1'
        x11-display-device = '/dev/tty8'
        display-device = ''
        remote-host-name = ''
        is-local = TRUE
        on-since = '2011-12-09T10:05:33.260932Z'
        login-session-id = '4294967295'

Now, second user logs into other seat, and this session is marked local and not 
active
Session4:
        unix-user = '1000'
        realname = 'User2'
        seat = 'Seat1'
        session-type = ''
        active = FALSE
        x11-display = ':0'
        x11-display-device = '/dev/tty7'
        display-device = ''
        remote-host-name = ''
        is-local = TRUE
        on-since = '2011-12-09T10:05:48.215295Z'
        login-session-id = '4294967295'

causing nothing that needs policykit (shutdown/usb mounting/...) to work.

Expected result: both sessions should be marked active and local. Perhaps this 
has
to do with the seat name being the same on both? (they're named differently in 
xorg.conf)

If user2 now logs out, and logs in again, then user1's active session will be 
marked inactive
and user2 will get the active session.


-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages consolekit depends on:
ii  dbus                   1.4.16-1
ii  libc6                  2.13-21
ii  libck-connector0       0.4.5-1
ii  libdbus-1-3            1.4.16-1
ii  libdbus-glib-1-2       0.98-1
ii  libglib2.0-0           2.30.2-4
ii  libpolkit-gobject-1-0  0.102-2
ii  libx11-6               2:1.4.4-4
ii  zlib1g                 1:1.2.3.4.dfsg-3

Versions of packages consolekit recommends:
ii  libpam-ck-connector  0.4.5-1

consolekit suggests no packages.

-- no debconf information

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages consolekit depends on:
ii  dbus                   1.4.16-1
ii  libc6                  2.13-21
ii  libck-connector0       0.4.5-1
ii  libdbus-1-3            1.4.16-1
ii  libdbus-glib-1-2       0.98-1
ii  libglib2.0-0           2.30.2-4
ii  libpolkit-gobject-1-0  0.102-2
ii  libx11-6               2:1.4.4-4
ii  zlib1g                 1:1.2.3.4.dfsg-3

Versions of packages consolekit recommends:
ii  libpam-ck-connector  0.4.5-1

consolekit suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to