[minuet] [Bug 441994] chord definitions for dominant seventh chords are mostly wrong
https://bugs.kde.org/show_bug.cgi?id=441994
dexx...@top-email.net changed:
What|Removed |Added
Ever confirmed|0 |1
Status|RESOLVED|REOPENED
Resolution|NOT A BUG |---
--- Comment #3 from dexx...@top-email.net ---
for example:
{
"tags": ["chord", "root-position", "major", "9", "extended"],
"name": "Major 9",
"sequence": "4 7 10 14"
},
shouldn't say "Major 9" but "Dominant 9", because the seventh is a minor
seventh.
A Xmaj9 chord is a major chord with a major seventh with a major ninth added, a
X9 chord is a major chord with a minor seventh and major ninth added. In the
example the seventh has 10 semitones which makes it a dominant chord.
I think the name of the chord is in all cases misleading. All "Major" and
"Minor" names should disappear in favour of the correct chord symbol.
the chord symbol should say X^9 because then its clear you want a dominant
seventh chord with a major ninth. A X^maj9 chord would contain a major seventh
and a major ninth
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 443237] focusing a window (with hover to focus) should not change its order on the "recently used" stack
https://bugs.kde.org/show_bug.cgi?id=443237 Adam Fontenot changed: What|Removed |Added Resolution|UNMAINTAINED|DUPLICATE --- Comment #3 from Adam Fontenot --- I misread the request to re-open the bug and ended up recreating it, I'm going to close this version as a duplicate because the new one is clearer about what the problem is. *** This bug has been marked as a duplicate of bug 476496 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476496] Hovering over a window raises it in the task switcher's "recently used" order when hover-to-focus is enabled
https://bugs.kde.org/show_bug.cgi?id=476496 --- Comment #1 from Adam Fontenot --- *** Bug 443237 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476496] New: Hovering over a window raises it in the task switcher's "recently used" order when hover-to-focus is enabled
https://bugs.kde.org/show_bug.cgi?id=476496 Bug ID: 476496 Summary: Hovering over a window raises it in the task switcher's "recently used" order when hover-to-focus is enabled Classification: Plasma Product: kwin Version: 5.27.9 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: tabbox Assignee: kwin-bugs-n...@kde.org Reporter: adam.m.fontenot+...@gmail.com Target Milestone: --- SUMMARY This boils down to breaking user expectations. Users who set hover-to-focus will often hover over multiple windows when moving the cursor from one window to another, but even though the intermediate windows are (briefly) focused, the user does not thereby show any intent to use the windows. In hover-to-focus mode (as well as any other mode), intent to use a window is only signaled by some other keyboard / mouse input on the window surface or when the window is raised. The result is a very annoying experience for hover-to-focus users who are switching back and forth between two windows with the task switcher (alt-tab). They will frequently end up switching to windows that they never intended to raise when the task switcher is activated. One proposed workaround is to use the "stacking order" in reversed mode (with the normal shortcut set to reverse and vice versa), which works around this specific issue because stacking order waits for the window to be raised before it affects the task switcher behavior. The problem with this is that stacking order *is not* what's wanted here, because stacking order includes windows set to "keep above" (always on top). If you are working on two windows that are not (both) set to keep above, activating the task switcher will switch to the window at the top of the stack, i.e. the window set to keep above. As far as I can see, other than adding a third sort order option to meet this need, the only possible way to get the behavior users of hover-to-focus expect is to change the "recently used" option so that hovering / focusing a window isn't enough for it to be considered "recently used". Focusing a window simply does not have those semantics when hover-to-focus is enabled. Changing this shouldn't affect any other use cases, because the only way to focus a window without hover-to-focus is to raise it. STEPS TO REPRODUCE 1. Enable hover-to-focus. Make sure the task switcher is set to "recently used" sort order. 2. Open three windows (e.g. kwrite). Type in one, move the cursor to the third while passing over the second, and click and type into the third. 3. Activate the task switcher (e.g. alt-tab). OBSERVED RESULT The task switcher activates the second window. EXPECTED RESULT The task switcher activates the most recently used window, i.e. the first window. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.5.9-arch2-1 (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION I was asked to recreate this bug for the current KWin version. The previous bug was https://bugs.kde.org/show_bug.cgi?id=443237 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476451] Compilation error with OpenJPEG
https://bugs.kde.org/show_bug.cgi?id=476451 --- Comment #3 from Amedeo Molnár --- The Problem with the patch was that it id not fix the error at all. it just prevented the OpenJPEG library to be found. -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 474125] Tokodon crash while idle
https://bugs.kde.org/show_bug.cgi?id=474125 rexbin...@icloud.com changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474044] Enter Animation has low fps
https://bugs.kde.org/show_bug.cgi?id=474044 Prajna Sariputra changed: What|Removed |Added CC||putr...@gmail.com --- Comment #6 from Prajna Sariputra --- I think I'm also experiencing this issue, I also see the `amdgpu: amdgpu_cs_ctx_create2 failed. (-13)` error messages while triggering overview/desktop grid combined effect, and the animations (especially concerning the desktop grid) feels rather choppy, certainly more so than in Plasma 5.27.9. I compiled Plasma 6 using kdesrc-build, KWin is currently at commit abf642d42e8189deaabf1999661e83aab25b99fa in the ~/kde/src/kwin folder, and my GPU is the AMD Radeon 680M (integrated with the AMD Ryzen 7 6800H), with Mesa 23.2.1, kernel 6.5.9, Qt 6.6.0, on Arch Linux. I also only tested with Wayland for now, so not sure how it looks with X11. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 436057] Current review sorting algorithm can cause... problems
https://bugs.kde.org/show_bug.cgi?id=436057 Nate Graham changed: What|Removed |Added Version Fixed In||6.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450874] Plasma Wayland remaps virtual tablet input
https://bugs.kde.org/show_bug.cgi?id=450874 Nate Graham changed: What|Removed |Added Version Fixed In||6.0 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 462041] Fingerprint unlock gets stuck after lock-then-sleep
https://bugs.kde.org/show_bug.cgi?id=462041 Nate Graham changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||6.0 Status|CONFIRMED |RESOLVED --- Comment #8 from Nate Graham --- This should be fixed in Plasma 6 now with a new authentication architecture used for the lock screen. -- You are receiving this mail because: You are watching all bug changes.
[PlasmaTube] [Bug 468796] Login to invidious instance not working
https://bugs.kde.org/show_bug.cgi?id=468796 --- Comment #6 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 474125] Tokodon crash while idle
https://bugs.kde.org/show_bug.cgi?id=474125 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 475814] Software Flashback
https://bugs.kde.org/show_bug.cgi?id=475814 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 450454] Crash when previewing online resource from Freesound
https://bugs.kde.org/show_bug.cgi?id=450454 --- Comment #9 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 470456] kdenlive crashes 24% into loading project clips with a segmentation fault
https://bugs.kde.org/show_bug.cgi?id=470456 --- 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.
[Discover] [Bug 445652] /var/lib/PackageKit/offline-update-action file not deleted automatically, causing Discover to always suggest a reboot
https://bugs.kde.org/show_bug.cgi?id=445652 --- Comment #14 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 476495] New: Incorrect flattening of animated layers with filter masks
https://bugs.kde.org/show_bug.cgi?id=476495 Bug ID: 476495 Summary: Incorrect flattening of animated layers with filter masks Classification: Applications Product: krita Version: 5.2.1 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: paleh21...@proton.me Target Milestone: --- Created attachment 162833 --> https://bugs.kde.org/attachment.cgi?id=162833=edit frame 3 after flattening on frame 1 STEPS TO REPRODUCE 1. Create an empty paint layer. 2. Create several (at least 3) frames on this layer. Draw something on these frames such that the bounding boxes of the frames intersect but don't entirely cover each other. 3. Add a filter mask for this layer, for example HSV/HSL Adjustment. 4. Switch to the first frame. 5. Flatten the animated layer. OBSERVED RESULT Switching to other frames, we can see that they contain elements of other frames. In the attached screenshot, each frame originally contained only one number, but after flattening frame 3 now contains parts of all 3 of them. EXPECTED RESULT Flattening keeps all the frames consistent with their projection before flattening. SOFTWARE/OS VERSIONS Linux: Ubuntu 22.04 Qt Version: 5.15.7 Appimage ADDITIONAL INFORMATION Bug is present in 5.2.0 and 5.3.0-7258fce19ce but is not present in 5.1.5 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 461891] Media control keyboard shortcuts always work on lock screen even if display of media control buttons is disabled
https://bugs.kde.org/show_bug.cgi?id=461891 Roman Odaisky changed: What|Removed |Added Version|5.25.5 |5.27.8 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 474283] Dolphin crashes when connecting to Thunderbolt
https://bugs.kde.org/show_bug.cgi?id=474283 fanzhuyi...@gmail.com changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||fanzhuyi...@gmail.com Resolution|--- |BACKTRACE --- Comment #3 from fanzhuyi...@gmail.com --- Hi! Thank you for your bug report. If you can reproduce this issue, could you try obtaining a backtrace with debug symbols? The wiki has instructions: https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports Thanks! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 471439] Konsole and other KDE applications crash on startup with global app menu enabled and more than one monitor connected
https://bugs.kde.org/show_bug.cgi?id=471439 --- Comment #19 from fanzhuyi...@gmail.com --- *** Bug 475804 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 475804] App crashes when external monitor is connected via USB Type C
https://bugs.kde.org/show_bug.cgi?id=475804 fanzhuyi...@gmail.com changed: What|Removed |Added Resolution|--- |DUPLICATE CC||fanzhuyi...@gmail.com Status|REPORTED|RESOLVED --- Comment #1 from fanzhuyi...@gmail.com --- *** This bug has been marked as a duplicate of bug 471439 *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 471439] Konsole and other KDE applications crash on startup with global app menu enabled and more than one monitor connected
https://bugs.kde.org/show_bug.cgi?id=471439 fanzhuyi...@gmail.com changed: What|Removed |Added Status|REOPENED|CONFIRMED --- Comment #18 from fanzhuyi...@gmail.com --- Marking as confirmed from the number of duplicate reports. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 471439] Konsole and other KDE applications crash on startup with global app menu enabled and more than one monitor connected
https://bugs.kde.org/show_bug.cgi?id=471439 --- Comment #17 from fanzhuyi...@gmail.com --- Should the product/component be changed since people are reporting this for a lot of applications, not just konsole? -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 470591] Kcalc shows 'nan' when pasting anything
https://bugs.kde.org/show_bug.cgi?id=470591 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #5 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/utilities/kcalc/-/merge_requests/67 -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 142728] when you click x10^y you cannot change the sign of y until the number y is inserted
https://bugs.kde.org/show_bug.cgi?id=142728 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #5 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/utilities/kcalc/-/merge_requests/67 -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 459999] can't easily calculate percentages
https://bugs.kde.org/show_bug.cgi?id=45 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #1 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/utilities/kcalc/-/merge_requests/67 -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 447347] pasting numbers starting with zero are parsed as octal
https://bugs.kde.org/show_bug.cgi?id=447347 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #6 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/utilities/kcalc/-/merge_requests/67 -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 470371] Feature request: edit the formula on the fly and see result
https://bugs.kde.org/show_bug.cgi?id=470371 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/utilities/kcalc/-/merge_requests/67 -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 443276] KCalc v19.12.3 - 500+200*2=1000
https://bugs.kde.org/show_bug.cgi?id=443276 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0 |1 --- Comment #6 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/utilities/kcalc/-/merge_requests/67 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 471439] Konsole and other KDE applications crash on startup with global app menu enabled and more than one monitor connected
https://bugs.kde.org/show_bug.cgi?id=471439 --- Comment #16 from fanzhuyi...@gmail.com --- *** Bug 458535 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 458535] Dolphin crashes on X11 multimonitor setup
https://bugs.kde.org/show_bug.cgi?id=458535 fanzhuyi...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||fanzhuyi...@gmail.com --- Comment #1 from fanzhuyi...@gmail.com --- Very likely duplicate of 471439 *** This bug has been marked as a duplicate of bug 471439 *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 471439] Konsole and other KDE applications crash on startup with global app menu enabled and more than one monitor connected
https://bugs.kde.org/show_bug.cgi?id=471439 --- Comment #15 from fanzhuyi...@gmail.com --- *** Bug 474903 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 474903] Dolphin crashes when external monitor is connected via USB type C/Thunderbolt docking station
https://bugs.kde.org/show_bug.cgi?id=474903 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from fanzhuyi...@gmail.com --- Very likely duplicate of 471439 *** This bug has been marked as a duplicate of bug 471439 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476390] Non-destructive date information management
https://bugs.kde.org/show_bug.cgi?id=476390 --- Comment #2 from LK --- For reference, I have created a script for those that run into this and have a backup of the original files available: https://gist.github.com/lkraider/83856fca740320751194bdf9c60a2ab6 This allows to keep the edited metadata info for the files, while updating the modified time back to those of the backup. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 476029] Dolphin crashes when trying to delete file, after using custom service menu
https://bugs.kde.org/show_bug.cgi?id=476029 fanzhuyi...@gmail.com changed: What|Removed |Added CC||fanzhuyi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 476029] Dolphin crashes when trying to delete file, after using custom service menu
https://bugs.kde.org/show_bug.cgi?id=476029 --- Comment #2 from fanzhuyi...@gmail.com --- Created attachment 162832 --> https://bugs.kde.org/attachment.cgi?id=162832=edit New crash information added by DrKonqi dolphin (23.08.2) using Qt 5.15.11 Steps to reproduce: 1. right click a pdf file and choose open with ocular/firefox 2. switch back to the dolphin window and press delete to delete the file Observed behavior: Dolphin crashes -- Backtrace (Reduced): #8 0x7f7d99b990d6 in qobject_cast(QObject*) (object=0x55db14355c00, object=) at ../../include/QtCore/../../src/corelib/kernel/qobject.h:519 #9 qWidgetShortcutContextMatcher(QObject*, Qt::ShortcutContext) (object=0x55db14355c00, context=Qt::WindowShortcut) at kernel/qshortcut.cpp:112 #10 0x7f7d99375f2c in QShortcutEntry::correctContext() const (this=0x55db13ccb418) at kernel/qshortcutmap.cpp:79 #11 QShortcutMap::find(QKeyEvent*, int) (this=this@entry=0x55db138d60f8, e=e@entry=0x7ffc13d82d30, ignoredModifiers=ignoredModifiers@entry=0) at kernel/qshortcutmap.cpp:457 #12 0x7f7d99376a65 in QShortcutMap::nextState(QKeyEvent*) (this=this@entry=0x55db138d60f8, e=e@entry=0x7ffc13d82d30) at kernel/qshortcutmap.cpp:372 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kuserfeedback] [Bug 468336] 1.2.0: test suite is failing in openglinfosourcetest unit
https://bugs.kde.org/show_bug.cgi?id=468336 --- Comment #1 from kloczek --- Any update? Just tested 1.3.0 and looks like issue still is around. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 476494] New: Toolbar out of screen when drawing rectangle region
https://bugs.kde.org/show_bug.cgi?id=476494 Bug ID: 476494 Summary: Toolbar out of screen when drawing rectangle region Classification: Applications Product: Spectacle Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: tts...@outlook.com CC: k...@david-redondo.de Target Milestone: --- Created attachment 162831 --> https://bugs.kde.org/attachment.cgi?id=162831=edit Toolbar being pushed out of the screen SUMMARY When using "Rectangle Region" to capture something at the bottom of the screen, the toolbar gets out of the screen and becomes unclickable. Thus the user is not able to mark or copy the image. STEPS TO REPRODUCE 1. Click "Rectangle Region" in capture modes 2. Draw a rectangle near the bottom of screen 3. Move the rectangle down and observe the position of toolbar OBSERVED RESULT The toolbar was pushex out of the screen and becomes unclickable. EXPECTED RESULT The toolbar should move to the upper side of rectangle to avoid getting out of screen. SOFTWARE/OS VERSIONS Linux: 6.5.9-zen2-1-zen KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476493] Guides used previously stop the playback of a new longer clip placed in the same position, even after deleting the guides.
https://bugs.kde.org/show_bug.cgi?id=476493 --- Comment #1 from Rod --- Kdenlive version 23.08.2 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476493] New: Guides used previously stop the playback of a new longer clip placed in the same position, even after deleting the guides.
https://bugs.kde.org/show_bug.cgi?id=476493 Bug ID: 476493 Summary: Guides used previously stop the playback of a new longer clip placed in the same position, even after deleting the guides. Classification: I don't know Product: kde Version: unspecified Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: rodanthon...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE Here is a link to a video where I show the procedure: https://youtu.be/0YF3WRUwIIs I will leave this unlisted for a week. If you don't require it anymore I will delete it after that. OBSERVED RESULT Guides get stuck At 2:26 you will see that after changing the length of a clip the playback keeps on going past the end of the new clip (it “remembers” the previous clip). To avoid this issue I have placed guides at the end of the new clips so I can render only the present clip without a trailing blank video. 3:35 When I repeat the process with a new clip cut off the long video, a clip longer than the previous, even if I delete the guide, when I start the playback it stops where the guide was and freezes. Even if I manually move the position the image is frozen where the guide was, so I can’t find the end of the new clip. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468159] After waking from sleep with complex triple-monitor setup, middle screen's desktop has the wrong size and windows leave ghost trails
https://bugs.kde.org/show_bug.cgi?id=468159 Beyley Thomas changed: What|Removed |Added Version|5.27.8 |5.27.9 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kglobalaccel] [Bug 453423] Numpad shortcuts don't work in wayland sessions.
https://bugs.kde.org/show_bug.cgi?id=453423 arcangelze...@gmail.com changed: What|Removed |Added CC||arcangelze...@gmail.com --- Comment #16 from arcangelze...@gmail.com --- Confirming this bug is still present on OpenSUSE Tumbleweed 20231031 NumLock is turned ON. Operating System: openSUSE Tumbleweed 20231031 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.5.9-1-default (64-bit) Graphics Platform: Wayland Keyboard: Corsair Strife RGB (104-key standard ANSI layout) KDE Keyboard model: Generic | Generic 104-key PC Keyboard Layout: English (US); English (US, intl., with dead keys) (Neither fix this issue) This does not happen on X11. Within KDE shortcuts under system settings, pre-existing shortcuts involving the number pad appear like the following examples: "Ctrl+Num+5" "Alt+Num+5" "Meta+Num+0" I wonder if "Num" is being considered as a separate, non-existent key? To test this, I tried using the NumLock key in a shortcut assignment. It actually reads as "numlock" and terminates the sequence. I'm unable to get "Num" as a registered sequence step. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 476492] New: System does not stay asleep while lid closed
https://bugs.kde.org/show_bug.cgi?id=476492 Bug ID: 476492 Summary: System does not stay asleep while lid closed Classification: I don't know Product: kde Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: jeremi.campa...@gmail.com Target Milestone: --- SUMMARY This issue might be specific to Framework laptops. With lid close event set to hybrid sleep or sleep, the system will resume from sleep when AC power is connected during sleep, even while the lid is closed. The system will not go back to sleep. This is also an issue when it comes to charging with Framework laptops as the laptop will disconnect from AC power when hitting 100% and reconnect when the battery falls to around 98%. When this cycling happens, the system remains awake. STEPS TO REPRODUCE 1. With a Framework Laptop 13 (AMD 7040 Series in my case), close the lid of the device and confirm it went to sleep 2. Connect the system to AC power 3. Listen for the charging chime or peek at the screen OBSERVED RESULT The system fails to go back to sleep and remains awake, even after 30 minutes while the AC-DC cycling occurs on full charge. EXPECTED RESULT The system should go back to sleep by itself after handling the DC to AC event. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.5.9-arch2-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics Memory: 30.5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: Framework Product Name: Laptop 13 (AMD Ryzen 7040Series) System Version: A7 ADDITIONAL INFORMATION The firmware behaviour of this laptop that can play a role in this issue has been confirmed intentional and expected behaviour by Framework : https://community.frame.work/t/tracking-framework-amd-ryzen-7040-series-lid-wakeup-behavior-feedback/39128/31 -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 473787] Accounts do not persist on software restart
https://bugs.kde.org/show_bug.cgi?id=473787 --- Comment #6 from Colin J Thomson --- (In reply to Joshua Goins from comment #5) > Can you see if you experience this issue still with 23.08.2? I'm restarting > my Flatpak here constantly, and can't get it to log out without me > explicitly doing so. I suspect that it's asking you to log in again because > of an invalid token/other issue, which is something that will be clearer in > the next release. I'm not sure who this question is for, but FYI it works the same here with 23.08.2 as it did with 23.08.0 details in comment2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 341314] Plasma 5 somehow falls back to US keyboard after startup
https://bugs.kde.org/show_bug.cgi?id=341314 Rui Zhao changed: What|Removed |Added CC||renyune...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 474548] Filters do not work in GHNS dialogs
https://bugs.kde.org/show_bug.cgi?id=474548 Ismael Asensio changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||isma...@gmail.com --- Comment #6 from Ismael Asensio --- I can reproduce this on self-built Qt6.6. It seems like the views are not getting updated correctly, with a lot of extra un-filtered empty items at the end. Changing the view mode fixes this temporarily for the current filter. Beside that, the sorting selector does not get applied to the views nor to the menu (it stays showing `Recent Items`). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 474949] Full store.kde.org description is cut off in the GHNS dialog's details page
https://bugs.kde.org/show_bug.cgi?id=474949 --- Comment #5 from Ismael Asensio --- My bad, replied on the wrong bug report. Please Nate, mark this comment and the previous one as spam. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 474949] Full store.kde.org description is cut off in the GHNS dialog's details page
https://bugs.kde.org/show_bug.cgi?id=474949 Ismael Asensio changed: What|Removed |Added CC||isma...@gmail.com --- Comment #4 from Ismael Asensio --- I can reproduce this on self-built Qt6.6. It seems like the views are not getting updated correctly, with a lot of extra un-filtered empty items at the end. Changing the view mode fixes this temporarily for the current filter. Beside that, the sorting selector does not get applied to the views nor to the menu (it stays showing `Recent Items`). -- You are receiving this mail because: You are watching all bug changes.
[minuet] [Bug 404139] After taking a rhythm test, correctly answered percentage is incorrect.
https://bugs.kde.org/show_bug.cgi?id=404139 Tammes Burghard changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #3 from Tammes Burghard --- https://invent.kde.org/education/minuet/-/merge_requests/29 This should fix it -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476491] scrollOnButtonDown only works for buttons of the same device.
https://bugs.kde.org/show_bug.cgi?id=476491 munzua...@gmail.com changed: What|Removed |Added CC||munzua...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476491] New: scrollOnButtonDown only works for buttons of the same device.
https://bugs.kde.org/show_bug.cgi?id=476491 Bug ID: 476491 Summary: scrollOnButtonDown only works for buttons of the same device. Classification: Plasma Product: kwin Version: 5.27.8 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: munzua...@gmail.com Target Milestone: --- I hope this is the correct place to report this. If not, I'd appreciate it if you could point me to the right direction. scrollOnButtonDown only works for buttons of the same device. My scenario is this: I use input-remapper to remap buttons on my Elecom Huge trackball. I currently do on-button scrolling by holding the middle click while moving the trackball. I enabled it with these commands: $ qdbus org.kde.KWin /org/kde/KWin/InputDevice/event31 org.kde.KWin.InputDevice.scrollOnButtonDown true $ qdbus org.kde.KWin /org/kde/KWin/InputDevice/event31 org.kde.KWin.InputDevice.scrollButton 274 274 corresponds to the middle click button code. Instead of the middle click, I'd like to use another button. The problem is that, in my case, mouse cursor movements belong to event31 but input-remapper assigns remapped buttons to e.g. event28. I verify this by doing $ libinput debug-events When I try to assign the scrollButton to one of the other buttons that I remapped with input-remapper, it doesn't work. In this case, I try to do it with a button that I remapped to right click (button code 273). $ qdbus org.kde.KWin /org/kde/KWin/InputDevice/event31 org.kde.KWin.InputDevice.scrollOnButtonDown true $ qdbus org.kde.KWin /org/kde/KWin/InputDevice/event28 org.kde.KWin.InputDevice.scrollOnButtonDown true $ qdbus org.kde.KWin /org/kde/KWin/InputDevice/event28 org.kde.KWin.InputDevice.scrollButton 273 These commands have no effect and don't throw an error. Turns out that this feature only works when the mouse cursor movements and the scrollButton come from the same device. I tested it by plugging in another mouse and setting one of its buttons as the scrollButton with commands like shown above. When I hold that button on the second mouse while moving my trackball, it doesn't work. If I move the cursor with my second mouse instead of my trackball, it works. In my case, it works with the middle click because I haven't remapped it in input-remapper so it belongs to the same device as the mouse cursor movements (event31). STEPS TO REPRODUCE 1. Plug in two mice, mouse A and mouse B 2. $ libinput debug-events 3. Press the desired scrollButton on mouse A and move the cursor with mouse B 4. Note which eventXX those events belong to, as well as which button code corresponds to the desired button 5. Enable scrollOnButtonDown on mouse B with $ qdbus org.kde.KWin /org/kde/KWin/InputDevice/ org.kde.KWin.InputDevice.scrollOnButtonDown true 6. Set the desired button on mouse A as the scrollButton with $ qdbus org.kde.KWin /org/kde/KWin/InputDevice/ org.kde.KWin.InputDevice.scrollButton OBSERVED RESULT Holding down the desired scrollButton on mouse A and moving the cursor with mouse B only moves the cursor and doesn't scroll. EXPECTED RESULT Holding down the desired scrollButton on mouse A and moving the cursor with mouse B should scroll. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.5-arch1-1 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION I realize that my use case is very niche since I use a trackball and input-remapper but I think enabling this feature to work on two separate devices would be nice for other people as well who would like to e.g. hold down the space button and move the cursor to scroll. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425627] When Dolphin crashes or is force-quit with Ctrl+Alt+Esc , tabs aren't saved
https://bugs.kde.org/show_bug.cgi?id=425627 --- Comment #9 from Henning --- I disagree, what size of file are we talking about? This first issue is about bad UX, opened tabs being gone after bad closes. Saving it every like 3 minutes would not be a problem I think. Having different profiles with names and alll is a different topic, not directly related. It could be opt-out and I am still a fan of a Plasma "Energysaver" metasetting (blur, animations, etc) but it should automatically save. -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 476490] New: Haruna - allow passing custom arguments to MPV
https://bugs.kde.org/show_bug.cgi?id=476490 Bug ID: 476490 Summary: Haruna - allow passing custom arguments to MPV Classification: Applications Product: Haruna Version: 0.12.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic Assignee: georgefb...@gmail.com Reporter: marco_silv...@sapo.pt Target Milestone: --- Like other players based on MPV (SMPlayer, ...), please allow passing arguments to MPV so that is possible to add audio or video filters. As an example, boosting the center audio channel, which is a very common audio feature in Windows players, is possible via this method, otherwise we can't add those custom features in Haruna on our own. (e.g of filter for boosting center audio channel: lavfi=[pan=6c|c0=c0|c1=c1|c2=2.0*c2|c3=c3|c4=c4|c5=c5] ) SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.1 lts KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111 Qt Version: 5.15.11 -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 476489] New: Haruna OSD bar does not toggle with input
https://bugs.kde.org/show_bug.cgi?id=476489 Bug ID: 476489 Summary: Haruna OSD bar does not toggle with input Classification: Applications Product: Haruna Version: 0.12.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic Assignee: georgefb...@gmail.com Reporter: marco_silv...@sapo.pt Target Milestone: --- SUMMARY When playing a video in fullscreen, the OSD shows and hides with mouse movement, however, it does not show up with touch-input. Lets say I use a touch-screen convertible (surface, ideapad etc), then in Fullscreen there isn't a way to bring up the OSD. This makes difficulties in using Haruna. Maybe there are 2 options: - Ideally, haruna should respond to sliding left or from bottom for bringing up the corresponding UI's playlist or OSD. - or simply touching the sides (if an user doesn't like this, this could be an on/off setting ). - an alternative would be to provide "OSD toggle" as an action, so that at least we could configure a "left-click" action with it. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.1 lts KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111 Qt Version: 5.15.11 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476438] crash after login with nvidia 545.29.02
https://bugs.kde.org/show_bug.cgi?id=476438 Adi Stadi changed: What|Removed |Added Ever confirmed|0 |1 Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #3 from Adi Stadi --- stupid me. released version is different: with 535.129.03: all fine with 545.29.02: crash -- You are receiving this mail because: You are watching all bug changes.
[minuet] [Bug 404139] After taking a rhythm test, correctly answered percentage is incorrect.
https://bugs.kde.org/show_bug.cgi?id=404139 Tammes Burghard changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Tammes Burghard --- I was able to reproduce this and will see if I can fix it. It seems like it is counting the number of correctly clicked elements and assumes a total of ten such elements while there are in fact 40. -- You are receiving this mail because: You are watching all bug changes.
[minuet] [Bug 404139] After taking a rhythm test, correctly answered percentage is incorrect.
https://bugs.kde.org/show_bug.cgi?id=404139 Tammes Burghard changed: What|Removed |Added Assignee|sandroandr...@kde.org |k...@kuchenmampfer.de CC||k...@kuchenmampfer.de -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 476488] New: SystemMonitor crash on switch to Application
https://bugs.kde.org/show_bug.cgi?id=476488 Bug ID: 476488 Summary: SystemMonitor crash on switch to Application Classification: Applications Product: plasma-systemmonitor Version: 5.27.9 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: marianpol...@gmail.com CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Application: plasma-systemmonitor (5.27.9) Qt Version: 5.15.11 Frameworks Version: 5.111.0 Operating System: Linux 6.2.0-35-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.9 [KCrashBackend] -- Information about the crash: when click to application or any other tab - app crash The crash can be reproduced every time. -- Backtrace: Application: System Monitor (plasma-systemmonitor), signal: Segmentation fault [KCrash Handler] #4 0x in ?? () #5 0x7f8c4265600b in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7f8c4265607d in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7f8c427e7b56 in QAccessibleQuickItem::role() const () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7f8c43f73f5a in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #9 0x7f8c43f76cd8 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #10 0x7f8c43f78502 in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #11 0x7f8c4266464b in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x7f8c4266bef6 in QQuickItem::setParentItem(QQuickItem*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #13 0x7f8c4266c441 in QQuickItem::~QQuickItem() () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #14 0x7f8c3825c889 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so #15 0x7f8c41bd3dff in QQmlTableInstanceModel::destroyModelItem(QQmlDelegateModelItem*, QQmlTableInstanceModel::DestructionMode) () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #16 0x7f8c41bfbe69 in ?? () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #17 0x7f8c41bd3800 in QQmlTableInstanceModel::drainReusableItemsPool(int) () from /lib/x86_64-linux-gnu/libQt5QmlModels.so.5 #18 0x7f8c4275c9f0 in QQuickTableView::geometryChanged(QRectF const&, QRectF const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #19 0x7f8c4266324f in QQuickItem::setSize(QSizeF const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #20 0x7f8c41ce0565 in QQuickControlPrivate::resizeContent() () from /lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5 #21 0x7f8c41cdcf80 in QQuickControlPrivate::setRightPadding(double, bool) () from /lib/x86_64-linux-gnu/libQt5QuickTemplates2.so.5 #22 0x7f8c496f5ef3 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #23 0x7f8c496f6db7 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #24 0x7f8c496f4914 in QQmlBinding::update(QFlags) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #25 0x7f8c496d12c5 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #26 0x7f8c47ef3ebb in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7f8c496780db in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #28 0x7f8c496f5ec8 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #29 0x7f8c496f6db7 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #30 0x7f8c496f4914 in QQmlBinding::update(QFlags) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #31 0x7f8c496d12c5 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #32 0x7f8c47ef3ebb in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7f8c42664698 in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #34 0x7f8c426645cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #35 0x7f8c426645cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #36 0x7f8c426645cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #37 0x7f8c426645cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #38 0x7f8c426645cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #39 0x7f8c426645cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #40 0x7f8c426645cb in QQuickItemPrivate::setEffectiveVisibleRecur(bool) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #41 0x7f8c426645cb in
[frameworks-baloo] [Bug 476479] baloo_file (baloo_file), signal: Aborted
https://bugs.kde.org/show_bug.cgi?id=476479 tagwer...@innerjoin.org changed: What|Removed |Added CC||tagwer...@innerjoin.org --- Comment #2 from tagwer...@innerjoin.org --- There's been a change to limit the amount of RAM baloo can use to 512M (assuming you are on a system with systemd). See: https://bugs.kde.org/show_bug.cgi?id=446071#c9 Without a cap on memory, baloo can expand and slug the system performance. With the cap, you might find baloo starting to use swap when doing large write transactions. Also not good. I've been setting MemoryHigh=50% and MemorySwapMax=0B to find a "middle way". Your mileage may vary You can watch the files being indexed with "balooctl monitor", you should see them indexed in batches of 40. You say "KDE Frameworks Version: 5.111.0", did you update the system halfway through the indexing? You also say "Current size of index is 67.41 GiB" which doesn't sound healthy. -- You are receiving this mail because: You are watching all bug changes.
[minuet] [Bug 441994] chord definitions for dominant seventh chords are mostly wrong
https://bugs.kde.org/show_bug.cgi?id=441994 Tammes Burghard changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #2 from Tammes Burghard --- Hmmm. I just looked through the definitions and they look correct to me. I will close this, if you disagree feel free to reopen and explain in further detail. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 476374] Cursor focus jumps when in Preview and entering a tag
https://bugs.kde.org/show_bug.cgi?id=476374 --- Comment #4 from john-d-sm...@hotmail.com --- (In reply to Maik Qualmann from comment #3) > This now only happens when the facial region display is activated. What does this mean, specifically? By 'activated' do you mean - when a user has specifically clicked into the facial region tagging box? - when 'show face tags' is turned on? - when _any_ faces are tagged? I understand what was happening in the other bug got addressed with a focus switch, but the focus should never change up on a user *in the middle of them typing elsewhere.* Do I understand correctly that in 8.2.0 that will no longer happen, or that it will happen with facial regions? (tagged or untagged) -- You are receiving this mail because: You are watching all bug changes.
[minuet] [Bug 441994] chord definitions for dominant seventh chords are mostly wrong
https://bugs.kde.org/show_bug.cgi?id=441994 --- Comment #1 from Tammes Burghard --- Yes, that should work. If you want to do that just for yourself, you would have to find that file. I didn't find it yet, but will try to. However, adding definitions upstream also is an option. I will try to fix this mistake there. -- You are receiving this mail because: You are watching all bug changes.
[minuet] [Bug 441994] chord definitions for dominant seventh chords are mostly wrong
https://bugs.kde.org/show_bug.cgi?id=441994 Tammes Burghard changed: What|Removed |Added Assignee|sandroandr...@kde.org |k...@kuchenmampfer.de CC||k...@kuchenmampfer.de -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 476487] Created sequence disappears
https://bugs.kde.org/show_bug.cgi?id=476487 nadie.nada.nu...@mail.com changed: What|Removed |Added URL||https://www.reddit.com/r/kd ||enlive/comments/17m20f5/cre ||ated_sequence_disappears/ Version|unspecified |23.08.1 Platform|Other |Microsoft Windows -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 476375] Powerdevil fails to start with ddcutil-2.0.0, spikes cpu usage to max every few seconds
https://bugs.kde.org/show_bug.cgi?id=476375 Natalie Clarius changed: What|Removed |Added Assignee|plasma-b...@kde.org |natalie_clar...@yahoo.de -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 476487] New: Created sequence disappears
https://bugs.kde.org/show_bug.cgi?id=476487 Bug ID: 476487 Summary: Created sequence disappears Classification: Applications Product: kdenlive Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: nadie.nada.nu...@mail.com Target Milestone: --- Created attachment 162830 --> https://bugs.kde.org/attachment.cgi?id=162830=edit Disappearing sequence SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** I selected several video/audio clips comprising two full tracks in Kdenlive and chose "Create sequence from selection". Kdenlive asked for a name for the sequence, so I gave it one and pressed Enter. The created sequence briefly appeared in the project bin, but then it immediately disappeared. In a possibly related bug, adding a new sequence through the Project menu completely wipes the already present sequence (Sequence 1) so that I cannot see any clips at all. Please see this reddit post: https://www.reddit.com/r/kdenlive/comments/17m20f5/created_sequence_disappears/ STEPS TO REPRODUCE 1. Select some clips. 2. Right click and select "Create Sequence from Selection". 3. Give it a name and press Enter. OBSERVED RESULT The sequence is created, but disappears immediately from the project bin. EXPECTED RESULT The sequence should stay, of course. SOFTWARE/OS VERSIONS Windows 10 64bit Kdenlive 23.08.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 476484] Touch swipe scrolling in ScrollablePage does not work over text
https://bugs.kde.org/show_bug.cgi?id=476484 --- Comment #1 from Tammes Burghard --- The same applies for swiping with the pen, but there, selecting text is fine with me. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 476271] Scrollable Page only semi scrollable with touch and NavigationTabButton not clickable with pen
https://bugs.kde.org/show_bug.cgi?id=476271 Tammes Burghard changed: What|Removed |Added Resolution|NOT A BUG |MOVED --- Comment #2 from Tammes Burghard --- Alright, I opened them -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 476486] New: NavigationTabButtons can not be clicked by my tablet's pen
https://bugs.kde.org/show_bug.cgi?id=476486 Bug ID: 476486 Summary: NavigationTabButtons can not be clicked by my tablet's pen Classification: Frameworks and Libraries Product: frameworks-kirigami Version: 5.109.0 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: k...@kuchenmampfer.de CC: m...@ratijas.tk, notm...@gmail.com Target Milestone: Not decided SUMMARY *** I use Kasts on my surface tablet running fedora silverblue and have several touch issues. This bug report is for the third one: I can't click on the NavigationTabButtons in the drawer with my pen. Tapping with the finger works and clicking other buttons also works, but these NavigationTabButtons only get highlighted and not clicked. *** STEPS TO REPRODUCE 1. Use Kasts on a tablet with pen 2. Try to open the Episodes Page with the pen OBSERVED RESULT The button gets highlighted EXPECTED RESULT The button gets clicked SOFTWARE/OS VERSIONS Linux: Fedora Silverblue Kasts: 23.04.3 as a Flatpak KDE Frameworks Version: 5.109 Qt Version: 5.15.10 Tablet: Microsoft Surface Go 2 Pen: Microsoft Surface Pen -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 476481] Firefox Crashes de whole OS, mostly but not only, when watching videos.
https://bugs.kde.org/show_bug.cgi?id=476481 Bug Janitor Service changed: What|Removed |Added Severity|grave |crash -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 476484] Touch swipe scrolling in ScrollablePage does not work over text
https://bugs.kde.org/show_bug.cgi?id=476484 Tammes Burghard changed: What|Removed |Added Platform|Other |Flatpak OS|Other |Linux -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 476485] New: ScrollablePage Scrollbar can not be grabbed by my tablet's pen
https://bugs.kde.org/show_bug.cgi?id=476485 Bug ID: 476485 Summary: ScrollablePage Scrollbar can not be grabbed by my tablet's pen Classification: Frameworks and Libraries Product: frameworks-kirigami Version: 5.109.0 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: k...@kuchenmampfer.de CC: m...@ratijas.tk, notm...@gmail.com Target Milestone: Not decided SUMMARY *** I use Kasts on my surface tablet running fedora silverblue and have several touch issues. This bug report is for the second one: In most cases, I can't grab the auto hiding Scrollbar with my pen. I think I managed to do it once, but couldn't recreate that. *** STEPS TO REPRODUCE 1. Use Kasts on a tablet with pen 2. Try to scroll by grabbing the scrollbar with the pen and moving it OBSERVED RESULT If I am precise enough, the pen grabs the page behind the scrollbar and I can move it that way EXPECTED RESULT The pen grabs the scroll thingy and I can scroll by moving that up and down SOFTWARE/OS VERSIONS Linux: Fedora Silverblue Kasts: 23.04.3 as a Flatpak KDE Frameworks Version: 5.109 Qt Version: 5.15.10 Tablet: Microsoft Surface Go 2 Pen: Microsoft Surface Pen -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 476484] New: Touch swipe scrolling in ScrollablePage does not work over text
https://bugs.kde.org/show_bug.cgi?id=476484 Bug ID: 476484 Summary: Touch swipe scrolling in ScrollablePage does not work over text Classification: Frameworks and Libraries Product: frameworks-kirigami Version: 5.109.0 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: k...@kuchenmampfer.de CC: m...@ratijas.tk, notm...@gmail.com Target Milestone: Not decided SUMMARY *** I use Kasts on my surface tablet running fedora silverblue and have several touch issues. This bug is for the first one: When I try to scroll the main ScrollablePage via touch, it works great as long as the ScrollablePage contains a GridView or ListView. But when it contains text, swiping over it selects the text instead of scrolling which is weird. *** STEPS TO REPRODUCE 1. Use Kasts on a tablet with pen 2. Open the Episodes Page with your finger 3. Open a single episode that has a page filling (long enough) description 4. Try to scroll by swiping over the text OBSERVED RESULT Text is selected EXPECTED RESULT The page gets scrolled SOFTWARE/OS VERSIONS Linux: Fedora Silverblue Kasts: 23.04.3 as a Flatpak KDE Frameworks Version: 5.109 Qt Version: 5.15.10 Tablet: Microsoft Surface Go 2 Pen: Microsoft Surface Pen -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 476375] Powerdevil fails to start with ddcutil-2.0.0, spikes cpu usage to max every few seconds
https://bugs.kde.org/show_bug.cgi?id=476375 Nate Graham changed: What|Removed |Added Summary|Powerdevil-5.27.9 fails to |Powerdevil fails to start |start with ddcutil-2.0.0, |with ddcutil-2.0.0, spikes |spikes cpu usage to max |cpu usage to max every few |every few seconds |seconds Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #12 from Nate Graham --- Thanks Antonio, that makes sense. So it sounds like the triggering factor here was in fact ddcutil 2.0, but of course we'll need to adapt to whatever change they made to cause this issue anyway. Natalie or Nicolas, would either of you be able to look into this? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-qqc2-desktop-style] [Bug 476483] New: Scrollbar handles are incorrectly sized and positioned until the window is resized
https://bugs.kde.org/show_bug.cgi?id=476483 Bug ID: 476483 Summary: Scrollbar handles are incorrectly sized and positioned until the window is resized Classification: Frameworks and Libraries Product: frameworks-qqc2-desktop-style Version: unspecified Platform: Other OS: Linux Status: REPORTED Keywords: qt6, regression Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: n...@kde.org CC: ahiems...@heimr.nl, k...@davidedmundson.co.uk, m...@ratijas.tk, noaha...@gmail.com, notm...@gmail.com Target Milestone: --- Plasma 6 Wayland built from git master against Qt 6.5.2 STEPS TO REPRODUCE 1. Run any QML-based KDE app that has scrollviews using the default qqc2-desktop-style. Apps that exhibit it: - System Settings - Discover - Cuttlefish - NeoChat - Scrollable views in Plasma widget config pages 2. Look at the scroll handle in a scrollable view OBSERVED RESULT The handle suffers from a variety of interrelated issues: - Initial size is too small - When dragged, the handle does not follow the cursor - Then scrolled using a touchpad or a mouse wheel, the handle does not move at all until you've scrolled a certain distance, or scrolled all the way to the bottom at least once EXPECTED RESULT None of those things happen ADDITIONAL INFORMATION When you resize the window, the scroll handle's problems disappear and it returns to normal. Does not happen with qqc2-breeze-style. This only started happening 2 days ago. I tried bisecting qqc2-desktop-style, but was unsuccessful. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476482] New: Widgets' activation shortcuts don't close their popups anymore
https://bugs.kde.org/show_bug.cgi?id=476482 Bug ID: 476482 Summary: Widgets' activation shortcuts don't close their popups anymore Classification: Plasma Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Keywords: qt6, regression Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: n...@kde.org CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Plasma 6 Wayland compiled from source this morning. STEPS TO REPRODUCE 1. Press Meta key to open Kickoff 2. Press it again OBSERVED RESULT Kickoff remains open EXPECTED RESULT Kickoff closes ADDITIONAL INFORMATION Also reproduces for custom shortcuts, e.g. my Meta+N shortcut to open a Notes widget on my panel no longer closes it. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 476481] New: Firefox Crashes de whole OS, mostly but not only, when watching videos.
https://bugs.kde.org/show_bug.cgi?id=476481 Bug ID: 476481 Summary: Firefox Crashes de whole OS, mostly but not only, when watching videos. Classification: KDE Neon Product: neon Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: grave Priority: NOR Component: general Assignee: neon-b...@kde.org Reporter: gau...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org Target Milestone: --- SUMMARY I don't know how long ago, probably no more than two months, my system began crashing mostly when viewing videos in Youtube with Firefox. Although it also crashed once just having Whatsapp Web opened. Let me point out that I didn't do any hardware change. STEPS TO REPRODUCE 1. Open Firefox 2. Start watching videos on YouTube 3. Wait until everything crashes OBSERVED RESULT Both of my screens go black, but the mouse cursor remains visible and frozen. Audio keeps working, for instance, if I'm having a remote call, the call continues, I can still talk with the other party. If I was sharing screen, I ask the other party to tell my if my cursor moves when I move the mouse, and it doesn't. It seems all inputs get frozen since I cannot even access any tty with CTRL+ALT+FX The only thing I can do at this point is a hard reset. EXPECTED RESULT To be able to use Firefox wihout any crashes. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Neon 5.27 KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Graphics Platform: X11 Graphic Card: ASUSTeK Computer Inc. Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] ADDITIONAL INFORMATION I usually run xanmod kernel but I tried with the general kernel and the problem is exactly the same. -- You are receiving this mail because: You are watching all bug changes.
[kmailtransport] [Bug 476480] KMail/Akonadi applies Unicode compatibility decomposition to sender and recipient names before sending
https://bugs.kde.org/show_bug.cgi?id=476480 --- Comment #1 from Erin Yuki Schlarb --- Just to avoid any potential misunderstandings I’d also like to point out that Unicode “compatibility” normalizations are not about “improving compatibility with software” but to make “compatible characters” equivalent during machine processing (typically full-text searches). I’m adding this specifically because I know e-mail is basically a giant compatibility hack and removing anything “cf compatibility“ may be met with an immediate “we can’t, it might break something”. -- You are receiving this mail because: You are watching all bug changes.
[kmailtransport] [Bug 476480] New: KMail/Akonadi applies Unicode compatibility decomposition to sender and recipient names before sending
https://bugs.kde.org/show_bug.cgi?id=476480 Bug ID: 476480 Summary: KMail/Akonadi applies Unicode compatibility decomposition to sender and recipient names before sending Classification: Applications Product: kmailtransport Version: unspecified Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: erin-kde@ninetailed.ninja Target Milestone: --- SUMMARY When changing my identity settings KMail settings to make use of U+2004 (THREE-PER-EM SPACE / thick space) and U+2009 (THIN SPACE) to visually separate the parts of my name I noticed that KMail shows these correctly in settings and composer, but the actually sent messages instead use U+0020 (ASCII SPACE). While I have not verified this in the source code I’m almost certain this is due to KMail/Akonadi/KMailTransport applying Unicode compatibility decomposition (NFKC normalization) before encoding the sender and recipient names. GitHub at least doesn’t seem to have any problems encoding these correctly and they are displayed correctly in KMail in messages received from it. Python’s `email.header` appears to encode it basically the same way. In particular for the name “First Collective Last” (using the mentioned U+2004 and U+2009), the three tested implements yield: 1. KMail/Akonadi/KMailTransport: “From: First Collective Last ” (using just ASCII spaces everywhere) 2. GitHub: “From: =?UTF-8?b?Rmlyc3TigIRDb2xsZWN0aXZl4oCJTGFzdA==?= ” 3. Python `email.header`: “From: =?utf-8?b?Rmlyc3TigIRDb2xsZWN0aXZl4oCJTGFzdA==?= “ STEPS TO REPRODUCE 1. Compose an email to “First Collective Last ” (copy-paste it!) in KMail – replacing the address as intended OBSERVED RESULT The received message has the fancy spaces replaced with the plain ASCII ones and hence contains a “To: First Collective Last ” as a header, discarding the extra information originally entered EXPECTED RESULT The fancy quotes should remain and be encoded instead. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian unstable KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476384] Task Switcher visualization stuck on "Breeze"
https://bugs.kde.org/show_bug.cgi?id=476384 --- Comment #3 from Nate Graham --- ~/.config/kwinrc is a *directory*? That's unexpected. Where is your kwinrc file stored? How did you install your system? -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 476299] Open containing folder, after selecting multiple images, fails to open a single file dialog window like it use to.
https://bugs.kde.org/show_bug.cgi?id=476299 Marc Chamberlin changed: What|Removed |Added CC||m...@marcchamberlin.com -- You are receiving this mail because: You are watching all bug changes.
[Plasma Vault] [Bug 386200] Import Vault
https://bugs.kde.org/show_bug.cgi?id=386200 Sefa Eyeoglu changed: What|Removed |Added CC|cont...@scrumplex.net | -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 439637] Unnecessary control buttons under every preview window
https://bugs.kde.org/show_bug.cgi?id=439637 Teoh Han Hui changed: What|Removed |Added CC||teohhan...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 476479] baloo_file (baloo_file), signal: Aborted
https://bugs.kde.org/show_bug.cgi?id=476479
--- Comment #1 from David Kredba ---
I am sorry, the complete backtrace follows:
Application: baloo_file (baloo_file), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[KCrash Handler]
#6 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
#7 0x7f29a60b3b6f in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78
#8 0x7f29a6063a02 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#9 0x7f29a604c22d in __GI_abort () at abort.c:79
#10 0x7f29a604d29c in __libc_message (fmt=fmt@entry=0x7f29a619d0da "%s\n")
at ../sysdeps/posix/libc_fatal.c:150
#11 0x7f29a60bd975 in malloc_printerr (str=str@entry=0x7f29a61a07f0
"mremap_chunk(): invalid pointer") at malloc.c:5765
#12 0x7f29a60c2cec in mremap_chunk (new_size=48, p=0x7f29a68663d0
) at malloc.c:3063
#13 __GI___libc_realloc (oldmem=0x7f29a68663e0 ,
bytes=32) at malloc.c:3473
#14 0x7f29a660c463 in QListData::realloc_grow
(this=this@entry=0x55da3b0a3a80, growth=growth@entry=1) at
/var/tmp/portage/dev-qt/qtcore-5.15.11-r1/work/qtbase-everywhere-src-5.15.11/src/corelib/tools/qlist.cpp:170
#15 0x7f29a660c50a in QListData::append (this=0x55da3b0a3a80, n=n@entry=1)
at
/var/tmp/portage/dev-qt/qtcore-5.15.11-r1/work/qtbase-everywhere-src-5.15.11/src/corelib/tools/qlist.cpp:196
#16 0x7f29a660c53a in QListData::append (this=) at
/var/tmp/portage/dev-qt/qtcore-5.15.11-r1/work/qtbase-everywhere-src-5.15.11/src/corelib/tools/qlist.cpp:206
#17 0x55da39d34781 in QList::append (t=..., this=)
at /usr/include/qt5/QtCore/qlist.h:643
#18 QList::append (this=, t=...) at
/usr/include/qt5/QtCore/qlist.h:620
#19 0x55da39d43ed9 in Baloo::FileContentIndexer::slotFinishedIndexingFile
(this=0x55da3b0a3a40, filePath=..., fileUpdated=) at
/var/tmp/portage/kde-frameworks/baloo-5.111.0/work/baloo-5.111.0/src/file/filecontentindexer.cpp:125
#20 0x7f29a67b4024 in QObject::event (this=0x55da3b0a3a40,
e=0x7ee99432ba20) at
/var/tmp/portage/dev-qt/qtcore-5.15.11-r1/work/qtbase-everywhere-src-5.15.11/src/corelib/kernel/qobject.cpp:1347
#21 0x7f29a6788f25 in doNotify (event=0x7ee99432ba20,
receiver=0x55da3b0a3a40) at
/var/tmp/portage/dev-qt/qtcore-5.15.11-r1/work/qtbase-everywhere-src-5.15.11/src/corelib/kernel/qcoreapplication.cpp:1154
#22 QCoreApplication::notify (event=, receiver=,
this=) at
/var/tmp/portage/dev-qt/qtcore-5.15.11-r1/work/qtbase-everywhere-src-5.15.11/src/corelib/kernel/qcoreapplication.cpp:1140
#23 QCoreApplication::notifyInternal2 (receiver=0x55da3b0a3a40,
event=0x7ee99432ba20) at
/var/tmp/portage/dev-qt/qtcore-5.15.11-r1/work/qtbase-everywhere-src-5.15.11/src/corelib/kernel/qcoreapplication.cpp:1064
#24 0x7f29a678914e in QCoreApplication::sendEvent (receiver=, event=) at
/var/tmp/portage/dev-qt/qtcore-5.15.11-r1/work/qtbase-everywhere-src-5.15.11/src/corelib/kernel/qcoreapplication.cpp:1462
#25 0x7f29a678c4c3 in QCoreApplicationPrivate::sendPostedEvents
(receiver=0x0, event_type=0, data=0x55da3b083b70) at
/var/tmp/portage/dev-qt/qtcore-5.15.11-r1/work/qtbase-everywhere-src-5.15.11/src/corelib/kernel/qcoreapplication.cpp:1821
#26 0x7f29a678c778 in QCoreApplication::sendPostedEvents
(receiver=, event_type=) at
/var/tmp/portage/dev-qt/qtcore-5.15.11-r1/work/qtbase-everywhere-src-5.15.11/src/corelib/kernel/qcoreapplication.cpp:1680
#27 0x7f29a67db013 in postEventSourceDispatch (s=0x55da3b0853f0) at
/var/tmp/portage/dev-qt/qtcore-5.15.11-r1/work/qtbase-everywhere-src-5.15.11/src/corelib/kernel/qeventdispatcher_glib.cpp:277
#28 0x7f29a4f73d52 in g_main_dispatch
(context=context@entry=0x55da3b085180) at ../glib-2.78.1/glib/gmain.c:3476
#29 0x7f29a4f76f07 in g_main_context_dispatch_unlocked
(context=0x55da3b085180) at ../glib-2.78.1/glib/gmain.c:4284
#30 g_main_context_iterate_unlocked (context=context@entry=0x55da3b085180,
block=block@entry=1, dispatch=dispatch@entry=1, self=) at
../glib-2.78.1/glib/gmain.c:4349
#31 0x7f29a4f7752c in g_main_context_iteration (context=0x55da3b085180,
may_block=1) at ../glib-2.78.1/glib/gmain.c:4414
#32 0x7f29a67dab16 in QEventDispatcherGlib::processEvents
(this=0x55da3b085080, flags=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.11-r1/work/qtbase-everywhere-src-5.15.11/src/corelib/kernel/qeventdispatcher_glib.cpp:423
#33 0x7f29a678797b in QEventLoop::exec (this=this@entry=0x7ffcd9102b80,
flags=..., flags@entry=...) at
/var/tmp/portage/dev-qt/qtcore-5.15.11-r1/work/qtbase-everywhere-src-5.15.11/include/QtCore/../../src/corelib/global/qflags.h:69
#34 0x7f29a678fc7d in QCoreApplication::exec () at
/var/tmp/portage/dev-qt/qtcore-5.15.11-r1/work/qtbase-everywhere-src-5.15.11/include/QtCore/../../src/corelib/global/qflags.h:121
#35 0x55da39d33915 in main (argc=, argv=) at
/var/tmp/portage/kde-frameworks/baloo-5.111.0/work/baloo-5.111.0/src/file/main.cpp:78
[Inferior 1 (process 5469) detached]
--
You are receiving
[frameworks-baloo] [Bug 476479] New: baloo_file (baloo_file), signal: Aborted
https://bugs.kde.org/show_bug.cgi?id=476479 Bug ID: 476479 Summary: baloo_file (baloo_file), signal: Aborted Classification: Frameworks and Libraries Product: frameworks-baloo Version: 5.111.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: kre...@kredba.cz Target Milestone: --- SUMMARY I am indexing from scratch, it takes terrible ages (over one month already, 14 hours a day, EXT4 on LUKS2 on MDRAID on rotating HDDs to index file stored on EXT4 on LUKS2 on SSD) and came home to see a KCrash handler icon. There is still 50 GiB of free space on SSD storing the index file. The 'balooctl status' command returns: Baloo File Indexer is not running Total files indexed: 716,213 Files waiting for content indexing: 151,027 Files failed to index: 0 Current size of index is 67.41 GiB OBSERVED RESULT #6 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #7 0x7f29a60b3b6f in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #8 0x7f29a6063a02 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #9 0x7f29a604c22d in __GI_abort () at abort.c:79 #10 0x7f29a604d29c in __libc_message (fmt=fmt@entry=0x7f29a619d0da "%s\n") at ../sysdeps/posix/libc_fatal.c:150 #11 0x7f29a60bd975 in malloc_printerr (str=str@entry=0x7f29a61a07f0 "mremap_chunk(): invalid pointer") at malloc.c:5765 #12 0x7f29a60c2cec in mremap_chunk (new_size=48, p=0x7f29a68663d0 ) at malloc.c:3063 #13 __GI___libc_realloc (oldmem=0x7f29a68663e0 , bytes=32) at malloc.c:3473 #14 0x7f29a660c463 in QListData::realloc_grow (this=this@entry=0x55da3b0a3a80, growth=growth@entry=1) at /var/tmp/portage/dev-qt/qtcore-5.15.11-r1/work/qtbase-everywhere-src-5.15.11/src/corelib/tools/qlist.cpp:170 #15 0x7f29a660c50a in QListData::append (this=0x55da3b0a3a80, n=n@entry=1) at /var/tmp/portage/dev-qt/qtcore-5.15.11-r1/work/qtbase-everywhere-src-5.15.11/src/corelib/tools/qlist.cpp:196 #16 0x7f29a660c53a in QListData::append (this=) at /var/tmp/portage/dev-qt/qtcore-5.15.11-r1/work/qtbase-everywhere-src-5.15.11/src/corelib/tools/qlist.cpp:206 #17 0x55da39d34781 in QList::append (t=..., this=) at /usr/include/qt5/QtCore/qlist.h:643 SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 Kernel Version: 6.6.0-gentoo (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 3800X 8-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series Manufacturer: Gigabyte Technology Co., Ltd. Product Name: X570 AORUS ELITE System Version: -CF -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466448] Allow forwarding mouse button events to X11 apps using "Legacy X11 App Support" page
https://bugs.kde.org/show_bug.cgi?id=466448 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/4595 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 476384] Task Switcher visualization stuck on "Breeze"
https://bugs.kde.org/show_bug.cgi?id=476384 --- Comment #2 from Tom Chiverton --- Err, $ grep LayoutName ~/.config/kwinrc grep: /home/falken/.config/kwinrc: Is a directory ~/.config/kwinrc/qmlcache (the only file in it) doesn't contain LayoutName before changing the dropdown, or after pressing apply. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476383] Panel spacers center applets in free space, instead of in the middle of the panel
https://bugs.kde.org/show_bug.cgi?id=476383 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3465 -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 476478] New: Kontact Crashes when trying to view Identities
https://bugs.kde.org/show_bug.cgi?id=476478 Bug ID: 476478 Summary: Kontact Crashes when trying to view Identities Classification: Applications Product: kontact Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: dave.conn...@gmail.com Target Milestone: --- Application: kontact (5.24.2 (23.08.2)) Qt Version: 5.15.11 Frameworks Version: 5.111.0 Operating System: Linux 6.5.9-arch2-1 x86_64 Windowing System: X11 Distribution: "Arch Linux" DrKonqi: 5.27.9 [KCrashBackend] -- Information about the crash: I have been dealing with issues relating to changing settings in my kmail. I tried to change the domain that is used in one of my identities. I tried sending an email from kmail after changing these settings, but my emails were being denied by Google due to DKIM (different issue). I noticed on the return to sender, that the domain still hadn't changed to what I had set in the Kontact settings. I deleted some emails from my outbox from the GUI, however Kmail then crashed. I tried cleaning the folders manually after following instructions from this bug report. https://bugs.kde.org/show_bug.cgi?id=339214#c24 I got it working after restarting my computer, however now I occasionally get crashes in the Kontact settings menu, especially when trying to view the Identities. Sometimes it doesn't crash, and the Identities page is just blank. Sometimes the Identities page seems to work after restarting the application. The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #4 0x7f44dc35f4e8 in KCModuleProxy::isChanged() const () at /usr/lib/libKF5KCMUtils.so.5 #5 0x7f44dc63e35e in () at /usr/lib/libkontactprivate.so.5 #6 0x7f44db0d1097 in () at /usr/lib/libQt5Core.so.5 #7 0x7f44da790b69 in KPageDialog::currentPageChanged(KPageWidgetItem*, KPageWidgetItem*) () at /usr/lib/libKF5WidgetsAddons.so.5 #8 0x7f44db0d1097 in () at /usr/lib/libQt5Core.so.5 #9 0x7f44da799489 in KPageWidget::currentPageChanged(KPageWidgetItem*, KPageWidgetItem*) () at /usr/lib/libKF5WidgetsAddons.so.5 #10 0x7f44db0d1097 in () at /usr/lib/libQt5Core.so.5 #11 0x7f44da79930c in KPageView::currentPageChanged(QModelIndex const&, QModelIndex const&) () at /usr/lib/libKF5WidgetsAddons.so.5 #12 0x7f44da79d965 in () at /usr/lib/libKF5WidgetsAddons.so.5 #13 0x7f44db0d1097 in () at /usr/lib/libQt5Core.so.5 #14 0x7f44db0688cc in QItemSelectionModel::selectionChanged(QItemSelection const&, QItemSelection const&) () at /usr/lib/libQt5Core.so.5 #15 0x7f44db06c400 in QItemSelectionModel::emitSelectionChanged(QItemSelection const&, QItemSelection const&) () at /usr/lib/libQt5Core.so.5 #16 0x7f44db06665f in QItemSelectionModel::select(QItemSelection const&, QFlags) () at /usr/lib/libQt5Core.so.5 #17 0x7f44dc059ba5 in QTreeViewPrivate::select(QModelIndex const&, QModelIndex const&, QFlags) () at /usr/lib/libQt5Widgets.so.5 #18 0x7f44dc04dfc2 in QTreeView::setSelection(QRect const&, QFlags) () at /usr/lib/libQt5Widgets.so.5 #19 0x7f44dbfde0f6 in QAbstractItemView::mousePressEvent(QMouseEvent*) () at /usr/lib/libQt5Widgets.so.5 #20 0x7f44dbdaf4e9 in QWidget::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #21 0x7f44dbe5d9d3 in QFrame::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5 #22 0x7f44db099142 in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #23 0x7f44dbd788ef in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #24 0x7f44dbd7ddaf in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #25 0x7f44db09c168 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #26 0x7f44dbd7c0ea in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer&, bool, bool) () at /usr/lib/libQt5Widgets.so.5 #27 0x7f44dbdcce85 in () at /usr/lib/libQt5Widgets.so.5 #28 0x7f44dbdcebd7 in () at /usr/lib/libQt5Widgets.so.5 #29 0x7f44dbd788ff in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #30 0x7f44db09c168 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #31 0x7f44db54194c in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () at /usr/lib/libQt5Gui.so.5 #32 0x7f44db52a6e5 in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () at /usr/lib/libQt5Gui.so.5 #33 0x7f44bc52f5e0 in () at /usr/lib/libQt5XcbQpa.so.5 #34 0x7f44d1d0df69 in () at /usr/lib/libglib-2.0.so.0 #35 0x7f44d1d6c327 in () at
[kdeconnect] [Bug 476475] New: Unable to pair with my PC
https://bugs.kde.org/show_bug.cgi?id=476475 Bug ID: 476475 Summary: Unable to pair with my PC Classification: Applications Product: kdeconnect Version: unspecified Platform: Android OS: Android 12.x Status: REPORTED Severity: critical Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: stemyad...@protonmail.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Install the plasma-desktop on PC 2. Install kde connect 3. Connect both devices on the same network 4. Launch the app OBSERVED RESULT List of available devices is inexplicably empty, both on PC and phone. EXPECTED RESULT Ability to pair both devices. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Mint 21.2 (available in About System) KDE Plasma Version: 5.24.7 KDE Frameworks Version: don't know Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 476124] Some buttons don't highlight when hovered
https://bugs.kde.org/show_bug.cgi?id=476124 Tobias Fella changed: What|Removed |Added Latest Commit||https://invent.kde.org/netw ||ork/neochat/-/commit/7fdb61 ||7b3307f12a601f36ff22eedc44c ||b554f4f Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Tobias Fella --- Git commit 7fdb617b3307f12a601f36ff22eedc44cb554f4f by Tobias Fella. Committed on 02/11/2023 at 18:15. Pushed by tfella into branch 'master'. Port RoundButtons in TimelineView to FloatingButton M +3-2src/qml/TimelineView.qml https://invent.kde.org/network/neochat/-/commit/7fdb617b3307f12a601f36ff22eedc44cb554f4f -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 425627] When Dolphin crashes or is force-quit with Ctrl+Alt+Esc , tabs aren't saved
https://bugs.kde.org/show_bug.cgi?id=425627 --- Comment #8 from Varaskkar --- It's true that the original idea is not efficient, because of writing to the disk continuously. As an alternative, I think the button is a good idea, besides being simple for the user. I agree with the proposal of the other ticket (306257). Something that can load several sessions and maybe give them a name like "Personal" or "Work", where each session has its own tabs, views or previously loaded configuration. It could be something like Activities in KDE, where you can have your own "working environment". -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476477] Plasma crash on initial startup from either startx or XDM
https://bugs.kde.org/show_bug.cgi?id=476477 Bug Janitor Service changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Bug Janitor Service --- Thank you for the bug report! However Plasma 5.24.7 is no longer eligible for support or maintenance from KDE; supported versions are 5.27, and 5.27 or newer. Please upgrade to a supported version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one. If you need support for Plasma 5.24.7, please contact your distribution, who bears the responsibility of providing support for older releases that are no longer supported by KDE. If you can reproduce the issue after upgrading to a supported version, feel free to re-open this bug report. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476383] Panel spacers center applets in free space, instead of in the middle of the panel
https://bugs.kde.org/show_bug.cgi?id=476383 Nate Graham changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476198] Cursor color is inverted in nested kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=476198 --- Comment #1 from Zamundaaa --- Can't reproduce -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476438] crash after login with nvidia 545.29.02
https://bugs.kde.org/show_bug.cgi?id=476438 --- Comment #1 from Adi Stadi --- no more crash with released nvidia 545.29.03 ``` ~ inxi -G Graphics: Device-1: NVIDIA AD102 [GeForce RTX 4090] driver: nvidia v: 535.129.03 Device-2: Microsoft LifeCam HD-3000 driver: snd-usb-audio,uvcvideo type: USB Display: wayland server: X.org v: 1.21.1.9 with: Xwayland v: 23.2.2 compositor: kwin_wayland driver: X: loaded: nvidia unloaded: fbdev,modesetting,vesa gpu: nvidia resolution: 2560x1440 API: OpenGL v: 4.6.0 NVIDIA 535.129.03 renderer: NVIDIA GeForce RTX 4090/PCIe/SSE2 ``` -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476438] crash after login with nvidia 545.29.02
https://bugs.kde.org/show_bug.cgi?id=476438 Adi Stadi changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Adi Stadi --- works with released nvidia driver 545.29.03 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 476383] Panel spacers center applets in free space, instead of in the middle of the panel
https://bugs.kde.org/show_bug.cgi?id=476383 Nate Graham changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/-/commi ||t/09893ea151923979c25f0b85c ||0d2bf83f76772f1 --- Comment #5 from Nate Graham --- Git commit 09893ea151923979c25f0b85c0d2bf83f76772f1 by Nate Graham, on behalf of Alex Čižinský. Committed on 02/11/2023 at 18:52. Pushed by ngraham into branch 'master'. Fix applet centering by spacers Prior to this fix, when using spacers to center an applet in a panel, the applet would be centered in the available space. However, the desired behavior is for the applet to be centered in the middle of the panel, just as it was in Plasma 5.27. The reason of this bug are the API changes in KF6. Prior to this fix, the code would try to call nonexistent properties, resulting in the optimalSize property being NaN. M +2-2applets/panelspacer/package/contents/ui/main.qml https://invent.kde.org/plasma/plasma-workspace/-/commit/09893ea151923979c25f0b85c0d2bf83f76772f1 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 476329] Incoming HTML e-mail believed to be Plain text, unless HTML by default option is on
https://bugs.kde.org/show_bug.cgi?id=476329 --- Comment #3 from Gert Oja --- Created attachment 162829 --> https://bugs.kde.org/attachment.cgi?id=162829=edit The same e-mail with HTML by default enabled -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 476329] Incoming HTML e-mail believed to be Plain text, unless HTML by default option is on
https://bugs.kde.org/show_bug.cgi?id=476329 --- Comment #2 from Gert Oja --- Created attachment 162828 --> https://bugs.kde.org/attachment.cgi?id=162828=edit Example e-mail that should have an HTML notice -- You are receiving this mail because: You are watching all bug changes.
