[krunner] [Bug 429177] wayland: krunner position no longer follows window rules and can't be set to "under mouse"
https://bugs.kde.org/show_bug.cgi?id=429177 Dmitry Misharov changed: What|Removed |Added CC||quarcks...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437645] New: [Wayland] System settings crashes
https://bugs.kde.org/show_bug.cgi?id=437645 Bug ID: 437645 Summary: [Wayland] System settings crashes Product: systemsettings Version: 5.21.5 Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: quarcks...@gmail.com Target Milestone: --- Application: systemsettings5 (5.21.5) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.4.0-73-generic x86_64 Windowing System: Wayland Drkonqi Version: 5.21.5 Distribution: KDE neon User Edition 5.21 -- Information about the crash: What I was doing when the application crashed: 1. Open systemsettings 2. Go to Window Management -> Window Rules 3. Create a new rule or adjust existing one Actual result: The application crashes but the rule was saved. Expected result: Systemsettings shouldn't crash on changing Window Rules The crash can be reproduced every time. -- Backtrace: Application: System Settings (systemsettings5), signal: Segmentation fault [New LWP 12541] [New LWP 12542] [New LWP 12543] [New LWP 12544] [New LWP 12545] [New LWP 12546] [New LWP 12547] [New LWP 12638] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f0c8d73baff in poll () from /lib/x86_64-linux-gnu/libc.so.6 [Current thread is 1 (Thread 0x7f0c894fb500 (LWP 12540))] Thread 9 (Thread 0x7f0c5866a700 (LWP 12638)): #0 0x7f0c8d73717c in read () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f0c8b955b2f in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0c8b90cebe in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0c8b90d312 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f0c8b90d4a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f0c8de55ffb in QEventDispatcherGlib::processEvents (this=0x7f0c50248610, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f0c8ddfa1eb in QEventLoop::exec (this=this@entry=0x7f0c58669cc0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #7 0x7f0c8dc14a52 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #8 0x7f0c8cf08fa9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7f0c8dc15bec in QThreadPrivate::start (arg=0x5580e54d0ac0) at thread/qthread_unix.cpp:329 #10 0x7f0c8c2cc609 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #11 0x7f0c8d748293 in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 8 (Thread 0x7f0c635ef700 (LWP 12547)): #0 0x7f0c8b95a500 in g_mutex_unlock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f0c8b90cd99 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0c8b90d312 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0c8b90d4a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f0c8de55ffb in QEventDispatcherGlib::processEvents (this=0x7f0c5c000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f0c8ddfa1eb in QEventLoop::exec (this=this@entry=0x7f0c635eecc0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #6 0x7f0c8dc14a52 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #7 0x7f0c8cf08fa9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f0c8dc15bec in QThreadPrivate::start (arg=0x5580e4a22760) at thread/qthread_unix.cpp:329 #9 0x7f0c8c2cc609 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #10 0x7f0c8d748293 in clone () from /lib/x86_64-linux-gnu/libc.so.6 Thread 7 (Thread 0x7f0c79bdb700 (LWP 12546)): #0 0x7f0c8b90c93d in g_main_context_prepare () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f0c8b90d29b in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f0c8b90d4a3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f0c8de55ffb in QEventDispatcherGlib::processEvents (this=0x7f0c68000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #4 0x7f0c8ddfa1eb in QEventLoop::exec (this=this@entry=0x7f0c79bdacc0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #5 0x7f0c8dc14a52 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #6 0x7f0c8cf08fa9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7f0c8dc15bec in QThreadPrivate::start (arg=0x5580e46fa020) at thread/qthread_unix.cpp:329 #8 0x7f0c8c2cc609 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x7f0c8d748293 in clone () from
[neon] [Bug 437547] Bad font kerning in internet browsers (Firefox on Wayland, Opera and Vivaldi)
https://bugs.kde.org/show_bug.cgi?id=437547 --- Comment #2 from Harald Sitter --- I'm guessing you have the Roboto font installed? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437468] You can't move a layer using a transform mask + Move Tool
https://bugs.kde.org/show_bug.cgi?id=437468 Dmitry Kazakov changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|CONFIRMED |NEEDSINFO --- Comment #5 from Dmitry Kazakov --- Hi, Tiar and Ahab! I have a bit of a problem with this bug. This behavioral change was somewhat intentional. Now, when you move a transform mask with the move tool, you move the mask itself over a layer, not the layer itself. Basically, you move it like a lens over a piece of newspaper. That does not look very obvious when the mask is set up in affine mode (translate/scale/rotation), but if you switch it into a perspective mode (or cage or mesh) you will see the difference. Here is a video illustrating the behavior: https://disk.yandex.ru/i/LDZRL-ggakOxDg I'm not sure what is the best solution to that actually. Theoretically, I can refactor the Move tool back and make it modify the translational part of the transform instead. But it sounds as a weird idea, because it would duplicate the transform tool. What is your opinion on that? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 437517] Fix file name display when showing a limited line number
https://bugs.kde.org/show_bug.cgi?id=437517 Méven Car changed: What|Removed |Added CC||meve...@gmail.com --- Comment #2 from Méven Car --- (In reply to Nate Graham from comment #1) > Hmm, cannot reproduce. > Me neither. Can you share the exact filename of the file having the issue, i.e "Resultado..." What is your locale ? I would guess spanish, right ? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 437539] Crash on clearing Wastebin
https://bugs.kde.org/show_bug.cgi?id=437539 --- Comment #4 from Ömer Fadıl USTA --- @Ian : could you recompile and check if the bug fixed or not ? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 437539] Crash on clearing Wastebin
https://bugs.kde.org/show_bug.cgi?id=437539 Ömer Fadıl USTA changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/syst ||em/dolphin/commit/879fa9fa7 ||d82a14c934c7a1361b97d39ffd0 ||a08b Status|ASSIGNED|RESOLVED --- Comment #3 from Ömer Fadıl USTA --- Git commit 879fa9fa7d82a14c934c7a1361b97d39ffd0a08b by Ömer Fadıl Usta. Committed on 25/05/2021 at 01:49. Pushed by usta into branch 'master'. [src/settings/contextmenu/contextmenusettingspage] Fix Crash because of nullptr M +7-5src/settings/contextmenu/contextmenusettingspage.cpp https://invent.kde.org/system/dolphin/commit/879fa9fa7d82a14c934c7a1361b97d39ffd0a08b -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436764] Plasma crashed in PlasmaQuick::ContainmentView::containmentChanged() when screen turned on after power saving
https://bugs.kde.org/show_bug.cgi?id=436764 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 435812] Wrong scale for GDK app
https://bugs.kde.org/show_bug.cgi?id=435812 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- 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.
[lattedock] [Bug 436889] Latte-dock crashes at login
https://bugs.kde.org/show_bug.cgi?id=436889 --- 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.
[sweeper] [Bug 436810] KDEInit could not launch '/usr/bin/sweeper
https://bugs.kde.org/show_bug.cgi?id=436810 --- 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.
[kdeconnect] [Bug 436756] when selecting *all*, the share options dissapears
https://bugs.kde.org/show_bug.cgi?id=436756 --- 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 436654] Task Manager crashes when hovering combined tasks
https://bugs.kde.org/show_bug.cgi?id=436654 --- Comment #11 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 436703] choqok abends due to something in .local/share/chokoq directory
https://bugs.kde.org/show_bug.cgi?id=436703 --- Comment #7 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 437523] ksystemstats segfaults on start
https://bugs.kde.org/show_bug.cgi?id=437523 --- Comment #2 from Maximiliano Bertacchini --- (In reply to Marco Martin from comment #1) > seems specifoc to lmsensors Indeed. Removing the lmsensors plugin from "/usr/lib/x86_64-linux-gnu/qt5/plugins/ksystemstats" unlocks both plasma-systemmonitor and kstatsviewer. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437631] Curves: Double-click on scalar keyframe should select all scalar keyframes at that time.
https://bugs.kde.org/show_bug.cgi?id=437631 Eoin O'Neill changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/1072ae783 ||162d1f31c099842b1dc7f0b3cbf ||5a46 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Eoin O'Neill --- Git commit 1072ae783162d1f31c099842b1dc7f0b3cbf5a46 by Eoin O'Neill. Committed on 25/05/2021 at 03:36. Pushed by eoinoneill into branch 'master'. KisAnimCurves: Added double click fast selection methods to curves docker as well. I'm not in love with the way select + drag operations work currently. There are cases where click and dragging to close to the handles will cause a deselection instead of a click drag. We might need to store intention of deselection across to release event, and check if any "dragging" occured along the way to prevent accidental deselection. I'll work on it more tomorrow. M +46 -3plugins/dockers/animation/KisAnimCurvesView.cpp M +1-0plugins/dockers/animation/KisAnimCurvesView.h https://invent.kde.org/graphics/krita/commit/1072ae783162d1f31c099842b1dc7f0b3cbf5a46 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 437644] New: cursor fails to switch to correct mode
https://bugs.kde.org/show_bug.cgi?id=437644 Bug ID: 437644 Summary: cursor fails to switch to correct mode Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: devguy...@gmail.com Target Milestone: --- SUMMARY This seems to happen mostly with Dolphin but I've seen the same issue with other application. This video shows the issue: https://youtu.be/4z-OUqD7bK8 Operating System: openSUSE Tumbleweed 20210521 KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.4-1-default OS Type: 64-bit Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: Radeon RX 570 Series ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 437539] Crash on clearing Wastebin
https://bugs.kde.org/show_bug.cgi?id=437539 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/system/dolphin/-/merge_requests/214 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437633] Frames outside of the playback range should not be displayed as cached.
https://bugs.kde.org/show_bug.cgi?id=437633 Eoin O'Neill changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/6d4e50872 ||e7ddb71b206a250fbde3e11d06c ||cdce Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Eoin O'Neill --- Git commit 6d4e50872e7ddb71b206a250fbde3e11d06ccdce by Eoin O'Neill. Committed on 25/05/2021 at 01:44. Pushed by eoinoneill into branch 'master'. KisAnimTimelineDocker: Cached status of frames now only shows for frames that exist within clip range. This should make the UI more clear about what these gray squares represent, and no longer be visually confusing by extending beyond the users intended playback range. M +9-2plugins/dockers/animation/KisAnimTimelineTimeHeader.cpp M +2-2plugins/dockers/animation/KisTimeBasedItemModel.h https://invent.kde.org/graphics/krita/commit/6d4e50872e7ddb71b206a250fbde3e11d06ccdce -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437630] Prev/Next Matching Key frame not working between two clones of the same frame.
https://bugs.kde.org/show_bug.cgi?id=437630 Eoin O'Neill changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/9279c5bb3 ||59c44ad471c80710396f1d389b3 ||6890 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Eoin O'Neill --- Git commit 9279c5bb359c44ad471c80710396f1d389b36890 by Eoin O'Neill. Committed on 25/05/2021 at 01:30. Pushed by eoinoneill into branch 'master'. Fix `nextKeyframeWithColor` and previous equivalent to work properly with clone frames. Originally, clones were ignored when seeking to the next keyframe of a specific color. Now, it works as expected. M +7-5libs/ui/canvas/kis_animation_player.cpp https://invent.kde.org/graphics/krita/commit/9279c5bb359c44ad471c80710396f1d389b36890 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435862] Blur effect not working in Plasma 5.21.90
https://bugs.kde.org/show_bug.cgi?id=435862 ryu.ketsu...@outlook.com changed: What|Removed |Added Version|git master |5.21.90 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435862] Blur effect not working in Plasma 5.21.90
https://bugs.kde.org/show_bug.cgi?id=435862 ryu.ketsu...@outlook.com changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435862] Blur effect not working in Plasma 5.21.90
https://bugs.kde.org/show_bug.cgi?id=435862 ryu.ketsu...@outlook.com changed: What|Removed |Added Summary|Blur effect not working in |Blur effect not working in |unstable builds |Plasma 5.21.90 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 435862] Blur effect not working in unstable builds
https://bugs.kde.org/show_bug.cgi?id=435862 --- Comment #8 from ryu.ketsu...@outlook.com --- Created attachment 138761 --> https://bugs.kde.org/attachment.cgi?id=138761=edit Screenshot showing how blur is not working on the titlebar Issue still exist on Plasma 5.21.90, coming from KDE repos for openSUSE Tumbleweed (not the Unstable repos). I just updated from 5.21.5. See attachment for screenshot -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 408928] Keyboard layout OSD doesn't work on X
https://bugs.kde.org/show_bug.cgi?id=408928 Christian Herenz changed: What|Removed |Added CC||eher...@eso.org -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 437632] Dolphin launched via link does not display overlapping icon for Samba shares
https://bugs.kde.org/show_bug.cgi?id=437632 --- Comment #3 from Harald Sitter --- Thanks. That's it. Of course there were no performance concern with the change to kdenetwork-filesharing since there's only ever one path we need to resolve. Quite a different story if it's 10k or more as would be the case here for dolphin's view. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 437632] Dolphin launched via link does not display overlapping icon for Samba shares
https://bugs.kde.org/show_bug.cgi?id=437632 --- Comment #2 from Patrick Silva --- (In reply to Harald Sitter from comment #1) > I feel like I've seen a similar bug report a couple months ago though for > the life of me I can't remember what the specifics were. possibly bug 425678 -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 437643] New: Crashing when closing Firefox
https://bugs.kde.org/show_bug.cgi?id=437643 Bug ID: 437643 Summary: Crashing when closing Firefox Product: kdeconnect Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: jangel.marti...@gmail.com Target Milestone: --- Application: kdeconnectd (21.04.1) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.8.0-53-generic x86_64 Windowing System: Wayland Drkonqi Version: 5.21.5 Distribution: KDE neon User Edition 5.21 -- Information about the crash: - What I was doing when the application crashed: I just close Firefox and several kde apps crashed suddenly at the same time The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Demonio de KDE Connect (kdeconnectd), signal: Aborted [New LWP 10568] [New LWP 10587] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fe4a5259aff in __GI___poll (fds=0x7ffe6d327868, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7fe4a172cd40 (LWP 10495))] Thread 3 (Thread 0x7fe49e9b1700 (LWP 10587)): #0 0x7fe4a5259aff in __GI___poll (fds=0x7fe490004e60, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fe4a3d4e36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe4a3d4e4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe4a5826ffb in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe4a57cb1eb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe4a55e5a52 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fe4a55e6bec in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fe4a476f609 in start_thread (arg=) at pthread_create.c:477 #8 0x7fe4a5266293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7fe49fbc2700 (LWP 10568)): #0 0x7fe4a5259aff in __GI___poll (fds=0x7fe498005240, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7fe4a3d4e36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fe4a3d4e4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fe4a5826ffb in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fe4a57cb1eb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fe4a55e5a52 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fe4a614ef4b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fe4a55e6bec in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fe4a476f609 in start_thread (arg=) at pthread_create.c:477 #9 0x7fe4a5266293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7fe4a172cd40 (LWP 10495)): [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #5 0x7fe4a5169859 in __GI_abort () at abort.c:79 #6 0x7fe4a55abbf7 in QMessageLogger::fatal(char const*, ...) const () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fe4a3a91d65 in ?? () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #8 0x7fe4a3aa316c in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib/x86_64-linux-gnu/libQt5WaylandClient.so.5 #9 0x7fe4a5803730 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fe4a5807773 in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fe4a5807f13 in QSocketNotifier::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7fe4a6341dc3 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7fe4a634abb8 in QApplication::notify(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #14 0x7fe4a57cc6da in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7fe4a5827be5 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #16 0x7fe4a3d4e17d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7fe4a3d4e400 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7fe4a3d4e4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x7fe4a5826ffb in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7fe4a57cb1eb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7fe4a57d3394 in
[yakuake] [Bug 437642] New: crashing when closing firefox
https://bugs.kde.org/show_bug.cgi?id=437642 Bug ID: 437642 Summary: crashing when closing firefox Product: yakuake Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: h...@kde.org Reporter: jangel.marti...@gmail.com Target Milestone: --- Application: yakuake (21.04.1) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.8.0-53-generic x86_64 Windowing System: Wayland Drkonqi Version: 5.21.5 Distribution: KDE neon User Edition 5.21 -- Information about the crash: - What I was doing when the application crashed: I just close Firefox and several kde apps crashed at the same time The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Yakuake (yakuake), signal: Aborted [New LWP 10591] [New LWP 10620] [New LWP 10621] [New LWP 10622] [New LWP 10623] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f6804e1eaff in __GI___poll (fds=0x7ffd6a6d82a8, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f6800bb3280 (LWP 10534))] Thread 6 (Thread 0x7f67f2059700 (LWP 10623)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5605c5afc438) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5605c5afc3e8, cond=0x5605c5afc410) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5605c5afc410, mutex=0x5605c5afc3e8) at pthread_cond_wait.c:647 #3 0x7f67fcc2fb5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f67fcc2f75b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f6803e3a609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f6804e2b293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f67f285a700 (LWP 10622)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5605c5afc438) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5605c5afc3e8, cond=0x5605c5afc410) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5605c5afc410, mutex=0x5605c5afc3e8) at pthread_cond_wait.c:647 #3 0x7f67fcc2fb5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f67fcc2f75b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f6803e3a609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f6804e2b293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f67ea85a700 (LWP 10621)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5605c5afc438) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5605c5afc3e8, cond=0x5605c5afc410) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5605c5afc410, mutex=0x5605c5afc3e8) at pthread_cond_wait.c:647 #3 0x7f67fcc2fb5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f67fcc2f75b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f6803e3a609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f6804e2b293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f67f305b700 (LWP 10620)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x5605c5afc438) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x5605c5afc3e8, cond=0x5605c5afc410) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x5605c5afc410, mutex=0x5605c5afc3e8) at pthread_cond_wait.c:647 #3 0x7f67fcc2fb5b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f67fcc2f75b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f6803e3a609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f6804e2b293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f67ff843700 (LWP 10591)): #0 0x7f6804e1eaff in __GI___poll (fds=0x7f67f8005240, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f680343b36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f680343b4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f68053e9ffb in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f680538e1eb in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f68051a8a52 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f68063c2f4b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f68051a9bec in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f6803e3a609 in start_thread (arg=) at pthread_create.c:477 #9
[dolphin] [Bug 437539] Crash on clearing Wastebin
https://bugs.kde.org/show_bug.cgi?id=437539
Ömer Fadıl USTA changed:
What|Removed |Added
CC||omeru...@gmail.com
--- Comment #1 from Ömer Fadıl USTA ---
(gdb) bt
#0 std::__uniq_ptr_impl >::_M_ptr (this=0x10)
at /usr/include/c++/11.1.0/bits/unique_ptr.h:173
#1 0x76e965ae in std::unique_ptr >::get (this=0x10)
at /usr/include/c++/11.1.0/bits/unique_ptr.h:422
#2 0x76e94d04 in std::unique_ptr >::operator-> (this=0x10)
at /usr/include/c++/11.1.0/bits/unique_ptr.h:416
#3 0x76e8f40e in KActionCollection::action (this=0x0, name=...) at
/home/kde-dev/kde/src/frameworks/kxmlgui/src/kactioncollection.cpp:138
#4 0x55619539 in ContextMenuSettingsPage::showEvent(QShowEvent*) ()
#5 0x75d810be in QWidget::event(QEvent*) () from
/usr/lib/libQt5Widgets.so.5
#6 0x75d3dd62 in QApplicationPrivate::notify_helper(QObject*, QEvent*)
() from /usr/lib/libQt5Widgets.so.5
#7 0x7526a00a in QCoreApplication::notifyInternal2(QObject*, QEvent*)
() from /usr/lib/libQt5Core.so.5
#8 0x75d7d8a8 in QWidgetPrivate::show_helper() () from
/usr/lib/libQt5Widgets.so.5
#9 0x75d80bbd in QWidgetPrivate::setVisible(bool) () from
/usr/lib/libQt5Widgets.so.5
#10 0x75d64b6e in QStackedLayout::setCurrentIndex(int) () from
/usr/lib/libQt5Widgets.so.5
#11 0x76b5ddad in KPageViewPrivate::pageSelected (this=0x5625d950,
index=..., previous=...)
at /home/kde-dev/kde/src/frameworks/kwidgetsaddons/src/kpageview.cpp:251
#12 0x76b5cbe4 in operator() (__closure=0x56277da0, selected=...,
deselected=...)
at /home/kde-dev/kde/src/frameworks/kwidgetsaddons/src/kpageview.cpp:51
#13 0x76b5f978 in QtPrivate::FunctorCall,
QtPrivate::List, void,
KPageViewPrivate::rebuildGui():: >::call(struct {...} &, void **) (f=..., arg=0x7fffcab0)
at /usr/include/qt/QtCore/qobjectdefs_impl.h:146
#14 0x76b5f8dd in
QtPrivate::Functor,
2>::call,
void>(struct {...} &, void *, void **) (f=..., arg=0x7fffcab0)
at /usr/include/qt/QtCore/qobjectdefs_impl.h:256
#15 0x76b5f798 in
QtPrivate::QFunctorSlotObject, 2, QtPrivate::List, void>::impl(int,
QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=1,
this_=0x56277d90, r=0x5611a480, a=0x7fffcab0, ret=0x0) at
/usr/include/qt/QtCore/qobjectdefs_impl.h:443
#16 0x752a13bb in ?? () from /usr/lib/libQt5Core.so.5
#17 0x75213aa1 in QItemSelectionModel::selectionChanged(QItemSelection
const&, QItemSelection const&) () from /usr/lib/libQt5Core.so.5
#18 0x7521a9dc in
QItemSelectionModel::emitSelectionChanged(QItemSelection const&, QItemSelection
const&) () from /usr/lib/libQt5Core.so.5
--
You are receiving this mail because:
You are watching all bug changes.
[dolphin] [Bug 437632] Dolphin launched via link does not display overlapping icon for Samba shares
https://bugs.kde.org/show_bug.cgi?id=437632 Harald Sitter changed: What|Removed |Added Ever confirmed|0 |1 CC||sit...@kde.org Status|REPORTED|CONFIRMED --- Comment #1 from Harald Sitter --- I feel like I've seen a similar bug report a couple months ago though for the life of me I can't remember what the specifics were. What I **think** happens here is that since you are inside a symlink the effective path of the directory is /home/stalker/Desktop/stalker/Apps which dolphin then doesn't find in the database of samba usershares because the path there is /home/stalker/Apps. i.e. something (not necessarily dolphin) would need to at some point resolve the path (which includes a symlink) to the canonical file path (which includes no symlinks anywhere). This is kind of problematic though because that would have to happen for every single directory that ever gets displayed in the view, potentially causing a lot of unnecessary disk access but certainly causing unnecessary power drain for basically only this niche corner case of share overlays (I dont think we have other overlays?). I'm not sure this is necessarily something we want to solve from an energy efficiency POV. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437527] Icons-only task manager (Breeze) design could have a cleaner look
https://bugs.kde.org/show_bug.cgi?id=437527 Lua changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |MOVED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437641] "System Information" could be renamed to "About system"
https://bugs.kde.org/show_bug.cgi?id=437641 --- Comment #1 from Lua --- Also, the word "about" seems to be a standard, because is present in macOS, Windows 10, GNOME. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437641] New: "System Information" could be renamed to "About system"
https://bugs.kde.org/show_bug.cgi?id=437641 Bug ID: 437641 Summary: "System Information" could be renamed to "About system" Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: lv215...@anonaddy.me Target Milestone: --- Created attachment 138760 --> https://bugs.kde.org/attachment.cgi?id=138760=edit System info "System Information" text create a repetitiveness with the "System Administration" header. Changing it to "About system" would break this repetitiveness. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437640] New: Plasma breaks when tryin to set some items in the system settings.
https://bugs.kde.org/show_bug.cgi?id=437640 Bug ID: 437640 Summary: Plasma breaks when tryin to set some items in the system settings. Product: systemsettings Version: 5.21.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: germanoal...@protonmail.com Target Milestone: --- Application: systemsettings5 (5.21.5) Qt Version: 5.15.2 Frameworks Version: 5.82.0 Operating System: Linux 5.11.12-300.fc34.x86_64 x86_64 Windowing System: Wayland Drkonqi Version: 5.21.5 Distribution: Fedora 34 (KDE Plasma) -- Information about the crash: - What I was doing when the application crashed: I was setting up the blur feature; adding virtuals desktops, etc. It doen't happen very often. Usually, it happens more when i have the monitor set as primary, but in this case it happened only with the laptop. I've madea few more attempts, and the same problem repeats itself a few times, but not always. The theme I use is the Breeze Dark, without any external modification or any theme downloaded from the store. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Configurações do sistema (systemsettings5), signal: Segmentation fault [KCrash Handler] #4 0x in ?? () #5 0x7fed409e6ed7 in QWaylandClientExtensionPrivate::handleRegistryGlobal(void*, wl_registry*, unsigned int, QString const&, unsigned int) () from /lib64/libQt5WaylandClient.so.5 #6 0x7fed409d33e9 in QtWaylandClient::QWaylandDisplay::registry_global(unsigned int, QString const&, unsigned int) () from /lib64/libQt5WaylandClient.so.5 #7 0x7fed409ef783 in QtWayland::wl_registry::handle_global(void*, wl_registry*, unsigned int, char const*, unsigned int) () from /lib64/libQt5WaylandClient.so.5 #8 0x7fed3e380c04 in ffi_call_unix64 () from /lib64/libffi.so.6 #9 0x7fed3e380107 in ffi_call () from /lib64/libffi.so.6 #10 0x7fed40940d10 in wl_closure_invoke.constprop () from /lib64/libwayland-client.so.0 #11 0x7fed4094142b in dispatch_event.isra () from /lib64/libwayland-client.so.0 #12 0x7fed4094161c in wl_display_dispatch_queue_pending () from /lib64/libwayland-client.so.0 #13 0x7fed409cb7b3 in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib64/libQt5WaylandClient.so.5 #14 0x7fed42d584fd in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #15 0x7fed42d5ab3a in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () from /lib64/libQt5Core.so.5 #16 0x7fed42d5b2d4 in QSocketNotifier::event(QEvent*) () from /lib64/libQt5Core.so.5 #17 0x7fed438b2e73 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #18 0x7fed42d27f48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #19 0x7fed42d7517f in socketNotifierSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #20 0x7fed40ae74cf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #21 0x7fed40b3b4e8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #22 0x7fed40ae4c03 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #23 0x7fed42d746f8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #24 0x7fed42d269b2 in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #25 0x7fed42d2e544 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #26 0x5637c0169d4c in main () [Inferior 1 (process 2996) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437580] Inconsistent vertical alignment of some settings pages
https://bugs.kde.org/show_bug.cgi?id=437580 Lua changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |MOVED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437580] Inconsistent vertical alignment of some settings pages
https://bugs.kde.org/show_bug.cgi?id=437580 --- Comment #2 from Lua --- Whops, I think this fits more to phabricator.kde.org. It confuses me a bit. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 437581] Uneven left and right margins in the places panel
https://bugs.kde.org/show_bug.cgi?id=437581 --- Comment #3 from Lua --- Created attachment 138759 --> https://bugs.kde.org/attachment.cgi?id=138759=edit File chooser dialog also affected The uneven margins of the places panel also affected the file chooser dialog. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 437581] Uneven left and right margins in the places panel
https://bugs.kde.org/show_bug.cgi?id=437581 --- Comment #2 from Lua --- Created attachment 138758 --> https://bugs.kde.org/attachment.cgi?id=138758=edit Dolphin others misalignments Seizing the opportunity, there's more misalignment in Dolphin, as shown in the attachment. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 433740] Show Image File Size While Resizing
https://bugs.kde.org/show_bug.cgi?id=433740 --- Comment #3 from Justin Zobel --- (In reply to Antonio Prcela from comment #2) > *** Bug 407040 has been marked as a duplicate of this bug. *** Wrong way around. You should mark the new as a duplicate of the old bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437123] [Wayland] virtual keyboard is not triggered for Xwayland applications
https://bugs.kde.org/show_bug.cgi?id=437123 --- Comment #3 from Aleix Pol --- For me it doesn't work on any Xwayland application. Also AFAIK, it cannot work unless Xwayland implemented the input protocols or we did it from KWin. Also I'd recommend you to upgrade to a newer Kubuntu release as there are several issues already solved that you will be hitting. -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 437639] Stop showing KSplash only after all desktop components are loaded
https://bugs.kde.org/show_bug.cgi?id=437639 --- Comment #1 from Lua --- could be smoother, giving Plasma startup a sleek feel* -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 437639] New: Stop showing KSplash only after all desktop components are loaded
https://bugs.kde.org/show_bug.cgi?id=437639 Bug ID: 437639 Summary: Stop showing KSplash only after all desktop components are loaded Product: ksplash Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: lv215...@anonaddy.me Target Milestone: --- Currently, KSplash stops displaying a little earlier before the taskbar is loaded. Doing so, the transition to the desktop could be smoother and gives Plasma startup a sleek feel. This would also fix this: https://bugs.kde.org/show_bug.cgi?id=422144 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437638] New: Pre-load the desktop while SDDM is running
https://bugs.kde.org/show_bug.cgi?id=437638 Bug ID: 437638 Summary: Pre-load the desktop while SDDM is running Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_sddm Assignee: k...@davidedmundson.co.uk Reporter: lv215...@anonaddy.me CC: k...@david-redondo.de, plasma-b...@kde.org Target Milestone: --- Aside from faster desktop startup, it could be possible to: 1. Make a smooth transition from SDDM to the splash screen; 2. Fix the issue when you type the password in SDDM and nothing happens for 2/3 seconds. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437629] Context menu opens on wrong desktop
https://bugs.kde.org/show_bug.cgi?id=437629 David Edmundson changed: What|Removed |Added Component|components |general Product|frameworks-plasma |plasmashell Resolution|--- |WAITINGFORINFO Target Milestone|--- |1.0 Assignee|notm...@gmail.com |k...@davidedmundson.co.uk Status|REPORTED|NEEDSINFO CC||k...@davidedmundson.co.uk Version|5.82.0 |master --- Comment #1 from David Edmundson --- Please include output of "qtdiag" (It might be called qtdiag-qt5 or some other derivative on your system) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 435833] Okular shows the [object Object] popup and crashes when the user enters something into a form field and hits TAB
https://bugs.kde.org/show_bug.cgi?id=435833 Albert Astals Cid changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #8 from Albert Astals Cid --- I made a mistake and push it to the wrong branch, fix has still not landed -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436990] Interactive PDF Forms with field validation cannot be filled due to repeating error window
https://bugs.kde.org/show_bug.cgi?id=436990 Albert Astals Cid changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #4 from Albert Astals Cid --- I made a mistake and push it to the wrong branch, fix has still not landed -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 436990] Interactive PDF Forms with field validation cannot be filled due to repeating error window
https://bugs.kde.org/show_bug.cgi?id=436990 Albert Astals Cid changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/okular/commit/37aacc7f ||8bba67e0ec6b4854d901fe9dab4 ||a8efd Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #3 from Albert Astals Cid --- Git commit 37aacc7f8bba67e0ec6b4854d901fe9dab4a8efd by Albert Astals Cid. Committed on 24/05/2021 at 22:26. Pushed by aacid into branch 'okular_focus_actions'. FormLineEdit: Don't run focusin action when gaining focus because of window management Adobe Reader doesn't do it, and with reason, because otherwise we end up with: * Run focus in script * script shows alert() * field loses focus and gains it again once the alert() is closed * infinite loop M +6-2part/formwidgets.cpp https://invent.kde.org/graphics/okular/commit/37aacc7f8bba67e0ec6b4854d901fe9dab4a8efd -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 435833] Okular shows the [object Object] popup and crashes when the user enters something into a form field and hits TAB
https://bugs.kde.org/show_bug.cgi?id=435833 Albert Astals Cid changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/grap ||hics/okular/commit/e23d398d ||78c1747616e13f72e99887ef63c ||bc357 Resolution|--- |FIXED --- Comment #7 from Albert Astals Cid --- Git commit e23d398d78c1747616e13f72e99887ef63cbc357 by Albert Astals Cid. Committed on 24/05/2021 at 22:24. Pushed by aacid into branch 'okular_focus_actions'. FormLineEdit: Don't run focusout/formatfield actions when losing focus because of window management Adobe Reader doesn't do it and if we do it can end up crashing because we end up running two focusout actions in parallel and our script system is not prepared for that: Scenario: * Tab out of a field * Script for that focusout runs * focus goes to next field * script for that focusout shows an alert() * second focusout script for that field runs while the first is running * bad stuff M +1-1part/formwidgets.cpp https://invent.kde.org/graphics/okular/commit/e23d398d78c1747616e13f72e99887ef63cbc357 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 435833] Okular shows the [object Object] popup and crashes when the user enters something into a form field and hits TAB
https://bugs.kde.org/show_bug.cgi?id=435833 --- Comment #6 from Albert Astals Cid --- Git commit 81344f8aa8244197f4292210c4f0b31d871a3d28 by Albert Astals Cid. Committed on 24/05/2021 at 17:53. Pushed by aacid into branch 'okular_focus_actions'. Unbox alert() parameters when they are in an object API let's you use both arguments or objects with named properties, so support both. This fixes the contents of the warning in 435833, the crash is still there though, working on that next M +54 -44 core/script/kjs_app.cpp https://invent.kde.org/graphics/okular/commit/81344f8aa8244197f4292210c4f0b31d871a3d28 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 430826] Unable to rotate screen
https://bugs.kde.org/show_bug.cgi?id=430826 S. Bryant changed: What|Removed |Added CC||st...@bawue.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437637] New: Dell dock display failure
https://bugs.kde.org/show_bug.cgi?id=437637 Bug ID: 437637 Summary: Dell dock display failure Product: plasmashell Version: 5.18.5 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: clintonbond...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.5) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.8.0-53-generic x86_64 Windowing system: Wayland Distribution: Ubuntu 20.04.2 LTS -- Information about the crash: - What I was doing when the application crashed: Plugged in dell dock to work on second monitor. - Unusual behavior I noticed: Audio and network connected, but display on laptop and second monitor was black. Until I disconnected the usb-c - Custom settings of the application: kde theme? The crash can be reproduced every time. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fb022da2280 (LWP 81774))] Thread 32 (Thread 0x7faf71ffd700 (LWP 129691)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55c9fd1b5350) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55c9fd1b5300, cond=0x55c9fd1b5328) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55c9fd1b5328, mutex=0x55c9fd1b5300) at pthread_cond_wait.c:638 #3 0x7fb0267f8b0f in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb0267f8c01 in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fb0284d7109 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fb0284d73ad in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fb0267f29d2 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fb025c97609 in start_thread (arg=) at pthread_create.c:477 #9 0x7fb026481293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 31 (Thread 0x7faf917fa700 (LWP 84307)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55c9f79cb924) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55c9f79cb8d0, cond=0x55c9f79cb8f8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55c9f79cb8f8, mutex=0x55c9f79cb8d0) at pthread_cond_wait.c:638 #3 0x7fb0267f8b0f in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb0267f8c01 in QWaitCondition::wait(QMutex*, unsigned long) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fafff303050 in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #6 0x7fafff306d4e in ?? () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #7 0x7fafff30 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #8 0x7fafff306da9 in ?? () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #9 0x7fafff30 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #10 0x7fafff306da9 in ?? () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #11 0x7fafff30 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #12 0x7fafff306da9 in ?? () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #13 0x7fafff30 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #14 0x7fafff306da9 in ?? () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #15 0x7fafff30 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #16 0x7fafff306da9 in ?? () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #17 0x7fafff30 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #18 0x7fafff306da9 in ?? () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #19 0x7fafff30 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #20 0x7fafff306da9 in ?? () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #21 0x7fafff30 in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #22 0x7fafff306da9 in ?? () from /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5 #23
[frameworks-baloo] [Bug 433204] baloo_file SEGV
https://bugs.kde.org/show_bug.cgi?id=433204 --- Comment #34 from Peter Wibberley --- (In reply to tagwerk19 from comment #31) > (In reply to Peter Wibberley from comment #30) > > ... Any clues ... > First off, I'd say create a file > /etc/sysctl.d/40-neon-inotify.conf > as per comment #12 (at least until 5.11). That would set the > max_user_watches every reboot. > > Then I'd see if > coredumpctl > gave a list of dumps as per comment #23 > > If it does, and you can get a backtrace, that would be a step forward. Tagwerk19, Sorry about the long gap, but life got in the way for a couple of months. In the meantime, I migrated from Neon LTS to the User Edition (using the instructions at https://userbase.kde.org/Neon/LTS/EOL). I had hoped that this might cure the problem, but alas not. The situation now is as follows: (1) If I use the default value for fs.inotify.max_user_watches of 8192 and run 'balooctl enable', I get a stream of messages, "kf.baloo: KDE Baloo File Indexer has reached the inotify folder watch limit. File changes will be ignored." (2) If I just double fs.inotify.max_user_watches to only 16384, and run 'balooctl enable', the watch limit error messages stop. However, 'balooctl status' shows the Baloo File Indexer as stopping after a few seconds. (3) If I run 'balooctl enable', wait for it to stop, and then run 'coredumpctl gdb ', as you recommended, I get, #0 0x7f1aff1919f4 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #1 0x7f1aff194e80 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #2 0x7f1aff195165 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #3 0x7f1aff195892 in ?? () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #4 0x7f1aff195ed4 in mdb_get () from /usr/lib/x86_64-linux-gnu/liblmdb.so.0 #5 0x7f1b0069d458 in Baloo::IdFilenameDB::get(unsigned long long) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #6 0x7f1b006921aa in Baloo::DocumentUrlDB::get(unsigned long long) const () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #7 0x7f1b006afa19 in Baloo::Transaction::documentUrl(unsigned long long) const () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #8 0x55fa2c6779f3 in ?? () #9 0x7f1b006be7ac in Baloo::WriteTransaction::removeRecursively(unsigned long long, std::function const&) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 ... #65486 0x7f1b006be7fe in Baloo::WriteTransaction::removeRecursively(unsigned long long, std::function const&) () from /usr/lib/x86_64-linux-gnu/libKF5BalooEngine.so.5 #65487 0x55fa2c67811c in ?? () #65488 0x7f1b001f5ff2 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #65489 0x7f1b001f2bec in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #65490 0x7f1aff200609 in start_thread (arg=) at pthread_create.c:477 #65491 0x7f1affd25293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 (4) I've also run strace when the indexer is still running and again when it's stopped, and the outputs look completely different. If it's running, the strace terminates in an orderly manner, but if the indexer isn't running then I get the SEGV fault. The fault seems to occur when a poll command gets a timeout. No idea what to make of all this! I would try a fresh install, but I had hoped the switch to the User Edition would achieve the same thing. Any suggestions? As ever, many thanks and regards Peter -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 437636] Alt+drag for block selection
https://bugs.kde.org/show_bug.cgi?id=437636 Nate Graham changed: What|Removed |Added CC||waqar@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-ktexteditor] [Bug 437636] New: Alt+drag for block selection
https://bugs.kde.org/show_bug.cgi?id=437636 Bug ID: 437636 Summary: Alt+drag for block selection Product: frameworks-ktexteditor Version: 5.82.0 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: n...@kde.org Target Milestone: --- Right now you invoke block selection by entering a dedicated "Block Selection" mode. However it might be nice if you could additionally make a quick block-selection without having to enter and exit that mode by dreagging while holding down the alt key. This is the way you invoke block selection mode in various other text editors and platforms (e.g. Notepad++, VSCode, and all macOS apps with text fields). -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 437635] New: Alt+drag for block selection
https://bugs.kde.org/show_bug.cgi?id=437635 Bug ID: 437635 Summary: Alt+drag for block selection Product: konsole Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: n...@kde.org Target Milestone: --- Right now you invoke block selection with Ctrl+Alt+drag. However the addition of Ctrl seems unnecessary; Alt+drag alone feels like it would be more natural, and also be consistent with the way you invoke block selection mode in various other text editors and platforms (e.g. Notepad++, VSCode, and all macOS apps with text fields including their terminal). -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437631] Curves: Double-click on scalar keyframe should select all scalar keyframes at that time.
https://bugs.kde.org/show_bug.cgi?id=437631 Emmet O'Neill changed: What|Removed |Added Summary|Double-click on scalar |Curves: Double-click on |keyframe should select all |scalar keyframe should |scalar keyframes at that|select all scalar keyframes |time. |at that time. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437634] New: Curves: Box selection of scalar keyframes.
https://bugs.kde.org/show_bug.cgi?id=437634 Bug ID: 437634 Summary: Curves: Box selection of scalar keyframes. Product: krita Version: git master (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Animation Assignee: eoinoneill1...@gmail.com Reporter: emmetoneill@gmail.com Target Milestone: --- SUMMARY It would be nice to be able to drag a box around a group of scalar keyframes on the curves docker to select them all. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437633] New: Frames outside of the playback range should not be displayed as cached.
https://bugs.kde.org/show_bug.cgi?id=437633 Bug ID: 437633 Summary: Frames outside of the playback range should not be displayed as cached. Product: krita Version: git master (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Animation Assignee: eoinoneill1...@gmail.com Reporter: emmetoneill@gmail.com Target Milestone: --- OBSERVED RESULT On the timeline docker, frames that are outside of the current playback range are considered cached. This is misleading and makes it less harder to see the current animation range. EXPECTED RESULT Frames outside of the playback range should be shown as not being cached. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 437632] New: Dolphin launched via link does not display overlapping icon for Samba shares
https://bugs.kde.org/show_bug.cgi?id=437632 Bug ID: 437632 Summary: Dolphin launched via link does not display overlapping icon for Samba shares Product: dolphin Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: bugsefor...@gmx.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 138757 --> https://bugs.kde.org/attachment.cgi?id=138757=edit screeen recording SUMMARY Normally folders shared via Samba have an overlapping icon. However, this icon is not displayed when I open Dolphin using a link created on desktop. Please watch the attached screen recording. STEPS TO REPRODUCE 1. create a link to your Home on desktop 2. create a Samba share in your Home 3. close Dolphin 4. open Dolphin using the link to Home created on desktop EXPECTED RESULT Dolphin launched via link should display overlapping icon for Samba shares SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.22.80 KDE Frameworks Version: 5.83.0 Qt Version: 5.15.2 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437105] Whole system tray is highlighted with a blue line after enabling/disabling "Keep open" feature of active applet
https://bugs.kde.org/show_bug.cgi?id=437105 --- Comment #6 from Konrad Materka --- (In reply to Nate Graham from comment #5) > Git commit 1ce09dcfcb78198c95a94bf4d6f75a49c2b77dc0 by Nate Graham, on > behalf of Konrad Materka. > Pushed by ngraham into branch 'Plasma/5.22'. Thank you, Nate! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437631] New: Double-click on scalar keyframe should select all scalar keyframes at that time.
https://bugs.kde.org/show_bug.cgi?id=437631 Bug ID: 437631 Summary: Double-click on scalar keyframe should select all scalar keyframes at that time. Product: krita Version: git master (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Animation Assignee: eoinoneill1...@gmail.com Reporter: emmetoneill@gmail.com Target Milestone: --- EXPECTED RESULT Just like how double-clicking on a raster keyframe on the animation timeline docker causes all of the keys at that time to become selected, double-clicking on a scalar keyframe on the curves docker should act in a similar way. Right now there isn't a great way to select multiple keys on the curves docker. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437630] New: Prev/Next Matching Key frame not working between two clones of the same frame.
https://bugs.kde.org/show_bug.cgi?id=437630 Bug ID: 437630 Summary: Prev/Next Matching Key frame not working between two clones of the same frame. Product: krita Version: git master (please specify the git hash!) Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Animation Assignee: eoinoneill1...@gmail.com Reporter: emmetoneill@gmail.com Target Milestone: --- SUMMARY If two key frames with matching color labels (i.e.: both are green on the timeline) are clones, the prev/next matching key frame action will not work correctly. STEPS TO REPRODUCE 1. Create a key frame, give it a green color label. 2. Create any number of non-green key frames after that frame. 3. Clone the green key frame. 4. Select either of the green frames and invoke the prev/next keyframe actions. OBSERVED RESULT The prev/next matching keyframe action will not select move the selection between the two green frames because they are clones. EXPECTED RESULT We expect the matching keyframe actions to always select the prev/next frame with the same color label, regardless of whether it is a clone of the selected keyframe or not. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux with GNOME. :) Qt Version: Qt 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 437200] New Tab menu entries are shown with default profile icon only
https://bugs.kde.org/show_bug.cgi?id=437200 Kurt Hindenburg changed: What|Removed |Added Latest Commit|https://invent.kde.org/util |https://invent.kde.org/util |ities/konsole/commit/e03a46 |ities/konsole/commit/c29e73 |8075c7067f62dba0dd5b513e8fc |4845950446f9d27e007f3b8486d |109f5d4 |7f5c0b1 --- Comment #3 from Kurt Hindenburg --- Git commit c29e734845950446f9d27e007f3b8486d7f5c0b1 by Kurt Hindenburg, on behalf of Ahmad Samir. Committed on 24/05/2021 at 20:28. Pushed by hindenburg into branch 'release/21.04'. Don't override profile icon in "New Tab" menu We only need to set the favourite emblem for the default profile icon, for other profiles, the profile icon is already set on the menu action. Rename a lambda to a more meaningful name. FIXED-IN: 21.08 (cherry picked from commit e03a468075c7067f62dba0dd5b513e8fc109f5d4) M +3-4src/MainWindow.cpp https://invent.kde.org/utilities/konsole/commit/c29e734845950446f9d27e007f3b8486d7f5c0b1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 437629] New: Context menu opens on wrong desktop
https://bugs.kde.org/show_bug.cgi?id=437629 Bug ID: 437629 Summary: Context menu opens on wrong desktop Product: frameworks-plasma Version: 5.82.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: components Assignee: notm...@gmail.com Reporter: voncl...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY I have a dual monitor setup..upon right clicking on a file on my main desktop - the context menu opens on the secondary desktop. STEPS TO REPRODUCE 1. Right Click on file on main desktop 2. Context menu opens on second monitor 3. OBSERVED RESULT Context menu opens on wrong desktop EXPECTED RESULT Open Context menu on correct desktop SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 437628] New: ksystemstats crashed (SIGSEGV)
https://bugs.kde.org/show_bug.cgi?id=437628 Bug ID: 437628 Summary: ksystemstats crashed (SIGSEGV) Product: ksysguard Version: 5.21.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: pos...@posteo.eu CC: plasma-b...@kde.org Target Milestone: --- Created attachment 138756 --> https://bugs.kde.org/attachment.cgi?id=138756=edit Full stacktrace SUMMARY When I looked into `coredumctl list` I found that ksystemstats had crashed: ``` Thread 1 (Thread 0x7f827ef00080 (LWP 1990)): #0 std::__atomic_base::load (__m=std::memory_order_relaxed, this=0x40004002c) at /usr/include/c++/10/bits/atomic_base.h:420 #1 QAtomicOps::loadRelaxed (_q_value=..., _q_value=...) at /usr/include/qt5/QtCore/qatomic_cxx11.h:239 #2 QBasicAtomicInteger::loadRelaxed (this=0x40004002c) at /usr/include/qt5/QtCore/qbasicatomic.h:107 #3 QWeakPointer::internalData (this=) at /usr/include/qt5/QtCore/qsharedpointer_impl.h:698 #4 QPointer::data (this=) at /usr/include/qt5/QtCore/qpointer.h:77 #5 QPointer::operator SensorProperty* (this=) at /usr/include/qt5/QtCore/qpointer.h:83 #6 AggregateSensor::value (this=0x5625a82805d0) at /usr/src/debug/ksysguard5-5.21.5-1.1.x86_64/libkstats/AggregateSensor.cpp:101 #7 0x5625a6403201 in operator() (__closure=0x7f827801a600) at /usr/src/debug/ksysguard5-5.21.5-1.1.x86_64/ksystemstats/client.cpp:57 #8 QtPrivate::FunctorCall, QtPrivate::List<>, void, Client::subscribeSensors(const QStringList&):: >::call (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146 #9 QtPrivate::Functor, 0>::call, void> (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256 #10 QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x7f827801a5f0, r=, a=, ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443 #11 0x7f8280f63c17 in QtPrivate::QSlotObjectBase::call (a=0x7fffe1a5e300, r=0x5625a83c5d60, this=0x7f827801a5f0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #12 doActivate (sender=0x5625a82805d0, signal_index=3, argv=0x7fffe1a5e300, argv@entry=0x0) at kernel/qobject.cpp:3886 #13 0x7f8280f5cf60 in QMetaObject::activate (sender=, m=m@entry=0x7f82812c4b80, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3946 #14 0x7f82812bb9e0 in SensorProperty::valueChanged (this=) at /usr/src/debug/ksysguard5-5.21.5-1.1.x86_64/build/libkstats/ksgrdbackend_autogen/EWIEGA46WW/moc_SensorProperty.cpp:153 #15 0x7f82812bbce6 in operator() (__closure=0x7f8278047af0) at /usr/src/debug/ksysguard5-5.21.5-1.1.x86_64/libkstats/AggregateSensor.cpp:233 #16 QtPrivate::FunctorCall, QtPrivate::List<>, void, AggregateSensor::delayedEmitDataChanged():: >::call (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:146 #17 QtPrivate::Functor, 0>::call, void> (arg=, f=...) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:256 #18 QtPrivate::QFunctorSlotObject, 0, QtPrivate::List<>, void>::impl(int, QtPrivate::QSlotObjectBase *, QObject *, void **, bool *) (which=, this_=0x7f8278047ae0, r=, a=, ret=) at /usr/include/qt5/QtCore/qobjectdefs_impl.h:443 #19 0x7f8280f67c32 in QtPrivate::QSlotObjectBase::call (a=0x7fffe1a5e360, r=, this=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #20 QSingleShotTimer::timerEvent (this=0x5625a8282680) at kernel/qtimer.cpp:320 #21 0x7f8280f5994f in QObject::event (this=0x5625a8282680, e=0x7fffe1a5e490) at kernel/qobject.cpp:1336 #22 0x7f8280f2d10f in doNotify (event=0x7fffe1a5e490, receiver=0x5625a8282680) at kernel/qcoreapplication.cpp:1153 #23 QCoreApplication::notify (event=, receiver=, this=) at kernel/qcoreapplication.cpp:1139 #24 QCoreApplication::notifyInternal2 (receiver=0x5625a8282680, event=0x7fffe1a5e490) at kernel/qcoreapplication.cpp:1063 #25 0x7f8280f840f3 in QTimerInfoList::activateTimers (this=this@entry=0x5625a823f330) at kernel/qtimerinfo_unix.cpp:643 #26 0x7f8280f84974 in timerSourceDispatch (source=source@entry=0x5625a823f2d0) at kernel/qeventdispatcher_glib.cpp:183 #27 0x7f827fe2f8b7 in g_main_dispatch (context=0x5625a823ced0) at ../glib/gmain.c:3337 #28 g_main_context_dispatch (context=0x5625a823ced0) at ../glib/gmain.c:4055 #29 0x7f827fe2fc38 in g_main_context_iterate (context=context@entry=0x5625a823ced0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4131 #30 0x7f827fe2fcef in g_main_context_iteration (context=0x5625a823ced0, may_block=may_block@entry=1) at ../glib/gmain.c:4196 #31 0x7f8280f84d30 in QEventDispatcherGlib::processEvents (this=0x5625a823c550, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #32 0x7f8280f2bb7b in QEventLoop::exec
[ksysguard] [Bug 437628] ksystemstats crashed (SIGSEGV)
https://bugs.kde.org/show_bug.cgi?id=437628 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 437627] kded5 crashed (suddenly)
https://bugs.kde.org/show_bug.cgi?id=437627 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 437627] New: kded5 crashed (suddenly)
https://bugs.kde.org/show_bug.cgi?id=437627 Bug ID: 437627 Summary: kded5 crashed (suddenly) Product: frameworks-kded Version: 5.82.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: pos...@posteo.eu CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 138755 --> https://bugs.kde.org/attachment.cgi?id=138755=edit Stacktrace SUMMARY kded5 has crashed suddenly. I will see if I can reproduce it again. For the full stacktrace containing all threads, please see the file attached. ``` Thread 1 (Thread 0x7f2429795640 (LWP 1998)): #0 __GI_raise (sig=sig@entry=11) at ../sysdeps/unix/sysv/linux/raise.c:49 #1 0x7f2436921e91 in KCrash::defaultCrashHandler(int) (sig=11) at /usr/src/debug/kcrash-5.82.0-1.1.x86_64/src/kcrash.cpp:567 #2 0x7f24356f1530 in () at /lib64/libc.so.6 #3 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:49 #4 0x7f24356f1530 in () at /lib64/libc.so.6 #5 __GI_raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:49 #9 0x7f242ae30b3f in (instance=, signal_id=, detail=detail@entry=0) at ../gobject/gsignal.c:3553 #6 0x7f242ae1769f in g_closure_invoke (closure=closure@entry=0x7f24200081a0, return_value=return_value@entry=0x0, n_param_values=3, param_values=param_values@entry=0x7f2429794970, invocation_hint=invocation_hint@entry=0x7f24297948f0) at ../gobject/gclosure.c:810 #7 0x7f242ae299c9 in signal_emit_unlocked_R (node=node@entry=0x7f24200081f0, detail=detail@entry=0, instance=instance@entry=0x7f242000b050, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7f2429794970) at ../gobject/gsignal.c:3780 #8 0x7f242ae309d9 in g_signal_emit_valist (instance=, signal_id=, detail=, var_args=var_args@entry=0x7f2429794b20) at ../gobject/gsignal.c:3497 #10 0x7f242a26b6d2 in emit_closed_in_idle (user_data=user_data@entry=0x7f2414009ae0) at ../gio/gdbusconnection.c:1379 #11 0x7f24348705d7 in g_idle_dispatch (source=source@entry=0x7f2414007440, callback=0x7f242a26b680 , user_data=0x7f2414009ae0) at ../glib/gmain.c:5848 #12 0x7f24348748b7 in g_main_dispatch (context=0x55912816cda0) at ../glib/gmain.c:3337 #13 g_main_context_dispatch (context=0x55912816cda0) at ../glib/gmain.c:4055 #14 0x7f2434874c38 in g_main_context_iterate (context=context@entry=0x55912816cda0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at ../glib/gmain.c:4131 #15 0x7f2434874cef in g_main_context_iteration (context=context@entry=0x55912816cda0, may_block=may_block@entry=1) at ../glib/gmain.c:4196 #16 0x7f2429f9d87d in dconf_gdbus_worker_thread (user_data=0x55912816cda0) at ../gdbus/dconf-gdbus-thread.c:82 #17 0x7f243489e72e in g_thread_proxy (data=0x7f2424002240) at ../glib/gthread.c:826 #18 0x7f243530a299 in start_thread (arg=0x7f2429795640) at pthread_create.c:481 #19 0x7f24357b44a3 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 ``` SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210522 KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.4-1-default OS Type: 64-bit Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 434908] [wayland] VNC not usable
https://bugs.kde.org/show_bug.cgi?id=434908 --- Comment #1 from Dmitry Misharov --- Created attachment 138754 --> https://bugs.kde.org/attachment.cgi?id=138754=edit chrome screenshot I faced that issue today. I have a container with a running VNC server and Google Chrome. When I tried to connect using krdc it's hard to recognize anything. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 437112] "Change speed" cripples clip in/out boundaries.
https://bugs.kde.org/show_bug.cgi?id=437112 --- Comment #6 from Veps --- That's the first minute of the file that produces the shift in the video of an clip after speed change: 1. Drag file onto project window. 2. Accept project setting change. 2.1. Already noticed that ending thumbnail is white. 3. Drag file onto timeline. 4. Change speed of the file to 98% via Ctrl+pulledge (right edge). Though the impact seems to be smaller -- probably due to the shorter video/clip but it is still noticeable due to the de-sync in audio or actually in the video since the audio stays correct. (You can here the 5 peeps before the game starts and the "woosh" of the menues that fly out of screen even though the frames are "cut out".) File about 60 mb: https://anonfiles.com/J3BcL9xbud/change-speed-issue-first-minute_7z -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 434908] [wayland] VNC not usable
https://bugs.kde.org/show_bug.cgi?id=434908 Dmitry Misharov changed: What|Removed |Added CC||quarcks...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433854] A lot of times copy-paste does not work.
https://bugs.kde.org/show_bug.cgi?id=433854 --- Comment #10 from Allexus J --- I agree with tagwer...@innerjoin.org I noticed too that the copy is done and it is in clipboard... but the paste doesn't happen. I just noticed now again the issue when pasting to Kate. I can see the text in clipboard though. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 437601] CSV import: cannot pass step 1
https://bugs.kde.org/show_bug.cgi?id=437601 pug...@yahoo.de changed: What|Removed |Added Resolution|WORKSFORME |NOT A BUG --- Comment #2 from pug...@yahoo.de --- Danke Thomas, I really did RTM, but somehow overlooked the part with entering the name in the text field. I took it for the file path field. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 397065] 'perspective', 'warp' and 'cage' and 'liquify' transformation modes do not work on vector layers
https://bugs.kde.org/show_bug.cgi?id=397065 --- Comment #5 from konrados --- (In reply to Dmitry Kazakov from comment #4) Thank you, Dmitry! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437605] Tooltips of some buttons in Entries section of system tray settings have unnecessary "&" character
https://bugs.kde.org/show_bug.cgi?id=437605 Nate Graham changed: What|Removed |Added CC||n...@kde.org Version Fixed In||5.22 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437605] Tooltips of some buttons in Entries section of system tray settings have unnecessary "&" character
https://bugs.kde.org/show_bug.cgi?id=437605 Nate Graham changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/commit/ |ma/plasma-workspace/commit/ |9a0f7f24306794b93ef0e3e10c8 |ef23b8f89aea50309a45ee38275 |48ff5db3e882c |cdd9a0660830b --- Comment #6 from Nate Graham --- Git commit ef23b8f89aea50309a45ee38275cdd9a0660830b by Nate Graham, on behalf of Nicolas Fella. Committed on 24/05/2021 at 19:48. Pushed by ngraham into branch 'Plasma/5.22'. [applets/systemtray] Strip mnemonic ampersand from entry config tooltip Some applet config titles contain ampersands for mnemonic purposes. PC3.ToolTip filters them out but QQC2.Tooltip does not, so they are visible in the system tray config window. (cherry picked from commit 9a0f7f24306794b93ef0e3e10c848ff5db3e882c) M +3-1applets/systemtray/package/contents/ui/ConfigEntries.qml https://invent.kde.org/plasma/plasma-workspace/commit/ef23b8f89aea50309a45ee38275cdd9a0660830b -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437605] Tooltips of some buttons in Entries section of system tray settings have unnecessary "&" character
https://bugs.kde.org/show_bug.cgi?id=437605 Nate Graham changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/commit/ ||9a0f7f24306794b93ef0e3e10c8 ||48ff5db3e882c Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #5 from Nate Graham --- Git commit 9a0f7f24306794b93ef0e3e10c848ff5db3e882c by Nate Graham, on behalf of Nicolas Fella. Committed on 24/05/2021 at 19:47. Pushed by ngraham into branch 'master'. [applets/systemtray] Strip mnemonic ampersand from entry config tooltip Some applet config titles contain ampersands for mnemonic purposes. PC3.ToolTip filters them out but QQC2.Tooltip does not, so they are visible in the system tray config window. M +3-1applets/systemtray/package/contents/ui/ConfigEntries.qml https://invent.kde.org/plasma/plasma-workspace/commit/9a0f7f24306794b93ef0e3e10c848ff5db3e882c -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433854] A lot of times copy-paste does not work.
https://bugs.kde.org/show_bug.cgi?id=433854 --- Comment #9 from Allexus J --- the problem is not only with firefox. it happens with others applications. also I don't know if this is related, but if I copy something from Libreoffice Calc and paste also to Libreoffice Calc, it appears like chinese language But if I paste the same content inside Kate for example I can see the real text that I copied, so not "chinese"... and if I copy from Kate to Libreoffice Calc now it correctly pastes the correct copied text link of video showing the bug: https://streamable.com/tj2fcd -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437415] 2 Point Perspective assistant can't be hidden through View > Show Painting Assistants
https://bugs.kde.org/show_bug.cgi?id=437415 Tiar changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/krita/commit/fa7d1828d ||fa40397e67f071e781aea9809e8 ||9a6f Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #2 from Tiar --- Git commit fa7d1828dfa40397e67f071e781aea9809e89a6f by Agata Cacko. Committed on 24/05/2021 at 18:57. Pushed by tymond into branch 'master'. Fix disabling preview of 2pp assistant Before this commit, 2pp assistant preview was impossible to turn off in the View menu. This commit ensures that if Show Assistant Preview is turned off, the grid disappears. Note: the behaviour is slightly different from Vanishing Point Assistant, because it does show the preview if "Show Painting Assistant" is off and the "Show Preview" is on. However this seemed more correct, and is consistent with other assistants like Parallel Ruler. M +8-4plugins/assistants/Assistants/TwoPointAssistant.cc https://invent.kde.org/graphics/krita/commit/fa7d1828dfa40397e67f071e781aea9809e89a6f -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 437573] Acquire EGL stream frame fails persistently with EGL_BAD_ACCESS in eglstreams backend for some applications
https://bugs.kde.org/show_bug.cgi?id=437573 Nate Graham changed: What|Removed |Added Version Fixed In||5.22 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 418094] lots of qml error messages
https://bugs.kde.org/show_bug.cgi?id=418094 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED CC||n...@kde.org Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- Looks like these are all fixed now. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 434892] Crash when using a color scheme with "random" background colors
https://bugs.kde.org/show_bug.cgi?id=434892 --- Comment #16 from Kurt Hindenburg --- Git commit 4177f5c01568b31f3d5c1ff20cde3841eec97f08 by Kurt Hindenburg, on behalf of Ahmad Samir. Committed on 24/05/2021 at 19:23. Pushed by hindenburg into branch 'release/21.04'. Fix type of randomSeed parameter It should be uint. I am not sure this fixes the mentioned bug, but it's correct anyway, std::mt19937 and co. unsigned types; and we shouldn't mix signed with unsigned. (cherry picked from commit b7f6849d287459ca03f8b0e6ab1c4770a9a9ce28) M +1-1src/terminalDisplay/TerminalColor.cpp M +1-1src/terminalDisplay/TerminalColor.h https://invent.kde.org/utilities/konsole/commit/4177f5c01568b31f3d5c1ff20cde3841eec97f08 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433861] All the panel items are not right-clickable
https://bugs.kde.org/show_bug.cgi?id=433861 --- Comment #3 from Allexus J --- issue still persists kernel: 5.10.38-1-lts distro: archlinux KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 434892] Crash when using a color scheme with "random" background colors
https://bugs.kde.org/show_bug.cgi?id=434892 Kurt Hindenburg changed: What|Removed |Added Latest Commit|https://invent.kde.org/util |https://invent.kde.org/util |ities/konsole/commit/8c2495 |ities/konsole/commit/b246ac |3bdefc28fa7f1db1d0b77f855f3 |57ee8000e15e71d833701fbcab0 |c1ec952 |b780f20 --- Comment #15 from Kurt Hindenburg --- Git commit b246ac57ee8000e15e71d833701fbcab0b780f20 by Kurt Hindenburg, on behalf of Luis Javier Merino Morán. Committed on 24/05/2021 at 19:23. Pushed by hindenburg into branch 'release/21.04'. Fix crash when using a color scheme with random colors A new assert in GCC 11.1.0 std::piecewise_linear_distribution fails in the case that the lower and upper boundaries are equal. So, make sure to not construct a std::piecewise_linear_distribution when minSaturation equals maxSaturation and when minLightness equals maxLightness. (cherry picked from commit 8c24953bdefc28fa7f1db1d0b77f855f3c1ec952) M +19 -13 src/colorscheme/ColorScheme.cpp https://invent.kde.org/utilities/konsole/commit/b246ac57ee8000e15e71d833701fbcab0b780f20 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 434892] Crash when using a color scheme with "random" background colors
https://bugs.kde.org/show_bug.cgi?id=434892 Nate Graham changed: What|Removed |Added Version Fixed In||21.08 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 437153] filenamesearch crashes in KCoreDirLister
https://bugs.kde.org/show_bug.cgi?id=437153 Nate Graham changed: What|Removed |Added Version Fixed In||5.83 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 421882] Allow Virtual Desktop List to Use Double Click to Edit Desktop Name
https://bugs.kde.org/show_bug.cgi?id=421882 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Severity|normal |wishlist CC||n...@kde.org Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 426627] Ability re-arrange existing virtual desktops
https://bugs.kde.org/show_bug.cgi?id=426627 Nate Graham changed: What|Removed |Added CC||xer...@pm.me --- Comment #1 from Nate Graham --- *** Bug 429918 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429918] Enable reordering virtual desktops
https://bugs.kde.org/show_bug.cgi?id=429918 Nate Graham changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 426627 *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437626] New: Krita crashes on save when documents are too large, and contain procedural layers
https://bugs.kde.org/show_bug.cgi?id=437626
Bug ID: 437626
Summary: Krita crashes on save when documents are too large,
and contain procedural layers
Product: krita
Version: 4.4.3
Platform: Other
OS: Microsoft Windows
Status: REPORTED
Severity: crash
Priority: NOR
Component: General
Assignee: krita-bugs-n...@kde.org
Reporter: menjah_transacti...@live.com
Target Milestone: ---
Created attachment 138753
--> https://bugs.kde.org/attachment.cgi?id=138753=edit
the file that crashes on autosave
SUMMARY
When creating 4k or 8k documents with multiple layers, Krita will often crash
on save, the crash can be triggered by an autosave or a manual save. This seems
to be caused by using procedural fill / filter layers -- deleting all fill
layers and replacing them with paint layers filled with a solid color seems to
prevent the crash.
I have tried turning most of the autosave / file handling settings on and off,
as well as switching the autosave drive from "same as file" to user, an HDD and
SSD, respectively, crash still happens.
I am using the Steam version on a win10 machine, crashing file attached.
I would submit a dxdiag but I can only add one attachment, so I've pasted it
below
STEPS TO REPRODUCE
1. open the crashing .kra
2. paint around a bit
3. save or wait for autosave
OBSERVED RESULT
crash!
EXPECTED RESULT
no crash!
SOFTWARE/OS VERSIONS
Windows: Win10
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
--
System Information
--
Time of this report: 5/24/2021, 12:10:26
Machine name: DESKTOP-DR1O1RV
Machine Id: {EE9A827C-2933-48B4-A69F-C13DD05CBAA7}
Operating System: Windows 10 Pro 64-bit (10.0, Build 19041)
(19041.vb_release.191206-1406)
Language: English (Regional Setting: English)
System Manufacturer: System manufacturer
System Model: System Product Name
BIOS: 1704 (type: UEFI)
Processor: Intel(R) Core(TM) i7-9800X CPU @ 3.80GHz (16 CPUs),
~3.8GHz
Memory: 65536MB RAM
Available OS Memory: 65206MB RAM
Page File: 56714MB used, 27504MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 12
DX Setup Parameters: Not found
User DPI Setting: 96 DPI (100 percent)
System DPI Setting: 192 DPI (200 percent)
DWM DPI Scaling: UnKnown
Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Not Supported
DirectX Database Version: 1.0.8
DxDiag Version: 10.00.19041.0928 64bit Unicode
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kio] [Bug 437153] filenamesearch crashes in KCoreDirLister
https://bugs.kde.org/show_bug.cgi?id=437153 Ahmad Samir changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/kio/commit/a38fcf356 ||de0cbba1ce97c8ef70979ed897a ||8094 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #6 from Ahmad Samir --- Git commit a38fcf356de0cbba1ce97c8ef70979ed897a8094 by Ahmad Samir, on behalf of Kai Uwe Broulik. Committed on 24/05/2021 at 19:16. Pushed by ahmadsamir into branch 'master'. [KCoreDirLister] Guard uiDelegate(), it might be null M +3-1src/core/kcoredirlister.cpp https://invent.kde.org/frameworks/kio/commit/a38fcf356de0cbba1ce97c8ef70979ed897a8094 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433854] A lot of times copy-paste does not work.
https://bugs.kde.org/show_bug.cgi?id=433854 Allexus J changed: What|Removed |Added Resolution|WORKSFORME |--- Status|RESOLVED|REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 433854] A lot of times copy-paste does not work.
https://bugs.kde.org/show_bug.cgi?id=433854 --- Comment #8 from Allexus J --- the issue still persists. kernel: 5.10.38-1-lts distro: archlinux KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 437625] New: Color model area of Advanced Color Selector doesn't change when selecting red
https://bugs.kde.org/show_bug.cgi?id=437625 Bug ID: 437625 Summary: Color model area of Advanced Color Selector doesn't change when selecting red Product: krita Version: nightly build (please specify the git hash!) Platform: Compiled Sources OS: All Status: REPORTED Severity: normal Priority: NOR Component: Color Selectors Assignee: krita-bugs-n...@kde.org Reporter: acc4commissi...@gmail.com Target Milestone: --- SUMMARY happens in both 4.x and 5.0 prealpha (git d1a1874) It seems only happen with red. STEPS TO REPRODUCE 1. Open Select a Color window and type any number in Red channel value. Green and Blue have to be 0. 2. Paint with that color on canvas, with full opacity. 3. Select any other colors in Advanced Color Selector. 4. With Color Picker, try to select back to the red you painted. OBSERVED RESULT The Hue in ACS changes, but the color of square(or triangle) inside doesn't change and remains as previous color. EXPECTED RESULT It should change. SOFTWARE/OS VERSIONS Windows: Win10 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.
[systemsettings] [Bug 425538] on-screen display period broken
https://bugs.kde.org/show_bug.cgi?id=425538 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Nate Graham --- Git commit b8580339b44e376dbf035cb7a93096f71319ee54 by Nate Graham, on behalf of David Edmundson. Committed on 24/05/2021 at 19:11. Pushed by ngraham into branch 'Plasma/5.22'. [kcmkwin/kwindesktop] Implement valueFromText in a spinbox If textFromValue is set, valueFromText must be. A lot of other implemenetations were using parseInt() which fails at reading "3,000" due to the comma. Qt's fromLocaleString handles that but needs any text stripping. This implementation isn't perfect, but really we need to work on a good upstream solution. (cherry picked from commit 5484b846b3869a8adca4cf801ca296b94017179e) M +1-0src/kcmkwin/kwindesktop/package/contents/ui/main.qml https://invent.kde.org/plasma/kwin/commit/b8580339b44e376dbf035cb7a93096f71319ee54 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 425538] on-screen display period broken
https://bugs.kde.org/show_bug.cgi?id=425538 Nate Graham changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/kwin/-/commit/b8580339b4 ||4e376dbf035cb7a93096f71319e ||e54 Version Fixed In||5.22 --- Comment #1 from Nate Graham --- Git commit 5484b846b3869a8adca4cf801ca296b94017179e by Nate Graham, on behalf of David Edmundson. Committed on 24/05/2021 at 18:51. Pushed by ngraham into branch 'master'. [kcmkwin/kwindesktop] Implement valueFromText in a spinbox If textFromValue is set, valueFromText must be. A lot of other implemenetations were using parseInt() which fails at reading "3,000" due to the comma. Qt's fromLocaleString handles that but needs any text stripping. This implementation isn't perfect, but really we need to work on a good upstream solution. M +1-0src/kcmkwin/kwindesktop/package/contents/ui/main.qml https://invent.kde.org/plasma/kwin/commit/5484b846b3869a8adca4cf801ca296b94017179e -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437460] "Apply" button remains greyed out after editing OSD time with keyboard
https://bugs.kde.org/show_bug.cgi?id=437460 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #5 from Nate Graham --- Git commit b8580339b44e376dbf035cb7a93096f71319ee54 by Nate Graham, on behalf of David Edmundson. Committed on 24/05/2021 at 19:11. Pushed by ngraham into branch 'Plasma/5.22'. [kcmkwin/kwindesktop] Implement valueFromText in a spinbox If textFromValue is set, valueFromText must be. A lot of other implemenetations were using parseInt() which fails at reading "3,000" due to the comma. Qt's fromLocaleString handles that but needs any text stripping. This implementation isn't perfect, but really we need to work on a good upstream solution. (cherry picked from commit 5484b846b3869a8adca4cf801ca296b94017179e) M +1-0src/kcmkwin/kwindesktop/package/contents/ui/main.qml https://invent.kde.org/plasma/kwin/commit/b8580339b44e376dbf035cb7a93096f71319ee54 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432618] Virtual Desktop settings app always sets on-screen display time to 0ms
https://bugs.kde.org/show_bug.cgi?id=432618 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #5 from Nate Graham --- Git commit b8580339b44e376dbf035cb7a93096f71319ee54 by Nate Graham, on behalf of David Edmundson. Committed on 24/05/2021 at 19:11. Pushed by ngraham into branch 'Plasma/5.22'. [kcmkwin/kwindesktop] Implement valueFromText in a spinbox If textFromValue is set, valueFromText must be. A lot of other implemenetations were using parseInt() which fails at reading "3,000" due to the comma. Qt's fromLocaleString handles that but needs any text stripping. This implementation isn't perfect, but really we need to work on a good upstream solution. (cherry picked from commit 5484b846b3869a8adca4cf801ca296b94017179e) M +1-0src/kcmkwin/kwindesktop/package/contents/ui/main.qml https://invent.kde.org/plasma/kwin/commit/b8580339b44e376dbf035cb7a93096f71319ee54 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437460] "Apply" button remains greyed out after editing OSD time with keyboard
https://bugs.kde.org/show_bug.cgi?id=437460 Nate Graham changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/kwin/-/commit/b8580339b4 ||4e376dbf035cb7a93096f71319e ||e54 Version Fixed In||5.22 --- Comment #4 from Nate Graham --- Git commit 5484b846b3869a8adca4cf801ca296b94017179e by Nate Graham, on behalf of David Edmundson. Committed on 24/05/2021 at 18:51. Pushed by ngraham into branch 'master'. [kcmkwin/kwindesktop] Implement valueFromText in a spinbox If textFromValue is set, valueFromText must be. A lot of other implemenetations were using parseInt() which fails at reading "3,000" due to the comma. Qt's fromLocaleString handles that but needs any text stripping. This implementation isn't perfect, but really we need to work on a good upstream solution. M +1-0src/kcmkwin/kwindesktop/package/contents/ui/main.qml https://invent.kde.org/plasma/kwin/commit/5484b846b3869a8adca4cf801ca296b94017179e -- You are receiving this mail because: You are watching all bug changes.
