[digikam] [Bug 378587] Geolocation hangs when opened twice
https://bugs.kde.org/show_bug.cgi?id=378587 Sander changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Version Fixed In||5.7.0 Resolution|WAITINGFORINFO |FIXED --- Comment #14 from Sander --- Reply to latest comment: Can't reproduce the problem with AppImage 5.8.0. AppImage 5.7.0 also works. Seems more like a local problem? Haven't tried AppImage 5.5.0 though. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 346335] System Settings crash while editting Global Keyboard Shortcuts
https://bugs.kde.org/show_bug.cgi?id=346335 Sander changed: What|Removed |Added CC||san...@dmafsu.nl -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 346335] System Settings crash while editting Global Keyboard Shortcuts
https://bugs.kde.org/show_bug.cgi?id=346335 --- Comment #6 from Sander --- Created attachment 108006 --> https://bugs.kde.org/attachment.cgi?id=108006&action=edit New crash information added by DrKonqi kcmshell5 (5.10.5) using Qt 5.9.1 - What I was doing when the application crashed: I opened up Global Shortcuts by searching this through the start menu. Following that I clicked on the component System Settings Module and here I selected Log out, clicked on None and entered the key combination Meta+L after which the crash occured. - Custom settings of the application: Log Out was already set to Custom without a key combination (None). I think I crashed before but cannot seem to reproduce it after crashing. - Extra info: After the crash the new key combination seemed to have been set up. The key combination was set in the System Settings Module. -- Backtrace (Reduced): #6 0x7fb88ad2e0b0 in QLabel::text() const () from /usr/lib64/libQt5Widgets.so.5 #7 0x7fb8893552d6 in ShortcutEditWidget::setKeySequence (this=0x55732d913eb0, activeSeq=...) at /usr/src/debug/kxmlgui-5.37.0/src/kshortcuteditwidget.cpp:192 [...] #9 0x7fb8841ad544 in KGlobalAccel::globalShortcutChanged (this=this@entry=0x7fb8843c7590 <(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>, _t1=, _t1@entry=0x55732d7a7a50, _t2=...) at /usr/src/debug/kglobalaccel-5.37.0/build/src/KF5GlobalAccel_autogen/include/moc_kglobalaccel.cpp:162 #10 0x7fb8841affa7 in KGlobalAccelPrivate::_k_shortcutGotChanged (this=, actionId=..., keys=...) at /usr/src/debug/kglobalaccel-5.37.0/src/kglobalaccel.cpp:480 [...] #12 0x7fb8841bb4ce in OrgKdeKGlobalAccelInterface::yourShortcutGotChanged (_t2=..., _t1=..., this=) at /usr/src/debug/kglobalaccel-5.37.0/build/src/kglobalaccel_interface.moc:267 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 378587] New: Geolocation hangs when opened twice
https://bugs.kde.org/show_bug.cgi?id=378587 Bug ID: 378587 Summary: Geolocation hangs when opened twice Product: digikam Version: 5.5.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Geolocation-Editor Assignee: digikam-de...@kde.org Reporter: b...@sanderdekievit.nl Target Milestone: --- Steps to reproduce: 1. Open Geolocation. Geotag (drag 'n drop) one image on the map. 2. Click Apply and close geolocation screen 3. Open Geolocation again. 4. Drag a picture to the map -> mouse cursor changes to 'forbidden to change' and digikam becomes unresponsive -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 378587] Geolocation hangs when opened twice
https://bugs.kde.org/show_bug.cgi?id=378587 Sander changed: What|Removed |Added CC||b...@sanderdekievit.nl -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 370217] [frameworks] Line width of freehand annotation is resolution dependent
https://bugs.kde.org/show_bug.cgi?id=370217 --- Comment #5 from Oliver Sander --- No, as I learned eventually this happens on master, too. Actually, on master it is worse, because there, the line-while-you-draw always has width 1, irrespective of what the line width settings say. Presumably that's because in annotationtools.cpp:153 it simply says const SmoothPath path( points, QPen(m_engineColor, 1) ); (the '1' is the width). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 372457] Bookmarks loosing in big documents.
https://bugs.kde.org/show_bug.cgi?id=372457 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- What do you mean by 'lose bookmarks'? Do you mean that the document contains certain bookmarks which are not shown by okular, but shown by other viewers? -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 351443] kate ask about file reload (changed outside) when exiting
https://bugs.kde.org/show_bug.cgi?id=351443 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 300992] Searching for a phrase does not find occurences split by a line break / newline in Pdf
https://bugs.kde.org/show_bug.cgi?id=300992 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #19 from Oliver Sander --- Could you please upload your patch to https://git.reviewboard.kde.org/ ? That will make reviewing it much easier. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 449808] butt caps shown as rounded
https://bugs.kde.org/show_bug.cgi?id=449808 Oliver Sander changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM CC||oliver.san...@tu-dresden.de --- Comment #3 from Oliver Sander --- This appear to be a bug in poppler, the library used by Okular to render pdf files. I can reproduce the problem with pdftoppm 20.09.0. Can you please open a bug at the poppler bugtracker: https://gitlab.freedesktop.org/poppler/poppler/-/issues Thank you! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 450887] Change font for plain text files
https://bugs.kde.org/show_bug.cgi?id=450887 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- You can do that. It's under "preferences -> set up display modules -> text" (or something like that, I'm translating from my German UI). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 455115] Show pop-up notes text more directly
https://bugs.kde.org/show_bug.cgi?id=455115 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #6 from Oliver Sander --- >From reading the description of your workflow it seems that your last suggestion (having the annotation texts visible/accessible from the review pane, in the side bar) seems most helpful. In an ideal world you would even be able to navigate there with the keyboard alone, for increased speed. Would you be able to code such a feature? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411877] Touchscreen input locked to first screen
https://bugs.kde.org/show_bug.cgi?id=411877 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #11 from Oliver Sander --- FWIW, I have a very similar issue with a SMART Podium 500 device, which is an external screen with a stylus. I can also get it recognized as an absolute pointer device, but then KWin maps the pointer movement to the entire virtual desktop (which comprises the external screen on the left, and my built-in laptop screen on the right). This happens with Plasma 5.24.4 running wayland. The libinput people have been very helpful debugging this. There is lots of technical information at https://gitlab.freedesktop.org/libinput/libinput/-/issues/769 Do you think this is the same issue, or should I open a separate report? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455309] New: Wayland: Allow to set InputMode of input device
https://bugs.kde.org/show_bug.cgi?id=455309 Bug ID: 455309 Summary: Wayland: Allow to set InputMode of input device Product: systemsettings Version: 5.24.90 Platform: Debian testing OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: oliver.san...@tu-dresden.de Target Milestone: --- I have a SMART Podium 500, which is a large screen with a stylus: https://support.smarttech.com/docs/hardware/podiums/podium-sp500/en/home.cshtml This device does not work properly out-of-the-box under Wayland: stylus movement is mapped to the entire virtual desktop (which I reported at https://bugs.kde.org/show_bug.cgi?id=411877), and no cursor appears. The friendly folks at libinput have been very helpful at debugging this, and there is lots of technical information at https://gitlab.freedesktop.org/libinput/libinput/-/issues/769 As it turns out, the device has an InputMode setting with integer arguments 0,1,2,3, and right now it doesn't seem like the default value is the best choice. I can set the mode using the `hid-feature` command-line tool, but a GUI somewhere in the system settings would be much more convenient. Of course in an ideal world the correct setting would be somehow detected and selected automatically, but my technical understanding is not sufficient to say whether this is something that I can hope for. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.94.0 Qt Version: 5.15.2 Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455462] New: Wayland: Wrong keyboard layout for non-KDE programs at login
https://bugs.kde.org/show_bug.cgi?id=455462
Bug ID: 455462
Summary: Wayland: Wrong keyboard layout for non-KDE programs at
login
Product: kwin
Version: 5.24.5
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: oliver.san...@tu-dresden.de
Target Milestone: ---
Created attachment 149841
--> https://bugs.kde.org/attachment.cgi?id=149841&action=edit
Screenshot of the relevant part of the 'settings' dialog.
My laptop computer has a German keyboard. When I log into a Wayland session,
however, the layout is English for all (many?) non-KDE programs. This includes
in particular Thunderbird, Firefox, and the 'Element' Matrix chat client.
I can get a German layout with the following steps:
1. Open the 'keyboard' part of the system settings program
2. Switch to the second tab ('Belegungen' / Layout(?))
3. Tick the checkbox 'setup layouts' (my translation. In German: 'Belegungen
einrichten').
4. Press apply.
Curiously, it doesn't seem to matter whether the checkbox is ticked or
unticked, as long as I can press 'apply' once.
I'll upload a screenshot of the settings dialong, because I am not sure about
the English names.
https://bugs.kde.org/show_bug.cgi?id=412101 seems closely related, but it is
marked as 'fixed'.
SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux
KDE Plasma Version: 5.24.5
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.4
Kernel Version: 5.18.0-1-amd64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 459174] okular crashes after signature checking
https://bugs.kde.org/show_bug.cgi?id=459174 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #8 from Oliver Sander --- Without having tried this myself: There has been a great number of bug reports similar to this one, and they have all been solved by updating to newer versions. Please try to get the latest flatpack version of Okular or build it from source and report back if the bug is still there. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 467328] Okular mismanages fonts embedded in PDF document when printing
https://bugs.kde.org/show_bug.cgi?id=467328 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #4 from Oliver Sander --- Printing in Okular is a bit special. I conjecture that you can print your document if you select the 'force rasterization' option in the print dialog. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 467328] Okular mismanages fonts embedded in PDF document when printing
https://bugs.kde.org/show_bug.cgi?id=467328 --- Comment #6 from Oliver Sander --- I fully agree that `force rasterization` is only a workaround. Okular currently converts pdf files to postscript and sends that to the printer (I forgot why exactly). Presumably it is the conversion step that goes wrong in your case. If you want to have a look at the code: That's at `generator_pdf.cpp:1366`. There used to be a patch that made Okular send the pdf file straight to the printer, but I can't seem to find it right now. And then there's the official Qt way of printing: Render everything to a `QPrinter` object. Code for that is at https://invent.kde.org/graphics/okular/-/merge_requests/411 , but that has its own set of problems. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 467328] Okular mismanages fonts embedded in PDF document when printing
https://bugs.kde.org/show_bug.cgi?id=467328 --- Comment #13 from Oliver Sander --- 1) Yes, poppler is used 2) On Windows, rasterization resolution follows the printer. Elsewhere, 300dpi is hardcoded. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 468017] Percentage value not localised
https://bugs.kde.org/show_bug.cgi?id=468017 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- Is this fixed by your patch https://invent.kde.org/graphics/okular/-/merge_requests/675 ? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 468112] Use Cairo backend for Poppler wrapper used in Okular
https://bugs.kde.org/show_bug.cgi?id=468112 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #2 from Oliver Sander --- See https://gitlab.freedesktop.org/poppler/poppler/-/merge_requests/546 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 468819] The application's title bar is set to the title in the PDF doc, instead of the filename
https://bugs.kde.org/show_bug.cgi?id=468819 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #3 from Oliver Sander --- The sixth option in settings --> okular settings --> general (actual names may differ, my Okular UI is not English) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 470108] Touchscreen zoom not working as expected
https://bugs.kde.org/show_bug.cgi?id=470108 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- See https://invent.kde.org/graphics/okular/-/merge_requests/134 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 126942] Kghostview can't show any overprint preview
https://bugs.kde.org/show_bug.cgi?id=126942 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #3 from Oliver Sander --- Can you please attach an example file? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 470734] Printing is extremely slow (Win10)
https://bugs.kde.org/show_bug.cgi?id=470734 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #2 from Oliver Sander --- > Assumption: Okular sends (large) rendered bitmaps to the printer (sub system > of Windows) where Acrobat Reader sends (small) texts. That's essentially correct. The code is in the method PDFGenerator::print in the file generator_pdf.cpp. Improving the situation is not particularly difficult, but it needs somebody with both the time to do it and a Windows machine. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 469044] Crash when closing an PDF file with digital sign
https://bugs.kde.org/show_bug.cgi?id=469044 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- Can you try this with a very new poppler and Okular? The signature code is being worked on and your problem may have been fixed already. Also, does this happen with every document with a signature? Can you share such a document? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 461371] PDFs digitally signed with Okular become locked in Adobe Acrobat so no one else can sign it
https://bugs.kde.org/show_bug.cgi?id=461371 --- Comment #5 from Oliver Sander --- I asked the colleague I mentioned above to test this, and it seems that the issue is indeed fixed for us as well. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 465055] All PDFs are shown stretched in y-axis
https://bugs.kde.org/show_bug.cgi?id=465055 --- Comment #21 from Oliver Sander --- Did you get Okular to build and link on your computer in the meantime? My apologies, but I am not the one who can help with linker problems. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411877] Touchscreen input locked to first screen
https://bugs.kde.org/show_bug.cgi?id=411877 --- Comment #18 from Oliver Sander --- (In reply to Oliver Sander from comment #14) > I just checked again. The input really is split across the two screens. I checked again yesterday, with an updated stack from Debian testing. This time, the input was *not* split across the two screens. Rather, the input is now exclusively on the wrong screen, as for everybody else in this thread. [shrugs] Operating System: Debian GNU/Linux KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.4 Kernel Version: 5.19.0-2-amd64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 460681] Laggy scrolling on high DPI display - profiling indicates excessive copying in PagePainter::paintCroppedPageOnPainter
https://bugs.kde.org/show_bug.cgi?id=460681 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- Some of the calls to `setDevicePixelRatio` where probably introduced by me. The deep-copying was not intentional. I am not very proficient in Qt programming, and I wasn't even aware that these calls trigger a deep copy. Does https://invent.kde.org/graphics/okular/-/merge_requests/612 fix your issue by any chance? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 464716] Very slow render time on restaurant menu
https://bugs.kde.org/show_bug.cgi?id=464716 Oliver Sander changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- I can confirm the multi-second pauses, even with the recent efficiency improvements in PagePainter. The document is indeed a single page, with custom size 452 x 2529 m. It contains a single image with 2312 x 12943 pixels. Okular apparently renders only the visible parts, and that seems to take a while. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 465055] All PDFs are shown stretched in y-axis
https://bugs.kde.org/show_bug.cgi?id=465055 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #6 from Oliver Sander --- Well, even if it is, it must be something subtle, because most people see a rendering of the circle in just the way it should be. Albert and me, for example. Is your setup a laptop with a built-in screen? Can you reproduce the problem if you use another screen? Another computer? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 465055] All PDFs are shown stretched in y-axis
https://bugs.kde.org/show_bug.cgi?id=465055 --- Comment #8 from Oliver Sander --- What happens when you swap the monitors? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 465055] All PDFs are shown stretched in y-axis
https://bugs.kde.org/show_bug.cgi?id=465055 --- Comment #13 from Oliver Sander --- Relax. This is just very difficult to debug without being able to reproduce it locally. Access to dpi information is gathered in the method `realDpi` in the file `utils.cpp`. Are you able to build your own Okular (it is not very difficult)? If so, this is the place to start looking. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 465055] All PDFs are shown stretched in y-axis
https://bugs.kde.org/show_bug.cgi?id=465055 --- Comment #15 from Oliver Sander --- Building Okular is described at https://okular.kde.org/build-it/ > But I guess, when I compile my own okular, it will display a circle - > murphy's law :-) That's possible. But then you will have free time to fix some other Okular bug if you are interested. There are lot's. :-) BTW, have you checked whether your issue persists if you change from X11 to Wayland or vice versa? I don't think hidden config files have anything to do with this, but I may be wrong. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 482363] Checkboxes on forms do not show as checked even though they are checked
https://bugs.kde.org/show_bug.cgi?id=482363 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #6 from Oliver Sander --- You can find the word processor that generated your particular document by looking at "File -> Properties". -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 482363] Checkboxes on forms do not show as checked even though they are checked
https://bugs.kde.org/show_bug.cgi?id=482363 --- Comment #8 from Oliver Sander --- Do you have access to Adobe professional? Then you could try to strip the problematic of all the confidential parts. Really, the/a file is needed to fix this. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 482363] Checkboxes on forms do not show as checked even though they are checked
https://bugs.kde.org/show_bug.cgi?id=482363 --- Comment #11 from Oliver Sander --- Is this maybe a font issue? Because I do see the checkmark in the box even with disabled 'forms' mode. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 486681] Display comments created by latex pdfcomment
https://bugs.kde.org/show_bug.cgi?id=486681 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- Please provide a simple test file. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 486681] Display comments created by latex pdfcomment
https://bugs.kde.org/show_bug.cgi?id=486681 --- Comment #3 from Oliver Sander --- Thank you! Please also attach the LaTeX source file. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 446549] Digital signature feature confusing for new users
https://bugs.kde.org/show_bug.cgi?id=446549 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #2 from Oliver Sander --- Albert, by and large I agree with you. However, I think Nicolai's suggestion to grey out the 'digitally sign' menu entry when there are no certificates is worth considering. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 446549] Digital signature feature confusing for new users
https://bugs.kde.org/show_bug.cgi?id=446549 --- Comment #5 from Oliver Sander --- I understand your point, but please no additional dialog box. It would mean an additional click for everyone. How about: * An additional menu entry like "graphically sign" right next to "digitally sign" * An explanatory dialog popping up when people click on "digitally sign" without having certificates installed -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 449717] When zooming with 2 fingers on a touchscreen, Okular also scrolls through the document, causing me to lose my place.
https://bugs.kde.org/show_bug.cgi?id=449717 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #4 from Oliver Sander --- I reckon this is fixed by https://invent.kde.org/graphics/okular/-/merge_requests/134 Somebody would need to finish that. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 451823] System settings crashes in icon view, but not in sidebar view
https://bugs.kde.org/show_bug.cgi?id=451823 Sander Lindeman changed: What|Removed |Added Resolution|BACKTRACE |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Sander Lindeman --- Here's the crash report I get: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #4 0x7f2773a66bed in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #5 0x7f2773a695d6 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #6 0x7f2773a6c7c1 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7f2773a1ea2b in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7f2772e1216a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f2773a1ddc7 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7f2773a739b0 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f2773a76c45 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7f2773a176b3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f2772e1216a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7f2773310257 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #15 0x7f27732e59bc in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #16 0x7f277063a5b4 in ?? () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #17 0x7f2770a428bb in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7f2770a95f08 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7f2770a40003 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7f2772e6b548 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f2772e10a9b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f2772e19024 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x55a7a6fdb1bf in ?? () #24 0x7f277273ffd0 in __libc_start_call_main (main=main@entry=0x55a7a6fda6b0, argc=argc@entry=1, argv=argv@entry=0x7ffc572c54d8) at ../sysdeps/nptl/libc_start_call_main.h:58 #25 0x7f277274007d in __libc_start_main_impl (main=0x55a7a6fda6b0, argc=1, argv=0x7ffc572c54d8, init=, fini=, rtld_fini=, stack_end=0x7ffc572c54c8) at ../csu/libc-start.c:409 #26 0x55a7a6fdbaf5 in ?? () [Inferior 1 (process 78103) detached] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455462] Wayland: Wrong keyboard layout for non-KDE programs at login
https://bugs.kde.org/show_bug.cgi?id=455462 --- Comment #2 from Oliver Sander --- Does xwininfo needs some special options to display? I don't see anything related to window managers in its output (see below). In any case, as far as I know these windows are XWayland. ~> xwininfo xwininfo: Please select the window about which you would like information by clicking the mouse in that window. xwininfo: Window id: 0x180006a "Inbox - oliver.san...@tu-dresden.de - Mozilla Thunderbird" Absolute upper-left X: 1191 Absolute upper-left Y: 41 Relative upper-left X: 0 Relative upper-left Y: 0 Width: 1978 Height: Depth: 32 Visual: 0x351 Visual Class: TrueColor Border width: 0 Class: InputOutput Colormap: 0x1800010 (not installed) Bit Gravity State: NorthWestGravity Window Gravity State: NorthWestGravity Backing Store State: NotUseful Save Under State: no Map State: IsViewable Override Redirect State: no Corners: +1191+41 --1121+41 --1121-0 +1191-0 -geometry 1978x+1191+0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455462] Wayland: Wrong keyboard layout for non-KDE programs at login
https://bugs.kde.org/show_bug.cgi?id=455462 --- Comment #4 from Oliver Sander --- When running firefox and thunderbird with MOZ_ENABLE_WAYLAND=1 I indeed do not have the problem. However, neither program then respects the KDE screen scaling setting, and they become very strenous to use on my hidpi screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411877] Touchscreen input locked to first screen
https://bugs.kde.org/show_bug.cgi?id=411877 --- Comment #14 from Oliver Sander --- I just checked again. The input really is split across the two screens. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455309] Wayland: Allow to set InputMode of input device
https://bugs.kde.org/show_bug.cgi?id=455309 --- Comment #2 from Oliver Sander --- Fair enough. But not all people that teach in this lecture room can be asked to apply a CLI trick. However, saying "go to the 'settings' page and select mode '0'" would be acceptable. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455462] Wayland: Wrong keyboard layout for non-KDE programs at login
https://bugs.kde.org/show_bug.cgi?id=455462 Oliver Sander changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 458722] Bad rendering of data matrix code in Okular (blurry in some conditions)
https://bugs.kde.org/show_bug.cgi?id=458722 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #5 from Oliver Sander --- xpdf does not use poppler. Instead, poppler is a (partial) fork of xpdf. The two codes are similar but not identical. To convince yourself that poppler is the culprit try to render the file with `pdftoppm`. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 458723] PDF document isn't shown - "Please wait ..." message is shown instead
https://bugs.kde.org/show_bug.cgi?id=458723 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #7 from Oliver Sander --- I haven't checked this particular case, but documents that show this warning message typically contain XFA forms. These forms are described in a document several hundred pages long, and nobody has ever had the nerve to start an open implementation. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #10 from Oliver Sander --- Can you reproduce the problem using one of the poppler command line tools like pdfinfo or pdftocairo? It may be a poppler bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438198] In wayland moving a window to another desktop becomes a needlessly complicated task
https://bugs.kde.org/show_bug.cgi?id=438198 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 383651] Custom/image stamp annotations are not saved into the PDF file in a way that can be printed or that other readers can see
https://bugs.kde.org/show_bug.cgi?id=383651 --- Comment #33 from Oliver Sander --- If all you need is printing, then enabling 'force rasterization' in the print dialog will probably circumvent the problem for you. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451067] Mouse reversed scrolling is wrong after system wakes up
https://bugs.kde.org/show_bug.cgi?id=451067 sander.linde...@gmail.com changed: What|Removed |Added CC||sander.linde...@gmail.com --- Comment #3 from sander.linde...@gmail.com --- I'm having the same issue on X11. I've tried using Wayland but I could not reproduce the issue there. It does not seem to be suspend-related. If I turn off and on the bluetooth on my mouse, I get the same result: scroll direction is reverted back. Also when I switch my mouse from bluetooth to usb-dongle the same happens. Operating System: Kubuntu 21.10 KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.2 Kernel Version: 5.17.0-rc8 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451067] Mouse reversed scrolling is wrong after disconnecting and reconnecting the mouse
https://bugs.kde.org/show_bug.cgi?id=451067 --- Comment #5 from Sander Lindeman --- A bug report about this has made it to the 15-minute bug initiative: https://bugs.kde.org/show_bug.cgi?id=435113 So hopefully this will be addressed soon! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451067] Mouse reversed scrolling is wrong after disconnecting and reconnecting the mouse
https://bugs.kde.org/show_bug.cgi?id=451067 Sander Lindeman changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #6 from Sander Lindeman --- *** This bug has been marked as a duplicate of bug 435113 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435113] certain mouse settings resets after restart/resume from suspend/dock/undock
https://bugs.kde.org/show_bug.cgi?id=435113 Sander Lindeman changed: What|Removed |Added CC||kdeaa...@iforgotmy.name --- Comment #44 from Sander Lindeman --- *** Bug 451067 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 451823] New: System settings crashes in icon view, but not in sidebar view
https://bugs.kde.org/show_bug.cgi?id=451823 Bug ID: 451823 Summary: System settings crashes in icon view, but not in sidebar view Product: systemsettings Version: 5.24.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: sander.linde...@gmail.com Target Milestone: --- SUMMARY *** When system settings is open and in icon view, selecting any setting results in an immediate a crash. When in sidebar view, it works as expected. *** STEPS TO REPRODUCE 1. Open system settings in icon view 2. Select any setting (e.g. Appearance, Users, Connections, etc) OBSERVED RESULT System settings crashes immediately EXPECTED RESULT System settings opens the selected sub-menu SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.10 KDE Plasma Version: 5.24.3 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.2 Kernel Version: 5.17.0 (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION The system settings window opens normally, both in icon view and in sidebar view. When open in icon view, sidebar view can be selected without problem, and system settings works as expected. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456703] New: Mouse settings revert to default after reconnecting
https://bugs.kde.org/show_bug.cgi?id=456703 Bug ID: 456703 Summary: Mouse settings revert to default after reconnecting Product: systemsettings Version: 5.25.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_mouse Assignee: plasma-b...@kde.org Reporter: sander.linde...@gmail.com Target Milestone: --- SUMMARY When I change the settings of my bluetooth mouse (scroll direction and pointer speed) they are reverted back to the default settings whenever my mouse reconnects. This also happens, when I connect my mouse with the USB-dongle, but only after my system wakes up after it suspends. STEPS TO REPRODUCE 1. Change settings for mouse (scroll direction and pointer speed in my case) 2. Suspend and wake-up system OR reconnect bluetooth mouse 3. Scroll and move mouse pointer OBSERVED RESULT The mouse settings (scroll direction and pointer speed) are reverted back to default settings EXPECTED RESULT The mouse settings are unchanged SOFTWARE/OS VERSIONS Operating System: Fedora Linux 36 KDE Plasma Version: 5.25.2 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.3 Kernel Version: 5.18.11-250.vanilla.1.fc36.x86_64 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics Memory: 14.9 GiB of RAM Graphics Processor: AMD RENOIR Manufacturer: Micro-Star International Co., Ltd. Product Name: Delta 15 A5EFK ADDITIONAL INFORMATION This seems X11 specific, as it does not happen when using Wayland. I can induce the same thing, settings reverting back to default, with 'sudo udevadm trigger -s input'. Interestingly, when the settings are reverted back to default, in System Settings, the indicators show the 'correct' values for scroll direction and pointer speed, but I have to re-apply them (untick scroll direction, apply, tick scroll direction, apply). Also, when I connect another mouse via usb, it seems to get configured with the default settings rather than the user's settings. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456703] Mouse settings revert to default after reconnecting
https://bugs.kde.org/show_bug.cgi?id=456703 Sander Lindeman changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Sander Lindeman --- *** This bug has been marked as a duplicate of bug 435113 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435113] certain mouse settings resets after restart/resume from suspend/dock/undock
https://bugs.kde.org/show_bug.cgi?id=435113 Sander Lindeman changed: What|Removed |Added CC||sander.linde...@gmail.com --- Comment #83 from Sander Lindeman --- *** Bug 456703 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456703] Mouse settings revert to default after reconnecting
https://bugs.kde.org/show_bug.cgi?id=456703 --- Comment #2 from Sander Lindeman --- BTW, just upgraded to Plasma 5.25.3: bug still exists. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456703] Mouse settings revert to default after reconnecting
https://bugs.kde.org/show_bug.cgi?id=456703 --- Comment #3 from Sander Lindeman --- Bug still exists in Plasma 5.25.4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455462] Wayland: Wrong keyboard layout for XWayland programs at login
https://bugs.kde.org/show_bug.cgi?id=455462 Oliver Sander changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #6 from Oliver Sander --- A recent update seems to have fixed this. Thanks to everyone involved! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] Okular does not take /UserUnit into account (page size incorrect for certain files)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #26 from Oliver Sander --- Can you guys please move the mupdf discussion elsewhere? While it is certainly interesting, it is only tangentially related to this bug. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443446] Add "previous view" and "next view" buttons
https://bugs.kde.org/show_bug.cgi?id=443446 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- Have you tried shift+alt+left? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443446] Add "previous view" and "next view" buttons
https://bugs.kde.org/show_bug.cgi?id=443446 --- Comment #3 from Oliver Sander --- I think you can already have such a button. Go to preference -> toolbar settings -> anotation toolbar, and there should be 'forward' and 'backward' actions. [The menu names may be slightly different, I translated them from my German UI.] -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 305534] Annotations don't show all non-ASCII letters
https://bugs.kde.org/show_bug.cgi?id=305534 Oliver Sander changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REOPENED|RESOLVED --- Comment #43 from Oliver Sander --- Closing again: This is a poppler issue. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 432611] Okular ignores system-wide sub-pixel rendering
https://bugs.kde.org/show_bug.cgi?id=432611 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #4 from Oliver Sander --- You can set certain aliasing settings in "preferences -> performance". They are not tied to any system-wide settings, though. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 432738] Okular prints no pdf files
https://bugs.kde.org/show_bug.cgi?id=432738 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- Does it print if you select 'force rasterization'? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 432738] Okular prints no pdf files
https://bugs.kde.org/show_bug.cgi?id=432738 --- Comment #5 from Oliver Sander --- > why Believe it or not, but 'rasterization' is actually a completely different way of printing. The standard way is to convert the file to postscript and send that to the printer. 'rasterization' renders the file into a QPrinter object, and uses the Qt printing infrastructure. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433003] PDF rendering on dual screen setup with different per-screen scaling appears broken
https://bugs.kde.org/show_bug.cgi?id=433003 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- I can confirm this not on windows, but on Plasma Wayland, where per-screen scaling is also possible. I am currently working on fixes for some of these issues---hang on. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433003] PDF rendering on dual screen setup with different per-screen scaling appears broken
https://bugs.kde.org/show_bug.cgi?id=433003 --- Comment #2 from Oliver Sander --- See https://invent.kde.org/graphics/okular/-/merge_requests/368 Doesn't fix the problem reported here, but it is related. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 432159] Okular display resolution for same pdf is low (when compared with other software) on secondary monitor with 125% scaling
https://bugs.kde.org/show_bug.cgi?id=432159 --- Comment #3 from Oliver Sander --- See https://invent.kde.org/graphics/okular/-/merge_requests/368 (which is think is related). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 432738] Okular prints no pdf files
https://bugs.kde.org/show_bug.cgi?id=432738 --- Comment #7 from Oliver Sander --- Hard to tell. It's a pretty fragile construction. Unfortunately I am not skilled enough to help you debug this. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420842] Scrolling with browse tool sticks at first after inertial scrolling implemented
https://bugs.kde.org/show_bug.cgi?id=420842 Oliver Sander changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/okular/commit/a5be0149 ||ec627fbc086e5b26cbbe7be13cd ||e49b8 --- Comment #8 from Oliver Sander --- Git commit a5be0149ec627fbc086e5b26cbbe7be13cde49b8 by Oliver Sander, on behalf of Kezi Olio. Committed on 15/09/2020 at 12:11. Pushed by ngraham into branch 'release/20.08'. Restore mouse drag scrolling, so it starts immediately QScroller uses a minimum drag distance before drag scrolling starts by default. This sets the minimum distance to 0.0, to restore the original behavior of the Browse tool. M +1-0ui/pageview.cpp https://invent.kde.org/graphics/okular/commit/a5be0149ec627fbc086e5b26cbbe7be13cde49b8 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 426679] Pinch to zoom results in scrolling in large documents
https://bugs.kde.org/show_bug.cgi?id=426679 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- Will this be fixed by https://invent.kde.org/graphics/okular/-/merge_requests/134 ? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 63749] import and export file format issues (usability)
https://bugs.kde.org/show_bug.cgi?id=63749 --- Comment #6 from Sander Devrieze --- Sorry, I am afraid that means this improvement proposal will then be gone. Unfortunately I can't help with this as I am not using KDE any more, so I have no clue about the actual state of applications. Anyone who still is using KDE will have to do this. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427356] Feature Request: save the drawings from presentation mode into a PDF file
https://bugs.kde.org/show_bug.cgi?id=427356 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #2 from Oliver Sander --- > The problem is probably that presentation drawing tools create a pixmap > overlay, No, they create paths, which is part of why they look a bit ugly. Even if they did create pixmaps (which I consider worth considering) Okular could still save those pixmaps along with the document. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427356] Feature Request: save the drawings from presentation mode into a PDF file
https://bugs.kde.org/show_bug.cgi?id=427356 --- Comment #4 from Oliver Sander --- Drawings in presentation mode are not as pretty as in other notetaking applications such as xournal++ or the Qt tablet example. Part of the reason is that Okular doesn't support changing the line width with pen pressure (I suppose that could be implemented). Another reason is that sometimes you see the line joins and ends, in particular with thicker lines. In contrast, the Qt tablet example draws sequences of spheres onto a pixmap, which avoids that problem. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 423360] Viewport blinks (flashes, disappears) while scrolling or dragging at moderate or high zoom levels
https://bugs.kde.org/show_bug.cgi?id=423360 --- Comment #5 from Oliver Sander --- > @Oliver: You wrote > https://invent.kde.org/graphics/okular/-/merge_requests/134#note_110955 . Do > you remember whether you recently updated across Poppler 0.63? No, I am quite certain that I had a new poppler when I wrote that. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 420571] Feature Request: Export/Import annotations to/from an XML file or the clipboard, using a toolbar button or context menu entry in the Reviews/Annotations side panel
https://bugs.kde.org/show_bug.cgi?id=420571 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #4 from Oliver Sander --- The two phabricator diffs mentioned in the first post look interesting in their own right. David, can I motivate you to submit them as gitlab merge requests (and maybe even adopt them wholesale)? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 409644] [Wayland] Panning in Okular is laggy with 4K monitor
https://bugs.kde.org/show_bug.cgi?id=409644 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #6 from Oliver Sander --- Do you also see the problem without scaling? Screen scaling works differently under Wayland, and you may[0] end up with an 8K temporary bitmap. That is simply a lot of data, and maybe the lagging is for that? [0] I am not 100% about this, but it is worth checking. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 409644] [Wayland] Panning in Okular is laggy with 4K monitor
https://bugs.kde.org/show_bug.cgi?id=409644 --- Comment #11 from Oliver Sander --- > Why is devicePixelRatio here forced to be 1...? That part of the code was reworked in a recent merge request. Maybe it'll help you: https://invent.kde.org/graphics/okular/-/merge_requests/371 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 438923] PDF contents tab doesn't respect empty page label number style
https://bugs.kde.org/show_bug.cgi?id=438923 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #7 from Oliver Sander --- I wouldn't mind seeing both, the number and the page label (empty if there is no label). If there is a general consensus against showing the page number, then showing nothing at all if there is no page label is okay for me, too. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 438980] display blurred
https://bugs.kde.org/show_bug.cgi?id=438980 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- What is your operating system? Do you use screen scaling? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 438980] display blurred
https://bugs.kde.org/show_bug.cgi?id=438980 --- Comment #5 from Oliver Sander --- Is it blurry on both monitors? Is it blurry if you set scaling to 100%? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 438980] display blurred
https://bugs.kde.org/show_bug.cgi?id=438980 Oliver Sander changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #7 from Oliver Sander --- This is what I expected. Per-screen-scaling hasn't seen much love until recently, because on Linux you won't get it anyway unless you use wayland. That being said, there have been a few patches recently. Can you try the 21.04 release, please, and report back? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 438980] display blurred
https://bugs.kde.org/show_bug.cgi?id=438980 --- Comment #9 from Oliver Sander --- What about the nightly builds mentioned at https://okular.kde.org/download/ ? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 438980] display blurred
https://bugs.kde.org/show_bug.cgi?id=438980 --- Comment #12 from Oliver Sander --- > Okular uses qApp->devicePixelRatio() in some places to get the screen scaling. I thought I fixed all that, but I may be wrong. The only remaining per-screen-scaling issue I know of is https://invent.kde.org/graphics/okular/-/merge_requests/368 (which only bites if you use presentation mode). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 438980] display blurred
https://bugs.kde.org/show_bug.cgi?id=438980 --- Comment #14 from Oliver Sander --- > But not in 20.12 maybe? No, not in 20.12. And I never tested it myself on Windows. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436301] Embedded Libreoffice files are not shown as embedded files in the File menu.
https://bugs.kde.org/show_bug.cgi?id=436301 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- Please attach such a file. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436301] Support non standard Libreoffice Embedded files
https://bugs.kde.org/show_bug.cgi?id=436301 Oliver Sander changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #12 from Oliver Sander --- Reading https://bugs.documentfoundation.org/show_bug.cgi?id=66580 (an old duplicate of your bug report), it seems quite clear that the LO folks are unhappy about their nonstandard way of embedding odt files into pdf files, and would rather see that changed. It is therefore extremely unlikely that Okular will ever implement support for the current LibreOffice way of embedding documents. Any developer effort is much better spent making LibreOffice standard-compatible. I will therefore close this bug report. Thanks for your interest in Okular! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436709] Autoplaying of renditions (audio/video)
https://bugs.kde.org/show_bug.cgi?id=436709 Oliver Sander changed: What|Removed |Added CC||oliver.san...@tu-dresden.de --- Comment #1 from Oliver Sander --- > I think that the current handling of "AutoPlay" is wrong for Renditions. Did you check what Acrobat does? Okular would usually strive to do the same. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427652] New: Strangely worded KMessageBox
https://bugs.kde.org/show_bug.cgi?id=427652
Bug ID: 427652
Summary: Strangely worded KMessageBox
Product: okular
Version: 1.11.2
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: okular-de...@kde.org
Reporter: oliver.san...@tu-dresden.de
Target Milestone: ---
When I open a pdf document with annotations, move one of the annotations
around, and try to quit without saving, I (rightly) get the message box
Do you want to save your changes to [filename] or discard them?
However, the choice of buttons then is
Ja Nein Abbrechen
(i.e., 'yes', 'no', 'cancel'), which doesn't really fit the question.
Strangely though, the code that produces the message box is part.cpp:1762
const int res = KMessageBox::warningYesNoCancel(widget(), i18n("Do you
want to save your changes to \"%1\" or discard them?", url().fileName()),
i18n("Close Document"), KStandardGuiItem::save(), KStandardGuiItem::discard());
To my untrained eye, the KStandardGuiItem::save() and
KStandardGuiItem::discard() make it seem like the buttons should really say
'save' and 'discard', but they don't, at least not in my German version. Is
this a bug in the German translation? Or is `warningYesNoCancel` not the right
type of message box?
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 427652] Strangely worded KMessageBox
https://bugs.kde.org/show_bug.cgi?id=427652 --- Comment #2 from Oliver Sander --- Thanks for checking. Apparently it really is a duplicate of https://bugs.kde.org/show_bug.cgi?id=420189 . I can reproduce what is described there: The buttons are only wrong when the message box appears for the first time. What exactly do I have to do to start Okular without the German translation? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427652] Strangely worded KMessageBox
https://bugs.kde.org/show_bug.cgi?id=427652 --- Comment #4 from Oliver Sander --- It must somehow be related to the translation. With LANGUAGE=en_US okular the message box works as expected. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 420189] Wrong wording for the "Save or discard" dialog
https://bugs.kde.org/show_bug.cgi?id=420189 --- Comment #7 from Oliver Sander --- I'm the reporter of Bug 427652, which is the same problem, but in Okular. Unfortunately I have a tiny bit of a nonstandard system ATM: * Okular is compiled from source * my base system is Debian testing * KDE and friends are installed from Norbert Preining's personal repository, see https://www.preining.info/blog/2020/06/kde-plasma-5-19-2-for-debian/ Plasma: 5.19.2 Frameworks: 5.71.0 Qt: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 427737] Possible vulnerability or not translated message?
https://bugs.kde.org/show_bug.cgi?id=427737 Oliver Sander changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL CC||oliver.san...@tu-dresden.de --- Comment #4 from Oliver Sander --- That French message is in the file itself. Uncompress the pdf file using, e.g., podofouncompress, and open it in a text editor. You will find 59 0 obj << /Length 1358 >> stream if (typeof(this.ADBE) == "undefined") this.ADBE = new Object(); ADBE.LANGUAGE = "ENU"; ADBE.Viewer_string_Title = "Adobe Acrobat"; ADBE.Viewer_string_Update_Desc = "Mise à jour des formulaires interactifs Adobe"; ADBE.Reader_string_Need_New_Version_Msg = "Ce fichier PDF exige l'utilisation d'une plus récente version d'Adobe Reader. Appuyez sur OK pour télécharger la plus récente version ou communiquez avec votre administrateur système."; ADBE.Viewer_string_Need_New_Version_Msg_Old = "Ce fichier PDF requiert une version plus récente d'Acrobat. Copiez cette URL et collez-la dans le navigateur, ou contacter l'admin. sys."; ADBE.Viewer_string_Need_New_Version_Msg = "Ce formulaire PDF requiert une version d'Adobe Acrobat plus récente. Sans cela, le formulaire s'affiche mais risque de ne pas fonctionner correctement. Certains éléments de formulaire risquent de ne pas s'afficher. Cliquez sur OK pour savoir comment obtenir la dernière version d'Adobe Reader."; ADBE.Viewer_string_Need_New_Version_Msg_Updater = "Ce formulaire PDF requiert une version d'Adobe Acrobat plus récente. Sans cela, le formulaire s'affiche mais risque de ne pas fonctionner correctement. Certains éléments de formulaire risquent de ne pas s'afficher. Si vous disposez d'une connexion Internet, cliquez sur OK pour télécharger et installer la dernière version du produit."; endstream endobj In conclusion, it's the intended behavior, even though it appears weird. -- You are receiving this mail because: You are watching all bug changes.
