Invisible pointer

Having trouble with the game? Report issues and get help here. Read this first!

Moderator: Forum Moderators

Forum rules
Before reporting issues in this section, you must read the following topic:
Post Reply
is_this_allowed
Posts: 4
Joined: August 16th, 2022, 4:08 pm

Invisible pointer

Post by is_this_allowed »

Hi,
I just installed Fedora 36 x64 on my desktop computer and then I proceeded to update the system, install a password manager and finally Wesnoth 1.16.5 through flatpak using flathub as remote. To reproduce the bug you just need to start Wesnoth: you'll notice that the mouse pointer is not visible while the interface works. If you move the mouse randomly and hover over a button it will get highlighted. Going through the menu options doesn't seem to solve the issue so it's not something related only to the main menu. Since I can't see the pointer I'll upload a screenshot with relevant information about the Wesnoth build. The language of the UI is Italian.
edit replaced 'cursor' with 'pointer'.
update: I uninstalled Wesnoth 1.16.5 and installed Wesnoth 1.16.1 from Fedora flatapak remote. This one works well and the pointer is visible. I do know Fedora official flatpak apps are packaged in a slightly different way than what Flatpak recommends but I don't think this is the culprit. Here are the build info:

Code: Select all

The Battle for Wesnoth version 1.16.1 x86_64
Running on Fedora Linux 35 (Thirty Five) x86_64
Distribution channel: Default

Game paths
==========

Data dir:        /app/share/wesnoth
User config dir: /home/USER/.var/app/org.wesnoth.Wesnoth/config/wesnoth
User data dir:   /home/USER/.var/app/org.wesnoth.Wesnoth/data/wesnoth/1.16
Saves dir:       /home/USER/.var/app/org.wesnoth.Wesnoth/data/wesnoth/1.16/saves
Add-ons dir:     /home/USER/.var/app/org.wesnoth.Wesnoth/data/wesnoth/1.16/data/add-ons
Cache dir:       /home/USER/.var/app/org.wesnoth.Wesnoth/cache/wesnoth

Libraries
=========

Boost:             1.76
Lua:               5.4.2
OpenSSL/libcrypto: 1.1.1l (runtime 1.1.1o)
Cairo:             1.17.4 (runtime 1.17.4)
Pango:             1.49.2 (runtime 1.50.4)
SDL:               2.0.16 (runtime 2.0.22)
SDL_image:         2.0.5 (runtime 2.0.5)
SDL_mixer:         2.0.4 (runtime 2.0.4)

Features
========

Lua console completion:       yes
D-Bus notifications back end: yes

Current video settings
======================

SDL video drivers:       [wayland] x11 KMSDRM dummy
Window size:             1280x1024
Screen refresh rate:     60
Screen dots per inch:    95.623528x96.331848
Screen dpi scale factor: 0.996078x1.003457

Current audio settings
======================

Audio not initialized.

Installed add-ons
=================

No add-ons installed.
Attachments
Screenshot from 2022-08-16 18-22-17.png
User avatar
Pentarctagon
Project Manager
Posts: 5530
Joined: March 22nd, 2009, 10:50 pm
Location: Earth (occasionally)

Re: Invisible pointer

Post by Pentarctagon »

It sounds like this issue, except the opposite - if anything I would've expected the Fedora flatpak to have the invisible cursor issue and the Flathub version to work as expected.
99 little bugs in the code, 99 little bugs
take one down, patch it around
-2,147,483,648 little bugs in the code
is_this_allowed
Posts: 4
Joined: August 16th, 2022, 4:08 pm

Re: Invisible pointer

Post by is_this_allowed »

Quite strange, did the other user install Wesnoth from the Flathub remote? I just checked and I'm correct, the Wesnoth version I'm running is from the Fedora remote. Same configuration as the other user except for the the desktop environment - I run GNOME 42 - and the application version which in their case is the 1.17 development version. My PC has an ancient AMD A4-5300 APU. The debug info above aren't correct, I'm running Fedora 36 not 35 (but probably the flatpak got downloaded from older remote).
User avatar
Pentarctagon
Project Manager
Posts: 5530
Joined: March 22nd, 2009, 10:50 pm
Location: Earth (occasionally)

Re: Invisible pointer

Post by Pentarctagon »

I believe the person in the bug report built wesnoth from source. The root issue though is that this is happening due to Wayland being used instead of X11 - and Fedora does default SDL2 applications to using Wayland - it's just strange to see that happening for a flatpak app since it wouldn't be using the system SDL2 libraries.
99 little bugs in the code, 99 little bugs
take one down, patch it around
-2,147,483,648 little bugs in the code
Post Reply