[00:00] other then it just not being safe, is there any other reason I just shouldn't set it up to use root? [00:48] So...err...the frontend doesn't come up now, and mythtv-setup talks about wanting to upgrade our schema, then seems to crash... >.> [00:58] Ah..I think it's in the process of updating. [01:02] Ah...upgrade failed. [01:02] Hooray logs... [01:07] http://pastebin.ubuntu.com/5603/ [01:16] any ideas why mythfilldatabases says it runs and grabs data, but then when I look in the program guide they are all unknown? [01:44] if anyone can help me with nuvexport, I'd be very grateful... http://ubuntuforums.org/showthread.php?p=4498478#post4498478 [01:58] hello, is upgrading from gutsy to hardy mythbuntu supported? or should I do a reinstall? [02:16] KillerKiwi2005, depends, we would like you to do it, so we can see how well it goes [02:17] lol :) [02:18] * tgm4883 isn't kidding [02:20] He's really not. They need guinea pigs. [02:21] sell it to me what new features will i get vs pain from wife for missing her recordings [02:21] flv in mythweb... does that work out of box? [02:21] or does it require transcodeing? [02:21] while we do need people to test it out, and we will try to help you fix any problems, you must realize that Mythbuntu Hardy comes with an Oklahome Warranty [02:22] ... well i do have 3 hds in it and im only using 2.... [02:22] actully 3 hds [02:22] 4 [02:22] did gnome-lirc-properties make it in? [02:22] Oklahoma Warranty? [02:23] Viaken, if it breaks, you get to keep both pieces [02:23] lol nice [02:23] bah [02:24] https://bugs.launchpad.net/ubuntu/+bug/192368 [02:56] I have been running -fixes weekly builds and tonight with a "apt-get upgrade dist-upgrade" I was at 0.21.... Now I noticed the mythbackend fails at the schema upgrade to 1171. Anyone else seeing this? Error is "Query was: INSERT storagegroup (groupname, hostname, dirname) SELECT 'Default', hostname, data FROM settings WHERE value = 'RecordFilePrefix';" "Error was: Driver error was [2/1062]:" [02:59] hi [03:03] camelreef [03:03] !ask | alfa [03:04] alfa: Please don't ask to ask a question, ask the question (all on ONE line, so others can read and follow it easily). If anyone knows the answer they will most likely answer. :-) [03:09] Well, it seems the latest upgrade broke mythfrontend. [03:11] Hardy or Gutsy? [03:11] hello, i just installed the update to 0.21 but the update for mythvideo is grayed out & i can't install it. anyone know what the deal is with that? [03:11] Viaken: gutsy [03:11] What went wrong with you? [03:12] Viaken: mythfrontend won't start. Trying to run from the command line errors out with this message: [03:12] 2008-03-11 21:08:53.203 This version of MythTV requires an updated database schema. Please run mythtv-setup or mythbackend to update your database. [03:12] degreseven: dpkg -l |grep myth [03:12] tritium: Do that then :) [03:12] see if mythvideo version matches the rest [03:13] hads: yes, I will, but that still doesn't address the root problem. An apt-get upgrade shouldn't require additional intervention afterward. [03:13] tritium: I ran into the same/similar issue. Check /var/log/mythtv/mythbackend.log [03:13] Viaken: thanks, I will. [03:13] I had to go in and remove the audioprops column from the programs table in the mythconverg database. [03:13] tritium: Running one of the installed programs isn't really intervention. It's also a mythtv requirement. now. [03:14] hads: I've already completed mythtv-setup before. A simple upgrade should not require it again. [03:14] It *is* intervention. [03:14] rhpot1991: what am i looking for here? its pretty much all 0.21, mythvideo is missing [03:14] It's a mythtv requirement. [03:15] As I said, I completed that requirement long ago, when I first installed. [03:15] rhpot1991: er, sorry.. mythvideo is not missing, it's still at 0.20.2 [03:15] tritium: Did you reboot after the upgrade? [03:15] tritium: It's a requirement to upgrade the DB schema. A mythtv requirement... [03:15] running mythtv-setup every time you want to run the front end, or every time a package is upgraded, is not a documented myhtv requirement [03:15] tritium: Read the error message. [03:16] degreseven: and what are the rest 0.21? [03:16] hads: then perhaps there should have been a note during the upgrade to re-run mythtv-setup, but there was no such note [03:16] Viaken: no, not yet [03:16] restart mythbackend, see if that works [03:16] ... or mythbackend. [03:17] Which is required for the fronent anyway. [03:17] rhpot1991: right [03:17] sudo apt-get install mythvideo should fix that [03:17] hads: what's your point? It still should not be required for a user to run after upgrading packages. [03:17] try that and see if it works [03:17] if not you might need to sudo apt-get dist-upgrade to get the required packages [03:17] tritium: If you say so. [03:18] hads: it is poor package management [03:18] tritium: Sure. [03:18] hads: what's with the attitude? [03:18] rhpot1991: hm it seemed to work, hah. Any idea why only that package would be blocked in the update manager? [03:19] degreseven: it requires a new package with it I think [03:19] as a dependency [03:19] rhpot1991: oh ok. well thanks for the help [03:19] np [03:21] Hmm, 9 new packages to upgrade, and several more if I dist-upgrade, but mythdvd is to be removed... [03:21] Viaken: did you dist-upgrade, and allow removal of mythdvd [03:21] ? [03:23] I did a full-upgrade, and don't recall what got removed. [03:23] Using aptitude, mind you [03:23] I use aptitude as well. [03:23] I'm just not too excited about mythdvd being removed. [03:23] Maybe that's a mythtv requirement ;) [03:23] This system isn't beefy enough to play DVDs realtime, so I don't care. lol [03:23] tritium, mythdvd is now part of mythvideo [03:24] I'll be upgrading soon enough. [03:24] tgm4883: ah, cool. Thanks. [03:24] degreseven, whats missing? [03:25] degreseven is good, he just needed to force the mythvideo install [03:25] rhpot1991, was mythdvd installed? [03:26] didn't ask [03:26] ah [03:26] I know I had to do that [03:26] I recall it has a new dependency, or was it that it wanted to remove mythdvd? [03:26] IIRC, mythdvd is depreciated [03:26] ya it is [03:27] its in mythvideo like you said [03:27] mythvideo is the new mythdvd [03:27] know what else is depreciated? [03:27] whats that? [03:27] foxxbuntu is depreciated [03:27] not as much as Hillary is [03:27] so i did the mythtv-setup and all of the logs are pointing to "Database Schema upgrade FAILED, unlocking." at 1171. Note: This is on 7.10, does anyone have this issue? [03:27] * rhpot1991 moves the political speak here instead [03:28] MythbuntuGuest77: I'll try soon. I'm having problems that sound similar, but haven't run mythtv-setup yet. [03:29] It results in the frontend/backend not starting.... Nice mythbuntu logo on a black backdrop..... [03:29] MythbuntuGuest77: I'm just dist-upgrading first. [03:30] MythbuntuGuest77: Mythtv ticket #4927 [03:31] MythbuntuGuest77: mythfrontend works for me now. Sorry... [03:32] hads: as I suspected, re-running mythtv-setup was not necessary. [03:32] Ticket 4927 looks like the one..... [03:32] tritium: Haha, so, like I said earlier... [03:32] So this would be a recompile to apply the patch... Is that right.. [03:33] hads: no, it's not like you said earlier. [03:33] MythbuntuGuest77: Shouldn't be nessecarry, the issue is in the SQL so you should be able to do it manually. [03:33] hads: it's more like I said earlier. Proper package management shouldn't require the user to run it. [03:33] tritium: Whatever. [03:34] You'd prefer the user to have to do it? [03:34] its easier than building from source, is it not? [03:35] rhpot1991: are you asking me? [03:36] MythbuntuGuest77: What you would need to do is look at what the schema upgrade is doing in libs/libmythtv/dbcheck.cpp and do it manually according to the patch on that ticket. [03:37] hey all [03:38] could use some help with a brand new mythbuntu setup [03:39] !ask | grepdashv [03:40] !ask [03:40] haha [03:40] grepdashv: ask your question and someone will answer if they know it [03:40] ok thx...thought there might be some kind of question bot >_> [03:40] tritium: ya, just saying junk breaks on upgrades it will get fixed [03:40] grepdashv: there is, but they're having problems today [03:41] its better than building from source after all [03:41] rhpot1991: that's true [03:41] i've got a pvr-150, and it seems to be detected ok, but when i try to set it up as an input and scan for channels, i get an error that says it can't be opened [03:45] don't all answer at once >_> [03:49] anyone? [03:52] grepdashv: Please don't ask to ask a question, ask the question (all on ONE line, so others can read and follow it easily). If anyone knows the answer they will most likely answer. :-) [03:53] wow is that the bot just now catching up? [03:54] yes, grepdashv [03:54] tritium: any idea on my pvr150 issue? [03:54] grepdashv: No, I'm sorry. I don't have one, and I've not encountered that error. [03:55] i was surprised that i didn't see anything about the error in the faq, since the card comes pretty highly recommended [03:55] but i may have missed it [03:56] grepdashv: try to sudo modprobe ivtv and then try it again [03:56] ivtv is loaded already afaik [03:56] dmesg | grep ivtv [03:57] [ 53.285504] ivtv0: Autodetected Hauppauge WinTV PVR-150 [04:00] tgm4883: any thoughts? [04:01] thats the only thing that shows up? [04:01] no, no [04:01] that was just what seemed most relevant [04:01] !pastebin [04:01] pastebin is a service to post multiple-lined texts so you don't flood the channel. The Ubuntu pastebin is at http://paste.ubuntu-nl.org (make sure you give us the URL for your paste - see also the channel topic) [04:01] put the whole thing there [04:01] ok [04:03] http://paste.ubuntu-nl.org/59332/ [04:04] grepdashv, pastebin this [04:04] ls -l /dev/vid* [04:04] also, is this a gutsy or hardy install? [04:05] 7.10, so gutsy? [04:05] yep [04:05] mythbuntu install? [04:05] yep [04:05] crw-rw---- 1 root video 81, 0 2008-03-11 11:40 /dev/video0 [04:05] crw-rw---- 1 root video 81, 24 2008-03-11 11:40 /dev/video24 [04:06] crw-rw---- 1 root video 81, 32 2008-03-11 11:40 /dev/video32 [04:06] just those 3 [04:07] and in mythtv-setup you set it up as /dev/video0 and as a hauppauge PVR card? [04:08] yup [04:08] hmm [04:08] tried it as each of v4l and mpeg [04:08] but when i got to the input section, neither one allowed me to scan for channels...failed to open card [04:20] so...? [05:18] fyi - it was because i had no scheduler set up; i have it using "no grabber" now [06:36] can I update the server to .21 without reseting or touching the database? [06:36] or do the packages take care of that? [06:39] hugolp, you will be required to update everything to .21 [06:39] Frontend Included [06:39] .21 does not work with previous versions [06:40] you don't work with previous versions [06:43] foxbuntu___: updating the frontend is fine, but what about the database? [06:44] the db schema will need to be updated [06:44] hugolp, everything has to be upgraded [06:45] tgm4883_laptop: means I have to delete the one that is now, and let the packages create an empty new one and configure it or I dont need to delete it and it will be upgraded automagically? [06:45] tgm4883_laptop, I know I don't work with previous versions [06:45] hugolp, it will be upgraded [06:45] foxbuntu___: cool [06:45] automagically [06:45] going to upgrade now [07:01] good morning [07:01] yes it is [07:01] but just barely [07:02] at least in Scotland [07:02] it's 00:02 here [07:02] camelreef, its 2A here :) [07:02] ouch [07:02] 7 here [07:02] weather is prob better there too [07:02] camelreef, something we can do for you? [07:02] 3C [07:03] for the time being, nothing [07:03] I'm a happy user [07:03] except if you know how to fix the UPnP memory leak [07:03] I have UPnP turned off as I don't need it in the mean time [07:04] https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/200761 [07:06] camelreef, nope sorry, thats a work in progress as im told === foxbuntu___ is now known as foxbuntu_laptop [07:07] who's working on it ? [07:07] not sure [07:07] upstream [07:08] k [07:09] are you using MythTV 0.21? [07:13] yup [07:13] I'm the one who posted the valgrind log [07:14] I was using the PPA backport, now I have the official backport [07:35] camelreef, you need to upgrade to hardy sometime so you can stay up-to-date with the changes [07:36] the backport is intial release only for 0.21, gutsy wont get the 0.21-fixes branch [07:36] foxbuntu_laptop, I'm trying to stick to something relatively stable [07:36] camelreef, I understand...just letting you know [07:37] but the alpha cycle has normally ended, I may switch once beta has started [07:37] I know the process [07:37] I started my mythtv system on gutsy alpha 2 or 3 [07:38] that was alright, I was building it, and the tuner driver also had issues [07:38] but now it is seriously in prod [07:39] I may start switching a few non-critical machines to Hardy in the next few days, though [08:09] hugolp doesn't know what he wants [08:10] work time === MythbuntuGuest10 is now known as Rimers [09:08] hi all [09:09] is there a way of monitoring what programs is accessing swap / harddisk? my Mythbuntu is accessing one of my drives all the time and i cant find out what program is doing it. [09:25] and another good morning from Scotland [09:26] good morning from germany :) [09:27] laga, any news on that leak? Any ticket on that upstream? i failed to find one [09:28] i'm going to make one now, didn't have time last night [09:28] thanks for the log, btw [09:29] OK [09:29] I can make a new one with the ubuntu2 backport that has arrived in the mean time [09:30] * camelreef should be getting his 1TB WD GP disk today :o) [09:31] camelreef: dont think the ubuntu2 build is gonna fix it.. doyou ystillhave the version number of that older build youused yesterday? [09:31] * laga should be getting his 500GB WD GP disk tomorrow :) [09:32] I was using the 0.21 released code backported on the mythbuntu-experimental PPA [09:32] ubuntu1 [09:34] there will be some liceCD, dd and gparted action tonight [09:35] good luck :) [09:35] mine will go in my main desktop (which is alsomy myth frontend) [09:35] my current samsung hdd is making lots of vibrations.. and they're most audible on the couch [09:36] I have currently a pair of 200G, noisy as hell [09:36] I'm planning on making that BE/FE less noticeable [09:36] hdd is the first step [09:36] 2 case fans will be replaced too [09:37] then the CPU heatsink/fan, for a model that is PWM compliant [09:37] and finally the power supply [09:37] i've already got noise dampening etc in this case [09:38] also some hdd noise blockers, but i don't think they're very good [09:38] and rubber nipppels for the fans :) [09:41] camelreef: though it'd be cool if you could make sure the problem still exists with -ubuntu2 [09:41] no need to valgrind, though [09:41] K [09:41] hold on [09:41] ah, one kid in front of the TV [09:42] bah, it's just a backend restart [09:43] done [09:43] hehe [09:43] 20M [09:43] damn kids, get off my tv.. ;) [09:43] not that I mind, I'm at work [09:44] and the 2-year old knows how to use MythTV [09:44] heh [09:44] from the keyboard [09:44] my 2yr old nephew never gets too watch tv, his mother is very strict about that [09:44] the remote is a little bit too abstract for him [09:47] camelreef: does it also consume 100% CPU? [09:57] nope [09:57] ok, that happens for hitme.. [09:57] i made a upstream bug report [09:59] yesterday it took alot of CPU [09:59] but that may have been valgrind [09:59] and I am @ 62M atm, nothing to call home about [10:00] and it's not rising dramatically [10:00] yeah [10:00] ok, i was just wondering ;) [10:00] weird build by the PPA ? [10:00] was I paying for my eagerness? [10:00] no, hitme666 is seeing it too, he's got it from hardy [10:01] ah [10:01] was he on ubuntu1 or ubuntu2 ? [10:02] ubuntu2 i think [10:02] hmm [10:02] crap, if thisd thing is not consistent, even on the same machine.... [10:03] maybe because you got the update? [10:03] we'll let the devs look at it [10:04] OK [10:04] I'm starting djmount on the network, see if using a upnp client changes things [10:05] (note: djmount doesn't work on amd64) [10:06] directhex|work: heh [10:06] I'm using it from a 32 bit machine on the network [10:06] java doesn't work well onamd64 either :/ [10:06] so projectx is borked. [10:06] which sccks because mytharchive finally worked for me with that [10:07] laga, fix your reception [10:07] commercial removal failed because of bad mpeg2, fixing the cabling and installing a masthead amp fixed it [10:07] my reception is fine (DVB-C). mythtranscode doesn't work well with multiple audio streams.. and i think projectx is faster anyways [10:07] ah [10:08] and it really sucks if you get french audio because it decided to throw the german audio stream away (i only have this situation for one channel which i barely watch, but hey) [10:08] using a upnp client made the be go up to 120M, and it went back to 65M [10:09] behaving normally [10:09] odd [10:09] indeed [10:09] we'll let the devs look at it :) [10:15] I gzipped the log and attached it to the MythTV ticket [10:15] camelreef: thanks [10:27] laga, I upgraded to Gutsy instead [10:28] they have this really handy new tool "do-release-upgrade" for servers [10:28] went pretty smooth except it stalled on restarting nfs-kernel-server [10:28] great :) [10:29] had to 'dpkg --configure -a' after a reboot to make it finish [10:29] * laga is afraid that his ACPI wakeup setup will break when upgrading. :/ [10:29] what's that? [10:29] sebrock: my backend shuts down when it's idle and will wake up for the next recording [10:30] oh I dont use that [10:30] my backend is on my 24/7 server [10:30] (although that hasn't worked so well lately, maybe i need to poke 0.21..) [10:30] is that a ug in gutsy or backend? [10:30] sebrock: i can't really justify that for just mythtv :) i used to have a 24/7 server, too [10:31] sure, but my server also does a helluva lot of other stuff, ftp, cups, apache... [10:31] to name some [10:31] sebrock: i still have feisty. i dont think it's a real bug at all.. there are certain locking mechanism where it determines whether it's safe to shutdown or not. maybe i broke one of these [10:31] gah, servers should be 24/7 [10:31] sebrock: yeah, mine only does mythtv. (and my local repo) [10:31] right, btw dpkg --configure -a [10:31] Daviey: no worries, my dedicated server runs 24/7 :) [10:32] great [10:32] what is that, I was told to do it when updating the repo [10:32] sebrock: it'll reconfigure all packages [10:32] and then it continued to configure stuff [10:33] because the upgrade stalled somewhere when configuring packages [10:33] so I'm unsure if I now have a full Gutsy or somewhere between 7.04 and 7.10 [10:34] try to upgrade again? [10:34] (i had to upgrade three times when going from gutsy to hardy.. but i also had some broken third-party packages) [10:35] well doing the same command tells me there is no new upgrade [10:35] and apt-get upgrade does neither [10:37] so all is gold? [10:40] if you've got "gutsy" all over your sources.list and if sudo aptitude dist-upgrade shows there are no new packages [10:40] you should be golden [10:42] then I am [10:42] some minor issues with apache2 tho [10:45] [Wed Mar 12 11:43:12 2008] [error] [client 91.126.96.52] Digest: user `sebastian' in realm `MythTV' not found: / [10:45] thats what I got when trying to access Mythweb [10:45] go to mcc and set your password again? [10:45] mcc? [10:45] my pasword is still in httpd-passwords [10:46] mythbuntu-control-centre [10:46] mcc can do it now [10:46] this is not mythbuntu... [10:46] its just an ordinary gutsy install with myth-backend [10:46] then use sudo dpkg-reconfigure mythweb [10:46] which does the same [10:46] sebrock: you can just install mythbuntu-control-centre on gutsy if you ever feel the need, btw [10:47] so it works on 'just' the backend alswell? [10:47] yes [10:47] and a backend thats not from the mythbuntu release [10:47] ok [10:47] mythbuntu is just ubuntu with mythbuntu-control-centre [10:48] you probably want to clean out old config files from your feisty mythweb install, though [10:49] hm.... [10:49] resetting the password didnt help [10:49] httpd-passwords <- what file is that? [10:49] I wonder what apache thinks a realm is [10:49] thats my file with encrypted passwords [10:50] I updated it with htpasswd but apache still says I'm not in the MythTV realm [10:50] sebrock: mythweb now uses a different kind of authentication IIRC. you need to clear your old config file [10:51] sebrock: it's using digest auth now which uses realms.. i think a realm is a third component which is factored in into the password encryption or something [10:51] oh [10:52] so which file do I have to delete? [11:00] I tried to change it with mythbuntu-control-center but it still says the same [11:04] i dunno. [11:04] i can't know because it was you who made your setup :) [11:05] Im guessing this is something new... my other password enabled sites works fine [11:05] yes, it's using a different setup [11:05] htdigest instead of the old plain auth method [11:12] yeah I noticed [11:13] works now [11:13] xcool [11:13] -x [11:19] wow [11:20] who came up with a default idle time of 60mn for the EIT crawl? [11:20] my EPG is emptying itself! [11:40] there is a gutsy backport now right? [11:40] yup [11:41] turn on the backports in synaptics or sources.list === camelreef is now known as camelreef-lunch [14:10] Anyone out there using the SA4250HDC stb? [14:36] I am thorn apart. Wait for 8.04 or 7.10? [14:36] WWJD? [14:36] 8.04 could use some testing, which also means it can break more easily :) [14:36] its due in april? [14:37] yes [14:37] they wont release POS, I hope === JThundley_ is now known as JThundley__ === JThundley__ is now known as JThundley_ [14:40] i like the philosophy behind mythbuntu [14:41] which is..? [14:41] the control panel [14:44] its a very well packaged product [14:48] I am trying to use the MythWeb flash player (and .asx sreams) in 0.21 but I keep getting the error ".mpg does not exist in any recognized storage group directories for this host." I found the error is being generated by handler.pl. Has anyone else seen this? [14:54] MythbuntuGuest09, are you using a framegrabber tv card? [14:55] directhex|work - No... PVR150 and PVR500 cards.... [14:58] how much is there to do on the alpha4 release? [14:58] or is the most part depending on the 8.04? [14:58] seems quite rough now that I tested it [14:59]