[10:24] <Riddell> dpm: query from KDE upstream http://paste.ubuntu.com/247033/
[10:24] <Riddell> dpm: we didn't have kde-l10n-sr-latin in jaunty so there's only a few files translated and it mixes sr@latin with sr
[10:30] <dpm> Riddell: I'm talking with Chusslove on kde-i18n atm. Basically, the variant translations are included in the main language' language pack. That means, the 'sr@latin' translations are included in the 'sr' language packs. The mixup is the normal behaviour, since variants fall back to the main language when there is no translation. If that is a problem, we might be able to explicitly define another fallback language. Let me talk to ArneGoetje about this
[10:31] <Riddell> dpm: yeah, it seems like a bug in the fallback to me
[10:40] <ghostcube> hi peoples
[10:40] <ghostcube> :)
[10:45]  * Riddell cranks the handle on home internet connection to make it upload faster
[10:46] <Riddell> dpm: I got an e-mail saying "I would like to be of help. I would like to help translating." where do I point them?
[10:53] <dpm> Riddell: if he/she said in which language he'd like to contribute to, the best thing is to point him/her to the list of translation groups -> https://translations.launchpad.net/+groups/ubuntu-translators, where then he/she can contact the translation team directly in his/her language. Otherwise, you can point them to the ubuntu-translators mailing list -> https://wiki.ubuntu.com/Translations/Contact. There someone will help them contacting the right t
[10:53] <dpm> eam. Or you can also forward the e-mail to me.
[11:34]  * davmor2 pokes Riddell livefs manifest still says 22nd dude
[11:35] <Riddell> davmor2: mm, KDE 4.3 failed to upload due to home internet breakage, it's uploading now
[11:36] <davmor2> Riddell: will there be a rebuild so I can test it?
[11:36] <Riddell> davmor2: I'll do one later today if it all gets built
[11:39] <davmor2> Riddell: Cool just ping me if you do I want to get some testing of the new installer in before alpha4
[14:46] <dantti> Riddell: ping
[14:48] <Guest44125> Riddell: ping, updated drupal.ryanak.ca , icons are smaller, 96px now
[14:50] <OdyX> Hi Kubuntu... Looking after gtk-qt-engine bugs in Debian, I wonder how Ubuntu handles those situations: a) launching gtk applications in KDE and b) launching gtk applications _as root_ in KDE
[14:51] <yuriy> OdyX: I think we've dumped gtk-qt-engine and set the gtk theme to QtCurve for both cases
[14:51] <OdyX> yuriy: hmm...
[14:51] <OdyX> yuriy: thanks !
[14:51] <yuriy> kept the settings module, how that works for root i don't know
[14:53] <Riddell> dantti: hi
[14:53] <dantti> Riddell: hey :D , was you that poke about printer stuff on the list?
[14:54] <Riddell> OdyX, yuriy: it doesn't, root GTK apps use the nasty built in theme
[14:54] <Riddell> dantti: that would be me
[14:54] <Riddell> shtylman too
[14:54] <Riddell> dantti: what are you planning?
[14:54] <OdyX> Riddell: okay... it's not so trivial to do right...
[14:55] <dantti> Riddell: well I starting some sort of book, and I'm teaching some friends, c++/qt/kdelibs with it, and one of the tasks i'm willing to help them do is the printer module..
[14:56] <Riddell> dantti: system-config-printer-kde is written in Python
[14:56] <dantti> Riddell: today it segfaults here, and it's made on python..
[14:56] <dantti> yep :P
[14:56] <dantti> so my idea was to rewrite it on c++
[14:56] <yuriy> OdyX: bug 205201
[14:56] <dantti> Riddell: basically cause it would have much mode kde devs to help later
[14:57] <dantti> Riddell: and that I also have more experience with kde modules in c++
[14:57] <Riddell> dantti: that seems like a lot of work to fix one bug, it would also lose Python developers like me and it would mean it couldn't be in sync with gnome's system-config-printer
[14:57] <OdyX> yuriy: thanks, but I have enough of these in Debian bts :->
[14:57] <dantti> Riddell: hmm why sync?
[15:00] <Riddell> dantti: well it's a fork of gnome's system-config-printer and it's kept in sync with it to remain current with CUPS and new features
[15:03] <dantti> Riddell: I see... well I'd need to look at both app to try to understand the basics, but if the code is going to be in python then i can't help, also if there were many benefits in using python i think it would be working by now.. (i'm not against python i just think c++ could benefit of most kde devs)
[15:04] <dantti> Riddell: if you think there is just little things to do to make it work, then i'll move to other stuff, otherwise we can start on c++...
[15:05] <Riddell> dantti: I'd be against starting a c++ version, it would be more work to do and maintain, I think the lack of interest is nothing new in printing (nobody cared for printing in KDE 3 either)
[15:08] <ghostcube> c++ is faster then python ever will be
[15:08] <ghostcube> a
[15:08] <dantti> ghostcube: well that's not the problem :P
[15:08] <ghostcube> but an fact pro
[15:08] <ghostcube> :D
[15:09] <OdyX> ghostcube: why caring about speed when you have an inkjet printer that lasts 40 seconds to print one page.
[15:09] <ghostcube> i have an laserjet oO
[15:09] <ghostcube> 2 secs
[15:09] <ghostcube> :D
[15:09] <dantti> ghostcube: it's just configure, we are not printing :P
[15:09] <ghostcube> i know i only was joking :P
[15:09] <ghostcube> btw didnt even python cancel python progz and reverted to an c++ pendant
[15:10] <dantti> Riddell: well, i now these things don't have much love, but more work to do and maintaing i guess depends on what do you know..
[15:10] <ghostcube> 3.0 to 3.1 afaik
[15:10] <ghostcube> guys even compiz gets c++ now so ...
[15:10] <ghostcube> lol
[15:12] <ghostcube> wouldnt the cups printer webpage all someone need for an printer setup ?
[15:12] <ghostcube> *be
[15:13] <ghostcube> i always manage mny printers by this
[15:13] <dantti> ghostcube: yep, but that's ugly, is much coller to have that manages by native kde look'n'fell
[15:13] <ghostcube> hmm isnt macos already build oO
[15:14]  * ghostcube ides and runs
[15:14] <dantti> Riddell: well last question: does that module get's in system settings? and automattically detects thje printer?
[15:14] <dantti> Riddell: cause if not i would like to make a kded module to detect the printer, show a popup, and call the printer manager..
[15:14] <Riddell> dantti: system-config-printer-kde is in system settings.  printer-applet from kdeutils is the bit that pops up when a new printer is detected
[15:15] <Riddell> hal-cups-utils (now system-config-printer-udev) is what does the actual printer detection
[15:15] <Riddell> your distro may vary
[15:15] <dantti> i see.. so that should be there, if it's not it's because it's not working right?
[15:16] <Riddell> yes it means something is missing or not working
[15:25] <mgraesslin> why are you still using patch kubuntu_10_turn_on_kwin_compositing.diff?
[15:26] <Riddell> mgraesslin: is there a reason we shouldn't?
[15:26] <mgraesslin> well KWin is able to detect if compositing is supported or not
[15:27] <mgraesslin> and that KWin requires Compiz looks strange :-P
[15:28] <ghostcube> compiz now has a workarround for the not syncing window refreshment
[15:28] <ghostcube> :)
[15:30] <Riddell> mgraesslin: kwin uses some information based on the kwin maintainers experience, the compiz blacklist uses information based on the actualy drivers in ubuntu which is far more reliable for us
[15:31] <mgraesslin> but that list is only used, if it is not intel, nvidia, radeon or fglrx
[15:32] <mgraesslin> and if the Ubuntu blacklist is better, it would probably be better to use the information directly in kwin
[15:37] <Riddell> yeah, so currently it trusts KDE for the main cards then trusts Ubuntu for the obscure ones
[15:38] <Riddell> we should probably ask for feedback from people to see if it works
[15:40] <mgraesslin> in case of the obscure cards I'd prefer keeping compositing turned off - those cards are mostly old and probably not powerfull enough to run a composited workspace
[15:51] <ghostcube> nope
[15:52] <ghostcube> on some of them the whitelisting works fine for compositing
[15:52] <ghostcube> so its at own risk if you want to bring compiz on
[15:52] <ghostcube> so it should be in kde too
[17:59] <Nightrose> people in identica and twitter are asking when kubuntu packages for 4.3 will be availible - what to tell them?
[18:04] <a|wen> Nightrose: last i've heard packages was still building on karmic ... hopefully finishing soon
[18:04] <Nightrose> ok
[18:06]  * a|wen so much needs a kde overview of versions + build status
[18:11] <a|wen> Nightrose: kdepim and kdeplasma-addons is still in depwait so we're not there yet
[18:12] <Nightrose> k thx
[18:12] <Nightrose> jaunty still has to wait as well i guess?
[18:14] <a|wen> nah, consider releasing it soon ... but wanted an extra ninja to agree
[18:15] <a|wen> considers*
[18:17] <Nightrose> ok let me know when packages are up so I can dent and tweet it
[18:17] <Nightrose> people are impatient already ;-)
[18:23] <ghostcube> will the main release be in backports ? or in the rc3 repo ?
[18:24] <a|wen> backports-ppa i'm quite sure
[18:24] <ghostcube> thx
[18:30]  * Trouble is poised for KDE 4.3 for Jaunty
[18:31] <a|wen> ghostcube: you on jaunty?
[18:31] <ghostcube> yes
[18:33] <a|wen> ghostcube: PM
[18:34] <Quintasan> bug #408962
[18:34] <Quintasan> I hope I done it right
[18:35] <Quintasan> JontheEchidna: ^
[18:41] <a|wen> ryanakca: ping
[18:49] <seele> Riddell: how can we get some of the papercuts assigned to a milestone? maco didn't get props on djsiegel's latest papercut entry
[18:50] <ScottK> seele: I think you ought to get djsiegel to add you to the papercuts project so you can just set it yourself.
[18:52] <ryanakca> a|wen: pong
[18:52] <jjesse> if you are a member of ubuntu-bugs you should be able to set milestones as well correct?
[18:53] <maco> jjesse: papercut milestones
[18:53] <a|wen> ryanakca: do we have a kde 4.3.0 news-item ready?
[18:53] <ScottK> jjesse: It's a separate LP project.
[18:53] <jjesse> ah sorry mis understood
[18:53] <ryanakca> a|wen: I don't know, not to my knowledge
[18:53] <maco> im confused about why fixed papercuts arent listed but im assuming its because only ones that are attached to a milestone are
[18:54] <a|wen> ryanakca: maybe time to produce one ... don't know who usually does that
[18:55] <ryanakca> a|wen: what PPA is it in?
[18:55] <seele> ScottK: i'm not allowed to be part of the project
[18:55] <a|wen> ryanakca: it will be in https://launchpad.net/~kubuntu-ppa/+archive/backports/ when we release it
[18:55] <ryanakca> a|wen: thanks
[18:56] <maco> seele: canonical only?
[18:56] <a|wen> ryanakca: packages for karmic are still building ... most of the core-packages looks done though
[18:56] <jjesse> that would suck if it was canonical only
[18:57] <seele> maco: yes
[18:57] <ScottK> seele: Oh.  That's an interesting demonstration of desire for community involvement.
[18:57] <Mamarok> a|wen: 4.3 on Jaunty installs fine, no problems here
[18:57] <jjesse> agreed
[18:57] <maco> jjesse: its owned by the ayatana team, i believe
[18:57] <a|wen> Mamarok: cool ... can you remember what you upgraded from?
[18:58] <Mamarok> from 4.2.98
[18:58] <Mamarok> a|wen: the only thing held back is kdepim-dev, but that's so since beta2
[18:59] <a|wen> Mamarok: okay ... that is no problem when upgrading from 4.2.x at least
[18:59] <Mamarok> as I have both the jaunty-backports and the backports PPA active, where does 4.3 come from?
[18:59] <Mamarok> PPA?
[18:59] <maco> seele jjesse ScottK:  Maintainer: Canonical User Experience and Design team
[19:00] <a|wen> Mamarok: from the backports-ppa when we choose to release it
[19:00] <a|wen> ryanakca: you started on a news-item? .. if so, ping if you need some proof-reading or when you have it ready
[19:01] <Mamarok> ok, is it supposed to end up in the jaunty-backports soon?
[19:02] <a|wen> Mamarok: that was the idea ... but depends on any larger issues coming up and more
[19:02] <Mamarok> ok
[19:03] <Mamarok> somebody mentionned a new patched tarball from upstream earlier, is this in already?
[19:03] <Mamarok> patche like yesterday or so
[19:04] <a|wen> new tarballs was synced less than 24 hours ago according to my backlog
[19:06] <ryanakca> a|wen: http://paste.ubuntu.com/247379
[19:07] <Mamarok> great :)
[19:11]  * ghostcube waits for launch
[19:11] <ghostcube> :D
[19:13] <a|wen> ryanakca: looks good ... http://paste.ubuntu.com/247384/ ?
[19:14] <a|wen> ryanakca: uh, and we probably want to link to http://kde.org/announcements/4.3/
[19:22] <ryanakca> a|wen: done, tell me (or someone else with access) when you're ready to have it published, the draft is on the website.
[19:23] <a|wen> ryanakca: cool, thanks ... just trying to get an overview over the status in karmic
[19:23] <ryanakca> a|wen: OK. If you prod someone else, the link to the draft is https://www-admin.kubuntu.org/news/kde-4.3
[19:24] <a|wen> ryanakca: perfect... thanks again
[20:42] <mgraesslin> I can't see any i18n packages being built in the staging repository. Will there be any?
[20:43]  * mgraesslin notes that golem.de has a screencast based on Kubuntu's 4.3 RC2 packages and in the comment section people are complaining about the bad i18n state
[20:44]  * ghostcube notes that germans should be able to read some english words :P
[20:45] <ghostcube> oda ?
[20:45] <ghostcube> hehe
[20:45] <mgraesslin> ghostcube: are you running KDE 4.3 in Kubuntu with a non english locale?
[20:45] <mgraesslin> if not, give it a try - it's terrible
[20:46] <mgraesslin> I don't mind English, but having the mixture is terrible
[20:46] <jjesse> i know they have done some work recently on translations
[20:46] <ghostcube> ich weiss ich hab die rc3 am laufen gehabt oO
[20:46] <a|wen> mgraesslin: in jaunty or karmic?
[20:46] <mgraesslin> jaunty
[20:46] <a|wen> mgraesslin: then that is why ... no translations to the ppa-packages
[20:46] <apachelogger> a|wen: I think batl10n* can be used for publishing kde-l10n to ppa
[20:47] <apachelogger> at least I seem to remember that I implemented that for the hardy backports
[20:47] <mgraesslin> I know that are mostly troll posts, but http://forum.golem.de/read.php?34174,1874427,1874455#msg-1874455
[20:49] <apachelogger> a|wen: there is still some hardcoded stuff, but technically you just need to ensure .batrc got BD set to jaunty and run batl10n jaunty
[20:50] <apachelogger> a|wen: then set ARCHIVE to whatever the ppa is named in the dput cf and batl10n-upload should be good to go as well
[20:50] <a|wen> apachelogger: cool ... so it does work with kde4
[20:51] <apachelogger> anyway
[20:51] <apachelogger> =>        bed
[20:51] <ghostcube> oo
[20:51] <ghostcube> alter man
[21:10] <rgreening> shtylman: Is the ubiquity stuff uploaded yet for the installer?
[21:10] <rgreening> Just trying the Kubuntu netbook and not seeing all your fancy work yet :(
[21:12]  * a|wen seriously misses a core-dev now
[21:55] <Riddell> 4.3 is in kubuntu backports!
[21:55] <Riddell> ryanakca: I believe you have a news story waiting?
[21:57] <Riddell> a|wen: or you have a news item?
[21:58] <a|wen> Riddell: https://www-admin.kubuntu.org/news/kde-4.3
[21:59] <Riddell> time to fire up konqueror
[21:59] <Riddell> groovy
[21:59] <Riddell> has the status bar disappeared from konqueror for anyone else?
[22:00] <Nightrose> Riddell: let me know when packages for jaunty are live and kubuntu.org has an announcement so i can dent it
[22:00] <Nightrose> people are waiting impatiently ;-)
[22:00] <maco> mine's still there
[22:00] <Riddell> Nightrose: go go! http://www.kubuntu.org/news/kde-4.3
[22:00] <Riddell> ~twitter update Kubuntu packages for 4.3 are up!  http://www.kubuntu.org/news/kde-4.3
[22:00] <kubotu> status updated
[22:00] <Nightrose> Riddell: thanks :)
[22:01] <maco> hmm kopete probably shouldnt hide in the tray instead of closing when...well...when plasma-desktop isnt running and thus there is no tray
[22:01] <dtchen> what are the plans for plasma-widget-networkmanagement for karmic wth respect to wep and wpa support?
[22:02] <Nightrose> Riddell: pushed
[22:02] <maco> dtchen: "cross your fingers"?
[22:02] <Riddell> dtchen: I hope to test that tomorrow, although it doesn't mean I can do much if it doesn't work
[22:02] <a|wen> yay!
[22:03] <Riddell> dtchen: wstephenson asked for some help with a UI issue earlier, maybe if we find someone to fix it he'll get it talking to networks in return
[22:03] <dtchen> the current snapshot in karmic still fails wep and wpa on ar9170 (running both karmic's kernel and compat-wireless-2009-08-04; network-manager-gnome works fine)
[22:04] <dtchen> with plasma-widget-networkmanagement, it seems to be looping once associated and immediately disassociating
[22:06] <Riddell> dtchen: wep works for me so it could be something driver specific
[22:06] <dtchen> Riddell: true, but that's rather unlikely given both wireless-tools and n-m-gnome work fine
[22:07] <dtchen> anyhow, if it's seriously annoying in the next two hours, i've grabbed the sources
[22:07] <dtchen> back to alsa bugs
[22:11] <maco> haha
[22:18] <nielsslot> is the X crashing bug still present when upgrading to KDE 4.3 in jaunty?
[22:19] <bdgraue> /var/cache/apt/archives/kde-icons-oxygen_4%3a4.3.0-0ubuntu1~jaunty1~ppa1_all.deb
[22:19] <bdgraue> E: Sub-process /usr/bin/dpkg returned an error code (1)
[22:19] <bdgraue> /var/cache/apt/archives/kde-icons-oxygen_4%3a4.3.0-0ubuntu1~jaunty1~ppa1_all.deb
[22:19] <bdgraue> E: Sub-process /usr/bin/dpkg returned an error code (1)
[22:19] <bdgraue> /var/cache/apt/archives/kde-icons-oxygen_4%3a4.3.0-0ubuntu1~jaunty1~ppa1_all.deb
[22:19] <bdgraue> E: Sub-process /usr/bin/dpkg returned an error code (1)
[22:20] <bdgraue> sry
[22:21] <bdgraue> did not want to spam
[22:21] <bdgraue> didnt get it, that it was already in here
[22:21] <Riddell> bdgraue: pastebin the whole problem (paste.ubuntu.com
[22:21] <bdgraue> Riddell: thx, i know
[22:22] <bdgraue> its very often with kde-icons-oxygen
[22:22] <bdgraue> i have to dpkg -i --force-overwrite
[22:23] <a|wen> bdgraue: we need to fix it so you don't have to do that ... so please pastebi the errors
[22:24] <Nightrose> http://identi.ca/notice/7564103 <- Riddell
[22:24] <Nightrose> what can i answer him?
[22:26] <bdgraue> a|wen, Riddell: hope its help, its almost german http://pastebin.ubuntu.com/247506/
[22:27] <Riddell> that figures, it's an upstream bug that
[22:28] <Riddell> Nightrose: umm, dunno what's going on there
[22:29] <Nightrose> k
[22:29] <Riddell> Nightrose: I'd ask him to try   apt-get -f install and if that didn't sort it paste the output from  apt-get install kde-core  also apt-cache policy kde-core
[22:30] <Nightrose> i'll just tell him to get support on IRC
[22:30] <Riddell> Nightrose: infact I don't know where he's getting that "kde" package form
[22:30] <Riddell> from
[22:31] <Nightrose> afaik from the announcement
[22:31] <Nightrose> we'll see if he comes to #kubuntu
[22:32] <Riddell> nothing about "kde" meta package there, it's called kde-full now
[22:32] <Nightrose> ah he might be installing the wrong package then
[22:32] <Nightrose> he's on ubuntu
[22:32] <dtchen> nielsslot: more details?
[22:33] <nielsslot> dtchen: the kubuntu release notes of the first two RC's mentioned the problem.. just wondering if it was fixed
[22:43] <ghostcube> hmmm
[22:43] <ghostcube> i updated to 4.3.0 and now after login pure white screen
[22:43] <ghostcube> oO
[22:43] <ghostcube> is there anything not ready till now
[22:45] <a|wen> ghostcube: tried disabling compositing?
[22:45] <ghostcube> i autostart compiz
[22:46] <ghostcube> what config stores the setting for the default wm
[22:51] <a|wen> uh, compiz ... /me runs
[22:51] <ghostcube> it worked before so the update has done anything :)
[22:52] <a|wen> what did you upgrade from?
[22:52] <ghostcube> in what file doe the systemsetting store the settings for the default wm
[22:52] <ghostcube> 4.2.4 to 4.3.0
[22:52] <ghostcube> and i only see a white backround
[22:52] <ghostcube> i can see some plasmoids
[22:52] <Quintasan> urgh, I built plasma-runner-kopete for karmic and now I can't use it in jaunty cause of version conflicts >_<
[22:53] <a|wen> then a lot of things have changed ... i've always sticked to kwin, so dunno
[22:53] <a|wen> Quintasan: make your own backport :)
[22:53] <Quintasan> I don't want to /sob
[22:53] <Quintasan> :S
[22:53] <ghostcube> JontheEchidna: do ypu may know where systemsettings stores what WM is loaded
[22:54] <ghostcube> in which file
[22:54] <Quintasan> python plasmoids still don't work for me
[22:54] <Quintasan> oh, I have a great idea
[22:54] <Quintasan> rm -r .kde
[22:57]  * a|wen seriously needs some more diskspace
[23:04] <bdgraue> kde 4.3 runs smooth, i like it :)
[23:05] <bdgraue> well done, package guys
[23:05] <Riddell> bdgraue: can you paste the output of apt-cache policy libqt4-core  ?
[23:06] <Riddell> bdgraue: actually   apt-cache policy libqt4-network
[23:07] <bdgraue> Riddell: http://pastebin.ubuntu.com/247530/
[23:07] <Riddell> thanks
[23:08] <Quintasan> Hell, it's damn fast
[23:10] <Quintasan> GRRRR, damn that stupid python
[23:12] <Riddell> ~twitter update KDE 4.3 packages need kubuntu staging PPA for now as well as backports
[23:13] <kubotu> status updated
[23:13] <a|wen> Riddell: has any of the kde-packages been built after qt?
[23:13] <Riddell> yes, we have updates last night
[23:14] <Quintasan> Riddell, a|wen: can you try adding python plamoids?
[23:14] <Quintasan> plasmoids*
[23:15] <a|wen> Riddell: damn ... at least it is a public ppa this time around
[23:15] <bdgraue> Riddell: so i have to add deb http://ppa.launchpad.net/kubuntu-ppa/staging/ubuntu jaunty main as well?
[23:16] <Riddell> bdgraue: well you're ok you already have that Qt
[23:16] <Riddell> and it'll copmile in backports soon I hope.  stupid PPA bugs.
[23:18] <Quintasan> urgh, and how do I set different plasmoids and wallpapers per desktop?
[23:18] <bdgraue> Quintasan: zoo, out and configure plasma
[23:19] <bdgraue> s/zoo,/zoom
[23:19] <Quintasan> oh, nice
[23:19] <Quintasan> thanks
[23:20]  * Quintasan notes his graphics card sucks and zooming out takes at least 5 seconds
[23:20] <a|wen> Quintasan: is there any of the default plasmoids that are python ones?
[23:21] <Quintasan> a|wen: don't think so, try installing Plasmacon using GNHS
[23:21] <a|wen> gnhs?
[23:21] <Quintasan> get new hot stuff
[23:21] <a|wen> ahh
[23:22] <Quintasan> oh god I lol'd
[23:22] <Quintasan> very clever
[23:23] <ghostcube> hmmm ok now with staging my white screen is gone
[23:23] <ghostcube> but still i cant do anything
[23:23] <ghostcube> is there still stuff compiling
[23:23] <Quintasan> ghostcube: the ultimate solution to every KDE config problem is to remove whole .kde directory ;)
[23:24] <ghostcube> -_-
[23:24] <a|wen> Quintasan: script initialization fails ... but i'm pretty sure that kdebindings is not kde 4.3 on jaunty
[23:25] <ghostcube> i have a very clean 4.2.4 install and did update so every one doing this will need to remove .kde ? i dont think so
[23:25] <ghostcube> i cant type into run command
[23:25] <ghostcube> hmmm
[23:25] <Quintasan> ghostcube: in my case everything worked
[23:25] <Quintasan> but I use kwin
[23:25] <ghostcube> i dont get to the systemsettings to change it
[23:26] <ghostcube> :|
[23:26] <Quintasan> try alt+f2
[23:26] <ghostcube> doesnt work cant type into
[23:26] <ghostcube> but there must be a file where systemsetings stores all you put in or
[23:26] <Quintasan> .kde/share/config
[23:27] <ghostcube> -_-
[23:27] <Quintasan> check the files in that directory
[23:31] <Quintasan> anyone here using fglrx?
[23:40] <shtylman> Riddell: how do we go about getting an icon requested to be added to kde? more specifically oxygen? do I just ask pinheiro? we need an add printer icon (I don't think on exists) if we want to be able to use meaninful icons in the system printer config
[23:40] <Riddell> shtylman: you report a bug in bugs.kde.org I believe
[23:40] <shtylman> k
[23:41] <Riddell> you can also ask kwwii but he's going on holiday for the next three weeks
[23:41] <shtylman> ahh
[23:41] <shtylman> I will try the bug route...see how that goes...
[23:41] <bdgraue> Nightrose: see pein in #kubuntu isn't that the guy you mentioned?
[23:57] <ewoerner> hi
[23:58] <ewoerner> one of the marble developers just noticed that kdeedu 4.3 might need a build dependency to libgps-dev
[23:58] <ewoerner> otherwise our uber-cool gps support won't get noticed ;-)