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 587450 - note corruption
note corruption
Status: RESOLVED DUPLICATE of bug 587070
Product: gnote
Classification: Applications
Component: main
0.5.x
Other Linux
: Normal critical
: 1.0
Assigned To: gnote-maint
gnote-maint
Depends on:
Blocks:
 
 
Reported: 2009-06-30 17:56 UTC by Robert Millan
Modified: 2009-06-30 18:56 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
sample note that will be corrupted when loaded on >=0.5.0 (1.11 KB, application/xml)
2009-06-30 18:10 UTC, Robert Millan 		Details

Description Robert Millan 2009-06-30 17:56:05 UTC 
gnote from 0.5.0 to git corrupts notes.  From Debian BTS (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534969):

<quote>
My notes from 0.3 are partially destroyed by gnote 0.5,
which converts e.g.
  0.7.99	<bold>Anfang September</bold>
to
  0.7.99	A<bold>nfang September</bold>

It also produces stuff like "Release • Candidate 2", whereas
this should read "• Release Candidate 2".
</quote>

Others have hit the same problem.  I traced this (git-bisect) to commit d23236275936e6f0f44dddae639528e4f0f7b935
Comment 1 Hubert Figuiere (:hub) 2009-06-30 18:01:53 UTC 
and do you have the original note?
Comment 2 Robert Millan 2009-06-30 18:10:09 UTC 
Created attachment 137640 [details]
sample note that will be corrupted when loaded on >=0.5.0
Comment 3 Robert Millan 2009-06-30 18:11:27 UTC 
(In reply to comment #1)
> and do you have the original note?

I was given a copy privately.  Just replaced the strings with dummy ones to protect the submitter's privacy, verified the result still triggers the bug, and attached it.
Comment 4 Hubert Figuiere (:hub) 2009-06-30 18:15:44 UTC 
I'm wondering if this is not a duplicate of bug 587070
Comment 5 Hubert Figuiere (:hub) 2009-06-30 18:50:56 UTC 

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