run.py crashed with OSError in save_months_to_disk()

Bug #1128285 reported by MyOtheHedgeFox
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
RedNotebook
Fix Released
High
Jendrik Seipp

Bug Description

ExecutablePath:
/usr/share/rednotebook/run.py

Package:
rednotebook 1.6.6-1~getdeb1 [Origin: GetDeb]

ProblemType:
Crash

Title:
run.py crashed with OSError in save_months_to_disk(): [Errno 1] Operation not allowed: '/path/to/rednotebook/2013-02.txt'

What is strange about this bug:
RedNotebook pops up this alarm via standard Ubuntu interface every time I save the journal. The thing is, RNB does not crash, it is still operational, and it saves all the files perfectly.
My files are stored on an NTFS Windows partition.

Revision history for this message
MyOtheHedgeFox (a-ztech) wrote :
Revision history for this message
Jendrik Seipp (jendrikseipp) wrote :

Thanks for your report. Fixed it in trunk by gracefully handling such cases.

Changed in rednotebook:
status: New → Fix Committed
importance: Undecided → High
assignee: nobody → Jendrik Seipp (jendrikseipp)
Revision history for this message
MyOtheHedgeFox (a-ztech) wrote : Re: [Bug 1128285] Re: run.py crashed with OSError in save_months_to_disk()

Hi again, Jendrik!

Hm... Is there any other way to check if the data is actually okay?
There might be reports saying that it said it saved the data but it
didn't.

Revision history for this message
Jendrik Seipp (jendrikseipp) wrote :

As long as you always edited and saved just a single month your files
should be fine. The error always happened after the file had been
written to disk.

Revision history for this message
Jendrik Seipp (jendrikseipp) wrote :

Fixed in 1.7.0

Changed in rednotebook:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.