[00:00] <quent56> if I put the command "touch ~/OK", OK is never created.
[00:03] <nudelsnack> I don't know much about that but as far as i remember the backend is not necessarily shut down when the frontend ends
[00:05] <nudelsnack> so it seems to me like your problem is that the backend is not shut down rather than the command not being run during shutdown
[00:05] <quent56> yes I think
[00:05] <baggar11> quent56: yes, backend will keep runnin until you shutdown the computer. That command is for specific instructions for mythtv-backend to stop itself before system shutdown.
[00:06] <quent56> There are a field : "The amount of time the master backend idles before it shuts down all backends. Set to 0 to disable auto shut down", I put 35 (seconds) here.
[00:07] <quent56> And I see in mythwelcome that the backend is idle
[00:07] <quent56> for 1 minutes (or more)
[00:09] <quent56> I have a PC with front end and backend installed, and I would like to shutdown the PC when there are no frontend and no record active
[00:10] <baggar11> quent56: I haven't set anything like that up. I keep my backend on all the time. only turn on/off the frontends as needed.
[00:11] <quent56> ok we are not in the same case
[00:11] <quent56> I would like to shutdown my pc, for electrical issue
[00:11] <nudelsnack> I only would like to set up a complete system shutdown by remote
[00:12] <quent56> nudelsnack> do you use lirc ?
[00:12] <nudelsnack> no, I have a MCE remote
[00:12] <baggar11> quent56: you can modify the frontends option so it will prompt you to shutdown the computer, when trying to close the frontend
[00:12] <quent56> baggar11> ok :) how can I do this ?
[00:13] <baggar11> quent56: it's an option under general I believe. I'm not at a frontend to tell you.
[00:13] <quent56> baggar11> ok I loof for, thanks
[00:13] <nudelsnack> by the way, what is logged to the mythwelcome.log? Mine is empty...
[00:13] <quent56> *look
[00:15] <quent56> nudelsnack> start mythwelcome like this : mythwelcome -l /var/log/mythtv/mythwelcome.log
[00:18] <nudelsnack> good to know about the tool :)
[00:18] <baggar11> quent56: found a forum post that said the mythfrontend exit options were in general
[00:19] <quent56> baggar11: yes, an option is here
[00:19] <baggar11> quent56: cool
[00:20] <quent56> baggar11> it's work partially, it's reboot or halt as demand, but I don't control it I think, I would like use it with mythwelcom
[00:21] <quent56> I would like boot up my PC when a record is shedule, and halt him after, so the front end is not launch and it's match backend options
[00:21] <quent56> as describe here : http://www.mythtv.org/wiki/ACPI_Wakeup
[00:21] <Zinn> [www.mythtv.org] ACPI Wakeup - MythTV
[00:25] <nudelsnack> quent56: did you set a wakeup event after the shutdown? there is a hint in the mythwelcome wiki page about at least 15mins
[00:25] <nudelsnack> otherwise the system won't shut down
[00:27] <quent56> I see it, and it's match to option "Max. wait for recording (min)          : 15", but I have no record shedule, and I have no wakeup event after shutdown
[01:21] <quent56> good night  and thank you for your help
[14:18] <patdk-wk> Hmm, I'm wondering if I did the mythbuntu ppa wrong or not
[14:18] <patdk-wk> I was attempting to track 0.24
[14:19] <patdk-wk> I have /repros/, /0.24/ and /testing/
[14:19] <patdk-wk> should I just have repos and 0.24?
[16:01] <tgm4883> patdk-wk, no, you are fine
[16:01] <tgm4883> that will give you 0.24 updates
[16:02] <patdk-wk> hmm, ok :)
[16:02] <patdk-wk> had testing in there, didn't know why
[16:02] <patdk-wk> so never-record in mythweb is broken, and doesn't look like mythwebs fault :(
[16:02] <tgm4883> cause you enabled mythbuntu updates
[16:03] <patdk-wk> it updates the database ok, it doesn't seem to do a reschedule though, but if I do one manually, it still is set to record :(
[16:03] <patdk-wk> I was just updating to make sure it wasn't already fixed
[16:03] <tgm4883> sounds like a mythtv bug
[16:03] <patdk-wk> ya, not reading the oldrecordings table right or something
[16:04] <mrand> I think I remember seeing a bug report, or at least a discussion on that, a few weeks back.
[16:04] <mrand> Or I could just be imaging it.
[16:04] <patdk-wk> my google search wasn't finding anything
[16:09] <mrand> Ok, I was actually thinking of Bug 9360 (http://code.mythtv.org/trac/ticket/9360), but that's for re-record.  Never record was last "fixed" here: http://code.mythtv.org/trac/ticket/8487 which should be included in 0.24
[16:10] <Zinn> Bug 9360 in linux-source-2.6.15 (Ubuntu) "Current acx100 module shows incorrect signal strength" [Medium, Invalid] http://www.launchpad.net/bugs/9360
[16:10] <mrand> ignore zinn
[16:10] <Zinn> Hi mrand, something I can help you with today?  I am a bot, use !help to see what I can do.
[16:10] <mrand> I know you're a bot, and no, you are not being helpful.
[16:14] <patdk-wk> hehe
[16:14] <patdk-wk> ya, I saw that bug, different issue
[16:14] <patdk-wk> it gets the program id's correct
[16:14] <mrand> patdk-wk: in that case, could you open a mythtv ticket on it?
[16:15] <patdk-wk> I'll try, probably later tonight, should do some work, while at work :)
[16:16] <patdk-wk> I had a marathon that was recording on the 1st, like 20 shows back to back, none of them would never-record :)
[16:16] <patdk-wk> clicking, dont-record worked though
[16:16] <mrand> that could get annoying ;-)
[16:16] <mrand> thanks.
[16:16] <patdk-wk> and I debugged the mythweb php code already, it's not the issue
[16:16] <patdk-wk> ya, I'll crossreference the database, make sure it is good, then file the bug
[16:17] <mrand> excellent.  They'll be happy to hear that it isn't php... those bugs tend to lay around a while I think.
[16:17] <patdk-wk> oh, if it was a php bug, I would submit a patch
[16:18] <patdk-wk> I would do it for the c code also, but well, I could probably spend a week or longer looking for the correct place to fix it, before figuring out what to fix :)
[16:18] <mrand> Unless it was a VERY trival patch, even then it is likely to sit around a while.
[16:18] <mrand> As least, based on past experience.
[16:18] <mrand> (referring to php patches)
[16:18] <patdk-wk> my trivial php patchs got submitted pretty quick
[16:19] <patdk-wk> mythweb video showing tv series out of order, not using the episode on the sort, and doing double sorts (mysql and php)
[16:19] <patdk-wk> needless to say, mysql is much better at sorting than php, cause it has indexs :)
[16:19] <mrand> heh.  so why not use them? ;-)
[16:20] <patdk-wk> also, mythweb video directorypath was broken, stripping /'s from paths
[16:20] <patdk-wk> both where commited in under a week :)
[16:21] <mrand> I'm thinking of the case when foxbuntu submitted two patches about the rss feeds.  They layed around for months.
[16:21] <patdk-wk> hmm, I don't even use the rss feature, probably why
[16:22] <patdk-wk> hmm, seems rss is only for recorded programs
[18:27] <thopiekar> hi.. I installed mythbuntu x64 and mythweb on it works great, but I can't watch recordings.. flowplayer says that it can't find the clip at path xy..
[18:31] <patdk-wk> flowplayer?
[18:35] <thopiekar> patdk-wk: yes..
[18:35] <thopiekar> same when trying to play via asx stream
[18:39] <patdk-wk> asx works fine here
[18:39] <patdk-wk> but mediaplayer doesn't like it
[18:39] <patdk-wk> any other video player itworks with
[18:40] <thopiekar> when clicking on the asx stream button I get on the browser: 29800_20101227201500.mpg does not exist in any recognized storage group directories for this host.
[18:40] <thopiekar> do I really need to set up the paths on mythtv-setup?
[18:41] <thopiekar> When I leave these settings untouched mythtv will use default paths isn't it?
[18:42] <thopiekar> because the error message I get when clicking on the asx stream says that it can't find any path in this group.
[18:50] <superm1> it could be a symlink problem
[18:50] <superm1> if you check on the filesystem under the mythweb directory in /var/www, look at the data folder
[18:51] <superm1> are there broken symlinks?
[18:54] <thopiekar> doesn't seem so..
[18:54] <thopiekar> mythtv-setup says before closing that I even haven'T set a default storage folder..
[18:55] <thopiekar> which should i set?
[18:55] <thopiekar> I mean choose?
[18:57] <thopiekar> superm1:
[18:58] <superm1> i'm not sure i've seen that before - do you not have all the right storage groups made maybe?
[19:00] <thopiekar> I haven't set any path atm.. so I 'd like to set a "default" one.. but which path should I choose?
[19:01] <thopiekar> I tried /home/mythtv but it doesn't have the permissions, mythtv-setup says..
[19:12] <superm1> oh /var/lib/mythtv is where "defaults" are
[19:13] <thopiekar> ok I made now an alternative folder which has all read/write rights for all users at /home/mythtv/storage
[19:13] <thopiekar> but thanks, superm1 ;)
[19:15] <thopiekar> yeaH! Settings this folder also fixed my streaming problem
[19:17] <thopiekar> so what you can add in the future, is to set this folder path for "Default" and problems like mine are "pre-solved" :D
[19:21] <tgm4883> thopiekar, default what?
[19:21] <thopiekar> storage group
[19:21] <superm1> well it should have been the default from the install - i suspect you might have made changes to some of the storage groups by hand?
[19:21] <tgm4883> for?
[19:22] <tgm4883> i'm assuming you mean either a videos storage group or a recordings storage group
[19:22] <tgm4883> which both already have defaults
[19:45] <thopiekar> hmm yes, but if these paths are not set mythweb can't find the recordings.
[19:45] <thopiekar> mythwebs fault?
[22:37] <bergqvistjl> Anyone having problems with lirc on mythbuntu 10.10 when upgrading via autobuilds to mythtv 0.24?