Discuss August 2018

discuss@lists.centos.org

80 participants
77 discussions

Centos 7.5..and My GDM Greeter/GDM Don't Work Anymore
by Paul E. Virgo 07 Aug '18

07 Aug '18

So, we've updated to 7.5, and for two machines--A Dell Precision M4800, and a Dell Precision 7510..both running Radeon cards--we no longer get the GDM Greeter login box NOR can we switch to virtual text login terminals. It's been driving me nuts. The systems do allow for SSH logins, so that's how we get to them, but I've checked the Xorg.0.log and nothing stands out. Did a systemctl status gdm.service and got this: > Aug 07 16:23:31 gs6102dsclxpvirgo3 gnome-shell[2023]: g_array_unref: > assertion 'array' failed > Aug 07 16:23:31 gs6102dsclxpvirgo3 gnome-shell[2023]: g_array_unref: > assertion 'array' failed > Aug 07 16:23:31 gs6102dsclxpvirgo3 gnome-shell[2023]: g_array_unref: > assertion 'array' failed > Aug 07 16:23:31 gs6102dsclxpvirgo3 gnome-shell[2023]: g_array_unref: > assertion 'array' failed > Aug 07 16:23:31 gs6102dsclxpvirgo3 gnome-shell[2023]: g_array_unref: > assertion 'array' failed > Aug 07 16:23:31 gs6102dsclxpvirgo3 gnome-session-binary[1926]: > WARNING: Could not get session path for session. Check that logind is > properly installed and pam_systemd is getting used at login. > Aug 07 16:23:31 gs6102dsclxpvirgo3 gnome-shell[2023]: g_array_unref: > assertion 'array' failed > Aug 07 16:23:31 gs6102dsclxpvirgo3 gnome-session[1926]: > gnome-session-binary[1926]: WARNING: Could not get session path for > session. Check that logind is properly installed and pam_systemd > is...ed at login. > Aug 07 16:23:31 gs6102dsclxpvirgo3 gnome-shell[2023]: g_array_unref: > assertion 'array' failed > Aug 07 16:23:32 gs6102dsclxpvirgo3 gnome-shell[2023]: JS ERROR: > Exception in callback for signal: reset: Gio.DBusError: > GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: No session available > LoginDialog<._resetGreeterProxy@resource:///org/gnome/shell/gdm/loginDialog.js:837:29 > wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22... Did the upgrade break something? Possibly. Any and all hints/ideas/etc. greatly welcomed. PEV -- Paul E Virgo Sr. System Administrator Code 610.2 SESDA III - DAAC/DISC Goddard Space Flight Ctr/NASA Greenbelt, MD Greenbelt, MD 20771 (301) 614-5751

1 0

Back to Xfce
by Robert Moskowitz 06 Aug '18

06 Aug '18

Now that the basic server is up and running. With Gnome via VNC (yuck), it is time to go back and figure out howto install Xfce without an Xfce group script. So I am asking those with X64 Centos for some pointers. Like where are the group scripts so maybe I can modify them for armhfp. I was reading: https://www.rootusers.com/how-to-install-xfce-gui-in-centos-7-linux/ Where the author talks about doing a minimal install then running: yum groupinstall "Server with GUI" But notes that this installs Gnome (which I don't want) and that instead to yum groupinstall “X Window System” But has concerns if this installs all needed followed up with yum groupinstall "Xfce" Thing is on armhfp, I do not have “X Window System” or "Xfce" I have come to understand that groups are scripts that install all the need rpms for the group. But I have not found where these scripts are so hopefully I can see them, figure out how to modify them for the armhfp rpms, and run them. So I am looking for pointers on where these are in tehx64 repos, and how to work with these scripts. thank you for your help..

3 8

rsync versioning problem
by Robert Moskowitz 06 Aug '18

06 Aug '18

