From: "Stefan Michaelis" <stefan.michaelis@gmx.de>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] hid2hci segementation fault at boot time
Date: Thu, 1 Sep 2005 11:28:42 +0200 (MEST) [thread overview]
Message-ID: <27820.1125566922@www47.gmx.net> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="us-ascii", Size: 1330 bytes --]
Dear all,
I own a Logitech Bluetooth Desktop keyboard and mouse. I wanted to use the
Logitech dongle to additionally connect my Bluetooth headset to the PC for
Skype voice calls.
So far no problems, modules and demons load fine, switched the Logitech
dongle to bluetooth mode via hid2hci.
To automate this process during boot time I enabled the bluetooth.init
script. The demons and modules still load fine, but hid2hci crashes with a
segmentation fault. When I run the init script after bootup as superuser
everything goes fine.
Any idea where is the difference or what I am doing wrong?
Running Suse 9.1 with a vanilla kernel 2.6.12.4. Tried the last three
releases of Bluez.
Regards
Stefan
--
5 GB Mailbox, 50 FreeSMS http://www.gmx.net/de/go/promail
+++ GMX - die erste Adresse für Mail, Message, More +++
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2005-09-01 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-01 9:28 Stefan Michaelis [this message]
2005-09-01 18:20 ` [Bluez-devel] hid2hci segementation fault at boot time Brad Midgley
2005-09-05 12:01 ` Marcel Holtmann
2005-09-26 8:58 ` Charles Majola
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=27820.1125566922@www47.gmx.net \
--to=stefan.michaelis@gmx.de \
--cc=bluez-devel@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 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 NNTP newsgroup(s).