Latest version breaks running it in KMSCON

[njjbjhbjhbhjbjhb]

On the latest version, I tried to run vtm in kmscon, and something happened. No mouse appeared, my top panel went away, and the bottom had messed up colors and "collin@collin-rx16:~$". What happened? I ran it on a laptop, with Zorin OS.

[o-sdn-o]

Thanks for reporting. I think it's because vtm changed its mouse tracking protocol. It happened around v2025.08.14. Try sudo killall vtm and reinstall vtm.

Update: I can't reproduce it, so it might be something else. If it doesn't work, I'll have to investigate it further.

[njjbjhbjhbhjbjhb]

I just saw something, the words "Segmentation fault".

[njjbjhbjhbhjbjhb]

https://drive.google.com/file/d/1WyjtOHeda8VG93-7ohNZ_wRC4RPxx8vG/view?usp=sharing
This is a link to a video.

[o-sdn-o]

Thanks for the video. Apparently I have a bug somewhere here.

[o-sdn-o]

I need some more information. Could you please share the output of the following commands:

kmscon -v
sudo vtm -a

Expected output:

sdn@zorinos17:~$ kmscon -v    
[0000.000000] NOTICE: kmscon Revision UnknownRevision Nov 12 2021 12:14:10 (log_print_init() in src/shl_log.c:509)
[0000.000051] INFO: conf: reading config file /etc/kmscon/kmscon.conf (conf_parse_file() in src/conf.c:547)
[0000.006421] ERROR: vt: cannot find parent tty (13, 13): Permission denied (seat_find_vt() in src/uterm_vt.c:791)
[0000.006516] ERROR: cannot create seat object on seat seat0: -14 (app_seat_new() in src/kmscon_main.c:221)
[0000.008519] WARNING: monitor: cannot open fbdev node /dev/fb0 for drm-device verification (13): Permission denied (get_fbdev_flags() in src/uterm_monitor.c:417)
[0000.008977] NOTICE: no running seats; exiting (main() in src/kmscon_main.c:629)
[0000.009531] INFO: exiting (main() in src/kmscon_main.c:667)
sdn@zorinos17:~$ sudo vtm -a                                                                                                      
Udev rules successfuly added to: "/etc/udev/rules.d/85-mouse.vtm.rules"
  # Allow all users direct access to pointing devices
  ACTION=="add", SUBSYSTEM=="input", KERNEL=="event*" ENV{ID_INPUT_MOUSE}=="1",         MODE="0666"
  ACTION=="add", SUBSYSTEM=="input", KERNEL=="event*" ENV{ID_INPUT_POINTINGSTICK}=="1", MODE="0666"
  ACTION=="add", SUBSYSTEM=="input", KERNEL=="event*" ENV{ID_INPUT_TOUCHPAD}=="1",      MODE="0666"
Trigger to reload udev rules:
  udevadm control --reload-rules
    Udev rules successfuly reloaded
    Set access bits 0666 for '/dev/input/event1' (Microsoft Vmbus HID-compliant Mouse)
sdn@zorinos17:~$ 

[o-sdn-o]

I found a bug in vtm rendering that can cause the crash you describe. I'll fix it in the next release.

[njjbjhbjhbhjbjhb]

collin@collin-RX16:~/vtm_linux_x86_64 (1)$ sudo vtm --uninstall && sudo ./vtm --install
[sudo] password for collin:     
File '/usr/local/bin/vtm' has been removed.
vtm is uninstalled.
Failed to copy process image ("/home/collin/vtm_linux_x86_64 (1)/vtm") to '/usr/local/bin/vtm"'.
collin@collin-RX16:~/vtm_linux_x86_64 (1)$  sudo ./vtm --install
Failed to copy process image ("/home/collin/vtm_linux_x86_64 (1)/vtm") to '/usr/local/bin/vtm"'.
collin@collin-RX16:~/vtm_linux_x86_64 (1)$ sudo ./vtm --install
Failed to copy process image ("/home/collin/vtm_linux_x86_64 (1)/vtm") to '/usr/local/bin/vtm"'.
collin@collin-RX16:~/vtm_linux_x86_64 (1)$ 

[o-sdn-o]

It seems that the problem is with file paths containing spaces. When there is a space in the file path, a quote creeps in at the end of the file name::

sdn@zorinos17:~/qq ww$ sudo ./vtm -i                                                                                              
[sudo] password for sdn:    
Failed to copy process image ("/home/sdn/qq ww/vtm") to '/usr/local/bin/vtm"'.
sdn@zorinos17:~/qq ww$ 

I will fix this bug in the next release. Thanks for the report.

[njjbjhbjhbhjbjhb]

I updated to the latest version, and it was worse. Now, nothing appears except for "Segmentation fault" but the GUI terminal works fine.

[o-sdn-o]

So there is a bug somewhere else. Could you please share the output of the following commands:

kmscon -v
sudo vtm -a

Expected output:

sdn@zorinos17:~$ kmscon -v    
[0000.000000] NOTICE: kmscon Revision UnknownRevision Nov 12 2021 12:14:10 (log_print_init() in src/shl_log.c:509)
[0000.000051] INFO: conf: reading config file /etc/kmscon/kmscon.conf (conf_parse_file() in src/conf.c:547)
[0000.006421] ERROR: vt: cannot find parent tty (13, 13): Permission denied (seat_find_vt() in src/uterm_vt.c:791)
[0000.006516] ERROR: cannot create seat object on seat seat0: -14 (app_seat_new() in src/kmscon_main.c:221)
[0000.008519] WARNING: monitor: cannot open fbdev node /dev/fb0 for drm-device verification (13): Permission denied (get_fbdev_flags() in src/uterm_monitor.c:417)
[0000.008977] NOTICE: no running seats; exiting (main() in src/kmscon_main.c:629)
[0000.009531] INFO: exiting (main() in src/kmscon_main.c:667)
sdn@zorinos17:~$ sudo vtm -a                                                                                                      
Udev rules successfuly added to: "/etc/udev/rules.d/85-mouse.vtm.rules"
  # Allow all users direct access to pointing devices
  ACTION=="add", SUBSYSTEM=="input", KERNEL=="event*" ENV{ID_INPUT_MOUSE}=="1",         MODE="0666"
  ACTION=="add", SUBSYSTEM=="input", KERNEL=="event*" ENV{ID_INPUT_POINTINGSTICK}=="1", MODE="0666"
  ACTION=="add", SUBSYSTEM=="input", KERNEL=="event*" ENV{ID_INPUT_TOUCHPAD}=="1",      MODE="0666"
Trigger to reload udev rules:
  udevadm control --reload-rules
    Udev rules successfuly reloaded
    Set access bits 0666 for '/dev/input/event1' (Microsoft Vmbus HID-compliant Mouse)
sdn@zorinos17:~$