Jabref window off screen5/29/2023 ![]() ![]() The first debug message itself is printed in half a minute after the launch, though.Ģ5d40cd Update iso690-full-note-cs.csl ( #4480)ĥde3904 Update budownictwo-i-architektura-pl.Manufacturing Method for Radio-Frequency Cavity Resonators and Corresponding Resonator The stack trace is printed after the first debug message without any delay. : connect timed outĪt (Native Method) ~Īt .(RemoteClient.java:67) ~Īt .(RemoteClient.java:29) ~Ġ3:41:21.048 DEBUG - Initializing frameĠ3:41:23.327 DEBUG - Finished adding panelsįor the proxy being either enabled or disabled. : Connection refused: connectĪt 0(Native Method) ~Īt (Unknown Source) ~Īt (Unknown Source) ~Īt (Unknown Source) ~Īt (Unknown Source) ~Īt (Unknown Source) ~ġ9:50:02.607 DEBUG .server.RemoteListenerServerThread - Interrupting JabRef - Remote Listener Server on port 6050Īpparently something is wrong the remote server connection, but I am not familiar with JavaFX, so I am afraid I cannot locate the problem further by myself.Ġ3:41:20.697 DEBUG .JabRefLogger - Showing debug messagesĠ3:41:20.909 DEBUG .client.RemoteClient - Could not ping server at port 6050 JabRef 5.0-dev-snapshot-master-930fa4efbġ9:49:58.634 DEBUG .client.RemoteClient - Could not ping server at port 6050 The stack trace is now as follows:ĭ:\Program Files\JabRef>java -jar -v -n -debugġ9:49:57.625 DEBUG .JabRefLogger - Showing debug messages This time it crashed exited in a few seconds after printing the first debug messages. I was indeed using a corporate HTTP proxy server (I left its IP address undisclosed), so I tried disabling it in Windows settings and launching JabRef again. INFO: I/O exception () caught when processing request to -> PROXY**:3128->ġ9:30:40.282 DEBUG .server.RemoteListenerServerThread - Interrupting JabRef - Remote Listener Server on port 6050Īpparently, the application was having some problems with the proxy server. : Malformed reply from SOCKS serverĪt (Unknown Source) ~Īt (Unknown Source) ~Īt (Unknown Source) ~Īt .(Unknown Source) ~Īt .(RemoteClient.java:64) ~Īt .(RemoteClient.java:28) ~Īt (JabRefMain.java:138) ~Īt (JabRefMain.java:71) ~Īt .LauncherImpl.lambda$launchApplication1$161(LauncherImpl.java:863) ~Īt .PlatformImpl.lambda$runAndWait$174(PlatformImpl.java:326) ~Īt .PlatformImpl.lambda$null$172(PlatformImpl.java:295) ~Īt (Native Method) ~Īt .PlatformImpl.lambda$runLater$173(PlatformImpl.java:294) ~Īt .InvokeLaterDispatcher$n(InvokeLaterDispatcher.java:95) ~Īt .win.WinApplication._runLoop(Native Method) ~Īt .$null$147(WinApplication.java:177) ~Īt (Unknown Source) ħ:30:40 PM .RetryExec execute It works when I drag it back to the first screen.ġ9:30:35.257 DEBUG .client.RemoteClient - Could not ping server at port 6050 However, when I drag the window over to the other screen the JabRef window goes completely black and becomes inoperable. In whatever screen JabRef loads up in it works (once it loads). ![]() ![]() So I don't know if this is a bug in what I have or a setting that's incorrect but any help on this would be greatly appreciated.Īdditionally, I use a dual screen system. I would expect people would stop using the software if this was normal. I can't imagine everyone is experiencing this kind of performance. I'm not sure what I need to change or what the issue is. I went and made coffee, came back wrote an e-mail and then logged onto GitHub to post this request for help before JabRef came up. Just a few moments ago I loaded a database with just 12 entries. However, it takes JabRef as long as 10 minutes to open up a database file. I only have about 50 entries total so far. However, the program loads so slowly on my machine it's almost unusable. I used to have a Mac machine at work and used Bibdesk before. ![]()
0 Comments
Leave a Reply. |