After CentOS 8 update, recurring stuck icons on desktop

mathog · 2020-07-16 16:40:06

First post here.

I recently updated an existing CentOS 8 system to 8.2.2004, and that upgraded XFCE4 (most of the RPMs have 4.14 in the version number). Since then the system keeps getting a stuck icon at or near the center of the screen. The first time it was a wristwatch, the second time (after a reboot) it was a hand icon. This icon is the topmost object, so it is always partially obscuring my work. These are about the same size as the icons in the strip along the top of the screen. In both cases the vertical position seems to be exactly midscreen, and the horizontal position is either dead center (the watch) or slightly right of that (the hand). The only applications running were Firefox (68.10.0esr) and Terminal (0.8.9.2). The stray icon is present on all 4 desktops, even though only one was in use. It stays there even if X11 is exited and restarted, or X11 is exited and the session logged out/logged in. If the system is shutdown completely (and left off overnight, although that might not be relevant) the system comes up without the icon. Then another one appears a short time later. So far there has only been one stuck icon at a time.

Anybody seen this and know of a way to make it stop?

Is there an application one can run which will identify the process that owns graphic elements on the desktop? (Ie, start the identifier, move the cursor over the element, and in some other window it shows the PID of the owning process.)

I suppose this could also be due to the video driver (mgag200) or Xorg (which updated
from 1.20.3 to 1.20.6).

The only other X11 related change I have noticed is that the system now starts up with one Terminal window open. Previously it started with a blank desktop (which is how I would like it to be once again.)

Thanks.

Note added 1: the stuck icon apparently forms at the location of the cursor shortly after the windows appear. If immediately after "startxfce4" the mouse is moved quickly to the right side of the screen the stuck icon will form there. It is still present, but at least less of a nuisance.

Note added 2: Discovered that there was both a saved session and the "save session" option was now checked on logout. Removed the saved session and unchecked that box. That got rid of the unwanted terminal startup, but had no effect on the stray icon.

Note added 3: After about an hour using this desktop the hand icon disappeared and the watch icon appeared in a different place on the desktop. This watch icon is not centered, it is probably wherever the cursor was when this transition occurred.

Last edited by mathog (2020-07-16 17:44:42)

Jerry3904 · 2020-07-16 20:01:09

Did you go to Session and Startup, and click the button to "Clear saved sessions"?

mathog · 2020-07-16 20:56:48

Jerry3904 wrote:

Did you go to Session and Startup, and click the button to "Clear saved sessions"?

Yes. That got rid of the autostarting Terminal but the icon problem remains. (While in there I also turned off "Geoclue Demo Agent", which also made no difference.)

ToZ · 2020-07-16 21:25:08

I'm leaning towards video artifact, but does disabling the compositor (Settings Manager > Window Manager Tweaks > Compositor tab) make a difference?

mathog · 2020-07-16 23:41:24

ToZ wrote:

I'm leaning towards video artifact, but does disabling the compositor (Settings Manager > Window Manager Tweaks > Compositor tab) make a difference?

That was toggled off and on a couple of times and the watch icon didn't even blink or move. Also, I cannot see any difference in the display between the two settings so I guess I might as well leave that off.

It be a video problem. That circuitry is on the motherboard, lscpi shows it as:

03:03.0 VGA compatible controller: Matrox Electronics Systems Ltd. MGA G200eW WPCM450 (rev 0a)
Subsystem: Dell Device 04de
Kernel driver in use: mgag200
Kernel modules: mgag200

The previous driver level issues I have encountered were nothing like this though. They were always something much more complex, like tearing or stuttering on video playback.

Last edited by mathog (2020-07-16 23:42:10)

ToZ · 2020-07-17 00:03:50

Can you post your Xorg.0.log file?

mathog · 2020-07-17 16:59:38

ToZ wrote:

Can you post your Xorg.0.log file?

This is the current Xorg.0.log. At the moment there is a "hand" icon near the middle of the screen.

Thanks for looking at it.

[    47.337] 
X.Org X Server 1.20.6
X Protocol Version 11, Revision 0
[    47.338] Build Operating System:  4.19.34-300.el7.x86_64 
[    47.339] Current Operating System: Linux poweredge.cluster 4.18.0-193.6.3.el8_2.x86_64 #1 SMP Wed Jun 10 11:09:32 UTC 2020 x86_64
[    47.339] Kernel command line: BOOT_IMAGE=(hd0,msdos1)/vmlinuz-4.18.0-193.6.3.el8_2.x86_64 root=UUID=d99fdaf2-7845-4734-9658-9f5f91a9042e ro crashkernel=auto resume=UUID=72a5c615-f54c-44f3-a064-314b14421514 nosplash
[    47.341] Build Date: 24 April 2020  02:49:29AM
[    47.341] Build ID: xorg-x11-server 1.20.6-3.el8 
[    47.342] Current version of pixman: 0.38.4
[    47.342] 	Before reporting problems, check [url]http://wiki.x.org[/url]
	to make sure that you have the latest version.
