=== emma is now known as em
pedro_hey folks, I'm designing the mentor reporting template, did i miss anything? http://paste.ubuntu.com/538616/12:04
vishpedro_: how many bugs? or list of bugs?12:24
vishah, well.. we could just gmane it :)12:25
vishpedro_: when exactly to use the template?  dint we abandon the mentorship and start with the mentor group?12:26
pedro_vish, this is more to report to the bugsquad/mentorship admin team so we can know what is the mentor/student doing12:28
pedro_vish, we can start using it for the next bugsquad meeting12:28
pedro_vish, right, with the mentor group you'll have students anyways, and  we need some info about how are they doing it :-)12:29
vishyay! i got 3 banshee bugs before kamusin got to them !! ;p12:45
vishno wait 4!12:45
kamusinvish, \o/ heee12:48
Psi-JackAlright, I'm trying to look into the issue that's a serious lsb-init bug still existant in Ubuntu 10.04.1 regarding status_of_proc, and I'm wondering if anyone here knows about it and if there's any bugs relating directly to it.13:22
=== yofel_ is now known as yofel
charlie-tcaseb128, bug 68336113:53
ubot2Launchpad bug 683361 in compiz (Ubuntu) "compiz crashed with SIGSEGV in radeon_bo_get_tiling() (affects: 1) (heat: 10)" [Undecided,New] https://launchpad.net/bugs/68336113:53
charlie-tcachanged to public with the coredump attached?13:53
=== ssj6akshat is now known as synapselover
Psi-JackOkay.. So, what's up with the bug tracker, I'm trying to link a bug to another bug, and it's telling me https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/683650 is a bug in a remote bug tracker, trying to link it for https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/68364013:54
ubot2Launchpad bug 683650 in dovecot (Ubuntu) "status_of_proc is returning incorrect error code (affects: 1) (heat: 6)" [Undecided,New]13:54
=== synapselover is now known as ssj6akshat
seb128charlie-tca, yes?13:56
seb128charlie-tca, not sure if that's a question13:56
charlie-tcaI thought you never take bugs from private to public with the coredump13:56
seb128why not?13:57
seb128well it's never done automatically13:57
charlie-tcaseb128, private data in the dump13:57
seb128but compiz doesn't hold user datas so I don't see the issue13:57
charlie-tcaI see. Okay13:57
charlie-tcaPsi-Jack, trying to link them how?13:57
seb128well in fact the bug made the retracer crash13:57
seb128so I made it public to easy debugging13:58
seb128it's going to be retraced and cleaned rsn13:58
Psi-Jackcharlie-tca: Still an error.13:58
seb128I didn't see an issue with making a compiz dump public for a bit13:58
seb128since it doesn't hold any datas13:58
charlie-tcaOuch. I guess that does matter. Just trying to make sure I understand13:58
Psi-Jackcharlie-tca: Oh..13:58
charlie-tcaPsi-Jack, they could be duplicates of each other, but they are both reported against ubuntu13:58
Psi-Jackcharlie-tca: On https://bugs.launchpad.net/ubuntu/+source/lsb/+bug/683640, I click on "Also affects project"13:59
ubot2Launchpad bug 683640 in lsb (Ubuntu) "status_of_proc is returning incorrect error code (affects: 1) (heat: 6)" [Undecided,New]13:59
charlie-tcaPsi-Jack, they are not upstream at all. They are both local ubuntu bugs13:59
charlie-tcaIf one is a duplicate of the other, just use "Mark as duplicate" in the upper right14:00
Psi-JackIt's not a duplicate. I made them both.14:00
Psi-JackOne is for lsb, one is for dovecot being effected by bugs in lsb.14:00
charlie-tcaThen you just comment on them14:00
charlie-tcaThey are both in ubuntu, though. You can't link them as projects of each other.14:00
charlie-tcaThanks, seb12814:01
charlie-tcaPsi-Jack, normally, you would just comment on each one that bug ??? is related to this issue14:02
Psi-JackGotcha.. Not sure how launchpad works, but not liking it, but eh well. ;)14:03
njinara: hello 20101201 amd64 still without panels14:03
njinbug 68340314:03
ubot2Launchpad bug 683403 in gnome-session (Ubuntu) "natty 20101130.1 without panel (affects: 2) (heat: 12)" [Low,Confirmed] https://launchpad.net/bugs/68340314:03
charlie-tcanjin, If you don't have the video hardware for unity with compiz, choose "classic desktop" session14:04
charlie-tcaThat is the no fallback issue14:04
Psi-JackOkay, so now, it's at least reported. Now to see if I can solve the problem myself. ;)14:04
charlie-tcanjin, Is that a duplicate of bug 683356 ?14:07
ubot2Launchpad bug 683356 in compiz (Ubuntu Natty) (and 1 other project) "Unity lost the 2D failback feature (affects: 4) (heat: 20)" [High,Fix released] https://launchpad.net/bugs/68335614:07
njincharlie-tca: hello, thanks, but now live session are unusable, i'm looking the other report14:08
Psi-JackHeh, sheash..14:12
Psi-JackThis is scarey.. Almost looks like whomever made the init-functions knows a "reasonable" amount of lsb standards, but completely failed to grasp the status portion completely.14:12
epimethIs it possible the package maintainers forgot to add the new linux-headers package to the latest upgrade?14:44
charlie-tcaepimeth, what is the issue?14:46
epimethI upgraded last night and when I went to turn on my computer today my wireless card and nvidia driver werent working... apt-get install linux-headers-$(uname -r) fixed the problem...... I figure that should have been part of the upgrade process no?14:46
charlie-tcaI don't know14:47
charlie-tcaI suppose file a bug for it14:48
epimethdo I do that in launchpad under kubuntu? or ubuntu? is there a specific package I need to enter it under?14:49
charlie-tcaepimeth, using a terminal,    ubuntu-bug linux14:51
epimethcharlie-tca: kk, cheers14:54
charlie-tcaThank you14:55
=== zyga is now known as zyga-food
=== zyga-food is now known as zyga
=== AbhiJit_ is now known as AbhiJit
=== bilalakhtar is now known as cdbs
=== deryck is now known as deryck[lunch]
=== deryck[lunch] is now known as deryck
njinhello to all, bug 683459 I don't know at wich package assign, can you help. Thanks17:39
ubot2Launchpad bug 683459 in ubuntu "hyper and super keys are mapped to the same modifier (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/68345917:39
sinurgenjin, no clue :|17:41
njinsinurge, too advanced for me17:44
sinurgenjin, for me as well guess lets leave it as what is17:45
jcastrobdmurray: http://status.qa.ubuntu.com/qapkgstatus/unity19:02
jcastrohey I was wondering, why not graph Fix Released?19:02
bdmurrayjcastro: because it will only ever increase and no work is required of those bugs19:06
njinbug 68385020:57
ubot2Launchpad bug 683850 in gconf (Ubuntu) "natty 20101201.1 amd 64, loop at login screen (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/68385020:57
njinouh, already rebuilded20:58
njinbug 68385321:00
ubot2Launchpad bug 683853 in gnome-panel (Ubuntu) "natty 20101201.1 amd64 classic desktop in live session, missed restart and shutdown (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/68385321:00
=== JanC_ is now known as JanC
=== bilalakhtar_ is now known as cdbs
=== greg_g is now known as greg-g
Psi-JackOkay, so I'd filed a bug using ubuntu-bug -p lsb-base, and it submits it as a bug for lsb, because lsb is the source package for lsb-base, correct?23:11
micahcowanSounds right to me.23:12
Psi-JackYeah, Sarge Hallyn completely fubared up my bug report.23:12
micahgPsi-Jack: -p is deprecated BTW, it's just ubuntu-bug lsb-base23:12
Psi-JackSame result, either way, launchpad associates it to lsb.23:17
micahgPsi-Jack: if you want to drop the bug # here, someone can look into it23:19
ubot2Launchpad bug 683640 in spamassassin (Ubuntu) (and 6 other projects) "status_of_proc is returning incorrect error code (affects: 1) (dups: 1) (heat: 12)" [Undecided,Invalid]23:20
micahgPsi-Jack: right, but if the root cause is determined to be in lsb, the bug should be fixed there23:22
Psi-JackYep. That's what I said. lsb is the actual source package that makes lsb-base.23:23
micahgPsi-Jack: so how is the bug report messed up?23:23
Psi-JackWell, the bug also effects the LSB init of all the other packages I associated with it, and Sarge marked them all invalid.23:24
micahgPsi-Jack: right, but is there an actual issue to be fixed in those packages?23:25
Psi-JackWhich also prohibits them from working properly in a CRM situation, like pacemaker.23:25
micahgPsi-Jack: right, but is there anything to be fixed in those packages?23:27
Psi-JackThey themselves are broken as a root cause of lsb being broken. So not technicaly, as far as I know, unless changing lsb-base's init-functions causes errors in them.23:27
micahgPsi-Jack: right, so they're affected, but there's nothing to do, hence invalid23:27
Psi-JackI see.. Sorta.. heh23:29
Psi-JackHeh. but yeah. Found this one myself because I was trying to put dovecot under pacemaker management control, and when I stopped it, pacemaker started throwing errors because of the return code of dovecot after it was stopped was 4, because the pidfile was deleted as a result of stopping it. Which is correct, except that's expected of stopped services. heh23:34
Psi-Jackmicahg: Now, here's a question.23:41
Psi-Jackclamav's package's init'd script for clamav-daemon and clamav-freshclam both aren't directly related to lsb because they re-write in the init script status_of_proc, /instead/ of using the init-functions's status_of_proc function proper. Would this be considered related, and needed to be fixed as a result of that?23:42
micahgPsi-Jack: if it's indeed broke, yes23:49
Psi-JackYeah. clamav-daemon literally has in it's script, status_of_proc() { ... } which is pretty much a clone of /lib/lsb/init-function's almost fully.23:50
Psi-JackI'd call that broken as a result of not being LSB compliant, for starters, for re-defining the function.23:51
micahgScottK: ^^23:51
ScottKPsi-Jack: What release are you on?23:52
ScottKPsi-Jack: Neither Debian nor Ubuntu are LSB compliant themselves.  It's explicitly not a design goal.  It is a goal for LSB compliant packages to work on Debian and Ubuntu.  Your point is orthogonal to this.23:53
ScottKPsi-Jack: I'm open to patches on clamav to use the lsb functions however.23:54
Psi-JackWell, I know ubuntu/canonical is going towards upstart, but for things that /are/ lsb-init oriented, and I'm sure Debian wants to continue to keep in that direction as well, it is important that they /are/ actually lsb-init compliant for CRM control.23:55
Psi-JackAnd upstart... I won't go into how many million bugs on it I need to file. ;)23:56
ScottKPsi-Jack: For clamav there's no reason not to use the lsb init stuff.23:57
Psi-JackReinventing the wheel whilst stil breaking lsb-init compliancy is a bug.23:57
Psi-JackSo yeah. :)23:57
ScottKThe clamav package predates the existance of those functions in Ubuntu/Debian.23:57
Psi-JackAhhh. That makes sense. :)23:58
ScottKSo if you can diff me a diff to use the lsb-init functions I think that's a reasonable thing to do and I'll get it pushed into Debian as well.23:59
Psi-JackYep. I can do that. I'd planned on it, too, because I use that in my pacemaker cluster as well.23:59

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!