[00:49] <valorie>  apachelogger: I love Austria! http://www.bbc.co.uk/news/world-europe-14135523
[08:16] <bambee> morning
[08:17] <shadeslayer> o/
[08:17] <shadeslayer> yofel: i have everything worked out except for the description :P
[08:17] <shadeslayer> symbols are here http://pastebin.com/raw.php?i=yy1VWeee and http://pastebin.com/raw.php?i=NzvNgxV2
[08:41] <yofel> morning
[08:44] <yofel> fun, kdelibs building for 9h now, 72%
[09:26] <HorusHorrendus> apachelogger: amarok (newest git) has problems building under current 11.10
[09:26] <HorusHorrendus> http://paste.kde.org/96205/
[09:26] <HorusHorrendus> I think it could have to do with libgcrypt.so moving to /lib from /usr/lib
[09:26] <HorusHorrendus> cmake seems to find libgcrypt correctly but the -lgcrypt doesn't find it
[09:36] <Quintasan> yofel: Do we have kdelibs-mobile?
[09:37] <yofel> not that I know of
[09:37]  * yofel tries to get ccache and icecc working again in pbuilder
[09:37] <yofel> it's like the initial run of dpkg-buildpackage sets it's own PATH
[09:37] <yofel> once you drop to shell they work fine
[10:03] <apachelogger> yofel: it might just b executed from the wrong envrionment
[10:04] <yofel> could be, what irritates me is that an A99env hook prints PATH=/usr/lib/ccache:/usr/lib/icecc/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
[10:04] <yofel> while cmake sees PATH: /usr/share/pkg-kde-tools/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
[10:05] <yofel> which doesn't even have the pbuilder base path
[10:06] <apachelogger> report a bug
[10:06] <apachelogger> ah
[10:06] <apachelogger> hold on
[10:06] <apachelogger> yofel: how do you export the path?
[10:06] <apachelogger> or where
[10:06] <apachelogger> or when
[10:06] <apachelogger> actually all of them :P
[10:07] <yofel> I export it in pbuilderrc
[10:08] <yofel> just reading pbuilder scripts
[10:08] <apachelogger> grep them for PATH ^^
[10:08] <yofel> good idea
[10:08] <yofel> only gives pbuilder-checkparams:    export PATH="/usr/lib/ccache:$PATH" :/
[10:09] <yofel> which obviously works 
[10:14]  * yofel adds some debugging output
[10:27] <yofel> I think it fails in the way pbuilder calls the build:
[10:27] <yofel> echo "cd tmp/buildd/*/ && dpkg-buildpackage -us -uc  -j6 -rfakeroot" | chroot /var/cache/pbuilder/build//4560 env LOGNAME=pbuilder su -p pbuilder
[10:32] <yofel> or not o.O
[10:41] <yofel> helps to search the debian BTS - debian bug 606687
[10:56] <shadeslayer> apachelogger: yofel need descriptions for libkateineterfaces4 and libktexteditorcodesnippetscore0.
[10:57] <apachelogger> lolwut?
[10:58] <shadeslayer> apachelogger: public libs, need to split out of kate
[11:01] <yofel> like I know what those do
[11:03] <shadeslayer> i have no idea myself
[11:05] <apachelogger> so read?
[11:08] <yofel> want me to put patched pbuilder and icecc into ninjas? This is pretty much unfunctional otherwise
[11:09] <apachelogger> sure whatever why not
[11:12] <shadeslayer> The Kate application interfaces provide a better integration into the app like tool views. 
[11:12] <shadeslayer> doxygen++
[11:13] <shadeslayer> This library contains the code used by kate plugins that provide a better  integration into the app like tool views
[11:14] <shadeslayer> good?
[11:14] <HorusHorrendus> apachelogger: did you see my libgcrypt problem?
[11:15] <yofel> shadeslayer: sounds like it does something, so good ^^
[11:17] <shadeslayer> O_O
[11:17] <shadeslayer> libktexteditorcodesnippetscore0 is actually under kate/plugins
[11:18] <shadeslayer> should i move it to kate-plugins?
[11:18] <yofel> what do you mean? /usr/lib/libktexteditor_codesnippets_core.so.0
[11:19] <apachelogger> HorusHorrendus: rm -rf build 
[11:19] <shadeslayer> well yes, but in the source tarball its kate-4.6.90/kate/plugins/snippets_tng/lib/
[11:21] <HorusHorrendus> apachelogger: trust me ... I tried that
[11:21] <HorusHorrendus> and many other things
[11:21] <HorusHorrendus> checked if libgcrypt is installed
[11:21] <HorusHorrendus> we also checked out a new FindLibgrcrpyt.cmake
[11:21] <yofel> shadeslayer: then ask them why the hell they install that in /usr/lib
[11:22] <shadeslayer> yeah, emailing the author
[11:23] <apachelogger> HorusHorrendus: report a bug I guess
[11:23] <HorusHorrendus> for libgcrypt?
[11:24] <apachelogger> whatever linker you are using
[11:24] <HorusHorrendus> gold I think ...
[12:32] <apachelogger> bug 662433
[12:32] <apachelogger> didnt we like have that feature?
[12:33] <apachelogger> y u loose my features
[12:33] <apachelogger> yofel: y u no blog?
[12:35] <yofel> I'll spend most of today studying after wasting time on pbuilder, I'll think about it
[12:42] <apachelogger> yofel: ok, then I'll do it :P
[13:49] <dpm> hey apachelogger, there are quite a lot of kde templates in the imports queue, and I'm wondering what to do with them. You said upstream had changed quite a lot of things wrt the l10n packages. Could you give me an overview of some of the changes so I know how I should approve or move around the templates in LP?
[14:11] <debfx> shadeslayer: what's the ETA for the kate package?
[14:11] <shadeslayer> debfx: i've asked upstream if libktexteditorcodesnippetscore0 is indeed a public lib and whether or not to ship it in its own package
[14:12] <shadeslayer> because libktexteditorcodesnippetscore0 is actually a part of kate plugins
[14:14] <shadeslayer> apart from that i have everything ready ( well except for a description for libktexteditorcodesnippetscore0 )
[14:16] <debfx> shadeslayer: maybe an external plugin also uses that library
[14:17] <debfx> if not we could just remove the header files from kate-dev and move the lib to kate-plugins
[14:17] <shadeslayer> debfx: i leave it to your discretion, if you want, i have everything ready to go
[14:25] <debfx> shadeslayer: ok, I'll do that. could you push your changes?
[14:26] <shadeslayer> debfx: sure, the only thing left is a description, lemme finish that up and then i'll push it :)
[14:27] <shadeslayer> debfx: i have a question about shlibs
[14:27] <debfx> shadeslayer: don't worry about libktexteditorcodesnippetscore0, I'll move it to kate-plugins for now
[14:27] <shadeslayer> alright
[14:38] <apachelogger> dpm: if only I knew
[14:38] <apachelogger> so
[14:39] <apachelogger> dpm: kdebase is now kde-baseapps, kdebase-runtime is now kde-runtime, kdebase-workspace is now kde-workspace
[14:39] <apachelogger> templates that formerly all came out of the kdegraphics source are now distributed across multiple source packages, though the template name should likely ahve changed the same
[14:40] <apachelogger> those include libksane, libkexiv2, libkdcraw, libkipi, ksaneplugin, kolourpaint, ksnapshot, gwenview, kruler, kcolorchoose, kgamma, kamera and okular
[14:40] <apachelogger> kate ealier was part of the kdesdk source, is now an independent source
[14:41] <apachelogger> konsole ealier was part of the kdebase source, is now an independent source too
[14:41] <apachelogger> kdeedu, like degraphics was split into multiple sources
[14:41] <apachelogger> blinken, cantor, kalgebra, kalzium, kanagram, kbruch, kgeography, khangman, kig, kiten, klettres, kmplot, kstars, ktouch, kturtle kwordquiz, libkdeedu, marble, parley, rocs and step
[14:42] <apachelogger> dpm: any new templates that are not covered by those changes need specific investigation I suppose
[14:43] <dpm> apachelogger, ok, that's really helpful already, so I've got something to start with. Thanks! :)
[14:43] <apachelogger> yw
[14:48] <CIA-52> [lp:~kubuntu-packagers/kubuntu-packaging/kate] Rohan Garg * 20 * debian/ (6 files) * Move arch indep files from kate to kate-data
[14:49] <shadeslayer> debfx: ^^
[14:49] <shadeslayer> please review and kick me for my mistakes :)
[14:55] <apachelogger> who is in 4.7?
[14:56] <shadeslayer> apachelogger: you mean the packaged 4.7?
[14:56] <shadeslayer> or does Neon count? :P
[14:56] <apachelogger> anything that looks like 4.7
[14:56] <apachelogger> I need a snazzy screenshot
[14:57] <shadeslayer> anything in particular?
[14:59] <apachelogger> something snazzy
[15:00] <shadeslayer> sheytan is probably your guy in that case
[15:00] <apachelogger> why?
[15:00] <shadeslayer> i have a very boring desktop http://i.imgur.com/zO5Tc.jpg
[15:00] <apachelogger> he is not running 4.7
[15:00] <shadeslayer> apachelogger: iirc he has neon as well
[15:00] <apachelogger> oh good lord
[15:00]  * apachelogger reports a bug
[15:00] <shadeslayer> ??
[15:06] <apachelogger> shadeslayer: plz fix
[15:06] <shadeslayer> hahaha
[15:09] <apachelogger> that is no fun business at all
[15:16] <karmo> Hi, do somebody know when the Kate will be updated to 3.7 RC1? At the moment it just crashes if I try to run it because KDE is 4.7 RC1 and Kate is still old version.
[15:17] <apachelogger> karmo: give shadeslayer a beating
[15:17] <apachelogger> he is holding it back
[15:18] <shadeslayer> hey i pushed it to bzr, debfx is (hopefully) reviewing it
[15:18]  * yofel needs a break
[15:22] <karmo> ok:) i really miss my favorite editor
[15:23] <shadeslayer> use emacs :P
[15:24] <yofel> nah, vim in yakuake
[15:25] <yofel> sooo... when are we wrapping up rc1? gwenview is stuck, I'm not sure how to split mobipocket, neither is it important, and smoke still has no sane copyright upstream
[15:26] <yofel> upload kate and kstars and move to rc2?
[15:26] <shadeslayer> perlkde
[15:26] <shadeslayer> thats left too iirc
[15:26] <karmo> what about networkmanager-kde? it doesn't work for wireless networks and i'm using gnome applet to connect wifi :)
[15:26] <yofel> shadeslayer: I can do perl in rc2 too...
[15:26] <shadeslayer> karmo: broken due to new networkmanager backend iirc
[15:26] <yofel> if we postpone this any longer we might as well skip rc2 and wait for final to come out
[15:27] <yofel> karmo: the plasma widget? works fine for me in oneiric
[15:27] <yofel> (it's from the nm-0.9 branch)
[15:28] <shadeslayer> i'm a bit busy for the next couple of days
[15:28] <shadeslayer> won't be able to help until next week
[15:28] <shadeslayer> apachelogger: can you bring your N900 to DS?
[15:29] <shadeslayer> i want to test a PIM sync over a local network
[15:33] <yofel> hm, if mobipocket is too generic, how about okular-plugin-mobipocket and strigi-plugin-mobipocket then?
[15:36] <apachelogger> shadeslayer: any other phones I should bring?
[15:37] <apachelogger> yofel: kdegraphics-plugin-mobipocket
[15:37] <apachelogger> eh
[15:37] <apachelogger> kdegraphics-mobipocket
[15:38] <yofel> hm, if that's enought for scott then perfect
[15:38] <yofel> -t
[15:47] <CIA-52> [lp:~kubuntu-packagers/kubuntu-packaging/mobipocket] Philip Muškovac * 10 * debian/control rename into kdegraphics-mobipocket and run wrap-and-sort
[15:47] <yofel> I made it enhance okular too
[15:49] <yofel> apachelogger: can you look at it later? (but today if possible)
[15:49] <yofel> and someone please look at kstars
[15:56] <shadeslayer> i'll look at kstars
[15:57] <yofel> I fixed some things, so should be ready for upload (except for indi being too old)
[15:59] <apachelogger> JontheEchidna: bug 810529
[15:59] <apachelogger> JontheEchidna: I think those random bug triagers get all smartass on me
[15:59] <yofel> LOL
[16:00] <shadeslayer> :P
[16:00] <yofel> stop mis-using launchpad for personal differences :P
[16:00] <shadeslayer> Riddell: you have libindi 0.7.2 in your PPA
[16:00] <shadeslayer> yofel: tell that to apachelogger
[16:00] <tsimpson> QML session starting in #ubuntu-classroom now (btw)
[16:00] <shadeslayer> ^^ i need that
[16:00]  * shadeslayer joins
[16:01] <yofel> shadeslayer: we need indi 0.8.0
[16:01] <shadeslayer> yofel: yeah, packaging that
[16:01] <yofel> k
[16:01] <Riddell> indi is a mess to package
[16:02] <Riddell> be careful with the plugins, they don't all have source or get released
[16:04] <shadeslayer> fun
[16:04] <shadeslayer> i just need the lib itself i think
[16:05] <shadeslayer> weird how debian does not have the package
[16:09] <Riddell> well you might just need the lib to compile against, but the lib won't do anything unless it has working plugins
[16:10] <apachelogger> akonadi
[16:10] <apachelogger> yofel
[16:10] <apachelogger> ppa/bzr
[16:10] <apachelogger> NEEDS UPLOAD
[16:10] <apachelogger> yofel: didnt I upload akonadi?
[16:10] <apachelogger> !info akonadi oneiric
[16:10] <apachelogger> fun :D
[16:10] <apachelogger> !info akonadi-server oneiric
[16:10] <yofel> you uploaded 1.5.80, ppa has 1.6.0
[16:10] <apachelogger> oh
[16:10] <apachelogger> bzr had .80
[16:10] <yofel> uh...
[16:11]  * apachelogger does not release from ppa
[16:11] <shadeslayer> Riddell: ah, are the plugins from your ppa any good?
[16:11] <yofel> apachelogger: refresh bzr?
[16:11] <apachelogger> well
[16:11] <apachelogger> dont have time
[16:11]  * apachelogger is writing blog post
[16:11] <yofel> well, not that important either
[16:11] <yofel> write the post
[16:12] <karmo> yofel: where did you get working networkmanager for kde in oneiric?
[16:13] <yofel> archive?
[16:13] <Riddell> shadeslayer: hard to tell, I'll forward you the discussion I had with upstream last I looked
[16:13] <shadeslayer> sure
[16:13] <yofel> !info plasma-widget-networkmanagement | karmo
[16:13] <yofel> bah
[16:14] <yofel> !info plasma-widget-networkmanagement oneiric | karmo
[16:14] <yofel> as you see from the version, that's for nm09
[16:15] <shadeslayer> hmm
[16:20] <shadeslayer> Riddell: http://sourceforge.net/projects/indi/files/indilib/0.8/ just has the lib
[16:20] <Riddell> shadeslayer: right, upstream isn't very good at releasing plugins
[16:20] <CIA-52> [lp:~kubuntu-packagers/kubuntu-packaging/kdelibs] Philip Muškovac * 364 * debian/ (6 files) * New upstream release candidate
[16:21] <shadeslayer> so we just use the older ones you packaged?
[16:22] <yofel> then you'll have to patch the cmake check, which I doubt is the right thing
[16:29] <shadeslayer> does sound nasty
[16:29] <shadeslayer> but i managed to build libindi 
[16:34]  * yofel trys to get perlqt done
[16:34] <yofel> *tries
[16:35]  * debfx wonders if we should put katepart into an own package since it was part of kdelibs5-plugins
[16:40] <shadeslayer> wasn't katepart in its own package?
[16:40] <shadeslayer> iirc it was in libkatepartinterfaces4
[16:41] <yofel> nope, it's in kate
[16:42] <debfx> shadeslayer: that's just the library katepart uses
[16:43] <shadeslayer> oh derp
[17:02] <apachelogger> I need saxy screenshot of the 4.7 or I will start waving my fist again!
[17:02] <apachelogger> also I need someone to read blog post
[17:02] <apachelogger> Nightrose: honey :) :) :)
[17:03] <apachelogger> ah
[17:03] <apachelogger> I know
[17:03] <apachelogger> the lazy ol' yofel :P
[17:04] <apachelogger> yofel: you haz mail
[17:04]  * apachelogger leaves to play some golf
[18:02] <shadeslayer> yofel: http://i.imgur.com/qp6kz.png << \o/
[18:02] <shadeslayer> i can finally haz memo sync 
[18:03] <Quintasan> shadeslayer: Can you take a look at https://bugs.kde.org/show_bug.cgi?id=235020 ?
[18:04]  * apachelogger beats shadeslayer to make a proper screenshot
[18:04] <shadeslayer> apachelogger: whats a proper screenshot? 
[18:04]  * Quintasan can't reproduce that while user in #ubuntu-pl gets this very often
[18:04] <apachelogger> one that does not contain unintersting plunder and uses a proper wallpaper
[18:06] <apachelogger> Quintasan: why dont you investigate?
[18:06] <shadeslayer> ^^ yes
[18:06] <Quintasan> apachelogger: Since I don't get a shit what's going on in those backtraces nor I have coding skillz?
[18:06] <shadeslayer> debug info is pretty good
[18:07] <apachelogger> Quintasan: but wouldnt it be because of that a perfect learning opportunity?
[18:07] <apachelogger> shadeslayer: no it is not
[18:07] <Quintasan> apachelogger: Learning what?
[18:07] <apachelogger> whoever wrote kcharselect did not know about the use of asserts clearly
[18:07] <shadeslayer> apachelogger: whut
[18:07] <apachelogger> Quintasan: codingz, debugginz, shitz
[18:08] <apachelogger> shadeslayer: the debug info is crapz or the bug would be fixed already
[18:08] <shadeslayer> apachelogger: how is that? you can clearly see where its crashing, you get the line number and everything
[18:09] <apachelogger> that does not make it good debug info as you dunno why shit goes wrong there
[18:09]  * Quintasan has no idea how to read that magic and even less ideas how to fix that
[18:11] <apachelogger> FWIW I cannot reproduce it either
[18:12] <shadeslayer> ahh
[18:12] <Quintasan> Nor can I
[18:12] <shadeslayer> apachelogger: lol @ comment 10
[18:13] <shadeslayer> apachelogger: the model index is out of range which is why it crashes?
[18:15] <apachelogger> *shrug*
[18:15] <apachelogger> shadeslayer: does that knowledge help?
[18:16] <shadeslayer> i'm just speculating
[18:17] <apachelogger> well, usually it is that kind of thing with models
[18:17] <apachelogger> which is why one should be using plenty of asserts
[18:18] <shadeslayer> hehehe
[18:21] <apachelogger> well
[18:21] <apachelogger> shadeslayer: I find the code there a bit weird
[18:21] <shadeslayer> i haven't read the code, thats all i could infer from the backtrace
[18:22] <apachelogger> what type is htat anyway
[18:22] <apachelogger> ah
[18:22]  * apachelogger hates reading code in a webz browsa
[18:23] <shadeslayer> it crashes at a ...brace ? 0.o
[18:24] <apachelogger> what
[18:24] <apachelogger> no
[18:24] <apachelogger> silly shadeslayer
[18:24] <apachelogger>     QChar c = m_chars[pos];
[18:24] <apachelogger> at least the most recent bracktrace
[18:24] <shadeslayer> i was looking at the original report
[18:25] <shadeslayer> ah yes, 
[18:25] <apachelogger> chances are they are different issues
[18:25] <apachelogger> in my experience any bug that was thought to be fixed once but was reopened is representing at least 2 different issues
[18:25] <apachelogger> more likely >2
[18:26] <apachelogger> phonon xine is a good example for that :P
[18:26] <apachelogger> then again it is shitty code and crashes all the time and everywhere, even without solar flares
[18:27] <apachelogger> now what is interesting about that most recent crash in kcharselect is that m_chars is a qlist
[18:27] <apachelogger> now as usual accessing a qlist with the [] operator is a bit of a dangerous thing because the index *must* be valid
[18:28] <apachelogger> to help comes line 680
[18:28] <apachelogger>     if (pos >= m_chars.size() || index.row() < 0 || index.column() < 0) {
[18:28] <apachelogger> inside only returns can happen
[18:28] <apachelogger> now the constraint for a valid index is 0 <= i < size IIRC
[18:29] <shadeslayer> hahaha
[18:29] <apachelogger> sup?
[18:30] <apachelogger> anyhow, that pos >= m_chars.size() should ensure valid index
[18:30] <apachelogger> which leaves 2 options
[18:31] <apachelogger> a) pos exceeds int range and goes int -int which would of course then result in pos < size BUT pos < 0, which doesnt meet the requirement for valid index
[18:31] <apachelogger> looking at the calcuation for pos
[18:31] <apachelogger>     int pos = m_columns * (index.row()) + index.column();
[18:32] <apachelogger> I'd say that is a possibility as result from brekage elsewhere
[18:32] <Quintasan> Elsewhere being?
[18:32] <apachelogger> b) the qchar at m_chars[pos] is kaput, but since it is not a list of qchar* I find it unlikely
[18:33] <apachelogger>     QChar c = m_chars[pos];
[18:33] <apachelogger> that would at least result in a call to the assignment operator
[18:33] <apachelogger> and there it would crash
[18:33] <apachelogger> so, putting the evidance together....
[18:33] <apachelogger> we have an if that checks half the valid index constraint
[18:34] <apachelogger> we have an index operator access on qlist
[18:34] <apachelogger> and we have a crash in ::data() even though the offending line should result in a deeper stack in terms of QChar copy/assignment
[18:35] <apachelogger> but oh, we are not there yet it seems
[18:36] <apachelogger> inline T &QList<T>::operator[](int i)
[18:36] <apachelogger> { Q_ASSERT_X(i >= 0 && i < p.size(), "QList<T>::operator[]", "index out of range");
[18:36] <apachelogger>   detach(); return reinterpret_cast<Node *>(p.at(i))->t(); 
[18:37] <apachelogger> that is the [] operator of qlist
[18:37] <apachelogger> and looking at it I wonder
[18:37] <apachelogger> if it were scenario a) as presented earlier
[18:37] <apachelogger> why does the stack not contain the assert call?
[18:38] <apachelogger> usually if you assert in a kapp the stack from assert position to what happens as part of an assert (qwarning and whatnot) should appear in the stack trace
[18:38] <apachelogger> but it is not in this case
[18:38] <apachelogger> however, perhaps their distros are built without debug in Qt
[18:38] <apachelogger> in which case the assert would not be fatal
[18:39] <apachelogger> and here comes Quintasan in
[18:39] <apachelogger> Quintasan: you said ubuntu users have seen that crash?
[18:39] <apachelogger> did they show you a backtrace? did they report a bug?
[18:39] <Quintasan> apachelogger: Indeed
[18:39] <Quintasan> https://bugs.kde.org/show_bug.cgi?id=235020
[18:39] <Quintasan> Comment 44
[18:39] <apachelogger> I see
[18:40] <apachelogger> shadeslayer: what do we conclude?
[18:40] <shadeslayer> users suck
[18:40] <apachelogger> and?
[18:41] <apachelogger> Quintasan: is that guy online by any chance?
[18:41] <Quintasan> apachelogger: Yes
[18:41] <shadeslayer> asserts rule ? :P
[18:41] <apachelogger> Quintasan: ok, ask him to start kcharselect form a terminal and try to trigger the crash
[18:41] <apachelogger> shadeslayer: and?
[18:42] <shadeslayer> dunno what else
[18:42] <apachelogger> ...and the code is crap and we dunno what the cause is because apachelogger eliminated a) and b) :P
[18:42] <apachelogger> unless!!!!!....!!!!#@12!
[18:42] <apachelogger> zomg
[18:42] <apachelogger> here is the thing
[18:43] <shadeslayer> hmm?
[18:43] <apachelogger> iff I do not remember correctly and asserts do not show up as part of the stack trace in drkonqi, then it could still be a)
[18:43] <Quintasan> apachelogger: 
[18:43] <Quintasan> http://wklej.to/Rrl9P
[18:43] <apachelogger> what we can say almost definitely is that it is not case b) 
[18:43] <Quintasan> nothing interesting here
[18:43] <apachelogger> it would be crashing elsewhere if it were in the assignment
[18:44] <apachelogger> Quintasan: indeed
[18:44] <apachelogger> Quintasan: gdb kcharselect
[18:44] <apachelogger> r
[18:44] <apachelogger> ...trigger crash...
[18:44] <apachelogger> thread apply all bt
[18:45] <Quintasan> thread apply all bt <-- is that gdb command?
[18:45] <apachelogger> yuz
[18:46] <apachelogger> applies the bt (backtrace) command to all threads ^^
[18:49] <Quintasan> apachelogger: http://wklej.to/hNrnH
[18:52] <Quintasan> apachelogger: Is that something more interesting?
[18:53] <apachelogger> hm
[18:53] <apachelogger> p pos
[18:54]  * apachelogger wonders if that works when the segfault already appeared ^^
[18:55] <Quintasan> apachelogger: Fanfares
[18:55] <Quintasan> $1 = -469761976
[18:55] <Quintasan> *shrug*
[18:55] <apachelogger> I win
[18:55] <apachelogger> a) right there
[18:56] <apachelogger> Quintasan: is he knowlegable enough to write a comment on the bug?
[18:56] <apachelogger> shadeslayer: ^ I get 50 bucks from you
[18:56] <Quintasan> apachelogger: Not at all, just your typical user
[18:56] <shadeslayer> apachelogger: sure, 50 INR
[18:56] <Quintasan> :DDDDD
[18:56] <apachelogger> Quintasan: ok, I'll write the findings down, tell him the thanks for helping
[18:56] <shadeslayer> thats like 1 USD
[18:56] <apachelogger> shadeslayer: more like 0.1 USD
[18:56] <apachelogger> and you call that moniez!!!!
[18:57] <shadeslayer> your math skillz are screwed up
[18:57] <apachelogger> yes
[18:57] <apachelogger> I no
[18:57] <apachelogger> I am software engineer
[18:57] <shadeslayer> google says its 1 USD :P
[18:57] <shadeslayer> 1.1 rather
[18:58] <Quintasan> apachelogger: btw. do they sell Dr. Pepper somewhere near your dwelling?
[18:59] <bambee> sweet baby jesus
[18:59] <bambee> [40146.009081] Out of memory: Kill process 28238 (knotify4) score 889 or sacrifice child
[19:00] <shadeslayer> hahah
[19:00] <bambee> swap: 700MB
[19:00] <bambee> o_O
[19:00] <bambee> WTF?
[19:00] <shadeslayer> lol .. i'm using QMap::count incorrectly it seems
[19:01] <bambee> kernel oops inside "oom" killer itself... well... I will reboot with the 2.6.38 :D
[19:01] <Quintasan> bambee: Magic
[19:01] <bambee> hehe
[19:02] <Quintasan> Out Of Magic
[19:02] <shadeslayer> heh
[19:02] <Quintasan> :P
[19:02] <apachelogger> Quintasan: ohoh
[19:02] <bambee> a good point for linux 3.0-rc7 => nouveau
[19:02] <bambee> it's very fast !
[19:02] <apachelogger> Quintasan: if at all possible it would be cool to get the output of
[19:02] <shadeslayer> Quintasan: LOL
[19:02] <apachelogger> p m_columns
[19:02] <apachelogger> p index.row()
[19:02] <apachelogger> and p index.column()
[19:02] <apachelogger> supposedly they are optimized out though at that point in the code
[19:03] <Quintasan> p m_columns - $2 = 18
[19:04] <Quintasan> p index.row() - Cannot evaluate function -- may be inlined
[19:04] <Quintasan> p index.column() - See above
[19:04] <Quintasan> apachelogger: ^
[19:04] <apachelogger> ah yeah, thx
[19:05] <Quintasan> apachelogger: I told him not to kill it yet
[19:05] <apachelogger> Quintasan: yeah, I have everything worth having :)
[19:05]  * Quintasan goes packing stuff for tomorrow's raid on the capital of Poland
[19:12] <apachelogger> Quintasan: https://bugs.kde.org/show_bug.cgi?id=235020#c46
[19:12] <apachelogger> there
[19:12] <apachelogger> now you can learnz something
[19:12] <apachelogger> Quintasan: oh you are going on a raid?
[19:12] <apachelogger> how jolly fun
[19:15] <yofel> apachelogger: lovin' the post
[19:16] <yofel> now it would be good for me to write up a post for kubuntu.org...
[19:16] <apachelogger> must be rubbish then ^^
[19:16] <apachelogger> yofel: yeah, do that, so I have something to link to :*
[19:16] <apachelogger> shadeslayer: y u no send me screenshotz?
[19:16] <yofel> right, that's what I was implying :/
[19:17] <shadeslayer> apachelogger: i did
[19:17] <shadeslayer> you filed a bug :P
[19:17] <yofel> hm, what to do re kdepim? kopy to experimental?
[19:17] <apachelogger> coz the shot is crap
 one that does not contain unintersting plunder and uses a proper wallpaper
