@eharris I think it's better to create a new report, because the cause of your problem might be different.
It's been merged to master branch. I'd presume, there has not been a major release from master for an year.
I presume you mean the description of how segregated linking works, you can read the pdf here. It's Collabora's site, but judging by the video the work have been done by Valve and Collabora together.
Nice! I personally unfortunately can't test, because for me that happened just once after weeks of uptime and I wasn't doing anything different from the weeks before it. Maybe @coolbeans234 has some steps to reproduce…?
⁺¹, just had the same problem. Pipewire 1.0 (the latest), and it is also inside audioconvert.c
(specifically, ../pipewire/spa/plugins/audioconvert/audioconvert.c:2899
). Inspecting in gdb
I found that bd->chunk
is 0x2
, so dereferencing bd->chunk->offset
results in crash.
FTR, meson supports ternary, so this can be simplified to a one-liner opt_flags = host_machine.cpu_family() != 'alpha'? ['-Ofast'] : ['-O3']
0.3.72
0.4.14
Arch Linux
6.4.1-arch2-1
Fresh Archlinux installation on Dell G15
.
wpctl status
shows two microphones:
Comet Lake PCH cAVS Headset Mono Microphone + Headphones Stereo Microphone
Comet Lake PCH cAVS Digital Microphone
2
is real, but 1
is the default one and does not receive any sound by default. However, if you plug in headphones, it will suddenly start receiving the internal sound that gets played in headphones, except it is distorted and has bad quality.
(FTR: I only tested plugging in headphones that have no microphone)
Comet Lake PCH cAVS Headset Mono Microphone + Headphones Stereo Microphone
is the default devicepw-record ./sound-from-micro
, say "hello", then Ctrl+c itmpv ./sound-from-micro
mpv
will produce distorted sound of whatever was playing in the headphones
You would hear "hello" and no other sound
pw-dump > pw-dump.log
: pw-dump.log
Konstantin Kharlamov (8c20afda) at 23 Jun 11:58
So, do I need to drop the russian translation commit too, or it is okay to have it?
Konstantin Kharlamov (8c20afda) at 22 Jun 07:42
ru.po: translate "Set as default"
... and 1 more commit
Okay, so, anyway, I removed the change to po/
dir completely, and just added a single russian translation in a separate commit.
Konstantin Kharlamov (93a177da) at 22 Jun 07:33
ru.po: translate "Set as default"
... and 1 more commit
I don't know if we change the
po
files this way, or if it filters back via translators.
FTR, if it's the only remaining question holding it back from being merged, I can just remove that part, because, like, whatever
Konstantin Kharlamov (3fecf7f7) at 21 Jun 16:26
treewide: change "[Set as] fallback" to "default"
Konstantin Kharlamov (dc13ead4) at 21 Jun 16:25
treewide: change "[Set as] fallback" to "default"
This came up on #pipewire, and as turned out many people have been making same mistake. Let's fix this source of confusion once and for all.
The "Set as fallback" title is a frequent source of confusion, many people look at it and do not realize that its actual functional is "setting as default". Presumably, when this title first appeared it was presumed that apps should chose a device themselves, and then if they don't there's a "fallback". But in reality most apps do not chose any device explicitly, and it's expected behavior to make use of this "fallback" device. So it is more correct to call a "default" device.
Konstantin Kharlamov (9a7402ee) at 21 Jun 16:19
treewide: change "[Set as] fallback" to "default"
Konstantin Kharlamov (e01e9956) at 21 Jun 16:18
treewide: change "[Set as] fallback" to "default"
Hello and thank you for testing this! What you stumbled upon seems like a new bug, so please create a report for it, so it can be tracked separately.