2009-09-18 20:18:41,966:966.454029083 UbuntuOne.OAuthDesktop.main Creating a LoginProcessor
2009-09-18 20:18:42,050:50.0960350037 UbuntuOne.OAuthDesktop.main Hooking libnotify
2009-09-18 20:18:42,069:69.5490837097 UbuntuOne.OAuthDesktop.main Getting configuration
2009-09-18 20:18:42,072:72.1819400787 UbuntuOne.OAuthDesktop.main Login D-Bus service starting up
2009-09-18 20:18:42,073:73.8708972931 UbuntuOne.Client.Applet Starting Ubuntu One client version 0.95.1
2009-09-18 20:18:44,261:261.744976044 UbuntuOne.OAuthDesktop.main maybe_login() D-Bus message received with realm='https://ubuntuone.com', consumer_key='ubuntuone'
2009-09-18 20:18:44,262:262.156009674 UbuntuOne.OAuthDesktop.main Initiating OAuth login in LoginProcessor
2009-09-18 20:18:44,262:262.382030487 UbuntuOne.OAuthDesktop.main Obtaining OAuth urls
2009-09-18 20:18:44,262:262.598991394 UbuntuOne.OAuthDesktop.main Fetching config URLs for realm='https://ubuntuone.com'
2009-09-18 20:18:44,262:262.94708252 UbuntuOne.OAuthDesktop.main Realm 'https://ubuntuone.com' is not in config
2009-09-18 20:18:44,263:263.484954834 UbuntuOne.OAuthDesktop.main OAuth URLs are: request='https://ubuntuone.com/oauth/request/', userauth='https://ubuntuone.com/oauth/authorize/', access='https://ubuntuone.com/oauth/access/', secret='hammertime'
2009-09-18 20:18:44,939:939.336061478 UbuntuOne.OAuthDesktop.auth auth.AuthorisationClient created with parameters realm='https://ubuntuone.com', request_token_url='https://ubuntuone.com/oauth/request/', user_authorisation_url='https://ubuntuone.com/oauth/authorize/',access_token_url='https://ubuntuone.com/oauth/access/', consumer_key='ubuntuone', callback_parent='<bound method LoginProcessor.got_token of <ubuntuone.oauthdesktop.main.LoginProcessor instance at 0xa3996ac>>'
2009-09-18 20:18:44,939:939.644098282 UbuntuOne.OAuthDesktop.main Calling auth.client.ensure_access_token in thread
2009-09-18 20:18:44,960:960.613012314 UbuntuOne.OAuthDesktop.auth Trying to fetch the token from the keyring
2009-09-18 20:18:45,097:97.9020595551 UbuntuOne.OAuthDesktop.auth Access token was not in the keyring
2009-09-18 20:18:45,098:98.2229709625 UbuntuOne.OAuthDesktop.auth Checking whether we are online
2009-09-18 20:18:45,603:603.240966797 UbuntuOne.OAuthDesktop.auth We are online
2009-09-18 20:18:45,603:603.538990021 UbuntuOne.OAuthDesktop.auth Creating a request token to begin access request
2009-09-18 20:18:45,603:603.684902191 UbuntuOne.OAuthDesktop.auth Creating a listening temp web server
2009-09-18 20:18:45,604:604.278087616 UbuntuOne.OAuthDesktop.auth Webserver listening on port '<<class 'twisted.internet.tcp.Port'> of twisted.web.server.Site on 35120>'
2009-09-18 20:18:45,605:605.000972748 UbuntuOne.OAuthDesktop.auth Making token request
2009-09-18 20:18:45,605:605.160951614 UbuntuOne.OAuthDesktop.auth Making a token request
2009-09-18 20:18:47,952:952.167034149 UbuntuOne.OAuthDesktop.auth Redirected to: https://one.ubuntu.com/oauth/request/
2009-09-18 20:18:50,071:71.221113205 UbuntuOne.OAuthDesktop.auth Token successfully requested
2009-09-18 20:18:50,072:72.1740722656 UbuntuOne.OAuthDesktop.auth Opening 'https://ubuntuone.com/oauth/authorize/?oauth_token=W3M313j6g2xNVt1z13rZ&description=jessica' in the browser
2009-09-18 20:19:05,283:283.262014389 UbuntuOne.OAuthDesktop.auth Incoming temp webserver hit received
2009-09-18 20:19:05,283:283.833026886 UbuntuOne.OAuthDesktop.auth Got verifier d7d73470-b0e2-4ae7-b5de-b178c836c299
2009-09-18 20:19:05,284:284.241914749 UbuntuOne.OAuthDesktop.auth Access token callback from temp webserver
2009-09-18 20:19:05,284:284.974098206 UbuntuOne.OAuthDesktop.auth Retrieving access token from OAuth
2009-09-18 20:19:05,285:285.389900208 UbuntuOne.OAuthDesktop.auth Making a token request
2009-09-18 20:19:21,653:653.551101685 UbuntuOne.OAuthDesktop.auth Redirected to: https://one.ubuntu.com/oauth/access/
2009-09-18 20:19:37,968:968.967914581 UbuntuOne.OAuthDesktop.auth Token successfully requested
2009-09-18 20:19:37,969:969.381093979 UbuntuOne.OAuthDesktop.auth Storing access token in keyring
2009-09-18 20:19:37,969:969.516992569 UbuntuOne.OAuthDesktop.auth Trying to store the token in the keyring
2009-09-18 20:19:38,002:2.11310386658 UbuntuOne.OAuthDesktop.auth Setting ACLs on the token in the keyring
2009-09-18 20:19:42,019:19.4489955902 UbuntuOne.OAuthDesktop.auth Calling the callback_parent
2009-09-18 20:19:42,020:20.0579166412 UbuntuOne.OAuthDesktop.main Token retrieved, calling NewCredentials function
2009-09-18 20:19:42,020:20.4570293427 UbuntuOne.OAuthDesktop.main Firing the NewCredentials signal
2009-09-18 20:19:42,465:465.478897095 UbuntuOne.OAuthDesktop.auth Incoming temp webserver hit received
2009-09-18 20:19:42,465:465.986013412 UbuntuOne.OAuthDesktop.auth Got verifier None
2009-09-18 20:19:45,021:21.8579769135 UbuntuOne.OAuthDesktop.auth Stopping temp webserver
2009-09-18 20:19:45,495:495.496034622 UbuntuOne.OAuthDesktop.auth Incoming temp webserver hit received
2009-09-18 20:19:45,495:495.81193924 UbuntuOne.OAuthDesktop.auth Got verifier None
2009-09-18 20:28:45,603:603.949069977 UbuntuOne.OAuthDesktop.auth Stopping temp webserver
2009-09-18 20:59:05,433:433.804035187 UbuntuOne.OAuthDesktop.main Creating a LoginProcessor
2009-09-18 20:59:06,795:795.486927032 UbuntuOne.OAuthDesktop.main Hooking libnotify
2009-09-18 20:59:06,802:802.328109741 UbuntuOne.OAuthDesktop.main Getting configuration
2009-09-18 20:59:06,855:855.292081833 UbuntuOne.OAuthDesktop.main Login D-Bus service starting up
2009-09-18 20:59:06,869:869.059085846 UbuntuOne.Client.Applet Starting Ubuntu One client version 0.95.1
2009-09-18 20:59:20,333:333.776950836 UbuntuOne.OAuthDesktop.main maybe_login() D-Bus message received with realm='https://ubuntuone.com', consumer_key='ubuntuone'
2009-09-18 20:59:20,934:934.242010117 UbuntuOne.OAuthDesktop.main Initiating OAuth login in LoginProcessor
2009-09-18 20:59:20,934:934.540987015 UbuntuOne.OAuthDesktop.main Obtaining OAuth urls
2009-09-18 20:59:20,934:934.667110443 UbuntuOne.OAuthDesktop.main Fetching config URLs for realm='https://ubuntuone.com'
2009-09-18 20:59:20,934:934.910058975 UbuntuOne.OAuthDesktop.main Realm 'https://ubuntuone.com' is not in config
2009-09-18 20:59:20,935:935.230970383 UbuntuOne.OAuthDesktop.main OAuth URLs are: request='https://ubuntuone.com/oauth/request/', userauth='https://ubuntuone.com/oauth/authorize/', access='https://ubuntuone.com/oauth/access/', secret='hammertime'
2009-09-18 20:59:23,380:380.989074707 UbuntuOne.OAuthDesktop.auth auth.AuthorisationClient created with parameters realm='https://ubuntuone.com', request_token_url='https://ubuntuone.com/oauth/request/', user_authorisation_url='https://ubuntuone.com/oauth/authorize/',access_token_url='https://ubuntuone.com/oauth/access/', consumer_key='ubuntuone', callback_parent='<bound method LoginProcessor.got_token of <ubuntuone.oauthdesktop.main.LoginProcessor instance at 0x8d4028c>>'
2009-09-18 20:59:24,718:718.678951263 UbuntuOne.OAuthDesktop.main Calling auth.client.ensure_access_token in thread
2009-09-18 20:59:24,816:816.67804718 UbuntuOne.OAuthDesktop.auth Trying to fetch the token from the keyring
2009-09-18 20:59:25,103:103.323936462 UbuntuOne.OAuthDesktop.auth Access token was not in the keyring
2009-09-18 20:59:25,586:586.570978165 UbuntuOne.OAuthDesktop.auth Checking whether we are online
2009-09-18 20:59:25,610:610.62002182 UbuntuOne.OAuthDesktop.auth We are currently going online
2009-09-18 20:59:26,497:497.642040253 UbuntuOne.OAuthDesktop.auth Online status has changed to 4
2009-09-18 20:59:26,497:497.885942459 UbuntuOne.OAuthDesktop.auth Not yet connected: continuing to wait
2009-09-18 20:59:30,004:4.78911399841 UbuntuOne.OAuthDesktop.auth Online status has changed to 2
2009-09-18 20:59:30,005:5.18298149109 UbuntuOne.OAuthDesktop.auth Not yet connected: continuing to wait
2009-09-18 20:59:32,555:555.190086365 UbuntuOne.OAuthDesktop.auth Online status has changed to 4
2009-09-18 20:59:32,555:555.438041687 UbuntuOne.OAuthDesktop.auth Not yet connected: continuing to wait
2009-09-18 21:06:38,426:426.469087601 UbuntuOne.OAuthDesktop.main Creating a LoginProcessor
2009-09-18 21:06:39,047:47.5680828094 UbuntuOne.OAuthDesktop.main Hooking libnotify
2009-09-18 21:06:39,326:326.680898666 UbuntuOne.OAuthDesktop.main Getting configuration
2009-09-18 21:06:39,935:935.740947723 UbuntuOne.OAuthDesktop.main Login D-Bus service starting up
2009-09-18 21:06:39,936:936.583995819 UbuntuOne.Client.Applet Starting Ubuntu One client version 0.95.1
2009-09-18 21:06:52,699:699.084997177 UbuntuOne.OAuthDesktop.main maybe_login() D-Bus message received with realm='https://ubuntuone.com', consumer_key='ubuntuone'
2009-09-18 21:06:52,699:699.388980865 UbuntuOne.OAuthDesktop.main Initiating OAuth login in LoginProcessor
2009-09-18 21:06:52,699:699.523925781 UbuntuOne.OAuthDesktop.main Obtaining OAuth urls
2009-09-18 21:06:52,699:699.645996094 UbuntuOne.OAuthDesktop.main Fetching config URLs for realm='https://ubuntuone.com'
2009-09-18 21:06:52,699:699.965000153 UbuntuOne.OAuthDesktop.main Realm 'https://ubuntuone.com' is not in config
2009-09-18 21:06:52,700:700.279951096 UbuntuOne.OAuthDesktop.main OAuth URLs are: request='https://ubuntuone.com/oauth/request/', userauth='https://ubuntuone.com/oauth/authorize/', access='https://ubuntuone.com/oauth/access/', secret='hammertime'
2009-09-18 21:06:56,262:262.527942657 UbuntuOne.OAuthDesktop.auth auth.AuthorisationClient created with parameters realm='https://ubuntuone.com', request_token_url='https://ubuntuone.com/oauth/request/', user_authorisation_url='https://ubuntuone.com/oauth/authorize/',access_token_url='https://ubuntuone.com/oauth/access/', consumer_key='ubuntuone', callback_parent='<bound method LoginProcessor.got_token of <ubuntuone.oauthdesktop.main.LoginProcessor instance at 0x978528c>>'
2009-09-18 21:06:56,262:262.928962708 UbuntuOne.OAuthDesktop.main Calling auth.client.ensure_access_token in thread
2009-09-18 21:06:56,273:273.312091827 UbuntuOne.OAuthDesktop.auth Trying to fetch the token from the keyring
2009-09-18 21:06:56,288:288.922071457 UbuntuOne.OAuthDesktop.auth Access token successfully found in the keyring
2009-09-18 21:06:56,289:289.393901825 UbuntuOne.OAuthDesktop.main Token retrieved, calling NewCredentials function
2009-09-18 21:06:56,289:289.534091949 UbuntuOne.OAuthDesktop.main Firing the NewCredentials signal
2009-09-18 21:14:12,146:146.723985672 UbuntuOne.OAuthDesktop.main Creating a LoginProcessor
2009-09-18 21:14:12,508:508.074998856 UbuntuOne.OAuthDesktop.main Hooking libnotify
2009-09-18 21:14:12,512:512.655973434 UbuntuOne.OAuthDesktop.main Getting configuration
2009-09-18 21:14:12,578:578.799962997 UbuntuOne.OAuthDesktop.main Login D-Bus service starting up
2009-09-18 21:14:12,592:592.880964279 UbuntuOne.Client.Applet Starting Ubuntu One client version 0.95.1
2009-09-18 21:14:24,720:720.123052597 UbuntuOne.OAuthDesktop.main maybe_login() D-Bus message received with realm='https://ubuntuone.com', consumer_key='ubuntuone'
2009-09-18 21:14:24,720:720.434904099 UbuntuOne.OAuthDesktop.main Initiating OAuth login in LoginProcessor
2009-09-18 21:14:24,720:720.567941666 UbuntuOne.OAuthDesktop.main Obtaining OAuth urls
2009-09-18 21:14:24,720:720.689058304 UbuntuOne.OAuthDesktop.main Fetching config URLs for realm='https://ubuntuone.com'
2009-09-18 21:14:24,720:720.896959305 UbuntuOne.OAuthDesktop.main Realm 'https://ubuntuone.com' is not in config
2009-09-18 21:14:24,721:721.205949783 UbuntuOne.OAuthDesktop.main OAuth URLs are: request='https://ubuntuone.com/oauth/request/', userauth='https://ubuntuone.com/oauth/authorize/', access='https://ubuntuone.com/oauth/access/', secret='hammertime'
2009-09-18 21:14:28,653:653.453111649 UbuntuOne.OAuthDesktop.auth auth.AuthorisationClient created with parameters realm='https://ubuntuone.com', request_token_url='https://ubuntuone.com/oauth/request/', user_authorisation_url='https://ubuntuone.com/oauth/authorize/',access_token_url='https://ubuntuone.com/oauth/access/', consumer_key='ubuntuone', callback_parent='<bound method LoginProcessor.got_token of <ubuntuone.oauthdesktop.main.LoginProcessor instance at 0xa2dd28c>>'
2009-09-18 21:14:28,653:653.803110123 UbuntuOne.OAuthDesktop.main Calling auth.client.ensure_access_token in thread
2009-09-18 21:14:28,673:673.891067505 UbuntuOne.OAuthDesktop.auth Trying to fetch the token from the keyring
2009-09-18 21:15:55,116:116.954088211 UbuntuOne.OAuthDesktop.auth Access token successfully found in the keyring
2009-09-18 21:15:55,117:117.424964905 UbuntuOne.OAuthDesktop.main Token retrieved, calling NewCredentials function
2009-09-18 21:15:55,117:117.588043213 UbuntuOne.OAuthDesktop.main Firing the NewCredentials signal
2009-09-18 21:55:07,923:923.261880875 UbuntuOne.OAuthDesktop.main Creating a LoginProcessor
2009-09-18 21:55:08,047:47.6651191711 UbuntuOne.OAuthDesktop.main Hooking libnotify
2009-09-18 21:55:08,052:52.0870685577 UbuntuOne.OAuthDesktop.main Getting configuration
2009-09-18 21:55:08,140:140.508890152 UbuntuOne.OAuthDesktop.main Login D-Bus service starting up
2009-09-18 21:55:08,364:364.208936691 UbuntuOne.Client.Applet Starting Ubuntu One client version 0.95.1
2009-09-18 21:55:23,078:78.0379772186 UbuntuOne.OAuthDesktop.main maybe_login() D-Bus message received with realm='https://ubuntuone.com', consumer_key='ubuntuone'
2009-09-18 21:55:23,078:78.3190727234 UbuntuOne.OAuthDesktop.main Initiating OAuth login in LoginProcessor
2009-09-18 21:55:23,078:78.4540176392 UbuntuOne.OAuthDesktop.main Obtaining OAuth urls
2009-09-18 21:55:23,078:78.5748958588 UbuntuOne.OAuthDesktop.main Fetching config URLs for realm='https://ubuntuone.com'
2009-09-18 21:55:23,078:78.7880420685 UbuntuOne.OAuthDesktop.main Realm 'https://ubuntuone.com' is not in config
2009-09-18 21:55:23,079:79.3359279633 UbuntuOne.OAuthDesktop.main OAuth URLs are: request='https://ubuntuone.com/oauth/request/', userauth='https://ubuntuone.com/oauth/authorize/', access='https://ubuntuone.com/oauth/access/', secret='hammertime'
2009-09-18 21:55:25,757:757.524013519 UbuntuOne.OAuthDesktop.auth auth.AuthorisationClient created with parameters realm='https://ubuntuone.com', request_token_url='https://ubuntuone.com/oauth/request/', user_authorisation_url='https://ubuntuone.com/oauth/authorize/',access_token_url='https://ubuntuone.com/oauth/access/', consumer_key='ubuntuone', callback_parent='<bound method LoginProcessor.got_token of <ubuntuone.oauthdesktop.main.LoginProcessor instance at 0x8fd228c>>'
2009-09-18 21:55:25,757:757.854938507 UbuntuOne.OAuthDesktop.main Calling auth.client.ensure_access_token in thread
2009-09-18 21:55:25,818:818.41301918 UbuntuOne.OAuthDesktop.auth Trying to fetch the token from the keyring
2009-09-18 21:55:25,819:819.556951523 UbuntuOne.OAuthDesktop.auth Access token successfully found in the keyring
2009-09-18 21:55:25,819:819.847106934 UbuntuOne.OAuthDesktop.main Token retrieved, calling NewCredentials function
2009-09-18 21:55:25,819:819.988965988 UbuntuOne.OAuthDesktop.main Firing the NewCredentials signal
2009-09-19 09:25:29,922:922.017097473 UbuntuOne.OAuthDesktop.main Creating a LoginProcessor
2009-09-19 09:25:30,057:57.1210384369 UbuntuOne.OAuthDesktop.main Hooking libnotify
2009-09-19 09:25:30,062:62.0820522308 UbuntuOne.OAuthDesktop.main Getting configuration
2009-09-19 09:25:30,150:150.110960007 UbuntuOne.OAuthDesktop.main Login D-Bus service starting up
2009-09-19 09:25:30,473:473.098993301 UbuntuOne.Client.Applet Starting Ubuntu One client version 0.95.1
2009-09-19 09:25:44,821:821.608066559 UbuntuOne.OAuthDesktop.main maybe_login() D-Bus message received with realm='https://ubuntuone.com', consumer_key='ubuntuone'
2009-09-19 09:25:44,821:821.938037872 UbuntuOne.OAuthDesktop.main Initiating OAuth login in LoginProcessor
2009-09-19 09:25:44,822:822.072029114 UbuntuOne.OAuthDesktop.main Obtaining OAuth urls
2009-09-19 09:25:44,822:822.192907333 UbuntuOne.OAuthDesktop.main Fetching config URLs for realm='https://ubuntuone.com'
2009-09-19 09:25:44,822:822.397947311 UbuntuOne.OAuthDesktop.main Realm 'https://ubuntuone.com' is not in config
2009-09-19 09:25:44,822:822.70693779 UbuntuOne.OAuthDesktop.main OAuth URLs are: request='https://ubuntuone.com/oauth/request/', userauth='https://ubuntuone.com/oauth/authorize/', access='https://ubuntuone.com/oauth/access/', secret='hammertime'
2009-09-19 09:25:47,657:657.277107239 UbuntuOne.OAuthDesktop.auth auth.AuthorisationClient created with parameters realm='https://ubuntuone.com', request_token_url='https://ubuntuone.com/oauth/request/', user_authorisation_url='https://ubuntuone.com/oauth/authorize/',access_token_url='https://ubuntuone.com/oauth/access/', consumer_key='ubuntuone', callback_parent='<bound method LoginProcessor.got_token of <ubuntuone.oauthdesktop.main.LoginProcessor instance at 0x905128c>>'
2009-09-19 09:25:47,657:657.654047012 UbuntuOne.OAuthDesktop.main Calling auth.client.ensure_access_token in thread
2009-09-19 09:25:47,903:903.698921204 UbuntuOne.OAuthDesktop.auth Trying to fetch the token from the keyring
2009-09-19 09:25:47,918:918.56098175 UbuntuOne.OAuthDesktop.auth Access token successfully found in the keyring
2009-09-19 09:25:47,919:919.054985046 UbuntuOne.OAuthDesktop.main Token retrieved, calling NewCredentials function
2009-09-19 09:25:47,919:919.19708252 UbuntuOne.OAuthDesktop.main Firing the NewCredentials signal
2009-09-20 08:36:34,942:942.122936249 UbuntuOne.OAuthDesktop.main Creating a LoginProcessor
2009-09-20 08:36:35,547:547.477960587 UbuntuOne.OAuthDesktop.main Hooking libnotify
2009-09-20 08:36:35,558:558.938980103 UbuntuOne.OAuthDesktop.main Getting configuration
2009-09-20 08:36:35,626:626.663923264 UbuntuOne.OAuthDesktop.main Login D-Bus service starting up
2009-09-20 08:36:35,640:640.544891357 UbuntuOne.Client.Applet Starting Ubuntu One client version 0.95.1
2009-09-20 08:36:50,824:824.067115784 UbuntuOne.OAuthDesktop.main maybe_login() D-Bus message received with realm='https://ubuntuone.com', consumer_key='ubuntuone'
2009-09-20 08:36:50,824:824.472904205 UbuntuOne.OAuthDesktop.main Initiating OAuth login in LoginProcessor
2009-09-20 08:36:50,824:824.609041214 UbuntuOne.OAuthDesktop.main Obtaining OAuth urls
2009-09-20 08:36:50,824:824.731111526 UbuntuOne.OAuthDesktop.main Fetching config URLs for realm='https://ubuntuone.com'
2009-09-20 08:36:50,824:824.937105179 UbuntuOne.OAuthDesktop.main Realm 'https://ubuntuone.com' is not in config
2009-09-20 08:36:50,825:825.244903564 UbuntuOne.OAuthDesktop.main OAuth URLs are: request='https://ubuntuone.com/oauth/request/', userauth='https://ubuntuone.com/oauth/authorize/', access='https://ubuntuone.com/oauth/access/', secret='hammertime'
2009-09-20 08:36:55,308:308.974981308 UbuntuOne.OAuthDesktop.auth auth.AuthorisationClient created with parameters realm='https://ubuntuone.com', request_token_url='https://ubuntuone.com/oauth/request/', user_authorisation_url='https://ubuntuone.com/oauth/authorize/',access_token_url='https://ubuntuone.com/oauth/access/', consumer_key='ubuntuone', callback_parent='<bound method LoginProcessor.got_token of <ubuntuone.oauthdesktop.main.LoginProcessor instance at 0x984b28c>>'
2009-09-20 08:36:59,915:915.400028229 UbuntuOne.OAuthDesktop.main Calling auth.client.ensure_access_token in thread
2009-09-20 08:37:00,213:213.527917862 UbuntuOne.OAuthDesktop.auth Trying to fetch the token from the keyring
2009-09-20 08:37:00,215:215.77501297 UbuntuOne.OAuthDesktop.auth Access token successfully found in the keyring
2009-09-20 08:37:00,216:216.494083405 UbuntuOne.OAuthDesktop.main Token retrieved, calling NewCredentials function
2009-09-20 08:37:00,216:216.888904572 UbuntuOne.OAuthDesktop.main Firing the NewCredentials signal
2009-09-21 07:43:22,639:639.878034592 UbuntuOne.OAuthDesktop.main Creating a LoginProcessor
2009-09-21 07:43:23,584:584.223031998 UbuntuOne.OAuthDesktop.main Hooking libnotify
2009-09-21 07:43:23,631:631.93488121 UbuntuOne.OAuthDesktop.main Getting configuration
2009-09-21 07:43:24,359:359.153985977 UbuntuOne.OAuthDesktop.main Login D-Bus service starting up
2009-09-21 07:43:24,372:372.720003128 UbuntuOne.Client.Applet Starting Ubuntu One client version 0.95.1
2009-09-21 07:43:38,098:98.8581180573 UbuntuOne.OAuthDesktop.main maybe_login() D-Bus message received with realm='https://ubuntuone.com', consumer_key='ubuntuone'
2009-09-21 07:43:38,099:99.1489887238 UbuntuOne.OAuthDesktop.main Initiating OAuth login in LoginProcessor
2009-09-21 07:43:38,099:99.2879867554 UbuntuOne.OAuthDesktop.main Obtaining OAuth urls
2009-09-21 07:43:38,099:99.4369983673 UbuntuOne.OAuthDesktop.main Fetching config URLs for realm='https://ubuntuone.com'
2009-09-21 07:43:38,099:99.6448993683 UbuntuOne.OAuthDesktop.main Realm 'https://ubuntuone.com' is not in config
2009-09-21 07:43:38,099:99.9538898468 UbuntuOne.OAuthDesktop.main OAuth URLs are: request='https://ubuntuone.com/oauth/request/', userauth='https://ubuntuone.com/oauth/authorize/', access='https://ubuntuone.com/oauth/access/', secret='hammertime'
2009-09-21 07:43:42,617:617.085933685 UbuntuOne.OAuthDesktop.auth auth.AuthorisationClient created with parameters realm='https://ubuntuone.com', request_token_url='https://ubuntuone.com/oauth/request/', user_authorisation_url='https://ubuntuone.com/oauth/authorize/',access_token_url='https://ubuntuone.com/oauth/access/', consumer_key='ubuntuone', callback_parent='<bound method LoginProcessor.got_token of <ubuntuone.oauthdesktop.main.LoginProcessor instance at 0x915228c>>'
2009-09-21 07:43:42,617:617.41900444 UbuntuOne.OAuthDesktop.main Calling auth.client.ensure_access_token in thread
2009-09-21 07:43:42,620:620.170116425 UbuntuOne.OAuthDesktop.auth Trying to fetch the token from the keyring
2009-09-21 07:44:13,492:492.060899734 UbuntuOne.OAuthDesktop.auth Access token successfully found in the keyring
2009-09-21 07:44:13,492:492.558002472 UbuntuOne.OAuthDesktop.main Token retrieved, calling NewCredentials function
2009-09-21 07:44:13,492:492.701053619 UbuntuOne.OAuthDesktop.main Firing the NewCredentials signal
2009-09-21 22:40:34,784:784.910917282 UbuntuOne.OAuthDesktop.main Creating a LoginProcessor
2009-09-21 22:40:34,912:912.574052811 UbuntuOne.OAuthDesktop.main Hooking libnotify
2009-09-21 22:40:34,917:917.876005173 UbuntuOne.OAuthDesktop.main Getting configuration
2009-09-21 22:40:34,980:980.473995209 UbuntuOne.OAuthDesktop.main Login D-Bus service starting up
2009-09-21 22:40:34,981:981.462001801 UbuntuOne.Client.Applet Starting Ubuntu One client version 0.95.1
2009-09-21 22:40:56,351:351.767063141 UbuntuOne.OAuthDesktop.main maybe_login() D-Bus message received with realm='https://ubuntuone.com', consumer_key='ubuntuone'
2009-09-21 22:40:56,493:493.453979492 UbuntuOne.OAuthDesktop.main Initiating OAuth login in LoginProcessor
2009-09-21 22:40:56,493:493.972063065 UbuntuOne.OAuthDesktop.main Obtaining OAuth urls
2009-09-21 22:40:56,494:494.35210228 UbuntuOne.OAuthDesktop.main Fetching config URLs for realm='https://ubuntuone.com'
2009-09-21 22:40:56,494:494.985103607 UbuntuOne.OAuthDesktop.main Realm 'https://ubuntuone.com' is not in config
2009-09-21 22:40:56,495:495.908975601 UbuntuOne.OAuthDesktop.main OAuth URLs are: request='https://ubuntuone.com/oauth/request/', userauth='https://ubuntuone.com/oauth/authorize/', access='https://ubuntuone.com/oauth/access/', secret='hammertime'
2009-09-21 22:41:00,158:158.612966537 UbuntuOne.OAuthDesktop.auth auth.AuthorisationClient created with parameters realm='https://ubuntuone.com', request_token_url='https://ubuntuone.com/oauth/request/', user_authorisation_url='https://ubuntuone.com/oauth/authorize/',access_token_url='https://ubuntuone.com/oauth/access/', consumer_key='ubuntuone', callback_parent='<bound method LoginProcessor.got_token of <ubuntuone.oauthdesktop.main.LoginProcessor instance at 0x9fd328c>>'
2009-09-21 22:41:00,158:158.936023712 UbuntuOne.OAuthDesktop.main Calling auth.client.ensure_access_token in thread
2009-09-21 22:41:00,341:341.522932053 UbuntuOne.OAuthDesktop.auth Trying to fetch the token from the keyring
2009-09-21 22:41:00,342:342.778921127 UbuntuOne.OAuthDesktop.auth Access token successfully found in the keyring
2009-09-21 22:41:00,343:343.091964722 UbuntuOne.OAuthDesktop.main Token retrieved, calling NewCredentials function
2009-09-21 22:41:00,343:343.230009079 UbuntuOne.OAuthDesktop.main Firing the NewCredentials signal
2009-09-25 17:11:30,454:454.596042633 UbuntuOne.OAuthDesktop.main Creating a LoginProcessor
2009-09-25 17:11:31,058:58.4580898285 UbuntuOne.OAuthDesktop.main Hooking libnotify
2009-09-25 17:11:31,063:63.5509490967 UbuntuOne.OAuthDesktop.main Getting configuration
2009-09-25 17:11:31,303:303.030014038 UbuntuOne.OAuthDesktop.main Login D-Bus service starting up
2009-09-25 17:11:31,303:303.893089294 UbuntuOne.Client.Applet Starting Ubuntu One client version 0.95.1
2009-09-25 17:11:49,361:361.643075943 UbuntuOne.OAuthDesktop.main maybe_login() D-Bus message received with realm='https://ubuntuone.com', consumer_key='ubuntuone'
2009-09-25 17:11:49,361:361.953020096 UbuntuOne.OAuthDesktop.main Initiating OAuth login in LoginProcessor
2009-09-25 17:11:49,362:362.086057663 UbuntuOne.OAuthDesktop.main Obtaining OAuth urls
2009-09-25 17:11:49,362:362.205982208 UbuntuOne.OAuthDesktop.main Fetching config URLs for realm='https://ubuntuone.com'
2009-09-25 17:11:49,362:362.411975861 UbuntuOne.OAuthDesktop.main Realm 'https://ubuntuone.com' is not in config
2009-09-25 17:11:49,362:362.720012665 UbuntuOne.OAuthDesktop.main OAuth URLs are: request='https://ubuntuone.com/oauth/request/', userauth='https://ubuntuone.com/oauth/authorize/', access='https://ubuntuone.com/oauth/access/', secret='hammertime'
2009-09-25 17:11:50,952:952.266931534 UbuntuOne.OAuthDesktop.auth auth.AuthorisationClient created with parameters realm='https://ubuntuone.com', request_token_url='https://ubuntuone.com/oauth/request/', user_authorisation_url='https://ubuntuone.com/oauth/authorize/',access_token_url='https://ubuntuone.com/oauth/access/', consumer_key='ubuntuone', callback_parent='<bound method LoginProcessor.got_token of <ubuntuone.oauthdesktop.main.LoginProcessor instance at 0xa73f3ac>>'
2009-09-25 17:11:50,952:952.579975128 UbuntuOne.OAuthDesktop.main Calling auth.client.ensure_access_token in thread
2009-09-25 17:11:50,954:954.937934875 UbuntuOne.OAuthDesktop.auth Trying to fetch the token from the keyring
2009-09-25 17:11:54,278:278.559923172 UbuntuOne.OAuthDesktop.auth Access token successfully found in the keyring
2009-09-25 17:11:54,278:278.986930847 UbuntuOne.OAuthDesktop.main Token retrieved, calling NewCredentials function
2009-09-25 17:11:54,279:279.128074646 UbuntuOne.OAuthDesktop.main Firing the NewCredentials signal
2009-09-26 11:40:24,610:610.414028168 UbuntuOne.OAuthDesktop.main Creating a LoginProcessor
2009-09-26 11:40:25,172:172.890901566 UbuntuOne.OAuthDesktop.main Hooking libnotify
2009-09-26 11:40:25,181:181.360960007 UbuntuOne.OAuthDesktop.main Getting configuration
2009-09-26 11:40:25,360:360.085010529 UbuntuOne.OAuthDesktop.main Login D-Bus service starting up
2009-09-26 11:40:25,361:361.932039261 UbuntuOne.Client.Applet Starting Ubuntu One client version 0.95.1
2009-09-26 11:40:38,150:150.527000427 UbuntuOne.OAuthDesktop.main maybe_login() D-Bus message received with realm='https://ubuntuone.com', consumer_key='ubuntuone'
2009-09-26 11:40:38,150:150.82192421 UbuntuOne.OAuthDesktop.main Initiating OAuth login in LoginProcessor
2009-09-26 11:40:38,150:150.954961777 UbuntuOne.OAuthDesktop.main Obtaining OAuth urls
2009-09-26 11:40:38,151:151.074886322 UbuntuOne.OAuthDesktop.main Fetching config URLs for realm='https://ubuntuone.com'
2009-09-26 11:40:38,151:151.282072067 UbuntuOne.OAuthDesktop.main Realm 'https://ubuntuone.com' is not in config
2009-09-26 11:40:38,151:151.590108871 UbuntuOne.OAuthDesktop.main OAuth URLs are: request='https://ubuntuone.com/oauth/request/', userauth='https://ubuntuone.com/oauth/authorize/', access='https://ubuntuone.com/oauth/access/', secret='hammertime'
2009-09-26 11:40:44,257:257.478952408 UbuntuOne.OAuthDesktop.auth auth.AuthorisationClient created with parameters realm='https://ubuntuone.com', request_token_url='https://ubuntuone.com/oauth/request/', user_authorisation_url='https://ubuntuone.com/oauth/authorize/',access_token_url='https://ubuntuone.com/oauth/access/', consumer_key='ubuntuone', callback_parent='<bound method LoginProcessor.got_token of <ubuntuone.oauthdesktop.main.LoginProcessor instance at 0x991934c>>'
2009-09-26 11:40:44,257:257.91311264 UbuntuOne.OAuthDesktop.main Calling auth.client.ensure_access_token in thread
2009-09-26 11:40:44,537:537.363052368 UbuntuOne.OAuthDesktop.auth Trying to fetch the token from the keyring
2009-09-26 11:40:44,540:540.729999542 UbuntuOne.OAuthDesktop.auth Access token successfully found in the keyring
2009-09-26 11:40:44,541:541.131019592 UbuntuOne.OAuthDesktop.main Token retrieved, calling NewCredentials function
2009-09-26 11:40:44,541:541.26906395 UbuntuOne.OAuthDesktop.main Firing the NewCredentials signal
2009-09-26 13:40:40,309:309.000015259 UbuntuOne.OAuthDesktop.main Creating a LoginProcessor
2009-09-26 13:40:40,652:652.303934097 UbuntuOne.OAuthDesktop.main Hooking libnotify
2009-09-26 13:40:40,657:657.855033875 UbuntuOne.OAuthDesktop.main Getting configuration
2009-09-26 13:40:40,793:793.766975403 UbuntuOne.OAuthDesktop.main Login D-Bus service starting up
2009-09-26 13:40:40,794:794.624090195 UbuntuOne.Client.Applet Starting Ubuntu One client version 0.95.1
2009-09-26 13:40:54,606:606.021881104 UbuntuOne.OAuthDesktop.main maybe_login() D-Bus message received with realm='https://ubuntuone.com', consumer_key='ubuntuone'
2009-09-26 13:40:54,606:606.327056885 UbuntuOne.OAuthDesktop.main Initiating OAuth login in LoginProcessor
2009-09-26 13:40:54,606:606.461048126 UbuntuOne.OAuthDesktop.main Obtaining OAuth urls
2009-09-26 13:40:54,606:606.583118439 UbuntuOne.OAuthDesktop.main Fetching config URLs for realm='https://ubuntuone.com'
2009-09-26 13:40:54,606:606.790065765 UbuntuOne.OAuthDesktop.main Realm 'https://ubuntuone.com' is not in config
2009-09-26 13:40:54,607:607.134103775 UbuntuOne.OAuthDesktop.main OAuth URLs are: request='https://ubuntuone.com/oauth/request/', userauth='https://ubuntuone.com/oauth/authorize/', access='https://ubuntuone.com/oauth/access/', secret='hammertime'
2009-09-26 13:40:58,556:556.333065033 UbuntuOne.OAuthDesktop.auth auth.AuthorisationClient created with parameters realm='https://ubuntuone.com', request_token_url='https://ubuntuone.com/oauth/request/', user_authorisation_url='https://ubuntuone.com/oauth/authorize/',access_token_url='https://ubuntuone.com/oauth/access/', consumer_key='ubuntuone', callback_parent='<bound method LoginProcessor.got_token of <ubuntuone.oauthdesktop.main.LoginProcessor instance at 0x97a734c>>'
2009-09-26 13:40:58,557:557.039022446 UbuntuOne.OAuthDesktop.main Calling auth.client.ensure_access_token in thread
2009-09-26 13:40:58,629:629.909038544 UbuntuOne.OAuthDesktop.auth Trying to fetch the token from the keyring
2009-09-26 13:40:58,633:633.662939072 UbuntuOne.OAuthDesktop.auth Access token successfully found in the keyring
2009-09-26 13:40:58,634:634.140014648 UbuntuOne.OAuthDesktop.main Token retrieved, calling NewCredentials function
2009-09-26 13:40:58,634:634.310007095 UbuntuOne.OAuthDesktop.main Firing the NewCredentials signal
2009-09-26 13:56:54,612:612.176895142 UbuntuOne.OAuthDesktop.main Creating a LoginProcessor
2009-09-26 13:56:55,179:179.229974747 UbuntuOne.OAuthDesktop.main Hooking libnotify
2009-09-26 13:56:55,184:184.322118759 UbuntuOne.OAuthDesktop.main Getting configuration
2009-09-26 13:56:55,453:453.18198204 UbuntuOne.OAuthDesktop.main Login D-Bus service starting up
2009-09-26 13:56:55,454:454.051971436 UbuntuOne.Client.Applet Starting Ubuntu One client version 0.95.1
2009-09-26 13:57:08,058:58.443069458 UbuntuOne.OAuthDesktop.main maybe_login() D-Bus message received with realm='https://ubuntuone.com', consumer_key='ubuntuone'
2009-09-26 13:57:08,058:58.7511062622 UbuntuOne.OAuthDesktop.main Initiating OAuth login in LoginProcessor
2009-09-26 13:57:08,059:59.103012085 UbuntuOne.OAuthDesktop.main Obtaining OAuth urls
2009-09-26 13:57:08,059:59.2310428619 UbuntuOne.OAuthDesktop.main Fetching config URLs for realm='https://ubuntuone.com'
2009-09-26 13:57:08,059:59.4398975372 UbuntuOne.OAuthDesktop.main Realm 'https://ubuntuone.com' is not in config
2009-09-26 13:57:08,059:59.7770214081 UbuntuOne.OAuthDesktop.main OAuth URLs are: request='https://ubuntuone.com/oauth/request/', userauth='https://ubuntuone.com/oauth/authorize/', access='https://ubuntuone.com/oauth/access/', secret='hammertime'
2009-09-26 13:57:09,305:305.051088333 UbuntuOne.OAuthDesktop.auth auth.AuthorisationClient created with parameters realm='https://ubuntuone.com', request_token_url='https://ubuntuone.com/oauth/request/', user_authorisation_url='https://ubuntuone.com/oauth/authorize/',access_token_url='https://ubuntuone.com/oauth/access/', consumer_key='ubuntuone', callback_parent='<bound method LoginProcessor.got_token of <ubuntuone.oauthdesktop.main.LoginProcessor instance at 0x8b8734c>>'
2009-09-26 13:57:09,305:305.397033691 UbuntuOne.OAuthDesktop.main Calling auth.client.ensure_access_token in thread
2009-09-26 13:57:09,336:336.10701561 UbuntuOne.OAuthDesktop.auth Trying to fetch the token from the keyring
2009-09-26 13:57:09,444:444.998025894 UbuntuOne.OAuthDesktop.auth Access token successfully found in the keyring
2009-09-26 13:57:09,445:445.472002029 UbuntuOne.OAuthDesktop.main Token retrieved, calling NewCredentials function
2009-09-26 13:57:09,445:445.611953735 UbuntuOne.OAuthDesktop.main Firing the NewCredentials signal
2009-09-26 14:10:40,937:937.877893448 UbuntuOne.OAuthDesktop.main Creating a LoginProcessor
2009-09-26 14:10:41,601:601.517915726 UbuntuOne.OAuthDesktop.main Hooking libnotify
2009-09-26 14:10:41,612:612.62011528 UbuntuOne.OAuthDesktop.main Getting configuration
2009-09-26 14:10:41,798:798.074960709 UbuntuOne.OAuthDesktop.main Login D-Bus service starting up
2009-09-26 14:10:41,799:799.957036972 UbuntuOne.Client.Applet Starting Ubuntu One client version 0.95.1
2009-09-26 14:10:48,886:886.914014816 UbuntuOne.OAuthDesktop.main maybe_login() D-Bus message received with realm='https://ubuntuone.com', consumer_key='ubuntuone'
2009-09-26 14:10:49,477:477.703094482 UbuntuOne.OAuthDesktop.main Initiating OAuth login in LoginProcessor
2009-09-26 14:10:49,477:477.97203064 UbuntuOne.OAuthDesktop.main Obtaining OAuth urls
2009-09-26 14:10:49,478:478.096008301 UbuntuOne.OAuthDesktop.main Fetching config URLs for realm='https://ubuntuone.com'
2009-09-26 14:10:49,478:478.324890137 UbuntuOne.OAuthDesktop.main Realm 'https://ubuntuone.com' is not in config
2009-09-26 14:10:49,478:478.638887405 UbuntuOne.OAuthDesktop.main OAuth URLs are: request='https://ubuntuone.com/oauth/request/', userauth='https://ubuntuone.com/oauth/authorize/', access='https://ubuntuone.com/oauth/access/', secret='hammertime'
2009-09-26 14:10:53,873:873.620033264 UbuntuOne.OAuthDesktop.auth auth.AuthorisationClient created with parameters realm='https://ubuntuone.com', request_token_url='https://ubuntuone.com/oauth/request/', user_authorisation_url='https://ubuntuone.com/oauth/authorize/',access_token_url='https://ubuntuone.com/oauth/access/', consumer_key='ubuntuone', callback_parent='<bound method LoginProcessor.got_token of <ubuntuone.oauthdesktop.main.LoginProcessor instance at 0xa7a734c>>'
2009-09-26 14:10:53,873:873.944997787 UbuntuOne.OAuthDesktop.main Calling auth.client.ensure_access_token in thread
2009-09-26 14:10:53,965:965.989112854 UbuntuOne.OAuthDesktop.auth Trying to fetch the token from the keyring
2009-09-26 14:13:15,919:919.75903511 UbuntuOne.OAuthDesktop.auth Access token successfully found in the keyring
2009-09-26 14:13:15,920:920.216083527 UbuntuOne.OAuthDesktop.main Token retrieved, calling NewCredentials function
2009-09-26 14:13:15,920:920.357942581 UbuntuOne.OAuthDesktop.main Firing the NewCredentials signal
2009-09-26 15:46:59,057:57.797908783 UbuntuOne.OAuthDesktop.main Creating a LoginProcessor
2009-09-26 15:46:59,402:402.981042862 UbuntuOne.OAuthDesktop.main Hooking libnotify
2009-09-26 15:46:59,555:555.577039719 UbuntuOne.OAuthDesktop.main Getting configuration
2009-09-26 15:46:59,765:765.1450634 UbuntuOne.OAuthDesktop.main Login D-Bus service starting up
2009-09-26 15:46:59,766:766.088962555 UbuntuOne.Client.Applet Starting Ubuntu One client version 0.95.1
2009-09-26 15:47:08,313:313.853979111 UbuntuOne.OAuthDesktop.main maybe_login() D-Bus message received with realm='https://ubuntuone.com', consumer_key='ubuntuone'
2009-09-26 15:47:08,314:314.177036285 UbuntuOne.OAuthDesktop.main Initiating OAuth login in LoginProcessor
2009-09-26 15:47:08,314:314.30888176 UbuntuOne.OAuthDesktop.main Obtaining OAuth urls
2009-09-26 15:47:08,314:314.464092255 UbuntuOne.OAuthDesktop.main Fetching config URLs for realm='https://ubuntuone.com'
2009-09-26 15:47:08,314:314.673900604 UbuntuOne.OAuthDesktop.main Realm 'https://ubuntuone.com' is not in config
2009-09-26 15:47:08,315:315.206050873 UbuntuOne.OAuthDesktop.main OAuth URLs are: request='https://ubuntuone.com/oauth/request/', userauth='https://ubuntuone.com/oauth/authorize/', access='https://ubuntuone.com/oauth/access/', secret='hammertime'
2009-09-26 15:47:11,995:995.102882385 UbuntuOne.OAuthDesktop.auth auth.AuthorisationClient created with parameters realm='https://ubuntuone.com', request_token_url='https://ubuntuone.com/oauth/request/', user_authorisation_url='https://ubuntuone.com/oauth/authorize/',access_token_url='https://ubuntuone.com/oauth/access/', consumer_key='ubuntuone', callback_parent='<bound method LoginProcessor.got_token of <ubuntuone.oauthdesktop.main.LoginProcessor instance at 0x927434c>>'
2009-09-26 15:47:11,995:995.440006256 UbuntuOne.OAuthDesktop.main Calling auth.client.ensure_access_token in thread
2009-09-26 15:47:12,073:73.9378929138 UbuntuOne.OAuthDesktop.auth Trying to fetch the token from the keyring
2009-09-26 15:47:14,836:836.395978928 UbuntuOne.OAuthDesktop.auth Access token successfully found in the keyring
2009-09-26 15:47:14,836:836.846113205 UbuntuOne.OAuthDesktop.main Token retrieved, calling NewCredentials function
2009-09-26 15:47:14,836:836.985111237 UbuntuOne.OAuthDesktop.main Firing the NewCredentials signal
2009-09-28 07:44:13,788:788.693904877 UbuntuOne.OAuthDesktop.main Creating a LoginProcessor
2009-09-28 07:44:14,363:363.249063492 UbuntuOne.OAuthDesktop.main Hooking libnotify
2009-09-28 07:44:14,717:717.340946198 UbuntuOne.OAuthDesktop.main Getting configuration
2009-09-28 07:44:14,902:902.731895447 UbuntuOne.OAuthDesktop.main Login D-Bus service starting up
2009-09-28 07:44:14,904:904.0350914 UbuntuOne.Client.Applet Starting Ubuntu One client version 0.95.1
2009-09-28 07:44:25,879:879.35590744 UbuntuOne.OAuthDesktop.main maybe_login() D-Bus message received with realm='https://ubuntuone.com', consumer_key='ubuntuone'
2009-09-28 07:44:25,908:908.144950867 UbuntuOne.OAuthDesktop.main Initiating OAuth login in LoginProcessor
2009-09-28 07:44:25,908:908.64109993 UbuntuOne.OAuthDesktop.main Obtaining OAuth urls
2009-09-28 07:44:25,911:911.787033081 UbuntuOne.OAuthDesktop.main Fetching config URLs for realm='https://ubuntuone.com'
2009-09-28 07:44:25,912:912.250995636 UbuntuOne.OAuthDesktop.main Realm 'https://ubuntuone.com' is not in config
2009-09-28 07:44:25,912:912.926912308 UbuntuOne.OAuthDesktop.main OAuth URLs are: request='https://ubuntuone.com/oauth/request/', userauth='https://ubuntuone.com/oauth/authorize/', access='https://ubuntuone.com/oauth/access/', secret='hammertime'
2009-09-28 07:44:34,718:718.137025833 UbuntuOne.OAuthDesktop.auth auth.AuthorisationClient created with parameters realm='https://ubuntuone.com', request_token_url='https://ubuntuone.com/oauth/request/', user_authorisation_url='https://ubuntuone.com/oauth/authorize/',access_token_url='https://ubuntuone.com/oauth/access/', consumer_key='ubuntuone', callback_parent='<bound method LoginProcessor.got_token of <ubuntuone.oauthdesktop.main.LoginProcessor instance at 0x9f2c34c>>'
2009-09-28 07:44:34,718:718.617916107 UbuntuOne.OAuthDesktop.main Calling auth.client.ensure_access_token in thread
2009-09-28 07:44:34,823:823.673009872 UbuntuOne.OAuthDesktop.auth Trying to fetch the token from the keyring
2009-09-28 07:44:34,845:845.251083374 UbuntuOne.OAuthDesktop.auth Access token successfully found in the keyring
2009-09-28 07:44:34,845:845.680952072 UbuntuOne.OAuthDesktop.main Token retrieved, calling NewCredentials function
2009-09-28 07:44:34,845:845.818996429 UbuntuOne.OAuthDesktop.main Firing the NewCredentials signal
2009-10-10 23:00:06,134:134.677886963 UbuntuOne.OAuthDesktop.main Creating a LoginProcessor
2009-10-10 23:00:06,510:510.273933411 UbuntuOne.OAuthDesktop.main Hooking libnotify
2009-10-10 23:00:06,525:525.290966034 UbuntuOne.OAuthDesktop.main Getting configuration
2009-10-10 23:00:06,563:563.283920288 UbuntuOne.OAuthDesktop.main Login D-Bus service starting up
2009-10-10 23:00:06,564:564.378023148 UbuntuOne.Client.Applet Starting Ubuntu One client version 0.96.0
2009-10-10 23:00:22,383:383.48698616 UbuntuOne.OAuthDesktop.main maybe_login() D-Bus message received with realm='https://ubuntuone.com', consumer_key='ubuntuone'
2009-10-10 23:00:22,383:383.815050125 UbuntuOne.OAuthDesktop.main Initiating OAuth login in LoginProcessor
2009-10-10 23:00:22,383:383.943080902 UbuntuOne.OAuthDesktop.main Obtaining OAuth urls
2009-10-10 23:00:22,384:384.063005447 UbuntuOne.OAuthDesktop.main Fetching config URLs for realm='https://ubuntuone.com'
2009-10-10 23:00:22,384:384.274959564 UbuntuOne.OAuthDesktop.main Realm 'https://ubuntuone.com' is not in config
2009-10-10 23:00:22,384:384.86790657 UbuntuOne.OAuthDesktop.main OAuth URLs are: request='https://ubuntuone.com/oauth/request/', userauth='https://ubuntuone.com/oauth/authorize/', access='https://ubuntuone.com/oauth/access/', secret='hammertime'
2009-10-10 23:00:25,683:683.096885681 UbuntuOne.OAuthDesktop.auth auth.AuthorisationClient created with parameters realm='https://ubuntuone.com', request_token_url='https://ubuntuone.com/oauth/request/', user_authorisation_url='https://ubuntuone.com/oauth/authorize/',access_token_url='https://ubuntuone.com/oauth/access/', consumer_key='ubuntuone', callback_parent='<bound method LoginProcessor.got_token of <ubuntuone.oauthdesktop.main.LoginProcessor instance at 0xa36228c>>'
2009-10-10 23:00:25,683:683.710098267 UbuntuOne.OAuthDesktop.main Calling auth.client.ensure_access_token in thread
2009-10-10 23:00:25,687:687.016010284 UbuntuOne.OAuthDesktop.auth Trying to fetch the token from the keyring
2009-10-10 23:00:25,689:689.033031464 UbuntuOne.OAuthDesktop.auth Access token successfully found in the keyring
2009-10-10 23:00:25,689:689.721107483 UbuntuOne.OAuthDesktop.main Token retrieved, calling NewCredentials function
2009-10-10 23:00:25,690:690.11092186 UbuntuOne.OAuthDesktop.main Firing the NewCredentials signal
2009-10-10 23:00:25,696:696.727991104 UbuntuOne.Client.Applet Not adding desktopcouch pairing since desktopcouch is not installed
Starting Ubuntu One client version 1.0.1
Starting Ubuntu One client version 1.0.1
Starting Ubuntu One client version 1.0.2
Starting Ubuntu One client version 1.0.2
Starting Ubuntu One client version 1.0.2
Starting Ubuntu One client version 1.0.2
Starting Ubuntu One client version 1.0.2
Starting Ubuntu One client version 1.0.2
Starting Ubuntu One client version 1.0.2
Starting Ubuntu One client version 1.0.2
Starting Ubuntu One client version 1.0.2
Starting Ubuntu One client version 1.0.2
Starting Ubuntu One client version 1.0.2
Starting Ubuntu One client version 1.0.2
Starting Ubuntu One client version 1.0.2
Starting Ubuntu One client version 1.0.2
Starting Ubuntu One client version 1.0.2
Starting Ubuntu One client version 1.0.2
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Starting Ubuntu One client version 1.0.2
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Starting Ubuntu One client version 1.0.2
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Starting Ubuntu One client version 1.0.2
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Starting Ubuntu One client version 1.0.2
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Starting Ubuntu One client version 1.0.2
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Starting Ubuntu One client version 1.0.2
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Starting Ubuntu One client version 1.0.2
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Starting Ubuntu One client version 1.0.2
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Starting Ubuntu One client version 1.0.2
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Starting Ubuntu One client version 1.0.2
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Starting Ubuntu One client version 1.0.2
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Starting Ubuntu One client version 1.0.2
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Starting Ubuntu One client version 1.0.2
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Starting Ubuntu One client version 1.0.2
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Starting Ubuntu One client version 1.0.2
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Starting Ubuntu One client version 1.0.2
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Starting Ubuntu One client version 1.0.2
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Starting Ubuntu One client version 1.0.2
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Starting Ubuntu One client version 1.0.2
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Starting Ubuntu One client version 1.0.2
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Starting Ubuntu One client version 1.0.2
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
DBus Error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.