[filelight] [Bug 472546] filelight says no QT platform plugin and crashes on launching filelight
https://bugs.kde.org/show_bug.cgi?id=472546 --- Comment #1 from GK --- Seems to work again as of 23.0.4.3-1426 Unsure if this was a nightly-build transient. I was wondering if the the scoop file light manifest could point instead to a monthly stable builds that have been checked to work instead of nightly builds direct from the kde-factory. AFAICT, these automatic new nightlies, build every 3 days, and its is not clear if there are any changes into the app's codebase. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 472911] New: Fails to compile on Qt6
https://bugs.kde.org/show_bug.cgi?id=472911 Bug ID: 472911 Summary: Fails to compile on Qt6 Classification: Applications Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Keywords: qt6 Severity: major Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: justin.zo...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- [ 40%] Building CXX object hg/CMakeFiles/fileviewhgplugin.dir/fileviewhgplugin.cpp.o cd /builddir/build/BUILD/dolphin-plugins-e025dd9/redhat-linux-build/hg && /usr/bin/g++ -DKCOREADDONS_LIB -DKF_DISABLE_DEPRECATED_BEFORE_AND_AT=0x055a00 -DKPLUGINFACTORY_PLUGIN_CLASS_INTERNAL_NAME=fileviewhgplugin_factory -DQT_CORE5COMPAT_LIB -DQT_CORE_LIB -DQT_DBUS_LIB -DQT_DISABLE_DEPRECATED_BEFORE=0x050f00 -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_NO_DEBUG -DQT_NO_FOREACH -DQT_NO_KEYWORDS -DQT_NO_URL_CAST_FROM_STRING -DQT_WIDGETS_LIB -DQT_XML_LIB -DTRANSLATION_DOMAIN=\"fileviewhgplugin\" -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -Dfileviewhgplugin_EXPORTS -I/builddir/build/BUILD/dolphin-plugins-e025dd9/redhat-linux-build/hg -I/builddir/build/BUILD/dolphin-plugins-e025dd9/hg -I/builddir/build/BUILD/dolphin-plugins-e025dd9/redhat-linux-build/hg/fileviewhgplugin_autogen/include -isystem /usr/include/qt6/QtCore -isystem /usr/include/qt6 -isystem /usr/lib64/qt6/mkspecs/linux-g++ -isystem /usr/include/qt6/QtWidgets -isystem /usr/include/qt6/QtGui -isystem /usr/include/KF6/KIOCore -isystem /usr/include/KF6/KIO -isystem /usr/include/KF6/KCoreAddons -isystem /usr/include/qt6/QtNetwork -isystem /usr/include/qt6/QtDBus -isystem /usr/include/KF6/KI18n -isystem /usr/include/KF6/KWidgetsAddons -isystem /usr/include/KF6/KTextEditor -isystem /usr/include/KF6/KParts -isystem /usr/include/KF6/KXmlGui -isystem /usr/include/qt6/QtXml -isystem /usr/include/KF6/KConfig -isystem /usr/include/KF6/KConfigCore -isystem /usr/include/KF6/KConfigWidgets -isystem /usr/include/KF6/KConfigGui -isystem /usr/include/KF6/KColorScheme -isystem /usr/include/KF6/KCompletion -isystem /usr/include/KF6/KSyntaxHighlighting -isystem /usr/include/qt6/QtCore5Compat -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-U_FORTIFY_SOURCE,-D_FORTIFY_SOURCE=3 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -mbranch-protection=standard -fasynchronous-unwind-tables -fstack-clash-protection -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer -fno-operator-names -fno-exceptions -Wall -Wextra -Wcast-align -Wchar-subscripts -Wformat-security -Wno-long-long -Wpointer-arith -Wundef -Wnon-virtual-dtor -Woverloaded-virtual -Werror=return-type -Werror=init-self -Wvla -Wdate-time -Wsuggest-override -Wlogical-op -DNDEBUG -std=gnu++17 -fPIC -fvisibility=hidden -fvisibility-inlines-hidden -MD -MT hg/CMakeFiles/fileviewhgplugin.dir/fileviewhgplugin.cpp.o -MF CMakeFiles/fileviewhgplugin.dir/fileviewhgplugin.cpp.o.d -o CMakeFiles/fileviewhgplugin.dir/fileviewhgplugin.cpp.o -c /builddir/build/BUILD/dolphin-plugins-e025dd9/hg/fileviewhgplugin.cpp /builddir/build/BUILD/dolphin-plugins-e025dd9/hg/fileviewhgplugin.cpp:34:10: fatal error: KApplicationTrader: No such file or directory 34 | #include | ^~~~ compilation terminated. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472909] Kickoff is taking focus away after being closed with meta key.
https://bugs.kde.org/show_bug.cgi?id=472909 --- Comment #1 from c354r@gmail.com --- Created attachment 160677 --> https://bugs.kde.org/attachment.cgi?id=160677=edit Loosing focus on closing by meta key -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 472910] Cannot see any devices in bluetooth pairing wizard
https://bugs.kde.org/show_bug.cgi?id=472910 Justin Zobel changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 472910] New: Cannot see any devices in bluetooth pairing wizard
https://bugs.kde.org/show_bug.cgi?id=472910 Bug ID: 472910 Summary: Cannot see any devices in bluetooth pairing wizard Classification: Plasma Product: Bluedevil Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wizard Assignee: now...@gmail.com Reporter: justin.zo...@gmail.com CC: n...@kde.org, plasma-b...@kde.org Target Milestone: --- 1. Open "Add Bluetooth Device" connection box 2. See no devices 3. Check bluetoothctl from a terminal 4. See devices available for pairing -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472909] New: Kickoff is taking focus away after being closed with meta key.
https://bugs.kde.org/show_bug.cgi?id=472909 Bug ID: 472909 Summary: Kickoff is taking focus away after being closed with meta key. Classification: Plasma Product: plasmashell Version: 5.27.7 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: c354r@gmail.com CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Press meta key, kickoff gets opened. 2. Press meta key again, kickoff gets closed. OBSERVED RESULT After kickoff was closed, focus does not return to the main window, it seems focus is retained by the panel. Although it works as normal when using mouse click or escape key. It is also happening on digital clock widget. EXPECTED RESULT 1. Press meta key to open kickoff, kickoff gets opened. 2. Press meta key to close kickoff, kickoff get closed. 3. Focus returns to main window. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Kernel Version: 6.4.7-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 6600H with Radeon Graphics Memory: 7.0 GiB of RAM Graphics Processor: AMD Radeon Graphics with Discrete Nvidia Graphics Manufacturer: LENOVO Product Name: 82SB System Version: IdeaPad Gaming 3 15ARH7 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 463247] Unable to create new KDE CONNECT SMS messages with "+New" - button greyed out
https://bugs.kde.org/show_bug.cgi?id=463247 Phani Pavan K changed: What|Removed |Added CC||kphanipa...@gmail.com --- Comment #9 from Phani Pavan K --- My Proposal: P1. The "+New" button appears and is enabled if (valid number is present in the search bar) AND (connected devices with sms capab is more than ZERO): Tooltip says what it says right now P2. The "+New" button appears but is greyed if (valid number is present in search bar) AND (connected devices equal to ZERO): Tooltip says "No Devices Connected" P3. The "+New" button doesn't appear otherwise, i.e. if (number in search bar is not valid). Additional Enhancements: A1. "+New" changes to "Open" if the number is already present in sms list Questions: Q1. Is "+" necessary in "+New"? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471375] Firefox url copy failure
https://bugs.kde.org/show_bug.cgi?id=471375 --- Comment #8 from Yani --- (In reply to Andrew Todd from comment #7) > > Should I report this to Mozilla? > > After you asked, I searched Mozilla's Bugzilla for related issues. > > I've just found an open bug at Mozilla that describes a workaround. I've > tested this workaround, and it seems to work for me. > > https://bugzilla.mozilla.org/show_bug.cgi?id=1791417 > > The workaround: > > Open System Settings -> Workspace Behavior -> General Behavior -> Middle > Click: Paste Selected Text > > Make sure that "Middle Click: Paste Selected Text" is checked. In other > words, make sure that it is enabled. > > Restart your system. > I've set it as you suggest. Seems like an unlikely fix as the issue is intermittent. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472662] When a widget is in edit mode, the bar with buttons disappears on mouseover
https://bugs.kde.org/show_bug.cgi?id=472662 --- Comment #5 from Nate Graham --- So when the mouse leaves the item container, the close timer starts. In Plasma 5, the two MouseAreas were somehow blocking this, but that doesn't seem to be working in Plasma 6. Frankly I'm struggling to understand how it would have worked in 5. But clearly input handling has changed in Qt 6 sufficiently that whatever made it work in Plasma 5 no longer does in 6. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 436538] kdeinit5: Qt: Session management error: networkIdsList argument is NULL
https://bugs.kde.org/show_bug.cgi?id=436538 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 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.
[frameworks-kinit] [Bug 409879] xdotool error KDEInit could not launch
https://bugs.kde.org/show_bug.cgi?id=409879 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #9 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.
[frameworks-kinit] [Bug 442322] lela star
https://bugs.kde.org/show_bug.cgi?id=442322 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.
[frameworks-kinit] [Bug 407855] Kdeinit5 unable to write to NFS share
https://bugs.kde.org/show_bug.cgi?id=407855 --- Comment #12 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.
[frameworks-kinit] [Bug 402743] kdeinit5 crashes the moment I navigate to smb://, Network > Samba Shares
https://bugs.kde.org/show_bug.cgi?id=402743 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.
[krita] [Bug 408182] Scaling with the transform tool deletes the selection
https://bugs.kde.org/show_bug.cgi?id=408182 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #21 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.
[frameworks-kdesignerplugin] [Bug 407073] Widget Event Calendar freezes up the desktop for 30 seconds or more.
https://bugs.kde.org/show_bug.cgi?id=407073 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.
[frameworks-kinit] [Bug 395143] Open files in Dolphin does not start corresponding program
https://bugs.kde.org/show_bug.cgi?id=395143 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 469016] Plasma panel visually (but not functionally) freezing with Wayland+Nvidia
https://bugs.kde.org/show_bug.cgi?id=469016 --- Comment #43 from fuyuyuyuyuyuyuy...@gmail.com --- Same issue Operating System: Arch Linux KDE Plasma Version: 5.27.7 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Kernel Version: 6.4.7-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-6700K CPU @ 4.00GHz Memory: 31.3 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2070/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: H170M-DS3H -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469016] Plasma panel visually (but not functionally) freezing with Wayland+Nvidia
https://bugs.kde.org/show_bug.cgi?id=469016 fuyuyuyuyuyuyuy...@gmail.com changed: What|Removed |Added CC||fuyuyuyuyuyuyuy...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 351579] Removing applet through context menu does not trigger remove animation
https://bugs.kde.org/show_bug.cgi?id=351579 --- Comment #4 from Noah Davis --- The relevant C++ code is currently in plasma-framework/src/plasma/applet.cpp and plasma-framework/src/plasma/private/applet_p.cpp -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 351579] Removing applet through context menu does not trigger remove animation
https://bugs.kde.org/show_bug.cgi?id=351579 Noah Davis changed: What|Removed |Added CC||noaha...@gmail.com --- Comment #3 from Noah Davis --- In case it helps anyone in the future, the issue is that the animation is defined in plasma-desktop/containments/desktop/package/contents/ui/ConfigOverlay.qml, so the QAction used by the menu can't use the same animation. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 472908] New: "Update software: Automatically" does not automatically install software updates for Flatpak
https://bugs.kde.org/show_bug.cgi?id=472908 Bug ID: 472908 Summary: "Update software: Automatically" does not automatically install software updates for Flatpak Classification: Applications Product: Discover Version: 5.27.7 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Updates (interactive) Assignee: plasma-b...@kde.org Reporter: ivb...@proton.me CC: aleix...@kde.org Target Milestone: --- SUMMARY The automatic software updater does not appear to do anything in Discover when enabled. I have packages installed as flatpaks through discover, but enabling the auto updater does not automatically update them. STEPS TO REPRODUCE 1. Enable automatic software updates: Enable `System Settings>Software Update>Update software>Automatically` 2. Observe that updates accumulate in discover, but they never get updated. OBSERVED RESULT Automatic updates do not occur EXPECTED RESULT I expect that when I enable "Update software: Automatically", the software in Discover would get automatically updated. SOFTWARE/OS VERSIONS Windows: n/a macOS: n/a Linux/KDE Plasma: Arch Linux, Kernel v6.4.7-arch1-2, KDE Plasma v5.27.7 KDE Plasma Version: v5.27.7 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION n/a -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 472907] New: Connect to devices through VPN connection, even on mobile data
https://bugs.kde.org/show_bug.cgi?id=472907 Bug ID: 472907 Summary: Connect to devices through VPN connection, even on mobile data Classification: Applications Product: kdeconnect Version: unspecified Platform: Android OS: Android 13.x Status: REPORTED Keywords: usability Severity: wishlist Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: sarcastic_mating...@simplelogin.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY Title. STEPS TO REPRODUCE 1. Set up KDE Connect. 2. Plug in a usable SIM card. 3. Turn off Wi-fi and connect to mobile data. 4. Connect to a VPN with all paired devices present. OBSERVED RESULT Nothing happened. EXPECTED RESULT KDE Connect seeks paired devices over the VPN connection and connects if found. SOFTWARE/OS VERSIONS Android 13 ADDITIONAL INFORMATION This should be an opt-in option, since many VPNs purely acts as a relay for address masking. Ideally, the user should be able to set a whitelist of allowed VPNs. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdesu] [Bug 452532] kdesu stopped working in KUbuntu due to sudo's use_pty option
https://bugs.kde.org/show_bug.cgi?id=452532 --- Comment #21 from pallaswept --- BTW, I've cross-referenced these issues to the original issue at sudo's github: https://github.com/sudo-project/sudo/issues/258 Thought someone ought to leave that link here somewhere :) I also just noticed this was reported a year and two months ago. This being a security hole in KDE, perhaps it ought to be bumped up the priority list a little? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdesu] [Bug 452532] kdesu stopped working in KUbuntu due to sudo's use_pty option
https://bugs.kde.org/show_bug.cgi?id=452532 pallaswept changed: What|Removed |Added CC||pallasw...@proton.me --- Comment #20 from pallaswept --- This is also breaking kdesu and thus YaST, on OpenSuSE. I discovered this when trying to run Yast software management, I'd get a bouncing icon and then nothing. Running the program from the CLI returns the following: > /usr/lib/YaST2/bin/sw_single_wrapper Don't need password!! kf.su: [ /home/abuild/rpmbuild/BUILD/kdesu-5.108.0/src/stubprocess.cpp : 215 ] Unknown request: "ok" I have run kwriteconfig5 --file kdesurc --group super-user-command --key super-user-command sudo so that kdesu will use sudo rather than su, so that sudoers will be respected by KDE. KDE frameworks got an update around the same time as this change rolled out, so the natural thought was that kdesu was broken, but it turns out to be this option. Running echo 'Defaults !use_pty' | sudo tee -a /etc/sudoers and then repeating the above instantly fixes it: > /usr/lib/YaST2/bin/sw_single_wrapper Don't need password!! and the GUI appears and works as intended. This option has been enabled for security reasons and accordingly kdesu needs to be updated to handle the new default behaviour securely, rather than a workaround that amounts to disabling the security measure. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 472904] Enable copy/pasting with Ctrl+c, Ctrl+v
https://bugs.kde.org/show_bug.cgi?id=472904 --- Comment #1 from mashkal2...@gmail.com --- *Ctrl+C sends SIGINT, not SIGTERM. That doesn't affect this feature request though -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 472906] New: MASSIVE amount of issues with GPU rendering
https://bugs.kde.org/show_bug.cgi?id=472906 Bug ID: 472906 Summary: MASSIVE amount of issues with GPU rendering Classification: Applications Product: kdenlive Version: 23.04.3 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: critical Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: gabrielpm2...@gmail.com Target Milestone: --- SUMMARY When rendering using GPU, on Windows 10 at least, SEVERAL issues can happen: -Screen Tearing that persists after closing the problem(only solves by doing a CTRL+ALT+DEL or restart) -Blackscreens(a worsen version of the above problem, usually after hours of editing and rendering) -Sometimes, any following render with different resolution(say, if I work on a tiktok after a youtube video) wont be rendered in the proper resolution, being instead a wide version contained inside the intended resolution -Images and effects may just, randomly take over the entire part of the video they're supposed to show at -etc STEPS TO REPRODUCE 1. Open KDEnlive 2. Edit for hours, do some rendering using GPU 3. Enjoy the several issues OBSERVED RESULT This only happens at random. Usually after 1h of editing/a few renders using GPU. SOFTWARE/OS VERSIONS Windows: 10 pro Latest drivers for my RTX 3060 and everything else, including bios. Irrelevant however, as it happened on a completely different setup before. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 472905] New: Missing plugin
https://bugs.kde.org/show_bug.cgi?id=472905 Bug ID: 472905 Summary: Missing plugin Classification: Applications Product: kdenlive Version: 23.04.3 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: Effects & Transitions Assignee: j...@kdenlive.org Reporter: gabrielpm2...@gmail.com Target Milestone: --- KDEnlive is missing the LADSPA Suppressor for Voice effect after this update STEPS TO REPRODUCE 1. Open Software 2. Look it up OBSERVED RESULT Lack of testing from devs resulted in yet another obvious problem EXPECTED RESULT Improvements for the next version, without regression SOFTWARE/OS VERSIONS Windows: 10, pro -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 472904] New: Enable copy/pasting with Ctrl+c, Ctrl+v
https://bugs.kde.org/show_bug.cgi?id=472904 Bug ID: 472904 Summary: Enable copy/pasting with Ctrl+c, Ctrl+v Classification: Applications Product: konsole Version: 23.04.3 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: copy-paste Assignee: konsole-de...@kde.org Reporter: mashkal2...@gmail.com Target Milestone: --- SUMMARY Feature request: when text is selected, ctrl+c and Ctrl+v copy and paste, rather than sending signals to the currently-running process. This feature is available in the VSCode console and the fact that it is missing from konsole is rather annoying. Always using Ctrl+Shift+C does not work since web browsers (both Firefox and Chrome) open devtools on Ctrl+Shift+C rather than copying, and have no way to rebind that. Having separate shortcuts for separate applications prevents building up muscle memory, and I have found myself accidentally stopping long-running processes and inadvertently opening browser devtools quite frequently due to the lack of this feature. STEPS TO REPRODUCE 1. Select text with mouse 2. Ctrl+C OBSERVED RESULT SIGTERM is sent EXPECTED RESULT text is copied ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[knotes] [Bug 472903] New: Crash
https://bugs.kde.org/show_bug.cgi?id=472903 Bug ID: 472903 Summary: Crash Classification: Applications Product: knotes Version: 5.23.80 Platform: Other OS: Linux Status: REPORTED Keywords: qt6 Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: justin.zo...@gmail.com CC: myr...@kde.org Target Milestone: --- #0 0x7f5b601a3a68 in QScopedPointer >::get (this=) at /usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/corelib/tools/qscopedpointer.h:111 #1 qGetPtrHelper > > (ptr=...) at /usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/corelib/global/qtclasshelpermacros.h:79 #2 QMenu::d_func (this=) at /usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/widgets/widgets/qmenu.h:29 #3 QMenu::popup (this=0x0, p=..., atAction=0x0) at /usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/widgets/widgets/qmenu.cpp:2290 #4 0x55ee22d002a8 in KNotesApp::slotActivateRequested(bool, QPoint const&) () #5 0x7f5b5edde394 in QtPrivate::QSlotObjectBase::call (a=0x7ffee857dd80, r=0x55ee232793c0, this=0x55ee233cd610) at /usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/corelib/kernel/qobjectdefs_impl.h:363 #6 doActivate (sender=0x7f5b440113a0, signal_index=4, argv=0x7ffee857dd80) at /usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/corelib/kernel/qobject.cpp:3992 #7 0x7f5b6125c208 in KStatusNotifierItem::activateRequested(bool, QPoint const&) () from /lib64/libKF6Notifications.so.6 #8 0x7f5b6128aeb8 in StatusNotifierItemAdaptor::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) () from /lib64/libKF6Notifications.so.6 #9 0x7f5b6128cb8f in StatusNotifierItemAdaptor::qt_metacall(QMetaObject::Call, int, void**) () from /lib64/libKF6Notifications.so.6 #10 0x7f5b60642d09 in QDBusConnectionPrivate::deliverCall (this=this@entry=0x7f5b44011470, object=object@entry=0x55ee233e3c60, msg=..., metaTypes=..., slotIdx=12) at /usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/dbus/qdbusintegrator.cpp:975 #11 0x7f5b60646266 in QDBusConnectionPrivate::activateCall (this=this@entry=0x7f5b44011470, object=0x55ee233e3c60, flags=flags@entry=273, msg=...) at /usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/dbus/qdbusintegrator.cpp:877 #12 0x7f5b60646dea in QDBusConnectionPrivate::activateCall (msg=..., flags=273, object=, this=0x7f5b44011470) at /usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/dbus/qdbusintegrator.cpp:823 #13 QDBusConnectionPrivate::activateObject (this=0x7f5b44011470, node=..., msg=..., pathStartPos=) at /usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/dbus/qdbusintegrator.cpp:1478 #14 0x7f5b6064945a in QDBusActivateObjectEvent::placeMetaCall (this=0x7f5b44013fb0) at /usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/dbus/qdbusintegrator.cpp:1598 #15 0x7f5b5edcfe57 in QObject::event (this=0x55ee23146f20, e=0x7f5b44013fb0) at /usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/corelib/kernel/qobject.cpp:1391 #16 0x7f5b5ffc0af8 in QApplicationPrivate::notify_helper (this=, receiver=0x55ee23146f20, e=0x7f5b44013fb0) at /usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/widgets/kernel/qapplication.cpp:3287 #17 0x7f5b5ed7cdb8 in QCoreApplication::notifyInternal2 (receiver=0x55ee23146f20, event=0x7f5b44013fb0) at /usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/corelib/kernel/qcoreapplication.cpp:1118 #18 0x7f5b5ed7cfbd in QCoreApplication::sendEvent (receiver=, event=) at /usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/corelib/kernel/qcoreapplication.cpp:1536 #19 0x7f5b5ed808d5 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55ee23148e00) at /usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/corelib/kernel/qcoreapplication.cpp:1898 #20 0x7f5b5ed80c0d in QCoreApplication::sendPostedEvents (receiver=, event_type=) at /usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/corelib/kernel/qcoreapplication.cpp:1757 #21 0x7f5b5f02108f in postEventSourceDispatch (s=0x55ee2318e0b0) at /usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/corelib/kernel/qeventdispatcher_glib.cpp:243 #22 0x7f5b5cd7648c in g_main_dispatch (context=0x7f5b44000f10) at ../glib/gmain.c:3460 #23 g_main_context_dispatch (context=0x7f5b44000f10) at ../glib/gmain.c:4200 #24 0x7f5b5cdd4648 in g_main_context_iterate.isra.0 (context=0x7f5b44000f10, block=1, dispatch=1, self=) at ../glib/gmain.c:4276 #25 0x7f5b5cd73b13 in g_main_context_iteration (context=0x7f5b44000f10, may_block=1) at ../glib/gmain.c:4343 #26 0x7f5b5f02092f in QEventDispatcherGlib::processEvents (this=0x55ee2314e920, flags=...) at /usr/src/debug/qt6-qtbase-6.5.2-1.fc38.x86_64/src/corelib/kernel/qeventdispatcher_glib.cpp:393 #27 0x7f5b5ed899f3 in QEventLoop::exec (this=this@entry=0x7ffee857e930, flags=..., flags@entry=...) at
[systemsettings] [Bug 472899] Play button is misplaced
https://bugs.kde.org/show_bug.cgi?id=472899 --- Comment #2 from Patrick Silva --- I use an integer size with a non-default font. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 472899] Play button is misplaced
https://bugs.kde.org/show_bug.cgi?id=472899 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Nate Graham --- Are you using a fractional point size with a non-default font? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472892] Plasma::Applet::removeInternalAction triggers infinite recursion and crashes plasmashell when closing the first "undo removing this widget" notification
https://bugs.kde.org/show_bug.cgi?id=472892 Fushan Wen changed: What|Removed |Added Version Fixed In||6.0 Latest Commit||https://invent.kde.org/fram ||eworks/plasma-framework/-/c ||ommit/cd5e4ab9cdec8c610ed8e ||01df01ff488966dfa4e Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #2 from Fushan Wen --- Git commit cd5e4ab9cdec8c610ed8e01df01ff488966dfa4e by Fushan Wen. Committed on 02/08/2023 at 03:13. Pushed by fusionfuture into branch 'master'. Applet: fix crash after a widget is removed or disabled In the connection with `QObject::destroyed`, there is no need to delete an action again, otherwise there is a double delete. FIXED-IN: 6.0 M +3-1src/plasma/applet.cpp https://invent.kde.org/frameworks/plasma-framework/-/commit/cd5e4ab9cdec8c610ed8e01df01ff488966dfa4e -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427668] If the panel has a shadow, make it not appear over windows, just the desktop
https://bugs.kde.org/show_bug.cgi?id=427668 Noah Davis changed: What|Removed |Added CC||jaku...@protonmail.com --- Comment #12 from Noah Davis --- *** Bug 472887 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472887] When placed at the top, panel places a shadow on top of windows.
https://bugs.kde.org/show_bug.cgi?id=472887 Noah Davis changed: What|Removed |Added Resolution|--- |DUPLICATE Severity|normal |wishlist CC||noaha...@gmail.com Status|REPORTED|RESOLVED --- Comment #2 from Noah Davis --- I'm pretty sure this is intentional behavior in the sense that everything is working correctly. The shadow is part of the Plasma theme. In order to remove or change the shadow, you have to modify the Plasma theme or choose a different Plasma theme. Still, I agree that it could look better. It seems like this bug report would also be solved by solving https://bugs.kde.org/show_bug.cgi?id=427668, so I will mark this as a duplicate of that one. *** This bug has been marked as a duplicate of bug 427668 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 468548] Toggling selection mode with spacebar, on, off, then on again, crashes dolphin
https://bugs.kde.org/show_bug.cgi?id=468548 --- Comment #16 from udo...@proton.me --- Created attachment 160676 --> https://bugs.kde.org/attachment.cgi?id=160676=edit New crash information added by DrKonqi dolphin (23.04.3) using Qt 5.15.10 When pressing the spacebar 3 times consecutively, Dolphin crashes. I'm using Nobara KDE, but the crash doesn't happen when I'm on KDE, only when I'm on bspwm. When running from the terminal, dolphin gives this output when crashing: QCoreApplication::postEvent: Unexpected null receiver KCrash: Application 'dolphin' crashing... KCrash: Attempting to start /usr/libexec/drkonqi QSocketNotifier: Invalid socket 6 and type 'Read', disabling... QSocketNotifier: Invalid socket 9 and type 'Read', disabling... QSocketNotifier: Invalid socket 19 and type 'Read', disabling... QSystemTrayIcon::setVisible: No Icon set [1] + 5001 suspended (signal) dolphin -- Backtrace (Reduced): #4 0x7f7f24c77df1 in QStyleSheetStyle::getDefaultStyleSheet() const () from /lib64/libQt5Widgets.so.5 #5 0x7f7f24c50d9b in QStyleSheetStyle::styleRules(QObject const*) const () from /lib64/libQt5Widgets.so.5 #6 0x7f7f24c588b7 in QStyleSheetStyle::renderRule(QObject const*, int, unsigned long long) const () from /lib64/libQt5Widgets.so.5 #7 0x7f7f24c5ac81 in QStyleSheetStyle::setGeometry(QWidget*) () from /lib64/libQt5Widgets.so.5 #8 0x7f7f24c5b206 in QStyleSheetStyle::unpolish(QWidget*) () from /lib64/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 468548] Toggling selection mode with spacebar, on, off, then on again, crashes dolphin
https://bugs.kde.org/show_bug.cgi?id=468548 udo...@proton.me changed: What|Removed |Added CC||udo...@proton.me -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472839] Discrete Canvas Rotation no longer snaps resulting angle to 15deg increments
https://bugs.kde.org/show_bug.cgi?id=472839 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/1880 -- You are receiving this mail because: You are watching all bug changes.
[kinfocenter] [Bug 387366] Energy page: Energy consumption statistics not available
https://bugs.kde.org/show_bug.cgi?id=387366 Ilpo Kantonen changed: What|Removed |Added CC||i...@iki.fi --- Comment #29 from Ilpo Kantonen --- I updated just Plasma to version 5.27.7 in Kubuntu 23.04. And I looked kinfocenter power consumption data. The kinfocenter displayed text that in this system it's possible to show poer consumption. Then I searches with Google and found this bug report. Mainboard: MSI Z490 A Pro Processor: i5-10400F Kubuntu 23.04 Plasma: 5.27.7 Kinfocenter and power started in console: $ kinfocenter KTranscript: Loaded property map: /usr/share/locale/fi/LC_SCRIPTS/ki18n5/general.pmapc KTranscript: Loaded module: /usr/share/locale/fi/LC_SCRIPTS/ki18n5/ki18n5.js kf.i18n: Interpolation "$[gen %1]" in "$[gen %1] " failed: "Non-string return value: undefined" kf.i18n: Interpolation "$[gen %1]" in "$[gen %1] käyttö" failed: "Non-string return value: undefined" kf.i18n: Interpolation "$[elat %1]" in " $[yleisnimi_..." failed: "Non-string return value: undefined" kf.i18n: Interpolation "$[elat %1]" in " $[yleisnimi_..." failed: "Non-string return value: undefined" kf.i18n: Interpolation "$[gen %1]" in "$[gen %1] käyttö" failed: "Non-string return value: undefined" kf.i18n: Interpolation "$[elat %1]" in " $[yleisnimi_..." failed: "Non-string return value: undefined" kf.xmlgui: cannot find .rc file "kinfocenterui.rc" for component "kinfocenter" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding loop detected for property "width" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding loop detected for property "width" QQmlEngine::setContextForObject(): Object already has a QQmlContext Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes. kf.sonnet.clients.hspell: HSpellDict::HSpellDict: Init failed file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding loop detected for property "implicitHeight" file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/ScrollablePage.qml:200:9: QML MouseArea: Binding loop detected for property "implicitHeight" kf.i18n: Interpolation "$[elat %1]" in "Tietoa $[yleisnimi_p..." failed: "Non-string return value: undefined" QQmlEngine::setContextForObject(): Object already has a QQmlContext file:///usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/templates/InlineMessage.qml:265:13: QML SelectableLabel: Binding loop detected for property "implicitWidth" Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations. Qt Quick Layouts: Detected recursive rearrange. Aborting after two iterations. file:///usr/share/kpackage/kcms/kcm_energyinfo/contents/ui/main.qml:31: Error: Cannot assign [undefined] to QObject* file:///usr/share/kpackage/kcms/kcm_energyinfo/contents/ui/main.qml:384: TypeError: Cannot read property 'temperature' of null file:///usr/share/kpackage/kcms/kcm_energyinfo/contents/ui/main.qml:384: TypeError: Cannot read property 'energyFullDesign' of null file:///usr/share/kpackage/kcms/kcm_energyinfo/contents/ui/main.qml:384: TypeError: Cannot read property 'energyFull' of null file:///usr/share/kpackage/kcms/kcm_energyinfo/contents/ui/main.qml:384: TypeError: Cannot read property 'energy' of null file:///usr/share/kpackage/kcms/kcm_energyinfo/contents/ui/main.qml:384: TypeError: Cannot read property 'voltage' of null file:///usr/share/kpackage/kcms/kcm_energyinfo/contents/ui/main.qml:384: TypeError: Cannot read property 'energyRate' of null file:///usr/share/kpackage/kcms/kcm_energyinfo/contents/ui/main.qml:384: TypeError: Cannot read property 'technology' of null file:///usr/share/kpackage/kcms/kcm_energyinfo/contents/ui/main.qml:384: TypeError: Cannot read property 'serial' of null file:///usr/share/kpackage/kcms/kcm_energyinfo/contents/ui/main.qml:384: TypeError: Cannot read property 'capacity' of null file:///usr/share/kpackage/kcms/kcm_energyinfo/contents/ui/main.qml:384: TypeError: Cannot read property 'chargePercent' of null file:///usr/share/kpackage/kcms/kcm_energyinfo/contents/ui/main.qml:384: TypeError: Cannot read property 'chargeState' of null file:///usr/share/kpackage/kcms/kcm_energyinfo/contents/ui/main.qml:384: TypeError: Cannot read property 'rechargeable' of null file:///usr/share/kpackage/kcms/kcm_energyinfo/contents/ui/Graph.qml:56: TypeError: Cannot read property 'x' of undefined -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 472902] Duplicate shortcut key causing error
https://bugs.kde.org/show_bug.cgi?id=472902 --- Comment #1 from Justin Zobel --- Created attachment 160675 --> https://bugs.kde.org/attachment.cgi?id=160675=edit error Error message screenshot -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 472902] New: Duplicate shortcut key causing error
https://bugs.kde.org/show_bug.cgi?id=472902 Bug ID: 472902 Summary: Duplicate shortcut key causing error Classification: Applications Product: konsole Version: 23.07.80 Platform: Other OS: Linux Status: REPORTED Keywords: qt6 Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: justin.zo...@gmail.com Target Milestone: --- Created attachment 160674 --> https://bugs.kde.org/attachment.cgi?id=160674=edit shortcuts menu Ctrl+Shift+C is duplicated on two identical shortcuts and causes an error when trying to use it. The screenshot attached shows the shortcuts menu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472662] When a widget is in edit mode, the bar with buttons disappears on mouseover
https://bugs.kde.org/show_bug.cgi?id=472662 --- Comment #4 from Nate Graham --- Ooh it's in ItemContainer::childMouseEventFilter -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 470381] Julia backend does not allow symlinked executable
https://bugs.kde.org/show_bug.cgi?id=470381 --- Comment #2 from hqu...@outlook.com --- Created attachment 160673 --> https://bugs.kde.org/attachment.cgi?id=160673=edit Screenshot showing that the julia backend works with symlink I attached a screenshot showing that the julia backend is really working and that the executable is a symlink. However, if I do the following, I get an error `Julia session can't login due internal julia problem with missing internal file - "/home/joshua/kde/src/lib/julia/sys.so"` 1. link julia to the current directory `ln -s $(which julia) ./julia` 2. add current directory to path `PATH=$(pwd):$PATH` 3. run cantor and select julia backend 4. try 1+1 From https://invent.kde.org/education/cantor/-/blob/670993d7bf38afcacd2914509d621761dd8e4e60/src/backends/julia/juliaserver/juliaserver.cpp#L27, the error occurs since the .so file cannot be found and the fallback path is `../lib/julia/sys.so`. So, I guess that the issue with symlinks depends on whether you also correctly symlink the lib/julia/sys.so file. However, the official installation instructions (https://julialang.org/downloads/platform/#linux_and_freebsd) for julia only recommends linking the julia binary and has no suggestions for also linking the shared library. Perhaps the restriction for symlinks could be removed and canonicalPath() could be used instead of dir().absolutePath() on line 32. (documentation for canonicalPath https://doc.qt.io/qt-5/qfileinfo.html#canonicalPath). This replacement allows the julia symlink in my current directory (which is on my path) to work. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472901] New: Screen flickers when switching virtual desktop with touchpad gesture and animations are off
https://bugs.kde.org/show_bug.cgi?id=472901 Bug ID: 472901 Summary: Screen flickers when switching virtual desktop with touchpad gesture and animations are off Classification: Plasma Product: kwin Version: 5.27.6 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: quinten@quinten.space Target Milestone: --- SUMMARY The screen flickers black for a frame or so when using the touchpad gesture to switch virtual desktops (three/four finger swipe). More specifically, it happens as soon as you release, and only when animations are disabled. STEPS TO REPRODUCE 1. Disable animations by dragging the "Animation speed" slider in systemsettings all the way to right. 2. Switch virtual desktops with 3/4 finger touchpad swipe. 3. Observe that the screen flickers black when releasing your fingers. OBSERVED RESULT Screen flickers black. EXPECTED RESULT Screen switches instantly to target desktop, without any visual flicker. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 38 kernel 6.4.6 (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION GPU: Intel UHD 620, Mesa 23.1.4 Graphics Platform: Wayland Wasn't sure which component to file against, so general. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472900] New: PSD import bug
https://bugs.kde.org/show_bug.cgi?id=472900 Bug ID: 472900 Summary: PSD import bug Classification: Applications Product: krita Version: 5.1.5 Platform: Other OS: Android 13.x Status: REPORTED Severity: critical Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: pinkd...@gmail.com Target Milestone: --- It seems that PSD import is not working properly. I use it along with Ibis and MediBang Paint, so I hope it will be improved soon. The device I am using is the Galaxy Tab S8 with Android 13. I am writing to you today to report a bug in your product. I have been using your product since January, and I have been experiencing a bug since the January update. I have been waiting for the bug to be fixed, but it has not been fixed yet. I am a Japanese user, so I am not very good at English. I would appreciate it if you could respond to me as soon as possible. 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. 2. 3. OBSERVED RESULT EXPECTED RESULT 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.
[okular] [Bug 472764] PDF form dropdown doesn't show up
https://bugs.kde.org/show_bug.cgi?id=472764 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/okular/-/merge_requests/788 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 472899] Play button is misplaced
https://bugs.kde.org/show_bug.cgi?id=472899 Patrick Silva changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 472899] New: Play button is misplaced
https://bugs.kde.org/show_bug.cgi?id=472899 Bug ID: 472899 Summary: Play button is misplaced Classification: Applications Product: systemsettings Version: master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_soundtheme Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com CC: isma...@gmail.com Target Milestone: --- Created attachment 160672 --> https://bugs.kde.org/attachment.cgi?id=160672=edit screenshot STEPS TO REPRODUCE 1. oen System Sounds KCM 2. observe the play button 3. OBSERVED RESULT as we can see in the attached screenshot, the play button is misplaced EXPECTED RESULT play button in the correct place SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.6.0 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 472898] New: Discover crashes early and often
https://bugs.kde.org/show_bug.cgi?id=472898 Bug ID: 472898 Summary: Discover crashes early and often Classification: Applications Product: Discover Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: dbkbusin...@yahoo.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-10-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: Discover crashes oftentimes when starting it, others when just using it. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x7f9917a50ac7 in PackageKitBackend::resolvePackages(QStringList const&) () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #5 0x7f9917a5a4b1 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #6 0x7f9917a54588 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/packagekit-backend.so #7 0x7f99330dd6f0 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f9934b62fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #9 0x7f99330b16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f99330b4681 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7f993310a153 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f99318627a9 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7f9931862a38 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #14 0x7f9931862acc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7f9933109836 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f99330b017b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f99330b82d6 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0xb88ce2a7 in ?? () #19 0x7f9932c461ca in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #20 0x7f9932c46285 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #21 0xb88ce811 in ?? () [Inferior 1 (process 1312929) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472662] When a widget is in edit mode, the bar with buttons disappears on mouseover
https://bugs.kde.org/show_bug.cgi?id=472662 --- Comment #3 from Nate Graham --- Haven't found the thing that causes ConfigOverlay's `open` property to get set to false when it's not hovered, but that seems to be the cause of the issue. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 471151] Paths are not entirely readable in Locations KCM
https://bugs.kde.org/show_bug.cgi?id=471151 --- Comment #19 from Patrick Silva --- $ systemsettings kcm_desktoppaths kf.xmlgui: cannot find .rc file "systemsettingsui.rc" for component "systemsettings" Using fontconfig file: "/home/stalker/.config/fontconfig/fonts.conf" Hspell: can't open /usr/share/hspell/hebrew.wgz.sizes. kf.sonnet.clients.hspell: HSpellDict::HSpellDict: Init failed qt.qml.typeresolution.cycle: Cyclic dependency detected between "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/private/MobileTextActionsToolBar.qml" and "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/private/TextFieldContextMenu.qml" qt.qml.typeresolution.cycle: Cyclic dependency detected between "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/private/MobileTextActionsToolBar.qml" and "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/Menu.qml" qt.qml.typeresolution.cycle: Cyclic dependency detected between "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/Menu.qml" qt.qml.typeresolution.cycle: Cyclic dependency detected between "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/private/MobileTextActionsToolBar.qml" and "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/private/TextFieldContextMenu.qml" qt.qml.typeresolution.cycle: Cyclic dependency detected between "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/private/MobileTextActionsToolBar.qml" and "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/Menu.qml" qt.qml.typeresolution.cycle: Cyclic dependency detected between "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/Menu.qml" qt.qml.typeresolution.cycle: Cyclic dependency detected between "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/private/MobileTextActionsToolBar.qml" and "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/private/TextFieldContextMenu.qml" qt.qml.typeresolution.cycle: Cyclic dependency detected between "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/private/MobileTextActionsToolBar.qml" and "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/Menu.qml" qt.qml.typeresolution.cycle: Cyclic dependency detected between "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/private/TextFieldContextMenu.qml" and "file:///usr/lib/x86_64-linux-gnu/qt6/qml/org/kde/desktop/Menu.qml" qml: The item SubCategoryPage_QMLTYPE_116(0x555c89cc5ea0) is already in the PageRow kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons: "Could not find plugin " kf.coreaddons:
[systemsettings] [Bug 471151] Paths are not entirely readable in Locations KCM
https://bugs.kde.org/show_bug.cgi?id=471151 --- Comment #18 from Nate Graham --- I suspect it's Qt 6.6, then. Can you run it in a terminal window with `systemsettings kcm_desktoppaths` and paste the output? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 471151] Paths are not entirely readable in Locations KCM
https://bugs.kde.org/show_bug.cgi?id=471151 --- Comment #17 from Patrick Silva --- The bug was fixed after closing this report and then reapppeared, I do not know when exactly. Possibly after Qt 6.6. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 472756] Infinite modal dialog in PDF form
https://bugs.kde.org/show_bug.cgi?id=472756 Albert Astals Cid changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/okular/-/commit/f940ca |hics/okular/-/commit/2e3163 |1e2eda350b6e556f21adbd330fc |e621e84afd6d13429a6582ccdd9 |99f8bb2 |ea79c99 --- Comment #5 from Albert Astals Cid --- Git commit 2e3163e621e84afd6d13429a6582ccdd9ea79c99 by Albert Astals Cid. Committed on 02/08/2023 at 00:16. Pushed by aacid into branch 'release/23.08'. Forms: Don't run focusin action when gaining focus because of window management Adobe Reader doesn't do it, and with reason, because otherwise we end up with: * Run focus in script * script shows alert() * form loses focus and gains it again once the alert() is closed * infinite loop The same fix we did in e457ceb73146790c5d4a9914182433ab4002815e but for the rest of the widgets (cherry picked from commit f940ca1e2eda350b6e556f21adbd330fc99f8bb2) M +1-1part/formwidgets.cpp https://invent.kde.org/graphics/okular/-/commit/2e3163e621e84afd6d13429a6582ccdd9ea79c99 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 472756] Infinite modal dialog in PDF form
https://bugs.kde.org/show_bug.cgi?id=472756 Albert Astals Cid changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/grap ||hics/okular/-/commit/f940ca ||1e2eda350b6e556f21adbd330fc ||99f8bb2 Status|ASSIGNED|RESOLVED --- Comment #4 from Albert Astals Cid --- Git commit f940ca1e2eda350b6e556f21adbd330fc99f8bb2 by Albert Astals Cid. Committed on 02/08/2023 at 00:07. Pushed by aacid into branch 'master'. Forms: Don't run focusin action when gaining focus because of window management Adobe Reader doesn't do it, and with reason, because otherwise we end up with: * Run focus in script * script shows alert() * form loses focus and gains it again once the alert() is closed * infinite loop The same fix we did in e457ceb73146790c5d4a9914182433ab4002815e but for the rest of the widgets M +1-1part/formwidgets.cpp https://invent.kde.org/graphics/okular/-/commit/f940ca1e2eda350b6e556f21adbd330fc99f8bb2 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 472897] New: Feature request: Keep system (DE) unlocked but allow screen off
https://bugs.kde.org/show_bug.cgi?id=472897 Bug ID: 472897 Summary: Feature request: Keep system (DE) unlocked but allow screen off Classification: Applications Product: kdeconnect Version: 23.04.3 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: renyune...@gmail.com Target Milestone: --- SUMMARY Currently, kdeconnect does provide an option to keep system unlocked when device is connected. However, it also keeps the screen on all the time. It would be ideal if it can add an option to allow screen going off, while still keeping system unlocked. This behaviour itself is at least supported by KDE Plasma. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 471151] Paths are not entirely readable in Locations KCM
https://bugs.kde.org/show_bug.cgi?id=471151 --- Comment #16 from Nate Graham --- I cannot reproduce the issue no matter how I try. Did this just start happening again when you upgraded to Qt 6.6 in Neon, by any chance? Or was it broken before Neon shipped Qt 6.6, and you're just now reporting the issue? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 472732] Multi -screen output cannot be switched from the unified output mode to the laptop screen mode.
https://bugs.kde.org/show_bug.cgi?id=472732 --- Comment #4 from Nate Graham --- Thanks. And can you confirm that the same problem happens when you access this feature from the System Tray widget, and not the OSD? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467170] Ability to define window border colours
https://bugs.kde.org/show_bug.cgi?id=467170 Nate Graham changed: What|Removed |Added Resolution|NOT A BUG |INTENTIONAL -- You are receiving this mail because: You are watching all bug changes.
[Oxygen] [Bug 472896] New: Oxygen window decoration gradient is absent under wayland
https://bugs.kde.org/show_bug.cgi?id=472896 Bug ID: 472896 Summary: Oxygen window decoration gradient is absent under wayland Classification: Plasma Product: Oxygen Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: win deco Assignee: unassigned-b...@kde.org Reporter: nope1000...@gmail.com 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 *** On Plasma 5 and also as far as i know Plasma 6, oxygen window decorations look plain on wayland when on x11 a gradient is shown acting in conjunction with the widget theme. On Plasma 6 gradient on widgets theme is also gone, when under X11 both the widgets gradient and window decoration gradient are displayed correctly STEPS TO REPRODUCE 1. Set Oxygen window decoration theme 2. 3. OBSERVED RESULT Titlebar is coloured with a plain color, on Plasma 6, window background itself looks also plain. EXPECTED RESULT Titlebar is coloured with a gradient pattern SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 38 / KDE Neon Unstable (available in About System) KDE Plasma Version: 5.27.6 / 6 Git KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION I don´t tried intensively the Plasma 6 case since Wayland session crashes a lot and I'm on nvidia and on VMs doesn't even start. I know this might not be the priority one bug to fix but is a nice to have feature that has been lost with the transition to wayland. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467209] Clicking "Virtual keyboard" button doesn't make virtual keyboard show up; you have to tap it with a touchscreen
https://bugs.kde.org/show_bug.cgi?id=467209 --- Comment #5 from Nate Graham --- Yes, because those patches I submitted haven't been merged yet. -- You are receiving this mail because: You are watching all bug changes.
[Welcome Center] [Bug 472691] Welcome center buttons don’t look and feel like buttons
https://bugs.kde.org/show_bug.cgi?id=472691 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #6 from Nate Graham --- The buttons in Discover and the buttons in Welcome Center are using the same QQC2.Button primitive with the same styling. I think you see the shadow in Discover more easily because the button is on a white background, so the gray shadow has better contrast there. They also have the same edge highlight on hover. I don't think there's a bug to solve in Welcome Center. If anything could be done, it would be in the Breeze QStyle, to make a global change to all buttons. But if we do that, it would apply to all buttons and we'd start to accumulate complaints that buttons feel too heavy. So I don't think there's a change we can make here, sorry. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 450551] Battery charge limit is not preserved after reboot on many laptops that support charge limits; need to write it on every boot
https://bugs.kde.org/show_bug.cgi?id=450551 Nate Graham changed: What|Removed |Added Alias|Kevlar700 | -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472890] digiKam Email with Thunderbird
https://bugs.kde.org/show_bug.cgi?id=472890 --- Comment #4 from Bert Broekstra --- Maik, In the DK Miscellaneous Settings, I opened the Appearance tab and removed the check for "Use native file dialogs from system". I then started DK, selected Email, selected TB from the Email list, selected Find on TB, which opened the Applications folder. Selected TB which then opened the binaries folder. Result: The Email function works! Thanks much for your help. Will you be adding this procedure to the DK User Manual for OSx users? As a side note, I removed DK from Full Disk Access in OSx Privacy Settings. This prevents DK from accessing the Applications folder, so DK does need Full Disk Access. Bert On 8/1/23 2:39 PM, Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=472890 > > --- Comment #3 from Maik Qualmann --- > digiKam needs the file path to Thunderbird to start it via parameter. > So you have to manually select the path in digiKam to Thunderbird. > This can be prevented by not using the native macOS File dialog. > However, the setting is located in the Appearance tab. > > Maik > -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467170] Ability to define window border colours
https://bugs.kde.org/show_bug.cgi?id=467170 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG CC||k...@davidedmundson.co.uk --- Comment #1 from David Edmundson --- there are ways to set palettes from application. Anything else isn't something we're looking at doing. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 472895] New: Accent
https://bugs.kde.org/show_bug.cgi?id=472895 Bug ID: 472895 Summary: Accent Classification: Plasma Product: lattedock Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: nicolasthier...@hotmail.fr Target Milestone: --- Created attachment 160671 --> https://bugs.kde.org/attachment.cgi?id=160671=edit Global App menu is not visible when mouse is hover because of missing accent color. SUMMARY Latte dock is not using accent color when using custom color scheme (not plasma palette). STEPS TO REPRODUCE 1. Settings => Appearance => Palette => Dark 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 349785] Intelligent auto-hide mode ("Dodge Windows") that hides the panel only when windows are maximized or move over it
https://bugs.kde.org/show_bug.cgi?id=349785 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=472894 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472894] Bring back "Windows Go Below" and "Windows Go Above" Panel visibility modes
https://bugs.kde.org/show_bug.cgi?id=472894 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=349785 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472894] New: Bring back "Windows Go Below" and "Windows Go Above" Panel visibility modes
https://bugs.kde.org/show_bug.cgi?id=472894 Bug ID: 472894 Summary: Bring back "Windows Go Below" and "Windows Go Above" Panel visibility modes Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Keywords: qt6 Severity: wishlist Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: n...@kde.org CC: niccolo.venera...@gmail.com Target Milestone: 1.0 These visibility modes were not removed deliberately as a result of an intentional design decision, but rather for technical reasons due to the port to standardized Wayland layer-shell protocol; see https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1521 and https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2924. In essence, these features would have been prohibitively challenging to implement on Wayland following the port to use the layer-shell. And the features were removed for X11 too to unify the experience across platforms and not make the KWin code excessively complex. This bug report tracks re-adding the features in some capacity. Ideally before Plasma 6 ships, either these modes will be brought back, or else we'll be able to implement Bug 349785 as an acceptable (and much-requested) alternative. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472887] When placed at the top, panel places a shadow on top of windows.
https://bugs.kde.org/show_bug.cgi?id=472887 --- Comment #1 from jaku...@protonmail.com --- Created attachment 160670 --> https://bugs.kde.org/attachment.cgi?id=160670=edit I think it introduces too much contrast, I also assume it's maybe fixed in the newer version of kde plasma. I'll check tomorrow. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472893] New: Second drag of a desktop file causes its thumbnail to jump back to the position it had before the first drag
https://bugs.kde.org/show_bug.cgi?id=472893 Bug ID: 472893 Summary: Second drag of a desktop file causes its thumbnail to jump back to the position it had before the first drag Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Keywords: qt6 Severity: normal Priority: NOR Component: Folder Assignee: plasma-b...@kde.org Reporter: n...@kde.org CC: h...@kde.org Target Milestone: 1.0 STEPS TO REPRODUCE 1. Have or put some files on your desktop 2. Reboot 3. Drag one of the desktop files to a different location 4. Immediately drag it again, to somewhere else OBSERVED RESULT On the second drag, the thumbnail of the file being dragged snaps back to its location after step 2! EXPECTED RESULT The thumbnail of the file being dragged stays glued to the pointer -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472890] digiKam Email with Thunderbird
https://bugs.kde.org/show_bug.cgi?id=472890 --- Comment #3 from Maik Qualmann --- digiKam needs the file path to Thunderbird to start it via parameter. So you have to manually select the path in digiKam to Thunderbird. This can be prevented by not using the native macOS File dialog. However, the setting is located in the Appearance tab. Maik -- You are receiving this mail because: You are watching all bug changes.
[kdev-python] [Bug 472816] Crash parsing Python file
https://bugs.kde.org/show_bug.cgi?id=472816 --- Comment #5 from Praise --- I don't really know - you should ask OpenSUSE Leap devs. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472890] digiKam Email with Thunderbird
https://bugs.kde.org/show_bug.cgi?id=472890 --- Comment #2 from Bert Broekstra --- Maik, I added DK to have Full Disk Access (FDA) under the Privacy & Security category. OSx describes FDA as: Allow the applications below to access data like Mail, Messages, Safari, Home, Backups and certain administrative settings for all users. Under the Files and Folder section, DK shows it has FDA. Result: Adding DK for FDA made no difference when selecting Email within DK. In DK's Miscellaneous section, I did not find a place to add a native field dialog for Thunderbird. Bert On 8/1/23 1:34 PM, Maik Qualmann wrote: > https://bugs.kde.org/show_bug.cgi?id=472890 > > Maik Qualmann changed: > > What|Removed |Added > > CC||metzping...@gmail.com > > --- Comment #1 from Maik Qualmann --- > You will need to navigate to the folder that contains the Thunderbird > executable. You may need to enable the native file dialog in the digKam > settings under Miscellaneous-> Behavior. > > Maik > -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472892] Plasma::Applet::removeInternalAction triggers infinite recursion and crashes plasmashell when closing the first "undo removing this widget" notification
https://bugs.kde.org/show_bug.cgi?id=472892 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from Nate Graham --- Looks to be fixed already by https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/837! -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 460616] disInstr(arm64): unhandled instruction 0x4E819402
https://bugs.kde.org/show_bug.cgi?id=460616 William Ashley changed: What|Removed |Added Attachment #160568|0 |1 is obsolete|| --- Comment #3 from William Ashley --- Created attachment 160669 --> https://bugs.kde.org/attachment.cgi?id=160669=edit Patch to add FEAT_DotProd support -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 471151] Paths are not entirely readable in Locations KCM
https://bugs.kde.org/show_bug.cgi?id=471151 --- Comment #15 from Patrick Silva --- Created attachment 160668 --> https://bugs.kde.org/attachment.cgi?id=160668=edit screenshot2 Desktop path is still not entirely readable. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472892] New: Plasma::Applet::removeInternalAction triggers infinite recursion and crashes plasmashell when closing the first "undo removing this widget" notification
https://bugs.kde.org/show_bug.cgi?id=472892 Bug ID: 472892 Summary: Plasma::Applet::removeInternalAction triggers infinite recursion and crashes plasmashell when closing the first "undo removing this widget" notification Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Keywords: qt6 Severity: crash Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: n...@kde.org CC: notm...@gmail.com Target Milestone: 1.0 STEPS TO REPRODUCE 1. Reboot 2. Add a widget to the desktop 3. Remove the widget via any means 4. Click the close button on the "Undo removing this widget" notification OBSERVED RESULT Plasma crashes: #0 0x7f61083cb864 in operator<(QString const&, QString const&) (s2=, s1=...) at /usr/include/qt6/QtCore/qstringview.h:137 #1 std::less::operator()(QString const&, QString const&) const (__y=, __x=..., this=) at /usr/include/c++/13/bits/stl_function.h:408 #2 std::_Rb_tree, std::_Select1st >, std::less, std::allocator > >::_M_lower_bound(std::_Rb_tree_node > const*, std::_Rb_tree_node_base const*, QString const&) const (this=0xcb26a8, __k=, __y=, __x=0x5875710) at /usr/include/c++/13/bits/stl_tree.h:1968 #3 std::_Rb_tree, std::_Select1st >, std::less, std::allocator > >::find(QString const&) const (this=0xcb26a8, __k=) at /usr/include/c++/13/bits/stl_tree.h:2545 #4 0x7f61080ade81 in std::map, std::allocator > >::find(QString const&) const (__x=..., this=0xcb26a8) at /usr/include/c++/13/bits/stl_map.h:1244 #5 QMap::value(QString const&, QAction* const&) const (defaultValue=, key=..., this=0x5e03e98) at /usr/include/qt6/QtCore/qmap.h:360 #6 Plasma::Applet::removeInternalAction(QString const&) (this=0x5af7fb0, name=...) at /home/nate/kde/src/plasma-framework/src/plasma/applet.cpp:672 #7 0x7f6104bddcd4 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffe6be4a1d0, r=0x5af7fb0, this=0x5803700) at /usr/src/debug/qt6-qtbase-6.5.1-2.fc38.x86_64/src/corelib/kernel/qobjectdefs_impl.h:363 #8 doActivate(QObject*, int, void**) (sender=0x57e4750, signal_index=0, argv=0x7ffe6be4a1d0) at /usr/src/debug/qt6-qtbase-6.5.1-2.fc38.x86_64/src/corelib/kernel/qobject.cpp:3992 #9 0x7f6104bd4757 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x57e4750, m=m@entry=0x7f61050042a0, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe6be4a1d0) at /usr/src/debug/qt6-qtbase-6.5.1-2.fc38.x86_64/src/corelib/kernel/qobject.cpp:4052 #10 0x7f6104bd4811 in QObject::destroyed(QObject*) (this=this@entry=0x57e4750, _t1=, _t1@entry=0x57e4750) at /usr/src/debug/qt6-qtbase-6.5.1-2.fc38.x86_64/redhat-linux-build/src/corelib/kernel/moc_qobject.cpp:266 #11 0x7f6104bdb5b2 in QObject::~QObject() (this=0x57e4750, __in_chrg=) at /usr/src/debug/qt6-qtbase-6.5.1-2.fc38.x86_64/src/corelib/kernel/qobject.cpp:1014 #12 0x7f6104bdbc25 in QObject::~QObject() (this=0x57e4750, __in_chrg=) at /usr/src/debug/qt6-qtbase-6.5.1-2.fc38.x86_64/src/corelib/kernel/qobject.cpp:1121 #13 0x7f61080adea9 in Plasma::Applet::removeInternalAction(QString const&) (this=0x5af7fb0, name=...) at /home/nate/kde/src/plasma-framework/src/plasma/applet.cpp:675 #14 0x7f6104bddcd4 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7ffe6be4a480, r=0x5af7fb0, this=0x5803700) at /usr/src/debug/qt6-qtbase-6.5.1-2.fc38.x86_64/src/corelib/kernel/qobjectdefs_impl.h:363 #15 doActivate(QObject*, int, void**) (sender=0x57e4750, signal_index=0, argv=0x7ffe6be4a480) at /usr/src/debug/qt6-qtbase-6.5.1-2.fc38.x86_64/src/corelib/kernel/qobject.cpp:3992 #16 0x7f6104bd4757 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (sender=sender@entry=0x57e4750, m=m@entry=0x7f61050042a0, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe6be4a480) --Type for more, q to quit, c to continue without paging--c at /usr/src/debug/qt6-qtbase-6.5.1-2.fc38.x86_64/src/corelib/kernel/qobject.cpp:4052 #17 0x7f6104bd4811 in QObject::destroyed(QObject*) (this=this@entry=0x57e4750, _t1=, _t1@entry=0x57e4750) at /usr/src/debug/qt6-qtbase-6.5.1-2.fc38.x86_64/redhat-linux-build/src/corelib/kernel/moc_qobject.cpp:266 #18 0x7f6104bdb5b2 in QObject::~QObject() (this=0x57e4750, __in_chrg=) at /usr/src/debug/qt6-qtbase-6.5.1-2.fc38.x86_64/src/corelib/kernel/qobject.cpp:1014 #19 0x7f6104bdbc25 in QObject::~QObject() (this=0x57e4750, __in_chrg=) at /usr/src/debug/qt6-qtbase-6.5.1-2.fc38.x86_64/src/corelib/kernel/qobject.cpp:1121 #20 0x7f61080adea9 in Plasma::Applet::removeInternalAction(QString const&) (this=0x5af7fb0, name=...) at
[systemsettings] [Bug 471151] Paths are not entirely readable in Locations KCM
https://bugs.kde.org/show_bug.cgi?id=471151 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REOPENED|NEEDSINFO --- Comment #14 from Nate Graham --- Sigh. Please attach another screenshot that shows it still happening. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472881] Grouping/Versioning: add grouping by filename with versioning
https://bugs.kde.org/show_bug.cgi?id=472881 --- Comment #12 from Eyal --- I think it should be standalone. Regarding priority it's of course your decision. I can only ask you to consider this: Digikam has versioning. Digikam has grouping. But the two features don't work together. If I batch process thousands of photos which creates thousands of image pairs, I have no way to group them except manually one by one. So I only ask that grouping support Digikam's own versioning scheme. Not "every grouping problem", not support versioning scheme of other tools. In any case, thank you for the attention and patience. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469576] In Volume OSD, "100%" volume string is a multi-line string
https://bugs.kde.org/show_bug.cgi?id=469576 Kai Uwe Broulik changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/-/commi |ma/plasma-workspace/-/commi |t/9737efa79440b65db303030f3 |t/94b2c3d1d4a72d70d48751395 |4f0039f1c9cd6a0 |4601c2cf723e673 --- Comment #14 from Kai Uwe Broulik --- Git commit 94b2c3d1d4a72d70d487513954601c2cf723e673 by Kai Uwe Broulik. Committed on 01/08/2023 at 21:41. Pushed by fvogt into branch 'Plasma/5.27'. OSD: Fix size calculation for progress value Use a common function for formatting the percent, so placeholder 100% label will use the exact formatting used by the label next to the progress bar. Also use font advanceWidth, which is the appropriate means of calculating the bounding box of text in this case. Also ceil it to avoid subpixel alignment. And to be absolutely sure disable word wrapping. (cherry picked from commit 9737efa79440b65db303030f34f0039f1c9cd6a0) M +8-3lookandfeel/org.kde.breeze/contents/osd/OsdItem.qml https://invent.kde.org/plasma/plasma-workspace/-/commit/94b2c3d1d4a72d70d487513954601c2cf723e673 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 471151] Paths are not entirely readable in Locations KCM
https://bugs.kde.org/show_bug.cgi?id=471151 Patrick Silva changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #13 from Patrick Silva --- This bug persists. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 436272] Changing the wallpaper sets the wallpaper, but the KCM does not remember it
https://bugs.kde.org/show_bug.cgi?id=436272 --- Comment #4 from Patrick Silva --- *** Bug 454966 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 454966] The 'Change background' popup of SDDM themes does not show the custom background in use
https://bugs.kde.org/show_bug.cgi?id=454966 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #4 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 436272 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472003] Clicks on systray icons have no effect
https://bugs.kde.org/show_bug.cgi?id=472003 --- Comment #9 from Patrick Silva --- Weird. I have even created a bootlable usb flash drive with neon-unstable-20230730-1119.iso and I can reproduce using mouse and touchpad. Clipboard and Media Player applets are unusable too - none of their buttons respond to clicks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472687] With thick panel, Application Launcher's CompactRepresentation overlaps adjacent widgets
https://bugs.kde.org/show_bug.cgi?id=472687 Nate Graham changed: What|Removed |Added Summary|Application Launcher icon's |With thick panel, |overlays the tray. |Application Launcher's ||CompactRepresentation ||overlaps adjacent widgets CC||n...@kde.org Severity|normal |minor Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #4 from Nate Graham --- Whoops! Can reproduce. I'll see if I can fix it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 472876] Slideshow background mode is not working
https://bugs.kde.org/show_bug.cgi?id=472876 Nate Graham changed: What|Removed |Added Severity|normal |major Ever confirmed|0 |1 CC||n...@kde.org, ||qydwhotm...@gmail.com Status|REPORTED|CONFIRMED --- Comment #1 from Nate Graham --- Can reproduce. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 472868] Doesn't Compile with LLVM's libc++ and compiler-rt
https://bugs.kde.org/show_bug.cgi?id=472868 nekone...@protonmail.ch changed: What|Removed |Added Resolution|FIXED |WAITINGFORINFO -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 472872] Tooltips have inconsistent height and font size
https://bugs.kde.org/show_bug.cgi?id=472872 Nate Graham changed: What|Removed |Added Assignee|unassigned-b...@kde.org |plasma-b...@kde.org Component|general |tooltips CC||k...@davidedmundson.co.uk, ||m...@ratijas.tk, ||notm...@gmail.com Product|kde |frameworks-plasma -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 472868] Doesn't Compile with LLVM's libc++ and compiler-rt
https://bugs.kde.org/show_bug.cgi?id=472868 nekone...@protonmail.ch changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED --- Comment #3 from nekone...@protonmail.ch --- ``` [100%] Linking CXX executable ../bin/plasmatube ld.lld: error: undefined symbol: _Unwind_Resume >>> referenced by qmetatype.h:0 (/usr/include/qt/QtCore/qmetatype.h:0) >>> >>> CMakeFiles/plasmatube.dir/plasmatube_autogen/mocs_compilation.cpp.o:(QMetaTypeIdQObject>> 8>::qt_metatype_id()) >>> referenced by main.cpp:0 >>> (/usr/src/debug/plasmatube-git/plasmatube/src/main.cpp:0) >>> CMakeFiles/plasmatube.dir/main.cpp.o:(main) >>> referenced by main.cpp:0 >>> (/usr/src/debug/plasmatube-git/plasmatube/src/main.cpp:0) >>> >>> CMakeFiles/plasmatube.dir/main.cpp.o:(main::$_5::__invoke(QQmlEngine*, >>> QJSEngine*)) >>> referenced 161 more times clang-15: error: linker command failed with exit code 1 (use -v to see invocation) make[2]: *** [src/CMakeFiles/plasmatube.dir/build.make:297: bin/plasmatube] Error 1 make[1]: *** [CMakeFiles/Makefile2:336: src/CMakeFiles/plasmatube.dir/all] Error 2 make: *** [Makefile:136: all] Error 2 ``` -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 472872] Tooltips have inconsistent height and font size
https://bugs.kde.org/show_bug.cgi?id=472872 --- Comment #3 from Nate Graham --- Our styling code can be found at: - https://invent.kde.org/frameworks/plasma-framework/-/blob/master/src/declarativeimports/plasmacomponents3/ToolTip.qml - https://invent.kde.org/frameworks/qqc2-desktop-style/-/blob/master/org.kde.desktop/ToolTip.qml -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472881] Grouping/Versioning: add grouping by filename with versioning
https://bugs.kde.org/show_bug.cgi?id=472881 Maik Qualmann changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472881] Grouping/Versioning: add grouping by filename with versioning
https://bugs.kde.org/show_bug.cgi?id=472881 Maik Qualmann changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REPORTED --- Comment #11 from Maik Qualmann --- Bug 318357 addresses the problem of grouping filenames with different schemes, not only versioning but also. So possibly to be able to group different file names as plugins and not to integrate every grouping problem individually. Well, I can make your bug standalone again, but like bug 338882, it's a low priority at the moment, there are more important things to do. Maybe next year we can get a GSoC-2024 student to work on it. Maik -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 472872] Tooltips have inconsistent height and font size
https://bugs.kde.org/show_bug.cgi?id=472872 Nate Graham changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||n...@kde.org --- Comment #2 from Nate Graham --- Can reproduce. When it happens, the following it printed to the journal log: Aug 01 13:35:53 Liberator plasmashell[270504]: :1:26: QML ToolTip: Binding loop detected for property "implicitHeight" I can reproduce this with Kickoff (which uses a PlasmaComponents3.Tooltip) and Elisa (which uses a QQC2.ToolTip). So either our styling code is broken in the same way in both places, or this is a Qt bug. Commenting out our implicitHeight overrides from both doesn't fix the problem, so I'm leaning towards a Qt bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469576] In Volume OSD, "100%" volume string is a multi-line string
https://bugs.kde.org/show_bug.cgi?id=469576 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/-/commi ||t/9737efa79440b65db303030f3 ||4f0039f1c9cd6a0 --- Comment #13 from Kai Uwe Broulik --- Git commit 9737efa79440b65db303030f34f0039f1c9cd6a0 by Kai Uwe Broulik. Committed on 01/08/2023 at 21:24. Pushed by broulik into branch 'master'. OSD: Fix size calculation for progress value Use a common function for formatting the percent, so placeholder 100% label will use the exact formatting used by the label next to the progress bar. Also use font advanceWidth, which is the appropriate means of calculating the bounding box of text in this case. Also ceil it to avoid subpixel alignment. And to be absolutely sure disable word wrapping. M +8-3lookandfeel/org.kde.breeze/contents/osd/OsdItem.qml https://invent.kde.org/plasma/plasma-workspace/-/commit/9737efa79440b65db303030f34f0039f1c9cd6a0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472890] digiKam Email with Thunderbird
https://bugs.kde.org/show_bug.cgi?id=472890 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- You will need to navigate to the folder that contains the Thunderbird executable. You may need to enable the native file dialog in the digKam settings under Miscellaneous-> Behavior. Maik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472662] When a widget is in edit mode, the bar with buttons disappears on mouseover
https://bugs.kde.org/show_bug.cgi?id=472662 --- Comment #2 from Nate Graham --- Ok, so the problem here is that we have two MouseAreas in ConfigOverlay.qml that are supposed to inhibit exiting Edit Mode when they're hovered, and that's not working in Plasma 6. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 472891] New: kdevelop crash
https://bugs.kde.org/show_bug.cgi?id=472891 Bug ID: 472891 Summary: kdevelop crash Classification: Applications Product: kdevelop Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: doc.ev...@gmail.com Target Milestone: --- Application: kdevelop (5.10.221202 (22.12.2)) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-10-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: switched to another file-editor tab while performing compilation; crash occurred. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: KDevelop (kdevelop), signal: Segmentation fault [KCrash Handler] #4 0x7f6d00d0d1dc in QAccessibleObject::object() const () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #5 0x7f6d017b618a in QAccessibleWidget::isValid() const () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #6 0x7f6d00d06848 in QAccessibleEvent::accessibleInterface() const () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #7 0x7f6d00d06d6d in QAccessible::updateAccessibility(QAccessibleEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #8 0x7f6cfe1f84ae in KateViewInternal::cursorMoved() () from /lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #9 0x7f6cfe1fefb6 in KateViewInternal::updateCursor(KTextEditor::Cursor, bool, bool, bool, bool) () from /lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #10 0x7f6cfe201378 in KateViewInternal::placeCursor(QPoint const&, bool, bool) () from /lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #11 0x7f6cfe2069f8 in KateViewInternal::mousePressEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libKF5TextEditor.so.5 #12 0x7f6d015a4db8 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7f6d01562fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7f6d0156b552 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #15 0x7f6d008b16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7f6d0156965e in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #17 0x7f6d015bdbd8 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f6d015c0f60 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f6d01562fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f6d008b16f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f6d00d3d3ed in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #22 0x7f6d00d11cac in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #23 0x7f6cf4afbeca in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #24 0x7f6cfc5d47a9 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7f6cfc5d4a38 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7f6cfc5d4acc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7f6d00909836 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7f6d008b017b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7f6d008b82d6 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x5646a35ee699 in ?? () #31 0x7f6d004461ca in __libc_start_call_main (main=main@entry=0x5646a35e9cc0, argc=argc@entry=1, argv=argv@entry=0x7fff3238aed8) at ../sysdeps/nptl/libc_start_call_main.h:58 #32 0x7f6d00446285 in __libc_start_main_impl (main=0x5646a35e9cc0, argc=1, argv=0x7fff3238aed8, init=, fini=, rtld_fini=, stack_end=0x7fff3238aec8) at ../csu/libc-start.c:360 #33 0x5646a35ef281 in ?? () [Inferior 1 (process 3449) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472855] Low free space notification has a generic icon
https://bugs.kde.org/show_bug.cgi?id=472855 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/fram ||eworks/knotifications/-/com ||mit/0367d529c61f46142487f85 ||62e77c2c2ef2d81d5 --- Comment #2 from Kai Uwe Broulik --- Git commit 0367d529c61f46142487f8562e77c2c2ef2d81d5 by Kai Uwe Broulik. Committed on 01/08/2023 at 21:07. Pushed by broulik into branch 'master'. Re-introduce IconName fallback to global config If the event has no icon, try whether the notifyrc has a global icon. This went missing in the KNotifyConfig cleanup. M +3-0src/notifybypopup.cpp M +3-0src/notifybyportal.cpp https://invent.kde.org/frameworks/knotifications/-/commit/0367d529c61f46142487f8562e77c2c2ef2d81d5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472855] Low free space notification has a generic icon
https://bugs.kde.org/show_bug.cgi?id=472855 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/knotifications/-/merge_requests/117 -- You are receiving this mail because: You are watching all bug changes.
