public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Mario Limonciello <mario_limonciello@dell.com>
To: Bastien Nocera <hadess@hadess.net>
Cc: marcel@holtmann.org, artem@makhutov.org, linux-bluetooth@vger.kernel.org
Subject: Re: bluetoothd not starting at boot with udev
Date: Mon, 13 Jul 2009 11:15:05 -0500	[thread overview]
Message-ID: <4A5B5D89.8020205@dell.com> (raw)
In-Reply-To: <1247418647.5460.3.camel@snoogens.fab.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 749 bytes --]

Hi Bastien:

Bastien Nocera wrote:
> On Sat, 2009-07-11 at 18:26 -0500, Mario_Limonciello@Dell.com wrote:
>   
>
> Your udev scripts are missing a call to "udevadm trigger --retry-failed"
>
> Cheers
>   
Currently in the Ubuntu udev init script there is a call to 'udevadm
trigger' (without any arguments).  Without any arguments it appears the
default is "--type=devices".  When I add --type=failed (--retry-failed
is deprecated), the system fails to boot up to X.  If I return it back
to it's old state and add a second call right afterward of
"--type=failed", there is no difference in behavior.  bluetoothd still
fails to spawn by the udev rule.
-- 
Mario Limonciello
*Dell | Linux Engineering*
mario_limonciello@dell.com


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2009-07-13 16:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-11 16:10 bluetoothd not starting at boot with udev Artem Makhutov
2009-07-11 18:40 ` Marcel Holtmann
2009-07-11 23:26   ` Mario_Limonciello
2009-07-12 17:10     ` Bastien Nocera
2009-07-13 16:15       ` Mario Limonciello [this message]
2009-07-13 23:07         ` Mario Limonciello
2009-07-14  4:30           ` Bastien Nocera
  -- strict thread matches above, loose matches on Subject: below --
2009-07-14 16:08 Mario Limonciello

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=4A5B5D89.8020205@dell.com \
    --to=mario_limonciello@dell.com \
    --cc=artem@makhutov.org \
    --cc=hadess@hadess.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.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