[00:08] <jduggan> WW) NVIDIA(0): No valid modes for "1280x720"; removing.
[00:09] <jduggan> a config that worked for 720p for months has stopped working, i think after an update
[00:09] <jduggan> someone like to hint what to look at?
[00:10] <blkorpheus> you running hardy?
[00:10] <blkorpheus> there were updates in hardy that broke myth
[00:11] <jduggan> im running the trunk builds in whatever the standard mythbuntu distro ships
[00:12] <jduggan> i dont generally use ubuntu, so i dont follow the release names
[00:12] <jduggan> trunk builds are mythtv only i believe, they shouldnt affect xorg
[00:12] <jduggan> eb http://weeklybuilds.mythbuntu.org/mythbuntu-trunk/ubuntu gutsy mu
[00:12] <jduggan> ltiverse universe restricted main
[00:13] <jduggan> ^using that repo
[00:13] <blkorpheus> my only point was update to myth
[00:14] <blkorpheus> if the development ubuntu use trunk, then there you have it
[00:14] <jduggan> erm, this is xorg not myth
[00:14] <jduggan> myth works great, xorg wont get the right res :)
[00:15] <jduggan> unless mythbuntu's repo is messing with xorg in its myth packages ;)
[00:16] <jduggan> also, do you know if mythappearance is in the trunk builds
[00:16] <blkorpheus> no, but there has been updates to xorg
[00:17] <blkorpheus> they prevented me from logining in
[00:17] <blkorpheus> loggin in
[00:17] <blkorpheus> had to recompile my nvidia driver
[00:18] <jduggan> hmm, my nvidia driver is working fine, perhaps i should try and find an update :)
[00:18] <jduggan> as for mythappearance, any ideas how i can get that in mythbuntu?
[00:18] <blkorpheus> I never said my driver had an issue
[00:18] <jduggan> (without cheking it out of svn etc
[00:18] <blkorpheus> all i said was I recompiled it
[00:19] <blkorpheus> my issue then vanished
[00:19] <jduggan> well if it worked fine, it wouldnt require a recompile ;)
[00:19] <Lynet> It might have been for fun.
[00:19] <Lynet> ..or he used to use Gentoo and misses it.
[00:19] <jduggan> yea, like them people that throw themselves out of planes
[00:19] <blkorpheus> omg
[00:19] <jduggan> :P
[00:20] <Lynet> ;-p
[00:21] <Lynet> Anyway. Anyone know why my pvr-500 is producing mpeg2-files that makes vlc stutter?
[00:21] <tgm4883_laptop> to get mythappearance into mythbuntu you will need to file a needs packaging bug against mythbuntu
[00:22] <jduggan> tgm4883_laptop: nice one, i take it i can do this from the mythbuntu.org website
[00:22] <tgm4883_laptop> !bugs
[00:22] <ubotu> If you find a bug in Ubuntu or any of its derivatives, please file a bug report at: http://bugs.launchpad.net/ubuntu  -  Bugs in/wishes for the bots can be filed at http://launchpad.net/ubuntu-bots
[00:22] <tgm4883_laptop> sec
[00:23] <blkorpheus> bug #185108
[00:24] <squish102> how do i make home dirs visible in apache? (~/public_html) will i screw up mythweb?
[00:24] <jduggan> already filed?
[00:25] <superm1> blkorpheus, you are getting it too?
[00:25] <jduggan> squish102: provided you load mod_userdir just Put UserDir public_html in your apache config
[00:26] <jduggan> if youre using packaged apache you probably wont need to worry about mod_userdir
[00:26] <jduggan> it'll be loaded
[00:26] <tgm4883_laptop> !bug 185108
[00:26] <jduggan> i dont use mythweb, but i cant see any issues arising from doing so
[00:28] <Lynet> mythweb lives under /mythweb/ and not in the web root, so it shouldn't cause problems.
[00:28] <squish102> kinda wired because my httpd.conf is empty (first time on ubuntu)
[00:28] <blkorpheus> superm1, yup, I feel better knowing you too :)
[00:28] <superm1> blkorpheus, well i dont unfortunately
[00:28] <superm1> been looking to  find the cause though
[00:28] <superm1> because thegodfather has it happening
[00:29] <superm1> i've tried to reproduce in a virtual machine with the new builds as well as with a hardy frontend
[00:29] <superm1> cant unfortunately
[00:29] <blkorpheus> the libs and the frontend version do not match from what I could discern from the flame I got in #mythtv-users
[00:29] <superm1> that is not the case, they were built together
[00:30] <superm1> do you have a good strace or apport report that we could look at?
[00:52] <tgm4883_laptop> superm1, are you able to VNC into your hardy mythbuntu machine?
[00:53] <superm1> well it's a vm
[00:53] <superm1> so
[00:53] <tgm4883_laptop> ah
[00:53] <tgm4883_laptop> I think there may be a bug in it
[00:53] <tgm4883_laptop> i enabled the vnc service
[00:53] <tgm4883_laptop> couldn't vnc in
[00:53] <tgm4883_laptop> rebooted
[00:53] <superm1> how long is your password
[00:53] <tgm4883_laptop> still cant
[00:54] <tgm4883_laptop> 6 chars
[00:54] <superm1> is that the minimum?
[00:54]  * tgm4883_laptop shrugs
[00:54] <tgm4883_laptop> yea, 6 is min
[00:55] <tgm4883_laptop> oh F, never mind
[00:56] <tgm4883_laptop> It helps that if you have a different user name on the target system to actually tell vnc to use that username
[00:56] <superm1> ah
[00:56] <superm1> okay brb i need to setup a second SSID on openwrt
[00:57] <tgm4883_laptop> then you need to seed the torrent
[01:01] <blkorpheus> arrgghh my frontend
[01:01] <blkorpheus> :(
[01:06] <tgm4883_laptop> interesting
[01:06] <tgm4883_laptop> superm1, i think the fglrx driver blew up my system
[01:06] <superm1> wouldn't be the first time
[01:08]  * tgm4883_laptop is going to rip it out and go with onboard video
[01:09] <tgm4883_laptop> there, gone
[01:09] <tgm4883_laptop> and it only sparked a few times
[01:09] <tgm4883_laptop> i was pretty quick at removing it that time
[01:09] <tgm4883_laptop> didn't shock myself once
[01:10] <tgm4883_laptop> I still think they need to work out the plug and play, it shouldn't shock you at all when you remove a piece of hardware
[01:12] <dpantke> Is there any way of upgrading from a standard ubuntu Gutsy load to mythbuntu (gaining autologin, etc)?
[01:12] <tgm4883_laptop> yes
[01:12] <tgm4883_laptop> There is even instructions on how to do it
[01:13] <dpantke> The documentation I keep looking at sends me in circles. Where's this doc at?
[01:13] <tgm4883_laptop> what doc are you looking at?
[01:13] <superm1> dpantke, take a look at mythbuntu.org/existing-ubuntu
[01:23] <lime4x4> When installing mythbuntu on a motherboard with a built in geforce 7150 should i configure the tv output at setup or after installing mythbuntu?
[01:46] <MythbuntuGuest94> Is superm1 online?
[01:49] <MythbuntuGuest94> I have successfully linked a front/backend install to a freenas server. I can see that my MP3's are available and can be seen. I have no sound via the onboard motherboard sound port via headphones. any suggestions on what to try?
[01:54] <tgm4883_laptop> MythbuntuGuest94, check it outside of mythtv
[01:55] <MythbuntuGuest94> thaks
[02:07] <jduggan> 2008-01-23 02:07:04.765 Unable to configure plugin 'mythvideo': not initialized
[02:08] <jduggan> /usr/lib/mythtv/plugins/libmythvideo.so: undefined symbol: _ZN18ConfigurationGroup6byNameE7QString
[02:08] <jduggan> anyone else seeing this in the trunk repo?
[02:27] <jduggan> that error was fixed in a mythvideo update
[02:27] <jduggan> pls ignore
[02:27] <jduggan> :)
[02:28] <blkorpheus> hope the update fixed the frontend
[02:28] <blkorpheus> bug 185108
[02:28] <blkorpheus> !bug 185108
[02:30] <jduggan> im not seeing that bug
[02:30] <jduggan> is that in stable, or trunk?
[02:40] <blkorpheus> I believe trunk
[02:40] <blkorpheus> as I'm using Hardy
[02:40] <blkorpheus> sorry for the delay, I'm trying to fix it myself
[02:40] <tgm4883_laptop> actually, it's probably stable
[02:40] <blkorpheus> true
[02:40] <blkorpheus> but the libs got an update
[02:41] <blkorpheus> it starts up
[02:41] <blkorpheus> then fails
[02:41] <blkorpheus> the backend is still recording and working as normal
[05:31] <superm1> interesting.  that stat64 issue is showing up again in mytharchive build
[05:31] <superm1> http://launchpadlibrarian.net/11491264/buildlog_ubuntu-hardy-i386.mythplugins_0.20.2%2Bfixes15096-0ubuntu3_FAILEDTOBUILD.txt.gz
[07:53] <zero> guten morgen allerseits
[07:53] <zero> or is this channel mainly english, than a good morning :)
[07:55] <thegodfather> morning guys
[07:55] <thegodfather> superm1: ping?
[07:55] <superm1> thegodfather, hey
[07:55] <thegodfather> hey dude
[07:55] <thegodfather> do you use dvb-s in your setup?
[07:55] <superm1> mythplugins is FTBFS due to stat64 problems too
[07:56] <superm1> http://launchpadlibrarian.net/11491264/buildlog_ubuntu-hardy-i386.mythplugins_0.20.2%2Bfixes15096-0ubuntu3_FAILEDTOBUILD.txt.gz
[07:56] <superm1> i dont in my setup no
[07:56] <thegodfather> do you know anybody that does?
[07:56] <thegodfather> i am having issues with the LNB settings
[07:56] <thegodfather> i believe it's a DB bug
[07:57] <superm1> Daviey may
[07:57] <superm1> but i'm not positive
[07:58] <thegodfather> feeeehe
[07:58] <thegodfather> http://www.mythtv.org/pipermail/mythtv-commits/2007-August/031242.html
[07:59] <superm1> well cant you just modify that by hand for now in the DB if thats the case?
[07:59] <thegodfather> yeah i could.. assuming i can find the value to change
[07:59] <superm1> but why that would suddenly show up now isnt explained
[08:00] <thegodfather> because i didn't have a kernel driver that did support diseqc before yesterday
[08:00] <thegodfather> i know it works.. scan blabla from dvb-utils works just fine
[08:00] <superm1> but didn't rolling back to the old libmyth resolve things?
[08:00] <thegodfather> this is a differnt problem
[08:00] <thegodfather> don't get confused
[08:00] <thegodfather> rolling back libmythtv did fix the crash
[08:01] <thegodfather> this is a selection issue from the DB
[08:01] <superm1> oh okay, i'm still thinking about the crash and looking into that :)
[08:01] <superm1> (which is looking like something in the newer binutils at this point)
[08:01] <thegodfather> but if you don't know how dvb-s works, i doubt you can understand the problem
[08:01] <superm1> yeah i've never dealt with dvb-s myself
[08:01] <superm1> as i'm in the US
[08:01] <superm1> and dont do FTA
[08:08] <camelreef> good morning in GMT
[08:19] <superm1> thegodfather, okay good news
[08:20] <superm1> thegodfather, i rebuilt (locally) that same mythtv checkout and mythplugins built against it without the stat64 problems
[08:20] <superm1> i suspect that rebuilding both again on the buildds will solve things then
[08:20] <thegodfather> before you do that..
[08:20] <superm1> ya?
[08:20] <thegodfather> compare the buildd log with the local one
[08:21] <thegodfather> check for different version of packages
[08:21] <superm1> well my pbuilder was set to grab newest stuff from the archive
[08:21] <thegodfather> try to pinpoint where the breakage happened
[08:21] <superm1> i suspect it was in kdelibs
[08:21] <superm1> because that got updated right after the build
[08:21] <superm1> (the last build that is)
[08:21] <thegodfather> ok, check it again
[08:21] <thegodfather> make sure
[08:21] <thegodfather> if there are binaries that did break other runtime binaries
[08:21] <thegodfather> we need to go and look at everything that was built with that broken binary
[08:22] <camelreef> Hi Mario !
[08:22] <superm1> good mornin
[08:22] <thegodfather> there might be tons of other packages that are broken the same way
[08:22] <superm1> k3b was one of them for at least one person
[08:23] <superm1> well and look at it this way, mythplugins would not build in my pbuilder or on the buildd with the first myth build that had the stat64 issue you had
[08:23] <camelreef> I see that 8.04 is still on 0.20.2
[08:23] <superm1> i rebuilt myth locally, and it does build, so i think this is a safe bet to say that was the issue
[08:23] <superm1> camelreef, yeah we are debating on flipping the switch at the end of the month
[08:23] <camelreef> oooh
[08:23] <superm1> but i'm a bit wary because there are still 157 pending bugs open upstream
[08:23] <camelreef> I have on Q regarding the trunk weeklies
[08:23] <superm1> targeted towards 0.21
[08:24] <thegodfather> superm1: you have a reproducible test case for a bug
[08:24] <camelreef> are those build like the release packages?
[08:24] <thegodfather> superm1: you need to pin it down
[08:24] <camelreef> like names, nomenclature, etc ?
[08:24] <superm1> camelreef, identically
[08:24] <thegodfather> superm1: if it is a problem like you describe, there might be other package affected by a wrong build
[08:24] <camelreef> so they would upgrade gracefully to a 8.04 release, then
[08:25] <superm1> in the ideal world yes
[08:25] <camelreef> are we in such a World ?
[08:25] <camelreef> ;o)
[08:25] <superm1> we'll see :)
[08:25] <camelreef> I'm trying to decide wether I want to switch to trunk or not
[08:26] <superm1> well the thing is that upstream they are shooting to be ready by next month or so
[08:26] <superm1> for 0.21
[08:26] <camelreef> ok
[08:26] <camelreef> I'll wait, then
[08:26] <camelreef> other topic
[08:26] <superm1> but if they slip on that, it will be quite a wreck of havoc for us if we are at that release already
[08:26] <camelreef> do you have any impact on v4l-dvb drivers included in the kernel ?
[08:27] <superm1> no more than you would
[08:27] <camelreef> ah
[08:27] <camelreef> I've been following and documenting the Nova-T-500 stuff
[08:27] <camelreef> on list and on the wiki
[08:27] <superm1> regarding the firmware for it?
[08:27] <camelreef> firmware and a few off tree patches
[08:27] <superm1> any idea on the licensing for the firmware?
[08:28] <camelreef> I'm pushing for a review of those last patches
[08:28] <superm1> well sending an email to the kernel team's ML is the best way to get those sorts of things included i've noticed
[08:28] <camelreef> firmware is hairy, but I would like to know where to ask about the inclusion of the latest v4l-dvb tree with eventual additional patches
[08:29] <superm1> they are already at a feature freeze on the kernel
[08:29] <superm1> so i'm not sure getting a new v4l-dvb tree is gonna happen
[08:29] <superm1> but if the patches fix things
[08:29] <camelreef> the nova-t-500 is a pretty attractive DVB-T board, and it would be nice to support it out of the box now that it is 99.9% stable
[08:30] <superm1> def agree there
[08:30] <camelreef> especially 2 tuners with the new mux multirec feature of 0.21
[08:30] <superm1> yeah that's probably why you want to move to trunk eh?
[08:30] <camelreef> that, and other things
[08:31] <superm1> i've been debating myself for that same reason :)
[08:31] <camelreef> plus the fact that the nice themes these days only track0.21
[08:31] <superm1> what themes are these that you are referring to?
[08:32] <superm1> still have a week or two that they can be added to apt possibly
[08:32] <camelreef> MePo - http://home.comcast.net/~zdzisekg/screenshots.html
[08:32] <superm1> can't do that one unfortunately due to licensing problems
[08:32] <camelreef> I'm using an old version of this one
[08:32] <superm1> on the artwork he uses
[08:33] <camelreef> Glass-wide - http://www.mythtvthemes.co.uk/glasswide.shtml
[08:34] <superm1> that's in hardy
[08:34] <camelreef> Metallurgy - http://miffteevee.co.uk/themes/metallurgy.html
[08:34] <camelreef> coool
[08:34] <camelreef> you guys are doing a hell of a work there
[08:34] <superm1> stuarta got metallurgy done
[08:34] <superm1> cool
[08:34]  * camelreef is a happy guy, then !
[08:34] <superm1> oh wait
[08:35] <superm1> "unfinished preview"
[08:35] <superm1> not done yet :)
[08:35] <camelreef> I'll check on the kernel ML about the patches
[08:35] <camelreef> and as for the themes, I can still do them manually
[08:35] <camelreef> like we've never used any beta stuff ;o)
[08:35] <superm1> take a look at http://packages.ubuntu.com/cgi-bin/search_packages.pl?keywords=mythtv-theme&searchon=names&subword=1&version=hardy&release=all
[08:36] <camelreef> .01 releases and Beta Google
[08:36] <superm1> you can see everything that is available now in hardy theme wise from apt
[08:36] <camelreef> K
[08:36] <camelreef> nice
[08:37] <camelreef> I'm crossing my fingers for the 0.21 timing, then
[08:37] <superm1> problem is that Ubuntu's feature freeze is Feb 14
[08:37] <superm1> so after that its a bit rough getting newer stuff in
[08:38] <camelreef> any hope of having 0.21/0.21-fixes in your repos if it doesn't make it in Ubuntu proper ?
[08:38] <superm1> it will be there for sure
[08:38] <superm1> but i would really prefer to make it to archive.ubuntu.com
[08:38] <superm1> most people dont even know about the mythbuntu repos
[08:39] <camelreef> I'm already tracking 0.20.2-fixes from you guys
[08:39] <camelreef> K, so all is not lost for those who know how to read and use Google !
[08:40] <superm1> haha
[08:40] <superm1> yeah
[08:40] <camelreef> the Flash stuff in Mythweb is tempting too, as I record mostly kid stuff and this would be nice to have when travelling
[08:40] <camelreef> nothing like a Dora to get a bit of quiet time
[08:40] <camelreef> and kids don;t care if it's ugly and pstage stamp-sized
[08:41] <superm1> yeah
[08:42] <camelreef> thanks much, have a great day
[08:43] <camelreef> and keep it up, greatly appreciated !
[08:43] <superm1> good day to you too :)
[09:35] <thegodfather> feh
[09:35] <thegodfather> ok.. i got LNB selection to work with an awesome workaround
[09:35] <thegodfather> so it's a bug in the DB
[10:20] <thegodfather> bah...
[10:20] <thegodfather> doesn't work
[10:22] <blkorpheus> /usr/bin/mythfrontend.real: symbol lookup error: /usr/lib/libmyth-0.20.2.so.0: undefined symbol: stat64
[10:22] <jduggan> im not getting that error
[10:24] <blkorpheus> arggghh
[10:24] <blkorpheus> must be a hardy thing :(
[10:24] <blkorpheus> what does that error mean in english?
[10:30] <directhex|bsp> blkorpheus, it means mythfrontend wants access to a particular method or property in /usr/lib/libmyth-0.20.2.so.0 which isn't in there
[10:31] <directhex|bsp> blkorpheus, because mythfrontend was compiled against a different, incompatible version of the library
[10:32] <zero_> may I interrupt you?
[10:32] <zero_> I'm pretty new tu mythtv and have some questions
[10:33] <zero_> mainly about the voip-client
[10:37] <zero_> I get "no open connections"
[10:38] <zero_> does this mean my nat is not configured correctly?
[10:54] <zero_> sorry, but is everyone at lunch?
[10:54] <zero_> :)
[11:01] <directhex|bsp> not many people use mythphone
[11:15] <zero_> :) ok, that's an answer.
[11:15] <zero_> maybe the information module is more often used?
[15:47] <MythbuntuGuest29> hello together
[15:48] <MythbuntuGuest29> hav a problem installing mythbuntu and can't find any help
[15:48] <MythbuntuGuest29> tried everything
[15:48] <jduggan> obviously didnt try waiting ;)
[15:48] <rhpot1991_laptop> or asking
[16:25] <blkorpheus> well the updates fixed the frontend
[16:25] <blkorpheus> but broke it somehow as well
[16:26] <blkorpheus> when the frontend starts itnow goes to the pictures folder?
[16:26] <blkorpheus> and I have to escape to get back to the main menu
[16:26] <blkorpheus> the frontend no longer accepts remote commands either
[16:46] <superm1> blkorpheus, try taking out any dvds
[16:46] <superm1> or cds in the drives
[16:49] <blkorpheus> got the remote working again
[16:49] <blkorpheus> ejected my cds
[16:50] <blkorpheus> trying frontend now
[16:50] <blkorpheus> still starting in photo browser mode
[16:50] <blkorpheus> weird
[16:51] <blkorpheus> http://ubuntuforums.org/showthread.php?p=4191648#post4191648
[16:53] <superm1> any usb drives plugged in?
[16:53] <blkorpheus> yes
[16:53] <superm1> try taking those out
[16:53] <blkorpheus> unhooked
[16:53] <blkorpheus> retying
[16:53] <blkorpheus> trying
[16:53] <superm1> there is a setting in the frontend for this behvaior
[16:54] <blkorpheus> I'm now guessing that
[16:54] <blkorpheus> it worked!
[16:54] <blkorpheus> thx superman
[16:54] <blkorpheus> now to change the settings
[16:54] <blkorpheus> sort of like how the removable media options in gnome
[16:55] <superm1> yeah
[16:55] <blkorpheus> ok
[16:55] <blkorpheus> glad this got fixed asap, thx!
[16:55] <superm1> no problem.  wish i knew why the first build got so messed up in the linking in the first place though :)
[16:55] <blkorpheus> now if we can help that other fella on the forum with thesame issue?
[16:56] <blkorpheus> I just try to do my part and report mishaps
[16:57] <superm1> that's another known issue with launchpad
[16:57] <superm1> its fix has been committed and should be released with launchpad's upcoming new release
[16:57] <blkorpheus> yeah, i did not recognize that was you on the bug page telling me to use apport
[16:57] <superm1> so the next weekly builds should take care of it
[16:57] <blkorpheus> apport just did not pick up the failed start of mythfrontend
[16:58] <superm1> that's so bizarre.  it seems to catch *everything* for me, even stuff that isn't packaged
[17:03] <blkorpheus> "path to import images from"
[17:03] <blkorpheus> has the cdroms and /media/usb
[17:04] <blkorpheus> but no option to tell it to go to the photo viewer?
[17:04] <blkorpheus> Should I just blank that line?
[17:05] <superm1> i'm honestly not sure the appropriate option
[17:05] <superm1> you'll have to play with it a bit
[17:20] <blkorpheus> it seems for now the frontend will not stop this behavior so long as removable media is mounted
[17:20] <blkorpheus> lookingto thebackend
[17:25] <rhpot1991_laptop> !pastebin
[17:25] <ubotu> pastebin is a service to post large 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 #ubuntu channel topic)
[17:28] <blkorpheus> I don't recall having to have no removable media in the drive before I started mythtv prior to these updates?
[19:20] <Bastian7_10> hi
[19:21] <Bastian7_10> where can i change die language of mythbuntu, on the desktop the language is germen, but in den media center i had englisch
[20:36] <laga> so, someone wants to know where to set the language to german?
[20:36] <tgm4883_laptop> Bastian7_10 does
[20:37]  * laga wakes up his master backend
[20:38]  * laga waits for his master backend to finish a file system check
[20:40] <laga> zubehör/konfiguration -> konfiguration -> erscheinungsbild AKA settings -> settings -> appearance
[20:40] <laga> or something like that
[20:40] <laga> don't have the exact wording for the english one handy
[20:41] <Bastian7_10> auf deutsch ist schon gut :)
[23:02] <lime4x4> odd problem i installed mythtv on my gutsy boxn i reboot the gusty box it wants to go thru the entire mythtv setup anyway to fix that?
[23:02] <lime4x4> just the front-end