Bug 210408

Summary:	problems with session saving / restoration
Product:	[Applications] akregator	Reporter:	m.wege
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	adam, dominik.stadler
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Unspecified
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description m.wege 2009-10-13 08:53:03 UTC

Version:            (using KDE 4.3.2)
Installed from:    Ubuntu Packages

Session saving and restoration does not work properly in Akregator. When I Akregator is started after reboot, it presents many feeds as unread, which have been read already. I would assume that this has something to do with akregator taking to long to close during shutdown. If I close akregator manually KDE asks me if I want to kill the task. I assume this is the same during shutdown, but instead of asking, KDE kills it. -> Session is not saved correctly.

Comment 1 Dominik Stadler 2009-10-28 20:27:15 UTC

This could be related to Bug 199232 "Database not saved until quitting "

Comment 2 Adam Spragg 2009-11-29 22:21:27 UTC

Another victim of this bug. If I log out of my session, akregator forgets which articles have been read. If I quit akregator before logging out, it remembers the state.

As well as being related to bug #199232, I'm wondering if it might be related to #209249, which I am also bitten by.

Comment 3 Dominik Stadler 2009-11-30 07:31:46 UTC

FYI, I am using the following command to ask Akregator to save it's state in-between, this also saves the state of articles correctly.

 dbus-send --session --dest=org.kde.akregator --type=method_call /Akregator  org.kde.akregator.part.saveSettings

Although you cannot put this in some cron script easily as it requires the D-Bus session (i.e. DBUS_... environment variables) which is only available in a terminal...

Comment 4 Christophe Marin 2010-02-22 01:31:59 UTC


*** This bug has been marked as a duplicate of bug 185507 ***