[krita] [Bug 457937] when making line will delay
https://bugs.kde.org/show_bug.cgi?id=457937 Halla Rempt changed: What|Removed |Added CC||ha...@valdyas.org Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Halla Rempt --- You likely enabled the stabilizer in the freehand tool options widget. To learn how to make bug reports, please go to https://docs.krita.org/en/untranslatable_pages/reporting_bugs.html. For user support, which is what you need, go to krita-artists.org. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457917] Krita crashes after opening the fill layer properties.
https://bugs.kde.org/show_bug.cgi?id=457917 --- Comment #2 from Halla Rempt --- I cannot reproduce this with the 5.1.0 RC1 appimage. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457934] Krita 4.2.6 stops working with brush tool after a specific set of time
https://bugs.kde.org/show_bug.cgi?id=457934 Halla Rempt changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REPORTED|RESOLVED CC||ha...@valdyas.org --- Comment #1 from Halla Rempt --- Sorry, we don't provide bug fixes for a version of Krita that's that old. We're releasing 5.1.0 this week... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457844] Applications are launched with shortcuts have cap_sys_nice=eip capabilities
https://bugs.kde.org/show_bug.cgi?id=457844 --- Comment #7 from Vlad Zahorodnii --- > cap_sys_nice=eip capabilities Hmm, the fact that cap_sys_nice is in the inheritable set is unexpected. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457903] no metadata in information panel
https://bugs.kde.org/show_bug.cgi?id=457903 --- Comment #2 from Roberto --- (In reply to Nate Graham from comment #1) > Do you have file indexing turned off in System Settings > Search > File > Search? I typically do not use it, but I've tried to enable it and it does not help. On my laptop (kubuntu devel) there is no need to enable baloo to get the metadata shown. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 447854] CONSISTENT RENDER CRASH - 100% of the time - right at the end of rendering
https://bugs.kde.org/show_bug.cgi?id=447854 --- Comment #10 from Andrey --- More info: I am rendering using the standard MP4-H264/AAC template but changing it to WebM or anything else or creating a custom one does not help. Parallel Processing is on, 16 threads (CPU is Ryzen with 8 cores). I suspect that turning Parallel Processing off may help (or not?), I can't test it properly because rendering becomes impossibly slow because of the sheer amount of effects I am using on the 4K video. -- You are receiving this mail because: You are watching all bug changes.
[colord-kde] [Bug 457942] New: Colord-kde missing in multiple distros
https://bugs.kde.org/show_bug.cgi?id=457942 Bug ID: 457942 Summary: Colord-kde missing in multiple distros Product: colord-kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Systems Settings Module (KCM) Assignee: dantt...@gmail.com Reporter: dannys...@live.com Target Milestone: --- SUMMARY I noticed colord-kde isn't packaged in a few distros, is there any plans to include this in any of the main KDE packages so the KDE experience is consistent between distros? Many of the mainstream distros include a separate standalone package to install colord-kde while some other distros refuse to package it due to the age of the last git tag and request a new release. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 447854] CONSISTENT RENDER CRASH - 100% of the time - right at the end of rendering
https://bugs.kde.org/show_bug.cgi?id=447854 Andrey changed: What|Removed |Added CC||meges...@efenstor.net --- Comment #9 from Andrey --- Having the same issue with the 22.04.3 and the nightly as well. Flatpak builds are the most troublesome, the AppImage seems more stable but I had one such crash there also. Starting the render again right after the crash without touching anything seems to help in some cases. The input clips are all H264 4K, the project is also 4K 23.96 fps. I am using proxies on all clips and lots of effects (Bezier Curves, Vignette, Deband, Video noise generator, LUT to name a few) on clips and tracks but none on the Master. By the way, Vignette (not Vignette Effect) often behaves abnormally on the beginning of a clip - first couple of frames contain no effect, then it appears but shrunk (i.e. the frame is almost black except for the center) for one frame, and after that it is normal. -- You are receiving this mail because: You are watching all bug changes.
[kalendar] [Bug 457941] New: calandar notifications still crashing
https://bugs.kde.org/show_bug.cgi?id=457941 Bug ID: 457941 Summary: calandar notifications still crashing Product: kalendar Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: claudio.cam...@gmail.com Reporter: mathias.hom...@opensuse.org CC: c...@carlschwan.eu Target Milestone: --- Application: kalendarac (5.20.3) Qt Version: 5.15.5 Frameworks Version: 5.96.0 Operating System: Linux 5.19.1-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: still the same: i dismiss a calendar notification and i get drkonqi. The crash can be reproduced sometimes. -- Backtrace: Application: Erinnerungen (kalendarac), signal: Segmentation fault [KCrash Handler] #4 std::__atomic_base::load (__m=, this=, this=, __m=) at /usr/include/c++/12/bits/atomic_base.h:486 #5 QAtomicOps::loadRelaxed (_q_value=..., _q_value=...) at /usr/include/qt5/QtCore/qatomic_cxx11.h:239 #6 QBasicAtomicInteger::loadRelaxed (this=0x7f1ed25cd954) at /usr/include/qt5/QtCore/qbasicatomic.h:107 #7 QWeakPointer::internalData (this=0x5625eff302b0) at /usr/include/qt5/QtCore/qsharedpointer_impl.h:698 #8 QPointer::data (this=0x5625eff302b0) at /usr/include/qt5/QtCore/qpointer.h:77 #9 QPointer::operator KNotification* (this=0x5625eff302b0) at /usr/include/qt5/QtCore/qpointer.h:83 #10 AlarmNotification::~AlarmNotification (this=, this=) at /usr/src/debug/akonadi-calendar-22.04.3-1.1.x86_64/reminder-daemon/alarmnotification.cpp:23 #11 KalendarAlarmClient::dismiss (this=0x7ffc13c67720, notification=0x5625eff302b0) at /usr/src/debug/akonadi-calendar-22.04.3-1.1.x86_64/reminder-daemon/kalendaralarmclient.cpp:120 #12 0x7f1bc4112e6f in QtPrivate::QSlotObjectBase::call (a=0x7ffc13c66ce0, r=0x7ffc13c67720, this=0x5625eff2b4b0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #13 doActivate (sender=0x5625eff7c650, signal_index=9, argv=0x7ffc13c66ce0) at kernel/qobject.cpp:3886 #14 0x7f1bc410c22f in QMetaObject::activate (sender=sender@entry=0x5625eff7c650, m=m@entry=0x7f1bc50ec6a0, local_signal_index=local_signal_index@entry=6, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #15 0x7f1bc50b4903 in KNotification::closed (this=this@entry=0x5625eff7c650) at /usr/src/debug/knotifications-5.96.0-1.1.x86_64/build/src/KF5Notifications_autogen/EWIEGA46WW/moc_knotification.cpp:582 #16 0x7f1bc50b7817 in KNotification::textChanged (this=0x5625eff7c650) at /usr/src/debug/knotifications-5.96.0-1.1.x86_64/src/knotification.cpp:358 #17 0x7f1bc4112e6f in QtPrivate::QSlotObjectBase::call (a=0x7ffc13c66e10, r=0x7f1bc50ee060 <(anonymous namespace)::Q_QGS_s_self::innerFunction()::holder>, this=0x5625effacb20) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #18 doActivate (sender=0x5625effad9a0, signal_index=3, argv=0x7ffc13c66e10) at kernel/qobject.cpp:3886 #19 0x7f1bc410c22f in QMetaObject::activate (sender=, m=m@entry=0x7f1bc50ec620 , local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffc13c66e10) at kernel/qobject.cpp:3946 #20 0x7f1bc50b4aef in KNotificationPlugin::finished (this=, _t1=) at /usr/src/debug/knotifications-5.96.0-1.1.x86_64/build/src/KF5Notifications_autogen/EWIEGA46WW/moc_knotificationplugin.cpp:173 #21 0x7f1bc50cb891 in NotifyByPopup::onNotificationClosed (this=0x5625effad9a0, dbus_id=, reason=3) at /usr/src/debug/knotifications-5.96.0-1.1.x86_64/src/notifybypopup.cpp:150 #22 0x7f1bc4112e6f in QtPrivate::QSlotObjectBase::call (a=0x7ffc13c66fe0, r=0x5625effad9a0, this=0x5625effaf1b0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #23 doActivate (sender=0x5625effad9d8, signal_index=5, argv=0x7ffc13c66fe0) at kernel/qobject.cpp:3886 #24 0x7f1bc410c22f in QMetaObject::activate (sender=, m=, local_signal_index=local_signal_index@entry=2, argv=argv@entry=0x7ffc13c66fe0) at kernel/qobject.cpp:3946 #25 0x7f1bc50d7599 in OrgFreedesktopNotificationsInterface::NotificationClosed (_t2=, _t1=, this=) at /usr/src/debug/knotifications-5.96.0-1.1.x86_64/build/src/notifications_interface.moc:287 #26 OrgFreedesktopNotificationsInterface::qt_static_metacall (_o=_o@entry=0x5625effad9d8, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=2, _a=_a@entry=0x7ffc13c67130) at /usr/src/debug/knotifications-5.96.0-1.1.x86_64/build/src/notifications_interface.moc:148 #27 0x7f1bc50d7f83 in OrgFreedesktopNotificationsInterface::qt_metacall (this=0x5625effad9d8, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0x7ffc13c67130) at /usr/src/debug/knotifications-5.96.0-1.1.x86_64/build/src/notifications_interface.moc:242 #28 0x7f1bc4b6056b in QDBusConnectionPrivate::deliverCall (this=, object=, msg=..., metaTypes=..., s
[krita] [Bug 457917] Krita crashes after opening the fill layer properties.
https://bugs.kde.org/show_bug.cgi?id=457917 Halla Rempt changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||ha...@valdyas.org Resolution|--- |WAITINGFORINFO --- Comment #1 from Halla Rempt --- Please install the debug symbols packages and attach the backtrace to this report. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 446468] Selected folder icon becomes white in selected list items
https://bugs.kde.org/show_bug.cgi?id=446468 --- Comment #21 from gianluca.pettine...@gmail.com --- Another side effect of the bug is that when you are editing a line in dolphin, all the other fields become white on white ie invisible. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376345] can't disable "auto spell check" while editing metadata
https://bugs.kde.org/show_bug.cgi?id=376345 --- Comment #5 from caulier.gil...@gmail.com --- Git commit 1df6bb1dd102230858e657cca219dbc888e77319 by Gilles Caulier. Committed on 16/08/2022 at 05:51. Pushed by cgilles into branch 'master'. Add 2 new classes to host spell check settings M +2-0core/libs/widgets/CMakeLists.txt A +67 -0core/libs/widgets/text/spellcheckcontainer.cpp [License: GPL (v2+)] A +66 -0core/libs/widgets/text/spellcheckcontainer.h [License: GPL (v2+)] A +140 -0core/libs/widgets/text/spellchecksettings.cpp [License: GPL (v2+)] A +83 -0core/libs/widgets/text/spellchecksettings.h [License: GPL (v2+)] https://invent.kde.org/graphics/digikam/commit/1df6bb1dd102230858e657cca219dbc888e77319 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457855] [Nvidia Wayland] Max Refresh rate is Smaller than Display
https://bugs.kde.org/show_bug.cgi?id=457855 --- Comment #2 from nekone...@protonmail.ch --- How do I produce this output? -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 457940] New: Resize title bar abnormal, strange ratio
https://bugs.kde.org/show_bug.cgi?id=457940 Bug ID: 457940 Summary: Resize title bar abnormal, strange ratio Product: Active Window Control Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: zrenf...@gmail.com Reporter: r...@pluvet.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 151349 --> https://bugs.kde.org/attachment.cgi?id=151349&action=edit see the title bar SUMMARY STEPS TO REPRODUCE 1. No 100% way to reproduce, but with following operations, its possible to trigger 2. Open some VSCode Window 3. Resize window 4. Let computer sleep 5. Awake, and resize window OBSERVED RESULT Strange window border EXPECTED RESULT Show be resized 1:1 SOFTWARE/OS VERSIONS Linux/KDE Plasma: x86_64 Linux 5.18.16-arch1-1 KDE Plasma Version: Plasma 5.25.4 KDE Frameworks Version: KDE 5.96.0 Qt Version: QMake version 3.1 Using Qt version 6.3.1 in /usr/lib QMake version 3.1 Using Qt version 5.15.5 in /usr/lib -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 457900] 2 minute delay in updating AC status in system tray
https://bugs.kde.org/show_bug.cgi?id=457900 --- Comment #2 from arno --- I guess that's why I'm not running Plasma on wla C64 🙂 > On 16/08/2022, at 5:39 AM, Nate Graham wrote: > > https://bugs.kde.org/show_bug.cgi?id=457900 > > Nate Graham changed: > > What|Removed |Added > > CC||n...@kde.org > > --- Comment #1 from Nate Graham --- > Works as expected with my ThinkPad X1 Yoga. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457899] System Settign crashes when changing system setting
https://bugs.kde.org/show_bug.cgi?id=457899 --- Comment #4 from Mohan Dash --- Today also the system setting closed unexpectedly. While accessing the Input Devices in system settings. The backtrace content are as below Application: System Settings (systemsettings), signal: Aborted [KCrash Handler] #4 0x7f12386e84dc in ?? () from /usr/lib/libc.so.6 #5 0x7f1238698998 in raise () from /usr/lib/libc.so.6 #6 0x7f123868253d in abort () from /usr/lib/libc.so.6 #7 0x7f12386dc67e in ?? () from /usr/lib/libc.so.6 #8 0x7f12387775da in __fortify_fail () from /usr/lib/libc.so.6 #9 0x7f12387775a6 in __stack_chk_fail () from /usr/lib/libc.so.6 #10 0x7f1236ade92b in ?? () from /usr/lib/libQt5Qml.so.5 #11 0x7f1236ae5e8b in QV4::QObjectWrapper::virtualResolveLookupGetter(QV4::Object const*, QV4::ExecutionEngine*, QV4::Lookup*) () from /usr/lib/libQt5Qml.so.5 #12 0x7f1236afabea in ?? () from /usr/lib/libQt5Qml.so.5 #13 0x7f1236b04e34 in ?? () from /usr/lib/libQt5Qml.so.5 #14 0x7f1236aa87f6 in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /usr/lib/libQt5Qml.so.5 #15 0x7f1236bfce6d in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /usr/lib/libQt5Qml.so.5 #16 0x7f1236bc0121 in QQmlBoundSignalExpression::evaluate(void**) () from /usr/lib/libQt5Qml.so.5 #17 0x7f1236bc109c in ?? () from /usr/lib/libQt5Qml.so.5 #18 0x7f1236be38cf in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /usr/lib/libQt5Qml.so.5 #19 0x7f1238d3ce6d in ?? () from /usr/lib/libQt5Core.so.5 #20 0x7f12370666d9 in ?? () from /usr/lib/libQt5Quick.so.5 #21 0x7f1237067eb9 in QQuickItemView::setCurrentIndex(int) () from /usr/lib/libQt5Quick.so.5 #22 0x7f1236ba90c2 in ?? () from /usr/lib/libQt5Qml.so.5 #23 0x7f1236bfe915 in ?? () from /usr/lib/libQt5Qml.so.5 #24 0x7f1236c0608e in ?? () from /usr/lib/libQt5Qml.so.5 #25 0x7f1236c05b73 in QQmlBinding::update(QFlags) () from /usr/lib/libQt5Qml.so.5 #26 0x7f1236be38cf in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /usr/lib/libQt5Qml.so.5 #27 0x7f1238d3ce6d in ?? () from /usr/lib/libQt5Core.so.5 #28 0x7f121c0411ed in ?? () from /usr/lib/qt/plugins/systemsettingsview/systemsettings_sidebar_mode.so #29 0x7f121c041e43 in ?? () from /usr/lib/qt/plugins/systemsettingsview/systemsettings_sidebar_mode.so #30 0x7f1236be3994 in ?? () from /usr/lib/libQt5Qml.so.5 #31 0x7f1236ae796c in ?? () from /usr/lib/libQt5Qml.so.5 #32 0x7f1236ae8f6d in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () from /usr/lib/libQt5Qml.so.5 #33 0x7f1236afb033 in ?? () from /usr/lib/libQt5Qml.so.5 #34 0x7f1236b04e34 in ?? () from /usr/lib/libQt5Qml.so.5 #35 0x7f1236aa87f6 in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /usr/lib/libQt5Qml.so.5 #36 0x7f1236bfce6d in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /usr/lib/libQt5Qml.so.5 #37 0x7f1236bc0121 in QQmlBoundSignalExpression::evaluate(void**) () from /usr/lib/libQt5Qml.so.5 #38 0x7f1236bc109c in ?? () from /usr/lib/libQt5Qml.so.5 #39 0x7f1236be38cf in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /usr/lib/libQt5Qml.so.5 #40 0x7f1238d3ce6d in ?? () from /usr/lib/libQt5Core.so.5 #41 0x7f1232457a5a in QQuickAbstractButtonPrivate::handleRelease(QPointF const&) () from /usr/lib/libQt5QuickTemplates2.so.5 #42 0x7f1232472ab9 in QQuickControl::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libQt5QuickTemplates2.so.5 #43 0x7f1236fad1c9 in QQuickItem::event(QEvent*) () from /usr/lib/libQt5Quick.so.5 #44 0x7f1239894b3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #45 0x7f1238d0cad8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #46 0x7f1236fbdd93 in QQuickWindowPrivate::deliverMouseEvent(QQuickPointerMouseEvent*) () from /usr/lib/libQt5Quick.so.5 #47 0x7f1236fbe7f2 in QQuickWindowPrivate::deliverPointerEvent(QQuickPointerEvent*) () from /usr/lib/libQt5Quick.so.5 #48 0x7f1239209b45 in QWindow::event(QEvent*) () from /usr/lib/libQt5Gui.so.5 #49 0x7f1239894b3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #50 0x7f1238d0cad8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #51 0x7f12372f6cae in QQuickWidget::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libQt5QuickWidgets.so.5 #52 0x7f12398cb707 in QWidget::event(QEvent*) () from /usr/lib/libQt5Widgets.so.5 #53 0x7f1239894b3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #54 0x7f123989a359 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #55 0x7f1238d0cad8 in QCore
[systemsettings] [Bug 457899] System Settign crashes when changing system setting
https://bugs.kde.org/show_bug.cgi?id=457899 --- Comment #3 from Mohan Dash --- (In reply to Nicolas Fella from comment #1) > The crash originates in the "Camera" section. Did you do anything in there? I was just checking the Removable device section. Nothing changed or edited. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457351] [krita] lags during work and a problem with adding resources
https://bugs.kde.org/show_bug.cgi?id=457351 --- 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.
[systemsettings] [Bug 457342] Flatpak Apps lose GTK theming after restart
https://bugs.kde.org/show_bug.cgi?id=457342 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 456477] reset Snap to Assistants
https://bugs.kde.org/show_bug.cgi?id=456477 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 456417] Translucency
https://bugs.kde.org/show_bug.cgi?id=456417 --- Comment #7 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456458] Cursor keeps disappearing! Disappears when moving from desktop to the taskbar. Changes from a normal 'arrow' to a 'hand' or some other icon. This started with the previous
https://bugs.kde.org/show_bug.cgi?id=456458 --- 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.
[kdenlive] [Bug 457878] Kdenlive ignores more than one space in the subtitles.
https://bugs.kde.org/show_bug.cgi?id=457878 Eric Jiang changed: What|Removed |Added Assignee|vpi...@kde.org |erji...@alumni.iu.edu -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 457878] Kdenlive ignores more than one space in the subtitles.
https://bugs.kde.org/show_bug.cgi?id=457878 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/multimedia/kdenlive/-/merge_requests/340 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457939] New: Crash when opening "Configure "Desktop and Wallpaper..." from desktop.
https://bugs.kde.org/show_bug.cgi?id=457939 Bug ID: 457939 Summary: Crash when opening "Configure "Desktop and Wallpaper..." from desktop. Product: systemsettings Version: 5.25.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: cgoh...@gmail.com Target Milestone: --- Application: systemsettings (5.25.4) Qt Version: 5.15.5 Frameworks Version: 5.97.0 Operating System: Linux 5.19.1-arch2-1 x86_64 Windowing System: X11 Distribution: "Arch Linux" DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: Crash when opening "Configure "Desktop and Wallpaper..." from desktop context menu. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: System Settings (systemsettings), signal: Aborted [KCrash Handler] #4 0x7f38770a14dc in ?? () from /usr/lib/libc.so.6 #5 0x7f3877051998 in raise () from /usr/lib/libc.so.6 #6 0x7f387703b53d in abort () from /usr/lib/libc.so.6 #7 0x7f387709567e in ?? () from /usr/lib/libc.so.6 #8 0x7f38771305da in __fortify_fail () from /usr/lib/libc.so.6 #9 0x7f38771305a6 in __stack_chk_fail () from /usr/lib/libc.so.6 #10 0x7f387577192b in ?? () from /usr/lib/libQt5Qml.so.5 #11 0x7f3875778e8b in QV4::QObjectWrapper::virtualResolveLookupGetter(QV4::Object const*, QV4::ExecutionEngine*, QV4::Lookup*) () from /usr/lib/libQt5Qml.so.5 #12 0x7f387578dbea in ?? () from /usr/lib/libQt5Qml.so.5 #13 0x7f3875797e34 in ?? () from /usr/lib/libQt5Qml.so.5 #14 0x7f387573b7f6 in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () from /usr/lib/libQt5Qml.so.5 #15 0x7f387588fe6d in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () from /usr/lib/libQt5Qml.so.5 #16 0x7f3875853121 in QQmlBoundSignalExpression::evaluate(void**) () from /usr/lib/libQt5Qml.so.5 #17 0x7f387585409c in ?? () from /usr/lib/libQt5Qml.so.5 #18 0x7f38758768cf in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /usr/lib/libQt5Qml.so.5 #19 0x7f38778bce6d in ?? () from /usr/lib/libQt5Core.so.5 #20 0x7f3875ef56d9 in ?? () from /usr/lib/libQt5Quick.so.5 #21 0x7f3875ef6eb9 in QQuickItemView::setCurrentIndex(int) () from /usr/lib/libQt5Quick.so.5 #22 0x7f387583c0c2 in ?? () from /usr/lib/libQt5Qml.so.5 #23 0x7f3875891915 in ?? () from /usr/lib/libQt5Qml.so.5 #24 0x7f387589908e in ?? () from /usr/lib/libQt5Qml.so.5 #25 0x7f3875898b73 in QQmlBinding::update(QFlags) () from /usr/lib/libQt5Qml.so.5 #26 0x7f38758768cf in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /usr/lib/libQt5Qml.so.5 #27 0x7f38778bce6d in ?? () from /usr/lib/libQt5Core.so.5 #28 0x7f3870019fc8 in ?? () from /usr/lib/qt/plugins/systemsettingsview/systemsettings_sidebar_mode.so #29 0x7f387001b46d in ?? () from /usr/lib/qt/plugins/systemsettingsview/systemsettings_sidebar_mode.so #30 0x7f387001bba1 in ?? () from /usr/lib/qt/plugins/systemsettingsview/systemsettings_sidebar_mode.so #31 0x55d2e3542bd0 in ?? () #32 0x55d2e3545e24 in ?? () #33 0x7f38778b0440 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5 #34 0x7f38790882ae in KXmlGuiWindow::event(QEvent*) () from /usr/lib/libKF5XmlGui.so.5 #35 0x7f3878578b3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5 #36 0x7f387788cad8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5 #37 0x7f387788d5e3 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQt5Core.so.5 #38 0x7f38778d3548 in ?? () from /usr/lib/libQt5Core.so.5 #39 0x7f38761dec6b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #40 0x7f3876235001 in ?? () from /usr/lib/libglib-2.0.so.0 #41 0x7f38761dc392 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #42 0x7f38778d732c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQt5Core.so.5 #43 0x7f387788527c in QEventLoop::exec(QFlags) () from /usr/lib/libQt5Core.so.5 #44 0x7f387788fda9 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5 #45 0x55d2e353cb7a in ?? () #46 0x7f387703c2d0 in ?? () from /usr/lib/libc.so.6 #47 0x7f387703c38a in __libc_start_main () from /usr/lib/libc.so.6 #48 0x55d2e353d4d5 in ?? () [Inferior 1 (process 143966) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450448] Scrolling with touchscreen does not work consistently
https://bugs.kde.org/show_bug.cgi?id=450448 Noah Davis changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-desktop/commit/66 ||507b5df163071128a90983d10f6 ||99aa1a9b3cf Resolution|--- |FIXED --- Comment #8 from Noah Davis --- Git commit 66507b5df163071128a90983d10f699aa1a9b3cf by Noah Davis. Committed on 16/08/2022 at 03:01. Pushed by ndavis into branch 'master'. Disable Drag and Drop for touch, fix drag and drop icons Drag and drop conflicted with drag/flick scrolling and drag and drop was deemed less important than scrolling or opening the context menu for touch. Maybe in the future we can have a way to at least rearrange favorites with touch input. Drag and drop icons seem to have been broken by commit 0868a5ae8154d10ccc7488034bc5b6e458a17968 and are now fixed. M +15 -12 applets/kickoff/package/contents/ui/AbstractKickoffItemDelegate.qml M +3-0applets/kickoff/package/contents/ui/KickoffGridDelegate.qml M +2-0applets/kickoff/package/contents/ui/KickoffListDelegate.qml https://invent.kde.org/plasma/plasma-desktop/commit/66507b5df163071128a90983d10f699aa1a9b3cf -- You are receiving this mail because: You are watching all bug changes.
[kdesvn] [Bug 457938] New: feature request: rename multiple files
https://bugs.kde.org/show_bug.cgi?id=457938 Bug ID: 457938 Summary: feature request: rename multiple files Product: kdesvn Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: kdesvn-bugs-n...@kde.org Reporter: da...@trefle.ru Target Milestone: --- Windows TortoiseSVN has a good feature: when refactoring, multiple files have to be renamed at once because those files belong together. e.g. file.aspx, file.aspx.cs, file.aspx.resx Please implement the same feature in KDESvn. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 401677] Some phone models, ROMs or Apps don't report SMS History
https://bugs.kde.org/show_bug.cgi?id=401677 Simon Redman changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #113 from Simon Redman --- Making as resolved since nobody appears to be having problems post my workaround. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457937] New: when making line will delay
https://bugs.kde.org/show_bug.cgi?id=457937 Bug ID: 457937 Summary: when making line will delay Product: krita Version: unspecified Platform: Microsoft Windows OS: Other Status: REPORTED Severity: normal Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: morgannh2...@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. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 PC macOS: N/A Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I'm sorry I have no real idea on how to report a bug here, since I just downloaded Krita. So, any time I write on my Huion tablet to draw, the line is either delayed or will only put a dot. I've already tried to see if it was a problem in the brush settings, but I couldn't find anything there. I tried using a different brush thinking that was the problem, but it's still like that. I honestly don't know how to fix this. Also, I'd preferably like it if you'd respond to me through email, MorganNH20092gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457936] New: No response to adjusting sorting mode in Dolphin Settings
https://bugs.kde.org/show_bug.cgi?id=457936 Bug ID: 457936 Summary: No response to adjusting sorting mode in Dolphin Settings Product: dolphin Version: 20.04.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: patrickhedleymil...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY *** Dolphin file manager does not register adjustments to changes made in Settings -> Configure Dolphin -> General -> Sorting mode: Natural vs Alphabetical, case insensitive vs Alphabetical, case sensitive. Sorting mode remains on Alphabetical, case insensitive mode despite adjustment and reboot. *** STEPS TO REPRODUCE 1. Fresh install Arch Linux x86_64 2. Fresh install plasma-meta kde-applications 3. Observe Alphabetical, case insensitive sorting despite adjustments in Settings -> Configure Dolphin OBSERVED RESULT Perseverance of Alphabetical, case insensitive sorting EXPECTED RESULT Natural sorting. SOFTWARE/OS VERSIONS OS: Arch Linux x86_64 Host: MS-7C02 1.0 Kernel: 5.15.60-1-lts Plasma 5.25.4 Dolphin 22.04.3 ADDITIONAL INFORMATION Other threads have mentioned locale settings can cause issues. Current locale output below: LANG=C LC_CTYPE="C" LC_NUMERIC=en_US.UTF-8 LC_TIME=C LC_COLLATE="C" LC_MONETARY=C LC_MESSAGES="C" LC_PAPER="C" LC_NAME="C" LC_ADDRESS="C" LC_TELEPHONE="C" LC_MEASUREMENT=C LC_IDENTIFICATION="C" LC_ALL= Switching to Gnome desktop resolves the issue without adjusting the locale settings. Nautilus applies natural sorting without issue. Expected natural sorting is possible using Plasma Konsole by passing ls -v parameter. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 438174] KDE windows always show on all Activities.
https://bugs.kde.org/show_bug.cgi?id=438174 Eric Edlund changed: What|Removed |Added Resolution|WORKSFORME |FIXED --- Comment #4 from Eric Edlund --- Yeah, Activities hasn't been maintained actively for a while. A bunch of us have gotten together to give it more attention -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457876] All GHNS windows have a title in their header bar, except 'Get new boot splash screens'
https://bugs.kde.org/show_bug.cgi?id=457876 Nate Graham changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/plymouth-kcm/commit/5b8e ||1c359ab2e1826e30411f0ea30b5 ||2111eada6 Status|ASSIGNED|RESOLVED Version Fixed In||5.26 Resolution|--- |FIXED --- Comment #4 from Nate Graham --- Git commit 5b8e1c359ab2e1826e30411f0ea30b52111eada6 by Nate Graham. Committed on 15/08/2022 at 17:20. Pushed by bcooksley into branch 'master'. Add missing Name key to knsrc file Otherwise the GHNS dialog won't show a name in its header. FIXED-IN: 5.26 M +1-0src/plymouth.knsrc https://invent.kde.org/plasma/plymouth-kcm/commit/5b8e1c359ab2e1826e30411f0ea30b52111eada6 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457935] New: Preview does not work for some large ISO files
https://bugs.kde.org/show_bug.cgi?id=457935 Bug ID: 457935 Summary: Preview does not work for some large ISO files Product: dolphin Version: 22.04.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: milas.ro...@live.fr CC: kfm-de...@kde.org Target Milestone: --- Created attachment 151348 --> https://bugs.kde.org/attachment.cgi?id=151348&action=edit Video where you can see that the preview work but does not show on the file ISO File does not show any preview while on the file STEPS TO REPRODUCE 1. Clone and install https://github.com/Hinara/dolphin-retro-thumbnail (my thumbnailer) 2. Enable it and check that previews are enable for file of ~1.4GB 3. Try to preview a Gamecube iso file OBSERVED RESULT The file preview does not work but the parent folder preview of it inner file does work EXPECTED RESULT That the file preview works as well as SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450448] Scrolling with touchscreen does not work consistently
https://bugs.kde.org/show_bug.cgi?id=450448 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #7 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1094 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457912] PlasmaShell is too long to load after boot and crash intermittently after log in
https://bugs.kde.org/show_bug.cgi?id=457912 --- Comment #3 from Ja Koolit --- (In reply to Nate Graham from comment #1) > Does this happen after you've updated your graphics drivers, but before > you've rebooted? If so, does it stop happening after you reboot? Hi Nate, no my gpu drivers was not updated, or there were no update on mesa at that time. I added a plugin (live wallpaper plugins available on store (smart video live wallpaper) and when I add a video for the live wallpaper, I noticed that system hangs for some time. After about a min or less, live wallpaper played but got also a plasmashell crash. I thought about something wrong with plugin, so I downloaded and use other live wallpaper plugin. All same thing.. plug ins I further added are smarter video wallpaper video video lockscreen. All same thing Then I switched to x11 session, live wallpapers are running great with no issues. rebooted, updated drivers, vulkan, mesa etc... nothing helps. Seems like only happening on plasma wayland. Id like to point out though that this only happen on my gentoo-plasma system. my all other plasma distros (Arch and Fedora) does not have these bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457912] PlasmaShell is too long to load after boot and crash intermittently after log in
https://bugs.kde.org/show_bug.cgi?id=457912 --- Comment #2 from Ja Koolit --- Hi Nate, no my gpu drivers was not updated, or there were no update on mesa at that time. I added a plugin (live wallpaper plugins available on store (smart video live wallpaper) and when I add a video for the live wallpaper, I noticed that system hangs for some time. After about a min or less, live wallpaper played but got also a plasmashell crash. I thought about something wrong with plugin, so I downloaded and use other live wallpaper plugin. All same thing.. plug ins I further added are smarter video wallpaper video video lockscreen. All same thing Then I switched to x11 session, live wallpapers are running great with no issues. rebooted, updated drivers, vulkan, mesa etc... nothing helps. Seems like only happening on plasma wayland. Id like to point out though that this only happen on my gentoo-plasma system. my all other plasma distros (Arch and Fedora) does not have these bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 457779] Kde Plasmashell Crashes Sometimes Unrecoverable by Reboot Even
https://bugs.kde.org/show_bug.cgi?id=457779 --- Comment #4 from nssz4...@anonaddy.me --- (In reply to Nate Graham from comment #3) > OK, thanks. Now run `coredumpctl debug 7672`. When it gives you the chance > to type something, type `bt` and then press the enter key. It will output a > bunch of stuff. Paste it here. Here it is: PID: 7672 (plasmashell) UID: 1000 (linux) GID: 1000 (linux) Signal: 11 (SEGV) Timestamp: Thu 2022-08-11 16:03:54 EDT (4 days ago) Command Line: /usr/bin/plasmashell Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-plasmashell-992668215fe946728266b7a514dfab89.scope Unit: user@1000.service User Unit: app-plasmashell-992668215fe946728266b7a514dfab89.scope Slice: user-1000.slice Owner UID: 1000 (linux) Boot ID: 3bfda0d7d76246ef982fa8f4ebe864eb Machine ID: d7582aa864e147d3b82abc881a5b6d1c Hostname: linux-ms7b10 Storage: /var/lib/systemd/coredump/core.plasmashell.1000.3bfda0d7d76246ef982fa8f4ebe864eb.7672.166024823400.zst (missing) Message: Process 7672 (plasmashell) of user 1000 dumped core. Module /usr/lib/libmpfr.so.6.1.0 (deleted) with build-id a0161120648b09097b346a2bc5a7ea91f1ceb6d4 Module /usr/lib/libtiff.so.5.8.0 (deleted) with build-id 31895d2bd133f34f0cdc2d4ac855ed838ec927b6 Module /usr/lib/libmvec.so.1 (deleted) with build-id 2c6aec81c79e91d66940b68be0819fdf780a976c Module /usr/lib/libLLVM-14.so (deleted) with build-id 1a2033d5ab1c892c325fe839c4f45d2d4724fd1f Module /usr/lib/libelf-0.187.so (deleted) with build-id c09e357a1a3b061bf219bcfb243ca31b175e77fa Module /usr/lib/libdl.so.2 (deleted) with build-id 94198b268228074fa9f405bbedbbae94112593ed Module /usr/lib/libresolv.so.2 (deleted) with build-id 89a368a6ad1b392d126a2a5beb9c2f61ade00279 Module /usr/lib/libpthread.so.0 (deleted) with build-id 95ae4f30a6f12ccbff645d30f8e1a3ee23ec7d36 Module /usr/lib/libltdl.so.7.3.2 (deleted) with build-id c4ee3f1ba09fe34163d71ff336756fbecb6f409f Module /usr/lib/libharfbuzz.so.0.50001.0 (deleted) with build-id b7daeb45a60c6cc012417c5cfaa09c91235d06bd Module /usr/lib/libgcc_s.so.1 (deleted) with build-id 0e3de903950e35ae59a5de8c00b1817a4a71ca01 Module /usr/lib/libQt5PrintSupport.so.5.15.5 (deleted) with build-id ff77b9ff81e4a1862b0971c69262668a44ca3dc7 Module /usr/lib/libc.so.6 (deleted) with build-id 60df1df31f02a7b23da83e8ef923359885b81492 Module /usr/lib/libstdc++.so.6.0.30 (deleted) with build-id a24b312bb5881ceae0ffbed599201690f2a1747b Module /usr/lib/libQt5Gui.so.5.15.5 (deleted) with build-id 5dc44434b080822ff6271acce3a21cc1dc08d632 Module /usr/lib/libm.so.6 (deleted) with build-id 1b7296ef9fd806e47060788389293c824b09ad72 Module /usr/lib/libQt5Widgets.so.5.15.5 (deleted) with build-id daaeb7c87490a699b9b5a98577fde1cdc6ed1819 Module ld-linux-x86-64.so.2 with build-id 0effd0e43efa4468d3c31871c93af0b7f3005673 Module linux-vdso.so.1 with build-id e742ac296f3e928fcdf6c0077898e2272659 Module libKF5NotifyConfig.so.5 with build-id 6dc0a15a73e6be6d5d73fe64f9e72986bbd2aa43 Module plasma_engine_notifications.so with build-id 0be1cec001039864987666e3c15f7326fb41186a Module libnss_systemd.so.2 with build-id b95d8a2f92021bc3d82b2b0c1409ac2c696db821 Module kio_file.so with build-id 3071b8bab70596a67c6806ad0832750f3fbb53d8 Module KF5IdleTimeXcbPlugin0.so with build-id 195c24f62fd337b392ef5c7240fc4bc9cfa52a0d Module libprisonquickplugin.so with build-id a4a20cd35bc8c8f1deb4fbda468a42b37ad82b6f Module libbluetoothplugin.so with build-id 1ff89c17d827cd2cf021700963173bff96308954 Module libKF5BluezQt.so.6 with build-id b1da112c6cb72de185025f6098c9e4439451f8b3 Module libbluezqtextensionplugin.so with build-id e2cd79fe4ca605edf368005b76c150d466bcea6c Module libQuickChartsControls.so with build-id 1dda9efb3509f80206cdb33fecf938260ca8cfe0 Module libplc4.so with build-id 2f3f90e73b1f4fc3424689615d6d32f7427bb783 Module libplds4.so with build-id 2b49ec2f43d2e5fc2e56f35bcd094968f9bf36e6 Module libnssutil3.so with build-id 36c34a5ab8de68047e7886fe56da7ccf6722f465 Module libnspr4.so with build-id e54087b0e38cf8936f6c458e922589406343b05d Module libnss3.so with build-id 87abb242025e6e243d6974b3a9da26166884533a Module libsmime3.so with build-id e80b1eacbb0979a1355fd008847c6eef060e83e3 Module libnm.so.0 with build-id 88ce128f6d765e2f017b5501a0a07184bfafc67a Mo
[frameworks-kglobalaccel] [Bug 456958] kglobalshortcutsrc does not propagate via $XDG_CONFIG_DIRS
https://bugs.kde.org/show_bug.cgi?id=456958 --- Comment #10 from Nicolas Fella --- The problem here is somewhat fundamental to the way kglobalaccel works. Therefore I'm very hesitant to just remove the SimpleConfig flag hoping it will fix everything. When a program registers a global shortcut it does that by calling e.g. KGlobalAccel::self()->setGlobalShortcut(). That will register the shortcut and its associated metadata (internal and user-facing name etc) with klgobalacceld. kglobalacceld then saves that information to kglobalshortcutsrc and loads it again on the next start. Any user modifications are also saved to kglobalshortcutsrc. This causes a behavior of kglobalshortcutsrc that is very different to typical config files. Usually when you never changed any particular setting the relevant file in ~/.config is empty and system-wide or buildin defaults apply. But here you will find that .config/kglobalshortcutsrc is always populated with stuff, even if you never changed anything. The current approacj is quite messy and causes problems (such as this). There is the idea of making shortcut definition more declarative by using per-component desktop files (see https://phabricator.kde.org/T12063). This could probably also help with enabling distro customization like you are asking for -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435004] Circular timeout indicator looks bad at fractional scale or when using some non-Breeze icon themes
https://bugs.kde.org/show_bug.cgi?id=435004 Nate Graham changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/commit/ |ma/plasma-workspace/commit/ |e52bfaf9e94193a3f966c4539fc |e462a0e3fcfbbb03dd7ebfc6ff7 |21a9f25fac3ca |b29ef9403e20e --- Comment #6 from Nate Graham --- Git commit e462a0e3fcfbbb03dd7ebfc6ff7b29ef9403e20e by Nate Graham, on behalf of Eugene Popov. Committed on 16/08/2022 at 00:27. Pushed by ngraham into branch 'Plasma/5.24'. applets/notifications: Fix displaying header progress indicator on different DPI Currently, the progress indicator is normally displayed only if the DPI is a multiple of 100; at other DPI values it's almost invisible or not visible at all. This commit fixes that issue. FIXED-IN: 5.24.7 (cherry picked from commit b5f903862e9383a8c7cb6087c1cdb5786c140f7b) M +2-2applets/notifications/package/contents/ui/NotificationHeader.qml https://invent.kde.org/plasma/plasma-workspace/commit/e462a0e3fcfbbb03dd7ebfc6ff7b29ef9403e20e -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435004] Circular timeout indicator looks bad at fractional scale or when using some non-Breeze icon themes
https://bugs.kde.org/show_bug.cgi?id=435004 Nate Graham changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/commit/ |ma/plasma-workspace/commit/ |b5f903862e9383a8c7cb6087c1c |e52bfaf9e94193a3f966c4539fc |db5786c140f7b |21a9f25fac3ca --- Comment #5 from Nate Graham --- Git commit e52bfaf9e94193a3f966c4539fc21a9f25fac3ca by Nate Graham, on behalf of Eugene Popov. Committed on 16/08/2022 at 00:27. Pushed by ngraham into branch 'Plasma/5.25'. applets/notifications: Fix displaying header progress indicator on different DPI Currently, the progress indicator is normally displayed only if the DPI is a multiple of 100; at other DPI values it's almost invisible or not visible at all. This commit fixes that issue. FIXED-IN: 5.24.7 (cherry picked from commit b5f903862e9383a8c7cb6087c1cdb5786c140f7b) M +2-2applets/notifications/package/contents/ui/NotificationHeader.qml https://invent.kde.org/plasma/plasma-workspace/commit/e52bfaf9e94193a3f966c4539fc21a9f25fac3ca -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 435004] Circular timeout indicator looks bad at fractional scale or when using some non-Breeze icon themes
https://bugs.kde.org/show_bug.cgi?id=435004 Nate Graham changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/commit/ ||b5f903862e9383a8c7cb6087c1c ||db5786c140f7b Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||5.24.7 --- Comment #4 from Nate Graham --- Git commit b5f903862e9383a8c7cb6087c1cdb5786c140f7b by Nate Graham, on behalf of Eugene Popov. Committed on 16/08/2022 at 00:25. Pushed by ngraham into branch 'master'. applets/notifications: Fix displaying header progress indicator on different DPI Currently, the progress indicator is normally displayed only if the DPI is a multiple of 100; at other DPI values it's almost invisible or not visible at all. This commit fixes that issue. FIXED-IN: 5.24.7 M +2-2applets/notifications/package/contents/ui/NotificationHeader.qml https://invent.kde.org/plasma/plasma-workspace/commit/b5f903862e9383a8c7cb6087c1cdb5786c140f7b -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 440507] Command-line arguments specified in exec= line get removed
https://bugs.kde.org/show_bug.cgi?id=440507 Nate Graham changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/kglobalaccel/commit/ ||625b53f516d27eb61eaad00175d ||d7108bf82572f Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||5.98 --- Comment #10 from Nate Graham --- Git commit 625b53f516d27eb61eaad00175dd7108bf82572f by Nate Graham, on behalf of Nicolas Fella. Committed on 16/08/2022 at 00:12. Pushed by ngraham into branch 'master'. Don't pass Exec arguments to kstart when launching via desktop entry name If we have a desktop file org.kde.foo.desktop with "Exec=foo bar bla" we are currently calling "kstart5 --application org.kde.foo bar bla" However we need to call "kstart5 --application org.kde.foo" without any args kstart5/ApplicationLauncherJob will read the Exec line again and pick up the args FIXED-IN: 5.98 M +2-3src/runtime/kserviceactioncomponent.cpp https://invent.kde.org/frameworks/kglobalaccel/commit/625b53f516d27eb61eaad00175dd7108bf82572f -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 457785] Kate is extremely slow to exit
https://bugs.kde.org/show_bug.cgi?id=457785 --- Comment #8 from Aaron Williams --- Yes. Any changes to the settings of Kate do not seem to take hold. Note that I had numerous instances of Kate running. I was able to fix this by logging out and deleting ~/.local/share/kate/anonymous.katesession. If other instances of kate are running, settings do not take effect. -- You are receiving this mail because: You are watching all bug changes.
[Reminder Daemon] [Bug 453805] Text of event reminders does not use local timezone
https://bugs.kde.org/show_bug.cgi?id=453805 David E. Narvaez changed: What|Removed |Added CC||david.narv...@computer.org --- Comment #1 from David E. Narvaez --- Forget about the timezone: it does not even say what day the event is. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 438174] KDE windows always show on all Activities.
https://bugs.kde.org/show_bug.cgi?id=438174 michael changed: What|Removed |Added Status|NEEDSINFO |RESOLVED --- Comment #3 from michael --- This specific issue seems to be fixed. Session restore still isn't fully operational so windows don't show up again if you logout or show up in some default position. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 440507] Command-line arguments specified in exec= line get removed
https://bugs.kde.org/show_bug.cgi?id=440507 Nate Graham changed: What|Removed |Added CC||poperi...@mailbox.org --- Comment #9 from Nate Graham --- *** Bug 457932 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 457932] Shortcuts for opening WezTerm no longer work
https://bugs.kde.org/show_bug.cgi?id=457932 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|ASSIGNED|RESOLVED --- Comment #10 from Nate Graham --- *** This bug has been marked as a duplicate of bug 440507 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 440507] Command-line arguments specified in exec= line get removed
https://bugs.kde.org/show_bug.cgi?id=440507 Nate Graham changed: What|Removed |Added CC||philippe.roub...@free.fr --- Comment #7 from Nate Graham --- *** Bug 456972 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 440507] Command-line arguments specified in exec= line get removed
https://bugs.kde.org/show_bug.cgi?id=440507 Nate Graham changed: What|Removed |Added CC||lu...@lwsabota.com --- Comment #8 from Nate Graham --- *** Bug 456589 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kstart] [Bug 456589] Launching application via keyboard shortcut fails when when said app's .desktop entry contains arguments
https://bugs.kde.org/show_bug.cgi?id=456589 Nate Graham changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||n...@kde.org --- Comment #4 from Nate Graham --- *** This bug has been marked as a duplicate of bug 440507 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 456972] custom shortcut, does not work anymore
https://bugs.kde.org/show_bug.cgi?id=456972 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #19 from Nate Graham --- *** This bug has been marked as a duplicate of bug 440507 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 457934] New: Krita 4.2.6 stops working with brush tool after a specific set of time
https://bugs.kde.org/show_bug.cgi?id=457934 Bug ID: 457934 Summary: Krita 4.2.6 stops working with brush tool after a specific set of time Product: krita Version: unspecified Platform: Other OS: Microsoft Windows Status: REPORTED Severity: task Priority: NOR Component: Brush Engine/Bristle Assignee: krita-bugs-n...@kde.org Reporter: starwarfa...@gmail.com Target Milestone: --- SUMMARY *** When using the brush tool, it ceases to function in any capacity after a set amount of time of using it between using other tools. Trying to change brush color, change layers or even try to use alternate tools such as the shape tool produces no result. It forces the user to stop whatever they are doing and close the program completely in order to solve the issue but this is only a temporary solution as the issue repeats itself. The time in which it takes for this issue to happen is undetermined as it sometimes happens within the first 20 minutes or could work fine for hours without signs and then suddenly stop working. *** STEPS TO REPRODUCE unknown OBSERVED RESULT Brush tool ceases functionality after a set amount of time that seems to be randomized each time that the program is closed and rebooted up. EXPECTED RESULT n/a SOFTWARE/OS VERSIONS Windows 10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457933] New: system settings crashed trying to open autostart page
https://bugs.kde.org/show_bug.cgi?id=457933 Bug ID: 457933 Summary: system settings crashed trying to open autostart page Product: systemsettings Version: 5.25.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: mariusz.lib...@gmail.com Target Milestone: --- Application: systemsettings (5.25.4) Qt Version: 5.15.5 Frameworks Version: 5.97.0 Operating System: Linux 5.19.1-arch2-1 x86_64 Windowing System: X11 Distribution: "Arch Linux" DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: 1. open system setttings 2. search for 'autostart' 3. click the 'autostart' search result 4. crash when I tried it again I couldn't reproduce the crash The reporter is unsure if this crash is reproducible. -- Backtrace: Application: System Settings (systemsettings), signal: Aborted [KCrash Handler] #4 0x7fe7890a14dc in () at /usr/lib/libc.so.6 #5 0x7fe789051998 in raise () at /usr/lib/libc.so.6 #6 0x7fe78903b53d in abort () at /usr/lib/libc.so.6 #7 0x7fe78909567e in () at /usr/lib/libc.so.6 #8 0x7fe7891305da in __fortify_fail () at /usr/lib/libc.so.6 #9 0x7fe7891305a6 in () at /usr/lib/libc.so.6 #10 0x7fe78757192b in () at /usr/lib/libQt5Qml.so.5 #11 0x7fe787578e8b in QV4::QObjectWrapper::virtualResolveLookupGetter(QV4::Object const*, QV4::ExecutionEngine*, QV4::Lookup*) () at /usr/lib/libQt5Qml.so.5 #12 0x7fe78758dbea in () at /usr/lib/libQt5Qml.so.5 #13 0x7fe787597e34 in () at /usr/lib/libQt5Qml.so.5 #14 0x7fe78753b7f6 in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () at /usr/lib/libQt5Qml.so.5 #15 0x7fe78768fe6d in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () at /usr/lib/libQt5Qml.so.5 #16 0x7fe787653121 in QQmlBoundSignalExpression::evaluate(void**) () at /usr/lib/libQt5Qml.so.5 #17 0x7fe78765409c in () at /usr/lib/libQt5Qml.so.5 #18 0x7fe7876768cf in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () at /usr/lib/libQt5Qml.so.5 #19 0x7fe7898bce6d in () at /usr/lib/libQt5Core.so.5 #20 0x7fe787cf56d9 in () at /usr/lib/libQt5Quick.so.5 #21 0x7fe787cf6eb9 in QQuickItemView::setCurrentIndex(int) () at /usr/lib/libQt5Quick.so.5 #22 0x7fe78763c0c2 in () at /usr/lib/libQt5Qml.so.5 #23 0x7fe787691915 in () at /usr/lib/libQt5Qml.so.5 #24 0x7fe78769908e in () at /usr/lib/libQt5Qml.so.5 #25 0x7fe787698b73 in QQmlBinding::update(QFlags) () at /usr/lib/libQt5Qml.so.5 #26 0x7fe7876768cf in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () at /usr/lib/libQt5Qml.so.5 #27 0x7fe7898bce6d in () at /usr/lib/libQt5Core.so.5 #28 0x7fe7802d534c in () at /usr/lib/qt/plugins/systemsettingsview/systemsettings_sidebar_mode.so #29 0x7fe7802d71ed in () at /usr/lib/qt/plugins/systemsettingsview/systemsettings_sidebar_mode.so #30 0x7fe7802d7e43 in () at /usr/lib/qt/plugins/systemsettingsview/systemsettings_sidebar_mode.so #31 0x7fe787676994 in () at /usr/lib/libQt5Qml.so.5 #32 0x7fe78757a96c in () at /usr/lib/libQt5Qml.so.5 #33 0x7fe78757bf6d in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () at /usr/lib/libQt5Qml.so.5 #34 0x7fe78758e033 in () at /usr/lib/libQt5Qml.so.5 #35 0x7fe787597e34 in () at /usr/lib/libQt5Qml.so.5 #36 0x7fe78753b7f6 in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () at /usr/lib/libQt5Qml.so.5 #37 0x7fe78768fe6d in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () at /usr/lib/libQt5Qml.so.5 #38 0x7fe787653121 in QQmlBoundSignalExpression::evaluate(void**) () at /usr/lib/libQt5Qml.so.5 #39 0x7fe78765409c in () at /usr/lib/libQt5Qml.so.5 #40 0x7fe7876768cf in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () at /usr/lib/libQt5Qml.so.5 #41 0x7fe7898bce6d in () at /usr/lib/libQt5Core.so.5 #42 0x7fe782fb8a5a in QQuickAbstractButtonPrivate::handleRelease(QPointF const&) () at /usr/lib/libQt5QuickTemplates2.so.5 #43 0x7fe782fd3ab9 in QQuickControl::mouseReleaseEvent(QMouseEvent*) () at /usr/lib/libQt5QuickTemplates2.so.5 #44 0x7fe787c3c1c9 in QQuickItem::event(QEvent*) () at /usr/lib/libQt5Quick.so.5 #45 0x7fe78a578b3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #46 0x7fe78988cad8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #47 0x7fe787c4cd93 in QQuickWindowPrivate::deliverMouseEvent(QQuickPointerMouseEvent*) () at /usr/lib/libQt5Quick.so.5 #48 0x7fe787c4d7f2 in QQuickWindowPrivate::deliverPointerEvent(QQuickPointerEvent*) () at /usr/lib/libQt5Quick.so.5 #49 0x7fe789d55b45 in QWindow::ev
[frameworks-kglobalaccel] [Bug 417087] Launching apps via global hotkeys does not display launch feedback on X11
https://bugs.kde.org/show_bug.cgi?id=417087 Nicolas Fella changed: What|Removed |Added Summary|Launching apps via global |Launching apps via global |hotkeys does not display|hotkeys does not display |launch feedback |launch feedback on X11 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 417087] Launching apps via global hotkeys does not display launch feedback
https://bugs.kde.org/show_bug.cgi?id=417087 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #8 from Nicolas Fella --- On Wayland this was fixed by https://invent.kde.org/frameworks/kglobalaccel/-/commit/ce28705bc9e6e0192108382a1c6bfb4ff59fddd7 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 417087] Launching apps via global hotkeys does not display launch feedback
https://bugs.kde.org/show_bug.cgi?id=417087 --- Comment #7 from Nicolas Fella --- *** Bug 451160 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 451160] On X11, launch feedback does not trigger for apps launched via global keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=451160 Nicolas Fella changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Nicolas Fella --- *** This bug has been marked as a duplicate of bug 417087 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 451160] On X11, launch feedback does not trigger for apps launched via global keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=451160 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #3 from Nicolas Fella --- On Wayland this was fixed by adding support for xdg-activation. On X11 there is a similar mechanism that should be used -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 457776] Global actions/shortcuts do not work after language change
https://bugs.kde.org/show_bug.cgi?id=457776 --- Comment #5 from empyreal --- My physical layout is Focus, not English, lol https://deskthority.net/wiki/Physical_keyboard_layout The so-called "Focus" layout is an alternative to Asian 101, where right shift is divided instead of Backspace. While the JIS layout also features a split right shift, JIS keyboards place the extra key to the left of right shift, whereas the Focus layout puts the extra key to the right. The origin of the layout is not known, but it is most notable by its use by Focus. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 457776] Global actions/shortcuts do not work after language change
https://bugs.kde.org/show_bug.cgi?id=457776 empyreal changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from empyreal --- Sorry for being messy... This problem is not that simple. physical keyboard layout: English System Settings > Input Devices > Keyboard: US, UK, GR, JP, BG, PL Greek do not work, Ukrainian do not work Bulgarian works, Japanese Works English works of course Polish do not work I trigger next and previous track: Metal + Alt + Z/Metal + Alt + B As for me, I need Ukrainian at the moment. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457808] after adding shortcut in System Settings - Shortcuts freeze happens - Apply, shortcut close, delete, change do not work
https://bugs.kde.org/show_bug.cgi?id=457808 empyreal changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from empyreal --- It is not freeze. It seems like freeze of shortcuts window. This bug happens even in Amarok and Krusader. Alt + Tab and you unfrozen, assign another shortcut, again Alt + Tab and so on. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 441680] The default activity can be removed
https://bugs.kde.org/show_bug.cgi?id=441680 Alexandre Pereira changed: What|Removed |Added CC||pereira.a...@gmail.com --- Comment #1 from Alexandre Pereira --- Hi, I tried reproducing this bug report in a new KDE Neon: neon-developer-20220808-1852.iso. I tried setting up a user on X11, with creating a new activity and immediately deleting the "original one". Nothing bad happened. I tried again with a new user, do the same on Wayland. I also tried with another new user, to add some widgets to the desktop first, and then create a new one and delete the original. Nothing bad happened. Can you try it on a VM (or in any other way) with a recent KDE ? Thanks ! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 457932] Shortcuts for opening WezTerm no longer work
https://bugs.kde.org/show_bug.cgi?id=457932 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |ASSIGNED --- Comment #9 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/kglobalaccel/-/merge_requests/50 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457200] If both files and folders are dragged between split views, dolphin copies only the files
https://bugs.kde.org/show_bug.cgi?id=457200 Felix Ernst changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #5 from Felix Ernst --- I guess this bug is resolved then. It is resolved for the 22.08 release of Dolphin because the commit was reverted. Albert just let me know that he has updated the tarball file (https://mail.kde.org/pipermail/release-team/2022-August/012751.html ) so users shouldn't be affected by this. For the 22.12 release of Dolphin the commit stays but we can expect that most people will have a frameworks version that contains >https://invent.kde.org/frameworks/kcoreaddons/-/commit/231c98e21f0dbb0e65014abc033b7022bf559877 until then. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 456348] KrArc freezes, both in Krusader and Dolphin
https://bugs.kde.org/show_bug.cgi?id=456348 --- Comment #12 from Grósz Dániel --- If you have time, it would be a good idea to release a new version of Krusader soon, or figure out the cause of the problem and backport the fix, or perhaps backport the current krarc implementation to the stable Krusader, or instruct packagers about what library version to require. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 456713] plasma-kded.service hangs for around a minute or more on system shutdown
https://bugs.kde.org/show_bug.cgi?id=456713 --- Comment #4 from Patrick O'Callaghan --- Finally realised (after discussion on the Fedora Users list) that this should be set under "user" rather than "system", for example: $ cat /etc/systemd/user.conf.d/99-stop-fast.conf [Manager] DefaultTimeoutStopSec=5s On Mon, 15 Aug 2022 at 12:20, Patrick O'Callaghan wrote: > https://bugs.kde.org/show_bug.cgi?id=456713 > > --- Comment #3 from Patrick O'Callaghan --- > (In reply to Patrick O'Callaghan from comment #2) > > Following discussion on the Fedora Users list, I implemented a workaround > > which solves the immediate problem. See: > > > > > https://lists.fedoraproject.org/archives/list/us...@lists.fedoraproject.org/ > > thread/4UY53SXJSQTGA264SQ4B5V22WYUQQEWG/ > > > > This works, but it would be much better to know exactly why kded is > hanging. > > Specifically, what is it waiting for? This is difficult to discover as > there > > isn't enough logging detail in the journal. All I can tell is that it's > > ignoring SIGTERM for some reason, presumably because one or more of its > > built-in daemons is still active. > > This solution has simply stopped working. The default timeout is indeed > set as > described: > > $ systemctl show --property=DefaultTimeoutStopUSec > DefaultTimeoutStopUSec=5s > > (note the strange and undocumented "USec" rather than "Sec", which you > have to > use to get the value despite "Sec" being used in setting the property) > > This did work for a time, but now makes no difference. I've changed nothing > apart from system updates. > > I once again have to manually kill the offending process (kded) to avoid a > 90-second delay on shutdown/reboot/re-login. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457867] Alacritty can't be opened in maximized mode
https://bugs.kde.org/show_bug.cgi?id=457867 Evgeny changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 456348] KrArc freezes, both in Krusader and Dolphin
https://bugs.kde.org/show_bug.cgi?id=456348 Toni Asensi Esteve changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #11 from Toni Asensi Esteve --- Thanks, Dániel for changing the status of this bug report (and, before that, writing some important information). As it seems that it's not a bug of Krusader (because the problem doesn't happen using the latest code of Krusader), I'm going to mark this bug as "RESOLVED - NOT A BUG". Anyway, please feel free to write in this bug report if you think it's necessary. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455450] Slide desktop animation is slower in 5.25, especially compared to other animations
https://bugs.kde.org/show_bug.cgi?id=455450 --- Comment #13 from Evgeny --- I created one more duplicate of this issue, sorry for that. I ended up patching kwin to make slide faster, here how it can be done in nix in case somebody is interested: https://github.com/kurnevsky/nixfiles/commit/c77a7662428cfa988a624f9db0e442669242fb93 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 457867] Alacritty can't be opened in maximized mode
https://bugs.kde.org/show_bug.cgi?id=457867 --- Comment #2 from Evgeny --- Just checked - with X11 it works correctly. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 457885] show end of line type on the status bar
https://bugs.kde.org/show_bug.cgi?id=457885 Waqar Ahmed changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/ktexteditor/commit/8 ||8ce720d481aa26b0b7143a59c84 ||eddd020c3475 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #3 from Waqar Ahmed --- Git commit 88ce720d481aa26b0b7143a59c84eddd020c3475 by Waqar Ahmed. Committed on 15/08/2022 at 21:02. Pushed by waqar into branch 'master'. Optionally allow to show EndOfLine type in statusbar M +3-0src/dialogs/katedialogs.cpp A +84 -0src/dialogs/statusbarconfigwidget.ui M +1-0src/utils/kateconfig.cpp M +1-0src/utils/kateconfig.h M +29 -0src/view/katestatusbar.cpp M +3-0src/view/katestatusbar.h M +5-0src/view/kateview.cpp M +1-0src/view/kateview.h https://invent.kde.org/frameworks/ktexteditor/commit/88ce720d481aa26b0b7143a59c84eddd020c3475 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 457932] Shortcuts for opening WezTerm no longer work
https://bugs.kde.org/show_bug.cgi?id=457932 --- Comment #8 from poperi...@mailbox.org --- (In reply to Nate Graham from comment #7) > Great, thanks. Does /usr/share/applications/org.wezfurlong.wezterm.desktop > exist? You're welcome. Yeah, it does. Here's its contents: [Desktop Entry] Name=WezTerm Comment=Wez's Terminal Emulator Keywords=shell;prompt;command;commandline;cmd; Icon=org.wezfurlong.wezterm StartupWMClass=org.wezfurlong.wezterm TryExec=wezterm Exec=wezterm start --cwd . -- Type=Application Categories=System;TerminalEmulator;Utility; Terminal=false -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 457932] Shortcuts for opening WezTerm no longer work
https://bugs.kde.org/show_bug.cgi?id=457932 --- Comment #7 from Nate Graham --- Great, thanks. Does /usr/share/applications/org.wezfurlong.wezterm.desktop exist? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 457932] Shortcuts for opening WezTerm no longer work
https://bugs.kde.org/show_bug.cgi?id=457932 --- Comment #6 from poperi...@mailbox.org --- (In reply to Nate Graham from comment #4) > Does this shortcut work if you set it as the launch shortcut for any other > app? Yes. I tried setting Meta+Return to open Konsole and that worked. > How was WezTerm installed? Distro packaging? Flatpak? Snap? Appimage? I installed it from the Arch Linux repository. > Does WezTerm launch if you set any other shortcut for it? No. I've tried Meta+T, Ctrl+Alt+T, Ctrl+Shift+T, etc. > Oh one final question: can you paste the output of `appstreamcli search wezterm` on your machine? Here you go: Identifier: org.wezfurlong.wezterm.desktop [desktop-application] Name: Wez's Terminal Emulator Summary: A GPU-accelerated cross-platform terminal emulator and multiplexer Package: wezterm Homepage: https://wezfurlong.org/wezterm/ Icon: wezterm_org.wezfurlong.wezterm.png --- Identifier: org.wezfurlong.wezterm [desktop-application] Name: Wez's Terminal Emulator Summary: A GPU-accelerated cross-platform terminal emulator and multiplexer Bundle: flatpak:app/org.wezfurlong.wezterm/x86_64/stable Homepage: https://wezfurlong.org/wezterm/ Icon: org.wezfurlong.wezterm.png -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 457932] Shortcuts for opening WezTerm no longer work
https://bugs.kde.org/show_bug.cgi?id=457932 --- Comment #5 from Nate Graham --- Oh one final question: can you paste the output of `appstreamcli search wezterm` on your machine? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 457932] Shortcuts for opening WezTerm no longer work
https://bugs.kde.org/show_bug.cgi?id=457932 --- Comment #4 from Nate Graham --- > [org.wezfurlong.wezterm.desktop] > _k_friendly_name=WezTerm > _launch=Meta+Return,none,WezTerm Ok, so KGlobalAccel has registered the shortcut. A few more questions: 1. Does this shortcut work if you set it as the launch shortcut for any other app? 2. How was WezTerm installed? Distro packaging? Flatpak? Snap? Appimage? 3. Does WezTerm launch if you set any other shortcut for it? -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 454000] current activity information doesn't change
https://bugs.kde.org/show_bug.cgi?id=454000 --- Comment #3 from Eric Edlund --- Are you on the latest version of plasma? 5.25.4 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457931] System Settings crash when application theme is set to kvantum
https://bugs.kde.org/show_bug.cgi?id=457931 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- This will be caused by the KVantum style; please report to Kvantum's bug tracker. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 457932] Shortcuts for opening WezTerm no longer work
https://bugs.kde.org/show_bug.cgi?id=457932 --- Comment #3 from poperi...@mailbox.org --- Created attachment 151346 --> https://bugs.kde.org/attachment.cgi?id=151346&action=edit kglobalshortcutsrc -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 457932] Shortcuts for opening WezTerm no longer work
https://bugs.kde.org/show_bug.cgi?id=457932 --- Comment #2 from poperi...@mailbox.org --- (In reply to Nate Graham from comment #1) > Can you attach your ~/.config/kglobalshortcutsrc file? Sure! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 457932] Shortcuts for opening WezTerm no longer work
https://bugs.kde.org/show_bug.cgi?id=457932 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||n...@kde.org Status|REPORTED|NEEDSINFO --- Comment #1 from Nate Graham --- Can you attach your ~/.config/kglobalshortcutsrc file? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 457387] Compose Key only works in certain applications
https://bugs.kde.org/show_bug.cgi?id=457387 --- Comment #8 from Lucas <0lc6wm...@mozmail.com> --- I have "Position of Compose key" set to caps lock, and no other boxes checked. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 457872] some custom shortcuts stop working
https://bugs.kde.org/show_bug.cgi?id=457872 --- Comment #2 from Rajinder Yadav --- All my shortcuts already existed and were working fine and then broke after an update. Go to system settings -> shortcuts Click Add application, select Kate, assign shortcut. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 449373] Slow wallpaper thumbnail loading
https://bugs.kde.org/show_bug.cgi?id=449373 Eric Edlund changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||ericedlund2...@gmail.com Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 447559] The "Activities" context menu is not updated after linking/unlinking a file to an activity
https://bugs.kde.org/show_bug.cgi?id=447559 Eric Edlund changed: What|Removed |Added CC||ericedlund2...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 431583] Activity stopped after reboot and can't be resumed
https://bugs.kde.org/show_bug.cgi?id=431583 Eric Edlund changed: What|Removed |Added Resolution|--- |WORKSFORME CC||ericedlund2...@gmail.com Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 438174] KDE windows always show on all Activities.
https://bugs.kde.org/show_bug.cgi?id=438174 Eric Edlund changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||ericedlund2...@gmail.com Resolution|--- |WORKSFORME --- Comment #2 from Eric Edlund --- Can't reproduce on Wayland. Is this still happening? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 452915] invert scroll direction shows as enabled but is not actually working upon rebooting when using bluetooth mouse
https://bugs.kde.org/show_bug.cgi?id=452915 --- Comment #5 from Cormac McCarthy --- Registered to say I have exactly the same issue. Invert mouse stops working upon rebooting or waking from sleep. Mouse: MX Master 3, bluetooth (not using the dongle). Operating System: Manjaro Linux KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.15.60-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 12 Ă— AMD Ryzen 5 5600X 6-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 5700 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 452915] invert scroll direction shows as enabled but is not actually working upon rebooting when using bluetooth mouse
https://bugs.kde.org/show_bug.cgi?id=452915 Cormac McCarthy changed: What|Removed |Added CC||maciej...@gmail.com --- Comment #4 from Cormac McCarthy --- Registered to say I have exactly the same issue. Invert mouse stops working upon rebooting or waking from sleep. Mouse: MX Master 3, bluetooth (not using the dongle). Operating System: Manjaro Linux KDE Plasma Version: 5.24.6 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.15.60-1-MANJARO (64-bit) Graphics Platform: X11 Processors: 12 Ă— AMD Ryzen 5 5600X 6-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 5700 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 376345] can't disable "auto spell check" while editing metadata
https://bugs.kde.org/show_bug.cgi?id=376345 --- Comment #4 from caulier.gil...@gmail.com --- Git commit 1cbabe037c7b19c0c0ede596e4da59c88b9dced9 by Gilles Caulier. Committed on 15/08/2022 at 20:08. Pushed by cgilles into branch 'master'. Add methods to active or not the spell-checking in common digiKam text edit classes. M +62 -0core/libs/widgets/text/dtextedit.cpp M +20 -0core/libs/widgets/text/dtextedit.h https://invent.kde.org/graphics/digikam/commit/1cbabe037c7b19c0c0ede596e4da59c88b9dced9 -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 457701] Add .mp4 support
https://bugs.kde.org/show_bug.cgi?id=457701 --- Comment #7 from WS --- I've sent it again as an e-mail. I can't attach it here because none of my songs fit into the size limit -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 457932] Shortcuts for opening WezTerm no longer work
https://bugs.kde.org/show_bug.cgi?id=457932 poperi...@mailbox.org changed: What|Removed |Added Platform|Other |Archlinux Packages -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 457932] New: Shortcuts for opening WezTerm no longer work
https://bugs.kde.org/show_bug.cgi?id=457932 Bug ID: 457932 Summary: Shortcuts for opening WezTerm no longer work Product: frameworks-kglobalaccel Version: 5.97.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: poperi...@mailbox.org Target Milestone: --- SUMMARY I'm not sure if it was after an update, but my Meta+Return shortcut for launching WezTerm (https://wezfurlong.org/wezterm/) no longer works. I also tried binding different shortcuts to it, but none work. Open WezTerm via KRunner does work though. STEPS TO REPRODUCE 1. Go to Settings -> Shortcuts -> Add application -> WezTerm, and bind a key combination to it. 2. Try pressing that key combination. OBSERVED RESULT WezTerm doesn't launch. EXPECTED RESULT WezTerm launches. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.19.1-arch2-1 (64-bit) Graphics Platform: Wayland Processors: 16 Ă— AMD Ryzen 7 3700X 8-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 5700 XT Manufacturer: ASUS -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457931] New: System Settings crash when application theme is set to kvantum
https://bugs.kde.org/show_bug.cgi?id=457931 Bug ID: 457931 Summary: System Settings crash when application theme is set to kvantum Product: systemsettings Version: 5.25.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: sarahgnur...@outlook.com Target Milestone: --- Application: systemsettings (5.25.4) Qt Version: 5.15.5 Frameworks Version: 5.96.0 Operating System: Linux 5.19.0-1-default x86_64 Windowing System: X11 Distribution: "openSUSE Tumbleweed" DrKonqi: 5.25.4 [KCrashBackend] -- Information about the crash: Using the kvantum theme manager causes system settings app to crash The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings), signal: Segmentation fault [KCrash Handler] #4 QGestureManager::getState (this=this@entry=0x55a3c89f5f00, object=object@entry=0x55a3c89f4e70, recognizer=recognizer@entry=0x41, type=type@entry=257) at kernel/qgesturemanager.cpp:210 #5 0x7f300ef1f916 in QGestureManager::filterEventThroughContexts (this=this@entry=0x55a3c89f5f00, contexts=..., event=event@entry=0x7ffcf396c640) at kernel/qgesturemanager.cpp:284 #6 0x7f300ef22b18 in QGestureManager::filterEvent (this=0x55a3c89f5f00, receiver=receiver@entry=0x55a3c89f4e70, event=event@entry=0x7ffcf396c640) at kernel/qgesturemanager.cpp:526 #7 0x7f300eed6eae in QApplication::notify (this=0x7ffcf396cd40, receiver=0x55a3c89f4e70, e=) at kernel/qapplication.cpp:2912 #8 0x7f300e215fb8 in QCoreApplication::notifyInternal2 (receiver=0x55a3c89f4e70, event=0x7ffcf396c640) at kernel/qcoreapplication.cpp:1064 #9 0x7f300eed5abe in QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x55a3c89f4e70, event=event@entry=0x7ffcf396c640, alienWidget=, nativeWidget=0x55a3c86abfc0, buttonDown=buttonDown@entry=0x7f300f41b330 , lastMouseReceiver=..., spontaneous=true, onlyDispatchEnterLeave=false) at kernel/qapplication.cpp:2619 #10 0x7f300ef29a88 in QWidgetWindow::handleMouseEvent (this=0x55a3c8aa5ab0, event=0x7ffcf396c8f0) at kernel/qwidgetwindow.cpp:683 #11 0x7f300ef2cfe0 in QWidgetWindow::event (this=0x55a3c8aa5ab0, event=0x7ffcf396c8f0) at kernel/qwidgetwindow.cpp:300 #12 0x7f300eecf41e in QApplicationPrivate::notify_helper (this=, receiver=0x55a3c8aa5ab0, e=0x7ffcf396c8f0) at kernel/qapplication.cpp:3637 #13 0x7f300e215fb8 in QCoreApplication::notifyInternal2 (receiver=0x55a3c8aa5ab0, event=0x7ffcf396c8f0) at kernel/qcoreapplication.cpp:1064 #14 0x7f300e7819b5 in QGuiApplicationPrivate::processMouseEvent (e=0x55a3c8adaca0) at kernel/qguiapplication.cpp:2282 #15 0x7f300e75533c in QWindowSystemInterface::sendWindowSystemEvents (flags=flags@entry=...) at kernel/qwindowsysteminterface.cpp:1169 #16 0x7f3008b327fa in xcbSourceDispatch (source=) at qxcbeventdispatcher.cpp:105 #17 0x7f300c736ea0 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #18 0x7f300c737258 in ?? () from /lib64/libglib-2.0.so.0 #19 0x7f300c7372ec in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #20 0x7f300e26d456 in QEventDispatcherGlib::processEvents (this=0x55a3c86940b0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #21 0x7f300e214a2b in QEventLoop::exec (this=this@entry=0x7ffcf396cc20, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #22 0x7f300e21cb96 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #23 0x55a3c7554e0b in ?? () #24 0x7f300db1f5b0 in __libc_start_call_main () from /lib64/libc.so.6 #25 0x7f300db1f679 in __libc_start_main_impl () from /lib64/libc.so.6 #26 0x55a3c7555755 in ?? () [Inferior 1 (process 16078) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 451003] Desktop files should be copied instead of symlinked
https://bugs.kde.org/show_bug.cgi?id=451003 --- Comment #3 from Trent M --- I think I've made a breakthrough here. This is *mostly* a Flatpak-specific issue, and here is why. I just tested out trying to edit an application I've installed in a custom system-wide Flatpak installation, located at `/xusr/flatpak`. I try to change its name, it fails, then I go look at the file it made. It is a symlink instead of a copy, but here's where it gets interesting. Flatpak wants you to put the `exports/share` directory in XDG_DATA_DIRS so that the DE can read the applications in `exports/share/applications`, and it does that automatically nowadays, but here is the rub: everything in that directory is already a symlink! I checked the points-to field of the resulting symlink that was made in `$XDG_DATA_HOME/applications`. It's not pointing to `/xusr/flatpak/exports/share/applications/com.github.unrud.VideoDownloader.desktop`. It's pointing at `/xusr/flatpak/app/com.github.unrud.VideoDownloader/current/active/export/share/applications/com.github.unrud.VideoDownloader.desktop`, which is the *target* of the first file. I think the reason I had not realized this was the case was because if you use `cp` to copy that file, it dereferences all the symlinks on the way to the actual file without you having to specify the `-L` argument. I am not sure why it does that. But Plasma really was already copying the file... it was just copying the symlink as-is. What it needs to do is dereference every symlink it finds on the way. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 457855] [Nvidia Wayland] Max Refresh rate is Smaller than Display
https://bugs.kde.org/show_bug.cgi?id=457855 --- Comment #1 from Zamundaaa --- Please attach the output of drm_info -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 105459] [PATCH] switch to Read Only Mode for files that are read only
https://bugs.kde.org/show_bug.cgi?id=105459 Roc Vallès changed: What|Removed |Added Resolution|INTENTIONAL |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED CC||valles...@gmail.com --- Comment #6 from Roc Vallès --- This annoyed me today (17 years later). If it can't just be the default, please at least consider making it a setting. -- You are receiving this mail because: You are watching all bug changes.
[Reminder Daemon] [Bug 457930] Seemingly high ram usage
https://bugs.kde.org/show_bug.cgi?id=457930 --- Comment #2 from Manuel de la Fuente --- Created attachment 151345 --> https://bugs.kde.org/attachment.cgi?id=151345&action=edit Searching akonadi under the processes view -- You are receiving this mail because: You are watching all bug changes.
[Reminder Daemon] [Bug 457930] Seemingly high ram usage
https://bugs.kde.org/show_bug.cgi?id=457930 --- Comment #1 from Manuel de la Fuente --- Created attachment 151344 --> https://bugs.kde.org/attachment.cgi?id=151344&action=edit System Monitor overview shows high RAM usage under Calendar Reminders -- You are receiving this mail because: You are watching all bug changes.
[Reminder Daemon] [Bug 457930] New: Seemingly high ram usage
https://bugs.kde.org/show_bug.cgi?id=457930 Bug ID: 457930 Summary: Seemingly high ram usage Product: Reminder Daemon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: m...@nueljl.in Target Milestone: --- Created attachment 151343 --> https://bugs.kde.org/attachment.cgi?id=151343&action=edit List of installed packages relating to akonadi SUMMARY Using System Monitor / Overview / Applications, 'Calendar Reminders' takes up around 300mb of ram. It's not in the processes view, so I'm guessing it's just combining everything akonadi in there. STEPS TO REPRODUCE 1. Log in 2. Open System Monitor OBSERVED RESULT Calendar Reminder takes too much RAM EXPECTED RESULT Calendar Reminder doesn't take too much RAM SOFTWARE/OS VERSIONS Operating System: Fedora Linux 36 KDE Plasma Version: 5.25.4 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 Kernel Version: 5.18.16-200.fc36.x86_64 (64-bit) Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
