On 4/18/25 6:20 PM, Darrell Anderson via tde-users wrote:
On 4/18/25 5:34 PM, deloptes via tde-users wrote:
don't you see anything on the screen?
usually a popup with progress bar is displayed that says notifying
applications etc etc and you can choose to kill them all or to wait.
Nothing like that. I never would have posted if there was some kind of
feedback.
I believe I found the root cause.
I long have suspected Firefox taking a long to fully terminate because
many times I have closed Firefox and within a few seconds later
attempted to launch again. I always receive an error dialog that Firefox
is busy. Busy? Busy doing what? I don't know.
I mentioned previously I tend to manually ensure everything is closed
before logging out, but with a few keystrokes that is a quick routine. I
then logout with the keyboard. But Firefox is not done whistling and
farting around.
I looked into that and confirmed Firefox takes about 10 to 12 seconds to
fully terminate. On a 4-core system with an nvme disk.
If I wait 10 to 12 seconds after closing Firefox then I don't see the
logout delay. At least so far I am not seeing the delay.
I long had forgotten about the TDE session logout status dialog. I
enabled that feature and confirmed Firefox is causing the delay.
With the logout status dialog enabled, attempting to logout before
Firefox fully terminates results in a kdebug crash. The backtrace is not
useful because I don't have symbols enabled.
I have no idea why Firefox takes 10 to 12 seconds to fully terminate.
That is WTF territory. Truly.