I have a desktop PC for home and a laptop for work. Both use the latest version of KDE Neon User Edition

Operating System: KDE neon 5.23
KDE Plasma Version: 5.23.4
KDE Frameworks Version: 5.89.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-43-generic (64-bit)
Graphics Platform: Wayland

Only difference is that PC desktop uses X11 session and the laptop uses Wayland session.

In PC desktop, Akregator auto starts fine with latest session used after reboot the system, but in Wayland, although I haven't configured the app to autostart  on system boot, when I launch the app I can always reproduce this issue that shows the recover session.

Will try to configure Akregator to autostart on system launch and update this comment.

(In reply to Alex Barrero from comment #1)
> I have a desktop PC for home and a laptop for work. Both use the latest
> version of KDE Neon User Edition
> 
> Operating System: KDE neon 5.23
> KDE Plasma Version: 5.23.4
> KDE Frameworks Version: 5.89.0
> Qt Version: 5.15.3
> Kernel Version: 5.11.0-43-generic (64-bit)
> Graphics Platform: Wayland
> 
> Only difference is that PC desktop uses X11 session and the laptop uses
> Wayland session.
> 
> In PC desktop, Akregator auto starts fine with latest session used after
> reboot the system, but in Wayland, although I haven't configured the app to
> autostart  on system boot, when I launch the app I can always reproduce this
> issue that shows the recover session.
> 
> Will try to configure Akregator to autostart on system launch and update
> this comment.

Forgot to add the Akregator version: 5.19.0 (21.12.0)

Can confirm.
A log-out and log-in is enough for akregator to show the recover-session screen.
I am on X11, fedora 35, akregator version 5.19.2

Same problem every boot. Akregator version 5.19.3

When I perform the steps to get the akregator window in front of me, I close it and open it, it is completely as it should be. But when I close the akregator window, open the konsole and give the command "killall akregator" and then open akregator again. it suddenly doesn't know what to do with the session...

Same thing here while using wayland on desktop HP prodesk 400 g5.
Akregator opens screen to restore last session, is wasnt shutdown properly it says.

When starting with x11 it doenst give any problems.

akregator 5.22.3 (22.12.3) 
debian 12 stable KDE

It seems to be an issue with how Akregator exits primarily, maybe it's a problem with how wayland signals applications to exit? I will endeavour to run a debug build and see what it spits out and put it here later if I can. 

This seems to be a very impactful bug on the user's experience, could we change the importance of this bug?

There's a whole lot of write errors as akregator exits:

^C
kf.kio.core: An error occurred during write. The worker terminates now.                                       
kf.kio.core: An error occurred during write. The worker terminates now.
user@comp2: ~ $ kf.kio.core: An error occurred during write. The worker terminates now.
kf.kio.core: An error occurred during write. The worker terminates now.
kf.kio.core: An error occurred during write. The worker terminates now.
kf.kio.core: An error occurred during write. The worker terminates now.
kf.kio.core: An error occurred during write. The worker terminates now.
kf.kio.core: An error occurred during write. The worker terminates now.

Same issue here. 

For me it actually won't close properly and that leads it to need to recover.

Operating System: openSUSE Tumbleweed 20240423
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.7-1-default (64-bit)
Graphics Platform: Wayland
Processors: 32 × AMD Ryzen 9 7950X3D 16-Core Processor
Memory: 30.5 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 4090/PCIe/SSE2
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: X670E AORUS PRO X
System Version: -CF

It's definitely an issue with how akregator uses KIO (or maybe a bug in KIO itself?), as the error message is from KIO::SlaveBase::send (src/core/slavebase.cpp:1470).

May have to look around and see what part of akregator calls the KIO stuff.

I have the same problem and as workaround I invoke a shutdown script containing:
   /usr/bin/qdbus-qt5 org.kde.akregator /akregator/MainWindow_1/actions/file_quit trigger

Hope it helps someone.

As of Akregator 6.1.1 (at least for me):
The recover session screen is still showing up every time it's launched, but it does seem to remember all the actions from the past session correctly (read articles, etc)

I just compile akregator from source. I change previousSessionCrashed function, compile and replace akregatorpart.so (edit file akregatorcentralwidget.cpp)

(In reply to Andrei Ivnitskii from comment #13)
> I just compile akregator from source. I change previousSessionCrashed
> function, compile and replace akregatorpart.so (edit file
> akregatorcentralwidget.cpp)

Where's the(In reply to Andrei Ivnitskii from comment #13)
> I just compile akregator from source. I change previousSessionCrashed
> function, compile and replace akregatorpart.so (edit file
> akregatorcentralwidget.cpp)

Could you please attach the patch?

Thanks

Just open "akregatorcentralwidget.cpp", find function "previousSessionCrashed" and always return FALSE

bool AkregatorCentralWidget::previousSessionCrashed() const
{
    return false;
}

(In reply to Andrei Ivnitskii from comment #15)
> Just open "akregatorcentralwidget.cpp", find function
> "previousSessionCrashed" and always return FALSE

What if it truly crashed?

I use it since 2017 and no really crash. But "restore session" on every start make me angry :)