-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Mon, 2018-12-17 at 11:23 -0400, Joey Hess wrote: > Yves-Alexis Perez wrote: > > Hi Joey, sorry I missed your bug. > > > > So after the upgrade, Thunar couldn't reach the daemon. Before removing > > .cache/sessions/xfce4-session-* did you try to quit the Thunar daemon > > (thunar > > - -q or restarting the session)? Did it change anything? > > I may have tried to kill it manually so no thunar processes were running > and then ran thunar.
So with no Thunar process running at all, running a new Thunar process would lead to the “timeout” message? > > > Is the daemon correctly running right now? > > Yes, I've rebooted since and it's working. But only after removing the .cache/session/xfce4-session-* files? Or did it work without? I'm trying to understand if it's just the “normal” issue of some Thunar upgrade where the protocol between daemon and process has changed and thus it's not possible to call the “old” Thunar daemon with the “new” thunar binary or if it is something different. Regards, - -- Yves-Alexis -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEE8vi34Qgfo83x35gF3rYcyPpXRFsFAlwXw8gACgkQ3rYcyPpX RFubaAf/aaBft5i3vYE88n3jlVbAc4pPTPQvFM331hDVo4CFyqVPxAkNbdW3cvP8 M0o7HzY9Uzo+0BcdjYAyRuyIRF7MAqL3U9qVS3IMDBsVOi9c9E00OtTZPHbgldsF hg/pJB/LcjXA5WoK4HYqDJQ4LnATmAbITOYSu/jpuW+nEkG1uBfykWGbu3F8y9Z8 JjeSc9m4fBSo5uyQ/TbURRG2JzPGYFZWaltRNR5di37LUDqjDOsT6boySN+NszbY SlmBPu6yQoObmFxhl24VpZbsGIN4ZWtGE3GsPrjmRyJUXAZ/rf244GzTNLulblOc IIcX0oJGQ9KZQU9UZ1kzFOCa+d+Tsg== =nuWf -----END PGP SIGNATURE-----
