On Wed, Aug 10, 2016 at 12:12:27AM -0400, Daniel Kahn Gillmor wrote: > So i'm not able to reproduce this behavior. > > Zack, can you help me narrow down how this is happening for you?
Sure, I'll be happy to. But as I mentioned before I wonder if it's worth to do it with my current package mix: I'm using testing, where the GNOME stack seems to be still in flux, apparently), with gnupg2 coming from experimental. I can debug, but I wonder if it'd be a good time investment. Unless you consider this issue potentially blocking for uploading to unstable, I'd rather wait for gnupg2 to land in testing and try again. After all the issue is for a non-default behavior that one should explicitly enabled, right? OTOH if you do consider this a blocker, I'll roll up my sleeves and have a look ASAP :-) > do you have logs of the failed login session someplace, or other details > that might help diagnose? I can look up logs, but I could use some guidance about where the GNOME user session logs are supposed to be. ~/.xsession-errors seems to be obsolete --- or else it hasn't received log entries on my laptop since March 2016, which seems unlikely... Cheers. -- Stefano Zacchiroli . . . . . . . z...@upsilon.cc . . . . o . . . o . o Maître de conférences . . . . . http://upsilon.cc/zack . . . o . . . o o Former Debian Project Leader . . . . . @zacchiro . . . . o o o . . . o . « the first rule of tautology club is the first rule of tautology club »