From noreply at ubuntu.com Sun Mar 2 20:48:18 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 02 Mar 2014 20:48:18 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Ubuntu_Bug_Weekend/Confirm_?= =?utf-8?q?bugs=22_by_es20490446e?= Message-ID: <20140302204818.2146.86435@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Ubuntu Bug Weekend/Confirm bugs" page has been changed by es20490446e: http://wiki.ubuntu.com/Bugs/Ubuntu%20Bug%20Weekend/Confirm%20bugs?action=diff&rev1=7&rev2=8 == == - * /!\ '''Before confirming''' bugs, you need to have installed [[http://cdimage.ubuntu.com/daily-live/current/|Ubuntu 14.04 alpha]] in your machine. + * /!\ '''Before confirming''' bugs, you need to have installed [[http://cdimage.ubuntu.com/daily-live/current/|Ubuntu 14.04 daily built]] in your machine. - * ;) But if you want to use Ubuntu 14.04 '''without having''' to modify your system so far, you can just install the [[http://cdimage.ubuntu.com/daily-live/current/|daily built]] into the "[[https://www.virtualbox.org|Virtualbox]]" application (which is also available in the [[One%20Hundred%20Papercuts/The%20Ubuntu%20Software%20Center|Ubuntu Software Center]]). + * ;) But if you want to use Ubuntu 14.04 '''without having''' to modify your system so far, you can just install the [[http://cdimage.ubuntu.com/daily-live/current/|daily built]] into the "[[https://www.virtualbox.org|Virtualbox]]" application, which is also available in the [[One%20Hundred%20Papercuts/The%20Ubuntu%20Software%20Center|Ubuntu Software Center]] (you can follow this [[http://youtu.be/FNTFDnle3Hc|video-tutorial]]). * (!) If a bug report seems '''very hard''' for you to manage, you shall want to '''just ignore''' it and continue with a different one. * ;) Alternatively you can [[https://wiki.ubuntu.com/QATeam/Contact|ask for guidance]]. From noreply at ubuntu.com Sat Mar 1 14:10:27 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sat, 01 Mar 2014 14:10:27 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22LibreOfficeBugWrangling=22_by_pe?= =?utf-8?q?nalvch?= Message-ID: <20140301141027.19934.84535@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "LibreOfficeBugWrangling" page has been changed by penalvch: http://wiki.ubuntu.com/LibreOfficeBugWrangling?action=diff&rev1=23&rev2=24 Comment: Added GUI debug tip as this has been helpful in identifying the offending area, and may provide a WORKAROUND. * Please consult https://wiki.ubuntu.com/Apport to ensure Apport is enabled. * Please make sure LibreOffice debug symbols are installed (libreoffice-dbg, uno-libs3-dbg, and ure-dbg). * If this happened while a particular document was open or you were manipulating the document in a certain way, please attach that document to the bug report with detailed, click-for-click steps on how to reproduce the crash. + * For suspected GUI/desktop environment driven crashes (ex. reproducible in Kubuntu but not Xubuntu), please uninstall the packages libreoffice-gtk, libreoffice-gnome, libreoffice-gtk3, and libreoffice-kde and comment on if this changes anything. == The Whole system hangs or boots to the login screen == * For instances when you are using LibreOffice and either the system hangs requiring a hard reset or you are booted to the login screen, this is a bug in either xorg or the linux kernel. Please follow https://help.ubuntu.com/community/DebuggingSystemCrash . As well, if this happened while a particular document was open or you were manipulating the document, please attach that document to the bug report with detailed, click-for-click steps on how to reproduce the crash. From es20490446e at gmail.com Mon Mar 3 13:25:14 2014 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Mon, 03 Mar 2014 14:25:14 +0100 Subject: screen freezes on restart, start after shutdown and even sometimes even during shutdown In-Reply-To: <5310D243.7070105@iitk.ac.in> References: <5310D243.7070105@iitk.ac.in> Message-ID: <531482BA.7070707@gmail.com> What you need is to collect information for the specific package (called "nvidia-graphics-drivers"). Regards ? El 28/02/14 19:15, bhanuc escribió: > Hi all, > I have Lenevo Y500 , with ubuntu 14.04 installed on SSD (only storage > device) with Nvidia 650m with graphics driver version 331.49 . My > system is fully updated and I update almost daily. > Some backstory- > Installed 14.04 , installed nvidia driver then after a restart unity > launcher disappeared. I reinstalled nvidia driver( this had happened > in 13.10 and this has fixed it ) , no change so I instead of using > compiz-plugins I decided to install ubuntu-gnome and gnome-shell. This > fixed that problem but now when-ever I restarted ,after the lenevo > boot screen my screen freezes onto nothing and I have to > force-shutdown and restart it again which instead of leading to that > freeze screen it leads to grub screen and then ubuntu loads > gracefully. But recently the system started freezing even while > shutting down. There is no automatic error getting generated (so > cannot log a bug ) nor did I see any fishy in my system log. Can > anyone please help. I am kind of a newbie with all this so please let > me know where should I start looking to solve this problem. I have > attached all kinds of logs which I could find . > Thanks Warm Regards > Bhanu Pratap Chaudhary > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From es20490446e at gmail.com Mon Mar 3 13:57:56 2014 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Mon, 03 Mar 2014 14:57:56 +0100 Subject: =?UTF-8?B?8J+QniBVYnVudHUgQnVnIFdlZWtlbmQgd2lsbCBzdGFydCB0aGlzIHc=?= =?UTF-8?B?ZWVrZW5k?= Message-ID: <53148A64.8030704@gmail.com> 🐞 Ubuntu Bug Weekend The Ubuntu Bug Weekend will start this *Friday 7th*, and will last till the end of *Sunday 9th* (all in your time zone ). If you are willing to participate please *remember* to: * Write down your name under the desired list of contributors. * *Set up your environment* in advance if needed, what can easily be done like explained below: 🔧 For coders to fix papercuts Just *follow* the "Fixing a bug in Ubuntu " manual. 🔍 For anyone to confirm bugs 1. *Download* the Ubuntu 14.04 Daily Built 2. *Install* VirtualBox (also easily available in the Ubuntu Software Center ) 3. *Mount* the Ubuntu 14.04 Daily Built into VirtualBox (you can follow the video-tutorial ) If you have any *questions*, please ask . And have a nice day :) -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Header Type: image/png Size: 22930 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: icon_smile.png Type: image/png Size: 385 bytes Desc: not available URL: From noreply at ubuntu.com Mon Mar 3 20:41:12 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 03 Mar 2014 20:41:12 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Ubuntu_Bug_Weekend/Set_bug_?= =?utf-8?q?importances_contributors=22_by_chilicuil?= Message-ID: <20140303204112.29096.37703@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Ubuntu Bug Weekend/Set bug importances contributors" page has been changed by chilicuil: http://wiki.ubuntu.com/Bugs/Ubuntu%20Bug%20Weekend/Set%20bug%20importances%20contributors?action=diff&rev1=13&rev2=14 ||User||Time zone||Quantity of managed bugs||List of bugs|| ||[[https://launchpad.net/~es20490446e|es20490446e]]||+1||0||[[http://pad.ubuntu.com/ZxEgHwUrCC|List]]|| + ||[[https://launchpad.net/~chilicuil|chilicuil]]||-6||0||[[http://pad.ubuntu.com/QEswJyEtY3|List]]|| From es20490446e at gmail.com Thu Mar 6 12:55:10 2014 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Thu, 06 Mar 2014 13:55:10 +0100 Subject: Bug Weekend is about to start! Message-ID: <5318702E.4000006@gmail.com> The Ubuntu Bug Weekend will start tomorrow Friday 7th (in your time-zone) and will last till the end of Sunday 9th. The event is taking place at If you need assistance any time, you can: - email us at . - chat with us at Regards, and happy debugging. Hope this event will make a real difference in the incoming Ubuntu release. ☆ミ From noreply at ubuntu.com Fri Mar 7 19:29:32 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Fri, 07 Mar 2014 19:29:32 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Ubuntu_Bug_Weekend/Confirm_?= =?utf-8?q?bugs_contributors=22_by_jose?= Message-ID: <20140307192932.18060.29576@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Ubuntu Bug Weekend/Confirm bugs contributors" page has been changed by jose: http://wiki.ubuntu.com/Bugs/Ubuntu%20Bug%20Weekend/Confirm%20bugs%20contributors?action=diff&rev1=6&rev2=7 ||User||Time zone||Quantity of managed bugs||List of bugs|| ||[[https://launchpad.net/~es20490446e|es20490446e]]||+1||0||[[http://pad.ubuntu.com/q4FtQoa4pB|List]]|| + ||[[LaunchpadHome:jose]]||-5||0||[[http://pad.ubuntu.com/uvJlx2m2rS|List]]|| From noreply at ubuntu.com Fri Mar 7 19:30:44 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Fri, 07 Mar 2014 19:30:44 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Ubuntu_Bug_Weekend=22_by_ns?= =?utf-8?q?kaggs?= Message-ID: <20140307193044.22539.14577@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Ubuntu Bug Weekend" page has been changed by nskaggs: http://wiki.ubuntu.com/Bugs/Ubuntu%20Bug%20Weekend?action=diff&rev1=39&rev2=40 <> - == 🔖 Bug Controlers: Set bug importances == + == 🔖 Bug Controllers: Set bug importances == {{http://ubuntuone.com/0JDky4ounrEDuiZhMvV6Wx||height=225}} From noreply at ubuntu.com Sat Mar 8 14:05:20 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sat, 08 Mar 2014 14:05:20 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Ubuntu_Bug_Weekend/Confirm_?= =?utf-8?q?bugs_contributors=22_by_wiranvaud?= Message-ID: <20140308140520.23921.85936@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Ubuntu Bug Weekend/Confirm bugs contributors" page has been changed by wiranvaud: http://wiki.ubuntu.com/Bugs/Ubuntu%20Bug%20Weekend/Confirm%20bugs%20contributors?action=diff&rev1=7&rev2=8 Comment: adding my name to the list ||User||Time zone||Quantity of managed bugs||List of bugs|| ||[[https://launchpad.net/~es20490446e|es20490446e]]||+1||0||[[http://pad.ubuntu.com/q4FtQoa4pB|List]]|| ||[[LaunchpadHome:jose]]||-5||0||[[http://pad.ubuntu.com/uvJlx2m2rS|List]]|| + ||[[LaunchpadHome:wiranvaud]]||-3||0||[[http://pad.ubuntu.com/0xzjKez23s|List]]|| From noreply at ubuntu.com Sat Mar 8 16:03:12 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sat, 08 Mar 2014 16:03:12 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Ubuntu_Bug_Weekend/Confirm_?= =?utf-8?q?bugs_contributors=22_by_walter-garcia?= Message-ID: <20140308160312.6328.48821@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Ubuntu Bug Weekend/Confirm bugs contributors" page has been changed by walter-garcia: http://wiki.ubuntu.com/Bugs/Ubuntu%20Bug%20Weekend/Confirm%20bugs%20contributors?action=diff&rev1=8&rev2=9 ||[[https://launchpad.net/~es20490446e|es20490446e]]||+1||0||[[http://pad.ubuntu.com/q4FtQoa4pB|List]]|| ||[[LaunchpadHome:jose]]||-5||0||[[http://pad.ubuntu.com/uvJlx2m2rS|List]]|| ||[[LaunchpadHome:wiranvaud]]||-3||0||[[http://pad.ubuntu.com/0xzjKez23s|List]]|| + ||[[LaunchpadHome:walter-garcia]]||+1||0||[[http://pad.ubuntu.com/yCWnEPb8aL|List]]|| From noreply at ubuntu.com Sat Mar 8 16:51:08 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sat, 08 Mar 2014 16:51:08 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Ubuntu_Bug_Weekend/Confirm_?= =?utf-8?q?bugs_contributors=22_by_walter-garcia?= Message-ID: <20140308165108.9483.23339@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Ubuntu Bug Weekend/Confirm bugs contributors" page has been changed by walter-garcia: http://wiki.ubuntu.com/Bugs/Ubuntu%20Bug%20Weekend/Confirm%20bugs%20contributors?action=diff&rev1=9&rev2=10 ||[[https://launchpad.net/~es20490446e|es20490446e]]||+1||0||[[http://pad.ubuntu.com/q4FtQoa4pB|List]]|| ||[[LaunchpadHome:jose]]||-5||0||[[http://pad.ubuntu.com/uvJlx2m2rS|List]]|| ||[[LaunchpadHome:wiranvaud]]||-3||0||[[http://pad.ubuntu.com/0xzjKez23s|List]]|| - ||[[LaunchpadHome:walter-garcia]]||+1||0||[[http://pad.ubuntu.com/yCWnEPb8aL|List]]|| + ||[[LaunchpadHome:walter-garcia]]||+1||5||[[http://pad.ubuntu.com/yCWnEPb8aL|List]]|| From noreply at ubuntu.com Sat Mar 8 17:36:54 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sat, 08 Mar 2014 17:36:54 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Ubuntu_Bug_Weekend/Confirm_?= =?utf-8?q?bugs_contributors=22_by_walter-garcia?= Message-ID: <20140308173654.15439.55075@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Ubuntu Bug Weekend/Confirm bugs contributors" page has been changed by walter-garcia: http://wiki.ubuntu.com/Bugs/Ubuntu%20Bug%20Weekend/Confirm%20bugs%20contributors?action=diff&rev1=10&rev2=11 ||[[https://launchpad.net/~es20490446e|es20490446e]]||+1||0||[[http://pad.ubuntu.com/q4FtQoa4pB|List]]|| ||[[LaunchpadHome:jose]]||-5||0||[[http://pad.ubuntu.com/uvJlx2m2rS|List]]|| ||[[LaunchpadHome:wiranvaud]]||-3||0||[[http://pad.ubuntu.com/0xzjKez23s|List]]|| - ||[[LaunchpadHome:walter-garcia]]||+1||5||[[http://pad.ubuntu.com/yCWnEPb8aL|List]]|| + ||[[LaunchpadHome:walter-garcia]]||+1||7||[[http://pad.ubuntu.com/yCWnEPb8aL|List]]|| From es20490446e at gmail.com Mon Mar 10 13:23:01 2014 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Mon, 10 Mar 2014 14:23:01 +0100 Subject: Bug Weekend concluded Message-ID: <531DBCB5.2050609@gmail.com> Thank you for helping out in the Ubuntu Bug Weekend (http://tinyurl.com/nd89z8d), where bug management was more needed at this time. Additionally, the following people won a gift for their special contribution: * Javier López (chilicuil), for being so supportive and being the only participant in the previous round of the Bug Week, helping setting priority to 28 bugs. * Ross Gammon (retail-0), for being the one with the greatest contribution to the bug confirmation; not only in quantity but also in quality. * Walter Garcia-Fontes (walter-garcia), for being so close to being managed as many bugs as Ross Gammon; (although I see it has been not from the provided list and mainly not concerning the "Trusty" release, which is the one which can take more time to confirm 8-D ). Please email me telling what courtesy you want to receive and where. And, since this is not about how much we can't do but actually what we can do and feels good to us, the rest of help is also appreciated. Thank you. From walter.garcia at upf.edu Mon Mar 10 13:51:14 2014 From: walter.garcia at upf.edu (Walter Garcia-Fontes) Date: Mon, 10 Mar 2014 14:51:14 +0100 Subject: Bug Weekend concluded In-Reply-To: <531DBCB5.2050609@gmail.com> References: <531DBCB5.2050609@gmail.com> Message-ID: <20140310135114.GE8798@upf.edu> * Alberto Salvia Novella, es20490446e at gmail.com [10/03/14 14:24]: > * Walter Garcia-Fontes (walter-garcia), for being so close to being > managed as many bugs as Ross Gammon; (although I see it has been not > from the provided list and mainly not concerning the "Trusty" > release, which is the one which can take more time to confirm 8-D ). > > Please email me telling what courtesy you want to receive and where. Thanks Alberto for organizing this, on the courtesy to me don't worry, if you want you can send it to our Loco team and we can include it in the lottery that we run after each release party among the participants (send it to the team coordinator, you can find addresses at http://loco.ubuntu.com/teams/ubuntu.cat/). Now, some (constructive, hopefully) comments: 1) In the part of "confirming" bugs, first I think we discussed some months ago that confirming bugs is not the most important part of managing bugs, as there are a lot of confirmed bugs that where confirmed just because two users saw it. The most important part is, in my opinion, checking if the reporter can provide more information, and seeing if it can be triaged. Second I find it almost impossible to deal with bugs if I don't concentrate in specific packages, issues, and so on. Otherwise each bug is so different from the next that I never get on speed on dealing with them. 2) On the part of paper cuts, I find that the list was not very useful. None of those bugs were, in my humble opinion, really "bitesize". some of them wouldn't make sense to handle as an Ubuntu package as they where of an upstream nature, and so on. But again, thanks for the effort. Last comment is that I think, and this is something that we discussed also lot of times, old bugs shouldn't be ignored, and some effort should be dedicated to clean those old bugs. This is one of the easiest task for new bug triagers, but not a nice thing to do, users who get the first answer after several months of an unattended bug can dedicate you really nice insults, especially if they have moved away from Ubuntu long ago. But better late than never. -- Walter Garcia-Fontes From noreply at ubuntu.com Mon Mar 10 11:35:25 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 10 Mar 2014 11:35:25 -0000 Subject: =?utf-8?q?New_attachment_added_to_page_DebuggingProgramCrash_on_Ubuntu_Wi?= =?utf-8?q?ki?= Message-ID: <20140310113525.18508.59975@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page "DebuggingProgramCrash" for change notification. An attachment has been added to that page by staticd-growthecommons. Following detailed information is available: Attachment name: list-dbgsym-packages-v2.1.sh Attachment size: 2950 Attachment link: http://wiki.ubuntu.com/DebuggingProgramCrash?action=AttachFile&do=get&target=list-dbgsym-packages-v2.1.sh Page link: http://wiki.ubuntu.com/DebuggingProgramCrash From noreply at ubuntu.com Mon Mar 10 13:24:20 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 10 Mar 2014 13:24:20 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingProgramCrash=22_by_stat?= =?utf-8?q?icd-growthecommons?= Message-ID: <20140310132420.30167.18902@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingProgramCrash" page has been changed by staticd-growthecommons: http://wiki.ubuntu.com/DebuggingProgramCrash?action=diff&rev1=117&rev2=118 Comment: added new version of file. previous version failed to get the debugsyms for many packages due to interfering arch info on the line. }}} You can also use the Synaptic Package Manager to search for 'yelp-dbgsym' and install it from there. - The above procedure will install the debug symbol package for yelp only. Chances are that yelp uses shared libraries in other packages and debug symbols for them might be required in order to obtain a readable stack trace. You can download the [[attachment:list-symbols-packages-v2.sh]] shell script and run it (after a chmod a+x list-symbols-packages-v2.sh) this way: + The above procedure will install the debug symbol package for yelp only. Chances are that yelp uses shared libraries in other packages and debug symbols for them might be required in order to obtain a readable stack trace or perform other debugging tasks. - /!\ we updated [[attachment:list-dbgsym-packages-v2.sh]] to [[attachment:list-symbols-packages-v2.sh]]. This is the first change to make it compatible with newer GDB (which does not, by default, load all libraries at start anymore). -v2 is currently only working if you run it against a currently-executing binary (i.e., with '-p $(pidof '). + You can download the following [[attachment:list-symbols-packages-v2.1.sh |shell script (list-symbols-packages-v2.1.sh)]] to resolve all the dependencies. Attaching a debugger to an already running process may require elevated privileges even if you own the process. The following invocation will print out the list of files to install. + {{{#!highlight bash + sudo bash ./list-symbols-packages-v2.sh -p $(pidof yelp)}}} + To automatically install them apt can be called with the input from the script. The script is invoked with {{{-t}}} for a terse output without the descriptions of the packages and error messages are suppressed. + + {{{#!highlight bash - {{{ - bash list-symbols-packages-v2.sh yelp - }}} - in order to obtain a more complete list of symbol packages to install. The script may also attach to a running process and in this case it gives an even more complete list of symbol packages to install, and this is recommended if the problem you are having does not prevent you from running the program. You can usually get the process ID of a running process using pidof, so while you have yelp running you might run: - {{{ - bash list-symbols-packages-v2.sh -p $(pidof -s yelp) + sudo bash ./list-symbols-packages-v2.sh -t -p $(pidof yelp) 2>/dev/null|\ - }}} - to get a list of packages that should be installed for best debug information. If the running process is a server (daemon), you might have to run 'list-symbols-packages.sh' with sudo. + xargs -d $'\n' sudo apt-get install }}} + + /!\ Version 2 of this script makes it compatible with the newer GDB (which no longer loads all libraries at startup by default). -v2 currently only works if you run it against a currently-executing binary (i.e., with '-p $(pidof '). The [[attachment:list-symbols-packages.sh|older version]] of the script is also available. a. Now you make a [[Backtrace]]. a. You can also run [[Valgrind]], if the program crashes with a "Segmentation fault" or "Bus error". From noreply at ubuntu.com Mon Mar 10 14:48:13 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 10 Mar 2014 14:48:13 -0000 Subject: =?utf-8?q?New_attachment_added_to_page_Debug_Symbol_Packages_on_Ubuntu_Wi?= =?utf-8?q?ki?= Message-ID: <20140310144813.7011.44918@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page "Debug Symbol Packages" for change notification. An attachment has been added to that page by staticd-growthecommons. Following detailed information is available: Attachment name: list-symbols-packages-v2.1.sh Attachment size: 2950 Attachment link: http://wiki.ubuntu.com/Debug%20Symbol%20Packages?action=AttachFile&do=get&target=list-symbols-packages-v2.1.sh Page link: http://wiki.ubuntu.com/Debug%20Symbol%20Packages From noreply at ubuntu.com Mon Mar 10 14:49:56 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 10 Mar 2014 14:49:56 -0000 Subject: =?utf-8?q?New_attachment_added_to_page_Debug_Symbol_Packages_on_Ubuntu_Wi?= =?utf-8?q?ki?= Message-ID: <20140310144956.6931.62196@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page "Debug Symbol Packages" for change notification. An attachment has been added to that page by staticd-growthecommons. Following detailed information is available: Attachment name: list-symbols-packages.sh Attachment size: 2645 Attachment link: http://wiki.ubuntu.com/Debug%20Symbol%20Packages?action=AttachFile&do=get&target=list-symbols-packages.sh Page link: http://wiki.ubuntu.com/Debug%20Symbol%20Packages From noreply at ubuntu.com Mon Mar 10 14:01:40 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 10 Mar 2014 14:01:40 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Debug_Symbol_Packages=22_by_stat?= =?utf-8?q?icd-growthecommons?= Message-ID: <20140310140140.3801.18550@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Debug Symbol Packages" page has been changed by staticd-growthecommons: http://wiki.ubuntu.com/Debug%20Symbol%20Packages Comment: create page New page: <> ||<>|| This document describes how to set up the debugging symbol packages ( *-dbg.deb and *-.dbgsym.ddeb ). You might need to do this when you are performing tasks like a [[Backtrace]] or using [[Valgrind]]. == Debug Symbol Packages == If you want to debug a crash in a project you are developing yourself or from a third-party package, or need the debug symbols for particular libraries very often, it is helpful to install those permanently into your system. Debugging a program or analyzing stack traces can be very hard because most of the information that can be extracted from them will be in the form of offsets into the binary machine code of the executable. The extra information that allows mapping a machine instruction in a complex module to a function and line number in a corresponding C file is stored in the debug symbol packages. The maintainers of a project usually place the {{{*-dbg.deb}}} packages alongside their binary package in the same repository. Installing them will just involve finding the appropriate package name based on the version of that is installed. However, not all maintainers do this and they may not be up to date. During compilation on the ubuntu servers debug packages are also [[https://launchpad.net/ubuntu/+source/pkg-create-dbgsym|created automatically]] for each binary package. These are named {{{*-dbgsym.ddeb}}} and are stored in a separate archive. This is because these packages are used relatively rarely compared to the main repositories and need not be mirrored as much. ([[AptElfDebugSymbols|the spec for this]]) Either one of these can be used. First, check if there is a package with a -dbg suffix in the main Ubuntu repositories. These are the debug symbol packages, and are equivalent to '-dbgsym' described below. You can safely use either one, but not both at once. Try installing the package, adding -dbg to its name, for example: {{{ sudo apt-get install xserver-xorg-core-dbg }}} if the package in question is the ''xserver-xorg-core'' package. If there is no -dbg package: 1. Create an `/etc/apt/sources.list.d/ddebs.list` by running the following line at a terminal: {{{ echo "deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe multiverse" | \ sudo tee -a /etc/apt/sources.list.d/ddebs.list }}} 1. Stable releases (not alphas and betas) require three more lines adding to the same file, which is done by the following terminal command: {{{ echo "deb http://ddebs.ubuntu.com $(lsb_release -cs)-updates main restricted universe multiverse deb http://ddebs.ubuntu.com $(lsb_release -cs)-security main restricted universe multiverse deb http://ddebs.ubuntu.com $(lsb_release -cs)-proposed main restricted universe multiverse" | \ sudo tee -a /etc/apt/sources.list.d/ddebs.list }}} You may also add these lines using the Synaptic Package Manager: * Choose ''Synaptic'' via the ''System > Administration'' menu. * Choose ''Software Sources'' or ''Repositories'' via the ''Settings'' menu, and click on the ''Third-Party Software'' tab. * Click the ''Add'' button and enter each ''deb ...'' line as above one by one and click the ''Add Source'' button (you will have to add these lines one at a time). 1. Import the debug symbol archive signing key: {{{ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 428D7C01 }}} 1. Then run {{{ sudo apt-get update }}} to update your package list or click the ''Reload'' button if you used the Synaptic Package Manager. 1. The debug symbol packages have the '-dbgsym' suffix attached, so to install the debug symbols for the package 'yelp', you first run: {{{ apt-cache policy yelp }}} This will show you the version number currently installed (we'll use 2.22.1-0ubuntu2.8.04.1 in this example). '''NOTE:''' 'yelp' [which is the package name of "Help and Support" located under the 'System' menu] is ''just an example'' and '''not''' a part of the command: 'yelp' is only used to demonstrate the procedure. You must replace 'yelp' with the name of the package you want to debug. 1. Install the debug symbols: {{{ sudo apt-get install yelp-dbgsym=2.22.1-0ubuntu2.8.04.1 }}} You can also use the Synaptic Package Manager to search for 'yelp-dbgsym' and install it from there. The above procedure will install the debug symbol package for yelp only. Chances are that yelp uses shared libraries in other packages and debug symbols for them might be required in order to obtain a readable stack trace or perform other debugging tasks. You can download the following [[attachment:list-symbols-packages-v2.1.sh |shell script (list-symbols-packages-v2.1.sh)]] to resolve all the dependencies. Attaching a debugger to an already running process may require elevated privileges even if you own the process. The following invocation will print out the list of files to install. {{{#!highlight bash sudo bash ./list-symbols-packages-v2.sh -p $(pidof yelp)}}} To automatically install them apt can be called with the input from the script. The script is invoked with {{{-t}}} for a terse output without the descriptions of the packages and error messages are suppressed. {{{#!highlight bash sudo bash ./list-symbols-packages-v2.sh -t -p $(pidof yelp) 2>/dev/null|\ xargs -d $'\n' sudo apt-get install }}} /!\ Version 2 of this script makes it compatible with the newer GDB (which no longer loads all libraries at startup by default). -v2 currently only works if you run it against a currently-executing binary (i.e., with '-p $(pidof '). The [[attachment:list-symbols-packages.sh|older version]] of the script is also available. ---- CategoryBugSquad CategoryDebugging From noreply at ubuntu.com Mon Mar 10 14:47:17 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 10 Mar 2014 14:47:17 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Debug_Symbol_Packages=22_by_stat?= =?utf-8?q?icd-growthecommons?= Message-ID: <20140310144717.6949.94407@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Debug Symbol Packages" page has been changed by staticd-growthecommons: http://wiki.ubuntu.com/Debug%20Symbol%20Packages?action=diff&rev1=1&rev2=2 Comment: rewrite for ease of use. write intro. Debugging a program or analyzing stack traces can be very hard because most of the information that can be extracted from them will be in the form of offsets into the binary machine code of the executable. The extra information that allows mapping a machine instruction in a complex module to a function and line number in a corresponding C file is stored in the debug symbol packages. - The maintainers of a project usually place the {{{*-dbg.deb}}} packages alongside their binary package in the same repository. Installing them will just involve finding the appropriate package name based on the version of that is installed. However, not all maintainers do this and they may not be up to date. During compilation on the ubuntu servers debug packages are also [[https://launchpad.net/ubuntu/+source/pkg-create-dbgsym|created automatically]] for each binary package. These are named {{{*-dbgsym.ddeb}}} and are stored in a separate archive. This is because these packages are used relatively rarely compared to the main repositories and need not be mirrored as much. ([[AptElfDebugSymbols|the spec for this]]) Either one of these can be used. + The maintainers of a project usually place the {{{*-dbg.deb}}} packages alongside their binary package in the same repository. Installing them will just involve finding the appropriate package name based on the version of that is installed. However, not all maintainers do this and they may not be up to date. During compilation on the ubuntu servers debug packages are also [[https://launchpad.net/ubuntu/+source/pkg-create-dbgsym|created automatically]] for each binary package. These are named {{{*-dbgsym.ddeb}}} and are stored in a separate archive. This is because these packages are used relatively rarely compared to the main repositories and need not be mirrored as much. ([[AptElfDebugSymbols|the spec for this]]) Either one of these can be used, but for a given package only one can be used at a time. + === Getting -dbgsym.ddeb packages === + In case the {{{-dbg}}} package is not available for the version of the package you are using, you might have to use the {{{-dbgsym}}} packages. When a large number of dependancies need to have their symbols retrieved it might become necessary to enable the {{{-dbgsym}}} repositories anyway. - - First, check if there is a package with a -dbg suffix in the main Ubuntu repositories. These are the debug symbol packages, and are equivalent to '-dbgsym' described below. You can safely use either one, but not both at once. Try installing the package, adding -dbg to its name, for example: - {{{ - sudo apt-get install xserver-xorg-core-dbg - }}} - if the package in question is the ''xserver-xorg-core'' package. - - If there is no -dbg package: 1. Create an `/etc/apt/sources.list.d/ddebs.list` by running the following line at a terminal: - {{{ + {{{#!highlight bash - echo "deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe multiverse" | \ + echo "deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe multiverse - sudo tee -a /etc/apt/sources.list.d/ddebs.list - }}} - 1. Stable releases (not alphas and betas) require three more lines adding to the same file, which is done by the following terminal command: - {{{ - echo "deb http://ddebs.ubuntu.com $(lsb_release -cs)-updates main restricted universe multiverse + deb http://ddebs.ubuntu.com $(lsb_release -cs)-updates main restricted universe multiverse deb http://ddebs.ubuntu.com $(lsb_release -cs)-security main restricted universe multiverse deb http://ddebs.ubuntu.com $(lsb_release -cs)-proposed main restricted universe multiverse" | \ sudo tee -a /etc/apt/sources.list.d/ddebs.list }}} + The last three repositories may not be needed on a testing (alpha, beta daily build etc) releases. - You may also add these lines using the Synaptic Package Manager: - * Choose ''Synaptic'' via the ''System > Administration'' menu. - * Choose ''Software Sources'' or ''Repositories'' via the ''Settings'' menu, and click on the ''Third-Party Software'' tab. - * Click the ''Add'' button and enter each ''deb ...'' line as above one by one and click the ''Add Source'' button (you will have to add these lines one at a time). - 1. Import the debug symbol archive signing key: + You can also add these repositories in your software sources from the Ubuntu software center or from synaptic. (see [[https://help.ubuntu.com/community/Repositories/Ubuntu|this article]] especially the section on [[https://help.ubuntu.com/community/Repositories/Ubuntu#Adding_Other_Repositories |adding other repositories]]) + You will need to add lines like {{{ + deb http://ddebs.ubuntu.com trusty main restricted universe multiverse}}} + + 1. Import the debug symbol archive [[https://help.ubuntu.com/community/Repositories/Ubuntu#Authentication_Tab|signing key]] from the ubuntu server: + {{{#!highlight bash sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 428D7C01 }}} - 1. Then run - {{{ + 1. Then run the following to update your package list or click the ''Reload'' button if you used the Synaptic Package Manager. + {{{#!highlight bash sudo apt-get update }}} - to update your package list or click the ''Reload'' button if you used the Synaptic Package Manager. + + === Manual install of debug packages === + If the package in question is the ''xserver-xorg-core'' package you can try + {{{ + sudo apt-get install xserver-xorg-core-dbg + }}} - 1. The debug symbol packages have the '-dbgsym' suffix attached, so to install the debug symbols for the package 'yelp', you first run: + or {{{ - apt-cache policy yelp + sudo apt-get install xserver-xorg-core-dbgsym }}} - This will show you the version number currently installed (we'll use 2.22.1-0ubuntu2.8.04.1 in this example). - '''NOTE:''' 'yelp' [which is the package name of "Help and Support" located under the 'System' menu] is ''just an example'' and '''not''' a part of the command: 'yelp' is only used to demonstrate the procedure. You must replace 'yelp' with the name of the package you want to debug. + === Automatic Resolution / Installation of necessary packages === + The above procedure will install the debug symbol package for a single package only. Chances are that the binary uses shared libraries in other packages and debug symbols for them might be required in order to obtain a readable stack trace or perform other debugging tasks. - 1. Install the debug symbols: - {{{ - sudo apt-get install yelp-dbgsym=2.22.1-0ubuntu2.8.04.1 - }}} - You can also use the Synaptic Package Manager to search for 'yelp-dbgsym' and install it from there. - The above procedure will install the debug symbol package for yelp only. Chances are that yelp uses shared libraries in other packages and debug symbols for them might be required in order to obtain a readable stack trace or perform other debugging tasks. - - You can download the following [[attachment:list-symbols-packages-v2.1.sh |shell script (list-symbols-packages-v2.1.sh)]] to resolve all the dependencies. Attaching a debugger to an already running process may require elevated privileges even if you own the process. The following invocation will print out the list of files to install. + You can download the following [[attachment:list-symbols-packages-v2.1.sh |shell script (list-symbols-packages-v2.1.sh)]] to resolve all the dependencies. Attaching a debugger to an already running process may require elevated privileges even if you own the process. The following invocation will print out the list of files to install. If you want to debug an instance of evince use: {{{#!highlight bash sudo bash ./list-symbols-packages-v2.sh -p $(pidof yelp)}}} - To automatically install them apt can be called with the input from the script. The script is invoked with {{{-t}}} for a terse output without the descriptions of the packages and error messages are suppressed. + To automatically install them apt can be called with the input from the script. The script is invoked with {{{-t}}} for a terse output without the descriptions of the packages and error messages are suppressed. {{{#!highlight bash sudo bash ./list-symbols-packages-v2.sh -t -p $(pidof yelp) 2>/dev/null|\ xargs -d $'\n' sudo apt-get install }}} - /!\ Version 2 of this script makes it compatible with the newer GDB (which no longer loads all libraries at startup by default). -v2 currently only works if you run it against a currently-executing binary (i.e., with '-p $(pidof '). The [[attachment:list-symbols-packages.sh|older version]] of the script is also available. + /!\ Version 2 of this script makes it compatible with the newer GDB (which no longer loads all libraries at startup by default). -v2 currently only works if you run it against a currently-executing binary (i.e., with '-p $(pidof '). The [[attachment:list-symbols-packages.sh|older version]] of the script is also available. ---- CategoryBugSquad CategoryDebugging From chilicuil at ubuntu.com Mon Mar 10 19:39:27 2014 From: chilicuil at ubuntu.com (Javier =?iso-8859-1?Q?L=F3pez?=) Date: Mon, 10 Mar 2014 13:39:27 -0600 Subject: Bug Weekend concluded In-Reply-To: <531DBCB5.2050609@gmail.com> References: <531DBCB5.2050609@gmail.com> Message-ID: <20140310193926.GB3931@sup.lan> Awesome work Alberto, thanks for the courtesy, however I won't be able to accept it, since I couldn't participate in the second edition even when I had already edited the wiki page to do so. In the other hand, I'd like to suggest to take a look at: https://wiki.ubuntu.com/OperationCleansweep I think it has the potential to fit better on these workshops. All listed bugs already contain patches, so it gets easier to inspect them, review them and merge them in Ubuntu. Hope this isn't the latest Ubuntu Bug Weekend I see in a while. Bests On 10/03/14 at 02:23pm, Alberto Salvia Novella wrote: > Thank you for helping out in the Ubuntu Bug Weekend > (http://tinyurl.com/nd89z8d), where bug management was more needed > at this time. > > > Additionally, the following people won a gift for their special > contribution: > > * Javier López (chilicuil), for being so supportive and being the > only participant in the previous round of the Bug Week, helping > setting priority to 28 bugs. > > * Ross Gammon (retail-0), for being the one with the greatest > contribution to the bug confirmation; not only in quantity but also > in quality. > > * Walter Garcia-Fontes (walter-garcia), for being so close to being > managed as many bugs as Ross Gammon; (although I see it has been not > from the provided list and mainly not concerning the "Trusty" > release, which is the one which can take more time to confirm 8-D ). > > Please email me telling what courtesy you want to receive and where. > > > And, since this is not about how much we can't do but actually what > we can do and feels good to us, the rest of help is also > appreciated. > > Thank you. From nicholas.skaggs at canonical.com Mon Mar 10 20:45:05 2014 From: nicholas.skaggs at canonical.com (Nicholas Skaggs) Date: Mon, 10 Mar 2014 16:45:05 -0400 Subject: Bug Weekend concluded In-Reply-To: <20140310193926.GB3931@sup.lan> References: <531DBCB5.2050609@gmail.com> <20140310193926.GB3931@sup.lan> Message-ID: <531E2451.303@canonical.com> On 03/10/2014 03:39 PM, Javier López wrote: > In the other hand, I'd like to suggest to take a look at: > > https://wiki.ubuntu.com/OperationCleansweep > > I think it has the potential to fit better on these workshops. All listed bugs > already contain patches, so it gets easier to inspect them, review them and > merge them in Ubuntu. oO That's a nice filter and a good idea! +1 from me. Nicholas From es20490446e at gmail.com Tue Mar 11 13:54:38 2014 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Tue, 11 Mar 2014 14:54:38 +0100 Subject: Bug Weekend concluded In-Reply-To: <20140310135114.GE8798@upf.edu> References: <531DBCB5.2050609@gmail.com> <20140310135114.GE8798@upf.edu> Message-ID: <531F159E.9070908@gmail.com> On 10/03/14 14:51, Walter Garcia-Fontes wrote: > Thanks Alberto for organizing this, on the courtesy to me don't > worry, if you want you can send it to our Loco team and we can include > it in the lottery that we run after each release party among the > participants (send it to the team coordinator, you can find addresses > at http://loco.ubuntu.com/teams/ubuntu.cat/). Done. On 10/03/14 14:51, Walter Garcia-Fontes wrote: > 1) In the part of "confirming" bugs, first I think we discussed some > months ago that confirming bugs is not the most important part of > managing bugs, as there are a lot of confirmed bugs that where > confirmed just because two users saw it. The most important part is, > in my opinion, checking if the reporter can provide more information, > and seeing if it can be triaged. Second I find it almost impossible to > deal with bugs if I don't concentrate in specific packages, issues, > and so on. Otherwise each bug is so different from the next that I > never get on speed on dealing with them. Yes, confirming bugs is not the most important think; but is the most important think that can be done in a Bug Weekend by anyone. In my opinion, the most important part of managing bugs is deciding importances; as this discovers were work is more needed. The next most important task is fixing the bug itself, because is what makes every piece of effort put in a report to seize constantly. Secondly, changing between task can be very distracting. That is why the provided lists has been deeply studied for being predictable, but not repetitive. Moreover, I have formed myself in the latest months specially for doing this. Confirming bugs in the Bug Weekend consist only in following steps in bugs' descriptions. And if there aren't any steps, to ask for them. The concept is like the following: http://youtu.be/hg5RlapdEtE On 10/03/14 14:51, Walter Garcia-Fontes wrote: > 2) On the part of paper cuts, I find that the list was not very > useful. None of those bugs were, in my humble opinion, really > "bitesize". some of them wouldn't make sense to handle as an Ubuntu > package as they where of an upstream nature, and so on. - Only bugs that can be fixed within a day can be marked as papercuts. - The Bug Weekend last three days. - If a bug cannot be fixed within a day, it should be unmarked as a papercut. On 10/03/14 14:51, Walter Garcia-Fontes wrote: > But again, thanks for the effort. Last comment is that I think, and > this is something that we discussed also lot of times, old bugs > shouldn't be ignored, and some effort should be dedicated to clean > those old bugs. This is one of the easiest task for new bug > triagers, but not a nice thing to do, users who get the first answer > after several months of an unattended bug can dedicate you really nice > insults, especially if they have moved away from Ubuntu long ago. But > better late than never. While old bugs shall be cared, the purpose of the event was to carry on the most important bugs only; so to fix where it was more needed. I think is normal people to get angry when something is full of defects that are not being fixed, but the alternative has been till now to use vintage or bad designed malicious bloated proprietary software. This is why we're now reinventing bug and quality management. Regards to you ;) From noreply at ubuntu.com Tue Mar 11 22:37:47 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 11 Mar 2014 22:37:47 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Ubuntu_Bug_Weekend/Confirm_?= =?utf-8?q?bugs_contributors=22_by_dkessel?= Message-ID: <20140311223747.4043.28350@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Ubuntu Bug Weekend/Confirm bugs contributors" page has been changed by dkessel: http://wiki.ubuntu.com/Bugs/Ubuntu%20Bug%20Weekend/Confirm%20bugs%20contributors?action=diff&rev1=19&rev2=20 Comment: added my contributions ||[[LaunchpadHome:wiranvaud]]||-3||1||[[http://pad.ubuntu.com/0xzjKez23s|List]]|| ||[[LaunchpadHome:walter-garcia]]||+1||14||[[http://pad.ubuntu.com/yCWnEPb8aL|List]]|| ||[[LaunchpadHome:cbaudier]]||-4||3||[[http://pad.ubuntu.com/C4pPYtN06U|List]]|| + ||[[LaunchpadHome:dkessel]]||+1||10||[http://http://pad.ubuntu.com/vTNSTcN3BV|List]]|| From noreply at ubuntu.com Tue Mar 11 22:39:13 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 11 Mar 2014 22:39:13 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Ubuntu_Bug_Weekend/Confirm_?= =?utf-8?q?bugs_contributors=22_by_dkessel?= Message-ID: <20140311223913.4037.55332@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Ubuntu Bug Weekend/Confirm bugs contributors" page has been changed by dkessel: http://wiki.ubuntu.com/Bugs/Ubuntu%20Bug%20Weekend/Confirm%20bugs%20contributors?action=diff&rev1=20&rev2=21 ||[[LaunchpadHome:wiranvaud]]||-3||1||[[http://pad.ubuntu.com/0xzjKez23s|List]]|| ||[[LaunchpadHome:walter-garcia]]||+1||14||[[http://pad.ubuntu.com/yCWnEPb8aL|List]]|| ||[[LaunchpadHome:cbaudier]]||-4||3||[[http://pad.ubuntu.com/C4pPYtN06U|List]]|| - ||[[LaunchpadHome:dkessel]]||+1||10||[http://http://pad.ubuntu.com/vTNSTcN3BV|List]]|| + ||[[LaunchpadHome:dkessel]]||+1||10||[[http://http://pad.ubuntu.com/vTNSTcN3BV|List]]|| From noreply at ubuntu.com Tue Mar 11 22:39:46 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 11 Mar 2014 22:39:46 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Ubuntu_Bug_Weekend/Confirm_?= =?utf-8?q?bugs_contributors=22_by_dkessel?= Message-ID: <20140311223946.4031.21732@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Ubuntu Bug Weekend/Confirm bugs contributors" page has been changed by dkessel: http://wiki.ubuntu.com/Bugs/Ubuntu%20Bug%20Weekend/Confirm%20bugs%20contributors?action=diff&rev1=21&rev2=22 ||[[LaunchpadHome:wiranvaud]]||-3||1||[[http://pad.ubuntu.com/0xzjKez23s|List]]|| ||[[LaunchpadHome:walter-garcia]]||+1||14||[[http://pad.ubuntu.com/yCWnEPb8aL|List]]|| ||[[LaunchpadHome:cbaudier]]||-4||3||[[http://pad.ubuntu.com/C4pPYtN06U|List]]|| - ||[[LaunchpadHome:dkessel]]||+1||10||[[http://http://pad.ubuntu.com/vTNSTcN3BV|List]]|| + ||[[LaunchpadHome:dkessel]]||+1||10||[[http://pad.ubuntu.com/vTNSTcN3BV|List]]|| From es20490446e at gmail.com Wed Mar 12 00:33:18 2014 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Wed, 12 Mar 2014 01:33:18 +0100 Subject: Bug Weekend concluded In-Reply-To: <20140310193926.GB3931@sup.lan> References: <531DBCB5.2050609@gmail.com> <20140310193926.GB3931@sup.lan> Message-ID: <531FAB4E.1020604@gmail.com> On 10/03/14 20:39, Javier López wrote: > In the other hand, I'd like to suggest to take a look at: > > https://wiki.ubuntu.com/OperationCleansweep > > I think it has the potential to fit better on these workshops. All listed bugs > already contain patches, so it gets easier to inspect them, review them and > merge them in Ubuntu. Good work-flow is somehow both predictable and varied. Working with patches in Launchpad is very unpredictable right now. http://youtu.be/S2nv4gD2p9A?t=49s From noreply at ubuntu.com Wed Mar 12 22:00:34 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Wed, 12 Mar 2014 22:00:34 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/FindRightPackage=22_by_serg?= =?utf-8?q?e-hallyn?= Message-ID: <20140312220034.8084.29268@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/FindRightPackage" page has been changed by serge-hallyn: http://wiki.ubuntu.com/Bugs/FindRightPackage?action=diff&rev1=127&rev2=128 * `pm-utils` is responsible for getting the system into a state where it can be suspended or hibernated, and handling any cleanup after resume. * [[#Kernel|The kernel]] implements the actual suspending and resuming and is generally the responsible package when there are any hardware-related failures after resume. - If you are unsure which package is causing the problem, a safe bet is the kernel, ''but make the bug title includes "suspend" or "hibernate"''. + If you are unsure which package is causing the problem, a safe bet is the kernel (package 'linux'), ''but make the bug title includes "suspend" or "hibernate"''. === Hotkeys === From es20490446e at gmail.com Thu Mar 13 19:12:22 2014 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Thu, 13 Mar 2014 20:12:22 +0100 Subject: Papercut definition updated Message-ID: <53220316.2090207@gmail.com> While setting importances for around 200 bugs, I realized the papercut definition was too complicated to be taken into practice by anyone, including myself. So I've overly simplified it. A papercut is a software defect that is: - insignificant. - fixable by one person within a day. - affecting the future release. What is to say, if you see something ridiculous affecting Trusty, please mark it as affecting "One Hundred Papercuts". Regards <コ:彡 From PhillW at PhillW.net Thu Mar 13 19:37:14 2014 From: PhillW at PhillW.net (Phill Whiteside) Date: Thu, 13 Mar 2014 19:37:14 +0000 Subject: Papercut definition updated In-Reply-To: <53220316.2090207@gmail.com> References: <53220316.2090207@gmail.com> Message-ID: Alberto, may I remind you of one simple thing... To the person reporting the bug, there is NO more important bug. You have to please 9 people to get a recommendation - only need to annoy one to get negative comments. Just my thoughts. Phill. On 13 March 2014 19:12, Alberto Salvia Novella wrote: > While setting importances for around 200 bugs, I realized the papercut > definition was too complicated to be taken into practice by anyone, > including myself. So I've overly simplified it. > > A papercut is a software defect that is: > - insignificant. > - fixable by one person within a day. > - affecting the future release. > > What is to say, if you see something ridiculous affecting Trusty, please > mark it as affecting "One Hundred Papercuts". > > Regards <コ:彡 > > -- > Ubuntu-quality mailing list > Ubuntu-quality at lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/ > mailman/listinfo/ubuntu-quality > -- https://wiki.ubuntu.com/phillw -------------- next part -------------- An HTML attachment was scrubbed... URL: From es20490446e at gmail.com Fri Mar 14 11:28:20 2014 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Fri, 14 Mar 2014 12:28:20 +0100 Subject: Papercut definition updated In-Reply-To: References: <53220316.2090207@gmail.com> Message-ID: <5322E7D4.1070305@gmail.com> El 13/03/14 20:37, Phill Whiteside escribió: > may I remind you of one simple thing... To the person reporting the bug, > there is NO more important bug. You have to please 9 people to get a > recommendation - only need to annoy one to get negative comments. Of what kind of recommendation are we talking about? From PhillW at PhillW.net Fri Mar 14 17:27:11 2014 From: PhillW at PhillW.net (Phill Whiteside) Date: Fri, 14 Mar 2014 17:27:11 +0000 Subject: Papercut definition updated In-Reply-To: <5322E7D4.1070305@gmail.com> References: <53220316.2090207@gmail.com> <5322E7D4.1070305@gmail.com> Message-ID: to ditch propietory and switch to F/OSS :D Regards, Phill. On 14 March 2014 11:28, Alberto Salvia Novella wrote: > El 13/03/14 20:37, Phill Whiteside escribió: > > may I remind you of one simple thing... To the person reporting the bug, >> there is NO more important bug. You have to please 9 people to get a >> recommendation - only need to annoy one to get negative comments. >> > > Of what kind of recommendation are we talking about? > -- https://wiki.ubuntu.com/phillw -------------- next part -------------- An HTML attachment was scrubbed... URL: From es20490446e at gmail.com Sat Mar 15 10:02:41 2014 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Sat, 15 Mar 2014 11:02:41 +0100 Subject: Papercut definition updated In-Reply-To: References: <53220316.2090207@gmail.com> <5322E7D4.1070305@gmail.com> Message-ID: <53242541.5000002@gmail.com> On 14/03/14 18:27, Phill Whiteside write: > may I remind you of one simple thing... To the person reporting the bug, > there is NO more important bug. You have to please 9 people to get a > recommendation - only need to annoy one to get negative comments. Normally people don't get convinced when you try them to be by words, but usually very easily if they can already see themselves results without saying nothing to them; what is, in the end, very wise from them. In this scenario they're the ones who begin to talk about the topic. Although many times it seems, because what they say, that they are not to change; they're rather looking an excuse from you for not taking what already seems better to them. So better to give a brief explanation, without entering in discussion, and let them look and think themselves. And talking about an specific scenario; this is why pilot schemes, which anyone can go and look themselves work, so well in making changes in organizations that are resistant to renovation. "Be the change you want to see in the world" "When the pupil is ready, the master appears" Have a nice day ~☆ From es20490446e at gmail.com Sat Mar 15 10:15:13 2014 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Sat, 15 Mar 2014 11:15:13 +0100 Subject: Papercut definition updated In-Reply-To: <53220316.2090207@gmail.com> References: <53220316.2090207@gmail.com> Message-ID: <53242831.7070000@gmail.com> El 13/03/14 20:12, Alberto Salvia Novella escribió: > While setting importances for around 200 bugs, I realized the papercut > definition was too complicated to be taken into practice by anyone, > including myself. So I've overly simplified it. >(...) > - affecting the future release. > (...) It seems to me important to explain this decision. What happens is papercuts' fixes, because being minor defects, rarely land in stable release updates; as seen in . So working in something that will never reach a release is just useless. On the other hand, I'm going to include a task for testing if old papercuts are still affecting the future release where they can land. More luckily Ubuntu release circle is going to be shortened, making papercuts' fixes to be delivered continuously in the near future. Regards. From noreply at ubuntu.com Mon Mar 17 09:48:54 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 17 Mar 2014 09:48:54 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Debug_Symbol_Packages=22_by_stat?= =?utf-8?q?icd-growthecommons?= Message-ID: <20140317094854.19055.67500@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Debug Symbol Packages" page has been changed by staticd-growthecommons: http://wiki.ubuntu.com/Debug%20Symbol%20Packages?action=diff&rev1=2&rev2=3 === Automatic Resolution / Installation of necessary packages === The above procedure will install the debug symbol package for a single package only. Chances are that the binary uses shared libraries in other packages and debug symbols for them might be required in order to obtain a readable stack trace or perform other debugging tasks. - You can download the following [[attachment:list-symbols-packages-v2.1.sh |shell script (list-symbols-packages-v2.1.sh)]] to resolve all the dependencies. Attaching a debugger to an already running process may require elevated privileges even if you own the process. The following invocation will print out the list of files to install. If you want to debug an instance of evince use: + You can download the following [[attachment:list-symbols-packages-v2.1.sh |shell script (list-symbols-packages-v2.1.sh)]] to resolve all the dependencies. Attaching a debugger to an already running process may require elevated privileges even if you own the process. The following invocation will print out the list of files to install. If you want to debug an instance of yelp use: {{{#!highlight bash sudo bash ./list-symbols-packages-v2.sh -p $(pidof yelp)}}} - To automatically install them apt can be called with the input from the script. The script is invoked with {{{-t}}} for a terse output without the descriptions of the packages and error messages are suppressed. + To automatically install them apt can be called with the input from the script. The script is invoked with {{{-t}}} for a terse output (without the descriptions of the packages) and error messages are suppressed. {{{#!highlight bash sudo bash ./list-symbols-packages-v2.sh -t -p $(pidof yelp) 2>/dev/null|\ From noreply at ubuntu.com Thu Mar 20 11:59:53 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Thu, 20 Mar 2014 11:59:53 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/FindRightPackage=22_by_shan?= =?utf-8?q?kao?= Message-ID: <20140320115953.19217.31390@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/FindRightPackage" page has been changed by shankao: http://wiki.ubuntu.com/Bugs/FindRightPackage?action=diff&rev1=130&rev2=131 * `notify-osd` in Ubuntu, Xubuntu and Edubuntu + Lock screen problems: + + * If your problem is with the lock screen itself, the package is gnome-screensaver until 13.10 or unity from 14.04 onwards. For more info, check https://wiki.ubuntu.com/DebuggingScreenLocking/HowScreenLockingWorks + === Printing === All printing in Ubuntu is done via the Common UNIX Printing System (CUPS). The package is `cups`. (See also [[DebuggingPrintingProblems]].) From noreply at ubuntu.com Sat Mar 22 15:03:35 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sat, 22 Mar 2014 15:03:35 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Bug_importances=22_by_es204?= =?utf-8?q?90446e?= Message-ID: <20140322150335.24254.85577@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Bug importances" page has been changed by es20490446e: http://wiki.ubuntu.com/Bugs/Bug%20importances?action=diff&rev1=40&rev2=41 * For example, if the system fails to boot, or X fails to start, on a certain make and model of computer * A problem with an essential hardware component (disk controller, built-in networking, video card, keyboard, mouse) * Has a moderate impact on a large portion of Ubuntu users (estimated) - * Prevents the application or any dependencies from functioning correctly at all + * Prevents the application or any dependencies from functioning correctly at everything. * Renders essential features or functionality of the application or dependencies broken or ineffective * Impacts accessibility of a core application * '''Critical''': A bug which has a severe impact on a large portion of Ubuntu users From es20490446e at gmail.com Sun Mar 23 17:53:18 2014 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Sun, 23 Mar 2014 18:53:18 +0100 Subject: Fwd: Re: [Bug 1285801] Re: virtuoso-t crashed with SIGSEGV on system startup In-Reply-To: References: Message-ID: <532F1F8E.40402@gmail.com> What shall be done in this case? -------- Mensaje original -------- Asunto: Re: [Bug 1285801] Re: virtuoso-t crashed with SIGSEGV on system startup Fecha: Sat, 22 Mar 2014 12:38:54 -0400 De: Obey Arthur Liu Para: es20490446e at gmail.com I haven't been the maintainer of this package for 3 years. Please advise. http://packages.qa.debian.org/v/virtuoso-opensource.html On Sat, Mar 22, 2014 at 9:44 AM, Alberto Salvia Novella > wrote: It prevents the package (or a dependent one) from functioning correctly at all. ** Changed in: virtuoso-opensource (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are subscribed to virtuoso-opensource in Ubuntu. https://bugs.launchpad.net/bugs/1285801 Title: virtuoso-t crashed with SIGSEGV on system startup Status in "virtuoso-opensource" package in Ubuntu: Confirmed Bug description: Since several years (and several versions of Ubuntu), Virtuoso has been crashing consitently upon system startup. This is regardless of the PC it is running on, user account, or what have you. I really hope that this long standing issue will be resolved before Ubuntu 14.10 is released, it is really getting old. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: virtuoso-opensource-6.1-bin 6.1.6+repack-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-12.32-generic 3.13.4 Uname: Linux 3.13.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 CurrentDesktop: KDE Date: Thu Feb 27 09:46:32 2014 ExecutablePath: /usr/bin/virtuoso-t InstallationDate: Installed on 2013-12-06 (82 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcCmdline: /usr/bin/virtuoso-t +foreground +configfile /tmp/virtuoso_GS3661.ini +wait ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x939d75: movq $0xffffffffffffffff,(%rax) PC (0x00939d75) ok source "$0xffffffffffffffff" ok destination "(%rax)" (0xffffffffffffffff) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: virtuoso-opensource StacktraceTop: ?? () ?? () ?? () ?? () ?? () Title: virtuoso-t crashed with SIGSEGV UpgradeStatus: Upgraded to trusty on 2014-02-27 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtuoso-opensource/+bug/1285801/+subscriptions -------------- next part -------------- An HTML attachment was scrubbed... URL: From es20490446e at gmail.com Mon Mar 24 15:01:48 2014 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Mon, 24 Mar 2014 16:01:48 +0100 Subject: Stop triaging bugs In-Reply-To: <53303775.9030406@canonical.com> References: <53302590.2080008@canonical.com> <5330351C.3030600@gmail.com> <53303775.9030406@canonical.com> Message-ID: <533048DC.1080901@gmail.com> El 24/03/14 14:47, Marc Deslauriers escribió: > On 14-03-24 09:37 AM, Alberto Salvia Novella wrote: >> El 24/03/14 13:31, Marc Deslauriers escribió: >>> Could you please stop changing statuses of bugs you don't intend on fixing yourself? >>> >>> Marking a bug as "triaged" and changing priorities on them makes absolutely no >>> sense if you aren't tasked to fix them. >>> >>> Changing one of my team's bugs to "triaged" means our scripts and procedures no >>> longer consider the bug to be new, hence, nobody will look at it anymore. It is >>> breaking our workflow. >> As said in the bug statuses page, >> which arbitrates the hole bug management work-flow in Launchpad, "triaged" means >> "a member of UbuntuBugControl >> believes that the report describes a genuine bug in enough detail that a >> developer could start working on a fix." >> >> Moreover, according to lean management >> : >> >> * The first source of flaws (or any waste) is them to remain invisible (or >> untriaged or with unset priority in the case of bug management). >> * Unpredictable work-flow has to be done manually till, after some continuous >> improvement and waste reduction, it becomes regular. >> >> So, since your work-flow conflicts with Launchpad's one and with principal >> productivity recommendations, I'm sorry I'm not taking on your request; except >> if I'm missing something. >> > (...) > Modifying in an arbitrary way bug statuses and priorities that teams depend on > to track work is simply a bad idea. > (...) What do you think; Quality, BugSquad and BugControl; about this topic? From jack at troop55.net Mon Mar 24 15:22:00 2014 From: jack at troop55.net (Jack Ramsay) Date: Mon, 24 Mar 2014 10:22:00 -0500 Subject: Stop triaging bugs In-Reply-To: <533048DC.1080901@gmail.com> References: <53302590.2080008@canonical.com> <5330351C.3030600@gmail.com> <53303775.9030406@canonical.com> <533048DC.1080901@gmail.com> Message-ID: On Mar 24, 2014 10:02 AM, "Alberto Salvia Novella" wrote: > > El 24/03/14 14:47, Marc Deslauriers escribió: >> >> On 14-03-24 09:37 AM, Alberto Salvia Novella wrote: >>> >>> El 24/03/14 13:31, Marc Deslauriers escribió: >>>> >>>> Could you please stop changing statuses of bugs you don't intend on fixing yourself? >>>> >>>> Marking a bug as "triaged" and changing priorities on them makes absolutely no >>>> sense if you aren't tasked to fix them. >>>> >>>> Changing one of my team's bugs to "triaged" means our scripts and procedures no >>>> longer consider the bug to be new, hence, nobody will look at it anymore. It is >>>> breaking our workflow. So couldn't launchpad do something about that? Couldn't it be set up to where triaged bugs still show as new? Honestly that way we can triage bugs and that way they won't be missed when a team member is looking at the new bugs. I honestly don't think we should stop triaging bugs. >>> As said in the bug statuses page, >>> which arbitrates the hole bug management work-flow in Launchpad, "triaged" means >>> "a member of UbuntuBugControl >>> believes that the report describes a genuine bug in enough detail that a >>> developer could start working on a fix." >>> >>> Moreover, according to lean management >>> : >>> >>> * The first source of flaws (or any waste) is them to remain invisible (or >>> untriaged or with unset priority in the case of bug management). >>> * Unpredictable work-flow has to be done manually till, after some continuous >>> improvement and waste reduction, it becomes regular. >>> >>> So, since your work-flow conflicts with Launchpad's one and with principal >>> productivity recommendations, I'm sorry I'm not taking on your request; except >>> if I'm missing something. >>> >> (...) >> Modifying in an arbitrary way bug statuses and priorities that teams depend on >> to track work is simply a bad idea. >> (...) > > What do you think; Quality, BugSquad and BugControl; about this topic? > > -- > 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 maarten.bezemer at gmail.com Mon Mar 24 15:35:31 2014 From: maarten.bezemer at gmail.com (Maarten Bezemer) Date: Mon, 24 Mar 2014 16:35:31 +0100 Subject: Stop triaging bugs In-Reply-To: <533048DC.1080901@gmail.com> References: <53302590.2080008@canonical.com> <53303775.9030406@canonical.com> <533048DC.1080901@gmail.com> Message-ID: <1945940.ETraQQKv76@bzrd-ram> On Monday 24 March 2014 16:01:48 Alberto Salvia Novella wrote: > El 24/03/14 14:47, Marc Deslauriers escribió: > > On 14-03-24 09:37 AM, Alberto Salvia Novella wrote: > >> El 24/03/14 13:31, Marc Deslauriers escribió: > >>> Could you please stop changing statuses of bugs you don't intend on > >>> fixing yourself? > >>> > >>> Marking a bug as "triaged" and changing priorities on them makes > >>> absolutely no sense if you aren't tasked to fix them. > >>> > >>> Changing one of my team's bugs to "triaged" means our scripts and > >>> procedures no longer consider the bug to be new, hence, nobody will > >>> look at it anymore. It is breaking our workflow. > >> > >> As said in the bug statuses > >> page, which arbitrates the hole bug management work-flow in Launchpad, > >> "triaged" means "a member of UbuntuBugControl > >> believes that the report > >> describes a genuine bug in enough detail that a developer could start > >> working on a fix." > >> > >> Moreover, according to lean management > >> > >> : > >> * The first source of flaws (or any waste) is them to remain invisible > >> (or > >> > >> untriaged or with unset priority in the case of bug management). > >> > >> * Unpredictable work-flow has to be done manually till, after some > >> continuous>> > >> improvement and waste reduction, it becomes regular. > >> > >> So, since your work-flow conflicts with Launchpad's one and with > >> principal > >> productivity recommendations, I'm sorry I'm not taking on your request; > >> except if I'm missing something. > > > > (...) > > Modifying in an arbitrary way bug statuses and priorities that teams > > depend on to track work is simply a bad idea. > > (...) > > What do you think; Quality, BugSquad and BugControl; about this topic? Each group uses the status (and other) field(s) for their own use. Depending on the bug and where it is send to, one should use the definitions of the group responsible. In this case the bugs (apparently) belong to a group that use different 'definitions' of the status field, than Bug Squat does. I have seen information on different uses of the bug fields somewhere on wiki.ubuntu.com but I cannot find it anymore..? I suppose this needs to be made more clear on https://wiki.ubuntu.com/Bugs/Bug%20statuses maybe with a list of links to the other groups and their descriptions/use of the fields. Regards, Maarten From es20490446e at gmail.com Mon Mar 24 15:39:40 2014 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Mon, 24 Mar 2014 16:39:40 +0100 Subject: Stop triaging bugs In-Reply-To: <1945940.ETraQQKv76@bzrd-ram> References: <53302590.2080008@canonical.com> <53303775.9030406@canonical.com> <533048DC.1080901@gmail.com> <1945940.ETraQQKv76@bzrd-ram> Message-ID: <533051BC.2030606@gmail.com> El 24/03/14 16:35, Maarten Bezemer escribió: > Each group uses the status (and other) field(s) for their own use. Yes, this could be made clearer somewhere; but here we are talking of setting importances to Ubuntu packages itself. So this is not group specific. From corbellini.andrea at gmail.com Mon Mar 24 15:42:09 2014 From: corbellini.andrea at gmail.com (Andrea Corbellini) Date: Mon, 24 Mar 2014 15:43:09 +0001 Subject: Stop triaging bugs In-Reply-To: <1945940.ETraQQKv76@bzrd-ram> References: <53302590.2080008@canonical.com> <53303775.9030406@canonical.com > <533048DC.1080901@gmail.com> <1945940.ETraQQKv76@bzrd-ram> Message-ID: <1395675729.2486.1@smtp.gmail.com> On Mon, Mar 24, 2014 at 4:35 PM, Maarten Bezemer wrote: > On Monday 24 March 2014 16:01:48 Alberto Salvia Novella wrote: >> El 24/03/14 14:47, Marc Deslauriers escribió: >> > On 14-03-24 09:37 AM, Alberto Salvia Novella wrote: >> >> El 24/03/14 13:31, Marc Deslauriers escribió: >> >>> Could you please stop changing statuses of bugs you don't >> intend on >> >>> fixing yourself? >> >>> >> >>> Marking a bug as "triaged" and changing priorities on them makes >> >>> absolutely no sense if you aren't tasked to fix them. >> >>> >> >>> Changing one of my team's bugs to "triaged" means our scripts >> and >> >>> procedures no longer consider the bug to be new, hence, nobody >> will >> >>> look at it anymore. It is breaking our workflow. >> >> >> >> As said in the bug statuses >> >> >> page, which arbitrates the hole bug management work-flow in >> Launchpad, >> >> "triaged" means "a member of UbuntuBugControl >> >> believes that the >> report >> >> describes a genuine bug in enough detail that a developer could >> start >> >> working on a fix." >> >> >> >> Moreover, according to lean management >> >> >> >> : >> >> * The first source of flaws (or any waste) is them to remain >> invisible >> >> (or >> >> >> >> untriaged or with unset priority in the case of bug >> management). >> >> >> >> * Unpredictable work-flow has to be done manually till, after >> some >> >> continuous>> >> >> improvement and waste reduction, it becomes regular. >> >> >> >> So, since your work-flow conflicts with Launchpad's one and with >> >> principal >> >> productivity recommendations, I'm sorry I'm not taking on your >> request; >> >> except if I'm missing something. >> > >> > (...) >> > Modifying in an arbitrary way bug statuses and priorities that >> teams >> > depend on to track work is simply a bad idea. >> > (...) >> >> What do you think; Quality, BugSquad and BugControl; about this >> topic? > > Each group uses the status (and other) field(s) for their own use. > Depending on > the bug and where it is send to, one should use the definitions of > the group > responsible. In this case the bugs (apparently) belong to a group > that use > different 'definitions' of the status field, than Bug Squat does. > > I have seen information on different uses of the bug fields somewhere > on > wiki.ubuntu.com but I cannot find it anymore..? Probably you are referring to this? https://wiki.ubuntu.com/Bugs/Bug%20triage#Special_types_of_bugs > I suppose this needs to be made more clear on > https://wiki.ubuntu.com/Bugs/Bug%20statuses maybe with a list of > links to the > other groups and their descriptions/use of the fields. > > Regards, > Maarten > > -- > 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 Mon Mar 24 15:54:14 2014 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Mon, 24 Mar 2014 16:54:14 +0100 Subject: Stop triaging bugs In-Reply-To: <1395675729.2486.1@smtp.gmail.com> References: <53302590.2080008@canonical.com> <53303775.9030406@canonical.com > <533048DC.1080901@gmail.com> <1945940.ETraQQKv76@bzrd-ram> <1395675729.2486.1@smtp.gmail.com> Message-ID: <53305526.4080601@gmail.com> El 24/03/14 16:42, Andrea Corbellini escribió: > Probably you are referring to this? > https://wiki.ubuntu.com/Bugs/Bug%20triage#Special_types_of_bugs Yes, here we have the problem. It has been a mistake of me, sorry. It will be good if the bug triage page could be simplified. -------------- next part -------------- An HTML attachment was scrubbed... URL: From corbellini.andrea at gmail.com Mon Mar 24 15:56:26 2014 From: corbellini.andrea at gmail.com (Andrea Corbellini) Date: Mon, 24 Mar 2014 15:57:26 +0001 Subject: Stop triaging bugs In-Reply-To: <53305526.4080601@gmail.com> References: <53302590.2080008@canonical.com> <533048DC.1080901@gmail.com> < 1945940.ETraQQKv76@bzrd-ram> <1395675729.2486.1@smtp.gmail.com> <53305526. 4080601@gmail.com> Message-ID: <1395676586.2486.2@smtp.gmail.com> On Mon, Mar 24, 2014 at 4:54 PM, Alberto Salvia Novella wrote: > El 24/03/14 16:42, Andrea Corbellini escribió: >> Probably you are referring to this? >> https://wiki.ubuntu.com/Bugs/Bug%20triage#Special_types_of_bugs > Yes, here we have the problem. It has been a mistake of me, sorry. > > It will be good if the bug triage page could be simplified. Or probably each 'special' package needs to have a note on its Launchpad page stating that non-standard triaging rules apply. -------------- next part -------------- An HTML attachment was scrubbed... URL: From teward at trekweb.org Mon Mar 24 15:59:49 2014 From: teward at trekweb.org (Thomas Ward) Date: Mon, 24 Mar 2014 11:59:49 -0400 Subject: [Ubuntu-bugcontrol] Stop triaging bugs In-Reply-To: <1395676586.2486.2@smtp.gmail.com> References: <53302590.2080008@canonical.com> <533048DC.1080901@gmail.com> < 1945940.ETraQQKv76@bzrd-ram> <1395675729.2486.1@smtp.gmail.com> <53305526. 4080601@gmail.com> <1395676586.2486.2@smtp.gmail.com> Message-ID: <2E0E6F15-F3EA-468F-A484-1C135EEB0470@trekweb.org> Correct me if I'm wrong, but the Triage Guide already IDs special package sets that have special rules, doesn't it? *Sent from my iPhone. Please excuse any typos, as they are likely to happen by accident.* > On Mar 24, 2014, at 11:56, Andrea Corbellini wrote: > >> On Mon, Mar 24, 2014 at 4:54 PM, Alberto Salvia Novella wrote: >> El 24/03/14 16:42, Andrea Corbellini escribió: >>> Probably you are referring to this? >>> https://wiki.ubuntu.com/Bugs/Bug%20triage#Special_types_of_bugs >> Yes, here we have the problem. It has been a mistake of me, sorry. >> >> It will be good if the bug triage page could be simplified. > > Or probably each 'special' package needs to have a note on its Launchpad page stating that non-standard triaging rules apply. > _______________________________________________ > Mailing list: https://launchpad.net/~ubuntu-bugcontrol > Post to : ubuntu-bugcontrol at lists.launchpad.net > Unsubscribe : https://launchpad.net/~ubuntu-bugcontrol > More help : https://help.launchpad.net/ListHelp -------------- next part -------------- An HTML attachment was scrubbed... URL: From es20490446e at gmail.com Mon Mar 24 16:07:03 2014 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Mon, 24 Mar 2014 17:07:03 +0100 Subject: Stop triaging bugs In-Reply-To: <1395675729.2486.1@smtp.gmail.com> References: <53302590.2080008@canonical.com> <53303775.9030406@canonical.com > <533048DC.1080901@gmail.com> <1945940.ETraQQKv76@bzrd-ram> <1395675729.2486.1@smtp.gmail.com> Message-ID: <53305827.8050301@gmail.com> El 24/03/14 16:42, Andrea Corbellini escribió: > Probably you are referring to this? > https://wiki.ubuntu.com/Bugs/Bug%20triage#Special_types_of_bugs I have highlighted the warning, so it's clear that care is needed in these cases. From es20490446e at gmail.com Mon Mar 24 16:14:22 2014 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Mon, 24 Mar 2014 17:14:22 +0100 Subject: [Ubuntu-bugcontrol] Stop triaging bugs In-Reply-To: <2E0E6F15-F3EA-468F-A484-1C135EEB0470@trekweb.org> References: <53302590.2080008@canonical.com> <533048DC.1080901@gmail.com> < 1945940.ETraQQKv76@bzrd-ram> <1395675729.2486.1@smtp.gmail.com> <53305526. 4080601@gmail.com> <1395676586.2486.2@smtp.gmail.com> <2E0E6F15-F3EA-468F-A484-1C135EEB0470@trekweb.org> Message-ID: <533059DE.6090607@gmail.com> El 24/03/14 16:59, Thomas Ward escribió: > Correct me if I'm wrong, but the Triage Guide already IDs special > package sets that have special rules, doesn't it? I think the mistake was induce not because not being detailed in the documentation, but because the documentation being bloated. While I have taking measures to develop my triaging with zero defect, I just couldn't handle in my mind all the details in such a long and non visual page as it's the bug triage one. -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at ubuntu.com Mon Mar 24 16:13:23 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 24 Mar 2014 16:13:23 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Responses=22_by_cjwatson?= Message-ID: <20140324161323.17227.7407@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Responses" page has been changed by cjwatson: http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=371&rev2=372 Comment: remove brainstorm response, as brainstorm has been decommissioned ||Thank you for reporting this bug to Ubuntu. RELEASE reached EOL on DATE.<
>See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases <
><
>I've tried recreating this bug with RELEASE and was unable to, given the information you've provided. Please upgrade to the latest version and re-test. If the bug is still reproducible, increase the verbosity of the steps to recreate it so we can try again.<
><
>Do feel free to report any other bugs you may find.|| - == An idea to improve Ubuntu == - Note: If it is a request to add a feature to a '''specific program''' it should be '''forwarded to the upstream developers instead.''' See: [[Bugs/HowToTriage#Forwarding%20upstream|Forwarding Bugs Upsteam]] - - Not everybody requesting an improvement should be directed to brainstorm. Only larger things, or instances where it would be good to get the feedback of users, such as changing a default program. If you redirected the reporter to brainstorm, please close the bug as Invalid. - - || Thank you for taking the time to make Ubuntu better. Since what you submitted is not really a bug, or a problem, but rather an idea to improve Ubuntu, you are invited to post your idea in Ubuntu Brainstorm at http://brainstorm.ubuntu.com/ where it can be discussed, voted by the community and reviewed by developers. Thanks for taking the time to share your opinion! || - == Patch attachment not flagged as a patch == When reviewing bug attachments you might find an attachment that is a [[ Bugs/Patches | patch ]], but is not flagged. Let people know what a patch is! From noreply at ubuntu.com Mon Mar 24 16:03:09 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 24 Mar 2014 16:03:09 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Bug_triage=22_by_es20490446?= =?utf-8?q?e?= Message-ID: <20140324160309.17301.28940@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Bug triage" page has been changed by es20490446e: http://wiki.ubuntu.com/Bugs/Bug%20triage?action=diff&rev1=160&rev2=161 Most bugs are code or packaging defects, but some groups within Ubuntu also use bugs for other things. Careful attention must be paid to these bugs so as not to disrupt team processes. These classes of bugs have special rules and different meanings for the statuses. They may even have different meanings depending on where Ubuntu is in its release cycle. - '''Unless a triager is familiar with the specific process in question, adjustments to these bugs are likely to be problematic.''' + || /!\ '''Unless a triager is familiar with the specific process in question, adjustments to these bugs are likely to be problematic.'''|| ==== Developer Process Bugs ==== - /!\ ''NOTE'': You should generally not change bugs of this type ''unless'' working with a developer/packager. + You should generally not change bugs of this type ''unless'' working with a developer/packager. Bugs in this category can have subjects like: * Please merge from Debian unstable (main) From brian at canonical.com Tue Mar 25 16:02:44 2014 From: brian at canonical.com (Brian Murray) Date: Tue, 25 Mar 2014 09:02:44 -0700 Subject: [Ubuntu-bugcontrol] Stop triaging bugs In-Reply-To: <533048DC.1080901@gmail.com> References: <53302590.2080008@canonical.com> <5330351C.3030600@gmail.com> <53303775.9030406@canonical.com> <533048DC.1080901@gmail.com> Message-ID: <20140325160244.GR14425@murraytwins.com> On Mon, Mar 24, 2014 at 04:01:48PM +0100, Alberto Salvia Novella wrote: > El 24/03/14 14:47, Marc Deslauriers escribió: > >On 14-03-24 09:37 AM, Alberto Salvia Novella wrote: > >>El 24/03/14 13:31, Marc Deslauriers escribió: > >>>Could you please stop changing statuses of bugs you don't intend on fixing yourself? > >>> > >>>Marking a bug as "triaged" and changing priorities on them makes absolutely no > >>>sense if you aren't tasked to fix them. > >>> > >>>Changing one of my team's bugs to "triaged" means our scripts and procedures no > >>>longer consider the bug to be new, hence, nobody will look at it anymore. It is > >>>breaking our workflow. > >>As said in the bug statuses page, > >>which arbitrates the hole bug management work-flow in Launchpad, "triaged" means > >>"a member of UbuntuBugControl > >>believes that the report describes a genuine bug in enough detail that a > >>developer could start working on a fix." > >> > >>Moreover, according to lean management > >>: > >> > >> * The first source of flaws (or any waste) is them to remain invisible (or > >> untriaged or with unset priority in the case of bug management). > >> * Unpredictable work-flow has to be done manually till, after some continuous > >> improvement and waste reduction, it becomes regular. > >> > >>So, since your work-flow conflicts with Launchpad's one and with principal > >>productivity recommendations, I'm sorry I'm not taking on your request; except > >>if I'm missing something. > >> > >(...) > >Modifying in an arbitrary way bug statuses and priorities that teams depend on > >to track work is simply a bad idea. > >(...) > What do you think; Quality, BugSquad and BugControl; about this topic? It's hard to have an opinion on something without complete details of the situation. What particular bug number was this message regarding? -- Brian Murray From es20490446e at gmail.com Tue Mar 25 16:15:32 2014 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Tue, 25 Mar 2014 17:15:32 +0100 Subject: [Ubuntu-bugcontrol] Stop triaging bugs In-Reply-To: <20140325160244.GR14425@murraytwins.com> References: <53302590.2080008@canonical.com> <5330351C.3030600@gmail.com> <53303775.9030406@canonical.com> <533048DC.1080901@gmail.com> <20140325160244.GR14425@murraytwins.com> Message-ID: <5331ABA4.8020308@gmail.com> El 25/03/14 17:02, Brian Murray escribió: > What particular bug number was this message regarding? Marc was referring to the following work-flow (security bugs with an status of "new"). -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian at ubuntu.com Tue Mar 25 22:32:28 2014 From: brian at ubuntu.com (Brian Murray) Date: Tue, 25 Mar 2014 15:32:28 -0700 Subject: Fwd: Re: [Bug 1285801] Re: virtuoso-t crashed with SIGSEGV on system startup In-Reply-To: <532F1F8E.40402@gmail.com> References: <532F1F8E.40402@gmail.com> Message-ID: <20140325223228.GY14425@murraytwins.com> On Sun, Mar 23, 2014 at 06:53:18PM +0100, Alberto Salvia Novella wrote: > What shall be done in this case? Could you please provide some more information about this particular situation so we can better provide advice? -- Brian Murray Ubuntu Bug Master From serge.hallyn at ubuntu.com Tue Mar 25 21:24:26 2014 From: serge.hallyn at ubuntu.com (Serge Hallyn) Date: Tue, 25 Mar 2014 16:24:26 -0500 Subject: [Ubuntu-bugcontrol] Stop triaging bugs In-Reply-To: <5331ABA4.8020308@gmail.com> References: <53302590.2080008@canonical.com> <5330351C.3030600@gmail.com> <53303775.9030406@canonical.com> <533048DC.1080901@gmail.com> <20140325160244.GR14425@murraytwins.com> <5331ABA4.8020308@gmail.com> Message-ID: <20140325212426.GA14857@sergelap> Switching to using tags instead of status to manage the workflow might be less likely to get trampled on, but only so much. Would it interfere with the workflow to have the bugs assigned to Ubuntu Security Team (regardless of status)? I don't think anyone would touch a bug assigned to them... Quoting Alberto Salvia Novella (es20490446e at gmail.com): > El 25/03/14 17:02, Brian Murray escribió: > >What particular bug number was this message regarding? > Marc was referring to the following work-flow > (security bugs with an status of > "new"). > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad From es20490446e at gmail.com Wed Mar 26 02:25:50 2014 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Wed, 26 Mar 2014 03:25:50 +0100 Subject: [Bug 1285801] Re: virtuoso-t crashed with SIGSEGV on system startup In-Reply-To: <20140325223228.GY14425@murraytwins.com> References: <532F1F8E.40402@gmail.com> <20140325223228.GY14425@murraytwins.com> Message-ID: <53323AAE.2010300@gmail.com> El 25/03/14 23:32, Brian Murray escribió: > Could you please provide some more information about this particular > situation so we can better provide advice? Perhaps Obey can. From brendan.donegan at canonical.com Wed Mar 26 08:54:39 2014 From: brendan.donegan at canonical.com (Brendan Donegan) Date: Wed, 26 Mar 2014 08:54:39 +0000 Subject: [Ubuntu-bugcontrol] Stop triaging bugs In-Reply-To: References: <53302590.2080008@canonical.com> <5330351C.3030600@gmail.com> <53303775.9030406@canonical.com> <533048DC.1080901@gmail.com> <20140325160244.GR14425@murraytwins.com> <5331ABA4.8020308@gmail.com> Message-ID: <533295CF.6040203@canonical.com> IMO, a team should also be looking at Triaged bugs when selecting new tasks to work on, so if the bugs are genuinely Triaged and they have enough information to go to In Progress (when a developer wants to work on them) then I don't see the harm in general. I personally would tend to look at both New and Triaged bugs when looking to pick up bug fixing work on the projects I help maintain. On 26/03/14 03:14, Pierre Equoy wrote: > On Wed, Mar 26, 2014 at 12:15 AM, Alberto Salvia Novella < > es20490446e at gmail.com> wrote: > >> El 25/03/14 17:02, Brian Murray escribió: >> >> What particular bug number was this message regarding? >>> >> Marc was referring to the following work-flow >> (security bugs with an status of "new"). >> >> > Would it be possible for the security team to update this workflow to: > security bugs with status in ("New", "Triaged") > ? > > That would be a request like this: > https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=&search=Search&field.status%3Alist=NEW&field.status%3Alist=TRIAGED&field.information_type%3Alist=PUBLICSECURITY&field.information_type%3Alist=PRIVATESECURITY&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.component-empty-marker=1&field.tag=&field.tags_combinator=ANY&field.status_upstream-empty-marker=1&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_no_package.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&orderby=-importance&memo=75&start=0&direction=backwards > > (I took the previous one and added issues with a "TRIAGED" status) > > Cheers, > > From pierre.equoy at gmail.com Wed Mar 26 03:14:43 2014 From: pierre.equoy at gmail.com (Pierre Equoy) Date: Wed, 26 Mar 2014 11:14:43 +0800 Subject: [Ubuntu-bugcontrol] Stop triaging bugs In-Reply-To: <5331ABA4.8020308@gmail.com> References: <53302590.2080008@canonical.com> <5330351C.3030600@gmail.com> <53303775.9030406@canonical.com> <533048DC.1080901@gmail.com> <20140325160244.GR14425@murraytwins.com> <5331ABA4.8020308@gmail.com> Message-ID: On Wed, Mar 26, 2014 at 12:15 AM, Alberto Salvia Novella < es20490446e at gmail.com> wrote: > El 25/03/14 17:02, Brian Murray escribió: > > What particular bug number was this message regarding? >> > Marc was referring to the following work-flow > (security bugs with an status of "new"). > > Would it be possible for the security team to update this workflow to: security bugs with status in ("New", "Triaged") ? That would be a request like this: https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=&search=Search&field.status%3Alist=NEW&field.status%3Alist=TRIAGED&field.information_type%3Alist=PUBLICSECURITY&field.information_type%3Alist=PRIVATESECURITY&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_commenter=&field.subscriber=&field.structural_subscriber=&field.component-empty-marker=1&field.tag=&field.tags_combinator=ANY&field.status_upstream-empty-marker=1&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_no_package.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on&field.has_blueprints.used=&field.has_blueprints=on&field.has_no_blueprints.used=&field.has_no_blueprints=on&orderby=-importance&memo=75&start=0&direction=backwards (I took the previous one and added issues with a "TRIAGED" status) Cheers, -- Pierre Equoy -------------- next part -------------- An HTML attachment was scrubbed... URL: From es20490446e at gmail.com Wed Mar 26 12:45:13 2014 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Wed, 26 Mar 2014 13:45:13 +0100 Subject: [Ubuntu-bugcontrol] Stop triaging bugs In-Reply-To: <533295CF.6040203@canonical.com> References: <53302590.2080008@canonical.com> <5330351C.3030600@gmail.com> <53303775.9030406@canonical.com> <533048DC.1080901@gmail.com> <20140325160244.GR14425@murraytwins.com> <5331ABA4.8020308@gmail.com> <533295CF.6040203@canonical.com> Message-ID: <5332CBD9.6010504@gmail.com> El 26/03/14 09:54, Brendan Donegan escribió: > IMO, a team should also be looking at Triaged bugs when selecting new > tasks to work on, so if the bugs are genuinely Triaged and they have > enough information to go to In Progress (when a developer wants to work > on them) then I don't see the harm in general. I personally would tend > to look at both New and Triaged bugs when looking to pick up bug fixing > work on the projects I help maintain. Just imitate the One Hundred Papercuts work-flow 's concepts :P * In general: simple over correct, because correction is the child of simplicity. Simplicity makes problems to became obvious rapidly, and to be easy to change. So focus on this, because is what really matters. * Starting by deciding where to start (setting importance), so your work will attach what is more needed first. The 80% of return belongs to only the 20% of developed work, so start there. * Then with the latest step in the bug fixing process, so every piece of work is immediately poured in real improvement, instead of having unfinished work along the hole process. * Making information visually obvious to anyone, because visually is how information is processed more rapidly and in detail by the brain; and you'll want people helping you to be easy for them. * Measured, because processes tend to improve themselves when what's going on becomes obvious. * Parted, so its simple to accomplish one task; instead of having to pay attention to a bunch of things. Anything can be accomplished by dividing it into small goals. * It doesn't need much discussion, because the system is self-explanatory: serve yourself! * And adjusted to what is really required, not what you think it's required. The second can easily be a slant. The result is generally something very small and minimalist that rarely will be noticed as what is: a power tool. As a rule of thumbs, as the tap when you open it for water, if it looks just too simple and easy to accomplish to be real; probably is well designed. Just notice, as result of working like that, we have at this time only 19 confirmed bugs with unknown priority for Trusty from the hundreds we had only three days ago :D (look at the final clean-up ) Philosophical but already powerful. Regards @_@ -------------- next part -------------- An HTML attachment was scrubbed... URL: From hggdh2 at ubuntu.com Wed Mar 26 15:36:34 2014 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Wed, 26 Mar 2014 10:36:34 -0500 Subject: [Ubuntu-bugcontrol] Stop triaging bugs In-Reply-To: <533295CF.6040203@canonical.com> References: <53302590.2080008@canonical.com> <5330351C.3030600@gmail.com> <53303775.9030406@canonical.com> <533048DC.1080901@gmail.com> <20140325160244.GR14425@murraytwins.com> <5331ABA4.8020308@gmail.com> <533295CF.6040203@canonical.com> Message-ID: On Wed, Mar 26, 2014 at 3:54 AM, Brendan Donegan < brendan.donegan at canonical.com> wrote: > IMO, a team should also be looking at Triaged bugs when selecting new > tasks to work on, so if the bugs are genuinely Triaged and they have > enough information to go to In Progress (when a developer wants to work > on them) then I don't see the harm in general. I personally would tend > to look at both New and Triaged bugs when looking to pick up bug fixing > work on the projects I help maintain. > It all depends. There is NO one-size-fits-all that will work. The security team (as well as the kernel team, and others) have special workflows. One problem we have in launchpad is that there is no concept of workflow, all we have are bugs (as far as we are concerned). Workflow was hammered in bugs, using what launchpad provides. (Also, you have imposed yourself a limit -- "when looking (...) on the projects I help maintain". You do not go and change bugs on projects you DO NOT maintain. You actually may go in, but you will be more careful.) But, back to the issue at hand. The majority of security bugs shown with Alberto's search are *visibly* different from the "normal" bugs we deal with. I expect triagers to be careful on what they do -- if a certain bug looks different from the "common" (whatever it may mean) bug, STOP. Find why it is different. Don't assume that it is all the same. And, of course, we should document these special workflows, at least to allow triagers to identify them. ..C.. -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian at ubuntu.com Wed Mar 26 15:48:10 2014 From: brian at ubuntu.com (Brian Murray) Date: Wed, 26 Mar 2014 08:48:10 -0700 Subject: [Ubuntu-bugcontrol] Stop triaging bugs In-Reply-To: References: <53302590.2080008@canonical.com> <5330351C.3030600@gmail.com> <53303775.9030406@canonical.com> <533048DC.1080901@gmail.com> <20140325160244.GR14425@murraytwins.com> <5331ABA4.8020308@gmail.com> <533295CF.6040203@canonical.com> Message-ID: <20140326154810.GC14425@murraytwins.com> On Wed, Mar 26, 2014 at 10:36:34AM -0500, C de-Avillez wrote: > On Wed, Mar 26, 2014 at 3:54 AM, Brendan Donegan < > brendan.donegan at canonical.com> wrote: > > > IMO, a team should also be looking at Triaged bugs when selecting new > > tasks to work on, so if the bugs are genuinely Triaged and they have > > enough information to go to In Progress (when a developer wants to work > > on them) then I don't see the harm in general. I personally would tend > > to look at both New and Triaged bugs when looking to pick up bug fixing > > work on the projects I help maintain. > > > > It all depends. There is NO one-size-fits-all that will work. The security > team (as well as the kernel team, and others) have special workflows. One > problem we have in launchpad is that there is no concept of workflow, all > we have are bugs (as far as we are concerned). Workflow was hammered in > bugs, using what launchpad provides. > > (Also, you have imposed yourself a limit -- "when looking (...) on the > projects I help maintain". You do not go and change bugs on projects you DO > NOT maintain. You actually may go in, but you will be more careful.) > > But, back to the issue at hand. The majority of security bugs shown with > Alberto's search are *visibly* different from the "normal" bugs we deal > with. I expect triagers to be careful on what they do -- if a certain bug > looks different from the "common" (whatever it may mean) bug, STOP. Find > why it is different. Don't assume that it is all the same. And, if something is different or you have any doubts ask for help either in the #ubuntu-bugs channel on irc or on the ubuntu-bugsquad mailing list. If you don't get an answer in a timely fashion ping me and I'll do my best to respond. -- Brian Murray -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From corbellini.andrea at gmail.com Wed Mar 26 17:36:28 2014 From: corbellini.andrea at gmail.com (Andrea Corbellini) Date: Wed, 26 Mar 2014 17:37:28 +0001 Subject: [Ubuntu-bugcontrol] Stop triaging bugs In-Reply-To: <533295CF.6040203@canonical.com> References: <53302590.2080008@canonical.com> <5330351C.3030600@gmail.com> <53303775.9030406@canonical.com> <533048DC.1080901@gmail.com> <20140325160244.GR14425@murraytwins.com> <5331ABA4.8020308@gmail.com> <533295CF.6040203@canonical.com> Message-ID: <1395855388.8966.1@smtp.gmail.com> On Wed, Mar 26, 2014 at 9:54 AM, Brendan Donegan wrote: > IMO, a team should also be looking at Triaged bugs when selecting new > tasks to work on, so if the bugs are genuinely Triaged and they have > enough information to go to In Progress (when a developer wants to > work > on them) then I don't see the harm in general. I personally would tend > to look at both New and Triaged bugs when looking to pick up bug > fixing > work on the projects I help maintain. As I see it, we (bug triagers) work for developers. If developers are not happy, than it's our fault, we can't blame them: they're our customers! We are free to discuss/blame their practices and suggest improvements. However such suggestions must reach the correct people (in this case, if I have understood correctly, the Ubuntu security team). We can't decide for them. But in my opinion, the real problem here is that either Launchpad or the Ubuntu Wiki or the security team fail to communicate that security bugs are special and shouldn't be touched unless you know the correct workflow. -------------- next part -------------- An HTML attachment was scrubbed... URL: From brendan.donegan at canonical.com Wed Mar 26 15:42:23 2014 From: brendan.donegan at canonical.com (Brendan Donegan) Date: Wed, 26 Mar 2014 15:42:23 +0000 Subject: [Ubuntu-bugcontrol] Stop triaging bugs In-Reply-To: References: <53302590.2080008@canonical.com> <5330351C.3030600@gmail.com> <53303775.9030406@canonical.com> <533048DC.1080901@gmail.com> <20140325160244.GR14425@murraytwins.com> <5331ABA4.8020308@gmail.com> <533295CF.6040203@canonical.com> Message-ID: <5332F55F.5060800@canonical.com> On 26/03/14 15:36, C de-Avillez wrote: > On Wed, Mar 26, 2014 at 3:54 AM, Brendan Donegan < > brendan.donegan at canonical.com> wrote: > >> IMO, a team should also be looking at Triaged bugs when selecting new >> tasks to work on, so if the bugs are genuinely Triaged and they have >> enough information to go to In Progress (when a developer wants to work >> on them) then I don't see the harm in general. I personally would tend >> to look at both New and Triaged bugs when looking to pick up bug fixing >> work on the projects I help maintain. >> > > It all depends. There is NO one-size-fits-all that will work. The security > team (as well as the kernel team, and others) have special workflows. One > problem we have in launchpad is that there is no concept of workflow, all > we have are bugs (as far as we are concerned). Workflow was hammered in > bugs, using what launchpad provides. > > (Also, you have imposed yourself a limit -- "when looking (...) on the > projects I help maintain". You do not go and change bugs on projects you DO > NOT maintain. You actually may go in, but you will be more careful.) No, I wasn't talking about Triaging bugs, I was talking about picking up new bugs to work on. > > But, back to the issue at hand. The majority of security bugs shown with > Alberto's search are *visibly* different from the "normal" bugs we deal > with. I expect triagers to be careful on what they do -- if a certain bug > looks different from the "common" (whatever it may mean) bug, STOP. Find > why it is different. Don't assume that it is all the same. It is the purpose of bug-control to triage bugs in Ubuntu - if there are exceptions to that then they should be documented. It sounds like we're talking about CVE's specifically and I can understand how they'd be a special case. I guess this should be documented somewhere. We shouldn't expect people to guess. > > And, of course, we should document these special workflows, at least to > allow triagers to identify them. > > ..C.. >