[kdeconnect] [Bug 422692] show more useful hover text (e.g. what device is currently connected)
https://bugs.kde.org/show_bug.cgi?id=422692 --- Comment #3 from kofler.max@gmail.com --- Yes, infact, I found a possibility to override this(I knew some plasmoids could do that, but I had to spend a whole day of research to finally find the function) , I am currently still working on reading things like battery information from within KDE-Connect. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 435120] Data protection: Removing or editing annotation metadata (author, date, time) should be possible
https://bugs.kde.org/show_bug.cgi?id=435120 --- Comment #18 from Rainer Klute --- (In reply to Albert Astals Cid from comment #17) You are right, the GDPR does not apply to a certain piece of software as such, but rather to a “controller”, i. e., “the natural or legal person, public authority, agency or other body which, alone or jointly with others, determines the purposes and means of the processing of personal data” (Article 4 (7) GDPR). Okular is such a possible “means of the processing of personal data”. A controller who has to stick to the GDPR may only deploy software that allows him to process personal data in a GDPR-compliant way. I’d appreciate if Okular would give him that possibility. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435179] face write to database with wrong user (''@'%') MariaDB backend
https://bugs.kde.org/show_bug.cgi?id=435179 --- Comment #17 from Maik Qualmann --- We have the problem that the users of the triggers are "@%". It should something like "gessel@%". You have probably GRANT the database after creating the database or deleted a user in the meantime. Try this: GRANT TRIGGER ON .* TO ''@'localhost'; Maik -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 434828] Shape Fill gradient colors changing to stroke gradient color
https://bugs.kde.org/show_bug.cgi?id=434828 Dmitry Kazakov changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/1fffa7e33 ||fb5581e2f379dc77101aa712830 ||bc01 Status|ASSIGNED|RESOLVED --- Comment #3 from Dmitry Kazakov --- Git commit 1fffa7e33fb5581e2f379dc77101aa712830bc01 by Dmitry Kazakov, on behalf of Sharaf Zaman. Committed on 01/04/2021 at 05:48. Pushed by dkazakov into branch 'master'. Bugfix: Inconsistent stroke fill and shape fill Problem: Embedding KoFillConfigWidget in KoStrokeConfigWidget created codepaths which KisAcyclicSignalConnector doesn't block, which resulted in an inconsistent behavior when both strokes and fill were used in a shape. Solution: By default if we hadn't embedded the widgets, signals from ResourceManager would've been blocked by KisAcyclicSignalConnector when we entered slotProposeCurrentColorToResourceManager. Since we don't, we have to manually block events when we are in this method. Related: bug 399127, bug 422204 M +8-0libs/ui/widgets/KoFillConfigWidget.cpp https://invent.kde.org/graphics/krita/commit/1fffa7e33fb5581e2f379dc77101aa712830bc01 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399127] Vector object fills itself when gradient stroke is selected in tool settings
https://bugs.kde.org/show_bug.cgi?id=399127 Dmitry Kazakov changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/1fffa7e33 ||fb5581e2f379dc77101aa712830 ||bc01 --- Comment #12 from Dmitry Kazakov --- Git commit 1fffa7e33fb5581e2f379dc77101aa712830bc01 by Dmitry Kazakov, on behalf of Sharaf Zaman. Committed on 01/04/2021 at 05:48. Pushed by dkazakov into branch 'master'. Bugfix: Inconsistent stroke fill and shape fill Problem: Embedding KoFillConfigWidget in KoStrokeConfigWidget created codepaths which KisAcyclicSignalConnector doesn't block, which resulted in an inconsistent behavior when both strokes and fill were used in a shape. Solution: By default if we hadn't embedded the widgets, signals from ResourceManager would've been blocked by KisAcyclicSignalConnector when we entered slotProposeCurrentColorToResourceManager. Since we don't, we have to manually block events when we are in this method. Related: bug 422204, bug 434828 M +8-0libs/ui/widgets/KoFillConfigWidget.cpp https://invent.kde.org/graphics/krita/commit/1fffa7e33fb5581e2f379dc77101aa712830bc01 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422204] Strokes with gradients mess up the fill colors
https://bugs.kde.org/show_bug.cgi?id=422204 Dmitry Kazakov changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/1fffa7e33 ||fb5581e2f379dc77101aa712830 ||bc01 Status|ASSIGNED|RESOLVED --- Comment #3 from Dmitry Kazakov --- Git commit 1fffa7e33fb5581e2f379dc77101aa712830bc01 by Dmitry Kazakov, on behalf of Sharaf Zaman. Committed on 01/04/2021 at 05:48. Pushed by dkazakov into branch 'master'. Bugfix: Inconsistent stroke fill and shape fill Problem: Embedding KoFillConfigWidget in KoStrokeConfigWidget created codepaths which KisAcyclicSignalConnector doesn't block, which resulted in an inconsistent behavior when both strokes and fill were used in a shape. Solution: By default if we hadn't embedded the widgets, signals from ResourceManager would've been blocked by KisAcyclicSignalConnector when we entered slotProposeCurrentColorToResourceManager. Since we don't, we have to manually block events when we are in this method. Related: bug 399127, bug 434828 M +8-0libs/ui/widgets/KoFillConfigWidget.cpp https://invent.kde.org/graphics/krita/commit/1fffa7e33fb5581e2f379dc77101aa712830bc01 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433854] A lot of times copy-paste does not work.
https://bugs.kde.org/show_bug.cgi?id=433854 tagwer...@innerjoin.org changed: What|Removed |Added CC||tagwer...@innerjoin.org --- Comment #7 from tagwer...@innerjoin.org --- I don't know if I see the same thing but I've noticed copy and paste with Firefox (and Thunderbird) being "definitely obstinate" I can highlight the text and "copy" and see the text in Klipper but I am not always able to paste. Typically I see the issue if trying to paste a link from Firefox into an email being written in Thunderbird. I find I have somewhat more success if I "Paste without Formatting". My workround has been to "Clear History", go back to the text and copy it again. Both can help - but neither are guaranteed There's also a thread here that seems to make sense https://old.reddit.com/r/kdeneon/comments/mgybdr/firefox_and_the_clipboard/ For me this is with X (within KVM guests and from one KVM guest to another) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435202] Newly imported images do not show in database
https://bugs.kde.org/show_bug.cgi?id=435202 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- If you select the album into which you have just imported images, will "hidden files" be displayed in the status bar at the bottom? Maik -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 435207] New: Grouping by tags does not show the title over the first group when navigating back into the user home folder
https://bugs.kde.org/show_bug.cgi?id=435207 Bug ID: 435207 Summary: Grouping by tags does not show the title over the first group when navigating back into the user home folder Product: dolphin Version: 20.12.2 Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: nilslindem...@tutanota.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY See title. STEPS TO REPRODUCE 1. Open Dolphin 2. Go to /home/ (it works in sub folders) 3. give some folders tags 4. Group by tags (the tags are now visible as group titles) 5. Navigate into a child folder 6. Navigate back OBSERVED RESULT The first group title is now gone in the home folder level, the others are still there. EXPECTED RESULT All group titles are visible in the home folder level. OS: Fedora KDE KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.79.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION Observing this on Fedora KDE and on Kubuntu. When – after the group title has gone – I disable and then re-enable grouping, then the title will be there again. Comments and star ratings do not produce the error on Fedora, but if I remember right, they did on Kubuntu, which I had installed before. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 407192] Filesystems created by Partition manager are owned by root
https://bugs.kde.org/show_bug.cgi?id=407192 --- Comment #30 from PK --- As I understand the fact that ext4 links owner-rights to all files stands in the way of making a writabel-for-all usb-stick. The methode of Ianp (comment 29) could very well be a way out. But I can imagine that there are also users who are not member of de "admin" group. Perhaps it would be smarter to choose a group all users are a member of. If such a group exists. That could be the way out, making the content of a medium be owned by a group everybody is a member of... -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 428022] ksmserver-logout-greeter crashing on logout
https://bugs.kde.org/show_bug.cgi?id=428022 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- 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.
[akregator] [Bug 390682] Keyboard shortcuts does not work properly
https://bugs.kde.org/show_bug.cgi?id=390682 --- Comment #4 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.
[krita] [Bug 433866] Krita GUI Main Window disappears after Krita is initiated and finishes 'Loading Main Window'. This condition arose after I did a Microsoft Windows Updates.
https://bugs.kde.org/show_bug.cgi?id=433866 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- 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.
[plasmashell] [Bug 433862] Start menu crashes whenever searching for apostrophe '
https://bugs.kde.org/show_bug.cgi?id=433862 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- 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.
[plasmashell] [Bug 424371] Plasma crashed when moving window to another desktop
https://bugs.kde.org/show_bug.cgi?id=424371 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |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 393704] exiting fullscreen does not work the first time.
https://bugs.kde.org/show_bug.cgi?id=393704 --- Comment #7 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.
[kdenlive] [Bug 414412] Kdenlive is broken on latest version of windows
https://bugs.kde.org/show_bug.cgi?id=414412 --- Comment #4 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.
[plasma-pa] [Bug 433712] Volume control keys not incrementing and decrementing volume percentage as expected
https://bugs.kde.org/show_bug.cgi?id=433712 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.
[kwin] [Bug 433854] A lot of times copy-paste does not work.
https://bugs.kde.org/show_bug.cgi?id=433854 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 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.
[plasmashell] [Bug 423764] Crash when switching audio output
https://bugs.kde.org/show_bug.cgi?id=423764 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|BACKTRACE |WORKSFORME --- 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 419833] Color Smudge Brush treats the space outside of the canvas as transparency
https://bugs.kde.org/show_bug.cgi?id=419833 --- Comment #6 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.
[krita] [Bug 430809] There is a bug whose resolution goes down from 300 to 299 when you save the picture after changing it to cmyk.
https://bugs.kde.org/show_bug.cgi?id=430809 --- 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.
[systemsettings] [Bug 434528] Plasma firewall module crashed when opened twice
https://bugs.kde.org/show_bug.cgi?id=434528 --- 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.
[kdenlive] [Bug 419513] a fade out doesn't work
https://bugs.kde.org/show_bug.cgi?id=419513 --- 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.
[kdenlive] [Bug 388385] Rendering as parts: lost frames
https://bugs.kde.org/show_bug.cgi?id=388385 --- 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.
[kdenlive] [Bug 415552] clip to timeline
https://bugs.kde.org/show_bug.cgi?id=415552 --- 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.
[krita] [Bug 412062] Empty swatches in palette are replaced by black on reloading krita.
https://bugs.kde.org/show_bug.cgi?id=412062 --- 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.
[krita] [Bug 419399] Laggy interface with kinetic scrolling and canvas and UI glitches.
https://bugs.kde.org/show_bug.cgi?id=419399 --- 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.
[akregator] [Bug 391372] Articles columns are not remembered
https://bugs.kde.org/show_bug.cgi?id=391372 --- Comment #4 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.
[kdenlive] [Bug 379613] Folder Navigation Problem in Kdenlive on Windows 7
https://bugs.kde.org/show_bug.cgi?id=379613 --- 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.
[akregator] [Bug 322602] Feeds do not update although I'm online
https://bugs.kde.org/show_bug.cgi?id=322602 --- 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.
[Bluedevil] [Bug 432715] REGRESSION: Paired PlayStation Dualshock 3 Wireless Controller does not appear in Bluetooth tray
https://bugs.kde.org/show_bug.cgi?id=432715 Leroy G changed: What|Removed |Added Summary|Paired PlayStation |REGRESSION: Paired |Dualshock 3 Wireless|PlayStation Dualshock 3 |Controller does not appear |Wireless Controller does |in Bluetooth tray |not appear in Bluetooth ||tray -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 432715] Paired PlayStation Dualshock 3 Wireless Controller does not appear in Bluetooth tray
https://bugs.kde.org/show_bug.cgi?id=432715 Leroy G changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #4 from Leroy G --- Tested with Kubuntu 20.10 which has plasma 5.19.5 and this bug doesn't happen there, so indeed the bug was introduced in Plasma 5.20 and it's also indeed a regression. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 435206] New: Title clips become green and enlarged, see attachment.
https://bugs.kde.org/show_bug.cgi?id=435206 Bug ID: 435206 Summary: Title clips become green and enlarged, see attachment. Product: kdenlive Version: 20.12.3 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: h...@huaonline.com Target Milestone: --- Created attachment 137219 --> https://bugs.kde.org/attachment.cgi?id=137219=edit Project has been minimized. Parts might be missing. SUMMARY Title clips become green and enlarged, see attachment greenTitle.mp4. It's shown perfectly in preview. But it's messed up after render. STEPS TO REPRODUCE 1. Open the attached project (which has been minimized for the purpose). 2. Verify in preview. 3. Run render (MP4 H264) 4. Verify the video. OBSERVED RESULT See attached greenTitle.mp4 EXPECTED RESULT As shown in preview. SOFTWARE/OS VERSIONS Windows: 10 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.
[systemsettings] [Bug 432818] Use libxkbregistry to parse the rules files
https://bugs.kde.org/show_bug.cgi?id=432818 andydecle...@gmail.com changed: What|Removed |Added CC||andydecle...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 435157] yr.no does not work anymore with meteo widget
https://bugs.kde.org/show_bug.cgi?id=435157 Nate Graham changed: What|Removed |Added Resolution|WAITINGFORINFO |DOWNSTREAM Status|NEEDSINFO |RESOLVED --- Comment #8 from Nate Graham --- Ah, I see. This is in fact not a KDE widget but rather a 3rd-party one. Looks like it's https://store.kde.org/p/998917/. You'll want to report this to the developer of that widget. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433576] keyboard configurations with single layout are broken on Wayland
https://bugs.kde.org/show_bug.cgi?id=433576 --- Comment #28 from Nate Graham --- *** Bug 433265 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433265] XKB options set in the Keyboard KCM sometimes stop working on Wayland
https://bugs.kde.org/show_bug.cgi?id=433265 Nate Graham changed: What|Removed |Added Resolution|FIXED |DUPLICATE --- Comment #18 from Nate Graham --- No worries. *** This bug has been marked as a duplicate of bug 433576 *** -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 433158] Different menu item height between breeze and breeze-gtk
https://bugs.kde.org/show_bug.cgi?id=433158 --- Comment #16 from Nate Graham --- You can check out the last commit that attempted to fix it: https://invent.kde.org/plasma/breeze-gtk/commit/7be4c04e4dca2ba61b5822d8d50b7d3ee3a87702 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 30481] Ability to customise the keyboard layout
https://bugs.kde.org/show_bug.cgi?id=30481 Nate Graham changed: What|Removed |Added Depends on|432818 | See Also||https://bugs.kde.org/show_b ||ug.cgi?id=432818 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=432818 [Bug 432818] Use libxkbregistry to parse the rules files -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432818] Use libxkbregistry to parse the rules files
https://bugs.kde.org/show_bug.cgi?id=432818 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=30481 Blocks|30481 | --- Comment #2 from Nate Graham --- Ah yeah, I suppose that could be wrapped in a GUI to avoid having to use XKB at all. Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=30481 [Bug 30481] Ability to customise the keyboard layout -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 30481] Ability to customise the keyboard layout
https://bugs.kde.org/show_bug.cgi?id=30481 andydecle...@gmail.com changed: What|Removed |Added CC||andydecle...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432750] No generic way to re-map keys on Wayland
https://bugs.kde.org/show_bug.cgi?id=432750 andydecle...@gmail.com changed: What|Removed |Added CC||andydecle...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 435167] IPv6: file browsing freezes on IPv4/IPv6 hydrid network due to nonsensical address passed to ssh
https://bugs.kde.org/show_bug.cgi?id=435167 --- Comment #5 from Thiago Macieira --- (In reply to 2wxsy58236r3 from comment #4) > My network is also IPv4/IPv6 hybrid, and it seems that if I unpair and pair > the devices again, and then browse the device via Dolphin, IPv6 will be used. > > But after a period of time, it will fallback to IPv4 again. It seems that > IPv4 is preferred most of the times. That's not good. The selection should be deterministic, preferably using established RFCs (3484 and 6724 come to mind, but I don't think they are correct for this purpose). Since they are always intra-network (link-local) addresses, I suppose we should prefer the local addresses to avoid accidentally trafficking over routers and over the Internet, in which case the order should be: 1) IPv6 link-local addresses, if possible (fe80::/64) - not always possible because they need a scope identifier in the address and some tools will not like that 2) IPv4 link-local addresses (169.254.0.0/16) 3) IPv6 realm-local addresses (you can probably ignore this) 4) IPv6 site-local addresses (fec0::/8 [deprecated], you can probably ignore this) 5) IPv6 unique local addresses (fc00::/7) 6) IPv4 addresses reserved by RFC 1918 and 6598 (10.0.0.0/8, 100.64.0.0/10, 172.16.0.0/12, 192.168.0.0/16) 7) IPv6 global addresses 8) IPv4 global addresses Or, alternatively speaking, sort addresses by ascending scope by grouping the IPv6 local addresses with IPv4 private-use and shared-use ones, and IPv6 preferred over IPv4 in each scope. See https://www.iana.org/assignments/ipv6-multicast-addresses/ipv6-multicast-addresses.xml#ipv6-scope for the full list. IPv6 v4-compat (::/96), Teredo (2001:0::/32) and 6to4 (2002::/16) addresses should be excluded. IPv6 v4-mapped addresses (:::0.0.0.0/32) should be treated like IPv4. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435190] plasmashell crash on Wayland when opening Thunderbird blog entry
https://bugs.kde.org/show_bug.cgi?id=435190 Alex changed: What|Removed |Added Status|REPORTED|CONFIRMED Component|general |generic-crash CC||alex...@protonmail.com Ever confirmed|0 |1 --- Comment #1 from Alex --- Can confirm on Fedora 34, same Qt, Frameworks, and Plasma versions as OP. Make sure to double-click the blog entry to bring it up, merely single-clicking to select it wasn't enough to generate a crash. I think you need to make sure it's the same blog entry, the one ending in 9e9c15d2, but I could be wrong about that. I'm not sure what I could get a backtrace of, because plasmashell thinks kwin is dead, when kwin isn't dead. drkonqi attempts to start, but fails for whatever reason, so I can't currently show a plasmashell backtrace. Some help diagnosing this would be appreciated... Additionally, I'm unable to reproduce this on my Neon Unstable VM. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 435031] Breeze Light Colour Scheme does not respect Colour Scheme KCM values
https://bugs.kde.org/show_bug.cgi?id=435031 --- Comment #5 from Paul McAuley --- Created attachment 137218 --> https://bugs.kde.org/attachment.cgi?id=137218=edit kdeglobals file corresponding to screenshot -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 435031] Breeze Light Colour Scheme does not respect Colour Scheme KCM values
https://bugs.kde.org/show_bug.cgi?id=435031 --- Comment #4 from Paul McAuley --- Created attachment 137217 --> https://bugs.kde.org/attachment.cgi?id=137217=edit Breze Light with inactive window on left and active window on right -- both have the same titlebar text colour, despite settings -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 434423] Digikam displaying incorrect lens info in 'Properties - Photograph Properties'
https://bugs.kde.org/show_bug.cgi?id=434423 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Version|7.1.0 |7.2.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435205] No ability to set scroll wheel parameters in system settings
https://bugs.kde.org/show_bug.cgi?id=435205 Jorn_Haga changed: What|Removed |Added CC||bjornlasan...@tuta.io -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435205] New: No ability to set scroll wheel parameters in system settings
https://bugs.kde.org/show_bug.cgi?id=435205 Bug ID: 435205 Summary: No ability to set scroll wheel parameters in system settings Product: systemsettings Version: 5.18.6 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: kcm_mouse Assignee: plasma-b...@kde.org Reporter: bjornlasan...@tuta.io Target Milestone: --- Created attachment 137216 --> https://bugs.kde.org/attachment.cgi?id=137216=edit screenshot showing mouse settings has no additional tabs as per the Mouse Help doc When using my mouse for editing documents as well as Audio production, the use of the scroll wheel is imperative as is the means to adjust its settings. The current ability to adjust the settings of the scroll wheel, as well as other settings of the mouse's functions are simply not there. The help documentation says they are, but enclosed is a screenshot showing that there are no separate tabs as per the help documentation for mouse settings. The only scroll wheel setting is to invert the scroll which is unsatisfactory. When scroll wheel is used now the movement jumps on average 3/4-2-1/2 pages depending on the zoom level. The zoom level is tied to the setting of the scroll wheel movement so why is it removed? STEPS TO REPRODUCE 1. Application Launcher/System Settings/Hardware/Input Devices/Mouse 2. Type System Settings in upper box in Application Launcher then Hardware/Input Devices/Mouse 3. Open Yast Repeat above to get to same place. OBSERVED RESULT The following settings are missing: Pointer threshold Double click interval Drag start time and Drag start distance Mouse wheel scrolls by(This is HUGE omission as it affects many other input options, zoom for one. Hitting Ctrl+scroll wheel I get options of maybe one two two huge visually words on the screen, or so small I cannot determine what the words are unless having a magnifying glass in hand and this is on a 4k 42" flat screen.) All potential settings under Keyboard Navigation in the Mouse Help doc. Clicking on the touchpad tab does bring up a window which allows one to test scroll function, but all ability to change settings are non-functional and greyed out. Several settings dealing with the mouse are in the Windows Behavior section of the System Settings under General Behavior and Windows Effects, but none pertain to the issue at hand. EXPECTED RESULT The ability to not have to hunt for settings that are necessary. If a feature is removed, remove it out of the documentation as well BEFORE implementing the change. While I am sure I can dig into the library files and locate the settings and change them myself to my liking, why should I have to? Not all Linux users are coders, nor should they be expected to be for simple I/O concerns. This is not due to the installment on any application outside the main OS. These are internal settings that are just gone. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 15.2 OpenSUSE Leap (available in About System) KDE Plasma Version: 5.18.6 KDE Frameworks Version: 5.71.0 Qt Version: 5.12.7 ADDITIONAL INFORMATION These functions need to be able to be set to fine detail for audio work. I am talking pixel size movement settings. I make money editing audio for a portion of my income and the way the scroll settings are now is a deal breaker. Is there a way to manually set the GPM in the meantime? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 434423] Digikam displaying incorrect lens info in 'Properties - Photograph Properties'
https://bugs.kde.org/show_bug.cgi?id=434423 --- Comment #5 from John O --- Hello, as a follow up I tested a few of the weekly snapshots, and have since installed the 7.2 final release, and the same issue remains. I can't find any rhyme or reason, certain images display the correct lens info, and others display the incorrect lens info. In some albums, its only a few pics that are incorrect, in other albums, the entire album is incorrect. Many show lenses I don't even own and have never shot with. I've tested on two systems and the result is the same. I've deleted my Collections, and let Digikam re-scan my entire collection to see if that resolves the issue, it does not. Both RAW and JPG are still inconsistent. Other software such as Gwenview still displays the correct lens information. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 435204] Krita 4.4.4 wont's save file(happens at random)
https://bugs.kde.org/show_bug.cgi?id=435204 Tiar changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||tamtamy.tym...@gmail.com --- Comment #1 from Tiar --- Can you please attach the content of Help -> Show Krita log for bug reports? And please do tell how was your work (the one you lost progress in) called. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 435204] New: Krita 4.4.4 wont's save file(happens at random)
https://bugs.kde.org/show_bug.cgi?id=435204 Bug ID: 435204 Summary: Krita 4.4.4 wont's save file(happens at random) Product: krita Version: git master (please specify the git hash!) Platform: Other OS: Microsoft Windows Status: REPORTED Severity: grave Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: tgdev...@gmail.com Target Milestone: --- SUMMARY I'm bitterly reporting that thanks to Krita being somewhere unstable, it wiped of my long work progress today. At random, the program won't dare save progress. And when it happens, you can't save anything more. This, hurts me like I can't explain it. Especially given the fact that I was doing professional work with the app. STEPS TO REPRODUCE I don't know how to reproduce the issue. The saving system of your app is unstable and that's all. OBSERVED RESULT Firstly it writes autosave, but it's stuck at a level in the progress bar. It didn't budge for lots of minutes. So I cancelled it. I then continued to work and tried to save again using all possible ways, but no saved file anymore. And the saving progress bar won't ever show up again after you confirm save location and file name in the save dialog. EXPECTED RESULT The save system should be flawless. By the way, this isn't common to this version of Krita only. It also happens with 4.4.2 and 4.4.3. SOFTWARE/OS VERSIONS Windows 10 1909 Additional information. App used : Krita stable git version 4.4.4 alpha(7d4dcb1) As soon as I noticed that I couldn't save to a new file, I wanted to copy all the layers. But when I did so, Krita immediately crashed ! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435202] Newly imported images do not show in database
https://bugs.kde.org/show_bug.cgi?id=435202 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- Which kind of database type did you use ? Sqlite ? Mysql interanm ? Mysql or MariaDb server ? Where is hosted your database ? Which settings do you use exactly ? Can you provide a Debuview trace while digiKam is running ? Look details in contribute page for details : https://www.digikam.org/contribute/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 433158] Different menu item height between breeze and breeze-gtk
https://bugs.kde.org/show_bug.cgi?id=433158 --- Comment #15 from gsbhasi...@gmail.com --- Sorry for creating a duplicate bug, I was not able to find it previously reported. I'm happy to play around and attempt to create a PR, but I'm not sure how the Breeze GTK build system works. If I get the time, I'll try taking a look over the weekend -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 435167] IPv6: file browsing freezes on IPv4/IPv6 hydrid network due to nonsensical address passed to ssh
https://bugs.kde.org/show_bug.cgi?id=435167 --- Comment #4 from 2wxsy5823...@opayq.com --- My network is also IPv4/IPv6 hybrid, and it seems that if I unpair and pair the devices again, and then browse the device via Dolphin, IPv6 will be used. But after a period of time, it will fallback to IPv4 again. It seems that IPv4 is preferred most of the times. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435154] kwin_killer_helper is started when systemd action is executed in systemsettings5 and user is trying to interact with the window
https://bugs.kde.org/show_bug.cgi?id=435154 --- Comment #8 from Kevin Kofler --- Well, it is according to the author: https://rthomsen6.wordpress.com/2016/12/18/introducing-systemdgenie/ but the codebase has always been only sporadically updated. -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 435203] New: Monthly report shows huge percentage for variation
https://bugs.kde.org/show_bug.cgi?id=435203 Bug ID: 435203 Summary: Monthly report shows huge percentage for variation Product: skrooge Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: guillaume.deb...@gmail.com Reporter: k...@mockies.de CC: steph...@mankowski.fr Target Milestone: --- Created attachment 137215 --> https://bugs.kde.org/attachment.cgi?id=137215=edit Monthly report screenshot SUMMARY Huge variations are no longer shown as "∞" in the monthly report. The report will get very wide. STEPS TO REPRODUCE 1. add a new account 2. add a operation with e.g. value "8000" with date in previous month 3. create a monthly report OBSERVED RESULT The variation is shown like 0,00 € 8.000,00 € +1.000.000.000.000.000.052.504.760.255.204.420.248.704.468.581.108.159.154.915.854.115.511.802.457.988.908.195.786.371.375.080.447.864.043.704.443.832.883.878.176.942.523.235.360.430.575.644.792.184.786.706.982.848.387.200.926.575.803.737.830.233.794.788.090.059.368.953.234.970.799.945.081.119.038.967.640.880.074.652.742.780.142.494.579.258.788.820.056.842.838.115.669.472.196.386.865.459.400.540.160,00 % EXPECTED RESULT In previous versions of skrooge huge values had been shown as "∞" SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.21.3 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.10-arch1-1 OS Type: 64-bit Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-4460 CPU @ 3.20GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4600 Skrooge Version 2.24.6 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 435195] Can the output file take hostname into account?
https://bugs.kde.org/show_bug.cgi?id=435195 --- Comment #2 from Hui Wang --- Hi Milian, Sure, I can do the pull request. Do you want the default output file name being suffix'ed with hostname as well, for example do the following change? - output=$(pwd)/heaptrack.$(basename "$client").$$ + output=$(pwd)/heaptrack.$(basename "$client").$(hostname).$$ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 414805] Crash in QScreen::handle() after QXcbIntegration::createPlatformOpenGLContext()
https://bugs.kde.org/show_bug.cgi?id=414805 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #18 from David Edmundson --- Some initial analysis #6 0x7f20d6e3b3a4 in QScreen::handle() const () at /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5 This just returns the platformScreen, this is set in the ctor, so for a crash to happen here it means the QScreen object has been deleted. In one of the dupes we can see a pointer is sent as this to QScreen::handle, which heavily implies it's a dangling pointer. If someone can reproduce reliably valgrind will tell us in an instant what's wrong. -- You are receiving this mail because: You are watching all bug changes.
[kstart] [Bug 140559] wish for start on specific xinerama screen
https://bugs.kde.org/show_bug.cgi?id=140559 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #4 from David Edmundson --- xinerama is ancient, closing geometry can be set -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 119268] Advanced Xinerama support for ksplashml
https://bugs.kde.org/show_bug.cgi?id=119268 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- xinerama is ancient, closing -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 435163] crash on highlighter usage only after save
https://bugs.kde.org/show_bug.cgi?id=435163 --- Comment #3 from Albert Astals Cid --- Does this happen with every single file or just wiht one in particular? If just one, can you share it? If not can you run valgrind okular myfile.pdf and do what you do to make okular crash and then attach the output of valgrind? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435113] Pointer speed resets after restart
https://bugs.kde.org/show_bug.cgi?id=435113 --- Comment #2 from george fb --- > Does the same thing happen immediately if you run `sudo udevadm trigger -s > input`? No. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 422204] Strokes with gradients mess up the fill colors
https://bugs.kde.org/show_bug.cgi?id=422204 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/graphics/krita/-/merge_requests/784 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 434828] Shape Fill gradient colors changing to stroke gradient color
https://bugs.kde.org/show_bug.cgi?id=434828 --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/784 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 399127] Vector object fills itself when gradient stroke is selected in tool settings
https://bugs.kde.org/show_bug.cgi?id=399127 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #11 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/784 -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 432910] Unintended pause button for videocall with Plasma-browser-integration
https://bugs.kde.org/show_bug.cgi?id=432910 Phu H. Nguyen changed: What|Removed |Added CC||phuhngu...@disroot.org Component|general |Chrome Product|Planet KDE |plasma-browser-integration Assignee|c...@walagran.com |k...@privat.broulik.de -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 435060] Notifications in the history lack interactive features that are in their pop-ups for KDE Connect
https://bugs.kde.org/show_bug.cgi?id=435060 --- Comment #4 from Nico --- @nate I double-checked and I think it was already added https://invent.kde.org/network/kdeconnect-kde/-/blob/master/plugins/notifications/notification.cpp#L95 So waiting for a new release 拾 -- You are receiving this mail because: You are watching all bug changes.
[Planet KDE] [Bug 359816] After opening notebook part of windows hide under task bar if they are maximized
https://bugs.kde.org/show_bug.cgi?id=359816 Phu H. Nguyen changed: What|Removed |Added CC||phuhngu...@disroot.org --- Comment #2 from Phu H. Nguyen --- Is this for another product? There's nothing related to "notebook" here. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435000] Crashed when i opened konsole
https://bugs.kde.org/show_bug.cgi?id=435000 Weng Xuetian changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #2 from Weng Xuetian --- The crash is in a plugin library of kime (https://github.com/Riey/kime) Likely to be a bug in kime instead of plasma since no other input method has similar bug reported. Since it's SIGSEGV so it might be some missing null pointer check in the kime's im module. Please report the bug to them. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 435076] Input level monitoring can cause Bluetooth headsets with microphones to switch to undesirable "headset" profile rather than using superior "A2DP" profile
https://bugs.kde.org/show_bug.cgi?id=435076 --- Comment #2 from Gurenko Alex --- (In reply to Nate Graham from comment #1) > Hmm, interesting problem. I guess this is a limited use case, but it actually hurts, because same volume level for different profiles leads to different output volume. Something to consider at least. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 435077] Audio is not switching for active clients when using PipeWire
https://bugs.kde.org/show_bug.cgi?id=435077 --- Comment #5 from Gurenko Alex --- (In reply to Nate Graham from comment #4) > But I guess if they fixed this in PipeWire's PulseAudio compatibility layer, > that's good too. It still happens right now, but generally it works with recent update. Cannot catch specific case when it's still happening -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 435193] crop redo causes crash
https://bugs.kde.org/show_bug.cgi?id=435193 tomtomtomreportin...@gmail.com changed: What|Removed |Added CC||tomtomtomreportingin@gmail. ||com --- Comment #1 from tomtomtomreportin...@gmail.com --- I'm not seeing the same things you see with these steps... are you sure you weren't triggering https://bugs.kde.org/show_bug.cgi?id=433770 , which is already fixed for upcoming releases? -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 435155] Heaptrack 1.2.0 fails to build with libunwind 1.5.0
https://bugs.kde.org/show_bug.cgi?id=435155 Milian Wolff changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #1 from Milian Wolff --- the reason is probably that a static library doesn't automatically pull in its dependencies - and you seem to be linking your static libunwind against a dynamic liblzma. I don't know how to detect this best, quite frankly I think that's a pretty custom setup which requires custom code like you have done. personally I'm always using the shared libraries for libunwind and that works just fine. if you want to improve support for static libs - patches welcome! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 435119] Search doesn't work.
https://bugs.kde.org/show_bug.cgi?id=435119 --- Comment #7 from Mina <842m...@gmail.com> --- > It may also be that things work differently if you've been running Neon for a > while and started with a far older version and upgraded. Yeah my neon is with me since 18.04 and I upgraded it to 20.04. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 435199] Offer a choice whether mute actions mute all relevant devices, or just the default one
https://bugs.kde.org/show_bug.cgi?id=435199 Ovidiu-Florin BOGDAN changed: What|Removed |Added CC||ovidiu@gmail.com --- Comment #1 from Ovidiu-Florin BOGDAN --- I like the idea presented in bug 434217 about having 2 sets of shortcuts: one for mute all and one for mute the default device. That way we don't need a setting to have one or the other and everyone can have both. Key combination with shift is a good idea. Which one is the default (without shift) is irrelevant to me as I expect we will be able to edit these shortcuts like all the others and choose what's most comfortable for each one of us. Thank you Nate for doing an awesome job aggregating these issues. -- You are receiving this mail because: You are watching all bug changes.
[Heaptrack] [Bug 435195] Can the output file take hostname into account?
https://bugs.kde.org/show_bug.cgi?id=435195 Milian Wolff changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Milian Wolff --- yes that sounds like a good idea. in general improving the ability to define the file name would be welcome. are you willing to provide a patch? It should be fairly easy to do. see existing code in src/track/heaptrack.sh.cmake which handles the `-o` switch. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 435119] Search doesn't work.
https://bugs.kde.org/show_bug.cgi?id=435119 --- Comment #6 from Mina <842m...@gmail.com> --- > is Baloo running or not? Yes it should be running. I have this: $ pgrep baloo 1427814 1430114 > when you do a Ctrl-F you'll see... I see something like this https://bugsfiles.kde.org/attachment.cgi?id=137169 which has "any type" & "any date" & "any rating". Therefore baloo should be running. > Try creating a test file in your Documents folder... Okay, but I used "~/Documents/TestBaloo" instead, because my Documents folder is quite messy. $ echo "Hello Penguin" > test-file.txt And now if I go to that folder and Ctrl + F and search "test" or "Penguin" I get no results. $ balooctl status It stays blank and I have to hit Ctrl + C to exit. $ balooshow -x test-file.txt test-file.txt: No index information found ...so there's no index. Okay. mono@gask:~/Documents/TestBaloo$ baloosearch test /home/mono/Sachen/Documents Library/Thesis/template/lstpatch.sty It returns things from another directory. This is not a full list. And test-file.txt is not in the list. $ baloosearch Penguin Elapsed: 15.2315 msecs Returns nothing. Now for balooctl monitor in one window and balooctl purge in another window. The first one: $ balooctl monitor Press ctrl+c to stop monitoring File indexer is running Idle The second one: $ balooctl purge Stopping the File Indexer ... - failed to stop! Not sure if you can see the output correctly, but it's just lots of dots and "failed to stop" in the end. > In System Settings "Search", you should see "Enable File Search" checked and > your home directory "indexed"... Yes it's checked, and home is indexed, and also "Also index file content" is checked. Hope any of this makes sense. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 435201] 'Enter' Key doesn't confirm crop.
https://bugs.kde.org/show_bug.cgi?id=435201 tomtomtomreportin...@gmail.com changed: What|Removed |Added CC||tomtomtomreportingin@gmail. ||com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Assignee|krita-bugs-n...@kde.org |sharafzaz...@gmail.com --- Comment #1 from tomtomtomreportin...@gmail.com --- This was known but wasn't on the bug tracker yet, Sharaf should already be looking into it. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 428757] microphone tray applet's mute toggle function doesn't always update selected device
https://bugs.kde.org/show_bug.cgi?id=428757 Daniel changed: What|Removed |Added Attachment #133085|0 |1 is obsolete|| --- Comment #4 from Daniel --- Created attachment 137214 --> https://bugs.kde.org/attachment.cgi?id=137214=edit wrong device volume is updated (now h264 video) I've noticed the video was encoded with h265, which browser sadly don't support yet, so i've uploaded it with h264. Also, I just reconfirmed the bug with Plasma 5.21.3 Also, I want to point out, that it is not exactly a duplicate, since #435142 is about changing the default mic only, while this bug is about the issue that (under certain circumstances) the current default mic is **not** toggled. However, both would be resolved if the toggle-option would just toggle all mics, wether they are the default or not, that's why you marked them as duplicate, @Nate isn't it? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 435202] New: Newly imported images do not show in database
https://bugs.kde.org/show_bug.cgi?id=435202 Bug ID: 435202 Summary: Newly imported images do not show in database Product: digikam Version: 7.2.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: Database-Scan Assignee: digikam-bugs-n...@kde.org Reporter: vaarti...@gmail.com Target Milestone: --- SUMMARY I did not have this problem previously, but suddenly do. Either it cropped up because the size of my image collection has grown substantially, from importing a lot of files from a previous storage location, or it came with the upgrade to 7.2.0. Both of these changes happened at the same time. Here is the current issue. When I import a photo from a memory card in digiKam, even a single photo, it does not appear in the digiKam album where I imported it. It does copy on the filesystem because I can manually browse to it. If I select "Open in File Manager" from digiKam, the photo is there. It does not show up in the album in digiKam right away... and I can't figure out how long it takes to finally appear. If I right click on the album and choose refresh... it does not populate with the new item. It does eventually, but not when I am actually trying to work with the new file. This behavior occurs 100% of the time, and is making digiKam almost useless as an import and edit tool for new images. I import, and then have to manually find it in the filesystem to open it. I suspect it has to do with "Find new items" and how that is processing. It's almost as if it is scanning the entire folder structure, which is massive, vs just scanning the album I just downloaded to or clicked "refresh" for. I assume, again, it relates to my large volume of photos because I only experienced this problem after I decided to use digiKam as my primary management and import solution and imported all of my old files. STEPS TO REPRODUCE 1. Import from Media Card 2. Attempt to find in Album 3. OBSERVED RESULT Newly downloaded/imported file is not shown EXPECTED RESULT Expect to see new file that I just imported. 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.
[digikam] [Bug 435179] face write to database with wrong user (''@'%') MariaDB backend
https://bugs.kde.org/show_bug.cgi?id=435179 --- Comment #16 from gessel --- MariaDB [digikam]> show triggers; +-++---+-+++---+-+--+--++ | Trigger | Event | Table | Statement | Timing | Created | sql_mode | Definer | character_set_client | collation_connection | Database Collation | +-++---+-+++---+-+--+--++ | insert_tagstree | INSERT | Tags | INSERT INTO TagsTree SELECT NEW.id, NEW.pid UNION SELECT NEW.id, pid FROM TagsTree WHERE id = NEW.pid | AFTER | 2021-03-26 21:09:24.38 | STRICT_TRANS_TABLES,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION | @% | utf8mb4 | utf8mb4_general_ci | utf8mb4_general_ci | | move_tagstree | UPDATE | Tags | BEGIN IF (NEW.pid != OLD.pid) THEN DELETE FROM TagsTree WHERE ((id = OLD.id) OR id IN (SELECT id FROM (SELECT id FROM TagsTree WHERE pid = OLD.id) AS tmpTree1))
[plasma-pa] [Bug 435076] Input level monitoring can cause Bluetooth headsets with microphones to switch to undesirable "headset" profile rather than using superior "A2DP" profile
https://bugs.kde.org/show_bug.cgi?id=435076 Nate Graham changed: What|Removed |Added Summary|Audio applet queries input |Input level monitoring can |level for all microphones |cause Bluetooth headsets ||with microphones to switch ||to undesirable "headset" ||profile rather than using ||superior "A2DP" profile Keywords||usability CC||k...@david-redondo.de, ||k...@davidedmundson.co.uk, ||k...@privat.broulik.de, ||n...@kde.org --- Comment #1 from Nate Graham --- Hmm, interesting problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435058] Plasma crash after Lattedock crash on wakeup
https://bugs.kde.org/show_bug.cgi?id=435058 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 414805 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 414805] Crash in QScreen::handle() after QXcbIntegration::createPlatformOpenGLContext()
https://bugs.kde.org/show_bug.cgi?id=414805 --- Comment #17 from Nate Graham --- *** Bug 435058 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 435077] Audio is not switching for active clients when using PipeWire
https://bugs.kde.org/show_bug.cgi?id=435077 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |UPSTREAM --- Comment #4 from Nate Graham --- But I guess if they fixed this in PipeWire's PulseAudio compatibility layer, that's good too. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 435077] Audio is not switching for active clients when using PipeWire
https://bugs.kde.org/show_bug.cgi?id=435077 --- Comment #3 from Nate Graham --- Active STREAMS! I meant active STREAMS! -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 435077] Audio is not switching for active clients when using PipeWire
https://bugs.kde.org/show_bug.cgi?id=435077 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 CC||n...@kde.org Summary|Audio is not switching for |Audio is not switching for |active clients |active clients when using ||PipeWire Status|REPORTED|CONFIRMED --- Comment #2 from Nate Graham --- This is because PipeWire doesn't use the same code that PulseAudio does to cause active screams to switch automatically. So when you use the setting for "Automatically switch all running streams when a new output becomes available", nothing happens, because this setting only affects PulseAudio. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 435201] New: 'Enter' Key doesn't confirm crop.
https://bugs.kde.org/show_bug.cgi?id=435201 Bug ID: 435201 Summary: 'Enter' Key doesn't confirm crop. Product: krita Version: nightly build (please specify the git hash!) Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Tools Assignee: krita-bugs-n...@kde.org Reporter: i...@ralek.art Target Milestone: --- After selecting an area to crop, hitting the 'enter' key cancels the crop. The only way to confirm a crop is to click the 'crop' button in the tool options docker. Version: 4.4.4-alpha (git 14e244c) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435042] kwin_wayland segfaults while recording via pipewire if mouse hovers over (close) button of window
https://bugs.kde.org/show_bug.cgi?id=435042 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435108] "Move mouse to center" action should center within the current screen, not the combined area of all screens
https://bugs.kde.org/show_bug.cgi?id=435108 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Assignee|k...@michael-jansen.biz |kwin-bugs-n...@kde.org Product|systemsettings |kwin Component|kcm_khotkeys|general Severity|wishlist|normal CC||n...@kde.org Summary|Shortcut to center mouse|"Move mouse to center" |within screen |action should center within ||the current screen, not the ||combined area of all ||screens Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435109] Mouse pointer highlighter is distracting and could use a visual overhaul
https://bugs.kde.org/show_bug.cgi?id=435109 Nate Graham changed: What|Removed |Added Severity|wishlist|normal Target Milestone|1.0 |--- Status|REPORTED|CONFIRMED CC||n...@kde.org Summary|New effect: Less|Mouse pointer highlighter |distracting mouse pointer |is distracting and could |highlighter |use a visual overhaul Product|plasmashell |kwin Version|master |5.21.3 Assignee|k...@davidedmundson.co.uk|kwin-bugs-n...@kde.org Ever confirmed|0 |1 Component|general |effects-various -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435113] Pointer speed resets after restart
https://bugs.kde.org/show_bug.cgi?id=435113 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||n...@kde.org --- Comment #1 from Nate Graham --- Does the same thing happen immediately if you run `sudo udevadm trigger -s input`? If so then this probably has the same root cause as Bug 414559. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 435133] After creating an access point and disconnecting, unable to make another access point
https://bugs.kde.org/show_bug.cgi?id=435133 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421780] Most ways of scrolling a document not working (Qt 5.15)
https://bugs.kde.org/show_bug.cgi?id=421780 --- Comment #19 from abulhair.sapa...@gmail.com --- Created attachment 137213 --> https://bugs.kde.org/attachment.cgi?id=137213=edit Okular autotest results I'm running Gentoo, so I just compiled the okular tests and ran them. -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 435134] Connecting to a configured network with a new wifi adapter makes plasma ask for password again
https://bugs.kde.org/show_bug.cgi?id=435134 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 435135] If the active hotspot's configuration is edited, a ghost entry appears on the network list
https://bugs.kde.org/show_bug.cgi?id=435135 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 435136] hotspot is created with no password by default
https://bugs.kde.org/show_bug.cgi?id=435136 Nate Graham changed: What|Removed |Added Severity|normal |major Priority|NOR |HI CC||n...@kde.org Summary|hotspot configuration |hotspot is created with no |"requires" trial and error |password by default -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 435152] Enabling Hotspot via applet causes kernel problems and firmware error
https://bugs.kde.org/show_bug.cgi?id=435152 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Component|applet |general Resolution|--- |UPSTREAM CC||n...@kde.org --- Comment #2 from Nate Graham --- Yep. -- You are receiving this mail because: You are watching all bug changes.
