Electron app run with --no-sandbox generates warnings and errors - visual-studio-code

I am trying to write my first electron app and deploy it to a system that requires me to run with the --no-sandbox option (I don't have root/sudo permissions on the system). While I am able to run with the --no-sandbox option, I see the following messages when I try to open a dialog to pick a file.
I can run vscode on the same system, and it also needs the --no-sandbox option, but I have not seen any of these messages while using vscode, so I assume it has something to do with the way may app is setup, or they way I am opening the dialog.
Error creating proxy: Unknown or unsupported transport “disabled” for address “disabled:” (g-io-error-quark, 13)
Error creating proxy: Unknown or unsupported transport “disabled” for address “disabled:” (g-io-error-quark, 13)
Error creating proxy: Unknown or unsupported transport “disabled” for address “disabled:” (g-io-error-quark, 13)
Error creating proxy: Unknown or unsupported transport “disabled” for address “disabled:” (g-io-error-quark, 13)
Error creating proxy: Unknown or unsupported transport “disabled” for address “disabled:” (g-io-error-quark, 13)
Gtk-Message: 11:03:02.463: GtkDialog mapped without a transient parent. This is discouraged.
(my-first-electron:158778): dconf-WARNING **: 11:03:02.658: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”
(my-first-electron:158778): dconf-WARNING **: 11:03:02.705: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”
(my-first-electron:158778): dconf-WARNING **: 11:03:02.714: failed to commit changes to dconf: Unknown or unsupported transport “disabled” for address “disabled:”
Here is an example of how I am opening the dialog.
import { remote } from 'electron'
then later
buttonClicked = () => {
console.log(this)
ipcRenderer.send('do-something')
const dialog = remote.dialog
console.log(dialog.showOpenDialogSync(remote.getCurrentWindow(), {
properties: ['openFile']
}))
}

Related

(Unreal Engine 4.27.2) Dedicated Server not working with Steam API

After I updated the ini file to activate the Steam Subsystem plugin, the dedicated server is unable to host the map level, and closes the connection and then creates an infinite loop of failed attempts. But on the client it works perfectly, I can even open the steam panel inside the standalone game.
Dedicated Server Log:
[2022.12.04-01.11.01:940][ 2]LogModuleManager: Warning: ModuleManager: Unable to load module 'SocketsSTEAM' - 0 instances of that module name found.
[2022.12.04-01.11.01:940][ 2]LogSockets: Warning: Unable to load SocketSubsystem module STEAM
[2022.12.04-01.11.01:940][ 2]LogNet: ReplicationDriverClass is null! Not using ReplicationDriver.
[2022.12.04-01.11.01:940][ 2]LogNetCore: DDoS detection status: detection enabled: 0 analytics enabled: 0
[2022.12.04-01.11.01:941][ 2]LogSockets: Warning: SteamSockets: Cannot get information on an invalid socket handle, returning null
[2022.12.04-01.11.01:941][ 2]LogNet: Warning: Could not create socket for bind address ::, got error SteamSockets: setsockopt SO_BROADCAST failed (0)
[2022.12.04-01.11.01:941][ 2]LogNet: Warning: Encountered an error while creating sockets for the bind addresses.
[2022.12.04-01.11.01:941][ 2]LogNet: Warning: Failed to init net driver ListenURL: /Game/ThirdPersonBP/Maps/ThirdPersonExampleMap500?closed:
[2022.12.04-01.11.01:941][ 2]LogNet: Error: UEngine::BroadcastNetworkFailure: FailureType = NetDriverListenFailure, ErrorString = , Driver = GameNetDriver IpNetDriver_3
[2022.12.04-01.11.01:941][ 2]LogNet: Server_Error: Net Driver Listen Failure
[2022.12.04-01.11.01:941][ 2]LogWorld: Failed to listen:
[2022.12.04-01.11.01:941][ 2]LogNet: DestroyNamedNetDriver IpNetDriver_3 [GameNetDriver]
[2022.12.04-01.11.01:941][ 2]LogNet: Error: LoadMap: failed to Listen(/Game/ThirdPersonBP/Maps/ThirdPersonExampleMap500?closed)
[2022.12.04-01.11.01:942][ 2]LogSkeletalMesh: USkeletalMeshComponent::InitArticulated : Could not find root physics body: '/Game/ThirdPersonBP/Maps/ThirdPersonExampleMap500.ThirdPersonExampleMap500:PersistentLevel.SK_Mannequin_Arms_2.SkeletalMeshComponent0'
start bat:
"C:\Program Files\Epic Games\UE_4.27\Engine\Binaries\Win64\UE4Editor.exe" "D:\MyProject\MyProject.uproject" ThirdPersonExampleMap500 -server -steam -log
exit
Even passing the "-nosteam" parameter, the dedicated server remains incommunicable as long as Steam is open.
STEAM SDK V1.51
UE4_Wiki
I've followed all these steps beyond activating the plugin to install the Steam SDK, but something seems to be missing to make it work in multiplayer.

eclipse can not debug, but run is ok

suddenly, my eclipse does not work in debug model. when click debug button, i got these error messages, and debug failed.
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: transport error 202: gethostbyname: unknown host
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [debugInit.c:750]
could anyone help, or gives some help.
i have found solution. "unknown host ERROR" in error message is the key.
just because i used switchhost app to change my mac's hosts file. And line of "127.0.0.1 localhost" had been removed.
so, what need to do to solve this problem is adding "127.0.0.1 localhost" to mac's hosts file.
127.0.0.1 localhost
Add the above entry in /etc/hosts file and you should be good.

IBM Worklight : Transport error 202: bind failed: Address already in use

I have an eclipse workspace with an IBM worklight project running and I want to run another instance of eclipse with another worklight project on different ports. I have modified the server.xml which has the Http ports as follows:
<httpEndpoint host="*" httpPort="10090" httpsPort="10453" id="defaultHttpEndpoint">
<tcpOptions soReuseAddr="true"/>
and also the admin port as follows:
<jndiEntry jndiName="ibm.worklight.admin.jmx.port" value="10453"/>
But when I start the second server, I get the below error:
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:750]
Which port am I missing to change and where do I change that in eclipse?
You may also need to change the debug port for each server.
See here under "Java remote debug...": http://www.ibm.com/support/knowledgecenter/SSHS8R_6.3.0/com.ibm.worklight.dev.doc/devref/c_dev_test_server_and_console.html
You need to open the jvm.options file in Eclipse > Servers > development server. Then edit the port number "10777" to a different one.

