[00:20] <tgm4883> devxdev is definitly not a noob
[00:20] <tgm4883> <devxdev> officially have a chrooted ubuntu-core running on a Samsung LN40B530P7N
[00:20] <tgm4883> an impressive feat
[01:40] <bkerensa> :D
[03:46] <bkerensa> slangasek: is there any protocol or suggested path for trying to get a bug addressed even if the person responsible for the related application is semi-ignoring the bug
[03:46] <bkerensa> https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/972063
[03:46] <lubotu1> Launchpad bug 972063 in bluez (Ubuntu) "Bluetooth Headset pairs but does not show up in Sound Settings profile" [Medium,Confirmed]
[04:41] <tgm4883> Bkerensa, yes, you attach a patch
[05:04] <slangasek> bkerensa: yes, the traditional path is to continue digging until you figure out how to fix it yourself :)
[05:05] <slangasek> there's no one "responsible" for bluetooth in Ubuntu in that sense
[08:20] <bkerensa> slangasek: well just kind of sad that I'm running a  Canonical certified laptop and it appears no bluetooth works on it in our LTS =/
[14:25] <slangasek> bkerensa: well, I don't believe bluetooth support is part of the certification
[14:25] <slangasek> (unfortunately IMHO)
[15:18] <blkperl> slangasek: any chance you get fix the amanda package in precise? or just sneak in the quantal package
[15:18] <slangasek> blkperl: no chance of me doing it personally :)
[15:19] <blkperl> slangasek: awwww
[16:00] <slangasek> bkerensa: can you bring your headset and laptop to the BSP?
[16:16] <devxdev> My I attend the BSP to learn/watch?
[16:25] <slangasek> devxdev: certainly; it's generally expected that people participating in a BSP will learn something :)
[16:29] <devxdev> O_O we are pulling an over-nighter I see lol
[16:50] <slangasek> who is?
[16:53] <devxdev> oh haha nevermind I read the times wrong >_<
[17:25] <devxdev> Will we be using this: http://harvest.ubuntu.com/opportunities/ ?
[17:28] <tgm4883> devxdev, what is that?
[17:35] <devxdev> current bugs
[17:35] <devxdev> & todo list
[17:47] <slangasek> so AIUI, the focus for this BSP will be the list of release-critical bugs known to Debian
[17:47] <devxdev> ooh ok :)
[18:07] <bkerensa> slangasek: I will see :P I was planning on playing hooky
[18:07] <bkerensa> or remotely participating
[18:10] <slangasek> well, as I recall one of the outstanding questions around that bug was whether it was an issue with the headset or with the bluetooth interface on the laptop
[18:10] <slangasek> until it's been narrowed down that much by cross-testing, it's hard for anyone to make much headway on the bug
[18:18] <tgm4883> slangasek, do you know much about errors.ubuntu.com
[18:19] <slangasek> a bit
[18:19] <tgm4883> slangasek, I'm trying to find out where we can add logs to be gathered for a specific report on there
[18:20] <tgm4883> based on this comment on askubuntu from ev
[18:20] <tgm4883> The plan is to allow developers to hook into the information collection process server-side. If I need /var/log/syslog but it's not already provided, I just change a setting on http://errors.ubuntu.com and the next person who experiences the error automatically adds it to the data they're sending.
[18:20] <slangasek> tgm4883: er, no facility exists for that today
[18:20] <tgm4883> ah
[18:20] <tgm4883> well that explains why I can't find it
[18:21] <slangasek> this is all very much a work in progress
[18:21] <tgm4883> So no logs are gathered at this point?
[18:21] <slangasek> no, just the crash
[18:22] <slangasek> however, on the backend there are smarts to be able to relate errors.u.c crashes to the apport-retracer's work on launchpad bugs
[18:22] <slangasek> so if someone opens a bug, you can ask for more logs there
[18:22] <slangasek> (i.e., the old way of doing things)
[18:22] <tgm4883> slangasek, ok, that seems like it's what we'll have to do then
[18:22] <tgm4883> thanks for the info
[18:23] <slangasek> n/p
[18:31] <devxdev> Are any of you experienced with chroot?
[19:14] <slangasek> certainly
[19:17] <devxdev> ah I figured it out was having some strange issue with "dangling symlink"