[kmymoney] [Bug 438105] some typos found in code
https://bugs.kde.org/show_bug.cgi?id=438105 --- Comment #10 from jack --- i can't help there... it's a problem. fwiw, i can give you one of my mail sigs that illustrates this very problem. i took it from from some microsoft spec years ago... i removed some words in the middle, but this is the essence of what the sentence said: "...check the database property...to ensure that it is not checked" jack the fast gorilla skied over a lazy cloud On 10/09/2021 19:39, Thomas Baumgart wrote: > https://bugs.kde.org/show_bug.cgi?id=438105 > > --- Comment #9 from Thomas Baumgart --- > In general I agree. The question is, where these keywords are used and what > the > meaning of 'check' in another context without a reference to printing may > mean. > -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 440871] Opening the Application Menu causes the Plasma Wayland session to crash
https://bugs.kde.org/show_bug.cgi?id=440871 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- Comment #8 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 441544] Elisa don’t open playlist in Dolphin
https://bugs.kde.org/show_bug.cgi?id=441544 --- Comment #11 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 440645] program terminates suddenly or freezes
https://bugs.kde.org/show_bug.cgi?id=440645 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #7 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442051] Buttons with different heights
https://bugs.kde.org/show_bug.cgi?id=442051 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #6 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 441462] kate crashes occasionally as soon as alt+tab is pressed
https://bugs.kde.org/show_bug.cgi?id=441462 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- 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.
[systemsettings] [Bug 442289] New: System Settings Crashes When Applying Changes in Screen Edges (Settings are Still Applied)
https://bugs.kde.org/show_bug.cgi?id=442289 Bug ID: 442289 Summary: System Settings Crashes When Applying Changes in Screen Edges (Settings are Still Applied) Product: systemsettings Version: 5.22.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: essyoff.perso...@gmail.com Target Milestone: --- Application: systemsettings5 (5.22.4) Qt Version: 5.15.2 Frameworks Version: 5.85.0 Operating System: Linux 5.13.14-200.fc34.x86_64 x86_64 Windowing System: Wayland Drkonqi Version: 5.22.4 Distribution: Fedora 34 (KDE Plasma) -- Information about the crash: - What I was doing when the application crashed: Applied changes to the "Switch desktop on edge:" settings. Initially was "Always Enabled" and after changes was "Only When Moving Windows". The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault [KCrash Handler] #4 0x7f1c31033f34 in QWaylandClientExtensionPrivate::handleRegistryGlobal(void*, wl_registry*, unsigned int, QString const&, unsigned int) () from /lib64/libQt5WaylandClient.so.5 #5 0x7f1c31020419 in QtWaylandClient::QWaylandDisplay::registry_global(unsigned int, QString const&, unsigned int) () from /lib64/libQt5WaylandClient.so.5 #6 0x7f1c3103c7c3 in QtWayland::wl_registry::handle_global(void*, wl_registry*, unsigned int, char const*, unsigned int) () from /lib64/libQt5WaylandClient.so.5 #7 0x7f1c2e8ebc04 in ffi_call_unix64 () from /lib64/libffi.so.6 #8 0x7f1c2e8eb107 in ffi_call () from /lib64/libffi.so.6 #9 0x7f1c30f8dd10 in wl_closure_invoke.constprop () from /lib64/libwayland-client.so.0 #10 0x7f1c30f8e42b in dispatch_event.isra () from /lib64/libwayland-client.so.0 #11 0x7f1c30f8e61c in wl_display_dispatch_queue_pending () from /lib64/libwayland-client.so.0 #12 0x7f1c310187a3 in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib64/libQt5WaylandClient.so.5 #13 0x7f1c3361f3f0 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #14 0x7f1c33621b4a in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /lib64/libQt5Core.so.5 #15 0x7f1c33622363 in QSocketNotifier::event(QEvent*) () from /lib64/libQt5Core.so.5 #16 0x7f1c341be443 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #17 0x7f1c335eb798 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #18 0x7f1c3363d5ff in socketNotifierSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #19 0x7f1c3137b4cf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #20 0x7f1c313cf4f8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #21 0x7f1c31378c03 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #22 0x7f1c3363cb78 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #23 0x7f1c335ea1a2 in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #24 0x7f1c335f26e4 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #25 0x562498ce358c in main () [Inferior 1 (process 12039) detached] The reporter indicates this bug may be a duplicate of or related to bug 441707. Possible duplicates by query: bug 441707, bug 441700, bug 441504, bug 441277, bug 440875. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 370292] 503 Error in Korganizer using caldav with Davmail
https://bugs.kde.org/show_bug.cgi?id=370292 gjditchfi...@acm.org changed: What|Removed |Added CC||gjditchfi...@acm.org Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #4 from gjditchfi...@acm.org --- Error 503, "Service Unavailable", should indicate that there was a problem on the server -- perhaps it was down at the time. Sadly, much time has passed. Can you still reproduce this problem? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442203] Keyboard Layout change "widget" no longer works or disappears after plugging in USB Webcam
https://bugs.kde.org/show_bug.cgi?id=442203 --- Comment #5 from srame...@gmail.com --- (In reply to Andrey from comment #3) > Could you test on Wayland? I'm really not sure how to even begin to use Wayland. I can give it a try though, if you can point me in the direction I need to go to test it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442288] New: The label of Opacity: in Brush Editor - Opacity - Opacity slider needs i18n
https://bugs.kde.org/show_bug.cgi?id=442288 Bug ID: 442288 Summary: The label of Opacity: in Brush Editor - Opacity - Opacity slider needs i18n Product: krita Version: 5.0.0-beta1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Translation Assignee: krita-bugs-n...@kde.org Reporter: tyson...@tysontan.com Target Milestone: --- In Brush Editor - Opacity There is a Opacity Slider, which label is: "Opacity: " It has no i18n and thus cannot be translated. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439131] Detached brush editor does not respect brush changes done via the Python API
https://bugs.kde.org/show_bug.cgi?id=439131 --- Comment #2 from Alan North --- Seeing that other bug report, it looks more like the bug is the brush editor was never designed to "listen" to external changes since it didn't need to be, although strange the sliders do affect it. Did not think to test this at the time, but any changes that can be made via the popup palette brush hud are also a problem. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 187116] Holidays > 1 day show as multiple holidays.
https://bugs.kde.org/show_bug.cgi?id=187116 gjditchfi...@acm.org changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/pim/ ||eventviews/commit/aabf184f8 ||500ba0b8b0b1d220a5875715dfb ||1e3e --- Comment #10 from gjditchfi...@acm.org --- Git commit aabf184f8500ba0b8b0b1d220a5875715dfb1e3e by Glen Ditchfield. Committed on 10/09/2021 at 01:44. Pushed by gditchfield into branch 'release/21.08'. Display multi-day holidays as one wide block in the Month View Display multi-day holidays, such as Lunar New Year in the Hong Kong holiday list, just like a multi-day event: a block that spans days, instead of separate blocks on each day. As a side-effect, Valentine's Day does not appear in the Month View when it happens to fall on a non-workday. The Month View will only show true non-workday holidays. Users of multiple regional calendars may see multiple holidays on a day, instead of one block with multiple holiday names in it. M +5-0src/month/autotests/monthitemordertest.cpp M +7-1src/month/monthitem.cpp M +5-3src/month/monthitem.h M +18 -10 src/month/monthview.cpp M +4-0src/month/monthview.h https://invent.kde.org/pim/eventviews/commit/aabf184f8500ba0b8b0b1d220a5875715dfb1e3e -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442287] New: Replace fill layer's properties dialog color button with a color picker with instant preview
https://bugs.kde.org/show_bug.cgi?id=442287 Bug ID: 442287 Summary: Replace fill layer's properties dialog color button with a color picker with instant preview Product: krita Version: 4.4.7 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: odraenco...@gmail.com Target Milestone: --- SUMMARY It would be useful if Krita's fill layers were more like Fire Alpaca's 8 bit layers. Like this: https://i.imgur.com/45hO0E1.mp4 PROBLEM Currently, to change a fill layer's color in Krita the following steps are necessary: 1. open the layer's properties dialog. 2. click on the color button in the dialog. 3. click on a color. 4. click OK, now you can see the color changed. 5. click OK again, now the color is set. Fire Alpaca/Medibang have 8 bit and 1 bit paint layers that work in a way similar to Krita/Photoshop's fill layers, except that they're not designed as a bucket fill that applies automatically, but instead as a paint layer that can only have one color (they don't fill the canvas by default, and black is opaque instead of white). These 8 bit layers are useful for artists with workflows that make use of multiple single-color paint layers (typically cel-shaded style, with one base layer for color, and multiply/addition/etc. blend modes on top for shading). The "fill" layers in Krita/Photoshop are designed backwards for this use case, but one could still use them the same way as the 8 bit paint layers: you'd just need to delete the mask after creating the layer and draw with white instead of black. So long as you don't have a brush that uses a multiply blend mode, for example, it should work the same way. The problem is that the way color change is designed in Krita makes them practically unusable for this use case. Without this type of layer, artists with this workflow use a normal paint layer, and to change color they lock the layer's alpha, select a new color, and use a shortcut (such as CTRL+F) to fill. While this is a bit of a hassle, you can quickly click color, CTRL+F, click color, CTRL+F, click color, CTRL+F, until you find the color that you want. In photoshop and Fire Alpaca, the 8 bit/fill layer's properties dialog has a color picker immediately accessible. With just one click you can change the color and preview the result, so it's much easier to search for the color you want. In Krita, you can't preview the result as quickly. There's a color button instead of a picker, and the color button opens a dialog where you choose the color. Then you have to click OK to preview the color changed. If the color doesn't look good, you'll have to open the dialog again, click a new color, click ok again, and repeat. The process to change the color in a layer type designed to have only a single color ends up being more complicated than the same process in the general-purpose paint layer type that's designed to have any color. This isn't a problem if the fill layer is supposed to be just an automated bucket fill tool that you barely touch, similar to a filter layer, but I think with some small changes like this one these fill layers could also be used as single-color paint layers, which would be useful for artists with the aforementioned workflow. PROPOSED SOLUTION Replace the color button with a color picker, and make picking a color preview the change instantly. ADDITIONAL INFORMATION Bug 412928 proposes to change the way the brush's color picker works when fill layers are selected, which would equally make the color-change process faster. I don't think this should be done. First, tools should work seamlessly independent of layer. Selecting the gray color makes the brush paint gray, and it just happens in mask/fill layers gray means half-transparent. If you changed this, there would be no way to paint "gray" in a fill layer. I don't remember for sure, but I think there was a brush setting to make it replace the layer's alpha with the brush's opacity instead of adding alpha. You could use this instead, but you would need to create a custom brush just for fill layers. Second, if selecting the color for the brush changes the layer's color, then conversely selecting a fill layer should change the brush's color to match. This would mean the brush color changes without you changing it. If you were painting green on one layer, and selected a blue fill layer, when you go back to the previous layer, is your brush green or blue? In either case it would be very confusing. Instead it makes more sense that the same color (white in Krita's case) always mean opaque, so you don't need to watch the brush's color when changing layers. One solution could be if clicking on the fill layer thumbnail (which shows its solid color) in the layers docker
[Breeze] [Bug 442286] Text in new "Shift to extend tooltip" is broken with Breeze High Contrast
https://bugs.kde.org/show_bug.cgi?id=442286 Thiago Sueto changed: What|Removed |Added Keywords||accessibility -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 442286] New: Text in new "Shift to extend tooltip" is broken with Breeze High Contrast
https://bugs.kde.org/show_bug.cgi?id=442286 Bug ID: 442286 Summary: Text in new "Shift to extend tooltip" is broken with Breeze High Contrast Product: Breeze Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: herzensch...@gmail.com Target Milestone: --- Created attachment 141462 --> https://bugs.kde.org/attachment.cgi?id=141462=edit Broken text with Breeze High Contrast Really, the screenshot should be self-explanatory. Text mentioning "Press shift to see more" is gray and unreadable in tooltips. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 439811] KStars crash when launched on Ubuntu 21.04
https://bugs.kde.org/show_bug.cgi?id=439811 --- Comment #7 from James --- (In reply to James from comment #6) > I am using kstars 5.5.5 compiled nightly on Kubuntu 21.04 with no issues in > this regard. But I use the stable Indi sources compiled too, not nightly. > Hope this helps I mean Kstars 3.5.5 lol -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 439811] KStars crash when launched on Ubuntu 21.04
https://bugs.kde.org/show_bug.cgi?id=439811 James changed: What|Removed |Added CC||jrlangsto...@gmail.com --- Comment #6 from James --- I am using kstars 5.5.5 compiled nightly on Kubuntu 21.04 with no issues in this regard. But I use the stable Indi sources compiled too, not nightly. Hope this helps -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 442252] konsole starts with tiny window if old konsolerc present
https://bugs.kde.org/show_bug.cgi?id=442252 --- Comment #3 from Ahmad Samir --- (It's also possible I got it wrong and State has nothing to do with the window size). -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 442252] konsole starts with tiny window if old konsolerc present
https://bugs.kde.org/show_bug.cgi?id=442252 Ahmad Samir changed: What|Removed |Added CC||a.samir...@gmail.com --- Comment #2 from Ahmad Samir --- It looks like it's not just the State= key, these ones come into play too: DP-1 Height DP-1 Width DP-1 XPosition DP-1 YPosition -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412928] Use color selector dockers for fill color when a fill layer is selected.
https://bugs.kde.org/show_bug.cgi?id=412928 Leonardo changed: What|Removed |Added CC||odraenco...@gmail.com --- Comment #6 from Leonardo --- (In reply to Halla Rempt from comment #4) > I think would agree with Ian: it makes more sense to select the color for > the fill layer than the level of grayness for the brush, given that opacity > also works fine for editing the fill layer. > > I have to say, I have never seen anyone use fill layers like this, though :-) I disagree. The color selector is supposed to select the color of the brush tool, and tools are supposed to work seamlessly regardless of layer type. If you select the gray color, you can make any paint layer gray, and any mask 50% alpha, and you can make a fill layer's mask 50% alpha. if you changed this only for fill layers, then you would need to create a custom brush to force 50% alpha just for fill layers. You wouldn't be able to use the same brush you use in a normal layer or in a transparency mask layer. The use cases are limited but I believe painting with a gray brush should make the alpha 50%. It's how it works in Fire Alpaca/Medibang, for example. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424649] Cannot paste text copied from GTK app after closing it when "Prevent empty clipboard" is turned off
https://bugs.kde.org/show_bug.cgi?id=424649 --- Comment #20 from James Flynn --- (In reply to Bharadwaj Raju from comment #19) > (In reply to James Flynn from comment #18) > > Not to be contrary, but at least with specifically Firefox (91.0.2), this is > > still an issue on my Fedora 34 KDE install. It does appear this is even with > > the "Prevent empty clipboard" checked, there are still *some* times where > > blank clipboard entries occur. See highlighted attachment > > Were you copying text from the webpage, or from the addressbar? > > For some reason, the former works for me reliably, while the latter often > doesn't and inserts a blank entry instead. Just text on a page, but happens to me often enough I forgot to mention that, sorry! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442253] KCM Defaults do not match kwin defaults
https://bugs.kde.org/show_bug.cgi?id=442253 David Edmundson changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/commit/ ||8f847087c178941d6c11996db40 ||064b122b33c33 --- Comment #2 from David Edmundson --- Git commit 8f847087c178941d6c11996db40064b122b33c33 by David Edmundson. Committed on 10/09/2021 at 22:25. Pushed by davidedmundson into branch 'master'. [libcolorcorrect] Sync night colour default values The default value for active in the kcfg file inside kwin for colour correction is false. As we have a bridge that mirrors the config contents over DBus and defaults hardcoded in a second format this has got out of sync. This both leads to the default button being enabled/disabled incorrectly on a fresh system and not working properly. More important as geo-location is on by default this leads to http requests being made without the user's explicit consent. A major bug. M +1-1libcolorcorrect/compositorcoloradaptor.h https://invent.kde.org/plasma/plasma-workspace/commit/8f847087c178941d6c11996db40064b122b33c33 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 442252] konsole starts with tiny window if old konsolerc present
https://bugs.kde.org/show_bug.cgi?id=442252 Ahmad Samir changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #1 from Ahmad Samir --- *** Bug 442284 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 442284] konsole is very small after very first start
https://bugs.kde.org/show_bug.cgi?id=442284 Ahmad Samir changed: What|Removed |Added Status|REPORTED|RESOLVED CC||a.samir...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from Ahmad Samir --- *** This bug has been marked as a duplicate of bug 442252 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442285] Moving Digital Clock widget in direction of Task Manager causes that Digital Clock disappars
https://bugs.kde.org/show_bug.cgi?id=442285 Piotr Mierzwinski changed: What|Removed |Added Platform|Other |Neon Packages CC||piotr.mierzwin...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442285] New: Moving Digital Clock widget in direction of Task Manager causes that Digital Clock disappars
https://bugs.kde.org/show_bug.cgi?id=442285 Bug ID: 442285 Summary: Moving Digital Clock widget in direction of Task Manager causes that Digital Clock disappars Product: plasmashell Version: git-master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: piotr.mierzwin...@gmail.com Target Milestone: 1.0 SUMMARY I have vertical panel. Digital Clock is placed on very bottom. I wanted to rearrange a bit the widgets on my Panel, so tried to move Digital Clock on top of the panel. In result I was very surprised because Digital Clock just disappeared when mouse cursor was over Task Manager. The same happened when I moved System Tray widget, which was placed also on bottom. Notice that underneath the Panel was nothing, I moved it from left to right edge of screen. This disappearing was very confused. I noticed, that when I want to rearrange widgets on Panel I need to just move Task Manager widget. Only in this case other widgets just jumps on Task Manager. To back to the previous situation I needed to drag and drop lost widgets taking them from Widgets side bar. STEPS TO REPRODUCE 1. Set panel as right side 2. Add to the panel (counting from bottom) Digital Clock, System Tray, Task Manager, Application launcher 3. Turn on "Edit Panel" 4. Try to move Digital Clock on top OBSERVED RESULT Digital Clock disappears EXPECTED RESULT Digital Clock should try to jump on Task Manger and don't lost SOFTWARE/OS VERSIONS Linux/KDE Plasma: YES (available in About System) KDE Plasma Version: 5.22.80 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Up-to-date Neon/Linux on day 2021/09/10, time 23:32 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 442228] Latte-dock causes Microsoft Edge to crash
https://bugs.kde.org/show_bug.cgi?id=442228 --- Comment #5 from Pango Gillespi --- informational only: today's Edge-dev release (95.0.1000.0-1) continues to have the same problem -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434286] [systemd startup] Sometimes System Monitor sensors do not work after re-login
https://bugs.kde.org/show_bug.cgi?id=434286 --- Comment #17 from David Edmundson --- Put #!/bin/sh dbus-monitor --pcap > /tmp/dbus-log & in /etc/X11/Xsession.d and make it executable That will create a file in /tmp/dbus-log Not that this file might contain lots of other information, so you might want to just ping me on IRC/whatever and take some screenshots from Bustle filtering ksystemstats -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 442284] New: konsole is very small after very first start
https://bugs.kde.org/show_bug.cgi?id=442284 Bug ID: 442284 Summary: konsole is very small after very first start Product: konsole Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: piotr.mierzwin...@gmail.com Target Milestone: --- Created attachment 141461 --> https://bugs.kde.org/attachment.cgi?id=141461=edit konsole - 3 rows, very first start SUMMARY I logged in on new user, and started konsole. In result I got window with 3 rows. STEPS TO REPRODUCE 1. Create new user 2. Log in on new ueser 3. Start konsole OBSERVED RESULT konsole window has 3 row EXPECTED RESULT In my opinion konsole window shold have more than 3 row, maybe 30 SOFTWARE/OS VERSIONS Linux/KDE Plasma: YES (available in About System) KDE Plasma Version: 5.22.80 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Up-to-date Neon/Linux on day 2021/09/10, time 23:32 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439127] Crash when switching to smudge brush engine with rgba tip in lightness map mode
https://bugs.kde.org/show_bug.cgi?id=439127 Alan North changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #2 from Alan North --- This had been a bug that I'd been asked to file when an MR regarding default rgba tip settings was being tested. In the end I think changes to the MR were made and this was fixed or no longer relevant. I just checked to be sure, but it's no longer a problem. I've closed it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442283] Restore session in Wayland doesn't work
https://bugs.kde.org/show_bug.cgi?id=442283 --- Comment #2 from Piotr Mierzwinski --- After I back to x11 I got broken desktop, I mean I lost the panel. Only Firefox was restored. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419277] krita-4.2.9: CMake Error at cmake/modules/FindOpenEXR.cmake:43, 49, 55: string sub-command REGEX, mode MATCHALL needs at least 5 arguments total to command
https://bugs.kde.org/show_bug.cgi?id=419277 --- Comment #25 from amyspark --- (In reply to Andreas Sturmlechner from comment #21) > (In reply to Halla Rempt from comment #20) > > Wasn't this fixed by now? > That depends how you look at it. cmake/modules/FindOpenEXR.cmake didn't > receive any fix for that meanwhile. > > I'm still applying the patch to use ECM FindOpenEXR to krita 4.4.2 because I > know it works and our repository still provides the older openexr-2.3.0 > (even if likely not used by krita users) besides >=2.5 where Pixar's module > seems to work. > > - Can we be sure it won't break in the future? > - Shouldn't ideally be ECM's module be fixed to work with Windows? Andreas, it'd be great if you could check with the module in my MR. Let me know if you find any errors. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442283] Restore session in Wayland doesn't work
https://bugs.kde.org/show_bug.cgi?id=442283 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #1 from Piotr Mierzwinski --- I started again my all applications. Logged out and logged in. In result again nothing was restored. I back to x11 windowing system. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419277] krita-4.2.9: CMake Error at cmake/modules/FindOpenEXR.cmake:43, 49, 55: string sub-command REGEX, mode MATCHALL needs at least 5 arguments total to command
https://bugs.kde.org/show_bug.cgi?id=419277 --- Comment #24 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/1049 -- 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 Manuel Geißer changed: What|Removed |Added CC|aa...@kde.org | -- 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 #9 from Manuel Geißer --- Sorry. I just thought you'd be the maintainer of Okular, and wondered why you are not in the CC list, but apparently this has its reason. Sorry, really. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442283] New: Restore session in Wayland doesn't work
https://bugs.kde.org/show_bug.cgi?id=442283 Bug ID: 442283 Summary: Restore session in Wayland doesn't work Product: plasmashell Version: git-master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: piotr.mierzwin...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 141460 --> https://bugs.kde.org/attachment.cgi?id=141460=edit Configuratio-Destkop_Session SUMMARY I switched for tests to Wayland session. I have opened couple applications like Firefox, Dolphin, Konsole, Kate and Clementine (on one from 3 activities). After first login ot Wayland session was correctly restored. So I started Dolphin application in my second activity, back to my default activity and signed out. I signed it and turned out that only Firefox was restored. STEPS TO REPRODUCE 1. Create couple activities 2. Start couple applications on 'default' activity 3. Sign off 4. Select Wayland session and sign in 5. On second activity start Dolphin 6. Sign out and Sign in OBSERVED RESULT Only Firefox is restored EXPECTED RESULT Should be restore all running applications in moment of signing out SOFTWARE/OS VERSIONS Linux/KDE Plasma: YES (available in About System) KDE Plasma Version: 5.22.80 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Up-to-date Neon/Linux on day 2021/09/10, 23:32 -- 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 Manuel Geißer changed: What|Removed |Added CC|aa...@kde.org | -- 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 #8 from Albert Astals Cid --- Do *not* add me to bugs. I don't understand what makes you think that is normal behaviour, but it's not, you're only making me ignore you. -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 442274] No winning games of Baker's Dozen
https://bugs.kde.org/show_bug.cgi?id=442274 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org, ||lang_mich...@ymail.com --- Comment #1 from Albert Astals Cid --- Adding Michael Lang which i hope is the same Michael Lang that implemented Baker's Dozen in kpat. Michael sorry if you aren't -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442282] Adding Digital Clock from desktop onto Panel makes that widget is visually broken
https://bugs.kde.org/show_bug.cgi?id=442282 --- Comment #3 from Piotr Mierzwinski --- Sign out -> Sign in, just helps. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442282] Adding Digital Clock from desktop onto Panel makes that widget is visually broken
https://bugs.kde.org/show_bug.cgi?id=442282 --- Comment #2 from Piotr Mierzwinski --- Notice that changing "Font style" in Digital Clock settings helps nothing. Still we can see visually broken digital clock. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442282] Adding Digital Clock from desktop onto Panel makes that widget is visually broken
https://bugs.kde.org/show_bug.cgi?id=442282 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #1 from Piotr Mierzwinski --- Created attachment 141459 --> https://bugs.kde.org/attachment.cgi?id=141459=edit lasma-broken-Digital_Clock -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442282] New: Adding Digital Clock from desktop onto Panel makes that widget is visually broken
https://bugs.kde.org/show_bug.cgi?id=442282 Bug ID: 442282 Summary: Adding Digital Clock from desktop onto Panel makes that widget is visually broken Product: plasmashell Version: git-master Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: piotr.mierzwin...@gmail.com Target Milestone: 1.0 SUMMARY When you move Digital Clock onto desktop and want you put it back to Panel then turns out that on Panel we get trashes (check screen shot). To get visually correct Digital Clock need to drag and drop it directly from Widgets side bar. I use vertical panel and didn't test it on horizontal one. STEPS TO REPRODUCE 1. Turn on "Edit Panel" 2. Move Digital Clock onto desktop (isn't possible to put is anywhere, because it will stuck very close to the panel) 3. Move back (Drag and Drop) Digital Clock from Desktop onto Panel OBSERVED RESULT we get visually broken Digital Clock, seems like could chosen some strange font. Clock is not readable EXPECTED RESULT Digital Clock when backs onto the panel should look like before we moved it onto desktop SOFTWARE/OS VERSIONS Linux/KDE Plasma: YES (available in About System) KDE Plasma Version: 5.22.80 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION In test I used up-do-date Neon on day: 2021/09/10, 23:02 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442241] Black screen with egl-wayland 1.1.8
https://bugs.kde.org/show_bug.cgi?id=442241 --- Comment #5 from Marcelo Bossoni --- Created attachment 141458 --> https://bugs.kde.org/attachment.cgi?id=141458=edit firefox screen capture -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442241] Black screen with egl-wayland 1.1.8
https://bugs.kde.org/show_bug.cgi?id=442241 --- Comment #4 from Marcelo Bossoni --- Created attachment 141457 --> https://bugs.kde.org/attachment.cgi?id=141457=edit Screen capture of about kcm -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442241] Black screen with egl-wayland 1.1.8
https://bugs.kde.org/show_bug.cgi?id=442241 --- Comment #3 from Marcelo Bossoni --- Interesting, tried with current master and same thing happens. When I open Firefox in wayland mode, my mouse cursor turns into a small white dot. After closing it, it turn into a black box. Screen capture using spectacle seems to show it properly. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 442089] Tens of "error while trying to delete calendar item" popups appear randomly
https://bugs.kde.org/show_bug.cgi?id=442089 gjditchfi...@acm.org changed: What|Removed |Added Product|korganizer |Akonadi CC||gjditchfi...@acm.org, ||kdepim-b...@kde.org Component|general |Google Resource Assignee|kdepim-b...@kde.org |dvra...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 439285] Bad request, Google replied "Contacts API is being deprecated"
https://bugs.kde.org/show_bug.cgi?id=439285 gjditchfi...@acm.org changed: What|Removed |Added CC||gjditchfi...@acm.org -- 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 #7 from Manuel Geißer --- Created attachment 141456 --> https://bugs.kde.org/attachment.cgi?id=141456=edit adobe_reader ... only Adobe Reader gets the proportions right -- 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 #6 from Manuel Geißer --- 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 ... -- 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 Manuel Geißer changed: What|Removed |Added Summary|Okular does not take|Okular does not take |/UserUnit into account |/UserUnit into account |(page size incorrect) |(page size incorrect for ||certain files) -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 442272] Playlist shows bogus track names when enqueueing tracks while shuffling is on
https://bugs.kde.org/show_bug.cgi?id=442272 --- Comment #3 from Nate Graham --- Yeah, I did do that. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442281] The key repeat speed is reset upon logging out or closing my laptop lid.
https://bugs.kde.org/show_bug.cgi?id=442281 --- Comment #2 from Andrey --- Please test both X11/Wayland -- 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)
https://bugs.kde.org/show_bug.cgi?id=442280
--- Comment #5 from Manuel Geißer ---
Created attachment 141455
--> https://bugs.kde.org/attachment.cgi?id=141455=edit
Proportions pdf
For you to confirm the UserUnit is set on the first page of the document in the
screenshot, but not on the other pages.
```python3
>>> from tests_pdfnodegraph.pathtools import TestOutput
>>> pdf = pikepdf.open(join(TestOutput,'out_14.pdf'))
>>> page = pdf.pages[0]
>>> page.UserUnit
Decimal('10.0')
>>> page_2 = pdf.pages[1]
>>> page_2.UserUnit
Traceback (most recent call last):
File "", line 1, in
File "/home/manuel/.local/lib/python3.8/site-packages/pikepdf/_methods.py",
line 1143, in __getattr__
return getattr(self.obj, name)
AttributeError: /UserUnit
>>>
```
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 442281] The key repeat speed is reset upon logging out or closing my laptop lid.
https://bugs.kde.org/show_bug.cgi?id=442281 --- Comment #1 from orbofl...@gmail.com --- I should clarify that I am referring to the key repeat DELAY, not RATE. Rate may also reset, but I don't change it so I don't know. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442281] New: The key repeat speed is reset upon logging out or closing my laptop lid.
https://bugs.kde.org/show_bug.cgi?id=442281 Bug ID: 442281 Summary: The key repeat speed is reset upon logging out or closing my laptop lid. Product: systemsettings Version: 5.22.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_keyboard Assignee: plasma-b...@kde.org Reporter: orbofl...@gmail.com CC: butir...@gmail.com Target Milestone: --- SUMMARY The key repeat speed is reset upon logging out or closing my laptop lid. STEPS TO REPRODUCE 1. Change key repeat speed from default (600) 2. Log out or close laptop 3. Log back in OBSERVED RESULT Key repeat speed is back at 600 EXPECTED RESULT Key repeat speed should be whatever I changed it to. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro KDE (available in About System) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION This issue is also present on my desktop, only when logging out (or restarting, which implies a logout.) Both of these computers experience this issue on a completely fresh install. -- 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)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #4 from Manuel Geißer --- > the space reserved for rendering the actual page or better formulated: the proportions of different pages to each other -- 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)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #3 from Manuel Geißer --- To clarify, I think it is not only the displayed size number that is incorrect, but also the space reserved for rendering the actual page: The screenshot I just added illustrates it better: The first page is from the userunit_10 file. The other 2 pages are ANSI A and A4 size, which is very roughly 200mm width - put one of the smaller pages three times next to each other, and it approximately matches the width of the larger page, although in fact it should be a lot larger - roughly thirty times the width of the smaller page! -- 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)
https://bugs.kde.org/show_bug.cgi?id=442280 --- Comment #2 from Manuel Geißer --- Created attachment 141454 --> https://bugs.kde.org/attachment.cgi?id=141454=edit userunit_screenshot -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441312] Add window titles and icons
https://bugs.kde.org/show_bug.cgi?id=441312 --- Comment #29 from Michał Dybczak --- Manuel, I just explained HOW MY BRAIN PROCESS IT AND I OR YOU CAN'T CHANGE IT. No matter how you argue, it doesn't change anything. There is nothing to agree or disagree upon. I can't disagree on how I feel, nor I can disagree on your feelings as well. Because you process overview better without icons, doesn't contradict the fact that others, like me, need icons to process it. Forcing one solution or the other would be hurtful to a lot of people. That is why, leaving option to turn on/off icons is just the sanest approach, especially that those options already exist, so we are merely making sure that those won't disappear with the next overview version. Since the case is RESOLVED FIXED, I assume, this means those options persist, so you get what you want, and I get what I want. All is well and there is nothing to discuss further. -- 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)
https://bugs.kde.org/show_bug.cgi?id=442280
--- Comment #1 from Manuel Geißer ---
Python shell code to reproduce (replace TestFiles.userunit_10 with the path
string where you saved the file, and skip the first import which depends on
custom test infrastructure of the lib I am developing):
```python3
Python 3.8.10 (default, Jun 2 2021, 10:49:15)
[GCC 9.4.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from tests_pdfnodegraph.testfiles import TestFiles
>>> import pikepdf
>>> pdf = pikepdf.Pdf.open(TestFiles.userunit_10)
>>> page = pdf.pages[0]
>>> page.MediaBox
pikepdf.Array([ Decimal('0.0'), Decimal('0.0'), Decimal('1785.6'),
Decimal('1785.6') ])
>>> page.UserUnit
Decimal('10.0')
>>> 1785.6 * 1/72 * 25.4
629.91998
>>> 1785.6*10 * 1/72 * 25.4
6299.2
```
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 399864] Folder view crashes when moving file from popup views into parent view
https://bugs.kde.org/show_bug.cgi?id=399864 Andrey changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399864] Folder view crashes when moving file from popup views into parent view
https://bugs.kde.org/show_bug.cgi?id=399864 --- Comment #23 from Andrey --- For X just can't drop it such way because the held file icon disappears as soon as it matched with the target folder. -- 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 --- Comment #1 from Manuel Geißer --- Ping. :) -- 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)
https://bugs.kde.org/show_bug.cgi?id=442280 Manuel Geißer changed: What|Removed |Added CC||aa...@kde.org, ||geisse...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 442280] New: Okular does not take /UserUnit into account (page size incorrect)
https://bugs.kde.org/show_bug.cgi?id=442280
Bug ID: 442280
Summary: Okular does not take /UserUnit into account (page size
incorrect)
Product: okular
Version: 21.08.1
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: PDF backend
Assignee: okular-de...@kde.org
Reporter: geisse...@gmail.com
Target Milestone: ---
Created attachment 141453
--> https://bugs.kde.org/attachment.cgi?id=141453=edit
userunit_10.pdf
SUMMARY
[PDF background]
In the PDF format, coordinates are given in PDF points, where by default 1
point is equivalent to 1/72 of an inch (1in -> 2.54cm). However, PDFs can
define custom units on a per-page basis, using the /UserUnit key.
/UserUnit is a float or decimal that scales the default conversion fraction of
1/72, so for a /UserUnit of 10, 1pt would mean 10/72in.
[What Okular does]
It seems that Okular (like many other open-source PDF software) does not take
/UserUnit into account for the displayed page size.
The attached test document `userunit_10.pdf` defines a /UserUnit of 10.
The document's /MediaBox looks like this:
```python3
[ Decimal('0.0'), Decimal('0.0'), Decimal('1785.6'), Decimal('1785.6')
```
Now the default conversion with 1pt -> 1/72in returns 630x630mm, which is what
Okular displays. However, this is incorrect. In reality, the size is 6300mm, 10
times larger!
(In particular, /UserUnit is used by Adobe Illustrator and possibly other PDF
software to circumvent the maximum number of 14400pt imposed by Adobe Reader
and some other PDF renderers.)
STEPS TO REPRODUCE
1. Open the attached file in Okular
2. Go to File -> Properties
3. See the displayed page size
4. Inspect the document with the pikepdf python library, or and other PDF
library of your choice
5. Print the /MediaBox and /UserUnit of page 0
OBSERVED RESULT
Displayed page size is too small by factor 10.
EXPECTED RESULT
Displayed page size should always reflect the real page size and take /UserUnit
into account.
Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.3
Kernel Version: 5.11.0-34-generic (64-bit)
Graphics Platform: Wayland
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 442189] HEIC photos with GPS coordinates embeded in metadata are not used in digikam database for geolocation
https://bugs.kde.org/show_bug.cgi?id=442189 --- Comment #7 from caulier.gil...@gmail.com --- Francisco, I think it's more the new HEIF metadata support introduced in Exiv2 and used to populate the database which can make mess. The Exiv2 version supporting HEIF is 0.27.4: https://www.exiv2.org/whatsnew.html digiKam for Windows has only used this Exiv2 version with last 7.3.0. Best regards Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 399864] Folder view crashes when moving file from popup views into parent view
https://bugs.kde.org/show_bug.cgi?id=399864 Andrey changed: What|Removed |Added CC||butir...@gmail.com --- Comment #22 from Andrey --- Can reproduce at least on Wayland, but it seem only happens if trying to drag from intermediate folder to a neighbor folder 2 levels up, as in the video: Folder1Folder2 (Drag here)\ Intermediate Folder | File to drag -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 423424] Kmail "forces" the user to accept invalid TLS certificates.
https://bugs.kde.org/show_bug.cgi?id=423424 Sandro Knauß changed: What|Removed |Added CC||skna...@kde.org --- Comment #2 from Sandro Knauß --- The vulnerable is now published under https://nostarttls.secvuln.info/ -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 441952] Cannot create a gocryptfs vault due to faulty version number checking code
https://bugs.kde.org/show_bug.cgi?id=441952 --- Comment #9 from Nowshed H. Imran --- Great! -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 442279] neon unstable is unable to update plasma-workspace package
https://bugs.kde.org/show_bug.cgi?id=442279 Patrick Silva changed: What|Removed |Added Summary|neon unstable is unable |neon unstable is unable to |tpupdate plasma-workspace |update plasma-workspace |package |package -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 442279] New: neon unstable is unable tpupdate plasma-workspace package
https://bugs.kde.org/show_bug.cgi?id=442279 Bug ID: 442279 Summary: neon unstable is unable tpupdate plasma-workspace package Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages Unstable Edition Assignee: neon-b...@kde.org Reporter: bugsefor...@gmx.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- 'sudo apt update && sudo apt full-upgrade' gives me this outout: The following packages have unmet dependencies: plasma-workspace-dev : Depends: libkfontinstui5 (= 4:5.22.4+p20.04+tunstable+git20210829.0322-0) but 4:5.22.5+p20.04+tunstable+git20210910.0201-0 is installed Depends: libkworkspace5-5 (= 4:5.22.4+p20.04+tunstable+git20210829.0322-0) but 4:5.22.5+p20.04+tunstable+git20210910.0201-0 is installed Depends: libplasma-geolocation-interface5 (= 4:5.22.4+p20.04+tunstable+git20210829.0322-0) but 4:5.22.5+p20.04+tunstable+git20210910.0201-0 is installed Depends: libweather-ion7 (= 4:5.22.4+p20.04+tunstable+git20210829.0322-0) but 4:5.22.5+p20.04+tunstable+git20210910.0201-0 is installed plasma-workspace-wayland : Depends: plasma-workspace (= 4:5.22.5+p20.04+tunstable+git20210910.0201-0) but 4:5.22.4+p20.04+tunstable+git20210829.0322-0 is installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). 'sudo apt --fix-broken install' gives me this output: Do you want to continue? [Y/n] (Reading database ... 341020 files and directories currently installed.) Preparing to unpack .../plasma-workspace_4%3a5.22.5+p20.04+tunstable+git20210910.0201-0_amd64.deb ... Unpacking plasma-workspace (4:5.22.5+p20.04+tunstable+git20210910.0201-0) over (4:5.22.4+p20.04+tunstable+git20210829.0322-0) ... dpkg: error processing archive /var/cache/apt/archives/plasma-workspace_4%3a5.22.5+p20.04+tunstable+git20210910.0201-0_amd64.deb (--unpack): trying to overwrite '/usr/share/metainfo/org.kde.breezedark.desktop.appdata.xml', which is also in package breeze 4:5.22.5+p20.04+tunstable+git20210901.0223-0 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/plasma-workspace_4%3a5.22.5+p20.04+tunstable+git20210910.0201-0_amd64.deb -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 442278] Crash when trying to edit title clip after changing project resolution
https://bugs.kde.org/show_bug.cgi?id=442278 Fabian changed: What|Removed |Added CC||fabianroel...@googlemail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 442278] New: Crash when trying to edit title clip after changing project resolution
https://bugs.kde.org/show_bug.cgi?id=442278 Bug ID: 442278 Summary: Crash when trying to edit title clip after changing project resolution Product: kdenlive Version: 21.08.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: fabianroel...@googlemail.com Target Milestone: --- STEPS TO REPRODUCE 1. Create a title clip. 2. Change the project's resolution. 3. Double-click the title clip to edit it. I have not tested whether this always happens with these steps, but it does at least happen every time I double-click a title clip in my current project. OBSERVED RESULT Warning: "This title clip was created with a different frame size.", then crash. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I do not have debug information, because the kdenlive-dbg and libmlt-dbg packages are not available on my system (at least the package manager doesn't list any candidates). This issue is related to #419985. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 423423] STARTTLS is ignored when "Server requires authentication" not checked in UI
https://bugs.kde.org/show_bug.cgi?id=423423 Sandro Knauß changed: What|Removed |Added CC||skna...@kde.org --- Comment #4 from Sandro Knauß --- The vulnerable is now published under https://nostarttls.secvuln.info/ -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 442277] Shortcuts reset on every start
https://bugs.kde.org/show_bug.cgi?id=442277 Fabian changed: What|Removed |Added CC||fabianroel...@googlemail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 442277] New: Shortcuts reset on every start
https://bugs.kde.org/show_bug.cgi?id=442277 Bug ID: 442277 Summary: Shortcuts reset on every start Product: kdenlive Version: 21.08.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: fabianroel...@googlemail.com Target Milestone: --- STEPS TO REPRODUCE 1. Set some keyboard shortcut. 2. Close and reopen KDEnlive. OBSERVED RESULT No action has any shortcut assigned, neither custom, nor default. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 442276] New: Chroma key does nothing
https://bugs.kde.org/show_bug.cgi?id=442276 Bug ID: 442276 Summary: Chroma key does nothing Product: kdenlive Version: 21.08.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: gmike.tra...@gmail.com Target Milestone: --- Created attachment 141452 --> https://bugs.kde.org/attachment.cgi?id=141452=edit example video clip SUMMARY STEPS TO REPRODUCE 1. Add attached clip to timeline 2. Add another clip below the first clip 3. Add chroma key effect to first clip 4. Set chroma key's color key to the background, using the color select tool OBSERVED RESULT Background is not deleted from the first clip, it covers up the second clip entirely. EXPECTED RESULT Background colors should be removed from the first clip and the remaining parts should be overlaid on the second clip. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 411878] Dolphin is not clearing prior filter view if directory is open
https://bugs.kde.org/show_bug.cgi?id=411878 --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/system/dolphin/-/merge_requests/271 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 442272] Playlist shows bogus track names when enqueueing tracks while shuffling is on
https://bugs.kde.org/show_bug.cgi?id=442272 --- Comment #2 from Nagy Tibor --- Did you enqueued the tracks one-by-one and not with the "enqueue the whole album" button? That's an important step for repro. Only breaks when the tracks are manually added, the enqueue whole album button works properly. Also this bug is a bit spurious, sometimes it may not manifest itself until you added 4-5 items to the playlist. I posted a worst case scenario in that video. I checked this bug on git master, I can still reproduce it there. (git 0dd33183) -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 426400] Fix KF5 issues on Windows
https://bugs.kde.org/show_bug.cgi?id=426400 Bug 426400 depends on bug 384051, which changed state. Bug 384051 Summary: No reset of hcbi account pin possible https://bugs.kde.org/show_bug.cgi?id=384051 What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |UPSTREAM -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 384051] No reset of hcbi account pin possible
https://bugs.kde.org/show_bug.cgi?id=384051 Thomas Baumgart changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |UPSTREAM --- Comment #13 from Thomas Baumgart --- @Ralf: AqBanking 6.3.1 and Gwenhywfar 5.7.1 are the new stable releases and maint branch points to them. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 438105] some typos found in code
https://bugs.kde.org/show_bug.cgi?id=438105 --- Comment #9 from Thomas Baumgart --- In general I agree. The question is, where these keywords are used and what the meaning of 'check' in another context without a reference to printing may mean. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 442112] Missing timezones
https://bugs.kde.org/show_bug.cgi?id=442112 --- Comment #4 from Vasil Yonkov --- Thank you for working on this issue. I must've misspelled Auckland when I was trying to come up with examples. Sometimes I interact with people from places like that and it's convenient to have the clock show their time. That's my use case. I was using gnome for a while and the clock there had all cities I needed, so my thinking was that you probably use an incomplete source. I was surprised when you said you maintain an explicit list of cities. It will indeed be much better if you can get the list automatically from a source that specializes in keeping track of timezones and that sort of stuff. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 430075] Plasma Shell Crash SSL Certificate
https://bugs.kde.org/show_bug.cgi?id=430075 --- Comment #3 from aleprez...@pm.me --- (In reply to Marco Antonucci from comment #2) > Same thing just happened to me on a freshly installed Kubuntu 20.04. Maybe > there's some geographical implication? I'm from Italy, as the original > reporter and (i suspect) "aleprez...@pm.me" who has commented on this bug... Yes I'm Italian and my device location is Italy. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 442261] undefined references to `DIGIKAM_WEBSERVICES_LOG()'
https://bugs.kde.org/show_bug.cgi?id=442261 --- Comment #4 from gessel --- retried: success! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441896] The compositor does not turn on when the system starts
https://bugs.kde.org/show_bug.cgi?id=441896 D1mon changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 441896] The compositor does not turn on when the system starts
https://bugs.kde.org/show_bug.cgi?id=441896 --- Comment #3 from D1mon --- The problem was in: "Allow application to block compositing" -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 442275] New: Creating a folder while filtering messes the filter results
https://bugs.kde.org/show_bug.cgi?id=442275 Bug ID: 442275 Summary: Creating a folder while filtering messes the filter results Product: dolphin Version: 21.08.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: bars: filter Assignee: dolphin-bugs-n...@kde.org Reporter: eduardo.c...@kdemail.net CC: kfm-de...@kde.org Target Milestone: --- Created attachment 141451 --> https://bugs.kde.org/attachment.cgi?id=141451=edit Parent folder "a" is not displayed, despite being expanded and its child folders "b" and "b2" being displayed. SUMMARY While filtering on expanded details view mode, if we create a folder that satisfies the filter as a child of an expanded folder, Dolphin will mess up the file listing, making the parent folder disappear and the childs appear in a buggy state without their parent being display (see screenshot). This is a very specific bug, very difficult to explain and difficult to trigger in normal use, but it exists and I have successfully devised a simple recipe to reproduce it consistently. It is really difficult to explain in words, its better to just do the steps below and you will see the bug for yourself. STEPS TO REPRODUCE 1. Create an empty folder anywhere, named "test" (or whatever name you desire). Open it on Dolphin. 2. Make sure you are on Details View mode with expandable folders. 3. Create a folder named "a" inside "test". 4. Right click "a", Create New -> Folder, and name it "b". 5. Expand folder "a", you should see the tree: "a" as parent and "b" as child. 6. Filter for the string "b". It should not change the view at all, since folder "b" passes the filter and "a" is shown because it is its parent. 7. Now, with the filter activated, right click "a" and create another folder named "b2" (a sibling of "b"). 8. The bug is now triggered: after 1 second, folder "a" will disappear, and you will only see folders "b" and "b2", weirdly linked to no parent (screenshot). OBSERVED RESULT Folders "b" and "b2" are displayed linked to an invisible parent. EXPECTED RESULT Folder "a" should remain on display, with folders "b" and "b2" as its children passing the filter. SOFTWARE/OS VERSIONS Dolphin 21.08.1 Operating System: Arch Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.14.2-arch1-2 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION I discovered this bug while testing my solution for bug #411878. I thought I had introduced the bug, bug then I found out it was already there before my changes. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434286] [systemd startup] Sometimes System Monitor sensors do not work after re-login
https://bugs.kde.org/show_bug.cgi?id=434286 --- Comment #16 from Patrick Silva --- could anyone provide instructions to get the log requested in the comment 15 please? -- You are receiving this mail because: You are watching all bug changes.
[umbrello] [Bug 442115] C++ importer does not recognize 'noexcept' keyword
https://bugs.kde.org/show_bug.cgi?id=442115 Oliver Kellogg changed: What|Removed |Added Latest Commit||https://invent.kde.org/sdk/ ||umbrello/commit/0372f89d799 ||5a5fbc557e6c6090208bc54950e ||88 Status|REPORTED|RESOLVED Resolution|--- |FIXED CC||okellogg@users.sourceforge. ||net -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442128] Help > Report Bug feature crashes Krita
https://bugs.kde.org/show_bug.cgi?id=442128 --- Comment #10 from Przemysław Gołąb --- Awesome, thank you for your work :) -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 441952] Cannot create a gocryptfs vault due to faulty version number checking code
https://bugs.kde.org/show_bug.cgi?id=441952 --- Comment #8 from Ivan Čukić --- No need. If this happens again, then I'll annoy them ;) Thanks -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441201] "Eraser Circle" and "Basic-5 Size" have become untagged
https://bugs.kde.org/show_bug.cgi?id=441201 --- Comment #3 from tomtomtomreportin...@gmail.com --- Created attachment 141450 --> https://bugs.kde.org/attachment.cgi?id=141450=edit Fresh Erasers.tag vs. my Erasers.tag It looks like my .tag files were scuffed, and removing resourcecache.sqlite or KRITA_RESOURCE_VERSION didn't seem to fix them. See the attachment comparing the Erasers.tag in a fresh environment to my Erasers.tag in my typical environment. Notably the .kpp extension for the Default Resources property is missing, along with the Resource Type property, although it's the former that affects this issue (is the Resource Type property important to have?). The fact that removing resourcecache.sqlite or KRITA_RESOURCE_VERSION doesn't fix the tag files is reproducible in a fresh environment. However, removing KRITA_RESOURCE_VERSION does regenerate the .tag file if it's outright missing. So is this an issue? -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 442263] Radio buttons for selecting active audio device do not work
https://bugs.kde.org/show_bug.cgi?id=442263 empyreal changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from empyreal --- Yes! Radio buttons! Exactly. When clicked, nothing happens. Radio button is unchecked. You can see on screenshot that current source is HDMI, but is not checked. Look at HDMI volume scale start (blue color). It's active but unchecked. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 441975] difficulties assigning shortcuts after upgrade
https://bugs.kde.org/show_bug.cgi?id=441975 --- Comment #7 from Nate Graham --- Thank you for clarifying that you are using a wacom pen, which is information that was not initially provided. :) I have one too and can try to reproduce the issue. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 442272] Playlist shows bogus track names when enqueueing tracks while shuffling is on
https://bugs.kde.org/show_bug.cgi?id=442272 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #1 from Nate Graham --- Cannot reproduce, works for me. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419277] krita-4.2.9: CMake Error at cmake/modules/FindOpenEXR.cmake:43, 49, 55: string sub-command REGEX, mode MATCHALL needs at least 5 arguments total to command
https://bugs.kde.org/show_bug.cgi?id=419277 amyspark changed: What|Removed |Added Status|REOPENED|ASSIGNED Assignee|krita-bugs-n...@kde.org |a...@amyspark.me CC||a...@amyspark.me Component|General |File formats --- Comment #23 from amyspark --- If the ECM module works everywhere *except for Windows*, I know what the issue is. Assigning. -- You are receiving this mail because: You are watching all bug changes.
