!XQQVyIbcAcHFvzmcTl:nixos.org

NixOS GNOME

394 Members
A room for maintainers of GNOME & GNOME-Related desktop environments (xfce, cinnamon, pantheon...)91 Servers

Load older messages


SenderMessageTime
24 Nov 2023
@hubofeverything:bark.lgbtHubble the Wolverine (they/them)Hm08:33:02
@uep:matrix.orguep

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:matrix.orguepOh, 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:matrix.orgueppavucontrol shows A2DP unavailable09:04:20
@hubofeverything:bark.lgbtHubble 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
@hubofeverything:bark.lgbtHubble 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
@hubofeverything:bark.lgbtHubble the Wolverine (they/them)That exact config09:10:37
@hubofeverything:bark.lgbtHubble the Wolverine (they/them)I removed it09:10:39
@uep:matrix.orguepinteresting.. same config, opposite effect09:11:12
@uep:matrix.orguepimage.png
Download image.png
09:25:53
@uep:matrix.orguepWell then09:25:56
@hubofeverything:bark.lgbtHubble the Wolverine (they/them)I think the workaround may be outdated13:53:21
@hubofeverything:bark.lgbtHubble 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
@hubofeverything:bark.lgbtHubble the Wolverine (they/them)No idea if this is related to nvidia drivers or not14:10:15
@hubofeverything:bark.lgbtHubble the Wolverine (they/them)I want to move to Hyprland but I also can't :P14:21:50
@alper-celik:matrix.org@alper-celik:matrix.org left the room.14:27:58
@jayhenks:matrix.orgjayhenks joined the room.15:01:40
@jayhenks:matrix.orgjayhenkswas photos app removed in gnome 45?15:16:49
@jayhenks:matrix.orgjayhenksi do not have it anymore15:16:56
@hubofeverything:bark.lgbtHubble the Wolverine (they/them)
In reply to @jayhenks:matrix.org
was photos app removed in gnome 45?

It's replaced with Image viewer (Loupe)

23.11 (WIP) release note:
- GNOME has been updated to version 45, see the [release notes](https://release.gnome.org/45/) for details. Notably, Loupe has replaced Eye of GNOME as the default image viewer, Snapshot has replaced Cheese as the default camera application, and Photos will no longer be installed.

15:24:16
@hubofeverything:bark.lgbtHubble the Wolverine (they/them)It can still be manually installed I think15:25:28
@jayhenks:matrix.orgjayhenks
In reply to @hubofeverything:bark.lgbt

It's replaced with Image viewer (Loupe)

23.11 (WIP) release note:
- GNOME has been updated to version 45, see the [release notes](https://release.gnome.org/45/) for details. Notably, Loupe has replaced Eye of GNOME as the default image viewer, Snapshot has replaced Cheese as the default camera application, and Photos will no longer be installed.

huh, but loupe does not really do the same as photos. Instead of showing all your photos in a nice grid you just have to click through them all
15:30:33
@jayhenks:matrix.orgjayhenksand also select the directories15:31:04
@jayhenks:matrix.orgjayhenksor am i wrong?15:32:59
@hubofeverything:bark.lgbtHubble the Wolverine (they/them)
In reply to @jayhenks:matrix.org
huh, but loupe does not really do the same as photos. Instead of showing all your photos in a nice grid you just have to click through them all
I'm not sure
15:36:38
@hubofeverything:bark.lgbtHubble the Wolverine (they/them)It was updated because of GTK4, an aging codebase, GPU acceleration etc Outlined here: https://blogs.gnome.org/sophieh/2023/08/30/viewing-images-in-gnome-loupe-and-glycin/ and https://apps.gnome.org/Loupe/15:39:07
@hubofeverything:bark.lgbtHubble the Wolverine (they/them)Again, eog (gnome-photos) can be installed with systemPackages, but loupe is the new default AFAIK15:40:20
@jayhenks:matrix.orgjayhenks
In reply to @hubofeverything:bark.lgbt
Again, eog (gnome-photos) can be installed with systemPackages, but loupe is the new default AFAIK
yeah, just a bit confusing for me as they actually server kinda different purposes
15:41:27
@hubofeverything:bark.lgbtHubble the Wolverine (they/them)I don't know enough about the two projects to comment further15:43:40
25 Nov 2023
@onscreenproton:kde.org@onscreenproton:kde.org joined the room.00:00:59

Show newer messages


Back to Room ListRoom Version: 6