[01:00] <Corsario> Hi everybody
[01:00] <Corsario> I dunno if I'm the only one with problems on my sound board. Can anyone help me?
[01:03] <Corsario> When I used Ubuntu 9 it's ok, the sound work properly, but now, I formatted and installed Ubuntu 10.04 and this doesn't recognize my sound board AC97
[01:04] <micahg> Corsario: https://wiki.ubuntu.com/DebuggingSoundProblems
[01:04] <Aquina> That's a bit unlikely. Have you activated all that stuff in your mixer?
[01:05] <Corsario> In the mixer doesn't appear the hardware
[01:07] <Corsario> And the only 'exit' I have is a false exit
[01:20] <Corsario> It's hard... I tried to follow the page /DebuggingSoundProblems but I simply din't find my sound board...
[01:21] <Corsario> When I type lsmod | grep -i snd, it doesn't return anything
[04:28] <arand> There's quite a bit of new activity on Bug #329146 which I reported back in Jaunty prerelease, and had since disappeared.. Should new reproters be directed to a new bug report or should it be reopened?
[04:29] <ubot4> Launchpad bug 329146 in nautilus (Ubuntu) (and 1 other project) "nautilus unable to start on login (affects: 5) (dups: 1)" [Low,Invalid] https://launchpad.net/bugs/329146
[06:04] <shishire> I just marked bug 485225 as confirmed, and confirmed that the proposed patch does in fact fix the bug.  I've never been on this end of the bug-tracking system before, what happens now?
[06:04] <ubot4> Launchpad bug 485225 in ftgl (Ubuntu) "Won't link when using ftglGetLayoutBBox (affects: 2) (heat: 6)" [Undecided,Confirmed] https://launchpad.net/bugs/485225
[06:06] <arand> shishire: subscribe ubuntu-reviewers and add the patch tag... I think
[06:07] <persia> That's almost never right
[06:07] <persia> There's a script that does that in some cases.
[06:08] <persia> Hm.  It is right in this case.  I don't understand why :(
[06:09] <shishire> this bug is slightly unusual in that upstream probably won't respond, the original developer has been awol for almost 2 years now.  Does that change anything?
[06:09] <persia> Not really, no.
[06:09] <persia> I just don't understand why it didn't get auto-subscribed.
[06:11] <arand> Hmm, might be that the script sometimes fails...
[06:11] <persia> Indeed, although I suspect the number of cases where the team shouldn't be subscribed exceeds the number where it should.
[06:12] <arand> Hmm, is it more when there's a proper debdiff ready, that that should happen?
[06:14] <persia> No, debdiff goes to sponsors, not reviewers.
[06:16] <persia> Anyway, let's focus on the fix, rather than the potentially messy process.
[06:17] <persia> So, several things need to happen, as follows: 1) someone should make sure the patch is documented in the upstream bug in case someone else adopts upstream, and make sure the patch is known in Debian.
[06:17] <persia> 2) Someone needs to prepare an upload (for either Ubuntu or Debian) and get the patch included in the package.
[06:17] <persia> 3) Someone needs to make sure that the upload is included in the latest Ubuntu release.
[06:18] <persia> shishire: How much of that are you up for doing?  Any?  All?
[06:18] <lithper1_> somebody submitted a new package request (https://bugs.launchpad.net/ubuntu/+bug/486914), this request has been granted, and a new package crated. however, the status is still "New". is this normal?
[06:18] <ubot4> Launchpad bug 486914 in ubuntu (and 1 other project) "[needs-packaging] Create package: J (affects: 1) (heat: 6)" [Wishlist,New]
[06:18] <persia> lithper1_: Yep: it's a bug in the way that changelog-closes-bugs works.  Just mark it Fix Released if the package is now available in Ubuntu.
[06:18] <shishire> I'll document upstream.  That's easy.  I don't know how to do 2 and 3, but I'm willing to do so if someone can explain how
[06:19] <thekorn> good morning
[06:20] <ddecator> morning thekorn
[06:20] <thekorn> hey ddecator
[06:25] <persia> shishire: Great.  Thanks.  There's a high chance that 2) can be inspired by a well-written Debian bug with the patch attached, in which case 3) may be just a matter of tracking the status.  Please feel free to ask if it seems stuck again.
[06:26] <shishire> There's currently no bug reports for the package in debian.  Create a new one, upload the patch, and note it's fixed down in Ubuntu?
[06:26] <persia> Well, except that it's *not* fixed in Ubuntu :)
[06:26] <persia> But yeah, create a new bug report, and attach the patch.
[06:26] <shishire> ok
[06:26] <shishire> I'll link to the ubuntu report, and try to add it as a watch
[06:27] <persia> Most of the time the maintainer will include available patches in the next upload.  if that doesn't happen for a while, then it's worth seeing about including it in Ubuntu (but it's lots of extra work to include in Ubuntu and then have to uninclude it later once it's included in Debian)
[06:28] <shishire> ummm...does "This source is not published in Debian" mean that the debian upstream doesn't have the ability to patch it?
[06:28]  * persia gets confused, and looks harder
[06:29] <shishire> oh... wrong bug tracker
[06:29] <persia> It is so published in Debian: http://packages.qa.debian.org/f/ftgl.html
[06:30] <persia> Heh.  Right.  patch to sourceforge in the existing bug, patch to Debian in a new bug.
[06:30] <persia> Make sure there are LP watches for both bugs.
[06:41] <dholbach> Development and MOTU Q&A Session in #ubuntu-classroom in 20m
[07:14] <shishire> ok, pushed it upstream: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=580451 .  I'll check on it tomorrow
[07:14] <ubot4> Debian bug 580451 in libftgl-dev "libftgl-dev: Typo in FTLayoutGlue ftglGetLayoutBBox()" [Normal,Open]
[07:17] <persia> shishire: Thanks!
[07:18] <shishire> this process has interested me.  I'm signing up to join the bugsquad, and I'll see if I can't help squash some bugs :D
[07:20] <ddecator> shishire: good to hear! =D
[08:00] <persia> it's Patch Day!  Anyone with time to help review patches, please come to #ubuntu-reviews and join in!
[08:02] <zus> when are patch days?
[08:03] <ddecator> bah, i need to help out with one of those sometime..
[08:03] <persia> Once in a while.  This is the first one, and no firm regular schedule has been determined.
[08:04] <persia> ddecator: Well, since nobody knows when the next one will occur, you might want to jump in today :)
[08:04] <ddecator> persia: does it go the whole day?
[08:05] <persia> ddecator: It's for the entirety of 5th May, anywhere on the globe, which means it ends in about 4 hours.
[08:05] <ddecator> persia: i'm about to go to bed =(
[08:06] <persia> Well, you can try to review one quick before you sleep, or you can stop by another day (although there might not be as many people working with you at the same time).
[08:07] <ddecator> not enough time unfortunately, but i'll hop in the channel and see if i can't help here and there
[08:12] <baptistemm> hello
[08:12] <ddecator> hey baptistemm
[08:15] <zus> i just caught up,... patch day is all of may 5th?
[08:15] <persia> Yep.
[08:16] <zus> hehe for the last 3 hours its been may 6th. talk about being a day late and a buck short
[08:16] <persia> 3 hours?  Depends where you are.
[08:16] <nasevz> hi
[08:17] <persia> It's still 5th May in some places, so there's a few more hours to go.  We'll keep at it until 5th may hits the international date line, and is no more.
[08:17] <zus> us eastern time. i think its -5 from UTC
[08:17] <baptistemm> heya ddecator
[08:17] <baptistemm> hello persia
[08:17] <persia> Hey baptistemm
[08:19] <nasevz> How can I report a bug when system is not bootable? I have the same bug as reported in forums http://ubuntuforums.org/showthread.php?t=1457176 (No boot after kernel upgrade to 2.6.32-21 on Lucid Beta2)
[08:19] <nasevz> the same problem is with 2.6.32.22 kernel
[08:20] <zus> well, im header to bed, before i fall asleep on the keys, wich i havent done since world of warcraft -
[08:21] <zus> nighterz
[08:21] <zus> persia, thanks for the info on the patch days
[08:21] <persia> zus: Happy to share.  The reviewers team always appreciates help, even on non-patch days, so drop by another day if you like.
[08:22] <zus> i saved the room =)
[08:24] <persia> nasevz: I'll recommend starting with `ubuntu-bug linux` once you got the system booted.
[08:27] <nasevz> ok, but I can't boot it with 2.6.32.21 or 2.6.32.22. If I boot with kernel that does work, I guess the bug would not be in the report.
[08:42] <persia> nasevz: Yeah, but I'm not sure how else to get the information about the machine the kernel team wants into the report.
[08:55] <BUGabundo_remote> triim triim, triim triim
[09:20] <arand_> persia: (Hmm, likely more appropriate here): So it's sponsors rather than -sru that should be subscribed there? If so are you able to unsubscribe them? (I don't seem to be able now...)
[09:24] <arand_> Also, should the plymouth taks be marked confirmed high as well, should I open Lucid tasks for it? And since there's two bugs, subscribe both or only one? The one which has loads of affected and steve assigned to it, or the one where the debdiffs and the testing reports are?
[09:25] <persia> -devel is appropriate.  I can unsubscribe sponsors, but not sru.
[09:27] <persia> But it looks like both should be subscribed in this case, as the SRU procedure says to subscribe the SRU team, and then upload, and if one can't upload, one subscribes the sponsors team to have someone else upload it.
[09:39] <arand_> persia: Ok, Should I mess with the status and open lucid tasks for the 571707 bug, and should I subscribe sponsors and sru to 553745 as well?
[09:40] <persia> For SRU, you need to mess with status and nomination.
[09:41] <persia> It's probably better to have the sponsors only subscribed to one bug (with the upload candidate that fixes both).
[09:41] <persia> But the SRU team would be subscribed to both bugs.
[09:47] <arand_> Ok, hope that turned out right now (seems the lucid tasks were already there), dunno if I shouldto request the "high" priority of the new plymouth task in 571707 from someone here?
[10:00] <persia> bug #571707
[10:00] <ubot4> persia: Bug 571707 on http://launchpad.net/bugs/571707 is private
[10:01] <persia> Well, shouldn't be private if it's an SRU bug.  Might need privacy review :)
[10:01] <persia> Says public on the bug report though, so maybe the bot is confused.
[10:02] <Laibsch> How do I mark bug 48708 as affecting the Japanese Kaizen project (https://launchpad.net/ubuntu-jp-improvement/) ?
[10:02] <ubot4> Launchpad bug 48708 in evince (Ubuntu) "evince should Suggests xpdf-japanese (or poppler-data when it'll be available) (affects: 2) (dups: 1) (heat: 4)" [Wishlist,Triaged] https://launchpad.net/bugs/48708
[10:02] <persia> arand_: Let's wait for someone to approve the lucid nominations first.
[10:02] <Laibsch> When I click on "affects project" it wants to link in upstream
[10:03] <persia> Have you tried the "Choose another project" link?
[10:04] <persia> But I don't see the point: adding Suggests won't help.
[10:04] <persia> In fact, it's duplicate to something else
[10:04]  * persia hunts
[10:04] <Laibsch> I agree that suggests won't help
[10:05] <Laibsch> I'm not necessarily advocating any solution
[10:05] <BUGabundo_remote> who in here is supporting chromium besides fta?
[10:05] <Laibsch> that ticket for me is about "evince on Ubuntu" has broken Japanese support in a normal installation
[10:05] <persia> OK.  Generally we don't tend to use alsp-affects that much for the Kaizen project: many of the Kaizen bugs are in Japanese, and end up being translated (as new bugs).
[10:06] <Laibsch> I'm not familiar with how things are currently done
[10:06] <Laibsch> But I think the most sensible thing is to indeed translate the bug
[10:06] <Laibsch> and then either mark as dupe or do the translation in the original report
[10:07] <Laibsch> I did mark bug 190609 as dupe to bug 432736 a few days ago
[10:07] <ubot4> Launchpad bug 190609 in ubuntu-jp-improvement "firefox＋CUPS-PDF で日本語のファイル名が扱えない。 (dup-of: 432736)" [Medium,Triaged] https://launchpad.net/bugs/190609
[10:07] <persia> Translations in original reports breaks the Ubuntu bugs standard practice.
[10:07] <ubot4> Launchpad bug 432736 in cups-pdf (Ubuntu) "cups-pdf chokes on non-ascii characters in filenames (affects: 1) (dups: 1) (heat: 16)" [Low,Confirmed] https://launchpad.net/bugs/432736
[10:07] <Laibsch> and now it's gone from the Kaizen overview
[10:07] <persia> Marking as duplicates hides stuff.
[10:07] <Laibsch> which is not good
[10:07] <Laibsch> it should still be there
[10:07] <Laibsch> IMHO
[10:08] <persia> Which is why duplicates aren't used for this.
[10:08] <persia> You might want to chat with nobuto or hito_jp about how the bugs in the Kaizen project are managed.
[10:08]  * persia undupes 190609
[10:09] <Laibsch> NOOO
[10:09] <persia> Why?
[10:09] <Laibsch> what's the use?
[10:09] <Laibsch> Look at the line I just added to the description
[10:09] <Laibsch> that's how it should be done
[10:10] <persia> For all 300 languages?
[10:10] <Laibsch> there's no use creating another Japanese island
[10:10] <Laibsch> with a bunch of ticket that don'T get fixed in Ubuntu proper
[10:10] <persia> That's not what that is.
[10:10] <Laibsch> but only make it in the Japanese remix
[10:10] <persia> There are an active set of folks that work on fixing those bugs in Ubuntu proper.
[10:11] <persia> And, generally, *every* triaged bug against the Kaizen project ends up being duplicate of some regular Ubuntu bug.
[10:11] <Laibsch> yes
[10:11] <persia> Which is by intent.
[10:11] <Laibsch> and they should clearly show that relation
[10:11] <Laibsch> sure
[10:11] <persia> Launchpad doesn't support that.
[10:12] <Laibsch> sure
[10:12] <Laibsch> sure it does
[10:12] <Laibsch> nobody prevents you from continuing discusion in a duped bug
[10:12] <persia> Not in original language.  Anyway, please don't, or if you do, first confirm with nobuto and hito_jp that it is a desired change to the model.
[10:12] <Laibsch> and then somebody can bubble up a translation to the main, English-language ticket
[10:12] <persia> It doesn't work that way, because of how Malone notifications get sent.
[10:13] <Laibsch> ?
[10:13] <persia> So folks end up getting all the updates to *all* the dupes via email.
[10:13] <persia> And they complain about this when they can't read it.
[10:14] <Laibsch> so what
[10:15] <persia> So, the entire *point* of the Kaizen project is to allow folks who don't want to get the English updates to avoid it.
[10:26] <Laibsch> are you sure about that?
[10:26] <Laibsch> I thought it was the other way round
[10:26] <persia> How do you mean?
[10:27] <Laibsch> to have a safe heaven for the always-frightened-of-English crowd to express themselves freely
[10:27] <Laibsch> that's been my understanding
[10:27] <persia> Right, which is why it's not interesting to duplicate the bugs, because then that crowd gets the updates to the Ubuntu task as well, which frightens them.
[10:28] <persia> (because of how Malone notifications work)
[10:28] <Laibsch> I don't think so
[10:28] <Laibsch> I know they will get more mails
[10:28] <Laibsch> But I don't think it will frighten them
[10:28] <Laibsch> as long as they know they have their little "Japanese garden" where they are not expected to be talking English
[10:29] <Laibsch> so, this caters to all three types:
[10:29] <Laibsch> a) Japanese frightened of English
[10:29] <Laibsch> b) those comfortable with both camps
[10:29] <Laibsch> the gatekeepers
[10:29] <Laibsch> c) those not capable to speak English (most of the devs)
[10:30] <Laibsch> currently b) are not well-served and they are critical IMHO, because they are the ones breaking up the Japanese island
[10:30] <Laibsch> and getting things into the mainstream, Ubuntu proper
[10:30] <persia> I think that this is more on-topic in -jp : that said, the issue is that mail gets send in incomprehensible languages to some or other folks.
[10:37] <Laibsch> I get that all the time ;-)
[10:38] <Laibsch> usually has something about "stick" or "pole" in the subject
[10:38] <Laibsch> haha
[11:05] <pune> hey boys, ive got a really annoying bug in the new ubuntu 10.4
[11:05] <pune> hopefully somebody here knows how to fix it
[11:05] <pune> i was using 9.10 AMD64 and everything was fine.  then i let it update to 10.4.  and now my keyboard and mouse dont work
[11:06] <pune> they work in grub as i can select different kernels to boot.  but once ubuntu starts, they arent recognized
[11:06] <BUGabundo_remote> its 10.*0*4
[11:07] <BUGabundo_remote> please try #ubuntu for support pune
[11:07] <pune> so this isnt considered a bug?
[11:10] <BUGabundo_remote> if you can't use it, it might
[11:10] <BUGabundo_remote> ... left
[11:27] <joaopinto> hi
[11:27] <joaopinto> how do we enable apport ?
[11:28] <BUGabundo_remote> humm
[11:28] <BUGabundo_remote> something in the defaults
[11:28] <BUGabundo_remote> echoing an 1 there , somewhere
[11:29] <baptistemm> it's explained in the wiki
[11:29] <persia> /etc/default/apport isn't it?
[11:29] <baptistemm> I guess
[11:29] <joaopinto> well, that doesn't seem to work
[11:29] <thekorn> https://wiki.ubuntu.com/Testing/EnableProposed has an "enable apport"-section
[11:29] <joaopinto> I mean
[11:29] <joaopinto> isn't it supposed to change ulimit -c ?
[11:29] <joaopinto> it didn't catch my crash and ulimit -c is set to 0
[11:30] <joaopinto> janito@janito-desktop:~$ initctl list | grep apport
[11:30] <joaopinto> apport start/running
[11:30] <joaopinto> is there an apport daemon that should be running ? I can't find it on the process list
[11:41] <joaopinto> hum, it is working per the sh -c 'kill -SEGV $$' test
[11:44] <charlie-tca> There are things apport won't catch
[11:45] <joaopinto> is not catching whatever is crashing gnome-settings-daemon :|
[11:45] <charlie-tca> what about a gdb backtrace while running?
[12:04] <yofel> iirc was checking for kernel segfault notifications, if apport catches a crash you should have a segfault message in dmesg
[12:04] <yofel> *apport was  checking...
[12:05] <joaopinto> charlie-tca, it crashes on the gnome session startup
[12:10] <thekorn> qense, happy birthday ;)
[12:11] <qense> thekorn: thanks! :)
[13:11] <BUGabundo_remote> uuuhh cake
[13:11] <BUGabundo_remote> I mean, Happy b'day qense
[13:12] <BUGabundo_remote> would help if he was here :(
[13:16] <charlie-tca> Hello, BUGabundo_remote
[13:17] <charlie-tca> Why did you wait until he left?
[13:17] <charlie-tca> ;-)
[13:17]  * charlie-tca runs to hide again
[13:19] <BUGabundo_remote> I was having lunch
[13:19] <BUGabundo_remote> just came back charlie-tca
[13:19] <BUGabundo_remote> I sent him a dent
[14:40] <cshong> Hello! I hope someone can help me. Situation is like this: I reported a linux kernel bug #575783  at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/575783  . Someone leave comments and want me to test whether the bug has been fixed in the latest kernel mainline built, then post  the result. But, I am not be able to fullfill the request because after I install the latest kernel mainline build, my computer will freeze if I
[14:40] <ubot4> cshong: Bug 575783 on http://launchpad.net/bugs/575783 is private
[14:40] <ubot4> Launchpad bug 575783 in linux (Ubuntu) "Cannot eject DVD/CD-ROM drive with the hotkey button (affects: 1)" [Undecided,Incomplete]
[14:41] <cshong> So, what can I do?
[14:42] <greg-g> I believe you were cut off, cshong, the last I saw was "my computer will freeze if I"
[14:42] <cshong> my computer will freeze if I boot Ubuntu with the latest mainline build.
[14:43] <greg-g> ah
[14:43] <greg-g> obvious enough :)
[14:49] <cshong> That means for the bug #575783, I cannot do what had been requested due to the freeze caused by the latest kernel mainline built. How can I tell him/her (the person who leave comment on the bug to request it) about this?
[14:49] <ubot4> Launchpad bug 575783 in linux (Ubuntu) "Cannot eject DVD/CD-ROM drive with the hotkey button (affects: 1)" [Undecided,Incomplete] https://launchpad.net/bugs/575783
[14:52] <greg-g> cshong: I believe you did already, you have left a comment to that affect on the bug 5 hours ago, correct?
[14:52] <ubot4> greg-g: Bug 5 on http://launchpad.net/bugs/5 is private
[14:55] <cshong> Ya. But I worry if he/she not see it. Never mind, I am very patient, I will wait for a few days for someone to reply.
[14:59] <greg-g> cshong: you can also join the #ubuntu-kernel channel and see if they have any suggestions on next steps to diagnose.
[15:00] <cshong> Joined before, but my message cannot be sent. don't know why.
[15:01] <greg-g> cshong: what error did you get?
[15:01] <greg-g> when trying to talk in the -kernel channel
[15:01] <cshong> Cannot send to channel: #ubuntu-kernel
[15:04] <cshong> The above are the error message I receive when sending message to the channel.
[15:04] <yofel> cshong: I'm just guessing, but are you registered?
[15:05] <cshong> Not. Need to register?
[15:05] <greg-g> cshong: do you see the conversation happening in -kernel right now?
[15:05] <yofel> hm, but the channel mode shouldn't require that :/
[15:06] <cshong> Yes, I did see someone chatting in the channel.
[15:10] <cshong> Same thing happen after I leave and join again.
[15:10] <ogra> weird
[15:10] <ogra> ask in #ubuntu-ops
[15:16] <cshong> Well, never mind. It is late night in my country now. I will ask tomorrow.
[15:16] <persia> Try again: the mode ws just changed.
[15:17] <cshong> Ok now trying.
[15:31] <vish> hrm , seems "Fred" has been going around on a tagging spree ;)
[15:31] <greg-g> vish: yep, I got a few
[16:43] <Laibsch> can sombody please have a look if bug 441756, bug 456846 and bug 475901 are dupes?
[16:43] <ubot4> Laibsch: Bug 441756 on http://launchpad.net/bugs/441756 is private
[16:43] <ubot4> Laibsch: Bug 456846 on http://launchpad.net/bugs/456846 is private
[16:43] <ubot4> Laibsch: Bug 475901 on http://launchpad.net/bugs/475901 is private
[16:45] <persia> certainly look like dupes to me
[16:46] <Laibsch> same request for bug 403277, bug 403876, bug 393980 and bug 403714
[16:46] <ubot4> Laibsch: Bug 403277 on http://launchpad.net/bugs/403277 is private
[16:46] <ubot4> Laibsch: Bug 403876 on http://launchpad.net/bugs/403876 is private
[16:46] <ubot4> Launchpad bug 393980 in scim (Ubuntu) "scim-launcher crashed with SIGSEGV in _Unwind_DeleteException() (affects: 1) (dups: 1) (heat: 11)" [Medium,Triaged] https://launchpad.net/bugs/393980
[16:46] <ubot4> Launchpad bug 403714 in scim (Ubuntu) "scim-launcher crashed with SIGSEGV in _Unwind_DeleteException() (affects: 3) (heat: 10)" [Medium,New] https://launchpad.net/bugs/403714
[16:46] <Laibsch> how does one determine the "dupeness"?
[16:46] <Laibsch> persia: thanks
[16:46] <persia> For crashes, I tend to check to make sure it's crashing at the same codepoint for the same reason.
[16:46] <persia> But it really depends on the bug.
[16:47] <persia> In all three of these cases, the stacktraces appear to have the same issue, so I'm guessing there's an incorrect cast or unsafe assignment happening.
[16:49] <Laibsch> OK
[16:50] <Laibsch> I think I understood that enough to be able to check myself in the future
[16:52] <Laibsch> persia: so, the other four would be dupes, as well, right?
[16:53] <persia> The other four?
[16:54]  * Laibsch hugs lp-set-dupe
[16:54] <Laibsch> same request for bug 403277, bug 403876, bug 393980 and bug 403714 <- those four
[16:54] <ubot4> Laibsch: Bug 403277 on http://launchpad.net/bugs/403277 is private
[16:54] <ubot4> Laibsch: Bug 403876 on http://launchpad.net/bugs/403876 is private
[16:54] <ubot4> Launchpad bug 393980 in scim (Ubuntu) "scim-launcher crashed with SIGSEGV in _Unwind_DeleteException() (affects: 1) (dups: 1) (heat: 11)" [Medium,Triaged] https://launchpad.net/bugs/393980
[16:54] <ubot4> Launchpad bug 403714 in scim (Ubuntu) "scim-launcher crashed with SIGSEGV in _Unwind_DeleteException() (affects: 3) (heat: 10)" [Medium,New] https://launchpad.net/bugs/403714
[16:54] <Laibsch> I've already marked them dupe now
[16:55] <persia> Looks like that to me.
[16:56] <persia> Note that you can't just look at the very top of the stacktrace, but have to go back a couple steps.
[16:56] <Laibsch> lp-set-dupe doesn't do anymore what it was conceived for :-(
[16:56] <persia> Sometimes you'll end up with 10 bugs that all crash in, say doit(), but doit() is being called unsafely in 4 different places, while it is itself a safe function, making it 4 bugs.
[17:19] <JFo> so, where do you think bug 576066 should go? It is quite obviously not a kernel issue.
[17:19] <ubot4> Launchpad bug 576066 in linux (Ubuntu) "ums_cypress missing from lucid server cd (affects: 1)" [Undecided,Triaged] https://launchpad.net/bugs/576066
[17:29] <persia> JFo: I'd say ubuntu-meta: it's really a seeds issue, but that's the closest package.
[17:30] <JFo> hmmm, ok thanks persia :)
[17:30] <persia> JFo: That said, this is only true if there exists a package that contains that driver.
[17:30] <JFo> ok
[17:30] <persia> If that driver isn't provided by a *different* package, then it is linux that should be providing it (either inside the modules package, or in a separate package)
[17:33] <JFo> sounds good to me. Thanks persia
[17:34] <persia> Sorry I don't know enough about the driver in question to give a clearer answer :)
[17:35] <BUGabundo_remote> yofel: wasn't it supposed to open +1 today?!
[17:35] <yofel> believing Pici yes
[17:36] <BUGabundo_remote> will wait a few more hours
[17:36] <hggdh> seems to be open, but needs invitation
[17:36] <persia> https://launchpad.net/ubuntu/maverick still says "Pre-release Freeze", so it might be early yet.
[17:37] <charlie-tca> I was thinking tomorrow, if the toolchain uploads today
[17:39] <BUGabundo_remote> booo
[17:40]  * charlie-tca back to hiding then... ;-)
[18:47] <MrKanister> Hi there. Could someone please renew my Ubuntu Bug Control membership? Thanks in advance.
[18:47] <MrKanister> My launchpad page is https://launchpad.net/~mrkanister
[18:49] <shishire> If a bug report is in spanish, at it's about the spanish translation of the ubuntu docs, does it need to be translated into english?
[18:50] <shishire> s/at/and
[18:55] <DrKenobi> shishire :-/
[18:55] <shishire> ?
[18:56] <DrKenobi> i am thinking, but i dont know what to say to you. Gran duda...
[18:59] <shishire> I noticed a lot of bugs got submitted in spanish over in the #ubuntu-bugs-announce channel.  I took a look, and at least some of them are translation issues, so I've been "also affects" ubuntu-translations, but I don't know whether I should also either translate the text or ask for a translation.
[19:00] <jbicha> pedro_: thanks for your Open Week session, you motivated me to finally apply for Bug Control
[19:00] <yofel> pedro_: nice session :)
[19:00]  * yofel hugs pedro_
[19:00] <pedro_> jbicha, awesome! looking forward to see your application there ;-)
[19:00] <balachmar_> ghe ghe I'm also here to do some bugs :)
[19:00]  * pedro_ hugs yofel 
[19:01] <shishire> balachmar_, I hope you mean fix, although the alternative might be amusing
[19:01] <pedro_> cool, please do look into the mentoring program if you're new with the bug triaging
[19:01] <pedro_> it's an awesome way to start
[19:02] <Salvad1> Hello. Can anyone replicate this before submitting?
[19:02] <balachmar_> shishire: Well, triage bugs first... fixing them well if I can...
[19:02]  * pedro_ -> lunch
[19:03] <Salvad1> Is gksudo in a terminal emulator.
[19:03] <Salvad1> Is gksudo synaptic in a terminal emulator.
[19:03] <shishire> balachmar_, I meant as opposed to creating bugs :P
[19:03] <Thiago-Br> is anyone using empathy right now?
[19:03] <hggdh> Salvad1: replicate what?
[19:04] <Salvad1> I got: "sudo: 3 incorrect password attempts" after an non correct one.
[19:04] <hggdh> Salvad1: known bug
[19:04] <Salvad1> Good to know.
[19:04] <Salvad1> And reported?
[19:05] <hggdh> Salvad1: yes, I am looking for it now
[19:05] <yofel> Thiago-Br: not really, but what's the issue?
[19:05] <balachmar_> shishire: Well I guessed as much :)
[19:06] <Thiago-Br> i'm not able to stop the automatic rolling
[19:06] <Thiago-Br> of any chat
[19:07] <Thiago-Br> sorry auto scrolling
[19:08] <jbicha> Thiago-Br: that's how empathy works, perhaps in a future release that will be fixed
[19:08] <bdrung_> jcastro: rdenis (lp name) is an upstream dev who triages a lot of vlc bugs. he should gain the right to set all statuses and see private bugs.
[19:08] <jcastro_> bdrung_: sure
[19:08] <jcastro_> has he signed the CoC?
[19:08] <Thiago-Br> oh, so this issue is known, right
[19:08] <Thiago-Br> good
[19:08] <jbicha> Thiago-Br: you could try installing pidgin instead if empathy annoys you too much
[19:09] <bdrung_> jcastro: yes
[19:09] <jcastro_> bdrung_: ok
[19:10] <jcastro_> bdrung_: do you talk to him regularly? Basically he just needs to know to not triage bugs for projects he's not a part of, since it's not that granular
[19:10] <Thiago-Br> jbicha: thanks, i know pidgin, i'm just giving empathy a try
[19:11] <bdrung_> jcastro: sometimes. not regularly.
[19:11] <DrKenobi> can anyone who know spanish read this? http://ubuntuone.com/p/2YX/ Its a "guide" to report bug i made while i am learning to report bugs. Opinions?
[19:11] <jbicha> Thiago-Br: I try empathy every so often hoping, but it's not usable enough for me yet
[19:11] <jcastro_> bdrung_: ok I'll just send you a mail.
[19:11] <jcastro_> bdrung_: I mean, send him a mail. :D
[19:11] <bdrung_> thanks
[19:12] <jcastro_> bdrung_: upstreams who want to do bugwork in ubuntu are more than welcome, keep em coming. :D
[19:13] <Thiago-Br> jbicha: are empathy and pidgin ready for msn video calls? (i know emesene)
[19:14] <jbicha> Thiago-Br: sorry, I don't use MSN (just IRC & XMPP), but I've heard both apps do video now
[19:15] <om26er> Thiago-Br, none do msn now. empathy did then microsoft changed something on their server side and now no audio/video calling for MSN :(
[19:17] <Thiago-Br> om26er: no, emesene can do
[19:17] <om26er> Thiago-Br, video only
[19:17] <Thiago-Br> ???
[19:17] <bdrung_> jcastro: when sending him a mail, please CC me. i appreciate upstream helping triaging bugs.
[19:18] <Thiago-Br> video, voice and obviously, chat
[19:19] <Thiago-Br> jbicha: thanks, i would rather to use only xmpp instead of msn but here in Brazil msn is the most used (yet, i hope)
[19:19] <om26er> Thiago-Br, http://kakaroto.homelinux.net/2010/03/amsn-0-98-2-to-be-released-without-audiovideo-support/ applied to emesene too afaik
[19:23] <Thiago-Br> om26er: hahaha microShitf
[19:24] <om26er> ooo
[19:26] <Thiago-Br> Steve Balmer have been in Brazil a few days ago and told that the brazillian policy of supporting open source software and linux is wrong and the correct is to take a more neutral position about it
[19:27] <balachmar_> :)
[19:27] <charlie-tca> but... steve balmer will say whatever he needs to in order to keep users
[19:28] <Thiago-Br> of course
[19:29] <DrKenobi> funny people this windows users
[19:35] <BUGabundo> funny... haven't use u1 for ages.. not I login, change a share, and now its 404 :|
[19:36] <DrKenobi> u1 its not workking proporly
[19:37] <BUGabundo> tell me about it :)
[19:39] <kklimonda> well, it's slow but it should work just fine
[19:39] <kklimonda> the 404 sounds scary
[19:39] <kklimonda> BUGabundo: u1 got decent in last months, you should probably give it a try.
[19:39] <DrKenobi> yes, its much better now!
[19:40] <kklimonda> it's almost up to par with with dropbox ;)
[19:41] <DrKenobi> U1 --> Internal Server Error
[19:41] <DrKenobi> ahh
[19:42] <BUGabundo> ahah
[19:42]  * yofel misses the *sync now* button :/
[19:43] <yofel> it's nice that it syncs in the background but I can't figure out when it does it, and if I want to have it sync before I shut down I don't know how...
[19:45] <DrKenobi> yofel, i was thinking the same today
[19:46] <BUGabundo> I never care about that with dropbox
[19:46] <BUGabundo> it circles around when syncing and has a list of changes
[19:47] <charlie-tca> I finally dropped u1 because I can't get it to sync on more than one system
[19:49] <DrKenobi> u1 is working now
[19:51] <DrKenobi> not anymore
[19:52] <BUGabundo> ahahahahaha
[21:45] <GeekSquid> User Interface bug reported in #ubuntu, on Live Disk screensaver needs to be turned off by default in 10.04.2, the screensaver activates and locks the screen on the live disk, and as there is no password, you cannot unlock the screen.
[21:51] <jeandaniel> hello, my Lucid system can't reboot, after a system upgrade including an upgrade of grub. The upgrade was done from a console, and I could read a big scary message about grub on gpt being unreliable (in capital)
[21:52] <jeandaniel> my laptop is a macbook with gpt and bootcamp, I think it is a common setup, are there other users impacted? would you have a piece of advice to make this system boot again?
[21:53] <jeandaniel> any recomfort ... :(
[21:53] <micahg> !support  | jeandaniel
[21:53] <ubot4> jeandaniel: The official ubuntu support channel is #ubuntu. Also see http://ubuntu.com/support and http://ubuntuforums.org
[21:54] <BUGabundo> muaau micahg
[21:55] <joaopinto> GeekSquid, I can't reproduce that
[21:55] <micahg> BUGabundo: muaau?
[21:55] <jeandaniel> yeah, break my laptop and lead me to professional support plan ...
[21:56] <micahg> jeandaniel: #ubuntu is free
[21:56] <micahg> jeandaniel: we help file and triage bugs in here
[21:57] <GeekSquid> joaopinto: strange, KimK in #ubuntu reported it, what are the default settings for the screensaver in Lucid, is it set to lock the screen? KimK may have checked lock screen unknowingly, I believe lock screen should be uncheckable on the live disk
[21:57]  * persia thought it might be Bug #527833 (which could use more information)
[21:57] <ubot4> Launchpad bug 527833 in grub2 (Ubuntu) "After grub-pc is upgraded on my SSD with GPT, it no longer has a BIOS Boot Partition until I manually chroot in and set it myself (affects: 1)" [Undecided,New] https://launchpad.net/bugs/527833
[21:57] <jeandaniel> micahg: please spare me
[21:57] <micahg> jeandaniel: take a look at the bug persia just posted
[21:58] <joaopinto> GeekSquid, the lock is set, but since there is no password it doesn't ask you for a password to unlock
[21:58] <persia> jeandaniel: Hrm?  No really, we focus on tracking and coordinating bugs here.  Workarounds are usually handled by the #ubuntu crew.
[21:58] <persia> That doesn't mean we can't help you determine which bug you have and what information is required to get it investigated, but it does mean that we're not well-prepared to actually solve your issues directly.
[21:59] <persia> (and it's to get more information about the issue and make sure it got into a bug report that I suggested you come here)
[21:59] <micahg> jeandaniel: I apologize, I didn't know you were directed here
[22:00] <jeandaniel> no problem, I read the bug report, I am not sure it is adapted since it is three month old while my system was updated a few minutes ago.
[22:00]  * persia suspects not enough folk have GPT disks
[22:01] <persia> jeandaniel: Ah, and your system worked fine until *very* recently?
[22:01] <jeandaniel> it is an update from an hour ago
[22:01] <GeekSquid> joaopinto: strange, I'll look into this further, although I don't expect to get anywhere, probably something the user did to make it do that, so long for now
[22:01] <GeekSquid> joaopinto: thanks for your triage time
[22:01] <jeandaniel> my system is an up to date Lucid system. installed from scratch at 9.10
[22:02] <persia> Have you found a workaround that lets you boot, or are you completely unbootable?
[22:03] <micahg> persia: last kernel update had at least 2 GPT changes
[22:03] <jeandaniel> i face the bootcamp menu: grey background and two icons
[22:03] <persia> micahg: Yeah, and also https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/508173 changed which may have moved the issue :(
[22:03] <ubot4> Launchpad bug 508173 in grub2 (Ubuntu Lucid) (and 2 other projects) "postinst has errors with grub-probe that cause the system to stop booting (affects: 1) (heat: 16)" [Medium,Fix released]
[22:03] <jeandaniel> when I click on the linux icon labelled "windows", I expect to see the grub first stage but the screen show no changes
[22:04] <persia> That seems more like grub than the kernel, but I may be mistaken.
[22:04] <jeandaniel> it is completely unbootable for an experienced linux user
[22:05] <ddecator> maybe try reinstalling grub using a live CD?
[22:05] <ddecator> idk if that works differently on macs
[22:05] <jeandaniel> yes this is the enxt step, I am not an expert in grub tools though
[22:06] <jeandaniel> there was an explicit error message on aptitude saying "grub is unreliable in GPT mode"
[22:06] <persia> Well, making it boot is easy: boot off alternate media, and give it a funny kernel command line.
[22:06] <persia> But there's probably *lots* of folks that will run into this (at least all recent Apple hardware)
[22:06] <jeandaniel> this was in capital, so I expect the bug in the grib upgrade
[22:06] <arand> If preparing an SRU from version 2.14 (of mountall), should the version number be 2.14-0ubuntu1? ubuntu0.1?
[22:07] <persia> So we ought try to get a bug filed, which kinda means figuring out what bit to file agianst, and what information to add.
[22:07] <persia> arand: -devel would likely be a better place for that sort of question.  I think it's 2.14.1 (because it's special for mountall).
[22:07] <jeandaniel> if there was a bug in the kernel I think I would have seen the grub menu
[22:07] <persia> arand: I believe mountall is differnt than most pacakges that way.
[22:08] <arand> persia: Ok, will reask, thanks
[22:08] <persia> Anyone done some grub triage?  What information do we need?
[22:12] <persia> Nobody?
[22:12] <ddecator> =\
[22:13] <persia> Looking at some other bugs against grub2, it seems like there's no apport hook for it.
[22:13] <persia> Anyone else have GPT hardware available to confirm?
[22:16] <jeandaniel> persia: maybe you should tell people with GPT hardware a simple test before asking them to upgrade and confirm
[22:17] <persia> What sort of test do you suggest?
[22:18] <persia> Basically, I'm hoping one of the folk regularly about can replicate and try to get fixed, so you can safely apply a workaround and get on with whatever you do with Ubuntu.
[22:18] <persia> If you're up for just filing the bug and waiting for developer feedback, that works too, but that might mean an extended time (especially since many developers are preparing for a week-long conference next week).
[22:18] <jeandaniel> persia: I am concerned about people not being able to reboot after the confirmation
[22:19] <persia> jeandaniel: When was the last time you updated before the recent one that caused the issue?
[22:20] <jeandaniel> persia: less than a week for sure. I am up for anything helpful for me and for you
[22:20] <yofel> while we're at grub, bug 576245 -> wth?
[22:20] <ubot4> Launchpad bug 576245 in ubuntu (and 1 other project) "can't start multiple os after installing 10.4 (affects: 1)" [Undecided,New] https://launchpad.net/bugs/576245
[22:21] <persia> Hrm.  I'm just noticing the update was published 3rd May, so wondered if it was something else, but "less than a week" makes me think it's grub2 1.98-1ubuntu6
[22:25] <jeandaniel> Does someone know which handy bootable system could fit on a 100 MB usb key (the only removable media available at this time)?
[22:26] <persia> http://archive.ubuntu.com/ubuntu/dists/lucid/main/installer-i386/current/images/netboot/mini.iso
[22:26] <persia> Note that I'm *not* sure if that works with usb-creator
[22:27] <persia> Nor have I ever figured out how to get Apple hardware to boot fom USB.
[22:28] <jeandaniel> I think I have to press a key (don't know which one, it is 'c' for cdrom), I am curious which one it could be, anyone?
[22:29] <balachmar> Hi, just to be sure: I just responded to the following bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/576645 should I mark it incomplete now?
[22:29] <ubot4> Launchpad bug 576645 in linux (Ubuntu) "kernel cannot boot (affects: 1)" [Undecided,New]
[22:30] <ddecator> balachmar: yes, and we usually replace BUGNUMBER with the bugnumber for the person ;)
[22:30] <jeandaniel> once I get the mini.iso, should I just dd it from the file to the key device?
[22:30] <persia> jeandaniel: 'c' is for CD-ROM.
[22:30] <balachmar> ddecator: aah I see that is a bit nicer yes :)
[22:30] <ddecator> balachmar: but anytime you request more information, you should mark it Incomplete
[22:30] <balachmar> I cannot edit my comment now can I?
[22:30] <persia> jeandaniel: The mini.iso is designed to burn to business-card CDs.  You'd need to convert it.  usb-creator *might* work.  The folks in #ubuntu might have other suggestions.
[22:31] <persia> balachmar: No.
[22:31] <ddecator> balachmar: it's not a big deal, the user should figure it out
[22:32] <jeandaniel> persia: ok, I'll ask there how to 'burn' the mini.iso to the key *from macosx*
[22:32] <balachmar> ddecator: Well yeah, but if I could edit my comment I would have done that. No need for an extra comment.
[22:32] <persia> Oh, heh.  RIght.  If you don't have a blank CD, you're probably stuck :(
[22:32] <yofel> balachmar: also, I guess you copied the response from somewhere else (as it's edited), you'll find the original here: https://wiki.ubuntu.com/Bugs/Responses#Debugging%20Kernel%20General - Adapting it to the bug report (removing the unnecessary parts) would be nice ;)
[22:33] <ddecator> yah, i forgot to remove a part from a canned response a couple days ago and the user wasn't too happy with me >.<
[22:33] <yofel> balachmar: at least adapting it to the report in question makes it sound a bit less... mechanic
[22:33] <yofel> heh
[22:34] <ddecator> i guess i was "condescending"
[22:34] <balachmar> yofel: I did, I removed the part of jaunty. But I thought it might be useful know what to do if apport-collect doesn't work or something. So I kept the rest.
[22:35] <balachmar> How could I have improved my response?
[22:35] <yofel> balachmar: sure, but it still says 'If you use an older release ...' which sounds confusing
[22:35] <yofel> in this context
[22:35] <balachmar> yofel: Aah that is true.
[22:36] <balachmar> yofel: next time I will paste the apport-collect stuff. And the other method only when asked, because there are problems with apport-collect.
[22:37] <yofel> balachmar: here's what I just used somewhere else (for lucid): http://paste.ubuntu.com/429168/ [one apport-collect gone, python-launchpadlib should be installed on lucid by default and removed notice to older release]
[22:37] <balachmar> By the way, how do you guys test if bugs occur on your computer. I for example rather not install everything in my own running version of the OS, do you guys use a VM or is there a simpler or lighter method?
[22:38] <ddecator> live CD, VM, or if we use the software ourselves already
[22:38] <yofel> I'm an alpha tester so I don't mind having a lot installed, but if it's another desktop environment I use a VM or CD
[22:38] <ddecator> yofel: +1
[22:40] <balachmar> ok thanks! Will first upgrade to lucid with this machine (it is a machine I use a bit less, so it has not been updated yet.) and then use testdrive.
[22:40] <ddecator> testdrive is really nice
[22:41] <persia> jeandaniel: I've just gotten some feedback from one of the updates testers, who has given me the procedure for making sure this gets reported as a regression.  Would you mind filing a new bug at https://bugs.launchpad.net/ubuntu/+source/grub2/+filebug?no-redirect
[22:42] <persia> I'll make sure it gets updated with the right information, but want to make sure you get appropriate notifications about the issue and it's solution.
[22:43] <jeandaniel> no problem, thanks for your help. I am currently fighting with putting the iso on the usb key from macosx
[22:44] <persia> jeandaniel: Good luck with that.
[22:44] <persia> jeandaniel: Just let me know the bug number once you've been able to file.
[22:53] <yofel> balachmar: something else: starting with lucid apport tags the bugs with the release the bug was reported against, 'lucid' in this case. When the tag is missing we usually add it, can you please do so for bug 576645? thanks
[22:53] <ubot4> Launchpad bug 576645 in linux (Ubuntu) "kernel cannot boot (affects: 1)" [Undecided,New] https://launchpad.net/bugs/576645
[22:55] <balachmar> yofel: of course comma separated?
[22:55] <yofel> balachmar: no, space
[22:55] <balachmar> yofel: thanks :) done
[22:56] <yofel> balachmar: thank YOU for helping out ;)
[22:56] <balachmar> aah, the person already did it! Now I am not technical enough to read all the log stuff...
[22:57] <balachmar> yofel: well, I use Ubuntu a lot, so why not give back a bit of my time.
[22:58] <yofel> balachmar: and another thing, if you're really interested in doing kernel triage you should read https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Bug%20Triage
[22:59] <balachmar> yofel: so I should move it to confirmed? because the apport has been done?
[23:00] <ddecator> balachmar: we only confirm when the same bug can be reproduced on a second machine
[23:01] <balachmar> ddecator: that is what I thought but https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Bug%20Triage it says: Once all the information has been provided, the bug should be moved from an Incomplete state to a Confirmed state.
[23:02] <yofel> kernel team and desktop team are a bit weird, yes :P
[23:02] <ddecator> huh...that's odd
[23:03] <yofel> motu too actually, in general, don't touch kernel or packaging bugs when you find one, the status definition is a bit different for those teams (and fix committed for desktop team)
[23:04] <ddecator> heh, that's what i get for primarily working with one package =p
[23:04] <persia> Hey.  *Please* touch packaging bugs.
[23:04] <balachmar> So it is better (for me) to let it stay on new?
[23:04] <balachmar> persia: meaning help with packaging new stuff into ubuntu?
[23:04] <persia> The only sorts that shouldn't be fiddled with are the *workflow* bugs: essentially freeze exceptions and syncs.
[23:04] <yofel> persia: I meant that as in 'Please sync/merge' or needs-packaging ...
[23:04] <persia> yofel: Ah, OK.
[23:05] <persia> balachmar: No, I meant that if someone reports a bug *in the packaging* it oughtn't be treated special: it's still a bug that needs triage like any other.
[23:05] <yofel> my fault for being vague
[23:05] <persia> Examples would be stuff like "missing dependency on foo" or "missing conflict on bar"
[23:06] <balachmar> persia: ooh I see. (Haven't seen one yet)
[23:06] <jeandaniel> persia: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/576662
[23:06] <ubot4> Launchpad bug 576662 in grub2 (Ubuntu) "latest grub2 renders gpt based system unbootable (affects: 1)" [Undecided,New]
[23:07] <robertzaccour> Hey I reported a bug a while back and did apport-collect and wanted to know if there was anything else that could be done
[23:07] <robertzaccour> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/574406
[23:07] <ubot4> Launchpad bug 574406 in linux (Ubuntu) "Realtek ALC272: Capture non-functional on 1025:034a (affects: 1) (heat: 6)" [Undecided,New]
[23:07] <persia> jeandaniel: Thanks!
[23:08] <persia> balachmar: I forget the number, but I filed one against "linux" because `apt-get source linux` doesn't get the "linux" source code.
[23:08] <persia> (yet another example of a packaging bug)
[23:08] <robertzaccour> my logitech plug-in headset works fine though
[23:08] <yofel> balachmar: examples you shouldn't touch include bug 567208 or bug 493242 (if anything make sure the latter is tagged needs-packaging)
[23:08] <ubot4> Launchpad bug 567208 in freebsd-buildutils (Ubuntu) "Please sync freebsd-buildutils 7.2-2 from sid (affects: 1)" [Undecided,Fix released] https://launchpad.net/bugs/567208
[23:08] <ubot4> Launchpad bug 493242 in ubuntu "[needs packaging] Opengoo (affects: 2) (heat: 10)" [Wishlist,New] https://launchpad.net/bugs/493242
[23:16] <persia> I think it's safe to touch needs-packaging bugs, but they're boring (tag, set to wishlist, change title, ignore)
[23:31] <jeandaniel> persia: de nada, cheers
[23:53] <balachmar> Hi, just to ask for a second opinion on #151622 it got reopened lately, but only to mention another bug report about the same problem but in newer software. What should I do mark invalid (as it was) or mark as duplicate of the new bug report?
[23:54] <micahg> bug 151622
[23:54] <ubot4> Launchpad bug 151622 in openoffice.org (Ubuntu) "Impress cannot play embedded videos (affects: 1) (heat: 9)" [Undecided,New] https://launchpad.net/bugs/151622
[23:54] <balachmar> (ghe ghe didn't know how to trigger the bot... )
[23:57] <micahg> balachmar: you can mark the older one as a dupe of the newer one if you want
[23:57] <balachmar> ok, then I will do that.
[23:58] <micahg> balachmar: general rule is whichever bug has better information is the one to use