[frollic]

Hi,

just today I upgraded one of my Fedora boxes to FC25 x86_64, and Kodi 17 beta 17 (out of RPMFusion).
RPMFusion calls this kodi-17.0-0.10 - 2016-12-19, beta 7.

When the system boots (using gdm as manager) the mouse pointer is seen, and will not disappear,
unless I first move the mouse. Once the pointer is moved, it goes away, as it should.

versions:

gdm-3.22.1-1.fc25.x86_64
xorg-x11-server-common-1.19.0-2.fc25.x86_64
xorg-x11-drv-synaptics-1.9.0-1.fc25.x86_64
xorg-x11-server-utils-7.7-20.fc25.x86_64
xorg-x11-font-utils-7.5-32.fc25.x86_64
xorg-x11-drv-wacom-0.34.0-1.fc25.x86_64
xorg-x11-server-Xwayland-1.19.0-2.fc25.x86_64
xorg-x11-xbitmaps-1.1.1-9.fc24.noarch
xorg-x11-server-Xvfb-1.19.0-2.fc25.x86_64
xorg-x11-drv-qxl-0.1.4-10.20160929gite13d28ee.fc25.x86_64
xorg-x11-xinit-1.3.4-13.fc25.x86_64
xorg-x11-utils-7.5-21.fc24.x86_64
xorg-x11-apps-7.7-15.fc24.x86_64
xorg-x11-drv-openchrome-0.5.0-2.fc25.x86_64
xorg-x11-drv-vmware-13.0.2-12.20150211git8f0cf7c.fc25.x86_64
xorg-x11-xkb-utils-7.7-17.fc24.x86_64
xorg-x11-drv-fbdev-0.4.3-25.fc25.x86_64
xorg-x11-drv-ati-7.7.1-1.20160928git3fc839ff.fc25.x86_64
xorg-x11-drv-nouveau-1.0.13-1.fc25.x86_64
xorg-x11-xauth-1.0.9-5.fc24.x86_64
xorg-x11-fonts-misc-7.5-16.fc24.noarch
xorg-x11-drv-intel-2.99.917-26.20160929.fc25.x86_64
xorg-x11-drv-vesa-2.3.2-25.fc25.x86_64
xorg-x11-server-Xorg-1.19.0-2.fc25.x86_64
xorg-x11-drv-evdev-2.10.4-1.fc25.x86_64

kernel is 4.8.15-300.fc25.x86_64

easiest solution would probably be to run xorg with -nocursor, but passing params on to xorg,
isn't, AFAIK, supported by gdm

[fritsch]

You can disable mouse support within kodi if that helps.

[frollic]

You can disable mouse support within kodi if that helps.

do you mean system -> settings -> input ?

it doesn't do anything for me, same behaviour, no matter what I set it to.

[FernetMenta]

what window manager do you use?

[frollic]

what window manager do you use?

errrr .... gdm ?

[FernetMenta]

gdm is a display/login manager, I asked for window manager

[frollic]

gdm is a display/login manager, I asked for window manager

oh, in that case, gnome ....

gnome-backgrounds-3.22.1-1.fc25.noarch
gnome-bluetooth-3.20.0-2.fc25.x86_64
gnome-bluetooth-libs-3.20.0-2.fc25.x86_64
gnome-calculator-3.22.2-1.fc25.x86_64
gnome-color-manager-3.22.2-1.fc25.x86_64
gnome-desktop3-3.22.2-1.fc25.x86_64
gnome-dictionary-3.20.0-1.fc25.x86_64
gnome-dictionary-libs-3.20.0-1.fc25.x86_64
gnome-epub-thumbnailer-1.5-3.fc24.x86_64
gnome-font-viewer-3.22.0-1.fc25.x86_64
gnome-icon-theme-3.12.0-4.fc24.noarch
gnome-icon-theme-extras-3.12.0-4.fc24.noarch
gnome-icon-theme-legacy-3.12.0-4.fc24.noarch
gnome-icon-theme-symbolic-3.12.0-4.fc24.noarch
gnome-initial-setup-3.22.1-1.fc25.x86_64
gnome-js-common-0.1.2-13.fc24.noarch
gnome-keyring-3.20.0-1.fc25.x86_64
gnome-keyring-pam-3.20.0-1.fc25.x86_64
gnome-menus-3.13.3-5.fc24.x86_64
gnome-online-accounts-3.22.3-1.fc25.x86_64
gnome-packagekit-3.22.1-1.fc25.x86_64
gnome-packagekit-common-3.22.1-1.fc25.x86_64
gnome-packagekit-installer-3.22.1-1.fc25.x86_64
gnome-packagekit-updater-3.22.1-1.fc25.x86_64
gnome-screenshot-3.22.0-1.fc25.x86_64
gnome-session-3.22.2-1.fc25.x86_64
gnome-session-wayland-session-3.22.2-1.fc25.x86_64
gnome-session-xsession-3.22.2-1.fc25.x86_64
gnome-settings-daemon-3.22.1-1.fc25.x86_64
gnome-shell-3.22.2-2.fc25.x86_64
gnome-system-log-3.9.90-6.fc24.x86_64
gnome-system-monitor-3.22.2-1.fc25.x86_64
gnome-terminal-3.22.1-2.fc25.x86_64
gnome-themes-2.32.0-14.fc24.noarch
gnome-themes-standard-3.22.2-1.fc25.x86_64
gnome-video-effects-0.4.1-4.fc24.noarch

[FernetMenta]

Compositing window managers have never been working well for running Kodi on X11. This mouse pointer issue might be one the minor problems you may encounter with this config. For the time being use a non-compositing WM for Kodi. Things will change with Wayland and Mir.

[frollic]

Compositing window managers have never been working well for running Kodi on X11. This mouse pointer issue might be one the minor problems you may encounter with this config. For the time being use a non-compositing WM for Kodi. Things will change with Wayland and Mir.

Thing is, it's not a new install, I simply did the FC24 -> FC25 upgrade, when the issue popped up.

The software components are the same from a long time ago, just upgraded over time when Fedora
released a new version of the package(s), or the OS.

I have the same setup (software wise, CPUs differ N2807 vs J1900), running on another two HTPCs -
obviously without this issue, since they're still on FC24.

[FernetMenta]

That is nothing unusual, things tend to break if underlying layers get upgraded. In general fixes are simple and made quickly. The problem in this case is that no developer really cares about compositing WMs for running Kodi and as a result this may take forever to get fixed.

[frollic]

That is nothing unusual, things tend to break if underlying layers get upgraded. In general fixes are simple and made quickly. The problem in this case is that no developer really cares about compositing WMs for running Kodi and as a result this may take forever to get fixed.

Good point.

So, what would a recommended WM be ?

Google told me Xfce and LXDE, is there something else, and which one should I pick ?

[FernetMenta]

On my box in my living room I use Fluxbox. Openbox is also an option. On a dev system I have Xfce that most of the time is ok. Only with Ubuntu 16.04 it should isseus with power manager. Cured with 16.10.

[frollic]

Finally managed to solve the problem.

Apparently Fedora defaults Wayland instead of X11 starting FC25, which caused the problem.

This can be reverted by settting WaylandEnable=false under the [daemon] section in
/etc/gdm/custom.conf.

source: https://fedoraproject.org/wiki/Changes/WaylandByDefault

[Derek]

easiest fix is to boot str8 into kodi and this problem will be gone