[00:13] <hggdh> madam_: probably a good idea is to boot from a recovery disk/usb stick, mount your root, and disable timidity from starting up.
[01:55] <ds-labs_> Hi
[01:55] <ds-labs_> Just a quick question, any news on the laptop overheat bug with ubuntu 12.10?
[02:12] <madam_> Did an update of 12.10 security patches and fixes... refuses to reboot. Hangs at the "starting timidity++ Alsa midi emulation" part.----Recovery menu: (file system state: read only) - so how do I get around the hang?----- Can I edit out the problem code and just bypass it?
[02:12] <madam_> ------If so how?----Any ideas on the subject?
[08:04] <aaaaaaaaaa> dcfvjgbhkjkll
[15:20] <ronswift> How can I help the BugSquad today
[15:28] <bdmurray> https://wiki.ubuntu.com/UbuntuBugDay/Ubuntu-release-upgrader-20130321
[15:28] <bdmurray> that page has some information on how you can help
[19:39] <nottheoilrig> how do i mark bug #1013798 as forwarded upstream to dan@ag-projects.com?
[19:39] <ubot2> Launchpad bug 1013798 in libgcrypt11 (Ubuntu Raring) "Blink SIP client segfaults with libgcrypt11 1.5.0-3ubuntu0.1" [Critical,In progress] https://launchpad.net/bugs/1013798
[19:56] <aaaaaaaaaa> aaaaaaaaaa
[19:57] <TheLordOfTime> nottheoilrig, is there an upstream bugtracker?
[19:59] <nottheoilrig> TheLordOfTime: no, i checked the pypi site, the ag projects site, and the docs in the source repository
[20:00] <TheLordOfTime> is dan AT ag-projects DOT com on the upstream dev team of libgcrypt11
[20:00] <nottheoilrig> i didn't find an upstream bug tracker
[20:01] <nottheoilrig> TheLordOfTime: he made the most recent commits in the source repository
[21:33] <nottheoilrig> what is the correct way to reassign bug #1013798 to the python-gnutls package?
[21:33] <ubot2> Launchpad bug 1013798 in libgcrypt11 (Ubuntu Raring) "Blink SIP client segfaults with libgcrypt11 1.5.0-3ubuntu0.1" [Critical,In progress] https://launchpad.net/bugs/1013798
[21:38] <bdmurray> click also affects distribution and add a new task for that package
[21:39] <bdmurray> I'd wouldn't just reassign that one since it has a long history
[21:39] <bdmurray> nottheoilrig: ^
[21:44] <nottheoilrig> bdmurray: thx
[22:21] <bdmurray> hggdh: are you about?
[22:52] <hggdh> bdmurray: now I am
[22:52] <bdmurray> hggdh: could you maybe try verifying bug 1094777 - I'm going a bit bonkers
[22:52] <ubot2> Launchpad bug 1094777 in ubuntu-release-upgrader (Ubuntu Quantal) "Can't use c-n-r-gtk to initiate Quantal -> Raring update" [Undecided,Fix committed] https://launchpad.net/bugs/1094777
[22:54] <hggdh> bdmurray: yeah. It will take a while, since I will have to build a new quantal VM
[22:55] <bdmurray> hggdh: okay, I'm trying again and will let you know if I get it sorted
[22:56] <hggdh> bdmurray: OK
[23:45] <hggdh> bdmurray: OK, on  pristine install, I get "timeout reached" when running check-new-release-gtk. Dist-upgrading with -proposed now
[23:46] <bdmurray> hggdh: So it works?
[23:47] <hggdh> bdmurray: no, it does not -- it timeouts somewhere (no bkactrace)
[23:47] <hggdh> I do no teven get the panel asking if I want to upgrade
[23:47] <bdmurray> hunh, mine started on a new system
[23:48] <hggdh> bdmurray: cosmic rays...
[23:51] <hggdh> this is weird. After enabling -proposed, a update && dist-upgrade got *nothing* to upgrade
[23:51] <bdmurray> check your sources.list for raring instead of quantal
[23:52] <hggdh> bah, got it -- finger check, I added quantal-proposed for deb-src :-(
[23:52] <hggdh> but not for dev
[23:53] <hggdh> deb even