https://bugs.kde.org/show_bug.cgi?id=370217
--- Comment #5 from Oliver Sander ---
No, as I learned eventually this happens on master, too.
Actually, on master it is worse, because there, the line-while-you-draw always
has width 1, irrespective of what the line width settings say. Presumably
https://bugs.kde.org/show_bug.cgi?id=372457
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=351443
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--
You are
https://bugs.kde.org/show_bug.cgi?id=300992
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #19
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=450887
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
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=411877
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #11
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=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: RE
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=467328
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #4
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
--- 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=468017
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
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=468819
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=126942
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #3
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=469044
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
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=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=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=460681
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
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=465055
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #6
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
--- 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 #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 h
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=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 are
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=486681
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
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=446549
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #2
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 "digit
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=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
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=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=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 acceptabl
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=458722
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #5
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=442280
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #10
https://bugs.kde.org/show_bug.cgi?id=438198
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--
You are
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=455462
Oliver Sander changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
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=443446
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
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 slight
https://bugs.kde.org/show_bug.cgi?id=305534
Oliver Sander changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|REOPENED
https://bugs.kde.org/show_bug.cgi?id=432611
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #4
https://bugs.kde.org/show_bug.cgi?id=432738
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. 'rasteriz
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=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=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=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=420842
Oliver Sander changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=426679
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=427356
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #2
https://bugs.kde.org/show_bug.cgi?id=427356
--- Comment #4 from Oliver Sander ---
Drawings in presentation mode are not as pretty as in other notetaking
applications such as xournal++ or the Qt tablet example. Part of the reason is
that Okular doesn't support changing the line width wit
https://bugs.kde.org/show_bug.cgi?id=423360
--- Comment #5 from Oliver Sander ---
> @Oliver: You wrote
> https://invent.kde.org/graphics/okular/-/merge_requests/134#note_110955 . Do
> you remember whether you recently updated across Poppler 0.63?
No, I am quite certain that I
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
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #6
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=438923
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #7
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=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
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
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
--- 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 #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=436301
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=436709
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=427652
Bug ID: 427652
Summary: Strangely worded KMessageBox
Product: okular
Version: 1.11.2
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priori
https://bugs.kde.org/show_bug.cgi?id=427652
--- Comment #2 from Oliver Sander ---
Thanks for checking. Apparently it really is a duplicate of
https://bugs.kde.org/show_bug.cgi?id=420189 . I can reproduce what is
described there: The buttons are only wrong when the message box appears for
the
https://bugs.kde.org/show_bug.cgi?id=427652
--- Comment #4 from Oliver Sander ---
It must somehow be related to the translation. With
LANGUAGE=en_US okular
the message box works as expected.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=420189
--- Comment #7 from Oliver Sander ---
I'm the reporter of Bug 427652, which is the same problem, but in Okular.
Unfortunately I have a tiny bit of a nonstandard system ATM:
* Okular is compiled from source
* my base system is Debian testing
https://bugs.kde.org/show_bug.cgi?id=427737
Oliver Sander changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=427903
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=427903
Oliver Sander changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=414701
--- Comment #17 from Oliver Sander ---
I think I remember Kezi complaining about the ViewPort setting location history
events itself, too. Wouldn't it make more sense to make the code that triggers
the location change request explicitly that th
https://bugs.kde.org/show_bug.cgi?id=428116
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=435568
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #2
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 opened ag
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=402017
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #66
https://bugs.kde.org/show_bug.cgi?id=305534
--- Comment #28 from Oliver Sander ---
It could, but that would be more work than simply fixing the poppler bug.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=370217
Oliver Sander changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=370217
--- Comment #9 from Oliver Sander ---
Sorry, but I never found the time to try that.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=429197
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #3
https://bugs.kde.org/show_bug.cgi?id=171463
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #13
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=474448
Oliver Sander changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|REPORTED
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
1 - 100 of 494 matches
Mail list logo
