From: Marcel Holtmann <marcel@holtmann.org>
To: Creative Monsters <lta@creativemonsters.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] pand Connection refused(111) when connecting to a Belkin NAP
Date: Tue, 22 Feb 2005 01:15:23 +0100 [thread overview]
Message-ID: <1109031323.7626.81.camel@pegasus> (raw)
In-Reply-To: <420F483D.20802@creativemonsters.com>
Hi,
> I'm not sure why the 'Segfault' happens, or what to do to check
> it. :-s
>
>
> Version-wise, I'm running...
>
>
> ( i ) bluez-pin-0.23-3
>
> ( ii ) bluez-hcidump-1.11-1
>
> ( iii ) bluez-libs-2.10-2
>
> ( iv ) bluez-bluefw-1.0-6
>
> ( v ) bluez-utils-2.10-2
>
>
> ... on the 64-bit version of Fedora Core 3 ( I'm running an AMD64 ).
install the latest version of these packages.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-02-22 0:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-08 23:42 [Bluez-devel] pand Connection refused(111) when connecting to a Belkin NAP lta
2005-02-09 0:13 ` Marcel Holtmann
[not found] ` <420F483D.20802@creativemonsters.com>
2005-02-22 0:15 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-21 20:48 Dave Henriksen
2004-01-21 19:56 ` Marcel Holtmann
[not found] ` <1074719150.2980.9.camel@linux.local>
2004-01-21 20:14 ` Marcel Holtmann
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=1109031323.7626.81.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=lta@creativemonsters.com \
/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 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.