[okular] [Bug 397463] Session management (named sessions, save/load sessions, auto-session-restore, etc) like in Kate

2023-05-02 Thread Alex A.D.
https://bugs.kde.org/show_bug.cgi?id=397463

Alex A.D.  changed:

   What|Removed |Added

 CC||al.neo...@gmail.com

--- Comment #33 from Alex A.D.  ---
Any progress on this? I would like to  have this feature implemented? Thanks!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 464030] Welcome screen stays visible after importing PostScript as PDF

2023-05-02 Thread dxt . wjb
https://bugs.kde.org/show_bug.cgi?id=464030

dxt@gmail.com  changed:

   What|Removed |Added

 CC||dxt@gmail.com

--- Comment #1 from dxt@gmail.com  ---
The Welcome Screen can also stay visible when a document has been opened via
the DBus interface.

1. Start Okular

2. Find the DBus server

$ qdbus| grep okular
org.kde.okular-9834

3. Open a document

 $ dbus-send --print-reply --dest=org.kde.okular-9834 /okular
org.kde.okular.openDocument string:/path/to/some.pdf

However, I think there's a more general problem with opening documents because
tab behaviour is also inconsistent the same way',
i.e.  the  "Open new files in tabs" and "Switch to existing tab..."
configuration options:  
   * work as expected for:
   * File | Open
   * File | Open Recent
   * have no effect for: 
   * File | Import Postscript as PDF
   * DBus OpenDocumentSOFTWARE/OS VERSIONS

SOFTWARE/OS VERSIONS
Operating System: Gentoo (amd64/stable) Linux-6.1.19
Okular Version: 22.12.3
KDE Plasma Version: 5.27.4.1
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.9
Graphics Platform: X11

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 464030] Welcome screen stays visible after importing PostScript as PDF

2023-05-02 Thread dxt . wjb
https://bugs.kde.org/show_bug.cgi?id=464030

--- Comment #2 from dxt@gmail.com  ---
Please disregard my dbus comments, shortly after pressing "Save Changes" I
tried the /okularshell path (as below) and the behaviour of Welcome Screen &
Tabs is as expected.
 $ dbus-send --print-reply --dest=org.kde.okular-9834 /okular
org.kde.okular.openDocument string:file://path/to/some.pdf

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 445573] Okular consumes an enormous amount of Memory (it reached over 1Gb today

2023-05-02 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=445573

pa...@reedyoung.net changed:

   What|Removed |Added

 CC||pa...@reedyoung.net

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 469216] Okular (through snap) GUI is all strange since 23.04.0

2023-05-02 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=469216

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org,
   ||sgmo...@kde.org

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 469216] Okular (through snap) GUI is all strange since 23.04.0

2023-05-02 Thread Scarlett Moore
https://bugs.kde.org/show_bug.cgi?id=469216

Scarlett Moore  changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|REPORTED|ASSIGNED
   Assignee|okular-devel@kde.org|sgmo...@kde.org

--- Comment #1 from Scarlett Moore  ---
I haven't been able to reproduce, but will look into it further.
Thank you
Scarlett

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 465146] Okular crashes when connecting to usb-c dock with external monitor

2023-05-02 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=465146

Nate Graham  changed:

   What|Removed |Added

 Status|REPORTED|RESOLVED
 CC||n...@kde.org
 Resolution|--- |DUPLICATE

--- Comment #2 from Nate Graham  ---


*** This bug has been marked as a duplicate of bug 465077 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 467419] Okular crashed when connecting usb-c docking with 4k screen

2023-05-02 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=467419

Nate Graham  changed:

   What|Removed |Added

 CC||n...@kde.org
 Resolution|--- |DUPLICATE
 Status|REPORTED|RESOLVED

--- Comment #1 from Nate Graham  ---


*** This bug has been marked as a duplicate of bug 465077 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 402017] Cannot save PDF when loaded file has been deleted

2023-05-02 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=402017

Nate Graham  changed:

   What|Removed |Added

   Version Fixed In||23.04.1
  Latest Commit||https://invent.kde.org/grap
   ||hics/okular/commit/b5191a2c
   ||1fa8f4ce45e36258942c6157a37
   ||99e7a
 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED

