From kamusin at gmail.com Mon Apr 4 19:44:33 2011 From: kamusin at gmail.com (Kamus) Date: Mon, 4 Apr 2011 16:44:33 -0300 Subject: Announcing the Next Ubuntu Bug Day! April 06th 2011 Message-ID: Fellow Ubuntu Triagers! This week's Bug Day targets are *drum roll please* Unity! * 49 New bugs need a hug * 49 Incomplete bugs need a status check * 49 Confirmed bugs need a review Bookmark it, add it to your calendars, turn over those egg-timers! * 06 April 2011 * https://wiki.ubuntu.com/UbuntuBugDay/20110406 Are you looking for a way to start giving some love back to your adorable Ubuntu Project? Did you ever wonder what Triage is? Want to learn about that? This is a perfect time!, Everybody can help in a Bug Day! open your IRC Client and go to #ubuntu-bugs (FreeNode) the BugSquad will be happy to help you to start contributing! Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! We are always looking for new tasks or ideas for the Bug Days, if you have one add it to the Planning page https://wiki.ubuntu.com/UbuntuBugDay/Planning If you're new to all this, head to http://wiki.ubuntu.com/Bugs Have a nice day, Kamus [from bugsquad] -- Victor Vargas B. Latitud:  -33.439177,-70.625267 Santiago, Chile. From cyan.spam at gmail.com Tue Apr 5 00:16:44 2011 From: cyan.spam at gmail.com (David Tombs) Date: Mon, 04 Apr 2011 20:16:44 -0400 Subject: New Wiki Structure Proposal In-Reply-To: References: Message-ID: <4D9A5F6C.7000501@gmail.com> On 03/20/2011 10:41 AM, Draycen DeCator wrote: > Hello fellow triagers! > > There has been a lot of discussion on IRC between the BugSquad and the > Ubuntu Beginners Team about how the BugSquad wiki can be improved so > it's more streamlined and user-friendly. As it stands now, the > HowToTriage page is the primary place for people to go and dump any > information related to triage. This has resulted in the page just being > a wall of text that is overwhelming to new users who are just getting > started. > > To improve this, the information will need to be spread out in a logical > way that walks new users through the process from beginning to end. > Attached is a mindmap showing what my proposal is for how this can be > done (I've included an image for those who just want to view it, and the > Freemind file if you want to make any changes). For a new user, they > would follow the whole setup from the top down, so it would walk them > through the entire process. For those with some experience, hopefully it > will be easy to get to the information that they need. > > As for the HowToTriage page, it would be more of an expansion of the > flowcharts that are on the wiki. This way, it will become a step-by-step > guide or a checklist for the triage process that anybody can follow. > > Take a look and let me know what you think. Once an initial structure is > decided on, I will make at least a few PDFs showing a concept of how the > actual pages will be setup. Those will then be sent to both the BugSquad > and the UBT mailing lists for further input. Eventually, the UBT Wiki > group will be helping us implement the changes. > > Hope you're all having a great weekend! > Dray Yes, Draycen, I agree with you. An explanation of flowcharts would be very good for beginners, it takes a lot of the guesswork out of the workflow. Thanks! David From dmcdonnell at hotmail.com Tue Apr 5 13:29:28 2011 From: dmcdonnell at hotmail.com (Dermot McDonnell) Date: Tue, 5 Apr 2011 13:29:28 +0000 Subject: Ondemand Frequency Governor broken in Ubuntu Natty (11.04) and work around Message-ID: I have had ubuntu for some time on a Dell Studio 1735 laptop with the latest bios. I have used ubuntu natty (11.04) 64-bit for two weeks and subscribe to daily updates. Last Friday, I upgraded my cpu to an Intel core 2 duo T7500 from an Intel mobile celeron dual core T1500. The T7500 has a 2.2GHz maximum cpu clock and a four times larger level 2 cache than the T1500 which has a maximum 1.86GHz cpu clock. Both cpus, T1500 & T7500, are rated 35W TDP (thermal design power). The old T1500 always ran at 1861MHz according to the Ubuntu System Profiler and Benchmark utility. Sadly, the T7500 ran at 1200MHz upon installation regardless of what applications were running. The power supply for my Dell Studio is a 65W unit. Upon first boot with the T7500 cpu, the bios reported I should be using the Dell 95W power supply. I examined /sys/devices/system/cpu/cpu0/cpufreq/bios_limit which reported 1200000 (1200MHz) as the cpu frequency limit imposed by the Dell bios. No changes to the Dell bios settings made any difference to this limit. After doing some research, I followed an on-line suggestion which fixed that issue - I added the line: GRUB_CMDLINE_LINUX="processor.ignore_ppc=1" to /etc/default/grub (see http://techmonks.net/bypassing-the-dell-unrecognized-adapter-issue). Remember to update grub if you do this! The /sys/devices/system/cpu/cpu0/cpufreq/bios_limit now reports 2201000 (2201MHz) as the cpu frequency limit. However, the actual cpu frequency rate remained stubbornly at 1.2GHz regardless of load. cpufreq-info reported: current policy: frequency should be within 1.20 GHz and 2.20 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.20 GHz. I had some success editing /etc/inid.d/local, inserting the lines: sudo cpufreq-set -c 0 -g conservative -d 1.6GHz sudo cpufreq-set -c 1 -g conservative -d 1.6GHz This script is executed at boot. In the above case, cpufreq-set, imposes a minimum frequency, -d 1.6GHz, on each cpu core, -c 0 & -c 1, and hands control to the governor "conservative" via -g conservative. This worked great for a brief period, only for the governor to change back to "ondemand" automagically and a complete end to any frequency scaling. Further research led me to edit the shell script /etc/init.d/ondemand which seems to get run regularly, imposing the seemingly broken "ondemand" governor instead of the perfectly functional "conservative" governor. I replaced the word "ondemand" with "conservative": for CPUFREQ in /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor do [ -f $CPUFREQ ] || continue echo -n conservative > $CPUFREQ done My laptop now responds wonderfully well to load and I have no power supply issues or over heating. Best regards to all, Dermot McDonnell Castlebar, Mayo, Ireland. -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at ubuntu.com Tue Apr 5 20:22:48 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 05 Apr 2011 20:22:48 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Unity/FilingBugs=22_by_jorge?= Message-ID: <20110405202248.14193.21074@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by jorge: http://wiki.ubuntu.com/Unity/FilingBugs?action=diff&rev1=36&rev2=37 ------------------------------------------------------------------------------ ... - (gdb) set logging file 'unity.log' + (gdb) set logging file unity.log (gdb) set logging on (gdb) b _exit Function "_exit" not defined. From kamusin at gmail.com Thu Apr 7 16:06:02 2011 From: kamusin at gmail.com (Victor Vargas) Date: Thu, 07 Apr 2011 13:06:02 -0300 Subject: Announcing the Next Ubuntu Bug Day! April 08th 2011 Message-ID: <4D9DE0EA.7020301@gmail.com> Fellow Ubuntu Triagers! This week's Bug Day targets are*drum roll please* update-manager! * 50 New bugs need a hug * 13 Incomplete bugs need a status check * 15 Confirmed bugs need a review Bookmark it, add it to your calendars, turn over those egg-timers! * 08 April 2011 *https://wiki.ubuntu.com/UbuntuBugDay/20110408 Are you looking for a way to start giving some love back to your adorable Ubuntu Project? Did you ever wonder what Triage is? Want to learn about that? This is a perfect time!, Everybody can help in a Bug Day! open your IRC Client and go to #ubuntu-bugs (FreeNode) the BugSquad will be happy to help you to start contributing! Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! We are always looking for new tasks or ideas for the Bug Days, if you have one add it to the Planning page https://wiki.ubuntu.com/UbuntuBugDay/Planning If you're new to all this, head tohttp://wiki.ubuntu.com/Bugs Have a nice day, Kamus [from bugsquad] -- Victor Vargas B. Latitud: -33.439177,-70.625267 Santiago, Chile. -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at ubuntu.com Fri Apr 8 18:51:51 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Fri, 08 Apr 2011 18:51:51 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Unity/FilingBugs=22_by_vish?= Message-ID: <20110408185151.7775.85385@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by vish: http://wiki.ubuntu.com/Unity/FilingBugs?action=diff&rev1=37&rev2=38 The comment on the change is: adding a link for Unity "needs-design" bugs ------------------------------------------------------------------------------ || [[https://launchpad.net/ubuntu/+source/compiz/+bugs?field.tag=unity|`unity`]] || Compiz bugs which are affecting Unity || || [[https://launchpad.net/ubuntu/+bugs?field.tag=running-unity|`running-unity`]] || Bugs reported by people who are running Unity || || [[https://launchpad.net/unity/+bugs?field.tag=bitesize|`bitesize`]] || Smaller bugs that would be ideal for new contributors. || + || [[https://launchpad.net/unity/+bugs?field.tag=needs-design|`needs-design`]] || A bug that needs UI design done first. || || ... || ... || From noreply at ubuntu.com Mon Apr 11 13:11:14 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Mon, 11 Apr 2011 13:11:14 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Events=22_by_pvillavi?= Message-ID: <20110411131114.23664.38992@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by pvillavi: http://wiki.ubuntu.com/Bugs/Events?action=diff&rev1=248&rev2=249 ------------------------------------------------------------------------------ || '''Name''' || '''Tag used''' || ## StartHugDayParsing + || [[UbuntuBugDay/20110414| Ubuntu Translations]] || hugday-20110414 || || [[UbuntuBugDay/20110303| USB Creator]] || hugday-20110303 || || [[UbuntuBugDay/20110210| OpenOffice/LibreOffice]] || hugday-20110210 || || [[UbuntuBugDay/20110203| Rhythmbox]] || hugday-20110203 || From yofel at gmx.net Mon Apr 11 18:26:52 2011 From: yofel at gmx.net (Philip Muskovac) Date: Mon, 11 Apr 2011 20:26:52 +0200 Subject: Bugsquad meeting reminder 04/12 Message-ID: <4DA347EC.8060104@gmx.net> Just a reminder that our monthly meeting is scheduled for tomorrow April 12. You can find and update the agenda items on https://wiki.ubuntu.com/BugSquad/Meeting Philip From brian at ubuntu.com Mon Apr 11 20:52:11 2011 From: brian at ubuntu.com (Brian Murray) Date: Mon, 11 Apr 2011 13:52:11 -0700 Subject: New Wiki Structure Proposal In-Reply-To: References: Message-ID: <20110411205211.GJ2525@murraytwins.com> On Sun, Mar 20, 2011 at 09:41:37AM -0500, Draycen DeCator wrote: > Hello fellow triagers! > > There has been a lot of discussion on IRC between the BugSquad and the > Ubuntu Beginners Team about how the BugSquad wiki can be improved so it's > more streamlined and user-friendly. As it stands now, the HowToTriage page > is the primary place for people to go and dump any information related to > triage. This has resulted in the page just being a wall of text that is > overwhelming to new users who are just getting started. > > To improve this, the information will need to be spread out in a logical way > that walks new users through the process from beginning to end. Attached is > a mindmap showing what my proposal is for how this can be done (I've > included an image for those who just want to view it, and the Freemind file > if you want to make any changes). For a new user, they would follow the > whole setup from the top down, so it would walk them through the entire > process. For those with some experience, hopefully it will be easy to get to > the information that they need. > > As for the HowToTriage page, it would be more of an expansion of the > flowcharts that are on the wiki. This way, it will become a step-by-step > guide or a checklist for the triage process that anybody can follow. I like what you've done here and the spreading out of the information makes a lot of sense to me but I'm not certain it addresses the issue of it being overwhelming. I've an idea about having two different categories of How to Triage one basic one that shows you how to get your toe wet if you will, as just confirming a bug report and adding a comment is part of the triage process, and a more advanced diving in one that links to all the possible ways to triage a bug report. > Take a look and let me know what you think. Once an initial structure is > decided on, I will make at least a few PDFs showing a concept of how the > actual pages will be setup. Those will then be sent to both the BugSquad and > the UBT mailing lists for further input. Eventually, the UBT Wiki group will > be helping us implement the changes. In the image is the "Special Bugs" portion a part of "Types of Bugs"? I think it should be if it isn't. I'm looking forward to seeing some more work on this. Thanks! -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From bayan.rafeh93 at gmail.com Tue Apr 12 08:15:48 2011 From: bayan.rafeh93 at gmail.com (Bayan Rafeh) Date: Tue, 12 Apr 2011 11:15:48 +0300 Subject: Updating PPA sources through proxy Message-ID: I have everything set including the bashrc and the /etc/apt/apt.conf folder but I cannot update ppa sources, or work with any of them for some reason. I get a 407 proxy authentication required error every time a ppa source is being updated in the sudo apt-get update process. Any help greatly appreciated -------------- next part -------------- An HTML attachment was scrubbed... URL: From rohangarg at ubuntu.com Tue Apr 12 15:49:28 2011 From: rohangarg at ubuntu.com (Rohan Garg) Date: Tue, 12 Apr 2011 21:19:28 +0530 Subject: Updating PPA sources through proxy In-Reply-To: References: Message-ID: Hi Did you try putting : * Acquire::http::proxy “http://username:password at proxy.blah.com:myport″;* in */etc/apt/apt.conf.d/70debconf* instead of apt.conf ? Regards Rohan Garg On Tue, Apr 12, 2011 at 1:45 PM, Bayan Rafeh wrote: > I have everything set including the bashrc and the /etc/apt/apt.conf folder > but I cannot update ppa sources, or work with any of them for some reason. I > get a 407 proxy authentication required error every time a ppa source is > being updated in the sudo apt-get update process. Any help greatly > appreciated > > -- > 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 ddecator at ubuntu.com Tue Apr 12 21:27:30 2011 From: ddecator at ubuntu.com (Draycen DeCator) Date: Tue, 12 Apr 2011 16:27:30 -0500 Subject: New Wiki Structure Proposal In-Reply-To: <20110411205211.GJ2525@murraytwins.com> References: <20110411205211.GJ2525@murraytwins.com> Message-ID: Initially I planned on "Special Bugs" having its own page since it seems like there would be enough information to justify it, but it could easily be added to "Types of Bugs" if we start laying out the information and it ends up making more sense there. Definitely something we'll have to think about. I also really like the idea of having a "Basic" and "Advanced" section for the "How to Triage" page, but what things would we want to classify as basic? Commenting and confirming definitely, but what about finding duplicates? Or assigning packages to bugs with no package? I feel like an argument can be made for those two, and possibly other actions, to be considered basic or advanced. Dray On Mon, Apr 11, 2011 at 3:52 PM, Brian Murray wrote: > On Sun, Mar 20, 2011 at 09:41:37AM -0500, Draycen DeCator wrote: > > Hello fellow triagers! > > > > There has been a lot of discussion on IRC between the BugSquad and the > > Ubuntu Beginners Team about how the BugSquad wiki can be improved so it's > > more streamlined and user-friendly. As it stands now, the HowToTriage > page > > is the primary place for people to go and dump any information related to > > triage. This has resulted in the page just being a wall of text that is > > overwhelming to new users who are just getting started. > > > > To improve this, the information will need to be spread out in a logical > way > > that walks new users through the process from beginning to end. Attached > is > > a mindmap showing what my proposal is for how this can be done (I've > > included an image for those who just want to view it, and the Freemind > file > > if you want to make any changes). For a new user, they would follow the > > whole setup from the top down, so it would walk them through the entire > > process. For those with some experience, hopefully it will be easy to get > to > > the information that they need. > > > > As for the HowToTriage page, it would be more of an expansion of the > > flowcharts that are on the wiki. This way, it will become a step-by-step > > guide or a checklist for the triage process that anybody can follow. > > I like what you've done here and the spreading out of the information > makes a lot of sense to me but I'm not certain it addresses the issue of > it being overwhelming. I've an idea about having two different > categories of How to Triage one basic one that shows you how to get your > toe wet if you will, as just confirming a bug report and adding a > comment is part of the triage process, and a more advanced diving in one > that links to all the possible ways to triage a bug report. > > > Take a look and let me know what you think. Once an initial structure is > > decided on, I will make at least a few PDFs showing a concept of how the > > actual pages will be setup. Those will then be sent to both the BugSquad > and > > the UBT mailing lists for further input. Eventually, the UBT Wiki group > will > > be helping us implement the changes. > > In the image is the "Special Bugs" portion a part of "Types of Bugs"? I > think it should be if it isn't. I'm looking forward to seeing some more > work on this. > > Thanks! > -- > Brian Murray > Ubuntu Bug Master > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iEYEARECAAYFAk2jafoACgkQDTAwc5ER+zXr9QCcD3QKQ+YErnH4sSXCWIn5wHK+ > xv8AoL3bl2M0ocnNeRtPzlZx5W713RvZ > =XC6Y > -----END PGP SIGNATURE----- > > -- Draycen DeCator BugSquad/UBT https://wiki.ubuntu.com/ddecator https://launchpad.net/~ddecator -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian at ubuntu.com Tue Apr 12 22:31:40 2011 From: brian at ubuntu.com (Brian Murray) Date: Tue, 12 Apr 2011 15:31:40 -0700 Subject: New Wiki Structure Proposal In-Reply-To: References: <20110411205211.GJ2525@murraytwins.com> Message-ID: <20110412223140.GM2525@murraytwins.com> On Tue, Apr 12, 2011 at 04:27:30PM -0500, Draycen DeCator wrote: > Initially I planned on "Special Bugs" having its own page since it seems > like there would be enough information to justify it, but it could easily be > added to "Types of Bugs" if we start laying out the information and it ends > up making more sense there. Definitely something we'll have to think about. > > I also really like the idea of having a "Basic" and "Advanced" section for > the "How to Triage" page, but what things would we want to classify as > basic? Commenting and confirming definitely, but what about finding > duplicates? Yes to commenting and confirming. No, to finding duplicates as it can vary in difficulty depending on the particular bug. > Or assigning packages to bugs with no package? This too can vary in difficulty however I think it is easier to know when you are uncertain. (I mean people are much more likely to make mistakes when marking duplicates than assigning packages.) So as long as we make it clear that if one is uncertain to ask for help it seems appropriate for the "Basic" section. > I feel like an argument can be made for those two, and possibly other > actions, to be considered basic or advanced. Other "Basic" actions include: Documenting steps to recreate the bug in the description Modifying the bug title to concise and descriptive Thanks, -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From dspinell at gmail.com Wed Apr 13 00:32:53 2011 From: dspinell at gmail.com (Davide Spinello) Date: Tue, 12 Apr 2011 20:32:53 -0400 Subject: No subject Message-ID: Hi, I need help with the touchpad of my acer aspire 1830t-68u118. It is ALPS touchpad and I am running ubuntu 11.04 beta1 64bit. The mouse application shows the touchpad tab with vertical scroll/two finger scrolling options, disable touchpad while typing, and horizontal scrolling. However, only basic functionalities work, and specifically I have no vertical scrolling nor two fingers scrolling. Horizontal scrolling and "deactivate while typing" do not work either. Thanks for your help -- Davide Spinello, PhD Assistant professor -------------------------------------------------------- Department of Mechanical Engineering 161 Louis Pasteur | CBY A205 University of Ottawa Ottawa ON Canada K1N 6N5 -------------------------------------------------------- e-mail: dspinell at uottawa.ca phone: 613-562-5800 ext 2460 fax: 613-562-5177 office: CBY A612 web: http://by.genie.uottawa.ca/~spinello/webpage/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From braiamp at gmail.com Wed Apr 13 02:27:39 2011 From: braiamp at gmail.com (Braiam Peguero) Date: Tue, 12 Apr 2011 22:27:39 -0400 Subject: No subject In-Reply-To: References: Message-ID: Hi Davide, This is not the place to report bugs. If you are facing issues please run <> that would help you collecting the information to helping us to fix the problem. Also you can ask in the irc at #ubuntu+1 in freenode.net. Thanks for taking the time to let us know about this and helping to make Ubuntu even better! Braiam Peguero De: ubuntu-bugsquad-bounces at lists.ubuntu.com [mailto:ubuntu-bugsquad-bounces at lists.ubuntu.com] En nombre de Davide Spinello Enviado el: martes, 12 de abril de 2011 08:33 p.m. Para: ubuntu-bugsquad at lists.ubuntu.com Asunto: Hi, I need help with the touchpad of my acer aspire 1830t-68u118. It is ALPS touchpad and I am running ubuntu 11.04 beta1 64bit. The mouse application shows the touchpad tab with vertical scroll/two finger scrolling options, disable touchpad while typing, and horizontal scrolling. However, only basic functionalities work, and specifically I have no vertical scrolling nor two fingers scrolling. Horizontal scrolling and "deactivate while typing" do not work either. Thanks for your help -- Davide Spinello, PhD Assistant professor -------------------------------------------------------- Department of Mechanical Engineering 161 Louis Pasteur | CBY A205 University of Ottawa Ottawa ON Canada K1N 6N5 -------------------------------------------------------- e-mail: dspinell at uottawa.ca phone: 613-562-5800 ext 2460 fax: 613-562-5177 office: CBY A612 web: http://by.genie.uottawa.ca/~spinello/webpage/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From kamusin at gmail.com Wed Apr 13 13:42:43 2011 From: kamusin at gmail.com (Victor Vargas) Date: Wed, 13 Apr 2011 10:42:43 -0300 Subject: Announcing the Next Ubuntu Bug Day! April 14th 2011 Message-ID: <4DA5A853.2070205@gmail.com> Fellow Ubuntu Triagers! This week's Bug Day targets are*drum roll please* *Ubuntu Translations*! * 28 New bugs need a hug * 32 Incomplete bugs need a status check * 17 Confirmed bugs need a review Bookmark it, add it to your calendars, turn over those egg-timers! * 14 April 2011 *https://wiki.ubuntu.com/UbuntuBugDay/20110414 Are you looking for a way to start giving some love back to your adorable Ubuntu Project? Did you ever wonder what Triage is? Want to learn about that? This is a perfect time!, Everybody can help in a Bug Day! open your IRC Client and go to #ubuntu-bugs (FreeNode) the BugSquad will be happy to help you to start contributing! Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! We are always looking for new tasks or ideas for the Bug Days, if you have one add it to the Planning page https://wiki.ubuntu.com/UbuntuBugDay/Planning If you're new to all this, head tohttp://wiki.ubuntu.com/Bugs Have a nice day, Kamus [from bugsquad] -- Victor Vargas B. Latitud: -33.439177,-70.625267 Santiago, Chile. -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian at ubuntu.com Wed Apr 13 15:20:08 2011 From: brian at ubuntu.com (Brian Murray) Date: Wed, 13 Apr 2011 08:20:08 -0700 Subject: your mail In-Reply-To: References: Message-ID: <20110413152008.GN2525@murraytwins.com> On Tue, Apr 12, 2011 at 08:32:53PM -0400, Davide Spinello wrote: > Hi, > > I need help with the touchpad of my acer aspire 1830t-68u118. It is ALPS > touchpad and I am running ubuntu 11.04 beta1 64bit. > > The mouse application shows the touchpad tab with vertical scroll/two finger > scrolling options, disable touchpad while typing, and horizontal scrolling. > However, only basic functionalities work, and specifically I have no > vertical scrolling nor two fingers scrolling. Horizontal scrolling and > "deactivate while typing" do not work either. The following wiki page from our Debugging Procedures should help diagnose the issue and make any bug you report more informative. https://wiki.ubuntu.com/DebuggingTouchpadDetection Please report each issue (vertical scrolling, two finger scrolling, etc...) as a separate bug report. Thanks! -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From noreply at ubuntu.com Tue Apr 12 17:38:49 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 12 Apr 2011 17:38:49 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Tags=22_by_micahg?= Message-ID: <20110412173849.22710.59447@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by micahg: http://wiki.ubuntu.com/Bugs/Tags?action=diff&rev1=175&rev2=176 The comment on the change is: Add multiarch to official tag list ------------------------------------------------------------------------------ || [[https://launchpad.net/ubuntu/+bugs?field.tag=likely-dup|`likely-dup`]] || The bug is likely a duplicate of another bug but you can't find it. (Maybe an upstream bug too.) || || [[https://launchpad.net/ubuntu/+bugs?field.tag=manpage|`manpage`]] || This bug is about a package's manpage being incorrect. || || [[https://launchpad.net/ubuntu/+bugs?field.tag=metabug|`metabug`]] || This bug has a high probability of duplicate reports being filed. || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=multiarch|`multiarch`]] || This bug is due to an issue with the new [[http://wiki.debian.org/Multiarch/Tuples|multiarch triplet paths]], this can be build time, install time, or run time issues. || || [[https://launchpad.net/ubuntu/+bugs?field.tag=nautilus-desktop-icons|`nautilus-desktop-icons`]] || Bugs related to the Nautilus desktop, especially the alignment, display and grid of icons. || || [[https://launchpad.net/ubuntu/+bugs?orderby=-importance&field.status%3Alist=New&field.status%3Alist=Incomplete&field.status%3Alist=Invalid&field.status%3Alist=Won%27t+Fix&field.status%3Alist=Confirmed&field.status%3Alist=Triaged&field.status%3Alist=In+Progress&field.status%3Alist=Fix+Committed&field.status%3Alist=Fix+Released&field.tag=needs-devrelease-testing&search=Search|`needs-devrelease-testing`]] || A bug that existed in a previous release of Ubuntu and needs to be tested in the latest development release || || [[https://launchpad.net/ubuntu/+bugs?field.tag=needs-reassignment|`needs-reassignment`]] || A bug that was reported about the wrong package but the package maintainer isn't sure which package it belongs to || From noreply at ubuntu.com Tue Apr 12 17:41:15 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 12 Apr 2011 17:41:15 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Tags=22_by_vorlon?= Message-ID: <20110412174115.22512.34482@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by vorlon: http://wiki.ubuntu.com/Bugs/Tags?action=diff&rev1=176&rev2=177 ------------------------------------------------------------------------------ || [[https://launchpad.net/ubuntu/+bugs?field.tag=likely-dup|`likely-dup`]] || The bug is likely a duplicate of another bug but you can't find it. (Maybe an upstream bug too.) || || [[https://launchpad.net/ubuntu/+bugs?field.tag=manpage|`manpage`]] || This bug is about a package's manpage being incorrect. || || [[https://launchpad.net/ubuntu/+bugs?field.tag=metabug|`metabug`]] || This bug has a high probability of duplicate reports being filed. || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=multiarch|`multiarch`]] || This bug is due to an issue with the new [[http://wiki.debian.org/Multiarch/Tuples|multiarch triplet paths]], this can be build time, install time, or run time issues. || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=multiarch|`multiarch`]] || This bug is due to an issue with the new [[http://wiki.debian.org/Multiarch|multiarch triplet paths]], this can be build time, install time, or run time issues. || || [[https://launchpad.net/ubuntu/+bugs?field.tag=nautilus-desktop-icons|`nautilus-desktop-icons`]] || Bugs related to the Nautilus desktop, especially the alignment, display and grid of icons. || || [[https://launchpad.net/ubuntu/+bugs?orderby=-importance&field.status%3Alist=New&field.status%3Alist=Incomplete&field.status%3Alist=Invalid&field.status%3Alist=Won%27t+Fix&field.status%3Alist=Confirmed&field.status%3Alist=Triaged&field.status%3Alist=In+Progress&field.status%3Alist=Fix+Committed&field.status%3Alist=Fix+Released&field.tag=needs-devrelease-testing&search=Search|`needs-devrelease-testing`]] || A bug that existed in a previous release of Ubuntu and needs to be tested in the latest development release || || [[https://launchpad.net/ubuntu/+bugs?field.tag=needs-reassignment|`needs-reassignment`]] || A bug that was reported about the wrong package but the package maintainer isn't sure which package it belongs to || From noreply at ubuntu.com Tue Apr 12 18:48:02 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 12 Apr 2011 18:48:02 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Unity/FilingBugs=22_by_alexlauni?= Message-ID: <20110412184802.23943.62075@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by alexlauni: http://wiki.ubuntu.com/Unity/FilingBugs?action=diff&rev1=38&rev2=39 ------------------------------------------------------------------------------ || Patch needs author to sign Canonical Contributer agreement || Looks good but before we merge it we need you to sign the Canonical contributer agreement. It's a quick, but necessary step to getting your code into the tree. Luckily you only need to sign it once and it will apply to all other Canonical project contributions you may make in the future. http://www.canonical.com/contributors Make sure to CC David Barth when you send it in. || || || Blocked waiting for design decision || This bug is awaiting design feedback before progress can be made. Confirming that there is a question to be answered. Will be marked triaged when design gives a suitable direction forward. || Mark status as ''incomplete'', and tag ''needs-design'' until design gives feedback. || || Bug reported from clutter based Unity || This bug was reported against an old version of Unity. The new version of Unity is almost an entire rewrite based on very different technologies. Could you please check if this issue is present in the current version, and if it is reopen the bug to a NEW status. || Set the bug to WONTFIX, and let the user reopen it || - || Bugs that don't appear to be Unity related at all || The issue you're describing doesn't sound related to Unity. Could you log into a Gnome 2 session and see if this issue persists? || || + || Bugs that don't appear to be Unity related at all || The issue you're describing doesn't sound related to Unity. Could you log into a classic gnome session and see if this issue persists? || || || Crashers for which you'd like the user to get a stack trace || Could you please follow the instructions on https://wiki.ubuntu.com/Unity/FilingBugs#Getting%20a%20stack%20trace and attach unity.log to this bug report? || || = Bug Tags = From jean-baptiste at ubuntu.com Thu Apr 14 16:18:10 2011 From: jean-baptiste at ubuntu.com (Jean-Baptiste Lallement) Date: Thu, 14 Apr 2011 18:18:10 +0200 Subject: Announcing a Bonus Ubuntu Bug Day this week ! - April 15th 2011 Message-ID: <4DA71E42.7060202@ubuntu.com> Fellow Ubuntu Triagers! This week, there is a special Bonus Bug Day. I announce *drum roll please* - Natty ISO Testing Bugs ! * 100 New bugs need a hug * 51 Incomplete bugs need a status check * 100 Confirmed bugs need a review Natty Beta 2 candidates have been tested, many bugs have been reported and are waiting to be triaged to make a final release full of awesomeness. Bookmark it, add it to your calendars, turn over those egg-timers! * April 15th, 2011 * http://wiki.ubuntu.com/UbuntuBugDay/20110415 Are you looking for a way to start giving some love back to your adorable Ubuntu Project? Did you ever wonder what Triage is? Want to learn about that? This is a perfect time!, Everybody can help in a Bug Day! open your IRC Client and go to #ubuntu-bugs (FreeNode) the BugSquad will be happy to help you to start contributing! Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! We are always looking for new tasks or ideas for the Bug Days, if you have one add it to the Planning page https://wiki.ubuntu.com/UbuntuBugDay/Planning If you're new to all this, head to http://wiki.ubuntu.com/Bugs Have a nice day, -- Jean-Baptiste irc: jibel From RedSingularity at gmx.com Thu Apr 14 22:50:11 2011 From: RedSingularity at gmx.com (RedSingularity) Date: Thu, 14 Apr 2011 18:50:11 -0400 Subject: Additional "status" option Message-ID: <4DA77A23.2000506@gmx.com> Hey everyone. While working a bug recently I thought to myself, Why not have a status item that lets people know that a triager is working on the bug. I know when I am looking for bugs to triage I always look for the "New" mark. That, to me, means that no one has started to triage it yet and thats a sign that I can go ahead and have a look at it. I know we have a "In Progress" option but I think thats more for developer use if I am correct. As of now when working a bug I use the "Incomplete" sign to show that it is being triaged by someone (me). I think this "Incomplete" mark may aggravate new reporters though, and is incorrect in some cases. For example, many times the reporter has given all the required info, and I am in the process of triaging it. As you can see the "Incomplete" mark, in this case, seems invalid since the report is actually complete. I guess to end my rant and sum up, I think a mark along the lines of "Work in Progress" in the status area would be helpful to triagers, and a "reassuring" mark for new users reporting bugs. This way triagers will know that the bug is being handled by someone and the end user feels better that the bug is indeed being worked on instead of being "Incomplete". Thanks for considering, --Tim (RedSingularity) From micahg at ubuntu.com Fri Apr 15 03:42:46 2011 From: micahg at ubuntu.com (Micah Gersten) Date: Thu, 14 Apr 2011 22:42:46 -0500 Subject: Additional "status" option In-Reply-To: <4DA77A23.2000506@gmx.com> References: <4DA77A23.2000506@gmx.com> Message-ID: <4DA7BEB6.2030008@ubuntu.com> On 04/14/2011 05:50 PM, RedSingularity wrote: > Hey everyone. While working a bug recently I thought to myself, Why > not have a status item that lets people know that a triager is working > on the bug. I know when I am looking for bugs to triage I always look > for the "New" mark. That, to me, means that no one has started to > triage it yet and thats a sign that I can go ahead and have a look at > it. I know we have a "In Progress" option but I think thats more for > developer use if I am correct. As of now when working a bug I use the > "Incomplete" sign to show that it is being triaged by someone (me). I > think this "Incomplete" mark may aggravate new reporters though, and > is incorrect in some cases. For example, many times the reporter has > given all the required info, and I am in the process of triaging it. > As you can see the "Incomplete" mark, in this case, seems invalid > since the report is actually complete. > > I guess to end my rant and sum up, I think a mark along the lines of > "Work in Progress" in the status area would be helpful to triagers, > and a "reassuring" mark for new users reporting bugs. This way > triagers will know that the bug is being handled by someone and the > end user feels better that the bug is indeed being worked on instead > of being "Incomplete". > > Thanks for considering, > > --Tim (RedSingularity) > With over 90k bugs open and about 400-500 active triagers/developers, I don't think this happens that often. However, if you find a specific contributor colliding with you, perhaps coordinating in IRC would be a way to work around this. Incomplete is definitely not appropriate for 'Triage in Progress'. Micah From brian at ubuntu.com Fri Apr 15 16:56:41 2011 From: brian at ubuntu.com (Brian Murray) Date: Fri, 15 Apr 2011 09:56:41 -0700 Subject: Additional "status" option In-Reply-To: <4DA77A23.2000506@gmx.com> References: <4DA77A23.2000506@gmx.com> Message-ID: <20110415165641.GA2525@murraytwins.com> On Thu, Apr 14, 2011 at 06:50:11PM -0400, RedSingularity wrote: > Hey everyone. While working a bug recently I thought to myself, Why > not have a status item that lets people know that a triager is > working on the bug. I know when I am looking for bugs to triage I > always look for the "New" mark. That, to me, means that no one has > started to triage it yet and thats a sign that I can go ahead and > have a look at it. I know we have a "In Progress" option but I > think thats more for developer use if I am correct. Yes, that is correct. > As of now when working a bug I use the "Incomplete" sign to show that > it is being triaged by someone (me). I think this "Incomplete" mark > may aggravate new reporters though, and is incorrect in some cases. > For example, many times the reporter has given all the required info, > and I am in the process of triaging it. As you can see the > "Incomplete" mark, in this case, seems invalid since the report is > actually complete. What is happening when you are in the process of triaging it and how long does it take? I'm curious about how long the "Work in Progress" status would be used. Additionally, a danger with using Incomplete is that the bug is then eligible for expiration. > I guess to end my rant and sum up, I think a mark along the lines of > "Work in Progress" in the status area would be helpful to triagers, > and a "reassuring" mark for new users reporting bugs. This way > triagers will know that the bug is being handled by someone and the > end user feels better that the bug is indeed being worked on instead > of being "Incomplete". A comment along the lines of "I'm working on testing this with X and Y" would convey the same information and prevent other issues. -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From RedSingularity at gmx.com Fri Apr 15 18:00:56 2011 From: RedSingularity at gmx.com (RedSingularity) Date: Fri, 15 Apr 2011 14:00:56 -0400 Subject: Additional "status" option In-Reply-To: <20110415165641.GA2525@murraytwins.com> References: <4DA77A23.2000506@gmx.com> <20110415165641.GA2525@murraytwins.com> Message-ID: <4DA887D8.10308@gmx.com> On 04/15/2011 12:56 PM, Brian Murray wrote: > On Thu, Apr 14, 2011 at 06:50:11PM -0400, RedSingularity wrote: >> Hey everyone. While working a bug recently I thought to myself, Why >> not have a status item that lets people know that a triager is >> working on the bug. I know when I am looking for bugs to triage I >> always look for the "New" mark. That, to me, means that no one has >> started to triage it yet and thats a sign that I can go ahead and >> have a look at it. I know we have a "In Progress" option but I >> think thats more for developer use if I am correct. > Yes, that is correct. > >> As of now when working a bug I use the "Incomplete" sign to show that >> it is being triaged by someone (me). I think this "Incomplete" mark >> may aggravate new reporters though, and is incorrect in some cases. >> For example, many times the reporter has given all the required info, >> and I am in the process of triaging it. As you can see the >> "Incomplete" mark, in this case, seems invalid since the report is >> actually complete. > What is happening when you are in the process of triaging it and how > long does it take? I'm curious about how long the "Work in Progress" > status would be used. Nothing in particular. For example sometimes I ask the user to try different things and report back with the result. This may take a few hours/days depending on how much I ,or the reporter, are online. > Additionally, a danger with using Incomplete is that the bug is then > eligible for expiration. Very true. >> I guess to end my rant and sum up, I think a mark along the lines of >> "Work in Progress" in the status area would be helpful to triagers, >> and a "reassuring" mark for new users reporting bugs. This way >> triagers will know that the bug is being handled by someone and the >> end user feels better that the bug is indeed being worked on instead >> of being "Incomplete". > A comment along the lines of "I'm working on testing this with X and Y" > would convey the same information and prevent other issues. I do that from time to time. Unfortunately a triager cant see this comment while 'sifting' through the bug list. I, on occasion, have been 'sifting' through reports marked "New" and have opened them only to find that someone is already in the process of triaging it. But since it had that status mark of "New" I figured it may be untouched. Obviously this is no big problem whatsoever, but more of an idea. I just though I would mention it :) > -- > Brian Murray > Ubuntu Bug Master From arno at wagner.name Fri Apr 15 16:56:41 2011 From: arno at wagner.name (Arno Wagner) Date: Fri, 15 Apr 2011 18:56:41 +0200 Subject: Ubuntu installer kills LUKS partitions without warning Message-ID: <20110415165641.GA6058@tansi.org> Hi, first, I don't have Ubuntu and I don't plan on using it. As I did not find another way that allows me to report a serious issue without subscribing to something, I use this venue. Please forward this to the Ubuntu installer development team. The dm-crypt mailing list (archive here: http://dir.gmane.org/gmane.linux.kernel.device-mapper.dm-crypt) has had several reports that the Ubuntu installer creates new LUKS partitions (encrypted partitions) on top of exisiting ones without giving adequate warning and at the same time giving the impression that the existing LUKS partition would be activated. The rather clear warning and verification question asked by the cryptsetup tool seems to get disabled with the "--batch-mode" option. This causes irreversible loss of all data! Nothing (in the cryptographically strong sense) can be done to get the data back! Checking for an existing LUKS partition is easy, it has the magic string 'L','U','K','S, 0xBA, 0xBe at the beginning. It seems this is not checked for, or no additional warning or only inadequate additional warning is given if a pre-exisiting LUKS partition is about to be permanently and irretrivably erased. Please fix the installer ASAP and if you need help doing it right, _ask_! We will be happy to help. Regards, Arno Wagner Maintainer cryptsetup FAQ -- Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno at wagner.name GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F ---- Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans If it's in the news, don't worry about it. The very definition of "news" is "something that hardly ever happens." -- Bruce Schneier From vish at ubuntu.com Fri Apr 15 19:50:05 2011 From: vish at ubuntu.com (Vishnoo) Date: Sat, 16 Apr 2011 01:20:05 +0530 Subject: Additional "status" option In-Reply-To: <4DA887D8.10308@gmx.com> References: <4DA77A23.2000506@gmx.com> <20110415165641.GA2525@murraytwins.com> <4DA887D8.10308@gmx.com> Message-ID: <1302897005.1051.109.camel@Aspire-5670> On Fri, 2011-04-15 at 14:00 -0400, RedSingularity wrote: > On 04/15/2011 12:56 PM, Brian Murray wrote: > > On Thu, Apr 14, 2011 at 06:50:11PM -0400, RedSingularity wrote: > >> Hey everyone. While working a bug recently I thought to myself, Why > >> not have a status item that lets people know that a triager is > >> working on the bug. I know when I am looking for bugs to triage I > >> always look for the "New" mark. That, to me, means that no one has > >> started to triage it yet and thats a sign that I can go ahead and > >> have a look at it. I know we have a "In Progress" option but I > >> think thats more for developer use if I am correct. > > Yes, that is correct. > > > >> As of now when working a bug I use the "Incomplete" sign to show that > >> it is being triaged by someone (me). I think this "Incomplete" mark > >> may aggravate new reporters though, and is incorrect in some cases. > >> For example, many times the reporter has given all the required info, > >> and I am in the process of triaging it. As you can see the > >> "Incomplete" mark, in this case, seems invalid since the report is > >> actually complete. > > What is happening when you are in the process of triaging it and how > > long does it take? I'm curious about how long the "Work in Progress" > > status would be used. > Nothing in particular. For example sometimes I ask the user to try different > things and report back with the result. This may take a few hours/days depending > on how much I ,or the reporter, are online. > If you have asked a question, or asked to test something, it needs to be marked "incomplete". Incomplete since you are waiting for some info from the reporter. If your goal to not step into another bug triager's work, this is where the lp extension is handy.. For people in bugsquad or bug control there will be an icon displayed next to their name. > > Additionally, a danger with using Incomplete is that the bug is then > > eligible for expiration. > Very true. > This is not a problem if the user has replied. Only incomplete bugs without replies after the status was marked incomplete expire. -- Cheers, Vish From RedSingularity at gmx.com Fri Apr 15 20:37:28 2011 From: RedSingularity at gmx.com (RedSingularity) Date: Fri, 15 Apr 2011 16:37:28 -0400 Subject: Additional "status" option In-Reply-To: <1302897005.1051.109.camel@Aspire-5670> References: <4DA77A23.2000506@gmx.com> <20110415165641.GA2525@murraytwins.com> <4DA887D8.10308@gmx.com> <1302897005.1051.109.camel@Aspire-5670> Message-ID: <4DA8AC88.1060404@gmx.com> On 04/15/2011 03:50 PM, Vishnoo wrote: > On Fri, 2011-04-15 at 14:00 -0400, RedSingularity wrote: >> On 04/15/2011 12:56 PM, Brian Murray wrote: >>> On Thu, Apr 14, 2011 at 06:50:11PM -0400, RedSingularity wrote: >>>> Hey everyone. While working a bug recently I thought to myself, Why >>>> not have a status item that lets people know that a triager is >>>> working on the bug. I know when I am looking for bugs to triage I >>>> always look for the "New" mark. That, to me, means that no one has >>>> started to triage it yet and thats a sign that I can go ahead and >>>> have a look at it. I know we have a "In Progress" option but I >>>> think thats more for developer use if I am correct. >>> Yes, that is correct. >>> >>>> As of now when working a bug I use the "Incomplete" sign to show that >>>> it is being triaged by someone (me). I think this "Incomplete" mark >>>> may aggravate new reporters though, and is incorrect in some cases. >>>> For example, many times the reporter has given all the required info, >>>> and I am in the process of triaging it. As you can see the >>>> "Incomplete" mark, in this case, seems invalid since the report is >>>> actually complete. >>> What is happening when you are in the process of triaging it and how >>> long does it take? I'm curious about how long the "Work in Progress" >>> status would be used. >> Nothing in particular. For example sometimes I ask the user to try different >> things and report back with the result. This may take a few hours/days depending >> on how much I ,or the reporter, are online. >> > > If you have asked a question, or asked to test something, it needs to be > marked "incomplete". Incomplete since you are waiting for some info from > the reporter. > > If your goal to not step into another bug triager's work, this is where > the lp extension is handy.. > For people in bugsquad or bug control there will be an icon displayed > next to their name. Yeah the lp extension is VERY handy indeed. Well I guess this would answer my question then. Incomplete would be the correct status since I am in fact waiting for more info from the user. > >>> Additionally, a danger with using Incomplete is that the bug is then >>> eligible for expiration. >> Very true. >> > This is not a problem if the user has replied. Only incomplete bugs > without replies after the status was marked incomplete expire. > > Thanks for the responses! Much appreciated!! :-) -Tim From noreply at ubuntu.com Sat Apr 16 14:31:03 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Sat, 16 Apr 2011 14:31:03 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingKernelBoot=22_by_tormod?= =?utf-8?q?volden?= Message-ID: <20110416143103.26719.74218@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by tormodvolden: http://wiki.ubuntu.com/DebuggingKernelBoot?action=diff&rev1=12&rev2=13 The comment on the change is: link to vt.handoff explanation ------------------------------------------------------------------------------ Additionally, being able to extract log files from the system would be helpful. Once dropped into an initramfs shell, you can type '''httpd'''. You should then be able to point a web browser to the IP address of the system and view the contents of /var/log . There is another initramfs boot parameter which can purposely drop you into the initramfs shell during different stages of the initial boot sequence. The parameter is '''break=[option]''' where option can be: top, modules, premount, mount, bottom, or init. The default is premount if no options are specified. More information about the break= parameters can be found in "/usr/share/initramfs-tools/init" on your Ubuntu system. + + == Links == + * [[http://askubuntu.com/questions/32999/what-is-vt-handoff-7-parameter-in-grub-cfg|vt.handoff]] explained ---- CategoryBugSquad CategoryDebugging From noreply at ubuntu.com Sat Apr 16 16:06:53 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Sat, 16 Apr 2011 16:06:53 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Importance=22_by_amoog?= Message-ID: <20110416160653.31008.78700@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by amoog: http://wiki.ubuntu.com/Bugs/Importance?action=diff&rev1=28&rev2=29 ------------------------------------------------------------------------------ * A bug that has an easy [[http://www.merriam-webster.com/dictionary/work-around|work-around]] * Ones that affect unusual configurations or uncommon hardware * A bug that has a moderate impact on a non-core application - * A cosmetic/usability issue that does not limit the functionality of an application + * A cosmetic/usability issue that does not limit the functionality of a non-core application * '''Medium''': most bugs are of medium importance, examples are: * A bug that has a moderate impact on a core application. * A bug that has a severe impact on a non-core application. * A bug which impacts accessibility of a non-core application. + * A usability issue that does not limit the functionality of a core application. * A problem with a non-essential hardware component (network card, camera, webcam, music player, sound card, power management feature, printer, etc.) * '''High''': A bug which fulfills one of the following criteria: * Has a severe impact on a small portion of Ubuntu users (estimated) From ubuntu at treblig.org Sat Apr 16 20:06:02 2011 From: ubuntu at treblig.org (Dr. David Alan Gilbert) Date: Sat, 16 Apr 2011 21:06:02 +0100 Subject: Ubuntu installer kills LUKS partitions without warning In-Reply-To: <20110415165641.GA6058@tansi.org> References: <20110415165641.GA6058@tansi.org> Message-ID: <20110416200602.GA18585@gallifrey> * Arno Wagner (arno at wagner.name) wrote: > Hi, > > first, I don't have Ubuntu and I don't plan on using it. > As I did not find another way that allows me to report > a serious issue without subscribing to something, I use > this venue. > > > Please forward this to the Ubuntu installer development team. > > > The dm-crypt mailing list (archive here: > http://dir.gmane.org/gmane.linux.kernel.device-mapper.dm-crypt) > has had several reports that the Ubuntu installer creates > new LUKS partitions (encrypted partitions) on top of exisiting > ones without giving adequate warning and at the same time > giving the impression that the existing LUKS partition would be > activated. The rather clear warning and verification question > asked by the cryptsetup tool seems to get disabled with the > "--batch-mode" option. > > This causes irreversible loss of all data! Nothing > (in the cryptographically strong sense) can be done > to get the data back! The bug below seems to be the equivalent of what is being described on the list: https://bugs.launchpad.net/ubuntu/+source/partman-crypto/+bug/194946 (from 2008) The good news is it's marked as high priority - the bad news is it's been high priority for over a year. Now that is a report for the alternate installer, and you generally need the alternate installer for doing LUKS stuff; what I don't know (not tried) is what happens if you try the standard installer on a machine with a LUKS partition. My reading of the thread on the dm-crypt list was that it was people using the alternate installer to install to existing LUKS partitions. > Checking for an existing LUKS partition is easy, > it has the magic string 'L','U','K','S, 0xBA, 0xBe > at the beginning. It seems this is not checked for, > or no additional warning or only inadequate additional > warning is given if a pre-exisiting LUKS partition > is about to be permanently and irretrivably erased. > > Please fix the installer ASAP and if you need help doing > it right, _ask_! We will be happy to help. Dave -- -----Open up your eyes, open up your mind, open up your code ------- / Dr. David Alan Gilbert | Running GNU/Linux | Happy \ \ gro.gilbert @ treblig.org | | In Hex / \ _________________________|_____ http://www.treblig.org |_______/ From brian at ubuntu.com Sat Apr 16 21:23:02 2011 From: brian at ubuntu.com (Brian Murray) Date: Sat, 16 Apr 2011 14:23:02 -0700 Subject: Ubuntu installer kills LUKS partitions without warning In-Reply-To: <20110416200602.GA18585@gallifrey> References: <20110415165641.GA6058@tansi.org> <20110416200602.GA18585@gallifrey> Message-ID: <20110416212302.GE2525@murraytwins.com> On Sat, Apr 16, 2011 at 09:06:02PM +0100, Dr. David Alan Gilbert wrote: > * Arno Wagner (arno at wagner.name) wrote: > > Hi, > > > > first, I don't have Ubuntu and I don't plan on using it. > > As I did not find another way that allows me to report > > a serious issue without subscribing to something, I use > > this venue. > > > > > > Please forward this to the Ubuntu installer development team. > > > > > > The dm-crypt mailing list (archive here: > > http://dir.gmane.org/gmane.linux.kernel.device-mapper.dm-crypt) > > has had several reports that the Ubuntu installer creates > > new LUKS partitions (encrypted partitions) on top of exisiting > > ones without giving adequate warning and at the same time > > giving the impression that the existing LUKS partition would be > > activated. The rather clear warning and verification question > > asked by the cryptsetup tool seems to get disabled with the > > "--batch-mode" option. > > > > This causes irreversible loss of all data! Nothing > > (in the cryptographically strong sense) can be done > > to get the data back! > > The bug below seems to be the equivalent of what is being > described on the list: > > https://bugs.launchpad.net/ubuntu/+source/partman-crypto/+bug/194946 > (from 2008) > > The good news is it's marked as high priority - the bad news > is it's been high priority for over a year. When I looked into this yesterday I found a different bug, http://launchpad.net/bugs/420080, which I've taken steps to ensure that it gets looked at and documented for 11.04. Thanks, -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From micahg at ubuntu.com Sun Apr 17 04:54:38 2011 From: micahg at ubuntu.com (Micah Gersten) Date: Sat, 16 Apr 2011 23:54:38 -0500 Subject: [Ubuntu Wiki] Update of "Bugs/Importance" by amoog In-Reply-To: <20110416160653.31008.78700@jostaberry.canonical.com> References: <20110416160653.31008.78700@jostaberry.canonical.com> Message-ID: <4DAA728E.5000803@ubuntu.com> On 04/16/2011 11:06 AM, Ubuntu Wiki wrote: > Dear Wiki user, > > You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. > > The following page has been changed by amoog: > http://wiki.ubuntu.com/Bugs/Importance?action=diff&rev1=28&rev2=29 > > ------------------------------------------------------------------------------ > * A bug that has an easy [[http://www.merriam-webster.com/dictionary/work-around|work-around]] > * Ones that affect unusual configurations or uncommon hardware > * A bug that has a moderate impact on a non-core application > - * A cosmetic/usability issue that does not limit the functionality of an application > + * A cosmetic/usability issue that does not limit the functionality of a non-core application > * '''Medium''': most bugs are of medium importance, examples are: > * A bug that has a moderate impact on a core application. > * A bug that has a severe impact on a non-core application. > * A bug which impacts accessibility of a non-core application. > + * A usability issue that does not limit the functionality of a core application. > * A problem with a non-essential hardware component (network card, camera, webcam, music player, sound card, power management feature, printer, etc.) > * '''High''': A bug which fulfills one of the following criteria: > * Has a severe impact on a small portion of Ubuntu users (estimated) Do we want to make a distinction between core and non-core for cosmetic bugs? Micah From vish at ubuntu.com Sun Apr 17 05:48:06 2011 From: vish at ubuntu.com (Vishnoo) Date: Sun, 17 Apr 2011 11:18:06 +0530 Subject: [Ubuntu Wiki] Update of "Bugs/Importance" by amoog In-Reply-To: <4DAA728E.5000803@ubuntu.com> References: <20110416160653.31008.78700@jostaberry.canonical.com> <4DAA728E.5000803@ubuntu.com> Message-ID: <1303019286.9449.2.camel@Aspire-5670> On Sat, 2011-04-16 at 23:54 -0500, Micah Gersten wrote: > On 04/16/2011 11:06 AM, Ubuntu Wiki wrote: > > Dear Wiki user, > > > > You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. > > > > The following page has been changed by amoog: > > http://wiki.ubuntu.com/Bugs/Importance?action=diff&rev1=28&rev2=29 > > > > ------------------------------------------------------------------------------ > > * A bug that has an easy [[http://www.merriam-webster.com/dictionary/work-around|work-around]] > > * Ones that affect unusual configurations or uncommon hardware > > * A bug that has a moderate impact on a non-core application > > - * A cosmetic/usability issue that does not limit the functionality of an application > > + * A cosmetic/usability issue that does not limit the functionality of a non-core application > > * '''Medium''': most bugs are of medium importance, examples are: > > * A bug that has a moderate impact on a core application. > > * A bug that has a severe impact on a non-core application. > > * A bug which impacts accessibility of a non-core application. > > + * A usability issue that does not limit the functionality of a core application. > > * A problem with a non-essential hardware component (network card, camera, webcam, music player, sound card, power management feature, printer, etc.) > > * '''High''': A bug which fulfills one of the following criteria: > > * Has a severe impact on a small portion of Ubuntu users (estimated) > > Do we want to make a distinction between core and non-core for cosmetic > bugs? > > Micah > IMO, not necessary. That addition kinda seems to make the importance guidelines a bit more complex for a new triager. -- Cheers, Vish From noname420 at gmail.com Sun Apr 17 13:14:42 2011 From: noname420 at gmail.com (IKT) Date: Sun, 17 Apr 2011 22:44:42 +0930 Subject: bug days is dead? Message-ID: The amount of activity surrounding the bug day has been quite low, or is it just that the wiki page isn't being updated to reflect people working on bugs? - ikt -------------- next part -------------- An HTML attachment was scrubbed... URL: From hggdh2 at ubuntu.com Sun Apr 17 16:34:06 2011 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Sun, 17 Apr 2011 11:34:06 -0500 Subject: [Ubuntu Wiki] Update of "Bugs/Importance" by amoog In-Reply-To: <4DAA728E.5000803@ubuntu.com> References: <20110416160653.31008.78700@jostaberry.canonical.com> <4DAA728E.5000803@ubuntu.com> Message-ID: <4DAB167E.20802@ubuntu.com> On 04/16/2011 11:54 PM, Micah Gersten wrote: > > Do we want to make a distinction between core and non-core for cosmetic > bugs? I am 60/40 to yes, but... Perhaps it would be better to separate cosmetic from usability -- I do not find a real need to separate core and non-core for cosmetic, but _usability_ is a different issue. And, the more I think about it, the more is does not make sense to bundle cosmetic and usability bugs together. ..C.. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 900 bytes Desc: OpenPGP digital signature URL: From arno at wagner.name Sun Apr 17 02:11:12 2011 From: arno at wagner.name (Arno Wagner) Date: Sun, 17 Apr 2011 04:11:12 +0200 Subject: Ubuntu installer kills LUKS partitions without warning In-Reply-To: <20110416212302.GE2525@murraytwins.com> References: <20110415165641.GA6058@tansi.org> <20110416200602.GA18585@gallifrey> <20110416212302.GE2525@murraytwins.com> Message-ID: <20110417021112.GB11053@tansi.org> On Sat, Apr 16, 2011 at 02:23:02PM -0700, Brian Murray wrote: > On Sat, Apr 16, 2011 at 09:06:02PM +0100, Dr. David Alan Gilbert wrote: > > * Arno Wagner (arno at wagner.name) wrote: > > > Hi, > > > > > > first, I don't have Ubuntu and I don't plan on using it. > > > As I did not find another way that allows me to report > > > a serious issue without subscribing to something, I use > > > this venue. > > > > > > > > > Please forward this to the Ubuntu installer development team. > > > > > > > > > The dm-crypt mailing list (archive here: > > > http://dir.gmane.org/gmane.linux.kernel.device-mapper.dm-crypt) > > > has had several reports that the Ubuntu installer creates > > > new LUKS partitions (encrypted partitions) on top of exisiting > > > ones without giving adequate warning and at the same time > > > giving the impression that the existing LUKS partition would be > > > activated. The rather clear warning and verification question > > > asked by the cryptsetup tool seems to get disabled with the > > > "--batch-mode" option. > > > > > > This causes irreversible loss of all data! Nothing > > > (in the cryptographically strong sense) can be done > > > to get the data back! > > > > The bug below seems to be the equivalent of what is being > > described on the list: > > > > https://bugs.launchpad.net/ubuntu/+source/partman-crypto/+bug/194946 > > (from 2008) > > > > The good news is it's marked as high priority - the bad news > > is it's been high priority for over a year. > > When I looked into this yesterday I found a different bug, > http://launchpad.net/bugs/420080, which I've taken steps to ensure that > it gets looked at and documented for 11.04. > > Thanks, > -- > Brian Murray > Ubuntu Bug Master Thanks, that seems to be it. Arno -- Arno Wagner, Dr. sc. techn., Dipl. Inform., CISSP -- Email: arno at wagner.name GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F ---- Cuddly UI's are the manifestation of wishful thinking. -- Dylan Evans If it's in the news, don't worry about it. The very definition of "news" is "something that hardly ever happens." -- Bruce Schneier -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 190 bytes Desc: Digital signature URL: From micahg at ubuntu.com Sun Apr 17 20:28:10 2011 From: micahg at ubuntu.com (Micah Gersten) Date: Sun, 17 Apr 2011 15:28:10 -0500 Subject: [Ubuntu Wiki] Update of "Bugs/Importance" by amoog In-Reply-To: <4DAB167E.20802@ubuntu.com> References: <20110416160653.31008.78700@jostaberry.canonical.com> <4DAA728E.5000803@ubuntu.com> <4DAB167E.20802@ubuntu.com> Message-ID: <4DAB4D5A.4040507@ubuntu.com> On 04/17/2011 11:34 AM, C de-Avillez wrote: > On 04/16/2011 11:54 PM, Micah Gersten wrote: >> >> Do we want to make a distinction between core and non-core for cosmetic >> bugs? > > I am 60/40 to yes, but... > > Perhaps it would be better to separate cosmetic from usability -- I > do not find a real need to separate core and non-core for cosmetic, > but _usability_ is a different issue. And, the more I think about > it, the more is does not make sense to bundle cosmetic and usability > bugs together. > > ..C.. I'll buy that :) +1 Micah From brian at ubuntu.com Mon Apr 18 15:42:34 2011 From: brian at ubuntu.com (Brian Murray) Date: Mon, 18 Apr 2011 08:42:34 -0700 Subject: Ubuntu installer kills LUKS partitions without warning In-Reply-To: <20110417021112.GB11053@tansi.org> References: <20110415165641.GA6058@tansi.org> <20110416200602.GA18585@gallifrey> <20110416212302.GE2525@murraytwins.com> <20110417021112.GB11053@tansi.org> Message-ID: <20110418154234.GK2525@murraytwins.com> On Sun, Apr 17, 2011 at 04:11:12AM +0200, Arno Wagner wrote: > On Sat, Apr 16, 2011 at 02:23:02PM -0700, Brian Murray wrote: > > On Sat, Apr 16, 2011 at 09:06:02PM +0100, Dr. David Alan Gilbert wrote: > > > * Arno Wagner (arno at wagner.name) wrote: > > > > Hi, > > > > > > > > first, I don't have Ubuntu and I don't plan on using it. > > > > As I did not find another way that allows me to report > > > > a serious issue without subscribing to something, I use > > > > this venue. > > > > > > > > > > > > Please forward this to the Ubuntu installer development team. > > > > > > > > > > > > The dm-crypt mailing list (archive here: > > > > http://dir.gmane.org/gmane.linux.kernel.device-mapper.dm-crypt) > > > > has had several reports that the Ubuntu installer creates > > > > new LUKS partitions (encrypted partitions) on top of exisiting > > > > ones without giving adequate warning and at the same time > > > > giving the impression that the existing LUKS partition would be > > > > activated. The rather clear warning and verification question > > > > asked by the cryptsetup tool seems to get disabled with the > > > > "--batch-mode" option. > > > > > > > > This causes irreversible loss of all data! Nothing > > > > (in the cryptographically strong sense) can be done > > > > to get the data back! > > > > > > The bug below seems to be the equivalent of what is being > > > described on the list: > > > > > > https://bugs.launchpad.net/ubuntu/+source/partman-crypto/+bug/194946 > > > (from 2008) > > > > > > The good news is it's marked as high priority - the bad news > > > is it's been high priority for over a year. > > > > When I looked into this yesterday I found a different bug, > > http://launchpad.net/bugs/420080, which I've taken steps to ensure that > > it gets looked at and documented for 11.04. > > > > Thanks, > > -- > > Brian Murray > > Ubuntu Bug Master > > > Thanks, that seems to be it. Thank you for bringing it to your attention! -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From hggdh2 at ubuntu.com Thu Apr 21 00:57:00 2011 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Wed, 20 Apr 2011 19:57:00 -0500 Subject: What we look for on Ubuntu-BugControl Message-ID: <4DAF80DC.6030009@ubuntu.com> I originally wrote the following text last year [1], piggybacking on a response to a BugControl application. Perhaps it would be better that this is sent completely separate, so that it will be as generic as possible (and not seen as a critique to a specific application). [1] https://lists.launchpad.net/ubuntu-bugcontrol/msg02249.html -x-x-x-x-x-x-x- *WHAT WE ARE LOOKING FOR on Ubuntu BugControl* First of all, given a problem, we must identify the root cause(s) from the description and supporting documentation (and keep in mind that correlation is not causation). For example, "I cannot run Ubuntu" states a *consequence* -- we must now go and try to find out what *causes* this failure. Triaging deals with this process. After root causes are identified, one can then go and develop a fix (or invalidate the problem, as needed)-- but this is problem _resolution_, not problem triaging! We are trying to verify your knowledge of triaging (and, specifically, your knowledge of the Ubuntu processes for bug triaging). This involves a series of things: * how you interact with the original poster (OP): being courteous is as important as being knowledgeable. Even more, courtesy is not an inbred trait, but must be exercised continuously. * explaining why some action is needed and how to get it done. We should never assume (unless we know the OP) that the OP understands Ubuntu, Linux, etc. * explaining the reason of a status change. We should not blindly change the status (or importance) of a bug. Always add a sentence, or comment, on the reason. * your problem identification process. How -- and why! -- you identified the basic issue, your backtracks ("I am sorry, but indeed my previous explanation/view/analysis in comment xx was wrong because of whadda gimpa blahblah"), etc. * keep in mind that others will (eventually) read the bug and its comments, trying to figure out what to do. Please make their life easier. Explain. Comment. Point out examples. By giving us 5 bugs you triaged, you provide us with a chance to glimpse your work on this area. We are not required to search for your contributions, although we *can* do so. *HAH! SO YOU _CAN_ SEARCH. WHY DON'T YOU, AND FREE ME FROM DOING IT?* Well. If you cannot be bothered with finding five bugs to show your work, why should *we* be bothered to search for it? Yes, we understand you are most probably busy, perhaps within the Ubuntu community, perhaps without. But, most of the times, so are we. You spend some time selecting your five examples of bug triaging, and we spend some time reviewing them. You can *choose* which ones to show off, and we will accept them. *WHY DO I NEED TO PROVIDE MY VIEW OF IMPORTANCE?* The most important difference between a triager-at-large and a bug-controller is the ability to set the bug's importance. Yes, there are other differences, but I personally do not consider them as critical. As such, it stands to reason that we want to know your view on what would be the importance. You may even disagree with the one set in the bug, this is acceptable. But you *must* give us your view on the importance, and you *must* explain why. *SO YOU ARE ACTUALLY AN ELITIST* No, we are not. Er, yes, perhaps we are. Both apply. As a bug-controller you will have more access and control over what bugs are looked at, and worked on. This has been discussed many times, and is still being discussed. What we are doing here is our consensus, as of now. Again, it stands to reason that we should be a bit more selective. And, after all, we are not requiring too much: * sign the Ubuntu Code of Conduct -- this is basic. Being nice *is* a requirement, and I personally fully support it. This is one of the major differences between Ubuntu and other projects -- we strive to be nice to others. * understand the triaging flow for Ubuntu -- note that this is for _Ubuntu_. Eventually, one will also work with upstreams, and knowing their bug flow will then apply. * privacy considerations -- every so often a bug will have private (or potentially private) data. One should be careful, and respect the OP's privacy. * five bugs showing one's understanding of the three bullets above. I posit this is not unreasonable. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 900 bytes Desc: OpenPGP digital signature URL: From noreply at ubuntu.com Wed Apr 20 19:20:02 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 20 Apr 2011 19:20:02 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingGwibber=22_by_kamus?= Message-ID: <20110420192002.29743.92037@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by kamus: http://wiki.ubuntu.com/DebuggingGwibber?action=diff&rev1=9&rev2=10 ------------------------------------------------------------------------------ gconftool-2 --recursive-unset /apps/gwibber + '''Fix your corrupted database''' + + $ cd ~/.config/gwibber <
> + $ sqlite3 gwibber.sqlite ".dump" > dump <
> + $ mv gwibber.sqlite gwibber.sqlite.backup <
> + $ cat dump | sqlite3 gwibber.sqlite <
> ---- CategoryBugSquad From micahg at ubuntu.com Thu Apr 21 23:04:04 2011 From: micahg at ubuntu.com (Micah Gersten) Date: Thu, 21 Apr 2011 18:04:04 -0500 Subject: Ubuntu Bugsquad Meeting Times & #ubuntu-meeting Message-ID: <4DB0B7E4.5040005@ubuntu.com> So, I did a little research into available times in #ubuntu-meeting, here's what's available: Tue 19:00 UTC Wed 16:00-18:00, 19:00 UTC Thu 16:00-18:00, 19:00 UTC Micah From noreply at ubuntu.com Fri Apr 22 21:38:26 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Fri, 22 Apr 2011 21:38:26 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Unity/FilingBugs=22_by_alexlauni?= Message-ID: <20110422213826.20158.55979@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by alexlauni: http://wiki.ubuntu.com/Unity/FilingBugs?action=diff&rev1=39&rev2=40 ------------------------------------------------------------------------------ In extreme circumstances, we may ask you to use the crashhandler plugin from [[http://git.compiz.org/compiz/plugins/crashhandler|git]] and enable that in ccsm. + If you are experiencing a freeze, but can still use Ctrl-Alt-F1 to get to TTY1, you can use gdb to connect to the running compiz process, and get a backtrace. This will be invaluable information for us to debug your issue. To attach to the running process switch to TTY1, and follow these instructions. + {{{ + $ sudo gdb compiz `pgrep compiz` + + (gdb) set logging file unity.log + (gdb) set logging on + (gdb) bt full + + [ then CTRL-D or re-run compiz to continue working ] + + (gdb) run + }}} = Triaging instructions = == Standard Operating Procedures == From micahg at ubuntu.com Thu Apr 28 02:02:36 2011 From: micahg at ubuntu.com (Micah Gersten) Date: Wed, 27 Apr 2011 21:02:36 -0500 Subject: Ubuntu Bugsquad Meeting Times & #ubuntu-meeting In-Reply-To: <4DB0B7E4.5040005@ubuntu.com> References: <4DB0B7E4.5040005@ubuntu.com> Message-ID: <4DB8CABC.8050806@ubuntu.com> On 04/21/2011 06:04 PM, Micah Gersten wrote: > So, I did a little research into available times in #ubuntu-meeting, > here's what's available: > > Tue 19:00 UTC > Wed 16:00-18:00, 19:00 UTC > Thu 16:00-18:00, 19:00 UTC > > Micah > Wanted to bump this since we discussed having a meeting the week before UDS and that's next week. Micah From brian at ubuntu.com Thu Apr 28 15:32:07 2011 From: brian at ubuntu.com (Brian Murray) Date: Thu, 28 Apr 2011 08:32:07 -0700 Subject: Ubuntu Bugsquad Meeting Times & #ubuntu-meeting In-Reply-To: <4DB0B7E4.5040005@ubuntu.com> References: <4DB0B7E4.5040005@ubuntu.com> Message-ID: <20110428153207.GF2525@murraytwins.com> On Thu, Apr 21, 2011 at 06:04:04PM -0500, Micah Gersten wrote: > So, I did a little research into available times in #ubuntu-meeting, > here's what's available: > > Tue 19:00 UTC > Wed 16:00-18:00, 19:00 UTC > Thu 16:00-18:00, 19:00 UTC I'd prefer either Tuesday or Thursday and it actually might be interesting to have it on Thursday with the Bug Day. As I interpret the times you've listed we could start at 1600, 1700 or 1900 if want an hour long meeting is that right? I'm flexible regarding the time but would prefer it wasn't at 1900. Thanks for looking into this. -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From pedro at ubuntu.com Thu Apr 28 15:33:59 2011 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Thu, 28 Apr 2011 12:33:59 -0300 Subject: Ubuntu Bugsquad Meeting Times & #ubuntu-meeting In-Reply-To: <20110428153207.GF2525@murraytwins.com> References: <4DB0B7E4.5040005@ubuntu.com> <20110428153207.GF2525@murraytwins.com> Message-ID: <1304004839.2152.13.camel@wombat> Hola, El Thu, 28-04-2011 a las 08:32 -0700, Brian Murray escribió: > On Thu, Apr 21, 2011 at 06:04:04PM -0500, Micah Gersten wrote: > > So, I did a little research into available times in #ubuntu-meeting, > > here's what's available: > > > > Tue 19:00 UTC > > Wed 16:00-18:00, 19:00 UTC > > Thu 16:00-18:00, 19:00 UTC > > I'd prefer either Tuesday or Thursday and it actually might be > interesting to have it on Thursday with the Bug Day. As I interpret the > times you've listed we could start at 1600, 1700 or 1900 if want an hour > long meeting is that right? I like this idea of having it on Thursday because of the Bug day if i'd have to vote i'd go for that one ;-) Thanks a lot for doing this. Happy release day!, pedro. From cjk at teamcharliesangels.com Thu Apr 28 16:22:42 2011 From: cjk at teamcharliesangels.com (Charlie Kravetz) Date: Thu, 28 Apr 2011 10:22:42 -0600 Subject: Ubuntu Bugsquad Meeting Times & #ubuntu-meeting In-Reply-To: <4DB0B7E4.5040005@ubuntu.com> References: <4DB0B7E4.5040005@ubuntu.com> Message-ID: <20110428102242.0b04c443@teamcharliesangels.com> On Thu, 21 Apr 2011 18:04:04 -0500 Micah Gersten wrote: > So, I did a little research into available times in #ubuntu-meeting, > here's what's available: > > Tue 19:00 UTC > Wed 16:00-18:00, 19:00 UTC > Thu 16:00-18:00, 19:00 UTC > > Micah > I could handle Thursday just fine, it is only one day a month, afterall. Having with the BugDay might get more people involved, too. -- Charlie Kravetz Linux Registered User Number 425914 [http://counter.li.org/] Never let anyone steal your DREAM. [http://keepingdreams.com] From micahg at ubuntu.com Thu Apr 28 17:52:40 2011 From: micahg at ubuntu.com (Micah Gersten) Date: Thu, 28 Apr 2011 12:52:40 -0500 Subject: Ubuntu Bugsquad Meeting Times & #ubuntu-meeting In-Reply-To: <20110428153207.GF2525@murraytwins.com> References: <4DB0B7E4.5040005@ubuntu.com> <20110428153207.GF2525@murraytwins.com> Message-ID: <4DB9A968.50401@ubuntu.com> On 04/28/2011 10:32 AM, Brian Murray wrote: > On Thu, Apr 21, 2011 at 06:04:04PM -0500, Micah Gersten wrote: >> So, I did a little research into available times in #ubuntu-meeting, >> here's what's available: >> >> Tue 19:00 UTC >> Wed 16:00-18:00, 19:00 UTC >> Thu 16:00-18:00, 19:00 UTC > I'd prefer either Tuesday or Thursday and it actually might be > interesting to have it on Thursday with the Bug Day. As I interpret the > times you've listed we could start at 1600, 1700 or 1900 if want an hour > long meeting is that right? > > I'm flexible regarding the time but would prefer it wasn't at 1900. > > Thanks for looking into this. > > -- > Brian Murray > Ubuntu Bug Master Yes, those start times are correct. Thursday is normally fine for me as well, I just won't be able to make it next week (assuming we have a meeting then). Micah Micah From brian at ubuntu.com Thu Apr 28 18:38:28 2011 From: brian at ubuntu.com (Brian Murray) Date: Thu, 28 Apr 2011 11:38:28 -0700 Subject: Launchpad's +karma page Message-ID: <20110428183828.GG2525@murraytwins.com> Every Launchpad user has a karma page[1] that sort of keeps track of their activity in Launchpad. During the Natty release cycle I took on a work item of investigating to see if we could make that page more informative. Come to find out this isn't easily possible as the karma table only includes information about the project, or distribution and package where the karma was earned not about specific bugs. When working on this though it occurred to me that I didn't recall the use case for having the page be more informative. Does anyone happen to remember the use case? I ask because there are other sources of information regarding actions and bugs. [1] http://launchpad.net/~brian-murray/+karma for example Thanks, -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From brian at ubuntu.com Thu Apr 28 19:00:57 2011 From: brian at ubuntu.com (Brian Murray) Date: Thu, 28 Apr 2011 12:00:57 -0700 Subject: Ubuntu Bugsquad Meeting Times & #ubuntu-meeting In-Reply-To: <4DB9A968.50401@ubuntu.com> References: <4DB0B7E4.5040005@ubuntu.com> <20110428153207.GF2525@murraytwins.com> <4DB9A968.50401@ubuntu.com> Message-ID: <20110428190057.GH2525@murraytwins.com> On Thu, Apr 28, 2011 at 12:52:40PM -0500, Micah Gersten wrote: > On 04/28/2011 10:32 AM, Brian Murray wrote: > > On Thu, Apr 21, 2011 at 06:04:04PM -0500, Micah Gersten wrote: > >> So, I did a little research into available times in #ubuntu-meeting, > >> here's what's available: > >> > >> Tue 19:00 UTC > >> Wed 16:00-18:00, 19:00 UTC > >> Thu 16:00-18:00, 19:00 UTC > > I'd prefer either Tuesday or Thursday and it actually might be > > interesting to have it on Thursday with the Bug Day. As I interpret the > > times you've listed we could start at 1600, 1700 or 1900 if want an hour > > long meeting is that right? > > > > I'm flexible regarding the time but would prefer it wasn't at 1900. > > > > Thanks for looking into this. > > > > -- > > Brian Murray > > Ubuntu Bug Master > > Yes, those start times are correct. Thursday is normally fine for me as > well, I just won't be able to make it next week (assuming we have a > meeting then). Maybe we should have one May 5th and May 12th and then return to our new normal program of the 2nd Thursday? Barring any objections let's choose 1700 UTC as the meeting time. -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From cjk at teamcharliesangels.com Thu Apr 28 19:05:54 2011 From: cjk at teamcharliesangels.com (Charlie Kravetz) Date: Thu, 28 Apr 2011 13:05:54 -0600 Subject: Ubuntu Bugsquad Meeting Times & #ubuntu-meeting In-Reply-To: <20110428190057.GH2525@murraytwins.com> References: <4DB0B7E4.5040005@ubuntu.com> <20110428153207.GF2525@murraytwins.com> <4DB9A968.50401@ubuntu.com> <20110428190057.GH2525@murraytwins.com> Message-ID: <20110428130554.42294b40@teamcharliesangels.com> On Thu, 28 Apr 2011 12:00:57 -0700 Brian Murray wrote: > On Thu, Apr 28, 2011 at 12:52:40PM -0500, Micah Gersten wrote: > > On 04/28/2011 10:32 AM, Brian Murray wrote: > > > On Thu, Apr 21, 2011 at 06:04:04PM -0500, Micah Gersten wrote: > > >> So, I did a little research into available times in #ubuntu-meeting, > > >> here's what's available: > > >> > > >> Tue 19:00 UTC > > >> Wed 16:00-18:00, 19:00 UTC > > >> Thu 16:00-18:00, 19:00 UTC > > > I'd prefer either Tuesday or Thursday and it actually might be > > > interesting to have it on Thursday with the Bug Day. As I interpret the > > > times you've listed we could start at 1600, 1700 or 1900 if want an hour > > > long meeting is that right? > > > > > > I'm flexible regarding the time but would prefer it wasn't at 1900. > > > > > > Thanks for looking into this. > > > > > > -- > > > Brian Murray > > > Ubuntu Bug Master > > > > Yes, those start times are correct. Thursday is normally fine for me as > > well, I just won't be able to make it next week (assuming we have a > > meeting then). > > Maybe we should have one May 5th and May 12th and then return to our new > normal program of the 2nd Thursday? > > Barring any objections let's choose 1700 UTC as the meeting time. > > -- > Brian Murray > Ubuntu Bug Master Sounds good to me. We are aware that the 12th is during UDS, right? -- Charlie Kravetz Linux Registered User Number 425914 [http://counter.li.org/] Never let anyone steal your DREAM. [http://keepingdreams.com] -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 490 bytes Desc: not available URL: From brian at ubuntu.com Thu Apr 28 19:15:39 2011 From: brian at ubuntu.com (Brian Murray) Date: Thu, 28 Apr 2011 12:15:39 -0700 Subject: Ubuntu Bugsquad Meeting Times & #ubuntu-meeting In-Reply-To: <20110428130554.42294b40@teamcharliesangels.com> References: <4DB0B7E4.5040005@ubuntu.com> <20110428153207.GF2525@murraytwins.com> <4DB9A968.50401@ubuntu.com> <20110428190057.GH2525@murraytwins.com> <20110428130554.42294b40@teamcharliesangels.com> Message-ID: <20110428191539.GI2525@murraytwins.com> On Thu, Apr 28, 2011 at 01:05:54PM -0600, Charlie Kravetz wrote: > On Thu, 28 Apr 2011 12:00:57 -0700 > Brian Murray wrote: > > > On Thu, Apr 28, 2011 at 12:52:40PM -0500, Micah Gersten wrote: > > > On 04/28/2011 10:32 AM, Brian Murray wrote: > > > > On Thu, Apr 21, 2011 at 06:04:04PM -0500, Micah Gersten wrote: > > > >> So, I did a little research into available times in #ubuntu-meeting, > > > >> here's what's available: > > > >> > > > >> Tue 19:00 UTC > > > >> Wed 16:00-18:00, 19:00 UTC > > > >> Thu 16:00-18:00, 19:00 UTC > > > > I'd prefer either Tuesday or Thursday and it actually might be > > > > interesting to have it on Thursday with the Bug Day. As I interpret the > > > > times you've listed we could start at 1600, 1700 or 1900 if want an hour > > > > long meeting is that right? > > > > > > > > I'm flexible regarding the time but would prefer it wasn't at 1900. > > > > > > > > Thanks for looking into this. > > > > > > > > -- > > > > Brian Murray > > > > Ubuntu Bug Master > > > > > > Yes, those start times are correct. Thursday is normally fine for me as > > > well, I just won't be able to make it next week (assuming we have a > > > meeting then). > > > > Maybe we should have one May 5th and May 12th and then return to our new > > normal program of the 2nd Thursday? > > > > Barring any objections let's choose 1700 UTC as the meeting time. > > > > -- > > Brian Murray > > Ubuntu Bug Master > > Sounds good to me. We are aware that the 12th is during UDS, right? Yes, that's why I meant to say the 19th. Thanks! -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From yofel at gmx.net Thu Apr 28 19:51:18 2011 From: yofel at gmx.net (Philip Muskovac) Date: Thu, 28 Apr 2011 21:51:18 +0200 Subject: Ubuntu Bugsquad Meeting Times & #ubuntu-meeting In-Reply-To: <20110428190057.GH2525@murraytwins.com> References: <4DB0B7E4.5040005@ubuntu.com> <20110428153207.GF2525@murraytwins.com> <4DB9A968.50401@ubuntu.com> <20110428190057.GH2525@murraytwins.com> Message-ID: <4DB9C536.4060702@gmx.net> On 04/28/2011 09:00 PM, Brian Murray wrote: > On Thu, Apr 28, 2011 at 12:52:40PM -0500, Micah Gersten wrote: >> On 04/28/2011 10:32 AM, Brian Murray wrote: >>> On Thu, Apr 21, 2011 at 06:04:04PM -0500, Micah Gersten wrote: >>>> So, I did a little research into available times in #ubuntu-meeting, >>>> here's what's available: >>>> >>>> Tue 19:00 UTC >>>> Wed 16:00-18:00, 19:00 UTC >>>> Thu 16:00-18:00, 19:00 UTC >>> I'd prefer either Tuesday or Thursday and it actually might be >>> interesting to have it on Thursday with the Bug Day. As I interpret the >>> times you've listed we could start at 1600, 1700 or 1900 if want an hour >>> long meeting is that right? >>> >>> I'm flexible regarding the time but would prefer it wasn't at 1900. >>> >>> Thanks for looking into this. >>> >>> -- >>> Brian Murray >>> Ubuntu Bug Master >> >> Yes, those start times are correct. Thursday is normally fine for me as >> well, I just won't be able to make it next week (assuming we have a >> meeting then). > > Maybe we should have one May 5th and May 12th and then return to our new > normal program of the 2nd Thursday? > > Barring any objections let's choose 1700 UTC as the meeting time. > > -- > Brian Murray > Ubuntu Bug Master > +1 from me for thursday 1700 UTC, I can manage that Philip From hggdh2 at ubuntu.com Fri Apr 29 13:55:24 2011 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Fri, 29 Apr 2011 08:55:24 -0500 Subject: Launchpad's +karma page In-Reply-To: <20110428183828.GG2525@murraytwins.com> References: <20110428183828.GG2525@murraytwins.com> Message-ID: <4DBAC34C.4010903@ubuntu.com> On 04/28/2011 01:38 PM, Brian Murray wrote: > Every Launchpad user has a karma page[1] that sort of keeps track of their > activity in Launchpad. During the Natty release cycle I took on a work > item of investigating to see if we could make that page more > informative. Come to find out this isn't easily possible as the karma > table only includes information about the project, or distribution and > package where the karma was earned not about specific bugs. > > When working on this though it occurred to me that I didn't recall the > use case for having the page be more informative. Does anyone happen to > remember the use case? One immediate benefit would be a direct way to follow one's most recent actions (mostly bug work), if we could link from karma to bug. I do remember we discussing this, I think during UDS-N. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 900 bytes Desc: OpenPGP digital signature URL: From noreply at ubuntu.com Thu Apr 28 23:15:05 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 28 Apr 2011 23:15:05 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Responses=22_by_yofel?= Message-ID: <20110428231505.6905.47547@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by yofel: http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=324&rev2=325 The comment on the change is: natty -> oneiric ------------------------------------------------------------------------------ Before using this, ''please'' check "rmadison " to see if the package version has changed between when the bug was reported and the current development release. If it has not changed, there is no need to ask. If it has changed, check the changelog (via aptitude changelog $PKGNAME) to see if this issue has been specifically addressed. - || Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Natty Narwhal. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.|| + || Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Oneiric Ocelot. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.|| == Missing a crash report or having a .crash attachment == @@ -214, +214 @@ ## Also we are actively promoting testing the development release of Ubuntu so something like this could be added: - ## || The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Natty Narwhal. It would help us greatly if you could test with it so we can work on getting it fixed in the actively developed release. You can find out more about the development release at http://www.ubuntu.com/testing/ || + ## || The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Oneiric Ocelot. It would help us greatly if you could test with it so we can work on getting it fixed in the actively developed release. You can find out more about the development release at http://www.ubuntu.com/testing/ || == Packages not provided by Ubuntu == @@ -238, +238 @@ The bug's state should become '''Fix Released''' and if the package qualifies for a [[https://wiki.ubuntu.com/StableReleaseUpdates#Procedure|Stable Release Update (SRU)]]: - || Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Natty Narwhal.<
><
> This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please do steps 1 and 2 of the SRU Procedure [1] to bring the need to a developer's attention.<
><
>[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure|| + || Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Oneiric Ocelot.<
><
> This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please do steps 1 and 2 of the SRU Procedure [1] to bring the need to a developer's attention.<
><
>[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure|| The bug's state should become '''Fix Released''' and if the package does not qualify for a SRU because it is considered a minor bug and the package can be backported: - || Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Natty Narwhal.<
><
> If you need a fix for the bug in previous versions of Ubuntu, please follow the instructions for "How to request new packages" at https://help.ubuntu.com/community/UbuntuBackports#request-new-packages || + || Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Oneiric Ocelot.<
><
> If you need a fix for the bug in previous versions of Ubuntu, please follow the instructions for "How to request new packages" at https://help.ubuntu.com/community/UbuntuBackports#request-new-packages || The bug's state should become '''Fix Released''' and if the package can not be backported: - || Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Natty Narwhal. It won't be fixed in previous versions of Ubuntu because the package doesn't fit the requirements for backporting. See https://help.ubuntu.com/community/UbuntuBackports for more information. || + || Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Oneiric Ocelot. It won't be fixed in previous versions of Ubuntu because the package doesn't fit the requirements for backporting. See https://help.ubuntu.com/community/UbuntuBackports for more information. || == Reported by someone not respecting the Code of Conduct == From brian at ubuntu.com Fri Apr 29 14:40:23 2011 From: brian at ubuntu.com (Brian Murray) Date: Fri, 29 Apr 2011 07:40:23 -0700 Subject: Launchpad's +karma page In-Reply-To: <4DBAC34C.4010903@ubuntu.com> References: <20110428183828.GG2525@murraytwins.com> <4DBAC34C.4010903@ubuntu.com> Message-ID: <20110429144023.GJ2525@murraytwins.com> On Fri, Apr 29, 2011 at 08:55:24AM -0500, C de-Avillez wrote: > On 04/28/2011 01:38 PM, Brian Murray wrote: > > Every Launchpad user has a karma page[1] that sort of keeps track of their > > activity in Launchpad. During the Natty release cycle I took on a work > > item of investigating to see if we could make that page more > > informative. Come to find out this isn't easily possible as the karma > > table only includes information about the project, or distribution and > > package where the karma was earned not about specific bugs. > > > > When working on this though it occurred to me that I didn't recall the > > use case for having the page be more informative. Does anyone happen to > > remember the use case? > > One immediate benefit would be a direct way to follow one's most > recent actions (mostly bug work), if we could link from karma to > bug. I do remember we discussing this, I think during UDS-N. We do have this feature of the lp_karma_suffix Greasemonkey script (which is a part of the extension) that allows you to "Follow the bug trail"[1] of a person by taking you to the Gmane archive of the ubuntu-bugs mailing list. [The ubuntu-bugs mailing list gets bug mail about all public Ubuntu bug reports.] Looking at this again there is actually a link to the bug trail from the +karma page of a person. I took a cursory look at searching for action dates (found in that page's source) on gmane and didn't get any matches but someone might be able to sort that out. However, gmane is behind a bit and the karma table doesn't say if the action was in Ubuntu or not so this might just result in more confusion. Perhaps making it easier to "follow the bug trail" of a person would help. Right now the link exists on an individual bug page and on +karma, perhaps sticking it on people pages (so you don't have to click the link to +karma) would help? [1] http://search.gmane.org/?query=&author=Ubuntu+QA%27s+Bug+Bot&group=gmane.linux.ubuntu.bugs.general&sort=date&DEFAULTOP=and -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From brian at ubuntu.com Fri Apr 29 15:18:40 2011 From: brian at ubuntu.com (Brian Murray) Date: Fri, 29 Apr 2011 08:18:40 -0700 Subject: Launchpad bug tool Message-ID: <20110429151840.GK2525@murraytwins.com> Have you ever been looking at a bug report and looked at one attachment and then another and then another try to find the exact thing you wanted? I personally found this process rather painful and wanted to write something to download all the attachments to my system so I would have them all available and could look at them locally. I recently found out I didn't need to write it because it already existed! There is a python script called grab-attachments which is part of the ubuntu-dev-tools package which you pass a bug number or two or three. grab-attachments 773137 This will create a folder named bug-773137 in your current directory with all the bug's attachments! Then you can use grep or something with all of them. -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From RedSingularity at gmx.com Fri Apr 29 15:40:03 2011 From: RedSingularity at gmx.com (RedSingularity) Date: Fri, 29 Apr 2011 11:40:03 -0400 Subject: Launchpad bug tool In-Reply-To: <20110429151840.GK2525@murraytwins.com> References: <20110429151840.GK2525@murraytwins.com> Message-ID: <4DBADBD3.5080808@gmx.com> On 04/29/2011 11:18 AM, Brian Murray wrote: Recently, I have been looking for something that does this as well. Thanks for that info! :-) > Have you ever been looking at a bug report and looked at one attachment > and then another and then another try to find the exact thing you > wanted? I personally found this process rather painful and wanted to > write something to download all the attachments to my system so I would > have them all available and could look at them locally. I recently > found out I didn't need to write it because it already existed! > > There is a python script called grab-attachments which is part of the > ubuntu-dev-tools package which you pass a bug number or two or three. > > grab-attachments 773137 > > This will create a folder named bug-773137 in your current directory > with all the bug's attachments! Then you can use grep or something with > all of them. > > -- > Brian Murray > Ubuntu Bug Master From cjk at teamcharliesangels.com Fri Apr 29 15:47:31 2011 From: cjk at teamcharliesangels.com (Charlie Kravetz) Date: Fri, 29 Apr 2011 09:47:31 -0600 Subject: Launchpad bug tool In-Reply-To: <20110429151840.GK2525@murraytwins.com> References: <20110429151840.GK2525@murraytwins.com> Message-ID: <20110429094731.56920cef@teamcharliesangels.com> On Fri, 29 Apr 2011 08:18:40 -0700 Brian Murray wrote: > Have you ever been looking at a bug report and looked at one attachment > and then another and then another try to find the exact thing you > wanted? I personally found this process rather painful and wanted to > write something to download all the attachments to my system so I would > have them all available and could look at them locally. I recently > found out I didn't need to write it because it already existed! > > There is a python script called grab-attachments which is part of the > ubuntu-dev-tools package which you pass a bug number or two or three. > > grab-attachments 773137 > > This will create a folder named bug-773137 in your current directory > with all the bug's attachments! Then you can use grep or something with > all of them. > > -- > Brian Murray > Ubuntu Bug Master Thank you for this one! I too have really wished I did not have to keep getting the attachments, one at a time. -- Charlie Kravetz Linux Registered User Number 425914 [http://counter.li.org/] Never let anyone steal your DREAM. [http://keepingdreams.com] -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 490 bytes Desc: not available URL: From yofel at gmx.net Fri Apr 29 16:23:12 2011 From: yofel at gmx.net (Philip Muskovac) Date: Fri, 29 Apr 2011 18:23:12 +0200 Subject: Launchpad bug tool In-Reply-To: <20110429151840.GK2525@murraytwins.com> References: <20110429151840.GK2525@murraytwins.com> Message-ID: <4DBAE5F0.9020207@gmx.net> On 04/29/2011 05:18 PM, Brian Murray wrote: > Have you ever been looking at a bug report and looked at one attachment > and then another and then another try to find the exact thing you > wanted? I personally found this process rather painful and wanted to > write something to download all the attachments to my system so I would > have them all available and could look at them locally. I recently > found out I didn't need to write it because it already existed! > > There is a python script called grab-attachments which is part of the > ubuntu-dev-tools package which you pass a bug number or two or three. > > grab-attachments 773137 > > This will create a folder named bug-773137 in your current directory > with all the bug's attachments! Then you can use grep or something with > all of them. > > -- > Brian Murray > Ubuntu Bug Master > Nice one, sad that it can't handle duplicate attachments which is common with apport-collect, I filed bug 773391 about that. Philip From brian at ubuntu.com Fri Apr 29 16:29:12 2011 From: brian at ubuntu.com (Brian Murray) Date: Fri, 29 Apr 2011 09:29:12 -0700 Subject: Launchpad bug tool In-Reply-To: <4DBAE5F0.9020207@gmx.net> References: <20110429151840.GK2525@murraytwins.com> <4DBAE5F0.9020207@gmx.net> Message-ID: <20110429162912.GM2525@murraytwins.com> On Fri, Apr 29, 2011 at 06:23:12PM +0200, Philip Muskovac wrote: > On 04/29/2011 05:18 PM, Brian Murray wrote: > >Have you ever been looking at a bug report and looked at one attachment > >and then another and then another try to find the exact thing you > >wanted? I personally found this process rather painful and wanted to > >write something to download all the attachments to my system so I would > >have them all available and could look at them locally. I recently > >found out I didn't need to write it because it already existed! > > > >There is a python script called grab-attachments which is part of the > >ubuntu-dev-tools package which you pass a bug number or two or three. > > > >grab-attachments 773137 > > > >This will create a folder named bug-773137 in your current directory > >with all the bug's attachments! Then you can use grep or something with > >all of them. > > > >-- > >Brian Murray > >Ubuntu Bug Master > > > > Nice one, sad that it can't handle duplicate attachments which is > common with apport-collect, I filed bug 773391 about that. I actually have a branch for this and will get it added to Oneiric. -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: