[00:15] <hipitihop> darthanubis: sorry I don't see upgrade instructions there... can I do a dist-upgrade or must I use the ISO image ?
[00:16] <Mister> or can i install a packed from cd?
[00:21] <Mister> bye
[00:44] <hads> Hmm stick around and someone could have helped.
[00:44] <hads> old-releases
[01:03] <hipitihop> can I upgrade from 9.04 to the new beta without using the ISO ?
[01:04] <hads> Yes
[01:05] <hads> update-manager can do it somehow, or you can go CLI with do-release-upgrade
[01:05] <hads> update-manager -c -d I think
[01:06] <hipitihop> I'm happy to go cli as I tend to ssh in anyway .. do you have a handy link to these instructions ?
[01:08] <hads> Cool, just ssh in and issue `sudo do-release-upgrade`
[01:41] <mrand> If it isn't a pure server, the correct command appears to be sudo do-release-upgrade -m desktop
[01:41] <mrand> Probably won't be the end of the world if you leave off the "desktop"
[01:47] <hipitihop> hads: sorry, been away distracted.. will do
[01:48] <hipitihop> hads: should I stop the backend ?
[01:50] <hipitihop> mrand: thanks for the clarification, I might not do it via ssh and instead go with streight terminal on the box itself
[01:52] <mrand> hipitihop that's command line, regardless of ssh or straight terminal.
[01:53] <mrand> It somehow changes the behavior of how it upgrades some desktop packages.  Can't remember what right now, and it isn't easy to find out - it isn't well documented (there is even a Ubuntu bug on the fact it isn't well documented).
[01:54] <hipitihop> mrand: sure, just thought it might be a little safer then a wireless ssh session if connection is lost or otherwise. Maybe I should use 'screen' then
[01:55] <mrand> Interesting point on the wireless ssh.  I think I've done that an not had a problem, but if it is easy to do on a real terminal, why not!
[02:00] <hipitihop> hmm after all that it reports: Checking for a new ubuntu release ...No new release found
[02:04] <hipitihop> mrand: sorry, do I need to change something in update manager first ?
[02:09] <hads> Oh, try adding a -d for devel release
[02:10] <hads> Interesting, I hadn't noticed the modes, wonder what they actually do.
[02:12] <hipitihop> hads: I see, added -d and it seems to now be off doing its thing
[02:15] <mrand> Sorry - yes since 9.10 isn't released yet, you need the -d
[02:16] <hipitihop> mrand: all cool, thanks for help
[02:25] <hipitihop> grr... now getting "Failed to fetch http://au.archive.ubuntu.com/ubuntu/dists/karmic/universe/binary-amd64/Packages.bz2 Hash Sum mismatch"
[02:30] <mrand> try again?
[02:45] <hads> Yes, sorry, I missed the -d off my original line.
[05:46] <schnerf> irc has been more reliable than http for me for decent size files. is there a mythbuntu iso dcc bot?
[05:47] <superm1> no
[05:47] <superm1> but there are many http mirrors
[05:47] <superm1> so if you got a slow one, just try again and you'll usually be handed a different one
[05:50] <schnerf> thank you. i'll give it a shot.
[05:50] <mrand> Or you might be able to torrent it.
[05:50] <mrand> oh well.
[05:50]  * mrand waves
[08:56] <sidh> greetings gentlemen
[08:56] <sidh> is there owner of HAUPPAUGE Nova TD 500 DVD-T cards ?
[08:56] <sidh> DVB*
[09:14] <beatbreak> i'm trying to test Mythbuntu 9.10 but it's saying "this version of MythTV requires an updated database (schema is 30 versions behind) - how do i get the schema up to date?
[09:22] <beatbreak> I've tried to do a system update and that won't help, also looked into mythtv-setup but i can't see where it is on there
[09:22] <beatbreak> i'm sorry if my engligh is not so good
[09:22] <hads> Running mythtv-setup should upgrade the database for you.
[09:22] <hads> Note that you can't downgrade.
[09:23] <beatbreak> where do i press in mythtv-setup ?
[09:24] <hads> It should do it automatically I believe.
[09:25] <beatbreak> i try again
[09:31] <beatbreak> same result, what have I done wrong? should i restart my backend?
[09:31] <sidh> beatbreak: i'm new to mythtv/mythbuntu, but i can tell you that if you have hauppauge nova td 500 dvb-t card, you will experience some problem with beta 9.10, whereas you won't with 9.04
[09:32] <beatbreak> that's my card
[09:33] <beatbreak> will it be fixed when the official comes out?
[09:34] <beatbreak> I bought this card for Linux to work
[09:36] <beatbreak> http://pastebin.com/m36f3fc1a here is output
[09:38] <beatbreak> I make a terrible mistake, i bought wrong card, i thought it is most popular. my big mistake, so stupid me
[09:38] <superm1> um don't start mythbackend like that
[09:38] <sidh> beatbreak: the problem i experienced with 9.10 is that the device can not be "opened," then you can not retrive channels info, scanning and so on, it is a permission problem that i gave up to solve, and install a 8.04 which , at least recognize the pci card, even if i can not make it work well
[09:38] <superm1> it's got an init script for a reason
[09:39] <superm1> the init script will run it as the right user and make sure only one is running at a time
[09:39] <superm1> there ain't a chance that you will have proper functionality if two instances of mythbackend are trying to grab your DVB device (as shown in that log)
[09:40] <superm1> those look like 0.21 launches too.  mythbuntu 9.10 runs 0.22
[09:40] <superm1> so those are not compatible with mythbuntu 9.10
[09:40] <beatbreak> sidh, it works good on 9.04
[09:41] <superm1> sidh, that is supposed to be fixed by a web update in 9.10
[09:41] <superm1> channel scanning was broke with the version on the beta disk
[09:41] <superm1> so do your apt updates and things should be fine
[09:41] <beatbreak> superm1, really? i try now
[09:42] <superm1> beatbreak, it doesn't look like you are running 9.10 though, you would have a 0.22 mythtv version then
[09:43] <beatbreak> i have Arch linux backend, then MythBuntu Frontend
[09:43] <sidh> If someone owns a HAUPPAUGE NOVA TD 500 DVB-T card and can make it works with reliability, could you PLEASE tell me your set up of this device, I'll pay you with Belgian beers (the best ever in the world)
[09:43] <superm1> beatbreak, then you need to upgrade your arch backend to 0.22 too, or use mythbuntu 9.04 for your frontend
[09:43] <beatbreak> MythBuntu never worked well so I made some reports to fix networking, i hope is fixed now
[09:43] <sidh> beatbreak: yes on 9.04 the card is well recognized
[09:45] <beatbreak> oh i see, Arch uses MythTV 0.21-2
[09:45] <beatbreak> is 0.22 in beta?
[09:48] <beatbreak> on mythTV website they have 0.21 also
[09:50] <hipitihop> while doing upgrade from 9.04 to beta I notice this in my terminal window "Preconfiguring packages ...Failed to connect to database (incorrect admin password)"
[09:53] <beatbreak> i don't understand, beta release needs 0.22 but the official release is 0.21 - am i mistake?
[09:53] <sidh> beatbreak: why do you need 9.10
[09:53] <sidh> .
[09:53] <sidh> ?
[09:54] <beatbreak> sidh, because networking never worked properley in 9.04
[09:54] <sidh> networking ?
[09:54] <sidh> you mean NFS
[09:54] <beatbreak> sidh, i spoke to Ubuntu and make a report to fix in 9.10
[09:55] <beatbreak> no not NFS, ummm how do you say? i start MythBuntu then when i'm on desktop network starts, but it fails in background during startup procedure
[09:55] <sidh> beatbreak: i use mythbuntu on on CF card, with all media exported on a NFS/ZFS server (FreeBSD of course), no problem with data
[09:55] <sidh> the LAN is gigabyte with jumboframes
[09:56] <beatbreak> ETH0 only detected when desktop starts, not in start up. so it makes it hard to map netowrk drive and ping/wol server
[09:57] <sidh> yes i noticed that too
[09:57] <beatbreak> it's important for me that it is fixed
[09:58] <beatbreak> it's not a mythbuntu problem, it's an Ubuntu problem
[09:58] <beatbreak> but now i have mythbuntu problem with new version you say?
[09:58] <beatbreak> nothing work right, i make some mistake somewhere?
[09:58] <sidh> beatbreak: before moving to mythbuntu, i tried the last version of LinHES (archlinux based) the network stack is much more well implemented
[10:00] <sidh> but as i need to compile lirc and lcdproc , and the only linux i'm used to is debian , i chose mythbuntu then
[10:00] <beatbreak> sidh, i'm not ever use Knoppix too, Arch is good, and too Debian base
[10:01] <beatbreak> lirc is such a complicated in Arch it make me pull me hair
[10:02] <beatbreak> mythbuntu is very quick for this one. So myth backend = arch, myth frontend = mythbuntu. it make me happy
[10:18] <hipitihop> why does the upgrade have problems logging into the database with "Setting up mythtv-database (0.22.0~trunk22242-0ubuntu1) ...Failed to connect to database (incorrect admin password) "
[10:34] <darthanubis> https://bugs.launchpad.net/ubuntu/+source/mythplugins/+bug/212460
[10:35] <darthanubis> superm1, Ive been meaning to check this out. I'll get back with you concerning this soon
[10:40] <hipitihop> well that upgrade was less then spectacular ... did not boot into desktop and left me at a login prompt
[10:41] <hipitihop> does do release upgrade log everything ? as I may have missed some other errors
=== Mazga is now known as _Mazga
[15:31] <Essobi> WEEEEEE!  I SAID WEEEEEEEEEEEEEEE!
[17:22] <sidh> ok i found this strange behaviour
[17:22] <sidh> for having sound on TV, i have to choose /dev/surround51, and for having video sound , i have to choose /dev/dsp1, in the set up menu
[17:23] <sidh> why isn'it possible to use the same ouput for both tv and video ?
[17:23] <sidh> it is quite boring to change that settings each time ...
=== meshe_ is now known as meshe
[18:32] <sidh> anybody ' here ?
[19:02] <CyberKnet> occasionally
[19:02] <CyberKnet> I do not know the answer to your question though sorry.
[20:02] <sidh> ok after i aptitude remove --purge kaffeine, i f i choose /dev/ALSA:surround51 as device i can watch tv and play music BUT i can not play video with mplayer
[20:12] <sidh> if i cat a file in /dev/dsp1 the speakermake noise, so the device is ok
[20:12] <sidh> why mplayer can not use that device
[21:28] <bhaa___> i'm running karmic, but since my q is mythtv specific i thought id try here...
[21:28] <bhaa___> apparently the mythtv package depends on nvidia libvdpau 185.
[21:28] <bhaa___> for other reasons i have nvidia 190
[21:28] <bhaa___> mythtv install wants to remove 190
[21:29] <bhaa___> is there any way of avoding this?
[21:29] <bhaa___> perhaps if the devs could change the package dependency...?
[21:30] <bhaa___> (i tried installing and couldnt get X running then)
[21:30] <mrand> I thought that they had made it so that it could depend on any of those.  If you're willing to wait a while, hopefully a superm1 can stop by and answer it.  When did you last update?
[21:31] <superm1> jya needs to push his vdpau independent package into debian first
[21:31] <mrand> At a minimum, you should be able to pin the one you want to use.
[21:31] <superm1> likely won't be able to fix that for karmic
[21:31] <bhaa___> mrand: today a few hours ago.
[21:31] <mrand> But he should be able to pin, right?
[21:31] <bhaa___> but its from danish servers which are a bit behind i belive
[21:31] <mrand> today is fine, regardless of server.
[21:31] <superm1> you can pin the package, but we are hard depending on the name "nvidia-185"
[21:32] <bhaa___> i didnt try pinning, it should work that way?
[21:32] <bhaa___> ill try
[21:32] <bhaa___> superm1: so it wont work then
[21:32] <superm1> so if the 190 driver is packed into a 185 name it will work
[21:32] <superm1> but otherwise no
[21:32] <bhaa___> ah, i see
[21:33] <superm1> the problem will be properly resolved for 10.04
[21:33] <superm1> it's a little too late in 9.10 to fix it properly though
[21:33] <superm1> mostly because NVIDIA didn't release the open source vdpau library for a long time
[21:34] <bhaa___> i see
[21:35] <bhaa___> so in conclusion, no push'n play solution until 10.4 (reminds me of osx tiger:)
[21:35] <bhaa___> i'll keep an eye on ppa's etc.
[21:35] <bhaa___> or do find some other workaround...
[21:37] <bhaa___> since it hasnt been resolved. are there non-trivial reasons the dependencies hasnt just been changed to accept both.
[21:37] <bhaa___> (asking in case i want to rebuild mythtv and change the dep myself)
[21:39] <superm1> well what's it link to?  can you check ldd output for mythfrontend?
[21:39] <bhaa___> but i cant install it....
[21:39] <superm1> we might be able to hardcode it to something like Depends: libvdpau, and have both drivers provides: libvdpau
[21:39] <bhaa___> mythfrontend that is :)
[21:40] <superm1> of course.  that would make it way too easy.
[21:41] <bhaa___> right...