Now, I have googled and I understand Evince/Document Viewer crashing is not news. But how come it only does this with one document for me? Opens it, loads, crashes.
Okular has been downloaded, btw. I'm asking this because I’m puzzled.
Bev
On Thu, 25 Oct 2018 at 09:42, Bev Nicolson lumos@gmx.co.uk wrote:
Now, I have googled and I understand Evince/Document Viewer crashing is not news. But how come it only does this with one document for me? Opens it, loads, crashes.
As a general rule you *might* find some clues if you run it from the command line.
Ie, from a terminal window: evince "path/to/pdf/file"
Most applications write quite a lot of information to the terminal when running (it's just that when you run them from the graphical interface it's hidden from view). You might get lucky by spotting an obvious error, maybe a font it couldn't open or a library it couldn't access. (Don't get your hopes up that you'll definitely get an answer, but a good detective will take all the clues they can get!)
-- Mark Rogers // More Solutions Ltd (Peterborough Office) // 0844 251 1450 Registered in England (0456 0902) 21 Drakes Mews, Milton Keynes, MK8 0ER
On 25/10/18 11:08, Mark Rogers wrote:
On Thu, 25 Oct 2018 at 09:42, Bev Nicolson lumos@gmx.co.uk wrote:
Now, I have googled and I understand Evince/Document Viewer crashing is not news. But how come it only does this with one document for me? Opens it, loads, crashes.
As a general rule you *might* find some clues if you run it from the command line.
Ie, from a terminal window: evince "path/to/pdf/file"
Most applications write quite a lot of information to the terminal when running (it's just that when you run them from the graphical interface it's hidden from view). You might get lucky by spotting an obvious error, maybe a font it couldn't open or a library it couldn't access. (Don't get your hopes up that you'll definitely get an answer, but a good detective will take all the clues they can get!)
-- Mark Rogers // More Solutions Ltd (Peterborough Office) // 0844 251 1450 Registered in England (0456 0902) 21 Drakes Mews, Milton Keynes, MK8 0ER
Well I've just tried that and 'this file does not exist' is a fairly big clue, I think. Evince clearly couldn't 'see' it. I'd best save that command if there's a next time.
Bev
On 25/10/18 13:48, Bev Nicolson wrote:
On 25/10/18 11:08, Mark Rogers wrote:
On Thu, 25 Oct 2018 at 09:42, Bev Nicolson lumos@gmx.co.uk wrote:
Now, I have googled and I understand Evince/Document Viewer crashing is not news. But how come it only does this with one document for me? Opens it, loads, crashes.
Ie, from a terminal window: evince "path/to/pdf/file"
<snip>
Well I've just tried that and 'this file does not exist' is a fairly big clue, I think. Evince clearly couldn't 'see' it. I'd best save that command if there's a next time.
Bev
Tried again just to see what happened having downloaded the file again. (It now opens nicely in Evince.) Still claims it is non-existent. How should I enter that command?
Bev
On Thu, 25 Oct 2018 at 14:12, Bev Nicolson lumos@gmx.co.uk wrote:
Ie, from a terminal window: evince "path/to/pdf/file"
Tried again just to see what happened having downloaded the file again. (It now opens nicely in Evince.) Still claims it is non-existent. How should I enter that command?
Sorry I wasn't very clear. You need to replace "path/to/pdf/file" with the path of the actual file you downloaded. Something like: evince "/home/bev/Downloads/MyPdf.pdf"
You might find it easier to navigate to the right directory first: cd cd Downloads ls -tr evince "MyPDF.pdf"
Note that the first cd (change directory) command without a directory will take you to your home directory. "ls -tr" lists ("ls") all files in the directory by time ("t") in reverse order ("r") so if you've just downloaded the file it'll be at the end of the list making it easier to find. You'll need to enter the correct filename (and it's case sensitive) in the last line. You don't need to enclose it in quotes unless it has special characters like spaces in it, but it does no harm!
Mark