20.04 update to kernel 5.4.0-71 killed Thunar

[userxub-3498]

Running 20.04 Xubuntu dist with Thunar as file manager. This morning it updated to kernel 5.4.0-71 and now Thunar doesn't launch. booted to 0-70 and it's dead there as well. Booted into 18.04 and it will run but barely and ssssslllllloooooooowwwww.
Booted into 20.04 again, Reinstalled Thunar, nothing.

Update: it opened but 5 minutes after the last try. Works fine once it launches but after booting again the first instance takes 5 minutes?????

Anyone else having this problem?

[CelticWarrior]

What you describe is very unlikely related with updates, especially considering the same problem occurs in different kernels and releases.

Maybe the drive is failing?

[userxub-3498]

There is nothing wrong with the drive. This problem began immediately after the kernel update which corrupted something related to Thunar and that's why it happens across the board.

[CelticWarrior]

Unless the exact update happened "across the board" (it didn't) then it couldn't.

[tea for one]

Running 20.04 Xubuntu dist with Thunar as file manager. This morning it updated to kernel 5.4.0-71 and now Thunar doesn't launch. booted to 0-70 and it's dead there as well. Booted into 18.04 and it will run but barely and ssssslllllloooooooowwwww.
Booted into 20.04 again, Reinstalled Thunar, nothing.

Update: it opened but 5 minutes after the last try. Works fine once it launches but after booting again the first instance takes 5 minutes?????

Anyone else having this problem?

If you start Thunar via the terminal, any error messages?

[ActionParsnip]

If you boot an older kernel is it OK there?

[CelticWarrior]

If you boot an older kernel is it OK there?

Quoting from the OP:

booted to 0-70 and it's dead there as well. Booted into 18.04 and it will run but barely and ssssslllllloooooooowwwww.

Clearly nothing to do with the update itself. Probably a drive failure or is about to fail.

[userxub-3498]

When I try using terminal it reports a timeout exceeded failure. I timed it today after re-booting and it took 12 minutes to open. Once it had run the first time though I can close it and re-launch no problem. The issue only happens after re-boot and only once.

[userxub-3498]

Again, there is nothing wrong with the drive. Thank you for repeating your opinion.

[userxub-3498]

I only have the previous kernel available right now and it does the same thing. Whatever happened during the kernel update affected the file manager everywhere. I may have to reinstall 20.04. Sucks.