[00:21] <ScottK> Quintasan: Can haz diffs for the FFes?
[00:22] <ScottK> rbelem: pong
[00:42] <jjesse> here's an interesting problem just updated my oneric vm today and after an update, rebooting and trying to login i get a white box that says "Could not start D-Bus, Can you call qdbus? and has an Okay button, after clicking the button i am prompted again with the login screen
[00:44] <yofel> jjesse: known issue, should be fixed with the next qt update, for now install qt4-dev-tools
[00:45] <jjesse> thanks yofel
[00:49] <rbelem> ScottK, could you take a look in the ffe? :-)
[01:11] <jjesse> hrmm ok last night i reported a bug i was having w/ kate and it appears to only be happening in an upgraded version of oneric and not a fresh version
[01:11] <jjesse> however i reported it on bugs.kde.org and now can't find it ;(
[01:12] <jjesse> ah found it: https://bugs.kde.org/show_bug.cgi?id=280236
[01:18] <jjesse> email about it send to the kubuntu-devel mailing list
[02:49] <ScottK> rbelem: Which?
[08:03] <bambee> morning
[09:14] <Quintasan> bambee: \o
[09:14] <Quintasan> Good morning as well
[09:14] <bambee> yo :)
[09:15] <Quintasan> ScottK: You can
[09:16] <Quintasan> ScottK: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/828159
[09:19] <Quintasan> ScottK: https://bugs.launchpad.net/ubuntu/+source/kde4libs/+bug/827286
[09:20] <Quintasan> ulmlogger: Can I merge kde-runtime-active branch?
[09:21] <Quintasan> WUT
[09:21] <Quintasan> yofel: PINGO
[09:21] <Quintasan> http://bazaar.launchpad.net/~yofel/kubuntu-packaging/kde-runtime-active-4.7/revision/223
[09:22] <Quintasan> Y U NO PATCHES?
[09:22] <ulmlogger> Quintasan: from where?
[09:22]  * yofel yawns
[09:22] <ulmlogger> Quintasan: I acked the stuff rbelem presented
[09:22] <yofel> @_@
[09:22] <ulmlogger> like 3 times or more :P
[09:22] <yofel> sry
[09:23] <Quintasan> ulmlogger: https://code.launchpad.net/~yofel/kubuntu-packaging/kde-runtime-active-4.7
[09:23] <jussi> ulmlogger: PM !!! :D
[09:23] <Quintasan> ulmlogger: I was looking at that branch but I discovered there are no patches :S
[09:23] <CIA-52> [kde-runtime] Philip Muškovac * 224 * debian/patches/ (6 files) Actually add the patches
[09:24] <Quintasan> Now I can merge and link to branch!
[09:25]  * Quintasan testbuilds
[09:26] <Quintasan> http://paste.kde.org/111259
[09:26] <Quintasan> hmmm
[09:26] <Quintasan> --with xine?
[09:26] <Quintasan> Is that some oneeyerick change?
[09:27] <yofel> sure it's oneiric since it's only there since dhmk is used
[09:29]  * Quintasan bzr-buildpackage -S
[09:29] <Quintasan> can't*
[09:30] <Quintasan> I see
[09:31] <Quintasan> TESTBUILDIN
[09:48] <Quintasan> werks
[09:53] <Quintasan> ScottK: https://bugs.launchpad.net/ubuntu/+source/kde-runtime/+bug/827283
[09:54] <Quintasan> ScottK: Then we have FFe for https://bugs.launchpad.net/ubuntu/+bug/828111
[09:54] <Quintasan> https://bugs.launchpad.net/ubuntu/+bug/512319
[09:54] <Quintasan> and https://bugs.launchpad.net/ubuntu/+source/plasma-mobile/+bug/828093
[09:54] <Quintasan> disregard 512319
[09:54] <Quintasan> bambee: file a FFe for touchegg
[09:55] <bambee> ok
[09:55] <bambee> sure
[09:55] <Quintasan> and ping ScottK with it, in bug description link to REVU package which I acke'd
[09:56] <Quintasan> ScottK: I need you to approve and upload FFe's for kde* packages so I can testbuild the rest and see if it works
[09:56] <Quintasan> If something doesn't work then we blame rbelem
[09:56]  * Quintasan goes back to cleaning 
[10:10] <rbelem> :-D
[10:10]  * rbelem pokes Quintasan 
[10:14]  * rbelem goes to work
[10:15] <bambee> Quintasan: bug 828637
[10:16] <Quintasan> What a beautiful FFe
[10:16] <Quintasan> ScottK: ^^
[10:16] <bambee> ohh... I need a review from another person normally... (It's the MOTU process...)
[10:17] <Quintasan> ulmlogger: I extend my every right to demand that you spare some time and review bambee's package http://revu.ubuntuwire.com/p/touchegg
[10:18] <Quintasan> Not much to review there, and leave an advocating comment
[10:18] <Quintasan> Unless he broke something
[10:18]  * Quintasan hands bambee Mighty Stick of ulmlogger Poking
[10:22]  * ulmlogger puts on some pants
[10:26]  * bambee pokes ulmlogger with his Mighty Stick and waits for "pants ack"
[10:27] <ulmlogger> you can already prepare your shell for fixing
[10:27] <ulmlogger> 2 seconds into the review -> first grave problem
[10:27] <bambee> really? o_O
[10:29]  * jussi steals the stick from bambee
[10:30] <yofel> bambee: this looks fooey
[10:30] <yofel>   3 Maintainer: Kubuntu Developers <kubuntu-devel@lists.ubuntu.com>
[10:30] <yofel>   4 XSBC-Original-Maintainer: Kubuntu Developers <kubuntu-devel@lists.ubuntu.com>
[10:31] <bambee> ?
[10:31] <yofel> either put yourself as original maintainer or just drop it
[10:31] <bambee> lintian displays warnings if I drop it
[10:32] <yofel> o.O
[10:32] <bambee> (I'am not sure if it's lintian, but something displays warnings)
[10:32] <bambee> let me check
[10:33] <yofel> ah, dpkg-source
[10:33]  * yofel usually ignores that
[10:34] <bambee> no it's dpkg-source
[10:34] <bambee> dpkg-source: warning: Version number suggests Ubuntu changes, but there is no XSBC-Original-Maintainer field
[10:34] <bambee> well, I ignore it
[10:35] <ulmlogger> bambee: revud
[10:35] <bambee> ulmlogger: thanks
[10:36] <bambee> "upstream tar i tar.gz not xz, do not change upstream tars for no good reason" => the original tarball does not contain the COPYING file
[10:36] <bambee> that's why I've repacked it
[10:36] <yofel> well, then you're missing a +repack in the version
[10:36] <bambee> right
[10:37] <yofel> also, run wrap-and-sort
[10:46] <jussi> ulmlogger: moar PM! :D
[11:40] <Quintasan> bambee: I didn't tell you that you need to add +repack?
[11:40] <Quintasan> silly Quintasan
[12:16] <Quintasan> bambee: Now you got a list of errors from ulmlogger and should fix them
[12:16] <Quintasan> The package should be mostly good afterwards
[12:49] <debfx> ScottK: do you have an idea why ntrack breaks kde again? bug #826969
[12:49] <debfx> or rather how we can fix that
[12:50] <ScottK> debfx: I don't.  I tested the fix that's in 014 and still had problems, which is why it wasn't included in the SRU.
[12:50] <ScottK> I'd ask asac.
[12:51] <ScottK> Presumably someone needs to figure a way to make it consistently do that and strace it or some such.
[12:52] <mfraz74> would someone here be able to help me with a compiling problem?
[13:11] <shadeslayer> mfraz74: is it related to Kubuntu development?
[13:12] <mfraz74> shadeslayer: not really I was trying out the http://developer.ubuntu.com/packaging/html/packaging-from-scratch.html and I'm stuck
[13:13] <shadeslayer> hmm ... #ubuntu-motu or #ubuntu-packaging i'd say
[13:13] <mfraz74> ok thanks
[13:17] <bambee> re
[13:18] <bambee> Quintasan: no you just said me to repack it, BUT I know that I need to add +repack... I just forgot it... silly error
[13:34] <shadeslayer> !find qrcodec.h
[13:44] <ScottK> ulmlogger, debfx, Quintasan, rbelem, etc: Looking at the kde4libs diff, I'm not super happy about the idea of adding experimental headers into kdelibs5-dev.
[13:45]  * ulmlogger complained about that
[13:45]  * ScottK is going to (again) suggest that stuff go into a new kdelibs5-experimental-dev package and ask for arguments why that's not the way we should do it.
[13:45] <ScottK> ulmlogger: ^^^?
[13:46] <ScottK> ulmlogger: Any idea where the new symbols in debian/libnepomukquery4a.symbols come from?  That seems a bit scary too.
[13:46] <ulmlogger> but everything in an experimental package
[13:46] <bambee> Quintasan: http://revu.ubuntuwire.com/p/touchegg
[13:46] <bambee> fixed
[13:47] <ulmlogger> actually, for all I care you could just create one experimental package with libs and headers inside
[13:47] <ScottK> debfx: ^^^ re the symbols - do you know?
[13:47] <ulmlogger> it is not like this thing is supposed to be used by anyone nor will it be existing for > 11.10
[13:47] <shadeslayer> ulmlogger: wait a sec, aren't the experimental libs and headers supposed to be internal ?
[13:47] <ulmlogger> ScottK: what symbols?
[13:47] <ScottK> ulmlogger: Look in the diff.
[13:47] <ulmlogger> define internal
[13:47] <ScottK> https://launchpadlibrarian.net/77504842/371_370.diff
[13:47] <ulmlogger> ScottK: where?
[13:47] <shadeslayer> not public
[13:48] <shadeslayer> not shipped in a seprate package to be precise
[13:48] <ScottK> shadeslayer: Internal to what?
[13:48] <ScottK> Can't very well build plasma-active without them can we?
[13:48] <shadeslayer> ScottK: Internal to KDE i meant
[13:48] <shadeslayer> . . .
[13:48] <ScottK> shadeslayer: Internal to KDE doesn't make any sense.
[13:48] <ulmlogger> ScottK: the new symbols come from new code
[13:48] <debfx> ScottK: I guess from a patch?
[13:48] <ScottK> Sigh.
[13:49] <shadeslayer> i don't know how to put my thoughts into a proper sentence right now
[13:49]  * shadeslayer needs coffee
[13:49] <ulmlogger> ScottK: https://git.reviewboard.kde.org/r/102112/
[13:49] <ScottK> So our experimental patch exposes new symbols that we can't guarantee will be supported?
[13:49]  * ScottK looks
[13:49]  * bambee orders a coffee for shadeslayer
[13:50] <ScottK> ulmlogger: It'd be nice if that'd get committed to the 4.7 branch too since that sounds bug fixish to me.
[13:52] <ScottK> Or not.
[13:52] <debfx> wait what, we are adding a gazillion of patches that are from the 4.7 branch?
[13:53] <debfx> are *not* from
[13:53] <shadeslayer> bambee: oh ... now i have 2 coffee cups ...
[13:54] <ScottK> That's what the FFe we are discussing is about.
[13:54] <bambee> :D
[13:54] <ScottK> So we can build the latest Active/Mobile stuff.
[13:54] <shadeslayer> why can't we put it in a PPA?
[13:54] <ScottK> Then it's rather not part of Kubuntu.
[13:55] <ulmlogger> also
[13:55] <ulmlogger> we
[13:55] <ulmlogger> rather
[13:55] <ulmlogger> need
[13:55] <ulmlogger> arm
[13:56] <ulmlogger> ppa++ for not having arms
[13:56] <shadeslayer> so, its a tradeoff between having a new product vs exposing new symbols?
[13:56] <ulmlogger> \o/ <-- obs, o <-- lunchpad
[13:56] <shadeslayer> heh
[13:56] <ulmlogger> shadeslayer: new product?
[13:56] <ulmlogger> plasma mobile is not new
[13:56] <shadeslayer> ulmlogger: Kubuntu Active
[13:56] <ulmlogger> kubuntu mobile
[13:56] <shadeslayer> are we discussing Active or Mobile?
[13:57] <shadeslayer> because i thought the patches enable you to build Active stuff
[13:59] <ulmlogger> ACTIVE IS MOBILE
[14:02] <shadeslayer> @_@
[14:03]  * Quintasan hits shadeslayer with ACTIVE sign
[14:03] <Quintasan> ScottK: Well, I'm not really happy about doing this after feature freeze :P
[14:03] <shadeslayer> there are like a bazillion names in KDE now
[14:04] <ScottK> Quintasan: Agreed the timing isn't best, but until 4.7.0 was done there really wasn't a way to do it.
[14:04] <shadeslayer> KDE Frameworks/KDE SC/Plasma Active ...
[14:14] <Quintasan> ScottK: So it would be acceptable if we'd ship this experimental stuff in a separate package, right?
[14:16] <ScottK> Quintasan: I think so.
[14:16] <Quintasan> bambee: The changelog needs to mention the cause of repack
[14:16] <ScottK> The patch that adds the symbols looks reasonably safe/maintainable.
[14:17] <ScottK> Quintasan: I would like it though if the nepomukquery patch were updated to correctly reflect the version we added it in our package rather than say 4.8 as the upstream comment does.
[14:18] <Quintasan> ulmlogger: I believe one can pass --dbg-package=touchegg-dbg directly to %
[14:18] <Quintasan> That way whole override on strip becomes useless
[14:19] <ulmlogger> yes you can
[14:19] <ulmlogger> that does not mean it is the best solution :P
[14:19] <Quintasan> In that case?
[14:19] <Quintasan> I'm wondering if we are getting any particular advantage in that case
[14:20] <bambee> less characters... inline command... I like it...
[14:20] <bambee> (we've not a lot of arguments to pass to dh, we've only two...)
[14:20] <Quintasan> bambee: Same here, I did that in other packages for no apparent reason
[14:20] <Quintasan> (override I mean)
[14:20] <Quintasan> ulmlogger: Thoughts?
[14:21] <Quintasan> bambee: There is also nice wrap-and-sort script
[14:21] <Quintasan> You can use it :)
[14:21] <bambee> wtf?
[14:21] <bambee> woo
[14:22] <Quintasan> bambee: add --dbg-package=touchegg-dbg to dh and get rid of the override
[14:22] <bambee> + the changelog
[14:22] <Quintasan> I don't think it will have any impact on THIS package
[14:22] <Quintasan> Yes
[14:23] <Quintasan> And I will advocate
[14:24] <Quintasan> ScottK: What about kde-workspace?
[14:24] <debfx> just to be clear, those patches won't be included in kdelibs 4.7 so we will have to carry them on until we remove kde4libs?
[14:24] <ScottK> The nepomukquery patch will be in 4.8.
[14:25] <ScottK> The rest is (after moving the headers and such into an experimental -dev package) in separate binaries.
[14:25] <ScottK> We can drop them if needed later.
[14:26] <debfx> I thought there will be no kdelibs 4.8
[14:26] <debfx> also some patches touc hplasma.h
[14:26] <ScottK> Hmm.
[14:27] <ScottK> The activitymanager changes in -runtime look a bit scary too.
[14:27] <ScottK> ulmlogger: This all seems rather invasive.
[14:27] <Quintasan> ScottK: Which patch is the nepomukquery one?
[14:27] <ScottK> Quintasan: https://git.reviewboard.kde.org/r/102112/
[14:28] <ScottK> That commit is in our diff.
[14:29] <Quintasan> So you want to get "\since 4.8" replaced with "since 4:4.7.0-0ubuntu3" ?
[14:29] <Quintasan> in the patch
[14:30] <ScottK> Yes.
[14:30] <Quintasan> There is only one instance of that, replacing
[14:30] <ScottK> But I don't want any of it uploaded until we've got through the whole set.
[14:31] <ScottK> Someone convince me why I shouldn't freak out about the scale of the activitymanager changes?
[14:31] <bambee> Quintasan: uploaded
[14:31] <Quintasan> bambee: Awesome
[14:32] <Quintasan> rbelem or ulmlogger may have sufficient explanations for this
[14:32] <Quintasan> ScottK: So new files from debian/kdelibs5-dev.install should land into other experimental package, is naming it kdelibs5-experimental-dev enough?
[14:32] <ScottK> Yes.  I think that's good.
[14:32] <ScottK> ulmlogger: ^^^ ?
[14:33]  * bambee blames "bzr commit" it does not open emacs anymore.... 
[14:33]  * bambee has a look at "man bzr"
[14:33] <bambee> (just in case)
[14:34] <shadeslayer> bambee: known bug/feature
[14:34] <Quintasan> feature
[14:34] <Quintasan> since vim > emacs
[14:34] <Quintasan> :P
[14:34]  * Quintasan hides
[14:34] <shadeslayer> heh :P
[14:35] <yofel> no, bzr feature
[14:36] <ScottK> Tell Riddell.  He uses emacs, so I'm sure he'd be right on top of fixing it.
[14:36] <bambee> Q_ASSERT(! vim > emacs);
[14:37] <Quintasan> ScottK: Should Depends on that experimental package be the same as kdelibs5-dev or I can just make it depend of kdelibs5-dev so it pulls everything?
[14:37] <Quintasan> s/of/on
[14:37] <ScottK> The latter is fine.
[14:38] <Quintasan> ScottK: http://paste.kde.org/111319 <-- Any other thoughts?
[14:39] <ScottK> Quintasan: It needs some kind of DO NOT USE warning in the description.
[14:40] <ScottK> Totally unstable API/ABI, may break without warning, etc.
[14:40] <yofel> Quintasan: also, IMO i should depend on the experimental lib packages so you can remove them from kdelibs5-dev
[14:40] <yofel> s/i/it/
[14:40] <kubotu> yofel meant: "Quitntasan: also, IMO i should depend on the experimental lib packages so you can remove them from kdelibs5-dev"
[14:40] <yofel> sed fail..
[14:40] <shadeslayer> lol
[14:41] <ScottK> yofel: Good point.
[14:44] <Quintasan> As far as I can see the kdelibs5-dev I merged doesnt depend on them :D
[14:44] <ScottK> Then the experimental one should pull them in.
[14:46] <Quintasan> ScottK: http://paste.kde.org/111325
[14:46] <ScottK> I'd have gone with unstable API rather than production environment.
[14:47] <ScottK> When someone uses this package and later their stuff doesn't build, I want to be able to say "Dude, did you read the package description - what did you think would happen".
[14:48] <Quintasan>  This package contains headers with unstable API and should not be used in production development ?
[14:48]  * Quintasan has no idea how to put that in words
[14:49] <Quintasan> Headers in this package provide unstable API, use at your own risk?
[14:49] <ulmlogger> USE NOT AT ALL
[14:50] <Quintasan> ScottK: ^
[14:50] <ScottK> Quintasan: As ulmlogger says.
[14:50] <yofel> don't use unless you know what you're doing?
[14:50] <ScottK> No.  Don't use.
[14:50] <yofel> k
[14:51] <Quintasan>  Headers in this package provide unstable API, do not use them.
[14:51]  * yofel would drop 'them' but otherwise ok
[14:51] <Quintasan> True
[14:51]  * ScottK is with yofel, but either way.
[14:52] <Quintasan> ScottK: The whole diff -> http://paste.kde.org/111331
[14:52] <ScottK> ulmlogger: Convince me on the activitymanager in -runtime.
[14:52] <Quintasan> ulmlogger: DO EET
[14:53] <ScottK> Could this stuff get shoved in some experimental package that's not installed normally?
[14:53] <ScottK> Quintasan: That looks good for libs.  No someone needs to sell me on runtime.
[14:53]  * Quintasan pushes
[14:55] <Quintasan> ScottK: Can you look at workspace while ulmlogger is looking for arguments? :P
[14:55] <ScottK> What bug is that?
[14:55] <Quintasan> https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/828159
[14:58] <ulmlogger> ScottK: well, yes, we could do a double build
[14:58] <ulmlogger> first without patches, second with
[14:58] <ScottK> ulmlogger: Wouldn't that be less risk?
[14:58] <ulmlogger> sure it would
[14:59] <ulmlogger> also it is a PITA to do :P
[14:59] <ScottK> The libs stuff seemed mostly isolated to new stuff.  -runtime not so much.
[14:59] <ScottK> Fortunately Quintasan is an expert now that he did the kwin-gles stuff.
[14:59] <Quintasan> FFFFFFFF
[14:59] <ulmlogger> win
[14:59]  * ulmlogger needs to shower and stuff
[15:00] <Quintasan> How do you expect the builder to know when to apply some patches and when not to?
[15:00] <Quintasan> building gles was easy since I didn't have to do any magic apart from few overrides
[15:00] <yofel> you run quilt between the builds?
[15:01] <yofel> which would probably be messy though..
[15:01] <Quintasan> !
[15:01] <Quintasan> Can we have a separate series file and pass that over to quilt during the second build?
[15:01] <yofel> you could redefine QUILT_PATCHES though maybe
[15:02] <Quintasan> or
[15:02] <yofel> that would give you a seperate series file too
[15:02] <Quintasan> more dirty
[15:02] <Quintasan> add the patches but remove them from series
[15:02] <Quintasan> do the first build
[15:03] <Quintasan> append new patch names in rules before second build
[15:03] <Quintasan> do a second build
[15:03] <Quintasan> yofel: I don't want to redefine it since we need all the previous patches too
[15:04] <yofel> well, apply patches -> redefine -> apply again
[15:04] <yofel> dpkg-source will apply the default ones anyway
[15:04] <ScottK> Quintasan: I don't understand "+Breaks: kdebase-workspace-bin (<< 4:4.5.80), kde-window-manager (= ${binary:Version})"
[15:05] <yofel> you would need to pop again between the configure and build step though I think
[15:05] <ScottK> Doesn't it break every version of kde-window-manager?
[15:05] <ScottK> Also short description should mention GLES.
[15:06] <ScottK> Same for both packages
[15:07] <ScottK> Other than that it seems OK.
[15:08] <ScottK> I approved the FFe, but please fix that stuff up.
[15:09] <ScottK> Quintasan: ^^^
[15:31] <Quintasan> ScottK: Look at the second diff
[15:31] <Quintasan> ScottK: Those packages cannot be installed at the same time
[15:31] <Quintasan> Because they provide the same files
[15:31] <ScottK> Quintasan: I get that.  Why is the breaks versioned?
[15:32] <Quintasan> It shouldn't be versioned?
[15:32] <Quintasan> Ah
[15:32] <Quintasan> Stupid question, removing
[15:32] <ScottK> Great.
[15:32] <ScottK> Quintasan: That applies to both packages (same issue)
[15:35] <Quintasan> ScottK: kde-window-manager (>= ${source:Version}) | kde-window-manager-gles (>= ${source:Version})
[15:35] <Quintasan> That's Depends on kde-workspace, is this good?
[15:35] <ScottK> That's fine.
[15:35] <Quintasan> Conflicts: kde-window-manager-gles
[15:36] <Quintasan> That's all
[15:36] <Quintasan> I'm not adding Conflicts: kde-window-manager on kde-window-manager-gles
[15:36] <Quintasan> That's pointless unless I'm misunderstanding how dpkg works
[15:36] <Quintasan> If I have installed -gles and try to install non-gles then it will conflict
[15:36] <Quintasan> if I have non-gles installed it will conflict too
[15:37] <Quintasan> right?
[15:37] <ScottK> I don't think conflicts are bi-directional like that, but I'm not sure.
[15:37]  * bambee hugs Quintasan and asks him to advocate touchegg on revu
[15:37] <bambee> :P
[15:37] <Quintasan> bambee: Urgh right, let me do kwin
[15:37] <Quintasan> ScottK: I'll add them back just to be safe
[15:38] <bambee> sure, there's no hurry
[15:38] <Quintasan> It won't hurt anyone
[15:39] <Quintasan> ScottK: http://paste.kde.org/111343
[15:39] <Quintasan> Before I commit
[15:40] <Quintasan> bambee: Advocated
[15:41] <ScottK> Quintasan: Yes.  Similar changes in the other gles binary too.
[15:42] <Quintasan> oh libkwineffects
[15:42] <Quintasan> ScottK: http://paste.kde.org/111349
[15:43] <ScottK> Looks good.
[15:43] <Quintasan> Pushing
[15:43] <ScottK> Before uploading I'd test to make sure those conflicts really do what you want.
[15:44] <bambee> Quintasan: thanks!
[15:46] <Quintasan> bambee: Now convince ScottK to approve FFe
[15:46] <Quintasan> :P
[15:47] <ScottK> What testing has the package had?
[15:48] <Quintasan> ScottK: I testbuilt and installed it. I don't have any hardware to test how it works
[15:48] <ScottK> So who does?
[15:48] <ScottK> Didn't ulmlogger score some hardware?
[15:49] <ScottK> If you can test it, I've no problem with FFe.
[15:49]  * Quintasan looks at ulmlogger
[15:49] <jussi> Has anyone tried installing from the CD/usb recently? 
[15:50] <Quintasan> jussi: One-eye-rick?
[15:50] <bambee> ScottK: actually? it's not tested yet, I've not the hardware for that
[15:50] <jussi> Quintasan: yeah
[15:50] <Quintasan> jussi: If you are talking about broken DBus then we know about that :P
[15:50] <ScottK> bambee: So find someone.
[15:50] <jussi> Quintasan: My 15th doesnt install - ubiqity doesnt start
[15:50] <ScottK> Broken dbus is fixed.
[15:50] <Quintasan> I see
[15:51] <ScottK> Sounds about right for broken dbus (time wise)
[15:51] <ulmlogger> ScottK, Quintasan: bulldog98 and I have hardware
[15:51] <ulmlogger> also I am going to do some cursing now
[15:51] <ScottK> jussi: Install from the Alpha 3 images and then upgrade.  Those work.
[15:51] <jussi> and my upgraded version doesnt even boot - hangs with a white blinking cursor
[15:52] <Quintasan> jussi: Did you try upgrading today?
[15:52] <jussi> I can make it boot via recovery, then resume and startx
[15:52] <jussi> Quintasan: no, I upgraded a few days back
[15:52] <Quintasan> As ScottK said, DBus got fix'd
[15:52] <bambee> Could someone test touchegg with the appropriated hardware please?
[15:52] <jussi> ahh, lets see
[15:53] <jussi> ooh, thats lots of upgraded stuff... let me see if it hels
[15:53] <Quintasan> bulldog98 or ulmlogger: pull-revu-sources touchegg, compile and try using that
[15:53] <Quintasan> we need that done SOON (TM)
[15:59] <Quintasan> That's sure stupid, Eject doesnt do umount before trying to eject
[16:01] <jussi> was it libqt4-dbus  that needed to be upgraded or?
[16:03] <ScottK> jussi: Read kubuntu-devel
[16:10] <jussi> ScottK: hrm... qdbus does not seem to exist (Im using archive.ubuntu.com, fully dist upgraded) ?
[16:12] <ScottK> Hmmm.
[16:12] <ScottK> jussi: What version of Qt do you have?
[16:13] <jussi> libqt4-dev is Version: 4:4.7.3-4ubuntu5
[16:13] <ScottK> You don't have the fixed one then.
[16:13] <ScottK> What you want is ubuntu6
[16:14] <ScottK> So you're in the "depending on how long your mirror takes to update" situation.
[16:14] <jussi> isnt archive.ubuntu.com the main mirror that goes first? 
[16:14] <ScottK> It is, but it's a mirror nontheless.
[16:15] <ScottK> I'd have expected it there by now, but stuff happens
[16:15] <jussi> oh look at that, apt-get updated and dist upgraded and its getting pulled in now :)
[16:16] <jussi>   libappindicator1 libboost-dev are still being held though
[16:16] <ScottK> Unrelated.
[16:16] <Quintasan> 94%
[16:16] <Quintasan> Oh wait, it's the first build
[16:16] <Quintasan> :/
[16:17] <jussi> also, anyone know what this is: W: libwmf0.2-7 is already removed. It is recommended to run defoma-app purge libwmf0.2-7.
[16:18] <Quintasan> Since it 's a warning you can ignore it :P
[16:19] <jussi> lol
[16:19]  * Quintasan hides
[16:19] <maco> ive had a simlar thing show up before
[16:19] <maco> when i ran defoma-app purge  bleh      it did some stuff and said the same thing during it
[16:19] <jussi> right, lets go see if kubuntu boots now
[16:25] <Quintasan> yofel, ScottK: Can I have a review before I merge? https://code.launchpad.net/~quintasan/kubuntu-packaging/kde-workspace/+merge/72066
[16:26] <ScottK> Quintasan: Depends/Build-depends in your changelog entry.
[16:28] <ScottK> What's Conflicts: kde-window-manager-gles (=< ${binary:Version}) ?
[16:28] <Quintasan> What the...
[16:28] <Quintasan> BRR
[16:29]  * Quintasan deletes that
[16:29] <Quintasan> I pushed wrong stuff
[16:30] <jussi> nope, still no boot :(
[16:31] <Quintasan> Can we have /var/log/Xorg.0.log?
[16:31]  * Quintasan goes playing Harvest Moon
[16:34] <jussi> Quintasan: when it doesnt boot, it doesnt get anywhere, just hangs with a white flashing cursor
[16:34] <Quintasan> Can you boot it in recovery mode?
[16:34] <jussi> yes
[16:34] <jussi> I do that, hit resume, then startx and get into kde like that
[16:34] <Quintasan> :O
[16:35] <jussi> strange thing
[16:35]  * Quintasan has no idea how to debug boot up
[16:37] <shadeslayer> kdeinit4 is consuming a entire core -.-
[16:38] <shadeslayer> jussi: yeah that has happened to me a couple of times
[16:39] <shadeslayer> some random update solved the issue for me
[16:40]  * jussi sighs. its sucky to live in a quiet world...
[16:43] <yofel> well, you could either disable splash, or set gfxplayload to text to get actual boot messages (and disable 'quiet'). If you want even more verbose boot add '--verbose' to the kernel command line
[16:48] <ulmlogger> Quintasan: no worky worky
[16:48] <ulmlogger> already tried that days ago
[16:48] <ulmlogger> there is some problem with touch input
[16:48] <ulmlogger> only once you use two fingers it will actually be detected as input
[16:48] <ulmlogger> so it is a bit of a drag
[16:48] <Quintasan> Is it a problem with the application or the input magic?
[16:48] <ulmlogger> litterally :P
[16:48] <ScottK> ulmlogger: Maybe cnd can help you with that?
[16:48] <ulmlogger> Quintasan: not sure
[16:49] <ulmlogger> probably input magic
[16:49] <ScottK> If it sort of works like that, I'm OK with FFe.
[16:49] <ulmlogger> touchegg is not meant for touch devices
[16:49] <ulmlogger> it is meant for touch pads
[16:49] <ulmlogger> the things on a laptop
[16:49] <ulmlogger> where it works perfectly
[16:50] <ScottK> I see.
[16:51] <ScottK> Someone point me at the FFe bug and I'll approve it.
[16:54] <Quintasan> bambee: ^
[16:56] <bambee> Quintasan: pong
[16:56]  * bambee is opening thunderbird
[16:57] <bambee> bug 828637
[16:57] <bambee> ScottK, Quintasan: ^
[16:58] <ScottK> bambee: Approved.
[16:58] <bambee> woo! thanks! :D
[17:09] <Quintasan> jussi: On my G+ post, I forgot to mention we are doing that after Feature Freeze :DDD
[17:36]  * rgreening wishes he had a G+ invite.
[17:36] <rgreening> ^ Quintasan :)
[17:36] <jjesse> i can give you one
[17:36] <Quintasan> rgreening: email please :)
[17:36] <rgreening> jjesse: cool. would be sweet
[17:36] <jjesse> https://plus.google.com/_/notifications/ngemlink?path=%2F%3Fgpinv%3DYm4x4zDkd94%3AF3ZUHdJh1fQ
[17:36] <rgreening> roderick DOT greening AT gmail.com
[17:37] <Quintasan> Oh jjesse beat it to me
[17:37] <jjesse> click on the link
[17:37] <rgreening> YAY!
[17:39] <rgreening> thanks.
[18:25] <ScottK> Please be fixing http://people.ubuntuwire.org/~wgrant/rebuild-ftbfs-test/test-rebuild-20110816-oneiric.html#kubuntu
[18:26] <ScottK> I think I got pimlibs and company fixed.
[18:40] <micahg> \o/ packagesets get more eyes :)
[18:58] <afiestas> rbelem today I explained the plans for the places view to ereslibre
[18:58] <afiestas> he loved them :)
[19:04] <rbelem> afiestas, awesome :-D
[19:04] <rbelem> afiestas, i already stated to hack that
[19:04] <rbelem> afiestas, i changed it to threeview
[19:04] <afiestas> already?
[19:04] <afiestas> that was fast
[19:04] <rbelem> afiestas, :-D
[19:05] <rbelem> afiestas, it is a pretty simple 
[19:07] <afiestas> rbelem: if there is not a screenshot, it never existed :p
[19:26] <rbelem> afiestas, as soon as i arrive home i will send a screenshot to you :-)
[19:26] <rbelem> Quintasan, ping
[19:52] <markey> konnichiwa me friends, we be doing the hangoutery, and if ye shall desire, ye can join the funy
[20:17] <bcooksley> Hi
[20:18] <bcooksley> is somebody around who feels responsible for the kde-workspace patch "kubuntu_11_fix_root_only_kcms.diff"?
[20:18] <bcooksley> it is terribly broken
[20:18] <ulmlogger> it is a patch imported from fedora actually
[20:18] <ulmlogger> might be that they have an unbroken version
[20:18] <bcooksley> I see
[20:18] <ulmlogger> bcooksley: is there a builtin way to handle this?
[20:18] <bcooksley> kind of
[20:18] <ulmlogger> because I really think that would be a worthwhile feature
[20:19] <ulmlogger> also in terms of 3rd party integration
[20:19] <bcooksley> through the external application feature
[20:19] <ulmlogger> think company wants to expand systemsettings for internal stuff they need
[20:19] <bcooksley> see kde-workspace/systemsettings/examples/external-application.txt
[20:19] <ulmlogger> bcooksley: cheers
[20:19] <bcooksley> they'll show up just like any other module, and have a replacement fill in provided by system settings when clicked
[20:20] <bcooksley> allowing you to relaunch it if you want
[20:20] <bcooksley> if you wanted to reimplement root mode - rather than adjusting the control modules
[20:20] <bcooksley> line 209 of ModuleView.cpp is where it should be implemented
[20:21] <Quintasan> rbelem: pong
[20:21] <bcooksley> the patch causes http://bugs.kde.org/280356
[20:22] <ScottK> ulmlogger: Are you going to fix it then?
[20:22] <ScottK> That might go nicely with Quintasan GLES magic for one big -workspace upload.
[20:22] <ScottK> bcooksley: Thanks for pointing it out.
[20:23] <bcooksley> ScottK: np
[20:23] <ulmlogger> ScottK: if only I figureed out how
[20:25] <bcooksley> if you're talking about system settings, I wrote the code in question (moduleview.cpp) so feel free to ask about that area
[20:26] <rbelem> Quintasan, is there some something that i have to do? :-)
[20:27] <ScottK> ulmlogger: Since the amount of C++ I know would fit into a very small thimble, I think it's up to you.
[20:28] <ulmlogger> well, point being, I just tried to whip the external app stuff into an existing rootonly kcm and everything goes kaput
[20:28] <ulmlogger> ah
[20:28] <ulmlogger> getting somewhere
[20:28] <ulmlogger> or not
[20:29] <bcooksley> updated sycoca?
[20:34] <ulmlogger> bcooksley: there is some stuff weird with it
[20:34] <bcooksley> such as..
[20:35] <ulmlogger> well, with partitonmanager anyway
[20:35] <yofel> great, tomahawk has fooey licensing too ~.~
[20:36] <bcooksley> what does it do ulmlogger?
[20:36] <bcooksley> it is supposed to launch the module when you click the icon
[20:36] <ulmlogger> well, there is an actual partitionmanager kcm, or rather it is a kcm
[20:36] <ulmlogger> no idea why
[20:36] <ulmlogger> bcooksley: yeah, I got the desktop file fixed up
[20:36] <ulmlogger> works now
[20:37] <bcooksley> ok, cool
[20:37] <ulmlogger> it lacks busy indication though, might be my fault I guess
[20:37] <bcooksley> the system settings app itself forks that off
[20:37] <bcooksley> so it is now independent
[20:37] <ulmlogger> right
[20:38] <ulmlogger> gotta talk to fedora about this too
[20:38]  * ulmlogger is a tad drunk right now, so he'll put this on his todo
[20:38] <bcooksley> ok, thanks for taking the lead on this
[20:38] <bcooksley> if they still want compat with existing root modules
[20:38] <bcooksley> then the way to do it is to copy ExternalAppModule, modify that 
[20:39] <bcooksley> then tie it in like ExternalAppModule is in ModuleView
[20:40] <ulmlogger> noted, thanks for the info :)
[20:41] <ulmlogger> yofel: markey will be pleased to know
[20:41] <ulmlogger> yofel: send me a mail
[20:41] <ulmlogger> I'll meet with muesli tomorrow
[20:42] <yofel> I can talk to muesli myself on IRC. tomahawk itself is mostly ok, but the thirdparty stuff they ship has some missing copies
[20:45] <ulmlogger> yofel: 3rd party code copies are discouraged in the archive :P
[20:45] <ulmlogger> so that is a no go pretty much really
[20:45] <ulmlogger> especially since one can build tomahawk without that shite
[20:45] <ScottK> If it's just library copies, yes, please get rid of them.
[20:46] <yofel> $ ls thirdparty/
[20:46] <yofel> CMakeLists.txt  jreen  liblastfm2  libportfwd  qtweetlib  qxt  SPMediaKeyTap  winhttp
[20:46] <yofel> haven't checked if anything of that is actually needed
[20:46] <ulmlogger> none
[20:48] <yofel> hm, getting rid of that dir would need some cmake fixes it seems
[21:13] <CIA-52> [kubuntu-tablet-settings] Harald Sitter <apachelogger@ubuntu.com> * apachelogger@ubuntu.com-20110818211305-kxpym7cqh0dx9a5e * (24 files in 7 dirs) Initial release
[21:16] <ulmlogger> bulldog98_: https://code.launchpad.net/kubuntu-tablet-settings plz try, mind that you will have to hook it into startkde as of yet
[21:16] <ulmlogger> or deploy an xession file
[21:16] <ulmlogger> ScottK: ^
[21:16] <ulmlogger> Quintasan_: ^
[21:20] <yofel> ulmlogger: well, 2 of those are optional (without archive packages), qxt is in the archive but with different ABI, liblastfm2 would need some cmake find magic and libportfwd is somehow built-in
[21:21] <yofel> SPMediaKeyTap and  winhttp are mac/win
[21:24] <ulmlogger> too drunk
[21:27]  * yofel has a headache and postpones till tomorrow
[22:22] <yofel> hm, now I have a runaway kded process too
[22:24] <ulmlogger> yeah, Mamarok had it too
[22:24] <ulmlogger> though I really do not feel like looking into that shitty code again
[22:24] <yofel> 3 people in +1 have it too
[22:25] <yofel> but I don't get which of the 6 threads gdb sees is broken...
[22:25] <yofel> hm, thread 4 doesn't start with __GI___poll
[22:26] <yofel> #0  0x00007f71988c1913 in select () at ../sysdeps/unix/syscall-template.S:82
[22:26] <yofel> #1  0x00007f7199cb36d1 in QProcessManager::run (this=0x7f719a0055a0) at io/qprocess_unix.cpp:245
[22:26] <yofel> #2  0x00007f7199beaca5 in QThreadPrivate::start (arg=0x7f719a0055a0) at thread/qthread_unix.cpp:320
[22:26] <yofel> #3  0x00007f7196389edc in start_thread (arg=0x7f717f49e700) at pthread_create.c:304
[22:26] <yofel> #4  0x00007f71988c889d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
[22:26] <yofel> #5  0x0000000000000000 in ?? ()
[22:30] <ulmlogger> depper
[22:30] <ulmlogger> deeper
[22:30] <yofel> http://paste.kde.org/111499
[22:30] <yofel> that's all I get
[22:33] <ulmlogger> ok
[22:33] <ulmlogger> yofel: valgrind it
[22:33] <ulmlogger> with --tool=callgrind
[22:33] <ulmlogger> let it run for a bit
[22:33] <yofel> how does one valgrind a running process?
[22:33] <ulmlogger> with a bit of luck it should show what is called too often
[22:33] <ulmlogger> ie what causes the endless loop eating th ecpu
[22:33] <ulmlogger> yofel: google it
[22:33] <yofel> (if that's even possible)
[22:33] <ulmlogger> sorry, I have the command somewhere
[22:34] <ulmlogger> but I am too drunk to look for it
[22:34] <ulmlogger> or actually too tired
[22:34] <yofel> ok, no
[22:34] <ulmlogger> if you do not feel like it I can look for it tomorrow
[22:34] <ulmlogger> actually I think I pasted the command in the cpu usage bug for natty
[22:34] <ulmlogger> or at least I was close to doing so IIRc
[22:35] <yofel> ah wait, callgrind can do that somehow it seems
[22:36] <yofel> hm no
[22:36] <yofel> still needs to be run in valgrind first
[22:38] <yofel> ulmlogger: uh fun
[22:38] <ulmlogger> yofel: callgrind is a tool for valgrind
[22:38] <yofel> trying to run kded by hand gives:
[22:38] <yofel> kded4: symbol lookup error: /usr/lib/ntrack/modules/ntrack-libnl3.so: undefined symbol: ntrack_list_insert_sorted
[22:38] <ulmlogger> oh yeah, you might need the dbgsym package from ddebs
[22:38] <ulmlogger> also FWIW valgrind is essentially just a shell for varous memory analysis tools
[22:38] <ulmlogger> valgrind, callgrind, cachegrind, massif...
[22:39] <yofel> I know what valgrind is, used it a few times, it's just that you can't attach it to running processes since it emulates things
[22:39] <yofel> great, now I have NO kded process anymore
[22:40] <yofel> ulmlogger: ROFLMAO
[22:40] <yofel> last ntrack upload 
[22:40] <yofel>   * debian/libntrack0.symbols: add missing ntrack_info_human_banner symbol.
[22:41] <yofel> well, not really
[22:41] <yofel> let's see if this UDD thing actually has a use for once
[22:55] <yofel> ulmlogger: uh... why would a symbol in a library end up as Undefined but still appear in nm?
[22:55] <yofel> $ nm -DC /usr/lib/ntrack/modules/ntrack-libnl3.so | grep ntrack_list_insert_sorted
[22:55] <yofel>                  U ntrack_list_insert_sorted
[22:59]  * ScottK is almost sure ntrack is to blame and whatever it is will turn out to be a problem on Natty as well.
[22:59] <ScottK> Go yofel.  Go.
[23:02] <bambee> Riddell: Riddell: as I am a kubuntu member now, could you subscribe me to kde-packagers please ? (however, there's no hurry)
[23:03] <yofel> +1
[23:04] <yofel> hm, rebuilding ntrack changed nothing
[23:05] <yofel> someone fix debsums...
[23:07] <yofel> ScottK: it doesn't really help that ntrack-libnl3.so has no symbols file in the ntrack package...
[23:08] <ScottK> yofel: You know about the dbgsym repo, right?
[23:09] <yofel> I said symbols file, not debugging symbols
[23:09] <ScottK> Ah.
[23:09] <yofel> I have latter
[23:09] <ScottK> cyphermox: ^^^ You should fix that.
[23:09] <ScottK> Today that would be a requirement to get in Main.
[23:10] <yofel> well, the other files have one, but this lib seems to be a module
[23:10] <yofel> but then it shouldn't make kded fail...
[23:15] <wgrant> ScottK: What's broken?
[23:16] <ScottK> yofel needs symbols for ntrack-libnl3.so to troubleshoot random ntrack causes other processes to consume 100% of CPU.
[23:23] <Riddell> bambee: I think you need to file a bug on bugs.kde.org for sysadmin to subscribe you
[23:23] <bambee> Riddell: oh sure
[23:23] <bambee> np
[23:43] <cyphermox> ScottK: reading backlog
[23:43]  * yofel gives up for today
[23:44] <wgrant> ScottK: That will teach me to read my scrollback while half asleep. Your link to the FTBFS page showed up as a ping, so I thought you were telling me there was something wrong with it.
[23:45] <wgrant> Ahem.
[23:47] <cyphermox> ntrack-libnl3 has no symbols file, yeah, that's possible...