Requesting support for MFC-9970CDW.

Took me a while to figure out Staudey's comment, but now I've got it working. If you don't have a $HOME/.local/share/Steam/package/beta file, open "Linux Steam Integration" from the main menu and disable the Native Runtime there. Start Steam as normal, also from the menu, and let it update and it'll work again.

Hi Josh, I wanted to ask if you might perhaps reconsider inclusion of Mosquitto with a different argument than the one given by WRostom: Mosquitto is not just a daemon (albeit it does include one, too), but also an MQTT client. At home, for example, we run the Daemon on an Alpine Linux box in the basement, but on my Laptop, which is Solus Linux, I'd love to be able to quickly check in on what's going on around the house, so having mosquitto_sub available would be nice :-)

I'm not the author of the Remote SSH extension. FWIW, this was brought up as a VSCode Issue first, before coming here. It seems Microsoft are not interesting in supporting builds other than their own. Any chance of a short phrase in Software Center warning people that the Solus build is likely to not work with an unknown number of extensions?

Unfortunately, at least the Remote SSH extension still doesn't seem to be working (or it might be a regression, I guess). Any chance of reactivating the MS version in 3rd-Party?

Damn shame, because it can do some things some people need that Meld just doesn't do...

Hopefully not OT?

Another helpful feature: Geeqie not only reads but also writes JPEG's title and description fields.

So if they'd be included in a distro that might send some contributors to them and then they might be able to make that change, it's a possibility, right? And in the meantime, couldn't the package description contain a warning about what you just explained? So then anyone who wants to install it, they can decide for themselves what's more important to them, privacy or security.

Does that mean it's not going to get approved now? :-(

First thought that comes to mind: atm there's no ldm yet. So make the driver a dependency of the software now and then swap it when hotplug driver installation has arrived, on which, if I understand you correctly, there's no eta anyways.

Thanks for following up, DataDrake! Unfortunately I really can't tell at the moment as I'll be in a place until at least mid/end May where laptops/etc. are prohibited. Phone only, so no Solus.

@mcritchlow's Gist is at https://gist.github.com/mcritchlow/61aeb06eae42cfe3125a949230c0e983 in case anyone else isn't finding it because of older comments being hidden.

Tbh I've given up on qemu-based things and have decided to stay with VirtualBox for the time being.

@mcritchlow, in the meantime, perhaps you wanna share that Gist here? (I've already got it installed, and obviously @greenwapiti has, too, but maybe others would be happy about finding it when googling.)

Urrr.... it's not that bad.

As it was not yet explicitly mentioned, I'll add that (only after upgrading a newly installed system), right before the Luks passphrase prompt, there's a message saying:

Okay, just managed to solve the problem with pyserial in a weird way:

It still has problems. After it complaining about missing python-setuptools and python-pyserial (which atm is 3.2.1-1-1) it now complains pkg_resources.DistributionNotFound: The 'pyserial<4' distribution was not found and is required by platformio and I've no idea how to fix that.

As a user, it goes like this:

Which noone having an integrated GPU only uses, his point prolly?

Installed, 150KB and 146KB respectively.

Thank you! It's starting up fine now. Would it be possible to make both of these dependencies to 'pcsc-lite'? (I've installed both as I wasn't sure which one I needed and they don't seem to conflict).

So I just tried, but unfortunately can't make it work because there's no /sbin/vboxconfig which VirtualBox tells me I need to run to compile a module.

Done, @mcritchlow! Let's hope you're right ;-)

That's a little sad, looking at the fpm project on GitHub (410 open issues, 42 open PRs). Apparently the request for Snap was made by His Shuttleworthness Himself a long time ago and there's also an ongoing situation regarding how to move forward. Perhaps if you point these two things out to the Zoom customer service person, they might forward the issue to an engineer?

Indeed it does! Thank you!

Can you reproduce the equalizer not working out-of-the-box?

So that leaves us with Gitkraken only? It'd be nice if there was a FLOSS alternative in the repos, although I've to admit I can't think of one atm.

One important thing about Hibiscus/Jameica is using card readers via CTAPI or pcsc-lite. At the moment that's something that doesn't (always? sometimes?) work under Solus and it seems that there's some sort of problem with the pcsc-lite version in Solus, but I'm not sure yet.

These seem to be relevant:

(And I've so far failed to get bridge networking going. But that's probably my bad understanding of libvirt concepts and I'll just have to keep at it). At least with bridge.conf being in /etc/qemu and /usr/libexec/qemu-bridge-helper being present there's now no error messages anymore.)

Update: bridge.conf is indeed expected in /etc/qemu.

@JoshStrobl, I'd still like to understand why there is a repository for geeqie (https://dev.solus-project.com/source/geeqie/) but it is not available as a package?
Is there anything that needs to be done to get it to appear as a package?

I do tend to do that, yeah. More matter-of-factly: how do things get into the thirdparty repository? Are they just ordinary packages that are stored in a different place from the main repository?

The English version of the website is not translated via Google Translate anymore. Also, the software itself is available in English (see note at the top of http://zettelkasten.danielluedecke.de/en/download.php). The official download link seems to be http://zettelkasten.danielluedecke.de/download/Zettelkasten3_linux.zip (it's still version 3.2.7 though).

(Hmm, it seems this here might be a duplicate of T3801?)

My apologies. Fixed.

It took a little more work for me than is described in comments so far. Here's what I had to do:

@der_eismann, why is it important for the build scripts to have a release so long as they can be instructed to build a specific release of the software itself?

With communication apps like this, I don't think a quality-over-quantity argument holds. They create peer pressure (being able to participate in a conversation, lesson, meeting, etc.) and if they're not available somewhere, then that platform can easily become uninteresting in the first place. And as far as the "it's easy to install yourself, there's a tutorial for it" argument: with apps belonging in to the TPR it's about convenience anyways. So why not offer that convenience to users who depend on an app like Zoom?

Thanks for the quick response. I'll re-open the other ticket and comment my argument there.

I was kinda sorta hopin' that it might be possible to make it available under "Third Party"?