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. 'rasteriz
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=432611
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #4
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=432159
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=431847
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #2
https://bugs.kde.org/show_bug.cgi?id=431848
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=429635
--- Comment #6 from Oliver Sander ---
I asked Leonard for clarification, and here is his answer:
> To avoid misunderstanding: Do you mean that a reader should process *all*
> actions (in the order you describe), or just the first one?
We sho
https://bugs.kde.org/show_bug.cgi?id=430394
Bug ID: 430394
Summary: Error at shutdown: NSS_Shutdown failed
Product: okular
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
https://bugs.kde.org/show_bug.cgi?id=429635
--- Comment #4 from Oliver Sander ---
Here is his answer:
"The order of the Annotations in the Annots array in the page dictionary
defines the order in which rendering and hit testing is performed. However,
there is nothing that precludes you
https://bugs.kde.org/show_bug.cgi?id=429635
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #2
https://bugs.kde.org/show_bug.cgi?id=430038
Oliver Sander changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=195083
Oliver Sander changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=193916
Oliver Sander changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
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=429197
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #3
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=370217
Oliver Sander changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
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=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=427903
Oliver Sander changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
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=427737
Oliver Sander changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
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=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=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
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=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=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=427356
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #2
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=420842
Oliver Sander changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution
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=423702
--- Comment #3 from Oliver Sander ---
That's possible. What do you set QT_SCREEN_SCALE_FACTORS to?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=423702
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=419221
--- Comment #4 from Oliver Sander ---
This was fixed by ef488d334ea9fe55d821c9a400bbe325981cd856, wasn't it?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=421159
--- Comment #12 from Oliver Sander ---
Thank you! There is a now a test at
https://invent.kde.org/graphics/okular/merge_requests/188
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=421159
--- Comment #10 from Oliver Sander ---
Thanks, I hadn't heard of of xdotool. But I need something that works from
within the QTest framework. And yes, gitlab does run the autotests.
--
You are receiving this mail because:
You are watching al
https://bugs.kde.org/show_bug.cgi?id=421159
--- Comment #8 from Oliver Sander ---
I tried to write a unit test for this, but I failed to find a way to send wheel
events to the PageView object. This seems to be a known problem:
https://stackoverflow.com/questions/50996997/how-to-simulate
https://bugs.kde.org/show_bug.cgi?id=421634
Oliver Sander changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=305534
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #20
https://bugs.kde.org/show_bug.cgi?id=421437
--- Comment #2 from Oliver Sander ---
I did some initial investigations at
https://invent.kde.org/graphics/okular/-/merge_requests/176.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=421755
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #2
https://bugs.kde.org/show_bug.cgi?id=421354
--- Comment #4 from Oliver Sander ---
Does https://invent.kde.org/graphics/okular/merge_requests/169 fix it? I
cannot check myself -- the bug doesn't show up here.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=421984
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #4
https://bugs.kde.org/show_bug.cgi?id=421482
Oliver Sander changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=421634
--- Comment #6 from Oliver Sander ---
I just noticed something interesting: When scaling my display with the control
center GUI, it sets
~> echo $QT_SCREEN_SCALE_FACTORS
eDP-1=1.5;DP-1=1.5;HDMI-1=1.5;HDMI-2=1.5;
(and QT_SCALE_FACTOR is unset).
https://bugs.kde.org/show_bug.cgi?id=421634
--- Comment #5 from Oliver Sander ---
I confirm that the problem goes away when I set QT_SCALE_FACTOR instead of
QT_SCREEN_SCALE_FACTORS. However, I don't usually set these variables per
hand. Rather, I use the slider in the control center, and
https://bugs.kde.org/show_bug.cgi?id=421634
Oliver Sander changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=421634
Bug ID: 421634
Summary: Presentation mode misrendering with two monitors and
screen scaling
Product: okular
Version: unspecified
Platform: Other
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=421468
Oliver Sander changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/kde
https://bugs.kde.org/show_bug.cgi?id=421468
--- Comment #3 from Oliver Sander ---
Thanks for testing!
> It is hard to say if it is worth implementing this for a regular user though.
I'd say "definitely": People do request it, and people who don't need it are
not bothered
https://bugs.kde.org/show_bug.cgi?id=421468
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=421484
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=421430
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #6
https://bugs.kde.org/show_bug.cgi?id=421413
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #2
https://bugs.kde.org/show_bug.cgi?id=421103
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
Resolution
https://bugs.kde.org/show_bug.cgi?id=421102
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
Status
https://bugs.kde.org/show_bug.cgi?id=361740
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #6
https://bugs.kde.org/show_bug.cgi?id=420183
--- Comment #3 from Oliver Sander ---
Sorry, but I am not an Ubuntu expert, and I don't know whether they ship a new
enough version somewhere.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=420183
Oliver Sander changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=419376
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #2
https://bugs.kde.org/show_bug.cgi?id=419221
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #2
https://bugs.kde.org/show_bug.cgi?id=410723
--- Comment #20 from Oliver Sander ---
>Can you please describe how to use the line tool in the presentation mode? I
>don't see any option.
In presentation mode, move the cursor to the upper edge of this screen. This
will make a too
https://bugs.kde.org/show_bug.cgi?id=419095
Oliver Sander changed:
What|Removed |Added
Status|REPORTED|RESOLVED
CC
https://bugs.kde.org/show_bug.cgi?id=418255
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #7
https://bugs.kde.org/show_bug.cgi?id=418527
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=418496
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=418017
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=417821
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=416796
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #8
https://bugs.kde.org/show_bug.cgi?id=403643
--- Comment #20 from Oliver Sander ---
> Other ways of debugging could be to collect more data by means of a remotely
> executed gdb script or even a remote gdb session. But both have severe
> privacy/security implications, so I'm
https://bugs.kde.org/show_bug.cgi?id=403643
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #3
https://bugs.kde.org/show_bug.cgi?id=416229
--- Comment #8 from Oliver Sander ---
> At some point we should either remove trim margins or someone should fix all
> its bugs
BTW: Where is the code that determines what the margin is?
--
You are receiving this mail because:
You are watchi
https://bugs.kde.org/show_bug.cgi?id=415502
Oliver Sander changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=416229
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=415502
--- Comment #9 from Oliver Sander ---
Thanks. The merge request now has the new code in #ifdefs. Somebody with a
post 5.61 frameworks installation please check the code for me.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=415502
--- Comment #7 from Oliver Sander ---
That's not a literal recommendation, right? main.cpp:40 checks for a particular
Qt version. But we need to check for a particular frameworks version, right?
How do I do that?
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=415502
--- Comment #5 from Oliver Sander ---
For a newbie: How would the proper '#ifdef' condition look like?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=414701
Oliver Sander changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution
https://bugs.kde.org/show_bug.cgi?id=415401
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #6
https://bugs.kde.org/show_bug.cgi?id=415834
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #2
https://bugs.kde.org/show_bug.cgi?id=415502
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=415468
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #1
https://bugs.kde.org/show_bug.cgi?id=415340
Oliver Sander changed:
What|Removed |Added
Status|REPORTED|CONFIRMED
CC
https://bugs.kde.org/show_bug.cgi?id=415012
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #6
https://bugs.kde.org/show_bug.cgi?id=414701
--- Comment #4 from Oliver Sander ---
Kezi, do you think you can find the cause for the problem in short time?
Otherwise we may have to revert your patch until we got the regressions sorted
out. Thanks!
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=413989
Oliver Sander changed:
What|Removed |Added
Resolution|--- |FIXED
Latest Commit
https://bugs.kde.org/show_bug.cgi?id=414183
Oliver Sander changed:
What|Removed |Added
Resolution|--- |FIXED
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=263042
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #17
https://bugs.kde.org/show_bug.cgi?id=413695
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #5
https://bugs.kde.org/show_bug.cgi?id=400473
--- Comment #6 from Oliver Sander ---
Can you still reproduce this with the patch
https://invent.kde.org/kde/okular/merge_requests/57 ?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=413591
Oliver Sander changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/kde
https://bugs.kde.org/show_bug.cgi?id=413591
--- Comment #8 from Oliver Sander ---
Fix: https://invent.kde.org/kde/okular/merge_requests/57
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=413591
--- Comment #4 from Oliver Sander ---
Longer answer: I don't care which time zone the time is saved in. But the
pop-up note simply says "13:14" even though my clock said "14:14" when I wrote
the annotation.
--
You are receivi
https://bugs.kde.org/show_bug.cgi?id=413591
Oliver Sander changed:
What|Removed |Added
Resolution|WAITINGFORINFO |FIXED
--- Comment #3 from Oliver Sander
https://bugs.kde.org/show_bug.cgi?id=413591
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
Ever confirmed
https://bugs.kde.org/show_bug.cgi?id=412957
--- Comment #6 from Oliver Sander ---
... and the problem happens with different annotation tools, too.
For example, with line annotations. That's because the calculations in
LineAnnotationPainter (pagepainter.cc:990ff) are not taking the d
https://bugs.kde.org/show_bug.cgi?id=412957
Oliver Sander changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Ever confirmed|0
101 - 200 of 470 matches
Mail list logo
