[02:04] <iceroot> hi, what is the ressource to open bugs against ubuntu.com?
[02:12] <dlentz> iceroot, https://bugs.launchpad.net/ubuntu-website-content/+filebug
[02:13] <iceroot> dlentz: thanky ou
[02:13] <iceroot> y
[02:13] <dlentz> yw
[08:19] <rbasak> How should backports bugs be triaged? I can documentation neither in https://wiki.ubuntu.com/UbuntuBackports nor https://wiki.ubuntu.com/Bugs/HowToTriage. This is bug 986649.
[08:19] <ubot2> Launchpad bug 986649 in puppet "puppet agent can't obtain catalogs" [Undecided,New] https://launchpad.net/bugs/986649
[08:21] <rbasak> And maverick is EOL anyway. Is this a Won't Fix due to that?
[08:23] <micahg> rbasak: well, if there's a bug, you can add a task for the respective $RELEASE-backports project, the main thing would be determining if the source of the backport is also affected in which case you'd leave the distro task open
[08:24] <micahg> or target to whichever series is affected if appropriate
[08:24] <micahg> yeah, maverick bugs are EOL, but that same backported version is in natty and oneiric
[08:24] <micahg> and lucid as well
[08:24] <rbasak> micahg: OK I'll do that - thanks!
[08:29] <micahg> rbasak: adding a task to maverick-backports at this point is useless (I hope I didn't imply that should be done)
[08:29]  * micahg removes
[08:29] <rbasak> Oh OK, I misunderstood
[08:30] <micahg> supported releases are fine to do that :)
[08:30] <micahg> the question is does it affect the other releases or not
[08:31] <rbasak> micahg: I was going to ask the reporter. Shall I go ahead and do that?
[08:31] <micahg> yeah, you can do that with a note about EOL for Maverick, would probably be good if someone could test this on oneiric
[16:55] <njin> ubuntu-wubi
[18:25] <alex_mayorga> Is there a way to recover a bug report that never managed to show a Launchpad window?
[21:41] <dcampoy> Hi. I just update my ubuntu to 12.04 and now I'm unable to make it boot again. I'm here to find a workaround to let me work again
[21:42] <dcampoy> At first time I get: "Failed to create PTY"-error that is already reported and has as workaround add --no-log as kernel parameter
[21:43] <dcampoy> but the boot still keep failing but without any error now.
[21:44] <dcampoy> Has anybody a clue?
[21:46] <rbasak> dcampoy: I think you want #ubuntu+1 for 12.04 support.
[21:46] <rbasak> (sorry I don't know the answer)
[21:47] <dcampoy> @rbasak thanks. Let's try :)
[21:47] <meetingology> dcampoy: Error: "rbasak" is not a valid command.
[22:09] <txomon|home> can someone have a look in bug 975197
[22:10] <ubot2> Launchpad bug 975197 in linux "Can't avoid mounting in boot time" [Medium,New] https://launchpad.net/bugs/975197
[22:10] <txomon|home> it is a very blocking feature, that can't be changed but booting from CD and modifying the fstab file
[22:24] <bdmurray> Setting up memtest86+ (4.20-1.1ubuntu1) ...^M
[22:24] <bdmurray> /usr/sbin/grub-mkconfig: 1: /etc/default/grub: splash”#: not found^M
[22:24] <bdmurray> dpkg: error processing memtest86+ (--configure):^M subprocess installed post-installation script returned error exit status 127^M
[22:29] <txomon|home> ?
[22:49] <bdmurray> misclick
[22:49] <txomon|home> ah oki