MIME-Version: 1.0
In-Reply-To: <CALCETrU7iTX6Q_8UUueMxZqcVM0CgnkqMRXMxc2VgWs3pgcm=Q@mail.gmail.com>
References: <20150626192628.GA25806@kroah.com>
	<CALCETrU8ESAr0SFTOeR=HBSaQSSYznz2uUDEkRxhx+G79Hge=w@mail.gmail.com>
	<CAG-2HqXSFU7J+2X1cX4UMe0aSEzQp_vXNs--vB5Ot8PzKOAf2A@mail.gmail.com>
	<CALCETrU7iTX6Q_8UUueMxZqcVM0CgnkqMRXMxc2VgWs3pgcm=Q@mail.gmail.com>
Date: Fri, 3 Jul 2015 10:43:21 +0200
Message-ID: <CANq1E4TfyDFJm-NGQ8Ndx6rXoVL4YVp9QyQ_TH9MPs+yp4Bs7A@mail.gmail.com>
Subject: Re: [!GIT PULL] kdbus for 4.2
From: David Herrmann <dh.herrmann@gmail.com>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Tom Gundersen <teg@jklm.no>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Andrew Morton <akpm@linux-foundation.org>,
        Arnd Bergmann <arnd@arndb.de>,
        "Eric W. Biederman" <ebiederm@xmission.com>,
        One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>,
        Jiri Kosina <jkosina@suse.cz>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Daniel Mack <daniel@zonque.org>, Djalal Harouni <tixxdz@opendz.org>
Content-Type: text/plain; charset=UTF-8
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1343
Lines: 31

Hi

On Fri, Jul 3, 2015 at 2:39 AM, Andy Lutomirski <luto@amacapital.net> wrote:
> Problem 1: Booting a kdbus-enabled kernel (CONFIG_KDBUS=y) causes gdm
> to bail saying "oops, something went wrong" or whatever the useless
> standard error message is.
>
> I can work around problem 1 by booting with kdbus=1, but that's not
> okay.  Unless this is limited to just some narrow range of Rawhide
> versions, I don't think the kernel gets to make changes that break
> userspace like that.  Maybe this is a kernel issue, not a user issue,
> in which case it's not a big deal as long as it gets fixed.

You're saying booting with the same kernel but kdbus not compiled in works?

> Problem 2: Running 'sudo mount /mnt/share' from a terminal hangs the
> whole graphical session hard.  This is repeatable.  /mnt/share is
> virtfs, but I doubt that matters.

This is triggered by running through pam from outside the gfx-session
but on a shared VT. It's not directly related to kdbus, though. It's
fixed in systemd-git. As a workaround, you can remove pam_systemd from
the sudo/su pam config.

Thanks
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/