Avatar
Dr. Hax
d30ea98ea65e953f91ab93f6b30ea51eb33c506f87d49f600a139aef00aa9511
Cypherpunk. Infosec veteran of about 15 years (vulnerability research, exploit development and cryptography). Cypherpunks write code. :-) Signet maintainer. Self-custody your passwords... in hardware! https://hax0rbana.org/signet Want to see wider adoption so Bitcoin can be used as digital cash and not just an investment vehicle. XMR: 44RDkTFmTeSetwAprJXnfpRBNEJWKvA5dBH5ZVXA4DofgoZ9AgjyZdSa2fo7pMD3Qe3pdKga8X22y3Lyn1xYde5kPQPzVUu
Replying to Avatar Dr. Hax

`qvm-device mic list` shows the mic

Using --persistent functioned the same as without that flag (rc=0, no mic audio in qube). How do I undo that? Detach tells me persistent devices can't be detached while the qube is running and with the qube shut down it tells me "pulseaudio agent not running".

I see the mic in dom0 and I see levels there. I see the mic in the qube's GUI, but it's not selected by default, I can select the device, turn the volume slider up, but it looks like it's muted and that button is disabled. Pics attached below.

I also found that I don't have /etc/qubes/policy.d/50-sys-audio.policy in dom0, but I'm not sure if that was only present in an old version of Qubes. I saw a reference to it here: https://forum.qubes-os.org/t/unable-to-passthrough-audio-device-to-sys-audio/9684

Here's dom0, working like a champ:

#m=image%2Fjpeg&dim=633x331&blurhash=i1R3Wftn4n%25h00-mRjRiRi00D%25Dhp0%3Fa%25LtRIU%25M00%7Eq%5E%2BD*oHIUNHWEae008_IV00%252oyRPx%5DM_00S6-%3FIU%3FaxtxVxuM%7B&x=7990f9b2646b83831ced61b3a729ab04a5080ed84f347f4a7fa9010ad455c700

The default view when I open the system settings in the qube:

#m=image%2Fjpeg&dim=990x670&blurhash=r0Rp8-000000004n00t80000-ooISj-%3A-%3BE1bH%25L00n%7D%3Fbo%23%25Ms%3A%3Fbt7ay009F9F%3Fb%25M-%3BM%7BRkt700x%5D%25M%25LtRt7%25MRjt7004o4.xY.8%3FbRjWBt7&x=66c90d7d460703920782b5e3a3be6d36f12d309147b15bf338d3d50df240617f

And the best I can do with making the qube's setting be what I want:

#m=image%2Fjpeg&dim=990x670&blurhash=r0Rp8-8%5E0000008_00a%7D0000t6Rj-%3B%25M%25MIUWBxu00ac%3FHx%5D%252j%40%3Fbxuf600M_ITXA%3FH%3FbIUWCt700SPtR%5E*R.of%25MWBoz008_4nt7%3Fb%3FbWBWBt7&x=cbbb0c21934bef5fc6ce964f88dd430e4208036fd6c3016d2af267a878f37603

Tagging nostr:npub1f6ugxyxkknket3kkdgu4k0fu74vmshawermkj8d06sz6jts9t4kslazcka in case it they missed my last reply

If you are mainly doing one-offs, I'm not sure a pnp is really necesary. It's not that hard to place components as long as they are 0402 (imperial) or larger. I'm trying to move to 0603s and larger, personally.

Then again, my main project with SMT parts is the Signet and there are only like 15 or so components. Maybe a pnp would still make sense for big, complicated things, even if they are one-offs

The tedious part is applying solder paste without a stencil. A laser cutter might make it worth making a stencil for a prototype or one-off, but paying $7 for a stencil that is only gong to be used once, on a $3 board is cringe, IMO.

`qvm-device mic list` shows the mic

Using --persistent functioned the same as without that flag (rc=0, no mic audio in qube). How do I undo that? Detach tells me persistent devices can't be detached while the qube is running and with the qube shut down it tells me "pulseaudio agent not running".

I see the mic in dom0 and I see levels there. I see the mic in the qube's GUI, but it's not selected by default, I can select the device, turn the volume slider up, but it looks like it's muted and that button is disabled. Pics attached below.

I also found that I don't have /etc/qubes/policy.d/50-sys-audio.policy in dom0, but I'm not sure if that was only present in an old version of Qubes. I saw a reference to it here: https://forum.qubes-os.org/t/unable-to-passthrough-audio-device-to-sys-audio/9684

Here's dom0, working like a champ:

#m=image%2Fjpeg&dim=633x331&blurhash=i1R3Wftn4n%25h00-mRjRiRi00D%25Dhp0%3Fa%25LtRIU%25M00%7Eq%5E%2BD*oHIUNHWEae008_IV00%252oyRPx%5DM_00S6-%3FIU%3FaxtxVxuM%7B&x=7990f9b2646b83831ced61b3a729ab04a5080ed84f347f4a7fa9010ad455c700

The default view when I open the system settings in the qube:

#m=image%2Fjpeg&dim=990x670&blurhash=r0Rp8-000000004n00t80000-ooISj-%3A-%3BE1bH%25L00n%7D%3Fbo%23%25Ms%3A%3Fbt7ay009F9F%3Fb%25M-%3BM%7BRkt700x%5D%25M%25LtRt7%25MRjt7004o4.xY.8%3FbRjWBt7&x=66c90d7d460703920782b5e3a3be6d36f12d309147b15bf338d3d50df240617f

And the best I can do with making the qube's setting be what I want:

#m=image%2Fjpeg&dim=990x670&blurhash=r0Rp8-8%5E0000008_00a%7D0000t6Rj-%3B%25M%25MIUWBxu00ac%3FHx%5D%252j%40%3Fbxuf600M_ITXA%3FH%3FbIUWCt700SPtR%5E*R.of%25MWBoz008_4nt7%3Fb%3FbWBWBt7&x=cbbb0c21934bef5fc6ce964f88dd430e4208036fd6c3016d2af267a878f37603

nostr:npub1f6ugxyxkknket3kkdgu4k0fu74vmshawermkj8d06sz6jts9t4kslazcka, you are a fellow #QubesOS user, do you know of any reason why I would be able to `qvm-device mic attach foobar dom0:mic` just fine but no mic audio shows up in the VM?

- Audio shows up in dom0

- Attach has a rc of zero

- Worked on Tuesday

- Template VMs are the stock Debian and Fedora images

๐Ÿค”๐Ÿง

Should I see anything in dmesg in the VM when I attach the mic, or is that transparent to the guest?

I honestly don't know how the mic passthru works in Qubes because it has always worked perfectly out of the box for me, so I have never needed to dig into the details.

That's why I was so surprised to have this issue today (well, that and the fact that I didn't [knowingly] change anything)

I'd pay someone 5K sats if they can get my microphone passthru working again in #QubesOS 4.1.2 before Saturday evening (US).

Did anyone else's #QubesOS microphone passthru stop working today?

I can't figure out if this was an update. I haven't changed anything outside of my qubes, so I'm not sure what's going on here.

I can see audio in dom0, but not in the Qube's sound settings. So it's something related to assigning the mic to a qube.

And it worked YESTERDAY!

It worked on my previoys GrapheneOS phone, and the one before that. So if I can fimd an Android dev to help out, I'm confident it'll work with Graphene. ๐Ÿ™‚

TIL a little about how the apple industry works. I had to slice about twice as many apples to make this batch of apple chips. Same size dehydrator.

Why? Because I bought a bag of apples instead of buying individual apples and then put them in a bag.

It turns out, they sell the big apples individually and the small ones get bundled into bags. I never thought about it, but in retrospact, it makes sense. People who are carefully looking over each individual apple can pick and choose, but if you're getting a bag, the consumer is basically just saying "give me whatever ya got".

So, now that I realize it's more time and more apple cores, I'll factor that in when I am comparing prices.

I just paid for a domain registration in BCH, which I thought was great! Fee was less than a penny (US), and I only had the coins because I was holding BTC before the split, so it's like free money.

I still like Gandi. They'll probably go downhill now that they've been acquired, but it hasn't happened yet.

Emmanuel Goldstein (of #2600 fame) was in a near panic tonight on #OffTheHook because ticket sales to the #Hope #conference weren't flying off the shelf. They just went on sale EARLIER TODAY.

It seems a bit premature to panic after only a few hours of sales.

I was also entertained that he was whining about Google deciding what emails make it to people's inboxes, but then neither he nor 2600 are on #Nostr, where he'd have more direct access to people who wasn't to subscribe to newsletters, notifications, and announcements.

Someone want to pitch Nostr to him? I'm busy with building cryptographically secure password managers and working on other open source projects.

I can't think of anything that is going to beat KeepassDX. They have keyboard integration, can be unlocked by biometrics, and I have it set up to automatically sync my database to my Nextvloud server.

The verson of the Signet mobile app copies passwords to the clipboard, which is suboptimal. Beyond that, it doesn't even install on the latest version of Android and I haven't been able to get it to compile.

I'm looking for an Android dev who wild be willing to volunteer a few hours to get it fixed, if you know anyone.

There's also browser integration via browser add-ons, but I don't think anyone is currently using them (I know I am not). I'm already stretched thin, but testing them out is on my list.