Inconsistent cursor size in Cinnamon

Issues & Assistance Cinnamon
1

Hey everyone, I'm not new to Garuda here but after updating my system about an hour ago I've been running into a few snags with my cursor. Although I managed to get it all set to the specific theme I wanted, thanks to the cursor themes page on the Arch Wiki, the one thing that still eludes me in Cinnamon however is setting a consistent cursor size, this issue has persisted for me well before the theme issue I mentioned.

I am currently using the Nordzy-cursors-white cursor theme and unfortunately the size slider in mouse and touchpad section doesn't apply to all windows and programs, as most applications such as Steam and Lutris will set the cursor to its smallest setting, when I want the cursor to be a little bigger across the board.

Spent a few hours scouring the internet on and off for the past couple of weeks and I'm seemingly at a dead stop so I thought I'd ask here. It's not a major issue by any means but it would be nice to have my cursor be a little bigger no matter what I'm hovering over.

System:
  Kernel: 6.0.11-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=d1811421-52d9-438e-bac3-684cad066ec0 rw rootflags=subvol=@
    quiet quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
    loglevel=3 ibt=off
  Desktop: Cinnamon v: 5.6.4 tk: GTK v: 3.24.35 wm: muffin vt: 7 dm: LightDM
    v: 1.32.0 Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Desktop System: Tactus product: Custom v: N/A
    serial: <superuser required>
  Mobo: ASUSTeK model: ROG STRIX X570-E GAMING WIFI II v: Rev X.0x
    serial: <superuser required> UEFI: American Megatrends v: 4101
    date: 09/10/2021
Battery:
  Device-1: hidpp_battery_0 model: Logitech G305 Lightspeed Wireless Gaming
    Mouse serial: <filter> charge: 100% (should be ignored) rechargeable: yes
    status: discharging
