Bug 89666 - kghostview can't turn page after reactivation of PC after standby
Summary: kghostview can't turn page after reactivation of PC after standby
Status: RESOLVED NOT A BUG
Alias: None
Product: okular
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Okular developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-16 23:49 UTC by Benedikt Nimmervoll
Modified: 2014-05-08 08:26 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Benedikt Nimmervoll 2004-09-16 23:49:26 UTC
Version:           0.20 (using KDE 3.2 BRANCH >= 20040204, Mandrake Linux Cooker i586 - Cooker)
Compiler:          gcc version 3.3.2 (Mandrake Linux 10.0 3.3.2-6mdk)
OS:                Linux (i586) release 2.4.25-2mdk

I had an open pdf-document, viewed by kghostview, as I switched my PC to standby. After reactivation I wanted to scroll through the open document, but kghostview gave back following message:

Error: /ioerror in --setfileposition--
Operand stack:
   7   1   --nostringval--   --nostringval--   --nostringval--   339258   18   0   18   --nostringval--   2951213
Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--   --nostringval--   --nostringval--   false   1   %stopped_push   1   3   %oparray_pop   1   3   %oparray_pop   1   3   %oparray_pop   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--   --nostringval--   --nostringval--   --nostringval--   --nostringval--   %loop_continue   --nostringval--   7   1   9   --nostringval--   %for_pos_int_continue   --nostringval--   --nostringval--   --nostringval--   --nostringval--   --nostringval--
Dictionary stack:
   --dict:1057/1417(ro)(G)--   --dict:0/20(G)--   --dict:73/200(L)--   --dict:97/127(ro)(G)--   --dict:229/230(ro)(G)--   --dict:19/24(L)--
Current allocation mode is local
Last OS error: 116
ESP Ghostscript 7.07.2: Unrecoverable error, exit code 1
Error: /ioerror in --setfileposition--
Operand stack:
   2   1   --nostringval--   --nostringval--   --nostringval--   3135   1   0   1   --nostringval--   2950873
Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--   --nostringval--   --nostringval--   false   1   %stopped_push   1   3   %oparray_pop   1   3   %oparray_pop   1   3   %oparray_pop   .runexec2   --nostringval--   --nostringval--   --nostringval--   2   %stopped_push   --nostringval--   --nostringval--   --nostringval--   --nostringval--   --nostringval--   %loop_continue   --nostringval--   2   1   9   --nostringval--   %for_pos_int_continue   --nostringval--   --nostringval--   --nostringval--   --nostringval--   --nostringval--
Dictionary stack:
   --dict:1057/1417(ro)(G)--   --dict:0/20(G)--   --dict:73/200(L)--   --dict:97/127(ro)(G)--   --dict:229/230(ro)(G)--   --dict:19/24(L)--
Current allocation mode is local
Last OS error: 116
ESP Ghostscript 7.07.2: Unrecoverable error, exit code 1

Then I closed the message window and kghostview worked fine again.
Comment 1 Benedikt Nimmervoll 2004-09-16 23:52:35 UTC
I forgot to mention, that the page preview in the side bar after this small, let's say accident, doesn't work properly any more. that means, it doesn't show the pages.
Comment 2 Luís Pedro Coelho 2004-09-17 00:11:49 UTC
Is this reproduceable? I mean, does it happen every time?
Can you check whether after reactivating the computer that there are two child 
gs processes running (children of kghostview)? [ You can use "KDE System 
Guard", looking at the process table in tree mode if you don't know how to do 
this ]

thanks,
luis

Comment 3 Benedikt Nimmervoll 2004-09-24 11:30:28 UTC
Sorry for answering so late.
Yes, the failure is reproducable everytime. I forgot to mention that I opened files 
stored on a CDRom. It doesn't occur on files loaded from hda1.
If this incident happened the two gs processes have not been available!

Bye!
Benedikt
Comment 4 Adrián Chaves (Gallaecio) 2012-10-15 19:31:51 UTC
Does this happen with Okular?
Comment 5 Albert Astals Cid 2014-05-08 08:26:24 UTC
No answer for years.