14:02:32 <rdieter> #startmeeting kde-sig -- https://fedoraproject.org/wiki/SIGs/KDE/Meetings/2010-02-23
14:02:32 <zodbot> Meeting started Tue Feb 23 14:02:32 2010 UTC.  The chair is rdieter. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:02:34 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
14:02:55 <rdieter> #chair Kevin_Kofler jreznik than svahl
14:02:56 <zodbot> Current chairs: Kevin_Kofler jreznik rdieter svahl than
14:03:03 <rdieter> #topic roll call
14:03:11 <rdieter> #meetingname kde-sig
14:03:12 <zodbot> The meeting name has been set to 'kde-sig'
14:03:19 <rdieter> who's present today?
14:03:35 <svahl> present
14:03:41 * jreznik is here
14:03:43 <Kevin_Kofler> Present.
14:03:47 <than> present
14:03:50 * ltinkl present
14:04:23 <rdieter> SMParrish_mobile: ping (hi)
14:04:50 <rdieter> ok, let's get rolling.
14:04:58 <rdieter> #topic agenda
14:05:11 <rdieter> anything to add to today's agenda?
14:05:50 <svahl> .bug 549687
14:05:52 <svahl> ?
14:05:52 <buggbot> Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=549687 medium, low, ---, jmccann, NEW, kdm: no autologin on first start
14:05:53 <zodbot> svahl: Bug 549687 kdm: no autologin on first start - https://bugzilla.redhat.com/show_bug.cgi?id=549687
14:05:55 <buggbot> Bug 549687: medium, low, ---, jmccann, NEW, kdm: no autologin on first start
14:06:41 <rdieter> sigh, yeah, still no word on that?
14:07:38 <SMParrish_mobile> I'm here
14:07:38 <killefiz> i'm still seeing "only 2nd login works in kdem" on f13 - that's related isn't it?
14:08:05 <rdieter> killefiz: that's the same issue
14:08:19 <Kevin_Kofler> There's also https://bugzilla.redhat.com/show_bug.cgi?id=566547
14:08:20 <buggbot> Bug 566547: medium, low, ---, tgl, ON_QA, mysql-5.1.43 incompat with akonadi
14:08:42 <Kevin_Kofler> I added this to the F13Alpha blocker (Oxf13 said I should add it to the blocker).
14:08:57 <Kevin_Kofler> Akonadi is quite screwed with the MySQL currently in F13 Alpha. :-(
14:09:27 <Kevin_Kofler> Or I should say, it doesn't work at all.
14:10:22 <than> Kevin_Kofler: does Akonadi work again with the fix (revert change)?
14:10:51 <rdieter> than: yes
14:10:57 <rdieter> ok, let's get started
14:11:07 <rdieter> #topic KDE-4.4.0 updates status, remaining blockers?
14:11:34 <Kevin_Kofler> .bug kde-4.4
14:11:34 <zodbot> Kevin_Kofler: Error: 'kde-4.4' is not a valid integer.
14:11:34 <rdieter> anything blocker-worthy keeping from us pushing kde-4.4.0 to stable updates?
14:11:39 <Kevin_Kofler> Hmmmph…
14:11:41 <Oxf13> Kevin_Kofler: we're going to need an RC3 so I can be sure to grab that build you need
14:11:59 <Kevin_Kofler> Oxf13: mysql-5.1.44-2.fc13 has the fix.
14:12:11 <Oxf13> did you mention that in the bug?
14:12:29 <Kevin_Kofler> It's already mentioned there.
14:12:41 <jreznik> .bug 533921
14:12:41 <Kevin_Kofler> (Automated Bodhi comments among other things.)
14:12:42 <buggbot> Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=533921 medium, low, ---, rdieter, NEW, kde-4.4 tracker
14:12:45 <zodbot> jreznik: Bug 533921 kde-4.4 tracker - https://bugzilla.redhat.com/show_bug.cgi?id=533921
14:12:47 <buggbot> Bug 533921: medium, low, ---, rdieter, NEW, kde-4.4 tracker
14:13:29 <Oxf13> on the subject of 4.4.0 updates, we brought Till Mass into the releng group to help with tag requests in the europe timezones
14:13:34 <Kevin_Kofler> https://bugzilla.redhat.com/showdependencytree.cgi?id=533921&hide_resolved=1
14:13:40 <Oxf13> that should hopefully delay the lag you've seen in getting stuff done
14:13:58 <rdieter> Oxf13: yay, kudos to till, he's done a great job already.
14:14:10 <Kevin_Kofler> So this is the list of unsolved 4.4 regressions. :-(
14:15:19 <rdieter> a few annoyances, not sure if anything is blocker-worthy.  anyone else have an opinion?
14:15:59 <rdieter> another consideration, 4.4.1 is going to be tagged soon.  if we don't go stable very soon, it may be worth waiting for 4.4.1
14:16:30 <jreznik> rdieter: when?
14:16:35 <SMParrish_mobile> If the mysql is fixed then I don't see anything that would warrant not pushing to stable
14:16:48 <jreznik> it will took some days to import it and rebuild...
14:16:51 <rdieter> February 25th, 2010: Tag KDE 4.4.1
14:17:08 <rdieter> per http://techbase.kde.org/Schedules/KDE4/4.4_Release_Schedule
14:17:14 <than> rdieter: mysql is the critical one for me
14:17:37 <than> when it's fixed, i don't see why we cannot move 4.4.0 to stable
14:17:37 <rdieter> good point, we have to block on mysql
14:17:51 <Kevin_Kofler> We don't.
14:17:57 <Kevin_Kofler> The MySQL in F11/F12 stable is fine.
14:18:04 <Kevin_Kofler> And in testing there's already a fixed build now.
14:18:13 <rdieter> ah right! ok.
14:18:16 <Kevin_Kofler> So F11/F12 is no longer affected by that regression, only F13.
14:18:21 <Kevin_Kofler> I took it off the kde-4.4 tracker
14:18:29 <SMParrish_mobile> If we wait for 4.4.1 then it would be mid march before it gets pushed to stable. That too long to make ppl wait for 4.4.x IMHO
14:18:37 <than> Kevin_Kofler: ah, we have old mysql version in F11/F12
14:18:47 <than> it's not affacted
14:18:54 <Kevin_Kofler> Right.
14:19:01 <Kevin_Kofler> The broken version only got up to testing.
14:19:14 <Kevin_Kofler> (except for F13 where it went in before the cutoff)
14:19:20 <than> i will say 4.4.0 is now ready for stable
14:19:25 <Kevin_Kofler> SMParrish_mobile: Not necessarily.
14:19:29 <jreznik> .bug 567350 should be fixed in 4.4.1 - aseigo reworked krunner plugins... but it's not worth to wait for this
14:19:30 <zodbot> jreznik: Error: "567350 should be fixed in 4.4.1 - aseigo reworked krunner plugins... but it's not worth to wait for this" is not a valid integer.
14:19:30 <buggbot> Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=567350 medium, low, ---, than, NEW, krunner takes 6-7 seconds to show up
14:19:55 <Kevin_Kofler> We could build 4.4.1 now, edit it in ASAP and push to stable on the 4.4.1 release day.
14:20:03 <Kevin_Kofler> But it might cause more breakage than it fixes.
14:20:09 <jreznik> Kevin_Kofler: yep
14:20:17 <than> Kevin_Kofler: +1
14:20:24 <jreznik> I prefer small steps - 4.4.0 to stable
14:20:28 <ltinkl> there might be regressions in 4.4.1, seeing the number of commits in the branch
14:20:35 <jreznik> and we don't have to hurry with 4.4.1
14:20:44 <rdieter> ok, proposal, queue 4.4.0 to stable?
14:20:45 <ltinkl> and some of them were not only bugfixes :)
14:20:47 <rdieter> asap
14:20:47 <SMParrish_mobile> jreznik: +1
14:20:51 <ltinkl> rdieter: +1
14:20:58 <rdieter> +1
14:21:03 <than> +1
14:21:08 <SMParrish_mobile> +1
14:21:13 <svahl> +1
14:21:33 <rdieter> #agreed will queue kde-4.4.0 update to stable updates asap
14:21:45 <Kevin_Kofler> What about all those unfixed regressions?
14:22:00 <Kevin_Kofler> Some of them seem quite bad to me.
14:22:09 <jreznik> Kevin_Kofler: which ones?
14:22:11 <than> Kevin_Kofler: which one
14:22:14 <Kevin_Kofler> https://bugzilla.redhat.com/show_bug.cgi?id=565410 is the worst.
14:22:15 <buggbot> Bug 565410: medium, low, ---, than, NEW, Kontact running but not showing up.
14:22:26 <Kevin_Kofler> But it seems not to be reproducible for most folks.
14:22:32 <jreznik> kontact looks worst for me
14:22:59 <Kevin_Kofler> We should also get libssh-0.4.1 finally pushed to stable.
14:23:04 <Kevin_Kofler> It has been in testing for way too long.
14:23:17 <ltinkl> kontact works fine here
14:23:18 <Kevin_Kofler> http://admin.fedoraproject.org/updates/F12/FEDORA-2010-1303
14:23:21 <Kevin_Kofler> http://admin.fedoraproject.org/updates/F11/FEDORA-2010-1644
14:23:36 <Kevin_Kofler> ltinkl: It works fine for most people, that's why it's that hard to fix.
14:23:48 <Kevin_Kofler> Oh darn, the update IDs are no longer valid.
14:23:53 <Kevin_Kofler> http://admin.fedoraproject.org/updates/libssh-0.4.1-1.fc12
14:23:55 <Kevin_Kofler> http://admin.fedoraproject.org/updates/libssh-0.4.1-1.fc11
14:24:01 <jreznik> for libssh I'll ping jfch
14:24:08 <ltinkl> Kevin_Kofler: I think dfaure fixed it in the branch
14:24:13 * ltinkl finding the commit
14:24:33 <Kevin_Kofler> ltinkl: Maybe we can get that fix in.
14:24:43 <ltinkl> http://websvn.kde.org/?view=revision&revision=1087778
14:24:49 <Kevin_Kofler> I guess we can ignore the other regressions.
14:24:55 <ltinkl> Fix the lack of akonadiserver startup when kontact is restored by session management,
14:24:56 <ltinkl> and fix the lack of a mainwindow appearing at all in some other cases (kmailpart
14:24:58 <ltinkl> waiting for akonadi forever), as discussed with Volker.
14:25:05 <ltinkl> I guess that should be it :)
14:25:06 <rdieter> anyway, all these things can and should continue being worked on, but didn't we just agree these aren't worth blocking for?
14:25:11 <Kevin_Kofler> I'm always very nervous about regressions, but we've been waiting for almost a whole month now with 4.4.0.
14:25:20 <Kevin_Kofler> We can't wait forever.
14:25:36 <ltinkl> I'll try to get the fix in today
14:25:42 <Kevin_Kofler> ltinkl: We already have that fix AFAIK.
14:25:46 <rdieter> ie, can we move on?
14:25:46 <ltinkl> ah
14:25:47 <Kevin_Kofler> It didn't help.
14:25:55 <Kevin_Kofler> Or even caused more issues.
14:26:01 <Kevin_Kofler> Hard to tell.
14:26:36 <rdieter> #topic disable kdebug by default? See also https://bugzilla.redhat.com/show_bug.cgi?id=560508
14:26:37 <buggbot> Bug 560508: low, low, ---, than, NEW, kdeinit4 is very noisy
14:26:38 <than> Kevin_Kofler: in my opinion these aren't worth blocking for 4.4.0
14:26:40 <Kevin_Kofler> http://cvs.fedoraproject.org/viewvc/rpms/kdepim/F-12/kdepim-4.4.1-kontact-startup.patch?revision=1.1&view=markup
14:27:08 <Kevin_Kofler> OK, so to conclude this, do you want me to queue 4.4.0 to stable right now?
14:27:21 <jreznik> jfch acks our request for libssh to stable
14:27:42 <rdieter> Kevin_Kofler: yep, that's what we agreed, do you disagree?
14:28:07 <Kevin_Kofler> I'm not that convinced it's a great idea, but as everyone else agrees I'll just do it. ;-)
14:28:22 <Kevin_Kofler> We still have kbluetooth 0.4.2 to build, but I guess that can go out as a separate update.
14:28:24 <rdieter> Kevin_Kofler: what is your concern?
14:28:28 <Kevin_Kofler> Or do we want to do that first?
14:28:33 <Kevin_Kofler> rdieter: The unfixed stuff.
14:28:43 <than> Kevin_Kofler: we can fix it later
14:28:44 <Kevin_Kofler> But it's true that we can't wait forever.
14:29:21 <jreznik> Kevin_Kofler: I can build it... it's shouldn't take too much time
14:29:31 <rdieter> ok, current topic.  I propose we disable kdebug by default for F-13+ , thoughts?
14:29:34 <jreznik> I didn't have time yesterday... :(
14:29:37 <Kevin_Kofler> jreznik: But maybe we want it to go out to testing first?
14:29:56 <rdieter> yes, it should go to testing first, no need to rush anything
14:30:03 <jreznik> Kevin_Kofler: it should be sane - just few bugfixes...
14:30:17 <jreznik> but let's go through testing
14:30:25 <Kevin_Kofler> rdieter: +1 for disabling kdebug by default, in fact I already suggested it a couple times.
14:30:27 <SMParrish_mobile> rdieter: What if anything do we lose by disabling it?
14:30:44 <ltinkl> rdieter: +1 disable it
14:30:57 <rdieter> SMParrish_mobile: the copious debugging detail that goes to stdout and ~/.xsession-errors is *sometimes* helpful to debug prolbems
14:31:31 <rdieter> so could hamper debugging efforts a bit (but it's easy enough to re-enable, so I don't consider it a big issue)
14:31:55 <jreznik> in this case +1
14:32:02 <SMParrish_mobile> Could we not keep it for rawhide. But disable for everything else?
14:32:40 <Kevin_Kofler> That might make sense.
14:32:48 <Kevin_Kofler> It's how the kernel folks handle this kind of issues.
14:32:58 <Kevin_Kofler> And some other stuff too.
14:32:58 <rdieter> SMParrish_mobile: I like that, but when we get into alpha/beta/rc phases, turn it off again
14:33:10 <Kevin_Kofler> We should just not forget to turn it off when the release branches.
14:33:17 <Kevin_Kofler> rdieter: Yeah.
14:33:23 <Kevin_Kofler> Right now we'd only enable it for devel, not F-13.
14:33:39 <SMParrish_mobile> Kevin_Kofler: Right
14:33:53 <rdieter> ok, any objections?  if not, I'll pull the trigger in kde-settings after the meeting.
14:34:09 <SMParrish_mobile> I'm +1 for that
14:34:20 <jreznik> do we really use it so much that's it's really worth to handle it differently (and then forget we want to disable/enable it?)
14:34:21 <svahl> +1 for disabling it
14:34:30 <Kevin_Kofler> rdieter: Just be careful about what you push in Bodhi, as kde-settings is also in the 4.4.0 update set.
14:34:45 <Kevin_Kofler> Having 2 kde-settings builds queued to stable at the same time will cause chaos.
14:34:46 <rdieter> Kevin_Kofler: this is for f13 only (so far)
14:35:00 <rdieter> unless folks want to consier it for < f13 too ?
14:35:28 <rdieter> but I'd be nervous about changing behavior like this mid-release
14:35:53 <than> rdieter: for f13 is ok
14:36:37 <Kevin_Kofler> OK, let's only change this for F13.
14:36:45 <Kevin_Kofler> Move on?
14:36:53 <Kevin_Kofler> (FYI, 4.4.0 is now queued for stable.)
14:36:57 <rdieter> #topic enable nepomuk by default?
14:37:13 <rdieter> I sent this idea to the mailing list for discussion a week or so ago.
14:37:30 <rdieter> in short, akonadi gets unhappy if nepomuk isn't enabled
14:38:03 <rdieter> this is already enabled for f13, I'm talking about f11/f12 here.
14:38:13 <rdieter> and only nepomuk, not strigi indexing
14:38:19 <rdieter> thoughts?
14:39:26 <Kevin_Kofler> Uhm, shouldn't we have decided this before rushing 4.4.0 to stable?
14:39:47 <rdieter> not necessarily.
14:40:13 <rdieter> um... the more I think about it, the same argument about making changes mid-release per the previous topic probably applies here too.
14:40:49 <rdieter> maybe we could play it safe, keep things as-is, but make sure to advertise/document the akonadi/nepomuk interaction here and how to re-enable it, if users so choose.
14:40:59 <SMParrish_mobile> I'd agree. Make it default f13. But not f11 or f12
14:41:40 <rdieter> ok, how best to advertise/document this then?  think another notice to kde ml would be sufficient?
14:41:44 <Kevin_Kofler> jreznik: Tell jfch2222 that he needs to hit that "push to stable" button for libssh himself, Bodhi won't let us do it for him (well, I guess we could abuse karma again like we did for the previous built, but…).
14:41:53 <than> rdieter: i agree with SMParrish_mobile we don't change it for F11/F12
14:42:19 <Kevin_Kofler> rdieter: Well, what exactly breaks if Nepomuk is not enabled?
14:42:43 <jreznik> Kevin_Kofler: I asked him to do it
14:42:44 <rdieter> akonadi stuff isn't searchable, and it complains (gives a warning that nepomuk indexing is disabled)
14:43:08 <rdieter> not exactly the most user-friendly warning in the world
14:43:27 <Kevin_Kofler> I guess it will be worse in 4.5 (i.e. no more search in KMail).
14:43:48 <rdieter> alright, let's leave it, I'll followup onlist
14:44:06 <rdieter> #topic f13 kde live image status (and related bugs)
14:45:27 <Kevin_Kofler> Well, Akonadi is broken, that will hopefully be fixed for the Alpha now.
14:45:38 <rdieter> the nightly image I tried last night was fail, kdm wouldn't start (selinux-policy issue apparently)
14:45:41 <Kevin_Kofler> But a bigger problem is that KPackageKit is reportedly broken and we don't have a fixed package at all.
14:45:44 <Kevin_Kofler> :-(
14:46:03 <rdieter> SMParrish_mobile: any news from kpk upstream?
14:46:21 <Kevin_Kofler> rdieter: That's also a big FAIL, but it also affects GDM, so that one will definitely not be there in the alpha. ;-)
14:46:47 <rdieter> Seriously folks, I suggested we have minimum standards, and consider switching to gnome-packagekit
14:47:13 <Kevin_Kofler> It's not exactly KPK's fault that things are broken.
14:47:21 <Kevin_Kofler> F13 is using an unreleased snapshot of PK.
14:47:29 <SMParrish_mobile> rdieter: I don't have much faith in kpk upstream. ATM
14:47:30 <rdieter> Kevin_Kofler: it is?
14:47:46 <Kevin_Kofler> PackageKit-0.6.2-0.1.20100209git.fc13
14:47:49 <Kevin_Kofler> That's not a release.
14:48:14 <rdieter> it was broken even when we used official 0.6.1 release too though
14:48:18 <rdieter> and 0.6.0
14:48:20 <Kevin_Kofler> The stable branch is the 0.5.x branch which F12 is using and which KPK is still targeting.
14:48:42 <rdieter> SMParrish_mobile comment is telling, I have little/no confidence we can expect stuff to get fixed for us
14:48:53 <rdieter> and we haven't the ability to help ourselves.
14:48:59 <Kevin_Kofler> KPK upstream may have already an uncommitted fix.
14:49:10 <Kevin_Kofler> SMParrish_mobile: Please nag him, talk to him!
14:49:18 <Kevin_Kofler> If you won't do it, I'll have to do it.
14:49:26 <Kevin_Kofler> And if upstream doesn't have a fix, I'll have to fix it.
14:49:30 <Kevin_Kofler> But then tell me so!
14:49:40 <Kevin_Kofler> I've been waiting all this time for news and it seems you haven't even TALKED to upstream.
14:49:51 <SMParrish_mobile> F13 already has 0.6.x. Of Packagekit and from what I can tell upstream is not ready for it.  I'll talk with dantti again today
14:50:09 <Kevin_Kofler> Which is the first thing you should have done when the blocker bug was filed.
14:50:20 <jreznik> I'm not sure we can ship kpk without sane pkgkit releases :(
14:50:50 <rdieter> jreznik: there've been 0.6.0 0.6.1 pk releases in the meantime
14:50:56 <rdieter> can't use that excuse this time
14:51:13 <Kevin_Kofler> KPK is now working great in F12, but it needs to be fixed for the 0.6 API changes.
14:51:19 <SMParrish_mobile> I have been talking to him. He is busy on work and other things. Upstream needs some help
14:51:29 <Kevin_Kofler> This is something I can do, but almost certainly not in time for the alpha. :-(
14:51:53 <Kevin_Kofler> Not before Wednesday evening for sure.
14:51:55 <jreznik> ok, so if kpk doesn't go very well with pkgkit development - we need someone who would care about it and work on it...
14:51:56 <rdieter> we all knew kpk is broken for some time.  and we had a pretty good idea kpk upstream was busy.
14:52:02 <SMParrish_mobile> Ins
14:52:05 <jreznik> we can't wait for upstream usually...
14:52:20 <Kevin_Kofler> rdieter: Well, I hoped we'd get a fixed version in time for the Alpha.
14:52:29 <Kevin_Kofler> Looks like I hoped too much.
14:52:32 <rdieter> right, so, 1.  we commit time/resources to help make kpk better
14:52:35 <rdieter> 2.  use another tool
14:52:41 <Kevin_Kofler> Next time I'll just fix things myself.
14:52:46 <SMParrish_mobile> I've told him repeatedly we need releases andbug fixes on a consistent sched and should coincide with pk releases
14:53:03 <Kevin_Kofler> The big issue there is that we never know whether he hasn't done any work or whether he just hasn't committed it.
14:53:21 <Kevin_Kofler> Because he's also known for not committing regularly (I hate this practice!).
14:53:49 <SMParrish_mobile> Kevin_Kofler: Right because he does not commit until he is ready to release. Bad practice IMO
14:53:50 <rdieter> Kevin_Kofler: he needs help obviously, probably long-term.
14:54:12 <jreznik> SMParrish_mobile: that's bad... commit early, commit often
14:54:31 <jreznik> rdieter: +1... help or move back to gnome one...
14:54:33 <rdieter> if we're not able to help steer/fix kpk development, I think we should consider another too
14:54:42 <rdieter> another tool
14:55:10 <Kevin_Kofler> SMParrish_mobile: Tell him he absolutely must commit as soon as he did any changes.
14:55:33 <Kevin_Kofler> I really want to help fixing KPK issues, but it's impossible to work with somebody who doesn't commit/push his changes.
14:55:39 <rdieter> Kevin_Kofler: you may as well contact him yourself, see where things are, if you're serious about wanting to help fix it
14:55:53 <Kevin_Kofler> Yeah, I'll take that up.
14:56:01 <rdieter> I'm sure he'll be happy for any help
14:56:28 <jreznik> SMParrish_mobile: dantti is upstream for kpk?
14:56:39 <SMParrish_mobile> Yes he is
14:57:21 <jreznik> SMParrish_mobile: ok, thanks... I'll ask him what he thinks about a) our help, b) commit policy :D
14:57:31 <Kevin_Kofler> jreznik: OK
14:57:38 <SMParrish_mobile> jreznik: Someone else does packagekit-a
14:57:47 <SMParrish_mobile> At th
14:58:08 <rdieter> lastly (before we run out of time)...
14:58:09 <SMParrish_mobile> -qt
14:58:12 <rdieter> #topic Bug 549687 kdm: no autologin on first start
14:58:13 <buggbot> Bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=549687 medium, low, ---, jmccann, NEW, kdm: no autologin on first start
14:58:16 <Kevin_Kofler> You've been working with him on the PK1 stuff, so he might listen to you more than to me. ;-)
14:58:28 <rdieter> another potential alpha blocker
14:58:33 <jreznik> Kevin_Kofler: I hope so ;-)
14:58:40 <rdieter> this is more visible that the akonadi problem even
14:58:57 <Kevin_Kofler> That's bad breakage, but we have no idea what causes it.
14:59:05 <Kevin_Kofler> I looked at the code and it seemed all fine, yet it didn't work.
14:59:10 <rdieter> svahl: I assume it is indeed still valid?
14:59:17 <Kevin_Kofler> And the exact same code works in F12.
14:59:24 <svahl> rdieter: yes, it is (at least for me)
14:59:28 <rdieter> ok
14:59:57 <Kevin_Kofler> https://bugzilla.redhat.com/show_bug.cgi?id=549687#c12
14:59:58 <buggbot> Bug 549687: medium, low, ---, jmccann, NEW, kdm: no autologin on first start
15:00:01 <rdieter> frustrating not to get any sort of feedback or help here
15:00:33 <Kevin_Kofler> * F12 has the same version of ConsoleKit, it works there.
15:00:48 <Kevin_Kofler> * libck-connector and the CK daemon come from the same tarball, they should always be in sync.
15:00:55 <rdieter> indeed
15:01:00 <Kevin_Kofler> * The "missing" method is clearly there according to the source code.
15:01:06 <Kevin_Kofler> So why is it not working?
15:01:41 <Kevin_Kofler> The ConsoleKit maintainers are ignoring the issue entirely. :-(
15:01:41 <rdieter> svahl: regarding kpk, since it's known-broken, may as well not include it in the kde live spin until it is fixed.
15:02:17 <svahl> rdieter: you mean -kpackagekit, +gnome-packagekit?
15:02:19 <Kevin_Kofler> What do we do then? Ship no updater at all in the alpha?
15:02:23 <rdieter> dunno, we don't have an alternative that works either
15:02:24 <Kevin_Kofler> gnome-packagekit won't work in KDE.
15:02:26 <Kevin_Kofler> It has NotShowIn.
15:02:30 <rdieter> gnome-packagekit is disabled right
15:02:35 <svahl> mhh, right
15:02:37 <jreznik> we are out of time
15:02:39 <Kevin_Kofler> And if we disable that, we'll be left with a mess for the whole release cycle. :-(
15:02:42 <rdieter> including nothing is better than shipping something known broken though
15:02:58 <Kevin_Kofler> I have no good solution there, I'm afraid.
15:03:00 <rdieter> ok, let's take it back to #fedora-kde , thanks everyone
15:03:03 <rdieter> #endmeeting