Description of problem: Opened a Read-only document, edited it, then tried to save the modified version. Program did not appear to crash Version-Release number of selected component: cherrytree-0.26.2-2.fc18 Additional info: libreport version: 2.0.14 abrt_version: 2.0.13 cmdline: /usr/bin/python /usr/bin/cherrytree kernel: 3.6.0-0.rc7.git1.4.fc18.i686 backtrace: :ctdb.py:306:write_db_node:OperationalError: disk I/O error : :Traceback (most recent call last): : File "/usr/share/cherrytree/modules/core.py", line 1046, in file_save : elif self.file_write(os.path.join(self.file_dir, self.file_name), first_write=False): : File "/usr/share/cherrytree/modules/core.py", line 1131, in file_write : self.file_write_low_level(filepath, xml_string, first_write) : File "/usr/share/cherrytree/modules/core.py", line 1085, in file_write_low_level : else: self.ctdb_handler.pending_data_write(self.db) : File "/usr/share/cherrytree/modules/ctdb.py", line 64, in pending_data_write : self.write_db_node(db, tree_iter, level, node_sequence, node_father_id, write_dict) : File "/usr/share/cherrytree/modules/ctdb.py", line 306, in write_db_node : db.execute('DELETE FROM children WHERE node_id=?', (node_id,)) :OperationalError: disk I/O error : :Local variables in innermost frame: :node_father_id: 8 :name: u'Matlab' :tags: u'' :self: <ctdb.CTDBHandler instance at 0x894860c> :sequence: 3 :db: <sqlite3.Connection object at 0x8b6c708> :syntax: 'custom-colors' :node_id: 11 :tree_iter: <GtkTreeIter at 0x8eb3250> :exporting: '' :write_dict: {'upd': True, 'buff': False, 'hier': True, 'child': False, 'prop': False} :level: 2 :is_richtxt: 1 :is_ro: 0
Created attachment 618912 [details] File: event_log
Created attachment 618913 [details] File: core_backtrace
How would you expect cherrytree to behave in case you have no write access?
I have a tendency to always submit a bug when the ABRT tool shows up. I understand that this problem could have very minimal impact on the user. I would downgrade the severity to low if I could.
In the upcoming version 0.28.1 there is a check before the attempt to write to disk, if there is no write access a dialog will be prompted.
cherrytree-0.28.5-1.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/cherrytree-0.28.5-1.fc18
Package cherrytree-0.28.5-1.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing cherrytree-0.28.5-1.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-20672/cherrytree-0.28.5-1.fc18 then log in and leave karma (feedback).
cherrytree-0.28.5-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.