https://bugs.kde.org/show_bug.cgi?id=460017
--- Comment #7 from Riccardo Robecchi ---
(In reply to Nate Graham from comment #6)
> Cool, can you file a kernel bug at https://bugzilla.kernel.org/?
I've filed one at Xanmod's bug tracker:
https://github.com/xanmod/linux/issues/321
--
You are recei
https://bugs.kde.org/show_bug.cgi?id=460017
Nate Graham changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=460017
--- Comment #5 from Arjen Hiemstra ---
That sounds like it. For comparison, this is smaps_rollup from my current
plasmashell process:
Rss: 324172 kB
Pss: 215660 kB
Pss_Dirty:182048 kB
Pss_Anon: 181628 kB
Pss_Fi
https://bugs.kde.org/show_bug.cgi?id=460017
--- Comment #4 from Riccardo Robecchi ---
Thank you for your reply, Arjen. When using 'ls -l /proc/$(pidof plasmashell)/'
I see that all files are owned by my user. I have just tried installing kernel
6.0.9 on a VM and the issue appears there, too. For
https://bugs.kde.org/show_bug.cgi?id=460017
--- Comment #3 from Arjen Hiemstra ---
I'm running kernel 6.0.8 at this point and have a working memory column. The
memory column works by reading the information of `/proc/$PID/smaps_rollup`.
Can you check the presence and permissions of those files on
https://bugs.kde.org/show_bug.cgi?id=460017
--- Comment #2 from Riccardo Robecchi ---
Still an issue as of 5.26.3 with Frameworks 5.100.0. Is there any way I can
help find the cause of this and help fix it?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=460017
--- Comment #1 from Riccardo Robecchi ---
The bug is still present in version 5.26.0.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=460017
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
--
You are receiving this mail beca
