ubuntu 8.04 and Asu 2008.12 fail

[GoogleCodeExporter]

#What steps will reproduce the problem?
1. Installed remoko-server and remoko with dependencies
2. start bluetooth in Openmoko (through the menu AND /etc/init.d/bluetooth
start)
3. scan on Ubuntu for the device, find it and run sudo hidd --connect
00:06:6E:17:2C:B3

#What is the expected output? What do you see instead?

Ubuntu gives me "HID create error 77 (File descriptor in bad state)

This is what remoko gives me:
root@om-gta02:~# DISPLAY=:0 remoko
dbus_objectInit...
could not create proxy for org.openmoko.accelg
es:/org/openmoko/accelges/Recognizer org.freed
esktop.DBus.Error.ServiceUnknown: The name org
.openmoko.accelges was not provided by any .se
rvice files
error in proxy
failcount= 0
dbus_objectInit...
could not create proxy for org.freesmartphone.
ousaged:/org/freesmartphone/Usage org.freedesk
top.DBus.Error.ServiceUnknown: The name org.fr
eesmartphone.ousaged was not provided by any .
service files
failcount= 1
dbus_objectInit...
could not create proxy for org.freesmartphone.
ousaged:/org/freesmartphone/Usage org.freedesk
top.DBus.Error.ServiceUnknown: The name org.fr                            
 eesmartphone.ousaged was not provided by any .                           
  service files
failcount= 1
dbus_objectInit...
on
You are using ASU
passou
Stopping Bluetooth subsystem: hcid.
Starting Bluetooth subsystem: hcid hid2hci.
initializing daemon ...
initializing listener ...
waiting connection to remoko-server ...
0x0005c0
0x0005c0
Device Class changed to: 0x0005c0
Can't listen on HID control channel: Address already in use
dbus.Array([], signature=dbus.Signature('s'))
ERROR: Bluetooth is off

and then it stops (screen is waiting for connection)

OR Ubuntu gives me "Can't get device information: Success" on connect and
remoko stops to "waiting connection to remoko-server ..."

To mee it looks weird that it says that channel already in use and BT is off.. 

And then finally I got this: 
waiting connection to remoko-server ...
0x0005c0
0x0005c0
Device Class changed to: 0x0005c0
Can't listen on HID control channel: Address already in u                 
                        se
Exception in thread Thread-2:
Traceback (most recent call last):
  File "/usr/lib/python2.5/threading.py", line 486, in __                 
                        bootstrap_inner
    self.run()
  File "/usr/share/remoko/remoko/remoko_server.py", line                  
                        265, in run
    reply = self.remoko.sock.recv(100)
error: (104, 'Connection reset by peer')

(sorry for the messed lines..)

Any tips? Has it been tested on 2008.12 with success? any link to point to
the required steps to run it?

Original issue reported on code.google.com by risto.kurppa@gmail.com on 15 Jan 2009 at 8:10

[GoogleCodeExporter]

