Updating from Thunar 1.7.2 to 1.8.0, `thunar --version` shows 1.8.0, but starting Thunar with `thunar` from the terminal and opening the window *About*, version 1.7.2 is shown. Logging out and back in, version 1.7.2 is shown. So, the version is somehow cached I guess. Do I need to run a command, to clear the cache after the update.
I cannot find any caching on the version-string in the code. The compile-time define PACKAGE_VERSION is used by both, the command line and the "about" dialog. PACKAGE_VERSION is generated into all Makefiles by ./autogen.sh Possibly you did not kill the old running thunar daemon ? Try: thunar -q; thunar You compiled thunar from source ? IS the about dialog correct if you execute thunar out of the source directory? ./thunar/thunar -q; ./thunar/thunar
99% sure there was a daemon of the previous version running, not so sure why it "survives" log out and in. What happens on reboot?
[Sorry, reply by email doesn’t seem to work.] Thank you for looking into this. Re-reading my original report, I screwed up. The correct version 1.8.0 is shown after logging out and back in. Sorry for messing that up. So it’s only cached for one session. I thought I checked with `ps aux | grep thunar`, that nothing runs, but I’ll try again on Monday.
Closing, reopen if you notice this again next time you update thunar.