[11:53] any pango or unity guys here? Bug 1239381 - the last comment someone added another way of triggering it, the backtrace looks similar on saucy, and it doesn't trigger on Trusty - should it be the same bug? [11:53] Launchpad bug 1239381 in Unity 7.0 "Unity crashes when entering a term including "emu" in the home lens" [Critical,In progress] https://launchpad.net/bugs/1239381 === ara_ is now known as ara === om26er is now known as om26er|food === om26er|food is now known as om26er === psivaa is now known as psivaa-afk [20:26] guys is there any fix for the dash home button being very laggy? [20:32] some days and pointless comments later there is still no visible progress regarding bug 1205384 [20:32] Launchpad bug 1205384 in lxsession (Ubuntu) "Lock can be circumvented by switching to console" [High,In progress] https://launchpad.net/bugs/1205384 [20:34] it is the no. 1 bug in Lubuntu 13.10, normally one would expect a emergency fix within few days... [20:35] wow that does seem serious! [20:36] it really is [20:37] ya i love lubuntu.. i think im on 12 and 11 though so... [20:39] I'm not even using Lubuntu, but I've informed the people in #lubuntu and in this channel several times, also marked the bug report as "security" one, talked to the QA lubuntu guy and guess what... no change so far [20:40] the package maintainer might be busy, but this is a serious issue [20:40] if he does not have the time, he should assign someone else [20:41] remember "open source" means "i have a day job" [20:42] this is no excuse for releasing a product with a major flaw [20:50] brainwash: As I've said before, you could try asking the guy assigned to it if there is any progress [20:52] penguin42: he does not react to the comment flood in the report [20:53] brainwash: He may well have hundreds of bugs on his plate, but the other thing you can try after asking him nicely if he doesn't respond, you could try asking in #ubuntu-dev [20:54] brainwash: But again, ubuntu gets released on a time basis, if something is broken in general it still gets released [20:54] brainwash: and lubuntu isn't supported so - shrug [20:55] brainwash: If you fix the problem and push a branch I'm sure you can get it merged [20:55] but it's an official release [20:55] Id on't see a patch or a upstream bug there [20:55] so some sort of QA should care about this kind of issues [20:55] brainwash: It's not supported [20:56] what a bummer [20:57] jtaylor: the package maintainer is already assigned and knows about this problem, but there is still no fix available (check the dates) [20:58] or at least I don't think it is - it does have a task: tag, so hmm [21:00] as I interpret his answer there is no solution [21:02] hnnm hggdh did ping him on the 6th [21:10] brainwash: The other thing I can't quite understand from that report is whether the dm-tool command the reporter is using to lock the screen is normal; i.e. does this thing fail if you just wait for the system to lock screen or is it only if you use dm-tool? If it's only when you use dm-tool it seems less of an issue [21:12] the lubuntu/lxde session calls lxlock which triggers dm-tool [21:14] it could be fixed by reverting the changes to lxlock, so it calls xscreensaver as first option... but xscreensaver is not part of the default lubuntu installation anymore [21:14] and proper lightdm locking is available starting with 14.04 -> light-locker [21:26] brainwash: So IMHO the right thing to do is wait a couple more days to see if he replies to hggdh's prod, and if he doesn't then hmm [21:41] penguin42: right, "hmm" [21:59] brainwash: I'm not sure what else I'd suggest; you could try asking the ubuntu-security guys, but the real mistake here seems to be the stuff went into the release too early