Re: Bug#814901: jabref: at start jabref hangs with the error message "No appenders could be found for logger ..."
Dear Gregor,
thanks a lot for your help. I now have a workaround, see below. It was great to work with you :-)
On Wed, Feb 17, 2016 at 12:11:47AM +0100, gregor herrmann wrote:
[...]
====================================================================================================
> > > > prompt> DEBUG_WRAPPER=1 JAVA_HOME=/usr/lib/jvm/java-8-openjdk-amd64/ jabref
> > > >
> > > > Xlib: extension "XInputExtension" missing on display ":0".
> > > Ha! Here's an extra line, and that's the difference to my output.
> > > Now we just need to find out what's missing / different on your
> > > system, so that java can't connect to the X server.
> > > (But then, your test with OpenJDK 7 should work?)
> > I have tried this particular test again five times and did not get the
> > Xlib message again.
>
> Hm. Maybe because there was still a java process lingering around?
I tried this test a couple of times more:
1) I get the error message
java: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
apart from the usual other erro messages and jabref crashed.
2) dito
3) It actually started and worked.
4) It hung.
Then I killed all java processes: $ killall -9 java
5) It actually started and worked.
6) It actually started and worked.
7) It hung.
Then I killed all java processes: $ killall -9 java
8) It actually started and worked.
9) It actually started and worked.
10) It hung.
Then I killed all java processes: $ killall -9 java
Ok, so much statistics for now. I am actually surprised that it
worked a couple of time. So far it normally did not work at all.
====================================================================================================
> > > Do other java programs work for you?
> > Hm, I don't know. How would I find out? What are common other java programs?
>
> Depends on what you like :)
> freemind, josm, tuxguitar are some that I use.
>
> `apt-cache rdepends default-jre' might give you some ideas.
'libreoffice' runs without problems.
====================================================================================================
> > Ok, I looked a bit on the internet and wanted to write a little mini
> > program in java. I figured I need the javac compiler. It is not
> > installed on my computer, and it was not in the Debian unstable
> > repository under that name either.
>
> "My" javac is /usr/bin/javac -> /etc/alternatives/javac -> /usr/lib/jvm/java-8-openjdk-amd64/bin/javac
> (from the openjdk-8-jdk package). But I guess installing another
> package with software written in Java is easier.
Ok, I found it. Now, it is all like that for my computer too.
However, I did not bother writing a little java programm anymore,
because 'libreoffice' runs ok and shows that java is ok in principle.
====================================================================================================
[...]
> > I hope all that gives you a bit more information to work with.
>
> It's certainly not a lack of information from your side that leaves
> me a bit clueless :) Currently I think that the problem lies not with
> JabRef but I have no idea what's happening between java and X on your
> machine. - My hopes still lie in the Java team and their expertise :)
====================================================================================================
> Or this: After some searching I found https://bugs.debian.org/802701
> which sounds quite similar. And even mentions JabRef ... with the
> upstream ticket at https://github.com/JabRef/jabref/issues/393 . And
> the Ubuntu bug at
> https://bugs.launchpad.net/ubuntu/+source/jabref/+bug/1520294
>
> The GitHub issue contains a workaround (changing the look&feel),
> maybe this works for you too? (Same info in the Launchpad bug.)
Ok, I commented out the line
assistive_technologies=org.GNOME.Accessibility.AtkWrapper
in file
/etc/java-8-openjdk/accessibility.properties
and then jabref started 10 times in a row with the usual error messages
$ jabref
log4j:WARN No appenders could be found for logger (org.java.plugin.ObjectFactory).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
Found 2 plugin(s):
- net.sf.jabref.export.misq (jar:file:/usr/share/jabref/JabRef-2.10.jar!/plugins/net.sf.jabref.export.misq/plugin.xml)
- net.sf.jabref.core (jar:file:/usr/share/jabref/JabRef-2.10.jar!/plugins/net.sf.jabref.core/plugin.xml)
but without any problems. Then I uncommented the line again and
jabref started to not work reliably again. So that is a workaround
for me.
----------------------------------------------------------------------------------------------------
Then I tried the other solution. I went to Options -> Preferences ->
Advanced and checked the tickbox 'Use other look and feel \\ Class
name: com.jgoodies.plaf.plastic.Plastic3DLookAndFeel'. That
workaround also worked, jabref started and apparently runs fine but
with some more error messages:
$ jabref
log4j:WARN No appenders could be found for logger (org.java.plugin.ObjectFactory).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
Found 2 plugin(s):
- net.sf.jabref.export.misq (jar:file:/usr/share/jabref/JabRef-2.10.jar!/plugins/net.sf.jabref.export.misq/plugin.xml)
- net.sf.jabref.core (jar:file:/usr/share/jabref/JabRef-2.10.jar!/plugins/net.sf.jabref.core/plugin.xml)
java.lang.ClassNotFoundException: com.jgoodies.plaf.plastic.Plastic3DLookAndFeel
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:348)
at javax.swing.SwingUtilities.loadSystemClass(SwingUtilities.java:1874)
at javax.swing.UIManager.setLookAndFeel(UIManager.java:582)
at net.sf.jabref.JabRef.setLookAndFeel(JabRef.java:669)
at net.sf.jabref.JabRef.openWindow(JabRef.java:726)
at net.sf.jabref.JabRef.<init>(JabRef.java:201)
at net.sf.jabref.JabRef.main(JabRef.java:84)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at net.sf.jabref.JabRefMain.main(Unknown Source)
Removing the tick mark again leads to the old unreliable behavior.
====================================================================================================
Ok, that solves the problem for me. Thanks a lot for your help.
Best wishes,
Josef.
Reply to: