[00:17] <mycosys> anybody here have experience with pre-0.24 OSD theming
[00:18] <mycosys> iamlindoro is having delusions
[06:18] <mycoDA> 10.04lts time
[06:18]  * mycoDA forsees great pain
[07:25] <mycosys> you guys know what do-release-upgrade does that synaptic wont?
[07:25] <mycosys> pretty sure do-release-upgrade will break my install in a nasty way
[07:26] <mycosys> have a number of repos enabled on jaunty that are a fair way ahead of what is standard on karmic
[07:26] <mycosys> ie weekly builds lol, and winswitch, and deluge, and medibuntu
[07:27] <mycosys> have synaptic doing download only atm - so that when it finishes i can chose one or the other
[07:46] <mycosys> aaaaaaaarghhhhhhhhhhhhhh
[07:47] <mycosys> need a way to upgrade without killing the mythbuntu repos
[07:47] <mycosys> you around superm1?
[07:48] <mycosys> tgm4883
[07:48] <mycosys> any of the other super amazing actually helpful people
[13:05] <superm1> mycosys, i'm here now for a little bit
[13:05] <superm1> do-release-upgrade does thing sthat can't be represented in apt
[13:05] <superm1> so conf file migrations, forced package removals
[13:06] <superm1> particularly ordered installs
[13:06] <superm1> it disables 3rd party sources before hand
[13:07] <superm1> it's less likely to break your box than s/jaunty/karmic/, but if it does for some reason, it's better to revert to to that after trying do-release-upgrade (or update-manager -d)
[13:07] <superm1> in any case, if mythbuntu repos are disabled, it's fairly easy to re-enable them
[13:07] <superm1> it's just a conffile change or dpkg-reconfigure mythbuntu-repos
[13:11] <mrand> mycosys, superm1: Note that do-release-upgrade has a little known, but important option that was not the default last time I checked (which has admittedly been a while): "-m desktop"  You'll find it randomly mentioned, or not, in the wiki's and online documentation, and so therefore I can't tell you what it does, but it is typically recommended for systems that are not servers.
[13:12] <superm1> my best guess would be  it probably sets it to -desktop mode, looking for a -desktop meta package
[13:12] <superm1> or installing one if it's not there
[13:12] <superm1> Daviey, ^
[13:14] <superm1> mrand, looking at the source it looks like that's actually now "-m MODE"
[13:15] <superm1> where modes are 'desktop' or 'server'
[13:18] <mrand> superm1: the desktop meta package rings a bell when I asked before.
[13:19] <mrand> superm1: I think the problem that many run into is that it defaults to server (or at least, used to)
[13:21] <mrand> yet the documentation says no such thing
[13:22] <superm1> we didn't start having a metapackage it recognized for a few releases
[13:23] <superm1> probably 8.10 i think
[13:24] <superm1> /usr/lib/python2.7/dist-packages/DistUpgrade/DistUpgradeCache makes references of running in 'desktop' mode because of particular package keys installed
[13:27] <superm1> we have a special key in that config now for mythbuntu-desktop
[13:28] <superm1> it actually might need some work because it calls out mythbuntu-artwork which we dont use any more
[13:31] <mycosys> thx superm1 & mrand
[13:32] <mycosys> saw that mode thing when i did do-release-upgrade --help
[13:34] <mycosys> appreciate the re-assurance
[13:45] <judget> does anyone know what is up with the ppa repos--
[13:46] <mycosys> ?
[13:48] <mycosys> just saw how rude you were on -users - ur not a nice person are you? did you pay your support subscription?
[13:50] <judget> ??
[13:50] <judget> Failed to fetch http://ppa.launchpad.net/mythbuntu/0.24/ubuntu/pool/main/m/mythtv/libmyth-0.24-0_0.24.0+fixes.20110322.c2baf1b-0ubuntu0mythbuntu2_i386.deb 404  Not Found
[13:52] <judget> did not mean to appear rude I was just agreeing with the advice to post the issue here
[13:52] <mycosys> kk
[13:52] <mycosys> not using .24 myself, and not a package maintainer, so dont know
[13:53] <judget> just wanted to let someone know that there may be an issue with the ppa repos
[13:53] <judget> that is one of a series of messages. appears an issue with the ppa site. who should i let know?
[13:53] <mycosys> need to do an update
[13:54] <mycosys> is 20110325
[13:54] <mycosys> sudo apt-get update
[13:55] <judget> ok tx ill try
[14:31] <mycosys> aaaaaaaaaaaaaaaaaaaaaaaaaargh is blocking at stopping bluetooth
[14:31] <mycosys> is hanging if i run /etc/init.d/bluetooth stop too
[14:31] <mycosys> any ideas superm1 or mrand?
[14:41] <Daviey> superm1, o/
[14:41] <Daviey> superm1, In regards to looking for a -desktop meta package, that is unreliable.... The current favoured way of seeing if it is a desktop is pidof /usr/bin/X
[14:47] <mycosys> ogod
[14:48] <mycosys> having finished the upgrade, apt-get upgrade -f wants to remove startup-tasks system-services ubuntu-minimal upstart-compat-sysv upstart-logd
[14:48] <mycosys> PLEASE tell me they are depicated in karmic :(
[14:48] <mycosys> daviey? superm1? mrand?
[14:50] <mycosys> they conflict upstart?
[14:52] <Daviey> mycosys, honestly, i have no idea.. you are upgrading TO karmic?
[14:52] <mycosys> uhuh
[14:52] <mycosys> so i can get to lucid
[14:52] <mycosys> still on jaunty
[14:53] <mycosys> looks like they conflict with upstart
[15:27] <mycosys> gotta say you guys are one heck of a lot more helpful than the dudes on #ubuntu
[15:29] <dewman> howdy
[15:30] <dewman> quick question....I just did a o/s reload and due to some wierd items going on, I got the db restored with no issues, but one thing i noticed is that my recording directory and a few other dirs underneath it are owned by messagebus and root
[15:31] <dewman> which is really odd.
[15:31] <dewman> i was originally on 10.04 and went to 10.10
[15:36] <mycosys> not very helpful, but why?
[15:36] <mycosys> 10.04 is lts
[15:38] <mycosys> could try doin what i am doing atm after goin 9.04 to 9.10 - apt get upgrade -f
[15:40] <dewman> o/s reload is already done. =)
[15:41] <mycosys> i am having to do it several times to get it all done
[15:41] <mycosys> plenty of stuff blocking
[15:42] <dewman> its just weird that some of the dir's ownership got changed
[16:56] <mycosys>  is there some way to make karmic wait for fsck to complete on startup BEFORE deciding not to mount a drive and continue on?
[16:56] <mycosys> completed upgrade to karmic, got the shock of my life when i found one of my drives unmounted, eventually figured out fsck was running in the background and it had continued on
[16:57] <mycosys> even seeing its progress would be handy
[18:55] <tgm4883> dewman, it is a little weird that they are now owned by messagebus and root, but I could guess why
[18:56] <tgm4883> it's not odd that they changed ownership after a reinstall
[18:56] <tgm4883> at least not that odd for home users
[19:16] <dewman> tgm4883, yeah odd...Owell, I 775'd and mythtv:mythtv to everything...so it should be all set.
[19:16] <dewman> err, at least to the recording drive
[19:18] <tgm4883> ok
[19:19] <tgm4883> should be working again
[19:29] <qwebirc268> hi all
[19:29] <qwebirc268> i have a microsoft remote
[19:29] <qwebirc268> runring mythbuntu 10.10
[19:29] <qwebirc268> on freshh install remote works but for a few buttons
[19:30] <qwebirc268> used mythcontrol centre to try a new remote
[19:30] <qwebirc268> now the remote doesnt work with mythbuntu
[19:30] <qwebirc268> is this a bug in mythbuntu 10.10?
[19:31] <qwebirc268> remote used to work fine in previous versions
 used mythcontrol centre to try a new remote
