desktop
desktop copied to clipboard
mattermost
Directory symlinks not followed when selecting an attachment
I confirm (by marking "x" in the [ ] below: [x]):
- [x] This is not a troubleshooting question. Troubleshooting questions go here: http://www.mattermost.org/troubleshoot/.
- [x] This doesn't reproduce on web browsers (such as in Chrome). If it does, issue reports go to the Mattermost Server repository.
- [x] I have read contributing guidelines.
Summary
Interface to add an attachment does not follow directory symlinks.
Steps to reproduce
- Pop!_OS 20.04 LTS
- Mattermost Desktop App version 4.6.0
- Mattermost Server version 5.25.0
- Open desktop client.
- Choose any channel.
- Click the paperclip icon.
- Double-click to navigate to a symlinked directory.
- Fail with the message 'There was a problem uploading your files."
Expected behavior Step 4 above does not fail, but instead navigates to the symlinked directory.
I have not observed this behavior with any other application on my machine.
Observed behavior Symlinks appear as files not directories in the GUI.
The only error message is "There was a problem uploading your files."
Possible fixes
?
JIRA tickets are created for all valid bug reports filed here. Bugs and features that the Mattermost core team are not immediately working on are opened as Help Wanted GitHub issues and welcome to contributions.
Our goal is to bring the Mattermost desktop repository into our day-to-day internal process with the hope of having more frequent desktop releases with faster feature development and turnaround time on bug fixes.
Hello and thanks for the feedback.
Quick question: does this behavior reproduces if you are using the browser for accessing mattermost?
It does not. The browser behaves as expected.
-------- Original Message -------- On Jan 18, 2021, 03:08, Guillermo Vayá wrote:
Hello and thanks for the feedback.
Quick question: does this behavior reproduces if you are using the browser for accessing mattermost?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
@wck0 Does this reproduce for you on v5.0.2? This does not reproduce for me.
