ubuntu (re)start/launch problem (snap) - When ~/Documents is symlink

[nickma82]

Describe the bug rocketchat-desktop starts/launches once and failes all consecutive times when any of {~/Documents, ~/Pictures, ~/Music} is a symlink.

• During the first startup rocketchat creates it's config files (in my case in ~/snap/rocketchat-desktop/current/.config)
• It then failes to start UNTIL one provides a real directory (no symlink) at the ~/snap/rocketchat-desktop/current/.config/user-dirs.dirs :: XDG_* target paths
  • In my case ~/Documents (i.e. XDG_DOCUMENTS_DIR) was a symlink

To Reproduce

1. Revoke rocktechat config
   (e.g. rm -rf ~/snap/rocketchat-desktop/*)
2. Make your ~/Documents path a symlink
   (e.g. mv ~/Documents ~/Documents_moved && ln -s ~/Documents_moved ~/Documents)
3. Start rocketchat-desktop once -> everything works just fine (some minor GTK warnings, but well)
4. Close the electron app
5. Re-open rocketchat-desktop
   app closes without any output i.e. immediately with exit code (echo $?) == 1

Expected behavior Normal startup even if XDG_DOCUMENTS_DIR is a symlin.

Additional context Tested with all channel version today including {3.5.5, 3.0.0-develop, 3.2.2}

$ snap info rocketchat-desktop
name:      rocketchat-desktop
summary:   Official Desktop Client for Rocket.Chat
publisher: Rocket.Chat (rocketchat✓)
store-url: https://snapcraft.io/rocketchat-desktop
[...]
channels:
  latest/stable:    3.2.2          2021-05-14 (416) 68MB -
  latest/candidate: 3.3.0-snapshot 2021-06-12 (451) 70MB -
  latest/beta:      3.0.0-develop  2020-09-30 (191) 69MB -
  latest/edge:      3.5.5          2021-09-21 (517) 71MB -
installed:          3.5.5                     (517) 71MB -

Kernel Linux rock 5.11.0-34-generic Ubuntu rev VERSION="20.04.3 LTS (Focal Fossa)"

[nickma82]

Quick fix: delete the symlinked folders out of ~/snap/rocketchat-desktop/current/.config/user-dirs.dirs

[jeanfbrito]

Please test if the latest release did solve this. If not please reopen the issue or create a new one and tell us. I will be closing this one for now.

Thank you!

[nickma82]

Please test if the latest release did solve this.

Hi @jeanfbrito tested with v3.7.5, symptoms are the same.

[nickma82]

please reopen the issue

Github: "you cannot re-open your own issues if a repo collaborator closed them". @jeanfbrito please re-open it.