[00:01] <rusivi> micahg: I'm going to mark myself affected asap
[00:06] <micahg> rusivi: did you clear the bug # from the duplicate box and click the green check?
[00:07] <rusivi> micahg: I tried that before asking but it did not undo the duplication.
[00:07] <micahg> rusivi: maybe it's a permissions thing
[00:07] <rusivi> Wouldn't be the first time ;)
[00:08] <rusivi> micahg: It did not respond that it could not do the action due to my permissions so IDK
[00:08] <rusivi> I clicked the check, the box disappeared, I refreshed the page, nothing changed.
[00:09] <micahg> rusivi: right, I would say, if it's reproducible, file a bug against launchpad in any event if it is a permissions thing, the text should be changed
[00:10] <rusivi> micahg: The next time I mistakenly mark a bug a duplicate (later rather than sooner) I'll check for it and create a malone bug if it does not work.
[00:11] <micahg> rusivi: malone is no more, all bugs are against launchpad now
[00:11] <rusivi> micahg: "Launchpad itself"
[00:11] <micahg> rusivi: yes
=== ogra is now known as Guest58620
[00:53] <Amaranth> I remember hearing something about regression-potential going away, did that happen?
[00:53] <micahg> Amaranth: yes
[00:53] <Amaranth> I was rather surprised to see two bugs in compiz we know about and plan on fixing well before the natty release get tagged "regression-release"
[01:05] <hggdh> Amaranth: it ended up regression-potential bugs had to be manually converted to regression-release *after* code release, and it was just unneeded work
[01:05] <hggdh> so regression-release got to be used for both dev and stable
[01:06] <Amaranth> hggdh: just call it "regression" then :)
[01:06] <Amaranth> Although the compiz wakeups one is not as big of a deal as people make it sounds...
[01:06] <hggdh> Amaranth: we considered that, but there are other regressions
[01:06] <Amaranth> There are?
[01:07] <hggdh> regression-proposed and -update
[01:07] <hggdh> and these are important enough to be kept
[01:40] <alex_mayorga> hi! Can somebody, please review bug 693828?
[01:40] <ubot2> Launchpad bug 693828 in linux (Ubuntu) "Fatal exception in interrupt: Kernel panic on 2.6.37-10-generic and 2.6.37-11-generic (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/693828
[04:08] <em> I have this same problem -- https://bugs.launchpad.net/ubuntu/+source/linux/+bug/692164
[04:08] <ubot2> Launchpad bug 692164 in linux (Ubuntu) "Hewlett-Packard HP Pavilion dv6 fails to resume from suspend (affects: 3) (heat: 579)" [Undecided,New]
[04:08] <em> is brian murray here?
[04:09] <em> bdmurray: are you Brian Murray?
[04:17] <em> is anyone awake here?
[04:26] <micahg> !patience | em
[04:26] <ubot2> em: Don't feel ignored and repeat your question quickly; if nobody knows your answer, nobody will answer you. While you wait, try searching https://help.ubuntu.com or http://ubuntuforums.org or http://askubuntu.com/
[04:28] <micahg> em: you should file a new bug
[04:29] <em> micahg: will it get linked to that one. Id really like for Ubuntu to fix this one. It surely affects a whole class of people. Everyone who has an HP Pavilion. Which is many people!
[04:30] <micahg> em: you should note this bug number in your report, but the kernel team prefers separate reports since sometimes hardware can be slightly different
[04:31] <em> okay, can you tell me how to make the best possible bug report for this? Like, what kind of information I should give them and such?
[04:31] <micahg> em: https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume
[04:32] <micahg> ubuntu-bug linux should do most of it
[05:24] <rusivi> Regarding bug https://bugs.launchpad.net/ubuntu/+source/keepassx/+bug/608396 while this bug has a easily performed workaround (don't hold the key-combo too long) it's a deal breaker if you hold it too long. Seems importance should be low or medium, leaning towards low.
[05:24] <ubot2> Launchpad bug 608396 in keepassx (Ubuntu) (and 1 other project) "KeePassX 0.4.3 bricks keyboard in Ubuntu 10.04 (affects: 4) (heat: 30)" [Undecided,Confirmed]
[05:54] <micahg> rusivi: ok, setting to Low -> Triaged, can you please edit the description for the workaround?
[05:55] <micahg> rusivi: see https://wiki.ubuntu.com/Bugs/Description
[06:00] <rusivi> micahg: Sure.
[06:01] <micahg> rusivi: thanks
[06:13] <rusivi> micahg: Put the WORKAROUND right at the top. BTW, I noticed in the bug description that bugs with workarounds don't get fixed?!
[06:13] <rusivi> micahg: sorry misunderstood meaning. As in, a workaround is not a solution.
[06:14] <micahg> rusivi: right
[06:14] <rusivi> micahg: threw me off at first hehe
[07:19] <rusivi> Regarding bug https://bugs.launchpad.net/ubuntu/+source/gcalctool/+bug/631665 just checked in Maverick, it's fixed. Should I just mark the "Maverick" as "Fix Released", or both this & "gcalctool (ubuntu)"?
[07:19] <ubot2> Launchpad bug 631665 in gcalctool (Ubuntu Maverick) (and 3 other projects) "Calculator does not show thousands seperator despite being chosen in preferences (affects: 10) (dups: 4) (heat: 64)" [Medium,Fix committed]
[07:42] <SpamapS> rusivi: did you verify that it is fixed in maverick-updates, or maverick-proposed ?
[07:43] <SpamapS> rusivi: if its fixed in maverick-proposed, then you need to post that you did the verification in the bug, and the SRU team will remove the verification-needed tag, set it to verification-done, and move the package from poposed to updates... which launchpad will see, and mark the task as Fix Released automatically.
[07:47] <rusivi> SpamapS: I verified it's fixed in maverick-updates
[07:48] <rusivi> SpamapS: It looks like update & proposed are the same now -> https://launchpad.net/ubuntu/maverick/+source/gcalctool/+builds
[07:50] <micahg> rusivi: yes, it was pushed to maverick-updates 2 months ago, so Fix released is appropriate for maverick and the default task
[07:50] <SpamapS> weird, I wonder why that wasn't caught by the updater
[07:50]  * SpamapS will have to ponder that while sleeping...
[07:50]  * SpamapS passes out
[07:50] <rusivi> micahg: K, will make notes of my successful test and mark both Fix Released
[07:51] <micahg> SpamapS: there were 3 revisions uploaded to -proposed and the final one didn't use -v :)
[07:51] <yofel> SpamapS: it was superseded by ubuntu4 before it even made it to -updates which confiused launchpad
[07:51] <yofel> micahg: what's -v?
[07:52] <micahg> yofel: yes, but what's supposed to happen is the uploader should pass the current release version when building the source so all the new versions show in the .changes file
[07:52] <yofel> aah
[07:53] <micahg> rusivi: it seems it was never verified either which was bad
[07:54] <rusivi> micahg: Ok... well it's fixed so I know that much!
[07:59] <rusivi> Regarding bug https://bugs.launchpad.net/ubuntu/+source/zsnes/+bug/616561 this looks like Importance Low b/c it has a WORKAROUND: Do not use the fast forward feature.
[07:59] <ubot2> Launchpad bug 616561 in zsnes (Ubuntu) (and 1 other project) "ZSNES randomly closes intermittently mid-game (affects: 1) (heat: 26)" [Undecided,New]
[09:35] <njin> hello to all, if in the report i see a Linux 2.6.35-24-generic-pae i686 is safe to require installation of ppa kernels ?
[10:56] <fat0ss> Hello, I new to ubuntu dev
[10:56] <fat0ss> Initially, I want to learn about projects by fixing bugs
[10:57] <fat0ss> How can I start ?
[10:57] <fat0ss> I Install already https://wiki.ubuntu.com/BeginnersTeam/FocusGroups/Development/Devbeginnings#Thorough%20Install:%20Ubuntu%20Development%20Tools all Dev tool
[11:06] <anoteng> fat0ss: https://wiki.ubuntu.com/Bugs/HowToTriage
[11:13] <fat0ss> anoteng, what are the possible Projects ? Like  Easy for Initial Level I know C/C++
[11:37] <anoteng> fat0ss: Find something you're interested in, or some project you use a lot yourself.
[11:37] <fat0ss> I scan the Bug site
[11:37] <anoteng> Or get yourself a sponsor, and get involved in whatever project your sponsor is involved with.
[11:37] <fat0ss> But I didn't find any list of projects
[11:38] <fat0ss> I am stuck How to start with a simple patch
[11:38] <fat0ss> What's is Sponsor thing ? Please explain me
[11:39] <anoteng> sorry, not sponsor, I meant mentor..
[11:40] <anoteng> https://wiki.ubuntu.com/BugSquad/Mentors
[11:42] <fat0ss> Okhay, Thanx a Lot ..
[11:42] <anoteng> list of packages: http://packages.ubuntu.com/natty/
=== daker_ is now known as daker
[14:29] <c2tarun> can anyone please look at bug 695696, i checked its man page and ubiquity is a software to install ubuntu from a live CD, then what are syslog and partman files, the reporter is talkiing about?
[14:29] <ubot2> Launchpad bug 695696 in ubiquity (Ubuntu) "Crashed Pinguy install on laptop (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/695696
[14:29] <c2tarun> bug 695696
[14:30] <charlie-tca> syslog and partman files are two logs from /var/log that are generated when ubiquity crashes.
[14:32] <c2tarun> charlie-tca: Can you please explain me a bit, that why we need ubiquity for installing ubuntu from a live CD. Even why we need any software when we have live CD?
[14:33] <charlie-tca> ubiquity is the installer built in to the live cd; There is no package called "live CD". the actual package name is ubiquity
[14:34] <c2tarun> ok, so I guess that we don't have any way to reproduce his bug. + he didn't mentioned about the ubuntu version he is trying to install?
[14:35] <charlie-tca> The live cd is simply a group of packages put together by developers and made to work as if it was an installed system. When something fails on the Live CD, we have to determine what application actually failed. The failing package during an install is ubiquity.
[14:36] <yofel> he should have said that, but you can get the ubuntu version from the syslog:
[14:36] <yofel> Dec 30 12:34:18 guest kernel: [    0.000000] Linux version 2.6.35-23-generic (buildd@rothera) (gcc version 4.4.5 (Ubuntu/Linaro 4.4.4-14ubuntu5) ) #37-Ubuntu SMP Fri Nov 5 19:17:11 UTC 2010 (Ubuntu 2.6.35-23.37-generic 2.6.35.7)
[14:36] <yofel> => maverick
[14:37] <c2tarun> Ok. But how can we confirm his bug? I googled and found someone also reported this bug on ubuntuforums.org
[14:38] <charlie-tca> To triage the bug in ubiquity, we need to know the date of the cd, and the bug should probably be against https://launchpad.net/pinguyos instead of ubiquity
[14:38] <charlie-tca> or also against pinguyos
[14:39] <charlie-tca> We can't actually confirm it
[14:40] <c2tarun> Ok, so what can we do with this bug?
[14:41] <wolfpack> hi i am new to bug squad , can this bug be set as WISHLIST .........  https://bugs.launchpad.net/ubuntu/+bug/695444
[14:41] <ubot2> Launchpad bug 695444 in ubuntu "Karmic/9.10 doesn't auto-detect external microphone (affects: 1) (heat: 6)" [Undecided,New]
[14:42] <charlie-tca> c2tarun: leave it alone
[14:42] <charlie-tca> I added pinguyos to the bug, we will let the developer look at it
[14:42] <c2tarun> charlie-tca: Ok, Thanks :)
[14:43] <charlie-tca> You are welcome
[14:43] <charlie-tca> c2tarun: just one of the many that we can't really work with
[14:43] <c2tarun> wolfpack: did you try to reproduce this bug?
[14:43]  * penguin42 gently wonders where Failed to set a proper state for notification semaphore identified by cookie value 223177637 (0xd4d6ba5) to initialize waiting for incoming notifications. would have come from in cryptsetup
[14:44] <charlie-tca> wolfpack: convert that to a question...
[14:44] <wolfpack> ok
[14:44] <charlie-tca> The reporter is seeking support more than reporting a bug
[14:45] <c2tarun> charlie-tca: what do you mean by converting a bug to question?
[14:46] <micahg> charlie-tca: idk about that, it seems like a wishlist bug in that it should auto detect
[14:46] <charlie-tca> There is a place in the top right column to convert to a question. some times the reporter is actually seeking support instead of reporting a bug, and converting to a question lets it get an answer
[14:47] <charlie-tca> micahg: What is "Is there a known solution for this??" if not a support question?
[14:47] <c2tarun> micahg: sorry to interrupt, but what is a "wishlist bug", I think either it is a wishlist or a bug. :(
[14:48] <charlie-tca> we do not triage that, it should have been answered through research already
[14:48] <micahg> charlie-tca: basically wanting to know if it's fixed in later releases or not
[14:48] <charlie-tca> micahg: then do what you want with it.
[14:49] <charlie-tca> I am tired of trying to justify every answer I give when you are around
[14:49] <micahg> charlie-tca: that's basically saying that people can't report bugs on older version w/out verifying it doesn't exist on a later version (which upstreams generally ask be done, but idk about our policy)
[14:49] <micahg> charlie-tca: you might indeed be right, I'm just trying to clarify a general policy regarding older releases
[14:50] <micahg> charlie-tca: you do a great job answering people's questions
[14:52] <micahg> charlie-tca: maybe it should be a topic for the next meeting?
[14:53] <charlie-tca> I am no longer discussing it. I get questioned and have to justify to you every thing I tell people.
[14:53] <charlie-tca> You just go ahead and help these people learn
[14:55] <micahg> charlie-tca: PM?
[14:55] <charlie-tca> go ahead
[15:13]  * ElPasmo thinks bug 629646 is ready to be set to Triaged with a Low importance. Can anyone do it for him?
[15:13] <ubot2> Launchpad bug 629646 in libgweather (Ubuntu) (and 1 other project) "Locations using bom.gov.au for forecast data no longer can no longer retrieve forecast data (affects: 10) (dups: 1) (heat: 61)" [Undecided,Confirmed] https://launchpad.net/bugs/629646
[15:17] <charlie-tca> ElPasmo: done. Thanks for helping
[15:19] <ElPasmo> thanks to you charlie-tca :)
[15:20] <wolfpack> how to add package name in a already filed bug ........I want to add package name "xorg" to this bug :  https://bugs.launchpad.net/ubuntu/+bug/695149
[15:20] <ubot2> Launchpad bug 695149 in ubuntu "Right-click menus don't disappear (affects: 1) (heat: 6)" [Undecided,New]
[15:22] <charlie-tca> wolfpack: that has no package at the present time, so click the down arrow symbol to the left of "ubuntu" and change the "affects" to xorg
[15:23] <charlie-tca> wolfpack: then use this response in comments:  https://wiki.ubuntu.com/Bugs/Responses#Bugs%20without%20a%20package
[15:23] <charlie-tca> just copy and paste the lines in the box
[15:27] <wolfpack> thanks charlie .
[15:28] <charlie-tca> You are welcome
[15:35]  * ElPasmo thinks bug 373268 is ready to be set to Triaged with a Low importance. Can anyone do it for him?
[15:35] <ubot2> Launchpad bug 373268 in libgweather (Ubuntu) (and 1 other project) "Can't choose the exact timezone location in Argentina (affects: 1) (heat: 7)" [Undecided,Confirmed] https://launchpad.net/bugs/373268
[15:39] <charlie-tca> done again
[15:40] <ElPasmo> ty
[15:48]  * ElPasmo thinks bug 572787 is ready to be set to Triaged with a Low importance. Can anyone do it for him?
[15:48] <ubot2> Launchpad bug 572787 in libgweather (Ubuntu) (and 1 other project) "Problem in libgweather (affects: 1) (heat: 16)" [Undecided,Confirmed] https://launchpad.net/bugs/572787
[15:51] <charlie-tca> ElPasmo: done
[15:52] <ElPasmo> ty
[16:11] <wolfpack1> For this bug, Fix has been released but still the status is NEW.  link : https://bugs.launchpad.net/ubuntu/+bug/677794 .Please look into it.
[16:11] <ubot2> Launchpad bug 677794 in ubuntu (and 1 other project) "[needs-packaging] wallch (affects: 2) (heat: 10)" [Undecided,New]
[16:13] <charlie-tca> wolfpack1: that is a packaging bug. Until the package wallch is actually built for Ubuntu, it will be an open bug.
[16:13] <wolfpack1> ok
[16:14] <charlie-tca> Even though it is being worked on, and does have a launchpad team, it is not yet available in natty
[16:15] <charlie-tca> um, pretty much any bug that says "needs-packaging", we stay away from it
[16:16] <wolfpack1> ok
[17:41] <hggdh> for all re. 'needs-packaging': please see https://wiki.ubuntu.com/Bugs/HowToTriage#Developer%20Process%20Bugs
[17:44] <charlie-tca> Thank you for that reference.
[17:48] <hggdh> and I am trying again the server ISO... will it suddenly reboot during install?
[17:50] <charlie-tca> did yesterday
[17:53] <hggdh> and did, again, just now :-(
[19:36] <rusivi> IMHO, Regarding "<micahg> charlie-tca: that's basically saying that people can't report bugs on older version w/out verifying it doesn't exist on a later version (which upstreams generally ask be done, but idk about our policy)" Upstream doesn't generally, it's a prereq for majority of projects I've seen! All kidding aside, it seems fair people who report bugs in prior releases (assuming not mass affecting, security hole, major
[19:36] <rusivi> issue, and if a newer package is available in newer release) be asked to test for the problem via Live CD or VM, and if they are in a position where they absolutely could not test it (time, refused, cost, lack of education), it still remains an open bug for others to help address in the release bugged and newer ones.
[19:54] <charlie-tca> hggdh: amd64 xubuntu alternate made it to installing core packages today
[19:55] <penguin42> this isn't something screwy like someone enabling a watchdog is it?
[19:55] <charlie-tca> before the restart
[19:55] <charlie-tca> don't know, how do I find it?
[19:57] <penguin42> not sure, personally I'd be tempted to find a way to get the kernel messages to another machine
[19:57] <charlie-tca> It does a complete restart, I don't know that there are any logs
[19:57] <hggdh> I am considering it, but I cannot find a way of getting the installer syslog out
[19:58] <penguin42> doesn't it dump it in the installed directory somewhere?
[19:58] <hggdh> it is written to the tmpfs...
[19:58] <charlie-tca> There isn't an installed directory at that point, is there?
[19:58] <hggdh> it will only dump it after system install (until then, there is no FS to be used
[19:58] <charlie-tca> and when it restarts, the logs are gone
[19:58] <penguin42> hmph
[19:59] <penguin42> do you think it'll reboot if you just leave it or do you need to keep interacting?
[19:59] <charlie-tca> open to ideas, though
[19:59] <charlie-tca> No, it reboots on its own when install packages
[19:59] <hggdh> it is rebooting (in my case) during base system install
[20:00] <penguin42> ok, as soon as it starts doing that, ctrl-alt-console and see if it says anything before it explodes
[20:00] <charlie-tca> it reads on screen, "installing core packages..."
[20:00] <hggdh> and -- again in my case -- "extracting libpcreg... BANG!"
[20:00] <charlie-tca> almost
[20:00] <charlie-tca> "ignoring pre-dependency problems"
[20:01] <charlie-tca> and then I missed the rest
[20:01] <hggdh> too fast :-(
[20:01] <charlie-tca> trying again
[20:01] <charlie-tca> Maybe I will boot the 400MHz cpu and try it
[20:02] <charlie-tca> I know. I will snapshot the screen
[20:04] <charlie-tca> coreutils is not installed
[20:05] <charlie-tca> there seems to be a bunch of missing packages
[20:05] <charlie-tca> snapshot was too slow
[20:07] <charlie-tca> missing libnewt0.52, ext2-modules, efi-modules
[20:07] <hggdh> at this point in time, there is almost nothing installed
[20:08] <penguin42> no coreutils then you're pretty screwed
[20:08] <charlie-tca> That was the last one I caught
[20:09] <hggdh> I will try here on KVM, and see if I can rescue it later (I tried on bare-metal -- but remote, and rescue did not work)
[20:10] <charlie-tca> Can't pull anything from VBox, since there is no way to keep it running long enough to pull
[20:10] <penguin42> you could try booting with the nowatchdog parameter - worth a shot, no more
[20:11] <hggdh> the only messages I see is "rebooting", and at about the same time "sending kill signal"
[20:11] <charlie-tca> heh, too fast
[20:11] <charlie-tca> I am going to try to snapshot it again
[20:19] <charlie-tca> Hey, last screen I get before it restarts - http://imagebin.org/130283
[20:20] <charlie-tca> Now you want me to try and do that to the server image? which one>?
[20:20] <penguin42> charlie-tca: There are no kernel messages there that might indicate what's going on - isn't there a console that has kernel stuff?
[20:21] <charlie-tca> No, that is the only one
[20:22] <penguin42> try ctrl-alt and work through f10-f5 - nothing on any of them?
[20:23] <charlie-tca> let me try that,
[20:23] <charlie-tca> you know, that takes a new install each time, right?
[20:24] <charlie-tca> it doesn't really stay on screen very long
[20:25] <penguin42> yeh but you should be able to find the console with the kernel messages before it dies in plenty of time
[20:26] <charlie-tca> looking
[20:27] <charlie-tca> That's the only console with messages on it
[20:27] <penguin42> hmm
[20:27] <penguin42> will it let you get a shell on the others?
[20:27] <charlie-tca> on 2 and 3 it will. 5, 6, 7, 8, 9, 10, 11, 12 are sitting with the _ on them
[20:28] <penguin42> you could try sitting on 2 or 3 while it does the install, possibly with something liek tail -f /var/log/messages if there is one
[20:29] <penguin42> you could also on 2 and 3   do   setterm -msg on      setterm -msglevel 8    which I think should give the maximum amount of blurb
[20:33] <charlie-tca> consoles are using built-in shell (ash)
[20:33] <charlie-tca> stterm not found
[20:33] <charlie-tca> setterm
[20:33] <penguin42> hmph
[20:33] <charlie-tca> It's a busybox shell
[20:34] <penguin42> yeh
[20:34] <penguin42> charlie-tca: You could try running tail -f /proc/kmsg & in one of the terminals
[20:34] <charlie-tca> server shot looks the same
[20:35] <penguin42> oh well, out of ideas
[20:39] <charlie-tca> attached to the bug
[21:14] <hggdh> hum
[21:15] <hggdh> the idea of monitoring /proc/kmsg might get us to something -- I am attaching to the bare-metal via a serial console, and I can set it on the tty, and wait
[21:31] <charlie-tca> I am sorry, I gave up
=== lamalex_ is now known as lamalex