From brian at ubuntu.com Thu Aug 1 15:05:54 2013 From: brian at ubuntu.com (Brian Murray) Date: Thu, 1 Aug 2013 08:05:54 -0700 Subject: Bug assigned to Ubuntu but there is no package In-Reply-To: References: <51F96D26.60503@the-gammons.net> <51F981B0.9000601@the-gammons.net> Message-ID: <20130801150554.GF2917@murraytwins.com> On Wed, Jul 31, 2013 at 06:57:16PM -0500, Adolfo Jayme Barrientos wrote: > I removed the Ubuntu task from the bug report, thank you. Could you explain how you did this so that other readers of the list can learn how? -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From retail at the-gammons.net Thu Aug 1 15:16:06 2013 From: retail at the-gammons.net (Ross Gammon) Date: Thu, 01 Aug 2013 17:16:06 +0200 Subject: Bug assigned to Ubuntu but there is no package In-Reply-To: <20130801150554.GF2917@murraytwins.com> References: <51F96D26.60503@the-gammons.net> <51F981B0.9000601@the-gammons.net> <20130801150554.GF2917@murraytwins.com> Message-ID: <51FA7BB6.6020200@the-gammons.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/01/2013 05:05 PM, Brian Murray wrote: > On Wed, Jul 31, 2013 at 06:57:16PM -0500, Adolfo Jayme Barrientos > wrote: >> I removed the Ubuntu task from the bug report, thank you. > > Could you explain how you did this so that other readers of the > list can learn how? > > -- Brian Murray Ubuntu Bug Master > I had the same thought. I googled and found this (a blog from 2011): http://blog.launchpad.net/bug-tracking/removing-a-project-from-a-shared-bug-report It says a feature would be added to Launchpad to allow a task to be deleted from a bug (only when there is more than one task). But only the person that originally added the task, the maintainer of the package, or the Bug Supervisor could do it. I assume that is what was done! Ross -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with undefined - http://www.enigmail.net/ iQIcBAEBAgAGBQJR+nurAAoJEFP+e72miRD828kP/0NHyHlG9GiSgttdfNf07gok 5PtjT0yZbGHUVx/MOMiPCCmAGMaKIkq6k9QrmzyzsqUzs9WvlEI7wYfsowCl0EPi OuYVT4tqnm7JXfJpzq5lb8GufSn3iD939vT4ytfR+LrrCo9nrwhi37Et8PWjW03z vy98l6ladO8WOmQe937K7Vo4KgOs9ZL1yDM2PEWrVrXJ9dtXHmKJ8FcyJQXwN/fc 83nSDIrw0bxpclwGBtsj6oLlawE8xuk0GkGJRKRRlgRx2EAvfi8ZTkotdq4CcGPX nkVoz5XFSD5TpyMlopm3P/I4L48dGTPp6WOOWXLpJNNQpUjCx4welICMTCZjOHav BLX3hyNz7V7Yo3KutyIYhimlMlDVQ3YrEGumEGtOtQOnL6UKqbKlAWkI2yLRTSv1 TLIPkt7UjBWefV+Ik4J8Z0k72rrIN4IkQqbirbaBGiLhT8IWQlCiwKRirhHHkgeX 3ZZAc8kVJXb952+aNf8RxWPrN7Mgg9dpaej1JHmzITh6kT3LYDGyeduC7C7GLuIx k+Y92raIKLRexWcMOmWqlAj35pTc7Rwl+3P1DQIxjHBpmfO8mHM31ThU3nfsDuS3 0aZeFyne8S8nzzSLOVKKRXAXHsRKgC/y2j3bROT6QdoKIsfuHez/KLXa3+6RZI7B lHKKHJcCpezZ6lg3Fc/L =fhSl -----END PGP SIGNATURE----- From matthew.fischer at canonical.com Thu Aug 1 15:20:12 2013 From: matthew.fischer at canonical.com (Matthew Fischer) Date: Thu, 1 Aug 2013 09:20:12 -0600 Subject: Bug assigned to Ubuntu but there is no package In-Reply-To: <20130801150554.GF2917@murraytwins.com> References: <51F96D26.60503@the-gammons.net> <51F981B0.9000601@the-gammons.net> <20130801150554.GF2917@murraytwins.com> Message-ID: I can explain. There's a minus sign by the second task. You just need to click on it, if you have the permissions to do so. See screencap of this example lightdm bug for the "minus sign". [image: Inline image 1] On Thu, Aug 1, 2013 at 9:05 AM, Brian Murray wrote: > On Wed, Jul 31, 2013 at 06:57:16PM -0500, Adolfo Jayme Barrientos wrote: > > I removed the Ubuntu task from the bug report, thank you. > > Could you explain how you did this so that other readers of the list can > learn how? > > -- > Brian Murray > Ubuntu Bug Master > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot from 2013-08-01 09:18:57.png Type: image/png Size: 26646 bytes Desc: not available URL: From brian at ubuntu.com Thu Aug 1 18:12:16 2013 From: brian at ubuntu.com (Brian Murray) Date: Thu, 1 Aug 2013 11:12:16 -0700 Subject: Bug assigned to Ubuntu but there is no package In-Reply-To: <51FA7BB6.6020200@the-gammons.net> References: <51F96D26.60503@the-gammons.net> <51F981B0.9000601@the-gammons.net> <20130801150554.GF2917@murraytwins.com> <51FA7BB6.6020200@the-gammons.net> Message-ID: <20130801181216.GG2917@murraytwins.com> On Thu, Aug 01, 2013 at 05:16:06PM +0200, Ross Gammon wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 08/01/2013 05:05 PM, Brian Murray wrote: > > On Wed, Jul 31, 2013 at 06:57:16PM -0500, Adolfo Jayme Barrientos > > wrote: > >> I removed the Ubuntu task from the bug report, thank you. > > > > Could you explain how you did this so that other readers of the > > list can learn how? > > > > -- Brian Murray Ubuntu Bug Master > > > I had the same thought. I googled and found this (a blog from 2011): > http://blog.launchpad.net/bug-tracking/removing-a-project-from-a-shared-bug-report > It says a feature would be added to Launchpad to allow a task to be > deleted from a bug (only when there is more than one task). But only > the person that originally added the task, the maintainer of the > package, or the Bug Supervisor could do it. Thanks for finding that post. The Bug Supervisor for the Ubuntu distribution in Launchpad is set to Ubuntu Bug Control so members of that team can remove tasks. -- Brian Murray Ubuntu Bug Master From one.ukit at gmail.com Sat Aug 10 09:38:13 2013 From: one.ukit at gmail.com (Phil Wyett) Date: Sat, 10 Aug 2013 10:38:13 +0100 Subject: Bug Squad and a lot of asks to update BIOS Message-ID: <1376127493.6307.3.camel@u-k-i-t-yoda> Hi all, Is it now policy with certain bugs, for the user to be asked to update their BIOS? It seems to happening a heck of a lot these days. With the inherent danger of BIOS updates and that Ubuntu (Linux for Human Beings) has users that are not that technically minded or would shy away from such an update - Should it being happening so often? Regards Phil -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part URL: From one.ukit at gmail.com Sat Aug 10 09:49:28 2013 From: one.ukit at gmail.com (Phil Wyett) Date: Sat, 10 Aug 2013 10:49:28 +0100 Subject: An invalidated bug. Should it have really been invalidated? Message-ID: <1376128168.6307.6.camel@u-k-i-t-yoda> Hi all, Could folks look at this bug and offer advise on why this bug was and should be invalidated? It was of at enough of an input level by users that I seem to feel it should not have been but maybe chased up more with relevant devs to try work it. Regards Phil -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part URL: From ubuntu at treblig.org Sat Aug 10 11:06:13 2013 From: ubuntu at treblig.org (Dr. David Alan Gilbert) Date: Sat, 10 Aug 2013 12:06:13 +0100 Subject: Bug Squad and a lot of asks to update BIOS In-Reply-To: <20130810105655.GA11808@gallifrey> References: <1376127493.6307.3.camel@u-k-i-t-yoda> <20130810105655.GA11808@gallifrey> Message-ID: <20130810110613.GB11808@gallifrey> * Phil Wyett (one.ukit at gmail.com) wrote: > Hi all, > > Is it now policy with certain bugs, for the user to be asked to update > their BIOS? It seems to happening a heck of a lot these days. With the > inherent danger of BIOS updates and that Ubuntu (Linux for Human Beings) > has users that are not that technically minded or would shy away from > such an update - Should it being happening so often? Yeh I've had a few of those - and I agree it's dangerous. There are bugs that might very well be fixed by a new BIOS, but it does need some careful consideration. Dave (Resent with right 'from') -- -----Open up your eyes, open up your mind, open up your code ------- / Dr. David Alan Gilbert | Running GNU/Linux | Happy \ \ gro.gilbert @ treblig.org | | In Hex / \ _________________________|_____ http://www.treblig.org |_______/ From stephen.webb at canonical.com Sat Aug 10 12:48:10 2013 From: stephen.webb at canonical.com (Stephen M. Webb) Date: Sat, 10 Aug 2013 08:48:10 -0400 Subject: An invalidated bug. Should it have really been invalidated? In-Reply-To: <1376128168.6307.6.camel@u-k-i-t-yoda> References: <1376128168.6307.6.camel@u-k-i-t-yoda> Message-ID: <5206368A.1060902@ubuntu.com> On 08/10/2013 05:49 AM, Phil Wyett wrote: > > Could folks look at this bug and offer advise on why this bug was and should be invalidated? It was of at enough of > an input level by users that I seem to feel it should not have been but maybe chased up more with relevant devs to > try work it. Er, which bug? -- Stephen M. Webb https://launchpad.net/~bregma From dave at treblig.org Sat Aug 10 10:56:55 2013 From: dave at treblig.org (Dr. David Alan Gilbert) Date: Sat, 10 Aug 2013 11:56:55 +0100 Subject: Bug Squad and a lot of asks to update BIOS In-Reply-To: <1376127493.6307.3.camel@u-k-i-t-yoda> References: <1376127493.6307.3.camel@u-k-i-t-yoda> Message-ID: <20130810105655.GA11808@gallifrey> * Phil Wyett (one.ukit at gmail.com) wrote: > Hi all, > > Is it now policy with certain bugs, for the user to be asked to update > their BIOS? It seems to happening a heck of a lot these days. With the > inherent danger of BIOS updates and that Ubuntu (Linux for Human Beings) > has users that are not that technically minded or would shy away from > such an update - Should it being happening so often? Yeh I've had a few of those - and I agree it's dangerous. There are bugs that might very well be fixed by a new BIOS, but it does need some careful consideration. Dave -- -----Open up your eyes, open up your mind, open up your code ------- / Dr. David Alan Gilbert | Running GNU/Linux | Happy \ \ gro.gilbert @ treblig.org | | In Hex / \ _________________________|_____ http://www.treblig.org |_______/ From one.ukit at gmail.com Sat Aug 10 15:16:40 2013 From: one.ukit at gmail.com (Phil Wyett) Date: Sat, 10 Aug 2013 16:16:40 +0100 Subject: An invalidated bug. Should it have really been invalidated? In-Reply-To: <5206368A.1060902@ubuntu.com> References: <1376128168.6307.6.camel@u-k-i-t-yoda> <5206368A.1060902@ubuntu.com> Message-ID: <1376147800.6307.10.camel@u-k-i-t-yoda> On Sat, 2013-08-10 at 08:48 -0400, Stephen M. Webb wrote: > On 08/10/2013 05:49 AM, Phil Wyett wrote: > > > > Could folks look at this bug and offer advise on why this bug was and should be invalidated? It was of at enough of > > an input level by users that I seem to feel it should not have been but maybe chased up more with relevant devs to > > try work it. > > Er, which bug? > > -- > Stephen M. Webb > https://launchpad.net/~bregma > The bug I am concerned about is #1172908 Regards Phil -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part URL: From flyingstar16 at gmail.com Sat Aug 10 16:31:43 2013 From: flyingstar16 at gmail.com (Claudio Moretti) Date: Sat, 10 Aug 2013 18:31:43 +0200 Subject: An invalidated bug. Should it have really been invalidated? In-Reply-To: <1376147800.6307.10.camel@u-k-i-t-yoda> References: <1376128168.6307.6.camel@u-k-i-t-yoda> <5206368A.1060902@ubuntu.com> <1376147800.6307.10.camel@u-k-i-t-yoda> Message-ID: On Sat, Aug 10, 2013 at 5:16 PM, Phil Wyett wrote: > The bug I am concerned about is #1172908 > I reopened it; in my opinion, it should have never been closed: if there's at least one person able to reproduce it, the bug is there. In this case, there are three. (Before that, though, I re-read the HowToReport[1] guide, just in case I was mistaken :P It doesn't seem that way to me, but please feel free to tell me if I was wrong!) Claudio [1] https://wiki.ubuntu.com/Bugs/HowToTriage#Confirming -------------- next part -------------- An HTML attachment was scrubbed... URL: From ubuntu at treblig.org Sat Aug 10 16:44:31 2013 From: ubuntu at treblig.org (Dr. David Alan Gilbert) Date: Sat, 10 Aug 2013 17:44:31 +0100 Subject: An invalidated bug. Should it have really been invalidated? In-Reply-To: References: <1376128168.6307.6.camel@u-k-i-t-yoda> <5206368A.1060902@ubuntu.com> <1376147800.6307.10.camel@u-k-i-t-yoda> Message-ID: <20130810164431.GC11808@gallifrey> * Claudio Moretti (flyingstar16 at gmail.com) wrote: > On Sat, Aug 10, 2013 at 5:16 PM, Phil Wyett wrote: > > > The bug I am concerned about is #1172908 > > > > I reopened it; in my opinion, it should have never been closed: if there's > at least one person able to reproduce it, the bug is there. In this case, > there are three. I agree, however it's a little tricky with Kernel bugs; the normal instructions there are not to merge bugs unless you're sure it's the same bug. In this case I would agree they're almost certainly the same problem (since the models are all the same). It does get a bit tricky when the original reporter gives up on it, but there are others affected. Dave -- -----Open up your eyes, open up your mind, open up your code ------- / Dr. David Alan Gilbert | Running GNU/Linux | Happy \ \ gro.gilbert @ treblig.org | | In Hex / \ _________________________|_____ http://www.treblig.org |_______/ From flyingstar16 at gmail.com Sat Aug 10 17:48:20 2013 From: flyingstar16 at gmail.com (Claudio Moretti) Date: Sat, 10 Aug 2013 19:48:20 +0200 Subject: An invalidated bug. Should it have really been invalidated? In-Reply-To: <20130810164431.GC11808@gallifrey> References: <1376128168.6307.6.camel@u-k-i-t-yoda> <5206368A.1060902@ubuntu.com> <1376147800.6307.10.camel@u-k-i-t-yoda> <20130810164431.GC11808@gallifrey> Message-ID: On Sat, Aug 10, 2013 at 6:44 PM, Dr. David Alan Gilbert wrote: > It does get a bit tricky when the original reporter gives up on it, > but there are others affected. > That's what comments are for, and the little "it affects me" flag, and the whole system: try to keep one report for one bug. I honestly don't understand why ~penalvch keeps invalidating it; it happened again, I reopened it again but maybe I was a little harsh. Can anyone else have a look at it, please? I need an external opinion... Claudio -------------- next part -------------- An HTML attachment was scrubbed... URL: From chrisjohnston at ubuntu.com Sat Aug 10 18:23:06 2013 From: chrisjohnston at ubuntu.com (Chris Johnston) Date: Sat, 10 Aug 2013 14:23:06 -0400 Subject: An invalidated bug. Should it have really been invalidated? In-Reply-To: References: <1376128168.6307.6.camel@u-k-i-t-yoda> <5206368A.1060902@ubuntu.com> <1376147800.6307.10.camel@u-k-i-t-yoda> <20130810164431.GC11808@gallifrey> Message-ID: I'm not going to comment on keeping the bug opened or closed, however I will point out: "Many Linux package, hardware, and other non-user space bugs are hardware dependent on both the hardware itself, and what other hardware the problematic hardware is connected to. The rule of thumb is *one report, per person, per hardware combination, per bug*. For more on this please see here, and further below in this article. As well, please do not post comments to another person's report, claiming you have the same problem, because you have the same hardware, or same computer model. Instead, please file a separate report, and make comments there. This is because no one can verify if you would have the same problem or not, because your hardware can not be analyzed. " https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette cJ On Sat, Aug 10, 2013 at 1:48 PM, Claudio Moretti wrote: > On Sat, Aug 10, 2013 at 6:44 PM, Dr. David Alan Gilbert < > ubuntu at treblig.org> wrote: > >> It does get a bit tricky when the original reporter gives up on it, >> but there are others affected. >> > > That's what comments are for, and the little "it affects me" flag, and the > whole system: try to keep one report for one bug. > > I honestly don't understand why ~penalvch keeps invalidating it; it > happened again, I reopened it again but maybe I was a little harsh. > > Can anyone else have a look at it, please? I need an external opinion... > > Claudio > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > -- Chris Johnston > QA Engineer - Canonical Ltd. www.ubuntu.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From hggdh2 at ubuntu.com Sat Aug 10 18:26:54 2013 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Sat, 10 Aug 2013 13:26:54 -0500 Subject: spam being received? Message-ID: <20130810132654.2c33da08@xango3> Hi, Today, on the #ubuntu-bugs, we were told that emailers to the list are receiving unsolicited spam back when they send in an email. I would like to know if others have noticed that. If so, please *ME* (not the list) one such full email, headers included. Cheers, ..C.. -- ab alio expectes alteri quod feceris From ubuntu at treblig.org Sat Aug 10 19:32:21 2013 From: ubuntu at treblig.org (Dr. David Alan Gilbert) Date: Sat, 10 Aug 2013 20:32:21 +0100 Subject: An invalidated bug. Should it have really been invalidated? In-Reply-To: References: <1376128168.6307.6.camel@u-k-i-t-yoda> <5206368A.1060902@ubuntu.com> <1376147800.6307.10.camel@u-k-i-t-yoda> <20130810164431.GC11808@gallifrey> Message-ID: <20130810193221.GG11808@gallifrey> * Chris Johnston (chrisjohnston at ubuntu.com) wrote: > I'm not going to comment on keeping the bug opened or closed, however I > will point out: > > "Many Linux package, hardware, > and other non-user space bugs are hardware dependent on both the hardware > itself, and what other hardware the problematic hardware is connected to. > The rule of thumb is *one report, per person, per hardware combination, per > bug*. For more on this please see > here, > and further below in this article. As well, please do not post comments to > another person's report, claiming you have the same problem, because you > have the same hardware, or same computer model. Instead, please file a > separate report, and make comments there. This is because no one can verify > if you would have the same problem or not, because your hardware can not be > analyzed. " Right, the challenge is how to group them though - if you think 20 bugs are actually the same bug: * how do we recognise that? - because it is useful to group when you think you've found the same thing * how do we keep hold of all the debug if the original reporter gives up and moves on? - we do see streams of bugs where one person finds it, gives up and the bug expires, then someone else finds it 6 months later and the same bug persists for years. The challenge with kernel bugs though is finding the point at which you say it's actually the same problem, and it can be really tricky which is I think why those guidelines are there; you don't want to start grouping stuff together just because it has similar symptoms though unless it's specific enough to be reasonably sure. The other thing I sometimes do is ask people to put another bug report in, but to add a comment on the original giving the number of their new report as a minimal sort of linking. Dave -- -----Open up your eyes, open up your mind, open up your code ------- / Dr. David Alan Gilbert | Running GNU/Linux | Happy \ \ gro.gilbert @ treblig.org | | In Hex / \ _________________________|_____ http://www.treblig.org |_______/ From flyingstar16 at gmail.com Sat Aug 10 23:18:55 2013 From: flyingstar16 at gmail.com (Claudio Moretti) Date: Sun, 11 Aug 2013 01:18:55 +0200 Subject: An invalidated bug. Should it have really been invalidated? In-Reply-To: <20130810193221.GG11808@gallifrey> References: <1376128168.6307.6.camel@u-k-i-t-yoda> <5206368A.1060902@ubuntu.com> <1376147800.6307.10.camel@u-k-i-t-yoda> <20130810164431.GC11808@gallifrey> <20130810193221.GG11808@gallifrey> Message-ID: Got it; I was wrong, and I apologize. Thanks for the answers, both of you! :) Cheers, Claudio -------------- next part -------------- An HTML attachment was scrubbed... URL: From one.ukit at gmail.com Sun Aug 11 05:13:09 2013 From: one.ukit at gmail.com (Phil Wyett) Date: Sun, 11 Aug 2013 06:13:09 +0100 Subject: An invalidated bug. Should it have really been invalidated? In-Reply-To: References: <1376128168.6307.6.camel@u-k-i-t-yoda> <5206368A.1060902@ubuntu.com> <1376147800.6307.10.camel@u-k-i-t-yoda> <20130810164431.GC11808@gallifrey> Message-ID: <1376197989.4259.12.camel@u-k-i-t-yoda> On Sat, 2013-08-10 at 14:23 -0400, Chris Johnston wrote: > I'm not going to comment on keeping the bug opened or closed, however > I will point out: > "Many Linux package, hardware, and other non-user space bugs are > hardware dependent on both the hardware itself, and what other > hardware the problematic hardware is connected to. The rule of thumb > is one report, per person, per hardware combination, per bug. For more > on this please see here, and further below in this article. As well, > please do not post comments to another person's report, claiming you > have the same problem, because you have the same hardware, or same > computer model. Instead, please file a separate report, and make > comments there. This is because no one can verify if you would have > the same problem or not, because your hardware can not be analyzed. " > https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette > Hi, I have read the whole document now after not reading it for a few years. It seems many changes and caveats have been introduced and now we have many flaws in the whole bug reporting process. What should be a simple process for new/inexperienced users (not me as a dev), has actually turned into a spiders web of iffy software and processes to perform the overall task with the addition of many 'do nots' introduced by contributors. Is there anyway the bug squad can hold a review in conjunction with the quality people and look at the whole process once more? As one example to why. If the whole notion of one bug per person per hardware combo and no posting to others reports is the way to go. We should really be using the duplication method on launchpad and the " This bug affects 'x' people. Does this bug affect you? Edit" with this affecting bug heat is essentially redundant. Regards Phil -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part URL: From one.ukit at gmail.com Sun Aug 11 05:37:10 2013 From: one.ukit at gmail.com (Phil Wyett) Date: Sun, 11 Aug 2013 06:37:10 +0100 Subject: Bug Squad and a lot of asks to update BIOS In-Reply-To: <20130810105655.GA11808@gallifrey> References: <1376127493.6307.3.camel@u-k-i-t-yoda> <20130810105655.GA11808@gallifrey> Message-ID: <1376199430.5257.6.camel@u-k-i-t-yoda> On Sat, 2013-08-10 at 11:56 +0100, Dr. David Alan Gilbert wrote: > * Phil Wyett (one.ukit at gmail.com) wrote: > > Hi all, > > > > Is it now policy with certain bugs, for the user to be asked to update > > their BIOS? It seems to happening a heck of a lot these days. With the > > inherent danger of BIOS updates and that Ubuntu (Linux for Human Beings) > > has users that are not that technically minded or would shy away from > > such an update - Should it being happening so often? > > Yeh I've had a few of those - and I agree it's dangerous. > There are bugs that might very well be fixed by a new BIOS, > but it does need some careful consideration. > > Dave > Dangerous I agree and often a point of fear with users. It would be nice if people doing this on bug reports could add a note. "Please do not feel pressured or required to perform the suggested BIOS update yourself if you are not comfortable with doing so. You may wish to consult a local I.T. professional, who can advise and possibly perform such an update for you in exchange for a fee." Or something like that... :-) Regards Phil -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part URL: From hggdh2 at ubuntu.com Sun Aug 11 19:06:05 2013 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Sun, 11 Aug 2013 14:06:05 -0500 Subject: An invalidated bug. Should it have really been invalidated? In-Reply-To: <1376197989.4259.12.camel@u-k-i-t-yoda> References: <1376128168.6307.6.camel@u-k-i-t-yoda> <5206368A.1060902@ubuntu.com> <1376147800.6307.10.camel@u-k-i-t-yoda> <20130810164431.GC11808@gallifrey> <1376197989.4259.12.camel@u-k-i-t-yoda> Message-ID: <20130811140605.6400e905@xango3> On Sun, 11 Aug 2013 06:13:09 +0100 Phil Wyett wrote: > I have read the whole document now after not reading it for a few > years. It seems many changes and caveats have been introduced and now > we have many flaws in the whole bug reporting process. What should be > a simple process for new/inexperienced users (not me as a dev), has > actually turned into a spiders web of iffy software and processes to > perform the overall task with the addition of many 'do nots' > introduced by contributors. Well. Let's keep in mind that bug reports are *technical* reports. On commercial systems, an end-user opens an incident, help-desk/L1-support looks at it and then -- if needed -- upgrades the incident to a bug (and involves L2/L3, as needed). (my personal view is that end-users [1] should never directly open a bug.) For any of us working with the developer/maintainer hat, it is a waste of time to look at conflated/confused/incomplete/incoherent LP bugs. We end up spending a LOT more time on one single "bug"... and this causes a series of other (perhaps better-written, perhaps more critical) bugs to be left aside. So, yes, bugs processes have gotten more complex. But this is not an unneeded complexity, I hope (of course, as time goes by chaos creeps in, and we should review the processes every so often). The crux here, to my understanding, is that end-users -- to say, non-expert, casual, users -- should NOT open a bug by hand. (for example, there is one LP user that insists in manually opening his/her bugs, always against 'Ubuntu'. I gave up asking to use 'ubuntu-bug', and I now leave all his/her new bugs aside. Also, most of her/his bugs are actually user issues, not package/code bugs.) Specifically for hardware-related bugs, the rules of thumb are: if you are not a developer/expert, (1) open a new bug; (2) use 'ubuntu-bug' to open the bug; (3) at most add a link to the existing bug you think may be related; (4) do NOT comment on other bugs. > > Is there anyway the bug squad can hold a review in conjunction with > the quality people and look at the whole process once more? As one > example to why. If the whole notion of one bug per person per > hardware combo and no posting to others reports is the way to go. We > should really be using the duplication method on launchpad and the " > This bug affects 'x' people. Does this bug affect you? Edit" with > this affecting bug heat is essentially redundant. We really should review the whole triage process every so often; if any of us think there is room for improvement, then, by all means, propose/justify it. This is a *group* process. And, by that, I also mean that my opinion is just that -- an opinion. The objective is to better triage bugs, not to cater to inflated opinions of anybody, myself included. Thank you for starting the process :-) ..C.. [1] by "end-users" I am refering to any and all non-subject-expert users. -- ab alio expectes alteri quod feceris From ubuntu at treblig.org Sun Aug 11 19:28:09 2013 From: ubuntu at treblig.org (Dr. David Alan Gilbert) Date: Sun, 11 Aug 2013 20:28:09 +0100 Subject: An invalidated bug. Should it have really been invalidated? In-Reply-To: <20130811140605.6400e905@xango3> References: <1376128168.6307.6.camel@u-k-i-t-yoda> <5206368A.1060902@ubuntu.com> <1376147800.6307.10.camel@u-k-i-t-yoda> <20130810164431.GC11808@gallifrey> <1376197989.4259.12.camel@u-k-i-t-yoda> <20130811140605.6400e905@xango3> Message-ID: <20130811192809.GC21050@gallifrey> * C de-Avillez (hggdh2 at ubuntu.com) wrote: > On Sun, 11 Aug 2013 06:13:09 +0100 > Phil Wyett wrote: > > > I have read the whole document now after not reading it for a few > > years. It seems many changes and caveats have been introduced and now > > we have many flaws in the whole bug reporting process. What should be > > a simple process for new/inexperienced users (not me as a dev), has > > actually turned into a spiders web of iffy software and processes to > > perform the overall task with the addition of many 'do nots' > > introduced by contributors. > > Well. Let's keep in mind that bug reports are *technical* reports. On > commercial systems, an end-user opens an incident, help-desk/L1-support > looks at it and then -- if needed -- upgrades the incident to a bug > (and involves L2/L3, as needed). > > (my personal view is that end-users [1] should never directly open a > bug.) Well, ok, but we don't have a separate 'bug' and 'incident' system; we've just got one; and I think I agree that's the real problem. > So, yes, bugs processes have gotten more complex. But this is not an > unneeded complexity, I hope (of course, as time goes by chaos creeps > in, and we should review the processes every so often). > > The crux here, to my understanding, is that end-users -- to say, > non-expert, casual, users -- should NOT open a bug by hand. Woah hang on, that's a separate problem - we're not talking about bugs without suitable info are we? I thought this was from a discussion about where the original reporter had given up. > (for example, there is one LP user that insists in manually opening > his/her bugs, always against 'Ubuntu'. I gave up asking to use > 'ubuntu-bug', and I now leave all his/her new bugs aside. Also, most of > her/his bugs are actually user issues, not package/code bugs.) > > Specifically for hardware-related bugs, the rules of thumb are: if you > are not a developer/expert, (1) open a new bug; (2) use > 'ubuntu-bug' to open the bug; (3) at most add a link to the existing > bug you think may be related; (4) do NOT comment on other bugs. Why (4)? The fact is the devs aren't getting around to diagnosing the contents of most of the bugs, especially hardware bugs, so it makes sense for end users to help to try and find where they have other people suffering from the same problem, and it often works well. I think the problem here is that we don't have a defined mechanism at the moment for anyone, including bugsquad/control/devs to create a way to actually say these bugs are all the same thing, and that makes sense when the original reporter walks away. Spotting the patterns in related bugs is critical, it's where we have chances to fix lots of things at once and spot really important breakages. Dave -- -----Open up your eyes, open up your mind, open up your code ------- / Dr. David Alan Gilbert | Running GNU/Linux | Happy \ \ gro.gilbert @ treblig.org | | In Hex / \ _________________________|_____ http://www.treblig.org |_______/ From brian at ubuntu.com Mon Aug 12 18:51:35 2013 From: brian at ubuntu.com (Brian Murray) Date: Mon, 12 Aug 2013 11:51:35 -0700 Subject: Bug Squad and a lot of asks to update BIOS In-Reply-To: <1376199430.5257.6.camel@u-k-i-t-yoda> References: <1376127493.6307.3.camel@u-k-i-t-yoda> <20130810105655.GA11808@gallifrey> <1376199430.5257.6.camel@u-k-i-t-yoda> Message-ID: <20130812185135.GZ2917@murraytwins.com> On Sun, Aug 11, 2013 at 06:37:10AM +0100, Phil Wyett wrote: > On Sat, 2013-08-10 at 11:56 +0100, Dr. David Alan Gilbert wrote: > > * Phil Wyett (one.ukit at gmail.com) wrote: > > > Hi all, > > > > > > Is it now policy with certain bugs, for the user to be asked to update > > > their BIOS? It seems to happening a heck of a lot these days. With the > > > inherent danger of BIOS updates and that Ubuntu (Linux for Human Beings) > > > has users that are not that technically minded or would shy away from > > > such an update - Should it being happening so often? > > > > Yeh I've had a few of those - and I agree it's dangerous. > > There are bugs that might very well be fixed by a new BIOS, > > but it does need some careful consideration. > > > > Dave > > > > Dangerous I agree and often a point of fear with users. It would be nice > if people doing this on bug reports could add a note. > > "Please do not feel pressured or required to perform the suggested BIOS > update yourself if you are not comfortable with doing so. You may wish > to consult a local I.T. professional, who can advise and possibly > perform such an update for you in exchange for a fee." > > Or something like that... :-) That sounds like a good suggestion to me, what packages / bugs have seen the comments to update your BIOS on? Thanks! -- Brian Murray From brian at ubuntu.com Mon Aug 12 19:03:28 2013 From: brian at ubuntu.com (Brian Murray) Date: Mon, 12 Aug 2013 12:03:28 -0700 Subject: An invalidated bug. Should it have really been invalidated? In-Reply-To: <20130810164431.GC11808@gallifrey> References: <1376128168.6307.6.camel@u-k-i-t-yoda> <5206368A.1060902@ubuntu.com> <1376147800.6307.10.camel@u-k-i-t-yoda> <20130810164431.GC11808@gallifrey> Message-ID: <20130812190327.GA2917@murraytwins.com> On Sat, Aug 10, 2013 at 05:44:31PM +0100, Dr. David Alan Gilbert wrote: > * Claudio Moretti (flyingstar16 at gmail.com) wrote: > > On Sat, Aug 10, 2013 at 5:16 PM, Phil Wyett wrote: > > > > > The bug I am concerned about is #1172908 > > > > > > > I reopened it; in my opinion, it should have never been closed: if there's > > at least one person able to reproduce it, the bug is there. In this case, > > there are three. > > I agree, however it's a little tricky with Kernel bugs; the normal > instructions there are not to merge bugs unless you're sure it's the same > bug. > In this case I would agree they're almost certainly the same problem > (since the models are all the same). I didn't read all the comments in the bug report, but how can we be certain that they are all the same models? I'm under the impression that internal components of systems change even though they may all be called the same name. Subsequently, I understand why the kernel team wants individual bug reports (with hardware information gathered) from each user. -- Brian Murray From brian at ubuntu.com Mon Aug 12 19:07:30 2013 From: brian at ubuntu.com (Brian Murray) Date: Mon, 12 Aug 2013 12:07:30 -0700 Subject: An invalidated bug. Should it have really been invalidated? In-Reply-To: <20130810193221.GG11808@gallifrey> References: <1376128168.6307.6.camel@u-k-i-t-yoda> <5206368A.1060902@ubuntu.com> <1376147800.6307.10.camel@u-k-i-t-yoda> <20130810164431.GC11808@gallifrey> <20130810193221.GG11808@gallifrey> Message-ID: <20130812190730.GB2917@murraytwins.com> On Sat, Aug 10, 2013 at 08:32:21PM +0100, Dr. David Alan Gilbert wrote: > * Chris Johnston (chrisjohnston at ubuntu.com) wrote: > > I'm not going to comment on keeping the bug opened or closed, however I > > will point out: > > > > "Many Linux package, hardware, > > and other non-user space bugs are hardware dependent on both the hardware > > itself, and what other hardware the problematic hardware is connected to. > > The rule of thumb is *one report, per person, per hardware combination, per > > bug*. For more on this please see > > here, > > and further below in this article. As well, please do not post comments to > > another person's report, claiming you have the same problem, because you > > have the same hardware, or same computer model. Instead, please file a > > separate report, and make comments there. This is because no one can verify > > if you would have the same problem or not, because your hardware can not be > > analyzed. " > > Right, the challenge is how to group them though - if you think 20 bugs > are actually the same bug: > * how do we recognise that? > - because it is useful to group when you think you've found the same > thing > * how do we keep hold of all the debug if the original reporter gives > up and moves on? > - we do see streams of bugs where one person finds it, gives up > and the bug expires, then someone else finds it 6 months later > and the same bug persists for years. > > The challenge with kernel bugs though is finding the point at which > you say it's actually the same problem, and it can be really tricky which > is I think why those guidelines are there; you don't want to start grouping > stuff together just because it has similar symptoms though unless > it's specific enough to be reasonably sure. > > The other thing I sometimes do is ask people to put another bug report > in, but to add a comment on the original giving the number of their > new report as a minimal sort of linking. This is a great best practice as it makes it easier to find bugs possibly related to the one a developer is fixing. Just a simple comment like "I reported bug 1234 which I think is related to this one as I have similar hardware" can be a huge help. -- Brian Murray From brian at ubuntu.com Mon Aug 12 19:13:07 2013 From: brian at ubuntu.com (Brian Murray) Date: Mon, 12 Aug 2013 12:13:07 -0700 Subject: An invalidated bug. Should it have really been invalidated? In-Reply-To: <1376197989.4259.12.camel@u-k-i-t-yoda> References: <1376128168.6307.6.camel@u-k-i-t-yoda> <5206368A.1060902@ubuntu.com> <1376147800.6307.10.camel@u-k-i-t-yoda> <20130810164431.GC11808@gallifrey> <1376197989.4259.12.camel@u-k-i-t-yoda> Message-ID: <20130812191306.GC2917@murraytwins.com> On Sun, Aug 11, 2013 at 06:13:09AM +0100, Phil Wyett wrote: > On Sat, 2013-08-10 at 14:23 -0400, Chris Johnston wrote: > > I'm not going to comment on keeping the bug opened or closed, however > > I will point out: > > > "Many Linux package, hardware, and other non-user space bugs are > > hardware dependent on both the hardware itself, and what other > > hardware the problematic hardware is connected to. The rule of thumb > > is one report, per person, per hardware combination, per bug. For more > > on this please see here, and further below in this article. As well, > > please do not post comments to another person's report, claiming you > > have the same problem, because you have the same hardware, or same > > computer model. Instead, please file a separate report, and make > > comments there. This is because no one can verify if you would have > > the same problem or not, because your hardware can not be analyzed. " > > > https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette > > > > Hi, > > I have read the whole document now after not reading it for a few years. > It seems many changes and caveats have been introduced and now we have > many flaws in the whole bug reporting process. What should be a simple > process for new/inexperienced users (not me as a dev), has actually > turned into a spiders web of iffy software and processes to perform the > overall task with the addition of many 'do nots' introduced by > contributors. > > Is there anyway the bug squad can hold a review in conjunction with the > quality people and look at the whole process once more? As one example > to why. If the whole notion of one bug per person per hardware combo and > no posting to others reports is the way to go. We should really be using > the duplication method on launchpad and the " This bug affects 'x' > people. Does this bug affect you? Edit" with this affecting bug heat is > essentially redundant. Could you elaborate on what you mean by the last two sentences here? Keep in mind there is a distinction between packages which are generally hardware specific (the kernel, X packages) and those that are generally not like update-manager and Ubuntu Software Center. -- Brian Murray Ubuntu Bug Master From jack at troop55.net Tue Aug 13 16:25:53 2013 From: jack at troop55.net (Jack Ramsay) Date: Tue, 13 Aug 2013 11:25:53 -0500 Subject: Bug reporter Message-ID: I just proposed a blue print for a better bug reporter as I got tired of the people not knowing what they're doing and manually reporting bugs as it got annoying we just have to wait to get it approved -- Thanks, Jack -------------- next part -------------- An HTML attachment was scrubbed... URL: From ubuntu at treblig.org Tue Aug 13 23:05:08 2013 From: ubuntu at treblig.org (Dr. David Alan Gilbert) Date: Wed, 14 Aug 2013 00:05:08 +0100 Subject: An invalidated bug. Should it have really been invalidated? In-Reply-To: <20130812190327.GA2917@murraytwins.com> References: <1376128168.6307.6.camel@u-k-i-t-yoda> <5206368A.1060902@ubuntu.com> <1376147800.6307.10.camel@u-k-i-t-yoda> <20130810164431.GC11808@gallifrey> <20130812190327.GA2917@murraytwins.com> Message-ID: <20130813230508.GB2916@gallifrey> * Brian Murray (brian at ubuntu.com) wrote: > On Sat, Aug 10, 2013 at 05:44:31PM +0100, Dr. David Alan Gilbert wrote: > > * Claudio Moretti (flyingstar16 at gmail.com) wrote: > > > On Sat, Aug 10, 2013 at 5:16 PM, Phil Wyett wrote: > > > > > > > The bug I am concerned about is #1172908 > > > > > > > > > > I reopened it; in my opinion, it should have never been closed: if there's > > > at least one person able to reproduce it, the bug is there. In this case, > > > there are three. > > > > I agree, however it's a little tricky with Kernel bugs; the normal > > instructions there are not to merge bugs unless you're sure it's the same > > bug. > > In this case I would agree they're almost certainly the same problem > > (since the models are all the same). > > I didn't read all the comments in the bug report, but how can we be > certain that they are all the same models? I'm under the impression > that internal components of systems change even though they may all be > called the same name. Subsequently, I understand why the kernel team > wants individual bug reports (with hardware information gathered) from > each user. I'm ok with requiring individual bugs from individual users but we've got to be able to do something when we find a bug that feels like it's specific and affects a certain range of machines. Can we be 'certain' no, but given that: - It's a specific well defined problem (Only the USB2 ports are failing not the USB3). - We're not seeing this on loads of different systems - But we are seeing it on a group of similar models - It's not a fluffy sometimes-happens bug. Now some of those are a judgement call rather than a hard and fast rule, but that's why we're not entirely scripted! Then I say we have a common bug here and we need some way to represent it. If the way isn't allowing multiple users to put their info on one report then we need a metabug or something, we also need a way to keep hold of it if any one of the original reporters gives up. Dave -- -----Open up your eyes, open up your mind, open up your code ------- / Dr. David Alan Gilbert | Running GNU/Linux | Happy \ \ gro.gilbert @ treblig.org | | In Hex / \ _________________________|_____ http://www.treblig.org |_______/ From hggdh2 at ubuntu.com Wed Aug 14 00:34:36 2013 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Tue, 13 Aug 2013 19:34:36 -0500 Subject: An invalidated bug. Should it have really been invalidated? In-Reply-To: <20130813230508.GB2916@gallifrey> References: <1376128168.6307.6.camel@u-k-i-t-yoda> <5206368A.1060902@ubuntu.com> <1376147800.6307.10.camel@u-k-i-t-yoda> <20130810164431.GC11808@gallifrey> <20130812190327.GA2917@murraytwins.com> <20130813230508.GB2916@gallifrey> Message-ID: <20130813193436.16180dcb@xango3> On Wed, 14 Aug 2013 00:05:08 +0100 "Dr. David Alan Gilbert" wrote: > * Brian Murray (brian at ubuntu.com) wrote: > > On Sat, Aug 10, 2013 at 05:44:31PM +0100, Dr. David Alan Gilbert > > wrote: > > > * Claudio Moretti (flyingstar16 at gmail.com) wrote: > > > > On Sat, Aug 10, 2013 at 5:16 PM, Phil Wyett > > > > wrote: > > > > > > > > > The bug I am concerned about is #1172908 > > > > > > > > > > > > > I reopened it; in my opinion, it should have never been closed: > > > > if there's at least one person able to reproduce it, the bug is > > > > there. In this case, there are three. > > > > > > I agree, however it's a little tricky with Kernel bugs; the normal > > > instructions there are not to merge bugs unless you're sure it's > > > the same bug. > > > In this case I would agree they're almost certainly the same > > > problem (since the models are all the same). > > > > I didn't read all the comments in the bug report, but how can we be > > certain that they are all the same models? I'm under the impression > > that internal components of systems change even though they may all > > be called the same name. Subsequently, I understand why the kernel > > team wants individual bug reports (with hardware information > > gathered) from each user. > > I'm ok with requiring individual bugs from individual users > but we've got to be able to do something when we find a bug > that feels like it's specific and affects a certain range of machines. > Can we be 'certain' no, but given that: > > - It's a specific well defined problem (Only the USB2 ports are > failing not the USB3). > - We're not seeing this on loads of different systems > - But we are seeing it on a group of similar models > - It's not a fluffy sometimes-happens bug. > > Now some of those are a judgement call rather than a hard > and fast rule, but that's why we're not entirely scripted! > > Then I say we have a common bug here and we need some way to represent > it. If the way isn't allowing multiple users to put their info > on one report then we need a metabug or something, we also > need a way to keep hold of it if any one of the original reporters > gives up. I agree, and I think all would agree as well. This is where I stated, in another subthread, that have a procedure to identify "collisions" would be nice, the more automated, the better. It could very well be a back-office process, giving as output a series of bugs that match hardware (and then would be analysed by humans). For *kernel* bugs, this would be simplified due to the automagic collection of bug data (with same-named-attachments). But it is still a bit complex since we do not have basic problem data as well-formed attributes. This means, potentially, a hell of a problem on parsing -- say -- bug titles for clues. Metadata, perhaps added to the description, might help; for example, a series of key=value fields. But this would make, if the reporter is expected to fill them in, bug reporting by casual users even more complex. (Which, of course, goes nicely with my previous comment that bugs are *technical* thingies.) One of the problems with "no mixing of affected users" on kernel (and other hardware-related) bugs is that the sheer amount of unique bugs cause many of them to die of old age. Recently, I myself received a series of emails asking for more data/try new kernel/update BIOS, for systems I do not have access to anymore, and for UBuntu versions already obsoleted. These were interesting bugs when they were opened, but now are on the track to be closed invalid. In other words: I fully agree with Dave; at the same time I do understand the kernel's requirement for one bug per user. Dave's approach might help, at least a bit, minimise age/relevance issues. Let's keep on, I like the suggestions :-) ..C.. -- ab alio expectes alteri quod feceris From hggdh2 at ubuntu.com Wed Aug 14 00:36:23 2013 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Tue, 13 Aug 2013 19:36:23 -0500 Subject: Bug reporter In-Reply-To: References: Message-ID: <20130813193623.63b432cf@xango3> On Tue, 13 Aug 2013 11:25:53 -0500 Jack Ramsay wrote: > I just proposed a blue print for a better bug reporter as I got tired > of the people not knowing what they're doing and manually reporting > bugs as it got annoying we just have to wait to get it approved > > > Where did you propose it? -- ab alio expectes alteri quod feceris From nicholas.skaggs at canonical.com Fri Aug 16 20:51:34 2013 From: nicholas.skaggs at canonical.com (Nicholas Skaggs) Date: Fri, 16 Aug 2013 16:51:34 -0400 Subject: Quality vUDS Sessions Message-ID: <520E90D6.4080900@canonical.com> Thus far I've created the following sessions for vUDS which is occurring August 27-29th: https://blueprints.launchpad.net/ubuntu/+spec/community-1308-quality-reporting-bugs https://blueprints.launchpad.net/ubuntu/+spec/appdev-1308-quality-testing-sdk https://blueprints.launchpad.net/ubuntu/+spec/community-1308-quality-flavors Please have a look and register to attend and participate. If you have an idea for a quality session or comments, please speak up now :-) Look forward to seeing everyone in the sessions! Nicholas -------------- next part -------------- An HTML attachment was scrubbed... URL: From cucarracha at tiscali.it Sat Aug 17 11:45:49 2013 From: cucarracha at tiscali.it (Me) Date: Sat, 17 Aug 2013 13:45:49 +0200 Subject: Quality vUDS Sessions In-Reply-To: <520E90D6.4080900@canonical.com> References: <520E90D6.4080900@canonical.com> Message-ID: <1376739949.4463.31.camel@Saxy> Hallo to everybody. I've noted the impair situation about UbuntuKylin in front of Ubuntu. It is not a flavour of Ubuntu, is Ubuntu for the Chinese people, so we can see the lacks of the testcases adopted for LVM and others. How we as Quality group can manage this situation for the Chinese people that cannot use an english tracker ? Have them their reserved Chinese channels ? Canonical and Chinese government starts this project, so we have to put some more effort to better raise this problem coordinating also with the UbuntuKylin teams. My best wishes to all of you. Fabio -------------- next part -------------- An HTML attachment was scrubbed... URL: From one.ukit at gmail.com Mon Aug 19 04:41:28 2013 From: one.ukit at gmail.com (Phil Wyett) Date: Mon, 19 Aug 2013 05:41:28 +0100 Subject: Bug Squad and a lot of asks to update BIOS In-Reply-To: <20130812185135.GZ2917@murraytwins.com> References: <1376127493.6307.3.camel@u-k-i-t-yoda> <20130810105655.GA11808@gallifrey> <1376199430.5257.6.camel@u-k-i-t-yoda> <20130812185135.GZ2917@murraytwins.com> Message-ID: <1376887288.5343.3.camel@u-k-i-t-yoda> On Mon, 2013-08-12 at 11:51 -0700, Brian Murray wrote: > On Sun, Aug 11, 2013 at 06:37:10AM +0100, Phil Wyett wrote: > > On Sat, 2013-08-10 at 11:56 +0100, Dr. David Alan Gilbert wrote: > > > * Phil Wyett (one.ukit at gmail.com) wrote: > > > > Hi all, > > > > > > > > Is it now policy with certain bugs, for the user to be asked to update > > > > their BIOS? It seems to happening a heck of a lot these days. With the > > > > inherent danger of BIOS updates and that Ubuntu (Linux for Human Beings) > > > > has users that are not that technically minded or would shy away from > > > > such an update - Should it being happening so often? > > > > > > Yeh I've had a few of those - and I agree it's dangerous. > > > There are bugs that might very well be fixed by a new BIOS, > > > but it does need some careful consideration. > > > > > > Dave > > > > > > > Dangerous I agree and often a point of fear with users. It would be nice > > if people doing this on bug reports could add a note. > > > > "Please do not feel pressured or required to perform the suggested BIOS > > update yourself if you are not comfortable with doing so. You may wish > > to consult a local I.T. professional, who can advise and possibly > > perform such an update for you in exchange for a fee." > > > > Or something like that... :-) > > That sounds like a good suggestion to me, what packages / bugs have seen > the comments to update your BIOS on? > > Thanks! > -- > Brian Murray There are so many instances it would be hard to name 1. My email for the 'ubuntu-bugs' list goes back to 2013-07-28 and there are > 300 instances of BIOS update requests to users if I do a search for the string "update is available for your BIOS". Regards Phil -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part URL: From one.ukit at gmail.com Mon Aug 19 04:44:18 2013 From: one.ukit at gmail.com (Phil Wyett) Date: Mon, 19 Aug 2013 05:44:18 +0100 Subject: An invalidated bug. Should it have really been invalidated? In-Reply-To: <20130812191306.GC2917@murraytwins.com> References: <1376128168.6307.6.camel@u-k-i-t-yoda> <5206368A.1060902@ubuntu.com> <1376147800.6307.10.camel@u-k-i-t-yoda> <20130810164431.GC11808@gallifrey> <1376197989.4259.12.camel@u-k-i-t-yoda> <20130812191306.GC2917@murraytwins.com> Message-ID: <1376887458.5343.5.camel@u-k-i-t-yoda> On Mon, 2013-08-12 at 12:13 -0700, Brian Murray wrote: > On Sun, Aug 11, 2013 at 06:13:09AM +0100, Phil Wyett wrote: > > On Sat, 2013-08-10 at 14:23 -0400, Chris Johnston wrote: > > > I'm not going to comment on keeping the bug opened or closed, however > > > I will point out: > > > > > "Many Linux package, hardware, and other non-user space bugs are > > > hardware dependent on both the hardware itself, and what other > > > hardware the problematic hardware is connected to. The rule of thumb > > > is one report, per person, per hardware combination, per bug. For more > > > on this please see here, and further below in this article. As well, > > > please do not post comments to another person's report, claiming you > > > have the same problem, because you have the same hardware, or same > > > computer model. Instead, please file a separate report, and make > > > comments there. This is because no one can verify if you would have > > > the same problem or not, because your hardware can not be analyzed. " > > > > > https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette > > > > > > > Hi, > > > > I have read the whole document now after not reading it for a few years. > > It seems many changes and caveats have been introduced and now we have > > many flaws in the whole bug reporting process. What should be a simple > > process for new/inexperienced users (not me as a dev), has actually > > turned into a spiders web of iffy software and processes to perform the > > overall task with the addition of many 'do nots' introduced by > > contributors. > > > > Is there anyway the bug squad can hold a review in conjunction with the > > quality people and look at the whole process once more? As one example > > to why. If the whole notion of one bug per person per hardware combo and > > no posting to others reports is the way to go. We should really be using > > the duplication method on launchpad and the " This bug affects 'x' > > people. Does this bug affect you? Edit" with this affecting bug heat is > > essentially redundant. > > Could you elaborate on what you mean by the last two sentences here? > > Keep in mind there is a distinction between packages which are generally > hardware specific (the kernel, X packages) and those that are generally > not like update-manager and Ubuntu Software Center. > > -- > Brian Murray > Ubuntu Bug Master > I am looking at the flow of launchpad for bugs at the moment. I will hopefully be able to better explain and offer opinion soon. Regards Phil -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part URL: From tschu_lo at bluewin.ch Mon Aug 19 12:03:13 2013 From: tschu_lo at bluewin.ch (Lothar Tschuor) Date: Mon, 19 Aug 2013 12:03:13 -0000 Subject: Ubuntu-bugsquad Digest, Vol 86, Issue 12 In-Reply-To: References: Message-ID: <507C7A15.60409@bluewin.ch> Am 19.08.2013 14:00, schrieb ubuntu-bugsquad-request at lists.ubuntu.com: > Send Ubuntu-bugsquad mailing list submissions to > ubuntu-bugsquad at lists.ubuntu.com > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > or, via email, send a message with subject or body 'help' to > ubuntu-bugsquad-request at lists.ubuntu.com > > You can reach the person managing the list at > ubuntu-bugsquad-owner at lists.ubuntu.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Ubuntu-bugsquad digest..." > > > Today's Topics: > > 1. Re: Bug Squad and a lot of asks to update BIOS (Phil Wyett) > 2. Re: An invalidated bug. Should it have really been > invalidated? (Phil Wyett) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 19 Aug 2013 05:41:28 +0100 > From: Phil Wyett > To: "ubuntu-bugsquad at lists.ubuntu.com" > > Subject: Re: Bug Squad and a lot of asks to update BIOS > Message-ID: <1376887288.5343.3.camel at u-k-i-t-yoda> > Content-Type: text/plain; charset="utf-8" > > On Mon, 2013-08-12 at 11:51 -0700, Brian Murray wrote: >> On Sun, Aug 11, 2013 at 06:37:10AM +0100, Phil Wyett wrote: >>> On Sat, 2013-08-10 at 11:56 +0100, Dr. David Alan Gilbert wrote: >>>> * Phil Wyett (one.ukit at gmail.com) wrote: >>>>> Hi all, >>>>> >>>>> Is it now policy with certain bugs, for the user to be asked to update >>>>> their BIOS? It seems to happening a heck of a lot these days. With the >>>>> inherent danger of BIOS updates and that Ubuntu (Linux for Human Beings) >>>>> has users that are not that technically minded or would shy away from >>>>> such an update - Should it being happening so often? >>>> Yeh I've had a few of those - and I agree it's dangerous. >>>> There are bugs that might very well be fixed by a new BIOS, >>>> but it does need some careful consideration. >>>> >>>> Dave >>>> >>> Dangerous I agree and often a point of fear with users. It would be nice >>> if people doing this on bug reports could add a note. >>> >>> "Please do not feel pressured or required to perform the suggested BIOS >>> update yourself if you are not comfortable with doing so. You may wish >>> to consult a local I.T. professional, who can advise and possibly >>> perform such an update for you in exchange for a fee." >>> >>> Or something like that... :-) >> That sounds like a good suggestion to me, what packages / bugs have seen >> the comments to update your BIOS on? >> >> Thanks! >> -- >> Brian Murray > There are so many instances it would be hard to name 1. My email for the > 'ubuntu-bugs' list goes back to 2013-07-28 and there are > 300 instances > of BIOS update requests to users if I do a search for the string "update > is available for your BIOS". > > Regards > > Phil > > > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 836 bytes > Desc: This is a digitally signed message part > URL: > > ------------------------------ > > Message: 2 > Date: Mon, 19 Aug 2013 05:44:18 +0100 > From: Phil Wyett > To: ubuntu-bugsquad at lists.ubuntu.com > Subject: Re: An invalidated bug. Should it have really been > invalidated? > Message-ID: <1376887458.5343.5.camel at u-k-i-t-yoda> > Content-Type: text/plain; charset="utf-8" > > On Mon, 2013-08-12 at 12:13 -0700, Brian Murray wrote: >> On Sun, Aug 11, 2013 at 06:13:09AM +0100, Phil Wyett wrote: >>> On Sat, 2013-08-10 at 14:23 -0400, Chris Johnston wrote: >>>> I'm not going to comment on keeping the bug opened or closed, however >>>> I will point out: >>>> "Many Linux package, hardware, and other non-user space bugs are >>>> hardware dependent on both the hardware itself, and what other >>>> hardware the problematic hardware is connected to. The rule of thumb >>>> is one report, per person, per hardware combination, per bug. For more >>>> on this please see here, and further below in this article. As well, >>>> please do not post comments to another person's report, claiming you >>>> have the same problem, because you have the same hardware, or same >>>> computer model. Instead, please file a separate report, and make >>>> comments there. This is because no one can verify if you would have >>>> the same problem or not, because your hardware can not be analyzed. " >>>> https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette >>>> >>> Hi, >>> >>> I have read the whole document now after not reading it for a few years. >>> It seems many changes and caveats have been introduced and now we have >>> many flaws in the whole bug reporting process. What should be a simple >>> process for new/inexperienced users (not me as a dev), has actually >>> turned into a spiders web of iffy software and processes to perform the >>> overall task with the addition of many 'do nots' introduced by >>> contributors. >>> >>> Is there anyway the bug squad can hold a review in conjunction with the >>> quality people and look at the whole process once more? As one example >>> to why. If the whole notion of one bug per person per hardware combo and >>> no posting to others reports is the way to go. We should really be using >>> the duplication method on launchpad and the " This bug affects 'x' >>> people. Does this bug affect you? Edit" with this affecting bug heat is >>> essentially redundant. >> Could you elaborate on what you mean by the last two sentences here? >> >> Keep in mind there is a distinction between packages which are generally >> hardware specific (the kernel, X packages) and those that are generally >> not like update-manager and Ubuntu Software Center. >> >> -- >> Brian Murray >> Ubuntu Bug Master >> > I am looking at the flow of launchpad for bugs at the moment. I will > hopefully be able to better explain and offer opinion soon. > > Regards > > Phil > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: signature.asc > Type: application/pgp-signature > Size: 836 bytes > Desc: This is a digitally signed message part > URL: > > ------------------------------ > From noreply at ubuntu.com Mon Aug 19 11:27:25 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 19 Aug 2013 11:27:25 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Responses=22_by_penalvch?= Message-ID: <20130819112725.16986.27932@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Responses" page has been changed by penalvch: http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=369&rev2=370 Comment: Generalized "Fixed_in_Development_release_while_still_existing_in_a_previous_release" as advised in https://lists.launchpad.net/ubuntu-bugcontrol/msg03922.html The bug's state should become '''Fix Released''' and if the package qualifies for a [[https://wiki.ubuntu.com/StableReleaseUpdates#Procedure|Stable Release Update (SRU)]]: - || Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Saucy Salamander.<
><
> This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please do steps 1 and 2 of the SRU Procedure [1] to bring the need to a developer's attention.<
><
>[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure|| + || Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Saucy Salamander. <
><
> This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please perform as much as possible of the SRU Procedure [1] to bring the need to a developer's attention. <
><
> [1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure || - The bug's state should become '''Fix Released''' and if the package does not qualify for a SRU because it is considered a minor bug and the package can be backported: From brian at ubuntu.com Mon Aug 19 17:04:45 2013 From: brian at ubuntu.com (Brian Murray) Date: Mon, 19 Aug 2013 10:04:45 -0700 Subject: Bug Squad and a lot of asks to update BIOS In-Reply-To: <1376887288.5343.3.camel@u-k-i-t-yoda> References: <1376127493.6307.3.camel@u-k-i-t-yoda> <20130810105655.GA11808@gallifrey> <1376199430.5257.6.camel@u-k-i-t-yoda> <20130812185135.GZ2917@murraytwins.com> <1376887288.5343.3.camel@u-k-i-t-yoda> Message-ID: <20130819170445.GA2917@murraytwins.com> On Mon, Aug 19, 2013 at 05:41:28AM +0100, Phil Wyett wrote: > On Mon, 2013-08-12 at 11:51 -0700, Brian Murray wrote: > > On Sun, Aug 11, 2013 at 06:37:10AM +0100, Phil Wyett wrote: > > > On Sat, 2013-08-10 at 11:56 +0100, Dr. David Alan Gilbert wrote: > > > > * Phil Wyett (one.ukit at gmail.com) wrote: > > > > > Hi all, > > > > > > > > > > Is it now policy with certain bugs, for the user to be asked to update > > > > > their BIOS? It seems to happening a heck of a lot these days. With the > > > > > inherent danger of BIOS updates and that Ubuntu (Linux for Human Beings) > > > > > has users that are not that technically minded or would shy away from > > > > > such an update - Should it being happening so often? > > > > > > > > Yeh I've had a few of those - and I agree it's dangerous. > > > > There are bugs that might very well be fixed by a new BIOS, > > > > but it does need some careful consideration. > > > > > > > > Dave > > > > > > > > > > Dangerous I agree and often a point of fear with users. It would be nice > > > if people doing this on bug reports could add a note. > > > > > > "Please do not feel pressured or required to perform the suggested BIOS > > > update yourself if you are not comfortable with doing so. You may wish > > > to consult a local I.T. professional, who can advise and possibly > > > perform such an update for you in exchange for a fee." > > > > > > Or something like that... :-) > > > > That sounds like a good suggestion to me, what packages / bugs have seen > > the comments to update your BIOS on? > > > > Thanks! > > -- > > Brian Murray > > There are so many instances it would be hard to name 1. My email for the > 'ubuntu-bugs' list goes back to 2013-07-28 and there are > 300 instances > of BIOS update requests to users if I do a search for the string "update > is available for your BIOS". The point of my question was to try and find out which team is requesting that users update their BIOS so that you can communicate your idea to them. bdmurray at bizarro:/mnt/storage/mailing-lists/ubuntu-bugs$ mboxgrep -B "update is available for your BIOS" 2013-08 | grep X-Launchpad-Bug: | grep sourcepackage | grep "sourcepackage=linux" | wc -l 206 bdmurray at bizarro:/mnt/storage/mailing-lists/ubuntu-bugs$ mboxgrep -B "update is available for your BIOS" 2013-08 | grep X-Launchpad-Bug: | grep sourcepackage | grep -v "sourcepackage=linux" | wc -l 7 Just looking at the ubuntu-bugs mailing list archive for 2013-08 it looks like these requests are overwhelmingly about the linux package, so the kernel team or probably Joe Salisbury is the right person to whom to speak. -- Brian Murray Ubuntu Bug Master From es20490446e at gmail.com Mon Aug 19 19:30:50 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Mon, 19 Aug 2013 21:30:50 +0200 Subject: Bug Squad and a lot of asks to update BIOS In-Reply-To: <1376887288.5343.3.camel@u-k-i-t-yoda> References: <1376127493.6307.3.camel@u-k-i-t-yoda> <20130810105655.GA11808@gallifrey> <1376199430.5257.6.camel@u-k-i-t-yoda> <20130812185135.GZ2917@murraytwins.com> <1376887288.5343.3.camel@u-k-i-t-yoda> Message-ID: <5212726A.7060802@gmail.com> El 19/08/13 06:41, Phil Wyett escribió: > On Mon, 2013-08-12 at 11:51 -0700, Brian Murray wrote: >> On Sun, Aug 11, 2013 at 06:37:10AM +0100, Phil Wyett wrote: >>> On Sat, 2013-08-10 at 11:56 +0100, Dr. David Alan Gilbert wrote: >>>> * Phil Wyett (one.ukit at gmail.com) wrote: >>>>> Hi all, >>>>> >>>>> Is it now policy with certain bugs, for the user to be asked to update >>>>> their BIOS? It seems to happening a heck of a lot these days. With the >>>>> inherent danger of BIOS updates and that Ubuntu (Linux for Human Beings) >>>>> has users that are not that technically minded or would shy away from >>>>> such an update - Should it being happening so often? >>>> Yeh I've had a few of those - and I agree it's dangerous. >>>> There are bugs that might very well be fixed by a new BIOS, >>>> but it does need some careful consideration. >>>> >>>> Dave >>>> >>> Dangerous I agree and often a point of fear with users. It would be nice >>> if people doing this on bug reports could add a note. >>> >>> "Please do not feel pressured or required to perform the suggested BIOS >>> update yourself if you are not comfortable with doing so. You may wish >>> to consult a local I.T. professional, who can advise and possibly >>> perform such an update for you in exchange for a fee." >>> >>> Or something like that... :-) >> That sounds like a good suggestion to me, what packages / bugs have seen >> the comments to update your BIOS on? >> >> Thanks! >> -- >> Brian Murray > There are so many instances it would be hard to name 1. My email for the > 'ubuntu-bugs' list goes back to 2013-07-28 and there are > 300 instances > of BIOS update requests to users if I do a search for the string "update > is available for your BIOS". > > Regards > > Phil > > > > So perhaps we can make a small note in the wiki, because it seems a recurrent issue. Also to say these issues are not coincidence: I have three different computer and I've been to reproduce bugs in all its updated BIOSes, and some were pretty serious. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5542 bytes Desc: Firma criptográfica S/MIME URL: From one.ukit at gmail.com Tue Aug 20 05:07:52 2013 From: one.ukit at gmail.com (Phil Wyett) Date: Tue, 20 Aug 2013 06:07:52 +0100 Subject: Bug Squad and a lot of asks to update BIOS In-Reply-To: <20130819170445.GA2917@murraytwins.com> References: <1376127493.6307.3.camel@u-k-i-t-yoda> <20130810105655.GA11808@gallifrey> <1376199430.5257.6.camel@u-k-i-t-yoda> <20130812185135.GZ2917@murraytwins.com> <1376887288.5343.3.camel@u-k-i-t-yoda> <20130819170445.GA2917@murraytwins.com> Message-ID: <1376975272.7170.2.camel@u-k-i-t-yoda> On Mon, 2013-08-19 at 10:04 -0700, Brian Murray wrote: > On Mon, Aug 19, 2013 at 05:41:28AM +0100, Phil Wyett wrote: > > On Mon, 2013-08-12 at 11:51 -0700, Brian Murray wrote: > > > On Sun, Aug 11, 2013 at 06:37:10AM +0100, Phil Wyett wrote: > > > > On Sat, 2013-08-10 at 11:56 +0100, Dr. David Alan Gilbert wrote: > > > > > * Phil Wyett (one.ukit at gmail.com) wrote: > > > > > > Hi all, > > > > > > > > > > > > Is it now policy with certain bugs, for the user to be asked to update > > > > > > their BIOS? It seems to happening a heck of a lot these days. With the > > > > > > inherent danger of BIOS updates and that Ubuntu (Linux for Human Beings) > > > > > > has users that are not that technically minded or would shy away from > > > > > > such an update - Should it being happening so often? > > > > > > > > > > Yeh I've had a few of those - and I agree it's dangerous. > > > > > There are bugs that might very well be fixed by a new BIOS, > > > > > but it does need some careful consideration. > > > > > > > > > > Dave > > > > > > > > > > > > > Dangerous I agree and often a point of fear with users. It would be nice > > > > if people doing this on bug reports could add a note. > > > > > > > > "Please do not feel pressured or required to perform the suggested BIOS > > > > update yourself if you are not comfortable with doing so. You may wish > > > > to consult a local I.T. professional, who can advise and possibly > > > > perform such an update for you in exchange for a fee." > > > > > > > > Or something like that... :-) > > > > > > That sounds like a good suggestion to me, what packages / bugs have seen > > > the comments to update your BIOS on? > > > > > > Thanks! > > > -- > > > Brian Murray > > > > There are so many instances it would be hard to name 1. My email for the > > 'ubuntu-bugs' list goes back to 2013-07-28 and there are > 300 instances > > of BIOS update requests to users if I do a search for the string "update > > is available for your BIOS". > > The point of my question was to try and find out which team is > requesting that users update their BIOS so that you can communicate your > idea to them. > > bdmurray at bizarro:/mnt/storage/mailing-lists/ubuntu-bugs$ mboxgrep -B > "update is available for your BIOS" 2013-08 | grep X-Launchpad-Bug: | > grep sourcepackage | grep "sourcepackage=linux" | wc -l > 206 > > bdmurray at bizarro:/mnt/storage/mailing-lists/ubuntu-bugs$ mboxgrep -B > "update is available for your BIOS" 2013-08 | grep X-Launchpad-Bug: | > grep sourcepackage | grep -v "sourcepackage=linux" | wc -l > 7 > > Just looking at the ubuntu-bugs mailing list archive for 2013-08 it > looks like these requests are overwhelmingly about the linux package, so > the kernel team or probably Joe Salisbury is the right person to whom to > speak. > > -- > Brian Murray > Ubuntu Bug Master > Yes, a look does show this is the case primarily. Looking at bugs and the reporting process. I am going to leave this for a week and see what comes out of: https://blueprints.launchpad.net/ubuntu/+spec/community-1308-quality-reporting-bugs at next weeks vUDS. Regards Phil -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part URL: From one.ukit at gmail.com Tue Aug 20 05:09:05 2013 From: one.ukit at gmail.com (Phil Wyett) Date: Tue, 20 Aug 2013 06:09:05 +0100 Subject: An invalidated bug. Should it have really been invalidated? In-Reply-To: <20130813193436.16180dcb@xango3> References: <1376128168.6307.6.camel@u-k-i-t-yoda> <5206368A.1060902@ubuntu.com> <1376147800.6307.10.camel@u-k-i-t-yoda> <20130810164431.GC11808@gallifrey> <20130812190327.GA2917@murraytwins.com> <20130813230508.GB2916@gallifrey> <20130813193436.16180dcb@xango3> Message-ID: <1376975345.7170.3.camel@u-k-i-t-yoda> On Tue, 2013-08-13 at 19:34 -0500, C de-Avillez wrote: > On Wed, 14 Aug 2013 00:05:08 +0100 > "Dr. David Alan Gilbert" wrote: > > > * Brian Murray (brian at ubuntu.com) wrote: > > > On Sat, Aug 10, 2013 at 05:44:31PM +0100, Dr. David Alan Gilbert > > > wrote: > > > > * Claudio Moretti (flyingstar16 at gmail.com) wrote: > > > > > On Sat, Aug 10, 2013 at 5:16 PM, Phil Wyett > > > > > wrote: > > > > > > > > > > > The bug I am concerned about is #1172908 > > > > > > > > > > > > > > > > I reopened it; in my opinion, it should have never been closed: > > > > > if there's at least one person able to reproduce it, the bug is > > > > > there. In this case, there are three. > > > > > > > > I agree, however it's a little tricky with Kernel bugs; the normal > > > > instructions there are not to merge bugs unless you're sure it's > > > > the same bug. > > > > In this case I would agree they're almost certainly the same > > > > problem (since the models are all the same). > > > > > > I didn't read all the comments in the bug report, but how can we be > > > certain that they are all the same models? I'm under the impression > > > that internal components of systems change even though they may all > > > be called the same name. Subsequently, I understand why the kernel > > > team wants individual bug reports (with hardware information > > > gathered) from each user. > > > > I'm ok with requiring individual bugs from individual users > > but we've got to be able to do something when we find a bug > > that feels like it's specific and affects a certain range of machines. > > Can we be 'certain' no, but given that: > > > > - It's a specific well defined problem (Only the USB2 ports are > > failing not the USB3). > > - We're not seeing this on loads of different systems > > - But we are seeing it on a group of similar models > > - It's not a fluffy sometimes-happens bug. > > > > Now some of those are a judgement call rather than a hard > > and fast rule, but that's why we're not entirely scripted! > > > > Then I say we have a common bug here and we need some way to represent > > it. If the way isn't allowing multiple users to put their info > > on one report then we need a metabug or something, we also > > need a way to keep hold of it if any one of the original reporters > > gives up. > > I agree, and I think all would agree as well. This is where I stated, > in another subthread, that have a procedure to identify "collisions" > would be nice, the more automated, the better. It could very well be a > back-office process, giving as output a series of bugs that match > hardware (and then would be analysed by humans). > > For *kernel* bugs, this would be simplified due to the automagic > collection of bug data (with same-named-attachments). But it is still a > bit complex since we do not have basic problem data as well-formed > attributes. This means, potentially, a hell of a problem on parsing -- > say -- bug titles for clues. > > Metadata, perhaps added to the description, might help; for example, a > series of key=value fields. But this would make, if the reporter is > expected to fill them in, bug reporting by casual users even more > complex. > > (Which, of course, goes nicely with my previous comment that bugs are > *technical* thingies.) > > One of the problems with "no mixing of affected users" on kernel (and > other hardware-related) bugs is that the sheer amount of unique bugs > cause many of them to die of old age. Recently, I myself received a > series of emails asking for more data/try new kernel/update BIOS, for > systems I do not have access to anymore, and for UBuntu versions > already obsoleted. These were interesting bugs when they were opened, > but now are on the track to be closed invalid. > > In other words: I fully agree with Dave; at the same time I do > understand the kernel's requirement for one bug per user. Dave's > approach might help, at least a bit, minimise age/relevance issues. > > Let's keep on, I like the suggestions :-) > > ..C.. > > > -- > ab alio expectes alteri quod feceris > Looking at bugs and the reporting process. I am going to leave this for a week and see what comes out of: https://blueprints.launchpad.net/ubuntu/+spec/community-1308-quality-reporting-bugs at next weeks vUDS. Regards Phil -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part URL: From one.ukit at gmail.com Tue Aug 20 05:11:23 2013 From: one.ukit at gmail.com (Phil Wyett) Date: Tue, 20 Aug 2013 06:11:23 +0100 Subject: Bug Squad and a lot of asks to update BIOS In-Reply-To: <1376975272.7170.2.camel@u-k-i-t-yoda> References: <1376127493.6307.3.camel@u-k-i-t-yoda> <20130810105655.GA11808@gallifrey> <1376199430.5257.6.camel@u-k-i-t-yoda> <20130812185135.GZ2917@murraytwins.com> <1376887288.5343.3.camel@u-k-i-t-yoda> <20130819170445.GA2917@murraytwins.com> <1376975272.7170.2.camel@u-k-i-t-yoda> Message-ID: <1376975483.7170.5.camel@u-k-i-t-yoda> On Tue, 2013-08-20 at 06:07 +0100, Phil Wyett wrote: > On Mon, 2013-08-19 at 10:04 -0700, Brian Murray wrote: > > On Mon, Aug 19, 2013 at 05:41:28AM +0100, Phil Wyett wrote: > > > On Mon, 2013-08-12 at 11:51 -0700, Brian Murray wrote: > > > > On Sun, Aug 11, 2013 at 06:37:10AM +0100, Phil Wyett wrote: > > > > > On Sat, 2013-08-10 at 11:56 +0100, Dr. David Alan Gilbert wrote: > > > > > > * Phil Wyett (one.ukit at gmail.com) wrote: > > > > > > > Hi all, > > > > > > > > > > > > > > Is it now policy with certain bugs, for the user to be asked to update > > > > > > > their BIOS? It seems to happening a heck of a lot these days. With the > > > > > > > inherent danger of BIOS updates and that Ubuntu (Linux for Human Beings) > > > > > > > has users that are not that technically minded or would shy away from > > > > > > > such an update - Should it being happening so often? > > > > > > > > > > > > Yeh I've had a few of those - and I agree it's dangerous. > > > > > > There are bugs that might very well be fixed by a new BIOS, > > > > > > but it does need some careful consideration. > > > > > > > > > > > > Dave > > > > > > > > > > > > > > > > Dangerous I agree and often a point of fear with users. It would be nice > > > > > if people doing this on bug reports could add a note. > > > > > > > > > > "Please do not feel pressured or required to perform the suggested BIOS > > > > > update yourself if you are not comfortable with doing so. You may wish > > > > > to consult a local I.T. professional, who can advise and possibly > > > > > perform such an update for you in exchange for a fee." > > > > > > > > > > Or something like that... :-) > > > > > > > > That sounds like a good suggestion to me, what packages / bugs have seen > > > > the comments to update your BIOS on? > > > > > > > > Thanks! > > > > -- > > > > Brian Murray > > > > > > There are so many instances it would be hard to name 1. My email for the > > > 'ubuntu-bugs' list goes back to 2013-07-28 and there are > 300 instances > > > of BIOS update requests to users if I do a search for the string "update > > > is available for your BIOS". > > > > The point of my question was to try and find out which team is > > requesting that users update their BIOS so that you can communicate your > > idea to them. > > > > bdmurray at bizarro:/mnt/storage/mailing-lists/ubuntu-bugs$ mboxgrep -B > > "update is available for your BIOS" 2013-08 | grep X-Launchpad-Bug: | > > grep sourcepackage | grep "sourcepackage=linux" | wc -l > > 206 > > > > bdmurray at bizarro:/mnt/storage/mailing-lists/ubuntu-bugs$ mboxgrep -B > > "update is available for your BIOS" 2013-08 | grep X-Launchpad-Bug: | > > grep sourcepackage | grep -v "sourcepackage=linux" | wc -l > > 7 > > > > Just looking at the ubuntu-bugs mailing list archive for 2013-08 it > > looks like these requests are overwhelmingly about the linux package, so > > the kernel team or probably Joe Salisbury is the right person to whom to > > speak. > > > > -- > > Brian Murray > > Ubuntu Bug Master > > > > Yes, a look does show this is the case primarily. Looking at bugs and > the reporting process. I am going to leave this for a week and see what > comes out of: > > https://blueprints.launchpad.net/ubuntu/+spec/community-1308-quality-reporting-bugs > > at next weeks vUDS. > > Regards > > Phil For those interested. The vUDS session next week has come about in part because of bug reports such as. https://bugs.launchpad.net/ubuntu/+bug/1212356 Regards Phil -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part URL: From brian at ubuntu.com Tue Aug 20 15:25:27 2013 From: brian at ubuntu.com (Brian Murray) Date: Tue, 20 Aug 2013 08:25:27 -0700 Subject: Bug Squad and a lot of asks to update BIOS In-Reply-To: <1376975272.7170.2.camel@u-k-i-t-yoda> References: <1376127493.6307.3.camel@u-k-i-t-yoda> <20130810105655.GA11808@gallifrey> <1376199430.5257.6.camel@u-k-i-t-yoda> <20130812185135.GZ2917@murraytwins.com> <1376887288.5343.3.camel@u-k-i-t-yoda> <20130819170445.GA2917@murraytwins.com> <1376975272.7170.2.camel@u-k-i-t-yoda> Message-ID: <20130820152526.GD2917@murraytwins.com> On Tue, Aug 20, 2013 at 06:07:52AM +0100, Phil Wyett wrote: > On Mon, 2013-08-19 at 10:04 -0700, Brian Murray wrote: > > On Mon, Aug 19, 2013 at 05:41:28AM +0100, Phil Wyett wrote: > > > On Mon, 2013-08-12 at 11:51 -0700, Brian Murray wrote: > > > > On Sun, Aug 11, 2013 at 06:37:10AM +0100, Phil Wyett wrote: > > > > > On Sat, 2013-08-10 at 11:56 +0100, Dr. David Alan Gilbert wrote: > > > > > > * Phil Wyett (one.ukit at gmail.com) wrote: > > > > > > > Hi all, > > > > > > > > > > > > > > Is it now policy with certain bugs, for the user to be asked to update > > > > > > > their BIOS? It seems to happening a heck of a lot these days. With the > > > > > > > inherent danger of BIOS updates and that Ubuntu (Linux for Human Beings) > > > > > > > has users that are not that technically minded or would shy away from > > > > > > > such an update - Should it being happening so often? > > > > > > > > > > > > Yeh I've had a few of those - and I agree it's dangerous. > > > > > > There are bugs that might very well be fixed by a new BIOS, > > > > > > but it does need some careful consideration. > > > > > > > > > > > > Dave > > > > > > > > > > > > > > > > Dangerous I agree and often a point of fear with users. It would be nice > > > > > if people doing this on bug reports could add a note. > > > > > > > > > > "Please do not feel pressured or required to perform the suggested BIOS > > > > > update yourself if you are not comfortable with doing so. You may wish > > > > > to consult a local I.T. professional, who can advise and possibly > > > > > perform such an update for you in exchange for a fee." > > > > > > > > > > Or something like that... :-) > > > > > > > > That sounds like a good suggestion to me, what packages / bugs have seen > > > > the comments to update your BIOS on? > > > > > > > > Thanks! > > > > -- > > > > Brian Murray > > > > > > There are so many instances it would be hard to name 1. My email for the > > > 'ubuntu-bugs' list goes back to 2013-07-28 and there are > 300 instances > > > of BIOS update requests to users if I do a search for the string "update > > > is available for your BIOS". > > > > The point of my question was to try and find out which team is > > requesting that users update their BIOS so that you can communicate your > > idea to them. > > > > bdmurray at bizarro:/mnt/storage/mailing-lists/ubuntu-bugs$ mboxgrep -B > > "update is available for your BIOS" 2013-08 | grep X-Launchpad-Bug: | > > grep sourcepackage | grep "sourcepackage=linux" | wc -l > > 206 > > > > bdmurray at bizarro:/mnt/storage/mailing-lists/ubuntu-bugs$ mboxgrep -B > > "update is available for your BIOS" 2013-08 | grep X-Launchpad-Bug: | > > grep sourcepackage | grep -v "sourcepackage=linux" | wc -l > > 7 > > > > Just looking at the ubuntu-bugs mailing list archive for 2013-08 it > > looks like these requests are overwhelmingly about the linux package, so > > the kernel team or probably Joe Salisbury is the right person to whom to > > speak. > > > > -- > > Brian Murray > > Ubuntu Bug Master > > > > Yes, a look does show this is the case primarily. Looking at bugs and > the reporting process. I am going to leave this for a week and see what > comes out of: > > https://blueprints.launchpad.net/ubuntu/+spec/community-1308-quality-reporting-bugs > > at next weeks vUDS. This blueprint is about how bugs are reported and we have been discussing how bugs are triaged so I think they are two different issues. -- Brian Murray Ubuntu Bug Master From one.ukit at gmail.com Wed Aug 21 02:39:04 2013 From: one.ukit at gmail.com (Phil Wyett) Date: Wed, 21 Aug 2013 03:39:04 +0100 Subject: Bug Squad and a lot of asks to update BIOS In-Reply-To: <20130820152526.GD2917@murraytwins.com> References: <1376127493.6307.3.camel@u-k-i-t-yoda> <20130810105655.GA11808@gallifrey> <1376199430.5257.6.camel@u-k-i-t-yoda> <20130812185135.GZ2917@murraytwins.com> <1376887288.5343.3.camel@u-k-i-t-yoda> <20130819170445.GA2917@murraytwins.com> <1376975272.7170.2.camel@u-k-i-t-yoda> <20130820152526.GD2917@murraytwins.com> Message-ID: <1377052744.6538.9.camel@u-k-i-t-yoda> On Tue, 2013-08-20 at 08:25 -0700, Brian Murray wrote: > On Tue, Aug 20, 2013 at 06:07:52AM +0100, Phil Wyett wrote: > > On Mon, 2013-08-19 at 10:04 -0700, Brian Murray wrote: > > > On Mon, Aug 19, 2013 at 05:41:28AM +0100, Phil Wyett wrote: > > > > On Mon, 2013-08-12 at 11:51 -0700, Brian Murray wrote: > > > > > On Sun, Aug 11, 2013 at 06:37:10AM +0100, Phil Wyett wrote: > > > > > > On Sat, 2013-08-10 at 11:56 +0100, Dr. David Alan Gilbert wrote: > > > > > > > * Phil Wyett (one.ukit at gmail.com) wrote: > > > > > > > > Hi all, > > > > > > > > > > > > > > > > Is it now policy with certain bugs, for the user to be asked to update > > > > > > > > their BIOS? It seems to happening a heck of a lot these days. With the > > > > > > > > inherent danger of BIOS updates and that Ubuntu (Linux for Human Beings) > > > > > > > > has users that are not that technically minded or would shy away from > > > > > > > > such an update - Should it being happening so often? > > > > > > > > > > > > > > Yeh I've had a few of those - and I agree it's dangerous. > > > > > > > There are bugs that might very well be fixed by a new BIOS, > > > > > > > but it does need some careful consideration. > > > > > > > > > > > > > > Dave > > > > > > > > > > > > > > > > > > > Dangerous I agree and often a point of fear with users. It would be nice > > > > > > if people doing this on bug reports could add a note. > > > > > > > > > > > > "Please do not feel pressured or required to perform the suggested BIOS > > > > > > update yourself if you are not comfortable with doing so. You may wish > > > > > > to consult a local I.T. professional, who can advise and possibly > > > > > > perform such an update for you in exchange for a fee." > > > > > > > > > > > > Or something like that... :-) > > > > > > > > > > That sounds like a good suggestion to me, what packages / bugs have seen > > > > > the comments to update your BIOS on? > > > > > > > > > > Thanks! > > > > > -- > > > > > Brian Murray > > > > > > > > There are so many instances it would be hard to name 1. My email for the > > > > 'ubuntu-bugs' list goes back to 2013-07-28 and there are > 300 instances > > > > of BIOS update requests to users if I do a search for the string "update > > > > is available for your BIOS". > > > > > > The point of my question was to try and find out which team is > > > requesting that users update their BIOS so that you can communicate your > > > idea to them. > > > > > > bdmurray at bizarro:/mnt/storage/mailing-lists/ubuntu-bugs$ mboxgrep -B > > > "update is available for your BIOS" 2013-08 | grep X-Launchpad-Bug: | > > > grep sourcepackage | grep "sourcepackage=linux" | wc -l > > > 206 > > > > > > bdmurray at bizarro:/mnt/storage/mailing-lists/ubuntu-bugs$ mboxgrep -B > > > "update is available for your BIOS" 2013-08 | grep X-Launchpad-Bug: | > > > grep sourcepackage | grep -v "sourcepackage=linux" | wc -l > > > 7 > > > > > > Just looking at the ubuntu-bugs mailing list archive for 2013-08 it > > > looks like these requests are overwhelmingly about the linux package, so > > > the kernel team or probably Joe Salisbury is the right person to whom to > > > speak. > > > > > > -- > > > Brian Murray > > > Ubuntu Bug Master > > > > > > > Yes, a look does show this is the case primarily. Looking at bugs and > > the reporting process. I am going to leave this for a week and see what > > comes out of: > > > > https://blueprints.launchpad.net/ubuntu/+spec/community-1308-quality-reporting-bugs > > > > at next weeks vUDS. > > This blueprint is about how bugs are reported and we have been > discussing how bugs are triaged so I think they are two different > issues. > At the present time I am treating these as the same. The whole process of reporting bugs as in https://help.ubuntu.com/community/ReportingBugs has been polluted by person(s) doing bug triage with a whole bunch of 'do this' and 'do not do that' before you even get to the point of actually finding out how to report a bug. Paragraph 2 is a good example of this and will no doubt intimidate many non technical users when confronted and asked to update BIOS, firmware etcetera on devices even before getting to the stage of just reporting their issue at hand. Regards Phil -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part URL: From nicholas.skaggs at canonical.com Mon Aug 26 17:49:39 2013 From: nicholas.skaggs at canonical.com (Nicholas Skaggs) Date: Mon, 26 Aug 2013 13:49:39 -0400 Subject: Quality vUDS Sessions In-Reply-To: <1376739949.4463.31.camel@Saxy> References: <520E90D6.4080900@canonical.com> <1376739949.4463.31.camel@Saxy> Message-ID: Thanks to everyone for the feedback! I have added sessions to cover all of these concerns and ideas -- I hope. Here's the details. Sorry for the late response as I was away last week. I hope to see everyone in the sessions! https://blueprints.launchpad.net/ubuntu/+spec/community-1308-quality-testreview https://blueprints.launchpad.net/ubuntu/+spec/community-1308-quality-rountable Nicholas On Sat, Aug 17, 2013 at 7:45 AM, Me wrote: > ** > Hallo to everybody. > I've noted the impair situation about UbuntuKylin in front of Ubuntu. > It is not a flavour of Ubuntu, is Ubuntu for the Chinese people, so we can > see the lacks of the testcases adopted for LVM and others. > How we as Quality group can manage this situation for the Chinese people > that cannot use an english tracker ? > Have them their reserved Chinese channels ? > Canonical and Chinese government starts this project, so we have to put > some more effort to better raise this problem coordinating also with the > UbuntuKylin teams. > My best wishes to all of you. > > Fabio > > > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicholas.skaggs at canonical.com Wed Aug 28 14:49:15 2013 From: nicholas.skaggs at canonical.com (Nicholas Skaggs) Date: Wed, 28 Aug 2013 10:49:15 -0400 Subject: Reminder: vUDS session on bug reporting happening now Message-ID: http://summit.ubuntu.com/uds-1308/meeting/21840/community-1308-quality-reporting-bugs/ Join via IRC or hop on the video. Your free to also leave notes in the pad. Thanks! Nicholas -------------- next part -------------- An HTML attachment was scrubbed... URL: From rohandighe18 at gmail.com Thu Aug 29 11:56:54 2013 From: rohandighe18 at gmail.com (rohan dighe) Date: Thu, 29 Aug 2013 17:26:54 +0530 Subject: sks init script bug in ubuntu 12.04 Message-ID: Hi Team, I am working on setting up a gpg key server on ubuntu server,but facing some issue as the init script of sks has some bug.when I set up the gpg key server and starts sks service I get the below output on command prompt its shows service running but its actually not running and also I cant get the pid process of sks service showing running. root at tripwiretest: sks]# /etc/init.d/sks start Starting sks daemons: sksdb.. sksrecon.. done. The ubuntu showing the bug on this link. https://bugs.launchpad.net/ubuntu/+source/sks/+bug/820354 I also followed the solution given on the link but with no success. As the sks comes from the ubuntu 12.04 repository do we have any permanent fix for the init script of sks. Please help me regarding the init script of sks. Thanks, Rohan -------------- next part -------------- An HTML attachment was scrubbed... URL: From teward at ubuntu.com Thu Aug 29 19:08:25 2013 From: teward at ubuntu.com (Thomas Ward) Date: Thu, 29 Aug 2013 15:08:25 -0400 Subject: sks init script bug in ubuntu 12.04 In-Reply-To: References: Message-ID: I took a look at that bug, the bug went inactive because it had no activity or updates when the bug was marked "Incomplete". Since the original poster and nobody else provided any additional information the bug auto expired. I can try confirming this bug, however if I remember when I was configuring sks back in the days of 11.04 and 11.10, you had to configure it before you could actually start or restart the sks process. I'll take a look and see if I can reproduce, but there's probably logs somewhere for sks explaining why it didn't start or such. I'll check back with this in a little bit after I've done some testing. ------ Thomas Ubuntu Member Bug Squad Member On Thu, Aug 29, 2013 at 7:56 AM, rohan dighe wrote: > Hi Team, > > I am working on setting up a gpg key server on ubuntu server,but facing > some issue as the init script of sks has some bug.when I set up the gpg key > server and starts sks service > > I get the below output on command prompt its shows service running but its > actually not running and also I cant get the pid process of sks service > showing running. > > root at tripwiretest: sks]# /etc/init.d/sks start > Starting sks daemons: sksdb.. sksrecon.. done. > > The ubuntu showing the bug on this link. > > https://bugs.launchpad.net/ubuntu/+source/sks/+bug/820354 > > I also followed the solution given on the link but with no success. > > As the sks comes from the ubuntu 12.04 repository do we have any permanent > fix for the init script of sks. > > Please help me regarding the init script of sks. > > Thanks, > Rohan > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From teward at ubuntu.com Thu Aug 29 19:18:03 2013 From: teward at ubuntu.com (Thomas Ward) Date: Thu, 29 Aug 2013 15:18:03 -0400 Subject: sks init script bug in ubuntu 12.04 In-Reply-To: References: Message-ID: Rohan, On Thu, Aug 29, 2013 at 3:08 PM, Thomas Ward wrote: > I took a look at that bug, the bug went inactive because it had no > activity or updates when the bug was marked "Incomplete". Since the > original poster and nobody else provided any additional information the bug > auto expired. > > I can try confirming this bug, however if I remember when I was > configuring sks back in the days of 11.04 and 11.10, you had to configure > it before you could actually start or restart the sks process. > > I'll take a look and see if I can reproduce, but there's probably logs > somewhere for sks explaining why it didn't start or such. > > I'll check back with this in a little bit after I've done some testing. > > ------ > Thomas > Ubuntu Member > Bug Squad Member > > > On Thu, Aug 29, 2013 at 7:56 AM, rohan dighe wrote: > >> Hi Team, >> >> I am working on setting up a gpg key server on ubuntu server,but facing >> some issue as the init script of sks has some bug.when I set up the gpg key >> server and starts sks service >> >> I get the below output on command prompt its shows service running but >> its actually not running and also I cant get the pid process of sks service >> showing running. >> >> root at tripwiretest: sks]# /etc/init.d/sks start >> Starting sks daemons: sksdb.. sksrecon.. done. >> >> The ubuntu showing the bug on this link. >> >> https://bugs.launchpad.net/ubuntu/+source/sks/+bug/820354 >> >> I also followed the solution given on the link but with no success. >> >> As the sks comes from the ubuntu 12.04 repository do we have any >> permanent fix for the init script of sks. >> >> Please help me regarding the init script of sks. >> >> Thanks, >> Rohan >> >> -- >> Ubuntu-bugsquad mailing list >> Ubuntu-bugsquad at lists.ubuntu.com >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad >> >> > Using a properly configured 'sks' instance, I am unable to reproduce this bug, and using the init.d script correctly launches the two sks processes, one for the DB, one for recon. Also, the package 'sks' does not by default set up the key database or other items just by installing. Did you actually configure 'sks' first before attempting to run it with the init script? ------ Thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: From rohandighe18 at gmail.com Fri Aug 30 14:04:35 2013 From: rohandighe18 at gmail.com (rohan dighe) Date: Fri, 30 Aug 2013 19:34:35 +0530 Subject: sks init script bug in ubuntu 12.04 In-Reply-To: References: Message-ID: Hi Team, Thanks for the immediate response I really appreciate your efforts on providing me the solution for sks server. Here are the steps I am following to setup the sks server on ubuntu 12.04 # aptitude install sks Set database permissions on the database used by sks to store keys # chown -Rc debian-sks:debian-sks /var/lib/sks/DB To start the server automatically, set initstart=yes in /etc/default/sks # Here I start the sks service # /etc/init.d/sks start Stopping sks daemons: sksrecon..start-stop-daemon: warning: failed to kill 31643: No such process sksdb..start-stop-daemon: warning: failed to kill 31640: No such process done. Starting sks daemons: sksdb.. sksrecon.. done. Then I configure webinterface for sks I install the sks winzip from internet Then I created a www directory in /var/lib/sks unzip the sks in /var/lib/sks/www folder After that 2 files gets downloaded in /var/lib/sks/www folder. 1) index.html 2) keys.jpg I Edit index.html and change the three references to your.site.name(currently at lines 20, 36 & 62) to the url of your keyserver) ( In my case its my server ip ) Then I change the permission on the files # chown -R debian-sks:debian-sks /var/lib/sks/www After that when I tried to browse http://myserverip:11371 its not working. I also tried to get the pid of the sks but the pid is not running on the server below is the given output. # ps -aufx | grep sks Warning: bad ps syntax, perhaps a bogus '-'? See http://procps.sf.net/faq.html root 31950 0.0 0.0 9384 900 pts/1 S+ 19:26 0:00 \_ grep --color=auto sks Here I cant see the 2 process running for sks one for the DB, one for recon. The ps output shows here that sks pid is not running ,It will be helpful if you let me know where exact the problem lies in sks. Thanks, Rohan On Fri, Aug 30, 2013 at 12:48 AM, Thomas Ward wrote: > Rohan, > > > On Thu, Aug 29, 2013 at 3:08 PM, Thomas Ward wrote: > >> I took a look at that bug, the bug went inactive because it had no >> activity or updates when the bug was marked "Incomplete". Since the >> original poster and nobody else provided any additional information the bug >> auto expired. >> >> I can try confirming this bug, however if I remember when I was >> configuring sks back in the days of 11.04 and 11.10, you had to configure >> it before you could actually start or restart the sks process. >> >> I'll take a look and see if I can reproduce, but there's probably logs >> somewhere for sks explaining why it didn't start or such. >> >> I'll check back with this in a little bit after I've done some testing. >> >> ------ >> Thomas >> Ubuntu Member >> Bug Squad Member >> >> >> On Thu, Aug 29, 2013 at 7:56 AM, rohan dighe wrote: >> >>> Hi Team, >>> >>> I am working on setting up a gpg key server on ubuntu server,but facing >>> some issue as the init script of sks has some bug.when I set up the gpg key >>> server and starts sks service >>> >>> I get the below output on command prompt its shows service running but >>> its actually not running and also I cant get the pid process of sks service >>> showing running. >>> >>> root at tripwiretest: sks]# /etc/init.d/sks start >>> Starting sks daemons: sksdb.. sksrecon.. done. >>> >>> The ubuntu showing the bug on this link. >>> >>> https://bugs.launchpad.net/ubuntu/+source/sks/+bug/820354 >>> >>> I also followed the solution given on the link but with no success. >>> >>> As the sks comes from the ubuntu 12.04 repository do we have any >>> permanent fix for the init script of sks. >>> >>> Please help me regarding the init script of sks. >>> >>> Thanks, >>> Rohan >>> >>> -- >>> Ubuntu-bugsquad mailing list >>> Ubuntu-bugsquad at lists.ubuntu.com >>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad >>> >>> >> > Using a properly configured 'sks' instance, I am unable to reproduce this > bug, and using the init.d script correctly launches the two sks processes, > one for the DB, one for recon. > > Also, the package 'sks' does not by default set up the key database or > other items just by installing. Did you actually configure 'sks' first > before attempting to run it with the init script? > > ------ > Thomas > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From teward at ubuntu.com Fri Aug 30 16:20:21 2013 From: teward at ubuntu.com (Thomas Ward) Date: Fri, 30 Aug 2013 12:20:21 -0400 Subject: sks init script bug in ubuntu 12.04 In-Reply-To: References: Message-ID: Rohan, On Fri, Aug 30, 2013 at 10:04 AM, rohan dighe wrote: > > > Hi Team, > > Thanks for the immediate response I really appreciate your efforts on providing me the solution for sks server. > > Here are the steps I am following to setup the sks server on ubuntu 12.04 > > # aptitude install sks > > Set database permissions on the database used by sks to store keys > > # chown -Rc debian-sks:debian-sks /var/lib/sks/DB > > To start the server automatically, set initstart=yes in /etc/default/sks > > # Here I start the sks service > > # /etc/init.d/sks start > Stopping sks daemons: sksrecon..start-stop-daemon: warning: failed to kill 31643: No such process > sksdb..start-stop-daemon: warning: failed to kill 31640: No such process > done. > > Starting sks daemons: sksdb.. sksrecon.. done. > > Then I configure webinterface for sks > > I install the sks winzip from internet > > Then I created a www directory in /var/lib/sks > > unzip the sks in /var/lib/sks/www folder > > After that 2 files gets downloaded in /var/lib/sks/www folder. > > 1) index.html > > 2) keys.jpg > > I Edit index.html and change the three references to your.site.name (currently at lines 20, 36 & 62) to the url of your keyserver) ( In my case its my server ip ) > > Then I change the permission on the files > > # chown -R debian-sks:debian-sks /var/lib/sks/www > > After that when I tried to browse http://myserverip:11371 its not working. > > I also tried to get the pid of the sks but the pid is not running on the server below is the given output. > > # ps -aufx | grep sks > Warning: bad ps syntax, perhaps a bogus '-'? See http://procps.sf.net/faq.html > root 31950 0.0 0.0 9384 900 pts/1 S+ 19:26 0:00 \_ grep --color=auto sks > > Here I cant see the 2 process running for sks one for the DB, one for recon. > > The ps output shows here that sks pid is not running ,It will be helpful if you let me know where exact the problem lies in sks. > > > Thanks, > Rohan > > On Fri, Aug 30, 2013 at 12:48 AM, Thomas Ward wrote: >> >> Rohan, >> >> On Thu, Aug 29, 2013 at 3:08 PM, Thomas Ward wrote: >>> >>> I took a look at that bug, the bug went inactive because it had no activity or updates when the bug was marked "Incomplete". Since the original poster and nobody else provided any additional information the bug auto expired. >>> >>> I can try confirming this bug, however if I remember when I was configuring sks back in the days of 11.04 and 11.10, you had to configure it before you could actually start or restart the sks process. >>> >>> I'll take a look and see if I can reproduce, but there's probably logs somewhere for sks explaining why it didn't start or such. >>> >>> I'll check back with this in a little bit after I've done some testing. >>> >>> ------ >>> Thomas >>> Ubuntu Member >>> Bug Squad Member >>> >>> >>> On Thu, Aug 29, 2013 at 7:56 AM, rohan dighe wrote: >>>> >>>> Hi Team, >>>> >>>> I am working on setting up a gpg key server on ubuntu server,but facing some issue as the init script of sks has some bug.when I set up the gpg key server and starts sks service >>>> >>>> I get the below output on command prompt its shows service running but its actually not running and also I cant get the pid process of sks service showing running. >>>> >>>> root at tripwiretest: sks]# /etc/init.d/sks start >>>> Starting sks daemons: sksdb.. sksrecon.. done. >>>> >>>> The ubuntu showing the bug on this link. >>>> >>>> https://bugs.launchpad.net/ubuntu/+source/sks/+bug/820354 >>>> >>>> I also followed the solution given on the link but with no success. >>>> >>>> As the sks comes from the ubuntu 12.04 repository do we have any permanent fix for the init script of sks. >>>> >>>> Please help me regarding the init script of sks. >>>> >>>> Thanks, >>>> Rohan >>>> >>>> -- >>>> Ubuntu-bugsquad mailing list >>>> Ubuntu-bugsquad at lists.ubuntu.com >>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad >>>> >>> >> >> Using a properly configured 'sks' instance, I am unable to reproduce this bug, and using the init.d script correctly launches the two sks processes, one for the DB, one for recon. >> >> Also, the package 'sks' does not by default set up the key database or other items just by installing. Did you actually configure 'sks' first before attempting to run it with the init script? >> >> ------ >> Thomas >> > Typically, when I configured sks on several systems, I always had to do this step to get the key db built after installing, then afterwards I chown'd /var/lib/sks/DB: sudo sks build Did you run the build command for sks before attempting to launch sks? If you did that and are still getting this error, then perhaps we should purge sks from your system and start anew? This link here [1] was able to help me get a brand new sks instance set up correctly without incident, though, and it correctly runs the sks process and builds the key database so it works. [1] https://kura.io/2011/12/17/running-your-own-pgp-keyserver-with-sks-on-debian-6ubuntu-10-04/ ------ Thomas From teward at ubuntu.com Fri Aug 30 16:25:11 2013 From: teward at ubuntu.com (Thomas Ward) Date: Fri, 30 Aug 2013 12:25:11 -0400 Subject: sks init script bug in ubuntu 12.04 In-Reply-To: References: Message-ID: Note: the tutorial I linked has their own keyserver page that they have you get for the web interface, and for all intents and purposes for testing, it works, but you are NOT obligated to use their web interface page, I do because it's text only and I don't have to mess with pictures on the HTML. (It looks like this: http://imagebin.org/index.php?mode=image&id=269248 (this image link is available for 14 days) ) On Fri, Aug 30, 2013 at 12:20 PM, Thomas Ward wrote: > Rohan, > > On Fri, Aug 30, 2013 at 10:04 AM, rohan dighe wrote: >> >> >> Hi Team, >> >> Thanks for the immediate response I really appreciate your efforts on providing me the solution for sks server. >> >> Here are the steps I am following to setup the sks server on ubuntu 12.04 >> >> # aptitude install sks >> >> Set database permissions on the database used by sks to store keys >> >> # chown -Rc debian-sks:debian-sks /var/lib/sks/DB >> >> To start the server automatically, set initstart=yes in /etc/default/sks >> >> # Here I start the sks service >> >> # /etc/init.d/sks start >> Stopping sks daemons: sksrecon..start-stop-daemon: warning: failed to kill 31643: No such process >> sksdb..start-stop-daemon: warning: failed to kill 31640: No such process >> done. >> >> Starting sks daemons: sksdb.. sksrecon.. done. >> >> Then I configure webinterface for sks >> >> I install the sks winzip from internet >> >> Then I created a www directory in /var/lib/sks >> >> unzip the sks in /var/lib/sks/www folder >> >> After that 2 files gets downloaded in /var/lib/sks/www folder. >> >> 1) index.html >> >> 2) keys.jpg >> >> I Edit index.html and change the three references to your.site.name (currently at lines 20, 36 & 62) to the url of your keyserver) ( In my case its my server ip ) >> >> Then I change the permission on the files >> >> # chown -R debian-sks:debian-sks /var/lib/sks/www >> >> After that when I tried to browse http://myserverip:11371 its not working. >> >> I also tried to get the pid of the sks but the pid is not running on the server below is the given output. >> >> # ps -aufx | grep sks >> Warning: bad ps syntax, perhaps a bogus '-'? See http://procps.sf.net/faq.html >> root 31950 0.0 0.0 9384 900 pts/1 S+ 19:26 0:00 \_ grep --color=auto sks >> >> Here I cant see the 2 process running for sks one for the DB, one for recon. >> >> The ps output shows here that sks pid is not running ,It will be helpful if you let me know where exact the problem lies in sks. >> >> >> Thanks, >> Rohan >> >> On Fri, Aug 30, 2013 at 12:48 AM, Thomas Ward wrote: >>> >>> Rohan, >>> >>> On Thu, Aug 29, 2013 at 3:08 PM, Thomas Ward wrote: >>>> >>>> I took a look at that bug, the bug went inactive because it had no activity or updates when the bug was marked "Incomplete". Since the original poster and nobody else provided any additional information the bug auto expired. >>>> >>>> I can try confirming this bug, however if I remember when I was configuring sks back in the days of 11.04 and 11.10, you had to configure it before you could actually start or restart the sks process. >>>> >>>> I'll take a look and see if I can reproduce, but there's probably logs somewhere for sks explaining why it didn't start or such. >>>> >>>> I'll check back with this in a little bit after I've done some testing. >>>> >>>> ------ >>>> Thomas >>>> Ubuntu Member >>>> Bug Squad Member >>>> >>>> >>>> On Thu, Aug 29, 2013 at 7:56 AM, rohan dighe wrote: >>>>> >>>>> Hi Team, >>>>> >>>>> I am working on setting up a gpg key server on ubuntu server,but facing some issue as the init script of sks has some bug.when I set up the gpg key server and starts sks service >>>>> >>>>> I get the below output on command prompt its shows service running but its actually not running and also I cant get the pid process of sks service showing running. >>>>> >>>>> root at tripwiretest: sks]# /etc/init.d/sks start >>>>> Starting sks daemons: sksdb.. sksrecon.. done. >>>>> >>>>> The ubuntu showing the bug on this link. >>>>> >>>>> https://bugs.launchpad.net/ubuntu/+source/sks/+bug/820354 >>>>> >>>>> I also followed the solution given on the link but with no success. >>>>> >>>>> As the sks comes from the ubuntu 12.04 repository do we have any permanent fix for the init script of sks. >>>>> >>>>> Please help me regarding the init script of sks. >>>>> >>>>> Thanks, >>>>> Rohan >>>>> >>>>> -- >>>>> Ubuntu-bugsquad mailing list >>>>> Ubuntu-bugsquad at lists.ubuntu.com >>>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad >>>>> >>>> >>> >>> Using a properly configured 'sks' instance, I am unable to reproduce this bug, and using the init.d script correctly launches the two sks processes, one for the DB, one for recon. >>> >>> Also, the package 'sks' does not by default set up the key database or other items just by installing. Did you actually configure 'sks' first before attempting to run it with the init script? >>> >>> ------ >>> Thomas >>> >> > > Typically, when I configured sks on several systems, I always had to > do this step to get the key db built after installing, then afterwards > I chown'd /var/lib/sks/DB: sudo sks build > > Did you run the build command for sks before attempting to launch sks? > If you did that and are still getting this error, then perhaps we > should purge sks from your system and start anew? This link here [1] > was able to help me get a brand new sks instance set up correctly > without incident, though, and it correctly runs the sks process and > builds the key database so it works. > > [1] https://kura.io/2011/12/17/running-your-own-pgp-keyserver-with-sks-on-debian-6ubuntu-10-04/ > > ------ > Thomas From teward at ubuntu.com Fri Aug 30 17:03:53 2013 From: teward at ubuntu.com (Thomas Ward) Date: Fri, 30 Aug 2013 13:03:53 -0400 Subject: sks init script bug in ubuntu 12.04 In-Reply-To: References: Message-ID: I'm... confused by why they're having you create a directory... The tutorial you linked has this: >Edit /etc/init.d/sks to automatically create the/var/run/sks directory on startup. >At (approx) line 71 (after the check for /etc/default/sks & before 'echo -n "sksdb.."') add >mkdir -p `dirname "$SKSDBPID"` >chown debian-sks `dirname "$SKSDBPID"` I'm a little confused by why they have you do this. The init script that already exists already does this in Precise. (http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/sks/precise-updates/view/head:/debian/sks.init#L71) So, because I'm completely unsure of whether what they're doing works or not, give me a minute to spin up a new server instance and test this with the tutorial you linked... I think they did something wonky somewhere... ------ Thomas On Fri, Aug 30, 2013 at 12:46 PM, rohan dighe wrote: > Hi Thomas, > > Thanks for sending me the link for setup of the sks,and yes i did run the > sks build command on the server while configuring sks server.But still > getting the error. > > I followed the below link on how to setup the sks server. > > http://www.rainydayz.org/content/installing-opensks-keyserver > > > > > On Fri, Aug 30, 2013 at 9:50 PM, Thomas Ward wrote: >> >> Rohan, >> >> On Fri, Aug 30, 2013 at 10:04 AM, rohan dighe >> wrote: >> > >> > >> > Hi Team, >> > >> > Thanks for the immediate response I really appreciate your efforts on >> > providing me the solution for sks server. >> > >> > Here are the steps I am following to setup the sks server on ubuntu >> > 12.04 >> > >> > # aptitude install sks >> > >> > Set database permissions on the database used by sks to store keys >> > >> > # chown -Rc debian-sks:debian-sks /var/lib/sks/DB >> > >> > To start the server automatically, set initstart=yes in /etc/default/sks >> > >> > # Here I start the sks service >> > >> > # /etc/init.d/sks start >> > Stopping sks daemons: sksrecon..start-stop-daemon: warning: failed to >> > kill 31643: No such process >> > sksdb..start-stop-daemon: warning: failed to kill 31640: No such process >> > done. >> > >> > Starting sks daemons: sksdb.. sksrecon.. done. >> > >> > Then I configure webinterface for sks >> > >> > I install the sks winzip from internet >> > >> > Then I created a www directory in /var/lib/sks >> > >> > unzip the sks in /var/lib/sks/www folder >> > >> > After that 2 files gets downloaded in /var/lib/sks/www folder. >> > >> > 1) index.html >> > >> > 2) keys.jpg >> > >> > I Edit index.html and change the three references to your.site.name >> > (currently at lines 20, 36 & 62) to the url of your keyserver) ( In my case >> > its my server ip ) >> > >> > Then I change the permission on the files >> > >> > # chown -R debian-sks:debian-sks /var/lib/sks/www >> > >> > After that when I tried to browse http://myserverip:11371 its not >> > working. >> > >> > I also tried to get the pid of the sks but the pid is not running on the >> > server below is the given output. >> > >> > # ps -aufx | grep sks >> > Warning: bad ps syntax, perhaps a bogus '-'? See >> > http://procps.sf.net/faq.html >> > root 31950 0.0 0.0 9384 900 pts/1 S+ 19:26 0:00 \_ grep --color=auto sks >> > >> > Here I cant see the 2 process running for sks one for the DB, one for >> > recon. >> > >> > The ps output shows here that sks pid is not running ,It will be helpful >> > if you let me know where exact the problem lies in sks. >> > >> > >> > Thanks, >> > Rohan >> > >> > On Fri, Aug 30, 2013 at 12:48 AM, Thomas Ward wrote: >> >> >> >> Rohan, >> >> >> >> On Thu, Aug 29, 2013 at 3:08 PM, Thomas Ward wrote: >> >>> >> >>> I took a look at that bug, the bug went inactive because it had no >> >>> activity or updates when the bug was marked "Incomplete". Since the >> >>> original poster and nobody else provided any additional information the bug >> >>> auto expired. >> >>> >> >>> I can try confirming this bug, however if I remember when I was >> >>> configuring sks back in the days of 11.04 and 11.10, you had to configure it >> >>> before you could actually start or restart the sks process. >> >>> >> >>> I'll take a look and see if I can reproduce, but there's probably logs >> >>> somewhere for sks explaining why it didn't start or such. >> >>> >> >>> I'll check back with this in a little bit after I've done some >> >>> testing. >> >>> >> >>> ------ >> >>> Thomas >> >>> Ubuntu Member >> >>> Bug Squad Member >> >>> >> >>> >> >>> On Thu, Aug 29, 2013 at 7:56 AM, rohan dighe >> >>> wrote: >> >>>> >> >>>> Hi Team, >> >>>> >> >>>> I am working on setting up a gpg key server on ubuntu server,but >> >>>> facing some issue as the init script of sks has some bug.when I set up the >> >>>> gpg key server and starts sks service >> >>>> >> >>>> I get the below output on command prompt its shows service running >> >>>> but its actually not running and also I cant get the pid process of sks >> >>>> service showing running. >> >>>> >> >>>> root at tripwiretest: sks]# /etc/init.d/sks start >> >>>> Starting sks daemons: sksdb.. sksrecon.. done. >> >>>> >> >>>> The ubuntu showing the bug on this link. >> >>>> >> >>>> https://bugs.launchpad.net/ubuntu/+source/sks/+bug/820354 >> >>>> >> >>>> I also followed the solution given on the link but with no success. >> >>>> >> >>>> As the sks comes from the ubuntu 12.04 repository do we have any >> >>>> permanent fix for the init script of sks. >> >>>> >> >>>> Please help me regarding the init script of sks. >> >>>> >> >>>> Thanks, >> >>>> Rohan >> >>>> >> >>>> -- >> >>>> Ubuntu-bugsquad mailing list >> >>>> Ubuntu-bugsquad at lists.ubuntu.com >> >>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad >> >>>> >> >>> >> >> >> >> Using a properly configured 'sks' instance, I am unable to reproduce >> >> this bug, and using the init.d script correctly launches the two sks >> >> processes, one for the DB, one for recon. >> >> >> >> Also, the package 'sks' does not by default set up the key database or >> >> other items just by installing. Did you actually configure 'sks' first >> >> before attempting to run it with the init script? >> >> >> >> ------ >> >> Thomas >> >> >> > >> >> Typically, when I configured sks on several systems, I always had to >> do this step to get the key db built after installing, then afterwards >> I chown'd /var/lib/sks/DB: sudo sks build >> >> Did you run the build command for sks before attempting to launch sks? >> If you did that and are still getting this error, then perhaps we >> should purge sks from your system and start anew? This link here [1] >> was able to help me get a brand new sks instance set up correctly >> without incident, though, and it correctly runs the sks process and >> builds the key database so it works. >> >> [1] >> https://kura.io/2011/12/17/running-your-own-pgp-keyserver-with-sks-on-debian-6ubuntu-10-04/ >> >> ------ >> Thomas > > From teward at ubuntu.com Fri Aug 30 17:38:40 2013 From: teward at ubuntu.com (Thomas Ward) Date: Fri, 30 Aug 2013 13:38:40 -0400 Subject: sks init script bug in ubuntu 12.04 In-Reply-To: References: Message-ID: Rohan, On Fri, Aug 30, 2013 at 1:16 PM, rohan dighe wrote: > > Hi Thomas, > > I did check the /etc/init.d/sks directory and found that the code >Edit > /etc/init.d/sks to automatically create the/var/run/sks directory on > startup. > >>At (approx) line 71 (after the check for /etc/default/sks & before 'echo -n >> "sksdb.."') add >>mkdir -p `dirname "$SKSDBPID"` >>chown debian-sks `dirname "$SKSDBPID"` > > Was present in the init script of sks so I skip that configuration and also > I skip the configuration In /etc/cron.daily/sks change db4.1_archive to > db4.6_archive.mentioned in that link. > > and tried to configure the setup.but still not able to configure sks. > > I really appreciate your efforts. > > > > > On Fri, Aug 30, 2013 at 10:33 PM, Thomas Ward wrote: >> >> I'm... confused by why they're having you create a directory... >> >> The tutorial you linked has this: >> >> >Edit /etc/init.d/sks to automatically create the/var/run/sks directory on >> > startup. >> >At (approx) line 71 (after the check for /etc/default/sks & before 'echo >> > -n "sksdb.."') add >> >mkdir -p `dirname "$SKSDBPID"` >> >chown debian-sks `dirname "$SKSDBPID"` >> >> I'm a little confused by why they have you do this. The init script >> that already exists already does this in Precise. >> >> (http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/sks/precise-updates/view/head:/debian/sks.init#L71) >> >> So, because I'm completely unsure of whether what they're doing works >> or not, give me a minute to spin up a new server instance and test >> this with the tutorial you linked... I think they did something wonky >> somewhere... >> >> ------ >> Thomas >> >> On Fri, Aug 30, 2013 at 12:46 PM, rohan dighe >> wrote: >> > Hi Thomas, >> > >> > Thanks for sending me the link for setup of the sks,and yes i did run >> > the >> > sks build command on the server while configuring sks server.But still >> > getting the error. >> > >> > I followed the below link on how to setup the sks server. >> > >> > http://www.rainydayz.org/content/installing-opensks-keyserver >> > >> > >> > >> > >> > On Fri, Aug 30, 2013 at 9:50 PM, Thomas Ward wrote: >> >> >> >> Rohan, >> >> >> >> On Fri, Aug 30, 2013 at 10:04 AM, rohan dighe >> >> wrote: >> >> > >> >> > >> >> > Hi Team, >> >> > >> >> > Thanks for the immediate response I really appreciate your efforts on >> >> > providing me the solution for sks server. >> >> > >> >> > Here are the steps I am following to setup the sks server on ubuntu >> >> > 12.04 >> >> > >> >> > # aptitude install sks >> >> > >> >> > Set database permissions on the database used by sks to store keys >> >> > >> >> > # chown -Rc debian-sks:debian-sks /var/lib/sks/DB >> >> > >> >> > To start the server automatically, set initstart=yes in >> >> > /etc/default/sks >> >> > >> >> > # Here I start the sks service >> >> > >> >> > # /etc/init.d/sks start >> >> > Stopping sks daemons: sksrecon..start-stop-daemon: warning: failed to >> >> > kill 31643: No such process >> >> > sksdb..start-stop-daemon: warning: failed to kill 31640: No such >> >> > process >> >> > done. >> >> > >> >> > Starting sks daemons: sksdb.. sksrecon.. done. >> >> > >> >> > Then I configure webinterface for sks >> >> > >> >> > I install the sks winzip from internet >> >> > >> >> > Then I created a www directory in /var/lib/sks >> >> > >> >> > unzip the sks in /var/lib/sks/www folder >> >> > >> >> > After that 2 files gets downloaded in /var/lib/sks/www folder. >> >> > >> >> > 1) index.html >> >> > >> >> > 2) keys.jpg >> >> > >> >> > I Edit index.html and change the three references to your.site.name >> >> > (currently at lines 20, 36 & 62) to the url of your keyserver) ( In >> >> > my case >> >> > its my server ip ) >> >> > >> >> > Then I change the permission on the files >> >> > >> >> > # chown -R debian-sks:debian-sks /var/lib/sks/www >> >> > >> >> > After that when I tried to browse http://myserverip:11371 its not >> >> > working. >> >> > >> >> > I also tried to get the pid of the sks but the pid is not running on >> >> > the >> >> > server below is the given output. >> >> > >> >> > # ps -aufx | grep sks >> >> > Warning: bad ps syntax, perhaps a bogus '-'? See >> >> > http://procps.sf.net/faq.html >> >> > root 31950 0.0 0.0 9384 900 pts/1 S+ 19:26 0:00 \_ grep --color=auto >> >> > sks >> >> > >> >> > Here I cant see the 2 process running for sks one for the DB, one for >> >> > recon. >> >> > >> >> > The ps output shows here that sks pid is not running ,It will be >> >> > helpful >> >> > if you let me know where exact the problem lies in sks. >> >> > >> >> > >> >> > Thanks, >> >> > Rohan >> >> > >> >> > On Fri, Aug 30, 2013 at 12:48 AM, Thomas Ward >> >> > wrote: >> >> >> >> >> >> Rohan, >> >> >> >> >> >> On Thu, Aug 29, 2013 at 3:08 PM, Thomas Ward >> >> >> wrote: >> >> >>> >> >> >>> I took a look at that bug, the bug went inactive because it had no >> >> >>> activity or updates when the bug was marked "Incomplete". Since >> >> >>> the >> >> >>> original poster and nobody else provided any additional information >> >> >>> the bug >> >> >>> auto expired. >> >> >>> >> >> >>> I can try confirming this bug, however if I remember when I was >> >> >>> configuring sks back in the days of 11.04 and 11.10, you had to >> >> >>> configure it >> >> >>> before you could actually start or restart the sks process. >> >> >>> >> >> >>> I'll take a look and see if I can reproduce, but there's probably >> >> >>> logs >> >> >>> somewhere for sks explaining why it didn't start or such. >> >> >>> >> >> >>> I'll check back with this in a little bit after I've done some >> >> >>> testing. >> >> >>> >> >> >>> ------ >> >> >>> Thomas >> >> >>> Ubuntu Member >> >> >>> Bug Squad Member >> >> >>> >> >> >>> >> >> >>> On Thu, Aug 29, 2013 at 7:56 AM, rohan dighe >> >> >>> >> >> >>> wrote: >> >> >>>> >> >> >>>> Hi Team, >> >> >>>> >> >> >>>> I am working on setting up a gpg key server on ubuntu server,but >> >> >>>> facing some issue as the init script of sks has some bug.when I >> >> >>>> set up the >> >> >>>> gpg key server and starts sks service >> >> >>>> >> >> >>>> I get the below output on command prompt its shows service running >> >> >>>> but its actually not running and also I cant get the pid process >> >> >>>> of sks >> >> >>>> service showing running. >> >> >>>> >> >> >>>> root at tripwiretest: sks]# /etc/init.d/sks start >> >> >>>> Starting sks daemons: sksdb.. sksrecon.. done. >> >> >>>> >> >> >>>> The ubuntu showing the bug on this link. >> >> >>>> >> >> >>>> https://bugs.launchpad.net/ubuntu/+source/sks/+bug/820354 >> >> >>>> >> >> >>>> I also followed the solution given on the link but with no >> >> >>>> success. >> >> >>>> >> >> >>>> As the sks comes from the ubuntu 12.04 repository do we have any >> >> >>>> permanent fix for the init script of sks. >> >> >>>> >> >> >>>> Please help me regarding the init script of sks. >> >> >>>> >> >> >>>> Thanks, >> >> >>>> Rohan >> >> >>>> >> >> >>>> -- >> >> >>>> Ubuntu-bugsquad mailing list >> >> >>>> Ubuntu-bugsquad at lists.ubuntu.com >> >> >>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad >> >> >>>> >> >> >>> >> >> >> >> >> >> Using a properly configured 'sks' instance, I am unable to reproduce >> >> >> this bug, and using the init.d script correctly launches the two sks >> >> >> processes, one for the DB, one for recon. >> >> >> >> >> >> Also, the package 'sks' does not by default set up the key database >> >> >> or >> >> >> other items just by installing. Did you actually configure 'sks' >> >> >> first >> >> >> before attempting to run it with the init script? >> >> >> >> >> >> ------ >> >> >> Thomas >> >> >> >> >> > >> >> >> >> Typically, when I configured sks on several systems, I always had to >> >> do this step to get the key db built after installing, then afterwards >> >> I chown'd /var/lib/sks/DB: sudo sks build >> >> >> >> Did you run the build command for sks before attempting to launch sks? >> >> If you did that and are still getting this error, then perhaps we >> >> should purge sks from your system and start anew? This link here [1] >> >> was able to help me get a brand new sks instance set up correctly >> >> without incident, though, and it correctly runs the sks process and >> >> builds the key database so it works. >> >> >> >> [1] >> >> >> >> https://kura.io/2011/12/17/running-your-own-pgp-keyserver-with-sks-on-debian-6ubuntu-10-04/ >> >> >> >> ------ >> >> Thomas >> > >> > > > Okay, I tested using the link that you provided and also tested with the link I provided. The link you provided asks you to run `sudo sks db` after you've build the key database. I'm not entirely certain, however I think that command, and then later closing out of it, is somehow causing it to break. I am drawing this conclusion because in one tutorial I don't run `sudo sks db` and it correctly launches later. So, let's start from the beginning, doing everything in your tutorial *but* running `sudo sks db` after building it, but using these steps to get it to launch, then using the rest of the tutorial for the web interface, and see if that works: (1) sudo apt-get purge sks (2) sudo apt-get install sks (3) sudo sks build (4) sudo chown -R debian-sks:debian-sks /var/lib/sks/DB (5) sudo nano /etc/default/sks (change initstart to "yes") (6) sudo /etc/init.d/sks start (7) sudo pidof sks (should show PIDs now) ------ Thomas From rohandighe18 at gmail.com Fri Aug 30 16:46:51 2013 From: rohandighe18 at gmail.com (rohan dighe) Date: Fri, 30 Aug 2013 22:16:51 +0530 Subject: sks init script bug in ubuntu 12.04 In-Reply-To: References: Message-ID: Hi Thomas, Thanks for sending me the link for setup of the sks,and yes i did run the sks build command on the server while configuring sks server.But still getting the error. I followed the below link on how to setup the sks server. http://www.rainydayz.org/content/installing-opensks-keyserver On Fri, Aug 30, 2013 at 9:50 PM, Thomas Ward wrote: > Rohan, > > On Fri, Aug 30, 2013 at 10:04 AM, rohan dighe > wrote: > > > > > > Hi Team, > > > > Thanks for the immediate response I really appreciate your efforts on > providing me the solution for sks server. > > > > Here are the steps I am following to setup the sks server on ubuntu 12.04 > > > > # aptitude install sks > > > > Set database permissions on the database used by sks to store keys > > > > # chown -Rc debian-sks:debian-sks /var/lib/sks/DB > > > > To start the server automatically, set initstart=yes in /etc/default/sks > > > > # Here I start the sks service > > > > # /etc/init.d/sks start > > Stopping sks daemons: sksrecon..start-stop-daemon: warning: failed to > kill 31643: No such process > > sksdb..start-stop-daemon: warning: failed to kill 31640: No such process > > done. > > > > Starting sks daemons: sksdb.. sksrecon.. done. > > > > Then I configure webinterface for sks > > > > I install the sks winzip from internet > > > > Then I created a www directory in /var/lib/sks > > > > unzip the sks in /var/lib/sks/www folder > > > > After that 2 files gets downloaded in /var/lib/sks/www folder. > > > > 1) index.html > > > > 2) keys.jpg > > > > I Edit index.html and change the three references to your.site.name(currently at lines 20, 36 & 62) to the url of your keyserver) ( In my case > its my server ip ) > > > > Then I change the permission on the files > > > > # chown -R debian-sks:debian-sks /var/lib/sks/www > > > > After that when I tried to browse http://myserverip:11371 its not > working. > > > > I also tried to get the pid of the sks but the pid is not running on the > server below is the given output. > > > > # ps -aufx | grep sks > > Warning: bad ps syntax, perhaps a bogus '-'? See > http://procps.sf.net/faq.html > > root 31950 0.0 0.0 9384 900 pts/1 S+ 19:26 0:00 \_ grep --color=auto sks > > > > Here I cant see the 2 process running for sks one for the DB, one for > recon. > > > > The ps output shows here that sks pid is not running ,It will be helpful > if you let me know where exact the problem lies in sks. > > > > > > Thanks, > > Rohan > > > > On Fri, Aug 30, 2013 at 12:48 AM, Thomas Ward wrote: > >> > >> Rohan, > >> > >> On Thu, Aug 29, 2013 at 3:08 PM, Thomas Ward wrote: > >>> > >>> I took a look at that bug, the bug went inactive because it had no > activity or updates when the bug was marked "Incomplete". Since the > original poster and nobody else provided any additional information the bug > auto expired. > >>> > >>> I can try confirming this bug, however if I remember when I was > configuring sks back in the days of 11.04 and 11.10, you had to configure > it before you could actually start or restart the sks process. > >>> > >>> I'll take a look and see if I can reproduce, but there's probably logs > somewhere for sks explaining why it didn't start or such. > >>> > >>> I'll check back with this in a little bit after I've done some testing. > >>> > >>> ------ > >>> Thomas > >>> Ubuntu Member > >>> Bug Squad Member > >>> > >>> > >>> On Thu, Aug 29, 2013 at 7:56 AM, rohan dighe > wrote: > >>>> > >>>> Hi Team, > >>>> > >>>> I am working on setting up a gpg key server on ubuntu server,but > facing some issue as the init script of sks has some bug.when I set up the > gpg key server and starts sks service > >>>> > >>>> I get the below output on command prompt its shows service running > but its actually not running and also I cant get the pid process of sks > service showing running. > >>>> > >>>> root at tripwiretest: sks]# /etc/init.d/sks start > >>>> Starting sks daemons: sksdb.. sksrecon.. done. > >>>> > >>>> The ubuntu showing the bug on this link. > >>>> > >>>> https://bugs.launchpad.net/ubuntu/+source/sks/+bug/820354 > >>>> > >>>> I also followed the solution given on the link but with no success. > >>>> > >>>> As the sks comes from the ubuntu 12.04 repository do we have any > permanent fix for the init script of sks. > >>>> > >>>> Please help me regarding the init script of sks. > >>>> > >>>> Thanks, > >>>> Rohan > >>>> > >>>> -- > >>>> Ubuntu-bugsquad mailing list > >>>> Ubuntu-bugsquad at lists.ubuntu.com > >>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > >>>> > >>> > >> > >> Using a properly configured 'sks' instance, I am unable to reproduce > this bug, and using the init.d script correctly launches the two sks > processes, one for the DB, one for recon. > >> > >> Also, the package 'sks' does not by default set up the key database or > other items just by installing. Did you actually configure 'sks' first > before attempting to run it with the init script? > >> > >> ------ > >> Thomas > >> > > > > Typically, when I configured sks on several systems, I always had to > do this step to get the key db built after installing, then afterwards > I chown'd /var/lib/sks/DB: sudo sks build > > Did you run the build command for sks before attempting to launch sks? > If you did that and are still getting this error, then perhaps we > should purge sks from your system and start anew? This link here [1] > was able to help me get a brand new sks instance set up correctly > without incident, though, and it correctly runs the sks process and > builds the key database so it works. > > [1] > https://kura.io/2011/12/17/running-your-own-pgp-keyserver-with-sks-on-debian-6ubuntu-10-04/ > > ------ > Thomas > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rohandighe18 at gmail.com Fri Aug 30 17:16:06 2013 From: rohandighe18 at gmail.com (rohan dighe) Date: Fri, 30 Aug 2013 22:46:06 +0530 Subject: sks init script bug in ubuntu 12.04 In-Reply-To: References: Message-ID: Hi Thomas, I did check the /etc/init.d/sks directory and found that the code >Edit /etc/init.d/sks to automatically create the/var/run/sks directory on startup. >At (approx) line 71 (after the check for /etc/default/sks & before 'echo -n "sksdb.."') add >mkdir -p `dirname "$SKSDBPID"` >chown debian-sks `dirname "$SKSDBPID"` Was present in the init script of sks so I skip that configuration and also I skip the configuration In */etc/cron.daily/sks* change *db4.1_archive*to *db4.6_archive*.mentioned in that link. and tried to configure the setup.but still not able to configure sks. I really appreciate your efforts. On Fri, Aug 30, 2013 at 10:33 PM, Thomas Ward wrote: > I'm... confused by why they're having you create a directory... > > The tutorial you linked has this: > > >Edit /etc/init.d/sks to automatically create the/var/run/sks directory on > startup. > >At (approx) line 71 (after the check for /etc/default/sks & before 'echo > -n "sksdb.."') add > >mkdir -p `dirname "$SKSDBPID"` > >chown debian-sks `dirname "$SKSDBPID"` > > I'm a little confused by why they have you do this. The init script > that already exists already does this in Precise. > ( > http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/sks/precise-updates/view/head:/debian/sks.init#L71 > ) > > So, because I'm completely unsure of whether what they're doing works > or not, give me a minute to spin up a new server instance and test > this with the tutorial you linked... I think they did something wonky > somewhere... > > ------ > Thomas > > On Fri, Aug 30, 2013 at 12:46 PM, rohan dighe > wrote: > > Hi Thomas, > > > > Thanks for sending me the link for setup of the sks,and yes i did run the > > sks build command on the server while configuring sks server.But still > > getting the error. > > > > I followed the below link on how to setup the sks server. > > > > http://www.rainydayz.org/content/installing-opensks-keyserver > > > > > > > > > > On Fri, Aug 30, 2013 at 9:50 PM, Thomas Ward wrote: > >> > >> Rohan, > >> > >> On Fri, Aug 30, 2013 at 10:04 AM, rohan dighe > >> wrote: > >> > > >> > > >> > Hi Team, > >> > > >> > Thanks for the immediate response I really appreciate your efforts on > >> > providing me the solution for sks server. > >> > > >> > Here are the steps I am following to setup the sks server on ubuntu > >> > 12.04 > >> > > >> > # aptitude install sks > >> > > >> > Set database permissions on the database used by sks to store keys > >> > > >> > # chown -Rc debian-sks:debian-sks /var/lib/sks/DB > >> > > >> > To start the server automatically, set initstart=yes in > /etc/default/sks > >> > > >> > # Here I start the sks service > >> > > >> > # /etc/init.d/sks start > >> > Stopping sks daemons: sksrecon..start-stop-daemon: warning: failed to > >> > kill 31643: No such process > >> > sksdb..start-stop-daemon: warning: failed to kill 31640: No such > process > >> > done. > >> > > >> > Starting sks daemons: sksdb.. sksrecon.. done. > >> > > >> > Then I configure webinterface for sks > >> > > >> > I install the sks winzip from internet > >> > > >> > Then I created a www directory in /var/lib/sks > >> > > >> > unzip the sks in /var/lib/sks/www folder > >> > > >> > After that 2 files gets downloaded in /var/lib/sks/www folder. > >> > > >> > 1) index.html > >> > > >> > 2) keys.jpg > >> > > >> > I Edit index.html and change the three references to your.site.name > >> > (currently at lines 20, 36 & 62) to the url of your keyserver) ( In > my case > >> > its my server ip ) > >> > > >> > Then I change the permission on the files > >> > > >> > # chown -R debian-sks:debian-sks /var/lib/sks/www > >> > > >> > After that when I tried to browse http://myserverip:11371 its not > >> > working. > >> > > >> > I also tried to get the pid of the sks but the pid is not running on > the > >> > server below is the given output. > >> > > >> > # ps -aufx | grep sks > >> > Warning: bad ps syntax, perhaps a bogus '-'? See > >> > http://procps.sf.net/faq.html > >> > root 31950 0.0 0.0 9384 900 pts/1 S+ 19:26 0:00 \_ grep --color=auto > sks > >> > > >> > Here I cant see the 2 process running for sks one for the DB, one for > >> > recon. > >> > > >> > The ps output shows here that sks pid is not running ,It will be > helpful > >> > if you let me know where exact the problem lies in sks. > >> > > >> > > >> > Thanks, > >> > Rohan > >> > > >> > On Fri, Aug 30, 2013 at 12:48 AM, Thomas Ward > wrote: > >> >> > >> >> Rohan, > >> >> > >> >> On Thu, Aug 29, 2013 at 3:08 PM, Thomas Ward > wrote: > >> >>> > >> >>> I took a look at that bug, the bug went inactive because it had no > >> >>> activity or updates when the bug was marked "Incomplete". Since the > >> >>> original poster and nobody else provided any additional information > the bug > >> >>> auto expired. > >> >>> > >> >>> I can try confirming this bug, however if I remember when I was > >> >>> configuring sks back in the days of 11.04 and 11.10, you had to > configure it > >> >>> before you could actually start or restart the sks process. > >> >>> > >> >>> I'll take a look and see if I can reproduce, but there's probably > logs > >> >>> somewhere for sks explaining why it didn't start or such. > >> >>> > >> >>> I'll check back with this in a little bit after I've done some > >> >>> testing. > >> >>> > >> >>> ------ > >> >>> Thomas > >> >>> Ubuntu Member > >> >>> Bug Squad Member > >> >>> > >> >>> > >> >>> On Thu, Aug 29, 2013 at 7:56 AM, rohan dighe < > rohandighe18 at gmail.com> > >> >>> wrote: > >> >>>> > >> >>>> Hi Team, > >> >>>> > >> >>>> I am working on setting up a gpg key server on ubuntu server,but > >> >>>> facing some issue as the init script of sks has some bug.when I > set up the > >> >>>> gpg key server and starts sks service > >> >>>> > >> >>>> I get the below output on command prompt its shows service running > >> >>>> but its actually not running and also I cant get the pid process > of sks > >> >>>> service showing running. > >> >>>> > >> >>>> root at tripwiretest: sks]# /etc/init.d/sks start > >> >>>> Starting sks daemons: sksdb.. sksrecon.. done. > >> >>>> > >> >>>> The ubuntu showing the bug on this link. > >> >>>> > >> >>>> https://bugs.launchpad.net/ubuntu/+source/sks/+bug/820354 > >> >>>> > >> >>>> I also followed the solution given on the link but with no success. > >> >>>> > >> >>>> As the sks comes from the ubuntu 12.04 repository do we have any > >> >>>> permanent fix for the init script of sks. > >> >>>> > >> >>>> Please help me regarding the init script of sks. > >> >>>> > >> >>>> Thanks, > >> >>>> Rohan > >> >>>> > >> >>>> -- > >> >>>> Ubuntu-bugsquad mailing list > >> >>>> Ubuntu-bugsquad at lists.ubuntu.com > >> >>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > >> >>>> > >> >>> > >> >> > >> >> Using a properly configured 'sks' instance, I am unable to reproduce > >> >> this bug, and using the init.d script correctly launches the two sks > >> >> processes, one for the DB, one for recon. > >> >> > >> >> Also, the package 'sks' does not by default set up the key database > or > >> >> other items just by installing. Did you actually configure 'sks' > first > >> >> before attempting to run it with the init script? > >> >> > >> >> ------ > >> >> Thomas > >> >> > >> > > >> > >> Typically, when I configured sks on several systems, I always had to > >> do this step to get the key db built after installing, then afterwards > >> I chown'd /var/lib/sks/DB: sudo sks build > >> > >> Did you run the build command for sks before attempting to launch sks? > >> If you did that and are still getting this error, then perhaps we > >> should purge sks from your system and start anew? This link here [1] > >> was able to help me get a brand new sks instance set up correctly > >> without incident, though, and it correctly runs the sks process and > >> builds the key database so it works. > >> > >> [1] > >> > https://kura.io/2011/12/17/running-your-own-pgp-keyserver-with-sks-on-debian-6ubuntu-10-04/ > >> > >> ------ > >> Thomas > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From teward at ubuntu.com Fri Aug 30 17:42:13 2013 From: teward at ubuntu.com (Thomas Ward) Date: Fri, 30 Aug 2013 13:42:13 -0400 Subject: sks init script bug in ubuntu 12.04 In-Reply-To: References: Message-ID: Oh, I miswrote those steps. Use these: (1) sudo apt-get purge sks (2) sudo rm -rf /var/lib/sks (3) sudo apt-get install sks (4) sudo sks build (5) sudo chown -R debian-sks:debian-sks /var/lib/sks/DB (6) sudo nano /etc/default/sks (change initstart to "yes") (7) sudo /etc/init.d/sks start (8) sudo pidof sks (should show PIDs now) On Fri, Aug 30, 2013 at 1:38 PM, Thomas Ward wrote: > Rohan, > > On Fri, Aug 30, 2013 at 1:16 PM, rohan dighe wrote: >> >> Hi Thomas, >> >> I did check the /etc/init.d/sks directory and found that the code >Edit >> /etc/init.d/sks to automatically create the/var/run/sks directory on >> startup. >> >>>At (approx) line 71 (after the check for /etc/default/sks & before 'echo -n >>> "sksdb.."') add >>>mkdir -p `dirname "$SKSDBPID"` >>>chown debian-sks `dirname "$SKSDBPID"` >> >> Was present in the init script of sks so I skip that configuration and also >> I skip the configuration In /etc/cron.daily/sks change db4.1_archive to >> db4.6_archive.mentioned in that link. >> >> and tried to configure the setup.but still not able to configure sks. >> >> I really appreciate your efforts. >> >> >> >> >> On Fri, Aug 30, 2013 at 10:33 PM, Thomas Ward wrote: >>> >>> I'm... confused by why they're having you create a directory... >>> >>> The tutorial you linked has this: >>> >>> >Edit /etc/init.d/sks to automatically create the/var/run/sks directory on >>> > startup. >>> >At (approx) line 71 (after the check for /etc/default/sks & before 'echo >>> > -n "sksdb.."') add >>> >mkdir -p `dirname "$SKSDBPID"` >>> >chown debian-sks `dirname "$SKSDBPID"` >>> >>> I'm a little confused by why they have you do this. The init script >>> that already exists already does this in Precise. >>> >>> (http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/sks/precise-updates/view/head:/debian/sks.init#L71) >>> >>> So, because I'm completely unsure of whether what they're doing works >>> or not, give me a minute to spin up a new server instance and test >>> this with the tutorial you linked... I think they did something wonky >>> somewhere... >>> >>> ------ >>> Thomas >>> >>> On Fri, Aug 30, 2013 at 12:46 PM, rohan dighe >>> wrote: >>> > Hi Thomas, >>> > >>> > Thanks for sending me the link for setup of the sks,and yes i did run >>> > the >>> > sks build command on the server while configuring sks server.But still >>> > getting the error. >>> > >>> > I followed the below link on how to setup the sks server. >>> > >>> > http://www.rainydayz.org/content/installing-opensks-keyserver >>> > >>> > >>> > >>> > >>> > On Fri, Aug 30, 2013 at 9:50 PM, Thomas Ward wrote: >>> >> >>> >> Rohan, >>> >> >>> >> On Fri, Aug 30, 2013 at 10:04 AM, rohan dighe >>> >> wrote: >>> >> > >>> >> > >>> >> > Hi Team, >>> >> > >>> >> > Thanks for the immediate response I really appreciate your efforts on >>> >> > providing me the solution for sks server. >>> >> > >>> >> > Here are the steps I am following to setup the sks server on ubuntu >>> >> > 12.04 >>> >> > >>> >> > # aptitude install sks >>> >> > >>> >> > Set database permissions on the database used by sks to store keys >>> >> > >>> >> > # chown -Rc debian-sks:debian-sks /var/lib/sks/DB >>> >> > >>> >> > To start the server automatically, set initstart=yes in >>> >> > /etc/default/sks >>> >> > >>> >> > # Here I start the sks service >>> >> > >>> >> > # /etc/init.d/sks start >>> >> > Stopping sks daemons: sksrecon..start-stop-daemon: warning: failed to >>> >> > kill 31643: No such process >>> >> > sksdb..start-stop-daemon: warning: failed to kill 31640: No such >>> >> > process >>> >> > done. >>> >> > >>> >> > Starting sks daemons: sksdb.. sksrecon.. done. >>> >> > >>> >> > Then I configure webinterface for sks >>> >> > >>> >> > I install the sks winzip from internet >>> >> > >>> >> > Then I created a www directory in /var/lib/sks >>> >> > >>> >> > unzip the sks in /var/lib/sks/www folder >>> >> > >>> >> > After that 2 files gets downloaded in /var/lib/sks/www folder. >>> >> > >>> >> > 1) index.html >>> >> > >>> >> > 2) keys.jpg >>> >> > >>> >> > I Edit index.html and change the three references to your.site.name >>> >> > (currently at lines 20, 36 & 62) to the url of your keyserver) ( In >>> >> > my case >>> >> > its my server ip ) >>> >> > >>> >> > Then I change the permission on the files >>> >> > >>> >> > # chown -R debian-sks:debian-sks /var/lib/sks/www >>> >> > >>> >> > After that when I tried to browse http://myserverip:11371 its not >>> >> > working. >>> >> > >>> >> > I also tried to get the pid of the sks but the pid is not running on >>> >> > the >>> >> > server below is the given output. >>> >> > >>> >> > # ps -aufx | grep sks >>> >> > Warning: bad ps syntax, perhaps a bogus '-'? See >>> >> > http://procps.sf.net/faq.html >>> >> > root 31950 0.0 0.0 9384 900 pts/1 S+ 19:26 0:00 \_ grep --color=auto >>> >> > sks >>> >> > >>> >> > Here I cant see the 2 process running for sks one for the DB, one for >>> >> > recon. >>> >> > >>> >> > The ps output shows here that sks pid is not running ,It will be >>> >> > helpful >>> >> > if you let me know where exact the problem lies in sks. >>> >> > >>> >> > >>> >> > Thanks, >>> >> > Rohan >>> >> > >>> >> > On Fri, Aug 30, 2013 at 12:48 AM, Thomas Ward >>> >> > wrote: >>> >> >> >>> >> >> Rohan, >>> >> >> >>> >> >> On Thu, Aug 29, 2013 at 3:08 PM, Thomas Ward >>> >> >> wrote: >>> >> >>> >>> >> >>> I took a look at that bug, the bug went inactive because it had no >>> >> >>> activity or updates when the bug was marked "Incomplete". Since >>> >> >>> the >>> >> >>> original poster and nobody else provided any additional information >>> >> >>> the bug >>> >> >>> auto expired. >>> >> >>> >>> >> >>> I can try confirming this bug, however if I remember when I was >>> >> >>> configuring sks back in the days of 11.04 and 11.10, you had to >>> >> >>> configure it >>> >> >>> before you could actually start or restart the sks process. >>> >> >>> >>> >> >>> I'll take a look and see if I can reproduce, but there's probably >>> >> >>> logs >>> >> >>> somewhere for sks explaining why it didn't start or such. >>> >> >>> >>> >> >>> I'll check back with this in a little bit after I've done some >>> >> >>> testing. >>> >> >>> >>> >> >>> ------ >>> >> >>> Thomas >>> >> >>> Ubuntu Member >>> >> >>> Bug Squad Member >>> >> >>> >>> >> >>> >>> >> >>> On Thu, Aug 29, 2013 at 7:56 AM, rohan dighe >>> >> >>> >>> >> >>> wrote: >>> >> >>>> >>> >> >>>> Hi Team, >>> >> >>>> >>> >> >>>> I am working on setting up a gpg key server on ubuntu server,but >>> >> >>>> facing some issue as the init script of sks has some bug.when I >>> >> >>>> set up the >>> >> >>>> gpg key server and starts sks service >>> >> >>>> >>> >> >>>> I get the below output on command prompt its shows service running >>> >> >>>> but its actually not running and also I cant get the pid process >>> >> >>>> of sks >>> >> >>>> service showing running. >>> >> >>>> >>> >> >>>> root at tripwiretest: sks]# /etc/init.d/sks start >>> >> >>>> Starting sks daemons: sksdb.. sksrecon.. done. >>> >> >>>> >>> >> >>>> The ubuntu showing the bug on this link. >>> >> >>>> >>> >> >>>> https://bugs.launchpad.net/ubuntu/+source/sks/+bug/820354 >>> >> >>>> >>> >> >>>> I also followed the solution given on the link but with no >>> >> >>>> success. >>> >> >>>> >>> >> >>>> As the sks comes from the ubuntu 12.04 repository do we have any >>> >> >>>> permanent fix for the init script of sks. >>> >> >>>> >>> >> >>>> Please help me regarding the init script of sks. >>> >> >>>> >>> >> >>>> Thanks, >>> >> >>>> Rohan >>> >> >>>> >>> >> >>>> -- >>> >> >>>> Ubuntu-bugsquad mailing list >>> >> >>>> Ubuntu-bugsquad at lists.ubuntu.com >>> >> >>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad >>> >> >>>> >>> >> >>> >>> >> >> >>> >> >> Using a properly configured 'sks' instance, I am unable to reproduce >>> >> >> this bug, and using the init.d script correctly launches the two sks >>> >> >> processes, one for the DB, one for recon. >>> >> >> >>> >> >> Also, the package 'sks' does not by default set up the key database >>> >> >> or >>> >> >> other items just by installing. Did you actually configure 'sks' >>> >> >> first >>> >> >> before attempting to run it with the init script? >>> >> >> >>> >> >> ------ >>> >> >> Thomas >>> >> >> >>> >> > >>> >> >>> >> Typically, when I configured sks on several systems, I always had to >>> >> do this step to get the key db built after installing, then afterwards >>> >> I chown'd /var/lib/sks/DB: sudo sks build >>> >> >>> >> Did you run the build command for sks before attempting to launch sks? >>> >> If you did that and are still getting this error, then perhaps we >>> >> should purge sks from your system and start anew? This link here [1] >>> >> was able to help me get a brand new sks instance set up correctly >>> >> without incident, though, and it correctly runs the sks process and >>> >> builds the key database so it works. >>> >> >>> >> [1] >>> >> >>> >> https://kura.io/2011/12/17/running-your-own-pgp-keyserver-with-sks-on-debian-6ubuntu-10-04/ >>> >> >>> >> ------ >>> >> Thomas >>> > >>> > >> >> > > Okay, I tested using the link that you provided and also tested with > the link I provided. > > The link you provided asks you to run `sudo sks db` after you've build > the key database. I'm not entirely certain, however I think that > command, and then later closing out of it, is somehow causing it to > break. I am drawing this conclusion because in one tutorial I don't > run `sudo sks db` and it correctly launches later. > > So, let's start from the beginning, doing everything in your tutorial > *but* running `sudo sks db` after building it, but using these steps > to get it to launch, then using the rest of the tutorial for the web > interface, and see if that works: > > (1) sudo apt-get purge sks > (2) sudo apt-get install sks > (3) sudo sks build > (4) sudo chown -R debian-sks:debian-sks /var/lib/sks/DB > (5) sudo nano /etc/default/sks (change initstart to "yes") > (6) sudo /etc/init.d/sks start > (7) sudo pidof sks (should show PIDs now) > > ------ > Thomas From rohandighe18 at gmail.com Fri Aug 30 19:45:43 2013 From: rohandighe18 at gmail.com (rohan dighe) Date: Sat, 31 Aug 2013 01:15:43 +0530 Subject: sks init script bug in ubuntu 12.04 In-Reply-To: References: Message-ID: Hi Thomas, Thanks for providing me the steps for setting up sks,I will try this steps on my server and let you know the output of it. Thanks, Rohan On Fri, Aug 30, 2013 at 11:12 PM, Thomas Ward wrote: > Oh, I miswrote those steps. > > Use these: > > (1) sudo apt-get purge sks > (2) sudo rm -rf /var/lib/sks > (3) sudo apt-get install sks > (4) sudo sks build > (5) sudo chown -R debian-sks:debian-sks /var/lib/sks/DB > (6) sudo nano /etc/default/sks (change initstart to "yes") > (7) sudo /etc/init.d/sks start > (8) sudo pidof sks (should show PIDs now) > > On Fri, Aug 30, 2013 at 1:38 PM, Thomas Ward wrote: > > Rohan, > > > > On Fri, Aug 30, 2013 at 1:16 PM, rohan dighe > wrote: > >> > >> Hi Thomas, > >> > >> I did check the /etc/init.d/sks directory and found that the code >Edit > >> /etc/init.d/sks to automatically create the/var/run/sks directory on > >> startup. > >> > >>>At (approx) line 71 (after the check for /etc/default/sks & before > 'echo -n > >>> "sksdb.."') add > >>>mkdir -p `dirname "$SKSDBPID"` > >>>chown debian-sks `dirname "$SKSDBPID"` > >> > >> Was present in the init script of sks so I skip that configuration and > also > >> I skip the configuration In /etc/cron.daily/sks change db4.1_archive > to > >> db4.6_archive.mentioned in that link. > >> > >> and tried to configure the setup.but still not able to configure sks. > >> > >> I really appreciate your efforts. > >> > >> > >> > >> > >> On Fri, Aug 30, 2013 at 10:33 PM, Thomas Ward > wrote: > >>> > >>> I'm... confused by why they're having you create a directory... > >>> > >>> The tutorial you linked has this: > >>> > >>> >Edit /etc/init.d/sks to automatically create the/var/run/sks > directory on > >>> > startup. > >>> >At (approx) line 71 (after the check for /etc/default/sks & before > 'echo > >>> > -n "sksdb.."') add > >>> >mkdir -p `dirname "$SKSDBPID"` > >>> >chown debian-sks `dirname "$SKSDBPID"` > >>> > >>> I'm a little confused by why they have you do this. The init script > >>> that already exists already does this in Precise. > >>> > >>> ( > http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/precise/sks/precise-updates/view/head:/debian/sks.init#L71 > ) > >>> > >>> So, because I'm completely unsure of whether what they're doing works > >>> or not, give me a minute to spin up a new server instance and test > >>> this with the tutorial you linked... I think they did something wonky > >>> somewhere... > >>> > >>> ------ > >>> Thomas > >>> > >>> On Fri, Aug 30, 2013 at 12:46 PM, rohan dighe > >>> wrote: > >>> > Hi Thomas, > >>> > > >>> > Thanks for sending me the link for setup of the sks,and yes i did run > >>> > the > >>> > sks build command on the server while configuring sks server.But > still > >>> > getting the error. > >>> > > >>> > I followed the below link on how to setup the sks server. > >>> > > >>> > http://www.rainydayz.org/content/installing-opensks-keyserver > >>> > > >>> > > >>> > > >>> > > >>> > On Fri, Aug 30, 2013 at 9:50 PM, Thomas Ward > wrote: > >>> >> > >>> >> Rohan, > >>> >> > >>> >> On Fri, Aug 30, 2013 at 10:04 AM, rohan dighe < > rohandighe18 at gmail.com> > >>> >> wrote: > >>> >> > > >>> >> > > >>> >> > Hi Team, > >>> >> > > >>> >> > Thanks for the immediate response I really appreciate your > efforts on > >>> >> > providing me the solution for sks server. > >>> >> > > >>> >> > Here are the steps I am following to setup the sks server on > ubuntu > >>> >> > 12.04 > >>> >> > > >>> >> > # aptitude install sks > >>> >> > > >>> >> > Set database permissions on the database used by sks to store keys > >>> >> > > >>> >> > # chown -Rc debian-sks:debian-sks /var/lib/sks/DB > >>> >> > > >>> >> > To start the server automatically, set initstart=yes in > >>> >> > /etc/default/sks > >>> >> > > >>> >> > # Here I start the sks service > >>> >> > > >>> >> > # /etc/init.d/sks start > >>> >> > Stopping sks daemons: sksrecon..start-stop-daemon: warning: > failed to > >>> >> > kill 31643: No such process > >>> >> > sksdb..start-stop-daemon: warning: failed to kill 31640: No such > >>> >> > process > >>> >> > done. > >>> >> > > >>> >> > Starting sks daemons: sksdb.. sksrecon.. done. > >>> >> > > >>> >> > Then I configure webinterface for sks > >>> >> > > >>> >> > I install the sks winzip from internet > >>> >> > > >>> >> > Then I created a www directory in /var/lib/sks > >>> >> > > >>> >> > unzip the sks in /var/lib/sks/www folder > >>> >> > > >>> >> > After that 2 files gets downloaded in /var/lib/sks/www folder. > >>> >> > > >>> >> > 1) index.html > >>> >> > > >>> >> > 2) keys.jpg > >>> >> > > >>> >> > I Edit index.html and change the three references to > your.site.name > >>> >> > (currently at lines 20, 36 & 62) to the url of your keyserver) ( > In > >>> >> > my case > >>> >> > its my server ip ) > >>> >> > > >>> >> > Then I change the permission on the files > >>> >> > > >>> >> > # chown -R debian-sks:debian-sks /var/lib/sks/www > >>> >> > > >>> >> > After that when I tried to browse http://myserverip:11371 its not > >>> >> > working. > >>> >> > > >>> >> > I also tried to get the pid of the sks but the pid is not running > on > >>> >> > the > >>> >> > server below is the given output. > >>> >> > > >>> >> > # ps -aufx | grep sks > >>> >> > Warning: bad ps syntax, perhaps a bogus '-'? See > >>> >> > http://procps.sf.net/faq.html > >>> >> > root 31950 0.0 0.0 9384 900 pts/1 S+ 19:26 0:00 \_ grep > --color=auto > >>> >> > sks > >>> >> > > >>> >> > Here I cant see the 2 process running for sks one for the DB, one > for > >>> >> > recon. > >>> >> > > >>> >> > The ps output shows here that sks pid is not running ,It will be > >>> >> > helpful > >>> >> > if you let me know where exact the problem lies in sks. > >>> >> > > >>> >> > > >>> >> > Thanks, > >>> >> > Rohan > >>> >> > > >>> >> > On Fri, Aug 30, 2013 at 12:48 AM, Thomas Ward > >>> >> > wrote: > >>> >> >> > >>> >> >> Rohan, > >>> >> >> > >>> >> >> On Thu, Aug 29, 2013 at 3:08 PM, Thomas Ward > >>> >> >> wrote: > >>> >> >>> > >>> >> >>> I took a look at that bug, the bug went inactive because it had > no > >>> >> >>> activity or updates when the bug was marked "Incomplete". Since > >>> >> >>> the > >>> >> >>> original poster and nobody else provided any additional > information > >>> >> >>> the bug > >>> >> >>> auto expired. > >>> >> >>> > >>> >> >>> I can try confirming this bug, however if I remember when I was > >>> >> >>> configuring sks back in the days of 11.04 and 11.10, you had to > >>> >> >>> configure it > >>> >> >>> before you could actually start or restart the sks process. > >>> >> >>> > >>> >> >>> I'll take a look and see if I can reproduce, but there's > probably > >>> >> >>> logs > >>> >> >>> somewhere for sks explaining why it didn't start or such. > >>> >> >>> > >>> >> >>> I'll check back with this in a little bit after I've done some > >>> >> >>> testing. > >>> >> >>> > >>> >> >>> ------ > >>> >> >>> Thomas > >>> >> >>> Ubuntu Member > >>> >> >>> Bug Squad Member > >>> >> >>> > >>> >> >>> > >>> >> >>> On Thu, Aug 29, 2013 at 7:56 AM, rohan dighe > >>> >> >>> > >>> >> >>> wrote: > >>> >> >>>> > >>> >> >>>> Hi Team, > >>> >> >>>> > >>> >> >>>> I am working on setting up a gpg key server on ubuntu > server,but > >>> >> >>>> facing some issue as the init script of sks has some bug.when I > >>> >> >>>> set up the > >>> >> >>>> gpg key server and starts sks service > >>> >> >>>> > >>> >> >>>> I get the below output on command prompt its shows service > running > >>> >> >>>> but its actually not running and also I cant get the pid > process > >>> >> >>>> of sks > >>> >> >>>> service showing running. > >>> >> >>>> > >>> >> >>>> root at tripwiretest: sks]# /etc/init.d/sks start > >>> >> >>>> Starting sks daemons: sksdb.. sksrecon.. done. > >>> >> >>>> > >>> >> >>>> The ubuntu showing the bug on this link. > >>> >> >>>> > >>> >> >>>> https://bugs.launchpad.net/ubuntu/+source/sks/+bug/820354 > >>> >> >>>> > >>> >> >>>> I also followed the solution given on the link but with no > >>> >> >>>> success. > >>> >> >>>> > >>> >> >>>> As the sks comes from the ubuntu 12.04 repository do we have > any > >>> >> >>>> permanent fix for the init script of sks. > >>> >> >>>> > >>> >> >>>> Please help me regarding the init script of sks. > >>> >> >>>> > >>> >> >>>> Thanks, > >>> >> >>>> Rohan > >>> >> >>>> > >>> >> >>>> -- > >>> >> >>>> Ubuntu-bugsquad mailing list > >>> >> >>>> Ubuntu-bugsquad at lists.ubuntu.com > >>> >> >>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > >>> >> >>>> > >>> >> >>> > >>> >> >> > >>> >> >> Using a properly configured 'sks' instance, I am unable to > reproduce > >>> >> >> this bug, and using the init.d script correctly launches the two > sks > >>> >> >> processes, one for the DB, one for recon. > >>> >> >> > >>> >> >> Also, the package 'sks' does not by default set up the key > database > >>> >> >> or > >>> >> >> other items just by installing. Did you actually configure 'sks' > >>> >> >> first > >>> >> >> before attempting to run it with the init script? > >>> >> >> > >>> >> >> ------ > >>> >> >> Thomas > >>> >> >> > >>> >> > > >>> >> > >>> >> Typically, when I configured sks on several systems, I always had to > >>> >> do this step to get the key db built after installing, then > afterwards > >>> >> I chown'd /var/lib/sks/DB: sudo sks build > >>> >> > >>> >> Did you run the build command for sks before attempting to launch > sks? > >>> >> If you did that and are still getting this error, then perhaps we > >>> >> should purge sks from your system and start anew? This link here > [1] > >>> >> was able to help me get a brand new sks instance set up correctly > >>> >> without incident, though, and it correctly runs the sks process and > >>> >> builds the key database so it works. > >>> >> > >>> >> [1] > >>> >> > >>> >> > https://kura.io/2011/12/17/running-your-own-pgp-keyserver-with-sks-on-debian-6ubuntu-10-04/ > >>> >> > >>> >> ------ > >>> >> Thomas > >>> > > >>> > > >> > >> > > > > Okay, I tested using the link that you provided and also tested with > > the link I provided. > > > > The link you provided asks you to run `sudo sks db` after you've build > > the key database. I'm not entirely certain, however I think that > > command, and then later closing out of it, is somehow causing it to > > break. I am drawing this conclusion because in one tutorial I don't > > run `sudo sks db` and it correctly launches later. > > > > So, let's start from the beginning, doing everything in your tutorial > > *but* running `sudo sks db` after building it, but using these steps > > to get it to launch, then using the rest of the tutorial for the web > > interface, and see if that works: > > > > (1) sudo apt-get purge sks > > (2) sudo apt-get install sks > > (3) sudo sks build > > (4) sudo chown -R debian-sks:debian-sks /var/lib/sks/DB > > (5) sudo nano /etc/default/sks (change initstart to "yes") > > (6) sudo /etc/init.d/sks start > > (7) sudo pidof sks (should show PIDs now) > > > > ------ > > Thomas > -------------- next part -------------- An HTML attachment was scrubbed... URL: