How to disable "Akregator did not close correctly" screen?

Help
1

Is there a way to disable the “Akregator did not close correctly. Would you like to restore the previous session?” screen?

I use Akregator as my main RSS reader, but one thing that’s been a little pet peeve is that I never manually close background tasks like Akregator, etc, when turning off my PC. This leads to the did not close correctly screen coming up every time I turn on my PC.

I looked around for a setting to disable that screen, but I couldn’t find any. It’s no big deal as I can just click do not restore session every time, but I’d rather not have to if possible.

1 Like
2

Im having the same issue, seems it’s not closing properly when shutting down the PC.

Akregator: 5.24.4 (23.08.4)
Plasma: 5.27.10
Frameworks: 5.113.0
Qt: 5.15.11
Wayland
3

There’s a bugzilla report open for it (#445351), but it doesn’t have any help in it, unfortunately.

4

There are two fixes currently available, but both are cumbersome:

  1. File → Quit when you’re done using it.
  2. Getting the Akregator developers to close the application rather than close to tray or at least give the user the option to not make it close to tray.
5

Hi! I’ve run into the same issue, and yes, the only thing I’d add there is that Ctrl+Q on the keyboard also works and, for me, was a bit faster than navigating the menus.

1 Like
6

Hi,

this thing has been bothering me for years but every time I opened up the source code, I realised that it is quite a bit over my head for a cosy evening. :frowning:

The issue is that Akregator recognises a crash when you log out of your desktop session while it is running (both as application or in system tray). This should not happen.

So, from the code I can see that the crashed state is kind of always set to true and is only set false when the Application is quit manually. This kind of makes sense because it is hard to set it to true when the application crashed, right? :smiley: I guess its the same with lock files in other applications.

So, there is a Part::clearCrashProperties(), which is supposed to be called when you click “Restore Session” (according to the code) … But in my ~/.local/share/akregator/crashed config file, crashed is still set to true after I click that button. Strange.

Ah well, still going over my head all this, which is not surprising given that I did not do C++ in years. For me it seems that Akregator does not handle a request to quit from the session manager gracefully.

I cannot understand how this can be going on for several years now. Everybody using Akregator should have this thrown into their face on a daily basis. … Or am I missing something and 95% of the users are doing it the right way and giggling about us who do not get it? :smiley:

Cheers

7

Isn’t the “Show Tray” option doing this?