[01:35] <savantelite_> so My 1st Time here setting up a backend mythtv. I installed mythtv through the ubuntu store.
[01:35] <savantelite_> Hostname?
[01:35] <savantelite_> Port?
[01:35] <savantelite_> Database name?
[01:38] <savantelite_> poor derek
[01:42] <tgm4883> savantelite_, likely you need to install the backend as well. I'm not entirely sure what gets installed if you just install mythtv
[01:43] <tgm4883> what are you trying to accomplish?
[01:43] <savantelite_> The back end I think is installed. It asked to install that.
[01:44] <savantelite_> my question is hostname or ip?    Do I just look at my connections and imput that ip?
[01:44] <tgm4883> use hostname
[01:44] <tgm4883> provided you can resolve hostnames to IP's on your network
[01:44] <Shadow__X> tgm4883: why wouldnt he just use ip and then know things will work
[01:45] <tgm4883> Shadow__X, too many users have dynamic IPs
[01:45] <tgm4883> plus, thats what hostnames are for :)
[01:45] <Shadow__X> dynamic ips are bad for you
[01:45] <tgm4883> not always
[01:46] <tgm4883> but yea, set up inproperly they are
[01:46] <savantelite_> I have a static IP on my router
[01:46] <tgm4883> which by default they are
[01:46] <savantelite_> For hostname it reads   localhost    by default
[01:47] <tgm4883> savantelite_, you have statically assigned ip's for your local network ?
[01:47] <savantelite_> Just my router
[01:47] <savantelite_> Will my router keep the rest of the machines with the same internal ip?
[01:48] <tgm4883> savantelite_, by default? probably not
[01:48] <savantelite_> so should I just leave it "localhost" for hostname?
[01:49] <tgm4883> no, i'd say set a static IP address on the PC using network manager
[01:49] <tgm4883> if you have any remote frontends in the future localhost will cause issues
[01:50] <savantelite_> k, So can I just do that in IPv4 settings?   or do I have to do it on my router?
[01:51] <tgm4883> savantelite_, just do that in IPv4 settings
[01:53] <savantelite_> Should I use the one it currently gave me? 192.168.2.21?
[01:53] <savantelite_> and what do I do with netmask and gateway feilds?
[01:54] <savantelite_> Is this stuff easy to change after I have a backend up?
[01:55] <tgm4883> no, don't use the one it gave you, as that may be assigned to another PC later
[01:55] <tgm4883> You would want to use something on the same subnet, like 192.168.2.201
[01:55] <tgm4883> netmask is likely 255.255.255.0, gateway is likely the IP of your router
[02:04] <savantelite_> cool that worked fine. I will have to set up my other computers like that:)
[02:04] <savantelite_> So now I put my new ip in to "Hostname"?
[02:05] <savantelite_> Thanks a ton, I will be back in a couple hours
[03:33] <miststlkr> running .23 and have a series which was tagged incorrectly.  If I manually go through and "reset metadata" then rescan using the series ID I can get it to group correctly and get the correct summary and all that, but it won't let go of the old/incorrect artwork.  is there a way to do this other than going through for each pierce of art for each episode and picking through the menu of all artwork?? surely there is at least a
[03:33] <miststlkr> way to wipe it clean for the episode/series at the very least??
[04:36] <yggdrasil> ok wtf have you done with grub/menu.lst
[11:27] <qwebirc45582> hi all
[11:27] <qwebirc45582> any one up for a q on a SQL error I am seeing on a clean 10.10 Mythbuntu install?
[13:05] <patdk-wk> guess not, since he didn't want to ask his question
[13:37] <Nasha> superm1 are you around?
[14:59] <superm1> Nasha, yeah i'm here
[15:00] <superm1> as for ideas to make your solution permanent, if rc.local isn't working, you've got a race condition of sorts going on i'm thinking
[15:01] <Nasha> I see...
[15:03] <Nasha> Do you think i could add it to the lirc init script, and that may make it work?
[15:03] <Nasha> Ad hoc solution, doesnt exactly sort out the cause of the solution though
[15:16] <superm1> i think still need to figure out the cause of the problem first to figure out the best place to fix it
[15:16] <superm1> maybe a good start is having each run of /etc/init.d/lirc echo out into a file
[15:16] <superm1> and run set -x
[15:17] <superm1> then perhaps you might be able to see if there are invokations of it racing somehow
[15:19] <Nasha> What do you mean, echo out into a file?
[15:19] <Nasha> I mean, what would we be echoing
[15:21] <Nasha> After looking at the in_kernel_support code in the init script, the file /sys/devices/virtual/rc/ doesnt exist, so the editing of the protocols file doesnt happen?
[15:24] <superm1> you can add set -x to the top of /etc/init.d/lirc, and there is a way in sh to set a file to redirect all output elsewhere
[15:25] <superm1> so if you redirect it to say /tmp/lirc.`tempfile` that should let you watch the messages output
[15:28] <Nasha> Youve exceeded my linux knowledge im afraid
[15:43] <patdk-wk> I dunno the correct way to do it :)
[15:43] <patdk-wk> but generally just rename the file
[15:43] <patdk-wk> and make a new script with the old name, and have it run the renamed script with output redirected
[15:44] <Nasha> Ok, im getting the general idea
[15:44] <Nasha> How exactly, do i do that?
[15:44] <patdk-wk> just like I said
[15:45] <patdk-wk> mv script script.orig
[15:45] <Nasha> Yep, that part i get
[15:45] <Nasha> As for the contents of the new script
[15:45] <patdk-wk> echo "#!/bin/sh\n. script.orig > script.log 2>script.err\n" > script; chmod a+x script
[15:47] <Nasha> And thats the contents of the new script, and the output will be in script.log
[15:47] <patdk-wk> yep
[15:47] <patdk-wk> I personally would use full paths for everything
[15:48] <Nasha> Yep, to avoid any mix ups
[15:53] <Nasha> Ok, ill give that a shot
[15:55] <superm1> you will probably want to use >> instead of > so that it appends to the file in case there are multiple times it's executed
[15:56] <superm1> and you'll want to make sure that you run set -x
[15:56] <Nasha> set -x in the new file or old?
[15:57] <superm1> either
[15:57] <Nasha> ok
[16:06] <Nasha> nasha@Ion-Frontend:~$ cat /etc/init.d/lirc.err
[16:06] <Nasha> lircd: there seems to already be a lircd process with pid 1003
[16:06] <Nasha> lircd: otherwise delete stale lockfile /var/run/lirc/lircd1.pid
[16:06] <Nasha> the lirc.log seems to be ok
[16:06] <Nasha> but the remote isn't functioning using the lirc mceusb driver, only the ir_core
[16:06] <superm1> so look at it from a fresh boot
[16:07] <Nasha> that is a fresh boot
[16:07] <superm1> that's from a fresh boot?  Then it certainly sounds like something launched it twice
[16:08] <Nasha> Isnt that the issue, the kernel is launching it, and lirc itself is launching/
[16:09] <superm1> so maybe it's udev rule conflicting
[16:09] <superm1> so you can try modifying /lib/udev/rules.d/85-lirc.rules
[16:09] <superm1> to comment out the add rule
[16:10] <Nasha> done, rebooting
[16:12] <Nasha> Nothing new in the err log, and remote is functioning with the repeat error as before
[16:14] <superm1> when you backed up your old conffiles, did you maybe also restore stuff in /etc/rc.d/ or so?
[16:14] <Nasha> certainly not
[16:14] <Nasha> I backed up only .lirc hardware.conf and lircd.conf
[16:15] <superm1> is this machine your master backend
[16:15] <Nasha> No, FE only
[16:16] <superm1> okay, would you mind booting a live disk and trying there, just to rule out some other unforseen modifications here?
[16:16] <superm1> but hm, that won't go through the same steps a fresh boot will
[16:16] <Nasha> Sure
[16:16] <Nasha> Ok...
[16:18] <Nasha> So you want me to load the livecd?
[16:19] <Nasha> Need to find the external dvd drive, dont want to look for it at 3am if i dont have to lol
[16:23] <superm1> well i think you should go to bed if it's 3am, just searching for straws at this point
[16:23] <superm1> nothing definitive to solve it yet
[16:24] <Nasha> Yeh its almost bed time, but because of the time difference, i need to compromise to catch you
[16:25] <superm1> well don't stay up on my account, my brain is a little fried for more ideas atm :)
[16:26] <Nasha> haha ok
[16:27] <Nasha> I was hoping to find a permanent solution, but its not that important. Jarod Wilson's words of advice were to just add the echo lirc > protocols to the lirc init script in place of the kernel code. But that either doesn't work, or ive commented out the wrong code
[16:28] <Nasha> Because it enables all the items in the protocols file, so ive just realised
[16:35] <baggar11> anyone running PIP in here? Wondering how the newer releases of MythTv handle it. Running 9.10 with 0.22 has always seemed to be crash happy...
[16:36] <patdk-wk> hmm, it's always worked for me
[16:36] <patdk-wk> but I haven't used it since .22 :)
[16:44] <baggar11> patdk-wk: what cards are you running?
[16:44] <patdk-wk> for?
[16:45] <patdk-wk> gt220 and gt240
[16:47] <baggar11> capturing of course, unless you weren't replying to my PIP question...
[16:50] <patdk-wk> what would capture matter in PIP?
[16:50] <patdk-wk> PIP only happens on the frontend, not backend
[16:51] <baggar11> because I've had problems with PIP with my capture cards
[16:51] <patdk-wk> PIP has nothing to do with the capture cards
[16:52] <patdk-wk> all pip does is playback two videos
[16:52] <patdk-wk> now, if you have issues recording from both of your cards at once, that is a totally different issue
[17:03] <baggar11> don't seem to have that problem with multiple frontends. so I guess its' the 0.22 frontend
[17:05] <baggar11> I'm about to upgrade to 0.24 on 10.10, and thought I would revisit PIP
[18:04] <persia> Hey.  I'm collecting information about installation targets for each flavour.  Does Mythbuntu plan to release for amd64/i386 for Natty again?  No powerpc or armel images?
[18:05] <tgm4883> persia, correct
[18:05] <tgm4883> also, #mythbuntu-mythtv-dev
[18:05] <tgm4883> err
[18:05] <tgm4883> #mythbuntu-dev
[18:06] <tgm4883> which should forward to #ubuntu-mythtv-dev
[18:25] <superm1> i think there is quite little utility in doing powerpc or armel
[18:26] <superm1> whenever flash gets released for amd64 i'd argue we should stop doing i386 too
[18:27] <rhpot1991> superm1: isn't it already
[18:27] <rhpot1991> or do you mean a stable release?
[18:27] <superm1> not a stable version
[18:27] <rhpot1991> ah ok
[18:27] <superm1> i'm not meaning stop doing i386 packages, just only release amd64 iso's
[18:27] <superm1> people on i386 could still function
 i'm not meaning stop doing i386 packages, just only release amd64 iso's
