On Mon 2017-05-15 19:10:35 -0400, Joey Morris wrote:
> Daniel Kahn Gillmor wrote on Wed, May 10, 2017 at
> 10:58:21PM -0400:
>> On Wed 2017-05-10 22:17:28 -0400, Joey Morris wrote:
>> > I have systemd version 222-1 installed, which appears to be wildly out of
>> > date.
>> > The first thing I'll
Daniel Kahn Gillmor wrote on Wed, May 10, 2017 at
10:58:21PM -0400:
> On Wed 2017-05-10 22:17:28 -0400, Joey Morris wrote:
> > I have systemd version 222-1 installed, which appears to be wildly out of
> > date.
> > The first thing I'll try when I get back to this is to upgrade systemd.
>
> yes,
On Wed 2017-05-10 22:17:28 -0400, Joey Morris wrote:
> I've been using my .xession setup for a number of years, and actually when
> this
> issue came up it was the first I'd heard of systemd user services. (I was
> aware
> of the system-level systemd, just not the user-specific part.) I'll spend
Daniel Kahn Gillmor wrote on Wed, May 10, 2017 at
02:10:27PM -0400:
> One difference i note is that you're using ~/.xsession, and i'm just
> relying on the alternatives system to launch openbox:
>
> 0 dkg@alice:~$ readlink -f $(which x-session-manager)
> /usr/bin/openbox-session
> 0
Hi Joey--
thanks for these details!
On Tue 2017-05-09 21:43:47 -0400, Joey Morris wrote:
> X11 via startx. I run openbox-session at the end of .xsession.
cool, we actually have fairly similar setups -- i'm also running
systemd, debian testing/unstable, with dbus-user-session, and
libpam-systemd
Thanks for thinking about this, Daniel. Answers to your questions below.
Daniel Kahn Gillmor wrote on Tue, May 09, 2017 at
12:38:56PM -0400:
> are you using systemd?
Yes.
> do you have dbus-user-session installed?
I didn't at first, but I do now. I saw the hanging behavior both before and
aft
On Tue 2017-05-09 09:32:43 -0400, Joey Morris wrote:
>
> Thanks Peter, I think this is indeed related to the systemd user sessions.
> Just
> to clarify, did you solve your problem by disabling the systemd units, or did
> you end up getting it working with them?
>
> Checking my apt logs, I upgraded
Hi Joey--
On Mon 2017-05-08 22:34:35 -0400, Joey Morris wrote:
> I've tried several things without figuring out the problem:
>
> - Verified that gpg-agent is running with `pgrep -u "${USER}" gpg-agent`.
> - Restarted gpg-agent with `killall gpg-agent`.
> - Verified that the socket reference
On 09/05/17 15:32, Joey Morris wrote:
> Thanks Peter, I think this is indeed related to the systemd user sessions.
> Just
> to clarify, did you solve your problem by disabling the systemd units, or did
> you end up getting it working with them?
I removed the following symlinks (format: destinatio
Peter Lebbing wrote on Tue, May 09, 2017 at
11:50:33AM +0200:
> Is it possible that this started occuring after upgrading the gnupg
> package? 2.1.17-4 (from 10 Jan) introduced using systemd user sessions
> for gpg-agent and dirmngr by default. When I had this enabled on Debian
> jessie, a connec
On 09/05/17 04:34, Joey Morris wrote:
> I'm running version 2.1.18 on debian sid. Does anyone have thoughts on what
> might be happening or suggestions for additional troubleshooting?
Is it possible that this started occuring after upgrading the gnupg
package? 2.1.17-4 (from 10 Jan) introduced usi
11 matches
Mail list logo
