Package: tigervnc-common
Version: 1.15.0+dfsg-2
Severity: normal
X-Debbugs-Cc: [email protected]
Dear Maintainer,
On Debian trixie, when launching tigervnc server for the first time, it
attempts to rename any existing ~/.vnc
folder to ~/.config/tigervnc. However, on a new headless server that the user
has not logged into graphically yet, ~/.config may not exist. This results in
vncserver failing with an error message like:
vncserver: Could not migrate /home/USER/.vnc to /home/USER/.config/tigervnc.
The 'mv' failure is coming from /usr/share/perl5/TigerVNC/Config.pm:1433.
Probably needs a:
mkpath(dirname($opts->{'vncUserDir'}));
before attempting the mv operation.
This can be reproduced by creating a ~/.vnc directory without a ~/.config
directory, and then running 'vncserver'.
Thanks,
Mike
-- System Information:
Debian Release: 13.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.12.74+deb13+1-amd64 (SMP w/32 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages tigervnc-common depends on:
ii libc6 2.41-12+deb13u2
ii libgcc-s1 14.2.0-19
ii libstdc++6 14.2.0-19
ii libx11-6 2:1.8.12-1
tigervnc-common recommends no packages.
tigervnc-common suggests no packages.
-- Configuration Files:
/etc/tigervnc/vncserver-config-defaults changed [not included]
-- no debconf information
