The mouse is not visible in graphical mode

Project:JNode Core
Category:feature request

The mouse is not visible in graphical mode. The desktop seems responding to the mouse button clicks (the context menu appears after clicking the right mouse button). However it is not possible to do anything because the mouse cursor is not visible.

It is a two button USB mouse with wheel. I mark the bug as critical because the desktop is totally unusable.

Additional information

The context menu appears in a various screen places after moving mouse and clicking on the mouse button. Hence the mouse movement is probably sensed.

The jnode.font.renderer = new results displaying garbage rather than text. The experimental rendering should not necessary work, but this information may provide a hint, what is going wrong.

mouse in graphical

I do not have the mouse either in the graphical mode it would definatly be easier if we could see the mouse even if it is a low resolution pixelated mouse icon

System info

Could you inform about your system? It could be a matter of finding a mouse driver.

Note, You have to use our

Note, You have to use our OS cup and not the Java cup, as it's trademark of Sun.

mouse display code

I have been working recently on the problem with there being no mouse icon and I have created an icon that anyone can use. I have the code for the icon to follow the mouse! I will put it right here. (It has the main method for an example)
import javax.swing.*;
import java.awt.*;
import java.awt.event.*;

public class LayeredPaneDemo2 extends JPanel
implements MouseMotionListener
private JPanel layeredPane = new JPanel();
private JLabel javaLabel;

public LayeredPaneDemo2()
final ImageIcon icon = createImageIcon("java cursor.jpg");
javaLabel = new JLabel(icon);

protected static ImageIcon createImageIcon(String path)
{ imgURL = LayeredPaneDemo2.class.getResource(path);
return new ImageIcon(imgURL);

public void mouseMoved(MouseEvent e)
// to set the icon right below the mouse cursor
public void mouseDragged(MouseEvent e)

public static void main(String[] args)
JFrame frame = new JFrame("Java Cursor App");

JComponent newContentPane = new LayeredPaneDemo2();



qemu / vnc workaround

If you're using QEmu to run jnode, there is a workaround using the -vnc option of qemu.

Most vnc viewers show a dot for the mouse position if the underlining server does not have a mouse set.

That is enough to make the system useable, but I also wonder why the mouse doesn't appear. The boot shows a logitech with scroll wheel detected.

Hai, good job, but why the Java CUP??

you done a good job....but why you use the picture of the SUN's logo??......

Still broken with release 0.2.5

I have just tried the recent release and was deeply impressed by how fast it boots (less then 8 seconds). The mouse cursor, however, stays invisible...

My mouse shows in /etc/X11/xorg.config as:
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "Emulate3Buttons" "true"

Hence, it should be "Kernel 2.6 and USB configuration mouse" (see Linux questions).

Under what conditions are you testing JNode?

The most frequent reason for the mouse cursor not being visible is that your graphic card is not supported and the VGA driver gets used when you run startawt. The mouse cursor will be visible only if the underlying graphic card and the related JNode driver have support for hardware cursor. Unfortunately the baseline VGA driver doesn't have such functionality (yet) and it has a few other issues too.


Here is a picture that we could use for the mouse all that will be left is to make the code for it which may be harder than making the picture.



Status:active» fixed

There is lot of things that's been done since that bug has been reported.
Especially, I wrote a SoftwareCursor which work with any graphic driver implementing FrameBufferAPI.

I am marking the bug as fixed.
If you can reproduce again that bug, then reopen it.


Status:fixed» closed

Automatically closed -- issue fixed for two weeks with no activity.


Really closing it!