[00:03] <hggdh> bdmurray: available?
[00:05] <bdmurray> hggdh: for you? always ;-)
[00:14] <kklimonda> hmm.. bug 628464 looks like a duplicate of bug 412944 but the latter should be fixed..
[00:14] <ubot2> Launchpad bug 628464 in couchdb-glib (Ubuntu) "package libdesktopcouch-glib-1.0-2 (not installed) failed to install/upgrade: (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/628464
[00:14] <ubot2> Launchpad bug 412944 in adobe-flashplugin (Ubuntu) "[Karmic] Removing Flash Plugin causes annoying package managing problems (affects: 209) (dups: 40) (heat: 319)" [Undecided,Fix released] https://launchpad.net/bugs/412944
[00:15] <kklimonda> any ideas whether it's a duplicate or only a similar issue?
[00:23] <micahg> kklimonda: you have the right bug #?
[00:24] <kklimonda> micahg: what do you mean?
[00:24] <kklimonda> micahg: oh, yes
[00:25] <kklimonda> micahg: if you check the logs from 628464 you can see errors with update-alternatives and iceape-flash..
[00:36] <micahg> kklimonda: we don't have iceape-flash in teh archive
[00:41] <kklimonda> micahg: I can only guess it came from medibuntu then
[00:42] <kklimonda> micahg: or from partner repository: https://edge.launchpad.net/ubuntu/+source/adobe-flashplugin
[00:42] <micahg> kklimonda: that's not iceape-flash
[00:42] <kklimonda> micahg: but it may provide iceape-flash through alternatives
[00:42] <hggdh> sbeattie: OK, nagios3 is running (but I had about 4 failures)
[00:45] <micahg> kklimonda: it could be flashplugin-installer ass well
[00:45] <micahg>  /etc/alternatives/iceape-flashplugin -> /var/lib/flashplugin-installer/npwrapper.libflashplayer.so
[00:45] <micahg> *as well
[00:47] <kklimonda> same with adobe-flashplugin.. neither is installed on OP's system (nor can I find anything relevant in attached /var/lib/dpkg/status) so we may not know
[00:47] <BUGabundo> nite
[00:48] <kklimonda> or not - it may still sit in /var/lib/dpkg/status - either adobe-flashplugin.prerm or flashplugin-installer.prerm
[00:48] <micahg> kklimonda: in hardy it would've been flashplugin-nonfree
[00:48] <kklimonda> yeah, I was going to say exactly that :)
[00:51] <kklimonda> can I reassign bug to no package?
[00:51] <kklimonda> well, I think I can but how :)
[00:52] <micahg> kklimonda: remove the package
[00:54] <kklimonda> micahg: ah, that makes some twisted sense :)
[01:03] <snadge> #578035
[01:03] <snadge> i thought there was a bot that gave a summary of the bug when you put the bug number in
[01:04] <snadge> !bug 578035
[01:04] <ubot2> Launchpad bug 578035 in openssh (Ubuntu) "ssh-askpass-gnome doesn't prompt for password in any release post ubuntu 8.10 32/64bit (affects: 1) (heat: 39)" [Undecided,Confirmed] https://launchpad.net/bugs/578035
[01:04] <snadge> the workaround is to manually add the key with ssh-add .. i dont like it
[01:07] <kklimonda> snadge: do you have seahorse-agent running?
[01:08] <snadge> kklimonda: apparently not
[01:09] <kklimonda> hmm, I'm not actually sure if it's responsible for ssh keys - it is for gpg ones..
[01:09] <kklimonda> lets see
[01:09] <snadge> i _think_ ssh-askpass-gnome is responsible for ssh keys
[01:10] <kklimonda> no, the owner of SSH_AUTH_SOCK is gnome-keyring-daemon itself
[01:10] <snadge> ahh okay.. when i opened up one of my messaging clients, possibly empathy.. it asked me to unlock my keyring
[01:11] <snadge> which is a different password to what my ssh key uses
[01:11] <hggdh> and a different password than your login?
[01:13] <hggdh> snadge: ^
[01:13] <snadge> yes
[01:14] <snadge> actually my login and ssh key use the same passphrase.. but my keyring uses a different one
[01:14] <kklimonda> snadge: and keyring stores ssh key password in its database
[01:14] <hggdh> snadge: there you go. Make the keyring password the same as the login, and it will be automagicallt opened on login
[01:14] <snadge> how do i change my keyring password?
[01:14] <snadge> luls ;)
[01:15] <hggdh> run seahorse, or "Password and encryption keys".
[01:15] <kklimonda> I wonder why is seahorse caching gpg password but g-k-d is the one responsible for ssh one..
[01:16] <hggdh> kklimonda: it is all, er, "the same" (sort of). seahorse and g-d-k are developed by the same people, AFAICR
[01:16] <hggdh> g-k-d. Oh dyslexia
[01:17] <snadge> ok so i've run seahorse.. now im looking for the change keyring password option
[01:17] <kklimonda> hggdh: but it's yet another thing users, administrators and us have to remember about :)
[01:17] <hggdh> kklimonda: indeed :-)
[01:18] <hggdh> snadge: alt-click on your login keyring, select change password
[01:18] <snadge> got it :)
[01:18] <snadge> i guess i have to relogin?
[01:18] <hggdh> it would be a good test, yes
[01:21] <kklimonda> what's funny is that even if I lock my keyring ssh password is still stored..
[01:22] <kklimonda> in memory*
[01:22] <snadge> its still doing it :|
[01:22] <snadge> prompting me for my passphrase in the terminal when i use ssh.. without popping up the GUI like it used to, i can't imagine whats changed
[01:23] <snadge> maybe i need to restart ssh or reboot.. i dont know
[01:23] <snadge> i just logged out and back in again
[01:23] <kklimonda> snadge: what is SSH_AUTH_SOCK set to?
[01:23] <snadge>  /tmp/keyring-QEMju3/ssh
[01:24] <kklimonda> and does lsof /tmp/keyring-QEMju3/ssh give the same pid that GNOME_KEYRING_PID?
[01:27] <snadge> checking
[01:27] <snadge> the file is a socket.. and when i cat it, i get
[01:28] <snadge> cat: /tmp/keyring-QEMju3/ssh: No such device or address
[01:28] <snadge> oh woops lsof :p
[01:28] <kklimonda> yeah
[01:28] <snadge> yes it gives the pid of the gnome-keyring-daemon which is running
[01:29] <kklimonda> snadge: is your keyring unlocked? can you open Passwords and Encryption Keys and browse stored passwords?
[01:29] <snadge> where is passwords and encryption keys in the menu?
[01:29] <kklimonda> run seahorse
[01:30] <kklimonda> and it's in Applications->Accesories in 10.04 afair
[01:30] <kklimonda> got moved to System->Preferences in maverick
[01:30] <snadge> got it yep
[01:30] <snadge> yes i think thats an appropriate move.. thats where i was looking ;)
[01:31] <snadge> ok i have two keys.. one called "login" one called "default"
[01:31] <kklimonda> now if it's not the case you can only check with the brand new user. this bug actually screams "local changes broke it" as this feature is probably the most used by developers :)
[01:31] <snadge> login is unlocked.. but default is locked
[01:31] <snadge> i should try unlocking default?
[01:32] <kklimonda> yes
[01:32] <snadge> ok its unlocked.. but this hasn't seemed to help ssh
[01:32] <kklimonda> but I'm not sure whether it being locked could break.. yeah..
[01:32] <snadge> inside it contains a wireless network password, and an msn password
[01:33] <kklimonda> snadge: have you had this problem since installation or has it shown after the upgrade? have you tried this with the new user?
[01:33] <snadge> ssh-add seems to work as you would expect, but obviously its uncool to have to do this every time you login.. particularly since its supposed to be all automagic
[01:34] <snadge> problem was since a complete re-install from scratch
[01:34] <snadge> i'll try creating a new user
[01:34] <snadge> the reinstall picked up my old install on another hard drive, and prompted me to import settings and i said yes
[01:35] <kklimonda> well, that may be a problem if there is something wrong with your configuration
[01:35] <snadge> what can i try blowing away or moving out of the way?
[01:37] <kklimonda> I'm not sure what could be responsible for that - I can't recreate it myself on pristine 10.04 installation
[01:37] <snadge> .gnome2/keyrings/ ?
[01:38] <snadge> i just moved that out of the way.. will see what that does
[01:38] <kklimonda> I don't think that could help
[01:38] <kklimonda> even with keyring locked you should still get a dialog
[01:40] <kklimonda> and gnome-keyring-daemon is responsible for the dialog (so bug should probably be reassigned)
[01:40] <snadge> yes that didn't help :/
[01:41] <snadge> creating a new user called test
[01:43] <snadge> ok same thing.. how frustrating
[01:44] <snadge> what should be the permissions of your .ssh dir and the id_dsa file?
[01:45] <kklimonda> 0700 and 0600
[01:45] <snadge> thats what i've got
[01:48] <kklimonda> maybe try running ssh with -vvv and see if anything related to agent shows up
[01:51] <snadge> it doesnt mention anything about the agent no
[01:51] <kklimonda> maybe try running ssh with -vvv and see if anything related to agent shows up/
[01:51] <snadge> i'll pastebin it
[01:51] <kklimonda> erm
[01:51] <kklimonda> what does gconftool-2 --get /apps/gnome-keyring/daemon-components/ssh return?
[01:52] <snadge> true
[01:52] <kklimonda> yeah, pastebin it
[01:52] <kklimonda> but I'm completely out of ideas
[01:53] <snadge> http://pastebin.com/S1ruwM9a
[01:53] <snadge> i have a netbook that i have recently installed 10.04 64bit on
[01:53] <snadge> i might try copying my key file over to that, and see what it does
[01:54] <snadge> its annoying not being able to reproduce bugs ;)
[01:55] <kklimonda> indeed
[01:55] <snadge> im new to attempting to do this so forgive me for stating the obvious hehe
[01:55] <drew212> snadge: that is the key problem of debugging =P
[01:56] <snadge> i was thinking earlier.. this bug is f$#@ing irritating.. why hasn't something this fundamental been fixed
[01:56] <snadge> now i know why ;)
[01:59] <snadge> ok the fscking netbook does it too
[01:59] <snadge> maybe theres something mong about my key?
[02:00] <snadge> maybe i should try it in a 32bit virtual machine
[02:00] <kklimonda> snadge: what cay does it actually use?
[02:00] <snadge> bonus.. its karmic
[02:01] <kklimonda> I see: debug2: key: /home/davidb/.ssh/id_rsa ((nil))
[02:01] <kklimonda> debug2: key: /home/davidb/.ssh/id_dsa ((nil))
[02:01] <kklimonda> debug2: key: /home/davidb/.ssh/identity ((nil))
[02:01] <snadge> this is bad i take it?
[02:01] <kklimonda> and below "no such identity" for all keys
[02:02] <kklimonda> I'm not exactly sure but that's the only weird thing I see in the log
[02:03] <kklimonda> it does try all three of them and return "no such identity" for either.
[02:03] <kklimonda> s/either/all/
[02:04] <snadge> well im just re-installing the guest additions to my 32bit karmic vm
[02:04] <snadge> so i can copy my key into it and try it on that
[02:04] <kklimonda> is it actually /home/davidb/.ssh/id_rsa ?
[02:05] <snadge> there is no rsa file, only dsa
[02:06] <kklimonda> but if you add it manually server accepts it?
[02:06] <snadge> correct
[02:06] <snadge> ok 32bit karmic does exactly the same thing
[02:06] <snadge> hehe
[02:07] <kklimonda> snadge: can you generate RSA 2048, upload it to your server and test again?
[02:07] <snadge> sure.. i'll give it a shot
[02:08] <snadge> i think you might be onto something.. it would seem most people use an rsa key
[02:08] <snadge> but for whatever reason, i have a dsa key (i have no idea why, it was too long ago to remember)
[02:09] <kklimonda> and both you and OP use dsa keys..
[02:09] <kklimonda> it's pretty far-stretched but I'm out of ideas
[02:11] <kklimonda> hmm.. from http://live.gnome.org/GnomeKeyring/Ssh: "Version 1 of the SSH agent protocol is supported in compatibility mode. No integration with Gnome Keyring exists for keys loaded this way. SSH version 1 keys can loaded with ssh-add will work as expected. "
[02:12] <snadge> i see.. my key is too old school
[02:12] <snadge> this is even more bizarre.. i just generated a brand new rsa key
[02:12] <snadge> attempted a login to a server at work
[02:12] <snadge> and it just allowed me to login straight away, without adding that key to "authorized_keys" file
[02:12] <snadge> wtf?
[02:13] <kklimonda> you have your dsa in cache?
[02:13] <kklimonda> see ssh-add -l
[02:13] <snadge> ahh because of ssh-add yes.. lol
[02:14] <snadge> ok so we've now finally determined the problem, at some point.. gnome keyring stopped supporting older dsa keys
[02:15] <snadge> but from the man page.. dsa was only supported in protocol version 2
[02:15] <snadge> version 1, only supported rsa.. bizarre
[02:16] <kklimonda> no, it still supports them - but you have to use ssh-add to add them
[02:16] <bcurtiswx> what would i report a v4l issue under package-wise?
[02:16] <bcurtiswx> gstreamer ?
[02:16] <snadge> kklimonda: but why?
[02:17] <snadge> maybe i should just be thankful that the problem has been determined.. and just generate a new key
[02:17] <snadge> however, i would like to save people the frustration of going through what i just have.. perhaps i will leave a comment in the bug on launchpad
[02:17] <kklimonda> snadge: I have no idea - it fully supports only the second version of ssh protocol.. but I don't see how that relates to dsa and rsa..
[02:17] <kklimonda> snadge: I'll add a coment shortly
[02:18] <snadge> having to replace my key on every single server i have access to.. just to work around this problem, is slightly annoying however.. so i will just use ssh-add for now :)
[02:21] <snadge> ok verified the dialog pops up correct for an rsa generated key
[02:21] <kklimonda> I think it may be related to how old the key is
[02:21] <kklimonda> I've created new dsa key and it worked
[02:21] <snadge> ok one other thing i've noticed is the rsa key is much shorter than my dsa key
[02:21] <snadge> perhaps i used an old guide some time ago.. that recommended using a larger keysize or something
[02:23] <snadge> my brain is hazy.. but should i pastebin my .authorized_keys file?
[02:23] <kklimonda> nah
[02:23] <snadge> thats a public key isnt it..
[02:25] <kklimonda> yes
[02:26] <kklimonda> but it won't tell me anything :)
[02:26] <snadge> ok now im about to get grilled for all the things i should've been doing instead of chasing htis bug ;) (in a meeting)
[02:26] <snadge> but im just going to blame stress and all sorts of other emotional problems
[02:26] <snadge> and then break down in tears and tell him to fire me
[02:27] <kklimonda> :)
[02:31] <snadge> do you think the problem is perhaps fixable now that we know a bit more about it?
[02:31] <kklimonda> snadge: no - it's not a bug but Gnome Keyring developers' decision not to fully support old version of ssh protocol (and apparently old keys)
[02:33] <kklimonda> snadge: I wonder, can you do
[02:33] <kklimonda> ssh-add -D
[02:33] <kklimonda> move ~/.ssh/id_rsa key somewhere else so only your old id_dsa key stays
[02:34] <kklimonda> and then force ssh to use v2 protocol (by calling ssh -2 host)
[02:34] <kklimonda> does it detect your dsa key?
[02:34] <kklimonda> by it I mean server
[02:56] <bcurtiswx> whats the default spell checker for ubuntu
[02:56] <bcurtiswx> aspell still?
[03:32] <snadge> kklimonda: sorry i was just in a meeting.. which i successfully negotiated not being blamed for derelict of duties :p
[03:34] <gorilla> snadge: eww. nasty.
[03:37] <snadge> my job i used to be cruising on easy street, but the company is transitioning from yahoo wild west style, to proper formal company style, and as such my workload has significantly increased
[03:38] <snadge> so developer type stuff is creeping into my sysadmin role, and im completely unfamiliar with how the system works from that perspective.. now i have to implement change requests and things like that, revoke developers access etc
[04:11] <bcurtiswx> all bugday new bugs taken care of :D
[04:16] <nigelb> that was fast
[04:16] <nigelb> it isn't yet thursday in some tz you know :p
[04:18] <Muscovy> Wow.
[04:19] <Muscovy> It's not even Sept 2nd for me either.
[04:28] <bcurtiswx> not here either
[04:28] <bcurtiswx> im the empathy guy, figured it was only right
[04:28] <nigelb> :)
[04:28]  * nigelb hugs bcurtiswx :)
[04:31] <bcurtiswx> :)
[04:53] <snadge> kklimonda: ssh -2 seems to have the same result
[08:51] <dwassel> Hi
[08:51] <dwassel> I seem to have found an issue with eglibc on lucid and I am not sure where and how to report it
[09:00] <dwassel> alright, I'll just dive into the details: I can observe differences in the results (minor) and runtime (drastic!) of the exp function between 32 and 64 bit versions on an Intel core2.
[09:02] <dwassel> the underlying reason seems to be that 32-bit libm calculates exp (and log, and possibly others) by __ieee754_exp, which uses some table-lookup and checks its own numeric error
[09:04] <dwassel> (actually both "bitness" versions due this, of course). Thing is, when calling exp with arguments close to eps, the check seems to succeed for 32-bit libm, but fails for 64-bit libm, so a soft-float variant of exp is called, which is accurate, but horribly slow
[09:06] <dwassel> this might be more suitable for libc, but eglibc is pretty inactive, and I am *very* hesitant to take this before the Drepper guy
[12:03] <vish> hmm , i thought we had 3-4 empathy adopters , why are so many bugs marked incomplete even after the questions have been answered :s
[13:08] <htorque> hello, i'm subscribed to four unity bugs that have their distro tasks marked "fix released" but their upstream tasks still say "fix committed" - should i update that to "fix released"?
[13:10] <seb128> htorque, depends if upstream rolled a tarball
[13:10] <seb128> htorque, we sometime backport changes before they do
[13:10] <seb128> could somebody test bug #612825?
[13:10] <ubot2> Launchpad bug 612825 in language-selector (Ubuntu) "[ubuntu] maverick: can't install new languages (nothing happen) (affects: 5) (heat: 137)" [Low,Confirmed] https://launchpad.net/bugs/612825
[13:10] <seb128> on a beta iso
[13:10] <seb128> pedro_, ara: ^
[13:10] <seb128> bug #625643 is similar
[13:10] <ubot2> Launchpad bug 625643 in language-selector (Ubuntu) "Not installing language packs after password (affects: 4) (dups: 1) (heat: 24)" [Low,New] https://launchpad.net/bugs/625643
[13:11] <seb128> if that's still happening the bug should be nominated
[13:11] <pedro_> seb128, looking
[13:11] <seb128> pedro_, ola
[13:11] <seb128> thanks ;-)
[13:11] <seb128> or is that hola?
[13:12] <pedro_> seb128, it is hola but ola also works ;-)
[13:12] <htorque> seb128, yes, there's a tarball available to contains all those fixes
[13:12] <bcurtiswx> Hey all, in case you didn't know.  Our buds over at #empathy have given us special updated packages to test bugs against today
[13:12] <seb128> works fine for french, we don't spell the h anyway there
[13:12] <htorque> *that
[13:12] <seb128> htorque, close the tasks then
[13:12] <bcurtiswx> https://edge.launchpad.net/~telepathy/+archive/ppa/+packages?field.name_filter=&field.status_filter=published&field.series_filter=maverick
[13:12] <htorque> seb128, thanks :)
[13:13] <vish> bcurtiswx: that should be updated in the wiki as well :)
[13:13]  * bcurtiswx is editing
[13:16] <bcurtiswx> added :)
[13:17] <bcurtiswx> vish: i like your pyramid approach going here (bottom up)
[13:18] <vish> bcurtiswx: heh, felt pretty depressing looking at those bugs! pretty bad state of the bugs though.. :s
[13:19] <bcurtiswx> vish: yeah, think of how I feel.  I still have to wait to start attacking these bugs
[13:19] <bcurtiswx> (qualifiers)
[13:19] <bcurtiswx> aaanyways, i have to get things going to work, bbs
[14:16] <Dink> Is there a site where I can go to where it lists what package was released on a specific day and view what it fixed ?
[14:18] <nigelb> Dink: you want to see changelogs?
[14:18] <Dink> Yeah
[14:18] <nigelb> packages.ubuntu.com would be a userfriendly place
[14:18] <nigelb> or changelogs.ubuntu.com if you're ok with searching
[14:19] <Dink> hmm looking for something I found the other day but forgot to bookmark. It wasn't those. It gave details on dates and what packages where released.
[14:20] <Dink> ahh found it. www.ubuntuupdates.org
[14:21] <Dink> nigelb, thanks for the help. I just needed that extra push to find it.
[14:26] <nigelb> Dink: that isn't an official site though.
[14:35] <Dink> nigelb, yeah figured based on the the url. It is a good site though. If there is an office site similar please let me know.
[14:36] <nigelb> Dink: I like what it does, just unsure of how fast info gets updated there
[14:36] <nigelb> There isn't /one/ place where you can do all that officially though
[14:37] <Dink> Ahh. Yeah not sure on how fast it gets updated. But most things are there when I try to look for them.
[15:12] <ashams> hi
[15:13] <ashams> #ubuntu-bugs: can someone help me! :)
[15:13] <nisshh> ashams: whats up?
[15:13] <ashams> nisshh: hi
[15:14] <nisshh> hey
[15:15] <ashams> nisshh: I want to attach multiple files all at once to some bug report, is this available in LP?
[15:15] <nisshh> ashams: im not sure
[15:15] <nisshh> ashams: let me have a look see
[15:16] <ashams> nisshh: ok
[15:16] <ashams> nisshh: I'll try to look at the LP help.
[15:17] <nisshh> ashams: ok, i dont think it will be in there
[15:17] <ashams> nisshh: so, where to look?
[15:18] <bilalakhtar> ashams: no you cannot
[15:18] <bilalakhtar> ashams: you have to attach it one-by-ope
[15:18] <bilalakhtar> *one
[15:18] <nisshh> bilalakhtar: didnt think so
[15:19] <bilalakhtar> nisshh: It is possible through the API, though
[15:19] <nisshh> bilalakhtar: would be a good feature though
[15:19] <nisshh> ah ok
[15:19] <bilalakhtar> nisshh: but the Web UI restricts it
[15:19] <nisshh> yea
[15:19] <nisshh> unfortunat3
[15:19] <nisshh> -3*
[15:19] <bilalakhtar> for example, in apport bugs, many attachments are attached at once
[15:20] <ashams> nisshh: so, how can I reach that API for future use?
[15:20] <nisshh> yea
[15:20] <bilalakhtar> 'coz apport uses the LP API
[15:20] <bilalakhtar> ashams: write an app for it :)
[15:20] <nisshh> ashams: its the API that runs launchpad
[15:20] <nisshh> ashams: or use launchpadlib :)
[15:20] <ashams> bilalakhtar: that's exactly what made me tought that it might be possible
[15:21] <bilalakhtar> nisshh: launchpadlib is somewhat bulky
[15:21] <nisshh> bilalakhtar: how so?
[15:21] <bilalakhtar> nisshh: Its API calls consume high bandwidth
[15:21] <nisshh> oh, do they?
[15:22] <nisshh> bilalakhtar: i thought lplib was the only way for a python app to interface with lp?
[15:22] <nisshh> or am i wrong?
[15:22] <bilalakhtar> yes they do, I went on to write an app, gave up because of the speed
[15:22] <bilalakhtar> nisshh: correct and wrong
[15:22] <bilalakhtar> nisshh: Its the only Python lib that facilitates that
[15:22] <nisshh> how is that possible?
[15:23] <bilalakhtar> nisshh: at the same time, as the wiki states
[15:23] <nisshh> hmmm
[15:23] <bilalakhtar> 'If you are using some other language than Python, you will have to wrap around the API yourelf'
[15:23] <bilalakhtar> *yourself
[15:23] <charlie-tca> You can use the email interface to attach more than one file at a time
[15:23] <ashams> charlie-tca: How to?
[15:24] <nisshh> bilalakhtar: so i cold write my own wrapper for the API?
[15:24] <bilalakhtar> so, if you want to write in C, you will have to use curl, for example, to interface with LP in a more dirtier way
[15:24] <nisshh> urh
[15:24] <bilalakhtar> nisshh: of course! one exists for PHP, AFAIK
[15:24] <nisshh> no thanks
[15:24] <charlie-tca> https://help.launchpad.net/Bugs/EmailInterface
[15:24] <nisshh> bilalakhtar: but what if i wanted my python app to interface with LP?
[15:24] <bilalakhtar> nisshh: use launchpadlib :(
[15:25] <Pici> nisshh: see https://help.launchpad.net/API
[15:25] <nisshh> bilalakhtar: heh, so why does lplib use so much bandwidth when interfacing with lp?
[15:25]  * devildante has 5000+ karma! yay!
[15:25] <nisshh> Pici: thanks
[15:25] <bilalakhtar> nisshh: well, it makes too many calls for a single purpose, but I agree its easy-to-use
[15:26] <nisshh> yea
[15:26] <bilalakhtar> nisshh: AND its well-written and less buggy
[15:26] <nisshh> bilalakhtar: are there plans to improve lplibs performance?
[15:26]  * bilalakhtar is not an lplib developer
[15:26] <hggdh> vish: there?
[15:26] <nisshh> i know
[15:27] <nisshh> bilalakhtar: ill have a look at it, i might fiddle with it
[15:27] <bilalakhtar> Congratulations devildante !
[15:27] <devildante> thanks, bilalakhtar :)
[15:27]  * hggdh has less karma than devildante
[15:27] <devildante> !
[15:28] <hggdh> nigelb: ping... ping... PING...
[15:28] <nigelb> hggdh: pong
[15:28]  * bilalakhtar has less karma than nigelb 
[15:28]  * nigelb never looked at karma after it crossed 100
[15:28]  * devildante has also less karma than nigelb
[15:29] <nigelb> after sometime you never look at karma
[15:29]  * bilalakhtar also never looks at hi karma
[15:29]  * charlie-tca thinks it never occurred to him to look at karma
[15:29] <bilalakhtar> well, karma means 'work done' in hindi
[15:29] <nigelb> Now, to look at how much I do actually have
[15:30]  * devildante sees bilalakhtar has more karma than nigelb
[15:30] <bilalakhtar> devildante: maybe, I didn't see nigelb's , I just guessed!
[15:30]  * devildante is not that far from nigelb
[15:30] <devildante> ;)
[15:31] <nigelb> devildante: It decays :)
[15:31] <nigelb> I haven't been very active with karma-ish stuff
[15:31] <devildante> nigelb: no excuses :p
[15:31] <charlie-tca> drops with each release. But a lot of things are not counted
[15:31] <nigelb> organizing irc sessions, helping with news team and stuff are not karma-ish stuff :)
[15:31] <charlie-tca> Wiki updating, irc help, too
[15:31]  * bilalakhtar 's karma shot up when he got involved with ubuntu development
[15:32]  * devildante seconds bilal
[15:32] <nigelb> charlie-tca: that's why in membership meetings the board tends to look at testimonials rather than karma
[15:32] <charlie-tca> correct
[15:33]  * bilalakhtar is lucky to have not applied for membership through an RMB
[15:33] <charlie-tca> and why it is important to be active within the community, rather than active in an activity
[15:33] <nigelb> well, developers are not intended to apply through rmb, which is why dmb exists
[15:34] <bilalakhtar> nigelb: IMHO applying for membership throught the DMB and developing for Ubuntu is easier than doing community work and applying through an RMB
[15:34] <bilalakhtar> in MY opinion
[15:34] <nigelb> bilalakhtar: It depends on what you're working on
[15:34] <nigelb> I went through rmb and didn't have much pains
[15:35] <nigelb> But then, I had a good deal of community work and still do.
[15:35] <bilalakhtar> nigelb: actually, I have seen people applying more than once to RMBs to become members
[15:35] <charlie-tca> MIne went right through, but I don't think I could get approval from dmb
[15:35] <bilalakhtar> that gave be the thinking
[15:35] <bilalakhtar> *me
[15:35] <nigelb> Well, you have took at cause of rejection
[15:35] <nigelb> the most awesome application at an rmb was sense
[15:36] <nigelb> before he could type his intro, he got +1s :D
[15:36] <devildante> what is dmb and rmb?
[15:36] <bilalakhtar> DMB -> Developer Membership Board
[15:36] <nigelb> Everyone knew him in the community + he did awesome work, further emphasizing charlie-tca's point
[15:36] <nisshh> nigelb: why is that?
[15:36] <nisshh> nvm
[15:36] <bilalakhtar> RMB -> Regional Memberhsip boards
[15:38] <nisshh> bilalakhtar: apparently mavericks version of lplib has some big performance improvements
[15:38] <bilalakhtar> nisshh: really? I never tested it on my maverick sys
[15:40] <nisshh> bilalakhtar: yea, apparently the newest versions of lplib (according to the NEWS file in the source) make far fewer HTTP requests and various other things, also there are some improvements in lazr.restful as well
[15:41] <bilalakhtar> good
[15:41] <nigelb> nisshh: Also, with LP, you need to write good code to make sure you aren't making too many requests
[15:41] <nisshh> although im not running maverick grrrr
[15:41] <nisshh> nigelb: yea, i can see that would be an issue
[15:42] <nigelb> I mean looping through all the bugs and filtering for LP isn't a great idea and a lot of stuff like that
[15:42] <nigelb> I've been through it when I've written scripts
[15:42] <nisshh> yea
[15:42] <nigelb> And when you want only number of results there are far more efficient methods than looping through every bug and doing i++
[15:43] <nisshh> nigelb: in my app, i want to user to be able to enter a bug number and it will search for it and return the description
[15:43] <nisshh> which shouldnt be too many requests
[15:43] <nigelb> nisshh: desktop app?
[15:43] <nisshh> nigelb: yep
[15:43] <nisshh> written in Python
[15:44] <nigelb> !info bughugger
[15:44] <nisshh> ah yes
[15:44] <ubot2> nigelb: bughugger (source: bughugger): Client for Managing Ubuntu Bug Tasks. In component universe, is extra. Version 10.04 (lucid), package size 125 kB, installed size 524 kB
[15:45] <nigelb> nisshh: ^^ take a look at it.  I'm not sure how well it works
[15:45] <nisshh> nigelb: iv used it
[15:45] <nigelb> I'd encourage you to fix it if its broken rather than writing a whole new one
[15:45] <nisshh> nigelb: my app isnt anything like bughugger
[15:45] <nigelb> Ah, ok
[15:46] <nisshh> nigelb: my app -> https://launchpad.net/pytask
[15:46] <nigelb> nisshh: sweet!
[15:47] <nisshh> :)
[15:47] <nigelb> nisshh: oh yeah! congrats on membership :)
[15:47] <vish> hggdh: Oui, monsieur
[15:47] <nisshh> nigelb: thanks :)
[15:48] <nigelb> vish: oh? getting a bit foreign now? :p
[15:48] <hggdh> vish: got what I needed, merci
[15:49] <vish>  ;p
[15:49]  * nigelb just made the mistake of /lastlog hggdh 
[15:49] <nigelb> hggdh => you talk way too much :p
[15:49] <hggdh> heh
[15:49] <hggdh> and I have been pretty much silent lately...
[15:52] <devildante> thanks bilalakhtar
[17:40] <bcurtiswx> on LP, how do I add a empathy lucid task in specific.
[17:43] <bcurtiswx> or can i not?
[17:43] <yofel> bcurtiswx: afaik only devs can do it, you can nominate it for lucid though
[17:44] <bcurtiswx> yofel, OK, i wasn't sure. thx
[17:50] <hggdh> yofel: you can nominate, but only the maintainers can accept/reject
[17:51] <bcurtiswx> vish: bugs in which you ask if people have forwarded upstream yet, you mark as new. why not incomplete?
[17:52] <vish> bcurtiswx: we decided that long time ago to *not* mark bugs incomplete for those , the bug is not incomplete , we are doing an incomplete job there ;)
[17:53] <bcurtiswx> wow, where was i for this discussion.  I think its quite contrary
[17:54] <bcurtiswx> a completel bug will be a triaged one, a new bug is one that hasn't been touched by a triager yet... thats my opinion
[17:54] <bcurtiswx> so if its not complete and not new, it should be incomplete
[17:55] <vish> bcurtiswx: no , these would be in confirm.. but some of the bugs , there hasnt been a second person to "confirm"
[17:55] <vish> its one of those needs-forwarding bugs , but empathy triage seems to follow its own rules
[17:55] <bcurtiswx> vish ?
[17:55] <bcurtiswx> own rules?
[17:55] <vish> :)
[17:56] <charlie-tca> I thought we were marking those confirmed
[17:56] <vish> charlie-tca: yes, if we can confirm them.. but these were marked incomplete
[17:57] <charlie-tca> If they can't be confirmed, why would we want to have them sent upstream?
[17:57] <bcurtiswx> if they needs-forwarding, doesn't that make it incomplete?
[17:57] <vish> charlie-tca: they reporter keeps saying that he has the bug and has answered all the questions
[17:57] <vish> the*
[17:57] <charlie-tca> Oh
[17:57] <charlie-tca> I see
[17:58] <charlie-tca> I have some like that, myself
[17:58] <bcurtiswx> i don't want to be inconsistent with general triage, but if a bug needs to be forwarded upstream, how is it closer to "new" than it is "incomplete" ?
[17:59] <bcurtiswx> if not confirmed
[17:59] <charlie-tca> A bug that is not confirmed is normally kept at new until it can be?
[17:59] <vish> bcurtiswx: incomplete is for a bug, when the user has to reply to a question
[18:00] <charlie-tca> The The fact that it can be sent upstream by the original reporter does not change the fact that it is not confirmed by more than one person
[18:00] <bcurtiswx> vish, OK, in the default reply to ask someone with the bug to forward uptream waiting for the user to "reply" to that question
[18:00] <charlie-tca> so, yes, new is correct
[18:01] <bcurtiswx> hmm, maybe my main argument is that if we request it to be sent upstream, we have in essence asked the reporter to perform an action and are waiting for that reply that its done..
[18:01] <bcurtiswx> not saying a triager can't do it...
[18:02] <vish> bcurtiswx: lets take a personal example.. i'v had bugs i could reproduce but , no one else was able to reproduce [yet] , but i collected the info the bug needed and forwarded it upstream, and later sometimes bugs get confirmed or not ..
[18:02] <vish> but the bug was valid and had to be looked into by upstream
[18:02] <charlie-tca> yes, if upstream can confirm it, we can move the status to confirmed also
[18:03] <bcurtiswx> so maybe i
[18:03] <bcurtiswx> hmm, premature enter hitting
[18:03] <bcurtiswx> sry
[18:03] <bcurtiswx> if its reported upstream, then it's typically marked as triaged
[18:04] <charlie-tca> yews
[18:04] <charlie-tca> yes
[18:04] <vish> yup
[18:04] <bcurtiswx> so upon waiting for someone to send it upstream, how is this differ from my previous statements that it needs to me incomplete while we wait for the bug to be reported upstream
[18:05] <bcurtiswx> be*
[18:05] <charlie-tca> but if the reporter has gathered all the data, he can push the bug upstream, and then he will also followup with upstream questions. If we push it based on a single reporter, they won't always follow the upstream report
[18:05] <vish> bcurtiswx: as a triager for a package all i need to know i what info upstream would ask for..
[18:05] <charlie-tca> We can not confirm it, why is it incomplete?
[18:05] <vish> bcurtiswx: if there is anything less, then we can always ask again :)
[18:06] <charlie-tca> incomplete could expire waiting for someone to confirm the bug. New bugs normally won't expire waiting for confirmation
[18:06] <bcurtiswx> hmm, maybe i'm asking the wrong question here.  let me rephrase
[18:07] <vish> bcurtiswx: the bugs i went through and was pretty disappointed at the way they were triaged.. several of the bugs marked incomplete were answered a long time ago...
[18:07] <charlie-tca> If someone else eventually confirms the issue, we as triagers can send it upstream
[18:07] <bcurtiswx> vish, who's issue is that?
[18:07] <vish> bcurtiswx: not you :)
[18:08] <vish> yours*
[18:09] <bcurtiswx> we have all upstream info, even if its not confirmed, so we need to get it sent upstream (assuming we have no time right now to do it ourselves) we ask in the bug for someone having the issue to forward it.
[18:09] <vish> bcurtiswx: also, none of my remarks of empathy triage were directed at you :)
[18:09] <bcurtiswx> at that point , im saying i see it being marked as new,... which i believe should be incomplete because we are waiting for a response to our question
[18:10] <charlie-tca> personally, if the bug can not be confirmed, I would prefer the reporter upstream it so the reporter follows up if needed
[18:10] <vish> charlie-tca: +1
[18:10] <charlie-tca> but I also do want the bug to expire in incomplete status
[18:11] <bcurtiswx> im just asking about why it's been set at new, and not incomplete as we wait for it to be sent upstream
[18:11] <charlie-tca> Which it will expire in 60 days if left in incomplete
[18:11] <vish> bcurtiswx: what was decide was to just leave those bugs as new.. since incomplete means that the reporter has to reply to some question we have asked..
[18:11] <vish> and the expiry issue
[18:11] <bcurtiswx> we are asking them to report it upstream
[18:12] <vish> bcurtiswx: forwarding the bug is not the reporters work, we need to do that :)
[18:12] <vish> that is actually what i meant by, 'incomplete for us'...
[18:12] <vish> err, incomplete job by us
[18:13] <bcurtiswx> 'eh, i guess I can't explain myself in the right way.  I have other things to do ATM.  I'll give it a go later probably.  sorry for the confusion
[18:16]  * charlie-tca finds it extremely confusing trying to keep up with things
[18:30] <ashams> simar:
[18:30] <ashams> simar: hi
[18:32] <simar> ashams: hey
[18:32] <simar> ashams: whats up
[18:32] <ashams> simar: fine, my good Mentor :)
[18:33] <simar> ashams: :))
[18:33] <ashams> simar: when would be your weekend?
[18:33] <ashams> simar: friday?
[18:33] <simar> ashams: right from sat to sun .. ;-))
[18:33] <ashams> simar: very nice,
[18:34] <simar> ashams: but i will be avaliable on friday
[18:34] <simar> ashams: how is you triaging going on?
[18:34] <simar> ashams: let me check
[18:34] <ashams> simar: would you like to spend more time mentoring me in these days?
[18:34] <simar> ashams: ofcourse ..
[18:35] <simar> ashams: ah!! good increase in karma value .
[18:35] <ashams> simar: thank you
[18:36] <simar> ashams: you are welcome to ask anything..
[18:36] <ashams> simar: well, I've to tell you that I'm a muslim, and this month is the one of Fasting and praying, that's only why I'm always busy...
[18:37] <simar> ashams: good you should pray to god before everything and above everything .. there is no problem, whenever you are free try to triage..
[18:42] <simar> ashams: let me tell you that you can also consider triaging some other package if you like doing so..
[18:42] <simar> ashams: or if you are not very comfortable with your present package
[18:49] <ashams> simar: no, it's fine
[18:49] <ashams> simar: I'm asking for some time before 16 UTC
[18:50] <simar> ashams: just tell me when to be online tomorrow?
[18:50] <ashams> 14 UTC ok?
[18:51] <ashams> simar: 14 UTC ok?
[18:51] <simar> ashams: fare enough ..
[18:52] <simar> ashams: be online and wait only for 14:30 and i will come hopefully
[18:52] <ashams> simar: Thank you very much, got to go!, sorry....
[18:52] <ashams> simar: OK
[18:52] <simar> ashams: c ya tomorrow
[18:52] <ashams> simar: :)
[19:18] <vish> bcurtiswx: werent the protocol icons removed from contact list? i vaguely remember you blogging a mockup..
[19:41] <bcurtiswx> vish, no they weren't.  You have to enable showing protocol icons
[19:41] <bcurtiswx> vish, if they are talking about contact merges, protocol icons aren't shown
[19:42] <vish> bcurtiswx: oh ok.. was about Bug #546881 btw, someone marked it fix-committed ;p
[19:42] <ubot2> Launchpad bug 546881 in empathy (Ubuntu) "protocol icons (particularly Facebook) obscure status icon too much (affects: 2) (heat: 12)" [Low,Fix committed] https://launchpad.net/bugs/546881
[19:44] <bcurtiswx> vish, <3 people trying to use launchpad without understanding it.. they should send it upstream and let cassidy decide if he wants to do that.  Right now it would represent a UI change, and wont make it into 2.32, though.
[19:44] <vish> yup..
[19:48] <El_Presidente> crimsun_, can you please take a look here https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/572146 again i think i found the bug http://yfrog.com/n2bildschirmfotovp
[19:48] <ubot2> Launchpad bug 572146 in alsa-driver (Ubuntu) "crackling sound from microphone with 2.6.32-21 kernel (affects: 4) (heat: 44)" [Undecided,Incomplete]
[19:54] <micahg> charlie-tca: how's the stability of xfce beta?
[19:54] <micahg> s/xfce/xubuntu/
[19:54] <charlie-tca> Looks good to me
[19:54] <charlie-tca> A few bugs, of course
[19:55] <micahg> charlie-tca: any of the menuproxy/appmenu issues that GNOME has?
[19:55] <charlie-tca> Don't think so
[19:56] <micahg> charlie-tca: cool, I guess I'm clear to upgrade this weekend then :)
[19:56] <charlie-tca> should be. I am still trying to test upgrades, my connection is a lot slow
[19:57] <micahg> charlie-tca: I can handle a few bugs, just not total breakage
[19:58] <charlie-tca> heh
[19:58] <charlie-tca> I been using it since right before alpha3, I think
[19:59] <micahg> I usually wait for beta so all the system wide changes land
[20:17] <simar__mohaar> simar: hello
[20:19] <simar> sima
[20:59] <simar> H
[21:06] <simar> simar h
[22:04] <simar> sima
[22:24] <dyfet> I believe bug #623330 can be marked as triaged.  At least what needs to be done has been identified.
[22:24] <ubot2> Launchpad bug 623330 in unison (Ubuntu) "Unison gui-language is english (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/623330
[22:31] <devildante> dyfet: you should report the bug upstream
[22:32] <dyfet> I would be happy to
[22:32] <dyfet> I wanted to make sure we identified what needs to be done first :)
[22:43] <devildante> dyfet, I meant you must report the bug upstream if you want it to be triaged
[23:53] <crimsun_> El_Presidente: well, reverting that commit breaks the original reporter's
[23:53] <crimsun_> El_Presidente: so, there is no good way to go about this.
[23:53] <crimsun_> El_Presidente: just use position_fix=0
[23:56] <crimsun_> El_Presidente: I've retitled the bug report and noted the workaround