Eclipse JDWP error when trying to debug

I get the following error when trying to debug a local java application in eclipse.
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: transport error 202: connect failed: Connection refused
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
I read that it might be caused by something using the same port as the one eclipse wants to use for debugging, but how do I determine the port number. I couldn't find anything in the error log or the preferences.
Any ideas?
I ran into the same issue and it turns out I was specifying server=n parameter in the jdwp debug string. It turns out that if we specify server=n in the debug connection string, it'll attempt to attach/connect to that port instead of listening on it. Switching to server=y solved my issue. It's documented in the
official jpda documentation.
Maybe it's your antivirus. Are you using avast if so look at this https://feedback.avast.com/responses/eclipse-debug-functionality-not-working-after-upgrade-to-avast-2014
The solution is upgrading to the latest version of avast (http://forum.avast.com/index.php?topic=139606.0)
Please ensure that, the below entry is there in /etc/hosts file (for mac/linux)
127.0.0.1 localhost
Previously I unknowingly commented out this line, so it worked for me after reverting back. Hope this helps.

Play Framework debugging problems with Eclipse

I am working through the YABE tutorial and would like to throw the debugger on to see why the captcha isnt working correctly.
I am using Eclipse and Play 1.2.
Here is the error im getting when trying to run as:
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
Ideas?
Its all there in the message itself!, "Address already in use", ie. the port numbers (8000 or 9000) may be already used/reserved by some other app or you may have a stale Play instance started earlier.
Try changing the JPDA port that Play listens on. It looks like the default port, 8000, is already in use by something else.
You can do this by modifying the "jpda.port" property in "conf/application.conf". Be sure to also modify the Eclipse JPDA launch file (the one that was generated by the play eclipsify command) if that is what you are using to start the debugging session.