[01:46] <mwhudson> queues: metadata: 63695; content: 75231; hash: 0
[01:46] <mwhudson> the metadata queue is going down at the rate of about 15 every 2 minutes
[01:47] <mwhudson> at this rate, the queue will be empty in 6 days
[01:48] <mwhudson> Chipaca: does this mean anything to you?
[03:49] <Mahjongg> hello I have synced folder on my desktop on PC A which is connected to the same u1 account as PC B and PC C. PC A and PC B can see the synced folder but C can't. What could be the reason?
[03:49] <Mahjongg> I tried creating the folder in PC C and then doing u1sdtool --refresh thatFolder but did not work
[06:42] <lahwran> how do I check if the ubuntu one client is running?
[06:42] <lahwran> I suspect lubuntu is not starting it
[06:43] <mwhudson> lahwran: u1sdtool -s
[06:46] <lahwran> thanks
[07:01] <lahwran> argh. http://www.pasteall.org/15081
[07:06] <lahwran> any idea what could be causing those dbus errors?
[07:14] <duanedesign> hello lahwran
[07:14] <lahwran> hello
[07:15] <lahwran> duanedesign, have an answer, or are you just saying hi? :D
[07:15] <duanedesign> lahwran: try :  u1sdtool -q
[07:15] <duanedesign> both :)
[07:15] <lahwran> ok.
[07:15] <duanedesign> then:  u1sdtool -c
[07:16] <lahwran> taking a long time on -c ...
[07:16] <duanedesign> you usually get that dbus error when the syncdaemon is too busy doing other stuff to take your command
[07:16] <lahwran> o.O
[07:16] <lahwran> what could that be?
[07:16] <lahwran> same dbus error.
[07:16] <lahwran> what would it be doing right after startup?
[07:17] <lahwran> I mean, ubuntu one hasn't worked on this lappy for 3 days
[07:18] <duanedesign> ok
[07:18] <duanedesign> try u1sdtool -q  again
[07:18] <lahwran> done
[07:18] <duanedesign> then run :  ps aux | grep ubu
[07:19] <duanedesign> 1 of the processes will be  grep ubu
[07:19] <duanedesign> but are there others?
[07:19] <lahwran> I know my command line ;)
[07:19] <duanedesign> :)
[07:20] <lahwran> there are others; they all match because of 'lubuntu'
[07:20] <duanedesign> oops
[07:20] <duanedesign> guess that is not to useful then
[07:20] <lahwran> O.o
[07:21] <lahwran> running -q again .. without having manually started the syncdaemon .. says it quit.
[07:28] <wgrant> So.
[07:28] <wgrant> Contacts have been down for roughly four months now.
[07:28] <wgrant> WTF?
[07:29] <lahwran> oh ...
[07:29] <lahwran> it may be gnome-keyring
[07:29] <lahwran> that was the answer! D
[07:29] <lahwran> :D*
[07:30] <lahwran> yay!
[07:31] <duanedesign> lahwran: ahh, was the daemon not running/
[07:31] <lahwran> it appears not.
[07:31] <duanedesign> wgrant: yes it is very frustrating
[07:32] <lahwran> I have had some weird boot problems ever since my semi-fail attempt to speed up the boot process; not sure what I broke, but I appear to have broken something.
[07:33] <wgrant> duanedesign: That's not what I'd call it.
[07:34] <duanedesign> lahwran: a good log file to look at if you have an issue with U1 is ~/.cache/ubuntuone/log/syncdaemon-exceptions.log
[07:35] <duanedesign> lahwran: you might find gnomekeyring.IOError from the gnome-keyring issue
[07:44] <lahwran> it's been 'processing queues' for like 10 minutes now
[07:53] <duanedesign> lahwran: u1sdtool -s shows 'With user With network'?
[07:54] <lahwran> yes
[07:54] <lahwran> looks like it just took 10 minutes
[07:55] <duanedesign> i like to use:  u1sdtool --waiting-metadata | wc -l
[07:55] <duanedesign> and: u1sdtool --waiting-content | wc -l
[07:56] <duanedesign> to see how many items are in the queue
[07:56] <duanedesign> it is a good way to gauge progress as the numbers should geet smaller over time. It processes the metadata first, then the content
[08:41] <duanedesign> ajmitch: you were the one working on getting Ubuntu One into Debian, correct?
[08:42] <duanedesign> bug 412424
[08:42] <ubot4> Launchpad bug 412424 in ubuntuone-client "Please support Debian too (affects: 2) (heat: 7)" [Undecided,New] https://launchpad.net/bugs/412424
[10:26] <rye> wooow, paste.ubuntu.com is shiny!
[10:45] <mandel_> rye, wow, the mush have just changed it, I was using it like 5 min ago and look as usual
[19:39] <ericedge> looking at the ubuntu one api slides from oscon 2009, it appears there's an open api I can use for ubuntu one, but there's no indication of a server name.
[19:39] <ericedge> I have a test account with ubuntu one now; where can I find more info on the api?
[19:42] <verterok> ericedge: hi, let me check the slides
[19:45] <verterok> ericedge: for the couchdb stuff?
[19:45] <ericedge> yeah; there's reference to simply doing an HTTP PUT against a path, but no server name is provided.
[19:46] <verterok> rye: do you know how to do that ^ ?
[19:46] <ericedge> I'm under the (possibly mistaken?) impression that Canonical has a server somewhere I could test against
[19:47] <verterok> ericedge: you can install desktopcouch and play with your local couchdb server
[19:47] <rye> ericedge, there are couchdb servers in canonical dc that provide the same API that your local couchdb will do. Currently direct access to couchdb api is restricted while the service is being switched to a newer version (this is actually happening as we are talking)
[19:48] <ericedge> ok, yeah, I saw that some of the services are down currently, that makes sense.
[19:49] <ericedge> I think I'll just download the client source and dig through that for some ideas.  Thanks for the help!
[19:50] <rye> ericedge, the file sync client is separated from couchdb
[19:51] <ericedge> that also makes sense.  Shucks.
[19:54] <ericedge> allrighty, I'll dig down a different path; I thank you sincerely for your help!
[19:56] <rye> ericedge, you are welcome, feel free to ask any ubuntuone-related questions here :)
[20:09] <Chipaca> ericedge: typically what you'd do is interact with your local couch and then let it replicate
[20:09] <Chipaca> ericedge: our (canonical) servers are not the only ones you could have set up to replicate against
[20:09] <Chipaca> ericedge: e.g. you could be replicating locally to other machines as well as to the cloud
[20:10] <Chipaca> ericedge: there's an app in desktopcouch-tools that lets you pair couches to set that up easily
[20:10] <Chipaca> ericedge: the process is similar to bluetooth pairing
[20:52] <ericedge> Chipaca: Cool, thanks for the tips!
[20:53] <Chipaca> ericedge: furthermore, couch.io providers (for now) free couchdb instances, you could sync to those as well as or instead of the canonical ones
[21:00] <ericedge> rockin', thx