I'm using Ubuntu 22.04 and Eclipse IDE (09.22). Every time I show the tooltip (for javadocs or so) it's just empty. I've seen people talking about similar problem and one of these solutions is to install gnome-color-chooser but I'm worried color-chooser is not right for jammy (Ubuntu 22.04) : I tried to install the deb but there are too many dependencies to be installed (who need dependencies on their own). Does anyone have the same issue? or know how to solve it? thank you.
This issue almost made eclipse unusable for me.
In my case i am on X11 not Wayland, which i think is relevant. Anyway, set this variable before starting eclipse e.g.
WEBKIT_DISABLE_COMPOSITING_MODE=1 ./eclipse
Another issue this fixes is the welcome screen (Help -> Welcome) was blank.
When running eclipse from the console, every time i hovered over something, i would get an empty dialog, and this error in the console
WebKitWebProcess:1211824): Gdk-ERROR **: 17:31:08.234: The program 'WebKitWebProcess' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 178 error_code 2 request_code 151 (GLX) minor_code 34)
Related
I hope I post that question in correct place.
Since a few days I have a problem with Netbeans 8.2 (fresh installation)
Java 1.8.0_162.
Operating system: Windows 7/10 . The problem occurs on three different computers.
Steps to reproduce:
Open any file in Netbeans IDE (the editing caret is blinking),
Deactivate NB window (click on another window, notepad, browser
doesn't matter),
Back to NB again by clicking directly on opened
document (caret is blinking again),
Now you should notice CPU usage. To make it lower click on "Output" panel.
SOLUTION FOR THIS ISSUE
Found a solution for this problem. I installed older vesion of JDK 8u144 and set netbeans_jdkhome variable in <netbeans install directory>/etc/netbeans.conf, so it points to that version. Now everything works correctly, no CPU usage at idle.
As ImtiazeA noticed Netbeans works fine without this issue with JDK 8u172 installed (thanks for your answer). They must have fixed it :) So just dont use 8u152 and 8u162 and it will be good.
EDIT
Deactivated all installed plugins and still the same problem.
Installed Netbeans 8.0 - didn't help...
Downloaded the Dev version of netbeans and got the same issue. Now using IDE Profiler and got this message:
java.awt.IllegalComponentStateException: component must be showing on the screen to determine its location
at java.awt.Component.getLocationOnScreen_NoTreeLock(Component.java:2062)
at java.awt.Component.getLocationOnScreen(Component.java:2036)
at javax.swing.text.JTextComponent$InputMethodRequestsHandler.getTextLocation(JTextComponent.java:4643)
at sun.awt.im.InputMethodContext.getTextLocation(InputMethodContext.java:278)
at sun.awt.windows.WInputMethod$1.run(WInputMethod.java:588)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:758)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.awt.EventQueue$3.run(EventQueue.java:703)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:90)
at java.awt.EventQueue$4.run(EventQueue.java:733)
at java.awt.EventQueue$4.run(EventQueue.java:731)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:80)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:730)
at org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:159)
[catch] at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:205)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
Someone somewhere said that it's a problem with Tasks pane somewhere in background doing something. Turn it on and then off in Menu/Window/Tasks, and your computer will start breathing again for a while.
For me, Ctrl-Shift-6, Ctrl-W is a new involuntary action.
If they don't fix that in the next seven years, I'm switching to another IDE. That's the maximum I'm giving them.
I have the same problem. What seems to be happening is Netbeans is constantly checking the selected code window for compile and syntax errors, even when Netbeans is minimized. My solution is to not delete the Start Page tab that appears when you start Netbeans. Then before minimizing, select this tab and the CPU usage drops to 0.
For those who did not notice the solution Krzysztof mentioned in the question, I installed another JDK and it fixed my issue. I just installed the latest JDK 8u172 (instead of 8u144) and it worked for me.
Another possible reason: Large amount of data in clipboard.
My NetBeans was consuming more than 70 % of CPU. I followed advice from a comment above and opened IDE Log from View menu. There I got the following error:
java.lang.OutOfMemoryError: OutOfMemoryError at
sun.awt.windows.WClipboard.getClipboardData(Native Method)
Switching to another window, selecting few characters and Ctrl-C resolved the issue.
Just to mention that I work on Intel i5 and Windows10-64bit.
I tried literally everything. After one of those system updates, my Netbeans 8.2 influenced a system to be very slow, almost to the point of unresponsiveness. During NB startup or build, system is practically unresponsive.
So, all possible tweaks both Netbeans and Java, couldn't solve a problem.
It seems that Windows update itself trigger off a problem to happen, as updates did changes on low system level, I suppose.
I decided to lower a Netbeans PID, by creating new shortcut like this :
cmd.exe /c start "Netbeans 8.2 LowPrio" /Low "C:\Program Files\NetBeans 8.2\bin\netbeans64.exe"
For now I can work without disruption, and it's far more smoother, than before.
https://gist.github.com/dobrivoje/2af15a84dbd3179938e0fbf288d512b4
I found a solution for this. Atleast that worked for me. I was having same issue.
My solution is to remove your netbeans inner folder from AppData and try restarting netbeans. It works perfect now. My path is C:\Users\awais\AppData\Roaming\NetBeans
Remove 8.1 or 8.2 folder and restart netbeans.
I had the same problem suddenly, but the problem was Windows 10 Dark mode, after switch back to Light color scheme on windows 10 it was normal as before.
TIP: You can profile the netbeans and check which consume more resources.
Canceled the unpacking index task that seemed to be stuck. (bottom right of screen)
I'm trying to install Netbeans 8.2 Java EE, but whenever I start the installer it quits after configuring it. I am trying to install it on Windows 10 64-bit.
This is not going to make sense at all, but do you happen to have the "God Mode" item on your desktop? Take it off the desktop (delete it, move it somewhere else, whatever). I have no idea why, but it worked for me: I found the solution in this bug report - https://netbeans.org/bugzilla/show_bug.cgi?id=269988
I do hope this helps you, too.
This is an Java issue, which was came up due to recent windows 10 update, that started treated differently for GodMode folder/shortcut.
This has been already fixed - https://bugs.openjdk.java.net/browse/JDK-8179014
You can verify the fix in early access build of JDK8 update 152, which is available here
We have verified the issue only with GodMode, do let us k now if there are any other scenarios that can cause such similar issues.
I'm adding this because: I had a different issue which I was unable to find addressed anywhere, this question appears near the top of a web search for "NetBeans 8.2 ee won't install on Windows 10", and someone else may have the problem I had.
My NetBeans install was almost immediately crashing with the following error:
An unexpected exception happened in thread main
Exception: javax.xml.parsers.FactoryConfigurationError: Provider for
class javax.xml.parsers.DocumentBuilderFactory cannot be created
In my Windows 10 System Properties -> Environment Variables -> System Variables, I had a previously created _JAVA_OPTIONS variable values using -Xbootclasspath/a to append some jar files to the end of the bootstrap class path. These files are used with some work I'm doing with the Oracle BI Publisher plug-in for Microsoft Word.
As soon as I renamed the _JAVA_OPTIONS variable to something else, my NetBeans installation started normally and completed with no issues.
After NetBeans installation, I reset the name of this variable back to _JAVA_OPTIONS, and discovered that the values I have for this System Variable cause NetBeans launch to crash. (Which does not completely make sense to me since I am only appending these files/classes to the class path, and not overwriting.)
Regardless, I'll have to go back to the drawing board for my work with the BI Publisher plug-in; but at least I can use NetBeans now!
Uninstall any Java installations along with NetBeans, and install Java with NetBeans (bundle) from the Oracle website.
I had the same issue, and then installed the bundle, works perfectly.
It's been happening lately for some unknown reason.I have the latest version of Eclipse ADT (25 Sept 2014) and it just shuts off while I'm working. Any ideas?
Start Eclipse from a terminal to see the standard output. Chances are that the Java VM runs into a problem because of SWT which can crash the VM. Note: If you're using Windows, you may have to use java.exe instead of javaw.exe to get output.
Also look into the Error Log. Eclipse has a view for that or look into the file .../workspace/.metadata/.log The file might contain an error message.
If you find an error in either the console or the error log, let us know and we might be able to help.
The issue could also be because of the JVM that was chosen for the project.
I have an issue with nodeclipse: I am unable to run even the simplest demo app (simple require http). When I try to run my "app.js" as a node application, I am just getting:
<terminated, exit value: -1073741819>Node.js Process
When I try to run from the command prompt node app.js, everything goes fine. Did I forget anything important ?
Thanks in advance for your help.
Here is some additionnal informations:
Env config: Win 8 64 bits + Eclipse Kepler 64 bits (JRE 6.0.390.4)
Enide from Eclipse marketplace (based on Nodeclipse 0.9.05)
NodeJs v 0.10.24
While this problem arise from time to time, the exact cause is not yet known. More feedback is needed.
(Once the problem goes away there is no way to reproduce healing; so the only way is to collect data in what environment, and how was solved)
Check Nodeclipse Online Help - Run page
There are 2 similar issues raised before.
#72, #176 was solved via Java upgrade to 1.7
#107 was solved via running node --debug-brk app.js from console first.
I have started to try to use StatET and Texlipse with a view to producing SWEAVE reports. When starting the R console in the StatET plug-in for Eclipse (OS X 10.6.4), I get the message:
[INFO] The R package 'rj' is not available, R-StatET tools cannot be initialized.
Information on http://www.walware.de/goto/statet states:
"The package only works in the default R Console (RJ) in StatET. Therefore you have to install and update it using the command line":
R CMD INSTALL --no-test-load rj_*.tar.gz
What does this mean exactly?
In Eclipse under "Install new Software" and the site
WalWare - http://download.walware.de/eclipse-3.6
it states that
RJ Core Library 0.5.0.b201008271600sw
is already installed.
Any helpful guidance gratefully received.
[rant] I also lack the reputation to put my response where it belongs. And there's no button there indicating this. Just a big screen full of nowhere desired to click upon. Negative discoverability sucks. It sucks in Eclipse and it sucks here, too. [/rant]
I'm finding rj frustrating under Ubuntu. On my system, with each major Ubuntu upgrade with a new version of R, I have to go through this procedure over again.
One time I tried to use a tilde (~) character in a path name within some Eclipse configuration field. This failed silently.
My current configuration is as follows. In my ~/.Renviron file:
R_LIBS_USER=~/etc/R/amd64/2.11
Once rJava works, there is an rJava directory here. Just so I don't drive myself insane, in ~/etc/R/README I put a note that my current R configuration is controlled by ~/.Renviron
Somehow at one point I ended up with permission problems where
R CMD javareconf
was failing. Once in frustration I foolishly ran this under sudo to work around this problem, and ended up with permission problems on the generated files. Stupid! The correct fix was to make all the files in /etc/R world readable. Maybe javareconf is only important if you mess with your default Java. Previously, I was running the Sun's JRE. Since 10.10 I'm running icedtea6 and it seems to be working OK. One time it was just the thing to make my configuration work again.
Once I have the right Java binding, from command line R:
install.packages("rJava")
I've had file permission problems running this in the past. I think it was fixed by making all files in /etc/R world readable.
The following is a useful diagnostic to see if this worked, from within any R console:
> system.file("jri",package="rJava")
[1] "/home/allan/etc/R/amd64/2.11/rJava/jri"
If it doesn't look right under Eclipse, there is also some startup debugging available, though it took forever before I noticed this in the docs at StatET.
I created an R Console run configuration for R 2.11 debug In the JRE tab add -Dde.walware.rj.verbose=true. In the Common tab, click Allocate additional Error Log Consoles.
The main configuration options are as follows. Main tab, Launch Type: RJ. R_Config tab, you need to select a Configured R Installation, or create/edit one if you don't have one that works. Mine is Name=R, Location=/usr/lib64/R In the Environment tab I have R_LIBS_USER=/home/USER/etc/R/amd64/2.11 according to how I set things up above. Do not use the tilde (~) character here!
If you end up mucking about with this problem as much as I did, you end up killing a lot of dead consoles. In the Main tab I added the program option --no-save. I don't think this does anything, since I can't end my console by pressing CTRL-D. In the R_Console tab, I added the following R snippet:
q <- function(save = "no", status = 0, runLast = TRUE){
.Internal(quit(save, status, runLast))
#<environment: namespace:base>
}
This gets rid of the annoying "save workspace" prompt when killing an R console with the red square (is that symbolic?) My current workspace also includes a C project, so my R console constantly comes up underneath a blank C-Build console. Annoying as all hell! Haven't solved that yet, but I did discover that from within a StatET code windows the keybinding CTRL-R C pulls the R console to the top.
With my R 2.11 debug configuration I get an extra console titled /usr/lib/jvm/java-6-openjdk/bin/java. You'll have to spelunk the console drop-down to find it. The following is a pertinent snippet of a successful initialization:
CONFIG: JR library path:
/home/allan/etc/R/amd64/2.11
/usr/local/lib64/R/site-library
/usr/lib64/R/library
10-Dec-2010 7:56:47 AM org.rosuda.rj.JRClassLoader addClassPath
FINE: Added '/home/allan/etc/R/amd64/2.11/rJava/java' to classpath of URL loader
A lot more spoo, then finally:
10-Dec-2010 7:56:48 AM de.walware.rj.server.jriImpl.RosudaJRIServer start
INFO: R engine started successfully. New Client-State: 'Connected'.
Looks good, right? But lo and behold in the R console:
[INFO] The R package 'rj' is not available, R-StatET tools cannot be initialized.
Ignore the lying bastard! Turns out my rj is working just fine. No idea why this failure message persists.
Every time around the block with this problem some new amazing piece of gravel ends up in my sneaker.
I don't know whether I've covered everything, but I've written enough for now. Maybe if there are comments I'll come back and fill in the blanks.
Note: found an Eclipse plugin for console switching by keyboard here: Eclipse: Keyboard shortcut for switching between consoles?
It looks like you need to install the RJ library which can be downloaded from the StatET site here: http://download.walware.de/rj/rj_0.5.0-5.tar.gz (more recent versions of RJ can be found at http://www.walware.de/it/downloads/rj.mframe)
If you save that file on your desktop, you can then load it into R with the command they provided R CMD INSTALL --no-test-load rj_*.tar.gz after navigating to your desktop or wherever you saved the library file. Alternatively, you MAY be able to use the GUI interface and select Install packages from local ZIP files under Packages in R, though I haven't used R on a Mac so the layout may be slightly different.
After installing rj with in the R console using
install.packages(c("rj", "rj.gd"), repos="http://download.walware.de/rj-1.1")
(See http://www.walware.de/?page=/it/statet/troubleshooting.mframe for the correct rj version),
do not forget to update the R_LIBS variable in Eclipse (Windows -> Preferences -> StatET -> Run/Debug -> R Environments -> Edit). To find out the value just type in the R console:
packageDescription("rj").
In my windows 8 installation this returns C:/Users/Fibonacci.PYTHAGORAS/Documents/R/win-library/3.0/rj/Meta/package.rds. The value of R_LIBS I set to
C:/Users/Fibonacci.PYTHAGORAS/Documents/R/win-library/3.0
which is the path where all libraries are installed.
As stated in http://www.walware.de/?page=/it/statet/troubleshooting.mframe newer versions (Versions > 0.5.5) do not need the R CMD INSTALL etc... command.
Here the quite similar I had and the solution I found.
I originally installed Statet using the Eclipse built-in tool "Install new software ...."
I seems it downloaded Statet + rj and that the installation process went well.
After this first installation, I tried to install both packages again. Eclipse refused reading that they already are installed. And, both packages/programs were actually listed in the window of Eclipse.
But, the R console still refused to launch, the dialog box reading that I had to check whether rj was available and that the file paths were correct. Another strange thing was that window explorer had been unable to locate rj on my disk.
???
To solve my whole problem, I simply downloaded rj from http://www.walware.de/ and installed this package via the r console and using the basic install.packages() command.
It now works perfectly .
But, I still don't understand everything ..... :-)
I'd make a comment but I lack the necessary reputation. For Windows, the procedure is the same. There's no zip file. Use the tar.gz. Worked for me. The command, working from the same folder as the downloaded file:
$ G:\R-2.12.0\bin\i386\R.exe CMD INSTALL --no-test-load rj_*.tar.gz
The project is now hosted on GitLab, see
https://gitlab.com/walware/de.walware.rj-server.gr/-/wikis/Installation.
To install:
install.packages(c("rj", "rj.gd"), repos="https://download.walware.de/rj-4.0")
Note that binary packages are available for Windows.
As explained in this message from Stephan Wahlbrink on 2022-02-03 announcing StatET 4.5 release, this version works with R 3.6 to 4.1, and RJ-4.0.
For current information on StatET, check the home page and especially the news.