[00:15] why will tvtime work but myth doesnt do squat === Seeker`_ is now known as Seeker` === ahhughes_ is now known as ahhughes [02:21] which mythtv protocol version does mythbuntu 9.10 support? [02:24] bunder: $ mythfrontend --version will always give you the current network protocol version,among other important info. [03:34] hey guys i had a question do i need to install the restricted drivers to properly connect my tv tuner to my machine [05:08] my disk is filling up with messages logged in /var/log/gdm/:0-greeter.log. I think the problem is that two window managers are being started (xfwm4 and metacity). I think that this is because both have files in /usr/share/gdm/autostart/LoginWindow. Can I just delete one? Or is this analysis wrong? [05:18] xfwm4 is started by mythbuntu-gdm-window-manager.desktop (it includes the line Exec=xfwm4) which comes from mythbuntu-gdm-theme package. [05:19] metacity is started by metacity.desktop which comes from gdm package. Does that mean these two packages conflict? [05:26] what are the messages logged to that log saying? [05:26] i mean what you say sounds plausible [05:27] Window manager warning: Screen 0 on display ":0.0" already has a window manager; try using the --replace option to replace the current window manager. [05:27] Window manager warning: Failed to read saved session file /var/lib/gdm/.config/metacity/sessions/1057e55ebdbfac9c126645249737304300000022070009.ms: Failed to open file '/var/lib/gdm/.config/metacity/sessions/1057e55ebdbfac9c126645249737304300000022070009.ms': No such file or directory [05:28] repeated over and over. === fleers is now known as fleers_ [05:29] yup that sounds like the situation to me then [05:30] go ahead and remove one of them from that directory and file a bug [05:31] do you see both those files on your system? (Mine is 9.10 + mythbuntu packages)? [05:31] all of the boxes i have are either full mythbuntu or 9.10 + mythbuntu-control-centre and some mythtv packages (no mythbuntu-default-settings) [05:32] btw, the infinite logging goes away once I log in, and stays away even when I log out. Seems to come back on reboot. [06:13] I've never used OpenID before. the Mythbuntu site requires OpenID. On a google account, I've enabled a profile URL. I think that that should allow me to log in with that as my openid. But it seems to get ignored. What am I likely to be doing wrong? [06:24] there is a special URL for google accounts [06:24] DHR, http://lists.openid.net/pipermail/openid-general/2009-July/009271.html [06:24] [lists.openid.net] [OpenID] What is my Google OpenID URL? [06:24] use that url listed in there to log in with a google openid [06:28] tried that. Did something (that involved google asking me if it was OK), but popped back to the mythbuntu page as if I'd not logged in. Same happened when I used my google profile URL. [06:29] i dunno. i'm able to log in with mine :) [06:29] it's easier to use your launchpad login imo though [06:29] and easier to remember [06:35] yup, my launchpad account worked. Thanks! [06:38] mythbuntu.org's time is out. It think the time is x:14 (where x depends on timezone). [06:38] Daviey, ^ [06:48] hmm. I guess that bug reports go in bugs.launchpad.net -- no separate bug database for mythbuntu. This isn't stated obvious places. [06:48] [bugs.launchpad.net] Launchpad Bugs [07:12] just created https://bugs.launchpad.net/ubuntu/+source/mythbuntu-gdm-theme/+bug/523639 [07:12] [bugs.launchpad.net] Bug #523639 in mythbuntu-gdm-theme (Ubuntu): “dueling window managers fill disk with logging flood” [08:37] i have an uptodate ubuntu 9.10 64bit with mythtv and nuvexport/mencoder etc installed from the repositories, recording works fine but when i'm trying to nuvexport-xvid it always stops at around 99% and says that it died early [08:37] anyone else have this problem? [08:38] oh, and by the way, does mythbuntu install include all the necessary codecs for encoding? === KB1JWQ is now known as PFY === PFY is now known as KB1JWQ [21:49] kees, am I just supposed to do "python check-bios-nx" from a command line? [21:50] tgm4883: you can, though it's not very interesting. try it with --verbose for more details [21:50] ah [21:50] yea I didn't get jack the first tim [21:51] it just sets an exit code (non-zero means "fix your bios") [21:51] I think i'm ok [21:51] This CPU has 'nx' in the flags, so the BIOS is not disabling it. [21:51] cool [21:52] would be nice to know that I was already setup with the right kernel though [21:52] yeah, I'm trying to do one piece at a time. this is strictly "is my bios dumb?" :) [21:53] something like "This CPU has 'nx' in the flags, so the BIOS is not disabling it. You also have pae activated. According to kees, your security is the bees knees" [21:53] hehe