From: Carl K <carl@personnelware.com>
To: Bluez-users@lists.sourceforge.net
Subject: [Bluez-users] seg fault in rfcomm
Date: Fri, 09 Jun 2006 05:00:23 -0500 [thread overview]
Message-ID: <448946B7.6000002@personnelware.com> (raw)
carl@asus17:~$ sudo hcitool scan
Scanning ...
08:00:37:03:EF:36 PM325 by LG
carl@asus17:~$ sudo rfcomm connect 0 08:00:37:03:EF:36 4
Connected /dev/rfcomm0 to 08:00:37:03:EF:36 on channel 4
Press CTRL-C for hangup
Segmentation fault
carl@asus17:~$
I was connected with minicom, did a ^AQ (exit without resetting the modem)
just tried again, no probmem.
Carl K
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2006-06-09 10:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 10:00 Carl K [this message]
2006-06-09 10:12 ` [Bluez-users] seg fault in rfcomm Marcel Holtmann
2006-06-09 10:22 ` Carl K
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=448946B7.6000002@personnelware.com \
--to=carl@personnelware.com \
--cc=Bluez-users@lists.sourceforge.net \
/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.