[02:44] <basix> can someone please take a look at this bug? https://bugs.launchpad.net/unity/+bug/791660 It needs triaging.
[02:44] <ubot4> Launchpad bug 791660 in unity (Ubuntu) (and 1 other project) "Dual-Screen setup broken in Unity (natty) (affects: 2) (heat: 14)" [Undecided,New]
[03:52] <thulle> getting timeout-errors adding a bug to launchpad last half hour, any info on when it's fixed?
[03:54] <charlie-tca> Been that way for months
[03:54] <thulle> k, so just to keep on trying?
[04:07] <micahg> thulle: there's a problem with bugs at the moment being looked into
[04:07] <micahg> thulle: I'd save your notes in a local file and try again tomorrow
[04:19] <thulle> micahg: thanks! and already done:) will get some sleep and try in the morning
[04:19] <micahg> thulle: good night
[04:41] <charlie-tca> bug filing should be fixed now, according to lauchpad
[04:41] <charlie-tca> bug filing should be fixed now, according to launchpad
=== stefank is now known as stefankuehnemund
=== stefankuehnemund is now known as skuehnemundt
=== Hurtz_ is now known as Hurtz
[15:24] <psusi> is there a release manager around who can approve the series tasks for bug #675108 please?  it's a natty regression with a proposed patch that I've worked into a bzr branch and tested... going to forward port it to oneiric next, but the SRU will need the natty task.
[15:24] <ubot4> Launchpad bug 675108 in gnome-power-manager (Ubuntu) (and 1 other project) "gnome-power-manager adds battery to indicator twice when battery hot-unplugged and plugged back in (affects: 42) (dups: 8) (heat: 130)" [Medium,In progress] https://launchpad.net/bugs/675108
[15:28] <yofel> there should be more of them in -motu than here
=== charlie-tca is now known as charlie-tca1
=== Abhijit_ is now known as Abhijit
[19:38] <micahg> pedro_: I looked at unity recently  and it has > 1500 bugs, looks like a good candidate for a future bug day
[19:39] <pedro_> micahg, sure i'll add it to the planning page :-)
=== zyga is now known as zyga-afk
=== yofel_ is now known as yofel
[21:08] <veger> pedro_: for bug 791007 and bug 793381, I asked for a (more) complete backtrace. You closed the reports as invalid afterwards. Should I had them get closed form the start?
[21:08] <ubot4> Launchpad bug 791007 in evolution (Ubuntu) "Evolution crashed after sending an email with a link (https) (affects: 1) (heat: 8)" [Undecided,Invalid] https://launchpad.net/bugs/791007
[21:08] <ubot4> Launchpad bug 793381 in evolution (Ubuntu) "evolution crashes with segmentation fault (affects: 1) (heat: 8)" [Undecided,Invalid] https://launchpad.net/bugs/793381
[21:09] <pedro_> veger, we ask people to enable apport and thus provide a new and better report
[21:09] <veger> ok, I will do that next time as well
[21:10] <roadmr> yay apport
[21:10] <pedro_> veger, thanks a lot :-)
[21:10] <veger> pedro_: thanks for helping again :)
[21:40] <roadmr> hi folks: bug 780962 and bug 792501 look the same to me, I'd like to dupe them but am unsure if it should go under unity or libreoffice. Also, unable to duplicate, but two people with the same problem looks legit enough to me
[21:40] <ubot4> Launchpad bug 780962 in libreoffice (Ubuntu) "Conflict with unity dock (affects: 1) (heat: 106)" [Undecided,Incomplete] https://launchpad.net/bugs/780962
[21:40] <ubot4> Launchpad bug 792501 in unity (Ubuntu) (and 1 other project) "sidebar launcher apears unexpected when i use libreoffice (affects: 3) (heat: 353)" [Undecided,Incomplete] https://launchpad.net/bugs/792501
[21:44] <veger> bug 698035, the reporter reports that the --help text is incomplete (according to his ideas). The complete text can be found in the manual pages... Should I open an upstream report for this case and let them decide what to do?
[21:44] <ubot4> Launchpad bug 698035 in evolution (Ubuntu) "evolution --help talks unhelpfully about "the specified component" (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/698035
=== PascalFR is now known as boxerjaune
[22:06] <LoOoD> I have a server that was running an older kernel version in lucid. And it kernel paniceed the other day. Should I still report a bug about it and post the kernel trace it printed out?
[22:06] <LoOoD> It did reboot into the lastest kernel version when it came back up
[22:26] <penalvch> Lo0oD: If you can reproduce the oops in the most recent kernel for Lucid then feel free to report a bug about it.
[22:28] <LoOoD> thanks