Hello there,
I'm affected with this as well. I've just run into this issue with a testing
virtual machine. It looks like to me that it is also the cause of mate-panel
not starting up along with dconf not being able to create a database in case of
a user with AFS home directory. Speaking of
Michael Biebl writes:
> So I guess we are kind of stuck here and I don't know enough of AFS to
> move this forward (and I don't have a setup to test anything). Are we
> (Debian the distro) really the first to run into this issue? Maybe
> there is some work we can steal from
Am 02.12.2016 um 22:18 schrieb Russ Allbery:
> Dirk Heinrichs writes:
>> 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
>>>
Hello Dirk,
sorry, I haven't had time to dive into this, but I did notice that
we don't put pam_env.so into /etc/pam.d/systemd-user. Does that help
by any chance?
Martin
--
Martin Pitt| http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer
Dirk Heinrichs writes:
> 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
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
On Thu, Dec 01, 2016 at 05:50:33PM +0100, Dirk Heinrichs wrote:
> 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
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
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
Am 01.12.2016 um 04:15 schrieb Russ Allbery:
> Benjamin Kaduk writes:
>> On Wed, Nov 30, 2016 at 08:55:02PM -0300, Felipe Sateler wrote:
>
>>> Well, this command imports an environment variable from the current
>>> environment into the systemd --user one. Therefore, it would need
Benjamin Kaduk writes:
> On Wed, Nov 30, 2016 at 08:55:02PM -0300, Felipe Sateler wrote:
>> Well, this command imports an environment variable from the current
>> environment into the systemd --user one. Therefore, it would need to be
>> run after each time that environment
On Wed, Nov 30, 2016 at 08:55:02PM -0300, Felipe Sateler wrote:
> On 30 November 2016 at 20:39, Russ Allbery wrote:
> >
> > Apologies for my lack of knowledge of systemd in user mode -- it's really
> > neat but I haven't had a chance to play with it yet. Who would run this
> >
On 30 November 2016 at 20:39, Russ Allbery wrote:
> Felipe Sateler writes:
>> On 30 November 2016 at 19:20, Michael Biebl wrote:
>>> Am 30.11.2016 um 23:12 schrieb Russ Allbery:
>
Anyway, it certainly could be registered in
On Wed, Nov 30, 2016 at 07:31:24PM -0300, Felipe Sateler wrote:
>
> `systemctl --user import-environment KRB5CCNAME` might be more
> appropriate if this variable should be copied from an already existing
> environment.
But when would this run, and what package would be responsible for causing
it
Felipe Sateler writes:
> On 30 November 2016 at 19:20, Michael Biebl wrote:
>> Am 30.11.2016 um 23:12 schrieb Russ Allbery:
>>> Anyway, it certainly could be registered in -noninteractive (there was
>>> some reason why I didn't do that), but I think the
On 30 November 2016 at 19:20, Michael Biebl wrote:
> Am 30.11.2016 um 23:12 schrieb Russ Allbery:
>> Anyway, it certainly could be registered in -noninteractive (there was
>> some reason why I didn't do that), but I think the Kerberos ticket cache
>> problem will still be an
Am 30.11.2016 um 23:20 schrieb Michael Biebl:
> Am 30.11.2016 um 23:12 schrieb Russ Allbery:
>> It's a little weird to me that systemd --user loads
>> common-session-interactive and then apparently starts xterms in this
>> particular situation. Those are kind of interactive. But presumably it's
Am 30.11.2016 um 23:12 schrieb Russ Allbery:
> It's a little weird to me that systemd --user loads
> common-session-interactive and then apparently starts xterms in this
> particular situation. Those are kind of interactive. But presumably it's
> assuming xterm will open its own interactive
Felipe Sateler writes:
> On 30 November 2016 at 17:30, Russ Allbery wrote:
>> I don't suppose there's any way to get systemd --user to open a PAM
>> session on behalf of the user before starting to run programs? That
>> would probably solve the problem
On 30 November 2016 at 17:30, Russ Allbery wrote:
>
> Michael Biebl writes:
>
> > Should we assign this to openafs? Is there something which needs to be
> > done on the systemd side, and if so, further information and help would
> > be welcome.
>
> I don't
Am 30.11.2016 um 21:42 schrieb Benjamin Kaduk:
> On Wed, Nov 30, 2016 at 09:11:58PM +0100, Michael Biebl wrote:
>> Am 30.11.2016 um 20:01 schrieb Dirk Heinrichs:
>>
>> Afaics, this will affect any service which was started as a systemd
>> --user service. dbus is just one of them.
>
> I have not
On Wed, Nov 30, 2016 at 09:11:58PM +0100, Michael Biebl wrote:
> Am 30.11.2016 um 20:01 schrieb Dirk Heinrichs:
>
> Afaics, this will affect any service which was started as a systemd
> --user service. dbus is just one of them.
I have not absorbed the full report yet, but wanted to note that
Michael Biebl writes:
> Should we assign this to openafs? Is there something which needs to be
> done on the systemd side, and if so, further information and help would
> be welcome.
I don't suppose there's any way to get systemd --user to open a PAM
session on behalf of the
Am 30.11.2016 um 20:01 schrieb 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,
Am 30.11.2016 um 20:01 schrieb 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,
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
26 matches
Mail list logo