15:14:38 #startmeeting kde-sig 15:14:39 Meeting started Tue Nov 6 15:14:38 2012 UTC. The chair is rdieter. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:14:39 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:14:41 #meetingname kde-sig 15:14:41 The meeting name has been set to 'kde-sig' 15:14:49 #topic roll call 15:14:59 howdy all, who's around today 15:15:03 * jgrulich is present 15:15:08 * ltinkl is here 15:15:16 present 15:15:18 jreznik, Kevin_Kofler: kde*foo: ping 15:15:34 * jreznik is here 15:15:35 Present. 15:15:36 * rnovacek is here 15:15:40 #chair jgrulich ltinkl than jreznik Kevin_Kofler rnovacek 15:15:40 Current chairs: Kevin_Kofler jgrulich jreznik ltinkl rdieter rnovacek than 15:15:49 #info rdieter jgrulich ltinkl than jreznik Kevin_Kofler rnovacek present 15:16:13 #topic agenda 15:16:13 late, but present! 15:16:23 #info dvratil present too :) 15:16:30 what to discuss today? 15:16:31 rdieter was faster :) 15:16:33 #chair dvratil 15:16:33 Current chairs: Kevin_Kofler dvratil jgrulich jreznik ltinkl rdieter rnovacek than 15:16:58 f18 test matrices 15:17:35 from me: qyoto/cmake-2.8.10; PyQt/PyKDE(3) FTBFS... time to eol? find new maintainer(s)? 15:17:47 * rdieter gets more coffee 15:18:12 Is it still the same old failure or do we have a new one? 15:18:41 I think I already had a look, but I can have another one. 15:19:02 (at the Py*3 stuff) 15:19:46 ok, let's get started 15:19:58 #topic f18 test matrices 15:20:02 jreznik: ? 15:20:54 Oh, another topic (late, sorry): print-manager status. 15:21:30 we are getting closer to beta release - so please help with filling kde test matrices 15:21:32 * rdieter notes 15:21:35 #link https://fedoraproject.org/wiki/Test_Results:Fedora_18_Beta_TC7_Desktop 15:21:54 hope to have rc soon and not to block on unfilled matrices... 15:22:37 cool, i'd encourage everyone to help test and provide results 15:22:45 that's all from me, I'll ping you once rc is ready 15:22:55 k, that was going to be my next question. :) 15:22:59 from the first look, we are in a good shape 15:23:10 (as for desktop) 15:23:27 moving on... 15:23:37 #topic qyoto/cmake-2.8.10 15:24:05 fyi, there's a FTBFS against cmake-2.8.10 currently, seems to be some sort of behavior change, thankfully still only affects rawhide, so it's not urgent 15:24:17 upstream is aware, and a thread is going on kde-packager/kde-buidsystem lists 15:24:38 Kevin_Kofler suggested a fix/workaround in our downstream bug, i hadn't had a chance to try it yet 15:25:06 .bug 872829 15:25:08 rdieter: Bug 872829 qyoto FTBFS with cmake-2.8.10 - https://bugzilla.redhat.com/show_bug.cgi?id=872829 15:25:33 I think my change should make it work, but of course if CMake upstream thinks the change is a mistake, then we better backport the upstream fix which reverts it. 15:25:34 i'll try to look at it before the end of the week, but any help before then would be appreciated. 15:25:52 Because the version comparison in my patch assumes the patch is here to stay. 15:26:06 ok 15:26:11 Otherwise you want to check for exactly 2.8.10 rather than ≥ 2.8.10 as now. 15:26:31 sure, hopefully upstream will sort it out quickly 15:26:39 (but even that is bad if we're going to get a 2.8.10 build with the change reverted) 15:26:59 (so in that case applying my patch probably does more harm than good) 15:27:19 sure, any fixes/changes in cmake will require corresponding changes in qyoto 15:28:02 i guess that's about it, moving on... 15:28:30 #topic PyQt/PyKDE(3) FTBFS 15:28:34 .bug 863104 15:28:37 rdieter: Bug 863104 PyQt FTBFS against sip-4.14+ - https://bugzilla.redhat.com/show_bug.cgi?id=863104 15:29:06 PyQt/PyKDE(3) seems to be break about every other sip release these days, may be worth considering eol'ing 15:29:15 rdieter: +1 15:29:28 Question of the day: Does anything in Fedora still use them? 15:29:34 or find new maintainers... honestly i've lost interest a long time ago 15:29:47 Kevin_Kofler: a few items 15:29:51 * rdieter repoqueries 15:30:00 I see you already did in the bug. 15:30:12 ScientificPython-qt, kodos, kphotobymail, pipviewer, smart-gui 15:30:41 I think we should at least try to fix the FTBFS before killing those packages. 15:30:42 ask the maintainers if they are still working on these packages? 15:30:53 I'll try to fix the FTBFS. 15:31:03 Kevin_Kofler: thanks 15:31:05 intersting, luma showed up in the list before, but it doesn't for me anymore 15:31:21 #actino Kevin_Kofler will try to fix the FTBFS 15:31:32 s/actino/action/ :-) 15:31:49 #action Kevin_Kofler will try to fix the FTBFS 15:31:52 better. :) 15:31:58 moving on... 15:32:14 #topic kde-print-manager status 15:32:34 so, the general idea was to replace kde-printer-applet with kde-print-manager sooner or later 15:32:51 dantti will be in brno this week... 15:33:05 it's in comps-f19 as default now, no f18 yet unfortunately 15:33:29 my own minimal testing has been mixed. it serves well as print queue manager 15:34:04 FYI, luma was upgraded to a PyQt4 version ~a month ago: http://pkgs.fedoraproject.org/cgit/luma.git/commit/?id=c0fc13c34b385f526a58798720dda89a05a78a76 15:34:08 it failed to correctly configure my avahi-detected network printer @ home (though that may well be a cups bug recommending the wrong driver/setup) 15:34:18 Kevin_Kofler: woo, one less to worry about. 15:34:33 so, more testing/feedback using it is needed 15:34:50 has anyone else tried it much yet? 15:35:17 * Kevin_Kofler would love having printer-applet by default ASAP, if anything because it's not system-config-printer-kde (and its kde-printer-applet). ;-) 15:35:24 it correctly setup both my local USB printer and the remote CUPS printers at Brno RH office 15:35:25 it's one of those 'manually add to systray plasma applet' like things 15:35:33 s-c-p-kde is just horribly buggy. 15:35:36 ltinkl: oh goodie 15:35:58 Kevin_Kofler: true, even with some faults, it probably is still the lesser of 2 evils 15:36:01 "manually add to systray plasma applet" – uh, that's what the init and update scripts are for. :-) 15:36:15 We need to ship some of those if we want to make it the default. 15:36:24 handy but you must always remember not to send any sensitive data to the "wrong" printers :) 15:37:17 that's good enough for me. any volunteer for writing the plasma init/update script? 15:37:24 rdieter, jreznik: is there still a possibility to include it for F18 by default? 15:37:51 ltinkl: even though it's a bit late, I'm ok with that. 15:37:57 ltinkl: not for beta 15:38:34 jreznik: sure, after beta and after having a thorough discussion with dantti this weekend 15:39:32 given how bad s-c-p-kde is 15:40:15 ltinkl: yep 15:40:48 * rdieter was disconnected for a couple minutes there, can you repeat anything said after my "I'm ok with that", and now? 15:41:50 nothing after [16:39] given how bad s-c-p-kde is 15:42:05 anyway, as an aside, anyone object to eol'ing s-c-p-kde and kde-printer-applet altogether (ie, not ship them, and add Obsoletes: to kde-print-manager) ? 15:42:20 ltinkl: will discuss it with dantti this week personally 15:42:54 rdieter: no objection 15:45:32 [16:37] ltinkl: even though it's a bit late, I'm ok with that. 15:45:33 [16:37] ltinkl: not for beta 15:45:35 [16:38] jreznik: sure, after beta and after having a thorough discussion with dantti this weekend 15:45:36 [16:39] given how bad s-c-p-kde is 15:46:03 i'll open a bug to track adding kde-print-manager as default, plasma init/update scripts, and Obsoletes 15:46:26 rdieter: No objection to EOL/Obsoletes IFF print-manager works as advertised and becomes the default. 15:46:31 f19 is a given (right?), once we have that in place, we can seriously consider f18'ifying it too 15:46:39 It's good to have one default. 15:47:17 Now we just need to lobby upstream to officially replace s-c-p-kde/printer-applet there too. :-) 15:48:08 * jreznik is switching to the phone... 15:49:18 moving on... 15:49:24 #topic open discussion 15:49:27 anything else for today? 15:50:01 oh, kde-4.9.3, all build in rawhide (minus qyoto). was waiting for f18 beta freeze to lift before charging ahead with f17/f18 builds. 15:50:34 just in case, we needed to fix anything else at the last minute for beta 15:50:47 The question is, how long will we be in freeze? 15:51:05 does it matter? 15:51:13 It may well be worth starting to build 4.9.3 stuff right now. If we need an urgent fix, we can build it from a quick branch. 15:51:31 maybe so, jreznik, what's your best guess? 15:51:38 jreznik_n9: ^^ too ? 15:52:06 * rdieter is ok with charging ahead 15:52:16 Just to be sure, do we have any open blockers against KDE SC right now? 15:52:25 * rdieter double-checks 15:52:35 (because if so, we want those fixed first :-) ) 15:52:51 .bug 873746 15:52:53 fyi ^^ 15:52:54 rdieter: Bug 873746 make kde-print-manger default - https://bugzilla.redhat.com/show_bug.cgi?id=873746 15:53:00 * rdieter fixes typo 15:54:10 kde-print-manger, is it Christmas already? ^^ 15:54:17 lol 15:55:00 .bug 846844 15:55:03 rdieter: Bug 846844 Fedora 18 Blocker KDE Tracker - https://bugzilla.redhat.com/show_bug.cgi?id=846844 15:55:06 i don't see anything on our plate ^^ 15:55:11 Good. 15:56:22 one more fyi, i took a baby step adding initial power-related systemd-login support to lightdm yesterday 15:56:46 so now shutdown/restart action is handled via systemd now 15:58:03 kudos to Tim Lauridsen for the initial polkit rules and proof-of-concept patch 15:58:28 .bug 872797 15:58:33 rdieter: Bug 872797 lightdm: provide polkit .rules for actions - https://bugzilla.redhat.com/show_bug.cgi?id=872797 15:59:05 than, ltinkl : what do you think about moving ahead doing kde-4.9.3 builds for f17/f18 now? 15:59:33 rdieter: i'm fine with 4.9.3 for f17/f18 15:59:49 rdieter: sure, go ahead 16:00:04 rdieter: +1 16:00:24 ok, I can, unless someone else wants the fun? :) 16:00:35 +1, go ahead. 16:00:41 * rdieter breaks out build-it.sh script 16:01:09 I belive the f17-kde/f18-kde koji targets should be ready 16:01:26 anything else for today? we're at the top of the hour. 16:02:03 .bug 868530 16:02:07 than: Bug 868530 Delay and cpu spike in file open/save dialogs - https://bugzilla.redhat.com/show_bug.cgi?id=868530 16:02:29 than, patch for Dolphin is in KDE RB, as soon as it's approved, I'll put it to Fedora 16:02:43 But we really need caching inside solid-udisks2. 16:03:04 dvratil: it seems it's affected in qfiledialog too 16:03:12 that has already been fixed 16:03:18 wait, Q? 16:03:27 dvratil: yes qfiledialog 16:03:31 not kde 16:03:40 KDE overrides the Qt file dialogs under some conditions. 16:04:01 So chances are the dialog that's the subject of complaints here isn't really the Qt-only one, but actually the KDE one. 16:04:03 If it's Solid issue, it can't affect the pure Qt dialog, they don't use Solid 16:04:13 dvratil: please try standarddialogs from qt-examples 16:04:20 and you will see the issue 16:04:49 than: Does the dialog you see look exactly like in a KDE app (other than possibly missing translations)? 16:04:55 reminds me, we need karma for kdelibs update 16:04:59 than, that's KDE dialog 16:05:03 probably injected somehow by KDE 16:05:17 Because then it's not the Qt-only dialog, it's the dialog overridden from KDE. 16:05:22 https://admin.fedoraproject.org/updates/FEDORA-2012-17234/kdelibs-4.9.2-11.fc18 16:05:22 Pute Qt dialog cannot have Nepomuk timeline :) 16:05:32 https://admin.fedoraproject.org/updates/FEDORA-2012-17385/kdelibs-4.9.2-11.fc17 16:05:44 need to be queue'd for stable before we can submit kde-4.9.3 for -testing 16:05:54 There are at least 2 things which can load KDE file dialogs into Qt-only apps: the KDE Platform Plugin and the Oxygen style. 16:06:27 So it's the same issue as in KDE apps. 16:06:43 and that should be fixed already in upstream and in our kdelibs 16:06:46 The same fix should fix it. 16:06:49 i removed all oxygen stuff before trying the qfiledialog 16:07:00 than: There's also the platform plugin. 16:08:05 than: that's a KDE dialog (for Qt apps running under KDE) 16:08:51 I must admit I didn't notice until now that KDE injects kdialogs to pure Qt apps :) 16:09:21 i will investigate more 16:12:55 dvratil: do you have the link for the patch in dolphin? 16:13:05 than, https://git.reviewboard.kde.org/r/107168/ 16:13:15 thanks 16:14:17 dvratil: if it's not too much trouble, we could include the patch in our packaging now (for testing, feedback) 16:15:04 rdieter, well the patch works (at least for me and ltinkl), but it's not sure whether Frank will accept it as it is now 16:15:29 ok, reading the review, yeah, seems maybe we should wait until we're closer to some consensus 16:15:40 rdieter: yup, I'd suggest waiting in this case 16:16:04 I'll ping you when things are sorted out 16:16:04 how about other kde apps like gwenview? 16:16:06 ok, will close meeting in 2 min 16:16:33 dvratil: i assume it could be affected in other kde apps too 16:16:33 than, gwenview is already doing smart-enough cacheing so that the performance impact is not really visible 16:17:18 maybe using the asynchronous cache could speed up start up time a bit, but there is no major usability issue like with dolphin 16:17:44 gwenview also have delay when starts 16:18:27 yeah and it indeed is caused by waiting for Solid, but at least you don't wait ~4 seconds for context menu :) 16:18:28 someone has reported that resizing of gwenviews's window takes so long 16:18:43 no problem here 16:18:59 it starts but at first shows empty window about 10 seconds before items shown 16:19:01 can reproduce either 16:19:03 *can't 16:19:15 ltinkl: have you tried to resize the windows? 16:19:20 than: yup, no prob 16:19:34 So what about adding caching to Solid itself? 16:19:49 If the problem is that it has to enumerate the whole device tree all the time, it should cache the tree somehow. 16:19:52 Kevin_Kofler: already there, from the start 16:20:01 Kevin_Kofler, the problem is the initial query 16:20:05 which is synchronous 16:20:20 dvratil: tested on f18? 16:20:25 than, yop 16:21:01 Kevin_Kofler, the patch of mine moves the query to another thread so it should not block...that's something you can't fix in Solid, until kdelibs is unfrozen 16:22:24 The kdelibs freeze really sucks. 16:22:55 What sucks the most is that they don't want to budge despite all the problems it's causing. 16:23:25 what really sucks is Solid's synchronous API (and whoever made it) 16:24:45 out of scope of this meeting, we're running out of time :) 16:25:15 I think we need to look into improving things in Solid with the API we have. 16:25:26 So try to get response times of the sync calls down. 16:25:46 uhm, sorry I got ksmscrash - what did I miss since my complaints about solid's API? 16:25:50 Maybe we should even try to ask udisks2 folks for the missing APIs instead of trying to work around it in expensive ways? 16:25:52 *ksmserver crash 16:26:01 [17:24] out of scope of this meeting, we're running out of time :) 16:26:02 [17:25] I think we need to look into improving things in Solid with the API we have. 16:26:33 "Enumerate everything, then filter" is a quite lame approach. :-( 16:27:13 Kevin_Kofler: +1 16:28:03 i think we've beaten that topic into submission, let's end the meeting. followup and further discussion can go on outside of the meeting 16:28:04 I don't see a problem with this approach, because we should have async API and sane caching - we have the caching, the synchronous API is the killer here 16:28:48 thanks everyone. 16:28:50 #endmeeting