[00:00] <high-rez> Just did an update/upgrade.  Now when I login I get "could not start ksmserver.  Check your installation"
[00:01] <neversfelde> high-rez: you should ask for support in #kubuntu
[00:02] <high-rez> neversfelde: I guess I'm trying to say that I think the latest kdelibs package is broken - not really asking for support.  Was just typing out the segfault info.  :)
[00:03] <high-rez> Not just a little broken, but kdeinit segfault broken ;)
[00:04] <neversfelde> in that case you should tell us the Kubuntu version you are using?
[00:05] <high-rez> Sorry, I'm testing 10.04.
[00:05] <JontheEchidna> I don't believe it'd be a widespread issue, seeing as the update was a bugfix for slow scrolling in konqueror
[00:05] <JontheEchidna> and also since I'm not affected ;P
[00:05] <high-rez> Interesting.
[00:05] <neversfelde> probably something is wrong with file rights
[00:05] <genii> high-rez: I have exact same problem. I'm on my 9.04 now as 10.04 won't even startx
[00:05] <neversfelde> I am not affected, either
[00:06] <high-rez> Well X is starting for me, but kdeinit is segfaulting.  Guess I'll grab a coredump
[00:06] <genii> It seems to be related to nvidia driver somehow
[00:07] <neversfelde> nvidia here, too. No problems so far
[00:08] <genii> I had mismatched openGL.so type errors
[00:08] <JontheEchidna> that'd do it, there was a mesa update just a few hours ago
[00:09] <high-rez> genii: Yep, I'm getting the same spew from my logs....  It looks like libglcore is 196.36.03 and libglo is 195.30
[00:10] <high-rez> s/libglo/libgl
[00:12] <genii> high-rez: Yup. I did a dpkg -i --force-overwrite   for the latest version I had in /var/cache/apt/archives    and with the modalialases to match but still no love yet
[00:12] <high-rez> Wow
[00:13] <high-rez> I have both versions installed 190.30 and 195.36.03 ;)
[00:15] <genii> high-rez: I tried to unify to 195.36.03  but still fail. In fact even going to any ctrl-alt-F# console and trying to login produces copious kernel error output
[00:15] <genii> (between login and passwd prompt)
[00:15] <high-rez> Well Xorg version that it's installed is 195.36
[00:16] <high-rez> So I guess I'll just get rid of the 195.30 libs and relink to 195.36.03
[00:17] <high-rez> Clearly this is just user error though - having two versions of the driver installed at the same time is normal operating procedure, and only 1^h2 persons are able to seeing the issue.
[00:17]  * high-rez ducks
[00:23] <high-rez> genii: I'm back up.  Just deleted the 195.30 files and changed the links to 195.36.03 by hand.
[00:25] <genii> high-rez: And X starts without major bitching?
[00:25] <high-rez> Yep
[00:25] <high-rez> I'm on it now.  ;)
[00:25] <high-rez> Probably not the *right* thing to do, but its pretty clear that the repo is broken.
[00:25] <genii> high-rez: Ok. I'll give it a try on next reboot
[00:25] <genii> (I'm currently on my 9.04 )
[00:29] <high-rez> YMMV ;)
[00:29] <high-rez> Works for me.  I'm sure it'll be fixed soon enough - just gotta get someone to believe.  :)
[00:34] <neversfelde> high-rez: just restarted, no problems here
[00:43] <high-rez> neversfelde: What version of the module did it install for you?  It install 195.36.03 for me - but left libs for both 195.30 and 195.36.03 laying around.
[00:44] <high-rez> E.g. the 195.30 libs where in /usr/lib/ : /usr/lib/tls : /usr/lib/xorg : /usr/lib/vdpau - but the 195.36.03 libs were in /usr/lib/nvidia-current/ /usr/lib/nvidia-current/{tls,xorg,vdpau}
[01:23] <ryanakca> Ummm... is it normal that /var/log/messages and /var/log/kern.log both grow to 2.6G in five days ?
[01:26] <ryanakca> 3.3G even. ... all entries like "Feb 19 20:25:05 lambda kernel: [642321.196818] [UFW AUDIT] IN= OUT=wlan0 SRC=192.168.1.143 DST=192.168.1.255 LEN=29 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=55428 DPT=8765 LEN=9" ... bug worthy? I don't seem to recall this happening before dist-upgrading to lucid.
[01:32] <ryanakca> ... which completely filled up my hard drive... now that I've removed them, I can run 'apt-get update' and it doesn't hang... Shouldn't apt tell the user that they're out of disk space and quit instead of just hanging there and letting them wonder? Or is there a reason it doesn't?
[08:08] <apachelogger> Xand3r: I need more buzz followers ;)
[08:42] <apachelogger> hm
[08:42] <apachelogger> we need some moderating moderator for kubuntu-devel
[08:42] <apachelogger> I just noticed that the PPA mess thread got hijacked for discussion about why kde point releases should go to -updates
[08:45] <apachelogger> claydoh: what do you expect to document as use case on the PPA page?
[08:46] <apachelogger> daskreech: ultimately canonical would just drop us a server so I can live out my crazy deployment ideas ;)
[08:47] <daskreech> apachelogger: you mean ideally
[08:47] <apachelogger> though for CD remastering we could ask novell to enhance suse studio to also support kubuntu, so we can use it for that kind of love ;)
[08:48] <apachelogger> daskreech: I always do, yet I always write ultimately because ideally looks rather silly :P
[08:48] <apachelogger> check your irc logs
[08:48] <apachelogger> I never ever say ideally :P
[08:49] <apachelogger> kubotu: np
[08:49] <kubotu> apachelogger is listening to "No woman no cry (live)" by Bob Marley & The Wailers [One Love: The Very Best Of] [http://open.spotify.com/track/2mKsPUojh602HvSeNt04CB] -- see http://www.last.fm/user/apachelogger for more
[08:49]  * apachelogger sings
[09:38] <apachelogger> claydoh: i am hijacking the doc and turn it into a semi-policy
[09:38] <apachelogger> I suppose only devs need to understand the inner reasoning
[09:39] <apachelogger> user will just use what they get told anyway
[09:43] <apachelogger> so
[09:44] <apachelogger> Mamarok: ping
[09:56] <Mamarok> apachelogger: pong
[09:56] <apachelogger> Mamarok: so where should amarok updates go?
[09:56] <apachelogger> all to backports ppa?
[09:57] <apachelogger> or point releases to what we have in the latest release to the updates ppa and new major updates to backports?
[09:57] <Mamarok> the latter, of course, and beta to beta
[09:58] <Mamarok> since the point release of the shipped version are something the user expects, so updates makes sense
[09:59] <apachelogger> ok
[09:59] <apachelogger> holy smokes, the new toolbar is dragable
[10:01] <Quintasan> apachelogger: When I try to edit Sources in KPackageKit I get this -> http://pastebin.ca/1803546   is this known?
[10:01] <apachelogger> O
[10:01] <apachelogger> o
[10:02] <apachelogger> in the name of all that is holy
[10:02] <apachelogger> can we please burn python
[10:02] <apachelogger> Quintasan: you are using a polish system?
[10:02] <Quintasan> apachelogger:yup
[10:03] <apachelogger> that might be the problem then
[10:03] <Quintasan> judging from that shitty utf-8 implementation we should burn it
[10:03] <apachelogger> well, obviously the problem is that python is crap
[10:03] <apachelogger> but you using a polish system exposes that
[10:03] <apachelogger> Quintasan: python does not really have a utf8 implementation
[10:04] <apachelogger> we have all sorts of decoders/encoder functions to wrap around and do proper stuff
[10:04] <Quintasan> that's why it should burn in deepest depths of hell
[10:04] <apachelogger> my thinking exactly
[10:05] <apachelogger> JontheEchidna: we should fork software-properties, make it more dynamic, import it to kde svn and comaintain with debian
[10:05]  * apachelogger is so sick of all the python issues
[10:06]  * Quintasan <3 git
[10:06] <apachelogger> Quintasan: please kdesudo kate /usr/lib/python2.6/dist-packages/softwareproperties/kde/SoftwarePropertiesKDE.py
[10:06] <apachelogger> navigate to line 606
[10:06] <apachelogger> should be
[10:06] <apachelogger> before that enter
[10:06] <apachelogger> print key
[10:06] <apachelogger> but watch out that you do not mess up the indents!
[10:06] <apachelogger> the python will eat you like a gator
[10:07] <apachelogger> kubotu: google python gator
[10:07] <kubotu> Results for python gator: 1. Photo in the News: Python Bursts After Eating Gator (Update): http://news.nationalgeographic.com/news/2005/10/1006_051006_pythoneatsgator.html | 2. Gator-guzzling python comes to messy end - Science- msnbc.com: http://www.msnbc.msn.com/id/9600151/ | 3. State: Gator vs. python ends in gory draw: http://www.sptimes.com/2005/10/06/State/Gator_vs_python_ends_.shtml
[10:07] <Quintasan> print key?
[10:07] <apachelogger> well
[10:07] <apachelogger>     self.userinterface.treeview2.addTopLevelItem(QTreeWidgetItem([utf8(key)]))
[10:07] <apachelogger> that is the function that calls on utf8() with key
[10:08] <apachelogger> so you make it print the key before it does that
[10:08] <apachelogger> so we might have a chance of finding out what particular string makes the utf8 stuff go down
[10:08] <Quintasan> oh I see
[10:09] <Quintasan> Launchpad PPA for Micha�\x82 Zaj�\x85c
[10:09] <Quintasan> :D
[10:09] <apachelogger> cool :D
[10:09] <apachelogger> you are at fault
[10:09] <apachelogger> muhaahahah :D
[10:09] <Quintasan> however beats me where that string is
[10:09] <Quintasan> ah
[10:10] <Quintasan> It's a GPG key
[10:10] <Quintasan> :S
[10:10] <apachelogger> aight
[10:11] <Quintasan> hm, they ain't in my keyring, they are in roots keyring?
[10:11] <apachelogger> in the apt key ring
[10:11] <Quintasan> so, how do I access that
[10:11] <apachelogger> fooey
[10:11] <Quintasan> also I wonder if it's a problem with the key itself or python fails to parse it
[10:12] <apachelogger> Quintasan: /etc/apt/trustdb.gpg
[10:12] <apachelogger> or rather the too apt-key
[10:12] <Quintasan> hmm in Konsole it's listed normally
[10:12] <apachelogger> Quintasan: python fails to parse
[10:12] <Quintasan> let's kill python then
[10:12] <apachelogger> that is the error, it cannot convert to utf8 for some reason
[10:13] <apachelogger> Quintasan: either case I would expect a function called unicode() to freaking convert any encoding to the one I want ;)
[10:13] <apachelogger> not go crash the app
[10:13] <Quintasan> PyFail and it's FailImplementation
[10:13]  * apachelogger looks at his utf8() wrapper for apturl
[10:13] <Quintasan> I wouldn't be suprised if python has a epicfail()
[10:14] <apachelogger> right
[10:14] <apachelogger> Quintasan: did you do that print stuff already?
[10:14] <apachelogger> ah
[10:14] <Quintasan> yeah
[10:14] <apachelogger> silly me :
[10:14] <apachelogger> )
[10:14] <Quintasan> You're drinking too much :P
[10:15] <apachelogger> Quintasan: somewhere towards the top of that file you should find a function utf8()
[10:15] <apachelogger> Quintasan: I am on pain meds
[10:15] <Quintasan> oh
[10:15] <Quintasan> apachelogger: yeah, there is def utf8(str)
[10:16] <shadeslayer> apachelogger: btw what happened?
[10:16] <apachelogger> Quintasan: http://pastebin.ca/1803550
[10:16] <shadeslayer> some kind of accident?
[10:16]  * apachelogger likes to note that this work around is rather braindead
[10:17] <apachelogger> best you can do in python though
[10:17] <apachelogger> IIRC mvo and I were looking into that crap for quite some time
[10:17] <apachelogger> apturl also failed with similar issues
[10:18] <apachelogger> shadeslayer: no, about any desease you can imagine
[10:18] <Quintasan> apachelogger: awesome, works now, thanks
[10:18] <shadeslayer> apachelogger: ow... well hope you get well soon :)
[10:18] <apachelogger> Quintasan: I am not sure, but I think we fixed this in software-properties bzr already
[10:19] <shadeslayer> ill send a card :P
[10:19] <apachelogger> Quintasan: we were working quite a bit on localization, because half the UI was not localized at all
[10:20] <apachelogger> shadeslayer: that depends on the defintions of soon and well ... I mustn't do any sports for at least 6 months
[10:20] <shadeslayer> apachelogger: wow... thats some disease... :(
[10:21] <apachelogger> Quintasan: oh, btw, that is another silly thing, we have all sorts of different versions of that utf8() function, instead of having one almighty version in some central place
[10:21] <apachelogger> shadeslayer: yeah :/
[10:22] <shadeslayer_> oh well ive got to take a bath,bbl
[10:22] <Quintasan> apachelogger: well, needs sorting out I guess, but more importantly, what the hell are you doing, being sick and playing with PyFailCode is dangerous, want to fry your brain? You'd better rest now ;P
[10:22] <shadeslayer_> hehe :)
[10:24] <apachelogger> can't, I was not allowed to walk for like a week hence I am now in pain from walking around
[10:24] <apachelogger> more resting will only make things worse I suppose :/
[10:25] <apachelogger> amichair: was your work on software-properties merged yet?
[10:25] <Quintasan> Mamarok: mind explaining me something? When I pick Repeat Playlist and the Random Tracks the Repeat Playlist gets unselected, why?
[10:26] <apachelogger> amichair: seems so, judging from I18nHelper :)
[10:26] <Mamarok> because they are mutually exclusive, we still have to find an algorithm that works
[10:27] <apachelogger> Quintasan: would you mind building software-properties from bzr and trying if that also goes down?
[10:27]  * shadeslayer_ passes rock candy around
[10:27]  * Quintasan want's to have playlists that repeats and the tracks are in random order
[10:27] <apachelogger> Quintasan: it does not have that latin1 fallback but amichair changed quite some bits around, so maybe it does not fail anyway
[10:28] <apachelogger> Quintasan: as for the repeat+random ... use bangarang :P
[10:30] <Quintasan> UnicodeDecodeError: 'utf8' codec can't decode bytes in position 43-44: invalid data
[10:30] <Quintasan> :P
[10:30] <apachelogger> Quintasan: complete output please
[10:30] <Quintasan> apachelogger: http://pastebin.ca/1803564
[10:31] <Quintasan> apachelogger: exacly the same
[10:31] <apachelogger> sebas: oh, btw, I always thought that KDE needs a central place to store slides and other stuff from presentations
[10:32] <apachelogger> the old kdeslides page on kde.org was not used a lot :(
[10:33] <apachelogger> Quintasan: k, thx
[10:33] <apachelogger> fixing there
[10:36] <Quintasan> apachelogger: hmm, bangarang looks nice
[10:36] <apachelogger> yeah, very promising
[10:36] <apachelogger> + it uses nepomuk
[10:36] <Quintasan> though the library thing is bit tricky
[10:36] <Quintasan> and it just crashed
[10:36] <Quintasan> :O
[10:38] <apachelogger> well, promising, not perfect ;)
[10:39] <Quintasan> hmm, the thing I would only lack there is KRunner applet for it
[10:39] <Quintasan> :P
[10:41] <apachelogger> Quintasan: pushed fix for sp issue, please try again with r595
[10:41] <apachelogger> broken
[10:44] <amichair> apachelogger: howdy
[10:48] <apachelogger> Quintasan: pushed fix for sp issue, please try again with r595
[10:48] <amichair> amichair: what's the bad usecase / bug number?
[10:48] <apachelogger> amichair: no bug I suppose
[10:48] <amichair> oops, talking to myself again :-)
[10:48] <apachelogger> that too :P
[10:49] <amichair> apachelogger: was there one?
[10:50] <apachelogger> amichair: no, Quintasan can tell you what happened :)
[10:50] <amichair> Quintasan: please do!
[10:50] <Quintasan> yare yare, apacheloggerI just bzr'd and stil the same I have rev 42
[10:51] <apachelogger> Quintasan: 42?
[10:51] <apachelogger> Quintasan: that might be the wrong branch
[10:51] <apachelogger> bzr branch lp:software-properties
[10:51] <apachelogger> rev 1
[10:51] <apachelogger> pff cvs2svn
[10:51] <Quintasan> amichair: when trying to edit Software Sources I get a UTF-8 parse error on my GPG key (Michał Zając) -> http://pastebin.com/f46d0c645
[10:51] <apachelogger> and what about the cvs history?
[10:52]  * apachelogger wants to know about the very first KDE commit
[10:52] <Quintasan> rev 2
[10:52] <Quintasan> :<
[10:53] <apachelogger> ah
[10:53] <apachelogger> fun
[10:53] <apachelogger> rev 4
[10:53] <amichair> Quintasan: there was a bug long open on that - if it's what I think it is, it was a bug in gnupg which was fixed (I think the updated upstream package was merged eventually)
[10:53] <apachelogger> german commit message :D
[10:53] <apachelogger> <3 coolo
[10:53] <apachelogger> Quintasan: maybe that is the cvs history?
[10:54] <apachelogger> would explain the german for sure
[10:54] <Quintasan> apachelogger: fix'd now, works :)
[10:54] <apachelogger> rev 2 is from Sun Apr 13 14:42:44 1997 UTC (12 years, 10 months ago)
[10:54] <apachelogger> sure is from cvs :D
[10:54] <Quintasan> amichair: it's not a problem in gpg, it's a problem with failimplementation of utf-8 in python
[10:55] <Quintasan> at least that's what I conclude because it works now
[10:55] <apachelogger> amichair: see the diff of my last commit
[10:55] <amichair> well there was a gnupg bug - otherwise upstream wouldn't have fixed it :-)
[10:55] <apachelogger> for some reason I do not even want to know unicode() fails on converting that gpg key name (possibly because it already is utf8?)
[10:55] <amichair> but maybe there's another!
[10:56] <amichair> how can I see closed bugs in lp?
[10:56] <apachelogger> amichair: search for it in the advanced search
[10:56] <apachelogger> lp UI is rather cruel in a lot of aspects, searching closed bugs is one of those :S
[10:58] <amichair> looks like bug 133937
[11:00] <shadeslayer> um.. can everyone update from the main servers? i cant :(
[11:00] <apachelogger> amichair: sounds like it from the description
[11:00] <amichair> are y'all using gnupg >= 1.4.10 when this happens?
[11:00] <apachelogger> does not happen here at all
[11:01] <amichair> so only Quintasan is seeing the bug?
[11:01] <apachelogger> well, I do not have keys with non-latin names in my ring :P
[11:01] <Quintasan> gnupg - Version: 1.4.9-4ubuntu7
[11:02] <Quintasan> amichair: and after apachelogger pushed some pyhaxes it worked
[11:02] <Quintasan> apachelogger: add mine PPA then :P
[11:02] <apachelogger> nah
[11:02] <apachelogger> better not
[11:02] <Quintasan> :3
[11:02] <apachelogger> who knows what happens :P
[11:02]  * apachelogger is writing dev documentation
[11:02] <Quintasan> hmm it's not like I have anything except gluon and mac there
[11:03] <amichair> so it sounds like you're using the old gnupg before they fixed it. they had a bug that the output in some cases was not proper utf8. they fixed it. the sp code doesn't require any changes...
[11:04] <Quintasan> amichair: sudo apt-key list works fine with not damned symbols
[11:04] <Quintasan> no*
[11:04] <Quintasan> and gpg --list-keys also outputs normal utf
[11:05] <amichair> the bug is only with certain command line options, which sp happens to use
[11:05] <amichair> you can see the dirty details at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=540340
[11:06] <Quintasan> amichair: well, seems legit I guess :P
[11:07] <Quintasan> amichair: and IMO s-p is partly to blame for using such obscure cli options :P
[11:07] <amichair> don't look at me, I just fixed someone else's code ;-)
[11:08] <apachelogger> amichair: I always find it depressing to fix someone else's code :P
[11:09] <apachelogger> mostly because I do not like how the code of others looks like :P
[11:09] <apachelogger> Quintasan: https://wiki.kubuntu.org/Kubuntu/KubuntuPPAs lucid enough? ;) ;) ;)
[11:09] <amichair> some day you'll get to fix my bugs as well... it's the vicious circle of bug-life :-)
[11:09] <apachelogger> probably to get more anal about what cannot go into the particular PPAs
[11:10] <Quintasan> apachelogger: >monor
[11:10] <Quintasan> Shouldn't be minor?
[11:12] <amichair> apachelogger: where can I see ur fix?
[11:12] <Quintasan> apachelogger: anyways, awesome, now I clearly get to know what goes where :P
[11:15] <Quintasan> fcks, I can't remember my LP password
[11:15] <shadeslayer> lol....
[11:22] <apachelogger> lol indeed
[11:22] <apachelogger> amichair: bzr branch lp:software-properties
[11:22] <apachelogger> Quintasan: yes, I did not write that though
[11:23] <apachelogger> Quintasan: are you sure it is clear enough what has to go where?
[11:23]  * apachelogger finds it a shame that google docs is so much more useful than those damn wikis
[11:23] <Quintasan> apachelogger: For me? Pretty clear, can't say for others but I guess it will be the same
[11:24] <shadeslayer> apachelogger: i agree :)
[11:24] <apachelogger> shadeslayer: pleaes read https://wiki.kubuntu.org/Kubuntu/KubuntuPPAs
[11:25] <apachelogger> and say if you find it clear enough to understand which packages need to be published to which ppa
[11:26] <shadeslayer> apachelogger: i read it,but why did i read it?
[11:26] <apachelogger> so that I know if it is clear enough :P
[11:26] <apachelogger> or if I need to explain in more detail what belongs where
[11:26] <apachelogger> must be super understandible to everyone
[11:26] <shadeslayer> apachelogger: ah... yeah its pretty clear,but the last kpackagekit link isnt working
[11:27] <shadeslayer> https://wiki.kubuntu.org/community/Repositories/Kubuntu
[11:27] <apachelogger> oh
[11:27] <apachelogger> yeah
[11:27] <apachelogger> fix0red
[11:27] <apachelogger> shadeslayer: thx
[11:28] <shadeslayer> apachelogger: no problem :)
[11:31] <apachelogger> oh my, because of good charlotte I just spilled my tea
[11:31] <apachelogger> amarok must be insane coming up with such unbarable music
[11:31]  * apachelogger goes all delete on that
[11:32] <Mamarok> what Charlotte?
[11:32]  * Mamarok just deleted a horrible Paolo Conte track
[11:32] <apachelogger> kubotu: google last.fm good charlotte
[11:32] <kubotu> Results for last.fm good charlotte: 1. Good Charlotte – Discover music, videos, concerts, & pictures at ...: http://www.last.fm/?artist=Good+Charlotte | 2. Good Charlotte – The Anthem – Video & free listening at Last.fm: http://www.last.fm/music/Good+Charlotte/_/The+Anthem | 3. Good Charlotte – Predictable – Video & free listening at Last.fm: http://www.last.fm/music/Good+Charlotte/_/Predictable
[11:34]  * shadeslayer wonders if kubotu is KDE'ish enough :P
[11:34] <apachelogger> mhh, goldfinger
[11:35] <apachelogger> seaLne: ping
[11:36] <shadeslayer> apachelogger: btw there are loads if incoming bugs on akonadi not starting in 4.4,any known fixes?
[11:37] <apachelogger> would have to look into that
[11:37] <Mamarok> shadeslayer: it starts here when I start Kontact, in Karmic
[11:37] <apachelogger> shadeslayer: are they lucid and karmic?
[11:37] <apachelogger> or just karmic?
[11:37] <shadeslayer> karmic+KDE 4.4
[11:37] <apachelogger> shadeslayer: on launchpad?
[11:37] <apachelogger> or elsewhere?
[11:38] <shadeslayer> i have the same problem as well....
[11:38] <shadeslayer> apachelogger: bugs on lp..
[11:38] <apachelogger> hm
[11:38] <shadeslayer> one sec
[11:38] <apachelogger> bug 524538 looks fooey
[11:38] <apachelogger> was wondering about that while going through gmail
[11:39] <shadeslayer> yeah i subscribed to kubuntu bugs and thats when i noticed this influx
[11:39] <shadeslayer> there were 2-3 more...
[11:40] <apachelogger> oha
[11:40] <shadeslayer> https://bugs.launchpad.net/bugs/448705
[11:40] <apachelogger> bug 524538 and bug 448705 are actually the same it seems
[11:40] <shadeslayer> https://bugs.edge.launchpad.net/bugs/524468
[11:41] <shadeslayer> thats about it i think :)
[11:42] <apachelogger> foobar
[11:42] <apachelogger> thar report is mostly invalid
[11:42] <shadeslayer> hmm
[11:42] <apachelogger> no plasma was fixed by adding kubuntu-meta to the ppa, if he got his kubuntu-desktop removed, then that is his problem
[11:43] <apachelogger> akonadi error is the same as presented already
[11:43] <apachelogger> Test 6: SKIP
[11:43] <apachelogger> --------
[11:43] <apachelogger> MySQL server custom configuration not available.
[11:43] <apachelogger> Details: The custom configuration for the MySQL server was not found but is optional.
[11:43] <apachelogger> maybe the new akonadi uses the system config if no other is found?
[11:44]  * apachelogger nukes his akonadi data
[11:44] <shadeslayer> hehe
[11:44] <shadeslayer> well ive marked them as duplicates of 448705
[11:44] <shadeslayer> since that one is a confirmed bug
[11:45] <apachelogger> aha
[11:45] <apachelogger> akonadi indeed comes up with error
[11:45] <shadeslayer> hmm.. qmysql problem?
[11:45] <apachelogger> no
[11:45] <apachelogger> apparmor
[11:45] <shadeslayer> ah...
[11:45] <apachelogger> that stupid thing is annoying me for years now
[11:46] <shadeslayer> i thought i heard that one too in one of the bug reports
[11:46] <apachelogger> well, easy enough to fix
[11:46] <shadeslayer> ok its in the 524538 report
[11:47] <shadeslayer> Mamarok: kontact hasnt even started for me yer
[11:47] <shadeslayer> stuck at " Starting Akonadi Server "
[11:48] <Mamarok> I had Akonadi refusing to start in 4.3.5, but not with 4.4 so far
[11:48] <shadeslayer> http://pastebin.ca/1803603 << my error report
[11:48] <apachelogger> I need a new dns provider
[11:50] <uelapeppa> hi
[11:50] <uelapeppa> how do you create official ISOs?
[11:50] <shadeslayer> uelapeppa: um what?
[11:51] <shadeslayer> uelapeppa: afaik there are build scripts in bzr which do that
[11:51] <shadeslayer> i could be wrong though
[11:53] <uelapeppa> shadeslayer: could you link some doc, please?
[11:54] <shadeslayer> uelapeppa: um nope :(
[11:55] <uelapeppa> shadeslayer: ok np
[11:55] <shadeslayer> uelapeppa: im just guessing,im not sure though
[11:56] <uelapeppa> i want to create a custom iso from scratch
[11:59] <apachelogger> uelapeppa: google for it
[11:59] <apachelogger> there are two launchpad project IIRC
[11:59] <apachelogger> ubuntu-cd or something
[12:00] <apachelogger> those combined with a whole load of other tools and stuff form the infrastructure to build CDs
[12:30] <apachelogger> mhh
[12:41] <apachelogger> mysql is so awesome
[12:41] <apachelogger> incredibly
[12:41] <apachelogger> almost as awesome as python
[12:42] <apachelogger> so opportunistic
[12:42] <apachelogger> takes every opportunity of not doing the right thing
[12:42] <apachelogger> incredible really
[12:48] <apachelogger> and how I do hate akonadi for using that crap
[12:49] <Tm_T> apachelogger: and Amarok?
[12:49] <apachelogger> amarok at least embedds it
[12:49] <shadeslayer> apachelogger: theres postgreSql too :P
[12:49] <apachelogger> yeah
[12:49] <apachelogger> Riddell: I propose we use postgres for akonadi
[12:49] <Tm_T> apachelogger: if possible, that is
[12:49] <apachelogger> mysql is freaking killing me
[12:51] <shadeslayer> this is just lol : https://bugs.launchpad.net/ubuntu/+source/kpackagekit/+bug/524748
[12:51] <shadeslayer> last comment ;)
[12:52] <apachelogger> ahhhhhhh
[12:52] <apachelogger> uhhhhh
[12:52] <apachelogger> maybe
[12:52]  * apachelogger tries something
[12:53] <apachelogger> oh well
[12:53] <apachelogger> I hate it
[12:55] <apachelogger> http://userbase.kde.org/Akonadi#Table_.27mysql._servers.27_doesn.27t_exist
[12:55] <apachelogger> the interesting thing here is that the freaking file is in place
[12:56] <apachelogger> on subsequent starts akonadi does not have any problems
[12:58] <apachelogger> this is so silly -.-
[12:58] <shadeslayer> apachelogger: the kde nm in your ppa,is it stable enough?
[12:58] <apachelogger> shadeslayer: it is freaking superior to any other version you will find
[12:58] <apachelogger> it even works with wifi and vpn
[12:59] <shadeslayer> ok well,somebody has a network problem in #kubuntu
[13:00] <apachelogger> well
[13:00] <apachelogger> the default knm is the crap
[13:01] <shadeslayer> hehe
[13:03] <apachelogger> I dont get this akonadi business
[13:04] <shadeslayer> apparently i dont have akonadi-kde installed
[13:04] <shadeslayer> meh transitional
[13:10] <shadeslayer> apachelogger: http://pastebin.com/fac9a965
[13:10] <shadeslayer> if it helps
[13:17] <apachelogger> well
[13:17] <apachelogger> I am out of options here
[13:20] <apachelogger> kubotu: np
[13:20] <kubotu> apachelogger is listening to "Wrong" by Depeche Mode [http://open.spotify.com/track/6BS4QLnPIHzVA7CGERW2ne] -- see http://www.last.fm/user/apachelogger for more
[13:25] <apachelogger> well
[13:25] <apachelogger> screw it
[13:25]  * apachelogger doesnt wanna look at it anymore
[13:44] <claydoh> apachelogger: re the ppa wiki page: attempting to better define for users why they might want to use a particular ppa
[13:44] <claydoh> then I got confused enough myself
[13:45] <shadeslayer_> claydoh: haha
[13:48] <apachelogger> claydoh: IMHO they might because kubuntu.org tells them to do so in order to get latest amarok ;)
[13:48] <apachelogger> shadeslayer_: so
[13:48] <apachelogger> i do know that mysql is crap
[13:48] <apachelogger> no news here
[13:48] <apachelogger> BUT
[13:49] <apachelogger> it is also the crappyness behind the akonadi issue at hand (dunno why though)
[13:49] <apachelogger> if you manually initialize the db using mysql_install_db and ensure the tables are all upgraded it seems to start properly
[13:50] <shadeslayer_> ok lemme try
[13:50] <apachelogger> well maybe not for your issue
[13:50] <apachelogger> because yours is different
[13:50] <shadeslayer_> apachelogger: http://pastebin.ca/1803669
[13:53] <apachelogger> ah
[13:53] <apachelogger> srsly
[13:53] <apachelogger> I do not want to look into this any longer
[13:53] <apachelogger> it also affects lucid btw
[13:53] <apachelogger> Riddell: I propose we deploy with postgres
[13:55] <claydoh> apachelogger: well, there are plenty that dent/tweet/post to use staging whenever they smell fresh packages in there as well :/
[13:55] <shadeslayer_> heh
[13:55] <apachelogger> it got one big fat DONT USE attached to the name
[13:56] <claydoh> apachelogger: they actually read that stuff?
[13:56] <apachelogger> they actually read a wiki page explaining why they would want to use a PPA?
[13:56] <claydoh> some are just using a reposomeone posted without even going to the ppa page
[13:56] <apachelogger> 4 word name vs. couple of hundred word wiki page
[13:56] <claydoh> apachelogger: got me on that one
[13:57] <apachelogger> wellz
[13:58] <apachelogger> the akonadi issue looks like this
[13:58] <apachelogger> akonadi is unwilling to invoke the db initialization binary of mysql
[13:58] <apachelogger> (not that it would be available right now)
[13:58] <apachelogger> without that it seems that no proper db gets created
[13:58] <apachelogger> which makes mysql all whiny
[13:59] <apachelogger> at times I really ponder switching desktops
[14:01] <shadeslayer_> kubotu: np
[14:01] <kubotu> shadeslayer_ listened to "Fireflies" by Owl City [Ocean Eyes, 2010] 4 weeks ago; [http://open.spotify.com/track/1mr3616BzLdhXfJmLmRsO8] -- see http://www.last.fm/user/shadeslayer_ for more
[14:06] <apachelogger> this is so silly -.-
[14:12] <shadeslayer_> apachelogger: do you think its a packaging or upstream bug?
[14:13] <apachelogger> shadeslayer_: I am not sure
[14:13] <apachelogger> could be both
[14:13] <shadeslayer_> hmm
[14:13] <apachelogger> because
[14:13] <apachelogger> it is defenitely not related to the default akonadi config
[14:13] <apachelogger> and also not to our mysql, because it worked just fine on karmic before
[14:13] <shadeslayer_> yeah..
[14:13] <apachelogger> so either upstream changed how they init mysql
[14:14] <shadeslayer_> or the config changed?
[14:14] <apachelogger> or we did some packaging screwup that makes akonadi incapable of initing properly
[14:14] <apachelogger> shadeslayer_: did not
[14:14] <apachelogger> I checked
[14:14] <shadeslayer_> oh ok
[14:16] <shadeslayer_> lemme see if google has a answer :P
[14:16] <Dario_Andres> Hi. Is "adept" still maintained ? thanks in advance.
[14:16] <apachelogger> shadeslayer_: better ask in #akonadi
[14:17] <apachelogger> Dario_Andres: I think debian is maintaining it
[14:17] <Dario_Andres> thanks apachelogger, I will ask
[14:17] <apachelogger> yw
[14:25] <apachelogger> weeh
[14:25] <apachelogger> the akonadi thingy is too cross-distro to be a packaging issue
[14:26] <apachelogger> it is just that mysql is useless and that akonadi does not work around the uselessness by using postgre -.-
[14:40] <apachelogger> Riddell:
[14:41] <Riddell> harald:
[14:41] <apachelogger> whoops, silly touchpad :)
[14:41] <apachelogger> but since you are here
[14:41] <apachelogger> Riddell: ideas about mysql?
[14:42] <apachelogger> Riddell: it seems mysql 5.1 requires another binary to be run to make it start without errors
[14:42] <Riddell> maybe http://userbase.kde.org/Akonadi#Apparmor
[14:42] <apachelogger> no, it's not apparmor
[14:43] <apachelogger> Riddell: search for mysql.servers on that page
[14:43] <apachelogger> that is the problem at hand
[14:43] <apachelogger> and only the command at the very bottom of that section fixes the issue
[14:43] <apachelogger> and apparently that is common to all mysql 5.1 setups
[14:43] <Riddell> dunno I'm afraid, I need to go
[14:44] <apachelogger> hm, ok :)
[14:44]  * apachelogger needs to write a mail about the mess once he is in not so angry mood
[14:52] <txwikinger2> hi Riddell
[15:20] <shadeslayer> apachelogger: oh btw the nm in your PPA,it can connect to WEP too right?
[15:20] <shadeslayer> WEP wifi i mean
[15:30] <apachelogger> shadeslayer: I have no clue, I'd rather get run over by a bus than use wep
[15:30] <shadeslayer> hehe :)
[15:31] <shadeslayer> well my college uses wep and i spent 30 mins trying to get in :P
[15:31] <apachelogger> Oo
[15:31] <shadeslayer> apachelogger: nm kept asking me for the password
[15:32] <apachelogger> so what exactly would be the point of that?
[15:32] <apachelogger> I mean using wep
[15:32] <shadeslayer> idk.. we have like 5 networks... some are available at a place while others are not
[15:32] <apachelogger> so that you can tell the administration, oh our wifi is all secure, look there is a lock icon in your windows connection manager
[15:32] <apachelogger> must be secure obviously
[15:32] <shadeslayer> out of those 5,3 are secured... for faculty :P
[15:32] <apachelogger> with wep?
[15:32] <apachelogger> secured?
[15:33] <apachelogger> oh my
[15:33] <shadeslayer> one of them is for students... which is always overloaded
[15:33] <shadeslayer> apachelogger: needs a wep passphrase
[15:33] <apachelogger> kubotu: wp wep
[15:33] <kubotu> Results for wep: 1. Wired Equivalent Privacy - Wikipedia, the free encyclopedia: http://en.wikipedia.org/wiki/Wired_Equivalent_Privacy | 2. WEP - Wikipedia, the free encyclopedia: http://en.wikipedia.org/wiki/WEP | 3. Wi-Fi Protected Access - Wikipedia, the free encyclopedia: http://en.wikipedia.org/wiki/Wi-Fi_Protected_Access
[15:33] <kubotu> [1] Wired Equivalent Privacy (WEP) is a deprecated algorithm to secure IEEE 802.11 wireless networks. Wireless networks broadcast messages using radio and are thus more susceptible to eavesdropping than wired networks. When introduced in 1997,[1] WEP was intended to provide confidentiality comparable to that of a traditional wired network.
[15:34] <apachelogger> wep is not secure
[15:34] <shadeslayer> apachelogger: and the last is so weak that i have place my laptop in special postions to catch it
[15:34] <apachelogger> end of discussion
[15:34] <shadeslayer> apachelogger: i know :P
[15:34] <apachelogger> anyway
[15:34] <apachelogger> it might very well be that the version from my ppa does not like wep
[15:34] <apachelogger> then again I personally do not care about that :P
[15:35] <apachelogger> as long as unsecure, wpa* and vpnc is working I am all happy
[15:36] <apachelogger> steveire: how are we supposed to deploy akonadi if that beast refuses to start properly?
[15:36] <apachelogger> without having the user execute a command
[15:36] <apachelogger> that, just for the fun of it is on ubuntu in a package that drags in all of mysql
[15:46] <shadeslayer> apachelogger: hmm.. fair enough.. lets see how it works out when i take my laptop next time... its usually just for KDE upgrades once in a while.. i get speeds of 800 KBps there :P
[15:55] <apachelogger> claydoh: so, what do you think of the enhanced version?
[16:05] <apachelogger> rdieter: hai! is fedora also affected by kde bug 185395
[16:05] <shadeslayer> apachelogger: the one which we have too?
[16:06] <apachelogger> yes
[16:06] <apachelogger> launchpad bug 448705
[16:06] <shadeslayer> aha! not our problem then :P
[16:06]  * shadeslayer goes and links both bugs 
[16:06] <apachelogger> already did that :P
[16:07] <shadeslayer> :D
[16:07] <shadeslayer> irssi is failing :P
[16:08] <shadeslayer> looks like it affects some but not others 0_o
[16:09] <shadeslayer> ok ive gtg and test out chromium-flow.... brb
[16:14] <apachelogger> oh my
[16:14] <apachelogger> Riddell: please make kubuntu-dev maintainer of kubuntu-defaults-settings project
[16:14] <apachelogger> and/or set a default branch for it
[16:20]  * shadeslayer is in awe
[16:21] <shadeslayer> i now fully realize why chrome os is specifically meant for netbooks :P
[16:21] <nixternal> cuz it sucks?
[16:22] <shadeslayer> nope
[16:22] <nixternal> I mean, it is good for people who really don't "use" a computer, but I didn't like it when I tried it
[16:22] <shadeslayer> nixternal: it looks HUGE on my 15 inch screen
[16:23] <daskreech> That's cause google has big ...umm I forget what. you can google it
[16:23] <nixternal> personally I feel android is enough reason for ChromeOS to not exist. Twitter, Facebook, GMail, and that type of shite is perfect for an Android phone
[16:23] <rdieter> apachelogger: don't think so, haven't seen that one myself (relatedly, we're looking at kde bug 226960 atm)
[16:23] <seaLne> apachelogger: pong?
[16:23] <nixternal> it hasn't been getting great reviews either
[16:24] <shadeslayer> hmmm im gonna install it..
[16:24] <shadeslayer> for times i just need to check my mail :)
[16:25] <shadeslayer> bye!
[16:26] <apachelogger> rdieter: uhm, good thing we are already in feature freeze, so hopefully the ubuntu server team will not land .43 ... if only akonadi used a sensible database ;)
[16:26] <apachelogger> seaLne: where would one get a KDE irc cloak from?
[16:26] <rdieter> apachelogger: :)
[16:27]  * apachelogger goes into ecma mode and improves plasma config scripts
[16:28] <ryanakca> Should I file a bug for http://ryanak.ca/~ryan/nepomuklog against virtuoso or nepomuk? It's happening on both computers I've dist-upgraded karmic->lucid.
[16:29] <shadeslayer> ryanakca: thanks for the awesome site :)
[16:29] <ryanakca> shadeslayer: :)
[16:30] <shadeslayer> ryanakca: i hope that some great artwork is in the making :P
[16:38] <seaLne> apachelogger: ask me :)
[16:43] <apachelogger> seaLne: can I have a nice and cosy KDE irc cloak pretty please :)
[16:44] <shadeslayer> hehe
[16:45] <apachelogger> hum
[16:45] <Quintasan> oh man, I fell asleep on keyboard
[16:45] <Quintasan> how rare
[16:45]  * apachelogger is wondering why hasBattery is not working from the plasma scripting api
[16:45] <shadeslayer> Quintasan: was the keyboard comfy?
[16:45] <apachelogger> Quintasan: never ever happened to me
[16:45] <yuriy> dear facebook, konqueror is not a mobile browser (yet)
[16:45] <apachelogger> esp not in the middle of the day :D
[16:45] <shadeslayer> yuriy: +1
[16:45] <apachelogger> +1
[16:46] <Quintasan> shadeslayer: not really, I wouldn't bez suprised if I have a Z on my cheek
[16:46] <apachelogger> though there is a konqueror embedded
[16:46] <apachelogger> or was
[16:46] <apachelogger> long time ago
[16:46] <Quintasan> be*
[16:48] <shadeslayer> :D
[16:52] <Quintasan> oh man this new keyboard is a bit tricky but awesome
[16:53] <Quintasan> For the first time in my whole life time I have to say microsoft did a good job
[17:09] <apachelogger> beautiful
[17:10] <apachelogger> Riddell: the plasma update script also gets executed after default-setup
[17:10] <apachelogger> that would also explain why hasBattery did not work
[17:18] <apachelogger> * [Whois] apachelogger is apachelogger!~quassel@kde/developer/sitter (Harald Sitter)
[17:18]  * apachelogger hugs seaLne
[17:18] <apachelogger> thanks :)
[17:24] <apachelogger> IMHO the plasma updates script got a beauty issue
[17:24] <apachelogger> anywhow
[17:24] <EagleScreen> Kubuntu installer does not fit in an Asus Eee-PC screen
[17:24]  * apachelogger made the battery applet only be added when hasBattery is true :D
[17:24] <apachelogger> no more battery applet on workstations
[17:30] <seaLne> apachelogger: np
[17:30] <seaLne> EagleScreen: yes it fails very badly on the 701
[17:32] <apachelogger> nixternal: shall we launch a commit mailing list for bzr commits?
[17:32] <apachelogger> lp team kubuntu-commits with associated list
[17:32] <claydoh> apachelogger: wiki page look good
[17:32] <apachelogger> claydoh: cool
[17:33] <claydoh> graphics help, too :)
[17:33] <apachelogger> claydoh: can you ditch it up on the ppa thread on the ml for final review?
[17:33] <apachelogger> I am a bit short on sensible mail clients :)
[17:35] <daskreech> alpine!
[17:35] <Quintasan> lol kmail?
[17:35] <apachelogger> not setup
[17:36] <claydoh> lol
[17:38] <apachelogger> hm
[17:38] <apachelogger> according to lp ubuntu lists should be created at lists.ubuntu.com
[17:38] <apachelogger> oh wellz
[17:52] <claydoh> apachelogger: email sent
[17:58] <daskreech> apachelogger: do you have a glut of insensible mail clients? :)
[18:21] <ryanakca> Could someone ack bug 524982 please?
[19:22] <jjesse> interesting question:  just download the live cd from yesterday and noticed the folder view plasmoid shows the home directory instead of desktop, is this on purpose?  had to open up desktop and then find the installer icon
[19:23] <jjesse> oh cool, you can now update the installer when you got installer, thats pretty cool
[19:37] <blueyed> where are the debug symbols for /usr/lib/qt4/plugins/phonon_backend/phonon_xine.so ?
[19:38] <Quintasan> damn I'm sooo lazy
[19:38] <blueyed> found it: phonon-backends-dbg
[19:42] <apachelogger> oh fancy
[19:42] <apachelogger> I already endosred neversfelde ^^
[19:42] <apachelogger> didnt remember that :D
[19:42] <apachelogger> jjesse: bug in kds I would suspect
[19:43] <apachelogger> yes, buggy
[19:43] <jjesse> apachelogger: ok should i report it?
[19:43] <apachelogger> nah
[19:43] <apachelogger> already on the fix
[19:50] <Quintasan> apachelogger: hey, got a second?
[19:52] <jjesse> hrmm after configuring disks, ubuiquity disappears
[20:00] <apachelogger> Quintasan: possibly
[20:00] <apachelogger> this scriptingness here doesnt want to follow my orders again ^^
[20:02] <Quintasan> apachelogger: well I got a cpp related question, my book covers things like implementing functions that return or accept structures as parameters and I was wondering whether it's actually used anywhere near Qt/KDE development or I can skip it for now
[20:04] <apachelogger> Quintasan: well, of course it is used at times ;)
[20:04] <Quintasan> hngh, couldn't they realease NM 0.8 earlier?
[20:04] <Quintasan> apachelogger: at times?
[20:05] <apachelogger> Quintasan: it depends, there are reasons to use structs and there are reasons not to use structs
[20:05] <apachelogger> depending on your book it might either make sense to read the section or not :P
[20:05] <Quintasan> apachelogger: well, would you say its safe to skip it for now?
[20:05] <apachelogger> no
[20:06] <apachelogger> they are an essential paradigm of C(++)
[20:06] <apachelogger> you can think of them as very very simple object templates in C
[20:07]  * Quintasan turns 20 pages back
[20:07] <Quintasan> :D
[20:07] <apachelogger> so if you want to implement a very small stoarge type in cpp you will probably still use a struct
[20:07] <apachelogger> even if you could archive the same with implementing a whole new class
[20:08] <Quintasan> apachelogger: I can imagine implementing a whole new class for this wouldnt be efficient, would it?
[20:08] <apachelogger> aight
[20:09] <Quintasan> well, the examples they put here are little bit hmmm, strange
[20:09] <Quintasan> C++ Primer Plus by Stephen Prata :S
[20:09] <apachelogger> Quintasan: get a C book and read about structs there :P
[20:10] <apachelogger> structs can only be understood from a C perspective :P
[20:10] <Quintasan> apachelogger:  I got the same book about C from that guy and well, it basically does the same thing with few exceptions like using printf
[20:10] <Quintasan> :P
[20:10] <apachelogger> lol
[20:11] <dhillon-v10> Quintasan, apachelogger hi :)
[20:11] <apachelogger> Quintasan: well, what does he wanna explain anyway?
[20:11] <apachelogger> hullos dhillon-v10
[20:11] <Quintasan> sup dhillon-v10
[20:11] <apachelogger> Quintasan: structs are rather simple, as everything else within C, since it is just a very neat asm container ;)
[20:12] <Quintasan> apachelogger: I know about structs, I finished reading about functions which take arrays as parameter and how to declarate prototypes and such
[20:13] <dhillon-v10> apachelogger: structs are pretty darn useful especially while making patches for linux-kernel :)
[20:13] <Quintasan> apachelogger: and then I've got source for simple app that adds whole array of variables and then he tells you can do it a few different ways etc.
[20:14] <apachelogger> sounds like a crappy example then :P
[20:14] <dhillon-v10> Quintasan: learning java in school, it beats every other language hands-down :)
[20:14] <apachelogger> Quintasan: well read it, maybe you will come to understand it later
[20:14] <apachelogger> one never knows with those books
[20:14] <apachelogger> haha
[20:14] <apachelogger> java
[20:14] <Quintasan> apachelogger: then he goes Cpt. Obvious why pointer to an array has sizeof 4
[20:15] <apachelogger> next semster
[20:15] <apachelogger> database course
[20:15] <apachelogger> with java programming
[20:15] <apachelogger> hrrhrr :D
[20:15] <Quintasan> dhillon-v10: lol java
[20:15] <dhillon-v10> apachelogger: java is pretty simple really :)
[20:15] <apachelogger> my former flatmate had almost gone insane because of java
[20:15] <apachelogger> dhillon-v10: java is an abomination of sanity
[20:15] <dhillon-v10> Quintasan: have you tried java?
[20:15] <Quintasan> it's just me or java is more strange than assembly?
[20:15] <apachelogger> and that I say as someone who was madly in love with the insanity bot :P
[20:15] <Quintasan> dhillon-v10: yeah, gave me a mindfuck at the very start
[20:16] <apachelogger> Quintasan: java is about as random as python
[20:16] <Quintasan> apachelogger: XD
[20:16] <apachelogger> no, hold on
[20:16] <dhillon-v10> apachelogger: lol :) I have been working with it for a while now
[20:16] <apachelogger> taking the awesomeness of cpp
[20:16] <apachelogger> add the randomness of python
[20:16] <dhillon-v10> Quintasan: lol
[20:16]  * Quintasan loves his new keyboard
[20:16] <apachelogger> and add pitiful approaches to xplatformness
[20:16] <apachelogger> then you get java
[20:16] <apachelogger> oh more randomness might be needed
[20:17] <dhillon-v10> apachelogger: one of the best things about java is the *vast* api that it has, all the little tasks can just be called in a single line method :)
[20:17] <Quintasan> sooo java is like cpp + lolpython?
[20:17] <apachelogger> python actually got some sane paradigms in all the randomness
[20:18] <apachelogger> dhillon-v10: well, if you like it
[20:18] <dhillon-v10> apachelogger: so KDE mostly uses cpp right?
[20:19] <apachelogger> so I have been told
[20:19] <Quintasan> I like c++ but I find the learning proccess tedious somtimes
[20:19] <apachelogger> Quintasan: if I were you I would get the basics straight and then digg into some handson work and learn as you go along
[20:19] <Quintasan> apachelogger: basics being?
[20:20] <dhillon-v10> apachelogger: are there a lot of differences in c and c++ besides that c++ is object oriented
[20:20]  * Quintasan thinks he might have covered basics but his understanding of "basics" might be a litte bit off
[20:20] <apachelogger> Quintasan: how to create a class, what a pointer is, basic data types, how to create a function, difference of call-by-reference and call-by-value, dynamic mem mangement
[20:21] <apachelogger> I think that is about all you need to know to create a simple app
[20:21] <Quintasan> soo, I need two things now
[20:21] <Quintasan> call-by-reference and value and classes
[20:21] <apachelogger> in fact I suppose you can even ignroe dynamic mem for starters
[20:21] <Quintasan> :P
[20:21] <apachelogger> not too important in cpp with kde and qt
[20:21] <apachelogger> dhillon-v10: C is an asm container, cpp is a programming language :P
[20:22] <Quintasan> apachelogger: dynamic mem being something like int * lol = new int [10];  ?
[20:22] <Quintasan> or malloc
[20:22] <Quintasan> who cares
[20:22] <apachelogger> dhillon-v10: really, cpp is a lot different from c
[20:22] <apachelogger> which is probably most coming from the object orientation ;)
[20:23] <Quintasan> apachelogger: pointers to functions? lol
[20:23] <dhillon-v10> apachelogger: ahh :) so how long do you think it would take me to learn cpp, i am pretty good at c
[20:23] <apachelogger> Quintasan: latter, former is on the stack
[20:24] <apachelogger> dhillon-v10: not long, as I said, java has a lot in common with cpp
[20:24] <apachelogger> well, not the randomness and the fake xplatformness :P
[20:25] <dhillon-v10> apachelogger: :) okay, after AMC is over I am going to look more into cpp
[20:25] <apachelogger> cool
[20:25] <apachelogger> Quintasan: also makes more sense to read when you need such a thingy ;)
[20:26] <apachelogger> I am not sure pointers to functions are very common in kde programming really
[20:26]  * apachelogger loved to use them in C :D
[20:27] <Quintasan> apachelogger: the book says that knowledge is not really useful to programmer unless you are doing some crazy stuff
[20:27] <Quintasan> :P
[20:27] <Quintasan> apachelogger: knowledge about pointers to functions
[20:27] <Quintasan> I forgot to mention that
[20:27] <Quintasan> :P
[20:27] <apachelogger> hm
[20:27] <apachelogger> interesting
[20:28] <apachelogger> Quintasan: does the C book also say that
[20:28] <apachelogger> because then I srsly doubt the srslyness of the author :P
[20:28] <Quintasan> apachelogger: dunno, too lazy to search for pdf on my hdd now
[20:28] <Quintasan> :P
[20:29] <apachelogger> one can implement pretty neat error handlers in C using pointers to functions
[20:35] <jjesse> hrmm install most being running in the background
[20:43] <Quintasan> fcks, dolphin segfaults here really often when tagging
[20:48] <apachelogger> hm
[20:48] <apachelogger> I am not sure why but folderview refuses to show desktop:/ right after setup
[20:49] <apachelogger> tried all tricks the api got :S
[20:51] <apachelogger> possibly a bug in folderview
[20:52] <apachelogger> as i see it the config change should be applied at script exit or at least when reloadConfig() gets called on that widget
[20:52] <apachelogger> but neither applies
[20:56] <Quintasan> apachelogger: does dolphing segfaults so often while tagging for you too or its just me?
[20:56] <apachelogger> I do not do tagging :P
[20:57] <apachelogger> IMHO that is against the purpose of a semantic desktop :P
[20:57] <Quintasan> apachelogger: try then pls :P
[20:58] <apachelogger> no crashery on lucid
[20:59] <Quintasan> hmm
[20:59] <Quintasan> hell yeah 570mb of dbg libs
[20:59] <Quintasan> :S
[20:59] <apachelogger> lzma!!!!!
[21:01] <Quintasan> apachelogger: ya best be trollin, I bet its going to be ages before we use lzma for kde things
[21:01] <apachelogger> we do?
[21:01] <apachelogger> or rather we did
[21:01] <Quintasan> why we are not do so now?
[21:02] <apachelogger> and will do, asap as someone adds the appropriate stuff to the dh7 magic
[21:03] <apachelogger> oh
[21:03] <apachelogger> cool
[21:03] <apachelogger> upstream calls it kdebase, the source package is called kdebase, the meta package is called kdebase-apps
[21:03] <apachelogger> makes sense
[21:04] <Quintasan> aint it normal in our case?
[21:04] <Quintasan> :D
[21:05] <apachelogger> well
[21:05] <apachelogger> quite frankly such shit annoys me shitless
[21:05] <apachelogger> apt-get source kdebase
[21:05] <apachelogger> oha pulls kde-meta
[21:05] <apachelogger> so then you are left wondering
[21:06] <Quintasan> oh updates, maybe dolphin will stop crashing
[21:14] <Lure> Any concern if I upload digikam 1.1 w/ Nepomuk support also to backports PPA (KDE 4.4 for Karmic)? People are asking me for digikam with Nepomuk support...
[21:16]  * Lure is not sure, since 1.1 is not in official backports yet
[21:17] <Quintasan> Lure: maybe rename the package to digikam-nepomuk and upload, if it breaks something then users wont automatically update to it :P
[21:17] <Quintasan> though it's a dirty workaround :P
[21:17] <Lure> Quintasan: it is optional functionality and off by default
[21:18] <Lure> Quintasan: current package just did not build with nepomuk...
[21:18] <Quintasan> Lure: oh well, I'm up for testing anyways, I think we can ask apachelogger or Riddell
[21:20] <apachelogger> Lure: push it to beta-backports if no one complains within the next couple of days we should be fine ;)
[21:20] <Lure> apachelogger: ok, will do that first and ask some of requestors to test it
[21:21] <apachelogger> sounds good
[21:21]  * apachelogger is wondering what one needs to do to get that freaking folderview to redraw itself
[21:23] <Lure> apachelogger: but beta-backports do not have kde 4.4 and virtuoso-nepomuk, so not sure it is good base at all
[21:24] <apachelogger> staging shoudl still have 4.4 I suppose
[21:25] <Lure> apachelogger: correct, will use that
[21:49] <dhillon-v10> apachelogger: have you tried building maximus in lucid, pbuilder gives me errors and I just realize that after finishing a diff for a merge
[21:50] <dhillon-v10> apachelogger: fixed it, sudo pbuilder --clean ;)
[21:53] <apachelogger> jussi01: could take a bit to fix that
[22:01] <dhillon-v10> apachelogger: need some help, pbuilder is acting strange again, while downloading some packages it says 404 address not found, why is that??
[22:02] <dhillon-v10> apachelogger: precisely something like this: Err http://us.archive.ubuntu.com lucid/main libdbus-1-dev 1.2.16-2ubuntu2        404  Not Found [IP: 91.189.88.46 80]
[22:02] <apachelogger> sudo pbuilder update
[22:02] <apachelogger> I would suppose your apt cache is out of date
[22:02] <apachelogger> dhillon-v10: also check out the pbuilder hooks
[22:03] <apachelogger> I think there is a hook that runs apt-get update before doing anything else
[22:03] <apachelogger> https://code.edge.launchpad.net/~kubuntu-members/pbuilder/pbuilder-hooks
[22:45] <shtylman> http://arstechnica.com/open-source/reviews/2010/02/hands-on-semantic-desktop-starts-to-show-in-kde-sc-44.ars?utm_source=rss&utm_medium=rss&utm_campaign=rss
[22:46] <shtylman> nice shoutout to kubuntu ^
[22:46] <neversfelde> apachelogger: thanks
[23:14] <Riddell> apachelogger: what's hasBattery?
[23:18] <Riddell> Lure: digikam 1.1 should be ok in backports
[23:18] <Riddell> as long as its tested first
[23:23] <Riddell> shtylman: we tried to install lucid on an eeePC tonight at the KDE 4.4 release party, we have to fix that thing for small resolutions