[okular] [Bug 495839] New: Cannot open file in path like "D:\#Temp\#Share\test.pdf"
https://bugs.kde.org/show_bug.cgi?id=495839 Bug ID: 495839 Summary: Cannot open file in path like "D:\#Temp\#Share\test.pdf" Classification: Applications Product: okular Version: 23.08.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: xll...@outlook.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY When open a pdf file "D:\#Temp\#Share\test.pdf", it does not open the file. Instead, it opens the folder "D:\#Temp\" STEPS TO REPRODUCE - Same as summary OBSERVED RESULT - Same as summary EXPECTED RESULT - Same as summary SOFTWARE/OS VERSIONS Windows: ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 495580] Okular shows 2 current page numbers, one of them is not correct
https://bugs.kde.org/show_bug.cgi?id=495580 --- Comment #2 from t.soer...@gmail.com --- It would be nice with an option to navigate by actual page numbers (i.e. not those reported within the text) On Wed, Oct 30, 2024 at 10:12 PM Albert Astals Cid wrote: > https://bugs.kde.org/show_bug.cgi?id=495580 > > Albert Astals Cid changed: > >What|Removed |Added > > > Resolution|--- |NOT A BUG > CC||aa...@kde.org > Status|REPORTED|RESOLVED > > --- Comment #1 from Albert Astals Cid --- > That's not a bug, that's the page number the document says that page number > corresponds to. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 495743] New: Okular window does not have focus when password prompt is dismissed
https://bugs.kde.org/show_bug.cgi?id=495743 Bug ID: 495743 Summary: Okular window does not have focus when password prompt is dismissed Classification: Applications Product: okular Version: 24.08.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: el...@seznam.cz Target Milestone: --- SUMMARY When I open passworded PDF and dismiss password prompt, Okular main window does not have focus and focus is returned to application that opened Okular. STEPS TO REPRODUCE 1. Open Dolphin and navigate to folder with passworded PDF 2. Open PDF 3. Okular shows prompt to enter password 4. Press ESC to dismiss prompt 5. Click OK to close alert 6. Press Alt+F4 to close application OBSERVED RESULT Dolphin is closed. EXPECTED RESULT Okular is closed. SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.2.2 KDE Frameworks Version: 6.7.0 Qt Version: 6.8.0 Kernel Version: 6.11.5-zen1-1-zen (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 495719] New: Okular for Windows not updated in a while
https://bugs.kde.org/show_bug.cgi?id=495719 Bug ID: 495719 Summary: Okular for Windows not updated in a while Classification: Applications Product: okular Version: unspecified Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: kulmer.dan...@gmail.com Target Milestone: --- The last three updates have not shipped in the Microsoft Store (current version is 23.08). I know that I can also get it via Winget, but the best case would surely be if the way suggested on the official website (https://okular.kde.org/download/) worked as expected. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 490189] Unable to zoom accurately on a hidpi display. Zoom factors are too large.
https://bugs.kde.org/show_bug.cgi?id=490189 --- Comment #2 from mba...@outlook.com --- I discovered by accident that if I opened a PDF document in okular while it was not maximized to my screen (opened the PDF normally and then pressed the middle button that is to the left of the close button to turn the window into a floating window), okular works as normal and I can zoom in / zoom out normally. Basically what I have to do is launch the PDF, if I launch it and it is fully maximized I would have to reduce the okular window size to turn it into a floating window and then restart okular. Then it would work as expected. However, I have changed my windows zoom scale to 125% (I was at 150% at the time of bug report) and i have a new monitor (I was on my laptop monitor before and didn't have two monitors). Everything else remains the same, expect I have the latest versions of every software (this update is after I just updated the flatpak version of okular). I believe this is new progress. I'm not sure if it was possible to have proper zooming out and zooming in before in previous versions of okular (fully maximized window or not). I really hope it is close to being resolved now as okular is one of the best PDF apps I have used so far. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 495674] New: inserting text /inline-text annotation make okular crash on macOS/arm64
https://bugs.kde.org/show_bug.cgi?id=495674 Bug ID: 495674 Summary: inserting text /inline-text annotation make okular crash on macOS/arm64 Classification: Applications Product: okular Version: unspecified Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: pinetree2...@gmail.com Target Milestone: --- SUMMARY I found that inserting annotations using text or inline-text make crash in macOS arm64 on the latest version of okular: okular-master-5440-macos-clang-arm64.dmg (downloaded from https://cdn.kde.org/ci-builds/graphics/okular/master/macos-arm64/). STEPS TO REPRODUCE 1. download okular-master-5440-macos-clang-arm64.dmg (build time: 2024-11-01 00:05) from https://cdn.kde.org/ci-builds/graphics/okular/master/macos-arm64/ 2. open any pdf document 3. try to insert text or inline-text note using default annotation tool 4. crash occurs OBSERVED RESULT immediate crash EXPECTED RESULT new inserted text annotation SOFTWARE/OS VERSIONS Windows: N/A macOS: sonoma, 14.5 Linux/KDE Plasma: N/A KDE Plasma Version: N/A KDE Frameworks Version: 6.7.0 Qt Version: 6.8.0 ADDITIONAL INFORMATION Thank you for maintanence and continous efforts. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 495674] inserting text /inline-text annotation make okular crash on macOS/arm64
https://bugs.kde.org/show_bug.cgi?id=495674 pinetree2...@gmail.com changed: What|Removed |Added CC||pinetree2...@gmail.com --- Comment #1 from pinetree2...@gmail.com --- Created attachment 175434 --> https://bugs.kde.org/attachment.cgi?id=175434&action=edit crash report generated from macOS -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 495580] New: Okular shows 2 current page numbers, one of them is not correct
https://bugs.kde.org/show_bug.cgi?id=495580 Bug ID: 495580 Summary: Okular shows 2 current page numbers, one of them is not correct Classification: Applications Product: okular Version: 24.08.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: t.soer...@gmail.com Target Milestone: --- Created attachment 175363 --> https://bugs.kde.org/attachment.cgi?id=175363&action=edit image This is page 190 but the field where you input page number for navigation shows 181 and does not correspond to actual page number -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 495510] New: Add Vim Style Marks in Okular
https://bugs.kde.org/show_bug.cgi?id=495510 Bug ID: 495510 Summary: Add Vim Style Marks in Okular Classification: Applications Product: okular Version: unspecified Platform: unspecified OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: omarkhaled200...@gmail.com Target Milestone: --- Be able to set marks similar to Vim, by pressing "m" and another key, then using "`" and the key to go back to the location in which the mark was made. Could also implement the same purpose using bookmark shortcuts. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 427953] Unique instance and open in tabs ignored
https://bugs.kde.org/show_bug.cgi?id=427953 nono...@gmail.com changed: What|Removed |Added CC||nono...@gmail.com Version|1.11.1 |23.03.80 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 427953] Unique instance and open in tabs ignored
https://bugs.kde.org/show_bug.cgi?id=427953 --- Comment #10 from nono...@gmail.com --- Hi, I’ve been using Okular for a few weeks. I like the application, but I also noticed this annoying bug. Thanks for the app by the way :) -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 495251] New: Signature Properties has huge width and cannot be resized
https://bugs.kde.org/show_bug.cgi?id=495251 Bug ID: 495251 Summary: Signature Properties has huge width and cannot be resized Classification: Applications Product: okular Version: 23.08.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: andreaswu...@gmx.de Target Milestone: --- Created attachment 175152 --> https://bugs.kde.org/attachment.cgi?id=175152&action=edit Signature Properties Dialog Hi, i have a signd document which contains various signatures. When i open the signature properties dialog i get a huge modal dialog showing the information which spans over my two screens and cannot be resized in width. See the screenshot attached. It would be nice if the signature properties dialog can be resized (in width) and is initially displayed in a reasonable size (not bigger in width than the parent okular window). Since the PDF document contains personal information i would not like to attacht the document to this public ticket. However i can send it to a developer (Sune?) who wants to have a look at the problem. That should be no problem. SOFTWARE/OS VERSIONS Operating System: TUXEDO OS 2 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.114.0 Qt Version: 5.15.12 Kernel Version: 6.5.0-10013-tuxedo (64-bit) Graphics Platform: offscreen Processors: 16 × AMD Ryzen 7 4800U with Radeon Graphics Memory: 30.8 GiB of RAM Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 493831] Okular Unable to Render AVIF Images Properly, Directly from ZIP Containers
https://bugs.kde.org/show_bug.cgi?id=493831 dnovome...@gmail.com changed: What|Removed |Added CC||dnovome...@gmail.com --- Comment #1 from dnovome...@gmail.com --- Can you upload your compressed file and the screenshot what exactly do you see wrong on your side? -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 494798] New: Can't quit app when in full screen and opening password locked pdf
https://bugs.kde.org/show_bug.cgi?id=494798 Bug ID: 494798 Summary: Can't quit app when in full screen and opening password locked pdf Classification: Applications Product: okular Version: 24.08.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: el...@seznam.cz Target Milestone: --- SUMMARY Can't quit app when in full screen and opening password locked PDF. STEPS TO REPRODUCE 1. Open any PDF. 2. Press Ctrl+Shift+F to go to full-screen mode. 3. Press Alt+F4 to close PDF. 4. Open password-protected PDF. 5. Press Esc to close password prompt. 6. Click OK to close prompt saying document can't be opened. OBSERVED RESULT Now you are presented with welcome screen without any decorations. First issue is that this window steals focus. Whenever I Alt+Tab to another application, Okular is always brought to the foreground. This does not happen when I'm reading PDF. There is a close button on the welcome screen. When I click it, I'm shown grey full-screen and I can only close it with Alt+F4 or from overview. No control is present on the screen. EXPECTED RESULT Okular should not steal focus and when closing welcome screen, application should close normally. SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.2.0 KDE Frameworks Version: 6.7.0 Qt Version: 6.8.0 Kernel Version: 6.11.3-zen1-1-zen (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 494388] The app inmediatelly crashes when trying to open a long pdf
https://bugs.kde.org/show_bug.cgi?id=494388 cuahpillico...@gmail.com changed: What|Removed |Added Keywords||usability -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 494388] New: The app inmediatelly crashes when trying to open a long pdf
https://bugs.kde.org/show_bug.cgi?id=494388 Bug ID: 494388 Summary: The app inmediatelly crashes when trying to open a long pdf Classification: Applications Product: okular Version: unspecified Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: crash Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: cuahpillico...@gmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Please remove this comment after reading and before submitting - thanks! *** SUMMARY STEPS TO REPRODUCE 1. Try to open a PDF file 5.4 MB or larger 2. Get a crash? 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 467084] Can't open any pdf containing signature! Non signed pdf open normally. Crashes on signing.
https://bugs.kde.org/show_bug.cgi?id=467084 cuahpillico...@gmail.com changed: What|Removed |Added CC||cuahpillico...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 476319] Okular crashes when trying to edit form fields
https://bugs.kde.org/show_bug.cgi?id=476319 filip.kend...@gmail.com changed: What|Removed |Added CC||gervais.m...@upperity.com --- Comment #2 from filip.kend...@gmail.com --- *** Bug 494210 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 494210] Okular Crashes When Filling Out Form
https://bugs.kde.org/show_bug.cgi?id=494210 filip.kend...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||filip.kend...@gmail.com --- Comment #1 from filip.kend...@gmail.com --- *** This bug has been marked as a duplicate of bug 476319 *** -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 494141] Can't Maximize Okular Window on Primary Display
https://bugs.kde.org/show_bug.cgi?id=494141 ventolinm...@yahoo.com.mx changed: What|Removed |Added CC||ventolinm...@yahoo.com.mx -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 494141] New: Can't Maximize Okular Window on Primary Display
https://bugs.kde.org/show_bug.cgi?id=494141 Bug ID: 494141 Summary: Can't Maximize Okular Window on Primary Display Classification: Applications Product: okular Version: 24.05.2 Platform: Ubuntu OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: ventolinm...@yahoo.com.mx Target Milestone: --- SUMMARY Can't maximize Okular. There's no maximize button on the title bar and can not maximize Okular neither by double clicking here or by right clicking and choosing Maximize (it is grayed out) or using the keyboard shortcut (super+up arrow). On my second monitor I can maximize as normal. Installed Okular with snap and I'm using the X11 Windowing System. STEPS TO REPRODUCE 1. Open Okular on primary display. 2. Can't maximize. OBSERVED RESULT Can't maximize. EXPECTED RESULT Maximized window. SOFTWARE/OS VERSIONS Linux: Ubuntu 22.04.5 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 493518] New: No response when opened
https://bugs.kde.org/show_bug.cgi?id=493518 Bug ID: 493518 Summary: No response when opened Classification: Applications Product: okular Version: 23.08.1 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: 10215101...@stu.ecnu.edu.cn Target Milestone: --- When I double-click to open the pdf, Okular stays unresponsive for a minute or two -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 436214] Feature Request: Measure distances (and areas?)
https://bugs.kde.org/show_bug.cgi?id=436214 vderu...@gmail.com changed: What|Removed |Added Version|21.04.0 |24.08.1 Summary|Measure distances (and |Feature Request: Measure |areas?) |distances (and areas?) Platform|Debian unstable |unspecified -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 493358] New: Feature request: viewport history addressed by file content
https://bugs.kde.org/show_bug.cgi?id=493358 Bug ID: 493358 Summary: Feature request: viewport history addressed by file content Classification: Applications Product: okular Version: 24.08.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: daimi...@gmail.com Target Milestone: --- SUMMARY I read PDF files on an SMB share opened in Dolphin and I wish Okular can remember reading progress for those files as well. Having a store of viewport history files addressed by the file's digest might be great. In case the viewport differs by method of retrieving the viewport (by the filename and the digest), possibly when viewing a changing file, we could just default to using the one associated with the filename. STEPS TO REPRODUCE 1. Open a PDF file in an SMB share in Dolphin 2. Read a bit in Okular 3. Close and reopen the file OBSERVED RESULT Reading progress is reset EXPECTED RESULT Reading progress is preserved SOFTWARE/OS VERSIONS (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION none -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 493163] Wrong rendering of some PDF files.
https://bugs.kde.org/show_bug.cgi?id=493163 --- Comment #5 from njuan...@gmail.com --- (In reply to Albert Astals Cid from comment #3) > You can add links you know, there's no need to be fancy and hide links in > base64, just makes our life harder. Had not seen the field, sorry, my bad. (In reply to Albert Astals Cid from comment #4) > We do not do pdf rendering ourself, poppler does, you can go and file a bug > at https://poppler.freedesktop.org/ but let me tell you this is 99% > unfixable because it's not really a bug, those PDF files are scanned images, > and contain LOTS OF NOISE, see a zoomed section here > https://i.imgur.com/UaKtRx2.png When less zoomed the rendering engine has to > decide what to do with all those "random" dots, and well it seems some > engines do something you like better and some something you like worse. > > As an example try firefox, at least here at 100% it's acceptable > https://i.imgur.com/Dfm0feQ.png but at 110% looks really bad > https://i.imgur.com/jSciNYl.png I see what you mean. I guess it does depend on the zoom, so there's not much to do. Guess I'll file the bug anyways just in case. Thank you for the help and explanation! -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 493163] Wrong rendering of some PDF files.
https://bugs.kde.org/show_bug.cgi?id=493163 --- Comment #2 from njuan...@gmail.com --- (In reply to Albert Astals Cid from comment #1) > Without files this is not actionable. The files are provided at the end. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 493189] New: okular closes and reopens itself
https://bugs.kde.org/show_bug.cgi?id=493189 Bug ID: 493189 Summary: okular closes and reopens itself Classification: Applications Product: okular Version: 22.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: kunzmor...@gmx.ch Target Milestone: --- if i open a document in Okular, it closes the doc and opens it instantly, so if i change something it always asks me if i want to keep my changes and then reopens. So i cant really work properly on any document rn -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 493163] New: Wrong rendering of some PDF files.
https://bugs.kde.org/show_bug.cgi?id=493163 Bug ID: 493163 Summary: Wrong rendering of some PDF files. Classification: Applications Product: okular Version: unspecified Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: njuan...@gmail.com Target Milestone: --- SUMMARY Some PDF files are rendered "incorrectly" or rather on a very difficult way for us to read them. STEPS TO REPRODUCE 1. Open a PDF file with these characteristics. 2. See how it is pretty much unreadable. 3. See comparisons here: Default PDF viewer from Linux Mint: https://images2.imgbox.com/bd/8b/qFzQQ3cP_o.png Okular: https://images2.imgbox.com/35/e0/SiEpq6OO_o.png Default PDF viewer: https://images2.imgbox.com/6d/44/0Cf4ul3p_o.png Okular: https://images2.imgbox.com/70/bc/uM6JJmUR_o.png OBSERVED RESULT PDF's are rendered incorrectly. EXPECTED RESULT Correct rendering so as to be able to read them. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux Mint 20.3 Cinnamon. KDE Plasma Version: -. KDE Frameworks Version: 5.68.0. Qt Version: 5.12.8. xcb window system. ADDITIONAL INFORMATION Wrong rendered files are provided for reference and testing if needed: aHR0cHM6Ly9tZWdhLm56L2ZpbGUvTmlGV0FBSWEjU09xZTgtdmJUSm02YWVETkQyMU1GU3pHcWdabnl1R2tuS2xyX0JsbVA5MA== aHR0cHM6Ly9tZWdhLm56L2ZpbGUva2lrMjFTWUEjd2xYUFlRQXNQYjdwckN1Umdvdk9jVUt1NE1FMFdPUmx2NUdPUlkyOWh2aw== (base64). -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 436214] Measure distances (and areas?)
https://bugs.kde.org/show_bug.cgi?id=436214 vderu...@gmail.com changed: What|Removed |Added CC||vderu...@gmail.com --- Comment #2 from vderu...@gmail.com --- Hi! I totally support this initiative. There is really a lack for this type of functionality in Linux. Unfortunately, I don't have the coding skills to do this myself, but I have used software with this functionality at my job and I can give some feedback on how the user experience usually is (to hopefully help to someone actually make it true :) ). Usually there are 2 types of ways for performing measurements into a document: ## Option 1 ("Easy") - The user selects the "calibration button" - The user picks two points in the document - A popup window appears asking the user for introducing the distance of those 2 points (in a drop-down menu you can select the unit) - Okular extracts the distance between 2 points and "calibrates" the document accordingly (using the dimensions of the page of the document) - The user now can select the "measure" button where two new points can be selected and obtain the desired the distance. ## Option 2 (Probably more tricky) - In the "calibrate" option there are a set of default scales the user can pick from (1:50, 1:100, etc. specifying the units, of course) - Knowing the dimensions of page, the calibration is set up and the user can measure as above. Once is developed the functionality can be extended in the future using with extra calculations such as simple areas (squares, circles), the perimeter of a polyline/polygone, etc. I'm aware that this is easier said than done, but I think quite some people could benefit from this! -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 492670] New: Build error with clang and musl (on Gentoo)
https://bugs.kde.org/show_bug.cgi?id=492670 Bug ID: 492670 Summary: Build error with clang and musl (on Gentoo) Classification: Applications Product: okular Version: 24.08.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: vadorov...@protonmail.com Target Milestone: --- SUMMARY Okular (both master branch and 24.08.0) fail to build with clang as compiler and musl as system libc. STEPS TO REPRODUCE 1. Use Gentoo with musl-llvm profile . Maybe it's reproducible also on Alpine, but I'm not sure. 2. Build Okular either from source (git) or with `emerge -av kde-apps/okular` OBSERVED RESULT [ 9%] Building C object CMakeFiles/okularcore.dir/core/synctex/synctex_parser.c.o /home/vadorovsky/src/okular/core/synctex/synctex_parser.c:1627:85: warning: missing field 'page' initializer [-Wmissing-field-initializers] 1627 | synctex_data_ref_thv_max}; | ^ /home/vadorovsky/src/okular/core/synctex/synctex_parser.c:3717:12: warning: variable 'tested_len' set but not used [-Wunused-but-set-variable] 3717 | size_t tested_len = 0;/* the number of characters at the beginning of the_string that match */ |^ /home/vadorovsky/src/okular/core/synctex/synctex_parser.c:8059:13: error: call to undeclared function 'vasprintf'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration] 8059 | if (vasprintf(&buffer, format, va) < 0) { | ^ /home/vadorovsky/src/okular/core/synctex/synctex_parser.c:8059:13: note: did you mean 'vsprintf'? /usr/include/stdio.h:116:5: note: 'vsprintf' declared here 116 | int vsprintf(char *__restrict, const char *__restrict, __isoc_va_list); | ^ 2 warnings and 1 error generated. gmake[2]: *** [CMakeFiles/okularcore.dir/build.make:581: CMakeFiles/okularcore.dir/core/synctex/synctex_parser.c.o] Error 1 gmake[1]: *** [CMakeFiles/Makefile2:731: CMakeFiles/okularcore.dir/all] Error 2 gmake: *** [Makefile:146: all] Error 2 EXPECTED RESULT A successful build SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux (musl-llvm profile) -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 485208] Incomplete PDF Icon Display in Windows with Okular
https://bugs.kde.org/show_bug.cgi?id=485208 --- Comment #4 from skywalker...@outlook.com --- It doesn't in my another computer with 100% zoom and same resolution Sent from my iPhone > On Aug 28, 2024, at 18:26, Albert Astals Cid wrote: > > https://bugs.kde.org/show_bug.cgi?id=485208 > > --- Comment #3 from Albert Astals Cid --- > does it also happen if you put the desktop zoom at 100%? > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You reported the bug. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 435535] Okular EPUB backend renders black background with black text
https://bugs.kde.org/show_bug.cgi?id=435535 istillal...@live.cn changed: What|Removed |Added CC||istillal...@live.cn -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 492568] New: APT flatpak malfunctioning "speak text" accessibility function
https://bugs.kde.org/show_bug.cgi?id=492568 Bug ID: 492568 Summary: APT flatpak malfunctioning "speak text" accessibility function Classification: Applications Product: okular Version: 24.05.2 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: jcb-w...@protonmail.com Target Milestone: --- Created attachment 173251 --> https://bugs.kde.org/attachment.cgi?id=173251&action=edit Screenshot of Okular configuration Accessibility module. If you click "mock" to look for altenratives in the drop down, none are present. *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. Open a PDF in Okular that was installed using apt-get or the Ubuntu GUI software installer. 2. Locate Okular menu tools to read a page or full document. 3. Click either "read page" or "read document" OBSERVED RESULT 1. No audio. Check sound settings, sound is assigned to speakers. Try other tool. No audio. 2. Open Okular settings, Accessibility section. 3. Note that "mock" is the only option for speech engine, despite "speechd" already being installed and running. EXPECTED RESULT 1. Okular speaks the text (full document or page only per command selected) SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: Ubuntu 20.04 KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Please be kind to a disabled grad student who may not have correctly followed all expected protocols for this bug report. I have a lot of PDFs to grok and it would really help if Okular's speak text tool functioned. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 492510] New: Contents sidebar mouse-over scrambled output
https://bugs.kde.org/show_bug.cgi?id=492510 Bug ID: 492510 Summary: Contents sidebar mouse-over scrambled output Classification: Applications Product: okular Version: 24.08.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: servomekan...@gmail.com Target Milestone: --- Created attachment 173214 --> https://bugs.kde.org/attachment.cgi?id=173214&action=edit showcasing the bug In a pdf that has contents enabled when showing them in the sidebar and mouse overing them, sometimes the chapters that popup are scrambled. If you move the mouse from one to another its more visible. Please check attached video. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 407547] Open new files in tabs does not work in windows
https://bugs.kde.org/show_bug.cgi?id=407547 fir...@oelwein.net changed: What|Removed |Added CC||fir...@oelwein.net --- Comment #17 from fir...@oelwein.net --- Confirm this behavior for 23.08.1 with Windows 10P22H2/19045.4780 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 485208] Incomplete PDF Icon Display in Windows with Okular
https://bugs.kde.org/show_bug.cgi?id=485208 --- Comment #2 from skywalker...@outlook.com --- Hi. Resolution 2k, 125% zoom. Sent from my iPhone > On Aug 27, 2024, at 18:16, Albert Astals Cid wrote: > > https://bugs.kde.org/show_bug.cgi?id=485208 > > Albert Astals Cid changed: > > What|Removed |Added > > CC||aa...@kde.org > > --- Comment #1 from Albert Astals Cid --- > Which resolution do you have in your monitor? And which zoom? > > -- > You are receiving this mail because: > You are on the CC list for the bug. > You reported the bug. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 491876] Feature: Rectangle Tool: Add Option to XOR the Colour
https://bugs.kde.org/show_bug.cgi?id=491876 fanzhuyi...@gmail.com changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 491728] New: highlighter does not show complete filling, with some blank pixels at the end of the markings.
https://bugs.kde.org/show_bug.cgi?id=491728 Bug ID: 491728 Summary: highlighter does not show complete filling, with some blank pixels at the end of the markings. Classification: Applications Product: okular Version: 24.07.90 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: pedro160...@gmail.com Target Milestone: --- Created attachment 172624 --> https://bugs.kde.org/attachment.cgi?id=172624&action=edit highlighter does not show complete filling, with some blank pixels at the end of the markings. *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. highlighter user 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 491723] Okular crashes when viewing a PDF page with many freehand lines
https://bugs.kde.org/show_bug.cgi?id=491723 duha.b...@gmail.com changed: What|Removed |Added Version|unspecified |24.05.2 CC||duha.b...@gmail.com Component|general |general Assignee|unassigned-b...@kde.org |okular-devel@kde.org Product|kde |okular -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 491607] create indexes for pdfs that don't have any
https://bugs.kde.org/show_bug.cgi?id=491607 fanzhuyi...@gmail.com changed: What|Removed |Added CC||epiqinf...@gmail.com --- Comment #1 from fanzhuyi...@gmail.com --- *** Bug 491611 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 491611] There is a lot of pdfs out there that are pretty long, but don't have an index/overview.
https://bugs.kde.org/show_bug.cgi?id=491611 fanzhuyi...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||fanzhuyi...@gmail.com --- Comment #1 from fanzhuyi...@gmail.com --- *** This bug has been marked as a duplicate of bug 491607 *** -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 491413] Escape character doesn't work for backticks
https://bugs.kde.org/show_bug.cgi?id=491413 --- Comment #2 from domojes...@gmail.com --- Created attachment 172424 --> https://bugs.kde.org/attachment.cgi?id=172424&action=edit A formatted version of a popular vim-related stackoverfllow answer Here's the exact file I was editing: the content actually references backticks explicitly, so hopefully it's easy to find the spots I'm referring to! -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 491413] New: Escape character doesn't work for backticks
https://bugs.kde.org/show_bug.cgi?id=491413 Bug ID: 491413 Summary: Escape character doesn't work for backticks Classification: Applications Product: okular Version: 24.05.2 Platform: Flatpak OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: markdown backend Assignee: okular-devel@kde.org Reporter: domojes...@gmail.com Target Milestone: --- SUMMARY If I want to display the backtick character (`) as inline code, I'm under the assumption that I would need to write something like this: `\``. However, this simply does not work. STEPS TO REPRODUCE 1. In a markdown file, write the string `\`` 2. Open the file in Okular. OBSERVED RESULT The backtick next to the backslash behaves like a normal Markdown backtick, expecting a closing backtick later and breaking the way the file is intended to be rendered. EXPECTED RESULT The backtick is seen rendered in monospace. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 490189] Unable to zoom accurately on a hidpi display. Zoom factors are too large.
https://bugs.kde.org/show_bug.cgi?id=490189 --- Comment #1 from mba...@outlook.com --- I'd like to update, I tried the windows version of okular and its the exact same issue. However, in Wayland on kde it works just fine and as expected. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 490189] Unable to zoom accurately on a hidpi display. Zoom factors are too large.
https://bugs.kde.org/show_bug.cgi?id=490189 gerrit.huebb...@gmail.com changed: What|Removed |Added CC||gerrit.huebb...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 480823] shift-mouse scroll should scroll left/right
https://bugs.kde.org/show_bug.cgi?id=480823 gerrit.huebb...@gmail.com changed: What|Removed |Added CC||gerrit.huebb...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 490435] printing from the selected range of pages does not work correctly
https://bugs.kde.org/show_bug.cgi?id=490435 erentar2...@gmail.com changed: What|Removed |Added CC||erentar2...@gmail.com --- Comment #1 from erentar2...@gmail.com --- I can reproduce this, in my case the pdf has some pages indexed in roman numerals at the start, and after the tenth page it starts roman numerals. i want to print pages 5,6 (v,vi) however printing `5,6` or `v,vi` does not produce any print output. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 491019] okular fails to open local non-home file by cmdline, but can open it by GUI navigation
https://bugs.kde.org/show_bug.cgi?id=491019 --- Comment #1 from myocyt...@sina.com --- Let directories be: ``` /storage (separate disk mounted on /) /storage/Downloads (dir on disk /storage) /_disk_home (separate disk mounted on /) /home (separate disk; bind mount from /_disk_home/home) /home/ (dir on /home) /home//Downloads (symlink) -> /storage/Downloads ``` -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 491019] New: okular fails to open local non-home file by cmdline, but can open it by GUI navigation
https://bugs.kde.org/show_bug.cgi?id=491019 Bug ID: 491019 Summary: okular fails to open local non-home file by cmdline, but can open it by GUI navigation Classification: Applications Product: okular Version: 24.05.1 Platform: Snap OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: myocyt...@sina.com Target Milestone: --- SUMMARY (snap okular 24.05.1) okular fails to open some local files (not under home) by cmdline, but can open it by GUI navigation STEPS TO REPRODUCE Let directories be: ``` /storage (separate disk mounted on /) /storage/Downloads (dir on disk /storage) /_disk_home (separate disk mounted on /) /home (separate disk; bind mount from /_disk_home) /home/ (dir on /home) /home//Downloads (symlink) -> /storage/Downloads ``` Then try to open same files by cmdline and GUI navigation. OBSERVED RESULT `okular /home//a.pdf` OK; `okular` then File->Open...->(gnome file dialog)->navigate/select: OK; `okular /home//Downloads/b.pdf` Fail; `okular` then navigate: OK; `okular /storage/Downloads/b.pdf` Fail; `okular` then navigate: OK; EXPECTED RESULT `okular /home//Downloads/b.pdf` & `okular /storage/Downloads/b.pdf` success SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 22.04.4 LTS KDE Frameworks Version: 6.4 Qt Version: 6.7.1 ADDITIONAL INFORMATION I don't understand the quirks of gnome/snap, so I don't know if it is gnome/snap's flaw. ``` mount | grep ext4 /dev/nvme2n1p3 on / type ext4 (rw,relatime,errors=remount-ro) /dev/nvme0n1p1 on /_disk_home type ext4 (rw,relatime,errors=remount-ro) /dev/nvme0n1p1 on /home type ext4 (rw,relatime,errors=remount-ro) /dev/nvme1n1p1 on /storage type ext4 (rw,relatime,errors=remount-ro) ``` ``` snap connections okular InterfacePlugSlot Notes audio-playback okular:audio-playback :audio-playback - content[icon-themes] okular:icon-themes gtk-common-themes:icon-themes - content[kf6-core22-all] okular:kf6-core22 kf6-core22:kf6-core22-slot - content[sound-themes]okular:sound-themes gtk-common-themes:sound-themes - cups okular:cups cups:cups - dbus - okular:session-dbus-interface - desktop okular:desktop :desktop - desktop-legacy okular:desktop-legacy :desktop-legacy - home okular:home :home - network okular:network :network - network-bind okular:network-bind :network-bind - opengl okular:opengl :opengl - removable-media okular:removable-media :removable-media - system-packages-doc okular:system-packages-doc :system-packages-doc - udisks2 okular:udisks2 - - unity7 okular:unity7 :unity7 - wayland okular:wayland :wayland - x11 okular:x11 :x11 - ``` -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 431792] PDF Form checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=431792 mba...@outlook.com changed: What|Removed |Added CC||mba...@outlook.com --- Comment #14 from mba...@outlook.com --- Okular works just fine when I use the flatpak version of it and it shows the checkboxes in pdf forms when you unhide the "form fields". But in the native arch linux version it does not work. I really hope this gets fixed. Super annoying bug. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 490189] New: Unable to zoom accurately on a hidpi display. Zoom factors are too large.
https://bugs.kde.org/show_bug.cgi?id=490189 Bug ID: 490189 Summary: Unable to zoom accurately on a hidpi display. Zoom factors are too large. Classification: Applications Product: okular Version: 24.05.2 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: mba...@outlook.com Target Milestone: --- SUMMARY Unable to zoom accurately on a hidpi display. Zoom factors are too large. STEPS TO REPRODUCE 1. Open any PDF document 2. Zoom to any scale OBSERVED RESULT Zoom factor of any size (even the smallest at 12%) is too large for my display. It does not fit properly like it should on other pdf editors. Using control + scroll wheel makes no different than if I manually select the zoom factor (because both do the same thing). Only "fit page" is able to show the full document on screen, and "fit width" is too large as it takes up the whole screen space. See the video as I show the expected result using gnome's document viewer (flatpak). https://youtu.be/U9H_XMsxbGE EXPECTED RESULT It should zoom in slowly instead of immediately starting off with a large zoom resolution. See the video below. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Arch Linux Kernel Version: 6.9.8-arch1-1 (64-bit) KDE Plasma Version: 6.1.2 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION Laptop: Legion 7 16ACHg6 Display Resolution: 2560x1600 165hz Server: X11 Software package: Flatpak -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 489953] New: Allow disabling rounded highlight
https://bugs.kde.org/show_bug.cgi?id=489953 Bug ID: 489953 Summary: Allow disabling rounded highlight Classification: Applications Product: okular Version: unspecified Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: erentar2...@gmail.com Target Milestone: --- Created attachment 171488 --> https://bugs.kde.org/attachment.cgi?id=171488&action=edit Screenshot shows how rounding in highlights can bleed over to adjacent words resulting in ugly text SUMMARY Rounded highlights sometimes bleed over to adjacent words resulting in a very ugly text. This issue does not occur in PDF viewers which have (the option to disable) non-rounded corners. STEPS TO REPRODUCE 1. Highlight a word in a dense text with the "text markup" highlighter tool OBSERVED RESULT - It is currently not possible to disable the rounding EXPECTED RESULT - Rounding should be a toggle option -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 489490] Saving of externally modified PDF fails
https://bugs.kde.org/show_bug.cgi?id=489490 lemo...@protonmail.com changed: What|Removed |Added Summary|Cannot save modified|Saving of externally ||modified PDF fails -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 489490] New: Cannot save modified
https://bugs.kde.org/show_bug.cgi?id=489490 Bug ID: 489490 Summary: Cannot save modified Classification: Applications Product: okular Version: 24.05.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: lemo...@protonmail.com Target Milestone: --- SUMMARY I get the following error when trying to save an annotated file that was modified on the disk: "File could not be saved in '/run/user/1001/app/org.kde.okular/okular.XgDXjc'. Try to save it to another location." Note that the displayed location is independent of the location where I want to save it. This seems related to what was fixed/implemented here: https://bugs.kde.org/show_bug.cgi?id=402017. My Okular version is up to date, I already see the new dialogs. STEPS TO REPRODUCE 1. Open PDF, add annotations 2. Have another Program modify the original PDF while it is still open in Okular 3. Prevent Okular from reloading the file 4. Try to save the file via "Save" or "Save As" to a location of your choice. OBSERVED RESULT "File could not be saved in '/run/user/1001/app/org.kde.okular/okular.XgDXjc'. Try to save it to another location." (The last string part of random characters changes from time to time. It seems like a session identifier? The location has nothing to do with the location to which I actually wanted to save the file.) EXPECTED RESULT Saves the PDF successfully. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 489478] New: Menu bar error as No text on Windows edition
https://bugs.kde.org/show_bug.cgi?id=489478 Bug ID: 489478 Summary: Menu bar error as No text on Windows edition Classification: Applications Product: okular Version: 23.08.1 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: sherkhan30...@gmail.com Target Milestone: --- Created attachment 171195 --> https://bugs.kde.org/attachment.cgi?id=171195&action=edit Screenshot displaying No text in menu bar SUMMARY Some buttons in the menu bar are showing as "No text" STEPS TO REPRODUCE 1. Install Okular from Windows Store App 2. Run it OBSERVED RESULT In the menu bar, some buttons are displaying as "No text". Please refer screenshot. EXPECTED RESULT To show properly menu button names SOFTWARE/OS VERSIONS Okular version: 23.8.1.1522.0 (as shown on Windows store app) Windows: Edition: Windows 10 Home Single Language Version: 22H2 OS build:19045.4529 Experience:Windows Feature Experience Pack 1000.19058.1000.0 ADDITIONAL INFORMATION None. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 470438] Open new files in tab does not work in flatpak verison of Okular 23.04.1
https://bugs.kde.org/show_bug.cgi?id=470438 kwvanderli...@gmail.com changed: What|Removed |Added CC||kwvanderli...@gmail.com --- Comment #1 from kwvanderli...@gmail.com --- Did some digging on this as I encountered the same problem on Linux Mint with Okular 24.05.1. I'm not an expert with the tech involved, but the issue seems to be a combo of collisions between D-Bus service names and lack of permissions on the flatpak itself. For flatpak permissions, okular needs to have access to the session bus since it needs to discover the other okular services. But the flatpak does not have this permission set by default and so the user has to enable it explicitly. For the D-Bus service name, okular includes the PID, which normally results in separate a D-Bus service for each okular process. But under flatpak, the PID is always the same due to running under a separate PID namespace (e.g., I always see a PID of 2). So when okular is already running, and we try to open a new document from the file explorer, the new okular process will have the same PID and D-Bus service name as the existing process. So even if the new process could discover the existing process service, it will think it just discovered itself and won't send the new paths over to the existing process. As a workaround, here's what I did to get the flatpak to open docs in new tabs instead of new windows: 1. Add the `socket=session-bus` permission, e.g., through flatseal. This is generally not recommended by flatpak, but is required for service discovery. 2. Enable PID sharing with the top-level namespace, which will give each okular process a distinct PID. Instead of `flatpak run org.kde.okular`, use `flatpak --parent-pid=1 --parent-share-pids run org.kde.okular`. I think the ideal (from a flatpak perspective) would be for okular to use one d-bus service with a consistent name rather than having a unique service per-process. This way the flatpak would only need permission for that particular service instead of the entire session bus. It would also mean there would be no issue with PID collisions, so those would not have to be shared with the parent namespace. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 432271] Can't save a file out of Okular
https://bugs.kde.org/show_bug.cgi?id=432271 --- Comment #15 from dma...@mailbox.org --- (In reply to Albert Astals Cid from comment #14) Hi, first of all thanks your code care efforts, cifs means a samba share, where files are offered within a network for a plenty of users. I suggest you set up a virtual machine for it, for example an Ubuntu Server 20.04 LTS. Samba setup on the server: sudo apt install samba sudo adduser --no-create-home --disabled-login --shell /bin/false testuser sudo smbpasswd -a testuser sudo mkdir /srv/data/all sudo vim /etc/samba/smb.cnf ... workgroup = team ... [testusershare] comment = Testuser Directories path = /srv/data/all browsable = yes read only = no create mask = 0770 force create mode = 0770 directory mask = 0770 force directory mode = 0770 inherit permissions = yes inherit acls = yes sudo systemctl restart smbd On the client side, i. e. a current Ubuntu: sudo mkdir /media/testusershare sudo apt install cifs-utils vim /home//.smbcredentials username=testuser password= chmod 600 /home//.smbcredentials vim /etc/fstab ... ///testusershare /media/testusershare cifs credentials=/home//.smbcredentials, uid=,gid=,vers=3.1.1,nobrl 0 0 ... sudo mount -a Voilà, then you should be able to save pdf files on /media/testusershare for testing purpose. Regards, dm -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 456058] On macOS, Okular does not handle open document action and does not declare supported file types in Info.plist
https://bugs.kde.org/show_bug.cgi?id=456058 nil-admir...@mailo.com changed: What|Removed |Added CC||nil-admir...@mailo.com Summary|Okular cannot load PDF file |On macOS, Okular does not |by dragging to the Dock |handle open document action |icon or "open with" |and does not declare ||supported file types in ||Info.plist Version|22.04.2 |24.05.1 Component|PDF backend |general --- Comment #1 from nil-admir...@mailo.com --- Encountered the same problem while trying to set Okular as a default DjVu files viewer: https://apple.stackexchange.com/questions/473651/open-djvu-with-an-app-that-doesnt-declare-djvu-support?noredirect=1#comment707323_473651. Got the response: > If I remember correctly, the open document action is implemented with > AppleEvents. > It's possible they didn't handle that in the code. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 432271] Can't save a file out of Okular
https://bugs.kde.org/show_bug.cgi?id=432271 dma...@mailbox.org changed: What|Removed |Added CC||dma...@mailbox.org --- Comment #13 from dma...@mailbox.org --- Same here: Pdf opened from samba share, after annotating 2-3 times, save/save as fail (file can't save in /tmp/okular.xyz). Same pdf opened from the local file system, after annotation 2-3 times, save/save as work as expected. Archlinux, i3wm, Okular version 24.05.1 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 461390] EPub rendered with HUGE font.
https://bugs.kde.org/show_bug.cgi?id=461390 --- Comment #2 from mil...@gmail.com --- fixed python code #!/usr/bin/env python3 # convert css values from short float to full float # example: .9 to 0.9 # aka: expand minified float values # fix too large fonts in okular # TODO regex is bad. use a proper css linter: stylelint # https://bugs.kde.org/show_bug.cgi?id=461390 import re, sys with open(sys.argv[1], "r") as f: css = f.read() print(re.sub(r":\s*\.([0-9]+)([a-zA-Z]+)\s*;", r":0.\1\2;", css)) -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 461390] EPub rendered with HUGE font.
https://bugs.kde.org/show_bug.cgi?id=461390 mil...@gmail.com changed: What|Removed |Added CC||mil...@gmail.com --- Comment #1 from mil...@gmail.com --- still an issue Okular Version 23.08.5 EPub Backend Version 0.2.3 sample epub file https://annas-archive.org/md5/6985fb6687007f71313d73356e71dbcc on page 2 there are 2 lines »Sei du selbst die Veränderung, die du dir wünschst für diese Welt« Mahatma Ghandi (1869–1948) for the curious, the quote translates to "Be the change you want to see in the world" html: OEBPS/xhtml/halftitle.html »Sei du selbst die Veränderung ...« Mahatma Ghandi (1869–1948) css: OEBPS/css/9783280037188.css .noindentd1 { font-size: 1em; } .right { font-size: .9em; } line 1 has normal size line 2 is too large line 1 has height 21px line 2 has height 186px 186px should be 19px so apparently font-size: .9em is parsed as font-size: 9em workaround: convert font size from short float to full float #!/usr/bin/env python3 # convert css font size from short float to full float # fix too large fonts in okular import re import sys with open(sys.argv[1], "r") as f: css = f.read() def replace(match): a, b, c = match.groups() #b = str(round(float(b) * 100)) + "%" # convert em to percent b = str(float(b)) + "em" # convert short float to full float: .9 to 0.9 return a + b + c css = re.sub(r"(font-size:\s*)([0-9]+|[0-9]+\.|\.[0-9]+|[0-9]+\.[0-9]+)em(\s*;)", replace, css, re.S) print(css) -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 489038] Stamp tool in dark mode get white on white
https://bugs.kde.org/show_bug.cgi?id=489038 kevindu52defarg...@protonmail.com changed: What|Removed |Added CC||kevindu52defargoth@protonma ||il.com -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 489038] Stamp tool in dark mode get white on white
https://bugs.kde.org/show_bug.cgi?id=489038 --- Comment #1 from kevindu52defarg...@protonmail.com --- Created attachment 170858 --> https://bugs.kde.org/attachment.cgi?id=170858&action=edit breeze dark (can't see what I am doing) -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 489038] New: Stamp tool in dark mode get white on white
https://bugs.kde.org/show_bug.cgi?id=489038 Bug ID: 489038 Summary: Stamp tool in dark mode get white on white Classification: Applications Product: okular Version: 24.05.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: kevindu52defarg...@protonmail.com Target Milestone: --- Created attachment 170857 --> https://bugs.kde.org/attachment.cgi?id=170857&action=edit breeze (working as intented) SUMMARY When using the stamp tool in Okular, we see a rectangle to show the area to cover. When Okular is in dark mode, this rectangle gets white on the white background. STEPS TO REPRODUCE 1. Open Okular. 2. Create a stamp in Settings > Configure Okular > Annotations > Add. 3. Use the "Stamp" button on a file. A rectangle appears to show where you will put the stamp. 4. Switch to dark mode (Go on Settings > Color Scheme > Breeze dark). 5. Try to use the stamp. OBSERVED RESULT The rectangle is white on white. EXPECTED RESULT The color of this rectangle should adapt to the color of the document instead of the theme. Maybe an alternating black/white rectangle could be use to be always visible. SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.1.0 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-41-generic (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Works on all types of files I tried. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 488497] Markdown not respecting linebreak
https://bugs.kde.org/show_bug.cgi?id=488497 machinedreamcatc...@temp752.ynh.fr changed: What|Removed |Added Status|REOPENED|NEEDSINFO Resolution|--- |NOT A BUG --- Comment #4 from machinedreamcatc...@temp752.ynh.fr --- > (Joplin, Zotero, Typora as desktop editors, or websites such as popular > software forges) are actually following as a base a common spec called > CommonMark (sometimes referred-to as "Github-flavoured"). It seems to me > relatively widespread, even if not the unique path as you demonstrated. After further research, the CommonMark spec alone is not enough to cover that linebreak issue, as show this page: https://markdown-it.github.io ("CommonMark strict" does not convert newlines in paragraphs as linebreaks, but checking the extra feature "breaks" would do it). In the section dedicated to soft and hard breaks, [the specs say](https://spec.commonmark.org/0.31.2/#example-649) that `a renderer may also provide an option to render soft line breaks as hard line breaks.` So the softwares I mentionned earlier may be using CommonMark-based markdown rendered together with extra-features, in particular for linebreak. But any CommonMark-based renderer is supposed to allow forcing hard linebreaks by adding a backslash OR 2 spaces or more at the end of a line. As for Discount, it also implements a way to force hard linebreak [since version 2.1.5a](https://www.pell.portland.or.us/~orc/Code/discount/#v2.1.5a) (and it works at least from Okular 21.12.3): `[support for github flavored markdown] input methods that put hardbreaks (== two spaces) at the end of every input line. The bahavior of linebreaks in Markdown has actually is being [subject to debate](https://talk.commonmark.org/search?q=line%20break), and personnally I would rather have the option to consider newline as linebreak, ideally within the same paragraph. > I do think that - at some point - it could make sense to switch Okular from > libdiscount to Qt's recently-ish gained markdown support (iirc based upon > md4c) but don't hold your breath for it. Will happily review patches though. Thank you for the feedback. [According to MD4C](https://github.com/mity/md4c?tab=readme-ov-file#links-to-related-projects), QT do use their implementation. MD4C has CommonMark and Github-flavour, as well as extra optional features, potentially the one regarding linebreaks. QT implements a strict CommonMark rendered as well a Github-flavoured one (according to the parameters which is set when using the method). Markdown-related methods seems to be implemented in `QTextDocument` & `QTextEdit` classes. Are those related to the former what you had in mind ? https://docs.w3cub.com/qt/qtextdocument#setMarkdown https://docs.w3cub.com/qt/qtextdocument#toMarkdown While I have never worked on a C++/QT/KDE project so far, it could be a starting point... This is not something I could work on with a high priority either, but I quickly checked the code and I guess I would have to focus on that folder : https://invent.kde.org/graphics/okular/-/tree/master/generators/markdown?ref_type=heads Would you have in mind: 1. Where in the code is libmarkdown (Discount) being called so far ? I could see mentions of it in what seem the build instructions or as comments in `/generators/markdown/converter.cpp`, but could not spot an actual call to the library. 2. Is the Markdown class (in converter.cpp) used to both render view and generate file ? In that case, the general markdown ouput string would be the one returned at the following line ? https://invent.kde.org/graphics/okular/-/blob/master/generators/markdown/converter.cpp?ref_type=heads#L177 Also, should QT/MD4C Markdown renderer be implemented as the new and only markdown backend, or should it be optional and offered as an alternative backend to Discount in the [configuration window](https://docs.kde.org/stable5/en/okular/okular/configure-backends.html)? Not sure whether this is feasible with QT, but ideally the config panel would offer optional markdown features included in MD4C. PS: could this bug report be moved to the Request section? -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 488497] Markdown not respecting linebreak
https://bugs.kde.org/show_bug.cgi?id=488497 machinedreamcatc...@temp752.ynh.fr changed: What|Removed |Added Ever confirmed|0 |1 Resolution|NOT A BUG |--- Status|RESOLVED|REOPENED --- Comment #2 from machinedreamcatc...@temp752.ynh.fr --- Thank you for noting this. So it is not a bug indeed and more of a feature request (not sure if there is room for this here). I was actually under the impression it was a bug due to the fact all the places I have been editing markdown (Joplin, Zotero, Typora as desktop editors, or websites such as popular software forges) are actually following as a base a common spec called CommonMark (sometimes referred-to as "Github-flavoured"). It seems to me relatively widespread, even if not the unique path as you demonstrated. Would it make sense to integrate this one to Okular (implementations of it already exist in a bunch of languages)? https://spec.commonmark.org/ https://github.com/commonmark/commonmark-spec/wiki/List-of-CommonMark-Implementations -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 488497] New: Markdown not respecting linebreak
https://bugs.kde.org/show_bug.cgi?id=488497 Bug ID: 488497 Summary: Markdown not respecting linebreak Classification: Applications Product: okular Version: 21.12.3 Platform: Mint (Ubuntu based) OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: markdown backend Assignee: okular-devel@kde.org Reporter: m...@protonmail.com Target Milestone: --- Created attachment 170496 --> https://bugs.kde.org/attachment.cgi?id=170496&action=edit Test markdown file and its PNG preview ISSUE ** Opening markdown files in Okular doesn't render correctly single linebreaks (it shows double linebreaks though), e.g. (indent only added here for the report clarity's sake): First Item Second Item Third Item Fourth Item Will be displayed as: First Item Second Item Third Item Fourth Item Full test file and PNG preview attached SOFTWARE/OS VERSIONS OS: Linux Mint 21 (Ubuntu 22.04 based). No difference whether using: - OS repo installation * Okular 21.12.3 * KDE Frameworks Version: 5.92.0-0ubuntu1 * Qt Version: 5.15.3 - Flatpak install * Okular 24.05.1 * KDE Frameworks Version: 6.2.0 * Qt Version: 6.6.3 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 488376] Okular not displaying some de facto standard annotation icons
https://bugs.kde.org/show_bug.cgi?id=488376 --- Comment #3 from nilskemail+...@gmail.com --- Reported upstream as https://gitlab.freedesktop.org/poppler/poppler/-/issues/1492 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 488377] New: Annotation tooltip stays at previous location even when moving cursor to new annotation
https://bugs.kde.org/show_bug.cgi?id=488377 Bug ID: 488377 Summary: Annotation tooltip stays at previous location even when moving cursor to new annotation Classification: Applications Product: okular Version: 24.05.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: nilskemail+...@gmail.com Target Milestone: --- Created attachment 170386 --> https://bugs.kde.org/attachment.cgi?id=170386&action=edit Demonstration of the tooltip staying in the old place even after moving the cursor to a different annotation SUMMARY When hovering over an annotation (until the tooltip opens) and then moving the cursor to a different annotation, the tooltip simply gets replaced with the content of the new tooltip but stays at the previous location instead of being moved next to the newly hovered-over annotation STEPS TO REPRODUCE 1. Open http://mirrors.ctan.org/macros/latex/contrib/pdfcomment/doc/pdfcomment.pdf 2. Scroll to section 1.2.4 (page 5) 3. Hover over an annotation icon 4. Quickly move the cursor over a different annotation icon OBSERVED RESULT The tooltip stays at the previous location but the content is replaced with the new one. EXPECTED RESULT The tooltip next to the old annotation should fade out and a new tooltip should appear next the newly hovered-over annotation SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 Kernel Version: 6.8.11-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics Memory: 30.7 GiB of RAM Graphics Processor: AMD Radeon 780M Manufacturer: Framework Product Name: Laptop 13 (AMD Ryzen 7040Series) System Version: A7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 488376] New: Okular not displaying some de facto standard annotation icons
https://bugs.kde.org/show_bug.cgi?id=488376 Bug ID: 488376 Summary: Okular not displaying some de facto standard annotation icons Classification: Applications Product: okular Version: 24.05.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: nilskemail+...@gmail.com Target Milestone: --- Created attachment 170385 --> https://bugs.kde.org/attachment.cgi?id=170385&action=edit A screenshot of the de-facto standard annotation icons which are not supported SUMMARY Okular does not display the Check, Star, RightArrow, RightPointer, UpArrow, UpLeftArrow, and CrossHairs icons STEPS TO REPRODUCE 1. Open http://mirrors.ctan.org/macros/latex/contrib/pdfcomment/doc/pdfcomment.pdf 2. Scroll to section 1.2.4 OBSERVED RESULT Of the non-mandatory icons, only Circle and Cross are shown (though the others are clickable - so they are simply invisible). EXPECTED RESULT The other icons should also be supported, or at least a fallback icon should be displayed. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION - Chromium simply displays them with the Comment icon. - PDF.js displays them as "[Star Annotation]" etc. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 488345] New: [BUG] On color change shortcut to toggle main toolbar is reset
https://bugs.kde.org/show_bug.cgi?id=488345 Bug ID: 488345 Summary: [BUG] On color change shortcut to toggle main toolbar is reset Classification: Applications Product: okular Version: 24.05.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: owl-from-hogva...@protonmail.com Target Milestone: --- SUMMARY When I toggle `Color change` tick, `toggle main toolbar` shortcut is reset to `None`. STEPS TO REPRODUCE 1. Set up shortcut for `Main toolbar` to something like `Ctrl + Shift + G` 2. Enable `Color change` 3. Save settings 4. Disable `Color change` 5. Save settings 6. Navigate to `Main toolbar` shortcut and watch it reset to `None` OBSERVED RESULT `Main toolbar` shortcut is reset when `Color change` is toggled. EXPECTED RESULT Shortcuts should be unaffected by changes in accessibility settings SOFTWARE/OS VERSIONS KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 487876] Bookmark sidebar doesn't update
https://bugs.kde.org/show_bug.cgi?id=487876 technpi...@gmail.com changed: What|Removed |Added CC||technpi...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 487876] New: Bookmark sidebar doesn't update
https://bugs.kde.org/show_bug.cgi?id=487876 Bug ID: 487876 Summary: Bookmark sidebar doesn't update Classification: Applications Product: okular Version: 23.08.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: technpi...@gmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Bookmarks do not appear in the bookmark list on the left sidebar when added, and do not disappear when removed. The list update can be triggered by toggling "Show for all documents" checkbox. STEPS TO REPRODUCE 1. Open a PDF document, ensure the Bookmarks tab is open on the left side bar. 2. Add a bookmark or remove a bookmark OBSERVED RESULT The bookmarks list does not update. EXPECTED RESULT The bookmarks list should update and either add the newly created bookmark, or remove the newly deleted bookmark. SOFTWARE/OS VERSIONS Windows: 11 Pro (Version 10.0.22631.3593) macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Installed via Microsoft Store, no application updates are available. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 452430] PDF: Find in view mode "facing pages" scroll to incorrect places
https://bugs.kde.org/show_bug.cgi?id=452430 yvan.vele...@hispeed.ch changed: What|Removed |Added CC||yvan.vele...@hispeed.ch --- Comment #6 from yvan.vele...@hispeed.ch --- I can confirm this bug when I have both "Facing pages" and "Continuous" enabled and zoom set to "Fit page". -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 339971] Detach Tabs / Combine multiple windows in tabs
https://bugs.kde.org/show_bug.cgi?id=339971 dmatteo...@gmail.com changed: What|Removed |Added CC||dmatteo...@gmail.com -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 487733] New: Make annotations compatible with other readers like Kobo Elipsa and Google Drive
https://bugs.kde.org/show_bug.cgi?id=487733 Bug ID: 487733 Summary: Make annotations compatible with other readers like Kobo Elipsa and Google Drive Classification: Applications Product: okular Version: 24.05.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: elia...@protonmail.ch Target Milestone: --- SUMMARY Currently it is possible to read annotations done on Kobo Elipsa in Okular. But the other way around is not true. Most annotations done in Okular are invisible to Kobo Elipsa. The only visible annotation is the free-line. Why not make other kinds of annotations (highlights, text additions) compatible as well? It would be very useful if they were. Or is it something that Kobo needs to implement? -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 487723] make adding text UI a little easier to use
https://bugs.kde.org/show_bug.cgi?id=487723 imthenacho...@gmail.com changed: What|Removed |Added CC||imthenacho...@gmail.com -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[okular] [Bug 487721] being able to change color of form field text
https://bugs.kde.org/show_bug.cgi?id=487721 imthenacho...@gmail.com changed: What|Removed |Added CC||imthenacho...@gmail.com Blocks|487723 | Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=487723 [Bug 487723] make adding text UI a little easier to use -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 487723] make adding text UI a little easier to use
https://bugs.kde.org/show_bug.cgi?id=487723 imthenacho...@gmail.com changed: What|Removed |Added Depends on|487721 | Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=487721 [Bug 487721] being able to change color of form field text -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
[okular] [Bug 487721] being able to change color of form field text
https://bugs.kde.org/show_bug.cgi?id=487721 imthenacho...@gmail.com changed: What|Removed |Added Blocks||487723 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=487723 [Bug 487723] make adding text UI a little easier to use -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 487723] New: make adding text UI a little easier to use
https://bugs.kde.org/show_bug.cgi?id=487723 Bug ID: 487723 Summary: make adding text UI a little easier to use Classification: Applications Product: okular Version: 23.08.5 Platform: Kubuntu OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: imthenacho...@gmail.com CC: okular-devel@kde.org Depends on: 487721 Target Milestone: --- Okular is a fantastic PDF reader/tool. I find the text entry (typewriter) UI a little clunky. You have to draw a box and then enter text in a pop-up that gets embedded in. I think it would be a lot cleaner if you can just click where you want to start typing and then type live in the document. That way you can get a better sense of placement and what not. Kind of how Adobe PDF or PDF Studio do it. Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=487721 [Bug 487721] being able to change color of form field text -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.
[okular] [Bug 487721] New: being able to change color of form field text
https://bugs.kde.org/show_bug.cgi?id=487721 Bug ID: 487721 Summary: being able to change color of form field text Classification: Applications Product: okular Version: 23.08.5 Platform: Kubuntu OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: imthenacho...@gmail.com Target Milestone: --- This is just a small feature request. I think it would be great if we could change the font/text color of form fields. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 487486] 24.05.0 crashes on start and complains about missing dll's on Windows
https://bugs.kde.org/show_bug.cgi?id=487486 gfowl...@outlook.com changed: What|Removed |Added Summary|24.05.0 crashes on start|24.05.0 crashes on start |and complains about missing |and complains about missing |dll's |dll's on Windows -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 487486] New: 24.05.0 crashes on start and complains about missing dll's
https://bugs.kde.org/show_bug.cgi?id=487486 Bug ID: 487486 Summary: 24.05.0 crashes on start and complains about missing dll's Classification: Applications Product: okular Version: 24.05.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: gfowl...@outlook.com Target Milestone: --- Hi, The latest 24.05.0 release crashes on start and complains about missing dll's. Both the exe and appx. Thank you -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 384147] Hovering over annotations no longer shows contents in tooltip
https://bugs.kde.org/show_bug.cgi?id=384147 nilskemail+...@gmail.com changed: What|Removed |Added CC||nilskemail+...@gmail.com --- Comment #11 from nilskemail+...@gmail.com --- This seems to have regressed again (Okular 24.02.2 on Fedora 40). Should I create a new bug or reopen this one? -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 473679] Pinch to zoom with touchpad
https://bugs.kde.org/show_bug.cgi?id=473679 janiu...@protonmail.com changed: What|Removed |Added CC||janiu...@protonmail.com -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 483204] Strange behavior when copy as image and pasting. The pasted image lacks clarity
https://bugs.kde.org/show_bug.cgi?id=483204 --- Comment #6 from ree...@gmail.com --- Do you need any additional information? This bug is not critical, but it is highly annoying and I'd be glad to provide more information if I can. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 465055] All PDFs are shown stretched in y-axis
https://bugs.kde.org/show_bug.cgi?id=465055 --- Comment #27 from pi...@gmx.de --- Since Okular Version 23.08.5 (fresh install of Kubuntu 24.04) the "hack" with a reload doesn't work anymore. It is now always stretched... Can no one else reproduce this? -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 486681] Display comments created by latex pdfcomment
https://bugs.kde.org/show_bug.cgi?id=486681 --- Comment #4 from aux...@gmail.com --- Created attachment 169259 --> https://bugs.kde.org/attachment.cgi?id=169259&action=edit LaTeX source -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 486681] Display comments created by latex pdfcomment
https://bugs.kde.org/show_bug.cgi?id=486681 --- Comment #2 from aux...@gmail.com --- Created attachment 169257 --> https://bugs.kde.org/attachment.cgi?id=169257&action=edit PDF file with 2 acronyms demonstrating the issue. The two acronyms are REST, SOAP. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 486681] New: Display comments created by latex pdfcomment
https://bugs.kde.org/show_bug.cgi?id=486681 Bug ID: 486681 Summary: Display comments created by latex pdfcomment Classification: Applications Product: okular Version: 24.02.1 Platform: openSUSE OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: PDF backend Assignee: okular-devel@kde.org Reporter: aux...@gmail.com Target Milestone: --- SUMMARY Comments in PDF files created by latex/xelatex acro/pdfcomment do not display in Okular, although evince displays them. Such comments are useful to display acronyms. STEPS TO REPRODUCE 1. Write a TeX file using latex, acro, pdfcomment, that includes acronyms and pdfcomments. 2. Open it with okular. OBSERVED RESULT The acronym pdfcomment is not displayed when I hover the cursor over the acronym. The mouse cursor changes shape over acronyms, which implies that Okular identifies the string as an acronym. EXPECTED RESULT The acronym pdfcomment is displayed on hover over the acronym. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed (available in About System) KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 476436] German umlaute are not shown in textfields in this PDF document
https://bugs.kde.org/show_bug.cgi?id=476436 steffen-wink...@posteo.de changed: What|Removed |Added Version|23.08.1 |24.02.2 -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 476436] German umlaute are not shown in textfields in this PDF document
https://bugs.kde.org/show_bug.cgi?id=476436 steffen-wink...@posteo.de changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #6 from steffen-wink...@posteo.de --- As the original bug creator, I checked and I can confirm this bug with the linked document on Okular 24.02.2. I can also confirm that the bug exists (again?) when using my attached document. -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 486077] Okular window does not activate when opening pdf file from nautilus ("Files" application in Gnome)
https://bugs.kde.org/show_bug.cgi?id=486077 fanzhuyi...@gmail.com changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REPORTED|RESOLVED CC||fanzhuyi...@gmail.com --- Comment #1 from fanzhuyi...@gmail.com --- Thank you for your bug report! Debian advises users to not submit bugs upstream (https://www.debian.org/Bugs/Reporting), as this version of the KDE software is out of support from KDE, and so it's possible that the bug exists only in Debian at this point. Could you report the bug to Debian using the report bug utility (https://packages.debian.org/stable/utils/reportbug)? If necessary, the maintainer of the package will forward the bug upstream. Thanks for understanding! -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 486027] New: Scrollbars almost invisible
https://bugs.kde.org/show_bug.cgi?id=486027 Bug ID: 486027 Summary: Scrollbars almost invisible Classification: Applications Product: okular Version: 24.02.2 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: elia...@protonmail.ch Target Milestone: --- Created attachment 168843 --> https://bugs.kde.org/attachment.cgi?id=168843&action=edit Scrollbar sample SUMMARY: The scroll bar and its background have very close colors, so much so that the scroll bar is almost invisible! STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 485721] New: Okular crashed after clicking the drop menu item "Configure annotations..."
https://bugs.kde.org/show_bug.cgi?id=485721 Bug ID: 485721 Summary: Okular crashed after clicking the drop menu item "Configure annotations..." Classification: Applications Product: okular Version: 23.08.1 Platform: Ubuntu OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: bugs.kde@gobuki.org Target Milestone: --- Application: okular (23.08.1) Qt Version: 5.15.10 Frameworks Version: 5.110.0 Operating System: Linux 6.5.0-27-generic x86_64 Windowing System: X11 Distribution: Ubuntu 23.10 DrKonqi: 5.27.8 [KCrashBackend] -- Information about the crash: The window did not open. Instead the application immediately crashed. The crash can be reproduced sometimes. -- Backtrace: Application: Okular (okular), signal: Segmentation fault [KCrash Handler] #4 __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:76 #5 0x7b8311fd9d7a in ?? () from /lib/x86_64-linux-gnu/libspeechd.so.2 #6 0x7b8311fdaa6d in ?? () from /lib/x86_64-linux-gnu/libspeechd.so.2 #7 0x7b8311fe6d12 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/texttospeech/libqtexttospeech_speechd.so #8 0x7b8311fe8f5b in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/texttospeech/libqtexttospeech_speechd.so #9 0x7b832e5d5cae in ?? () from /lib/x86_64-linux-gnu/libQt5TextToSpeech.so.5 #10 0x7b832e5d6122 in QTextToSpeech::QTextToSpeech(QString const&, QObject*) () from /lib/x86_64-linux-gnu/libQt5TextToSpeech.so.5 #11 0x7b83240c81a5 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/okularpart.so #12 0x7b8332d06312 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7b8333a71a75 in QComboBox::currentIndexChanged(int) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7b8333a732e6 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7b8333a76c5b in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7b8333a77003 in QComboBox::setCurrentIndex(int) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7b8333a7e01b in QComboBox::qt_metacall(QMetaObject::Call, int, void**) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7b8332cdae4a in QMetaProperty::write(QObject*, QVariant const&) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7b8332d04650 in QObject::setProperty(char const*, QVariant const&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7b83343c1c0f in KConfigDialogManager::setProperty(QWidget*, QVariant const&) () from /lib/x86_64-linux-gnu/libKF5ConfigWidgets.so.5 #21 0x7b83343c3ca0 in KConfigDialogManager::setupWidget(QWidget*, KConfigSkeletonItem*) () from /lib/x86_64-linux-gnu/libKF5ConfigWidgets.so.5 #22 0x7b83343c43c0 in KConfigDialogManager::parseChildren(QWidget const*, bool) () from /lib/x86_64-linux-gnu/libKF5ConfigWidgets.so.5 #23 0x7b83343c5a70 in KConfigDialog::addPage(QWidget*, QString const&, QString const&, QString const&, bool) () from /lib/x86_64-linux-gnu/libKF5ConfigWidgets.so.5 #24 0x7b83240ccefc in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/okularpart.so #25 0x7b83240ee40c in Okular::Part::slotAnnotationPreferences() () from /usr/lib/x86_64-linux-gnu/qt5/plugins/okularpart.so #26 0x7b8332d06312 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7b8333965256 in QAction::triggered(bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x7b8333967f57 in QAction::activate(QAction::ActionEvent) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #29 0x7b8333af0d22 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7b8333af8bdb in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7b83339aeb28 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #32 0x7b833396bc82 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #33 0x7b83339741bd in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #34 0x7b8332ccc7a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #35 0x7b83339724b2 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #36 0x7b83339c886a in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #37 0x7b83339cb12f in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #38 0x7b833396bc82 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #39 0x7b8332ccc7a8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #40 0x7b8333143bdb in QGuiApplicationPrivate::processMouseEvent(QWin
[okular] [Bug 484294] Size of the text in forms while editing is dependent on pdf size
https://bugs.kde.org/show_bug.cgi?id=484294 --- Comment #3 from mifoo...@vivaldi.net --- Created attachment 168430 --> https://bugs.kde.org/attachment.cgi?id=168430&action=edit A PDF to test the bug -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 485445] New: Okluar crashes after computer enters Screen Energy Saving Mode
https://bugs.kde.org/show_bug.cgi?id=485445 Bug ID: 485445 Summary: Okluar crashes after computer enters Screen Energy Saving Mode Classification: Applications Product: okular Version: 23.08.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: mkschu...@gmail.com Target Milestone: --- Application: okular (23.08.3) Qt Version: 5.15.11 Frameworks Version: 5.111.0 Operating System: Linux 6.6.8-200.fsync.fc38.x86_64 x86_64 Windowing System: X11 Distribution: Nobara Linux 38 (KDE Plasma) DrKonqi: 5.27.9 [KCrashBackend] -- Information about the crash: When waking from Screen Energy Saving, Okular will crash. Seemingly, the longer the computer has been in this mode, the more likely Okular is to crash. For example, if I happen to be by my computer when the screen turns off and I immediately wake it, Okular will most likely not crash. When I return to my computer from this state overnight, it is almost guaranteed to have crashed. The crash can be reproduced every time. -- Backtrace: Application: Okular (okular), signal: Segmentation fault [KCrash Handler] #4 0x7febd7578ecd in __memmove_avx_unaligned_erms () from /lib64/libc.so.6 #5 0x7febd36b63ba in QXcbBackingStoreImage::flushPixmap(QRegion const&, bool) [clone .part.0] () from /lib64/libQt5XcbQpa.so.5 #6 0x7febd36b6a42 in QXcbBackingStoreImage::put(unsigned int, QRegion const&, QPoint const&) () from /lib64/libQt5XcbQpa.so.5 #7 0x7febd36b73d2 in QXcbBackingStore::flush(QWindow*, QRegion const&, QPoint const&) () from /lib64/libQt5XcbQpa.so.5 #8 0x7febd8304f16 in QBackingStore::flush(QRegion const&, QWindow*, QPoint const&) () from /lib64/libQt5Gui.so.5 #9 0x7febd89bcd4d in QWidgetRepaintManager::flush(QWidget*, QRegion const&, QPlatformTextureList*) () from /lib64/libQt5Widgets.so.5 #10 0x7febd89be938 in QWidgetRepaintManager::flush() () from /lib64/libQt5Widgets.so.5 #11 0x7febd89c0a86 in QWidgetRepaintManager::paintAndFlush() () from /lib64/libQt5Widgets.so.5 #12 0x7febd8a0c991 in QWidgetWindow::handleResizeEvent(QResizeEvent*) () from /lib64/libQt5Widgets.so.5 #13 0x7febd8a10917 in QWidgetWindow::event(QEvent*) () from /lib64/libQt5Widgets.so.5 #14 0x7febd89aeb75 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #15 0x7febd7cb4538 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #16 0x7febd816982e in QGuiApplicationPrivate::processGeometryChangeEvent(QWindowSystemInterfacePrivate::GeometryChangeEvent*) () from /lib64/libQt5Gui.so.5 #17 0x7febd814acfc in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib64/libQt5Gui.so.5 #18 0x7febd36c24d6 in xcbSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5XcbQpa.so.5 #19 0x7febd63134fc in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #20 0x7febd63716b8 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0 #21 0x7febd6310b83 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #22 0x7febd7d06ad9 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #23 0x7febd7cb2efb in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #24 0x7febd7cbb18b in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #25 0x55ff8b959d0d in main () [Inferior 1 (process 52830) detached] The reporter indicates this bug may be a duplicate of or related to bug 473405. Reported using DrKonqi -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 485442] [Feature Request] Adding shortcuts to call a shell script.
https://bugs.kde.org/show_bug.cgi?id=485442 zaidkharouf30...@gmail.com changed: What|Removed |Added Keywords||efficiency, usability -- You are receiving this mail because: You are the assignee for the bug.
[okular] [Bug 485442] New: [Feature Request] Adding shortcuts to call a shell script.
https://bugs.kde.org/show_bug.cgi?id=485442 Bug ID: 485442 Summary: [Feature Request] Adding shortcuts to call a shell script. Classification: Applications Product: okular Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-devel@kde.org Reporter: zaidkharouf30...@gmail.com Target Milestone: --- Adding an option to use custom Shortcuts that executes a shell script, or a command like so: In the shortcuts menu, you can add option, add custom shortcut which asks for a shell command, or a script to execute. Some examples: F xdotool super+f e alacritty -e 'lf' o dmenu_recent_okular ( this could be a user shell-script ) It would make okular much more extensible. -- You are receiving this mail because: You are the assignee for the bug.