https://bugs.documentfoundation.org/show_bug.cgi?id=132577

            Bug ID: 132577
           Summary: [Enhancement][Snap] Default save location should not
                    be inside "~/snap/libreoffice".
           Product: LibreOffice
           Version: 6.4.3.2 release
          Hardware: All
                OS: Linux (All)
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: medium
         Component: UI
          Assignee: libreoffice-bugs@lists.freedesktop.org
          Reporter: sampmccorm...@gmail.com

Description:
When installed as a Snap, the default save location in Libreoffice Writer is
"~/snap/libreoffice/XXX". I have first-hand experience of this being a severe
usability problem. 

Case study:

- User is new to Linux and installs Libreoffice as a Snap alongside version
from repositories. 
- User saves document in Snap Libreoffice to the default location.
- User uninstalls Snap version of Libreoffice.
- User's documents are deleted.

Although this may not sound serious ("who would not save to ~/Documents?"), the
reality is that Libreoffice is one the programs that inexperienced Linux users
are most likely to try. These users are unfamiliar with how the Snap packaging
system works.

I suggest that Libreoffice chooses "~" as its default save location, or perhaps
"~/Documents" if it exists.

Steps to Reproduce:
1. Open Libreoffice Writer (freshly installed via Snap) on Linux.
2. Press "Ctrl"+"S".
3. View default save location.

Actual Results:
Default save location is "~/snap/libreoffice/XXX".

Expected Results:
Default save location should be home ("~"), or perhaps "~/Documents" if it
exists.


Reproducible: Always


User Profile Reset: No



Additional Info:
Only applies when Libreoffice is installed as a Snap.

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs

Reply via email to