[00:47] <neversfelde> Riddell: it is bug #525658 and I am mostly offline for some days, sorry for it :( I cannot correct anything from now on :(
[01:29] <Riddell> new ubuntu logo went public I see
[01:36] <Riddell> ScottK: the designer is still working on designs for the kubuntu logo, we'll get some options based on thoughts that me and seele had, we can choose between them or get more iterations as we see fit
[01:37] <seele> the xubuntu logo is cute with the little mouse in the circle
[01:37] <seele> too bad we couldnt get kubuntu done in time for this announcement though
[01:37] <seele> looks like we dont exist
[01:38] <Riddell> that was done by the xubuntu guy
[01:38] <seele> ah
[01:40] <Riddell> they didn't want to rush the kubuntu logo, which I think it a good thing
[01:42] <Riddell> where was this announced anyway?  just blogs?
[01:43] <Riddell> ~identica dent New logo announced for Ubuntu.  Design team still working on Kubuntu logo, expect gear-ification soon
[01:43] <kubotu> status updated
[01:44] <nixternal> hrmm, interesting that was announced already...thought it was going to be later on this week
[01:45] <Riddell> was ment to be last week
[01:46] <maco2> Riddell: silly lad, should've !Kubuntu'd it so itd go to the gorup
[01:46] <maco2> *group
[01:49] <Riddell> ~identica dent New logo announced for Ubuntu.  Design team still working on Kubuntu logo, expect gear-ification soon !kubuntu
[01:49] <kubotu> status updated
[01:50] <Riddell> this microblogging thing is so confusing
[01:52] <maco2> hahaha
[01:52] <ejat> :)
[01:52] <persia> Adding the '!' when using "Kubuntu" in other contexts is probably easier than adding tags at the end (and more human-readable)
[01:53] <maco2> thats what i expected him to do
[01:53] <Riddell> I never find microblogs at all readable
[01:53] <maco2> maybe youre Doin It Wrong
[01:53] <persia> They are nearly as reliable as udp.
[01:59] <nixternal> hrmm, some seem to like to the new change for ubuntu and a lot are really dissing it so far...personally, it finally doesn't feel cartoonish to me...
[02:00] <nixternal> keeping my mouth shut now for about 2 weeks about the logo wasn't easy, but at the same time it was easy, as I totally forgot about it until it was accidentally leaked last week
[02:10] <Trouble> One of the things that first attracted to me to KDE was the fact it wasn't brown :-p
[02:11] <maco2> oh i liked the brown
[02:11] <maco2> gutsy had a lovely wallpaper
[02:45] <persia> Hey tuxdavis.  Thanks for offering to help out with the kdebindings FTBFS on armel.
[02:46] <tuxdavis> np
[03:13] <shtylman> I still don't understand why the new ubuntu theme window buttons are the way they are...
[03:13] <shtylman> sigh... maybe I never will
[03:51] <ScottK> Riddell: I've filed Bug #531697 on the qt4-x11 FTBFS on IA64.  Since it's an ICE, we're pretty dead on  that arch unless someone like doko jumps in an fixes it.  I think it's worth bring up at the release team meeting on Friday.
[04:05]  * shtylman finished rsyncing the kde svn repo
[04:05] <shtylman> all 60GB of it
[04:05] <shtylman> to help with the git migration efforts
[04:05] <shtylman> thats alot of code
[07:23] <zegenie> is kubuntu gonna change the window buttons layout order as well ?
[07:23] <zegenie> in the default settings I mean
[08:30] <Mamarok> I have a serious problem: since my upgrade to SC 4.4.1, I don't see the KNotes anymore in the SystemTray. When starting the application and setting it to show in the SystemTray, it never shows up
[08:30] <Mamarok> all my memos and notes for work are in there...
[08:31] <Mamarok> and accessing it throug Kontact is a pain, since you don't even see the whole title there, and I have like 50 of those
[08:34] <ulysses>  /part
[09:38] <Mamarok> I have a serious problem: since my upgrade to SC 4.4.1, I don't see the KNotes anymore in the SystemTray. When starting the application and setting it to show in the SystemTray, it never shows up
[09:38] <Mamarok> all my memos and notes for work are in there...
[09:38] <Mamarok> and accessing it throug Kontact is a pain, since you don't even see the whole title there, and I have like 50 of those
[09:39] <Mamarok> which makes it a serious regression for me :(
[10:30] <Riddell> kdebindings built on ARM!
[10:30]  * Riddell does the kdebindings building on ARM dance
[10:30] <persia> Oh it did!  Cool.
[10:30] <persia> tuxdavis: Please don't worry about it anymore.
[10:41] <Riddell> well this is a workaround not a fix, would be better to have it fixed properly
[10:41] <Riddell> this is just disabling ruby and c# bindings which isn't ideal, but we can live with it
[10:43] <persia> OK.  I know tuxdavis had replicated it and was preparing some debug rebuilds before day-end.  Maybe it can be made to work later.
[10:43] <persia> But at least it's no longer a blocking bug, and maybe we can get images again in a couple days.
[10:43]  * Riddell wonders who tuxdavis is
[11:04] <Torch> hi all
[11:04] <Torch> can anyone confirm that using KFileDialog::getOpenFileName() from an application running as root does NOT work on kubuntu?
[11:04] <Torch> (e.g. run kdesu konqueror and try to file-> open file)
[11:11] <persia> Riddell: Some guy who told me he had arm hardware and wanted to help port kubuntu :)
[11:11] <Riddell> Torch: works fine here
[11:11] <persia> Riddell: He was at barcelona.  Usually does games.
[11:11] <Torch> Riddell: thx
[11:28]  * apachelogger stumbles in
[11:29] <Riddell> asac: bug 531848 MIR for the firefox kde stuff
[11:42]  * apachelogger forgot what he was working on before going to bed -.-
[11:52] <Riddell> apachelogger: clearing out my inbox?
[11:53] <Mamarok> no, mine
[11:58] <apachelogger> neither :P
[11:59]  * apachelogger was reading about the powers of 16 ^^
[12:16] <ejat> apachelogger: is there a bug file about plasmoid knetworkmanager? seem like it show "Activating .... " not connected .. i need to manually get dhcp for wired or wireless
[12:17] <Riddell> ejat: we know that plasma-widget-networkmanagement isn't working well, that's why it's not on the CD
[12:17] <Riddell> ejat: however agateau did some fixes in svn so it would be good if someone could test that
[12:20] <ScottK> Riddell: Did you see about the qt4-x11 ICE on IA64?  I pinged you about the bug last night.
[12:20] <ejat> thanks Riddell for the info ..
[12:20] <ScottK> We're pretty dead on that arch until that gets fixed.
[12:20] <ScottK> dpm: Would you please have a look at quassel templates.  We got some more that need a push.
[12:23] <Riddell> ScottK: yes thanks.  I must admit that ia64 isn't a priority for me but it would be nice to have qt4 compiling at least
[12:24] <ScottK> It'd be a shame to lose an arch for the LTS when we've been good on all archs the last couple of releases.
[12:26] <dpm> ScottK, there's https://translations.edge.launchpad.net/ubuntu/lucid/+source/quassel/+imports?field.filter_status=all&field.filter_extension=pot That one should be fine, it's been automatically approved, but not yet imported because there are quite a lot of entries (translations and templates) in the Ubuntu queue right now. In principle, there shouldn't be any more manual approving needed for any of the current templates, they're now approved automatic
[12:26] <dpm> ally, it's just that Launchpad is still processing the queue, so I expect that they should get imported in the next couple of days (a bit of a guessed estimation)
[12:27] <ScottK> dpm: I was looking at https://translations.launchpad.net/ubuntu/lucid/+source/quassel/+imports showing several as "Needs Review".
[12:56] <dpm> ScottK, ah, those, thanks. Not sure why they weren't approved, but I could think it's for the same reason (LP is still going through the queue). I've now approved them manually -> https://translations.edge.launchpad.net/ubuntu/lucid/+source/quassel/+imports?field.filter_status=NEEDS_REVIEW&field.filter_extension=all
[12:57] <ScottK> dpm: I think it's because they hadn't been uploaded before (they are the result of the first pull from LP).  Thanks.
[13:00] <dpm> ScottK, they should have been imported automatically with the template anyway. We manually approve templates once (the first time LP sees them), and once that's done translations are approved automatically along with the template. In any case, if you see this happening again, just give me a shout
[13:00] <dpm> and thanks for the heads up
[13:00] <ScottK> dpm: Will do.
[13:07] <Riddell> new kbluetooth uploaded
[14:49] <fabo> danimo: wrt to qtcreator slow boot time, have you found something ?
[14:49] <fabo> i received a bug report about it.
[14:50] <danimo> fabo: no, it disappeared after a while. I guess it's the indexing. once that's done, creator is fine
[14:50] <danimo> fabo: but it will need some more scientific research (i.e. a valgrind run if possible)
[14:51] <danimo> fabo: the problem is that if you try to observe it, you keep closing creator immediately, in which case indexing the docs never finishes
[14:54] <fabo> danimo: http://bugs.debian.org/572493
[14:57] <danimo> fabo: ok, that's weird
[15:14]  * Riddell pokes the council in the secret council channel
[15:15] <Riddell> fabo: yo
[15:15] <Riddell> fabo: any plans to rename kdebluetooth in line with upstream to kbluetooth?
[15:15] <Riddell> fabo: also upstream may be releasing a new version with our kubuntu patch and an autostart file added
[15:44] <t3rm1n4l> hi
[15:44] <t3rm1n4l> is there kdm greeter plugin support in kde4 ?
[15:45] <Riddell> it has themes
[15:45] <t3rm1n4l> not themes
[15:45] <t3rm1n4l> i need to show a dialog at kdm
[15:46] <Riddell> I don't think there's any plugin support for features, you'd need to edit the code
[15:47] <t3rm1n4l> but when i wrote a dialog, it is not getting focus
[15:47] <t3rm1n4l> i mean cursor stays in usr/pass lineedits
[15:48] <t3rm1n4l> but cursor doesnt come to my dialog
[15:48] <Riddell> there's no window manager at KDM stage so focus won't do what you expect
[15:49] <Riddell> you may want to try talking to the maintainer, ossi, who is in #kde-devel
[15:49] <Riddell> he's not always the most patient of chaps however
[15:50] <fabo> Riddell: ok, i rename kdebluetooth -> kbluetooth
[15:50] <fabo> Riddell: new version = 0.4.2 or something else ?
[15:51] <fabo> apachelogger: what about depends on bluez and recommends bluez-alsa, bluez-cups ?
[15:52] <fabo> this way, drop only bluez-gstreamer and keep same behavior
[15:52] <apachelogger> huh?
[15:52]  * apachelogger doesnt quite follow
[15:53] <fabo> you replace bluetooth dependency by bluez-alsa, bluez-cups.
[15:53] <fabo> but bluez-alsa, bluez-cups are a recommends of bluetooth.
[15:54] <fabo> it means we can't install kbluetooth without them anymore
[15:54] <fabo> => what about depends on bluez and recommends bluez-alsa, bluez-cups ?
[15:55] <fabo> it allows to install kbluetooth with bluez only (--no-install-recommends)
[15:56] <Riddell> Depends: ${shlibs:Depends}, ${misc:Depends}, bluez-alsa, bluez-cups, obex-data-server, python-qt4-dbus, python-qt4
[15:56] <Riddell> is what we have
[15:56] <Riddell> I'll drop the python bits, those aren't needed now kblueplugd can go
[15:57] <Riddell> fabo: http://people.canonical.com/~jriddell/tmp/kubuntu_01_document_path.diff http://people.canonical.com/~jriddell/tmp/kubuntu_02_autostart.diff  are the patches he'll probably include in a 0.4.3 release
[15:57] <fabo> ok
[15:58] <fabo> Riddell: + bluez, obex-data-server, python-qt4-dbus, python-qt4
[15:58] <fabo> +Recommends: bluez-alsa, bluez-cups
[15:58] <fabo> (drop the python bits - not included)
[15:59] <Riddell> can kbluetooth even pair with printers and sound devices?
[16:00] <fabo> not tested ...
[16:07] <Riddell> fabo: I'll ask upstream what the right dependencies are
[16:10] <maco2> eeeek
[16:10] <daskreech> Mouse?
[16:10] <maco2> so after installing 4.4.1 from k-b my contact list was empty
[16:11] <maco2> now the std.vcf is in the list and all the names are there... hmm ok, dunno how that came back but sure
[16:11] <maco2> except... none of the data that goes *with* the names is there
[16:12] <maco2> whew.. ok the data's still in the vcf. kaddressbook has just decided that it's invisible, thats all.
[16:22] <fabo> Riddell: current package -> http://git.debian.org/?p=pkg-kde/kde-extras/kdebluetooth4.git;a=summary
[16:23] <Riddell> fabo: you can get rid of kblueplugd and kblueplugd.desktop, the autostart file replaces that
[16:24] <fabo> Riddell: have you got a bazaar branch i could sync ?
[16:24] <Riddell> fabo: we don't currently keep it in bzr, but I could do so if that would help
[16:25] <fabo> Riddell: that could help :) easier for me to merge/sync
[16:27] <Riddell> fabo: one sec
[16:28] <fabo> np
[16:31] <Riddell> fabo: https://code.edge.launchpad.net/~kubuntu-members/kde-bluetooth/ubuntu
[16:32] <fabo> Riddell: thks
[16:35] <Riddell> gosh, two shtylman_s
[16:50] <pielud> please see https://bugs.launchpad.net/ubuntu/+bug/531844
[16:53] <Riddell> pielud: hmm interesting
[16:53] <Riddell> pielud: we don't include those files because they're only needed for building nepomuk which is part of kdebase-runtime anyway
[16:53] <Riddell> seems strange that nepomuk in playground would require nepomuk from kdebase-runtime
[16:57] <Riddell> dantti: new packagekit uploaded thanks
[16:58] <Riddell> pielud: where is nepomuk in playground?
[17:03] <Riddell> right enough no interfaces directory there http://websvn.kde.org/trunk/playground/base/nepomuk-kde/
[17:20] <pielud> Riddell - Nepomuk playground is not part of the base. Remeber "Nepomuk playground" is not part of Nepomuk
[17:20] <Riddell> pielud: are you on lucid or karmic?
[17:20] <pielud> lucid - 10.4
[17:20] <pielud> kde 4.4.1
[17:21] <Riddell> hmm, no kdebase-runtime-dev to add the files to
[17:21] <pielud> I know
[17:21] <Riddell> guess I can just add them to kdebase-runtime-data
[17:22] <pielud> my openSUSE has it in kdebase-runtime
[17:22] <pielud> will quickly check Madriva too
[17:23] <pielud> Mandriva
[17:24] <daskreech> Riddell: There is a unified Canonical push for the themeing ?
[17:29] <Riddell> daskreech: Canonical's designers are working on ideas for the kubuntu logo
[17:30] <daskreech> Ok
[17:31] <daskreech> Good :)
[17:32] <dantti> Riddell: yw
[17:52] <pielud> Yes Riddell. Mandriva has a kdebase4-runtime-devel   http://fr2.rpmfind.net//linux/RPM/mandriva/devel/cooker/i586/media/main/release/kdebase4-runtime-devel-4.4.0-8mdv2010.1.i586.html
[17:54] <pielud> or see http://doc4.mandriva.org/bin/view/d4/package/bfb4f17219bf555a389df35ee410bbad5f7f3af1?d=#files
[17:55] <daskreech> Hi rickspencer3
[17:55] <rickspencer3> hi daskreech
[17:55]  * daskreech hugs pielud. Thanks. You are cool :)
[17:55] <rickspencer3> 'sup?
[17:56] <pielud> huh?
[17:56] <ScottK> persia: Which lib was the one that was at issue when you were trying to build plasma-mobile?
[17:57] <daskreech> pielud: Caring enough to find out what's wrong instead of just saying it's broken! Fix it and going off
[17:57] <daskreech> rickspencer3: nothing much. How's the day?
[17:58] <rickspencer3> daskreech, hectic week for me
[17:58] <pielud> I need it Roger, to lazy to compile KDE today :-)
[17:58] <persia> ScottK: I don't remember offhand.  I think the conclusion rbelem and I had was that we'd like to see kdebase-workspace broken into lots of constituent source packages.
[17:58] <rickspencer3> but fun
[17:59] <persia> ScottK: Do you need me to check my logs and get a specific reference?
[17:59] <ScottK> persia: I do.  I'm discussing additional splits with Debian right now.
[17:59] <Riddell> daskreech: we know what's wrong, I'll fix it shortly
[17:59] <ScottK> I'll look in mine too.
[17:59]  * persia checks logs
[17:59] <Riddell> pielud can also just copy the files out of the sources, they don't get modified
[18:00] <daskreech> Riddell: I know but pielud following up is still cool :)
[18:01] <persia> ScottK: kdm, kwin, kcontrol
[18:02] <pielud> Riddell, I'll have a look if that work-around compiles for now , thanx
[18:03] <pielud> Not yet sure what else is missing :(
[18:09] <ScottK> persia: Found it.  libplasmagenericshell
[18:10] <persia> ScottK: That wasn't even in my logs.  Good find.
[18:11] <ScottK> persia: Thanks to Quassel's infinite backscroll.
[18:11] <ScottK> Gotta run.  Sick kid to pick up from school.
[18:13] <persia> Ah, found it now.  That was the one I where I wanted to have kdebase-workspace-dev depend on kdebase-workspace-bin .  libkcontrol was so that rbelem could build kwin and kdm outside of kdebase.
[18:32] <apachelogger> fabo, Riddell: bluez-utils/bluetooth recommends all bluez- packages, including bluez-gstreamer, thus we cannot use the metapackage as it would drag gstreamer onto the kubuntu CD
[18:37] <Riddell> apachelogger: we know, the question is if bluez-alsa, bluez-cups or bluez do any good for kbluetooth
[18:37] <apachelogger> yeah, that I wondered too when I saw it ^^
[18:38] <Riddell> e-mailed upstream anyway
[18:45] <shtylman_> Riddell: where are we on artwork? anything needing doing or sharing with upstream?
[18:48] <Riddell> shtylman_: see other channel
[20:04] <apachelogger> Riddell: for the debug symbol installer should the user be asked if he wants to continue looking for dbg packages even if ia dbg package for a file could not be found?
[20:05]  * apachelogger suppose that it might be useful in some corner cases, but also notes that he does not know how to best implement this n non-blocking manner
[20:05] <ScottK> apachelogger: Apparently stacks of notifications is the KDE 4.4 way for stuff.
[20:05] <apachelogger> lol
[20:05] <ScottK> I now get three whenever I upload my laptop.
[20:05] <Quintasan> oh yeah
[20:06] <apachelogger> ScottK: the current code design is so crappy I couldnt even implement this in a painless way :P
[20:06] <apachelogger> it is like a shell script written in cpp ^^
[20:06] <ScottK> Nice.
[20:07] <apachelogger> oh actually it is like a shell script written in cpp, depending on KDE and with useful functions
[20:07] <apachelogger> making useful functions in say bash is close to impossible
[20:07] <ScottK> Sounds like a perfect candidate for pythonification.
[20:08] <Quintasan> apachelogger: really, how do you manage to create such code?
[20:08] <apachelogger> ScottK: how so?
[20:09] <ScottK> apachelogger: My normal workflow is to do really simple stuff in shell and as soon as I scratch my head, I reimplement in Python because it's much easier for anythin non-trivial.
[20:09] <apachelogger> Quintasan: write a shell script, then get a template kde cpp code and stuff everything you had in shell into main
[20:09]  * Quintasan notes even his utterly useless Kalculator is coded nicely :P
[20:09] <apachelogger> Quintasan: stack a UI on top of that and you are all good :D
[20:10] <apachelogger> ScottK: well, I cppified it, so I do not have to worry about runtime issues ^^
[20:10] <Quintasan> apachelogger: result of my boredom at chemistry -> http://wklej.org/id/290358/
[20:10] <apachelogger> unless I ran into some pointer crazyness, which never ever happenes because I got pointers all figured out
[20:11]  * apachelogger would like to have a pointer as bf :P
[20:11] <apachelogger> Quintasan: shouldnt you like listen? :P
[20:12] <Quintasan> listen to what? your rants about PyFail?
[20:12] <apachelogger> for example
[20:12] <apachelogger> Quintasan: I could also rant about people who write non-english words in their code :P
[20:13] <Quintasan> apachelogger: well it's not like you can't understand what it does from the code, isn't it?
[20:13] <Quintasan> should be " is it?"
[20:14] <apachelogger> Quintasan: that is not the point
[20:14] <apachelogger> you need to know without looking at the code
[20:14] <apachelogger> in a best case scenario a function name is descriptive enough that I know exactly what the function does
[20:15] <apachelogger> as usual my famous IBM aix C best practice document comes in handy here ;)
[20:15] <apachelogger> http://www.ibm.com/developerworks/aix/library/au-hook_duttaC.html
[20:16] <apachelogger> Quintasan: see section funciton names
[20:16] <Quintasan> I see what they did there
[20:17]  * Quintasan goes back to git and cpp awesomeness
[20:18] <apachelogger> ScottK: what is your opinion on the "let user decide whether to continue"?
[20:18] <ScottK> I think I don't understand it enough to have one.
[20:19] <apachelogger> oh my
[20:20] <ScottK> Some of http://www.python.org/dev/peps/pep-0008/ is Python specific, but it also has some good general rules on coding conventions.
[20:20] <shtylman_> from now one.. I will always comment my "add one to i"
[20:20] <ScottK> No, "Add one to i."
[20:20] <ScottK> Grammar counts.
[20:21] <shtylman_> hahaha
[20:21] <ScottK> That's actually a pep-8 rule: Use full sentences in comments.
[20:21] <ScottK> It helps readability.
[20:22] <apachelogger> ScottK: drkonqi allows the user to install missing dbg packages, for that it starts a distro provided app/script and passes it a list of all files for which no debug symbols could be found, the app/script does then check for the packages that contain the debug symbols for those files... now if it cant find it for one, should it ask the user "oh my, couldnt find dbg package, do you want to continue anyway?"  or just tell them that the
[20:22] <apachelogger>  package could not be found and that they shall go sob in a corner
[20:22] <Quintasan> apachelogger: the second one is better
[20:23] <ScottK> At that point it might be useful to see if the -dbgsym repo is enabled and if not recommend it.
[20:23] <ScottK> Then try again.
[20:23] <Quintasan> add a pop-up window saying - "Now you can go to nearest corner and sob"
[20:23] <apachelogger> ScottK: I want to automize that part
[20:23] <ScottK> OK.
[20:23] <apachelogger> so the assumption is that the dbg package could not be found because it either does not exist or because it does not match the search patterns
[20:24] <apachelogger> (e.g. is not called binpkg-dbg or srcpkg-dbg or each with -dbgsym)
[20:24] <ScottK> So you're automatically adding a new repo and running apt-get update?
[20:24] <ScottK> How's that working?
[20:25] <apachelogger> ScottK: software-properties for sources.list manipulation, and packagekit for update, I am hoping
[20:25] <apachelogger> of course with user feedback, so first thing the app does is tell the user that some debug symbols might not be findable without the ddebs repo and if they want to add that repo
[20:26] <apachelogger> something like that at least
[20:26] <ScottK> OK
[20:26] <apachelogger> Quintasan: http://paste.ubuntu.com/388507/
[20:26] <apachelogger> Quintasan: that is the current message actually ;)
[20:27] <apachelogger> but again, the design is not dynamic enough to annoy us with notifications ;)
[20:27] <apachelogger> ScottK: so what do you think? tell the user or just abort?
[20:27] <ScottK> If there's a useful chance of continuing, I'd tell the user.
[20:29]  * apachelogger starts wondering on how to implement that in non-blocking manner :S
[20:31] <Quintasan> apachelogger: http://wklej.org/id/290377/
[20:31] <Quintasan> change it to this
[20:31] <Quintasan> :P
[20:32] <apachelogger> <3
[20:32]  * apachelogger notes that a newline is missing there though :P
[20:32] <Quintasan> apachelogger: http://wklej.org/id/290379/
[20:32] <Quintasan> fix'd
[20:32] <Quintasan> :P
[20:33] <apachelogger> in that case a whitespace is missing, and you are exceeding 80chars/line :P
[20:34] <Quintasan> oh man
[20:34]  * Quintasan gives up
[20:34] <Quintasan> Change it to -> "No dgb for u, go to your corner and sob"
[20:34] <Quintasan> :P
[20:34] <Quintasan> or "wallow in despair"
[20:34] <Quintasan> Sounds better IMO
[20:35] <Quintasan> I'm going to bed, finally friday tomorrow
[20:35] <apachelogger> or who markey would put it: "puny user, cant even install dbg packages yourself! well, I cant either! we are boned!"
[20:36] <apachelogger> Quintasan: nini
[20:36] <ScottK> ... abandon all hope, go to your corner and wail with despair.
[20:36] <apachelogger> ah!!!!!!!!!!!!!!!!!!
[20:37] <apachelogger> ...idea...
[20:37] <apachelogger> how about presenting that dialog only once, at the very end, before asking the user whether to install the found crap?
[20:37] <apachelogger> instead of for each package without dbg package
[20:38] <apachelogger> that way it also does not conflict with the blockingness necessary for a loop
[20:38] <ScottK> Sounds reasonable.
[20:38] <ScottK> Even smart.
[20:39] <apachelogger> yay, I am smart \o/
[20:44] <apachelogger> http://imagebin.ca/view/KCUk9O.html
[21:09] <kwwii> hi Riddell
[21:18] <Riddell> hi kwwii
[21:28] <Trouble> Hi kwwii
[21:29] <apachelogger> http://people.ubuntu.com/~apachelogger/screencasts/drkonqi-installdbgsymbols-2.ogv
[21:40] <apachelogger> oh my
[21:40] <apachelogger> one cant start kpk with nofork
[21:40] <apachelogger> dantti: ^
[21:41] <apachelogger> dantti: I suppose it would also not exit non-0 if a user says no to installing a package by name?
[21:41] <dantti> apachelogger: hmm can you poke me tomorow? I'm going home now, and really don't know what the answeard is :P
[21:42] <apachelogger> oki ^^
[21:42] <dantti> thanks, bye
[21:45] <peterson> hello, everyone! I was wondering if anyone knows what is going to happen to kubuntu after this whole ubuntu re-branding thing. Is kubuntu going to get a new (own) theme? Colours?
[21:46] <apachelogger> kubuntu does have it's own theme?
[21:48] <ScottK> peterson: Kubuntu will get some new stuff.  Exactly what is still being worked on.
[21:48] <peterson> I don't think so, apachelogger
[21:48] <ScottK> In general we don't deviate much from upstream KDE.  I don't expect that to change significantly.
[21:48] <peterson> I think it is KDE default, innit?
[21:48] <ScottK> Mostly.
[21:48] <Riddell> peterson: the new logo is still being worked on
[21:48] <apachelogger> so what is so bad about KDE's default?
[21:49] <peterson> It's not bad, it's just not.. personalized.
[21:49] <peterson> thanks ScottK =)
[21:49] <apachelogger> peterson: no?
[21:49] <peterson> and Riddell
[21:49] <apachelogger> it uses Kubuntu colors all over the palce, doesnt it? :P
[21:49] <apachelogger> all blue here :P
[21:49] <peterson> apachelogger AEhaeH or could we say kubuntu uses kde colours? =P
[21:50] <apachelogger> traditionally our color palette was blue, extactly because we are a kde distribution and thus want to share a similar identity
[21:50] <peterson> hmmmm
[21:50] <peterson> but what did you think of the purple and orange thing? Did you (personally) like it? Is there any chance of a significant change in that direction?
[21:51] <apachelogger> we hadone purple release :P
[21:52] <peterson> haEhaEhAE really? What do you mean? Sorry if that was irony, I'm not native speaker, so I might not get it =P
[21:52] <apachelogger> peterson: edgy eft had a purple theming
[21:53] <peterson> hummm I didn't know that.
[21:53] <apachelogger> other than that we stuck with blue IIRC
[21:53] <apachelogger> and blue did proof itself, so I do not see why would want to change that either
[21:53] <apachelogger> just because ubuntu's color palette sucked doesnt mean that ours did ;)
[21:53] <peterson> It makes sense =) eaheaheahea
[21:53] <peterson> I'm going to look for a screenshot, I'm curious...
[21:54] <peterson> Although at that time it was kde 3, right?
[21:54] <apachelogger> yep
[21:56] <peterson> haehhae funny..
[21:57] <peterson> by the way, is there any way I can change the colours of kde apps in gnome (since I don't have the KDE system centre)?
[22:01] <peterson> anyone..? =P
[22:01]  * Trouble thinks Kubuntu should go brown for 10.4 to catch and convert all the Ubuntu users who don't like the new default theme :-p
[22:01] <Riddell> peterson: you'd need to install system-settings
[22:02] <peterson> thanks Riddell =)
[22:05] <peterson> well, thanks for the enlightenment (even though we're talking about KDE... horrible joke) and.. good bye! keep on rocking, you do an awesome desktop system ^^
[23:22]  * maco2 liked the brown
[23:26]  * ryanakca liked Edgy's purple
[23:30] <maco2> i liked edgy cuz it had aiglx in its xorg thus letting intel users like me have beryl
[23:31]  * ryanakca had forgotten about beryl and compiz and co.
[23:31] <ryanakca> Cool to look at, but not really that useful once the novelty fades.
[23:32] <Trouble> I really like the new Ubuntu palette <3
[23:32] <maco2> ryanakca: i found it much more useful than metacity
[23:33] <ryanakca> Ah