LIBGDX ios simulator crash. LibGDX / Robovm compiles for 64bit instead of 32bit. What should I do? - libgdx

My libgdx app starts up on ios simulator and shows ios intro libgdx pic, then crashes.
I get:
[ERROR] Session could not be started: Error Domain=NSPOSIXErrorDomain Code=3 "Unable to run app in Simulator" UserInfo=0x7f853960ff60 {NSUnderlyingError=0x7f8539464ff0 "Failed to lookup the process ID of se.myapp.IOSLauncher after successful launch. Perhaps it crashed after launch.", NSLocalizedFailureReason=An error was encountered while running (Domain = NSPOSIXErrorDomain, Code = 3), NSLocalizedDescription=Unable to run app in Simulator}
Seems to be related to trying to run 64bit on iPhone 4s, where it is not supported. Does anyone know how to turn off 64bit for robovm in libgdx?
If I change the ios-sim command:
/Users/macuser/Documents/workspace/.metadata/.plugins/org.robovm.eclipse.ui/robovm-1.4.0/bin/ios-sim launch /Users/macuser/Documents/workspace/.metadata/.plugins/org.robovm.eclipse.ui/build/myapp-ios/myapp-ios/ios/x86_64/IOSLauncher.app --timeout 90 --unbuffered --devicetypeid "com.apple.CoreSimulator.SimDeviceType.iPhone-4s, 8.0" --stdout /var/folders/ml/zdhkbw3x0g9550pq9mgfrcsw0000gn/T/robovm-stdout-6250612031367207111.fifo --stderr /var/folders/ml/zdhkbw3x0g9550pq9mgfrcsw0000gn/T/robovm-stderr-5592986297298678222.fifo --setenv ROBOVM_LAUNCH_MODE=release --args -rvm:log=warn
To:
/Users/macuser/Documents/workspace/.metadata/.plugins/org.robovm.eclipse.ui/robovm-1.4.0/bin/ios-sim launch /Users/macuser/Documents/workspace/.metadata/.plugins/org.robovm.eclipse.ui/build/myapp-ios/myapp-ios/ios/x86/IOSLauncher.app --timeout 90 --unbuffered --devicetypeid "com.apple.CoreSimulator.SimDeviceType.iPhone-4s, 8.0" --stdout /var/folders/ml/zdhkbw3x0g9550pq9mgfrcsw0000gn/T/robovm-stdout-6250612031367207111.fifo --stderr /var/folders/ml/zdhkbw3x0g9550pq9mgfrcsw0000gn/T/robovm-stderr-5592986297298678222.fifo --setenv ROBOVM_LAUNCH_MODE=release --args -rvm:log=warn
It works with the old robovm. But for the new version it seems those directories aren't even built at all, so it fails.
Where should I specify the architecture? There is:
<arch>thumbv7</arch>
in robovm.xml but it doesn't seem to do anything?
Has this anything to do with the eclipse integration plugin (I am running from eclipse)?

OK I found out (after about 12 hours of digging)!
I looked in the wrong place all the time. The solution is (in eclipse) to go to Run Configurations / iOS Simulator App / Choose a device and select 32-bit (x86).

Related

Snap apps giving "error while loading shared libraries" and "cannot open shared object file: No such file or directory" when opened

Some snap apps (namely discord and telegram-desktop), stopped opening when I turned my laptop on this morning (Fedora 31 64bit), and when opened from terminal discord shows this:
~/ discord
WARNING: cgroup v2 is not fully supported yet, proceeding with partial confinement
/snap/discord/109/usr/share/discord/Discord: error while loading shared libraries: libX11.so.6: cannot open shared object file: No such file or directory
and telegram-desktop shows this:
~/ telegram-desktop
WARNING: cgroup v2 is not fully supported yet, proceeding with partial confinement
/snap/telegram-desktop/1561/bin/telegram-desktop: error while loading shared libraries: libQt5Widgets.so.5: cannot open shared object file: No such file or directory
both packages are installed, and I'm a bit stumped after searching threads and forums for most of the morning, nothing I tried worked, reinstalling them, trying different versions of the libraries and then the apps, installing 32bit versions, and on and on. Any help, prompts, ideas, or just general rambling about what the issue could be is much appreciated.
TLDR: Snap apps giving "error while loading shared libraries" and "cannot open shared object file: No such file or directory" when opened. Packages that are missing are installed correctly, so I'm stumped.
The warning is not your issue.
The real problem is simply you miss some dependencies in your snaps: for some reason snap is not installing all the requiered depdencies, while it should.
In an Ubuntu I have telegram-desktop and it works fine and I did this check:
snap list
to list the actual snaps.
And next I did check all the interdependencies by looking at the connections with:
snap connections telegram-desktop
this on my Utbuntu machine yields:
Interface Plug Slot Notes
alsa telegram-desktop:alsa - -
audio-playback telegram-desktop:audio-playback :audio-playback -
audio-record telegram-desktop:audio-record - -
content[gtk-3-themes] telegram-desktop:gtk-3-themes gtk-common-themes:gtk-3-themes -
content[icon-themes] telegram-desktop:icon-themes gtk-common-themes:icon-themes -
content[kde-frameworks-5-core18-all] telegram-desktop:kde-frameworks-5-plug kde-frameworks-5-core18:kde-frameworks-5-core18-slot -
content[sound-themes] telegram-desktop:sound-themes gtk-common-themes:sound-themes -
desktop telegram-desktop:desktop :desktop -
desktop-legacy telegram-desktop:desktop-legacy :desktop-legacy -
gsettings telegram-desktop:gsettings :gsettings -
home telegram-desktop:home :home -
network telegram-desktop:network :network -
network-manager telegram-desktop:network-manager - -
opengl telegram-desktop:opengl :opengl -
pulseaudio telegram-desktop:pulseaudio :pulseaudio -
removable-media telegram-desktop:removable-media - -
unity7 telegram-desktop:unity7 :unity7 -
wayland telegram-desktop:wayland :wayland -
x11 telegram-desktop:x11 :x11 -
next I have found that the library libQt5Widgets.so.5 you are missing is provided by kde-frameworks-5-core18
sudo find /snap -name libQt5Widgets.so
/snap/kde-frameworks-5-core18/32/usr/lib/x86_64-linux-gnu/libQt5Widgets.so
I don't know if on fedora you could use:
snap install kde-frameworks-5-core18
to fix your missing dependency.
On the other side on Fedora and similar distros you could try to use flatpak instaead of snap: flatpak comes as default app-package manager for the Fedora family.
First you need to add flathub as a flatpak remote repository:
sudo flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrepo
next you can search:
flatpak search discord
flatpak search telegram
and next install the apps:
sudo flatpak install com.discordapp.Discord
sudo flatpak install org.telegram.desktop
I tested this on a CentOS virtual machine (I dont' have a fedora ready to test, but CentOS is close enough) and I got them both correctly working.
Hey I'm not an expert at all, but I've been facing the same issue, and it seems that doing a "snap refresh" fixed the problem on my ubuntu. I'm not sure if it's relevant or not, but it might help

Why won't DraftSight run on Fedora 26 with Intel graphics?

DraftSight 2017SP1 Linux (beta) worked on Fedora 24. It fails after upgrading to Fedora 26. Running it from the command line so you can see the low-level errors,
/opt/dassault-systemes/DraftSight/Linux/DraftSight
Qt: Session management error: None of the authentication protocols specified are supported
Could not parse stylesheet of object 0x238a050
Could not parse stylesheet of object 0x238a050
In the graphics environment you see the usual start screens, then error pop-ups which offer to report the error and then close the application when clicked. One says that error-reporting is not available.
Similarly with 2017SP3 and 2018SP0. Fedora updates are current as of today.
This system is an Intel core i3. lspci reports "Intel Corp Xeon E3-1200 v3/4th Gen core processor Integrated Graphics Controller (rev 06)"
2018SP0 does work once an Nvidia GT710 card and the nvidia driver module are installed. It does not work with the nouveau driver module and the same card.
Does anybody have any insight as to the cause? A regression in Fedora, or a latent bug in DraftSight, or anything else?
Knowing whether it works with Fedora 26 and AMD graphics might be very helpful.
Edit March 2018
Doesn't work but differently on a system with AMD R5 230. No "Could not parse" errors, not anything else on the terminal window, but Draftsight starts up with the display all wrong and then locks up. Clicking the "X" gets to "the program is not responding".
Also worth noting that this isn't a Wayland issue. Systems are running Cinnamon and lightdm, so it's good old X.
Also a work-around, if performance is unimportant. (And it probably isn't, with Gen 4 Intel Graphics). Run it as a "remote" application on localhost, on a system with Intel graphics.
$ ssh -X 127.0.0.1
password:
Last login: Wed Mar ...
-bash-4.4$ /opt/dassault-systemes/DraftSight/Linux/DraftSight
(success)
Further update Fedora 29, DraftSight 2018SP3
New wrinkles for Nvidia, Cinnamon as above
Needs invocation
LD_PRELOAD=/usr/lib64/libfreetype.so.6 /opt/dassault-systemes/DraftSight/Linux/DraftSight
otherwise fails with /lib64/libfontconfig.so.1 lookup error FT_DOne_MM_Var
Also kernel 4.20 plus NVidia 390.87 fails to build. There's a patched NVidia installer that does work at if_not_false_then_true site.
Also does not install a .desktop file into /usr/share/applications
I had similar problems when I updated Fedora 24 to 25. The parse stylesheet messages still show up but I can run draftsight from an Xorg session, (not Wayland), using the nouveau drivers but only under root privileges using sudo .
You might try the following script:
sudo DISPLAY=$DISPLAY vblank_mode=1 /opt/dassault-systemes/DraftSight/Linux/DraftSight
I can only get DraftSight to run as root under Fedora 27, 4.18.16-100.fc27.x86_64. I have installed a VM with Ubuntu, and it runs fine, without elevated privileges.

IDEA Javascript Chrome Remote Debugging

I try to get the JetBrains IDE Support 2.0.9 running with my IDEA 2017.1.4.
IDEA says that it waits for connection from the Support Extension on IDE port 63342.
The problem I found is that the Chrome Plugin gets an 404 error when it tries to create the WebSocket Connection
Ready to load system latest for IntelliJ IDEA 2017.1.4 (127.0.0.1:63342)
logging.kt:43 System latest loaded for IntelliJ IDEA 2017.1.4 (127.0.0.1:63342)
socket.kt:50 WebSocket connection to 'ws://127.0.0.1:63342/jsonRpc?v=2.0.9&f=Mozilla%2F5.0%20(Windows%20NT%206.1%3B%20Win64%3B%20x64)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F59.0.3071.115%20Safari%2F537.36' failed: Error during WebSocket handshake: Unexpected response code: 404
value # socket.kt:50
value # socket.kt:69
value # platform.kt:32
value # chrome.kt:23
$f9 # console.kt:57
$fb # bootstrap.kt:157
$fc # bootstrap.kt:174
logging.kt:51 onerror [object Event]
value # logging.kt:51
$f4 # socket.kt:92
I try to find some solution via Google but the keyword "jsonRpc" polluted the results with no connections to IDEA that helped.
Further informations:
Network has no access to Internet
Chrome Version 59.0.3071.115 64-Bit
OS: Win 7 64bit
IDEA 2017.1.4
Plugin 2.0.9
Installed IDEA Plugins (External Ones)
Atlassian Connector for IntelliJ IDE (Version 3.0.16,SVN:1504201227)
CodeReview for IntelliJ IDEA (Version 0.5.4)
Grep Console (Version 5.9.141.000)
IDETalk (Version 145.258.11)
Lombok Plugin (Version 0.14.16)
SonarLint (Version 2.3.2)
String Manipulatio (Version 4.2.132.445)
Maven Helper (Version 3.1.138.1503)
I know that some could be very old but we don't have Internet Access at our Workstation to se updates or even update very good
PS: is there some kind of documentation what all the WebInterface URLs in IDEA are/how the Interface is constructed?

Visual Studio 2012 / WP8 SDK: "Connection to Windows Phone Device or Emulator Failed"

I'm opening the default project for Windows Phone 8 using VS 2012 Professional and WP8 SDK, and am trying to configure the Windows Phone 8 WVGA 512 (default) emulator.
Using build and deploy both work. Build and deploy are both checked in the build settings for all build types. The output gives me this:
Deploy started: Project: ABCD, Configuration: Debug x86
Deploying C:\Users\Guy\My Projects\ABCD\ABCD\bin\WindowsPhone\x86\Debug\ABCD_Debug_x86.xap...
Connecting to Emulator WVGA 512MB...
Installing the application...
Deployment of C:\Users\Guy\My Projects\ABCD\ABCD\bin\WindowsPhone\x86\Debug\ABCD_Debug_x86.xap succeeded.
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Deploy: 1 succeeded, 0 failed, 0 skipped ==========
However if I try to open the Simulation Dashboard to change any settings (Lock Screen -> Unlocked or "Enable Network Simulation", Visual Studio returns the error:
Connection to Windows Phone device or emulator failed.
How do I fix this issue? I have no headway on this problem because there's nothing from Google or stackoverflow, and I've tried a ton of things related to this problem (mainly the fixes for the infamous Could Not Debug Application error.)
Thanks for the help.
I have very similar problem, but in my case the simulation does not work on actual device (it used to, but now suddenly it doesn't). It does work with emulator. Deploying and debugging works fine on both.
This would suggest that it might be more general problem. Not tied to target device type in particular.

MonoDroid:INSTALL_FAILED_OLDER_SDK

Using MonoDroid 4.0.6 and MonoDevelop, any attempt to run in an emulator fails with this error listed below:
The minSdkVersion matches the emulator's SDK version. All AVDs were created by the MonoDroid isntaller.
Detecting package list location
Getting package list from device
Installing shared runtime package on device
1849 KB/s (25866362 bytes in 13.657s)
pkg: /data/local/tmp/Mono.Android.DebugRuntime-debug.apk
Success
Installing the platform framework
1565 KB/s (16530851 bytes in 10.310s)
pkg: /data/local/tmp/Mono.Android.Platform.apk
Failure [INSTALL_FAILED_OLDER_SDK]
Failed to install the platform framework
I solved this in 2 ways.
1) In the manifest the minSdkVersion should match or be lower than the emulator
2) (what tripped me up) The Mono DLLs References of the project should be set to the Android version too.
Both are needed. I come from a Java Android background so never thought to change anything but the manifest.