[    47.343] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[    47.345] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Jul 17 09:39:17 2020
[    47.365] (==) Using config directory: "/etc/X11/xorg.conf.d"
[    47.366] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    47.403] (==) No Layout section.  Using the first Screen section.
[    47.403] (==) No screen section available. Using defaults.
[    47.403] (**) |-->Screen "Default Screen Section" (0)
[    47.403] (**) |   |-->Monitor "<default monitor>"
[    47.403] (==) No monitor specified for screen "Default Screen Section".
	Using a default monitor configuration.
[    47.403] (==) Automatically adding devices
[    47.403] (==) Automatically enabling devices
[    47.403] (==) Automatically adding GPU devices
[    47.403] (==) Automatically binding GPU devices
[    47.409] (==) Max clients allowed: 256, resource mask: 0x1fffff
[    47.438] (**) FontPath set to:
	/usr/share/fonts/msttcore,
	catalogue:/etc/X11/fontpath.d,
	built-ins
[    47.438] (==) ModulePath set to "/usr/lib64/xorg/modules"
[    47.438] (II) The server relies on udev to provide the list of input devices.
	If no devices become available, reconfigure udev or disable AutoAddDevices.
[    47.438] (II) Loader magic: 0x5635cbef0020
[    47.438] (II) Module ABI versions:
[    47.438] 	X.Org ANSI C Emulation: 0.4
[    47.438] 	X.Org Video Driver: 24.0
[    47.438] 	X.Org XInput driver : 24.1
[    47.438] 	X.Org Server Extension : 10.0
[    47.440] (++) using VT number 1

[    47.440] (--) controlling tty is VT number 1, auto-enabling KeepTty
[    47.444] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_31
[    47.445] (II) xfree86: Adding drm device (/dev/dri/card0)
[    47.445] (II) Platform probe for /sys/devices/pci0000:00/0000:00:1e.0/0000:03:03.0/drm/card0
[    47.446] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 0
[    47.449] (--) PCI:*(3@0:3:0) 102b:0532:1028:04de rev 10, Mem @ 0xc0000000/8388608, 0xc1000000/16384, 0xc0800000/8388608, BIOS @ 0x????????/131072
[    47.449] (II) LoadModule: "glx"
[    47.475] (II) Loading /usr/lib64/xorg/modules/extensions/libglx.so
[    47.535] (II) Module glx: vendor="X.Org Foundation"
[    47.535] 	compiled for 1.20.6, module version = 1.0.0
[    47.535] 	ABI class: X.Org Server Extension, version 10.0
[    47.535] (==) Matched modesetting as autoconfigured driver 0
[    47.535] (==) Matched fbdev as autoconfigured driver 1
[    47.535] (==) Matched vesa as autoconfigured driver 2
[    47.535] (==) Assigned the driver to the xf86ConfigLayout
[    47.535] (II) LoadModule: "modesetting"
[    47.535] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[    47.549] (II) Module modesetting: vendor="X.Org Foundation"
[    47.549] 	compiled for 1.20.6, module version = 1.20.6
[    47.549] 	Module class: X.Org Video Driver
[    47.549] 	ABI class: X.Org Video Driver, version 24.0
[    47.549] (II) LoadModule: "fbdev"
[    47.549] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
[    47.558] (II) Module fbdev: vendor="X.Org Foundation"
[    47.558] 	compiled for 1.20.3, module version = 0.5.0
[    47.558] 	Module class: X.Org Video Driver
[    47.558] 	ABI class: X.Org Video Driver, version 24.0
[    47.558] (II) LoadModule: "vesa"
[    47.558] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
[    47.562] (II) Module vesa: vendor="X.Org Foundation"
[    47.562] 	compiled for 1.20.3, module version = 2.4.0
[    47.562] 	Module class: X.Org Video Driver
[    47.562] 	ABI class: X.Org Video Driver, version 24.0
[    47.562] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    47.562] (II) FBDEV: driver for framebuffer: fbdev
[    47.562] (II) VESA: driver for VESA chipsets: vesa
[    47.562] (II) modeset(0): using drv /dev/dri/card0
[    47.562] (WW) Falling back to old probe method for fbdev
[    47.562] (II) Loading sub module "fbdevhw"
[    47.562] (II) LoadModule: "fbdevhw"
[    47.569] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
[    47.576] (II) Module fbdevhw: vendor="X.Org Foundation"
[    47.576] 	compiled for 1.20.6, module version = 0.0.2
[    47.576] 	ABI class: X.Org Video Driver, version 24.0
[    47.577] (II) modeset(0): Creating default Display subsection in Screen section
	"Default Screen Section" for depth/fbbpp 24/32