[19:17] <apachelogger> shadeslayer: ^
[19:17] <shadeslayer> no time for that, have to figure out QMap shitz
[19:18] <apachelogger> question
[19:18] <apachelogger> oh
[19:18]  * apachelogger beats shadeslayer with a long pornon stick
[19:18] <apachelogger> what is wrong with you people :@
[19:18]  * shadeslayer gets a syncevo stick and battles it out
[19:18] <apachelogger> anyone knows why the big 11.04 banner on kubuntu.org links to download?
[19:18] <apachelogger> that seems rather odd
[19:19] <apachelogger> no one goes somewhere and simply buys stuff without first knowing what they are getting
[19:21] <bjsnider_> is anyone here using kde4/i386?
[19:22] <yofel> ... because he's writing a flash installer and wants to test whether the installer works right for kde4/i386
[19:23] <yofel> apachelogger_: and where else should a banner with 'download now' on it is supposed to link to?
[19:23] <yofel> though it's far too huge IMO
[19:24] <yofel> s/should/is/
[19:24] <kubotu> yofel: You did something wrong... Try s/you/me/ or tell me "help sed"
[19:25] <Quintasan> apachelogger_: lol @ comment #47 "D
[19:25] <Quintasan> :D
[19:26] <shadeslayer> yofel: flash installer? 0.o
[19:26] <yofel> shadeslayer: ask him
[19:27] <Quintasan> bjsnider_: Does a VirtualBox machine count?
[19:27] <apachelogger_> yofel: my point being that it should not be download now
[19:27] <shadeslayer> i'm off to bed, cya tomorrow
[19:27] <apachelogger> Quintasan: do I haz to do everything
[19:28] <Quintasan> apachelogger: Erm, I'm not following on that one
[19:28] <apachelogger> it is magic
[19:28] <apachelogger> anyhow
[19:28] <apachelogger> CAN I PRTYPLZ GET A FLIPPING SCREENSHOT OF FLIPPING 4.7 ALREADY
[19:28] <apachelogger> G
[19:29] <bjsnider_> Quintasan, absolutely
[19:29]  * yofel thinks of http://emilsedgh.info/blog/index.php?/archives/13-The-sad-state-of-our-websites..html when looking at our webpage
[19:30] <bjsnider_> Quintasan, it has web access?
[19:30] <yofel> apachelogger: give me a minute to create a new user, changing this into something snapshottable would take hours :P
[19:30] <Quintasan> bjsnider_: Sorry, it's amd64 apparently
[19:31] <Quintasan> stupid VirtualBox
[19:31] <bjsnider_> dammit
[19:31] <Quintasan> I can do a quick install now
[19:31] <bjsnider_> don't any linux users use i386 anymore? does everybody have over 4gb of ram now?
[19:33] <Quintasan_> bjsnider_: installing i386 on VM
[19:35] <yofel> apachelogger: what do you want screenshots of?
[19:36] <yofel> wow, haven't seen the default session in a while ^^
[19:38] <Quintasan> bjsnider_: Should be ready soon
[19:49] <apachelogger> yofel: anything that looks good
[19:49] <apachelogger> and use the stripes wallpaper if it isnt default anyway
[19:49] <apachelogger> dolphin or something
[19:49] <yofel> apachelogger: here's some of the default http://people.ubuntu.com/~yofel/pics/screens/
[19:49] <yofel> ah no, it wasn't
[19:49] <yofel> give me a minute
[19:49] <apachelogger> Quintasan: you are on 64bit? the other dude is on 32bit?
[19:50] <apachelogger> Quintasan: that would explain why we cannot reproduce the issue, though our int should also be 32bit, unless ubuntu gcc is all sorts of fancy
[19:50] <apachelogger> yofel: lol, they still did not fix the date thing?
[19:50] <apachelogger> funfunfun
[19:51] <apachelogger> someone deserves a whipping I guess :P
[19:52] <yofel> date?
[19:52] <yofel> oh, didn't even notice that ^^
[19:53] <yofel> odd, after logging in again the date is gone o.O
[19:54] <apachelogger> :O
[19:54] <apachelogger> funfunfun
[19:55] <yofel> apachelogger: http://people.ubuntu.com/~yofel/pics/screens/snapshot6.png
[19:56] <yofel> stripes looks somewhat plain...
[19:58] <yofel> apachelogger: snap 7 and 8 with dolphin
[19:59] <apachelogger> cheers
[19:59] <yofel> something else?
[20:00]  * yofel switches sessions again
[20:12] <apachelogger> http://apachelog.wordpress.com/2011/07/14/kubuntu-and-kde-sc-4-7-a-love-story/
[20:13] <apachelogger> and now for some http://www.youtube.com/watch?v=QH2-TGUlwu4
[20:39] <bambee> does knotify4 contain a swap bomb? (Memory: 91%)
[20:39] <bambee> o_O
[20:40] <yofel> I would call that a pretty nice memleak :P
[20:41] <bambee> I used it during a week... no problem... and this evening my system is just unusable
[20:57] <Quintasan> http://identi.ca/notice/78777602
[20:57] <Quintasan> REDENT!
[20:59] <Quintasan> apachelogger: ping
[21:08] <Quintasan> apachelogger: nvm, this will have to wait until tomorrow