All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: David Herrmann <dh.herrmann@gmail.com>,
	Andy Lutomirski <luto@amacapital.net>,
	Tom Gundersen <teg@jklm.no>,
	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>
Subject: Re: [!GIT PULL] kdbus for 4.2
Date: Fri, 03 Jul 2015 18:22:42 +0200	[thread overview]
Message-ID: <5596B6D2.70008@nod.at> (raw)
In-Reply-To: <20150703152706.GA10626@kroah.com>

Am 03.07.2015 um 17:27 schrieb Greg Kroah-Hartman:
> On Fri, Jul 03, 2015 at 10:53:57AM +0200, Richard Weinberger wrote:
>> On Fri, Jul 3, 2015 at 10:43 AM, David Herrmann <dh.herrmann@gmail.com> wrote:
>>> 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.
>>
>> 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.
> 
> Use your distro's package management system to build a new systemd
> package  based on just adding the single big patch diff from the last
> release to the git head, or pick individual ones.  But really, this
> isn't a kernel issue, you know how to build userspace distro packages...

I hoped some distros already offer such a package. Maybe Fedora?
Building packages is no fun nor trivial.

And IMHO this belongs here as systemd is the only user of kdbus and
kernel folks may want to give it a try.

Thanks,
//richard

  reply	other threads:[~2015-07-03 16:22 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26 19:26 [!GIT PULL] kdbus for 4.2 Greg Kroah-Hartman
2015-06-26 19:33 ` Andy Lutomirski
2015-06-26 19:36   ` Tom Gundersen
2015-06-28  7:51     ` Richard Weinberger
2015-07-03  0:39     ` Andy Lutomirski
2015-07-03  8:43       ` David Herrmann
2015-07-03  8:53         ` Richard Weinberger
2015-07-03 15:27           ` Greg Kroah-Hartman
2015-07-03 16:22             ` Richard Weinberger [this message]
2015-07-03 16:23         ` Andy Lutomirski
2015-06-29 14:10 ` Richard Weinberger
2015-06-29 15:45   ` Greg Kroah-Hartman
2015-06-29 15:47     ` Richard Weinberger
2015-06-30  1:06       ` chunshan.zhu
2015-06-30  6:29         ` Richard Weinberger
2015-07-01 15:55           ` David Herrmann
2015-07-01 16:12             ` Steven Rostedt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5596B6D2.70008@nod.at \
    --to=richard@nod.at \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=daniel@zonque.org \
    --cc=dh.herrmann@gmail.com \
    --cc=ebiederm@xmission.com \
    --cc=gnomes@lxorguk.ukuu.org.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=teg@jklm.no \
    --cc=tixxdz@opendz.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.