Re: [systemd-devel] pam_limits: Could not set limit for ...: Operation not permitted

2015-02-22 Thread Kai Krakow
Kai Krakow schrieb: >>> But now I got a new message in the log: >>> Unable to autolaunch a dbus-daemon without a $DISPLAY for X11 >> >> Hmm, maybe Gentoo ships some dbus hookup for systemd user sessions >> that triggers this? > > It's triggered by gnome-keyring-daemon... I already set DISPLAY=:0

Re: [systemd-devel] pam_limits: Could not set limit for ...: Operation not permitted

2015-02-11 Thread Kai Krakow
Lennart Poettering schrieb: > On Wed, 11.02.15 20:05, Kai Krakow (hurikha...@gmail.com) wrote: > >> Lennart Poettering schrieb: >> >> > On Tue, 10.02.15 22:28, Kai Krakow (hurikha...@gmail.com) wrote: >> > >> >> This is the plain Gentoo kernel 3.18.6 for desktop, nothing special >> >> except

Re: [systemd-devel] pam_limits: Could not set limit for ...: Operation not permitted

2015-02-11 Thread Lennart Poettering
On Wed, 11.02.15 20:05, Kai Krakow (hurikha...@gmail.com) wrote: > Lennart Poettering schrieb: > > > On Tue, 10.02.15 22:28, Kai Krakow (hurikha...@gmail.com) wrote: > > > >> This is the plain Gentoo kernel 3.18.6 for desktop, nothing special > >> except BFQ patches (applied by the Gentoo kerne

Re: [systemd-devel] pam_limits: Could not set limit for ...: Operation not permitted

2015-02-11 Thread Kai Krakow
Lennart Poettering schrieb: > On Tue, 10.02.15 22:28, Kai Krakow (hurikha...@gmail.com) wrote: > >> This is the plain Gentoo kernel 3.18.6 for desktop, nothing special >> except BFQ patches (applied by the Gentoo kernel package itself, not >> manually patched). I'm pretty sure Gentoo does not ap

Re: [systemd-devel] pam_limits: Could not set limit for ...: Operation not permitted

2015-02-11 Thread Kai Krakow
Andrei Borzenkov schrieb: > В Tue, 10 Feb 2015 22:28:23 +0100 > Kai Krakow пишет: > >> Lennart Poettering schrieb: >> >> > On Tue, 10.02.15 20:16, Kai Krakow (hurikha...@gmail.com) wrote: >> > >> >> Then the question is: Why or what does try to start a user session in >> >> the first place?

Re: [systemd-devel] pam_limits: Could not set limit for ...: Operation not permitted

2015-02-11 Thread Lennart Poettering
On Tue, 10.02.15 22:28, Kai Krakow (hurikha...@gmail.com) wrote: > This is the plain Gentoo kernel 3.18.6 for desktop, nothing special except > BFQ patches (applied by the Gentoo kernel package itself, not manually > patched). I'm pretty sure Gentoo does not apply any special extra patches. > A

Re: [systemd-devel] pam_limits: Could not set limit for ...: Operation not permitted

2015-02-10 Thread Andrei Borzenkov
В Tue, 10 Feb 2015 22:28:23 +0100 Kai Krakow пишет: > Lennart Poettering schrieb: > > > On Tue, 10.02.15 20:16, Kai Krakow (hurikha...@gmail.com) wrote: > > > >> Then the question is: Why or what does try to start a user session in the > >> first place? I don't think KDE does this as it's not

Re: [systemd-devel] pam_limits: Could not set limit for ...: Operation not permitted

2015-02-10 Thread Kai Krakow
Lennart Poettering schrieb: > On Tue, 10.02.15 20:16, Kai Krakow (hurikha...@gmail.com) wrote: > >> Then the question is: Why or what does try to start a user session in the >> first place? I don't think KDE does this as it's not there yet (at least >> in KDE 4.x). And I didn't enable a user@...

Re: [systemd-devel] pam_limits: Could not set limit for ...: Operation not permitted

2015-02-10 Thread Lennart Poettering
On Tue, 10.02.15 20:16, Kai Krakow (hurikha...@gmail.com) wrote: > Then the question is: Why or what does try to start a user session in the > first place? I don't think KDE does this as it's not there yet (at least in > KDE 4.x). And I didn't enable a user@...service (but shouldn't it work then

Re: [systemd-devel] pam_limits: Could not set limit for ...: Operation not permitted

2015-02-10 Thread Kai Krakow
Lennart Poettering schrieb: > On Tue, 10.02.15 08:42, Kai Krakow (hurikha...@gmail.com) wrote: > >> >> Dez 15 22:33:57 jupiter systemd[1515]: >> >> pam_limits(systemd-user:session): Could not set limit for 'memlock': >> >> Operation not permitted Dez 15 22:33:57 jupiter systemd[1515]: >> >> pam_

Re: [systemd-devel] pam_limits: Could not set limit for ...: Operation not permitted

2015-02-10 Thread Lennart Poettering
On Tue, 10.02.15 08:42, Kai Krakow (hurikha...@gmail.com) wrote: > >> Dez 15 22:33:57 jupiter systemd[1515]: pam_limits(systemd-user:session): > >> Could not set limit for 'memlock': Operation not permitted > >> Dez 15 22:33:57 jupiter systemd[1515]: pam_limits(systemd-user:session): > >> Could no

Re: [systemd-devel] pam_limits: Could not set limit for ...: Operation not permitted

2015-02-09 Thread Kai Krakow
Lennart Poettering schrieb: > On Mon, 15.12.14 22:42, Kai Krakow (hurikha...@gmail.com) wrote: > >> Hello! >> >> I'm seeing the following errors in systemd's journal: >> >> Dez 15 22:33:57 jupiter systemd[1515]: pam_limits(systemd-user:session): >> Could not set limit for 'memlock': Operation

Re: [systemd-devel] pam_limits: Could not set limit for ...: Operation not permitted

2015-02-03 Thread Lennart Poettering
On Mon, 15.12.14 22:42, Kai Krakow (hurikha...@gmail.com) wrote: > Hello! > > I'm seeing the following errors in systemd's journal: > > Dez 15 22:33:57 jupiter systemd[1515]: pam_limits(systemd-user:session): > Could not set limit for 'memlock': Operation not permitted > Dez 15 22:33:57 jupiter

[systemd-devel] pam_limits: Could not set limit for ...: Operation not permitted

2014-12-15 Thread Kai Krakow
Hello! I'm seeing the following errors in systemd's journal: Dez 15 22:33:57 jupiter systemd[1515]: pam_limits(systemd-user:session): Could not set limit for 'memlock': Operation not permitted Dez 15 22:33:57 jupiter systemd[1515]: pam_limits(systemd-user:session): Could not set limit for 'nice