#StackBounty: #centos #gnome #mate-desktop How do we enable quick launcher and Min,max button in MATE (CentOS)?

Bounty: 50

I have installed MATE desktop environment in my CentOS (version 7.5 x64). But there is no quick launcher ‘applications’ button and also my VS code installation doesn’t have min,max,close buttons.

I have used below command to install MATE desktop.

yum -y groupinstall "MATE Desktop"

What is wrong? enter image description here

In Gnome 3 desktop, ‘application’ button shown as below. how to enable ‘application’ button in MATE?

enter image description here


Get this bounty!!!

#StackBounty: #centos #redhat #mount #loop-device loop device does not auto detach on umount

Bounty: 50

I have a backup script in which I umount a squashfs file, I do backup then mount it back again. A simplified version of the script is:

umount /home/backup/auto/mnt/os
mksquashfs /src-dir /home/backup/auto/os.sqfs.img
mount -t squashfs -o loop /home/backup/auto/os.sqfs.img /home/backup/auto/mnt/os

The idea is to have access at all times to backedup data.

And this worked for long time. However I got an error of not having enough loopback devices and I saw that umount does not detach loop devices mounted with mount anymore.

Lately I had two major changes:

  1. I updated the kernel to 2.6.32-754.11.1.el6.i686
  2. I moved the OS to an SSD.

I just noticed that there is new kernel update 2.6.32-754.12.1.el6, so I updated, but it did not fix the problem.

OS: CentOS 6.10


Get this bounty!!!

#StackBounty: #centos #x11 #gnome #nvidia #nouveau GNOME issues on a laptop with Nvidia GEForce graphic card

Bounty: 50

I have installed CentOS 7 on dual boot on an 10ish-year-old Toshiba Qosmio laptop which came with Windows 7.

I did the minimal install, yum update, then installed the “GNOME desktop” group package and started GNOME via startx. It worked for some seconds, then it froze when I selected the options for power management.

After reboot, it asks the LUKS password, it shows the GNOME prompt to select the user, then the screen stays black while the CPU fan turns like mad. After a few minutes the CapsLock key light starts blinking.

I’ve tried to boot at GRUB with a previous kernel version but it does the same, except for the CapsLock key light.

The laptop has a Nvidia GEForce GTX 560m, might the cause be a wrong graphic driver?


EDIT 22/3: I removed the nouveau driver and installed the appropriate Nvidia graphic driver as described here. System is set to boot to multi-user.target.

Now when I run startx the screen goes black for a split second and then outputs the following error:

xauth:  file /home/dr/.serverauth.6309 does not exist


X.Org X Server 1.20.1
X Protocol Version 11, Revision 0
Build Operating System:  3.10.0-957.1.3.el7.x86_64
Current Operating System: Linux hackbox 3.10.0-957.10.1.el7.x86_64 #1 SMP Mon Mar 18 15:06:45 UTC 2019 x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-3.10.0-957.10.1.el7.x86_64 root=UUID=3a27c3be-ea50-4548-92db-53879292b3aa ro rd.luks.uuid=luks-fac75b1c-2869-4923-8ff1-0e7e7e868dd3 rd.luks.uuid=luks-735bf876-be70-40a4-ac81-f6c6ab46b542 rhgb quiet nouveau.modeset=0
Build Date: 14 March 2019  10:37:36AM
Build ID: xorg-x11-server 1.20.1-5.3.el7_6
Current version of pixman: 0.34.0
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat Mar 23 11:40:25 2019
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
xinit: connection to X server lost

waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.

Here are the relevant lines from /var/log/Xorg.0.log, reporting only the lines with warnings or errors:

(...)
[   409.722] (II) modeset(0): using drv /dev/dri/card0
[   409.722] (WW) Falling back to old probe method for fbdev
[   409.722] (II) Loading sub module "fbdevhw"
[   409.722] (II) LoadModule: "fbdevhw"
[   409.722] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
[   409.723] (II) Module fbdevhw: vendor="X.Org Foundation"
[   409.723]    compiled for 1.20.1, module version = 0.0.2
[   409.723]    ABI class: X.Org Video Driver, version 24.0
[   409.723] (EE) [drm] Failed to open DRM device for (null): -2
[   409.724] (II) modeset(0): Creating default Display subsection in Screen section
        "Default Screen Section" for depth/fbbpp 24/32