I seem to have an rsync versioning problem. The sender is an old ClearOS6 server with rsynv 3.0.6 The receiver is a brand new Centos7-armv7 server with rsync 3.1.2 I am running rsync over ssh Got the error: rsync error: error in rsync protocol data stream (code 12) at io.c(600) [sender=3.0.6] And researching this it comes down to a versioning issue. But all I have found was to upgrade the 3.0.6 system! That will happen when I migrate to ClearOS7! Is there some option to specify to get this to work? rsync -ah --stats --delete -e "ssh" /var/flexshare/shares x.htt-consult.com:/media/backup/homebase/var/flexshare/shares/

2 6

Installing GCC 5.3.0 in CentOS 6 in Docker.
by Mohan Ganesalingam 06 Aug '18

06 Aug '18

I need to compile some C++ 11 with GCC 5.3.0 on CentOS 6. All of this is happening inside docker in CI using the centos:6 base image. (NB. It can't be GCC 6 or 7, because I have to send binaries to clients who won't install newer vs of libstdc++.so.) Until recently, I was installing devtoolset-4-gcc-c++ via yum, and then using RUN scl enable devtoolset-4 gcc to build the code. Unfortunately, devtoolset-4 is no longer supported, so this has stopped working. I've been trying to compile GCC from scratch, but it's been running for hours and hours – even if I get it working, I'll have to replicate the whole process inside Docker and I suspect it will be very brittle. Is there any easy way of downloading a precompiled version? E.g. -- Is there something that I can do to go back to the old v. of Software Collections? Or -- Is there somewhere I might find a precompiled gcc 5 package? Thanks very much, Mohan

1 0

Lenovo Ideapad 320 touchpad not recognized
by Frank Cox 04 Aug '18

04 Aug '18

I'm setting up a new Lenovo Ideapad 320 and everything shows up and works fine except for the touchpad. I did have to get into the bios and set Legacy for boot device and boot mode to get Centos 7 to finish installing. The default bios settings would load the Centos 7 Gnome Live image from a usb flash drive and work (except for the touchpad) but when I tried to install to the hard drive it would get to the end of the process and kernel panic when it was writing the bootloader. Setting Legacy Boot in the bios solved that problem. I have run yum update so everything is up to date. But the touchpad doesn't show up at all. [frankcox@localhost ~]$ cat list.txt ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ - Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ - Logitech USB Receiver id=8 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] - Virtual core XTEST keyboard id=5 [slave keyboard (3)] - Video Bus id=6 [slave keyboard (3)] - Power Button id=7 [slave keyboard (3)] - EasyCamera id=9 [slave keyboard (3)] - AT Translated Set 2 keyboard id=10 [slave keyboard (3)] - Ideapad extra buttons id=11 [slave keyboard (3)] The Logitech USB Receiver listed here is the wireless mouse that I'm using on it right now since the touchpad doesn't work. I've been reading everything I can find about this problem, tried a few different grub parameters that didn't help, and the most advanced solution that I've tried was this: https://superuser.com/questions/1156057/touchpad-not-working-on-centos-7-2 1. Add i8042.nopnp to grub command line in /etc/default/grub: # change this: GRUB_CMDLINE_LINUX_DEFAULT="... quiet splash" # to: GRUB_CMDLINE_LINUX_DEFAULT="... quiet splash i8042.nopnp" 2. Update your grub config (as root): # If you're using UEFI boot grub2-mkconfig -o /boot/efi/EFI/centos/grub.cfg # or legacy grub2-mkconfig -o /boot/grub2/grub.cfg 3. Blacklist module i2c_hid (as root): echo "blacklist i2c_hid" > /etc/modprobe.d/i2c-hid.conf 4. Regenerate your initramfs (as root): cp -v /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak dracut -f 5. Reboot! Unfortunately, that didn't change anything; xinput --list still doesn't show the touchpad. I have found references to some deb packages and fedora rpms that don't appear to exist for Centos 7: xorg-x11-drv-synaptics-legacy.x86_64 elantech-0608-dkms_0.2_all.deb I've pretty much run out of ideas. I checked the bios and don't see anything that appears to be related to the touchpad (not that I was really expecting to). -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com

1 0

