I encountered a similar problem when upgrading from stable xbindkeys (1.8.3-1) to 1.8.5-1
In previous versions there is no file /etc/X11/Xsession.d/98xbindkeys, thus the usual user (like me) starts xbindkeys in the session startup (xinitrc, autostart et al) manually. After the upgrade xbindkeys is started automatically, so now two xbindkey processes are in the system, with the one started by Xsession.d taking precedence (as least for me). I needed half a day to identify this issue, because the processes spawned from Xsession's xbindkey lack some enviroment variables - like the ones set by ssh-agent during Xsession startup. Proposed solution: a.) Inform the user during upgrade about this change (and the risk of breaking ssh-agent et al) so they can manually disable either their call of xbindkey or the one from Xsession.d b.) Do not use the Xsession.d mechanism per default, inform the user to enable it at their own risk. Regards! -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
