[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [akregator] [Bug 342381] New: no 'fsync' for 'akregatorc' or for 'feeds.opml'
From:       Peter Grandi <pg_kde () kde ! for ! sabi ! co ! UK>
Date:       2014-12-31 19:11:24
Message-ID: bug-342381-17878 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=342381

            Bug ID: 342381
           Summary: no 'fsync' for 'akregatorc' or for 'feeds.opml'
           Product: akregator
           Version: 4.13.2
          Platform: Kubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: NOR
         Component: general
          Assignee: kdepim-bugs@kde.org
          Reporter: pg_kde@kde.for.sabi.co.UK

aKregator does not seem to 'fsync' very much, that is only when quitting; I
think that this was verified by Red Dieter.

This means that in case of crashes for whatever reason often the files
'akregatorc' and especially 'feeds.opml' are corrupted or empty.

This seems to be a general issue with KDE, or perhaps it was a few years ago:

http://sandeen.net/wordpress/uncategorized/coming-clean-on-o_ponies/
http://lwn.net/Articles/351422/


Reproducible: Sometimes

Steps to Reproduce:
Crash or kill aKregator without quitting it.

Actual Results:  
'akregatorc' or more commonly 'feeds.opml' are empty, missing or corrupted.


Expected Results:  
Files written by aKregator get committed with 'fsync' when saved or auto-saved.

It is particulaly annoying because the 'feeds.opml~' save file is not properly
syncronized either, so it is essentially useless.

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]