[Spectacle] [Bug 469518] The preview of Rectangular Region screenshot is not correct when working with a dual monitor
https://bugs.kde.org/show_bug.cgi?id=469518 ihipop changed: What|Removed |Added Resolution|FIXED |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #6 from ihipop --- (In reply to Nate Graham from comment #5) > Yes, quite possible. Let's call it fixed for now, until and unless it shows > up again. @Yu Te Wang 23.04.1 is still not working I'm using Manjaro and I've been waiting for the update of Spectacle ``` pamac info spectacle Name : spectacle Version : 23.04.1-1 Description : KDE screenshot capture utility URL : https://apps.kde.org/spectacle/ Licenses : GPL Repository: extra Installed Size: 3.4 MB Groups: kde-applications kde-graphics Depends On: xcb-util-cursor purpose knewstuff qt5-tools kpipewire Optional Dependencies : -- Required By : -- Optional For : -- Provides : -- Replaces : -- Conflicts With: -- Packager : Antonio Rojas Build Date: Wed 10 May 2023 04:57:28 PM CST Install Date : Tue 06 Jun 2023 05:18:56 PM CST Install Reason: Explicitly installed Validated By : Signature Backup files : -- ``` As I reported before, it is still the same. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470925] New: Dolphin crashes on drag and drop
https://bugs.kde.org/show_bug.cgi?id=470925
Bug ID: 470925
Summary: Dolphin crashes on drag and drop
Classification: Applications
Product: dolphin
Version: 23.04.1
Platform: Archlinux
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: dolphin-bugs-n...@kde.org
Reporter: a...@melissaautumn.com
CC: kfm-de...@kde.org
Target Milestone: ---
Application: dolphin (23.04.1)
Qt Version: 5.15.9
Frameworks Version: 5.106.0
Operating System: Linux 6.3.6-arch1-1 x86_64
Windowing System: Wayland
Distribution: EndeavourOS
DrKonqi: 5.27.5 [KCrashBackend]
-- Information about the crash:
While interacting with a custom application that requires you to drag and drop
files onto it, I found that dolphin crashed every time I selected the file
after a succesful drag and drop.
The crash can be reproduced every time.
-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 0x7f4666b7d74a in QMap::constFind
(akey=, this=) at
../../include/QtCore/../../src/corelib/tools/qmap.h:852
#7 QDrag::dragCursor (this=0x0, action=Qt::CopyAction) at kernel/qdrag.cpp:349
#8 0x7f4666b81fee in QBasicDrag::updateCursor
(this=this@entry=0x562a74f49fa0, action=Qt::CopyAction) at
kernel/qsimpledrag.cpp:307
#9 0x7f4664357a0c in QtWaylandClient::QWaylandDrag::setResponse
(this=this@entry=0x562a74f49fa0, response=...) at
/usr/src/debug/qt5-wayland/qtwayland/src/client/qwaylanddnd.cpp:123
#10 0x7f466435ca2e in operator() (action=Qt::CopyAction,
accepted=, __closure=) at
/usr/src/debug/qt5-wayland/qtwayland/src/client/qwaylanddatadevice.cpp:140
#11 QtPrivate::FunctorCall, QtPrivate::List, void,
QtWaylandClient::QWaylandDataDevice::startDrag(QMimeData*, Qt::DropActions,
QtWaylandClient::QWaylandWindow*):: >::call
(arg=, f=...) at /usr/include/qt/QtCore/qobjectdefs_impl.h:146
#12
QtPrivate::Functor, 2>::call, void>
(arg=, f=...) at /usr/include/qt/QtCore/qobjectdefs_impl.h:256
#13
QtPrivate::QFunctorSlotObject, 2, QtPrivate::List, void>::impl(int,
QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=, r=, a=,
ret=) at /usr/include/qt/QtCore/qobjectdefs_impl.h:443
#14 0x7f4cffe7 in QtPrivate::QSlotObjectBase::call (a=,
r=, this=, this=, r=, a=) at
../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398
#15 doActivate (sender=0x562a75e65fd0, signal_index=5,
argv=0x7ffdf85e9230) at kernel/qobject.cpp:3923
#16 0x7f4664360cce in
QtWaylandClient::QWaylandDataSource::dndResponseUpdated (this=,
_t1=, _t2=) at
.moc/moc_qwaylanddatasource_p.cpp:184
#17 0x7f466435f886 in QtWayland::wl_data_source::handle_target
(data=0x562a75e65fe0, object=, mime_type=0x7f464c0048dc
"text/uri-list") at
/usr/src/debug/qt5-wayland/build/src/client/qwayland-wayland.cpp:697
#18 0x7f46617b34f6 in ffi_call_unix64 () at ../src/x86/unix64.S:104
#19 0x7f46617aff5e in ffi_call_int (cif=cif@entry=0x7ffdf85e9450,
fn=, rvalue=, avalue=,
closure=closure@entry=0x0) at ../src/x86/ffi64.c:673
#20 0x7f46617b2b73 in ffi_call (cif=cif@entry=0x7ffdf85e9450, fn=, rvalue=rvalue@entry=0x0, avalue=avalue@entry=0x7ffdf85e9520) at
../src/x86/ffi64.c:710
#21 0x7f4664834645 in wl_closure_invoke
(closure=closure@entry=0x7f464c004800, target=,
target@entry=0x562a75f064b0, opcode=opcode@entry=0, data=,
flags=1) at ../wayland-1.22.0/src/connection.c:1025
#22 0x7f4664834e73 in dispatch_event (display=display@entry=0x562a74f4c5d0,
queue=0x562a74f4c6c0) at ../wayland-1.22.0/src/wayland-client.c:1631
#23 0x7f466483513c in dispatch_queue (queue=0x562a74f4c6c0,
display=0x562a74f4c5d0) at ../wayland-1.22.0/src/wayland-client.c:1777
#24 wl_display_dispatch_queue_pending (display=0x562a74f4c5d0,
queue=0x562a74f4c6c0) at ../wayland-1.22.0/src/wayland-client.c:2019
#25 0x7f4664338c06 in QtWaylandClient::QWaylandDisplay::flushRequests
(this=) at
/usr/src/debug/qt5-wayland/qtwayland/src/client/qwaylanddisplay.cpp:255
#26 0x7f4c2834 in QObject::event (this=0x562a74f4c470,
e=0x7f46540013d0) at kernel/qobject.cpp:1347
#27 0x7f466737893f in QApplicationPrivate::notify_helper (this=, receiver=0x562a74f4c470, e=0x7f46540013d0) at
kernel/qapplication.cpp:3640
#28 0x7f49ab18 in QCoreApplication::notifyInternal2
(receiver=0x562a74f4c470, event=0x7f46540013d0) at
kernel/qcoreapplication.cpp:1064
#29 0x7f49fa7b in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x562a74f3b300) at
kernel/qcoreapplication.cpp:1821
#30 0x7f4e6088 in postEventSourceDispatch (s=0x562a74f64080) at
kernel/qeventdispatcher_glib.cpp:277
#31 0x7f4664510981 in g_main_dispatch (context=0x7f465c000ee0) at
../glib/glib/gmain.c:3460
#32 g_main_context_dispatch (context=0x7f465c000ee0) at
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 470914] Mouse courser 'X' and 'o' do not show on the kstars star chart if you use the Wayland graphic platform. Works OK if using the X11 graphic platform.
https://bugs.kde.org/show_bug.cgi?id=470914 Jasem Mutlaq changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Jasem Mutlaq --- We can't do much about this, this is an issue with Qt5 / Wayland / KWin. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 470389] Accent mark should be shown before pressing a letter that can be accented
https://bugs.kde.org/show_bug.cgi?id=470389 --- Comment #4 from esperluett...@proton.me --- I continue to investigate this, but I found a Qt ticket (https://bugreports.qt.io/browse/QTBUG-79216) that explains that "Qt only generates keyReleaseEvent() for dead keys", confirming that it's on Qt side. Testing with xev show "correctly" (if I understand the output correctly) that press and release events are generated on a single press. Pressing "a" gives: > KeyPress event, serial 39, synthetic NO, window 0x121, >root 0x3c9, subw 0x0, time 17983802, (86,0), root:(219,356), >state 0x0, keycode 24 (keysym 0x61, a), same_screen YES, >XLookupString gives 1 bytes: (61) "a" >XmbLookupString gives 1 bytes: (61) "a" >XFilterEvent returns: False > KeyRelease event, serial 39, synthetic NO, window 0x121, >root 0x3c9, subw 0x0, time 17983857, (86,0), root:(219,356), >state 0x0, keycode 24 (keysym 0x61, a), same_screen YES, >XLookupString gives 1 bytes: (61) "a" >XFilterEvent returns: False And pressing accent key (aka dead key) "^" also gives two events: > KeyPress event, serial 39, synthetic NO, window 0x121, >root 0x3c9, subw 0x0, time 17985745, (86,0), root:(219,356), >state 0x0, keycode 34 (keysym 0xfe52, dead_circumflex), same_screen YES, >XLookupString gives 1 bytes: (5e) "^" >XmbLookupString gives 0 bytes: >XFilterEvent returns: True > KeyRelease event, serial 39, synthetic NO, window 0x121, >root 0x3c9, subw 0x0, time 17985793, (86,0), root:(219,356), >state 0x0, keycode 34 (keysym 0xfe52, dead_circumflex), same_screen YES, >XLookupString gives 1 bytes: (5e) "^" >XFilterEvent returns: False So I seems like Qt ignores the dead key (as not a "real" key event) before merging it with next character (certainly to lookup if the accent + character is a valid and so, a single character, or not valid and outputs two characters), but I need more investigation to understand where exactly the event is "lost", if may be recoverable or not by KDE, or if Qt prevents it completely (since Qt team don't seem to change this behaviour, and so, I will close this ticket). The consequence of this may not only be visual, like in the case for this ticket: https://bugs.kde.org/show_bug.cgi?id=464822 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443317] plasmashell crashes after toggle the "Show Background" on applet
https://bugs.kde.org/show_bug.cgi?id=443317 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #10 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 469702] When I upload a krita file it comes blurry
https://bugs.kde.org/show_bug.cgi?id=469702 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 469677] CLOSING SESSIONKrita Version: 5.0.0 Languages: zh_CN, zh, en_US, en Hidpi: true Qt Version (compiled): 5.12.12 Version (loaded): 5.12.12 OS Information Build ABI: x8
https://bugs.kde.org/show_bug.cgi?id=469677 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 470090] [Wayland][Nvidia?] Ksplashqml, plasma and systemsettings crash on login
https://bugs.kde.org/show_bug.cgi?id=470090 --- Comment #17 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 469188] Alternate buttons not working under Wayland
https://bugs.kde.org/show_bug.cgi?id=469188 --- Comment #6 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437925] Crash in BlurEffect::blurRegion
https://bugs.kde.org/show_bug.cgi?id=437925 --- Comment #11 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.
[kate] [Bug 470920] Makefile syntax highlighting doesn't handle line-breaks for multiple targets
https://bugs.kde.org/show_bug.cgi?id=470920 samcas...@gmail.com changed: What|Removed |Added CC||samcas...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 467082] Kup/bup fails to save
https://bugs.kde.org/show_bug.cgi?id=467082 samcas...@gmail.com changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- CC||samcas...@gmail.com Ever confirmed|0 |1 --- Comment #2 from samcas...@gmail.com --- I'm reopening as this keeps happening, and I now cannot fix it by restarting kup. Does anyone have any ideas? Some relevant facts: - One of my backups saves fine, the other does not. - The integrity check is satisfied, almost the whole backup is completed, and it errors right near the end. (As you can see below, with bup "save") -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 470924] Discover crashed when I tried to search for an item
https://bugs.kde.org/show_bug.cgi?id=470924 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DOWNSTREAM --- Comment #1 from Bug Janitor Service --- Thank you for the bug report! However Plasma 5.25.5 is no longer eligible for support or maintenance from KDE; supported versions are 5.27, and 5.27 or newer. Please upgrade to a supported version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one. If you need support for Plasma 5.25.5, please contact your distribution, who bears the responsibility of providing support for older releases that are no longer supported by KDE. If you can reproduce the issue after upgrading to a supported version, feel free to re-open this bug report. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 470924] New: Discover crashed when I tried to search for an item
https://bugs.kde.org/show_bug.cgi?id=470924 Bug ID: 470924 Summary: Discover crashed when I tried to search for an item Classification: Applications Product: Discover Version: 5.25.5 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: thedarcb...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.25.5) Qt Version: 5.15.6 Frameworks Version: 5.98.0 Operating System: Linux 5.19.0-44-generic x86_64 Windowing System: X11 Distribution: Ubuntu 22.10 DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: I entered the word Vis (for Visual Studio) in the search box, and the app crashed before I could proceed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 0x7fa229b4f54f in QTextStream::operator<<(char) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa1e1b162dd in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so #6 0x7fa1e1b19332 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so #7 0x7fa1e1b2530f in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/discover/flatpak-backend.so #8 0x7fa229af36ff in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fa2298d6f2d in QFutureWatcherBase::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fa22ad6bf32 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #11 0x7fa229abae38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7fa229abdeb1 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fa229b15427 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7fa228721569 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fa2287763c8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7fa22871ed20 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7fa229b14aea in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #18 0x7fa229ab97cb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7fa229ac1c2a in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x561e703966d3 in ?? () #21 0x7fa229023510 in __libc_start_call_main (main=main@entry=0x561e70395e20, argc=argc@entry=1, argv=argv@entry=0x7ffdc8df7dd8) at ../sysdeps/nptl/libc_start_call_main.h:58 #22 0x7fa2290235c9 in __libc_start_main_impl (main=0x561e70395e20, argc=1, argv=0x7ffdc8df7dd8, init=, fini=, rtld_fini=, stack_end=0x7ffdc8df7dc8) at ../csu/libc-start.c:381 #23 0x561e703970a5 in ?? () [Inferior 1 (process 99458) detached] The reporter indicates this bug may be a duplicate of or related to bug 467506, bug 467557, bug 468123, bug 469614, bug 470270, bug 470655, bug 470887. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467426] Often wrong window preview shown on hover
https://bugs.kde.org/show_bug.cgi?id=467426 Fushan Wen changed: What|Removed |Added CC||nyanpas...@tuta.io --- Comment #5 from Fushan Wen --- *** Bug 470012 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470012] Hovering icons in Icons-Only Task Manager on Wayland results in slow preview transitions, incorrect positions
https://bugs.kde.org/show_bug.cgi?id=470012 Fushan Wen changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||qydwhotm...@gmail.com --- Comment #2 from Fushan Wen --- *** This bug has been marked as a duplicate of bug 467426 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470923] New: When search result are updated, the field text cursor position is placed at the field end
https://bugs.kde.org/show_bug.cgi?id=470923 Bug ID: 470923 Summary: When search result are updated, the field text cursor position is placed at the field end Classification: Applications Product: dolphin Version: 23.04.1 Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: search Assignee: dolphin-bugs-n...@kde.org Reporter: esperluett...@proton.me CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When searching in a folder in Dolphin, the search term is updated after some delay. If the user moves the text cursor position in this field before the end of the delay, the text cursor position is set in the field end after the delay. Editing the field can become quite difficult when removing/inserting characters in the middle of the search term. STEPS TO REPRODUCE 1. Activate search in Dolphin 2. Enter a search term 3. *Before* the search delay ends, move the text cursor in the middle of the search term 4. Wait for the search delay to end 5. Press any key to edit the search term OBSERVED RESULT The pressed character is added to the end of the search term (since the cursor if placed at the end when delay ends). EXPECTED RESULT The text cursor position should stay unchanged, and so the inserted character placed where the text cursor was before the delay ended. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon Live (20230504-0714) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Graphics: X11 on Neon -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470922] New: Pasting file/folder to Desktop doesn't follow cursor position
https://bugs.kde.org/show_bug.cgi?id=470922 Bug ID: 470922 Summary: Pasting file/folder to Desktop doesn't follow cursor position Classification: Plasma Product: plasmashell Version: master Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Desktop Containment Assignee: plasma-b...@kde.org Reporter: esperluett...@proton.me CC: notm...@gmail.com Target Milestone: 1.0 SUMMARY When copy-pasting a file/folder to the Desktop using Ctrl+C then Ctrl+V, the item is not positioned under the mouse but on top-left edge of the Desktop. The behaviour should be the same as when dragging a file/folder, where the final position of item should be where the mouse was positioned when the operation was started. STEPS TO REPRODUCE 1. Open a Dolphin window 2. Select a file to copy 3. Click on Desktop 4. Press Ctrl+V to paste the file on Desktop OBSERVED RESULT The file is positioned on top-left edge. EXPECTED RESULT The file should be positioned as the same place that the mouse cursor when Ctrl+V was pressed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Neon Live (20230504-0714) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Graphics: X11 on Neon -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 470921] New: UI bug - icon is not lit like the other icons
https://bugs.kde.org/show_bug.cgi?id=470921 Bug ID: 470921 Summary: UI bug - icon is not lit like the other icons Classification: Applications Product: Haruna Version: 0.11.1 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic Assignee: georgefb...@gmail.com Reporter: sunsp...@gmail.com Target Milestone: --- Created attachment 159607 --> https://bugs.kde.org/attachment.cgi?id=159607=edit Screen snip of the Haruna configure settings SUMMARY This is a minor UI bug, but it should be consistent. The video icon is dim compared to the rest of the icons in the configure settings. STEPS TO REPRODUCE 1. Look at the configure settings. OBSERVED RESULT The video icon is dim compared to the other icons. EXPECTED RESULT Icon should be the same brightness as the rest of the icons. SOFTWARE/OS VERSIONS Operating System: SteamOS 3.4.6 KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 5.13.0-valve36-1-neptune (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 470889] KPhotoAlbum crashes when closing the Annotations window if previous Viewer window is already closed
https://bugs.kde.org/show_bug.cgi?id=470889 --- Comment #4 from Victor Lobo --- Wow, such a quick response. I tested, and the fix works correctly. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 470920] New: Makefile syntax highlighting doesn't handle line-breaks for multiple targets
https://bugs.kde.org/show_bug.cgi?id=470920 Bug ID: 470920 Summary: Makefile syntax highlighting doesn't handle line-breaks for multiple targets Classification: Applications Product: kate Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: samcas...@gmail.com Target Milestone: --- Created attachment 159606 --> https://bugs.kde.org/attachment.cgi?id=159606=edit screenshot example Syntax highlighting handles line breaks in dependencies correctly, e.g.: ``` target1 target2 &: \ dep1 \ dep2 \ dep3 ``` will correctly highlight all of the deps as (for me) blue, the line breaks as purple, and the targets as yellow. However if I have multiple targets split over multiple lines: ``` target1 \ target2 \ target3 &: \ dep1 \ dep2 \ dep3 ``` Then the first two lines of targets area not highlighted. Apologies if pedantic. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 467829] The line tool doesn't work propperly with pressure sensitive brushes
https://bugs.kde.org/show_bug.cgi?id=467829 marcelo.lope...@gmail.com changed: What|Removed |Added CC||marcelo.lope...@gmail.com --- Comment #3 from marcelo.lope...@gmail.com --- I find the same with the Freehand tool. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 470691] "Address book" button doesn't bring any window
https://bugs.kde.org/show_bug.cgi?id=470691 Rafael Linux User changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #2 from Rafael Linux User --- Yes, really is "Address book" in English, I'm sorry. I include "Open in Address Book" in Kmail toolbar., but it doesn't nothing. I changed icon to "Address book" and it works now. Maybe I don't understand right what's "Open in Address Book", sorry. I'll try to guess. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470919] Pressure sensitivity with a Bamboo Ink pen is not working in Krita on MS Surface Laptop Studio
https://bugs.kde.org/show_bug.cgi?id=470919 marcelo.lope...@gmail.com changed: What|Removed |Added CC||marcelo.lope...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470919] New: Pressure sensitivity with a Bamboo Ink pen is not working in Krita on MS Surface Laptop Studio
https://bugs.kde.org/show_bug.cgi?id=470919 Bug ID: 470919 Summary: Pressure sensitivity with a Bamboo Ink pen is not working in Krita on MS Surface Laptop Studio Classification: Applications Product: krita Version: 5.1.5 Platform: Compiled Sources OS: All Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: marcelo.lope...@gmail.com Target Milestone: --- Created attachment 159605 --> https://bugs.kde.org/attachment.cgi?id=159605=edit Notice that none of the strokes reflect pressure sensitivity differences being present. SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Use a Bamboo Ink pen (using MPP protocol) by pairing it with the Surface Laptop Studio. 2. Test with MS Whiteboard (notice that Pressure sensitivity works when using any selected pen) 3. Open Krita, create a new canvas. 4. Select any pen style that makes use of pressure sensitivity (a Marker for example). 5. Draw on the canvas with the lightest touch possible, then increase the pressure and you will notice that there is no difference in the FULLNESS of what's drawn on the Screen. 6. I checked settings to use BOTH WinTab and Windows 8+ configurations. Neither of which results in any pressure sensitivity expectations being present. OBSERVED RESULT No pressure sensitivity being present. EXPECTED RESULT Pressure sensitivity being present. SOFTWARE/OS VERSIONS Windows: 11 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION: Test requires a Wacom Bamboo Ink Stylus/Pen -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401800] Even so I enabled pen pressure, pen pressure is not working
https://bugs.kde.org/show_bug.cgi?id=401800 marcelo.lope...@gmail.com changed: What|Removed |Added CC||marcelo.lope...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 470691] "Address book" button doesn't bring any window
https://bugs.kde.org/show_bug.cgi?id=470691 Rafael Linux User changed: What|Removed |Added CC||rafael.linux.u...@gmail.com Summary|"Phonebook" button doesn't |"Address book" button |bring any window|doesn't bring any window -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 470918] SDDM numlock behaviour is broken
https://bugs.kde.org/show_bug.cgi?id=470918 Emre changed: What|Removed |Added Platform|Other |Debian stable -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 470918] New: SDDM numlock behaviour is broken
https://bugs.kde.org/show_bug.cgi?id=470918 Bug ID: 470918 Summary: SDDM numlock behaviour is broken Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: emretunc...@gmail.com Target Milestone: --- SUMMARY *** I enabled NumLock from Settings -> Keyboard -> Hardware, also I added; "[General] Numlock=on" to /etc/sddm.conf but after fresh reboot in SDDM Login Screen numpad doesnt work. Numlock seems enabled as it should be but I need to click password bar to use numpad keys otherwise cannot write anything with numpad even if it looks like I can write. *** STEPS TO REPRODUCE 1. Settings -> Keyboard -> Hardware -> NumLock on Plasma Startup -> Turn on. 2. Adding Numlock=on to [General] section in /etc/sddm.conf file. 3. Reboot or Log Out from system. OBSERVED RESULT NumLock seems enabled but numpad keys doesn't work until clicking password area. EXPECTED RESULT Numpad keys should work without clicking password bar or disabling/enabling NumLock. SOFTWARE/OS VERSIONS Linux: Debian 12 Stable KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Graphics Platform: Wayland SDDM Version: 0.19.0-5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470888] Can KDE officially implement the functions of xdotool and wmctrl tools in KWin?
https://bugs.kde.org/show_bug.cgi?id=470888 --- Comment #2 from silentdoer <1010993...@qq.com> --- (In reply to David Edmundson from comment #1) > This is out of scope for a bug report. That's true, but I don't know where to apply for this feature -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 470917] Cannot clear/erase the playlist once created
https://bugs.kde.org/show_bug.cgi?id=470917 --- Comment #1 from sunsp...@gmail.com --- remember checked (default unchecked) - hitting clear, the app remembers that it is cleared, pops open the panel and leaves it open.. but the playlist is still present. If one opens a file from the file-open menu, all the files in the playlist will re-open. probably related to the below if it is checked. auto load unchecked (default checked) - disables the playlist interface BUT.. all the videos selected in dolphin all open at once and start playing at once! This is very broken.. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 470917] New: Cannot clear/erase the playlist once created
https://bugs.kde.org/show_bug.cgi?id=470917 Bug ID: 470917 Summary: Cannot clear/erase the playlist once created Classification: Applications Product: Haruna Version: 0.11.1 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic Assignee: georgefb...@gmail.com Reporter: sunsp...@gmail.com Target Milestone: --- SUMMARY Once a playlist is created by multi-selecting files in dolphin and clicking play, it's impossible to clear/erase/remove files from the playlist. STEPS TO REPRODUCE 1. Select two files in dolphin, right-click and select open with Haruna 2. Moving the mouse to the right pops up the playlist slider. Right-click on files and select "remove from playlist" or "clear playlist" 3. Close Haruna and re-open it. 4. Play any file at all. OBSERVED RESULT All the files manually removed from the playlist and/or cleared by pressing the button are still present/return. Not only that, but launching another file from dolphin by itself ADDS to the playlist.. the playlist will grow and grow. Due to files being opened being auto-added to the playlist, it also means once a video finishes playing it will move on to the next video even if you didn't want it to be there at all. EXPECTED RESULT That the user interface have the ability to CLEAR the playlist or REMOVE a file from the playlist. SOFTWARE/OS VERSIONS Operating System: SteamOS 3.4.6 KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 Kernel Version: 5.13.0-valve36-1-neptune (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION Flatpak -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 470809] Haruna restarts the video after playback ends
https://bugs.kde.org/show_bug.cgi?id=470809 --- Comment #5 from sunsp...@gmail.com --- Now I have found the playlist due to the dolphin multi-select, and there is a playlist bug. Time for a new report. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 470916] New: Google voice typing doesn't work.
https://bugs.kde.org/show_bug.cgi?id=470916 Bug ID: 470916 Summary: Google voice typing doesn't work. Classification: Applications Product: kdeconnect Version: unspecified Platform: Android OS: Android 11.x Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: mashkal2...@gmail.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Remote Input 2. tap Keyboard icon 3. tap mic button on Google Keyboard OBSERVED RESULT no text is entered EXPECTED RESULT text is entered SOFTWARE/OS VERSIONS v 1.25.0 ADDITIONAL INFORMATION I know the compose menu exists, but but that adds an extra buffer. Any chance the main remote input could support voice typing? -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 470809] Haruna restarts the video after playback ends
https://bugs.kde.org/show_bug.cgi?id=470809 --- Comment #4 from sunsp...@gmail.com --- Looking in the configure, I see "Repeat" has a installation default setting of checked. Unchecking it stops the repeat. At the end of the video it displays the frame visible from the beginning of the video instead of the last frame, but doesn't otherwise continue playing. I have no idea where in the user interface one would work with playlists. The file portal doesn't allow selecting multiple files at once and there doesn't seem to be any menu option for creating playlists. The only thing I can see is that one can select multiple files in dolphin, but only there, but after playback is started there is no visible indication that a playlist exists. I think repeat should not be a default setting for a new profile if every media file opened is considered a playlist. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 456482] hardware decoding doesn't work
https://bugs.kde.org/show_bug.cgi?id=456482 --- Comment #18 from sunsp...@gmail.com --- PS. Environment is x.org on this device. I don't have the option of using wayland as it is not available. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 456482] hardware decoding doesn't work
https://bugs.kde.org/show_bug.cgi?id=456482 sunsp...@gmail.com changed: What|Removed |Added CC||sunsp...@gmail.com Version|0.8.0 |0.11.1 Platform|Debian unstable |Flatpak --- Comment #17 from sunsp...@gmail.com --- I was trying to get this to work so that it would use vaapi instead of vaapi-copy on this AMD APU 0405. I set the environment variable in the /etc/environment file as well as the other ways like export, etc. I had no success with the flatpak version. It continues to use vaapi-copy. mpv flatpak can use vaapi however. I wonder if an environment variable like this needs to be set inside the flatpak, or if mpv does something different compared to libmpv? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 470915] New: Discover on Debian 12 does not show the top bar button window
https://bugs.kde.org/show_bug.cgi?id=470915 Bug ID: 470915 Summary: Discover on Debian 12 does not show the top bar button window Classification: Applications Product: Discover Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: todo.ciencia.y.electron...@gmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 159604 --> https://bugs.kde.org/attachment.cgi?id=159604=edit Screenshot buttons not appear SUMMARY As the title suggests, on debian 12 systems with KDE Plasma Desktop the Discover window does not Generate window buttons (Close maximize/minimize etc.) -Debian 12 Stable was released on June 10, so there are no pending updates. STEPS TO REPRODUCE 1. Install or Update to a Debian 12 Stable release. [Clean Instalation using previous User Settings backup from a Deb11 with testing repository] 2. Open discover [default included with Deb12] - App work as normal but the top bar buttons the upper buttons are not generated although they maintain the functions if they are clicked (blind click) 3. - Restarting don't fix issue. (other windows or apps work/have buttons normally) OBSERVED RESULT The program operates normally and continues to maintain the functions of the window buttons if you click on them, (they are simply not visible) EXPECTED RESULT Discover should generate Window buttons SOFTWARE/OS VERSIONS Linux/KDE Plasma: Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.1.0-9-amd64 (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx Memory: 13.6 GiB of RAM Graphics Processor: AMD Radeon Vega 8 Graphics Manufacturer: HP Product Name: HP 245 G7 Notebook PC ADDITIONAL INFORMATION -KDE Plasma Dark theme with Plastik theme windows, Adapta icons. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 469955] Problemes instalación de Kmymoney en Windows 11Pro
https://bugs.kde.org/show_bug.cgi?id=469955 Jack changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #5 from Jack --- Sorry this got lost. It turns out there was a problem in the build system for the Windows versions, which was fixed about five days ago. Please try downloading a more recent version, and let us know if it still doesn't work. *** This bug has been marked as a duplicate of bug 470001 *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 470001] KMM crashes on startup on Window
https://bugs.kde.org/show_bug.cgi?id=470001 Jack changed: What|Removed |Added CC||joancfra...@gmail.com --- Comment #10 from Jack --- *** Bug 469955 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469275] Non-removable volumes shown as removable volumes
https://bugs.kde.org/show_bug.cgi?id=469275 Aleksey Kontsevich changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Aleksey Kontsevich --- Any chance to fix this?! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470175] Without focus, XWayland apps cannot get Clipboard/Selection change events from Wayland apps.
https://bugs.kde.org/show_bug.cgi?id=470175 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #4 from David Edmundson --- >Also not sure if it's intentional. It's definitely intentional. >Meanwhile, it works OK on GNOME Wayland. That's the more surprising twist. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470913] With multiple power Battery & Brightness widgets, "manually block" state isn't synchronized/
https://bugs.kde.org/show_bug.cgi?id=470913 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kphotoalbum] [Bug 470889] KPhotoAlbum crashes when closing the Annotations window if previous Viewer window is already closed
https://bugs.kde.org/show_bug.cgi?id=470889 Johannes Zarl-Zierl changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/kphotoalbum/-/commit/e ||ae40928b1949c36838bda0b265f ||b5fec1bb95fc --- Comment #3 from Johannes Zarl-Zierl --- Git commit eae40928b1949c36838bda0b265fb5fec1bb95fc by Johannes Zarl-Zierl. Committed on 11/06/2023 at 21:26. Pushed by johanneszarl into branch 'master'. Fix crash when AnnotationDialog is called from ViewerWidget If the AnnotationDialog is called from the ViewerWidget (via the "Annotate..." action in the context menu, ViewerWidget::editImage() is called which calls MainWindow::configureImages(). Since MainWindow::configureImages() is a potentially long-running function call, it is possible that the ViewerWidget was closed (and deleted) before the function returns. In this case, the execution returns to ViewerWidget::editImage of the already deleted ViewerWidget object, leading to a crash. By calling MainWindow::configureImages asynchronoulsy, the whole issue is avoided. M +6-3Viewer/ViewerWidget.cpp https://invent.kde.org/graphics/kphotoalbum/-/commit/eae40928b1949c36838bda0b265fb5fec1bb95fc -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470874] KWin Wayland crash in KWin::Group::icon()
https://bugs.kde.org/show_bug.cgi?id=470874 David Edmundson changed: What|Removed |Added Ever confirmed|0 |1 CC||k...@davidedmundson.co.uk Status|REPORTED|CONFIRMED --- Comment #2 from David Edmundson --- Can reproduce. I believe the path is: - client gets released (presumably unmapped?) - we clear grouping - they update an icon property A guard is trivial if that's the right direction. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 470910] Trying to open applications or get applications through discover or even other applications outside of Discover, all come up with the error: "no metadata URIs for vendor-direc
https://bugs.kde.org/show_bug.cgi?id=470910 --- Comment #6 from Jim Maguire --- (In reply to Nicolas Fella from comment #1) > "no metadata URIs for vendor-directory" and "could not open > appstream://org.kde.kdeconnect.app" are entirely unrelated. For the former > see https://bugs.kde.org/show_bug.cgi?id=462931 Ok so I followed that thread to it's conclusion and removing the check in the vendor directory checkbox does prevent the issue occurring, however (and this is an arch newbie question) does that not limit the content that discover can now provide me? if no, then I'm happy this is resolved. If yes then it's not really a perfect solution. Just curious -- You are receiving this mail because: You are watching all bug changes.
[skrooge] [Bug 384119] DELETE
https://bugs.kde.org/show_bug.cgi?id=384119 Irfend changed: What|Removed |Added Component|general |general CC||steph...@mankowski.fr Product|apper |skrooge Version|1.0.0 |2.22.0 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 470449] Error while trying to submit review on plasma-discover (server replied: BAD REQUEST)
https://bugs.kde.org/show_bug.cgi?id=470449 --- Comment #2 from threeseven.t...@gmail.com --- (In reply to Nate Graham from comment #1) > I've periodically seen this too. Doesn't seem 100% reproducible; kinda > random. Maybe we should retry a few times if the server is being flaky. Hmm, for me it seems to be happening 100% of the time. Regardless of the application or time of the day. It isn't a huge deal, but it's something you would expect to work typically with no issue. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 470910] Trying to open applications or get applications through discover or even other applications outside of Discover, all come up with the error: "no metadata URIs for vendor-direc
https://bugs.kde.org/show_bug.cgi?id=470910 --- Comment #5 from Jim Maguire --- Hey guys, thank you for chipping in on this. A-lot of googling and experimenting later I've managed to resolve this partially. by default KDE Plasma on Arch Linux doesn't install packagekit-qt5 or appstream-qt it seems. So I manually installed both and the list of applications available in discover is now listed. Outside of that I still get the meta data error however if I close it now I can access the stuff in the list and install KDE Connect. I haven't set it up and used it yet but it does install. in answer to your statement Nicolas that it was weird it opened at all. The welcoming wizard actually points you to it and says you can use KDE Connect etc, etc... so I presume it's actually meant to be there?? I'm not sure, that's just conjecture but it's odd they'd mention it and it not be there. Anyway I have it working for now, but I would like to find a resolution to the popup message re: metadata and to remove that if you guys have ideas? -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 470664] Laptop screen brightness not restored if interrupted while screen-dimming
https://bugs.kde.org/show_bug.cgi?id=470664 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #2 from Nicolas Fella --- What do you mean with "Then interrupt by keyboard press. Login again."? -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 470914] Mouse courser 'X' and 'o' do not show on the kstars star chart if you use the Wayland graphic platform. Works OK if using the X11 graphic platform.
https://bugs.kde.org/show_bug.cgi?id=470914 Charles changed: What|Removed |Added CC||kennedy.charle...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 470914] New: Mouse courser 'X' and 'o' do not show on the kstars star chart if you use the Wayland graphic platform. Works OK if using the X11 graphic platform.
https://bugs.kde.org/show_bug.cgi?id=470914 Bug ID: 470914 Summary: Mouse courser 'X' and 'o' do not show on the kstars star chart if you use the Wayland graphic platform. Works OK if using the X11 graphic platform. Classification: Applications Product: kstars Version: 3.6.5 Platform: Kubuntu OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: kennedy.charle...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Switch display platform from default X11 to Wayland 2. Open kstars. Make sure mouse pointer curser is set to 'X' or 'O'. 3. Note that mouse curser disappears when on star chart. OBSERVED RESULT Mouse curser disappears EXPECTED RESULT Mouse curser appears. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KUBUNTU 23.04 (available in About System) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION duplicated this problem on two different systems. all running the same versions of everything. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 470880] Crash while opening .nef raw image
https://bugs.kde.org/show_bug.cgi?id=470880 Nicolas Fella changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #3 from Nicolas Fella --- Thanks. This appears to be a regression from exiv 0.28. I've opened https://github.com/Exiv2/exiv2/issues/2649 for this -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470845] Dolphin crashes in Solid::StorageAccess::isEncrypted when generating thumbnails
https://bugs.kde.org/show_bug.cgi?id=470845 Christoph Cullmann changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/fram ||eworks/kio/-/commit/3fdcb7b ||cdae3a3dc95ce5b3d1574080245 ||0b129e Resolution|--- |FIXED --- Comment #5 from Christoph Cullmann --- Git commit 3fdcb7bcdae3a3dc95ce5b3d15740802450b129e by Christoph Cullmann, on behalf of Nicolas Fella. Committed on 11/06/2023 at 20:29. Pushed by cullmann into branch 'master'. [previewjob] Check whether thumbRootDevice is valid before access storageAccessFromPath may return an invalid device, e.g. because the thumbnail directory doesn't exist yet In that case we must not use the device M +1-1src/gui/previewjob.cpp https://invent.kde.org/frameworks/kio/-/commit/3fdcb7bcdae3a3dc95ce5b3d15740802450b129e -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 470913] New: With multiple power Battery & Brightness widgets, "manually block" state isn't synchronized/
https://bugs.kde.org/show_bug.cgi?id=470913 Bug ID: 470913 Summary: With multiple power Battery & Brightness widgets, "manually block" state isn't synchronized/ Classification: Applications Product: systemsettings Version: 5.27.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_powerdevil Assignee: plasma-b...@kde.org Reporter: o...@geek.co.il CC: k...@privat.broulik.de, natalie_clar...@yahoo.de Target Milestone: --- SUMMARY I have setup - in addition to the Battery & Brightness popup widget in the system tray - more Battery & Brightness widgets on the desktops in each of the activities I use - so it is always very accessible. When I change any of the sliders on the widget - that change is immediately reflected in all the other copies of Battery & Brightness. But when I toggle the "Manually block sleep and screen locking" checkbox - it is not reflected in any other copy, i.e. there is one copy of Battery & Brightness that shows that locking is inhibited, but all other copies don't show anything, not even the "X is inhibiting sleep & screen locking" message that appears when something is inhibiting sleep. The problem with that is that I use manual inhibiting quite a lot, but often forget in which activity I did that, so when I look at the other widget and see it isn't blocked, I feel I can walk away from my computer and when I come back I see our malicious CISO had change my wallpaper to an annoying message about locking my computer! STEPS TO REPRODUCE 1. Add a Battry & Brightness widget to your background. 2. Make sure the CISO has an image with red text on black background saying something like "You should always lock your computer!". 3. Open the Battery & Brightness system tray widget and check "Manually block sleep and screen locking". 4. Work on something for a while. 5. Get up and stretch, look at your Battery & Brightness widget on the desktop and see that its "Manually block sleep" checkbox is off. Conclude that its OK to go get that espresso you'd been promising yourself for the last couple of hours. OBSERVED RESULT You come back to find your screen unlocked, your wallpaper is now an ugly red & black nightmare, and the CISO evilly sniggering in his corner office. EXPECTED RESULT You would notice that your system is inhibited, so you manually lock the screen before leaving to get that espresso. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.9 Kernel Version: 6.2.0-20-generic (64-bit) Graphics Platform: offscreen Processors: 8 × Intel® Core™ i7-7820HQ CPU @ 2.90GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 630 ADDITIONAL INFORMATION I've known people whose CISO does `rm -rf $HOME` and then feign ignorance when they exclaim that the company's backup software had been misbehaving the last couple of weeks and there are multiple open IT tickets about that. Luckily, I'm not in that situation . -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 470758] Slightly incorrect UI on playback (timer area)
https://bugs.kde.org/show_bug.cgi?id=470758 --- Comment #4 from george fb --- I don't know what I'll do. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 470817] Help button items are greyed out if one changes an option first
https://bugs.kde.org/show_bug.cgi?id=470817 george fb changed: What|Removed |Added Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470888] Can KDE officially implement the functions of xdotool and wmctrl tools in KWin?
https://bugs.kde.org/show_bug.cgi?id=470888 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from David Edmundson --- This is out of scope for a bug report. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470898] resource leak: the number of threads increases over time, boundlessly
https://bugs.kde.org/show_bug.cgi?id=470898 David Edmundson changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||k...@davidedmundson.co.uk Status|REPORTED|NEEDSINFO --- Comment #1 from David Edmundson --- How did you see how many threads were being used? Could you reproduce this with firefox going fullscreen and back? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 465191] Dozens to hunderts of kioslave crashed warnings until Plama crashes
https://bugs.kde.org/show_bug.cgi?id=465191 --- Comment #8 from Uwe Köhler --- As stated before, no further information can be provided, since this is a architecture bug. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 461887] libpoppler-glib8 as shipped in Neon breaks Inkscape PDF import
https://bugs.kde.org/show_bug.cgi?id=461887 --- Comment #7 from Louis Moureaux --- I'm afraid this will never be fixed, it's apparently a policy that breaking Gtk apps is fine. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 465004] No interactive manipulation of transform effect
https://bugs.kde.org/show_bug.cgi?id=465004 Uwe Köhler changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #8 from Uwe Köhler --- Still disabled by default after recent update, but can be activated now via option in its toolbar to Show/Hide the edit controls -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 465003] Menus in top right corner of clip and project view missing
https://bugs.kde.org/show_bug.cgi?id=465003 Uwe Köhler changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Uwe Köhler --- Fixed after recent update -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 463601] Inkscape user interface brocken
https://bugs.kde.org/show_bug.cgi?id=463601 Uwe Köhler changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Uwe Köhler --- Fixed after recent update -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470012] Hovering icons in Icons-Only Task Manager on Wayland results in slow preview transitions, incorrect positions
https://bugs.kde.org/show_bug.cgi?id=470012 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467426] Often wrong window preview shown on hover
https://bugs.kde.org/show_bug.cgi?id=467426 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 461887] libpoppler-glib8 as shipped in Neon breaks Inkscape PDF import
https://bugs.kde.org/show_bug.cgi?id=461887 --- Comment #6 from Uwe Köhler --- Still broken after recent update. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 469462] No drag and drop to the timeline on Fedora 38 with Appimage
https://bugs.kde.org/show_bug.cgi?id=469462 mBetar changed: What|Removed |Added Resolution|DUPLICATE |FIXED --- Comment #8 from mBetar --- The issue has been resolved with the latest Mutter 44.2 on Fedora 38. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 469462] No drag and drop to the timeline on Fedora 38 with Appimage
https://bugs.kde.org/show_bug.cgi?id=469462 --- Comment #7 from mBetar --- The issue has been resolved with the latest `mutter 44.2`. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 470717] KDE Neon doesn't update
https://bugs.kde.org/show_bug.cgi?id=470717 --- Comment #2 from Uwe Köhler --- Many thanks, got lots of packages updated. However, the documentation explicitly states not to use apt for package management. That is very confusing. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 469431] Need better way to handle changes in stock price quote source
https://bugs.kde.org/show_bug.cgi?id=469431 bryan.williams7...@gmail.com changed: What|Removed |Added CC||bryan.williams7...@gmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 453756] Location bar resets after several seconds when typing
https://bugs.kde.org/show_bug.cgi?id=453756 --- Comment #26 from Tracy Poff --- I also run docker. Lots of different containers (postgres, nginx, …), though not that zerotier one. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 470910] Trying to open applications or get applications through discover or even other applications outside of Discover, all come up with the error: "no metadata URIs for vendor-direc
https://bugs.kde.org/show_bug.cgi?id=470910 --- Comment #4 from Antonio Rojas --- (In reply to Nicolas Fella from comment #3) > @Antonio can you please clarify whether Arch does something special wrt > appstream here? No, appstream generator also indexes desktop files for applications that don't provide appstream data (such as kdeconnect-app). I guess Fedora has this disabled. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 470880] Crash while opening .nef raw image
https://bugs.kde.org/show_bug.cgi?id=470880 --- Comment #2 from David Strobach --- (In reply to Nicolas Fella from comment #1) > Can you attach one of the affected files? Nope, not really, because of the size limit. You can, however, download it here: https://mega.nz/file/j3RGELSa#wMs5nJ-HlrMZrjytiC9NkESXF6TRIIVzPDlZsa-uI3E -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 424782] org.kde.kdeconnect_open.desktop: does not pass validation w/ multiple invalid values (was: invalid mime type)
https://bugs.kde.org/show_bug.cgi?id=424782 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/network/kdeconnect-kde/-/merge_requests/553 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467574] kwin_screencast: Dropping a screencast frame because the compositor is slow
https://bugs.kde.org/show_bug.cgi?id=467574 --- Comment #15 from Aleix Pol --- Please note that kwin taking 100% CPU here is not this bug, please open a separate one and we'll discuss how to debug it there. -- You are receiving this mail because: You are watching all bug changes.
