15:13:44 #startmeeting kde-sig 15:13:44 Meeting started Tue Feb 5 15:13:44 2013 UTC. The chair is rdieter. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:13:44 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:13:52 #topic roll call 15:14:07 hola ladies and gents, who's present for kde-sig meeting today? 15:14:15 me 15:14:50 Present. 15:14:53 present 15:15:08 * rnovacek is here 15:15:11 present 15:15:27 is here 15:18:20 #info rdieter jgrulich Kevin_Kofler ltinkl rnovacek than dvratil 15:18:26 #chair jgrulich Kevin_Kofler ltinkl rnovacek than 15:18:26 Current chairs: Kevin_Kofler jgrulich ltinkl rdieter rnovacek than 15:18:35 #info tdfischer stirring 15:18:40 #topic agenda 15:18:45 what to discuss today? 15:18:46 lol 15:18:50 4.10 f18 plans 15:21:02 anything else? 15:21:16 * than would plan 4.10.1 for f18 15:21:30 than: good idea 15:21:53 ok, let's start on that. 15:22:04 #topic kde 4.10.x and f18 15:22:15 Any known blockers preventing it? 15:22:32 I know about the libkdcraw mess and I want to sort it out tomorrow. 15:22:32 proposal: target initial 4.10.1 for f18 15:22:46 Proposal: Fix the blockers and then queue 4.10.0 immediately. 15:23:03 ltinkl: maybe even include the systemd_login1 powerdevil stuff? 15:23:13 rdieter: yup 15:23:45 ok, I'll make a bz blocker bug to track things 15:23:52 I don't think we have one yet 15:24:23 todo (but probably not blocker): split kdegames 4.10 packaging 15:24:25 rdieter: I never understood the point of waiting just for the sake of waiting. We should track the blockers, and when all are fixed, go ahead. 15:24:38 Why wait for .1 just because it's .1? 15:24:55 Kevin_Kofler: fair enough, we haven't even formally tracked any bugs yet. 15:25:25 But IMHO split kdegames packaging is a requirement unless you do a non-split package. 15:25:45 Just keeping kdegames at the old version doesn't make sense. 15:26:16 why is that a blocker? 15:26:33 the older kdegames stuff still runs ok 15:26:42 yes it sucks, but nothing *bad* happens if we don't do it 15:27:39 the plasma cache goes "bleh" on upgrade is still a bit of a problem 15:27:44 Because 4.10 is 4.10, not 4.10 with parts of 4.9. 15:28:27 we fixed the "krunner can't logout/reboot on upgrade to 4.10" problem. (yay Kevin_Kofler), probably needs a bit more testing than my *one* try 15:28:58 Well, I'm sure that I fixed the problem, so one confirmation is enough for me. ;-) 15:29:11 any other blocker'ish type things anyone notice yet? 15:29:36 first off, how many here are using/testing 4.10 currently? 15:29:49 * rdieter is 15:29:53 * than is using 4.9.5 15:29:55 me too 15:30:01 * dvratil too 15:30:15 if not, why not yet? 15:30:43 * ltinkl is on 4.10 as well 15:31:02 apart from the double-suspend and (missing) resuming signal, all good 15:31:09 * Kevin_Kofler just upgraded from 4.8.5 to 4.9.5 this weekend. 15:31:15 and those should be fixed with yesterday's patch 15:31:27 Kevin_Kofler: and _you_ are pushing for 4.10? :p 15:31:40 ltinkl: I'd actually want 4.10 for F17 too! 15:31:45 And I'd have wanted 4.9 for F16! 15:31:48 gotta say though, this does seem to be the best KDE X.0 release I can remember 15:31:55 rdieter: +1 15:31:56 I miss the time where we actually properly supported Fn-1. 15:32:37 I'd have run 4.9 much earlier if it had been pushed to F16. 15:33:41 ok, who's for 4.10 on F18? (+1 yes, -1 wait for 4.10.1) 15:33:53 I have one issue with 4.10.0, unlock screen dialog sometimes doesn't have focus on password box 15:34:02 * rdieter got busy with other packaging tasks, like qt5, simon to do kdegames. any help would be appreciated 15:34:20 there is upstream bug for that, let me dig it out 15:34:28 rnovacek: ask dvratil :) multiple monitors? :) 15:34:33 I believe this has been fixed in 4.9.98 or something 15:34:36 ltinkl: yes 15:34:42 ltinkl, not KScreen fault, luckily 15:34:47 I know 15:34:55 * rdieter blames systemd somehow 15:35:00 tee hee 15:35:12 dvratil: it happens a lot less with 4.9.98 but almost always on 4.10.0 15:35:14 * ltinkl blames QML 15:35:18 interesting 15:35:53 but still a minor problem 15:35:54 rnovacek: once I get the 4.10 tracker bug, let's file one locally (rh bz) to track it 15:36:07 rdieter: ok 15:36:15 (though honestly that's probably not worth considering as a blocker though) 15:36:42 I saw another screen locker bug... the DPMS/screensaver doesn't kick in so the dialog stays there forever :/ 15:37:11 wrt waiting for 4.10.1 or not, I'd feel better waiting for .1 regardless. means a bit more polish, and more opportunities to test things 15:37:12 this one: https://bugs.kde.org/show_bug.cgi?id=311188 15:37:41 * than can help rdieter to package qt5 15:37:55 ltinkl: on fedora-kde list someone mentioned that happened for them too, but seemed to happen only if chrome was running. 15:38:23 rdieter: oh ye... chrome recently does the KDE inhibition tricks... and probably doesn't release them 15:38:36 that would be my guess 15:38:55 not sure why a browser would care about screensaver inhibition, but meh 15:38:58 or, the screenlocker-qml should release them all 15:38:59 NOTABUG or at least NOTOURBUG. 15:39:16 rdieter: for fullscreen things, like youtube etc ;) 15:39:18 If Chrome is broken, it's Chrome's fault, we can't do anything about it and shouldn't try. 15:39:29 Kevin_Kofler: don't think it's broken 15:39:30 ltinkl: exceptions sure, in fullscreen mode, or while playing a video 15:39:36 rdieter: exactly 15:40:43 than: step 1 is getting qtbase pkg review completed 15:40:52 it drives me crazy when I'm watching some fullscreen youtube video and have to move the mouse every 30 seconds or so to put the brightness back to max 15:41:29 rdieter: do you have the url? 15:41:59 bug alias qtbase 15:42:01 .bug 878188 15:42:05 rdieter: Bug 878188 Review Request: qt5-qtbase - Qt5 - QtBase components - https://bugzilla.redhat.com/show_bug.cgi?id=878188 15:42:56 anything wrt 4.10.x ? 15:43:28 rdieter: umm that bug with N9/Android phones 15:43:45 which actually happens only on 4.10 due to udisks2 backend 15:43:51 ah, ok. 15:44:02 * rdieter hurries to open tracker bug 15:44:11 I partly fixed it already, so the device at least appears 15:44:28 tomorrow I should have some testing device to finish it :) 15:44:31 i think bz is being extra slow to mock me 15:44:35 * ltinkl looks at dvratil's N9 15:45:04 * dvratil does not have any USB cable at hand 15:45:13 * dvratil will try at home 15:45:47 .bug 907993 15:45:51 ltinkl: what's the problem with n9? 15:45:56 rdieter: Bug 907993 kde-4.10 tracker - https://bugzilla.redhat.com/show_bug.cgi?id=907993 15:45:58 ^^ go nuts 15:46:25 rnovacek: does it work correctly on KDE 4.10 for you? 15:46:37 ltinkl: why you can't test it on your android phone? 15:46:41 (maybe it's just some Android phones, who knows) 15:46:53 ltinkl: seems so 15:47:06 jgrulich: mine works fine, it happens only with built-in storage, not SD cards 15:47:29 ltinkl: mount, open with doplhin, umount works 15:47:48 rnovacek: Device Notifier too? do you get that popup? 15:48:46 rnovacek: lol maybe it does because I already fixed it in Fedora builds :) 15:49:06 rnovacek: do you get the correct storage size in the popup? 15:50:00 just tried with rnovacek's cable...it does not work for me 15:50:16 The storage size fix is already in the F18 kde-workspace update that went stable today. 15:50:19 it prompts me a sudo password, Device notifier remain empty all the time 15:50:38 in Dolphin I see the device 2x - once as a partition (mountable, works) and second probably asa device, which cannot be mounted 15:50:41 both called "Nokia N9" 15:51:08 hm, for me it works, tested with Nexus S 15:51:14 and after unplugging only on of the devices disappeared from Dolphin 15:51:19 Kevin_Kofler: I think the patch we tested was only against 4.9.x builds 15:51:20 * rdieter checks 15:51:24 ltinkl: I don't see any storage size in the popup 15:51:59 dvratil: ye that§s the bug, update :) 15:52:13 dvratil: rpm -q kde-workspace 15:52:25 rdieter: I'm talking about the 4.9.5-7.fc18 build, indeed. I haven't followed what you did to 4.10. :-) 15:52:31 * dvratil is updating right now... 15:52:43 confirmed, ltinkl I can add that notifier_freespace patch to 4.10 builds too 15:52:50 But really, all patches we apply to 4.9.5 really ought to be applied to 4.10.x too, or we are creating a regression! 15:53:00 rdieter: nope, that's not the one 15:53:20 Kevin_Kofler: it was for testing-purposes only, awaiting feedback (at the time) 15:53:30 I suppose I could have done just a scratch build instead 15:53:35 rdieter: actually kdelibs, needs kdelibs-udisks2_2_stage.patch 15:54:12 ltinkl: ok, that one too then :) 15:54:22 ltinkl: don't care about the -workspace one then? 15:54:30 (should I drop it?) 15:54:35 rdieter: the other part, the correct size, still needs fixing (tomorrow when I have physical access to some testing device) 15:54:52 rdieter: the other part being in kde-workspace 15:55:13 I'll just do the 2_stage.patch for now then 15:55:24 rdieter: you backported kdelibs-udisks2_2_stage.patch for a scratch build but I don't see a relase for that 15:55:51 ltinkl: "the other part, the correct size, still needs fixing" → Oops, I guess we should have pulled it out of those kde-workspace builds. :-/ 15:56:15 Kevin_Kofler: it does no harm, I will just (hopefully) update the patch tomorrow 15:56:25 The F18 one is already in stable, but I can revoke the push request I put in for the F17 one after the last push if you want. 15:58:07 kdelibs-4.10.0-2 build underway 15:58:38 rdieter: great 15:59:06 rdieter: we'll sort it out tomorrow with dvratil and rnovacek 15:59:11 k 15:59:49 OK, great. 16:01:19 about of time, any last thoughts? 16:01:23 out of time even 16:03:10 ok, thanks everyone! 16:03:12 #endmeeting