[SOLVED] Debianster - System Monitor Works Only On Root User

[yuvarajvelmurugan]

System Monitor tool is not working in normal user mode.

When i switch to root user from terminal and launch the "sudo ksysguard" command it is displaying cpu and other history information graph.

[Head_on_a_Stick]

System Monitor tool is not working in normal user mode.

Please explain the failure more fully. Have you tried launching it from a terminal to see any error messages? Or check ~/.xsession-errors

[yuvarajvelmurugan]

System Monitor tool is not working in normal user mode.

Please explain the failure more fully. Have you tried launching it from a terminal to see any error messages? Or check ~/.xsession-errors

CPU history, Memory & Swap history, Network history none of these are showing any graphs. They are idle in zero.

When i tried launching system monitor from terminal using the command "sudo ksysguard" the tool is showing graphs for CPU history, Memory & Swap history, Network history.

Also in terminal i am getting below message:

Code: Select all

QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
QDBusConnection: name 'org.kde.kglobalaccel' had owner '' but we thought it was ':1.1'

Then i ran a command "journalctl _UID=0" on terminal to view session logs:

Code: Select all

-- Logs begin at Fri 2020-11-06 17:30:38 IST, end at Fri 2020-11-06 17:42:39 I
Nov 06 17:30:38 yuvi-pc systemd-journald[286]: Journal started
Nov 06 17:30:38 yuvi-pc systemd-journald[286]: Runtime journal (/run/log/journ
Nov 06 17:30:38 yuvi-pc systemd[1]: Starting Flush Journal to Persistent Stora
Nov 06 17:30:38 yuvi-pc systemd[1]: Started Create System Users.
Nov 06 17:30:38 yuvi-pc systemd[1]: Starting Create Static Device Nodes in /de
Nov 06 17:30:38 yuvi-pc systemd-journald[286]: Runtime journal (/run/log/journ
Nov 06 17:30:38 yuvi-pc systemd-tmpfiles[302]: [/usr/lib/tmpfiles.d/speech-dis
Nov 06 17:30:38 yuvi-pc systemd-tmpfiles[302]: [/usr/lib/tmpfiles.d/speech-dis
Nov 06 17:30:38 yuvi-pc systemd-tmpfiles[302]: [/usr/lib/tmpfiles.d/speech-dis
Nov 06 17:30:38 yuvi-pc systemd-tmpfiles[302]: [/usr/lib/tmpfiles.d/speech-dis
Nov 06 17:30:38 yuvi-pc systemd-tmpfiles[302]: [/usr/lib/tmpfiles.d/speech-dis
Nov 06 17:30:38 yuvi-pc systemd[1]: Started Create Static Device Nodes in /dev
Nov 06 17:30:38 yuvi-pc systemd[1]: Started Flush Journal to Persistent Storag
Nov 06 17:30:38 yuvi-pc systemd[1]: Starting udev Kernel Device Manager...
Nov 06 17:30:38 yuvi-pc systemd[1]: Reached target Local File Systems (Pre).
Nov 06 17:30:38 yuvi-pc systemd[1]: Started udev Kernel Device Manager.
Nov 06 17:30:38 yuvi-pc systemd[1]: Starting Show Plymouth Boot Screen...
Nov 06 17:30:38 yuvi-pc systemd[1]: plymouth-start.service: Succeeded.
Nov 06 17:30:38 yuvi-pc systemd[1]: Started Show Plymouth Boot Screen.
Nov 06 17:30:38 yuvi-pc systemd[1]: Started Forward Password Requests to Plymo
Nov 06 17:30:38 yuvi-pc systemd[1]: Condition check resulted in Dispatch Passw
Nov 06 17:30:38 yuvi-pc systemd[1]: Reached target Local Encrypted Volumes.
Nov 06 17:30:38 yuvi-pc systemd[1]: Reached target Paths.
Nov 06 17:30:38 yuvi-pc systemd-udevd[335]: link_config: autonegotiation is un
Nov 06 17:30:38 yuvi-pc systemd-udevd[316]: Using default interface naming sch
Nov 06 17:30:38 yuvi-pc systemd-udevd[316]: link_config: autonegotiation is un
Nov 06 17:30:39 yuvi-pc mtp-probe[373]: checking bus 1, device 3: "/sys/device
Nov 06 17:30:39 yuvi-pc mtp-probe[372]: checking bus 1, device 2: "/sys/device
Nov 06 17:30:39 yuvi-pc mtp-probe[373]: bus: 1, device: 3 was not an MTP devic
Nov 06 17:30:39 yuvi-pc mtp-probe[372]: bus: 1, device: 2 was not an MTP devic
Nov 06 17:30:39 yuvi-pc systemd[1]: Found device ST1000DM010-2EP102 1.
Nov 06 17:30:39 yuvi-pc systemd[1]: Starting Show Plymouth Boot Screen...
Nov 06 17:30:39 yuvi-pc systemd[1]: Condition check resulted in Kernel Configu
Nov 06 17:30:39 yuvi-pc systemd[1]: Condition check resulted in FUSE Control F
Nov 06 17:30:39 yuvi-pc systemd[1]: Condition check resulted in Rebuild Hardwa
lines 1-36...skipping...
-- Logs begin at Fri 2020-11-06 17:30:38 IST, end at Fri 2020-11-06 17:42:39 IST. --
Nov 06 17:30:38 yuvi-pc systemd-journald[286]: Journal started
Nov 06 17:30:38 yuvi-pc systemd-journald[286]: Runtime journal (/run/log/journal/e5f7e3b77325486ebffe5159513d78ab) is 8.0M, max 159.3M, 151.3M free.
Nov 06 17:30:38 yuvi-pc systemd[1]: Starting Flush Journal to Persistent Storage...
Nov 06 17:30:38 yuvi-pc systemd[1]: Started Create System Users.
Nov 06 17:30:38 yuvi-pc systemd[1]: Starting Create Static Device Nodes in /dev...
Nov 06 17:30:38 yuvi-pc systemd-journald[286]: Runtime journal (/run/log/journal/e5f7e3b77325486ebffe5159513d78ab) is 8.0M, max 159.3M, 151.3M free.
Nov 06 17:30:38 yuvi-pc systemd-tmpfiles[302]: [/usr/lib/tmpfiles.d/speech-dispatcher.conf:1] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher → /r
Nov 06 17:30:38 yuvi-pc systemd-tmpfiles[302]: [/usr/lib/tmpfiles.d/speech-dispatcher.conf:2] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.cac
Nov 06 17:30:38 yuvi-pc systemd-tmpfiles[302]: [/usr/lib/tmpfiles.d/speech-dispatcher.conf:3] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.spe
Nov 06 17:30:38 yuvi-pc systemd-tmpfiles[302]: [/usr/lib/tmpfiles.d/speech-dispatcher.conf:4] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.cac
Nov 06 17:30:38 yuvi-pc systemd-tmpfiles[302]: [/usr/lib/tmpfiles.d/speech-dispatcher.conf:5] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/log 
Nov 06 17:30:38 yuvi-pc systemd[1]: Started Create Static Device Nodes in /dev.
Nov 06 17:30:38 yuvi-pc systemd[1]: Started Flush Journal to Persistent Storage.
Nov 06 17:30:38 yuvi-pc systemd[1]: Starting udev Kernel Device Manager...
Nov 06 17:30:38 yuvi-pc systemd[1]: Reached target Local File Systems (Pre).
Nov 06 17:30:38 yuvi-pc systemd[1]: Started udev Kernel Device Manager.
Nov 06 17:30:38 yuvi-pc systemd[1]: Starting Show Plymouth Boot Screen...
Nov 06 17:30:38 yuvi-pc systemd[1]: plymouth-start.service: Succeeded.
Nov 06 17:30:38 yuvi-pc systemd[1]: Started Show Plymouth Boot Screen.
Nov 06 17:30:38 yuvi-pc systemd[1]: Started Forward Password Requests to Plymouth Directory Watch.
Nov 06 17:30:38 yuvi-pc systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped.
Nov 06 17:30:38 yuvi-pc systemd[1]: Reached target Local Encrypted Volumes.
Nov 06 17:30:38 yuvi-pc systemd[1]: Reached target Paths.
Nov 06 17:30:38 yuvi-pc systemd-udevd[335]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Nov 06 17:30:38 yuvi-pc systemd-udevd[316]: Using default interface naming scheme 'v240'.
Nov 06 17:30:38 yuvi-pc systemd-udevd[316]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Nov 06 17:30:39 yuvi-pc mtp-probe[373]: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-8"
Nov 06 17:30:39 yuvi-pc mtp-probe[372]: checking bus 1, device 2: "/sys/devices/pci0000:00/0000:00:14.0/usb1/1-7"
Nov 06 17:30:39 yuvi-pc mtp-probe[373]: bus: 1, device: 3 was not an MTP device
Nov 06 17:30:39 yuvi-pc mtp-probe[372]: bus: 1, device: 2 was not an MTP device
Nov 06 17:30:39 yuvi-pc systemd[1]: Found device ST1000DM010-2EP102 1.
Nov 06 17:30:39 yuvi-pc systemd[1]: Starting Show Plymouth Boot Screen...
Nov 06 17:30:39 yuvi-pc systemd[1]: Condition check resulted in Kernel Configuration File System being skipped.
Nov 06 17:30:39 yuvi-pc systemd[1]: Condition check resulted in FUSE Control File System being skipped.
Nov 06 17:30:39 yuvi-pc systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
Nov 06 17:30:39 yuvi-pc systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
Nov 06 17:30:39 yuvi-pc systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
Nov 06 17:30:39 yuvi-pc systemd[1]: Starting File System Check on /dev/disk/by-uuid/D0AB-B531...
Nov 06 17:30:39 yuvi-pc systemd[1]: Found device ST1000DM010-2EP102 3.
Nov 06 17:30:39 yuvi-pc systemd[1]: plymouth-start.service: Succeeded.
Nov 06 17:30:39 yuvi-pc systemd[1]: Started Show Plymouth Boot Screen.
Nov 06 17:30:39 yuvi-pc systemd[1]: Started File System Check Daemon to report status.
Nov 06 17:30:39 yuvi-pc systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch being skipped.
Nov 06 17:30:39 yuvi-pc systemd[1]: Activating swap /dev/disk/by-uuid/a65f2578-10e0-4f1b-a6fb-498eee0fc1e9...
Nov 06 17:30:39 yuvi-pc systemd[1]: Activated swap /dev/disk/by-uuid/a65f2578-10e0-4f1b-a6fb-498eee0fc1e9.
Nov 06 17:30:39 yuvi-pc systemd[1]: Reached target Swap.
Nov 06 17:30:40 yuvi-pc systemd-fsck[413]: fsck.fat 4.1 (2017-01-24)
Nov 06 17:30:40 yuvi-pc systemd-fsck[413]: /dev/sda1: 9 files, 1307/121614 clusters
Nov 06 17:30:40 yuvi-pc systemd[1]: Started File System Check on /dev/disk/by-uuid/D0AB-B531.

[sunrat]

KSysguard works fine here on a Buster system so something is weird with yours. What version of Debian? How did you install it? It's impossible for us to guess with the information you have posted. Show us

Code: Select all

journalctl -b -p3

and install inxi and post

Code: Select all

inxi -Fx

[yuvarajvelmurugan]

KSysguard works fine here on a Buster system so something is weird with yours. What version of Debian? How did you install it? It's impossible for us to guess with the information you have posted. Show us

Code: Select all

journalctl -b -p3

and install inxi and post

Code: Select all

inxi -Fx

Step 1 - I downloaded debian from: https://cdimage.debian.org/debian-cd/cu ... so.torrent

Step 2 - Then created a bootable usb device using rufus tool.

Step 3 - I downloaded non-free firmware from: http://cdimage.debian.org/cdimage/unoff ... rmware.zip

Step 4 - Then created a folder name "firmware" in usb device.

Step 5 - Unzipped the non-free firmware to the firmware folder on usb device.

Step 6 - Modified boot priority in system bios setting to UEFI- something.

Step 7 - Installed debian on my hard drive with manual partition: sda1 UEFI, sda2 root, sda3 swap, sda4 home

hw-probe of my machine: https://linux-hardware.org/index.php?probe=0a7ea62580

journalctl -b -p3

Code: Select all

-- Logs begin at Fri 2020-11-06 23:40:17 IST, end at Fri 2020-11-06 23:42:01 IST. --
Nov 06 23:40:17 yuvi-pc kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
Nov 06 23:40:17 yuvi-pc kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT0._GTF, AE_NOT_FOUND (20180810/psparse-516)
Nov 06 23:40:17 yuvi-pc kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
Nov 06 23:40:17 yuvi-pc kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT0._GTF, AE_NOT_FOUND (20180810/psparse-516)

inxi -Fx

Code: Select all

System:    Host: yuvi-pc Kernel: 4.19.0-12-amd64 x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: KDE Plasma 5.14.5 
           Distro: Debian GNU/Linux 10 (buster) 
Machine:   Type: Desktop System: Gigabyte product: B250M-D3H v: N/A serial: N/A 
           Mobo: Gigabyte model: B250M-D3H-CF v: x.x serial: N/A UEFI: American Megatrends v: F9 date: 04/10/2018 
CPU:       Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB 
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31296 
           Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 
Graphics:  Device-1: Intel HD Graphics 630 vendor: Gigabyte driver: i915 v: kernel bus ID: 00:02.0 
           Display: x11 server: X.Org 1.20.4 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz 
           OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 4.5 Mesa 18.3.6 direct render: Yes 
Audio:     Device-1: Intel 200 Series PCH HD Audio vendor: Gigabyte driver: snd_hda_intel v: kernel bus ID: 00:1f.3 
           Sound Server: ALSA v: k4.19.0-12-amd64 
Network:   Device-1: Intel Ethernet I219-V vendor: Gigabyte driver: e1000e v: 3.2.6-k port: f040 bus ID: 00:1f.6 
           IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: i removed it 
Drives:    Local Storage: total: 931.51 GiB used: 739.41 GiB (79.4%) 
           ID-1: /dev/sda vendor: Seagate model: ST1000DM010-2EP102 size: 931.51 GiB temp: 38 C 
Partition: ID-1: / size: 78.35 GiB used: 8.70 GiB (11.1%) fs: ext4 dev: /dev/sda2 
           ID-2: /home size: 821.91 GiB used: 730.70 GiB (88.9%) fs: ext4 dev: /dev/sda4 
           ID-3: swap-1 size: 14.90 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda3 
Sensors:   System Temperatures: cpu: 37.0 C mobo: N/A 
           Fan Speeds (RPM): N/A 
Info:      Processes: 174 Uptime: 2h 51m Memory: 15.56 GiB used: 1004.7 MiB (6.3%) Init: systemd runlevel: 5 Compilers: 
           gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.32 

dmesg --level=emerg,alert,crit,err,warn

Code: Select all

[    0.000000] secureboot: Secure boot could not be determined (mode 0)
[    0.227082] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
[    0.227082]  #3
[    1.709763] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
[    1.709769] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT0._GTF, AE_NOT_FOUND (20180810/psparse-516)
[    1.710520] ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
[    1.710524] ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT0._GTF, AE_NOT_FOUND (20180810/psparse-516)

[sickpig]

When i switch to root user from terminal and launch the "sudo ksysguard" command it is displaying cpu and other history information graph.

root by default can not open graphical applications unless you have taken special pains to allow it. I have checked in normal netinst Debian and I get error message "cannot open display" when I try to open gui apps as root. Which is expected. I suppose the same is applicable in KDE as well?

[sunrat]

Nothing obvious there. ACPI errors are usually benign. Check if you have intel-microcode package installed (it's in non-free repo), it may help with the MDS CPU bug.
There are install images available which include nonfree firmware so you could have saved yourself that step.
Is the process monitor section of KSysguard working, just not the graphs?

Only thing I can suggest is to create a new user and see if the problem exists there in case there is corruption in your user profile, or maybe just rename ~/.kde to force it to create a new KDE user profile. It's a strange problem particularly on a freshly installed system.

[sunrat]

When i switch to root user from terminal and launch the "sudo ksysguard" command it is displaying cpu and other history information graph.

root by default can not open graphical applications unless you have taken special pains to allow it. I have checked in normal netinst Debian and I get error message "cannot open display" when I try to open gui apps as root. Which is expected. I suppose the same is applicable in KDE as well?

Generally true Mr. Pig. However I did try it (for science ) and was able to launch it with sudo albeit with the same warning messages OP got. I tried it with KWrite and got this:

Code: Select all

Executing KWrite with sudo is not possible due to unfixable security vulnerabilities.

So I assume KSysguard is "special"

[sickpig]

Thanks for checking. Well bravo KDE I guess for allowing root to have easy access to gui apps. My understanding is that its generally not advisable for root to access to X.

@OP you my want to check xsession errors as advised by hoas.

[yuvarajvelmurugan]

Nothing obvious there. ACPI errors are usually benign. Check if you have intel-microcode package installed (it's in non-free repo), it may help with the MDS CPU bug.
There are install images available which include nonfree firmware so you could have saved yourself that step.
Is the process monitor section of KSysguard working, just not the graphs?

Only thing I can suggest is to create a new user and see if the problem exists there in case there is corruption in your user profile, or maybe just rename ~/.kde to force it to create a new KDE user profile. It's a strange problem particularly on a freshly installed system.

Yup. You was right. The problem was with the user profile. Seems user profile corrupted, since home partition with data already existed during installation.

To check i created a new user profile and tested the new user login. It works good. So i deleted only the user profile which was creating problem and kept the data.

Then i removed all hidden files and folders inside the corrupted user profile folder.

Again recreated a user profile with same username and password which was deleted. I logged out of present session and then logged into the new user i created finally.

It works great.

[sunrat]

Good you got it working.
I always consider reusing old user profiles to be asking for problems, and sharing them between different distros is just illogical (although I see it recommended from time to time and also regularly see forum posts about resultant issues). Best to create a new one for a new installation and copy data over. If the old one is backed up it is possible to refer back to it for any special application settings if needed.