[00:04] <kklimonda> hmm, is it good idea to add u1 ribbon to $HOME/Downloads?
[00:05] <kklimonda> as it is a default folder for various applications to save downloaded data in it's going to be big.
[10:27] <duanedesign> morning all
[11:30] <rodrigo_> hi duanedesign
[11:31] <duanedesign> hey rodrigo_
[11:33]  * duanedesign is working on a creative uses for ubuntu one blog post.
[11:36] <duanedesign> but i am having trouble coming up with a cron job that will take a screenshot of your desktop every N minutes and save with a unique name.
[11:36] <duanedesign> http://paste.rtg.in.ua/2cd563e9b4a630e2abbdee668b2187a9/
[11:40] <rodrigo_> duanedesign, having trouble with picking a unique name?
[11:44] <rye> duanedesign, i keep coming up with doc/docx/otherproprietaryformats convertor that will work by sharing the folder with some other user, which may run all sort of magic software chain that will print the data into pdf and put the generated file back into the share... Every time i think about that I feel that it is not needed :)
[11:45] <duanedesign> rodrigo_: yes the rodrigo_ i think that is where the problem is. "/home/duanedesign/$(date=%m-%l-%M).png"  is not working
[11:45] <popey> duanedesign: how about a webcam saving images in your u1 storage?
[11:46] <rye> duanedesign, $(date +%m-%l-%M) ?
[11:46] <rye> popey, that can be done by camE btw
[11:46] <popey> there's a command line "webcam" package which can do it too, thats what I use
[11:46] <duanedesign> rye: well the whole line is: 01 04 * * * import -window root -quality 100 "/home/duanedesign/Ubuntu\ One/screenshots/$(date=%m-%l-%M).png"
[11:47] <rye> duanedesign, it will try to run "date=%m-%l-%M" which is not really a command i believe
[11:48] <popey> I get...
[11:48] <popey> import: unable to open image `/home/alan/Ubuntu\ One/screenshots/.png':  @ error/blob.c/OpenBlob/2498.
[11:48] <rye> popey, $() expansion breaks
[11:49] <rodrigo_> duanedesign, replace that with `date +%Y%m%d`
[11:49] <rye> duanedesign, erm, what is the intended expansion for %m-%l-%M ? it gives pretty strange 09- 1-49.png result now
[11:50] <rodrigo_> duanedesign, the '+' is the key
[11:50] <rye> duanedesign, and the space before that + :)
[11:50] <rodrigo_> duanedesign, or $(date  +%Y%m%d)
[11:50] <rodrigo_> yeah, and the space
[11:51] <duanedesign> thank you all!
[11:51] <popey> also, use a better date format than USA!
[11:51] <popey> YYYY-MM-DD
[11:51] <popey> then it sorts properly
[11:52] <popey> the USA date format of MM-DD-YYYY is demented in the extreme for file names
[11:52] <duanedesign> popey: yeah the results coming back are weird....
[11:54] <rodrigo_> duanedesign, yeah, yyyymmdd is the best, for sorting
[12:03] <duanedesign> what is @ error/blob.c/OpenBlob/2498
[12:10] <rye> duanedesign, have you seen lp:~chipaca/+junk/watgui ?
[12:11] <rye> duanedesign, i believe that error is because screenshots folder does not exist
[12:19] <duanedesign> rye: /me looking
[12:58] <Chipaca> kklimonda: I created an old-style u1 token and it started working for me
[12:59] <Chipaca> kklimonda: so if you have oauthdesktop lying around in some old bzr branch, that's what you want to do :)
[13:39] <Chipaca> rye: duanedesign: have you played with that? (the watgui thing)
[13:40] <Chipaca> rye: duanedesign: you need an old-style (pre-sso) token to get to couch, because of a bug server-side
[13:42] <duanedesign> Chipaca: i was just trying it
[13:50] <duanedesign> Chipaca: i am getting http://paste.rtg.in.ua/adddfc9f5c3d54a2c2c494298f90301f/
[13:51] <Chipaca> duanedesign: you need the gir1.0-soup-2.4 package
[13:52] <duanedesign> aha, that the package
[13:53] <rye> Chipaca, i played with that and I won!
[13:55] <duanedesign> Chipaca: yes, much better now :)
[13:56] <Chipaca> rye: did you get couch to couch?
[13:56] <rye> Chipaca, nope, I am not among the lucky $numberofpeoplewithreplicationenabled
[13:57] <Chipaca> rye: aha. So what does going to the couch url do for you?
[13:58] <duanedesign> i got the 503
[13:59] <rye> Chipaca, http://ubuntuone.com/p/HjJ/
[13:59] <rye> Chipaca, 503 to be short
[14:00] <Chipaca> ah well
[14:00] <rye> anybody got alt+PrintScreen running in Maverick?
[14:03] <duanedesign> rye: on my lappy it is sysrq instead of prtsc
[14:03] <duanedesign> fn + sys rq == screenshot
[14:05] <rye> duanedesign, alt+printscreen should yield the screenshot of the current active window only
[14:24] <psypher246> hi ubuntuone team, anyone there?
[14:27] <duanedesign> hello psypher246
[14:28] <psypher246> hi duane, trying to get my pc added a computer agina, but I can't get to that screen at all
[14:28] <psypher246> it was removeed cos the client got confused and told me i need ot add it again
[14:29] <psypher246> in the end i removed both and now i can't add it again
[14:29] <psypher246> where is the button, add this pc?
[14:30] <psypher246> REALLY hope I don't have to upload 20GB again
[14:31] <psypher246> duanedesign: you there?
[14:32] <duanedesign> hello, sorry
[14:32] <duanedesign> psypher246: ok can you try the following
[14:33] <duanedesign> psypher246: close the Ubuntu One Preferences (if  open)
[14:33] <duanedesign> psypher246: open a Terminal and run the command:   u1sdtool -q; killall ubuntuone-login; u1sdtool -c
[14:34] <duanedesign> this should open the browser and prompt you to add your computer
[14:35] <psypher246> just hanging after:
[14:35] <psypher246> $ u1sdtool -q; killall ubuntuone-login; u1sdtool -c
[14:35] <psypher246> ubuntuone-syncdaemon stopped.
[14:36] <duanedesign> ok
[14:37] <duanedesign> psypher246: can you open Applications > Preferences >. Password and Encryption Keys
[14:37] <duanedesign> sorry, applications > accessories
[14:38] <psypher246> yeah i had to dfelete that whoile gnome kyrimg folder cos i changed my password
[14:39] <duanedesign> psypher246: ok so there is no Ubuntu One Token left in Seahorse?
[14:39] <psypher246> well there was now
[14:40] <duanedesign> if there is could you right-click and delete it
[14:40] <psypher246> ok
[14:40] <duanedesign> psypher246: ok did the terminal command finally give you a dbus error?
[14:40] <psypher246> ok u1sdtool -c does not start the clinet, client started now from me menu and NOW it's asking to join pc, why does the clinet not start with -c?
[14:44] <duanedesign> psypher246: usually when a u1sdtool hangs like that the syncdaemon is busy doing something and not able to respond to your command at the moment
[14:45] <psypher246> ok well it looks like it's working. do you know how to get ubuntu one to sync my private encrypted folder?
[14:45] <psypher246> tried the right click and sync with ubuntu one, well that just crashed nautilus and now that option is greyed out
[14:55] <rye> psypher246, if you want to sync Private folder you should know that your data will not be encrypted on the servers, if you want to sync .Private folder then the events about file changes may not reach syncdaemon
[14:55] <duanedesign> psypher246: you can check if it 'took' with the command: u1sdtool --list-folders
[15:00] <psypher246> no i tried it did take the command
[15:00] <psypher246> rye: so trying either private or .private won't work
[15:01] <psypher246> so i DIDn'T take the folder and sync it
[15:01] <psypher246> list folder shows nothin
[15:01] <rye> psypher246, Private will work but it will not be that private and I had mixed results with using .Private
[15:01] <rye> psypher246, let me try this again
[15:01] <psypher246> ok how bout this
[15:01] <rye> now on Maverick :)
[15:01] <psypher246> ag forget it it won't work
[15:02] <psypher246> so hopefully someday we can have encrypted folders as well on u1
[15:03] <psypher246> best i can do i create a new encrypted folder in the u1 folder mount it and manually sync my important info which must be encrypted to that folder. will that work?
[15:15] <zeroXten> anyone else having problems with U1 syncing atm?
[15:18] <rye> zeroXten, what issue are you experiencing?
[15:19] <zeroXten> ahh.. it has gone up
[15:19] <zeroXten> very slow, and it looks like perhaps the UI doesn't update unless its reopened
[15:19] <zeroXten> hmmm
[19:11] <Chipaca> kklimonda: ping
[19:11] <kklimonda> pong
[19:11] <Chipaca> kklimonda: have you been able to get the old token?
[19:12] <Chipaca> kklimonda: if no, can you apply http://pastebin.ubuntu.com/501670/ and tell me if it works for you?
[19:12] <kklimonda> Chipaca: no, I don't know where to look for it
[19:12] <kklimonda> sure
[19:13] <Chipaca> nessita: kklimonda has a sso token and a low user id
[19:13] <Chipaca> nessita: so he's testing :)
[19:14] <nessita> awesome!
[19:14] <kklimonda> Chipaca: with the patch I get "{"error":"invalid_token","reason":"Invalid OAuth token."}" when I open magic:couch
[19:14] <Chipaca> kklimonda: rather than the 'bad consumer' you got before
[19:15] <kklimonda> yes, it's a new error :)
[19:15] <Chipaca> I suspected as much
[19:15] <Chipaca> nessita: thisfred: ^
[19:15] <nessita> Chipaca: who's returning that? I mean, who is validating the token and against what source?
[19:16] <Chipaca> nessita: I think that is couch itself
[19:16] <nessita> right, and is querying the account database... I guess?
[19:16] <Chipaca> nessita: no, it queers the users database
[19:17] <Chipaca> nessita: *disastrous* consequences... or wonderful, depending which side of the closet you're on
[19:17]  * Chipaca stops
[19:18] <nessita> Chipaca: I know an account database and a storage database. Which one is users? :-)
[19:18] <Chipaca> nessita: the couchdb _users database
[19:19] <Chipaca> nessita: open futon and look at yours :)
[19:19] <Chipaca> nessita: the ubuntu one's one is ... slightly larger
[19:19] <Chipaca> but essentially the same :)
[19:19] <Chipaca> right, thisfred?
[19:19]  * Chipaca might be getting this all wrong but thinks not
[19:19] <nessita> Chipaca: ah, so it may occur that the signal is not processed properly in cloud_server. In any case, I'm submitting a branch and I'll add some debug
[19:20]  * thisfred is not here, but yes, that is correct
[19:20] <Chipaca> nessita: no, the *invalid* token is because a token can only be 'unpacked' with the right consumer token
[19:20] <nessita> ah!
[19:20] <Chipaca> nessita: *handwave*
[19:21] <nessita> Chipaca: wait - where is couch trying to unpack it?
[19:21] <Chipaca> nessita: I don't know - but is that relevant?
[19:22] <nessita> Chipaca: yes, it is. I mean, what I consider "unpacking a token" is the code located ion pull_data_from_sso. IF any other piece of code is "unpacking a token" (ie accessing SSO server), we may have a design issue
[19:22] <thisfred> I don't think there is any packing or unpacking: the two legged oauth uses the consumer token + secret and the regular token + secret to sign the request and couch uses those four to verifyu the signature
[19:23] <thisfred> couch (on the server) only looks in the _users db
[19:24] <nessita> thisfred, Chipaca: were the consumer and token are separated, no need to unpack one from the other, right?
[19:24] <thisfred> we store the 4 bits of oauth info in the user's document
[19:24] <Chipaca> my limited understanding is that those four secret bits (the consumer key and secret, and the session key and secret) are not sent over the wire, but that what is sent over the wire needs those four bits at the other end to unpack what is sent over the wire
[19:24] <thisfred> nessita: Chipaca: essentially correct, at least when using hmac-sha1, (plaintext does send the tokens)
[19:25] <Chipaca> hmm!
[19:25] <Chipaca> hold on
[19:25] <thisfred> Chipaca: except I wouldn't call it packing/unpacking
[19:25] <Chipaca> kklimonda: did you uncheck 'hmac'?
[19:25] <Chipaca> thisfred: poteito, potahto
[19:25] <Chipaca> thisfred: :-p
[19:26] <thisfred> Chipaca: well, the content of the request is not packed/encrypted or anything, it's just signed.
[19:26] <thisfred> because we send it over ssl that's fine
[19:26] <kklimonda> Chipaca: no, but it doesn't change anything
[19:26] <Chipaca> kklimonda: ok, thanks
[19:26] <thisfred> anyway, back to finding something to eat
[19:27]  * thisfred forages
[20:50] <Chipaca> kklimonda: ping
[21:00] <kklimonda> pong
[21:00] <kklimonda> Chipaca: ^
[21:02] <Chipaca> kklimonda: hi. Question: the error you got re "invalid token", that was with the patch applied, right?
[21:02] <kklimonda> Chipaca: yes
[21:03] <Chipaca> kklimonda: could you try generating a brand new sso token and trying again?
[21:04] <Chipaca> kklimonda: it works for me (tm) :)
[21:04] <kklimonda> Chipaca: sure, but a bit later
[21:05] <Chipaca> kklimonda: ok