Comment 3 for bug 1826691

Thank you very much. I think I can live with the first option. I'll look more into the implications, but it seems to be better than not having the process running at all.

Not sure if I need to do anything to close this.

> 1. Blacklist synapticsmst plugin in fwupd in /etc/fwupd/daemon.conf

This seems to help. I reinstalled the fwupd package and added synapticsmst to the blacklist. Now I get responses back from the fwupdmgr command. It also responds to systemctl start/stop.

> 2. Try a newer kernel (like 5.x)

19.04 is running 5.0.

$ uname -rmv
5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64

> 3. Backport that patch from fwupd

I tried pulling the repo and building the latest 1.2.8 tag, but I didn't make it very far into the build. I'm not very familiar with ninja, so I'll have to see if I can figure out why it's failing. If I get it all the way through, I'll see if this works without the blacklisting.