[16:59] *** rdieter sets the channel topic to "KDE-SIG Meeting -- http://fedoraproject.org/wiki/SIGs/KDE/Meetings/2008-04-22 -- Init". [17:01] kde sig meeting about to start, who's present today? ping: Kevin_Kofler, svahl, than, ltinkl, kde*foo [17:01] Present. [17:01] * spstarr_work watches [17:01] I'm here this time [17:02] can I participate as a "spectator"? [17:02] lvillani: sure! [17:03] *** stickster_afk is now known as stickster. [17:03] fine :) [17:03] short-n-sweet agenda today, let's get started... [17:03] *** rdieter sets the channel topic to "KDE-SIG Meeting -- http://fedoraproject.org/wiki/SIGs/KDE/Meetings/2008-04-22 -- recent security announcements on kde-packager". [17:03] --> gbcox has joined this channel (n=gbcox@76.91.247.10). [17:03] topic 1: recent security announcements on kde-packager [17:03] ltinkl wanted to commit the patches, but CVS is still down for branching. [17:03] Gerald Cox her [17:03] e [17:04] Kevin_Kofler: cvs should be good to now now. [17:04] good to go now even [17:04] --> ltinkl has joined this channel (n=ltinkl@82.100.47.250). [17:04] re [17:04] https://www.redhat.com/archives/fedora-devel-list/2008-April/msg01566.html [17:04] CVS is back up. [17:04] ltinkl: so, you game to take care of the security patches, announcments? [17:05] <-- kital has left this server (Remote closed the connection). [17:05] dunno what's been said to the topic already but I have the patches ready in my local CVS, just waiting for it to be open again for writing [17:05] --> couf_afk has joined this channel (n=bart@fedora/couf). [17:05] *** stickster is now known as stickster_afk. [17:06] ltinkl: I just committed something a few minutes ago, so go go go. [17:06] *** couf_afk is now known as couf. [17:06] ok, will do after the meeting [17:06] <-- couf has left this server (Client Quit). [17:06] --> shalem has joined this channel (n=hans@ip32-174-211-87.adsl2.versatel.nl). [17:06] lets move on [17:06] --> hans__ has joined this channel (n=hans@ip32-174-211-87.adsl2.versatel.nl). [17:06] --> couf has joined this channel (n=bart@fedora/couf). [17:07] fyi, agenda: http://fedoraproject.org/wiki/SIGs/KDE/Meetings/2008-04-22 [17:07] *** rdieter sets the channel topic to "KDE-SIG Meeting -- http://fedoraproject.org/wiki/SIGs/KDE/Meetings/2008-04-22 -- disabling/hiding "Zoom out" in Plasma desktop toolbox until 4.1? (request by mefoster, see also http://websvn.kde.org/?view=rev&revision=794496)". [17:07] topic 2: disabling/hiding "Zoom out" in Plasma desktop toolbox until 4.1? (request by mefoster, see also http://websvn.kde.org/?view=rev&revision=794496) [17:07] <-- nphilipp has left this server ("Leaving"). [17:07] *** hans__ is now known as hansg. [17:07] that seems reasonable, the functionality is not ready yet [17:07] and, https://bugzilla.redhat.com/show_bug.cgi?id=443610 [17:07] Bug 443610: low, low, ---, Lukas Tinkl, ASSIGNED , RFE: disable "Zoom Out" button in corner [17:08] We wouldn't be the only distro doing it ... [17:08] any objections to this? [17:08] Erm, no FPC meeting yet, aren't the DST's synchronised again? [17:08] otoh, this isn't a F9blocker, and I'd kinda rather this get sorted out upstream, but I can live with patching locally in the meantime. [17:08] <-- shalem has left this server (Client Quit). [17:09] rdieter: as a external patch? [17:09] Basically, zooming out doesn't work at all. [17:09] It would be just one line to disable it. [17:09] I don't think it will be actually fixed before 4.1. [17:10] spstarr_work: yes, see https://bugzilla.redhat.com/show_bug.cgi?id=443610 [17:10] Bug 443610: low, low, ---, Lukas Tinkl, ASSIGNED , RFE: disable "Zoom Out" button in corner [17:10] you could always turn it on if that functionality gets backported, but i dont think theres going to be any backports anymore [17:10] Plasma API is *broken* now :) [17:10] And once it's fixed, it'll still be backwards-incompatible. [17:10] yeah [17:10] And backports are going to be less and less useful the closer 4.1 will come. [17:10] ok, I see/hear no objections, so let's "just do it". [17:10] +1 [17:11] +1 [17:11] as an observer with no authority i'd say +1 :) [17:12] alright, let's move on then. [17:12] *** rdieter sets the channel topic to "KDE-SIG Meeting -- http://fedoraproject.org/wiki/SIGs/KDE/Meetings/2008-04-22 -- https://bugzilla.redhat.com/show_bug.cgi?id=443610". [17:12] topic 3: https://bugzilla.redhat.com/show_bug.cgi?id=443610 [17:12] Bug 443610: low, low, ---, Lukas Tinkl, ASSIGNED , RFE: disable "Zoom Out" button in corner [17:12] oops [17:13] https://bugzilla.redhat.com/show_bug.cgi?id=443320 [17:13] Bug 443320: low, low, ---, X/OpenGL Maintenance List, ASSIGNED , Cannot enter keyboard input into kdm after logout [17:13] *** rdieter sets the channel topic to "KDE-SIG Meeting -- http://fedoraproject.org/wiki/SIGs/KDE/Meetings/2008-04-22 -- https://bugzilla.redhat.com/show_bug.cgi?id=443320". [17:13] *** topic 3 has been marked as a duplicate of topic 2 ;-) [17:13] just wanted to raise awareness here, looks bad. [17:13] --> J5 has joined this channel (n=quintice@nat/redhat/x-fe59c34b1bb94dfd). [17:14] That KDM/keyboard bug is weird. [17:14] I've seen that -- as I said in the bug, it looks like hitting ctrl-C once I'm logged in restarts X and all is good. [17:14] any brainstorm ideas on ways we can help debug this? [17:14] (I'm using the live image so can log in w/o password) [17:14] Ctrl-C shouldn't be restarting X... [17:14] Yeah, no kidding!! [17:14] Looks like somehow the input goes to the terminal, not X11. [17:15] not sure, can't switch to the console to confirm tho. :) [17:15] And X11 doesn't trap Ctrl-C because it normally handles keyboard events itself. [17:15] I only discovered ctrl-C by accident. I don't know if it has an effect in KDM too. [17:15] (Might be a red herring ...) [17:15] I may try using gdm to see if the problem goes away or not. ?? [17:16] Normally, Ctrl-C in a GUI context copies the selection to the clipboard. [17:16] <-- hansg has left this server ("Leaving"). [17:17] --> ezq_ has joined this channel (n=ezq@host198.190-31-29.telecom.net.ar). [17:17] I can test post-meeting to see whether I'm making this ctrl-C thing up or not, but I'm 99% confident it was reproduceable. [17:18] mefoster: thx [17:19] well, in the meantime, if we can nudge, bribe your local congressman, legislator, QA member, X maintainer, etc, the support would be appreciated. [17:19] moving on... [17:19] *** rdieter sets the channel topic to "KDE-SIG Meeting -- http://fedoraproject.org/wiki/SIGs/KDE/Meetings/2008-04-22 -- Open Discussion". [17:19] --> ltinkl_ has joined this channel (n=ltinkl@82.100.47.250). [17:19] that's it for the agenda, open discussion. [17:20] <-- ltinkl has left this server (Nick collision from services.). [17:20] Now that the mass branch has happened, are we going to start importing 4.1 to F10? [17:20] *** ltinkl_ is now known as ltinkl. [17:20] <-- ezq_ has left this server (Client Quit). [17:20] Kevin_Kofler: good question. [17:20] i have a question (I don't really know if some else asked the same).. what about making split packages for individual sub applications in kde 4.x ? [17:20] imo, yes, we should do so at earliest convenience. [17:20] The latest snapshot appears to be 4.0.70: http://gd.tuwien.ac.at/kde/unstable/4.0.70/src/ [17:21] lvillani: that's a FAQ, sure, want to help with all the extra work to make it happen? :) [17:21] heh, it would be nice to do so [17:21] :) [17:21] lvillani: that's a lot of work indeed :) [17:21] <-- JSchmitt has left this server ("Konversation terminated!"). [17:21] because, all kidding aside, it's a *lot* of work. [17:21] Split packages are going to multiply the maintenance workload by at least a factor of 5. :-( [17:22] So, the status-quo is that we've only considered doing so in cases where the payoff is significant. [17:22] lvillani: instead of suggesting doing so wholesale, do you have concrete examples where pkg split would be largely beneficial? [17:23] and "would be nice" doesn't count. :) [17:23] mhh let me think... [17:24] lvillani: and, ever wonder why upstream kde doesn't release things split already? (hint, part of our motivation for status-quo is that we're following upstream here) [17:25] <-- viking-ice has left this server ("Ex-Chat"). [17:25] lvillani: well, we don't need an answer now, but if you have good ideas, feel free to bring them up anytime (here, #fedora-kde, or report RFE to bugzilla.redhat.com) [17:25] rdieter, I think that kde modules are just a way to categorize a certain set of applications and libraries [17:26] lvillani: yeah, that's part of it, monolithic tarballs have pros and cons, a serious con for pkg maintainers wanting split applications. [17:26] for example: kdegraphics now contains okular, gwenvie, kamera, kcolorchooser and many other [17:27] <-- ltinkl has left this server (Read error: 104 (Connection reset by peer)). [17:27] it's just a categorization (graphical applications) of independent apps [17:27] *gwenview* sorry [17:27] --> ltinkl has joined this channel (n=ltinkl@194.212.22.14). [17:28] so my question is: "why install the whole module when I want to install only gwenview because, for instance, eog sucks?" :D [17:29] counter that with: why not? (disk is cheap you know) [17:30] I understand where you're coming from, but we have to pick and choose how our time is best spent. [17:30] Split tarballs mean we have tons of packages, and usually all have their own version numbers, which I really dislike about GNOME and the new modular X11. [17:30] Kevin_Kofler: pros and cons again. :) [17:30] With KDE-style monolithic tarballs, you know that something is part of 4.0.3. [17:30] With split tarballs, assuming you want the tarball to carry the actual version of the app, you don't. [17:31] And I think you do want that, otherwise it's going to be confusing. [17:31] rdieter, "where you're coming from" (you mean debian?) [17:31] "where you're coming from" -> split packages would be nice, but... [17:31] No, it's just an idiomatic expression. [17:31] oh :) [17:32] "I see where your coming from" means approximately "I see what you mean" or "I see why you're suggesting that". [17:32] Kevin_Kofler, heh English is not my native language :) [17:32] neither ours :) [17:32] And it's spelled "I see where you're coming from" actually. ;-) [17:33] by the way, I understand your points, it was just a low low low priority RFE :) [17:33] hee [17:33] any other topics to discuss today? [17:34] you are right, in the ideal world this would be the best for users but given the current number of ppl we have, we can't afford it I'm afraid [17:34] <-- ezq has left this server (Read error: 110 (Connection timed out)). [17:34] --> kital has joined this channel (n=Joerg_Si@fedora/kital). [17:35] When importing 4.1, we'll want to skip at least kdewebdev, Quanta is still not ready. :-( [17:35] It's not in the 4.0.70 tarball at least. [17:35] quanta is going to miss 4.1 too? [17:36] If it will go in eventually, I'm ok with it missing temporarily. [17:36] but if nothing else depends on it, I'm ok with temporarily skipping it too [17:36] I don't know what state KDevelop is in, it's in the snapshots, but that doesn't mean it will be in 4.1 judging from the kdepim 4.0 experience. [17:37] We'll need kdevplatform reviewed to upgrade kdevelop, it's new and it's a dependency of KDevelop and will be one of Quanta too. [17:37] fun! [17:37] For kdewebdev, I think we should just stay with 3.5 until we have a kdewebdev 4 with Quanta. [17:38] --> SMParrish has joined this channel (n=steven@cpe-069-134-255-095.nc.res.rr.com). [17:40] ok, for now anyway. [17:40] anything else for today (or can we end early)? [17:41] For kdevelop, I suggest we upgrade it, if it's not ready we can epoch bump and downgrade, it's not like Epoch 9 or 10 is going to make that big a difference. ;-) [17:41] <-- J5 has left this server (Read error: 113 (No route to host)). [17:41] nod [17:44] has anyone looked at this packagekit bug https://bugzilla.redhat.com/show_bug.cgi?id=443233 in regards to getting a KDE icon [17:44] Bug 443233: low, low, ---, Robin Norwood, ASSIGNED , "Thinking" icon is a Gnome foot [17:44] Just seems strange to seen a gnome icon when using it [17:45] Yeah, that's why I posted the bug [17:45] what it would take to see if that icon is in the iconspec or not. If not, packagekit should switch to something that is. [17:46] glad you did because I was going to [17:46] It's an animated icon, I think ... [17:47] --> marek has joined this channel (n=pyxel@fedora/pyxel). [17:47] If it *is* in the spec, then it is oxygen simply lacking an icon. [17:47] Oxygen isn't even used for GTK+ apps. [17:47] They use either whatever gnome-settings-daemon tells them to use or whatever .gtkrc-2.0 tells them to use. [17:48] The latter is just "gnome" as a generic fallback. [17:48] arg, all the xsettings crud again. [17:49] Possible relevant mailing-list thread (haven't read through it): http://lists.freedesktop.org/archives/xdg/2007-July/008555.html [17:50] getting xsettings-kde working under kde4 would be a start. [17:50] But the icons would also have to be actually added to Oxygen. [17:51] The xsettings issue is just part of it, the other half of the problem is that GNOME and KDE both have additional icons compared to the naming spec. [17:52] Right, both problems need effort to solve. [17:53] gnome isn't the only guilty party here, there's a lot of kde-specific stuff still used in kde4 and oxygen. [17:53] The problem with solving it is that both GNOME and KDE will be reluctant to add icons to their themes which their desktop isn't even using. [17:54] Even if it is in the spec. For example there's no edit-find-replace in Oxygen. [17:54] I think both sides would be ok with supporting the existing spec, and would agree that not doing so would be considered a bug worth fixing. [17:54] Then maybe a feddora icon or something generic, just not a gnome foot [17:55] Honestly, I don't think this is a blocker and I also don't think we'll have a good solution for this problem in time for F9. [17:55] SMParrish: that's all dependant on the icon-theme. (gtk's fallback theme in this case) [17:55] Kevin_Kofler: +1 [17:55] <-- dstarh has left this server ("Leaving"). [17:56] Yeah, it's more WTF than an actual problem [17:56] mefoster: nod [17:56] * SMParrish agrees [17:57] --> d_star_h has joined this channel (n=d_starh_@216.177.206.254). [17:57] I've hinted at it before, but I'll get more serous soon... kde users should try using gnome-icon-theme, and gnome users try using oxygen-icon-theme, and everyone help report/fix the bugs. [17:57] <-- d_star_h has left this channel ("Leaving"). [17:57] --> delero has joined this channel (n=denis@nat/sun/x-9fdc837b1dbcc536). [17:58] or something even more crazy like making a common icon-theme that all DE's can use. [17:58] both are frought with peril [17:58] Isn't that what Echo is supposed to be about? [17:58] or bluecurve? [17:59] Unfortunately, Echo is probably seriously broken in KDE. :-( [17:59] Bluecurve has the added advantage of working properly in KDE 3 too. [17:59] I fixed it up for KDE 4, so it shouldn't be completely broken. [17:59] But unfortunately people don't like it because they say it looks "outdated". [18:00] right, echo is *still* horribly broken kde-wise. folks have reported bugs, but without any kde-background/experience from folks working on echo, fixes have been glacially slow in coming [18:00] --> hansg has joined this channel (n=hans@ip32-174-211-87.adsl2.versatel.nl). [18:00] It's also missing some icons it should have for KDE 4, like edit-select-all. [18:00] (It = Bluecurve, dunno about Echo) [18:01] well, time's up folks, I *think* fpc is meeting today. [18:01] KDE SIG meeting end