[   409.724] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[   409.724] (==) modeset(0): RGB weight 888
[   409.724] (==) modeset(0): Default visual is TrueColor
[   409.724] (II) Loading sub module "glamoregl"
[   409.724] (II) LoadModule: "glamoregl"
[   409.725] (WW) Warning, couldn't open module glamoregl
[   409.725] (EE) modeset: Failed to load module "glamoregl" (module does not exist, 0)
[   409.725] (EE) modeset(0): Failed to load glamor module.
(...)
[   409.766] (II) Initializing extension GLX
[   409.766] (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
(...)

and the output of lsmod | grep nvidia :

nvidia_drm             39676  0
nvidia_modeset       1108588  1 nvidia_drm
nvidia              14368631  1 nvidia_modeset
ipmi_msghandler        56032  2 ipmi_devintf,nvidia
drm_kms_helper        179394  3 i915,nouveau,nvidia_drm
drm                   429744  6 ttm,i915,drm_kms_helper,nouveau,nvidia_drm

EDIT 28/3: It seems that glamoregl is part of the ATI driver framework and does not work with Nvidia. So I uninstalled xorg-x11-glamor (and had to reinstall xorg-x11-server which was deleted as a dependency).

The X log reported errors about missing fbdev and vesa drivers, so I installed xorg-x11-drv-fbdev-0.5.0-1.el7.x86_64 and
xorg-x11-drv-vesa.x86_64.

I also installed xorg-x11-drv-nouveau.x86_64 and reenabled it from the kernel options in GRUB.

Now startx correctly starts Gnome but it doesn’t accept any keypress or mouse input. Gnome however is functional, because the clock in the upper right corner works, and I can run commands on this X instance by ssh’ing to the laptop from a different computer and launching GUI programs by specifying the target display, e.g.:

DISPLAY=:3 gedit

which opens the Gedit application on the laptop screen.

Note that the X log doesn’t contain any error, only a warning:

[   197.636] (WW) Falling back to old probe method for fbdev


Get this bounty!!!

#StackBounty: #centos #x11 #gnome #nvidia #nouveau GNOME does not boot on a Toshiba laptop with Nvidia GEForce

Bounty: 50

I have installed CentOS 7 on dual boot on an 10ish-year-old Toshiba Qosmio laptop which came with Windows 7.

I did the minimal install, yum update, then installed the “GNOME desktop” group package and started GNOME via startx. It worked for some seconds, then it froze when I selected the options for power management.

After reboot, it asks the LUKS password, it shows the GNOME prompt to select the user, then the screen stays black while the CPU fan turns like mad. After a few minutes the CapsLock key light starts blinking.

I’ve tried to boot at GRUB with a previous kernel version but it does the same, except for the CapsLock key light.

The laptop has a Nvidia GEForce GTX 560m, might the cause be a wrong graphic driver?


EDIT 1: I removed the nouveau driver and installed the appropriate Nvidia graphic driver as described here. System is set to boot to multi-user.target.

Now when I run startx the screen goes black for a split second and then outputs the following error:

xauth:  file /home/dr/.serverauth.6309 does not exist


X.Org X Server 1.20.1
X Protocol Version 11, Revision 0
Build Operating System:  3.10.0-957.1.3.el7.x86_64
Current Operating System: Linux hackbox 3.10.0-957.10.1.el7.x86_64 #1 SMP Mon Mar 18 15:06:45 UTC 2019 x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-3.10.0-957.10.1.el7.x86_64 root=UUID=3a27c3be-ea50-4548-92db-53879292b3aa ro rd.luks.uuid=luks-fac75b1c-2869-4923-8ff1-0e7e7e868dd3 rd.luks.uuid=luks-735bf876-be70-40a4-ac81-f6c6ab46b542 rhgb quiet nouveau.modeset=0
Build Date: 14 March 2019  10:37:36AM
Build ID: xorg-x11-server 1.20.1-5.3.el7_6
Current version of pixman: 0.34.0
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sat Mar 23 11:40:25 2019
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
xinit: connection to X server lost

waiting for X server to shut down (II) Server terminated successfully (0). Closing log file.

Here are the relevant lines from /var/log/Xorg.0.log, reporting only the lines with warnings or errors:

(...)
[   409.722] (II) modeset(0): using drv /dev/dri/card0
[   409.722] (WW) Falling back to old probe method for fbdev
[   409.722] (II) Loading sub module "fbdevhw"
[   409.722] (II) LoadModule: "fbdevhw"
[   409.722] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
[   409.723] (II) Module fbdevhw: vendor="X.Org Foundation"
[   409.723]    compiled for 1.20.1, module version = 0.0.2
[   409.723]    ABI class: X.Org Video Driver, version 24.0
[   409.723] (EE) [drm] Failed to open DRM device for (null): -2
[   409.724] (II) modeset(0): Creating default Display subsection in Screen section
        "Default Screen Section" for depth/fbbpp 24/32
[   409.724] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[   409.724] (==) modeset(0): RGB weight 888
[   409.724] (==) modeset(0): Default visual is TrueColor
[   409.724] (II) Loading sub module "glamoregl"
[   409.724] (II) LoadModule: "glamoregl"
[   409.725] (WW) Warning, couldn't open module glamoregl
[   409.725] (EE) modeset: Failed to load module "glamoregl" (module does not exist, 0)
[   409.725] (EE) modeset(0): Failed to load glamor module.
(...)
[   409.766] (II) Initializing extension GLX
[   409.766] (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
(...)

and the output of lsmod | grep nvidia :

nvidia_drm             39676  0
nvidia_modeset       1108588  1 nvidia_drm
nvidia              14368631  1 nvidia_modeset
ipmi_msghandler        56032  2 ipmi_devintf,nvidia
drm_kms_helper        179394  3 i915,nouveau,nvidia_drm
drm                   429744  6 ttm,i915,drm_kms_helper,nouveau,nvidia_drm

EDIT 2: It seems that glamoregl is part of the ATI driver framework and does not work with Nvidia. So I uninstalled xorg-x11-glamor (and reinstalled xorg-x11-server which was deleted as a dependency).

Now startx starts Gnome but it is unresponsive: it doesn’t accept any keypress, and the mouse pointer doesn’t move. The system isn’t frozen or crashed though, because the clock in the upper right corner works.


Get this bounty!!!

#StackBounty: #linux #centos #password #expired #xrdp Issues with expired passwords using XRDP in CentOS

Bounty: 100

I am running a series of docker containers running an xfce desktop which can only be accessed via xrdp. I set password restrictions and expired the current passwords of all users expecting to get a prompt through xrdp on the next login to change the password.

I would expect, once the user enters their (now expired) password they would be prompted to change the password and it would allow a login. xrdp, however, simply fails with a “login failed for display 0”.

Is there a setting I’m missing within xrdp that would allow for password reset / changes on login?


Get this bounty!!!

#StackBounty: #linux #networking #centos #monitoring How to show realtime traffic on each virtual network interface?

Bounty: 300

I have a dedicated server with a few virtual network interfaces, each mapped to a public IP address. How can I monitor the realtime traffic (in packets/s or Mb/s) of each of them, ideally on a single screen?

What I’m looking for is something like:

eth0:0 123 packets/s
eth0:1 234 packets/s
eth0:2 345 packets/s

I tried iptraf, iftop, jnettop, but I could not get any of them to group the display by virtual interface: they all show the whole eth0.

Note that I’m open to other tools, as long as they’re available on CentOS (+ EPEL / remi).


Get this bounty!!!

#StackBounty: #hard-drive #centos #ext4 Getting an “is not a block special device.” error when trying to mount an 8TB disk in CentOS 7.6

Bounty: 50

I’m trying to format and mount a 8TB external as an ext4 and it doesn’t seem to work right.

I can create my partition using gdisk:

sdc               8:32   0   7.3T  0 disk
└─sdc1            8:33   0   7.3T  0 part

But when I create the filesystem I get a weird error that says: “/dev/sdc1 is not a block special device.” however it seems to complete:

# mke2fs -t ext4 /dev/sdc1
mke2fs 1.42.9 (28-Dec-2013)
/dev/sdc1 is not a block special device.
Proceed anyway? (y,n) y
Discarding device blocks: done
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
246512 inodes, 984801 blocks
49240 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=1008730112
31 block groups
32768 blocks per group, 32768 fragments per group
7952 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376, 294912, 819200, 884736

Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done

Afterwards though, when mounting it doesn’t seem to work and it mounts /dev/loop0 instead? I’m not even sure what that is and the filesystem is the wrong size.

/dev/loop0               4.0G   16M  3.7G   1% /mnt/test

I was reading apparently this is some new type of drive with sectors not in the normal place? Any help would be appreciated.


Get this bounty!!!

#StackBounty: #postgresql #backup #centos #pgpool Postgres 9.6 – Taking differenctial backup

Bounty: 100

I have a few CentOS boxes running Postgres 9.6. I am planning a central server which can make local copies of all DBs on the other servers. These servers are accessible via SSH on Internet.

What is the best approach to take differential backup? I am considering below points :

  1. Central Backup Server may not be up 24/7.
  2. Internet Link may fail.
  3. Bandwidth Consumption on the DB server.

And I am considering the below approaches :

  1. Directly Rsync the Postgres data directory.
  2. Some kind of log archive, to be read by Postgres.
  3. Best of open source solution such as the pitrtool or pgpool2.

Which is the most efficient or even possible from above? Any other recommendation?


Get this bounty!!!