ronin688

Just wanted to add that running the mover resolves this. So you don't have to fiddle with share settings to clear it.

I encountered this issue after changing cache settings on shares as noted above. I had planned on doing a reboot to resolve it, so I started the mover and by the time it was done the "starting services" text was gone. Not sure if the mover had anything to do with it but just wanted to add my experience here in case anyone else has this crop up. I know it's mentioned that this will be fixed in the next release, but I'm just curious if it's actually breaking something? Or is it just a harmless display bug? Thanks!

Just had this error in FCP as well. I went googling for answers and found this thread. Ignored for now. Thanks for posting about it, I just recently updated to 6.11.5. from 6.9.2 and was worried it was somehow related. Was happy to see this thread was only 6 hours old.

Thanks for this! Worked perfectly for me. I didn't require an HDMI dummy plug, my motherboard is a Gigabyte B460 HD3 with an i5 10400.

I'm on 6.9.2 as well. Just realised I hadn't mentioned that in my post. I've also tested this with VMware and the keyboard works fine.

I've been experiencing this issue as well. I can't type the | character, and several other keys are swapped such as # and ~. I may not have noticed but I'm taking an Intro to Linux course and just got to a section dealing with pipes. The keyboard works just fine in any other app, works fine on the unraid terminal, docker terminals etc. I've tried changing the keyboard layouts in the various vm's I've got running with no effect. I'm running the ENG (Canada) layout on the Win10 machine that is accessing the vm's using VNC. Would love to find a fix for this! Thanks!