Sounds like that app is buggy. You'll need to report this to the app's authors. Thanks!

I have been trying to find the solution too my workaround is I uninstall cloudflare-warp before logout/reboot and reinstall it after

It doesn't make sense, I reinstalled and somehow it worked after a second try. Too random and buggy though. Seems like a previous behavior that happened with Restart.


Why the app is buggy? the DE (or KDE), should enforce to close, regardless, in case it doesnt want to.

Main problem was with logout, that never worked. So, maybe something are missing in KDE logout, to forcefully close if needed. Who knows if KDE are considering all cases. Because the application never caused any problems in the system.


It's a simple tray that can be closed by stopping a user (non-sudo) service. It should not cause issue like this.
systemctl --user stop warp-taskbar 

Seems more like DE problem here, than app.

That's it, pretty much the service keeps respawning the tray. If I press to logout and it hang / doesnt work. As soon as I run the command to stop the service, the logout process continue.

So, the problem are that KDE are not stopping user services to logout, restart and who knows what else. 

That's the bug.

(In reply to dougg0k from comment #4)
> That's it, pretty much the service keeps respawning the tray. If I press to
> logout and it hang / doesnt work. As soon as I run the command to stop the
> service, the logout process continue.
> 
> So, the problem are that KDE are not stopping user services to logout,
> restart and who knows what else. 
> 
> That's the bug.

share the command please and which service did you stop? the `warp-svc`??, I also tried closing the programs running with warp and they kept re spawning. 

just to give more info I am on Endeavour OS. and I had been using gnome warp-cli for about 5 months and didnt have any problem

(In reply to Abdul Rafay Shaikh from comment #5)
> (In reply to dougg0k from comment #4)
> > That's it, pretty much the service keeps respawning the tray. If I press to
> > logout and it hang / doesnt work. As soon as I run the command to stop the
> > service, the logout process continue.
> > 
> > So, the problem are that KDE are not stopping user services to logout,
> > restart and who knows what else. 
> > 
> > That's the bug.
> 
> share the command please and which service did you stop? the `warp-svc`??, I
> also tried closing the programs running with warp and they kept re spawning. 
> 
> just to give more info I am on Endeavour OS. and I had been using gnome
> warp-cli for about 5 months and didnt have any problem

ignore my previous comment I skipped a comment that had the relevant info I was looking for!

A temporary automated solution to this.

Create a bash script:
touch logout.sh

Add the content:
#!/bin/bash
systemctl --user stop warp-taskbar

Make sure it's executable:
chmod +x logout.sh

Open System Settings > Autostart > Add New > Logout Script > Choose logout.sh

Done.

Edit doesnt work here. So, if unable to use the UI.

Here is the location that the script would be.

~/.config/plasma-workspace/shutdown/logout.sh

If the app fails to quit properly when not explicitly stopped using systemctl, that's a bug in the app. In Plasma 6.3, we'll have a notification that tells you about such apps.

Plewase report this to the developers of cloudflare-warp-bin

Not really.

Other apps are also causing the same issue for the same reason.

https://github.com/feschber/lan-mouse/issues/237

The fact that other apps have the same bug doesn't absolve those apps of the responsibility for fixing it.

Does it block forever or block for 90 seconds?

The fact that we're processing the timeout scripts means that from a KDE POV we haven't blocked the logout and are shutting down completely. KDE's stuff has stopped running at this point and we've closed all apps at any sort of application level and have ended the session.

We're then hitting systemd's clearup of stray processes. 

This timeout can be configured with /etc/systemd/user.conf where it has: 
#DefaultTimeoutStopSec=90s

I didnt check, but good to know.

Also note that some distros override this. AFAIK Fedora sets it to 45 seconds while Neon sets it to 5 seconds.

5 seconds seems about the right value to set.

Can you answer David's question? When this happens, does it block logout literally forever, or just until it hits the systemd timeout number?

Just tested.

I didnt uncoment anything in the systemd conf file. 

But if the default were to be 90s, it didnt work. 

Just as the UI stopped working, so did the clock, but only by stopping that service, the logout process continued.

I tried setting DefaultTimeoutStopSec to 5s to make sure. And tried to logout after a reboot. It didnt work.

Only solution at this point

echo 'systemctl --user stop warp-taskbar' | tee ~/.config/plasma-workspace/shutdown/logout.sh && chmod +x ~/.config/plasma-workspace/shutdown/logout.sh

> It didnt work.
What didn't work? The app failed to get terminated after the configured termination duration? Did you try waiting the full 90 seconds anyway?

Please try waiting for two full minutes to see if logout eventually happens at that point in time.

Yes and yes.

I waited for more than 3 minutes.

App does not get terminated, if you kill it, it will just be instantly be respawned, that's why the service need to be stopped.

If that timeout does not stop the user services, that cleanup doesnt do a thing.

Yes, if the app literally restarts itself, then there's nothing even systemd can do. Which makes this *unequivocally* an app bug. It's a really user-hostile behavior for it to re-spawn itself automatically unless you know the magic incantation to disable its systemd service. Please report this to the devs of such apps and ask that they reconsider this behavior.

I can also confirm that no matter how long you wait it does not log out. Even if you kill the program it respawns and doesnt logout `reboot` command works from terminal and the script posted by dougg0k I have been using that and it works! thanks dougg0k