I am trying to install Choregraphe Suite on my macOS Catalina (v10.15.7) from the softbankrobotics website but I get this message:
Website link: https://developer.softbankrobotics.com/nao6/naoqi-developer-guide/choregraphe-suite/choregraphe-suite-installation-guide#desktop-installation
I don't know what I'm missing in order to run the installation on my laptop. I would appreciate it if anyone can help me on this.
Update: I left clicked it and it opened in command line. I went into the choregraphe-folder/bin/naoqi-bin and when I executed the file I got this:
Last login: Sat Nov 7 09:05:34 on ttys000
/Users/name/EEP_work/choregraphe-suite-2.8.6.23-mac64/bin/naoqi-bin ; exit;
name#Mahlas-MBP ~ % /Users/name/EEP_work/choregraphe-suite-2.8.6.23-mac64/bin/naoqi-bin ; exit;
dyld: Library not loaded: #rpath/QtCore.framework/Versions/5/QtCore
Referenced from: /Users/name/EEP_work/choregraphe-suite-2.8.6.23-mac64/bin/naoqi-bin
Reason: image not found
zsh: abort
[Process completed]
Thanks :)
You can go to the system settings > security & privacy and explicitly allow the opening of the installer (screenshot attached).
allow opening of installer
It will then bring up a second dialog:
"macOS cannot verify the developer of “choregraphe-suite-2.8.6.23-mac64-setup”. Are you sure you want to open it?
By opening this app, you will be overriding system security which can expose your computer and personal information to malware that may harm your Mac or compromise your privacy."
You can then click on "Open", but for my Mac (10.15.7) the installer crashes directly afterwards and I cannot install anything.
allow installation
It seems impossible to install Choregraphe on a recent Mac OS X. Help would be much appreciated.
'Allow install from internet' is the step you have to go over for all 3rd party apps(always happening) for macs. But still 'choregraphe' setup file didn't worked.
I hope my solution helps, i searched a lot too :)
install not setup file, try binaries oneenter image description here, and unzip. Open file you will see 'choregraphe' unix executable file, i clicked that file and app worked, best
P.s. i am not expert or anything that is only way i was able to make it work for my MacOs 10.15.7 (Catalina)
Related
I have installed and configured and also used TV the first time today in Nvidia jetson Xavier,
but after restart Im getting this issue:
teamviewerd.service: Can't open PID file /var/run/teamviewerd.pid (yet?) after start: No such file or directory
Please tell me why and how to fix it, it is of extreme importance !
I use TeamViewer to connect to a machine (Ubuntu 20.04) that not always have a graphical user session started and I noticed that even with teamviewerd running the machine is offline.
I fixed the problem running:
sudo teamviewer setup
From teamviewer --help:
teamviewer setup Configure headless modes (non-gui/console)
Without running this, the only way for me was to start manually a graphical user session and open the TeamViewer GUI on the host I wanted to use.
Make sure you enable/start gdm.service or another supported login manager
Found this question via a search when facing the same issue on Fedora 30 x86_64.
Solution for me was to edit /etc/systemd/system/teamviewerd.service and comment out the line that says:
PIDFile = /run/teamviewerd.pid
So it reads:
# PIDFile = /run/teamviewerd.pid
(or whatever PIDFile it specifies)
then run:
systemctl daemon-reload
systemctl start teamviewerd
systemctl status teamviewerd
I’m getting strange error while building project in Xcode 9.4
Build system information - unexpected service error: The Xcode build system has crashed. Please close and reopen your workspace.
I tried Xcode quit and reopen but that didn’t worked. Any solution?
Please clear derived data folder (located at ~/Library/Developer/Xcode/DerivedData) and restart the Xcode project.
This error usually happens between Xcode major versions. Apple usually claim their new build system is ** times faster than their previous version. If you see this error(I see this on changing Xcode9 to Xcode10 beta), you can always change it to the legacy build system. Here is how you can do this:
Open 'workspace settings'( it is now changed to 'Project Settings' if you are using Xcode10 or later) in the File Menu
Change build system to 'legacy'
Update for Xcode 13.4.1:
I had this infamous bug today as well. I tried a lot including clean project, delete derived, restart max etc.
What did the fix finally is similar to the answer of kakaiikaka: I set the workspace settings to "Legacy Build System (Deprecated)" for both, the shared and per user workspace. I tried to build with this, but got an error because I had packages wich are not supported.
Restarted Xcode, then changed back the build system. Restarted Xcode again.
Now the crash doesn't happen any more.
Looks like something internal was spoilt and cycling the build system fixed it.
I moved a lot of files all at once between folders, including nested folders. This error started happening. Nothing I did in regards to cleaning, purging derived data, or undoing the move operation would help.
What I did to help was: restore the previous version of the project file from source control and then re-add all the applicable new files to it. It was project file related. Deleting user data inside the project container did not help in my case. So as long as you use source control and can rollback the .xcodeproj, this may be an option.
it happened to me when i changed build configuration names. After deleting Pods folder and Podfile.lock, and then runnnig "pod install" fixed the issue.
For Xcode 10.2 delete podfile, podfile.lock, xcworkspace, open terminal, cd directory of project, pod init, add pods you want to pod file, pod install, open xcworkspac. Everything will be indexing now and then you can build.
I am trying out SecureInput extension sample that demonstrates NativeMessaging capabilities in MS Edge browser extensions and I running into problems deploying the extension after building using VS community edition 2017. I don’t have Universal Windows Platform Apps development experience, so I apologize if there is a pretty obvious answer I am not aware of. But following readme.md in the sample doesn’t work, so posting this question here...
https://github.com/MicrosoftEdge/MicrosoftEdge-Extensions-Demos/tree/master/SecureInput
Steps followed…
Turned on developer mode in “Use Developer Features”
Turned on Enable extension developer features in Edge browser’s about:flags.
Downloaded the sample as a zip file to the local machine.
Copied SecureInput.html to my local webserver
Loaded SecureInput.sln in VS
community edition 2017 Out of two options.. InProc or OutOfProc, I
wanted to try InProc. So needed to select Project in
NativeMessagingHostInProcess in Build Configuration manager. Other
settings used... Debug - configuration; Any CPU – Active solution
platform; NativeMessagingHostInProcess – x64 project platform as I
was using 64 bit Windows and edge running as a 64 bit process as
well; Left rest as default.
With Debug Configuration and Any CPU Solution platform built the entire solution.
Deployment Summary
Built Entire SecureInput solution.
Installed AppX package by running
Add-AppxPackage -register [PathtoSecureInputSolutionFolder] NativeMessagingHostInProcess\bin\x64\Debug\AppxManifest.xml
No errors during building or while running Add-AppXPackage from elevated Power shell prompt.
Expected: At this point EdgeBrowser->MoreOptions->Extensions should list extension installed by AppX package (Deployment Summary/Step 2). =>> Doesn’t happen.
Few other details
I am using 64 bit Win 10 creators build (1703 – OS build 16063.128)
I am suspecting Add-AppxPackage failed to add the extension silently. Verbose flag doesn’t give me any clues either.
Get-AppXPackage shows newly added AppX package.
Name : ae24a957-5239-43b2-a36c-b96805a58ade
Publisher : CN=msft
Architecture : X64
ResourceId :
Version : 1.0.0.0
PackageFullName : ae24a957-5239-43b2-a36c-b96805a58ade_1.0.0.0_x64__2yx4q2bk84nj4
InstallLocation : [PathtoSecureInputSolutionFolder] \NativeMessagingHostInProcess\bin\x64\Debug
IsFramework : False
PackageFamilyName : ae24a957-5239-43b2-a36c-b96805a58ade_2yx4q2bk84nj4 PublisherId : 2yx4q2bk84nj4
IsResourcePackage : False
IsBundle : False
IsDevelopmentMode : True
IsPartiallyStaged : False
I would like to know if anyone got this sample working. If Microsoft Edge folks are monitoring stackoverflow, I really appreciate if someone can jump in to help your early adopters like me. :-)
With offline help from Chee Chen, we were able to figure out why SecureInput was not working. My sincere thanks to him for going out of his way to help. In my specific case, here are the things that went wrong.
URL manifest.json gives permissions to is case sensitive. I had a typo when I first entered the URL in edge browser very first time.. I typed in as SecureInput.html. Try cleaning the cache if you see that using lower case secureinput.html doesn't help.
When instructions didn't work right first time, I used Add-AppxPackage way of deploying the Extension. While doing that, I picked AppxManifest file in NativeMessagingHostInProcess\bin\x64\Debug\AppxManifest.xml instead of NativeMessagingHostInProcess\bin\x64\Debug\AppX\AppxManifest.xml. Something to watch out for and if you make the same mistake, make sure you uninstall the appx package completely and start all over again.
So here are my supplemental instructions for others trying the sample :-)
Make sure you selected right Platform as per your target test machine. Edge runs as 64 bit process so your extension needs to be targeted at that platform.
Make sure right AppServiceName is selected in PasswordInputProtection->Program.cs and Extension->background.js
I think PasswordInputProtection.csproj has a hardcoded Program files (x86) in its path, which will break if you try the sample on 32 bit machine. Edit the project file in notepad and fix it before you try.
Ensure NativeMessagingHost project's Output paths are correctly configured... It needs to be "bin\[Platform]\[Configuration]\AppX\" and not "bin\[Platform]\[Configuration]\"
Avoid typos if you can, because I see very little feedback or verbose logs on why things are not working.
Have you tried following the deployment steps in the documentation? The actual steps and ordering is important:
Build and deploy the NativeMessagingHostinProcess UWP app.
This will generate:
Necessary binaries and files needed for the UWP app.
The AppX folder.
The AppXManifest.xml based on the content of package.manifest. (The content of package.manifest in this sample has been edited to include the necessary entries for Edge extensions).
Build the PasswordInputProtection Desktop Bridge.
This will:
Build the binaries for this project
Trigger a post-build event that will copy the output of the exe to the AppX folder and copy the Extension folder to the AppX folder.
Now that the files are all ready to go, you will need to register the AppX.
There are two ways to accomplish this:
Run Add-AppxPackage from PowerShell: Add-AppxPackage -register [Path to AppX folder]\AppxManifest.xml
OR
Deploy the NativeMessagingHostInProcess project. Visual Studio will run the same PowerShell script to register the AppX from the folder.
Mac OS X Lion 10.7.5(11G63)
installer-bbndk-bb10_1_x-macosx-338-201302012246-201302032157.dmg
BlackBerry10Simulator-Installer-BB10_1_X-338-Mac-201302031817.dmg
After install the upper two dmg files, I can find qde in the launchpad, but I can not find the "BlackBerry10Simulator-BB10_n_nn.vmwarevm" file".
I want to re-install ,so I run the app "BlackBerry10Simulator-Installer.app" in Finder->devices->BlackBerry10Simulator-BB10-1-x, just get the pop-up-box saying
The Installer cannot be run.
Multiple launches of this installer is not allowed. It will now quit
, and then the installer quit.
How can I find the simulator install path, or
How can I re-Install it successfully.
P.S.
At the first time installing, I did not change anything while installing, just clicked those "next","accept..." buttons.
I think the simulator should be installed in default file path, but I don't know where is it, and can't find it even searching "BlackBerry10Simulator" in Finder.
Maybe there is something wrong while first time installing simulator?
The BB10 simulators are VMware virtual machines. On a Mac, you need to have VMWare Fusion installed in order to run the simulator VM. This is mentioned in the system requirements. All the dmg installer does is uncompress the VMware image and place it on your hard drive. I just installed this myself, and the default location seems to be:
/Users/<your username>/Documents/Virtual Machines
Inside there should be a folder Blackberry10Simulator-BB10_1_X-338 and inside that there should be BlackBerry10Simulator-BB10_1_X.vmwarevm which contains the actual virtual machine .vmx and .vmdk files.
There should also be an alias (shortcut) created on your desktop to point to this location, called Blackberry 10 Simulator.
To uninstall, there is a script in Blackberry10Simulator-BB10_1_X-338/install called uninstaller which should remove everything and allow you to install again.
Unfortunately, VMWare Fusion is not free but you can sign up for a 30-day trial in order to be able to run the simulator and test out your app.
I recently encountered this error with a different installer (but also installanywhere based). There seems to be a problem with the mirroring feature in VM Ware Fusion and the multiple install detection in Install anywhere. If you disable mirroring, I suspect the "Multiple launches of this installer is not allowed." error will no longer occur.
I downloaded Python and installed it, and when I go download GoogleAppEngine_1.2.0.msi and try to install it and I get this error:
This installation package could not be
opened. Contact the application
vendor to verify that this is a valid
Windows Installer package.
Am I forgetting something? I am assuming this is pretty simple.
I had the same error. The file downloaded by IE was about 190k and would not run. The file ought to be 2.7M. Firefox downloads correctly. Also IE will download correctly if you select RUN instead of SAVE. That is my experience and I now have the SDK installed. I hope this helps you.
Download it again and try to install the newly downloaded file. Maybe the file was damaged during download or not completely downloaded which can both happen sometimes.
If this does not help and the same error message appears you could control the checksum which should be
5ea87b8ed3011a5f55a9135c96abe96b6a6fd48b
for this file.
When you are sure that the downloaded file is ok, check if the version of your operating system is supported.
Maybe installing the Windows installer could help?
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=5a58b56f-60b6-4412-95b9-54d056d6f9f4
If not, try out on another machine or inside a virtual machine.