[    47.577] (==) modeset(0): Depth 24, (==) framebuffer bpp 32
[    47.577] (==) modeset(0): RGB weight 888
[    47.577] (==) modeset(0): Default visual is TrueColor
[    47.577] (II) Loading sub module "glamoregl"
[    47.577] (II) LoadModule: "glamoregl"
[    47.577] (II) Loading /usr/lib64/xorg/modules/libglamoregl.so
[    47.741] (II) Module glamoregl: vendor="X.Org Foundation"
[    47.741] 	compiled for 1.20.6, module version = 1.0.1
[    47.741] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    49.197] (II) modeset(0): Refusing to try glamor on llvmpipe
[    49.214] (EE) modeset(0): glamor initialization failed
[    49.214] (II) modeset(0): ShadowFB: preferred YES, enabled YES
[    49.214] (II) modeset(0): Double-buffered shadow updates: on
[    49.248] (II) modeset(0): Output VGA-1 has no monitor section
[    49.282] (WW) EDID timing clock 148.50 exceeds claimed max 145MHz, fixing
[    49.282] (II) modeset(0): EDID for output VGA-1
[    49.282] (II) modeset(0): Manufacturer: WDT  Model: 191e  Serial#: 9999
[    49.282] (II) modeset(0): Year: 2245  Week: 1
[    49.282] (II) modeset(0): EDID Version: 1.3
[    49.282] (II) modeset(0): Analog Display Input,  Input Voltage Level: 0.700/0.300 V
[    49.282] (II) modeset(0): Sync:  Separate
[    49.282] (II) modeset(0): Max Image Size [cm]: horiz.: 41  vert.: 26
[    49.282] (II) modeset(0): Gamma: 2.20
[    49.282] (II) modeset(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
[    49.282] (II) modeset(0): First detailed timing is preferred mode
[    49.282] (II) modeset(0): redX: 0.636 redY: 0.349   greenX: 0.290 greenY: 0.584
[    49.282] (II) modeset(0): blueX: 0.143 blueY: 0.080   whiteX: 0.313 whiteY: 0.329
[    49.282] (II) modeset(0): Supported established timings:
[    49.282] (II) modeset(0): 640x480@60Hz
[    49.282] (II) modeset(0): 800x600@60Hz
[    49.282] (II) modeset(0): 1024x768@60Hz
[    49.282] (II) modeset(0): Manufacturer's mask: 0
[    49.282] (II) modeset(0): Supported standard timings:
[    49.282] (II) modeset(0): #0: hsize: 1920  vsize 1080  refresh: 60  vid: 49361
[    49.282] (II) modeset(0): Supported detailed timing:
[    49.282] (II) modeset(0): clock: 148.5 MHz   Image Size:  708 x 398 mm
[    49.282] (II) modeset(0): h_active: 1920  h_sync: 2008  h_sync_end 2052 h_blank_end 2200 h_border: 0
[    49.282] (II) modeset(0): v_active: 1080  v_sync: 1084  v_sync_end 1089 v_blanking: 1125 v_border: 0
[    49.282] (II) modeset(0): Serial No: 9999
[    49.282] (II) modeset(0): Ranges: V min: 60 V max: 75 Hz, H min: 30 H max: 80 kHz, PixClock max 149 MHz
[    49.282] (II) modeset(0): Monitor name: LD-2480
[    49.282] (II) modeset(0): EDID (in hex):
[    49.282] (II) modeset(0): 	00ffffffffffff005c941e190f270000
[    49.282] (II) modeset(0): 	01ff010308291a78ead6a5a2594a9524
[    49.282] (II) modeset(0): 	145054210800d1c00101010101010101
[    49.282] (II) modeset(0): 	010101010101023a801871382d40582c
[    49.282] (II) modeset(0): 	4500c48e2100001e000000ff00393939
[    49.282] (II) modeset(0): 	390a2020202020202020000000fd003c
[    49.282] (II) modeset(0): 	4b1e500e000a202020202020000000fc
[    49.282] (II) modeset(0): 	004c442d323438300a202020202000d3
[    49.282] (II) modeset(0): Printing probed modes for output VGA-1
[    49.282] (II) modeset(0): Modeline "1024x768"x60.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)
[    49.282] (II) modeset(0): Modeline "800x600"x60.3   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[    49.282] (II) modeset(0): Modeline "640x480"x59.9   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[    49.282] (II) modeset(0): Output VGA-1 connected
[    49.282] (II) modeset(0): Using exact sizes for initial modes
[    49.282] (II) modeset(0): Output VGA-1 using initial mode 1024x768 +0+0
[    49.282] (==) modeset(0): Using gamma correction (1.0, 1.0, 1.0)
[    49.282] (==) modeset(0): DPI set to (96, 96)
[    49.282] (II) Loading sub module "fb"
[    49.282] (II) LoadModule: "fb"
[    49.283] (II) Loading /usr/lib64/xorg/modules/libfb.so
[    49.290] (II) Module fb: vendor="X.Org Foundation"
[    49.290] 	compiled for 1.20.6, module version = 1.0.0
[    49.290] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    49.290] (II) Loading sub module "shadow"
[    49.290] (II) LoadModule: "shadow"
[    49.290] (II) Loading /usr/lib64/xorg/modules/libshadow.so
[    49.291] (II) Module shadow: vendor="X.Org Foundation"
[    49.291] 	compiled for 1.20.6, module version = 1.1.0
[    49.291] 	ABI class: X.Org ANSI C Emulation, version 0.4
[    49.291] (II) UnloadModule: "fbdev"
[    49.291] (II) Unloading fbdev
[    49.291] (II) UnloadSubModule: "fbdevhw"
[    49.291] (II) Unloading fbdevhw
[    49.291] (II) UnloadModule: "vesa"
[    49.291] (II) Unloading vesa
[    49.292] (==) modeset(0): Backing store enabled
[    49.292] (==) modeset(0): Silken mouse enabled
[    49.293] (II) modeset(0): Initializing kms color map for depth 24, 8 bpc.
[    49.293] (==) modeset(0): DPMS enabled
[    49.293] (II) Initializing extension Generic Event Extension
[    49.293] (II) Initializing extension SHAPE
[    49.293] (II) Initializing extension MIT-SHM
[    49.294] (II) Initializing extension XInputExtension
[    49.294] (II) Initializing extension XTEST
[    49.294] (II) Initializing extension BIG-REQUESTS
[    49.294] (II) Initializing extension SYNC
[    49.295] (II) Initializing extension XKEYBOARD
[    49.295] (II) Initializing extension XC-MISC
[    49.295] (II) Initializing extension XFIXES
[    49.295] (II) Initializing extension RENDER
[    49.295] (II) Initializing extension RANDR
[    49.295] (II) Initializing extension COMPOSITE
[    49.296] (II) Initializing extension DAMAGE
[    49.296] (II) Initializing extension MIT-SCREEN-SAVER
[    49.296] (II) Initializing extension DOUBLE-BUFFER
[    49.296] (II) Initializing extension RECORD
[    49.296] (II) Initializing extension DPMS
[    49.296] (II) Initializing extension Present
[    49.297] (II) Initializing extension DRI3
[    49.297] (II) Initializing extension X-Resource
[    49.297] (II) Initializing extension XVideo
[    49.297] (II) Initializing extension XVideo-MotionCompensation
[    49.297] (II) Initializing extension SELinux
[    49.297] (II) SELinux: Disabled by boolean
[    49.297] (II) Initializing extension GLX
[    49.297] (II) AIGLX: Screen 0 is not DRI2 capable
[    49.303] (II) IGLX: Loaded and initialized swrast
[    49.303] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[    49.303] (II) Initializing extension XFree86-VidModeExtension
[    49.303] (II) Initializing extension XFree86-DGA
[    49.303] (II) Initializing extension XFree86-DRI
[    49.303] (II) Initializing extension DRI2
[    49.303] (II) modeset(0): Damage tracking initialized
[    49.303] (II) modeset(0): Setting screen physical size to 270 x 203
[    49.650] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[    49.650] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[    49.650] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[    49.650] (**) Power Button: Applying InputClass "system-keyboard"
[    49.650] (II) LoadModule: "libinput"
[    49.650] (II) Loading /usr/lib64/xorg/modules/input/libinput_drv.so
[    49.702] (II) Module libinput: vendor="X.Org Foundation"
[    49.702] 	compiled for 1.20.3, module version = 0.29.0
[    49.702] 	Module class: X.Org XInput Driver
[    49.702] 	ABI class: X.Org XInput driver, version 24.1
[    49.702] (II) Using input driver 'libinput' for 'Power Button'
[    49.703] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 22 paused 0
[    49.703] (**) Power Button: always reports core events
[    49.703] (**) Option "Device" "/dev/input/event0"
[    49.703] (**) Option "_source" "server/udev"
[    49.732] (II) event0  - Power Button: is tagged by udev as: Keyboard
[    49.732] (II) event0  - Power Button: device is a keyboard
[    49.732] (II) event0  - Power Button: device removed
[    49.732] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input0/event0"
[    49.732] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[    49.732] (**) Option "xkb_layout" "us"
[    49.734] (II) event0  - Power Button: is tagged by udev as: Keyboard
[    49.734] (II) event0  - Power Button: device is a keyboard
[    49.735] (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/event1)
[    49.735] (**) Logitech USB Optical Mouse: Applying InputClass "evdev pointer catchall"
[    49.735] (**) Logitech USB Optical Mouse: Applying InputClass "libinput pointer catchall"
[    49.735] (II) Using input driver 'libinput' for 'Logitech USB Optical Mouse'
[    49.788] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 25 paused 0
[    49.788] (**) Logitech USB Optical Mouse: always reports core events
[    49.788] (**) Option "Device" "/dev/input/event1"
[    49.788] (**) Option "_source" "server/udev"
[    49.790] (II) event1  - Logitech USB Optical Mouse: is tagged by udev as: Mouse
[    49.791] (II) event1  - Logitech USB Optical Mouse: device is a pointer
[    49.791] (II) event1  - Logitech USB Optical Mouse: device removed
[    49.791] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/0003:046D:C018.0001/input/input1/event1"
[    49.791] (II) XINPUT: Adding extended input device "Logitech USB Optical Mouse" (type: MOUSE, id 7)
[    49.791] (**) Option "AccelerationScheme" "none"
[    49.791] (**) Logitech USB Optical Mouse: (accel) selected scheme none/0
[    49.791] (**) Logitech USB Optical Mouse: (accel) acceleration factor: 2.000
[    49.791] (**) Logitech USB Optical Mouse: (accel) acceleration threshold: 4
[    49.793] (II) event1  - Logitech USB Optical Mouse: is tagged by udev as: Mouse
[    49.793] (II) event1  - Logitech USB Optical Mouse: device is a pointer
[    49.795] (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/mouse0)
[    49.795] (II) No input driver specified, ignoring this device.
[    49.795] (II) This device may have been added with another device file.
[    49.796] (II) config/udev: Adding input device Logitech Logitech USB Keyboard (/dev/input/event2)
[    49.796] (**) Logitech Logitech USB Keyboard: Applying InputClass "evdev keyboard catchall"
[    49.796] (**) Logitech Logitech USB Keyboard: Applying InputClass "libinput keyboard catchall"
[    49.796] (**) Logitech Logitech USB Keyboard: Applying InputClass "system-keyboard"
[    49.796] (II) Using input driver 'libinput' for 'Logitech Logitech USB Keyboard'
[    49.797] (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 26 paused 0
[    49.797] (**) Logitech Logitech USB Keyboard: always reports core events
[    49.797] (**) Option "Device" "/dev/input/event2"
[    49.797] (**) Option "_source" "server/udev"
[    49.800] (II) event2  - Logitech Logitech USB Keyboard: is tagged by udev as: Keyboard
[    49.800] (II) event2  - Logitech Logitech USB Keyboard: device is a keyboard
[    49.800] (II) event2  - Logitech Logitech USB Keyboard: device removed
[    49.800] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.0/0003:046D:C316.0002/input/input2/event2"
[    49.800] (II) XINPUT: Adding extended input device "Logitech Logitech USB Keyboard" (type: KEYBOARD, id 8)
[    49.800] (**) Option "xkb_layout" "us"
[    49.801] (II) event2  - Logitech Logitech USB Keyboard: is tagged by udev as: Keyboard
[    49.801] (II) event2  - Logitech Logitech USB Keyboard: device is a keyboard
[    49.802] (II) config/udev: Adding input device Logitech Logitech USB Keyboard Consumer Control (/dev/input/event3)
[    49.802] (**) Logitech Logitech USB Keyboard Consumer Control: Applying InputClass "evdev keyboard catchall"
[    49.802] (**) Logitech Logitech USB Keyboard Consumer Control: Applying InputClass "libinput keyboard catchall"
[    49.802] (**) Logitech Logitech USB Keyboard Consumer Control: Applying InputClass "system-keyboard"
[    49.802] (II) Using input driver 'libinput' for 'Logitech Logitech USB Keyboard Consumer Control'
[    49.803] (II) systemd-logind: got fd for /dev/input/event3 13:67 fd 27 paused 0
[    49.803] (**) Logitech Logitech USB Keyboard Consumer Control: always reports core events
[    49.803] (**) Option "Device" "/dev/input/event3"
[    49.803] (**) Option "_source" "server/udev"
[    49.805] (II) event3  - Logitech Logitech USB Keyboard Consumer Control: is tagged by udev as: Keyboard Joystick
[    49.805] (II) event3  - Logitech Logitech USB Keyboard Consumer Control: device is a keyboard
[    49.805] (II) event3  - Logitech Logitech USB Keyboard Consumer Control: device removed
[    49.805] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.1/0003:046D:C316.0003/input/input3/event3"
[    49.805] (II) XINPUT: Adding extended input device "Logitech Logitech USB Keyboard Consumer Control" (type: KEYBOARD, id 9)
[    49.805] (**) Option "xkb_layout" "us"
[    49.806] (II) event3  - Logitech Logitech USB Keyboard Consumer Control: is tagged by udev as: Keyboard Joystick
[    49.806] (II) event3  - Logitech Logitech USB Keyboard Consumer Control: device is a keyboard
[    49.807] (II) config/udev: Adding input device Logitech Logitech USB Keyboard System Control (/dev/input/event4)
[    49.807] (**) Logitech Logitech USB Keyboard System Control: Applying InputClass "evdev keyboard catchall"
[    49.807] (**) Logitech Logitech USB Keyboard System Control: Applying InputClass "libinput keyboard catchall"
[    49.807] (**) Logitech Logitech USB Keyboard System Control: Applying InputClass "system-keyboard"
[    49.807] (II) Using input driver 'libinput' for 'Logitech Logitech USB Keyboard System Control'
[    49.808] (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 28 paused 0
[    49.808] (**) Logitech Logitech USB Keyboard System Control: always reports core events
[    49.808] (**) Option "Device" "/dev/input/event4"
[    49.808] (**) Option "_source" "server/udev"
[    49.810] (II) event4  - Logitech Logitech USB Keyboard System Control: is tagged by udev as: Keyboard
[    49.810] (II) event4  - Logitech Logitech USB Keyboard System Control: device is a keyboard
[    49.810] (II) event4  - Logitech Logitech USB Keyboard System Control: device removed
[    49.810] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.1/0003:046D:C316.0003/input/input4/event4"
[    49.810] (II) XINPUT: Adding extended input device "Logitech Logitech USB Keyboard System Control" (type: KEYBOARD, id 10)
[    49.810] (**) Option "xkb_layout" "us"
[    49.811] (II) event4  - Logitech Logitech USB Keyboard System Control: is tagged by udev as: Keyboard
[    49.811] (II) event4  - Logitech Logitech USB Keyboard System Control: device is a keyboard
[    49.812] (II) config/udev: Adding input device PC Speaker (/dev/input/event5)
[    49.812] (II) No input driver specified, ignoring this device.
[    49.812] (II) This device may have been added with another device file.
[    52.449] (II) modeset(0): Disabling kernel dirty updates, not required.
[    52.587] (WW) EDID timing clock 148.50 exceeds claimed max 145MHz, fixing
[    52.587] (II) modeset(0): EDID vendor "WDT", prod id 6430
[    52.587] (II) modeset(0): Using EDID range info for horizontal sync
[    52.587] (II) modeset(0): Using EDID range info for vertical refresh
[    52.587] (II) modeset(0): Printing DDC gathered Modelines:
[    52.587] (II) modeset(0): Modeline "1920x1080"x0.0  148.50  1920 2008 2052 2200  1080 1084 1089 1125 +hsync +vsync (67.5 kHz eP)
[    52.587] (II) modeset(0): Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync (37.9 kHz e)
[    52.587] (II) modeset(0): Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync (31.5 kHz e)
[    52.587] (II) modeset(0): Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync -vsync (48.4 kHz e)

ToZ: added code tags

Last edited by ToZ (2020-07-17 17:08:23)

ToZ · 2020-07-17 17:16:26

I added code tags to you post, makes it easier to read.

What's odd is that log file shows that you are using the modesetting driver, not mgag200. Is it the correct log file?

One of my suggestions would have been to specify a modesetting driver with glamor disabled. To do so, drop this file into /etc/X11/xorg.conf.d/20-modesetting.conf :

Section "Device"
  Identifier "Matrox"
  Driver "modesetting"
  Option "AccelMethod" "none"
EndSection

The other suggestion would be to get the mgag200 driver working - but there is a discrepancy between what lspci is showing and what is being shown in the log file.

mathog · 2020-07-18 03:44:39

ToZ wrote:

I added code tags to you post, makes it easier to read.
What's odd is that log file shows that you are using the modesetting driver, not mgag200. Is it the correct log file?
One of my suggestions would have been to specify a modesetting driver with glamor disabled. To do so, drop this file into /etc/X11/xorg.conf.d/20-modesetting.conf :
Section "Device"
  Identifier "Matrox"
  Driver "modesetting"
  Option "AccelMethod" "none"
EndSection
The other suggestion would be to get the mgag200 driver working - but there is a discrepancy between what lspci is showing and what is being shown in the log file.

It is the correct log file. lsmod shows mgag200 loaded, but that does not mean that X11 is using it.

lsmod | grep -i mga
mgag200                36864  2
drm_vram_helper        20480  1 mgag200
i2c_algo_bit           16384  1 mgag200
drm_kms_helper        212992  1 mgag200
drm                   536576  6 drm_kms_helper,drm_vram_helper,mgag200,ttm

There is also:

dmesg | grep -i mga
[    3.044039] mgag200 0000:03:03.0: vgaarb: deactivate vga console
[    3.178030] fbcon: mgag200drmfb (fb0) is primary device
[    4.010147] mgag200 0000:03:03.0: fb0: mgag200drmfb frame buffer device
[    4.061038] [drm] Initialized mgag200 1.0.0 20110418 for 0000:03:03.0 on minor 0
[   53.105316] mgag200 0000:03:03.0: Video card doesn't support cursors with partial transparency.
[   53.105320] mgag200 0000:03:03.0: Not enabling hardware cursor.

This is a Dell Poweredge T110 II, by the way. Not normally used for graphics, it is normally a compute node, but I'm working at home with it, so it would be nice if it wouldn't glitch.

ToZ · 2020-07-18 14:15:18

mathog wrote:

[ 53.105316] mgag200 0000:03:03.0: Video card doesn't support cursors with partial transparency.
[ 53.105320] mgag200 0000:03:03.0: Not enabling hardware cursor.

I think this might be the root of the problem.

This post suggests using the "mgag200.modeset=0" kernel parameter.

mathog · 2020-07-20 17:55:33

Stranger and stranger.

Today's boot has no stuck cursor, at least so far, and it has been up for a full hour. Yet Xorg.0.log is identical (once the "[ numbers ]" is stripped from the front of each line) and the mgag lines in /var/log/messages are also the same. No RPMs have been added or removed in the interim, so the software should all be the same. Same applications running as before.

There is apparently no "xorg-x11-drv-mga" package. Looks like Red Hat desupported that after EL 6 and so it is absent from CentOS 7 and 8 too. They left the mga module in the kernel though. That at least explains why it isn't using the X11 mga driver.

mathog · 2020-07-20 22:52:51

And its back. Not sure when it happened, but there is a wristwatch icon on the screen 5 hours after the X11 server started. So it went from not doing this to doing this without the X11 server having to shutdown and restart.

mathog · 2020-07-21 23:36:00

ToZ wrote:

One of my suggestions would have been to specify a modesetting driver with glamor disabled. To do so, drop this file into /etc/X11/xorg.conf.d/20-modesetting.conf :
Section "Device"
  Identifier "Matrox"
  Driver "modesetting"
  Option "AccelMethod" "none"
EndSection

Did that today. The Xorg.0.log now contains:

[  4694.960] (**) modeset(0): glamor disabled

But it still comes up with the hand icon in the middle of the screen.

ToZ wrote:

The other suggestion would be to get the mgag200 driver working - but there is a discrepancy between what lspci is showing and what is being shown in the log file.

Not so easy to do since RedHat/CentOS dropped support a while back. I finally managed to build and install this, see the first (currently only) post here:

https://forums.centos.org/viewtopic.php?f=54&t=75123

I even managed to get it to try to load by placing this:

cat  /etc/X11/xorg.conf.d
Section "Device"
	Identifier  "Card0"
	 Driver      "mga"
	BusID       "PCI:3:3:0"
EndSection

and restarting. But it wouldn't, it complained about

undefined symbol: fbdevHWSave

and bailed out. "ldd -r" on the vesa video driver also shows a ton of undefined symbols, although not that particular one.

The xorg-x11-server version is 1.20.6-3, which for all I know is wildly incompatible with the mageia mga driver.

ToZ · 2020-07-22 00:32:49

Are you able to test another DE? KDE/Plasma or Gnome? See if the problem replicates in those DEs?

Or try compton instead of xfwm4 to rule out the compositor.

mathog · 2020-07-22 17:17:18

ToZ wrote:

Are you able to test another DE? KDE/Plasma or Gnome? See if the problem replicates in those DEs?

I don't want to mess about that much with X11 for an annoying but otherwise minor glitch.

ToZ wrote:

Or try compton instead of xfwm4 to rule out the compositor.

The compositor is turned off in "Window Manager Tweaks". (I am not a fan of fancy desktops: I don't like transparency, windows that jump up and down or wiggle, and so forth.) So I think the compositor cannot be the problem.

In the CentOS forums they told me that the mga driver is deprecated and that it is supposed to use the mga200 kernel module with the modesetting X11 driver. Which it is. It may well be that the glitch is in something which runs on top of that.

Thanks.

Last edited by mathog (2020-07-22 17:17:55)

mathog · 2020-07-22 18:48:02

Things that do not remove a stuck icon:

1. killing the screensaver
2. xfwm4 --replace
3. killing xfce4-panel

ToZ · 2020-07-22 23:41:07

mathog wrote:

In the CentOS forums they told me that the mga driver is deprecated and that it is supposed to use the mga200 kernel module with the modesetting X11 driver. Which it is. It may well be that the glitch is in something which runs on top of that.

Perhaps a bug report against the mgag200 kernel module would be the best way forward. This appears to be the place to create the bug reports.

mathog · 2020-07-23 22:11:14

With some help from CentOS forums member "chemal" I finally managed to get the mga driver work. It has been running now for over 5 hours and there are no stuck icons on the screen. Details of how to do that here:

https://forums.centos.org/viewtopic.php … 09#p316204

If this continues to work then the stuck icons pretty much have to be a problem with either mgag200 or the modesetting video driver, more likely the former than the latter, given how uncommon the first is and how common the second.

ToZ · 2020-07-23 22:40:27

Nice. Thanks for posting back with the solution.

mathog · 2020-07-24 17:58:58

ToZ wrote:

Perhaps a bug report against the mgag200 kernel module would be the best way forward. This appears to be the place to create the bug reports.

Posted there:

https://gitlab.freedesktop.org/drm/misc/-/issues/21

alcornoqui · 2020-07-24 18:58:27

Great thread, thanks!

Xfce Forum

Sub domains

#1 2020-07-16 16:40:06

After CentOS 8 update, recurring stuck icons on desktop

#2 2020-07-16 20:01:09

Re: After CentOS 8 update, recurring stuck icons on desktop

#3 2020-07-16 20:56:48

Re: After CentOS 8 update, recurring stuck icons on desktop

#4 2020-07-16 21:25:08

Re: After CentOS 8 update, recurring stuck icons on desktop

#5 2020-07-16 23:41:24

Re: After CentOS 8 update, recurring stuck icons on desktop

#6 2020-07-17 00:03:50

Re: After CentOS 8 update, recurring stuck icons on desktop

#7 2020-07-17 16:59:38

Re: After CentOS 8 update, recurring stuck icons on desktop

#8 2020-07-17 17:16:26

Re: After CentOS 8 update, recurring stuck icons on desktop

#9 2020-07-18 03:44:39

Re: After CentOS 8 update, recurring stuck icons on desktop

#10 2020-07-18 14:15:18

Re: After CentOS 8 update, recurring stuck icons on desktop

#11 2020-07-20 17:55:33

Re: After CentOS 8 update, recurring stuck icons on desktop

#12 2020-07-20 22:52:51

Re: After CentOS 8 update, recurring stuck icons on desktop

#13 2020-07-21 23:36:00

Re: After CentOS 8 update, recurring stuck icons on desktop

#14 2020-07-22 00:32:49

Re: After CentOS 8 update, recurring stuck icons on desktop

#15 2020-07-22 17:17:18

Re: After CentOS 8 update, recurring stuck icons on desktop

#16 2020-07-22 18:48:02

Re: After CentOS 8 update, recurring stuck icons on desktop

#17 2020-07-22 23:41:07

Re: After CentOS 8 update, recurring stuck icons on desktop

#18 2020-07-23 22:11:14

Re: After CentOS 8 update, recurring stuck icons on desktop

#19 2020-07-23 22:40:27

Re: After CentOS 8 update, recurring stuck icons on desktop

#20 2020-07-24 17:58:58

Re: After CentOS 8 update, recurring stuck icons on desktop

#21 2020-07-24 18:58:27

Re: After CentOS 8 update, recurring stuck icons on desktop

Board footer