After an update in Fedora 41, my cursor has disappeared. The mouse still works, though. I have an idea of where I am on the page, and clicking on an area will produce the result you would expect. But it is a total pain not to be able to see the cursor. This happened 10 days to two weeks ago, and I did my usual response to wait for an update to fix the problem. I also researched how other people have resolved similar problems. I am finally desperate enough to sign up for this forum and ask how to fix this.
Welcome to Fedora @eutrochium
First thing you can do is to create a new user to see if you have the same issue there.
If the second user works, have a look on the settings of the theming inclusive Cursors … so you might can you revert the issue.
If it not works we do need more details about your hardware, additional software inkl. theming etc.
I created a second user. Still no cursor with the new user.
I was able to change the themes, but the cursor remained missing. I’m not sure what software to tell you about. I use KDE. I have thought about trying another desktop environment to see if the cursor appears in it.
My machine is new. There are still some minor glitches with video rendering. Sometimes little areas will be solid blocks of a single color (white or black). Here are the details about my hardware:
$ inxi -fxxxza
CPU:
Info: model: Intel Core Ultra 9 185H bits: 64 type: MST AMCP
arch: Meteor Lake level: v3 note: check built: 2023+ process: Intel 4 (7nm)
family: 6 model-id: 0xAA (170) stepping: 4 microcode: 0x20
Topology: cpus: 1x dies: 1 clusters: 9 cores: 16 threads: 22 mt: 6 tpc: 2
st: 10 smt: enabled cache: 24 MiB note: check
Speed (MHz): avg: 1045 min/max: 400/4800:5100:3800:2500 scaling:
driver: intel_pstate governor: powersave cores: 1: 1045 2: 1045 3: 1045
4: 1045 5: 1045 6: 1045 7: 1045 8: 1045 9: 1045 10: 1045 11: 1045 12: 1045
13: 1045 14: 1045 15: 1045 16: 1045 17: 1045 18: 1045 19: 1045 20: 1045
21: 1045 22: 1045 bogomips: 135168
Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
arch_capabilities arch_lbr arch_perfmon art avx avx2 avx_vnni bmi1 bmi2
bts bus_lock_detect clflush clflushopt clwb cmov constant_tsc cpuid
cpuid_fault cx16 cx8 de ds_cpl dtes64 dtherm dts epb ept ept_ad erms est
f16c flexpriority flush_l1d fma fpu fsgsbase fsrm fxsr gfni hfi ht hwp
hwp_act_window hwp_epp hwp_notify hwp_pkg_req ibpb ibrs ibrs_enhanced ibt
ida intel_pt invpcid lahf_lm lm mca mce md_clear mmx monitor movbe
movdir64b movdiri msr mtrr nonstop_tsc nopl nx ospke pae pat pbe pcid
pclmulqdq pconfig pdcm pdpe1gb pebs pge pku pln pni popcnt pse pse36 pts
rdpid rdrand rdseed rdtscp rep_good sdbg sep serialize sha_ni smap smep
smx split_lock_detect ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall
tm tm2 tpr_shadow tsc tsc_adjust tsc_deadline_timer tsc_known_freq umip
user_shstk vaes vme vmx vnmi vpclmulqdq vpid waitpkg x2apic xgetbv1 xsave
xsavec xsaveopt xsaves xtopology xtpr
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: reg_file_data_sampling status: Not affected
Type: retbleed status: Not affected
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Enhanced / Automatic IBRS; IBPB:
conditional; RSB filling; PBRSB-eIBRS: Not affected; BHI: BHI_DIS_S
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
I miss the GPU and their drivers. Your inxi is too technical and as I see mostly about the processor. inxi -Fzxx normally gives the info we can deal with. It also shows what drivers are active etc.
2 Likes
Is the machine a tablet? Do you use a virtual keyboard?
journalctl --no-hostname -b -g cursor|cat may have some useful details.
There may be workarounds using accessibility options.
1 Like
Here is the result of inxi -Fzxx
System:
Kernel: 6.11.8-300.fc41.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 2.43.1-2.fc41
Desktop: KDE Plasma v: 6.2.4 tk: Qt v: N/A wm: kwin_wayland dm: SDDM
Distro: Fedora Linux 41 (KDE Plasma)
Machine:
Type: Mini-pc System: ASUSTeK product: NUC14RVS-B v: 90AR0051-M000F0
serial: <superuser required> Chassis: type: 35 v: 2.0
serial: <superuser required>
Mobo: ASUSTeK model: NUC14RVS v: 60AS0080-MBCA02
serial: <superuser required> part-nu: NUC14RVS-B UEFI: ASUSTeK
v: RVMTL357.0038.2024.0115.1528 date: 01/15/2024
CPU:
Info: 16-core (6-mt/10-st) model: Intel Core Ultra 9 185H bits: 64
type: MST AMCP arch: Meteor Lake rev: 4 cache: 24 MiB note: check
Speed (MHz): avg: 1666 min/max: 400/4800:5100:3800:2500 cores: 1: 1666
2: 1666 3: 1666 4: 1666 5: 1666 6: 1666 7: 1666 8: 1666 9: 1666 10: 1666
11: 1666 12: 1666 13: 1666 14: 1666 15: 1666 16: 1666 17: 1666 18: 1666
19: 1666 20: 1666 21: 1666 22: 1666 bogomips: 135168
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: Intel Meteor Lake-P [Intel Arc Graphics] vendor: ASUSTeK
driver: i915 v: kernel arch: Gen-13 ports: active: HDMI-A-1 empty: DP-1,
DP-2, DP-3, DP-4, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:7d55
Display: wayland server: Xwayland v: 24.1.4 compositor: kwin_wayland
driver: N/A display-ID: 0
Monitor-1: HDMI-A-1 res: 2752x1152 size: N/A
API: EGL v: 1.5 platforms: device: 0 drv: iris device: 1 drv: swrast gbm:
drv: iris surfaceless: drv: iris wayland: drv: iris x11: drv: iris
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.2.7 glx-v: 1.4
direct-render: yes renderer: Mesa Intel Arc Graphics (MTL)
device-ID: 8086:7d55 display-ID: :0.0
API: Vulkan v: 1.3.296 surfaces: xcb,xlib,wayland device: 0
type: integrated-gpu driver: N/A device-ID: 8086:7d55 device: 1 type: cpu
driver: N/A device-ID: 10005:0000
Audio:
Device-1: Intel Meteor Lake-P HD Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel bus-ID: 00:1f.3 chip-ID: 8086:7e28
Device-2: C-Media USB PnP Sound Device
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 1.1 speed: 12 Mb/s
lanes: 1 bus-ID: 3-5.2:6 chip-ID: 0d8c:013a
API: ALSA v: k6.11.8-300.fc41.x86_64 status: kernel-api
Server-1: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin
Network:
Device-1: Intel Meteor Lake PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:7e40
IF: wlo1 state: down mac: <filter>
Device-2: Intel Ethernet I226-V vendor: ASUSTeK driver: igc v: kernel
pcie: speed: 5 GT/s lanes: 1 port: N/A bus-ID: 57:00.0 chip-ID: 8086:125c
IF: enp87s0 state: up speed: 100 Mbps duplex: full mac: <filter>
IF-ID-1: tun0 state: unknown speed: 10000 Mbps duplex: full mac: N/A
Bluetooth:
Device-1: Intel AX211 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 bus-ID: 3-10:7 chip-ID: 8087:0033
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.3
lmp-v: 12
Drives:
Local Storage: total: 4.15 TiB used: 1.52 TiB (36.7%)
ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 990 PRO 2TB size: 1.82 TiB
speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 32.9 C
ID-2: /dev/nvme1n1 model: PCIe SSD size: 1.86 TiB speed: 31.6 Gb/s
lanes: 4 serial: <filter> temp: 26.9 C
Partition:
ID-1: / size: 160 GiB used: 25.83 GiB (16.1%) fs: btrfs dev: /dev/nvme0n1p3
ID-2: /boot/efi size: 299.4 MiB used: 19.5 MiB (6.5%) fs: vfat
dev: /dev/nvme0n1p1
Swap:
ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 40.5 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 64 GiB available: 62.29 GiB used: 3.16 GiB (5.1%)
Processes: 484 Power: uptime: 1m wakeups: 0 Init: systemd v: 256
target: graphical (5) default: graphical
Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 10
Compilers: gcc: 14.2.1 Shell: Bash v: 5.2.32 running-in: konsole
inxi: 3.3.36
Perhaps you have found the problem. There is no occurrence of “cursor” in the journal.
It may be unrelated but Plasma 5 themes could not work correctly with Plasma 6, you need a Plasma 6 theme. I had missing icons, maybe it is the same with the mouse cursor. Try with a different theme or ignore this comment if you are using the default Plasma 6 theme.
1 Like
Thanks for your suggestion. I played around with it, but it was not the problem.
My current best guess is that you have sent me in the direction of a solution.
I think the problem is that my journal in Fedora 41 does have lines that look like these
Dec 01 04:40:29 sddm-helper-start-x11user[1168]: Setting default cursor…
Dec 01 04:40:42 sddm-helper-start-x11user[1727]: Setting default cursor…
Those lines are from when I boot my machine using OpenMandriva Linux
Your iGPU may need the xe module:
% modinfo xe
filename: /lib/modules/6.11.10-300.fc41.x86_64/kernel/drivers/gpu/drm/xe/xe.ko.xz
import_ns: DMA_BUF
license: GPL and additional rights
description: Intel Xe Graphics
author: Intel Corporation
It does support your iGPU model:
% modinfo xe | grep 'pci:v00008086d00007D55'
alias: pci:v00008086d00007D55sv*sd*bc03sc*i*
I think desktops with Xe graphics provide a special memory configuration. A SFF model may be more like a laptop configuration. Search for your model on the LHDB to see if other distros use the Xe module.
Here, using Fedora 41 Workstation GNOME Wayland (with GDM):
% journalctl --no-hostname -b -g cursor|cat
-- No entries --
1 Like
The xe module is loaded during boot in both the working OpenMandriva and the cursor-deficient Fedora 41. There is something else that sets the default cursor in OpenMandriva, but not in Fedora 41. I’m beginning to fear that the only thing I can do is reinstall Fedora 41 and hope for the best. Is there any way I could get my problem to the developers of Fedora 41?
Yes, you can report a bug. Unfortunately you need to explain how it is possible to reproduce. Then it is possible to open a bug request.
I saw this here on the kde discourse:
Is it not that what you have?
Try to downgrade kwin. sudo dnf downgrade kwin
Thanks for your suggestion. I tried sudo dnf downgrade kwin, but it told me there is a problem with the installed packages and suggested I use the --skip-broken option. I tried that but --skip-broken is an unknown argument for dnf5. I then tried to install the LXQT desktop, but there was the same problem with the installed packages. So I tried to install the XCFE desktop. That worked and I have cursors in it.
So the XCFE desktop is usable, but I like my KDE.
Is the xe module still loaded in a user session? I wonder if it bails out and is replaced by i915.
1 Like
Yes, you are correct that xe is loaded at the start of a user session.
I dual-boot my machine with Fedora and OpenMandriva because I expect that occasionally my love of using Fedora’s Betas will run into a problem that will take a while to resolve. Since I think the package dependencies are currently a mess in Fedora 41 KDE, I guess using OpenMandriva for a while is the solution to my problem. But thank you so much for your help!
Just so you know, the modules xe and i915 are both loaded when I use OpenMadriva, which suggests to me that they should be loaded in Fedora 41 KDE. Correct me if I am wrong.
Should I mark this as solved? It doesn’t seem to be the solution people would want to find.
Your issue may affect other distros when they update to package versions used in Fedora, so the community will benefit if you can find time to provide more details:
- Compare
inxi -Dzfor both Fedora and OpenMandriva? I’m not familiar with the latter. - Use
journalctlto look for errors related to thei915andxemodules. Maybe the priority option will help isolate the relevant entries. Thexemodule name is unfortunate as it appears in many irrelevant journalctl entries. You can try to find a grep pattern, maybe'kernel: xe', that omits irrelevant entries.
Dropped
--skip-brokenoption, as it was already available in DNF4 only for compatibility reasons with YUM, but it has no effect. Instead, the decision about selecting the newer version of a package into the transaction and skipping possible dependency issues is based on the :ref:best <best_option_ref-label>or :ref:no-best <no_best_option_ref-label>option.
So, --skip-broken is not available in dnf5 anymore. Use --best or --no-best instead.
If you want to use skip-broken you can do while call dnf with the comman dnf4
Thanks for being so helpful in attempting to solve this problem. Unfortunately, neither --best nor --no-best could resolve the dependency problems in trying to downgrade kwin.
My current solution is to wait a week, and hopefully, the mess of dependency problems in Fedora 41 KDE will have been resolved. Since I like to use Fedora KDE Betas, I dual-boot my machine with another Linux to cope with situations like this.
1 Like