[dolphin] [Bug 487307] New: Dragging text file from Dolphin to Kate window crashes instance of Dolphin window and file is not opened in Kate...
https://bugs.kde.org/show_bug.cgi?id=487307 Bug ID: 487307 Summary: Dragging text file from Dolphin to Kate window crashes instance of Dolphin window and file is not opened in Kate... Classification: Applications Product: dolphin Version: 24.02.2 Platform: Arch Linux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: squashyna...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Dolphin frequently crashes during file dragging. STEPS TO REPRODUCE 1. Open Dolphin and select a text file. 2. Open Kate and start a new file . 3. Drag the text file you'd like to edit from Dolphin to the Kate window. OBSERVED RESULT Dolphin window crashes and file is not opened in Kate. Other open Dolphin windows seem unaffected.. EXPECTED RESULT Dolphin doesn't crash and Kate opens the text file normally. SOFTWARE/OS VERSIONS Operating System: Garuda Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.1.0 Qt Version: 6.7.0 Kernel Version: 6.8.9-zen1-2-zen (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics Manufacturer: Framework Product Name: Laptop System Version: AB ADDITIONAL INFORMATION Tuesday, May 21, 2024 2:32:01 AM EDTsystemd-coredumpProcess 445682 (dolphin) of user 1000 dumped core. Stack trace of thread 445682: #0 0x7bc6c70a8e44 n/a (libc.so.6 + 0x94e44) #1 0x7bc6c7050a30 raise (libc.so.6 + 0x3ca30) #2 0x7bc6c98b945f _ZN6KCrash19defaultCrashHandlerEi (libKF6Crash.so.6 + 0x645f) #3 0x7bc6c7050ae0 n/a (libc.so.6 + 0x3cae0) #4 0x7bc6c778d30b _ZN7QObject11deleteLaterEv (libQt6Core.so.6 + 0x18d30b) #5 0x7bc6c9dd9cce n/a (libKF6KIOFileWidgets.so.6 + 0xb3cce) #6 0x7bc6c8749817 _ZN7QWidget5eventEP6QEvent (libQt6Widgets.so.6 + 0x149817) #7 0x7bc6c86fc44d _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0xfc44d) #8 0x7bc6c87017d3 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0x1017d3) #9 0x7bc6c773fe18 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x13fe18) #10 0x7bc6c8760fb4 n/a (libQt6Widgets.so.6 + 0x160fb4) #11 0x7bc6c86fc44d _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0xfc44d) #12 0x7bc6c773fe18 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x13fe18) #13 0x7bc6c7d7eb64 _ZN22QGuiApplicationPrivate11processDragEP7QWindowPK9QMimeDataRK6QPoint6QFlagsIN2Qt10DropActionEES8_INS9_11MouseButtonEES8_INS9_16KeyboardModifierEE (libQt6Gui.so.6 + 0x17eb64) #14 0x7bc6c7de6f72 _ZN22QWindowSystemInterface10handleDragEP7QWindowPK9QMimeDataRK6QPoint6QFlagsIN2Qt10DropActionEES8_INS9_11MouseButtonEES8_INS9_16KeyboardModifierEE (libQt6Gui.so.6 + 0x1e6f72) #15 0x7bc6c52552e6 n/a (libQt6WaylandClient.so.6 + 0xaf2e6) #16 0x7bc6c4597596 n/a (libffi.so.8 + 0x7596) #17 0x7bc6c459400e n/a (libffi.so.8 + 0x400e) #18 0x7bc6c4596bd3 ffi_call (libffi.so.8 + 0x6bd3) #19 0x7bc6c66a0645 n/a (libwayland-client.so.0 + 0x7645) #20 0x7bc6c66a0e73 n/a (libwayland-client.so.0 + 0x7e73) #21 0x7bc6c66a113c wl_display_dispatch_queue_pending (libwayland-client.so.0 + 0x813c) #22 0x7bc6c520ab5e n/a (libQt6WaylandClient.so.6 + 0x64b5e) #23 0x7bc6c778c147 _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x18c147) #24 0x7bc6c86fc44d _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0xfc44d) #25 0x7bc6c773fe18 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x13fe18) #26 0x7bc6c77401d2 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt6Core.so.6 + 0x1401d2) #27 0x7bc6c79959ac n/a (libQt6Core.so.6 + 0x3959ac) #28 0x7bc6c5e18a89 n/a (libglib-2.0.so.0 + 0x5ca89) #29 0x7bc6c5e7a9b7 n/a (libglib-2.0.so.0 + 0xbe9b7) #30 0x7bc6c5e17f95 g_main_context_iteration (libglib-2.0.so.0 + 0x5bf95) #31 0x7bc6c7993389 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x393389) #32 0x7bc6c7748350 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x148350) #33 0x7bc6c810a59b _ZN10QBasicDrag4dragEP5QDrag (libQt6Gui.so.6 + 0x50a59b) #34 0x7bc6c810af89 _ZN12QDragManager4dragEP5QDrag (libQt6Gui.so.6 + 0x50af89) #35 0x7bc6c810b2cf _ZN5QDrag4execE6QFlagsIN2Qt10DropActionEES2_ (libQt6Gui.so.6 + 0x50b2cf) #36 0x7bc6c9ee5a63 _ZN19KItemListController13startDraggingEv (libdolphinprivate.so.6 + 0xafa63) #37 0x7bc6c9ede0ec _ZN19KItemListController14mouseMoveEventEP24QGraphicsSceneMouseEventRK10QTransform (libdolphinprivate.so.6 + 0xa80ec
[kwin] [Bug 483137] Screencast plugin fails if PipeWire is started after KWin
https://bugs.kde.org/show_bug.cgi?id=483137 Andy changed: What|Removed |Added CC||tux.ris...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487269] Dragging files or folders to the location bar reliably crashes Dolphin
https://bugs.kde.org/show_bug.cgi?id=487269 Brian M changed: What|Removed |Added CC||squashyna...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 477292] Request - Create Flatpak of Spectacle, also put on FlatHub
https://bugs.kde.org/show_bug.cgi?id=477292 --- Comment #3 from Noah Davis --- There is some work toward re-adding flatpak nightly builds for spectacle: https://invent.kde.org/graphics/spectacle/-/merge_requests/314 Unfortunately, the flatpak version can't actually take screenshots. If someone with flatpak expertise could help make the flatpak built from the linked MR usable, that would be helpful. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 487297] The "spectacle" program crashes when the time zone is set incorrectly
https://bugs.kde.org/show_bug.cgi?id=487297 Noah Davis changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |BACKTRACE --- Comment #1 from Noah Davis --- Can you please attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl? I'm wondering if the issue comes from spectacle itself or a library we use. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 487268] Less contrast when using balanced or power saving mode on AMD integrated GPU
https://bugs.kde.org/show_bug.cgi?id=487268 Bacteria changed: What|Removed |Added Summary|Less contrast when using|Less contrast when using |power saving mode |balanced or power saving ||mode on AMD integrated GPU -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 487268] Less contrast when using power saving mode
https://bugs.kde.org/show_bug.cgi?id=487268 --- Comment #2 from Bacteria --- Just to clarify my display is also not HDR. I have another laptop with an AMD iGPU renoir. It does not support amd_pstate and that's why it has no power profiles. The issue is also not reproducible. So it seems power profiles is messing up with the color profiles? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 486310] Add Clip or Folder dialog window too small
https://bugs.kde.org/show_bug.cgi?id=486310 --- Comment #5 from Jean-Baptiste Mardelle --- Git commit 6c65851d52202189f210e43f52b1c3390d935721 by Jean-Baptiste Mardelle. Committed on 21/05/2024 at 05:07. Pushed by mardelle into branch 'master'. Fix effect name focus in save effect M +1-0src/effects/effectstack/view/collapsibleeffectview.cpp https://invent.kde.org/multimedia/kdenlive/-/commit/6c65851d52202189f210e43f52b1c3390d935721 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483801] Night Color wrong temperature when HDR is enabled
https://bugs.kde.org/show_bug.cgi?id=483801 Zamundaaa changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/kwin/-/commit/9fef6380d4 |ma/kwin/-/commit/1c7d007165 |d4de7d20408861db8708505bec8 |e81b52bcd0b0c9fae3a68053cc0 |de0 |eb8 --- Comment #3 from Zamundaaa --- Git commit 1c7d007165e81b52bcd0b0c9fae3a68053cc0eb8 by Xaver Hugl. Committed on 21/05/2024 at 04:09. Pushed by zamundaaa into branch 'Plasma/6.0'. backends/drm: adapt the color factors to the target colorspace Otherwise the effect of night color is much bigger in larger colorspaces. This is mostly a workaround, but the better solution (adapting the color temperature of the colorspace instead) will have to wait for 6.1 FIXED-IN: 6.0.5 (cherry picked from commit 9fef6380d4d4de7d20408861db8708505bec8de0) M +7-4src/backends/drm/drm_egl_layer_surface.cpp M +1-0src/backends/drm/drm_egl_layer_surface.h https://invent.kde.org/plasma/kwin/-/commit/1c7d007165e81b52bcd0b0c9fae3a68053cc0eb8 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 485943] Overlapping back button.
https://bugs.kde.org/show_bug.cgi?id=485943 Justin Zobel changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #4 from Justin Zobel --- I just tested on my PC and it seems it might be fixed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485851] if a window is under another window but part of the window of the window below is visible clicking on it does not return to the front
https://bugs.kde.org/show_bug.cgi?id=485851 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #7 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 487248] Colorspace error
https://bugs.kde.org/show_bug.cgi?id=487248 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 485869] Cannot highlight/select (with click+drag) text in "send a message" box
https://bugs.kde.org/show_bug.cgi?id=485869 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 486544] [wish] defining an hour for updating
https://bugs.kde.org/show_bug.cgi?id=486544 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480885] High CPU usage for window under cursor \ plasma shell (if over desktop) and kwin_wayland when moving mouse cursor
https://bugs.kde.org/show_bug.cgi?id=480885 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #14 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 468375] Add option to automatically show annotation tools after taking a screenshot in the main window
https://bugs.kde.org/show_bug.cgi?id=468375 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Arianna] [Bug 468513] Arianna crash when added some books
https://bugs.kde.org/show_bug.cgi?id=468513 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486570] app launcher didn't start on external monitor
https://bugs.kde.org/show_bug.cgi?id=486570 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454775] No open animation with google-chrome in CSD mode
https://bugs.kde.org/show_bug.cgi?id=454775 --- Comment #13 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.
[ark] [Bug 484404] Fails to find plugin for 7z files
https://bugs.kde.org/show_bug.cgi?id=484404 Alastor Tenebris changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #4 from Alastor Tenebris --- Forgot I reported this. Yeah, it works fine now. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 479250] Brief screen freeze when opening Thumbnail Grid tabbox
https://bugs.kde.org/show_bug.cgi?id=479250 adam.br...@fenixhaven.com changed: What|Removed |Added CC||adam.br...@fenixhaven.com --- Comment #12 from adam.br...@fenixhaven.com --- This bug is plaguing me as well on my amd desktop (both cpu and gpu). Since I have a spare computer, I used gdb when this happened, here's the slow backtrace: #0 0x70d995a46b4d in clock_gettime () #1 0x70d9922f2e2d in __GI___clock_gettime (clock_id=, tp=) at ../sysdeps/unix/sysv/linux/clock_gettime.c:42 #2 0x70d9924d2dd8 in std::chrono::_V2::steady_clock::now () at /usr/src/debug/gcc/gcc/libstdc++-v3/src/c++11/chrono.cc:87 #3 0x70d99294b456 in QElapsedTimer::durationElapsed (this=0x70d99574bc10 ) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qelapsedtimer.cpp:278 #4 QElapsedTimer::elapsed (this=this@entry=0x70d99574bc10 ) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qelapsedtimer.cpp:312 #5 0x70d9951c1698 in KWin::AnimationEffect::clock () at /usr/src/debug/kwin/kwin-6.0.4.1/src/effect/animationeffect.h:347 #6 KWin::AnimationEffect::updateLayerRepaints (this=this@entry=0x55ad5de0d9c0) at /usr/src/debug/kwin/kwin-6.0.4.1/src/effect/animationeffect.cpp:858 #7 0x70d9951c22eb in KWin::AnimationEffect::triggerRepaint (this=0x55ad5de0d9c0) at /usr/src/debug/kwin/kwin-6.0.4.1/src/effect/animationeffect.cpp:815 #8 0x70d9951c5bfb in KWin::AnimationEffect::p_animate (this=this@entry=0x55ad5de0d9c0, w=w@entry=0x55ad5e889a00, a=a@entry=KWin::AnimationEffect::Opacity, meta=, meta@entry=0, ms=150, to=..., curve=..., delay=0, from=..., keepAtTarget=true, fullScreenEffect=false, keepAlive=false, shader=0x0) at /usr/src/debug/kwin/kwin-6.0.4.1/src/effect/animationeffect.cp p:283 #9 0x55ad31836079 in KWin::AnimationEffect::set (to=, from=, a=KWin::AnimationEffect::Opacity, meta=0, delay=0, fullScreen=false, keepAlive=false, shader=0x0, curve=..., ms=, w=0x55ad5e889a00, this=0x 55ad5de0d9c0) at /usr/src/debug/kwin/kwin-6.0.4.1/src/effect/animationeffect.h:411 #10 KWin::HighlightWindowEffect::startGhostAnimation (this=this@entry=0x55ad5de0d9c0, window=, window@entry=0x55ad5e889a00) at /usr/src/debug/kwin/kwin-6.0.4.1/src/plugins/highlightwindo w/highlightwindow.cpp:219 #11 0x55ad31836265 in KWin::HighlightWindowEffect::prepareHighlighting (this=this@entry=0x55ad5de0d9c0) at /usr/src/debug/kwin/kwin-6.0.4.1/src/plugins/highlightwindow/highlightwindow.cpp:170 #12 0x55ad31839c3a in KWin::HighlightWindowEffect::highlightWindows (this=this@entry=0x55ad5de0d9c0, windows=...) at /usr/src/debug/kwin/kwin-6.0.4.1/src/plugins/highlightwindow/highlightwindow.cpp :209 #13 0x55ad31839f13 in KWin::HighlightWindowEffect::highlightWindows (windows=..., this=0x55ad5de0d9c0) at /usr/src/debug/kwin/kwin-6.0.4.1/src/plugins/highlightwindow/highlightwindow.cpp:198 #14 KWin::HighlightWindowEffect::perform (feature=, arguments=, this=0x55ad5de0d9c0) at /usr/src/debug/kwin/kwin-6.0.4.1/src/plugins/highlightwindow/highlightwindow.cpp:27 3 #15 KWin::HighlightWindowEffect::perform (this=0x55ad5de0d9c0, feature=, arguments=) at /usr/src/debug/kwin/kwin-6.0.4.1/src/plugins/highlightwindow/highlightwindow.cpp:26 5 #16 0x70d9951d758e in KWin::EffectsHandler::highlightWindows (this=, windows=) at /usr/src/debug/kwin/kwin-6.0.4.1/src/effect/effecthandler.cpp:1418 #17 0x70d9954ef4fc in KWin::TabBox::TabBoxHandlerImpl::highlightWindows (this=, window=, controller=0x55ad5e695a10) at /usr/src/debug/kwin/kwin-6.0.4.1/src/tabbox/tabb ox.cpp:274 #18 0x70d9929a1e3e in QtPrivate::QSlotObjectBase::call (this=, r=0x55ad5d1fa280, a=0x7ffe2bac8d98, this=, r=, a=) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobjectdefs_impl.h:469 #19 doActivate (sender=, signal_index=, argv=) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobject.cpp:4078 #20 0x70d9928d34d4 in QSingleShotTimer::timeout (this=0x55ad5de29e10) at /usr/src/debug/qt6-base/build/src/corelib/Core_autogen/7GB2EGQPHR/moc_qsingleshottimer_p.cpp:139 #21 QSingleShotTimer::timerEvent (this=0x55ad5de29e10) at /usr/src/debug/qt6-base/build/src/corelib/Core_autogen/7GB2EGQPHR/../../../../../qtbase/src/corelib/kernel/qsingleshottimer_p.h:116 #22 0x70d99298c809 in QObject::event (this=0x55ad5de29e10, e=0x7ffe2bac8f70) at /usr/src/debug/qt6-base/qtbase/src/corelib/kernel/qobject.cpp:1423 #23 0x70d993afc4dc in QApplicationPrivate::notify_helper (this=, receiver=0x55ad5de29e10, e=0x7ffe2bac8f70) at /usr/src/debug/qt6-base/qtbase/src/widgets/kernel/qapplication.cpp:3287 #24 0x70d992945678 in QCoreApplication::noti
[krita] [Bug 487248] Colorspace error
https://bugs.kde.org/show_bug.cgi?id=487248 --- Comment #2 from tim.ar...@gmail.com --- Hi - thanks! It appears to only happen when I'm selecting adjustment filter layers or filter masks, it did persist despite closing and reopening the app. I updated to 5.2.2 and the error has now gone away. sRGB-elle-V2-srgbtrc.icc - I haven't changed the colrspace during the project. Didn't do anythign special to this file - I hadn't tried it in other files. Im happy that 5.2.2 seems to have fixed it I'm happy to send you the flie, how'd you like me to do that. Thanks for all that you do -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 485029] Upgrade YOLO to a more recent version to improve face recognition
https://bugs.kde.org/show_bug.cgi?id=485029 Craig changed: What|Removed |Added CC||craigfryer...@gmail.com --- Comment #2 from Craig --- (In reply to Antonio Petricca from comment #0) > This is my scenario: I have a daughter which grew up during the years, and > for that reason the recognize engine often fails. > > Is it possible to replace the YOLO engine from the v3 to a more recent one > like the v8.1? > > Thank you so much! My understanding is that YOLO is only the face or object detection. The face recognition is done by another module. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487306] Nested kwin_wayland was unresponsive in VMs using the virgl driver with an XWayland crash
https://bugs.kde.org/show_bug.cgi?id=487306 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480925] Crash in KeyboardInterface::sendKey
https://bugs.kde.org/show_bug.cgi?id=480925 Ryan Rix changed: What|Removed |Added CC||r...@n.rix.si --- Comment #7 from Ryan Rix --- I've been experiencing this crash for a while as well on an AMD running NixOS resulting in the same backtrace which BK lists in the journalctl output: Thread 1 (Thread 0x7fa17dac1380 (LWP 147914)): #0 0x7fa185601d60 in KWaylandServer::ClientConnection::client() const () from /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/lib/libkwin.so.5 #1 0x7fa185614b24 in KWaylandServer::KeyboardInterfacePrivate::keyboardsForClient(KWaylandServer::ClientConnection*) const () from /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/lib/libkwin.so.5 #2 0x7fa185614f79 in KWaylandServer::KeyboardInterface::sendKey(unsigned int, KWaylandServer::KeyboardKeyState, KWaylandServer::ClientConnection*) () from /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/lib/libkwin.so.5 #3 0x7fa185407401 in KWin::KeyboardInputRedirection::processKey(unsigned int, KWin::InputRedirection::KeyboardKeyState, std::chrono::duration >, KWin::InputDevice*) () from /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/lib/libkwin.so.5 #4 0x7fa183973c35 in void doActivate(QObject*, int, void**) () from /nix/store/h8jsqbn5bpci7v8gaxy7hrp2xc0s804v-qtbase-5.15.12/lib/libQt5Core.so.5 #5 0x7fa185322bfc in KWin::InputDevice::keyChanged(unsigned int, KWin::InputRedirection::KeyboardKeyState, std::chrono::duration >, KWin::InputDevice*) () from /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/lib/libkwin.so.5 #6 0x7fa1855c3405 in KWin::LibInput::Connection::processEvents() () from /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/lib/libkwin.so.5 #7 0x7fa1839684c0 in QObject::event(QEvent*) () from /nix/store/h8jsqbn5bpci7v8gaxy7hrp2xc0s804v-qtbase-5.15.12/lib/libQt5Core.so.5 #8 0x7fa18273e04e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /nix/store/h8jsqbn5bpci7v8gaxy7hrp2xc0s804v-qtbase-5.15.12/lib/libQt5Widgets.so.5 #9 0x7fa18393c978 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /nix/store/h8jsqbn5bpci7v8gaxy7hrp2xc0s804v-qtbase-5.15.12/lib/libQt5Core.so.5 #10 0x7fa18393f9b1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /nix/store/h8jsqbn5bpci7v8gaxy7hrp2xc0s804v-qtbase-5.15.12/lib/libQt5Core.so.5 #11 0x7fa183991ae0 in QEventDispatcherUNIX::processEvents(QFlags) () from /nix/store/h8jsqbn5bpci7v8gaxy7hrp2xc0s804v-qtbase-5.15.12/lib/libQt5Core.so.5 #12 0x0056a96d in QUnixEventDispatcherQPA::processEvents(QFlags) () #13 0x7fa18393b373 in QEventLoop::exec(QFlags) () from /nix/store/h8jsqbn5bpci7v8gaxy7hrp2xc0s804v-qtbase-5.15.12/lib/libQt5Core.so.5 #14 0x7fa183943876 in QCoreApplication::exec() () from /nix/store/h8jsqbn5bpci7v8gaxy7hrp2xc0s804v-qtbase-5.15.12/lib/libQt5Core.so.5 #15 0x0044e897 in main () I use the Bismuth tiling plugin but otherwise have a straightforward plasma configuration. it mostly happens when I am hitting an Emacs keybinding with a Ctrl modifier, but sometimes happens at random. Operating System: NixOS 23.11 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.12 Kernel Version: 6.1.90 (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 7640U w/ Radeon 760M Graphics Memory: 60.7 GiB of RAM Graphics Processor: AMD Radeon Graphics -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 487303] plasma-brower-integration causes Cloudflare to lock out humans
https://bugs.kde.org/show_bug.cgi?id=487303 Dominik Kummer changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Dominik Kummer --- I can confirm now that the Chromium Plasma Integration Extension causes Cloudflare to classify me as non-human. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487306] New: Nested kwin_wayland was unresponsive in VMs using the virgl driver with an XWayland crash
https://bugs.kde.org/show_bug.cgi?id=487306
Bug ID: 487306
Summary: Nested kwin_wayland was unresponsive in VMs using the
virgl driver with an XWayland crash
Classification: Plasma
Product: kwin
Version: 6.0.4
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: matt.fagn...@bell.net
Target Milestone: ---
SUMMARY
I booted the Fedora Rawhide/41 KDE Plasma live image
Fedora-KDE-Live-x86_64-Rawhide-20240518.n.0.iso in a QEMU/KVM VM using GNOME
Boxes with 3D acceleration enabled using the virgl driver from mesa 24.1.0-rc4.
Plasma 6.0.4 on Wayland started. I started Konsole. I tried to run a nested
kwin_wayland session using the instructions at
https://community.kde.org/KWin/Wayland
export $(dbus-launch)
kwin_wayland --xwayland
The nested kwin_wayland window appeared but was unresponsive. The kwin_wayland
output in Konsole showed a crash in XWayland.
kwin_wayland --xwayland
No backend specified, automatically choosing Wayland because WAYLAND_DISPLAY is
set
unable to lock lockfile /run/user/1000/wayland-0.lock, maybe another compositor
is running
Accepting client connections on sockets: QList("wayland-1")
OpenGL vendor string: Mesa
OpenGL renderer string: virgl (AMD Radeon R5 Graphics
(radeonsi, carrizo, LLVM 18.1...)
OpenGL version string: 4.3 (Core Profile) Mesa 24.1.0-rc4
OpenGL shading language version string: 4.30
Driver: Unknown
GPU class: Unknown
OpenGL version: 4.3
GLSL version: 4.30
Mesa version: 24.1
Requires strict binding:no
Virtual Machine:no
Timer query support:yes
linux_dmabuf_feedback.main_device: Failed to fetch DRM device
linux_dmabuf_feedback.tranche_target_device: Failed to fetch DRM device
linux_dmabuf_feedback.tranche_target_device: Failed to fetch DRM device
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/Xwayland (0x557c2ad2d000+0x1660c2) [0x557c2ae930c2]
(EE) 1: /usr/bin/Xwayland (0x557c2ad2d000+0x1661c5) [0x557c2ae931c5]
(EE) 2: /lib64/libc.so.6 (0x7f55eb00c000+0x40750) [0x7f55eb04c750]
(EE) 3: /usr/bin/Xwayland (0x557c2ad2d000+0x41075) [0x557c2ad6e075]
(EE) 4: /usr/bin/Xwayland (0x557c2ad2d000+0x3466f) [0x557c2ad6166f]
(EE) 5: /usr/bin/Xwayland (0x557c2ad2d000+0x1fa76) [0x557c2ad4ca76]
(EE) 6: /lib64/libc.so.6 (0x7f55eb00c000+0x2a1c8) [0x7f55eb0361c8]
(EE) 7: /lib64/libc.so.6 (__libc_start_main+0x8b) [0x7f55eb03628b]
(EE) 8: /usr/bin/Xwayland (0x557c2ad2d000+0x224c5) [0x557c2ad4f4c5]
(EE)
(EE) Segmentation fault at address 0x8
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)
The Xwayland crash was in xwl_glamor_gbm_init_main_dev in frame 10 from
xorg-x11-server-Xwayland-24.1.0-1.fc41. The crashing line in
xwl_glamor_gbm_init_main_dev had a null pointer main_dev so
main_dev->available_nodes looked like a null pointer dereference.
Core was generated by `/usr/bin/Xwayland :1 -listenfd 61 -listenfd 62
-displayfd 52 -rootless -wm 56'.
Program terminated with signal SIGABRT, Aborted.
#0 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
Downloading source file
/usr/src/debug/glibc-2.39.9000-18.fc41.x86_64/nptl/pthread_kill.c
44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO
(ret) : 0;
(gdb) bt
#0 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#1 0x7f55eb0a41f3 in __pthread_kill_internal (threadid=,
signo=6) at pthread_kill.c:78
#2 0x7f55eb04c69e in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#3 0x7f55eb034942 in __GI_abort () at abort.c:79
#4 0x557c2ae9c86a in OsAbort () at ../os/utils.c:1283
#5 0x557c2ae9caee in AbortServer () at ../os/log.c:892
#6 FatalError (f=) at ../os/log.c:1030
#7 0x557c2ae93222 in OsSigHandler (unused=, signo=11,
sip=) at ../os/osinit.c:156
#8 OsSigHandler (signo=11, sip=, unused=) at
../os/osinit.c:110
#9
#10 xwl_glamor_gbm_init_main_dev (xwl_screen=) at
../hw/xwayland/xwayland-glamor-gbm.c:1517
#11 xwl_glamor_gbm_init_egl (xwl_screen=) at
../hw/xwayland/xwayland-glamor-gbm.c:1552
#12 xwl_glamor_init (xwl_screen=0x557c42ab86d0) at
../hw/xwayland/xwayland-glamor.c:232
#13 0x557c2ad6166f in xwl_screen_init (pScreen=0x557c42ab8040,
argc=, argv=) at
../hw/xwayland/xwayland-screen.c:1109
#14 0x557c2ad4ca76 in AddScreen (pfnInit=, argc=, argv=) at ../dix/dispatch.c:3993
#15 InitOutput (screen_info=, argc=,
argv=) at ../hw/xwayland/xwayland.c:455
#16 dix_main (argc=, argv=, envp=)
at ../dix/main.c:193
#17 main (argc=, argv=, envp=) at
../dix
[kde] [Bug 487305] I don't know what exactly led to it, but all my tools stopped responding the second i grouped a bunch of sketches together. Nothing is responding.
https://bugs.kde.org/show_bug.cgi?id=487305 --- Comment #1 from Syed Galib --- Created attachment 169671 --> https://bugs.kde.org/attachment.cgi?id=169671&action=edit A Krita file where the bug occurred this file is the document where bugs occurred and I couldn't draw on it anymore. Maybe if you try the file you'll see what I mean. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 486814] Lines ending with emoji are copied to clipboard without newline character
https://bugs.kde.org/show_bug.cgi?id=486814 ninj...@gmail.com changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||ninj...@gmail.com --- Comment #1 from ninj...@gmail.com --- *** This bug has been marked as a duplicate of bug 473500 *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 473500] Copy paste loses line break
https://bugs.kde.org/show_bug.cgi?id=473500 ninj...@gmail.com changed: What|Removed |Added CC||mariusz.atamanczuk.tlen@gma ||il.com --- Comment #3 from ninj...@gmail.com --- *** Bug 486814 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 487305] New: I don't know what exactly led to it, but all my tools stopped responding the second i grouped a bunch of sketches together. Nothing is responding.
https://bugs.kde.org/show_bug.cgi?id=487305 Bug ID: 487305 Summary: I don't know what exactly led to it, but all my tools stopped responding the second i grouped a bunch of sketches together. Nothing is responding. Classification: I don't know Product: kde Version: unspecified Platform: Microsoft Windows OS: Other Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: galibs...@gmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE (a guess) 1. a bunch of pencil sketches are made 2. group them together 3. work a sketch on the group layer name. 4. problem created OBSERVED RESULT tools stop responding and do not give an input onto the canvas. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION Krita usage log: SESSION: 18 May 2024 00:56:54 -0400. Executing C:\Program Files\Krita (x64)\bin\krita.exe Krita Version: 5.2.2, Qt version compiled: 5.15.7, loaded: 5.15.7. Process ID: 11200 -- -- -- -- -- -- -- -- 18 May 2024 00:56:54 -0400: Style: fusion. Available styles: windowsvista, Windows, Fusion 18 May 2024 00:56:58 -0400: Creating database from scratch (database didn't exist, new schema version: 0.0.17). 18 May 2024 00:57:11 -0400: Non-store package - creating updater 18 May 2024 00:57:45 -0400: Created image "Unnamed", 1920 * 1080 pixels, 300 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 2 18 May 2024 01:04:45 -0400: Autosaving: C:/Users/syedm/AppData/Local/Temp/krita-11200-document_0-autosave.kra 18 May 2024 01:04:45 -0400: Converting from application/x-krita to application/x-krita. Location: C:/Users/syedm/AppData/Local/Temp/krita-11200-document_0-autosave.kra. Real location: C:/Users/syedm/AppData/Local/Temp/krita-11200-document_0-autosave.kra. Batchmode: 0. Configuration: none 18 May 2024 01:04:45 -0400: Completed saving C:/Users/syedm/AppData/Local/Temp/krita-11200-document_0-autosave.kra (mime: application/x-krita). Result: OK. Warning: . Size: 142868 18 May 2024 01:20:58 -0400: Removing autosave file: C:/Users/syedm/AppData/Local/Temp/krita-11200-document_0-autosave.kra 18 May 2024 01:20:58 -0400: CLOSING SESSION SESSION: 18 May 2024 16:17:05 -0400. Executing C:\Program Files\Krita (x64)\bin\krita.exe Krita Version: 5.2.2, Qt version compiled: 5.15.7, loaded: 5.15.7. Process ID: 14164 -- -- -- -- -- -- -- -- 18 May 2024 16:17:05 -0400: Style: fusion. Available styles: windowsvista, Windows, Fusion 18 May 2024 16:17:10 -0400: Database is up to date. Version: 0.0.17, created by Krita 5.2.2, at Sat May 18 00:56:58 2024 18 May 2024 16:17:10 -0400: Non-store package - creating updater 18 May 2024 16:17:33 -0400: Created image "Unnamed", 1920 * 1080 pixels, 300 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 2 18 May 2024 16:31:33 -0400: Autosaving: C:/Users/syedm/AppData/Local/Temp/krita-14164-document_0-autosave.kra 18 May 2024 16:31:33 -0400: Converting from application/x-krita to application/x-krita. Location: C:/Users/syedm/AppData/Local/Temp/krita-14164-document_0-autosave.kra. Real location: C:/Users/syedm/AppData/Local/Temp/krita-14164-document_0-autosave.kra. Batchmode: 0. Configuration: none 18 May 2024 16:31:33 -0400: Completed saving C:/Users/syedm/AppData/Local/Temp/krita-14164-document_0-autosave.kra (mime: application/x-krita). Result: OK. Warning: . Size: 121581 18 May 2024 18:31:10 -0400: Removing autosave file: C:/Users/syedm/AppData/Local/Temp/krita-14164-document_0-autosave.kra 18 May 2024 18:31:11 -0400: CLOSING SESSION SESSION: 19 May 2024 18:00:56 -0400. Executing C:\Program Files\Krita (x64)\bin\krita.exe Krita Version: 5.2.2, Qt version compiled: 5.15.7, loaded: 5.15.7. Process ID: 2232 -- -- -- -- -- -- -- -- 19 May 2024 18:00:56 -0400: Style: fusion. Available styles: windowsvista, Windows, Fusion 19 May 2024 18:01:01 -0400: Database is up to date. Version: 0.0.17, created by Krita 5.2.2, at Sat May 18 00:56:58 2024 19 May 2024 18:01:01 -0400: Non-store package - creating updater 19 May 2024 18:03:55 -0400: Created image "Unnamed", 1920 * 1080 pixels, 300 dpi. Color model: 8-bit integer/channel RGB/Alpha (sRGB-elle-V2-srgbtrc.icc). Layers: 2 19 May 2024 18:24:55 -0400: Autosaving: C:/Users/syedm/AppData/Local/Temp/krita-2232-document_0-
[systemsettings] [Bug 487304] New: Allow disabling Night color for certain applications or windows
https://bugs.kde.org/show_bug.cgi?id=487304 Bug ID: 487304 Summary: Allow disabling Night color for certain applications or windows Classification: Applications Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_nightcolor Assignee: plasma-b...@kde.org Reporter: tomash...@gmail.com CC: kwin-bugs-n...@kde.org Target Milestone: --- It might make sense for users to disable Night color for games or videos, especially in fullscreen, when the intended color might often be desired by the user. As of now, one needs turn it off (and then on) manually or write scripts per app to do that (like this for MPV for example: https://gist.github.com/Zharkan/5f65ff9b1da85b2a2c79b777ed9e6199). It would be great if it were possible to configure KDE to do this automatically. One would need a way to select applications and/or a checkbox to disable the feature for fullscreen windows. This was also discussed here: https://discuss.kde.org/t/make-exceptions-for-night-color-in-some-apps/2392 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487298] Edit mode broken in RTL
https://bugs.kde.org/show_bug.cgi?id=487298 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 487303] New: plasma-brower-integration causes Cloudflare to lock out humans
https://bugs.kde.org/show_bug.cgi?id=487303 Bug ID: 487303 Summary: plasma-brower-integration causes Cloudflare to lock out humans Classification: Plasma Product: plasma-browser-integration Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Chrome Assignee: k...@privat.broulik.de Reporter: ad...@arkades.org Target Milestone: --- Actually Cloudflare (as gitlab sentinel) classifies me as a robot with Falkon (QtWebengine) but during research I stumbled over this discussion: https://gitlab.com/gitlab-org/gitlab/-/issues/421396#note_1912051035 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 487302] New: Compose key does not work on Xorg anymore since Plasma 6
https://bugs.kde.org/show_bug.cgi?id=487302
Bug ID: 487302
Summary: Compose key does not work on Xorg anymore since Plasma
6
Classification: I don't know
Product: kde
Version: unspecified
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: unassigned-b...@kde.org
Reporter: cdauth+bugs.kde@cdauth.eu
Target Milestone: ---
I'm not sure where to start investigating this.
I'm using Plasma Desktop on Arch Linux with Xorg. I have Caps Lock configured
as my compose key.
Since upgrading to Plasma Desktop 6, the compose key does not work in KDE
applications anymore, for example in dolphin, konsole, krunner, kwrite. The
compose key still works in chromium, firefox, gnucash, signal-desktop, element,
vscode. Interestingly, it also seems to have stopped working in lowriter, steam
and qgit.
In the apps where it doesn't work anymore, pressing the compose key will simply
have no effect. It will not enable caps lock and the following letters will
just be typed as normal.
This is the output of setxkbmap -print -query:
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat{ include "complete" };
xkb_symbols { include
"pc+us+de:2+cz(qwerty):3+es:4+inet(evdev)+compose(caps)"};
xkb_geometry { include "pc(pc105)" };
};
rules: evdev
model: pc105
layout: us,de,cz,es
variant:,,qwerty,
options:compose:caps
SOFTWARE/OS VERSIONS
Linux: Arch Linux
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 487300] sharing minimized (non-rendering?) window results in random parts of screen being casted
https://bugs.kde.org/show_bug.cgi?id=487300 Martin Bednar changed: What|Removed |Added CC||martin+...@serafean.cz -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 481691] Debugger plugin (GDB) ignores breakpoints
https://bugs.kde.org/show_bug.cgi?id=481691 le...@yahoo.it changed: What|Removed |Added CC||le...@yahoo.it --- Comment #1 from le...@yahoo.it --- It happens the same on my computer Operating System: Arch Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485152] Feature Request: Allow Editing Default KWin Custom Tiling Shortcut
https://bugs.kde.org/show_bug.cgi?id=485152 micheleoro.nob...@gmail.com changed: What|Removed |Added CC||micheleoro.nob...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 485034] Feature requests for Custom Tiling
https://bugs.kde.org/show_bug.cgi?id=485034 micheleoro.nob...@gmail.com changed: What|Removed |Added CC||micheleoro.nob...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 487301] New: RUNNING status not included in XML output for forked children
https://bugs.kde.org/show_bug.cgi?id=487301 Bug ID: 487301 Summary: RUNNING status not included in XML output for forked children Classification: Developer tools Product: valgrind Version: 3.24 GIT Platform: Other OS: Other Status: REPORTED Severity: minor Priority: NOR Component: memcheck Assignee: jsew...@acm.org Reporter: imb2...@columbia.edu Target Milestone: --- Created attachment 169670 --> https://bugs.kde.org/attachment.cgi?id=169670&action=edit Append running status to child's XML file along with preamble SUMMARY When outputting XML of child processes to different destinations (e.g., using --xml-file=%p.xml), children do not get a RUNNING status (appending the RUNNING status is handled elsewhere in the code than the rest of the preamble). STEPS TO REPRODUCE Write and compile a program (test.c) that forks, and run it with Memcheck, outputting info to separate XML files: valgrind --leak-check=yes --xml=yes --xml-file=test-%p.xml ./test OBSERVED RESULT Child's XML output contains a FINISHED status but not a RUNNING status. EXPECTED RESULT Running status appended to child's XML output after fork. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 486802] Loosing pairing after some time. kdeconnectd cpu load 100%
https://bugs.kde.org/show_bug.cgi?id=486802 Schlaefer changed: What|Removed |Added CC||openmail+...@siezi.com --- Comment #1 from Schlaefer --- Created attachment 169669 --> https://bugs.kde.org/attachment.cgi?id=169669&action=edit kdeconnectd at 100% CPU and no devices showing up I experience that too - maybe twice a month. Suddenly kdeconnectd sits at 100% CPU on one core and the app says no connected devices. Killing the kdeconnectd process fixes the CPU usage and all connected devices show up again in the app. Operating System: CachyOS Linux KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.9.1-2-cachyos-echo-lto (64-bit) Graphics Platform: Wayland Processors: 12 × 11th Gen Intel® Core™ i5-11400 @ 2.60GHz Memory: 31,2 GiB of RAM Graphics Processor: Mesa Intel® Arc -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487300] New: sharing minimized (non-rendering?) window results in random parts of screen being casted
https://bugs.kde.org/show_bug.cgi?id=487300 Bug ID: 487300 Summary: sharing minimized (non-rendering?) window results in random parts of screen being casted Classification: Plasma Product: kwin Version: 6.0.4 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: screencasting Assignee: kwin-bugs-n...@kde.org Reporter: martin+...@serafean.cz Target Milestone: --- Created attachment 169668 --> https://bugs.kde.org/attachment.cgi?id=169668&action=edit showcasing bug. Only terminal window shared, panel & firefox can be discerned SUMMARY Sharing a window, which isn't currently rendering, results in garbled cast video, while possibly sharing parts of other windows. Marking as grave as this can create privacy issues (if the part of the random data contains parts of another window) STEPS TO REPRODUCE 1. Minimize a maximized window, wait a while (unsure how long. Maybe screensaver required to activate...) 2. Share only window using firefox (to https://onlinescreenshare.com ) 3. Pick a window to share. Getting the "Share" button to enable is sometimes a bit finicky, but randomly selecting/deselecting windows usually does the trick. Move cursor over last location of window. ( related bug : https://bugs.kde.org/show_bug.cgi?id=486081 ) OBSERVED RESULT Garbled casted result. Possibly containing fragments of other windows. Raising the shared window fixes it. EXPECTED RESULT Unsure. Either don't allow sharing such a window, or enable the window, possibly raising it? SOFTWARE/OS VERSIONS Linux/KDE Plasma: linux-6.6.30, Gentoo KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.0.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION I have 2 screens. Firefox with cast on left screen, last location of minimized window on right screen: Moving cursor anywhere on right screen causes cast stream corruption. I have reproduced it a few times, twice using the process described, but I don't know how to force the exact conditions which allow reproducing. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 487297] The "spectacle" program crashes when the time zone is set incorrectly
https://bugs.kde.org/show_bug.cgi?id=487297 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487299] New: overview + showDesktop is a confusing UX
https://bugs.kde.org/show_bug.cgi?id=487299 Bug ID: 487299 Summary: overview + showDesktop is a confusing UX Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: effects-overview Assignee: kwin-bugs-n...@kde.org Reporter: k...@davidedmundson.co.uk Target Milestone: --- If show desktop is activated (enter edit mode in plasmashell) hotcorners are still active and overview can be started. If a window is clicked it animates back, but the user is still in show desktop mode so the selected window suddenly disappears. Dismissing show desktop when overview starts is probably the easiest solution -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487298] New: Edit mode broken in RTL
https://bugs.kde.org/show_bug.cgi?id=487298 Bug ID: 487298 Summary: Edit mode broken in RTL Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: k...@davidedmundson.co.uk CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Run plasmashell --reverse start edit mode open widget explorer desktop moves the wrong way -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 484435] Icon in notification area does not match other icons
https://bugs.kde.org/show_bug.cgi?id=484435 --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/pim/kleopatra/-/merge_requests/206 -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 484435] Icon in notification area does not match other icons
https://bugs.kde.org/show_bug.cgi?id=484435 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/pim/kleopatra/-/merge_requests/206 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481113] Changes to pinned apps are not saved when Plasmashell quits
https://bugs.kde.org/show_bug.cgi?id=481113 Andreas Sturmlechner changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #36 from Andreas Sturmlechner --- Reopening, I can confirm not fixed with the patch applied to libplasma-6.0.4. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 485999] kdiff3 segaborts when comparing two files
https://bugs.kde.org/show_bug.cgi?id=485999 Andreas Sturmlechner changed: What|Removed |Added CC||ast...@gentoo.org -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 487297] New: The "spectacle" program crashes when the time zone is set incorrectly
https://bugs.kde.org/show_bug.cgi?id=487297 Bug ID: 487297 Summary: The "spectacle" program crashes when the time zone is set incorrectly Classification: Applications Product: Spectacle Version: 24.04.90 Platform: NixOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: kixonco...@gmail.com CC: k...@david-redondo.de Target Milestone: --- 1. setting the wrong time zone through the nixos config and generating it (in my case, not knowing that there was only one time zone “Asia/Almaty” left, I set it to “Asia/Astana”) 2. an attempt to take a screenshot, of a region, of the entire screen, an attempt to save it or copy it to the clipboard, after which it crashes 3. when run via terminal using the command "spectacle -bcr " the error "Unable to determine system time zone: please check your system configuration. Segmentation fault (core dumped)" it just doesn't work in the wrong time zone, making it difficult to diagnose using topic chats os: nixos unstable chanel, KDE plasma 6.0.5 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 290061] pie elf always loaded at 0x108000
https://bugs.kde.org/show_bug.cgi?id=290061 --- Comment #6 from Paul Floyd --- The patch no longer applies cleanly. Currently there is some special case code for mips64. I've tried to access a suitable machine to check if this is still relevant, but no success so far. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 487296] New: --track-fds=yes and --track-fds=all report erroneous information when fds 0, 1, or 2 are used as non-std
https://bugs.kde.org/show_bug.cgi?id=487296
Bug ID: 487296
Summary: --track-fds=yes and --track-fds=all report erroneous
information when fds 0, 1, or 2 are used as non-std
Classification: Developer tools
Product: valgrind
Version: 3.24 GIT
Platform: Other
OS: Other
Status: REPORTED
Severity: minor
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: imb2...@columbia.edu
Target Milestone: ---
Created attachment 169667
--> https://bugs.kde.org/attachment.cgi?id=169667&action=edit
patch to accurately report leaks for fds 0, 1, 2
SUMMARY
If a program closes any std fd then reopens it as non-std, Memcheck's
--track-fds=yes report is inaccurate. If fds 0, 1, or 2 are in use,
--track-fds=yes and --track-fds=all treat them as std (regardless of whether
they are or not), leading to erroneous output. Leak messages are consequently
omitted with --track-fds=yes.
STEPS TO REPRODUCE
Run a program that closes one of the std fds, and reopens another file in its
place without closing it:
// test.c
#include
#include
#include
int main(void) {
FILE *fp;
assert(fclose(stdout) == 0);
fp = fopen("newfile.txt", "w");
assert(fileno(fp) == STDOUT_FILENO);
return 0;
}
OBSERVED RESULT
$ gcc -g -Wall test.c -o test && valgrind --leak-check=yes --track-fds=yes
./test
==422217== Memcheck, a memory error detector
==422217== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et al.
==422217== Using Valgrind-3.24.0.GIT and LibVEX; rerun with -h for copyright
info
==422217== Command: ./test
==422217==
==422217==
==422217== FILE DESCRIPTORS: 3 open (3 std) at exit.
==422217==
==422217== HEAP SUMMARY:
==422217== in use at exit: 472 bytes in 1 blocks
==422217== total heap usage: 1 allocs, 0 frees, 472 bytes allocated
==422217==
==422217== LEAK SUMMARY:
==422217==definitely lost: 0 bytes in 0 blocks
==422217==indirectly lost: 0 bytes in 0 blocks
==422217== possibly lost: 0 bytes in 0 blocks
==422217==still reachable: 472 bytes in 1 blocks
==422217== suppressed: 0 bytes in 0 blocks
==422217== Reachable blocks (those to which a pointer was found) are not shown.
==422217== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==422217==
==422217== For lists of detected and suppressed errors, rerun with: -s
==422217== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Note that Memcheck reports 3 std fds open at exit, does not report a leak
message, and does not report any errors.
EXPECTED RESULT
Memcheck should report 2 std fds open at exit, a leak message should be
outputted for the newly opened fd, and the error summary should list 1 error.
--
You are receiving this mail because:
You are watching all bug changes.
[Kamera] [Bug 487295] New: Error code 150 when accessing camera (in dolphin)
https://bugs.kde.org/show_bug.cgi?id=487295
Bug ID: 487295
Summary: Error code 150 when accessing camera (in dolphin)
Classification: Applications
Product: Kamera
Version: 24.02.2
Platform: openSUSE
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: General
Assignee: kdelibs-b...@kde.org
Reporter: pas...@orange.fr
Target Milestone: ---
SUMMARY
Error code 150 (in French "E/S en cours" meaning peripheral is busy) happens
when accessing PTP camera (Nikon Coolpix S5100). Then camera does not respond
anymore until it is restarted (even gphoto sees it is busy).
STEPS TO REPRODUCE
1. Connect camera
2. Wait for it to appear in the "Disks & peripherals" (in French "Disques et
périphériques") in the systray
3. Click on "Display pictures in file manager" ("Open in file manager" does
not work for me, see https://bugs.kde.org/show_bug.cgi?id=487293)
4. Navigate in the filesystem or copy files
OBSERVED RESULT
At some point in time, we get error 150 and camera does not respond any more
and camera battery is consumed really fast (less than 1H)
EXPECTED RESULT
No issues as when I use gphotofs (FUSE based filesystem to access PTP cameras).
SOFTWARE/OS VERSIONS
Distribution: openSUSE Tumbleweed 20240517
Linux: 6.8.9-1-default (64-bit)
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.0
gPhoto: 2.5.28
ADDITIONAL INFORMATION
Camera: Nikon Coolpix S5100
NB: I can open the about.txt and summary.txt special files (with Kate).
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 487294] casted cursor moves even when not moved over window
https://bugs.kde.org/show_bug.cgi?id=487294 --- Comment #1 from Martin Bednar --- Update: this happens even when the window is minimized: the casted cursor moves when moved over the last known window position. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487294] casted cursor moves even when not moved over window
https://bugs.kde.org/show_bug.cgi?id=487294 Martin Bednar changed: What|Removed |Added CC||martin+...@serafean.cz -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487294] New: casted cursor moves even when not moved over window
https://bugs.kde.org/show_bug.cgi?id=487294 Bug ID: 487294 Summary: casted cursor moves even when not moved over window Classification: Plasma Product: kwin Version: 6.0.4 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: screencasting Assignee: kwin-bugs-n...@kde.org Reporter: martin+...@serafean.cz Target Milestone: --- Casted cursor moves even when shared window not in focus. STEPS TO REPRODUCE 1. 2 displays (might not be relevant, but makes seeing it easier) 2. Share one window only using firefox (tested to https://onlinescreenshare.com/ ) 3. place another window over shared window OBSERVED RESULT Cursor in casted video moves over shared window, although in reality (ie locally) focus is on another window. EXPECTED RESULT No cursor movement if shared window not in focus SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo 2.15/kernel 6.6.30 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.0.0 Qt Version: 6.7.0 -- You are receiving this mail because: You are watching all bug changes.
[Kamera] [Bug 487293] New: "Open in file manager" does not work
https://bugs.kde.org/show_bug.cgi?id=487293
Bug ID: 487293
Summary: "Open in file manager" does not work
Classification: Applications
Product: Kamera
Version: 24.02.2
Platform: openSUSE
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: General
Assignee: kdelibs-b...@kde.org
Reporter: pas...@orange.fr
Target Milestone: ---
SUMMARY
"Open in file manager" ("Ouvrir dans le gestionnaire de fichiers", in French)
in "Disks & peripherals" (in French "Disques et périphériques") in systray does
not work for PTP camera (Nikon S5100). "Display pictures in file manager" (in
French, "Afficher les photoes dans le gestionnaire de fichiers") works though,
need to unfold camera item.
STEPS TO REPRODUCE
1. Connect camera
2. Wait for it to appear in the "Disks & peripherals" (in French "Disques et
périphériques") in the systray
3. Click on "Open in file manager"
OBSERVED RESULT
It opens home folder.
EXPECTED RESULT
It should open `camera:/`
SOFTWARE/OS VERSIONS
Distribution: openSUSE Tumbleweed 20240517
Linux: 6.8.9-1-default (64-bit)
KDE Plasma Version: 6.0.4
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.0
gPhoto: 2.5.28
ADDITIONAL INFORMATION
Camera: Nikon Coolpix S5100
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 486755] images.album = NULL without reason (disappearing images in DK)
https://bugs.kde.org/show_bug.cgi?id=486755 --- Comment #2 from Maik Qualmann --- Another note: the "sanity check" you want is the initial scan in digiKam, which keeps the entries in the file system in sync with those in the database. Maik -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 486755] images.album = NULL without reason (disappearing images in DK)
https://bugs.kde.org/show_bug.cgi?id=486755 Maik Qualmann changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED Version Fixed In||8.4.0 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 487290] Host KDE Neon repository at Codeberg or Forgejo
https://bugs.kde.org/show_bug.cgi?id=487290 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #2 from Nicolas Fella --- Thank you for your proposal. We use a self-hosted Gitlab instance for all our code in KDE and it has served us well. The Gitlab we use is fully open source (we do not use the premium edition despite it being available to us without cost). The existence of non-open Gitlab code doesn't affect us really. We are currently not looking into switching to a different git forge. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 473679] Pinch to zoom with touchpad
https://bugs.kde.org/show_bug.cgi?id=473679 janiu...@protonmail.com changed: What|Removed |Added CC||janiu...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 447989] Support Armv8.2 SHA-512 instructions
https://bugs.kde.org/show_bug.cgi?id=447989 Paul Floyd changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #15 from Paul Floyd --- I got some AWS credits from the FreeBSD dev that makes everything work on ec2, no problems with the patch. Thanks again. commit 5bf987891972478376e816fefea2d9abac3cb4fe (origin/master, origin/HEAD) Author: David Benjamin Date: Wed Jan 5 00:22:30 2022 -0500 Add support for Armv8.2 SHA-512 instructions Fixes https://bugs.kde.org/show_bug.cgi?id=447989 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 479213] Cannot change kde languages because of locale
https://bugs.kde.org/show_bug.cgi?id=479213 muso...@gmail.com changed: What|Removed |Added CC||muso...@gmail.com --- Comment #3 from muso...@gmail.com --- Same problem, Fedora 40 KDE 6.0.4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487292] New: Option to enable activate on hover for bottom panel, as well as customize the bottom panel
https://bugs.kde.org/show_bug.cgi?id=487292 Bug ID: 487292 Summary: Option to enable activate on hover for bottom panel, as well as customize the bottom panel Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: windows2li...@zoho.com CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 Can we get an option to use "activate on hover" for the bottom panel, which includes "Applications" and "Places"? There's already enough clicking and flinging the cursor around to do what the Legacy Launcher could do more easily and intuitively. Now we have *fewer* options to configure our launcher? It's one of the *most used features* of the Plasma desktop. Because the Legacy Launcher no longer works with Plasma 6, I have no choice but to try and adapt to this new launcher. And why have "Places" at the bottom, which then further divides into *three more* sub-categories on the opposite side, which requires more mouse flinging to navigate to often-used items? We can no longer have this at the bottom panel (Legacy Launcher style): Applications -> quickly access an app Places -> quickly access favorite folders History -> quickly access recently opened files/folders Instead, we are forced into this: Applications -> quickly access an app Places -> must click (no option to hover) -> aim the mouse cursor over to three more sub-categories -> hover over the desired one -> fling the mouse cursor back to the opposite side to select the item There seems to be a trend of trying to "cram things into panels" and "require more side-to-side mouse movements". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466744] wayland: 2 monitor setup with 175% scaling on one screen and 100% on the other causes various problems
https://bugs.kde.org/show_bug.cgi?id=466744 slartibar...@gmail.com changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #5 from slartibar...@gmail.com --- Hi all, this problem seems gone with plasma 6.0.x Tested on 2 different machines with different resolutions/scaling factors closing this bug -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 487290] Host KDE Neon repository at Codeberg or Forgejo
https://bugs.kde.org/show_bug.cgi?id=487290 Tobias Fella changed: What|Removed |Added Resolution|--- |INTENTIONAL CC||fe...@posteo.de Status|REPORTED|RESOLVED --- Comment #1 from Tobias Fella --- no. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 487235] Some Breeze (light) icons not recolored for the Breeze Dark package
https://bugs.kde.org/show_bug.cgi?id=487235 Corbin changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #9 from Corbin --- Ah, turns out I used the wrong email for opening this bug report, so it didn't auto close. Anyway, my merge request was accepted, this problem will be solved with the next release. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 487285] Date/Time correction tool applies corrections twice, and in seemingly random order
https://bugs.kde.org/show_bug.cgi?id=487285 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #2 from Maik Qualmann --- We only have a limited influence on the order of processing; the same behavior can also be observed in BQM. We start a QThreadPool that processes the jobs according to free processor time. Maik -- You are receiving this mail because: You are watching all bug changes.
[kget] [Bug 480506] Resuming download after pause does not work
https://bugs.kde.org/show_bug.cgi?id=480506 Frank Kruger changed: What|Removed |Added CC||fkrue...@mailbox.org -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 487285] Date/Time correction tool applies corrections twice, and in seemingly random order
https://bugs.kde.org/show_bug.cgi?id=487285 Maik Qualmann changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/digikam/-/commit/45ac0 ||cb26f0e2e4194283898c547a950 ||e5c46c41 Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||8.4.0 --- Comment #1 from Maik Qualmann --- Git commit 45ac0cb26f0e2e4194283898c547a950e5c46c41 by Maik Qualmann. Committed on 20/05/2024 at 18:14. Pushed by mqualmann into branch 'master'. fix apply Date Time Adjust twice FIXED-IN: 8.4.0 M +1-1NEWS M +11 -3core/dplugins/generic/metadata/timeadjust/timeadjustdialog.cpp https://invent.kde.org/graphics/digikam/-/commit/45ac0cb26f0e2e4194283898c547a950e5c46c41 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483876] Spectacle takes blurry screenshots depending on the window position on Wayland with 1.5 fractional scale
https://bugs.kde.org/show_bug.cgi?id=483876 --- Comment #9 from zvova7...@gmail.com --- Yep, that's me :) Thanks for the merge! -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 485085] Unlocked desktop with apps flashes before kscreenlocker obscures the locked screen after wake-up from sleep
https://bugs.kde.org/show_bug.cgi?id=485085 popov895 changed: What|Removed |Added CC||popov...@ukr.net --- Comment #3 from popov895 --- (In reply to Daniel Duris from comment #2) > Another thing that seems related - once on a locked screen, if I press Esc > key, it goes to blank/black screen, where nothing is shown, not even a > cursor. Pressing Esc once more goes back to lockscreen. Esc used to defocus > out of the "enter password" dialog, now it does this. Definitely not a > feature as not even a background is shown. It's not a bug. Pressing Esc when the screen is locked simply turns it off/on. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 441146] Autosave and recovery for unsaved changes
https://bugs.kde.org/show_bug.cgi?id=441146 Makbac changed: What|Removed |Added Status|CONFIRMED |REPORTED Keywords||efficiency CC||annetjanne...@gmail.com Ever confirmed|1 |0 --- Comment #3 from Makbac --- Hello, there was an error while saving. Specifically, I saved the file initially, and when I finished my work and wanted to save it to avoid losing my progress, it gave me the following message: "You cannot save or create a new file because the auto-save process is still not finished." Please do something about this. I really don't want to lose the hours I spent on my drawing. -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 487291] Please port to Plasma 6
https://bugs.kde.org/show_bug.cgi?id=487291 apache changed: What|Removed |Added CC||sabayo...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[QtCurve] [Bug 487291] New: Please port to Plasma 6
https://bugs.kde.org/show_bug.cgi?id=487291 Bug ID: 487291 Summary: Please port to Plasma 6 Classification: Frameworks and Libraries Product: QtCurve Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: yyc1...@gmail.com Reporter: sabayo...@gmail.com CC: h...@kde.org Target Milestone: --- Please make it work on Plasma 6, QT6 I read this Qt6 support (#2) · Issues · System / QtCurve · GitLab https://invent.kde.org/system/qtcurve/-/issues/2 but I don't know who is ultimately responsible for qtcurve and what system Egor uses and how many months it will take. If developer doesn't have suitable distribution perhaps this could be done on virtual machine (I hope). For some users it is a big issue because as Linux users we love customize our systems :) No Qtcurve "Application Style" in Plasma 6 - Help - KDE Discuss https://discuss.kde.org/t/no-qtcurve-application-style-in-plasma-6/15353 -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 487094] Nextcloud Sync Client (Flatpak) asks for credentials every relaunch when KDE wallet subsystem disabled
https://bugs.kde.org/show_bug.cgi?id=487094 --- Comment #5 from Samuel Sanchez --- (In reply to Daniel Rusek from comment #4) > Did you try reinstalling the Flatpak and removing its existing config files > and other data? Yes, I have tried that for both the Bitwarden and the Standard Notes flatpaks, but this did not resolve the issue. Successful workarounds for the issue include switching to the Bitwarden and Standard Notes AppImages, or switching the desktop environment to GNOME Shell 46.1, or rolling back KDE Frameworks to version 6.1.0. It is the combination of KDE Wallet 6.2.0 and the Bitwarden and Standard Notes flatpaks that cause the issue on my end. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 487290] Host KDE Neon repository at Codeberg or Forgejo
https://bugs.kde.org/show_bug.cgi?id=487290 Francois Carpentier (Francewhoa) changed: What|Removed |Added URL||https://codeberg.org -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 487279] Feature Request, App Icon
https://bugs.kde.org/show_bug.cgi?id=487279 Albert Astals Cid changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||aa...@kde.org, ||sgmo...@kde.org Resolution|--- |WAITINGFORINFO --- Comment #1 from Albert Astals Cid --- Why would need a screenshot of your butt-ugly icon. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 487290] Host KDE Neon repository at Codeberg or Forgejo
https://bugs.kde.org/show_bug.cgi?id=487290 Francois Carpentier (Francewhoa) changed: What|Removed |Added CC||compost.idu_20230512_063308 ||@en.francewhoa.ca -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 487290] New: Host KDE Neon repository at Codeberg or Forgejo
https://bugs.kde.org/show_bug.cgi?id=487290 Bug ID: 487290 Summary: Host KDE Neon repository at Codeberg or Forgejo Classification: KDE Neon Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: compost.idu_20230512_063...@en.francewhoa.ca CC: carlosdema...@gmail.com, j...@jriddell.org, neon-b...@kde.org Target Milestone: --- Suggestion For a stronger security, stronger privacy, and for using a repository software that better match KDE Neon's values, I suggest two actions: ___1. Use the fully Libre Source (Open Source) and free https://codeberg.org or https://forgejo.org as PRIMARY code repository. Instead of the present GitLab. ___2. Use the partly Secret Source (Proprietary) GitLab as SECONDARY already existing code repository. In other words, an automated mirror of Codeberg or Forgejo primary repository above. For those not familiar with GitLab's strategy, it is only Libre Core (Open Core). Not fully Libre Source. GitLab modules are Secret Source. Both me and the Ubertus.Org team would be happy, as volunteer, to contribute testing and documentation, if needed. I was redirected from https://invent.kde.org to here at https://bugs.kde.org to communicate any suggestions or new features about KDE Neon. I am an end-user. Not a developer. I do not have a financial conflict of interest with Codeberg or Forgejo. I am just a happy end user. --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- --- Below is the same as above. But with details for those interested in those. Including my review of Forgejo. Strength • Forgejo visual design and workflow are similar to Github and GitLab. Which make migration and initial learning curve much easier. • Quick and easy start with the free and Libre Source (Open Source) at https://codeberg.org Which is a SaaS powered by Forgejo. Alternatively, the free and Libre Source (Open Source) Forgejo can be self-hosted per documentation at https://forgejo.org • Drop-in replacement for Gitea • Libre Source (Open Source). If you are not familiar with "Libre Source", it means this software has both stronger security & stronger privacy. Because its code is publicly available for review and contributions at https://codeberg.org/forgejo/forgejo • Attractive MIT license. This means the software code is owned and supported by a friendly not-for-profit community. Instead of a for-profit corporation. https://forgejo.org/imprint/ In comparison, Github, GitLab, Gitea are owned by for-profit corporation. • Federated • API • Kanban board • Dark theme • For those not familiar with the challenge with Gitea is that, starting in October 2022, without knowledge or approval of the community, a for-profit company took over the Gitea community domains and trademark. Big mistake. Since then, most of the Gitea community left to Forgejo.org. ___• What the Gitea community needed was to continue for a not-for profit organization to be the owner of its infrastructure and direction. Such as, but not limited to, its domains, trademark. ___• Obviously what would have resolved this challenge above was for the main developer and maintainer to simply create a for-profit organization. With its own domains and trademark. Without interfering in any ways to the already existing not-for-profit community organization. ___• Before leaving, the Gitea community communicated their needs to the Gitea main developer and maintainer. Which ignored them, then declined their suggestion. ___• The risk with for-profit company is that, usually, they value money above people. So in the future, it is very high risk that Gitea will introduce lock-ins to monetize. Functionalities available only if you pay. And increasingly make decision without involving the community or just ignore it. Why. Simply because legally speaking, for-profit organization communicate a clear intent that they value money above people. Above you ;) ___• "In October 2022 the domains and trademark of Gitea were transferred to a for-profit company without knowledge or approval of the community. Despite writing an open letter, the takeover was later confirmed." Source at: __• https://gitea-open-letter.coding.social __• https://archive.ph/T573R#selection-83.0-99.83 __• In other words, this challenge above could have been resolved with two organizations. A not-for-profit and a for-profit. Each with its own domains and trademarks. Unfortunately, the maintainer declined this. Took over the not-for-profit community. As a result, most of the Gitea community left to Forgejo. ___• To resolve this challenge, I suggest to migrating to any alternative to your liking which is owned by a NOT-for-profit organization. The keyword here is "NOT-for-profit". Be
[plasmashell] [Bug 487289] plasmashell on Wayland crashes when more than ~100 windows are open
https://bugs.kde.org/show_bug.cgi?id=487289 --- Comment #1 from Jacob Kauffmann --- The video (~1 minute) is too large to attach. Here's a link instead: https://www.dropbox.com/scl/fi/ybenhbnf563428nr165gm/kde-plasma-100-windows.webm?rlkey=9hbuk02e2v89s0cvm5dbcex60&e=1&st=rtyscexo&dl=0 -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 487214] Qt6 "kcoreaddons_add_plugin" attempts to link plugin in /INSTALL_NAMESPACE
https://bugs.kde.org/show_bug.cgi?id=487214
grmpf changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|--- |NOT A BUG
--- Comment #7 from grmpf ---
Thanks Nicolas for giving the correct hint! I could solve it by moving the line
set(KF_DEP_VERSION "${QT_MAJOR_VERSION}")
almost to the very top of the file. With this I can now build my plugin with
both Qt5 and Qt6.
I am closing the bug report because the change for the link/output path was
probably intentional instead of a bug.
However I am still curious why the Qt5 build links the binary in ./build/
while Qt6 creates the library in ./build/bin/kf6/ktexteditor/
Is there any reason why this was changed?
--
You are receiving this mail because:
You are watching all bug changes.
[Powerdevil] [Bug 353032] Add ability to set screen brightness for non-laptop displays so I can adjust to the room's lighting
https://bugs.kde.org/show_bug.cgi?id=353032 --- Comment #5 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/powerdevil/-/merge_requests/361 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 431994] per display ddcutil brightness control with -DHAVE_DDCUTIL
https://bugs.kde.org/show_bug.cgi?id=431994 --- Comment #6 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/powerdevil/-/merge_requests/361 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 487029] kmail uses media type literal packet in OpenPGP
https://bugs.kde.org/show_bug.cgi?id=487029 --- Comment #1 from theodor-andreas.boer...@gmx.de --- The bug was introduced in this commit: https://invent.kde.org/pim/messagelib/-/commit/df004260 I haven't tested, but I think reverting df004260 and d72f0c76 should fix it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487289] New: plasmashell on Wayland crashes when more than ~100 windows are open
https://bugs.kde.org/show_bug.cgi?id=487289 Bug ID: 487289 Summary: plasmashell on Wayland crashes when more than ~100 windows are open Classification: Plasma Product: plasmashell Version: 6.0.4 Platform: Neon OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: ja...@nerdonthestreet.com Target Milestone: 1.0 SUMMARY When running on Wayland, plasmashell has a maximum number of windows that it can handle-- around 100. When more than this number is opened, plasmashell crashes. It can be restarted once the number of windows goes back down, but not while the number remains the same. (See the attached video.) STEPS TO REPRODUCE 1. Start a KDE Wayland session 2. Open 100 windows, then a few more OBSERVED RESULT plasmashell crashes. EXPECTED RESULT plasmashell continues to run. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION This is happening on KDE Neon and Arch Linux (both currently with 6.0.4). The specific application does not matter. I recreated this in Neon with both Firefox and Kate, and most of my windows on Arch are typically Brave. The hardware also does not matter. I recreated this in Neon on VirtualBox, and in Arch on physical hardware (AMD CPU + NVIDIA GPU). When I'm teetering on the edge of the maximum window limit, opening the Notifications applet in the bottom panel is also able to count as a "window" and cause plasmashell to crash. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 487272] Crash while naming a new face tag.
https://bugs.kde.org/show_bug.cgi?id=487272 --- Comment #5 from Denis --- Taille du champs trop petite ... tailles champs de saisieChamp plus opérationnel ... reste en noir Concernant le face tag, je viens de découvrir qu'il ne fonctionne partiellement Lorsqu'on clic sur un nom saisie auparavant, le même symptôme se produit signalé précédemment. Au plaisir ... Denis Schmitt -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 487288] KIM (Kde Image Menu) and KDE 5 Service Menu & ReImage resizing shows weird colors in Gwenview
https://bugs.kde.org/show_bug.cgi?id=487288 --- Comment #5 from Kangarooo --- Reported also in and found out problem in gwenview https://github.com/caco3/kim5/issues/14 -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 487231] Hint button is too close to the demo button
https://bugs.kde.org/show_bug.cgi?id=487231 Albert Astals Cid changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 487268] Less contrast when using power saving mode
https://bugs.kde.org/show_bug.cgi?id=487268 Aru Sahni changed: What|Removed |Added CC||arusa...@gmail.com --- Comment #1 from Aru Sahni --- I'm encountering this, too, but with a non-HDR display. Theme: Breeze Dark Operating System: EndeavourOS KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.9.1-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics Memory: 30.7 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Framework Product Name: Laptop 13 (AMD Ryzen 7040Series) System Version: A7 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467766] MySQL foreign key error on a zero image id
https://bugs.kde.org/show_bug.cgi?id=467766 --- Comment #81 from Petr Schonmann --- Ive tested digiKam-8.4.0-20240512T090210-Qt6-x86-64.appimage and seems the problem gone Im getting this query fyi 2024-05-20 18:33:59.244565 Digikam::ItemLister::listImageTagPropertySearch: Search query: 2024-05-20 18:33:59.244585 "SELECT DISTINCT Images.id, Images.name, Images.album,Albums.albumRoot,ImageInformation.rating, Images.category,ImageInformation.format, ImageInformation.creationDate, Images.modificationDate, Images.fileSize,ImageInformation.width, ImageInformation.height,ImageTagProperties.value, ImageTagProperties.property, ImageTagProperties.tagid FROM ImagesINNER JOIN ImageTagProperties ON ImageTagProperties.imageid=Images.idLEFT JOIN ImageInformation ON Images.id=ImageInformation.imageidINNER JOIN Albums ON Albums.id=Images.album WHERE Images.status=1 AND ( ( ( ImageTagProperties.tagid=? AND ImageTagProperties.property=? ) OR ( ImageTagProperties.tagid=? AND ImageTagProperties.property=? ) OR ( ImageTagProperties.tagid=? AND ImageTagProperties.property=? ) OR ( ImageTagProperties.tagid=? AND ImageTagProperties.property=? ) ) );" 2024-05-20 18:33:59.244608 QList(QVariant(int, 4538), QVariant(QString, "autodetectedPerson"), QVariant(int, 4538), QVariant(QString, "autodetectedFace"), QVariant(int, 4538), QVariant(QString, "ignoredFace"), QVariant(int, 4538), QVariant(QString, "tagRegion")) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483876] Spectacle takes blurry screenshots depending on the window position on Wayland with 1.5 fractional scale
https://bugs.kde.org/show_bug.cgi?id=483876 Nate Graham changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/kwin/-/merge_requests/55 ||16 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||6.0.5 --- Comment #8 from Nate Graham --- This is fixed with the commits in https://invent.kde.org/plasma/kwin/-/merge_requests/5516, authored by Volodymyr Zolotopupov. They'll appear in Plasma 6.0.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 446288] In one-column view with subcategory page on the stack, clearing search returns inappropriately navigates back to subcategory page
https://bugs.kde.org/show_bug.cgi?id=446288 Bug Janitor Service changed: What|Removed |Added Priority|NOR |HI -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 487288] KIM (Kde Image Menu) and KDE 5 Service Menu & ReImage resizing shows weird colors in Gwenview
https://bugs.kde.org/show_bug.cgi?id=487288 --- Comment #4 from Kangarooo --- Created attachment 169664 --> https://bugs.kde.org/attachment.cgi?id=169664&action=edit Animation of making thouse files and opening in gwenview -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 487288] KIM (Kde Image Menu) and KDE 5 Service Menu & ReImage resizing shows weird colors in Gwenview
https://bugs.kde.org/show_bug.cgi?id=487288 --- Comment #3 from Kangarooo --- Created attachment 169663 --> https://bugs.kde.org/attachment.cgi?id=169663&action=edit How it looks in gvenview -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 487288] KIM (Kde Image Menu) and KDE 5 Service Menu & ReImage resizing shows weird colors in Gwenview
https://bugs.kde.org/show_bug.cgi?id=487288 --- Comment #2 from Kangarooo --- Created attachment 169662 --> https://bugs.kde.org/attachment.cgi?id=169662&action=edit Resized with weird colors in gwenview -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 425900] Search string matching only a single category shows the matched and disabled category in the results view, which is useless
https://bugs.kde.org/show_bug.cgi?id=425900 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||6.1 --- Comment #6 from Nate Graham --- I am not able to reproduce this anymore with today's git master. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 487288] KIM (Kde Image Menu) and KDE 5 Service Menu & ReImage resizing shows weird colors in Gwenview
https://bugs.kde.org/show_bug.cgi?id=487288 --- Comment #1 from Kangarooo --- Created attachment 169661 --> https://bugs.kde.org/attachment.cgi?id=169661&action=edit Original -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447486] In search result Appearance root node should be grayed to be consistent with other root nodes
https://bugs.kde.org/show_bug.cgi?id=447486 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||6.1 Status|CONFIRMED |RESOLVED --- Comment #1 from Nate Graham --- The "Appearance" group has been replaced with "Colors & Themes" and as of today's git master, I see that it becomes grayed out appropriately in search results. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 487288] New: KIM (Kde Image Menu) and KDE 5 Service Menu & ReImage resizing shows weird colors in Gwenview
https://bugs.kde.org/show_bug.cgi?id=487288 Bug ID: 487288 Summary: KIM (Kde Image Menu) and KDE 5 Service Menu & ReImage resizing shows weird colors in Gwenview Classification: Applications Product: gwenview Version: 21.12.3 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: kangar...@gmail.com Target Milestone: --- Kubuntu 22.04 https://bugs.launchpad.net/ubuntu/+source/gwenview/+bug/2064747 Okular shows normal colors of resized images, but not Gwenview See screenshots of original and resized images and screenshot of Gwenview with opened image how it shows 1a. Install KIM Cant download from https://store.kde.org/p/1126887 Found https://github.com/caco3/kim5 Here i also posted bugs Install error https://github.com/caco3/kim5/issues/13 Image resize error in Gwenview https://github.com/caco3/kim5/issues/14 1b. OR install ReImage 2. Reopen Dolphin or Log out and Log in 3. Right click image, make Kim -> Resize to some smaller size 4. In Gwenview image is weird colors having UPDATE: Also bad colors if installing https://store.kde.org/p/1231579/ 2.5.deb Heres buggy colors from KDE 5 Service Menu ReImage https://imgur.com/a/JeLMtin -- You are receiving this mail because: You are watching all bug changes.
