Bug 445351 - Akregator always wants to recover the session on boot
Summary: Akregator always wants to recover the session on boot
Status: CONFIRMED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: 5.22.3
Platform: Debian stable Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-11-11 17:54 UTC by Gianmarco
Modified: 2024-04-25 18:56 UTC (History)
13 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
The recover session screen (109.20 KB, image/png)
2021-11-11 17:54 UTC, Gianmarco
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gianmarco 2021-11-11 17:54:48 UTC
Created attachment 143464 [details]
The recover session screen

SUMMARY
When I log in Akregator starts in the background, as expected, but when I open its window it says that the last Akregator session was not closed properly and gives me the options to recover the session, remind later or ignore.

STEPS TO REPRODUCE
1. Make Akregator auto-start on login.
2. Log out and back in or reboot.
3. Open Akregator's main window.

OBSERVED RESULT
Asks to recover the session.

EXPECTED RESULT
Should open a new session like usual.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux
(available in About System)
KDE Plasma Version: 5.23.2
KDE Frameworks Version: 5.87.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Comment 1 Alex Barrero 2021-12-23 09:44:25 UTC
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.
Comment 2 Alex Barrero 2021-12-23 09:45:51 UTC
(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)
Comment 3 pixelplanetdev 2022-05-08 00:07:03 UTC
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
Comment 4 Andrei Ivnitskii 2023-09-18 07:41:47 UTC
Same problem every boot. Akregator version 5.19.3
Comment 5 PK 2023-10-18 05:12:45 UTC
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...
Comment 6 Jan Wesselink 2024-01-04 12:23:50 UTC
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
Comment 7 Thomas Dickson 2024-04-20 12:14:11 UTC
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?
Comment 8 Thomas Dickson 2024-04-21 04:26:41 UTC
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.
Comment 9 Ryein Goddard 2024-04-25 18:56:18 UTC
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