14:07:32 #startmeeting KDE-SIG Meeting -- https://fedoraproject.org/wiki/SIGs/KDE/Meetings/2009-08-11 14:07:54 #topic Init 14:07:57 who's present today? 14:08:01 present 14:08:02 Present. 14:08:05 present 14:08:12 Present 14:09:41 alrighty, 14:09:51 #topic KDE 4.3.0 blockers (for F11/F10) 14:10:29 this should help, https://bugzilla.redhat.com/showdependencytree.cgi?id=515075&hide_resolved=1 14:11:23 2 open items: fish:// and cntl-f12 dashboard shortcut 14:11:48 https://bugzilla.redhat.com/show_bug.cgi?id=516416 14:11:49 Bug 516416: medium, low, ---, than, ASSIGNED, fish protocol broken in kde 4.3 14:12:07 There's an upstream commit being suspected for the regression. 14:12:17 We need to try reverting it and testing whether that fixes it. 14:12:32 +1, revert and see 14:12:40 seems upstream borked fish:// but good, yeah, who wants to work on testing out reverting ? 14:13:12 The offending commit: http://websvn.kde.org/?view=rev&revision=946444 14:13:25 rdieter: I'll give it a shot 14:13:41 Also suspicious: the fish.cpp change in: http://websvn.kde.org/?view=rev&revision=933202 14:13:42 * thomasj late present 14:13:47 ok, #action ltinkl to try reverting suspect upstream commit(s), and test things out 14:14:02 thomasj: hiya 14:14:03 If reverting 946444 doesn't fix it, we should try reverting 933202 too. 14:14:09 Hi :) 14:14:16 I didn't see any other relevant change between 4.2 and 4.3. 14:14:51 https://bugzilla.redhat.com/show_bug.cgi?id=516445 14:14:52 Bug 516445: low, low, ---, than, ASSIGNED, Show Dashboard Shortcut (ctrl-f12) doesn't work after upgrade to kde 4.3.0 14:14:58 That's the second one. 14:15:01 that one is funny :) 14:15:03 We don't seem to have much of a lead there. 14:15:34 ctrl+f12 - I can't reproduce it anymore... I was trying to reinstall kdesettings, deleting users globalshortcuts... for new user it's ok 14:15:36 somehow the default shortcut got lost during the update; system setting thinks the shortcut is conflicting 14:15:47 there's a lot of mysterious "shortcuts not working" bugs on upgrades. we saw that a bit with 4.2 too. 14:15:54 but the other shortcut it reports is the very same one :) 14:16:09 ctrl+f12 works for me. I can't reproduce 14:16:17 it doesn't for me 14:16:25 ie I can reproduce that 14:16:36 yeah, it either "just works" or mysteriously fails. 14:16:42 fun bug 14:17:08 I'm not sure but maybe I've seen it fail when desktop effects were enabled 14:17:26 normally I don't use it and it works then 14:17:30 svahl: I don't have DE enabled and it failed 14:18:06 svahl: same as jreznik 14:18:12 * thomasj cant reproduce it 14:18:13 ok, was just a try. :) 14:18:49 * jreznik has 2 other boxes to upgrade, will check it 14:18:55 is that one reported upstream (yet)? 14:19:00 if not, shouldn't we? 14:19:02 My opinion since its not 100% reproducable is bounce it upstream 14:19:09 Of course we should. 14:19:16 There's no upstream reference in our bug. 14:19:17 yup (it hasn't been reported upstream afaik) 14:19:17 what are the video cards of who it works vs dont 14:19:24 So I guess it hasn't been reported upstream yet. 14:19:34 just triaged it to request upstream filing 14:19:48 Southern_Gentlem: wrong window? :) 14:19:48 Southern_Gentlem: I don't think video cards have anything to do with this. ?? 14:19:48 Southern_Gentlem: I doubt it's a graphics driver bug. 14:19:51 Though you can never be sure. 14:20:23 ltinkl, what video card do you have 14:20:26 nouveau... 14:20:27 I'd propose someone currently experiencing it, upstream it, ltinkl ? 14:20:36 It just doesn't behave like a graphics driver bug. 14:20:49 the question is - is it really upstream bug? 14:21:10 hmm, now that I think of it, might be something to do with translations 14:21:15 I am using the binary nvidia blob here on 1 machine and nouveau on another 14:21:41 ltinkl: That could be it. 14:21:45 jreznik: english/czech KDE? 14:21:53 ltinkl: english 14:22:01 ok, that can't be it then :) 14:22:01 What locales are the people using who have the issue? And those who don't? 14:22:30 Yeah, if it can be reproduced with en_US.UTF-8 locale, it's likely not translations. 14:22:47 en_US works 14:22:59 de_DE too 14:23:08 en_US here 14:23:10 I think it's something else. 14:23:33 Maybe it depends on whether you customized the shortcuts while using 4.2 or not? 14:23:36 Though keyboard is DE 14:23:43 Kevin_Kofler: you're prob right 14:23:49 Kevin_Kofler: ye, maybe that as well, I had them customized before 14:23:58 I think it must be that. 14:24:09 Not customized here 14:24:15 which makes it "fun" to try to test/reproduce 14:24:16 ltinkl: I didn't customize them 14:24:20 The customization leaves some config file entries which apparently conflict with the new defaults. 14:24:31 jreznik: sure? 14:24:32 jreznik: Sure? 14:25:05 * jreznik is not 100% sure but usually don't customize global shortcuts 14:25:45 I'll check it home on laptops - I'll try to customize one and second I'll let without customizations 14:25:55 jreznik: does ~/.kde/share/config/kglobalshortcutsrc exist for you? 14:26:17 if you hadn't customized it, it shouldn't exist 14:27:33 ltinkl: you're right it existed, I tried to remove it while checking to reproduce... 14:27:40 jreznik: Keep the file! 14:27:43 Rename it or something. 14:27:51 But it's useful for testing. 14:27:55 ok, lt's clear we need more leads on this one, can discuss more after meeting, any other bugs to worry about? 14:28:00 ltinkl, i believe you, for sure, but i havent customized shortcuts at all and i have that file. 14:28:10 ops, too late... but I'll try to reproduce it on clean F11 image 14:28:22 Ouch, I'm on 4.2.4 right now and my kglobalshortcutsrc is a trainwreck, I have lots of entries of the {01079d9c-a5c7-484e-900b-f554f526254b}=,none,PrintScreen form with varying UUIDs. 14:28:29 No wonder PrintScreen doesn't work for some people. 14:28:38 There are dozens of conflicting entries for it. 14:29:40 I also have that fun entry there: {ee5b94c6-5735-4c35-8421-702dcb87fa2e}=,none,Perform DCOP call 'kdesktop KDesktopIface popupExecuteCommand()' 14:29:45 Looks like a leftover from KDE 3. 14:30:22 yup 14:30:37 Anyway, I don't think that is really related to that issue. 14:30:48 Those shortcuts got uuid-ized to get rid of them, it seems. 14:31:05 There seems to be a different migration issue for 4.2 to 4.3. 14:31:12 I guess the ID for "show dashboard" changed. 14:31:20 There must be 2 types of "show dashboard" now. 14:31:23 ah 14:31:30 And you end up with the same shortcut being assigned to both. 14:31:35 yes 14:31:42 I've read somewhere 4.3 has a different implementation of "show dashboard". 14:31:52 There must be the old one too, still, and the same shortcut for both. 14:32:01 * ltinkl digging in the sources and config files 14:32:27 The 4.2 one is: 14:32:28 [plasma] 14:32:29 Show Dashboard=Ctrl+F12,Ctrl+F12,Dashboard anzeigen 14:32:32 hmm, that could be our goal 14:32:51 Figure out what the 4.3 one is. 14:32:59 Then write a kconf_update scriptlet. 14:33:22 That file has been touched by other kconf_update stuff, so it's possible to kconf_update it (we shouldn't get a mess like for plasma-appletsrc). 14:33:55 Kevin_Kofler: there you go! 14:34:12 it shouldn't contain the German string imo 14:34:32 [plasma-desktop] 14:34:33 Show Dashboard=Ctrl+F12,Ctrl+F12,Show Dashboard 14:34:44 Kevin_Kofler: notice the different group name! 14:35:00 [plasma] -> [plasma-desktop] 14:35:04 Oh, that explains it. 14:35:05 looks like we have a winner 14:35:11 Need a kconf_update script for that. 14:35:21 yup, now I remember 14:35:39 aseigo mentioning the plasma executable changed from plasma to plasma-desktop 14:35:45 Who's going to write the script? 14:35:47 hmm, yes... I didn't realize that it's not plasma binary but plasma-desktop... 14:36:18 can someone do this on 4.2: ps aux | grep plasma 14:36:27 On 4.2 it's called just plasma. 14:36:32 let's get an upstream bug open first, document our findings, then a fix can be made (by us, upstream, whatever), sound like a plan? 14:36:35 It got renamed in 4.3. 14:37:05 That pointless rename is just causing problem. :-/ 14:37:08 *problems 14:37:31 hmm, looks like Plasma has only one shortcut assigned, so we see this only with the Show Dashboard action, right? 14:37:39 it's plasma on 4.2, plasma-desktop on 4.3 14:37:45 Wrong. 14:37:52 I also have "Activate Application Launcher Widget=Alt+F1,Alt+F1,Application Launcher" 14:38:20 same here 14:38:37 aha 14:38:40 the app launcher shortcut has never seems to work for me, is that the same class of problem? 14:38:44 that one doesn't work either for me 14:38:51 rdieter: definitely 14:39:31 alt+F1 shows Search 14:39:45 who wants the the task of working on this one? (or should we assign it to than as penance for not being here? :) ) 14:39:48 jreznik: nothing here 14:40:14 ltinkl: KickOff search is focused 14:40:27 it's not application launcher but could be used that way 14:40:27 jreznik: nothing happens here 14:40:28 I'm using the classic menu on 4.2.4, Alt+F1 does nothing. 14:40:53 nothing here 14:41:43 well, let's move on then, we're running shortish on time. 14:41:54 #topic Extragear for KDE 4.3.0 (status) 14:42:06 who's working on the extragear stuff? 14:42:17 than said that last week 14:42:29 I don't think anybody is, right now. 14:42:38 Than started importing some stuff, then nothing happened. 14:43:03 ok, another todo item them, any volunteers? 14:43:49 otherwise, we can punt on that until we have a chance to talk to than 14:44:16 Well, I think we don't have to wait for him. 14:44:23 I would but I'm booked solid until next week -( 14:44:30 I'll do that (and also try to contact than) 14:44:49 svahl: great, thanks 14:44:56 but I don't have rights for all extragear packages 14:45:22 svahl: Request the ones you're missing, we'll try to give you access to all. 14:45:42 sure 14:46:26 boo, separate issue, just for team management, does pkgdb allow for assigning rights, acls for groups? ie, have a kdesig group, so we don't have to go through this (like we did recenty for mathstuf, and now svahl)? 14:46:56 No. 14:47:06 ok, was afraid of that. 14:47:12 There's a hardcoded checkbox for provenpackager (which is supposed to be always checked these days) and that's all. 14:47:33 alright, next topic... 14:47:48 #topic KDE live images - status (see also http://lists.fedoraproject.org/pipermail/fedora-kde/2009-August/003555.html) 14:48:03 svahl ? 14:48:30 I've uploaded i686 and x86_64 images yesterday: http://lists.fedoraproject.org/pipermail/fedora-kde/2009-August/003555.html 14:48:44 but there were only one reporter yet 14:49:34 thanks! I'll make sure to get it myself asap. 14:49:37 * jreznik is currently trying x86_64 image in VBox 14:49:39 He also said that he needs to use prelink to get it working. Not sure what this means 14:50:03 first login - it crashed, on second attempt it was ok 14:50:35 with The process for the desktop protocol died... 14:50:39 svahl, it means one needs to run: prelink -f /usr/bin/kdeinit4 <== saw that in his rawhide installation already 14:50:42 there has been recent intermittent prelink-related breakage of kdeinit4 , prelink/glibc maintainer closed the bug once someone "fixed" things by manually re-running prelink (I don't consider that a fix) 14:50:57 so is this something I have to use in the kickstart? 14:51:14 svahl: maybe we should omit prelink altogether for now. 14:51:17 IMHO the packages should work after a clean installation 14:52:11 hmm, really kios are dead 14:52:36 the images also contain newer PyKDE4 and kde-settings from koji to get printer configuration and wallpaper back. Are they already tagged for F12Alpha? 14:53:37 svahl: should be, I'll double-check after meeting 14:53:51 thx 14:54:04 confirmed 14:54:05 They are, they hit Rawhide last night. 14:54:24 the biggest issue I've encountered is that firstboot isn't working after installation. bug #515419 14:54:25 Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=515419 medium, low, ---, clumens, NEW, firstboot GUI crashes when launched 14:55:07 clumens said that this probably won't be fixed before alpha: https://bugzilla.redhat.com/show_bug.cgi?id=515419#c6 14:55:09 Bug 515419: medium, low, ---, clumens, NEW, firstboot GUI crashes when launched 14:55:34 I guess the only related bug I can find is: https://bugzilla.redhat.com/show_bug.cgi?id=514048 14:55:36 Bug 514048: medium, medium, ---, jakub, CLOSED RAWHIDE, kded crashes at kde startup 14:56:06 and we (Kevin) closed it. oh well. time for another one I guess 14:56:14 mhh. that one I've not seen in my tests 14:56:20 . 14:56:35 I closed it because we thought the latest prelink in Rawhide fixed it. 14:56:47 But it looks like it's still broken. 14:56:50 So we should reopen it. 14:56:59 but randomly the desktop protocol died unexpectactly (or so) 14:57:13 right after login 14:57:29 desktop protocol is indeed broken on rawhide, that's been reported several times 14:57:41 ah, ok 14:57:53 for the package list: popular packages missing atm: amarok, kpresenter, konq-plugins, kdeartwork 14:58:39 my images for x86_64 are 30-40 megs bigger than the i686 ones. Cannot explain, why. I think I need someone else for confirmation 14:58:55 Any multilibs? 14:59:24 shouldn't be 14:59:25 no 14:59:52 we're almost out of time, any last thoughts before we end the meeting? 14:59:58 one time the install size of the kernel was 80 megs for i686 and 100 on x86_64 15:00:42 seems dracut is increasing kernel size a bunch, x86_64 even more, so maybe that explains it 15:01:15 maybe. but my test run for the gnome spin was only 2 megs difference 15:01:32 oh, interesting, ok, more investigation is warranted then 15:01:44 ok. I'll search for more information after the meeting 15:01:49 * rdieter too 15:01:50 I think we can't say much more without more data, so let's look into it. 15:01:53 I think that's all for live images 15:02:05 Let's close the meeting, the bug zappers are knocking on our door. 15:02:09 ok, let's wrap things up, thanks everyone 15:02:11 #endmeeting