[kwin] [Bug 459453] New: FPS keep decline with the time of use, system become lag
https://bugs.kde.org/show_bug.cgi?id=459453 Bug ID: 459453 Summary: FPS keep decline with the time of use, system become lag Classification: Plasma Product: kwin Version: 5.25.5 Platform: Archlinux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: ove...@gmail.com Target Milestone: --- Created attachment 152271 --> https://bugs.kde.org/attachment.cgi?id=152271&action=edit kwin_x11 and xorg log SUMMARY The fps will drop to 30 in 2-4hours, and drop to 20fps in 4 - 8hours, and will keep decline. In this situaltion, Xorg will take about 50% cpu even close all windows(cpu consume will drop a little bit, but it will back to 50% if there are any action performed), and will take more with the time passing. eg: It will take about 100% when fps go down to 15-20. kwin_x11 consume up to 20% cpu according the number of windows. Also tested glxgears, and it shows good performance with 60 fps. Tried restart plasmashell with "--replace" option, not work. The only solution i found is to restart kwin_11 with "--replace" options. But it will keep happened in next 2hours. There are no related error log print by Xorg or Kwin_x11, i will attach logs below. STEPS TO REPRODUCE 1. Login to system 2. Normal use 3. FPS drop SOFTWARE/OS VERSIONS KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.9-arch1-1 (64-bit) Graphics Platform: X11 Processors: 6 × Intel® Core™ i5-9500T CPU @ 2.20GHz Memory: 62.6 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459453] FPS keep decline with the time of use, system become lag
https://bugs.kde.org/show_bug.cgi?id=459453 --- Comment #2 from Ovear --- Yeah, i do notice that too, but it's seems the result that compositor lagged[1]. And it may noe caused this problem i think, since there are actually a number of ubuntu and debian users reported it to upstream[2][3][4]. I also found multiple bugs in bugs.kde.org which mentioned this[5], but seems none of it is related to "compositor lagged continuous". Since there are no more detail logs in Xorg and kde, we think we may try to find a way to figured the root case which caused it. May be more verbose log or flame graph through efbp(with SystemTap or perf)? I am not familiar with kde an Xorg, so i have no idea how to apporach it. I am still trying to isolate this case, and see if I can find out more detail about this. [1]https://askubuntu.com/questions/1292691/why-am-i-getting-event-processing-lagging-behind-msg-in-ubuntu-20-10/1292837#1292837 [2]https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1914806 [3]https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968093 [4]https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1870597 [5]https://bugs.kde.org/show_bug.cgi?format=multiple&id=454590 (In reply to Nate Graham from comment #1) > A lot of messages like this: > > [ 20012.277] (EE) event9 - SONiX USB DEVICE: client bug: event processing > lagging behind by 28ms, your system is too slow > [ 20320.057] (EE) event9 - SONiX USB DEVICE: client bug: event processing > lagging behind by 24ms, your system is too slow > [ 20816.976] (EE) event15 - Logitech MX Master 3: client bug: event > processing lagging behind by 33ms, your system is too slow > [ 20816.976] (EE) client bug: timer event15 debounce short: scheduled expiry > is in the past (-21ms), your system is too slow > [ 20921.164] (EE) event15 - Logitech MX Master 3: client bug: event > processing lagging behind by 22ms, your system is too slow > [ 20921.978] (EE) event15 - Logitech MX Master 3: client bug: event > processing lagging behind by 29ms, your system is too slow > [ 22127.914] (EE) event15 - Logitech MX Master 3: client bug: event > processing lagging behind by 32ms, your system is too slow -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 470382] New: Baloo unable to index any files
https://bugs.kde.org/show_bug.cgi?id=470382 Bug ID: 470382 Summary: Baloo unable to index any files Classification: Frameworks and Libraries Product: frameworks-baloo Version: 5.106.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: baloo-bugs-n...@kde.org Reporter: ove...@gmail.com Target Milestone: --- STEPS TO REPRODUCE 1. Search new files 2. Use balooctl to index those unindex files OBSERVED RESULT Manually index through `balooctl index` result no responding no matter what file is used(including files that not exist). And baloo has been stopped index file for days, even after execute `balooctl check`, still not work. Besides that `balooctl status` takes long time to return result. EXPECTED RESULT Baloo can index new files normally. SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.3.4-arch1-1 (64-bit) Graphics Platform: Wayland ADDITIONAL INFORMATION Nothing releated was found in journalctl. inotify checked through inotifywait and confirmed work. ``` $ time balooctl status Baloo File Indexer is running Indexer state: Idle Total files indexed: 1,192,757 Files waiting for content indexing: 1,554 Files failed to index: 0 Current size of index is 5.78 GiB real0m50.142s user0m0.010s sys 0m0.007s $ balooctl indexSize File Size: 5.78 GiB Used: 290.39 MiB PostingDB: 1.47 GiB 517.279 % PositionDB: 1.92 GiB 677.729 % DocTerms: 666.52 MiB 229.526 % DocFilenameTerms: 77.92 MiB26.832 % DocXattrTerms: 4.00 KiB 0.001 % IdTree: 20.74 MiB 7.143 % IdFileName: 86.97 MiB29.950 % DocTime: 47.92 MiB16.503 % DocData: 12.54 MiB 4.317 % ContentIndexingDB: 48.00 KiB 0.016 % FailedIdsDB:0 B 0.000 % MTimeDB: 3.54 MiB 1.217 % $ balooctl monitor Press ctrl+c to stop monitoring File indexer is running Idle ``` -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 470382] Baloo unable to index any files
https://bugs.kde.org/show_bug.cgi?id=470382 Ovear changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Ovear --- Hi, Oh, change MemoryHigh works for me. According to status output from systemd, baloo just hits the memory limited by systemd. > Memory: 600.6M (high: 512.0M available: 0B) Is that possible to output a warning when baloo failed to request more memory as both systemd and baloo keep silence when it happened? Or may be adjust default memory limit is an option? I am not sure what is the optimal minimal required memory to keep Baloo from freezing. 512M may be a bit insufficient. But I also noticed Baloo doesn't seem to release memory after indexed. Except that, is possible to find what file / reason it wants to index that caused those high memory demand. > Memory: 8.1G (high: 31.2G available: 23.0G) Anyway, Thanks for your help. I will try to add this to Baloo's ArchWiki troubleshoot section. To those who may be affected by this, here is the process to increase systemd memory limit. 1. Use systemd edit function to override default limit > # systemctl --user edit kde-baloo 2. You may modify the file to something like below. ``` ### Anything between here and the comment below will become the contents of the drop-in file [Service] MemoryHigh=50% ### Edits below this comment will be discarded ``` 3. Restart kde-baloo, and it should work. > # systemctl restart --user kde-baloo -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 470382] Baloo unable to index any files
https://bugs.kde.org/show_bug.cgi?id=470382 --- Comment #3 from Ovear --- Sorry for the typo. > Except that, is that possible to find what file / reason it wants to index > that caused those high memory demand? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kquickcharts] [Bug 434462] Weird horizontal lines in charts
https://bugs.kde.org/show_bug.cgi?id=434462 Ovear changed: What|Removed |Added CC||ove...@gmail.com --- Comment #21 from Ovear --- Hi, I encountered this problem after upgrading to KDE Plasma 6 too. Operating System: EndeavourOS KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 6 × Intel® Core™ i5-9500T CPU @ 2.20GHz Memory: 62.6 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 482076] Clipboard no longer appears under mouse cursor
https://bugs.kde.org/show_bug.cgi?id=482076 Ovear changed: What|Removed |Added CC||ove...@gmail.com --- Comment #20 from Ovear --- I'm experiencing the same issue after upgrading to KDE Plasma 6. In my experience, this fueature only work occasionally (maybe 10% if the time) when no windows are displayed on the desktop. However, as soon as any program is launched or a window is shown, the clipboard popup gets stuck in the center of the screen, as shown in the attached screenshot titled "Screenshot with clipboard popup bellow screen". Operating System: EndeavourOS KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 6 × Intel® Core™ i5-9500T CPU @ 2.20GHz Memory: 62.6 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 453594] New: RGB range setting missing
https://bugs.kde.org/show_bug.cgi?id=453594 Bug ID: 453594 Summary: RGB range setting missing Product: KScreen Version: 5.24.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: ove...@gmail.com Target Milestone: --- SUMMARY *** Hi, I am using KDE 5.24.5(x11) with sddm, but "RGB range" is missing in screen settings which seems support by KDE a years ago. The intel drvier misconfig RGB range and needs to set manually, and "xrandr --set "Broadcast RGB"" workaround confirms works. Thanks *** STEPS TO REPRODUCE 1. Open screen setting 2. No "RGB range" option 3. xrandr quirk to set "RGB range" works. OBSERVED RESULT "RGB range" option missing EXPECTED RESULT "RGB range" option exist SOFTWARE/OS VERSIONS KDE Plasma Version: 5.24.5 KDE Frameworks Version: 5.93.0 Qt Version: 5.15.3 Kernel Version: 5.17.5-arch1-1 (64-bit) Graphics Platform: X11 Graphics Processor: Mesa Intel® UHD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 453594] RGB range setting missing
https://bugs.kde.org/show_bug.cgi?id=453594 --- Comment #2 from Ovear --- Hi, Oh, i didn't notice this is a wayland only feature. Tested on wayland session, and perform as excpeted. Is that possible to support this feature on X11 session too? It's really helpful when grphic card drvier choose wrong rgb range. Thanks -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459453] FPS keep decline with the time of use, system become lag
https://bugs.kde.org/show_bug.cgi?id=459453 --- Comment #5 from Ovear --- Hi, I have migrated to KDE plasma Wayland session for a while, but fortunately, I haven't reinstalled my system yet. I'll check if I can reproduce this issue by switching back to X11 session, possibly this weekend. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 470382] Baloo unable to index any files
https://bugs.kde.org/show_bug.cgi?id=470382 --- Comment #7 from Ovear --- Hi, Thanks for the update! I hadn't noticed that this problem was fixed. I'll remove the overridden settings to see if kde-baloo works as expected. For now, here's a brief update on the current memory usage, which I'm not quite sure how to interpret. ``` ● kde-baloo.service - Baloo File Indexer Daemon Loaded: loaded (/usr/lib/systemd/user/kde-baloo.service; disabled; preset: enabled) Drop-In: /home/REDACTED/.config/system/user/kde-baloo.service.d └─override.conf Active: active (running) since Sat 2024-06-29 15:56:04 CST; 1 week 1 day ago Main PID: 3606 (baloo_file) Tasks: 2 (limit: 76867) Memory: 12.0G (high: 31.2G available: 5.2G peak: 13.2G) > Limit to 50% by override.conf CPU: 7min 39.112s CGroup: /user.slice/user-1000.slice/user@1000.service/background.slice/kde-baloo.service └─3606 /usr/lib/kf6/baloo_file ``` -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 470382] Baloo unable to index any files
https://bugs.kde.org/show_bug.cgi?id=470382 --- Comment #9 from Ovear --- Hi, I have done some tests of this situation. > I think I'd stepwise reduce the MemoryHigh value rather than removing the > override. Thanks for your suggestion, and you predicted exactly what will happen next. First, the good news: baloo works with the updated version. It can initialize, load the index and is operational for both indexing and searching. ``` $ LANG=en_US.UTF8 balooctl6 status Baloo File Indexer is running Indexer state: Idle Total files indexed: 700,557 Files waiting for content indexing: 0 Files failed to index: 0 Current size of index is 12.17 GiB ● kde-baloo.service - Baloo File Indexer Daemon Loaded: loaded (/usr/lib/systemd/user/kde-baloo.service; disabled; preset: enabled) Drop-In: /home/REDACTED/.config/system/user/kde-baloo.service.d └─override.conf Active: active (running) since Wed 2024-07-10 18:20:26 CST; 50s ago Process: 1441235 ExecCondition=/usr/bin/kde-systemd-start-condition --condition baloofilerc:Basic Settings:Indexing-Enabled:true (code=exited, status=0/SUCCESS) Main PID: 1441238 (baloo_file) Tasks: 3 (limit: 76867) Memory: 222.6M (high: 512.0M available: 289.3M peak: 223.5M) CPU: 20.640s CGroup: /user.slice/user-1000.slice/user@1000.service/background.slice/kde-baloo.service └─1441238 /usr/lib/kf6/baloo_file ``` However, there's also some bad news. About a day after I reverted my changes to systemd service files, baloo got stuck again. The `balooctl6 status` hung up and didn't response. Upon a quick diagnosis, I found that baloo hit the memory limit again. ``` $ balooctl6 -v baloo 6.2.0 $ ps -e -o pid,comm,pmem,rss|grep baloo 45489 baloorunner 0.5 363196 1144015 baloo_file 1.5 984736 1322906 baloo_file_extr 1.4 922908 $ systemctl status --user kde-baloo.service ● kde-baloo.service - Baloo File Indexer Daemon Loaded: loaded (/usr/lib/systemd/user/kde-baloo.service; disabled; preset: enabled) Active: active (running) since Mon 2024-07-08 02:47:52 CST; 2 days ago Process: 1144013 ExecCondition=/usr/bin/kde-systemd-start-condition --condition baloofilerc:Basic Settings:Indexing-Enabled:true (code=exited, status=0/SUCCESS) Main PID: 1144015 (baloo_file) Tasks: 5 (limit: 76867) Memory: 584.4M (high: 512.0M available: 0B peak: 584.9M) CPU: 3min 49.366s CGroup: /user.slice/user-1000.slice/user@1000.service/background.slice/kde-baloo.service ├─1144015 /usr/lib/kf6/baloo_file └─1322906 /usr/lib/kf6/baloo_file_extractor ``` After changeing MemoryHigh to 50%, baloo quickly consumed 3GB of memory and went back to operation. ``` Memory: 1.3G (high: 31.2G available: 5.7G peak: 3.0G) ``` I assumed this might be due to baloo indexing some files that require more memory. I am trying to isolate and reproduce this issue and will update once I make progress. PS: I have tried creating small text files, and baloo works with the default MemoryHigh settings currently. Any advice or hints to isolate this problem would be greatly welcomed. -- You are receiving this mail because: You are watching all bug changes.
[kcalc] [Bug 487566] Kcalc doesn't chain result into next calculation anymore
https://bugs.kde.org/show_bug.cgi?id=487566 Ovear changed: What|Removed |Added CC||ove...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459453] FPS keep decline with the time of use, system become lag
https://bugs.kde.org/show_bug.cgi?id=459453 Ovear changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME --- Comment #7 from Ovear --- Hi, I am running KDE plasma 6 for a few days, and unable to reproduce this issues now, although Kwin_x11 and plasma-shell stop responding everyday. Consider I migrated to Wayland for a long time, and KDE plasma performs well, I am going to change this issue to WORKSFORME. Thanks for everyone. PS: I am wondering if it's necessary to report the not responding problem mentioned before, will try to search it online to see if I can got more information. -- You are receiving this mail because: You are watching all bug changes.
