[00:00]  * micahg facepalms since it's not on the list
[00:00] <hggdh> :-)
[00:00] <hggdh> been there, done that ;-)
[00:00]  * micahg suggests someone add that channel
[00:00] <persia> micahg, Add it :p
[00:01]  * micahg will add it later unless someone does it first
[00:01] <hggdh> I will do it
[00:01] <charlie-tca> We can do that?
[00:02] <micahg> charlie-tca: its on the Wiki, why not?
[00:02] <MiMe> Where should I report a bug if I found one in a PPA version (namely, nautilus-elementary)
[00:02] <charlie-tca> Never occurred to me it was something we could do. Braindead?
[00:02] <kklimonda> MiMe: to the owner of ppa in question.
[00:03] <persia> MiMe, You can tell the PPA owner, but there is no useful way to report that kind of bug in general.
[00:03] <micahg> MiMe: upstream or PPA owner, some team PPAs post guidelines for bug reporting
[00:03] <MiMe> Thanks all
[00:03] <persia> upstream is often not so helpful unless one has tested upstream code
[00:04] <micahg> persia: true, but it might already be reported
[00:04] <persia> true
[04:49] <RedSingularity> When closing a bug for inactivity should I mark it as "invalid"?
[04:50] <micahg> RedSingularity: yes, if you cannot reproduce it and there's not enough information
[04:50] <RedSingularity> micahg:  ok
[05:00] <persia> What?
[05:01] <persia> I thought we had the new shiny "expired" status for those that we were supposed to use.
[05:01] <RedSingularity> persia: Really?
[05:01] <persia> I'm not a big fan of "expired", for lots of reasons, but I'm not sure why we oughtn't use it if we must have it.
[05:02] <RedSingularity> persia:  I dont see an "expired" tag.
[05:02] <RedSingularity> under status??
[05:02] <persia> I'm not sure how it works for users: might need the API or something.
[05:02] <persia> Anyway, may as well set "Invalid" which is the correct way of doing things pre-expired.
[05:03] <persia> And sometime when more people are awake, we can argue over whether that's still a good thing to do.
[05:03] <persia> (and how to use expired)
[05:10] <vish> persia¦ yea, expired is available now only via API..  so when doing it manually people are using the good old invalid..
[05:12] <persia> vish, We oughn't have two ways to do it.  If "expired" is correct, we ought have a script that does so via the API that we use if we need to expire bugs.
[05:12] <micahg> Expired is API accesible only
[05:12] <persia> Just something tucked in ubuntu-qa-tools that lets us say things like `expire LP#2"
[05:13] <vish> i think the kernel team and the x team already have scripts running to expire bugs..
[05:22] <persia> Indeed, and the LP team has started to run some internally.
[05:22] <persia> Doesn't help for the rest of things (like the one RedSingluarity was working on)
[07:01] <micahg> RedSingularity: bug 663099 is due to an out of date mirror
[07:01] <ubot2> Launchpad bug 663099 in update-manager (Ubuntu) "failed to fetch http://ftp.udc.es/ubunto/pool/universe/o/orc/liborc-0.4-0_0.4-5-1_i386.deb 404 Not Found (affects: 1) (heat: 8)" [Undecided,Incomplete] https://launchpad.net/bugs/663099
[07:06] <persia> Sometimes I think we ought set the default sources.list with the local mirror as primary and the base mirror as secondary so that failures like that fall back to archive.ubuntu.com and just work.
[07:06] <persia> Of course, this might result in archive.ubuntu.com being as slow as ports.ubuntu.com, and that would be annoying.
[07:07] <RedSingularity> micahg:  I figured....what do you recommend?
[07:07] <micahg> RedSingularity: #ubuntu-mirror for help?
[07:08] <RedSingularity> micahg:  that is a custom mirror no?  Its not official ubuntu correct?
[07:10] <micahg> RedSingularity: it's listed as an archive mirror
[07:12] <RedSingularity> micahg:  The site is http://ftp.udc.es/   That doesnt look ubuntu related.  It has many distros in it as well.
[07:12] <micahg> RedSingularity: https://edge.launchpad.net/ubuntu/+mirror/ftp.udc.es-archive
[07:12] <RedSingularity> micahg: ahhh can I mark the bug to that instead of update-manager?
[07:14] <micahg> RedSingularity: no, but you can remove the package
[07:14] <micahg> persia: what do you think of subscribing ubuntu-mirror-admins ^^^
[07:15] <persia> I think it won't help.
[07:15] <persia> Is the package still missing?
[07:15] <micahg> persia: yes, the file listing is not in sync with the files in the mriror
[07:15] <persia> Looks like that mirror doesn't have universe at all.
[07:16] <persia> Um.  Notice "ubunto" vs. "ubuntu"
[07:16]  * micahg has ubuntu in the URL
[07:16] <persia> http://ftp.udc.es/ubunto/pool/universe/o/orc/liborc-0.4-0_0.4-5-1_i386.deb
[07:17] <micahg> http://ftp.udc.es/ubuntu/pool/universe/o/orc/liborc-0.4-0_0.4.5-1_i386.deb just as broke
[07:17] <persia> http://ftp.udc.es/ubuntu/pool/universe/o/orc/liborc-0.4-doc_0.4.5-1_all.deb is there
[07:18] <micahg> persia: not for me
[07:18] <RedSingularity> or me
[07:18] <persia> with "all" or "i386"?
[07:18] <micahg> either, it's out of date anyways (current version is 0.4.6-1
[07:18] <persia> Oh, I see.
[07:19] <persia> Well, some might argue it's 1:0.4.11-1 :)
[07:19] <persia> But I don't see any reason for 0.4.5-1 to be around, based on rmadison output.
[07:19] <persia> I expect it not to be there.
[07:19] <micahg> I'm assuming the user is sane, so I assumed Maverick
[07:20] <persia> I expect 0.4.2-1, 0.4.3-5, 0.4.6-1, and 1:0.4.11-1
[07:20] <persia> (although the last appears to be missing)
[07:20] <micahg> right
[07:20] <micahg> well, I would expect the last one to be msising if 0.4.6 is missing :D
[07:21] <RedSingularity> Whats the verdict?  Remove update-manager?
[07:21] <micahg> RedSingularity: definitely not update-manager's fault, it's being returned a false list
[07:21] <persia> It's a broken mirror.  Failed update started 01-Jul-2010 17:32 and hasn't recovered.
[07:21] <RedSingularity> micahg: i agree
[07:22] <RedSingularity> I cant remove the package....can you?
[07:22] <micahg> RedSingularity: hggdh has dealt with mirror issues before, we should get some type of procedure written for broken mirror bugs
[07:23] <persia> Problem is that only the mirror admins can do anything.
[07:23] <micahg> persia: right, but we need a procedure for contact or a bucket to toss these bugs
[07:23] <persia> I suppose we could try to SRU python-apt everytime we found a broken mirror, but that seems like it would get painful fast.
[07:23] <persia> can't we reassign to ubuntu-mirrors?
[07:23] <micahg> persia: if they use that workflow, that's my question
[07:24] <persia> Ah, no.  That's not a project anymore.
[07:24] <persia> Could subscribe the mirror admin to the bug :)
[07:25] <RedSingularity> Sounds good to me....micahg??
[07:25] <persia> https://launchpad.net/ubuntu/+archivemirrors should provide a link to the mirror registration, which should have a listed administrator.
[07:25] <micahg> RedSingularity: sure
[07:27] <RedSingularity> Give the user the email address for the maintainer?
[07:28] <persia> I'd probably subscribe the mirror admin to the bug, and then add a note that this appears to be an out-of-date mirror (carefully commenting on the timestamp of the Archive-update-in-progress file in the mirror root).
[07:28] <persia> The admin would be sent a copy (as they were subscribed), and could follow up in the bug.
[07:29] <persia> Otherwise the user has to contact the admin, and we can't know whether that conversation goes well or badly.
[07:29] <RedSingularity> And mark as invalid?
[07:29] <persia> In a bug we can help mitigate, and make sure the right thing happens.
[07:29] <persia> I'd leave it "triaged" and against no package until resolved: this will require following it.
[07:31] <RedSingularity> Take the liberty to mark?  And how can I remove the package?
[07:31] <persia> Same as reassigning to a different package, except erase the name of the package completely.
[07:32] <persia> And please go ahead with this one, yes.  If you can't do "triaged", "confirmed" works just as well.
[07:32] <persia> Still ought get raised on the mailing list: we ought have a useful bucket for these.
[07:33] <persia> And like I said before, I'm not sure it's not a bug in python-apt that we aren't automatically providing fallback mirrors when the selected ones fail.
[07:33] <persia> (but not worth cluttering that report with actual issues, really)
[12:21] <TomAble> Hi there, I'd like to report a bug: ubuntu 10.10-alternate.i386 overwrited my crypt partition during setup without asking. The partition was tagged as "Linux LVM (df)" but contained crypted data created by "cryptsetup luksFormat". It seems, that ubuntu 10.10 figured out that it wasn't able to read any pv-information from the lvm partition and decided to do a pvcreate on the partition without asking.
[12:22] <TomAble> after setup the partition header looked exactly as a header when you do a pvcreate on a partition manually
[12:23] <TomAble> I was able to reproduce this
[12:24] <TomAble> looks to me, like ubuntu now acts almost similar to Windows - what I don't know I'll overwirte and better not ask the dumb user
[12:27] <persia> It shouldn't be overwriting without you telling it.
[12:27] <persia> Could you file a bug with full installer logs?
[12:27] <TomAble> yes I would also apreciate that
[12:27] <TomAble> how Do I do that?
[12:27] <persia> `ubuntu-bug debian-installer` might work
[12:28] <persia> I suspect it won't, and you'll have to file the bug manually.
[12:28] <persia> To file it manually, start from http://bugs.launchpad.net/ubuntu/+source/debian-installer/+bugs
[12:28] <TomAble> is there any documentation, ... thanks :-)
[12:29] <persia> I'd recommend attaching everything from /var/log/ in the installer environment.  The syslog and the parted.log are most important.
[12:30] <TomAble> okay, thanks for the info.
[12:31] <persia> Thanks for the report.  I've done a few alternate installs with prior use of LVM and luks and preserved them.  I'm sure something went odd (and am even more sure it's not intentional)
[12:44] <TomAble> yes, that's what I assume also :-) I did also a few alternate installs with releases before 10.10 and always kept my crypt-partition untouched during installation. This went well all the time, but this time the crypt partition now has a fine LVM2 header
[15:33] <drizztbsd> hi
[15:33] <drizztbsd> any news for bug #422284?
[15:33] <ubot2> Launchpad bug 422284 in universalindentgui (Ubuntu) "universalindentgui crashed with SIGSEGV in QsciScintilla::setLexer() (affects: 3) (heat: 7)" [Medium,New] https://launchpad.net/bugs/422284
[15:46] <hggdh> drizztbsd: looking
[15:46] <drizztbsd> regression bug
[15:47] <drizztbsd> since with qscintilla 2.4.3 works
[15:49] <hggdh> drizztbsd: since the bug was opened (against karmic), a new version of the package has been published (1.1.0). Have you tested with it?
[15:49] <drizztbsd> yes
[15:49] <drizztbsd> I use 10.10
[15:50] <hggdh> are you the bug reporter?
[15:51] <drizztbsd> no
[15:51] <drizztbsd> I onlu hate to open duplicates
[15:51] <drizztbsd> only
[15:52] <hggdh> please update the bug with your findings. Upstream is at http://universalindent.sourceforge.net/, seems dormant, but I will see the bugs list there
[15:57] <hggdh> drizztbsd: what qscintilla is current now? (meaning version)
[15:58] <drizztbsd> 2.4.4
[15:58] <drizztbsd> if I install 2.4.3 it works
[15:58] <hggdh> yes, I found https://sourceforge.net/tracker/?func=detail&aid=2947699&group_id=167482&atid=843127 but then it does not match :-(
[15:59] <ubot2> hggdh: Error: <Bugtracker.plugin.Sourceforge instance at 0xa0bf24c> bug 2947699 not found
[16:04] <hggdh> drizztbsd: did you get an apport crash file for this error?
[16:08] <hggdh> drizztbsd: reason is it is a new version, and newer qscintilla -- I am not sure it is the same issue
[18:13] <pedro_> devildante, https://blueprints.edge.launchpad.net/ubuntu/+spec/ubuntutheproject-qa-n-bugsquad-doc-review
[18:13] <devildante> thanks pedro_ :)
[18:14] <pedro_> you're welcome
[18:14] <devildante> maybe you'll want to subscribe yourself to the blueprint?
[18:14] <pedro_> I guess i should be since i've registered?
[18:14] <pedro_> oh well don't trust lp
[18:14] <pedro_> :-P
[18:58] <slinker> can I report a bug I upstreamed?
[19:00] <rusivi> slinker: What is the link to the upstream bug?
[19:00] <slinker> I tagged it onto 663364 already
[19:04] <vish> pedro_¦ boo! you closed Bug 663119 ! ;p
[19:05] <ubot2> Launchpad bug 663119 in nautilus (Ubuntu) (and 5 other projects) "Unneeded items in System > Preferences (affects: 27) (heat: 124)" [Undecided,Invalid] https://launchpad.net/bugs/663119
[19:05] <pedro_> vish, yeah ;-)
[19:05] <vish> pedro_¦ since that bug is a troll bait, i was waiting for everyone to comment there and then mark it a dup ;p
[19:05] <vish> it would be a dup of an invalid bug … hehe!
[19:06] <pedro_> vish, oh you're evil :-P
[19:06] <vish> pedro_¦ you spoiled  my evil plan :(
[19:08] <vish> pedro_¦  i knew where the 'traffic' was coming from , and if i marked the bug as dup or invalid, it would only move the discussion to another bug.. and spam more people.. :(
[19:08] <pedro_> lol
[19:08] <pedro_> vish, you really had a whole plan for it
[19:09] <pedro_> vish, i'll stay away from you next week :-P
[19:09] <vish> pedro_¦ hehe, nah.. i suddenly say a lot of comment on one bug and wondered if i should close it early,but i knew *I* would be trolled instead, so i stayed silent :
[19:10] <vish> saw*
[19:15] <vish> pedro_¦ btw, that whole bug is a moot point with http://live.gnome.org/Design/SystemSettings in gnome 3 ;)
[19:17] <kklimonda> vish: damn, it's less than 6 months before GNOME 3 is supposed to be released and there is nothing substantial on this page..
[19:18] <vish> kklimonda¦ my thoughts too, but it seems a lot of the background work is getting done, its more of the GUI design that needs to be completed..
[19:18] <vish> or so i am told..
[19:18] <kklimonda> vish: so we should buckle up for KDE 4.0 bis..
[19:18] <vish> hehe!
[19:18] <kklimonda> vish: can you change the character after nick you use for completion?
[19:19] <kklimonda> weechat doesn't highlight it properly (or not at all)
[19:19] <vish> kklimonda¦ hmm, is it breaking your irc client? :)
[19:19] <kklimonda> indeed
[19:19] <vish> ah!
[19:19] <hggdh> kklimonda: what gives on weechat?
[19:20] <kklimonda> hggdh: I can see the ¦ character, weechat just doesn't consider it a proper nick to highlight.
[19:20] <vish> yea, it prevents me from tab complete too  it just stays on as part of the nick, and i cannot switch to the next name..
[19:20] <kklimonda> it's a bug in weechat but before it's fixed vish is going to be ignored ;)
[19:21] <vish> vish ¦
[19:21] <hggdh> kklimonda: have you tried the Latest & Greatest from my PPA?
[19:21] <vish> kklimonda ¦ works now?
[19:21] <vish> kklimonda ¦ it should have highlighted now..
[19:22] <kklimonda> vish: works fine
[19:22] <kklimonda> hggdh: no :)
[19:22] <vish> wheeeeeeeeee!!
[19:22] <hggdh> kklimonda: might be interesting -- it is 3.4-dev, updated almost daily
[19:23] <njin> pedro_: hello, can i disturb ?
[19:24] <pedro_> njin, you can always disturb hggdh or vish, sure :-P
[19:24] <kklimonda> hggdh: I almost never restart my irc client
[19:24] <kklimonda> hggdh: and when I do I prefer it to work ;)
[19:24] <pedro_> njin, btw feel free to ask in the channel, there's no need to ask if you can ask something
[19:24] <njin> pedro_. can we look at tyhis wishlist ?
[19:24] <njin> https://bugs.launchpad.net/ubuntu/+bug/662919
[19:24] <ubot2> Launchpad bug 662919 in ubuntu "UPnP MediaServer KIO-slave (affects: 1) (heat: 6)" [Undecided,New]
[19:24] <vish> !ask | \o/
[19:24] <ubot2> \o/: Please don't ask to ask a question, simply ask the question (all on ONE line and in the channel, so that others can read and follow it easily). If anyone knows the answer they will most likely reply. :-)
[19:24] <kklimonda> hggdh: I know, there is /reload or maybe /restart but I'm connected to most networks using ssl so it doesn't work for me.
[19:25] <kklimonda> hggdh: I guess I'm conservative when it comes to the IRC clients :)
[19:25] <hggdh> kklimonda: it is /upgrade
[19:25] <hggdh> kklimonda: but yes, it will bounce the SSL/TLS sessions
[19:25] <pedro_> njin, what about it?
[19:26] <pedro_> njin, what's your question about the bug exactly
[19:26] <njin> pedro_: i've tsalked yesterday about this with xtee.. and he said that this is a wishlist
[19:27] <njin> pedro_: he ask me to cleanout it in accord to our standards but i don't understand what he mean
[19:28] <pedro_> njin, right, looks like the reporter is asking for that package to be included in Ubuntu
[19:28] <njin> ok
[19:28] <pedro_> njin, have a look to  https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages#Requesting%20a%20new%20package%20for%20Ubuntu
[19:28] <hggdh> kklimonda: just upgraded, BTW :-)
[19:29] <pedro_> njin, there's a couple of example bug reports there, feel free to edit the previous bug to look alike to the examples
[19:29] <njin> pedro_: thanks, i'm looking
[19:29] <pedro_> njin, template is here: https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages/ExamplePackageRequest
[19:29] <pedro_> njin, you're welcome
[19:32] <vish> njin ¦ btw, i think you are doing an incredible amount of work, thanks for helping with bugs :)
[19:32] <njin> vish: thanks :-) it mekes me happy
[19:33] <njin> *makes
[19:33] <vish> :)
[20:12] <njin> pedro_: done, can you take a look ? https://bugs.launchpad.net/ubuntu/+bug/662919
[20:12] <ubot2> Launchpad bug 662919 in ubuntu "[needs-packaging] UPnP MediaServer KIO-slave (affects: 1) (heat: 6)" [Undecided,New]
[20:13] <pedro_> njin, looks fine, want me to set it as Wishlist for you?
[20:13] <njin> pero_: of course
[20:14] <pedro_> doing that now
[20:14] <njin> pedro_: of course
[20:14] <pedro_> njin, done, thanks for helping :-)
[20:14] <njin> thank to youu to help me .9
[21:13] <njin> hello  set status to https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/656745
[21:13] <ubot2> Launchpad bug 656745 in gnome-power-manager (Ubuntu) "dell vostro 3700 always crash (frozen) if I work with battery (power or thermal limit exceeded) (affects: 2) (heat: 14)" [Undecided,Confirmed]
[21:13] <njin> thanks
[21:25]  * hggdh just sent a request for niceness on the bugsquad ML, and sits down and waits
[21:32] <njin> hello guys , a good man to set importance here https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/657508
[21:32] <ubot2> Launchpad bug 657508 in gnome-power-manager (Ubuntu) "Network becomes sluggish when running on battery (affects: 2) (heat: 14)" [Undecided,New]
[21:32] <njin> and here https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/656745
[21:32] <ubot2> Launchpad bug 656745 in gnome-power-manager (Ubuntu) "dell vostro 3700 always crash (frozen) if I work with battery (power or thermal limit exceeded) (affects: 2) (heat: 14)" [Undecided,Confirmed]
[21:33] <njin> thanks
[21:39] <Book_em_Dano> Would anyone mind giving me some assistance with triaging this bug, LP: #658183?
[21:39] <Book_em_Dano> Not sure what to look for in the logs
[21:40] <Book_em_Dano> I see a lot of activity w/ the open chrome driver, but not sure if that is the culprit
[22:13] <flipefr> hi
[22:14] <flipefr> can anybody look at the bug 663326
[22:14] <ubot2> Launchpad bug 663326 in gparted (Ubuntu) "gparted crashes on startup (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/663326
[22:41] <flipefr> hi
[22:41] <flipefr> can anybody look at the bug 663326
[22:41] <ubot2> Launchpad bug 663326 in gparted (Ubuntu) "gparted crashes on startup (affects: 1) (heat: 6)" [Undecided,Incomplete] https://launchpad.net/bugs/663326
[22:46] <rusivi> flipefr: The first thing that comes to my mind is did you md5sum the iso you downloaded and the CD you burned?
[22:48] <rusivi> that's what I would want the OP to answer of course ;)
[22:48] <flipefr> of course
[22:48] <flipefr> i will ask him
[22:48] <flipefr> thanks
[22:49] <flipefr> rusivi
[22:49] <rusivi> np, I'm hyper paranoid about bugging LiveCD stuff that I did not md5sum the iso and the burned CD. If I don't do both, I don't bug live cd issues.
[22:50] <rusivi> I don't trust my CD/DVD drive :p
[23:01] <devildante> rusivi: it's a bug, then :p
[23:17] <flipefr> rusivi: thanks again for your confindence about your cd drive
[23:17] <flipefr> i am leaving
[23:18] <flipefr> bye
[23:48] <Book_em_Dano> Would anyone mind giving me some assistance with triaging this bug, LP: #658183?
[23:48] <Book_em_Dano> Not sure what to look for in the logs to pinpoint what is going wrong.