Closed Thor77 closed 8 years ago
Logged In: YES user_id=114903 Originator: YES
Action commands will now be logged if a command takes too long to execute. This should be about it... (By highno)
Logged In: YES user_id=114903 Originator: YES
Unwritable logfiles are also noted on the console. (By highno)
Logged In: YES user_id=114903 Originator: YES
a broken config file is now mentioned on the console. I think that these outputs should all go on console if the relate to changes that could only be made on the console itself like changing the config file to an unallowed structure. (By highno)
Logged In: YES user_id=114903 Originator: YES
Thanks for the patch - I now included it and expanded that solution to all external modules. Watch out for the SVN version and new nightly build tonight.
Bye Lars (By highno)
Logged In: YES user_id=1692926 Originator: NO
Here's my patch:
--- ../blueproximity-1.2/proximity.py 2007-09-11 23:48:34.000000000 +0200 +++ proximity.py 2007-09-22 10:41:15.000000000 +0200 @@ -28,7 +28,14 @@ import gobject import signal from configobj import ConfigObj from validate import Validator -import bluetooth +try:
gtk.gdk.threads_init() gtk.main()
\ No newline at end of file
(By thstaerk)
As there is none at the moment it would be nice to be informed of what's going on and what is not working out. That should at least include having a broken .blueproximityrc file, using an unwritable logfile, action commands not working out or taking too long to execute, a mac address with the wrong format.