After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 634685 - Note lost due to power cut
Note lost due to power cut
Status: RESOLVED DUPLICATE of bug 653445
Product: tomboy
Classification: Applications
Component: General
1.2.x
Other Linux
: High major
: 1.6.0
Assigned To: Tomboy Maintainers
Tomboy Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-11-12 14:30 UTC by Jef
Modified: 2012-05-30 04:20 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jef 2010-11-12 14:30:30 UTC 
I was editing a note when my laptop lost its power. The .note file is 0 bytes large and thus all the text is lost.

Luckily I made a backup copy to Opera notes not so long ago. Time for me to find out how to synchronize Tomboy notes...

How does a laptop abruptly looses power you may ask? My 6+ year old laptop sometimes powers off when the battery is recharging: when it almost reaches 100%, there is now a fairly good chance it looses power. I know this, so I work on battery for a while and then plug it in again; or I remove the battery. But yesterday it was almost recharged before I stopped working, I forgot and then it happened.

I think this is extremely rare to occur again for me or others, but it is a bug that can be avoided.

I'm using Tomboy 1.2.1 on openSUSE 11.3.
Comment 1 Sandy Armstrong 2010-11-12 15:10:52 UTC 
Are you by any chance using ext4?
Comment 2 Jef 2010-11-12 23:25:18 UTC 
Yes, I am using ext4.
Comment 3 Sandy Armstrong 2010-11-12 23:35:26 UTC 
Yeah, this problem seems to be exclusive to ext4.  I've not been able to reproduce and am not sure of the best fix but you're right that we should be able to avoid this.

Targeting for this cycle.  Note data loss is pretty serious.
Comment 4 Jared Jennings 2012-05-30 04:20:16 UTC 

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