Thread: [aKregator-devel] [Bug 199232] New: Database not saved until quitting
Brought to you by:
lippel
From: Ben B. <Mat...@gm...> - 2009-07-07 02:59:32
|
https://bugs.kde.org/show_bug.cgi?id=199232 Summary: Database not saved until quitting Product: akregator Version: unspecified Platform: Fedora RPMs OS/Version: unspecified Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: akr...@li... ReportedBy: Mat...@gm... Version: (using KDE 4.2.4) Installed from: Fedora RPMs If Akregator (or Kontact) crashes, Akregator loses all feeds and read/unread state since the last successful quit. It should at least dump to the database on every update of feeds, otherwise weeks of feeds can be lost if something goes wrong. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. |
From: Christophe G. <cgi...@gm...> - 2009-07-07 19:21:37
|
https://bugs.kde.org/show_bug.cgi?id=199232 Christophe Giboudeaux <cgi...@gm...> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |wishlist -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. |
From: Micah G. <kde...@mi...> - 2009-10-26 00:22:40
|
https://bugs.kde.org/show_bug.cgi?id=199232 Micah Gersten <kde...@mi...> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kde...@mi... | |m --- Comment #1 from Micah Gersten <kde bugs micahscomputing com> 2009-10-26 01:20:55 --- I can confirm this with KDE 4.3.2 on Ubuntu: https://bugs.launchpad.net/bugs/460756 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. |
From: Dominik S. <dom...@gm...> - 2009-10-28 19:25:50
|
https://bugs.kde.org/show_bug.cgi?id=199232 Dominik Stadler <dom...@gm...> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dom...@gm... -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. |
From: Dominik S. <dom...@gm...> - 2009-10-28 19:31:26
|
https://bugs.kde.org/show_bug.cgi?id=199232 --- Comment #2 from Dominik Stadler <dominik stadler gmx at> 2009-10-28 20:31:11 --- This is very similar to Bug 187687 "When there is a crash read links are not stored. ", also Bug 210408 "problems with session saving / restoration" sounds related. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. |
From: Dominik S. <dom...@gm...> - 2009-11-04 23:38:58
|
https://bugs.kde.org/show_bug.cgi?id=199232 --- Comment #3 from Dominik Stadler <dominik stadler gmx at> 2009-11-05 00:38:46 --- Also Bug 196633 and Bug 185507 are related, maybe we can duplicate most of these to this one. I'm using the following command to ask Akregator to save the current state (all in one line): dbus-send --session --dest=org.kde.akregator --type=method_call /Akregator org.kde.akregator.part.saveSettings this will use d-bus to instruct Akregator to persist its database, at least it seems to work for me. Unfortunately you cannot run this workaround in a cron-job periodically as it requires access to the d-bus session, which you don't have inside cron. But you can probably add it to some X-shutdown script and make it work this way. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. |
From: Oliver H. <yoh...@ho...> - 2010-03-03 18:42:41
|
https://bugs.kde.org/show_bug.cgi?id=199232 Oliver Henshaw <yoh...@ho...> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |yoh...@ho... -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. |
From: Oliver H. <yoh...@ho...> - 2010-03-06 13:38:13
|
https://bugs.kde.org/show_bug.cgi?id=199232 --- Comment #4 from Oliver Henshaw <yoho_ahoy hotmail com> 2010-03-06 14:35:16 --- What is Storage::autoCommit() used for? It looks like it's only checked on close() but isn't this only called on the shutdown path where you'd want to always commit to the database? -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. |
From: Marcin G. <mg...@fo...> - 2010-09-14 09:02:04
|
https://bugs.kde.org/show_bug.cgi?id=199232 Marcin Gryszkalis <mg...@fo...> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mg...@fo... --- Comment #5 from Marcin Gryszkalis <mg fork pl> 2010-09-14 10:59:04 --- (In reply to comment #3) > Unfortunately you cannot run this workaround in a cron-job periodically as it > requires access to the d-bus session, which you don't have inside cron. As a workaround I use a simple wrapper that harvests DBUS_SESSION_BUS_ADDRESS from environment of existsing kde processes (via /proc) - with that you can call dbus from cronjob. See http://www.mail-archive.com/deb...@li.../msg30421.html -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. |
From: <pi...@gm...> - 2011-02-19 08:28:57
|
https://bugs.kde.org/show_bug.cgi?id=199232 --- Comment #6 from <pitom71 gmx net> 2011-02-19 09:29:37 --- Akregator v1.6.5 Besides loosing the read/unread information (which is very annoying) it also looses the settings which columns to display (title/feed/author/date). Also the severity of this bug should not be "wishlist" but "normal" to its degrade of function during specified conditions. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. |