<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 13, 2018 at 11:13 AM, Robert Heller <span dir="ltr"><<a href="mailto:heller@deepsoft.com" target="_blank">heller@deepsoft.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="gmail-HOEnZb"><div class="gmail-h5">At Tue, 13 Feb 2018 10:26:17 -0800 "Ubuntu user technical support, not for general discussions" <<a href="mailto:ubuntu-users@lists.ubuntu.com">ubuntu-users@lists.ubuntu.com</a><wbr>> wrote:<br>
<br>
><br>
><br>
><br>
> On Tue, Feb 13, 2018 at 10:02 AM, Robert Heller <<a href="mailto:heller@deepsoft.com">heller@deepsoft.com</a>> wrote:<br>
><br>
> > At Tue, 13 Feb 2018 09:47:13 -0800 "Ubuntu user technical support, not<br>
> > for general discussions" <<a href="mailto:ubuntu-users@lists.ubuntu.com">ubuntu-users@lists.ubuntu.com</a><wbr>> wrote:<br>
> ><br>
> > ><br>
> > ><br>
> > ><br>
> > > I downloaded and installed a daily build of bionic-desktop-amd64.iso<br>
> > yesterday<br>
> > > and found it to be unstable... the X interface became unresponsive other<br>
> > > than the ability to move the mouse. This happened using the default<br>
> > > environment and in plasma with and without Wayland. I have 4 monitors<br>
> > with<br>
> > > an nvidia graphics card.<br>
> > ><br>
> > > VGA compatible controller: NVIDIA Corporation GK106 [GeForce GTX 660]<br>
> > (rev<br>
> > > a1)<br>
> > ><br>
> > > I didn't try to install the proprietary driver for it. I understand that<br>
> > > daily builds can be unstable, so my question is, should I bother trying<br>
> > to<br>
> > > report this problem and if so, how can I get any useful debug info from a<br>
> > > system that is non-responsive other than the ability to move the mouse?<br>
> > Or<br>
> > > is this kind of bug typical at this stage in testing and I should wait<br>
> > and<br>
> > > try again in a month?<br>
> ><br>
> > About getting "useful debug info from a system that is non-responsive other<br>
> > than the ability to move the mouse": can you do any of these:<br>
> ><br>
> > ssh into the machine from another computer?<br>
> ><br>
> Didn't try yet. I didn't know the IP address and my firewalls are locked<br>
> down pretty tight on that network, so I'd have to reconfigure things to<br>
> try. If I did get in, what should I look for? tail of logs, dmesg???<br>
<br>
</div></div>Looking at /var/log/Xorg.0.log could be enlightening, otherwise, yes looking<br>
at log files can could be useful. Seeing what sort of state X is in (S or D<br>
or R or what). Seeing what kill X or kill -9 X does, etc.<br>
<span class="gmail-"><br>
><br>
> > did you try installing as a non-graphical startup/login?<br>
> ><br>
> No I didn't but I don't anticipate any problems in that environment, so<br>
> there would be nothing to debug.<br>
<br>
</span>*Excecpt* you could verify that it is indeed the *GUI* subsystem that is<br>
borked. Also, you can separate the GUI *login* from the GUI itself. And you<br>
can try ctrl-alt-backspace to kill X11 and return to the console terminal and<br>
then look at log files, etc. Doing ctrl-alt-backspace with a GUI login, just<br>
restarts the GUI login and if the *GUI* is borked, that can be fruitless.<br>
<span class="gmail-"><br>
><br>
><br>
> > were you able to switch to another virtual console?<br>
> ><br>
><br>
> I didn't try that yet either... would that be ctrl-alt-F2? Again, what<br>
> commands would I run to capture useful data on a partially responsive<br>
> graphical session?<br>
<br>
</span>ctrl-alt-F[1234567]<br>
<br></blockquote><div>So the answer is that ctrl-alt-F[1234567] don't work when it gets into that state and neither does the caps lock light change when I press the button. Furthermore, after an upgrade, it gets into an even less responsive state where the mouse doesn't respond.</div><div><br></div><div>Additionally, after I installed kubuntu-desktop and logged in under plasma with Wayland and then rebooted and tried to log into a standard Ubuntu session, I got this error window on a black screen:</div><div><br></div><div>"unsupported number of arguments (4); falling back to default session"<br></div><div><br></div><div>Another problem I saw was that one of my monitors is in portrait mode and when I move the mouse across the right boundary, I see two mouse pointers for a while... one where it should be in the window the to right and one where it would be if it was in landscape mode.</div><div><br></div><div>Cheers,</div><div><br></div><div> Dave</div><div><br></div></div></div></div>