I want to export a collection. The process seems simple: Export Data → Export the full collection → Export → Save. Yet, after clicking Save, nothing happens… not errors, no progress bar, nothing. And, of course, nothing is saved. The Target output file UI sees other .json files in the target directory. This should be a simple procedure.
Version 1.45.4
I don’t see a “Save”
I see EXPORT DATA → dropdown Export the Full Collection
Then I see:
And I click “Export …” and up pops a file requester for the filename.
Works every time.
What are you experiencing?
Note that the latest Compass is 1.46.2 …
The file requestor which I assume is the Target output file dialog box has a Save button in the lower right corner. When I click the Save button, the dialog box closes, but nothing else happens. I know no files get saved because I ran a find command. And I’ve tried a half dozen different file paths.
I haven’t had time to install the newer version, but I assume Export should have worked for the previous 15 versions.
Brian, try saving in a different directory where you’re sure you have write permissions.
I tried that. It’s no big deal. I can export from the database. I just can’t use compass to do it.
@Brian_Sheely can you share your log file with us? Retrieve Compass Logs - Compass - MongoDB Docs
That might have more information we can use to debug the issue.
Tried a quick manual on my windows machine and I was able to successfully export.
I’m having the same issues with the latest version of Compass 1.46.3 (Stable) on Kubuntu Linux 24.04.
The log file states the following error: “$listSearchIndexes stage is only allowed on MongoDB Atlas”
I tried to export data from a local MongoDB installation so I definetly don’t have an Atlas running on my local machine.
Any ideas?
@Christian_Nielebock That’s an unrelated error, we check for search indexes support by running that command for the indexes tab. Do you see a Start export log in your log file? id 1001000185
I figured out that the log files are json and not gzipped.
Nothing is logged at all when i click on the save button.
I kave the same error on Kubuntu using version 1.46.3.
I have the exact same symptons as described by @Brian_Sheely .
After clicking on the save button, nothjing happens.
Log files are not readable on my system:
gzip -d 68482502e71c994c8b6db2a2_log.gz
gzip: 68482502e71c994c8b6db2a2_log.gz: unexpected end of file
Ark throws a similar error saying files are corrupted.
compass_log.txt (5.6 KB)
I tried to export this morning. There’s not much activity in the log. I don’t event see an attempt to export. Maybe the gui just doesn’t work.
I have the same issue on Kubuntu. Been happening since at least version 1.46.3. I upgrade to 1.46.4 just now and have the same issue. Its extremely frustrating. Would be great if it could be fixed.
Did anyone actually file an issue on this?
1 Like
I did just now 1. COMPASS-9503
I did just now
Good, @Alistair_Prestidge, but I feel you should edit your issue:
- Copy and paste in the fine report that was made here, that’s what the engineers want. Don’t demand that they browse to the Forums. Give them all the details in the issue!
- Do provide the logs and other info they request.
Bug reports (says this development engineer) should be totally self-contained. If you put everything in the bug report, someone might decide to eat lunch at their desk and fix the problem 
1 Like
Also responded on the jira ticket:
Does selecting the home folder in the file save dialog before saving fix the issue? That would give us a check of if it is the issue from the investigation below is it. (Also it would serve as a workaround for now).
Doing some investigation:
This may be the same file pathing issue filed in signal’s desktop app: Unable to save media or files via Desktop on Linux, while Android works fine · Issue #6912 · signalapp/Signal-Desktop · GitHub
They fixed in Fix file save dialog default path for Linux KDE · signalapp/Signal-Desktop@520620f · GitHub
Seeing mentions of a KDE Portal xdg-desktop-portal-kde issue happening which may be the root cause of the bug. [Bug]: GNU/Linux/Fedora/KDE: file selection dialog doesn't work · Issue #42250 · electron/electron · GitHub
Which means our file selector returns nothing so we just are closing the file selection.
As a fix we can try explicitly adding the home path for these environments, similar to the signal fix.
3 Likes
Thanks for share!
clicking Home before navigating to the desired folder indeed could be used as a workaround!
I was going crazy here for this bug!!!