[11:35] <jamespage> if there are any archive admins around, the three neutron-* packages I just uploaded to the vivid NEW queue are refactorings of drivers out of the core neutron codebase, two involve moving binary packages as well - 1:2015.1~b1-0ubuntu4 of neutron drops these from the neutron source package.
[11:36] <jamespage> coreycb, zul: fyo ^^
[16:04] <arges> mlankhorst: hey. I see two xserver-xorg-vide-intel packages uploaded into trusty. Can you confirm if I should reject the older upload and only review the newer one? Thanks
[16:05] <mlankhorst> reject older I think
[16:05] <mlankhorst> *checks*
[16:06] <mlankhorst> yeah
[16:06] <arges> mlankhorst: thanks
[19:21] <ogra_> stgraber, are there any known issues with the importer, it seems to take really long for the last touch image (the rootfs finished over 1h ago) i see it running when i check the processlist on nusakan though
[19:21] <stgraber> ogra_: yep, it was broken, I fixed the bug about 20min ago, so it must be running for good now
[19:22] <ogra_> ah. perfect, thanks !
[21:23] <tkamppeter> bdmurray, hi
[21:24] <bdmurray> tkamppeter: hello
[21:24] <tkamppeter> bdmurray, I got a mail about a possible s-c-p regression from some error report bot which you are running.
[21:26] <tkamppeter> bdmurray, looking into the tracebacks of these crashes they happen at places which I did not change, which did not change for long time, so they seem unrelated to the update. What do I have to do?
[21:26] <bdmurray> tkamppeter: I can override those but this looks new - https://errors.ubuntu.com/problem/d2a942520573c92c3250978db9ff5c8fee2962ed
[21:27] <bdmurray> tkamppeter: and https://errors.ubuntu.com/problem/ace34f647267a4452d4ccc0d603a1e7bb9d6fbc2
[21:32] <tkamppeter> The first one seems to be caused that a _query_jockey() call tries to access the discontinued Jockey. Strange is here that this bug did not get hit earlier.
[21:34] <tkamppeter> One would need to know which printer(s) these users have so that one can run the driver queries for them. Seems that making the driver queries working reveals some bugs which were hidden behind the broken driver query part.
[21:34] <bdmurray> Wasn't the SRU related to downloading printer drivers?
[21:35] <tkamppeter> bdmurray, yes.
[21:35] <bdmurray> the individual crashes should have some information to help out
[21:35] <tkamppeter> bdmurray, driver package download via OpenPrinting query did not work. This I have fixed and made available as an SRU.
[21:39] <tkamppeter> I am looking in one of the crash reports now, it does not contain info about which preinter the user tried to add. I would like to ask the user what he did, bnut it seems that the reports are anonymizes.
[21:42] <tkamppeter> I would either need tyo be able to reproduce the bug or to interact with a user suffering the bug to be able to fix it.
[21:46] <bdmurray> mightn't it be in lsusb?
[21:47] <bdmurray> Lsusb 	
[21:47] <bdmurray> Bus 001 Device 003: ID 04b8:08ae Seiko Epson Corp.
[21:52] <tkamppeter> Yes, this is already a hint, but also not perfect, as Epson does not have PIDs for each printer model. One even knows at least that it probably happens for printers which are supported by a downloadable driver.
[21:53] <tkamppeter> This means that most people are unaffected, but people with a supported printer are not able to get the driver in all cases. Some will get it some will hit this bug.
[22:00] <bdmurray> this support was also added to 15.04?