CPU:
  Info: model: AMD Ryzen 9 5900X bits: 64 type: MT MCP arch: Zen 3 gen: 4
    level: v3 note: check built: 2021-22 process: TSMC n7 (7nm)
    family: 0x19 (25) model-id: 0x21 (33) stepping: 2 microcode: 0xA201204
  Topology: cpus: 1x cores: 12 tpc: 2 threads: 24 smt: enabled cache:
    L1: 768 KiB desc: d-12x32 KiB; i-12x32 KiB L2: 6 MiB desc: 12x512 KiB
    L3: 64 MiB desc: 2x32 MiB
  Speed (MHz): avg: 3686 high: 3700 min/max: 2200/4950 boost: enabled
    scaling: driver: acpi-cpufreq governor: performance cores: 1: 3700 2: 3700
    3: 3700 4: 3700 5: 3700 6: 3700 7: 3700 8: 3700 9: 3700 10: 3700 11: 3700
    12: 3700 13: 3700 14: 3700 15: 3700 16: 3700 17: 3593 18: 3593 19: 3700
    20: 3700 21: 3700 22: 3700 23: 3700 24: 3593 bogomips: 177262
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  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: retbleed 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: Retpolines, IBPB: conditional, IBRS_FW,
    STIBP: always-on, RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Navi 21 [Radeon RX 6800/6800 XT / 6900 XT] vendor: Gigabyte
    driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm)
    built: 2020-22 pcie: gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-2
    empty: DP-1,HDMI-A-1,HDMI-A-2 bus-ID: 0c:00.0 chip-ID: 1002:73bf
    class-ID: 0300
  Display: x11 server: X.Org v: 21.1.4 with: Xwayland v: 22.1.5 driver: X:
    loaded: amdgpu unloaded: modesetting,radeon alternate: fbdev,vesa
    dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.65x15.00")
    s-diag: 777mm (30.58")
  Monitor-1: DP-2 mapped: DisplayPort-1 model: Gigabyte AORUS FI32Q
    serial: <filter> built: 2021 res: 2560x1440 dpi: 93 gamma: 1.2
    size: 698x392mm (27.48x15.43") diag: 801mm (31.5") ratio: 16:9 modes:
    max: 2560x1440 min: 720x400
  API: OpenGL v: 4.6 Mesa 22.2.3 renderer: AMD Radeon RX 6800 XT (navi21
    LLVM 14.0.6 DRM 3.48 6.0.11-zen1-1-zen) direct render: Yes
Audio:
  Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel
    bus-ID: 1-3:2 pcie: gen: 4 chip-ID: 19f7:0003 class-ID: 0300 speed: 16 GT/s
    lanes: 16 bus-ID: 0c:00.1 chip-ID: 1002:ab28 class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: ASUSTeK
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 0e:00.4 chip-ID: 1022:1487 class-ID: 0403
  Device-3: RODE Microphones NT-USB type: USB
    driver: hid-generic,snd-usb-audio,usbhid
  Device-4: Creative Pebble V3 type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 5-2:2 chip-ID: 041e:3272
    class-ID: 0300 serial: <filter>
  Sound API: ALSA v: k6.0.11-zen1-1-zen running: yes
  Sound Server-1: PulseAudio v: 16.1 running: no
  Sound Server-2: PipeWire v: 0.3.61 running: yes
Network:
  Device-1: MEDIATEK MT7921K Wi-Fi 6E 80MHz driver: mt7921e v: kernel pcie:
    gen: 2 speed: 5 GT/s lanes: 1 bus-ID: 04:00.0 chip-ID: 14c3:0608
    class-ID: 0280
  IF: wlp4s0 state: up mac: <filter>
  Device-2: Realtek RTL8125 2.5GbE vendor: ASUSTeK driver: r8169 v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 port: e000 bus-ID: 05:00.0
    chip-ID: 10ec:8125 class-ID: 0200
  IF: enp5s0 state: down mac: <filter>
  Device-3: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb v: kernel
    pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 06:00.0
    chip-ID: 8086:1539 class-ID: 0200
  IF: enp6s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: MediaTek Wireless_Device type: USB driver: btusb v: 0.8
    bus-ID: 1-6:4 chip-ID: 0e8d:0608 class-ID: e001 serial: <filter>
  Report: bt-adapter ID: hci0 rfk-id: 0 state: up address: <filter>
Drives:
  Local Storage: total: 8.19 TiB used: 3.8 TiB (46.4%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Seagate model: FireCuda 530
    ZP1000GM30013 size: 931.51 GiB block-size: physical: 512 B logical: 512 B
    speed: 63.2 Gb/s lanes: 4 type: SSD serial: <filter> rev: SU6SM001
    temp: 40.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 QVO 2TB
    size: 1.82 TiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
    type: SSD serial: <filter> rev: 2B6Q
  ID-3: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST2000DM008-2FR102
    size: 1.82 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    type: HDD rpm: 7200 serial: <filter> rev: 0001
  ID-4: /dev/sdc maj-min: 8:32 vendor: Seagate model: ST4000NE001-2MA101
    size: 3.64 TiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    type: HDD rpm: 7200 serial: <filter> rev: EN01
Partition:
  ID-1: / raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 125.6 GiB (13.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 608 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 125.6 GiB (13.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-4: /var/log raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 125.6 GiB (13.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-5: /var/tmp raw-size: 931.22 GiB size: 931.22 GiB (100.00%)
    used: 125.6 GiB (13.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
  ID-1: swap-1 type: zram size: 62.71 GiB used: 768 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 37.0 C mobo: 33.0 C gpu: amdgpu temp: 67.0 C
    mem: 66.0 C
  Fan Speeds (RPM): N/A gpu: amdgpu fan: 0
Info:
  Processes: 469 Uptime: 12m wakeups: 3 Memory: 62.71 GiB
  used: 5.23 GiB (8.3%) Init: systemd v: 252 default: graphical
  tool: systemctl Compilers: gcc: 12.2.0 Packages: 1454 pm: pacman pkgs: 1442
  libs: 412 tools: paru pm: flatpak pkgs: 12 Shell: fish v: 3.5.1
  default: Bash v: 5.1.16 running-in: gnome-terminal inxi: 3.3.23
Garuda (2.6.10-1):
  System install date:     2022-11-20
  Last full system update: 2022-12-08
  Is partially upgraded:   No
  Relevant software:       NetworkManager
  Windows dual boot:       No/Undetected
  Snapshots:               Snapper
  Failed units:
1 Like
2

Hi @Mankybus, welcome to the community. :slightly_smiling_face:

There was another thread recently where someone had set up a GTK theme that was not being acknowledged by Qt apps in Cinnamon. I wonder if your cursor issue is a similar issue (GTK vs Qt theming)?

If so, you could try your hand at the solution in the linked thread, or a more straightforward method would be to use a theme engine like Kvantum to get Qt apps to accept your GTK theme.

The basic idea is you would add the Nordzy theme to Kvantum, and then set your Qt theme to Kvantum.

5 Likes
3

welcome to the community!

2 Likes
4

Thanks for the warm welcome! :slight_smile:
Sadly I have experimented around with Kvantum a couple of times before but I've not found anything relating to cursors or its size, unless there's something I'm missing of course :confused: I tried a few other suggestions on the thread you linked but none of them seemed to have worked neither, as the mouse still goes to its smallest size when hovering over Steam and such :frowning:

I've never had much of an issue with how apps look, as the Kvantum sweet-dark theme does work with qt apps just fine, it's purely the mouse cursor size that's completely stumped me right now.

5

As you see, it is a per-application issue. You should ask at the respective applications support, to get proper advice/info.

It is a GUI/Dev Toolkit issue. This is the beauty and ugliness of Linux. Each programmer writes the code he likes. Most of them don’t care to unify Linux experience. :person_shrugging:

Since you know Archwiki cursors page, you may want to try some of the workarounds listed there.

3 Likes
6

I did read through more of the page but I didn't spot anything that could be of use when it comes to sizing, so I'm not quite sure where I should start on that. I did use the XDG method to get my cursor theme universal across all apps at the least so I wonder if there's a way to set the size of the cursor in similar manner.

7

Cursors are like icons AFAIK. Look into how icon sizes are treated from those misbehaving apps, and…

3 Likes
8

Welcome to the community :smiley:

Garuda doesn't have any bugs or issues, those strange things happening are by design to sign up to the Garuda forum :smiley: :penguin: :eagle:

4 Likes
9

One must not conclude from the green M distribution to others. :grin:

4 Likes
10

I see then, was hoping there would be a more universal solution, seems like I have more to learn about GTK/QT/etc :sweat: Well this issue just so happens to affect the Garuda apps as well (Welcome, Gamer, Assistant, etc) so perhaps we could look into that for a start, if possible. :thinking:

11

Well it appears I fell right into their devious schemes, right where they want me :stuck_out_tongue: But thanks a ton for the welcome!

1 Like