Ticket Created
over 5 years ago

WERETECH-9679

SDK Manager fails in Fedora Linux

Split off from other bug report.

The SDK manager gives the following error on Fedora 32:

Unable to download the list of SDKs. Error code: 33554509

and

Unable to downloaded the device list. Error code: 33554509

The errors occur after successfully logging in.

using an ubuntu docker image, the sdkmanager does work.

Also tried to run sdkmanager via a proxy to see what it was doing. If I configure a system proxy then sdkmanager makes a few successful requests to cloudflare then crashes with a segmentation violation.

9256409
  • over 4 years ago in reply to Former Member

    yes Slight smile

    so the sdk manager, rely on the fact that mac os x is now shipped with open ssl at a specific location, which wasn't the case with mac os 10.11

    In order to make it starting :

    1 - install brew on your mac

    /bin/bash -c "$(curl -fsSL raw.githubusercontent.com/.../install.sh)"
    

    2 - install open ssl : brew install openssl
    

    Here, I had a few issues which I needed to solve, like permission, etc, sorry but I can't remember the details..... look at the messages it returns during install, if I remember, on package failed, and it was easy to miss it doing so.
    

    3 - run this :
    

         sudo mkdir /usr/local/etc/openssl
        sudo ln -s /usr/local/etc/[email protected]/cert.pem /usr/local/etc/openssl/cert.pem
    

    the sdk manager will then start immediately Slight smile
    

    Good luck.
    

    
	
    

    

    
	
    
		
	
    

    

    
		 			
    
		
	
    

    

    • 

	

  • 
	
    


    
	
    
					Former Member
			
    
	
    
		
			
							Former Member
					
		
			over 4 years ago
		
									
					in reply to Klick
				
						
    

    

    
			
    I get the same on Mac os X 10.11 - have you found a fix? 
    
	
    

    

    
	
    
		
	
    

    

    
		 			
    
		
	
    

    

    • 

	

  • 
	
    


    
	
    
					
			
    
	
    
		
			
											
					
		
			over 5 years ago
		
									
					in reply to Klick
				
						
    

    

    
			
    My account works with the following:
    

    $ cat Dockerfile 
FROM ubuntu:bionic

RUN DEBIAN_FRONTEND=noninteractive apt-get -y update && DEBIAN_FRONTEND=noninteractive apt-get -y install software-properties-common && DEBIAN_FRONTEND=noninteractive apt-get -y update && DEBIAN_FRONTEND=noninteractive apt-get -y install git openjdk-8-jre-headless build-essential sudo wget unzip libxxf86vm1 libgtk2.0-0 openssh-server libusb-1.0-0 libsm6 libwebkitgtk-1.0-0 imagemagick imagemagick-common x11-apps nodejs && apt-get clean && rm -rf /var/lib/apt/lists/*

RUN wget https://developer.garmin.com/downloads/connect-iq/sdk-manager/connectiq-sdk-manager-linux.zip && unzip connectiq-sdk-manager-linux.zip

$ cat run
#!/bin/sh
docker build -t ub .
docker run -e DISPLAY=$DISPLAY -v /tmp/.X11-unix:/tmp/.X11-unix -e XDG_RUNTIME_DIR=$T -e WAYLAND_DISPLAY=$WAYLAND_DISPLAY -v $XDG_RUNTIME_DIR/$WAYLAND_DISPLAY:/tmp/$WAYLAND_DISPLAY -it --rm ub bash

    
	
    

    

    
	
    
		
	
    

    

    
		 			
    
		
	
    

    

    • 

	

  • 
	
    


    
	
    
					
			
    
	
    
		
			
											
					
		
			over 5 years ago
		
			
    

    

    
			
    interestingly, I'm having the same exact problem on ... mac os x (10.11) on my 2 machines.
    

    I start to wonder if the problem is not linked to our garmin account, and not to the binaries themselves.
    
	
    

    

    
	
    
		
	
    

    

    
		 			
    
		
	
    

    

    •