[19:39] <tgm4883> What does that mean?
[19:39] <tgm4883> You can't just pick random remotes and expect things to work
[19:40] <qwebirc268> i am using mce remote
[19:40] <qwebirc268> was working
[19:40] <qwebirc268> but some buttons wasnt
[19:40] <tgm4883> ok
[19:40] <qwebirc268> i just went into mythcontrol center to change
[19:41] <tgm4883> brb
[19:58] <qwebirc268> is anyone using devinput for their remote
[20:00] <galorin> Got a nova-t not showing up after a reinstall, I know there is a fix, but can't remember what it is.
[20:02] <qwebirc268> lol great
[20:03] <qwebirc268> whats the use of mythcontrol center if its just going to break things]
[20:03] <galorin> It makes life fun for us.
[20:03] <qwebirc268> i can see in hardware.conf it generates remote = /de/lirc0
[20:04] <qwebirc268> */dev/lirc0
[20:04] <qwebirc268> that doesnt exist
[20:04] <qwebirc268>  ls -al /dev/input/by-path/
[20:04] <qwebirc268> 9 2011-03-26 19:19 pci-0000:00:09.2-event-ir -> ../event5
[20:04] <qwebirc268>  pci-0000:00:0a.2-event-ir -> ../event7
[20:05] <qwebirc268> i am guesing this is my reciever right?
[20:05] <qwebirc268> i have tried to configure the hardware.cong using devinput
[20:05] <qwebirc268> no joy
[20:09] <rhpot1991> qwebirc268: sounds like you have a generic mce device which run as input devices now
[20:09] <rhpot1991> unfortunately there isn't a real easy way to fix missing or incorrect buttons on these
[20:10] <rhpot1991> you could setup lirc to use devinput and then map things in there
[20:16] <qwebirc268> hmm
[20:18] <qwebirc268> so the deafault mappings
[20:18] <qwebirc268>  /usr/share/lirc/remotes/devinput/lircd.conf.devinput
[20:18] <qwebirc268> wont work with mce?
[22:32] <Seeker`> I've got a nova-t 500 remote tha tisn't working after doing an update
[23:47] <Teligard> Hello
[23:47] <Teligard> I'm trying to understand where I'm going wrong in the configuratio of my Ubuntu/Mythbuntu install
[23:48] <Teligard> I get asked 5+ times to enter a new password into mysql
[23:48] <Teligard> I'm wondering if this is normal, or if I need to do something different
[23:52] <Teligard> I'm wondering if 1. this is normal, 2. if this could be part of my issue with getting the backend server properly configured, and 3. if this is what is causing the need for me to do a manual setup of the mythconverg database and addition of the mythtv user
[23:52] <Teligard> I've been dealing with it for the past two days (and countless reinstalls of mythbuntu), and it's driving me batty.