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