Re: [!GIT PULL] kdbus for 4.2

From: Richard Weinberger
Date: Fri Jul 03 2015 - 04:54:10 EST


On Fri, Jul 3, 2015 at 10:43 AM, David Herrmann <dh.herrmann@xxxxxxxxx> wrote:
> Hi
>
> On Fri, Jul 3, 2015 at 2:39 AM, Andy Lutomirski <luto@xxxxxxxxxxxxxx> 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.

Just because I'm starring right now at similar issues, how can I run
systemd-git?
I fear to use a plain "make && make install" as I don't want to break my
distro's package management and I want to make sure that nothing from the
currently installed systemd influences the system.

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