When I run jEdit, it displays the splash screen and then hangs with the following error messages on the console, this is reproducible every time:
Note that this problem only happens when I log in with KDE Plasma 5, if I log in using GNOME, jEdit works fine.
Command line to run jEdit: jedit -reuseview jEdit version: 5.3.0 Java version: Oracle JRE 1.8.0_92 Operating system: openSuSE Tumbleweed UI Interface: KDE Plasma 5
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: Exception in thread "AWT-EventQueue-0"
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: java.lang.IllegalArgumentException: Width (0) and height (0) must be non-zero
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at java.awt.image.ReplicateScaleFilter.<init>(ReplicateScaleFilter.java:102)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at java.awt.Image.getScaledInstance(Image.java:174)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at sun.awt.CustomCursor.<init>(CustomCursor.java:69)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at sun.awt.X11CustomCursor.<init>(X11CustomCursor.java:43)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at sun.awt.X11.XCustomCursor.<init>(XCustomCursor.java:42)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at sun.awt.X11.XToolkit.createCustomCursor(XToolkit.java:1140)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at org.gjt.sp.jedit.textarea.TextAreaPainter.addNotify(TextAreaPainter.java:181)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at java.awt.Container.addNotify(Container.java:2773)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at javax.swing.JComponent.addNotify(JComponent.java:4740)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at org.gjt.sp.jedit.textarea.TextArea.addNotify(TextArea.java:4682)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at java.awt.Container.addNotify(Container.java:2773)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at javax.swing.JComponent.addNotify(JComponent.java:4740)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at java.awt.Container.addNotify(Container.java:2773)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at javax.swing.JComponent.addNotify(JComponent.java:4740)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at java.awt.Container.addNotify(Container.java:2773)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at javax.swing.JComponent.addNotify(JComponent.java:4740)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at java.awt.Container.addNotify(Container.java:2773)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at javax.swing.JComponent.addNotify(JComponent.java:4740)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at java.awt.Container.addNotify(Container.java:2773)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at javax.swing.JComponent.addNotify(JComponent.java:4740)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at java.awt.Container.addNotify(Container.java:2773)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at javax.swing.JComponent.addNotify(JComponent.java:4740)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at java.awt.Container.addNotify(Container.java:2773)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at javax.swing.JComponent.addNotify(JComponent.java:4740)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at javax.swing.JRootPane.addNotify(JRootPane.java:757)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at java.awt.Container.addNotify(Container.java:2773)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at java.awt.Window.addNotify(Window.java:770)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at java.awt.Frame.addNotify(Frame.java:487)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at java.awt.Window.pack(Window.java:807)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at org.gjt.sp.jedit.jEdit.newView(jEdit.java:2580)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at org.gjt.sp.jedit.jEdit.newView(jEdit.java:2549)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at org.gjt.sp.jedit.jEdit.newView(jEdit.java:2525)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at org.gjt.sp.jedit.jEdit$8.run(jEdit.java:4190)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:756)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at java.awt.EventQueue.access$500(EventQueue.java:97)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at java.awt.EventQueue$3.run(EventQueue.java:709)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at java.awt.EventQueue$3.run(EventQueue.java:703)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at java.security.AccessController.doPrivileged(Native Method)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at java.awt.EventQueue.dispatchEvent(EventQueue.java:726)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
22:37:16 [AWT-EventQueue-0] [error] AWT-EventQueue-0: at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
Withe the latest openSuSE Tumbleweed update (as of 5-Jul-2016) using "zypper dup", jEdit is working again! Not sure which updated library fixed the problems with jEdit. Here are the list of updated libraries:
I am also using KDE5 Plasma with Java 1.8.0_91 (kubuntu) and do not see the same problem.
It looks like your recent upgrade installed replaced that version of Java with a newer one (Java 1.9) which might explain why things are different for you, but not why I am not seeing the same problem.
Can I close this as "works for me"?
Hi Alan, thanks for your message. As per my update, the problem has gone away after the latest Tumbleweed update on 5-Jul.
However, I would like to clarify that I did double-checked the version of Java that was used by jEdit and it was definitely Java 1.8.0_92, hence I am not convinced that the version of Java is the culprit here. If you look at the list of Tumbleweed updates that I did on 5-Jul which fixed the problem, there are no updates to Java.
Furthermore, over the past 3 weeks, I have encountered this issue twice after installing Tumbleweed updates (using "zypper dup"), and each time no Java JRE/JDK has been updated. Hence I think there is a library which has been updated that has caused the issue, but I have not been able to nail down exactly which library was the culprit.
Last edit: TL88 2016-07-07
Hi Alan,
Arrggg!!!, with the latest openSuSE Tumbleweed as of 11-Jul-2016, jEdit is crashing again with exactly the same error!!! Here are the updated packages, I am still not sure which updated package actually causes the problem:
Does it reproduce with "jedit -noplugins"?
what about "jedit -nosettings"?
Hi Alan, I tried both "jedit -noplugins" and "jedit -nosettings" and both still give the same errors.
The exception seems to be complaining about an X11CustomCursor.
Perhaps your KDE installation is trying to set a weird custom cursor?
What if you go to System Settings - Worksapce Theme - Cursor Theme
and select a different cursor theme? Does that make a difference?
I am using the "Breeze" theme.
I just checked and I am also using the "Breeze" theme :-) I tried "DMZ" theme and it still produces the same error.
Well, to eliminate all possibility of it something in your KDE settings, I would suggest creating a new user and seeing if you can reproduce it while logged as that user, from a clean KDE settings.
I just created a brand-new user, logged in to the new user's account and jEdit still gives the same error :-(
As per your suggestion, I have just installed jEdit 5.3.1 daily build "2016-07-10_19-57-37" and it still gives the same error.
Hi Alan,
Guess what? with the latest Tumbleweed update a of 13-Jul (using command "zypper dup"), jEdit is working again!!! it seems like everytime I do an update, jEdit breaks for a few days, then gets fixed with a new update! I still have not managed to isolate the package(s) that are causing problems, here are the list of packages I updated on 13-Jul:
Hi Alan,
This problem is driving me nuts! The latest Tumbleweed update as of 21-Jul-2016 has broken jEdit yet again. Here are the updated packages:
I still haven't seen this on Kubuntu. Does rebooting after you see this problem make any difference? If I have other ideas, I will post them.
I don't know anything about Tumbleweed, but the list you posted looks
like it's replacing a java 7 vm (1.7.0 openJDK) with something called
1.5.0 gcj-compat, which implies it's emulating a Java 5 (or 1.5) VM
instead. This was apparently done on purpose.
If I were investigating this, I'd start here... did you just downgrade
from a Java 7 virtual machine to a Java 5 VM? if so, why? Downgrading
from Java7 to Java5 would definitely affect how jedit performs (if at
all.)
java 1_7_0-openjdk-1.7.0.101-3.1.x86_64 --->
1_5_0-gcj-compat-1.5.0.0-137.5.x86_64
On Thu, Jul 21, 2016 at 2:26 PM, Alan Ezust ezust@users.sf.net wrote:
Related
Bugs: #3999
Hi Mikey,
With regards to version of Java, I actually manually set things so that jEdit always use a specific version of JRE (in this case it's java version "1.8.0_92"). Hence the Java updated packages should not have made any difference. I have also tested jEdit against a number of JRE (both from Oracle as well as OpenJDK) and the problem still persists, hence the culprit seems to be with other packages (probably some graphics library) that jEdit references. This is evidenced from some of the updates which broke jEdit without updating any of the JREs.
With regards to Tumbleweed, the main reason I am using it is because this is my development machine and using openSuSE, and I use a number of other development tools which at one time broke under the stable openSuSE realse and took a long time to get fixed, hence my decision to move to Tumbleweed.
With the exception of jEdit which regularly breaks-works-breaks with every update of Tumbleweed, on the whole, Tumbleweed has been very stable for me. So I think I would just have to cross my fingers and hope that someone finds the culprit and permanently fix the issue.
Kind regards.
Linux typically comes in one of 2 flavors, bleeding edge or LTS (long term
support). You appear to be on a bleeding edge upgrade plan. Which means
you can expect things to break regularly forever.
If you'd like to be seeing fewer things to deal with, figure out an LTS
distro that works for you. I recommend ubuntu 16.04 LTS. It seeks to
minimize updates that break everything, and only do true security updates.
It's support cycle is scheduled to end in 2022.
On Thu, Jul 21, 2016 at 4:04 PM, Michael H cmahte@gmail.com wrote:
Related
Bugs: #3999
Hi Alan,
Unfortunately no amount of reboot helps at all :-(
Dear all,
In my attempt to figure out what is causing the problem with jEdit on my system, I checked out the jEdit source code and proceeded to compile using Oracle's Java SDK 1.8.0_92. The version I built from the source code exhibited exactly the same symptom, and I think I have traced it to the following piece of code in the file TextAreaPainter.java around line 181 in the method
public void addNotify()
The code that is causing the problem is:
If I comment out the above line of code (I know I shouldn't be blindly commenting out codes, but ... in the interest of trying to figure out where things are breaking), jEdit runs find without any problem.
I hope this helps with your investigation. Given that jEdit works fine under GNOME and only causes problems under KDE, my guess is that every time I do an update, some KDE librarie(s) get updated which breaks jEdit.
Kind regards.