[01:14] <tmkt> Helllo Hello
[01:29] <tmkt> hey hey, anyone having any problems with their Videos(not recordings) only playing back at dolby 2.0 with Myth 0.23?
[01:29] <tmkt> Seems the pass through options are gone in the General Settings
[02:24] <olskolirc> i have the control center and the mythtv-setup who want to help me set up my server?  says something about a 4 digit number somewhere that I have to put in the sql box on the control center help please?
[02:24] <olskolirc> do I need an sql server?  I don't want anyone to connect to my mythtv
[03:03] <superm1> olskolirc, you using lucid?
[03:04] <superm1> i suppose that box might be confusing to someone new how it is
[11:57] <gbee> whenever I press the eject button on a DVD-Rom drive I get an error dialog (gnome) telling me it failed, 'eject' from a shell works, any idea how I disable gnomes' media handler so that the eject button works again?
[12:38] <gbee> nevermind, decided to upgrade the distro anyway which may fix it
[14:02] <Jay2k1> !help
[14:02] <Zinn> !help For a  complete list of my knowledge visit: http://www.baablogic.net/Zinn.cgi  Other available commands: !status, !about, !bug [bug_number].
[14:04] <tmkt> Another nice fix would me to add m4v as a video extension for jamu
[14:13] <Jay2k1> fyi: the Zinn help entry contains a broken link at FAQ, is mythbuntu.org/FAQ, should be mythbuntu.org/wiki/faq
[14:13] <Zinn> Hi Jay2k1, something I can help you with today?  I am a bot, use !help to see what I can do.
[15:48] <cr3> I just noticed apt-setup/cdrom/failed popping up today, known problem?
[15:48] <cr3> as part of the installation for the latest lucid image
[15:48] <cr3> at 76% of the installation
[15:50] <cr3> this problem seems to apply across other flavours as well, strange
[16:02] <mrand> thanks Jay2k1.
[16:02] <mrand> @delete faq
[16:06] <superm1> cr3, i noticed that the other day too, but i think it's only if you are installing from !cdrom
[16:06] <superm1> eg usb, network, etcs
[16:06] <superm1> cr3, did you see if today's logic to skip the last page worked for you?
[16:06] <superm1> i added something in that should skip it in --automatic mode
[16:07] <Jay2k1> so, the auto builds thing lets me upgrade from the mythtv 0.22 pre-release that came with mythbuntu 9.10 karmic to 0.22-fixes? because I don't want trunk updates
[16:07] <superm1> Jay2k1, sure they well
[16:07] <superm1> it should explain it all on the faq section on the auto-builds link
[16:07] <Jay2k1> well, it was a bit confusing for me, sure I've read that page
[16:08] <Jay2k1> but then again, I had a look at the sources.list afterwards, and saw something with "trunk" in it
[16:08] <superm1> well we should certainly clarify that text then on that page
[16:08] <superm1> it says trunk-0.22 probably
[16:09] <Jay2k1> yes that
[16:09] <superm1> its because launchpad doesn't allow renaming PPAs
[16:09] <superm1> its only 0.22 builds on that PPA
[16:09] <Jay2k1> couldnt look it up because the partition is unmounted, doing a partimage now before apt-get upgrade just to be sure
[16:09] <cr3> superm1: I've seen some systems with mythbuntu automatically installed, so it seems to have worked
[16:09] <superm1> cr3, awesome :)
[16:09] <Jay2k1> ah ok that explains
[16:10] <cr3> superm1: do you have a bug open for that fix? I could take the opportunity to attach my preseed to that bug which I totally forgot to do last week
[16:10] <superm1> cr3, i just fixed it without a bug report
[16:10] <cr3> superm1: ok, I'll open a quick bug report and you can immediately mark it as fix released :)
[16:11] <superm1> so just file a new bug for that against mythbuntu-live-autostart and attach
[16:11] <superm1> i'll probably install it to /usr/share/doc/mythbuntu-live-autostart/examples or something, need to figure out the right place
[16:12] <cr3> superm1: I've been talking with mathiaz, from the server team, about finding a way to formalize where preseeds could be located across ubuntu flavours
[16:12] <cr3> superm1: it doesn't seem like there's an obvious solution, especially if we potentially consider templating in the mix
[16:12] <cr3> maybe a good topic of conversation/debate for uds
[16:13] <Jay2k1> and - now that I'm here anyway - let me express my appreciation for all your people's work on this project
[16:13] <superm1> cr3, well the primary purpose would be for people to do daily testing or such right?  so maybe it's just best to pick a path and then have testdrive know to try to load from that path
[16:13] <superm1> Jay2k1, thanks!
[16:14] <superm1> cr3, i'm not sure i'm coming yet.  i've got new management, and on the new team i'm not sure we have the budget to send me to brussels, so we'll see
[16:15] <cr3> superm1: what if we sponsored you? could you spare the week?
[16:16] <superm1> cr3, probably
[16:16] <cr3> superm1: by the way, might it be possible that the --automatic fix you applied skips the late_command/success part of the installation?
[16:16] <cr3> superm1: I'll propose your name to my manager then
[16:17] <superm1> cr3, cool thanks.  i'll discuss it with my manager next week and see what he says about this quarters budget too
[16:17] <superm1> i doubt that fix would cause it to skip the late_command
[16:17] <superm1> did it work with earlier images?
[16:19] <cr3> superm1: I don't remember unfortunately, I just noticed that for some of the systems I noticed with mythbuntu magically installed, the late command stuff did not seem to have run like installing ssh for example.
[16:19] <cr3> it is possible that earlier parts of the late command failed, which could've prevented the remaining commands to run, haven't had time to investigate yet
[16:19] <superm1> cr3, do you have both a success and fail late command defined?
[16:20] <superm1> it's a different preseed than you use for alternates, which only supports a single late command
[16:20] <superm1> you might consider also that there are ways to run package installs "during" the install provided the package is available on the pool you are using during install via an ubiquity plugin
[16:21] <superm1> for 10.04 work stuff that's what we're gonna start doing for our factory installs
[16:22] <superm1> oh, but considering you mentioned it was supposed to install ssh, remember ssh is normally installed by default on mythbuntu, and it is controlled by an additional preseed
[16:22] <cr3> superm1: I couldn't find mythbuntu-live-autostart, so I reported bug #533875 with my preseed against the mythbuntu project
[16:22] <Zinn> Bug 533875 in mythbuntu "Mythbuntu prompting to configure backend during installation cannot be automated" [Undecided, New] http://www.launchpad.net/bugs/533875
[16:22] <superm1> cool, works for me
[16:23] <superm1> http://bazaar.launchpad.net/~dell-team/dell-recovery/trunk/annotate/head:/ubiquity/dell-bootstrap.py
[16:23] <Zinn> [bazaar.launchpad.net] ~dell-team/dell-recovery/trunk : contents of ubiquity/dell-bootstrap.py at revision 244
[16:23] <superm1> there's a lot of logic there you don't need to worry about, but take a look at the "Install" class
[16:23] <superm1> by defining something like that you're able to mark additional packages during install as the plugin is processed
[16:24] <cr3> superm1: In my particular context, when I install Ubuntu flavours, this is for testing purposes rather than convenience purposes. So, one implication is that I want the initial install to be as vanilla as possible and not be poluted by other repositories.
[16:24] <superm1> ah, right
[16:24] <cr3> superm1: If I need packages from other repositories, I add the repository and only install the necessary packages explicitly at the very end in the late_command
[16:24] <cr3> superm1: this has been a humbling lesson to learn when reporting false positive bugs :(
[16:25] <superm1> yeah, then that way makes much more sense, and helps to avoid false positives indeed
[16:29] <Jay2k1> Another thing, the auto builds site says "Builds are produced from both the latest "stable" and "trunk" branches from upstream MythTV". Doing dpkg-reconfigure mythbuntu-repos, it asked me to which version I wanted to upgrade, 0.22 or 0.23. Is it correct that 0.22 equals the latest stable here and 0.23 would be trunk then? If so, wouldn't it be a good idea to clarify this in the dpkg-reconfigure text? like, if it'd let you choose between "
[16:29] <Jay2k1> (latest stable)" and "0.23 (trunk - use on your own risk)" or something like that
[16:31] <superm1> Jay2k1, yeah that's correct.
[16:31] <superm1> tgm4883, ^ that's a good recommendation to clarify
[16:32] <superm1> Jay2k1, i've updated the text on the website too, so once the cache expires you should be able to to see it
[16:32] <superm1> cr3, some of the commands you are using for early and late, i'm not sure i'd expect to work on desktop media.  httpd and in-target I thought were specifics to d-i installs only
[16:33] <cr3> superm1: yeah, that's why I check for [ -e /usr/bin/httpd ]
[16:33] <superm1> ah, i see
[16:34] <cr3> I find it unfortunate that this command is not available in the live environment, it's very useful
[16:34] <superm1> on the alternate media what provides it?  surely no full apache install, it's probably a wrapper for something like nc right?
[16:34] <cr3> it's installation specific though, so it would not really make sense to provide in a live environment which is a combination of installation and real environment
[16:35] <cr3> superm1: exactly
[16:35] <superm1> might want to ask cjwatson about pulling it into the live media via casper or something
[16:35] <cr3> I kinda asked a question to that effect in #ubuntu-installer, but perhaps a bug report or an email would be more effective during the weekend :)
[16:35] <superm1> ah yeah just looked at bt there
[16:36] <superm1> i've been seeing him poke around over the weekend now that he has an n900
[16:36] <superm1> but it does sound like it would be incredibly useful for debugging purposes, even in the live env
[16:40] <cr3> superm1: especially since ubiquity has been preseedable, we don't have much of an environment to work from apart from the command line. so, being able to troubleshoot from remote is even more revelant now
[16:43] <superm1> cr3, well i can forsee two logical ways to go about adding that script, take a look at lp:ubuntu/lucid/casper . 1) in the bin/ directory some useful shell scripts live 2) in the scripts/casper-bottom directory, a collection of items that get ran during the boot process.
[16:43] <superm1> i'd probably think the former is the way to go
[16:45] <cr3> superm1: is nc already available in the casper environment?
[16:45] <superm1> Jay2k1, take a look now at http://mythbuntu.org/auto-builds (cache has expired).  does that make more sense now?
[16:46] <Jay2k1> yes, that's better I think.
[16:47] <superm1> cr3, hmm.  you'd have to unpack the initrd to see for sure
[16:48] <superm1> if not, it's on the live system already, so the latter solution of providing a casper script that runs on some flag on /proc/cmdline or some preseed would be sufficient
[16:49] <superm1> Jay2k1, cool thanks.   feel free to point out anything else that is confusing on the site.  people who are new always best at pointing out the stuff that we all take for granted when writing
[16:49] <cr3> superm1: nope, nc is not in initrd.lz
[16:50] <Jay2k1> sure, at least this is something that I could give in return :)
[16:50] <superm1> cr3, you can refer to it as /root/bin/nc at that time instead though probably
[16:50] <superm1> since on the live media, you do have full access to the mounted squashfs at the time of the early command in /root
[16:52] <Jay2k1> I'll explain what led me to all this, perhaps it's nice to know for you: I wanted to build a htpc, looked at several programs/distris and finally decided to use mythtv because of its look and features. I wanted to use a distribution with mythtv preinstalled because I wanted to have as much out-of-the-box working stuff as I could get, and ubuntu, being debian based and yet very up-to-date, seemed to me as the best choice. I downloaded the 
[16:52] <Jay2k1> karmic ISO and installed it. After three weeks or so it all ran smoothly.
[16:53] <Jay2k1> now today I found a bug, googled but couldn't find a solution, explained it on #mythtv-users and they told me it has been fixed 8 wks ago  (http://svn.mythtv.org/trac/changeset/23110/)
[16:53] <Zinn> [svn.mythtv.org] Changeset 23110 – MythTV
[16:53] <superm1> Jay2k1, so you started from a mythbuntu karmic, or ubuntu karmic?
[16:53] <Jay2k1> sorry, mythbuntu.
[16:53] <superm1> Ok.
[16:54] <superm1> so how did you discover autobuilds then?
[16:54] <Jay2k1> they also told me to upgrade to get rid of this, and that I was "using the pre-release, not 0.22 version they put in just so they could get 0.22-fixes into Karmic"
[16:54] <superm1> ah okay, so the folks in there pointed you to auto-builds then, that's good
[16:55] <Jay2k1> and I should not worry, upgrading to 0.22 stable wouldnt break anything, I should just not upgrade to a trunk version
[16:55] <Jay2k1> "You need to enable the repo that has the current 0.22-fixes branch.  I don't know how.  Someone using *buntu could tell you."
[16:56] <Jay2k1> "#mythbuntu likely has someone who could help you enable the repo to get it.  Just make sure you don't enable the trunk repo if you don't want to upgrade to trunk (it's a one-way path, so once you do, you're stuck on trunk until 0.23)"
[16:56] <Jay2k1> this is what they told me.
[16:56] <superm1> so perhaps we need to find a way to make that more discoverable to people if they run into problems
[16:56] <Jay2k1> yes
[16:56] <mrand> Jay2k1: Yeah, the 0.22-trunk is just an unfortunate name - it was left over from when 0.22 WAS trunk.
[16:56] <Jay2k1> I googled for "mythbuntu sources.list" and somehow ended up on the auto builds page, not really sure if that was what I wanted
[16:57] <Jay2k1> so I asked here to be sure.
[16:57] <superm1> mrand, so what i'm thinking is we need a landing page for anyone that has a bug on mythbuntu.org
[16:57] <superm1> and in there reference autobuilds
[16:57] <superm1> and the launchpad tracker
[16:57] <mrand> superm1: good idea.   Also, when was the repo selection added to MCC?
[16:57] <superm1> and the rest of the support page
[16:57] <superm1> mrand, it's only if you have mythbuntu-repos installed that you get that
[16:58] <mrand> Ah.  That could be another pathway to explain about bugs and -fixes
[16:58] <mrand> Even if the repo plugin isn't installed by default, it could have a screen about bugs in MCC
[16:58] <superm1> so once we get a page like that up and running, we need to find a way to make it higher on google searches
[16:59] <superm1> mrand, i think we can do even better than that... if we get this landing page up, we'll just put something in the Applications menu for Mythbuntu help that directs to the webpage
[16:59] <superm1> it allows us to then retroactively update it even on stable releases
[16:59] <mrand> superm1: true.
[17:00] <Jay2k1> now after all this, I think it's a bit suboptimal that a) my mythbuntu ISO contained a pre-release (my bug was minor stuff, but still) and b) that it was not that beginner-friendly to figure out how to be able to update to the latest stable, I thought the repos needed would be enabled already
[17:00] <mrand> superm1: should we expand/rework http://www.mythbuntu.org/testingandreporting since it is already pretty in google results?
[17:01] <Jay2k1> now you could think that enabling the stable repo by default would be the best to do, on the other hand theres the "if its working, dont fix it" rule, and users might have a stable system which might show unwanted behaviours with these kind of auto updates
[17:01] <superm1> a) was unfortunate, but it's how the timing worked out for the release cycle for upstream mythtv versus the ubuntu release cycle we followed.  hopefully they should sync up nicer this time around
[17:02] <superm1> b) is a technical reason, you aren't allowed to enable third party repos by default from ubuntu packages, and yes since they are automated, there is always the chance something can break in that chain (if its working dont fix it is definitely at play here)
[17:03] <Jay2k1> I see
[17:03] <superm1> so i think if we get a /help landing page together for people, that should hopefully alleviate problems with b)
[17:03] <Jay2k1> yes, maybe
[17:04] <superm1> mrand, well that's from our development wiki site for people wanting to contribute
[17:04] <mrand> yeah, It's not a perfect match
[17:04] <superm1> and it's quite wordy right now
[17:04] <superm1> i'm thinking probably a new page would be better
[17:05] <superm1> if we link to it from the front page, it will make it up onto google's pretty links after a short time period
[17:05] <mrand> cool.
[17:08] <mrand> superm1: I'm trying to think of an idea name.   /bugs or maybe reportingbugs is somewhat close, and could also list common known problems (like the release notes page... maybe move that stuff to this page).   I don't care for /help for some reason, although I can't justify it well.
[17:08] <Jay2k1> what would have helped me would have been a note that says "mythbuntu 9.10 users: from default install, you are using a pre-release of mythtv 0.22 that still contains some minor bugs (click here to see why). We recommend that you upgrade to the final version 0.22 by following these three steps: [explain enabling auto builds here]"
[17:09] <superm1> mrand, i'm open to anything, but considering it will probably be linked to from a help menu item in Applications, /help made sense to me
[17:09] <superm1> Jay2k1, yes that sounds like a great recommendation for the release notes on 9.10
[17:09] <mrand> Jay2k1: did you encounter the 9.10 release notes page in your reading/searching?
[17:10] <Jay2k1> touché heh
[17:10] <Jay2k1> (that's a no)
[17:10] <cr3> superm1: are you sure in-target is not available from the ubiquity success_command? I rely on that command and haven't noticed any problems, which doesn't necessarily mean there aren't any problems :)
[17:11] <mrand> Jay2k1: That's perfectly fine.   Just trying to figure out what a user ends up finding.
[17:11] <superm1> mrand, so maybe on download page we should link to release notes too then
[17:11] <superm1> eg "While you're downloading, you may care to read over the <link>"
[17:11] <mrand> superm1: for sure!  I'll do that.
[17:12] <superm1> cr3, well from a live cd booted up, does "which in-target" work?
[17:12] <Jay2k1> well you know, I'm sysadmin, most of my servers are linux, I'm not a noob and usually I'm the one that tells others to rtfm, I feel a bit shitty about this
[17:12] <mrand> hahaha Jay2k1.  think nothing of it.
[17:12] <Jay2k1> :)
[17:13] <superm1> cr3, i'm not aware what would be providing it, since it's normally in the initrd for alternate media
[17:13] <mrand> We know that our stuff is kinda fragmented, and that we have some semi-special situations that are difficult to capture in an easy to find way.  Your case is a perfect example.
[17:13] <cr3> superm1: I'll have to look into that, thanks for the heads up though
[17:14] <superm1> and it's especially difficult to know what the habits are of people that are new to the project (linux experience or not), so a lot of times we're just fishing in murky waters
[17:15] <Jay2k1> I have to admit that I regard release notes as a place where I can mainly see what has changed since the previous version (the most important stuff from the changelog). Of course release notes may also contain important stuff about that particular release
[17:16] <superm1> cr3, ah just checked ubiquity changelog. debian/changelog:  * Install chroot-setup.sh and in-target from debian-installer-utils
[17:16] <superm1> so yes it's included in ubiquity, how nice :)
[17:17] <superm1> be careful with it though, I don't think a debconf frontend is really running at that point still necessarily
[17:17] <cr3> superm1: man, you had me worried for a while there :)
[17:21] <superm1> cr3, does your preseed normally stack on top of the one on the media, or replace it?
[17:22] <superm1> there are a few specifics that are on the media's preseed that you'll want in here still wrg to language support
[17:22] <cr3> superm1: replace it
[17:23] <cr3> superm1: like d-i     pkgsel/install-language-support boolean false and d-i     pkgsel/language-pack-patterns   string?
[17:23] <superm1> exactly, yup
[17:24] <cr3> I've been considering having my preseed override the media preseed, because I think the preseed parser supports redefining keys which get overwritten if they exist already
[17:24] <cr3> that would be a good use case. I wonder if the default preseed name is consistent throughout all flavours
[17:25] <superm1> it should be consistent throughout all flavors
[17:25] <superm1> and as of casper for lucid i added support to use multiple preseeds
[17:26] <cr3> yep, looks like it: xubuntu.seed, mythbuntu.seed, ubuntu.seed, ie authoritative flavour name dot seed
[17:26] <cr3> superm1: man, I should stop joining this channel, more work on my plate now :)
[17:26] <superm1> haha
[17:29] <gbee> so trunk-0.22 is actually the -fixes repo?
[17:30]  * gbee asks before configuring it
[17:34] <gbee> hmm, it's unable to install half the packages for some reason, keeps asking if I want to do a partial install (which I don't since that will break badly)
[17:34] <Spanner3003> hi is interactive tv working the the latest mythbuntu autobuild?
[17:35] <gbee> Spanner3003: mheg?
[17:36] <Spanner3003> yes
[17:36] <gbee> no reason it shouldn't be, at least not one that I'm aware of
[17:36] <gbee> unless someone backported a patch which broke it and no-one has noticed yet
[17:37] <mrand> gbee: , yes trunk-0.22 is actually -fixes
[17:37] <mrand> That unfortunate naming will be avoided in the future.
[17:37] <superm1> gbee, yeah, 0.23 is already named "0.23", 0.24 will be 0.24 etc
[17:37] <gbee> superm1: cool
[17:38] <gbee> did the partial upgrade thing anyway and it turns out to have been misleading, it just wanted to uninstall a couple of conflicting nvidia packages
[17:38] <superm1> gbee, yeah i was just gonna say, that's probably what it was
[17:38] <superm1> because we switched to an nvidia driver that supports an external libvdpau library
[17:39] <superm1> which is the default for 10.04, but wasnt supported on the repos for 9.10
[17:39] <Spanner3003> ok so what am i doing wrong i looked at the myth frontend out put on dmcc and mheg and its dowloading the mheg app but nothing in mheg
[17:39] <gbee> the upgrade from 9.04 to 9.10 went remarkably smoothly, I'm impressed, I would have done it much earlier if I'd known ;)
[17:40] <gbee> Spanner3003: which country?
[17:40] <mrand> gbee: a decent fraction of people had trouble with sound.  Good to hear you aren't one of them!
[17:40] <Spanner3003> uk
[17:40] <gbee> freesat or freeview?
[17:40] <gbee> and which channel
[17:40] <Spanner3003> freesat
[17:40] <Spanner3003> bbc1
[17:41] <Spanner3003> well any bbc channel
[17:41] <Jay2k1> so I'm not the only one who stumbled upon this :)
[17:42] <gbee> mrand: I had to change to unmute the digital output _again_ which was odd, obviously a package insists on muting it when installed, but other than that
[17:44] <gbee> Spanner3003: heh, I was about to say it's working fine in trunk but it's not, seems to have been broken, possibly by the ffmpeg resync a couple of weeks ago, are you using 0.22-fixes or trunk?
[17:45] <gbee> Daniel won't be pleased, that's a new blocker for the 0.23 release
[17:45] <Spanner3003> 0.23 a mythbuntu autobuilb
[17:46] <mrand> gbee:  :-(
[17:46] <Spanner3003> 0.23 a mythbuntu autobuild
[17:46] <gbee> trunk then, yeah, confirmed that it is broken, that's for bringing it to my attention
[17:46] <superm1> Spanner3003, can you file a bug on svn.mythtv.org with this information so that this can be tracked?  also provide the rev # of the autobuild you're on right now
[17:46] <Zinn> [svn.mythtv.org]
[17:47] <gbee> superm1, Spanner3003: don't bother, I'll do it
[17:47] <Spanner3003> how please i've never done one
[17:47] <superm1> Ok.
[17:47] <superm1> Spanner3003, apt-cache policy mythtv-common will tell us the autobuild you're on
[17:48] <superm1> would be useful to verify you are running a build after the sync
[17:48] <gbee> more expedient as I'd only end up being the one to triage it anyway
[17:49] <Spanner3003> what patest bin do you use
[17:49] <superm1> !pastebin
[17:49] <Zinn> when pasting more than 5 lines of data please use http://mythbuntu.pastebin.com so you don't flood the channel.  Then please post the link in the channel.
[17:52] <Spanner3003> http://mythbuntu.pastebin.com/3t4nsptb
[17:52] <Spanner3003> that is the autobuild revition i'm on
[17:52] <superm1> cool thanks, quite recent then
[17:53] <Spanner3003> yep sorry did say i updated today
[17:53] <Spanner3003> did'n
[17:54] <Spanner3003> did'nt***
[18:00] <gbee> superm1: the mythfrontend/backend wrappers don't pass through --version?
[18:01] <gbee> well the mythfrontend wrapper, since the backend doesn't have one as I though
[18:01] <gbee> t
[18:03] <superm1> gbee, huh?  the frontend wrapper should
[18:03] <superm1> it calls         exec /usr/bin/mythfrontend.real "$@"
[18:03] <superm1> which should pass all arguments
[18:03] <gbee> the output is captured?
[18:05] <superm1> if it's started from a non terminal, then it's captured into /var/log/mythtv/mythfrontend.log
[18:06] <superm1> if it's started from a terminal, it goes to stdout
[18:07] <gbee> must be a ssh/ubuntu thing then, guess it's not that important
[18:07] <mrand> gbee:  I have the same setup as you, and it wfm.   puzzling....
[18:07] <superm1> what's happening exactly?
[18:08] <gbee> nothing ;)
[18:08] <superm1> weird...
[18:08] <gbee> http://mythbuntu.pastebin.com/iXjpxa0i
[18:08] <mrand> I do get xprop:  unable to open display ''  (that is two single quotes), but otherwise it does output
[18:09] <gbee> mythfrontend.real --version does work, as expected
[18:09] <superm1> well i'd like to ditch that wrapper script for 10.10, but there are a bunch of problems with doing so still
[18:09] <superm1> what's in your /etc/mythtv/session-settings?
[18:09] <superm1> anything non-standard?
[18:09] <superm1> oh, do you have mythfrontend running?
[18:09] <superm1> there is a pidof mythfrontend.real 2>&1 >/dev/null && wmctrl -a "MythTV Frontend" 2>/dev/null && exit 0
[18:10] <gbee> afaik I've never modified that, and without an original to diff against I could say what is or isn't standard
[18:10] <gbee> superm1: ahh, yes it's running
[18:10] <superm1> that's exactly why then
[18:10] <gbee> right, solved then :)
[18:10] <superm1> its in that script to people don't launch mythfrontend multiple times
[18:10] <superm1> which causes some weird behaviors
[18:12] <mrand> that reminds me that I was going to submit an option to allow for that.
[18:14] <gbee> heh, I've just deleted the session cache because exactly that was happening to me, two instances of mythfrontend were running and I'm guessing the second was there because the xfwm session was starting it
[18:15] <gbee> just a theory, but it was in the session file so that was probably it
[18:15] <greenwom> Hello, Hauppauge hvr-1950  Mythbuntu 9.10    can't get it working.  Have it set as dvb and bound to a source.
[18:15] <greenwom> where should I look first?
[18:16] <gbee> and that's my queue to leave, thanks for the help guys
[18:16] <gbee> err, cue
[18:17] <mrand> greenwom: I don't have dvb, but the first place I'd check is /var/log/dmesg and verify that the device is being initialized successfully.
[18:20] <greenwom> It's hard to tell... the device shows up out of the box as /dev/dvb/frontend/  ** if I add firmware that I extractr I get a /dev/video0
[18:22] <greenwom> either way I can't get it to start :)\
[18:22] <greenwom> !help
[18:22] <Zinn> !help For a  complete list of my knowledge visit: http://www.baablogic.net/Zinn.cgi  Other available commands: !status, !about, !bug [bug_number].
[18:22] <mrand> greenwom: have you tried cat /dev/video0 > filename.mpg
[18:23] <greenwom> I'll add the firmware and try
[18:29] <greenwom> brb, reboot
[18:33] <greenwom> back
[18:34] <greenwom> well I lost my /dev/video0, I am at square one with the hvr-1950
[18:35] <greenwom> !help
[18:35] <Zinn> !help For a  complete list of my knowledge visit: http://www.baablogic.net/Zinn.cgi  Other available commands: !status, !about, !bug [bug_number].
[18:35] <mrand> greenwom: did you check dmesg log?
[18:36] <mrand> greenwom: also try: lsusb
[18:38] <greenwom> it shows up is lsusb,  under dmesg I am still sifting through it (I'm guessing not from all the junk).
[18:38] <greenwom> ya its not loading properly
[18:39] <greenwom> I'm not sure if I should be using the out of thebox support that gives my the /dev/dvb/adapter0/frontend or adding the firmware I extracted....
[18:42] <mrand> greenwom: not sure.  Looks like there was a problem in the past, but I'd expect that to have been resolved by now.   http://ubuntuforums.org/showthread.php?t=994566 Might search the forums for more info.
[18:42] <Zinn> [ubuntuforums.org] [SOLVED] Can't Get Hauppauge hvr-1950 to install - Ubuntu Forums
[18:48] <greenwom> Zinn: I've tried adding the firmware via those instructions...  not haveing any luck
[18:48] <Zinn> Hi greenwom, something I can help you with today?  I am a bot, use !help to see what I can do.
[19:41] <greenwom> mrand: I now have it back as DVB...  but still no luck
[19:42] <greenwom> now I get configuratio #1 chosen from 1 choice (in dmesg)
[19:43] <greenwom> but when I scan for channels card does not start, and there is another firmware error?
[19:47] <greenwom1> http://mythbuntu.pastebin.com
[19:47] <greenwom1> any help?
[19:48] <greenwom1> http://mythbuntu.pastebin.com/Ua2pimfa
[19:51] <greenwom1> hvr-1950 mythbuntu 9.10
[20:44] <dorgan> hello all
[20:44] <dorgan> maybe someone in here can help I have gotten no help on the mythtv mailing list
[20:44] <dorgan> i am trying to get sound working via HDMI with my GT 220 card
[20:45] <dorgan> i have followed: http://wiki.xbmc.org/?title=HOW-TO_set_up_HDMI_audio_on_nVidia_GeForce_G210,_GT220,_or_GT240#Before_You_Begin.2FNotes
[20:45] <Zinn> [wiki.xbmc.org] HOW-TO set up HDMI audio on nVidia GeForce G210, GT220, or GT240 - XBMC
[20:45] <dorgan> and in alsamixer I have unmuted S/PDIF but still i have no sound
[20:49] <dorgan> Zinn: didnt you see I followed that
[20:49] <Zinn> Hi dorgan, something I can help you with today?  I am a bot, use !help to see what I can do.
[20:50] <dorgan> No
[20:50] <dorgan> lol
[20:52] <dorgan> anyone else around
[21:05] <benomatic> anybody have suggestions for a theme that makes the commercial editing coloring easy to see?  so far i'm having little luck finding a good one...
[21:05] <greenwom> wish I could help.  I am still waiting on some help for my hvr-1950.....
[21:06] <greenwom> http://mythbuntu.pastebin.com/Ua2pimfa
[21:24] <dorgan> http://www.nvnews.net/vbulletin/attachment.php?attachmentid=39135&d=1263249229
[21:24] <Zinn> [www.nvnews.net]
[21:24] <dorgan> hello all
[21:24] <dorgan> 3:44
[21:24] <dorgan> maybe someone in here can help I have gotten no help on the mythtv mailing list
[21:24] <dorgan> 3:44
[21:24] <dorgan> i am trying to get sound working via HDMI with my GT 220 card
[21:24] <dorgan> 3:45
[21:24] <dorgan> i have followed: http://wiki.xbmc.org/?title=HOW-TO_set_up_HDMI_audio_on_nVidia_GeForce_G210,_GT220,_or_GT240#Before_You_Begin.2FNotes
[21:24] <Zinn> [wiki.xbmc.org] HOW-TO set up HDMI audio on nVidia GeForce G210, GT220, or GT240 - XBMC
[21:25] <dorgan> and in alsamixer I have unmuted S/PDIF but still i have no sound
[21:40] <gbee> I spoke too soon earlier, between upgrading to Karmic and installing the latest 0.22-fixes weekly builds, the remote stopped working - lirc is correctly configured and working (tested with irw) and mythfrontend can see the socket and is reading the correct lircrc, so I'm stumped
[21:59] <davisc> I've just installed Mythbuntu karmic clean on my system. The internal video player is stretching videos to fill the screen instead of letterboxing in them. Any suggestions?
[22:02] <gbee> davisc: are you now, or have you ever used mythtv on a two monitor (twinview/xinerama) setup?
[22:03] <gbee> I'm not sure if it's even displayed otherwise, but in multi-monitor setups there is a Monitor Aspect Ratio setting in the 'Screen settings' page of the appearance settings
[22:05] <gbee> if it's there you should check that it's correct, SD TVs will be 4:3, widescreen TVs will be 16:9, monitors normally 16:10
[22:05] <davisc> gbee: No, this is a clean mythtv install. Wiped the disk from my previous mythbuntu gutsy install
[22:06] <davisc> gbee: And it's a 19" LCD monitor connected by DVI
[22:08] <gbee> davisc: have you modified the x config? Changed DisplaySize? If a DisplaySize lie exists in xorg.conf, then try removing it
[22:11] <davisc> gbee: There isn't even an xorg.conf. Everything else shows fine, just the videos are causing a problem
[22:12] <gbee> pastebin the output of xdpyinfo
[22:18] <davisc> http://pastebin.ca/1827753
[22:20] <dorgan> EUREEKA….apparently i needed to create /etc/asound.conf and add the following:pcm.!default hdmi:NVidia
[22:20] <dorgan> pcm:iec958 hdmi:NVidia
[22:23] <gbee> davisc: that looks fine, I'm out of ideas but you might want to ask the question in #mythtv-users where they are bound to think of something I haven't
[22:24] <davisc> Thanks
[22:24] <gbee> there is a video aspect override setting that might be worth looking at, but again that should only be a problem if you'd modified the defaults, not on a clean install
[22:32] <superm1> gbee, try ircat
[22:33] <superm1> just to check for any errors in the lircrc itself
[22:34] <superm1> that's a really weird upgrade bug though, especially if it's working w/ irw and was working fully before
[22:54] <gbee> ircat shows everything working too, and I've found I can make things work again if I edit lircrc while the frontend is running ... which is bizarre
[22:55] <gbee> I'm going to change .mythtv/lircrc from a symlink and see whether that has any relationship
[23:00] <superm1> that is the weirdest thing i've ever heard
[23:06] <gbee> yeah, because it's not true, I've figured it out as a myth_system locking bug that I thought had been fixed in -fixes
[23:07] <superm1> do you have a reference to a commit by chance?
[23:07] <gbee> it prevented lirc working for the first two to three minutes after a frontend start
[23:08] <gbee> so editing the file didn't fix anything, it's just that the locks had been released coincidently just as a saved
[23:08] <gbee> s/a/I/
[23:08] <gbee> superm1: I'll dig them up and try to find out why the fix wasn't backported
[23:10] <gbee> doesn't seem the fix was backported after all, http://svn.mythtv.org/trac/changeset/23314  was the trunk commit, http://svn.mythtv.org/trac/ticket/7921  was the ticket
[23:10] <Zinn> [svn.mythtv.org] Changeset 23314 – MythTV
[23:11] <gbee> heh, Zinn only checks the first link
[23:11] <Zinn> Hi gbee, something I can help you with today?  I am a bot, use !help to see what I can do.
[23:11] <gbee> Zinn: do you want to play a game?
[23:11] <Zinn> Hi gbee, something I can help you with today?  I am a bot, use !help to see what I can do.
[23:12] <gbee> aww, he has obviously never seen War Games
[23:17] <gbee> superm1: I've just backported the fix, any idea when the weekly build script runs?
[23:19] <superm1> gbee, 4:40 central time from what i can tell
[23:19] <superm1> Daviey can tell you for sure
[23:21] <gbee> Daviey: ^^, on Sunday, so we've missed it by a couple of hours?
[23:24] <Spanner3003> hi i'v asked this before but i can work out why
[23:24] <gbee> well, less than an hour in fact
[23:25] <Spanner3003> i have mythbuntu the latest autobuild
[23:25] <Spanner3003> and a hauppauge nova-s
[23:27] <superm1> gbee, for some reason it looks like 23670 just got queued up somehow on the PPA
[23:27] <superm1> either Daviey manually did that one, Zinn grew smarter than i ever thought, or there is some magic logic going on for when they're getting queued
[23:27] <Zinn> Hi superm1, something I can help you with today?  I am a bot, use !help to see what I can do.
[23:28] <Spanner3003> i have pulse audio and alsa installed and they seem to work fine but in myth backend i have alsa, pulse audio, /dev/dsp1 and /dev/dsp2 but only /dev/dsp2 gives me sound in tv
[23:28] <gbee> superm1: heh
[23:29] <jolaren> Any swede here using boxer?
[23:32] <Spanner3003> did i explain my-self clear another?
[23:33] <Spanner3003> as i am admittedly not good at explaining my-self
[23:34] <jolaren> Is it okay to discuss cam modules within the own household? my operator required me to have a card to view my channels and I can only get the freechannels to work (i pay for them ofcourse)
[23:37] <jolaren> I do understand if its not allowed.. I guess
[23:38] <Daviey> superm1: I blame Zinn
[23:38] <Zinn> Hi Daviey, something I can help you with today?  I am a bot, use !help to see what I can do.
[23:38] <superm1> Daviey, so did you manually queue that one, or is the cron just running late then?
[23:40] <Daviey> superm1: Zinn logged in and did it manually, with my help
[23:40] <Zinn> Hi Daviey, something I can help you with today?  I am a bot, use !help to see what I can do.
[23:40] <superm1> Daviey, how come cron didn't run it earlier then?
[23:40] <superm1> there were changes to 0.23 earlier today that should have caused a 0.23 build
[23:41] <Daviey> superm1: I changed the time
[23:41] <superm1> oh
[23:41] <Daviey> superm1: do you have any preference on time?
[23:41] <superm1> what's the new time then?
[23:43] <Daviey> superm1: 6:00 AM UTC, unless you think a different time matters
[23:44] <superm1> that's probably fine
[23:45] <Daviey> superm1: urk, lucid failure
[23:45] <superm1> on 0.22, which shouldnt be building on lucid anyway
[23:45] <superm1> i'll disable that
[23:54] <jolaren> superm1: :-) I followed ur guide the first time I installed mythtv
[23:54] <jolaren> =)
[23:55] <Daviey> superm1: i just did a push to mythbuntu-weekly-build.. My hands are left dirty.
[23:57] <superm1> oh god that's dirty
[23:57] <superm1> but i guess it works for now
[23:58] <superm1> cool jolaren, things have come a long way since those old guides :)
[23:58] <superm1> as for discussing cams, soft cams are off limits, hardware cams are fine