Bug#846377: discovered likely cause of this issue

2018-03-08 Thread Dirk Heinrichs
Am 08.03.2018 um 12:11 schrieb Michael Biebl:

> Dirk, can you confirm that adding pam_keyinit.so to
> /etc/pam.d/systemd-user solves the problem for you as well? 

No, it doesn't. After adding it and logging out and back in I still get
this:

% keyctl show @s
Keyring
 918482795 ---lswrv  0 0  keyring: _ses.20321
  92578899 s--v  0 0   \_ afs_pag: _pag

and, for example:

% systemctl --user enable syncthing
Failed to enable unit: Access denied

However, I got the hint in the related systemd issue
<https://github.com/systemd/systemd/issues/7261#issuecomment-370509405>,
that it might be possible to solve this in AFS, by using the user
keyring instead of the session keyring. Will start a discussion on this
on openafs-info soon...

Bye...

    Dirk

-- 
Dirk Heinrichs <dirk.heinri...@altum.de>
GPG Public Key: D01B367761B0F7CE6E6D81AAD5A2E54246986015
Sichere Internetkommunikation: http://www.retroshare.org
Privacy Handbuch: https://www.privacy-handbuch.de



signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#846377: Solved (or worked around) the problem

2016-12-03 Thread Dirk Heinrichs
Hi,

I've meanwhile found a solution(?): After removing package
dbus-user-session and logging out and back in again the problem was
gone. However, I  don't know whether that is a real solution or just a
workaround.

Package description, for reference:
dbus-user-session - simple interprocess messaging system (systemd --user
integration)

Bye...

Dirk

-- 
Dirk Heinrichs <dirk.heinri...@altum.de>
GPG Public Key CB614542 | Jabber: dirk.heinri...@altum.de
Sichere Internetkommunikation: http://www.retroshare.org
Privacy Handbuch: https://www.privacy-handbuch.de

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers


Bug#846377: [systemd] /lib/systemd/systemd --user starts dbus-daemon without AFS token

2016-12-02 Thread Dirk Heinrichs
Am 01.12.2016 um 18:12 schrieb Benjamin Kaduk:
> I think that the KRB5CCNAME thing is only expected to help when combined
> with a change to run libpam-afs-session from common-session-noninteractive
> instead of common-session only.

On my system, configured with pam-auth-update (so no manual changes),
it's in both.

Bye...

Dirk

-- 
Dirk Heinrichs <dirk.heinri...@altum.de>
GPG Public Key CB614542 | Jabber: dirk.heinri...@altum.de
Tox: he...@toxme.se
Sichere Internetkommunikation: http://www.retroshare.org
Privacy Handbuch: https://www.privacy-handbuch.de

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers


Bug#846377: [systemd] /lib/systemd/systemd --user starts dbus-daemon without AFS token

2016-12-01 Thread Dirk Heinrichs
Am 01.12.2016 um 12:35 schrieb Michael Biebl:

> Dirk, could run
> systemctl --user import-environment KRB5CCNAME
> systemctl --user restart dbus.service dbus.socket
> then kill the running dconf-service process and see if it restarts with
> the correct context

Sure. Doesn't seem to help. Started evolution from the same shell
afterwards and got the same error as before.

Bye...

    Dirk

-- 
Dirk Heinrichs <dirk.heinri...@altum.de>
GPG Public Key CB614542 | Jabber: dirk.heinri...@altum.de
Tox: he...@toxme.se
Sichere Internetkommunikation: http://www.retroshare.org
Privacy Handbuch: https://www.privacy-handbuch.de

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers


Bug#846377: [systemd] /lib/systemd/systemd --user starts dbus-daemon without AFS token

2016-12-01 Thread Dirk Heinrichs
Am 30.11.2016 um 21:42 schrieb Benjamin Kaduk:

> I have not absorbed the full report yet, but wanted to note that Dave Botsch 
> (IIRC)
> put together some notes on using AFS with systemd --user at:
> https://docs.google.com/document/d/1P27fP1uj-C8QdxDKMKtI-Qh00c5_9zJa4YHjnpB6ODM/pub

Will take a look, thanks.

Bye...

    Dirk

-- 
Dirk Heinrichs <dirk.heinri...@altum.de>
GPG Public Key CB614542 | Jabber: dirk.heinri...@altum.de
Tox: he...@toxme.se
Sichere Internetkommunikation: http://www.retroshare.org
Privacy Handbuch: https://www.privacy-handbuch.de

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers


Bug#846377: [systemd] /lib/systemd/systemd --user starts dbus-daemon without AFS token

2016-11-30 Thread Dirk Heinrichs
Package: systemd
Version: 232-6
Severity: important

