The File Manager in the whonix app cube no longer opens

Hello, everyone.
The File Manager in the whonix app cube no longer opens. To be precise, the text turns black and it works, but the File Manager and Tor browser windows don’t open. The problem isn’t that it doesn’t start up, but that data is stored inside, so you can’t retrieve it. Please tell me how to open File Manager or retrieve data from it. I would appreciate your answers.

Other information we can provide is as follows:

・Version is R4.2.3 - Qubes is installed in a brand-new external HDD with a 2TB capacity

・The problematic appcube template is a clone of whonix17 that was set up from the default

・After the problem was discovered, I updated dom0 and the Foo template to the latest version.

・The app cube created based on the 40 xfce template also does not work

・The disposable app cube made under the same conditions is working properly.

・The template that is the source of the problematic app cube is working properly, and the file manager can be opened as well.

Are you still using whonix 17 or have you updated to whonix 18?

Hello @phirip

First thing: If you have disk space, make a clone of the bad qube, and work on the clone. This will preserve the original of it, with all the backup volumes.

Some ideas - maybe one will help:

Then you can tell us what does work in the clone and in your Qubes system… I am thinking memor, disk or obsolete file manager application…

  • terminal? console? other applications?
    • can you use qvm-copy in the terminal of the clone, to send the files to some other qube?
    • can you open some apps using terminal? Does the terminal show any errors? Do the windows appear?
    • can you run top in the clone terminal or console, to verify free and used memory?
    • can you run df to verify disk volume is not full?
  • create new qube based on the same template?
    • does file manager open in the new one?
  • Settings for the clone?
    • verify memory settings - not too small?
    • verify the Applications tab…
      • Do any applications at right pane show errors?
      • Try “refresh” and activate some other file manager(s), some other applications?
  • Can you change the template of the clone, or of a new clone? Try a template that works fully, and that allows to create new qubes with file manager… You can set netvm to empty to avoid accidental reveal of the qube.

What do you see? Does any test allow you to get your files? Tell us which one, please!

Thank you both of you. I will answer them in order.

still using whonix17 ?

I’m still using 17; I updated to 17 and haven’t evolved it to 18

Can I use the QVM-copy of the clone terminal to send files to other Qubes?

Are you saying to create more clones of problematic clone apps for Qube and put them into other Qubes? I thought it was a good idea and tried it, but it wouldn’t start.

Can I open some apps using the terminal?
Is there an error display in the terminal?
Will the window be displayed?

For problematic Qube apps, only the settings screen will be displayed.

Can I move the top button on a clone device or console to check available and used memory? Can I run DF to check if the disk volume is full? Check the memory settings – isn’t it too small? > Regarding memory, since the amount of data stored is small, I think this should not be a problem. However, In the AppSettings, the memory/CPU settings in Advanced remain at their default settings.

Create a new QBE based on the same template?
Does the new file manager open it?

Using the same template, I created a new app, and as a result, the file manager opened.

What about the clone settings?
Default settings Please check the Applications tab… Are there any applications that show errors on the right panel?

No. Try “Refresh” to enable other file managers and applications.
You can’t open the problematic AppQube terminal or file manager, but you can open the settings screen, so try running an application refresh but it doesn’t work. The problem seems to lie not with this whonix template, but with the data you entered (it’s puzzling that the same problem occurs even with Fedra without data).

If the data you enter is too large for Qube and causes a problem, what kind of action should be taken? Should I increase the memory/CPU in the Advanced section of AppSetting?