https://bugs.kde.org/show_bug.cgi?id=371904
David Hurka changed:
What|Removed |Added
CC||okular-devel@kde.org
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=395497
--- Comment #37 from David Hurka ---
> Well, in option 1 you mean keeping the part.rc intact and then copying all
> the options to shell.rc?
No, I don’t mean to copy actions from part.rc to shell.rc. I think we tracked
this bug down to shell.rc
https://bugs.kde.org/show_bug.cgi?id=421468
--- Comment #6 from David Hurka ---
Zooming farther than 2000% using middle-click-drag zoom is laggy on my Thinkpad
X240 (Core i5 4300, 8GB). Additionaly the console reports:
Running out of memory on page 2 (26436x25245 px);
Apparently tiling does
https://bugs.kde.org/show_bug.cgi?id=305534
David Hurka changed:
What|Removed |Added
Summary|Anotation don't show all|Annotations don'
https://bugs.kde.org/show_bug.cgi?id=423335
Bug ID: 423335
Summary: Assert crash at closing tabs with new annotation
toolbar
Product: okular
Version: unspecified
Platform: Compiled Sources
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=423335
David Hurka changed:
What|Removed |Added
Summary|Assert crash at closing |Assert crash at closing
|tabs
https://bugs.kde.org/show_bug.cgi?id=423360
Bug ID: 423360
Summary: Viewport blinks (flashes, disappears) while scrolling
or dragging at moderate or high zoom levels
Product: okular
Version: 1.10.1
Platform: Compiled Source
https://bugs.kde.org/show_bug.cgi?id=209364
--- Comment #2 from David Hurka ---
Now that annotations are stored inside PDF documents, is this even possible?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=423363
David Hurka changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=388450
David Hurka changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=423432
--- Comment #2 from David Hurka ---
The actions with same icon are:
* Auto Fit
* Fit Page
* Zoom
* Zoom (yes, two of them)
I think one Zoom could be a magnifier. But at least these icons are not used in
the same context. (Auto Fit and Fit Page are in
https://bugs.kde.org/show_bug.cgi?id=399488
David Hurka changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=319870
David Hurka changed:
What|Removed |Added
Version Fixed In||1.10
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=423432
--- Comment #4 from David Hurka ---
Well, If you put all these actions into your toolbar, you can configure both
icon and text.
What icons would you suggest for the other actions?
I think we could use zoom-fit-height for Fit Page, if we can agree
https://bugs.kde.org/show_bug.cgi?id=423517
--- Comment #3 from David Hurka ---
The widget style looks very much like Breeze, but the color scheme is very
likely not Breeze. It looks similar, but note the white text on blue background
on the pressed button.
If you can determine your color
https://bugs.kde.org/show_bug.cgi?id=423517
--- Comment #5 from David Hurka ---
Ah, ok, now I realize it. So the bug is:
Text in form fields becomes smaller when the window is made wider, and
eventually disappears. But when form fields are disabled, everthing is fine.
Correct?
--
You are
https://bugs.kde.org/show_bug.cgi?id=422856
David Hurka changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=418758
David Hurka changed:
What|Removed |Added
CC||withholdpurposefully@yahoo
https://bugs.kde.org/show_bug.cgi?id=418758
--- Comment #2 from David Hurka ---
If the document URL contains a #, Okular tries to focus the page specified by
the number following the #. Of course this fails if # is part of the actual
URL.
It was already suggested to interpret only #page=1234 as
https://bugs.kde.org/show_bug.cgi?id=418758
David Hurka changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=406831
David Hurka changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=423560
--- Comment #1 from David Hurka ---
Is it possible that Okular sets only some obvious extensions (like .pdf, .epub,
.okular), and you are missing extentions like .png, which are usually better
handled by other applications?
My memories of configuring
https://bugs.kde.org/show_bug.cgi?id=423517
David Hurka changed:
What|Removed |Added
Summary|Unable to see text typed|Text in enabled form fields
https://bugs.kde.org/show_bug.cgi?id=423432
--- Comment #8 from David Hurka ---
These are the design guidelines for Breeze icons. I fear that the icons
presented in the forum thread don’t work in 16px or 22px.
https://hig.kde.org/style/icons/monochrome/index.html
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=418758
--- Comment #8 from David Hurka ---
Maybe Explorer passes the # as #, and Dolphin passes it as %35?
Code is here:
https://invent.kde.org/graphics/okular/-/blob/master/part.cpp#L1736
--
You are receiving this mail because:
You are the assignee for
https://bugs.kde.org/show_bug.cgi?id=423148
--- Comment #8 from David Hurka ---
Thanks. To me it tells that you have Okular 20.04.x (1.10.x) installed, but not
the package okular-dbgsym. Can you install that package and wait for the next
crash, or did you already try that?
The problem (as I
https://bugs.kde.org/show_bug.cgi?id=423148
David Hurka changed:
What|Removed |Added
Summary|Okular crashes every time |Okular crashes when opening
https://bugs.kde.org/show_bug.cgi?id=423694
David Hurka changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=404549
David Hurka changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=423148
--- Comment #13 from David Hurka ---
Thanks for all the information! I see that you disabled the laptop screen.
Still, only using my one external screen vertically doesn’t crash for me...
Crash at opening a new tab supports my theory that QScroller is
https://bugs.kde.org/show_bug.cgi?id=423735
David Hurka changed:
What|Removed |Added
Component|PDF backend |printing
--- Comment #1 from David Hurka
https://bugs.kde.org/show_bug.cgi?id=423735
--- Comment #3 from David Hurka ---
Relevant context is that architectural plans often have page sizes far above A4
or whatever you have in your printer, correct?
Printing a specific section at a specific zoom is at least confusing. Look at
the PDF
https://bugs.kde.org/show_bug.cgi?id=423841
Bug ID: 423841
Summary: Page number widget doesn’t allow to enter a number
when pages have names different to their usual number
Product: okular
Version: 1.10.1
Platform: unspecif
https://bugs.kde.org/show_bug.cgi?id=423841
David Hurka changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=423841
David Hurka changed:
What|Removed |Added
Summary|Page number widget doesn’t |Page number widget is
|allow
https://bugs.kde.org/show_bug.cgi?id=423841
--- Comment #6 from David Hurka ---
Make the page name line edit an editable combo box, so it suggests completions?
Enter “2”, it suggests:
2 (Page 15) [Default choice]
2 (Page 2)
2 (Page 3)
2 (Page 4)
...
Pretty useless in this case, but maybe
Thanks a lot!
But braces arround single-line conditional blocks are still missing, contrary
to KDElibs coding style. Is that intended?
Date: Sat, 11 Jul 2020 10:06:37 +0200
From: Albert Astals Cid
>
> This means that all your pending Merge Requests conflict like crazy and hard
> kind of hard t
https://bugs.kde.org/show_bug.cgi?id=424103
David Hurka changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=419394
David Hurka changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=406489
David Hurka changed:
What|Removed |Added
CC||jesterflint...@gmail.com
--- Comment #10 from
https://bugs.kde.org/show_bug.cgi?id=406489
David Hurka changed:
What|Removed |Added
CC||jonat...@demeyer.name
--- Comment #11 from David
https://bugs.kde.org/show_bug.cgi?id=424234
David Hurka changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=169847
David Hurka changed:
What|Removed |Added
CC||sam...@damagehead.com
--- Comment #33 from David
https://bugs.kde.org/show_bug.cgi?id=188784
David Hurka changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=419394
David Hurka changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=301302
David Hurka changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=419394
David Hurka changed:
What|Removed |Added
See Also|https://bugs.kde.org/show_b |
|ug.cgi?id=301302
https://bugs.kde.org/show_bug.cgi?id=406489
David Hurka changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=301302
David Hurka changed:
What|Removed |Added
See Also|https://bugs.kde.org/show_b |https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=149798
David Hurka changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=406489
David Hurka changed:
What|Removed |Added
CC||stef...@klupsch.de
--- Comment #12 from David
https://bugs.kde.org/show_bug.cgi?id=311043
David Hurka changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=406489
David Hurka changed:
What|Removed |Added
CC||comenius...@gmail.com
--- Comment #13 from David
https://bugs.kde.org/show_bug.cgi?id=424285
David Hurka changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=424296
--- Comment #1 from David Hurka ---
AFAIK PDF protection is only a hypothetical thing. If you uncheck Configure
Okular -> General -> Obey DRM limitations, annotation tools should be
activated, and annotations are saved in the PDF as usual.
So ye
https://bugs.kde.org/show_bug.cgi?id=330364
--- Comment #2 from David Hurka ---
I agree that this behavior is frustrating. As far as I can reproduce it now, it
is not an Okular issue. On my KDE Neon, any fullscreen window (including non-Qt
applications) raises automatically when it gets focus
https://bugs.kde.org/show_bug.cgi?id=353560
David Hurka changed:
What|Removed |Added
Resolution|--- |FIXED
Version Fixed In
https://bugs.kde.org/show_bug.cgi?id=410723
David Hurka changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=410723
--- Comment #27 from David Hurka ---
(Credits for the patch go to Rene.)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=353560
--- Comment #4 from David Hurka ---
(The actual code implementing this feature was submitted by Luca Citi. Thanks!)
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=353560
--- Comment #6 from David Hurka ---
> use the authorship information in git
I can revert that, but how should I include the authorship information? I could
add these information in the commit message, but GitLab will always set me as
the “author”.
https://bugs.kde.org/show_bug.cgi?id=353560
--- Comment #7 from David Hurka ---
> a revert commit and a new commit
As alternative, to keep the mess more compact, I could append a single commit
that informs about the authors of the last commits.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=353560
--- Comment #9 from David Hurka ---
This page tells me that we use the squash feature in GitLab.
https://community.kde.org/Infrastructure/GitLab#Create_the_Merge_Request
Do you say I should not use the Merge button in GitLab, but push merge requests
https://bugs.kde.org/show_bug.cgi?id=353560
--- Comment #12 from David Hurka ---
Thanks, I think now I understand what is going on. I *created* the new MR in
GitLab, so GitLab considered me being the author, although the commits *in* the
MR are from Rene. The correct behavior would have been to
https://bugs.kde.org/show_bug.cgi?id=410723
David Hurka changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap
https://bugs.kde.org/show_bug.cgi?id=353560
--- Comment #14 from David Hurka ---
Bug 410723:
> Git commit ab7ae92a891adcb5c43435e75ea0e9ce8c078d81 by David Hurka, on behalf
> of René van Paassen.
Ok, should be fine now.
So a GitLab “merge”-merge merges the actual commits, as the
https://bugs.kde.org/show_bug.cgi?id=424542
Bug ID: 424542
Summary: Inline text annotation: “Current annotation has no
fill color”
Product: okular
Version: unspecified
Platform: Compiled Sources
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=236288
David Hurka changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=424522
--- Comment #7 from David Hurka ---
If Gentoo gives you release/20.04 source code, you will have 20.04 installed.
Then you “download source code”, that will probably give you master source
code. If you build that, and don’t `ninja install` it, your
https://bugs.kde.org/show_bug.cgi?id=402017
--- Comment #35 from David Hurka ---
Below is the commit that made Okular refuse to save if the file is modified.
Looks like Sven Brauch was basically trying to revert this commit, but we
should first figure out what’s the problem with poppler.
commit
https://bugs.kde.org/show_bug.cgi?id=402017
--- Comment #36 from David Hurka ---
If some generators can’t keep their own document file, we should probably
consider every file a remote file, i. e. make a temporary copy of every file
and open that instead. Right?
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=402017
--- Comment #38 from David Hurka ---
There exists this code in part.cpp:
> if (m_document->canSaveChanges()) {
> [...]
> } else {
> // If the generators doesn't support saving changes, we will
> // just copy the
https://bugs.kde.org/show_bug.cgi?id=402017
--- Comment #40 from David Hurka ---
> it moves us away from being able to load as you go PDF linearized files.
Hmm, ok.
Since this is not closed as INTENDED, I assume there must be another solution.
A) Keep the current swapBackingFile
https://bugs.kde.org/show_bug.cgi?id=402017
--- Comment #41 from David Hurka ---
> I mean think of this message you would have to show the user "Sorry, we
> can't open your file because you don't have enough space on disk".
If there is not enough space to create a temp
https://bugs.kde.org/show_bug.cgi?id=402017
--- Comment #44 from David Hurka ---
> Personally, i would suggest trying to figure out why poppler fails and
> fix it other than doing all strange things that need the user to read
> lots of stuff that has "if this and if that and not t
https://bugs.kde.org/show_bug.cgi?id=402017
--- Comment #46 from David Hurka ---
This means reverting 559836c3 would make Okular work nicely with Firefox in
many cases, but probably not all cases.
I think we can agree on some priorities now?
1. Work nicely with Firefox in many cases (I. e
https://bugs.kde.org/show_bug.cgi?id=402017
--- Comment #48 from David Hurka ---
Sven wrote:
> if they do open("filename.tmp"), write(), close(),
> rename("filename.tmp", "filename"), you get the old contents,
> because the new contents are in a *different
https://bugs.kde.org/show_bug.cgi?id=423360
--- Comment #2 from David Hurka ---
I marked all the pixmaps fetched by PagePainter, to understand how tiling
works.
* A rounded rectangle precisely marks the tile outline.
* Two “measuring tapes” show me that the pixmaps are shown in
their correct
https://bugs.kde.org/show_bug.cgi?id=423360
--- Comment #3 from David Hurka ---
(In reply to Albert Astals Cid from comment #1)
> > Page is always shown, at least where it is already rendered
>
> That's a wrong expectation, at some point we need to evict pages already
&
https://bugs.kde.org/show_bug.cgi?id=424714
--- Comment #2 from David Hurka ---
Settings -> Configure Shortcuts... should work?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=424810
Bug ID: 424810
Summary: Assert crash when selecting Stamp quick annotation
tool
Product: okular
Version: 1.10.80
Platform: Compiled Sources
OS: Linux
S
https://bugs.kde.org/show_bug.cgi?id=424810
David Hurka changed:
What|Removed |Added
Summary|Assert crash when selecting |Assert crash when selecting
https://bugs.kde.org/show_bug.cgi?id=424810
David Hurka changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/grap |
|hics/okular/commit/280fe3c7
https://bugs.kde.org/show_bug.cgi?id=424810
David Hurka changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
Albert wrote:
> For example, you sign a pdf that says "sign to get your annual bonus" and
> then the PDF is modified to say "you're fired" and still have your
> signature on it.
>
> https://pdf-insecurity.org/download/exploits-shadow/hide.zip
>
> When opening the "forged" PDF file on Okular we cu
https://bugs.kde.org/show_bug.cgi?id=421206
--- Comment #4 from David Hurka ---
I got an idea: On some task managers you can right-click the second Okular
entry, and go to More Actions -> [x] Fullscreen. If you uncheck Fullscreen,
does WebRTC work then?
--
You are receiving this mail beca
> > 1) Okular is provided AS IS and WITHOUT WARRANTY, right?
>
> I'm confused as to why you brought this up.
>
> Are we going to answer "Okular is provided AS IS and WITHOUT WARRANTY,
> right?" to all the bugs we have in bugzilla and close them?
I don’t think that would be nice, and not the purp
https://bugs.kde.org/show_bug.cgi?id=425075
David Hurka changed:
What|Removed |Added
Summary|"Straight line" annotation |Internal annotat
https://bugs.kde.org/show_bug.cgi?id=425099
--- Comment #1 from David Hurka ---
Created attachment 130713
--> https://bugs.kde.org/attachment.cgi?id=130713&action=edit
Internal link tooltip
Do you mean tooltips on hovering an internal link, like this?
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=384695
--- Comment #4 from David Hurka ---
I can’t find where Okular could handle the Alt key, so I think this is handled
in Qt. But it is not documented in QWheelEvent or QScroller, and I can’t find
it in Qt::ApplicationAttributes. Upstream bug?
--
You are
https://bugs.kde.org/show_bug.cgi?id=424817
--- Comment #18 from David Hurka ---
I don’t think there is any bug, but just that Poppler uses the available
algorithms in e. g. the Qt painting framework, instead of complicated
cutting-edge alternatives which *might* perform *slightly* better
https://bugs.kde.org/show_bug.cgi?id=425170
--- Comment #1 from David Hurka ---
I never used a touchscreen, but scrolling with two fingers should work fine.
Did you try that?
AFAIK two finger gestures are sent as “pinch” gesture event first, and then
Okular just needs to process and accept this
https://bugs.kde.org/show_bug.cgi?id=425148
--- Comment #4 from David Hurka ---
(In reply to Albert Astals Cid from comment #1)
> Sure, valid issue, but at this point how many people are left using such old
> versions that this is actually an issue we want to spend time fixing?
Yes, I th
https://bugs.kde.org/show_bug.cgi?id=425188
--- Comment #3 from David Hurka ---
Now my theory is that it will crash when you enable tabs and open a file from
File -> Open. Right? (Settings -> Configure Okular -> General -> Open new files
in tabs)
QScroller appears to access screen()
> I tried
> kwriteconfig5 --group RecentDocuments --key MaxEntries 40
Maybe RecentDocuments is not correct? In shell.cpp it says:
> m_recent->saveEntries(KSharedConfig::openConfig()->group("Recent Files"));
(shell/shell.cpp:313)
https://bugs.kde.org/show_bug.cgi?id=425354
--- Comment #1 from David Hurka ---
> 1. The "Quick annotations" no longer stays fixed to the side of the document
> when clicked. Now it's a pop-up menu that hides after selecting a tool. Is
> this by design? Because it'
https://bugs.kde.org/show_bug.cgi?id=425438
--- Comment #1 from David Hurka ---
We thought the new toolbar was great. You are the second one who complains.
As a quick suggestion, I would add another toolbar which holds just the quick
annotation tools. These tools could be triggered by clicking
> 3. I do not see any options for kreadconfig5 to dump existing groups
> nor existing keys.
> It seems to require that you know exactly what groups and keys exist in
> advance.
> Am I missing something?
The settings are stored in ~/.config/okularrc or similar.
In that file search for [Recent Files
https://bugs.kde.org/show_bug.cgi?id=425593
David Hurka changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|REPORTED
Hi,
the text selection color is taken from the system color palette, so you have
an option to change it through System Settings. The problem is that selection
rectangles are painted in Multiply composition mode, which is invisible on
black background, and also at blue on green foreground. :(
T
901 - 1000 of 1170 matches
Mail list logo
