[09:17] <Sergobot> Riddell: are you here?
[12:19] <BluesKaj_> 'Morning folks
[12:30] <soee_> hiho BluesKaj_
[12:33] <BluesKaj_> hey soee
[17:12] <kranzer> Riddell: hi, are you here&
[17:12] <kranzer> ?
[18:30] <Pali> Riddell: ping, have you looked at my PPA?
[18:33] <murthy> shadeslayer: are you there?
[18:35] <murthy> yofel: are you there?
[18:35] <shadeslayer> yes
[18:35] <shadeslayer> ssup
[18:35] <murthy> shadeslayer: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1389847
[18:36] <murthy> shadeslayer: who is the maintainer of ubiquity-kde?
[18:36] <shadeslayer> no one
[18:36] <shadeslayer> more or less unmaintained
[18:36] <murthy> shadeslayer: Can you give me some direction on how to push for this bug \
[18:36] <shadeslayer> I can have a look
[18:37] <shadeslayer> murthy: so basically, you ran driver manager on a live medium
[18:37] <shadeslayer> and then ubiquity got blocked when it was doing it's thing
[18:37] <murthy> shadeslayer: no
[18:37] <murthy> the driver-manager is the sub process of the ubiquity
[18:38] <shadeslayer> can't be
[18:38] <shadeslayer> separate things
[18:38] <yofel> it is though
[18:38] <shadeslayer> what
[18:38] <murthy> ok let me explain
[18:38] <shadeslayer> driver-manager isn't supposed to be triggered by ubiquity afaik
[18:38] <yofel> ubiquity can install third party drivers during install if you check the "install 3rd party software" box
[18:39] <murthy> ps aux shows driver manager running and after that apt-get downloading the binary driver
[18:39] <shadeslayer> ahhh
[18:39] <yofel> it does that in the background, and the nvidia blob is pretty huge
[18:39] <murthy> ya
[18:39] <murthy> the thing is if the bug is in the 3rd party side i wont care but i feel the bug is in our side
[18:40] <shadeslayer> yofel: ah so it starts downloading things right after the system requirements page?
[18:40] <shadeslayer> I did not know that 0.o
[18:41] <yofel> I don't quite remember when exactly, but it does block on it at some point without visual indication that it's doing something
[18:41] <shadeslayer> ack
[18:42] <murthy> the wait for me is 53 mins
[18:42] <shadeslayer> murthy: might be useful to send a email to Kubuntu Devel if no one looks at it in a few weeks
[18:42] <shadeslayer> I might be able to, but can't say for sure
[18:42] <shadeslayer> maybe sgclark would like to learn about ubiquity :p
[18:43] <yofel> I *think* the idea was to install stuff like broadcom wifi drivers before continuing with the install, but the driver manager doesn't blacklist the nvidia one at that point
[18:43] <shadeslayer> mhh
[18:43] <yofel> because installing nvidia at this point is pretty useless
[18:43] <shadeslayer> one could potentially have some sort of timeout, that goes : "Downloading for > 15 mins, bugger it and proceed"
[18:46] <murthy> why is it blocking the main process?
[18:47] <yofel> if this really is about wifi drivers, then those should've finished installing before the wifi selection at the next step
[18:48] <murthy> good point
[18:51] <murthy> yofel: so konversation is default now?
[18:56] <yofel> dunno, our defaults for p5 aren't quite correct
[18:56] <yofel> e.g. konqueror is NOT the default browser
[18:57] <murthy> yofel: ok. got confused after I saw it in 15.04
[19:08] <sitter> yofel: I don't see how driver-manager factors into this?
[19:08] <sitter> the 3rdparty stuff is implemented in ubiquity
[19:12] <yofel> the third party installation stuff isn't re-implemented in ubiquity. It just tells u-d-m to install the drivers at that point
[19:12] <yofel> IIRC
[19:15] <sitter> there is no driver-manager package anymore
[19:15] <sitter> it's a query library nowadays
[19:15] <sitter> so the install happens in ubiquity
[19:58] <soee_> when will QT4 be availabel in Vivid ?
[19:58] <soee_> *5.4
[19:58] <shadeslayer> Depends on how much wine sitter gets
[19:59] <soee_> :)
[20:01] <kranzer> Riddell: hello, are you here?