Re: Handling crash reports
On Thu, Jan 25, 2007 at 04:29:03PM -0600, David Farning wrote: This is follow up to the changing nature of bug reports from a few weeks ago. On the Mozillateam our triagers are getting swamped with automatic crash reports. I would like to make a few suggestions that would greatly help our efforts and hopefully others developers too. 1. Add a top level boolean that categorizes issue reports as crashes. This will greatly aid the sorting of bugs for different types of triagers. If your intention is to suggest this as an improvement to Launchpad, then you should send it to the launchpad-users list (the Launchpad developers don't read ubuntu-devel-discuss). 2. Automate the process for apport to upload crash report data. Many of our issue are reports of crashes without the crash data. This is now implemented in Feisty, as we had been working along these lines for some time now. 3. Automate the process of symbolizing crash reports. The process of downloading the crash report, running apport-retrace, and re-uploading the now symbolized crash report is very slow for all but the fastest network connections. This has, of course, been our intention from the start, which is why you see that all of the pieces for it already exist but need some work to be glued together. Unfortunately, this gluing is sometimes the hard part. Newer versions of apport in Feisty provide a more standardized summary for the bug, which should help in culling duplicates. If the reports are only useful with debug symbols, then apport could check whether firefox-dbg is installed, and guide the user to install it in order to submit the report. The new apport hook infrastructure might be sufficient for the task. -- - mdz -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: restarting firefox
On Sat, Jan 27, 2007 at 11:37:01PM -0600, David Farning wrote: A number of browser related bug seem to caused by not restarting the browser after updating some packages in the system. These packages seem to be firefox itself, some themes, and some fonts. Until the mozillateam gets these issues sorted out, would it be feasible to have update manager request that firefox be restart if any themes or fonts are updated. This is already done for Firefox itself. Can you point to some of the apparent issues with themes and fonts? I've never known those to cause a problem. Martin: how about an apport hook which would check for the existence of the file which indicates that a restart is needed, and suppresses the problem report, apologizing and telling the user that Firefox must be restarted after updating it. -- - mdz -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Herd 3: Crash Report right after Booting Live or Fresh Install
Hi everyone, I'm just checking if these are known bug(s): 1) Right after booting Herd 3 live or a fresh install I get a crash report (about Add/Remove Programs) in the systray area. This seems to be very reproducible. 2) I tried to use the designated error reporting mechanism for reporting the error, but unfortunately the web browser never showed up after sending the crash data. I am using a Dell Latitude X1, which did not surface problem #1 with Herd 2 or earlier. Regards, Andreas -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Herd 3: Crash Report right after Booting Live or Fresh Install
On 2/3/07, Andreas Schildbach [EMAIL PROTECTED] wrote: Hi everyone, I'm just checking if these are known bug(s): 1) Right after booting Herd 3 live or a fresh install I get a crash report (about Add/Remove Programs) in the systray area. This seems to be very reproducible. 2) I tried to use the designated error reporting mechanism for reporting the error, but unfortunately the web browser never showed up after sending the crash data. I am using a Dell Latitude X1, which did not surface problem #1 with Herd 2 or earlier. Regards, Andreas Herd 3 now includes Python 2.5 (with all the necessary modules), and doing so, removed alot of Python 2.4 modules. And I see that most of the applications are working with 2.5, except that Gnome App Install is the only application that use Python 2.4, which is currently an increment of CD space, which is too bad, because we can't test out one of the most shiningly important and super advance application in this world, the libgimme super automatic codec installer. Oh the humanity! Cheers, Joel -- Carpe Diem -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
Re: Herd 3: Crash Report right after Booting Live or Fresh Install
On 2/2/07, Joel Bryan Juliano [EMAIL PROTECTED] wrote: Herd 3 now includes Python 2.5 (with all the necessary modules), and doing so, removed alot of Python 2.4 modules. And I see that most of the applications are working with 2.5, except that Gnome App Install is the only application that use Python 2.4, which is currently an increment of CD space, which is too bad, because we can't test out one of the most shiningly important and super advance application in this world, the libgimme super automatic codec installer. Oh the humanity! ??? libgimme works in Herd 3 :) I even took screenshots: http://members.shaw.ca/Limulus/misc/gimme1a.png http://members.shaw.ca/Limulus/misc/gimme1.png http://members.shaw.ca/Limulus/misc/gimme2.png Tested with this file iiRC: http://www.kemado.com/site/downloadaudio.php?artist=thefeverfile=waitingforthecentipede.mp3 CK -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
