[14:11] <lsolesen> How do I change what happens when sending shutdown to ubuntu. I need to make sure that mythshutdown --safeshutdown is used.
[16:30] <tgm4883> lsolesen, I don't think you can change that
[18:42] <lsolesen> tgm4883: you are probably right. what i want is also more the obvious power down buttons to use mythshutdown, e.g. the unity shutdown and xbmc shutdown and mythshutdown.
[18:43] <yunosh> hi, is this only me, or has automatic jamu updating been broken in fixes? /etc/cron.hourly/mythtv-backend still points to /usr/share/doc/mythtv-backend/contrib/metadata/jamu.py but jamu is in /usr/share/mythtv/mythvideo/scripts/jamu.py now
[19:30] <tgm4883> yunosh, what version of mythtv are you using (full version please)
[19:31] <yunosh> tgm4883: 0.24.1+fixes.20110617.5aa5e48-0ubuntu0mythbuntu1
[19:33] <tgm4883> yunosh, what pacakge does it say that /etc/cron.hourly/mythtv-backend is in?
[19:33] <yunosh> mythv-backend
[19:33] <tgm4883> (probably says mythtv-backend, I just want to be sure)
[19:33] <tgm4883> OK
[19:34] <tgm4883> yunosh, do you have a /etc/cron.hourly/mythvideo?
[19:34] <yunosh> yes. oh, and it has the correct path indeed
[19:35] <tgm4883> ok sec
[19:36] <tgm4883> yunosh, ok go ahead and delete /etc/cron.hourly/mythtv-backend
[19:36] <tgm4883> it was left over from an old build that had an issue
[19:36] <yunosh> k
[19:37] <tgm4883> yunosh, actually
[19:37] <tgm4883> have you removed it yet?
[19:37] <yunosh> yes :) but i have another copy of it, from mythtv-frontend ;)
[19:38] <yunosh> though that points to the correct location
[19:38] <yunosh> still a duplicate though
[19:39] <tgm4883> yunosh, that was a bug that was fixed recently, but I can't find the bug report so I'm unsure exactly when it was fixed
[19:39] <tgm4883> It might have been after the 17th
[19:40] <yunosh> doesn't look like it
[19:40] <yunosh> at least not in -fixes
[19:40] <tgm4883> well it was an issue with our builds
[19:41] <tgm4883> wouldn't show up in the changlog
[19:41] <tgm4883> found it https://bugs.launchpad.net/mythbuntu/+bug/797668
[19:41] <yunosh> ah okay
[19:41] <Zinn> [bugs.launchpad.net] Bug #797668 in Mythbuntu: “mythtv-frontend cron scripts call jamu, which is in a different package”
[19:41] <tgm4883> It actually might not be fixed yet, might be pending right now
[19:41] <yunosh> thanks
[19:42] <tgm4883> yw
[21:36] <qwebirc60750> I've got Mythtv working after a fashion - but it works poorly as compared to myy 6 year old set-top dvb box  when plugged into the same ariel - is there anyway I can probe my hardware to find out how to optimise the performance of my tuner?
[21:43] <qwebirc60750> using the lspci  -v command I can see most of my hardware, but there is nothing that I can immediately pick out as my digital tuner
[22:06] <tgm4883> qwebirc60750, what tuner do you have?
[22:06] <tgm4883> qwebirc60750, what version of mythtv are you running? What version of Mythbuntu?
[22:14] <qwebirc60750> it's a Peak DVT-Dual tuner PCI (221544AGPK)
[22:14] <qwebirc60750> on the 2.4.1 mythbuntu release
[22:15] <qwebirc60750> sorry 2.4.1 mythtv
[22:16] <qwebirc60750> 11.04 version of mythbuntu
[22:17] <qwebirc60750> the Tuner is listed under DVB-T PC160-2T at linuxtv.org
[22:19] <gregL> qwebirc60750, The rule of thumb is if a tuner works in Linux,It will usually work for Mythtv..
[22:22] <qwebirc60750> it's working in mythtv, but not picking up all the channels I should be able to pick up
[22:23] <qwebirc60750> and some seem to be really poor signal - what I don't understand is why the hardware  performs so badly as compared to my old set-top box
[22:24] <qwebirc60750> it's attached to the same antenna
[22:41] <qwebirc60750> is there a possibility that I just have the incorrect configuration - if so how do I find the correct settings?
=== Gibby_ is now known as Gibby