[digikam] [Bug 433984] DigiKam does not save tags as hierarchical tags in Extended Attributes
https://bugs.kde.org/show_bug.cgi?id=433984 --- Comment #2 from tagwer...@innerjoin.org --- Checked with build 2021-03-06 That works so much better. I can see two changes, hierarchical tags I create within digiKam are written as hierarchical tags to the extended attributes - so I see: # file: testfile.jpg user.xdg.tags="Parenttag/Mytag" I can set these tags in Dolphin/Gwenview, read them into digiKam and write them out and it works. A "full circle" test works. I also notice that when digiKam reads the Extended Attribute Tags, they appear 'as given' in the Tag view, not prefixed by /BalooTags. I also do not need to create a new Tag under /BalooTags in order for it to be exported to the xattrs. For me, that is a real improvement. Many thanks! There might be an edge case when someone deletes tags within digiKam and expects the tags to be cleared when written to the xattr. Can check and log this as a separate issue -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434048] New: system setting crashes when trying to open bluetooth setting
https://bugs.kde.org/show_bug.cgi?id=434048 Bug ID: 434048 Summary: system setting crashes when trying to open bluetooth setting Product: systemsettings Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: minh.vln140...@gmail.com Target Milestone: --- Application: systemsettings5 (5.21.80) (Compiled from sources) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.4.0-66-generic x86_64 Windowing System: X11 Drkonqi Version: 5.21.80 Distribution: KDE neon Unstable Edition -- Information about the crash: when I try to open bluetooth setting, the app keeps crashing. and then I log out and log in again, the problem still occurs The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault [New LWP 37494] [New LWP 37495] [New LWP 37496] [New LWP 37497] [New LWP 37498] [New LWP 37499] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fa2e28ddaff in __GI___poll (fds=0x7ffe40d7e3a8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7fa2de6a28c0 (LWP 37492))] Thread 7 (Thread 0x7fa2ca85a700 (LWP 37499)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55ab91769f08) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55ab91769eb8, cond=0x55ab91769ee0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55ab91769ee0, mutex=0x55ab91769eb8) at pthread_cond_wait.c:638 #3 0x7fa2d53b4b5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7fa2d53b475b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7fa2e1477609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fa2e28ea293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7fa2cb05b700 (LWP 37498)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55ab91769f08) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55ab91769eb8, cond=0x55ab91769ee0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55ab91769ee0, mutex=0x55ab91769eb8) at pthread_cond_wait.c:638 #3 0x7fa2d53b4b5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7fa2d53b475b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7fa2e1477609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fa2e28ea293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7fa2c705b700 (LWP 37497)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55ab91769f08) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55ab91769eb8, cond=0x55ab91769ee0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55ab91769ee0, mutex=0x55ab91769eb8) at pthread_cond_wait.c:638 #3 0x7fa2d53b4b5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7fa2d53b475b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7fa2e1477609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fa2e28ea293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7fa2d4c82700 (LWP 37496)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55ab91769f08) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55ab91769eb8, cond=0x55ab91769ee0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55ab91769ee0, mutex=0x55ab91769eb8) at pthread_cond_wait.c:638 #3 0x7fa2d53b4b5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7fa2d53b475b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7fa2e1477609 in start_thread (arg=) at pthread_create.c:477 #6 0x7fa2e28ea293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7fa2dcc59700 (LWP 37495)): #0 0x7fa2e28ddaff in __GI___poll (fds=0x7fa2d0012520, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fa2e0b6718e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fa2e0b672c3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fa2e2ff7fbb in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fa2e2f9c1ab in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fa2e2db6a12 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fa2e1cc7f4b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fa2e2db7bac in ??
[kdeconnect] [Bug 434047] New: No media controls for Kodi
https://bugs.kde.org/show_bug.cgi?id=434047 Bug ID: 434047 Summary: No media controls for Kodi Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: dagobert...@mailbox.org Target Milestone: --- SUMMARY When playing a video in Kodi, media controls do not show up. Is it a bug in KDE Connect or does Kodi may be not support some standard? Operating System: KDE neon 5.21 KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.4.0-66-generic OS Type: 64-bit Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 434046] New: "File already exists" is freezing
https://bugs.kde.org/show_bug.cgi?id=434046 Bug ID: 434046 Summary: "File already exists" is freezing Product: gwenview Version: 20.12.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: coli...@mailbox.org Target Milestone: --- Created attachment 136428 --> https://bugs.kde.org/attachment.cgi?id=136428=edit unresponsive dialog SUMMARY Since a month or two the "file already exists" dialog gets unresponsive so I can't select any action (like skip, rename, overwrite, cancel). STEPS TO REPRODUCE 1. Create two folders 2. Place the same image in each of them 3. Select both images (either by unfold both folders or through the search function 4. open with gwenview via the right mouse click menu OBSERVED RESULT The "File already exists" dialog is not responding to any action. EXPECTED RESULT The "File already exists" shouldn't be unresponsive. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.21.1 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 I am on openSUSE Tumbleweed on a 3 day old installation. ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434045] New: Systemsettings crashes "org.kde.systemsettings.app: Error loading plugin"
https://bugs.kde.org/show_bug.cgi?id=434045 Bug ID: 434045 Summary: Systemsettings crashes "org.kde.systemsettings.app: Error loading plugin" Product: systemsettings Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: jodr...@live.com Target Milestone: --- Application: systemsettings5 (5.21.80) Qt Version: 5.15.2 Frameworks Version: 5.80.0 Operating System: Linux 5.11.3-xanmod1-cacule x86_64 Windowing System: X11 Drkonqi Version: 5.21.80 Distribution: "openSUSE Tumbleweed" -- Information about the crash: Running it from a terminal shows : "org.kde.systemsettings.app: Error loading plugin" Trying to launch it from krunner or any individual kcm (eg: krunner > icons) will crash it too. Using kcmshell5 from a terminal to launch kcms works fine. The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault Content of s_kcrashErrorMessage: [Current thread is 1 (Thread 0x7f422751d500 (LWP 9000))] [KCrash Handler] #6 0x7f42263984d4 in KConfigGroup::sync (this=0x55b947835768) at /usr/src/debug/kconfig-5.80.0git.20210301T142846~36f12b2-ku.8.1.x86_64/src/core/kconfiggroup.cpp:599 #7 0x7f41d0951e90 in SidebarMode::~SidebarMode (this=, this=) at /usr/src/debug/systemsettings5-5.21.80git.20210304T140718~1ec8b707-ku.12.1.x86_64/sidebar/SidebarMode.cpp:318 #8 0x7f41d0951f39 in SidebarMode::~SidebarMode (this=, this=) at /usr/src/debug/systemsettings5-5.21.80git.20210304T140718~1ec8b707-ku.12.1.x86_64/sidebar/SidebarMode.cpp:320 #9 0x55b947394449 in KPluginFactory::create (args=..., parent=0x55b9475c43a0, this=0x55b9478c1930) at /usr/include/KF5/KCoreAddons/kpluginfactory.h:775 #10 SettingsBase::initApplication (this=0x55b9475c43a0) at /usr/src/debug/systemsettings5-5.21.80git.20210304T140718~1ec8b707-ku.12.1.x86_64/app/SettingsBase.cpp:142 #11 0x7f422600b351 in QObject::event (this=0x55b9475c43a0, e=0x55b94770) at kernel/qobject.cpp:1314 #12 0x7f4227860909 in KXmlGuiWindow::event (this=0x55b9475c43a0, ev=0x55b94770) at /usr/src/debug/kxmlgui-5.80.0git.20210305T140912~23dfc4b-ku.6.1.x86_64/src/kxmlguiwindow.cpp:109 #13 0x7f4226c954ff in QApplicationPrivate::notify_helper (this=, receiver=0x55b9475c43a0, e=0x55b94770) at kernel/qapplication.cpp:3632 #14 0x7f4225fdf32a in QCoreApplication::notifyInternal2 (receiver=0x55b9475c43a0, event=0x55b94770) at kernel/qcoreapplication.cpp:1063 #15 0x7f4225fe1d61 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x55b9473a66f0) at kernel/qcoreapplication.cpp:1817 #16 0x7f4226037233 in postEventSourceDispatch (s=s@entry=0x55b9474c7f50) at kernel/qeventdispatcher_glib.cpp:277 #17 0x7f4223b54f57 in g_main_dispatch (context=0x7f421c005000) at ../glib/gmain.c:3325 #18 g_main_context_dispatch (context=0x7f421c005000) at ../glib/gmain.c:4043 #19 0x7f4223b552d8 in g_main_context_iterate (context=context@entry=0x7f421c005000, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4119 #20 0x7f4223b5538f in g_main_context_iteration (context=0x7f421c005000, may_block=may_block@entry=1) at ../glib/gmain.c:4184 #21 0x7f42260368bf in QEventDispatcherGlib::processEvents (this=0x55b9474d5f20, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #22 0x7f4225fddceb in QEventLoop::exec (this=this@entry=0x7ffc2dc19120, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #23 0x7f4225fe5f60 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #24 0x7f422653e35c in QGuiApplication::exec () at kernel/qguiapplication.cpp:1867 #25 0x7f4226c95475 in QApplication::exec () at kernel/qapplication.cpp:2824 #26 0x55b94738c47a in main (argc=, argv=0x7ffc2dc19240) at /usr/src/debug/systemsettings5-5.21.80git.20210304T140718~1ec8b707-ku.12.1.x86_64/app/main.cpp:222 [Inferior 1 (process 9000) detached] Possible duplicates by query: bug 225025, bug 187894, bug 182494, bug 181571, bug 176961. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415408] No Qt platform plugin could be initialized
https://bugs.kde.org/show_bug.cgi?id=415408 ciccioric...@yopmail.com changed: What|Removed |Added CC||ciccioric...@yopmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434044] New: Multi-word searches appear to stop at the first word
https://bugs.kde.org/show_bug.cgi?id=434044 Bug ID: 434044 Summary: Multi-word searches appear to stop at the first word Product: plasmashell Version: 5.21.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: ddascalescu+...@gmail.com CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Created attachment 136427 --> https://bugs.kde.org/attachment.cgi?id=136427=edit Launcher searching for KDE Menu Editor surfaces other results first Searching in the launcher for "KDE Menu Editor" surfaces other results containing "KDE" above "KDE Menu Editor". -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 432915] Kdenlive + OBS audio corruption bug [2021]
https://bugs.kde.org/show_bug.cgi?id=432915 --- Comment #8 from katastic --- This also affected a bluray rip of the movie Hot Rod. I let the preview rendering run and it still did it. Not OBS. Not NVENC. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 432507] Discover crashes on startup
https://bugs.kde.org/show_bug.cgi?id=432507 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |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.
[krita] [Bug 432959] When you move the stylus, it moves sideways, avoiding part of the canvas.
https://bugs.kde.org/show_bug.cgi?id=432959 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433230] Dolphin window doesn't return to size set by user after returning from maximize state
https://bugs.kde.org/show_bug.cgi?id=433230 --- Comment #9 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 432626] krita is not detecting directx 12
https://bugs.kde.org/show_bug.cgi?id=432626 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433275] Being able to set that every OpenGL window gets composited to Vulkan (with Wayland)
https://bugs.kde.org/show_bug.cgi?id=433275 --- 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.
[kdenlive] [Bug 399028] I can't save
https://bugs.kde.org/show_bug.cgi?id=399028 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|UNMAINTAINED|WORKSFORME --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 404728] Kdenlive crashes immediately
https://bugs.kde.org/show_bug.cgi?id=404728 --- Comment #8 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 413308] Error shortcut
https://bugs.kde.org/show_bug.cgi?id=413308 --- 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.
[plasmashell] [Bug 434043] New: Plasma shell crashes on startup
https://bugs.kde.org/show_bug.cgi?id=434043 Bug ID: 434043 Summary: Plasma shell crashes on startup Product: plasmashell Version: 5.20.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: averyfree...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.20.5) Qt Version: 5.15.2 Frameworks Version: 5.78.0 Operating System: Linux 5.11.0.zfs x86_64 Windowing system: X11 Distribution: Debian GNU/Linux bullseye/sid -- Information about the crash: - What I was doing when the application crashed: Opening desktop - Unusual behavior I noticed: Startup animations slower than usual. Once taskbar area usually appears, now goes blank and bug report window opens. No windows, etc. present, desktop inaccessible. Appears to happen every time - have reproduced 5 times now. - Custom settings of the application: Using self-compiled vanilla 5.11.0 kernel. The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7fe9c6ef661f in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #5 0x7fe9c6cfbeaf in QV4::PersistentValueStorage::allocate() () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7fe9c6cfc4f3 in QV4::PersistentValue::set(QV4::ExecutionEngine*, QV4::Value const&) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fe9c6e99b8f in QQmlJavaScriptExpression::setupFunction(QV4::ExecutionContext*, QV4::Function*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7fe9c6e9ff2f in QQmlBinding::create(QQmlPropertyData const*, QV4::Function*, QObject*, QQmlContextData*, QV4::ExecutionContext*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7fe9c6eb3112 in QQmlObjectCreator::setPropertyBinding(QQmlPropertyData const*, QV4::CompiledData::Binding const*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x7fe9c6eb4cf4 in QQmlObjectCreator::setupBindings(bool) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #11 0x7fe9c6eb0c8b in QQmlObjectCreator::populateInstance(int, QObject*, QObject*, QQmlPropertyData const*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #12 0x7fe9c6eb3a42 in QQmlObjectCreator::setPropertyBinding(QQmlPropertyData const*, QV4::CompiledData::Binding const*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #13 0x7fe9c6eb4cf4 in QQmlObjectCreator::setupBindings(bool) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #14 0x7fe9c6eb0c8b in QQmlObjectCreator::populateInstance(int, QObject*, QObject*, QQmlPropertyData const*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #15 0x7fe9c6eb1c55 in QQmlObjectCreator::createInstance(int, QObject*, bool) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #16 0x7fe9c6eb28bf in QQmlObjectCreator::create(int, QObject*, QQmlInstantiationInterrupt*, int) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #17 0x7fe9c6eb1f4f in QQmlObjectCreator::createInstance(int, QObject*, bool) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #18 0x7fe9c6eb4848 in QQmlObjectCreator::setPropertyBinding(QQmlPropertyData const*, QV4::CompiledData::Binding const*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #19 0x7fe9c6eb4cf4 in QQmlObjectCreator::setupBindings(bool) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #20 0x7fe9c6eb0c8b in QQmlObjectCreator::populateInstance(int, QObject*, QObject*, QQmlPropertyData const*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #21 0x7fe9c6eb1c55 in QQmlObjectCreator::createInstance(int, QObject*, bool) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #22 0x7fe9c6eb4848 in QQmlObjectCreator::setPropertyBinding(QQmlPropertyData const*, QV4::CompiledData::Binding const*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #23 0x7fe9c6eb4cf4 in QQmlObjectCreator::setupBindings(bool) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #24 0x7fe9c6eb0c8b in QQmlObjectCreator::populateInstance(int, QObject*, QObject*, QQmlPropertyData const*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #25 0x7fe9c6eb1c55 in QQmlObjectCreator::createInstance(int, QObject*, bool) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #26 0x7fe9c6eb28bf in QQmlObjectCreator::create(int, QObject*, QQmlInstantiationInterrupt*, int) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #27 0x7fe9c6eb1f4f in QQmlObjectCreator::createInstance(int, QObject*, bool) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #28 0x7fe9c6eb28bf in QQmlObjectCreator::create(int, QObject*, QQmlInstantiationInterrupt*, int) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #29 0x7fe9c6e4389b in QQmlComponentPrivate::beginCreate(QQmlContextData*) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #30 0x7fe9c6e45b7d in QQmlComponent::createObject(QQmlV4Function*) () from
[gwenview] [Bug 416794] Gwenview crashes when working with multiple images selected
https://bugs.kde.org/show_bug.cgi?id=416794 --- Comment #3 from Vince LaConte --- Created attachment 136426 --> https://bugs.kde.org/attachment.cgi?id=136426=edit New crash information added by DrKonqi gwenview (20.08.2) using Qt 5.14.2 - What I was doing when the application crashed: Same behavior as before, slightly different system and backtrace, (if these additional crashes are helpful someone let me know otherwise I'll just be quiet now. -- Backtrace (Reduced): #4 0x7f91837c4af4 in KActivities::ResourceInstance::setUri(QUrl const&) () from /lib/x86_64-linux-gnu/libKF5Activities.so.5 #5 0x563a8dedbeed in Gwenview::ViewMainPage::openUrls (this=, allUrls=..., currentUrl=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:156 #6 0x563a8def695a in Gwenview::MainWindow::openSelectedDocuments (this=0x563a8f8e1020) at ./app/mainwindow.cpp:1081 #7 0x563a8def6c75 in Gwenview::MainWindow::slotSelectionChanged (this=0x563a8f8e1020) at ./app/mainwindow.cpp:1229 #8 0x7f9181e942e6 in QtPrivate::QSlotObjectBase::call (a=0x7ffd929a49d0, r=0x563a8f8e1020, this=0x563a8fe1f720) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 434042] New: Sensor browser is hard to navigate with a mouse
https://bugs.kde.org/show_bug.cgi?id=434042 Bug ID: 434042 Summary: Sensor browser is hard to navigate with a mouse Product: plasma-systemmonitor Version: 5.21.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: nicolas.wer...@ymail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 136425 --> https://bugs.kde.org/attachment.cgi?id=136425=edit Sensor browser using half the screen height and sorting cores wrong as well as missing information what is being added and where you are. SUMMARY When selecting sensors, you are always presented with a new list with almost no context or hinting if you are currently adding a sensor or just opening another nested list. There is also no context of how deep you currently are and where you can go back to as well as no easy (or no intuitive) way to go back to the top. Also the view sometimes doesn't fill all the available vertical space and leaves a blank space. The lists are also sorted wrong, where core 11 will come after core 2. I feel like this would be much easier to navigate, if this was a tree view, that you could collapse and uncollapse as needed. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION The attached screenshot shows me trying to temperature sensors for my CPUs. I have no idea, what menu I clicked on to get there. I have no idea, what clicking any of those things does and when I click on "all" something completely different happens than clicking on an individual core. It took me 2 minutes to get to the same menu again by accident and then figuring out that there ARE temperature sensors for the individual cores, just not for all cores and I need to click them manually each time. I however did not do that in the end, since I do not want to navigate to the same menu 16 times, which needs 16*3 + 2 = 50 clicks, more if you ever click out of that screen by accident. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433979] American tax forms checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=433979 --- Comment #11 from Leonard Lausen --- It turns out this is due to a mismatch in fontconfig (too recent) and font file (too old) in Gentoo. See https://bugs.gentoo.org/716856 I opened an upstream bug in Poppler to suggest the idea that poppler may warn the user if the chosen fallback font can't render all characters in the document: https://gitlab.freedesktop.org/poppler/poppler/-/issues/1054 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 434019] Move Context Menu's Duplicate dock into Add Dock/Panel submenu
https://bugs.kde.org/show_bug.cgi?id=434019 --- Comment #2 from tr...@yandex.com --- (In reply to Michail Vourlakos from comment #1) > Makes sense, at the top or the bottom of it? I think you can simply append it to the list. | Default Dock | | Default Panel | | Empty Panel| | Duplicate this | -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 434041] Labels in memory overview overlap and curve is wrong at the start
https://bugs.kde.org/show_bug.cgi?id=434041 --- Comment #1 from Nicolas Werner --- Woops, this is probably a duplicate of https://bugs.kde.org/show_bug.cgi?id=429156 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433621] No category name over "Appearance" on Manjaro, which looks weird
https://bugs.kde.org/show_bug.cgi?id=433621 Chris Holland changed: What|Removed |Added CC||zrenf...@gmail.com --- Comment #3 from Chris Holland --- $ grep "Name=Hardware Configuration" /usr/share/kservices5/*.desktop /usr/share/kservices5/msm_mhwd.desktop:Name=Hardware Configuration $ pacman -Qo /usr/share/kservices5/msm_mhwd.desktop /usr/share/kservices5/msm_mhwd.desktop is owned by manjaro-settings-manager-kcm 0.5.6-11 * https://gitlab.manjaro.org/applications/manjaro-settings-manager * https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/blob/master/src/manjaro-category.desktop#L6 $ pacman -Qo /usr/share/kservices5/settings-appearance.desktop /usr/share/kservices5/settings-appearance.desktop is owned by systemsettings 5.21.0 settings-appearance.desktop has settings-root-category.desktop as a parent category. The only ugly way I can think of is for Manjaro to patch the systemsettings package, however this bug probably affects all distros who put a kcm at the top. I think this is the commit that tells it to not display "Name=Root"? This looks slightly more complicated than just replacing an empty string in a desktop file. https://invent.kde.org/plasma/systemsettings/-/commit/f8e5cc22f4e90778fa8943f867cec9015e5cd6c4#81309d4ed02920d5a144031db1af0c3b7a0bb337_109_112 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 434041] New: Labels in memory overview overlap and curve is wrong at the start
https://bugs.kde.org/show_bug.cgi?id=434041 Bug ID: 434041 Summary: Labels in memory overview overlap and curve is wrong at the start Product: plasma-systemmonitor Version: 5.21.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: nicolas.wer...@ymail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 136424 --> https://bugs.kde.org/attachment.cgi?id=136424=edit Screenshot of graph SUMMARY When opening the memory use history initially, it for some reason overlapped the labels of swap and memory use? Also the line starts out very weirdly. The memory usage profile was flat for the last 10 hours, but the widgets shows a few weird jumps in the beginning. This is probably related to the smoothing? All of that fixes itself after waiting for a bit and/or switching tabs. STEPS TO REPRODUCE 1. Open system monitor 2. Go to history tab OBSERVED RESULT See intro EXPECTED RESULT Labels don't overlap and curve goes smoothly or sharply from 0 to 53 instead of wiggling at the start and end. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 434040] New: Default CPU usage graph scales badly to 16+ cores
https://bugs.kde.org/show_bug.cgi?id=434040 Bug ID: 434040 Summary: Default CPU usage graph scales badly to 16+ cores Product: plasma-systemmonitor Version: 5.21.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: nicolas.wer...@ymail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 136423 --> https://bugs.kde.org/attachment.cgi?id=136423=edit Comparison of the old and new graphs with different settings and sizes SUMMARY There are multiple issues here. In the default size, the percentages below the CPU graph are unreadable. This should be partially fixed by https://invent.kde.org/frameworks/kquickcharts/-/merge_requests/28 But KSysguard solved that more nicely, by first shrinking the legend to just colored percentages. You should still wrap them at some point, because otherwise 48 threads will fit on pretty much no screen, but having a colored line next to it is not very useful at that size. Secondly, the default of using a stacked chart leads to a chart going to 1600%, but because only one core is pinned, that one sits at 1/16th of the chart. This does not provide much useful information about why an application hangs, since it looks like it is hanging in IO instead of in a CPU loop. Third, there is no actual unstacked line graph mode. The only option is a line mode with everything below it filled, which is very hard to read and to recognize patterns in (i.e. everything spiked to 100% but with some drops here and there to 0). KSysguard solved that by having the area below the line half transparent, which allowed you to see all the lines in any case. STEPS TO REPRODUCE 1. Open CPU widget on a system with 16 cores or more OBSERVED RESULT Badly scaled CPU graph, that hides half the information. EXPECTED RESULT CPU graph that shows information of all CPU cores at a glance. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 434039] New: Memory details are missing
https://bugs.kde.org/show_bug.cgi?id=434039 Bug ID: 434039 Summary: Memory details are missing Product: plasma-systemmonitor Version: 5.21.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: nicolas.wer...@ymail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 136422 --> https://bugs.kde.org/attachment.cgi?id=136422=edit Memory details view in Ksysguard SUMMARY KSysguard used to provide detailed memory information about where and what memory is used. While it is unfortunate, that this was rendered in a WebView, this view alone is my primary reason for using KSysguard. Since KSysguard is going to be replaced (I'm told), systemmonitor should provide the same or an equivalent view. You can find the view in Ksysguard by going to the process view and right clicking on a process. OBSERVED RESULT No memory detail view in the replacement for KSysguard. EXPECTED RESULT A memory detail view, that is at least as powerful as the tool, that it is intended to replace. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION KSysguard is always the first KDE tool I install on a new system, specifically, because the memory overview is much more powerful than tools like htop provide. I really don't want to use one of my most used features, just to make a nicer looking tool. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433059] Changing "Active/Inactive Titlebar" colors has no effect when Header colors are present
https://bugs.kde.org/show_bug.cgi?id=433059 Chris Spiegel changed: What|Removed |Added CC||cspie...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 434038] New: Please provide an updated version of Maliit that is usable
https://bugs.kde.org/show_bug.cgi?id=434038 Bug ID: 434038 Summary: Please provide an updated version of Maliit that is usable Product: neon Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: 2gd4...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY Since the QT5 Virtual keyboard support has been removed, can packages please be supplied that allow the easy installation of Maliit. It does not show up under Discover and apt-get install maliit-framework throws the error it is dependent on QT 5.12.8 (which I guess is from ubuntu). Functioning virtual keyboard support would be greatly appreciated ( we would need to know how to integrate it with kwin but at least having an installable package would be a great start. Many thanks STEPS TO REPRODUCE 1. Open terminal 2. pkcon install maliit-framework 3. OBSERVED RESULT Fatal error: The following packages have unmet dependencies: maliit-framework: Depends: qtbase-abi-5-12-8 Recommends: maliit-inputmethod-plugin but it is not installable EXPECTED RESULT Install without errors SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE Neon 5.21 (available in About System) KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433799] item geometries not created for new user accounts created using lookandfeel and/or layout templates
https://bugs.kde.org/show_bug.cgi?id=433799 --- Comment #16 from Jeff Hodd --- That does indeed fix the issue. Thanks much, Martin. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 434037] New: Application page should be hidden on unsupported systems
https://bugs.kde.org/show_bug.cgi?id=434037 Bug ID: 434037 Summary: Application page should be hidden on unsupported systems Product: plasma-systemmonitor Version: 5.21.2 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: nicolas.wer...@ymail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 136421 --> https://bugs.kde.org/attachment.cgi?id=136421=edit Screenshot of the empty application page SUMMARY On systems without systemd, the application page is just empty. That is pretty confusing. Either show, that it is unsupported or hide the page alltogether. STEPS TO REPRODUCE 1. Install a distro without systemd 2. Open system monitor 3. Navigate to applications page OBSERVED RESULT Empty application page. EXPECTED RESULT No page or a hint, why it is empty. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433979] American tax forms checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=433979 Leonard Lausen changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM --- Comment #10 from Leonard Lausen --- I used qt5/demos/poppler_qt5viewer from poppler to confirm that this is a poppler bug. If I compile qt5/demos/poppler_qt5viewer on Ubuntu 20.04, the checkboxes show up fine. On my Gentoo system they do not. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 433967] If Baloo Indexing is disabled, but Baloo is enabled, searches immediately return 0 results
https://bugs.kde.org/show_bug.cgi?id=433967 --- Comment #2 from The Feren OS Dev --- Created attachment 136420 --> https://bugs.kde.org/attachment.cgi?id=136420=edit Baloo KCM -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433987] Login scripts don't start in systemd mode
https://bugs.kde.org/show_bug.cgi?id=433987 David Edmundson changed: What|Removed |Added CC||kde.podag...@slmail.me --- Comment #2 from David Edmundson --- *** Bug 433133 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433133] [systemd] Only applications are converted into systemd units
https://bugs.kde.org/show_bug.cgi?id=433133 David Edmundson changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from David Edmundson --- *** This bug has been marked as a duplicate of bug 433987 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433987] Login scripts don't start in systemd mode
https://bugs.kde.org/show_bug.cgi?id=433987 David Edmundson changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from David Edmundson --- Urgh, we have two sets of login script. We do call runEnvironmentScripts() but I don't have an equivalent of StartupPhase2::runUserAutostart --- We have a few options: We could make a tiny binary that executes those scripts, then provide a .desktop file that runs this in autostart phase 2. then we can remove the specific code from the legacy boot, and both can share this and have it "just work" for both. We could make a custom generator, somewhat like the apps autostart Maybe the KCM should create .desktop files with the Exec line porting to the script, rather than copying things into a specific dir. Then we get to attach metadata to the script and we reduce our code paths here. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 432952] [Master] Restore Defaults for Canvas Input Settings softly removes all the canvas input shortcuts
https://bugs.kde.org/show_bug.cgi?id=432952 vanyossi changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REOPENED|NEEDSINFO --- Comment #4 from vanyossi --- Im sorry but I cannot reproduce this one in e2d3c4, pushing the restore default does not erase default canvas input setting shortcuts. Probably your settings files are modified and krita restores to those modified settings files, erasing all canvas input settings -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433657] [systemd] some environment variables got overriden when use plasma systemdBoot
https://bugs.kde.org/show_bug.cgi?id=433657
David Edmundson changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution|--- |NOT A BUG
--- Comment #2 from David Edmundson ---
>2. create `~/.config/environment.d/99-env.conf` with content:
XAUTHORITY=${XDG_RUNTIME_DIR}/Xauthority
It's a good thing that's overridden, it's set by SDDM on login.
PATH I don't know of, but it's not our code directly.
We do correctly source a bunch of scripts during login /etc/X11/Xsession.d for
example, anything set later overrides something set very early in the boot
script.
I'm happy to investigate further if you can pinpoint something we're actually
doing wrong, but so far I can't see anything
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 381266] Icontasks identifying Chrome apps as Chrome windows
https://bugs.kde.org/show_bug.cgi?id=381266
--- Comment #15 from Andrei Shevchuk ---
I think I have a [decent
workaround](https://shevchuk.co/notes/2021/03/06/chromium-web-apps-on-kde-plasma).
The problem is that task bar seems to ignore instance name when making grouping
decision. It also does not update grouping even if you update window class
manually. As a workaround, we have to hide window from the task bar, then
change its class and bring it back. But if we bring it back too quickly,
taskbar still won't update grouping despite the new class, so we have to add
some delay before bringing window back. So here is a script I use:
```sh
#! /usr/bin/env sh
TIMEOUT=10 # seconds
T0=$(date +%s)
if [ $# -ne 2 ] ; then
echo "Usage: `basename $0`" '"class search regex" "new class"'
exit 1
fi
while [ $(( `date +%s` - T0 )) -lt $TIMEOUT ]; do
w=$(wmctrl -l -x | awk -v e="$1" '$3 ~ e { print $1 }' 2>/dev/null | head -n
1)
if [ -n "$w" ]; then
wmctrl -i -r $w -b add,skip_taskbar
xdotool set_window --class "$2" --classname "$2" $w
sleep 1
wmctrl -i -r $w -b remove,skip_taskbar
break
fi
done
```
Basically, we search for our window by class using regex, then hide it, change
its class and bring it back. All in a loop with a timeout, so we don't search
forever.
Save it somewhere in your `$PATH`, e.g. `~/.local/bin/change-window-class`
You can use it like this: `change-window-class "^class-regex-to-search-for"
"new-class"`
With Chromium web app:
`chromium --profile-directory="App - Google" --app=https://calendar.google.com
& change-window-class "^calendar.google.com" "web-app-google-calendar"`
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 434036] New: Plasma widgets show up in task manager.
https://bugs.kde.org/show_bug.cgi?id=434036 Bug ID: 434036 Summary: Plasma widgets show up in task manager. Product: plasmashell Version: 5.21.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: german...@hotmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 136419 --> https://bugs.kde.org/attachment.cgi?id=136419=edit Picture showing the plasma "app" in the task manager SUMMARY When a widget is opened like the Application launcher or the volume level popup, An application named "Plasma" appears in the task manager. When the widget is closed the icon disappears. STEPS TO REPRODUCE 1. Open a widget ex. Application launcher OBSERVED RESULT A new icon appears in the task manager. EXPECTED RESULT Plasma widgets shouldn't appear in the task manager, they are not applications. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro, Kernel 5.11.2 (available in About System) KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 434035] New: vgdb might crash if valgrind is killed
https://bugs.kde.org/show_bug.cgi?id=434035
Bug ID: 434035
Summary: vgdb might crash if valgrind is killed
Product: valgrind
Version: unspecified
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: m...@klomp.org
CC: pe...@palves.net, philippe.waroqui...@skynet.be
Target Milestone: ---
This is an odd corner case, but happens specifically with the gdb testcase make
check TESTS=gdb.base/valgrind-infcall-2.exp. At the end valgrind gets killed
with SIGKILL (-9) which cannot be blocked. But vgdb at the time is inside
waitstopped. It sees the process wasn't exited (WIFEXITED(status) is false) and
so assumes the process was stopped by a signal. Which it asserts:
assert (WIFSTOPPED(status));
signal_received = WSTOPSIG(status);
if (signal_received == signal_expected)
break;
But the assert fails and vgdb dumps core. The gdb testcase doesn't care,
because it already finished its test and just makes sure all processes are
gone. But it slowly fills your disk with core files (if you have enabled them)
when running the testsuite.
Proposed fix is to simply check first whether the program has termined normally
or by getting a fatal signal:
diff --git a/coregrind/vgdb-invoker-ptrace.c b/coregrind/vgdb-invoker-ptrace.c
index cb37677d5..389748960 100644
--- a/coregrind/vgdb-invoker-ptrace.c
+++ b/coregrind/vgdb-invoker-ptrace.c
@@ -267,7 +267,8 @@ Bool waitstopped (pid_t pid, int signal_expected, const
char *msg)
return False;
}
- if (WIFEXITED(status)) {
+ /* The process either exited or was terminated by a (fatal) signal. */
+ if (WIFEXITED(status) || WIFSIGNALED(status)) {
shutting_down = True;
return False;
}
--
You are receiving this mail because:
You are watching all bug changes.
[Falkon] [Bug 408312] Add filter to Preferences > Extensions
https://bugs.kde.org/show_bug.cgi?id=408312 Juraj changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/netw ||ork/falkon/commit/d8a706f3a ||981d730f46e35d3e2da42490541 ||29e2 Resolution|--- |FIXED --- Comment #2 from Juraj --- Git commit d8a706f3a981d730f46e35d3e2da4249054129e2 by Juraj Oravec, on behalf of Juraj Oravec. Committed on 06/03/2021 at 00:25. Pushed by jurajo into branch 'master'. Add filter to preferences extensions page Developed by: Yehor Tsyba @malibushko M +7-0src/lib/preferences/pluginslist.ui M +14 -0src/lib/preferences/pluginsmanager.cpp M +1-0src/lib/preferences/pluginsmanager.h M +1-1src/lib/tools/scripts.cpp https://invent.kde.org/network/falkon/commit/d8a706f3a981d730f46e35d3e2da4249054129e2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433036] [Wayland] Crash when configuring Window/Application settings while in the "Workspace Behaviour" or "Window Management" sections
https://bugs.kde.org/show_bug.cgi?id=433036
--- Comment #2 from magib...@hotmail.com ---
I can still reproduce in Plasma 5.21.2, from the "Desktop Effects" view as in
the screen recording in the first message.
> #0 0x in ?? ()
> #1 0x7efd1c8ab683 in
> QWaylandClientExtensionPrivate::handleRegistryGlobal (data=0x55919ee2c9a0,
> registry=0x55919d55f660, id=43, interface=..., version=1) at
> /usr/src/debug/qtwayland-everywhere-src-5.15.2/src/client/global/qwaylandclientextension.cpp:67
> #2 0x7efd1c893b32 in QtWaylandClient::QWaylandDisplay::registry_global
> (this=, id=43, interface=..., version=1) at
> /usr/src/debug/qtwayland-everywhere-src-5.15.2/src/client/qwaylanddisplay.cpp:396
> #3 0x7efd1c8b4dee in QtWayland::wl_registry::handle_global
> (data=0x55919d563300, object=, name=43,
> interface=0x55919f0be8e0 "org_kde_kwin_slide_manager", version=1) at
> qwayland-wayland.cpp:94
> #4 0x7efd1a386acd in ?? () from /usr/lib/libffi.so.7
> #5 0x7efd1a38603a in ?? () from /usr/lib/libffi.so.7
> #6 0x7efd1c819fe4 in wl_closure_invoke (closure=0x55919f0be800, flags=1,
> target=, opcode=0, data=) at
> ../wayland-1.19.0/src/connection.c:1018
> #7 0x7efd1c816563 in dispatch_event
> (display=display@entry=0x55919d563830, queue=,
> queue=) at ../wayland-1.19.0/src/wayland-client.c:1452
> #8 0x7efd1c817cac in dispatch_queue (queue=0x55919d563900,
> display=0x55919d563830) at ../wayland-1.19.0/src/wayland-client.c:1598
> #9 wl_display_dispatch_queue_pending (display=0x55919d563830,
> queue=0x55919d563900) at ../wayland-1.19.0/src/wayland-client.c:1840
> #10 0x7efd1c817d0d in wl_display_dispatch_pending (display= out>) at ../wayland-1.19.0/src/wayland-client.c:1903
> #11 0x7efd1c89344d in QtWaylandClient::QWaylandDisplay::flushRequests
> (this=0x55919d5632f0) at
> /usr/src/debug/qtwayland-everywhere-src-5.15.2/src/client/qwaylanddisplay.cpp:221
> #12 0x7efd1ed10dc0 in doActivate (sender=0x55919d589ca0,
> signal_index=3, argv=argv@entry=0x7ffd3ee085c0) at kernel/qobject.cpp:3898
> #13 0x7efd1ed09f20 in QMetaObject::activate
> (sender=sender@entry=0x55919d589ca0, m=m@entry=0x7efd1ef717a0
> ,
> local_signal_index=local_signal_index@entry=0,
> argv=argv@entry=0x7ffd3ee085c0) at kernel/qobject.cpp:3946
> #14 0x7efd1ed142f0 in QSocketNotifier::activated
> (this=this@entry=0x55919d589ca0, _t1=..., _t2=, _t3=...) at
> .moc/moc_qsocketnotifier.cpp:178
> #15 0x7efd1ed14afd in QSocketNotifier::event (this=0x55919d589ca0,
> e=0x7ffd3ee086d0) at kernel/qsocketnotifier.cpp:302
> #16 0x7efd1f89c752 in QApplicationPrivate::notify_helper (this= out>, receiver=0x55919d589ca0, e=0x7ffd3ee086d0) at
> kernel/qapplication.cpp:3632
> #17 0x7efd1ecd9a2a in QCoreApplication::notifyInternal2
> (receiver=0x55919d589ca0, event=0x7ffd3ee086d0) at
> kernel/qcoreapplication.cpp:1063
> #18 0x7efd1ed332a6 in socketNotifierSourceDispatch
> (source=0x55919d5aae00) at kernel/qeventdispatcher_glib.cpp:107
> #19 0x7efd1c9a5b84 in g_main_context_dispatch () from
> /usr/lib/libglib-2.0.so.0
> #20 0x7efd1c9f9c21 in ?? () from /usr/lib/libglib-2.0.so.0
> #21 0x7efd1c9a43b1 in g_main_context_iteration () from
> /usr/lib/libglib-2.0.so.0
> #22 0x7efd1ed32691 in QEventDispatcherGlib::processEvents
> (this=0x55919d579640, flags=...) at kernel/qeventdispatcher_glib.cpp:423
> #23 0x7efd1ecd83ac in QEventLoop::exec (this=this@entry=0x7ffd3ee08930,
> flags=..., flags@entry=...) at
> ../../include/QtCore/../../src/corelib/global/qflags.h:69
> #24 0x7efd1ece0844 in QCoreApplication::exec () at
> ../../include/QtCore/../../src/corelib/global/qflags.h:121
> #25 0x7efd1f1a184e in QGuiApplication::exec () at
> kernel/qguiapplication.cpp:1867
> #26 0x7efd1f89c6c6 in QApplication::exec () at
> kernel/qapplication.cpp:2824
> #27 0x55919bbec960 in main (argc=, argv=0x7ffd3ee08a60) at
> /usr/src/debug/systemsettings-5.21.2/app/main.cpp:222
> (gdb) frame 1
> #1 0x7fd59ca70683 in
> QWaylandClientExtensionPrivate::handleRegistryGlobal (data=0x55c040570740,
> registry=0x55c03edff660, id=44, interface=..., version=1) at
> /usr/src/debug/qtwayland-everywhere-src-5.15.2/src/client/global/qwaylandclientextension.cpp:67
> 67if (interface ==
> QLatin1String(extension->extensionInterface()->name) &&
> !extension->d_func()->active) {
> (gdb) print *extension
> $1 = { = {_vptr.QObject = 0x55919d553f50, static staticMetaObject =
> {d = {superdata = {direct = 0x0}, stringdata = 0x7efd1eea5720
> , data = 0x7efd1eea5600 ,
> static_metacall = 0x7efd1ed0f4d0 QMetaObject::Call, int, void**)>, relatedMetaObjects = 0x0, extradata =
> 0x0}}, d_ptr = {d = 0x55919f062d20}, static staticQtMetaObject = {d =
> {superdata = {direct = 0x0}, stringdata = 0x7efd1eea86c0
> , data = 0x7efd1eea5840 ,
> static_metacall = 0x0, relatedMetaObjects = 0x0, extradata = 0x0}}}, static
> staticMetaObject = {d = {superdata = {direct
[kdevelop] [Bug 434031] Code parsing stalls (and hogs cpu) on clang_parseTranslationUnit2 error
https://bugs.kde.org/show_bug.cgi?id=434031 --- Comment #1 from Raúl --- Created attachment 136418 --> https://bugs.kde.org/attachment.cgi?id=136418=edit standalone clang invokation + backtrace I've mangled paths to avoid some non-relevant information disclosuring -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434034] New: Refresh the list of printers after removing one of them
https://bugs.kde.org/show_bug.cgi?id=434034 Bug ID: 434034 Summary: Refresh the list of printers after removing one of them Product: systemsettings Version: 5.21.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_printer_manager Assignee: dantt...@gmail.com Reporter: es204904...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- https://youtu.be/yqwf4JW9YB4 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434032] Unable to save printer settings after adding the printer manually, or changing its driver
https://bugs.kde.org/show_bug.cgi?id=434032 Alberto Salvia Novella changed: What|Removed |Added CC||es204904...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434032] Unable to save printer settings after adding the printer manually, or changing its driver
https://bugs.kde.org/show_bug.cgi?id=434032 --- Comment #1 from Alberto Salvia Novella --- Created attachment 136417 --> https://bugs.kde.org/attachment.cgi?id=136417=edit errors.log -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 434033] New: Download of KNewStuff files fails for zip files
https://bugs.kde.org/show_bug.cgi?id=434033 Bug ID: 434033 Summary: Download of KNewStuff files fails for zip files Product: frameworks-knewstuff Version: 5.79.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: major Priority: NOR Component: general Assignee: ad...@leinir.dk Reporter: mutla...@ikarustech.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY We are receiving many reports in KStars that catalog addons cannot be installed under Windows 10. The same catalogs are installed fine on KStars Linux & MacOS versions. This is the error: [2021-03-05T16:53:12.308 Arab Standard Time WARN ][ default] - QMimeDatabase: Error loading internal MIME data An error has been encountered at line 1 of : Premature end of document.: [2021-03-05T16:53:12.308 Arab Standard Time CRIT ][ kf.newstuff.core] - Could not determine type of archive file ' "C:/Users/mutla/AppData/Local/Temp/asBMsq-abell_pn_1.0.zip" ' When checking the zip file above, it's a valid ZIP file and I can open it just fine. STEPS TO REPRODUCE 1. Open KStars on Windows 10 2. Go to Data --> Download New Data 3. Try to download any catalog and it would say "File not found" error. OBSERVED RESULT Catalog downloaded but not installed. EXPECTED RESULT Catalog downloaded and installed. SOFTWARE/OS VERSIONS KStars built using KDE Binary Factory, so whatever used by KDE Binary Factory as of March 1st, 2021. Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433986] Links in XWayland apps are not functional
https://bugs.kde.org/show_bug.cgi?id=433986 Alex changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #2 from Alex --- (In reply to Nate Graham from comment #1) > Does it open in the browser, but the browser remains in the background > rather than being brought forward as you wwould expect? What was happening is the link just wasn't opening at all, it opening in the background was the previous behaviour. Anyway, I don't get this issue anymore after a relog, so I'll close it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434032] New: Unable to save printer settings after adding the printer manually, or changing its driver
https://bugs.kde.org/show_bug.cgi?id=434032 Bug ID: 434032 Summary: Unable to save printer settings after adding the printer manually, or changing its driver Product: systemsettings Version: 5.21.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_printer_manager Assignee: dantt...@gmail.com Reporter: es204904...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- It doesn't happen on the CUPS web interface. Screencast: https://youtu.be/g7bXjJXdeeo -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 432952] [Master] Restore Defaults for Canvas Input Settings softly removes all the canvas input shortcuts
https://bugs.kde.org/show_bug.cgi?id=432952 vanyossi changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|DUPLICATE |--- Ever confirmed|0 |1 --- Comment #3 from vanyossi --- Reopening -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 434003] Color Selector Settings restore to defaults when pressed when other section is active i.e. Tablet settings
https://bugs.kde.org/show_bug.cgi?id=434003 vanyossi changed: What|Removed |Added Summary|Ambiguous Restore Defaults |Color Selector Settings |Button, it appears to be|restore to defaults when |for the current section.|pressed when other section ||is active i.e. Tablet ||settings -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 434003] Ambiguous Restore Defaults Button, it appears to be for the current section.
https://bugs.kde.org/show_bug.cgi?id=434003 --- Comment #5 from vanyossi --- Im a little tired, didn't notice this :3 Ill restore and recheck both bugs -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 433992] Kdenlive crashes when user tries to add ogg file
https://bugs.kde.org/show_bug.cgi?id=433992 --- Comment #3 from farid --- Created attachment 136416 --> https://bugs.kde.org/attachment.cgi?id=136416=edit ogg in timeline I am unable to reproduce but have seen people talking about this elsewhere... -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 434031] New: Code parsing stalls (and hogs cpu) on clang_parseTranslationUnit2 error
https://bugs.kde.org/show_bug.cgi?id=434031
Bug ID: 434031
Summary: Code parsing stalls (and hogs cpu) on
clang_parseTranslationUnit2 error
Product: kdevelop
Version: 5.6.2
Platform: Debian testing
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Language Support: CPP (Clang-based)
Assignee: kdevelop-bugs-n...@kde.org
Reporter: rasas...@gmail.com
Target Milestone: ---
Created attachment 136415
--> https://bugs.kde.org/attachment.cgi?id=136415=edit
all threads backtrace after 99% parsing and ctrl-Q kdevelop
When kdevelope is parsing a somewhat big project, with includes properly
configured so all code dependencies are captured, clang parser shows an error,
the background parser never ends parsing (stalled at 99%). Moreover on kdevelop
quit (ctrl-Q) the background parser keeps on running hogging the CPU
STEPS TO REPRODUCE
1. Start with a recent zephyr project checkout:
https://docs.zephyrproject.org/latest/getting_started/index.html (up to west
init step)
2. Open zephyr rtos recent version as project (CMake based)
3. Add some important parsing paths in the project language parsing
configuration:
zephyrproject/modules/lib/mcumgr/mgmt/include
zephyrproject/modules/lib/mcumgr/smp/include
zephyrproject/modules/lib/tinycbor/include
zephyrproject/bootloader/mcuboot/boot/bootutil/include
zephyrproject/zephyr/include
zephyrproject/bootloader/mcuboot/boot/zephyr/include
4. Let kdevelop parse the code
OBSERVED RESULT
Background parsing stalls at 99% and exit kdevelop keeps background parser
running, even GUI has been shutdown. You'd need to kill kdevelop (again) for it
to exit.
EXPECTED RESULT
kdevelop properly parses code, tolerates parsing failures or at least stop
background parsing.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian testing
kdevelop 5.6.2
KDE Frameworks 5.78.0
Qt 5.15.2
ADDITIONAL INFORMATION
I'm attaching an all threads backtrace. See how there are 2 lengthy stacked
frames threads
console output:
libclang: crash detected during parsing: {
'source_filename' : 'zephyrproject/zephyr/drivers/dac/dac_dacx0508.c'
'command_line_args' : ['clang', '-ferror-limit=100', '-fspell-checking', '',
'-Wunused-parameter', '-Wunreachable-code', '-Wall', '-std=c99', '-nostdinc',
'-xc', '-isystemzephyrproject/modules/lib/mcumgr/mgmt/include',
'-isystemzephyrproject/modules/lib/mcumgr/smp/include',
'-isystemzephyrproject/modules/lib/tinycbor/include',
'-isystemzephyrproject/bootloader/mcuboot/boot/bootutil/include',
'-isystem/usr/lib/gcc/arm-none-eabi/8.3.1/include',
'-isystem/usr/lib/gcc/arm-none-eabi/8.3.1/include-fixed',
'-isystem/usr/include/newlib', '-Izephyrproject/zephyr/include',
'-Izephyrproject/bootloader/mcuboot/boot/zephyr/include', '-isystem',
'/usr/lib/llvm-11/lib/clang/11.0.1/include', '-imacros',
'/tmp/kdevelop.uxcuiC'],
'unsaved_files' : [],
'options' : 513,
}
kdevelop.plugins.clang: clang_parseTranslationUnit2 return with error code 2
kdevelop.plugins.clang: (start KDevelop with `KDEV_CLANG_DISPLAY_DIAGS=1
kdevelop` to see more diagnostics)
kdevelop.plugins.clang: Failed to parse translation unit:
"zephyrproject/zephyr/drivers/dac/dac_dacx0508.c"
libclang: crash detected during parsing: {
'source_filename' : 'zephyrproject/zephyr/subsys/usb/class/audio/audio.c'
'command_line_args' : ['clang', '-ferror-limit=100', '-fspell-checking', '',
'-Wunused-parameter', '-Wunreachable-code', '-Wall', '-std=c99', '-nostdinc',
'-xc', '-isystemzephyrproject/modules/lib/mcumgr/mgmt/include',
'-isystemzephyrproject/modules/lib/mcumgr/smp/include',
'-isystemzephyrproject/modules/lib/tinycbor/include',
'-isystemzephyrproject/bootloader/mcuboot/boot/bootutil/include',
'-isystem/usr/lib/gcc/arm-none-eabi/8.3.1/include',
'-isystem/usr/lib/gcc/arm-none-eabi/8.3.1/include-fixed',
'-isystem/usr/include/newlib', '-Izephyrproject/zephyr/include',
'-Izephyrproject/bootloader/mcuboot/boot/zephyr/include', '-isystem',
'/usr/lib/llvm-11/lib/clang/11.0.1/include', '-imacros',
'/tmp/kdevelop.hjUibn'],
'unsaved_files' : [],
'options' : 513,
}
kdevelop.plugins.clang: clang_parseTranslationUnit2 return with error code 2
kdevelop.plugins.clang: (start KDevelop with `KDEV_CLANG_DISPLAY_DIAGS=1
kdevelop` to see more diagnostics)
kdevelop.plugins.clang: Failed to parse translation unit:
"zephyrproject/zephyr/subsys/usb/class/audio/audio.c"
--
You are receiving this mail because:
You are watching all bug changes.
[krita] [Bug 434003] Ambiguous Restore Defaults Button, it appears to be for the current section.
https://bugs.kde.org/show_bug.cgi?id=434003 --- Comment #4 from tomtomtomreportin...@gmail.com --- I do not think this is a problem of visual cue. If you click Restore Defaults in the Keyboard Shortcuts interface, it only resets the Keyboard Shortcuts. If you click Restore Defaults in the Canvas Input Settings, it only resets the Canvas Input Settings, and so on. I would think this modular resetting is intentional, especially as there's already a "Reset Krita Configurations" option under the Settings in the menu bar. Also, as I said in the other report, I do not think it's a duplicate either. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 432952] [Master] Restore Defaults for Canvas Input Settings softly removes all the canvas input shortcuts
https://bugs.kde.org/show_bug.cgi?id=432952 --- Comment #2 from tomtomtomreportin...@gmail.com --- Uh, I do not believe this bug is a duplicate? I am reporting an entirely separate issue that only exists in the upcoming 5.0. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 433944] Brush outline unwanted grid snapping after editing pen pressure curve
https://bugs.kde.org/show_bug.cgi?id=433944 vanyossi changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||ghe...@gmail.com Resolution|--- |WAITINGFORINFO --- Comment #1 from vanyossi --- Could you please explain/show this with a screen record? I can't acuatlly notice anything on my side. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 433321] Arrows of screenshots gallery don't always work
https://bugs.kde.org/show_bug.cgi?id=433321 nttkde changed: What|Removed |Added CC||watisthis...@outlook.com --- Comment #2 from nttkde --- -Also, optimally, the arrows should take the screenshot gallery(/window) width into account and hide when it's wide enough to show all screenshots at once (as the arrows are then unnecessary and obviously won't do anything when user clicks on them). Currently, the logic seems to be the arrows are hidden when there is only one screenshot. On the other hand, the horizontal gallery scrollbar does hide correctly based on gallery width. -And the current way it works, as Nate said, causes also another bug; the arrows aren't affected by the horizontal gallery scrollbar. If I drag the scrollbar to the right side and then press the right arrow, it'll jump back to the second screenshot from the start. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 434003] Ambiguous Restore Defaults Button, it appears to be for the current section.
https://bugs.kde.org/show_bug.cgi?id=434003 vanyossi changed: What|Removed |Added Summary|Restore Defaults restores |Ambiguous Restore Defaults |too much|Button, it appears to be ||for the current section. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 433356] Kdenlive crashes when editing a title clip and clicking both mouse buttons at the same time.
https://bugs.kde.org/show_bug.cgi?id=433356 Julius Künzel changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 416341] Project generated by old version 18.04 cannot be opened by new version 19.12
https://bugs.kde.org/show_bug.cgi?id=416341 Julius Künzel changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 432952] [Master] Restore Defaults for Canvas Input Settings softly removes all the canvas input shortcuts
https://bugs.kde.org/show_bug.cgi?id=432952 vanyossi changed: What|Removed |Added CC||ghe...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from vanyossi --- *** This bug has been marked as a duplicate of bug 434003 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 434003] Restore Defaults restores too much
https://bugs.kde.org/show_bug.cgi?id=434003 vanyossi changed: What|Removed |Added CC||tomtomtomreportingin@gmail. ||com --- Comment #3 from vanyossi --- *** Bug 432952 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 433992] Kdenlive crashes when user tries to add ogg file
https://bugs.kde.org/show_bug.cgi?id=433992 --- Comment #2 from norwegian_panca...@protonmail.ch --- Created attachment 136414 --> https://bugs.kde.org/attachment.cgi?id=136414=edit console output of bug procedure I forgot to specify - I used the appimage and not the OS-specific version. I used it on openSUSE Tumbleweed. I tried the same procedure on Debian 10 and the appimage still crashes. Here is the link (https://commons.wikimedia.org/wiki/File:Erik_Satie_-_gymnopedies_-_la_1_ere._lent_et_douloureux.ogg) to the file I used. Any ogg file will crash kdenlive. I cannot upload it here because it is too large. I also attached a screenshot of the console output when adding the ogg file to kdenlive. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 434003] Restore Defaults restores too much
https://bugs.kde.org/show_bug.cgi?id=434003 --- Comment #2 from vanyossi --- Created attachment 136413 --> https://bugs.kde.org/attachment.cgi?id=136413=edit restore settings button appears to be from open section -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 434030] New: Errores comunes
https://bugs.kde.org/show_bug.cgi?id=434030 Bug ID: 434030 Summary: Errores comunes Product: Discover Version: 5.21.1 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: pokepih...@nobitcoin.net CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.21.1) Qt Version: 5.15.2 Frameworks Version: 5.79.0 Operating System: Linux 5.4.0-66-generic x86_64 Windowing System: X11 Drkonqi Version: 5.21.1 Distribution: KDE neon User Edition 5.21 The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault [New LWP 17299] [New LWP 17300] [New LWP 17301] [New LWP 17302] [New LWP 17303] [New LWP 17304] [New LWP 17305] [New LWP 17306] [New LWP 17307] [New LWP 17308] [New LWP 17309] [New LWP 17310] [New LWP 17311] [New LWP 17312] [New LWP 17313] [New LWP 17314] [New LWP 17315] [New LWP 17316] [New LWP 17334] [New LWP 17336] [New LWP 17374] [New LWP 17383] [New LWP 17384] [New LWP 17385] [New LWP 17386] [New LWP 17387] [New LWP 17388] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". futex_wait_cancelable (private=, expected=0, futex_word=0x55681f431b40) at ../sysdeps/nptl/futex-internal.h:183 [Current thread is 1 (Thread 0x7fec44dc8e40 (LWP 17296))] Thread 28 (Thread 0x7feba9ffb700 (LWP 17388)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7feba9ffab90, clockid=, expected=0, futex_word=0x5568205677f0) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7feba9ffab90, clockid=, mutex=0x5568205677a0, cond=0x5568205677c8) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x5568205677c8, mutex=0x5568205677a0, abstime=0x7feba9ffab90) at pthread_cond_wait.c:656 #3 0x7fec49720ca8 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fec4971e1b1 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fec4971abac in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fec486b3609 in start_thread (arg=) at pthread_create.c:477 #7 0x7fec4939c293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 27 (Thread 0x7febaa7fc700 (LWP 17387)): #0 0x7fec4995a889 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7fec4995911d in QTimerInfoList::updateCurrentTime() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fec499596f9 in QTimerInfoList::timerWait(timespec&) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fec4995ad16 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fec47d0570f in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fec47d060bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fec47d062c3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fec4995afbb in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fec498ff1ab in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fec49719a12 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fec4971abac in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fec486b3609 in start_thread (arg=) at pthread_create.c:477 #12 0x7fec4939c293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 26 (Thread 0x7febaaffd700 (LWP 17386)): #0 futex_abstimed_wait_cancelable (private=, abstime=0x7febaaffcb90, clockid=, expected=0, futex_word=0x7feb8c005dd0) at ../sysdeps/nptl/futex-internal.h:320 #1 __pthread_cond_wait_common (abstime=0x7febaaffcb90, clockid=, mutex=0x7feb8c005d80, cond=0x7feb8c005da8) at pthread_cond_wait.c:520 #2 __pthread_cond_timedwait (cond=0x7feb8c005da8, mutex=0x7feb8c005d80, abstime=0x7febaaffcb90) at pthread_cond_wait.c:656 #3 0x7fec49720ca8 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fec4971e1b1 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fec4971abac in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fec486b3609 in start_thread (arg=) at pthread_create.c:477 #7 0x7fec4939c293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 25 (Thread 0x7febab7fe700 (LWP 17385)): #0 0x7fec47d0407d in g_source_ref () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7fec47d04148 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fec47d05adf in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fec47d06132 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fec47d062c3 in
[krita] [Bug 434003] Restore Defaults restores too much
https://bugs.kde.org/show_bug.cgi?id=434003 vanyossi changed: What|Removed |Added CC||ghe...@gmail.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from vanyossi --- The button is not from the tablet curve setting, the button is for all krita settings. I will confirm this bug given it is confusing there is no visual "cue" to distingish this button as being global -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433576] Compose Key does not work since Plasma 5.21 on Wayland
https://bugs.kde.org/show_bug.cgi?id=433576 Göran Uddeborg changed: What|Removed |Added CC||goe...@uddeborg.se -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405388] Virtual keyboard implementation forces compositor-side input method handling on wayland clients
https://bugs.kde.org/show_bug.cgi?id=405388 Andrey changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=411729 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411729] Accented and dead keys do not work when QT_IM_MODULE is set to anything
https://bugs.kde.org/show_bug.cgi?id=411729 Andrey changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=405388 --- Comment #31 from Andrey --- Could it be related to this? client: rework input method handling: https://codereview.qt-project.org/c/qt/qtwayland/+/248181 If so, the bug can be on our side: "Some users might mistakenly think that this patch introduces a regression with Qt on KDE, but it is actually a KWin/Wayland compositor bug: https://bugs.kde.org/show_bug.cgi?id=405388; -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 433936] Feature Requests: Jump to next/previous cut, Ripple Edit, Trim one frame at a time, Adjustment Layers, Extend Edit, Opening multiple sequences
https://bugs.kde.org/show_bug.cgi?id=433936
--- Comment #4 from candideu ---
(In reply to Julius Künzel from comment #2)
> Extend edit is already possible as far as I understood: the actions are
> called "Resize Item Start" and "Resize Item End" the default shortcuts are
> "(" and ")". Please try whether this is what you meant…
WOW, thank you Julius! This is exactly what I meant, I just had no clue it
existed already.
--
You are receiving this mail because:
You are watching all bug changes.
[kdenlive] [Bug 433936] Feature Requests: Jump to next/previous cut, Ripple Edit, Trim one frame at a time, Adjustment Layers, Extend Edit, Opening multiple sequences
https://bugs.kde.org/show_bug.cgi?id=433936 --- Comment #3 from candideu --- (In reply to Jean-Baptiste Mardelle from comment #1) > Thanks for your feedback, here is the current status regarding your > questions: > > * Moving to next/previous cut can be achieved with ALT+Left/Right arrows. > * Ripple edit is on our roadmap > * Adjustment layers: I agree this is a handy feature. There is currently no > way to achieve this easily in our video backend but we have room for > improvement in how we manage effects. For example effects can have an in/out > point, so we could implement a way to apply an effect on all clips in the > timeline in a certain zone... that would be a start, I will think about it. > * Extend edit: nice idea, this could easily be implement. > * Multiple sequence edit: on our roadmap, probably for the august release of > Kdenlive 21.08 Thank you for the first tip Jean-Baptiste! I'm learning new things about Kdenlive every day. :D It's exciting to hear that some of these are on Kdenlive's radar. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 425931] Application: Kontact (kontact), signal: Segmentation fault
https://bugs.kde.org/show_bug.cgi?id=425931 --- Comment #20 from john4deidre2...@xtra.co.nz --- Created attachment 136412 --> https://bugs.kde.org/attachment.cgi?id=136412=edit New crash information added by DrKonqi kontact (5.16.2 (20.12.2)) using Qt 5.15.2 - What I was doing when the application crashed: starting kontact once again and it crashed. this seems to be a very long standing bug and an annoying one at that -- Backtrace (Reduced): #4 0x7fbe92c6d5f7 in std::__atomic_base::load (__m=std::memory_order_relaxed, this=) at /usr/include/c++/10/bits/atomic_base.h:426 #5 QAtomicOps::loadRelaxed (_q_value=...) at ../../include/QtCore/../../src/corelib/thread/qatomic_cxx11.h:239 #6 QBasicAtomicInteger::loadRelaxed (this=) at ../../include/QtCore/../../src/corelib/thread/qbasicatomic.h:107 #7 QtPrivate::RefCount::isShared (this=) at ../../include/QtCore/../../src/corelib/tools/qrefcount.h:101 #8 QList::append (this=0x562382d87020, t=@0x7ffe83e50530: 0x562384bdc590) at ../../include/QtCore/../../src/corelib/tools/qlist.h:622 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433799] item geometries not created for new user accounts created using lookandfeel and/or layout templates
https://bugs.kde.org/show_bug.cgi?id=433799 --- Comment #15 from Jeff Hodd --- Am doing a test build. I'll let you know if that fixes it. The source code changes appear to be what's needed. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 422102] Can't login to freesound to download high-quality audios
https://bugs.kde.org/show_bug.cgi?id=422102 Julius Künzel changed: What|Removed |Added Resolution|--- |UNMAINTAINED CC||jk.kde...@smartlab.uber.spa ||ce Status|REPORTED|RESOLVED --- Comment #1 from Julius Künzel --- There have been several fixed for the online resources and finally they got a rewrite so this bug refers to code that does not exist anymore and I am closing this now. Feel free to create a new report if you find another bug with the new online resource implementation in version 21.04 (going to be released in April 2021) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 409700] A GUI glitch in the Effects selector
https://bugs.kde.org/show_bug.cgi?id=409700 Julius Künzel changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO CC||jk.kde...@smartlab.uber.spa ||ce --- Comment #5 from Julius Künzel --- Can you please update to the latest version (20.12.2 at the moment, https://kdenlive.org/en/download/) and report here whether this is still happening? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433979] American tax forms checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=433979 --- Comment #9 from Leonard Lausen --- I built Okular 20.04.3 against poppler 0.86 (which matches the versions used in Ubuntu 20.04), but the issue persists on my system. Do you have any suggestions how to further debug? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 405388] Virtual keyboard implementation forces compositor-side input method handling on wayland clients
https://bugs.kde.org/show_bug.cgi?id=405388 Andrey changed: What|Removed |Added CC||butir...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 417772] When audio is playing in google chrome or chromium, plasma doesnt distinguish the both
https://bugs.kde.org/show_bug.cgi?id=417772 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #3 from Nicolas Fella --- I can't reproduce this with current Plasma master, neither with Chrome/Chromium nor Firefox/Firefox Developer Edition -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 434029] New: File access to smb share by backup program causes Dolphin to hang
https://bugs.kde.org/show_bug.cgi?id=434029 Bug ID: 434029 Summary: File access to smb share by backup program causes Dolphin to hang Product: frameworks-kio Version: 5.79.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kio-bugs-n...@kde.org Reporter: k...@paulmcauley.com CC: kdelibs-b...@kde.org Target Milestone: --- I have configured my backups to a SMB network share using Deja-Dup/Duplicity. The SMB location was mapped as a Network Folder through Dolphin. Deja-Dup backs up to a SMB directory with hundreds of files. The problem is that when a backup is being performed to the network I cannot use Dolphin. It does not open initially and will hang for many seconds before opening. When open, Dolphin becomes unresponsive. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.2 KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.3.18-lp152.63-default OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-7700HQ CPU @ 2.80GHz Memory: 31.2 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433987] Login scripts don't start in systemd mode
https://bugs.kde.org/show_bug.cgi?id=433987 Nicolas Fella changed: What|Removed |Added Assignee|nicolas.fe...@gmx.de|k...@davidedmundson.co.uk -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 302474] Only emit tick sound on releasing mouse cursor
https://bugs.kde.org/show_bug.cgi?id=302474 Jonathan Marten changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 302361] Don’t "tick" when volume is full
https://bugs.kde.org/show_bug.cgi?id=302361 Jonathan Marten changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 323608] "Volume Feedback" doesn't work
https://bugs.kde.org/show_bug.cgi?id=323608 Jonathan Marten changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED CC||j...@keelhaul.me.uk --- Comment #6 from Jonathan Marten --- The previous commit makes some changes to volume feedback which means that it should work with both PulseAudio and ALSA (and in theory also OSS, but not tested). Please reopen if there are still problems as reported. -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 302474] Only emit tick sound on releasing mouse cursor
https://bugs.kde.org/show_bug.cgi?id=302474 Jonathan Marten changed: What|Removed |Added CC||j...@keelhaul.me.uk --- Comment #2 from Jonathan Marten --- The previous commit should have addressed the problem - the feedback sound does not actually take account of the mouse button being down over the slider, but there is a minimum delay which means that continuous sounds do not merge into one. Please reopen the bug if this does not seem to be working or if there is still a problem. -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 302361] Don’t "tick" when volume is full
https://bugs.kde.org/show_bug.cgi?id=302361 Jonathan Marten changed: What|Removed |Added CC||j...@keelhaul.me.uk --- Comment #3 from Jonathan Marten --- The previous commit should have fixed the problem - the feedback does not now sound unless the volume actually changes. Please reopen the bug if still observed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434028] New: Year 0 in the Calendar applet is broken
https://bugs.kde.org/show_bug.cgi?id=434028 Bug ID: 434028 Summary: Year 0 in the Calendar applet is broken Product: plasmashell Version: 5.21.1 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Calendar Assignee: plasma-b...@kde.org Reporter: gamingforyou...@gmail.com Target Milestone: 1.0 Created attachment 136411 --> https://bugs.kde.org/attachment.cgi?id=136411=edit Year 0 week view SUMMARY The difference between this bug report and the one I opened a little while ago, is that this time, you have to have "Astronomical Events" and "Holidays" turned OFF. The bug sure is interesting (nonsense.png). STEPS TO REPRODUCE 1. Scroll back to year 0 - 9 (from the decade view). 2. Click on year 10 (between year -1 and 1) OBSERVED RESULT The name of the year in the week view turns into Nan. Going into the week view utterly breaks everything. EXPECTED RESULT Show year 0 properly. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 5.11.1, KDE Plasma 5.21.1 (available in About System) KDE Plasma Version: 5.21.1 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION I know I shouldn't be proposing solutions, but the 3 bug reports I opened could be fixed easily by not allowing the user to scroll past for example the 1900s. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433979] American tax forms checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=433979 --- Comment #8 from Leonard Lausen --- I rebuilt Okular 20.12.2 against poppler 0.86, but the issue persists on my system. Any ideas what component could cause the issue? -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 415352] Kdenlive crashes on Title creation inside the clips.
https://bugs.kde.org/show_bug.cgi?id=415352 Julius Künzel changed: What|Removed |Added CC||jk.kde...@smartlab.uber.spa ||ce Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from Julius Künzel --- Can you please update to the latest version (20.12.2 at the moment, https://kdenlive.org/en/download/) and report here whether this is still happening? -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 434013] Favorited apps are no longer weighted more heavily in search results
https://bugs.kde.org/show_bug.cgi?id=434013 Nate Graham changed: What|Removed |Added CC||n...@kde.org Summary|Bad search results |Favorited apps are no ||longer weighted more ||heavily in search results Keywords||regression, usability -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 433936] Feature Requests: Jump to next/previous cut, Ripple Edit, Trim one frame at a time, Adjustment Layers, Extend Edit, Opening multiple sequences
https://bugs.kde.org/show_bug.cgi?id=433936
Julius Künzel changed:
What|Removed |Added
CC||jk.kde...@smartlab.uber.spa
||ce
--- Comment #2 from Julius Künzel ---
Extend edit is already possible as far as I understood: the actions are called
"Resize Item Start" and "Resize Item End" the default shortcuts are "(" and
")". Please try whether this is what you meant…
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kio] [Bug 433965] kiod crashlooping
https://bugs.kde.org/show_bug.cgi?id=433965 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |BACKTRACE Status|REPORTED|NEEDSINFO --- Comment #1 from Nate Graham --- Can you attach an example crashlog? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 433979] American tax forms checkbox state cannot been seen when form is hidden
https://bugs.kde.org/show_bug.cgi?id=433979 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433986] Links in XWayland apps are not functional
https://bugs.kde.org/show_bug.cgi?id=433986 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||n...@kde.org Resolution|--- |WAITINGFORINFO --- Comment #1 from Nate Graham --- Does it open in the browser, but the browser remains in the background rather than being brought forward as you wwould expect? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427340] Systemd startup: things in autostart don't autostart when using a custom prefix
https://bugs.kde.org/show_bug.cgi?id=427340 Nate Graham changed: What|Removed |Added Assignee|k...@davidedmundson.co.uk|nicolas.fe...@gmx.de Target Milestone|1.0 |--- Product|plasmashell |systemsettings Component|general |kcm_autostart Version|master |5.21.2 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 431871] Updating proprietary Nvidia drivers on OpenSUSE Tumbleweed requires multiple license agreements
https://bugs.kde.org/show_bug.cgi?id=431871 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #2 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/discover/-/merge_requests/90 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433987] Login scripts don't start in systemd mode
https://bugs.kde.org/show_bug.cgi?id=433987 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=433299 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434027] New: Scrolling past year -1 still crashes Plasma
https://bugs.kde.org/show_bug.cgi?id=434027 Bug ID: 434027 Summary: Scrolling past year -1 still crashes Plasma Product: plasmashell Version: 5.21.1 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Calendar Assignee: plasma-b...@kde.org Reporter: gamingforyou...@gmail.com Target Milestone: 1.0 Created attachment 136410 --> https://bugs.kde.org/attachment.cgi?id=136410=edit Crash log SUMMARY I opened a bug report a few months ago about this, and the fix didn't really fix the issue. It's still possible to access years before 0. STEPS TO REPRODUCE 1. Turn on "Astronomical Events" or "Holidays" from the calendar applet settings. 2. From the decade view, scroll to year 0 - 9. 3. Click on the year -1. 4. From the week/day view, scroll into the past. OBSERVED RESULT Plasma crashes. EXPECTED RESULT Not being able to access years before 0. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux 5.11.1, KDE Plasma 5.21.1 (available in About System) KDE Plasma Version: 5.21.1 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433299] [systemd] Applications meant to autostart do not start after switching to systemd
https://bugs.kde.org/show_bug.cgi?id=433299 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=433987 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433987] Login scripts don't start in systemd mode
https://bugs.kde.org/show_bug.cgi?id=433987 Nate Graham changed: What|Removed |Added Component|general |kcm_autostart Product|ksmserver |systemsettings CC||n...@kde.org Assignee|k...@davidedmundson.co.uk|nicolas.fe...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
