15:01:37 #startmeeting kde-sig -- https://fedoraproject.org/wiki/SIGs/KDE/Meetings/2011-01-04 15:01:37 Meeting started Tue Jan 4 15:01:37 2011 UTC. The chair is jreznik. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:01:37 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:01:54 #meetingname kde-sig 15:01:54 The meeting name has been set to 'kde-sig' 15:02:03 #topic roll call 15:02:14 who's present today? 15:02:36 here 15:02:52 Present. 15:04:31 #chair rdieter Kevin_Kofler 15:04:31 Current chairs: Kevin_Kofler jreznik rdieter 15:04:57 * jsmith lurks just for the fun of it 15:05:20 * rdieter hands jsmith popcorn 15:05:27 :) 15:05:52 rdieter: Thanks :-) 15:06:17 #info jreznik rdieter Kevin_Kofler present, jsmith lurks with popcorn 15:06:43 #topic agenda 15:07:10 any New Years topic? except the New Year? 15:08:01 Various status updates? 15:08:18 E.g. any news about libreoffice-kde? 15:09:06 phonon for one, upstream split the core library and the backends. will require packaging/reviewing backends 15:09:19 Oh right. 15:09:55 Kevin_Kofler: libreoffice-kde is more topic for ltinkl, he's not here... 15:09:56 Speaking of the default backend, Dragon Player still relies on xine-lib to show DVD menus and it looks like Phonon is lacking one function which would be needed there (a way to trigger the DVD menu). 15:09:57 I ran into that after Sho asked me to package a newer phonon snapshot 15:10:19 ok, so lets start with Phonon 15:10:20 Kevin_Kofler: darn, I thought apachelogger had fixed that 15:10:30 #topic Phonon 15:10:50 rdieter: could you give us some overview what happens in Phonon land? 15:10:57 He's done some DVD menu work in Phonon-GStreamer, but the API to trigger the menu is missing. 15:11:11 to sum up: phonon upstream has moved to git.kde.org and the core library and backends are now split 15:11:16 I wanted to port Dragon Player to the new API and noticed there wasn't any. :-/ 15:11:29 I asked apachelogger and he said it just isn't there yet. 15:11:30 http://apachelog.wordpress.com/2010/12/23/the-phonon-family-is-moving/ 15:13:06 Kevin_Kofler: suckage. so... if we want to ship f15 xine-less, we'll lose out on that (in dragonplayer anyway) 15:13:24 Yes, unless something happens thereā€¦ 15:13:52 I guess I'm willing to live with that (for now) 15:14:15 apachelogger now knows it's needed. 15:16:14 ok, I guess that's about it from phonon-land then. 15:16:28 I'll finish working on the phonon repackaging, and submit some reviews 15:17:43 rdieter: ok, ping me, and I'll do reviews 15:17:55 cool, will do 15:18:02 #action rdieter to finish working on the phonon repackaging, and submit reviews 15:18:18 #action jreznik to review rdieter's reviews 15:20:56 so that's all for Phonon 15:21:27 So FYI we have KOffice 2.3.0 in Rawhide now, plus a backported patch to support the new libwp*. 15:21:28 [16:08] Various status updates? 15:21:34 which ones? 15:21:44 Well, that was one. :-) 15:21:44 * jreznik was completely out during Holidays :( 15:21:52 Kevin_Kofler: you were faster :) 15:22:02 rdieter did the upgrade and I did the libwp* backport. 15:22:11 #topic Various status updates 15:22:37 #info we have KOffice 2.3.0 in Rawhide now, plus a backported patch to support the new libwp* by Kevin_Kofler and rdieter 15:23:37 The new KPK for F14 hit stable, as well as a Qt fix for a tree view crash affecting KPK. 15:23:51 speaking of koffice, another related item... kdab has (finally) released a standalone kdchart, when I find time, I'll finish up packaging that up too (and then build both koffice and kmymoney against it) 15:24:20 Yes, that'd be great! 15:25:01 What do we do about the Lokalize mess (the crash is fixed but now there's junk appended instead). 15:25:38 Do we use the workaround from Lokalize upstream? (Is it already in 4.5.5?) And what about Psi, is that hit by the "junk appended" issue as well? 15:25:54 I'm considering to just revert the performance optimization in Qt which caused that regression. 15:25:58 I'd rather have slow, working code. 15:26:20 There have been 2 followup crash fixes to that "optimized" code and it's still broken! 15:26:36 Kevin_Kofler: +1 15:26:49 Kevin_Kofler: that's the lokalize upstream workaround? 15:27:00 err, s/that's/what is/ 15:27:35 IIRC, the upstream workaround is a hack inside Lokalize where they use some convoluted process to "select all" instead of the normal method. 15:27:41 See the upstream bug. 15:27:55 https://bugs.kde.org/show_bug.cgi?id=249373 15:28:25 I haven't checked whether that was committed to 4.5.5 or only 4.6.0. 15:29:12 jreznik: The thing is, that optimization was considered a bugfix by Nokia (otherwise they wouldn't have applied it to a point release). 15:29:31 This trend really worries me, they keep doing performance optimizations which break things. 15:29:33 and for reference, http://bugreports.qt.nokia.com/browse/QTBUG-15659 15:29:41 They care about speed above quality these days. :-( 15:29:55 Kevin_Kofler: optimalizations are needed but should not break things... 15:31:26 Another big problem is that upstream Qt keeps asking for non-KDE testcases each time they break something in KDE. 15:32:00 not necessarily non-kde testcases, just minimal test-cases (non-trivial test-cases are obviously harder for them to use) 15:34:22 that makes sense 15:35:30 I guess we have 2 options: just use localize workaround or revert the qt optmization 15:37:08 does it affect other apps (Kevin mentioned Psi)... 15:37:10 ? 15:37:25 in that case, we should revert the qt optimalization 15:38:04 The crash was also found in Psi, I don't know whether the "junk appended" issue affects it, too. 15:38:12 See http://bugreports.qt.nokia.com/browse/QTBUG-15857 15:40:44 ok, revert +1 15:41:35 revert +1 15:42:28 Of course we need to test whether that optimization is really the patch to blame, but I'm fairly sure it is. 15:44:39 Kevin_Kofler: could you try it? 15:46:48 I guess I can try to build it, then see if I can test it. 15:47:20 Of course, the uphill battle will be convincing upstream Nokia that they should revert their broken optimization. 15:48:00 Hmmm, that said, in the upstream reports, the Lokalize author suggests a possible fix, which looks to be a 1-line fix. 15:48:14 (fix which doesn't require reverting the optimization) 15:48:18 I guess we need to try that too. 15:48:34 But I think he hasn't tested it, he just says it "should" work. 15:48:57 but then you have to fix Psi and whatever affected 15:49:05 jreznik: 1-line fix to Qt 15:49:11 Kevin_Kofler: ok 15:49:21 sounds even better 15:49:48 "the problem with current fix is that select() method can fail, it doesnt check for return value of movePosition() calls, which is false on a non-valid cursor 15:49:48 my guess is that using setPosition(0) instead of movePosition(Start) should eliminate the problem" 15:50:36 What annoys me a bit is that they're patching over the bugs repeatedly instead of just reverting the regressing optimization, which would IMHO be a much safer action on a release branch. 15:50:54 I guess they really need that stuff to be fast for their mobile targets. 15:51:14 But if that bug is really 1 line to fix, we should probably do that. 15:51:45 I think what I'll try is 1. the suggested 1-line fix and (if that doesn't work) 2. reverting the optimization. 15:52:06 (And if that doesn't work either, I'll have to give up.) 15:53:38 makes sense 15:58:47 #action Kevin_Kofler to try the 1-line fix, then reverting optimalization 15:58:57 ok that's probably all for this meeting 15:59:03 thanks 15:59:21 agreed 15:59:42 * jreznik is going to prepare meeting summary 15:59:51 #endmeeting