I'm using Pop OS 20.4 and installed Unity Hub from its store (I think it just downloads the app image from the Unity website and installs it but I don't know).
I set a personal license and want to install the version 2020.1.15f1. As you can see on the next tab there is enough space to install it
Unfortunately I get this error message when trying to install it
at the bottom of the hub this toast message appears
Does someone know what's wrong here? I clearly have enough space on my disk.
I get the same error for other versions too.
Ok here is the solution that worked for me:
Instead of installing it from the Pop OS store I uninstalled this Unity hub version. I restarted my machine and installed the .appimage file from the official website. I copied that file into the root of my home directory. When executing this version there was no error for me.
The reason why it is showing this error is because there is not enough space in your root directory. Typically this happens when there is only a single partition (at least in my case). So a workaround for this is to create a folder in you HOME directory called tmp and running the UnityHub.AppImage file pointing to that tmp folder and the application gets ample amount of space to install. It looks something like this :
TEMP=~/tmp ./UnityHub.AppImage
You can go to this link for further details.
Related
Background
I just developed my first flutter desktop app for a windows machine. The app is working fine while developing/debugging it, but I am trying to test it as an application in release mode.
What’s done
I created an msix using pub msix.
For signing, I have tried both my
own certificate and the test certificate that comes with msix
packages by default.
I have tried both stable and beta channels.
Actual Problem
When I install the app on the other system (or even on the actual system where I debugged the app). I can install the msix setup successfully I can see my app listed in the apps, but when I try to open it, it is stuck on a blank/white screen. There is no UI rendered. And if I try to maximize the window, it goes to App not responding state.
Any help will be really appreciated.
Thanks in advance.
Update / New Finding
After going through the links provided by Yehuda Kremer and pulling my hair for a few days, I found the answer in this tweet
https://twitter.com/FilledStacks/status/1436280577439715338?s=20
So the main issue is that app is using some absolute paths that don't work on other machines (after release)
1- My app was using a database, so I have made sure that that database path is relative to the application document directory.
2- Now the build is also referring to some dependencies and their paths are also absolute. I have noticed a flag CMAKE_INSTALL_LOCAL_ONLY in the cmake_install.cmake but that flag is not being set anywhere.
Here is the log of flutter build windows -v
https://pastebin.com/LAeshUMY
-- Now I am looking for a proper way to convert all the paths to relative so that the build is ready for installation on different machines, instead of local installation only.
I have found the solution.
The main problem was that the app was looking for some dependencies and it was unable to find them. As mentioned here.
The reason for not finding that in release mode can be one of the following,
You are using some dll (package that depends on a dll) that is available on a specific path in your system, but when you are release the app that (absolute) path is not valid anymore.
You are adding some asset with absolute path (that is only applicable to your system).
Solution:
If it is a dll, you should be adding that to the release folder. In my case it was sqlite3.dll
If it is some other asset then you should always use the relative path.
You mentioned msix package, let see if the problem is in the app or in the packaging process
run flutter build windows without the flutter pub run msix:create, then run the created .exe file to see if its work.
btw this issue mention here: https://github.com/flutter/flutter/issues/74507
and here (the 'maximizing' problem): Black screen appears on maximizing and minimizing flutter desktop app
I'm trying to install moodle4mac on Catalina via a .dmg file. The .dmg file mounts okay. However, when I try to drag the MAMP folder to the Applications folder, I get the message "The operation can’t be completed because you don’t have permission to access some of the items."
When install dialog is showing 4 folders;
.DocumentRevisions-V100
.TemporaryItems
.Trashes
.fseventsd
The first three have no go signs on the folders suggesting that these are the problematic ones. I have checked the read/write permissions of the Applications folder, which looks fine. I have also run sudo spctl --master-disable which gives me the opportunity to download apps from anywhere, but this does not make any difference.
Any pointers greatly welcome!
Okay. It turns out the culprit was Sophos Home Antivirus. There was no indication in any of the error messages that Sophos was blocking this, hence I did not put two and two together. However, a warning message about the mounted volume popped up this morning, and I was able to trace this back to Sophos. It would be great if Sophos / MacOS could provide more detailed messages regarding such errors in future.
Unity 3d doesnt work, when I try to open my project it says that This can happen if layout contains custom windows and there are compile errors in the project. I tried reinstalling OpenGL and something that I found on the internet but didn't work. The error window says that Revert Factory Settings but same thing happens after it too my Unity version is 2020.1.0a My OS is Ubuntu and I gave all the permissions to some folders. Didn't work And all this happened after a fresh install
Unity 2020.1.0a3 is an ALPHA VERSION!
As any alpha version it is not stable for production and can be expected to be full of bugs and unexpected behavior.
Search through the Known Issues in 2020.1.0a3 maybe your problem is already listed there.
In general do not touch alpha or beta versions unless you want to checkout a new added feature and test it.
For anything else stick to the stable releases like 2019.1.14f1 or 2019.2.6f1
On the last letter you can see their state:
a = Alpha
b = Beta
f = Release
Not sure if these are related but here and here also others had this problem already in early version so maybe one of their hot-fixes work for you as well.
This error may occur in released versions.
To resolve this problem:
Go to this directory:
C:\Users{YOUR_USER}\AppData\Roaming\Unity\Editor-5.x\Preferences\Layouts\default
Open Default.wlt file with Notepad or any text editor and copy all its contents.
Go to your unity project directory like this:
{YOUR_UNITY_PROJECT}\Library
Open CurrentLayout-default.dwlt file with Notepad or any text editor and delete all its contents then paste the contents of Default.wlt that you copied in step 2
If these files exist in Library delete them:
CurrentMaximizeLayout.dwlt
CurrentLayout.dwlt
Stop the Unity Hub service by a click the system tray and right-click on Unity Hub icon then select Quit Unity Hub.
Run your project again.
Jeez, how hard is it to get SQL Developer to work.
Last month I downloaded the latest version and kept getting the cannot find ‘msvcr100.dll’ file error.
So I reverted back to an old version I had installed.
Now I have downloaded the latest version 4.2.0.
1 The first time I tried to launch it I was asked to set the JDK path. So I set it to ‘C:\Program Files\Java\jdk1.8.0_121’. Is this correct??
2 When I launch SQL Developer I get the initial splash screen, the progress bar does not get half way, and then it vanishes.
3 I went into the folder sqldeveloper\sqldeveloper\bin and amended the file ‘sqldeveloper.conf’ i.e. SetJavaHome C:/Program Files/Java/jdk1.8.0_121
I still get the splash screen and then it vanishes.
Anyone with any ideas.
Cheers
I experienced the same problem with the version with the built-in JDK and finally got it to work by:
1) Removing all other versions of Java from the system
2) Commenting the line under the #Set our usage tracking URI line in the sqldeveloper.conf file (sqldeveloper/sqldeveloper/bin)
Not sure which one did the trick but hoping this helps someone else.
I've downloaded and installed STS 3.8.2 on my Mac (10.12.1). Each time the STS.app file is launched, it creates a new org.springsource.sts_3.8.2.RELEASE_########_macosx_cocoa_x86_64 folder under the hidden .eclipse folder (the hashes are there because I have MANY of the same folder with the numbers in the hash area being the only difference). In doing so, the default workspace and all plugins I installed the last time it was running are wiped out (because they exist in the previous #### folder).
I've tried installing the previous 3.8.1 and 3.8.0 version, but they are doing the same thing. My previous STS install started at 3.7 and has been upgraded to 3.8.1, but will not update anymore because of update errors that I can't seem to fix (none of the StackOverflow "fixes" have worked for me).
Is there a way to have STS not create a new folder (instance) in the .eclipse folder each time it launches? If so, how?
This got reported to STS and is documented here:
https://issuetracker.springsource.com/browse/STS-4406
The corresponding bug at Eclipse is:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=507328
To cut a long story short:
This is caused by macOS Sierra Gatekeeper App Translocation, a security feature that moves the app into a private read-only location for security reasons. Therefore Eclipse/STS creates a folder for its configuration in that location that you described above.
Since macOS Sierra does the app translocation again after every restart, Eclipse/STS doesn't know anything about the "old" configuration area anymore and creates a new one. As far as I can see, there is no way for Eclipse/STS to distinguish between a separate install and a newly translocated app... :-(
The workaround is:
A) Move STS.app into a different location on your disc after
unpacking the tar.gz archive (using the Finder, not the command
line). If you move it to "Applications", for example, everything
works as before (no app translocation happens in that case).
B) You could also start Eclipse/STS by clicking on the Executable (in
STS.app/Contents/MacOS). That also doesn't cause app translocation
and therefore everything is fine.
As this bug — alternatively unfortunate side-effect of Apple security measures — still exists in STS 3.9.8 (I assume also in 3.9.9) and the Eclipse bug report in the previous answer is closed as a duplicate of Workspace Preferences Do Not Persist on MacOS Sierra that, while being marked as "solved, actually in itself actually do not solve this dislocation issue — in that moving the app to /Applications or having a signed DMG, both making no difference — the info missing is that one can turn off App Dislocation on an app by app basis by using the "xattr" command in the Terminal, that works upon extended file attributes.
Use the command
sudo xattr -r -d com.apple.quarantine /Applications/sts.app
where -r makes the command recursive for all app contents (macOS apps being folders) and -d deletes the particular attribute at the given path.
To verify a successful result simply run
sudo xattr /Applications/sts.app
The successful result you want is a new prompt line. If you get "quarantine" on there you were not successful.
Note that, I could only test this in macOS 10.12.6