[frameworks-ktexteditor] [Bug 443642] Selection clipboard no longer works with Shift + click
https://bugs.kde.org/show_bug.cgi?id=443642 David Hurka changed: What|Removed |Added Resolution|WORKSFORME |--- Version|5.86.0 |5.90.0 Status|RESOLVED|REPORTED --- Comment #6 from David Hurka --- I tested this on my other computer, which has KDE Neon developer edition, with KF 5.91 and Kate 22.03.70. It still doesn’t work as I described in “Steps to reproduce”. But it works if I do “Hold shift and click-and-drag somewhere else” instead of step 4. I. e. I need to do a slight mouse movement during the second click. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 454443] The Recent files menu is disabled if it contains only one file
https://bugs.kde.org/show_bug.cgi?id=454443 --- Comment #3 from David Hurka --- I think it is a bug. This menu is even disabled if “Switch to tab if file is already open” is disabled, although it would do something: open the file again. I do this sometimes with long documents, where I need to switch between two chapters often. If I didn’t open other documents before, so the recent files menu is disabled, it will slow me down. Then I wonder why. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421040] Mouse warp effect can't be disabled (wrap to opposite screen edge at drag srolling)
https://bugs.kde.org/show_bug.cgi?id=421040
--- Comment #18 from David Hurka ---
You should look at the existing merge requests (most of them already merged),
which we got about scrolling.
At least one of them is concerned about exactly this.
They can show you which code is related to this.
Adding this checkbox to the configuration dialog should be easy.
You can look how the other checkboxes are implemented (KConfigXT), add this
one, and then wrap the call to CursorWrapHelper in an if(){} thing, just like
the other checkboxes are queried.
I can’t tell whether that MR would be accepted.
The only problem would be UI clutter in the configuration dialog.
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 455013] Port sidebar to QDockWidget
https://bugs.kde.org/show_bug.cgi?id=455013 --- Comment #1 from David Hurka --- Good idea, but note that Okular is designed as KParts application. There is an Okular shell, which has a main window, and an Okular part, which does the document view and implements the sidebar. The part provides a widget which is placed in the tab widget of the shell. Therefore, the part can not use QDockWidget in the straightforward way like a “normal” application could do. Personally, I would like to see the sidebar in dock widgets. So if you know a good solution to implement that, let us know. :) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 455115] Show pop-up notes text more directly
https://bugs.kde.org/show_bug.cgi?id=455115 --- Comment #3 from David Hurka --- Some video games rely on mouse hover tooltips, and therefore show them instantly. It would (probably) be possible to do the same for annotation tooltips in Okular. Okular should not rely on tooltips, because there are also touchscreen users. So I think the last suggestion makes more sense, where comments are always displayed somewhere. Until any of that is implemented, I suggest you enable the focus policy “Focus follows mouse”, which is a setting somewhere in the window behavior. That saves you at least one click. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 455118] Documentation on development workflow
https://bugs.kde.org/show_bug.cgi?id=455118 --- Comment #9 from David Hurka --- > But then what? Always make install first to some temp dir? > Or can you directly execute the binary? > Do you need to setup the LD path such that it finds the so files? This should be explained in Okulars README, see https://invent.kde.org/graphics/okular#build-instructions. In particular, prefix.sh sets the path variables of your shell, so that you can successfully run the newly compiled Okular. > I thought that other KDE/Qt packages usually use qmake, > so I thought that Okular is an exception by using cmake > and it would not follow the regular KDE packages. Maybe you have been misleaded by the long description of the cmake workflow, compared to the one-line link to the kdesrc-build introduction. The usual workflow, including Okular, is to use kdesrc-build. But under the hood it is cmake, because KDE prefers cmake over qmake. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 458859] Many icons are invisible or nearly invisible.
https://bugs.kde.org/show_bug.cgi?id=458859 David Hurka changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from David Hurka --- All I can tell from the GIF is that you do not use Breeze or Breeze Dark icon set. Can you explain which icon set you use and why you use it? If your desktop environment allows to use a dark color scheme, it would be reasonable to expect that it provides a compatible icon set. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 459093] New: Unable to configure syntax highlight themes
https://bugs.kde.org/show_bug.cgi?id=459093 Bug ID: 459093 Summary: Unable to configure syntax highlight themes Product: kate Version: 22.08.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: david.hu...@mailbox.org CC: david.hu...@mailbox.org Target Milestone: --- Created attachment 152047 --> https://bugs.kde.org/attachment.cgi?id=152047&action=edit Configuration dialog SUMMARY I noticed that the default highlighting theme for Lua has changed, and tried to change it back to what I am used to. In the configuration dialog I noticed that there were minor changes to the GUI. The new GUI does not work. Most changes to highlighting themes are immediately undone by the configuration dialog, and other changes simply have no effect. STEPS TO REPRODUCE 1. Open a code file. 2. Open configuration dialog -> Color Themes -> Theme Editor -> Highlighting Text Styles. 3. Copy the Breeze Light theme, so editing is allowed. 4. Select a line, like “Keyword”. 5. Uncheck the “Bold” checkbox. 6. Check the “Italic” checkbox. 7. Uncheck the “Use Default Style” checkbox. 8. Click “Normal” to change the text color, choose a different color. 9. Repeat steps 5 and 6. 10. Close configuration dialog. OBSERVED RESULT 3. New theme is created, and can be selected from menu bar -> Settings -> Syntax Hightlight Theme. 5. The “Bold” checkbox is immediately checked again when I click anywhere else. 6. The “Italic” checkbox keeps its new state, but is reset when I click “Apply”. 7. Can not be toggled. A message box tells me that it is changed automatically when I change other settings. 8. Colors can be changed, and the “Use Default Style” checkbox is indeed unchecked automatically. 9. The “Bold” checkbox can now be toggled, and the “Italic” checkbox even keeps its state after clicking “Apply”. 10. After selecting the new theme from the menu bar, no changes at all are visible. EXPECTED RESULT 5. and 6. The checkboxes can be toggled, and “Use Default Style” is automatically unchecked. Clicking “Apply” does not reset the checkboxes. 10. After selecting the new theme, it is actually used. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 459447] Incorrect selection by Text Selection tool on given PDF
https://bugs.kde.org/show_bug.cgi?id=459447 David Hurka changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #2 from David Hurka --- Problem of XY-Cut algorithm. The affected paragraphs are not part of a text rectangle running all across the page. On page 2, for example, the left-most paragraph works fine. *** This bug has been marked as a duplicate of bug 407133 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 407133] Copy text from rotated pdf gives rubbish
https://bugs.kde.org/show_bug.cgi?id=407133 David Hurka changed: What|Removed |Added CC||zbwu1...@gmail.com --- Comment #9 from David Hurka --- *** Bug 459447 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 458530] Crash when trying to open certificate database
https://bugs.kde.org/show_bug.cgi?id=458530 --- Comment #7 from David Hurka --- (In reply to Albert Astals Cid from comment #6) > The "Unable to open QuickAnnotatingTools XML definition" may or may not be > important, but it's also defenitely strange, did you self compile OKular or > are you running a distribution one? I guess the lazyness inherent to all humans still hasn’t shipped this file to Neon. ;) https://bugs.kde.org/show_bug.cgi?id=425887 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460622] New: Lock screen does not accept keyboard input for keys like Enter, Backspace, arrow keys
https://bugs.kde.org/show_bug.cgi?id=460622 Bug ID: 460622 Summary: Lock screen does not accept keyboard input for keys like Enter, Backspace, arrow keys Classification: Plasma Product: plasmashell Version: 5.26.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Theme - Breeze Assignee: plasma-b...@kde.org Reporter: david.hu...@mailbox.org CC: visual-des...@kde.org Target Milestone: 1.0 SUMMARY I just updated KDE Neon to Plasma 5.26, and I noticed that I fail to unlock the screen. Fortunately, there is the option to show the entered password in clear text, and a virtual keyboard. Therefore, I noticed that the password text box does not accept any input from navigation keys: Backspace and arrow keys do not have any effect. Same for Enter, and therefore I could not unlock. I managed to unlock by entering my password as usual, and then pressing the Enter button of the virtual keyboard. Of course, my buttons are physically fine. After unlocking, I can type as usual. STEPS TO REPRODUCE 1. Lock the screen. (Meta + L) 2. Press buttons on the physical keyboard. 3. Press buttons on the virtual keyboard (after clicking “virtual keyboard” in the lower left corner of the lock screen). OBSERVED RESULT Only letters from the physical keyboard are accepted. EXPECTED RESULT All buttons are accepted. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.26 KDE Plasma Version: 5.26.0 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.15.0-50-generic (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION I use neo2 keyboard layout. This layout offers a second set of navigation keys on the main field. However, both the second set and the “traditional” navigation keys are affected the same way. The second set of number keys works fine. A typical symptom of applications without neo2 support is that the second set of navigation keys and number keys are broken, and type symbols like “~/}_()-:”, or are simply dead. More ridiculous applications present gibberish like “KP_EnterKP_LeftKP_RightKP_BackspaceKP_4KP_5KP_6KP_Comma”... I conclude that the problem with the lock screen is not that neo2 is broken. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 415130] Lock and login screens: entering incorrect password or moving focus away breaks using return/enter key to submit password
https://bugs.kde.org/show_bug.cgi?id=415130 --- Comment #68 from David Hurka --- (In reply to Nate Graham from comment #67) > *** Bug 460622 has been marked as a duplicate of this bug. *** Indeed. It appeared that I can no longer reproduce it, but actually the problem begins when you enter a wrong password and ends when you turn off the computer, just like this bug report describes. Lesson: Only the correct password allows you to unlock the screen. ;) (In reply to Enrico from comment #61) > (In reply to Andrey E. from comment #60) > > There are two "Enter" keys on my laptop - the first one is on the main > > keyboard area, the second is on the numeric pad. And I can say that the > > "Main Enter" doesn't work while the "NumPad Enter" works fine. > > I confirm this behavior Don’t confirm. Only the enter key of the virtual keyboard works here. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 460681] Laggy scrolling on high DPI display - profiling indicates excessive copying in PagePainter::paintCroppedPageOnPainter
https://bugs.kde.org/show_bug.cgi?id=460681 --- Comment #3 from David Hurka --- (In reply to maximumsomething from comment #0) > I was going to go ahead and fix these things myself, but I was wondering if > anyone familiar with the code knows why it was written this way/any gotchas > that might apply if the deep copies are not made. I thought I would just mention that I have made https://invent.kde.org/graphics/okular/-/merge_requests/240 long time ago. The intention was to simplify the code, just like the title suggests. I also tried to understand the code, and prepare it for peformance improvements. I was not aware of deep copying, actually. My patch still uses setDevicePixelRatio(), so it actually does not fix this problem. Honestly I lost interest in this. If you want, you may continue the work, or just look at it if it helps you to understand anything. :) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 445851] Don't copy newlines within paragraph
https://bugs.kde.org/show_bug.cgi?id=445851 David Hurka changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=407133 --- Comment #1 from David Hurka --- > Newlines used to break the content are preserved: This is not exactly what happens. The Okular user interface does not know about newlines or paragraphs, it only knows about the positions of individual letters. If a letter is below the previous one, it inserts a newline to the selection. Besides that, I think this should not be different, at least not for PDF. If newlines are not copied, the selection will still contain hyphens. Like this: Because every-thing is on one line, it will be diffi-cult to remove the hyphens manual-ly afterwards. ;) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 407133] Copy text from rotated pdf gives rubbish
https://bugs.kde.org/show_bug.cgi?id=407133 David Hurka changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=445851 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 445842] Okular cannot open the same file twice in different tabs
https://bugs.kde.org/show_bug.cgi?id=445842 --- Comment #4 from David Hurka --- I have re-enabled this option for me, so I do not open more and more tabs of the same document, only because I am to lazy to search through all the tabs whether I have the document already open. But sometimes I want to open a second tab of one long document for the use case described. Can we add a menu action “Duplicate tab”? Many web browsers have this action too. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 445900] The icons for the annotation tools look off when compared to the general look of Okular icons
https://bugs.kde.org/show_bug.cgi?id=445900 --- Comment #4 from David Hurka --- > This creates another visual discrepancy, because now the > icons *for the same function* are different in different toolbars. This is often misunderstood. The colorful icons select a whole tool (including configuration like color and width), and try to visualize the configuration. The monochrome icons select only the type of the tool, the configuration is done by the right part of the annotation toolbar. (Since the configuration is still unique to each tool, it looks like both icons do the same.) > look ancient and [...] don't look good on low-res displays either. I agree with this. They are ancient (for computers), and they used to be displayed at a much bigger size. They didn’t have text at that time, so they needed to visualize a lot at once. > EXPECTED RESULT > An icon more like the icons in the Annotation Toolbar, and > maybe the icon can be filled with color to show the color of > the selected tool. But the paper at the back looks bad. I think your ideas are welcome. :) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 446092] Inline images using http URL don't display in rendered document
https://bugs.kde.org/show_bug.cgi?id=446092 --- Comment #2 from David Hurka --- Is this bug report about data URLs or about HTTP URLs now? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 444297] Okular "Could not open" a certain PDF, with no other details
https://bugs.kde.org/show_bug.cgi?id=444297
--- Comment #16 from David Hurka ---
There are two ways to set this message:
QMetaObject::Connection errorToOpenErrorConnection =
QObject::connect(m_generator, &Generator::error, m_parent, [this](const QString
&message) { m_openError = message; });
(in DocumentPrivate::openDocumentInternal())
d->m_openError = i18n("Can not find a plugin which is able to handle
the document being passed.");
(in Document::openDocument())
But the Poppler generator does not seem to emit the Generator::error signal.
The DVI generator emits a lot more error messages.
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-ktexteditor] [Bug 453541] New: .kateconfig kate-wildcard(...) does not allow path separators
https://bugs.kde.org/show_bug.cgi?id=453541 Bug ID: 453541 Summary: .kateconfig kate-wildcard(...) does not allow path separators Product: frameworks-ktexteditor Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: david.hu...@mailbox.org CC: david.hu...@mailbox.org Target Milestone: --- SUMMARY I am trying to configure Kate to follow the indentation style of a git repository which does not use my usual indentation style. So I put a .kateconfig file in the parent directory, which uses the kate-wildcard(subdir/*) rule. This does not work. My current workaround is to use .git/info/exclude to allow .kateconfig in the git repository itself. STEPS TO REPRODUCE 1. Add this to a .kateconfig file, assuming replace-tabs is on by default: > kate-wildcard(subdir/*): replace-tabs off; 2. Open a file from the current directory. 3. Open a file from the subdir directory. OBSERVED RESULT Both files use replace-tabs on. (In Kate status bar displayed as soft tabs.) EXPECTED RESULT The file in subdir directory uses replace-tabs off. (In Kate status bar displayed as Indent/Tab) SOFTWARE/OS VERSIONS Operating System: KDE neon 5.24 KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 453614] Highlighter Annotation not readable
https://bugs.kde.org/show_bug.cgi?id=453614 David Hurka changed: What|Removed |Added Resolution|WAITINGFORINFO |DUPLICATE Status|NEEDSINFO |RESOLVED --- Comment #4 from David Hurka --- You are in Text Selection mode. This mode will make the mouse select text if there is text. Since there is text, it does not select the annotation instead. You need to use Browse mode. I agree that this is not intuitive user interface. :( *** This bug has been marked as a duplicate of bug 155563 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 155563] Automatic text selection in Okular (instead of choosing “Browse” or “Text Selection” mouse mode)
https://bugs.kde.org/show_bug.cgi?id=155563 David Hurka changed: What|Removed |Added CC||i.proud...@oxon.org --- Comment #9 from David Hurka --- *** Bug 453614 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421206] okular presentation mode does not allow for WebRTC screensharing in Firefox/Chromium
https://bugs.kde.org/show_bug.cgi?id=421206 --- Comment #9 from David Hurka --- In the meantime I refactored the PresentationWidget code related to screen selection and fullscreen. Okular 21.12 and newer use the new code. But I can’t tell what part of it could have caused this bug to be fixed. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 455830] Can no longer use scroll wheel to scroll through document
https://bugs.kde.org/show_bug.cgi?id=455830 --- Comment #4 from David Hurka --- If you have a mouse with free spinning mouse wheel, which doesn’t scroll in discrete steps, this is Bug 443404. You can actually advance to the next page, but you need to sroll so fast that Okular sees so much scrolling at once that it is considered a discrete step. With a touchpad this is easy to do, but still very hard to control. :( -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 455830] Can no longer use scroll wheel to scroll through document
https://bugs.kde.org/show_bug.cgi?id=455830 David Hurka changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #6 from David Hurka --- Then I make it a duplicate. > It was fine in the previous version. May also be related to updating some mouse driver or other library at the same time, which previously didn’t make the bug visible. *** This bug has been marked as a duplicate of bug 443404 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443404] Mousewheel scroll does not work in full page size and non-continous mode for some mouses
https://bugs.kde.org/show_bug.cgi?id=443404 David Hurka changed: What|Removed |Added CC||mfraz74+...@gmail.com --- Comment #8 from David Hurka --- *** Bug 455830 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443404] Mousewheel scroll does not work in full page size and non-continous mode for some mouses
https://bugs.kde.org/show_bug.cgi?id=443404 David Hurka changed: What|Removed |Added OS|Linux |All Platform|Manjaro |unspecified -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 455945] Cannot modify properties when overlaping objects
https://bugs.kde.org/show_bug.cgi?id=455945 --- Comment #3 from David Hurka --- The video looks like the intended behavior. You do a rightclick to configure one of the annotations, and because there are two annotations in this place, Okular shows a context menu with two sections, one for each annotation. You select one of them, by clicking on one of the “Properties” menu items, and Okular configures that one. I see the problem, that you do not know which of the two menu sections is relevant. There is no disambiguation. The menu sections could show “Typewriter: Top obj...” instead of just “Typewriter”. It is also a bit weird that the menu shows all annotations of that position, although one of them is already selected. If there is an annotation selected, the context menu should probably show just one section for that one annotation. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 456107] Show ... toolbar actions loose all their shortcuts when okularpart configuration is modified.
https://bugs.kde.org/show_bug.cgi?id=456107 David Hurka changed: What|Removed |Added CC||kdelibs-b...@kde.org Summary|Main toolbar keyboard |Show ... toolbar actions |shortcut throwing an error. |loose all their shortcuts ||when okularpart ||configuration is modified. Status|REPORTED|CONFIRMED Platform|Archlinux Packages |unspecified Ever confirmed|0 |1 --- Comment #1 from David Hurka --- Reminds me of Bug 384700. There a shortcut was reset when the configuration of okularpart was modified, which happens in response to certain actions. In particular, “Toggle change colors” changed the configuration, which in turn caused the shortcut of “Toggle change colors” to be reset. That bug could have been worked around by avoiding action stuff in response to configuration changes, in particular by avoiding calls to refreshActionProperties(). In the end, the bug has been fixed in KXmlGui, and Okular still calls refreshActionProperties() in response to any configuration changes. In this case, the shortcut for “Main Toolbar” gets lost when the configuration of okularpart is modified, too. You describe the bug for “Show sidebar”, but other actions, which write to the configuration, like “Change colors” trigger the bug as well. But this case is also different. It says “Shortcut for action set with QAction::setShortcut()!”, which was not the case in Bug 384700. Also, it deletes any shortcut even if it was already saved to disk. I think the cause for this bug is refreshActionProperties(), again, and the fact that “Main Toolbar” is somehow special. You can notice that you can set a shortcut for this action, but you can not add it to any toolbar. The other show ... toolbar actions have the same behavior. So I think the bug is in KXmlGui, because it handles these show ... toolbars in some special way. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 457748] Review tools toolbar appears on all desktops when it's floating
https://bugs.kde.org/show_bug.cgi?id=457748 --- Comment #7 from David Hurka --- I remember this bug from the past, but can’t reproduce it now. Other KXmlGui applications seem to have “lost” the bug too. Using KDE Neon with X11, Plasma 5.25.4, Okular 22.04.3. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 458802] Okular should be able to open any PDF documents, regardless of them being tailored for Adobe Reader
https://bugs.kde.org/show_bug.cgi?id=458802 David Hurka changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from David Hurka --- Sorry, but your request seems unrealistic to me. PDF means portable, yes. But that does not prevent authors from intentionally creating bad documents. The content of this document is “Please wait ...”. It is hard to guess what Adobe Reader would show instead. In this particular case it may be enough to implement XFA. But in other cases Okular would need to guess how Adobe Reader’s implementation of XFA would behave. That would be like magic. *** This bug has been marked as a duplicate of bug 458723 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 458723] PDF document isn't shown - "Please wait ..." message is shown instead
https://bugs.kde.org/show_bug.cgi?id=458723 --- Comment #8 from David Hurka --- *** Bug 458802 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 440405] Add the ability to copy & paste annotations
https://bugs.kde.org/show_bug.cgi?id=440405 --- Comment #5 from David Hurka --- (In reply to Jason Liam from comment #4) > Hi, has this feature been added to okular? Maybe to a new testing branch. AFAIK not, no one is currently planning to implement this. If you want, you may try it yourself, the repository is at https://invent.kde.org/graphics/okular. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 406489] Can not save/export images in pdf file
https://bugs.kde.org/show_bug.cgi?id=406489 David Hurka changed: What|Removed |Added Summary|Can not save image in pdf |Can not save/export images |file use okular |in pdf file -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442131] [Feature request] Saveas as well as copy
https://bugs.kde.org/show_bug.cgi?id=442131 David Hurka changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from David Hurka --- If I understand you right, this is a duplicate of Bug 406489. *** This bug has been marked as a duplicate of bug 406489 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 406489] Can not save/export images in pdf file
https://bugs.kde.org/show_bug.cgi?id=406489 David Hurka changed: What|Removed |Added CC||dav1dblunk...@hotmail.com --- Comment #15 from David Hurka --- *** Bug 442131 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #14 from David Hurka --- (In reply to Oliver Sander from comment #10) > Can you reproduce the problem using one of the poppler command line tools > like pdfinfo or pdftocairo? It may be a poppler bug. `pdfinfo userunit_10.pdf` reports `Page size: 1785.6 x 1785.6 pts` (In reply to Manuel Geißer from comment #6) > List of other affected PDF software: > * Chromium integrated PDF viewer (uses PDFium) > * Firefox integrated PDF viewer (uses pdf.js) > * Inkscape PDF importer (uses Poppler) > * Scribus PDF importer > * PDFStitcher (uses pikepdf) > * PDF Arranger (uses pikepdf) > * even the proprietary Master PDF Editor 4 and 5 > > Probably more ... I think you should report at PDFium, pdf.js, Poppler, and pikepdf. Poppler is here: https://gitlab.freedesktop.org/poppler/poppler/issues It is the library used by Okular. There is also a muPDF backend for Okular. Did you try that? `mutool info userunit_10.pdf` reports `[ 0 0 17856 17856 ]`. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442381] Bookmark annotation "Insert custom name for the annotation"
https://bugs.kde.org/show_bug.cgi?id=442381 David Hurka changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from David Hurka --- > Whenever I annotate something with (e.g. highlighter), okular asks for a > custom name for this annotation. This should usually not happen. What is your “Author” name in Settings -> Configure Okular... -> Annotations? Okular should fill this in with your user name automatically. If that does not work, it might ask you directly as soon as it is needed. Can you provide a screenshot of how Okular asks for a name? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442525] New: Feedback for the new throbber in Plasma
https://bugs.kde.org/show_bug.cgi?id=442525 Bug ID: 442525 Summary: Feedback for the new throbber in Plasma Product: plasmashell Version: 5.22.90 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Theme - Breeze Assignee: visual-des...@kde.org Reporter: david.hu...@mailbox.org CC: david.hu...@mailbox.org, plasma-b...@kde.org Target Milestone: 1.0 Created attachment 141593 --> https://bugs.kde.org/attachment.cgi?id=141593&action=edit New throbber on Kate icon This is about the throbber which appears on top or next to an icon when you clicked it, and the action it performs needs some time to complete. For example, clicking an application launcher in the plasma panel, or connecting to a network in the Networks widget. The previous throbber was a circle line that faded rotationally. The new throbber is an 8-teeth gear outline, which looks like the KDE logo. But it is hard to see. It barely changes its appearance while rotating, because it repeats 8 times rotationally, and the teeth are too small. It is also slightly smaller than the previous one, so it does not rotate around most icons, but within them. Because most application icons are blue too, it is even harder to see. SOFTWARE VERSIONS KDE neon 5.22 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442525] Feedback for the new throbber in Plasma
https://bugs.kde.org/show_bug.cgi?id=442525 --- Comment #1 from David Hurka --- Created attachment 141594 --> https://bugs.kde.org/attachment.cgi?id=141594&action=edit Old throbber on Kate icon -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442503] Scroll Page Up teleports to top of previous page
https://bugs.kde.org/show_bug.cgi?id=442503 David Hurka changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from David Hurka --- Can not reproduce with Okular 21.08.1 on KDE Neon user edition. Can you provide screenshots or a screencast of the whole window, so we can try to reconstruct more precisely? Can you provide more information on your configuration? Do you have smooth scrolling enabled (if that makes a difference)? (Besides that, this is an excellent bug report. :) ) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442503] Scroll Page Up teleports to top of previous page
https://bugs.kde.org/show_bug.cgi?id=442503 David Hurka changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #10 from David Hurka --- Thanks. I think I recreated all preconditions correctly, but unfortunately still can not reproduce the issue. I don’t know what else could be relevant. If you know how to do that, you may build Okular from source and do a git bisect to find the problem. The source is located at https://invent.kde.org/graphics/okular. The README.md contains a description how to build from source. If you are interested, we can help you with that. :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442525] Feedback for the new progress spinner in Plasma
https://bugs.kde.org/show_bug.cgi?id=442525 --- Comment #4 from David Hurka --- Could the circle line of the existing spinner be modified, so it resembles a sector of the KDE gear? The mean radius and the conical fade would stay. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442503] Scroll Page Up teleports to top of previous page if in non-continuous view and trimmed view
https://bugs.kde.org/show_bug.cgi?id=442503 David Hurka changed: What|Removed |Added Summary|Scroll Page Up teleports to |Scroll Page Up teleports to |top of previous page|top of previous page if in ||non-continuous view and ||trimmed view Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #12 from David Hurka --- Wow, you are fast. Yes, this helps! I guess you have View -> Trim View -> Trim to Selection enabled, but you did not select anything, or something similar. I can reproduce the issue when I enable Trim to Selection and select some area. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442679] Sidebar Feature (instant web search)
https://bugs.kde.org/show_bug.cgi?id=442679 --- Comment #1 from David Hurka --- -1: Okular is a document viewer, not a browser, and therefore shouldn’t care about the extra complexity with an embedded browser. I also do not think that having a browser in the sidebar makes sense. Except if you want to promote your company’s own search engine. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442759] Scrolling with touchpad is not based on the action/speed of scrolling
https://bugs.kde.org/show_bug.cgi?id=442759 --- Comment #1 from David Hurka --- I agree that stepwise scrolling is not good for touchpad use. Okular usually has per-pixel scrolling, so it should follow touchpad input directly. The problem here is probably related to using Okular on Windows. I don’t know much about Windows. Anyways, did you install Okular from the Microsoft Store, or somehow else? (Probably irrelevant: does it change if you toggle the Use Smooth Scrolling option in Settings -> Configure Okular...?) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442777] Global menu change to "no text"
https://bugs.kde.org/show_bug.cgi?id=442777 David Hurka changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |DUPLICATE --- Comment #3 from David Hurka --- No, we can’t really reproduce this. Maybe it is one specific action that needs to be added to the toolbar, but we don’t know which one. But if you can figure out how to reproduce it, or gain any other information, you may add it to Bug 395497. *** This bug has been marked as a duplicate of bug 395497 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 395497] Menubar - No text - Editing the shell toolbar from Configure Toolbars sometimes corrupts shell.rc
https://bugs.kde.org/show_bug.cgi?id=395497 David Hurka changed: What|Removed |Added CC||yzsha...@126.com --- Comment #51 from David Hurka --- *** Bug 442777 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442863] Bookmark icon overlaid on top of thumbnails
https://bugs.kde.org/show_bug.cgi?id=442863 --- Comment #3 from David Hurka --- I think I have seen that before. But same here, I wasn’t aware of it. I never use bookmarks. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442863] Bookmark icon overlaid on top of thumbnails needs visual polish
https://bugs.kde.org/show_bug.cgi?id=442863 --- Comment #6 from David Hurka --- Here it appears in the top-right corner. Looks a bit like a paper clip. Maybe it is not correctly positioned on hiDPI? I think it doesn’t look very beautiful. And it is not very noticeable, when navigating through the document the thumbnails panel scrolls too fast. There is not only this emblem appearing, the whole viewport changes. I think bookmarks should be visible in the main view. Like a speech bubble outside the left or right page border. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443055] Pdf File's Size Changed to 0 Bytes After Sudden Power Outage
https://bugs.kde.org/show_bug.cgi?id=443055 --- Comment #1 from David Hurka --- > My question is that Is there a way to get back my old pdf file back > using these above xml files? No, but... > For example, i have an old pdf which is the same as the old pdf > except that this one doesn't have any annotations in it. So Will > it be possible to add these xml information into that file(that > doesn't have any annotation)? > > I am using Ubuntu 18.04 x86_64 and Okular 1.3.3 This old Okular version stored annotations in these XML files. So if you find that one of these XML files contains your annotations, you only need to get the original PDF file back. Then the annotations will either appear magically in the PDF file, or you can figure out which new XML file is created for this new PDF file, and copy the annotations from the old XML file to the new XML file. To get the annotations actually in the PDF file, you will need to install a newer version of Okular. It should offer you to migrate the annotations from the XML file to the PDF file. I am surprised that the PDF file has been lost. Your Okular version should theoretically not modify it... -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443055] Pdf File's Size Changed to 0 Bytes After Sudden Power Outage
https://bugs.kde.org/show_bug.cgi?id=443055 --- Comment #3 from David Hurka --- If you say you created at least X bytes worth of annotations, but you can’t find a docdata file which is bigger than X bytes, I am afraid, you can not recover the annotations. :( Except there is another location where Okular stored annotations in these days. It was definitifely an XML file. But as far as I remember, it was these docdata files. > > I am surprised that the PDF file has been lost. Your Okular version should > > theoretically not modify it... > > Yes if instead a temporary file were used to write and checked if the write > was successful this problem could have been avoided. Okular should theoretically open a PDF file only for reading, not for writing. So it should stay in its state on disk. But actually I remember a bug report where a PDF file has shrunken to 0 bytes after a power outage. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443055] Pdf File's Size Changed to 0 Bytes After Sudden Power Outage
https://bugs.kde.org/show_bug.cgi?id=443055 --- Comment #5 from David Hurka --- You are right, Okular 1.3.3 already saves annotations in PDF files. I thought this feature had been added in 1.4 or later, but it was actually added in 0.15. In that case you unfortunately can not recover the annotations in a usual way. You might try some data recovery tools, depending on the file system which you use. The docdata files are used to remember which page you viewed last, so when you open the document again, you see the same page. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 451149] Support opening wide images as a single page in double page mode
https://bugs.kde.org/show_bug.cgi?id=451149 --- Comment #1 from David Hurka --- So instead of “Facing pages” and “Facing pages (center first page)” you would need a “Facing pages (smart)” mode? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451425] New: KWin crashed after opening the Application Menu (menu style) from the panel
https://bugs.kde.org/show_bug.cgi?id=451425 Bug ID: 451425 Summary: KWin crashed after opening the Application Menu (menu style) from the panel Product: kwin Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: david.hu...@mailbox.org Target Milestone: --- Application: kwin_x11 (5.24.80) Qt Version: 5.15.3 Frameworks Version: 5.92.0 Operating System: Linux 5.13.0-35-generic x86_64 Windowing System: X11 Distribution: KDE neon Unstable Edition DrKonqi: 5.24.80 [CoredumpBackend] -- Information about the crash: - What I was doing when the application crashed: I just connected to the computer with x2x, while it was showing the empty desktop immediately after starting up. I hovered the Application Menu launcher with the physical mouse, then used the x2x mouse to click it. I moved the x2x mouse to select an application, and KWin instantly crashed, automatically restarted, and crashed again. The third KWin survived. I can imagine that the instant cursor jump, which occurs when switching from the physical mouse to the x2x mouse, caused this crash. For example, the x2x cursor may have hovered some part of the menu before it was sufficiently initialized. When using only one mouse, there would be sufficient delay between clicking the launcher and moving the cursor over the menu. - Custom settings of the application: The panel is moved to the top screen edge. Besides that and x2x, I don’t know of potentially relevant configuration. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KWin (kwin_x11), signal: Segmentation fault [New LWP 1919] [New LWP 1974] [New LWP 1964] [New LWP 1967] [New LWP 1975] [New LWP 1936] [New LWP 1972] [New LWP 1966] [New LWP 1965] [New LWP 1971] [New LWP 1977] [New LWP 1968] [New LWP 1962] [New LWP 1969] [New LWP 2062] [New LWP 2003] [New LWP 1973] [New LWP 1976] [New LWP 1980] [New LWP 1970] [New LWP 1978] [New LWP 1979] [New LWP 1963] [New LWP 2051] [New LWP 2008] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/bin/kwin_x11'. Program terminated with signal SIGSEGV, Segmentation fault. #0 raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 [Current thread is 1 (Thread 0x7f3934f48f40 (LWP 1919))] __preamble__ [Current thread is 1 (Thread 0x7f3934f48f40 (LWP 1919))] Thread 25 (Thread 0x7f38fd7fa700 (LWP 2008)): #0 0x7f39398a5ac6 in __ppoll (fds=fds@entry=0x7f38c0008018, nfds=nfds@entry=3, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:44 #1 0x7f393ba16619 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=3, fds=0x7f38c0008018) at kernel/qcore_unix.cpp:132 #3 qt_ppoll (timeout_ts=0x0, nfds=3, fds=0x7f38c0008018) at kernel/qcore_unix.cpp:129 #4 qt_safe_poll(pollfd*, unsigned long, timespec const*) (fds=0x7f38c0008018, nfds=3, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:155 #5 0x7f393ba17cc3 in QEventDispatcherUNIX::processEvents(QFlags) (this=, flags=...) at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:211 #6 0x7f393b9be92b in QEventLoop::exec(QFlags) (this=this@entry=0x7f38fd7f9bb0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #7 0x7f393b7d8462 in QThread::exec() (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #8 0x7f3939cd0f4b in () at /lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7f393b7d9643 in QThreadPrivate::start(void*) (arg=0x7f3939d54d80) at thread/qthread_unix.cpp:331 #10 0x7f393b6f0609 in start_thread (arg=) at pthread_create.c:477 #11 0x7f39398b2163 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 24 (Thread 0x7f38f75ef700 (LWP 2051)): #0 0x7f39398a5ac6 in __ppoll (fds=fds@entry=0x7f38b8000d78, nfds=nfds@entry=1, timeout=, timeout@entry=0x0, sigmask=sigmask@entry=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:44 #1 0x7f393ba16619 in ppoll (__ss=, __timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:77 #2 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f38b8000d78) at kernel/qcore_unix.cpp:132 #3 qt_ppoll (timeout_ts=0x0, nfds=1, fds=0x7f38b8000d78) at kernel/qcore_unix.cpp:129 #4 qt_safe_poll(pollfd*, unsigned long, timespec const*) (fds=0x7f38b8000d78, nfds=1, timeout_ts=timeout_ts@entry=0x0) at kernel/qcore_unix.cpp:155 #5 0x7f393ba17cc3 in QEventDispatcherUNIX::processEvents(QFlags) (this=, flags=...) at ../../include/QtCore/../../src/corelib/tools/qarraydata.h:211 #6 0x7f393b9be92b in QEventLoop::exec(QFlags) (this=this@entry=0x7f38f75eebc0
[okular] [Bug 444319] Sign a file with a document in a card reader
https://bugs.kde.org/show_bug.cgi?id=444319 --- Comment #5 from David Hurka --- Might it be related to the thing outlined in the Okular manual as follows? I think this is not exactly expected behavior, so you might have been fooled by it. :) --- We use the Poppler library to handle signing of PDF documents and Poppler is using the NSS library to handle certificates. At the point of writing, Poppler will try to use one of the following NSS certificate stores in order (the first that exists): * The current Firefox user certificate store. * The system-wide /etc/pki/nssdb certificate store. * The current user $HOME/.pki/nssdb If you want to use a custom certificate store you can do so by setting it in the PDF Backend Configuration section of the Configure Backends... dialog. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436774] When I want to open many files sharing the same window but different tabs, I have to drag the second/third .. files to the window of first file. If I simply open two files by cli
https://bugs.kde.org/show_bug.cgi?id=436774 David Hurka changed: What|Removed |Added Summary|Program Feature "Open new |When I want to open many |files in tabs" not working |files sharing the same ||window but different tabs, ||I have to drag the ||second/third .. files to ||the window of first file. ||If I simply open two files ||by clicking, it will open ||two windows rather than two ||tabs. Platform|Archlinux Packages |Microsoft Windows Status|CONFIRMED |REPORTED OS|Linux |Microsoft Windows Ever confirmed|1 |0 Version|21.08.2 |unspecified --- Comment #9 from David Hurka --- Thanks for your bug report! But please open a new ticket instead of modifying a different one. In this case, please also describe how you installed Okular. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 445068] Some errors were found in the document
https://bugs.kde.org/show_bug.cgi?id=445068 David Hurka changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=444297 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 444297] Okular "Could not open" a certain PDF, with no other details
https://bugs.kde.org/show_bug.cgi?id=444297 David Hurka changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=445068 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 456732] more configuration settings?
https://bugs.kde.org/show_bug.cgi?id=456732 David Hurka changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from David Hurka --- I do not understand this bug report. If you do not like “Fit Width” as default, why don’t you change the default? Menu bar -> Settings -> Configure Okular... -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 336381] Save bookmarks directly to PDF or a sibling bookmarks file
https://bugs.kde.org/show_bug.cgi?id=336381 David Hurka changed: What|Removed |Added Summary|Directly save bookmarks to |Save bookmarks directly to |PDF |PDF or a sibling bookmarks ||file -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 457115] Changes to toolbar buttons in main toolbar are only reflected for current or new tabs but not for others until restart
https://bugs.kde.org/show_bug.cgi?id=457115 --- Comment #2 from David Hurka --- > I have opened a new bug report, which describes the issue better. Aaahh, I wondered. Nice idea, but I doubt it helps, since the old report was more specific. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 457245] Tablet or touchscreen-friendly settings
https://bugs.kde.org/show_bug.cgi?id=457245 David Hurka changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #2 from David Hurka --- (In reply to Julian from comment #1) > Edit: version is 1.10.70, could not find that in the drop down menu. You are right, most versions are apparently gone. I notified the kde-devel mailing list. > 1. [...] or the document will unintentionally go flying. I think we fixed that in version 20.12. You use 1.10 (meaning 20.04), so you should try updating. 1.10 unfortunately has several issues with scrolling (which were introduced after 1.9). > 2. The pinch gesture is used in wayland to go to the overview of open > windows. That work with Okular, too, but unfortunately, it will unset your > viewing settings, in particular "Fit Width". So it would be great if there > was an option to lock "Fit Width" or any other zoom setting. That would probably require to turn off pinch gestures entirely? > 3. Wouldn't be surprised if there is nothing that can be done over this, but > I seem to be unable to change textbox sizes when I add an Inline Note. I can > only move the note around. There are no eight small squares in the outline of the box? These should be resize handles. --- I am closing this bug report, since Bugzilla is meant to have only one issue per bug report. Please open individual bug reports for each issue. :) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 457374] Hovering over truncated bookmark pops up screen with file properties.
https://bugs.kde.org/show_bug.cgi?id=457374 David Hurka changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from David Hurka --- I can not reproduce this with Okular 22.04.3 on KDE Neon. Can you describe the issue a bit more detailed? For example, these questions may be helpful: Are you talking about the sidebar tab called “Bookmarks”? Is the bookmark in the current document? Do you have “Show for all documents” enabled? Is the File Properties window about the currently opened document, or the hovered bookmark? You may also use screenshots or screencasts for clarification. Can you describe how you installed Okular, and which libraries (Qt, KDE Frameworks, okularpart) you use? And may it be possible that some unknown device or software causes stray keyboard inputs? If you use Ubuntu, you could try the command line tool “xev” to monitor any inputs for some time. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442046] copy-paste from LTR languages bring reversed text
https://bugs.kde.org/show_bug.cgi?id=442046 David Hurka changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from David Hurka --- *** This bug has been marked as a duplicate of bug 207748 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 207748] LTR languages searches text backwards
https://bugs.kde.org/show_bug.cgi?id=207748 David Hurka changed: What|Removed |Added CC||adam.golan...@gmail.com --- Comment #24 from David Hurka --- *** Bug 442046 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 457448] When copying and pasting Arabic from a PDF file, the text reverse direction
https://bugs.kde.org/show_bug.cgi?id=457448 David Hurka changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from David Hurka --- This config option can be added to the toolbar, but it does not affect text, only page layout in Facing Pages mode. *** This bug has been marked as a duplicate of bug 207748 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 207748] LTR languages searches text backwards
https://bugs.kde.org/show_bug.cgi?id=207748 David Hurka changed: What|Removed |Added CC||overman.supermundane@gmail. ||com --- Comment #25 from David Hurka --- *** Bug 457448 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 320723] No way to go back when following an embedded link in a pdf file.
https://bugs.kde.org/show_bug.cgi?id=320723 --- Comment #10 from David Hurka --- If I think a bit about it, this may be medium difficult to implement, because Okular uses KParts. If a new window/tab shall be opened, Part has to tell the shell to open an URL. The shell probably has a function that just needs to be called with a QUrl. But you need to understand how the Part tells commands to the shell. If there shall be a way to go back (with the “Back” action), the Back action has to distinguish between the viewport history (which is already there but currently buggy) and a document history, which is not yet there in the Part. The Back action belongs to the Part, while the document history (“Open Recent” menu) belongs to the shell. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 387673] menu headings corrupt, showing "no text"
https://bugs.kde.org/show_bug.cgi?id=387673 David Hurka changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=395497, ||https://bugs.kde.org/show_b ||ug.cgi?id=443316 --- Comment #10 from David Hurka --- (In reply to Shaya from comment #9) > I seemed to have reproduced this issue with Dolphin. See here: > https://bugs.kde.org/show_bug.cgi?id=443316 Thanks for the report! (In reply to Shaya from comment #9) > I did configure the toolbar, but then reverted my changes, and now the menu > options all show "no text" Does that mean you clicked the “Defaults” button before applying the changes with “Apply” or “OK”? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 395497] Menubar - No text - Editing the shell toolbar from Configure Toolbars sometimes corrupts shell.rc
https://bugs.kde.org/show_bug.cgi?id=395497 David Hurka changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=387673 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 443316] Dolphin AppMenu and Hambuger Menu display "No text" instead of menu headings
https://bugs.kde.org/show_bug.cgi?id=443316 David Hurka changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=387673 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #22 from David Hurka --- No, the muPDF backend is not part of Okular, it is an independent project. Just search for it in the internet for okular-backend-mupdf or okular-mupdf-backend. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 443401] New: 300 processes of drkonqi-coredump-processor occupying 100% of CPU, Plasma desktop unusable.
https://bugs.kde.org/show_bug.cgi?id=443401 Bug ID: 443401 Summary: 300 processes of drkonqi-coredump-processor occupying 100% of CPU, Plasma desktop unusable. Product: drkonqi Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: david.hu...@mailbox.org CC: david.hu...@mailbox.org, fa...@kde.org, kdelibs-b...@kde.org Target Milestone: --- Created attachment 142209 --> https://bugs.kde.org/attachment.cgi?id=142209&action=edit htop showing drkonqi-coredump-processor processes. SUMMARY Since the last updates today, I am not able to use my KDE Neon developer edition machine anymore, because many drkonqi-coredump-processor processes make it totally unresponsive after a few seconds. These processes appear at a rate of 1Hz. At the same time, I observe a similar amount of sddm-greeter processes appearing, each doing nothing. When I log out fast enough, I can see one additional sddm-greeter process, which is operational and does the login screen. The drkonqi-coredump-processor processes continue to run, until they disappear after 300 seconds. STEPS TO REPRODUCE 1. Log in graphically on KDE Neon developer edition, with a local X session OBSERVED RESULT Every second a process appears and runs at full CPU load: `drkonqi-coredump-processor ` EXPECTED RESULT No such processes appear. In case sddm-greeter (or something else) actually crashes and causes these processes to appear, they should not lock up at 100% CPU. SOFTWARE/OS VERSIONS $ ssh -X david@tarja kinfocenter Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.23.80 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-37-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 4800U with Radeon Graphics Memory: 30.8 GiB of RAM Graphics Processor: llvmpipe $ ssh david@tarja apt show drkonqi Version: 5.22.5+p20.04+tunstable+git20211006.0214-0 $ ssh david@tarja apt show sddm 0.19.0+p20.04+tunstable+git20211004.1953-0 -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 443401] 300 processes of drkonqi-coredump-processor occupying 100% of CPU, Plasma desktop unusable.
https://bugs.kde.org/show_bug.cgi?id=443401 --- Comment #1 from David Hurka --- Created attachment 142211 --> https://bugs.kde.org/attachment.cgi?id=142211&action=edit htop showing one of 12 drkonqi-coredump-launcher processes and 3 children. Downgrading drkonqi to 5.22.5+p20.04+tunstable+git20210917.0137-0 does not change anything. Downgrading sddm to 0.18.1-1ubuntu2 does not change anything. I can see 12 inactive processes of drkonqi-coredump-launcher starting at login and quitting at logout. I think this is not related (12 != 300), I cc-ed Frameworks anyway. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 443401] 300 processes of drkonqi-coredump-processor occupying 100% of CPU, Plasma desktop unusable.
https://bugs.kde.org/show_bug.cgi?id=443401 --- Comment #2 from David Hurka --- Created attachment 142219 --> https://bugs.kde.org/attachment.cgi?id=142219&action=edit Aptitude log of the update which led to this problem. The issue went away itself after installing more updates. I do not know which package may have caused this, neither drkonqi nor sddm were updated. In case this becomes relevant again, I am attaching my aptitude logs. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 443401] 300 processes of drkonqi-coredump-processor occupying 100% of CPU, Plasma desktop unusable.
https://bugs.kde.org/show_bug.cgi?id=443401 --- Comment #3 from David Hurka --- Created attachment 142220 --> https://bugs.kde.org/attachment.cgi?id=142220&action=edit Aptitude log of the actions which did not change this problem. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 443401] 300 processes of drkonqi-coredump-processor occupying 100% of CPU, Plasma desktop unusable.
https://bugs.kde.org/show_bug.cgi?id=443401 --- Comment #4 from David Hurka --- Created attachment 142221 --> https://bugs.kde.org/attachment.cgi?id=142221&action=edit Aptitude log of the update which made this problem disappear. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 443401] 300 processes of drkonqi-coredump-processor occupying 100% of CPU, Plasma desktop unusable.
https://bugs.kde.org/show_bug.cgi?id=443401 David Hurka changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443388] Double click on the tool on the annotation toolbar don't stay enabled
https://bugs.kde.org/show_bug.cgi?id=443388 David Hurka changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from David Hurka --- I assume you mean the annotation toolbar like the one visible here: https://invent.kde.org/websites/okular-kde-org/-/raw/fd23b5175e04452ebe9daf29711833465c075f52/static/images/screenies/okular-annotations-main.png Since Okular 20.08 the old annotation toolbar (https://invent.kde.org/websites/okular-kde-org/-/raw/e8194614e0d08099236a0a760a6aebfc05da2226/images/screenies/okular-annotations.png, the vertical bar with 8 buttons) was replaced by the new toolbar. The new toolbar is a “native” toolbar with QActions, which do not have support for double-click. Therefore, there is now a button that looks like a pin needle for this feature. (In the first image the right-most button.) --- Anyway, if you think the double-click behavior is missing now, we will be happy about your feedback. :) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443390] Feature Request: Command Line option to get the last page of reading when exit.
https://bugs.kde.org/show_bug.cgi?id=443390 --- Comment #2 from David Hurka --- (In reply to shenlebantongying from comment #0) > Okular can remember the lasted opened position (i think?), Yes, not only the last position. Okular stores the viewport history in XML files, usually under ~/.local/share/okular/docdata/. It should be possible to parse these, although not very convenient. > Scripting a GUI application! > > I might be the only want this :/ No, this is one use case for D-Bus. You can try the application d-feet to look which D-Bus methods are available in Okular. For example, you can query the currentPage() method. Of course, you need to query it before Okular is closed. > Does Okualr can be used as a KPart? Yes, the okularpart component, which is used by the “Okular” desktop application, is actually a KPart in a shared library. It provides the same currentPage() method. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443404] Mousewheel scroll does not work in full page size and non-continous mode for some mouses
https://bugs.kde.org/show_bug.cgi?id=443404 --- Comment #2 from David Hurka --- Here, scroll wheel always changed the page in non-continuous mode. If the end of the page is nearer than one scroll step, it scrolls only to the end, and the next scroll step goes to the next page. The problem is with continuous (stepless, non-discrete) scrolling. Scrolling on one page works as expected (per-pixel scrolling), and scrolling from the end of one page to the next page requires at least 15° in one wheel event, which is awkward with continuous scrolling devices. @Rafa: Are the mentioned mice such continuously scrolling ones? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443404] Mousewheel scroll does not work in full page size and non-continous mode for some mouses
https://bugs.kde.org/show_bug.cgi?id=443404 --- Comment #4 from David Hurka --- As I understand these mice, you can add/remove some part or flip a lever that makes the mouse wheel physically spin continuously or in steps. If you change only the mouse wheel to spin in steps, that is maybe not be enough, because the mouse could still sends events for every sub-step. To check if there is confusion in this area, you can try to use the up/down arrow keys. These are handled the same way as purely discrete mouse wheel events. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 443642] New: Selection clipboard no longer works with Shift + click
https://bugs.kde.org/show_bug.cgi?id=443642 Bug ID: 443642 Summary: Selection clipboard no longer works with Shift + click Product: frameworks-ktexteditor Version: 5.86.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: david.hu...@mailbox.org Target Milestone: --- SUMMARY Since today, selecting text with the Shift key no longer populates the selection clipboard, which forces me to use the clipboard with Ctrl+C and Ctrl+V. Since Ctrl+C does not affect the selection clipboard, this makes it difficult to conveniently copy a section of text to multiple locations. STEPS TO REPRODUCE 1. Open Kate or KDevelop with some long text. 2. Click a point in the text. 3. Clear Klipper. 4. Hold Shift and click another point in the text. OBSERVED RESULT Nothing is copied to any clipboard. Text is just selected. EXPECTED RESULT Selected text is copied to selection clipboard. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-37-generic (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION The click, Shift+click workflow still works in any other application, and many other ways to populate the selection keyboard in KTextEditor still work. This includes: * Select with click-drag-release * Select with click, Shift + navigation keys * Select with double-click or triple-click * Select with double- or triple-click-drag-release But it doesn’t work with: (I can not confirm that these worked before) * Select with Ctrl+A -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 365890] When using Shift+Home/End as shortcut using the neo layout, the Shift+U / Shift+O keys do not enter large U/O anymore.
https://bugs.kde.org/show_bug.cgi?id=365890 David Hurka changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #3 from David Hurka --- Confirmed here. I use Neo2 exclusively. Besides that, these global shortcuts do not even work themselves. Operating System: KDE neon 5.22 User edition KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-37-generic (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427913] Resizing the sidebar causes disk write to go up
https://bugs.kde.org/show_bug.cgi?id=427913 David Hurka changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=441676, ||https://bugs.kde.org/show_b ||ug.cgi?id=389411, ||https://bugs.kde.org/show_b ||ug.cgi?id=430190 --- Comment #2 from David Hurka --- I think this may be the cause for some other bug reports. Adding them to See Also. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 441676] Resizing the left panel is jerky
https://bugs.kde.org/show_bug.cgi?id=441676 David Hurka changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=427913 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 389411] Okular and X unresponsive when resizing Okular's sidebar
https://bugs.kde.org/show_bug.cgi?id=389411 David Hurka changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=427913 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 430190] Crash when moving sidebar on Wayland
https://bugs.kde.org/show_bug.cgi?id=430190 David Hurka changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=427913 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443707] Okular crashes while searching
https://bugs.kde.org/show_bug.cgi?id=443707 --- Comment #3 from David Hurka --- > Just before the crash it became impossible to resize index pane to make the > section entries larger. I am doing some guess. Are your observations like this? 1. Search for “cable” 2. Okular is busy with searching and becomes unresponsive 3. While Okular is busy, you try to resize the side panel 4. Resizing the side panel does not work (“unresponsive”) 5. Shortly after, Okular crashes -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443928] Manga mode
https://bugs.kde.org/show_bug.cgi?id=443928 David Hurka changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from David Hurka --- What exactly do you mean? Is your document ordered like 8-7-6-5-4-3-2-1 and you would like to fix it through a setting in Okular? Or is there a feature in the cbz format for this and Okular does not seem to support it? Or is your document ordered 1-2-3-4-5-6-7-8, but left pages are displayed on the right in Okular? In this case, you can select “Right to left reading direction” in the configuration. This option is also accessible from Settings -> Configure Toolbars... and Configure Shortcuts... :) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443707] Okular crashes while searching
https://bugs.kde.org/show_bug.cgi?id=443707 --- Comment #5 from David Hurka --- Sorry, I do not have anything. I just provided an example, so Jonathan can say “yes, that’s what happens” or “no, it’s more like ...” :) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443819] Ctrl+Scroll to zoom is incompatible with inertia touchpads
https://bugs.kde.org/show_bug.cgi?id=443819 --- Comment #3 from David Hurka --- > Ctrl+Scroll to zoom is incompatible with inertia touchpads As I understood it, this is the main reason why inertia is nowadays no longer done in the touchpad driver. So: 3) Disable inertia in your touchpad driver. Qt (the GUI framework used by Okular) provides a concept to communicate when the finger is lifted from the touchpad while scrolling. But to my knowledge, touchpad drivers do not communicate this. Implementing suggestion 1 in Okular would probably be unreliable. Suggestion 2 seems most realistic, but I think we are concerned about bloating the configuration dialog. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444015] plasmashell crashes at showing window thumbnails
https://bugs.kde.org/show_bug.cgi?id=444015 David Hurka changed: What|Removed |Added CC||david.hu...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444015] plasmashell crashes at showing window thumbnails
https://bugs.kde.org/show_bug.cgi?id=444015 --- Comment #6 from David Hurka --- Created attachment 142630 --> https://bugs.kde.org/attachment.cgi?id=142630&action=edit New crash information added by DrKonqi plasmashell (5.23.80) using Qt 5.15.3 - What I was doing when the application crashed: Move mouse cursor on the task manager. - Custom settings of the application: I have the panel on the top, otherwise it is as usual. When the crash first appeared, I had two windows with the same title (one with <2> appended), and a fullscreen window. This crash appeared immediately after installing updates and logging in again. The Alt+Tab task switcher (which also uses thumbnail images) works correctly. -- Backtrace (Reduced): #3 0x7fa598fd17c4 in Plasma::WindowThumbnail::updatePaintNode(QSGNode*, QQuickItem::UpdatePaintNodeData*) (this=0x55ba251e92c0, oldNode=, updatePaintNodeData=) at ./src/declarativeimports/core/windowthumbnail.cpp:327 #4 0x7fa606c82380 in QQuickWindowPrivate::updateDirtyNode(QQuickItem*) (this=0x55ba23b02970, item=0x55ba251e92c0) at items/qquickwindow.cpp:3872 #5 0x7fa606c82c3b in QQuickWindowPrivate::updateDirtyNodes() (this=this@entry=0x55ba23b02970) at items/qquickwindow.cpp:3617 #6 0x7fa606c84330 in QQuickWindowPrivate::syncSceneGraph() (this=this@entry=0x55ba23b02970) at items/qquickwindow.cpp:524 #7 0x7fa606c21e97 in QSGRenderThread::sync(bool, bool) (this=this@entry=0x55ba24985240, inExpose=inExpose@entry=false, inGrab=inGrab@entry=false) at scenegraph/qsgthreadedrenderloop.cpp:647 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443819] Ctrl+Scroll to zoom is incompatible with inertia touchpads
https://bugs.kde.org/show_bug.cgi?id=443819 --- Comment #5 from David Hurka --- I understood your bug report in the way that your touchpad driver implements inertia. Okular does not have inertia for scroll input, because of the problem I have outlined. It only has inertia for swipe (flick) gesture input. If you observe inertia after scrolling with the touchpad, that is because your touchpad driver implements it. Okular just does what your hardware tells it to do. --- In case you can compile Okular from source, you can search for Qt::ControlModifier in PageView::wheelEvent(). It’s located in part/pageview.cpp around line 3200, and the source code is available at https://invent.kde.org/graphics/okular. If you remove the if branch with this Qt::ControlModifier, your Okular will not zoom with Ctrl+scroll. :) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 444085] Menus show up in wrong place.
https://bugs.kde.org/show_bug.cgi?id=444085 David Hurka changed: What|Removed |Added CC||david.hu...@mailbox.org Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from David Hurka --- I doubt that this is a problem with Okular, its more likely related to KXmlGui. Do you have other Qt or KDE applications with menu bars where the same problem occurs? Can you describe your screen arrangement precisely? Maybe with screenshots from configuration tools? Do you use X or Wayland? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 353330] pressing Ctrl (while document is sliding because of scrolling) lets the document zoom instead of further sliding.
https://bugs.kde.org/show_bug.cgi?id=353330 David Hurka changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from David Hurka --- *** This bug has been marked as a duplicate of bug 443819 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443819] Ctrl+Scroll to zoom is incompatible with inertia touchpads
https://bugs.kde.org/show_bug.cgi?id=443819 David Hurka changed: What|Removed |Added CC||sp...@web.de --- Comment #8 from David Hurka --- *** Bug 353330 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
