[kwin] [Bug 487043] Extreme stutters/hangs when using certain desktop effects when "~/.cache" is on slow storage
https://bugs.kde.org/show_bug.cgi?id=487043 Victoria changed: What|Removed |Added CC||vi...@pm.me --- Comment #9 from Victoria --- Can this also be the reason why Plasma can sometimes completely freeze during heavy IO (like downloading a big game on Steam)? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406484] Possibility to use *.cube 3D LUT
https://bugs.kde.org/show_bug.cgi?id=406484 caulier.gil...@gmail.com changed: What|Removed |Added Component|Plugin-Editor-3DLut |Plugin-Editor-GmicQt -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 406484] Possibility to use *.cube 3D LUT
https://bugs.kde.org/show_bug.cgi?id=406484 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com Status|REPORTED|RESOLVED Version Fixed In||8.4.0 Resolution|--- |FIXED --- Comment #1 from caulier.gil...@gmail.com --- digiKam Image Editor GmicQt tool has powerful LUT3D filters which allows to use external lut files. https://i.imgur.com/sFjMXIq.png Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 378392] Implement custom LUT3D tables
https://bugs.kde.org/show_bug.cgi?id=378392 caulier.gil...@gmail.com changed: What|Removed |Added Component|Plugin-Editor-3DLut |Plugin-Editor-GmicQt -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 378392] Implement custom LUT3D tables
https://bugs.kde.org/show_bug.cgi?id=378392 caulier.gil...@gmail.com changed: What|Removed |Added Version Fixed In||8.4.0 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from caulier.gil...@gmail.com --- GmicQt tool for digiKam Image Editor has a very powerful Lut3D customizer and filter: https://i.imgur.com/GEUM4uT.png Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 473163] KGlobalAccel: Let me name descriptions for custom function
https://bugs.kde.org/show_bug.cgi?id=473163 gudvinr+...@gmail.com changed: What|Removed |Added CC||gudvinr+...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 487343] Baloo File Extractor crashed while indexing a mobi file
https://bugs.kde.org/show_bug.cgi?id=487343 --- Comment #4 from tagwer...@innerjoin.org --- ... and that's the one I was looking for 8-] Bug 475975 The Mobi extraction code needs a friend... -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 342513] Add support for fractional radius in blur and unsharp mask filters.
https://bugs.kde.org/show_bug.cgi?id=342513 caulier.gil...@gmail.com changed: What|Removed |Added Summary|Add support for fractional |Add support for fractional |radius in blur and unsharp |radius in blur and unsharp |mask filters [patch]|mask filters. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 342513] Add support for fractional radius in blur and unsharp mask filters [patch]
https://bugs.kde.org/show_bug.cgi?id=342513 caulier.gil...@gmail.com changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Version Fixed In||8.4.0 --- Comment #20 from caulier.gil...@gmail.com --- I considerate this file as obsolete. If you want a more powerful blur/sharpen filters, with more adjustments,considerate to use GmicQt tool available in digiKam image editor https://i.imgur.com/txAhZbR.png Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 487343] Baloo File Extractor crashed while indexing a mobi file
https://bugs.kde.org/show_bug.cgi?id=487343 tagwer...@innerjoin.org changed: What|Removed |Added CC||tagwer...@innerjoin.org --- Comment #3 from tagwer...@innerjoin.org --- Also... ... Bug 475730, Bug 486853 and some history about crash handling in Bug 421317 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 227946] Adding frame in excentric position
https://bugs.kde.org/show_bug.cgi?id=227946 caulier.gil...@gmail.com changed: What|Removed |Added Component|Plugin-Editor-Border|Plugin-Editor-GmicQt -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 227946] Adding frame in excentric position
https://bugs.kde.org/show_bug.cgi?id=227946 caulier.gil...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED Version Fixed In||8.4.0 --- Comment #1 from caulier.gil...@gmail.com --- There are plenty of frame filter in Image Editor GmicQt tool which allows to do it : https://i.imgur.com/lJOF4C7.png Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 484733] Spectable crashes when we record several times a video
https://bugs.kde.org/show_bug.cgi?id=484733
--- Comment #1 from h...@mav.wtf ---
Created attachment 169693
--> https://bugs.kde.org/attachment.cgi?id=169693=edit
New crash information added by DrKonqi
spectacle (23.08.5) using Qt 5.15.12
Tried to start a entire-workspace recording. Appeared to be working fine until
I attempted to stop recording at which point it segfaulted. This is Fedora
Kinoite.
-- Backtrace (Reduced):
#4 0x7f9899d27654 in QQuickView::rootObject() const () from
/lib64/libQt5Quick.so.5
#5 0x557d6077ca06 in ViewerWindow::showInlineMessage(QString const&,
QMap const&) ()
#7 0x7f98988e9151 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
#8 0x557d6079b373 in
QtPrivate::QFunctorSlotObject
const&, bool)::{lambda()#2}, 0, QtPrivate::List<>, void>::impl(int,
QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) ()
#9 0x7f98988e9151 in void doActivate(QObject*, int, void**) () from
/lib64/libQt5Core.so.5
--
You are receiving this mail because:
You are watching all bug changes.
[Spectacle] [Bug 484733] Spectable crashes when we record several times a video
https://bugs.kde.org/show_bug.cgi?id=484733 h...@mav.wtf changed: What|Removed |Added CC||h...@mav.wtf -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482428] Scrolling over time-based comboboxes using a two-finger touchpad scroll malfunctions
https://bugs.kde.org/show_bug.cgi?id=482428 --- Comment #7 from Jakob Petsovits --- I'll note that the "fix" referenced above looks a little different than the suggestion for expected behavior in comment #0. > The time units should range according, like if its more than 59 seconds then > change the units to mins and if more than 59 mins then to hours and so on. I wanted to do this initially, but Qt Quick makes this sort of hard. The SpinBox component has a single field called "stepSize", it affects the value for both going up and going down. Now if I'm at 1 minute, what I would like is to go down by 1 second but up by 1 minute. This can't be done without terrible (and possibly buggy) hacks at the moment, as far as I'm aware. So in the new UI, you get drop-downs with a few preset values instead, and if those preset values aren't what you're looking for, you can configure a custom value with the "Custom..." option. The dialog that presents the custom duration prompt will provide a SpinBox input field like before, but instead of combining value and time unit in the same field, it lets you choose between seconds and minutes through a pair of radio buttons to the right of the input field. This also solves the mentioned issue, though perhaps not in the way that you originally had in mind. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 325844] Add access to watermark tool in Image editor
https://bugs.kde.org/show_bug.cgi?id=325844 caulier.gil...@gmail.com changed: What|Removed |Added Component|Plugin-Editor-InsertText|Plugin-Editor-GmicQt Status|REPORTED|RESOLVED Version Fixed In||8.4.0 Resolution|--- |FIXED --- Comment #1 from caulier.gil...@gmail.com --- The GMicqt Watermark tool is avaialble in ImageEditor instead. https://i.imgur.com/w9mDXdz.png Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482428] Scrolling over time-based comboboxes using a two-finger touchpad scroll malfunctions
https://bugs.kde.org/show_bug.cgi?id=482428 Jakob Petsovits changed: What|Removed |Added Version Fixed In||6.1.0 -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 480157] KStars 3.6.8 missing official tarball
https://bugs.kde.org/show_bug.cgi?id=480157 Jasem Mutlaq changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482853] "When locked, turn off screen" needs a checkbox to disable/enable it
https://bugs.kde.org/show_bug.cgi?id=482853 --- Comment #4 from Jakob Petsovits --- Git commit 511469e52d4676d6c71f66acaaf277a7efc25e1e by Jakob Petsovits. Committed on 22/05/2024 at 04:36. Pushed by jpetso into branch 'master'. kcmodule: Switch to comboboxes for selecting idle timeout values This follows the direction spearheaded by kcm_screenlocker, in plasma/kscreenlocker commit 311db2a9. In addition to a few select preset options, the user can also select a "Custom…" option which presents a duration prompt dialog. Using comboboxes has a few nice UX characteristics: * It allows us to replace the checkbox of some timeout settings with a textual option called "Never", which is easier to grasp. Likewise, "Immediately" is more obvious than "0 sec". * It increases the mouse area available for clicking, which makes the control easier to hit for users with low-precision pointer input devices. * It sidesteps the problem of SpinBox ignoring the defined step size when scrolling with a high-resolution scroll wheel. * By putting the SpinBox into a custom duration prompt dialog, it's more obvious that both seconds and minutes are supported for each setting. Some options also provide second-level presets. The downside is that it now takes three extra clicks to enter and confirm a custom timeout duration. Hopefully our users are comfortable with that trade-off. In order to implement this, the latest versions of the ComboBoxWithCustomValue and DurationPromptDialog components are copied from kcm_screenlocker. Several improvements to these components will be fed back to kcm_screenlocker and hopefully upstreamed to Kirigami (or Kirigami Addons) at a later time. In addition, this commit introduces TimeDurationComboBox, a glue code component combining two aforementioned components, to further reduce the amount of boilerplate required in ProfileConfig.qml. Related: bug 482428 A +164 -0kcmodule/profiles/ui/ComboBoxWithCustomValue.qml [License: LGPL(v2.1+)] A +212 -0kcmodule/profiles/ui/DurationPromptDialog.qml [License: LGPL(v2.1+)] M +264 -104 kcmodule/profiles/ui/ProfileConfig.qml D +0-49 kcmodule/profiles/ui/TimeDelaySpinBox.qml A +151 -0kcmodule/profiles/ui/TimeDurationComboBox.qml [License: LGPL(v2.1+)] https://invent.kde.org/plasma/powerdevil/-/commit/511469e52d4676d6c71f66acaaf277a7efc25e1e -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482428] Scrolling over time-based comboboxes using a two-finger touchpad scroll malfunctions
https://bugs.kde.org/show_bug.cgi?id=482428 Jakob Petsovits changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/powerdevil/-/commit/5114 ||69e52d4676d6c71f66acaaf277a ||7efc25e1e Status|ASSIGNED|RESOLVED --- Comment #6 from Jakob Petsovits --- Git commit 511469e52d4676d6c71f66acaaf277a7efc25e1e by Jakob Petsovits. Committed on 22/05/2024 at 04:36. Pushed by jpetso into branch 'master'. kcmodule: Switch to comboboxes for selecting idle timeout values This follows the direction spearheaded by kcm_screenlocker, in plasma/kscreenlocker commit 311db2a9. In addition to a few select preset options, the user can also select a "Custom…" option which presents a duration prompt dialog. Using comboboxes has a few nice UX characteristics: * It allows us to replace the checkbox of some timeout settings with a textual option called "Never", which is easier to grasp. Likewise, "Immediately" is more obvious than "0 sec". * It increases the mouse area available for clicking, which makes the control easier to hit for users with low-precision pointer input devices. * It sidesteps the problem of SpinBox ignoring the defined step size when scrolling with a high-resolution scroll wheel. * By putting the SpinBox into a custom duration prompt dialog, it's more obvious that both seconds and minutes are supported for each setting. Some options also provide second-level presets. The downside is that it now takes three extra clicks to enter and confirm a custom timeout duration. Hopefully our users are comfortable with that trade-off. In order to implement this, the latest versions of the ComboBoxWithCustomValue and DurationPromptDialog components are copied from kcm_screenlocker. Several improvements to these components will be fed back to kcm_screenlocker and hopefully upstreamed to Kirigami (or Kirigami Addons) at a later time. In addition, this commit introduces TimeDurationComboBox, a glue code component combining two aforementioned components, to further reduce the amount of boilerplate required in ProfileConfig.qml. Related: bug 482853 A +164 -0kcmodule/profiles/ui/ComboBoxWithCustomValue.qml [License: LGPL(v2.1+)] A +212 -0kcmodule/profiles/ui/DurationPromptDialog.qml [License: LGPL(v2.1+)] M +264 -104 kcmodule/profiles/ui/ProfileConfig.qml D +0-49 kcmodule/profiles/ui/TimeDelaySpinBox.qml A +151 -0kcmodule/profiles/ui/TimeDurationComboBox.qml [License: LGPL(v2.1+)] https://invent.kde.org/plasma/powerdevil/-/commit/511469e52d4676d6c71f66acaaf277a7efc25e1e -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 461541] Add new plugin to integrate GFPGAN for face restoration.
https://bugs.kde.org/show_bug.cgi?id=461541 --- Comment #1 from caulier.gil...@gmail.com --- GFPGAN is a Python code project. digiKam is C++ one. So, it's complex to integrate. Instead, i recommend to take a look to GMicQt Repair filters which give great results. GmiQt is available in Image Editor and will be integrated soon in digiKam Batch Queue Manager. https://i.imgur.com/9UAggJf.png Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 440434] Wish: Data analysis tools for determining travel patterns of wildlife with Trail Cameras
https://bugs.kde.org/show_bug.cgi?id=440434 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- For the feature "ability to detect and identify animals.", since digiKam 8.3.0, we have a new tool using AI to analysis and detect subjects in photo. This includes the animals. The tool generate keywords automatically. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 338779] Add new tool to embed hidden watermarking (based on wavelets or Fourier transforms)
https://bugs.kde.org/show_bug.cgi?id=338779 caulier.gil...@gmail.com changed: What|Removed |Added Component|Plugin-Bqm-WaterMark|Plugin-Bqm-WishForNewTools -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 442379] When using Natural Scrolling, scrolling direction to change volume is inverted
https://bugs.kde.org/show_bug.cgi?id=442379 --- Comment #13 from Hector Martin --- > I find the new behaviour quite unnatural after using it the way it was for so > long. That sounds like "I got used to the old way even though it didn't make sense", which isn't a terribly good reason not to fix it. :) > Also since the sliders are perpendicular to the direction of motion, I don't > believe there really is a "correct" way for them to respond. Other systems > have likely preferred to keep their audio sliders vertical for this same > reason. If you're implying that for a vertical volume slider then "scroll up" on a trackpad should in fact be volume up (i.e. the current behavior after this bug was fixed) *then* it stands to reason that the same should be true for a horizontal slider as, despite there being no "correct" spatial mapping due to the axis being different, the "volume up" metaphor still holds. Indeed, this same rationale applies to non-spatial cases like the Plasma system tray volume icon itself, which simply displays a varying number of "waves". In general, non-scrollbar linear widgets on desktop environments (and, indeed, largely so in the physical world) have always used the "positive right / up" convention, so it stands to reason that they would be mapped this way. That said, I just noticed that horizontal sliders and indeed the tray icon itself *also* respond to horizontal trackpad movement, which is also excellent as it matches the direction of the slider. As I said in my earlier comment, the only reason we ended up in this mess to begin with is because scroll wheels were *specifically* intended for the use case of viewport scrolling first (which is inverted vs. the content), then widgets have always tried to use "natural scrolling" by inverting the scroll direction at the widget level, and then finally "natural scrolling" for trackpads was originally implemented as a hack that inverted all scrolling regardless of scroll target, making the widgets move backwards unintentionally. People might have gotten used to that, but I really doubt there is a strong argument to be made that this behavior is, in any way, intuitive. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 487303] plasma-brower-integration causes Cloudflare to lock out humans
https://bugs.kde.org/show_bug.cgi?id=487303 Steve Zhu changed: What|Removed |Added CC||steve.ziyao...@icloud.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486504] Primary display changes to 640x480 resolution after suspend (wayland only)
https://bugs.kde.org/show_bug.cgi?id=486504 --- Comment #15 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 485668] Discover freezes on opening
https://bugs.kde.org/show_bug.cgi?id=485668 --- 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.
[plasmashell] [Bug 485966] Implement freedesktop wallpaper API
https://bugs.kde.org/show_bug.cgi?id=485966 --- 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.
[kwin] [Bug 484210] kwin_kill_helper not responding
https://bugs.kde.org/show_bug.cgi?id=484210 --- 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.
[Discover] [Bug 378568] Annoying (and seemingly unnecessary) KWallet popup on start
https://bugs.kde.org/show_bug.cgi?id=378568 --- 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.
[Discover] [Bug 472589] DIscover crashes with memory corruption
https://bugs.kde.org/show_bug.cgi?id=472589 --- 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.
[frameworks-kwallet] [Bug 487348] New: Secret Portal fails to store secret for Flatpak applications
https://bugs.kde.org/show_bug.cgi?id=487348 Bug ID: 487348 Summary: Secret Portal fails to store secret for Flatpak applications Classification: Frameworks and Libraries Product: frameworks-kwallet Version: 6.2.0 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: va...@kde.org Reporter: s...@datagirl.xyz CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY When using the KWallet XDG Secrets Portal implementation with Flatpak packages, the generated secret never gets stored back to the wallet. STEPS TO REPRODUCE 1. With KWallet running and the main wallet open, run a Flatpak that uses the XDG Secret Portal. 2. Trigger the application to look for secrets (e.g., try to open an encrypted vault). 3. If the application caches its secret, restart the application and try the operation again. OBSERVED RESULT Applications will successfully create secrets, but be unable to read them back. In the case of the repro program I wrote (see "Additional Information"), output similar to the following is given: 2024-05-22T03:04:18.100605Z INFO kwallet_secretportal_repro: Attempt #1 2024-05-22T03:04:18.103380Z INFO kwallet_secretportal_repro: Secret CRC: b9446548 2024-05-22T03:04:18.103399Z INFO kwallet_secretportal_repro: Attempt #2 2024-05-22T03:04:18.112340Z INFO kwallet_secretportal_repro: Secret CRC: cf16a0a8 2024-05-22T03:04:18.112356Z ERROR kwallet_secretportal_repro: Secrets don't match (old CRC: b9446548, new CRC: cf16a0a8) After a couple attempts, KWallet shows a message box saying: "There have been repeated failed attempts to gain access to a wallet. An application may be misbehaving." EXPECTED RESULT The secret provided from KWallet is the same every time, so applications can decrypt secrets they stored. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Gentoo Linux 2.15 (Kernel 6.6.30-gentoo-dist) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION To help reproduce this error, I've built a small test program (https://invent.kde.org/flurry/secretportalrepro). For a real-world example, I originally saw this when trying to use Pika Backup (https://flathub.org/apps/org.gnome.World.PikaBackup). Note that this error does not occur when interacting with the Secret Portal outside of a Flatpak. For example, using the same test program in a shell with `cargo run`: $ cargo run Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.07s Running `target/debug/kwallet-secretportal-repro` 2024-05-22T03:05:20.027170Z INFO kwallet_secretportal_repro: Attempt #1 2024-05-22T03:05:20.030658Z INFO kwallet_secretportal_repro: Secret CRC: becbc17e 2024-05-22T03:05:20.030685Z INFO kwallet_secretportal_repro: Attempt #2 2024-05-22T03:05:20.033057Z INFO kwallet_secretportal_repro: Secret CRC: becbc17e 2024-05-22T03:05:20.033081Z INFO kwallet_secretportal_repro: Attempt #3 2024-05-22T03:05:20.034901Z INFO kwallet_secretportal_repro: Secret CRC: becbc17e -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 487347] New: Update failed with no output
https://bugs.kde.org/show_bug.cgi?id=487347 Bug ID: 487347 Summary: Update failed with no output Classification: I don't know Product: kde Version: unspecified Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: filex.st...@proton.me Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY When trying to upgrade to the newly released Kubuntu 24, a window "Update Failed - KDE Daemon" (kded5) pops up, showing "Upgrade failed with the following output:" and an empty box. STEPS TO REPRODUCE 1. Click on upgrade 2. See the window after a short interval OBSERVED RESULT A window with no output. EXPECTED RESULT A window telling you what to do SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 23.10 / Linux 6.5.0-35-generic (64-bit) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION This bug seems to be known since at least Kubuntu 22 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487043] Extreme stutters/hangs when using certain desktop effects when "~/.cache" is on slow storage
https://bugs.kde.org/show_bug.cgi?id=487043 --- Comment #8 from Brodie Robertson --- (In reply to Mithras from comment #5) > Is it throughout whole .cache folder or a specific subfolder? Any chance I > can mount tmpfs for these animation only? The folder at fault is .cache/kwin/qmlcache from what I can tell, at least from early testing putting this on a tmpfs seems to not cause additional issues. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487043] Extreme stutters/hangs when using certain desktop effects when "~/.cache" is on slow storage
https://bugs.kde.org/show_bug.cgi?id=487043 --- Comment #7 from Brodie Robertson --- Additionally Plasma seems to be the only software that is this negatively effected by the cache existing on a hard drive, GNOME, Hyprland and other desktops do not seem to exhibit similar issues. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487043] Extreme stutters/hangs when using certain desktop effects when "~/.cache" is on slow storage
https://bugs.kde.org/show_bug.cgi?id=487043 Brodie Robertson changed: What|Removed |Added CC||brodierobertson54321@gmail. ||com --- Comment #6 from Brodie Robertson --- (In reply to Nate Graham from comment #4) > This is probably an issue we should fix for the benefit of people with a > single slow storage disk, but I have to ask... if you're a technical expert > and have multiple options for storage hardware options, would it mot make > more sense to put the cache on your fastest one, rather than a known slow > one? In my case I have my boot and application data on my NVME drive as this has the most noticeable effect on system speeds, but my home directory is on my bulk storage hard drive. SSDs are much cheaper now and on my next upgrade I will probably make the swap but even if I do move to something faster it doesn't change the issue that Kwin is constantly adding wear to the drive with little pings every time a desktop effect is used. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 487346] New: Feature Request: Speak beginning from current page
https://bugs.kde.org/show_bug.cgi?id=487346 Bug ID: 487346 Summary: Feature Request: Speak beginning from current page Classification: Applications Product: okular Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: alphabitser...@pm.me Target Milestone: --- SUMMARY Currently, Okular has the following options for text-to-speech as far as I'm aware: - Tools → Speak Whole Document - Tools → Speak Current Page - Select a text block → Right-click context menu → "Speak Text" I'm requesting the inclusion of an additional option to the Tools menu, which would be functionally identical to "Speak Whole Document" except that it begins speech from the current page, as opposed to page 1 of the document. One use case for this feature is in resuming the reading of long texts. I have several books which are hundreds of pages long, which I normally read in multiple sessions. When I come back to a book, currently I need to either select Speak Current Page for each new page of the book, or I need to select the text from the beginning of where I'm starting some end point several pages later. Another use case is for skipping e.g. table of contents, copyright/publisher info, etc. which are sometimes located at the beginning of a book. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 487317] Inaccurate TL sign (₺) display
https://bugs.kde.org/show_bug.cgi?id=487317 Jack changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Jack --- What version, exactly? Either do "kmymoney --version" at command line, or Help/About KMyMoney menu item. Did it work previously? Can you say with which version? What locale do you have set? Does it work correctly in other applications? For example Libreoffice and Calligra. That might show if it is a general problem on your installation, KDE specific, or just KMyMoney. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469247] Show OSD feedback when switching webcam on and off
https://bugs.kde.org/show_bug.cgi?id=469247 Fabian Arndt changed: What|Removed |Added CC||fabian.ar...@root-core.net -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 442379] When using Natural Scrolling, scrolling direction to change volume is inverted
https://bugs.kde.org/show_bug.cgi?id=442379 Sollace changed: What|Removed |Added CC||solla...@gmail.com --- Comment #12 from Sollace --- (In reply to Adam Fontenot from comment #10) > I want to add that I strongly agree with @paul, above, that it is the *new* > behavior that is unexpected and unintuitive. > > I argue that most users who select "natural" or reversed scrolling on a > touchpad want reversed scrolling everywhere, not to have their settings > second guessed by KDE and overridden on desktop applets (but seemingly > nowhere else). > > This seemed so obvious to me that I filed a bug about the new behavior: > https://bugs.kde.org/show_bug.cgi?id=478146 > > I'd really like to see this reconsidered or at least an option to turn it > off and respect the reversed-scrolling setting. I think the decision to > change this happened too quickly, probably without much input from users who > use natural scrolling regularly. +1 On adding a "natural slider adjustment" option. I find the new behaviour quite unnatural after using it the way it was for so long. Also since the sliders are perpendicular to the direction of motion, I don't believe there really is a "correct" way for them to respond. Other systems have likely preferred to keep their audio sliders vertical for this same reason. Having separate natural scrolling toggles for content and UI elements seems the most sensible solution. -- You are receiving this mail because: You are watching all bug changes.
[Marknote] [Bug 487345] Dark mode for Marknote in non-Plasma desktop environments
https://bugs.kde.org/show_bug.cgi?id=487345 318...@gmail.com changed: What|Removed |Added Version|1.1.1 |1.2.1 -- You are receiving this mail because: You are watching all bug changes.
[Marknote] [Bug 487345] New: Dark mode for Marknote in non-Plasma desktop environments
https://bugs.kde.org/show_bug.cgi?id=487345 Bug ID: 487345 Summary: Dark mode for Marknote in non-Plasma desktop environments Classification: Applications Product: Marknote Version: 1.1.1 Platform: Flatpak OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@kaidan.im Reporter: 318...@gmail.com CC: c...@carlschwan.eu, m...@kaidan.im Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** When running the Marknote Flatpak on Linux Mint 21.3 Cinnamon, the application uses light colors and there is no way to set it to dark mode. STEPS TO REPRODUCE 1. Set your desktop to a dark color theme. 2. Open Marknote 3. Observe that Marknote uses a white background and black text. 4. Attempt to change the color scheme of Marknote to dark mode. OBSERVED RESULT There is no way to get Marknote to use dark mode. EXPECTED RESULT There should be a dark mode for accessibility. SOFTWARE/OS VERSIONS Windows: macOS: Linux: Mint 21.3 Cinnamon KDE Plasma Version: KDE Frameworks Version: 6.2.1 Qt Version: 6.6.3 ADDITIONAL INFORMATION flatpak --version 1.12.7 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487344] New: Memory Usage widget in Task Manager crashes plasmashell on Fedora Asahi Remix 40
https://bugs.kde.org/show_bug.cgi?id=487344 Bug ID: 487344 Summary: Memory Usage widget in Task Manager crashes plasmashell on Fedora Asahi Remix 40 Classification: Plasma Product: plasmashell Version: 6.0.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: dylanchap...@rocketmail.com CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 Created attachment 169692 --> https://bugs.kde.org/attachment.cgi?id=169692=edit Screen recording of the steps to reproduce the problem. Performed under a new user account. SUMMARY On a Fedora Asahi Remix 40 machine (Apple ARM computers), if the Memory Usage widget is added to Task Manager and selected, plasmashell crashes continuously. STEPS TO REPRODUCE 1. Right click on Task Manager 2. Click Add Widgets... 3. Add Memory Usage 4. Click on the new Memory Usage widget OBSERVED RESULT plasmashell crashes, attempts to restart, and crashes again continuously until the widget definition is removed from ~/.config/plasma-org.kde.plasma.desktop-appletsrc . EXPECTED RESULT The widget opens and displays more information. SOFTWARE/OS VERSIONS Operating System: Fedora Linux Asahi Remix 40 KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.8.9-404.asahi.fc40.aarch64+16k (64-bit) Graphics Platform: Wayland Processors: 4 × Apple Firestorm (M1), 4 × Apple Icestorm (M1) Memory: 15.1 GiB of RAM Graphics Processor: Apple M1 Product Name: Apple MacBook Air (M1, 2020) ADDITIONAL INFORMATION The problem did not occur on an x86 Fedora 40 virtual machine. Here is my bug report to Fedora Asahi Remix. I was told to report it here as they do not modify the KDE stack from what Fedora provides. https://pagure.io/fedora-asahi/remix-bugs/issue/8 BACKTRACE Already logging to plasmashell-4-00.txt. Continuing. [Thread 0xfffecf2eada0 (LWP 27629) exited] [Thread 0xfffecfb7eda0 (LWP 27628) exited] [Detaching after fork from child process 30017] [New Thread 0xfffecfb7eda0 (LWP 30040)] [New Thread 0xfffecf2eada0 (LWP 30041)] [New Thread 0x4484eda0 (LWP 30042)] [New Thread 0x6bffeda0 (LWP 30043)] [New Thread 0x515dada0 (LWP 30050)] [New Thread 0x5096eda0 (LWP 30051)] [New Thread 0x47ffeda0 (LWP 30052)] Downloading separate debug info for /lib64/libKF6NewStuffWidgets.so.6 [New Thread 0x3fffeda0 (LWP 30392)] [New Thread 0xfffef49beda0 (LWP 30395)] [New Thread 0xfffee37eeda0 (LWP 30396)] Thread 1 "plasmashell" received signal SIGABRT, Aborted. __pthread_kill_implementation (threadid=281473355993504, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 Downloading source file /usr/src/debug/glibc-2.39-13.fc40.aarch64/nptl/pthread_kill.c 44return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0; Thread 37 (Thread 0xfffee37eeda0 (LWP 30396) "QSGRenderThread"): #0 0x9c0d290c in __futex_abstimed_wait_common64 (private=0, futex_word=0xaaab5904150c, expected=0, op=393, abstime=0x0, cancel=true) at futex-internal.c:57 #1 __futex_abstimed_wait_common (futex_word=0xaaab5904150c, expected=0, clockid=0, abstime=0x0, private=0, cancel=true) at futex-internal.c:87 #2 __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0xaaab5904150c, expected=expected@entry=0, clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=private@entry=0) at futex-internal.c:139 #3 0x9c0d5974 [PAC] in __pthread_cond_wait_common (cond=0xaaab590414e0, mutex=0xaaab590414b0, clockid=0, abstime=0x0) at pthread_cond_wait.c:503 #4 ___pthread_cond_wait (cond=0xaaab590414e0, mutex=0xaaab590414b0) at pthread_cond_wait.c:618 #5 0x9c7e6194 [PAC] in QWaitConditionPrivate::wait (this=0xaaab590414b0, deadline=...) at /usr/src/debug/qt6-qtbase-6.7.0-5.fc40.aarch64/src/corelib/thread/qwaitcondition_unix.cpp:102 #6 QWaitCondition::wait (this=this@entry=0xaaab590413d0, mutex=mutex@entry=0xaaab590413c8, deadline=...) at /usr/src/debug/qt6-qtbase-6.7.0-5.fc40.aarch64/src/corelib/thread/qwaitcondition_unix.cpp:180 #7 0x9e5fe144 [PAC] in QSGRenderThreadEventQueue::takeEvent (this=0xaaab590413b0, wait=true) at /usr/include/qt6/QtCore/qdeadlinetimer.h:31 #8 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0xaaab59041310) at /usr/src/debug/qt6-qtdeclarative-6.7.0-2.fc40.aarch64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:868 #9 0x9e5fe488 [PAC] in QSGRenderThread::run (this=0xaaab59041310) at /usr/src/debug/qt6-qtdeclarative-6.7.0-2.fc40.aarch64/src/quick/scenegraph/qsgthreadedrenderloop.cpp:991 #10 0x9c7d7db4 [PAC] in operator() (__closure=) at /usr/src/debug/qt6-qtbase-6.7.0-5.fc40.aarch64/src/corelib/thread/qthread_unix.cpp:326 #11 (anonymous namespace)::terminate_on_exception > (t=)
[frameworks-baloo] [Bug 487343] Baloo File Extractor crashed while indexing a mobi file
https://bugs.kde.org/show_bug.cgi?id=487343 --- Comment #2 from Victor Oliver --- Created attachment 169691 --> https://bugs.kde.org/attachment.cgi?id=169691=edit baloofilerc -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 487343] Baloo File Extractor crashed while indexing a mobi file
https://bugs.kde.org/show_bug.cgi?id=487343 --- Comment #1 from Victor Oliver --- Created attachment 169690 --> https://bugs.kde.org/attachment.cgi?id=169690=edit Output of `balooctl monitor` -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 487343] New: Baloo File Extractor crashed while indexing a mobi file
https://bugs.kde.org/show_bug.cgi?id=487343 Bug ID: 487343 Summary: Baloo File Extractor crashed while indexing a mobi file Classification: Frameworks and Libraries Product: frameworks-baloo Version: 6.1.0 Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: victor_su...@hotmail.com Target Milestone: --- Application: baloo_file_extractor (6.1.0) Qt Version: 6.7.0 Frameworks Version: 6.1.0 Operating System: Linux 6.5.0-35-generic x86_64 Windowing System: Wayland Distribution: KDE neon 6.0 DrKonqi: 6.0.4 [KCrashBackend] -- Information about the crash: Baloo File Extractor crashed while indexing files in the background. The crash always happens when reaching a mobi file. Purging the index and restarting baloo will lead to the same results after a while, as soon as it hits the same file. Hiding the offeding mobi file allows baloo to progress further, however it will still crash on the next mobi file it finds. The crash can be reproduced every time. -- Backtrace: Application: Baloo File Extractor (baloo_file_extractor), signal: Segmentation fault [KCrash Handler] #4 QArrayDataPointer::QArrayDataPointer (other=..., this=, this=, other=...) at ./src/corelib/tools/qarraydatapointer.h:37 #5 QString::QString (other=..., this=, this=, other=...) at ./src/corelib/text/qstring.h:1186 #6 QVariant::Private::Private (t=..., this=0x7ffecd082250) at ./src/corelib/kernel/qvariant_p.h:98 #7 QVariant::QVariant (this=, val=..., this=, val=...) at ./src/corelib/kernel/qvariant.cpp:948 #8 0x7fd52299550a in standardDeclarationForNode (node=...) at ./src/corelib/tools/qlist.h:183 #9 0x7fd522954d20 in QTextHtmlParser::declarationsForNode (node=1811, this=0x7ffecd082510) at ./src/gui/text/qtexthtmlparser.cpp:2141 #10 QTextHtmlParser::parseTag (this=) at ./src/gui/text/qtexthtmlparser.cpp:676 #11 QTextHtmlParser::parse (this=) at ./src/gui/text/qtexthtmlparser.cpp:606 #12 QTextHtmlParser::parse (_resourceProvider=, text=..., this=) at ./src/gui/text/qtexthtmlparser.cpp:549 #13 QTextHtmlImporter::QTextHtmlImporter (this=, _doc=, _html=..., mode=, resourceProvider=, this=, _doc=, _html=..., mode=, resourceProvider=) at ./src/gui/text/qtextdocumentfragment.cpp:456 #14 0x7fd52293ca8d in QTextDocument::setHtml (this=0x7ffecd082690, html=...) at ./src/gui/text/qtextdocument.cpp:1301 #15 0x7fd51f382116 in KFileMetaData::MobiExtractor::extract (this=, result=0x7ffecd082b00) at ./src/extractors/mobiextractor.cpp:96 #16 0x60bae6536120 in Baloo::App::index (this=0x7ffecd083280, tr=0x60bae84ad030, url=..., id=386785227105192397) at ./src/file/extractor/app.cpp:180 #17 0x60bae65373ee in Baloo::App::processNextFile (this=0x7ffecd083280) at /usr/include/c++/11/bits/unique_ptr.h:173 #18 0x7fd5239fa272 in QObject::event (this=0x7ffecd083280, e=0x60bae87bafa0) at ./src/corelib/kernel/qobject.cpp:1446 #19 0x7fd523aa1c13 in doNotify (event=, receiver=) at ./src/corelib/kernel/qcoreapplication.cpp:1235 #20 QCoreApplication::notify (event=, receiver=, this=) at ./src/corelib/kernel/qcoreapplication.cpp:1218 #21 QCoreApplication::notifyInternal2 (receiver=0x7ffecd083280, event=event@entry=0x60bae87bafa0) at ./src/corelib/kernel/qcoreapplication.cpp:1134 #22 0x7fd523aa1c7d in QCoreApplication::sendEvent (receiver=, event=event@entry=0x60bae87bafa0) at ./src/corelib/kernel/qcoreapplication.cpp:1575 #23 0x7fd523aa23e0 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x60bae8496e60) at ./src/corelib/kernel/qcoreapplication.cpp:1932 #24 0x7fd523878277 in postEventSourceDispatch (s=0x60bae849dd50) at ./src/corelib/kernel/qeventdispatcher_glib.cpp:244 #25 0x7fd521d20d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7fd521d762b8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7fd521d1e3e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x7fd523876570 in QEventDispatcherGlib::processEvents (this=0x60bae849b0b0, flags=...) at ./src/corelib/kernel/qeventdispatcher_glib.cpp:394 #29 0x7fd523aa3e3b in QEventLoop::exec (this=this@entry=0x7ffecd083190, flags=..., flags@entry=...) at ./src/corelib/global/qflags.h:34 #30 0x7fd523aa5a6c in QCoreApplication::exec () at ./src/corelib/global/qflags.h:74 #31 0x60bae652bc8a in main (argc=, argv=) at ./src/file/extractor/main.cpp:33 [Inferior 1 (process 1007477) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487043] Extreme stutters/hangs when using certain desktop effects when "~/.cache" is on slow storage
https://bugs.kde.org/show_bug.cgi?id=487043 mithras@gmail.com changed: What|Removed |Added CC||mithras@gmail.com --- Comment #5 from mithras@gmail.com --- Is it throughout whole .cache folder or a specific subfolder? Any chance I can mount tmpfs for these animation only? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 486391] QMplay2 crashes when using Vaapi on Wayland
https://bugs.kde.org/show_bug.cgi?id=486391 Zamundaaa changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/kwin/-/commit/0f41239515 ||99cfdc99b53cde6911990158151 ||293 --- Comment #6 from Zamundaaa --- Git commit 0f4123951599cfdc99b53cde6911990158151293 by Xaver Hugl. Committed on 21/05/2024 at 22:26. Pushed by zamundaaa into branch 'master'. waylandserver: set render backend for linuxdrmsyncobj directly The code would previously never set the render backend, causing the use of explicit sync to fail M +0-4src/platformsupport/scenes/opengl/abstract_egl_backend.cpp M +4-0src/wayland_server.cpp https://invent.kde.org/plasma/kwin/-/commit/0f4123951599cfdc99b53cde6911990158151293 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487043] Extreme stutters/hangs when using certain desktop effects when "~/.cache" is on slow storage
https://bugs.kde.org/show_bug.cgi?id=487043 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #4 from Nate Graham --- This is probably an issue we should fix for the benefit of people with a single slow storage disk, but I have to ask... if you're a technical expert and have multiple options for storage hardware options, would it mot make more sense to put the cache on your fastest one, rather than a known slow one? -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 487342] New: Capture Module under file settings cannot change directory
https://bugs.kde.org/show_bug.cgi?id=487342 Bug ID: 487342 Summary: Capture Module under file settings cannot change directory Classification: Applications Product: kstars Version: 3.7.0 Platform: Other OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mutla...@ikarustech.com Reporter: dennisjcoll...@gmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY When selecting the folder button next to the Directory field under File Settings in the Capture Module nothing happens. A spinning color wheel appears indicating it is attempting the operation but it eventually just times out and nothing happens. STEPS TO REPRODUCE 1. goto capture module 2. select folder icon to change directory under file settings 3. nothing happens OBSERVED RESULT Spinning colored wheel and eventually times out EXPECTED RESULT window appear to change directory where images will be saved to SOFTWARE/OS VERSIONS Windows: macOS: version 14.4.1 Sonoma 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.
[kdeplasma-addons] [Bug 487341] New: The entire Appearance tab is non functional if used as a desktop applet
https://bugs.kde.org/show_bug.cgi?id=487341 Bug ID: 487341 Summary: The entire Appearance tab is non functional if used as a desktop applet Classification: Plasma Product: kdeplasma-addons Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Weather Assignee: plasma-b...@kde.org Reporter: jus...@kde.org Target Milestone: --- Not sure if it's possible to detect how the applet is being used, on a panel or on the desktop. But the entire Appearance tab only affects the applet when it's on a panel and is irrelevant when used on the desktop. -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 349675] Commands such as /fortune do not send messages
https://bugs.kde.org/show_bug.cgi?id=349675 argonel changed: What|Removed |Added Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw |ork/konversation/-/commit/a |ork/konversation/-/commit/9 |941c4fd4faf45cb8a9bdda1b13f |f0a87cbc0376bb188076c9c23c0 |bc035cad4335|9e337754e9ce --- Comment #6 from argonel --- Git commit 9f0a87cbc0376bb188076c9c23c09e337754e9ce by Eli MacKenzie. Committed on 21/05/2024 at 23:49. Pushed by argonel into branch 'release/24.05'. Provide scripts with an env var to find qdbus While the qdbus tool has been a RUNTIME dependency of Konversation since 2008, most distros didn't add a requirement. Given there's no standard way to advertise runtime deps, qdbus is now a build dep in addition to being a runtime dep. Unfortunately qdbus doesn't have a consistent name nor location. This attempts to find it by asking Qt where the binaries probably got installed and then tries a few possible names. A script run from inside Konversation now expects to receive an environment variable "KONVERSATION_DBUS_BIN" that is the full pathname of the actual program. This is set by the script launcher if it isn't present in the environment on launch. FIXED-IN: 1.10.24020 M +11 -0CMakeLists.txt M +1-0ChangeLog M +2-0NEWS M +5-4data/scripting_support/python/konversation/dbus.py M +2-2data/scripting_support/python/konversation/i18n.py M +2-1data/scripts/fortune M +2-2data/scripts/gauge M +3-2data/scripts/media M +1-1data/scripts/sayclip M +2-2data/scripts/tinyurl M +7-5data/scripts/uptime M +13 -0src/CMakeLists.txt A +1-0src/konvi_qdbus.h.in M +3-0src/scriptlauncher.cpp https://invent.kde.org/network/konversation/-/commit/9f0a87cbc0376bb188076c9c23c09e337754e9ce -- You are receiving this mail because: You are watching all bug changes.
[konversation] [Bug 349675] Commands such as /fortune do not send messages
https://bugs.kde.org/show_bug.cgi?id=349675 argonel changed: What|Removed |Added Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw |ork/konversation/-/commit/b |ork/konversation/-/commit/a |7a551d6fd07c901d81b25f46f07 |941c4fd4faf45cb8a9bdda1b13f |82a9846c7c23|bc035cad4335 --- Comment #5 from argonel --- Git commit a941c4fd4faf45cb8a9bdda1b13fbc035cad4335 by Eli MacKenzie. Committed on 21/05/2024 at 23:50. Pushed by argonel into branch 'master'. Provide scripts with an env var to find qdbus While the qdbus tool has been a RUNTIME dependency of Konversation since 2008, most distros didn't add a requirement. Given there's no standard way to advertise runtime deps, qdbus is now a build dep in addition to being a runtime dep. Unfortunately qdbus doesn't have a consistent name nor location. This attempts to find it by asking Qt where the binaries probably got installed and then tries a few possible names. A script run from inside Konversation now expects to receive an environment variable "KONVERSATION_DBUS_BIN" that is the full pathname of the actual program. This is set by the script launcher if it isn't present in the environment on launch. FIXED-IN: 1.10.24020 M +11 -0CMakeLists.txt M +1-0ChangeLog M +2-0NEWS M +5-4data/scripting_support/python/konversation/dbus.py M +2-2data/scripting_support/python/konversation/i18n.py M +2-1data/scripts/fortune M +2-2data/scripts/gauge M +3-2data/scripts/media M +1-1data/scripts/sayclip M +2-2data/scripts/tinyurl M +7-5data/scripts/uptime M +13 -0src/CMakeLists.txt A +1-0src/konvi_qdbus.h.in M +3-0src/scriptlauncher.cpp https://invent.kde.org/network/konversation/-/commit/a941c4fd4faf45cb8a9bdda1b13fbc035cad4335 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 479891] Some text glyphs in QML software are mis-aligned or squished when using a fractional scale factor
https://bugs.kde.org/show_bug.cgi?id=479891 Kelvie Wong changed: What|Removed |Added CC||kel...@kelvie.ca -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 484860] Crash during add new l2tp connection
https://bugs.kde.org/show_bug.cgi?id=484860 --- Comment #3 from Yury Zhuravlev --- Why is it a duplicate? My ticket was made `2024-04-01`, but ticket 487135 was created 2024-05-17. 487135 is a duplicate of my ticket. ) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487058] plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=487058 --- Comment #4 from Dylan --- (In reply to Dylan from comment #3) > I just installed some updates, and this issue seems to be gone. I'm not sure > exactly what package upgrade fixed it though... Never mind, the issue still persists. It happened again after another reboot. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480925] Crash in KeyboardInterface::sendKey
https://bugs.kde.org/show_bug.cgi?id=480925 --- Comment #9 from Ryan Rix --- I'm sorry, I should have added that as an attachment or filtered the output. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 480925] Crash in KeyboardInterface::sendKey
https://bugs.kde.org/show_bug.cgi?id=480925 --- Comment #8 from Ryan Rix --- This crash has been happening to me multiple times a day some days for about three months now. does anyone have any advice to root-cause and debug this? I am prepared to patch and compile kwayland and kwin_wayland at least from source, and can decently printf debug, but don't really know much about how wayland works to really have a conceptual understanding of what is happening on this codepath. But it happens most regularly when i press ctrl-backspace, which i do in both of my primary applications emacs and firefox, as a muscle memory. It happened while I was drafting this comment. [rrix@virtuous-cassette:~]$ sudo coredumpctl list | grep kwin_wayland [sudo] password for rrix: Mon 2024-04-15 20:09:01 PDT5657 1000 1000 SIGSEGV missing /nix/store/8hwpp6dgndnihkg2gbwkvqllv3hjsg8y-kwin-5.27.10/bin/.kwin_wayland-wrapped - Mon 2024-04-15 22:31:34 PDT 393757 1000 1000 SIGSEGV missing /nix/store/8hwpp6dgndnihkg2gbwkvqllv3hjsg8y-kwin-5.27.10/bin/.kwin_wayland-wrapped - Tue 2024-04-16 09:42:25 PDT 410080 1000 1000 SIGSEGV missing /nix/store/8hwpp6dgndnihkg2gbwkvqllv3hjsg8y-kwin-5.27.10/bin/.kwin_wayland-wrapped - Fri 2024-04-19 17:57:46 PDT 461114 1000 1000 SIGSEGV missing /nix/store/8hwpp6dgndnihkg2gbwkvqllv3hjsg8y-kwin-5.27.10/bin/.kwin_wayland-wrapped - Mon 2024-04-22 17:06:28 PDT5764 1000 1000 SIGSEGV missing /nix/store/8hwpp6dgndnihkg2gbwkvqllv3hjsg8y-kwin-5.27.10/bin/.kwin_wayland-wrapped - Tue 2024-04-23 09:57:43 PDT 185495 1000 1000 SIGSEGV missing /nix/store/8hwpp6dgndnihkg2gbwkvqllv3hjsg8y-kwin-5.27.10/bin/.kwin_wayland-wrapped - Sat 2024-04-27 11:35:21 PDT 273848 1000 1000 SIGSEGV missing /nix/store/8hwpp6dgndnihkg2gbwkvqllv3hjsg8y-kwin-5.27.10/bin/.kwin_wayland-wrapped - Tue 2024-04-30 14:52:11 PDT5924 1000 1000 SIGSEGV missing /nix/store/8hwpp6dgndnihkg2gbwkvqllv3hjsg8y-kwin-5.27.10/bin/.kwin_wayland-wrapped - Mon 2024-05-06 13:22:22 PDT5623 1000 1000 SIGSEGV present /nix/store/8hwpp6dgndnihkg2gbwkvqllv3hjsg8y-kwin-5.27.10/bin/.kwin_wayland-wrapped 15.3M Mon 2024-05-06 20:06:06 PDT 211479 1000 1000 SIGSEGV present /nix/store/8hwpp6dgndnihkg2gbwkvqllv3hjsg8y-kwin-5.27.10/bin/.kwin_wayland-wrapped 16.5M Tue 2024-05-07 22:25:10 PDT 283556 1000 1000 SIGSEGV present /nix/store/8hwpp6dgndnihkg2gbwkvqllv3hjsg8y-kwin-5.27.10/bin/.kwin_wayland-wrapped 16.7M Tue 2024-05-07 22:26:29 PDT 631249 1000 1000 SIGSEGV present /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/bin/.kwin_wayland-wrapped 9.4M Tue 2024-05-07 22:32:00 PDT 634884 1000 1000 SIGSEGV present /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/bin/.kwin_wayland-wrapped 8.3M Tue 2024-05-14 19:31:29 PDT 639991 1000 1000 SIGSEGV present /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/bin/.kwin_wayland-wrapped 20.3M Tue 2024-05-14 19:32:23 PDT 1765630 1000 1000 SIGSEGV present /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/bin/.kwin_wayland-wrapped 7.8M Fri 2024-05-17 18:02:07 PDT5670 1000 1000 SIGSEGV present /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/bin/.kwin_wayland-wrapped 15.0M Sun 2024-05-19 21:32:47 PDT5714 1000 1000 SIGSEGV present /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/bin/.kwin_wayland-wrapped 13.8M Sun 2024-05-19 23:11:33 PDT 27291 1000 1000 SIGSEGV present /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/bin/.kwin_wayland-wrapped 14.1M Sun 2024-05-19 23:41:46 PDT 42049 1000 1000 SIGSEGV present /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/bin/.kwin_wayland-wrapped 12.5M Mon 2024-05-20 00:18:35 PDT 47675 1000 1000 SIGSEGV present /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/bin/.kwin_wayland-wrapped 9.4M Mon 2024-05-20 11:08:22 PDT 53705 1000 1000 SIGSEGV present /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/bin/.kwin_wayland-wrapped 11.9M Mon 2024-05-20 11:17:08 PDT 60377 1000 1000 SIGSEGV present /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/bin/.kwin_wayland-wrapped 13.5M Mon 2024-05-20 11:54:00 PDT 64847 1000 1000 SIGSEGV present /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/bin/.kwin_wayland-wrapped 16.0M Mon 2024-05-20 11:56:54 PDT 82622 1000 1000 SIGSEGV present /nix/store/pphwrqfrkbngq394cpxv1pi98i1a54ys-kwin-5.27.11/bin/.kwin_wayland-wrapped 9.9M Mon 2024-05-20 12:25:42 PDT 86677 1000 1000 SIGSEGV present
[kwin] [Bug 487043] Extreme stutters/hangs when using certain desktop effects when "~/.cache" is on slow storage
https://bugs.kde.org/show_bug.cgi?id=487043 Oded Arbel changed: What|Removed |Added CC||o...@geek.co.il --- Comment #3 from Oded Arbel --- If I understand correctly, the problem is that kwin -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487043] Extreme stutters/hangs when using certain desktop effects when "~/.cache" is on slow storage
https://bugs.kde.org/show_bug.cgi?id=487043 Fabian Arndt changed: What|Removed |Added CC||fabian.ar...@root-core.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 483429] Screen freezes with Adaptive Sync enabled
https://bugs.kde.org/show_bug.cgi?id=483429 Fabian Arndt changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #2 from Fabian Arndt --- I can confirm that issue on Nobara (AMD GPU) and Manjaro (Intel/Nvidia), both Plasma 6.0.4. It sometimes freezes for a longer period, until you move the cursor or the screen refreshes. So it seems to be a timing / refresh issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487058] plasmashell crash
https://bugs.kde.org/show_bug.cgi?id=487058 --- Comment #3 from Dylan --- I just installed some updates, and this issue seems to be gone. I'm not sure exactly what package upgrade fixed it though... -- You are receiving this mail because: You are watching all bug changes.
[kcolorchooser] [Bug 479406] The "Pick Screen Color" button is missing on Wayland session
https://bugs.kde.org/show_bug.cgi?id=479406 Nate Graham changed: What|Removed |Added Version Fixed In||24.05 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 482853] "When locked, turn off screen" needs a checkbox to disable/enable it
https://bugs.kde.org/show_bug.cgi?id=482853 --- Comment #3 from Jakob Petsovits --- A relevant merge request gets halfway to implementing this bug report: https://invent.kde.org/plasma/powerdevil/-/merge_requests/358 In addition to UI changes, this also does away with the upper limit on locked-screen timeouts. I designed in in a way that it should be straightforward to add a "When locked: Never" option to round out the existing functionality. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487340] New: window focus and clipboard act flaky
https://bugs.kde.org/show_bug.cgi?id=487340 Bug ID: 487340 Summary: window focus and clipboard act flaky Classification: Plasma Product: kwin Version: 6.0.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: akostadi...@gmail.com Target Milestone: --- SUMMARY I observe flaky behavior of window focus and clipboard. I file this as a single bug because both things I will describe are related to switching windows so are likely related. Often when swithing to an existing konsole window with the mouse or Alt+Tab, the cursor in the terminal appears hollow and pasting with middle mouse click does not work no matter how many times I click with the mouse inside the window. Only when I press a keyboard button, the cursor becomes filled and now I can paste with a middle mouse click. Then switching between Firefox (125.0.3 in wayland mode), selecting a line, doesn't set clipboard content. I have to try more than once sometimes until the text is copied. I have selected the option in clipboard "keep the selection and clipboard the same". STEPS TO REPRODUCE 1. Open Firefox and Konsole 2. Switch to Firefox window and select text with the mouse 3. switch to Konsole window and middle click to paste text OBSERVED RESULT 1. sometimes selected text in Firefox doesn't reach clipboard, more attempts to select needed 2. often first need to press a keyboard key before I can middle-click paste into konsole EXPECTED RESULT 1. Selected text should always reach clipboard 2. I should be able to just click Konsole window to bring focus to it and middle-click paste without the need to press a keyboard button SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.8.9-300.fc40.x86_64 (64-bit) (available in About System) KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Graphics: Radeon 780M Graphics ADDITIONAL INFORMATION I have no idea how to debug this. I wanted to see like in earlier plasma versions, to choose between software renderer and OpenGL, I can't see that option here though. So I understand the bug report is not very useful unless you can reproduce it, but then I assume you would have fixed it already if you had it in your system, because it is not really tolerable... or maybe that's just me. Anyway if you tell me how can I provide more useful debug information, I'll gladly do. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 487115] Custom Clip Job error message for ffmpeg parameters
https://bugs.kde.org/show_bug.cgi?id=487115 --- Comment #11 from Bernd --- (In reply to Bernd from comment #10) > (In reply to Jean-Baptiste Mardelle from comment #9) > > This should now be fixed with my last commits in git master, please test. > > Test works: I added a new clip job with an ffmpeg command line parameter > list enclosed with " and it works. > > The field Output File Extension expects an extension like mp4 or mkv, and > throws an error if anything else is entered. I don't understand why this is > needed as ffmpeg uses the same container as the input file. If the field is > to have a file name suffix like "clip_job" or "0001" it doesn't work that > way and would need to be renamed to Output File Suffix. Tested on Windows 11 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 487247] OBS closes with no error reports in log when I click ANY button that browses files.
https://bugs.kde.org/show_bug.cgi?id=487247 Joshua Goins changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/kwidgetsaddons/-/com ||mit/64fcc6fff124dd74e059b92 ||71ba6693a2d561704 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #5 from Joshua Goins --- Git commit 64fcc6fff124dd74e059b9271ba6693a2d561704 by Joshua Goins. Committed on 21/05/2024 at 21:15. Pushed by redstrate into branch 'master'. KMessageWidget: Avoid calling polish() inside of palette update This causes infinite recursion as the palette is set and unset when the application uses CSS stylesheets. But this call is simply unnecessary and can be removed. M +1-1src/kmessagewidget.cpp https://invent.kde.org/frameworks/kwidgetsaddons/-/commit/64fcc6fff124dd74e059b9271ba6693a2d561704 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487043] Extreme stutters/hangs when using certain desktop effects when "~/.cache" is on slow storage
https://bugs.kde.org/show_bug.cgi?id=487043 devmi...@devminer.xyz changed: What|Removed |Added CC||devmi...@devminer.xyz --- Comment #2 from devmi...@devminer.xyz --- This solved the Alt+Tab animations being slow and hanging for me, even though I already have a sort-of fast PCIe gen 3 SSD. The data loaded from disk on every Alt+Tab seems small enough to just stay in memory, so I would appreciate if the effects would just stay loaded in, *especially* for something like Alt+Tab. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwidgetsaddons] [Bug 487247] OBS closes with no error reports in log when I click ANY button that browses files.
https://bugs.kde.org/show_bug.cgi?id=487247 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/frameworks/kwidgetsaddons/-/merge_requests/248 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 487310] Plasma Panel has weird extra space at plasmashell startup when using icons only task manager
https://bugs.kde.org/show_bug.cgi?id=487310 duha.b...@gmail.com changed: What|Removed |Added CC||duha.b...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 487210] plasmashell doesn't start due to systemmonitor plasmoid placed in Panel
https://bugs.kde.org/show_bug.cgi?id=487210 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #2 from Piotr Mierzwinski --- (In reply to Nicolas Fella from comment #1) > > plasmashell: symbol lookup error: > > /usr/lib/x86_64-linux-gnu/qt6/plugins/plasma/applets/org.kde.plasma.systemmonitor.so: > > undefined symbol: > > _ZN9KSysGuard20SensorFaceControllerC1ER12KConfigGroupP10QQmlEngine > > This is a Neon packaging issue Thanks for info. Anyway this is sad that issue has not been fixed since couple days. Today happened update of packages. After that I made restart and nothing changed :(. I hope plasma will work (in Neon) soon. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 423031] [Wayland] Modifier keys to move (shift), copy (ctrl) and create a link (ctrl+shift) don't work if pressed after I start to drag the file/folder
https://bugs.kde.org/show_bug.cgi?id=423031 --- Comment #25 from Max --- > It does seem like kde people have given feedback, and its mostly qt we are > waiting on. ... I got confused, David Edmundson has not reviewed it yet, maybe it has fallen between the cracks.. Maybe this bug should be reopened since it needs action from kde people still.. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 481461] Clicking checkbox to select content to share does not work
https://bugs.kde.org/show_bug.cgi?id=481461 Nate Graham changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/fram ||eworks/kirigami/-/commit/4a ||0bc5a89725407e800ce44c662e2 ||1e7f4a35d4f Resolution|--- |FIXED Version Fixed In||6.3 --- Comment #13 from Nate Graham --- Git commit 4a0bc5a89725407e800ce44c662e21e7f4a35d4f by Nate Graham. Committed on 21/05/2024 at 19:36. Pushed by ngraham into branch 'master'. Card: emit toggled() when the user clicks on the header checkbox Checkable cards display a checkbox in the header. When clicked, they emit toggled() which gets bubbled up to the card. However the card doesn't emit the toggled() signal itself, instead only setting the value of its "checked" property. As a result, anything that's listening to the card for a toggled() signal will not get one. Such as, for example, the screen chooser portal code. Fix this by emitting the signal. FIXED-IN: 6.3 M +1-0src/controls/Card.qml https://invent.kde.org/frameworks/kirigami/-/commit/4a0bc5a89725407e800ce44c662e21e7f4a35d4f -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 423031] [Wayland] Modifier keys to move (shift), copy (ctrl) and create a link (ctrl+shift) don't work if pressed after I start to drag the file/folder
https://bugs.kde.org/show_bug.cgi?id=423031 m...@eterkludd.se changed: What|Removed |Added CC||m...@eterkludd.se --- Comment #24 from m...@eterkludd.se --- It should not work yet, as the supposed [fix](https://codereview.qt-project.org/c/qt/qtwayland/+/525413) is open and not merged yet. It even has a merge conflict. It does seem like kde people have given feedback, and its mostly qt we are waiting on. This is one of the deeper papercuts left in wayland, it would really be great if it was given more priority by them, or if theres a way for kde people to take it over. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 455691] Cannot connect to older Windows server "ERRCONNECT_TLS_CONNECT_FAILED"
https://bugs.kde.org/show_bug.cgi?id=455691 Fabio changed: What|Removed |Added Latest Commit||https://invent.kde.org/netw ||ork/krdc/-/commit/8bca0c765 ||c75e38f26f38bde650a48308ab1 ||aaeb Status|REPORTED|RESOLVED CC||ctrlal...@gmail.com Resolution|--- |FIXED Version Fixed In||24.05 --- Comment #1 from Fabio --- Fixed by https://invent.kde.org/network/krdc/-/merge_requests/65 An option to set the minimum TLS security level has been added -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482137] Regression: Filesystem/Clipboard not shared anymore
https://bugs.kde.org/show_bug.cgi?id=482137 Fabio changed: What|Removed |Added CC||teej.d@gmail.com --- Comment #4 from Fabio --- *** Bug 484607 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 484607] Copy and Paste and Folder Sharing not working
https://bugs.kde.org/show_bug.cgi?id=484607 Fabio changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||ctrlal...@gmail.com --- Comment #1 from Fabio --- Clipboard has been fixed in current development version (see BUG 484666), filesystem sharing is still missing. *** This bug has been marked as a duplicate of bug 482137 *** -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482137] Regression: Filesystem/Clipboard not shared anymore
https://bugs.kde.org/show_bug.cgi?id=482137 Fabio changed: What|Removed |Added CC||ctrlal...@gmail.com --- Comment #3 from Fabio --- Clipboard has been fixed in current development version (see BUG 484666), filesystem sharing is still missing. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 484666] Copy - Paste is not working
https://bugs.kde.org/show_bug.cgi?id=484666 Fabio changed: What|Removed |Added CC||sunwe...@gmail.com --- Comment #5 from Fabio --- *** Bug 487140 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 487140] Clipboard doesn't work
https://bugs.kde.org/show_bug.cgi?id=487140 Fabio changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||ctrlal...@gmail.com --- Comment #1 from Fabio --- Duplicate of 484666. Fixed in current development version *** This bug has been marked as a duplicate of bug 484666 *** -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 487334] I would like the Faces "Unconfirmed" and "Unknown" views to be filterable by Album & Sub-Tree
https://bugs.kde.org/show_bug.cgi?id=487334 --- Comment #2 from Michael Moore --- Thanks Maik, Yes, I group/separate the view by albums sometimes and it does help a bit. I'd like to get to where I can Filter by Album and then Group By Face. Then I could see all shots of (eg.) my kid when they were 1. It would make it very easy to quickly say "oh yeah, that's how Kid looked in 2008". -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 487303] plasma-brower-integration causes Cloudflare to lock out humans
https://bugs.kde.org/show_bug.cgi?id=487303 dofficialg...@gmail.com changed: What|Removed |Added CC||dofficialg...@gmail.com --- Comment #5 from dofficialg...@gmail.com --- Also experiencing this issue on all (chromium) browsers that I have the extension enabled on, regardless if actually running on Linux. -- You are receiving this mail because: You are watching all bug changes.
[kcolorchooser] [Bug 479406] The "Pick Screen Color" button is missing on Wayland session
https://bugs.kde.org/show_bug.cgi?id=479406 Nicolas Fella changed: What|Removed |Added Latest Commit|https://invent.kde.org/grap |https://invent.kde.org/grap |hics/kcolorchooser/-/commit |hics/kcolorchooser/-/commit |/dace6c0d2b04b444b4e4a92045 |/7a03f1ccac935cb9c1a8e030a1 |0a7ed24b79cc30 |98d9267b0479f1 --- Comment #19 from Nicolas Fella --- Git commit 7a03f1ccac935cb9c1a8e030a198d9267b0479f1 by Nicolas Fella, on behalf of Thomas Weißschuh. Committed on 21/05/2024 at 20:00. Pushed by nicolasfella into branch 'release/24.05'. Allow dbus processing in qt-base to enable color-picking via portal qt-base uses dbus to query the desktop portal if color-picking is supported, without explicitly waiting for the result. kcolorchooser creates its QColorDialog before the response was processed and therefore color picking via the portal is presumed to be unavailable. Give the eventloop the opportunity to process the event and only afterwards create the QColorDialog. See https://bugreports.qt.io/browse/QTBUG-120957 (cherry picked from commit dace6c0d2b04b444b4e4a920450a7ed24b79cc30) M +3-0kcolorchooser.cpp https://invent.kde.org/graphics/kcolorchooser/-/commit/7a03f1ccac935cb9c1a8e030a198d9267b0479f1 -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 487339] New: Filelight Tooltip Incorrect Offset when Displayed to the Right of the Mouse Cursor
https://bugs.kde.org/show_bug.cgi?id=487339 Bug ID: 487339 Summary: Filelight Tooltip Incorrect Offset when Displayed to the Right of the Mouse Cursor Classification: Applications Product: filelight Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: eamonn...@protonmail.com CC: martin.sandsm...@kde.org Target Milestone: --- Created attachment 169689 --> https://bugs.kde.org/attachment.cgi?id=169689=edit Incorrect Tooltip Behaviour SUMMARY When the Filelight tooltip displays to the *right* of the mouse cursor (i.e. when it has enough room to display on the right), then it displays very slightly to the right and down of the mouse cursor, like a tooltip with some padding. But when the Filelight tooltip displays to the *left* of the mouse cursor, it is offset, and the further to the *right* that the mouse cursor goes, the further to the *left* that the tooltip goes. In other words moving the cursor to the right of the window moves the tooltip *further away* from the cursor, and moving it to the right moves the tooltip *closer to* the cursor. As it gets closer it eventually has enough space to display to the right of the cursor again and so fades back to being beside the cursor as described above, and displays normally. I have attached a screenshot of the offset tooltip. STEPS TO REPRODUCE 1. Open Filelight 2. Move the cursor far enough to the right of the window so that the tooltip appears on the left of the cursor - The window may need to be reduced in size to make this easier to accomplish 3. Observe tooltip being on the incorrect side of the window. OBSERVED RESULT Tooltip displays away from the mouse when to the left of the cursor. EXPECTED RESULT Tooltip behaves the same on the left side of the cursor as it does on the right. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.9.1 Linux Zen KDE Plasma Version: 6.0.4 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION I don't remember this happening in Plasma 5.X, but unsure if it affected all versions of Plasma 6. I took a look at the code but wasn't sure why this was happening, I couldn't find the logic that flips the tooltip. I looked for other applications I have installed that use Kirigami which have the same dynamic tooltips as Filelight but couldn't find any, I wanted to see if they have the same behaviour and if not what they do on their side to fix the problem. But I came up short. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479492] On Wayland, plasmashell exits with large(ish) number of windows
https://bugs.kde.org/show_bug.cgi?id=479492 --- Comment #13 from Fushan Wen --- Git commit e65a6c29138751cdeb7298b9cd4f0520769e3712 by Fushan Wen, on behalf of Xaver Hugl. Committed on 21/05/2024 at 19:34. Pushed by fusionfuture into branch 'master'. libtaskmanager: update org_kde_plasma_window_management to version 17 M +46 -6libtaskmanager/waylandtasksmodel.cpp https://invent.kde.org/plasma/plasma-workspace/-/commit/e65a6c29138751cdeb7298b9cd4f0520769e3712 -- You are receiving this mail because: You are watching all bug changes.
[kcolorchooser] [Bug 479406] The "Pick Screen Color" button is missing on Wayland session
https://bugs.kde.org/show_bug.cgi?id=479406 Thomas Weißschuh changed: What|Removed |Added Latest Commit||https://invent.kde.org/grap ||hics/kcolorchooser/-/commit ||/dace6c0d2b04b444b4e4a92045 ||0a7ed24b79cc30 Resolution|--- |FIXED Status|CONFIRMED |RESOLVED --- Comment #18 from Thomas Weißschuh --- Git commit dace6c0d2b04b444b4e4a920450a7ed24b79cc30 by Thomas Weißschuh. Committed on 21/05/2024 at 18:02. Pushed by nicolasfella into branch 'master'. Allow dbus processing in qt-base to enable color-picking via portal qt-base uses dbus to query the desktop portal if color-picking is supported, without explicitly waiting for the result. kcolorchooser creates its QColorDialog before the response was processed and therefore color picking via the portal is presumed to be unavailable. Give the eventloop the opportunity to process the event and only afterwards create the QColorDialog. See https://bugreports.qt.io/browse/QTBUG-120957 M +3-0kcolorchooser.cpp https://invent.kde.org/graphics/kcolorchooser/-/commit/dace6c0d2b04b444b4e4a920450a7ed24b79cc30 -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 487338] New: Floating point exception: 8
https://bugs.kde.org/show_bug.cgi?id=487338 Bug ID: 487338 Summary: Floating point exception: 8 Classification: Applications Product: kdiff3 Version: 1.11.1 Platform: Homebrew (macOS) OS: macOS Status: REPORTED Severity: critical Priority: NOR Component: application Assignee: reeves...@gmail.com Reporter: k...@jaggard.org.uk Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Install kdiff3 1.11.1 on MacOS using brew 2. Launch kdiff3 using git mergetool (it launches with --auto --L1 --L2 --L3 -o and redirects stderr to stdout and stdout to /dev/null Example command line: /Applications/kdiff3.app/Contents/MacOS/kdiff3 --auto --L1 'path/to/MyFile.java (Base)' --L2 'path/to/MyFile.java (Local)' --L3 'path/to/MyFile.java (Remote)' -o path/to/MyFile.java ./path/to/MyFile_BASE_31578.java ./path/to/MyFile_LOCAL_31578.java ./path/to/MyFile_REMOTE_31578.java OBSERVED RESULT Floating point exception: 8 EXPECTED RESULT Diff shown SOFTWARE/OS VERSIONS macOS: 14.4.1 KDE Frameworks Version 6.2.0 Qt Version 6.7.0 (built against 6.7.0) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 487115] Custom Clip Job error message for ffmpeg parameters
https://bugs.kde.org/show_bug.cgi?id=487115 Bernd changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |CONFIRMED --- Comment #10 from Bernd --- (In reply to Jean-Baptiste Mardelle from comment #9) > This should now be fixed with my last commits in git master, please test. Test works: I added a new clip job with an ffmpeg command line parameter list enclosed with " and it works. The field Output File Extension expects an extension like mp4 or mkv, and throws an error if anything else is entered. I don't understand why this is needed as ffmpeg uses the same container as the input file. If the field is to have a file name suffix like "clip_job" or "0001" it doesn't work that way and would need to be renamed to Output File Suffix. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 486689] File creation and saving File Dialog not coherent with current project context
https://bugs.kde.org/show_bug.cgi?id=486689 Igor Kushnir changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||igor...@gmail.com --- Comment #1 from Igor Kushnir --- Kate does something similar to what you request: it uses the directory of the last active tab though (not the previous in the visible tab order). KDevelop ends up using the directory of some unspecified tab (possibly first in tab order). Here is why: 1. KTextEditor::DocumentPrivate::getSaveFileUrl() delegates the ordering to KTextEditor::Editor::instance()->application()->activeMainWindow()->views() [we will try to get the url of the last used view, we assume some properly ordered views() list is around]. 2. Kate returns KateMainWindow::views(), which delegates to KateViewManager::views() [@return all views sorted by their last use, most recently used first]. 3. KDevelop returns KTextEditorIntegration::MainWindow::views(), which delegates to Sublime::Area::views() [@return the list of all views in this area in no particular order]. KDevelop's Most-Recently-Used Document Switcher plugin (Ctrl+Tab) maintains the list of documents sorted by their last use. So KDevelop could do the same as Kate. Might be difficult to implement properly though, because the list is in the plugin, not KDevPlatform. Maybe your proposed tab ordering would be easier to implement. Note: I don't expect anyone to implement this feature any time soon, unless you scratch your own itch. -- You are receiving this mail because: You are watching all bug changes.
[kuser] [Bug 376157] kf5 kuser
https://bugs.kde.org/show_bug.cgi?id=376157 Stuart K. Smith changed: What|Removed |Added CC||stuartksm...@gmail.com Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #13 from Stuart K. Smith --- NOT resolved. No actual way to modify users from System Settings of than: Name, Username, Account type, Email address. The old KUser allowed editing of Home directory, Groupmemberships (and editing of Groups themselves), and login shell. At a minimum, the ability to add a user to a group is required unless the decision has been made to move all administrative tasks to the command line. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 487337] New: fingerprint not unlocking
https://bugs.kde.org/show_bug.cgi?id=487337 Bug ID: 487337 Summary: fingerprint not unlocking Classification: Plasma Product: kscreenlocker Version: 6.0.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ndbeck...@gmail.com Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY This is a fully updated F40 laptop, lenovo x1. I've enrolled a fingerprint. But if I lock screen, I can't unlock with fingerprint. Password works. STEPS TO REPRODUCE 1. enroll fingerprint 2. lock screen Meta-L 3. try to unlock with fingerprint OBSERVED RESULT Only possibly relevant info from journal: May 21 15:03:46 nbecker0 kscreenlocker_greet[83641]: kscreenlocker_greet: Lockscreen QML outdated, falling back to default May 21 15:03:50 nbecker0 wpa_supplicant[1461]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=-59 noise= txrate=29200 May 21 15:03:58 nbecker0 audit[83692]: USER_AUTH pid=83692 uid=1000 auid=1000 ses=3 subj=unconfined_u:unconfined_r:chkpwd_t:s0-s0:c0.c1023 > May 21 15:03:58 nbecker0 kscreenlocker_greet[83641]: qt.qpa.wayland: Could not create EGL surface (EGL error 0x3000) May 21 15:03:58 nbecker0 kscreenlocker_greet[83641]: Failed to write to the pipe: Bad file descriptor. EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 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.
[plasmashell] [Bug 483348] Plasma desktop panel moving to wrong screen on next login
https://bugs.kde.org/show_bug.cgi?id=483348 Kristen McWilliam changed: What|Removed |Added CC||kmcwilliampub...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479492] On Wayland, plasmashell exits with large(ish) number of windows
https://bugs.kde.org/show_bug.cgi?id=479492 --- Comment #12 from Zamundaaa --- Git commit 3465ecac1685256b0862d5c4478756d2b5ca1c4f by Xaver Hugl. Committed on 21/05/2024 at 15:48. Pushed by zamundaaa into branch 'master'. wayland: implement plasma window management v17 This fixes plasmashell crashing because of the stacking order string exceeding the size of a Wayland message M +35 -3src/wayland/plasmawindowmanagement.cpp https://invent.kde.org/plasma/kwin/-/commit/3465ecac1685256b0862d5c4478756d2b5ca1c4f -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481113] Changes to pinned apps are not saved when Plasmashell quits
https://bugs.kde.org/show_bug.cgi?id=481113 --- Comment #38 from yurzhang...@gmail.com --- Created attachment 169688 --> https://bugs.kde.org/attachment.cgi?id=169688=edit Patch for kglobalacceld-6.0.4 (In reply to Nate Graham from comment #37) > I wonder if this could have been caused by the bug that > https://invent.kde.org/plasma/kglobalacceld/-/merge_requests/49 fixed. > Apparently in some distros, kbuildsycoca is run frequently/repeatedly, and > there was previously an issue that could cause some things to not get saved > properly. > > Can anyone test with Plasma 6.0.5, which includes this fix and is being > released today? I created a patch from this merge request and applied it but the bug still exist. I haven't tried Plasma 6.0.5 yet, if it is fixed in 6.0.5, maybe some other change fixed it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485312] On X11, Window appears in task bar of wrong screen in multiscreen setup
https://bugs.kde.org/show_bug.cgi?id=485312 --- Comment #6 from Thorolf E.R. Weißhuhn --- Don't remember having seen that before 6. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 482705] Selecting MP4/H.264 for video output creates garbled video.
https://bugs.kde.org/show_bug.cgi?id=482705 VesperLlama changed: What|Removed |Added CC||k...@vesperllama.anonaddy.co ||m -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 470369] Add "Pin Screenshot" Functionality to Spectacle
https://bugs.kde.org/show_bug.cgi?id=470369 VesperLlama changed: What|Removed |Added CC||k...@vesperllama.anonaddy.co ||m -- You are receiving this mail because: You are watching all bug changes.
[kuser] [Bug 376157] kf5 kuser
https://bugs.kde.org/show_bug.cgi?id=376157 --- Comment #12 from s...@altereddreams.net --- Yes there is a section in the System Settings but that doesn't allow viewing groups or system users like you could in older versions of KDE using KUser. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 487135] L2tp vpn setup bug
https://bugs.kde.org/show_bug.cgi?id=487135 duha.b...@gmail.com changed: What|Removed |Added CC||maxson.jor...@gmail.com --- Comment #2 from duha.b...@gmail.com --- *** Bug 487313 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 487313] BUG L2tp Configurations KD6
https://bugs.kde.org/show_bug.cgi?id=487313 duha.b...@gmail.com changed: What|Removed |Added CC||duha.b...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from duha.b...@gmail.com --- *** This bug has been marked as a duplicate of bug 487135 *** -- You are receiving this mail because: You are watching all bug changes.
