[03:19] <munson> anyone else have 11.04 and no sound for the "Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)" and a fix?
[04:11] <munson> or maybe should i just downgrade
[05:21] <munson> hmm
[11:52] <htpcuser_> hi all, got a problem with mythbuntu 10.10 combined fe/be and getting the system to wake from suspend via the mce remote. Anyone's area of expertise?
[12:53] <neil_> what is the chances of a USB Digital TV receiver like this one http://www.ebay.com.au/itm/USB-HDTV-TV-tuner-DVB-T-4-Laptop-PC-Record-digital-TV-/120667853872?pt=AU_Laptop_Accessories&hash=item1c185d5430 working with mythbuntu?
[12:53] <Zinn> [www.ebay.com.au] USB HDTV TV tuner DVB-T 4 Laptop & PC Record digital TV | eBay
[12:54] <munson> anyone else have 11.04 and "no sound" for the "Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 01)" and a fix?
[13:54] <Guinness2702> Hey guys.  I think maybe I might have found a problem in the mythbuntu-repos package (not really sure exactly)
[13:55] <Guinness2702> Basically, I installed it, then upgraded mythtv-backend - not everything was upgraded, and I had problems (mainly the mythtv hourly cron job failed)
[13:55] <superm1> what wasn't upgraded?
[13:55] <Guinness2702> Anybody here interested in more info, to see if it's a problem
[13:55] <superm1> and why wasn't the rest upgraded?
[13:56] <Guinness2702> libmyth-python, libmyth-perl, myth-tv-database and mythweb
[13:56] <superm1> and you did apt-get dist-upgrade?
[13:56] <superm1> or you used update-manager?
[13:57] <Guinness2702> http://pastebin.com/Gpwr9EdN
[13:57] <Zinn> [pastebin.com] root@central:/etc# dpkg -l | grep myth rc libmyth-0.23-0 0.2 - Pastebin.com
[13:57] <Guinness2702> superm1,  I didn't do a dist-upgrade, no
[13:57] <Guinness2702> I don't want to upgrade my entire distro
[13:57] <superm1> dist-upgrade doesn't upgrade the distro
[13:57] <Guinness2702> I just needed to upgrade mythtv
[13:57] <superm1> it forces upgrades that can't be done without removing packages
[13:57] <superm1> upgrading the distro is done via 'do-release-upgrade'
[13:57] <superm1> or with update-manager -d
[13:58] <superm1> if you run update-manager it will offer a  partial upgrade and fix this scenario
[13:58] <superm1> or apt-get dist-upgrade will
[13:58] <Guinness2702> I used apt-get
[13:58] <superm1> in either situation it's expected behavior
[13:58] <Guinness2702> apt-get install mythtv-backend  IIRC
[13:59] <Guinness2702> really?  I'd expect that to upgrade all required deps, rather than leaving it in an unstable state
[13:59] <superm1> apt-get won't remove packages in the normal 'apt-get upgrade' scenario
[13:59] <superm1> aptitude will, update-manager will (in partial upgrade mode) and apt-get dist-upgrade will
[14:00] <superm1> there's a reason we specifically mention update-manager in http://mythbuntu.org/auto-builds :)
[14:00] <Zinn> [mythbuntu.org] Mythbuntu Repositories | Mythbuntu
[14:00] <Guinness2702> update-manager - that the ubuntu GUI update manager right?
[14:00] <superm1> yeah
[14:00] <Guinness2702> I wouldn't run that - my backend is headless
[14:01] <superm1> if you don't want to use it, that's fine, just apt-get dist-upgrade and you'll be back in working order
[14:01] <Guinness2702> superm1, - I already fixed it by doing individual packages :)
[14:01] <Guinness2702> but I would need to do "apt-get dist-upgrade mythtv-backend" right?
[14:02] <superm1> just apt-get dist-upgrade
[14:02] <Guinness2702> are you sure that won't upgrade anything else?
[14:02] <superm1> positive
[14:02] <superm1> well other stuff within the given "os release"
[14:02] <superm1> but it wont jump release to release
[14:03] <superm1> if there was updates published for other things they'll be included in that too
[14:04] <Guinness2702> I'm wary of doing such things.  I could do without my server being down, and big upgrades always risk that
[14:04] <Guinness2702> but what the fuck, I've got time today I guess
[14:04] <Zinn> Guinness2702: Please watch your language.
[14:05]  * Guinness2702 apologises to the bot
[14:05] <superm1> well you can always do them one at a time too, it's just a convenience thing
[14:05] <superm1> some people prefer to go and dig into changelogs et'al
[14:06] <Guinness2702> Anyway, if it really is just I/O error, then fine - just wondered if you guys wanted to know about it - if it's not a problem, then it's not :)
[14:07] <superm1> maybe it could have been lessened with a more proper package transition.  i think that's how a lot of debian and ubuntu do it, but because we support the same packaged for lucid, maverick, natty, and oneiric (well except for minor build tweaks), that's a lot more difficult to get right
[14:09] <Guinness2702> The real problem was that I used different distros on different machines, which came with incompatible versions of myth, so I had to force an older distro to use a newer myth
[14:11] <superm1> going forward your best bet is to use LTS on all boxes
[14:11] <superm1> that's what we'll be releasing ISOs for
[14:11] <superm1> and keeping builds up to date all the time for
[14:11] <superm1> you can do in-between releases if you want, but we're only supporting up to to mythtv releases on them
[14:11] <superm1> eg natty will only ever support 0.24 and 0.25
[14:12] <superm1> but if 0.23, 0.24, 0.25 and 0.26 all come out before oneiric+1 (next LTS), then they'll all be on lucid
[14:12] <Guinness2702> I use LTS for my server, but I always keep my desktops on the latest version
[14:12] <Guinness2702> Not normally a problem, but this strategy broke myth
[14:12] <Guinness2702> :(
[14:17] <Guinness2702> Anyways, boi boi