On 7/5/2019 9:30 AM, Steve McIntyre wrote: > On Fri, Jul 05, 2019 at 02:09:24AM +0000, Kevin Williams wrote: >> On 7/4/19 11:21 AM, Steve McIntyre wrote: >>> >>> That's odd. I've just done a test installation of lxqt here in >>> qemu/kvm using that image and I can't reproduce your problem - see >>> >>> https://www.einval.com/~steve/tmp/lxqt-rc3.png >>> >>> from straight after boot. Could you give us a copy of your >>> installation syslog please? >> >> Sure. It's too big for pastebin, so here it is: >> https://mega.nz/#!OFYiDYST!6rvFjxgnwVangqm_5TXvoWt-mcnBWruuqq_Tn2rdXls >> >> Since I made the report, I made a Hyper-V VM with a fresh install of >> Buster/KDE and it's got the same behavior. Possibly sddm and Hyper-V >> don't get along? No troubles with DEs that use lightdm. > > OK, that looks like it. There's no obvious problems in the syslog, so > it looks like the installer worked fine. Are there any special options > for Hyper-V to control graphics emulation or pass-through? I'm > *guessing* that might be it, but I've never played with it myself.
Not that I can see. There's an option to install a RemoteFX 3D Video Adapter (not presently installed) but that's all. If I install lightdm into this virtual machine, set it as the default, and reboot, Buster/LXQt will bring up a login GUI as expected. Should we close this ticket and make one against sddm?
<<attachment: ktwilliams.vcf>>
