Bug 262255 - auto-refresh does not always work
Summary: auto-refresh does not always work
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: kdecore (show other bugs)
Version: 4.5
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
: 260629 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-01-06 00:26 UTC by Peter
Modified: 2023-01-13 05:14 UTC (History)
5 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 Peter 2011-01-06 00:26:30 UTC
Version:           0.11.2 (using KDE 4.5.4) 
OS:                MS Windows

More often than not, Okular does not refresh when the pdf file is modified, even though this particular option is turned on. This is under windows 7. 

Reproducible: Sometimes

Steps to Reproduce:
I use Kile+Okular. When compiling a latex pdf document and opening it in Okular, it works fine. However, when I modify the document and recompile it, Okular will often not reload the document. Sometimes it does, but more often it doesn't. Which means I have to manually reload it.

Actual Results:  
Okular does not always reload my pdf document when it is recompiled.

Expected Results:  
It should reload my pdf document every time it is compiled.

I used to use KDE 4.2.95 and here everything worked flawlessly. I just installed KDE 4.5.4 yesterday and it is only since this upgrade that I am suffering from this problem. So, I think the problem was only introduced recently.
Comment 1 Albert Astals Cid 2011-01-06 00:36:16 UTC
I guess you do not have a linux machine to test if it works there, do you?
Comment 2 Peter 2011-01-09 19:35:38 UTC
I do have access to a linux machine but it's not mine so I can't mess around with it arbitrarily. Currently this machine is running Okular 0.11.1 under KDE 4.5.1 (in Ubuntu 10.10) and everything seems to work flawlessly there.

Also, I was asked by a KDE forum moderator to link to this post as well:
http://forum.kde.org/viewtopic.php?f=59&t=90219&p=184430#p184430
Comment 3 Pino Toscano 2011-01-09 20:23:58 UTC
@kde-windows guys:
can you please run the kdirwatch test suite on windows?
Comment 4 Diego 2011-01-09 20:34:25 UTC
(In reply to comment #1)
> I guess you do not have a linux machine to test if it works there, do you?

No problem in Linux.

Could be duplicate of bug #260629
Comment 5 Peter 2011-01-09 21:03:08 UTC
(In reply to comment #4)
> Could be duplicate of bug #260629

Wow, it seems I missed that one. I totally confirm this:
1) Indeed, the times I tried since I read this, I noticed that it works for the first reload and it doesn't work after that any more. Just as #260629 describes.
2) Indeed, if instead of opening the pdf from Kile (where Kile launches Okular and reads the pdf) I open the pdf manually in Okular, then the bug is gone, it refreshes flawlessly. Just as #260629 describes.
3) Indeed, if I save my .tex file in the C: root (and open Kile with admin permissions, which is needed to write to C: in win7), it refreshes flawlessly.  Just as #260629 describes.

So indeed, this is a duplicate as #260629. I don't know whether the / vs \ thing makes sense from a technical point of view, but the fact that running from C: root solves the problem, makes this explaining quite plausible. Working in C:/temp already makes the problem appear as described here, so it's not a spaces problem.

(In case anyone would wonder: it is not the admin permissions that make C: succesful: I tried on other folders as admin and the bug was the same as usual.)
Comment 6 Carlo Segato 2011-01-13 11:04:34 UTC
*** Bug 260629 has been marked as a duplicate of this bug. ***
Comment 7 bluebirdx11 2011-01-19 17:40:40 UTC
I can confirm everything written by Peter working exactly the same way for me using the same versions.

I just want to add, that right clicking on the .pdf file -> open with -> okular reproduces the bug.
Comment 8 Andrew Crouthamel 2018-11-05 03:21:01 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Andrew Crouthamel 2018-11-17 04:54:32 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 10 Justin Zobel 2022-12-14 03:09:11 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 11 Bug Janitor Service 2022-12-29 05:23:41 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 12 Bug Janitor Service 2023-01-13 05:14:36 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!