I have pretty obsolete dbus in my system and olive-gtk 0.95.0 fails to even 
start with exception.
Attached patch  implements extra step in detecting dbus errors in that case.
Hope is strict enough to be included.

Regards,
-- 
Mateusz Korniak
# Bazaar merge directive format 2 (Bazaar 0.90)
# revision_id: [EMAIL PROTECTED]
# target_branch: http://bazaar.launchpad.net/%7Ebzr-gtk/bzr-gtk/trunk/
# testament_sha1: eda105bc10e04872213fdc4ec527b1165daf1b74
# timestamp: 2008-08-05 17:35:00 +0200
# source_branch: ./
# base_revision_id: [EMAIL PROTECTED]
# 
# Begin patch
=== modified file 'seahorse.py'
--- seahorse.py	2008-07-23 00:07:09 +0000
+++ seahorse.py	2008-08-05 13:56:46 +0000
@@ -40,6 +40,12 @@
         name = get_name()
     else:
         name = getattr(e, '_dbus_error_name', None)
+        
+    if name is None:
+        args = getattr(e, 'args', None) # This is case for old python-dbus-0.62
+        if args == ("Unable to determine the address of the message bus (try 'man dbus-launch' and 'man dbus-daemon' for help)",):
+            raise ImportError
+        
     # DBus sometimes fails like this, just treat it as if seahorse is not
     # available rather than crashing.
     if name in ("org.freedesktop.DBus.Error.Spawn.ExecFailed", 

# Begin bundle
IyBCYXphYXIgcmV2aXNpb24gYnVuZGxlIHY0CiMKQlpoOTFBWSZTWX2aFDAAAaFfgERQWOf/91Yr
BgC////wUAPMng1ZrbV5duuEkpkmaTKeTI0ZqCR5T0anqZoQaMJoOYBMAJgABMAATAAEoQTRT001
PTU0zU0epkDQ0aBo0aGgSSEaZRHqfqjTQyaaeo00aaANAB6gSSJkaZTFHhCnqek9TxNTT0gAAAeK
/TEl/Nyvd+8I6mnUwy6mwzxc8CfGSEcj8wglFPk1b76vb6uNdKirt2G58hbBRX5pz1/q3Z36NjPw
e6meEIrZZbbfjfGmxqJQpjJJOfFQmZhonJLI2NzDbF6IVCO1WO4sBs87KnBayxs9TGTTnnNBboMP
RUC0r5insHpScDRdfMxjQsbesvMerNL3I2Z5hUtzHwM0qcCoFyIokQHC7Kh79HDkDCGLOigW6Lnq
sLkOcLN+5imbYsUGF7TFQIu9cjecCJkZDFC/a8MpjOywiCqT0+hYPBiJIcM8svM6FSCAmrF2uWha
SLVLIYiYj1XjaK+8VhTrKhurY1GWxT1W3NrWWqpBBXC1ncLB94otAuNaxIEBUFTNOHkhZtHWRK3U
CRekxuIM9kEGMhAw0COIgoM+D4lAr2pWONjrFAsMAw77JtiSzZiaqtNoQy6m1heLHS3LXh5RpObE
XqNNdrNF7oMTKzpwNSOqVFPStqqSSpqJmGBqPpkpa70Z4T79htO/Lar668CcitMblAJm4j0/Krt5
kp4pcK0dH89k6/TAUQ7HexlesKLkbQlTvfsMqmr3EeL9dbTa30HM8CKgQVQ95MOs2GNQ3AkbzE3c
xXGfx3cOmh2L7nt4yu7bQsLyRa32EOxqSo1Sm6l4Yan528DSaeyg/J7Fu/UihlxVWVNzSDnJRCzb
RKADKEfK2jsDE9QxzOJM3mbjQYmfDvy3sjwdjJKq96v2LUF5Cb493lHalUnVUjfAOOn8uM6eVeYb
MtHK92TGxknHJuzkBbDpp5zCvYX5BsVwHQqVqmvylt5B3dzFQfawhzN6geR1qTX4HgmyhCLtvUQj
mrhE9ppXjSsHGJhX4VirIoqTGCkq/hanqKi5DLRmlgOVM1RTmHJXnhpVkkpORMaAEA24K+esqVr8
jCcl5irpjGKeZEUSNw0zTDQMEu8WZUnI8tpaqwnkia3yMiL1Iwb275kJV6sHCqOnilEnIy0utDMb
oxFFUiMrjHuly1s97B1r+UpDNFdllu1qnnVCsBpKaIBoGjLtNzidxdJzWtDM4seYzkPM4gOolMOA
pt+vFxJlik8zWGmEH5xYaSTAUMrK0VVyyqtTKY4p72cAw4pqsJv+LuSKcKEg+zQoYA==
-- 
bzr-gtk mailing list
[email protected]
Modify settings or unsubscribe at: 
https://lists.canonical.com/mailman/listinfo/bzr-gtk

Reply via email to