[kate] [Bug 478629] Kate is very slow to Launch, and very slow to open even a simple Text file with a couple paragraphs (even on a fresh Win11 install)
https://bugs.kde.org/show_bug.cgi?id=478629 Waqar Ahmed changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #9 from Waqar Ahmed --- Thanks for testing :) It was a few patches, most noticeably I think the removal of dbus on windows by Christoph might have helped improved the startup times. There might be more small improvements in the future. Will close this for now. -- You are receiving this mail because: You are watching all bug changes.
[kweather] [Bug 485488] KWeather widget is incompatible with Plasma 6
https://bugs.kde.org/show_bug.cgi?id=485488 Björn Bidar (Thaodan) changed: What|Removed |Added CC||bjorn.bi...@thaodan.de --- Comment #3 from Björn Bidar (Thaodan) --- The widget is not marked as supported but shows this error: file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/main.qml:452:25: Type FullRepresentation unavailable file:///usr/share/plasma/plasmoids/org.kde.plasma.weather/contents/ui/FullRepresentation.qml:38:24: Cannot assign object of type "QQC2.Action" to property of type "Action_QMLTYPE_130*" as the former is neither the same as the latter nor a sub-class of it. -- You are receiving this mail because: You are watching all bug changes.
[Alligator] [Bug 479190] content can be scrolled out of its page
https://bugs.kde.org/show_bug.cgi?id=479190 Justin Zobel changed: What|Removed |Added Status|REOPENED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||jus...@kde.org --- Comment #5 from Justin Zobel --- I can't replicate this in Alligator built from git. What version are you running? And how are you scrolling left/right? -- You are receiving this mail because: You are watching all bug changes.
[Alligator] [Bug 480749] Crash when opening redstrate post and maximizing Alligator
https://bugs.kde.org/show_bug.cgi?id=480749 Justin Zobel changed: What|Removed |Added CC||jus...@kde.org Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 486487] New: Open new files in tabs not working
https://bugs.kde.org/show_bug.cgi?id=486487 Bug ID: 486487 Summary: Open new files in tabs not working Classification: Applications Product: okular Version: 23.08.1 Platform: Microsoft Windows OS: Other Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: tgran...@outlook.com Target Milestone: --- SUMMARY On Windows 11 Pro using version 23.09 "Open new files in tabs" does not change the behavior of opening new files in their own window. PDF Backend Version 0.6.5 A PDF file renderer, Using Poppler 23.09.0 STEPS TO REPRODUCE 1. Install Okular from Microsoft store on Windows 11 pro 2. Open Okular for the first time, go to Settings -> General -> Program Features: and check "Open new files in tabs" and leave "Switch to existing tab if file is already open" checked. 3. Try to open two different PDF documents from file explorer OBSERVED RESULT Subsequent PDF documents open in their own application windows. EXPECTED RESULT Subsequent PDF documents should open in new tabs in the original application window. SOFTWARE/OS VERSIONS Windows: 11 Pro KDE Plasma Version: Not sure KDE Frameworks Version: 5.109.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 475357] Regression in Dolphin 23.08.1 - Expandable folders in Details view mode broken
https://bugs.kde.org/show_bug.cgi?id=475357 Anon changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 485287] 4 finger touchpad swipe up/down very inconsistent over time.
https://bugs.kde.org/show_bug.cgi?id=485287 mira...@mirandastreeter.com changed: What|Removed |Added CC||mira...@mirandastreeter.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 392879] AC Power Energy Saving settings are ignored
https://bugs.kde.org/show_bug.cgi?id=392879 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 484702] Numlock off after disconnect
https://bugs.kde.org/show_bug.cgi?id=484702 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #8 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484878] Plasma crashes after wakeup from suspend when clicking on the Kickoff launcher
https://bugs.kde.org/show_bug.cgi?id=484878 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |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.
[kdenlive] [Bug 484651] title- and video clips disappearing
https://bugs.kde.org/show_bug.cgi?id=484651 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #7 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 485725] Spectacle UI ignores user theme settings
https://bugs.kde.org/show_bug.cgi?id=485725 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 480759] Onion Skins don't immediately reappear after scrubbing.
https://bugs.kde.org/show_bug.cgi?id=480759 --- Comment #7 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485710] Dolphin "Open with" not remembering application
https://bugs.kde.org/show_bug.cgi?id=485710 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 484816] xdg-open doesn't work with dolphin
https://bugs.kde.org/show_bug.cgi?id=484816 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468890] Spectacle consistently crashes in ViewerWindow::~ViewerWindow() when trying to take a screenshot from the main window
https://bugs.kde.org/show_bug.cgi?id=468890 --- Comment #6 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 486484] [Feature Request] Speech recognition (VOSK/Whisper) to template title instead of subtitles
https://bugs.kde.org/show_bug.cgi?id=486484 Bug Janitor Service changed: What|Removed |Added Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 484452] Documentation is unavailable
https://bugs.kde.org/show_bug.cgi?id=484452 Samuel Jimenez changed: What|Removed |Added CC||the.real.samuel.jimenez@gma ||il.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486034] clicklockd, a mouse accessibility tool doesn't work correctly on Wayland
https://bugs.kde.org/show_bug.cgi?id=486034 --- Comment #3 from Bruno Filipe --- Here's some reference for expected multiseat behavior (from https://wayland.freedesktop.org/libinput/doc/latest/seats.html) if the same button is pressed on different devices, the button should only be considered logically pressed once. if the same button is released on one device, the button should be considered logically down if still down on another device. if two different buttons or keys are pressed on different devices, the logical state is that of both buttons/keys down. if a button is pressed on one device and another device moves, this should count as dragging. if two touches are down on different devices, the logical state is that of two touches down. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 486486] Build fails with LTO
https://bugs.kde.org/show_bug.cgi?id=486486
--- Comment #1 from Eli Schwartz ---
https://invent.kde.org/office/kmymoney/-/blob/b49b51460c3314562fb88d81a28b58f5637f2b23/kmymoney/dialogs/kcurrencyeditdlg.cpp#L51
```
// duplicated eMenu namespace from menuenums.h for consistency
// there shouldn't be any clash, because we don't need menuenums.h here
namespace eMenu {
enum class Action {
// *
// The currency menu
// *
NewCurrency, RenameCurrency, DeleteCurrency,
SetBaseCurrency,
```
no clash?
--
You are receiving this mail because:
You are watching all bug changes.
[kmymoney] [Bug 486486] New: Build fails with LTO
https://bugs.kde.org/show_bug.cgi?id=486486 Bug ID: 486486 Summary: Build fails with LTO Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: buildsystem Assignee: kmymoney-de...@kde.org Reporter: eschwart...@gmail.com Target Milestone: --- Created attachment 169124 --> https://bugs.kde.org/attachment.cgi?id=169124=edit build.log I tried to build with the following *FLAGS to optimize the build: `-flto=4 -Werror=odr -Werror=lto-type-mismatch -Werror=strict-aliasing` Note the -Werror=* flags are used to help detect cases where the compiler tries to optimize by assuming UB cannot exist in the source code -- if it does exist, ordinarily the code would be miscompiled, and this says to make the miscompilation a fatal error. I got this error: ``` FAILED: bin/kmymoney : && /usr/bin/x86_64-pc-linux-gnu-g++ -march=native -fstack-protector-all -O2 -pipe -fdiagnostics-color=always -frecord-gcc-switches -flto=4 -Werror=odr -Werror=lto-type-mismatch -Werror=strict-aliasing -Wformat -Werror=format-security -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 -fdiagnostics-color=always -fexceptions -Wall -Wextra -Wlogical-op -Wno-null-dereference -Wshadow -Wunused -Wno-misleading-indentation -Wsuggest-override -Wcast-qual -Wformat=2 -fno-common -Wl,--enable-new-dtags -Wl,-O1 -Wl,--as-needed -flto=4 -Werror=odr -Werror=lto-type-mismatch -Werror=strict-aliasing -Wl,--defsym=__gentoo_check_ldflags__=0 -Wl,--as-needed -Wl,--allow-multiple-definition-Wl,--no-undefined kmymoney/CMakeFiles/kmymoney.dir/kmymoney_autogen/mocs_compilation.cpp.o kmymoney/CMakeFiles/kmymoney.dir/main.cpp.o kmymoney/CMakeFiles/kmymoney.dir/kmymoney.cpp.o kmymoney/CMakeFiles/kmymoney.dir/pluginloader.cpp.o kmymoney/CMakeFiles/kmymoney.dir/kmymoneyadaptor.cpp.o kmymoney/CMakeFiles/kmymoney.dir/qrc_kmymoney.cpp.o -o bin/kmymoney -Wl,-rpath,/var/tmp/portage/app-office/kmymoney-5.1.3/work/kmymoney-5.1.3_build/lib: lib/libviews.a lib/libkmymoney_base.a lib/libkmymoney_common.a lib/libnewuserwizard.a lib/libnewaccountwizard.a lib/libnewinvestmentwizard.a lib/libnewloanwizard.a lib/libendingbalancedlg.a lib/libwizardpages.a lib/libdialogs.a lib/libwidgets.a lib/libsettings.a lib/libconverter.a lib/libkmm_menus.so.5.1.3 lib/libkmm_widgets.so.5.1.3 lib/libinterfaces.a /usr/lib64/libQt5WebEngineWidgets.so.5.15.13 /usr/lib64/libQt5WebEngineCore.so.5.15.13 /usr/lib64/libQt5WebChannel.so.5.15.13 lib/libkmm_printer.so.5.1.3 lib/libkmm_models.so.5.1.3 /usr/lib64/libKF5ItemModels.so.5.115.0 /usr/lib64/libKF5Notifications.so.5.115.0 lib/libonlinetask_interfaces.a lib/libkmymoney_base.a lib/libkmymoney_common.a lib/libkmm_settings.so.5.1.3 /usr/lib64/libKF5KIOFileWidgets.so.5.115.0 /usr/lib64/libKF5Bookmarks.so.5.115.0 /usr/lib64/libKF5KIONTLM.so.5.115.0 lib/libkmm_utils_webconnect.a lib/libkmm_utils_platformtools.a lib/libnewaccountwizard.a lib/libkmymoneywizard.a lib/libkmm_csvimportercore.so.5.1.3 lib/libkmm_mymoney.so.5.1.3 lib/libkmm_plugin.so.5.1.3 lib/libkmm_icons.so.5.1.3 lib/libkmm_payeeidentifier.so.5.1.3 /usr/lib64/libKF5KCMUtils.so.5.115.0 /usr/lib64/libQt5Quick.so.5.15.13 /usr/lib64/libQt5QmlModels.so.5.15.13 /usr/lib64/libQt5Qml.so.5.15.13 /usr/lib64/libKF5XmlGui.so.5.115.0 /usr/lib64/libQt5PrintSupport.so.5.15.13 /usr/lib64/libKF5ItemViews.so.5.115.0 /usr/lib64/libalkimia5.so.8.1.2 /usr/lib64/libKF5TextWidgets.so.5.115.0 /usr/lib64/libKF5SonnetUi.so.5.115.0 /usr/lib64/libKF5KIOWidgets.so.5.115.0 /usr/lib64/libKF5IconThemes.so.5.115.0 /usr/lib64/libKF5ConfigWidgets.so.5.115.0 /usr/lib64/libKF5Codecs.so.5.115.0 /usr/lib64/libKF5Auth.so.5.115.0 /usr/lib64/libKF5Completion.so.5.115.0 /usr/lib64/libKF5ConfigGui.so.5.115.0 /usr/lib64/libKF5KIOGui.so.5.115.0 /usr/lib64/libKF5KIOCore.so.5.115.0 /usr/lib64/libKF5Service.so.5.115.0 /usr/lib64/libKF5I18n.so.5.115.0 /usr/lib64/libKF5ConfigCore.so.5.115.0 /usr/lib64/libKF5AuthCore.so.5.115.0 /usr/lib64/libQt5Network.so.5.15.13 /usr/lib64/libKF5Solid.so.5.115.0 /usr/lib64/libQt5Xml.so.5.15.13 /usr/lib64/libKF5JobWidgets.so.5.115.0 /usr/lib64/libKF5WidgetsAddons.so.5.115.0 /usr/lib64/libKF5CoreAddons.so.5.115.0 /usr/lib64/libQt5Widgets.so.5.15.13 /usr/lib64/libKF5WindowSystem.so.5.115.0 /usr/lib64/libQt5Gui.so.5.15.13 /usr/lib64/libX11.so /usr/lib64/libQt5DBus.so.5.15.13 /usr/lib64/libQt5Core.so.5.15.13 /usr/lib64/libgmp.so /usr/lib64/libsqlcipher.so && cd /var/tmp/portage/app-office/kmymoney-5.1.3/work/kmymoney-5.1.3_build/lib && /usr/bin/cmake -E create_symlink . kmymoney
[kdeconnect] [Bug 468105] Desktop displays deleted messages
https://bugs.kde.org/show_bug.cgi?id=468105 --- Comment #6 from Simon Redman --- (In reply to MikMak from comment #5) > @simon sorry for the mood of my comment it was not appropriate and I was > indeed surprised that the incident had not received a response. > I do try to reply to every bug report. It's not nice when someone goes to the effort to file a report and doesn't get a reply. > I do understand it's not easy, it's an open source project and we have to > accept that not everything is perfect. I apologize for that. > Thanks. Apology accepted. > In fact I looked how I could contribute to your project, and I will be happy > to do this. But I am not sure I could help. I am on nixos, don't use KDE, > etc... But I would really like to help for this project. > Feel free to join us on Matrix and talk about how you could help. To take this example, a distro-agnostic project could be to add support for hiding archived messages in the KDE Connect Android app. https://matrix.to/#/!KPnlFCXuKzRXyhSxnY:kde.org?via=matrix.org=kde.org=mozilla.org > Anyway, I deleted the archived messages on my phone and after a while, not > immediately, kdeconnect no longer displayed the messages. Good to hear! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 486437] Incorrect rendering on glyph that have round side/corner
https://bugs.kde.org/show_bug.cgi?id=486437 --- Comment #1 from g311571...@gmail.com --- It happen obviously when I increase the font size and then decrease. Maybe it is a off-by-one pixel problem? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 486485] New: System tray does not show options
https://bugs.kde.org/show_bug.cgi?id=486485 Bug ID: 486485 Summary: System tray does not show options Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: esteban7...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org Target Milestone: --- Created attachment 169123 --> https://bugs.kde.org/attachment.cgi?id=169123=edit System tray does not show options *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. Install KDE Neon 2. Click on any icon in the system tray 3. OBSERVED RESULT System tray does not show options EXPECTED RESULT System tray icons work correctly SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: KDE NEON (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 486484] New: [Feature Request] Speech recognition (VOSK/Whisper) to template title instead of subtitles
https://bugs.kde.org/show_bug.cgi?id=486484 Bug ID: 486484 Summary: [Feature Request] Speech recognition (VOSK/Whisper) to template title instead of subtitles Classification: Applications Product: kdenlive Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: j...@kdenlive.org Reporter: moo...@outlook.com Target Milestone: --- Template titles are more customizable for effects and better than static subtitles. [Feature Request] -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485456] With Qt 6.7, System Tray popup is inappropriately resized to a tiny nub
https://bugs.kde.org/show_bug.cgi?id=485456 Esteban Vidal González changed: What|Removed |Added CC||esteban7...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Alligator] [Bug 465221] Drawer doesn't go away when tapping on items
https://bugs.kde.org/show_bug.cgi?id=465221 Justin Zobel changed: What|Removed |Added CC||jus...@kde.org --- Comment #2 from Justin Zobel --- Still present on git master. -- You are receiving this mail because: You are watching all bug changes.
[Alligator] [Bug 478078] In some posts, images start to flicker when made too big
https://bugs.kde.org/show_bug.cgi?id=478078 Justin Zobel changed: What|Removed |Added Ever confirmed|0 |1 CC||jus...@kde.org Status|REPORTED|CONFIRMED --- Comment #3 from Justin Zobel --- Can confirm this on latest build from git master. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486483] New: restarting plasma-plasmashell.service causes loss of all notification history
https://bugs.kde.org/show_bug.cgi?id=486483 Bug ID: 486483 Summary: restarting plasma-plasmashell.service causes loss of all notification history Classification: Plasma Product: plasmashell Version: master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: plasma-b...@kde.org Reporter: pa...@bonedaddy.net CC: k...@privat.broulik.de Target Milestone: 1.0 SUMMARY When the Plasma Shell is restarted, it looses all notification history. STEPS TO REPRODUCE 1. Get an application to send a notification. 2. Verify the notification is in the history. 3. Run `systemctl restart plasma-plasmashell.service` 4. Check the notification history again. OBSERVED RESULT The notification history is empty after the restart. EXPECTED RESULT The notification history is preserved after restarts. SOFTWARE/OS VERSIONS KDE Neon: neon-unstable-20240428-1118.iso (available in About System) KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION I discovered this on Debian trixie with KDE Plasma Desktop 5 and then verified it was still present in the latest KDE Neon unstable distribution. The restarts on Debian were due to plasmashell crashes, but I also want to safely be able to do systemctl restarts based on needrestart output after library upgrades. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476440] Moving panels in Storyboard Docker erases image layer data for all frames on save
https://bugs.kde.org/show_bug.cgi?id=476440 Freya Lupen changed: What|Removed |Added CC||alexyanghaoch...@gmail.com --- Comment #7 from Freya Lupen --- *** Bug 486393 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 486393] reordering the storyboard will cause all boards to go blank white, restarting won't help
https://bugs.kde.org/show_bug.cgi?id=486393 Freya Lupen changed: What|Removed |Added CC||penguinflyer2...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Freya Lupen --- *** This bug has been marked as a duplicate of bug 476440 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483803] Screen does not turn back on after Powerdevil turns it off.
https://bugs.kde.org/show_bug.cgi?id=483803 Jakob Petsovits changed: What|Removed |Added Assignee|plasma-b...@kde.org |kwin-bugs-n...@kde.org Component|general |wayland-generic Product|Powerdevil |kwin --- Comment #6 from Jakob Petsovits --- (In reply to stevenmcfeely42 from comment #5) > I have been testing this for the past 48 hours and it appears to work. > Setting Environment="KWIN_DRM_NO_AMS=1" allows my desktop's monitor to > properly wake up. Thanks for testing. Let's reassign the bug report to KWin in that case. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 486482] New: LSP plugin server is not working for HTML files
https://bugs.kde.org/show_bug.cgi?id=486482 Bug ID: 486482 Summary: LSP plugin server is not working for HTML files Classification: Applications Product: kate Version: 22.12.3 Platform: PiSi Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plugin-snippets Assignee: kwrite-bugs-n...@kde.org Reporter: jairoquilumbaqu...@gmail.com Target Milestone: --- SUMMARY kate lsp plugin is not working for vscode-html-language-server it tells that it has no binary but the repo was update 2 months ago, the solution was compile it with node. STEPS TO REPRODUCE 1. Create an HTML file and save it 2. See the output option OBSERVED RESULT [20:25:44  Cliente LSP Advertencia] No se ha podido encontrar el binario del servidor: vscode-html-languageserver Compruebe su PATH para el binario. EXPECTED RESULT No errors. SOFTWARE/OS VERSIONS Linux/KDE Plasma: OpenSuse (available in About System) KDE Plasma Version: 6.0 ADDITIONAL INFORMATION these solution works for me https://github.com/helix-editor/helix/discussions/9605 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 486481] No scrolling
https://bugs.kde.org/show_bug.cgi?id=486481 --- Comment #1 from Justin --- Hmm, how to edit the original?? Extra notes: Plasma 6.04 Same behaviour on Wayland and Xorg. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 486481] New: No scrolling
https://bugs.kde.org/show_bug.cgi?id=486481 Bug ID: 486481 Summary: No scrolling Classification: Plasma Product: kdeplasma-addons Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Dashboard Assignee: plasma-b...@kde.org Reporter: kdebugs.cm...@slmail.me Target Milestone: --- SUMMARY Cannot scroll with trackpad or use arrow keys to navigate. STEPS TO REPRODUCE 1. Launch Application Dashboard 2. Go to All Aplications and try to scroll. 3. No movement apart from the scroll bar only. 4. Use arrow key to move through applications - no response. 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.
[kwin] [Bug 484323] High CPU load of kwin_x11 when locking or turning off the screen
https://bugs.kde.org/show_bug.cgi?id=484323 outloudvi changed: What|Removed |Added CC||i...@outv.im -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 479464] Running command doesn't work when there are spaces in the command
https://bugs.kde.org/show_bug.cgi?id=479464 Bobby Wibowo changed: What|Removed |Added CC||bo...@fiery.me -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486480] New: Global menu disappears in certain programs after a dialog is opened.
https://bugs.kde.org/show_bug.cgi?id=486480 Bug ID: 486480 Summary: Global menu disappears in certain programs after a dialog is opened. Classification: Plasma Product: plasmashell Version: 6.0.4 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Global Menu Assignee: plasma-b...@kde.org Reporter: nat...@upchur.ch CC: k...@privat.broulik.de, mvourla...@gmail.com Target Milestone: 1.0 Created attachment 169122 --> https://bugs.kde.org/attachment.cgi?id=169122=edit A video of the bug occuring with Krita SUMMARY In certain programs, such as Krita, Inkscape, and Scribus, the global menu disappears after a dialog is opened. It returns when the application menu is closed and re-opened. I have replicated this successfully on a fresh installation of EndeavourOS / Arch in a VM. STEPS TO REPRODUCE 1. Open a document in Krita, Inkscape, or Scribus. 2. Use the global menu to select an item that causes a dialog to open. In krita, I used File > Export. The global menu will now disappear. 3. Open and close the application menu. The global menu will now reappear. OBSERVED RESULT The global menu disappears when a dialog is opened. EXPECTED RESULT The global menu remains accessible when a dialog is opened. SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-arch1-1 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480693] Major memory leak when changing wallpapers
https://bugs.kde.org/show_bug.cgi?id=480693 vinkmr <0vinoth0kum...@gmail.com> changed: What|Removed |Added Resolution|FIXED |--- Version|master |6.0.4 Status|RESOLVED|REOPENED Ever confirmed|0 |1 CC||0vinoth0kum...@gmail.com Platform|Other |Fedora RPMs --- Comment #3 from vinkmr <0vinoth0kum...@gmail.com> --- I am still running into the same issue. Switching to 'Image Wallpaper type' works as workaround. I can also get the memory usage down by restarting the plasmashell via cmdline. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 416153] Allow Night color temperature adjustment with mouse wheel
https://bugs.kde.org/show_bug.cgi?id=416153 --- Comment #11 from Natalie Clarius --- Git commit 0af47262d53f6b5acd515f9a255cb2e2b409fb15 by Natalie Clarius. Committed on 02/05/2024 at 23:19. Pushed by nclarius into branch 'master'. applets/brightness: clarify UI of Night Light inhibition To clarify that the toggle action (switch and middle-click in the applet) for Night Light merely temporarily disables the blue light filter, rather than turning the schedule off permanently like the "Disabled" setting in the KCM does, - use "suspended/resume" terminology instead of "off/on", - set a label on the switch, - turn the switch around so that the on state means inhibited, so that the UI becomes similar to "Do not disturb mode" in the notification applet. M +3-2applets/brightness/package/contents/ui/NightLightItem.qml M +7-3applets/brightness/package/contents/ui/main.qml https://invent.kde.org/plasma/plasma-workspace/-/commit/0af47262d53f6b5acd515f9a255cb2e2b409fb15 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 486479] New: Dolphin crashed after dragging a file over the breadcrumbs
https://bugs.kde.org/show_bug.cgi?id=486479
Bug ID: 486479
Summary: Dolphin crashed after dragging a file over the
breadcrumbs
Classification: I don't know
Product: kde
Version: unspecified
Platform: NixOS
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: fresh.frog5...@fastmail.com
Target Milestone: ---
Application: (24.02.2)
Qt Version: 6.7.0
Frameworks Version: 6.1.0
Operating System: Linux 6.6.27-xanmod1 x86_64
Windowing System: Wayland
Distribution: NixOS 24.05 (Uakari)
DrKonqi: 6.0.4 [CoredumpBackend]
-- Information about the crash:
After dragging a file into IntelliJ IDEA (Community Edition), Dolphin crashed.
I was able to reproduce this reliably, and after experimenting a bit, found
that this appeared to depend on how deeply nested the file was. For instance,
`/home/v/a/a/a/a/b` would crash Dolphin, whereas `/home/v/a/a/a/b` would not.
Only dragging the file into the editor section of IDEA would induce a crash;
dragging into the Project file listing would open a modal as expected.
While trying to reproduce this, I discovered what appeared to be another bug:
Dolphin would crash when dragging a file onto the directory path/breadcrumbs at
the top. I eventually realized that this and the initial bug were one and the
same, and that these had nothing to do with the directory depth, since any time
I dragged the file *over* the breadcrumbs it would crash a moment later as
well. Naturally, longer paths were more likely to result in me moving the
cursor over the breadcrumbs, leading to a crash in only those cases when
initially debugging this.
The crash can be reproduced every time.
-- Backtrace:
Application: Dolphin (), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[New LWP 575904]
[New LWP 575905]
[New LWP 575909]
[New LWP 575906]
[New LWP 575908]
[New LWP 575923]
[New LWP 575907]
[New LWP 575940]
[New LWP 575925]
[New LWP 575924]
[New LWP 575926]
[New LWP 575942]
[New LWP 575932]
[New LWP 575941]
[New LWP 575939]
[New LWP 575943]
[New LWP 575944]
[New LWP 576016]
[New LWP 576242]
[New LWP 575948]
[New LWP 575945]
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/nix/store/35pq4hr29c3sl79lgfwgsvd9nwzyp4am-glibc-2.39-5/lib/libthread_db.so.1".
Core was generated by `/run/current-system/sw/bin/dolphin'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 __pthread_kill_implementation (threadid=,
signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44
44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO
(ret) : 0;
[Current thread is 1 (Thread 0x7fae066a3fc0 (LWP 575904))]
Cannot QML trace cores :(
Unexpectedly stumbled over an objfile
(/nix/store/5zk3svqc96pnjkf9yxwx4vpb5bh0hqzj-libdeflate-1.20/lib/libdeflate.so.0)
without build_id. Not creating payload.
[Current thread is 1 (Thread 0x7fae066a3fc0 (LWP 575904))]
Thread 21 (Thread 0x7fadb37fe6c0 (LWP 575945)):
#0 0x7fae0b839c5e in __futex_abstimed_wait_common64 (private=0,
cancel=true, abstime=0x7fadb37fda10, op=137, expected=0, futex_word=0x14bd3a4)
at futex-internal.c:57
#1 __futex_abstimed_wait_common (futex_word=futex_word@entry=0x14bd3a4,
expected=expected@entry=0, clockid=clockid@entry=1,
abstime=abstime@entry=0x7fadb37fda10, private=private@entry=0,
cancel=cancel@entry=true) at futex-internal.c:87
#2 0x7fae0b839cdf in __GI___futex_abstimed_wait_cancelable64
(futex_word=futex_word@entry=0x14bd3a4, expected=expected@entry=0,
clockid=clockid@entry=1, abstime=abstime@entry=0x7fadb37fda10,
private=private@entry=0) at futex-internal.c:139
#3 0x7fae0b83c7d5 in __pthread_cond_wait_common (abstime=0x7fadb37fda10,
clockid=1, mutex=0x14bd350, cond=0x14bd378) at pthread_cond_wait.c:503
#4 ___pthread_cond_timedwait64 (cond=0x14bd378, mutex=0x14bd350,
abstime=0x7fadb37fda10) at pthread_cond_wait.c:643
#5 0x7fae0c087393 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from
/nix/store/r8a6ss3xnc9j4yrgajbvy8wnn359cpkq-qtbase-6.7.0/lib/libQt6Core.so.6
#6 0x7fae0c08409c in QThreadPoolThread::run() () from
/nix/store/r8a6ss3xnc9j4yrgajbvy8wnn359cpkq-qtbase-6.7.0/lib/libQt6Core.so.6
#7 0x7fae0c07ade1 in QThreadPrivate::start(void*) () from
/nix/store/r8a6ss3xnc9j4yrgajbvy8wnn359cpkq-qtbase-6.7.0/lib/libQt6Core.so.6
#8 0x7fae0b83d272 in start_thread (arg=) at
pthread_create.c:447
#9 0x7fae0b8b8dcc in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
Thread 20 (Thread 0x7fade5d2a6c0 (LWP 575948)):
#0 0x7fae0b8abb66 in __GI_ppoll (fds=0x7fade5d29840, nfds=1,
timeout=, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:42
#1 0x7fae0c0777f9 in qt_safe_poll(pollfd*, unsigned long, QDeadlineTimer)
() from
[Powerdevil] [Bug 483803] Screen does not turn back on after Powerdevil turns it off.
https://bugs.kde.org/show_bug.cgi?id=483803 --- Comment #5 from stevenmcfeel...@gmail.com --- (In reply to Jakob Petsovits from comment #4) > For later convenience, the error portion of the log goes as follows. > Apparently kscreenlocker_greet does not have a valid EGL surface to draw its > contents on (preceded by a few potentially unrelated pipewire errors): > > Mar 12 12:41:38 smcfeely-desktop wireplumber[2238]: > Failed to call Lookup: > GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera > Mar 12 12:41:38 smcfeely-desktop pipewire[2229]: [0:34:16.149552308] [2229] > ERROR IPAModule ipa_module.cpp:172 Symbol ipaModuleInfo not found > Mar 12 12:41:38 smcfeely-desktop pipewire[2229]: [0:34:16.149561108] [2229] > ERROR IPAModule ipa_module.cpp:292 v4l2-compat.so: IPA module has no valid > info > Mar 12 12:41:38 smcfeely-desktop pipewire[2229]: [0:34:16.149575598] [2229] > INFO Camera camera_manager.cpp:284 libcamera v0.2.0 > Mar 12 12:41:38 smcfeely-desktop wireplumber[2238]: > Failed to call Lookup: > GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera > Mar 12 12:41:46 smcfeely-desktop kscreenlocker_greet[3770]: > file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/ > lockscreen/NoPasswordUnlock.qml:26: ReferenceError: tryToSwitchUser is not > defined > Mar 12 12:41:48 smcfeely-desktop kscreenlocker_greet[3770]: qt.qpa.wayland: > eglSwapBuffers failed with 0x300d, surface: 0x0 > Mar 12 12:41:48 smcfeely-desktop kscreenlocker_greet[3770]: qt.qpa.wayland: > Could not create EGL surface (EGL error 0x3000) > Mar 12 12:41:49 smcfeely-desktop kscreenlocker_greet[3770]: Failed to write > to the pipe: Bad file descriptor. > > Although the undefined tryToSwitchUser error may not be linked to the EGL > stuff, potentially also worth investigating. > > (In reply to Re Play from comment #2) > > Same issue here. Googling around a bit, I found that Mutter had an issue > > that was extremely similar to this. They never found the exact cause, but > > had a Mutter specific workaround. Perhaps that could be useful for narrowing > > this down? https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040 > > I don't know about possible causes at this point, but it looks like KWin's > equivalent to MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 is KWIN_DRM_NO_AMS=1 looking > at the code. If you think this is worth trying, you could set it for KWin's > systemd unit (`systemctl --user edit plasma-kwin_wayland.service`): > > ### Editing > /home/kpetso/.config/systemd/user/plasma-kwin_wayland.service.d/override.conf > ### Anything between here and the comment below will become the contents of > the drop-in file > > [Service] > Environment="KWIN_DRM_NO_AMS=1" > > ### Edits below this comment will be discarded I have been testing this for the past 48 hours and it appears to work. Setting Environment="KWIN_DRM_NO_AMS=1" allows my desktop's monitor to properly wake up. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 445598] Dynamic word wrapping in Kile stopped working in Ubuntu 21.10
https://bugs.kde.org/show_bug.cgi?id=445598 --- Comment #5 from Samuel Jimenez --- (In reply to Kishore Gopalakrishnan from comment #4) > (In reply to Samuel Jimenez from comment #3) > > This happens sporadically on 2.9.95 > > Operating System: Arch Linux > > KDE Plasma Version: 6.0.4 > > KDE Frameworks Version: 6.1.0 > > Qt Version: 6.7.0 > > > > If an entry for the file is created in kilerc, it remains persistent. (This > > corresponds to View >Word Wrap > Dynamic Word Wrap) > > [View-Settings,View=0,URL=file://:@/path/to/file.tex] > > Dynamic Word Wrap=true > > > > However, until this is saved per-file, the setting inherited from > > KTextEditor is not consistently respected. > > (Settings > Configure > Kile > Editor > Appearance > Dynamic Word Wrap) > > [KTextEditor View] > > Dynamic Word Wrap=true > > Are you sure this is not a ktexteditor bug? I seem to be seeing similar > behaviour in Kate too. In which version of Kate do you see this? I cannot reproduce in Kate version 24.02.2. While I don't claim to be sure, I see it around 50% in Kile. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486478] Quick Tiled windows no longer act maximised
https://bugs.kde.org/show_bug.cgi?id=486478 --- Comment #2 from jeremy.lel...@gmail.com --- Created attachment 169121 --> https://bugs.kde.org/attachment.cgi?id=169121=edit KDE 6.0.4 after tiling -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486478] Quick Tiled windows no longer act maximised
https://bugs.kde.org/show_bug.cgi?id=486478 --- Comment #1 from jeremy.lel...@gmail.com --- Created attachment 169120 --> https://bugs.kde.org/attachment.cgi?id=169120=edit KDE 5.27 before tiling -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486478] New: Quick Tiled windows no longer act maximised
https://bugs.kde.org/show_bug.cgi?id=486478 Bug ID: 486478 Summary: Quick Tiled windows no longer act maximised Classification: Plasma Product: kwin Version: 6.0.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Quick Tiling Assignee: kwin-bugs-n...@kde.org Reporter: jeremy.lel...@gmail.com Target Milestone: --- Created attachment 169119 --> https://bugs.kde.org/attachment.cgi?id=169119=edit KDE 5.27 after tiling SUMMARY In KDE 5.27, quick tiling a window would make the window decorate itself as if it was maximized. This is most noticeable in Firefox, where the empty "grabber" section in the upper left of the title bar goes away when maximized. It is also noticeable in that window corners appear curved normally, but rectangular when maximized. In KDE 6.0.4, quick tiled windows still have curved corners, and Firefox still shows that large empty "grabber" section. STEPS TO REPRODUCE 1. Launch Firefox 2. Windows + Left (or drag to left edge of screen to trigger Quick Tile) 3. Note upper left of Firefox titlebar OBSERVED RESULT Still has large empty "grabber" area, still has rounded corner showing desktop below. EXPECTED RESULT Grabber area should be gone, corners of window should be rectangular. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION See screenshots from an older installation showing KDE 5.27 behavior vs current KDE 6.0.4 behavior. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486477] The System Tray popup is unusably small and can't be resized when the panel is small, and when not floating
https://bugs.kde.org/show_bug.cgi?id=486477 --- Comment #1 from bluescreenaven...@gmail.com --- Forgot to add, it regressed sometime after late December, I have an own build from then, and it was working in that one, -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486477] New: The System Tray popup is unusably small and can't be resized when the panel is small, and when not floating
https://bugs.kde.org/show_bug.cgi?id=486477 Bug ID: 486477 Summary: The System Tray popup is unusably small and can't be resized when the panel is small, and when not floating Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: bluescreenaven...@gmail.com CC: mate...@gmail.com Target Milestone: 1.0 SUMMARY It seems that when the panel is not floating, (and is smaller than the default height?) the systray popup is 0x0, just a very small little dot that appears, instead of an actual panel I thought it was something up with my own-built KDE but now I can replicate on a Fedora live CD STEPS TO REPRODUCE 1. Download https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20240502.n.0/compose/Spins/x86_64/iso/Fedora-KDE-Live-x86_64-Rawhide-20240502.n.0.iso boot it in a VM 2. Set the Panel Width to 30 3. Move the Welcome Center window down so the panel stops floating 4. Try to expand the panel popup OBSERVED RESULT A little dot appears above the clock EXPECTED RESULT The panel popup should appear instead SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora Linux 41 (available in About System) KDE Plasma Version: 6.0.4 (and Master) KDE Frameworks Version: 6.1 (and Master) Qt Version: 6.7 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmag] [Bug 438912] No output from KMagnifier on Wayland
https://bugs.kde.org/show_bug.cgi?id=438912 --- Comment #20 from Ahmed Faisal --- (In reply to Nicolas Fella from comment #19) > It was not ignored. It was pointed out that we already have a fully > functional screen magnification tool on Plasma Wayland, so accessibility use > cases are already covered No, it was not. To elaborate my point, I would like to point to two famous applications for desktop magnification. the Gnome's and Cinnamon's. Those two examples by name has two types of zooming: 1- Full screen zooming: the same one applied in KDE Plasma -that you mean by "got covered", and xFce, and Compiz and probably others that I forget about or did not know of. 2- Projected zooming: I don't know if that was the precise term for it, because I made that up. The projected zooming is found only in Gnome, Cinnamon, Kmag and Xmag. Where zoomed image is displayed on a side window (Kmag, Xmag and Windows Magnifier) or a part of screen, make that top half, bottom half, right half or left half. as seen in Gnome and Cinnamon. not counting W.Magnifier as this feature still very crappy after all those years. Conclusion: KDE Plasma gives full screen zooming. KMagnifier gives projected zooming. Meaning that you are able to see zoomed image and zoomed object in real size, so you can easily find your location in full view beside your zoomed view. you can try it yourself in Cinnamon by writing anything in full screen zooming (here you will realize the importance of zooming-follow-typing feature) than make that right half where you can see the whole page you write in left half and the exact line you edit in right half (if you have 2 monitors this can be your whole right monitor!). I hope I did put the matter the right, sufficient way. Greetings -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 485407] polkit-kde-agent crashes with nullptr
https://bugs.kde.org/show_bug.cgi?id=485407 --- Comment #10 from jorgylbran...@gmail.com --- This is my best attempt getting a backtrace. I hope you find this useful. -- You are receiving this mail because: You are watching all bug changes.
[policykit-kde-agent-1] [Bug 485407] polkit-kde-agent crashes with nullptr
https://bugs.kde.org/show_bug.cgi?id=485407 --- Comment #9 from jorgylbran...@gmail.com --- Created attachment 169118 --> https://bugs.kde.org/attachment.cgi?id=169118=edit GDB log This is my best attempt of a back trace, I hope it's useful. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 486413] Headphones default and switch to "Line Out" mode
https://bugs.kde.org/show_bug.cgi?id=486413 --- Comment #3 from Wilbur Jaywright --- Correction: But, not if I scroll over the volume icon at least once before in the session to change the volume that way. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476794] Kicad icons are not displayed correctly
https://bugs.kde.org/show_bug.cgi?id=476794 --- Comment #9 from twistedturtle --- Thank you for your reply. :) >If we use the window icon when windows are not grouped, then you'll have the >experience of clicking on a launcher icon (which uses the app's icon) and then >once the app launches, the icon will change into a different icon specific to >what the window shows. That would be rather odd. That should only happen if the first window closed, and another one opened. I think using the window icon would be proper behavior, but it should be a separate entity. In other words the launcher always stays the same. If the main/first window to which that icon applies is open then it's listed under that launcher, otherwise the window has it's own icon separate from the launcher (of course this includes any additional windows that use the launcher icon). Or again when not grouped, launchers are just launchers and always spawn a new window object. Seems like a candidate for an option. What you describe is basically the reverse of what we have now. We click on a launcher with one icon (in Kicad's main window), it launches a window with the same icon, but the task manager uses a different icon). You can see it all in the screenshot I posted. If the window has an icon then it's there for a reason, so presumably that's what should be displayed. Anything else seems rather odd. >The greater issue is that right now the UX here is incoherent since the >icons-only task manager was originally intended to implement the "dock" style >UI where windows are always grouped under an icon provided by the app itself, >not any of its specific windows. You're right, this issue is why (or at least one reason why) it's incoherent. Grouping them under a single icon is one thing, but that doesn't mean you can't also use window icons where appropriate. I just checked out cairo-dock, it uses icons for the windows in a group, but incorrectly uses the same icon for all windows in the group. Even if you want to otherwise copy docks, there's no reason not to use the proper window icon. >We need to sort out the design vision here before we start pulling it in any >given direction, or else it will drift ever more aimlessly in random >directions that make the UX less coherent. Fair enough, but that should've been done when the functionality to ungroup the windows was addedarguably that functionality never should've been omitted in the first place. I see only one option, which is what you're already doing. Allow both grouped and not grouped modes. Speaking as a user and as someone who likes window switchers and doesn't like docks, the only thing I've found to screw up the UX is the lack of proper window icons. So my way of looking at it: There are groups, windows and launchers. In this context I see launchers as pinned groups, I'll lump them together with groups. The task manager shows groups or windows. A window is represented by it's own icon. When you hover over it, an image of the window is displayed and above that is the icon on the left followed by the title. So almost the same as now but use the window icon, twice. A group is represented by the app icon, presumably you already have a definition for that, but I'd say it's the icon from the launcher (the main window should be the same anyway). When you hover, a window list is displayed. Each window in the list is shown the same way as described above. So again the same as now but use the window icon for the windows. Combined with the launcher stuff from the top, I think it's coherent and should suit most if not all, but perhaps there's more to consider. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 486413] Headphones default and switch to "Line Out" mode
https://bugs.kde.org/show_bug.cgi?id=486413 --- Comment #2 from Wilbur Jaywright --- correction: It switches back to Line Out EVERY time I change the volume with the keyboard buttons. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483997] KScreenLocker breaks when Wayland crashes
https://bugs.kde.org/show_bug.cgi?id=483997 --- Comment #6 from techxga...@outlook.com --- May have been tied to my PCoIP (gdb) bt #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=124434375484544) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=124434375484544) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=124434375484544, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x712c1e642476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x712c1e628885 in __GI_abort () at ./stdlib/abort.c:100 #5 0x712c1a0b3abb in ?? () from /lib/libGraphicsMagick-Q16.so.3 #6 #7 __pthread_kill_implementation (no_tid=0, signo=6, threadid=124434375484544) at ./nptl/pthread_kill.c:44 #8 __pthread_kill_internal (signo=6, threadid=124434375484544) at ./nptl/pthread_kill.c:78 #9 __GI___pthread_kill (threadid=124434375484544, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #10 0x712c1e642476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #11 0x712c1e6287f3 in __GI_abort () at ./stdlib/abort.c:79 #12 0x712c1eaa2b9e in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #13 0x712c1eaae20c in ?? () from /lib/x86_64-linux-gnu/libstdc++.so.6 #14 0x712c1eaae277 in std::terminate() () from /lib/x86_64-linux-gnu/libstdc++.so.6 #15 0x5f1211233661 in std::thread::~thread() () #16 0x712c1e645a56 in __cxa_finalize (d=0x712c1fa47c00) at ./stdlib/cxa_finalize.c:83 #17 0x712c1f8a7967 in ?? () from /usr/lib/x86_64-linux-gnu/pcoip-client/libbroker_client.so #18 0x7fff57139fe0 in ?? () #19 0x712c2512724e in _dl_fini () at ./elf/dl-fini.c:142 Backtrace stopped: frame did not save the PC -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483997] KScreenLocker breaks when Wayland crashes
https://bugs.kde.org/show_bug.cgi?id=483997 --- Comment #5 from techxga...@outlook.com --- Wrong bt Here's the right one (gdb) bt #0 0x76df62886e98 in KWin::EffectWindow::pos() const () at /lib/x86_64-linux-gnu/libkwin.so.6 #1 0x5b83efba4951 in () #2 0x76df62865741 in KWin::EffectsHandler::prePaintWindow(KWin::EffectWindow*, KWin::WindowPrePaintData&, std::chrono::duration >) () at /lib/x86_64-linux-gnu/libkwin.so.6 #3 0x76df6296fa75 in KWin::WorkspaceScene::preparePaintSimpleScreen() () at /lib/x86_64-linux-gnu/libkwin.so.6 #4 0x76df62972705 in KWin::WorkspaceScene::prePaint(KWin::SceneDelegate*) () at /lib/x86_64-linux-gnu/libkwin.so.6 #5 0x76df6296048a in KWin::SceneDelegate::prePaint() () at /lib/x86_64-linux-gnu/libkwin.so.6 #6 0x76df627f6f59 in KWin::Compositor::prePaintPass(KWin::RenderLayer*, QRegion*) () at /lib/x86_64-linux-gnu/libkwin.so.6 #7 0x76df627f7a70 in KWin::Compositor::composite(KWin::RenderLoop*) () at /lib/x86_64-linux-gnu/libkwin.so.6 #8 0x76df6026355e in () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #9 0x76df62815526 in KWin::RenderLoop::frameRequested(KWin::RenderLoop*) () at /lib/x86_64-linux-gnu/libkwin.so.6 #10 0x76df62817987 in KWin::RenderLoopPrivate::dispatch() () at /lib/x86_64-linux-gnu/libkwin.so.6 #11 0x76df6026355e in () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #12 0x76df602165ae in QTimer::timeout(QTimer::QPrivateSignal) () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #13 0x76df601fa1ce in QObject::event(QEvent*) () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #14 0x76df6140992b in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt6Widgets.so.6 #15 0x76df602a1c38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #16 0x76df60182dda in QTimerInfoList::activateTimers() () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #17 0x76df60185cdd in QEventDispatcherUNIX::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #18 0x76df60b11501 in QUnixEventDispatcherQPA::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt6Gui.so.6 #19 0x76df602a3e3b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #20 0x76df602a5a6c in QCoreApplication::exec() () at /lib/x86_64-linux-gnu/libQt6Core.so.6 #21 0x5b83efb6904a in () #22 0x76df5f629d90 in __libc_start_call_main (main=main@entry=0x5b83efb66d60, argc=argc@entry=14, argv=argv@entry=0x7ffc6b8ad978) at ../sysdeps/nptl/libc_start_call_main.h:58 #23 0x76df5f629e40 in __libc_start_main_impl (main=0x5b83efb66d60, argc=14, argv=0x7ffc6b8ad978, init=, fini=, rtld_fini=, stack_end=0x7ffc6b8ad968) at ../csu/libc-start.c:392 #24 0x5b83efb6f8b5 in () -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486462] Fractional Scaling affects the wallpaper, making it look blurry even when sized 1:1 with the monitor
https://bugs.kde.org/show_bug.cgi?id=486462 fanzhuyi...@gmail.com changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 483997] KScreenLocker breaks when Wayland crashes
https://bugs.kde.org/show_bug.cgi?id=483997 --- Comment #4 from techxga...@outlook.com --- (gdb) bt #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=123291088106048) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=123291088106048) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=123291088106048, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x7021f1642476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x7021f16287f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x7021f22fdb6e in qAbort () at ./src/corelib/global/qglobal.cpp:161 #6 0x7021f22f820a in qt_message_fatal (message=..., context=...) at ./src/corelib/global/qlogging.cpp:2025 #7 qt_message(QtMsgType, const QMessageLogContext &, const char *, typedef __va_list_tag __va_list_tag *) (msgType=msgType@entry=QtFatalMsg, context=..., msg=, ap=ap@entry=0x7ffd9c6e3640) at ./src/corelib/global/qlogging.cpp:374 #8 0x7021f22fe511 in QMessageLogger::fatal (this=, msg=) at ./src/corelib/global/qlogging.cpp:889 #9 0x7021f22c2ac2 in qt_assert (assertion=assertion@entry=0x7021f25f5050 "!d->sensorObjects.contains(id)", file=file@entry=0x7021f25f5028 "./systemstats/SensorContainer.cpp", line=line@entry=57) at ./src/corelib/global/qassert.cpp:68 #10 0x7021f25dc3e4 in KSysGuard::SensorContainer::addObject (this=0x5dd7def72b00, object=0x5dd7df11b190) at ./systemstats/SensorContainer.cpp:57 #11 0x7021f21fa272 in QObject::event (this=0x5dd7def72b00, e=0x5dd7df038b30) at ./src/corelib/kernel/qobject.cpp:1446 #12 0x7021f22a1c13 in doNotify (event=, receiver=) at ./src/corelib/kernel/qcoreapplication.cpp:1235 #13 QCoreApplication::notify (event=, receiver=, this=) at ./src/corelib/kernel/qcoreapplication.cpp:1218 #14 QCoreApplication::notifyInternal2 (receiver=0x5dd7def72b00, event=event@entry=0x5dd7df038b30) at ./src/corelib/kernel/qcoreapplication.cpp:1134 #15 0x7021f22a1c7d in QCoreApplication::sendEvent (receiver=, event=event@entry=0x5dd7df038b30) at ./src/corelib/kernel/qcoreapplication.cpp:1575 #16 0x7021f22a23e0 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x5dd7def63f10) at ./src/corelib/kernel/qcoreapplication.cpp:1932 #17 0x7021f2078277 in postEventSourceDispatch (s=0x5dd7def68f50) at ./src/corelib/kernel/qeventdispatcher_glib.cpp:244 #18 0x7021f0f20d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7021f0f76258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x7021f0f1e3e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x7021f2076570 in QEventDispatcherGlib::processEvents (this=0x5dd7def66310, flags=...) at ./src/corelib/kernel/qeventdispatcher_glib.cpp:394 #22 0x7021f22a3e3b in QEventLoop::exec (this=this@entry=0x7ffd9c6e3b60, flags=..., flags@entry=...) at ./src/corelib/global/qflags.h:34 #23 0x7021f22a5a6c in QCoreApplication::exec () at ./src/corelib/global/qflags.h:74 #24 0x5dd7dd266fb8 in main (argc=, argv=) at ./src/main.cpp:31 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486476] New: Tray applets opening to zero width after any window is made fullscreen
https://bugs.kde.org/show_bug.cgi?id=486476 Bug ID: 486476 Summary: Tray applets opening to zero width after any window is made fullscreen Classification: Plasma Product: plasmashell Version: 6.0.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: k...@rad1an.aleeas.com CC: mate...@gmail.com Target Milestone: 1.0 Created attachment 169117 --> https://bugs.kde.org/attachment.cgi?id=169117=edit Demonstration of tray bug Tray applets opening to zero width after any window is made fullscreen STEPS TO REPRODUCE 1. Open an applet (such as tray (Show hidden icons), audio or networks) 2. See that it opens 3. Open any window and make it fullscreen 4. Try opening the same applet OBSERVED RESULT The applet is zero-width and can't be expanded unless the window is no more fullscreen Additionally, plasma starts freezing EXPECTED RESULT The applet should just open SOFTWARE/OS VERSIONS Operating System: Fedora Linux 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.7-300.fc40.x86_64 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION I attach a video -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484323] High CPU load of kwin_x11 when locking or turning off the screen
https://bugs.kde.org/show_bug.cgi?id=484323 --- Comment #22 from Kevin Krammer --- (In reply to Zamundaaa from comment #21) > Does this still happen if you > 1. kill kwin_x11 before locking the screen? When I kill kwin_x11 or call it manually with --replace then the CPU load does no longer exceed normal levels. > 2. or disable KScreen2 in the background services settings page? Will try next time I re-login -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483625] The microphone icon is missing. Notifications flew to the corner of the screen
https://bugs.kde.org/show_bug.cgi?id=483625 Luca Carlon changed: What|Removed |Added CC||carlon.l...@gmail.com --- Comment #10 from Luca Carlon --- I'm also experiencing this issue. I've never experienced this with Plasma 5. It only started with Plasma 6. I found a way to reproduce quickly: 1. setup the system to have two screens (I have the laptop screen and an external screen), and set the external screen to be the primary; 2. unplug the external screen; 3. wait for the system to adapt to the new setup; 4. plug the screen again; 5. try to set the volume; 6. you should see the volume window in the upper left corner of one screen. It won't even move to the other screen properly. It is also possible to simply turn off the screen by using the proper Plasma shortcut. To fix: logout and then login again. I can reproduce in a few seconds. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486462] Fractional Scaling affects the wallpaper, making it look blurry even when sized 1:1 with the monitor
https://bugs.kde.org/show_bug.cgi?id=486462 --- Comment #2 from max...@directbox.com --- It happens the same way on both wayland and x11. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 486475] New: Unable to create a new profile, error "Profile name exceeded maximum allowed length (-9)."
https://bugs.kde.org/show_bug.cgi?id=486475 Bug ID: 486475 Summary: Unable to create a new profile, error "Profile name exceeded maximum allowed length (-9)." Classification: Applications Product: yakuake Version: 24.02.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: h...@kde.org Reporter: mba...@outlook.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Unable to create a new profile, given error in flatpak version, "Profile name exceeded maximum allowed length (-9)." STEPS TO REPRODUCE 1. Download flatpak version 2. Press Manage profiles 3. Create new profile and name it anything you want. OBSERVED RESULT Profile name exceeded maximum allowed length (-9). EXPECTED RESULT Make a new profile with given settings SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.8-arch1-1 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics Memory: 31.2 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 Manufacturer: LENOVO Product Name: 82N6 System Version: Legion 7 16ACHg6 ADDITIONAL INFORMATION Does not work only on the flatpak version. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467766] MySQL foreign key error on a zero image id
https://bugs.kde.org/show_bug.cgi?id=467766 --- Comment #68 from Maik Qualmann --- Are you using multicore option in the face engine settings of the people view? Please deactivate it once, restart if necessary and see if the problem also occurs. Maik -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 486473] Crash when selecting applications with "Applications" page
https://bugs.kde.org/show_bug.cgi?id=486473 --- Comment #1 from gugolp...@gmail.com --- I have to add that it seems more stable (no crashes) on Wayland. X11 still crashing. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 486468] Amarok 2.9.71 crashes at startup on Fedora 40
https://bugs.kde.org/show_bug.cgi?id=486468 Tuomas Nurmi changed: What|Removed |Added CC||tuo...@norsumanageri.org --- Comment #1 from Tuomas Nurmi --- Thank you for your report! Looking at the backtrace, the fact that the crash happens very early during initialization suggests there might be something problematic with how phonon-vlc backend interacts with pipewire. This might be a long shot, but could you try if similar crashes happen when starting up e.g. Dragon player? (which also uses phonon for audio playback) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 486418] Only part of the selected pictures are imported
https://bugs.kde.org/show_bug.cgi?id=486418 --- Comment #4 from niccolo.cas...@gmail.com --- (In reply to Maik Qualmann from comment #3) > Please look in your target folder with a file manager that you selected when > downloading with the import tool. Are there any files here with the > "digikamtempfile" part in the name? > > Maik No, there aren't. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 486474] Smb4k does not support alternatives to KDE Wallet
https://bugs.kde.org/show_bug.cgi?id=486474 --- Comment #1 from Odin Vex --- For some reason I wasn't able to specify the version of Smb4k, 3.2.5. -- You are receiving this mail because: You are watching all bug changes.
[Smb4k] [Bug 486474] New: Smb4k does not support alternatives to KDE Wallet
https://bugs.kde.org/show_bug.cgi?id=486474 Bug ID: 486474 Summary: Smb4k does not support alternatives to KDE Wallet Classification: Applications Product: Smb4k Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.reinho...@kdemail.net Reporter: odin@ethicalexploiting.com Target Milestone: --- SUMMARY Smb4k does not use libsecret (to support alternatives to KDE Wallet such as KeePassXC). STEPS TO REPRODUCE 1. Disable KDE Wallet. 2. Enable KeePassXC as Secret Service. 3. Attempt to retrieve/store credentials for bookmarks/mounts. OBSERVED RESULT Credentials are not stored. EXPECTED RESULT Credentials to be stored. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro x64 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 ADDITIONAL INFORMATION libsecret is often used to replace archaic hard-coding around KDE Wallet. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486368] WIFI cannot be enabled at Kubuntu 24.04 LTS
https://bugs.kde.org/show_bug.cgi?id=486368 --- Comment #9 from Bas Roufs --- (In reply to fanzhuyifan from comment #7) > Yet another possibility is that your laptop has a physical button to > enable/disable the wifi, and you need to press that > (https://askubuntu.com/questions/98702/how-to-unblock-something-listed-in- > rfkill). The button combination FN -F5 is seemlingly aimed at toggling WIFI. However, nothing happens. When alternating this button combination with the terminal command connmanctl enable wifi, I keep getting this feedback: wifi is not available. bas@Camino:~$ connmanctl enable wifi wifi is not available Weird detail: at Kubuntu 22.04.4 LTS, I did not have such an issue. WIFI worked simply. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 486457] build of amarok3 crashes on starte
https://bugs.kde.org/show_bug.cgi?id=486457 Tuomas Nurmi changed: What|Removed |Added CC||tuo...@norsumanageri.org --- Comment #1 from Tuomas Nurmi --- Thank you for your report! Looking at the backtrace, the crash seems to happen during QML ContextView applet loading (a failing assert), which might indicate some problems with data installation paths. Can you provide output if you run `amarok --debug`? (Additionally, running cmake with parameter like -DCMAKE_INSTALL_PREFIX=`kf5-config --prefix` when compiling might have an effect here) -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 486473] New: Crash when selecting applications with "Applications" page
https://bugs.kde.org/show_bug.cgi?id=486473 Bug ID: 486473 Summary: Crash when selecting applications with "Applications" page Classification: Applications Product: plasma-systemmonitor Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: gugolp...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. Open System Monitor 2. Select "Applications" from the sidebar 3. Select an application OBSERVED RESULT System Monitor will crash EXPECTED RESULT Just selecting the application clicked on. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.0 (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467766] MySQL foreign key error on a zero image id
https://bugs.kde.org/show_bug.cgi?id=467766 --- Comment #67 from Petr Schonmann --- Created attachment 169116 --> https://bugs.kde.org/attachment.cgi?id=169116=edit digikam_debug_467766_2024-05-02-another_debug_day.txt -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486368] WIFI cannot be enabled at Kubuntu 24.04 LTS
https://bugs.kde.org/show_bug.cgi?id=486368 --- Comment #8 from Bas Roufs --- (In reply to fanzhuyifan from comment #6) > (In reply to Bas Roufs from comment #5) > > I understand and respect this opinion. However, clarify what means > > «downstream» in this situation - Kubuntu, the system where I stumbled on > > this bug? If some useful info will come in from there, I'll share it here. > > May be, also other Kubuntu users will subscribe to this bug - I am not the > > only one who experiences this problem. > > IMO this might be a hardware issue (there is something physically wrong with > the card/the connection), or this might be a driver issue (driver bug or > wrong driver). Anyways I would suggest asking for help on the distribution > forums. Of course, I'll check all such options at such forums. However, when I worked with Kubuntu 22.04.4 LTS at exactly the same device, I WAS able to work with WIFI - then, it was no problem to enable it. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 486472] New: ALT+TAB confirm face in unconfirmed faces when selected name
https://bugs.kde.org/show_bug.cgi?id=486472 Bug ID: 486472 Summary: ALT+TAB confirm face in unconfirmed faces when selected name Classification: Applications Product: digikam Version: 8.4.0 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Faces-Workflow Assignee: digikam-bugs-n...@kde.org Reporter: pschonm...@gmail.com Target Milestone: --- SUMMARY ALT+TAB confirm face in unconfirmed faces when selected name STEPS TO REPRODUCE 1. Go to unconfirmed faces 2. Choose face thats not belong to automatically detected person 3. Write right person name and dont confirm that with enter or just arrow down to !! select !! only the person and dont confirm with enter 4. ALT+TAB > confirms face not switch windows :D OBSERVED RESULT Bad hotkeys behavior EXPECTED RESULT Just switch windows SOFTWARE/OS VERSIONS digiKam-8.4.0-20240502T115124-Qt6-x86-64.appimage -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486368] WIFI cannot be enabled at Kubuntu 24.04 LTS
https://bugs.kde.org/show_bug.cgi?id=486368 --- Comment #7 from fanzhuyi...@gmail.com --- Yet another possibility is that your laptop has a physical button to enable/disable the wifi, and you need to press that (https://askubuntu.com/questions/98702/how-to-unblock-something-listed-in-rfkill). -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486368] WIFI cannot be enabled at Kubuntu 24.04 LTS
https://bugs.kde.org/show_bug.cgi?id=486368 --- Comment #6 from fanzhuyi...@gmail.com --- (In reply to Bas Roufs from comment #5) > I understand and respect this opinion. However, clarify what means > «downstream» in this situation - Kubuntu, the system where I stumbled on > this bug? If some useful info will come in from there, I'll share it here. > May be, also other Kubuntu users will subscribe to this bug - I am not the > only one who experiences this problem. IMO this might be a hardware issue (there is something physically wrong with the card/the connection), or this might be a driver issue (driver bug or wrong driver). Anyways I would suggest asking for help on the distribution forums. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486368] WIFI cannot be enabled at Kubuntu 24.04 LTS
https://bugs.kde.org/show_bug.cgi?id=486368 --- Comment #5 from Bas Roufs --- (In reply to fanzhuyifan from comment #4) > I understand that your issue is still ongoing, but marking this bug report > as resolved-downstream just means that there is nothing we could do about > this issue on KDE's side, and this seems like an issue downstream. So please > don't reopen this unless there is further evidence that this indicates a bug > in KDE software. I understand and respect this opinion. However, please clarify me: what means, in my situation, «downstream»? Kubuntu? If something(In reply to fanzhuyifan from comment #4) > I understand that your issue is still ongoing, but marking this bug report > as resolved-downstream just means that there is nothing we could do about > this issue on KDE's side, and this seems like an issue downstream. So please > don't reopen this unless there is further evidence that this indicates a bug > in KDE software. I understand and respect this opinion. However, clarify what means «downstream» in this situation - Kubuntu, the system where I stumbled on this bug? If some useful info will come in from there, I'll share it here. May be, also other Kubuntu users will subscribe to this bug - I am not the only one who experiences this problem. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 466293] Cannot scroll beyond the border of the screen using Wayland
https://bugs.kde.org/show_bug.cgi?id=466293 Mihai Coman changed: What|Removed |Added CC||mi...@m1x.ro -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486462] Fractional Scaling affects the wallpaper, making it look blurry even when sized 1:1 with the monitor
https://bugs.kde.org/show_bug.cgi?id=486462 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from fanzhuyi...@gmail.com --- Is this on wayland or x11 or both? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 486270] When opening this *.kdenlive file on any Linux and any version of kdenlive it creates a d: drive in the folder, corrupting the partition. This file came from Windows.
https://bugs.kde.org/show_bug.cgi?id=486270 --- Comment #4 from Antonio --- Try opening this html file that I sent in any Linux distro with kdenlive 23.08.2 or higher, and you will notice the errors... -- You are receiving this mail because: You are watching all bug changes.
[KSystemLog] [Bug 447768] The GUI should not be run as root but only prompt for the root password for loading the logs (security & Wayland issues)
https://bugs.kde.org/show_bug.cgi?id=447768 fanzhuyi...@gmail.com changed: What|Removed |Added CC||cont...@ikel.slmail.me --- Comment #3 from fanzhuyi...@gmail.com --- *** Bug 486442 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[KSystemLog] [Bug 486442] sudo error and app theme
https://bugs.kde.org/show_bug.cgi?id=486442 fanzhuyi...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED CC||fanzhuyi...@gmail.com Resolution|--- |DUPLICATE --- Comment #1 from fanzhuyi...@gmail.com --- *** This bug has been marked as a duplicate of bug 447768 *** -- You are receiving this mail because: You are watching all bug changes.
[KSystemLog] [Bug 447768] The GUI should not be run as root but only prompt for the root password for loading the logs (security & Wayland issues)
https://bugs.kde.org/show_bug.cgi?id=447768 fanzhuyi...@gmail.com changed: What|Removed |Added CC||xenoida...@gmail.com --- Comment #2 from fanzhuyi...@gmail.com --- *** Bug 456793 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[KSystemLog] [Bug 456793] KSystemLog asks for Root Password instead of Sudo
https://bugs.kde.org/show_bug.cgi?id=456793 fanzhuyi...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||fanzhuyi...@gmail.com --- Comment #1 from fanzhuyi...@gmail.com --- *** This bug has been marked as a duplicate of bug 447768 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 486455] I would like to inform that my KDE app seems to be using the language that I don't use for my device where it's Japanese but I use English
https://bugs.kde.org/show_bug.cgi?id=486455 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com Severity|critical|normal -- You are receiving this mail because: You are watching all bug changes.
[kmag] [Bug 438912] No output from KMagnifier on Wayland
https://bugs.kde.org/show_bug.cgi?id=438912 --- Comment #19 from Nicolas Fella --- It was not ignored. It was pointed out that we already have a fully functional screen magnification tool on Plasma Wayland, so accessibility use cases are already covered -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486469] Maximized windows have a semi-transparent line between window content and decorations
https://bugs.kde.org/show_bug.cgi?id=486469 fanzhuyi...@gmail.com changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||fanzhuyi...@gmail.com Status|REPORTED|NEEDSINFO --- Comment #4 from fanzhuyi...@gmail.com --- Is this under fractional scaling? Does this happen for native wayland apps, or xwayland apps, or both? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486368] WIFI cannot be enabled at Kubuntu 24.04 LTS
https://bugs.kde.org/show_bug.cgi?id=486368 fanzhuyi...@gmail.com changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #4 from fanzhuyi...@gmail.com --- I understand that your issue is still ongoing, but marking this bug report as resolved-downstream just means that there is nothing we could do about this issue on KDE's side, and this seems like an issue downstream. So please don't reopen this unless there is further evidence that this indicates a bug in KDE software. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 486270] When opening this *.kdenlive file on any Linux and any version of kdenlive it creates a d: drive in the folder, corrupting the partition. This file came from Windows.
https://bugs.kde.org/show_bug.cgi?id=486270 --- Comment #3 from Antonio --- I didn't express myself correctly about the bug, it creates a drive, not a folder, and when going through Windows' chkdsk it finds an error in the partition; See the html file I sent... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486471] New: "Track Mouse" doesn't track tablet cursor movements
https://bugs.kde.org/show_bug.cgi?id=486471 Bug ID: 486471 Summary: "Track Mouse" doesn't track tablet cursor movements Classification: Plasma Product: kwin Version: 6.0.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: pawel.vese...@gmail.com Target Milestone: --- SUMMARY Wayland Tablet Wacom Intous S Pen [vps@phoenix]~$ rpm -qa |grep -i wacom xorg-x11-drv-wacom-serial-support-1.2.2-1.fc40.x86_64 libwacom-data-2.10.0-1.fc40.noarch libwacom-2.10.0-1.fc40.x86_64 xorg-x11-drv-wacom-1.2.2-1.fc40.x86_64 STEPS TO REPRODUCE 1. Enable and activate "Track Mouse" desktop effect. 2. Move mouse cursor with the tablet OBSERVED RESULT The "tracker" stays where the cursor was left off by the last mouse movement, and does not follow cursor when moved by the tablet pen. EXPECTED RESULT The mouse cursor should be followed by the tracker regardless of the device that moves it. SOFTWARE/OS VERSIONS Linux/KDE Plasma: F40/Wayland KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 486470] New: System monitor does not show used memory of some processes
https://bugs.kde.org/show_bug.cgi?id=486470 Bug ID: 486470 Summary: System monitor does not show used memory of some processes Classification: Applications Product: plasma-systemmonitor Version: 6.0.4 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: dvs-1...@yandex.ru CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY System monitor does not show used memory of some processes STEPS TO REPRODUCE 1. Open system monitor, go to processes page 2. find some processes without a value in memory column (example: Virtualbox with started VM) 3. No memory usage is shown OBSERVED RESULT No value of used memory EXPECTED RESULT All processes have a value of used memory SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.5.0-28-generic (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-8750H CPU @ 2.20GHz Memory: 15.3 ГиБ of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 Manufacturer: Dell Inc. Product Name: XPS 15 9570 ADDITIONAL INFORMATION In htop launches as user (not root), memory usage is shown, so there is access, no security block -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485811] The Trash disappears from the desktop after being emptied and until plasmashell restart
https://bugs.kde.org/show_bug.cgi?id=485811 --- Comment #9 from Sin Jeong-hun --- I thought it was random but it seems that, in my case, whenever I delete a file by drag-and-dropping a file into the Trash icon, whether the Trash was empty or not. I have also trying setting the same icon for both full/empty, but that made no difference. -- You are receiving this mail because: You are watching all bug changes.
[kmag] [Bug 438912] No output from KMagnifier on Wayland
https://bugs.kde.org/show_bug.cgi?id=438912 Ahmed Faisal changed: What|Removed |Added CC||ahmedfai...@gmail.com Status|REOPENED|CONFIRMED --- Comment #18 from Ahmed Faisal --- Ignored, as always. All accessibility related bugs / feature requests in this decade! "Importance normal". Ok, this maybe right for you. For us, visually impaired, it renders the whole system useless. Microsoft Windows is still on my system, not for Adobe software, not for office, not for games. It's a simple feature that wasn't by the way supported on their system last year(!!): the zooming in their magnifier wasn't following typing in editors, but now it follows. I reported that in Linux's best magnifying tool: the gnome zoom. The output? They just kept asking me for proofs and steps to reproduce (I've even been asked for a video screencast for a problem that exists in every gnome installation!!!). This is terribly off-topic. I know. But here in Kmagnifier I confirm this bug. It's in every kmag that runs on any Wayland desktop (e.g. hyprland) on any distro. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 486047] ".desktop" shorts randomly disappear from the desktop
https://bugs.kde.org/show_bug.cgi?id=486047 Sin Jeong-hun changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Sin Jeong-hun --- *** This bug has been marked as a duplicate of bug 485811 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485811] The Trash disappears from the desktop after being emptied and until plasmashell restart
https://bugs.kde.org/show_bug.cgi?id=485811 --- Comment #8 from Sin Jeong-hun --- *** Bug 486047 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486469] Maximized windows have a semi-transparent line between window content and decorations
https://bugs.kde.org/show_bug.cgi?id=486469 --- Comment #3 from Yoshio Sato --- Created attachment 169115 --> https://bugs.kde.org/attachment.cgi?id=169115=edit window with deleted area around the line window with deleted area around the line, the background is actual background that was at the time of making the screenshot -- You are receiving this mail because: You are watching all bug changes.
[subtitlecomposer] [Bug 485596] Crashing after a short while unless Waveform pane is disabled
https://bugs.kde.org/show_bug.cgi?id=485596 David Marzal changed: What|Removed |Added CC||mundoli...@tutanota.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486469] Maximized windows have a semi-transparent line between window content and decorations
https://bugs.kde.org/show_bug.cgi?id=486469 --- Comment #2 from Yoshio Sato --- Created attachment 169114 --> https://bugs.kde.org/attachment.cgi?id=169114=edit where the line is where the line is -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486469] Maximized windows have a semi-transparent line between window content and decorations
https://bugs.kde.org/show_bug.cgi?id=486469 --- Comment #1 from Yoshio Sato --- Created attachment 169113 --> https://bugs.kde.org/attachment.cgi?id=169113=edit window window -- You are receiving this mail because: You are watching all bug changes.
