[02:12] <cpbtklogic> I installed lucid RC today and experienced some problems with the installer.  I'm trying to figure out where I should report it.
[02:12] <cpbtklogic> I have an ICH7 Intel Software RAID.
[02:14] <atrus> cpbtklogic: #ubuntu+1
[03:08] <kermiac> anyone know what package a bug related to the "Enter your password to perform administrative tasks" should be filed against? Is it gksu?
[03:12] <zeroseven0183> kermiac, is it PolicyKit?
[03:12] <zeroseven0183> policykit-1
[03:12] <kermiac> zeroseven0183: could be.... I was tossing up between policykiet & gksu
[03:13] <kermiac> bug 568451
[03:13] <ubot4> Launchpad bug 568451 in ubuntuone-client (Ubuntu) "Unable to authenticate to perform administrator functions (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/568451
[03:13] <zeroseven0183> Yeah, can be gksu also since a frontend to su
[03:13]  * kermiac shrugs
[03:14] <kermiac> I'll file it against gksu for now as that seems the best fit - it can be re-assigned if required
[03:15] <persia> atrus: We probably want to start hunting bugs out of folks for lucid soon: it's too late to fix lots of them, but we can get a head start on making sure the developers are prepared for maverick.
[03:29] <jpiche> but 559610 is marked as incomplete, but I'm pretty sure that it's a duplicate of 548952 because I've seen about 10 duplicates just like it, but it doesn't have much info in it... is it safe to mark as duplicate or should I leave it?
[03:29] <persia> bugs #559610 $548952
[03:29] <ubot4> Launchpad bug 559610 in gnome-nettool (Ubuntu) "gnome-nettool crashed with SIGSEGV (affects: 1) (heat: 10)" [Medium,Incomplete] https://launchpad.net/bugs/559610
[03:30] <persia> Oops.
[03:30] <persia> bug #548952
[03:30] <ubot4> Launchpad bug 548952 in gtk2-engines-murrine (Ubuntu) (and 3 other projects) "gnome-nettool crashed with SIGSEGV in on_ping_graph_expose() (affects: 330) (dups: 21) (heat: 1580)" [Low,Fix released] https://launchpad.net/bugs/548952
[03:37] <persia> jpiche: They're (slightly) different.
[03:38] <persia> jpiche: The thing that convinces me of this is that 559610 says "Segfault happened at: 0xfc458e:	Cannot access memory at address 0xfc458e" and 548952 says  Segfault happened at: 0x7fe12138951f:	mov 0x58(%r14),%rdi
[03:38] <persia>  PC (0x7fe12138951f) ok
[03:38] <persia>  source "0x58(%r14)" (0x00000058) not located in a known VMA region (needed readable region)!"
[03:38] <persia> While we can't get the disassembly for 559610, we can know it's different because the segfault error is different (cannot access memory vs. not located in VMA region)
[03:40] <persia> My suggestion would be to close 559610 as "Invalid" with a comment apologising for this, but our automatic crash analysis tools couldn't understand the issue, and encouraging the user to file a *new* bug with an up-to-date system in the hopes that we can debug it.  It's also worth asking the user to try to share what they were doing when it broke, if they know, to help replicate the issue.
[04:40] <crimsun> plars: please attach output from http://www.alsa-project.org/alsa-info.sh (if possible) to lp 568781
[04:40] <ubot4> Launchpad bug 568781 in alsa-driver (Ubuntu) "[twl4030 - omap3beagle] Recording problem (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/568781
[04:41] <crimsun> plars: if there're worries of nondisclosure, use --no-upload and redact the portions of /tmp/alsa-info.txt
[04:41] <plars> crimsun: nah, it's fine on that, however I don't think I still have the default alsa settings as I was mucking around trying to make it work
[07:54] <Damascene> were some one should ask about the wiki?
[07:54] <ddecator> the bug triage wiki?
[07:55] <ddecator> Damascene: can you be more specific?
[07:55] <Damascene> https://wiki.ubuntu.com/
[07:55] <Damascene> I want to sign but I don't know how
[07:55] <Damascene> it's poor documented
[07:56] <ddecator> sign?
[07:57] <Damascene> like when you sign on paper
[07:57] <Damascene> signature
[07:57] <ddecator> oh, for signing the code of conduct?
[07:58] <Damascene> no
[07:58] <Damascene> look here...
[07:58] <ddecator> what are you trying to sign?
[07:58] <Damascene> https://wiki.ubuntu.com/Mlterm
[07:58] <Damascene> I've singed once but now I don't know how to do it. at the lowest part of the page
[07:59] <persia> @@SIG@@  ?
[08:00] <Damascene> were did you find that, please?
[08:00] <persia> Someone said it on IRC once.
[08:01] <Damascene> thanks
[08:02] <Damascene> I think I'll add that to some help page
[08:03] <persia> I actually fon't fine it useful at all, personallly.  I just write "-- EmmetHikory" which generates a link to my page, and looks cleaner.  If someone cares about the timestamp, the wiki tracks change history.
[08:03] <persia> s/fon't fint/Don't find/
[08:03] <Damascene> I wonder why don't they use dokuwiki or media wiki
[08:03] <Damascene> persia, but it's useful
[08:03] <persia> "they"?
[08:04] <Damascene> easier
[08:04] <Damascene> I mean the site admin
[08:04] <persia> I suspect it was because we asked them to use whatever they use.
[08:04] <persia> The admins mostly just administer based on what Ubuntu requests.
[08:05] <Damascene> so ubuntu requested this unique wiki
[08:06] <persia> I don't think it's unique.  It's moinmoin, isn't it?
[08:06]  * persia didn't happen to be involved in that decision, and doesn't much care which wiki backend is used, as long as it accepts text input and dispays it.
[08:08] <ddecator> heh, fair enough persia =p
[08:09] <Damascene> just look here, how to make sample code block by this wiki https://wiki.ubuntu.com/HelpOnFormatting
[08:10] <Damascene> it's the hardest I've ever seen. look at "Code"
[08:11] <persia> {{{ }}} ?
[08:12] <Damascene> no that
[08:12] <Damascene> the code block
[08:15] <Damascene> `something` <BR>
[08:15] <Damascene> that part
[08:15] <Damascene> and it seems like they get it wrong in that guide too
[08:16] <persia> Guide might have been written for several generations ago/: there have been a few wiki migrations over the years.
[08:16] <Damascene> I want to suggest using dokuwiki. where should I do that?
[08:17] <Damascene> and line strike doesn't work :/
[09:11] <BUGabundo_remote> TGIF \m/
[09:20] <a8> Hi, yesterday I run into a problem booting Lucid as a Xen guest on a AMD Magny-Cours system. Looks like it's known and also KVM has the same problem. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/556480
[09:20] <ubot4> Launchpad bug 556480 in linux (Ubuntu) "kernel crash under KVM when on AMD Magny-Cours (affects: 1) (heat: 8)" [Undecided,New]
[09:21] <a8> That means you cannot boot the ISO in a KVM or Xen guest. :(
[12:25] <Damascene> is there any known bug with compizconfig settings manager in Lucid?
[12:26] <Damascene> I've installed it but nothing show in command line with that name nor in the GUI
[12:26] <yofel> Damascene: the command should be ccsm
[12:27] <Damascene> thanks. it works now. what about the shortcut, were should I found it
[12:28] <yofel> somewhere in system->preferences I think, i don't remeber the exact location
[12:29] <Damascene> oh, I found it now. it's translated but the workd compiz isn't there at all
[12:30] <Damascene> *word
[12:53] <Damascene> hi, I've installed compizconfig and now when I change some setting it compiz get disabled and when I enable it I see the changes are revertedd
[13:00] <persia> Damascene: Have you checked at https://bugs.launchpad.net/ubuntu/+source/compizconfig/+bugs ?
[13:01] <Damascene> page not found
[13:06] <Damascene> 0ubuntu1 (compizconfig-settings-manager
[13:09] <Damascene> https://bugs.launchpad.net/compizconfig-settings-manager/+bugs ?
[13:10] <Damascene> persia, should I report it?
[13:10] <persia> Sure.
[13:10] <persia> More bugs are good.  Without bugs, we don't know what needs fixing.
[13:12] <Damascene> :)
[13:12] <Damascene> can you reproduce it?
[13:19] <persia> I don't use compiz, and I'm not going to install it today.
[13:45] <JoshuaL> Hello, i think this is a bug so i want to report it but i dont know what package it belongs too. This is the case: I bought a new router with 802.11n support, i set the router to use 802.11n connections and whenever i try to connect my laptop it does not work (it simply wont connect). Using another laptop with windows works fine so it is not a router issue. Im totally sure my laptops wireless card supports 802.11n. Im using the Br
[13:45] <JoshuaL> oadcom drivers shipped via hardware manager.
[13:57] <maxb> I need help figuring out where to search for or report a bug: On Lucid, the tickmarks in on/off context menu items appear white-on-light-grey, and so pretty much invisible.
[14:08] <Damascene> http://uppix.net/f/0/3/6fa151016336535846868309a4a09.png wrong direction of Arabic text
[14:09] <Damascene> is it a bug in compiz-config
[14:30] <persia> Damascene: Ugh.  Another one.  May as well start there, and see where you end up .
[14:31] <persia> Damascene: For extra points, you might just go through everything to check RTL stuff: it looks like we miss too much :(
[14:31] <Damascene> persia, for the first one they tell me that it's a problem with inter card I have
[14:31] <Damascene> for the second I reported it
[14:31] <Damascene> and yes I asked them for the second one at #compiz
[14:32] <persia> Oh,the fact that it doesn't work is hardware, and the fact that it prints everything wrong is a bug?
[14:33] <Damascene> I still thing it's a bug thought but I'll talk about later
[14:33] <Damascene> persia, you don't use Persian?
[14:34] <persia> I'm not persian.
[14:34] <Damascene> oh, sorry. your name made me think so
[14:36] <Damascene> I'm trying to help with RTL as much as I can
[14:36] <Damascene> is there a way to be notified when ever rtl tag is added?
[14:38] <yofel> no, there was a bug for malone about not being able to subscribe to tags
[14:38] <Damascene> I think I'll just search form time to time :)
[14:38] <Damascene> or is there rss feed for tags
[15:52] <igcek> hello, ive tried to upgrade to 10.04, and it reported a gazilion bugs ( it didnt complete it ). what i want to know is, where do i report this?
[15:53] <igcek> here does not say https://help.ubuntu.com/community/ReportingBugs#Getting%20advice
[15:54] <SwedeMike> igcek: "it reported bugs" ?
[15:57] <igcek> ubuntu, while upgrading
[15:57] <igcek> the "process" of upgrating
[15:59] <igcek> i mean, reported errors, and saved them in var/log/dist-upgrade...
[18:37] <bdmurray> thekorn: the bug we were looking at ended up getting marked as a dup of bug 414967
[18:37] <ubot4> Launchpad bug 414967 in ipython (Ubuntu) (and 1 other project) "print statements get incorrectly mangled by the autocall feature under Python 2.6 (affects: 12) (dups: 5) (heat: 100)" [Undecided,New] https://launchpad.net/bugs/414967
[18:37] <bdmurray> thekorn: and it looks like there is fix now
[18:42] <thekorn> bdmurray: cool, did you try if this patch works
[18:42] <thekorn> esp. if this patch 'our' issue
[18:42] <thekorn> when I was reading the other bugreport the first time I did not see how they are related
[18:43] <thekorn> but since Fernando is one of the devs he might know what he is doing ;)
[18:44] <bdmurray> thekorn: yeah, that was my thought ;-)
[18:44] <bdmurray> I tried cherry picking the patch(es) and wasn't getting very far
[18:45] <bdmurray> it does seem to work though
[19:02] <thekorn> bdmurray: hmm, let me look at the revisions mentioned in the bug,
[19:03] <thekorn> maybe I can get a diff against the lp:ubuntu/ipython
[19:05] <bdmurray> thekorn: I tried bzr log -r -p and bzr merge -r 1224..1225 and neither applied cleanly
[19:05] <bdmurray> but it might be me
[19:12] <thekorn> yes, merging somehow is not working, let me try to use bzr diff and bzr patch
[19:22] <thekorn> bdmurray: I think I fixed it in lp:~thekorn/+junk/ipython_bug414967
[19:30] <bdmurray> thekorn: awesome, I'll build test and upload
[20:50] <bdmurray> thekorn: upon further investigation I realize this should be a quilt formatted patch in debian/patches
[23:00] <thekorn> bdmurray, sorry, I've no idea how this quilt system works
[23:01] <micahg> thekorn: /usr/share/doc/quilt/README.gz
[23:04] <elleuca> https://bugs.launchpad.net/bugs/566437
[23:04] <thekorn> I guess I need some quilt package for this
[23:04] <ubot4> Launchpad bug 566437 in fglrx-installer (Ubuntu) "package fglrx 2:8.723.1-0ubuntu2 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2 (affects: 3) (heat: 16)" [Undecided,New]
[23:05] <elleuca> it seems you are unable to remove fglrx drivers (at least after upgrade to lucid for me)
[23:08] <bdmurray> thekorn: I can sort it out tomorrow
[23:08] <thekorn> bdmurray, this would be great, thanks
[23:08] <thekorn> bdmurray, but always remember, it's weekend ;)
[23:08] <bdmurray> thekorn: no problem thank you!
[23:09] <bdmurray> thekorn: the weekend before release!
[23:09] <thekorn> lucid is in good shape,
[23:09] <thekorn> no need to worry too much