17:34:41 #startmeeting 17:34:41 Meeting started Wed Oct 17 17:34:41 2012 UTC. The chair is tittiatcoke. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:34:41 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:35:11 #meetingtopic Welcome to the openSUSE KDE community IRC meeting! Please wait with other discussion until the meeting is over. This meeting is logged. 17:35:32 Meeting topics for tonight are: 17:35:45 old action items 17:35:50 status report 17:36:13 KDE Improvements 17:36:23 Do we prefer now inlne patch-tags vs the old KDE patch annotaion policy 17:36:28 Bug Handling 17:36:37 Bug squashing session 17:36:46 Q&A, misc 17:37:00 anything else ? 17:37:42 #topic old action items 17:38:07 Action for all: Check/Validate the Team tasklist 17:38:17 Have to admit that I didn't do anything on this one. 17:38:49 ctrippe, alin, einar77_work, tigerfoot ? 17:38:55 cb400f: ? 17:39:19 hm, nope.. I added some ideas to the idea page 17:39:32 Ok. That is the third agenda point :-) 17:39:52 I've added a few things to the page, but there is more work to be done 17:39:57 Ok. 17:40:00 tittiatcoke: not that much to add, except we will miss you at Praha :-) 17:40:08 :-) 17:40:09 Quite a few things are alo outdated 17:40:29 ok. Let's keep it on the action list for the next meeting. Have to look at it properly 17:40:47 #action all Check/Validate the Team tasklist 17:41:07 Action 3: NicoK send a list of packages in KR49 to tittiatcoke that needs working on. 17:41:42 Part of this was resolved with the update to 4.9.2. At least all the KDE packages are now properly linked to the packages in KDF and KDF is the main development repo again :-) 17:42:01 does someone have a link to the task list? 17:42:11 cb400f: http://en.opensuse.org/openSUSE:KDE_Meeting_20120926 17:42:26 Action 4: tittiatcoke contact the maintenance team to discuss the possiblity to provide KDE point releases throught the maintenance workflow 17:43:50 I have good news here. The response from the maintenance team was very positive and they are fine with providing minor KDE updates through the maintenance channel. This means that for 12.3, we could ship it with 4.10.0 and then have updates to 4.10.1, etc through the standard maintenance channel. So KRxy would be fully replacing KDS. 17:44:03 tittiatcoke: here I am 17:45:12 This is then for the main KDE packages. I would propose that bugfixes for KDE related packages (e.g. amarok, etc) are done in the same way. Starting from KRxy. Having updates from KUA could mean a major update instead of just bugfixes. 17:45:54 won't KRxy have major updates of non-SC apps too? 17:46:25 I agree, however this means no major updated in KRxy IMHO 17:46:37 cb400f: If that would happen, then it means that with a bugfix the package has to be branched seperately then. 17:46:52 ok 17:47:06 cb400f: But wouldn't we utilize KUA for major updates for non-SC apps ? 17:47:45 I certainly think that's the best approach 17:49:10 Ok. So we provide minor KDE updates in KRxy and moving this forward through the maintenance channel for the respective distro. Major updates for non-SC apps are provided through KUA. bugfixes for non-sc apps are provided in KRxy and then send through the maintenance channel. 17:49:27 Hi all, I'm here for the meeting. 17:49:45 Has it started yet? 17:49:56 Solaris444: Yes, we are in the old action items. 17:50:02 Ah ok. 17:50:07 Old action items including? 17:50:20 everybody aligned on the maintenance update procedure ? 17:50:34 tittiatcoke: yap 17:50:39 Solaris444: summary of last meeting: http://en.opensuse.org/openSUSE:KDE_Meeting_20120926 17:50:50 Thankyou. 17:51:07 OK, up to date. 17:51:33 tittiatcoke: yes 17:52:28 #decision minor KDE:SC release updates and bugfixes for non-SC packages will be done in KRxy repo and then forwarded to the maintenance channel for distro updates. Major updates for non-SC packages are provided through KUA. 17:52:45 action: tittiatcoke check with coolo the release calendar for 12.3 and when the freeze would be 17:53:20 I noticed that there was some discussion around the release calendar, but didn't had the time to follow up on this one. Will come back on this on the next meeting 17:53:29 #info postponed for the next meeting 17:53:42 action: tittiatcoke create a wiki page to list the items we need to do and create metabugs to used to list/tracke the ship-block bugs and nice-to-have bugs. 17:53:42 no decision yet afaik.. will be discussed at the conf 17:53:48 cb400f: Ok :-) 17:54:05 but I don't think the conf will even make the final decision.. there'll prolly be another discussion on -factory after that 17:54:15 * cb400f wants to stick with 8 months 17:54:16 Most likely :-) 17:54:37 This action point is part of the agenda. Wiki page was created 17:54:43 lots of tumbleweed conspirators are arguing for 12 months 17:54:55 :-) To make live easier for them 17:55:17 The action item regarding calligra was already resolved during the meeting. 17:55:35 That were the old action items. so lets move to the status reports 17:55:41 #topic Status reports 17:55:55 and up-to-date calligra is now in KUA :-) 17:56:03 :-) 17:56:07 yet to check if krita will run now 17:56:15 Status reports is only for existing work in progress right? 17:56:20 From my side, I can report that KR49, KDF and Factory are now having KDE 4.9.2 17:56:21 Apologies, this is my first meeting. 17:56:40 Solaris444: Status reports are related to whatever was done since the last meeting. 17:56:53 OK, thankyou. 17:57:20 Also I have pushed a new update into KUSC, which was published for 12.2 but for factory it is not building that fast :-( 17:57:37 Any other status reports ? 17:57:38 I have pushed a few online updates for 12.2 17:58:37 Ok 17:59:18 anything else ? 17:59:48 Ok. Lets move then to the next agenda item 17:59:55 #topic KDE Improvements 18:00:06 I have two issues to mention. 18:00:09 The list is on http://en.opensuse.org/KDE/KDE_improvements 18:00:26 Solaris444: go ahead 18:01:02 Thank you. In both 12.1 and 12.2, there are two glaring issues. Firstly, when KDE users try to log in, their first attempt almost always fails. 18:01:40 This really isn't good considering it is the first thing a user is going to do. 18:01:41 https://bugzilla.novell.com/show_bug.cgi?id=728554 18:01:48 openSUSE bug 728554 in openSUSE 12.2 (Other) "first login attempt after boot always fails" [Critical,New] 18:02:07 the meetings are not for discussing individual bugs 18:02:20 aren't those issues specific to the nouveau driver? 18:02:24 No. 18:02:37 .. never happened to me, but I've heard it a lot 18:02:48 I get the same with the radeonHD driver. 18:02:51 (I'm on intel gfx) 18:02:59 radeonhd is looooong dead 18:03:06 ok, well the radeon drivers. 18:03:14 Whichever the current open source drivers are. 18:03:21 Included in the distro. 18:04:03 In any case, my point was that the two first things the user tries to do 1) eject the install disc and 2) log in, do not work properly. 18:04:07 And have not for some time. 18:04:37 Solaris444: cb400f is correct. Discussing of bugreports should happen in the Q&A session at the end of the meeting 18:04:47 OK, I will wait until then. 18:04:53 Solaris444: Thanks :-) 18:05:04 Ok. Back the KDE Improvement lists. 18:05:31 Seems to be nicely growing with some good things there. 18:05:58 Who asked for the SFLPhone stuff ? 18:07:27 me 18:08:05 it seems like a decent skype alternative.. although they don't seem to have versions for OSX and MS Windows :-/ 18:08:20 not sure how good telepathy works as a sip client 18:09:13 cb400f: it seems that the KDE client of sflphone is seeing some developments and is hosted now on kde git. Which is good. Unfortunately I don't have any experience with either Skype nor Sflphone nor telepathy as SIP client. 18:09:27 At this moment I wouldn't put too much hope on telepathy as sip client :-) 18:09:37 that's what I thought ;-) 18:09:55 It would be helpful not to have to use pidgin 18:09:58 and since a commercial company is developing stuff in kde git I thought it'd be nice to support them a little bit 18:10:04 It doesn't get much attention from the dev these days. 18:10:22 Plus of course it's GTK and not QT 18:10:27 Ok. I will try to contact the maintainer of the common sflphone package to see if he/she is willing to push it to Factory. Then we can package the kde client 18:10:36 So Telepathy would make a nice replacement for it if it is functional. 18:10:52 Comments on stability of Telepathy? 18:11:36 Solaris444: I am running latest git of Telepathy and for normal chats it is quite stable and functional. Bad thing is that it still depends on gstreamer-0_10 18:12:16 Ah. Is there a move to change that? 18:12:45 Solaris444: Not at the moment. 18:12:48 alin: any news on that ? 18:13:27 didn't todd decide to drop the component needing gstreamer? 18:13:58 iirc only some non-critical component needed the nasty gstreamer stuff 18:14:11 cb400f: Yeah. That was the ktp-call-ui 18:14:46 Presumably this won't be removed in time for 12.3 though? 18:15:13 yay, krita from kua starts 18:15:52 cb400f: Good :-) 18:16:08 so at least we have a workaround for 12.2 users who need krita 18:16:22 Solaris444: KDE-Telepathy is not yet part of the distro at the moment 18:17:05 Ok. For the next meeting I would like to ask volunteers for each item on this Improvement list :-) 18:17:20 cb400f: I have a professional illustrator of children's books using Krita. I assume I can't update her to 12.2 for the time being? 18:17:52 cb400f: actually it wasn't a krita bug but an opengtl one 18:18:08 krita 2.4.x from the official distro segfaults on start... but she'd prolly want nice krita 2.5.2 from KUA anyway ;-) 18:18:35 Thanks. 18:19:17 cb400f: no see https://bugzilla.novell.com/show_bug.cgi?id=778260 which was fixed by adra, otherwise please reopen the bug 18:19:19 crap! 18:19:21 openSUSE bug 778260 in openSUSE 12.2 (KDE4 Applications) "Krita crashes during start" [Major,Resolved: fixed] 18:19:25 I forgot about the meeting! 18:19:33 einar77: :-) 18:19:34 but I think we should go on with the meeting 18:19:38 oh, was the patch shipped? 18:19:39 More people forgot about it 18:19:50 ctrippe: Yup :-) 18:19:57 There is now an updated opengtl package for 12.2 18:20:19 We're stil on KDE improvements? 18:20:23 awesome, hadn't noticed 18:21:04 #action all Assign yourself to the items on the Improvement list that you will take care off. 18:21:21 Ok. Lets move to the next agenda item. 18:21:43 #topic inlne patch-tags vs the old KDE patch annotaion policy 18:21:50 ctrippe: This is your point :-) 18:21:53 That's from me. 18:22:05 WHat's the main difference between the two policies? Got some examples? 18:22:24 tittiatcoke: yes... sorry I was away... atthe moment things are not ported to the new gstreamer... 18:22:30 alin: Ok 18:22:36 Will once told me that KDE would use the KDE patch annotation policy from http://en.opensuse.org/openSUSE:KDE_Patch_Annotation_Policy 18:22:58 However the in spec tags now seem to be the opensuse standard 18:23:03 tittiatcoke: as the two 0_10 and 1.0 supposed to run in parallel shall be no problem once we fix the farstream issues... 18:23:07 but 12.3 will have both gstreamer versions, right? 18:23:14 yes 18:23:18 since afaik phonon isn't ported either 18:23:24 cb400f: which will create a mess 18:23:27 cb400f: This might come sooner 18:23:40 gstreamer = mess... 2x gstreamer = 2x mess 18:23:44 ctrippe: do you have a link to an openSUSE package with the spec tags? 18:23:59 * einar77 used the KDE annotation policy atm 18:24:39 cb400f: unfortunately in streamer case a and b != a+b but a+b+(a,b) 18:24:52 alin: Please take that one offline :-) We are on a new agenda item 18:25:53 ctrippe: I believe that the KDE annotation policy is moving all the documentation to the patch-file itself, while the openSUSE policy brings it back into the spec-file. Am I correct ? 18:26:05 tittiatcoke: yes 18:26:29 ANd to be honest I havened seen many patches really using this policy lately 18:26:38 Unfortunately Will isn't in the meeting. Guess he also forgot :-) 18:26:44 ctrippe: Which policy ? 18:27:13 tittiatcoke: To use tags in the patch 18:27:25 tittiatcoke: speak of the devil 18:27:43 One of the reasons I guess is that they are easily removed when using quilt 18:27:44 wstephenson: ping 18:27:59 pong 18:28:01 I think I've seen one made like that, but 18:28:05 wstephenson: Welcome to the meeting :-) 18:28:08 sorry, couldn't make it earlier 18:28:12 ctrippe: how are those generated? 18:28:39 wstephenson: We are just talking about the policy for annotation of patches. If we follow the KDE one or the openSUSE one 18:29:30 wstephenson: What would be your preference ? 18:29:47 tittiatcoke: personally i prefer the kde one. it's technically better 18:30:09 otoh the other one has established itself as a de facto 'standard' within the project 18:30:31 even if it was just because prusnak called it a standard 18:30:44 :-) Well at lot of people are now using it 18:31:04 we can call the kde one kernel standard if you want to feel better about it 18:31:05 yes 18:31:12 and there is tooling for it 18:32:07 wstephenson: But what stops us to combine both policies ? the openSUSE one indicates the usage of certain terminology in the spec-file, while the KDE one puts a lot of information in the patch file itself 18:32:31 Question is only if tools like quilt are used, is that information kept with the new patch or not ? 18:33:13 wstephenson: what kind of tools? 18:34:44 einar77: spec-file-cleaner 18:34:52 oh, right, now I remember 18:35:09 tittiatcoke: nothing! :) 18:36:21 Then let's combine it and provide as much info as possible. Maybe it would be good to make a kind of empty patchfile with the tags in the right place ? 18:36:29 +1 18:37:04 Everyone agrees ? 18:37:22 +1 18:37:27 +1 18:37:53 tittiatcoke there is no "-1", so everyone agrees :) 18:38:01 #decision KDE packages will combine the openSUSE and KDE patch annotation policies to provide optimal information. 18:38:13 it would be easy to script a patch-formatter to add the kde standard headers when we add a patch 18:38:27 wstephenson: Interested to create one ? 18:38:39 i have a python app somewhere that does it 18:39:06 wstephenson: :-) That sounds like you just volunteerd :-) 18:39:14 wstephenson: if you don't have time, send it my way and I can help 18:39:39 #action wstephenson einar77 create a patch-formatter to add the kde standard headers. 18:39:48 it does a bunch of other now useless stuff too (graphically cherrypicking commits from svn branches) 18:40:20 wstephenson: I leave it up to you what you want to keep in that formatter :-) 18:40:51 Ok. next agenda item. 18:41:04 #topic Bug handling 18:41:11 ctrippe: Again your item :-) 18:42:06 At the moment not too many people are looking at bnc for KDE bugs and most of the packages in KDF have kdemaintainer@suse as bugowner 18:42:44 What is the net result of that ctrippe? 18:42:45 I think it ould be useful if we would create a list of the KDF packages with one or two people feeling resopnsible for it 18:43:15 Maybe that would make it a bit less of a black hole 18:43:30 +1 18:44:03 wstephenson: is there anybody behind kdemaintainer@suse.com ? 18:44:24 To summarize the idea would be, that not everyone has to follow all KDE bug reports, but the people doing this, e.g. myself can assign or take the hopefully knowledgable person into CC 18:44:38 tittiatcoke: yes, it's manually maintained alias on our mailserver 18:44:45 basically all the old suse kde team 18:44:52 ctrippe: +1 18:45:30 ctrippe: that's a job that is a recipe for burnout, mind. 18:46:18 wstephenson: I know 18:46:27 seen it happen to a bunch of upstream bko guys 18:47:02 ctrippe: would it make sense to make the people "responsible" bugowners, or would it be too much? 18:47:17 wstephenson: any suggestion ? 18:47:46 at least it might be good to have someone to point out the important bugs and the easily fixable suse specific ones 18:47:55 like e.g. the krita crash 18:48:06 so those don't get lost 18:48:06 somehow I feel more for keeping the alias, but to extend the alias with the full community team 18:48:24 tittiatcoke: a possibility 18:48:33 tittiatcoke: the problem with having too many people on a big job is nobody feels responsible 18:48:41 wstephenson: true 18:49:05 tittiatcoke: that can easily be achieved by everyone via following kdemaintainers in bugzilla 18:49:06 wstephenson: can more than one bugowner be set for a specific package? 18:49:31 An alternative could be is to discuss the new bug reports during the team meeting and then to assign a person to it. 18:49:45 tittiatcoke: That are too many 18:50:07 einar77: not sure 18:50:13 Especially at the bnc-screenign team assignes every bug which mentions KDE to us :( 18:50:29 Even for gnome apps 18:50:51 tittiatcoke: that would take forever during meetings and limit it to people who come to meetings... 18:51:17 we went through a few models with this in the kde team, when we still tried to care about all the bugs 18:51:27 eg having a rotating 'bug tsar' every week 18:51:40 Ok 18:51:52 or having queries that partition incoming bugs 18:52:08 eg "will takes all the bug numbers ending in 1,2,3" etc 18:53:10 i think a solution which could work is one which doesn't try to be perfect 18:53:16 :-) 18:53:56 but try to give all bugs a quick look at least 18:54:17 wstephenson: +1 18:54:38 i don't have a solution for this though :( 18:54:38 Ok. I would suggest that we take this as an action item for the next meeting. So that everybody can think about a good solution that works :-) 18:55:08 another thing we need to do is participate in the project bugzilla redesign process 18:55:24 so that delivers a system that meets this team's needs 18:55:32 wstephenson: Can you enlighten us on that one ? 18:55:54 discussions are underway to get a separate suse+opensuse bugzilla instance that we administer 18:56:20 with fine-grained product/components 18:56:24 I see. 18:56:34 i started a thread about it on -project 18:57:12 That would make our current discusion even more important. As that we would need to give the right input 18:57:27 exactly 18:57:58 Any deadlines known for that new instance ? 18:58:08 not afaik 18:58:15 Ok 18:58:56 i'm not sure what the state of the discussion is atm, there might be a BoF at osc12 18:59:03 Then let's think about this topic and discuss this further in the next meeting. I don't think that we are coming up with the right input this evening. 18:59:10 wstephenson: Ok. 18:59:13 ok 18:59:23 tigerfoot: As you will be at osc12, can you keep an eye on that ? 19:00:05 #action all Think about the current bug reporting/solving process and how it could be improved 19:00:06 who else is going? 19:01:03 I know maxlin will be there to present the new maintenance process for KDE, but he couldn't participate in tonights meeting 19:01:06 me 19:02:30 kokeroulis: Maybe you can see if there is such a BoF and check out the discussion ? If you have the time for it of course 19:02:53 * terietor will also be in osc2012 19:03:17 ok. i will 19:03:49 kokeroulis: You might want to check with tigerfoot and terietor about their schedules. Just in case you are not able to participate. 19:04:14 at least with three people there we stand a good change that at least one could participate 19:04:34 ok 19:04:38 Thanks 19:05:24 #action kokeroulis, terietor, tigerfoot Validate if there is BoF session at osc12 regarding a new bugzilla instance for openSUSE and if possible participate. 19:05:30 Next topic. :-) 19:05:47 #topic bug squashing session for closure of 11.4 bugs. 19:05:49 That's me again :) 19:05:57 ctrippe: You are popular :-) 19:06:09 ctrippe: Wouldn't it be much easier just to close those bugs ? 19:06:11 :-) 19:06:35 How much longer is 11.4 supported for? 19:06:46 Solaris444: Supports ends on November 5 19:06:47 tittiatcoke: If we think this should be done. That would be fine for me 19:07:16 I would support the closure IMO 19:07:21 Question then. Why bother squashing bugs for a distro that's out of support in what... 3 weeks? 19:07:33 ctrippe: Just a quick thought :-) But please explain your thinking here 19:07:36 so anything valid doesn't get lost 19:08:33 Actually: There might very well be suse spefic bugs which might get lost 19:08:42 what about organizing a bug day or something to close stuff that's already fixed, or won't be fixed because things in 12.1+ changed, and keep the ones still valid? 19:08:51 For 11.3 I at least found 20-3ß bgs stillv alid for 12.1 when I cleaned them up 19:09:13 Fair enough. 19:09:35 einar77: yes, that was actually my intention. I only thought the end of 11.4 would be good timing for this 19:09:36 A bug day sounds good. einar77 Interested in organizing it ? 19:10:11 We have some wiki packages already explaining the todos 19:10:43 tittiatcoke: I fear I might not be able to be around to actually help, as weekends are mostly off-limits for most stuff 19:11:02 I could help with collateral such as announcements, blog posts etc, though 19:11:04 actually cwh was supposed to be organising one before we got stuck with 12.2 release publicity 19:11:23 so i should be able to get some opensuse team time on it, during the week 19:11:24 einar77: That would be more than sufficient already :-) 19:11:30 I am also mostly available in the evening during the week 19:11:58 I guess we don't have to necessarily do it during one day. We could also agree on a longer period 19:12:04 I would prepare the wiki pages which were used for the last KDE specific bug sessions 19:12:51 ok. May I then assign the action of organizing the bug squashing period to ctrippe and einar77 ? 19:13:16 tittiatcoke: let's say yes for now, I hope I can keep up 19:13:18 Fine for me. 19:13:50 #action einar77, ctrippe Organize a bug squashing for the KDE bugs in 11.4. 19:14:25 As that there were no more agenda items, I would like to move to the Q&A, Misc part. 19:14:34 #topic Q&A, Misc 19:14:49 Solaris444: You had to wait so long for it, so I would say go ahead with your two bug reports :-) 19:14:54 THankyou 19:14:55 :) 19:15:20 OK well, there are two issues that have been in the last two releases that I don't think should have ever made it into final in either version. 19:15:45 Which two issues ? 19:15:50 Firstly, users are unable to eject optical discs via the GUI without the tray automatically reclosing. 19:16:02 https://bugzilla.novell.com/show_bug.cgi?id=659153 19:16:04 I think the login issue is related to typing too fast 19:16:07 openSUSE bug 659153 in openSUSE 12.2 (KDE4 Workspace) "Ejecting Optical Drives Causes Immediate Re-Close of Tray and KNotify Crash" [Critical,Reopened] 19:16:33 KNotify no longer crashes, and the issue was briefly fixed in one of the 12.2 milestones, but then reappeared in the release candidate I think. 19:16:46 I have been logging into kde succesfully from kdm a million times on 12.1 and 12.2.. but if I type to fast initially for some strange reason keypresses get lost 19:16:49 It's been in for nearly 2 years. 19:17:04 I'll get to that one cb400f 19:17:30 It seems to me that it is a basic point of functionality that ejecting optical drives should work. 19:18:01 That's the first one. 19:18:16 Solaris444: to be honest I can't see this in current master 19:18:26 einar77: It is there. I assure you. 19:18:37 On every system I have tested. 19:18:42 Intel, AMD... 19:18:46 Solaris444: Which KDE version ? 19:18:53 Solaris444: I'm not using released code 19:18:58 The one that ships with release. 19:19:09 wasn't the cd issue isolated to udisks? 19:19:10 So 4.8.5 at the current time. 19:19:40 maybe it'll be fixed with udisks2 19:19:42 sysctl dev.cdrom.autoclose 19:19:47 12.3 will use udisks2 indeed 19:19:58 But it was dependent on another bug as well. 19:20:09 fedora did it and tittiatcoke made it build 19:20:23 Surely it can be fixed in the current release though? Considering it was fixed for a period of time and then reappeared? 19:20:36 Perhaps somebody accidentally reverted something? 19:21:27 Solaris444: I will check with cartman to see what the issue is with it and why it got back in again during the final 12.2. Let's prevent it from popping up again for 12.3 19:21:36 Indeed. 19:21:40 OK, second bug. 19:21:42 The login issue. 19:21:51 login issues being? 19:22:03 https://bugzilla.novell.com/show_bug.cgi?id=728554 19:22:08 The first login attempt almost always fails when using KDE einar77. 19:22:08 openSUSE bug 728554 in openSUSE 12.2 (Other) "first login attempt after boot always fails" [Critical,New] 19:22:16 I get that too.. I have to type sloooow at kdm 19:22:30 #action tittiatcoke check with cartman with regards to bug #659153 19:22:30 openSUSE bug 659153 in openSUSE 12.2 (KDE4 Workspace) "Ejecting Optical Drives Causes Immediate Re-Close of Tray and KNotify Crash" [Critical,Reopened] https://bugzilla.novell.com/659153 19:22:32 but it's become a habit.. so I don't even think about it anymore 19:22:40 Right. It may not be specifically related to typing speed though. 19:23:21 * tigerfoot sorry feeding bags with stuff for osc ... but will keep an eyes on the bof about bugzilla 19:23:23 something is clearly fscked up... but if I wait about 2-3 seconds between char 1 and char 2, there's no problem 19:23:24 Henryk mentions that the keypresses are being read. 19:23:36 And looked up. 19:23:40 But then dropped somewhere after that. 19:23:53 And that the problem doesn't occur with the default them. 19:23:55 *theme 19:24:02 Only with the SUSE theme. 19:24:14 ah, well that's useful info 19:24:27 Assuming my understanding is correct anyway. 19:24:59 what's the status of lightdm and qml kdm themes and whatnot? 19:25:11 cb400f: kdm is unmaintained, period 19:25:38 my bets would be to evaluate lightdm and its kde greeter 19:25:44 any chance lightdm will be ready for 12.3? 19:25:45 ah 19:25:55 cb400f: I use it daily currently 19:26:04 but I don't use any fancy auth method 19:26:12 einar, does it display a clickable user list? 19:26:25 cb400f: There is a kde theme for lightdm available. einar77, alin and myself are using lightdm with good results. It seems that it can work also without consolekit, but at the moment the KDE theme requires a higher version of lightdm 19:26:26 Solaris444: one of the themes, yes 19:26:46 there's a bug being worked on for icons 19:27:07 tittiatcoke: do you know if it has all the fancy "enterprise" features like ActiveDirectory login and all that nasty crapola 19:27:20 cb400f: it should be handled either by plugisn or by something underneath 19:27:29 it needs a patch to work with systemd without consolekit 19:27:36 we'll see once the new systemd hits factory 19:27:42 ok folks, time for me to go off 19:27:48 I'll check the rest of the meeting notes in the ML 19:27:50 see you! 19:27:58 Thanks 19:28:40 thx einar77 .. 19:28:49 cb400f: Don't know. Have to check that one. But this is more for lightdm then the greeter 19:28:54 It's about time for me to go too, but I would like to point out that for a desktop distro, these kinds of bugs that affect the experience of every user really should take highest priority. 19:29:33 Not being able to login or eject cds are pretty big oopses for a PC. 19:29:50 Not so crucial for a headless server running SSH. 19:30:00 But definitely for a desktop distro. 19:30:34 no one is unable to do those things.. there are just some minor annoyances 19:30:52 like typing slower... and pressing the hardware eject button instead of clicking the mouse 19:31:47