[00:22] <hggdh> I think LP does it automatically
=== asac_ is now known as asac
[00:54] <bdmurray> savvas: Yes
[00:56] <savvas> thanks bdmurray :)
[00:56] <savvas> ah, hggdh as well :P
[01:11] <Laibsch> some kind soul to help me understand the compile failure in http://tinyurl.com/dyln2m so that I can progress with bug 340298?
[01:11] <ubottu> Launchpad bug 340298 in cups "[Jaunty] Canon Pixus 550i stopped working a few days ago" [Undecided,Incomplete] https://launchpad.net/bugs/340298
[01:12] <Laibsch> pstocanonbj.c:6:23: error: cups/cups.h: No such file or directory
[01:12] <Laibsch> Is some cups-dev package missing in the compile-time dependencies?
[01:40] <Laibsch> It was indeed as simple as that, missing compile-time dependency
[01:41] <Laibsch> libcups2-dev
[03:11] <tlcoffee> when seeing a duplicate bug we just need to mark it as duplicate or do we need to comment as well
[03:13] <greg-g> tlcoffee: search this page for "duplicate" https://wiki.ubuntu.com/Bugs/Responses
[03:13] <tlcoffee> thnx
=== teKnofreak is now known as techno_freak
[06:12] <bz0b> hey guys, anyone know how to solve the issue with the tty messing up, like unreadable and can't see anything
[06:35] <persia> bz0b, Have you tried "reset" ?
[06:37] <bz0b> persia, what do u mean reset
[06:38] <Ryan52> bz0b: run the command reset
[06:39] <bz0b> ok
[06:39] <persia> It's a command from the ncurses-bin package
[06:39] <bz0b> as room
[06:39] <bz0b> as root*
[06:39] <Ryan52> as whatever user you are experiencing the problem as, in that tty.
[06:39] <bz0b> like clear
[06:39] <bz0b> ya that fixed it
[06:39] <bz0b> lol
[06:39] <Ryan52> ya, sort of.
[06:40] <bz0b> why does that happen at boot up though?
[06:42] <persia> It shouldn't happen at boot up.  That's worth a bug.
[06:44] <bz0b> ok
[06:44] <bz0b> so how do i post a bug, i've never done it before
[06:44] <bz0b> my gfx card is intell 4500 mhd
[06:45] <bz0b> intel*
[06:50] <bz0b> brb
[07:06] <dholbach> good morning
[07:19] <thekorn> good morning!!
[07:40] <YoBoY> good morning
[07:43] <hggdh> good morning
=== mdz_ is now known as mdz
[10:20] <YoBoY> bug 340834 << not a bug, but a feature request or a more complicated and expensive discussion request, how i triage this ?
[10:20] <ubottu> Launchpad bug 340834 in gnome-power-manager "Power Manager misnames "External power" source as "AC power"" [Undecided,New] https://launchpad.net/bugs/340834
=== jussio1 is now known as jussi01
[10:32] <YoBoY> bug 340834 -> wishlist
[10:32] <ubottu> Launchpad bug 340834 in gnome-power-manager "Power Manager misnames "External power" source as "AC power"" [Undecided,New] https://launchpad.net/bugs/340834
[10:38] <davmor2> GrueMaster: Morning Dude
[11:04] <GrueMaster> Morning.  We're having dns issues, so I'm popping up and down like crazy.
[13:42] <pfarmer> /wc/
[15:03] <bddebian> Boo
=== yuriy_ is now known as yuriy
[16:20] <torkiano> hello all, I'm testing jaunty alpha5. If I find a bug is there any rule about the subject of the bug report? eg; [jaunty] or  [alpha5] ...
[16:21] <popey> personally i use [jaunty] because alpha5 will be passed soon
[16:22] <torkiano> popey: do you know if there is any document in the wiki for this question?
[16:22] <popey> pass
[16:26] <hggdh> torkiano, just mark it as [jaunty] in the title, and in the description make sure you add in the applicable package versions
[16:28] <torkiano> hggdh: ok, and no tags?
[16:28] <persia> Or just file it with `ubuntu-bug ${package}` which automatically adds all sorts of useful information, including sufficient data that we can tell not only that it's jaunty, but where in the development cycle it happened.
[16:29] <hggdh> torkiano, persia's option is even better. But no, there are no specific tags for alpha
[16:30] <persia> And it's not usually very helpful to know that it's "jaunty" or "alpha X" when figuring out the cause of the bug anyway.
[16:30] <persia> The specific package version is *much* more useful.
[16:33] <charlie-tca> torkiano: instead of alpha 5, it might be more useful to test the daily image, which becomes alpha 6 tomorrow
[16:34] <charlie-tca> A lot of issues with alpha 5 cd have already fixed
[16:34] <torkiano> ok, thank you all
=== dholbach_ is now known as dholbach
[16:56] <pedro_> Ubuntu QA Meeting in ~4 minutes at #ubuntu-meeting
[16:57] <nullack> ping seb128
[16:57] <seb128> nullack: contextless ping = no pong
[16:58] <nullack> Sebastien you know what Im pinging about
[16:58] <nullack> seb128 - the bug I mailed you on
[16:58] <seb128> nullack: no, I didn't get any email from you
[16:59] <nullack> seb128 Then LP is bugged too
[16:59] <nullack> seb128 Anyway its 228981
[16:59] <nullack> bug #228981
[16:59] <ubottu> Launchpad bug 228981 in gnome-system-tools "Time and Date GUI Workflow Broken on NTP Install" [Undecided,Confirmed] https://launchpad.net/bugs/228981
[16:59] <seb128> nullack: ah, lp comment, yeah, I get some hundred emails every day
[17:00] <seb128> nullack: and I don't read g-s-t bugs ;-)
[17:00] <nullack> seb128 Now that Ive logged onto IRC especially for you, can you please cast your eye over it, and see if it can get some of that magic of yours :)
[17:01] <seb128> looking
[17:01] <nullack> seb128 thanks
[17:02] <torkiano> is bug 338977 related to kmix or to alsa?
[17:02] <ubottu> Launchpad bug 338977 in kdemultimedia "[jaunty][alpha5][kubuntu] Volume control kmix doesn't work correctly in DELL XPS 1330" [Undecided,New] https://launchpad.net/bugs/338977
[17:02] <seb128> nullack: what sort of feedback do you want?
[17:02] <seb128> nullack: it's a bug but very very low on my priority list
[17:02] <seb128> nullack: we should just drop time-admin from the default install imho and use the gnome-panel dialog
[17:02] <pedro_> hey MrKanister
[17:02] <seb128> it lacks ntp sync right now though...
[17:02] <MrKanister> hi pedro_
[17:03] <nullack> seb128 I can push it up steam if its in gnome with no debian or our patches
[17:04] <MrKanister> pedro_: I hope I am on time for the qa meeting ;)
[17:04] <seb128> nullack: it's an ubuntu patch to install ntp I think and there is nobody working on it upstream for some cycle
[17:04] <pedro_> MrKanister: you are ;-)
[17:05] <nullack> seb128 Ok, understand, you will prioritise it as needed - Ive got full confidence in ya. Just seems to me to be a silly dam bug :)
[17:06] <seb128> nullack: we have ve around 6000 silly desktop bugs on launchpad
[17:06] <seb128> nullack: would take around 80 years to fix all those with the ressources we have
=== fader_ is now known as fader
[17:06] <seb128> random number but you get the issue ;-)
[17:06] <seb128> I'm looking at ffmpeg crashing for lot of people and that sort of issue right now
[17:06] <nullack> seb128: Understand, youll prioritise like always
[17:06] <seb128> ntp seems such a detail ...
[17:07] <nullack> seb128 Yeah, and the code uses legacy 32bit capabilities from the kernel too, I bugged that as well
[17:19] <bcurtiswx> ok, ive linked bugs upstream before... why cant i find it anymore..
[17:20] <charlie-tca> bcurtiswx: what did you lose?
[17:21] <bcurtiswx> charlie-tca, this may be my dumb error for the day, one sec
[17:21]  * charlie-tca wishes for only one 
[17:22] <bcurtiswx> lol
[17:22] <bcurtiswx> charlie-tca i cant find the link to add upstream bug watch
[17:22] <charlie-tca> also affects project?
[17:22] <bcurtiswx> yeah, its an older bug... but i get errors
[17:23] <charlie-tca> Maybe it doesn't have an upstream source yet
[17:23] <bcurtiswx> its pidgin
[17:23] <bcurtiswx> i have the link to the bug report
[17:23] <bcurtiswx> theres nothing in that section to paste the link into
[17:25] <charlie-tca> If it comes up with "project name: " or similar, just type in pidgin
[17:25] <bcurtiswx> ah ha
[17:25] <charlie-tca> It should then give you the right box
[17:25] <bcurtiswx> yeah that was it... dumb me #1 today
[17:25] <bcurtiswx> well at least it happened after 12PM
[17:25] <charlie-tca> No, it is launchpad being dumb today
[17:28] <bcurtiswx> charlie-tca: thanx though
[17:28] <charlie-tca> no problem.
[17:28] <charlie-tca> Took me a long time to figure that one out
[17:57] <bcurtiswx> hey all, is there a wiki page that shows a general user how to apply a patch file
[17:58] <bdmurray> Not that I've seen
[17:59] <bcurtiswx> idk how to myself.. but someone has attached a patch to a bug report im triaging and i'd like to offer the user a page that tells them how to use it... (maybe an idea for a wiki page)?
[18:00] <bdmurray> sounds like a good idea to me
[18:00] <bcurtiswx> anyone interested?
[18:01] <bcurtiswx> if need be, i can google around for how tos and create a page... but if anyone already knows how.. it would save  me some time
[18:01] <pedro_> well there's https://wiki.ubuntu.com/Bugs/HowToFix but i don't know if that's exactly what you're looking for
[18:02] <pedro_> for general/final users i don't think we have something
[18:02] <bcurtiswx> pedro_: not really what im looking for, good link though
[18:03] <pedro_> ok
[18:03] <bcurtiswx> im looking for more like "you have a .patch file, so heres what you do with it"
[18:03] <bdmurray> bcurtiswx: you are looking for something like apt-get source $package; wget patch; patch -pX < patch; build; install test?
[18:04] <bcurtiswx> i imagine we would need appropriate warnings, so the user knows they are using it at a risk...
[18:04] <bcurtiswx> bdmurray: yeah
[18:05] <bcurtiswx> bug #184796 is the bug im triaging that has a patch
[18:05] <ubottu> Launchpad bug 184796 in pidgin "pidgin crashes with glibc error "double free or corruption"" [Medium,Triaged] https://launchpad.net/bugs/184796
[18:05] <bdmurray> bcurtiswx: why don't you add it to https://wiki.ubuntu.com/BugSquad/TODO
[18:09] <bcurtiswx> bdmurray: added
[18:13] <bdmurray> bcurtiswx: did you want to test that particular patch right away?
[18:14] <bcurtiswx> i don't personally need to, no. the patch is for the BlueT person on that bug report
[18:15] <bcurtiswx> bdmurray ^^ and I would also like to know how to do this myself ( so i can inform users how to in the future and test patches myself)
[19:29] <mrooney> There is currently no individual 5-a-day data right, although it is being logged via bug mail?
[19:30] <bdmurray> mrooney: afaik but check w/ dholbach
[19:32] <mrooney> oh boy 27 people in -bugs-announce, that is pretty good!
[19:32] <hggdh> well, take out the usual suspects before cheering ;-)
[19:33] <hggdh> but yes, some new people!
[19:34] <mrooney> hggdh: yeah, though it was down to 8-10 or so before we got a bot up and running again, and it seems to have taken a bit to creep back up
[19:35] <hggdh> mrooney, it would, not many people see fun on new bugs being announced... but slowly we are getting back
[19:35] <mrooney> I think it might be more now, I feel like it was hovering around 20 before
[19:36] <hggdh> I agree
[19:38] <salty-horse> hi. should this remain open? https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/319852
[19:38] <ubottu> Ubuntu bug 319852 in calibre "TypeError: error_dialog() takes exactly 3 arguments (2 given)" [Undecided,New]
[19:39] <hggdh> salty-horse, if the fix was indeed committed, it should be "Fix Committed"
[19:39] <salty-horse> hggdh, even if it's unrelated to the ubuntu package?
[19:40] <hggdh> salty-horse, no, not in this case. We would have to add an upstream task for the fix committed
[19:40] <salty-horse> I reported it by email.
[19:40] <salty-horse> (it's a trivial fix)
[19:41] <hggdh> thats OK
[19:41] <salty-horse> so what's the correct status? :)
[19:41] <hggdh> also, the status for the Ubuntu task should be at least triaged (and add the upstream as fix committed)
[19:42] <salty-horse> ok
[19:42] <hggdh> thanks, salty-horse .
[19:43] <salty-horse> hggdh, can you have a look now?
[19:43] <hggdh> yes
[19:44] <hggdh> salty-horse, perfect. I updated the status for Ubuntu to triaged/Importance low. Thank you for helping
[19:45] <salty-horse> thank you!
=== bcurtiswx1 is now known as bcurtiswx
[20:20] <mrooney> where do bugs go against the installer boot menu? Bug 341259 is new to me
[20:20] <ubottu> Launchpad bug 341259 in ubuntu "cannot launch install" [Undecided,New] https://launchpad.net/bugs/341259
[20:21] <bdmurray> gfxboot I think
[20:31] <mrooney> bdmurray: ah yes, that looks right based on other reports!
[20:32] <bdmurray> mrooney: yep
[21:35] <bcurtiswx> hmm, ubuntu made slashdot for a bug... that can't be that good
[21:36] <bcurtiswx> eh its good, its getting attention it may need
[21:38] <jpds> bcurtiswx: That bug already had attention..
[21:39] <bcurtiswx> jpds: yeah, i guess so.
[21:50] <pitwalker> https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/332563
[21:50] <ubottu> Ubuntu bug 332563 in gnome-panel "gnome panel keeps freezing randomly" [Medium,Confirmed]
[21:50] <pitwalker> http://bugzilla.gnome.org/show_bug.cgi?id=513347
[21:50] <ubottu> Gnome bug 513347 in window list "gnome panel freeze when opening more than 7 windows on a right panel." [Normal,New]
[21:51] <pitwalker> Opened by Oxmosys 2008-01-31 and still open! why?
[21:53] <bcurtiswx> pitwalker: are you asking us why the gnome bug is still open?
[21:54] <pitwalker> bcurtisws: yes, widescreen displays are common today
[21:54] <pitwalker> i like awn
[21:56] <bcurtiswx> pitwalker: that may be a great question for the bug itself, but this channel deals with bug reported in launchpad that are ubuntu related.
[21:56] <bcurtiswx> pitwalker: also the two bugs you listed aren't related
[22:01] <pitwalker> i'm back from the gnome-panel hang
[22:02] <pitwalker> i needed to kill the 8th window not only the gnome-panel to come back
[22:10] <bdmurray> mrooney: search for bugs in the API deals with bug tasks not bugs
[22:10] <bdmurray> mrooney: However someting like tasks = ubuntu.searchTasks(status='New',order_by="-datecreated") and tasks[0:5] should work
[22:14] <bcurtiswx> pitwalker: did you get that backtrace as requested by sebastien?
[22:23] <mrooney> bdmurray: interesting, that could work. The New criteria may or may not be desired? That will for example miss new reports that people self-confirm or someone else quickly invalidates / incompletes
[22:23] <bdmurray> mrooney: right, that just an idea
[22:24] <bdmurray> mrooney: hunh, this works too launchpad.bugs[0:5] but you'd have to ensure they had ubuntu tasks
[22:25] <mrooney> bdmurray: yeah, I wonder which approach is better.
[22:26] <mrooney> you'd have to grab more bugs with the second one, to make sure you didn't miss any ubuntu bugs
[22:26] <bdmurray> It really depends on whether you are interested in looking at bugs or bug tasks
[22:31] <bdmurray> its possible a lower bug number could get a new task that would be interesting
[22:56] <mrooney> bdmurray: yeah, that seems an advantage of the first way you mentioned, announcing those might be desirable