From: Daniel Hatton <dan.hatton@btinternet.com>
To: GUIX help list <help-guix@gnu.org>
Subject: Re: How to diagnose Bluetooth trouble? SOLVED
Date: Wed, 27 Nov 2024 10:51:55 +0000 [thread overview]
Message-ID: <5e091640-254b-4c5d-852e-c9b1f21ab40e@btinternet.com> (raw)
In-Reply-To: <871pz0ewd1.fsf@lapenas.dev>
[-- Attachment #1.1: Type: text/plain, Size: 883 bytes --]
On 24/11/2024 10:53, Ignas Lapėnas wrote:
> Noticed that you're using bluetooth-service instead of
> bluetooth-service-type in services:
> 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.
Wahay! Edited config.scm as shown below, and now not only does
Bluetooth work, it actually starts at boot time. Thanks very much.
$ rcsdiff -r1.3.1.2.2.7 config.scm
===================================================================
RCS file: RCS/config.scm,v
retrieving revision 1.3.1.2.2.7
diff -r1.3.1.2.2.7 config.scm
56c56
< (bluetooth-service #:auto-enable? #t)
---
> (service bluetooth-service-type)
59d58
< (service pulseaudio-service-type)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2024-11-27 10:59 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
2024-11-27 10:51 ` Daniel Hatton [this message]
2024-11-27 11:34 ` How to diagnose Bluetooth trouble? SOLVED 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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5e091640-254b-4c5d-852e-c9b1f21ab40e@btinternet.com \
--to=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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).