[02:09] <dj_segfault> Trying to do software update and autobuilds is timing out.  "W: Failed to fetch http://us.autobuilds.mythbuntu.org/mythbuntu/trunk-0.22/ubuntu/dists/karmic/Release.gpg  Could not connect to us.autobuilds.mythbuntu.org:80 (87.117.230.144), connection timed out"
[02:10] <silverdulcet> dj_segfault: yeah noticed it was timing out yesterday as well, you could reconfigure the auotbuilds package and try the uk repo, I did that for a while when the us repo was down for a while last time.
[02:11] <dj_segfault> Heh.  Ok.  Just change us to uk in the url?
[02:12] <silverdulcet> dj_segfault: I think you can do a dpkg-reconfigure mythbuntu-autobuilds err, whatever the package is called. Its a deb now.
[02:12] <silverdulcet> then it asks you which repo you want to use, one of the options is uk or us.
[02:13] <silverdulcet> sorry its mythbuntu-repos.deb
[02:13] <dj_segfault> Thanks.  It's mythbuntu-repos for the record.
[02:14] <silverdulcet> you could edit it in the text file, but if you do it through the deb, it keeps things nice and neat for upgrades from them, etc.
[02:15] <dj_segfault> Worked great.  Thanks.
[02:17] <silverdulcet> dj_segfault: np, was kismet, was thinking of doing the same thing if the us repo didn't respond again. ;-p
[02:17] <dj_segfault> I noticed it yesterday too, but I figured it would go away.  Is there someone to notify or will they figure it out?
[02:23] <silverdulcet> dj_segfault: not sure who runs it, last year when it was down it was for quite a while, pretty sure they know about it.
[02:23] <dj_segfault> OK, I guess the squirrels on the treadmill got tired.  I'll leave it as UK for now.  It's fast enough that way
[07:07] <ripperda> hey guys, I'm trying to modify what the power button on my gyration remote does, but I'm having trouble figuring out how it routes through the system. does anyone have experience with that?
[13:32] <Shred00> us.autobuilds.mythbuntu.org appears to be down
[13:33] <Daviey> bah
[13:36] <innatech> Having a problem w/M-buntu Karmic and an HVR-1600 card (CX-18 based) -- S-Video is recording only green bars and garbled audio.
[13:38] <Daviey> Shred00: I've changed the IP address, so you either need to flush your cache or wait for it to expire
[13:38] <Daviey> Shred00: or change to another mirror :)
[13:40] <Shred00> Daviey: :-(  typically one should reduce the TTL to something very small and wait for (old) TTL time to expire before one makes an IP change so that users are not left holding on to an old record for (up to) TTL.
[13:40] <Shred00> i guess i will just have to wait.  i just sucks that apt sits waiting and waiting and waiting until it times out.
[13:41] <Daviey> Shred00: well in this instance it serves no purpose reducing the TTL as the old record doesn't work
[13:42] <Daviey> Shred00: sed -i 's/us.autobuilds/uk.autobuilds/g' /etc/apt/$sourcesfile ; would be a much faster fix for you
[13:42] <Shred00> Daviey: i think you misunderstand.  in advance of changing the ip, you reduce the ttl on the existing RR and then wait for that time before you change the ip.  so if the ttl is a week, you reduce it to 5 minutes, then wait a week before you make the change.
[13:43] <Daviey> Shred00: i think you misunderstand, there isn't a RR
[13:43] <Shred00> before the ip change?
[13:43] <Daviey> There never was
[13:44] <Shred00> how did us.autobuilds.mythbuntu.org ever resolve then?
[13:44] <Daviey> It doesn't need a RR to resolve
[13:44] <Daviey> the TTL is 1hr which is hardly painful anyway.
[13:44] <Shred00> how does us.autobuilds.mythbuntu.org not need an RR?  nobody could ever resolve that name without one.
[13:45] <Shred00> here is the (old) RR right here:
[13:45] <Shred00> us.autobuilds.mythbuntu.org. 166 IN     A       87.117.230.144
[13:46] <Shred00> here is the new one:
[13:46] <Shred00> us.autobuilds.mythbuntu.org. 3600 IN    A       87.117.230.247
[13:46] <Daviey> Shred00: by RR i assumed you mean'tRound Robin, but i guess you mean Resouce Record/
[13:46] <Shred00> yes.  RR == Resource Record
[13:46] <Daviey> Shred00: I know what the entries are, *I* just changed them
[13:47] <Shred00> Daviey: but you were denying there was an RR which clearly there had to be so I had to provide evidence to refute your claim that there wasn't one.
[13:47] <Daviey> Shred00: it looks like you had a TTL of 166, so it's hardly a long wait for you anway.
[13:48] <Daviey> Shred00: I'm not sure what you are trying to prove.
[13:48] <Shred00> in any case, the way you minimize the impact of changing an ip is to first reduce the TTL of the existing record.  then wait that long before you make the change
[13:49] <Daviey> Shred00: Ok, next time we have a mirror that doesn't resolve.. i'll ensure that i reduce the TTL to leave people hanging longer.
[13:49] <Shred00> in any case.  it's clear that the problem was just transient.
[13:49] <Shred00> how does reducing the TTL leave people hanging longer?
[13:49] <Daviey> 87.117.230.144 is a DEAD mirror, so reducing the TTL for that is foolhardy.
[13:50] <Daviey> So you suggest i reduce the ttl from 1hr (which is pretty short anyway) to 5 mins, wait an hour then make the change?
[13:50] <Daviey> makes no sense.
[13:50] <Shred00> i take this was an "emergency" change then?
[13:51] <Daviey> take it how you please.
[13:51] <Shred00> you didn't say that originally.  you simply said you changed the ip.  i interpreted that as this was a planned change.
[13:55] <Shred00> anyway.  thanx for taking care of it.
[14:01] <DuCkNeT> ouch...
[14:01] <DuCkNeT> i guess he woke up on wrong side of the bed...
[20:08] <tjw> is http://us.autobuilds.mythbuntu.org going to come back eventually?
[20:09] <rhpot1991> tjw: its being worked on, last I saw
[20:10] <tjw> ok, it's been down for a few days, so i was just wondering if i need to reconfigure it to use a different server or something
[20:12] <tjw> i just did 'sudo dpkg-reconfigure mythbuntu-repos' and chose PPA instead of US and that seems to work
[20:12] <tjw> fwiw
[20:12] <tjw> at least I'm hoping they have the same files
[20:36] <slonbg> hi. I'm logged in to my mythbuntu box over ssh. I'm trying to restart the GUI from there with sudo /etc/init.d/gdm stop. Unfortuantely, this command never exits (i.e. does not shut down gdm). Instead, a pupup jumps on the tv with the text "There already appears to be an X server running on dysplay: 0. Should another display number is tried?". How can I restart the GUI from a ssh login?
[20:38] <rhpot1991> slonbg: sudo /etc/init.d/gdm restart
[20:39] <slonbg> rhpot1991: I hit ctrl-c on the gdm stop. with restart, the same popup happen
[20:40] <rhpot1991> is another user logged in or something?
[21:30] <slonbg> rhpot1991: sorry for the delay. No, no other user. Its a standalone machine, connected to the TV. Only remote there. It auto log in to start mythtv. then I login over ssh.
[21:33] <rhpot1991> slonbg: what version of mythbuntu?
[21:34] <slonbg> rhpot1991: 9.04
[21:37] <slonbg> rhpot1991: hmmm. ps aux displays 2 equal gdm lines for /usr/sbin/gdm ...and one for /usr/bin/X .... -auth /avr/lib/gdm/:0.Xauth ...
[21:38] <slonbg> the gdm line are like: /usr/sbin/gdm --config=/etc/gdm/gdm-cdd.conf
[21:39] <slonbg> one has flags Ss, the other only S