15:11:48 #startmeeting kde-sig 15:11:48 Meeting started Tue Oct 9 15:11:48 2012 UTC. The chair is rdieter. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:11:48 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:11:55 #meetingname kde-sig 15:11:55 The meeting name has been set to 'kde-sig' 15:12:00 #topic roll call 15:12:04 Present. 15:12:11 me! 15:12:16 present 15:12:45 than, ltinkl, rnovacek : ping 15:12:51 * ltinkl is here 15:12:59 * rnovacek is here 15:13:02 present 15:14:45 #chair Kevin_Kofler dvratil jgrulich ltinkl rnovacek than 15:14:45 Current chairs: Kevin_Kofler dvratil jgrulich ltinkl rdieter rnovacek than 15:14:54 #info rdieter Kevin_Kofler dvratil jgrulich ltinkl rnovacek than present 15:14:58 #topic agenda 15:15:12 moving on to agenda, nothing published, so what should we discuss today? 15:15:52 rdieter: any blocker bugs for f18 15:16:14 * rdieter checks https://bugzilla.redhat.com/show_bug.cgi?id=F18Blocker-kde 15:16:28 .bug 829881 15:16:32 rdieter: Bug 829881 Use polkit .rules files instead of .pkla files - https://bugzilla.redhat.com/show_bug.cgi?id=829881 15:17:06 Yeah well, that one isn't really a blocker, I doubt QA would let it pass as a real blocker, NTH at best. 15:17:17 true 15:17:22 * rdieter checks https://bugzilla.redhat.com/show_bug.cgi?id=F18Target-kde 15:17:26 The .rules file will just have no effect, which means setting the clock requires a password by default. 15:17:28 * tdfischer is here, late 15:17:36 Uh, I mean the old .pkla file. 15:17:48 a few on target too 15:17:51 .bug 688956 15:17:54 rdieter: Bug 688956 kcm_touchpad: "Enable Tapping" doesn't work - https://bugzilla.redhat.com/show_bug.cgi?id=688956 15:17:58 If I get some time, I'll see if I can come up with a .rules file for that. 15:18:06 qwt6... 15:18:23 blocking on someone doing qwt5 review 15:18:23 Ah, that kcm_touchpad one is fun, default tapping actions being empty is lame. 15:18:34 You shouldn't have to enable tapping twice to enable it. 15:18:41 yeah 15:18:50 That's also something I had wanted to look into, sigh…… 15:18:55 .bug 845591 15:18:58 rdieter: Bug 845591 Review Request: qwt5 - Qt Widgets for Technical Applications - https://bugzilla.redhat.com/show_bug.cgi?id=845591 15:19:12 so... any help on these would be appreciated 15:19:33 (I just realized, we're still in agenda items, sorry) 15:19:46 anything else to discuss today, before moving on? 15:20:02 phonone-gstreamer is being ported to gst1.0 15:20:13 tdfischer: Yay! 15:20:14 that's my only contribution 15:20:18 tdfischer: thanks! 15:20:25 np 15:20:26 tdfischer: But it's a great one. :-) 15:20:46 moving on officially then... 15:20:52 #topic F18 blocker/target bugs 15:21:02 https://bugzilla.redhat.com/show_bug.cgi?id=F18Blocker-kde 15:21:08 https://bugzilla.redhat.com/show_bug.cgi?id=F18Target-kde 15:21:50 So for both #829881 and #688956, I have a pretty clear-cut idea of what needs to be done to fix those, but I just didn't get around to looking into them. 15:22:10 I'll have a look this week. 15:22:38 Kevin_Kofler: could you maybe document your ideas in those bugs... given that, maybe someone else could jump in and help finish it up. 15:22:42 (That's the PolicyKit rules and the kcm_touchpad stupidity.) 15:23:02 the pk thing should be fairly straight-forward tho 15:23:12 just adapting to the newer syntax 15:23:14 Well, for the PolicyKit rules, look at some existing .rules files and then make one which matches what the .pkla file did. 15:23:33 Yeah, just look at examples to see how the new syntax should look like. 15:24:20 For kcm_touchpad, I think that we need something like "if tapping is disabled, uncheck 'Enable tapping' and set tapping actions to some default actions rather than reading the settings which are all disabled". 15:24:56 I guess the time where it loads the driver settings and sets the UI based on that is probably the best time to set those. 15:25:34 Or alternatively, one could set some default actions when the user checks the box, but I think that's less nice, checking the box should only affect the grayed-out state of the tapping actions, not their values. 15:26:26 that sounds fun. 15:26:51 Oh, there's an issue which SHOULD be a blocker, but I don't think it's filed yet: the Anaconda rendering issues with oxygen-gtk! 15:27:14 that's news to me, what's up with that? 15:27:15 DaemonFC showed a screenshot where almost the whole UI was empty and as a result one couldn't make the required input to proceed to the next step. 15:27:22 So IMHO it's a blocker! 15:27:41 guess time to try a newer snapshot, that was definitely not the case with f18-alpha 15:27:43 There was some discussion about graphical glitches on the chan before, but it seems to be really bad. 15:27:54 rdieter: Yes, it's a post-alpha regression (probably in GTK+). 15:27:57 Kevin_Kofler, could #863276 be related? 15:29:05 dvratil: I'm having a look… 15:29:14 you can't see the hub (just a gray area), but it reacts on clicks 15:29:31 fyi, f18beta-tc2-kde x86_64 image is currently ~816mb 15:29:39 No, it's not the same. 15:29:51 The whole VM is gray in the screenshot in #863276. 15:30:19 In DaemonFC's screenshot, parts of the liveinst dialog are visible. 15:30:26 And it only happens with oxygen-gtk. 15:30:44 #863276 is standalone Anaconda, which doesn't use oxygen-gtk. 15:31:34 ok...I was able to reliably reproduce it in KDE spin, but not in Gnome 15:31:39 Let me see if I can find his screenshot (he posted it to the chan last night, it must be in tigcc_bot's logs). 15:32:26 dvratil: I think what you're seeing is DaemonFC's bug, not the OP of #863276's bug. 15:33:23 hmm, that could explain why I can't see it in Gnome :)) 15:33:47 https://imageshack.us/a/img43/760/snapshot1dv.png 15:33:53 This is DaemonFC's screenshot. 15:33:57 yeah, that exactly what I can get 15:34:02 *-can 15:34:10 Compare with https://bugzilla.redhat.com/attachment.cgi?id=621834 from #863276. 15:34:10 wow,nasty 15:34:24 the content is still clickable though, you just can't see the buttons 15:34:53 We need a separate bug filed (against GTK+ maybe?) and proposed as F18Beta blocker. 15:35:44 there are some runtime Gtk warnings, so maybe oxygen-gtk can't cope with it 15:37:04 dvratil: can you check which version of gtk is in use? 15:37:08 In any case, please file a separate bug and propose it as a blocker. 15:37:29 * rdieter will test too after meeting, as time allows 15:37:44 ok, I'll deal with it 15:38:04 .bug 856367 15:38:07 rdieter: Bug 856367 Impossible to rename a pdf file after choosing the directory - https://bugzilla.redhat.com/show_bug.cgi?id=856367 15:38:14 i was almost going to suspect ^^, but the symptoms are very different 15:38:48 and I guess that's largely limited to gtk2 these days (anaconda is gtk3 now or not?) 15:39:20 gtk3-3.6.0-1.fc18 15:39:43 whoa, we ship gtk2 too? 15:40:21 of course, lot's of things still use it 15:40:35 even on the live cd? 15:41:06 pretty sure yes, i'll double check when I test the f18-beta-tc2 image here in a bit 15:41:15 and take note what pulls it in 15:41:39 may be worth trying to omit it if it's not too much pain 15:41:45 Anaconda and all the system-config-* used to be PyGTK2. 15:43:10 These days, I don't know. But I think at least firstboot is still gtk2. 15:43:37 ok, I uninstalled oxygen-gtk3, now I can see the hub again 15:44:26 so either it's oxygen-gtk3 issue, or it's caused by Anaconda misusing Gtk (thus runtime warnings) which confuses oxygen-gtk 15:44:35 (Last I checked, the firstboot developers said they can't port to gtk3 because they want to keep supporting all the vendor-provided custom firstboot screens written for older RHEL versions. :-/ ) 15:45:18 dvratil: Or it's a gtk3 bug which breaks oxygen-gtk3. 15:45:55 indeed, that's an option too 15:46:06 (and FWIW, oxygen-gtk3 definitely does misuse GTK+ to some extent ;-) but normally it's supposed to work) 15:46:48 f18-Alpha had gtk3-3.5.10-1.fc18 oxygen-gtk3-1.1.0-2.fc18 15:47:05 Was Anaconda in Alpha already using gtk3? 15:47:14 now we're at (f18 tag): gtk3-3.6.0-1.fc18 oxygen-gtk3-1.1.1-1.fc18 15:47:33 We need to try downgrading things to see what changed. 15:48:07 ok, we have a plan on how to test that (after meeting). 15:48:19 #topic open discussion 15:48:26 anything else for today, before we close our meeting? 15:48:46 * dvratil is curious what will we do about the Nepomuk plugins 15:49:14 dvratil: ship what we can (ffmpeg is out of course) 15:49:21 Wait for how upstream tars them up, then package them where we can, get the rest into RPM Fusion. 15:49:41 nice 15:50:48 I don't think there's much more we can decide before we have the tarballs. 15:51:03 And I guess then it'll be straightforward, one specfile per tarball. 15:51:37 And we can decide whether and what to Require (obviously we can't Require the ffmpeg stuff, but we're probably expected to drag the rest in by default somehow). 15:51:56 But we need to see what the pieces are before we can make any reasonable decision there. 15:52:22 sure, this won't happen before KDE 4.10 anyway 15:55:53 looks like discussion tapered off, let's wrap up. thanks everyone! 15:55:56 #endmeeting