[02:33] <ScottK> debfx: I don't think it should.
[04:32] <vikapi> any1 has issue with rekonq..for me it jus stops responding quite often..i ve to restart the app again..
[04:33] <valorie> vikapi: this isn't a support channel
[04:33] <valorie> I'll help you in #kubuntu
[04:33] <vikapi> valorie,i understand.i did a post in #kubuntu but noone responded.. 
[04:34] <valorie> fine, but this chan isn't for support
[04:49] <shadeslayer> Morning :)
[07:15] <debfx> ScottK: yes, question is how do we make it stop
[07:16] <debfx> ScottK: is python 2.6 going to be dropped from the archive this cycle?
[08:29] <bambee> morning
[09:05] <yofel> moin o/
[10:16] <apachelogger> emit yawn(LionYawn);
[10:16] <shadeslayer> morning apachelogger
[10:16] <apachelogger> aloha
[10:17] <apachelogger> senior yofel!
[10:17] <shadeslayer> CSMA/CD is better :P
[10:17] <apachelogger> dunno what this is
[10:17] <apachelogger> sounds naughty
[10:17] <apachelogger> stop talking about it
[10:17] <shadeslayer> apachelogger: seems everyone passed mid term
[10:18] <apachelogger> http://www.youtube.com/watch?v=wj768KO7IoQ
[10:29] <shadeslayer> yofel: i don't thinkusr/lib/kde4/ktexteditor_* belongs to katepart
[10:30] <yofel> well, I'm not sure, they were in kdelibs5-plugin before, so I assume they are related at least (maybe used by katepart)
[10:30] <yofel> *kdelibs5-plugins
[10:30] <shadeslayer> i think katepart should suggest/recommend kate-plugins
[10:32] <shadeslayer> the question is, does katepart need these libs or are they optional
[10:35] <yofel> not sure either, it at least doesn't seem to be directly linked to them
[10:36] <shadeslayer> well, i'm also not sure if we should split katepart
[10:37] <apachelogger> random thought: ask upstream?
[10:37] <yofel> uh, why should kile for example require kate being installed?
[10:37] <yofel> it uses katepart, not kate
[10:38] <yofel> also, I don't want to make kdelibs5-plugins depend on kate
[10:41] <shadeslayer> won't katepart dep on kate?
[10:41] <shadeslayer> or are kparts standalone?
[10:41] <shadeslayer> apachelogger: ^^
[10:41] <yofel> the kpart was in kdelibs before, so why would you start thinking it needs kate o.O?
[10:41] <apachelogger> ask upstream
[10:42] <apachelogger> you can implement it in all sorts of ways
[10:42] <apachelogger> it certainly does not depend on a kapplication
[10:42] <yofel> kate certainly needs the kpart, not the other way around
[10:42] <bambee> knotify really needs fixing... 
[10:42] <bambee> 23336 bambi     20   0 5296m 4.5g  17m R  100 77.2   6:37.29 knotify4 
[10:42] <yofel> bambee: find out what's broken, no memleak here
[10:42] <shadeslayer> alright that in case
[10:43] <bambee> 77.2 => memory
[10:43] <shadeslayer> uh
[10:43] <apachelogger> bambee: what memory
[10:43] <shadeslayer> *i'll split it
[10:43] <yofel> apachelogger: %
[10:43] <bambee> apachelogger: knotify uses 77.2% of the system memory here
[10:43] <apachelogger> ah
[10:43] <yofel> but 4.5 GB RES is...
[10:43] <bambee> my system swaps all the time
[10:44] <yofel> get yourself an SSD then you won't notice it that much at least ^^
[10:45] <bambee> a SSD is faster but still slower than memory :)
[10:45] <yofel> true, but at least the system stays usable
[10:45] <bambee> it's also expensive :p
[10:47] <shadeslayer> ok, from the katepart project page, usr/lib/kde4/ktexteditor_* should go into katepart
[10:47] <shadeslayer> "KatePart is a fast and featurerich text editor component with many advanced features. It implements the KTextEditor interfaces, a common interface collection for text editor components in KDE, allowing it to be selected as the editor in applications that lets the user chose from different implementations, as well as it can use KTextEditor plug-ins.
[10:47] <shadeslayer> "
[11:53] <debfx> ScottK: kate, kdegraphics-mobipocket and svgpart are in New
[12:49] <debfx> oh kubuntu_12_kubuntu_homepage.diff is basically empty
[12:49] <debfx> patch quality++
[12:59] <bambee> debfx: this patch is from kde-workspace, right?
[12:59] <debfx> bambee: yes
[12:59] <bambee> it's empty, really? 
[12:59]  * bambee blames quilt
[13:00] <debfx> I've fixed the patch now
[13:03] <debfx> quilt is imho a horrible tool to use
[13:04] <debfx> I usually just do quilt pop -a, edit the patches and let debuild apply them again
[13:06] <yofel> quilt is fine IMO, but that dpkg-source auto-applies the patches is annoying indeed. Esp. since it breaks many other tools (m-o-m being the most annoying perhaps)
[13:32] <karmo> is it feature or bug that i cannot go back in kmenu with that long "<" button on the right side (button doesn't exist anymore)?
[13:32] <karmo> left side*
[13:35] <debfx> karmo: seems to be a feature but I also miss that button
[14:45] <apachelogger> karmo, debfx: breadcrumb nagivation
[14:50] <debfx> apachelogger: which requires much more aiming and is less obvious
[15:16] <mfraz74> what are the plans for Amarok in 11.10 and 11.04 PPAs?
[16:31] <apachelogger> debfx: and usability experts have been asking for it for years
[18:55] <yofel> apachelogger: http://paste.kde.org/97651 Either he didn't get the problem or they don't care :/
[19:02] <apachelogger> I am not sure, but I think what rdieter was trying to say is that it is mess in general
[19:02] <apachelogger> rdieter: also, there are git repos which have a kdegraphics- prefix
[19:03] <apachelogger> that said the modules as they were are still existing, so I personally do not see a reason why generic repos should be packed into a tar with module prefix
[23:34] <valorie> brrrr, I just realized that updates broke my headphones jack again
[23:34] <valorie> were scheduled updates this last week or so including a kernel update that I didn't notice?