[04:40] <cellofellow> How do I remove a specific couchdb database from Ubuntu One? I need to purge the settings from an app (gwibber) but whenever I remove them from my desktopcouch they get repopulated from ubuntu one.
[04:56] <beuno> cellofellow, one sec, I'll fetch you a link
[04:57] <beuno> http://www.freedesktop.org/wiki/Specifications/desktopcouch/Documentation/Troubleshooting?action=AttachFile&do=view&target=ubuntuone-couchdb-query
[04:57] <beuno> get that
[04:57] <beuno> and then run: python ubuntuone-couchdb-query --http-method=DELETE dbname
[04:58] <beuno> I think gwibber's dbname would be gwibber_messages
[04:59] <cellofellow> ok, I'll try this
[05:01] <cellofellow> that worked, thanks
[05:01] <cellofellow> wish there was an interface in the ubuntu one website to see all databases in ubuntu one, not just contacts and notes.
[05:02] <beuno> there will be  :)
[05:03] <cellofellow> ok :)
[05:05] <cellofellow> will the web interface get faster too? currently it
[05:05] <cellofellow> currently it's very sluggish, especially compared to dropbox.
[06:28] <Tig3rzhark> I'm having trouble logging into ubuntuone
[06:29] <Tig3rzhark> Every time I try to login, I get this error id (Error ID: 1536carambola3)
[06:35] <kermiac> hi. The OP in bug 523361 says this issue has now been resolved. Looking through the bug workflow, I don't see if it's appropriate for me to set this to "fix released" or something else as the OP didn't post any logs or advise which version they were having this issue with
[08:29] <rye> hm, I wonder why syncdaemon sometimes recreates the folders on the local system that were removed previously. No files are downloaded from the server, only folders are brought back
[09:46] <kermiac> The OP in bug 523361 says this issue has now been resolved. Looking through the bug workflow, I don't see if it's appropriate for me (as a triager) to set this to "fix released" or something else as the OP didn't post any logs or advise which version they were having this issue with
[09:47] <kermiac> The OP said "It said something about having a build the cloud was not prepared for yet - that lasted about a week - then everything mysteriously went away." so I believe a newer version has fixed the OP's issue
[09:49] <rye> kermiac, I'll deal with it - it is a dup of bug #462828 - he was given 'Capabilities Mismatch' error
[09:49] <rye> kermiac, thanks!
[09:49] <kermiac> ok, np... ty rye :)
[10:01] <persia> .names
[10:01] <persia> Hi!  I've seen a lot of discussion requesting private branches from launchpad.
[10:01] <persia> I was wondering if there were any obstacles to hosting a bzr branch in one's Ubuntu One repository?
[10:50] <duanedesign> hello persia
[10:52] <persia> Hey duanedesign.  You don't happen to know about hosting branches in ubuntuone, do you?
[10:54] <duanedesign> persia: i have seen bug reports on this issue. But those might be more of a one off problem someone had.
[10:55] <persia> duanedesign: Can you point me at any?
[10:55] <persia> I believe it should just work, but I'm curious if there's some data parsing happening in the ubuntuone protocol that might cause issues, etc.
[10:55] <duanedesign> rye: good day. Do you know anything about hosting bzr branches in your U1 folder
[10:56] <duanedesign> persia: yes most of what i have tested worked fine
[10:56] <persia> rye: Or rather, do you know of any reason it wouldn't work, or wouldn't be a bug if something went wrong?
[10:57] <corecode> is it me or does tomboy sync not work?
[10:59] <rye> duanedesign, rye - i am still hesitating to answer. The first thing is that there is nothing wrong with that, I am now hosting small svn repository in my u1 folder
[11:00] <rye> persia, the only issues that may arise so far is that in case there is a heavy usage of the branch then the changes may not be momentarily uploaded. And the file timestamps are not preserved during download
[11:01] <rye> corecode, there ... well, I need to update the subject
[11:02] <persia> rye: So there are no issues related to bzr tracking inode rather than filename, etc.?
[11:02] <persia> (svn doesn't do this)
[11:06] <rye> corecode, there is an issue at the moment with Tomboy note syncing - bug #538140
[11:08] <rye> persia, the files are not physically moved to another location but in case .bzr metadata relies on some file properties then that might cause some issue. I am not a heavy user of bzr yet. My has been damaged with CVS (I was exposed to it for 4 years) and I am still recovering.
[11:10] <persia> Heh.  OK.  I'll check with the bzr folk.
[11:10] <persia> ubuntuone just copies files?
[11:12] <rye> persia, yup
[11:17] <persia> rye: For your svn stuff, do you have an svn "repository" or an svn "checkout"?
[11:18] <rye> persia, svn checkout, repository is at googlecode
[11:18] <persia> rye: Thanks.
[11:18]  * persia is chatting with the bzr folk
[11:24] <persia> As it turns out, it's a very bad idea to put bzr branches in u1 (or svn repos, etc.), because the structured data assumes that nothing is replicating it in realtime, and multiple writers break all the semantics.
[11:24] <persia> Thanks for the help, and sorry for any confusion.
[11:25] <rye> persia, hm.. well, ubuntuone does not perform any write activity in UBuntu One folder when it is uploading things
[11:25] <persia> I've been told in #bzr that at least one user has already had a branch eaten, so it may even be worth adding a note to some FAQ to not use u1 for bzr, sqlite, etc.
[11:25] <rye> persia, except for nautilus plugin in current stable karmic... grrr
[11:25] <persia> rye: It would be when it was downloading : some user with the u1 folder mounted on more than one machine.
[11:25] <lifeless> rye: if you have two machines signed into u1 and run 'bzr $something' on both, then u1 will write back the changes to the other machine
[11:26] <lifeless> rye: but do so *without* honouring the bzr locking
[11:26] <rye> lifeless, because locks are on the files, right?
[11:26] <lifeless> rye: amongst other things
[11:27] <lifeless> it will often work ok, but its inherently unsafe, and when it goes munch munch munch there will not be much you can do
[11:27] <persia> rye: It's dangerous for all the same reasons that the couchdb sync is different from file sync in u1
[11:27] <lifeless> if you want to share bzr branches, push them to launchpad - much easier, much faster, much more scalable: its what LP is designed to handle
[11:28] <lifeless> I have to go sleep :)
[11:28] <lifeless> gnight
[11:28] <persia> The original use case was non-public sharing/backup for a single user.
[11:28] <persia> But u1 doesn't seem to be the solution for that.
[11:28] <lifeless> backup would be ok, but you'd have to be extremely careful not to have two machines
[11:28] <lifeless> (using bzr in the u1 share)
[11:29] <lifeless> you could push into a u1 share, and pull from it somewhere else, quite robustly.
[11:29] <persia> lifeless: Backup as in making a tarball and stuffing that in u1, yes.  replication, no.
[11:29] <lifeless> just don't ever *work in it*
[11:29] <lifeless> persia: as in 'bzr push ~/Ubuntu One/foo'
[11:29] <persia> replication was what the original user wanted (work on homework at home, sync to u1, use branch at school, etc.)
[11:30] <lifeless> we should document the interactions
[11:30] <persia> lifeless: Ah, so if one limits oneself to bzr push/pull/branch/merge it ought be safe?
[11:30] <lifeless> persia: treating the U1 folder like launchpad means you'll have a clean bzrdir somewhere always
[11:30] <persia> Oh, then that solves the use case.
[11:31] <persia> And, yes, ought be documented.  Does it belong in u1 docs or bzr docs?
[11:31] <lifeless> even if the u1 content gets narfed, you have the seperate dir to work from
[11:31] <lifeless> persia: both
[11:31]  * persia files a bug, taking advantage of LP's multiple task feature
[11:31] <lifeless> bzr should document how it will interact with dropbox,u1,$asyncreplicatorsthatarenotfilesystems
[11:32] <lifeless> u1 should tell folk how databases will generally behave when you store them in u1 and do 'stuff impossible to do locally' on them
[11:35] <rye> ok, I know the second reason why web UI for notes might fail.
[11:35] <persia> Filed as bug #539504
[11:36] <persia> Thanks a lot rye and lifeless
[11:36] <pecisk> hi people, when I delete file from web interface, everytime my files gets mixed up and I seem them doubled or tripled, I have to click on Files again
[11:36] <pecisk> is it known bug?
[11:36] <rye> pecisk, yes, let me find the number...
[11:37] <rye> pecisk, bug #516140 along with the video
[11:37] <pecisk> thanks :)
[11:41] <rye> ok, there's some kind of inefficiency. Whenever the user requests notes for /notes/ ui, all the notes are loaded and parsed (i.e. converted from XML to HTML). I believe this calls for a problem for large amount of notes...
[11:41] <rye> since the result is most probably thrown away
[11:42] <rye> desktop+ team / web ui - is that ok ^ ?
[11:46] <rye> well, filing two bugs, first for the converter and second for the parsing...
[12:28] <psyphercode> honk
[12:28] <rye> psyphercode, honk-pong
[12:29] <psyphercode> rye: oh am i supposed to say honk-pong?
[12:29] <rye> psyphercode, no, i belive we might need to change "Please honk" to "Please ping" :)
[12:29] <rye> or ping rye
[12:30] <psyphercode> ok
[12:31] <psyphercode> dude, my reads are taking longer than a work day now, i made adjustments, deleted a whole bunch of files but i think the index files are still there causing it to take so long to read. is there a way to delete all the indexes files, have it reindex and see what still needs to be uploadad wihout having to upload the stuff i know is already on the web?
[12:33] <psyphercode> i've been waiting 3 days now for the index reads to stop so it can actually start uploading the files, just don't want to have to upload all the files again which are already there
[12:51] <psyphercode> rye: what do u say?
[12:52] <rye> psyphercode, so now you have all metadata read and you see the server queries in the logs, right?
[12:53] <psyphercode> well i am assuming that the metadat has been created, it just take longer than 8 hours to read, yet i thknk that excess metadat is there causing it to be slower than it should
[12:55] <psyphercode> rye: the log says the scan has been started only
[12:55] <psyphercode> 2010-03-16 13:21:54,651 - ubuntuone.SyncDaemon.Main - NOTE - ---- MARK (state: INIT; queues: metadata: 0; content: 0; hash: 0, fsm-cache: hit=0 miss=195800) ----
[12:55] <psyphercode> 2010-03-16 13:21:54,652 - ubuntuone.SyncDaemon.Main - NOTE - Local rescan starting...
[12:55] <psyphercode> 2010-03-16 13:21:54,652 - ubuntuone.SyncDaemon.local_rescan - INFO - start scan all shares
[12:55] <rye> 13:21 and now it is 14:55, right?
[12:55] <psyphercode> yes
[12:56] <psyphercode> only 12867 now, not 385000
[12:56] <psyphercode> so should be lots lsower
[12:56] <psyphercode> should be doing something at least, not just "reading" all day long
[12:56] <psyphercode> also converned about my hard drives lifespan now
[12:59] <psyphercode> rye: so thats why i am wondering if i can clear all the metadata, have it re-index the less amount of files, then read it then hopefully compare it to whats online laready and then upload the diffrence
[13:05] <nessita> psyphercode: hi there
[13:05] <psyphercode> nessita: hi
[13:05] <nessita> psyphercode: could you please pastebin all the log file?
[13:05] <psyphercode> ok
[13:05] <nessita> psyphercode: if the daemon is doing local rescan, it passed already the metadat loagin phase
[13:05] <rye> nessita, maybe private bug report would be better?
[13:05] <nessita> loading*
[13:05] <nessita> rye: yeah
[13:06] <psyphercode> so u want all of these:
[13:06] <psyphercode> /.cache/ubuntuone/log$ ls
[13:06] <psyphercode> log.tar.gz
[13:06] <psyphercode> oauth-login.log
[13:06] <psyphercode> syncdaemon-exceptions.log
[13:06] <psyphercode> syncdaemon-exceptions.log.2010-03-12_07-15-58
[13:06] <psyphercode> syncdaemon-exceptions.log.2010-03-12_10-23-13
[13:06] <psyphercode> syncdaemon-exceptions.log.2010-03-12_11-40-05
[13:06] <psyphercode> syncdaemon-exceptions.log.2010-03-15_07-36-32
[13:06] <psyphercode> syncdaemon-exceptions.log.2010-03-16_12-36-26
[13:06] <psyphercode> syncdaemon.log
[13:06] <psyphercode> syncdaemon.log.2010-03-12_10-23-13
[13:06] <psyphercode> syncdaemon.log.2010-03-12_11-40-05
[13:06] <psyphercode> syncdaemon.log.2010-03-15_07-36-32
[13:06] <psyphercode> syncdaemon.log.2010-03-15_07-36-33
[13:06] <psyphercode> syncdaemon.log.2010-03-16_12-36-26
[13:06] <nessita> psyphercode: yes please! Could you please open a private report?
[13:07] <nessita> psyphercode: I'll be happy to try to diagnose what the issue
[13:07] <psyphercode> nessita: 388188 file int ~/.local/share/ubuntuone/syncdaemon/fsm
[13:07] <psyphercode> but only 12867 files in ubuntone fol;der
[13:07] <nessita> psyphercode: please add that data on the report too
[13:07] <psyphercode> ok what do i say in the repost, already have some many
[13:07] <psyphercode> report*
[13:08] <psyphercode> could i not use the one i have already logged for this?
[13:08] <nessita> psyphercode: do you have several reports for this same issue?
[13:09] <psyphercode> well it depends, i have rporst for the clietn app crashing because it's still doing the scan
[13:09] <nessita> psyphercode: please open a new one, reporting the speed issues you experince
[13:09] <psyphercode> ok
[13:12] <psyphercode> arg where is the "report a bug" button on launchpad??
[13:16] <nessita> psyphercode: top right corner
[13:17] <psyphercode> nessita: nope no such thing
[13:17] <nessita> psyphercode: one sec, I'll give you a link
[13:17] <psyphercode> i see username and logout
[13:17] <psyphercode> but i will use ubuntu-bug from cli
[13:17] <nessita> https://bugs.launchpad.net/ubuntuone-client/+filebug
[13:17] <nessita> psyphercode: ^
[13:19] <psyphercode> you have to search for the app 1st then there is a report a bug button, can't just do that from the homepage, silly
[13:19] <psyphercode> anyway busy with it now
[13:19] <nessita> psyphercode: is that every bug report is tied to a specific project
[13:20] <nessita> psyphercode: please also add, besides the whole log dir content and the amount of files/metadata, the ubuntu version and ubuntuone-client version
[13:20] <nessita> rye: could you help him doing that?
[13:20] <psyphercode> i understand that, i would have just put a fat report a bug button on the home page, then specify what apps
[13:22] <rye> nessita, ok, (twinview-only nouveau makes it hard for me to find windows :-/ )
[13:23] <nessita> psyphercode: file another report to launchpad for that! :-)
[13:23] <psyphercode> ;)
[13:23] <rye> psyphercode, I believe you will want to create new bug report, file some basic details... hm, apport-bug ubuntuone-client might do that for you (it seems to be working now)
[13:23] <psyphercode> i know, not your job :)
[13:25] <psyphercode> nessita: https://bugs.launchpad.net/ubuntu/+source/ubuntuone-client/+bug/539573
[13:25] <nessita> psyphercode: more than not being my job there is no much I can do :-)
[13:25] <psyphercode> done
[13:25] <rye> psyphercode, after you create the bug report, please mark it as a private one and then add the files that were requested
[13:26] <psyphercode> done
[13:26] <psyphercode> will add files now
[13:28] <psyphercode> done
[13:31] <nessita> psyphercode: looking at it right now and checking with other devs for more eyes :-)
[13:31] <psyphercode> nessita: ok sweet thanks
[13:32] <nessita> psyphercode: ok, for starters you have an "old" client, have you consider switching to PPA's?
[13:32] <psyphercode> sure if it give me more stability
[13:33] <nessita> I will leave that advice to rye. What do you think?
[13:33] <nessita> psyphercode: for completeness sake I need you to run this:
[13:34] <nessita> find .local/share/ubuntuone/syncdaemon/fsm/ -type f | wc -l
[13:34] <nessita> psyphercode: and
[13:35] <nessita> find Ubuntu\ One/ | wc -l
[13:35]  * rye feels we need to have ubuntuone-servers-notes project or something like this...
[13:35] <psyphercode> yeah pretty much same i got the values earlier. the fsm one will ake a while
[13:36] <psyphercode> find Ubuntu\ One/ | wc -l
[13:36] <psyphercode> 17080
[13:38] <nessita> psyphercode: question. You mention you added 38500 files, are those still on Ubuntu One?
[13:39] <nessita> 385000*
[13:40] <psyphercode> no, i had like 100 files on there, bulk, then copied the rest of my home folder over, whihc was the 380000, it never even started updating, so i deleted most of it and now still waiting for anything to upload, still just 100 on ubuntu one
[13:40] <psyphercode> fsm: 383820
[13:46] <rye> nessita, i believe due to bug #531273 (which title I need to rename, but the keyword ages is pretty relevant in this case)
[13:46] <nessita> rye, psyphercode: at first it's not safe to delete the metadata
[13:47] <nessita> one option would be to backup your whole Ubuntu One folder and the metadata, and then delete, but it's a bit risky
[13:47] <psyphercode> nessita: ye rather no risks
[13:47] <rye> psyphercode, re: PPA - I have not experienced any syncdaemon crashes with PPA on Lucid but for Jaunty the applet is no longer present. Stability - yes, but no major speed gain
[13:47] <psyphercode> so is there ot a clean up fucntion to delete stale metadata?
[13:47] <psyphercode> rye: so stick with the normal repo's
[13:48] <rye> psyphercode, well, the applet is not that required, actually, it only has a 'Connect' button I believe. OTOH it provides notifications that are now missing in Lucid
[13:48] <rye> and actuall for all PPA users
[13:49] <psyphercode> rye: ok so what do u suggest
[13:51] <psyphercode> nessita: u know what i also just realised which happened. i pretty much copied my entire home folder, and i must have included the metadata folder as well, DOH! so i have metadata of metadata, dumb of me!!!
[13:52] <nessita> psyphercode: :-/
[13:52] <rye> psyphercode, ~Ubuntu\ One/.local/share/ubuntuone/syncdaemon ?
[13:52] <nessita> psyphercode: ok, so, at first, is not safe to delete your metadata, much les without having a backup of it and of the Ubuntu One folder
[13:52] <psyphercode> rye: well everything, i copied the entire home folder
[13:53] <rye> psyphercode, before you remove that, in case that you want to remove that - find -type f ~Ubuntu\ One/.local/share/ubuntuone/syncdaemon | wc -l
[13:53] <psyphercode> nessita: yeah i understand but does the deamon not do a cleanup itself?
[13:53] <rye> psyphercode, so you got thumbnails there, firefox cache, other browsers cache, actually everything...
[13:54] <psyphercode> rye: nah it's not there anymore
[13:55] <rye> psyphercode, by anymore you mean you removed that?
[13:55] <psyphercode> yes
[13:55] <psyphercode> just these foldeers:
[13:55] <psyphercode> ruald@schweet:~$ ls -la Ubuntu\ One/ruald/
[13:55] <psyphercode> total 72
[13:55] <psyphercode> drwxr-xr-x 10 ruald ruald  4096 2010-03-11 13:14 .
[13:55] <psyphercode> drwxrwxr-x  3 ruald ruald  4096 2010-03-02 12:54 ..
[13:55] <psyphercode> drwxr-x---  4 ruald ruald  4096 2010-03-08 15:33 Backup
[13:55] <psyphercode> -rwxr-x---  1 ruald ruald  4672 2010-01-15 09:13 .bashrc
[13:55] <psyphercode> drwx------  3 ruald ruald  4096 2010-02-26 13:28 bin
[13:55] <psyphercode> -rwxr-x---  1 ruald ruald  3265 2010-01-15 09:30 .conkyrc
[13:55] <psyphercode> drwxrwxrwx 37 ruald ruald 12288 2010-02-27 15:20 Documents
[13:55] <psyphercode> drwxr-xr-x 10 ruald ruald  4096 2010-03-09 11:20 .evolution
[13:55] <psyphercode> drwx------  6 ruald ruald  4096 2010-03-09 12:34 .mozilla
[13:55] <psyphercode> drwxr-xr-x 20 ruald ruald  4096 2010-03-04 07:21 Pictures
[13:55] <psyphercode> drwx------  2 ruald ruald  4096 2010-01-15 09:13 .ssh
[13:55] <psyphercode> drwxr-x---  8 ruald ruald 16384 2010-01-15 09:11 .tomboy
[13:55] <rye> psyphercode, the metadata files are required for the proper operation of syncdaemon, it is cleaned whenever it is required
[13:55] <psyphercode> but the meatadat still exists that the problem
[13:56] <rye> psyphercode, the issue is that for every normal file at least one metadata file is generated, that's ok but then the process of loading these files take enormous time
[13:56] <psyphercode> rye: so no way for it to clean out the metadata which it no longer requires? surely it cannot just keep the stale files foreever, your drive will even tually fill up
[13:57] <psyphercode> rye: yeah i get that, but still 380000 unrequired files being read
[13:57] <rye> psyphercode, in order to clean it up, it needs to load it first, then perform a local rescan and then it should remove the entries that are no longer valid, is it correct, nessita?
[13:58] <nessita> rye: I think so, yes,I'm checking wit verterok and with facundobatista_
[14:12] <rye> great. In case someone has got a link to an attachment from a bug report, he/she might download that even if the report is marked as private
[14:12]  * rye went to #launchpad
[14:21] <nessita> psyphercode: we're working on a script to delete the unused metadata
[14:21] <nessita> psyphercode: are you gonna be around in ~1 hr?
[14:22] <psyphercode> prob not, gonna be packing up
[14:22] <psyphercode> but u can put it on the bug report
[14:22] <nessita> psyphercode: perfect
[14:22] <psyphercode> i'll check it out tomorrow
[14:22] <psyphercode> sweet THANK SO MUCH!
[14:22] <nessita> psyphercode: we're also going through the code to check if we actually delete or not the unused metadata
[14:23] <nessita> psyphercode: so you may have discovered a bug
[14:23] <psyphercode> cool
[14:23] <psyphercode> i like it
[14:42] <corecode> cute.  now all my notes are gone
[14:44] <rye> corecode, how?
[14:49] <corecode> i had removed the old notes from one
[14:49] <corecode> but i had them still on a different machine
[14:50] <corecode> so everything alright now
[14:50] <corecode> anybody know whether conboy already supports syncing with one?
[14:51] <pecisk> by the way, is there any hope for Ubuntu One client to support proxy?
[14:56] <rye> pecisk, so far, for syncdaemon, there are only workarounds but that is doable. This has to be solved for couchdb as well as it does not support proxies for replication and that will most likely will need to require upstream support
[14:56] <pecisk> allright
[15:32] <fagan> Im having trouble with ubuntuone in lucid
[15:32] <fagan> Its not syncing anymore
[15:34] <fagan> jcastro had something similar
[15:41] <fagan> I killed all the processes and removed all the config files for u1
[15:41] <fagan> how do I force u1 to reauth?
[15:44] <jcastro> I remove the key from the gnome keyring with seahorse
[15:44] <jcastro> then launch the applet and the browser will ask you to add the computer
[15:45] <fagan> nice thanks jcastro
[15:45] <rye> jcastro, do you mean applet or preferences window?
[15:45] <jcastro> the applet thing in the me menu.
[15:45] <rye> ah, ok
[15:45] <jcastro> is that the applet or the prefs window?
[15:46] <rye> jcastro, prefs, applet with the cloud icon is removed in Lucid
[16:05] <fagan> hmmmm I deleted all the settings on my computer and now ubuntu one isnt working at all
[16:05] <fagan> :/
[16:06] <fagan> Any ideas on how to debug the problem?
[16:11] <rye> fagan, could you please describe in some more details the "deleted all the settings"?
[16:12] <fagan> I removed .config .cache .gnome2...etc
[16:12] <fagan> It refreshes all the settings back to default when you reboot
[16:13] <fagan> But ubuntuone is broken now for some reason
[16:17] <fagan> And I removed the auth token from the keyring and wanted u1 to auth itself again but it doesnt work for some reason
[16:18] <fagan> rye: any ideas?
[16:19] <rye> fagan, could you please pastebin the content of ~/.cache/ubuntuone/log/ubuntuone-syncdaemon.log ?
[16:20] <fagan> Its empty
[16:21] <fagan> I did remove the .cache folder and u1 hasnt been on since so it makes sense
[16:22] <dobey> it's just "syncdaemon.log"
[16:24] <rye> dobey, ah, thanks. fagan - ~/.cache/ubuntuone/log/syncdaemon.log
[16:24] <fagan> Nope still empty
[16:24] <dobey> and there's syncdaemon-exceptions.log and oauth-login.log which might be of use
[16:25] <fagan> The oauth-login.log is there
[16:25] <rye> fagan, ok, could you please try running /usr/lib/ubuntuone/ubuntuone-syncdaemon directly from the terminal
[16:25] <rye> fagan, btw, what release are you using ?
[16:25] <fagan> lucid
[16:26] <fagan> Ok so the oauth-login.log says its starting the ubuntu one login manager
[16:28] <fagan> fyi its /usr/lib/ubuntuone-client/ubuntuone-syncdaemon
[16:29] <fagan> I doesnt seem to be doing anything
[16:29] <dobey> the syncdaemon.log is still empty?
[16:30] <fagan> Oh it worked ish but I dont know why its not authed
[16:32] <fagan> I think I just made myself a corner case :)
[16:34] <rye> fagan, ok, try killing ubuntuone-syncdaemon and ubuntuone-login (if it exists) and try running /usr/lib/ubuntuone-client/ubuntuone-login in one terminal, ubuntuone-syncdaemon in another terminal
[16:34] <rye> and run u1sdtool --connect in the third one
[16:36]  * Ng wonders if there is anything useful he can do to provide information on bug #500975
[16:36] <fagan> rye: I have a traceback for you :)
[16:36] <rye> Ng, I am now making a script that will attempt to detect bug #539521 better (tomboy-recovery.py) - does not work as I want to
[16:37] <fagan> its gnome keyring giving problems
[16:37] <Ng> rye: if necessary I'm prepared to sanitise my notes to remove anything private and make them available to developers
[16:37] <fagan> http://pastebin.ubuntu.com/396239/
[16:37] <rye> Ng, basically this is the only thing that is known to kill sync from U1 to Tomboy, web ui story is a little bit more complicated
[16:40]  * fagan just makes a new account its a lot easier 
[16:45] <rye> Ng, http://paste.ubuntu.com/396242/  - could you please make a copy of ~/.local/share/tomboy somewhere and run that script?
[16:46] <rye> fagan, I believe you killed gnome-keyring, i.e. it is not running on login
[16:48] <rye> Ng, the script won't fix the items at the moment, since they are on the server side however you might find out what notes are w/o content
[16:48] <Ng> rye: sure, just a sec
[16:48] <rye> Ng, but make a backup - in case next sync works
[16:57] <fagan> rye: I got it working thanks for the help
[16:57] <rye> fagan, you are welcome. You started gnome-keyring daemon and syncdaemon started to work, right?
[16:58] <fagan> yep
[16:58] <fagan> when I deleted my settings it took out the keyring and didnt get put back
[16:58] <rye> fagan, ok, thanks. good to know
[16:58] <fagan> I just had to start the daemon make a new keyring and it was fixed
[17:06] <fagan> Yay and now gwibber is working again :)
[18:09] <thisfred> seg|away: I haven't looked, but is there a mechanism by which you update the design document in couchdb when the views change in the code?
[18:14] <seg|away> thisfred: yeah, look at init_design_doc in gwibber/microblog/util/couch.py
[18:14] <thisfred> seg|away: what I have done on the server is version the design documents, and check the version when calling a view
[18:14] <thisfred> seg|away: oh ok, awesome
[18:15] <seg|away> thisfred: you basically don't have to do anything because it already gets called when the program starts
[18:15] <seg|away> if you change the contents of COUCH_VIEW_MESSAGES, it will just seamlessly update
[18:16] <thisfred> seg|away: hmm, so that didn't really seem to work, the views were not changed after restarting gwibber. OTOH, maybe it was using my system gwibber code. Is there a good way to run things in place?
[18:17] <thisfred> seg|away: I just did python setup.py build, and ran the scripts from the build directory
[18:17] <thisfred> but I don't know how well they're isolated
[18:17] <seg|away> gwibber is designed so that you can it directly from the checkout
[18:17] <thisfred> perhaps I need to set a PYTHONPATH
[18:17] <seg|away> ./bin/gwibber-service && ./bin/gwibber
[18:17] <thisfred> oh ok, awesome
[18:18] <seg|away> the scripts are set up so that they will use the right paths
[18:18] <thisfred> I hope to finish this on my lunch break. I have 12 more minutes :)
[18:18] <seg|away> thanks
[18:26] <fagan> Im getting service temporaarily unavailable when I try to download a file from one.ubuntu.com
[18:26] <fagan> Is it down?
[18:27] <rye> fagan, confirming, escalating
[18:28] <fagan> Arg I need to grab my project :/
[18:36] <duanedesign> i just upgraded to Lucid. I have a beam.smp process that is running 100%cpu and i cant seem to kill it
[18:36] <rye> duanedesign, hm, is strace -p $PID shows something?
[18:37] <markl_> part of erlang
[18:37] <markl_> maybe try ps -auxww | grep beam
[18:37] <markl_> see if you can get more details
[18:37] <markl_> or even top -c
[18:39] <thisfred> seg|away: ok, so I see no errors, I threw the view index away, and it's about a factor 10 smaller. IOW, I think this is ready for review: https://code.launchpad.net/~thisfred/gwibber/incredible-shrinking-views/+merge/21469
[18:39] <seg|away> thisfred: awesome! :-D
[18:39] <duanedesign> http://paste.ubuntu.com/396301/
[18:39] <thisfred> seg|away: somehow the .pot file got changed, probably because I did the build.
[18:40] <duanedesign> that paste is from doing ps -auxww | grep beam
[18:40] <thisfred> seg|away: I won't have time to do more work on it today, but I will look at it tomorrow if it needs changes
[18:47] <duanedesign> oh, it finally throttled down. i guess i just needed to let it run for 20 minutes. You could cook an egg on my laptop, lol
[18:51] <rye> ok, updown is up
[18:51] <rye> hm
[19:22] <Ng> rye: sorry, I only just got a chance to run that script for you
[19:22] <Ng> rye: looks like it found a blank note, "Note New Note Template"
[19:22] <Ng> although tomboy's UI shows no such note
[19:24] <rye> this is a note template
[19:24] <rye> nessita, i believe I have reproduced the problem with dirs
[19:24] <rye> in vm, yay!
[19:25] <nessita> rye: great, could you please add a report with debug logs? :-)
[19:25] <dobey> hmm
[19:25] <Ng> rye: the new note template is always going to be empty though, right? I'm somewhat reluctant to just fudge something into it so my notes sync if it's just going to explode for everyone
[19:25] <dobey> seg|away: did gwibber ever use gnome-keyring? there are some bug reports that kind of suggest it did at some point
[19:25] <Ng> s/always/usually/
[19:26] <rye> Ng, that would be fixed, the bug is known, but usually the note template contains "Add the description for a new note here"
[19:27] <seg|away> dobey: it did use gnome-keyring for passwords back in the day. But it broke when gnome switched to using d-bus for the keyring
[19:27] <seg|away> dobey: I would really like to be able to use the keyring again, but the current issue is that the keyring doesn't sync
[19:27] <Ng> rye: fair enough, in which case I can just add some content to the note and be done. How do I add some content on the server side if that's not shown in the UI?
[19:27] <dobey> i don't think i'd call that an issue
[19:28] <dobey> i would rather not sync my passwords, than have them stored in plaintext and synced to the internet and all of my machines :)
[19:28] <seg|away> account syncing is useless if the user has to type their passwords in again on every computer
[19:28] <seg|away> I'm happy to implement support for keyring password storage, but I'd have to disable u1 account syncing
[19:29] <dobey> that's fine by me
[19:29] <seg|away> haha is that fine with canonical?
[19:29] <rye> Ng, note templates are not visible, right... But there is a workaround, let me modify the script...
[19:30] <dobey> seg|away: i'm presuming the credentials are in fact just stored in plaintext in desktopcouch?
[19:30] <seg|away> yes
[19:31] <dobey> then, yes, i'm sure the security team would want to pummel you about the head if they knew you were doing that :)
[19:31] <rye> Ng, http://paste.ubuntu.com/396322/ , actually that's one line diff but it has the UUID as well
[19:31] <dobey> and we concsioiusly chose to not do keyring sync for lucid, so accounts for other things aren't getting synced either. i don't see what would make gwibber special in that regard :)
[19:33] <seg|away> kenvandine: ^
[19:33]  * Ng tries not to read things like "keyring sync". my insides all scrunch up when i see things like that discussed ;(
[19:33] <dobey> Ng: were you at the UDS session about it?
[19:33] <Ng> dobey: I forget, probably not
[19:34] <dobey> i don't recall if you were or not
[19:34] <Ng> I was mostly in the server track
[19:35] <rye> Ng, after UUID is known, append it to https://one.ubuntu.com/notes/edit/  and it will be opened
[19:35] <dobey> Ng: ah, well lamont and mdeslaur were, and we came up with a method that would belay any fears of theirs, and make lamont happy :)
[19:36] <Ng> rye: hurrah, thanks, I appear to be able to sync now
[19:37] <dobey> Ng: we figured out a nice balance for having it be secure, and not horrible for the user, that i was willing to implement. but it was postponed in favor of other things
[19:37] <rye> Ng, bug #539521
[19:37] <Ng> dobey: was it basically to sync the encrypted version of the keyring?
[19:37] <rye> oops, wrong bug
[19:38] <dobey> Ng: no, we would only sync select types of secrets in the keyring, and they would be encrypted/decrypted individually
[19:38] <rye> nessita, is it possible that directory removal will not make it into the server?
[19:38] <nessita> rye: hum... if you're not connected, yes
[19:38] <dobey> Ng: so it would be a layer on top of the keyring, and it could easily work with other keyrings than gnome-keyring
[19:38] <nessita> rye: or if the directory parent doesn't exist on the server, it will fail
[19:38] <dobey> Ng: we can't just sync the keyring file itself, because it would potentially cause data loss
[19:39] <nessita> rye: or... I should check your logs
[19:40] <rye> nessita, ok, I am still trying to create an empty env to re-re-re-reproduce the bug
[19:40] <Ng> dobey: will there be another session about this at the next UDS? :)
[19:40] <dobey> Ng: possibly
[19:41] <dobey> Ng: if not, you are welcome to give me beer and talk about it at the end of the day :)
[19:41] <Ng> dobey: if you can describe it to kees and have him not punch you, I'll be happy, but I'm also very prepared to feed you hoegaarden in exchange for discussion :)
[19:41] <dobey> hehe
[19:42] <dobey> well, like i said, lamont was content :)
[19:47] <Ng> both of the hotel bars sell hoegaarden, as do basically all of the restaurants in Waterloo \o/
[19:50] <dobey> probably
[19:50] <dobey> but i'm sure there are better beers to try there :)
[19:50] <Ng> let us not take the hoegaarden's name in vain (but yes, there are many wonderful beers in belgium)
[20:00] <Ng> does the tomboy sync protocol make it possible/likely that we'll be able to share notes with people/groups?
[20:04] <dobey> no and yes
[20:04] <dobey> it's not a feature of the way tomboy sync works, but the notes on the server are stored in your couchdb
[20:05] <dobey> so technically, we could implement something on top of the current notes UI on the web which allows you to do this, but it would only be doable on the web, and not in Tomboy itself
[20:16] <kenvandine> dobey, isn't desktopcouch itself protected by the keyring?
[20:17] <dobey> kenvandine: no
[20:17] <kenvandine> is that just for futon?
[20:18] <dobey> kenvandine: at least not unless couchdb encrypts everything you put in it somehow, using the desktopcouch oauth token
[20:18] <dobey> but then futon wouldn't work, because it doesn't auth with oauth
[20:18] <kenvandine> i think it uses the keyring to store the passwd to access couch
[20:19] <dobey> to access it via normal means, sure
[20:19] <kenvandine> how about with the records api?
[20:19] <kenvandine> that is just user perms, right?
[20:19] <dobey> but i'm pretty sure that the db isn't encrypted
[20:20] <kenvandine> dobey, i think you are right... just looking at the normal usage
[20:20] <dobey> if i got access to your couchdb file from somewhere, i could still read the text
[20:20] <kenvandine> yes, of course
[20:28] <dobey> so yeah, i am not using gwibber now
[21:23] <sandy|lurk> hey folks, quick question
[21:23] <sandy|lurk> I'm looking at /topic
[21:23] <sandy|lurk> and see: "Notes: LP:539521 (notes w/o content cause Tomboy sync failure)"
[21:23] <sandy|lurk> but that's not the right LP #
[21:24] <sandy|lurk> (it's the same as the last one listed in /topic)
[21:24] <sandy|lurk> does anyone have the right LP #?
[21:27] <sandy|lurk> maybe it's this one? https://bugs.launchpad.net/ubuntuone-servers/+bug/538140
[21:32] <beuno> rye, ^
[21:35] <rye> sandy|lurk, thanks!
[21:36] <abdalla> rye: Hi
[21:36] <rye> abdalla, hi
[21:37] <rye> I believe so far I filed all possible bug reports regarding note oopsing, waiting for rodrigo to fix that...
[21:47] <abdalla> rye: last days i took overall view for UbuntuOne and CouchDB (i did not have much time because of my regular work :) )..but i`m interest to start contribution
[22:34] <seg|away> thisfred: I'm going to merge your branch. It's working great for me
[22:34] <thisfred> seg|away: yay!
[22:35] <thisfred> seg|away: I think the bulk updates would be another low hanging performance fruit, but I don't think I'll have more time this week
[22:35] <seg|away> thisfred: bulk updates are not supported on karmic, right?
[22:36] <thisfred> seg|away: ah, not sure about that
[22:36] <seg|away> I'm pretty sure it's only in newer desktopcouch
[22:36] <thisfred> seg|away: well they're not in desktopcouch, but they may be in couchdb-python, I don't know in which version they got added
[22:36] <seg|away> yeah
[22:37] <seg|away> thisfred: http://bazaar.launchpad.net/~mandel/desktopcouch/batch_update/revision/118
[22:37] <seg|away> very recent addition to the library
[22:38] <seg|away> has that been merged?
[22:40] <thisfred> seg|away: yes, looks like, but I don't know that there has been a lucid release after that. I think so, though
[23:27] <rye> hi all, could you please check what you see in https://one.ubuntu.com/contacts/ ?
[23:28] <jcastro> rye: I see a rolodex-style alphabet thing
[23:28] <jcastro> after it asked me to auth
[23:28] <rye> jcastro, ok, do you see your contacts?
[23:28] <jcastro> with one letter
[23:28] <jcastro> but not the others
[23:29] <rye> jcastro, well, it is your own entry, right?
[23:29] <rye> w/ fields empty?
[23:29] <jcastro> no, this is an entry I made for my cat a while ago
[23:30] <rye> beuno, ^
[23:31] <jcastro> I can edit it and stuff
[23:52] <popey> i am getting "auth failed" when i connect to u1ms
[23:52] <popey> well, u1sdtool gives auth failed
[23:56] <duanedesign> i see about every other letter highlighted with a (1). When i click for instance C(1) I dont see any entry show up in the right hand box
[23:56] <rye> beuno, ^
[23:59] <beuno> duanedesign, what browser is this?
[23:59] <beuno> and, can you report a bug  :)