[00:10]  * hipitihop waves good morning to the residents
[00:14] <Seeker`> hi
[00:29] <phillip> hi all...audigy se sound card, HVR-1600, i'm not getting any audio passed from the tuner
[00:29] <phillip> i get audio from websites, but not tuner through mythtv or VLC...I'm running mythbuntu 9.10
[00:30] <jfry> is the audio being recorded?
[00:31] <jfry> And assuming it is, have you set your audio & mixer settings on the frontend
[00:32] <phillip> no, recordings do not have sound
[00:33] <phillip> and my channel scan is limited to 2-14, it's not picking up the rest of them
[00:33] <jfry> You tried to play one on a known working system or at least a working media player on that same machine?
[00:34] <phillip> I'm not getting audio from anything that comes through my tuner with anything on this machine
[00:36] <jfry> Source (digital, analog broadcast, Svideo, composite?
[00:36] <phillip> analog broadcast
[00:36] <phillip> streaming hulu works great
[00:37] <jfry> have you played any media in mythtv and had audio?
[00:38] <phillip> not besides hulu
[00:38] <phillip> i'm wondering if my DVD drive is crapping out on me too, it won't load a dvd into VLC
[00:39] <jfry> have you installed de-css?
[00:40] <phillip> no i haven't
[00:40] <jfry> I suspect that you need to check the audio configuration in mythtv... I am guessing that the audio is being captured with the video, but mythtv is not configured to output it to the right output.
[00:41] <phillip> the mythtv settings wouldn't affect the VLC would it?
[00:42] <jfry> You can install libdvdcss with mythbuntu control center.
[00:42] <phillip> i'm installing that now...thanks for the lead ;-)
[00:42] <jfry> and no, mythtv uses it's own internal media player (unless you configure it otherwise)
[00:44] <phillip> still not getting DVD playback through VLC..let me see if rebooting kicks in it gear
[00:44] <jfry> That should solve your dvd playback issue.  How are your speakers connected to the computer (analog, coaxial digital, optical)?
[00:45] <phillip> i'm getting MP3 playback
[00:45] <phillip> analog
[00:45] <jfry> getting mp3 playback in what app?
[00:45] <phillip> vlc
[00:46] <jfry> ok... so we know vlc is addressing the soundcard properly.  Have you tried to play one of your recording files in VLC?
[00:49] <phillip> excuse my ignorance, but where are my recordings stored?
[00:51] <phillip> nm
[00:53] <phillip> no audio from recording through VLC
[00:56] <jfry> interesting
[00:58] <jfry> your recording via the analog tuner on the card right... the encoder on the card should encode the audio right into the mpg file.... strange
[00:59] <jfry> I would check your settings in mythtv-setup as they relate to the tuner... perhaps you muted it accidentally?
[01:00] <phillip> checking now
[01:01] <phillip> on another note...what could cause my channels to stop at channel 14?
[01:01] <jfry> not exactly sure... are you connected to cable or an antenna?
[01:02] <phillip> cable
[01:02] <phillip> in looking through set up I didn't see anyway I could've muted it
[01:02] <jfry> What cable type are you using... IRC HRC Standard?
[01:03] <phillip> standard
[01:04] <jfry> Try changing it and rescanning ... I know it takes a while but it might solve both of your issues...
[01:06] <phillip> it freezes at channel 14 still
[01:06] <jfry> it freezes?
[01:07] <phillip> it stops scanning totally
[01:07] <jfry> your using us-cable-IRC, or us-cable-HRC, or even us-cable-standard and it freezes on channel 14 when scanning.
[01:07] <jfry> ?
[01:09] <phillip> i've tried channel frequency tables - try all - us-bcast - us-cable - us-cable-hrc - us-cable-irc
[01:09] <jfry> wierd
[01:09] <jfry> your doing a full scan right... not an update
[01:09] <phillip> correct
[01:10] <jfry> that is very strange
[01:11] <mrand> philip: using mythtv-setup?
[01:11] <phillip> yup
[01:12] <mrand> Ok, if you can't figure anything out, you can do the following to capture more logs and submit a bug:
[01:12] <mrand> sudo /etc/init.d/mythtv-backend stop
[01:12] <mrand> and then
[01:12] <mrand> sudo mythtv-setup.real --verbose channelscan,siparser,channel,record,extra > mythtv-setup.log
[01:12] <mrand> replace "stop" with "restart" to relaunch the backend
[01:13] <jfry> I'm at a loss..  thanks for taking over mrand... he's got two major issues, possibly related..  1. can't scan past channel 14, 2. no audio is being recorded.
[01:14] <jfry> If I had to guess, though I'd probably be wrong, I'd say firmware for the capture card.
[01:14] <phillip> this HVR-1600 has been nothing but a headache
[01:16] <ripperda> so I haven't had a lot of luck today; I have ripped a dvd to .iso and transcoded to .avi, but mythvideo still can't find any videos
[01:16] <ripperda> I've also tried increasing the mythtvfrontend verbosity, but didn't see anything that stood out
[01:17] <ripperda> there must be some way of identifying what subdirectory mythvideo is looking at for the videos, whether via verbose output or even direct mysql itself, no?
[01:17] <jfry> phillip: I'm not sure how current this is, but did you see: http://www.mythtv.org/wiki/Hauppauge_HVR-1600
[01:18] <jfry> ripperda, yeah... check the mythvideo setup.
[01:18] <jfry> ripperda, and it will play .iso files directly, no need to transcode
[01:18] <ripperda> jfry, any help would be appreciated, but I did work on this a little with superm1 and mrand earlier today
[01:18] <ripperda> so here's a little background:
[01:18] <phillip> i've almost memorized that page, the firmware files loaded w/ 9.10 install are the same as the ones you download from the link there
[01:19] <jfry> k
[01:19] <ripperda> I installed mythbuntu, but changed the paths (for all media) to /home/mythtv/<directory>, due to partition layout and having a much larger /home partition
[01:20] <jfry> ripperda, I do the same thing on my setups
[01:20] <ripperda> I've manually changed the directories in the backend (via mythtv-setup, storage directories), as well as the frontend, via the mythvideo setup pages
[01:20] <ripperda> but for some reason, mythtv refuses to find any videos
[01:20] <ripperda> I did double check the permissions and that my own user account can see & access the files
[01:21] <ripperda> superm1 suggested disabling storage groups on the backend, so I've deleted the video storage directory on the backend, but have set the path in the frontend
[01:21] <jfry> try opening video manager once... it will scan for video files and add them to the database
[01:22] <jfry> ripperda, the mythtv-setup has nothing to do with mythvideo
[01:22] <jfry> utilities -> video manger  (that's the usual place for it)
[01:23] <ripperda> jfry, thanks, I'm learning :)
[01:23] <ripperda> ok, opened video manager, said no files found. I then used 'm' to pull up the menu and told it to scan
[01:23] <ripperda> it claimed nothing found, but now I'm seeing things in the mythvideo section.
[01:24] <ripperda> I see 18 files, I think a lot of those are from a dvd I previously grabbed all VOBs from
[01:24] <ripperda> let me play with this, but it looks like that worked
[01:24] <jfry> ripperda, also, in the mythvideo setup... general settings, there is a "newly scanned files are browsable by default" option... check it and it will scan and add files every time you open your videos menu.
[01:27] <ripperda> excellent, thanks jfry. playing back my video now, time to play around with things
[01:27] <ripperda> much thanks
[01:28] <jfry> phillip, did you see: http://ubuntuforums.org/showthread.php?t=1142113
[01:28] <jfry> ripperda, glad to hear it
[01:29] <mrand> sorry, gotta go eat.  bbl
[01:32] <phillip> jfry...those settings are exactly how i have mine set up
[01:32] <phillip> oh well...i'm gonna step outside...i'll bbs
[01:33] <jfry> take care
[01:33] <superm1> ripperda, if you are still having troubles, ask iamlindoro in #mythtv-users for some more help
[01:35] <ripperda> thanks superm1, I think the scanning option in video manager seems to have resolved the problem
[01:36] <superm1> ripperda, that's the same option as if you scan from "watch videos"
[01:36] <superm1> just need to remember to leave the plugin for 5 seconds and come back
[01:37] <ripperda> ok, I must not have scanned properly. thanks for the help. I'll play around with things a lot and will probably be back on and off over the next few weeks with more questions
[01:38] <ripperda> thanks much for the help and all the hard work of putting this together in the first place
[01:38] <jfry> ripperda, welcome to mythtv... been on it for 5 years (really that long?) and I can't imagine being without.
[01:40] <jfry> of course I'm a set it and forget it... so everytime a new release comes out I have to relearn everything
[01:47] <phillip> superm1...i'm still having issues w/ the HVR-1600
[01:47] <phillip> blah
[01:50] <mrand> phillip, you talking about your channel scan issue?
[01:50] <mrand> I'm back for a just a sec
[01:50] <phillip> channel scan and lack of audio thru my tuner card
[01:51] <phillip> my firmware files match the ones listed in the mythtv wiki on the HVR-1600 and i've tried every tuner card type option available
[01:52] <mrand> I assume dmesg shows things are ok at bookup?
[01:52] <phillip> yes sir
[01:53] <scovel> Running the latest Mythbuntu 9.10 Beta, with updates.  Seeing some weird socket timeouts from the frontend.  MythSocket(a0dd228:40): readStringList: Error, timed out after 7000 ms.  RemoteFile::openSocket(control socket), Error: Failed to open socket, timeout
[01:57] <mrand> phillip, despite me pushing around a bunch of dvb bugs, I don't know much about them (I capture analog off a cable box), so I'm going to have to defer to collecting the log info above.
[01:58] <mrand> you could try mythtv-users thought
[01:58] <mrand> rather, #mythtv-users though.
[01:58] <mrand> Or the ubuntu forums, or the mythtv-users mailing list.
[01:59] <phillip> thanks mrand...i'm thinking i'll try 9.04...i know the HVR-1600 has worked in them
[01:59] <mrand> Or searching the above two for similar problems.  The last few lines (before it hangs) of the mythtv-setup.log file should hopefully contain some hints on what to search for.
[01:59] <mrand> phillip, actually that might be helpful.
[01:59] <mrand> If you can try 0.22 on 9.04, that would let us know if it is a mythtv problem, or a ubuntu related problem.
[02:00] <phillip> is it possible to use multiple hdd's in 9.04?
[02:01] <mrand> hdd = hd-homerun?
[02:01] <phillip> multiple hard drives
[02:01] <mrand> I'm certainly not aware of any reason you can't.  Did you have some concern in particular about it?
[02:02] <mrand> scovel: is that a remote front-end?  You said updates... I assume that means you're running 223xx or newer?
[02:02] <phillip> i'm still soaked behind the ears when it comes to mythtv and ubuntu, but my buddy said it was hard to get mythbuntu to use multiple harddrives in previous versions
[02:03] <scovel> yes, a remote frontend.
[02:03] <scovel> MythTV Version   : 22359
[02:03] <scovel> MythTV Branch    : trunk
[02:03] <scovel> Network Protocol : 50
[02:03] <scovel> Library API      : 0.22.20091008-1
[02:03] <scovel> QT Version       : 4.5.2
[02:04] <mrand> phillip, the only thing I can even possibly imagine is either ext4 related issue, or storage group stuff (which was expanded for 0.22, and has nothing to do with 9.04 vs. 9.10).  In general you should be fine.
[02:04] <mrand> scovel, there were a number of socket bugs fixed, but you're current, so anything you're seeing is either (1) bug, (2) config problem (3) network problem.
[02:05] <phillip> can i run ext4 in 9.04?
[02:05] <mrand> Yes, although it wasn't the default filesystem.
[02:06] <phillip> i'm guessing it's the default in 9.10
[02:06] <mrand> I'm not aware of any particular issues with ext4, but I haven't looked into it at all either.
[02:06] <scovel> (1) probably (2) backend has been around for sometime.  local frontend is fine. (3) possible, I'll run a couple ftps and nfs tests and see what's what.
[02:07] <mrand> phillip - yes, I believe that it is, at least on standard Ubuntu installs.
[02:07] <mrand> scovel, there are probably some verbose flags you can throw at frontend and backend to capture more info regarding sockets.
[02:07] <mrand> I'll bbl.
[02:07] <phillip> thanks again mrand!
[02:12] <scovel> got to figure out where to do that.  9.10 and upstart take some getting used to.  Everything has moved just a little bit.
[02:22] <hipitihop> eek, going backwards here... this mornings update && upgrade ... now forntend displays "This application not compatible with installed MythTV libraries. Recompile after doing a make distclean" ???
[02:23] <scovel> stupid updates held back some files.  do "apt-get dist-upgrade"
[02:24] <scovel> same thing happened to me
[02:25] <scovel> hipitihop, that was for you.  MythTV experienced, IRC noob...
[02:28] <hipitihop> scovel: will have a look, I have had some held back for couple of days but was told here not to do dist-upgrade if it wants to remove anything and yesterday it did want to...checking now
[02:31] <hipitihop> scovel: dist-upgrade looks better this morning, only want to remove a couple of themes which looks harmless
[02:32] <scovel> hipitihop:  some of the themes are obsolete anyway.  I think yesterday sometime it upgraded libmyth but held back some of the plugins, causing the errors.
[02:32]  * hipitihop has dist-upgrade running, fingers crossed
[02:37] <hipitihop> I wonder if anyone knows how to get rid of small vertical border on my display. Using HDMI output to an LG50" Plasma. it is a HDMI -> HMDI connection but I get 2-3 pixel vertical border on left and right of display.
[02:38] <scovel> hiptihop -  there is a built-in utility to adjust the screen size.  Its somewhere under setup.  Have you tried that
[02:50] <scovel> mrand, network seems fine.  Transferring at 2.5MB/s over wireless.
[02:50] <hipitihop> scovel: the one that places arrows in corner of screen, yes but I don't quite know how to use that via keyboard (remote still not functional) so I only seem to be able to effect the top left corner
[02:52] <scovel> hipitihop: that can be a problem.  The screen tells you the names of the functions to switch from UL to BR.  You can probably look up they keyboard shortcuts for those.  What does it say to use to switch?
[02:57] <hipitihop> scovel: btw that dist-upgrade seems to have sorted things (although sounds is now broke so I'll investigate)
[02:57] <hipitihop> scovel: as for the screen stuff... I suspect it is something lover level as the broders are visible while grub is loading
[02:58] <scovel> hipitihop:  there's always one more thing to look into.
[02:58] <hipitihop> scovel: anyweay thanks for the dist-upgrade tip,
[02:58] <hipitihop> scovel: waht timezone re you in ?
[02:59] <scovel> hiptihop: HDMI is beyond my financial means ATM.  Still analog myself.  S-Video.  Maybe someday.
[02:59] <scovel> hiptihop: Eastern Standard
[03:06] <scovel> mrand:  with network,socket,extra I get this:
[03:06] <scovel> 2009-10-12 22:05:12.781 MythContext: Connecting to backend server: 10.10.20.20:6543 (try 1 of 1)
[03:06] <scovel> 2009-10-12 22:05:12.781 MythSocket(a3e01b0:25): new socket
[03:06] <scovel> 2009-10-12 22:05:12.782 MythSocket(a3e01b0:25): attempting connect() to (10.10.20.20:6543)
[03:06] <scovel> 2009-10-12 22:05:12.785 MythSocket(a3e01b0:25): state change Idle -> Connected
[03:06] <scovel> 2009-10-12 22:05:12.785 MythSocket(a3e01b0:25): write -> 25 21      MYTH_PROTO_VERSION 50
[03:06] <scovel> 2009-10-12 22:05:12.785 MythSocket(a3e01b0:25): writeBlock(0x175520832, 29)
[03:06] <scovel> 2009-10-12 22:05:19.787 MythSocket(a3e01b0:25): readStringList: Error, timed out after 7000 ms.
[03:06] <scovel> 2009-10-12 22:05:19.787 MythSocket(a3e01b0:25): state change Connected -> Idle
[03:06] <scovel> 2009-10-12 22:05:19.788 MSocketDevice::close: Closed socket 25
[03:06] <scovel> 2009-10-12 22:05:19.788 Protocol version check failure. The response to MYTH_PROTO_VERSION was empty.
[03:06] <scovel> 2009-10-12 22:05:19.788 MythSocket(a3e01b0:-1): DownRef: -1
[03:06] <scovel> 2009-10-12 22:05:19.788 MythSocket(a3e01b0:-1): delete socket
[03:11] <mrand> Hate that error.
[03:11] <mrand> :-)
[03:12] <mrand> Anything on the backend side?
[03:12] <scovel> :'(
[03:12] <scovel> I was just going to ask you where the hell the log file went for the backend.
[03:12] <Zinn> scovel: Please watch your language.
[03:13] <scovel> oooo, do you know me?
[03:13] <mrand> go away Zinn, he's frustrated.
[03:13] <mrand> Zinn is a bot.
[03:13] <scovel> ah, I see
[03:13] <scovel> !@#@#$ bot
[03:13] <mrand> !zinn
[03:13] <mrand> !help
[03:13] <Zinn> Sorry I don't know about @#@#$ bot
[03:13] <Zinn> see !about
[03:13] <Zinn> !help For a  complete list of my knowledge visit: http://www.baablogic.net/Zinn.cgi  Other available commands: !status, !about, !bug [bug_number].
[03:14] <scovel> I'm looking in /var/log/mythtv/mythtvbackend.log and nothing has changed for over 12 hours.  Restarted the backend too
[03:16] <mrand> That would explain why the backend is not responding... it isn't running?  ps -ef?
[03:16] <scovel> yeah, it's running.  The frontend even got a list of recorded shows once.  Big dump in the logfile.
[03:17] <mrand> hrmmm
[03:18] <scovel> where are the upstart scripts?  I don't get upstart yet.
[03:18] <superm1> scovel, there was something wrong with yesterday's package
[03:18] <superm1> it didn't update /etc/default/mythtv-backend
[03:18] <superm1> you can manually fix it by overwriting it with the one form the bzr branch
[03:19] <superm1> that will fix logging
[03:19] <scovel> "bzr branch" ???
[03:19] <superm1> http://bazaar.launchpad.net/~ubuntu-mythtv/mythtv/mythtv-trunk-022/annotate/head%3A/debian/mythtv-backend.default
[03:19] <superm1> hit download file
[03:19] <superm1> and overwrite /etc/default/mythtv-backend with that file
[03:20] <mrand> Or he can wait until tomorrow?
[03:20] <superm1> Yeah
[03:20] <superm1> i'm manually doing a push since daviey messed up the cleanup / push action last night
[03:21] <scovel> that's easy enough.  Let me see what we get now
[03:22] <scovel> ok, I see new logging.  Let me try to connect
[03:24] <scovel> got this right away, before I even tried to connect:
[03:24] <scovel> 2009-10-12 22:21:19.339 Connecting to master server: 10.10.20.20:6543
[03:24] <scovel> 2009-10-12 22:21:19.342 Connected successfully
[03:24] <scovel> 2009-10-12 22:21:49.345 MythSocket(84ea1e8:19): readStringList: Error, timed out after 30000 ms.
[03:24] <scovel> 2009-10-12 22:21:49.348 MainServer, Error: Failed to open master server socket, timeout
[03:24] <scovel> 2009-10-12 22:21:49.353 adding: mythbuntu as a slave backend server
[03:24] <scovel> 2009-10-12 22:21:49.358 MainServer, Warning: Unknown socket closing MythSocket(0x84ea1e8)
[03:24] <scovel> 2009-10-12 22:21:49.362 MythSocket(84ea1e8:-1): writeStringList: Error, socket went unconnected.
[03:24] <scovel>                         We wrote 0 of 10 bytes with 1 errors
[03:24] <scovel> 2009-10-12 22:21:50.351 Connecting to master server: 10.10.20.20:6543
[03:24] <scovel> 2009-10-12 22:21:50.355 Connected successfully
[03:24] <scovel> 2009-10-12 22:22:20.360 MythSocket(8503fd8:19): readStringList: Error, timed out after 30000 ms.
[03:24] <scovel> 2009-10-12 22:22:20.363 MainServer, Error: Failed to open master server socket, timeout
[03:24] <scovel> 2009-10-12 22:22:20.368 adding: mythbuntu as a slave backend server
[03:24] <scovel> 2009-10-12 22:22:20.372 MainServer, Warning: Unknown socket closing MythSocket(0x84f7808)
[03:24] <scovel> 2009-10-12 22:22:20.375 MythSocket(84f7808:-1): writeStringList: Error, socket went unconnected.
[03:24] <scovel>                         We wrote 0 of 10 bytes with 1 errors
[03:25] <tgm4883> !pastebin | scovel
[03:25] <scovel> oh no.  IRC protocol.  Someone explain?
[03:25] <mrand> Ignore that.
[03:25] <Zinn> scovel: 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.
[03:26] <scovel> k :-[
[03:26] <mrand> scovel: sounds like your system got confused and something thinks it is a slave backend.
[03:26] <mrand> Go into mcc and make sure that the remote front end is configured as a remote front end, and the back end is configured as a _master_ backend.
[03:26] <scovel> that did look weird now that I see that
[03:27] <tgm4883> where is Zinn?
[03:27] <tgm4883> fricking slow bot
[03:28] <scovel> backend is running ubuntu server
[03:29] <scovel> no mcc
[03:30] <mrand> ok.  You mean mythtv-backend-master package?
[03:31] <scovel> mcc for the frontend says "no backend" and "desktop frontend"
[03:31] <scovel> actually I mean it's running ubuntu server, not Mythbuntu.
[03:31] <scovel> ask opposed to ubuntu desktop
[03:31] <mrand> I understand.  Did you use the Ubuntu packages to install the backend?  If so, it should be -master
[03:32] <scovel> I did.  It has been the master backend for year(s)
[03:32] <scovel> I did upgrade it to 9.10 Beta though
[03:33] <mrand> what does this command spit out? apt-cache policy mythtv-backend-master
[03:33] <mrand> My upgrade got confused and I didn't have a -master
[03:34] <scovel> mythtv-backend-master:
[03:34] <scovel>   Installed: (none)
[03:35] <scovel>   Candidate: 0.22.0~trunk22359-0ubuntu1
[03:35] <scovel> this is new territory for me, and I used Gentoo for years...
[03:35] <mrand> same problem as me.
[03:35] <mrand> You can use aptitude or apt-get, but you need to install -master
[03:35] <mrand> Or synaptic.
[03:36] <scovel> apt-get install mythtv-backend-master?
[03:36] <mrand> sudo  ^^^^^
[03:36] <mrand> yes
[03:36] <scovel> sudo su
[03:37] <scovel> sudo make me a sandwich
[03:37] <scovel> I love that comic...
[03:37] <scovel> It's installing.
[03:38] <mrand> sorry, don't know the comic
[03:39] <tgm4883> mrand, xbcd?
[03:39] <tgm4883> xkcd
[03:39] <tgm4883> http://xkcd.com
[03:39] <mrand> Oh, I know xkcd.
[03:39] <mrand> Great stuff
[03:39] <tgm4883> !sudo
[03:39] <Zinn> Sorry I don't know about sudo
[03:40] <mrand> !learn xkcd http://xkcd.com
[03:40] <Zinn> Sorry I don't know about learn xkcd http://xkcd.com
[03:40] <tgm4883> http://xkcd.com/149/
[03:40] <tgm4883> @learn sudo - http://xkcd.com/149/
[03:40] <Zinn> I just learned: sudo - http://xkcd.com/149/
[03:41] <mrand> I missed and/or forgot that one.
[03:43] <scovel> this isn't good
[03:43] <scovel> 2009-10-12 22:42:59.638 MythBackend: Running as a slave backend.
[03:43] <scovel> 2009-10-12 22:42:59.665 MythBackend, Error: No valid capture cards are defined in the database.
[03:43] <scovel>                         Perhaps you should re-read the installation instructions?
[03:44] <scovel> eventually it gets to this: 2009-10-12 22:43:01.543 Connecting to master server: 10.10.20.20:6543
[03:44] <scovel> 2009-10-12 22:43:01.547 Connected successfully
[03:44] <mrand> why does it still say slave?  You might need to reboot.
[03:44] <scovel> reboots are for adding hardware....
[03:44] <mrand> or stop and restart mythbackend anyway
[03:45] <scovel> I'll give it a shot.
[03:45] <scovel> I did stop/restart at least 2X
[03:45] <hipitihop> I'm still getting upgrade problem for nfs-coomon etc can someone have a look pls here is output http://paste.ubuntu.com/292032/
[03:47] <mattwj2002> hey guys
[03:47] <mattwj2002> I found a weird bug with mythbuntu 9.10 beta
[03:48] <mattwj2002> I literally hear my optical mouse
[03:48] <mrand> Turn your speaker down?  :-)
[03:48] <superm1> i smell color too :)
[03:48] <mrand> Or Up.  One or the other.
[03:49] <mrand> Is it an older computer?
[03:49] <mattwj2002> nope
[03:49] <mattwj2002> it is a quad core
[03:49] <mattwj2002> :)
[03:50] <mattwj2002> if I unplug the mouse the noise goes away
[03:50] <mattwj2002> any idea how to get rid of it?
[03:50] <mrand> So it wasn't there in 9.04?
[03:50] <mattwj2002> to be honest I am not sure
[03:50] <mattwj2002> I jumped from 8.10 to 9.10
[03:50] <mattwj2002> did a fresh install
[03:51] <mrand> ah.  Same but different - no noise on 8.10
[03:51] <mrand> I know... it must be the fault of pulse audio.  That's the big difference.
[03:51] <mattwj2002> no problem in 8.10
[03:51] <mrand> :-)
[03:52] <mattwj2002> can I uninstall pulse audio?
[03:52] <mattwj2002> do I need it?
[03:52] <mattwj2002> for audio?
[03:52] <mrand> that's debatable.
[03:53] <mrand> pulse audio is the future of Linux sound.  Ubuntu has has some trouble implementing it though.  I was mostly joking - it's just that PA is the source of multiple headaches
[03:54] <scovel> so, what's this all about?
[03:54] <scovel> No UPnP backends found
[03:54] <scovel> Would you like to configure the database connection now? [no]
[03:54] <scovel> [console is not interactive, using default 'no']
[03:55] <mrand> scovel: check out http://www.bramkortleven.be/?p=131
[03:56] <mattwj2002> mrand
[03:57] <mattwj2002> is there a way to switch back to alsa?
[03:58] <mrand> yes... please hold
[03:58] <mattwj2002> okay thank you
[04:00] <scovel> looking better.....
[04:01] <mrand> mattwj2002: still looking.
[04:02] <mrand> !stab launchpad, for being slow
[04:02]  * Zinn stabs launchpad with a sharpened mce remote, for being slow.
[04:03] <scovel> mrand, dude, you made my night.  No more slavery, no more socket errors!  The kids can watch Clone Wars in the morning.
[04:03] <mrand> *phew*
[04:03] <mrand> Glad we got it, scovel.
[04:04] <scovel> I had about 5 mysql.txt files laying about.  I hope things clear up before the final version is out, or you are going to be busy!
[04:05] <scovel> now to get lirc going....tomorrow I think.  Bed time.
[04:05] <mrand> no kidding.  Me too!
[04:05] <mrand> lirc... oh man....
[04:05] <mrand> wait for the weekend to do your next update
[04:05] <mrand> if this system is to be used by the kids
[04:05] <scovel> thanks for the advice
[04:05] <mrand> big change going in tonight.  We're crossing our fingers.
[04:05] <scovel> wife and kids mad for 3 weeks.
[04:06] <mrand> hahah  tell them sorry!
[04:06] <scovel> you can read my post on mythbuntu forum about getting VDPAU working, and CPU scaling issues.
[04:06] <mrand> man... you've had it rough.
[04:06] <scovel> stupid CPU scaling....
[04:06] <scovel> ok, have a good one.  later
[04:07] <mrand> have fun!
[04:07] <mattwj20021> mrand did you find anything?
[04:08] <mrand> Believe it or not, I'm still looking for this one thing in particular.  It was a thread that I found before on the forums.  I hope I'm getting close.
[04:10] <mattwj20021> ok
[04:14] <mrand> I can't believe I can't find it right now.  I usually have good google-fo.
[04:14] <mrand> are you running gnome or xfce?
[04:17] <mrand> sorry, there are a number of threads, but most are older and aren't geared for 9.10, which does things somewhat differently (especialy gnome).  I'm not really recommending you disable/remove it.  But if you do, make sure you follow recent directions (for 9.10).  I gotta run.
[04:21] <mattwj2002> I am running xfce
[04:22] <mrand> (10:17:30 PM) mrand: sorry, there are a number of threads, but most are older and aren't geared for 9.10, which does things somewhat differently (especialy gnome).  I'm not really recommending you disable/remove it.  But if you do, make sure you follow recent directions (for 9.10).  I gotta run.
[04:24] <mattwj2002> okay thanks anyways mrand
[04:24] <mattwj2002> :)
[04:25] <tmkt> anyone have gmythmovies_0.3d.pl?
[04:25] <tmkt> web site doesn't seem to work anymore
[05:04] <foxbuntu> tmkt, not familiar with that script, what was it for?
[05:05] <tmkt> to get movise listings
[05:05] <tmkt> from google
[05:05] <tmkt> since the current movie listings in mythv don't work for canadians or anyone outside the US
[05:05] <foxbuntu> ah
[05:06] <tmkt> had it before...but the site that provided it..doesn't seem to anymore
[05:06] <foxbuntu> what seems to be the issue with the script?
[05:06] <foxbuntu> oh
[05:09] <foxbuntu> yeah..Im not finding it eiter
[05:09] <foxbuntu> mythmovies doesnt support outside the US?
[05:10] <foxbuntu> tmkt, what version of MythTV are you using?
[05:11] <foxbuntu> tmkt, you might want to try this out: http://www.gossamer-threads.com/lists/mythtv/users/336179
[05:14] <puff> Hi, I have a fairly new mythbuntu box.  I also have an extra 1TB SATA drive that I want to install in it.
[05:15] <puff> It wouldn't be a big deal to just reinstall mythbuntu, since there's almost nothing on the box now, but is there an easy way to just add the new drive to mythbuntu?
[05:17] <foxbuntu> puff, its actually quite easy to setup a new disk
[05:18] <foxbuntu> puff, this is assuming you know the hardware side of installing the disk
[05:21]  * foxbuntu waits for puff to reply
[05:32] <puff> foxbuntu: sorry, I was off elsewhere.
[05:32] <foxbuntu> puff, np
[05:32] <puff> foxbuntu: Well the hardware side should be pretty straightforward, though this is my first SATA disk.
[05:32] <puff> Power cable, data cable, right?
[05:33] <puff> I need to find a mounting kit, apparently this drive didn't come with one, but until then I think it should be safe to just set it on top of the existing drive.
[05:33] <foxbuntu> puff, yes, just don't want you to break your system doing something you are not comfortable with
[05:34] <puff> No sweat... I don't mess with hardware too often, but unless there are some gotchas, I should be fine.
[05:34] <foxbuntu> ok
[05:34] <puff> An example of a gotcha, albeit one you're not likely to run into these days:  do NOT try to install an MFM and IDE drive controller in the same machine.
[05:34] <puff> They do not play well with each other.
[05:34] <foxbuntu> well if you get the drive in the system and booted back up I would be glad to walk you through creating the partition and mounting it
[05:34] <puff> Cool.
[05:35] <puff> One sec while I go down to the TV room.
[05:39] <puff> Argh, make that one minute, I just realized I left the car blocking the driveway.
[05:54] <puff> Okay, back, phew.  I love where I live, but it does have its drawbacks.
[06:02] <foxbuntu> puff, alright, got your system prep'd?
[06:11] <puff> Okay, all plugged in.  That was, like much in my life, too much trouble.
[06:12] <puff> Is location on the power cable significant?
[06:12] <puff> (He says, hoping the answer is "no")
[06:13] <puff> Booting it back up now.  Do I need to unplug the video out to get it ot use this LCD screen (the TV screen is kinda hard to see from the keyboard).
[06:14] <puff> I really need to reorganize this stuff, which will happen once everything is running smoothly.
[06:14] <foxbuntu> puff, yes, if you booted with the TV the last time it will require you o unplug the tv
[06:15] <foxbuntu> puff, and what do you mean by, "location of the power cable" ?
[06:17] <puff> Location _on_ the power cable... probably irrelevant, I think I was remembering older systems where each plug on the ribbon cable had a specific identity, e.g. the primary drive, the one the machine booted from, was the first plug, etc.
[06:17] <puff> Speaking of which, I suspect I'll have to enter cmos and change the boot order...
[06:18] <foxbuntu> puff, not the case with SATA
[06:18] <foxbuntu> puff, SATA drive priority is determined by the slot you plug it into, much like SCSI ID used to be but easier
[06:18] <puff> Hm,odd.  In the BIOS it... ah.
[06:19] <puff> Okay, then I need to power down and swap the data cables around.
[06:19] <foxbuntu> puff, unless the other drive is IDE (PATA)
[06:19] <puff> Because now, although the bios shows both drives, in the boot device priority list,it only shows the new drive.
[06:21] <foxbuntu> puff, also, if you are directing something in IRC to me, please type my name first, it helps me know when you say something as I am flipping back and fourth between channels/screens
[06:21] <puff> foxbuntu: Okay.  I have an asus p4p800s-x with american megatrends bios.
[06:21] <foxbuntu> puff, alright (not that I know what is in the BIOS) but what type of drive is the other HDD you already had in there?
[06:21] <foxbuntu> is it also sata?
[06:22] <puff> foxbuntu: The bios menu has a boot screen, on the boot screen there are four entries: Boot device priority, hard disk drives, boot settings configuration, security.
[06:23] <puff> Looks like a seagate:  4m-st3250823AS
[06:23] <foxbuntu> puff, I meant Type as in IDE/SCSI/SATA ?
[06:24] <puff> On the "hard disk drives" screen it lists "1st drive, 3M-Hitachi-HDT7210" and "2nd Drive 4M-st3250823AS"
[06:24] <puff> Googling on the second string seemsto indicate seagate SATA 250GB, which sounds right.
[06:24] <puff> And I know the new drive is a hitachi, so.
[06:24] <foxbuntu> puff, ok, so SATA
[06:24] <foxbuntu> puff, if you go to the boot prioity screen
[06:25] <foxbuntu> usually  you can arrow down into the list, hit enter, and the other drive should be in the list
[06:25] <foxbuntu> then you can just select it
[06:25] <puff> It says "1st Boot Device:  1st FLOPPY DRIVE", "2nd Boot Device: 3M-Hitachi HDT7210", "3rd Boot Device:  SM-_NEC DVD_RW ND"
[06:25] <foxbuntu> (hit enter in the spot you want to have that drive boot)
[06:26] <foxbuntu> hit enter on the Hitachi drive
[06:26] <puff> When I select any of these devies, it pops up a menu listing the three devices, no seagate drive on it.
[06:26] <puff> Options popup, listing  "1st:  1st FLOPPY DRIVE", "2nd 3M-Hitachi HDT7210", "3rd SM-_NEC DVD_RW ND", "Disabled"
[06:27] <foxbuntu> hmm
[06:27] <foxbuntu> let me see if I can find the info
[06:28] <puff> Well, it should be fairly quick to power down and swap the data cables and try, right?
[06:29] <foxbuntu> did you swap them when you installed this drive?
[06:30] <puff> Possibly... had to root around in the cables a fair bit.
[06:30] <foxbuntu> lets put it this way: the boot drive should be in plug 0 and the secondary in plug 1
[06:30] <puff> Got it.
[06:31] <puff> Turns out that the hard disk drives menu lets you select which is first and second.
[06:31] <puff> And only the selectd-as-first shows up in boot priority menu.
[06:31] <foxbuntu> ah
[06:31] <puff> Bingo, booting properly now.
[06:31] <foxbuntu> I kind of assumed that but wanted to see what the menus looked like
[06:32] <foxbuntu> good
[06:32] <foxbuntu> I actually have the mobo manual for that now
[06:32] <foxbuntu> lol
[06:32] <puff> Heh.
[06:32] <foxbuntu> thats an old mobo isnt it
[06:32] <puff> One problem is that the only convenient power source for this box is wired to a wall switch, so it has to be feasible to shut it off eaisly.
[06:33] <puff> Two years ago it was fairly bleeding edge, but reliable.
[06:33] <puff> E.g. not so bleeding edge that it didn'thave a good track record.
[06:33] <foxbuntu> yea
[06:33] <foxbuntu> guess its not that old
[06:33] <foxbuntu> just seems that way
[06:33] <foxbuntu> heh
[06:33] <puff> Anyway, is there a way to set it up to make it easy/qiuck to shut it down?
[06:33] <foxbuntu> yes
[06:33] <foxbuntu> mythwelcome
[06:34] <foxbuntu> and irexec from a remote
[06:34] <puff> Hm, it did a filesystem check, found some errors, corrected them, requested a reboot, rebooted, now the screen has been blank for a wihle.
[06:34] <foxbuntu> but I dont have time to explain all that tonight
[06:34] <puff> I don't have a cable cpature card or remote yet, so no worries.
[06:34] <puff> I'm using it solely for video out.
[06:35] <puff> My friend is recommending an HD Home Run ethertuner.
[06:35] <foxbuntu> they work very well
[06:35] <foxbuntu> I own one
[06:35] <puff> Screenis sitll blank... now what?
[06:35] <foxbuntu> did it actually reboot?
[06:35] <foxbuntu> did you see the bios splash?
[06:35] <puff> It said it was going to reboot, then the screen went blank, it beeped, etc.
[06:36] <puff> Ah, no, I don't htink I saw the bios splash, so... hard reboot?
[06:36] <foxbuntu> power cycle it
[06:36] <puff> Booting properly now.
[06:36] <foxbuntu> ok
[06:37] <puff> This box is both backend and frontend at the moment, though it's entirely possible/likely that we'll have oher frontends throughout the house.
[06:38] <puff> And I'd like it to be easy for my roommates to tune in from their PCs.
[06:38] <foxbuntu> thats no problem
[06:38] <puff> Hm, screen went blank again.
[06:38] <puff> Still powered up but the power button is orange.
[06:39] <foxbuntu> sounds like X is not starting
[06:39] <puff> i.e. power is on but no video signal.
[06:39] <foxbuntu> push ctrl+alt+f1
[06:39] <puff> Hnmm, yup, ctrl-alt-shift-f1 gets me a cosnole.
[06:40] <foxbuntu> ok
[06:40] <foxbuntu> well one thing at a time
[06:40] <foxbuntu> lets get your disk added because that pretty easy
[06:40] <puff> Cool.
[06:40] <puff> Login, I presume?
[06:40] <foxbuntu> yup
[06:41] <puff> Okay, now?
[06:41] <foxbuntu> alright
[06:41] <foxbuntu> I need the output of this: ls /dev/sd*
[06:42] <foxbuntu> essentially you should see several /dev/sda1 2 5 (ect)
[06:43] <foxbuntu> then there should be one, /dev/sdb (no number)
[06:43] <foxbuntu> is that correct?
[06:44] <puff> sda, sdb, sdb1, sdb2, sdb5, sdb6
[06:44] <foxbuntu> hmm
[06:44] <foxbuntu> looks like your sata cables are backwards
[06:45] <foxbuntu> ts alright though
[06:45] <foxbuntu> do this: sudo fdisk /dev/sda
[06:45] <foxbuntu> n
[06:45] <foxbuntu> p
[06:45] <foxbuntu> 1q
[06:45] <foxbuntu> er
[06:45] <foxbuntu> 1
[06:45] <foxbuntu> [enter] (for defaults)
[06:46] <foxbuntu> [enter] (for defaults)
[06:46] <foxbuntu> w
[06:46] <foxbuntu> q
[06:46] <foxbuntu> that should be all the commands
[06:46] <foxbuntu> ignore 1q and er
[06:46] <puff> right.
[06:47] <puff> I'm not entirely inexperienced, but I don't fdisk drives very often.
[06:47] <foxbuntu> np
[06:47] <puff> Looks good.  "The partition table has been altered!  Calling icotl() to re-read partition table.  Syncing disks."
[06:48] <foxbuntu> everyone's level of expertise is different so I try to offer basic advice, don't take it personal
[06:48] <puff> I really gotta get a cat5 cable strung down to this box.
[06:48] <puff> Cool, not a problem.
[06:48] <foxbuntu> alright
[06:48] <puff> In case it wasn't apparent, I very much appreciate the help.
[06:48] <foxbuntu> so you should be back at the command prompt
[06:48] <puff> yup.
[06:49] <foxbuntu> so now: sudo mkfs.ext4 /dev/sdb1
[06:49] <foxbuntu> well
[06:49] <puff> It's mounted.
[06:49] <foxbuntu> that assumes you are using the Mythbuntu 9.10
[06:49] <puff> Pretty recent, lemme check.
[06:50] <foxbuntu> lsb_release -a
[06:50] <puff> 9.0.4
[06:50] <foxbuntu> alright
[06:50] <foxbuntu> mounted?
[06:50] <puff> Yup. "/dev/sdb1 is mounted: will not make afilesystem here!"
[06:50] <foxbuntu> oh craps
[06:50] <puff> Shoud it be sda?
[06:51] <foxbuntu> I meant: sudo mkfs.xfs /dev/sda1
[06:51] <puff> Righto.
[06:51] <foxbuntu> since you are on 9.04
[06:51] <puff> Thar she goes.
[06:51] <foxbuntu> it shouldnt take long
[06:51] <foxbuntu> couple of moments
[06:51] <puff> Yeah, I've had thoughts about putting together an ubuntu "usability pakage" which would just override certain commands with some friendlier behaviors..
[06:52] <puff> Sort of like how bash now suggests installing the appropriate package if you try a command tht isn't there.
[06:53] <foxbuntu> thats what tab complete is for
[06:53] <foxbuntu> and man pages :)
[06:53] <foxbuntu> or when those fail, google
[06:53] <foxbuntu> heh
[06:54] <puff> Eh, I can't think of many of the issues off the top of my head, I have a file ofnotes somewhere.
[06:54] <foxbuntu> not to discourage community participation
[06:55] <foxbuntu> it sounds like a good idea
[06:55] <puff> But as an example, one part would be augmenting apt to warn about problems.
[06:55] <puff> And also to give more useful responses in cases like ipodder and kdiff3.
[06:55] <puff> Okay, done.
[06:56] <foxbuntu> perhaps rather than making a package to add to other packages you could contribute to existing ones to make them more user friendly
[06:56] <puff> Possibly.
[06:56] <puff> the apt thing would actually not be altering apt, but providing some very apt-flavored information tools.
[06:56] <foxbuntu> at any rate, is the mkfs.xfs done?
[06:56] <puff> Yup, done.
[06:57] <puff> I said a second ago :-).
[06:57] <foxbuntu> alright
[06:57] <foxbuntu> must have missed it
[06:57] <foxbuntu> anyhow
[06:57] <puff> Yup, now what, add it to fstab?
[06:57] <foxbuntu> sudo nano /etc/fstab
[06:58] <puff> Yup.
[06:58] <foxbuntu> alright
[06:58] <foxbuntu> basically it should be:
[06:59] <foxbuntu> /dev/sda1       /mythtv/ xfs    errors=remount-ro       0       1
[07:00] <puff> Done.
[07:01] <foxbuntu> then: sudo mkdir /mythtv
[07:01] <puff> Whoops, gotta add the trailing backslsah on mythtv.
[07:01] <puff> Dobe,
[07:01] <puff> Done and done.
[07:01] <foxbuntu> sudo chown mythtv:mythtv /mythtv
[07:01] <puff> Done
[07:01] <foxbuntu> sudo chmod 775 /mythtv
[07:01] <puff> Done
[07:01] <foxbuntu> sudo mount -a
[07:02] <puff> hm, mount: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error.  In some cases useful info is found in syslog
[07:02] <foxbuntu> hmm
[07:02] <hipitihop> nonene else having nfs-common upgrade problems ?
[07:02] <puff> dmesg:  XFS: unknown mount option.
[07:03] <hipitihop> does mythbuntu actually need/depend on nfs-common and nfs-kernel-server ?
[07:04] <hipitihop> I know there is a services option in backend setup
[07:04] <foxbuntu> puff, ah, found my issue
[07:04] <foxbuntu> /dev/sda1       /mythtv/ xfs    defaults       0       1
[07:04] <foxbuntu> go back to the fstab and make it that
[07:05] <foxbuntu> then save and sudo mount -a
[07:05] <puff> Hm, same result.
[07:06] <puff> Dmesg, in addition to XFS: unknown mount option [errors]
[07:06] <puff> Also "XFS: bad mgic number" and "XFS: SB validate failed"
[07:08] <foxbuntu> delete the 0 and 1 at the end of the line and try it again
[07:08]  * foxbuntu notes its been awhile since he mounted xfs like this
[07:09] <puff> same error.
[07:10] <foxbuntu> thats really odd
[07:11] <foxbuntu> alright lets do this
[07:11] <foxbuntu> not sure why you have this error but...
[07:12] <foxbuntu> sudo mkfs.ext3 /dev/sda1
[07:12] <puff> I just figured out someting.
[07:12] <foxbuntu> oh?
[07:12] <puff> The *old* fstab was assuming sda was the 250GB.
[07:12] <puff> Right?
[07:12] <foxbuntu> no
[07:12] <foxbuntu> I dont think so
[07:12] <puff> That is, the existing lines in /etc/fstab refer to sda1 and sda6.
[07:13] <foxbuntu> oh?
[07:13] <puff> I would guess that's because sda1 used to be the 250GB.
[07:13] <foxbuntu> do this: cat /etc/fstab | pastebinit
[07:13] <puff> There's seven lines of comments.
[07:13] <foxbuntu> then prive me the link
[07:13] <puff> The box isn't on the net.
[07:13] <puff> I'll typeit up, one sec.
[07:13] <foxbuntu> oh right
[07:14] <foxbuntu> no
[07:14] <foxbuntu> is /dev/sda1 commented with the drive UUID below it in the fstab?
[07:16] <puff> Yes.
[07:16] <foxbuntu> then no worries
[07:16] <foxbuntu> the UUID is independant
[07:16] <foxbuntu> that why the boot still works :)
[07:17] <foxbuntu> so lets go down this route: sudo mkfs.ext3 /dev/sda1
[07:18] <foxbuntu> /dev/sda1       /mythtv/ ext3    defaults       0       0
[07:18] <foxbuntu> sudo mount -a
[07:19] <puff> http://pastebin.com/d753190e3
[07:19] <puff> okay, editing...
[07:20] <foxbuntu> ok
[07:20] <puff> Er, formtting.
[07:24] <puff> No errors.
[07:24] <puff> yay!
[07:25] <foxbuntu> cool
[07:25] <puff> Odd, df output says size 917 G, used 200 M, avail 871 G.
[07:25] <foxbuntu> one last thig
[07:26] <puff> I guess ext3 uses some of the space for journaling or something?
[07:26] <foxbuntu> yes
[07:26] <foxbuntu> thats it
[07:26] <foxbuntu> all done
[07:26] <puff> One last thing?
[07:26] <foxbuntu> see pretty easy
[07:26] <puff> Oh, df?
[07:26] <foxbuntu> I was just gonna have you do df -h
[07:26] <puff> Cool, well, it's easy if oyu know what you're doing :-).
[07:26] <foxbuntu> just to make sure it looked right
[07:26] <puff> So, thanks, and if you ever need any advice with java, php or perl, please ask.
[07:27] <puff> So do I have to tell mythtv that the file space is there?
[07:27] <foxbuntu> yup
[07:27] <foxbuntu> add it as a storage group
[07:27] <foxbuntu> if you google mythtv setup storage group
[07:27] <foxbuntu> you should find how to present it to mythtv
[07:28] <puff> So, step 1 start X.
[07:28] <foxbuntu> heh
[07:28] <puff> Step 2, start mythtv.
[07:28] <foxbuntu> yea
[07:28] <puff> Well, X still isn't up.
[07:28] <foxbuntu> mythtv-setup
[07:28] <foxbuntu> I have a little bit of time before I have to go
[07:28] <puff> Cannot open display.
[07:28] <puff> xprop: unable to open display ''
[07:29] <puff> Reboot, maybe?
[07:29] <foxbuntu> yeah, you will need X running to run tat
[07:29] <foxbuntu> well lets do this
[07:29] <foxbuntu> nano /var/log/Xorg.0.log
[07:29] <foxbuntu> and look for errors as to why it failed
[07:30] <foxbuntu> what type of video card are you using?
[07:32] <foxbuntu> puff, I am sorry but I am going to have to stop for the night
[07:33] <foxbuntu> puff, try a reboot if it still fails try searching through the logs, then ask someone in here again
[07:33] <puff> cool.
[07:33] <puff> thanks.
[07:33] <foxbuntu> np
[07:33] <foxbuntu> gl
[07:33] <puff> It's a pretty decent video card... I figured out what it was last week, now I can't remember.
[07:41] <hipitihop> anyone know if mythbuntu need nfs-common and and nfs-kernel-server ? can I remove them ?
[07:42] <SpicyLemon> I've got mythbuntu 9.04 installed.  Everything was working fine for a while, then tonight, a couple minutes after starting a  recording, the sound stopped working.  I've tried other recordings, and other video files, all that I know have working sound, but nothing comes out.  I tried rebooting, that didn't fix it.  Now, it won't even let me exit the mythbuntu frontend.
[07:48] <SpicyLemon> in my frontend log I see the error "Mixer unable to find control PCM"
[07:50] <SpicyLemon> /etc/init.d/alsa-utils restart gives a ton of errors similar to:
[07:50] <SpicyLemon> ALSA lib conf.c:3079:(snd_config_update_r) hooks failed, removing configuration amixer: Mixer attach hw:2 error: Invalid argument
[07:50] <SpicyLemon> ALSA lib conf.c:1593:(snd_config_load1) /home/danny/.asoundrc.asoundconf:13:1:Unexpected }
[07:52] <SpicyLemon> aplay -l gives a ton of errors like the ones above.
[08:05] <SpicyLemon> When I tried playing a movie in mplayer before the restart, I got this error, "[AO_ALSA] Unable to find simple control 'PCM'.0" After the reboot I get "[AO_ALSA] Playback open error: Invalid argument"
[08:12] <SpicyLemon> :/
[08:22] <hipitihop> If anyone else had a problem with upgrade to nfs-common, I have managet to get around it by removing the package.
[08:59] <ToeBee> superm1: yay today's CD works again!
[09:00] <ToeBee> *and* my sound seems to be still working as well
[09:00] <ToeBee> double awesome
[12:53] <mrand> ToeBee: does your remote work?  Can you please do apt-cache policy lirc
[14:07] <tmkt> anyone having problems with mythtv-backend the last couple days?
[14:07] <tmkt> won't seem to install for me
[14:09] <tmkt> http://pastebin.ca/1617718
[14:23] <mrand> tmkt: looks like https://bugs.launchpad.net/bugs/450217
[14:43] <tmkt> thanks
[14:45] <bobbob1016> My Mythbackend seems to be unable to talk to my mysql db.  Looking through the output I get in terminal, it says something about mysql.txt not having the right DBName.  I forgot what I named it, how would I find this?
[14:51] <mrand> bobbob1016: /etc/mythtv/mysql.txt
[14:53] <tmkt>  or ~/.mythtv/config.xml on trunk
[14:58] <Essobi> Morning.
[15:10] <gunni5> superm1: There? It was you discussing the "mythbackend starts to early for the driver issue" with me? Well, it is gone today. Only thing that changed is that the /etc/default/mythtv file is now the correct one. Seems like this was related to this wrong file there. Two reboots, and twice a correct start, unlike yesterday were 2 reboots twice missing dvb device.
[15:10] <bobbob1016> mrand, Here is the error I get when starting mythbackend http://pastebin.com/m79281949 .  It is a mysql database error, right?
[15:23] <gunni5> bobbob1016: Your backend seem to run as root. (Or databaseuser is root), should run as an own user (mythtv as example).
[15:26] <gunni5> bobbob1016: Can you pastebin your ~/.mythtv/config.xml but dont pastebin the password in there.
[15:27] <bobbob1016> gunni5, It's an empty file
[15:27] <bobbob1016> I think this issue started because I didn't have space on my / partition, and I tried some fixes but that messed things up.
[15:28] <gunni5> Do you have a user mythtv ?
[15:28] <bobbob1016> yes
[15:28] <mrand> bobbob1016: possible recovery ideas: http://ubuntuforums.org/showthread.php?t=1222575
[15:31] <bobbob1016> I'm thinking of reinstalling with the 9.10 beta anyways, since it has .22
[15:34] <bobbob1016> Would this be easier to fix if I start with a new mysql database?  I'm not using myth to record tv anyways, just play content.
[15:37] <mrand> I believe the config file is not used by mysql itself... it is used by mythtv to access mysql.  So new mysql database wouldn't help.
[15:38] <bobbob1016> It seems like I have the wrong password, I tried "sudo mysqldump -u mythtv -p (my password) mythconverg -c > mythtv_backup.sql" and it said incorrect password
[15:39] <mrand> the password is the mythconverg password.... contained in /etc/mythtv/mysql.txt
[15:40] <bobbob1016> That is the same password I've been trying
[15:41] <mrand> you could try the mysql root user.  -u root     Many people do not set password for that, so leave off the -p
[15:42] <tmkt> other odd thing is
[15:42] <tmkt> myth seems to start before lirc or something
[15:42] <tmkt> my remote doesn't work until about a minute after mythfe is running
[15:42] <mrand> tmkt: is that new behavior as of today?
[15:42] <bobbob1016> mrand, No, same thing, permission denied.
[15:43] <mrand> Might try some of your passwords for the root user.
[15:44] <bobbob1016> mrand, No, same thing, permission denied.
[15:44] <bobbob1016> I've tried a few different passwords I use/used
[15:45] <mrand> If you google around, there are several procedures for recovering from the lost mysql password situation.  Here's but one: http://en.wikibooks.org/wiki/MythTV/Troubleshooting#I_lost_my_MySQL_password
[15:47] <superm1> gunni5, great! glad that's all it was
[15:47] <superm1> too bad we broke intrepid and jaunty builds in the process, but that should be fixed today :)
[15:49] <bobbob1016> I tried that, and when I do service mysql stop it says failed, same with /etc/init.d/mysql stop, I did sudo su though, not su like the directions said, su didn't work
[16:00] <superm1> mrand, still no one freaking out w/ lirc 0.8.6. maybe no problems :)
[16:01] <tmkt> mrand: yeah..maybe yesterday also
[16:01] <tmkt> i think yesterday too
[16:01] <tmkt> ah..would love to try 0.8.6..but when i built it..it didn't work for me..
[16:02] <tmkt> anxious to install 9.10 with 22...but right now...9.04 with 22 works for the most part for me..some issues but at least everything works
[16:05] <superm1> tmkt, well if you are willing, there's still time to get issues fixed if there are any :)
[16:12] <tmkt> big issue was the remte
[16:13] <tmkt> not sure why lcdproc can't be compiled with lis by default though
[16:13] <tmkt> that'd be nice too
[16:14] <wombo> hehe
[16:15] <wombo> you never know your luck
[16:24] <rwat> hi, having problems with 2.6.31-13 on ubuntu karmic, not getting a lock on dvb devices - any known problems?
[16:25] <gunni5> rwat: Which dvb card?
 j-rod: device is a cheap kworld dvb tuner, using the dibusb driver
[16:27] <rwat> :)
[16:27] <rwat> I said that without moving my lips :)
[16:27] <wombo> hehe
[16:28]  * rwat does not have his hand up wombo's back
[16:28] <wombo> lol
[16:28] <wombo> I can read your mind
[16:28] <rwat> was working on jaunty, probably with 2.6.28-11
[16:28] <rwat> I could try rebooting to that still perhaps
[16:30] <rwat> all things appear normal in dmesg, mythtv connects to the devices (I have two identical) however it can't tune them and tzap doesn't ever get a lock
[16:31] <wombo> It doesnt look like the right people are online at the moment, just leave the session opan and someone might answer who knows
[16:32] <rwat> ok - I'm trying the old kernel
[16:32] <rwat> I suppose it's theoretically possiboe that someone cut the aerial wire :)
[16:35] <mrand> rwat: it is looking like some people (especially those with HVR-1300) are having a regression with the karmic kernel.  If you can revert to an older kernel and prove that it works, that would be somewhat helpful.  Someone else (gunni/gunni5) built a .31 kernel yesterday with the change removed and it seemed to fix things (right gunni?).
[16:36] <gunni5> Yes, but that was HVR1300 specific. Dont know about kworld ... but IIRC kworld is a cx88 device also.
[16:37] <rwat> something else which has regressed for me on the upgrade is that the box now doesn't want to reboot unless there's a monitor attached
[16:38] <rwat> either that or its something else that seems to coincide with that
[16:39] <tmkt> superm1: ok
[16:40] <tmkt> update-manager -d
[16:40] <tmkt> here i go
[16:40] <tmkt> just hoping i dont have to compile 0.84a lirc
[16:42] <rwat> mrand: on this kernel now it's not managing the devices properly, I'm ending up with dvb0.demux0 dvb0.net0 etc
[16:42] <rwat> can that be fixed temporarily with symlinks?
[16:42] <tmkt> yeah..nothing i could do was producing lirc0 for my hvr-1600
[16:42] <tmkt> but lets see how that goes now
[16:46] <rwat> ok, so how can udev be working ok for 2.6.31 but not for 2.6.28?
[16:59] <rwat> ok on kernel 2.6.28 if I mknod my own devices I get a lock
[17:00] <rwat> a bit pedestrian but it works
[17:00] <rwat> 2.6.31 makes its own devices properly but doesn't work
[17:01] <mrand> 0.22 myth?
[17:01] <rwat> using 0.22.0~trunk22413-0ubuntu1
[17:03] <mrand> rwat: Cool.  Helps to further confirm that it is either a pure kernel bug, or a change in the kernel that myth isn't handling correctly.  My only concern about this issue is that I thought other apps were working fine with it even on the new kernel.  Can you confirm that?
[17:03] <mrand> gunni5: what about you?
[17:04] <rwat> tzap does not get a lock either
[17:05] <mrand> oh.  hmmm... what about kaffeine or any other app?
[17:06] <rwat> I'm not sure about those, this machine doesn't have a monitor attached normally
[17:06] <mrand> oh yeah.  hrm.
[17:06] <gunni5> For me it was something like: kaffeine 0.8.6 worked including changing channels, kaffeine 1.0pre2 got me video, on changing channel, did not change, on restarting kaffeine channel was changed
[17:06] <mrand> gunni5: that was on .31 kernel?
[17:06] <gunni5> Yes
[17:07] <gunni5> I installed jaunty kaffeine for testing purposes, as i read of channel switching problems with karmic version.
[17:08] <mrand> Kinda strange that an older version of kaffeine worked with .31, but newer versions didn't.
[17:08] <rwat> anyone know the major and minor node numbers for the the second dvb adaptor?
[17:08] <gunni5> But the switching problems are now gone even with the karmic version after my kernel change
[17:09] <rwat> gunni5: did you send in your patch?
[17:11] <gunni5> I send the patch to stoth from linuxtv and to the ML there, but did not arrive at ML. I talked to stoth, and he received it.
[17:11] <mrand> Ok.  It's too late for us to make a wholesale  kernel change like that, especially since that change has been in the mainline kernel for a year now.  superm1 thought that there may be a way to allow users to reload that module to fix it though, and then work through the proper channels  for 10.04.
[17:11] <mrand> gunni5: cool... keep us advised.
[17:13] <rwat> ok well that's me up and running for now, I guess I'll stick with .28 until I hear otherwise
[17:14] <rwat> I think this must be the bumpiest upgrade for a long time
[17:15] <rwat> not particularly just myth, but loads of changes in ubuntu. no doubt all good but a bit of a surprise
[17:16] <mrand> 8.04 to 8.10 was smooth as silk for me.  8.10 to 9.04 was bumpier.  And those were well after they were released.
[17:16] <mrand> Do you typically upgrade on beta releases?
[17:17] <rwat> it has been known :)
[17:17] <rwat> not for anything important (i.e. not for work)
[17:17] <rwat> for home stuff I often upgrade a couple of weeks ahead
[17:20] <gunni5> For me it was the bumpiest upgrade i remember
[17:20] <rwat> I think somewhere around breezy there was a bumpy one
[17:21] <mrand> Well, thanks to people like you all, this will be a lot smoother than it would have been otherwise.  We have two weeks left to get it right.
[17:22] <mrand> Of course, it can only be as good as upstream delivers :-)   (ignoring what the mythbuntu team value adds)
[17:23] <gunni5> mrand: So you think this wont be fixed in the kernel? Well would be sad, and one year in the kernel does not mean there were no problems, as from jaunty to karmic is from .28 -> .31 ...
[17:24] <rwat> mrand: well thanks for being here :)
[17:24] <rwat> I remember the first time I reported an issue, it was on kde in Caldera in about 2000
[17:25] <gunni5> Have to leave for the train now, but my other personality is here in the channel for callbacks
[17:25] <mrand> gunni5: Understood.  the .31 kernel maybe hasn't had much exposure.  this affects enough people that we are going to try to figure out a work-around without patching the kernel.
[17:37] <mrand> rwat and gunni: Does 9.10 have the latest firmware?  Dates/versions are here: http://www.linuxtv.org/downloads/firmware/
[18:04] <walidus> Hi, i have problem. In MythTV my /dev/video1 is unavailable when in setup it's finding channels
[18:04] <walidus> in tvtime its works
[18:09] <walidus> avertv hybrid volar hx - my tuner
[18:27] <mrand> Walidus, searching with google, I found this: http://ubuntuforums.org/showthread.php?t=1119405
[18:27] <mrand> I would suggest posting and/or following up there.
[18:41] <Seeker`> o/
[19:02] <walidus> thx. I'll try
[19:52] <sbak> does anyone know why the top and bottom ubuntu desktop menu bars are present in my mythtv?
[19:53] <tgm4883> sbak, ATI card?
[19:53] <sbak> nvidia
[19:54] <tgm4883> interesting
[19:54] <tgm4883> output of dpkg -l mythtv
[19:55] <sbak> msi8500gt -- It has HDMI out, but im using DVI with the DVI-vga adapter into my 42inch plasma. I spent a year tring to get rid of overscan with HDMI but cant. I created a custom modeline that was close, but not perfect.
[19:55] <sbak> ii  mythtv                            0.21.0+fixes19961-0ubuntu8        A personal video recorder application (client and server)
[19:56] <sbak> When i choose adjust screen, the box is postitioned at 0,0. So it sees 0,0 under the menu bar
[20:00] <Seeker`> sbak: can your TV not turn on/off overscan itself?
[20:01] <sbak> Seeker`: correct. I wish to god it could. I have spent so much time trying to get this card to work. if i try to adjust V2 and V3 to the point where the top menu is not cut off, the TV can not display the input signal.
[20:02] <Seeker`> :/
[20:03] <tgm4883> sbak, which version of mythtv?
[20:03] <sbak> Seeker`: tried xvidtune, gtf, and other online modeline tools. I not sure whats better NO overscan with analog. or Slight overscan with HDMI
[20:05] <sbak> tgm4883: not entirely sure, i got it from apt-get install mythtv 2 days ago. first time i did it that way as i normally install it from svn
[20:05] <tgm4883> sbak, open up a command prompt and do
[20:05] <tgm4883> dpkg -l mythtv
[20:06] <sbak> i did and pasted above: 0.21.0+fixes19961-0ubuntu8
[20:06] <tgm4883> hmm
[20:06] <tgm4883> that seems kinda old
[20:06] <tgm4883> sec
[20:07] <tgm4883> yea, latest is 0.21.0+fixes21768-0ubuntu0+mythbuntu3
[20:07] <sbak> is there an easy way to upgrade. i doubt apt-get upgrade will work as i got it from the repository 2 days ago
[20:09] <tgm4883> I would recommend activating weekly builds
[20:09] <tgm4883> !weekly
[20:09] <Zinn> Weekly builds are available for MythTV 0.21 (Stable) and MythTV Trunk 0.22 (Unstable, use at your own RISK) for Hardy (0.21 only), Intrepid, Jaunty, and Karmic (0.22 and 0.23-trunk).  See http://www.mythbuntu.org/auto-builds for more info.
[20:09] <tgm4883> !stab Zinn
[20:09] <tgm4883> rhpot1991, ?
[20:09] <tgm4883> sbak, don't use the US repo though, it is broke
[20:09]  * Zinn stabs Zinn with a rusty spork.
[20:09] <tgm4883> use the UK or PPA
[20:09] <rhpot1991> tgm4883: ?
[20:09] <rhpot1991> !status
[20:09] <Zinn> I am alive.
[20:09] <rhpot1991> !stab tgm4883
[20:09] <tgm4883> rhpot1991, either my internet connection is crappy (possible) or zinn is really slow
[20:09]  * Zinn stabs tgm4883 with a rusty spork.
[20:09] <rhpot1991> seems little laggy
[20:10] <sbak> tgm4883: ty
[20:10] <tgm4883> np
[20:11] <rhpot1991> !hulu
[20:11] <Zinn> Hulu has released a Linux version of their desktop client. While support for this is available in the Hulu forums http://www.hulu.com/discussions/19 , there is a quick writeup on how to get it working from your frontend here http://ubuntuforums.org/showthread.php?p=8075632
[20:11] <rhpot1991> tgm4883: seems ok now, might have been laggy interweb or just coincidence
[20:12] <tgm4883> could be
[20:12] <rhpot1991> !mysql
[20:12] <Zinn> If you are having problems connecting to your mysql database, you can perform the following to reconfigure it: 1. sudo dpkg-reconfigure mysql-server-5.0 (pay attention to the root password you set, you will need it for the next step) 2. sudo dpkg-reconfigure mythtv-database 3. sudo dpkg-reconfigure mythtv-common
[20:12] <rhpot1991> !rtfm
[20:12] <Zinn> http://xkcd.com/293/
[20:13] <rhpot1991> hmmmm did I listen to the last UUPC?
[20:36] <tmkt> lirc 0.86 no help
[20:36] <tmkt> where can i dl 0.84a?
[20:40] <superm1> you can't(easily) revert to older lirc versions
[20:40] <superm1> because the kernel modules are shipped with the kernel
[20:40] <superm1> what's the problem with 0.8.6?
[20:40] <superm1> it's possible to just on your system build an older module if necessary....
[20:40] <tmkt> my hvr-1600 remote
[20:40] <tmkt> won't be detected
[20:41] <tmkt> no /dev/lirc0 no matter what i try
[20:41] <superm1> does lirc-i2c not load?
[20:41] <tmkt> yup
[20:41] <tmkt> its loaded
[20:41] <superm1> does dmesg speak about it?
[20:42] <tmkt> [   12.439006] lirc_dev: IR Remote Control driver registered, major 61
[20:42] <tmkt> thats all
[20:43] <tmkt> works great on 9.04 with lirc 0.84a
[20:45] <tmkt> only thing that isn't working for me with 9.10
[20:46] <tmkt> i think LCDproc should be compiled with lis driver, not sure why it isn't
[20:48] <superm1> tmkt, okay so here's the experiment to do then:
[20:48] <superm1> 1) install lirc-modules-source
[20:48] <tmkt> done
[20:49] <superm1> 2) Go to http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-jaunty.git;a=blob_plain;f=ubuntu/lirc/lirc_i2c/lirc_i2c.c;hb=HEAD
[20:49] <superm1> save that file as lirc_i2c.c
[20:49] <superm1> that's the source file for i2c from jaunty
[20:49] <superm1> 3) Overwrite /usr/src/lirc-0.8.6/lirc_i2c/lirc_i2c.c
[20:49] <superm1> 4) sudo dkms remove -m lirc -v 0.8.6
[20:50] <superm1> err 4) sudo dkms remove -m lirc -v 0.8.6 --all
[20:50] <superm1> 5) sudo dkms add -m lirc -v 0.8.6
[20:50] <superm1> 6) sudo dkms build -m lirc - v 0.8.6
[20:50] <superm1> 7) sudo dkms install -m lirc -v 0.8.6
[20:50] <superm1> and then reboot/retest with the lirc-i2c from jaunty
[20:52] <tmkt> so no lirc_i2c dir in /usr/src/lirc..
[20:52] <superm1> tmkt, it might be in a subdirectory
[20:52] <tmkt> yup
[20:52] <tmkt> drivers
[20:52] <tmkt> all good
[20:54] <sbak> with mythbuntu auto-builds, how can you force a daily build to take place now?
[20:54] <tmkt> at step 6 right now
[20:56] <tmkt> sudo dkms install -m lirc -v 0.8.6
[20:56] <tmkt> Error! Could not locate lirc_dev.ko for module lirc in the DKMS tree.
[20:56] <tmkt> You must run a dkms build for kernel 2.6.31-13-generic (x86_64) first
[20:58] <tmkt> ah error in the buid
[20:59] <tmkt> alot of warnings and errors in the make.log
[21:01] <tmkt> http://pastebin.ca/1618151
[21:07] <tmkt> i'll do anything to get this working
[21:08] <tmkt> no tlooking forward to reinstall 9.04
[21:12] <superm1> tmkt, hold off
[21:12] <superm1> i'll take a look at your error in a few min
[21:14] <tmkt> k
[21:16] <mrand> !weekly
[21:16] <Zinn> Weekly builds are available for MythTV 0.21 (Stable) and MythTV Trunk 0.22 (Unstable, use at your own RISK) for Hardy (0.21 only), Intrepid, Jaunty, and Karmic (0.22 and 0.23-trunk).  See http://www.mythbuntu.org/auto-builds for more info.
[21:16] <mrand> sbak ^^^^  is that what you're looking for?
[21:16] <mrand> weekly really equals daily
[21:21] <tmkt> spent 4-5 hours last week trying to get lirc going..so i'll give it to end of tomorrow
[21:28] <tmkt> suprised it hasn't come up anywhere in bugzilla
[21:48] <superm1> tmkt, so lirc-i2c in 0.8.4a looks like it won't work against 2.6.31
[21:48] <superm1> you could look at a diff  though to see if there is something in it that points to why it doesnt work for your device
[22:11] <sbak> mrand: Yes, but im specifically looking a way to maually initialize that auto-build process (a bit of a contradiciton, i know)
[22:11] <sbak> mrand: I just don't want to wait a day to get the update.
[22:12] <sbak> Is there a log that shows the auto-build activity?
[22:12] <sbak> ls
[22:12] <sbak> cd /var/log/
[22:12] <sbak> ls
[22:12] <sbak> ls
[22:12] <sbak> pwd
[22:12] <sbak> shit, sorry
[22:12] <Zinn> sbak: Please watch your language.
[22:19] <tmkt> superm1: so no solution? what about if i build lirc 0.84 from scratch?
[22:54] <gunni> mrand: Just for the log: after latest mythtv update (also kernel update today) i had to recompile the driver, so changeset22406 did not help
[23:01] <superm1> tmkt, it wont work on that kernel
[23:01] <superm1> lirc 0.8.4a doesn't support kernel 2.6.31 due to upstream changes
[23:14] <tmkt> nope
[23:14] <tmkt> so SOL?
[23:15] <tmkt> 9.04 is my only solution i guss..or get a new remote
[23:15] <tmkt> trying to recompile 0.86 with debug
[23:17] <tmkt> so what options would uyou recommend?
[23:19] <tmkt> useless no errors with debug enabled