[okular] [Bug 483968] New: Okular now moves the starting point of the text selection region when I position my cursor before the original starting point.
https://bugs.kde.org/show_bug.cgi?id=483968 Bug ID: 483968 Summary: Okular now moves the starting point of the text selection region when I position my cursor before the original starting point. Classification: Applications Product: okular Version: 24.02.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: liusish...@gmail.com Target Milestone: --- When I use the text selection tool to select text in a PDF file, Okular lets the starting point instead of the end point of the text selection region follow my cursor when the cursor is located before the original starting point. I don't think it is an intended behavior because it is super confusing and unintuitive. STEPS TO REPRODUCE 1. Open a pdf file in Okular. 2. Use the official text selection tool to select something. OBSERVED RESULT The starting point of the text selection region follow the cursor when it is located before the original starting point. EXPECTED RESULT The starting point should be fixed during the text selection operation. SOFTWARE/OS VERSIONS Okular Version: 24.02.0 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 483678] Signing with Luxtrust's non-repudiation certificate just hangs
https://bugs.kde.org/show_bug.cgi?id=483678 --- Comment #8 from Alain Knaff --- (In reply to Albert Astals Cid from comment #7) > "Just called Luxtrust about this, they claimed that there was only one > certificate on the card." > > Well, NSS disagrees if firefox shows 2, not much we can do here really. Exactly, they _claimed_ ... :-) In the meantime, I got nss3 patched to get the signature working. It was a deadlock: the non-working certificate was a "non-repudiation" certificate which required 2 pin entries (same PIN, but needed to be re-entered again). While signing, NSS acquires a lock to the card slot, and then calls PK11_DoPassword to prompt for the "second" password. But unfortunately, PK11_DoPassword then tries to re-acquire the same lock a second time => which causes the block. However, even after fixing this, okular still doesn't work. Now, okular does pop up a password prompt for password re-entry, but this prompt returns control immediately to the code, even while the dialog box is still showing (as far as I can see, it returns an empty password). The password entered by the user is ignored, and the prompt keeps appearing. Commenting out the second call to PK11_DoPassword in NSS altogether allows signature to proceed. Of course, the card (or its pkcs11 module) notices that the second password was never entered, so now the pkcs11 module pops up its own password prompt via an X connection that it opened up itself. And that finally works. => I think this points to a threading issue within okular (or poppler?): SEC_SignData is not really supposed to be called from the thread handling the GUI. Indeed, this not only freezes the GUI while it does its calculation (or forever, in the case of a deadlock), but it also becomes iffy if it needs to call the GUI itself. There is no "clean" way for it to get back to the X client event loop to wait for password entry, and so has no other choice than return an empty password as soon as the box is up. Usually long operations, or operations that could potentially block, are supposed to be run from another thread than the thread handling the GUI. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 483678] Signing with Luxtrust's non-repudiation certificate just hangs
https://bugs.kde.org/show_bug.cgi?id=483678 --- Comment #7 from Albert Astals Cid --- "Just called Luxtrust about this, they claimed that there was only one certificate on the card." Well, NSS disagrees if firefox shows 2, not much we can do here really. -- You are receiving this mail because: You are the assignee for the bug.
Re: Usage of okular on windows
El dijous, 14 de març de 2024, a les 20:17:44 (CET), Lionel Bruno va escriure: > Dear Okular developers, > > We are a french institution that adopted Okular on our computers ( tired of > Acrobat advertising in their GUI ). > > We used to download the windows version from binary-factory.kde.org ( the > windows store is not allowed on our machines ). The replacement for unstable releases is https://cdn.kde.org/ci-builds/graphics/okular/master/ but we don't have windows build yet. > > Is there an alternative way to get the recent version and future updates > outside the windows store ? For the official build you can always download it from download.kde.org i.e. https://download.kde.org/Attic/release-service/23.08.1/windows/ But it's a bit tricky because you have to know which of the releases had a windows release. > > Thanks for your great work and thanks in advance you for your response. We do not provide an auto-updater besides Windows Store. choco seems to have okular https://community.chocolatey.org/packages/okular But i have no idea how much you can trust those packages or if choco would be allowed on your computers. Cheers, Albert > > > regards > > --- > Lionel Bruno > > Service des systèmes d'information > +33 1 47 03 89 12 > lionel.br...@inha.fr
[okular] [Bug 483904] Okular crash when closing a inline or popup note
https://bugs.kde.org/show_bug.cgi?id=483904 Albert Astals Cid changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||aa...@kde.org --- Comment #1 from Albert Astals Cid --- Please provide a more complete backtrace of the crash https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 483678] Signing with Luxtrust's non-repudiation certificate just hangs
https://bugs.kde.org/show_bug.cgi?id=483678 --- Comment #6 from Alain Knaff --- (In reply to Albert Astals Cid from comment #5) > (In reply to Alain Knaff from comment #4) > > I now wanted to try whether it works better with gpg, but I couldn't find > > how to switch to gpg. > > > > In Settings->ConfigureBackends->PDF, it seems to assume NSS, and there is no > > switch to use GPG > > > > Or is this in an entirely different place in settings? If so, where? > > It's there, i see you're probably using a too old version of okular/poppler > for it to show up. I retried with okular 23.08.1 from Debian testing, and with a poppler that I compiled myself (24.03.0), and GPG still didn't show up :-( > > How many certificates do you get shown in Firefox->Own certificates > preferences page? I see 3 certificates: the 2 from the smartcard, and an old expired software CA cert that I happened to have lying around -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 483678] Signing with Luxtrust's non-repudiation certificate just hangs
https://bugs.kde.org/show_bug.cgi?id=483678 --- Comment #5 from Albert Astals Cid --- (In reply to Alain Knaff from comment #4) > I now wanted to try whether it works better with gpg, but I couldn't find > how to switch to gpg. > > In Settings->ConfigureBackends->PDF, it seems to assume NSS, and there is no > switch to use GPG > > Or is this in an entirely different place in settings? If so, where? It's there, i see you're probably using a too old version of okular/poppler for it to show up. How many certificates do you get shown in Firefox->Own certificates preferences page? -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 483914] Okular can print first page or all the pages of a pdf, not a range of pages, neither a single page between 2 and last
https://bugs.kde.org/show_bug.cgi?id=483914 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 483914] New: Okular can print first page or all the pages of a pdf, not a range of pages, neither a single page between 2 and last
https://bugs.kde.org/show_bug.cgi?id=483914 Bug ID: 483914 Summary: Okular can print first page or all the pages of a pdf, not a range of pages, neither a single page between 2 and last Classification: Applications Product: okular Version: 24.02.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: printing Assignee: okular-devel@kde.org Reporter: sebast.we...@free.fr Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open a multi-pages pdf 2. Set a range in options (let’s say 2-3) 3. Print OBSERVED RESULT Nothing is printed. EXPECTED RESULT Selected pages of the pdf printed. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 32 × 13th Gen Intel® Core™ i9-13900HX Memory: 31.1 Gio of RAM Graphics Processor: Mesa Intel® Graphics ADDITIONAL INFORMATION This is happening with a fresh install of Arch Linux / Plasma 6 and on two different printers (Oki MB-472 and Epson XP-15000). Okular can print the first page, the whole pdf, but not a single page or a range of pages inside the pdf. Cups error_log simply reports 'Backend ipp returned status 5 (cancel job)". Other app (like xpdf) print well. Regards, SW. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 483904] Okular crash when closing a inline or popup note
https://bugs.kde.org/show_bug.cgi?id=483904 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 483904] Okular crash when closing a inline or popup note
https://bugs.kde.org/show_bug.cgi?id=483904 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 483904] New: Okular crash when closing a inline or popup note
https://bugs.kde.org/show_bug.cgi?id=483904 Bug ID: 483904 Summary: Okular crash when closing a inline or popup note Classification: Applications Product: okular Version: 24.02.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: lts20050...@gmail.com Target Milestone: --- SUMMARY When trying to add a inline or popup note, closing the yellow note editor window crash Okular. STEPS TO REPRODUCE 1. Open okular 2. Open a PDF file 3. In the top left, click "Annotations" to make the annotation bar appear 4. Click the "inline note" or "popup note" button 5. Click anywhere on the PDF file to open the yellow note editor window. 6. Close the yellow note editor window OBSERVED RESULT Okular crash EXPECTED RESULT Okular doesn't crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon Version: 6.0 KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Graphics Platform: Wayland Log: ``` Unable to open QuickAnnotatingTools XML definition ASSERT failure in AnnotWindow: "Called object is not of the correct type (class destructor may have already run)", file /usr/include/x86_64-linux-gnu/qt6/QtCore/qobjectdefs_impl.h, line 129 KCrash: Application 'okular' crashing... crashRecursionCounter = 2 QSocketNotifier: Invalid socket 6 and type 'Read', disabling... QSocketNotifier: Invalid socket 15 and type 'Read', disabling... KCrash: Application Name = okular path = /usr/bin pid = 16287 KCrash: Arguments: /usr/bin/okular KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi void ReportInterface::maybePickUpPostbox() kf5idletime_wayland: This plugin does not support polling idle time 29 ../sysdeps/unix/sysv/linux/poll.c: No such file or directory. void ReportInterface::maybePickUpPostbox() fish: Job 1, 'okular' has stopped ``` -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 483891] Feature Request: Exit with last tab
https://bugs.kde.org/show_bug.cgi?id=483891 Bug Janitor Service changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 483891] New: Feature Request: Exit with last tab
https://bugs.kde.org/show_bug.cgi?id=483891 Bug ID: 483891 Summary: Feature Request: Exit with last tab Classification: Applications Product: okular Version: 23.08.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: tbert...@gmail.com Target Milestone: --- SUMMARY Okular should have an option to close itself with the last closed tab. STEPS TO REPRODUCE 1. Open a file with Okular 2. Close the tab (CTRL+W or File > Close) OBSERVED RESULT Okular closes the file then stays opened. EXPECTED RESULT Okular closes itself. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
