[okular] [Bug 486681] Display comments created by latex pdfcomment
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.
[okular] [Bug 486681] Display comments created by latex pdfcomment
https://bugs.kde.org/show_bug.cgi?id=486681 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- Please provide a simple test file. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 482363] Checkboxes on forms do not show as checked even though they are checked
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.
[okular] [Bug 482363] Checkboxes on forms do not show as checked even though they are checked
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 watching all bug changes.
[okular] [Bug 482363] Checkboxes on forms do not show as checked even though they are checked
https://bugs.kde.org/show_bug.cgi?id=482363 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #6 from Oliver Sander --- You can find the word processor that generated your particular document by looking at "File -> Properties". -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 478540] Can't edit form field after entering invalid character
https://bugs.kde.org/show_bug.cgi?id=478540 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- Is this possibly a duplicate of https://bugs.kde.org/show_bug.cgi?id=474889 ? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 474889] New: Form field misuse leads to 'NaN' which won't disappear
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 Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: oliver.san...@tu-dresden.de Target Milestone: --- Created attachment 161880 --> https://bugs.kde.org/attachment.cgi?id=161880=edit The problematic document I have a pdf document with a form field that should (I guess) only accept numbers. By deliberate entering a non-digit I can make it show NaN. Afterwards, it is not possible to remove this NaN again. STEPS TO REPRODUCE 1. Open the attached document; click on 'show forms' 2. Click on the top left square (below "70 Liter") 3. Enter the letter X 4. Click outside of that square --> the X changes to NaN 5. Click into the square again --> the NaN changes back to X 6. Replace the X by a 2 7. Click on "hide forms" OBSERVED RESULT Instead of the number "2" the "NaN" is shown again. EXPECTED RESULT I am not quite sure what to expect. Should I be prevented from entering non-digits in the first place? At the very least I would expect to see a "2" at the end of the seven steps, not NaN. SOFTWARE/OS VERSIONS Betriebssystem: Debian GNU/Linux 12 KDE-Plasma-Version: 5.27.5 KDE-Frameworks-Version: 5.103.0 Qt-Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 474888] Signing requires (empty) password in document that has password-restriction for modification
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.
[okular] [Bug 474888] New: Signing requires (empty) password in document that has password-restriction for modification
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 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: oliver.san...@tu-dresden.de Target Milestone: --- Created attachment 161878 --> https://bugs.kde.org/attachment.cgi?id=161878=edit The problematic document The attached pdf file contains a signature form field. However, when trying to sign it I am asked for a password. Using the empty string as the password allows me to sign the document. The reason is apparently that in this document the *modification* of the document is password-restricted. Please see the attached Acrobat security settings (German only, sorry. The blue line says: "Admissible changes: Filling-out form fields and signing existing signature fields".) SOFTWARE/OS VERSIONS Betriebssystem: Debian GNU/Linux 12 KDE-Plasma-Version: 5.27.5 KDE-Frameworks-Version: 5.103.0 Qt-Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 474448] Wish: Allow cursor placement by mouse click in the current command
https://bugs.kde.org/show_bug.cgi?id=474448 Oliver Sander changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #4 from Oliver Sander --- Oh, indeed! I should have read the documentation even more thoroughly. It is a bit nonobvious to set up, but then it does exactly what I wanted. Thank you both! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 474448] Wish: Allow cursor placement by mouse click in the current command
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 cannot move it by mouse clicks. Thanks for pointing me to the QuickCommands plugin. It feels clunky compared to my original wish, but it will nevertheless be helpful for me. I quickly found several bugs concerning the plugin (for example, shift-ctrl-F1 will only open it if the menu bar is not hidden). If you care I can file separate bug reports. Feel free to close this issue if you think that it is unimplementable. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 474448] New: Wish: Allow cursor placement by mouse click in the current command
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 stable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: oliver.san...@tu-dresden.de Target Milestone: --- I sometimes find myself working with very long command lines in konsole. One example are compiler invocations which can easily get 700 letters long. In my workflow, I copy them from the clipboard into Konsole and then I need to edit them. The problem is that it is very tedious to move around in such long lines. I can jump to the beginning and to the end of the line with the Pos1 and End keys. To move around I can go left and right with the arrow-left and arrow-right keys, and that's apparently it. Unfortunately, moving around in such a long line with the two arrow keys only can take a long time. My wish is that when I click onto the current command line the Konsole cursor moves to the position of the mouse cursor, just as it does in Kate or LibreOffice. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 465055] All PDFs are shown stretched in y-axis
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 and y (which are then ignored) it issues a warning: qCDebug(OkularCoreDebug) << "QScreen calculation returned a non square dpi." << res << ". Falling back"; Do you see this message when you enable Okular debug output with kdebugdialog5? (KDE gurus: please correct me if something else is needed to enable the warning). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 471422] Okular crashes when opening specific PDF files
https://bugs.kde.org/show_bug.cgi?id=471422
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
Ever confirmed|0 |1
Status|REPORTED|CONFIRMED
--- Comment #1 from Oliver Sander ---
Backtrace:
#0 getCertificateInfoFromCERT (cert=0x5679e5e0)
at /home/sander/poppler/poppler/NSSCryptoSignBackend.cc:619
#1 0x7fffa946d674 in NSSSignatureVerification::getCertificateInfo
(this=0x567776a0)
at /home/sander/poppler/poppler/NSSCryptoSignBackend.cc:658
#2 0x7fffa934bf29 in FormFieldSignature::validateSignature
(this=0x55bade30,
doVerifyCert=doVerifyCert@entry=true,
forceRevalidation=forceRevalidation@entry=false,
validationTime=-1, ocspRevocationCheck=,
enableAIA=enableAIA@entry=false)
at /home/sander/poppler/poppler/Form.cc:2419
#3 0x7fffa934bfd8 in FormWidgetSignature::validateSignature
(this=this@entry=0x567789b0,
doVerifyCert=doVerifyCert@entry=true,
forceRevalidation=forceRevalidation@entry=false,
validationTime=, ocspRevocationCheck=,
enableAIA=enableAIA@entry=false) at
/home/sander/poppler/poppler/Form.cc:578
#4 0x7fffbda685ff in Poppler::FormFieldSignature::validate
(this=this@entry=0x567779b0,
opt=opt@entry=1, validationTime=...) at
/home/sander/poppler/qt5/src/poppler-form.cc:1021
#5 0x7fffbda688f1 in Poppler::FormFieldSignature::validate
(this=0x567779b0,
opt=Poppler::FormFieldSignature::ValidateVerifyCertificate)
at /home/sander/poppler/qt5/src/poppler-form.cc:971
#6 0x7fffbdb11d9d in PopplerFormFieldSignature::PopplerFormFieldSignature
(this=0x56786fc0,
field=std::unique_ptr = {...})
at /home/sander/kde-invent/okular/generators/poppler/formfields.cpp:400
#7 0x7fffbdafe571 in PDFGenerator::getFormFields (this=0x55aaba90,
popplerPage=0x567782c0)
at /home/sander/kde-invent/okular/generators/poppler/generator_pdf.cpp:1934
#8 0x7fffbdaf8603 in PDFGenerator::loadPages (this=0x55aaba90,
pagesVector=..., rotation=0,
clear=false) at
/home/sander/kde-invent/okular/generators/poppler/generator_pdf.cpp:873
--Type for more, q to quit, c to continue without paging--c
#9 0x7fffbdaf7cca in PDFGenerator::init (this=0x55aaba90,
pagesVector=..., password=...)
at /home/sander/kde-invent/okular/generators/poppler/generator_pdf.cpp:734
#10 0x7fffbdaf789a in PDFGenerator::loadDocumentWithPassword
(this=0x55aaba90, filePath=...,
pagesVector=..., password=...)
at /home/sander/kde-invent/okular/generators/poppler/generator_pdf.cpp:678
#11 0x7fffe8207abb in Okular::DocumentPrivate::openDocumentInternal
(this=0x557d8c40,
offer=..., isstdin=false, docFile=..., filedata=..., password=...)
at /home/sander/kde-invent/okular/core/document.cpp:942
#12 0x7fffe8211571 in Okular::Document::openDocument (this=0x557af760,
docFile=..., url=...,
_mime=..., password=...) at
/home/sander/kde-invent/okular/core/document.cpp:2460
#13 0x7fffe04d1184 in Okular::Part::doOpenFile (this=0x556254f0,
mimeA=...,
fileNameToOpenA=..., isCompressedFile=0x7fffd077)
at /home/sander/kde-invent/okular/part/part.cpp:1465
#14 0x7fffe04d20e6 in Okular::Part::openFile (this=0x556254f0)
at /home/sander/kde-invent/okular/part/part.cpp:1599
#15 0x77f50785 in ?? () from /lib/x86_64-linux-gnu/libKF5Parts.so.5
#16 0x77f5187e in KParts::ReadOnlyPart::openUrl(QUrl const&) ()
from /lib/x86_64-linux-gnu/libKF5Parts.so.5
#17 0x7fffe04d3a86 in Okular::Part::openUrl (this=0x556254f0, _url=...,
swapInsteadOfOpening=false) at
/home/sander/kde-invent/okular/part/part.cpp:1825
#18 0x7fffe04d363a in Okular::Part::openUrl (this=0x556254f0, url=...)
at /home/sander/kde-invent/okular/part/part.cpp:1773
#19 0x55572980 in Shell::openUrl (this=0x5578d2c0, url=...,
serializedOptions=...)
at /home/sander/kde-invent/okular/shell/shell.cpp:418
#20 0x555724e0 in Shell::openDocument (this=0x5578d2c0, url=...,
serializedOptions=...)
at /home/sander/kde-invent/okular/shell/shell.cpp:362
#21 0x5556e290 in Okular::main (paths=..., serializedOptions=...)
at /home/sander/kde-invent/okular/shell/okular_main.cpp:216
#22 0x5556b4fc in main (argc=2, argv=0x7fffdc08)
at /home/sander/kde-invent/okular/shell/main.cpp:97
(gdb)
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 470734] Printing is extremely slow (Win10)
https://bugs.kde.org/show_bug.cgi?id=470734 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #2 from Oliver Sander --- > Assumption: Okular sends (large) rendered bitmaps to the printer (sub system > of Windows) where Acrobat Reader sends (small) texts. That's essentially correct. The code is in the method PDFGenerator::print in the file generator_pdf.cpp. Improving the situation is not particularly difficult, but it needs somebody with both the time to do it and a Windows machine. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 126942] Kghostview can't show any overprint preview
https://bugs.kde.org/show_bug.cgi?id=126942 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #3 from Oliver Sander --- Can you please attach an example file? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 470108] Touchscreen zoom not working as expected
https://bugs.kde.org/show_bug.cgi?id=470108 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- See https://invent.kde.org/graphics/okular/-/merge_requests/134 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 465055] All PDFs are shown stretched in y-axis
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 changes.
[okular] [Bug 461371] PDFs digitally signed with Okular become locked in Adobe Acrobat so no one else can sign it
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.
[okular] [Bug 469044] Crash when closing an PDF file with digital sign
https://bugs.kde.org/show_bug.cgi?id=469044 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- Can you try this with a very new poppler and Okular? The signature code is being worked on and your problem may have been fixed already. Also, does this happen with every document with a signature? Can you share such a document? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 468819] The application's title bar is set to the title in the PDF doc, instead of the filename
https://bugs.kde.org/show_bug.cgi?id=468819 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #3 from Oliver Sander --- The sixth option in settings --> okular settings --> general (actual names may differ, my Okular UI is not English) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 468112] Use Cairo backend for Poppler wrapper used in Okular
https://bugs.kde.org/show_bug.cgi?id=468112 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #2 from Oliver Sander --- See https://gitlab.freedesktop.org/poppler/poppler/-/merge_requests/546 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 468017] Percentage value not localised
https://bugs.kde.org/show_bug.cgi?id=468017 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- Is this fixed by your patch https://invent.kde.org/graphics/okular/-/merge_requests/675 ? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 467328] Okular mismanages fonts embedded in PDF document when printing
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.
[okular] [Bug 467328] Okular mismanages fonts embedded in PDF document when printing
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 wrong in your case. If you want to have a look at the code: That's at `generator_pdf.cpp:1366`. There used to be a patch that made Okular send the pdf file straight to the printer, but I can't seem to find it right now. And then there's the official Qt way of printing: Render everything to a `QPrinter` object. Code for that is at https://invent.kde.org/graphics/okular/-/merge_requests/411 , but that has its own set of problems. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 467328] Okular mismanages fonts embedded in PDF document when printing
https://bugs.kde.org/show_bug.cgi?id=467328 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #4 from Oliver Sander --- Printing in Okular is a bit special. I conjecture that you can print your document if you select the 'force rasterization' option in the print dialog. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 459174] okular crashes after signature checking
https://bugs.kde.org/show_bug.cgi?id=459174 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #8 from Oliver Sander --- Without having tried this myself: There has been a great number of bug reports similar to this one, and they have all been solved by updating to newer versions. Please try to get the latest flatpack version of Okular or build it from source and report back if the bug is still there. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 465055] All PDFs are shown stretched in y-axis
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 free time to fix some other Okular bug if you are interested. There are lot's. :-) BTW, have you checked whether your issue persists if you change from X11 to Wayland or vice versa? I don't think hidden config files have anything to do with this, but I may be wrong. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 465055] All PDFs are shown stretched in y-axis
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 Okular (it is not very difficult)? If so, this is the place to start looking. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 465055] All PDFs are shown stretched in y-axis
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.
[okular] [Bug 465055] All PDFs are shown stretched in y-axis
https://bugs.kde.org/show_bug.cgi?id=465055 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #6 from Oliver Sander --- Well, even if it is, it must be something subtle, because most people see a rendering of the circle in just the way it should be. Albert and me, for example. Is your setup a laptop with a built-in screen? Can you reproduce the problem if you use another screen? Another computer? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 464716] Very slow render time on restaurant menu
https://bugs.kde.org/show_bug.cgi?id=464716 Oliver Sander changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- I can confirm the multi-second pauses, even with the recent efficiency improvements in PagePainter. The document is indeed a single page, with custom size 452 x 2529 m. It contains a single image with 2312 x 12943 pixels. Okular apparently renders only the visible parts, and that seems to take a while. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443403] Reduce the size of the digital signature display
https://bugs.kde.org/show_bug.cgi?id=443403 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #15 from Oliver Sander --- This is probably fixed by https://invent.kde.org/graphics/okular/-/merge_requests/537 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 423360] Viewport blinks (flashes, disappears) while scrolling or dragging at moderate or high zoom levels
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.
[okular] [Bug 460681] Laggy scrolling on high DPI display - profiling indicates excessive copying in PagePainter::paintCroppedPageOnPainter
https://bugs.kde.org/show_bug.cgi?id=460681 Oliver Sander changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from Oliver Sander --- Fixed by merging https://invent.kde.org/graphics/okular/-/merge_requests/665 . -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 462579] the barcodes disappear in the printed edition under okular
https://bugs.kde.org/show_bug.cgi?id=462579 Oliver Sander changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED CC||oliver.san...@tu-dresden.de Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 457739] Okular handbook confused on annotations
https://bugs.kde.org/show_bug.cgi?id=457739 Oliver Sander changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/okular/commit/0136eddb ||12151530bd162fd9b8862926a55 ||007e3 Resolution|--- |FIXED --- Comment #7 from Oliver Sander --- Git commit 0136eddb12151530bd162fd9b8862926a55007e3 by Oliver Sander, on behalf of Paul Worrall. Committed on 01/12/2022 at 15:29. Pushed by sander into branch 'master'. Handbook: Select Browse to edit/delete annotations Minor change to handbook to say that the Browse tool has to be selected before you can edit or delete annotations M +2-2doc/index.docbook https://invent.kde.org/graphics/okular/commit/0136eddb12151530bd162fd9b8862926a55007e3 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 462304] Okular and other poppler related tools cannot handle some pdf pages
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 are watching all bug changes.
[okular] [Bug 462304] Okular and other poppler related tools cannot handle some pdf pages
https://bugs.kde.org/show_bug.cgi?id=462304 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #5 from Oliver Sander --- Can you post a poppler bug for this, please? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436742] Involuntary scrolling when annotations encounter edge of page
https://bugs.kde.org/show_bug.cgi?id=436742 Oliver Sander changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/okular/commit/e6002e79 ||8d06cf52a71d9d35716c4d0b9c2 ||82d99 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #4 from Oliver Sander --- Git commit e6002e798d06cf52a71d9d35716c4d0b9c282d99 by Oliver Sander, on behalf of Nikola Nikolic. Committed on 15/11/2022 at 13:30. Pushed by sander into branch 'master'. Fix: Involuntary scrolling when annotations encounter the edge of the page There are three reasons why scrolling happens (first two cases of scrolling are actually due to viewport transition that is triggered by annotation being traslated/created): 1. VisiblePageRect are NormalizedRect and should be represented by four values in [0, 1] interval. Due to rounding errors caused by using QRect, they only reach the [0, 0.999] interval. That means that right and bottom edge of the page are never visible so if annotation is translated along the right/bottom edge viewport transition occurs (fixed in PageView::slotRequestVisiblePixmaps) 2. For freehand line there are some constants (dX, dY) that make a line to be drawn outside the page borders causing viewport transition. Removing these constants solves the problem (fixed in SmoothPathEngine::event) 3. Browse mode is activated as soon as the cursor is moved outside the viewport. Instead, we should forward the move event to the annotation which than can ignore the event (fixed in PageView::mouseMoveEvent) M +8-10 part/annotationtools.cpp M +11 -6part/pageview.cpp https://invent.kde.org/graphics/okular/commit/e6002e798d06cf52a71d9d35716c4d0b9c282d99 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 315930] Ability to sign a PDF with my scanned signature (i.e. picture file) like in Adobe Acrobat
https://bugs.kde.org/show_bug.cgi?id=315930 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #11 from Oliver Sander --- It's in the pipeline: https://invent.kde.org/graphics/okular/-/merge_requests/537 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 461371] PDFs digitally signed with Okular become locked in Adobe Acrobat so no one else can sign it
https://bugs.kde.org/show_bug.cgi?id=461371 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Oliver Sander --- A colleague of mine just confirmed this. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 460681] Laggy scrolling on high DPI display - profiling indicates excessive copying in PagePainter::paintCroppedPageOnPainter
https://bugs.kde.org/show_bug.cgi?id=460681 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- Some of the calls to `setDevicePixelRatio` where probably introduced by me. The deep-copying was not intentional. I am not very proficient in Qt programming, and I wasn't even aware that these calls trigger a deep copy. Does https://invent.kde.org/graphics/okular/-/merge_requests/612 fix your issue by any chance? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411877] Touchscreen input locked to first screen
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 input was *not* split across the two screens. Rather, the input is now exclusively on the wrong screen, as for everybody else in this thread. [shrugs] Operating System: Debian GNU/Linux KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.4 Kernel Version: 5.19.0-2-amd64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 458723] PDF document isn't shown - "Please wait ..." message is shown instead
https://bugs.kde.org/show_bug.cgi?id=458723 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #7 from Oliver Sander --- I haven't checked this particular case, but documents that show this warning message typically contain XFA forms. These forms are described in a document several hundred pages long, and nobody has ever had the nerve to start an open implementation. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 458722] Bad rendering of data matrix code in Okular (blurry in some conditions)
https://bugs.kde.org/show_bug.cgi?id=458722 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #5 from Oliver Sander --- xpdf does not use poppler. Instead, poppler is a (partial) fork of xpdf. The two codes are similar but not identical. To convince yourself that poppler is the culprit try to render the file with `pdftoppm`. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455462] Wayland: Wrong keyboard layout for XWayland programs at login
https://bugs.kde.org/show_bug.cgi?id=455462 Oliver Sander changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #6 from Oliver Sander --- A recent update seems to have fixed this. Thanks to everyone involved! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455462] Wayland: Wrong keyboard layout for non-KDE programs at login
https://bugs.kde.org/show_bug.cgi?id=455462 Oliver Sander changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455309] Wayland: Allow to set InputMode of input device
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 receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411877] Touchscreen input locked to first screen
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.
[plasmashell] [Bug 455462] Wayland: Wrong keyboard layout for non-KDE programs at login
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 hidpi screen. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455462] Wayland: Wrong keyboard layout for non-KDE programs at login
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 xwininfo: Please select the window about which you would like information by clicking the mouse in that window. xwininfo: Window id: 0x180006a "Inbox - oliver.san...@tu-dresden.de - Mozilla Thunderbird" Absolute upper-left X: 1191 Absolute upper-left Y: 41 Relative upper-left X: 0 Relative upper-left Y: 0 Width: 1978 Height: Depth: 32 Visual: 0x351 Visual Class: TrueColor Border width: 0 Class: InputOutput Colormap: 0x1800010 (not installed) Bit Gravity State: NorthWestGravity Window Gravity State: NorthWestGravity Backing Store State: NotUseful Save Under State: no Map State: IsViewable Override Redirect State: no Corners: +1191+41 --1121+41 --1121-0 +1191-0 -geometry 1978x+1191+0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455462] New: Wayland: Wrong keyboard layout for non-KDE programs at login
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: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: oliver.san...@tu-dresden.de
Target Milestone: ---
Created attachment 149841
--> https://bugs.kde.org/attachment.cgi?id=149841=edit
Screenshot of the relevant part of the 'settings' dialog.
My laptop computer has a German keyboard. When I log into a Wayland session,
however, the layout is English for all (many?) non-KDE programs. This includes
in particular Thunderbird, Firefox, and the 'Element' Matrix chat client.
I can get a German layout with the following steps:
1. Open the 'keyboard' part of the system settings program
2. Switch to the second tab ('Belegungen' / Layout(?))
3. Tick the checkbox 'setup layouts' (my translation. In German: 'Belegungen
einrichten').
4. Press apply.
Curiously, it doesn't seem to matter whether the checkbox is ticked or
unticked, as long as I can press 'apply' once.
I'll upload a screenshot of the settings dialong, because I am not sure about
the English names.
https://bugs.kde.org/show_bug.cgi?id=412101 seems closely related, but it is
marked as 'fixed'.
SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.4
Kernel Version: 5.18.0-1-amd64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 455309] New: Wayland: Allow to set InputMode of input device
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 Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: oliver.san...@tu-dresden.de Target Milestone: --- I have a SMART Podium 500, which is a large screen with a stylus: https://support.smarttech.com/docs/hardware/podiums/podium-sp500/en/home.cshtml This device does not work properly out-of-the-box under Wayland: stylus movement is mapped to the entire virtual desktop (which I reported at https://bugs.kde.org/show_bug.cgi?id=411877), and no cursor appears. The friendly folks at libinput have been very helpful at debugging this, and there is lots of technical information at https://gitlab.freedesktop.org/libinput/libinput/-/issues/769 As it turns out, the device has an InputMode setting with integer arguments 0,1,2,3, and right now it doesn't seem like the default value is the best choice. I can set the mode using the `hid-feature` command-line tool, but a GUI somewhere in the system settings would be much more convenient. Of course in an ideal world the correct setting would be somehow detected and selected automatically, but my technical understanding is not sufficient to say whether this is something that I can hope for. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411877] Touchscreen input locked to first screen
https://bugs.kde.org/show_bug.cgi?id=411877 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #11 from Oliver Sander --- FWIW, I have a very similar issue with a SMART Podium 500 device, which is an external screen with a stylus. I can also get it recognized as an absolute pointer device, but then KWin maps the pointer movement to the entire virtual desktop (which comprises the external screen on the left, and my built-in laptop screen on the right). This happens with Plasma 5.24.4 running wayland. The libinput people have been very helpful debugging this. There is lots of technical information at https://gitlab.freedesktop.org/libinput/libinput/-/issues/769 Do you think this is the same issue, or should I open a separate report? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 455115] Show pop-up notes text more directly
https://bugs.kde.org/show_bug.cgi?id=455115 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #6 from Oliver Sander --- >From reading the description of your workflow it seems that your last suggestion (having the annotation texts visible/accessible from the review pane, in the side bar) seems most helpful. In an ideal world you would even be able to navigate there with the keyboard alone, for increased speed. Would you be able to code such a feature? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 449717] When zooming with 2 fingers on a touchscreen, Okular also scrolls through the document, causing me to lose my place.
https://bugs.kde.org/show_bug.cgi?id=449717 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #4 from Oliver Sander --- I reckon this is fixed by https://invent.kde.org/graphics/okular/-/merge_requests/134 Somebody would need to finish that. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 383651] Custom/image stamp annotations are not saved into the PDF file in a way that can be printed or that other readers can see
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.
[okular] [Bug 450887] Change font for plain text files
https://bugs.kde.org/show_bug.cgi?id=450887 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- You can do that. It's under "preferences -> set up display modules -> text" (or something like that, I'm translating from my German UI). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 449808] butt caps shown as rounded
https://bugs.kde.org/show_bug.cgi?id=449808 Oliver Sander changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM CC||oliver.san...@tu-dresden.de --- Comment #3 from Oliver Sander --- This appear to be a bug in poppler, the library used by Okular to render pdf files. I can reproduce the problem with pdftoppm 20.09.0. Can you please open a bug at the poppler bugtracker: https://gitlab.freedesktop.org/poppler/poppler/-/issues Thank you! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 449043] underline
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.
[okular] [Bug 449043] underline
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.
[okular] [Bug 449043] underline
https://bugs.kde.org/show_bug.cgi?id=449043 Oliver Sander changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||oliver.san...@tu-dresden.de --- Comment #2 from Oliver Sander --- Indeed, I can confirm that. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 448735] Bad path format for embedded documents
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 because: You are watching all bug changes.
[okular] [Bug 448735] Bad path format for embedded documents
https://bugs.kde.org/show_bug.cgi?id=448735 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- Can you attach such a pdf file? If the embedded file is truly embedded then its path shouldn't matter, should it? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 448448] Okular unable to print to LAN printer - status: rendering completed
https://bugs.kde.org/show_bug.cgi?id=448448 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- I think I have seen this error message as well, but I can't reproduce it now. As a workaround: Does printing work if you enable "force rasterization"? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 447589] printi
https://bugs.kde.org/show_bug.cgi?id=447589 Oliver Sander changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- This doesn't look like a serious bug report. Closing. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 446549] Digital signature feature confusing for new users
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 "digitally sign" * An explanatory dialog popping up when people click on "digitally sign" without having certificates installed -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 446549] Digital signature feature confusing for new users
https://bugs.kde.org/show_bug.cgi?id=446549 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #2 from Oliver Sander --- Albert, by and large I agree with you. However, I think Nicolai's suggestion to grey out the 'digitally sign' menu entry when there are no certificates is worth considering. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443446] Add "previous view" and "next view" buttons
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 translated them from my German UI.] -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443446] Add "previous view" and "next view" buttons
https://bugs.kde.org/show_bug.cgi?id=443446 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- Have you tried shift+alt+left? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
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.
[kwin] [Bug 438198] In wayland moving a window to another desktop becomes a needlessly complicated task
https://bugs.kde.org/show_bug.cgi?id=438198 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #10 from Oliver Sander --- Can you reproduce the problem using one of the poppler command line tools like pdfinfo or pdftocairo? It may be a poppler bug. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420571] Feature Request: Export/Import annotations to/from an XML file or the clipboard, using a toolbar button or context menu entry in the Reviews/Annotations side panel
https://bugs.kde.org/show_bug.cgi?id=420571 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #4 from Oliver Sander --- The two phabricator diffs mentioned in the first post look interesting in their own right. David, can I motivate you to submit them as gitlab merge requests (and maybe even adopt them wholesale)? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 409644] [Wayland] Panning in Okular is laggy with 4K monitor
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 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 409644] [Wayland] Panning in Okular is laggy with 4K monitor
https://bugs.kde.org/show_bug.cgi?id=409644 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #6 from Oliver Sander --- Do you also see the problem without scaling? Screen scaling works differently under Wayland, and you may[0] end up with an 8K temporary bitmap. That is simply a lot of data, and maybe the lagging is for that? [0] I am not 100% about this, but it is worth checking. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 438980] display blurred
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.
[okular] [Bug 438980] display blurred
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.kde.org/graphics/okular/-/merge_requests/368 (which only bites if you use presentation mode). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 438980] display blurred
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.
[okular] [Bug 438980] display blurred
https://bugs.kde.org/show_bug.cgi?id=438980 Oliver Sander changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #7 from Oliver Sander --- This is what I expected. Per-screen-scaling hasn't seen much love until recently, because on Linux you won't get it anyway unless you use wayland. That being said, there have been a few patches recently. Can you try the 21.04 release, please, and report back? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 438980] display blurred
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.
[okular] [Bug 438980] display blurred
https://bugs.kde.org/show_bug.cgi?id=438980 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- What is your operating system? Do you use screen scaling? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 438923] PDF contents tab doesn't respect empty page label number style
https://bugs.kde.org/show_bug.cgi?id=438923 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #7 from Oliver Sander --- I wouldn't mind seeing both, the number and the page label (empty if there is no label). If there is a general consensus against showing the page number, then showing nothing at all if there is no page label is okay for me, too. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 437926] Non-ASCII characters in certificate names are not printed on a signed document
https://bugs.kde.org/show_bug.cgi?id=437926 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #6 from Oliver Sander --- Let me ignore the whole "discrimination" and "offense" business. Johannes, this is a Poppler bug and needs to be fixed there. Johannes, can you reproduce the problem using the pdfsig problem (which is part of Poppler)? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436709] Autoplaying of renditions (audio/video)
https://bugs.kde.org/show_bug.cgi?id=436709 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- > I think that the current handling of "AutoPlay" is wrong for Renditions. Did you check what Acrobat does? Okular would usually strive to do the same. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436301] Support non standard Libreoffice Embedded files
https://bugs.kde.org/show_bug.cgi?id=436301 Oliver Sander changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #12 from Oliver Sander --- Reading https://bugs.documentfoundation.org/show_bug.cgi?id=66580 (an old duplicate of your bug report), it seems quite clear that the LO folks are unhappy about their nonstandard way of embedding odt files into pdf files, and would rather see that changed. It is therefore extremely unlikely that Okular will ever implement support for the current LibreOffice way of embedding documents. Any developer effort is much better spent making LibreOffice standard-compatible. I will therefore close this bug report. Thanks for your interest in Okular! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436301] Embedded Libreoffice files are not shown as embedded files in the File menu.
https://bugs.kde.org/show_bug.cgi?id=436301 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- Please attach such a file. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 402017] Cannot save PDF when loaded file has been deleted
https://bugs.kde.org/show_bug.cgi?id=402017 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #66 from Oliver Sander --- > I don't really understand why this bug is still open after so many users Because there is nobody who has both the skills and the free time to fix it. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 435669] PDF renders in low quality when using two monitors with mixed scales
https://bugs.kde.org/show_bug.cgi?id=435669 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- There have been a few patches regarding mixed scaling recently. Are you able to test with a self-compiled Okular? (Or wait for 21.04)? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 435568] "Do you want to save or discard?" Options are Yes, No, or Abort
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 again it was translated correctly. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 435568] "Do you want to save or discard?" Options are Yes, No, or Abort
https://bugs.kde.org/show_bug.cgi?id=435568 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #2 from Oliver Sander --- Let me guess: You do not want "Save/Discard/Abort", but the German translation of that, right? It does work properly in English, but there is a problem with the translation. I do see the same issue, and I remember there being a bug report about it (can't find it right now). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 435120] Data protection: Removing or editing annotation metadata (author, date, time) should be possible
https://bugs.kde.org/show_bug.cgi?id=435120 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #10 from Oliver Sander --- To a large extend this is a resource problem -- Okular is not very well staffed. If somebody came up with a patch it would certainly receive consideration. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 434613] System DPI ignored for PDF files
https://bugs.kde.org/show_bug.cgi?id=434613
Oliver Sander changed:
What|Removed |Added
CC||oliver.san...@tu-dresden.de
--- Comment #2 from Oliver Sander ---
What we do have, however, is
if (qAbs(res.width() - res.height()) / qMin(res.height(),
res.width()) < 0.05) {
return res;
} else {
qCDebug(OkularCoreDebug) << "QScreen calculation returned a non
square dpi." << res << ". Falling back";
}
in method Utils::realDpi, file utils.cpp. In other words, unequal dpi values
for x and y are actively ignored by Okular. I am not sure whether that is a
bug or a feature. Probably both.
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 434111] Different scaling of displays creates pixelated output
https://bugs.kde.org/show_bug.cgi?id=434111 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- Two patches concerning setups with differently-scaled screens have been merged recently https://invent.kde.org/graphics/okular/-/merge_requests/380 https://invent.kde.org/graphics/okular/-/merge_requests/371 and a third one is in the pipeline: https://invent.kde.org/graphics/okular/-/merge_requests/368 Maybe you can try those to see if they fix your problem? Linux people: Plasma Wayland supports per-screen scaling, and I suppose that the bugs you see are mostly the ones recently reported for Windows. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 432738] Okular prints no pdf files
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.
[okular] [Bug 432159] Okular display resolution for same pdf is low (when compared with other software) on secondary monitor with 125% scaling
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.
[okular] [Bug 433003] PDF rendering on dual screen setup with different per-screen scaling appears broken
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.
[okular] [Bug 433003] PDF rendering on dual screen setup with different per-screen scaling appears broken
https://bugs.kde.org/show_bug.cgi?id=433003 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- I can confirm this not on windows, but on Plasma Wayland, where per-screen scaling is also possible. I am currently working on fixes for some of these issues---hang on. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 432738] Okular prints no pdf files
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' renders the file into a QPrinter object, and uses the Qt printing infrastructure. -- You are receiving this mail because: You are watching all bug changes.
