cancel
Showing results for 
Search instead for 
Did you mean: 
SOLVED

Code: 500

aFouraker
Long-established Member

Code: 500

I am using a virtual machine with Ubuntu 18.04.5 LTS and getting the following problem went trying to install the python samples from SDK1.8 and SDK1.10. 

aFouraker_0-1628706554084.png

 

 

7 REPLIES 7
aFouraker
Long-established Member

Re: Code: 500

I saw in some other threads to build in WSL so I attempted that and have the following error:

aFouraker_0-1628798826573.png

I have treid many things to try and get around this error. Built as sudo user, built as sudo user with the -H flag, built from terminal and from inside of vscode, I have also tried building with the venv active and deactivated. The documentaion is unclear on this point.  

aFouraker
Long-established Member

Re: Code: 500

Is anyone else experiencing these problems? 

CodeShepherd
Community Moderator

Re: Code: 500

How did you copy the SDK data to your Ubuntu VM? Please use a "cp -r" function to copy the SDK to your working folder. If you are using exchange folders that are managed by windows the user rights could not be fitting in Ubuntu.

aFouraker
Long-established Member

Re: Code: 500

It is on in the WSL file system. It is in the location /home/$USER/home/SDK-... and was copied in the way you describe. 

Should it be in a differnet location? 

CodeShepherd
Community Moderator

Re: Code: 500

I am normally working directly in the user folder "~" but subfolders should make no difference.

Did you accidentally copy the data with "sudo cp -r"? Then the rights on the folder could be wrong, too. I would also suggest to probably use no spaces in your path (seen on the picture above).

aFouraker
Long-established Member

Re: Code: 500

I may have copied with sudo but I then changed the permissions with chmod. I will try again with no spaces in the path and will copy as the user that will build and see if that resolves it. 

aFouraker
Long-established Member

Re: Code: 500

After I recopied in the folders as @CodeShepherd recommended I was then able to build IF I used the sudo -H option with snapcraft, otherwise there were permission errors. It looked like this:

snapcraft clean

sudo -H snapcraft

 

Icon--AD-black-48x48Icon--address-consumer-data-black-48x48Icon--appointment-black-48x48Icon--back-left-black-48x48Icon--calendar-black-48x48Icon--center-alignedIcon--Checkbox-checkIcon--clock-black-48x48Icon--close-black-48x48Icon--compare-black-48x48Icon--confirmation-black-48x48Icon--dealer-details-black-48x48Icon--delete-black-48x48Icon--delivery-black-48x48Icon--down-black-48x48Icon--download-black-48x48Ic-OverlayAlertIcon--externallink-black-48x48Icon-Filledforward-right_adjustedIcon--grid-view-black-48x48IC_gd_Check-Circle170821_Icons_Community170823_Bosch_Icons170823_Bosch_Icons170821_Icons_CommunityIC-logout170821_Icons_Community170825_Bosch_Icons170821_Icons_CommunityIC-shopping-cart2170821_Icons_CommunityIC-upIC_UserIcon--imageIcon--info-i-black-48x48Icon--left-alignedIcon--Less-minimize-black-48x48Icon-FilledIcon--List-Check-grennIcon--List-Check-blackIcon--List-Cross-blackIcon--list-view-mobile-black-48x48Icon--list-view-black-48x48Icon--More-Maximize-black-48x48Icon--my-product-black-48x48Icon--newsletter-black-48x48Icon--payment-black-48x48Icon--print-black-48x48Icon--promotion-black-48x48Icon--registration-black-48x48Icon--Reset-black-48x48Icon--right-alignedshare-circle1Icon--share-black-48x48Icon--shopping-bag-black-48x48Icon-shopping-cartIcon--start-play-black-48x48Icon--store-locator-black-48x48Ic-OverlayAlertIcon--summary-black-48x48tumblrIcon-FilledvineIc-OverlayAlertwhishlist