Thanks for testing!

I see, thanks.

Wow, weird. Wonder if it has anything to do with this? https://www.phoronix.com/scan.php?page=news_item&px=Mesa-19.2-EGL-Plaform-Device

It does? Huh, I didn't see that in the release notes. That's kind of a big deal for them not to mention?

Bugfix release Mesa 19.1.1 is now available. Edited the task accordingly.

Thanks Josh! I've now noticed the same occurs with Musepack (mpcenc, no package), Opus (opusenc, libopusenc), TTA (ttaenc, no package), and Wavpack (wavpack, wavpack-utils). I don't use any of these currently, though (haven't even heard of TTA until now)

I don't have Intel anymore, so I can't test, sorry.

I've since done a fresh install from the new ISO and it's no longer an issue.

Aah, okay. I'll just wait a couple days for the sync, thanks guys!

Requirement already satisfied: nbxmpp in /usr/lib64/python3.6/site-packages (0.6.7)

"npxmpp" is a typo for "nbxmpp"

Gajim doesn't launch for me anymore. Here's the terminal output:

Using 2.39.1 on Ubuntu, the issue did not occur. I'll try 2.40 there next.

Just updated. Issue is still present. I can go test on Ubuntu to see if the issue is present there too.

@BlueKenny I'm using regular KeePass. Are you using KeePassX?

Yeah it's working fine now, sorry. For some reason I never got emailed for @DataDrake's response.

Nope!

Many thanks! Now I'll be able to play Talos Principle VR again without switching!

Note that python 3.7 is not backwards compatible with 3.6

Python has something to with Proton? Well, either way it would be nice to have the newest version in the repos. Done.

It's due in the next version, 1.4.0. If someone wants to build it when it releases, here's their guide. https://github.com/moneymanagerex/moneymanagerex/blob/master/BUILD.md#linux

On a fresh install of the latest Plasma ISO, the problem didn't occur, but after I ran through the updates I was reminded what this bug looks like.

It works! Thanks so much.

@sunnyflunk Still getting a "filter failed" error. Here's my error log:

Well unlike me and Stigarn (we both use the i5-4690k) you have an i7. It might help to name the specific model.

They are a small team and this issue doesn't seem to affect many people, so I'm guessing it's not the highest priority, that's OK. Also, we're not paying. Well, I'm paying them a few bucks on Patreon but that doesn't mean anything. Of course I'm sure they'd like to fix it, but this is one open issue out of many, it has a quick workaround, and they've got to choose how they spend their time.

Never mind, the issue resolved itself somehow.

I think it doesn't automatically install the right driver because the printer is a Brother HL-2220, but the correct driver is named "Brother HL2220". It probably needs the hyphen. I removed the printer and instead tried installing it through CUPS. However printing fails, and a status says filter failed. I've attached troubleshoot.txt:

Thank you very much!

Attached: Brother HL-2220

Yup.

Oh, I get this on Ubuntu too.

Here's two logs, one from waiting over 5 minutes for it to resolve itself, and another from waiting only 30 seconds before forcing it to connect by clicking "Wired Connection 1".

Here's some related bug reports on the Gnome Bugzilla. Guess this is probably an upstream issue?

This still happens, and I think it was also preventing me from getting online today: https://dev.solus-project.com/T5946

I managed to connect to the Internet using ip, but I didn't have DNS configured, as I could ping 8.8.8.8 but not google.com. Found that /etc/resolv.conf was an empty file (aside from a comment generated by networkmanager), so I put the nameserver line in there. Now I had DNS! So I installed slick-greeter and rebooted, which let me get into Budgie. But then I didn't have a network connection anymore. So I went to Edit Connections, and saw that "Automatically connect to VPN when using this connection" was still checked, despite having deleted that connection. So after unchecking it I was able to get online again.

Found at least one thing is needed in mesa for direct mode: VK_EXT_direct_mode_display, which a patch has recently been made for: https://patchwork.freedesktop.org/patch/203827/

After power cycling the SteamVR link box, I was able to get Steam to detect my Vive. However, then I run into this error:

What's the status of this? Talos Principle seems to work in Vulkan mode for me.

I noticed that the udev rule wasn't present in /usr/lib64/udev/rules.d, nor in /usr/lib/udev/rules.d, though the Steam Controller rule is in both. I tried adding the rule and rebooting, but my Vive still isn't recognized by Steam, only by the system as a second display. What do I need to do?

This works for what I need it to do. Thanks for packaging this!

@stigarn, have you tried disabling intel_iommu? It works for me, as without it the problem still occurs on that latest kernel.

Yeah, this doesn't happen to me anymore.

I was going to boot from the previous kernel again and get the dmesg from there to compare, but it's not in my boot menu anymore. Would that be helpful? If so, how do I get clr-boot-manager to show the last kernel again, or has it been removed from the system now?

The only relevant thing I could find was this PDF mentioning DMA remapping faults for the Xeon mentioned in the inxi output. But I'm not using integrated graphics so I'm not sure how that'd be related. https://www.thailand.intel.com/content/dam/www/public/us/en/documents/specification-updates/xeon-e3-1200v5-spec-update.pdf

Oh, I forgot about that old comment. It was hidden in the "older changes". I have my bar on the top of the screen and it shows up. You could try moving the bar? Though I would be surprised if that worked.

I don't know what @n8v8R means by a missing icon, but I'm referring to the Network Connections window you can get by right-clicking the network icon in the top bar of Budgie and clicking Edit Connections, or by right-clicking and choosing "Configure VPN" under VPN Connections. I then hit the '+' icon, and choose type "Import a saved VPN configuration", and then choose a *.ovpn file. I use UDP.

Since it's been a couple months, I figured I'd post an update: still happening. Hopefully this will be gone in Solus 4!

This doesn't happen anymore. Probably because I finally switched from linux-lts to linux-current.

Update: still happens, but I can confirm it does eventually connect, consistently about 5 minutes after startup.

I've noticed that this doesn't happen when a filesystem check happens on boot. I guess that adds the few extra seconds that are required to have the mouse/keyboard ready for the login.

Since it's been about a month, I figured I'd post an update: still happens.

Could you please support the HL-2220? It doesn't work in Solus currently, and I was able to get it working in Arch previously. Here is the driver: http://support.brother.com/g/b/downloadtop.aspx?c=us&lang=en&prod=hl2220_us