public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: bluez 5 not connecting
Date: Wed, 28 May 2014 23:28:34 +0100	[thread overview]
Message-ID: <201405282329.03803.michaelkintzios@gmail.com> (raw)
In-Reply-To: <538632C5.9090908@gentoo.org>

[-- Attachment #1: Type: Text/Plain, Size: 551 bytes --]

On Wednesday 28 May 2014 20:02:29 Samuli Suominen wrote:
> On 28/05/14 21:42, Mick wrote:
> > Hmm ... am I alone in this quest?
> 
> See here, http://bugs.gentoo.org/show_bug.cgi?id=505362

Thanks!  I missed this bug when I glanced earlier.  However, it does not 
mention rfcomm is now missing, or the fact that the gentoo rc script fails to 
initialise bluethooth and complains about rfcomm service not having 
started/exist, or that bluetoothctl now does not work at all.  Is all this 
down to a missing udev rule?

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2014-05-28 22:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-23  9:13 [gentoo-user] bluez 5 not connecting William Kenworthy
2014-04-23 11:59 ` covici
2014-04-23 12:48   ` William Kenworthy
2014-04-23 13:26     ` covici
2014-04-23 17:06 ` [gentoo-user] " James
2014-04-24  1:11   ` William Kenworthy
2014-04-26 18:33     ` Mick
2014-04-27  3:14       ` William Kenworthy
2014-04-27  7:27         ` William Kenworthy
2014-05-28 18:42           ` Mick
2014-05-28 19:02             ` Samuli Suominen
2014-05-28 22:28               ` Mick [this message]
2014-05-28 23:05                 ` William Kenworthy
2014-05-29  6:27                   ` Mick
2014-05-29 10:18                     ` Mick
2014-05-29 22:32                       ` William Kenworthy
2014-05-30  5:34                         ` Mick
2014-06-01 19:20                           ` Mick

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=201405282329.03803.michaelkintzios@gmail.com \
    --to=michaelkintzios@gmail.com \
    --cc=gentoo-user@lists.gentoo.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