[00:35] anyone know how to uninstall ubuntuone? [00:39] the easiest way is probably just to uninstall the ubuntuone-client package === inkvizitor68sl is now known as ink_away [01:09] tcole: or python-ubuntuone-storageprotocol [01:09] and now, genesis games, amish lemonade, and food [01:41] Thanks tcole, that did it! [03:31] hello! Anyone here? [03:33] need help with ubuntuone. can't seem to log on anymore. "Cannot Authenticate" [03:34] tried removing the password from the keyring, but it won't re-authenticate. :( [03:37] hello! [03:37] need help with ubuntuone. can't seem to log on anymore. "Cannot Authenticate" [03:37] tried removing the password from the keyring, but it won't re-authenticate. :( [03:38] i've been looking for solutions on the net, one is to use u1sync [03:38] curiouscat: perhaps try killing the client after removing the authentication token from the keyring? [03:38] But it couldn't find the command, and i don't know from where to install this thing. [03:38] jamesh: did that already. Didn't work. [03:39] rebooted even. No love. : [03:39] :( [03:43] so, if you make sure ubuntuone-client-applet is not running, and then run "ubuntuone-client-applet --signup" on the command line, what happens? [03:44] (this is assuming that the token doesn't show up under the passwords tab of Applications -> Accessories -> Passwords and Encryption Keys) [03:45] tried that. it just starts the applet without going to the webpage for adding a new computer [03:45] does going through that process help? [03:45] even removed the computer from UbuntuOne account as well. Then tried the whole quit-applet-run-signup thing all over again. Still nothing [03:46] Can't understand why it doesn't recognize that the password is not longer in the keyring and that the computer is no longer associated. :( [03:47] removing the computer doesn't ask me to reassign it after the signup, btw. [03:48] the weird thing is the authentication problem is only on one laptop. I have another that has ubuntuone installed and it connects to my account just fine. [03:48] unfortunately, that laptop has to be returned in a few days. :( [03:50] the data in the keyring is what gets used to decide whether to authenticate. Let me try some things [03:50] ok [03:51] will just be waiting here. :) [03:56] so, I killed ubuntuone-client-applet and ubuntuone-syncdaemon, then deleted the token in the keyring [03:57] ran "ubuntuone-client-applet --signup" and it went through the authorisation process [03:58] (I had to tell it to add my computer again) [03:59] hmm. ok. i didn't kill the daemon. Maybe that's the clincher. Let me try [03:59] ok. no daemon or applet running [04:00] If I only kill the applet, it doesn't seem to start the reauthentication process. [04:00] it didn't go through the signup process [04:01] hmm, that's strange. [04:01] maybe try right clicking on the applet and pick connect if it doesn't do so automatically [04:02] it just generates an unhandled error when i try to connect [04:03] exceptions.AttributeError: 'NoneType' object has no attribute 'key' [04:04] Could you provide the full traceback here? http://paste.ubuntu.com/ [04:05] http://paste.ubuntu.com/236298/ [04:09] that's bizarre [04:09] i know! [04:10] thinking if i should try removing then reinstalling the app. you think that would work? [04:10] if I'm reading that right, it is failing to acquire the initial OAuth request token (a session identifier used for the authentication process [04:11] oh. So... a reinstall won't cut it? :( [04:25] well, if you want to try that, note that ubuntuone stores some data under ~/.cache/ubuntuone-storage [04:25] perhaps it'd be worth clearing that after killing the client+daemon [04:37] ah! ok. [04:47] still giving me the same error. [04:47] :( [04:51] I'm not quite sure what to suggest. Could you file a bug report about this? [04:52] describe the symptoms, and perhaps attach some of the logs from ~/.cache/ubuntuone/ [04:52] (assuming they don't have anything private in them) [04:52] okidoki. [05:00] hmm. i think i found the problem. [05:00] well, not sure actually. [05:00] saw this on the oath log, but I'm not really sure what this means: 2009-07-29 23:46:48,594:594.978094101 UbuntuOne.OAuthDesktop.auth Token was not successfully retrieved: data was 'Expired timestamp: given 1248882405 and now 1248925646 has a greater difference than threshold 300' [05:03] curiouscat, your local time on your PC may be wrong [05:03] although our threshold might be set a bit too low [05:05] statik: prior to the problem, my laptop's time had reset to 2005. noticed it. Reset back to current date. Then this problem started. [05:06] we had a bug report earlier where someones clock was about 5 hours off and they were getting this problem setting up the initial token [05:06] haven't looked at it closely yet, but adjusting the clock got past it [05:07] hmm. i set the time manually for this laptop. i'll try setting the preferences to get it from the time server instead. [05:13] i'll be back. Will restart laptop to see what happens. [05:18] FINALLY! It works! [05:18] Dang time thing. :P [05:18] Thanks so much guys! [05:20] jamesh: Thanks for showing me the ubuntuone logs. If it hadn't been for that, I wouldn't have known there was a log for the OATH. :) [05:20] what did you have to do to fix it? [05:21] statik: Thanks for pointing out that bug report about time vs authentication problem [05:21] ah. [05:21] np. i hope we can find a way to prevent this, and make the solution more obvious when it happens [05:22] jamesh: I made sure that my laptop's time is synched via an NTP server instead. [05:22] jamesh: restarted the laptop so that it would start pulling the time from the server. That's when UbuntuOne finally opened the site to re-authenticate the computer. [05:23] statik: I hope so too. Will be blogging about this in a bit. :) [05:24] given the server sends the date back in HTTP responses, we could potentially detect these issues. [05:25] but given we're using PLAINTEXT signatures (since the data is going over SSL anyway), a bad nonce timestamp isn't the end of the world [05:25] the nonces only add security for the HMAC-SHA1 signature method [05:28] I never even thought the time would be a problem actually. I had corrected the time earlier (manually) when I couldn't login to GMail. [05:29] So I figured, if GMail finally recognized I have the correct time, then all my other apps should be able to login as well. :P [05:29] there are lots of authentication protocols that depend on synchronised clocks [05:29] although ours probably shouldn't need to care. [05:30] never knew that UbuntuOne would be a stickler for exact server time. LOL! [05:32] well, exact to within 5 minutes [05:33] a number of authentication schemes depend on relatively synchronized clocks, including ours [05:34] strangely, it was telling me that it was off by 30minutes. [05:34] jamesh, btw did you get a chance to look at the oauth 1.0a vulnerability with 3-legged oauth? i think we are vulnerable, but haven't been able to figure out what we need to change to comply with the new spec [05:35] er, the vulnerability that prompted the release of the 1.0a spec i mean [05:43] just looking through the specification diff. It probably would affect us. [05:48] the oauth_verifier stuff looks like it'd work for our current setup. === ink_away is now known as inkvizitor68sl [13:24] aquarius, Hi. I'm trying to delete couchdb views using couchdb-python . The "design" module doesn't provide a direct way, AFAICT. Can I do it with the "client" module, like any other document? [13:24] CardinalFang, yeah; design docs are still docs and can be deleted the same way [13:25] (or if you want to delete one view, just rePUT the doc without the view in it) [13:25] how's the temp-view-removal stuff doing? [13:25] This the only missing piece. [13:25] wow! nice [13:26] So, to remove one view, I must collect all the existing views, delete my target view, and then rePUT? [13:26] I saw this way in "design" module, but that makes me cry. [13:33] Maybe I haven't drunk enough couchdb Kool-Aid yet, but it seems ugly to download, mutate, and then upload, potentially clobbering something that was updated in the mean time. I've spent enough years debugging race conditions. === verterok_ is now known as verterok [13:37] CardinalFang: there are no race conditions due to the MVCC versioning stuff [13:37] CardinalFang: you'll get a conflict error instead of clobbering something, then you just have to try again [13:39] That is exactly what I feared. [13:45] I thought you feared race conditions [13:47] Well, I fear designing an ugly API. [13:52] well, you have to handle multiple people updating the same thing somehow [13:52] either you let people clobber stuff, or you generate conflicts [13:52] I agree it's not ideal [13:59] It's that all views together are "the same thing" that bothers me. If you and I are both fighting over view "foo" then I agree nothing is good. If I'm updating view "foo" and you add "bar", then it shouldn't affect me. [13:59] jasondavies, ^ [14:00] CardinalFang: good point [14:00] * CardinalFang considers different design documents per view. [14:01] that is a possibility === JamalFanaian|afk is now known as JamalFanaian [15:04] blimey, 3pm, standup time [15:04] aquarius: yep [15:04] MEETING BEGINS: say me if you're here :) [15:04] me [15:04] me [15:04] me [15:04] me [15:05] me [15:05] me [15:05] me i guess... am here ethereally anyway [15:05] aquarius, isn't that a bit too inclusive? ;-) [15:05] teknico, well, if someone else says me then we can ask what they worked on today ;) [15:05] is that everyone? jblount's away today afaik [15:06] statik too [15:06] DONE: talk to statik about feature freeze and couch; mark couchdb issues that we need for feature freeze as 0.10 blockers in couch jira; decide on notes schema with vds and rodrigo; help document it on freedesktop; document Bindwood bookmark schema on freedesktop; discuss couchdb upcoming plans and release schedule with couch people; help integrate valid-user-only patch into couchdb [15:06] TODO: talk to arusha and rodrigo about notes web UI; work through bug list [15:06] BLOCKED: none [15:06] vds: speak your piece [15:06] DONE:finished funambol deployment scripts, discussed with Mark about deployment, with Stuart and Rodrigo about tomboy sync. [15:06] TODO: land funambol deployment scripts, update the funambol wiki, email funambol support guys [15:06] BLOCKED: nope [15:06] CardinalFang: go [15:07] DONE: Most of desktopcouch API. [15:07] TODO: Finish desktopcouch API. Get reviews of that and of Spawning [15:07] BLOCKED: Maybe. Some db/HTTP weirdness in desktopcouch behavior. [15:07] vds, O HAI! [15:07] DONE: reviews, defined the subscription options for phone syncing [15:07] TODO: implement the subscription check when syncing a phone [15:07] BLOCKED: none [15:07] next: urbanape [15:07] CardinalFang, *cough* [15:07] DONE: Submitted a branch for proposal to properly deal with deleting empty folders. [15:07] TODO: Yay, javascript. [15:07] BLOCK: Nada [15:07] rodrigo_1: you're up. [15:07] • DONE: REST API changes in U1, tomboy and snowy. Started desktopcouch pages in XDG (http://www.freedesktop.org/wiki/Specifications/desktopcouch). Started discussion on initial config for couchdb-using apps [15:07] • TODO: land use-source-properties branch. Add more tests in couchdb-glib test suite. More openSUSE packaging. Store UUIDs in VCARD's correctly. Fix notes/ saving and tomboy syncing. Change note record format as per xdg page [15:07] • BLOCKED: none [15:07] dobey: go [15:08] rodrigo_1, snowy is done too? winner! [15:08] DONE: Fix oauthdesktop to support 1.0a, Fix python-oauth to do 1.0a, [15:08] TODO: 1.0a on server side, #378707 [15:08] BLCK: None. [15:08] aquarius: not fully done, in fact I'd need your help, or any other djando's expert help [15:08] rodrigo_1, cool, I can do that [15:08] i guess that's all [15:08] cool, anything else, all? [15:09] nope. good [15:09] MEETING ENDS [15:09] quickest standup ever :) [15:10] vds, did you catch my question earlier about whether we need seqnos in trigger data on the desktop? [15:11] aquarius: so, I need to have the /api/1.0 accessible without auth, but they don't use the nice decorators we use, so not sure what needs changing [15:11] rodrigo_1, ah, ok, I'll take a look. do you have a snowy branch somewhere with your latest changes? [15:12] aquarius: no, just have a patch for the uris, sending it [15:12] kk [15:14] Hi all [15:17] Howdy! [15:17] hey facundobatista [16:27] mmm, I uploaded a file, but the "Sharing" tab is inactive [16:27] I managed sharing folders before [16:28] teknico: do you have the file selected in the list, or just the folder? [16:28] dobey, the file is selected in the web interface [16:28] the folder is the "My Files" one [16:29] the "Overview" and "Details" tabs work correctly, the "Sharing" one is inactive [16:30] teknico: you can't have the file selected [16:31] statik: ping === yofel_ is now known as yofel [16:32] statik: https://bugs.edge.launchpad.net/ubuntuone-client/+bug/406938 I heard there was some discussion a few months back about this on the ML. The design team is quite worried about it. [16:32] Launchpad bug 406938 in ubuntuone-client "Folder heirarchy should prioritize user files, not bury them" [Undecided,New] === djsiegel2 is now known as djsiegel [16:32] dobey, what do you mean? [16:34] if I click on the "My Files" folder, in the "Folders & Shares" left column, the "Sharing" tab on the right is active [16:34] teknico: right [16:34] teknico: if you click on any of the files in the center list, it will become inactive [16:34] (which is strange in itself, since clicking then on the "Share" button does not do anything) [16:34] teknico: because you can't share individual files [16:35] dobey, that's it, I was fearing it... [16:35] dobey, and there's no way to put the file in a folder on the server without reuploading it, right? [16:36] djsiegel2: statik is on holiday the rest of this week [16:36] joshuahoover: ok, I will interrogate him at the distro sprint in dublin :) [16:36] djsiegel: perfect! ;) [16:37] djsiegel: there is a desire to support syncing folders outside of that dir structure [16:37] teknico: i don't know what you mean with that question [16:37] djsiegel: yeah, he's flying on monday [16:37] dobey, is there any way to share the file I uploaded, without reuploading it? [16:38] joshuahoover: yeah, that's a slightly different issue I think [16:38] I am talking about our default config [16:38] teknico: you have to share the folder the file is in [16:38] but I can't wait until I can do: [16:38] $ echo ".zshrc" >> .ubuntuonerc [16:38] and have my .zshrc sync everywhere... :) [16:39] dobey, the file is directly in the "My Files" folder, which seems sharable at first, but then is not (as I described above) [16:39] djsiegel: there are several other bugs about the default directory structure already as well [16:39] and I wouldn't want to do that anyway :-) [16:39] dobey: where are they files? [16:39] teknico: there may be a bug, but you shouldn't do that anyway [16:39] filed* [16:39] I searched in ubuntuone-client and didn't see them [16:40] djsiegel: hmmm...let me see if i can find them here [16:41] djsiegel: ok, we don't have it in LP yet as a user story but it is on our backlog...i'll add the story...we've had numerous requests on LP for it (worded in various ways) [16:42] well, keep my bug, my description is so well worded :) [16:42] lol [16:43] djsiegel: heh...yeah, yours is a bit different (i think)...not going to replace it :) [16:43] djsiegel: #396561 #392583 #388986 #386077 #385155 #375486 #375482 #369099 [16:43] djsiegel: those are a few of them :) [16:43] dobey: dayum [16:44] djsiegel: yeah, as it turns out, inviting a LOT of linux users to your new service's beta gets you a LOT of bug reports [16:44] dobey: heh [16:44] dobey: should I mark these as dupes? [16:45] djsiegel: they probably aren't all dups. and there are a few others that i can't seem to find the numbers for right now either [16:45] djsiegel: but it is definitely a plan that we want to support arbitrary folder syncing [16:46] dobey: right, many of the bugs are about that [16:47] yeah [16:47] but i think there's one that's pretty descriptive that i can't find right now [16:48] which they should probably be marked a dup of (the ones that are fixable with arbitrary folders anyway) [16:48] dobey: i'll do that === dpm is now known as dpm-afk === dpm-afk is now known as dpm [19:05] dobey: has bug #397027 been fixed (related to the oauth key not getting deleted on removing the client)? [19:05] Launchpad bug 397027 in ubuntuone-client "Can't register computer after uninstall" [Undecided,New] https://launchpad.net/bugs/397027 [19:06] joshuahoover: no, and we can't go delete user configuration on uninstall of the package anyway [19:06] joshuahoover: i would say it's a duplicate of... let me find the bug [19:07] dobey: oh, it seemed like you were saying we could/would do that [19:08] gah launchpad needs much better searching, seriously [19:08] dobey: yeah, it does [19:08] joshuahoover: that should be a dup of bug #363243 [19:08] Launchpad bug 363243 in ubuntuone-client "No way to re-add a computer to your account" [High,Triaged] https://launchpad.net/bugs/363243 [19:09] dobey: ok, i'll mark it [19:15] i am tempted to just temporarily remove the use of gnome-keyring [19:15] so very very tempted [19:34] dobey: i agree on the launchpad's search complaint [19:35] heh [19:35] i think everyone agrees on that :) [19:39] lol === BitSchupser is now known as Bit_Schupser === Bit_Schupser is now known as BitSchupser [20:13] Where can I get a png of the Ubuntu One icon? [20:17] Xpistos|work: it's in the source [20:20] dobey: I am a bit of a noob so that is a tad over my head. Where can I download the source? [20:21] Xpistos|work: i do presume you mean the ubuntu logo inside the clouds? [20:21] correct. [20:21] dobey: Yes [20:21] Xpistos|work: http://launchpad.net/ubuntuone-client/+download [20:25] dobey: Thank you. That is what I needed === rmcbride changed the topic of #ubuntuone to: Help contact: | File Sharing for Ubuntu | https://ubuntuone.com | https://launchpad.net/ubuntuone | Currently in limited beta, new invitations are sent regularly | Current Beta Client Revno is 113, Protocol Revno is 58 | Release 0.91 === inkvizitor68sl is now known as ink|Regnum [21:32] Hey === heroin is now known as Guest17173 === Guest17173 is now known as heroni [21:33] Hey [21:33] damn :( nick change === kklimonda is now known as Guest41062 === _kklimonda is now known as kklimonda_ === kklimonda_ is now known as Guest67854 === Guest67854 is now known as kklimonda__ === kklimonda__ is now known as kklimonda === kklimonda is now known as Guest30301 === Guest30301 is now known as kklimonda