[kwin] [Bug 445628] New: Changing screen resolution on laptop leaves black region
https://bugs.kde.org/show_bug.cgi?id=445628 Bug ID: 445628 Summary: Changing screen resolution on laptop leaves black region Product: kwin Version: 5.23.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: m...@iyanmv.com Target Milestone: --- SUMMARY First of all, sorry if it's not the right product or component to report the bug. Please, move it where it fits better, if you know better. Today I discover that if I change the resolution from 1920x1200 (16:10) to 1920x1080 (16:9), when I change it back to the 16:10 one, there is a black region on the bottom. It is not just a render issue, because the mouse cannot move to it. It's hard to explain, but I hope you get the idea. Maybe I can add a video if it's not clear. I realized this by connecting my laptop to an external TV with HDMI, unifying output (then resolution changed automatically to a 16:9), and then removing the HDMI. First thing I noticed, is that laptop didn't revert to its native 16:10 resolution (should I open a different report for this?), which is a thing I would expect, but then I saw the main bug that I described above when I tried to select the right resolution manually. In any case, I can reproduce the main issue without attaching the laptop to an external monitor. STEPS TO REPRODUCE (I guess a laptop with a 16:10 aspect ratio screen is needed) 1. Go to System Settings -> Display and Monitor -> Display Configuration, select 1920x1980 (16:9) and apply. 2. Change back to 1920x1200 (16:10) and apply OBSERVED RESULT There is a black region on the bottom of the screen that shows nothing. Mouse also cannot pass to that region. EXPECTED RESULT Resolution changes successfully. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.15.2-arch1-1 (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 445627] New: Query on Leak summary
https://bugs.kde.org/show_bug.cgi?id=445627 Bug ID: 445627 Summary: Query on Leak summary Product: valgrind Version: 3.15 SVN Platform: Other OS: Other Status: REPORTED Severity: major Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: amita1...@gmail.com Target Milestone: --- Can you please let us know how to check for memory leak or to print that output again when we need. This is required when we do a 24 hour run on Valgrind and check memory leak after 24 hours. Currently the leak summary gets printed at the very beginning of testing. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 445626] New: Crash when using "Mix Clips" and moving them around
https://bugs.kde.org/show_bug.cgi?id=445626 Bug ID: 445626 Summary: Crash when using "Mix Clips" and moving them around Product: kdenlive Version: 21.08.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: kirk...@hotmail.com Target Milestone: --- Created attachment 143650 --> https://bugs.kde.org/attachment.cgi?id=143650=edit gdb trace log SUMMARY *** Using "Mix Clips" option and moving the clips around for a bit often causes crashing. *** STEPS TO REPRODUCE 1. Place two clips in a row in the same track. 2. Remove part of the first clip's ending, and remove part of the second clips start. 3. Place clips next to each other. 4. Select first clip and hit "Mix Clips", you'll see blue area between the clips. 5. Move the Mix Clips zones around, and move the first and second clip around relative to eachother, keep repeating steps until crash. OBSERVED RESULT Crash. EXPECTED RESULT Not crashing. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro, Kernel 5.10, KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 433171] Yakuake Opens, but does not close under wayland
https://bugs.kde.org/show_bug.cgi?id=433171 --- Comment #3 from Andrew Ammerlaan --- (In reply to Oded Arbel from comment #2) > Recently there were various changes to how Yakuake handles opening and > closing on Wayland and X11 - can you please check if this is still an issue? Still an issue with version 21.08.3, "QT_QPA_PLATFORM=xcb yakuake" works as a workaround. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445444] wrong window size for alacritty terminal emulator
https://bugs.kde.org/show_bug.cgi?id=445444 Vlad Zahorodnii changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/kwin/commit/068d60e36a11 |ma/kwin/commit/325208347c40 |2c6b901010331ef3a995019c97c |d7311aea83572b5150ba3750cba |b |9 --- Comment #10 from Vlad Zahorodnii --- Git commit 325208347c40d7311aea83572b5150ba3750cba9 by Vlad Zahorodnii. Committed on 17/11/2021 at 06:59. Pushed by vladz into branch 'Plasma/5.23'. Revert "wayland: Check workspace position when preferred deco mode changes" This reverts commit 2560288e4b66acfdbb8a8f4daafd2d600aeb525a. It broke alacricitty. The fix is not obvious, so revert the commit for the time being. (cherry picked from commit 068d60e36a112c6b901010331ef3a995019c97cb) M +1-1src/xdgshellclient.cpp https://invent.kde.org/plasma/kwin/commit/325208347c40d7311aea83572b5150ba3750cba9 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445444] wrong window size for alacritty terminal emulator
https://bugs.kde.org/show_bug.cgi?id=445444 Vlad Zahorodnii changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/kwin/commit/068d60e36a11 ||2c6b901010331ef3a995019c97c ||b Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #9 from Vlad Zahorodnii --- Git commit 068d60e36a112c6b901010331ef3a995019c97cb by Vlad Zahorodnii. Committed on 17/11/2021 at 06:58. Pushed by vladz into branch 'master'. Revert "wayland: Check workspace position when preferred deco mode changes" This reverts commit 2560288e4b66acfdbb8a8f4daafd2d600aeb525a. It broke alacricitty. The fix is not obvious, so revert the commit for the time being. M +1-1src/xdgshellclient.cpp https://invent.kde.org/plasma/kwin/commit/068d60e36a112c6b901010331ef3a995019c97cb -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445444] wrong window size for alacritty terminal emulator
https://bugs.kde.org/show_bug.cgi?id=445444 --- Comment #8 from David Edmundson --- first configure event is [3085629.386] xdg_toplevel@22.configure(1, 1, array) which shows kwin is telling it do this, which is weird. From the logs I can't see why it wouldn't be 0,0. but the log shows something very wrong on the client. We're committing the surface before setting min/max/deco. This needs fixing their side. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444715] Under wayland, session lock/logout/restart and poweroff 30s timeout screen doesn't show
https://bugs.kde.org/show_bug.cgi?id=444715 Martin van Es changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #5 from Martin van Es --- I added the info, what more can I do? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 443928] Manga mode
https://bugs.kde.org/show_bug.cgi?id=443928 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 445500] Saving file fails if a backup file exists with brackets in the filename
https://bugs.kde.org/show_bug.cgi?id=445500 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #5 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.
[Discover] [Bug 443936] Discover crash always
https://bugs.kde.org/show_bug.cgi?id=443936 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.
[plasmashell] [Bug 444715] Under wayland, session lock/logout/restart and poweroff 30s timeout screen doesn't show
https://bugs.kde.org/show_bug.cgi?id=444715 --- 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.
[lattedock] [Bug 444588] GLobal menu don't go away on closing KDE Systemsettings
https://bugs.kde.org/show_bug.cgi?id=444588 --- 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.
[kmymoney] [Bug 443551] Default reconciliation state not used for new entries
https://bugs.kde.org/show_bug.cgi?id=443551 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #7 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434950] Task manager labels disappearing
https://bugs.kde.org/show_bug.cgi?id=434950 --- 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 443521] Trackpad Disabled on Wayland
https://bugs.kde.org/show_bug.cgi?id=443521 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.
[okular] [Bug 443707] Okular crashes while searching
https://bugs.kde.org/show_bug.cgi?id=443707 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #7 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 425169] Cannot open file unknown account id
https://bugs.kde.org/show_bug.cgi?id=425169 --- Comment #14 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 411039] Use the tray / SNI model as an additional source for "what's running" in libtaskmanager
https://bugs.kde.org/show_bug.cgi?id=411039 --- Comment #8 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 406936] Changing account from checking to savings type caused crash
https://bugs.kde.org/show_bug.cgi?id=406936 --- 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 392841] grouped icon in taskmanager does not respond on click after a while.
https://bugs.kde.org/show_bug.cgi?id=392841 --- 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 445367] Adding a bundle with resource duplicated in disabled bundle disables the resource
https://bugs.kde.org/show_bug.cgi?id=445367 Tiar changed: What|Removed |Added CC||tamtamy.tym...@gmail.com --- Comment #4 from Tiar --- Related (possibly talking about issues related to automatic deactivation in case of equal md5): bug 443876 (reported) bug 439703 (marked as intentional) bug 445408 (marked as fixed, because after the fix it was possible to find and put deactivated brush tips into the bundle) bug 441347 (marked as fixed, because after the fix the presets started working with deactivated brush tips, I think) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 444798] Possible issue with layer styles causing files to become unusable
https://bugs.kde.org/show_bug.cgi?id=444798 Eoin O'Neill changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|REMIND |--- -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 444798] Possible issue with layer styles causing files to become unusable
https://bugs.kde.org/show_bug.cgi?id=444798 Eoin O'Neill changed: What|Removed |Added Resolution|--- |REMIND Status|CONFIRMED |NEEDSINFO CC||eoinoneill1...@gmail.com --- Comment #6 from Eoin O'Neill --- Hi Jaiden Williams, This is currently working on my master branch with the given test file. Would you try the latest nightly again and see if this error still occurs? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445390] Layer styles duplicate bundle patterns
https://bugs.kde.org/show_bug.cgi?id=445390 Eoin O'Neill changed: What|Removed |Added Ever confirmed|0 |1 CC||eoinoneill1...@gmail.com Status|REPORTED|CONFIRMED --- Comment #1 from Eoin O'Neill --- Yes this is definitely occurring. Interestingly, the new (erroneous) database entry has the following as the filename: `751bdf15-6ddd-46d6-bf9d-bac02b5d4628.0001.pat` This probably means that somewhere in the embedded resource loading, there's a erroneous call that is using the md5 as the file name. This is probably fine when dealing with resources that aren't already present in the database, but we should try to load existing resources and compare md5 hash values first to allow for reuse wherever possible. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 442089] Tens of "error while trying to delete calendar item" popups appear randomly
https://bugs.kde.org/show_bug.cgi?id=442089 fyrefi...@gmail.com changed: What|Removed |Added CC||fyrefi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445367] Adding a bundle with resource duplicated in disabled bundle disables the resource
https://bugs.kde.org/show_bug.cgi?id=445367 Eoin O'Neill changed: What|Removed |Added CC||eoinoneill1...@gmail.com --- Comment #3 from Eoin O'Neill --- Hmm, I can't seem to reproduce this in master. Has this been fixed? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445623] When a window type is not selected for a window filter on a khotkeys shortcut, no windows are matched instead of all of them
https://bugs.kde.org/show_bug.cgi?id=445623 Dmitry Alexandrov changed: What|Removed |Added CC||d...@gnui.org -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445502] KPL palettes fail to open or import
https://bugs.kde.org/show_bug.cgi?id=445502 Eoin O'Neill changed: What|Removed |Added CC||eoinoneill1...@gmail.com --- Comment #3 from Eoin O'Neill --- As of master today, importing a KPL seems to work as expected. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 445624] Selecting menu entry "Configure Elisa...." dialogue crashes Elisa when running under Wayland
https://bugs.kde.org/show_bug.cgi?id=445624 --- Comment #1 from Rob Collins --- I just fired up Elisa in a x11 session and discovered the same qrc error and crash as described in my bug report. So, a bug for both wayland and x11. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445581] Krita crashes when selecting a brush
https://bugs.kde.org/show_bug.cgi?id=445581 Eoin O'Neill changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||eoinoneill1...@gmail.com Resolution|--- |REMIND --- Comment #1 from Eoin O'Neill --- Hi Andreas Resch, Regarding your bundle -- does it normally include the brush tips within the zip contents? The bug here could be related to how Krita loads that initial resource bundle, as trying to import a brush tip on it's own w/ a fresh version of Krita 5 works as expected on my end. Thanks, Eoin. -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 394476] Can't edit applications that are installed through flatpak
https://bugs.kde.org/show_bug.cgi?id=394476 --- Comment #5 from Thiago Sueto --- In the meantime, for those looking for a workaround, you can simply install your flatpak repositories with the --user flag, e.g. flatpak remote-add --user flathub-beta https://flathub.org/beta-repo/flathub-beta.flatpakrepo This way sudo isn't needed to install applications, they are installed in userspace (~/.local/share/flatpak/exports/share/applications/ would include symlinks to ~/.local/share/flatpak/app/), and editing the .desktop launchers works as intended since there are sufficient permissions. -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 394476] Can't edit applications that are installed through flatpak
https://bugs.kde.org/show_bug.cgi?id=394476 Thiago Sueto changed: What|Removed |Added CC||herzensch...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445625] New: The Resource Manager's tags widget make the panel wiggle in place
https://bugs.kde.org/show_bug.cgi?id=445625 Bug ID: 445625 Summary: The Resource Manager's tags widget make the panel wiggle in place Product: krita Version: 5.0.0-beta2 Platform: Compiled Sources OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: a...@amyspark.me Target Milestone: --- 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 *** The Resource Manager's tags widget are manually rendered via a mix of paint events and customized QLabels. Since the add and delete "buttons" do not respect the system's QLabel sizing, they make the form layout row extend and contract in place. This causes the widget to wiggle in place because of the stretcher in the metadata widget above its panel. Removing the stretcher above does fix the wiggle, but the mis-sizing should still be fixed. STEPS TO REPRODUCE 1. Open Krita. 2. Open the Resource Manager. 3. Select Brush Presets, then the Krita 4 bundle, and finally navigate among the items. OBSERVED RESULT The widget that holds the preset's data goes slightly up and down whenever there are enough tabs to make the numbers of rows vary. Furthermore, the "Tags:" label is stretched to match the row's (incorrect) height. EXPECTED RESULT Layout should be stable. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION 7fe1e8a6c9 (upstream/krita/5.0, krita/5.0) Revert "build fix" -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444535] Window filtering conditions for custom shortcuts (usually) don't work
https://bugs.kde.org/show_bug.cgi?id=444535 --- Comment #4 from Adam Fontenot --- (In reply to Dmitry Alexandrov from comment #3) >>> (In meanwhile, I guess, that you are forgetting to select window type.) >> That sounds like a really nasty bug, though. Surely if you don't select a >> window type the expected behavior would be to match all window types! > Yes, I also think that it worth at least reporting. I reported this. Here's a link for those who come across this and want to track that bug: https://bugs.kde.org/show_bug.cgi?id=445623 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 445624] New: Selecting menu entry "Configure Elisa...." dialogue crashes Elisa when running under Wayland
https://bugs.kde.org/show_bug.cgi?id=445624
Bug ID: 445624
Summary: Selecting menu entry "Configure Elisa" dialogue
crashes Elisa when running under Wayland
Product: Elisa
Version: 21.08.3
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: general
Assignee: matthieu_gall...@yahoo.fr
Reporter: robcollin...@gmail.com
Target Milestone: ---
For verbose print of what is going on, I started Elisa via the terminal.
STEPS TO REPRODUCE
1. cmd "elisa" at terminal
2. select file>configure Elisa
3. Elisa freezes/crashes
OBSERVED RESULT
Elisa crashes/freezes (graphical interface remains on screen but unresponsive).
The terminal outputs the following:
qrc:/qml/SettingsForm.qml:174:13: QML Connections: Implicitly defined onFoo
properties in Connections are deprecated. Use this syntax instead: function
onFoo() { ... }
qrc:/qml/SettingsForm.qml:129:13: QML Connections: Implicitly defined onFoo
properties in Connections are deprecated. Use this syntax instead: function
onFoo() { ... }
file:///usr/lib/qt/qml/org/kde/kirigami.2/ScrollablePage.qml:123:18: QML
RefreshableScrollView: Binding loop detected for property "rightSpacing"
Qt Quick Layouts: Polish loop detected. Aborting after two iterations.
Qt Quick Layouts: Polish loop detected. Aborting after two iterations.
Qt Quick Layouts: Polish loop detected. Aborting after two iterations.
[etcsame "Qt Quick Layouts:.. line repeatedly]
EXPECTED RESULT
Elisa configuration dialogue should appear (does not appear with this bug)
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.15.2-zen (Garuda Linux distribution of Arch Linux)
KDE Plasma Version: 5.23.3
KDE Frameworks Version: 5.88.0
Qt Version: 5.15.2
taglib version: 1.12-1 from archlinux "extra" repo
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 445623] New: When a window type is not selected for a window filter on a khotkeys shortcut, no windows are matched instead of all of them
https://bugs.kde.org/show_bug.cgi?id=445623 Bug ID: 445623 Summary: When a window type is not selected for a window filter on a khotkeys shortcut, no windows are matched instead of all of them Product: systemsettings Version: 5.23.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_khotkeys Assignee: k...@michael-jansen.biz Reporter: adam.m.fontenot+...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Issue / limitation pointed out by Dmitry here: https://bugs.kde.org/show_bug.cgi?id=444535#c1 who suggested I file a separate bug report about it. I can provide repro steps if necessary. Actual behavior: If you make a keyboard shortcut in the khotkeys system setting UI, and that shortcut has a window filter, if you don't actively select a bullet to indicate the type of window you want to match, no windows are matched. Expected behavior: When creating a filter, if you don't choose a specific type of window to match, most users would expect that part of the filter to be inactive and all window types to be matched. Presumably the user wants to filter on something else, like window title or role. Suggested fix: Simply changing the behavior to match all windows if no window type is selected would still not be ideal from a UI perspective. That's because the user is not given any way to actively select "all windows" for the type filter, and if the user accidentally or deliberately selects a type filter, there's no way to undo that and go back to matching all windows (because of the way radio buttons work in QT). So the best solution here is to add an additional radio button that says "All windows" or something similar, and have that selected as the default option in the filter widget UI. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 445622] New: PackageKit selects KCoreAddons "5:5.86.0" over "5.88", breaking plasmashell 5.88 (unresolved symbol in PluginMetaData)
https://bugs.kde.org/show_bug.cgi?id=445622 Bug ID: 445622 Summary: PackageKit selects KCoreAddons "5:5.86.0" over "5.88", breaking plasmashell 5.88 (unresolved symbol in PluginMetaData) Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: modchip...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Recent update via pkcon refresh+update earlier today borked my plasmashell due to an unresolved symbol PluginMetaData::value(), which is supposed to be provided by libkf5coreaddons. Running apt list --installed, I saw I had libkf5plasma5 5.88 installed, but libkf5coreaddons5 was stuck on 5.86, and another pkcon refresh+update would not update it. It's there in the repositories, though, and I was able to install the .deb files manually which fixed the problem for me (see below). Note: I forgot to try apt update+upgrade; not sure if that would have made a difference. STEPS TO REPRODUCE 1. Update KDE Neon User 20.04 (sudo pkcon refresh && sudo pkcon update) 2. Reboot OBSERVED RESULT * libkf5coreaddons5 gets stuck on version 5.86 * The login screen reports the following error: file:///user/share/sddm/themes/breeze/Main.qml:14:1: plugin cannot be loaded for module "org.kde.plasma.core": Cannot load library /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/core/libcorebindingsplugin.so: (/usr/lib/x86_64-linux-gnu/libKF5Plasma.so.5: undefined symbol: _ZNK15KPluginMetaData5valueERK7QStringRK11QStringList) * Attempting to log in hangs. * Opening another screen with Ctrl+Alt+F2 and running "plasmashell" directly from the terminal, we get that same "undefined symbol" error as above. EXPECTED RESULT * libkf5coreaddons5 should update to 5.88 * Plasmashell should launch like normal SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon User 20.04 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION Fixed my plasmashell by forcing Ubuntu to install the correct version of KCoreAddons 5.88: sudo pkcon refresh apt download libkf5coreaddons-data=5.88.0-0xneon+20.04+focal+release+build32 libkf5coreaddons-dev=5.88.0-0xneon+20.04+focal+release+build32 libkf5coreaddons-dev-bin=5.88.0-0xneon+20.04+focal+release+build32 libkf5coreaddons-dev-bin=5.88.0-0xneon+20.04+focal+release+build32 libkf5coreaddons5=5.88.0-0xneon+20.04+focal+release+build32 sudo dpkg -i libkf5coreaddons-data_5.88.0-0xneon+20.04+focal+release+build32_all.deb libkf5coreaddons-dev_5.88.0-0xneon+20.04+focal+release+build32_amd64.deb libkf5coreaddons-dev-bin_5.88.0-0xneon+20.04+focal+release+build32_amd64.deb libkf5coreaddons5_5.88.0-0xneon+20.04+focal+release+build32_amd64.deb During installation, I saw the following warning from dpkg: warning: downgrading libkf5coreaddons-dev:amd64 from 5:5.86.0-0xneon+20.04+focal+release+build25 to 5.88.0-0xneon+20.04+focal+release+build32 which I think means dpkg thinks the version string "5:5.86.0" is newer than "5.88". -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 445621] New: No music library indexed - baloo's fault it seems
https://bugs.kde.org/show_bug.cgi?id=445621 Bug ID: 445621 Summary: No music library indexed - baloo's fault it seems Product: Elisa Version: 21.08.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: baloo Assignee: matthieu_gall...@yahoo.fr Reporter: robcollin...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 0. Set up network samba share using systemd .automount and .mount units, working fine with network music directory mounted locally as (not important so I make something up here) ~/me/music/. 1. cmd: balooctl resume resumes normally and indexing seems to progress by viewing with cmd: balooctl status 2. cmd: balooctl status shows the indexing is stuck with files left to index - ie indexing appears frozen at a particular flac file after successfully indexing x1000's of other flac files. 3. after a while a TagLib error is automatically printed at the command line. The error seems to vary slightly each time but all errors are similar to "TagLib: MPEG::Properties::read() -- Could not find a valid last MPEG frame in the stream. " 4. interestingly, the supposed successful indexed flac file metadata of the successfully indexed flac's do not show up in (eg) "artist" or "album" columns in Dolphin. OBSERVED RESULT - baloo stops indexing, stuck with a remaining number of files to index when balooctl status is entered in terminal - metadata from flac files reported by balooctl status as successfully indexed do not show up in (eg) "artist" or "album" columns in Dolphin. - no music library appears in Elisa EXPECTED RESULT baloo should finish its indexing work and following finish should return the following with the command "balooctl status": Baloo File Indexer is running Indexer state: Idle (Powersave) Total files indexed: (some number) Files waiting for content indexing: 0 Files failed to index: 0 Current size of index is (some number) MiB - music library metadata should appear in Elisa and Dolphin (does not do that with this bug). SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.15.2-zen (Garuda Linux distribution of Arch Linux) KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 taglib version: 1.12-1 from archlinux "extra" repo ADDITIONAL INFORMATION I have tried this under both wayland and x11 with the same/similar taglib error results. I have had to swap to the "index files directly" option in Elisa which is sad because that's not the indexing method intention of Elisa as I understand it. I have filed a similar report under "frameworks-baloo". -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 445620] New: Baloo indexing crashes while indexing random vorbis-tagged flac files on samba share
https://bugs.kde.org/show_bug.cgi?id=445620 Bug ID: 445620 Summary: Baloo indexing crashes while indexing random vorbis-tagged flac files on samba share Product: frameworks-baloo Version: 5.88.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: robcollin...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 0. Set up network samba share using systemd .automount and .mount units, working fine with network music directory mounted locally as (not important so I make something up here) ~/me/music/. 1. cmd: balooctl resume 2. cmd: balooctl status shows the indexing is stuck with files left to index - ie indexing appears frozen at a particular flac file after successfully indexing x1000's of other flac files. 3. after a while a TagLib error is automatically printed at the command line. The error seems to vary slightly each time but all errors are similar to "TagLib: MPEG::Properties::read() -- Could not find a valid last MPEG frame in the stream. " 4. interestingly, the supposed successful indexed flac file metadata of the sucessessfully indexed flac's do not show up in (eg) "artist" or "album" columns in Dolphin. OBSERVED RESULT - baloo stops indexing, stuck with a remaining number of files to index when balooctl status is entered in terminal - metadata from flac files reported by balooctl status as successfully indexed do not show up in (eg) "artist" or "album" columns in Dolphin. EXPECTED RESULT baloo should finish its indexing work and following finish should return the following with the command "balooctl status": Baloo File Indexer is running Indexer state: Idle (Powersave) Total files indexed: (some number) Files waiting for content indexing: 0 Files failed to index: 0 Current size of index is (some number) MiB SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.15.2-zen (Garuda Linux distribution of Arch Linux) KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 taglib version: 1.12-1 from archlinux "extra" repo ADDITIONAL INFORMATION I have tried this under both wayland and x11 with the same/similar taglib error results. This bug is particularly problematic for Elisa music library collation as it relies heavily on the baloo backend, and is the reason why I'm here. I will submit this bug under Elisa also, being such a critical part of that program. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443910] [Plasma 5.23] kwin_core: Failed to initialize compositing, compositing disabled
https://bugs.kde.org/show_bug.cgi?id=443910 --- Comment #21 from Alvin Smith --- Hi KWin default assignee, Sorry, I don't know your name. Any progress to share or anything we could look forward to? Cheers, Alvin -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445619] [Gmic] a random crash (rare) after calling GMIC dialog
https://bugs.kde.org/show_bug.cgi?id=445619 amyspark changed: What|Removed |Added CC||a...@amyspark.me, ||david.tschumpe...@gmail.com --- Comment #1 from amyspark --- Summoning dtschump, this looks like a crash deep inside CImg. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443347] [Transform tool] crash after a free transform on a layer group (with subgroups)
https://bugs.kde.org/show_bug.cgi?id=443347 --- Comment #4 from David REVOY --- Created attachment 143649 --> https://bugs.kde.org/attachment.cgi?id=143649=edit ASAN SUMMARY: AddressSanitizer: 88456835 byte(s) leaked in 23362 allocation(s). Hey @dmitryk, I tried to test and reproduce the crash with the ASAN build; and I couldn't (and believe me, I tried very *very* hard with my super nested group comic pages, with weird selection, file layers/vector layer/channel desactivated/inherit alpha/alpha lock/etc... and with all the transform modes; liquify, perspective, etc... Impressive Krita survived my stress test.) So, transform tool looks 'rock stable' in krita-5.1.0-prealpha-4807d9c-ASAN-x86_64.appimage. At least, I don't know how to make it crash on purpose. But something happened that might be normal for the ASAN build; so let me know if I report that for nothing. Once I closed Krita, my terminal output went crazy, and I had a long output of many 'Indirect leak of' , a text file of 100K lines, 12MB (it was bigger than the backlog limit of my terminal output). In attachement , I put a sample , cut in half to comply with the limit of 4MB attachement on Bugzilla. Let me know if this is useful and I'll send the 12MB version. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445619] New: [Gmic] a random crash (rare) after calling GMIC dialog
https://bugs.kde.org/show_bug.cgi?id=445619 Bug ID: 445619 Summary: [Gmic] a random crash (rare) after calling GMIC dialog Product: krita Version: nightly build (please specify the git hash!) Platform: Appimage OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: G'Mic for Krita Assignee: krita-bugs-n...@kde.org Reporter: i...@davidrevoy.com Target Milestone: --- Created attachment 143648 --> https://bugs.kde.org/attachment.cgi?id=143648=edit Gmic crash, calling back a windows with Fractalize, GDB Backtrace. Hi, I usually have a very high stability with Gmic plugin in Krita Plus and I use it very often. But here is a rare case where this one crashed full Krita after I called back a Fractalize filter ( Thread 1252 "GmicQt::FilterT" received signal SIGABRT ). I checked: the bug is not reproducible unfortunately, but I had a full gdb backtrace. So I copy it here in attachement, in case it is a useful one. Krita 5 Plus; krita-5.0.0-beta2-188e619-x86_64.appimage Kubuntu 20.04 LTS. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445589] Unable to only use the external display because plasmashell won't show panels on it
https://bugs.kde.org/show_bug.cgi?id=445589 Aleix Pol changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/commit/ ||468a59cbb3a507e7efc29ece9fa ||0386d6271efb7 --- Comment #3 from Aleix Pol --- Git commit 468a59cbb3a507e7efc29ece9fa0386d6271efb7 by Aleix Pol. Committed on 16/11/2021 at 16:48. Pushed by fusionfuture into branch 'master'. shell: Make sure the primary output is initialised on X11 as well M +4-0shell/primaryoutputwatcher.cpp https://invent.kde.org/plasma/plasma-workspace/commit/468a59cbb3a507e7efc29ece9fa0386d6271efb7 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 444520] Baloo content indexing resurrects itself after being killed *and* disabled
https://bugs.kde.org/show_bug.cgi?id=444520 --- Comment #5 from Adam Fontenot --- (In reply to tagwerk19 from comment #4) Just a couple of clarifications: > > Sooner or later, whenever Baloo kicks back in, it may also restart indexing > > file content, despite being disabled. > Baloo should really not restart on its own. If disabled it should stay > disabled - although if the baloo_file process died or was killed it would be > restarted (at least) at the next logon. To be clear, the issue here is that *content* indexing was disabled (the setting "also index file content") in the file search settings, and baloo_file_extractor was killed. Normal indexing (just the file name / file search option) was *not* disabled. And so the specific issue I'm seeing here is that when the normal indexing resumes (possibly after a reboot, possibly not), baloo_file_extractor starts trying to index file content again despite that feature being disabled in the settings. > I'd also suspect the "very large" PDF being the reason for the large index > (baloo will write a reverse index entry for each of the "random words"), > however there are other things that can also trigger the index to balloon in > size. The PDF in question is only 20 MB. It's "large" only in the sense that it has a ton of indexable text (according to the poppler devs). This suggests another pretty obvious heuristic in addition to those I mentioned in the bug report on Baloo memory use: If the index for a file grows to be larger than the original file, kill the extraction process, add the file to a list of failed files, delete the index for it, and don't try indexing the content of the file again. I realize the reality might be a bit more complicated than "just" doing that, but at the end of the day Baloo desperately needs some better heuristics given the large number of resource consumption issues users report with it. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441569] Freehand Selection Tool produces severe artifacts when holding Ctrl to draw polygonal outline
https://bugs.kde.org/show_bug.cgi?id=441569 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #5 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/1164 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 437795] System uptime is displayed in minutes and seconds only, instead of days, hours, etc.
https://bugs.kde.org/show_bug.cgi?id=437795 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #3 from Nate Graham --- Heh, forgot about that! *** This bug has been marked as a duplicate of bug 436775 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436775] More human readable uptime
https://bugs.kde.org/show_bug.cgi?id=436775 Nate Graham changed: What|Removed |Added CC||pe...@hack-libre.org --- Comment #1 from Nate Graham --- *** Bug 437795 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 380456] Suspected memory leak in baloo_file_extractor
https://bugs.kde.org/show_bug.cgi?id=380456 --- Comment #18 from Adam Fontenot --- (In reply to tagwerk19 from comment #17) > If you look at htop, you'll see that baloo_file and baloo_file_extractor run > with minimum priority. They'll yield to nearly everything that wants a CPU. > They should take all the time they need without annoying anything else Hmm, even assuming this is true, does the process suspend if the user is on battery? An otherwise idle system consuming 100% of a core for hours on end is sure to annoy the user even if it doesn't interfere with other processes. I'd also point out that I discovered this issue (after several years of being vaguely aware of "baloo problems") when I saw stuttering in a full screen game. Alt-tabbing to htop showed baloo_file_extractor at 100%. Baloo may in theory yield to other processes, but it didn't prevent me from seeing issues. > Memory usage is different, baloo "memory maps" the index and pulls pages > from disc to memory as needed, they'll be "forgotten" again if the RAM is > needed (and the pages have not been modified). You might see that baloo_file > / baloo_file_extractor use a lot of memory but that can be "just cache". If I'm not mistaken, that's just for internal Baloo memory usage, right? In my case, baloo_file_extractor is calling out to an external library (poppler), and that library is consuming an endlessly growing amount of memory (from 1-3 GB before I've killed it). It's probably safe to say that this memory usage is in the form of anonymous mappings which can't be reclaimed. Baloo *must* take that into account and kill the extractor process if it begins affecting system resources. > I'm tempted to say that if this is a application generated file with > little/no human readable information in it (that happens to be a PDF) it > would make sense to have an application specific mimetype for it. Then that > can be added to baloo's "exclude filters" list. I suspect though that if the > file is generated by a script, that might not be possible. In this case, it's a graph of some scientific data. Plotting scientific data to PDF or SVG (which both can have extractable text) is very common. In any case, it shouldn't be on the user to determine which files are causing problems (I had to use strace!) and exclude them. A file indexer should "just work". -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 445618] New: Can not assign mouse gesture under custom shortcuts anymore
https://bugs.kde.org/show_bug.cgi?id=445618 Bug ID: 445618 Summary: Can not assign mouse gesture under custom shortcuts anymore Product: systemsettings Version: 5.23.3 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_khotkeys Assignee: k...@michael-jansen.biz Reporter: ahje...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 143647 --> https://bugs.kde.org/attachment.cgi?id=143647=edit attached is the screen where I suppose to draw the mouse gesture 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 1. Go to setting/shortcuts/custom shortcuts 2. under mouse gesture create new mouse gesture action (any type , command for example) 3. go to Trigger Tab, then press edit, draw anything is should draw but it does not OBSERVED RESULT It does not draw to be save EXPECTED RESULT it should draw, I have done it before, I can not remember what version most probably 20.04 kubuntu; however I have the latest of everything now SOFTWARE/OS VERSIONS Linux/KDE Plasma: kubuntu 21.10 / kde versoin 5.23.3 (available in About System) KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I tried it, in my desktop and laptop, please fix, this is a great feature can not live without it, -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 439781] About dialog of Elisa does not locate in the center of the parent window
https://bugs.kde.org/show_bug.cgi?id=439781 ilutov changed: What|Removed |Added CC||ilija.tov...@me.com --- Comment #6 from ilutov --- Is `QApplication::activeWindow()` an option for the "About Elisa" and "Report Bug..."? That seems to work fine. "Configure Elisa..." uses a `QQmlComponent`, I couldn't find an option to set the parent window here. Similarly, "Elisa Handbook" calls `QDesktopServices::openUrl()` where setting a parent window doesn't seem possible. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 444860] Unable to share all or userdata since android 12
https://bugs.kde.org/show_bug.cgi?id=444860 michael changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #1 from michael --- Looks like this something baked into Android 12+. Certain directories are prohibit from being shared in the that kde-connect does. These same directories are permitted for local access with the right permission flag. That is set in kde-connect. I'd say there's nothing to be done from kde's side. -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 435338] Krfb on Wayland doesn't accept remote keyboard input
https://bugs.kde.org/show_bug.cgi?id=435338 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 361872] When added to panel, customized popup size not saved
https://bugs.kde.org/show_bug.cgi?id=361872 ham...@laposte.net changed: What|Removed |Added Version|5.6.2 |5.23.3 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 445610] Cannot create new archives
https://bugs.kde.org/show_bug.cgi?id=445610 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/utilities/ark/-/merge_requests/74 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 445612] When cropping from center, the crop area shrinks asymmetrically after it overflows the image boundary
https://bugs.kde.org/show_bug.cgi?id=445612 --- Comment #2 from Maik Qualmann --- I think it's good that you can drag over the image size, because a limitation at the edge of the image is always somehow "strange". But after letting go, we have to go back to the image size, because we don't support levels like Gimp. We can think about mouse handles in the middle. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 445612] When cropping from center, the crop area shrinks asymmetrically after it overflows the image boundary
https://bugs.kde.org/show_bug.cgi?id=445612 --- Comment #1 from Maik Qualmann --- In principle, the Gimp behaves in a similar way to digiKam. Only when the option "Expand from center" is activated in Gimp does it behave as you wish. Maik -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 445610] Cannot create new archives
https://bugs.kde.org/show_bug.cgi?id=445610 --- Comment #3 from Kai Uwe Broulik --- Ah, yeah, I opened an existing archive, then chose "Create New" and it told me "The archive will be created once you add files". So it's really only the welcome page not disappearing. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445617] New: Gradient: Mesh Gradient is not responding at first time invocation
https://bugs.kde.org/show_bug.cgi?id=445617 Bug ID: 445617 Summary: Gradient: Mesh Gradient is not responding at first time invocation Product: krita Version: 5.0.0-beta1 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Tools/Vector Assignee: krita-bugs-n...@kde.org Reporter: hoangduytran1...@gmail.com Target Milestone: --- SUMMARY When invoke the first time, the Mesh Gradient option doesn't show any changes on the canvas STEPS TO REPRODUCE 1. Start Krita, use any default setting for new image 2. Delete the current paint layer, add a vector layer 3. Select the rectangle tool, make sure the options are - Fill: Background color - Outline: No Outline 4. Choose a none black/white background color 5. Draw a rectangle, it should be filled with the chosen background color 6. Use select tool and select the shape. 7. In the Tool Options, select the 'Fill' option (third on the right), the text you can see is 'Solid' 8. Select the 4th Option (Mesh Gradient icon), the 4th option, next to the text 'Solid' 9. Nothing appeared to have happened on the canvas. 10. Now change to 'Solid' (second icon) again, then back to 4th option 'Mesh Gradient' (second invocation), now you can see changes on the canvas. OBSERVED RESULT At the first time invocation, the canvas remains at the state before, as if nothing is happening. I'm not saying the code underneath doesn't performing anything, but going on the changes on the canvas, it appears as if NOTHING is being done. However, on subsequent invocations, the display of changes is instant, showing that the code performed the action as required. Maybe at the first invocation, the screen is NOT REFRESHED as expected. EXPECTED RESULT As soon as the option 'Mesh Gradient' is chosen, the transform will be reflected on the canvas immediately SOFTWARE/OS VERSIONS macOS: 10.17.5 ADDITIONAL INFORMATION Please see testing steps from this screencast (https://drive.google.com/file/d/1bxlvFSlbxkFiTT60_UvymetmUhkiBRmy/view?usp=sharing) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 398685] Creating Resource Bundle Allows Selecting but Silently Does Not Include Existing Brushes
https://bugs.kde.org/show_bug.cgi?id=398685 Tiar changed: What|Removed |Added CC||andr...@andreasresch.at --- Comment #5 from Tiar --- *** Bug 445597 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445597] Brush tips and brush size are not saved in bundle
https://bugs.kde.org/show_bug.cgi?id=445597 Tiar changed: What|Removed |Added Severity|major |normal Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |DUPLICATE --- Comment #4 from Tiar --- Since now we embed brush tips into presets, it might be a somewhat easy fix, but also might not be. In any case, it's not a regression since Krita 4 didn't support exporting bundles with ABR brush tips either. *** This bug has been marked as a duplicate of bug 398685 *** -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 444654] segfault upon exit/save
https://bugs.kde.org/show_bug.cgi?id=444654 michael changed: What|Removed |Added Latest Commit|https://invent.kde.org/sdk/ |https://invent.kde.org/sdk/ |kdiff3/commit/a9244cfb81e45 |kdiff3/commit/d929ff5d528d9 |699c301f26fab0e52f47afcb10a |082bba84d7739716e42d2968517 --- Comment #3 from michael --- Git commit d929ff5d528d9082bba84d7739716e42d2968517 by Michael Reeves. Committed on 16/11/2021 at 21:46. Pushed by mreeves into branch 'master'. Fix race condition in teardown Manually disconnect from QApplication::focusChanged to prevent spurious focus change signals from reaching us during teardown. FIXED-IN:1.9.4 M +5-1src/kdiff3.cpp https://invent.kde.org/sdk/kdiff3/commit/d929ff5d528d9082bba84d7739716e42d2968517 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 445610] Cannot create new archives
https://bugs.kde.org/show_bug.cgi?id=445610 --- Comment #2 from Albert Astals Cid --- I think you can, it's just that the main page is not correctly implemented and does not disappear (i already complained about that but noone did anything). Can you confirm that after all those steps you can do Archive->Add files (and you can't before the steps)? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 445616] Update broke keys and colors in Midnight Commander.
https://bugs.kde.org/show_bug.cgi?id=445616 Martin Collins changed: What|Removed |Added CC||kdeb...@mkcollins.org -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 445616] New: Update broke keys and colors in Midnight Commander.
https://bugs.kde.org/show_bug.cgi?id=445616 Bug ID: 445616 Summary: Update broke keys and colors in Midnight Commander. Product: konsole Version: 21.08.2 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: keyboard Assignee: konsole-de...@kde.org Reporter: kdeb...@mkcollins.org Target Milestone: --- SUMMARY In Midnight Commander a number of important keys either no longer work or do something wrong. Also some of its colors have changed, hampering usability. STEPS TO REPRODUCE 1. Run mc in a konsole. 2. Try pressing F1-F4, home, end, numpad operators, probably more. 3. Look at the colors! OBSERVED RESULT Some of the keys no longer work or do the wrong thing. eg. F3 should view a file, instead it selects all files. And they go brown instead of yellow. Oh, probably unrelated but Chinese characters are still broken too. That was from an earlier update. EXPECTED RESULT No surprise changes to my precious mc. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Sparky Linux 6.1 (Debian Testing) kernel 5.14.0-4-amd64 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I tried running mc in a UXTerm. Still normal. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445087] Selected folder icons are drawn in white
https://bugs.kde.org/show_bug.cgi?id=445087 Rafael Lima changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||rafael.palma.l...@gmail.com Ever confirmed|0 |1 --- Comment #1 from Rafael Lima --- Since the latest update to 5.23.3 selected folders in Dolphin are appearing in white color. I am using the default theme. I can confirm this issue in: Operating System: Kubuntu 21.10 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.13.0-21-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 15,6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1660/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 445612] When cropping from center, the crop area shrinks asymmetrically after it overflows the image boundary
https://bugs.kde.org/show_bug.cgi?id=445612 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 442607] KDiff3 (in Windows) menu in French and in English
https://bugs.kde.org/show_bug.cgi?id=442607 michael changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 --- Comment #4 from michael --- Sorry missed that second attachment. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 444516] Crash while painting
https://bugs.kde.org/show_bug.cgi?id=444516 --- Comment #25 from David REVOY --- Created attachment 143646 --> https://bugs.kde.org/attachment.cgi?id=143646=edit Backtrace with ASAN build Thanks for the appimage @dmitryk, as I told on IRC; this one is not comfortable to use: glitch with refresh of layers within groups, performances are slow, no GMIC, and I noticed also my KPL palettes unable to load. Hard to keep it in production but I do the effort :-P Anyway: I could reproduce a crash after probably 8h painting and save the terminal output, I attached it here. I hope I caught a good fish :-) -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 444654] segfault upon exit/save
https://bugs.kde.org/show_bug.cgi?id=444654 michael changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/sdk/ ||kdiff3/commit/a9244cfb81e45 ||699c301f26fab0e52f47afcb10a Version Fixed In||1.9.4 Status|REPORTED|RESOLVED --- Comment #2 from michael --- Git commit a9244cfb81e45699c301f26fab0e52f47afcb10a by Michael Reeves. Committed on 16/11/2021 at 20:49. Pushed by mreeves into tag '1.9.4'. Fix race condition in teardown Manually disconnect from QApplication::focusChanged to prevent spurious focus change signals from reaching us during teardown. FIXED-IN:1.9.4 M +1-0ChangeLog M +5-1src/kdiff3.cpp https://invent.kde.org/sdk/kdiff3/commit/a9244cfb81e45699c301f26fab0e52f47afcb10a -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 445615] Configuring toolbar is a head-scratcher
https://bugs.kde.org/show_bug.cgi?id=445615 --- Comment #1 from Thomas Rossi --- Created attachment 143645 --> https://bugs.kde.org/attachment.cgi?id=143645=edit Kate - PartView Toolbar -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 445615] New: Configuring toolbar is a head-scratcher
https://bugs.kde.org/show_bug.cgi?id=445615 Bug ID: 445615 Summary: Configuring toolbar is a head-scratcher Product: kate Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: rossi.t...@gmail.com Target Milestone: --- Created attachment 143644 --> https://bugs.kde.org/attachment.cgi?id=143644=edit Kate - Main Toolbar SUMMARY I would like to customize the tools on the toolbar, but the default configuration looks like i'll break it if I touch it. The configuration it not clearly reflecting what is shown on the toolbar, the KatePartView buttons seem to be somehow embedded within the main toolbar. Plus, every separator is tripled for an obscure reason. (See screenshots of default configuration) Would it be possible to simplify how the toolbar works on Kate, so it's easier to customize it ? -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 427795] CPU Applet does not round Load average numbers
https://bugs.kde.org/show_bug.cgi?id=427795 --- Comment #3 from Sébastien P. --- Hi Gerald, Do you have a commit hash/know version? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #10 from geisserml --- So now I managed to roll back both the qtdeclaratives5-dev and the qtdeclaratives5-dev-tools package to the older versions using the following commands: ```bash cd /var/cache/apt/archives sudo dpkg --force-all -i qtdeclarative5-dev-tools_5.15.2+p20.04+tunstable+git2020.0228-0_amd64.deb qtdeclarative5-dev_5.15.2+p20.04+tunstable+git2020.0228-0_amd64.deb ``` However, it's still the same issue anyway... -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 445614] New: "Toggle Filter Bar" button does not actually toggle
https://bugs.kde.org/show_bug.cgi?id=445614 Bug ID: 445614 Summary: "Toggle Filter Bar" button does not actually toggle Product: dolphin Version: 21.08.2 Platform: Other OS: All Status: REPORTED Severity: minor Priority: NOR Component: bars: filter Assignee: dolphin-bugs-n...@kde.org Reporter: rossi.t...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY The "Toggle Filter Bar" on the toolbar does not toggle, it only makes the filter bar appear if it's not shown. STEPS TO REPRODUCE AND OBSERVED RESULTS AGAINST EXPECTED RESULTS: 1. With the Filter bar non visible, click on the Filter button on the toolbar. The filter bar appears as expected 2. Click again on the button to close the bar, the bar stays opened. EXAMPLE OF WORKING TOGGLE BUTTON: This behavior works as expected with the search bar. Clicking on the "Toggle Seach bar" button will make the search bar appear if not showing, and disappear if showing. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445599] mouse pointer klipper menu should paste a selected line by default
https://bugs.kde.org/show_bug.cgi?id=445599 --- Comment #2 from elypter --- would it be possible to do it safely with the middle mouse button? that is rarely pressed accidentally -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445444] wrong window size for alacritty terminal emulator
https://bugs.kde.org/show_bug.cgi?id=445444 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #7 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/1674 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #9 from geisserml --- > That one and the `qtdeclarative5-dev-tools`. Oh, pardon - I overlooked the "that one and". I'll have to re-test this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #8 from geisserml --- @tgnff242 I rolled back the `qtdeclarative5-dev-tools` package as suggested, but it didn't fix the issue, unfortunately. From looking at the package contents, this would also seem unlikely, since it appears to only contain development utilities that are not used at runtime, as far as I can guess. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 445613] New: The player crashes when you open the settings
https://bugs.kde.org/show_bug.cgi?id=445613 Bug ID: 445613 Summary: The player crashes when you open the settings Product: Elisa Version: 21.08.3 Platform: Flatpak OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: jeremymachad...@gmail.com Target Milestone: --- Created attachment 143643 --> https://bugs.kde.org/attachment.cgi?id=143643=edit Crash image SUMMARY The player crashes when you open the settings STEPS TO REPRODUCE 1. Open the app 2. Go to settings 3. Wait for the crash OBSERVED RESULT Elisa crashes EXPECTED RESULT Open Elisa settings SOFTWARE/OS VERSIONS Linux: Elementary OS odin -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 445612] New: When cropping from center, the crop area shrinks asymmetrically after it overflows the image boundary
https://bugs.kde.org/show_bug.cgi?id=445612 Bug ID: 445612 Summary: When cropping from center, the crop area shrinks asymmetrically after it overflows the image boundary Product: digikam Version: 7.3.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plugin-Editor-Crop Assignee: digikam-bugs-n...@kde.org Reporter: war...@gmx.de Target Milestone: --- SUMMARY I have a 4:3 image which shows an object. I want to crop an area with 1:1 aspect that is centered on that object, and which will use the image's full height, which means that it only cuts away parts of the image to the left and right. STEPS TO REPRODUCE 1. Start crop tool 2. Position initial 1:1 crop, centered on the object so that the frame touches the left and right edge of the object 3. Enlarge the crop, but with keeping the object in the center (by pressing Ctrl during dragging) 4. At first, the Crop area enlarges as expected OBSERVED RESULT If I enlarge the crop area so much that one of its sides leaves the image area, the area shrinks as soon as I release the mouse button in order to fit into the image again. The problem is that this does not keep the center of the area. EXPECTED RESULT 1a. Either the crop area should keep its center after releasing the mouse button, 1b. or the crop tool should not be able to expand past the image boundary in the first place. But in that case, it will not be possible to set a crop area around a center point by just dragging the corners. The best solution (not only for this problem but also as a general feature) is to introduce drag handles an the center of the four sides of the crop area. For reference what I mean, please look at the cropping tool of Gimp. Thank you. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.16-arch1-1 (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-4590 CPU @ 3.30GHz Memory: 31.0 GiB of RAM Graphics Processor: AMD PITCAIRN -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 445611] Corrupted screenshots with fullscreen OpenGL applications
https://bugs.kde.org/show_bug.cgi?id=445611 --- Comment #1 from Nikos Chantziaras --- Created attachment 143642 --> https://bugs.kde.org/attachment.cgi?id=143642=edit glxgears screenshot -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 445611] New: Corrupted screenshots with fullscreen OpenGL applications
https://bugs.kde.org/show_bug.cgi?id=445611 Bug ID: 445611 Summary: Corrupted screenshots with fullscreen OpenGL applications Product: Spectacle Version: 21.08.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: rea...@gmail.com CC: k...@david-redondo.de Target Milestone: --- Created attachment 143641 --> https://bugs.kde.org/attachment.cgi?id=143641=edit RetroArch screenshot SUMMARY When running a fullscreen application that uses OpenGL (primary use case are video games) with desktop effects disabled (the application disables them or manually with Shift+Alt+F12, Spectacle often produces pixel garbage in the screenshots. Attached are two screenshots showing the issue. One is from RetroArch, the other with plain old glxgears after switching it to fullscreen mode using Alt+F3/More Actions/Fullscreen. STEPS TO REPRODUCE 1. Disable the compositor (default shortcut Shift+Alt+F12.) 2. Run glxgears. 3. Make it fullscreen through KWin (upper-left icon on the window title bar, "More Actions", "Fullscreen". 4. Press Shift+PrintScr multiple times to take several screenshots and automatically save them in the default screenshot location configured in Spectacle. OBSERVED RESULT Some of the screenshots will have thick horizontal bars of black pixels. EXPECTED RESULT Screenshots should be clean without black pixels. SOFTWARE/OS VERSIONS Operating System: Gentoo Linux 2.8 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.10.79-gentoo (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 980 Ti/PCIe/SSE2 ADDITIONAL INFORMATION I installed flameshot (a screenshot tool, https://github.com/flameshot-org/flameshot) and it does not have this issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445448] [Wayland] Jagged cursor in Firefox, but MOZ_ENABLED_WAYLAND is enabled
https://bugs.kde.org/show_bug.cgi?id=445448 --- Comment #1 from poperi...@mailbox.org --- This definitely seems to be an issue with fractional scaling, because it doesn't happen at 100% scaling, but does at 150%. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 445610] Cannot create new archives
https://bugs.kde.org/show_bug.cgi?id=445610 Alexander Lohnau changed: What|Removed |Added CC||alexander.loh...@gmx.de Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #1 from Alexander Lohnau --- Can confirm the issue, the KFileItemActions plugin works fine though -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445046] Present option to merge tags instead of replace when renaming a tag.
https://bugs.kde.org/show_bug.cgi?id=445046 Eoin O'Neill changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REPORTED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445046] Present option to merge tags instead of replace when renaming a tag.
https://bugs.kde.org/show_bug.cgi?id=445046 Eoin O'Neill changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 445361] Animation Playback Lag
https://bugs.kde.org/show_bug.cgi?id=445361 Eoin O'Neill changed: What|Removed |Added CC||eoinoneill1...@gmail.com --- Comment #2 from Eoin O'Neill --- (In reply to Ahab Greybeard from comment #1) > I think this is related to (if not identical to) bug: > https://bugs.kde.org/show_bug.cgi?id=422239 I think this might be the case as well, my linux system has no issues. I'll test it out on Windows too though to make sure. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 444654] segfault upon exit/save
https://bugs.kde.org/show_bug.cgi?id=444654 --- Comment #1 from michael --- That's an intresting one. Not able to reproduce it on my machine. I wonder if its timing issue with when the QSplitter gets destroyed. -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 445610] New: Cannot create new archives
https://bugs.kde.org/show_bug.cgi?id=445610 Bug ID: 445610 Summary: Cannot create new archives Product: ark Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: elvis.angelac...@kde.org Reporter: k...@privat.broulik.de CC: aa...@kde.org, rthoms...@gmail.com Target Milestone: --- SUMMARY I am unable to create a new archive with Ark STEPS TO REPRODUCE 1. Start Ark 2. Click "Create New Archive" 3. Choose a folder 4. Choose a name 5. Choose a format (I tried .tar and .tar.lz4) OBSERVED RESULT Nothing happens, no archive file is created in the designated location, no error on terminal, no view change (remains on Welcome page) EXPECTED RESULT A new archive is created and opened SOFTWARE/OS VERSIONS Linux/KDE Plasma: git master as of 2021-11-16 ADDITIONAL INFORMATION Opening existing archives works, it just doesn't create new ones. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445599] mouse pointer klipper menu should paste a selected line by default
https://bugs.kde.org/show_bug.cgi?id=445599 David Edmundson changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- This is difficult to do safely and as such out of scope. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 445196] Open/Save File Dialog suffers from horrible tearing in Wayland under certain circumstances.
https://bugs.kde.org/show_bug.cgi?id=445196 --- Comment #9 from David Edmundson --- Edit, it's not quite the same. The window parent is null in both cases. Though it's still a bit odd that we're creating two platform windows when we open the open dialog. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445587] Response to mouse clicks broken
https://bugs.kde.org/show_bug.cgi?id=445587 --- Comment #7 from tgnff...@gmail.com --- @geisserml That one and the `qtdeclarative5-dev-tools`. `apt` keeps the previous packages somewhere in `/var/caches`. If you hadn't cleared it yet, you should be able to find it. Also, the Present Windows seems to work. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 415151] Add A Plugin To Mount OneDrive
https://bugs.kde.org/show_bug.cgi?id=415151 Rafael Lima changed: What|Removed |Added CC||rafael.palma.l...@gmail.com --- Comment #1 from Rafael Lima --- As of 5.23 this feature hasn't been implemented yet. Maybe Dolphin could simply list all configured rclone mounts so that the user can choose to mount/umount them. However this would still leave it to the user to config the rclone mount using the command line. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 445609] New: Navigating rclone mounts too slow with KDE file picker, but very fast on Dolphin
https://bugs.kde.org/show_bug.cgi?id=445609 Bug ID: 445609 Summary: Navigating rclone mounts too slow with KDE file picker, but very fast on Dolphin Product: frameworks-kio Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Open/save dialogs Assignee: kio-bugs-n...@kde.org Reporter: rafael.palma.l...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY I have some rclone mounts on my system for my OneDrive accounts (personal, business, etc). They're all working fine and when I navigate them using Dolphin, they're very responsive. Opening folders with many items usually takes less than a second to load using Dolphin. However, when I'm on an application (f.i. Kate, LibreOffice, etc) and I use the File Picker to navigate the rclone mounts and choose a place to save the file, the navigation happens very slowly. Even for folders with few items, it takes about 10 seconds to load. Folders with many items take 30 seconds. I don't know exactly the problem, but it seems the file picker is caching recursively the entire folder contents, whereas Dolphin only loads the current folder contents. STEPS TO REPRODUCE 1. Create a rclone mout 2. Navigate it on Dolphin 3. Navigate the same mount with the file picker OBSERVED RESULT On Dolphin everything is snappy... using the file picker on the same mount is very slow. EXPECTED RESULT Both should have the same speed. SOFTWARE/OS VERSIONS Operating System: Kubuntu 21.10 KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.11.0-38-generic (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-10750H CPU @ 2.60GHz Memory: 15,5 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 445196] Open/Save File Dialog suffers from horrible tearing in Wayland under certain circumstances.
https://bugs.kde.org/show_bug.cgi?id=445196 --- Comment #8 from David Edmundson --- It's the issue seen before. QWidget::winId() called on a non-toplevel First QPlatformWindow #10 0x75d6f6ce in QWidget::winId (this=0x5f2023e0) at ../../include/QtWidgets/../../../../../src/Qt5/qtbase/src/widgets/kernel/qwidget.h:132 #11 0x701aef0d in KDEPlatformFileDialogHelper::restoreSize (this=0x5efd5ef0) Second QPlatformWindow #10 0x75d7b760 in QWidget::setVisible (this=this@entry=0x7fffc610, visible=visible@entry=true) at /home/david/projects/kde5/src/Qt5/qtbase/src/widgets/kernel/qwidget.cpp:8044 #11 0x75f79542 in QDialog::setVisible (this=this@entry=0x7fffc610, visible=visible@entry=true) note how this is a different widget. Code in KDEPlatformFileDialogHelper is probably wrong. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445608] When pressing and holding META+ the window should not just flicker by constantly toggling minimize but instead toggle maximizing the window once
https://bugs.kde.org/show_bug.cgi?id=445608 elypter changed: What|Removed |Added CC||elyp...@yahoo.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445608] New: When pressing and holding META+ the window should not just flicker by constantly toggling minimize but instead toggle maximizing the window once
https://bugs.kde.org/show_bug.cgi?id=445608 Bug ID: 445608 Summary: When pressing and holding META+ the window should not just flicker by constantly toggling minimize but instead toggle maximizing the window once Product: plasmashell Version: 5.23.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: elyp...@yahoo.de CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY when pressing meta+ you can bring the window at position into focus. pressing it again hides it. holding however just switches hiding and unhiding in quick succession which is not very useful. instead a long press of the shortcut should toggle maximize the window a single time. SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Kernel Version: 5.15.2-arch1-1 (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5500U with Radeon Graphics Memory: 7.2 GiB of RAM Graphics Processor: AMD RENOIR -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 445607] New: Unhandled amd64-freebsd syscall: 247
https://bugs.kde.org/show_bug.cgi?id=445607 Bug ID: 445607 Summary: Unhandled amd64-freebsd syscall: 247 Product: valgrind Version: unspecified Platform: FreeBSD Ports OS: FreeBSD Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: serpent7...@gmail.com Target Milestone: --- Created attachment 143640 --> https://bugs.kde.org/attachment.cgi?id=143640=edit swi-pl crash log when running under valgrind SUMMARY Running swi prolog under FreeBSD 12.2 results in unhandled syscall 247 warning followed by a swi-pl crash. Looking at /usr/src/sys/sys/syscall.h it looks like syscall 247 is SYS_clock_getcpuclockid2. STEPS TO REPRODUCE 1. run `valgring swipl` on FreeBSD OBSERVED RESULT A lot of warnings "unhandled amd64-freebsd syscall: 247" printed, followed by swi-pl segfault (attached log file). EXPECTED RESULT No warnings, swi-pl should work normally under valgrind. SOFTWARE/OS VERSIONS FreeBSD DaemONX 12.2-RELEASE-p7 FreeBSD 12.2-RELEASE-p7 GENERIC amd64 valgrind-3.18.1 SWI-Prolog version 8.2.3 for amd64-freebsd ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
