I have a similar bug. I have been able to get past plymouth to t blank screen.
Here are contents from one of lightdm.logs
lightdm.log.5
rm: cannot remove '/run/user/ventrical/gvfs': Is a directory Error writing to daemon: Broken pipe Error writing to daemon: Broken pipe Error writing to daemon: Broken pipe Error writing to daemon: Broken pipe Error writing to daemon: Broken pipe Error writing to daemon: Broken pipe *** Error in `lightdm': double free or corruption (out): 0x09d36128 *** rm: cannot remove '/run/user/ventrical/gvfs': Is a directory
** (lightdm:1000): WARNING **: Failed to connect to Mir: connect: No such file or directory
** (lightdm:994): WARNING **: Failed to connect to Mir: connect: No such file or directory
** (lightdm:23809): WARNING **: Failed to connect to Mir: connect: No such file or directory
I have a similar bug. I have been able to get past plymouth to t blank screen.
Here are contents from one of lightdm.logs
lightdm.log.5
rm: cannot remove '/run/user/ ventrical/ gvfs': Is a directory ventrical/ gvfs': Is a directory
Error writing to daemon: Broken pipe
Error writing to daemon: Broken pipe
Error writing to daemon: Broken pipe
Error writing to daemon: Broken pipe
Error writing to daemon: Broken pipe
Error writing to daemon: Broken pipe
*** Error in `lightdm': double free or corruption (out): 0x09d36128 ***
rm: cannot remove '/run/user/
** (lightdm:1000): WARNING **: Failed to connect to Mir: connect: No such file or directory
** (lightdm:994): WARNING **: Failed to connect to Mir: connect: No such file or directory
** (lightdm:23809): WARNING **: Failed to connect to Mir: connect: No such file or directory