The issue should be fixed in Oneiric
** Changed in: evince (Ubuntu)
Importance: Undecided = High
** Changed in: evince (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: evince
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/772399
Title:
About 50% of all annotation content is not saved at saving a copy of
the
** Changed in: evince
Status: Unknown = Confirmed
** Changed in: evince
Importance: Unknown = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/772399
Title:
About 50% of all
Thanks for the instructions, I was now able to reproduce the issue. I
tried first with many comments on one page and this did work, but with
comments on different pages I get the empty comments, you are seeing.
The simplest example to reproduce the bug for me is: Put a comment on
page one and
Adding another 3 comments (this time not by cut+paste, but keyboard
input) 2 were fine, one had zero content.
So cut+paste may have no impact.
Gerd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Marcel,
thanks for responding. The bug is quite easily reproducible. Here is
what I did:
I prepared a plain file with 10 comments:
lulu:/vm cat input.txt
Comment #1
Comment #2
Comment #3
Comment #4
Comment #5
Comment #6
Comment #7
Comment #8
Comment #9
Comment #10
lulu:/vm
The I copied
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/772399
Title:
About 50% of all annotation content is not saved at saving a copy of
the pdf
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as
detailed as possible.
This will help us to find and resolve the problem.
**
