Bug 7799 - vncviewer creates ~/.vnc on connect
Summary: vncviewer creates ~/.vnc on connect
Status: CLOSED FIXED
Alias: None
Product: ThinLinc
Classification: Unclassified
Component: VNC (show other bugs)
Version: trunk
Hardware: PC Unknown
: P2 Normal
Target Milestone: 4.19.0
Assignee: Pierre Ossman
URL:
Keywords: adaha_tester, relnotes
Depends on:
Blocks:
 
Reported: 2021-11-19 13:49 CET by Pierre Ossman
Modified: 2025-02-13 15:41 CET (History)
2 users (show)

See Also:
Acceptance Criteria:
MUST: * No permanent non-ThinLinc files or directories should be created by running and using the ThinLinc client

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Pierre Ossman cendio 2021-11-19 13:49:22 CET 
Upstream TigerVNC uses ~/.vnc to store its configuration (among other things). We've patched ours to not use that configuration as we have our own. Unfortunately our viewer still tries to create the directory each start, which isn't really correct.

Seen with 4.13.0, but has probably been around since at least 2011.
Comment 1 Pierre Ossman cendio 2024-05-21 14:58:41 CEST 
TigerVNC has now started respecting XDG directories, so we should be seeing ~/.config/tigervnc and similar instead.
Comment 2 Pierre Ossman cendio 2025-02-04 16:35:52 CET 
Doing this now since it will get worse with the update in bug 8485.
Comment 4 Pierre Ossman cendio 2025-02-07 11:00:51 CET 
Seems to work well. Tested on macOS 15, Windows 11 and Fedora 41. ThinLinc 4.18.0 created a "vnc" directory on all three, but the latest build does not.
Comment 5 Adam Halim cendio 2025-02-13 15:41:22 CET 
Tested client build 3809 on Fedora 40, Windows 10 and macOS 15.

Confirmed that the "vnc" directory is no longer created, while they are created with ThinLinc 4.18.0.

The commit & release note look good.
Note You need to log in before you can comment on or make changes to this bug.