[00:47] <ryanakca> valorie: OK, email me your postal address and I'll send some over. myIRCnick@kubuntu.org
[00:48] <DarkwingDuck> Any idea on an ETA for the new branding on the website?
[00:52] <ryanakca> DarkwingDuck: I think this week
[00:52] <DarkwingDuck> Okay cool. :)
[00:52] <DarkwingDuck> I still need to pull the SVG for the new logo
[00:52] <DarkwingDuck> And the font.
[01:03] <valorie> ryanakca: sent
[01:04] <valorie> thanks again
[01:36] <imbrandon> evenign all
[02:38] <ScottK> DarkwingDuck: OK.
[02:38] <ScottK> Evening imbrandon
[02:40] <jjesse> evening
[02:52] <ScottK> mmmm.  Nice to be home.  Downloads going ~30 times faster than they did in the hotel.
[02:52] <jjesse> total
[02:52] <jjesse> hotel internet always sucks
[03:11] <DarkwingDuck> jjesse: I talked to nixternal today, I think we are going to leave this doc release and bug run for Maverick to save the translators
[03:14] <jjesse> really??? why it is a lts
[03:14] <jjesse> we should be fixing bugs on lts's
[03:14] <jjesse> including doc bugs
[03:15] <jjesse> hold on brb
[03:17] <jjesse> DarkwingDuck: would be interested to hear nixternal's reasoning
[03:18] <DarkwingDuck> jjesse:
[03:18] <DarkwingDuck> jjesse: I think that we should fix what we can and push it out like Matt talked about in May
[03:19] <jjesse> agreed
[03:19] <DarkwingDuck> I don't know nixternal's reasoning when I talked to him but, I agree with you that because it is an LTS we should bug fix ASAP
[03:19] <DarkwingDuck> I know he has no time so I'm guessing it's gonna be us to fix
[03:19] <DarkwingDuck> It's may 1st. How much time will you have this week?
[03:20] <jjesse> dont' know
[03:20] <jjesse> the problem is buildign the packages
[03:20] <jjesse> and that's what nixternal really hates doing
[03:20] <jjesse> unless you know how to do it?
[03:20] <jjesse> may 1st is today
[03:20] <jjesse> was today
[03:20] <DarkwingDuck> Yeah
[03:20] <DarkwingDuck> I don't know how to build... Never done it but, I've been wanting to learn.
[03:20] <jjesse> i think we just need to get as many fixed as possible and then figure out how to update
[03:21] <DarkwingDuck> Agreed
[03:22] <DarkwingDuck> I've assigned myself 11
[03:23] <DarkwingDuck> there are three new
[03:23] <DarkwingDuck> That is 14 reported bugs.
[03:23] <jjesse> and i have think i 1 or 2
[03:24] <DarkwingDuck> You want to talk what you have and those new ones and see what we can kick out by next fri night?
[03:24] <jjesse> sure
[03:24] <jjesse> asign them to me pleaze
[03:25] <DarkwingDuck> Yup, what's your LP name?
[03:25] <DarkwingDuck> jjesse?
[03:25] <jjesse> yea
[03:25] <DarkwingDuck> kk
[03:26] <DarkwingDuck> We'll kick these out by fri night and we'll get them rebuilt. Just upload to the lp:kubuntu-docs branch or, upload the paches to the bugs and I'll figure out what branch to place them in.
[03:30] <DarkwingDuck> jjesse: assigned
[03:30] <jjesse> awesome thanks
[03:31] <DarkwingDuck> NP We'll get this kicked out. Let's go ahead and upload to the maverick branch so they are fixed there for +1 anyway.
[03:38] <DarkwingDuck> nixternal: when you get a chance ping me.
[03:38] <jjesse> agreed
[03:38] <jjesse> commit to both lucid and maverick
[03:38] <jjesse> is lucid now lp:kubuntu-docs/lucid and maverick lp:kubuntu-docs?
[03:38] <DarkwingDuck> correct
[03:39] <jjesse> cool will make sure i have the latest updates
[03:39] <DarkwingDuck> sweet. Up downloading to my laptop and desktop too
[03:40] <jjesse> time for bed for me
[03:40] <DarkwingDuck> Okay, :) I'll hunt you down on friday :P I'll pop an email to ya when I finish a bug
[03:41] <jjesse> cool thanks
[09:12] <Tm_T> ScottK: I don't know how to install without damaging the current installation, virtual machine isn't option I guess, with 512 MiB ram
[09:18] <imbrandon> Tm_T: what ya after ?
[09:19] <Tm_T> imbrandon: ppc images needs install test
[09:19] <imbrandon> Tm_T: ah
[09:20] <Tm_T> but I don't want to crap out the system I need to use
[09:20] <imbrandon> right
[09:20] <imbrandon> yea thats not a good thing
[12:00] <ScottK> Tm_T: OK.  I guess it's up to nixternal then.
[12:12] <Tm_T> shame I can't help more ):
[13:28] <oxymoron>  Hi guys, how do I fix this? http://pastebin.com/Cs8zah5G
[14:04] <jussi> ScottK: yup, it works. let me know if you need something else. :)
[15:20] <Daskreech> Hallo. Is it kdeinit that starts the kdebluetooth on login ?
[15:34] <sithlord48> hey devel ppls. can some one possibly expain this oddity i had durring install, i installed (saveing my /home partition) after install my video worked 100% desktop effects nice plymouth (i have a raideon 4830HD) . after first reboot i had lost glx and 3d accel, and was prompted by jockey to install fglrx driver. now ulgy plymouth , can anyone explain this oddity
[15:59] <Quintasan> sithlord48: this a problem with the driver itself if I am informed correctly. There was a solution somewhere on softpedia but I can't say for sure whether it works.
[16:00] <sithlord48> ok but what driver was i useing before restart the radionhd one?
[16:00] <Quintasan> sithlord48: probably the opensource radeon
[16:00] <Quintasan> sithlord48: wait, you have installed FGLRX, right?
[16:01] <sithlord48> now i have
[16:01] <Quintasan> sithlord48: I think Kubuntu uses radeonhd by default
[16:01] <sithlord48> i know its causeing my ulgy plymouth, but i want the open driver if my 3d is gonna work
[16:01] <Quintasan> sithlord48: 3D is NOT working for you when you are using FGLRX?
[16:02] <sithlord48> no everything is working fine w/ fglrx
[16:02] <Quintasan> sithlord48: if you want to fix the plymouth you can try this -> sithlord48: if you are running fglrx now -> http://news.softpedia.com/news/How-to-Fix-the-Big-and-Ugly-Plymouth-Logo-in-Ubuntu-10-04-140810.shtml
[16:03] <Quintasan> sithlord48: though I can't guarantee it will work
[16:03] <sithlord48> after installed the os on that first boot i had working 3d accel , i restarted after installing a few programs none related to xorg or video drivers. after the system came back up i had no 3d accel and the hw wizard told me i should install a "restricted driver"
[16:04] <sithlord48> i would like to know what happened to the working 3d accel after the first reboot
[16:10] <sithlord48> i guess i will try the plymouth fix, anyway since its all ulgy. im just annoyed that the glx and 3d worked w/ the opendriver for 1 time and not another.. (perhaps its a bug in that drver too)
[16:24] <DarkwingDuck> grrrr... I'm really sick of the ram drain from Firefox
[17:49] <imbrandon> google chrome
[19:17] <Quintasan> apachelogger: now that I know the basics Qt seems easier than before :P
[19:18] <ofirk> Riddell: hey :D
[19:19] <ofirk> Riddell: the release notes for Lucid points to http://releases.ubuntu.com/kubuntu/10.04/ for iso download
[19:20] <ofirk> Riddell: why not point to the download page, where more download options and some explanations are available?
[20:00] <Riddell> ofirk: good idea, go ahead
[20:01] <maco> Riddell: can you change the kubuntu.org header to have the new logo?
[20:02] <Riddell> maco: no that needs sysadmins to change the theme which they should be doing next week anyway for ofirk's new theme
[20:02] <maco> does ofirk's new theme have the new logo?
[20:03] <Riddell> yes
[20:18] <ghostcube> meeeeh jackd still not in main ;(
[20:23] <ofirk> Riddell: are you in contact with the sysadmins?
[20:27]  * Tm_T huggles ofirk
[20:28] <ofirk> wow, thanks :)
[20:28]  * ofirk wonders why?
[20:29] <Tm_T> because hugging is fun?
[20:29]  * Tm_T hides
[20:30] <ofirk> lol
[20:30]  * ofirk huggles Tm_T back :)
[22:15] <apparle> is there any software center for kubuntu/KDE... or is one being developed?
[22:19] <apparle> anyone here
[22:20] <ulysses> You can install the software-center package too
[22:23] <apparle> ulysses: you mean the existing on for ubuntu?
[22:23] <ulysses> yes
[22:24] <apachelogger> o/
[22:24] <apachelogger> Quintasan: sounds about right ^^
[22:25] <apparle> So basically if I am thinking of making a software center for project for SoK it would not be creating which already exists
[22:26]  * apachelogger imagines that difficult in a KDE context
[22:27] <apparle> apachelogger: didn't understand
[22:27] <apachelogger> apparle: how do you plan to make this work across all distros?
[22:28] <apparle> apachelogger: basically the app will call kpackagekit which is there on all distros
[22:28] <apachelogger> that is a false assumption
[22:28] <apachelogger> packagkit does somewhat work on fedora and ubuntu/debian
[22:28] <apachelogger> but that is about it
[22:28] <apachelogger> also some distros resent the concept of pk
[22:29] <apachelogger> so IMHO you'd need a generic abstraction ontop of all the packaging mess, which is something I wanted to do for age ^^
[22:30] <apachelogger> the problem is, when making software for KDE you must not make assumptions about what is there or not, from a KDE pov the only thing that is there is KDE + its deps
[22:30] <Sput> for some distros, pk isn't nearly sufficient too :)
[22:31] <apachelogger> technically you shouldnt even consider distro integration for starters
[22:31] <apachelogger> Sput: which is probably why they do not like it ;)
[22:31] <Sput> apachelogger: yep :)
[22:31] <apparle> so... I think targetting Kubuntu would be good enough... but at least it would be a start
[22:32] <apachelogger> apparle: well, it is Season of KDE, not Season of Kubuntu :/
[22:32] <apachelogger> proposing it to be kubuntu-only will render the likelyhood of getting accepted towards 0
[22:33] <apachelogger> </personal opinion>
[22:33] <apparle> apachelogger: would start off with kpackagekit... and then with time it can include support for various distros package managers
[22:33] <apparle> and what happened to kgrupeditor....
[22:34] <apparle> is there an app for grub2
[22:34]  * ulysses uses GRUB legacy
[22:34] <apparle> I could do that for project
[22:35] <apparle> kgrubeditor2
[22:36] <apachelogger> apparle: I do not think that is a good approach... that way you do not only bind it to a very specific package management software but only one UI version of it
[22:37] <apachelogger> apparle: if I were you I would propose to sort the underlying mess first ... i.e. create a backend-agnostic KDE API for package management interactions
[22:37] <apachelogger> kind of what KAuth is for authentication
[22:37] <apparle> ohh
[22:37] <apparle> apachelogger: but as you know I don't have any damn experience in development
[22:37] <apachelogger> that would not only allow you to create a software center that is truely indepedent of a backend, but also solve a whole bunch of other problems
[22:37] <apachelogger> key word: package splitting
[22:38] <apachelogger> apparle: I do not know the specific requirements towards a SoK proposal, but maybe you could just do the theoretical stuff ;)
[22:40] <apachelogger> apparle: I would bring this up in #kde-devel and ask for some opinions
[22:41] <apachelogger> but from where I am standing, only draftig up a design for such a system would be worth a lot
[22:41] <apparle> apachelogger: I don't mind working on somepart of it
[22:42] <apparle> apachelogger:  you are talking about KDE api for package management or the whole software center stuff?
[22:42] <apachelogger> apparle: former
[22:44] <apparle> no problem.... coz later would be very simple based on the former
[22:44] <apachelogger> exactly
[22:44] <apachelogger> well
[22:45] <apachelogger> let's say "easier" ... a software center itself is enough a complex piece of software IMHO
[22:46] <apparle> apachelogger: :D
[22:46] <apparle> apachelogger: its just that all the ideas I am coming up with are way above my level
[22:47] <apparle> is there any kgrubeditor for grub2
[22:47] <apparle> apachelogger: you started stuff at kde-devel
[22:47]  * apachelogger thinks that most ideas can be reduced by going away from thinking about end-user ready products :)
[22:48] <apparle> apachelogger: :D
[22:48] <apparle> I would like to work on that api thing.... but I don't know whom to approach... it will need a mentor for starters.....
[22:49] <apparle> apachelogger: and I would need a lot of mentoring :D
[22:54] <apparle> apachelogger: you there?
[22:55] <apachelogger> apparle: just post to the kde-devel mailing list
[22:56] <apparle> apachelogger: oh... i thought you were on #kde-devel
[22:56] <apparle> apachelogger: as for the kgrubeditor you know anyone working on it for grub2
[22:57] <apachelogger> no idea
[23:05] <apparle> apachelogger: tell me if anything happens.... I am not always in kubuntu-devel but am usually in kubuntu (I am yet to become a developer :))