Running instance of Evince keeps using the old location of a document when it was already copied elsewhere

Bug #520828 reported by Onderstekop
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evince (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: evince

I love Evince, but this has bit me several times:

  * directly open a .ps.tar or similar from Firefox, which starts the archive manager
  * open the .ps in the archive, which starts Evince
  * read a couple of pages from the document and click "Save a Copy" in the file menu.
  * do something else
  * close the archive manager
  * procrastinate some more
  * come back to Evince, which suddenly can't load any more pages that weren't already seen although I had already saved a copy, because the archive manager removed the document in /tmp and Evince is still using that location.

I see how this wouldn't happen to me if I never closed the archive manager or if I properly saved the archive, unpacked and then later moved the document to my paper stash and deleted the archive.. but wouldn't it be nicer to start reading pages from a copy, when it has explicitly been saved?

ProblemType: Bug
Architecture: amd64
Date: Fri Feb 12 07:36:30 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/evince
NonfreeKernelModules: nvidia
Package: evince 2.28.1-0ubuntu1.2
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
SourcePackage: evince
Uname: Linux 2.6.31-19-generic x86_64

Revision history for this message
Onderstekop (rhijnauwen) wrote :
Revision history for this message
Victor Vargas (kamus) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Changed in evince (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in evince (Ubuntu):
status: Incomplete → Invalid
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.