| Summary: | configuration settings not being saved | ||
|---|---|---|---|
| Product: | [Applications] okular | Reporter: | pnewell0705 |
| Component: | general | Assignee: | Okular developers <okular-devel> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | john.kizer, pnewell0705 |
| Priority: | NOR | ||
| Version First Reported In: | 24.12.3 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | screenshot of what I am seeing | ||
After a couple more openings of okular, about an hour after I reported this bug okular suddenly seemed to pick up the change. From a "I'm just a user" I have to admit this is strange as I would expect that when one changes the setting it would show up on the next opening of okular. The other odd thing is that I looked okularrc and the last file write was updated to very recently. But nothing was there related to this. I did find the change in okularparttc so my earlier "I don't see a change" are inaccurate as I now know that I should have looked in a different file. Not certain how/why things are where they are as user expectations are that settings are in an rc file So I don't know if there is a bug or not here. If there is something I can do to test further to get a better sense so you can better determine if there is a bug, please let me know Hi - I'm not 100% sure myself, but I *think* that Okular remembers the last view mode that was in use for each individual document, and prefers that over a global default when it's available. Could you perhaps double-check if the file that you opened after changing the default view, which didn't reflect that new default view, is one that you had previously opened with the a different view mode in use? Just thinking that might be related here. Thanks! John: Thanks for the reply. When I read your message, I had this strong feeling that made a mistake in my testing as your suggestion sounds very much like expected behavior. So I ran a test on a pdf I have never put into okular and that is exactly what it is going. I have a feeling I got locked into changing the default and never changing the file's setting as I expect (incorrectly I now know) the default to "do its magic. I would like to chalk it up as a "senior moment" but I think this one is more a case of going down the wrong rabbit hole. I appreciate clarifying and, obviously, this is a "Pilot Error" and not a bug Paul Haha! I'm just glad it's actually working as intended :-) I almost reported a bug a while back around power profiles when plugged in, not realizing it was because I hadn't actually plugged in my laptop! |
Created attachment 180339 [details] screenshot of what I am seeing SUMMARY: configuration settings not being saved STEPS TO REPRODUCE 1. open okular, go to settings -> configure -> general, change zoom from default Fit Width to Fit Page, click apply, click OK, exit program 2. open okular with a pdf and observe the zoom is set to Fit Width 3. examine ~/.config/okularrc to see if there is anything there about zoom (there isn't) OBSERVED RESULT changing zoom setting in configuration appears not to be saved EXPECTED RESULT if I set zoom to Fit Page in the configuration then I expect every pdf I open to start with Fit Page SOFTWARE/OS VERSIONS contents of file /etc/redhat-release: Rocky Linux release 9.5 (Blue Onyx) Windows: -- macOS: -- (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: ??? KDE Plasma Version: ??? KDE Frameworks Version: ??? Qt Version: 5.15.9 ADDITIONAL INFORMATION My Rocky 9.5 opSys is fully updated as of 16apr25 and, so far, everything else about okular is working. This is the first time I have tried to work with the settings. I am running under the Mate desktop I have attached a screen shot after 1) opening okular and observing what the zoom starts at and 2) opening the configuration to see that state that okular started up in (as in "should have") Thank you for any help. If this has been fixed in a later version (which won't be available in rocky/RHEL for the next major release (?maybe a minor?), can you at least let me know what line I need to patch into okularrc