--- Comment #73 from Nate Graham  ---
Git commit b5191a2c1fa8f4ce45e36258942c6157a3799e7a by Nate Graham.
Committed on 02/05/2023 at 20:57.
Pushed by ngraham into branch 'master'.

Let user "Save As..." when document has been externally modified

Currently Okular stops the user from saving their document if it has
unsaved changes and was modified externally. This makes some sense
because there are now two sources of truth, and Okular cannot reconcile
them itself. However as a consequence, it causes data loss since the
user's unsaved changes in Okular become un-save-able. This is quite
frustrating when it happens.

But this prohibiton on saving over an externally-modified document only
really makes sense for a "Save" operation that overwrites the original
document. If instead, the user does a "Save As...", then they can save
their local changes to another file and avoid losing unsaved changes.
Then if needed, they can manually compare the original
externally-modified document with their newly-saved document and
reconcile the changes by hand.

Accordingly, this commit avoids showing the error message box and
blocking saving if the user is doing a "Save As..." to a new location,
rather than overwriting the open file.
FIXED-IN: 23.04.1

M  +3-1part/part.cpp

https://invent.kde.org/graphics/okular/commit/b5191a2c1fa8f4ce45e36258942c6157a3799e7a

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 402017] Cannot save PDF when loaded file has been deleted

2023-05-02 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=402017

--- Comment #74 from Nate Graham  ---
Git commit 89f17155bffa20500d7f3f098b08f61eedcb780d by Nate Graham.
Committed on 02/05/2023 at 20:57.
Pushed by ngraham into branch 'master'.

Offer options when trying to overwrite externally-modified file

When the user tries to do a "Save" operation on an open file that was
since modified externally, currently Okular prohibits it. We can make
this a bit more user-friendly by instead explaining the situation
clearly and offering the user some options:
- Yes, really overwrite the changes made in the other program
- Instead save the unsaved changes as a new file elsewhere
- Abort

M  +35   -14   part/part.cpp

https://invent.kde.org/graphics/okular/commit/89f17155bffa20500d7f3f098b08f61eedcb780d

-- 
You are receiving this mail because:
You are the assignee for the bug.

[okular] [Bug 402017] Cannot save PDF when loaded file has been deleted

2023-05-02 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=402017

Nate Graham  changed:

   What|Removed |Added

  Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap
   |hics/okular/commit/b5191a2c |hics/okular/commit/b596df0c
   |1fa8f4ce45e36258942c6157a37 |937e015ab284f44fdd7159e925c
   |99e7a   |7acb2

--- Comment #75 from Nate Graham  ---
Git commit b596df0c937e015ab284f44fdd7159e925c7acb2 by Nate Graham.
Committed on 02/05/2023 at 21:11.
Pushed by ngraham into branch 'release/23.04'.

Let user "Save As..." when document has been externally modified

Currently Okular stops the user from saving their document if it has
unsaved changes and was modified externally. This makes some sense
because there are now two sources of truth, and Okular cannot reconcile
them itself. However as a consequence, it causes data loss since the
user's unsaved changes in Okular become un-save-able. This is quite
frustrating when it happens.

But this prohibiton on saving over an externally-modified document only
really makes sense for a "Save" operation that overwrites the original
document. If instead, the user does a "Save As...", then they can save
their local changes to another file and avoid losing unsaved changes.
Then if needed, they can manually compare the original
externally-modified document with their newly-saved document and
reconcile the changes by hand.

Accordingly, this commit avoids showing the error message box and
blocking saving if the user is doing a "Save As..." to a new location,
rather than overwriting the open file.
FIXED-IN: 23.04.1


(cherry picked from commit b5191a2c1fa8f4ce45e36258942c6157a3799e7a)

M  +3-1part/part.cpp

https://invent.kde.org/graphics/okular/commit/b596df0c937e015ab284f44fdd7159e925c7acb2

-- 
You are receiving this mail because:
You are the assignee for the bug.