[00:08] <alex_mayorga> Hi! Just got bug 812602
[00:08] <ubot4> alex_mayorga: Bug 812602 on http://launchpad.net/bugs/812602 is private
[00:09] <alex_mayorga> anything else I can provide?
[04:22] <ohsix> where can i get eyes on this? i had no luck undoing the rats nest https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/802276
[04:23] <ubot4> Launchpad bug 802276 in gnome-power-manager (Ubuntu) "brightness adjust 3 steps from hard (Fn) keys (affects: 1) (heat: 158)" [Undecided,New]
=== Ursinha is now known as Ursinha-bbl
=== zyga is now known as zyga-food
=== zyga-food is now known as zyga
[15:26] <stef31> bonjour
[15:26] <stef31> is it an english room ?
[15:27] <charlie-tca> yes
[15:28] <stef31> do you know the french room for bug on ubuntu ?
[15:29] <pedro_> ubuntu-fr ?
[15:29] <stef31> it's for specialy bug on ubuntu too ?
[15:30] <davmor2> stef31: possibly not but they can certainly help you with bugs
[15:31] <stef31> ok , i'll test to explain my bug . if i understand , i'll go to ubuntu-fr
[15:32] <stef31> my graphic card is nvidia 6200, and drivers actived but not used ...
[15:34] <stef31> and often , when i switch on my computer , resolution is really bad : 640 x 480 max
[15:34] <stef31> i had delete and install an other time drivers
[15:35] <stef31> but , bug always is here
=== Ursinha-bbl is now known as Ursinha
[16:12] <pedro_> Folks if you're part of the ubuntu-bugcontrol, could you please give us input on the application of the canonical-server team ?
[16:14] <hggdh> mine is there already
[16:15] <charlie-tca> I did too, didn't I?
[16:16] <hggdh> yes sir, you did :-)
[16:16] <hggdh> actually, we already have the votes, but I would really love to have more community input
[16:16] <pedro_> indeed
[16:17]  * charlie-tca thinks it is "apathy"
=== davmor2_ is now known as davmor2
=== abhinav- is now known as NetBSD
=== NetBSD is now known as abhinav-
[20:32] <SWAT> where should I preferbly file a bugreport/fix about a bluez issue (initscript) in Ubuntu (Debian unstable has a newer/fixed version)?
[20:33] <micahg> SWAT: what's your goal?
[20:33] <SWAT> micahg: getting proper a fix for Natty
[20:34] <micahg> SWAT: you'll want to file a bug against bluez then describing the issue w/a test case, we'll need a patch for natty, oneiric would have to get the fix first though
[20:37] <SWAT> micahg: oneiric will probably have it already, since it will use updated packages from upstream. I'm running Debian unstable on another machine
[20:37] <micahg> SWAT: ah, ok, is the fix upstream?
[20:38] <SWAT> in bluez-4.94 it is ;-)
[20:38] <micahg> !sru | SWAT
[20:38] <ubot4> SWAT: Stable Release Update information is at http://wiki.ubuntu.com/StableReleaseUpdates
[20:39] <SWAT> basically bluetooth does not work due to an incorrect initscript, and the fix is really simple
[20:39] <dtchen> SWAT: if you can file the bug and point out the patch now, I can do the SRU legwork and upload it to natty-proposed
[20:39] <micahg> so, oneiric has 4.94, so we're good on that front, go ahead and file a bug w/a test case and a link to the upstream commit that fixes it if you have it
[20:40] <seb128> it's not likely that bluetooth doesn't work and that didn't get noticed
[20:40] <seb128> it's rather it's buggy in some cases right?
[20:42] <SWAT> seb128: I was also suprised, but I tested with the LXDE natty install. Actually my dad noticed the bug, since bluetooth didn't work anymore after the upgrade.
[20:42] <SWAT> don't have other systems with natty _and_ bluetooth
[20:42] <seb128> well, I use bluetooth every week and it works fine on natty and oneiric
[20:42] <SWAT> dtchen: reading now
[20:42] <seb128> but I don't use LXDE
[20:43] <seb128> the init script is hacked in ubuntu as well btw so it's likely that "new versions" will not fix it for you
[20:43] <seb128> i.e I don't think we changed the init script between natty and oneiric
=== Hellow is now known as collinp
[20:50] <SWAT> seb128: hmmm, okay. In my case (upgraded to natty and gnome to lxde) the default init script didn't work, but a simple 'start-stop-daemon --start --quiet --oknodo --pidfile /var/run/bluetoothd.pid --exec $DAEMON' worked fine.
[20:50] <seb128> SWAT, did you find an error in the init script?
[20:53] <SWAT> seb128: yes, the 'start' command did not work, although it indicated it did.
[20:54] <SWAT> I fixed it for him, so basically I just wanted to fix/report for others. I don't think people should nag about FLOSS software, if they don't contribute (or try to)
[20:54] <seb128> SWAT, best to open a bug describing your issue and what you did, I'm not sure what is wrong right now but I know bluetooth work under GNOME or unity for others
[20:56] <SWAT> seb128: alright, thanks for the info. Since this is a downstream issue, where should I preferbly post it?
[20:58] <seb128> SWAT, https://bugs.launchpad.net/ubuntu/+source/bluez/+filebug
[20:58] <SWAT> dtchen: will post a regular bug report first, but thanks for the headsup
[20:58] <SWAT> seb128: thanks!
[20:58] <seb128> thank you!
=== yofel_ is now known as yofel
[21:17] <greg-g> ok, where is the bug report for Unity where it complains about windows going all the ef over the place when you go from dual monitor to single? :)
[22:02] <dtchen> 4 more reviewed and uploaded for Patch Pilot.
=== kentb_ is now known as kentb-out
=== zyga is now known as zyga-afk
[23:08] <RenatoSilva> ubuntu-bug audio after asking some questions is running indefinitely, what do I do?
[23:13] <RenatoSilva> I ran it because of this: http://pastie.org/2239582. The onboard audio is selected as default output. However, the front audio (headphone) only starts working after I "stimulate" it by plugging in some connector in the onboard hear jack. Doesn't happen in Windows, there the problem is different.
[23:30] <RenatoSilva> if someone can help, /memo me please