[12:29] well we can always target 7.10 instead [12:29] and just have several betas between [12:29] i think this auto detection stuff would be really awesome to have in if possible [12:29] I've not looked (doing it Thurs) however we will need a database of cobos for it to work [12:29] cobos? [12:30] combos [12:30] oh right :) [12:30] well this will be directly related to some udev work keescook is doing [12:30] about card order and generic naming schemes [12:30] and I was wondering if it would be betetr to preahps have a button on the completed install asking if they want to submit there setup, which we can use within the database [12:31] this database may not be "necessary" for that exact reason ^(above) === DaveMorris needs to learn to touch type, rather than having his head down [12:32] still could have a feedback button that basically submits lspci or lshal - just to see what we are working with [12:32] but not sure of it's merits tho [12:32] well, I'm not sure if I can actually detect specifically which type of myth device a /dev/video* devnode is, but I'm hoping to at least give unique names to the cards as they're detected [12:32] well /dev/video* nodes are always analog tuners [12:32] /dev/dvb nodes are always digital [12:33] and the only ones that need special support are the pvr's, correct? [12:33] my backend has a /dev/video1 [12:33] not sure why... [12:33] can the nova do analogue too? [12:33] no [12:34] mine are /dev/dvb [12:34] /dev/video1 [12:34] 0 and 2 [12:34] odd [12:34] although my nova's show up as /dev/dvb/* [12:36] Well so for the purposes of these udev rules though,i guess rules for both analog and digtial necessary. For analog to have their own names would be the /dev/video* devices so as to not mix a pvr-xxb with a bttv card. for digital so that your order of cards doesnt get mixed if you say do QAM and OTA or have DVB-S and DVB-T [12:38] So are we trying automate 'mythtv-setup' [12:38] well investigate automation of it at least [12:38] hmm... didn't really think about it [12:38] mythdora and knoppmyth have some level of automation - which DaveMorris and bendailey are looking into [12:38] I didn't realise that [12:38] keescook, perhaps you were thinking about udev rule naming schemes. can you query the PCI ids and the PCI database that lspci uses? [12:39] Haven't tried knoppmyth in well over a year [12:39] and perhaps just a generic /dev/v4l/vendor-model-# ? [12:39] or perhaps get that same info from /sysfs [12:39] superm1: oooh, I can! I need to write a small utility to do produce the right output. that's a _great_ idea! [12:40] How can you find the relationship between lspic output and /dev/location [12:40] I was going to use the v4l "name" that a v4l driver sets, but maybe pci would be better [12:40] the details are already in the udev environment for a given node. [12:40] well perhaps then you can take it this step further, and put symlinks in say /dev/v4l to all the devices as they are created [12:40] and make sure myth *only* uses /dev/v4l and /dev/dvb/something [12:41] for populating its lists in mythtv-setup [12:41] e.g. sudo udevinfo -a -p $(udevinfo -q path -n /dev/video0) [12:41] ATTRS{subsystem_device}=="0x3000" [12:41] ATTRS{subsystem_vendor}=="0x7063" [12:41] that works??? [12:41] wow [12:41] yea just mapping that over to the PCI database would work wonderfully then [12:41] yeah, this is what I was looking at: [12:41] ATTR{name}=="cx88_0_ video _pcHDTV HD3000 HD" [12:41] vs [12:41] ATTR{name}=="ivtv0 encoder MPEG" [12:42] the 2nd ivtv would be "ivtv1 encoder MPEG" and the 2nd cx88 would be cx88_1_ .... [12:42] and then have a fallback to that hex word if no info is avail in PCI database? [12:42] keescook: worth noting that when i run that on my dvb/nova box - it shows them up [12:42] so for some reason /dev/video0 IS also /dev/dvb [12:42] don't think it's a symlink tho [12:43] Daviey: can you pastebin the output of the udevinfo for the device? [12:43] sure [12:44] http://pastebin.ubuntu-uk.org/253 [12:44] very cool, so that's the cx88 too. sweet. [12:45] :) [12:45] though it seems the "name" is cut short like my pcHDTV card too [12:45] I would have thought that: sudo udevinfo -a -p $(udevinfo -q path -n /dev/dvb/adapter0) would work - but it doesn't [12:45] [ 50.241584] CORE cx88[0] : subsystem: 7063:3000, board: pcHDTV HD3000 HDTV [card=22,autodetected] [12:45] vs "pcHDTV HD3000 HD" [12:46] Daviey: I think subdirs are specifically reserved for symlinks, and for -n you need the "real" node or something? I'm still learning my way around udev [12:46] Daviey: what does your dmesg say dmesg | grep Nova ? [12:46] heh - i made my first udev rule last week. That's the only experience i have with it [12:47] returns nothing [12:47] dmesg | grep cx88 [12:47] perhaps? [12:47] oh. dmesg | grep board: ? yeah, or cx88? [12:47] yep [12:47] pastebin? [12:47] sure [12:48] hmm 2000 lines [12:49] http://pastebin.ubuntu-uk.org/254 [12:49] I think I have the same cards as Daviey [12:49] oooh. [12:49] disclaimer - it is an edgy box === DaveMorris backend is a dapper [12:49] Daviey: I think it scrolled off, try sudo grep Nova /var/log/kern.log | tail -1 [12:50] actually its edgy, 2.6.17 [12:50] tail -1? [12:50] what does -1 do? [12:50] 1 line [12:50] last line. I should really get in the habit of tail -n 1 [12:50] keescook: that was > to file then copied. Crappy pastebin cut it off [12:51] Daviey: no, i mean I think the cx88 init string I'm looking for has scrolled out of the kernel dmesg buffer. [12:51] anyway, I gotta run. cya guys later [12:51] cya keescook [12:51] $ sudo grep cx88 /var/log/kern.log | tail -n 1 [12:51] May 29 23:30:25 server kernel: [18402464.800000] cx88[0] /2: cx8802_restart_queue: queue is empty [12:51] see ya keescook [12:51] Daviey: grep for Nova instead of cx88? [12:51] blank [12:52] what's your uptime? [12:52] 14 days :( === j_ack_ [n=jack@p508DAE43.dip0.t-ipconnect.de] has joined #ubuntu-mythtv [12:53] okay, last try: (sudo zcat /var/log/kern*gz; sudo cat /var/log/kern.log.0) | grep Nova | tail -1 ? [12:53] (based on your cx88 output, I bet your logs are _huge_) [12:53] DaveMorris, I was thinking more about this, depending on how this auto configure script is implemented, it can maybe even be put into the regular packages. I can see a lot of it possibly moved to debconf and then probing these new directories that are created by symlinks for udev stuff. Then if someone adds a new card, dpkg-reconfigure mythtv-backend catching it [12:53] yep [12:53] keescook: do you want it? [12:54] Daviey: nah, I just want to see the Nova line if you get it. [12:54] I'm just curious if v4l is cutting off your board's name like it's doing for me [12:54] May 15 19:48:16 server kernel: [17179592.448000] input: cx88 IR (Hauppauge Nova-T DVB-T as /class/input/input2 [12:55] That's the ir module tho [12:55] hm, (sudo zcat /var/log/kern*gz; sudo cat /var/log/kern.log.0) | grep CORE | grep Nova | tail -1 ? [12:55] perhaps that same above command without the tail and pipe [12:55] superm1: yeah, that too [12:56] May 15 19:48:16 server kernel: [17179592.236000] CORE cx88[1] : subsystem: 0070:9002, board: Hauppauge Nova-T DVB-T [card=18,autodetected] [12:56] http://www.pastebin.ca/520457 [12:56] cool [12:57] yeah, yours gets cut off too. I'd love to get the _whole_ name into the udev symlink. okay, I'm gone. thanks for hunting that up. [12:57] np - ttfn [12:57] hey there [12:57] superm1: you therE? [12:57] hi [12:57] Hi gardenhermit [12:58] superm1: i managed to check out that mythbuntu branch but there was no mythweather patch. i' [12:58] s/i'// [12:59] the mythweather patch is on the mythtv branch. I've got the packages built for it for feisty though on my repo space [12:59] at www.mythbuntu.org/~supermario/personal [12:59] ah [12:59] i'll extract $stuff from your .diff.gz then [12:59] got to go bed now.. sorry for missing the CC meeting, i thought it was next week :( [12:59] wait gardenhermit are you gardengnome? [01:00] i'm confused... [01:00] :) [01:01] yes === gardenhermit is now known as gardengnome [01:01] :) [01:01] ornamental hermits are fun. [01:01] i've got to go to bed now [01:01] I'm off as well [01:01] night all [01:02] night guys [01:02] when we release we should ask popey for screencasts of installing/using mythbuntu [01:02] http://linux.slashdot.org/linux/07/05/29/2244233.shtml [01:03] I'm going to be aswell [01:03] night all [01:05] and that article tells me mythdora dosen't automate MythTV setup [01:05] still to determine knoppmyth though [01:05] :) [01:05] yep [01:05] night [01:05] night === hugolp [n=hugolp@89.129.170.80] has joined #ubuntu-mythtv === j_ack_ [n=jack@p508daac9.dip0.t-ipconnect.de] has joined #ubuntu-mythtv === j_ack__ [n=jack@p508DA7A2.dip0.t-ipconnect.de] has joined #ubuntu-mythtv === hugolp [n=hugolp@89.129.170.80] has joined #ubuntu-mythtv === varka_ [n=varkatop@p54A5EC7E.dip.t-dialin.net] has joined #ubuntu-mythtv === superm1 [n=superm1@ubuntu/member/superm1] has joined #ubuntu-mythtv === Hugol1 [n=jo@89.129.170.80] has joined #ubuntu-mythtv === Hugolp [n=jo@89.129.170.80] has joined #ubuntu-mythtv === jono [n=jono@ubuntu/member/jono] has joined #ubuntu-mythtv === Daviey [n=daviey@cpc4-sout2-0-0-cust715.sotn.cable.ntl.com] has joined #ubuntu-mythtv === Daviey [n=daviey@ubuntu/member/daviey] has joined #ubuntu-mythtv === Daviey__ [n=daviey@cpc4-sout2-0-0-cust715.sotn.cable.ntl.com] has joined #ubuntu-mythtv === defendguin [n=supertux@ip5-155.tvmax-fiber-1.hou.ygnition.net] has joined #ubuntu-mythtv [04:59] superm1: you got a sec? [05:02] or would anyone know how to determine the password that ubuntu creates for the mythtv user account === superm1_ [n=superm1@ubuntu/member/superm1] has joined #ubuntu-mythtv [05:09] hey mario [05:09] hey [05:10] how can i tell what the password is for the mythtv user account that fedora creates? [05:10] that ubuntu creates [05:11] well for the account, it doesnt create a known password [05:11] its intended to be random [05:11] lol [05:11] how do i ssh into the box as mythtv user? [05:11] so that you only use the mythtv account for running the BE [05:11] or for auto login to the FE [05:12] you ssh in as the normal user [05:12] well i need to manually run the mythfilldb command [05:12] don't i need to be the mythtv user for that? [05:13] Nope [05:13] just in the mythtv group [05:13] hmmm [05:15] usermod -g mythtv myusername [05:15] G [05:15] arent you on feisty packages/ [05:15] yeah [05:16] then after you run mythtv-setup [05:16] it adds you [05:16] automatically [05:16] ohh hmm [05:16] i get an error when i try to run mythfill [05:16] whats the error? [05:16] 2007-05-29 23:01:52.577 Unable to connect to database! [05:16] 2007-05-29 23:01:52.577 Driver error was [1/1045] : [05:16] QMYSQL3: Unable to connect [05:17] Access denied for user 'mythtv'@'localhost' (using password: YES) [05:17] okay is there a ~/.mythtv/mysql.txt [05:17] for your user? [05:17] (not mythtv) [05:18] 2007-05-29 22:58:57.084 Unable to read configuration file mysql.txt [05:18] 2007-05-29 22:58:57.084 Trying to create a basic mysql.txt file [05:18] 2007-05-29 22:58:57.100 Writing settings file /home/justin/.mythtv/mysql.txt [05:18] okay [05:18] from the first time i tried to run it [05:18] you dont want that [05:18] you must not be in the mythtv group still [05:18] you ran mythtv-setup, it will add you [05:18] i did run it when i first setup the box [05:18] as the regular user? [05:19] i can't be positive of that [05:19] well remove ~/.mythtv [05:19] and run mythtv-setup again [05:19] and it will handle making sure groups are right [05:23] :-) [05:24] i just changed cable providers and i edited my settings at zap2it an hour ago and i'm trying to get the programming guide right [05:25] i went and ssh in as my user ran mythtv-setup it added me to the group and asked me to logout and log back in [05:25] i did so and am trying to run mythtv-setup from my ssh session with the gui displaying here but i dont think it is going well [05:26] just a blue screen [05:28] superm1: should i go through the setup again or should i just run mythfill again will that work well enough? [05:29] blue screen? [05:29] when forwarding over X? [05:31] yeah the wavy blue screen [05:31] no widgets buttons or boxes [05:31] are you forwarding over wifi? [05:31] yeah [05:31] that'd be it [05:32] X forwarding is slow as hell on wifi [05:32] i guess just updating the DB wouldn't work [05:32] seems the channel data is still wrong [05:32] you have to switch channel layouts in mythtv-setup and delete the old channels [05:32] and such [05:32] ahh === defendguin_ [n=supertux@ip5-155.tvmax-fiber-1.hou.ygnition.net] has joined #ubuntu-mythtv [05:36] now i'm connected via a wired connection and it seems to be about the same [05:36] give it a min or so [05:36] it should ventually come up [05:36] (and much faster than wifi would have) [05:36] ok i can do that [05:38] 2007-05-29 23:34:35.827 Using NV NPOT texture extension is the last thing it said in the term window [05:39] if it doesn't come up, you can do "-O ThemePainter=qt" at the end of the command line [05:39] perhaps its trying to use opengl [05:39] which you cant do over ssh [05:39] i don't have a nvidia card on this pc would that make a difference? [05:39] did you set it to opengl painter before> [05:39] 2007-05-29 23:34:30.205 Using the OpenGL painter [05:39] yeah i did [05:40] thats it [05:40] so do it [05:40] mythtv-setup -O ThemePainter=qt [05:40] much better [05:42] hmmm for direct data lineup it says tx62678 [05:45] blow away the dd info i say [05:45] and just put the new stuff in [05:46] i forget do i need to hit the retrieve lineups button now? [05:46] probably [05:47] but nothing comes up in the drop down box after i do [05:47] then username/pass is likely wrong [05:47] if nothing comes up [05:49] hmmm nada and i logged into the zap2it site to double check [05:49] the term should tell you why thats happenin then [05:50] 2007-05-29 23:50:14.805 Fetching lineups from Tribune Media Zap2It... [05:50] 2007-05-29 23:50:14.814 Grabbing channel data [05:50] --23:50:14-- http://datadirect.webservices.zap2it.com/tvlistings/xtvdService [05:50] => `-' [05:50] Resolving datadirect.webservices.zap2it.com... failed: Name or service not known [05:51] hmm [05:52] i can't ping that address maybe they are having issues [05:53] superm1: can you ping that address? [05:53] nope cant ping it either [05:53] but it is resolving [05:53] 206.18.98.160 [05:53] yup [05:54] perhaps DD is having issues [05:54] maybe we need to flush out dns entries [05:57] http://datadirect.webservices.zap2it.com/tvlistings/ this page comes up when i try in a browser [06:02] looks like an error page though so i have no clue [06:03] and i deleted my video source so no tv even with the wrong data lol [06:08] I think zap2it is just having issues [06:08] oh well [06:08] try again in an hour or so i say [06:08] sounds like a plan [06:09] did you pick up a dvi-hdmi cable yet? [06:09] should be in the mail tomorrow [06:09] ah vg [06:15] http://bb.labs.zap2it.com/viewtopic.php?t=791 [06:16] nm thats old [06:21] but i guess its still happening [06:25] have you tried to reboot to let all web info be flushed out (DNS cache, conntrack tables, and anything else) [06:29] still nada [06:29] i term served into my computer at work and it didn't work there either [06:30] pinging that address [06:35] well you can get to the site from a web browser though [06:35] so i dunno what to thikn [06:35] i say go to #mythtv-users and see if you can grab someone else to try to update zap2it data [06:36] (my backend isnt accessible to me atm) === BrainRocketry [n=balvarez@c-68-52-7-152.hsd1.tn.comcast.net] has joined #ubuntu-mythtv === MegaQuark__ [n=gary@pool-71-117-203-17.ptldor.dsl-w.verizon.net] has joined #ubuntu-mythtv [07:50] imbrandon, would you be able to revu a package tonight? [07:51] imbrandon, if you get a chance: http://revu.tauware.de./details.py?upid=5325 (libhdhomerun) === superm1 [n=superm1@ubuntu/member/superm1] has joined #ubuntu-mythtv === superm1_ [n=superm1@ubuntu/member/superm1] has joined #ubuntu-mythtv === hugolp [n=hugolp@89.129.170.80] has joined #ubuntu-mythtv === hugolp [n=hugolp@89.129.170.80] has left #ubuntu-mythtv ["Kopete] === hugolp [n=hugolp@89.129.170.80] has joined #ubuntu-mythtv === hugolp [n=hugolp@89.129.170.80] has left #ubuntu-mythtv ["Kopete] === Hugolp [n=jo@89.129.170.80] has joined #ubuntu-mythtv [10:19] morning === jono [n=jono@ubuntu/member/jono] has joined #ubuntu-mythtv === Hugol1 [n=jo@89.129.167.251] has joined #ubuntu-mythtv === Scholle [n=Scholle@nbra-4db1660c.pool.einsundeins.de] has joined #ubuntu-mythtv === Scholle [n=Scholle@nbra-4db1660c.pool.einsundeins.de] has left #ubuntu-mythtv ["Kopete] === Hugol1 [n=jo@89.129.167.251] has left #ubuntu-mythtv [] === Hugolp [n=jo@89.129.167.251] has joined #ubuntu-mythtv === Hugolp [n=jo@89.129.167.251] has left #ubuntu-mythtv [] === Hugolp [n=jo@89.129.167.251] has joined #ubuntu-mythtv === Hugolp [n=jo@89.129.167.251] has joined #ubuntu-mythtv === Hugolp [n=jo@89.129.167.251] has left #ubuntu-mythtv [] === mattfletcher [n=matt@ctl-heysham-gw.nshc.co.uk] has joined #ubuntu-mythtv [03:23] hello, is this the right room to ask about mythbuntu? [03:23] Yup mattfletcher [03:24] cool. it sounds exciting. i've always wanted to try mythtv on my winmce machine, but it always looked so complex. i just wanted to know if my mce remote will work with it out of the box, as well as my nova-t pci card [03:25] once we are at release, the nova-t will. atm it requires manually loading a module [03:25] we are depending on another team's work for lirc support though, so depending on how far they make it by our release, the remote may require extra work or may not [03:26] morning guys :) [03:26] morning gardengnome [03:32] i see, so with a bit of legwork, they can both run already, but not out of the box? [03:33] Exactly [03:33] superm1_: I haven't yet had a chance to try the image you wanted me to test [03:33] ook tritium [03:33] I'll get to it as soon as possible [03:34] and i can do that legwork on a live cd before i decide whether to replace win mce or not just yet? [03:34] Well unfortunately no. The livecd will only function as a frontend [03:34] the biggest reason is because the backend needs to have somewhere to write to [03:35] but there are a few other technical reasons keeping it from running the backend [03:36] The most ideal thing to do - if you have an extra hard drive (Say 40 gigs), throw that in there [03:36] and do a quick install [03:36] !mythtv [03:36] MythTV is a TV framework for Linux - Instructions for using with Ubuntu at https://help.ubuntu.com/community/MythTV [03:36] will walk you through doing it [03:38] !boobs [03:38] Sorry, I don't know anything about boobs - try searching on http://bots.ubuntulinux.nl/factoids.cgi [03:38] oh. sad. [03:46] tritium, if your tv does indeed only do 640x480, I anticipate things won't look right or be legible. I toyed with the resolution in a VM, and 640x480 is very very difficult to read [03:47] superm1_: I'll verify. it's either 640x480 or 800x600 before I install nvidia-glx [03:47] Then I get 1280x720 [03:49] 800x600 would be much better [03:50] Yes, but still not enough for the big ubiquity windows, which can't be resized [03:50] well they do scale the text to the resolution [03:50] The issue isn't clarity, it's being able to click "Next" to continue the installation [03:50] so if your maximize the window, it should all show up [03:50] but you'll see [03:50] Or, rather, _not_ being able to [03:51] No, maximizing doesn't work [03:52] Anyway, I'm at work, and need to get back to being productive. [03:52] I'll be on this evening... [03:52] Okay. see ya [03:52] See you :) === mattfletcher [n=matt@ctl-heysham-gw.nshc.co.uk] has left #ubuntu-mythtv [] === n4LR [n=n4LR@mail.trinityvideo.net] has joined #ubuntu-mythtv === jono [n=jono@ubuntu/member/jono] has joined #ubuntu-mythtv === hugolp [n=hugolp@89.129.167.251] has joined #ubuntu-mythtv === tgm4883 [n=thomas@c-67-160-174-176.hsd1.or.comcast.net] has joined #ubuntu-mythtv === superm1 [i=malimonc@ubuntu/member/superm1] has joined #ubuntu-mythtv === waldo323 [n=waldo323@h69-129-95-226.69-129.unk.tds.net] has joined #ubuntu-mythtv [06:40] rogue780|mythser, you there? [07:32] superm1, I am now [08:00] hi rogue780|mythser === ompaul [n=ompaul@freenode/staff/gnewsense.ompaul] has joined #ubuntu-mythtv [08:00] superm1, I'm having the same issure with the new mythbuntu build...when it finishes the usplash the screen goes blank and says out of raneg [08:01] *range [08:01] out of range [08:01] can you boot in safe graphics mode? [08:01] nope. the monitor just goes to standby after the usplash [08:02] after the usplash? [08:02] or the first splash [08:02] with the meny [08:02] menu [08:02] the usplash. [08:02] I see the menu, then once I select an option I see the usplash w/the throbber for a few minutes then blackness [08:02] well if you choose safe graphics at the first menu though, any more luck? [08:02] nope [08:03] does an ordinary ubuntu disk work? [08:03] and I might add that the computer I'm testing it on runs feisty just fine [08:04] have you tried particularly - a feisty live disk? [08:04] to see if it comes up [08:05] yes [08:05] works fine [08:05] now *that* is bizarre [08:05] because we use the same packages as them [08:05] have you checked your ISO md5sum? [08:06] to make sure it matches the same thing on the mythbuntu server [08:07] they match [08:07] does the disk check come out okay? [08:07] on the disk? [08:07] i'm not sure if it will at this point [08:08] i havent looked much into properly creating it, but i think it should [08:09] although when I run the disk check it says it finds errors in 3 files [08:09] which 3? [08:10] it doesn't say. it merely states that it found errors in 3 files [08:11] could you boot it up in a vm by chance? [08:11] and compare [08:11] see if it still finds those 3 errors? [08:11] i dont have a vm accessible to me here right now (at work) [08:13] just so as to rule out problems with the burn [08:15] not on this computer (I've had issues with VM destroying ubuntu...I'll try it in a little bit on a computer besides my server) [08:15] with a VM destroying ubuntu? [08:15] woah [08:16] what happened? [08:16] well it broke apt anyway [08:16] which vm package did you use? [08:16] it never installed properly, and everything I tried to use apt it kept trying to finish the install of vmware. no matter how I tried to uninstall, remove, or make apt forget about vm...it stayed. [08:17] I thought I had fixed it at one point, but I actually put the final bullet in apt [08:17] vmware player i'm thining? [08:17] 's head and had to reinstall ubuntu [08:17] not server [08:17] yeah [08:17] i had a similar issue at a point with it [08:17] one of the big reasons i switched to virtualbox === hugolp [n=hugolp@89.129.167.251] has left #ubuntu-mythtv ["Kopete] [08:18] virtualbox? [08:18] http://www.virtualbox.org/ [08:18] they have debs on their site === hugolp [n=jo@89.129.167.251] has joined #ubuntu-mythtv [09:04] rogue780|mythser, also i was going to ask you for a next venture: [09:04] a gdm screen [09:05] I'm not sure what has to go into making one as of yet though, so might have to investigate [09:08] but in the screen, a very simple method of switching sessions needs to be present. (this is essential) === grndslm [n=grndslm@24-116-87-97.cpe.cableone.net] has joined #ubuntu-mythtv [09:40] k guys...i can't get mythbackend to run at start!!! [09:40] this happens with every release of ubuntu...how is this not fixed, or what am i doing wrong? [09:41] what version of ubunut are you running? [09:41] ubuntu* [09:41] before i just added "/usr/bin/mythbackend -d -l /var/log/wherever.log" to the end of /etc/init.d/mythtv-backend...but even that's not working [09:41] feisty [09:41] Hi grndslm, can you start it via the init script manually? [09:41] without your modification [09:41] superm1: no, it won't start [09:41] without [09:42] have you manually changed passwords for the mythtv user or mysql mythtv account? [09:42] even with at startup....but if i run it with the modification at terminal it finally starts [09:42] yup [09:42] and updated /etc/mythtv/mysql.txt? [09:42] hmm....pretty sure, but now that you mention it... [09:42] well the way you should do it is this [09:42] sudo dpkg-reconfigure mythtv-database [09:43] and then sudo dpkg-reconfigure mythtv-common [09:43] make sure the info is right there too [09:43] and it will update all necessary files and debconf databases [09:43] by updating the debconf databases, there won't be a chance for it to break next release [09:45]