[18:28] <tgm4883> I like that idea
[18:28] <tgm4883> but whats the reason?
[20:09] <tafkaz> sorry for crossposting, but i really would like to hear your thoughts on this:
[20:10] <tafkaz> i found a wiki entry telling me,. that you can reset the playback profiles back to default by deleting the entries there completely
[20:11] <tafkaz> i tried this, and i managed to delete most of those profiles. but some wont delete...
[20:11] <tafkaz> in the log i get:
[20:11] <tafkaz> 2010-11-23 21:01:59.347 TriggeredConfigurationGroup::removeTarget(): Failed to find desired value(Schonend) -- aborting
[20:11] <tafkaz> anything i could do?
[20:11] <tafkaz> thank you very much for your ideas
[22:02] <Gibby> what is the package for the hdhomerun gui?
[22:03] <rhpot1991> hdhomerun-config-gui I think
[22:03] <rhpot1991> hdhomerun-config - Configuration utility for Silicon Dust HD HomeRun
[22:03] <rhpot1991> hdhomerun-config-gui - GUI Configuration utility for Silicon Dust HD HomeRun
[22:03] <rhpot1991> Gibby: ^
[22:03] <Gibby> can i install just the gui?
[22:04] <rhpot1991> yep
[22:04] <rhpot1991> I'd install both, the cli can do things the gui can't
[22:04] <rhpot1991> which you may never need
[22:04] <Gibby> sweet, it just got here in the mail
[22:04] <rhpot1991> Gibby: very nice
[22:09] <Gibby> is it safe to flash the firmware with this utitlity?
[22:10] <rhpot1991> Gibby: yep should be fine, go get the latest from SD's website
[22:11] <Gibby> yep already got it... so this utility is good for just looking at signal strength and flashing?
[22:11] <rhpot1991> Gibby: you can watch tv with it too, it launches vlc
[22:12] <rhpot1991> kinda useful for checking channels when fixing your lineup
[22:13] <rhpot1991> not sure if there is a better way to add listings for HDHR anymore, back when I did it I added my cable listings, scanned with the HDHR then added the xmltv id's for the scanned channels to match with my cable channels
[22:14] <Gibby> hmm my symbol quality is all over the place