all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ignas Lapėnas" <ignas@lapenas.dev>
To: Daniel Hatton <dan.hatton@btinternet.com>
Cc: GUIX help list <help-guix@gnu.org>
Subject: Re: How to diagnose Bluetooth trouble?
Date: Sun, 24 Nov 2024 12:53:30 +0200	[thread overview]
Message-ID: <871pz0ewd1.fsf@lapenas.dev> (raw)
In-Reply-To: <871df5e0-98e9-4663-b11b-de3ec0707599@btinternet.com> (Daniel Hatton's message of "Thu, 21 Nov 2024 18:26:55 +0000")

Hi,

Tried trying to get your config running with guix system reconfigure.
Noticed that you're using bluetooth-service instead of
bluetooth-service-type in services:

/home/ignaslapenas/develop/packages/oses/test.os:47:17: warning: 'bluetooth-service' is deprecated, use 'bluetooth-service-type' instead

Also got something new, that I had no idea it could happen.

guix system: error: duplicate 'pulse' entry for /etc

This one should be because %desktop-services already contain the
definition for pulseaudio. You can find what services are enabled by
default in desktop.scm (gnu/services/desktop.scm)

Both are a possiblity for broken bluetooth by the looks of it.

-- 
Pagarbiai,
Ignas Lapėnas


  reply	other threads:[~2024-11-24 10:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-16 10:39 How to diagnose Bluetooth trouble? Daniel Hatton
2024-11-18  7:57 ` Ignas Lapėnas
2024-11-18  9:53   ` Daniel Hatton
2024-11-18 11:35     ` Ignas Lapėnas
2024-11-18 13:48       ` Daniel Hatton
2024-11-18 14:15         ` Ignas Lapėnas
2024-11-20 13:02           ` Daniel Hatton
2024-11-21 12:13             ` Daniel Hatton
2024-11-21 12:37               ` Ignas Lapėnas
2024-11-21 18:26                 ` Daniel Hatton
2024-11-24 10:53                   ` Ignas Lapėnas [this message]
2024-11-27 10:51                     ` How to diagnose Bluetooth trouble? SOLVED Daniel Hatton
2024-11-27 11:34                       ` Ignas Lapėnas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871pz0ewd1.fsf@lapenas.dev \
    --to=ignas@lapenas.dev \
    --cc=dan.hatton@btinternet.com \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.