[kscreenlocker] [Bug 493422] New: No longer possible to show clock on prompt but hide it when prompt is hidden
https://bugs.kde.org/show_bug.cgi?id=493422 Bug ID: 493422 Summary: No longer possible to show clock on prompt but hide it when prompt is hidden Classification: Plasma Product: kscreenlocker Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: k...@privat.broulik.de Target Milestone: --- SUMMARY There is only an optioon “Show Clock” now which either hides or shows the clock. The screen saver use case of showing the clock only on the prompt is no longer properly supported. STEPS TO REPRODUCE 1. Go to screen locker settings 2. Click “change appearance” OBSERVED RESULT Only a global clock option is there EXPECTED RESULT It is possible to show the clock only on the prompt (screen saver use case) SOFTWARE/OS VERSIONS Linux/KDE Plasma: git master as of 2024-09-14 Qt Version: 6.7.2 ADDITIONAL INFORMATION The settings changed without my intervention and and my clock is completely gone now -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 472863] "showbackground" icon from Breeze Plasma theme is missing from Breeze icon theme
https://bugs.kde.org/show_bug.cgi?id=472863 Kai Uwe Broulik changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-desktop/-/commit/ |ma/plasma-desktop/-/commit/ |4f87e59791b0ce497f7282093cf |1df659c999c92252cb0f60e025e |5d75a4d6ffe25 |e7a9141c1265d --- Comment #7 from Kai Uwe Broulik --- Git commit 1df659c999c92252cb0f60e025ee7a9141c1265d by Kai Uwe Broulik. Committed on 08/09/2024 at 12:50. Pushed by broulik into branch 'Plasma/6.1'. containments/desktop: Use show-background icon The showbackground config overlay was moved into Breeze icons. (cherry picked from commit 4f87e59791b0ce497f7282093cf5d75a4d6ffe25) Co-authored-by: Kai Uwe Broulik M +1-3containments/desktop/package/contents/ui/ConfigOverlay.qml https://invent.kde.org/plasma/plasma-desktop/-/commit/1df659c999c92252cb0f60e025ee7a9141c1265d -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 472863] "showbackground" icon from Breeze Plasma theme is missing from Breeze icon theme
https://bugs.kde.org/show_bug.cgi?id=472863 Kai Uwe Broulik changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/plasma-desktop/-/commit/ ||4f87e59791b0ce497f7282093cf ||5d75a4d6ffe25 --- Comment #6 from Kai Uwe Broulik --- Git commit 4f87e59791b0ce497f7282093cf5d75a4d6ffe25 by Kai Uwe Broulik. Committed on 07/09/2024 at 12:57. Pushed by broulik into branch 'master'. containments/desktop: Use show-background icon The showbackground config overlay was moved into Breeze icons. M +1-3containments/desktop/package/contents/ui/ConfigOverlay.qml https://invent.kde.org/plasma/plasma-desktop/-/commit/4f87e59791b0ce497f7282093cf5d75a4d6ffe25 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 472863] "showbackground" icon from Breeze Plasma theme is missing from Breeze icon theme
https://bugs.kde.org/show_bug.cgi?id=472863 --- Comment #5 from Kai Uwe Broulik --- Git commit 34867b228eba605ce1b9706fb5973600426cb91d by Kai Uwe Broulik. Committed on 07/09/2024 at 12:31. Pushed by broulik into branch 'master'. Add show-background icon This lifts the "showbackground" icon from Plasma's original config overlays SVG. A +22 -0icons/actions/16/show-background.svg https://invent.kde.org/frameworks/breeze-icons/-/commit/34867b228eba605ce1b9706fb5973600426cb91d -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 401088] Potentially misleading "Filesystem mounted at '/' is not responding" notifications
https://bugs.kde.org/show_bug.cgi?id=401088 Kai Uwe Broulik changed: What|Removed |Added Status|CONFIRMED |RESOLVED URL||https://invent.kde.org/plas ||ma/plasma-workspace/-/commi ||t/18b550f6c640bae38ff492a15 ||6d8e32081ed93a7 Resolution|--- |FIXED CC||k...@privat.broulik.de --- Comment #52 from Kai Uwe Broulik --- I removed the "filesystem not responding" notification -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 492087] Plasma Integration Extension no longer compatible with Chrome due to Manifest V3 rollout
https://bugs.kde.org/show_bug.cgi?id=492087 --- Comment #3 from Kai Uwe Broulik --- Please give this a try: https://invent.kde.org/plasma/plasma-browser-integration/-/merge_requests/78 -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 492087] Plasma Integration Extension no longer compatible with Chrome due to Manifest V3 rollout
https://bugs.kde.org/show_bug.cgi?id=492087 --- Comment #2 from Kai Uwe Broulik --- So far it’s only dev builds, right? I will update p-b-i to Manifest v3 within the next few weeks. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466771] Some windows are painted black on X11, processes freeze
https://bugs.kde.org/show_bug.cgi?id=466771 --- Comment #35 from Kai Krakow --- (In reply to Ben Hay from comment #33) > Even swapped my NVidia card for AMD. Bug still occured, although it takes a > little longer to manifest. > > Finally I uninstalled the latte-dock package. > Plasma is stable again. This is probably because latte-dock is a heavy user of GPU resources, probably in terms of VRAM. I don't think this is caused by latte-dock per se, there's something generally going wrong deeper in the stack. Same probably applies to plasmashell. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488941] Plasma 6.1 Screen turn off on login into a Wayland session if HDR is enabled
https://bugs.kde.org/show_bug.cgi?id=488941 --- Comment #45 from Kai --- I can confirm this behavior with separate HDR/WCG settings. - both disabled: Plasma starts - HDR enabled and WCG disabled: Plasma starts - HDR disabled and WCG enabled: no output to screen - both enabled: no output to screen -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 489866] Krunner doesn't order results based on my preferred order
https://bugs.kde.org/show_bug.cgi?id=489866 Kai Eckert changed: What|Removed |Added CC||gen-...@kaiec.de Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Kai Eckert --- I can confirm this bug. It sounds like a small thing, I would suspect that it got introduced in this commit: https://github.com/KDE/krunner/commit/d02e1c13a9ee92a90218a4584a3642f39da4e28a -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466771] Some windows are painted black on X11, processes freeze
https://bugs.kde.org/show_bug.cgi?id=466771 Kai Krakow changed: What|Removed |Added CC||k...@kaishome.de --- Comment #32 from Kai Krakow --- I've first seen this on Plasma 6 with Gen4 Intel iGPU using wayland. It doesn't happen with Xorg on that same system. Maybe related: On my NVIDIA system, the same thing happens with wayland quite easily if I run wayland during gaming/streaming with OBS. It's really bad, I've gone back to Xorg. But even with Xorg, kwin_x11 and plasma-shell often crash and restart after 2+ hours, causing severe stutters in game and causing framedrops in recording/streaming. When this happens, plasmashell already uses 2 GB of VRAM. I really don't know why it eats so much VRAM, and it probably crashes because it fails to allocate anything more. VRAM usage of plasmashell it absurd, even when idle, it already uses 800+ MB, after some light usage, it easily uses 1+ GB already. The nvidia-drivers can do some cleanup every once in a while (a feature called "CPMM", please ask NVIDIA developers about the details, I'm not allowed to disclose the tuning parameters: it's active by default with 10min cleanup interval). It brings usage down from 800 MB initially to only 170 MB (using 15 seconds cleanup interval [1]). But that only means that plasmashell piles up a lot of render surfaces or render buffers it never cleans up on its own. This feature only works for GL, so if you switch to Vulkan using "kcmshell6 qtquicksettings", it shows the bad behavior again. Unfortunately, using the software renderer no longer works in Plasma 6: it renders icons to the wrong positions or completely removes them from rendering as soon as you hover the mouse over them. But in this mode, plasmashell uses only 4 MB of VRAM and I'm seeing no negative performance impact. In Plasma 5, this has been the game changer. Now with Plasma 6, the system isn't really usable if you stress the system with VRAM allocations as games usually do. And that's not limited to NVIDIA, it happens on Intel iGPUs too, and usually very quickly because of the low amount of shared VRAM. And with wayland, all of this is handled exceptionally bad, Xorg is a little more forgiving. While wayland works beautifully (ultra-smooth desktop, proper scaling etc) for light desktop usage, everything causes havoc if you do some real work like having lots of open windows on multiple monitors (4 in my instance), rendering or gaming, especially with OBS. Plasma starts to fight with every process in the system over GPU resources. There's no longer an option to use software rendering because rendering is just broken with it. I really don't need hardware accelerated rendering for the plasmashell: In the end, it's just a bar to switch between applications, and launcher and notification manager. But it's the main consumer of GPU resources on a KDE desktop, and it fights for it really hard, hurting performance more than what is gained by hardware rendering. Currently I can work around it by using QSV with OBS (instead of NVENC), limiting my main game VRAM usage through DXVK and using a short CMPP interval only for plasmashell. But that only helps short term, longer sessions are really borked, and after more than 2 days of usage, I'd rather need to reboot before trying anything else. Also, it's a little more stable by using the NVIDIA open kernel drivers: they seem to handle VRAM a little different. But even if drivers can or should fix it, VRAM usage of plasmashell is still absurdly high and it will hurt performance for gaming - no matter what a driver can do. I hope this gets fixed sooner than later, that would be great. :-) [1]: This low interval has some unwanted side-effects in OBS as it cleans up OBS render resources, too, leading to repeated frametime spikes during recording or streaming. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 488653] plasma-browser-integration-host crashes in Firefox 127.0 after upgrade to Plasma 6.1
https://bugs.kde.org/show_bug.cgi?id=488653
--- Comment #24 from Kai ---
(In reply to Fabian Vogt from comment #23)
> If anyone is able to reprouce this reliably, please try
> plasma-browser-integration-host with this line removed:
Your patch seems to have solved the problem for me.
Builded with https://aur.archlinux.org/plasma-browser-integration-git.git and
the following modifications:
diff --git a/PKGBUILD b/PKGBUILD
index fb7e900..c37db3c 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -3,14 +3,14 @@
# Contributor: Antonio Rojas
pkgname=plasma-browser-integration-git
pkgver=6.0.80_r1569.g57b9b6a3
pkgrel=1
pkgdesc='Components necessary to integrate browsers into the Plasma Desktop'
arch=($CARCH)
url='https://www.kde.org/plasma-desktop'
license=(GPL-2.0-or-later)
-depends=(gcc-libs glibc plasma-activities-git kconfig-git kcoreaddons-git
kcrash-git kdbusaddons-git kfilemetadata-git ki18n-git kio-git kjobwidgets-git
kservice-git kstatusnotifieritem-git plasma-workspace-git purpose-git qt6-base)
-makedepends=(git extra-cmake-modules-git)
+depends=(gcc-libs glibc plasma-activities kconfig kcoreaddons kcrash
kdbusaddons kfilemetadata ki18n kio kjobwidgets kservice kstatusnotifieritem
plasma-workspace purpose qt6-base)
+makedepends=(git extra-cmake-modules)
conflicts=(${pkgname%-git})
provides=(${pkgname%-git})
groups=(plasma-git)
@@ -27,6 +27,20 @@ build() {
cmake -B build -S ${pkgname%-git} \
-DQT_MAJOR_VERSION=6 \
-DINSTALL_CHROME_MANIFEST=ON
+
+ patch -d $srcdir/${pkgname%-git} -p1 <setWindowIcon(QIcon::fromTheme(service->icon()));
+
+ m_tasksModel->disconnect(this); // prevent further signal emission to not
deref a nullptr https://bugs.kde.org/show_bug.cgi?id=435811
+-m_tasksModel->deleteLater();
+ m_tasksModel = nullptr;
+
+ return true;
+EOF
+
cmake --build build
}
plasma-browser-integration: 6.1.80_r1606.g51427d9a-1
Firefox: 128.0.3-1
Operating System: Arch Linux
KDE Plasma Version: 6.1.3
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.2
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kio] [Bug 454436] Elided Places Panel items don't have tooltips showing their full text
https://bugs.kde.org/show_bug.cgi?id=454436 Kai Uwe Broulik changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||https://invent.kde.org/fram ||eworks/kio/-/commit/d553b5f ||2d585fbccc900cae2eea64d77ea ||54e407 Resolution|--- |FIXED --- Comment #3 from Kai Uwe Broulik --- Git commit d553b5f2d585fbccc900cae2eea64d77ea54e407 by Kai Uwe Broulik. Committed on 24/07/2024 at 17:38. Pushed by broulik into branch 'master'. KFilePlacesView: Show label in tooltip if it is elided Suppress tooltip on Wayland before Qt 6.8, however. Qt Wayland cannot reposition popups before that, causing in the tooltips being stuck in place, which is distracting. M +42 -4src/filewidgets/kfileplacesview.cpp M +5-0src/filewidgets/kfileplacesview_p.h https://invent.kde.org/frameworks/kio/-/commit/d553b5f2d585fbccc900cae2eea64d77ea54e407 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 454436] Elided Places Panel items don't have tooltips showing their full text
https://bugs.kde.org/show_bug.cgi?id=454436 Kai Uwe Broulik changed: What|Removed |Added CC||anditosan1...@gmail.com --- Comment #2 from Kai Uwe Broulik --- *** Bug 463831 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 463831] Elided Text in Sidebar Needs to Show Full String in Tooltip
https://bugs.kde.org/show_bug.cgi?id=463831 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de Resolution|--- |DUPLICATE Status|ASSIGNED|RESOLVED --- Comment #2 from Kai Uwe Broulik --- *** This bug has been marked as a duplicate of bug 454436 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 490432] ~/.config/plasma-workspace/env startup scripts cannot set an environment variable as empty
https://bugs.kde.org/show_bug.cgi?id=490432 Kai Uwe Broulik changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/-/commi |ma/plasma-workspace/-/commi |t/f469e2f22d8137e578fe5a729 |t/a413e7d985bcd0b54dea24755 |3287e64eb1dce94 |6aa21328ffcd43b --- Comment #3 from Kai Uwe Broulik --- Git commit a413e7d985bcd0b54dea247556aa21328ffcd43b by Kai Uwe Broulik. Committed on 23/07/2024 at 12:14. Pushed by broulik into branch 'Plasma/6.1'. startplasma: Also set environment variable when it is not currently set qgetenv returns a null QByteArray when there is currently no such variable. A null QByteArray is distinct from an empty one. However, operator!= will treat them the same. Therefore it's impossible to set an environment variable to an empty value. Explicitly check for null and also qputenv it when this is the case. (cherry picked from commit f469e2f22d8137e578fe5a7293287e64eb1dce94) Co-authored-by: Kai Uwe Broulik M +2-1startkde/startplasma.cpp https://invent.kde.org/plasma/plasma-workspace/-/commit/a413e7d985bcd0b54dea247556aa21328ffcd43b -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 490432] ~/.config/plasma-workspace/env startup scripts cannot set an environment variable as empty
https://bugs.kde.org/show_bug.cgi?id=490432 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/-/commi ||t/f469e2f22d8137e578fe5a729 ||3287e64eb1dce94 --- Comment #2 from Kai Uwe Broulik --- Git commit f469e2f22d8137e578fe5a7293287e64eb1dce94 by Kai Uwe Broulik. Committed on 23/07/2024 at 11:03. Pushed by broulik into branch 'master'. startplasma: Also set environment variable when it is not currently set qgetenv returns a null QByteArray when there is currently no such variable. A null QByteArray is distinct from an empty one. However, operator!= will treat them the same. Therefore it's impossible to set an environment variable to an empty value. Explicitly check for null and also qputenv it when this is the case. M +2-1startkde/startplasma.cpp https://invent.kde.org/plasma/plasma-workspace/-/commit/f469e2f22d8137e578fe5a7293287e64eb1dce94 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482889] plasmashell hits ASSERT on startup after upgrade to 6.0.0
https://bugs.kde.org/show_bug.cgi?id=482889 Kai Uwe Broulik changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-desktop/-/commit/ |ma/plasma-desktop/-/commit/ |0264726f8720d3093bd3ba10f61 |20e6c20de00e03ebb1c4cf61246 |07197b4f90be3 |f7fbcd1e3fbbc --- Comment #9 from Kai Uwe Broulik --- Git commit 20e6c20de00e03ebb1c4cf61246f7fbcd1e3fbbc by Kai Uwe Broulik. Committed on 17/07/2024 at 20:48. Pushed by broulik into branch 'Plasma/5.27'. Folder Model: Handle invalid URL in desktop file There's no point in handling an invalid URL, and KProtocolInfo asserts that the scheme is not empty. (cherry picked from commit 0504f0e0ef2b0ebc4f1b1faa9ee8c74d2191931b) (cherry picked from commit 0264726f8720d3093bd3ba10f6107197b4f90be3) M +4-1containments/desktop/plugins/folder/foldermodel.cpp https://invent.kde.org/plasma/plasma-desktop/-/commit/20e6c20de00e03ebb1c4cf61246f7fbcd1e3fbbc -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 490416] battery applet does not open
https://bugs.kde.org/show_bug.cgi?id=490416 --- Comment #1 from Kai Uwe Broulik --- I have also seen this happening when it’s in the hidden applets popup. Not entirely sure how this happens, I think focussing it with keyboard still worked but clicking didn’t open it. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 486726] discover needs to include the fwupd version in the user agent
https://bugs.kde.org/show_bug.cgi?id=486726 Kai Uwe Broulik changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/discover/-/commit/33202c |ma/discover/-/commit/dfc07e |20e7fa28b20710f5a665e882683 |ea5aafd47ea213160c869d90dd9 |ac8a0d9 |b0d0bba --- Comment #5 from Kai Uwe Broulik --- Git commit dfc07eea5aafd47ea213160c869d90dd9b0d0bba by Kai Uwe Broulik. Committed on 16/07/2024 at 09:56. Pushed by broulik into branch 'Plasma/5.27'. FwupdBackend: Set user agent from client Ensures it include any information fwupd expects/sets, such as the fwupd version, distro version, in addition to our package version. (cherry picked from commit 3d5ad3e32c273000720738b834aa0aedd1f0b23a) (cherry picked from commit 33202c20e7fa28b20710f5a665e882683ac8a0d9) M +3-2libdiscover/backends/FwupdBackend/FwupdTransaction.cpp https://invent.kde.org/plasma/discover/-/commit/dfc07eea5aafd47ea213160c869d90dd9b0d0bba -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484323] High CPU load of kwin_x11 when locking or turning off the screen
https://bugs.kde.org/show_bug.cgi?id=484323 --- Comment #38 from Kai Krakow --- (In reply to Kai Krakow from comment #36) > Is this caused by the blur effects of plasma and konsole? It may have been resolved, at least partially, by https://github.com/NVIDIA/open-gpu-kernel-modules/commit/1795a8bb20fe09f9939ca3e82d76791f5741e467. It mentions KDE here: https://www.nvidia.com/Download/driverResults.aspx/228410/en-us/ I'm using the 555 driver, and since the update, high CPU usage /while/ using the system has gone down. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488941] Plasma 6.1 Screen turn off on login into a Wayland session if HDR is enabled
https://bugs.kde.org/show_bug.cgi?id=488941 Kai changed: What|Removed |Added Version|6.1.1 |6.1.2 CC||kai.uppenbr...@gmail.com --- Comment #22 from Kai --- Can confirm that the bug is still there. I have the Nvidia driver 555.58.02 KDE Plasma 6.1.2 OS is up to date. After login to KDE 6.1.2 + Wayland both monitors go into standby when HDR is activated. After deleting the file "~/.config/kwinoutputconfig.json" the login is possible. HDR is then deactivated. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 488653] plasma-browser-integration-host crashes in Firefox 127.0 after upgrade to Plasma 6.1
https://bugs.kde.org/show_bug.cgi?id=488653 Kai changed: What|Removed |Added CC||kn5i02...@mozmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488941] Plasma 6.1 Screen turn off on login into a Wayland session if HDR is enabled
https://bugs.kde.org/show_bug.cgi?id=488941 Kai changed: What|Removed |Added CC||m...@kmoschcau.de --- Comment #15 from Kai --- Hi, I can still reproduce this after just having upgraded the nvidia drivers from 555.58 to 555.58.02. I have `nvidia-drm.modeset=1` and `nvidia-drm.fbdev=1`. When I start into the Wayland session from SDDM with HDR enabled, I loose all display output and switching to a different tty no longer works. I can boot up to SDDM, switch to a different tty, disable HDR in `~/.config/kwinoutputconfig.json` and then just start the Wayland session no problem. Also enabling HDR when already in the session works. Operating System: EndeavourOS KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 Kernel Version: 6.9.7-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-9700K CPU @ 3.60GHz Memory: 31.2 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 2080/PCIe/SSE2 Manufacturer: Gigabyte Technology Co., Ltd. Product Name: Z390 AORUS MASTER -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 404057] Uses an insane amount of memory (RSS/PSS) writing a *ton* of data while re-indexing unchanged files
https://bugs.kde.org/show_bug.cgi?id=404057 --- Comment #51 from Kai Krakow --- (In reply to tagwerk19 from comment #50) > (In reply to Kai Krakow from comment #49) > > Thank you for the insights. That's a lot more to think about... You're welcome. > What we had previously, of BTRFS presenting "another different" device > number on reboot and Baloo's initial scan for changes not committing at > intervals, that was a catastrophic combination. I initiated the idea to fold the uuid into the dev/inode feels somehow, I just hadn't time exploring the source code. Luckily, someone finally implemented that idea. \o/ > I think, in *general*, > nowadays Baloo does not demand so much memory. Maybe though I should check > when a lot of files have been deleted and Baloo has to catch up. How Baloo > might behave when it is squeezed for memory (rather than being the culprit), > that's something new to think about... Yeah exactly. I think one remaining issue is when system performance suffers not because baloo uses too much memory but because it becomes squeezed into too little memory. Thanks for testing it. I'm currently running fine with `MemoryLow=512M` and no high limit, seems to work great so far even with games running and while streaming, using btrfs on bcache with hdds. With that configuration, more baloo memory has been pushed into swap - but it was never reclaimed so its probably inactive memory anyways and should be in swap. I'd recommend to look into the "below" tool (an alternative implementation to "atop"), it tracks memory usage via cgroups and thus can tell you also the accounted cache memory of a process group where "htop" or "top" only show resident process memory without caches accounted. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 404057] Uses an insane amount of memory (RSS/PSS) writing a *ton* of data while re-indexing unchanged files
https://bugs.kde.org/show_bug.cgi?id=404057 --- Comment #49 from Kai Krakow --- (In reply to tagwerk19 from comment #47) > That said, I've not noticed the percentages behaving differently than a > defined amount of memory (so, I think a "MemoryHigh=25%" on a 2GB system > acts the same as a "MemoryHigh=512M"). It would be interesting if this was > not the case... No, it should not be different. In the end, it boils down to fixed numbers as can be seen in `systemctl --user status kde-baloo.service`: # Memory: 136.4M (high: 2.0G available: 1.8G peak: 1.3G swap: 18.4M swap peak: 18.5M zswap: 6.9M) (where "high" is calculated from percentage to this number) > I'm pretty sure the "MemoryHigh" is a soft limit, I was able to push the > usage to just a little above the given limit but the process slowed down > (markedly, when I pushed hard), I think when trying to claim more memory. MemoryHigh is not a limit. MemoryHigh is an indicator/hint for the kernel beyond which value the process group is considered to use a high amount of memory. Now, if the kernel needs memory, it will reclaim memory from process groups first that are most above their "MemoryHigh" value. Thus, if you make this very high, the kernel will decide to reclaim memory from baloo last because it is potentially the only service with a very high "MemoryHigh" value. The service is allowed to go beyond that memory usage just fine as long as the kernel has no need for other memory. This is also a problem in itself if mixing non-memory constrained services with ones that have this setting. The system becomes very unbalanced unless you adjust it for your very own needs. Leaving `MemoryHigh` empty instructs cgroups to balance memory usage in a fair way. > I > tried the same with MemoryMax but this seemed to be a hard limit. Yes, it is a hard limit. Allocations beyond `MemoryMax` will force the process group to swap out inactive memory of itself. > I tried > setting a MemoryHigh with a slightly higher MemoryMax but it didn't seem to > bring any benefits, the MemoryHigh on its own seemed to be quite effective > at limiting Baloo's memory use. Cannot work. `MemoryHigh` is not a limit, it's a hint for the memory management when to consider a service to use "too much" memory, so services beyond that allocation will be considered for reclaim first. Or viewed from the other side: `MemoryHigh` is a type of resident memory protection which the kernel _tries_ to guarantee to the service (`MemoryMin` will force the guarantee). > I'm also pretty sure that even with a defined MemoryHigh, Baloo releases > memory when other processes require it. Yes, because it's a "soft guarantee", not a "soft limit". If the kernel has no more other processes to reclaim memory from, it will start reclaiming memory from `MemoryHigh` services below their setting, in order of priority that makes sense in that context. Baloo itself surely will free memory, too, by itself, and that's reflected here. Those memory allocations also include cache which baloo cannot directly control. The kernel tracks page cache ownership per cgroup, and accounts that to memory usage, too. I'm pretty sure `MemoryHigh` has been set so low (512M) because someone considered it a soft limit, but it's a soft guarantee. And setting it too low will hint the kernel to reclaim memory from such processes first - and that's usually cache before swapping memory out (depends on vm.swappiness). Thus, `MemoryHigh` should be set to a proper value that includes the active working set of memory pages for the process + a good value for cache to let it do it's job without stuttering the desktop. That settles around 1.5G of memory for me. But OTOH, that means, we will also protect its memory even if baloo is idle (and may be fine with using less than 1.5G RAM including caches). Thus I think, it may be a better idea to completely leave that value empty, maybe only include it as a comment with explanation so users can tune it easily with `systemctl --user edit kde-baloo.service`. > Certainly, there was dropping and rereading of clean pages when Baloo was > closing on the limit. That was visible in iotop. I noticed in "pathological > cases", indexing large quantities of data and having to manage very many > dirty pages, pushed Baloo to swap and performance very clearly suffered > (even when the rest of the system has sufficient space). I think it's > (likely) worthwhile adding the MemorySwapMax=0 for Baloo to stop it reaching > that point (although only if MemoryHigh is reasonable). The argument being > an OOM for Baloo is (likely) better than it swapping. This is a value > judgement through... `MemoryHigh` is a two-edged sword... You can stop the observed behavior by using a high valu
[kwin] [Bug 489556] New: When screen timer is allowed to run out and auto lock, brightness is turned down
https://bugs.kde.org/show_bug.cgi?id=489556 Bug ID: 489556 Summary: When screen timer is allowed to run out and auto lock, brightness is turned down Classification: Plasma Product: kwin Version: 6.1.1 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: kaiwin...@gmail.com Target Milestone: --- SUMMARY Allow Plasma to auto-timeout so the screen becomes locked, the brightness gets turned down and once you log in, there is no way to turn the brightness back up. You have to reboot for the controls to become available again STEPS TO REPRODUCE 1. Plasma 6.1.1, allow timeout so it locks the screen 2. Once the locked screen is shown, login 3. Go to settings > Power Management 4. No way of adjusting the screen brightness as Power Management is blank EXPECTED RESULT Ability to change screen brightness as before 6.x update ADDITIONAL INFORMATION Operating System: Alpine Linux 3.21.0_alpha20240606 KDE Plasma Version: 6.1.1 KDE Frameworks Version: 6.3.0 Qt Version: 6.6.3 Kernel Version: 6.6.36-0-lts (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-7700 CPU @ 3.60GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 404057] Uses an insane amount of memory (RSS/PSS) writing a *ton* of data while re-indexing unchanged files
https://bugs.kde.org/show_bug.cgi?id=404057 --- Comment #46 from Kai Krakow --- (In reply to tagwerk19 from comment #45) > Yes, there's been a handful of bug reports where I've "blamed" the 512M > limit. > > I tentatively recommend "MemoryHigh=25%". I don't suppose many people run on > systems with 2G RAM (even as VM's) and having a percentage means Baloo gets > a lot more room to breath on systems with 8G. > > I think "MemoryHigh=40%" is still quite reasonable and I would also include > a "MemorySwapMax=0" to forestall swapping (which does seem to cause problems) MemorySwapMax can lead to OOM situations, even for other processes, if the only swap victim would be baloo. It is fine to swap out some dead pages which the process never uses. And we should be careful with percentages: `MemoryHigh` sets a priority at which the kernel memory manager chooses processes to reduce memory usage (by discard caches, flushing writeback, or swapping anonymous memory). We actually want this to happen, we should be careful to not make baloo the last resort by accidentally giving it the highest memory priority. If we want to limit it, `MemoryMax` should be set (then baloo will never get more memory). But `MemoryHigh` should be set to a reasonable minimum we want to protect for the process so it can make forward progress. Setting it too high creates an inverse effect for other important processes of the desktop. It the lower bound of what is considered high memory usage before making memory available to other processes. Memory is taken away from processes with the highest `MemoryHigh` last. As an idea, baloo could watch `/proc/pressure/memory` and if latencies go high, it could pause for a while and flush its own caches. One cannot try to emulate such a behavior with `MemoryHigh`. Maybe the memory limits should be removed completely, and rather let the kernel do the job using mgLRU (which could be recommended for distributions if it works fine), and then let baloo watch memory pressure instead to throttle itself. The problem is not with baloo reading files and using CPU, it's already highly optimized here. The problem is with how the database uses memmap, so it's directly competing with important desktop processes needing resident memory (it's not designed to compete with other processes for memory). Using memory pressure, we could mark selected memory ranges as "not needed" and flush unwritten data early so it becomes available. I had no more problems with baloo until it added the `MemoryHigh=512M` parameter, so I added another one to force 2G instead. Which makes me wonder if we need that parameter at all. Just my 2 cents, no need to re-open. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 404057] Uses an insane amount of memory (RSS/PSS) writing a *ton* of data while re-indexing unchanged files
https://bugs.kde.org/show_bug.cgi?id=404057 --- Comment #44 from Kai Krakow --- (In reply to tagwerk19 from comment #43) > I think the dust has probably settled here after: > https://invent.kde.org/frameworks/baloo/-/merge_requests/131 > and cherrypicked for KF5 > https://invent.kde.org/frameworks/baloo/-/merge_requests/169 These work fine for me, I'm actually using baloo again in production. > There's also been > https://invent.kde.org/frameworks/baloo/-/merge_requests/121 Actually, `MemoryHigh=512M` is quite aggressive. It can lead to swap storms and cache thrashing of baloo under memory pressure because the process itself is already 512M big, this leaves no space for caching which is important for baloo to work with proper performance (consider that memory cgroups also account cache usage). Especially the sub process baloo_file is hurt by this a lot while indexing new files. I personally used `MemoryHigh=2G` to fix this for my system - but this parameter really depends a lot on the system environment. The service shows a peak usage of 1.3G with almost no swap usage (less than 30M), so `MemoryHigh=1536M` may be fine. > and > https://invent.kde.org/frameworks/baloo/-/merge_requests/148 No objections, it makes sense. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484323] High CPU load of kwin_x11 when locking or turning off the screen
https://bugs.kde.org/show_bug.cgi?id=484323 Kai Krakow changed: What|Removed |Added CC||k...@kaishome.de --- Comment #36 from Kai Krakow --- I can confirm this for 6.1.1. I'm using 4 monitors, one of them is sometimes turned off. Perf data looks like this: # Overhead Command Shared ObjectSymbol # ... ... ... # 24.22% kwin_x11 [vdso] [.] __vdso_clock_gettime 15.66% kwin_x11 libc.so.6[.] __sched_yield 10.43% kwin_x11 [unknown][k] 0x81c00150 1.71% kwin_x11 libc.so.6[.] clock_gettime@@GLIBC_2.17 1.46% kwin_x11 libnvidia-glcore.so.555.58 [.] 0x00b00d13 1.24% kwin_x11 libnvidia-glcore.so.555.58 [.] 0x00b00d00 1.02% kwin_x11 libnvidia-glcore.so.555.58 [.] 0x009eea66 0.78% kwin_x11 libnvidia-glcore.so.555.58 [.] 0x009eea61 0.72% kwin_x11 libnvidia-glcore.so.555.58 [.] 0x00a03904 0.71% kwin_x11 libnvidia-glcore.so.555.58 [.] 0x00b00d30 0.68% kwin_x11 libnvidia-glcore.so.555.58 [.] 0x009eea59 It looks like most of the time is spent in a tight loop getting the clock and yielding. Most of the time is spent outside of kwin_x11 but filtering by dso shows where it is involved: # dso: kwin_x11 # # Total Lost Samples: 0 # # Samples: 5K of event 'cpu_atom/cycles/Pu' # Event count (approx.): 2421254389 # # Overhead Command Symbol # ... ... # 0.12% kwin_x11 [.] KWin::BlendChanges::isActive 0.07% kwin_x11 [.] QtPrivate::QCallableObject, void>::impl 0.04% kwin_x11 [.] KWin::OutputFrame::presented@plt 0.03% vsync event mon [.] std::chrono::_V2::steady_clock::now@plt 0.03% kwin_x11 [.] KWin::ApplicationX11::metaObject 0.03% kwin_x11 [.] KWin::ContrastEffect::shouldContrast 0.03% kwin_x11 [.] KWin::ContrastEffect::doContrast 0.02% kwin_x11 [.] KWin::ZoomEffect::slotWindowDamaged 0.02% kwin_x11 [.] KWin::GlxLayer::doBeginFrame 0.02% kwin_x11 [.] KWin::PaintData::yTranslation@plt 0.02% kwin_x11 [.] KWin::BlurEffect::blurRegion 0.02% kwin_x11 [.] KWin::EffectsHandler::prePaintScreen@plt 0.02% kwin_x11 [.] KWin::ContrastEffect::isActive 0.02% kwin_x11 [.] KWin::EffectWindow::isDesktop@plt 0.02% kwin_x11 [.] KWin::ContrastEffect::drawWindow 0.02% kwin_x11 [.] KWin::GlxBackend::primaryLayer 0.02% kwin_x11 [.] KWin::SlideEffect::isActive 0.02% kwin_x11 [.] QRegion::end@plt 0.02% vsync event mon [.] KWin::SGIVideoSyncVsyncMonitorHelper::poll 0.02% kwin_x11 [.] KWin::OutputLocatorEffect::isActive 0.01% vsync event mon [.] operator delete@plt 0.01% kwin_x11 [.] KWin::GlxBackend::makeCurrent 0.01% vsync event mon [.] QMetaObject::activate@plt 0.00% vsync event mon [.] QtPrivate::QCallableObject, void>::impl # Samples: 1M of event 'cpu_core/cycles/Pu' # Event count (approx.): 737751025988 # # Overhead Command Symbol # ... . . # 0.01% kwin_x11 [.] KWin::BlurEffect::blurRegion 0.00% kwin_x11 [.] KWin::GlxBackend::present 0.00% kwin_x11 [.] KWin::BlurEffect::prePaintWindow 0.00% kwin_x11 [.] QRegion::~QRegion@plt 0.00% kwin_x11 [.] KWin::BlurEffect::blur 0.00% kwin_x11 [.] KWin::GlxBackend::present 0.00% kwin_x11 [.] KWin::GlxBackend::doBeginFrame 0.00% kwin_x11 [.] KWin::GlxContext::makeCurrent 0.00% vsync event mon [.] KWin::SGIVideoSyncVsyncMonitorHelper::poll 0.00% vsync event mon [.] std::chrono::_V2::steady_clock::now@plt 0
[frameworks-kconfig] [Bug 187172] truncated configuration files on power loss or hard crash
https://bugs.kde.org/show_bug.cgi?id=187172 --- Comment #47 from Kai Krakow --- (In reply to Martin Steigerwald from comment #46) > Nowadays where Ext3 should not be in wide use anymore, if at all, and > nowadays where many people use flash based storage, I am strongly for just > making sure to sync where needed. > > That written, I did not see any truncated config file since ages. I still > have "KDE_EXTRA_FSYNC=1" set, but whether this actually really makes a > difference, given some of the comments above, I do not know. Anyway, I'd > just sync by default. It really can't be a performance issue anymore – > except maybe on embedded device with some slow SD card –, especially as > unchanged files are not rewritten anymore. If I remember correctly, you may be using btrfs. On btrfs, this is actually not needed, it works fine without fsync and is actually faster that way no matter the storage technology. I'm running with `KDE_EXTRA_FSYNC=0` since years on btrfs and never had a problem. I suggest that the behavior is kept to optionally disable fsync/fdatasync, but it should befault to "on". The problem is with file systems which do not commit metadata and data properly in a single transaction or in expected order, e.g. xfs does this and writes data lazily or delayed. In that case, xfs ensures that you do not see stale or old data after a crash by zeroing or truncating the affected files. I think ext3/ext4 does something similar unless you use its full journal mode (which is a lot slower, ofc), where xfs probably behaves like ext4 with "journal=writeback". Especially with btrfs, the argument is not whether it's on flash or spinning disks: fsync/fdatasync can significantly slow the system down because btrfs may have a rather long list of outstanding transactions it would have to write then (blocking) until reaching the transaction affected by the sync. This can take a long time and blocks the system even on flash disks. So if this discussion is about whether we should remove `KDE_EXTRA_FSYNC`, I'd rather not have it force-enabled, especially because KDE seems to be very busy with its config files and reads and writes them a lot (similar to the cache directory). IMHO, the variable could be changed to require `KDE_DISABLE_EXTRA_FSYNC=this_is_dangerous_and_I_know_what_I_am_doing`. This may make it more obvious to people who blindly follow some internet guides to "make things faster" that they may be doing something harmful. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477017] Plasma is not properly rendered when using an ICC profile and both the contrast and blur effects
https://bugs.kde.org/show_bug.cgi?id=477017 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #16 from Kai Uwe Broulik --- *** Bug 487679 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487679] Blur effect broken
https://bugs.kde.org/show_bug.cgi?id=487679 Kai Uwe Broulik changed: What|Removed |Added Resolution|WAITINGFORINFO |DUPLICATE Status|NEEDSINFO |RESOLVED --- Comment #3 from Kai Uwe Broulik --- Looks like Bug 477017 if I disable "Color profile" (even though I did not have one set) the glitches went away *** This bug has been marked as a duplicate of bug 477017 *** -- 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 #30 from Kai Uwe Broulik --- Patch has just been merged into Qt 6.8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 487679] New: Blur effect broken
https://bugs.kde.org/show_bug.cgi?id=487679 Bug ID: 487679 Summary: Blur effect broken Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: k...@privat.broulik.de Target Milestone: --- Created attachment 169906 --> https://bugs.kde.org/attachment.cgi?id=169906&action=edit Weird transparency during animation SUMMARY For a few weeks the blur effect is broken for me, it just renders completely black, disregarding the window mask and flickering during sliding popups effect, where you can see some diagonal tiling of black during the animation. STEPS TO REPRODUCE 1. Have blur contrast effect enabled 2. Open KRunner or Kickoff OBSERVED RESULT There’s black flickering during the animation and when it finished you can see that the corners around KRunner are black. Also affects other plasma popups EXPECTED RESULT No flickering, beautiful rendering ;) SOFTWARE/OS VERSIONS Linux/KDE Plasma: git master as of 2024-05-25 on Intel UHD 620 GPU Qt version: 6.7.0 ADDITIONAL INFORMATION When I took a screenshot during the animation I could see that the resulting output was completely transparent, maybe there’s some blending issue there that it ends up “punching through” to the root plane which is black and then you see it through. Whatever the case, it’s completely borked right now. -- 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 --- Comment #13 from Kai Uwe Broulik --- Git commit ee2584eca783947a5013d8a7ff15a492dc6b357b by Kai Uwe Broulik. Committed on 25/05/2024 at 14:06. Pushed by broulik into branch 'master'. Namespace custom event types They can clash with website otherwise. M +4-4extension/content-script.js M +5-5extension/page-script.js https://invent.kde.org/plasma/plasma-browser-integration/-/commit/ee2584eca783947a5013d8a7ff15a492dc6b357b -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 486506] Firefox (Flatpak) does not inhibit power management when playing videos
https://bugs.kde.org/show_bug.cgi?id=486506 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #6 from Kai Uwe Broulik --- Perhaps the sandbox prevents it from working properly like it breaks Plasma Browser Integration, too -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486665] Plasmashell crashes randomly
https://bugs.kde.org/show_bug.cgi?id=486665 Kai Uwe Broulik changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/-/commi ||t/bf8545946cc340c262911c0ba ||94e28661a7feb8a Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #3 from Kai Uwe Broulik --- Git commit bf8545946cc340c262911c0ba94e28661a7feb8a by Kai Uwe Broulik. Committed on 14/05/2024 at 12:30. Pushed by broulik into branch 'master'. Notifications: Restore custom DragHelper When the notification popup closes, the ListView mode is unloaded to save some resources. On Wayland, during drag and drop another window might be raised and focussed causing the notification popup to close. QtQuick's built-in drag handling does not take kind to having the item it's operating on destroyed behind its back, particularly because it uses a freaking' nested event loop inside of dragStarted! Restore the original DragHandler which detaches the drag operation entirely from the item that triggered it. It also creates a proper drag pixmap for dragging the file icon and keeps it for the entire duration of the drag. As a bonus this also lets us export the URL to the Document portal to enable drag and drop of thumbnails to sandboxed apps. Related: bug 484546 M +3-0applets/notifications/CMakeLists.txt A +84 -0applets/notifications/draghelper.cpp [License: GPL(3+eV) GPL(v3.0) GPL(v2.0)] A +42 -0applets/notifications/draghelper.h [License: GPL(3+eV) GPL(v3.0) GPL(v2.0)] M +4-0applets/notifications/notificationapplet.cpp M +10 -9applets/notifications/package/contents/ui/DraggableFileArea.qml M +2-5applets/notifications/package/contents/ui/JobItem.qml M +2-5applets/notifications/package/contents/ui/ThumbnailStrip.qml https://invent.kde.org/plasma/plasma-workspace/-/commit/bf8545946cc340c262911c0ba94e28661a7feb8a -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 484546] Plasma crashes when drag'n'dropping file from notifications menu
https://bugs.kde.org/show_bug.cgi?id=484546 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/-/commi ||t/bf8545946cc340c262911c0ba ||94e28661a7feb8a --- Comment #2 from Kai Uwe Broulik --- Git commit bf8545946cc340c262911c0ba94e28661a7feb8a by Kai Uwe Broulik. Committed on 14/05/2024 at 12:30. Pushed by broulik into branch 'master'. Notifications: Restore custom DragHelper When the notification popup closes, the ListView mode is unloaded to save some resources. On Wayland, during drag and drop another window might be raised and focussed causing the notification popup to close. QtQuick's built-in drag handling does not take kind to having the item it's operating on destroyed behind its back, particularly because it uses a freaking' nested event loop inside of dragStarted! Restore the original DragHandler which detaches the drag operation entirely from the item that triggered it. It also creates a proper drag pixmap for dragging the file icon and keeps it for the entire duration of the drag. As a bonus this also lets us export the URL to the Document portal to enable drag and drop of thumbnails to sandboxed apps. Related: bug 486665 M +3-0applets/notifications/CMakeLists.txt A +84 -0applets/notifications/draghelper.cpp [License: GPL(3+eV) GPL(v3.0) GPL(v2.0)] A +42 -0applets/notifications/draghelper.h [License: GPL(3+eV) GPL(v3.0) GPL(v2.0)] M +4-0applets/notifications/notificationapplet.cpp M +10 -9applets/notifications/package/contents/ui/DraggableFileArea.qml M +2-5applets/notifications/package/contents/ui/JobItem.qml M +2-5applets/notifications/package/contents/ui/ThumbnailStrip.qml https://invent.kde.org/plasma/plasma-workspace/-/commit/bf8545946cc340c262911c0ba94e28661a7feb8a -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480693] Major memory leak when changing wallpapers
https://bugs.kde.org/show_bug.cgi?id=480693 --- Comment #12 from Kai Uwe Broulik --- But I cannot reproduce it rising as I change wallpapers -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 480693] Major memory leak when changing wallpapers
https://bugs.kde.org/show_bug.cgi?id=480693 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #11 from Kai Uwe Broulik --- Yup, I am seeing a 60 MiB leak in heaptrack in the wallpaper stuff... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486810] Some settings pages are missing
https://bugs.kde.org/show_bug.cgi?id=486810 --- Comment #4 from Kai Uwe Broulik --- ~/.cache, not ~/.config -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486810] Some settings pages are missing
https://bugs.kde.org/show_bug.cgi?id=486810 --- Comment #3 from Kai Uwe Broulik --- Try removing ~/.config/systemsettings and see if the problem goes away. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486810] Some settings pages are missing
https://bugs.kde.org/show_bug.cgi?id=486810 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #2 from Kai Uwe Broulik --- This usually goes away when I clear the relevant QML cache suggesting there’s an issue with Qt’s qml module qmlcachegen situation. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 486813] Many error messages because a not existing item could not be deleted
https://bugs.kde.org/show_bug.cgi?id=486813 Kai changed: What|Removed |Added CC||kn5i02...@mozmail.com -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 486813] New: Many error messages because a not existing item could not be deleted
https://bugs.kde.org/show_bug.cgi?id=486813 Bug ID: 486813 Summary: Many error messages because a not existing item could not be deleted Classification: Applications Product: kmail2 Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: kn5i02...@mozmail.com Target Milestone: --- Created attachment 169344 --> https://bugs.kde.org/attachment.cgi?id=169344&action=edit Screenshot of error messages SUMMARY Sometimes my complete desktop gets filled with error messages, because a not existing calendar item can not be deleted. Even though the logs suggest that this is a problem with the calendar synchronization I opened this bug for kmail because the error messages belong to kmail. OBSERVED RESULT Sometimes my complete desktop gets filled with error messages, because a not existing calendar item can not be deleted. These windows open almost simultaneously. I have collected the following output from the log files and attached a screenshot of the error messages. ``` 09/05/2024 15:08kioworker Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8. Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead. If this causes problems, reconfigure your locale. See the locale(1) manual for more information. 09/05/2024 15:08akonadi_davgroupware_resource org.kde.pim.davresource: Unable to fetch collections 320 "Invalid responses from backend" 09/05/2024 15:08kioworker Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8. Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead. If this causes problems, reconfigure your locale. See the locale(1) manual for more information. 09/05/2024 15:08akonadiserver org.kde.pim.akonadiserver: Error while handling command DeleteItems on connection kalendarac-1686444273 (0x57b8ac82a020) 09/05/2024 15:08kalendarac "No items found" 09/05/2024 15:08kmail "No items found" 09/05/2024 15:08akonadiserver org.kde.pim.akonadiserver: Error while handling command DeleteItems on connection kmail2-3365511548 (0x57b8ac82ac00) 09/05/2024 15:08kalendarac "No items found" 09/05/2024 15:08akonadiserver org.kde.pim.akonadiserver: Error while handling command DeleteItems on connection kalendarac-1686444273 (0x57b8ac82a020) 09/05/2024 15:08akonadiserver org.kde.pim.akonadiserver: Error while handling command DeleteItems on connection kmail2-3365511548 (0x57b8ac82ac00) 09/05/2024 15:08kmail "No items found" 09/05/2024 15:08kalendarac "No items found" 09/05/2024 15:08akonadiserver org.kde.pim.akonadiserver: Error while handling command DeleteItems on connection kalendarac-1686444273 (0x57b8ac82a020) 09/05/2024 15:08kmail "No items found" 09/05/2024 15:08akonadiserver org.kde.pim.akonadiserver: Error while handling command DeleteItems on connection kmail2-3365511548 (0x57b8ac82ac00) 09/05/2024 15:08kalendarac org.kde.pim.akonadicalendar: CalendarBase::internalRemove2: incidence is null, item.id= "22399; summary=Test; uid=12cf5e7b-d84d-46cf-8814-dfc799e82732; type=0; recurs=0; recurrenceId=Tue May 24 14:00:00 2022 UTC+02:00; dtStart=Tue May 24 14:00:00 2022 UTC+02:00; dtEnd=Tue May 24 14:01:00 2022 UTC+02:00; parentCollection=339" 09/05/2024 15:08kalendarac org.kde.pim.akonadicalendar: CalendarBase::internalRemove2: incidence is null, item.id= "22611; summary=Test; uid=14504994-2727-46f0-8bb7-bc88df40a095; type=0; recurs=0; recurrenceId=; dtStart=Mon Mar 6 19:30:42 2023 UTC+01:00; dtEnd=Mon Mar 6 22:30:42 2023 UTC+01:00; parentCollection=339" 09/05/2024 15:08kmail org.kde.pim.akonadicalendar: CalendarBase::internalRemove2: incidence is null, item.id= "22399; summary=Test; uid=12cf5e7b-d84d-46cf-8814-dfc799e82732; type=0; recurs=0; recurrenceId=Tue May 24 14:00:00 2022 UTC+02:00; dtStart=Tue May 24 14:00:00 2022 UTC+02:00; dtEnd=Tue May 24 14:01:00 2022 UTC+02:00; parentCollection=339" 09/05/2024 15:08kmail org.kde.pim.akonadicalendar: CalendarBase::internalRemove2: incidence is null, item.id= "22611; summary=Test; uid=14504994-2727-46f0-8bb7-bc88df40a095; type=0; recurs=0; recurrenceId=; dtStart=Mon Mar 6 19:30:42 2023 UTC+01:00; dtEnd=Mon Mar 6 22:30:42 2023 UTC+01:00; parentCollection=339" 09/05/2024 15:08kmail "No items found" 09/05/2024 15:08akonadiserver org.kde.pim.akonadiserver: Error while handling command DeleteItems on connection kmail2-3365511548 (0x57b8ac82ac00) 09/05/2024 15:08kalendarac org.kde.pim.akonadicalendar: CalendarBase::internalRemove2: incidence is null, item.id= "22685; summary=Test; uid=19289d68-3995-4786-bc3d
[Discover] [Bug 486726] discover needs to include the fwupd version in the user agent
https://bugs.kde.org/show_bug.cgi?id=486726 Kai Uwe Broulik changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/discover/-/commit/3d5ad3 |ma/discover/-/commit/33202c |e32c273000720738b834aa0aedd |20e7fa28b20710f5a665e882683 |1f0b23a |ac8a0d9 --- Comment #3 from Kai Uwe Broulik --- Git commit 33202c20e7fa28b20710f5a665e882683ac8a0d9 by Kai Uwe Broulik. Committed on 08/05/2024 at 06:29. Pushed by broulik into branch 'Plasma/6.0'. FwupdBackend: Set user agent from client Ensures it include any information fwupd expects/sets, such as the fwupd version, distro version, in addition to our package version. (cherry picked from commit 3d5ad3e32c273000720738b834aa0aedd1f0b23a) M +3-2libdiscover/backends/FwupdBackend/FwupdTransaction.cpp https://invent.kde.org/plasma/discover/-/commit/33202c20e7fa28b20710f5a665e882683ac8a0d9 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 486726] discover needs to include the fwupd version in the user agent
https://bugs.kde.org/show_bug.cgi?id=486726 Kai Uwe Broulik changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/discover/-/commit/3d5ad3 ||e32c273000720738b834aa0aedd ||1f0b23a Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Kai Uwe Broulik --- Git commit 3d5ad3e32c273000720738b834aa0aedd1f0b23a by Kai Uwe Broulik. Committed on 08/05/2024 at 06:22. Pushed by broulik into branch 'master'. FwupdBackend: Set user agent from client Ensures it include any information fwupd expects/sets, such as the fwupd version, distro version, in addition to our package version. M +3-2libdiscover/backends/FwupdBackend/FwupdTransaction.cpp https://invent.kde.org/plasma/discover/-/commit/3d5ad3e32c273000720738b834aa0aedd1f0b23a -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 486743] Notifications leak memory
https://bugs.kde.org/show_bug.cgi?id=486743 --- Comment #1 from Kai Uwe Broulik --- I had a quick look with hotspot and it seems like there’s a leak in QRhi somewhere. Seems every window gets its own RHI instance with its own glyph cache which is then leaked. Alas, I haven’t managed to figure out where it comes from or what the remedy would be, or if that’s even the case, or why it only really shows with notifications (I doubt it’s only notifications but they create a new window every time). for reference the leak stack in heaptrack: 2,7MB (33.2%) contribution to peak consumption in QRhi::nextResourceUpdateBatch() in libQt6Gui.so.6 and below. 2,7MB (33.2%) contribution to peak consumption in QSGDefaultRenderContext::glyphCacheResourceUpdates() in libQt6Quick.so.6 and below. 2,7MB (33.2%) contribution to peak consumption in QSGRhiTextureGlyphCache::createEmptyTexture(QRhiTexture::Format) in libQt6Quick.so.6 and below. 2,7MB (33.2%) contribution to peak consumption in QSGRhiTextureGlyphCache::endFillTexture() in libQt6Quick.so.6 and below. 2,8MB (34.5%) contribution to peak consumption in QTextureGlyphCache::fillInPendingGlyphs() in libQt6Gui.so.6 and below. 2,8MB (34.9%) contribution to peak consumption in QSGTextMaskMaterial::populate(QPointF const&, QList const&, QList const&, QSGGeometry*, QRectF*, QPointF*, QMargins const&) in libQt6Quick.so.6 and below. 2,8MB (35%) contribution to peak consumption in QSGDefaultGlyphNode::update() in libQt6Quick.so.6 and below. 2,8MB (35.1%) contribution to peak consumption in QSGInternalTextNode::addGlyphs(QPointF const&, QGlyphRun const&, QColor const&, QQuickText::TextStyle, QColor const&, QSGNode*) in libQt6Quick.so.6 and below. 2,8MB (35.1%) contribution to peak consumption in QQuickTextNodeEngine::addToSceneGraph(QSGInternalTextNode*, QQuickText::TextStyle, QColor const&) in libQt6Quick.so.6 and below. 2,8MB (35.1%) contribution to peak consumption in QSGInternalTextNode::doAddTextLayout(QPointF, QTextLayout*, int, int, int, int) in libQt6Quick.so.6 and below. 2,8MB (35.1%) contribution to peak consumption in QSGTextNode::addTextLayout(QPointF, QTextLayout*, int, int, int, int) in libQt6Quick.so.6 and below. 2,9MB (35.6%) contribution to peak consumption in QQuickText::updatePaintNode(QSGNode*, QQuickItem::UpdatePaintNodeData*) in libQt6Quick.so.6 and below. 3,0MB (37.5%) contribution to peak consumption in QQuickWindowPrivate::updateDirtyNode(QQuickItem*) in libQt6Quick.so.6 and below. 3,0MB (37.6%) contribution to peak consumption in QQuickWindowPrivate::updateDirtyNodes() in libQt6Quick.so.6 and below. 3,1MB (38%) contribution to peak consumption in QQuickWindowPrivate::syncSceneGraph() in libQt6Quick.so.6 and below. 3,1MB (38%) contribution to peak consumption in QSGRenderThread::sync(bool) in libQt6Quick.so.6 and below. 5,6MB (69.6%) contribution to peak consumption in QSGRenderThread::syncAndRender() in libQt6Quick.so.6 and below. 7,1MB (88.2%) contribution to peak consumption in QSGRenderThread::run() in libQt6Quick.so.6 and below. 7,1MB (88.2%) contribution to peak consumption in terminate_on_exception >::operator() in libQt6Core.so.6 and below. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 486558] No notification sounds on Kubuntu 24.04 (minimal installation)
https://bugs.kde.org/show_bug.cgi?id=486558 Kai Uwe Broulik changed: What|Removed |Added Status|REPORTED|RESOLVED CC||k...@privat.broulik.de Resolution|--- |NOT A BUG --- Comment #4 from Kai Uwe Broulik --- There is currently no “default” notification sound handling. A simple notify-send will not play anything. KDE apps play the sound they deem appropriate for the given event which can be a generic ”Notification” but doesn’t have to. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 486657] volume decreases when mixer popup hides
https://bugs.kde.org/show_bug.cgi?id=486657 Kai Uwe Broulik changed: What|Removed |Added Component|general |general Product|plasmashell |plasma-pa CC||isma...@gmail.com, ||k...@privat.broulik.de, ||m...@ratijas.tk Target Milestone|1.0 |--- --- Comment #1 from Kai Uwe Broulik --- Likely the volume monitors. We install a monitor on all streams to show the live output/input peak. This might cause a headset to switch modes (e.g. from high fidelity audio output to handsfree output + microphone). Might have other effects, too. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475922] kwin_wayland freeze loop on DisplayLink connection
https://bugs.kde.org/show_bug.cgi?id=475922 --- Comment #20 from Kai Uwe Broulik --- If anyone experiencing this bug could test the above merge request that would be appreciated. I cannot reproduce the issue on my DisplayLink docking station so I’m wary of merging it without having verified it actually fixes the issue (and doesn’t make things worse) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 485455] Audio indicators missing
https://bugs.kde.org/show_bug.cgi?id=485455 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/libr ||aries/pulseaudio-qt/-/commi ||t/9a09133fb368ba400e5748dcf ||88a32a478d44ea0 Status|ASSIGNED|RESOLVED --- Comment #2 from Kai Uwe Broulik --- Git commit 9a09133fb368ba400e5748dcf88a32a478d44ea0 by Kai Uwe Broulik. Committed on 01/05/2024 at 08:28. Pushed by broulik into branch 'master'. Stream: Fix client In pulseaudio-qt, client is a *list*, unlike plasma-pa where it was a map where the PulseAudio index was used as key. Fix it by looking for the client in the given list instead. M +8-1src/stream.cpp https://invent.kde.org/libraries/pulseaudio-qt/-/commit/9a09133fb368ba400e5748dcf88a32a478d44ea0 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 485507] Unspecified Error With LUKS Encrypted Removable Drives
https://bugs.kde.org/show_bug.cgi?id=485507 Kai Uwe Broulik changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/fram ||eworks/solid/-/commit/9ecaf ||388ccd41d2831ab3833c26627f7 ||2ab78f40 --- Comment #15 from Kai Uwe Broulik --- Git commit 9ecaf388ccd41d2831ab3833c26627f72ab78f40 by Kai Uwe Broulik. Committed on 17/04/2024 at 10:55. Pushed by broulik into branch 'master'. udisks: Return empty string for "root" clearTextPath There cannot be an empty object path on DBus, so "/" is used to denote no clear text device. Return empty string explicitly here to avoid littering even more places with empty || "/" checks. M +5-1src/solid/devices/backends/udisks2/udisksstorageaccess.cpp https://invent.kde.org/frameworks/solid/-/commit/9ecaf388ccd41d2831ab3833c26627f72ab78f40 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 485437] Powerdevil restricts the minimum monitor brightness to 1%, causing it to be unable to reach the lowest possible brightness
https://bugs.kde.org/show_bug.cgi?id=485437 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #1 from Kai Uwe Broulik --- You can still use the brightness keys to go to 0%? -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 484892] Rectangular selection unusably slow
https://bugs.kde.org/show_bug.cgi?id=484892 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #6 from Kai Uwe Broulik --- Can confirm on Qt 6.7. Not entirely sure what changed but changing the scale to 1,1 fixes it for me [1]. Probably just one link in the chain that gets broken and then it stops this loop but of course looks a bit broken then [1] https://invent.kde.org/graphics/spectacle/-/blob/master/src/Gui/Handle.qml?ref_type=heads#L166 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460819] Dialog Parent does not dim parent window on Wayland
https://bugs.kde.org/show_bug.cgi?id=460819 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #9 from Kai Uwe Broulik --- Qt has been merged, so has KWin. So on Plasma 6.1 with Qt 6.8 it should work. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465031] Plasma crashed after disconnecting Bluetooth device
https://bugs.kde.org/show_bug.cgi?id=465031 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #3 from Kai Uwe Broulik --- https://codereview.qt-project.org/c/qt/qtdeclarative/+/536727 wonder if this helps -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483985] plasmashell crashes in QQuickAccessibleAttached::setRole
https://bugs.kde.org/show_bug.cgi?id=483985 Kai Uwe Broulik changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM CC||k...@privat.broulik.de --- Comment #3 from Kai Uwe Broulik --- Qt bug: https://codereview.qt-project.org/c/qt/qtdeclarative/+/551356 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475922] kwin_wayland freeze loop on DisplayLink connection
https://bugs.kde.org/show_bug.cgi?id=475922 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #19 from Kai Uwe Broulik --- Possible workaround: https://invent.kde.org/plasma/kwin/-/merge_requests/5513 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 457894] DKIM plugin treats ed25119 signed messages as invalid
https://bugs.kde.org/show_bug.cgi?id=457894 Kai Bojens changed: What|Removed |Added CC||k...@kbojens.de -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 483487] Kate crash clicking on "empty" horizontal scroll bar line
https://bugs.kde.org/show_bug.cgi?id=483487 Kai Uwe Broulik changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/breeze/-/commit/8af48c52 |ma/breeze/-/commit/c949bb4b |063d04883c055ba3cf0f5a2ddef |d288bba5eda06e9a89ea0a05492 |ef41c |0c719 --- Comment #7 from Kai Uwe Broulik --- Git commit c949bb4bd288bba5eda06e9a89ea0a054920c719 by Kai Uwe Broulik. Committed on 16/03/2024 at 11:50. Pushed by broulik into branch 'Plasma/6.0'. kstyle: Don't send event to disabled scroll bar If nobody accepts the event, it can lead to infinite recursion. (cherry picked from commit 8af48c52063d04883c055ba3cf0f5a2ddefef41c) M +1-1kstyle/breezestyle.cpp https://invent.kde.org/plasma/breeze/-/commit/c949bb4bd288bba5eda06e9a89ea0a054920c719 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 479230] Network graph always shows 2 GiB/s download speed
https://bugs.kde.org/show_bug.cgi?id=479230 Kai Uwe Broulik changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-nm/-/commit/ba505 |ma/plasma-nm/-/commit/9dd7b |d0d93629645d928087fddfc9417 |54936b76e6e06ca1318c2932bb7 |73af086a|ea42007a --- Comment #16 from Kai Uwe Broulik --- Git commit 9dd7b54936b76e6e06ca1318c2932bb7ea42007a by Kai Uwe Broulik. Committed on 16/03/2024 at 11:49. Pushed by broulik into branch 'Plasma/6.0'. Use "double" for storing received/sent bytes An int can overflow and lead to negative and nonsensical speed values. (cherry picked from commit ba505d0d93629645d928087fddfc941773af086a) M +3-2applet/contents/ui/ConnectionItem.qml https://invent.kde.org/plasma/plasma-nm/-/commit/9dd7b54936b76e6e06ca1318c2932bb7ea42007a -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 479230] Network graph always shows 2 GiB/s download speed
https://bugs.kde.org/show_bug.cgi?id=479230 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/plasma-nm/-/commit/ba505 ||d0d93629645d928087fddfc9417 ||73af086a Status|CONFIRMED |RESOLVED --- Comment #15 from Kai Uwe Broulik --- Git commit ba505d0d93629645d928087fddfc941773af086a by Kai Uwe Broulik. Committed on 16/03/2024 at 10:37. Pushed by broulik into branch 'master'. Use "double" for storing received/sent bytes An int can overflow and lead to negative and nonsensical speed values. M +3-2applet/contents/ui/ConnectionItem.qml https://invent.kde.org/plasma/plasma-nm/-/commit/ba505d0d93629645d928087fddfc941773af086a -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 483707] When selecting a end date for a recurring event the wrong date is saved
https://bugs.kde.org/show_bug.cgi?id=483707 Kai changed: What|Removed |Added CC||kn5i02...@mozmail.com -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 483707] New: When selecting a end date for a recurring event the wrong date is saved
https://bugs.kde.org/show_bug.cgi?id=483707 Bug ID: 483707 Summary: When selecting a end date for a recurring event the wrong date is saved Classification: Applications Product: korganizer Version: 6.0.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: recurrence Assignee: kdepim-b...@kde.org Reporter: kn5i02...@mozmail.com Target Milestone: --- SUMMARY When selecting a end date for a recurring event the date before the selected date is used. STEPS TO REPRODUCE 1. Create a recurring event with a end date ending "on" a specific date 2. See that the event ends one day before the selected date OBSERVED RESULT The saved date to end the recurring event is one day before the selected event. EXPECTED RESULT The selected event should be used. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.7.9-arch1-1 (64-bit) (available in About System) KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.2 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 483487] Kate crash clicking on "empty" horizontal scroll bar line
https://bugs.kde.org/show_bug.cgi?id=483487 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/breeze/-/commit/8af48c52 ||063d04883c055ba3cf0f5a2ddef ||ef41c --- Comment #6 from Kai Uwe Broulik --- Git commit 8af48c52063d04883c055ba3cf0f5a2ddefef41c by Kai Uwe Broulik. Committed on 14/03/2024 at 22:06. Pushed by cullmann into branch 'master'. kstyle: Don't send event to disabled scroll bar If nobody accepts the event, it can lead to infinite recursion. M +1-1kstyle/breezestyle.cpp https://invent.kde.org/plasma/breeze/-/commit/8af48c52063d04883c055ba3cf0f5a2ddefef41c -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 483572] New: Cannot repeadly click next or previous month to navigate quickly
https://bugs.kde.org/show_bug.cgi?id=483572 Bug ID: 483572 Summary: Cannot repeadly click next or previous month to navigate quickly Classification: Frameworks and Libraries Product: frameworks-plasma Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: components Assignee: plasma-b...@kde.org Reporter: k...@privat.broulik.de CC: m...@ratijas.tk, notm...@gmail.com Target Milestone: --- SUMMARY When clicking next or previous month button in the calendar quickly, it doesn't switch months properly. It animates whenever I click but will just animate to the same month again. I have to wait for the animation to finish before I can click again. STEPS TO REPRODUCE 1. Open calendar in digital clock 2. Click next 5 times OBSERVED RESULT I see April 2024 (today is March 2024) EXPECTED RESULT I see August 2024 SOFTWARE/OS VERSIONS Linux/KDE Plasma: git master as of 2022-03-14 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483374] No Default Leave Option any more
https://bugs.kde.org/show_bug.cgi?id=483374 Kai Uwe Broulik changed: What|Removed |Added Version Fixed In||6.1.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483374] No Default Leave Option any more
https://bugs.kde.org/show_bug.cgi?id=483374 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #6 from Kai Uwe Broulik --- But it seems shutdown is the default option now. Closing. The fact that the setting is carried over from 5 and breaks the dialog is a different bug, I guess. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 482581] Dolphin icon no longer changes according to the accent color
https://bugs.kde.org/show_bug.cgi?id=482581 Kai Uwe Broulik changed: What|Removed |Added Latest Commit||https://invent.kde.org/syst ||em/dolphin/-/commit/3a7e54f ||4b4c0b795279360cbe01d8dc423 ||45607f Status|CONFIRMED |RESOLVED Version Fixed In||24.02.1 Resolution|--- |FIXED --- Comment #4 from Kai Uwe Broulik --- Git commit 3a7e54f4b4c0b795279360cbe01d8dc42345607f by Kai Uwe Broulik. Committed on 13/03/2024 at 17:18. Pushed by broulik into branch 'master'. Sync Dolphin icon with Breeze system-file-manager The upstream Breeze variant colorizes based on the user's color scheme which was lost when Dolphin switched to using its org.kde.dolphin icon. FIXED-IN: 24.02.1 M +136 -290 src/icons/org.kde.dolphin.svg https://invent.kde.org/system/dolphin/-/commit/3a7e54f4b4c0b795279360cbe01d8dc42345607f -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483374] No Default Leave Option any more
https://bugs.kde.org/show_bug.cgi?id=483374 --- Comment #3 from Kai Uwe Broulik --- Also, be glad I am annoyed by this too, and I will ignore your second comment, otherwise good luck trying to convince someone of your arguments with that tone. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483374] No Default Leave Option any more
https://bugs.kde.org/show_bug.cgi?id=483374 Kai Uwe Broulik changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||k...@privat.broulik.de --- Comment #2 from Kai Uwe Broulik --- I agree. While I believe most people leave their computer through the Kickoff menu, and got confused by the options, which is why the menu is also simplified in the upcoming 6.1, I use the “Leave” option on the context menu to leave my session and am annoyed it’s defunct now, too. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483417] No Tabs on Icons-Only-Taskmanager
https://bugs.kde.org/show_bug.cgi?id=483417 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de Severity|normal |wishlist --- Comment #1 from Kai Uwe Broulik --- Because why would they? -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 483335] Application menu throws an error and is empty with some Qt5 applications
https://bugs.kde.org/show_bug.cgi?id=483335 --- Comment #2 from Kai --- (In reply to Nicolas Fella from comment #1) > Is plasma5-integration installed? No, it wasn't. Only plasma-integration. Manually installing plasma5-integration solved the problem. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483351] plasma-emojier high memory usage
https://bugs.kde.org/show_bug.cgi?id=483351 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #2 from Kai Uwe Broulik --- Sounds like https://bugreports.qt.io/browse/QTBUG-120007 -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 483335] Application menu throws an error and is empty with some Qt5 applications
https://bugs.kde.org/show_bug.cgi?id=483335 Kai changed: What|Removed |Added CC||kn5i02...@mozmail.com -- You are receiving this mail because: You are watching all bug changes.
[kded-appmenu] [Bug 483335] New: Application menu throws an error and is empty with some Qt5 applications
https://bugs.kde.org/show_bug.cgi?id=483335 Bug ID: 483335 Summary: Application menu throws an error and is empty with some Qt5 applications Classification: Plasma Product: kded-appmenu Version: 6.0.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Titlebar menu button/popup Assignee: plasma-b...@kde.org Reporter: kn5i02...@mozmail.com Target Milestone: --- SUMMARY When starting some Qt5 applications (krdc, kmymoney, qt5-tools, keepassxc, sqlitebrowser) the following error is displayed in system logs and the application menu is not accessible (empty or hidden). ``` 12/03/2024 13:20kded6 org.kde.plasma.appmenu: Got an error 12/03/2024 13:20kded6 org.kde.plasma.appmenu: Got an error 12/03/2024 13:20kded6 org.kde.plasma.appmenu: Got an error 12/03/2024 13:20kded6 org.kde.plasma.appmenu: Got an error ``` STEPS TO REPRODUCE 1. Open an application, watch the logs and search for the application menu. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.7.9-arch1-1 (64-bit) (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482889] plasmashell hits ASSERT on startup after upgrade to 6.0.0
https://bugs.kde.org/show_bug.cgi?id=482889 Kai Uwe Broulik changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-desktop/-/commit/ |ma/plasma-desktop/-/commit/ |0504f0e0ef2b0ebc4f1b1faa9ee |0264726f8720d3093bd3ba10f61 |8c74d2191931b |07197b4f90be3 --- Comment #8 from Kai Uwe Broulik --- Git commit 0264726f8720d3093bd3ba10f6107197b4f90be3 by Kai Uwe Broulik. Committed on 09/03/2024 at 12:33. Pushed by broulik into branch 'Plasma/6.0'. Folder Model: Handle invalid URL in desktop file There's no point in handling an invalid URL, and KProtocolInfo asserts that the scheme is not empty. (cherry picked from commit 0504f0e0ef2b0ebc4f1b1faa9ee8c74d2191931b) M +4-1containments/desktop/plugins/folder/foldermodel.cpp https://invent.kde.org/plasma/plasma-desktop/-/commit/0264726f8720d3093bd3ba10f6107197b4f90be3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482889] plasmashell hits ASSERT on startup after upgrade to 6.0.0
https://bugs.kde.org/show_bug.cgi?id=482889 Kai Uwe Broulik changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/plasma-desktop/-/commit/ ||0504f0e0ef2b0ebc4f1b1faa9ee ||8c74d2191931b --- Comment #7 from Kai Uwe Broulik --- Git commit 0504f0e0ef2b0ebc4f1b1faa9ee8c74d2191931b by Kai Uwe Broulik. Committed on 09/03/2024 at 12:23. Pushed by broulik into branch 'master'. Folder Model: Handle invalid URL in desktop file There's no point in handling an invalid URL, and KProtocolInfo asserts that the scheme is not empty. M +4-1containments/desktop/plugins/folder/foldermodel.cpp https://invent.kde.org/plasma/plasma-desktop/-/commit/0504f0e0ef2b0ebc4f1b1faa9ee8c74d2191931b -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482889] plasmashell hits ASSERT on startup after upgrade to 6.0.0
https://bugs.kde.org/show_bug.cgi?id=482889 Kai Uwe Broulik changed: What|Removed |Added CC||fa...@kde.org --- Comment #5 from Kai Uwe Broulik --- Hmm, [$e] should expand environment variables. I know we dumbed down the evironment expansion for security reasons when used in desktop files which could have broken this here? @dfaure you have any idea? Either way, let's not assert in Folder Model about broken URLs. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482889] plasmashell hits ASSERT on startup after upgrade to 6.0.0
https://bugs.kde.org/show_bug.cgi?id=482889 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #2 from Kai Uwe Broulik --- Sounds like a trivial fix but I’d like to understand how the scheme can be empty in the first place. Any chance you could look at what the url is it tries to check? Looks like a broken desktop file you have there? -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 449517] Applet instance should show a brief error in addition to the notification about connection failure
https://bugs.kde.org/show_bug.cgi?id=449517 Kai Uwe Broulik changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/bluedevil/-/commit/3efb2 ||a2dbe8e60de11a6033ef4977f64 ||100a9646 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #2 from Kai Uwe Broulik --- Git commit 3efb2a2dbe8e60de11a6033ef4977f64100a9646 by Kai Uwe Broulik, on behalf of Patrik Fábián. Committed on 05/03/2024 at 12:55. Pushed by broulik into branch 'master'. applet: Indicate connnection failure in the applet There is no indication of an unsuccessful connection attempt in the applet, only a notification is shown, which could be missed in some cases. This adds a "Connection failed" message under the device's name. M +5-0src/applet/package/contents/ui/DeviceItem.qml https://invent.kde.org/plasma/bluedevil/-/commit/3efb2a2dbe8e60de11a6033ef4977f64100a9646 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 482182] Breeze is mixes up light & dark
https://bugs.kde.org/show_bug.cgi?id=482182 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #1 from Kai Uwe Broulik --- Judging from the slider this isn't actually Breeze theme but looks like Fusion. Maybe some dependency is missing. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482081] Translation of local keyboard layout fails when not set to en-US
https://bugs.kde.org/show_bug.cgi?id=482081 Kai changed: What|Removed |Added CC||kn5i02...@mozmail.com -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482081] New: Translation of local keyboard layout fails when not set to en-US
https://bugs.kde.org/show_bug.cgi?id=482081 Bug ID: 482081 Summary: Translation of local keyboard layout fails when not set to en-US Classification: Applications Product: krdc Version: 23.08.5 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: VNC Assignee: uwol...@kde.org Reporter: kn5i02...@mozmail.com CC: aa...@kde.org Target Milestone: --- SUMMARY Only when the local keyboard layout is set to English (US) the keys are transmitted almost correctly. STEPS TO REPRODUCE 1. Set local keyboard layout to something different then English (US). In my case German. 2. Connect to a remote with VNC. 3. Try to type any special characters. OBSERVED RESULT 1. When the local and remote keymap is set to German: "@" -> "²", "&" -> "/", "-" -> "ß", "_" -> "?", "|" -> "’" 2. When the local keymap is set to German and the remote keymap to English (US): "@" -> "2", "&" -> "&", "-" -> "-", "_" -> "_", "|" -> "\" 3. When the local and remote keymap is set to English (US): seems to work fine 4. When the local keymap is set to English (US) and the remote keymap to German: almost correct. like typing on a German keyboard EXPECTED RESULT Keyboard input should be transmitted correctly. SOFTWARE/OS VERSIONS Linux: Arch Linux 6.7.6-arch1-1 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481912] Feature request: Wayland remote login sessions with Plasma, like xrdp
https://bugs.kde.org/show_bug.cgi?id=481912 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #2 from Kai Uwe Broulik --- There’s also this effort by Google: https://mail.kde.org/pipermail/kde-devel/2024-February/002476.html with https://gitlab.freedesktop.org/jadahl/xdg-specs/-/merge_requests/1 -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 481972] File picker closes when scrolling
https://bugs.kde.org/show_bug.cgi?id=481972 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #4 from Kai Uwe Broulik --- Wonder if that is also that wayland relative motion protocol issue, i.e. "wl_pointer has no event 10" -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481840] Removing a VPN connection is impossible on 6.0
https://bugs.kde.org/show_bug.cgi?id=481840 Kai Uwe Broulik changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-nm/-/commit/341a1 |ma/plasma-nm/-/commit/2fd1b |db2f4503d30abd85ecb0622ee67 |7960defbe794c48bddb61d3d123 |c27838b0|286b0c1c --- Comment #8 from Kai Uwe Broulik --- Git commit 2fd1b7960defbe794c48bddb61d3d123286b0c1c by Kai Uwe Broulik. Committed on 27/02/2024 at 14:56. Pushed by broulik into branch 'Plasma/6.0'. KCM: Work around MessageDialog not emitting accepted signal Reported as QTBUG-122770 (cherry picked from commit 341a1db2f4503d30abd85ecb0622ee67c27838b0) M +8-5kcm/qml/main.qml https://invent.kde.org/plasma/plasma-nm/-/commit/2fd1b7960defbe794c48bddb61d3d123286b0c1c -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481840] Removing a VPN connection is impossible on 6.0
https://bugs.kde.org/show_bug.cgi?id=481840 Kai Uwe Broulik changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/plasma-nm/-/commit/341a1 ||db2f4503d30abd85ecb0622ee67 ||c27838b0 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #7 from Kai Uwe Broulik --- Git commit 341a1db2f4503d30abd85ecb0622ee67c27838b0 by Kai Uwe Broulik. Committed on 27/02/2024 at 14:51. Pushed by broulik into branch 'master'. KCM: Work around MessageDialog not emitting accepted signal Reported as QTBUG-122770 M +8-5kcm/qml/main.qml https://invent.kde.org/plasma/plasma-nm/-/commit/341a1db2f4503d30abd85ecb0622ee67c27838b0 -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 481759] After sending a file to Bluetooth device via Bluetooth applet, notification shows a clickable link that's always wrong
https://bugs.kde.org/show_bug.cgi?id=481759 Kai Uwe Broulik changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-workspace/-/commi |ma/plasma-workspace/-/commi |t/f807a2793bd91360324469c5e |t/403431b1b801326cbca732dbc |2f1b621a62be426 |c759a719c1bb7f0 --- Comment #4 from Kai Uwe Broulik --- Git commit 403431b1b801326cbca732dbcc759a719c1bb7f0 by Kai Uwe Broulik. Committed on 27/02/2024 at 11:19. Pushed by broulik into branch 'Plasma/6.0'. Notifications: Only convert absolute paths to file URLs If the contents is just e.g. a device name, there's no point in turning it into a URL. (cherry picked from commit f807a2793bd91360324469c5e2f1b621a62be426) M +5-0libnotificationmanager/job_p.cpp https://invent.kde.org/plasma/plasma-workspace/-/commit/403431b1b801326cbca732dbcc759a719c1bb7f0 -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 439470] KFontView is unable to open or install a font on Wayland
https://bugs.kde.org/show_bug.cgi?id=439470 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #26 from Kai Uwe Broulik --- Yes. Reworking the font management to be independent of X is a whole different story. I am working on it but it will take a lot of effort, so I won't promise it will be done soon. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 481759] After sending a file to Bluetooth device via Bluetooth applet, notification shows a clickable link that's always wrong
https://bugs.kde.org/show_bug.cgi?id=481759 Kai Uwe Broulik changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/-/commi ||t/f807a2793bd91360324469c5e ||2f1b621a62be426 --- Comment #3 from Kai Uwe Broulik --- Git commit f807a2793bd91360324469c5e2f1b621a62be426 by Kai Uwe Broulik. Committed on 27/02/2024 at 09:22. Pushed by broulik into branch 'master'. Notifications: Only convert absolute paths to file URLs If the contents is just e.g. a device name, there's no point in turning it into a URL. M +5-0libnotificationmanager/job_p.cpp https://invent.kde.org/plasma/plasma-workspace/-/commit/f807a2793bd91360324469c5e2f1b621a62be426 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481840] Removing a VPN connection is impossible on 6.0
https://bugs.kde.org/show_bug.cgi?id=481840 Kai Uwe Broulik changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 481840] Removing a VPN connection is impossible on 6.0
https://bugs.kde.org/show_bug.cgi?id=481840 Kai Uwe Broulik changed: What|Removed |Added CC||k...@privat.broulik.de --- Comment #5 from Kai Uwe Broulik --- QtQuick Dialogs, the gift that keeps on giving. For some reason the onAccepted handler is never called... (For 6.1 we should really provide our own dialog implementation through plasma-integration) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481759] Error message after click on the link from the notification shown after sending a file via Bluetooth applet
https://bugs.kde.org/show_bug.cgi?id=481759 Kai Uwe Broulik changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 481678] New: xdg-desktop-portal-kde process does not quit when DBus connection is lost
https://bugs.kde.org/show_bug.cgi?id=481678 Bug ID: 481678 Summary: xdg-desktop-portal-kde process does not quit when DBus connection is lost Classification: Plasma Product: xdg-desktop-portal-kde Version: 5.27.10 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: k...@privat.broulik.de CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org Target Milestone: --- SUMMARY When running XDG desktop portal kde with its own DBus daemon, it does not quit when the DBus daemon dies. xdg-desktop-portal and xdg-desktop-portal-gtk quit but the kde one sticks around STEPS TO REPRODUCE 1. export $(dbus-launch) 2. qdbusviewer (Qt 6 version seems to call into the portal immediately) 3. kill $DBUS_SESSION_BUS_PID OBSERVED RESULT xdg-desktop-portal and xdg-desktop-portal-kde quit, xdg-desktop-portal-kde remains EXPECTED RESULT xdg-desktop-portal-kde also quits SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.27.10 Qt Version: 5.15.3 (6.8 git dev) ADDITIONAL INFORMATION They can accumulate so much that eventually X apps fail to start with "too many clients connected" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481636] Custom date format doesn't respect regional settings
https://bugs.kde.org/show_bug.cgi?id=481636 Kai Uwe Broulik changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed In||6.0.0 Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/-/commi ||t/f3ef11ea6915d549fe04289c2 ||a9958f4368e4e5b CC||k...@privat.broulik.de --- Comment #1 from Kai Uwe Broulik --- Fixed in 6.0 final by https://invent.kde.org/plasma/plasma-workspace/-/commit/f3ef11ea6915d549fe04289c2a9958f4368e4e5b -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 462381] KIO-Extras AFC URL error
https://bugs.kde.org/show_bug.cgi?id=462381 Kai Uwe Broulik changed: What|Removed |Added Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw |ork/kio-extras/-/commit/6ea |ork/kio-extras/-/commit/85e |74a117a85235238567d758ab0d0 |831b581466f737b2111b0cff034 |da60829d55 |f3756bc209 --- Comment #11 from Kai Uwe Broulik --- Git commit 85e831b581466f737b2111b0cff034f3756bc209 by Kai Uwe Broulik. Committed on 20/02/2024 at 19:49. Pushed by broulik into branch 'release/24.02'. afc: Drop pretty name handling Instead, set UDI as host and rely on KFilePlaces to match up the names. (cherry picked from commit 6ea74a117a85235238567d758ab0d0da60829d55) M +13 -6afc/afcurl.cpp M +2-0afc/afcurl.h M +14 -108 afc/kio_afc.cpp M +1-5afc/kio_afc.h https://invent.kde.org/network/kio-extras/-/commit/85e831b581466f737b2111b0cff034f3756bc209 -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 462381] KIO-Extras AFC URL error
https://bugs.kde.org/show_bug.cgi?id=462381 Kai Uwe Broulik changed: What|Removed |Added Latest Commit||https://invent.kde.org/netw ||ork/kio-extras/-/commit/6ea ||74a117a85235238567d758ab0d0 ||da60829d55 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #10 from Kai Uwe Broulik --- Git commit 6ea74a117a85235238567d758ab0d0da60829d55 by Kai Uwe Broulik. Committed on 20/02/2024 at 14:20. Pushed by broulik into branch 'master'. afc: Drop pretty name handling Instead, set UDI as host and rely on KFilePlaces to match up the names. M +13 -6afc/afcurl.cpp M +2-0afc/afcurl.h M +14 -108 afc/kio_afc.cpp M +1-5afc/kio_afc.h https://invent.kde.org/network/kio-extras/-/commit/6ea74a117a85235238567d758ab0d0da60829d55 -- You are receiving this mail because: You are watching all bug changes.
