[systemd-devel] Failed to apply ACLs: Invalid argument

2017-07-18 Thread Matwey V. Kornilov 
Hello,

I am running systemd 228. And one one particular system installation
there are messages 'Failed to apply ACLs: Invalid argument' from
systemd-logind. Moreover, ACL on /dev/dri/* are not set correctly
after user log in. How could I figure out which argument is invalid?
Managing ACLs on /dev filesystem using setfacl works fine. I've tried
using debug log_level, but nothing helpful here:


июл 18 16:21:00 photon systemd-logind[12814]: Got message
type=method_call sender=:1.59 destination=org.freedesktop.login1 obj
ect=/org/freedesktop/login1 interface=org.freedesktop.login1.Manager
member=CreateSession cookie=2 reply_cookie=0 error=n/a
июл 18 16:21:00 photon systemd-logind[12814]: Sent message
type=method_call sender=n/a destination=org.freedesktop.DBus object
=/org/freedesktop/DBus interface=org.freedesktop.DBus
member=GetConnectionUnixUser cookie=108 reply_cookie=0 error=n/a
июл 18 16:21:00 photon systemd-logind[12814]: Got message
type=method_return sender=org.freedesktop.DBus destination=:1.53 obj
ect=n/a interface=n/a member=n/a cookie=33 reply_cookie=108 error=n/a
июл 18 16:21:00 photon systemd-logind[12814]: Sent message type=signal
sender=n/a destination=n/a object=/org/freedesktop/logi
n1/seat/seat0 interface=org.freedesktop.DBus.Properties
member=PropertiesChanged cookie=109 reply_cookie=0 error=n/a
июл 18 16:21:00 photon systemd-logind[12814]: Sent message
type=method_call sender=n/a destination=org.freedesktop.systemd1
object=/org/freedesktop/systemd1
interface=org.freedesktop.systemd1.Manager member=StartTransientUnit
cookie=110 reply_cookie=0 error=n/a
июл 18 16:21:00 photon systemd-logind[12814]: Got message
type=method_return sender=:1.0 destination=:1.53 object=n/a
interface=n/a member=n/a cookie=2075 reply_cookie=110 error=n/a
июл 18 16:21:00 photon systemd-logind[12814]: New session 6 of user matwey.
июл 18 16:21:00 photon systemd-logind[12814]: VT changed to 7
июл 18 16:21:00 photon systemd-logind[12814]: Sent message type=signal
sender=n/a destination=n/a object=/org/freedesktop/login1/session/_35
interface=org.freedesktop.DBus.Properties member=PropertiesChanged
cookie=111 reply_cookie=0 error=n/a
июл 18 16:21:00 photon systemd-logind[12814]: Failed to apply ACLs:
Invalid argument
июл 18 16:21:00 photon systemd-logind[12814]: Electing new display for
user matwey
июл 18 16:21:00 photon systemd-logind[12814]: Choosing session 6 in
preference to 4
июл 18 16:21:00 photon systemd-logind[12814]: Ignoring session 2
июл 18 16:21:00 photon systemd-logind[12814]: Sent message type=signal
sender=n/a destination=n/a object=/org/freedesktop/login1
interface=org.freedesktop.login1.Manager member=SessionNew cookie=112
reply_cookie=0 error=n/a
июл 18 16:21:00 photon systemd-logind[12814]: Sent message type=signal
sender=n/a destination=n/a object=/org/freedesktop/login1/user/_1001
interface=org.freedesktop.DBus.Properties member=PropertiesChanged
cookie=113 reply_cookie=0 error=n/a
июл 18 16:21:00 photon systemd-logind[12814]: Sent message type=signal
sender=n/a destination=n/a object=/org/freedesktop/login1/seat/seat0
interface=org.freedesktop.DBus.Properties member=PropertiesChanged
cookie=114 reply_cookie=0 error=n/a
июл 18 16:21:00 photon systemd-logind[12814]: Got message type=signal
sender=:1.0 destination=n/a object=/org/freedesktop/systemd1
interface=org.freedesktop.systemd1.Manager member=JobRemoved
cookie=2078 reply_cookie=0 error=n/a
июл 18 16:21:00 photon systemd-logind[12814]: Sending reply about
created session: id=6 object_path=/org/freedesktop/login1/session/_36
uid=1001 runtime_path=/run/user/1001 session_fd=22 seat=seat0 vtnr=7
июл 18 16:21:00 photon systemd-logind[12814]: Sent message
type=method_return sender=n/a destination=:1.59 object=n/a
interface=n/a member=n/a cookie=115 reply_cookie=2 error=n/a

-- 
With best regards,
Matwey V. Kornilov
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] no user dbus session in container

2017-07-18 Thread Simon McVittie 
On Fri, 14 Jul 2017 at 12:36:12 +, arnaud gaboury wrote:
> After upgrade from Fedora 25 to 26, there is no more user dbus session for 
> user
> in container.
...
> On container, user can't connect to dbus session, and I have no idea why.
> May someone please give me some hints on how to debug this issue?

Please start by reading the system log (the Journal).

The chain of events that is meant to result in a D-Bus session bus is:

* A user logging in (somehow) starts a login session
* The login session starts an instance of `systemd --user`
* `systemd --user` starts the dbus.socket user service, listening on
  that user's $XDG_RUNTIME_DIR/bus
* Some client in the login session interacts with the session bus
* As a side-effect of connecting to $XDG_RUNTIME_DIR/bus,
  `systemd --user` starts the dbus.service user service
  (dbus-daemon --session --address=systemd:)
* The dbus-daemon accepts the client's connection

The system log should tell you which step in that chain of events is
no longer happening.

S
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] /etc/systemd/system/default.target.wants/ no longer checked for unit files

2017-07-18 Thread Jérémy Rosen 



On 16/07/2017 16:33, Lennart Poettering wrote:

On Fri, 14.07.17 10:13, Richard W.M. Jones (rjo...@redhat.com) wrote:


https://github.com/systemd/systemd/issues/6334

Since this commit
https://github.com/systemd/systemd/commit/2d058a87ffb2d31a50422a8aebd119bbb4427244
(in v233 and v234), you can no longer create
/etc/systemd/system/default.target.wants/ and drop in service files
(or symlinks).  The directory is skipped.  I have reverted the commit
on top of systemd from git and that makes defaults.target.wants work
again.

Is this supposed to work?  It worked fine since at least Fedora 18-25,
but it is now broken in Fedora 26.

The new code in systemd is simply broken, and we really need to fix
this. The old behaviour was correct.

can I ask a more generic question ?

How should alias and drop-in work ? for all intent and purpose, 
default.target is an alias for multi-user.target (or other)


should alias drop-ins be loaded when we start an alias but not the main 
names ? should all drop-ins from all alias be used ? only the one for 
the one we call ? should we skip drop-ins for the  main name ?


afaik this is an interesting question that is not documented anywhere...

Jérémy

Lennart



--
Logo 

20 rue des Jardins
92600 Asnières-sur-Seine
www.smile.fr    
*Jérémy ROSEN*
Architecte technique
Email : jeremy.ro...@smile.fr 
Tel : +33141402967

Facebook  Google%2B 
 LinkedIn 
 Twitter 




bandeaux_mail 



eco Pour la planète, n'imprimez ce mail que si c'est nécessaire
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel