| 23 Nov 2023 |
|  @ThorHop:matrix.org changed their display name from hopland (flaky frank) to hopland (evil entrepeneur). | 17:30:39 |
| @ThorHop:matrix.org changed their display name from hopland (evil entrepeneur) to hopland (nixpkgs-rolling when). | 18:25:24 |
| 24 Nov 2023 |
 uep | Ok, one really annoying 45 change so far: I can't use bluetooth A2DP audio anymore. It's locked af HFP, for several different headsets. pavucontrol says A2DP is "unavailable" and it appears to be because it's keeping the mic input open | 06:41:44 |
| uep | (I don't know if there's a better pipewire-specific tool) | 06:42:34 |
 Hubble the Wolverine (they/them) | In reply to @uep:matrix.org
Ok, one really annoying 45 change so far: I can't use bluetooth A2DP audio anymore. It's locked af HFP, for several different headsets. pavucontrol says A2DP is "unavailable" and it appears to be because it's keeping the mic input open Oh hm
I'm using release-23.11 right now and Bluetooth profiles work perfectly for me
I'm using a pxc-550 II | 07:31:38 |
| Hubble the Wolverine (they/them) | I used to have problems with profiles if I set custom options, where the HFP profiles go missing when I did set them | 07:32:22 |
| uep | they worked fine in the previous generation before the g45 update landed | 07:32:35 |
| uep | it would sometimes pick the wrong one by default, but I could switch them | 07:32:54 |
| Hubble the Wolverine (they/them) | What headphones are you using? Could that be related? | 07:33:36 |
| uep | three different sets all behave the same | 07:33:56 |
| Hubble the Wolverine (they/them) | What about setup? Do you have Bluetooth related settings? | 07:36:23 |
 Jan Tojnar | I can confirm AD2P works for me as well. There was a gnome-bluetooth update but that should mostly just be fixes. Maybe pipewire got bumped around the same time? | 08:00:02 |
| Hubble the Wolverine (they/them) | Hm | 08:33:02 |
| uep | I do have this, which I wouldn't expect to be the issue but can test without (a bit later)
services.pipewire.enable = true;
environment.etc = {
"wireplumber/bluetooth.lua.d/51-bluez-config.lua".text = ''
bluez_monitor.properties = {
["bluez5.enable-sbc-xq"] = true,
["bluez5.enable-msbc"] = true,
["bluez5.enable-hw-volume"] = true,
["bluez5.headset-roles"] = "[ hsp_hs hsp_ag hfp_hf hfp_ag ]"
}
'';
};
| 08:43:26 |
| uep | Oh, to be clear: the gnome control panel says it's in A2DP mode, but it's very clearly not. Mono audio, phone call quality, single speaker in the "play test sound" widget. Plus one of my headsets plays a particular indicator sound when in HFP, meant to indicate an incoming call from the second paired device while in use as headphones from the first) | 09:01:51 |
| uep | pavucontrol shows A2DP unavailable | 09:04:20 |
| Hubble the Wolverine (they/them) | In reply to @uep:matrix.org
I do have this, which I wouldn't expect to be the issue but can test without (a bit later)
services.pipewire.enable = true;
environment.etc = {
"wireplumber/bluetooth.lua.d/51-bluez-config.lua".text = ''
bluez_monitor.properties = {
["bluez5.enable-sbc-xq"] = true,
["bluez5.enable-msbc"] = true,
["bluez5.enable-hw-volume"] = true,
["bluez5.headset-roles"] = "[ hsp_hs hsp_ag hfp_hf hfp_ag ]"
}
'';
};
the environment.etc part is exactly what caused the problem | 09:10:28 |
| Hubble the Wolverine (they/them) | In reply to @uep:matrix.org
I do have this, which I wouldn't expect to be the issue but can test without (a bit later)
services.pipewire.enable = true;
environment.etc = {
"wireplumber/bluetooth.lua.d/51-bluez-config.lua".text = ''
bluez_monitor.properties = {
["bluez5.enable-sbc-xq"] = true,
["bluez5.enable-msbc"] = true,
["bluez5.enable-hw-volume"] = true,
["bluez5.headset-roles"] = "[ hsp_hs hsp_ag hfp_hf hfp_ag ]"
}
'';
};
* the environment.etc part is exactly what caused my problem | 09:10:33 |
| Hubble the Wolverine (they/them) | That exact config | 09:10:37 |
| Hubble the Wolverine (they/them) | I removed it | 09:10:39 |
| uep | interesting.. same config, opposite effect | 09:11:12 |
| uep | 
Download image.png | 09:25:53 |
| uep | Well then | 09:25:56 |
| Hubble the Wolverine (they/them) | I think the workaround may be outdated | 13:53:21 |
| Hubble the Wolverine (they/them) | In reply to @hubofeverything:bark.lgbt
Now I have a separate issue
When I plug in my display with displayport, gnome seems to restart. This doesn't happen with my HDMI display.
Short excerpt from the log of display-manager.service
Nov 21 04:30:40 Gulo-Laptop gdm[1842]: Gdm: GdmDisplay: Session never registered, failing
Nov 21 04:30:40 Gulo-Laptop gdm[1842]: Gdm: Child process -7523 was already dead.
I'm on the gnome branch, using a laptop with nvidia hybrid graphics.
Re: displayport instability on 23.11
Nov 24 06:06:16 Gulo-Laptop systemd[2731]: Starting GNOME Shell on Wayland...
Nov 24 06:06:16 Gulo-Laptop .gnome-shell-wr[2907]: Running GNOME Shell (using mutter 45.1) as a Wayland display server
Nov 24 06:06:17 Gulo-Laptop .gnome-shell-wr[2907]: Made thread 'KMS thread' realtime scheduled
Nov 24 06:06:17 Gulo-Laptop .gnome-shell-wr[2907]: Device '/dev/dri/card1' prefers shadow buffer
Nov 24 06:06:17 Gulo-Laptop systemd[2731]: org.gnome.Shell@wayland.service: Main process exited, code=killed, status=9/KILL
Nov 24 06:06:17 Gulo-Laptop systemd[2731]: org.gnome.Shell@wayland.service: Failed with result 'signal'.
Nov 24 06:06:17 Gulo-Laptop systemd[2731]: Failed to start GNOME Shell on Wayland.
Nov 24 06:06:17 Gulo-Laptop systemd[2731]: org.gnome.Shell@wayland.service: Triggering OnFailure= dependencies.
| 14:09:37 |
| Hubble the Wolverine (they/them) | No idea if this is related to nvidia drivers or not | 14:10:15 |
