From rohandighe18 at gmail.com Wed Sep 4 11:04:57 2013 From: rohandighe18 at gmail.com (rohan dighe) Date: Wed, 4 Sep 2013 16:34:57 +0530 Subject: sks init script bug in ubuntu 12.04 In-Reply-To: References: Message-ID: Hi Thomas, Thanks for giving me the steps on how to configure sks on the server,that steps worked for me and now my sks is running properly. Now I wanted to run sks on port no 80 instead of port no 11371. I did check the option of opening of port no 80 in /etc/sks/sksconf file use_port_80: parameter, but its not working I also followed this link https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/716438 https://bugs.launchpad.net/launchpad/+bug/524416 https://answers.launchpad.net/ubuntu-website/+question/79193 Can you please provide me any other solution as to work sks on port no 80 instead of port 11371. I really appreciate your help. Thanks, Rohan On Sat, Aug 31, 2013 at 1:15 AM, rohan dighe wrote: > 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: From noreply at ubuntu.com Sun Sep 8 18:08:20 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 08 Sep 2013 18:08:20 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingProcedures=22_by_michae?= =?utf-8?q?l-j-daniel?= Message-ID: <20130908180820.10179.48648@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingProcedures" page has been changed by michael-j-daniel: http://wiki.ubuntu.com/DebuggingProcedures?action=diff&rev1=115&rev2=116 '''Note: If you wish to report a bug, see ReportingBugs and if you wish to help with bugs, see HelpingWithBugs''' - If you want to add information on how to debug a package to this page, use this [[DebuggingTemplate|template]]. + If you want to add information to this page on how to debug a package, use this [[DebuggingTemplate|template]]. As part of triaging bug reports about specific packages or subsystems, bug triagers and developers have been writing debugging procedures for them. These include information about how to troubleshoot issues, gather the proper log files and common bug reports. If you find one missing, and if no one else can help, e-mail the Bug Squad! You can find them at ubuntu-bugsquad at lists.ubuntu.com . Or in #ubuntu-bugs on irc.ubuntu.com . From es20490446e at gmail.com Wed Sep 11 14:44:05 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Wed, 11 Sep 2013 16:44:05 +0200 Subject: Why XMir patches have been frozen for Intel? Message-ID: <523081B5.2070109@gmail.com> Does someone know why we have this ?: Snapshot 2.99.902 (2013-08-07) ============================== We do not condone or support Canonical in the course of action they have chosen, and will not carry XMir patches upstream. -The Management -------------- 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 dtl131 at gmail.com Wed Sep 11 16:08:10 2013 From: dtl131 at gmail.com (Daniel Letzeisen) Date: Wed, 11 Sep 2013 12:08:10 -0400 Subject: Why XMir patches have been frozen for Intel? In-Reply-To: <523081B5.2070109@gmail.com> References: <523081B5.2070109@gmail.com> Message-ID: <5230956A.8070005@gmail.com> On Wed 11 Sep 2013 10:44:05 AM EDT, Alberto Salvia Novella wrote: > Does someone know why we have this (Intel dropping XMir support) > Alberto, that is Intel's decision and that is the reason they gave. What's to discuss with the Bug Squad? From es20490446e at gmail.com Wed Sep 11 16:17:50 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Wed, 11 Sep 2013 18:17:50 +0200 Subject: Why XMir patches have been frozen for Intel? In-Reply-To: <5230956A.8070005@gmail.com> References: <523081B5.2070109@gmail.com> <5230956A.8070005@gmail.com> Message-ID: <523097AE.7080703@gmail.com> Just for info, since this seems to me a very important decision for the Ubuntu Project. El 11/09/13 18:08, Daniel Letzeisen escribió: > On Wed 11 Sep 2013 10:44:05 AM EDT, Alberto Salvia Novella wrote: >> Does someone know why we have this (Intel dropping XMir support) >> > > Alberto, that is Intel's decision and that is the reason they gave. > What's to discuss with the Bug Squad? -------------- 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 corbellini.andrea at gmail.com Wed Sep 11 16:24:32 2013 From: corbellini.andrea at gmail.com (Andrea Corbellini) Date: Wed, 11 Sep 2013 16:26:32 +0002 Subject: Why XMir patches have been frozen for Intel? In-Reply-To: <523097AE.7080703@gmail.com> References: <523081B5.2070109@gmail.com> <5230956A.8070005@gmail.com> < 523097AE.7080703@gmail.com> Message-ID: <52309944.ed0cb40a.4580.ffffbd19@mx.google.com> On Wed, Sep 11, 2013 at 6:17 PM, Alberto Salvia Novella wrote: > Just for info, since this seems to me a very important decision for > the Ubuntu Project. Technically speaking, this just means that the Ubuntu project will have to carry patches downstream rather than upstream. More work for Mir developers, less work for Intel ones. From es20490446e at gmail.com Thu Sep 12 12:34:39 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Thu, 12 Sep 2013 14:34:39 +0200 Subject: Why XMir patches have been frozen for Intel? In-Reply-To: <52309944.ed0cb40a.4580.ffffbd19@mx.google.com> References: <523081B5.2070109@gmail.com> <5230956A.8070005@gmail.com> < 523097AE.7080703@gmail.com> <52309944.ed0cb40a.4580.ffffbd19@mx.google.com> Message-ID: <5231B4DF.5010304@gmail.com> Thank you for the comment, Andrea. El 11/09/13 18:24, Andrea Corbellini escribió: > On Wed, Sep 11, 2013 at 6:17 PM, Alberto Salvia Novella > wrote: > >> Just for info, since this seems to me a very important decision for >> the Ubuntu Project. > Technically speaking, this just means that the Ubuntu project will > have to carry patches downstream rather than upstream. More work for > Mir developers, less work for Intel ones. > -------------- 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 walter.garcia at upf.edu Sat Sep 14 15:26:04 2013 From: walter.garcia at upf.edu (Walter Garcia-Fontes) Date: Sat, 14 Sep 2013 17:26:04 +0200 Subject: Opened a page for triage for the Global Jam Message-ID: <20130914152604.GA17282@upf.edu> I'll be doing some triaging during the Global Jam, if anybody wants to join I've opened a page with new, incomplete and confirmed bugs for "unity": https://wiki.ubuntu.com/UbuntuBugDay/20130914#preview -- Walter Garcia-Fontes From thinkndev at gmail.com Sat Sep 14 15:57:47 2013 From: thinkndev at gmail.com (John Kim) Date: Sat, 14 Sep 2013 08:57:47 -0700 Subject: Opened a page for triage for the Global Jam In-Reply-To: <20130914152604.GA17282@upf.edu> References: <20130914152604.GA17282@upf.edu> Message-ID: <761029ff-1ce2-4e94-b857-de1ef4b177fb@email.android.com> Wow, that's a lot of bugs. Is the only task to mark bugs as confirmed? What else can be done by someone without triaging rights? Can't wait to help. :-) Walter Garcia-Fontes 이 씀: >I'll be doing some triaging during the Global Jam, if anybody wants to >join I've opened a page with new, incomplete and confirmed bugs for >"unity": > >https://wiki.ubuntu.com/UbuntuBugDay/20130914#preview > >-- >Walter Garcia-Fontes > > >-- >Ubuntu-bugsquad mailing list >Ubuntu-bugsquad at lists.ubuntu.com >https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: From teward at ubuntu.com Sat Sep 14 16:19:06 2013 From: teward at ubuntu.com (Thomas Ward) Date: Sat, 14 Sep 2013 12:19:06 -0400 Subject: Opened a page for triage for the Global Jam In-Reply-To: <761029ff-1ce2-4e94-b857-de1ef4b177fb@email.android.com> References: <20130914152604.GA17282@upf.edu> <761029ff-1ce2-4e94-b857-de1ef4b177fb@email.android.com> Message-ID: Hi, everyone! On Sat, Sep 14, 2013 at 11:57 AM, John Kim wrote: > Wow, that's a lot of bugs. Is the only task to mark bugs as confirmed? What > else can be done by someone without triaging rights? Anyone can help triage. The only thing is, to set "triaged" you need a bug-control rights. Typically, members of bug-control are around. While I typically don't stray outside of the server packages of which I routinely work with, since today is a day where I do nothing but sit around in remote systems windows today to upgrade some servers and install Ubuntu onto one of my other systems, I have nothing really eventful to do today, so I can make myself available on #ubuntu-bugs on IRC (irc.freenode.net) to help set things as triaged or set a bug's importance, and other tasks which require Ubuntu Bug Control access. I'm certain that other bugcontrollers will be able to make themselves available to assist, as well. > > Can't wait to help. :-) > > Walter Garcia-Fontes 이 씀: >> >> I'll be doing some triaging during the Global Jam, if anybody wants to >> join I've opened a page with new, incomplete and confirmed bugs for >> "unity": >> >> https://wiki.ubuntu.com/UbuntuBugDay/20130914#preview > > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > > ------ Thomas Ward Ubuntu Member BugSquad Member From sergioandresmeneses at gmail.com Sat Sep 14 16:21:11 2013 From: sergioandresmeneses at gmail.com (Sergio Meneses) Date: Sat, 14 Sep 2013 11:21:11 -0500 Subject: Opened a page for triage for the Global Jam In-Reply-To: References: <20130914152604.GA17282@upf.edu> <761029ff-1ce2-4e94-b857-de1ef4b177fb@email.android.com> Message-ID: Thanks a lot for sharing this! On Sat, Sep 14, 2013 at 11:19 AM, Thomas Ward wrote: > Hi, everyone! > > > On Sat, Sep 14, 2013 at 11:57 AM, John Kim wrote: > > Wow, that's a lot of bugs. Is the only task to mark bugs as confirmed? > What > > else can be done by someone without triaging rights? > > Anyone can help triage. The only thing is, to set "triaged" you need > a bug-control rights. Typically, members of bug-control are around. > > While I typically don't stray outside of the server packages of which > I routinely work with, since today is a day where I do nothing but sit > around in remote systems windows today to upgrade some servers and > install Ubuntu onto one of my other systems, I have nothing really > eventful to do today, so I can make myself available on #ubuntu-bugs > on IRC (irc.freenode.net) to help set things as triaged or set a bug's > importance, and other tasks which require Ubuntu Bug Control access. > I'm certain that other bugcontrollers will be able to make themselves > available to assist, as well. > Perfect > > > > > Can't wait to help. :-) > > > > Walter Garcia-Fontes 이 씀: > >> > >> I'll be doing some triaging during the Global Jam, if anybody wants to > >> join I've opened a page with new, incomplete and confirmed bugs for > >> "unity": > >> > >> https://wiki.ubuntu.com/UbuntuBugDay/20130914#preview > > > > > > -- > > Sent from my Android device with K-9 Mail. Please excuse my brevity. > > > > > > ------ > Thomas Ward > Ubuntu Member > BugSquad Member > > -- > 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 walter.garcia at upf.edu Sat Sep 14 16:25:21 2013 From: walter.garcia at upf.edu (Walter Garcia-Fontes) Date: Sat, 14 Sep 2013 18:25:21 +0200 Subject: Opened a page for triage for the Global Jam In-Reply-To: <761029ff-1ce2-4e94-b857-de1ef4b177fb@email.android.com> References: <20130914152604.GA17282@upf.edu> <761029ff-1ce2-4e94-b857-de1ef4b177fb@email.android.com> Message-ID: <20130914162521.GB17282@upf.edu> * John Kim, thinkndev at gmail.com [14/09/13 17:57]: > Wow, that's a lot of bugs. Is the only task to mark bugs as confirmed? What else can be done by someone without triaging rights? If by triaging rights you mean the right to mark a bug as "triaged", don't worry, I don't have it either (only members of the bug control team have that right, as far as I know). But I can check if the user has used apport to file the bug, or ask for more information, or see if the bug is filed against the appropriate package, and a lot of other stuff. Check bugs for responses to get an idea and the page for possible (and appropriate) responses: https://wiki.ubuntu.com/Bugs/Responses to see what type of things you can do. -- Walter Garcia-Fontes From teward at ubuntu.com Sat Sep 14 16:32:17 2013 From: teward at ubuntu.com (Thomas Ward) Date: Sat, 14 Sep 2013 12:32:17 -0400 Subject: Opened a page for triage for the Global Jam In-Reply-To: <20130914162521.GB17282@upf.edu> References: <20130914152604.GA17282@upf.edu> <761029ff-1ce2-4e94-b857-de1ef4b177fb@email.android.com> <20130914162521.GB17282@upf.edu> Message-ID: On Sat, Sep 14, 2013 at 12:25 PM, Walter Garcia-Fontes wrote: > * John Kim, thinkndev at gmail.com [14/09/13 17:57]: >> Wow, that's a lot of bugs. Is the only task to mark bugs as confirmed? What else can be done by someone without triaging rights? > > If by triaging rights you mean the right to mark a bug as "triaged", > don't worry, I don't have it either (only members of the bug control > team have that right, as far as I know). You're right, only bug controllers have the right to set things as "triaged". > > But I can check if the user has used apport to file the bug, or ask > for more information, or see if the bug is filed against the > appropriate package, and a lot of other stuff. Check bugs for > responses to get an idea and the page for possible (and appropriate) > responses: > > https://wiki.ubuntu.com/Bugs/Responses > > to see what type of things you can do. Also, I suggest that you all load up the freenode webchat or an IRC client and join into the #ubuntu-bugs channel on freenode, myself and other bug controllers are in the channel and will be around throughout the day to assist you with setting things as "triaged" and to help with other tasks that only bug control has access to. > > -- > Walter Garcia-Fontes > > > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad From teward at ubuntu.com Sat Sep 14 16:44:11 2013 From: teward at ubuntu.com (Thomas Ward) Date: Sat, 14 Sep 2013 12:44:11 -0400 Subject: Opened a page for triage for the Global Jam In-Reply-To: References: <20130914152604.GA17282@upf.edu> <761029ff-1ce2-4e94-b857-de1ef4b177fb@email.android.com> <20130914162521.GB17282@upf.edu> Message-ID: Since I obviously forgot to provide a link, if you would like to join the #ubuntu-bugs IRC channel on freenode to get help with the triage stuff, or to get a bug controller involved to help with setting "Triaged" or the importance, this link will allow you to use the Freenode Webchat to access the channel, just choose a nickname that we can recognize, or is on your Launchpad profile, and join in. http://webchat.freenode.net/?channels=ubuntu-bugs On Sat, Sep 14, 2013 at 12:32 PM, Thomas Ward wrote: > On Sat, Sep 14, 2013 at 12:25 PM, Walter Garcia-Fontes > wrote: > > * John Kim, thinkndev at gmail.com [14/09/13 17:57]: > >> Wow, that's a lot of bugs. Is the only task to mark bugs as confirmed? > What else can be done by someone without triaging rights? > > > > If by triaging rights you mean the right to mark a bug as "triaged", > > don't worry, I don't have it either (only members of the bug control > > team have that right, as far as I know). > > You're right, only bug controllers have the right to set things as > "triaged". > > > > > But I can check if the user has used apport to file the bug, or ask > > for more information, or see if the bug is filed against the > > appropriate package, and a lot of other stuff. Check bugs for > > responses to get an idea and the page for possible (and appropriate) > > responses: > > > > https://wiki.ubuntu.com/Bugs/Responses > > > > to see what type of things you can do. > > Also, I suggest that you all load up the freenode webchat or an IRC > client and join into the #ubuntu-bugs channel on freenode, myself and > other bug controllers are in the channel and will be around throughout > the day to assist you with setting things as "triaged" and to help > with other tasks that only bug control has access to. > > > > > > -- > > Walter Garcia-Fontes > > > > > > > > -- > > 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 jack at troop55.net Sat Sep 14 16:45:54 2013 From: jack at troop55.net (Jack Ramsay) Date: Sat, 14 Sep 2013 11:45:54 -0500 Subject: Opened a page for triage for the Global Jam In-Reply-To: References: <20130914152604.GA17282@upf.edu> <761029ff-1ce2-4e94-b857-de1ef4b177fb@email.android.com> <20130914162521.GB17282@upf.edu> Message-ID: How do I mark a bug off on the wiki page I have nothing to do I can tackle a bunch of bugs On Sep 14, 2013 11:44 AM, "Thomas Ward" wrote: > Since I obviously forgot to provide a link, if you would like to join the > #ubuntu-bugs IRC channel on freenode to get help with the triage stuff, or > to get a bug controller involved to help with setting "Triaged" or the > importance, this link will allow you to use the Freenode Webchat to access > the channel, just choose a nickname that we can recognize, or is on your > Launchpad profile, and join in. > > http://webchat.freenode.net/?channels=ubuntu-bugs > > > On Sat, Sep 14, 2013 at 12:32 PM, Thomas Ward wrote: > >> On Sat, Sep 14, 2013 at 12:25 PM, Walter Garcia-Fontes >> wrote: >> > * John Kim, thinkndev at gmail.com [14/09/13 17:57]: >> >> Wow, that's a lot of bugs. Is the only task to mark bugs as confirmed? >> What else can be done by someone without triaging rights? >> > >> > If by triaging rights you mean the right to mark a bug as "triaged", >> > don't worry, I don't have it either (only members of the bug control >> > team have that right, as far as I know). >> >> You're right, only bug controllers have the right to set things as >> "triaged". >> >> > >> > But I can check if the user has used apport to file the bug, or ask >> > for more information, or see if the bug is filed against the >> > appropriate package, and a lot of other stuff. Check bugs for >> > responses to get an idea and the page for possible (and appropriate) >> > responses: >> > >> > https://wiki.ubuntu.com/Bugs/Responses >> > >> > to see what type of things you can do. >> >> Also, I suggest that you all load up the freenode webchat or an IRC >> client and join into the #ubuntu-bugs channel on freenode, myself and >> other bug controllers are in the channel and will be around throughout >> the day to assist you with setting things as "triaged" and to help >> with other tasks that only bug control has access to. >> >> >> > >> > -- >> > Walter Garcia-Fontes >> > >> > >> > >> > -- >> > Ubuntu-bugsquad mailing list >> > Ubuntu-bugsquad at lists.ubuntu.com >> > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad >> > > > -- > 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 walter.garcia at upf.edu Sat Sep 14 16:52:38 2013 From: walter.garcia at upf.edu (Walter Garcia-Fontes) Date: Sat, 14 Sep 2013 18:52:38 +0200 Subject: Opened a page for triage for the Global Jam In-Reply-To: References: <20130914152604.GA17282@upf.edu> <761029ff-1ce2-4e94-b857-de1ef4b177fb@email.android.com> <20130914162521.GB17282@upf.edu> Message-ID: <20130914165238.GC17282@upf.edu> * Jack Ramsay, jack at troop55.net [14/09/13 18:46]: > How do I mark a bug off on the wiki page I have nothing to do I can tackle > a bunch of bugs Just edit the page and write after the first brackets ( [[ ) without any space, and put your name at the end. Check the first bugs where I have done it myself and just do the same, but put your name. -- Walter Garcia-Fontes From robert.park at canonical.com Sat Sep 14 17:21:12 2013 From: robert.park at canonical.com (Robert Park) Date: Sat, 14 Sep 2013 10:21:12 -0700 Subject: Opened a page for triage for the Global Jam In-Reply-To: References: <20130914152604.GA17282@upf.edu> <761029ff-1ce2-4e94-b857-de1ef4b177fb@email.android.com> <20130914162521.GB17282@upf.edu> Message-ID: On Sat, Sep 14, 2013 at 9:32 AM, Thomas Ward wrote: > You're right, only bug controllers have the right to set things as "triaged". Don't forget about the members of the team that own the project. They also can set the bug statuses as they like, even if they aren't in bug control. From noreply at ubuntu.com Sat Sep 14 03:08:09 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sat, 14 Sep 2013 03:08:09 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22PulseAudio/Log=22_by_dtl131?= Message-ID: <20130914030809.29134.15696@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "PulseAudio/Log" page has been changed by dtl131: http://wiki.ubuntu.com/PulseAudio/Log?action=diff&rev1=9&rev2=10 * Open a terminal, then enter these commands: {{{ - echo autospawn = no >> ~/.pulse/client.conf + echo autospawn = no >> ~/.config/pulse/client.conf #use ~/.pulse/client.conf on Ubuntu <= 12.10 killall pulseaudio LANG=C pulseaudio -vvvv --log-time=1 > ~/pulseverbose.log 2>&1 }}} From thinkndev at gmail.com Sun Sep 15 00:50:36 2013 From: thinkndev at gmail.com (John Kim) Date: Sat, 14 Sep 2013 17:50:36 -0700 Subject: Opened a page for triage for the Global Jam In-Reply-To: <20130914152604.GA17282@upf.edu> References: <20130914152604.GA17282@upf.edu> Message-ID: <5235045C.3030703@gmail.com> On 09/14/2013 08:26 AM, Walter Garcia-Fontes wrote: > I'll be doing some triaging during the Global Jam, if anybody wants to > join I've opened a page with new, incomplete and confirmed bugs for > "unity": > > https://wiki.ubuntu.com/UbuntuBugDay/20130914#preview > Hopefully, this is an ongoing thing for at least one week. That bug list cannot be completed in one Bug Day. Fortunately, I was able to go over 8 bugs! :-) @Walter, how do I set my launchpad id to be hyperlinked? f-jack and I come out as hardcoded text. Thanks! -- John Kim FOSS Enthusiast www.internet-in-a-box.org thinkndev at gmail.com From walter.garcia at upf.edu Sun Sep 15 05:17:13 2013 From: walter.garcia at upf.edu (Walter Garcia-Fontes) Date: Sun, 15 Sep 2013 07:17:13 +0200 Subject: Opened a page for triage for the Global Jam In-Reply-To: <5235045C.3030703@gmail.com> References: <20130914152604.GA17282@upf.edu> <5235045C.3030703@gmail.com> Message-ID: <20130915051713.GB6275@upf.edu> * John Kim, thinkndev at gmail.com [15/09/13 02:51]: > @Walter, how do I > set my launchpad id to be hyperlinked? f-jack and I come out as > hardcoded text. You need to have a description in your profile, that will become a page in the wiki titled as your name. Mine is for instance WalterGarciaFontes . Writing this in the wiki will create automatically a link to that page. -- Walter Garcia-Fontes From thinkndev at gmail.com Sun Sep 15 15:17:09 2013 From: thinkndev at gmail.com (John Kim) Date: Sun, 15 Sep 2013 08:17:09 -0700 Subject: Opened a page for triage for the Global Jam In-Reply-To: <20130915051713.GB6275@upf.edu> References: <20130914152604.GA17282@upf.edu> <5235045C.3030703@gmail.com> <20130915051713.GB6275@upf.edu> Message-ID: <30405F0F-3D38-4D5C-ABC4-245129CE2E52@gmail.com> Ah, got it. Looks like I need to start my own wiki page soon. John Kim Student/FOSS Enthusiast www.internet-in-a-box.org thinkndev at gmail.com On Sep 14, 2013, at 10:17 PM, Walter Garcia-Fontes wrote: > * John Kim, thinkndev at gmail.com [15/09/13 02:51]: >> @Walter, how do I >> set my launchpad id to be hyperlinked? f-jack and I come out as >> hardcoded text. > > You need to have a description in your profile, that will become a > page in the wiki titled as your name. Mine is for instance > WalterGarciaFontes . Writing this in the wiki will create > automatically a link to that page. > > -- > Walter Garcia-Fontes > > From thinkndev at gmail.com Sun Sep 15 15:17:09 2013 From: thinkndev at gmail.com (John Kim) Date: Sun, 15 Sep 2013 08:17:09 -0700 Subject: Opened a page for triage for the Global Jam In-Reply-To: <20130915051713.GB6275@upf.edu> References: <20130914152604.GA17282@upf.edu> <5235045C.3030703@gmail.com> <20130915051713.GB6275@upf.edu> Message-ID: <30405F0F-3D38-4D5C-ABC4-245129CE2E52@gmail.com> Ah, got it. Looks like I need to start my own wiki page soon. John Kim Student/FOSS Enthusiast www.internet-in-a-box.org thinkndev at gmail.com On Sep 14, 2013, at 10:17 PM, Walter Garcia-Fontes wrote: > * John Kim, thinkndev at gmail.com [15/09/13 02:51]: >> @Walter, how do I >> set my launchpad id to be hyperlinked? f-jack and I come out as >> hardcoded text. > > You need to have a description in your profile, that will become a > page in the wiki titled as your name. Mine is for instance > WalterGarciaFontes . Writing this in the wiki will create > automatically a link to that page. > > -- > Walter Garcia-Fontes > > From noreply at ubuntu.com Sun Sep 15 17:55:43 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 15 Sep 2013 17:55:43 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingProcedures=22_by_penalv?= =?utf-8?q?ch?= Message-ID: <20130915175543.22902.32937@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingProcedures" page has been changed by penalvch: http://wiki.ubuntu.com/DebuggingProcedures?action=diff&rev1=116&rev2=117 Comment: 1) Added existing debugging USB article under Hardware section. * [[DebuggingTouchpadDetection|Touchpad detection]] * [[Hotkeys/Troubleshooting|Troubleshooting Hotkeys]] * [[DebuggingKeyboardDetection|Keyboard detection]] + * [[https://wiki.ubuntu.com/Kernel/Debugging/USB|USB problems]] == Storage devices == From es20490446e at gmail.com Mon Sep 16 07:35:14 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Mon, 16 Sep 2013 09:35:14 +0200 Subject: Opened a page for triage for the Global Jam In-Reply-To: <20130914152604.GA17282@upf.edu> References: <20130914152604.GA17282@upf.edu> Message-ID: <5236B4B2.3080103@gmail.com> El 14/09/13 17:26, Walter Garcia-Fontes escribió: > I'll be doing some triaging during the Global Jam, if anybody wants to > join I've opened a page with new, incomplete and confirmed bugs for > "unity": > > https://wiki.ubuntu.com/UbuntuBugDay/20130914#preview > I was to say that I will have a deep look into this list in these following days, but the server returns an 500 (Internal Server Error) when I try to go to the list. I tell you just for the case you didn't know already. Regards -------------- 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 walter.garcia at upf.edu Mon Sep 16 07:46:24 2013 From: walter.garcia at upf.edu (Walter Garcia-Fontes) Date: Mon, 16 Sep 2013 09:46:24 +0200 Subject: Opened a page for triage for the Global Jam In-Reply-To: <5236B4B2.3080103@gmail.com> References: <20130914152604.GA17282@upf.edu> <5236B4B2.3080103@gmail.com> Message-ID: <20130916074624.GH8497@upf.edu> * Alberto Salvia Novella, es20490446e at gmail.com [16/09/13 09:35]: > I was to say that I will have a deep look into this list in these > following days, but the server returns an 500 (Internal Server > Error) when I try to go to the list. I tell you just for the case > you didn't know already. If it is the typical "Timeout" that Launchpad gives, it is just a matter of trying again, it does it all the time. -- Walter Garcia-Fontes From es20490446e at gmail.com Mon Sep 16 07:54:08 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Mon, 16 Sep 2013 09:54:08 +0200 Subject: Opened a page for triage for the Global Jam In-Reply-To: References: <20130914152604.GA17282@upf.edu> <761029ff-1ce2-4e94-b857-de1ef4b177fb@email.android.com> <20130914162521.GB17282@upf.edu> Message-ID: <5236B920.2020009@gmail.com> El 14/09/13 18:32, Thomas Ward escribió: > You're right, only bug controllers have the right to set things as "triaged". I suggest that members of Ubuntu BugControl rather *focus* on triaging bugs and setting priority than in any other thing, because there are many people out there that can do the rest of the tasks (and they do indeed) but only a small proportion can get reports ready to be worked on. *Expectation* of the rest of the community isn't having more written or confirmed reports but more triaged and fixed ones, and this is what will encourage users to get involved in bug management tasks. So the bugs I suggest for Ubuntu Bug Control members are those which: * Are *affecting* the 'Ubuntu' project * Have a *status* of 'new' or 'confirmed' * Have a *priority* of 'undecided' * Are *tagged* with the latest release name (in this case 'Saucy') Regards -------------- 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 es20490446e at gmail.com Mon Sep 16 07:59:38 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Mon, 16 Sep 2013 09:59:38 +0200 Subject: Opened a page for triage for the Global Jam In-Reply-To: <20130916074624.GH8497@upf.edu> References: <20130914152604.GA17282@upf.edu> <5236B4B2.3080103@gmail.com> <20130916074624.GH8497@upf.edu> Message-ID: <5236BA6A.7070904@gmail.com> El 16/09/13 09:46, Walter Garcia-Fontes escribió: > * Alberto Salvia Novella, es20490446e at gmail.com [16/09/13 09:35]: >> I was to say that I will have a deep look into this list in these >> following days, but the server returns an 500 (Internal Server >> Error) when I try to go to the list. I tell you just for the case >> you didn't know already. > If it is the typical "Timeout" that Launchpad gives, it is just a > matter of trying again, it does it all the time. > Oh, it's true. Thank you. -------------- 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 thinkndev at gmail.com Mon Sep 16 12:46:13 2013 From: thinkndev at gmail.com (John Kim) Date: Mon, 16 Sep 2013 05:46:13 -0700 Subject: Opened a page for triage for the Global Jam In-Reply-To: <5236B920.2020009@gmail.com> References: <20130914152604.GA17282@upf.edu> <761029ff-1ce2-4e94-b857-de1ef4b177fb@email.android.com> <20130914162521.GB17282@upf.edu> <5236B920.2020009@gmail.com> Message-ID: <57a5dd06-dcd0-4089-b7ed-2fab54e2048f@email.android.com> Hey Alberto, So what should we do with the bugs that don't comply with the priority list you mentioned? Mark them as invalid? I'm just a volunteer, so I'm curious what else could be done on the page. Alberto Salvia Novella 이 씀: >El 14/09/13 18:32, Thomas Ward escribió: >> You're right, only bug controllers have the right to set things as >"triaged". >I suggest that members of Ubuntu BugControl rather *focus* on triaging >bugs and setting priority than in any other thing, because there are >many people out there that can do the rest of the tasks (and they do >indeed) but only a small proportion can get reports ready to be worked >on. > >*Expectation* of the rest of the community isn't having more written or > >confirmed reports but more triaged and fixed ones, and this is what >will >encourage users to get involved in bug management tasks. > >So the bugs I suggest for Ubuntu Bug Control members are those which: > > * Are *affecting* the 'Ubuntu' project > * Have a *status* of 'new' or 'confirmed' > * Have a *priority* of 'undecided' > * Are *tagged* with the latest release name (in this case 'Saucy') > >Regards > > >------------------------------------------------------------------------ > >-- >Ubuntu-bugsquad mailing list >Ubuntu-bugsquad at lists.ubuntu.com >https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: From es20490446e at gmail.com Mon Sep 16 14:26:54 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Mon, 16 Sep 2013 16:26:54 +0200 Subject: Opened a page for triage for the Global Jam In-Reply-To: <57a5dd06-dcd0-4089-b7ed-2fab54e2048f@email.android.com> References: <20130914152604.GA17282@upf.edu> <761029ff-1ce2-4e94-b857-de1ef4b177fb@email.android.com> <20130914162521.GB17282@upf.edu> <5236B920.2020009@gmail.com> <57a5dd06-dcd0-4089-b7ed-2fab54e2048f@email.android.com> Message-ID: <5237152E.3050808@gmail.com> El 16/09/13 14:46, John Kim escribió: > So what should we do with the bugs that don't comply with the priority > list you mentioned? Mark them as invalid? I wasn't specifically speaking about the list but in general, when using the '*advance search*' feature that can be found under any search box in Launchpad (for example, if you click on the 'advance search' option in this page ; which is the bug search for the Ubuntu project). I was simply suggesting that if you search using this feature and you're a member of Ubuntu BugControl; that you perform it using these *parameters*, which seems to me the ones that will show the most quantity of bugs expecting to be reviewed by a member of this team: * Are *affecting* the 'Ubuntu' project (what is done by simply using the search feature being in the Ubuntu page, the one I asked you to go to before) * Have a *status* of 'new' or 'confirmed' * Have a *priority* of 'undecided' * Are *tagged* with the latest release name (in this case 'Saucy') On the other hand, if what are you wanting is to help with the Ubuntu BugDay lists and are a member of Ubuntu BugControl, perhaps will be better for you to begin with the *confirmed bug list*; which has the higher probability of needing to be marked as 'triaged'. But if you find a bug that needs a *different action* than being triaged, you can just perform that action and that's all. If you're *not a member* of BugControl you shall be wanting to focus on the oposite, the 'new bugs' list or the 'incomplete bugs' list. Thanks for your help -------------- 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 webmaster at ubuntu.com Mon Sep 16 12:25:06 2013 From: webmaster at ubuntu.com (Help Ubuntu) Date: Mon, 16 Sep 2013 12:25:06 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_bjoern-michaelsen?= Message-ID: <20130916122506.29912.33129@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Community Ubuntu Documentation" for change notification. The "ReportingBugs" page has been changed by bjoern-michaelsen: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=242&rev2=243 <
><
> Many of the triagers and developers who are providing support to you, '''are volunteers doing so out of altruism'''. Please keep this in mind when making your comments. <
><
> - Please '''do not report bugs about software in [[PPA]]s''' on Launchpad. This is because software in PPAs are not provided by the official Ubuntu repositories. Instead, the PPA homepage would have a contact point and preference of the PPA provider. + Please '''do not report bugs about software in [[PPA]]s''' on Launchpad. This is because software in PPAs are not provided by the official Ubuntu repositories. Instead, the PPA homepage would have a contact point and preference of the PPA provider. The exception is [[LibreOffice]] as per [[https://lists.launchpad.net/libreoffice/msg00072.html|this mail]], as LibreOffice is too big to be tracked via email: as described in the mail, file a bug on Launchpad with tag "ppa". <
><
> Please do not add project tasks to bug reports that are invalid because they are not supported. For example, if you were using the LibreOffice PPA and reported a bug against the package libreoffice (Ubuntu), which would be marked Status Invalid, please do not add the Launchpad Project [[https://launchpad.net/df-libreoffice|df-libreoffice]] to the report, or change the package libreoffice (Ubuntu) to the project df-libreoffice. The purposes of adding the upstream project to a report is to track valid bugs in Ubuntu that are valid upstream, and may have been reported upstream, not to start another upstream bug tracker. From es20490446e at gmail.com Tue Sep 17 09:43:33 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Tue, 17 Sep 2013 11:43:33 +0200 Subject: Suggestion about the BugDay Message-ID: <52382445.5030901@gmail.com> I suggest the next BugDay to be about reports tagged with the latest Ubuntu release name; cause I found that otherwise most reports, at least in the 'confirmed bugs' list, are from EOL releases which haven't got an Apport Information that tells Launchpad Janitor to automatically close the report. On the other hand; it may help the next release to be perceived more stable, and no several weeks after its publication. Thank you -------------- 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 es20490446e at gmail.com Tue Sep 17 10:22:01 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Tue, 17 Sep 2013 12:22:01 +0200 Subject: About bug status in the wiki Message-ID: <52382D49.5070808@gmail.com> In https://wiki.ubuntu.com/Bugs/Status it's said: /*Incomplete*//: /// * /If you have to ask the reporter questions, set the bug to //Incomplete///// * /Ask the submitter to provide any necessary information in a comment, and make sure you subscribe yourself to the bug report so you will get any updates to the bug via e-mail/ The question I have here is "will be enough to subscribe to all the bug report except comments?". Thank you in advance. -------------- 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 maarten.bezemer at gmail.com Tue Sep 17 10:38:40 2013 From: maarten.bezemer at gmail.com (Maarten Bezemer) Date: Tue, 17 Sep 2013 12:38:40 +0200 Subject: About bug status in the wiki In-Reply-To: <52382D49.5070808@gmail.com> References: <52382D49.5070808@gmail.com> Message-ID: <1705838.rYaRV6TA4C@bzr-ram> On Tuesday 17 September 2013 12:22:01 Alberto Salvia Novella wrote: > In https://wiki.ubuntu.com/Bugs/Status it's said: > > /*Incomplete*//: /// > > * > > /If you have to ask the reporter questions, set the bug to > //Incomplete///// > > * /Ask the submitter to provide any necessary information in a > comment, and make sure you subscribe yourself to the bug report > so you will get any updates to the bug via e-mail/ > > The question I have here is "will be enough to subscribe to all the bug > report except comments?". Not really, as you are asking the reporter for details, which (s)he provides by using the comments. So in order to get notified of the response of the report you need to subscribe to the comments as well. Cheers, Maarten From es20490446e at gmail.com Tue Sep 17 10:47:31 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Tue, 17 Sep 2013 12:47:31 +0200 Subject: About bug status in the wiki In-Reply-To: <1705838.rYaRV6TA4C@bzr-ram> References: <52382D49.5070808@gmail.com> <1705838.rYaRV6TA4C@bzr-ram> Message-ID: <52383343.7030209@gmail.com> El 17/09/13 12:38, Maarten Bezemer escribió: > So in order to get notified of the response of the report you need to subscribe > to the comments as well. This is what I needed to know. Thanks for your attention. -------------- 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 brian at ubuntu.com Tue Sep 17 15:14:38 2013 From: brian at ubuntu.com (Brian Murray) Date: Tue, 17 Sep 2013 08:14:38 -0700 Subject: Opened a page for triage for the Global Jam In-Reply-To: <20130914162521.GB17282@upf.edu> References: <20130914152604.GA17282@upf.edu> <761029ff-1ce2-4e94-b857-de1ef4b177fb@email.android.com> <20130914162521.GB17282@upf.edu> Message-ID: <20130917151438.GD3055@murraytwins.com> On Sat, Sep 14, 2013 at 06:25:21PM +0200, Walter Garcia-Fontes wrote: > * John Kim, thinkndev at gmail.com [14/09/13 17:57]: > > Wow, that's a lot of bugs. Is the only task to mark bugs as confirmed? What else can be done by someone without triaging rights? > > If by triaging rights you mean the right to mark a bug as "triaged", > don't worry, I don't have it either (only members of the bug control > team have that right, as far as I know). Yes, only members of the Ubuntu Bug Control team can set a bug task's status to Triaged or set the importance for a bug report. However, there are many things that can be done to improve[1] a bug report. For example, documenting steps to recreate the bug, adding tags to the bug report, and more. [1] https://wiki.ubuntu.com/Bugs/Improving -- Brian Murray From brian at ubuntu.com Tue Sep 17 15:18:31 2013 From: brian at ubuntu.com (Brian Murray) Date: Tue, 17 Sep 2013 08:18:31 -0700 Subject: Opened a page for triage for the Global Jam In-Reply-To: <20130914165238.GC17282@upf.edu> References: <20130914152604.GA17282@upf.edu> <761029ff-1ce2-4e94-b857-de1ef4b177fb@email.android.com> <20130914162521.GB17282@upf.edu> <20130914165238.GC17282@upf.edu> Message-ID: <20130917151831.GE3055@murraytwins.com> On Sat, Sep 14, 2013 at 06:52:38PM +0200, Walter Garcia-Fontes wrote: > * Jack Ramsay, jack at troop55.net [14/09/13 18:46]: > > How do I mark a bug off on the wiki page I have nothing to do I can tackle > > a bunch of bugs > > Just edit the page and write after the first > brackets ( [[ ) without any space, and put your name at the end. Check > the first bugs where I have done it myself and just do the same, but > put your name. There is also the hugday script which is part of the ubuntu-qa-tools bzr branch which makes, or used to make, this easier. https://launchpad.net/ubuntu-qa-tools -- Brian Murray Ubuntu Bug Master From es20490446e at gmail.com Tue Sep 17 20:35:14 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Tue, 17 Sep 2013 22:35:14 +0200 Subject: What we have learned from the Bug Day Message-ID: <5238BD02.5090402@gmail.com> Walteeerr! all the bugs for the Bug Day are from 2011?! Almost all are EOL! 😵 And something relevant: http://youtu.be/aOKa_IIyLJE Greetings -------------- 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 thinkndev at gmail.com Wed Sep 18 00:32:11 2013 From: thinkndev at gmail.com (John Kim) Date: Tue, 17 Sep 2013 17:32:11 -0700 Subject: What we have learned from the Bug Day In-Reply-To: <5238BD02.5090402@gmail.com> References: <5238BD02.5090402@gmail.com> Message-ID: <81a04fce-b7a8-4a44-87f4-92af8ae96a93@email.android.com> Now what? :-( none of the bugs are worth treating? Where should a prospective bugsquad start? Alberto Salvia Novella wrote: >Walteeerr! all the bugs for the Bug Day are from 2011?! Almost all are >EOL! 😵 > >And something relevant: http://youtu.be/aOKa_IIyLJE > >Greetings > > > >------------------------------------------------------------------------ > >-- >Ubuntu-bugsquad mailing list >Ubuntu-bugsquad at lists.ubuntu.com >https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jack at troop55.net Wed Sep 18 00:34:12 2013 From: jack at troop55.net (Jack Ramsay) Date: Tue, 17 Sep 2013 19:34:12 -0500 Subject: What we have learned from the Bug Day In-Reply-To: <81a04fce-b7a8-4a44-87f4-92af8ae96a93@email.android.com> References: <5238BD02.5090402@gmail.com> <81a04fce-b7a8-4a44-87f4-92af8ae96a93@email.android.com> Message-ID: Yeah I don't understand On Sep 17, 2013 7:32 PM, "John Kim" wrote: > Now what? :-( none of the bugs are worth treating? Where should a > prospective bugsquad start? > > Alberto Salvia Novella wrote: >> >> Walteeerr! all the bugs for the Bug Day are from 2011?! Almost all are >> EOL! >> >> And something relevant: http://youtu.be/aOKa_IIyLJE >> >> Greetings >> >> -- >> Ubuntu-bugsquad mailing list >> Ubuntu-bugsquad at lists.ubuntu.com >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad >> >> > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > > -- > 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 walter.garcia at upf.edu Wed Sep 18 05:21:59 2013 From: walter.garcia at upf.edu (Walter Garcia-Fontes) Date: Wed, 18 Sep 2013 07:21:59 +0200 Subject: What we have learned from the Bug Day Message-ID: <20130918052159.GA32679@upf.edu> > Alberto Salvia Novella wrote: > >Walteeerr! all the bugs for the Bug Day are from 2011?! Almost all are > >EOL! 😵 You're talking about the ones marked "Confirmed", in the "New" list there are reports until right the moment before I downloaded the list. In any case I think one of the tasks of the bug squad is to review this old never attended bugs, ask the users if they still see the issue (there are some issues that survive for a long time because only very particular combination of steps reproduce them, but that still should be fixed if they can be reproduced). A bug reported in a no longer supported version should not be closed because of that, but because it is invalid or because the reporter does not provide more information. In any case, good job everybody! It is not bad that we have reduced the number of unattended bugs in the "Unity" package quite significantly in a couple of days. There are still some bugs to review if anybody wants to help. * John Kim, thinkndev at gmail.com [18/09/13 02:32]: > Now what? :-( none of the bugs are worth treating? Where should a > prospective bugsquad start? > That's life! In my experience 99% of the reports are either incomplete (lack information to reproduce), invalid or non reproducible. A lot others are opinions, feature requests. And don't forget the main goal of this squad is triaging, not fixing bugs. -- Walter Garcia-Fontes From es20490446e at gmail.com Wed Sep 18 14:35:06 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Wed, 18 Sep 2013 16:35:06 +0200 Subject: What we have learned from the Bug Day In-Reply-To: <20130918052159.GA32679@upf.edu> References: <20130918052159.GA32679@upf.edu> Message-ID: <5239BA1A.9010403@gmail.com> The 18/09/13 07:21, Walter Garcia-Fontes wrote: > I think one of the tasks of the bug squad is to review this old never attended bugs, ask the users if they still see the issue /I agree, but I also see bugs for the //*latest release*//of being of much higher interest in general./ The 18/09/13 07:21, Walter Garcia-Fontes wrote: > In any case, good job everybody! /*Thanks*//for your dedication, specially to Walter for organizing the Day.// // //I also find that small contributions are also appreciated, since this is not about where we must get to but how much//can we help./ The 18/09/13 07:21, Walter Garcia-Fontes wrote: > It is not bad that we have reduced the number of unattended bugs in the "Unity" package quite significantly in a couple of days. /Yes, many of them //*began to move*//after the Bug Day. Perhaps one day we will see a massive contribution in the Bug Day, but it seems we have to do the path before anyone wants to travel it.// // //Till then, good luck./ The 18/09/13 07:21, Walter Garcia-Fontes wrote: > That's life! In my experience 99% of the reports are either incomplete > (lack information to reproduce), invalid or non reproducible. /In mine, when you //*learn*//how to search Launchpad and read the bugs, you can rapidly bypass the irrelevant ones and get tons of bugs which your contribution will be appreciated./ The 18/09/13 07:21, Walter Garcia-Fontes wrote: > And don't forget the main goal of this squad is triaging, not fixing > bugs. /I think this to be the golden rule; to //*focus*//in the job that no one else can do, or will do in a higher expenditure of time:// / * /*Reporters*//to write bug reports and to improve them as asked./ * /*BugSquad*//to confirm bug reports and to notify them upstream// / * /*BugControl*//to review bugs reports with higher probability of being ready to be workable/ * /*Programers*////to patch triaged bugs/ /Have a nice day all/ -------------- 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 hggdh2 at ubuntu.com Wed Sep 18 15:52:40 2013 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Wed, 18 Sep 2013 10:52:40 -0500 Subject: What we have learned from the Bug Day In-Reply-To: <5239BA1A.9010403@gmail.com> References: <20130918052159.GA32679@upf.edu> <5239BA1A.9010403@gmail.com> Message-ID: <20130918105240.05242ba6@xango3> On Wed, 18 Sep 2013 16:35:06 +0200 Alberto Salvia Novella wrote: > The 18/09/13 07:21, Walter Garcia-Fontes wrote: > > I think one of the tasks of the bug squad is to review this old > > never attended bugs, ask the users if they still see the issue Certainly. > /I agree, but I also see bugs for the //*latest release*//of being of > much higher interest in general./ The sad fact is we have many more bugs reported than we can timely look at. But another sad fact is that a bug is not more, or less, important just based on its age. All open bugs, still untriaged, should be looked at. If a bug was reported for a release that is now EOL, we still have to check if it is applicable for the currently-supported releases. If it is, then we should mark it as so (by adding a comment describing the current version(s) affected, tagging with an updated release, and -- in general -- triaging it. Note that triaging also means setting the importance. Ubuntu, or any other distribution, is not only make of the current, in-development version. > The 18/09/13 07:21, Walter Garcia-Fontes wrote: > > That's life! In my experience 99% of the reports are either > > incomplete (lack information to reproduce), invalid or non > > reproducible. > /In mine, when you //*learn*//how to search Launchpad and read the > bugs, you can rapidly bypass the irrelevant ones and get tons of bugs > which your contribution will be appreciated./ This brings up a different pet-peeve of mine: bugs are *technical* reports. They should be opened by *technical-savvy* people. A BTS should, then, be a restricted resource, with new bugs being "promoted" from non-technical reports written elsewhere (like answers.ubuntu.com, sort of abandoned nowadays, or ask.ubuntu.com, or whatever). But this is a different discussion. > The 18/09/13 07:21, Walter Garcia-Fontes wrote: > > And don't forget the main goal of this squad is triaging, not > > fixing bugs. > /I think this to be the golden rule; to //*focus*//in the job that no > one else can do, or will do in a higher expenditure of time:// > / > > * /*Reporters*//to write bug reports and to improve them as asked./ > * /*BugSquad*//to confirm bug reports and to notify them upstream// > / > * /*BugControl*//to review bugs reports with higher probability of > being ready to be workable/ > * /*Programers*////to patch triaged bugs/ Indeed. Cheers, ..C.. -- ab alio expectes alteri quod feceris -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From es20490446e at gmail.com Wed Sep 18 16:11:08 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Wed, 18 Sep 2013 18:11:08 +0200 Subject: What we have learned from the Bug Day In-Reply-To: <20130918105240.05242ba6@xango3> References: <20130918052159.GA32679@upf.edu> <5239BA1A.9010403@gmail.com> <20130918105240.05242ba6@xango3> Message-ID: <5239D09C.3060502@gmail.com> El 18/09/13 17:52, C de-Avillez escribió: > ab alio expectes alteri quod feceris Oh; just what I needed, just like magic. Reading this helped me to clear a matter I has been thinking for a while. And thanks for the appointments. I found them of much interest. -------------- 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 cshubhamrao at gmail.com Wed Sep 18 16:47:45 2013 From: cshubhamrao at gmail.com (cshubhamrao at gmail.com) Date: Wed, 18 Sep 2013 22:17:45 +0530 Subject: Prepare for new release In-Reply-To: References: Message-ID: <701F820E-2062-4CD6-AD81-925A5F349BF2@gmail.com> How to prepare for the newer release of Ubuntu? I know there's still time. From dtl131 at gmail.com Wed Sep 18 18:54:16 2013 From: dtl131 at gmail.com (Daniel Letzeisen) Date: Wed, 18 Sep 2013 14:54:16 -0400 Subject: What we have learned from the Bug Day In-Reply-To: <20130918105240.05242ba6@xango3> References: <20130918052159.GA32679@upf.edu> <5239BA1A.9010403@gmail.com> <20130918105240.05242ba6@xango3> Message-ID: <5239F6D8.5060506@gmail.com> On 09/18/2013 11:52 AM, C de-Avillez wrote: > This brings up a different pet-peeve of mine: bugs are *technical* > reports. They should be opened by *technical-savvy* people. A BTS > should, then, be a restricted resource, with new bugs being "promoted" > from non-technical reports written elsewhere (like answers.ubuntu.com, > sort of abandoned nowadays, or ask.ubuntu.com, or whatever). But this > is a different discussion. It's not an entirely different discussionand it's one worth having.I often feel the same way, but I think a restricted bug tracker would be a step in the wrong direction. What I would rather see is apport defaulting (or otherwise not-so-gently encouraging users) to create support requests at answers.launchpad.net/ubuntu and those questions being converted to bugs by bug squad members. Currently, it's being done in the opposite direction, and "Convert to question" is still one of the more underused tools in the toolbox. The answer tracker has some things going for it: - Questions expire if they remain open or incomplete for 15 days (I would like to star this 1,000 times to emphasize its importance) - Users are less likely to suffer from the delusion that they're talking to canonical devs/employees - Lacks some forum features that are unnecessary - signatures, bean counts, avatars, etc. And some drawbacks: - A relatively low ratio of helpers/helpees, probably even lower than ubuntuforums or askubuntu - Lacks more helpful forum features - editing posts, code tags, stickies etc. All that said, I still think users should be able to file bug reports directly (via Launchpad and apport) if they strongly feel their issue is a bug. > But another sad fact is that a bug is not more, or less, important just > based on its age. Maybe in theory, but my experience has been that most bugs filed with currently EOL releases (especially unconfirmed ones) fall into one or more of the following categories: - Already fixed upstream - Aren't reproducible in modern versions - Need more info and the OP won't respond Sometimes, I have my own personal bug days where I pick a package I like and go wading through the ancient reports. If I can't reproduce and ask the user whether they are still experiencing the issue, it's extremely rare that they'll respond. So I have to disagree with the "bug age has no correlation to importance" meme. From es20490446e at gmail.com Thu Sep 19 13:45:45 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Thu, 19 Sep 2013 15:45:45 +0200 Subject: Prepare for new release In-Reply-To: <701F820E-2062-4CD6-AD81-925A5F349BF2@gmail.com> References: <701F820E-2062-4CD6-AD81-925A5F349BF2@gmail.com> Message-ID: <523B0009.8030902@gmail.com> El 18/09/13 18:47, cshubhamrao at gmail.com escribió: > How to prepare for the newer release of Ubuntu? I know there's still time. > Sorry, but I don't understand the question. What do you mean with 'prepare'? -------------- 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 hggdh2 at ubuntu.com Tue Sep 24 19:03:55 2013 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Tue, 24 Sep 2013 14:03:55 -0500 Subject: What we have learned from the Bug Day In-Reply-To: <5239F6D8.5060506@gmail.com> References: <20130918052159.GA32679@upf.edu> <5239BA1A.9010403@gmail.com> <20130918105240.05242ba6@xango3> <5239F6D8.5060506@gmail.com> Message-ID: On Wed, Sep 18, 2013 at 1:54 PM, Daniel Letzeisen wrote: > On 09/18/2013 11:52 AM, C de-Avillez wrote: > >> This brings up a different pet-peeve of mine: bugs are *technical* >> reports. They should be opened by *technical-savvy* people. A BTS should, >> then, be a restricted resource, with new bugs being "promoted" from >> non-technical reports written elsewhere (like answers.ubuntu.com, sort >> of abandoned nowadays, or ask.ubuntu.com, or whatever). But this is a >> different discussion. >> > > It's not an entirely different discussionand it's one worth having.I often > feel the same way, but I think a restricted bug tracker would be a step in > the wrong direction. If it is done by itself, it certainly would be a step in the wrong direction. It would have to be done as part of a larger effort, and would *require* integration with some other mean(s) for users to report their issues, or ask for help. The keyword here, methinks, is integration. > What I would rather see is apport defaulting (or otherwise not-so-gently > encouraging users) to create support requests at > answers.launchpad.net/ubuntu and those questions being converted to bugs > by bug squad members. Currently, it's being done in the opposite direction, > and "Convert to question" is still one of the more underused tools in the > toolbox. > Actually, one should be able to to link to a bug from answers.lp.c. > The answer tracker has some things going for it: > - Questions expire if they remain open or incomplete for 15 days (I would > like to star this 1,000 times to emphasize its importance) > - Users are less likely to suffer from the delusion that they're talking > to canonical devs/employees > - Lacks some forum features that are unnecessary - signatures, bean > counts, avatars, etc. > > And some drawbacks: > - A relatively low ratio of helpers/helpees, probably even lower than > ubuntuforums or askubuntu > - Lacks more helpful forum features - editing posts, code tags, stickies > etc. > > All that said, I still think users should be able to file bug reports > directly (via Launchpad and apport) if they strongly feel their issue is a > bug. I am not 100% against it. But, in this case, I would like to be able to unilaterally close the bug invalid if the minimum required data is not there. > > > But another sad fact is that a bug is not more, or less, important just >> based on its age. >> > > Maybe in theory, but my experience has been that most bugs filed with > currently EOL releases (especially unconfirmed ones) fall into one or more > of the following categories: > - Already fixed upstream > - Aren't reproducible in modern versions > - Need more info and the OP won't respond > > Sometimes, I have my own personal bug days where I pick a package I like > and go wading through the ancient reports. If I can't reproduce and ask the > user whether they are still experiencing the issue, it's extremely rare > that they'll respond. So I have to disagree with the "bug age has no > correlation to importance" meme. > I agree, but I would also like to point out that correlation is not causation. Some bugs are more prone to go away with time: presentation bugs, for example. The whole point is we cannot be *sure*. And... what is new today will be old tomorrow... I welcome this discussion. We had a session about that during the last UDS [1]. I am trying to get more involvement/opinions from bugsquadders/controllers, so that we can present something more polished as an option/plan-of-action. [1] https://blueprints.launchpad.net/ubuntu/+spec/community-1308-quality-reporting-bugs -- ..hggdh.. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dtl131 at gmail.com Wed Sep 25 03:50:41 2013 From: dtl131 at gmail.com (Daniel Letzeisen) Date: Tue, 24 Sep 2013 23:50:41 -0400 Subject: What we have learned from the Bug Day In-Reply-To: References: <20130918052159.GA32679@upf.edu> <5239BA1A.9010403@gmail.com> <20130918105240.05242ba6@xango3> <5239F6D8.5060506@gmail.com> Message-ID: <52425D91.7040601@gmail.com> On 09/24/2013 03:03 PM, C de-Avillez wrote: > Actually, one should be able to to link to a bug from answers.lp.c. Yes, but that doesn't close the question and convert it into a bug, and then further conversation occurs in both the question and bug, which leads to confusion IMO. > I am not 100% against it. But, in this case, I would like to be able > to unilaterally close the bug invalid if the minimum required data is > not there. Agreed. If an advanced user goes out of the way to file a bug report directly not using the tools, s/he should have some technical insight into the issue or it's a really obvious bug (like a typo in a package description). > I agree, but I would also like to point out that correlation is not > causation. Some bugs are more prone to go away with time: presentation > bugs, for example. The whole point is we cannot be *sure*. And... what > is new today will be old tomorrow... I understand, but I really bugs from EOL releases that haven't been touched in years (I call them "ghost bugs"). I'd love it if every bug was tagged with an associated release(s), and once all the releases were EOL, the bug would automatically become Incomplete and Expire unless a user indicated it still affects them in a current release. From es20490446e at gmail.com Wed Sep 25 10:31:39 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Wed, 25 Sep 2013 12:31:39 +0200 Subject: What we have learned from the Bug Day In-Reply-To: <52425D91.7040601@gmail.com> References: <20130918052159.GA32679@upf.edu> <5239BA1A.9010403@gmail.com> <20130918105240.05242ba6@xango3> <5239F6D8.5060506@gmail.com> <52425D91.7040601@gmail.com> Message-ID: <5242BB8B.3010108@gmail.com> El 25/09/13 05:50, Daniel Letzeisen escribió: > >> I am not 100% against it. But, in this case, I would like to be able >> to unilaterally close the bug invalid if the minimum required data is >> not there. > Agreed. If an advanced user goes out of the way to file a bug report > directly not using the tools, s/he should have some technical insight > into the issue or it's a really obvious bug (like a typo in a package > description). > I think marking it as 'incomplete' and asking the user for further information is enough; since the bot 'Lauchpad Janitor' will clean it automatically in 60 days, and there's no need for the user to write a new report if he's interested in helping. El 25/09/13 05:50, Daniel Letzeisen escribió: > I'd love it if every bug was tagged with an associated release(s), and > once all the releases were EOL, the bug would automatically become > Incomplete and Expire unless a user indicated it still affects them in > a current release. > Yes, a good solution will be perhaps a bot marking the report as 'incomplete' and saying: Please, if you are still experiencing this bug: - Change its status to 'confirmed' or 'triaged' - Tag it with the names of the Ubuntu releases where you find it (https://wiki.ubuntu.com/Releases) Also will be a good idea the bot to complete the tag list of 'confirmed' bugs with the names of currently supported releases from the release the bug has been notified to the latest tagged. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2260 bytes Desc: Firma criptográfica S/MIME URL: From dtl131 at gmail.com Thu Sep 26 00:49:01 2013 From: dtl131 at gmail.com (Daniel Letzeisen) Date: Wed, 25 Sep 2013 20:49:01 -0400 Subject: What we have learned from the Bug Day In-Reply-To: <5242BB8B.3010108@gmail.com> References: <20130918052159.GA32679@upf.edu> <5239BA1A.9010403@gmail.com> <20130918105240.05242ba6@xango3> <5239F6D8.5060506@gmail.com> <52425D91.7040601@gmail.com> <5242BB8B.3010108@gmail.com> Message-ID: <5243847D.9010001@gmail.com> On 09/25/2013 06:31 AM, Alberto Salvia Novella wrote: > I think marking it as 'incomplete' and asking the user for further > information is enough; since the bot 'Lauchpad Janitor' will clean it > automatically in 60 days, and there's no need for the user to write a > new report if he's interested in helping. That's usually what I do, but some people prefer to quickly close bugs with no logs where the user simply says "I don't know" or "???", etc. C de-Avillez is referring to doing that for bugs filed directly/manually without apport. For bugs filed manually, I still think LP should use something like Debian's reportbug template that asks the user the basic questions (which you're free to delete if they're not applicable) that I/we have copied/pasted so many times: https://wiki.ubuntu.com/Bugs/Responses#Not_described_well -------------- next part -------------- An HTML attachment was scrubbed... URL: From es20490446e at gmail.com Thu Sep 26 15:13:22 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Thu, 26 Sep 2013 17:13:22 +0200 Subject: What we have learned from the Bug Day In-Reply-To: <5243847D.9010001@gmail.com> References: <20130918052159.GA32679@upf.edu> <5239BA1A.9010403@gmail.com> <20130918105240.05242ba6@xango3> <5239F6D8.5060506@gmail.com> <52425D91.7040601@gmail.com> <5242BB8B.3010108@gmail.com> <5243847D.9010001@gmail.com> Message-ID: <52444F12.5050608@gmail.com> El 26/09/13 02:49, Daniel Letzeisen escribió: > C de-Avillez is referring to doing that for bugs filed > directly/manually without apport. These are most of the bugs that belong to Ubuntu 11.04 and 11.10. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2260 bytes Desc: Firma criptográfica S/MIME URL: From wvan13 at gmail.com Sat Sep 28 17:52:34 2013 From: wvan13 at gmail.com (William Van Hevelingen) Date: Sat, 28 Sep 2013 10:52:34 -0700 Subject: What we have learned from the Bug Day In-Reply-To: <52425D91.7040601@gmail.com> References: <20130918052159.GA32679@upf.edu> <5239BA1A.9010403@gmail.com> <20130918105240.05242ba6@xango3> <5239F6D8.5060506@gmail.com> <52425D91.7040601@gmail.com> Message-ID: > I agree, but I would also like to point out that correlation is not >> causation. Some bugs are more prone to go away with time: presentation >> bugs, for example. The whole point is we cannot be *sure*. And... what is >> new today will be old tomorrow... >> > > I understand, but I really bugs from EOL releases that haven't been > touched in years (I call them "ghost bugs"). I'd love it if every bug was > tagged with an associated release(s), and once all the releases were EOL, > the bug would automatically become Incomplete and Expire unless a user > indicated it still affects them in a current release. > > +1 It's a waste to expect triagers to be looking at bugs on EOL releases when there's a flood of current bugs that need attention. -- Thanks, William -------------- next part -------------- An HTML attachment was scrubbed... URL: From webmaster at ubuntu.com Sat Sep 28 14:16:18 2013 From: webmaster at ubuntu.com (Help Ubuntu) Date: Sat, 28 Sep 2013 14:16:18 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_penalvch?= Message-ID: <20130928141618.5715.27473@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Community Ubuntu Documentation" for change notification. The "ReportingBugs" page has been changed by penalvch: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=244&rev2=245 Comment: Due to LP#1171003 et. el. added statement on how BIOS release notes tend not to cover linux. Common response to update requests is "Well the release notes don't talk about it..." Thank you for reading this article. This will guide you on how best to present your bug report so that it gets addressed as soon as possible. Here are a few guiding principles that lead to success in getting bugs fixed: <
><
> - Before filing any hardware related reports on Launchpad, please '''update''' your BIOS, and hardware firmware (CF card readers, SSDs, USB 3.0 controllers, DVD/CD drives, etc.) to the newest available from your vendor. Outdated and buggy BIOS and firmware is a common cause of a variety of hardware issues (ex. intermittent wireless, suspend not working, certain keys on keyboard not working correctly, card readers not working, and kernel panics after plugging USB drive in). If your vendor has a newer version of the BIOS on their website, and you have not updated to this, your report is considered [[https://wiki.ubuntu.com/Bugs/Status|Status Incomplete]] whether or not someone toggled the Status of your report. + Before filing any hardware related reports on Launchpad, please '''update''' your BIOS, and hardware firmware (CF card readers, SSDs, USB 3.0 controllers, DVD/CD drives, etc.) to the newest available from your vendor. Outdated and buggy BIOS and firmware is a common cause of a variety of hardware issues (ex. intermittent wireless, suspend not working, certain keys on keyboard not working correctly, card readers not working, and kernel panics after plugging USB drive in). As well, because BIOS vendors tend test to Windows and make release notes commenting on results to it, it wouldn't advise on if a problem in linux is resolved by it. Hence, one should update anyways, even if your problem isn't specifically mentioned. In summation, if your vendor has a newer version of the BIOS on their website, and you have not updated to this, your report is considered [[https://wiki.ubuntu.com/Bugs/Status|Status Incomplete]] whether or not someone toggled the Status of your report. <
><
> Please do not speculate on what you think is or isn't a duplicate report (ex. I googled around and found bug report...). This is largely unhelpful as it tends not to be a duplicate, and already has been or easily done by triagers and developers. Instead, ensuring the report has all the requested testing information performed would be the fastest way to ensure your bug is resolved as soon as possible. <
><
> From martellif67 at gmail.com Sun Sep 29 13:11:59 2013 From: martellif67 at gmail.com (Franco Martelli) Date: Sun, 29 Sep 2013 15:11:59 +0200 Subject: Kubuntu 13.10 beta2 amd64 installation report Message-ID: <5248271F.4040000@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, installation process doesn't ask for root password forcing user to use "sudo passwd" command in order to change it once installation is completed Installation process in italian language still contain untranslated items On my system installation process once completed successfully at the end return a black screen waiting user to hit "Enter" key to reboot but he isn't advised on this. TIA Best regards. P.S. I'm not on mailing list, please cc to me your email. - -- Franco Martelli -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJSSCceAAoJEFM/ma7n+T+7qR0H/RnO0cdz5iJL4wIFt1pCx358 n/OhG6KSZQSnulxkukbUqkoNCSg9LsyoeyT8SeZViqYIsB3EkP8u/YJlLuqZB+oi mP1efc4evXoJDBWZI7NFP22zpJ9oitJj/Gs6PPFt5JDuwzLgl4tSSNe4pdArjOFo e7idqS/F4pq4AVhCSGnl7iHBbBEmte222k9NclcDsf1UeEBnN4m9FBOwZSqRfEYf KwIFcgoC6SMB14XFN0fVuWlZS3lfBW6QF1YgIgS9N86xlaMQYIGVAduxk7OGxwwH +SBPtB7CUb2Qy3guOQM/jbEA8T5Rz7FQ8LKjIoIWKCJJY/2nLbMPrQs/6VBKoz0= =8SmG -----END PGP SIGNATURE----- From jack at troop55.net Sun Sep 29 21:47:14 2013 From: jack at troop55.net (Jack Ramsay) Date: Sun, 29 Sep 2013 16:47:14 -0500 Subject: Kubuntu 13.10 beta2 amd64 installation report In-Reply-To: <5248271F.4040000@gmail.com> References: <5248271F.4040000@gmail.com> Message-ID: Its still a beta release there's the translation page on the Ubuntu launchpad page. Check the status there On Sep 29, 2013 4:45 PM, "Franco Martelli" wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > installation process doesn't ask for root password forcing user to use > "sudo passwd" command in order to change it once installation is completed > > Installation process in italian language still contain untranslated items > > On my system installation process once completed successfully at the > end return a black screen waiting user to hit "Enter" key to reboot > but he isn't advised on this. > TIA > Best regards. > > P.S. > I'm not on mailing list, please cc to me your email. > > - -- > Franco Martelli > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.12 (GNU/Linux) > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQEcBAEBAgAGBQJSSCceAAoJEFM/ma7n+T+7qR0H/RnO0cdz5iJL4wIFt1pCx358 > n/OhG6KSZQSnulxkukbUqkoNCSg9LsyoeyT8SeZViqYIsB3EkP8u/YJlLuqZB+oi > mP1efc4evXoJDBWZI7NFP22zpJ9oitJj/Gs6PPFt5JDuwzLgl4tSSNe4pdArjOFo > e7idqS/F4pq4AVhCSGnl7iHBbBEmte222k9NclcDsf1UeEBnN4m9FBOwZSqRfEYf > KwIFcgoC6SMB14XFN0fVuWlZS3lfBW6QF1YgIgS9N86xlaMQYIGVAduxk7OGxwwH > +SBPtB7CUb2Qy3guOQM/jbEA8T5Rz7FQ8LKjIoIWKCJJY/2nLbMPrQs/6VBKoz0= > =8SmG > -----END PGP SIGNATURE----- > > -- > 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 Sun Sep 29 21:53:30 2013 From: teward at ubuntu.com (Thomas Ward) Date: Sun, 29 Sep 2013 17:53:30 -0400 Subject: Kubuntu 13.10 beta2 amd64 installation report In-Reply-To: <5248271F.4040000@gmail.com> References: <5248271F.4040000@gmail.com> Message-ID: Franco, On Sun, Sep 29, 2013 at 9:11 AM, Franco Martelli wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > installation process doesn't ask for root password forcing user to use > "sudo passwd" command in order to change it once installation is completed Ubuntu doesn't configure a root password by default. Unlike other distributions which do that, Ubuntu does not set the root password by default. The user who is set up during installation will have the ability to use `sudo` to run commands with the superuser permission set, and it has been that way for a long long time. > > Installation process in italian language still contain untranslated items This information may need to be referred to the Translations team. > > On my system installation process once completed successfully at the > end return a black screen waiting user to hit "Enter" key to reboot > but he isn't advised on this. This might be a bug against `ubiquity` and should probably be filed as such. > TIA > Best regards. > > P.S. > I'm not on mailing list, please cc to me your email. > > - -- > Franco Martelli > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.12 (GNU/Linux) > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQEcBAEBAgAGBQJSSCceAAoJEFM/ma7n+T+7qR0H/RnO0cdz5iJL4wIFt1pCx358 > n/OhG6KSZQSnulxkukbUqkoNCSg9LsyoeyT8SeZViqYIsB3EkP8u/YJlLuqZB+oi > mP1efc4evXoJDBWZI7NFP22zpJ9oitJj/Gs6PPFt5JDuwzLgl4tSSNe4pdArjOFo > e7idqS/F4pq4AVhCSGnl7iHBbBEmte222k9NclcDsf1UeEBnN4m9FBOwZSqRfEYf > KwIFcgoC6SMB14XFN0fVuWlZS3lfBW6QF1YgIgS9N86xlaMQYIGVAduxk7OGxwwH > +SBPtB7CUb2Qy3guOQM/jbEA8T5Rz7FQ8LKjIoIWKCJJY/2nLbMPrQs/6VBKoz0= > =8SmG > -----END PGP SIGNATURE----- > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad ------ Thomas From andrewjr911 at gmail.com Sun Sep 29 21:50:22 2013 From: andrewjr911 at gmail.com (Andrew Rufkahr) Date: Sun, 29 Sep 2013 17:50:22 -0400 Subject: Unsubscribe Message-ID: I wish to no longer receive emails from this list, yet I can't seem to remove myself from the mailing list. Clicking unsubscribe does not send me an email for a link to follow. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jack at troop55.net Sun Sep 29 22:08:34 2013 From: jack at troop55.net (Jack Ramsay) Date: Sun, 29 Sep 2013 17:08:34 -0500 Subject: Unsubscribe In-Reply-To: References: Message-ID: To unsubscribe click the link at the bottom of this email On Sep 29, 2013 5:03 PM, "Andrew Rufkahr" wrote: > I wish to no longer receive emails from this list, yet I can't seem to > remove myself from the mailing list. Clicking unsubscribe does not send me > an email for a link to follow. > > -- > 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 es20490446e at gmail.com Sun Sep 29 22:26:56 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Mon, 30 Sep 2013 00:26:56 +0200 Subject: Unmentioned bug tag in the wiki Message-ID: <5248A930.4020306@gmail.com> Apport retracing service added the 'bugpattern-needed' tag to bug #1098266 , but this tag is not mentioned in the wiki . -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2260 bytes Desc: Firma criptográfica S/MIME URL: From es20490446e at gmail.com Sun Sep 29 22:38:38 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Mon, 30 Sep 2013 00:38:38 +0200 Subject: Broken link in the wiki Message-ID: <5248ABEE.4080400@gmail.com> 'Upstream' page has a link to 'The Upstream Report' page, but the second one can't be found. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2260 bytes Desc: Firma criptográfica S/MIME URL: From dtl131 at gmail.com Sun Sep 29 23:49:46 2013 From: dtl131 at gmail.com (Daniel Letzeisen) Date: Sun, 29 Sep 2013 19:49:46 -0400 Subject: Unmentioned bug tag in the wiki In-Reply-To: <5248A930.4020306@gmail.com> References: <5248A930.4020306@gmail.com> Message-ID: <5248BC9A.4070708@gmail.com> On 09/29/2013 06:26 PM, Alberto Salvia Novella wrote: > Apport retracing service added the > 'bugpattern-needed' tag to bug #1098266 > , but > this tag is not mentioned in the wiki . From what I gather, it's mostly for devs to limit bugmail about an issue which affects a lot of people when they're already aware of it and/or working on it. https://bugs.launchpad.net/ubuntu/+source/apport/+bug/487900 https://wiki.ubuntu.com/Apport/DeveloperHowTo#Bug_patterns -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian at ubuntu.com Mon Sep 30 22:05:43 2013 From: brian at ubuntu.com (Brian Murray) Date: Mon, 30 Sep 2013 15:05:43 -0700 Subject: Kubuntu 13.10 beta2 amd64 installation report In-Reply-To: References: <5248271F.4040000@gmail.com> Message-ID: <20130930220543.GC13842@murraytwins.com> On Sun, Sep 29, 2013 at 05:53:30PM -0400, Thomas Ward wrote: > Franco, > > On Sun, Sep 29, 2013 at 9:11 AM, Franco Martelli wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Hi, > > installation process doesn't ask for root password forcing user to use > > "sudo passwd" command in order to change it once installation is completed > > Ubuntu doesn't configure a root password by default. Unlike other > distributions which do that, Ubuntu does not set the root password by > default. > > The user who is set up during installation will have the ability to > use `sudo` to run commands with the superuser permission set, and it > has been that way for a long long time. > > > > > Installation process in italian language still contain untranslated items > > This information may need to be referred to the Translations team. > > > > > On my system installation process once completed successfully at the > > end return a black screen waiting user to hit "Enter" key to reboot > > but he isn't advised on this. > > This might be a bug against `ubiquity` and should probably be filed as such. Actually, if I understand the situation correctly (and the user does not see the message that says something like "Remove the installation CD and press Enter to reboot") this is after the installation has completed and could be an issue with plymouth or the video driver. -- Brian Murray Ubuntu Bug Master From brian at ubuntu.com Mon Sep 30 22:12:11 2013 From: brian at ubuntu.com (Brian Murray) Date: Mon, 30 Sep 2013 15:12:11 -0700 Subject: Unmentioned bug tag in the wiki In-Reply-To: <5248BC9A.4070708@gmail.com> References: <5248A930.4020306@gmail.com> <5248BC9A.4070708@gmail.com> Message-ID: <20130930221211.GD13842@murraytwins.com> On Sun, Sep 29, 2013 at 07:49:46PM -0400, Daniel Letzeisen wrote: > On 09/29/2013 06:26 PM, Alberto Salvia Novella wrote: > >Apport retracing service added > >the 'bugpattern-needed' tag to bug #1098266 > >, > >but this tag is not mentioned in the wiki > >. > > From what I gather, it's mostly for devs to limit bugmail about an > issue which affects a lot of people when they're already aware of it > and/or working on it. > > https://bugs.launchpad.net/ubuntu/+source/apport/+bug/487900 > https://wiki.ubuntu.com/Apport/DeveloperHowTo#Bug_patterns Bug patterns are written to prevent the reporting of bug reports to Launchpad, thereby preventing needless triaging, and retracing work. Bug patterns can be written by anyone, but only members of the Ubuntu Bug Control team can commit to the bzr branch for them. I covered how to write bug patterns in an Ubuntu Developer Week class a bit ago. https://wiki.ubuntu.com/MeetingLogs/devweek1107/WorkingWithApportBugs -- Brian Murray Ubuntu Bug Master