[05:04] <Rocket2DMn> ok guys, bug 308978 - xorg or linux?
[05:07] <Ryan52> xorg, I think.
[05:09] <Rocket2DMn> that seems to be it since restarting X fixes it.  But the suspend/resume is suspicious
[05:10] <Ryan52> ya....hrm.
[06:36] <Ziroday> ogasawara: ping
[07:45] <shiunji> ugh, ever since the last hardy update, firefox has been *really* crashy
[07:46] <shiunji> not sure which bug this goes under since i don't have a bt or anything, but i assume it's well known since up until now FF never crashed on my system
[07:47] <shiunji> have there been lots of recent complaints about it lately?
[09:30] <whatisneveritis> how do I find out which package gnome-display-properties belongs to?
[09:31] <Ryan52> whatisneveritis: dpkg -S `which gnome-display-properties`
[09:31] <whatisneveritis> thanks
[09:45] <Hew> Who can access bug 310126? It's referenced in the latest xorg changelog, but apparently even Bug Control can't access it. I haven't come across this situation before..
[13:23] <alinhan> hello
[13:23] <alinhan> can someone help me with reporting a bug?
[13:24] <Hew> alinhan: What do you need help with?
[13:24] <alinhan> today I did my first ISO test and hit a problem right at the beginning
[13:25] <alinhan> and since this is my first test and my first possible bug report, I wan't to make sure that I didn't screw up somewhere in the process
[13:26] <alinhan> the ISO I tested is this: http://iso.qa.ubuntu.com/qatracker/info/2204
[13:27] <alinhan> and the problem that I run into is that the keyboard doesn't work at the graphical boot menu
[13:27] <Hew> alinhan: I wouldn't worry about that, you're not going to break anything :P. Just make sure all the relevant details are there and a triager will check it and ask for any additional info.
[13:27] <alinhan> ok, thanks
[13:27] <Hew> ah ok
[13:28] <Hew> alinhan: Have you tested a previous iso (even a previous release) and had the keyboard working?
[13:28] <Hew> alinhan: If we know that, we can determine where the regression occurred (if it's a regression at all)
[13:28] <alinhan> no, but on that machine I have another OS on another HDD, that works fine
[13:29] <alinhan> the other OS is Windows XP
[13:29] <Hew> alinhan: So this Jaunty daily CD is the first Ubuntu CD you've used on the machine?
[13:29] <alinhan> yes
[13:29] <Hew> Do you have an Intrepid LiveCD lying around?
[13:30] <Hew> it may be worth trying that if you do
[13:30] <alinhan> ok, will try Intrepid
[13:30] <Hew> alinhan: Yea that would be good additional info
[13:30] <alinhan> can I get back to you after that?
[13:30] <Hew> alinhan: In any case feel free to report the bug when you're ready, a triager will ask for any needed information :-)
[13:30] <Hew> alinhan: Of course
[13:31] <alinhan> ok, thanks
[13:31] <Hew> alinhan: Thank you for your help with testing!
[13:31] <alinhan> glad to help
[13:41] <bramlet> i was unable to install 64 bit guest in virtualbox is this just a missing feature?
[13:42] <bramlet> version 2.1 is supposedly able to have 64bit guest on 32 bit host i have 64 bit host
[13:54] <Hew> bramlet: 2.0 was meant to have it but there have been issues, I've already reported a bug for it and there's a 2.1 upgrade bug as well.
[13:56] <Hew> bramlet: bug 271651, bug 304859
[13:58]  * Hobbsee wonders how that can possibly class as 'triaged' without a package attached.
[13:58]  * Hobbsee bumps it back to new
[14:01] <Hew> Hobbsee: Triaged means the bug report has all the necessary info, right? I suppose for upgrade requests there isn't much difference between new and triaged.
[14:05] <Hew> Hobbsee: What should be added to the report to justify triaged status? A debdiff?
[14:18] <Hew> Hobbsee: Bug 304859 was triaged by blueyed who has done the virtualbox-ose uploads in the past.
[14:18] <Lupine> hello all, I wanted to help give something back to Ubuntu and decided to help triage bugs
[14:18] <Lupine> I just read over the: https://wiki.ubuntu.com/Bugs/HowToTriage
[14:19] <Lupine> but I was curious what should be done if I can't duplicate a bug.  simply mark that in the comments, and change nothing else?
[14:20] <Lupine> also, is there anything "formal" I should do, to state that I'm triaging a particular bug?
[14:27] <Hew> Lupine: If you can't reproduce the bug, you should ask the reporter for more information on how to do so, and make sure they are using the latest version of the package. When you ask for additional information, you set the status to incomplete.
[14:27] <Lupine> Hew, great, thx!  Will do.
[14:27] <Hew> Lupine: There is nothing formal you need to do, but if you are triaging it is a good idea to join the Bugsquad if you haven't already.
[14:28] <Hew> Lupine: No worries, thanks for your help :-)
[14:29] <bramlet> I am using version 2.1 of virtual box and still cant get jauntyu alpha 2 64 bit to install....should this be a separate bug from #271651
[14:29] <bramlet> also im not sure if its even ose
[14:31] <bramlet> probably not a ubuntu bug anyway but maybe somebody knows
[14:32] <Hew> bramlet: 2.1 isn't in the Ubuntu archive so that's not an Ubuntu bug, you probably want to report that upstream.
[14:33] <Hew> bramlet: Does it say the CPU is not x86-64 when you try and boot?
[14:33] <bramlet> yeah thats what i figured
[14:33] <bramlet> yeah somthing like that...
[14:35] <bramlet> This kernal requires an x86_64 CPU, but detected an i686 CPU
[14:36] <Hew> bramlet: That may still be bug 271651. I'm not sure whether it's an upstream or Ubuntu packaging bug. I think the next step is to get 2.1 in the archive and see how that performs.
[14:37] <bramlet> I'm assuming its been reported upstream already?
[14:40] <Hew> bramlet: Well I thought it may have been an Ubuntu packaging issue with 2.0, but if you're getting the same issue with (I assume) the upstream 2.1 deb, it's probably an upstream issue. My guess is broken 64-bit guests would already be a known bug, but it's always worth checking.
[14:40] <bramlet> http://www.virtualbox.org/changeset/15251
[14:40] <bramlet> "disabled 64 bit guests for 32bit hosts for now- too much trouble"
[14:41] <bramlet> I have 64 bit host but maybe this disabled all 64bit guests
[14:41] <Hew> bramlet: Yes I have 64-bit host too. If that commit is in their 2.1 release I find that very strange indeed.
[16:01] <aji> Hi,
[16:09] <alimon> someone knows user robert-in-au??
[16:20] <Hew> alimon: No, but why do you ask?
[16:42] <MrKanister> Can someone please set the bug #6297 to "wishlist"? Thanks in advance.
[16:43] <MrKanister> It could also be "low", but i would say it's kind of feature request
[16:49] <Hew> MrKanister: I have set the importance of bug 6297 as low, since it describes a bug. I would also question such anecdotal evidence, I don't think there's anything unusual about hearing a song twice in a short period of time (as long as it's not a regular occurance).
[16:50] <MrKanister> Hew: Thanks
[16:52] <Hew> MrKanister: It's been a while since I studied statistics, but I'm sure a user could run rhythmbox for a while and see what sort of spread they get across their playlist. Also, the original bug description doesn't seem to apply to current rhythmbox. I'm thinking this should either be closed, or asked for more information.
[16:53] <Hew> I think every music player receives criticism of having a non-random shuffle, whether the criticism is deserved or not. The easiest way to check is probably to look at the code, I guess.
[16:54] <MrKanister> Hew: Yes, probably. The bug is very old (I was about to keep up with some old bugs ;)). But the last comment was written on 30.11.2008
[16:57] <Hew> MrKanister: None of the comments relate to the original bug description. I think the bug should just be closed. eg. "I just got the same song to play thrice", what does that prove?
[16:58] <MrKanister> Hew: I know what you mean. I will asked if it is still a problem and set it to "incomplete". Then we will see
[16:59] <Hew> MrKanister: Good idea. Make sure you're clear which issue you are referring to, since there are effectively two bugs in the one report.
[17:00] <alimon> hello
[17:00] <Hew> alimon: Hi
[17:00] <alimon> i want to ask about a bug in ivman
[17:00] <alimon> sorry about my poor english
[17:00] <Hew> alimon: Which bug #?
[17:02] <alimon> i dont know if is a bug but the user RobertH published a patch
[17:02] <alimon> https://bugs.launchpad.net/debian/+source/ivman/+bug/219635
[17:02] <alimon> yes
[17:04] <alimon> i was patching the sources and generate the deb
[17:04] <alimon> and install
[17:04] <alimon> the patch work ok
[17:04] <alimon> but now
[17:04] <alimon> i have another question about ivman
[17:04] <Hew> alimon: The bug is already upstream, where it looks like the patch was taken from.
[17:08] <Hew> alimon: What is the other question?
[17:08] <alimon> a ok
[17:09] <alimon> i want to add a condition in IvmConfigProperties.xml
[17:10] <alimon> i added a property in this file
[17:10] <Hew> alimon: This channel is for bug triage, not for end user support. You might be better off asking support questions in #ubuntu
[17:10] <alimon> a ok
[17:10] <alimon> thanks
[17:10] <Hew> alimon: No worries :-)
[17:26] <MrKanister> What to do with request for closed source printers?
[17:26] <MrKanister> I mean. They can not be included
[17:31] <Hew> MrKanister: I closed bug 6297. Make sure when you set bugs to incomplete that you are actually requesting some information. You should triage the bug that was originally reported.
[17:31] <Hew> MrKanister: As for the printer drivers, what is the request? Perhaps they can be added to multiverse, depending on their license.
[17:33] <MrKanister> Hew: bug #133121 is about the printing (don't mind my last comment on that bug, i did that when I was very very new to launchpad)
[17:34] <MrKanister> Hew: Sorry for not asking the right things bug #6297. the problem was that my english is not good enough and I didn't know how to ask what I wanted to ask. It was quite complicating :/
[17:37] <MrKanister> Information about copying: http://paste.pocoo.org/show/96290/
[17:37] <Hew> MrKanister: No problem, it was a messy bug that had nothing to do with the reporters problem. In many cases you can use the responses at https://wiki.ubuntu.com/Bugs/Responses if you are worried about correct English. In this case it was necessary to tell the commenters that they weren't commenting on the correct bug.
[17:39] <MrKanister> Ok, thanks
[17:40] <pleia2> I maintain a couple packages in debian, and recently there were some launchpad bugs opened against them
[17:40] <Hew> MrKanister: That license doesn't allow the distribution of the software, so it cannot be included even in multiverse.
[17:41] <pleia2> we're going to be uploading something to experimental soon, but I think I need some help with launchpad bug stuff to know how I'm supposed to report/change status/etc
[17:42] <pleia2> is there any documentation for this kind of thing someone can point me to?
[17:42] <MrKanister> Hew: So I can add a comment and close the bug?
[17:43] <Hew> pleia2: I'm not quite sure what you are asking. Are there Launchpad bugs that have been fixed in the experimental released that you want to mark as such?
[17:43] <Hew> pleia2: https://wiki.ubuntu.com/Bugs/Status ?
[17:43] <pleia2> Hew: yes
[17:44] <pleia2> but it's in debian experimental, I'm not really familiar with how ubuntu slurps the packages from debian, and until lenny is released we won't be moving the fixes to unstable and testing
[17:45] <Hew> MrKanister: Yes, notice in the license from about line 33 onwards, that's the problem. The bug should be marked invalid, but make sure you are clear about the reason.
[17:46] <Hew> pleia2: I think Ubuntu automatically takes sid packages. I've seen experimental ones around, but I think they're done manually (not sure on this).
[17:47] <Hew> pleia2: In any case, if the bugs are reported against Ubuntu then they can't be marked Fix Released until the package has landed in Ubuntu itself.
[17:47] <pleia2> Hew: right, so should I comment that it's fixed in experimenta, then mark them as fix-committed?
[17:47] <Hew> pleia2: Yep, that should work :-)
[17:48] <pleia2> awesome, thanks :)
[17:48] <Hew> thank you for providing the fixes!
[17:48] <MrKanister> Hew: I see. The important restriction is "You may not copy the  Software into any public network." I will close the bug with an informal comment
[17:49] <Hew> MrKanister: Yes, that sentence sums it up nicely :-)
[17:52] <MrKanister> Hew: Done
[17:53] <Hew> MrKanister: Perfect, thanks for that.
[17:55] <MrKanister> Hew: Thank you for your patience
[17:55] <pckchem> lp acting funny for others or is it just me. On edge here.
[17:55] <Hew> MrKanister: Thank you for your help triaging!
[17:56] <Hew> pckchem: edge has serious problems atm, disable redirection at https://launchpad.net/ (and in 2 hours, and 4 hours..)
[17:56] <pckchem> Thanks Hew
[17:57] <pckchem> Is it just me or are some font's looking a bit funny, even on production?
[17:58] <Hew> pckchem: I haven't noticed any font problems.
[17:59] <Hew> Standard Launchpad should be fine. If you need help you can ask the guys in #launchpad
[18:00] <pckchem> *shrug* its only on the frontpage, probably intentional I just haven't looked at the page in eons.
[18:01] <Hew> hehe
[18:23] <Rocket2DMn> does anybody think that bug 310122 might qualify for SRU?
[21:29] <MrKanister> Can sombody set bug #206095 to "wishlist"? Thanks in advance
[21:34] <crimsun> MrKanister: done
[21:34] <MrKanister> crimsun: Thank you
[21:35] <crimsun> no, thank you =)
[21:38] <MrKanister> crimsun: Can you now set it to triaged :)
[21:47] <Ryan52> MrKanister, done
[21:47] <MrKanister> Ryan52: Thanks
[23:40] <duanedesign> could someone please set the status of Bug #309953 to 'Wishlist' Thank you
[23:40] <nhandler> Done duanedesign
[23:41] <duanedesign> could someone please set the status of Bug #309953 to 'Wishlist' Thank you
[23:41] <nhandler> I already did duanedesign ;)
[23:49] <duanedesign> thank you for the prompt reply to the 'wishlist' request
[23:49] <nhandler> duanedesign: You're welcome. I'm pretty bored, so you gave me something to do ;)
[23:50] <duanedesign> I have to get my five for today so maybe I will find another:)
[23:54]  * WelshDragon test
[23:55]  * WelshDragon asd
[23:55] <duanedesign> could someone please set the status of Bug #308823 to 'Wishlist' Thank you