[04:15] <semitones> does ubuntu-bug check for duplicates before submitting?
[04:18] <greg-g> semitones: it sends the info to LP, LP then processes it, you put in a title, then the duplicate check is done, then you have the opportunity to submit or cancel
[04:19] <greg-g> so, ubuntu-bug doesn't, but LP does before it is really submitted
[04:19] <semitones> greg-g: ok thanks. I'd like to volunteer with triage maybe this summer -- I feel like marking duplicates would help a lot
[04:20] <greg-g> semitones: it does, indeed. And there's no reason to not start now! ;)
[04:21] <semitones> heh, maybe after I get out of the woods in terms of schoolwork
[04:21] <greg-g> luckily, LP is getting pretty good at finding duplicates so most new bugs that were submitted via Apport (when a crash happens) are identified as diplicates (or not) correctly
[04:21] <semitones> greg-g: does it become easy to tell when something truly is a duplicate, or when the symptoms of different bugs are the same?
[04:22] <semitones> if you are looking through launchpad
[04:22] <greg-g> the easy ones are easy ("XYZ doesn't have feature ABC" or "XYZ crashed with this error with this data set") but the others can take a bit of investigation
[04:23] <greg-g> but mostly you can figure it out with a couple back and forths with the submitter
[04:24] <micahg> ubuntu-bug does check first against stuff w/signatures
[04:29] <semitones> greg-g: because when I submitted a touchpad bug with my hardware and information, LP didn't detect any duplicates, but later I saw a bunch of other people having similar problems, and wondered if they all had the same cause too
[04:31] <micahg> semitones: hardware bugs are best submitting again in case the hardware is different
[04:31] <greg-g> semitones: and those are tough for LP to determine as duplicates, so many variables that need to be cehcked by people
[04:32] <semitones> it looked like a lot of them had to do with ALPS pointing devices
[04:49] <semitones> i just grouped all the alps pointing devices bugs into this one (had the most people affected). hope that helps https://bugs.launchpad.net/ubuntu/+source/linux/+bug/747092
[04:49] <ubot4> Launchpad bug 747092 in xserver-xorg-input-synaptics (Ubuntu) (and 1 other project) "[FUJITSU FMVNP2PL] edge scrolling does not work (affects: 10) (dups: 4) (heat: 69)" [Undecided,Invalid]
[04:53] <micahg> semitones: the Xorg team prefers separate bugs from each submitter since the hardware could be different and might need different drivers
[04:54] <micahg> s/Xorg/X/
[04:54] <semitones> oh :/ should i unduplicate them
[04:56] <micahg> semitones: hold on, let me grab someone
[04:58] <micahg> hi RAOF, so semitones duplicated some xorg bugs into bug 747092 before I mentioned that the X team prefers separate bugs for each submitter due to possible different hardware and was wondering if they should be unduped
[04:58] <ubot4> Launchpad bug 747092 in xserver-xorg-input-synaptics (Ubuntu) (and 1 other project) "[FUJITSU FMVNP2PL] edge scrolling does not work (affects: 10) (dups: 4) (heat: 69)" [Undecided,Invalid] https://launchpad.net/bugs/747092
[05:00] <RAOF> Hm.  Even more so; that's a kernel bug, and they really don't like duplicates not done by themselves.
[05:02] <RAOF> Although at least some of them appear to be duplicates.
[05:03] <micahg> RAOF: ah, sorry for dragging you in here then
[05:03] <RAOF> No problem :)
[05:03]  * micahg appears to need a caffeine boost to help with reading at this hour
[05:03] <semitones> thanks :)
[05:05] <semitones> I also wanted to try installing the mainline kernel and trying to replicate the bug
[05:05] <semitones> does it matter that I'm using maverick and not oneiric though
[05:05] <RAOF> Well, that _would_ replicate it, as the only reason it works on dell machines is that we've got a non-upstream patch fudging stuff :)
[05:06] <semitones> hmm, because the bug says it will be marked for expiration soon, so I thought I had to do something to keep it valid
[05:13] <semitones> it would be useful if there were a live usb image made for new development kernels, and you could zsync to get it.
[05:25] <RAOF> ISTR there was such a usb at one point, but it was a lot of effort to maintain.
[05:55] <Laibsch> I'd appreciate if somebody who is familiar with the maintainer scripts had a look at bug 881806 to help with triage
[05:55] <ubot4> Launchpad bug 881806 in icecc (Ubuntu) (and 1 other project) "icecc does not remove cleanly (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/881806
[06:05] <micahg> Laibsch: you should probably as in -motu
[06:06] <Laibsch> micahg: what's the purpose of this channel?  it's been pretty quiet recently.
[06:07] <micahg> Laibsch: to help triage/file bugs
[06:07] <Laibsch> that's what I'm requesting ;-)
[06:07] <micahg> right, but maintainer scripts are something you want a dev to look at
[07:48] <kanha> how to mirror a branch
[10:27] <alourie> hello
[10:27] <alourie> is bug 26394 still relevant? I think no. Unless we still support it in older releases...
[10:27] <ubot4> Launchpad bug 26394 in gnome-panel (Ubuntu) "Web browser button on top panel should open preferred application, rather than firefox/evolution" [Wishlist,Confirmed] https://launchpad.net/bugs/26394
[16:00] <bil21al> what command is used in terminal to shut down the machine in oneiric?
[16:00] <roadmr> bil21al: I do sudo poweroff
[16:02] <bil21al> is there any command if this type for shutdown "sudo shutdown -P"
[16:02] <bil21al> roadmr
[16:02] <roadmr> bil21al: sudo shutdown -h should work
[16:02] <bil21al> ok
[17:07] <bil21al> see this https://bugs.launchpad.net/ubuntu/+source/unity/+bug/865612
[17:08] <ubot4> Launchpad bug 865612 in unity (Ubuntu) (and 1 other project) "Unity slow at logout/shutting down (affects: 4) (heat: 28)" [Undecided,Confirmed]
[17:09] <bil21al> and this also
[17:09] <bil21al> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/882133
[17:09] <ubot4> Launchpad bug 882133 in chromium-browser (Ubuntu) "adding a tabs in chromium cause icons of tabs dissappear (affects: 1) (heat: 6)" [Undecided,New]
[18:00] <Laibsch> has verification-done-$release become an official tag or is the simple verification-done tag without any indication as to what release the verification was done for still the way to go?
[18:26] <bullgard4> [GNOME Shell 3.2] Rather often I cannot terminate the program »system monitor« normally. Then the  process »gnome-system-monitor« persists and takes 12% of the CPU processing time. Is this worth reporting to Launchpad?