https://bugzilla.novell.com/show_bug.cgi?id=301780#c2 Marcus Schaefer changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |lslezak@novell.com Summary|Bluetooth mouse get's connected, but no |sax2: bluetooth mouse get's connected, but no |mousepointer in X |mousepointer in X --- Comment #2 from Marcus Schaefer 2007-08-20 07:40:30 MST --- I don't know if a bluetooth device (mouse) needs a yast2 configuration first. Maybe Ladislav Slezak can answer this question -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=301780#c4 Marcus Schaefer changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|ms@novell.com |bnc-team-screening@forge.provo.novell.com --- Comment #4 from Marcus Schaefer 2007-08-20 08:46:55 MST --- that's what I thought as well -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=301780#c6 Stefan Seyfried changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tpatzig@novell.com --- Comment #6 from Stefan Seyfried 2007-08-23 08:50:12 MST --- The Yast bluetooth module needs to have bluetooth support enabled. This is the case here. Then you can connect the mouse with the inputwizard (either by clicking through kdebluetooth menu or by starting /opt/kde3/bin/kinputwizard Once the window appears, you click on "Add new devices" and press the connect button on the mouse for a second or two. The mouse should now be found. Select it and then click "Setup". You should get a final confirmation window asking "Do you want to allow mouse $FOO to connect?", select "yes". After that it is "just working". At least for me (i tried it right now as i am typing this). :-) Technically, a new input device shows up in /proc/bus/input/devices: I: Bus=0005 Vendor=046d Product=b003 Version=4310 N: Name="Logitech MX1000 mouse" P: Phys=00:50:F2:EA:6B:EF S: Sysfs=/class/input/input17 U: Uniq=00:07:61:3F:1B:6D H: Handlers=mouse2 event6 B: EV=7 B: KEY=ffff0000 0 0 0 0 0 0 0 0 B: REL=143 which should, AFAIK, just be handled by X's generic mouse driver. Adding Tom Patzig, the author of the input wizard, to CC. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=301780#c8 Fred van Zwieten changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|fvzwieten@vxcompany.com | Resolution| |FIXED --- Comment #8 from Fred van Zwieten 2007-08-24 04:33:56 MST --- OK, seife's instructions worked (i'm running beta2 now btw). I'd like to add a little to it. After doing this it popped up a authorization dialog. I choose " always accept" and off it went :-) Thanx guys Btw: Beta2 looking good, except for the 3945 wireless wars :-( -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.