[COMPASS-7263] The application stays on a white screen after startup Created: 26/Sep/23  Updated: 29/Oct/23  Resolved: 13/Oct/23

Status: Closed
Project: Compass
Component/s: None
Affects Version/s: 1.40.0
Fix Version/s: 1.40.3

Type: Bug Priority: Major - P3
Reporter: Balam Eliseo Barrón Ortíz Assignee: Unassigned
Resolution: Fixed Votes: 5
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OS: Linux


Attachments: File 6513434212a10db1220d51a8_log.gz     HTML File 6514aca159fe9114e5f1a634_log     HTML File 6515a6cfaeff2fddc1307cae_log     File 6515bf0dec799f95eefe552f_log-1.gz     File 6515bf0dec799f95eefe552f_log.gz     File 6515bf1aba47deaae108a9ad_log.gz     File General.json     File _usr_lib_mongodb-compass_MongoDB Compass.1000.crash     File compass_error.mp4     File compass_error02.mp4     File compass_error03.mp4    
Issue Links:
Depends
depends on COMPASS-7291 Upgrade electron to the latest 26 or 27 Needs Triage
Duplicate
is duplicated by COMPASS-7283 Compass window turns white few second... Closed
is duplicated by COMPASS-7309 White screen Closed
Related
is related to COMPASS-7269 Compass should start even when prefer... Closed
Documentation Changes: Not Needed

 Description   

Problem Statement/Rationale

I start the app, it shows me my connections and then it loads the screen without selecting anything and it goes blank



 Comments   
Comment by Balam Eliseo Barrón Ortíz [ 13/Oct/23 ]

Hello
If the problem is solved, thank you

Comment by Dominik Zogg [ 12/Oct/23 ]

Yes its fixed, i update the flatpak package, so it can be used there as well

Comment by Basit Chonka [ 12/Oct/23 ]

We published Compass v1.40.3 that fixes this issue, where we downgraded electron to 25.8.4.

Comment by Le Roux Bodenstein [ 11/Oct/23 ]

You could try the latest beta where we rolled back electron: https://github.com/mongodb-js/compass/releases/tag/v1.40.3-beta.4

Comment by Krushna Joshi [ 09/Oct/23 ]

Hi,

 

just wanted to know if there is any update on this or should we use 1.39.x versions for now?

I'm also facing this same issue.

Comment by Dominik Zogg [ 08/Oct/23 ]

I got the same issue testing the flatpak builds for 1.40.x, thats the reason i haven't merged those changes, so it does not break the flatpak version.

Comment by Anna Henningsen [ 02/Oct/23 ]

balam.barron@tfja.gob.mx Thank you! This makes us almost certain that this issue is one that has been reported for other applications as well: https://github.com/electron/electron/issues/39775

We’ll keep this ticket updated as we figure out what we can do about it from our side.

Comment by Balam Eliseo Barrón Ortíz [ 02/Oct/23 ]

crash

_usr_lib_mongodb-compass_MongoDB Compass.1000.crash

 

Revisando el archivo no encontré conexión a la base

Comment by Balam Eliseo Barrón Ortíz [ 02/Oct/23 ]

Hello Sergei and Anna

I think there was an error in the translation and the part of the * where what jira did was make it bold, if I found the files mentioned and deleted them, I no longer save my connections, I don't have any variables like the one you mention, I only have the following variables:

XDG_CONFIG_DIRS=/etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
XDG_MENU_PREFIX=xfce-
XDG_SEAT=seat0
XDG_SESSION_DESKTOP=xubuntu
XDG_SESSION_TYPE=x11
XDG_GREETER_DATA_DIR=/var/lib/lightdm-data/balam
XDG_CURRENT_DESKTOP=XFCE
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
XDG_SESSION_CLASS=user
XDG_VTNR=7
XDG_SESSION_ID=c2
XDG_RUNTIME_DIR=/run/user/1000
xdg_data

I did find the aforementioned General.json file, check its contents, however, it does not have folder save references, I attach it, I also attach the crash files for your evaluation.

General.json

General.json

Crash

 

Comment by Anna Henningsen [ 02/Oct/23 ]

balam.barron@tfja.gob.mx It’s also great to know that these files in /var/crash exist – if you can upload them, please feel free to do so, they may prove helpful in finally diagnosing this issue. (Be aware that these files may contain any data that the Compass application has loaded, e.g. saved connection strings).

Comment by Sergey Petushkov [ 02/Oct/23 ]

Hmmmm, that's interesting that you can't locate those files. I'm afraid there are more questions we'd have to ask to clarify some details:

  • Do you still see your saved connection after this clean up when starting the app?
  • Maybe that's already what you did, but I think you might need to include * in your find command to make sure you're looking for the partial name, so something like: find ~/ -name "*Compass"
  • If doing the above didn't help find the config folder:
    • Do you have $XDG_CONFIG_HOME set on your machine to some non-default value? In this case I think this is where the files will end up at.
    • Can you try locating folder called AppPreferences or a file called General.json (it should be inside this user data folder)? This should help you find the location of those Compass config files
Comment by Balam Eliseo Barrón Ortíz [ 29/Sep/23 ]

Hello Sergey

When I deleted, in fact, I only deleted the ".mongodb/compass" folder and the ".cache/gnome-software/odrs/mongodb-compass.desktop.json" file. Following your recommendation, I deleted the files in the ".config" folder and deleted the following files:

"/var/crash/_usr_lib_mongodb-compass_MongoDB Compass.1000.uploaded"
"/var/crash/_usr_lib_mongodb-compass_MongoDB Compass.1000.upload"
"/var/crash/_usr_lib_mongodb-compass_MongoDB Compass.1000.crash"

I searched my computer using find -name compass , mongodb-compass, Compass, mongodb and MongoDB and I did not find any other files that were related, I uninstalled the software and installed it again After deleting the folders, however, it did not solve the problem, I will continue trying to see what causes the problem, I validated with 2 colleagues to install the latest version and they had no problems, they also use Xubuntu but we did not identify what the difference is or the problem.

Comment by Sergey Petushkov [ 29/Sep/23 ]

balam.barron@tfja.gob.mx just wanted to say first that we extremely appreciate your patience in helping us debug the issue, there are some other similar reports we're seeing and so far we can't pinpoint the issue, thank you a lot for trying out all those things we ask you for!

When you say you cleaned up all the files generated by Compass, do you also mean the user data files? Asking because in the video we can see your saved connections in the side bar and if you'd remove all the files, favorite connections should also be gone in theory. On linux all those user data files should be under the "~/.config/MongoDB Compass" folder. Something in there can be the root cause, so potentially removing the contents of this folder might resolve the issue. BEFORE YOU TRY REMOVING THIS FOLDER can you back this folder up please so that you can restore your saved connections later and we can potentially investigate with your help what exactly there might be the root cause if removing it will help?

Comment by Balam Eliseo Barrón Ortíz [ 28/Sep/23 ]

Anna

Instead of closing the application I clicked on the connect and exit menu and the following error returned:

 

Error sending from webFrameMain:  Error: Render frame was disposed before WebFrameMain could be accessed
    at WebFrameMain.send (node:electron/js2c/browser_init:2:94495)
    at WebContents.send (node:electron/js2c/browser_init:2:79721)
    at App.<anonymous> (/usr/lib/mongodb-compass/resources/app.asar/build/main.js:2:93245)
    at App.emit (node:events:513:28)
    at click (/usr/lib/mongodb-compass/resources/app.asar/build/959.js:1:11879)
    at MenuItem.click (node:electron/js2c/browser_init:2:30958)
    at Menu._executeCommand (node:electron/js2c/browser_init:2:36354)

Comment by Balam Eliseo Barrón Ortíz [ 28/Sep/23 ]

hello Anna

I purged the installation and cleaned the files generated by the compass, reinstalled again and I still have the problem, I even installed the beta version, but it didn't work, I attached the log files and the video

Log's files

6515bf1aba47deaae108a9ad_log.gz

6515bf0dec799f95eefe552f_log.gz

Video

compass_error03.mp4

Comment by Anna Henningsen [ 28/Sep/23 ]

balam.barron@tfja.gob.mx Thank you again for sharing these! Unfortunately, the log seems to cut off early, it’s hard to tell whether that’s related to the problem itself or not.

Is it possible for you to run Compass and open the Developer Tools console? On Linux, that should work with Ctrl+Alt+I, or under View → Toggle DevTools. That should give us some better hints about what’s happening. Also, if you run Compass via the terminal like you did in the last session here, are you getting any output there?

Comment by Balam Eliseo Barrón Ortíz [ 28/Sep/23 ]

hello Anna

Attached the information I had the same result

Log

6515a6cfaeff2fddc1307cae_log

 

Video

compass_error02.mp4

Comment by Anna Henningsen [ 28/Sep/23 ]

balam.barron@tfja.gob.mx Could you check what happens when you run Compass from the command line with --no-networkTraffic, i.e. /path/to/mongodb-compass --no-networkTraffic?

Comment by Balam Eliseo Barrón Ortíz [ 27/Sep/23 ]

Hi Rhys.

Unfortunately, the error still appears attached to the application log file, to avoid any false positives, purge the software and reinstall and it still generates the error 6514aca159fe9114e5f1a634_log

Comment by Rhys Howell [ 27/Sep/23 ]

Hi balam.barron@tfja.gob.mx - we've fixed this in https://jira.mongodb.org/browse/COMPASS-7269 which is released in 1.40.2 - can you update and give it another try? Thanks for reporting the issue! Apologies for the inconvenience.

Comment by PM Bot [ 26/Sep/23 ]

Hello balam.barron@tfja.gob.mx, thank you for reaching out to us! The team will review your issue and get back to you soon as soon as possible.

Please review your issue to ensure you've included your environment details and have attached relevant logs (with any sensitive data redacted), so that we're best able to provide you a timely and thorough response. Thanks again!

Generated at Wed Feb 07 22:45:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.