--- Please enter the report below this line. ---
I'm running systems with user home directories located in an OpenAFS
network filesystem. This used to work fine for years. However, since
some time now, some desktop environments/applications (KDE, Evolution,
etc.) have trouble writing their config files, while writing to the
same file from within a shell worked fine.

I did some investigation and found out that dbus-daemon is not started
be the pam-authenticated user session anymore, but
via /lib/systemd/systemd --user.

This in itself wouldn't be a problem, but /lib/systemd/systemd --user
has been started by PID 1 and thus doesn't run with an AFS token, which
means that all processes spawned from it don't have one either:

testuser 2013 1  0 18:54 ?00:00:00 /lib/systemd/systemd
--user
testuser 2015  2013  0 18:54 ?00:00:00 (sd-pam)
testuser 7783  2013  0 19:29 ?00:00:01 /usr/bin/dbus-daemon
--session --address=systemd: --nofork --nopidfile --systemd-activation

This means that any application that wants to access files through dbus
fails to do so, for example:

(evolution:9447): dconf-WARNING **: failed to commit changes to dconf:
GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dfile_2derror_2dquark.Code2:
Cannot open dconf database: Failed to open file
'/afs/altum.de/home/testuser/.config/dconf/user': Permission denied

To verify, I added an AFS ACL entry to each sub-directory of testuser's
home, which allowed write access for system:anyuser. Afterwards, the
errors were gone.

Of course, it's not a solution to grant unauthenticated
users write access to every user's home directory.

So, in it's current form, this setup makes most desktop environments
simply unusable.

--- System information. ---
Architecture: Kernel:   Linux 4.8.0-1-amd64

Debian Release: stretch/sid
  990 testing www.deb-multimedia.org   990 testing
ftp.de.debian.org   500 syncthing   apt.syncthing.net   500 stable
update.devolo.com   500 stable  repo.saltstack.com
--- Package information. ---
Depends   (Version) | Installed
===-+-=
libacl1   (>= 2.2.51-8) | 2.2.52-3
libapparmor1  (>= 2.9.0-3+exp2) | 2.10.95-6
libaudit1  (>= 1:2.2.1) | 1:2.6.7-1
libblkid1   (>= 2.19.1) | libc6
(>= 2.17) | libcap2 (>= 1:2.10) |
libcryptsetup4 (>= 2:1.4.3) | libgcrypt20
   (>= 1.7.0) | libgpg-error0 (>= 1.14) |
libidn11  (>= 1.13) | libip4tc0
  | libkmod2(>= 5~) |
liblz4-1  (>= 0.0~r127) | liblzma5   (>=
5.1.1alpha+20120614) | libmount1   (>= 2.26.2) |
libpam0g  (>= 0.99.7.1) | libseccomp2
   (>= 2.3.1) | libselinux1  (>= 2.1.9) |
libsystemd0   (= 232-6) | util-linux
  (>= 2.27.1) | mount (>= 2.26) |
adduser |

Package Status   (Version) | Installed
==-+-===
udev   | 232-6
dracut | initramfs-tools| 0.125


Recommends  (Version) | Installed
=-+-===
libpam-systemd| 232-6
dbus  | 1.10.12-1


Suggests   (Version) | Installed
-+-===
systemd-ui   | systemd-container| 232-6
policykit-1  | 0.105-17



--- Output from package bug script ---




-- 
Dirk Heinrichs <dirk.heinri...@altum.de>
GPG Public Key CB614542 | Jabber: dirk.heinri...@altum.de
Tox: he...@toxme.se
Sichere Internetkommunikation: http://www.retroshare.org
Privacy Handbuch: https://www.privacy-handbuch.de

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers


Bug#809408: [systemd] systemctl -a: Failed to list units: No such method 'ListUnitsFiltered'

2015-12-31 Thread Dirk Heinrichs
Am Donnerstag 31 Dezember 2015, 00:42:56 schrieb Michael Biebl:

> Control: tags -1 moreinfo unreproducible
> 
> Am 30.12.2015 um 13:26 schrieb Dirk Heinrichs:
> > Package: systemd
> > Version: 228-2+b1
> > Severity: important
> > 
> > 
> > Debian Release: stretch/sid
> > 
> > --- Package information. ---
> > libsystemd0 (= 215-5+b1) |
> 
> systemctl -a works fine here (on v228)
> 
> You seem to be mixing different versions. I'm unsure how you managed to
> do that, given that systemd has a strictly versioned dependency on
> libsystemd. Are the versions in this bug report correct?

Didn't recognize that. But no, that's not correct, don't know where that 
version comes from.

# dpkg --list|grep systemd 
ii  libpam-systemd:amd64  228-2+b1  
 
amd64system and service manager - PAM module
ii  libsystemd0:amd64 228-2+b1  
 
amd64systemd utility library
ii  libsystemd0:i386  228-2+b1  
 
i386 systemd utility library
ii  python-systemd231-2 
 
