[kdiff3] [Bug 487338] Possible regression: Floating point exception
https://bugs.kde.org/show_bug.cgi?id=487338 Sergio changed: What|Removed |Added Summary|Floating point exception: 8 |Possible regression: ||Floating point exception -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 487338] Floating point exception: 8
https://bugs.kde.org/show_bug.cgi?id=487338 Sergio changed: What|Removed |Added CC||sergio.calleg...@gmail.com --- Comment #1 from Sergio --- This is not just MacOS. Same issue on Manjaro Linux. Most likely a regression, since I think that kdiff3 was working fine until not long ago. Seen with Operating System: Manjaro Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.9.2-1-MANJARO (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 9 6900HS with Radeon Graphics Memory: 30.6 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: ASUSTeK COMPUTER INC. Product Name: ROG Zephyrus G14 GA402RK_GA402RK System Version: 1.0 Application reports org.kde.kdiff3: Diff: A <-> B org.kde.kdiff3: Linediff: A <-> B org.kde.kdiff3: Enter: calcDiff3LineListUsingAB org.kde.kdiff3: Leave: calcDiff3LineListUsingAB Floating point exception (core dumped) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482780] Incorrect color gamut with HDR enabled
https://bugs.kde.org/show_bug.cgi?id=482780 kilgore.tr...@idesmi.eu changed: What|Removed |Added CC||kilgore.tr...@idesmi.eu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486725] sRGB content is over-saturated in HDR
https://bugs.kde.org/show_bug.cgi?id=486725 kilgore.tr...@idesmi.eu changed: What|Removed |Added CC||kilgore.tr...@idesmi.eu -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487790] When performing Virtual Desktop Switch Gestures too fast, the current desktop moves by 2 steps
https://bugs.kde.org/show_bug.cgi?id=487790 --- Comment #2 from Marco --- I don't think this is the same bug. In the other bug it is quite the opposite: if going too slow, you can move 2 desktops. This does not happen to me with Plasma 6, no matter how slow I swipe. My issue appears when swiping fast. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 487822] "Wipe all tags from Database only" crashes digiKam
https://bugs.kde.org/show_bug.cgi?id=487822 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- We need a debugger backtrace to investiguate. Look in the Windows section of the contribute page : https://www.digikam.org/contribute/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 487370] Face Recognition crashes - pre-release built on 20-05-2024 07:25
https://bugs.kde.org/show_bug.cgi?id=487370 --- Comment #34 from caulier.gil...@gmail.com --- ok, and next build will done later 5PM Paris time -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 487370] Face Recognition crashes - pre-release built on 20-05-2024 07:25
https://bugs.kde.org/show_bug.cgi?id=487370 --- Comment #33 from Maik Qualmann --- Git commit 1ecb551c1ab64379afb287485a200557f38a634a by Maik Qualmann. Committed on 31/05/2024 at 06:01. Pushed by mqualmann into branch 'master'. no style changes only to the ComboBox M +4-6core/utilities/facemanagement/widgets/assignnamewidget_p.cpp https://invent.kde.org/graphics/digikam/-/commit/1ecb551c1ab64379afb287485a200557f38a634a -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 487370] Face Recognition crashes - pre-release built on 20-05-2024 07:25
https://bugs.kde.org/show_bug.cgi?id=487370 --- Comment #32 from Maik Qualmann --- The ComboBox with tree view works again and there are no more crashes. I will do another test where we only suppress the style of the ComboBox. Maik -- You are receiving this mail because: You are watching all bug changes.
[spacebar] [Bug 485719] spacebar-daemon crashes when an SMS text is received; no notification shown, no message shown in Spacebar
https://bugs.kde.org/show_bug.cgi?id=485719 --- Comment #5 from jresc...@outlook.com --- Josh, thank you for your input and additional research and troubleshooting. The bug report you linked to is similar, but not quite the same as what I am experiencing. The only notification I receive is a notification that the spacebar-daemon has crashed as soon as I send a test text message to the PinePhone. Interestingly, I can send text messages until an incoming test text message crashes the daemon. I looked at merge request 158 that you referenced. It appears that merge request was rejected in favor of 159, which was merged a few weeks ago and was supposed to resolve the same issue that 158 addressed. The CMakeLists.txt file in the master branch of the spacebar indicates the latest version is 24.05.0. That is the version I have installed from pacman, so I assume the fix from 159 is present in the build I am running. Unfortunately, it does not seem to resolve my issue. However, I do have interesting new developments to report. After building from source with the latest commit to the master branch, and running the daemon in the terminal with /usr/local/lib/libexec/spacebar-daemon as before, I now receive text messages and notifications! Unfortunately, I can only receive them when the spacebar front end is closed. Otherwise, the text message is never received, there is no notification, and the daemon outputs the same message as my previous comment in this thread: futuresql: SQL error: "database is locked Unable to fetch row" Perhaps this database lock conflict is occurring because I am manually running the daemon in the terminal? Maybe it has to be initiated by some other process to work properly in the background? For thoroughness, I applied the changed from merge request 158, and rebuilt it, but had the same result. Have you tried building from source? Do you have the same results as I do? Here is how I built it if you need. Hopefully I remembered everything: I uninstalled the spacebar package: $ sudo pacman -Rsn spacebar I installed the following packages (c-ares is a dependency of spacebar, the other packages are for building): $ sudo pacman -S base-devel cmake extra-cmake-modules git c-ares I followed the build instructions from https://invent.kde.org/plasma-mobile/spacebar: $ git clone https://invent.kde.org/plasma-mobile/spacebar.git $ cd spacebar I tried building with the following command: $ cmake -B build && cmake --build build But I got stuck here: [ 51%] Linking CXX executable ../bin/spacebar-daemon /usr/bin/ld: ../lib/libkTelephonySupport.a(phonenumber.cpp.o): undefined reference to symbol '_ZN4absl12lts_2024011612log_internal21CheckOpMessageBuilderC1EPKc' /usr/bin/ld: /usr/lib/libabsl_log_internal_check_op.so.2401.0.0: error adding symbols: DSO missing from command line collect2: error: ld returned 1 exit status make[2]: *** [daemon/CMakeFiles/spacebar-daemon.dir/build.make:227: bin/spacebar-daemon] Error 1 make[1]: *** [CMakeFiles/Makefile2:1177: daemon/CMakeFiles/spacebar-daemon.dir/all] Error 2 make: *** [Makefile:146: all] Error 2 I resolved the linker error by explicitly adding the following libraries to the target_link_libraries in src/CMakeLists.txt and daemon/CMakeLists.txt: absl_log_internal_check_op absl_log_internal_message Then I built and installed it: $ cmake -B build && cmake --build build $ sudo cmake --install build This is how I run the daemon from the terminal: $ /usr/local/lib/libexec/spacebar-daemon I use the following command to uninstall the package that I built from source: $ sudo xargs rm < build/install_manifest.txt I am increasingly confident that the database lock (futuresql: SQL error: "database is locked Unable to fetch row") is my issue. I still don't know how to fix it, but that appears to be the smoking gun. Perhaps a more experienced developer can produce a fix. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 487821] Keep People/Face Tag, but Mark Them to be Ignored in Further Recognition Suggestions
https://bugs.kde.org/show_bug.cgi?id=487821 Maik Qualmann changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- *** This bug has been marked as a duplicate of bug 459499 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 459499] The possibility to disable persons
https://bugs.kde.org/show_bug.cgi?id=459499 Maik Qualmann changed: What|Removed |Added CC||carlo.m...@outlook.com --- Comment #4 from Maik Qualmann --- *** Bug 487821 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482987] With fractional scale, bottom edge of screen has pixels that are held to the color of previously opened windows after closing those windows
https://bugs.kde.org/show_bug.cgi?id=482987 ProodjePindakaas changed: What|Removed |Added CC|f.vdbosc...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 487822] New: "Wipe all tags from Database only" crashes digiKam
https://bugs.kde.org/show_bug.cgi?id=487822 Bug ID: 487822 Summary: "Wipe all tags from Database only" crashes digiKam Classification: Applications Product: digikam Version: 8.3.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: Tags-Manager Assignee: digikam-bugs-n...@kde.org Reporter: carlo.m...@outlook.com Target Milestone: --- SUMMARY "Wipe all tags from Database only" crashes digiKam STEPS TO REPRODUCE 1. Go to Tag Manager 2. Click Sync Export 3. Click Wipe all tags from Database only OBSERVED RESULT The wipe seems to complete, but it crashes digiKam EXPECTED RESULT The wipe should complete, but keep digiKam running SOFTWARE/OS VERSIONS Windows: 11 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 444394] Rejected face suggestions reappear for the same person the next time recognition is run
https://bugs.kde.org/show_bug.cgi?id=444394 CM changed: What|Removed |Added CC||carlo.m...@outlook.com --- Comment #7 from CM --- I'd like this feature also. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 487821] New: Keep People/Face Tag, but Mark Them to be Ignored in Further Recognition Suggestions
https://bugs.kde.org/show_bug.cgi?id=487821 Bug ID: 487821 Summary: Keep People/Face Tag, but Mark Them to be Ignored in Further Recognition Suggestions Classification: Applications Product: digikam Version: 8.3.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: Faces-Recognition Assignee: digikam-bugs-n...@kde.org Reporter: carlo.m...@outlook.com Target Milestone: --- I understand there is an "Ignored" function. What I'd like to have is the ability to mark a face or person tag so that the app will no longer try to recognize the face and make further suggestions as potential matches. I want to keep the tags therefore simply putting them as "Ignored" is not ideal. Assume the scenario where the person has passed away and no more photos of that person are expected. I've been able to achieve the same effect by manually editing the Sqlite database and delete certain rows from the 'FaceMatrices' table. Can a similar function be added? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487779] ERROR:gbm_pixmap_wayland.cc(82)] Cannot create bo with format= YUV_420_BIPLANAR and usage=SCANOUT_CPU_READ_WRITE
https://bugs.kde.org/show_bug.cgi?id=487779 --- Comment #3 from Bernie Innocenti --- Found an existing bug in the Chromium bug tracker: https://issues.chromium.org/issues/331796411 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487806] Adjusting scaling on Wayland leads to incorrectly scaled wallpaper or background
https://bugs.kde.org/show_bug.cgi?id=487806 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from David Edmundson --- I cannot reproduce. If you right click in the black area do you get a context menu? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487120] NVIDIA 3080, proprietary drivers with Wayland constant crashes plasma 6
https://bugs.kde.org/show_bug.cgi?id=487120 --- 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.
[plasma-systemmonitor] [Bug 486359] The system settings program (Preferencias de sistema) start in all bootings.
https://bugs.kde.org/show_bug.cgi?id=486359 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.
[kwin] [Bug 487820] Track Mouse effect doesn't follow mouse
https://bugs.kde.org/show_bug.cgi?id=487820 Tom Dzmelyk changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487820] New: Track Mouse effect doesn't follow mouse
https://bugs.kde.org/show_bug.cgi?id=487820 Bug ID: 487820 Summary: Track Mouse effect doesn't follow mouse Classification: Plasma Product: kwin Version: git-stable-Plasma/6.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: tddzm...@mtu.edu Target Milestone: --- Created attachment 170009 --> https://bugs.kde.org/attachment.cgi?id=170009&action=edit Spectacle recording of a stationary effect and the moving mouse. SUMMARY With the Plasma 6.1 beta the 'Track Mouse' effect doesn't follow the mouse and instead lingers at the spot where it was activated. STEPS TO REPRODUCE 1. Toggle Track Mouse 2. Move mouse OBSERVED RESULT Effect stays stationary EXPECTED RESULT Effect follows mouse SOFTWARE/OS VERSIONS Arch Linux Plasma 6.1 beta kwin 6.0.90.1-1 from arch kde-unstable mesa-git-c1d3fa007ca (May 29th) ADDITIONAL INFORMATION I compiled kwin from the Plasma/6.1 branch (commit b13ae603) to check if it had been fixed since the initial release of the 6.1 beta but the bug is still present there. I also tried seeing if it was maybe a problem with the software cursor, but the bug occurs both with and without KWIN_DRM_DONT_FORCE_AMD_SW_CURSOR=1 set. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 476921] Pressing Meta+B should cycle through all modes in Power OSD
https://bugs.kde.org/show_bug.cgi?id=476921 Fabian Arndt changed: What|Removed |Added Assignee|plasma-b...@kde.org |fabian.ar...@root-core.net Ever confirmed|0 |1 Status|REPORTED|ASSIGNED CC||fabian.ar...@root-core.net --- Comment #1 from Fabian Arndt --- https://invent.kde.org/plasma/powerdevil/-/merge_requests/368 -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 487038] Plasma broke login/splash themes
https://bugs.kde.org/show_bug.cgi?id=487038 GregS changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 487038] Plasma broke login/splash themes
https://bugs.kde.org/show_bug.cgi?id=487038 --- Comment #4 from GregS --- I have confirmed QuickControls IS installed (somewhere on the system??); but Plasma obviousluy camnnot locate it. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487770] Feature Request: Option to bind arbitrary command lines to shortcut keys and/or custom toolbar buttons
https://bugs.kde.org/show_bug.cgi?id=487770 --- Comment #2 from ocalhoun <7485...@gmail.com> --- Hmm... The only way I can find for doing so is: Configure Dolphin --> Context Menu --> Download New Services --> Download New Stuff window --> contribute your own --> open KDE store website --> create account on KDE store website --> confirm email on KDE store website --> log in to KDE store website --> click on user icon --> Add Product --> (go through a seemingly rather complicated process of setting up an addon there, which is *far* more complicated than it needs to be for just executing a single command for one user) --> back to Configure Dolphin --> Context Menu --> Download New Services (again) --> search for the service you just created --> download it While it may technically be possible to do things this way ... this process seems a bit unnecessarily convoluted if you're just trying to do something simple. And it seems to require making your new addon publicly available, which could be just cluttering the store with things so specific they're only relevant to you personally, or it could possibly even have privacy concerns, if the command you need to run includes private information. That seems far from ideal to me. It's a reasonable process for adding a new Plasma widget or desktop theme, sure ... but far too complicated to just get Dolphin to execute a console command. It would be much nicer and simpler to have one of those list items in the Context Menu settings be "Run Command:" with a text box or popup or something to enter your command into. (And a new blank "Run Command:" entry added afterward.) -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 486277] Artifacts systemmonitor
https://bugs.kde.org/show_bug.cgi?id=486277 --- Comment #2 from Dmitry --- (In reply to Arjen Hiemstra from comment #1) > This is a GPU driver bug and you should report it to your GPU driver's > author. I thought the problem was only observed in the system monitor. It is he who is to blame, not the driver. Let me add that there are no such or similar problems anywhere else. But I understand you, I will solve the problem through the driver. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kidletime] [Bug 328987] Power saving should not trigger if joystick/controller/gamepad is in use
https://bugs.kde.org/show_bug.cgi?id=328987 Angus K changed: What|Removed |Added CC||angu...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 486506] Firefox (Flatpak) does not inhibit power management when playing videos
https://bugs.kde.org/show_bug.cgi?id=486506 Angus K changed: What|Removed |Added CC||angu...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 460895] plasmashell process uses all available RAM and several UI elements freeze
https://bugs.kde.org/show_bug.cgi?id=460895 Fushan Wen changed: What|Removed |Added Assignee|qydwhotm...@gmail.com |plasma-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487816] No clean way to change the wallpaper for distributions
https://bugs.kde.org/show_bug.cgi?id=487816 Zamundaaa changed: What|Removed |Added CC||notm...@gmail.com, ||qydwhotm...@gmail.com, ||xaver.h...@gmail.com Assignee|kwin-bugs-n...@kde.org |plasma-b...@kde.org Target Milestone|--- |1.0 Product|kwin|plasmashell Component|core|Image Wallpaper -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487806] Adjusting scaling on Wayland leads to incorrectly scaled wallpaper or background
https://bugs.kde.org/show_bug.cgi?id=487806 Zamundaaa changed: What|Removed |Added Target Milestone|--- |1.0 Assignee|kwin-bugs-n...@kde.org |plasma-b...@kde.org Version|unspecified |git-stable-Plasma/6.1 CC||notm...@gmail.com, ||qydwhotm...@gmail.com, ||xaver.h...@gmail.com Component|wayland-generic |Image Wallpaper Product|kwin|plasmashell -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487590] Ambiguous shortcut on F3 (split view) after update
https://bugs.kde.org/show_bug.cgi?id=487590 --- Comment #3 from 1r8l8...@duck.com --- (In reply to Felix Ernst from comment #2) > Considering that you can't find the conflicting shortcut in Dolphin, I > wonder if this could either be a shortcut that is only available while the > Konsole panel is active in Dolphin (to check this, first activate Dolphin's > terminal panel, then open the Dolphin keyboard shortcuts configuration), or > if some global keyboard shortcut might cause a conflict. This is just a stab > in the dark on my part though, I don't actually know that much about how > such a keyboard conflict could suddenly appear during an update. Opening the Konsole panel did not bring up any extra options associated with just F3 in the keyboard config menu. I have reset all the shortcuts to their default settings but this also did not resolve the ambiguous shortcut. I would like to delete the config files for Dolphin, but I'm not sure which files to delete within ~/.config/. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487777] kwin_wayland 6.0.90.1 crashed repeatedly when starting in VMs using the virgl driver resulting in a black screen
https://bugs.kde.org/show_bug.cgi?id=48 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/plasma/kwin/-/merge_requests/5803 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 487819] After a5a9b6e70, on macOS, konsole crashes upon creating 2nd tab
https://bugs.kde.org/show_bug.cgi?id=487819 --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/utilities/konsole/-/merge_requests/1002 -- You are receiving this mail because: You are watching all bug changes.
[spacebar] [Bug 485719] spacebar-daemon crashes when an SMS text is received; no notification shown, no message shown in Spacebar
https://bugs.kde.org/show_bug.cgi?id=485719 --- Comment #4 from Josh W --- I believe this issue is the same: https://bugs.kde.org/show_bug.cgi?id=479067 That thread mentions a fix at https://invent.kde.org/plasma-mobile/spacebar/-/merge_requests/158/diffs -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ksvg] [Bug 453876] kf.plasma.core: "findInCache with a lastModified timestamp of 0 is deprecated" log warning
https://bugs.kde.org/show_bug.cgi?id=453876 Anael changed: What|Removed |Added CC||an...@anael.es -- You are receiving this mail because: You are watching all bug changes.
[spacebar] [Bug 485719] spacebar-daemon crashes when an SMS text is received; no notification shown, no message shown in Spacebar
https://bugs.kde.org/show_bug.cgi?id=485719 Josh W changed: What|Removed |Added CC||winchesterjosh...@gmail.com --- Comment #3 from Josh W --- I have this same error. I am using Arch+KDE+Plasma Mobile 6 (not Manjaro) but am also having issues getting texts with spacebar. Sadly, there is no other text messaging application that I am aware of. I had this problem 2 months ago when I updated to Plasma 6, and the solution I came up with then was the laziest possible: sudo pacman -U file:///path/to/old/spacebar.pkg.tar.xz. My texts worked like they had before. I had other issues, and reinstalled the OS again recently and still have this problem. In other words this is from a fresh install from https://github.com/dreemurrs-embedded/Pine64-Arch/releases; I then did a full system upgrade using sudo pacman -Syuu glibc-locales --overwrite /usr/lib/locale/\*/\* --noconfirm I still have this issue, nearly the same as jresch: [alarm@pcubed ~]$ sudo journalctl -b | grep spacebar [sudo] password for alarm: May 30 19:21:42 pcubed spacebar-daemon[4249]: Could not find modem "" May 30 19:21:42 pcubed spacebar-daemon[4249]: current (old) database revision 8 May 30 19:21:42 pcubed spacebar-daemon[4249]: futuresql: Marking migration "2023-05-07-102621_init" as done. May 30 19:21:42 pcubed spacebar-daemon[4249]: futuresql: SQL error: "UNIQUE constraint failed: __qt_schema_migrations.version Unable to fetch row" May 30 19:21:42 pcubed spacebar-daemon[4249]: futuresql: Migrations finished May 30 19:21:48 pcubed spacebar-daemon[4249]: kf.modemmanagerqt: Unknown Mobile Country Code: 0 May 30 19:21:48 pcubed spacebar-daemon[4249]: Country Code: "" May 30 19:21:48 pcubed spacebar-daemon[4249]: Country code is null! Phone numbers may not be interpreted correctly May 30 19:21:48 pcubed spacebar-daemon[4249]: qt.dbus.integration: Could not connect "org.freedesktop.DBus.Properties" to onPropertiesChanged(QString, QVariantMap, QStringList) : May 30 19:21:49 pcubed spacebar-daemon[4249]: country code changed "US" May 30 19:21:49 pcubed spacebar-daemon[4249]: dns: "" May 30 19:21:49 pcubed spacebar-daemon[4249]: interface: "" May 30 19:21:50 pcubed spacebar-daemon[4249]: interface changed: "wwu1i4" May 30 19:21:50 pcubed spacebar-daemon[4249]: bearer connected: true May 30 19:21:50 pcubed spacebar-daemon[4249]: dns4 updated: "198.224.155.135,198.224.153.135" May 30 19:22:31 pcubed spacebar[4390]: kf.coreaddons: The plugin "/usr/lib/qt6/plugins/kpeople/datasource/KPeopleVCard.so" explicitly states an Id in the embedded metadata, which is different from the one derived from the filename The Id field from the KPlugin object in the metadata should be removed May 30 19:22:31 pcubed spacebar[4390]: futuresql: Running "\nWITH Numbers AS (\nSELECT\nMAX(time) AS maxTime,\nphoneNumber\nFROM Messages\n GROUP BY phoneNumber\n)\nSELECT phoneNumber\n FROM Numbers\nORDER BY maxTime desc\n" May 30 19:22:31 pcubed spacebar[4390]: qrc:/ChatsPage.qml:17:1: QML ChatsPage: Created graphical object was not placed in the graphics scene. May 30 19:22:31 pcubed spacebar[4390]: kf.quickcharts.datasource: ModelSource: Invalid role -1 "color" May 30 19:22:31 pcubed spacebar[4390]: kf.quickcharts.datasource: ModelSource: Invalid role -1 "color" May 30 19:22:37 pcubed drkonqi-coredump-processor[4079]: "/usr/lib/spacebar-daemon" 4246 "/var/lib/systemd/coredump/core.spacebar-daemon.1000.628fc09f3f704dcd9d30dc228b6d651c.4246.171710651700.zst" May 30 19:22:37 pcubed drkonqi-coredump-processor[4079]: "/usr/lib/spacebar-daemon" 4244 "/var/lib/systemd/coredump/core.spacebar-daemon.1000.06b3bc244a9a4ee2a37b50c446361402.4244.171710738900.zst" May 30 19:22:37 pcubed drkonqi-coredump-processor[4079]: "/usr/lib/spacebar-daemon" 4252 "/var/lib/systemd/coredump/core.spacebar-daemon.1000.e812c6ab526a485f9197ec8b894c6151.4252.171710958100.zst" May 30 19:22:37 pcubed drkonqi-coredump-processor[4079]: "/usr/bin/spacebar" 4484 "/var/lib/systemd/coredump/core.spacebar.1000.bbdb1101375c4d59947d745b1a669150.4484.171711075800.zst" May 30 19:22:37 pcubed drkonqi-coredump-launcher[4404]: Unable to find file for pid 4246 expected at "kcrash-metadata/spacebar-daemon.628fc09f3f704dcd9d30dc228b6d651c.4246.ini" May 30 19:22:37 pcubed drkonqi-coredump-launcher[4405]: Unable to find file for pid 4244 expected at "kcrash-metadata/spacebar-daemon.06b3bc244a9a4ee2a37b50c446361402.4244.ini" May 30 19:22:37 pcubed drkonqi-coredump-launcher[4408]: Unable to find file for pid 4252 expected at "kcrash-metadata/spacebar-daemon.e812c6ab526a485f9197ec8b894c6151.4252.ini" May 30 19:22:37 pcubed drkonqi-coredump-launcher[4409]: Unable to find file for pid 4484 expected at "kcrash-
[konsole] [Bug 487819] New: After a5a9b6e70, on macOS, konsole crashes upon creating 2nd tab
https://bugs.kde.org/show_bug.cgi?id=487819 Bug ID: 487819 Summary: After a5a9b6e70, on macOS, konsole crashes upon creating 2nd tab Classification: Applications Product: konsole Version: master Platform: Other OS: macOS Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: khindenb...@kde.org Target Milestone: --- https://invent.kde.org/utilities/konsole/-/merge_requests/996 VM Region Info: 0x60 is not in any region. Bytes before following region: 4314632096 REGION TYPESTART - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL UNUSED SPACE AT START ---> __TEXT 1012c1000-1012db000[ 104K] r-x/r-x SM=COW /Applications/KF6/konsole.app/Contents/MacOS/konsole Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libkonsoleprivate.24.07.70.dylib 0x1023b5e3b Konsole::SessionController::session() const + 27 (SessionController.h:95) 1 libkonsoleprivate.24.07.70.dylib 0x102559bec Konsole::SessionController::userTitle() const + 44 (SessionController.cpp:2160) 2 libkonsoleprivate.24.07.70.dylib 0x102578275 Konsole::TerminalDisplayAccessible::TerminalDisplayAccessible(Konsole::TerminalDisplay*) + 53 (TerminalDisplayAccessible.cpp:16) 3 libkonsoleprivate.24.07.70.dylib 0x10257831d Konsole::TerminalDisplayAccessible::TerminalDisplayAccessible(Konsole::TerminalDisplay*) + 29 (TerminalDisplayAccessible.cpp:17) 4 libkonsoleprivate.24.07.70.dylib 0x1024be292 Konsole::accessibleInterfaceFactory(QString const&, QObject*) + 66 (TerminalDisplay.cpp:185) 5 QtGui 0x1070aabde QAccessible::queryAccessibleInterface(QObject*) + 414 (qaccessible.cpp:691) 6 QtWidgets 0x104ebb648 QStyleHelper::isInstanceOf(QObject*, QAccessible::Role) + 22 (qstylehelper.cpp:106) [inlined] 7 QtWidgets 0x104ebb648 QStyleHelper::hasAncestor(QObject*, QAccessible::Role) + 56 (qstylehelper.cpp:117) 8 libqmacstyle.dylib 0x105f8d820 QMacStyle::styleHint(QStyle::StyleHint, QStyleOption const*, QWidget const*, QStyleHintReturn*) const + 1680 (qmacstyle_mac.mm:2819) 9 QtWidgets 0x10500b297 QScrollBarPrivate::init() + 119 (qscrollbar.cpp:353) 10 libkonsoleprivate.24.07.70.dylib 0x1024ec8a1 Konsole::TerminalScrollBar::TerminalScrollBar(QWidget*) + 33 (TerminalScrollBar.cpp:27) 11 libkonsoleprivate.24.07.70.dylib 0x1024ecb3d Konsole::TerminalScrollBar::TerminalScrollBar(QWidget*) + 29 (TerminalScrollBar.cpp:28) 12 libkonsoleprivate.24.07.70.dylib 0x1024be975 Konsole::TerminalDisplay::TerminalDisplay(QWidget*) + 1717 (TerminalDisplay.cpp:224) 13 libkonsoleprivate.24.07.70.dylib 0x1024c040d Konsole::TerminalDisplay::TerminalDisplay(QWidget*) + 29 (TerminalDisplay.cpp:213) 14 libkonsoleprivate.24.07.70.dylib 0x1023e6b02 Konsole::ViewManager::createTerminalDisplay(Konsole::Session*) + 50 (ViewManager.cpp:1059) 15 libkonsoleprivate.24.07.70.dylib 0x1023e55d9 Konsole::ViewManager::createView(Konsole::Session*) + 137 (ViewManager.cpp:932) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 356294] After clearing, set before shortcut for profile, still works
https://bugs.kde.org/show_bug.cgi?id=356294 --- Comment #3 from Piotr Mierzwinski --- (In reply to Kurt Hindenburg from comment #2) > This should be fixed in recent versions. Thanks. BTW. This was almost 9 years old bug. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 485829] "Virtual Display" button doesn't work, if krfb / krdc are not installed
https://bugs.kde.org/show_bug.cgi?id=485829 Aleix Pol changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/netw ||ork/kdeconnect-kde/-/commit ||/b24d6298027fa0b94c61f2c27e ||cf955a5123d3fc Resolution|--- |FIXED --- Comment #5 from Aleix Pol --- Git commit b24d6298027fa0b94c61f2c27ecf955a5123d3fc by Aleix Pol Gonzalez, on behalf of Fabian Arndt. Committed on 30/05/2024 at 23:13. Pushed by apol into branch 'master'. virtualmonitor: implemented capabilities check ## Summary Currently, the plugin just fails silently if the local device is missing the `krfb` package or if the remote device misses an `vnc://` protocol/scheme handler. You click the button and nothing happens. One issue is, that the plugin is considered `virtualmonitor.available` in the `DeviceDelegate.qml`, even if the check for `krfb-virtualmonitor` fails and no dbus-path is provided. I investigated the behavior a bit, but ignored it in the end as this MR benefits from being shown for device constellations that _could_ provide this feature. A warning is shown with brief instructions, how to get the plugin working correctly. - Check if krfb-virtualmonitor is available locally - Check default scheme handler for vnc:// on device (Linux) - Show warnings / reasons, if no connection could be established ## Test Plan Regarding if the devices have mentioned packages installed, we should see different behaviors. If the remote device has no VNC client, it can not connect to out server. _A warning should be shown._ If the local device hasn't the `krfb-virtualmonitor` available, the remote device couldn't connect. _A warning should be shown._ If both problems are present, _both warnings should be shown._ If none of these are present, no warning should be shown and we should try to establish a connection. The connection attempts failed? _A warning should be shown._ M +0-1declarativeplugin/qml/PluginChecker.qml M +29 -7plasmoid/package/contents/ui/DeviceDelegate.qml M +4-0plugins/virtualmonitor/kdeconnect_virtualmonitor.json M +61 -1plugins/virtualmonitor/virtualmonitorplugin.cpp M +25 -0plugins/virtualmonitor/virtualmonitorplugin.h https://invent.kde.org/network/kdeconnect-kde/-/commit/b24d6298027fa0b94c61f2c27ecf955a5123d3fc -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487590] Ambiguous shortcut on F3 (split view) after update
https://bugs.kde.org/show_bug.cgi?id=487590 --- Comment #2 from Felix Ernst --- Considering that you can't find the conflicting shortcut in Dolphin, I wonder if this could either be a shortcut that is only available while the Konsole panel is active in Dolphin (to check this, first activate Dolphin's terminal panel, then open the Dolphin keyboard shortcuts configuration), or if some global keyboard shortcut might cause a conflict. This is just a stab in the dark on my part though, I don't actually know that much about how such a keyboard conflict could suddenly appear during an update. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487590] Ambiguous shortcut on F3 (split view) after update
https://bugs.kde.org/show_bug.cgi?id=487590 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org --- Comment #1 from Felix Ernst --- Very weird. By your description this is very annoying and can't really be resolved as a user, so we usually should get a bunch of bug reports about this. This doesn't seem to be the case yet, so either people haven't updated to the latest Dolphin 24.05 version as fast as you have, or the bug is somewhat specific to your setup in some way. It might be worth looking into deleting your Dolphin configuration files and resetting Dolphin if we don't see a bunch of similar bug reports coming in soon. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 407486] dolphin, extended toolbar disappear. It does not allow me to click hidden buttons.
https://bugs.kde.org/show_bug.cgi?id=407486 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org --- Comment #4 from Felix Ernst --- AFAIK the issue is that the location bar is implemented to have a fixed size. I did that because it was the only way to position it nicely while it actually tries to take up as much space as it can get itself. I assume the fix for this is making sure that location bars/KUrlNavigators in general don't expand to take up all the space and then move away from a fixed width approach in Dolphin, which in programming terms means: 1. In the KIO framework, calculate sizeHint() for KUrlNavigators in a way that they only want as much space as they need to show the path. 2. In the KIO framework, set the default size policy of KUrlNavigators away from QSizePolicy::MinimumExpanding. 3. In Dolphin, avoid setting a fixed size for DolphinNavigatorsWidgetAction and instead set a QSizePolicy::MinimumExpanding there so it takes up the remaining space dynamically without ever expecting more space than the toolbar has. This is a bit of an untested assumption and I assume it might be a bit fiddly to get this right. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 141968] Holding down key to launch app spawns insane number of windows which can bog down the system
https://bugs.kde.org/show_bug.cgi?id=141968 --- Comment #9 from Fabian Arndt --- This wouldn't fix the problem with detecting a hold shortcut though.. it would just prevent spamming it. In my usecase it would be nice to detect if the shortcut was pressed or hold. I don't think the API would allow such a change, without extending it with an event like functionality (like in Qt.KeyEvent). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 445608] When pressing and holding META+ the window should not just flicker by constantly toggling minimize but instead toggle maximizing the window once
https://bugs.kde.org/show_bug.cgi?id=445608 Fabian Arndt changed: What|Removed |Added CC||fabian.ar...@root-core.net See Also||https://bugs.kde.org/show_b ||ug.cgi?id=141968 --- Comment #2 from Fabian Arndt --- Probably a duplicate of / caused by BUG 141968, but I'm leaving it open. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 141968] Holding down key to launch app spawns insane number of windows which can bog down the system
https://bugs.kde.org/show_bug.cgi?id=141968 Fabian Arndt changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=445608 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 485599] dolphin crash when using select file shorcuts (shortcut space)
https://bugs.kde.org/show_bug.cgi?id=485599 Felix Ernst changed: What|Removed |Added CC||saurabh2...@glbajajgroup.or ||g --- Comment #9 from Felix Ernst --- *** Bug 487718 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487718] dolphin crashing on double tapping the spacebar.
https://bugs.kde.org/show_bug.cgi?id=487718 Felix Ernst changed: What|Removed |Added Status|REPORTED|RESOLVED CC||felixer...@kde.org Resolution|--- |DUPLICATE --- Comment #2 from Felix Ernst --- *** This bug has been marked as a duplicate of bug 485599 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487770] Feature Request: Option to bind arbitrary command lines to shortcut keys and/or custom toolbar buttons
https://bugs.kde.org/show_bug.cgi?id=487770 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Felix Ernst --- In the Dolphin settings there is a "Context Menu" category. There one can download new plugins and services which will then be available from the context menu and will act on the currently selected files or will act on the currently open folder. These actions can be user-defined and downloaded. There are tutorials for this online if you need anything specific. >Some other examples of what a user could create: Some of these indeed are already available for download there! About binding these to keyboard shortcuts: This is indeed not possible currently. There is a long-standing bug report with many duplicates for this. I don't have it at hand at the moment but it shouldn't be too hard to find it. It might make sense to mark this bug report here as a duplicate of that bug report if this is the only aspect missing to resolve this bug report. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 487786] can't save any filetype in any folder "error: Cannot open file for writing." (i have full permissions for the folder and all other programs can save to it.)
https://bugs.kde.org/show_bug.cgi?id=487786 mr.flaresp...@gmail.com changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #2 from mr.flaresp...@gmail.com --- (In reply to Halla Rempt from comment #1) thank you for taking the time to point me in the right direction, now that i know that krita saves to a temp folder first i can test to see if that folder has proper permissions.(In reply to Halla Rempt from comment #1) > No, this is a problem specific to your system. Because, of course, Krita can > save its files, it does so on millions of other systems. Also, the log shows > you have been able to properly save files many times. > > The problem seems to be: > > 30 May 2024 00:56:49 -0700: Completed saving > C:/Users/BoxFort/AppData/Local/Temp/.krita-10564-document_0-autosave.kra > (mime: application/x-krita). Result: Cannot open file for writing. Reason: > The file could not be opened.. Warning: . Size: 0 > > Krita first saves to the temporary folder, then checks whether that > succeeded, and then copies the file to the real location. For some reason, > on your system, Krita cannot write to > C:/Users/BoxFort/AppData/Local/Temp/.krita-10564-document_0-autosave.kra -- > apparently the file it tries to save there is zero bytes after saving. > > Since we don't have access to your computer, it's very hard to determine why > this might be the case. thank you for taking the time to tell me about krita saving to a temporary folder. now that i know where it is, i have resolved the permissions issue. i was unable to find a solution through google like i normally do, hopefully this one can help others solve the issue themselves. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 483948] Repeatedly pressing shortcut for power profiles OSD stacks windows
https://bugs.kde.org/show_bug.cgi?id=483948 Fabian Arndt changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=141968 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 141968] Holding down key to launch app spawns insane number of windows which can bog down the system
https://bugs.kde.org/show_bug.cgi?id=141968 Fabian Arndt changed: What|Removed |Added CC||fabian.ar...@root-core.net See Also||https://bugs.kde.org/show_b ||ug.cgi?id=483948 --- Comment #8 from Fabian Arndt --- This problem was also seen in BUG 483948, as it allowed infinite instances of the shortcut target to be created. The default behaviour should be to filter hold keys, so the filter should be opt-out. It's not trivial to filter it out on the receiving side, as Wayland's security concept implies that you know "a" shortcut was pressed... but not necessarily which one and how. I've experimented with timers, but they're not reliable as they're not accurate and tend to trip. (Remaining time > interval and interval - remaining < 0) It's also not clear what would be a good threshold: I can deliberately spam keys quite fast (e.g. to cycle through elements), which gives me a delta comparable to that of holding down a shortcut. -- You are receiving this mail because: You are watching all bug changes.
[libalkimia] [Bug 487813] Make remote online offer available under additional names
https://bugs.kde.org/show_bug.cgi?id=487813 Ralf Habacker changed: What|Removed |Added Summary|Add |Make remote online offer ||available under additional ||names -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 448865] [Request] Dark Mode for Windows 10/11
https://bugs.kde.org/show_bug.cgi?id=448865 Felix Ernst changed: What|Removed |Added Resolution|--- |FIXED CC||felixer...@kde.org Latest Commit||https://invent.kde.org/syst ||em/dolphin/-/commit/aeb7048 ||51d3b33f88eb601d597c2b0743d ||4e08df Version Fixed In||24.05 Status|CONFIRMED |RESOLVED --- Comment #4 from Felix Ernst --- This should now be fixed by the combination of https://invent.kde.org/system/dolphin/-/commit/aeb704851d3b33f88eb601d597c2b0743d4e08df and https://invent.kde.org/system/dolphin/-/commit/b30eabbee26b1a2189170571e49bc86c0a49d334 . The latter also changes the styling on Windows to be closer to the Linux version which wasn't really a goal but the easiest way to accomplish dark mode working. These fixes are available in Dolphin 24.05 and later which is the version that was just released a few days ago, however I haven't looked into how long it takes for it to then become available as a Windows download. Glad you are enjoying Dolphin on Windows! It unfortunately doesn't get as much testing as the Linux version, so sorry for any issues you encounter. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484155] Defocused fullscreen apps sometimes continue to display over everything else
https://bugs.kde.org/show_bug.cgi?id=484155 username changed: What|Removed |Added CC||linx.system@gmail.com --- Comment #4 from username --- I think is the same issue: https://www.reddit.com/r/kde/comments/1bwk5lb/alt_tabbing_junkiness_in_full_screen_apps_with/ Does unchecking "Click raises active window" in Window management > Window behavior helps? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481113] When not using Systemd or Plasma's Systemd session launch integration, changes to pinned apps are not saved when Plasmashell quits
https://bugs.kde.org/show_bug.cgi?id=481113 --- Comment #50 from Randall Winkhart --- I can also confirm this affects Alpine Linux. Doing a fresh install on Alpine 3.20 using "setup-alpine" followed by "setup-desktop" leads to this behavior under both the Wayland and X11 sessions (which is odd, because on my Artix Linux system with 6.0.5, this bug only affects the Wayland session). -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486746] Untitled documents disappear from the working set when the user starts or stops debugging
https://bugs.kde.org/show_bug.cgi?id=486746 Christoph Roick changed: What|Removed |Added Version Fixed In||5.15.240800 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/kdev ||elop/kdevelop/-/commit/9cc5 ||682da37101b62eabd56437fd901 ||c554b202c --- Comment #5 from Christoph Roick --- Git commit 9cc5682da37101b62eabd56437fd901c554b202c by Christoph Roick. Committed on 30/05/2024 at 21:47. Pushed by croick into branch 'master'. Keep unsaved documents open when switching areas The document controller can find unsaved files by specifying the "untitled" document name as long as the controller exists. Show the document if it is found. FIXED-IN: 5.15.240800 M +8-0kdevplatform/shell/tests/test_workingsets.cpp M +8-2kdevplatform/shell/workingsets/workingset.cpp https://invent.kde.org/kdevelop/kdevelop/-/commit/9cc5682da37101b62eabd56437fd901c554b202c -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 487818] New: Krita does not include name in windowbar to other apps
https://bugs.kde.org/show_bug.cgi?id=487818 Bug ID: 487818 Summary: Krita does not include name in windowbar to other apps Classification: Applications Product: krita Version: 5.2.2 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: kel...@shadewing.net Target Milestone: --- When trying to set up OBS automatic scene switcher, it does not detect Krita. The Krita window shows ` [Not Saved] (48.2 MiB) * -- Krita`, but when other apps look for it, all they see is ` [Not Saved] (48.2 MiB) *`, which is the part that's constnatly subject to change. I'm not sure why the name is added to the window by what seems to be something else, maybe the system itself, but an easy fix would be for Krita to just put Krita on the windowbar itself. Krita Version: 5.2.2 Hidpi: true Qt Version (compiled): 5.15.7 Version (loaded): 5.15.7 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.10.0-28-amd64 Pretty Productname: Freedesktop SDK 23.08 (Flatpak runtime) Product Type: org.freedesktop.platform Product Version: 23.08 Desktop: XFCE Appimage build: No Locale Languages: en_US, en, en_Latn_US C locale: en_US.UTF-8 QLocale current: en QLocale system: en QTextCodec for locale: UTF-8 OpenGL Info Vendor: "AMD" Renderer: "AMD Radeon RX 580 Series (radeonsi, polaris10, LLVM 17.0.6, DRM 3.40, 5.10.0-28-amd64)" Driver version: "4.6 (Core Profile) Mesa 24.0.7 (git-cc175010c5)" Shading language: "4.60" Requested format: QSurfaceFormat(version 3.3, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CompatibilityProfile) Current format: QSurfaceFormat(version 4.6, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::CoreProfile) GL version: 4.6 Supports deprecated functions false Is OpenGL ES: false supportsBufferMapping: true supportsBufferInvalidation: true forceDisableTextureBuffers: false Extensions: GL_NV_conditional_render GL_ARB_debug_output GL_EXT_texture_integer GL_EXT_vertex_array_bgra GL_ARB_pixel_buffer_object GL_MESA_framebuffer_flip_y GL_ARB_bindless_texture GL_ARB_vertex_array_bgra GL_EXT_timer_query GL_ARB_derivative_control GL_ARB_texture_compression_rgtc GL_EXT_window_rectangles GL_ANGLE_texture_compression_dxt5 GL_EXT_packed_float GL_ARB_conservative_depth GL_ARB_texture_buffer_range GL_EXT_texture_compression_rgtc GL_ARB_framebuffer_sRGB GL_EXT_blend_equation_separate GL_ARB_tessellation_shader GL_ARB_transform_feedback2 GL_ARB_texture_border_clamp GL_ATI_blend_equation_separate GL_ARB_sampler_objects GL_AMD_texture_texture4 GL_ARB_multi_draw_indirect GL_ARB_shader_objects GL_ARB_query_buffer_object GL_ARB_texture_storage_multisample GL_ARB_draw_buffers GL_AMD_multi_draw_indirect GL_ARB_ES3_2_compatibility GL_ARB_polygon_offset_clamp GL_NV_alpha_to_coverage_dither_control GL_ARB_color_buffer_float GL_ATI_texture_mirror_once GL_ARB_shader_texture_lod GL_EXT_shader_image_load_store GL_ARB_draw_buffers_blend GL_NV_shader_atomic_int64 GL_KHR_robust_buffer_access_behavior GL_ARB_copy_buffer GL_EXT_shader_image_load_formatted GL_ARB_shader_subroutine GL_ARB_spirv_extensions GL_ARB_shader_bit_encoding GL_ARB_texture_float GL_ARB_shader_atomic_counters GL_EXT_framebuffer_sRGB GL_EXT_texture_compression_dxt1 GL_ARB_shading_language_include GL_ARB_instanced_arrays GL_ARB_multi_bind GL_NVX_gpu_memory_info GL_ARB_gpu_shader_int64 GL_ARB_clear_buffer_object GL_ATI_meminfo GL_EXT_provoking_vertex GL_EXT_framebuffer_multisample GL_ARB_map_buffer_range GL_ANGLE_texture_compression_dxt3 GL_ARB_explicit_attrib_location GL_EXT_draw_instanced GL_ARB_vertex_shader GL_EXT_polygon_offset_clamp GL_EXT_texture_compression_s3tc GL_EXT_texture_sRGB_R8 GL_NV_copy_image GL_ARB_ES3_1_compatibility GL_ARB_parallel_shader_compile GL_ARB_shader_atomic_counter_ops GL_ARB_blend_func_extended GL_KHR_textur
[krita] [Bug 487817] Every time I use the pen on the tablet Krita automatically recognizes it as the move tool, it doesn't work as a brush, even if I selected the brush the pen doesn't work as a brush
https://bugs.kde.org/show_bug.cgi?id=487817 Halla Rempt changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG CC||ha...@valdyas.org --- Comment #1 from Halla Rempt --- Originally, your subject said "pan tool", which means you configured your pen to send a middle-mouse button press on pressing the pen to the canvas. It is impossible for a pen press to invoke the move tool, unless you reconfigured the pen press to invoke the M button. But in any case, this is not a bug in Krita. Just reset your misconfiguration: https://docs.krita.org/en/KritaFAQ.html#resetting-krita-configuration -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 487817] Every time I use the pen on the tablet Krita automatically recognizes it as the move tool, it doesn't work as a brush, even if I selected the brush the pen doesn't work as a brush
https://bugs.kde.org/show_bug.cgi?id=487817 gustavomanoelni...@usp.br changed: What|Removed |Added Summary|Every time I use the pen on |Every time I use the pen on |the tablet Krita|the tablet Krita |automatically recognizes it |automatically recognizes it |as the pan tool, it doesn't |as the move tool, it |work as a brush, even if I |doesn't work as a brush, |selected the brush the pen |even if I selected the |doesn't work as a brush.|brush the pen doesn't work |It's not a pen problem |as a brush. It's not a pen |since this problem of mine |problem since this problem |only happens in Krita. |of mine only happens in ||Krita. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 487817] New: Every time I use the pen on the tablet Krita automatically recognizes it as the pan tool, it doesn't work as a brush, even if I selected the brush the pen doesn't work as a b
https://bugs.kde.org/show_bug.cgi?id=487817 Bug ID: 487817 Summary: Every time I use the pen on the tablet Krita automatically recognizes it as the pan tool, it doesn't work as a brush, even if I selected the brush the pen doesn't work as a brush. It's not a pen problem since this problem of mine only happens in Krita. Classification: Applications Product: krita Version: 5.2.2 Platform: Compiled Sources OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: gustavomanoelni...@usp.br 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. 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 Krita Version: 5.2.2 Installation type: installer / portable package Hidpi: true Qt Version (compiled): 5.15.7 Version (loaded): 5.15.7 OS Information Build ABI: x86_64-little_endian-llp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: winnt Kernel Version: 10.0.22631 Pretty Productname: Windows 10 Version 2009 Product Type: windows Product Version: 10 Locale Languages: pt_BR, pt, pt_Latn_BR, en_US, en, en_Latn_US C locale: C QLocale current: pt QLocale system: pt QTextCodec for locale: UTF-8 Process ACP: 65001 (UTF-8) System locale default ACP: 1252 (ANSI - Latino I) OpenGL Info Vendor: "Google Inc. (Intel)" Renderer: "ANGLE (Intel, Intel(R) Iris(R) Xe Graphics Direct3D11 vs_5_0 ps_5_0, D3D11-31.0.101.4502)" Driver version: "OpenGL ES 3.0.0 (ANGLE 2.1.0 git hash: f2280c0c5f93+krita_qt5)" Shading language: "OpenGL ES GLSL ES 3.00 (ANGLE 2.1.0 git hash: f2280c0c5f93+krita_qt5)" Requested format: QSurfaceFormat(version 3.0, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::DoubleBuffer, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) Current format: QSurfaceFormat(version 3.0, options QFlags(), depthBufferSize 24, redBufferSize 8, greenBufferSize 8, blueBufferSize 8, alphaBufferSize 8, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 0, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) GL version: 3.0 Supports deprecated functions false Is OpenGL ES: true supportsBufferMapping: true supportsBufferInvalidation: false forceDisableTextureBuffers: true Extensions: GL_ANGLE_texture_compression_dxt3 GL_EXT_draw_elements_base_vertex GL_NV_fence GL_EXT_multisampled_render_to_texture GL_OES_draw_elements_base_vertex GL_EXT_texture_compression_bptc GL_EXT_map_buffer_range GL_OES_compressed_EAC_R11_unsigned_texture GL_EXT_blend_minmax GL_EXT_texture_format_BGRA GL_EXT_robustness GL_OES_EGL_image_external GL_OES_surfaceless_context GL_ANGLE_texture_usage GL_EXT_blend_func_extended GL_ANGLE_lossy_etc_decode GL_OES_EGL_image_external_essl3 GL_CHROMIUM_bind_generates_resource GL_OES_compressed_ETC2_RGB8_texture GL_CHROMIUM_copy_compressed_texture GL_ANGLE_robust_client_memory GL_OES_element_index_uint GL_NV_framebuffer_blit GL_OES_texture_stencil8 GL_OES_compressed_EAC_RG11_signed_texture GL_OES_texture_npot GL_OES_compressed_ETC2_sRGB8_alpha8_texture GL_ANGLE_multiview_multisample GL_CHROMIUM_bind_uniform_location GL_EXT_clip_control GL_ANGLE_pack_reverse_row_order GL_EXT_texture_compression_dxt1 GL_OES_depth32 GL_OES_fbo_render_mipmap GL_OES_draw_buffers_indexed GL_ANGLE_base_vertex_base_instance GL_ANGLE_get_serialized_context_string GL_OES_texture_half_float_linear GL_NV_EGL_stream_consumer_external GL_ANGLE_get_tex_level_parameter GL_EXT_disjoint_timer_query GL_EXT_debug_label GL_EXT_texture_storage GL_OES_vertex_array_object GL_ANGLE_translated_shader_source GL_EXT_draw_buffers_indexed GL_EXT_sRGB GL_EXT_texture_compression_s3tc_srgb GL_EXT_color_buffer_half_float GL_EXT_EGL_image_external_wrap_modes GL_ANGLE_base_vertex_base_instance_shader_builtin GL_ANGLE
[digikam] [Bug 487370] Face Recognition crashes - pre-release built on 20-05-2024 07:25
https://bugs.kde.org/show_bug.cgi?id=487370 --- Comment #31 from Maik Qualmann --- Git commit 55103429ef282047ca89b016a283f7b149df339c by Maik Qualmann. Committed on 30/05/2024 at 20:59. Pushed by mqualmann into branch 'master'. Revert "switch Windows build to rev 7d64840905ba968de186a9f30bc3ccff64c89224" M +2-2project/bundles/vcpkg/config.sh https://invent.kde.org/graphics/digikam/-/commit/55103429ef282047ca89b016a283f7b149df339c -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 487370] Face Recognition crashes - pre-release built on 20-05-2024 07:25
https://bugs.kde.org/show_bug.cgi?id=487370 --- Comment #30 from Maik Qualmann --- Git commit 476c2591229145431e1f374dd3e353eff552df17 by Maik Qualmann. Committed on 30/05/2024 at 20:57. Pushed by mqualmann into branch 'master'. not apply style changes to QComboBox on Windows and Qt-6.7.0 M +6-0core/utilities/facemanagement/widgets/assignnamewidget_p.cpp M +1-0core/utilities/facemanagement/widgets/assignnamewidget_p.h https://invent.kde.org/graphics/digikam/-/commit/476c2591229145431e1f374dd3e353eff552df17 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487816] New: No clean way to change the wallpaper for distributions
https://bugs.kde.org/show_bug.cgi?id=487816 Bug ID: 487816 Summary: No clean way to change the wallpaper for distributions Classification: Plasma Product: kwin Version: 6.0.5 Platform: postmarketOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: ollieparan...@postmarketos.org Target Milestone: --- There is no clean way to change the default wallpaper for distributions. It would be great if there was a simple config file that the distribution could write, which would then set a different wallpaper as default. (The default wallpaper of Plasma 6 is really beautiful, but we are looking into setting a consistent wallpaper across all UIs in postmarketOS, and changing it with every release.) For example, with GNOME this can be done by writing a file like this to /usr/share/glib-2.0/schemas/10_pmOS-wallpaper.gschema.override: [org.gnome.desktop.background] picture-uri='file:///usr/share/wallpapers/postmarketos/contents/images/2707x2707.png' picture-uri-dark='file:///usr/share/wallpapers/postmarketos/contents/images_dark/2707x2707.png' Doing it for Plasma only seems to work by talking to the D-Bus API within a running Plasma session. I've done it via the following hack for now: 1. Write to /etc/skel/.config/autostart/set-plasma-wallpaper.desktop: [Desktop Entry] Exec=/usr/libexec/postmarketos/set-plasma-wallpaper.sh Name=Set postmarketOS Wallpaper for Plasma Terminal=False Type=Application 2. Write to /usr/libexec/postmarketos/set-plasma-wallpaper.sh: #!/bin/sh MARKER=~/.local/state/postmarketos/plasma-wallpaper-has-been-set WALLPAPER_PATH="/usr/share/wallpapers/postmarketos" # Only run this script in Plasma sessions. This variable is set in in both # Plasma Desktop and Plasma Mobile (unlike e.g. XDG_DESKTOP_SESSION). if [ -z "$KDE_FULL_SESSION" ]; then exit 1 fi # Only run this script once. If the user selects a different wallpaper # afterwards, it should not be changed. if [ -e "$MARKER" ]; then exit 0 fi echo "set-plasma-wallpaper: changing to: $WALLPAPER_PATH" # Unfortunately this fails if the D-Bus API isn't available yet. So we have to # try multiple times. for i in $(seq 1 30); do sleep 1 if ! plasma-apply-wallpaperimage "$WALLPAPER_PATH"; then continue fi mkdir -p "$(dirname "$MARKER")" touch "$MARKER" echo "set-plasma-wallpaper: success" exit 0 done echo "set-plasma-wallpaper: failed" exit 1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487785] Dolphin does not list files ending with the extension ".old" (and maybe others?)
https://bugs.kde.org/show_bug.cgi?id=487785 Paul Worrall changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #5 from Paul Worrall --- Sorry, the tool-tip says "Backup files are the files whose mime-type is application/x-trash, patterns: *~, *%, *.bak, *.old, *.sik". I think we should mark this bug as fixed on the grounds that the behaviour is optional in later versions of Dolphin? Reopen if you disagree. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487815] New: After changing the CPU bar chart to application list, the entire shell freezes due to a binding loop
https://bugs.kde.org/show_bug.cgi?id=487815 Bug ID: 487815 Summary: After changing the CPU bar chart to application list, the entire shell freezes due to a binding loop Classification: Plasma Product: plasmashell Version: 6.0.5 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: fifis.hi...@gmail.com CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 SUMMARY After I accidentally changed the display style of the CPU usage tray sensor to ‘Application list’, the entire shell froze; Alt+Tab and shortcuts (e.g. Terminal, Ctrl+Alt+T) still work. Rebooting changes nothing – it still freezes. STEPS TO REPRODUCE 1. In the CPU usage monitor in the system tray, change ‘Bar chart’ to ‘Application list’ 2. The system tray and desktop freeze and become unresponsive. OBSERVED RESULT After `kquitapp5 plasmashell` and `kstart5 plasmashell`, here is the console log: ``` (base) [avk@UL0012159 ~]$ kstart5 plasmashell (base) [avk@UL0012159 ~]$ kf.plasma.quick: Applet preload policy set to 1 file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:196:25: QML FolderViewDropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth" file:///usr/share/plasma/plasmoids/org.kde.desktopcontainment/contents/ui/main.qml:196:25: QML FolderViewDropArea (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "minimumWidth" qml: The backend got an unknown wallpaper provider type. The wallpaper will now fall back to the default. Please check your wallpaper configuration! file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:162:21: QML KSortFilterProxyModel: Binding loop detected for property "sourceModel" file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/main.qml:162:21: QML KSortFilterProxyModel: Binding loop detected for property "sourceModel" qml: SystemTray ItemLoader: Invalid state, cannot determine source! qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile QFont::setPointSizeF: Point size <= 0 (0.00), must be greater than 0 QFont::setPointSizeF: Point size <= 0 (0.00), must be greater than 0 file:///usr/lib/qt6/qml/org/kde/kirigami/Dialog.qml:334:18: QML ScrollView: Binding loop detected for property "calculatedImplicitWidth" file:///usr/lib/qt6/qml/org/kde/kirigami/Dialog.qml:386:33: QML Binding: Binding loop detected for property "target" file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/main.qml:38:25: QML FullRepresentation: Binding loop detected for property "contentItem" file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/main.qml:38:25: QML FullRepresentation: Binding loop detected for property "contentItem" file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/main.qml:38:25: QML FullRepresentation: Binding loop detected for property "contentItem" ... ``` EXPECTED RESULT Expected responsive shell and working widget that would show the CPU usage. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.0.5 Qt Version: qt6-base 6.7.1-3, qt5-base 5.15.14+kde+r140-1 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 487370] Face Recognition crashes - pre-release built on 20-05-2024 07:25
https://bugs.kde.org/show_bug.cgi?id=487370 --- Comment #29 from Maik Qualmann --- Ok, back to master. I'm thinking of a workaround up to Qt-6.7.1. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 487370] Face Recognition crashes - pre-release built on 20-05-2024 07:25
https://bugs.kde.org/show_bug.cgi?id=487370 --- Comment #28 from caulier.gil...@gmail.com --- Hum very possible. In all case, you have right and i'm wrong. the anterior git rev do not compile with Qt 6.7 with boost based classes : E:\b\dktemp\digikam-master\core\libs\database\history\itemhistorygraphmodel.cpp(508,17): error C2666: 'Digikam::Graph::Vertex::operator ==': overloaded functions have similar conversions [E:\b\dktemp\digikam-master\build\core\libs\database\digikamdatabase_obj.vcxproj] E:\b\dktemp\digikam-master\core\libs\database\history\itemhistorygraph_boost.h(201,14): could be 'bool Digikam::Graph::Vertex::operator ==(const unsigned __int64 &) const' [rewritten expression '!(x == y)'] E:\b\dktemp\digikam-master\core\libs\database\history\itemhistorygraph_boost.h(201,14): or 'bool Digikam::Graph::Vertex::operator ==(const unsigned __int64 &) const' [synthesized expression '!(y == x)'] E:\b\dktemp\digikam-master\core\libs\database\history\itemhistorygraphmodel.cpp(508,17): or 'built-in C++ operator!=(unsigned __int64, unsigned __int64)' E:\b\dktemp\digikam-master\core\libs\database\history\itemhistorygraphmodel.cpp(508,17): while trying to match the argument list '(const Digikam::Graph::Vertex, Digikam::Graph::Vertex)' E:\b\dktemp\digikam-master\core\libs\database\history\itemhistorygraphmodel.cpp(547,14): error C2666: 'Digikam::Graph::Vertex::operator ==': overloaded functions have similar conversions [E:\b\dktemp\digikam-master\build\core\libs\database\digikamdatabase_obj.vcxproj] E:\b\dktemp\digikam-master\core\libs\database\history\itemhistorygraph_boost.h(201,14): could be 'bool Digikam::Graph::Vertex::operator ==(const unsigned __int64 &) const' E:\b\dktemp\digikam-master\core\libs\database\history\itemhistorygraph_boost.h(201,14): or 'bool Digikam::Graph::Vertex::operator ==(const unsigned __int64 &) const' [synthesized expression 'y == x'] E:\b\dktemp\digikam-master\core\libs\database\history\itemhistorygraphmodel.cpp(547,14): or 'built-in C++ operator==(unsigned __int64, unsigned __int64)' E:\b\dktemp\digikam-master\core\libs\database\history\itemhistorygraphmodel.cpp(547,14): while trying to match the argument list '(const Digikam::Graph::Vertex, const Digikam::Graph::Vertex)' Gilles -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 487370] Face Recognition crashes - pre-release built on 20-05-2024 07:25
https://bugs.kde.org/show_bug.cgi?id=487370 --- Comment #27 from Maik Qualmann --- Gilles, I think this could be the Qt bug, only Qt-6.7.0 is affected and with style changes. We change the style of the ComboBox. https://bugreports.qt.io/browse/QTBUG-124191 Maik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487664] [BUG] Panel being drawn over desktop folder labels
https://bugs.kde.org/show_bug.cgi?id=487664 --- Comment #4 from jman12...@live.com --- (In reply to David Edmundson from comment #3) > The window manager does, it's complicated logic that we're not duplicating. I tried hard-coding the correct height for myself but it didn't seem to work. Can you direct me to where the KDE panel gets avoided so that I can piggyback off of that code and fix it for myself? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 477347] System tray icon is missing in Waybar on Hyprland (Wayland)
https://bugs.kde.org/show_bug.cgi?id=477347
salsa...@gmail.com changed:
What|Removed |Added
CC||salsa...@gmail.com
Ever confirmed|0 |1
Status|REPORTED|CONFIRMED
--- Comment #3 from salsa...@gmail.com ---
Did you fix the errors?
error activating kdeconnectd:
QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "Could not activate
remote peer: unit failed.")
error activating kdeconnectd:
QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "Could not activate
remote peer: unit failed.")
i get the same errrors its work on kde plasma 6 but not in hyprland .
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 487814] New: Dolphin crashed while collapsing a folder
https://bugs.kde.org/show_bug.cgi?id=487814 Bug ID: 487814 Summary: Dolphin crashed while collapsing a folder Classification: Applications Product: dolphin Version: 22.12.3 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: k...@assez.biz CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (22.12.3) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-21-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: Dolphin crashed while collapsing a folder The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7f5ebb2666be in KFileItemModel::expandedParentsCount(KFileItemModel::ItemData const*) () from /lib/x86_64-linux-gnu/libdolphinprivate.so.5 #5 0x7f5ebb294911 in KItemListView::hasSiblingSuccessor(int) const () from /lib/x86_64-linux-gnu/libdolphinprivate.so.5 #6 0x7f5ebb29607c in KItemListView::updateSiblingsInformation(int, int) () from /lib/x86_64-linux-gnu/libdolphinprivate.so.5 #7 0x7f5ebb29dfa5 in KItemListView::slotItemsRemoved(KItemRangeList const&) () from /lib/x86_64-linux-gnu/libdolphinprivate.so.5 #8 0x7f5eb9209f4f in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f5ebb252d95 in KItemModelBase::itemsRemoved(KItemRangeList const&) () from /lib/x86_64-linux-gnu/libdolphinprivate.so.5 #10 0x7f5ebb275b5a in KFileItemModel::setExpanded(int, bool) () from /lib/x86_64-linux-gnu/libdolphinprivate.so.5 #11 0x7f5ebb28b2ec in KItemListController::onRelease(QPointF const&, QFlags, QFlags, bool) () from /lib/x86_64-linux-gnu/libdolphinprivate.so.5 #12 0x7f5ebb28b4a0 in KItemListController::mouseReleaseEvent(QGraphicsSceneMouseEvent*, QTransform const&) () from /lib/x86_64-linux-gnu/libdolphinprivate.so.5 #13 0x7f5ebb28ea79 in KItemListController::processEvent(QEvent*, QTransform const&) () from /lib/x86_64-linux-gnu/libdolphinprivate.so.5 #14 0x7f5ebb29f66c in KItemListView::event(QEvent*) () from /lib/x86_64-linux-gnu/libdolphinprivate.so.5 #15 0x7f5eb9ca4fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #16 0x7f5eb91d26f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #17 0x7f5eb9fd7985 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #18 0x7f5eb9fd7d25 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #19 0x7f5eb9fdd84a in QGraphicsScene::mouseReleaseEvent(QGraphicsSceneMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f5eb9fea069 in QGraphicsScene::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #21 0x7f5eb9ca4fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #22 0x7f5eb91d26f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7f5eba006ffc in QGraphicsView::mouseReleaseEvent(QMouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #24 0x7f5eb9ce6db8 in QWidget::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #25 0x7f5eb9d9248e in QFrame::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #26 0x7f5eb91d247b in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7f5eb9ca4f9e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #28 0x7f5eb9cad552 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #29 0x7f5eb91d26f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #30 0x7f5eb9cab65e in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7f5eb9cffbd8 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #32 0x7f5eb9d02f60 in ?? () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #33 0x7f5eb9ca4fae in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #34 0x7f5eb91d26f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #35 0x7f5eb95b13ed in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #36 0x7f5eb9585cac in QWindowSystemInterface::sendWindowSystemEvent
[Powerdevil] [Bug 487706] "Presentation mode" wont disappear from the list of inhibitions when disabled from System Tray -> Display Configuration
https://bugs.kde.org/show_bug.cgi?id=487706 Jakob Petsovits changed: What|Removed |Added CC||jpe...@petsovits.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487713] Panel doesn't work occasionally when not present on primary display
https://bugs.kde.org/show_bug.cgi?id=487713 --- Comment #3 from eputty...@gmail.com --- (In reply to David Edmundson from comment #2) > please confirm if this is still an issue with the newly coming driver The issue is resolved with both the latest proprietary driver and the beta proprietary driver, all around working as intended now. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482950] KRDC RDP Blue screen shows nothing
https://bugs.kde.org/show_bug.cgi?id=482950 --- Comment #21 from Mykola Krachkovsky --- If you use openSUSE Tubleweed, you can either 1. Install older KRDC (krdc5 — 23.08.4) from this repo: https://download.opensuse.org/repositories/home:/wolfi323:/branches:/KDE:/Frameworks5/openSUSE_Tumbleweed/ Which could be installed simultaneously with KRDC based on KF6. OR 2. Install develompent version from https://download.opensuse.org/repositories/KDE:/Unstable:/Applications/KDE_Unstable_Frameworks_openSUSE_Factory/ But in my experience this version has problems with mouse input with scaling or multiple screens (not sure) on wayland session at least. -- You are receiving this mail because: You are watching all bug changes.
[libalkimia] [Bug 487813] New: Add
https://bugs.kde.org/show_bug.cgi?id=487813 Bug ID: 487813 Summary: Add Classification: Frameworks and Libraries Product: libalkimia Version: master Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: Online quotes widget Assignee: kmymoney-de...@kde.org Reporter: ralf.habac...@freenet.de Target Milestone: --- Created attachment 170008 --> https://bugs.kde.org/attachment.cgi?id=170008&action=edit test case SUMMARY In KMyMoney files, the names of online quote sources used are stored in the price or rate queried. STEPS TO REPRODUCE 1. start kmymoney from master branch 2. open appended file 4. select menu entry Extra->"Update shares or exchange rates" 5. select the present entry and press "online course notes" OBSERVED RESULT If these prices or rates are to be updated in the future by an installed remote online source, there are currently two options: 1. the new source must be selected for each entry in the "Update shares or exchange rates" dialog. This has the disadvantage that you have to do this for all existing price or short entries. 2. the installed remote online source is duplicated and the name is changed to the previously used source. The disadvantage here is that this process must be repeated manually after updating the source. EXPECTED RESULT As an alternative, it would therefore be helpful if you could give a remote online source additional names under which this source is available or that you can create a reference to a remote online source, which then receives the required name. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487043] Extreme stutters/hangs when using certain desktop effects when "~/.cache" is on slow storage
https://bugs.kde.org/show_bug.cgi?id=487043 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 433569] When using Header colors, color change for titlebar and window header isn't synchronized when window becomes active or inactive
https://bugs.kde.org/show_bug.cgi?id=433569 pikaphase changed: What|Removed |Added CC||pikaph...@tutanota.com --- Comment #12 from pikaphase --- Confirmed on Plasma 6.1 Beta (6.0.90). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 487370] Face Recognition crashes - pre-release built on 20-05-2024 07:25
https://bugs.kde.org/show_bug.cgi?id=487370 --- Comment #26 from caulier.gil...@gmail.com --- Git commit 2888c174b8b66f4a6091e9eb7487fe63ebd1b8e7 by Gilles Caulier. Committed on 30/05/2024 at 19:44. Pushed by cgilles into branch 'master'. switch Windows build to rev 7d64840905ba968de186a9f30bc3ccff64c89224 M +2-2project/bundles/vcpkg/config.sh https://invent.kde.org/graphics/digikam/-/commit/2888c174b8b66f4a6091e9eb7487fe63ebd1b8e7 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 487370] Face Recognition crashes - pre-release built on 20-05-2024 07:25
https://bugs.kde.org/show_bug.cgi?id=487370 --- Comment #25 from caulier.gil...@gmail.com --- yes sure... -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 487812] I changed my brightness by mistake, the second screen is stuck on a wrong brightness value
https://bugs.kde.org/show_bug.cgi?id=487812 --- Comment #1 from V --- Also specs: CPU: R7 7800X3D RAM: 32Gb GPU: RX 7900 XTX Driver: Mesa 24.0.7 and i run wayland. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 487370] Face Recognition crashes - pre-release built on 20-05-2024 07:25
https://bugs.kde.org/show_bug.cgi?id=487370 --- Comment #24 from Maik Qualmann --- Hi Gilles, this was a revert. I'm lost at the moment, can we build the corresponding commit number that still worked with Qt-6.6.1 to really rule out code changes in digiKam? Maik -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 487812] New: I changed my brightness by mistake, the second screen is stuck on a wrong brightness value
https://bugs.kde.org/show_bug.cgi?id=487812 Bug ID: 487812 Summary: I changed my brightness by mistake, the second screen is stuck on a wrong brightness value Classification: Plasma Product: Powerdevil Version: 6.0.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: c9lyw0...@mozmail.com CC: m...@ratijas.tk, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY I scrolled by mistake on the brightness tray icon, messing up the brightness of my screens. Now one of my 2 screens is stuck in an insanely bright mode, despite controlling the brightness cursor on the tray (apparently the only place where i can change that value), one screen changes, but not the other. STEPS TO REPRODUCE 1. scroll by mistake like a moron on the tray icon 2. Brightness messed up 3. Enjoy the flashbang on the second screen for the rest of your life. :) OBSERVED RESULT Brightness not changing on the second screen. EXPECTED RESULT Brightness should change as it sometimes does on the second screen. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Void-Linux 6.9.2 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.6.0 ADDITIONAL INFORMATION Nothing. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 487811] Cannot switch to external screen in the Display Configuration
https://bugs.kde.org/show_bug.cgi?id=487811 --- Comment #1 from Oleksii Zolotarevskyi --- Created attachment 170007 --> https://bugs.kde.org/attachment.cgi?id=170007&action=edit Cannot switch to the external screen -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481085] Battery widget in panel doesn't save "show percent" setting
https://bugs.kde.org/show_bug.cgi?id=481085 Jakub changed: What|Removed |Added CC||jjaruszew...@outlook.com --- Comment #10 from Jakub --- Can still reproduce on Plasma 6.0.5 on two different laptops. Now one has this setting permanently disabled (it was a relatively fresh plasma 6 install). And one has this setting permanently enabled (I enabled it back in Plasma 5). Either way changes to this setting does not save the changes to the config file :c -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 487811] New: Cannot switch to external screen in the Display Configuration
https://bugs.kde.org/show_bug.cgi?id=487811 Bug ID: 487811 Summary: Cannot switch to external screen in the Display Configuration Classification: Plasma Product: KScreen Version: 6.0.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: OSD and Plasma applet Assignee: kscreen-bugs-n...@kde.org Reporter: rocking...@proton.me Target Milestone: --- *** I have a laptop with a single screen connected via DisplayPort. When I use only the laptop screen and select "Switch to External Screen" in the Display Configuraion menu in the System Tray, both screens turn black. The system panel disappears and the wallpaper changes to black color (see the demonstration in the attachment). *** SUMMARY STEPS TO REPRODUCE 1. Have a laptop with the external screen connected 2. Activate only the laptop screen in the display configuration and deactivate the external screen 3. Select "Switch to external screen" in the Display Configuration of the System Tray OBSERVED RESULT The desktop is not switched to the external screen. The Plasma Panel disappears from the desktop, the wallpaper changes to the black color. EXPECTED RESULT The desktop is switched to the external screen. The laptop screen is deactivated. The plasma desktop remains functional. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Stable KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION Graphics Platform: X11 Graphics Adapter: Nvidia+Intel, with Nvidia set as primary GPU Graphics Driver Version: 550.78 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 487799] Geolocalization icon always black in thumbnail view
https://bugs.kde.org/show_bug.cgi?id=487799 Maik Qualmann changed: What|Removed |Added Version Fixed In||8.4.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 487799] Geolocalization icon always black in thumbnail view
https://bugs.kde.org/show_bug.cgi?id=487799 --- Comment #9 from Maik Qualmann --- Ok, dann ist es klar, dass das System Symboldesign verwendet werden muss. Es gibt einige wenige Symbole in digiKam die nicht automatisch die Farbe wechseln, wenn das Farbschema gewechselt wird, dies ist in digiKam-8.4.0 behoben. OpenSUSE hat digiKam-8.3.0 noch gegen Qt5 gebaut, Qt6 währe auch schon möglich. Maik -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 487810] New: adding and changing languages gives me an error even though it works
https://bugs.kde.org/show_bug.cgi?id=487810 Bug ID: 487810 Summary: adding and changing languages gives me an error even though it works Classification: Applications Product: systemsettings Version: 6.0.5 Platform: Other OS: Linux Status: REPORTED Keywords: accessibility, usability Severity: normal Priority: NOR Component: kcm_regionandlang Assignee: plasma-b...@kde.org Reporter: eli.we...@gmail.com CC: hanyo...@protonmail.com Target Milestone: --- SUMMARY I have a fresh fedora 40 installation with the language set to german (switzerland). when i want to add a language or change the current one, after selecting a language the following message appears: "Could not find the system's available locales using the localectl tool. Please file a bug report about this at https://bugs.kde.org"; But after a restart, the language is changed/added and works and no error message shows up in settings. localectl outputs the following though: System Locale: LANG=de_CH.UTF-8 VC Keymap: ch X11 Layout: ch X11 Model: pc105 SOFTWARE/OS VERSIONS Linux/KDE Plasma: fedora 40 (available in About System) KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 487150] Blue dot in lower right part of updates icon persists after software update and reboot. Discover indicates system up to date and icon (and sometimes a banner) alerts that updat
https://bugs.kde.org/show_bug.cgi?id=487150 --- Comment #11 from Peter --- FYI, this issue is resolved. I did not end up doing a full clean install, and best I can tell, all parts of my system, including icon visibility and updates with Discover are working perfectly. I did unpin and then replace several icons on task manager and that seems to have addressed all the messed up icons. On Friday, May 24th, 2024 at 4:08 AM, Peter H. Larkam wrote: > > > "No packages requiring newer versions." > > How about you close out the bug and spend zero more of your time & thought > about it. I will do a clean install with latest version of Neon and not use > the install script program that "broke" the system. I was able to get a clean > exe file for Windows apart from the company's packaged script for Linux. > Hopefully I can get all that to work fine just using stock wine and > PlayOnLinux. > > Sorry to have taken your time on a problem I caused that is not a true "bug." > Really appreciate all that you and others do to keep the system so elegant > and functional. > > Cheers. > > > On Thursday, May 23rd, 2024 at 11:32 PM, Harald Sitter > bugzilla_nore...@kde.org wrote: > > > https://bugs.kde.org/show_bug.cgi?id=487150 > > > > --- Comment #9 from Harald Sitter sit...@kde.org --- > > > > Your system is in a broken state because of the wine stuff. Not sure what > > to do > > about it though, technically we should be telling you about this in the UI > > somehow but I am not sure which component fails to propagate the error. > > > > What happens when you run `pkcon update` > > > > -- > > You are receiving this mail because: > > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487785] Dolphin does not list files ending with the extension ".old" (and maybe others?)
https://bugs.kde.org/show_bug.cgi?id=487785 --- Comment #4 from Gunter Ohrner --- Ok, curious... Unfortunately, KDE neon currently does not seem to provide a more recent Dolphin version. Nevertheless, it should be configurable in any case, also in my version, as it's a somewhat "surprising" behaviour. (Who actually decides which extensions are considered as "hidden" files - is it hard coded or also configurable? It will surely be heavily dependent on the user's locale?) -- You are receiving this mail because: You are watching all bug changes.
[angelfish] [Bug 487804] Icons not appearing in menu bar & unable to upload attachments
https://bugs.kde.org/show_bug.cgi?id=487804 --- Comment #5 from josh.lelo...@gmail.com --- Thank you. On Thu, May 30, 2024 at 12:22 PM Jonah Brüchert wrote: > https://bugs.kde.org/show_bug.cgi?id=487804 > > Jonah Brüchert changed: > >What|Removed |Added > > > Resolution|--- |DOWNSTREAM > Status|REPORTED|RESOLVED > > --- Comment #4 from Jonah Brüchert --- > * missing icons => only happens when environment sets no theme or one > without > the required icons > * missing ui style => only happens if environment sets none, we have since > added a fallback > * file upload is at least not broken on the Qt 6 based current builds. > > Consider using the flatpak instead, the version in Debian is from 2022. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 487370] Face Recognition crashes - pre-release built on 20-05-2024 07:25
https://bugs.kde.org/show_bug.cgi?id=487370 --- Comment #23 from caulier.gil...@gmail.com --- Hi Maik, This Windows build is restarted just now including your last changes... Gilles -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 403324] Can only drag tabs from one window into another when using single-process mode
https://bugs.kde.org/show_bug.cgi?id=403324 --- Comment #15 from TraceyC --- Current system details: Operating System: Solus 4.5 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 Kernel Version: 6.8.11-292.current (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[angelfish] [Bug 487804] Icons not appearing in menu bar & unable to upload attachments
https://bugs.kde.org/show_bug.cgi?id=487804 Jonah Brüchert changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #4 from Jonah Brüchert --- * missing icons => only happens when environment sets no theme or one without the required icons * missing ui style => only happens if environment sets none, we have since added a fallback * file upload is at least not broken on the Qt 6 based current builds. Consider using the flatpak instead, the version in Debian is from 2022. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 403324] Can only drag tabs from one window into another when using single-process mode
https://bugs.kde.org/show_bug.cgi?id=403324 --- Comment #14 from TraceyC --- (In reply to tcanabrava from comment #12) > Created attachment 170005 [details] > attachment-2267002-0.html > > probably related to wayland. can you test on a x11 session? Can confirm that the inability to drag tabs to a new window at all is specific to Wayland. In an X11 session: - Started 2 Konsole windows from Kickoff - Created a second tab in one window and dragged it to the second window Also successful when launching from KRunner -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487809] New: Icons in the Taskbar are blurry, become sharp when hovering over them
https://bugs.kde.org/show_bug.cgi?id=487809 Bug ID: 487809 Summary: Icons in the Taskbar are blurry, become sharp when hovering over them Classification: Plasma Product: plasmashell Version: 6.0.5 Platform: Other OS: Linux Status: REPORTED Keywords: usability Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: elias@wiesmann.online CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY Fresh Fedora 40 installation, the icons in the taskbar appear blurry on startup, hovering over an icon fixes that and it becomes sharp. STEPS TO REPRODUCE 1. Boot the System 2. Log in 3. Most Taskbar Icons are blurry 4. Hovering over an Icon makes it sharp OBSERVED RESULT blurry icons on startup EXPECTED RESULT sharp icons SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 40 (available in About System) KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION Hardware: 4 × Intel® Core™ i5-7400T CPU @ 2.40GHz Mesa Intel® HD Graphics 630 this is a mini pc with a FullHD screen, all settings on standard after a fresh install. No scaling I have a laptop also running a fresh fedora 40 install, haven't noticed this issue there yet, but cannot confirm at the moment since no access to the laptop at the time of writing Since this is my first bug report, please correct me if I made mistakes/give feedback what to do better next time -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 403324] Can only drag tabs from one window into another when using single-process mode
https://bugs.kde.org/show_bug.cgi?id=403324 --- Comment #13 from postix --- > probably related to wayland. can you test on a x11 session? Can confirm that it doesn't work on Plasma 6.0.5 Wayland and Konsole 24.0.2. On X11 it works by sliding the tab over to another Konsole window, however the whole UI is pretty non intuitive and difficult to use. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 487743] No keyboard light control and always on by default
https://bugs.kde.org/show_bug.cgi?id=487743 Jakob Petsovits changed: What|Removed |Added CC||jpe...@petsovits.com -- You are receiving this mail because: You are watching all bug changes.
