https://bugs.kde.org/show_bug.cgi?id=486681
--- Comment #3 from Oliver Sander ---
Thank you! Please also attach the LaTeX source file.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=486681
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=482363
--- Comment #11 from Oliver Sander ---
Is this maybe a font issue? Because I do see the checkmark in the box even
with disabled 'forms' mode.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=482363
--- Comment #8 from Oliver Sander ---
Do you have access to Adobe professional? Then you could try to strip the
problematic of all the confidential parts. Really, the/a file is needed to fix
this.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=482363
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #6
https://bugs.kde.org/show_bug.cgi?id=478540
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=474889
Bug ID: 474889
Summary: Form field misuse leads to 'NaN' which won't disappear
Classification: Applications
Product: okular
Version: 23.08.1
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=474888
--- Comment #1 from Oliver Sander ---
Created attachment 161879
--> https://bugs.kde.org/attachment.cgi?id=161879=edit
Acrobat security settings
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=474888
Bug ID: 474888
Summary: Signing requires (empty) password in document that has
password-restriction for modification
Classification: Applications
Product: okular
Version: unspecified
https://bugs.kde.org/show_bug.cgi?id=474448
Oliver Sander changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=474448
--- Comment #2 from Oliver Sander ---
Thank you for your help.
I kinda do understand why this is difficult to implement. From a user
perspective, however, the behavior is puzzling: There is something that looks
like a cursor in an editor, but I
https://bugs.kde.org/show_bug.cgi?id=474448
Bug ID: 474448
Summary: Wish: Allow cursor placement by mouse click in the
current command
Classification: Applications
Product: konsole
Version: unspecified
Platform: Debian
https://bugs.kde.org/show_bug.cgi?id=465055
--- Comment #24 from Oliver Sander ---
I would still be interested to see what your Utils::realDpi method does. Have
you been able to get your local Okular to link yet?
Looking at the code again I see that if the system reports different dpi for x
https://bugs.kde.org/show_bug.cgi?id=471422
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
Ever confirmed
https://bugs.kde.org/show_bug.cgi?id=470734
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #2
https://bugs.kde.org/show_bug.cgi?id=126942
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #3
https://bugs.kde.org/show_bug.cgi?id=470108
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=465055
--- Comment #21 from Oliver Sander ---
Did you get Okular to build and link on your computer in the meantime? My
apologies, but I am not the one who can help with linker problems.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=461371
--- Comment #5 from Oliver Sander ---
I asked the colleague I mentioned above to test this, and it seems that the
issue is indeed fixed for us as well. Thank you!
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=469044
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=468819
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #3
https://bugs.kde.org/show_bug.cgi?id=468112
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #2
https://bugs.kde.org/show_bug.cgi?id=468017
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=467328
--- Comment #13 from Oliver Sander ---
1) Yes, poppler is used
2) On Windows, rasterization resolution follows the printer. Elsewhere, 300dpi
is hardcoded.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=467328
--- Comment #6 from Oliver Sander ---
I fully agree that `force rasterization` is only a workaround.
Okular currently converts pdf files to postscript and sends that to the printer
(I forgot why exactly). Presumably it is the conversion step that goes
https://bugs.kde.org/show_bug.cgi?id=467328
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #4
https://bugs.kde.org/show_bug.cgi?id=459174
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #8
https://bugs.kde.org/show_bug.cgi?id=465055
--- Comment #15 from Oliver Sander ---
Building Okular is described at https://okular.kde.org/build-it/
> But I guess, when I compile my own okular, it will display a circle -
> murphy's law :-)
That's possible. But then you will have fre
https://bugs.kde.org/show_bug.cgi?id=465055
--- Comment #13 from Oliver Sander ---
Relax. This is just very difficult to debug without being able to reproduce it
locally.
Access to dpi information is gathered in the method `realDpi` in the file
`utils.cpp`. Are you able to build your own
https://bugs.kde.org/show_bug.cgi?id=465055
--- Comment #8 from Oliver Sander ---
What happens when you swap the monitors?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=465055
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #6
https://bugs.kde.org/show_bug.cgi?id=464716
Oliver Sander changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=443403
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #15
https://bugs.kde.org/show_bug.cgi?id=423360
--- Comment #9 from Oliver Sander ---
Is this still an issue now that
https://invent.kde.org/graphics/okular/-/merge_requests/665 has been merged?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=460681
Oliver Sander changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=462579
Oliver Sander changed:
What|Removed |Added
Resolution|WAITINGFORINFO |FIXED
CC
https://bugs.kde.org/show_bug.cgi?id=457739
Oliver Sander changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=462304
--- Comment #7 from Oliver Sander ---
Yes please. You should be able to reproduce the bug with the `pdftoppm` tool
(which is part of poppler). That way, your bug report becomes independent from
Okular.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=462304
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #5
https://bugs.kde.org/show_bug.cgi?id=436742
Oliver Sander changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/grap
https://bugs.kde.org/show_bug.cgi?id=315930
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #11
https://bugs.kde.org/show_bug.cgi?id=461371
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
Status
https://bugs.kde.org/show_bug.cgi?id=460681
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=411877
--- Comment #18 from Oliver Sander ---
(In reply to Oliver Sander from comment #14)
> I just checked again. The input really is split across the two screens.
I checked again yesterday, with an updated stack from Debian testing. This
time, the in
https://bugs.kde.org/show_bug.cgi?id=458723
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #7
https://bugs.kde.org/show_bug.cgi?id=458722
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #5
https://bugs.kde.org/show_bug.cgi?id=455462
Oliver Sander changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=455462
Oliver Sander changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=455309
--- Comment #2 from Oliver Sander ---
Fair enough. But not all people that teach in this lecture room can be asked
to apply a CLI trick. However, saying "go to the 'settings' page and select
mode '0'" would be acceptable.
--
You are
https://bugs.kde.org/show_bug.cgi?id=411877
--- Comment #14 from Oliver Sander ---
I just checked again. The input really is split across the two screens.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=455462
--- Comment #4 from Oliver Sander ---
When running firefox and thunderbird with MOZ_ENABLE_WAYLAND=1 I indeed do not
have the problem.
However, neither program then respects the KDE screen scaling setting, and they
become very strenous to use on my
https://bugs.kde.org/show_bug.cgi?id=455462
--- Comment #2 from Oliver Sander ---
Does xwininfo needs some special options to display? I don't see anything
related to window managers in its output (see below).
In any case, as far as I know these windows are XWayland.
~> xwininfo
xwini
https://bugs.kde.org/show_bug.cgi?id=455462
Bug ID: 455462
Summary: Wayland: Wrong keyboard layout for non-KDE programs at
login
Product: kwin
Version: 5.24.5
Platform: Other
OS: Linux
Status:
https://bugs.kde.org/show_bug.cgi?id=455309
Bug ID: 455309
Summary: Wayland: Allow to set InputMode of input device
Product: systemsettings
Version: 5.24.90
Platform: Debian testing
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=411877
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #11
https://bugs.kde.org/show_bug.cgi?id=455115
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #6
https://bugs.kde.org/show_bug.cgi?id=449717
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #4
https://bugs.kde.org/show_bug.cgi?id=383651
--- Comment #33 from Oliver Sander ---
If all you need is printing, then enabling 'force rasterization' in the print
dialog will probably circumvent the problem for you.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=450887
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=449808
Oliver Sander changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=449043
--- Comment #6 from Oliver Sander ---
I confirm this. Underlining both lines separately makes both underlines thin.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=449043
--- Comment #4 from Oliver Sander ---
Created attachment 145852
--> https://bugs.kde.org/attachment.cgi?id=145852=edit
Small pdf file showing the problem
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=449043
Oliver Sander changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=448735
--- Comment #3 from Oliver Sander ---
I don't have a Windows machine to test with anyways. Can you, by any chance,
embed some file in a test pdf file on Windows and upload that? That should
fail on my Linux, right?
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=448735
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=448448
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=447589
Oliver Sander changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=446549
--- Comment #5 from Oliver Sander ---
I understand your point, but please no additional dialog box. It would mean an
additional click for everyone.
How about:
* An additional menu entry like "graphically sign" right next to "
https://bugs.kde.org/show_bug.cgi?id=446549
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #2
https://bugs.kde.org/show_bug.cgi?id=443446
--- Comment #3 from Oliver Sander ---
I think you can already have such a button. Go to preference -> toolbar
settings -> anotation toolbar, and there should be 'forward' and 'backward'
actions.
[The menu names may be slightly different, I tran
https://bugs.kde.org/show_bug.cgi?id=443446
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=442280
--- Comment #26 from Oliver Sander ---
Can you guys please move the mupdf discussion elsewhere? While it is certainly
interesting, it is only tangentially related to this bug.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438198
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--
You
https://bugs.kde.org/show_bug.cgi?id=442280
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #10
https://bugs.kde.org/show_bug.cgi?id=420571
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #4
https://bugs.kde.org/show_bug.cgi?id=409644
--- Comment #11 from Oliver Sander ---
> Why is devicePixelRatio here forced to be 1...?
That part of the code was reworked in a recent merge request. Maybe it'll help
you:
https://invent.kde.org/graphics/okular/-/merge_requests/371
--
https://bugs.kde.org/show_bug.cgi?id=409644
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #6
https://bugs.kde.org/show_bug.cgi?id=438980
--- Comment #14 from Oliver Sander ---
> But not in 20.12 maybe?
No, not in 20.12. And I never tested it myself on Windows.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438980
--- Comment #12 from Oliver Sander ---
> Okular uses qApp->devicePixelRatio() in some places to get the screen scaling.
I thought I fixed all that, but I may be wrong. The only remaining
per-screen-scaling issue I know of is
https://invent.k
https://bugs.kde.org/show_bug.cgi?id=438980
--- Comment #9 from Oliver Sander ---
What about the nightly builds mentioned at
https://okular.kde.org/download/
?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438980
Oliver Sander changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=438980
--- Comment #5 from Oliver Sander ---
Is it blurry on both monitors? Is it blurry if you set scaling to 100%?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=438980
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=438923
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #7
https://bugs.kde.org/show_bug.cgi?id=437926
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #6
https://bugs.kde.org/show_bug.cgi?id=436709
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=436301
Oliver Sander changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=436301
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=402017
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #66
https://bugs.kde.org/show_bug.cgi?id=435669
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=435568
--- Comment #4 from Oliver Sander ---
Yes, it was more subtle than simply "the buttons are wrong". Without testing
again I think what happened was that the dialog was wrong when opened for the
first time after program start. When op
https://bugs.kde.org/show_bug.cgi?id=435568
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #2
https://bugs.kde.org/show_bug.cgi?id=435120
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #10
https://bugs.kde.org/show_bug.cgi?id=434613
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #2
https://bugs.kde.org/show_bug.cgi?id=434111
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=432738
--- Comment #7 from Oliver Sander ---
Hard to tell. It's a pretty fragile construction. Unfortunately I am not
skilled enough to help you debug this.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=432159
--- Comment #3 from Oliver Sander ---
See https://invent.kde.org/graphics/okular/-/merge_requests/368 (which is think
is related).
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=433003
--- Comment #2 from Oliver Sander ---
See
https://invent.kde.org/graphics/okular/-/merge_requests/368
Doesn't fix the problem reported here, but it is related.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=433003
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=432738
--- Comment #5 from Oliver Sander ---
> why
Believe it or not, but 'rasterization' is actually a completely different way
of printing. The standard way is to convert the file to postscript and send
that to the printer. 'rasterization' rend
1 - 100 of 462 matches
Mail list logo
