emqx / MQTTX

A Powerful and All-in-One MQTT 5.0 client toolbox for Desktop, CLI and WebSocket.

Home Page:https://mqttx.app

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Export data: No file in directory found

Jambola77 opened this issue · comments

What did I do

I tried to export the data from a recent session to the file system in json format.

What happened

Export dialog shows up and after presseing confirm the file seems to be written to my home directory.

Expected

I can see the file in my home directory, but it is not there! My home directory is empty.

Environment

  • OS: LinuxMint 21.1
  • MQTTX version: v1.9.6

More detail

grafik

I started the mqttx under my user, so I would not expect any write issues. It is interesting that previous written files are shown up in the dialog, but not on my ssd.

Hi, @Jambola77 . I have tested the export data feature of mqttx on both Ubuntu(Ubuntu 22.04.3 Gnome) and Mint(Linux Mint 21.2 Cinnamon), and they both work fine, generating files with correct content. Attached are the screenshots.

ubuntu
mint

I need more information from you to reproduce this issue. Firstly, did you install mqttx via deb/snap/flatpak/appimage? Secondly, are you using any other desktop environment, such as Mate? Finally, is it because of root permissions that you can't see these files as a normal user? Try to see if you can export the data to another folder?

Thank you!

Hi Ni00, I think I use flathub installation. Syslog says: Started app-flatpak-com.emqx.MQTTX-4645.scope.
grafik
The file should be there, but it is not.
grafik
I also tried to save under /tmp with the same results.

I have now searched my whole disk and it was found here:
/run/user/1000/.flatpak/com.emqx.MQTTX/tmp/Broker.json

This seems to be caused by Flatpak. I will test it later because I installed it using the .deb method before, so I may not have noticed this issue.

This issue is related to file system permissions after packaging with Flatpak. The files are generated in a unified directory for Flatpak, rather than in the user directory. I will wait for the 2.0 version update and test if this problem still exists. If there is an issue, it may be necessary to configure packaging parameters. Please refer to: https://docs.flatpak.org/en/latest/sandbox-permissions.html#filesystem-access