forked from BackupTheBerlios/lbrc-devel-maillist
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy path2008-January.txt
1830 lines (1541 loc) · 64.7 KB
/
2008-January.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
From matthias.blaesing at rwth-aachen.de Wed Jan 9 10:46:28 2008
From: matthias.blaesing at rwth-aachen.de (Matthias =?ISO-8859-1?Q?Bl=E4sing?=)
Date: Wed, 09 Jan 2008 10:46:28 +0100
Subject: [Lbrc-devel] Error with newer version of python-bluetooth
Message-ID: <1199871988.21886.2.camel@prometheus.glx>
Hello,
There was a problem with newer versions of python-bluetooth (the
version, that recently hit debian unstable). LBRC used a deprecated API
call to determine a free rfcomm channel. I commited a fix for this to
svn and you find the solution attached to this email. So if you
experience crashes at startup this might cure it - if not, where is your
bug report??? ;-)
Greetings
Matthias
--
So long and thanks for all the fish!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: revision221.diff
Type: text/x-patch
Size: 700 bytes
Desc: not available
URL: <https://lists.berlios.de/pipermail/lbrc-devel/attachments/20080109/f51f652f/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
URL: <https://lists.berlios.de/pipermail/lbrc-devel/attachments/20080109/f51f652f/attachment.pgp>
From k at mo.ubal.to Fri Jan 11 03:58:23 2008
From: k at mo.ubal.to (tloudev)
Date: Fri, 11 Jan 2008 03:58:23 +0100 (CET)
Subject: [Lbrc-devel] LBRCdbus --debug output
Message-ID: <Pine.LNX.4.64.0801110216150.24572@poblijon.ubal.to>
hi there,
kino lbrc-0.5 # LBRCdbus --debug
Traceback (most recent call last):
File "/usr/bin/LBRCdbus", line 13, in <module>
brs = Core(debug=logging.DEBUG)
File "/usr/lib/python2.5/site-packages/LBRC/dbusinterface.py", line 195,
in __init__
bus_name = dbus.service.BusName(DBUSNAME, bus=dbus.SessionBus())
File "/usr/lib/python2.5/site-packages/dbus/_dbus.py", line 213, in
__new__
mainloop=mainloop)
File "/usr/lib/python2.5/site-packages/dbus/_dbus.py", line 102, in
__new__
bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 125, in
__new__
bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
dbus.exceptions.DBusException:
org.freedesktop.DBus.Error.Spawn.ExecFailed: Failed to execute dbus-launch
to autolaunch D-Bus session
kino lbrc-0.5 # dbus-launch
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-0xZhPbuZti,guid=ae56e520cd8400329d6d79004786d176
DBUS_SESSION_BUS_PID=14834
I'm using gentoo linux with kernel 2.6.23 and dbus-python 0.82.3
thank you for any help.
Ondrej Pachner
--
Check my PGP public key at http://poblijon.ubal.to/~tloudev/pgp.pub
From matthias.blaesing at rwth-aachen.de Fri Jan 11 12:01:42 2008
From: matthias.blaesing at rwth-aachen.de (Matthias =?ISO-8859-1?Q?Bl=E4sing?=)
Date: Fri, 11 Jan 2008 12:01:42 +0100
Subject: [Lbrc-devel] DBUS Daemon not running (was: Re: LBRC errors)
In-Reply-To: <Pine.LNX.4.64.0801111043530.24572@poblijon.ubal.to>
References: <Pine.LNX.4.64.0801111043530.24572@poblijon.ubal.to>
Message-ID: <1200049302.24740.13.camel@prometheus.glx>
Hello Ondrej,
I will only comment on the problems with the newer bindings (the 0.8
version, as that is the version also present in debian unstable).
This looks like you are trying to run LBRC as root. Firstly: I don't
know why this is so popular, but I would strongly advise against it.
But the basic problem would stay - namely: There is no dbus daemon
running. Or at least it can't be accessed. If no dbus daemon is launched
automaticly - you have to do it yourself (its explained in more detail
in the manual pages of dbus-launch).
dbus-launch will invoke a new session bus and will print the enviroment
variables necessary for the programms, that want to use the bus. You
have to set these variables yourself, as a programm can't modify the
environment of the calling parent.
So you can either run dbus-launch and manually export the variables or
use the shell to help you:
test at prometheus:~$ eval `dbus-launch`
test at prometheus:~$ export DBUS_SESSION_BUS_ADDRESS
test at prometheus:~$ export DBUS_SESSION_BUS_PID
The first command calls dbus-launch and evaluates the output - in this
case it sets environment variables. The next to lines make sure, that
the just set variables are passed down into the environment of child
prozesses.
Hope that helps
Matthias
PS: please keep lbrc-devel as CC - this is a common problem, so another
user might be interested.
Am Freitag, den 11.01.2008, 10:48 +0100 schrieb tloudev:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> hi,
> I'm trying to run LBRC v0.5, but I have several problems runnin LBRCdbus
> with dbus-python >=0.80 the proram exits with:
> kino lbrc-0.5 # LBRCdbus --debug
> Traceback (most recent call last):
> File "/usr/bin/LBRCdbus", line 13, in <module>
> brs = Core(debug=logging.DEBUG)
> File "/usr/lib/python2.5/site-packages/LBRC/dbusinterface.py", line 195,
> in __init__
> bus_name = dbus.service.BusName(DBUSNAME, bus=dbus.SessionBus())
> File "/usr/lib/python2.5/site-packages/dbus/_dbus.py", line 213, in
> __new__
> mainloop=mainloop)
> File "/usr/lib/python2.5/site-packages/dbus/_dbus.py", line 102, in
> __new__
> bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
> File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 125, in
> __new__
> bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
> dbus.exceptions.DBusException:
> org.freedesktop.DBus.Error.Spawn.ExecFailed:
> Failed to execute dbus-launch to autolaunch D-Bus session
>
>
> with dbus-python-0.71:
> kino lbrc-0.5 # LBRCdbus
> Traceback (most recent call last):
> File "/usr/bin/LBRCdbus", line 3, in <module>
> from LBRC.dbusinterface import Core
> File "/usr/lib/python2.5/site-packages/LBRC/dbusinterface.py", line 27,
> in <module>
> class DBUSProfileControl(dbus.service.Object):
> File "/usr/lib/python2.5/site-packages/LBRC/dbusinterface.py", line 33,
> in DBUSProfileControl
> @dbus.service.signal(DBUSIFACE, signature='ss')
> File "/usr/lib/python2.5/site-packages/dbus/decorators.py", line 64, in
> decorator
> sig = tuple(dbus_bindings.Signature(signature))
> File "dbus_bindings.pyx", line 84, in dbus_bindings.SignatureIter.next
> TypeError: exceptions must be strings, classes, or instances, not type
>
> the file dbus_bindings.pyx doesn't exist, there's only dbus_bindings.so
> I'm using gentoo linux with 2.6.23 kernel
> thank you for any help
> Ondrej Pachner
>
>
>
> - --
>
> Check my PGP public key at http://poblijon.ubal.to/~tloudev/pgp.pub
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (GNU/Linux)
>
> iD8DBQFHhztcFM6HvNRuG3ARAleWAKDpv8CVQ3hIhdmoHrPMHDAn9uyy+gCcCCVQ
> 7j0nNYeUMBjJGD6pbsagUkQ=
> =KSA2
> -----END PGP SIGNATURE-----
--
So long and thanks for all the fish!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
URL: <https://lists.berlios.de/pipermail/lbrc-devel/attachments/20080111/79804bee/attachment.pgp>
From k at mo.ubal.to Fri Jan 11 13:09:51 2008
From: k at mo.ubal.to (tloudev)
Date: Fri, 11 Jan 2008 13:09:51 +0100 (CET)
Subject: [Lbrc-devel] DBUS Daemon not running (was: Re: LBRC errors)
In-Reply-To: <1200049302.24740.13.camel@prometheus.glx>
References: <Pine.LNX.4.64.0801111043530.24572@poblijon.ubal.to>
<1200049302.24740.13.camel@prometheus.glx>
Message-ID: <Pine.LNX.4.64.0801111241230.24572@poblijon.ubal.to>
hi Matthias,
so the correct version of the dbus-python should be >=0.80.. OK.
right now it seems much better in this case, but I have another error,
probably between the chair and the keyboard again :-)
O.P.
kino lbrc-0.5 # cat .lbrc.conf
{
"uinputdevice": "/dev/misc/uinput",
"defaultprofile": "nokia_6230i_maus1"
}
kino lbrc-0.5 # LBRCdbus --debug
Traceback (most recent call last):
File "/usr/bin/LBRCdbus", line 13, in <module>
brs = Core(debug=logging.DEBUG)
File "/usr/lib/python2.5/site-packages/LBRC/dbusinterface.py", line 204,
in __init__
self.btserver = BTServer()
File "/usr/lib/python2.5/site-packages/LBRC/BTServer.py", line 185, in
__init__
self.config = config()
File "/usr/lib/python2.5/site-packages/LBRC/config.py", line 42, in
__init__
self.reread()
File "/usr/lib/python2.5/site-packages/LBRC/config.py", line 72, in
reread
self.profile_index.extend([('user', profile_name) for profile_name in
self.user['profiles']])
KeyError: 'profiles'
I'd like to change the profile, but Idon't know where can I find other
profiles available.
kino lbrc-0.5 # find ./ -name "*nokia*"
./doc/mappings/nokia_6230i.txt
./doc/mappings/nokia_n70.txt
kino lbrc-0.5 # grep -r "nokia" *
config.conf: "defaultprofile": "nokia_6230i_maus1"
doc/bluez-dbus-api.txt:Copyright (C) 2005-2006 Johan Hedberg
<johan.hedberg at nokia.com>
doc/config.conf: "defaultprofile": "nokia_6230i_maus1"
On Fri, 11 Jan 2008, Matthias Bl?sing wrote:
> I will only comment on the problems with the newer bindings (the 0.8
> version, as that is the version also present in debian unstable).
> This looks like you are trying to run LBRC as root. Firstly: I don't
> know why this is so popular, but I would strongly advise against it.
yes of course... Just a tuning phase to avoid permission problems.
> But the basic problem would stay - namely: There is no dbus daemon
> running. Or at least it can't be accessed. If no dbus daemon is launched
> automaticly - you have to do it yourself (its explained in more detail
> in the manual pages of dbus-launch).
hmm... interesting.. I start dbus from /etc/init.d at the boot time and
accd to ps axuw it's running.
101 3582 0.0 0.1 2180 832 ? Ss 13:28 0:00
/usr/bin/dbus-daemon --system
> dbus-launch will invoke a new session bus and will print the enviroment
> variables necessary for the programms, that want to use the bus. You
> have to set these variables yourself, as a programm can't modify the
> environment of the calling parent.
> So you can either run dbus-launch and manually export the variables or
> use the shell to help you:
> test at prometheus:~$ eval `dbus-launch`
> test at prometheus:~$ export DBUS_SESSION_BUS_ADDRESS
> test at prometheus:~$ export DBUS_SESSION_BUS_PID
>> I'm trying to run LBRC v0.5, but I have several problems runnin
LBRCdbus
>> with dbus-python >=0.80 the proram exits with:
>> kino lbrc-0.5 # LBRCdbus --debug
>> Traceback (most recent call last):
>> File "/usr/bin/LBRCdbus", line 13, in <module>
>> brs = Core(debug=logging.DEBUG)
>> File "/usr/lib/python2.5/site-packages/LBRC/dbusinterface.py", line 195,
>> in __init__
>> bus_name = dbus.service.BusName(DBUSNAME, bus=dbus.SessionBus())
>> File "/usr/lib/python2.5/site-packages/dbus/_dbus.py", line 213, in
>> __new__
>> mainloop=mainloop)
>> File "/usr/lib/python2.5/site-packages/dbus/_dbus.py", line 102, in
>> __new__
>> bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
>> File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 125, in
>> __new__
>> bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
>> dbus.exceptions.DBusException:
>> org.freedesktop.DBus.Error.Spawn.ExecFailed:
>> Failed to execute dbus-launch to autolaunch D-Bus session
--
Check my PGP public key at http://poblijon.ubal.to/~tloudev/pgp.pub
From matthias.blaesing at rwth-aachen.de Fri Jan 11 16:12:29 2008
From: matthias.blaesing at rwth-aachen.de (Matthias =?ISO-8859-1?Q?Bl=E4sing?=)
Date: Fri, 11 Jan 2008 16:12:29 +0100
Subject: [Lbrc-devel] DBUS Daemon not running (was: Re: LBRC errors)
In-Reply-To: <Pine.LNX.4.64.0801111241230.24572@poblijon.ubal.to>
References: <Pine.LNX.4.64.0801111043530.24572@poblijon.ubal.to>
<1200049302.24740.13.camel@prometheus.glx>
<Pine.LNX.4.64.0801111241230.24572@poblijon.ubal.to>
Message-ID: <1200064349.16013.28.camel@prometheus.glx>
Hello again,
ok - you just hit a bug and undocumented behaviour. I'm not how much the
Format of lbrc.conf has changed, but your config looks strange.
Your problem is, that if there is a user config file, lbrc expects a
profiles section to be present. Well I commited a fix for this into svn.
To help you with 0.5 try this as .lbrc.conf:
{
"generic-config": {
"uinputdevice": "/dev/misc/uinput"
},
"profiles": {}
}
This sets the uinputdevice, defines an custom profiles section, that is
empty. Existing profiles can find in the lbrc.conf, that is installed
systemwide. If you execute LBRC from the source directory it is directly
in the base directory. If it is installed please use find.
And then you mentioned the dbus daemon started by init.d. There are
diffent "dbuses". The one you mentioned is the system bus, that is used
for system-wide services. The one we use is called the session bus. This
is created, when dbus-launch is called. Here connect all services, that
belong to one session. I hope the clears it a bit.
Greetings
Matthias
Am Freitag, den 11.01.2008, 13:09 +0100 schrieb tloudev:
> hi Matthias,
> so the correct version of the dbus-python should be >=0.80.. OK.
> right now it seems much better in this case, but I have another error,
> probably between the chair and the keyboard again :-)
>
> O.P.
>
> kino lbrc-0.5 # cat .lbrc.conf
> {
> "uinputdevice": "/dev/misc/uinput",
> "defaultprofile": "nokia_6230i_maus1"
> }
> [Traceback into config.py]
>
> I'd like to change the profile, but Idon't know where can I find other
> profiles available.
> kino lbrc-0.5 # find ./ -name "*nokia*"
> ./doc/mappings/nokia_6230i.txt
> ./doc/mappings/nokia_n70.txt
> kino lbrc-0.5 # grep -r "nokia" *
> config.conf: "defaultprofile": "nokia_6230i_maus1"
> doc/bluez-dbus-api.txt:Copyright (C) 2005-2006 Johan Hedberg
> <johan.hedberg at nokia.com>
> doc/config.conf: "defaultprofile": "nokia_6230i_maus1"
>
>
> On Fri, 11 Jan 2008, Matthias Bl?sing wrote:
> > I will only comment on the problems with the newer bindings (the 0.8
> > version, as that is the version also present in debian unstable).
> > This looks like you are trying to run LBRC as root. Firstly: I don't
> > know why this is so popular, but I would strongly advise against it.
>
> yes of course... Just a tuning phase to avoid permission problems.
>
> > But the basic problem would stay - namely: There is no dbus daemon
> > running. Or at least it can't be accessed. If no dbus daemon is launched
> > automaticly - you have to do it yourself (its explained in more detail
> > in the manual pages of dbus-launch).
>
> hmm... interesting.. I start dbus from /etc/init.d at the boot time and
> accd to ps axuw it's running.
> 101 3582 0.0 0.1 2180 832 ? Ss 13:28 0:00
> /usr/bin/dbus-daemon --system
>
> > dbus-launch will invoke a new session bus and will print the enviroment
> > variables necessary for the programms, that want to use the bus. You
> > have to set these variables yourself, as a programm can't modify the
> > environment of the calling parent.
> > So you can either run dbus-launch and manually export the variables or
> > use the shell to help you:
> > test at prometheus:~$ eval `dbus-launch`
> > test at prometheus:~$ export DBUS_SESSION_BUS_ADDRESS
> > test at prometheus:~$ export DBUS_SESSION_BUS_PID
>
> >> I'm trying to run LBRC v0.5, but I have several problems runnin
> LBRCdbus
> >> with dbus-python >=0.80 the proram exits with:
> >> kino lbrc-0.5 # LBRCdbus --debug
> >> Traceback (most recent call last):
> >> File "/usr/bin/LBRCdbus", line 13, in <module>
> >> brs = Core(debug=logging.DEBUG)
> >> File "/usr/lib/python2.5/site-packages/LBRC/dbusinterface.py", line 195,
> >> in __init__
> >> bus_name = dbus.service.BusName(DBUSNAME, bus=dbus.SessionBus())
> >> File "/usr/lib/python2.5/site-packages/dbus/_dbus.py", line 213, in
> >> __new__
> >> mainloop=mainloop)
> >> File "/usr/lib/python2.5/site-packages/dbus/_dbus.py", line 102, in
> >> __new__
> >> bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
> >> File "/usr/lib/python2.5/site-packages/dbus/bus.py", line 125, in
> >> __new__
> >> bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
> >> dbus.exceptions.DBusException:
> >> org.freedesktop.DBus.Error.Spawn.ExecFailed:
> >> Failed to execute dbus-launch to autolaunch D-Bus session
>
>
>
> --
>
> Check my PGP public key at http://poblijon.ubal.to/~tloudev/pgp.pub
>
> _______________________________________________
> Lbrc-devel mailing list
> Lbrc-devel at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/lbrc-devel
--
So long and thanks for all the fish!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
URL: <https://lists.berlios.de/pipermail/lbrc-devel/attachments/20080111/4767d901/attachment.pgp>
From k at mo.ubal.to Fri Jan 11 17:09:47 2008
From: k at mo.ubal.to (tloudev)
Date: Fri, 11 Jan 2008 17:09:47 +0100 (CET)
Subject: [Lbrc-devel] DBUS Daemon not running (was: Re: LBRC errors)
In-Reply-To: <1200064349.16013.28.camel@prometheus.glx>
References: <Pine.LNX.4.64.0801111043530.24572@poblijon.ubal.to>
<1200049302.24740.13.camel@prometheus.glx>
<Pine.LNX.4.64.0801111241230.24572@poblijon.ubal.to>
<1200064349.16013.28.camel@prometheus.glx>
Message-ID: <Pine.LNX.4.64.0801111656590.24572@poblijon.ubal.to>
hi,
solvin one problem causes another problem visible..
I have rfcomm kernel module loaded, bluetooth started, but:
kino / # /etc/init.d/bluetooth start
* Starting Bluetooth ...
* Starting hcid ... [ ok ]
* Starting rfcomm ... [ ok ]
kino / # hciconfig -a
hci0: Type: USB
BD Address: 11:11:11:11:11:11 ACL MTU: 672:3 SCO MTU: 48:1
UP RUNNING PSCAN ISCAN
RX bytes:284954058 acl:15 sco:5587243 events:130 errors:0
TX bytes:1982 acl:15 sco:0 commands:91 errors:0
Features: 0xff 0x3e 0x85 0x38 0x18 0x18 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: ACCEPT MASTER
Name: 'kino'
Class: 0x080100
Service Classes: Capturing
Device Class: Computer, Uncategorized
HCI Ver: 2.0 (0x3) HCI Rev: 0x1f4 LMP Ver: 2.0 (0x3) LMP Subver:
0x1f4
Manufacturer: CONWISE Technology Corporation Ltd (66)
kino / # LBRCdbus
Traceback (most recent call last):
File "/usr/bin/LBRCdbus", line 15, in <module>
brs = Core()
File "/usr/lib/python2.5/site-packages/LBRC/dbusinterface.py", line 204,
in __init__
self.btserver = BTServer()
File "/usr/lib/python2.5/site-packages/LBRC/BTServer.py", line 193, in
__init__
self.port = bluetooth.get_available_port( bluetooth.RFCOMM )
AttributeError: 'module' object has no attribute 'get_available_port'
BTW is there some way to add the LBRC service to the standard bluez
configuration? Can I run other bt services simultaneously?
O.P.
On Fri, 11 Jan 2008, Matthias Bl?sing wrote:
> Hello again,
> ok - you just hit a bug and undocumented behaviour. I'm not how much the
> Format of lbrc.conf has changed, but your config looks strange.
> Your problem is, that if there is a user config file, lbrc expects a
> profiles section to be present. Well I commited a fix for this into svn.
> To help you with 0.5 try this as .lbrc.conf:
>
> {
> "generic-config": {
> "uinputdevice": "/dev/misc/uinput"
> },
> "profiles": {}
> }
>
> This sets the uinputdevice, defines an custom profiles section, that is
> empty. Existing profiles can find in the lbrc.conf, that is installed
> systemwide. If you execute LBRC from the source directory it is directly
> in the base directory. If it is installed please use find.
>
> And then you mentioned the dbus daemon started by init.d. There are
> diffent "dbuses". The one you mentioned is the system bus, that is used
> for system-wide services. The one we use is called the session bus. This
> is created, when dbus-launch is called. Here connect all services, that
> belong to one session. I hope the clears it a bit.
>
> Greetings
>
> Matthias
>
> Am Freitag, den 11.01.2008, 13:09 +0100 schrieb tloudev:
>> hi Matthias,
>> so the correct version of the dbus-python should be >=0.80.. OK.
>> right now it seems much better in this case, but I have another error,
>> probably between the chair and the keyboard again :-)
>>
>> O.P.
From matthias.blaesing at rwth-aachen.de Fri Jan 11 17:38:35 2008
From: matthias.blaesing at rwth-aachen.de (Matthias =?ISO-8859-1?Q?Bl=E4sing?=)
Date: Fri, 11 Jan 2008 17:38:35 +0100
Subject: [Lbrc-devel] DBUS Daemon not running (was: Re: LBRC errors)
In-Reply-To: <Pine.LNX.4.64.0801111656590.24572@poblijon.ubal.to>
References: <Pine.LNX.4.64.0801111043530.24572@poblijon.ubal.to>
<1200049302.24740.13.camel@prometheus.glx>
<Pine.LNX.4.64.0801111241230.24572@poblijon.ubal.to>
<1200064349.16013.28.camel@prometheus.glx>
<Pine.LNX.4.64.0801111656590.24572@poblijon.ubal.to>
Message-ID: <1200069515.5999.9.camel@prometheus.glx>
Hi,
this concrete problem is fixed in svn. Not sure how good your at reading
patches, but this is the needed fix:
Index: LBRC/BTServer.py
===================================================================
--- LBRC/BTServer.py (Revision 220)
+++ LBRC/BTServer.py (Revision 221)
@@ -189,9 +189,9 @@
self.server_io_watch = None
- self.port = bluetooth.get_available_port( bluetooth.RFCOMM )
self.server_sock = bluetooth.BluetoothSocket( bluetooth.RFCOMM )
- self.server_sock.bind(("", self.port))
+ self.server_sock.bind(("", bluetooth.PORT_ANY))
+ (addr, self.port) = self.server_sock.getsockname();
self.server_sock.listen(1)
self.bluez_db = dinterface(dbus.SystemBus(), 'org.bluez', '/org/bluez', 'org.bluez.Database')
As I stated in the message I send when commiting this patch, it was
caused by python-bluez dropping a deprecated api. This caught my
attention, when debian got a new version of python-dbus.
Towards your question regarding other bluetooth services. Yes you can
run any other service in parallel. Think of the bluez (or bluetooth in
general) services as server processes - ok there are not that many
rfcomm channels, but ports on tcp/ip can be compared to L2CAP sockts
which are the basis for rfcomm and other protocolls.
Greetings
Matthias
Am Freitag, den 11.01.2008, 17:09 +0100 schrieb tloudev:
> hi,
> solvin one problem causes another problem visible..
> I have rfcomm kernel module loaded, bluetooth started, but:
> kino / # /etc/init.d/bluetooth start
> * Starting Bluetooth ...
> * Starting hcid ... [ ok ]
> * Starting rfcomm ... [ ok ]
> kino / # hciconfig -a
> hci0: Type: USB
> BD Address: 11:11:11:11:11:11 ACL MTU: 672:3 SCO MTU: 48:1
> UP RUNNING PSCAN ISCAN
> RX bytes:284954058 acl:15 sco:5587243 events:130 errors:0
> TX bytes:1982 acl:15 sco:0 commands:91 errors:0
> Features: 0xff 0x3e 0x85 0x38 0x18 0x18 0x00 0x00
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> Link policy: RSWITCH HOLD SNIFF PARK
> Link mode: ACCEPT MASTER
> Name: 'kino'
> Class: 0x080100
> Service Classes: Capturing
> Device Class: Computer, Uncategorized
> HCI Ver: 2.0 (0x3) HCI Rev: 0x1f4 LMP Ver: 2.0 (0x3) LMP Subver:
> 0x1f4
> Manufacturer: CONWISE Technology Corporation Ltd (66)
>
> kino / # LBRCdbus
> Traceback (most recent call last):
> File "/usr/bin/LBRCdbus", line 15, in <module>
> brs = Core()
> File "/usr/lib/python2.5/site-packages/LBRC/dbusinterface.py", line 204,
> in __init__
> self.btserver = BTServer()
> File "/usr/lib/python2.5/site-packages/LBRC/BTServer.py", line 193, in
> __init__
> self.port = bluetooth.get_available_port( bluetooth.RFCOMM )
> AttributeError: 'module' object has no attribute 'get_available_port'
>
> BTW is there some way to add the LBRC service to the standard bluez
> configuration? Can I run other bt services simultaneously?
> O.P.
>
>
> On Fri, 11 Jan 2008, Matthias Bl?sing wrote:
>
> > Hello again,
> > ok - you just hit a bug and undocumented behaviour. I'm not how much the
> > Format of lbrc.conf has changed, but your config looks strange.
> > Your problem is, that if there is a user config file, lbrc expects a
> > profiles section to be present. Well I commited a fix for this into svn.
> > To help you with 0.5 try this as .lbrc.conf:
> >
> > {
> > "generic-config": {
> > "uinputdevice": "/dev/misc/uinput"
> > },
> > "profiles": {}
> > }
> >
> > This sets the uinputdevice, defines an custom profiles section, that is
> > empty. Existing profiles can find in the lbrc.conf, that is installed
> > systemwide. If you execute LBRC from the source directory it is directly
> > in the base directory. If it is installed please use find.
> >
> > And then you mentioned the dbus daemon started by init.d. There are
> > diffent "dbuses". The one you mentioned is the system bus, that is used
> > for system-wide services. The one we use is called the session bus. This
> > is created, when dbus-launch is called. Here connect all services, that
> > belong to one session. I hope the clears it a bit.
> >
> > Greetings
> >
> > Matthias
> >
> > Am Freitag, den 11.01.2008, 13:09 +0100 schrieb tloudev:
> >> hi Matthias,
> >> so the correct version of the dbus-python should be >=0.80.. OK.
> >> right now it seems much better in this case, but I have another error,
> >> probably between the chair and the keyboard again :-)
> >>
> >> O.P.
> _______________________________________________
> Lbrc-devel mailing list
> Lbrc-devel at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/lbrc-devel
--
So long and thanks for all the fish!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
URL: <https://lists.berlios.de/pipermail/lbrc-devel/attachments/20080111/e1e50a94/attachment.pgp>
From k at mo.ubal.to Fri Jan 11 18:34:36 2008
From: k at mo.ubal.to (tloudev)
Date: Fri, 11 Jan 2008 18:34:36 +0100 (CET)
Subject: [Lbrc-devel] DBUS Daemon not running (was: Re: LBRC errors)
In-Reply-To: <1200069515.5999.9.camel@prometheus.glx>
References: <Pine.LNX.4.64.0801111043530.24572@poblijon.ubal.to>
<1200049302.24740.13.camel@prometheus.glx>
<Pine.LNX.4.64.0801111241230.24572@poblijon.ubal.to>
<1200064349.16013.28.camel@prometheus.glx>
<Pine.LNX.4.64.0801111656590.24572@poblijon.ubal.to>
<1200069515.5999.9.camel@prometheus.glx>
Message-ID: <Pine.LNX.4.64.0801111745480.24572@poblijon.ubal.to>
hi,
patches are OK, only the python language is a real nightmare :-)
but.. HEAKAPAAA! IT WORKS! I can get events! Thank you!
and the last question is: whire is the FIFO? I'm runnin mplayer from the
startup scripts with some window geometry and display settins, so it's
totally non-interactive. I need to run it with some -input FIFO parameter,
but accordin to /proc/XXXX/fd/ and netstat -lpn I can't locate the output
fifo from LBRC. I suppose it's conected some way to the current virtual
terminal, but where is the output goin in non-interactive mode?
thank you
Ondrej Pachner
On Fri, 11 Jan 2008, Matthias Bl?sing wrote:
> Hi,
>
> this concrete problem is fixed in svn. Not sure how good your at reading
> patches, but this is the needed fix:
>
> Index: LBRC/BTServer.py
> ===================================================================
> --- LBRC/BTServer.py (Revision 220)
> +++ LBRC/BTServer.py (Revision 221)
> @@ -189,9 +189,9 @@
>
> self.server_io_watch = None
>
> - self.port = bluetooth.get_available_port( bluetooth.RFCOMM )
> self.server_sock = bluetooth.BluetoothSocket( bluetooth.RFCOMM )
> - self.server_sock.bind(("", self.port))
> + self.server_sock.bind(("", bluetooth.PORT_ANY))
> + (addr, self.port) = self.server_sock.getsockname();
> self.server_sock.listen(1)
>
> self.bluez_db = dinterface(dbus.SystemBus(), 'org.bluez', '/org/bluez', 'org.bluez.Database')
>
> As I stated in the message I send when commiting this patch, it was
> caused by python-bluez dropping a deprecated api. This caught my
> attention, when debian got a new version of python-dbus.
>
> Towards your question regarding other bluetooth services. Yes you can
> run any other service in parallel. Think of the bluez (or bluetooth in
> general) services as server processes - ok there are not that many
> rfcomm channels, but ports on tcp/ip can be compared to L2CAP sockts
> which are the basis for rfcomm and other protocolls.
>
> Greetings
>
> Matthias
From matthias.blaesing at rwth-aachen.de Fri Jan 11 21:44:05 2008
From: matthias.blaesing at rwth-aachen.de (Matthias =?ISO-8859-1?Q?Bl=E4sing?=)
Date: Fri, 11 Jan 2008 21:44:05 +0100
Subject: [Lbrc-devel] DBUS Daemon not running (was: Re: LBRC errors)
In-Reply-To: <Pine.LNX.4.64.0801111745480.24572@poblijon.ubal.to>
References: <Pine.LNX.4.64.0801111043530.24572@poblijon.ubal.to>
<1200049302.24740.13.camel@prometheus.glx>
<Pine.LNX.4.64.0801111241230.24572@poblijon.ubal.to>
<1200064349.16013.28.camel@prometheus.glx>
<Pine.LNX.4.64.0801111656590.24572@poblijon.ubal.to>
<1200069515.5999.9.camel@prometheus.glx>
<Pine.LNX.4.64.0801111745480.24572@poblijon.ubal.to>
Message-ID: <1200084245.2565.3.camel@prometheus.glx>
Hey,
Am Freitag, den 11.01.2008, 18:34 +0100 schrieb tloudev:
> and the last question is: whire is the FIFO? I'm runnin mplayer from the
> startup scripts with some window geometry and display settins, so it's
> totally non-interactive. I need to run it with some -input FIFO parameter,
> but accordin to /proc/XXXX/fd/ and netstat -lpn I can't locate the output
> fifo from LBRC. I suppose it's conected some way to the current virtual
> terminal, but where is the output goin in non-interactive mode?
the mplayer module uses it's own mplayer instance, that is started from
inside the module and feeds the commands into it via stdin. I have to
look into this, as the last time I tried to use the fifo it did not do
what I would have expected. I think the main problem was, that I fifo
could not be closed and opened again - but that's the vague recollection
of the events happening a year ago or so.
Greetings
Matthias
--
So long and thanks for all the fish!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
URL: <https://lists.berlios.de/pipermail/lbrc-devel/attachments/20080111/fe12c3ca/attachment.pgp>
From matthias.blaesing at rwth-aachen.de Sat Jan 12 20:36:05 2008
From: matthias.blaesing at rwth-aachen.de (Matthias =?ISO-8859-1?Q?Bl=E4sing?=)
Date: Sat, 12 Jan 2008 20:36:05 +0100
Subject: [Lbrc-devel] LBRC Installation successful but Service is not
discovered.
In-Reply-To: <1200114081.11528.6.camel@uruk.bastardsonofgod.com>
References: <1200114081.11528.6.camel@uruk.bastardsonofgod.com>
Message-ID: <1200166565.8662.13.camel@prometheus.glx>
Hello Arthur,
you commented, that the documentation for LBRC on the webspace is a bit
thin - thats quite right, but then - I try to get LBRC stable and that
costs enough time. I'll happily include input for the webspace and the
overall documentation though!
Am Freitag, den 11.01.2008, 20:01 -0900 schrieb Arthur Brown:
> [LBRC-Log of successfull run: http://pastebin.ca/851741]
This looks quite good. What you can see is LBRC coming up and
initializing the VolumeControl Profile. (So far so good)
> When I run the client application
> on my Nokia 6085, I am able to see the server, but when I select it I am
> told the the LBRC service is not found.
This is bad - bad because if you can see the server, but there seems not
to be a service record for LBRC. Could you please start LBRCdbus and
provide me with the output of "sdptool browse local"? There all the
advertised services of the local bluetooth adapter are listed.
> I notice that DBUSCaller kills
> itself when it fails to find the profile it was looking for, but I don't
> know enough about ordinary dbus behavior or your program to know if this
> was intended, unfortunately.
Can you describe a bit more precise, I mean: what do mean by "DBUSCaller
kills itself"?
Greetins
Matthias
PS: Please direct your mails to lbrc-devel at lists.berlios.de, as there
the mails are archived. You don't need to subscribe - I'll CC the list
and direct the answers to you.
--
So long and thanks for all the fish!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
URL: <https://lists.berlios.de/pipermail/lbrc-devel/attachments/20080112/18bcf737/attachment.pgp>
From a.brown at acetylene-computing.com Sat Jan 12 22:51:54 2008
From: a.brown at acetylene-computing.com (Arthur Brown)
Date: Sat, 12 Jan 2008 12:51:54 -0900
Subject: [Lbrc-devel] LBRC Installation successful but Service is not
discovered.
Message-ID: <1200174714.11528.13.camel@uruk.bastardsonofgod.com>
Hello,
This is the output of"sdptool browse local" after calling LBRCdbus from
console:
enkidu at uruk:~$ sdptool browse local
Browsing FF:FF:FF:00:00:00 ...
Service Name: LBRC
Service RecHandle: 0x10000
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 1
Service Name: LBRC
Service RecHandle: 0x10001
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 2
Despite that, the LBRC service is still not being found by my cellphone
when I select the server. Is there a means of monitoring the raw data
sent to and from the server when it is queried for the service? I think
that this might reveal more about the problem. Thanks again,
Arthur
From matthias.blaesing at rwth-aachen.de Sat Jan 12 23:50:20 2008
From: matthias.blaesing at rwth-aachen.de (Matthias =?ISO-8859-1?Q?Bl=E4sing?=)
Date: Sat, 12 Jan 2008 23:50:20 +0100
Subject: [Lbrc-devel] LBRC Installation successful but Service is
not discovered.
In-Reply-To: <1200174714.11528.13.camel@uruk.bastardsonofgod.com>
References: <1200174714.11528.13.camel@uruk.bastardsonofgod.com>
Message-ID: <1200178220.4890.9.camel@prometheus.glx>
Hey,
you can capture the bluetooth traffic - but that does not help much -
you only see the packes as they go to air, and there you see the
encrypted traffic (at least in all solutions I have seen).
Could you try a newer build of the j2me client from:
http://www.doppel-helix.eu/LBRC.jad and
http://www.doppel-helix.eu/LBRC.jar
I have a suspicion, that Nokia might report Norecords, but find them
anyway. Please report the complete displayer error message.
Another problem could be, that the service search by uuid is broken on
your phone - that would be the next step.
Greetings
Matthias
Am Samstag, den 12.01.2008, 12:51 -0900 schrieb Arthur Brown:
> [sdptool lists LBRC as service]
> Despite that, the LBRC service is still not being found by my cellphone
> when I select the server. Is there a means of monitoring the raw data
> sent to and from the server when it is queried for the service? I think
> that this might reveal more about the problem. Thanks again,
>
> Arthur
--
So long and thanks for all the fish!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
URL: <https://lists.berlios.de/pipermail/lbrc-devel/attachments/20080112/037571ea/attachment.pgp>
From a.brown at acetylene-computing.com Sun Jan 13 00:05:30 2008
From: a.brown at acetylene-computing.com (Arthur Brown)
Date: Sat, 12 Jan 2008 14:05:30 -0900
Subject: [Lbrc-devel] LBRC Installation successful but Service is
not discovered.
In-Reply-To: <1200178220.4890.9.camel@prometheus.glx>
References: <1200174714.11528.13.camel@uruk.bastardsonofgod.com>
<1200178220.4890.9.camel@prometheus.glx>
Message-ID: <1200179130.11528.19.camel@uruk.bastardsonofgod.com>
The full content of the error using the newer build of the client
software follows:
LBRC Service not found! Length of service list: 0
If my phone is unable to search for services by uuid, would it be
possible to force it to assume that the service is present on a
predefined channel?
Arthur
From matthias.blaesing at rwth-aachen.de Sun Jan 13 19:32:01 2008
From: matthias.blaesing at rwth-aachen.de (Matthias =?ISO-8859-1?Q?Bl=E4sing?=)
Date: Sun, 13 Jan 2008 19:32:01 +0100
Subject: [Lbrc-devel] MPlayer module with FIFO support (was: DBUS Daemon
not running)
In-Reply-To: <1200084245.2565.3.camel@prometheus.glx>
References: <Pine.LNX.4.64.0801111043530.24572@poblijon.ubal.to>
<1200049302.24740.13.camel@prometheus.glx>
<Pine.LNX.4.64.0801111241230.24572@poblijon.ubal.to>
<1200064349.16013.28.camel@prometheus.glx>
<Pine.LNX.4.64.0801111656590.24572@poblijon.ubal.to>
<1200069515.5999.9.camel@prometheus.glx>
<Pine.LNX.4.64.0801111745480.24572@poblijon.ubal.to>
<1200084245.2565.3.camel@prometheus.glx>
Message-ID: <1200249121.24065.10.camel@prometheus.glx>
Hey again,
I think, that I have a solution. I attached a patch against the MPlayer
module shipped with LBRC 0.5 (will commit today or tomorrow into svn).
Please apply the attached patch and create a profile like the one below.
The minimal config - only defining the profile for MPlayer:
{
"generic-config": {
"default-profile": [
"user",