[13:28] <iceroot> is there a way to put comments on launchpad with mail? background is, there is an exisitng bug in launchpad and i need to open same thing to LKML and dont want to post it twice also the feedback from LKML would go directly into launchpad
[13:28] <iceroot> also but others ways to i have to "link" the launchpad-bug to the LKML discussion without just a comment with a link?
[13:34] <pleia2> iceroot: https://help.launchpad.net/Bugs/EmailInterface
[13:34] <pleia2> you need to use gpg
[13:35] <iceroot> pleia2: great, pgp already setup and linked with launchpad
[13:36] <iceroot> pleia2: but the answer from LKML will not get there until they have a gpg on launchpad
[15:09] <puff> Hi. I'm not sure if this is an inappropriate question, but... I have a thinkpad t520 running 10.4 LTS and I'd like to upgrade to a more recent release.  In the past I've been bitten by significant bugs on each release upgrade, so I'm trying to check into it before upgrading.
[15:09] <puff> I searched on launchpad, that shows me only 5 bugs:
[15:09] <puff> https://launchpad.net/ubuntu/+bugs?field.searchtext=t520&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_package=
[15:26] <jibel> bdmurray, could something be done at update-manager level to prevent people reporting bugs like bug 885992 ?
[15:26] <Guest29594> Launchpad bug 885992 in update-manager (Ubuntu) "update manager crashes when starting (affects: 1) (heat: 8)" [Undecided,Invalid] https://launchpad.net/bugs/885992
[15:27] <hggdh> puff: (caveat -- I have not looked at your link, too big and got broken here) first of all, the upgrade path would be 10.04 -> 10.10 -> 11.04 -> 11.10
[15:28] <hggdh> (when we release 12.04, you can do 10.04 -> 12.04 straight)
[15:32] <puff> hggdh: Yeah, I'm waffling between just upgrading to 10.10 (not sure if that would solve enough of my problems) versus reinstalling my / partition to 11.04 or 11.10.
[15:54] <puff> I'm leaning strongly towards installing a dual boot of 11.10 alongside 10.4 LTS, so I can quickly switch back to 10.4 if I have problems.
[15:55] <Angelo> Hi! :-)
[15:56] <Angelo> What should I do to help?
[15:57] <puff> thanks for the help folks!
[15:57] <micahg> title of channel still says we're having a bug day from a week ago
[18:02] <njin> hello, can someone wishlist bug 700126 for me, thanks
[18:02] <Guest29594> Launchpad bug 700126 in system-config-printer (Ubuntu) "non-primary users not added to acl list for scanner/printer (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/700126
[18:48] <elgaton> Hi, I'm triaging bug #882255 (if an empty password is set, Sudo incorrectly prompts for it, so operations requiring administrative privileges are not possible). Which package should I target (sudo, pam...)? I'm asking this also because empty passwords are a security risk and the user, when changing password, should be warned of that (or empty passwords should be not allowed, although this choice is a bit limitative, for example for system accounts).
[18:48] <Guest29594> Launchpad bug 882255 in ubuntu "No root access after setting password to 'None' (affects: 2) (heat: 12)" [Undecided,Confirmed] https://launchpad.net/bugs/882255
[18:52] <hggdh> and?
[18:53] <hggdh> sorry, wrong channel
[19:14] <hggdh> elgaton: which password was set to none, and how was it done?
[19:14] <hggdh> ?
[19:15] <elgaton> hggdh: The password of the main user account was set to an empty one (I think during installation or using the User Account management utilities, haven't asked yet).
[19:16] <hggdh> ok, so not the root password (which is set to empty by default)
[19:16] <elgaton> hggdh: OK
[19:24] <hggdh> elgaton: IIRC, one has to change LightDM's to ask for a password
[19:24] <hggdh> elgaton: let me check
[19:24] <elgaton> hggdh: Thanks
[19:27] <hggdh> darn
[19:27] <elgaton> hggdh: What happened?
[19:27] <hggdh> elgaton: I know I saw it the other day, but cannot remember where.
[19:28] <hggdh> elgaton: you will problably get people that know more of desktop on the #ubuntu-desktop channel
[19:28] <elgaton> hggdh: OK, I'll ask there. Thanks for your work
[19:30] <elgaton> hggdh: It just came to my mind that it is also possible to change user password using the "passwd" command, so a fix in the GUI part is not enough.
[19:31] <elgaton> hggdh: Maybe PAM (used by Sudo as well) could be a possible choice?
[19:33] <hggdh> elgaton: it could, but it all depends on what was actually done (i.e., how the OP changed the password, how the system was setup, etc. There may indeed be a bug -- or more -- lurking in there.
[19:34] <elgaton> hggdh: OK, I'll setup a test VM and try changing in every possible way (passwd and GUI) and see if I can reproduce the bug, but I think the problem is at the Sudo/PAM level.
[19:35] <hggdh> elgaton: it could indeed. But we must understand what was actually done -- command sequence, etc -- so that it would be easier to reproduce, instead of running thru a potentially large number of permutations
[19:46] <elgaton> hggdh: OK, I'll test thoroughly
[19:47] <elgaton> Thanks again