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