[12:29] <superm1> well we can always target 7.10 instead
[12:29] <superm1> and just have several betas between
[12:29] <superm1> i think this auto detection stuff would be really awesome to have in if possible
[12:29] <DaveMorris> I've not looked (doing it Thurs) however we will need a database of cobos for it to work
[12:29] <superm1> cobos?
[12:30] <DaveMorris> combos
[12:30] <superm1> oh right :)
[12:30] <superm1> well this will be directly related to some udev work keescook is doing
[12:30] <superm1> about card order and generic naming schemes
[12:30] <DaveMorris> 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] <superm1> this database may not be "necessary" for that exact reason ^(above)
[12:32] <Daviey> still could have a feedback button that basically submits lspci or lshal - just to see what we are working with
[12:32] <Daviey> but not sure of it's merits tho
[12:32] <keescook> 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] <superm1> well /dev/video* nodes are always analog tuners
[12:32] <superm1> /dev/dvb nodes are always digital
[12:33] <superm1> and the only ones that need special support are the pvr's, correct?
[12:33] <Daviey> my backend has a /dev/video1
[12:33] <Daviey> not sure why...
[12:33] <superm1> can the nova do analogue too?
[12:33] <Daviey> no
[12:34] <DaveMorris> mine are /dev/dvb
[12:34] <Daviey> /dev/video1
[12:34] <Daviey> 0 and 2
[12:34] <Daviey> odd
[12:34] <Daviey> although my nova's show up as /dev/dvb/*
[12:36] <superm1> 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] <Daviey> So are we trying automate 'mythtv-setup'
[12:38] <superm1> well investigate automation of it at least
[12:38] <Daviey> hmm... didn't really think about it
[12:38] <superm1> mythdora and knoppmyth have some level of automation - which DaveMorris and bendailey are looking into
[12:38] <Daviey> I didn't realise that
[12:38] <superm1> 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] <Daviey> Haven't tried knoppmyth in well over a year
[12:39] <superm1> and perhaps just a generic /dev/v4l/vendor-model-# ?
[12:39] <superm1> or perhaps get that same info from /sysfs
[12:39] <keescook> superm1: oooh, I can!  I need to write a small utility to do produce the right output.  that's a _great_ idea!
[12:40] <Daviey> How can you find the relationship between lspic output and /dev/location
[12:40] <keescook> I was going to use the v4l "name" that a v4l driver sets, but maybe pci would be better
[12:40] <keescook> the details are already in the udev environment for a given node.
[12:40] <superm1> 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] <superm1> and make sure myth *only* uses /dev/v4l and /dev/dvb/something
[12:41] <superm1> for populating its lists in mythtv-setup
[12:41] <keescook> e.g. sudo udevinfo -a -p $(udevinfo -q path -n /dev/video0)
[12:41] <keescook>     ATTRS{subsystem_device}=="0x3000"
[12:41] <keescook>     ATTRS{subsystem_vendor}=="0x7063"
[12:41] <superm1> that works???
[12:41] <superm1> wow
[12:41] <superm1> yea just mapping that over to the PCI database would work wonderfully then
[12:41] <keescook> yeah, this is what I was looking at:
[12:41] <keescook>     ATTR{name}=="cx88_0_ video _pcHDTV HD3000 HD"
[12:41] <keescook> vs
[12:41] <keescook>     ATTR{name}=="ivtv0 encoder MPEG"
[12:42] <keescook> the 2nd ivtv would be  "ivtv1 encoder MPEG"  and the 2nd cx88 would be  cx88_1_ ....
[12:42] <superm1> and then have a fallback to that hex word if no info is avail in PCI database?
[12:42] <Daviey> keescook: worth noting that when i run that on my dvb/nova box - it shows them up
[12:42] <Daviey> so for some reason /dev/video0 IS also /dev/dvb
[12:42] <Daviey> don't think it's a symlink tho
[12:43] <keescook> Daviey: can you pastebin the output of the udevinfo for the device?
[12:43] <Daviey> sure
[12:44] <Daviey> http://pastebin.ubuntu-uk.org/253
[12:44] <keescook> very cool, so that's the cx88 too.  sweet.
[12:45] <Daviey> :)
[12:45] <keescook> though it seems the "name" is cut short like my pcHDTV card too
[12:45] <Daviey> I would have thought that:  sudo udevinfo -a -p $(udevinfo -q path -n /dev/dvb/adapter0)  would work - but it doesn't
[12:45] <keescook> [   50.241584]  CORE cx88[0] : subsystem: 7063:3000, board: pcHDTV HD3000 HDTV [card=22,autodetected] 
[12:45] <keescook> vs "pcHDTV HD3000 HD"
[12:46] <keescook> 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] <keescook> Daviey: what does your dmesg say   dmesg | grep Nova    ?
[12:46] <Daviey> heh - i made my first udev rule last week.  That's the only experience i have with it
[12:47] <Daviey> returns nothing
[12:47] <superm1> dmesg | grep cx88
[12:47] <superm1> perhaps?
[12:47] <keescook> oh.    dmesg | grep board:  ?   yeah, or cx88?
[12:47] <Daviey> yep
[12:47] <Daviey> pastebin?
[12:47] <keescook> sure
[12:48] <Daviey> hmm 2000 lines
[12:49] <Daviey> http://pastebin.ubuntu-uk.org/254
[12:49] <DaveMorris> I think I have the same cards as Daviey
[12:49] <keescook> oooh.
[12:49] <Daviey> disclaimer - it is an edgy box
[12:49] <keescook> Daviey: I think it scrolled off, try   sudo grep Nova /var/log/kern.log | tail -1
[12:50] <DaveMorris> actually its edgy, 2.6.17
[12:50] <superm1> tail -1?
[12:50] <superm1> what does -1 do?
[12:50] <DaveMorris> 1 line
[12:50] <keescook> last line.  I should really get in the habit of  tail -n 1
[12:50] <Daviey> keescook: that was > to file then copied.  Crappy pastebin cut it off
[12:51] <keescook> Daviey: no, i mean I think the cx88 init string I'm looking for has scrolled out of the kernel dmesg buffer.
[12:51] <keescook> anyway, I gotta run.  cya guys later
[12:51] <superm1> cya keescook
[12:51] <Daviey> $ sudo grep cx88 /var/log/kern.log | tail -n 1
[12:51] <Daviey> May 29 23:30:25 server kernel: [18402464.800000]  cx88[0] /2: cx8802_restart_queue: queue is empty
[12:51] <Daviey> see ya keescook
[12:51] <keescook> Daviey: grep for Nova instead of cx88?
[12:51] <Daviey> blank
[12:52] <keescook> what's your uptime?
[12:52] <Daviey> 14 days :(
[12:53] <keescook> okay, last try:   (sudo zcat /var/log/kern*gz; sudo cat /var/log/kern.log.0) | grep Nova | tail -1     ?
[12:53] <keescook> (based on your cx88 output, I bet your logs are _huge_)
[12:53] <superm1> 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] <Daviey> yep
[12:53] <Daviey> keescook: do you want it?
[12:54] <keescook> Daviey: nah, I just want to see the Nova line if you get it.
[12:54] <keescook> I'm just curious if v4l is cutting off your board's name like it's doing for me
[12:54] <Daviey> May 15 19:48:16 server kernel: [17179592.448000]  input: cx88 IR (Hauppauge Nova-T DVB-T as /class/input/input2
[12:55] <Daviey> That's the ir module tho
[12:55] <keescook> hm, (sudo zcat /var/log/kern*gz; sudo cat /var/log/kern.log.0) | grep CORE | grep Nova | tail -1   ?
[12:55] <superm1> perhaps that same above command without the tail and pipe
[12:55] <keescook> superm1: yeah, that too
[12:56] <Daviey> 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] <DaveMorris> http://www.pastebin.ca/520457
[12:56] <keescook> cool
[12:57] <keescook> 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] <Daviey> np - ttfn
[12:57] <gardenhermit> hey there
[12:57] <gardenhermit> superm1: you therE?
[12:57] <DaveMorris> hi
[12:57] <superm1> Hi gardenhermit
[12:58] <gardenhermit> superm1: i managed to check out that mythbuntu branch but there was no mythweather patch. i'
[12:58] <gardenhermit> s/i'//
[12:59] <superm1> 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] <superm1> at www.mythbuntu.org/~supermario/personal
[12:59] <gardenhermit> ah
[12:59] <gardenhermit> i'll extract $stuff from your .diff.gz then
[12:59] <gardenhermit> got to go bed now.. sorry for missing the CC meeting, i thought it was next week :(
[12:59] <superm1> wait gardenhermit are you gardengnome?
[01:00] <superm1> i'm confused...
[01:00] <superm1> :)
[01:01] <gardenhermit> yes
[01:01] <gardengnome> :)
[01:01] <gardengnome> ornamental hermits are fun.
[01:01] <gardengnome> i've got to go to bed now
[01:01] <DaveMorris> I'm off as well
[01:01] <DaveMorris> night all
[01:02] <superm1> night guys
[01:02] <DaveMorris> when we release we should ask popey for screencasts of installing/using mythbuntu
[01:02] <DaveMorris> http://linux.slashdot.org/linux/07/05/29/2244233.shtml
[01:03] <Daviey> I'm going to be aswell
[01:03] <Daviey> night all
[01:05] <DaveMorris> and that article tells me mythdora dosen't automate MythTV setup
[01:05] <superm1> still to determine knoppmyth though
[01:05] <superm1> :)
[01:05] <DaveMorris> yep
[01:05] <DaveMorris> night
[01:05] <superm1> night
[04:59] <defendguin> superm1: you got a sec?
[05:02] <defendguin> or would anyone know how to determine the password that ubuntu creates for the mythtv user account
[05:09] <defendguin> hey mario
[05:09] <superm1_> hey
[05:10] <defendguin> how can i tell what the password is for the mythtv user account that fedora creates?
[05:10] <defendguin> that ubuntu creates
[05:11] <superm1_> well for the account, it doesnt create a known password
[05:11] <superm1_> its intended to be random
[05:11] <defendguin> lol
[05:11] <defendguin> how do i ssh into the box as mythtv user?
[05:11] <superm1_> so that you only use the mythtv account for running the BE
[05:11] <superm1_> or for auto login to the FE
[05:12] <superm1_> you ssh in as the normal user
[05:12] <defendguin> well i need to manually run the mythfilldb command
[05:12] <defendguin> don't i need to be the mythtv user for that?
[05:13] <superm1_> Nope
[05:13] <superm1_> just in the mythtv group
[05:13] <defendguin> hmmm
[05:15] <defendguin> usermod -g mythtv myusername
[05:15] <defendguin> G
[05:15] <superm1_> arent you on feisty packages/
[05:15] <defendguin> yeah
[05:16] <superm1_> then after you run mythtv-setup
[05:16] <superm1_> it adds you
[05:16] <superm1_> automatically
[05:16] <defendguin> ohh hmm
[05:16] <defendguin> i get an error when i try to run mythfill
[05:16] <superm1_> whats the error?
[05:16] <defendguin> 2007-05-29 23:01:52.577 Unable to connect to database!
[05:16] <defendguin> 2007-05-29 23:01:52.577 Driver error was [1/1045] :
[05:16] <defendguin> QMYSQL3: Unable to connect
[05:17] <defendguin> Access denied for user 'mythtv'@'localhost' (using password: YES)
[05:17] <superm1_> okay is there a ~/.mythtv/mysql.txt
[05:17] <superm1_> for your user?
[05:17] <superm1_> (not mythtv)
[05:18] <defendguin> 2007-05-29 22:58:57.084 Unable to read configuration file mysql.txt
[05:18] <defendguin> 2007-05-29 22:58:57.084 Trying to create a basic mysql.txt file
[05:18] <defendguin> 2007-05-29 22:58:57.100 Writing settings file /home/justin/.mythtv/mysql.txt
[05:18] <superm1_> okay
[05:18] <defendguin> from the first time i tried to run it
[05:18] <superm1_> you dont want that
[05:18] <superm1_> you must not be in the mythtv group still
[05:18] <superm1_> you ran mythtv-setup, it will add you
[05:18] <defendguin> i did run it when i first setup the box
[05:18] <superm1_> as the regular user?
[05:19] <defendguin> i can't be positive of that
[05:19] <superm1_> well remove ~/.mythtv
[05:19] <superm1_> and run mythtv-setup again
[05:19] <superm1_> and it will handle making sure groups are right
[05:23] <defendguin> :-)
[05:24] <defendguin> 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] <defendguin> 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] <defendguin> 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] <defendguin> just a blue screen
[05:28] <defendguin> superm1: should i go through the setup again or should i just run mythfill again  will that work well enough?
[05:29] <superm1> blue screen?
[05:29] <superm1> when forwarding over X?
[05:31] <defendguin> yeah the wavy blue screen
[05:31] <defendguin> no widgets buttons or boxes
[05:31] <superm1> are you forwarding over wifi?
[05:31] <defendguin> yeah
[05:31] <superm1> that'd be it
[05:32] <superm1> X forwarding is slow as hell on wifi
[05:32] <defendguin> i guess just updating the DB wouldn't work
[05:32] <defendguin> seems the channel data is still wrong
[05:32] <superm1> you have to switch channel layouts in mythtv-setup and delete the old channels
[05:32] <superm1> and such
[05:32] <defendguin> ahh
[05:36] <defendguin_> now i'm connected via a wired connection and it seems to be about the same
[05:36] <superm1> give it a min or so
[05:36] <superm1> it should ventually come up
[05:36] <superm1> (and much faster than wifi would have)
[05:36] <defendguin_> ok i can do that
[05:38] <defendguin_> 2007-05-29 23:34:35.827 Using NV NPOT texture extension   is the last thing it said in the term window
[05:39] <superm1> if it doesn't come up, you can do "-O ThemePainter=qt" at the end of the command line
[05:39] <superm1> perhaps its trying to use opengl
[05:39] <superm1> which you cant do over ssh
[05:39] <defendguin_> i don't have a nvidia card on this pc would that make a difference?
[05:39] <superm1> did you set it to opengl painter before>
[05:39] <defendguin_> 2007-05-29 23:34:30.205 Using the OpenGL painter
[05:39] <defendguin_> yeah i did
[05:40] <superm1> thats it
[05:40] <superm1> so do it
[05:40] <superm1> mythtv-setup -O ThemePainter=qt
[05:40] <defendguin_> much better
[05:42] <defendguin_> hmmm for direct data lineup it says tx62678
[05:45] <superm1> blow away the dd info i say
[05:45] <superm1> and just put the new stuff in
[05:46] <defendguin_> i forget do i need to hit the retrieve lineups button now?
[05:46] <defendguin_> probably
[05:47] <defendguin_> but nothing comes up in the drop down box after i do
[05:47] <superm1> then username/pass is likely wrong
[05:47] <superm1> if nothing comes up
[05:49] <defendguin_> hmmm nada and i logged into the zap2it site to double check
[05:49] <superm1> the term should tell you why thats happenin then
[05:50] <defendguin_> 2007-05-29 23:50:14.805 Fetching lineups from Tribune Media Zap2It...
[05:50] <defendguin_> 2007-05-29 23:50:14.814 Grabbing channel data
[05:50] <defendguin_> --23:50:14--  http://datadirect.webservices.zap2it.com/tvlistings/xtvdService
[05:50] <defendguin_>            => `-'
[05:50] <defendguin_> Resolving datadirect.webservices.zap2it.com... failed: Name or service not known
[05:51] <defendguin_> hmm
[05:52] <defendguin_> i can't ping that address  maybe they are having issues
[05:53] <defendguin_> superm1: can you ping that address?
[05:53] <superm1> nope cant ping it either
[05:53] <superm1> but it is resolving
[05:53] <defendguin_> 206.18.98.160
[05:53] <superm1> yup
[05:54] <superm1> perhaps DD is having issues
[05:54] <defendguin_> maybe we need to flush out dns entries
[05:57] <defendguin_> http://datadirect.webservices.zap2it.com/tvlistings/   this page comes up when i try in a browser
[06:02] <defendguin_> looks like an error page though so i have no clue
[06:03] <defendguin_> and i deleted my video source so no tv even with the wrong data lol
[06:08] <superm1> I think zap2it is just having issues
[06:08] <defendguin_> oh well
[06:08] <superm1> try again in an hour or so i say
[06:08] <defendguin_> sounds like a plan
[06:09] <superm1> did you pick up a dvi-hdmi cable yet?
[06:09] <defendguin_> should be in the mail tomorrow
[06:09] <superm1> ah vg
[06:15] <defendguin_> http://bb.labs.zap2it.com/viewtopic.php?t=791
[06:16] <defendguin_> nm thats old
[06:21] <defendguin_> but i guess its still happening
[06:25] <superm1> have you tried to reboot to let all web info be flushed out (DNS cache, conntrack tables, and anything else)
[06:29] <defendguin_> still nada
[06:29] <defendguin_> i term served into my computer at work and it didn't work there either
[06:30] <defendguin_> pinging that address
[06:35] <superm1> well you can get to the site from a web browser though
[06:35] <superm1> so i dunno what to thikn
[06:35] <superm1> i say go to #mythtv-users and see if you can grab someone else to try to update zap2it data
[06:36] <superm1> (my backend isnt accessible to me atm)
[07:50] <superm1> imbrandon, would you be able to revu a package tonight?
[07:51] <superm1> imbrandon, if you get a chance: http://revu.tauware.de./details.py?upid=5325 (libhdhomerun)
[10:19] <gardengnome> morning
[03:23] <mattfletcher> hello, is this the right room to ask about mythbuntu?
[03:23] <superm1_> Yup mattfletcher
[03:24] <mattfletcher> 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] <superm1_> once we are at release, the nova-t will.  atm it requires manually loading a module
[03:25] <superm1_> 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] <gardengnome> morning guys :)
[03:26] <superm1_> morning gardengnome
[03:32] <mattfletcher> i see, so with a bit of legwork, they can both run already, but not out of the box?
[03:33] <superm1_> Exactly
[03:33] <tritium> superm1_: I haven't yet had a chance to try the image you wanted me to test
[03:33] <superm1_> ook tritium
[03:33] <tritium> I'll get to it as soon as possible
[03:34] <mattfletcher> and i can do that legwork on a live cd before i decide whether to replace win mce or not just yet?
[03:34] <superm1_> Well unfortunately no.  The livecd will only function as a frontend
[03:34] <superm1_> the biggest reason is because the backend needs to have somewhere to write to
[03:35] <superm1_> but there are a few other technical reasons keeping it from running the backend
[03:36] <superm1_> The most ideal thing to do - if you have an extra hard drive (Say 40 gigs), throw that in there
[03:36] <superm1_> and do a quick install
[03:36] <superm1_> !mythtv
[03:36] <ubotu> MythTV is a TV framework for Linux - Instructions for using with Ubuntu at https://help.ubuntu.com/community/MythTV
[03:36] <superm1_> will walk you through doing it
[03:38] <gardengnome> !boobs
[03:38] <ubotu> Sorry, I don't know anything about boobs - try searching on http://bots.ubuntulinux.nl/factoids.cgi
[03:38] <gardengnome> oh. sad.
[03:46] <superm1_> 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] <tritium> superm1_: I'll verify.  it's either 640x480 or 800x600 before I install nvidia-glx
[03:47] <tritium> Then I get 1280x720
[03:49] <superm1_> 800x600 would be much better
[03:50] <tritium> Yes, but still not enough for the big ubiquity windows, which can't be resized
[03:50] <superm1_> well they do scale the text to the resolution
[03:50] <tritium> The issue isn't clarity, it's being able to click "Next" to continue the installation
[03:50] <superm1_> so if your maximize the window, it should all show up
[03:50] <superm1_> but you'll see
[03:50] <tritium> Or, rather, _not_ being able to
[03:51] <tritium> No, maximizing doesn't work
[03:52] <tritium> Anyway, I'm at work, and need to get back to being productive.
[03:52] <tritium> I'll be on this evening...
[03:52] <superm1_> Okay. see ya
[03:52] <tritium> See you :)
[06:40] <superm1> rogue780|mythser, you there?
[07:32] <rogue780|mythser> superm1, I am now
[08:00] <superm1> hi rogue780|mythser
[08:00] <rogue780|mythser> 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] <rogue780|mythser> *range
[08:01] <superm1> out of range
[08:01] <superm1> can you boot in safe graphics mode?
[08:01] <rogue780|mythser> nope. the monitor just goes to standby after the usplash
[08:02] <superm1> after the usplash?
[08:02] <superm1> or the first splash
[08:02] <superm1> with the meny
[08:02] <superm1> menu
[08:02] <rogue780|mythser> the usplash.
[08:02] <rogue780|mythser> 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] <superm1> well if you choose safe graphics at the first menu though, any more luck?
[08:02] <rogue780|mythser> nope
[08:03] <superm1> does an ordinary ubuntu disk work?
[08:03] <rogue780|mythser> and I might add that the computer I'm testing it on runs feisty just fine
[08:04] <superm1> have you tried particularly - a feisty live disk?
[08:04] <superm1> to see if it comes up
[08:05] <rogue780|mythser> yes
[08:05] <rogue780|mythser> works fine
[08:05] <superm1> now *that* is bizarre
[08:05] <superm1> because we use the same packages as them
[08:05] <superm1> have you checked your ISO md5sum?
[08:06] <superm1> to make sure it matches the same thing on the mythbuntu server
[08:07] <rogue780|mythser> they match
[08:07] <superm1> does the disk check come out okay?
[08:07] <superm1> on the disk?
[08:07] <superm1> i'm not sure if it will at this point
[08:08] <superm1> i havent looked much into properly creating it, but i think it should
[08:09] <rogue780|mythser> although when I run the disk check it says it finds errors in 3 files
[08:09] <superm1> which 3?
[08:10] <rogue780|mythser> it doesn't say. it merely states that it found errors in 3 files
[08:11] <superm1> could you boot it up in a vm by chance?
[08:11] <superm1> and compare
[08:11] <superm1> see if it still finds those 3 errors?
[08:11] <superm1> i dont have a vm accessible to me here right now (at work)
[08:13] <superm1> just so as to rule out problems with the burn
[08:15] <rogue780|mythser> 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] <superm1> with a VM destroying ubuntu?
[08:15] <superm1> woah
[08:16] <superm1> what happened?
[08:16] <rogue780|mythser> well it broke apt anyway
[08:16] <superm1> which vm package did you use?
[08:16] <rogue780|mythser> 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] <rogue780|mythser> I thought I had fixed it at one point, but I actually put the final bullet in apt
[08:17] <superm1> vmware player i'm thining?
[08:17] <rogue780|mythser> 's head and had to reinstall ubuntu
[08:17] <superm1> not server
[08:17] <rogue780|mythser> yeah
[08:17] <superm1> i had a similar issue at a point with it
[08:17] <superm1> one of the big reasons i switched to virtualbox
[08:18] <rogue780|mythser> virtualbox?
[08:18] <superm1> http://www.virtualbox.org/
[08:18] <superm1> they have debs on their site
[09:04] <superm1> rogue780|mythser, also i was going to ask you for a next venture:
[09:04] <superm1> a gdm screen
[09:05] <superm1> I'm not sure what has to go into making one as of yet though, so might have to investigate
[09:08] <superm1> but in the screen, a very simple method of switching sessions needs to be present.  (this is essential)
[09:40] <grndslm> k guys...i can't get mythbackend to run at start!!!
[09:40] <grndslm> this happens with every release of ubuntu...how is this not fixed, or what am i doing wrong?
[09:41] <waldo323> what version of ubunut are you running?
[09:41] <waldo323> ubuntu*
[09:41] <grndslm> 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] <grndslm> feisty
[09:41] <superm1> Hi grndslm, can you start it via the init script manually?
[09:41] <superm1> without your modification
[09:41] <grndslm> superm1:  no, it won't start
[09:41] <grndslm> without
[09:42] <superm1> have you manually changed passwords for the mythtv user or mysql mythtv account?
[09:42] <grndslm> even with at startup....but if i run it with the modification at terminal it finally starts
[09:42] <grndslm> yup
[09:42] <superm1> and updated /etc/mythtv/mysql.txt?
[09:42] <grndslm> hmm....pretty sure, but now that you mention it...
[09:42] <superm1> well the way you should do it is this
[09:42] <superm1> sudo dpkg-reconfigure mythtv-database
[09:43] <superm1> and then sudo dpkg-reconfigure mythtv-common
[09:43] <superm1> make sure the info is right there too
[09:43] <superm1> and it will update all necessary files and debconf databases
[09:43] <superm1> by updating the debconf databases, there won't be a chance for it to break next release
[09:45] <grndslm> hmm...well, i edited mysql.txt, init script still didn't work!
[09:45] <grndslm> superm1:  i will try dpkg-reconfigure
[09:45] <superm1> what does /var/log/mythtv/mythbackend.log say when you are trying?
[09:45] <superm1> perhaps something about permissions to the recordings directory?
[09:49] <grndslm> ahh, yes...thank you superm1:  i did chmod that directory, but it wasn't recursively
[09:50] <grndslm> i think i'm good to go now
[09:50] <superm1> i should have said permissions the first time around, its the most common problem with starting the backend
[09:50] <grndslm> well, you were right both times ;-)
[10:03] <rogue780|mythser> superm1, I think I might be able to rustle something up
[10:05] <superm1> what i'd ideally like is something simlar to a face browswer
[10:05] <superm1> theme
[10:05] <superm1> you know how it lets you choose user names
[10:05] <superm1> but instead have a session browser
[10:05] <superm1> that can show the automatic login as well as the special system administration session we will be shipping
[10:06] <rogue780|mythser> so instead of a username list, it would be a session list?
[10:06] <superm1> if its possible
[10:06] <superm1> i'm not sure if it is
[10:06] <rogue780|mythser> well, might have to modify gdm to do it
[10:07] <superm1> well if it comes down to us having to modify gdm, we can of course do that, but it'd be preferable not to
[10:07] <superm1> the less applications we have to modify, the better :)
[10:17] <rogue780|mythser> indeed
[10:17] <rogue780|mythser> I've gotta go give my wife her ID...she left it behind. bbl
[10:18] <superm1> k
[10:39] <rogue780|mythser> superm1, how do I use virtual box once it's installed? it's not in the menu
[10:39] <superm1> Sure it is
[10:39] <gardengnome> run VirtualBox
[10:40] <superm1> its under system tools
[10:40] <superm1> I think its entitled Innotek Virtualbox
[10:40] <superm1> under that menu
[10:41] <superm1> virtualbox didn't kill your session did it?
[10:57] <rogue780|mythser> no
[10:57] <rogue780|mythser> I killed it so that magically the menu item would appear
[10:57] <rogue780|mythser> how do I get out of fullscreen in virtualbox?
[10:58] <superm1> oh its like rtctrl-entre
[10:58] <superm1> or something like that
[11:00] <DaveMorris> does anyone here use mythtMusic and find it dosen't load all of there music up?
[11:01] <rogue780|mythser> anyway, mythbuntu runs fine in virtualbox
[11:01] <superm1> rogue780|mythser, does it check out fine htough?
[11:01] <superm1> the disk check
[11:02] <superm1> in virtualbox
[11:03] <rogue780|mythser> it found 3 errors with virtualbox
[11:04] <superm1> Ok. well then that will be something that needs to be fixed yet (the disk check)
[11:04] <superm1> i'm wondering why it doesnt boot for your computer though
[11:04] <superm1> or moreover why the regular feisty disk would
[11:04] <DaveMorris> what kernels are been used on them?
[11:05] <superm1> well the one on mythbuntu is the very very latest feisty kernel
[11:05] <superm1> 2.6.20-16
[11:05] <superm1> the one on the feisty disk is likely 2.6.20-15
[11:05] <gardengnome> what about those realtime kernels? would they be beneficial?
[11:05] <rogue780|mythser> I dunno. I'm running a Sempron64 2800, 1Gig'o'ram,  nvidia fx5200
[11:06] <DaveMorris> I've had problems where my mini-itx boards haven't loaded the generic kernel, but loads the 383 kernel
[11:06] <superm1> gardengnome, are they in ubuntu yet?
[11:06] <superm1> err 386 kernel :)
[11:06] <rogue780|mythser> I's about to say...I'd never heard of the 383
[11:07] <gardengnome> superm1: i think i saw them, but i'm not too sure. might have been universe
[11:07] <DaveMorris> yeah 386
[11:07] <superm1> i think they'd be more trouble than worth atm
[11:07] <superm1> maybe as a future option though
[11:07] <DaveMorris> and my main PC won;t boot a 386 kernel only the generic one
[11:08] <gardengnome> virtualbox won't boot those server kernels
[11:08] <gardengnome> ;)
[11:08] <superm1> oh really?
[11:08] <gardengnome> no
[11:08] <gardengnome> http://www.virtualbox.org/ticket/289
[11:08] <gardengnome> ^^
[11:19] <superm1> ah
[11:48] <superm1> keescook, could you comment at all about the source package naming in question in -motu at all given your core-dev and debianness?
[11:50] <keescook> superm1: one sec
[11:52] <keescook> superm1: I'm not able to follow the discussion, which package is in question?
[11:52] <superm1> http://revu.tauware.de/details.py?upid=5325 libhdromerun
[11:53] <superm1> its a package that was put up on revu, but the upstream package is named libhdhomerun.
[11:53] <superm1> the binary developed is hdhomerun-config
[12:04] <keescook> I would also recommend against libhdromerun, just to avoid confusion.  most packagers are expecting a lib* package to produce some .h and .a files, etc.
[12:04] <superm1> even though it will cause confusion with new versions?
[12:05] <keescook> what do you mean by new version confusion?
[12:06] <superm1> well when new versions of libhdhomerun are released, it would require renaming the upstream tarball again
[12:07] <keescook> well, you always have to rename the tarball -- no one releases with the suffix .orig.tar.gz.  Also, the version you're using is 0.{date}, but they use just {data} so you'd have to rename it for that too.
[12:07] <superm1> oh good point.
[12:07] <keescook> So, end of the day, I think it's worth naming it with a less confusing source package name
[12:08] <keescook> random other comments: I think you can leave lgpl.txt out of "docs" since you already mention where to find it in the copyright
[12:08] <superm1> well that has been an item of discussion
[12:08] <superm1> as crimsun had mentioned during mythbuntu-artwork-usplash
[12:08] <superm1> that a COPYING file
[12:08] <superm1> needs to be shipped *in* the package
[12:08] <keescook> ah, in that case, go with what the more experienced motus say.  :)
[12:08] <superm1> and contain the entire GPL or LGPL
[12:09] <keescook> great, the rest of the package looks fine.  nice and simple.  :)
[12:09] <superm1> yea, i'm really stating to love cdbs
[12:09] <superm1> i want to do more packages with it instead :)
[12:11] <keescook> I use it whenever I can.  Unfortunately the last few things have been totally insane stuff like lirc and apparmor.  :)
[12:12] <superm1> oh did you get lirc straightend out with a sru for that serial patch?