[Bug 954108] New: No visible mouse pointer
http://bugzilla.opensuse.org/show_bug.cgi?id=954108 Bug ID: 954108 Summary: No visible mouse pointer Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: 64bit OS: openSUSE 42.1 Status: NEW Severity: Major Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs@forge.provo.novell.com Reporter: antoine.mechelynck@gmail.com QA Contact: xorg-maintainer-bugs@forge.provo.novell.com Found By: --- Blocker: --- After upgrading my desktop system from 13.2 to Leap 42.1: GUI mouse "works", but no visible mouse pointer (GPM mouse is OK). Mouse (and keyboard) connected on USB Graphics hardware by Intel. It worked normally under 13.2 (with kernel-desktop). AFAICT the Leap 42.1 system has only kernel-default (and kernel-xen). Then I configured repositories and ran "zypper up". It found more than 3100 packages to upgrade. At some point during the zypper run, the mouse pointer appeared (white arrow on KDE windows, black arrow on GNOME windows). After reboot, no mouse pointer again. Even actions which are supposed to change the mouse pointer shape don't make it visible: for instance in ksnapshot, selecting "Take a new snapshot" makes its window disappear, the crosshairs pointer isn't visible. Then clicking the mouse makes the ksnapshot window reappear, the arrow (default) pointer is still not visible. Similarly when moving the hot point between a "normal" area (default cursor not visible) and a browser textarea (I-beam cursor not visible). I can only see where the mouse is if it happens to be on a widget which changes its look on mouseover, or by drag-select where that is possible. In the general case I have to guess. Keyboard control is often (not always) possible, but usually not easy (tabbing through to the desired widget is often quite time-consuming). This happens in both KDE and GNOME windows so I suppose the bug is in neither. Xorg is my "best guess" at a component, feel free to move the bug as appropriate. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
Tony Mechelynck
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c1
--- Comment #1 from Tony Mechelynck
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c2
Stefan Dirsch
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c4
Bjørn Lie
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c5
--- Comment #5 from Tony Mechelynck
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c6
--- Comment #6 from Tony Mechelynck
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c7
Tony Mechelynck
This may be similar to bsc#827698 (or bsc#905158 - which is a customer issue and thus not visible to everybody).
Can you change /etc/X11/xorg.conf.d/50-devices.conf and select a different driver (ie. fbdev?) and see if the issue reoccurs?
# ls -l /etc/X11/xorg.conf.d/50-devices.conf ls: cannot access /etc/X11/xorg.conf.d/50-devices.conf: No such file or directory Shall I create it? And with which contents? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c8
Tony Mechelynck
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c9
--- Comment #9 from Tony Mechelynck
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c10
Tony Mechelynck
Since I don't know how to change it, let's see if YaST can do it for me…
No obvious menuitem. OK, please tell me. As I said in comment #0 (but sometimes there are things which are worth saying twice) my graphics hardware is by Intel. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c11
Egbert Eich
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c12
--- Comment #12 from Tony Mechelynck
Sorry, YaST can't do this for you.
- Uncomment lines starting with 'Section', 'Identifier', 'Driver' and 'EndSection'.
- Replace the string after 'Driver' (ie "radeon" here) with a different driver ("fbdev" for instance).
OK, here's the result. # Having multiple "Device" sections is known to be problematic. Make # sure you don't have in use another one laying around e.g. in another # xorg.conf.d file or even a generic xorg.conf file. More details can # be found in https://bugs.freedesktop.org/show_bug.cgi?id=32430. # Section "Device" Identifier "Default Device" # Driver "fbdev" # # ## Required magic for radeon/radeonhd drivers; output name # ## (here: "DVI-0") can be figured out via 'xrandr -q' # #Option "monitor-DVI-0" "Default Monitor" # EndSection It seems to make sense to Vim syntax highlighting. Now the biggie: close everything cleanly and reboot. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c13
Tony Mechelynck
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c14
Egbert Eich
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c15
Tony Mechelynck
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c16
--- Comment #16 from Tony Mechelynck
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c17
Bjørn Lie
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c18
Egbert Eich
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c19
Bob Goddard
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c20
--- Comment #20 from Tony Mechelynck
This happens with NVidia driver as well and is very random.
The only iffy solution I have found is to run "unclutter -reset -root -grab -idle 1 -visible", wait a second or two then move the mouse pointer and see if it comes back. You may have to do this a few dozen times before it appears.
This bug has been in place since at least 13.1 and affects all distros.
So we have several solutions: • the above (does it have to be run from an X terminal or is it OK in a pure-text console, e.g. when seeing the X login form but not yet replying to it)? I haven't yet tested it, I shall at next reboot. (BTW unclutter wasn't yet installed on my system; I just installed it.) A few dozen times? We-e-ell… • restarting X, e.g. "systemctl try-restart display-manager" which can be run from /dev/tty2 while the X login form is up; see also comment #16; • setting fbdev as the driver instead. On my system this appears on 42.1 but on 13.2 and before it didn't. I hope that a solution will be found even if fbdev works for me. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c21
--- Comment #21 from Bob Goddard
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c22
Tony Mechelynck
It connects to the X server, so as long as DISPLAY is set correctly, it should work.
The reason I use it rather than resetting the X server, is there is usually something on the screen I want to preserve, or setting everything up after I log in is a pain.
Yeah, that's why IMHO restarting the display manager is only practical while the X login form is waiting for an answer, see comment #1. (In reply to Tony Mechelynck from comment #20)
So we have several solutions: s/solutions/workarounds/
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c23
--- Comment #23 from Egbert Eich
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c24
--- Comment #24 from Egbert Eich
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c25
--- Comment #25 from Tony Mechelynck
Currently building in https://build.opensuse.org/project/show/home:eeich:bsc954108/xorg-x11-server. Bob, Tony, any taker?
404 Not Found. At the moment I don't have a remote machine where I could run gdb, but "a server which spits out the info needed to come closer to the cause in the log" sounds interesting to me. Since AFAIK the bug is solid on my machine I wouldn't have to leave it on for days. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c26
--- Comment #26 from Tony Mechelynck
(In reply to Bob Goddard from comment #19)
This happens with NVidia driver as well and is very random.
The only iffy solution I have found is to run "unclutter -reset -root -grab -idle 1 -visible", wait a second or two then move the mouse pointer and see if it comes back. You may have to do this a few dozen times before it appears.
This bug has been in place since at least 13.1 and affects all distros.
So we have several solutions: • the above (does it have to be run from an X terminal or is it OK in a pure-text console, e.g. when seeing the X login form but not yet replying to it)? I haven't yet tested it, I shall at next reboot. (BTW unclutter wasn't yet installed on my system; I just installed it.) A few dozen times? We-e-ell… [...]
(In reply to Bob Goddard from comment #21)
It connects to the X server, so as long as DISPLAY is set correctly, it should work. [...]
It doesn't work on /dev/tty2, where $DISPLAY is not set. I believe that this is intentional. So you have to be already logged-in to X in order to use it — in xterm, konsole, gnome-terminal, etc. but not in a non-X linux console. I tried, and what I got was "unclutter: could not open display" followed by exit 1. There was an update to Xorg today (from Leap 42.1 Update or Update-Test?) but no change. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c27
--- Comment #27 from Egbert Eich
It doesn't work on /dev/tty2, where $DISPLAY is not set. I believe that this is intentional. So you have to be already logged-in to X in order to use it — in xterm, konsole, gnome-terminal, etc. but not in a non-X linux console.
DISPLAY is not set on the console as it makes sense only in an X session. Of course you can set it manually. But depending on the location of your authorization file it may not work either as the client isn't able to find the credentials it requires to authenticate to the Xserver. So the Xserver may treat it as unauthorized and refuse connection. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c28
--- Comment #28 from Bob Goddard
(In reply to Tony Mechelynck from comment #20)
(In reply to Bob Goddard from comment #19)
This happens with NVidia driver as well and is very random.
The only iffy solution I have found is to run "unclutter -reset -root -grab -idle 1 -visible", wait a second or two then move the mouse pointer and see if it comes back. You may have to do this a few dozen times before it appears.
This bug has been in place since at least 13.1 and affects all distros.
So we have several solutions: • the above (does it have to be run from an X terminal or is it OK in a pure-text console, e.g. when seeing the X login form but not yet replying to it)? I haven't yet tested it, I shall at next reboot. (BTW unclutter wasn't yet installed on my system; I just installed it.) A few dozen times? We-e-ell… [...]
(In reply to Bob Goddard from comment #21)
It connects to the X server, so as long as DISPLAY is set correctly, it should work. [...]
It doesn't work on /dev/tty2, where $DISPLAY is not set. I believe that this is intentional. So you have to be already logged-in to X in order to use it — in xterm, konsole, gnome-terminal, etc. but not in a non-X linux console.
I tried, and what I got was "unclutter: could not open display" followed by exit 1.
There was an update to Xorg today (from Leap 42.1 Update or Update-Test?) but no change.
Log into the vty as the desktop user , run "export DISPLAY=:0", the try unclutter. -- You are receiving this mail because: You are on the CC list for the bug.
For some reason the full link doesn't work. Try: https://build.opensuse.org/package/show/home:eeich:bsc954108 [...] I still get Error 404, even after logging in to the Build Service. Maybe that
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c29
--- Comment #29 from Tony Mechelynck
Log into the vty as the desktop user , run "export DISPLAY=:0", the try unclutter.
I'll try that at next reboot (or maybe "DISPLAY=:0 unclutter" etc.) but when you say "the desktop user" doesn't it mean "the user already logged-in to X"? At the X11 login prompt, there isn't yet a "desktop user", is there? (there is only a "default desktop user" presented by the display manager but not yet authenticated), and after logging in I could start an xterm (by keyboard: Alt+F2 then type "xterm" without quotes) and see when (and if) the mouse pointer appears without needing to switch between text (Ctrl+Alt+F2) and GUI (Ctrl+Alt+F7). Well I'll try anyway. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c30
--- Comment #30 from Tony Mechelynck
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c31
--- Comment #31 from Bob Goddard
Before logging into X, that unclutter command complains about "no protocol" (or something) and exits with status 1. After logging in, AFAICT it hangs.
Restarting the display-manager service (when not yet logged in to X) or logging out and back in (when already logged in) suit me better: more responsive and more deterministic.
I have already said that the vty console login should be as the same user as the logged in desktop. It does NOT hang. It stays in the foreground, it is not a natural daemon, it does not exit when run. Why do you think there is an "idle" option, it loops. And I have already said it is useful if you need to preserve what is on your current desktop. I'm now out of this. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c32
--- Comment #32 from Egbert Eich
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c33
--- Comment #33 from Tony Mechelynck
Please grab the xserver in http://download.opensuse.org/repositories/home:/eeich:/bsc954108/standard/. This got some extra logging. Thanks!
I found a software repository there, enabled it in YaST, and I'm going to look which packages seem relevant; but before I do: There just was an update to systemd (in Leap42.1 Update-Test) so I had to reboot. Usually I hit Esc as soon as the graphical "waiting" screen (green with a square on its diagonal and three alternating blinking disks) appears, because I prefer watching the boot log in the text console. This time I didn't, and when the X11 login screen appeared, it had a visible mouse pointer. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c34
Tony Mechelynck
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c35
--- Comment #35 from Tony Mechelynck
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c36
--- Comment #36 from Tony Mechelynck
(In reply to Tony Mechelynck from comment #30)
Before logging into X, that unclutter command complains about "no protocol" (or something) and exits with status 1. After logging in, AFAICT it hangs.
Restarting the display-manager service (when not yet logged in to X) or logging out and back in (when already logged in) suit me better: more responsive and more deterministic.
I have already said that the vty console login should be as the same user as the logged in desktop.
It does NOT hang. It stays in the foreground, it is not a natural daemon, it does not exit when run. Why do you think there is an "idle" option, it loops.
And I have already said it is useful if you need to preserve what is on your current desktop.
I'm now out of this.
Ah, OK. Well, when I ran it in xterm I didn't see the mouse pointer appear. Maybe I wasn't patient enough. OTOH on my system the pointer does not appear at first start of X (so the sooner I get it back the better) but once I got it it stays on. I suppose this is a case of "YMMV". -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c37
--- Comment #37 from Egbert Eich
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c38
--- Comment #38 from Egbert Eich
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c39
--- Comment #39 from Tony Mechelynck
Unfortunately, the log file from comment #34 does not provide any clue as the culprits I had been thinking about did not appear :(
I don't remember exactly what I did to run the test (other than what appears in my above comments) but I notice the following on my present system: - package xorg-x11-server was compiled 2015-11-26 (a few days after I did the test); its "Vendor" is set to "openSUSE". - my current /etc/X11/xorg.conf.d/50-device.conf is entirely commented-out but I have an /etc/X11/xorg.conf.d/50-device.conf.new which sets fbdev as the default driver. - I have a visible mouse pointer as soon as the X login form appears after reboot. The problem may or may not have been fixed by the Nov.26 Xorg update but my present setup is good enough for me. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c41
Tony Mechelynck
Tony, are you saying the problem disappeared since you've updated the Xserver? I'm not sure why, meanwhile we've updated a lot of other components as well. To know what had been changed in the Xserver you're using, I'd need the output of 'rpm -q --changelog xorg-x11-server'.
It's almost two months now since you've reported this working - does it still work for you? Can we close the ticket?
Current x11-xorg-server package is version 7.6_1.17.2-x86_64 from vendor openSUSE (IOW, IIRC, it isn't yours, which had a different vendor name). The problem has not reappeared for me. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c42
Tony Mechelynck
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c43
--- Comment #43 from Tony Mechelynck
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c44
--- Comment #44 from Tony Mechelynck
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c45
--- Comment #45 from Tony Mechelynck
P.S. Egbert, maybe see bug 961439 comment #4 ?
(mentioned by the following entry in my changelog: * Mon Jan 11 2016 eich@suse.com - u_busfault_sigaction-Only-initialize-pointer-when-matched.patch Only initialize pointer when matched (boo#961439). ) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=954108
http://bugzilla.opensuse.org/show_bug.cgi?id=954108#c46
--- Comment #46 from Tony Mechelynck
participants (1)
-
bugzilla_noreply@novell.com