Description: Even when “Use data for document properties” in Preferences >> General >> User Data, my user dada is still being applied to documents I create or open by default. Steps to Reproduce: 0. Have Preferences >> General >> User Data >> Use Data for Document Properties off. 1. Open or create a document. 2. Go to File >> Properies. Actual Results: “Apply user data” is still checked. Expected Results: “Apply user data” should not be checked. Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes
This is a security issue. I don't want my information being leaked by default if I send something at 3 a.m. without manually removing my user data.
Please test with Menu>Help>Restart in Safe Mode. Please paste here the information in Menu>Help>About LibreOffice. (There is an icon in the center to copy the information).
Version: 25.8.1.1 (X86_64) Build ID: 54047653041915e595ad4e45cccea684809c77b5 CPU threads: 8; OS: Linux 6.8; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-US Calc: threaded Safe Mode didn't do anything.
Still an issue in 25.8.4.2-2.
Tested this: New user profile → Opened LO → Tools → Options → LibreOffice → User Data Written forename and surename in the fields, then → Use data for document properties → unckecked. File → New → Text document File → Properties → General "Apply user data" is checked. It shouldn't be checked when I have unchecked this in Tools → Options. So having a look at Tools → Options → LibreOffice → User Data: "Use data for document properties" is still unchecked, also unchecked when closing and opening LO again, but it won't do anything… Could confirm the buggy behavior. Tested with Version: 25.8.4.2 (X86_64) Build ID: 290daaa01b999472f0c7a3890eb6a550fd74c6df CPU threads: 6; OS: Linux 6.4; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: en-US Calc: threaded Tested also with older versions, earliest version here 6.4.7.2 - behavior is the same. Seems it never worked well.