From: Brad Smith <bgsmith@bendcable.com>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Lost connections - mouse and keyboard
Date: Wed, 28 Nov 2007 19:03:46 -0800 [thread overview]
Message-ID: <1196305426.23029.12.camel@pico> (raw)
In-Reply-To: <1196056187.4217.54.camel@aeonflux>
[-- Attachment #1.1: Type: text/plain, Size: 2548 bytes --]
Thank you for the reply Marvel. I use the gnome bluetooth client which
apparently does manage bluetooth devices using bluetooth-input-service.
I still have the problem of the devices disappearing if idle for too
long such as when i lock the desktop or log out for a long period.
Sometimes I can re-enable the devices, but sometimes I cannot. This is
frustrating.
I see a the following several times in the system log if i restart
bluetooth:
Nov 28 18:53:39 pico kernel: WARNING: at drivers/hid/hid-core.c:784
implement() (Tainted: P )
Nov 28 18:53:39 pico kernel:
Nov 28 18:53:39 pico kernel: Call Trace:
Nov 28 18:53:39 pico kernel: [<ffffffff811d8549>] hid_output_report
+0x1c5/0x232
Nov 28 18:53:39 pico kernel: [<ffffffff811ddaf1>] hid_submit_ctrl
+0x60/0x24b
Nov 28 18:53:39 pico kernel: [<ffffffff811dde45>] usbhid_submit_report
+0x169/0x19e
Nov 28 18:53:39 pico kernel: [<ffffffff811e030b>] hiddev_ioctl
+0x368/0x919
Nov 28 18:53:39 pico kernel: [<ffffffff810f54c5>] inode_has_perm
+0x65/0x72
Nov 28 18:53:39 pico kernel: [<ffffffff81120c17>] __up_read+0x19/0x7f
Nov 28 18:53:39 pico kernel: [<ffffffff8125eecc>] do_page_fault
+0x490/0x7e4
Nov 28 18:53:39 pico kernel: [<ffffffff810a7399>] do_ioctl+0x55/0x6b
Nov 28 18:53:39 pico kernel: [<ffffffff810a75f2>] vfs_ioctl+0x243/0x25c
Nov 28 18:53:39 pico kernel: [<ffffffff810a7664>] sys_ioctl+0x59/0x79
Nov 28 18:53:39 pico kernel: [<ffffffff8100bd45>] tracesys+0xd5/0xda
Brad
On Mon, 2007-11-26 at 06:49 +0100, Marcel Holtmann wrote:
> Hi Brad,
>
> > I have a Logitech mouse and keyboard that use bluetooth (dinovo). I
> > have enabled bluetooth on this Fedora 8 system and both work well with
> > two problems.
> >
> > (1) When I lock the system and return later the mouse no longer works.
> > I have to open a terminal window and issue an hidd --connect command.
> >
> > (2) When I log out, both the mouse and keyboard stop working. I have to
> > connect a USB mouse and USB keyboard to enter the authentication
> > information. Once logged in the bluetooth devices usually work,
> > although I sometimes have to issue an hidd --connect command to enable
> > the keyboard.
> >
> > Any suggestions on resolving these issues would be appreciated.
>
> not using hidd and using bluetoothd-input-service instead is one thing.
> For input devices to re-connect you have to have a daemon running that
> handles this. The input service is the best way to achieve this. Check
> the BlueZ wiki for details.
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 309 bytes --]
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-11-29 3:03 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-25 16:43 [Bluez-users] Lost connections - mouse and keyboard Brad Smith
2007-11-26 5:49 ` Marcel Holtmann
2007-11-29 3:03 ` Brad Smith [this message]
2007-11-29 8:06 ` Dave Young
2007-11-29 20:19 ` Marcel Holtmann
2007-11-29 20:43 ` Jiri Kosina
2007-11-30 1:06 ` Dave Young
2007-11-30 9:15 ` Jiri Kosina
2007-12-07 23:42 ` Didier Link
2007-12-08 10:25 ` Fabrice Ménard
2007-12-08 12:57 ` Didier Link
2007-12-09 16:45 ` Fabrice Ménard
2007-12-10 12:36 ` Didier Link
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=1196305426.23029.12.camel@pico \
--to=bgsmith@bendcable.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox