Comment 4 for bug 1741925

Answers:
Do you have an additional monitor connected? NO What is the display resolution you use? 12??X800 Do things still crash if you change the resolution to something smaller than the native NO

Thank you for your direction. In attempt to narrow the failure down I examined the two visible symptoms:
1. Mouse-over the launcher causes the launcher and the task line at the top to disappear
2. There appears to be a recovery time of 10 to 30 seconds and then the launcher and all reappear
The most likely culprits appear to be:
1. Mouse software; I assume that is part of the Lunux kernel. I was unable to find any information on the Ubuntu software stack or architecture so I could not identify the process(es) used for the mouse.
To evaluate mouse malfunction I (a) tried both the laptop’s mouse-pad and a USB mouse with no difference in behavior and (b) did a mouse-over of some Linux apps where the button or widget reacts to a mouse-over; the mouse-over behavior worked as expected.
My conclusion is that the mouse and the mouse code is behaving properly.
2. Launcher code; without a software stack the name of the process is unknowable. Doing a query in the System Monitor gave a likely “api-spi-bus-launcher” (see that attached image, “Launcher properties 2018-01-09 12-44-12.png”).
An strace on that pid
 sudo strace -p 1488 -b execve -o launcher.txt
 [sudo] password for bruce:
yielded
   restart_syscall(<... resuming interrupted poll ...>) = 1
   read(3, "\2\0\0\0\0\0\0\0", 16) = 8
   poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}], 2, -1) = 1 ([{fd=3, revents=POLLIN}])
   read(3, "\2\0\0\0\0\0\0\0", 16) = 8
   poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}], 2, -1) = 1 ([{fd=3, revents=POLLIN}])
   read(3, "\2\0\0\0\0\0\0\0", 16) = 8
   poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}], 2, -1
I do not know how to read strace output. The “restart_syscall” line looks suspiciously like an error recover execution.
The launcher disappearance behavior is captured in two images, before the failure “Launcher failure a 2018-01-09 12-23-23.png” and during recovery “Launcher failure b 2018-01-09 12-24-39.png”. They are attached.?field.comment=Answers:
Do you have an additional monitor connected? NO What is the display resolution you use? 12??X800 Do things still crash if you change the resolution to something smaller than the native NO

Thank you for your direction. In attempt to narrow the failure down I examined the two visible symptoms:
1. Mouse-over the launcher causes the launcher and the task line at the top to disappear
2. There appears to be a recovery time of 10 to 30 seconds and then the launcher and all reappear
The most likely culprits appear to be:
1. Mouse software; I assume that is part of the Lunux kernel. I was unable to find any information on the Ubuntu software stack or architecture so I could not identify the process(es) used for the mouse.
To evaluate mouse malfunction I (a) tried both the laptop’s mouse-pad and a USB mouse with no difference in behavior and (b) did a mouse-over of some Linux apps where the button or widget reacts to a mouse-over; the mouse-over behavior worked as expected.
My conclusion is that the mouse and the mouse code is behaving properly.
2. Launcher code; without a software stack the name of the process is unknowable. Doing a query in the System Monitor gave a likely “api-spi-bus-launcher” (see that attached image, “Launcher properties 2018-01-09 12-44-12.png”).
An strace on that pid
 sudo strace -p 1488 -b execve -o launcher.txt
 [sudo] password for bruce:
yielded
   restart_syscall(<... resuming interrupted poll ...>) = 1
   read(3, "\2\0\0\0\0\0\0\0", 16) = 8
   poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}], 2, -1) = 1 ([{fd=3, revents=POLLIN}])
   read(3, "\2\0\0\0\0\0\0\0", 16) = 8
   poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}], 2, -1) = 1 ([{fd=3, revents=POLLIN}])
   read(3, "\2\0\0\0\0\0\0\0", 16) = 8
   poll([{fd=3, events=POLLIN}, {fd=5, events=POLLIN}], 2, -1
I do not know how to read strace output. The “restart_syscall” line looks suspiciously like an error recover execution.
The launcher disappearance behavior is captured in two images, before the failure “Launcher failure a 2018-01-09 12-23-23.png” and during recovery “Launcher failure b 2018-01-09 12-24-39.png”. They are attached.