How to set macaddr with nmcli
by Robert Moskowitz 03 Aug '18

03 Aug '18

I see my problem. I mis-read what nmcli con mod eth0 mac "02:67:15:00:81:0B" does. It sets HWADDR; which interface to link to, not MACADDR, what MAC address you want for your interface. So I have read the nmcli pages and googled a bit. I cannot find a way to set MACADDR. I suppose I can set HWADDR then use sed to change it to MACADDR, but this seems a real hack. ARM boards do not have assigned MAC addresses. Uboot uses various information to generate a local MAC address. I want finer control of my MAC address for my servers. In the past, I just edited ifcfg-eth0. I am trying now to do it all with nmcli. I thought I had it, but I misread the manual. Any pointers? thanks BTW, I remember setting MAC addresses on 3COM 3C501C boards because the old board died and we had software licensed to specific MAC addresses. So you had to specify your MAC address in the config file. The DEC admin had to do a similar thing if he had to swap out his LAN card (related: read up on why Dr. Comer set ARP timeout to 10min). Then there was that counterfeit 3C503C from Malaysia, all with the same MAC address. Caused havoc on the networks. EVERYONE had to specify their MAC address with those. 3COM did find the plant making these clones and shut them down. But the damage was done to a lot of us.

2 2

How to set macaddr with nmcli
by Robert Moskowitz 03 Aug '18

03 Aug '18

1 0

ifcfg-link?
by Robert Moskowitz 03 Aug '18

03 Aug '18

This is happening with the Centos7-armv7 image 1804, but I was wondering if it is a broader C7 issue. My image has only 2 ifcfg files: ifcfg-l0 and -link. 'ip a' is listing the ethernet as eth0. ifcfg-link has contains: DEVICE=link BOOTPROTO=dhcp ONBOOT=on I then used nmcli to create my ifcfg-eth0 nmcli con delete eth0 nmcli con add type ethernet con-name eth0 ifname eth0 ip4 192.168.129.11/25 gw4 192.168.129.1 nmcli con mod eth0 ipv4.dns "50.253.254.2 192.168.129.1" nmcli con mod eth0 mac "02:67:15:00:81:0B" I moved the cable to the 192.168.129.1 vlan (which does not have a dhcp server), and nmcli con up eth0 Error: Connection activation failed: No suitable device found for this connection. Oops. ? rebooting did not help. Came up with no address for interface eth0, yet no suitable device. Where would I look to find what may be happening here? I appreciate that this may be specific to armv7 and my Cubieboard2, but then again, it may be something known by other Centos people. Thanks for any help!

1 1

NFS/RDMA connection closed
by admin＠genome.arizona.edu 02 Aug '18

02 Aug '18