amd64Python 2 bindings for systemd
ii  systemd   228-2+b1  
 
amd64system and service manager
ii  systemd-sysv  228-2+b1  
 
amd64    system and service manager - SysV links

Bye...

Dirk
-- 
Dirk Heinrichs <dirk.heinri...@altum.de>
GPG Public Key CB614542 | Jabber: dirk.heinri...@altum.de
Tox: he...@toxme.se
Sichere Internetkommunikation: http://www.retroshare.org
Privacy Handbuch: https://www.privacy-handbuch.de


signature.asc
Description: This is a digitally signed message part.
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#809408: Error message changed after reinstalling systemd packages

2015-12-31 Thread Dirk Heinrichs
Am Donnerstag 31 Dezember 2015, 14:16:52 schrieben Sie:

> Am 31.12.2015 um 10:57 schrieb Dirk Heinrichs:
> > I've meanwhile reinstalled all systemd-related packages. It still doesn't
> > work, but I get a different error message now:
> > 
> > # systemctl -a
> > Failed to list units: Launch helper exited with unknown return code 1
> 
> Are you sure systemd is your active PID 1?

Aaargh, it wasn't. Don't know why, somehow the "init=/bin/systemd" part 
disappeared from my kernel command line. dpkg-reconfigure'd grub-pc to add it 
again and rebooted. Everything's fine again.

> Do you have systemd-sysv installed?

Yes, I do.

Anyway, works again. Can be closed.

Thanks a lot and sorry for the fuzz.

Bye...

Dirk
-- 
Dirk Heinrichs <dirk.heinri...@altum.de>
GPG Public Key CB614542 | Jabber: dirk.heinri...@altum.de
Tox: he...@toxme.se
Sichere Internetkommunikation: http://www.retroshare.org
Privacy Handbuch: https://www.privacy-handbuch.de


signature.asc
Description: This is a digitally signed message part.
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#809408: Error message changed after reinstalling systemd packages

2015-12-31 Thread Dirk Heinrichs
I've meanwhile reinstalled all systemd-related packages. It still doesn't 
work, but I get a different error message now:

# systemctl -a
Failed to list units: Launch helper exited with unknown return code 1

Bye...

Dirk
-- 
Dirk Heinrichs <dirk.heinri...@altum.de>
GPG Public Key CB614542 | Jabber: dirk.heinri...@altum.de
Tox: he...@toxme.se
Sichere Internetkommunikation: http://www.retroshare.org
Privacy Handbuch: https://www.privacy-handbuch.de


signature.asc
Description: This is a digitally signed message part.
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#809408: [systemd] systemctl -a: Failed to list units: No such method 'ListUnitsFiltered'

2015-12-30 Thread Dirk Heinrichs
Package: systemd
Version: 228-2+b1
Severity: important

--- Please enter the report below this line. ---
See subject, cannot list units anymore.

--- System information. ---
Architecture: amd64
Kernel:   Linux 4.3.0-1-amd64

Debian Release: stretch/sid
  990 testing www.deb-multimedia.org 
  990 testing security.debian.org 
  990 testing ftp.de.debian.org 
  500 utopic  ppa.launchpad.net 
  500 unstabledownload.jitsi.org 
  500 stable  update.devolo.com 
  500 nightly pkg.tox.chat 

--- Package information. ---
Depends(Version) | Installed
-+-==
libacl1(>= 2.2.51-8) | 2.2.52-2
libaudit1   (>= 1:2.2.1) | 1:2.4.4-4
libblkid1(>= 2.19.1) | 2.27.1-1
libcap2  (>= 1:2.10) | 1:2.24-12
libcryptsetup4  (>= 2:1.4.3) | 2:1.6.6-5
libkmod2 (>= 5~) | 21-1
libpam0g   (>= 0.99.7.1) | 1.1.8-3.1
libselinux1   (>= 2.1.9) | 
libsystemd0 (= 215-5+b1) | 
util-linux (>= 2.19.1-2) | 
initscripts(>= 2.88dsf-53.2) | 
sysv-rc  | 
udev | 
acl  | 
adduser  | 
libcap2-bin  | 


Package Status  (Version) | Installed
=-+-===
udev  | 228-2+b1


Recommends  (Version) | Installed
=-+-===
libpam-systemd| 228-2+b1
dbus  | 1.10.6-1


Suggests(Version) | Installed
=-+-===
systemd-ui| 



--- Output from package bug script ---
-- 
Dirk Heinrichs <dirk.heinri...@altum.de>
GPG Public Key CB614542 | Jabber: dirk.heinri...@altum.de
Tox: he...@toxme.se
Sichere Internetkommunikation: http://www.retroshare.org
Privacy Handbuch: https://www.privacy-handbuch.de


signature.asc
Description: This is a digitally signed message part.
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers