=== CShadowRun is now known as cshadowrun === cshadowrun is now known as CShadowRun [00:47] i have a crossover cable connecting to my other computer which is sharing it's internet connection.. worked fine in 9.04 but its not connecting in the latest 9.10 [00:52] anyone know what might be causing it? everythings set up the same afaik [00:52] as far as i can tell* [01:19] trying to install emulators sucks without apt-get :( [01:20] have you tried refreshing your dhcp leasE? [01:21] no DHCP, i set the IPs manually since it's just a 1-1 connection [01:25] Seventoes: make sure you set things like the gateway or dns [01:25] also verify if it can see other internal computer or not [01:25] it won't connect at all [01:25] tries and fails [01:27] btw...what was the point of dontzap change? [01:39] uhg this is agrivating [01:50] ahh.. checked syslog, had to turn off IPv6 for the connection. was timing out trying to get an IP for 6 [02:43] well sound survived upgrades. IR did not :) [03:29] hmm where do all the files in ~/.lirc/ come from? [03:30] mythbuntu-lirc-generator [03:30] it creates them [03:30] aha [03:31] hmm I don't see an option in mythbuntu control center for a straight devinput remote [03:32] was there one previously during 9.10? [03:33] don't think so [03:49] yeah the only button that the lirc-generator seems to recognize from the devinput lircd.conf file is play/pause [04:07] ah yeah looks like the button dictionary in core.py doesn't know about the key names used int he devinput lirc conf file [04:07] it uses "KEY_?" for most of the buttons [04:08] like "KEY_1" instead of just "1" like a lot of them use [04:19] ToeBee, actually you know what, i might have a fix for that... [04:20] would you mind testing it? [04:21] sure. Was thinking about trying my own hand at it after I finish my cookies [04:21] ToeBee, okay, if you can grab the bzr branch: "bzr get lp:~mythbuntu/mythbuntu/mythbuntu-lirc-generator" [04:21] and then "cd mythbuntu-lirc-generator" [04:21] and then "dpkg-buildpackage" [04:22] you'll have a deb with my improvements in place [04:23] bah! no bzr installed by default in beta versions?! :) [04:23] haha, it's a development tool [04:23] you probably won't have the stuff for dpkg-buildpackage either [04:24] but it'll tell you what's missing [04:26] yep. dpkg-dev [04:32] hmm ok [04:33] I see a warning... where does it put the final package? [04:34] ah looks like one directory up [04:35] Yup [04:36] well that looks much more promising [04:39] hmm odd. My rewind button works but not the fast forward [04:44] ToeBee, well it's quite possible i'm still missing some stuff [04:44] those changes were to improve one of the antec remotes [04:44] ok buttons that didn't get mapped: KEY_1, KEY_PLAYPAUSE, KEY_STOP, KEY_FASTFORWARD [04:45] so if you've got some more to propose adding, i'm happy to accept a diff :) [04:45] looks like KEY_1 got mapped as KEY_102ND [04:45] ah [04:49] not familiar with python although I have thought about learning it. Might be the opportunity I've been looking for :) [04:52] I'm assuming you added in the business about key_split=button.split('KEY_') [04:52] yeah i did [04:52] just follow the stuff at the top of core.py and mythtv.py [04:52] it should just be another 3-5 lines you've gotta add for your extra keys [04:58] well I see why it didn't catch the fast forward button but it looks like it should have caught the KEY_STOP, KEY_PLAYPAUSE and KEY_1 [05:00] there is a problem with the remapping of some keys [05:00] where you can't have a key mapped twice [05:00] so it might have gotten caught on something else [05:00] ah [05:01] well the devinput lircd.conf file does have a lot of extra buttons that my remote doesn't have so that could be complicating things [05:02] I see it mapped KEY_CLOSE and KEY_CANCEL to "Escape" for mythtv but not KEY_STOP [05:02] Yup that's the double key issue [05:05] heh. yeah if I comment those two out in lircd.conf then it assigns KEY_CLOSECD and KEY_ESC [05:07] so basically for my situation the devinput lircd.conf file is just too broad [05:10] well get me a diff for your missing key and i'll try to investigate a better solution for the double mappign [05:10] unfortunately that was introduced a month ago (debian/changelog:) [05:10] - Merge together remotes if two of the same named remotes are [05:10] defined in the lircd.conf set. Unfortunately this has the side [05:10] effect that if two buttons that perform the same action are [05:10] defined with a different name, only the first gets selected. [05:12] well I think the only one of mine that needs tweaking in core.py is the KEY_FASTFORWARD. just need a |^fastforward added on line 37 [05:13] there is fastfwd and fforward but no fastforward [05:13] I was somewhat amused that the "zoom" button on my remote actually worked :) [05:22] ooh I just made frontend crash too! [05:23] boo! nothing fun in the log [05:26] didn't happen then :) [05:26] got a crash report in /var/crash? [05:26] yeah after commenting out everything except for the buttons that my remote actually has, things are much better. Only complaints are the fast forward and some mappings I personally would prefer to be different based on my usage but probably make sense for most other remotes [05:27] yes there is [05:27] Wonderful, you can be a guinea pig for our testing of the crash reporting mechanism [05:27] can you backup that crash report somewhere and then run "ubuntu-bug FILE"? [05:28] I'm asking to back it up because it would automatically be removed after filing otherwise [05:28] mrand, ^ [05:29] sure [05:30] holy crap it wants to send 447 MB :) [05:30] the crash report was 53 [05:32] Yeah that may take a while [05:33] hmm it sure is greedy. Looks like it grabbed the entire frontend log [05:33] couldn't that be trimmed down to, say, just the last 1,000 lines or something? [05:33] it's not really 447 [05:33] Yeah, I noticed that too [05:33] it will be about 47 [05:33] there's something wrong with the way it calulates it [05:34] calculates even [05:34] Aha [05:35] heh. "I must have put a decimal point in the wrong place or something. I always do that. I always mess up some mundane detail" [05:35] -- office space [05:35] the most important thing is the coredump, the rest can really care less bout [05:36] ok well I'm uploading it now [05:36] Well, the stack trace would be nice too. [05:36] good call on backing it up, superm1 [05:36] well a stack trace should be generated from the core dump [05:36] a bettererer stack trace at least :) [05:36] not like I'm on dialup or anything [05:36] heheh [05:37] But considering that the stack trace is the output we're really interested in, it would be nice to see what things produce usable output. [05:37] superm1: Does he need to run apport-retrace himself? [05:37] ToeBee, are you? [05:37] if so, then maybe this is a bad exercise for you [05:38] mrand, i was figuring we'd do that right after he gets launchpad to process her [05:38] gotcha [05:38] 30% complete [05:38] good. not too slow then. [05:39] nah. I can usually sustain about 100 KB/sec up [05:39] Anything to change to this, superm1?1. if you have something in /var/crash, install the appropriate ddebs from http://ddebs.ubuntu.com/pool/multiverse/m/mythtv/ (hint: you might need libmyth-0.22-0, among other more obvious ones, and some [like mythplugins] may be in a directory higher) [05:39] 2. while doing that, install apport-retrace [05:39] 3. After above two steps are done, execute "sudo apport-retrace -s /var/crash/CRASHFILE" perhaps use -sv if you are on a slow connection. -p (like -p mythvideo) may provide even more info. [05:39] 4. attach output to a ticket (same ticket you just created would be fine) [05:39] I distilled down what you'd written last night [05:40] mrand, well i think we need to figure out whether (1) is actually necessary [05:40] apport-retrace might do it all for you, i'm not sure [05:40] ah, I misunderstood. I thought you were saying that with regards to something else. [05:40] but otherwise that sounds concise (and might just need some experimentation) [05:40] which is why it's good we have ToeBee here to help out :) [05:41] gotcha. I need to run for now... hopefully ToeBee can help us narrow that down! [05:41] yay testers [05:42] ok so I should go ahead and install apport-retrace? === Casper0082 is now known as NOT_Captain_murd === NOT_Captain_murd is now known as Casper0082 [05:46] well the upload finished [05:47] uh-oh. I think I broke launchpad. Just got a "Please try again" message while trying to visit the URL it gave me [05:47] oh crap, you hit that too? [05:48] try hitting refresh [05:48] we might need to narrow down the stuff that's getting attached to the bug since launchpad apparently hates us [05:48] yeah browser waits for about 50 seconds then displays the error message [05:50] ooh got a different message this time [05:51] something about edge servers? [05:51] "As a member of the Launchpad Beta Testers team..." wait, when did that promotion happen? [05:53] Oh you're on edge? [05:54] edge has a quicker timeout [05:54] can you switch off of edge? [05:55] yeah it has a button to disable it for 2 hours. No clue what edge is or how I got on it but hey... :) [05:55] if you can't get this uploaded in a few minutes, don't worry, just do the retrace locally [05:55] and hopefully that will get the right information filed [05:57] well that time I got an apache "502 Proxy Error" page [05:58] if I keep crashing it, is Shuttleworth going to come break down my front door? [05:59] I hope so [05:59] because that means that it'll probably get fixed too [05:59] lol [06:00] yeah I don't think this is going to work [06:01] so what's this retrace business all about? [06:02] so install the package apport-retrace [06:02] it will locally run the trace that launchpad normally would [06:02] and get you a stack trace that you can post to the bug [06:02] done [06:03] so run it like mrand said "sudo apport-retrace -sv CRASHFILE" [06:03] looks like the file in /var/crash/ is still there [06:03] hopefully it will install the dependencies for retracing automagically, but if not will walk you through doing so [06:05] yeah looks like it is doing something with the repositories [06:05] bunch of warnings about incompatible packages [06:06] should be fien [06:06] as long as it's grabbing debs for you for the debug symbols [06:07] hmm I got a stack trace... was I supposed to capture the output to a file or did apport-retrace crash? [06:08] capture the output [06:08] you can use the -o flag instead of -s i think [06:08] probably should have said that [06:08] hmm I do see a bunch of "No symbol table info available" messages [06:08] and I don't see any output indicating that it actually installed anything [06:08] hopefully they're in irrelevant places [06:09] oh, well if it didn't install anything then that probably won't work [06:09] can you add the repo as indicated in https://wiki.edubuntu.org/DebuggingProgramCrash ? [06:12] mrand, somehow i got lucky enough to find a piece of hardware that reproduces bug 452725 [06:12] Bug 452725 in ubiquity (Ubuntu) "ubiquity-dm crashed with XStartupError in run()" [High, Incomplete] http://www.launchpad.net/bugs/452725 [06:12] it looks like a race condition, i think i've got a fix for it [06:14] ok apport-retrace is actually installing things now [06:15] sweet [06:15] so our steps for a local retrace need to include adding that repo first then [06:15] so it would seem [06:17] lot of stuff to install. I guess it's doing all dependencies from the ground up? [06:17] well anything it would need for this retrace [06:19] ok yeah that stack trace definitely looks different [06:19] good! :) [06:21] so now I create a launchpad ticket and attach that? I'm guessing since launchpad crashed on me earlier that one is of no use [06:22] yeah [06:51] ToeBee, see how this core.py handles ya [06:51] http://pastebin.com/f37555061 [06:52] i need to make sure there are no regressions in using it with one of my remotes, but i think it will DTRT [07:04] bug 457890 [07:04] Bug 457890 in mythtv (Ubuntu) "mythfrontend crash while stopping a recording" [Undecided, New] http://www.launchpad.net/bugs/457890 [07:04] got a little distracted but I eventually got it posted :) [07:06] Oo that was tricky. When I shifted the DB and master BE to a new host I didn't define a Defualt storage group on that host. So when I added a card to the new master it got messed up and tried to record to a non-existant path from the slave. [07:07] superm1: want me to try that with the full lircd.conf or just with the buttons on my remote? [07:08] ToeBee, full lircd.conf [07:08] i think it should map everything correctly now [07:09] well the files are noticably larger [07:12] well the config file looks ok. Trying to restart mythfrontend to actually try and use it [07:12] and it froze on the "do you really want to exit" screen :/ [07:12] actually it has done this to me before [07:13] I'm wondering if it doesn't like me restarting lirc while it is running [07:13] i certainly don't like that. i'm sure myth doesn't either :) [07:14] Fixing that actually has the added side effect that the "back" button on my mceusb finally works too! :) [07:17] for some reason the jamu scripts aren't on my backend, but they are on the frontends for the diskless stuff I setup, from the instructions I've read, its supposed to be run on the backend, is there a package I didn't install or something? [07:17] they come in the mythvideo package [07:17] I think everything is working now... except KEY_POWER [07:18] i installed mythvideo on the backend, and they aren't there either [07:18] ToeBee, well KEY_POWER we don't have anything good for it to do though [07:18] ah [07:18] nevermind [07:18] i'm too scared to make it really halt the system [07:18] I'm blind, I'll go from here, thanks [07:18] heh yeah that probably wouldn't be good [07:18] that makes it way too easy for my dog to sabotage my recordings for the night [07:19] maybe a good action would be to spawn mythfrontend though if it's not already running? [07:19] and if it is, just dont do anything [07:20] hmm yeah that might work [07:21] and of course I will probably remap the fastforward and rewind buttons to skip instead but that just depends on personal preference and how many buttons your remote has [07:22] Yeah [07:22] actually... [07:23] now that I actually know how lirc works a little I may try to program the blank slot on my universal remote to something random and make THAT control my mythfrontend :) [07:24] but hey at least I helped something along the way! [07:25] i noticed the daily builds repository isn't working... is there another repository? i'd like to try 22 RC1 out... i'm running ubuntu, not mythbuntu, btw [07:26] jtmoney, run dpkg-reconfigure mythbuntu-repos [07:27] and try a different mirror [07:27] which one were you using though? [07:27] US [07:27] try the PPA repo instead [07:27] thanks [07:28] tgm4883, ^ [07:53] P.S. Mythbuntu is Ubuntu [07:59] oh huh. Windows 7 is out [07:59] * ToeBee yawns [08:01] anyone know if 9.10 will come with 22 RC1 or not? [08:02] it will likely be a little later of a snapshot than 0.22rc1 [08:02] hopefully gold is out by then, but if not it will be just before gold [08:02] AFAIK yes, either rc1 (currently) or another -fixes [08:02] Oh, what he said. [08:03] cool [08:03] i seemed to have screwed up my machine by going from 0.21 to 0.22-fixes [08:03] i guess i'll just wait for 9.10 [08:03] (the frontend isn't communicating w/ the backend... sudo /etc/init.d/mythbackend restart didn't fix it) [08:03] You can upgrade now, there's not much changing. [08:04] Look in the logs to see what the problem is. [08:04] !logs [08:04] MythTV logs are stored in /var/log/mythtv/ You can use mythbuntu-log-grabber from the Applications menu to automatically post the most relevant logs to our pastebin. [08:05] okay, let me play around with it [08:05] dpkg: error processing /var/cache/apt/archives/mythtv-theme-blueosd_1%3a0.22.0+fixes22550-0ubuntu0+mythbuntu2_all.deb (--unpack): [08:05] trying to overwrite `/usr/share/mythtv/themes/blueosd/position-indicator.png', which is also in package mythtv-common [08:05] anyone know how i can resolve this? [08:05] Okay well that's nothing to do with mythbackend. [08:06] i know... just noticed it though [08:06] oh that's a packaging bug for during the upgrade [08:06] fun fun [08:06] to fix it temporarily, remove that theme package and finish the upgrade [08:07] you can install it afterward again [08:07] It may seem so but removing packages doesn't need to be scary, it won't break things. [08:08] ok, thanks [08:09] i just committed something to bzr that should help with that [08:10] (for people in the future builds) [08:10] wow, that was odd [08:10] my backend host was set to "localhost" [08:11] i changed it to 192.168.1.2 and that fixed it [08:14] where did you have to make that change? [08:35] settings, general [08:36] by the way... installed mythbuntu-repos, enabled testing, etc... ran apt-get update and apt-get upgrade... but mythfrontend is still 0.21 [08:37] mythfrontend version: 0.21.20080304-1 www.mythtv.org [08:38] that's strange... i selected the 0.22 branch [08:41] maybe i have to apt-get remove mythtv-* first? :-X [08:49] did you have jya's stuff enabled at one point? [14:01] Hello all, I upgraded to Mythbuntu 9.10 yesterday and I cannot access my USB external soundblaster now. Worked fine in 8.10 and 9.04. Nothing appears in the hardware tab of the sound configuration tool.Can anyone help? [14:18] hello [15:07] I have a question regarding connecting my mythbuntu box to my tv. [15:08] my mythbuntu only has a DVI output [15:08] my tv only has HDMI [15:09] can i use the converter here to output from the DVI to a HDMI [15:09] http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=250505501145&ssPageName=STRK:MEWAX:IT [15:22] i just want to know if it will work and if the quality is good? Any drawbacks to using this method? [15:26] hdmi == dvi + extra lines for audio [15:26] so you'll have the same results just no audio on the cable [15:26] so all those splitters really do is null terminate the audio lines [15:26] you can get them from amazon too without screwing around with auction stuff [15:27] Hello all, I upgraded to Mythbuntu 9.10 yesterday and I cannot access my USB external soundblaster now. Worked fine in 8.10 and 9.04. Nothing appears in the hardware tab of the sound configuration tool. but cat /proc/asound/cards shows the card! Can anyone help? [15:28] MythBork, you're probably best off filing someting on the forums [15:28] !forums | MythBork [15:28] MythBork: The Mythbuntu forums are located at http://ubuntuforums.org/forumdisplay.php?f=301. If you aren't getting a timely response here, there are lots of very active individuals there that may be able to help. [15:29] superm1: thanks for the amazon tip. i was just looking for a picture to show my point. [15:30] superm1: i get the audio through my sound card that has a cable with a Y-splitter for left/right channel. [15:31] i was want to make sure that the signal strength from the DVI is good enough for the TV [15:31] thanks [15:31] Yeah definitely [15:31] enjoy! :) [15:31] Bicchi: I use a DVI-to-HDMI converter [15:31] works fine. I do use a standard 2.5mm stereo patch cable for audio [15:31] good to know. my TV last night took a dump and the one i just bought doesn't have s-video output [15:32] which i find weird since it has 2 RCA inputs [15:32] RCA video being worse than S-video [15:32] my TV only listens to the analog audio on HDMI1 [16:47] !ops [16:47] Sorry I don't know about ops [17:19] mrand, ? [17:21] MythBork: Thanks for submitting your bug report, but it doesn't have anything about what version you are installing... I think you said it was the mythbuntu rc (that you picked up from the daily directory??). [17:23] mrand, I upgraded by using update-manager -d on 10/21/09 [17:23] from version 8.10 running 0.21 fixes [17:23] The bug report doesn't include what kernel version you're running. However, I see Linux 2.6.28-15-generic ehci_hcd EHCI Host Controller listed, which seems wrong to me for a 9.10 system. [17:23] 8.10 can upgrade to 9.04, not 9.10 [17:24] superm1, it happened yesterday :) [17:24] mrand, what kernel should be running? [17:26] hmmm, my desktop is on 2.6.31-14-generic, and the mythbox is on 2.6.28-15-generic [17:28] MythBork, it sounds like you upgraded to 9.04 tbh [17:28] update-manager clearly said 9.10 [17:28] Did you upgrade to 9.04 first? There may be an error in the update manager. [17:28] that's what it's sounding like to me [17:28] If you go to system -> about ubuntu, what does it say? [17:29] can you try to run update-manager -d again? [17:29] mrand, no I did not [17:29] and lsb_release -a [17:29] lsb_release -a will tell you what branch you are on [17:30] lsb_release shows: [17:30] Description: Ubuntu 9.10 [17:30] Release: 9.10 [17:30] Codename: karmic [17:32] MythBork, okay then somehow you are booting into the wrong kernel? [17:32] Ok, sounds like a bug in update manager when run with -d on an older system. It didn't update your kernel, or maybe just didn't update grub. Check and see if there is a newer version of the kernel in /boot that grub isn't show you. [17:32] what's uname -a say? [17:32] superm1, seems so [17:33] MythBork, can you install linux-image-generic? that should get you the latest kernel [17:33] I'm lagged [17:33] bbl [17:33] and linux-headers-generic too [17:33] and if after a reboot you are still on the wrong kernel, then something si wrong with your grub setup [17:33] seems a 2.6.28-15 is there, but not in grub [17:34] I'm going to update grub and reboot [17:44] well that's still a 9.04 kernel not a 9.10 kernel [17:44] something about your system is a bit messed up [17:44] can you file a bug using "ubuntu-bug update-manager" [17:44] that should gather a bunch of information about the upgrade scenario for debugging [18:15] superm1, mrand - updating kernel fixed problem [18:16] MythBork, so you are at 2.6.31 now right? [18:17] yes, just updated the bug report [18:17] sound works fine now [18:18] wonder what went wrong in that upgrade though [18:18] it would probably be a good idea to file a separate update manager bug and explain what you had to do [18:18] (sudo ubuntu-bug update-manager) [18:20] mrand: thanks for the pointers yesterday. I had already left the computer, but tried again today. The problem is that there isn't any dbgsym package for the version I'm running. [18:21] Is it possible for me to create the dbgsym package myself? [18:27] olejl, are you running a build from the PPA? [18:27] yes [18:27] in theory those should have debug symbols built into them (and not necessitate -dbgsym packages) [18:27] so can you try to apport-retrace without installing symbols and see if the trace is useful at all? [18:31] apport-retrace -s /var/crash gives me report file does not contain required fields: CoreDump Package ExecutablePathreport file does not contain required fields: CoreDump Package ExecutablePath [18:31] gdb mythfrontend.real gives me: Reading symbols from /usr/bin/mythfrontend.real...(no debugging symbols found)...done. [18:34] shame okay so something is STILL wrong with the PPA builds not getting us debug symbols :( [18:37] I haven't updated today though [18:38] I'm running r22547 [18:40] maybe I will just compile mythtv myself. What should I uninstall before doing so? [18:44] basically mythtv-* [18:45] it's too bad we can't seem to get these packages to build right though :( [18:47] I will give it a shot [19:12] I see the RC is released on mythbuntu.org, I currently have the beta, how would I update to the RC? I tried "update-manager -d" and nothing. [19:23] bobbob1016, make sure that you are doing regular apt-updates and you'll be at RC [19:26] hmm the mythbuntu "RC is out now!" page points to a dead link on ubuntu.com :) [19:26] http://www.ubuntu.com/testing/karmic/rc [19:32] ToeBee, Not here, I get "Changes from beta" and the usual [19:36] bobbob1016: yes, the page itself is fine. But it links over to a nonexistent page on ubuntu.com [19:37] this line: Underlying Ubuntu updates (see http://www.ubuntu.com/testing/karmic/rc) [19:55] hi, folks. hope everyone's doing well today. i'm struggling with major problems in the last couple days' builds of 0.22-trunk on 9.04-amd64. 0.22.0+fixes22517 was the last "good" build for me. [19:58] I'll start out with an easy one though... is gray-osd now part of one of the base packages? Its separate package is no longer compatible with the rest, but even without it installed, I can choose it from the Playback OSD menu, and seems to work fine. Probably it should be removed from Control Centre, so that doesn't try to install/uninstall the separate package, ending up with a "broken package cache" error. [20:12] The rest may be upstream mythtv issues: [20:12] 1. Playback of HD recordings using XVideo locks up the X server (nvidia 7050PV chip) after a second or two. Tried both ffmpeg & libmpeg2. X server process pegs the CPU at 100%, mythfrontend.real at 35%, screen frozen. Requires killing mythfrontend. OpenGL works, but jerky playback, so I really need to get back to XVideo. (XvMC never worked reliably on my hardware, but it also locks up now.) [20:13] 2. Program Guide during LiveTV has disappeared. I only get a completely gray screen (with live playback continuing in the upper corner as expected). Program Guide from the Schedule Recordings menu is fine. [20:16] 3. Regardless of theme used, mythfrontend rather consistently consumes 15% of the CPU when sitting idle at the main (or any other) menu. Seems that something is waking up the main event loop more often than expected? Just noticed it because my box used to be cold when idle, now it's warm, sort of a waste. [20:27] Oh yeah, and US.weeklybuilds.mythbuntu.org seems to have been down this week, but UK is fine. [20:28] hmm I think I've noticed the idle CPU spinning but only sometimes. Never really looked into it [20:33] yeah, that part has been happening for a few weeks now, since I first transitioned to 0.22, so it's not as new a behavior as the rest. possibly related to the new qt4.5 framework? [20:34] I think I was seeing it back on .21 actually [20:38] maybe it's mythweather or something else grabbing updates. guess i should turn off all plugins and see if that makes a difference. [20:40] ppww, that is because US.weeklybuilds.... is the wrong address. I'm testing the fixed package now [20:43] really? well, then "dpkg-reconfigure mythbuntu-repos" inserts the wrong info then. [20:50] ppww, what did i just say? [20:51] "I'm testing the fixed package now" [20:51] oh, you meant the mythbuntu-repos package.... thanks much. [20:52] yea [20:53] give me a few minutes and i'll push the update [21:44] <]Oscar> I'd like to build a diskless client, just as MCC do, but not using it. I tryed with just ltsp-build-image but the client works as a thin client, using server's cpu, etc. which is the trick? [21:48] ppww, which version of mythbuntu-repos do you have installed? [21:49] the file timestamp is 2009-10-04 11:49, grabbed from http://www.mythbuntu.org/files/mythbuntu-repos.deb [21:49] ppww, do this [21:49] dpkg -l mythbuntu-repos [21:50] 5-0ubuntu0+mythbuntu~karmic [21:50] ppww, ok try this [21:50] which is odd, since i'm running jaunty [21:50] ppww, thats fine actually ;) [21:50] do this [21:51] apt-get update and apt-get install mythbuntu-repos [21:52] ppww, actually, it just got published, so you may have to wait a few minutes [21:53] got it, now 6.1-0ubuntu0+mythbuntu~jaunty, and it retrieved http://weeklybuilds.mythbuntu.org Packages files ok. [21:53] good deal [21:53] you didn't have to dpkg-reconfigure it did you [21:54] not sure, i just did the reconfig automatically, assuming it would have remembered my previous "UK" selection. [21:54] yea it should have remembered your previous selection [21:55] do another apt-get update [21:55] because it shouldn't be using weeklybuilds.m.o unless you have US selected [21:57] like i said, i already did dpkg-reconfigure, and selected US, that's why. so it seems fine. [21:57] ppww, yea, except I just found another problem ;) [21:57]