On that launchpad bug report they're saying that core16 is no longer supported/maintained and that this is a downstream issue

There's a github repo that contains these (along with any of the other fonts from fonts.google.com): https://github.com/google/fonts

I saw that the ubuntu budgie project has been looking at the possibility of using this in place of nautilus for desktop icon support:

maybe solus MATE could use this instead?

I removed my custom /etc/systemd/system/lightdm.service file, and with the latest updates it does seem to boot reliably without the workaround on my xps 13 9360

In any case, it does seem like there are some others having similar issues with 8265 with recent firmware updates:

In T7225#136706, @moriel5 wrote:

Do you have a 7265? As I do not (Edit: I too have mistaken one of the posters for the OP).
By the way, @OddTod, after a bit of research, I had found someone posting similar post on the Intel forums.
That person's 7265 came with his laptop, made by Huawei (the model was not posted), and the Intel representative said that their 7265 may have had a customized OEM firmware, perhaps this is a similar situation?
I can say that I had pulled my QCA9377 from a Dell Vostro 3568, so that may have been the reason why it cannot find any networks on kernel 4.9-LTS.

I'm running an intel 8265 and the wifi is working without issue on kernel 4.19

Try my workaround from this comment: https://dev.getsol.us/T5641#135504

Afaik, there were two places xrender could be used in firefox:

In T5641#135597, @Girtablulu wrote:

Would be surprised if it get fixed this way, but I could already add this non-less to my open diff regarding updating lightdm D4299 @sunnyflunk.

What's so weird is that the intel_backlight takes sometimes a lot of time to start the other time it's extremely fast, @bwat47 did you do a reboot or a complete shutdown and new start for testing the changes?

In T5641#135572, @sunnyflunk wrote:

What if you change it to this https://dev.getsol.us/T7098#134111

It will bring it in line with the other DM's

In T5641#135565, @Girtablulu wrote:

Can you try to edit lightdm.service to

[Unit]
Description=Display Manager
Conflicts=xdm.service gdm.service kdm.service lxdm.service slim.service
After=systemd-backlight@.service

[Service]
ExecStart=/usr/sbin/lightdm
Restart=always
IgnoreSIGPIPE=no
BusName=org.freedesktop.DisplayManager

[Install]
Alias=displaymanager.service
WantedBy=graphical.target

this should force lightdm.service starter after systemd-backlight is started

In T5641#135555, @Girtablulu wrote:

1.112s systemd-backlight@backlight:intel_backlight.service, shoudn't this start earlier? does lightdm start after it with the sleep function?

In T5641#135552, @Girtablulu wrote:

I think this could be solved with an

After=${command}

instead of putting the lightdm.service to sleep, the question is just which one is needed.

Would be interesting to see the systemd-analyze blame output without the sleep to see if there is an issue with the booting order on your notebooks

I seem to have a reliably booting system after configuring my system to delay the start of lightdm by several seconds:

seems like this happens on nearly every boot for me now, in some cases I have to try like 5 times in a row to boot without getting stuck on a black screen. I'm at a loss as to what this could be... no other distro has ever given me this problem (including other distros using kernel 4.18).

In T5641#134625, @onepunchdan wrote:

@Peter-Kot, in my case, I cannot ctrl-alt-f[0-9] into any virtual console when I get a black screen, which prevents me from running "uname -r" and comparing that to the eopkg-installed version. As far as running out of space on the boot partition, I allocated ~500MB to the ESP when I first installed Solus and "df" shows only 82/500MB used.

One detail that might be useful to mention: when I first ran into this issue with kernel 4.18, I was able to get the system to boot successfully every time using the "nolapic" kernel parameter. Having only one logical cpu core made for an unpleasant user experience so I reverted to 4.17.

I was playing with solus on my 2013 macbook air the other day and I noticed the SSD not being detected at all as you're describing. I found that it works and detects the SSD if I boot with intel_iommu=off, might be worth a try

This still frequently happens on my xps 13 9360. even with a fresh solus 3.9999 install

Thanks, working great!

I have an xbox one controller and was having the same problem.

Thanks, I went into the ~/.config/menus folder and ran the command ln -s /usr/share/xdg/menus/applications.menu mate-applications.menu and now it works :)

I noticed that if I launch version 2.1.4 from the terminal it tells me: WARNING:menulibre: getDefaultMenuPrefix() 'No menu prefix found, MenuLibre will not function properly.'

if the visual refresh of MATE will use adapta (like the budgie version) I noticed the brisk menu looks kind of wonky with adapta: https://github.com/solus-project/brisk-menu/issues/83

I came across this old fedora issue that sounds really similar to this: https://bugzilla.redhat.com/show_bug.cgi?id=1006386

sounds similar to https://dev.solus-project.com/T4964

I've run into this on one of my machines (an ivybridge intel NUC)

I can confirm this here, I can login with the same email/pass from chrome or firefox fine but with the simple note app from the repo it just refuses to login

It almost seems like this is some kind of race condition. I'm finding that if I logout, wait 30 seconds and log back in the audio is fine.