[kwin] [Bug 445240] Logging from kwin_wayland failing to start with 10 "cannot open display" Gtk-WARNING lines is not helpful enough to determine the issue
https://bugs.kde.org/show_bug.cgi?id=445240 --- Comment #5 from Alex Folland --- No, I didn't see any change in visibility from the TTY. The source of these logs is from redirecting the output to a file, and there was no output that wasn't redirected, as I saw no text output, but the file was populated. I think you've hit the nail on the head about what this issue ticket is for: the fact that the logging output from kwin is not helpful enough to determine the issue. It shouldn't simply exit without saying exactly what happened. Instead, it should show some kind of helpful error message explaining exactly what's wrong, or better yet, simply work instead, since other graphical programs work with no issue. I can even run RetroArch directly, for example, with no X11 or Wayland server previously running, so kwin doesn't have a good excuse to not simply render to my screens. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443183] New File dialog startup time is dependent on size of image in clipboard
https://bugs.kde.org/show_bug.cgi?id=443183 Halla Rempt changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/commit/bdf06f651 |hics/krita/commit/2b4743edc |1a8c29a3988b021cedca0b23a0a |4c6a8d0a2ad35bfcd270a2c6dcc |74b7|a7e5 --- Comment #9 from Halla Rempt --- Git commit 2b4743edc4c6a8d0a2ad35bfcd270a2c6dcca7e5 by Halla Rempt. Committed on 12/08/2022 at 05:39. Pushed by rempt into branch 'krita/5.1'. Only access the clipboard when we really need it * remove two superfluous sig/slot connections in KisClipboard. These QClipboard modes are not relevant for Krita, and were fired together with dataChanged, resulting in clipboardChanged being called three times. * remove the preview() method which was only used by the custom image widget * set the default w/h for the imagefromclipboard widget to 1, so we don't need to retrieve the QImage from the clipboard just to get the actual dimensions * simplify KisClipboard::clipboardDataChanged so it doesn't need to retrieve the qimage from the clipboard. This means that hasClip() can be true because there are images on the qclipboard, so that needs to be tested. (cherry picked from commit bdf06f6511a8c29a3988b021cedca0b23a0a74b7) M +3-9libs/ui/KisMainWindow.cpp M +3-40 libs/ui/kis_clipboard.cc M +0-3libs/ui/kis_clipboard.h M +0-1libs/ui/widgets/kis_custom_image_widget.cc M +23 -9libs/ui/widgets/kis_image_from_clipboard_widget.cpp M +4-4libs/ui/widgets/kis_image_from_clipboard_widget.h https://invent.kde.org/graphics/krita/commit/2b4743edc4c6a8d0a2ad35bfcd270a2c6dcca7e5 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443183] New File dialog startup time is dependent on size of image in clipboard
https://bugs.kde.org/show_bug.cgi?id=443183 Halla Rempt changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/krita/commit/3d7b2e017 |hics/krita/commit/bdf06f651 |e49276064ceafce7932a7235954 |1a8c29a3988b021cedca0b23a0a |1aad|74b7 --- Comment #8 from Halla Rempt --- Git commit bdf06f6511a8c29a3988b021cedca0b23a0a74b7 by Halla Rempt. Committed on 12/08/2022 at 05:39. Pushed by rempt into branch 'master'. Only access the clipboard when we really need it * remove two superfluous sig/slot connections in KisClipboard. These QClipboard modes are not relevant for Krita, and were fired together with dataChanged, resulting in clipboardChanged being called three times. * remove the preview() method which was only used by the custom image widget * set the default w/h for the imagefromclipboard widget to 1, so we don't need to retrieve the QImage from the clipboard just to get the actual dimensions * simplify KisClipboard::clipboardDataChanged so it doesn't need to retrieve the qimage from the clipboard. This means that hasClip() can be true because there are images on the qclipboard, so that needs to be tested. M +3-9libs/ui/KisMainWindow.cpp M +3-40 libs/ui/kis_clipboard.cc M +0-3libs/ui/kis_clipboard.h M +0-1libs/ui/widgets/kis_custom_image_widget.cc M +23 -9libs/ui/widgets/kis_image_from_clipboard_widget.cpp M +4-4libs/ui/widgets/kis_image_from_clipboard_widget.h https://invent.kde.org/graphics/krita/commit/bdf06f6511a8c29a3988b021cedca0b23a0a74b7 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414746] Selections and select shape tool behave weirdly with guide feature
https://bugs.kde.org/show_bug.cgi?id=414746 Halla Rempt changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #10 from Halla Rempt --- Okay, closing then for now. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412849] Crash after deleting layers, resizing image and cropping on relatively large file
https://bugs.kde.org/show_bug.cgi?id=412849 Halla Rempt changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414746] Selections and select shape tool behave weirdly with guide feature
https://bugs.kde.org/show_bug.cgi?id=414746 --- Comment #9 from acc4commissi...@gmail.com --- I generally always have Canvas Graphics Accelerations on. I'm not entirely sure but I'm pretty sure it was enabled. But when I tested with the latest nightly build today(git f03ffc1) this bug didn't show. I'll post here if it happens again later. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 439268] Typing text in the search bar sends data although suggestions are disabled
https://bugs.kde.org/show_bug.cgi?id=439268 Juraj changed: What|Removed |Added CC||jurajora...@mailo.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Juraj --- Confirmed. The suggestions from search engine are JUST not displayed while the search engine is always being contacted. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 447247] dbus-run-session startplasma-wayland locks up my console
https://bugs.kde.org/show_bug.cgi?id=447247 --- 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.
[konsole] [Bug 434214] Cursor font is huge on startup with some fonts.
https://bugs.kde.org/show_bug.cgi?id=434214 --- Comment #5 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.
[kwin] [Bug 455521] WindowHeap-based effects open and close way too fast
https://bugs.kde.org/show_bug.cgi?id=455521 --- Comment #17 from breakingsp...@gmail.com --- > Just to clear one possible issue, you are also using kde git version, correct? Yes, I use kdesrc-build against master branch for testing, while my system KDE is 5.25.4 release. My test prep is setting Desktop Grid to Custom layout for 2x2 grid with 4 virtual desktops, nothing else changed from defaults aside from global animation slider while testing. BTW, it doesn't look like the merge to change the duration has made it into KDE Neon just yet, my eyes noticed on a fresh boot, and the build logs match up (neon-testing-20220809-1823.iso while the commit and build for kwin went in on 8/10 via https://build.neon.kde.org/). Next one should have this change, I'm looking forward to testing it from iso too. >Yes, i agree, the extreme values are way ... extreme :) If Nate has no issue, >I could supply a patch to make it less "extreme" and more granular. I think this is an excellent idea, simplifies config in a good way, and wouldn't be too hard to implement. It's hard to think of a use case that would desire the outer edges of the global slider, a default center and two or three ticks to each side seems much more reasonable. A new merge request for enhancement would be the best way to move that forward. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 412849] Crash after deleting layers, resizing image and cropping on relatively large file
https://bugs.kde.org/show_bug.cgi?id=412849 Bug Janitor Service changed: What|Removed |Added Ever confirmed|1 |0 Resolution|WORKSFORME |--- Status|NEEDSINFO |REPORTED --- Comment #7 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.
[krita] [Bug 457155] Slow start
https://bugs.kde.org/show_bug.cgi?id=457155 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 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.
[frameworks-kiconthemes] [Bug 456541] KDE Menu Editor stops responding and then crashes when attempting to change app icon.
https://bugs.kde.org/show_bug.cgi?id=456541 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 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.
[kio-extras] [Bug 456669] dolphin and kioclient stucks when connecting to smb with domain
https://bugs.kde.org/show_bug.cgi?id=456669 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #10 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 449442] Brush tool display freezes intermittently during normal use.
https://bugs.kde.org/show_bug.cgi?id=449442 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 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 452685] Shortcuts not working unless one switches back and forth between applications
https://bugs.kde.org/show_bug.cgi?id=452685 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 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.
[kdenlive] [Bug 457160] Speech Recognition fails with vosk-model-en-us-0.21
https://bugs.kde.org/show_bug.cgi?id=457160 --- 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.
[plasmashell] [Bug 456620] Application launcher opens on wrong monitor
https://bugs.kde.org/show_bug.cgi?id=456620 --- Comment #5 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.
[Discover] [Bug 450949] Discover crashed in KNSBackend::setResponsePending() while uninstalling a plasma widget
https://bugs.kde.org/show_bug.cgi?id=450949 --- 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.
[kwin] [Bug 444604] Pointer misbehave on Wayland
https://bugs.kde.org/show_bug.cgi?id=444604 --- Comment #9 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.
[kwin] [Bug 430010] Desktop freeze after resume from Screen Energy Saving.
https://bugs.kde.org/show_bug.cgi?id=430010 --- Comment #3 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.
[palapeli] [Bug 446583] cursor size changed to a smaller one after update
https://bugs.kde.org/show_bug.cgi?id=446583 --- Comment #3 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.
[kwin] [Bug 435979] Crash whenever QtQuick scene is attempted to be created (tabbox, snapping indicator, etc.)
https://bugs.kde.org/show_bug.cgi?id=435979 --- Comment #5 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.
[kwin] [Bug 430516] UI freezes after ~2-3 mins after every login for ~30 seconds
https://bugs.kde.org/show_bug.cgi?id=430516 --- Comment #3 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.
[kwin] [Bug 342326] window contents freeze
https://bugs.kde.org/show_bug.cgi?id=342326 --- Comment #43 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.
[Oxygen] [Bug 325390] oxygen mouse cursor: intermediate size?
https://bugs.kde.org/show_bug.cgi?id=325390 --- Comment #3 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.
[kdeconnect] [Bug 441830] 12 TCP keepalive packets per minute is excessive, battery drain hazard.
https://bugs.kde.org/show_bug.cgi?id=441830 --- Comment #6 from Maxim Egorushkin --- Longer story about this bug report. My OnePlus 7T Pro McLaren would go 2 days without charge in my routine, with day 2 morning charge above 55% for the first 8 months, I was quite impressed. Then suddenly day 2 morning charge became ~38%. I examined phone battery stats and there was Android System being top battery consumer with 25%+, which I hadn't seen being above 10% before. I wasn't able to find the cause of Android System battery drain at the time and had to switch to charging the phone every night. A few weeks later I started Wireshark on my workstation for unrelated task and couldn't help but notice these 5-second keepalive TCP messages between KDE Connect on the workstation and the phone. The phone with its screen off replied to all these keepalive messages, which looked excessive and unnecessary. I uninstalled KDE Connect app from my phone, went on with my task, charged the phone overnight. Next day at charge time the remaining charge was above 60% and Android System battery usage went lower than 10%. I switched back to charging the phone once in 2 days. I had to make this workaround because it makes 2x difference for me in how often the phone needs to be charged. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455521] WindowHeap-based effects open and close way too fast
https://bugs.kde.org/show_bug.cgi?id=455521 --- Comment #16 from Alexandre Pereira --- Hi, > Alexandre, may I ask how you have perceived the speed of the old > implementation of Present Windows (pre-Overview) until Plasma 5.24? The previous speed of Present Windows were fine, and it was when I switched to it as an alt tab replacement. I also checked the code: https://invent.kde.org/plasma/kwin/-/blob/v5.23.0/src/effects/presentwindows/presentwindows.cpp#L164 > Could you test with a live CD? In my perception, this new values are just a > touch slower than the old, 300 ms feels just a bit closer to my eye. But like > my whole bug report and the Reddit thread with dozens of upvotes found, 200 > ms is definitely way too fast. I will test a live iso later on. Like I said on my previous comment, I use the 1 tick slider speed anim to the left, which makes ALL animations smooth and consistent. Overview seems smooth, but now noticeable slow, and others super fast. Also, the speed can be related to the bug I mentioned on the previous commit, when it was changed from kwinrc to kdeglobals, and the speed was reset (making it faster to those that had a slower speed factor on kwinrc. I am speculating here, could be, probably isn't). > If you have used it like an Alt + Tab replacement, maybe look into the Alt + > Tab window switcher settings, there is a grid layout you can chose. hum... I actually prefer the present windows/overview effect to the grid layout, but I know the effect you mention, since I use the small grid as alt tab. I just don't like alt tab as much as I prefer to see all windows scaled on the screen. > Present Windows, Overview and the actual Grid should have another speed with > more elegance, signaling also your current window positions. That’s how this > effect series worked since Plasma 4, Compiz and on their origins in OS X. > Plasma 5.25’s speeds just were a shortsighted fault of the reimplemetation. I don't think 5.25's speeds are faster. Looking at the code, they are slower. But in my mind, some effects shouldn't have more "elegance" than others, they all should have elegance (especially no frame skipping). That is why, again, I used the 1.4 factor, which would probably put the timings around 300ms from the 200ms (and with it, all the effects were buttery smooth). Maybe 300ms is a good middle ground, if you also feel it is a touch slower. But as to how it should be, that isn't for me to say, nor I am part of the VDG nor a "usability expert". If the goal is to have some effects fast and some slow, and I am the only one with an issue to it, then nevermind, I will adapt to it some way. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 416475] Display Configuration not saved properly on Wayland with multiple monitors
https://bugs.kde.org/show_bug.cgi?id=416475 Forrest Hilton changed: What|Removed |Added Version|5.17.90 |5.24.4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455521] WindowHeap-based effects open and close way too fast
https://bugs.kde.org/show_bug.cgi?id=455521 --- Comment #15 from Maximilian Böhm --- (In reply to Alexandre Pereira from comment #12) Alexandre, may I ask how you have perceived the speed of the old implementation of Present Windows (pre-Overview) until Plasma 5.24? Could you test with a live CD? In my perception, this new values are just a touch slower than the old, 300 ms feels just a bit closer to my eye. But like my whole bug report and the Reddit thread with dozens of upvotes found, 200 ms is definitely way too fast. If you have used it like an Alt + Tab replacement, maybe look into the Alt + Tab window switcher settings, there is a grid layout you can chose. Present Windows, Overview and the actual Grid should have another speed with more elegance, signaling also your current window positions. That’s how this effect series worked since Plasma 4, Compiz and on their origins in OS X. Plasma 5.25’s speeds just were a shortsighted fault of the reimplemetation. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 442143] System Monitor crashes when switching to "Applications" section
https://bugs.kde.org/show_bug.cgi?id=442143 --- Comment #4 from Marcelo Zoel --- Created attachment 151269 --> https://bugs.kde.org/attachment.cgi?id=151269=edit New crash information added by DrKonqi plasma-systemmonitor (5.25.4) using Qt 5.15.5 EVery time when I click on Applications the system crashes -- Backtrace (Reduced): #5 0x7f2ade683ceb in QQuickItemLayer::~QQuickItemLayer() () from /lib64/libQt5Quick.so.5 #6 0x7f2ade683d5d in QQuickItemLayer::~QQuickItemLayer() () from /lib64/libQt5Quick.so.5 #7 0x7f2ade80b0a6 in QAccessibleQuickItem::role() const () from /lib64/libQt5Quick.so.5 #8 0x7f2adf876a39 in AtSpiAdaptor::pathForInterface(QAccessibleInterface*) const () from /lib64/libQt5WaylandClient.so.5 #9 0x7f2adf8798b8 in AtSpiAdaptor::notifyStateChange(QAccessibleInterface*, QString const&, int) () from /lib64/libQt5WaylandClient.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 442143] System Monitor crashes when switching to "Applications" section
https://bugs.kde.org/show_bug.cgi?id=442143 Marcelo Zoel changed: What|Removed |Added CC||marcelo.z...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455521] WindowHeap-based effects open and close way too fast
https://bugs.kde.org/show_bug.cgi?id=455521 --- Comment #14 from Alexandre Pereira --- > Interesting, I wonder if another factor is at play or causing the scaling to > be wrong in cases. On my system and liveCD tests, the merged changes to > duration and easing cause the WindowHeap transitions to match every other > effect, when they didn't before. Even the old duration of 300ms is too quick. Its strange, here it was "on par" with other effects, which I then used a 1.4 animation factor ( one tick just to the left of default ). > I just spun up a new local user with no config, tried plus and minus 2 ticks > on the global Animation Speed slider, and compared the Overview and Desktop > Grid against the open/close Window Animations (Fade, Glide, Scale) and > Minimize effects, they still match up for me and look very consistent. Even > extremes on the scale match up, and i'm honestly wondering why the scale is > so large as the center 5 ticks are the most distinct. Yes, i agree, the extreme values are way ... extreme :) If Nate has no issue, I could supply a patch to make it less "extreme" and more granular. Its extremely weird, because the other effects are all around 150ms~200ms. even old present windows. And here is very very noticeable. > Could something in config be overriding the duration and throwing things off > on some environments but not all? For instance, I removed this line in my > config a year or so ago (around 5.23 release when things regressed) to fix > the issue in the title: https://bbs.archlinux.org/viewtopic.php?id=263845. > It makes me wonder if a similar thing is occurring with the Windowheap > effects for some users, possibly even the systems that 400ms look good on > (liveCD though..) I've also tested the durations with a 60hz laptop while on > a trip this last week, to rule out higher refresh displays being an edge case. I can try a kde neon live cd in the weekend or earlier if I can. But that setting is correct here. I tend to keep an eye on it, because there was a bug that used to reset it, which David Edmundson fixed. ( he also fixed other bugs, like this one: https://invent.kde.org/plasma/kwin/-/commit/0bb3eb2baf5b0a4c0aacbe23bf55c47c0a2c39fd ). Just to clear one possible issue, you are also using kde git version, correct? Also as a workaround, the slide/glide effect allow to specify the duration. Overriding it to 400 makes it more similar in timings to the overview/present windows now. So something weird is happening here... I don't know if its not my system at fault, but I checked the kwinrc variable (it should NOT have one) and the kdeglobals one (which can actually be a custom number if one edits it manually). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450448] Scrolling with touchscreen does not work consistently
https://bugs.kde.org/show_bug.cgi?id=450448 --- Comment #6 from Nate Graham --- We could port them to *Handler items, but there's sort of a conceptual incompatibility between touch-scrolling and touch-dragging, for views where items are draggable. We currently have press-and-hold bound to "show context menu," so we would have to re-arrange the UI a bit probably, to make press-and-hold-and-drag re-arrange items, while press-and-hold-and-release-without-moving opens a context menu. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455521] WindowHeap-based effects open and close way too fast
https://bugs.kde.org/show_bug.cgi?id=455521 --- Comment #13 from breakingsp...@gmail.com --- Interesting, I wonder if another factor is at play or causing the scaling to be wrong in cases. On my system and liveCD tests, the merged changes to duration and easing cause the WindowHeap transitions to match every other effect, when they didn't before. Even the old duration of 300ms is too quick. I just spun up a new local user with no config, tried plus and minus 2 ticks on the global Animation Speed slider, and compared the Overview and Desktop Grid against the open/close Window Animations (Fade, Glide, Scale) and Minimize effects, they still match up for me and look very consistent. Even extremes on the scale match up, and i'm honestly wondering why the scale is so large as the center 5 ticks are the most distinct. Could something in config be overriding the duration and throwing things off on some environments but not all? For instance, I removed this line in my config a year or so ago (around 5.23 release when things regressed) to fix the issue in the title: https://bbs.archlinux.org/viewtopic.php?id=263845. It makes me wonder if a similar thing is occurring with the Windowheap effects for some users, possibly even the systems that 400ms look good on (liveCD though..) I've also tested the durations with a 60hz laptop while on a trip this last week, to rule out higher refresh displays being an edge case. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455521] WindowHeap-based effects open and close way too fast
https://bugs.kde.org/show_bug.cgi?id=455521 Alexandre Pereira changed: What|Removed |Added CC||pereira.a...@gmail.com --- Comment #12 from Alexandre Pereira --- Hi, This is just a matter of taste/opinion, i guess... but as a heavy present windows/overview user, this is now way too slow. As using present windows as almost an alt+tab replacement, its now ... weird ... Worse, i guess, is that it feels completely disconnected with other animation speeds: window opening, closing, fading, minimizing, plasma popups sliding. for example: * sliding popups is 150ms * slide (open/close) is 200ms and glide is 160ms * fade is 150 ms The issue with 400 for me, is that is completely set apart from the rest of kde's animations, making me unable to control it (set it faster, makes everything super fast... make everything "normal speed", present windows/ overview seem super slow ) Could a middle ground be achieved on this ? Thanks ! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 457742] Plasmashell crashes when unlocking
https://bugs.kde.org/show_bug.cgi?id=457742 --- Comment #2 from macr...@gmail.com --- (In reply to Nate Graham from comment #1) > FWIW the "unlock button doesn't work" issue is very likely Bug 456210. Much obliged, I will look into that thread and see if I can contribute anything of value. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457784] New: Filter layers generate incorrect preview when bounds change.
https://bugs.kde.org/show_bug.cgi?id=457784 Bug ID: 457784 Summary: Filter layers generate incorrect preview when bounds change. Product: krita Version: git master (please specify the git hash!) Platform: Other OS: All Status: REPORTED Severity: normal Priority: NOR Component: Filter Layers Assignee: krita-bugs-n...@kde.org Reporter: i...@ralek.art Target Milestone: --- Created attachment 151268 --> https://bugs.kde.org/attachment.cgi?id=151268=edit Example corruption Occurs on both Linux and Windows builds, on master and on 5.0.6. I have tried reverting 81f9b1aac8 with no luck. When transforming or cropping filter layers, the final preview is incorrect. The canvas shows large holes in the filter layer. See attached. These corruptions are cosmetic, and fix themselves if the affected filter layer is hidden and re-shown. To reproduce : 1. Create a new document 2. Create a new layer other than background and fill with a darker color 3. Create a filter layer above the dark layer. As far as I have tested, it doesn't matter which. 4. Transform the adjustment layer. I've found it seems to show up more the longer the transform process takes. Sometimes it doesn't show up unless you undo the transformation. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450448] Scrolling with touchscreen does not work consistently
https://bugs.kde.org/show_bug.cgi?id=450448 --- Comment #5 from Nate Graham --- Looks like it's the embedded MouseArea in each delegate that blocks events from reaching the scrollable view. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456076] Task Manager icons no longer honor panel margins, effectively making them bigger than intended
https://bugs.kde.org/show_bug.cgi?id=456076 --- Comment #12 from loca...@tutanota.com --- > I can't find what part of the Task Manager icon code adds in the Panel > margins; it's like it's missing. Maybe that's the problem lol The change happened between plasma versions 5.24.4 and 5.25.3, so running a diff on the Task Manager code between those two versions should help identifying it. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 457783] Mix transitions don't work. Error message: Not enough frames at clip [end/start] to apply the mix. Transitions not saved if added to image clips.
https://bugs.kde.org/show_bug.cgi?id=457783 Darwin McGrath changed: What|Removed |Added CC||dar...@mcgrathtoronto.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 457783] New: Mix transitions don't work. Error message: Not enough frames at clip [end/start] to apply the mix. Transitions not saved if added to image clips.
https://bugs.kde.org/show_bug.cgi?id=457783 Bug ID: 457783 Summary: Mix transitions don't work. Error message: Not enough frames at clip [end/start] to apply the mix. Transitions not saved if added to image clips. Product: kdenlive Version: 22.04.3 Platform: Compiled Sources OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: dar...@mcgrathtoronto.com Target Milestone: --- SUMMARY Mix transitions not working 1. Mix transitions between video clips cannot be applied. Error message is: "Not enough frames at clip [end/start] to apply the mix" despite clips being 40+ seconds long 2. Mix transitions between image clips are not saved. Missing when project is reloaded. STEPS TO REPRODUCE 1. Create a new project and add video and image clips to the Project bin and add them to the timeline 2. Double click between two video clips of suitable length to add mix. Will receive error message, mix not created. 3. Double click between two image clips to add mix. Mix will be added. edit transition as desired (e.g. slide) 4. Save file. Close kdenlive. open kdenlive, open saved project. transition is gone or missing .pgm file message pops up. OBSERVED RESULT Error message when trying to create mix transition between video clips. Mix Transitions between image clips gone or pgm file missing when reloading project EXPECTED RESULT Should be able to add mix transitions between video clips. Transitions should be saved. SOFTWARE/OS VERSIONS Windows: 11 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Attempted mix transition with slide from right to left and with luma bar horizontal -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kquickcharts] [Bug 457248] System monitor pie chart scaling error with non-zero manual data range
https://bugs.kde.org/show_bug.cgi?id=457248 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/fram ||eworks/kquickcharts/-/commi ||t/7d72fc0e9173dc95e8095c1d3 ||3ded5ca45673b90 Status|CONFIRMED |RESOLVED Version Fixed In||5.98 --- Comment #10 from Nate Graham --- Fixed by Roman Lebedev with https://invent.kde.org/frameworks/kquickcharts/-/commit/7d72fc0e9173dc95e8095c1d33ded5ca45673b90 in Frameworks 5.98! -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 457782] New: Music folder resets if not reachable
https://bugs.kde.org/show_bug.cgi?id=457782 Bug ID: 457782 Summary: Music folder resets if not reachable Product: Elisa Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: ja...@nerdonthestreet.com Target Milestone: --- SUMMARY I keep my music folder on a NAS that I mount manually when I boot my desktop computer. Sometimes, I forget to mount the NAS, and when I open Elisa, my music folder resets from the NAS mount directory to the default (~/Music). This indexes several thousand files that I don't want in my library, and causes me to have to re-configure my desired music folder after mounting the NAS. While automatically mounting the NAS may be one obvious workaround to this, the issue would also affect the NAS or network connection going down temporarily; if I happen to launch Elisa during one of those events, I wouldn't want my music folder reset either. STEPS TO REPRODUCE 1. Configure the music directory 2. Unmount or otherwise remove access to the music directory 3. Launch Elisa OBSERVED RESULT The music directory resets to ~/Music. EXPECTED RESULT The previously-configured music directory should remain configured. If it doesn't exist, I might expect the music collection to show up as empty, and/or an error message that one of the music folders can't be found could be displayed. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 92310] wish: spell check support in picture comments
https://bugs.kde.org/show_bug.cgi?id=92310 --- Comment #29 from caulier.gil...@gmail.com --- Git commit 5043eee626e3143924637936f869f5b66dc95e2b by Gilles Caulier. Committed on 11/08/2022 at 23:30. Pushed by cgilles into branch 'master'. Add spell-checking to JAlbumExport project title settings Related: bug 402922, bug 360954, bug 256471 M +12 -10 core/dplugins/generic/tools/jalbum/wizard/jalbumoutputpage.cpp https://invent.kde.org/graphics/digikam/commit/5043eee626e3143924637936f869f5b66dc95e2b -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 256471] add spell checking to text areas
https://bugs.kde.org/show_bug.cgi?id=256471 --- Comment #28 from caulier.gil...@gmail.com --- Git commit 5043eee626e3143924637936f869f5b66dc95e2b by Gilles Caulier. Committed on 11/08/2022 at 23:30. Pushed by cgilles into branch 'master'. Add spell-checking to JAlbumExport project title settings Related: bug 402922, bug 360954, bug 92310 M +12 -10 core/dplugins/generic/tools/jalbum/wizard/jalbumoutputpage.cpp https://invent.kde.org/graphics/digikam/commit/5043eee626e3143924637936f869f5b66dc95e2b -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 360954] No spell checking when entering Tags
https://bugs.kde.org/show_bug.cgi?id=360954 --- Comment #34 from caulier.gil...@gmail.com --- Git commit 5043eee626e3143924637936f869f5b66dc95e2b by Gilles Caulier. Committed on 11/08/2022 at 23:30. Pushed by cgilles into branch 'master'. Add spell-checking to JAlbumExport project title settings Related: bug 402922, bug 256471, bug 92310 M +12 -10 core/dplugins/generic/tools/jalbum/wizard/jalbumoutputpage.cpp https://invent.kde.org/graphics/digikam/commit/5043eee626e3143924637936f869f5b66dc95e2b -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 402922] Spell check
https://bugs.kde.org/show_bug.cgi?id=402922 --- Comment #34 from caulier.gil...@gmail.com --- Git commit 5043eee626e3143924637936f869f5b66dc95e2b by Gilles Caulier. Committed on 11/08/2022 at 23:30. Pushed by cgilles into branch 'master'. Add spell-checking to JAlbumExport project title settings Related: bug 360954, bug 256471, bug 92310 M +12 -10 core/dplugins/generic/tools/jalbum/wizard/jalbumoutputpage.cpp https://invent.kde.org/graphics/digikam/commit/5043eee626e3143924637936f869f5b66dc95e2b -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 457701] Add .mp4 support
https://bugs.kde.org/show_bug.cgi?id=457701 --- Comment #4 from WS --- I've emailed it to you -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 456313] Forms does not work, street art guide
https://bugs.kde.org/show_bug.cgi?id=456313 Albert Astals Cid 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 450448] Scrolling with touchscreen does not work consistently
https://bugs.kde.org/show_bug.cgi?id=450448 --- Comment #4 from Nate Graham --- Looks like it works if you drag on a header (using either a touchscreen or a pointing device, interestingly), but if you do it on an item, it eats the event and treats it as an attempt to activate the item. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 452430] PDF: Find in view mode "facing pages" scroll to incorrect places
https://bugs.kde.org/show_bug.cgi?id=452430 --- Comment #5 from Albert Astals Cid --- Still can not reproduce. Could you record a video of it failing? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457552] Add ctrl+k and ctrl+j shortcuts to navigate up and down in the Kickoff search results
https://bugs.kde.org/show_bug.cgi?id=457552 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1089 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 457748] Review tools toolbar appears on all desktops when it's floating
https://bugs.kde.org/show_bug.cgi?id=457748 Albert Astals Cid changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- CC||aa...@kde.org --- Comment #5 from Albert Astals Cid --- Cannot reproduce here. Can anyone else see that? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416130] Global Shortcuts for seeking forward and backward by 5s, 10s etc.
https://bugs.kde.org/show_bug.cgi?id=416130 Patrick Silva changed: What|Removed |Added CC||empyr...@ukr.net --- Comment #7 from Patrick Silva --- *** Bug 457749 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457749] Global actions/shortcuts to skip back or forward some number of seconds in the currently playing track
https://bugs.kde.org/show_bug.cgi?id=457749 Patrick Silva changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||bugsefor...@gmx.com Resolution|--- |DUPLICATE --- Comment #2 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 416130 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456076] Task Manager icons no longer honor panel margins, effectively making them bigger than intended
https://bugs.kde.org/show_bug.cgi?id=456076 --- Comment #11 from Nate Graham --- (In reply to d7ghrrkcz from comment #10) > I'm sorry, I am not a developer. I just wish problem has been fixed and Task > Manager behaves like before. Of course you do; so do I. :) To make that happen, someone needs to fix it. That's type of contribution that's helpful at this point. I'm looking into it, but could use some help. I can't find what part of the Task Manager icon code adds in the Panel margins; it's like it's missing. Maybe that's the problem lol -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 457781] New: Autonomization of tasks causes disappearance of them and no demonstration of autonomy until Kontact is reinitialized.
https://bugs.kde.org/show_bug.cgi?id=457781 Bug ID: 457781 Summary: Autonomization of tasks causes disappearance of them and no demonstration of autonomy until Kontact is reinitialized. Product: kontact Version: 5.20.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: todo Assignee: kdepim-b...@kde.org Reporter: beedellrokejulianlockh...@gmail.com Target Milestone: --- OBSERVED RESULT: Causing tasks to become independent solely causes their titles to disappear from the interface until Kontact is subsequently reinitialized. STEPS TO REPRODUCE: 1stly, invoke the contextual menu of any subtask. 2ndly, invoke "Make this to-do independent". EXPECTED RESULT: Each separated subtask should instantly appear above or beneath the parental task. SOFTWARE/OS VERSIONS Windows: Whether affected is unknown. macOS: Whether affected is unknown. Linux/KDE Plasma: Affected. KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION I forgot to screenshot the window whilst this problem was present. Consequently, if it subsequently occurs, I shall provide pictography that depicts this problem. If this problem repetitively does not occur during subsequent separation, I shall file this report as "works-for-me" or remediated. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456076] Task Manager icons no longer honor panel margins, effectively making them bigger than intended
https://bugs.kde.org/show_bug.cgi?id=456076 --- Comment #10 from d7ghrr...@mozmail.com --- (In reply to Nate Graham from comment #9) > Task Manager Icons having a maximum size that's too low, or icons not > resizing smoothly, are different bugs. We will need additional bug reports > for those--one per issue. > > If you'd like to contribute to fixing these issues, great, feel free! Merge > requests can be submitted at > https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/. See > https://community.kde.org/Infrastructure/GitLab#Submitting_a_Merge_Request I'm sorry, I am not a developer. I just wish problem has been fixed and Task Manager behaves like before. Before update, I had panel with adjustable size and icons on Task Manager were scaling smoothly. Now, icons are fixed in size. Not scaling anymore, and too small to my preference. And no option to adjust icon size at all. Please resolve this issue, if possible, be reverting offending regression. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457773] Incorrect display of mounted ISO images in Dolphin
https://bugs.kde.org/show_bug.cgi?id=457773 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- Can reproduce with certain ISOs on Arch Linux running Dolphin 22.08 RC. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 455270] Line around floating panel after un-maximising a fullscreen window
https://bugs.kde.org/show_bug.cgi?id=455270 Celeste changed: What|Removed |Added CC||coelacant...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456076] Task Manager icons no longer honor panel margins, effectively making them bigger than intended
https://bugs.kde.org/show_bug.cgi?id=456076 --- Comment #9 from Nate Graham --- Task Manager Icons having a maximum size that's too low, or icons not resizing smoothly, are different bugs. We will need additional bug reports for those--one per issue. If you'd like to contribute to fixing these issues, great, feel free! Merge requests can be submitted at https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/. See https://community.kde.org/Infrastructure/GitLab#Submitting_a_Merge_Request -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456076] Task Manager icons no longer honor panel margins, effectively making them bigger than intended
https://bugs.kde.org/show_bug.cgi?id=456076 d7ghrr...@mozmail.com changed: What|Removed |Added CC||d7ghrr...@mozmail.com --- Comment #8 from d7ghrr...@mozmail.com --- I also would like to contribute to this problem. I use KDE with 4k monitor, and since upgrade, icons have become too small. Before, when I adjusted panel size, Task Manager icons would decrease/increase accordingly, scaling smoothly, perfectly for my needs. Now, icons are fixed in size, and too small for me. I use 4K monitor, vertical panel of 256 size, with Task Manager. Icons are too small. https://i.imgur.com/Mqd4ZrC.png Can you please restore smooth icon sizing functionality, or introduce setting in Task Manager so I can set icon size? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456076] Task Manager icons no longer honor panel margins, effectively making them bigger than intended
https://bugs.kde.org/show_bug.cgi?id=456076 Nate Graham changed: What|Removed |Added Summary|Size of icons backgrounds |Task Manager icons no |in Task Manager became |longer honor panel margins, |bigger in 5.25 |effectively making them ||bigger than intended -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456076] Size of icons backgrounds in Task Manager became bigger in 5.25
https://bugs.kde.org/show_bug.cgi?id=456076 Nate Graham changed: What|Removed |Added CC||niccolo.venera...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456076] Size of icons backgrounds in Task Manager became bigger in 5.25
https://bugs.kde.org/show_bug.cgi?id=456076 --- Comment #7 from Nate Graham --- Specifically, it looks like the icon is applying its own internal margin, but the Task Manager is completely ignoring the margin added by the panel, instead of fitting the icon box within it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456076] Size of icons backgrounds in Task Manager became bigger in 5.25
https://bugs.kde.org/show_bug.cgi?id=456076 --- Comment #6 from Nate Graham --- Ah, I think I may see the issue. App icons (well, most icons) internally have their own margins between the icon itself and the bounding box it lives in, and those should be preserved in addition to the margins that the Task Manager adds in code. Looks like that's not happening. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456076] Size of icons backgrounds in Task Manager became bigger in 5.25
https://bugs.kde.org/show_bug.cgi?id=456076 Nate Graham changed: What|Removed |Added Status|REOPENED|CONFIRMED Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456076] Size of icons backgrounds in Task Manager became bigger in 5.25
https://bugs.kde.org/show_bug.cgi?id=456076 Nate Graham changed: What|Removed |Added CC||loca...@tutanota.com --- Comment #5 from Nate Graham --- *** Bug 457379 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457379] Task Manager (not icons-only version ) icon size undesirably increased when widget is located on ≥ 40px thickness vertical panel
https://bugs.kde.org/show_bug.cgi?id=457379 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #15 from Nate Graham --- *** This bug has been marked as a duplicate of bug 456076 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456076] Size of icons backgrounds in Task Manager became bigger in 5.25
https://bugs.kde.org/show_bug.cgi?id=456076 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Resolution|INTENTIONAL |--- Status|RESOLVED|REOPENED --- Comment #4 from Nate Graham --- Re-opening since we're getting a lot of complaints about this, particularly for panels that are 38 or 40px in thickness or thicker (the exact value depends on the screen edge). In particular, at exactly 38 or 40px thickness, the icons are just enormous and nearly touch the edges of their bounding boxes. It just doesn't look good. This may conceptually be a tricky problem to solve though, since the change was intentional to allow the icons in Task Manager tasks to use the same margins as other panel widgets, so that all of the icons on your panel align. We'll need to see if we can resolve this visual issue without abandoning that effort. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 419591] "Configure" button is bigger than Weather Report widget added to desktop
https://bugs.kde.org/show_bug.cgi?id=419591 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kdeplasma-addons/-/merge_requests/216 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 457780] New: Konsole crashes on launch.
https://bugs.kde.org/show_bug.cgi?id=457780 Bug ID: 457780 Summary: Konsole crashes on launch. Product: konsole Version: 22.04.3 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: mcarpen...@smtcorp.com Target Milestone: --- Application: konsole (22.04.3) Qt Version: 5.15.5 Frameworks Version: 5.96.0 Operating System: Linux 5.15.0-46-generic x86_64 Windowing System: X11 Distribution: KDE neon User - 5.25 DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: Whern attempting to launch Konsole from any location, it crashes, this behavior persists across reboots, shutdowns and login/logout cycles. I noticed this started happening after an update, couldn't tell you the version jump. The crash can be reproduced every time. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault [New LWP 1389] [New LWP 1390] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f89c76ff99f in __GI___poll (fds=0x7fff332da9b8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 __preamble__ [Current thread is 1 (Thread 0x7f89c212f9c0 (LWP 1388))] Thread 3 (Thread 0x7f89c0954700 (LWP 1390)): #0 0x7f89c76ff99f in __GI___poll (fds=0x7f89b4004e60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f89c5c9b36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f89c5c9b4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f89c7cd25bb in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f89c7c7676b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f89c7a90372 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f89c6b27f4b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f89c7a91553 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f89c663b609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f89c770c133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f89c15be700 (LWP 1389)): #0 0x7f89c76ff99f in __GI___poll (fds=0x7f89c15bdae8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f89c588cc1a in ?? () from /lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f89c588e90a in xcb_wait_for_event () from /lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f89c1d0d3c8 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f89c7a91553 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f89c663b609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f89c770c133 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f89c212f9c0 (LWP 1388)): [KCrash Handler] #4 0x7f89c8862104 in QWidget::hide() () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #5 0x7f89c89d00ad in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #6 0x7f89c89d44f0 in QMenuBar::changeEvent(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #7 0x7f89c8879d14 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #8 0x7f89c89d461b in QMenuBar::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f89c8836e83 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #10 0x7f89c883fc98 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7f89c7c77c6a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f89c886a655 in QWidgetPrivate::updateFont(QFont const&) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f89c887a7cb in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f89c89d461b in QMenuBar::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7f89c8836e83 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f89c883fc98 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f89c7c77c6a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7f89c8894bf6 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f89c8894c2a in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f89c8894c91 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7f89c7caed50 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f89c813aea3 in QWindow::screenChanged(QScreen*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #23
[krita] [Bug 412849] Crash after deleting layers, resizing image and cropping on relatively large file
https://bugs.kde.org/show_bug.cgi?id=412849 Larpon changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 from Larpon --- Yes, sorry I couldn't provide any more details or crash logs at the time. I'm on Kubuntu 20.04 these days and happily using 5.0 now. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 449503] My Laptop in 'Panic State' when disengaged from the docking station/VGA port disconnected ... Laptop unusable, if 'Windows Effect' disabled laptop usable without the eye candy
https://bugs.kde.org/show_bug.cgi?id=449503 --- Comment #8 from Nate Graham --- It's not possible to know, as the changes have been too numerous, and this bug report is too vague to be actionable anyway. kwin-5.15 is completely ancient, it's almost 3 years old. Using old software that's been heavily patched with newer changes is just a recipe for sadness. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 457483] Screeching noise comes out of HDMI monitor when clicking the volume icon in system tray
https://bugs.kde.org/show_bug.cgi?id=457483 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #5 from Nate Graham --- If 3rd-party software can trigger it as well, it's an upstream elsewhere in the audio stack. I would recommend filing a bug report with pulseaudio or pipewire. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 416475] Display Configuration not saved properly on Wayland with multiple monitors
https://bugs.kde.org/show_bug.cgi?id=416475 Forrest Hilton changed: What|Removed |Added Ever confirmed|0 |1 Keywords||multiscreen, wayland CC||forrestmhil...@gmail.com Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 457765] "Copy" action in context menu always copies the path of the leaf node folder, not the path of the folder you right-clicked on
https://bugs.kde.org/show_bug.cgi?id=457765 Nate Graham changed: What|Removed |Added Assignee|dolphin-bugs-n...@kde.org |kio-bugs-n...@kde.org Status|REPORTED|CONFIRMED Severity|wishlist|normal Summary|The "Copy" option in|"Copy" action in context |context menu is ambiguous / |menu always copies the path |Add ability to copy partial |of the leaf node folder, |directory path |not the path of the folder ||you right-clicked on Component|bars: location |URL navigator Product|dolphin |frameworks-kio Ever confirmed|0 |1 CC||kdelibs-b...@kde.org Version|22.04.3 |5.96.0 --- Comment #3 from Nate Graham --- Ah, I get it now. It copies the full path, but the context implies that it would copy the past of the thing you right-clicked on. That's a totally reasonable thing to assume. I was confused because that's what I expected too! I can reproduce this in Gwenview too, which means it's a bug in the library component rather than in Dolphin. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457779] New: Kde Plasmashell Crashes Sometimes Unrecoverable by Reboot Even
https://bugs.kde.org/show_bug.cgi?id=457779 Bug ID: 457779 Summary: Kde Plasmashell Crashes Sometimes Unrecoverable by Reboot Even Product: plasmashell Version: 5.24.6 Platform: Manjaro OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: nssz4...@anonaddy.me Target Milestone: 1.0 SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE Random Crashes, worse in Wayland but sometimes in X11 OBSERVED RESULT Sometimes plasmashell (the application toolbar especially) will freeze and have to be restart with killall plasmashell && kstart5 plasmashell but if its given enough time it seems it will crash completely and need to be started with just kstart5 plasmashell. In Wayland this is so bad its almost unusable, in X11 it happens occasionally but it seems like some of the crashes appear to handle themselves and you can see plasmashell restart. Sometimes however if its bad enough kstart5 plasmashell wont even work and will only show $ killall plasmashell && kstart5 plasmashell Omitting both --window and --windowclass arguments is not recommended $ kf.plasma.quick: Applet preload policy set to 1 and not restart and often times even rebooting wont fix it and it just has to wait to process itself out EXPECTED RESULT No crashes, and better handling of crashes SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 ADDITIONAL INFORMATION I know linux well enough to get around but Im not a regular KDE debugger Ive installed Debuginfod like it says here in arch https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports, however I am not familar with how to use this tool for debugging and the page it links to https://wiki.archlinux.org/title/Debugging/Getting_traces seems like techno babble to me. Im not even sure if this program is for getting backtraces or if its used with other programs since its been described as "an HTTP file server that serves debugging resources to debugger-like tools" If someone guides me or gives me a more step by step guide on how to get useful backtraces for crashes for plasmashell that would be helpful. I am just a regular user that doesn't use debugging tools regularly. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 457777] Okular crashes after signing and reopening the document
https://bugs.kde.org/show_bug.cgi?id=45 Albert Astals Cid changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED CC||aa...@kde.org --- Comment #1 from Albert Astals Cid --- Tell your distro to update poppler to >= 22.07.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457740] When screens are arranged to be partially overlapping in KScreen KCM, main screen drawn over part of external monitor
https://bugs.kde.org/show_bug.cgi?id=457740 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED Version Fixed In||5.26 --- Comment #9 from Nate Graham --- Awesome, thanks so much for testing! It would seem that it's already fixed in Plasma 5.26, then. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457740] When screens are arranged to be partially overlapping in KScreen KCM, main screen drawn over part of external monitor
https://bugs.kde.org/show_bug.cgi?id=457740 --- Comment #8 from piotr.juzw...@pm.me --- HI Graham, I've tested it with the latest Unstable KDE Neon and I couldn't reproduce the same issue (besides having another issue with gpu but unrelated). -- You are receiving this mail because: You are watching all bug changes.
[kgeography] [Bug 132702] Questions should have sound confirmation
https://bugs.kde.org/show_bug.cgi?id=132702 --- Comment #5 from Albert Astals Cid --- Someone needs to create/find nice sounds for us to use -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 457778] New: Muting an incoming call incorrectly unmutes ringer
https://bugs.kde.org/show_bug.cgi?id=457778 Bug ID: 457778 Summary: Muting an incoming call incorrectly unmutes ringer Product: kdeconnect Version: unspecified Platform: Other OS: Android 11.x Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: em...@scgtrp.net Target Milestone: --- SUMMARY When receiving a call with the ringer muted, and clicking the button to mute the call on the PC side, the phone's ringer is unmuted after the call. STEPS TO REPRODUCE 1. Have ringer muted. 2. Receive call from obvious telemarketer. Click "mute call" in the PC-side notification. 3. Receive another call. OBSERVED RESULT The second call rings at maximum volume. EXPECTED RESULT The second call only vibrates, as that was what was set before the first call, and I did not intentionally change it. SOFTWARE/OS VERSIONS KDE Connect Linux: 22.04.3 KDE Connect Android: 1.19.1 ADDITIONAL INFORMATION Scrolling through the source (https://github.com/KDE/kdeconnect-android/blob/305a1d4c78b96e59a57fbe7c119a36cf754605a0/src/org/kde/kdeconnect/Plugins/TelephonyPlugin/TelephonyPlugin.java), I believe what's happening is: - At startup, the phone is muted, but `isMuted` is false (it is never set to `true` unless KDE Connect mutes the ringer itself). - First call comes in, `unmuteRinger()` is called unconditionally (:175), but does nothing because `isMuted` is false (:217). This is actually the correct behavior, but for the wrong reason. - I click the mute button. `muteRinger()` is called, it mutes the ringer (which was already muted) and sets `isMuted = true` (:236). - I don't answer the call, it gets rejected, `unmuteRinger()` is called (:197). This time, `isMuted` matches the actual mute state of the phone, so `unmuteRinger()` unmutes the ringer. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 457777] New: Okular crashes after signing and reopening the document
https://bugs.kde.org/show_bug.cgi?id=45 Bug ID: 45 Summary: Okular crashes after signing and reopening the document Product: okular Version: 22.04.3 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: davidruppre...@gmail.com Target Milestone: --- Application: okular (22.04.3) Qt Version: 5.15.5 Frameworks Version: 5.96.0 Operating System: Linux 5.13.0-22-generic x86_64 Windowing System: X11 Distribution: KDE neon User - 5.25 DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: When signing a document with the sign function okular crashes also reopening the signed file crashes okular. The crash can be reproduced every time. -- Backtrace: Application: Okular (okular), signal: Aborted [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #5 0x7f0f01003859 in __GI_abort () at abort.c:79 #6 0x7f0f01274a31 in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #7 0x7f0f012805dc in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #8 0x7f0f01280647 in std::terminate() () from /lib/x86_64-linux-gnu/libstdc++.so.6 #9 0x7f0f012808e9 in __cxa_throw () from /lib/x86_64-linux-gnu/libstdc++.so.6 #10 0x7f0f012772c3 in std::__throw_logic_error(char const*) () from /lib/x86_64-linux-gnu/libstdc++.so.6 #11 0x7f0ee02c45ab in std::__cxx11::basic_string, std::allocator >::_M_construct (this=this@entry=0x7ffcf209fe30, __beg=__beg@entry=0x0, __end=0x ) at /usr/include/c++/9/bits/basic_string.tcc:212 #12 0x7f0ee0447855 in std::__cxx11::basic_string, std::allocator >::_M_construct_aux (__end=, __beg=0x0, this=0x7ffcf209fe30) at /usr/include/c++/9/bits/basic_string.h:247 #13 std::__cxx11::basic_string, std::allocator >::_M_construct (__end=, __beg=0x0, this=0x7ffcf209fe30) at /usr/include/c++/9/bits/basic_string.h:270 #14 std::__cxx11::basic_string, std::allocator >::basic_string > (__a=..., __s=0x0, this=0x7ffcf209fe30) at /usr/include/c++/9/bits/basic_string.h:531 #15 SignatureHandler::getSignerName[abi:cxx11]() (this=this@entry=0x7ffcf209fee0) at ./poppler/SignatureHandler.cc:541 #16 0x7f0ee031833c in FormFieldSignature::validateSignature (forceRevalidation=, enableAIA=false, ocspRevocationCheck=true, validationTime=-1, doVerifyCert=true, this=0x560d8adee9a0) at ./poppler/Form.cc:2334 #17 FormFieldSignature::validateSignature (this=0x560d8adee9a0, doVerifyCert=, forceRevalidation=, validationTime=-1, ocspRevocationCheck=, enableAIA=) at ./poppler/Form.cc:2284 #18 0x7f0ee05bf0f8 in Poppler::FormFieldSignature::validate (this=this@entry=0x560d8ae62860, opt=opt@entry=1, validationTime=...) at ./qt5/src/poppler-form.cc:1008 #19 0x7f0ee05bf654 in Poppler::FormFieldSignature::validate (this=0x560d8ae62860, opt=Poppler::FormFieldSignature::ValidateVerifyCertificate) at ./qt5/src/poppler-form.cc:958 #20 0x7f0ee80a4333 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/okular/generators/okularGenerator_poppler.so #21 0x7f0ee8099976 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/okular/generators/okularGenerator_poppler.so #22 0x7f0ee809dace in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/okular/generators/okularGenerator_poppler.so #23 0x7f0ee809df35 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/okular/generators/okularGenerator_poppler.so #24 0x7f0ee809e2d2 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/okular/generators/okularGenerator_poppler.so #25 0x7f0ef5c2f2e8 in ?? () from /lib/x86_64-linux-gnu/libOkular5Core.so.10 #26 0x7f0ef5c2f9e3 in Okular::Document::openDocument(QString const&, QUrl const&, QMimeType const&, QString const&) () from /lib/x86_64-linux-gnu/libOkular5Core.so.10 #27 0x7f0ef5d9c195 in Okular::Part::doOpenFile (this=this@entry=0x560d8a332610, mimeA=..., fileNameToOpenA=..., isCompressedFile=isCompressedFile@entry=0x7ffcf20a0727) at ./part/part.cpp:1457 #28 0x7f0ef5d9d151 in Okular::Part::openFile (this=0x560d8a332610) at ./part/part.cpp:1582 #29 0x7f0f02ee9cb4 in KParts::ReadOnlyPartPrivate::openLocalFile (this=this@entry=0x560d8a33afd0) at ./src/readonlypart.cpp:180 #30 0x7f0f02eeadfe in KParts::ReadOnlyPart::openUrl (this=this@entry=0x560d8a332610, url=...) at ./src/readonlypart.cpp:141 #31 0x7f0ef5d8cc4b in Okular::Part::openUrl (this=, _url=..., swapInsteadOfOpening=) at ./part/part.cpp:1808 #32 0x560d8937cf73 in Shell::openUrl (this=0x560d8a31cc50, url=..., serializedOptions=...) at ./shell/shell.cpp:319 #33 0x560d8937d2ae in Shell::openDocument (this=0x560d8a31cc50, url=..., serializedOptions=...) at ./shell/shell.cpp:265 #34 0x560d89373f60 in Okular::main (paths=..., serializedOptions=...) at ./shell/okular_main.cpp:193 #35
[lattedock] [Bug 456094] Random crash when interacting with the dock
https://bugs.kde.org/show_bug.cgi?id=456094 --- Comment #4 from ryu.ketsu...@outlook.com --- When should I expect the next version of Plasma with this fix? -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 455012] With a large number of tabs open, the browser starts slowly
https://bugs.kde.org/show_bug.cgi?id=455012 Juraj changed: What|Removed |Added CC||jurajora...@mailo.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Juraj --- Can confirm. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425315] Auto-started apps with system tray icons don't always show their tray icons after reboot when they launch before plasmashell is finished launching
https://bugs.kde.org/show_bug.cgi?id=425315 Ilya Fedin changed: What|Removed |Added CC||fedin-ilja2...@ya.ru --- Comment #52 from Ilya Fedin --- TL;DR Qt's architecture is complicated in order to fallback to XEMBED when SNI is not available, since it's an architectural issue in Qt, it may be they never would fix the architecture to allow switching the backends on the fly (as needs a lot of work). Since they don't switch on the fly, the effect is if SNI host is started after application is started, the tray icon is blurry on X11 and doesn't show at all on Wayland (as there's nowhere to fallback). As Discord is mentioned in this bug, it may be that Electron has a similar issue. So it may be way easier to ensure that applications are started after all services like SNI host, global menu service, xsettingsd (Qt reads XSETTINGS and doesn't handle when it appears after Qt initialization, just like with SNI/global menu), kwin (https://bugreports.qt.io/browse/QTBUG-95338) and etc, rather than fixing all bugs in all toolkits. That's where Qt decides to use SNI or not: https://github.com/qt/qtbase/blob/a8e6a0e546a6a90ff2daee79c3cf504b7160cb86/src/gui/platform/unix/qgenericunixthemes.cpp#L71-L101 It's called by createPlatformSystemTrayIcon() down this file. If it's not available, it returns nullptr. Every other platform has built-in platformtheme and has windowing system-based tray backend returned by createPlatformSystemTrayIcon() therefore. But X11 is different. They replace entire private QSystemTrayIcon class implementation for it: https://github.com/qt/qtbase/blob/a8e6a0e546a6a90ff2daee79c3cf504b7160cb86/src/widgets/CMakeLists.txt#L825-L833 So it tries to call createPlatformSystemTrayIcon() and creates X11 window right in the private class: https://github.com/qt/qtbase/blob/a8e6a0e546a6a90ff2daee79c3cf504b7160cb86/src/widgets/util/qsystemtrayicon_x11.cpp#L186-L217 -- You are receiving this mail because: You are watching all bug changes.
[Spam] [Bug 457774] Stream and Activate Paramount Plus on Firestick and Apple TV
https://bugs.kde.org/show_bug.cgi?id=457774 Nicolas Fella changed: What|Removed |Added URL|https://easytoactivate.com/ | |activate-paramount-plus/| Product|Active Window Control |Spam Assignee|zrenf...@gmail.com |n...@kde.org CC||nicolas.fe...@gmx.de Component|General |Spam -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457740] When screens are arranged to be partially overlapping in KScreen KCM, main screen drawn over part of external monitor
https://bugs.kde.org/show_bug.cgi?id=457740 --- Comment #7 from piotr.juzw...@pm.me --- I've added two versions from kscreen folder where I noticed a difference. I've saved both config files before and after change to compare. Please let me know what kind of other information you'd like me to get. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457740] When screens are arranged to be partially overlapping in KScreen KCM, main screen drawn over part of external monitor
https://bugs.kde.org/show_bug.cgi?id=457740 --- Comment #6 from piotr.juzw...@pm.me --- Created attachment 151267 --> https://bugs.kde.org/attachment.cgi?id=151267=edit Config after change -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457740] When screens are arranged to be partially overlapping in KScreen KCM, main screen drawn over part of external monitor
https://bugs.kde.org/show_bug.cgi?id=457740 --- Comment #5 from piotr.juzw...@pm.me --- Created attachment 151266 --> https://bugs.kde.org/attachment.cgi?id=151266=edit Config before change -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 457776] New: Global actions/shortcuts do not work after language change
https://bugs.kde.org/show_bug.cgi?id=457776 Bug ID: 457776 Summary: Global actions/shortcuts do not work after language change Product: frameworks-kglobalaccel Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: empyr...@ukr.net Target Milestone: --- SUMMARY Global actions/shortcuts in System Settings - Shortcuts - Media Controller work only when EN language is selected. STEPS TO REPRODUCE 1. Assign Global Shortcuts in System Settings - Shortcuts with EN layout. 2. Choose any language with non-latin layout and shortcuts stop working. OBSERVED RESULT Shortcuts work only in language used to assign them. EXPECTED RESULT Global shortcuts should not depend on keyboard layout. SOFTWARE/OS VERSIONS Operating System: Kubuntu 22.10 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.4 Kernel Version: 5.15.0-46-generic (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425315] Auto-started apps with system tray icons don't always show their tray icons after reboot when they launch before plasmashell is finished launching
https://bugs.kde.org/show_bug.cgi?id=425315 Pawel changed: What|Removed |Added CC||bednarczyk.pa...@outlook.co ||m -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 457750] Discover: Päivitys valittu -> Päivitä valitut
https://bugs.kde.org/show_bug.cgi?id=457750 --- Comment #2 from Lasse Liehu --- Thanks for the report! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 457775] Effects are not working and some are not seen in the effects menu
https://bugs.kde.org/show_bug.cgi?id=457775 sabadia...@gmail.com changed: What|Removed |Added CC||sabadia...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 457775] New: Effects are not working and some are not seen in the effects menu
https://bugs.kde.org/show_bug.cgi?id=457775 Bug ID: 457775 Summary: Effects are not working and some are not seen in the effects menu Product: kde Version: unspecified Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: sabadia...@gmail.com Target Milestone: --- Created attachment 151265 --> https://bugs.kde.org/attachment.cgi?id=151265=edit Available Effects SUMMARY *** I've installed Kubuntu on my new PC and everything but the effects seems to work. KDE effects like squash and wobbly windows are not appearing in the menu. I tried to install some effects from "Get New Desktop Effects" and installed "successfully" but I cannot see them in the menu as well. Also, Virtual Desktop effects are not working. *** STEPS TO REPRODUCE 1. Go to System Settings -> Workspace -> Workspace Behavior -> Desktop Effects 2. Look at the menu and see the missing effects OBSERVED RESULT No effects are working or appearing. EXPECTED RESULT All desired effects working. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Tried to install all updates and reboot. Everything else works perfectly so far (fresh install) -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 457750] Discover: Päivitys valittu -> Päivitä valitut
https://bugs.kde.org/show_bug.cgi?id=457750 Unknown changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Unknown --- SVN commit 1631025 by lliehu: Fix and update Finnish translation of Plasma Discover M +146 -61 libdiscover.po M +137 -49 plasma-discover.po WebSVN link: http://websvn.kde.org/?view=rev=1631025 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 309193] Keyboard shortcuts doesn't work if non-english keyboard layout is set before english one
https://bugs.kde.org/show_bug.cgi?id=309193 Nate Graham changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 309193] Keyboard shortcuts doesn't work if non-english keyboard layout is set before english one
https://bugs.kde.org/show_bug.cgi?id=309193 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #78 from Nate Graham --- That sounds like a different issue. Please file a new bug report. -- You are receiving this mail because: You are watching all bug changes.
