=== j_f-f_ is now known as j_f-f
[11:03] <NikTh> Help https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1255428 :-)
[11:03] <ubot2> Launchpad bug 1255428 in xserver-xorg-video-intel (Ubuntu) "LCD brightness control keys and widget do not work on Intel Graphics on Saucy" [Undecided,Incomplete]
[11:04] <NikTh> It's because /etc/apt/sources.list does not exist ?
[11:08] <penguin42> haha
[11:08] <penguin42> hmm
[11:08] <penguin42> I'd ask him just to create a dummy empty sources.list and try again - I think he's probably right that you can split everything into entries in /etc/apt/sources.list.d  but it's not too surprising some things don't like it
[11:11] <ogra_> you could surely do that as long as you make 100% sure that the required system entries end up in an /etc/apt/sources.list.d file ... but thats pretty much nonsense
[11:11] <penguin42> ogra_: That stack trace though seems to have an attempt to access /etc/apt/sources.list though
[11:12] <ogra_> yeah, seems python-apt kind of expects that the system setup is existing :)
[11:14] <penguin42> NikTh: When he creates the dummy /etc/apt/sources.list   and it reports that bug, ask him to file another bug against apport :-)
[11:25] <NikTh> Thanks guys . Helpful as always :-)
[11:58] <NikTh> One more question: If I change the package on a bug report and then the reporter runs "apport-collect BUGNUMBER" it will gather information about the new associated package ?
[11:58] <NikTh> I think yes, but I'm asking for a confirmation.
[11:59] <penguin42> I think so
[15:03] <hggdh> it will grab data on the package listed in the bug. If there are MORE than one packages in a bug... then IDK. Never tried.
=== j_f-f_ is now known as j_f-f
[19:56] <Cas> hi, not sure if I am missng something really obvious but how do I link a personal bzr branch to a bug
[19:58] <Cas> hang on there is an option in the branch, ha :)
=== thomi_ is now known as thomi