15:03:47 #startmeeting KDE SIG Meeting 15:03:47 Meeting started Tue Mar 4 15:03:47 2014 UTC. The chair is Kevin_Kofler. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:03:47 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:03:51 #meetingname kde-sig 15:03:51 The meeting name has been set to 'kde-sig' 15:03:57 #topic Role call 15:04:01 * Kevin_Kofler is present, who else? 15:04:13 * danofsatx-work ist hier 15:04:28 * jgrulich is present 15:05:34 here 15:06:03 present 15:07:13 A/V system crash...I'll be back in a sec or 10 15:08:27 * ltinkl present 15:09:38 * jreznik is around 15:09:54 #info Kevin_Kofler, danofsatx-work, jgrulich, rdieter, than, ltinkl, jreznik present. 15:10:04 #chair jgrulich rdieter than ltinkl jreznik 15:10:04 Current chairs: Kevin_Kofler jgrulich jreznik ltinkl rdieter than 15:10:13 #topic Agenda 15:12:45 kde-4.12.3 status 15:13:39 There's also a new KF5 alpha, but dvratil is not here to discuss it… 15:14:51 dvratil is on vacations 15:17:03 jreznik: OK 15:17:23 So will he work on the new KF5 alpha when he's back or is somebody else working on it? 15:17:53 * jreznik should contact the guy in the university regarding Akademy instead of dvratil... 15:18:06 present... sort of 15:18:36 Kevin_Kofler: I can take a look at it, I should have access to dvratil's COPR repository 15:19:01 jgrulich: OK 15:19:13 Thanks. 15:19:15 #action jgrulich to look into KF5 alpha 2 15:19:18 mbriza: have you seen the mail I forwarded to you - qt5 polkit-qt-1 and kdesrc-build - I don't have a clue what are the current plans 15:19:48 #chair mbriza 15:19:48 Current chairs: Kevin_Kofler jgrulich jreznik ltinkl mbriza rdieter than 15:20:45 jreznik: it was discussed a while ago... it seems drf will go for naming it polkit-qt-qt5 or something like that 15:21:02 Why not polkit-qt5? 15:21:14 mbriza: ok, I just saw it in my email and did not see any reply from anyone 15:22:07 #topic kde-4.12.3 status 15:22:10 rdieter: Your turn. 15:22:11 yeah, i'm not particularly sure how to respond 15:23:47 ok, kde-4.12.3 is in kde-testing repo since yesterday. bodhi update is pending (awaiting official upstream announcement before queuing to -testing) 15:24:20 kde-workspace-4.11.7 bit is already in -testing for a few days though 15:24:34 thats it 15:24:51 #info kde-4.12.3 is in kde-testing repo since yesterday. bodhi update is pending (awaiting official upstream announcement before queuing to -testing) 15:24:58 #info kde-workspace-4.11.7 bit is already in -testing for a few days though 15:25:10 rdieter: Thanks! 15:25:25 for meeting logs... 15:25:31 https://admin.fedoraproject.org/updates/FEDORA-2014-3179/kde-workspace-4.11.7-1.fc19 15:25:39 https://admin.fedoraproject.org/updates/FEDORA-2014-3168/kde-workspace-4.11.7-1.fc20 15:26:09 I don't think there are any problems or anything to discuss with that, is there? 15:26:27 It's a bugfix release, should just work. :-) 15:26:28 I don't think so either 15:26:51 #topic Open discussion 15:26:58 So, anything else? 15:26:58 one tiny packaging change was the introduction of a kdepimlibs-gpgme subpkg 15:27:18 (due to kwallet growing a new dep on gpgme) 15:27:20 Ah right, to avoid dragging in kdepimlibs from kde-runtime yet again. 15:27:31 We missed that in earlier 4.12.x packaging. 15:27:39 A user brought that to our attention. 15:28:32 #info A kdepimlibs-gpgme subpackage was split from kdepimlibs in our 4.12.3 packaging so that kde-runtime (KWallet) does not drag in the whole kdepimlibs. 15:30:27 * Kevin_Kofler thinks we're out of topics to discuss for today… 15:30:45 * Kevin_Kofler will close the meeting in 60 seconds if nobody speaks up. 15:31:42 don't know if it's meeting worthy but the the kdeartwork bug from F18 is still present in F20. 15:31:49 The screensaver crash? 15:31:52 We know that. 15:32:05 I think upstream wants to do away with those screensavers entirely. 15:32:10 yeah, that one. 15:32:11 k 15:32:15 They had been wanting to do that for several releases already. 15:32:41 So the code is not maintained upstream, chances to get those crashes fixed are slim. 15:32:53 They might also be the graphics drivers' fault, for all I know. 15:33:23 The backtrace is inconclusive (it shows that some X error got caught, but not where it was thrown, because those are caught asynchronously). 15:34:17 So I think that was it for this week, thanks all for coming! 15:34:19 I'm hitting it pretty reliably, I can toss some T/S cycles at it if we're interested in tracking it down. 15:34:55 danofsatx-work: Yeah, I guess setting the environment variable to trigger synchronous X errors (I forgot how it was called) would be the first step. 15:35:32 But there's also no evidence that everyone's X error is the same. 15:35:52 MESA_XSYNC 15:35:54 And IIRC there are also some other weird crashes in KScreenSaver, like segfaults on exit or so. 15:37:05 yeah, it's a weird one, but more annoyance than anything. if upstream is killing the screensaver slideshow, then there is no reason to debug it. 15:37:15 Anyway, if you can come up with a more useful backtrace, we'll appreciate it. 15:37:42 Upstream's plan is to support only Plasma screensavers instead of the traditional xscreensaver-based ones. 15:37:51 I'll see what I can do, and bug you and rdieter in the main channel 15:38:08 OK, thanks. 15:38:25 If it's something simple, I can probably fix it, if it's something like the driver crashing, not much I'll be able to do. 15:39:36 #action danofsatx-work will help debugging the KScreenSaver crashes. 15:39:41 So I think that was really all for this week now. :-) Thanks all for coming! 15:39:44 #endmeeting