[Bug 285227] New: bluetooth devices still not usable - Alpha 5
https://bugzilla.novell.com/show_bug.cgi?id=285227 Summary: bluetooth devices still not usable - Alpha 5 Product: openSUSE 10.3 Version: Alpha 5 Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: clarkt@cnsp.com QAContact: qa@suse.de Found By: Beta-Customer Created an attachment (id=146876) --> (https://bugzilla.novell.com/attachment.cgi?id=146876) copy of the crash report from kbluetooth Clean install of Alpha 5 to retest bluetooth devices (mouse) after bug 283260 was closed. Trying to use Kbluetooth to connect to an input device results in a crash of that segment of the program. In trying the Gnome version, it knows that the bluetooth adapter is present but has no way to connect to devices. -- 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=285227#c1 --- Comment #1 from Clark Tompsett <clarkt@cnsp.com> 2007-06-18 10:58:37 MST --- Created an attachment (id=146877) --> (https://bugzilla.novell.com/attachment.cgi?id=146877) segment from dmesg showing identification of the usb bluetooth adapter -- 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=285227#c2 Jiri Dluhos <jdluhos@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kernel-maintainers@forge.provo.novell.com Status|NEW |NEEDINFO Info Provider| |clarkt@cnsp.com --- Comment #2 from Jiri Dluhos <jdluhos@novell.com> 2007-07-02 04:49:36 MST --- Please attach the output of 'hwinfo --bluetooth' and the contents of '/var/log/messages'. Adding CC to kernel developers so they can ask more specific questions. -- 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=285227 Patrick Kirsch <pkirsch@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |kde-maintainers@suse.de |screening@forge.provo.novell| |.com | Status|NEEDINFO |NEW Info Provider|clarkt@cnsp.com | -- 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=285227 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kde-maintainers@suse.de |dgollub@novell.com -- 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=285227#c3 Daniel Gollub <dgollub@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|kernel- |tpatzig@novell.com |maintainers@forge.provo.nove| |ll.com | Status|NEW |ASSIGNED --- Comment #3 from Daniel Gollub <dgollub@novell.com> 2007-07-02 10:16:10 MST --- I'm quite sure it's only a problem of kdebluetooth and the new kinputwizard. The kinputwizard is still quite experimental. Could you install kdebluetooth-debuginfo and try to reproduce the crash with kdebluetooth and the kinputwizard. The attached backtrack is less usefull without debugging symbols. CC'ing Tom - the author of kinputwizard. Tom, we should try to fix this crash before we do a kdebluetooth 1.0 beta4 release. I'll provide a build of the latest version kdebluetooth later - to see if this got already fixed. -- 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=285227#c4 --- Comment #4 from Clark Tompsett <clarkt@cnsp.com> 2007-07-02 10:44:34 MST --- There is no debug package in the Factory repository for KDEBluetooth. -- 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=285227#c5 Tom Patzig <tpatzig@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #5 from Tom Patzig <tpatzig@novell.com> 2007-07-04 14:48:59 MST --- We've build a new package. http://software.opensuse.org/download/home:/tpatzig/openSUSE_Factory/i586/kd... Just give it a try. The kinputwizard wont crash anymore. But it is still experimental. So you may find sometimes issues, that the connect to the device won't work properly. -- 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=285227#c6 --- Comment #6 from Clark Tompsett <clarkt@cnsp.com> 2007-07-04 16:03:46 MST --- That's a 32 bit package. I'm running 64bit. -- 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=285227#c7 --- Comment #7 from Clark Tompsett <clarkt@cnsp.com> 2007-07-04 16:31:23 MST --- Created an attachment (id=149721) --> (https://bugzilla.novell.com/attachment.cgi?id=149721) input crash dump -- 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=285227#c8 --- Comment #8 from Clark Tompsett <clarkt@cnsp.com> 2007-07-04 16:32:52 MST --- Created an attachment (id=149723) --> (https://bugzilla.novell.com/attachment.cgi?id=149723) config crash dump Grabbed the src package and rebuilt as a 64bit. It crashes if you select input or configure. Crash dumps attached. -- 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=285227#c9 --- Comment #9 from Tom Patzig <tpatzig@novell.com> 2007-07-05 05:51:59 MST --- sorry for linking to the wrong package. The 64bit package is also in buildservice, so you didn't need to build it your own. http://software.opensuse.org/download/home:/tpatzig/openSUSE_Factory/x86_64/... -- 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=285227#c10 --- Comment #10 from Tom Patzig <tpatzig@novell.com> 2007-07-05 08:19:36 MST --- The problem, because the inputwizard crashes, causes when you select setup without having selected an remote Device. I have fixed the problem, now there will be a popup message telling you to select a device to go further. The new build package: http://software.opensuse.org/download/home:/tpatzig/openSUSE_Factory/x86_64/... -- 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=285227#c11 --- Comment #11 from Clark Tompsett <clarkt@cnsp.com> 2007-07-05 09:12:41 MST --- Created an attachment (id=149880) --> (https://bugzilla.novell.com/attachment.cgi?id=149880) hciscan output Kdebluetooth does not see any devices when you attempt to add device. Output from hcidump attached. -- 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=285227#c12 --- Comment #12 from Clark Tompsett <clarkt@cnsp.com> 2007-07-05 09:13:49 MST --- Created an attachment (id=149881) --> (https://bugzilla.novell.com/attachment.cgi?id=149881) output from hcitool Using hcitool with scan option. Bluetooth mouse is seen. -- 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=285227#c13 Clark Tompsett <clarkt@cnsp.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #13 from Clark Tompsett <clarkt@cnsp.com> 2007-07-11 09:28:56 MST --- Latest kde updates in 10.2 have the same issue as alpha 5 -- 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=285227#c14 --- Comment #14 from Tom Patzig <tpatzig@novell.com> 2007-08-04 08:13:46 MST --- the latest kdebluetooth package includes a lot of bugfixes, especially in the kinputwizard. So please test it and let me know if the issue still occurs: http://download.opensuse.org/repositories/home:/tpatzig/openSUSE_Factory/x86... Please make sure that you have bluez-utils and bluez-libs >= 3.13 -- 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=285227 Tom Patzig <tpatzig@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|dgollub@novell.com |tpatzig@novell.com Status|REOPENED |ASSIGNED -- 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=285227#c15 --- Comment #15 from Clark Tompsett <clarkt@cnsp.com> 2007-08-04 17:11:06 MST --- Tried the new kdebluetooth. Still not able to detect bluetooth mouse. Selecting add device, bluetooth adapter flashes, mouse is in detect mode. Mouse does not appear in the list. Blue-utils 3.15. -- 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=285227#c16 --- Comment #16 from Tom Patzig <tpatzig@novell.com> 2007-08-06 04:08:18 MST --- Ok. But the wizard does not crash anymore, when searching for devices. So u also can test to look for your device with "hcitool scan" if the device is found there, then maybe the inputwizard does not detects your mouse as input device (major class). If hcitool scan finds your device you can also use kbluemon to detect remote devices. In the kinputwizard you also can start the search again.So maybe press the connect button of your mouse for some seconds longer and search again. If the device can't be found by any of these tools, you have to check your device (battery status). bluez-utils 3.15 ... there is no such release yet. The latest bluez-utils version is 3.13, related to bluez.org/download.html ?! -- 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=285227#c17 --- Comment #17 from Clark Tompsett <clarkt@cnsp.com> 2007-08-11 14:29:09 MST --- In beta 1, kbluetooth still does not find the bluetooth mouse. When you select input device, add device, it searches but nothing is found. The search box at the bottom is gray out all the time. -- 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=285227#c18 --- Comment #18 from Tom Patzig <tpatzig@novell.com> 2007-08-13 02:13:04 MST --- The Search button stays disabled if there is no signal DiscoveryComleted thrown. So i think the search didn't started right. Please check the other tools i mentioned (hcitootl scan, kbluemon) to find your remote device, if they also didn't find your mouse, it must be a problem with your BT adapter. -- 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=285227 Tom Patzig <tpatzig@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Normal Status|ASSIGNED |NEEDINFO Info Provider| |clarkt@cnsp.com -- 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=285227#c19 --- Comment #19 from Clark Tompsett <clarkt@cnsp.com> 2007-08-13 19:08:24 MST --- Created an attachment (id=157220) --> (https://bugzilla.novell.com/attachment.cgi?id=157220) output from hcitool scan hcitool scan saw the mouse. Output attached. Kbluemon did not see anything. Scanning button was grayed out. In cups, I can see and connect to a bluetooth printer 20 feet away. No problem printing to it in 10.3 B1. -- 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=285227#c20 --- Comment #20 from Tom Patzig <tpatzig@novell.com> 2007-08-22 08:57:51 MST --- so there must be a problem with starting the Discovery Methods on your BT adapter. I've included a statusbar in kbluemon and kinputwizard to show a message, if the DiscoverDevices method is succesfully called. There will be no error message, when it failes to start the method, except in kbluemon, there the start of the PeriodicDiscovery shows you also errors, within calling the method. So please checkout kinputwizard with this version and have a look onthe statusbar, if there is displayed a message. http://download.opensuse.org/repositories/home:/tpatzig/openSUSE_Factory/x86... -- 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=285227#c21 --- Comment #21 from Clark Tompsett <clarkt@cnsp.com> 2007-08-22 18:13:56 MST --- Pulled the blues 3.14 files from factory and your test program. When I select add device, now kinputmethod searches and sees the mouse. The search button is now black and is usable. I can then connect and attach to the mouse and it will work. I will need to do additional tests, as it appears that I may have to reconnect to the mouse each time the machine is booted. In 10.2 once the login screen is presented, all I have to do is press any button on the mouse and it's reconnected and ready to use. This may not be the same behaver in 10.3. This looks really good. -- 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=285227#c22 --- Comment #22 from Clark Tompsett <clarkt@cnsp.com> 2007-08-22 19:11:53 MST --- On a clean boot with the adapter pluged in, upon logging in kbluetooth crashes. You have to do a rcbluetooth restart and restart kbluetooth. Then clicking on a button on the mouse will restore the connection. On a clean boot with the adapter out, after logging in and then inserting the bluetooth adapter, kbluetooth displays a message about no bluetooth adapter found and exits. You then have to run rcbluetooth restart and restart kbluetooth. Just restarting kbluetooth results in the same message about no adapter found and exits. Pressing a mouse button will re-establish the connection and the mouse works. -- 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=285227#c23 --- Comment #23 from Tom Patzig <tpatzig@novell.com> 2007-08-28 01:58:11 MST --- Yes.I know about that problem.Kbluetooth checks on startup wether there is an adapter or not(or hcid running or not), because no adapter kbluetooth would crash.. The problem is, that in the yast BT module bt is disabled this means that the option in your hcid.conf START_SERVICES is set to no.This option says, when an adapter is plugged in start the hcid, which would be the best soulution. So there is already a bug for our yast team to enable this default. So for you just enable bt in the yast module or set the option in the hcid.conf. But am glad that your mouse seems to work. ;) -- 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=285227#c24 --- Comment #24 from Clark Tompsett <clarkt@cnsp.com> 2007-08-28 05:20:01 MST --- Last night (late) I was checking and during the install I had set bt to start. When I checked the runlevels, it was not starting. Once I changed that, the crash's in kbluetooth stopped. This is not the first item I found that I selected to start on boot during the installation. I'll run additional testing but it looks like that was the problem. -- 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=285227#c25 --- Comment #25 from Clark Tompsett <clarkt@cnsp.com> 2007-08-28 18:36:57 MST --- Have your changes made it into factory? I just tried the 1.2 version from your directory to text and now the mouse is not seen. The 1.1 did work. -- 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=285227#c26 --- Comment #26 from Tom Patzig <tpatzig@novell.com> 2007-09-10 05:48:52 MST --- in the earlier revisions there were some major bugs in the libkbluetooth. Some methods made use of possibly empty char pointers. So maybe this is also an effect of your unstable behavior. Please check the new release: http://download.opensuse.org/repositories/home:/tpatzig/openSUSE_Factory/x86... -- 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=285227#c27 --- Comment #27 from Clark Tompsett <clarkt@cnsp.com> 2007-09-10 09:35:43 MST --- Still no go in B3 (32 and 64 bit). When trying to connect to mouse, the search button is grayed out, the bluetooth icon is flashing, dongle is flashing and the mouse is responding, but no connection is established. -- 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=285227#c28 --- Comment #28 from Tom Patzig <tpatzig@novell.com> 2007-09-11 04:25:56 MST --- The inputwizard only lists new devices, when the device isn't already configured as inputdevice (listed in the ListView above). So when your mouse is already in this list the wizard won't find it again. When the search button is grayed out, the whole time, it seems, that the search didn't starts properly. When it starts succesfully, there must be a status message in the statusbar ("Discovery Started"). To restrat the search you can either restart the wizard or just toggle the extension button ("Add new Devices"). -- 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=285227#c29 --- Comment #29 from Clark Tompsett <clarkt@cnsp.com> 2007-09-11 05:26:30 MST --- I did a clean install of b3. The mouse is not in the list. Restarting add new devices still does not find the mouse. I can see the bluetooth adapter on the printer fine, but no input devices. -- 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=285227#c30 --- Comment #30 from Clark Tompsett <clarkt@cnsp.com> 2007-09-11 07:29:04 MST --- Kbluetooth appears not to be using the bluetooth drivers. I turned off bluetooth, rcbluetooth stop. Kbluetooth still talks to the adapter and the mouse but cannot see anything. Also, 1) you cannot turn bluetooth on during the install. Setting bluetooth to be active during the install results in it being left disabled. 2) Selecting devices from kbluetooth and changing values from connectable to discover does not stick. It continues to default to base values. 3) please provide manual instructions on how to do manual connects using hci since the method used with hidd is no longer viable. -- 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=285227#c31 --- Comment #31 from Tom Patzig <tpatzig@novell.com> 2007-09-11 08:39:32 MST --- if you stop the hcid, when kbluetooth is running and then try to start a bt app using bluez methods it would definitely crash. have you installed the new rpms after your fresh install, i posted in comment #26 (this is the newest package) to 1) the issues with bluetooth within the installation procedure are known. If you have plugged in a dongle while installation then the hcid gets started via yast and is running after installation. If your dongle is a hid dongle you also can use your bt mouse in the installation procedure.Other bluetooth features within the installation process are not yet implemented. to 2) All methods in the kbluetooth framework are send over dbus to the org.bluez backend, provided by the hcid. To test if a method is succesfull or not you can install bluez-test and use the tool apitest (in this example "apitest GetMode") to see if the method was successfully called. If the methods do not behave as they should it can also be a problem with you're adapter to 3) the new kbluetooth framework is everything else than complete.And as a fully rewrite of kbluetoothd, with the usage of the bluez dbus api it is a step in the right direction, but surely not yet stable enough. To manually connect to your mouse you must yous the dbus methods (e.g with dbus-send) therefore have a look in the inputwizard.cpp -- 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=285227#c32 --- Comment #32 from Clark Tompsett <clarkt@cnsp.com> 2007-09-11 08:53:27 MST --- I tried the latest version you made with no results. We're at the point of needing a debug version. I took your sources and did a configure --enable-debug=yes but I cannot find where the debug messages are. We're going around and around on this.. so getting debug output is the only way to solve this. -- 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=285227#c33 --- Comment #33 from Tom Patzig <tpatzig@novell.com> 2007-09-11 09:02:54 MST --- Yes good idea.to build the source on youre own do a: configure --enable-debug=full --disable-final Then you should see the debug msgs. -- 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=285227#c34 --- Comment #34 from Clark Tompsett <clarkt@cnsp.com> 2007-09-11 09:49:27 MST --- Configured as you stated, did the make and make install. No messages displayed and I don't know the name of the log file or it's location. -- 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=285227#c35 --- Comment #35 from Tom Patzig <tpatzig@novell.com> 2007-09-11 10:08:12 MST --- no you do not need to install it.just change in the kdebluetooth/kdebluetooth/kinputwizard and start the binary from there with :./kinputwizard --nofork -- 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=285227#c36 --- Comment #36 from Clark Tompsett <clarkt@cnsp.com> 2007-09-11 10:41:22 MST --- No output in the term window. -- 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=285227#c37 --- Comment #37 from Tom Patzig <tpatzig@novell.com> 2007-09-11 12:45:12 MST --- you maybe have to enabele the kdebug output. kdebugdialog --fullmode Set each combobox to shell. To see if the Discovery Process has started right you an also do the following: 1. rcbluetooth stop 2. hcid -xnsf /etc/bluetooth/hcid.conf 3. restart kbluetooth and try to find your mouse with the inputwizard (when the wizard searches have a look at the debug output of the hcid) -- 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=285227#c38 --- Comment #38 from Clark Tompsett <clarkt@cnsp.com> 2007-09-11 18:30:25 MST --- Created an attachment (id=163395) --> (https://bugzilla.novell.com/attachment.cgi?id=163395) output from hcid --not much information. -- 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=285227#c39 --- Comment #39 from Tom Patzig <tpatzig@novell.com> 2007-09-12 11:27:09 MST --- if you like, you can test the new release (some library fixes) http://download.opensuse.org/repositories/home:/tpatzig/openSUSE_Factory/x86... or http://download.opensuse.org/repositories/home:/tpatzig/openSUSE_Factory/i58... -- 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=285227#c40 --- Comment #40 from Clark Tompsett <clarkt@cnsp.com> 2007-09-15 21:50:30 MST --- I've spent the last several days testing several configurations. 1) B2 updated to B3 via factory. Bluetooth fails even with your latest test files. 2) B2 updated to B3 via update from cd. Same results as 1. 3) Clean install of B3 from kde cd. Bluetooth works in both 32/64 with kbluetooth from the cd. Tested finding the mouse, connecting, deleting the mouse and re-discovering and connecting. It work each time. Trying you last set of files showed that the connect button did not appear to connect in the same manor as the version delivered on the cd. Based on the tests, it looks like by updating from factory or from the cd results in a file(s) not properly being updated (unknown which one(s)). If B4 shows the same results as B3 then this issue should be fixed. -- 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=285227#c41 Stephan Kulow <coolo@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|clarkt@cnsp.com | --- Comment #41 from Stephan Kulow <coolo@novell.com> 2007-11-22 12:33:43 MST --- looks like info is provided -- 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=285227 User tpatzig@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=285227#c42 Tom Patzig <tpatzig@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #42 from Tom Patzig <tpatzig@novell.com> 2008-09-22 10:21:09 MDT --- There is a new default kde bluetooth app available (kdebluetooth4-0.2). Due to that bugs are not (yet :) ) found in kdebluetooth4 i close this report. -- 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.
participants (1)
-
bugzilla_noreply＠novell.com