*Xcursor* is a format for the graphics of the cursor in *X11* (file reports X11 cursor). xcursorgen allows you to convert PNG files and some metadata to Xcursor files. How do I convert an Xcursor file to PNG images? Imagemagick's convert unfortunately returns: >> no decode delegate for this image format

According to the documentation of [XCreateFontCursor]: > Applications are encouraged to use this interface for their cursors because the font can be customized for the individual display type. How do I actually customize the cursor generated from this method? I've tried setting XCURSOR_SIZE environment variable to no percieved effect, I've tried setting XCursor.theme: redglass in my Xresources and this changes some applications but not all, (interestingly emacs uses the selected theme in the editor area but not in the menu bars) and as I am using dwm as my window manager no configuration specific to a desktop environment is applicable.

I'm left-handed and I want to be able to correctly flip any arbitrary xcursor theme so that I can use it as a left-handed version. I’m surprised this isn’t build in. So a way to flip an xcursor file, say /usr/share/icons/Bibata-Original-Ice-LH/cursors/pencil, would help me do that. I expected it to be as simple as convert pencil -flop pencil, but Imagemagick doesn’t support xcursor files, it seems. And scripting it with Gimp’s script-fu would work, but when using gimp-file-xmc-save it expects me to set the hotspot and such, and I can’t find any way to find the old values from the existing file I opened (let alone the hassle of learning Scheme just to do the math to get the flipped values).

Suppose you have several X cursors on your system such as golden-xcursors or silver-xcursors. I already know it's possible to specify which cursor size you prefer by editing ~/.Xresources. For example: Xcursor.theme: Gold Xcursor.size: 16 But how can I get the list of available X cursor sizes to choose from (for example: 32, 48 or 64)? Is there a command for that?

I have a plan to make my own Xcursor theme. I'm looking at existing themes and found some strange names such as 08e8e1c95fe2fc01f976f1e063a24ccd. I found a piece of code that contain this name. https://vimsky.com/examples/detail/cpp-ex---QHash-reserve-method.html According to the comment, it seems to be an MD5 hash of something hardcoded. But I failed to produce this hash. Which programs need these names? All the themes installed on my system are symbolic links to these names, but I can't find any documentation for this. And there are two cursors named size_bdiag for top-right/bottom-left window resizing and size_fdiag for top-left/bottom-right window resizing. But I failed to understand what these names mean. Maybe 'diag' means 'diagonal' but still I can't guess what 'b' and 'f' mean. I googled several times but I can't find any documentation. Do those have no meaning? Is the original author just playing with me?

A square area around my mouse pointer is being rendered incorrectly. Instead of rendering the window it is supposed to render, it seems to be rendering the window underneath instead. It is very clear in this screenshot, which omits the mouse pointer itself, but in which you can see part of my gray desktop background “through” the all-white Konsole window: If I log out and then log in again, without rebooting, the problem goes away. Here are a couple more screenshots, cropped to the areas of interest: Here the pointer is hovering over the Firefox tab with the blue “J”; the black popup is the tool tip for the tab, part of it is missing and you can see the main Firefox window instead: Here the pointer is hovering over the Firefox “try again” button, but X has rendered a bit from the Spectacle window that is underneath Firefox: My X server is:

X.Org X Server 1.19.3
Release Date: 2017-03-15
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.0-87-generic x86_64 Ubuntu
Current Operating System: Linux avocet 4.10.0-33-generic #37~16.04.1-Ubuntu SMP Fri Aug 11 14:07:24 UTC 2017 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.10.0-33-generic root=UUID=19f82f72-a807-4624-a7aa-8297febd0f5a ro quiet splash vt.handoff=7
Build Date: 25 July 2017  01:30:08PM
xorg-server 2:1.19.3-1ubuntu1~16.04.2 (For technical support please see http://www.ubuntu.com/support)  
Current version of pixman: 0.33.6

The OS is:

Distributor ID: Ubuntu
Description:    Ubuntu 16.04.3 LTS
Release:        16.04
Codename:       xenial

The window system is KDE. The hardware is a Lenovo Thinkpad T460p laptop. I'm not sure which parts of the system configuration are relevant. Here's the compositor configuration: Here's part of the output of lshw that seems relevant: *-pci:1 description: PCI bridge product: Sky Lake PCIe Controller (x4) vendor: Intel Corporation physical id: 1.2 bus info: pci@0000:00:01.2 version: 07 width: 32 bits clock: 33MHz capabilities: pci pm msi pciexpress normal_decode bus_master cap_list configuration: driver=pcieport resources: irq:121 ioport:d000(size=4096) memory:f1000000-f1ffffff ioport:c0000000(size=301989888) *-display description: 3D controller product: GM108M [GeForce 940MX] vendor: NVIDIA Corporation physical id: 0 bus info: pci@0000:02:00.0 version: a2 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=nvidia latency=0 resources: irq:130 memory:f1000000-f1ffffff memory:c0000000-cfffffff memory:d0000000-d1ffffff ioport:d000(size=128) *-display description: VGA compatible controller product: Intel Corporation vendor: Intel Corporation physical id: 2 bus info: pci@0000:00:02.0 version: 06 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:126 memory:f0000000-f0ffffff memory:e0000000-efffffff ioport:e000(size=64) memory:c0000-dffff How should I proceed in trying to diagnose and fix this? If I should be reporting a bug, then to whom should I report it, and how? [ Added 2017-SEP-18: This appears to be a bug, [described here](https://www.kubuntuforums.net/showthread.php/72149-Mouse-artifact-introduced-in-7-26-update) . Restarting sddm with sudo systemctl restart sddm works around the problem. ]

I am automatically hiding the cursor with unclutter -idle 3 in my bspwmrc. But I want the cursor to show again ever time I focus a different window with the keyboard. (This would provide a little more visual feedback as to which window focus was moved to). bspwm has a setting that makes the cursor move to the newly focused window anytime you change focus with the keyboard. This setting is enabled for me, but it doesn't make a difference visually because the cursor is almost always hidden. Ideally, I would like to modify the keybindings I have to change focus so that they unhide the cursor before (or immediately after) changing focus, then three seconds later, unclutter would hide it again. There doesn't seem to be an option to show the cursor once it has been hidden with unclutter, and googling around didn't produce any results. Is there a command that will show the cursor?

I have problems with cursor size on one of my Xorg screens on CentOS 7. I have two screens. One runs xfce4 window manager and desktop, while another runs mwm window manager. This is a custom setup, which allows a fullscreen Motif application to run on screen with mwm, and other apps on xfce4 screen. I also have special kind of monitor for Motif app, which is 2048x2048 resolution. The problem I have is that all except one cursors are to big on mwm, while on xfce4 they are all normal. Cursor shaped "X" on desktop background is normal size while others are oversized. Here's a picture where an one of oversizeds cursor can be seen: How can I change the size of cursors on mwm screen? I have tried Xcursor.size in Xresources, but with no effect. Here are some more pictures showing cursor sizes. **Another update:** I have tried different window managers to see if cursor size is big there too. KDE, for instance, works fine. However, when I open XTerm window cursors are too big within that window. The app I use also uses Xt and Motif widgets, and also shows big cursors.

So, I'm on a HiDPI machine (XPS 9370) and using the Adwaita cursor; this is on a fresh install of Antergos w/ i3 for context. I've been playing around with some settings for adapting to HiDPI, but I realized that my cursor changes size depending on what application it is hovering on. Whereas when not hovering over any application or hovering over a few, it may be sized appropriately for the display, but, say when hovering over termite or Firefox, it will decrease to a fraction of the size and become barely visible. How do I make the cursor size consistent across the entire system? Xcursor.size does not seem to affect the cursor sizes in the programs I listed.

Under Kubuntu 17.04, I'm trying to obtain a dual pointer setup where one is attached to my mouse as usual and the other is attached to the touchscreen that otherwise works correctly while attached to the core pointer (including pinch-like gestures): $ xinput ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ My touchscreen id=11 [slave pointer (2)] ⎜ ↳ My mouse id=18 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ... Following this answer , I created another pointer and attached the touchscreen to it: $ xinput create-master Touchscreen $ xinput reattach 11 "Touchscreen pointer" $ xinput ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ My mouse id=18 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ... ⎡ Touchscreen pointer id=21 [master pointer (22)] ⎜ ↳ My touchscreen id=11 [slave pointer (21)] ⎜ ↳ Touchscreen XTEST pointer id=23 [slave pointer (21)] ⎣ Touchscreen keyboard id=22 [master keyboard (21)] ↳ Touchscreen XTEST keyboard id=24 [slave keyboard (22)] This is also functional, including gestures. The problem is the cursor attached to the Touchscreen pointer flickers. This does not happen with the core pointer. What is weird is that the flicker only happens when the I move the mouse pointer. If I don't move the mouse, the Touchscreen pointer stays invisible when the touchscreen is not used, which is very close to what I want. **Ideally, the touchscreen pointer would stay always hidden.** Solution 1 (doesn't work): -------------------------- Using xicursorset as suggested by the above answer . The code ultimately uses XIDefineCursor to set the cursor image for individual pointers. This simply did nothing for me under KDE, no errors. If it worked, I would set the cursor to an empty image, which I'm not sure would solve the flickering issue. Solution 2 (only partially works): ---------------------------------- Leaving the touchscreen floating via: $ xinput float 11 $ xinput ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ My mouse id=18 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ... ∼ My touchscreen id=11 [floating slave] In this configuration, no KDE window recognizes the touchscreen but surprisingly, Chrome recognizes gestures like one finger scroll or two finger pinch zoom. If I could get this kind of functionality in every window, it would be enough for me. Solution 3 (works in theory, not in practice due to crash): ----------------------------------------------------------- To add/remove pointer dynamically. In other words, using the following script called ~/.local/bin/watch-touchscreen.py: #!/usr/bin/python import sys; from subprocess import call; while True: line = sys.stdin.readline() if line.startswith("button press"): call(["xinput", "create-master", "Touchscreen"]) call(["xinput", "reattach", "11", "Touchscreen pointer"]) elif line.startswith("button release"): call(["xinput", "remove-master", "Touchscreen pointer"]) like this: $ xinput test 11 | ~/.local/bin/watch-touchscreen.py The idea is to create a new pointer every time the touchscreen is touched and destroy it when the touch is released, at which point the touchscreen would return to being a floating slave. This works very briefly until the X session promptly crashes, forcing me to login again. Not a clever idea to dynamically create and destroy xinput pointers after all, I guess. Any ideas, workarounds?

I am currently using the nouveau DRM with fallback xf86-video-modesetting drivers on arch linux with a GTX 1080. I am currently experiencing an issue in x.org where my mouse will be stuck at the position on the top left of my monitor about 10 pixels from (0,0). When I run xev -root, I still see mouse movement registered and I can see the mouse cursor actually change (from cursor to I-bone to glove) as it should depending on what it's "hovering" over. The mouse itself is still usable as I can click/right click things just as normal (I will have to "guess" the mouse position based on what text is selected, what window is in focus from mouse hover, etc). Xorg.0.log: http://pastebin.com/RqurVjz0 $lsmod Module Size Used by fuse 98304 3 snd_usb_audio 155648 2 mousedev 20480 0 snd_usbmidi_lib 28672 1 snd_usb_audio joydev 20480 0 snd_rawmidi 28672 1 snd_usbmidi_lib input_leds 16384 0 snd_seq_device 16384 1 snd_rawmidi cfg80211 495616 0 snd_hda_codec_hdmi 45056 1 nls_iso8859_1 16384 1 nls_cp437 20480 1 vfat 20480 1 fat 65536 1 vfat intel_rapl 20480 0 x86_pkg_temp_thermal 16384 0 intel_powerclamp 16384 0 coretemp 16384 0 kvm_intel 188416 0 kvm 516096 1 kvm_intel irqbypass 16384 1 kvm crct10dif_pclmul 16384 0 crc32_pclmul 16384 0 crc32c_intel 24576 0 ghash_clmulni_intel 16384 0 aesni_intel 167936 0 aes_x86_64 20480 1 aesni_intel lrw 16384 1 aesni_intel eeepc_wmi 16384 0 gf128mul 16384 1 lrw glue_helper 16384 1 aesni_intel asus_wmi 24576 1 eeepc_wmi ablk_helper 16384 1 aesni_intel sparse_keymap 16384 1 asus_wmi iTCO_wdt 16384 0 cryptd 20480 3 ablk_helper,ghash_clmulni_intel,aesni_intel iTCO_vendor_support 16384 1 iTCO_wdt led_class 16384 2 asus_wmi,input_leds intel_cstate 16384 0 intel_rapl_perf 16384 0 pcspkr 16384 0 nouveau 1523712 2 psmouse 126976 0 ttm 86016 1 nouveau drm_kms_helper 126976 1 nouveau drm 294912 5 nouveau,ttm,drm_kms_helper syscopyarea 16384 1 drm_kms_helper sysfillrect 16384 1 drm_kms_helper sysimgblt 16384 1 drm_kms_helper snd_hda_codec_realtek 69632 1 snd_hda_codec_generic 69632 1 snd_hda_codec_realtek fb_sys_fops 16384 1 drm_kms_helper i2c_algo_bit 16384 1 nouveau mei_me 36864 0 mei 86016 1 mei_me e1000e 229376 0 snd_hda_intel 32768 5 snd_hda_codec 106496 4 snd_hda_intel,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek snd_hda_core 65536 5 snd_hda_intel,snd_hda_codec,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec_realtek ptp 20480 1 e1000e snd_hwdep 16384 2 snd_hda_codec,snd_usb_audio pps_core 20480 1 ptp i2c_i801 24576 0 snd_pcm 90112 6 snd_hda_intel,snd_hda_codec,snd_usb_audio,snd_hda_core,snd_hda_codec_hdmi i2c_smbus 16384 1 i2c_i801 snd_timer 28672 1 snd_pcm snd 69632 25 snd_hda_intel,snd_hwdep,snd_hda_codec,snd_usb_audio,snd_timer,snd_rawmidi,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_usbmidi_lib,snd_seq_device,snd_hda_codec_realtek,snd_pcm soundcore 16384 1 snd hci_uart 81920 0 shpchp 32768 0 btbcm 16384 1 hci_uart btqca 16384 1 hci_uart btintel 16384 1 hci_uart fan 16384 0 bluetooth 487424 4 hci_uart,btintel,btqca,btbcm thermal 20480 0 battery 20480 0 rfkill 20480 4 asus_wmi,bluetooth,cfg80211 i2c_hid 20480 0 intel_lpss_acpi 16384 0 intel_lpss 16384 1 intel_lpss_acpi fjes 28672 0 evdev 24576 13 acpi_pad 20480 0 mac_hid 16384 0 acpi_als 16384 0 kfifo_buf 16384 1 acpi_als industrialio 53248 2 acpi_als,kfifo_buf tpm_tis 16384 0 tpm_tis_core 20480 1 tpm_tis tpm 36864 2 tpm_tis,tpm_tis_core sch_fq_codel 20480 2 ip_tables 28672 0 x_tables 28672 1 ip_tables ext4 524288 1 crc16 16384 2 bluetooth,ext4 jbd2 90112 1 ext4 fscrypto 24576 1 ext4 mbcache 16384 2 ext4 sd_mod 36864 3 hid_generic 16384 0 usbhid 49152 0 hid 114688 3 i2c_hid,hid_generic,usbhid uas 24576 0 usb_storage 61440 1 uas serio_raw 16384 0 atkbd 24576 0 libps2 16384 2 atkbd,psmouse mxm_wmi 16384 1 nouveau ahci 36864 2 libahci 28672 1 ahci xhci_pci 16384 0 libata 208896 2 ahci,libahci xhci_hcd 172032 1 xhci_pci usbcore 208896 7 usbhid,snd_usb_audio,usb_storage,xhci_pci,snd_usbmidi_lib,uas,xhci_hcd scsi_mod 159744 4 sd_mod,usb_storage,libata,uas usb_common 16384 1 usbcore i8042 28672 0 serio 20480 6 serio_raw,atkbd,psmouse,i8042 wmi 16384 3 asus_wmi,mxm_wmi,nouveau video 36864 2 asus_wmi,nouveau button 16384 1 nouveau I can have an empty xorg.conf or the xorg.conf configured by the nvidia DRM, so this is negligible. However, I will go ahead and post my xorg.conf $cat /etc/X11/xorg.conf.bak # nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 370.28 (buildmeister@swio-display-x64-rhel04-17) Thu Sep 1 20:22:52 PDT 2016 Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" 0 0 InputDevice "Keyboard0" "CoreKeyboard" InputDevice "Mouse0" "CorePointer" EndSection Section "Files" EndSection Section "InputDevice" # generated from default Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/psaux" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" # generated from default Identifier "Keyboard0" Driver "kbd" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Unknown" ModelName "Unknown" HorizSync 28.0 - 33.0 VertRefresh 43.0 - 72.0 Option "DPMS" EndSection Section "Device" Identifier "Device0" #Driver "nvidia" VendorName "NVIDIA Corporation" EndSection Section "Screen" Identifier "Screen0" Device "Device0" Monitor "Monitor0" DefaultDepth 24 SubSection "Display" Depth 24 EndSubSection EndSection Here's the output from lspci: 00:00.0 Host bridge: Intel Corporation Skylake Host Bridge/DRAM Registers (rev 07) 00:01.0 PCI bridge: Intel Corporation Skylake PCIe Controller (x16) (rev 07) 00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31) 00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31) 00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] (rev 31) 00:1b.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Root Port #17 (rev f1) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1) 00:1c.2 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #3 (rev f1) 00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31) 00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31) 00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31) 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V (rev 31) 01:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1080] (rev a1) 01:00.1 Audio device: NVIDIA Corporation GP104 High Definition Audio Controller (rev a1) 03:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller 04:00.0 PCI bridge: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge (rev 04) **EDIT:** This behavior is actually the same in a vanilla arch install without nvidia drivers.

I have created a replacement for xterm cursor that will allow me to see the cursor (Windows, incidentally, calls the xterm cursor the "i-beam", which is rather more descriptive) much better. Problem is, I've yet to be able to correctly convert the PNG to the xcursor format. Anyone know what I can do here? OS: Linux Mint 17.3 (Ubuntu-based; understands Debian packages)

When I use rdesktop to connect to a Microsoft Windows server, the mouse cursor is set to a monochrome version of the Windows true-colour cursor. This ends up being a white arrow with no outline, so it's very difficult to see it over a white surface. I don't want to change the cursor on the Windows machine, but my understanding of how Xcursor works is following: When any cursor is set, it is looked up by filename (using a hash of the cursor image) so that if a match is found, that Xcursor is used instead of the original monochrome one. My idea is that if I can supply this file and put a clearer cursor image in it (like the default arrow) then it will solve my problem by using the default arrow most of the time. Plus it will still allow rdesktop to change the cursor to something else (like a resize arrow) if the remote machine needs to. * How can I find out what hash to use for the rdesktop cursor image I am getting? * How can I map that hash to the normal arrow cursor in the theme I am using?