I don't tested ReMoko on 2008.12 yet.
The first error that you got in Ubuntu (HID create error 77 (File descriptor in 
bad
state) is probably caused, because you don't have the ReMoko app running on 
device yet.
Which version of bluez-utils do you have on your device ?

Original comment by vdv...@gmail.com on 15 Jan 2009 at 4:27

[GoogleCodeExporter]

I have bluez-utils_3.33-r3_armv4t.opk installed

Ok so the HID thing should not be a problem, just a too quick try.

Original comment by risto.kurppa@gmail.com on 15 Jan 2009 at 5:38

[GoogleCodeExporter]

Humm, I already tested ReMoko with Bluez-utils_3.33, and it worked fine.
Ignore all the other errors, the problem here is this : Can't listen on HID 
control
channel: Address already in use.
This means that the bluetooth input system is running (in order to act as host, 
to
receive BT keyboard connections), but the input service is terminated here: 
"Stopping
Bluetooth subsystem: hcid.".
Try to restart the neo, and start again, first start ReMoko on a shell, then 
try to
connect Ubuntu to it, and paste the output here again. 

Original comment by vdv...@gmail.com on 15 Jan 2009 at 6:12

[GoogleCodeExporter]

OK, so I restarted Freerunner and now, without manually doing anything for 
Bluetooth,
started remoko and got the 'your bluetooth is not on, turn it on yes/no?' 
-message
and pressend yes and tried to scan for the device on Ubuntu but wasn't able to 
find
it. Here's the output of Freerunner:

root@om-gta02:~# DISPLAY=:0 remoko                                       
dbus_objectInit...                                                       
could not create proxy for 
org.openmoko.accelges:/org/openmoko/accelges/Recognizer
org.freedesktop.DBus.Error.ServiceUnknown: The name org.openmoko.accelges was 
not
provided by any .service files                                                  

error in proxy                                                                  

failcount= 0                                                                    

dbus_objectInit...                                                              

could not create proxy for org.freesmartphone.ousaged:/org/freesmartphone/Usage
org.freedesktop.DBus.Error.ServiceUnknown: The name org.freesmartphone.ousaged 
was
not provided by any .service files                                              

failcount= 1                                                                    

dbus_objectInit...                                                              

could not create proxy for org.freesmartphone.ousaged:/org/freesmartphone/Usage
org.freedesktop.DBus.Error.ServiceUnknown: The name org.freesmartphone.ousaged 
was
not provided by any .service files                                              

failcount= 1                                                                    

dbus_objectInit...                                                              

off                                                                             

transition to bluetooth_off_alert                                               

You are using ASU
finished
transition to main
finished
Traceback (most recent call last):
  File "ecore.c_ecore_timer.pxi", line 29, in ecore.c_ecore.timer_cb
(ecore/ecore.c_ecore.c:891)
  File "ecore.c_ecore_timer.pxi", line 91, in ecore.c_ecore.Timer._exec
(ecore/ecore.c_ecore.c:1465)
  File "/usr/share/remoko/remoko/remoko", line 1609, in initialize_remoko_server
    self.connection = Connect()
  File "/usr/share/remoko/remoko/remoko_server.py", line 43, in __init__
    self.input = dbus.Interface(bus_input.get_object('org.bluez',
'/org/bluez/service_input'), 'org.bluez.Service')
  File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 244, in get_object
    follow_name_owner_changes=follow_name_owner_changes)
  File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 241, in __init__
    self._named_service = conn.activate_name_owner(bus_name)
  File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 183, in activate_name_owner
    self.start_service_by_name(bus_name)
  File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 281, in start_service_by_name
    'su', (bus_name, flags)))
  File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 622, in call_blocking
    message, timeout)
DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name org.bluez 
was not
provided by any .service files

Original comment by risto.kurppa@gmail.com on 17 Jan 2009 at 11:29

[GoogleCodeExporter]

Now the D-bus Bluez stuff isn't running, I don't have my freerunner right now
available for test this stack, I will check it in the weekend.
This problem here is that OpenMoko doesn't stabilize the core system, every 
release
the packages changed, this is very bad for me as a programmer and also as a 
user:(

Original comment by vdv...@gmail.com on 20 Jan 2009 at 10:29

[GoogleCodeExporter]

Right.. Yes, it's a pain that things keep changing all the time. Thanks for 
your effort!

Original comment by risto.kurppa@gmail.com on 21 Jan 2009 at 6:49

[GoogleCodeExporter]

Hello, I had the same problem, try to start the hci-daemon with the command hcid
before starting remoko.

wiwa

Original comment by www.w...@gmail.com on 22 Jan 2009 at 12:44

[GoogleCodeExporter]

The Om2008.12 distro have a bug in the D-bus/BlueZ system:
https://docs.openmoko.org/trac/ticket/2218

If you want to try ReMoko right now the only options are Om2008.09 (without 
updates)
and FSO ML4.

Best regards.

Original comment by vdv...@gmail.com on 27 Jan 2009 at 4:58