[00:06] I just did a sound check in the terminal... and it keeps doing it... [00:06] how do I get it to stop? [00:18] well it connects to my backend, but configuring it required me to use gconf-editor [00:18] that's hacky.. [00:18] and now it claims that gstreamer doesn't know how to talk MYTH [00:18] so must need *another* "shrug" app for that [00:21] it's the gnome way! your config screen should have one tickbox for "do i like blue?", and the rest is managed via complex xml configs [00:21] haha [00:21] i dont get why they couldnt just use that shiney configure button [00:21] on the plugins page [00:22] superm1: Presumably because they haven't actually written the UI code to do that :P [00:22] yeah, i suppose :) [00:22] well maybe this just "works" when your backend is localhost [00:22] and it probes mysql.txt or something [00:23] bah. it depends on two other apps that have to make it in. gmencoder /and/ gms [00:24] okay well more packaging to go then :) this will make a fun MIR once all said and done [00:28] hey superm1: you there [00:29] sure [00:30] when where you typically going to push autotrunk build through (day of the week) [00:30] usually saturdays [00:31] but last week went two days early [00:31] because the week before ftbfs [00:31] also the notice the Milestone .21 svn is 85% that is a 4% change [00:33] yeah a lot of those bugs were reclassed [00:33] to 0.222 [00:33] er 0.22 [00:35] i see that nw [00:35] now [00:54] how long to you think it should take to click watch tv and see a picture [00:55] 3-5 seconds for me [00:55] hum i am 7-10 seconds [00:56] Depends on many factors; signal strength, dvb tuner, how stupid your FTA dvb broadcasters are... [00:56] 2 second buffer i believe [00:57] well i usual lockin at 80+%, pchdtv card, and i not sure the intelligancy of the broadcasters [01:00] i just to me it seem to take longer than usual [01:02] anyone ever see anything where you have working wifi using wep, go to configure it to wap instead which fails and then it will no longer connect to the old wep? [01:03] win 1 [01:04] met4llica: is that in response to me, or something else? [01:04] rhpot1991: That's in response to him forgetting a / on the front, probably :) [01:04] error actually [01:04] sorry [01:05] heh === met4llica is now known as met4llica[idle] [01:11] hey how do extrenal hdd preform and [01:12] i have 1 hd tuner and 1 analog and i am usaul watching one strem [01:12] stream [01:23] is there any easy way to temporarily have an nvidia card display through vga instead of svideo? [01:29] mv xorg.conf bak.xorg.conf and restart X, should startx with a generic config - maybe not optimised though [01:29] then move your conf back [01:29] i dont know if theres an easier way === met4llica[idle] is now known as met4llica [02:01] is there a way to configure samba from withen mythbuntu? or do I have to use the terminal? [02:02] Lossif, you can enable samba via mythbuntu-control-centre [02:02] but configuring it had to be done on your own [02:02] you can enable it... [02:02] ahh [02:03] so to tell it where to share... [02:03] exactly [02:03] I have to use the terminal... [02:03] blah [02:03] oh well thanks alot [02:12] for some reason myth is saying cx8801 is my default digital output, but it should be my turtle beach card... [02:17] asoundconf [02:17] will let you modify these types of things [03:22] Hello, everyone. I'm trying to install Mythbuntu 7.10, but X keeps failing to start and my attempts to troubleshoot it has failed. [03:22] There is no errors in dmesg or /var/log/Xorg.0.log [03:24] I'm using an ati graphics card with "ati" driver configured in xorg.conf [07:38] Hi all! [07:39] I'm new to mythbuntu and mythtv [07:39] I've a problem and I can't find a solution in documentation... [07:40] I've installed Mythbuntu on my PC and I'm trying to setup the dvb card (technisat skystar2) that is recognized by the system [07:45] but I haven't an internet connection [07:45] and I can't scan for channels without internet... [08:58] hi who about ? [09:01] help need setting my hauppauge 45 button remote [09:01] I have limited fuction only [09:02] upgrade to the newer mythbuntu-lirc-generator [09:02] and regenerate your remote [09:04] this is where im going to come unstuck [09:06] im complete noob to linux but learning as i go iv managed most of the setup [09:09] okay well open up the mythbuntu control centre [09:09] and then open up update manager in it [09:09] and do the updates [09:09] one of them should be mythbuntu lirc generator [09:10] once that finishes, go back to mythbuntu control centre [09:10] and pick the remote tab [09:10] and check the little box to regenerate dynamic button mappings [09:10] restart mythfrontend and you should have more functional buttons [09:13] checking update know [09:18] still has`nt worked still limited fuction [09:19] i have picked hauppauge nova t 500 which my card is [09:21] well next think you can try is to run irw [09:21] from a command line [09:21] and see if it sees more buttons [09:21] when you press them [09:21] MythbuntuGuest45: You need to ugrade v4l-dvb for that card, hit the mythtv wiki for a how to [09:21] or listen to Daviey [09:22] :), if you "dmesg" and there is no mention of an input, that is [09:24] ok irw running the only button that fuction is direction and number pad [09:24] ah, in that case then - as superm1 said, your lirc settings need fixing :) [09:30] ok done dmesg what am i looking out for [09:32] looked at the last lines in dmesg and has listed dib0700 :unknown remote controller key:0 38 [11:22] hello i have a problem. When i play a recordet video with mythbuntu it works only an a monitor, on my tv have the film lags. [11:22] have somebody an idear? [13:36] MythbuntuGuest86, you have both screens connected at once? [13:45] hello problem is the driver... failsafe vesa driver, somebody help me in german room.... [15:19] anyone there? === dr_fate is now known as blkorpheus [17:42] * jarle did not even know this channel existed :) [17:42] well see mythbuntu.org/support [17:42] and you would have seen it [17:42] :) [17:42] okay so your on gutsy running -fixes weekly builds [17:42] with an nvidia legacy driver? [17:43] superm1: running svn weekly [17:43] superm1: with nvidia legacy... [17:44] superm1: I do not use this frontend that often, I used to run -fixes weekly without any problems.. [17:45] jarle, and the checkout in apt (in the ubuntu archive) doesn't exhibit this behavior? [17:45] superm1: not sure if this problem started as soon as I moved over to svn or if I had svn working for a while on this frontend, can't remember.. [17:45] superm1: what do you mean? [17:47] jarle, well in order to compare your issue with the one you pointed me to on svn.mythtv.org, we need to see if it happens with the distributed version in multiverse [17:47] or if it only happens on mythbuntu weekly builds [17:48] superm1: is there a svn build in multiverse? [17:48] jarle, of course [17:51] superm1: I'm using "deb http://uk.weeklybuilds.mythbuntu.org/mythbuntu-trunk/ubuntu gutsy multiverse universe restricted main" [17:52] right, you'll have to tremove that repository, and downgrade to all the packages in multiverse [17:52] on the normal repository [17:52] to check this [17:52] superm1: when I used "svn" I was actually talking about the weekly trunk :) [17:52] trunk. [17:52] oh.. [17:53] well that's a different story, and definitely not related to that bug you referred me to [17:53] since its about an issue on -fixes that was backported [17:53] superm1: sorry for misleading you... [17:55] The problem seems to be that the package is built in a way telling it to use glXGetProcAddress instead of glXGetProcAddressARB as (I think) should be used in my setup... [17:56] and the http://svn.mythtv.org/trac/changeset/14643/branches/release-0-20-fixes (the fix posted in the bug I quoted) was related to which function to be used.. [18:01] jarle, what you can try to do to verify this hypothesis is build the source package yourself [18:01] against nvidia-glx-legacy libraries [18:02] if you apt-get source the mythtv package with the weekly builds deb-src repo [18:02] and then apt-get build-dep mythtv [18:02] and then typing debuild in the directory [18:02] be sure to debuild as root [18:02] er not as root i mean [18:05] superm1: can't seem to find a link to the deb-src repo? [18:06] jarle, exact same repo, but just change deb to deb-src [18:07] superm1: so I just change deb into deb-src and then run "apt-get build-dep mythtv" ? [18:08] jarle, well you'll need both in place, the deb and the deb-src [18:08] and then apt-get update [18:08] the build-dep gets anything necessary to build a mythtv source package [18:08] and then apt-get source downloads and extracts the source package [18:09] Hey superm1 ! [18:09] hi frink__ [18:09] how are you? [18:09] gooood thanks! [18:09] gah [18:09] another bloody meeting.. [18:09] gotta go. sorryy! We'll talk one day :) [18:09] okay :) [18:25] superm1: does the mythtv package install the backend also? I only need the frontend... [18:37] jarle, then install mythtv-frontend [18:41] superm1: and then when it comes to the actual installation (after running debuild)? [18:41] install the debs [18:41] it produces debs [18:43] superm1: oki... thnx for your help so far.... [18:44] guess I might have to force it to replace the binary packages already installed? [18:45] yeah you will [22:10] when was 'Watch List' Added to the watch recordings menu? [22:15] in trunk AFAIK [22:22] nice addition that i didnt see before [22:22] ive overlooked it for the last few months hehe [23:25] Hi everyone [23:26] Any gurus about who might know how to resolve what looks like an IRQ issue with my DVB-T cards? [23:30] The two cards in question have worked fine before under Fiesty and Gutsy and even Mythbuntu 7.10. I changed motherboards to an almost identical one (to replace one that wouldn't work. And rebuilt with Mythbuntu 7.10 but the DVB cards won't work. [23:32] Here is the lspci -vv output for anyone that might know what it means: http://pastebin.ubuntu.com/4016/ [23:32] And I've started a topic here on it: http://ubuntuforums.org/showthread.php?t=682631 [23:34] The DVB cards are a DVICO and an Avermedia and have been supported in the kernel for quite a while now which is why this is confusing. It has, and should, work out of the box.