Hi, we are having a problem with NFS using RDMA protocol over our FDR10 Infiniband network. I previously wrote to NFS mailing list about this, so you may find our discussion there. I have taken some load off the server which was using NFS for backups, and converted it to use SSH, but we are still having critical problems with NFS clients losing connection to the server, causing the clients to hang and needing a reboot. I wanted to check in here before filing a bug with CentOS. Our setup is a cluster with one head node (NFS server) and 9 compute nodes (NFS clients). All the machines are running CentOS 6.9 2.6.32-696.30.1.el6.x86_64 and using the "Inbox"/CentOS RDMA implementation/drivers (not Mellanox OFED). (We also have other NFS clients but they are using 1GbE for NFS connection and, while they will still hang with messages like "NFS server not responding, retrying" or "timed out", they will eventually recover and don't need a reboot.) On the server (which is named pac) I will see messages like this: Jul 30 18:19:38 pac kernel: svcrdma: failed to send reply chunks, rc=-5 Jul 30 18:19:38 pac kernel: svcrdma: failed to send write chunks, rc=-5 Jul 31 15:03:05 pac kernel: svcrdma: failed to send write chunks, rc=-5 Jul 31 15:09:06 pac kernel: svcrdma: failed to send write chunks, rc=-5 Jul 31 15:16:09 pac kernel: svcrdma: failed to send write chunks, rc=-5 Jul 31 15:23:31 pac kernel: svcrdma: Error -107 posting RDMA_READ Jul 31 15:53:55 pac kernel: svcrdma: failed to send write chunks, rc=-5 Jul 31 16:09:19 pac kernel: svcrdma: failed to send reply chunks, rc=-5 Jul 31 16:09:19 pac kernel: svcrdma: failed to send reply chunks, rc=-5 Previously I had also seen messages like "Jul 11 21:09:56 pac kernel: nfsd: peername failed (err 107)!" however have not seen that in this latest hangup. And on the clients (named n001-n009) I will see messages like this: Jul 30 18:17:26 n001 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff8810674024c0 (stale): WR flushed Jul 30 18:17:26 n001 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff88106638a640 (stale): WR flushed Jul 30 18:19:26 n001 kernel: nfs: server 10.10.11.100 not responding, still trying Jul 30 18:19:36 n001 kernel: nfs: server 10.10.10.100 not responding, timed out Jul 30 18:19:38 n001 kernel: rpcrdma: connection to 10.10.11.100:20049 on mlx4_0, memreg 5 slots 32 ird 16 Jul 30 18:19:38 n001 kernel: nfs: server 10.10.11.100 OK Jul 31 14:42:08 n001 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff8810671f02c0 (stale): WR flushed Jul 31 14:42:08 n001 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff8810677bda40 (stale): WR flushed Jul 31 14:42:08 n001 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff8810677bd940 (stale): WR flushed Jul 31 14:42:08 n001 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff8810671f0240 (stale): WR flushed Jul 31 14:43:35 n001 kernel: rpcrdma: connection to 10.10.11.100:20049 on mlx4_0, memreg 5 slots 32 ird 16 Jul 31 15:01:53 n001 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff881065133140 (stale): WR flushed Jul 31 15:01:53 n001 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff8810666e3f00 (stale): WR flushed Jul 31 15:01:53 n001 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff881063ea0dc0 (stale): WR flushed Jul 31 15:01:53 n001 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff8810677bdb40 (stale): WR flushed Jul 31 15:03:05 n001 kernel: rpcrdma: connection to 10.10.11.100:20049 on mlx4_0, memreg 5 slots 32 ird 16 Jul 31 15:07:07 n001 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff881060e59d40 (stale): WR flushed Jul 31 15:07:07 n001 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff8810677efac0 (stale): WR flushed Jul 31 15:07:07 n001 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff88106638a640 (stale): WR flushed Jul 31 15:07:07 n001 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff8810671f03c0 (stale): WR flushed Jul 31 15:09:06 n001 kernel: rpcrdma: connection to 10.10.11.100:20049 on mlx4_0, memreg 5 slots 32 ird 16 Jul 31 15:16:09 n001 kernel: rpcrdma: connection to 10.10.11.100:20049 closed (-103) Jul 31 15:53:32 n001 kernel: nfs: server 10.10.10.100 not responding, timed out Jul 31 16:08:56 n001 kernel: nfs: server 10.10.10.100 not responding, timed out Jul 30 18:17:26 n002 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff881064461500 (stale): WR flushed Jul 30 18:17:26 n002 kernel: RPC: rpcrdma_sendcq_process_wc: frmr ffff8810604b2600 (stale): WR flushed Jul 30 18:19:26 n002 kernel: nfs: server 10.10.11.100 not responding, still trying Jul 30 18:19:38 n002 kernel: rpcrdma: connection to 10.10.11.100:20049 on mlx4_0, memreg 5 slots 32 ird 16 Jul 30 18:19:38 n002 kernel: nfs: server 10.10.11.100 OK Jul 31 14:43:35 n002 kernel: rpcrdma: connection to 10.10.11.100:20049 closed (-103) Jul 31 16:08:56 n002 kernel: nfs: server 10.10.10.100 not responding, timed out Similar messages show up on the other clients n003-n009. After these messages on the clients, their load will continually go up (viewable through Ganglia) (I would guess since they are waiting for NFS mount to re-appear). They aren't reachable any longer through SSH and neither can root log in through console via IPMI web applet (just hangs after entering password, may get to prompt eventually but system load is so high), they need to be rebooted through IPMI interface. Here is /etc/fstab on the server, UUID=f15df051-ffb8-408c-8ad2-1987b6f082a2 / ext3 defaults 0 1 UUID=c854ee27-32cf-445d-8308-4e6f1a87d364 /boot ext3 defaults 0 2 UUID=b92a100f-2521-408b-9b15-93671c6ae056 swap swap defaults 0 0 UUID=a8a7b737-25ed-43a7-ae4b-391c71aa8c08 /data xfs defaults 0 2 UUID=d5692ec2-d5dc-4bb8-98d4-a4fb2ff54748 /projects xfs defaults 0 2 /dev/drbd0 /newwing xfs noauto 0 0 UUID=a305f309-d997-43ec-8e4f-78e26b07652f /working xfs defaults 0 2 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0 I read that adding "inode64,nobarrier" for the xfs mount options may help? That is something I can try once the server can be rebooted. Here is current mounts on the server, /dev/sda3 on / type ext3 (rw) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) tmpfs on /dev/shm type tmpfs (rw) /dev/sda1 on /boot type ext3 (rw) /dev/sdc1 on /data type xfs (rw) /dev/sdb1 on /projects type xfs (rw) /dev/sde1 on /working type xfs (rw,nobarrier) none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw) sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) nfsd on /proc/fs/nfsd type nfsd (rw) /dev/drbd0 on /newwing type xfs (rw) Here is /etc/exports on the server, /data 10.10.10.0/24(rw,no_root_squash,async) /data 10.10.11.0/24(rw,no_root_squash,async) /data 150.x.x.192/27(rw,no_root_squash,async) /data 150.x.x.64/26(rw,no_root_squash,async) /home 10.10.10.0/24(rw,no_root_squash,async) /home 10.10.11.0/24(rw,no_root_squash,async) /opt 10.10.10.0/24(rw,no_root_squash,async) /opt 10.10.11.0/24(rw,no_root_squash,async) /projects 10.10.10.0/24(rw,no_root_squash,async) /projects 10.10.11.0/24(rw,no_root_squash,async) /projects 150.x.x.192/27(rw,no_root_squash,async) /projects 150.x.x.64/26(rw,no_root_squash,async) /tools 10.10.10.0/24(rw,no_root_squash,async) /tools 10.10.11.0/24(rw,no_root_squash,async) /usr/share/gridengine 10.10.10.10/24(rw,no_root_squash,async) /usr/share/gridengine 10.10.11.10/24(rw,no_root_squash,async) /usr/local 10.10.10.10/24(rw,no_root_squash,async) /usr/local 10.10.11.10/24(rw,no_root_squash,async) /working 10.10.10.0/24(rw,no_root_squash,async) /working 10.10.11.0/24(rw,no_root_squash,async) /working 150.x.x.192/27(rw,no_root_squash,async) /working 150.x.x.64/26(rw,no_root_squash,async) /newwing 10.10.10.0/24(rw,no_root_squash,async) /newwing 10.10.11.0/24(rw,no_root_squash,async) /newwing 150.x.x.192/27(rw,no_root_squash,async) /newwing 150.x.x.64/26(rw,no_root_squash,async) The 10.10.10.0/24 network is 1GbE and the 10.10.11.0/24 is the Infiniband. The other networks are also 1GbE. Our cluster nodes will normally mount all of these using the Infiniband with RDMA and the computation jobs will normally be using /working which will see the most reading/writing but /newwing, /projects, and /data are also used. Here is an /etc/fstab from the nodes, #NFS/RDMA #10.10.11.100:/opt /opt nfs rdma,port=20049 0 0 #10.10.11.100:/data /data nfs rdma,port=20049 0 0 #10.10.11.100:/tools /tools nfs rdma,port=20049 0 0 #10.10.11.100:/home /home nfs rdma,port=20049 0 0 #10.10.11.100:/usr/local /usr/local nfs rdma,port=20049 0 0 #10.10.11.100:/usr/share/gridengine /usr/share/gridengine nfs rdma,port=20049 0 0 #10.10.11.100:/projects /projects nfs rdma,port=20049 0 0 #10.10.11.100:/working /working nfs rdma,port=20049 0 0 #10.10.11.100:/newwing /newwing nfs rdma,port=20049 0 0 #NFS/IPoIB 10.10.11.100:/opt /opt nfs tcp 0 0 10.10.11.100:/data /data nfs tcp 0 0 10.10.11.100:/tools /tools nfs tcp 0 0 10.10.11.100:/home /home nfs tcp 0 0 10.10.11.100:/usr/local /usr/local nfs tcp 0 0 10.10.11.100:/usr/share/gridengine /usr/share/gridengine nfs tcp 0 0 10.10.11.100:/projects /projects nfs tcp 0 0 10.10.11.100:/working /working nfs tcp 0 0 10.10.11.100:/newwing /newwing nfs tcp 0 0 #NFS/TCP #10.10.10.100:/opt /opt nfs defaults 0 0 #10.10.10.100:/data /data nfs defaults 0 0 #10.10.10.100:/tools /tools nfs defaults 0 0 #10.10.10.100:/home /home nfs defaults 0 0 #10.10.10.100:/usr/local /usr/local nfs defaults 0 0 #10.10.10.100:/usr/share/gridengine /usr/share/gridengine nfs defaults 0 0 #10.10.10.100:/projects /projects nfs defaults 0 0 #10.10.10.100:/working /working nfs defaults 0 0 #10.10.10.100:/newwing /newwing nfs defaults 0 0 Here I can switch between different interfaces/protocols for the NFS mounts. Currently we are trying the IPoIB. We haven't started a cluster job yet so not sure how it will perform. With the NFS/TCP over 1GbE the server/nodes would hang from time to time but still did not crash at least, however was of course slow being limited by 1GbE. We haven't had this problem until recently. I upgraded our cluster to add the two additional nodes (n008 and n009) and we also added more storage to the server (/newwing and /working). The new nodes are AMD EPYC platform whereas the server and the nodes n001-n007 are Intel Xeon platform, not sure if that would cause such a crash. The new nodes were cloned from n001 and only kernel command line and network parameters were changed. The jobs are submitted to the cluster via Sun Grid Engine, and in total there are about 61 jobs that may start at once and open connections to the NFS server... it sounds like it is a system overload, although the load on the server remains low, under 10%, even as it hangs the load may increase to 80%. The server is a few years old but still has 2x 6-core Intel Xeon E5-2620 v2 @ 2.10GHz with 128GB of RAM. Would appreciate your assistance to troubleshoot this critical problem and, if needed, gather the required information to submit a bug to the tracker! Thanks, -- Chandler Arizona Genomics Institute www.genome.arizona.edu

1 1

Desktop lag with CentOS7/Mate and high CPU usage
by James Pearson 02 Aug '18

02 Aug '18

We have noticed significant desktop/UI lag on CentOS7 workstations using Mate when the CPU usage is high - i.e. the mouse pointer lags and moving windows (e.g. terminal windows) become jumpy (not smooth) We didn't see (or notice) this issue with CentOS6/Gnome2 This can easily be shown by running something like 'cpuburn' (https://patrickmn.com/projects/cpuburn/) and moving a mate-terminal window around the screen We can make things 'better' by running CPU intensive apps via 'nice' (without any noticeable performance hit to the CPU intensive app) - but this is a rather messy way of fixing the issue We can also make things better by renice'ing X to a negative nice level However, both these approaches seem wrong to me - as I'm probably missing something straightforward here Does anyone know of any CentOS7/Mate settings that could be used to improve desktop/UI responsiveness with high CPU usage ? Thanks James Pearson

5 5

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss August 2018