From brian at ubuntu.com Tue May 1 15:47:37 2012 From: brian at ubuntu.com (Brian Murray) Date: Tue, 1 May 2012 08:47:37 -0700 Subject: Bitesize Task Message-ID: <20120501154737.GA2879@murraytwins.com> I just cleaned up some texinfo package installation failure bug reports due to syntax errors in /etc/environment. However, I didn't get all of them because DpkgTerminalLog is sometimes included in the bug's description. For an example see http://launchpad.net/bugs/778504 which has: /etc/environment: line 2: CLASSPATH: command not found This is something the reporter will need to sort out. It would be great if somebody could review the rest of the textinfo apport-package bug reports for these errors. If you want to narrow your search further, I found that most reports had an exit status of 127 or 2. https://bugs.launchpad.net/ubuntu/+source/texinfo -- Brian Murray Ubuntu Bug Master From maarten.bezemer at gmail.com Wed May 2 08:17:37 2012 From: maarten.bezemer at gmail.com (Maarten Bezemer) Date: Wed, 02 May 2012 10:17:37 +0200 Subject: Bitesize Task In-Reply-To: <20120501154737.GA2879@murraytwins.com> References: <20120501154737.GA2879@murraytwins.com> Message-ID: <2199486.A9tlr8BOAp@ce-bzr> On Tuesday 01 May 2012 08:47:37 Brian Murray wrote: > I just cleaned up some texinfo package installation failure bug reports > due to syntax errors in /etc/environment. However, I didn't get all of > them because DpkgTerminalLog is sometimes included in the bug's > description. For an example see http://launchpad.net/bugs/778504 which > has: > > /etc/environment: line 2: CLASSPATH: command not found > > This is something the reporter will need to sort out. It would be great > if somebody could review the rest of the textinfo apport-package bug > reports for these errors. If you want to narrow your search further, I > found that most reports had an exit status of 127 or 2. > > https://bugs.launchpad.net/ubuntu/+source/texinfo I am willing to take a look at the list, but it is unclear to me what exactly needs to be done... (still learning! ) When a 'CLASSPATH: command not found' error is available in the report: I should ask for additional information? If so, what information is missing in such cases? Regards, Maarten From brian at ubuntu.com Wed May 2 14:41:34 2012 From: brian at ubuntu.com (Brian Murray) Date: Wed, 2 May 2012 07:41:34 -0700 Subject: Bitesize Task In-Reply-To: <2199486.A9tlr8BOAp@ce-bzr> References: <20120501154737.GA2879@murraytwins.com> <2199486.A9tlr8BOAp@ce-bzr> Message-ID: <20120502144134.GB2879@murraytwins.com> On Wed, May 02, 2012 at 10:17:37AM +0200, Maarten Bezemer wrote: > On Tuesday 01 May 2012 08:47:37 Brian Murray wrote: > > I just cleaned up some texinfo package installation failure bug reports > > due to syntax errors in /etc/environment. However, I didn't get all of > > them because DpkgTerminalLog is sometimes included in the bug's > > description. For an example see http://launchpad.net/bugs/778504 which > > has: > > > > /etc/environment: line 2: CLASSPATH: command not found > > > > This is something the reporter will need to sort out. It would be great > > if somebody could review the rest of the textinfo apport-package bug > > reports for these errors. If you want to narrow your search further, I > > found that most reports had an exit status of 127 or 2. > > > > https://bugs.launchpad.net/ubuntu/+source/texinfo > > I am willing to take a look at the list, but it is unclear to me what exactly > needs to be done... (still learning! ) > When a 'CLASSPATH: command not found' error is available in the report: I > should ask for additional information? If so, what information is missing in > such cases? The example bug report shows how I handled the bug and how they should be handled. I indicated that the reporter need to fix line 2 of their /etc/environment file and that the bug was Invalid. -- Brian Murray Ubuntu Bug Master From stimberg at users.sourceforge.net Wed May 2 14:50:46 2012 From: stimberg at users.sourceforge.net (Marcel Stimberg) Date: Wed, 2 May 2012 16:50:46 +0200 Subject: Bitesize Task In-Reply-To: <20120502144134.GB2879@murraytwins.com> References: <20120501154737.GA2879@murraytwins.com> <2199486.A9tlr8BOAp@ce-bzr> <20120502144134.GB2879@murraytwins.com> Message-ID: Hi Brian, > The example bug report shows how I handled the bug and how they should > be handled.  I indicated that the reporter need to fix line 2 of their > /etc/environment file and that the bug was Invalid. actually, the linked example bug ( http://launchpad.net/bugs/778504 ) does not have any response and is still at status "New"... Cheers Marcel From brian at ubuntu.com Wed May 2 15:00:52 2012 From: brian at ubuntu.com (Brian Murray) Date: Wed, 2 May 2012 08:00:52 -0700 Subject: Bitesize Task In-Reply-To: References: <20120501154737.GA2879@murraytwins.com> <2199486.A9tlr8BOAp@ce-bzr> <20120502144134.GB2879@murraytwins.com> Message-ID: <20120502150052.GC2879@murraytwins.com> On Wed, May 02, 2012 at 04:50:46PM +0200, Marcel Stimberg wrote: > Hi Brian, > > > The example bug report shows how I handled the bug and how they should > > be handled.  I indicated that the reporter need to fix line 2 of their > > /etc/environment file and that the bug was Invalid. > actually, the linked example bug ( http://launchpad.net/bugs/778504 ) > does not have any response and is still at status "New"... Ah, I see what I did (or didn't) do there. http://launchpad.net/bugs/984562 Thanks! -- Brian Murray Ubuntu Bug Master From maarten.bezemer at gmail.com Wed May 2 15:16:55 2012 From: maarten.bezemer at gmail.com (Maarten Bezemer) Date: Wed, 02 May 2012 17:16:55 +0200 Subject: Bitesize Task In-Reply-To: <20120502150052.GC2879@murraytwins.com> References: <20120501154737.GA2879@murraytwins.com> <20120502150052.GC2879@murraytwins.com> Message-ID: <6242410.pzt3noh3Pj@ce-bzr> On Wednesday 02 May 2012 08:00:52 Brian Murray wrote: > On Wed, May 02, 2012 at 04:50:46PM +0200, Marcel Stimberg wrote: > > Hi Brian, > > > > > The example bug report shows how I handled the bug and how they should > > > be handled. I indicated that the reporter need to fix line 2 of their > > > /etc/environment file and that the bug was Invalid. > > > > actually, the linked example bug ( http://launchpad.net/bugs/778504 ) > > does not have any response and is still at status "New"... > > Ah, I see what I did (or didn't) do there. > > http://launchpad.net/bugs/984562 > > Thanks! That explains why I did not understood... :) I'll take a look at these bugs soon. Greetings, Maarten From m.m.bezemer at utwente.nl Wed May 2 15:16:01 2012 From: m.m.bezemer at utwente.nl (Maarten Bezemer) Date: Wed, 02 May 2012 17:16:01 +0200 Subject: Bitesize Task In-Reply-To: <20120502150052.GC2879@murraytwins.com> References: <20120501154737.GA2879@murraytwins.com> <20120502150052.GC2879@murraytwins.com> Message-ID: <1677935.stiXnIh2mg@ce-bzr> On Wednesday 02 May 2012 08:00:52 Brian Murray wrote: > On Wed, May 02, 2012 at 04:50:46PM +0200, Marcel Stimberg wrote: > > Hi Brian, > > > > > The example bug report shows how I handled the bug and how they should > > > be handled. I indicated that the reporter need to fix line 2 of their > > > /etc/environment file and that the bug was Invalid. > > > > actually, the linked example bug ( http://launchpad.net/bugs/778504 ) > > does not have any response and is still at status "New"... > > Ah, I see what I did (or didn't) do there. > > http://launchpad.net/bugs/984562 That explains why I did not understood... :) I'll take a look at these bugs soon. Greetings, Maarten From webmaster at ubuntu.com Wed May 2 17:10:46 2012 From: webmaster at ubuntu.com (Help Ubuntu) Date: Wed, 02 May 2012 17:10:46 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_sunil-sunilkchopra?= Message-ID: <20120502171046.21026.1375@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Community Ubuntu Documentation" for change notification. The "ReportingBugs" page has been changed by sunil-sunilkchopra: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=169&rev2=170 Comment: added 12.04 to the list of links for release notes * [[http://www.ubuntu.com/getubuntu/releasenotes/1010|Ubuntu 10.10 (Maverick Meerkat)]] * [[http://www.ubuntu.com/getubuntu/releasenotes/1104|Ubuntu 11.04 (Natty Narwhal)]] * [[http://www.ubuntu.com/getubuntu/releasenotes/1110|Ubuntu 11.10 (Oneiric Ocelot)]] + * [[http://www.ubuntu.com/getubuntu/releasenotes/1204|Ubuntu 12.04 (Precise Pangolin)]] If you have further information about an already reported bug, add this information to the existing report, rather than opening a new one. From webmaster at ubuntu.com Wed May 2 17:11:27 2012 From: webmaster at ubuntu.com (Help Ubuntu) Date: Wed, 02 May 2012 17:11:27 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_sunil-sunilkchopra?= Message-ID: <20120502171127.20790.12186@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Community Ubuntu Documentation" for change notification. The "ReportingBugs" page has been changed by sunil-sunilkchopra: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=170&rev2=171 Comment: added "LTS" to the link text for 12.04 release notes * [[http://www.ubuntu.com/getubuntu/releasenotes/1010|Ubuntu 10.10 (Maverick Meerkat)]] * [[http://www.ubuntu.com/getubuntu/releasenotes/1104|Ubuntu 11.04 (Natty Narwhal)]] * [[http://www.ubuntu.com/getubuntu/releasenotes/1110|Ubuntu 11.10 (Oneiric Ocelot)]] - * [[http://www.ubuntu.com/getubuntu/releasenotes/1204|Ubuntu 12.04 (Precise Pangolin)]] + * [[http://www.ubuntu.com/getubuntu/releasenotes/1204|Ubuntu 12.04 LTS (Precise Pangolin)]] If you have further information about an already reported bug, add this information to the existing report, rather than opening a new one. From noreply at ubuntu.com Fri May 4 12:49:03 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Fri, 04 May 2012 12:49:03 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/EasyTasks/List=22_by_hggdh2?= Message-ID: <20120504124903.2845.28990@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/EasyTasks/List" page has been changed by hggdh2: http://wiki.ubuntu.com/Bugs/EasyTasks/List?action=diff&rev1=25&rev2=26 Comment: took out 3 MIA reports ||<#8ae234> || [[https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-datecreated&search=Search&field.status%3Alist=New&field.assignee=&field.owner=&field.omit_dupes=on&field.has_patch=&field.has_no_package=on&field.tag=apport-bug|Bugs without a package and tagged apport-bug so contain lots of information]] || [[https://wiki.ubuntu.com/Bugs/FindRightPackage|Find the Right Package]] || ||<#8ae234> || [[https://bugs.launchpad.net/ubuntu/+expirable-bugs|Bugs marked for expiration]]|| [[https://bugs.edge.launchpad.net/ubuntu/+source/grub/+bug/32443|32443]] || ||<#8ae234>|| [[ http://people.ubuntu.com/~brian/reports/gt5comments/no-package.html | Bugs without a package with more than 5 comments ]] || [[https://wiki.ubuntu.com/Bugs/FindRightPackage|Find the Right Package]] || - ||<#8ae234> || [[ http://qa.ubuntu.com/reports/package/gt5subscribers/no-package.html | Bugs without a package with more than 5 subscribers ]] ||[[https://wiki.ubuntu.com/Bugs/FindRightPackage|Find the Right Package]] || ||<#fce94f> || [[https://bugs.launchpad.net/bugs/+bugs?field.searchtext=&orderby=-datecreated&search=Search&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.status_upstream=pending_bugwatch&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.tag=&field.tags_combinator=ANY|Bugs that need to be forwarded to an upstream bug tracker]] ||[[https://bugs.edge.launchpad.net/ubuntu/+source/zenity/+bug/317140|Downstream Report]] - [[http://bugzilla.gnome.org/show_bug.cgi?id=567773|Upstream Report]] || ||<#fce94f> || [[ http://qa.ubuntu.com/reports/launchpad-database/unlinked-bugwatch.html | Unlinked upstream bugs ]] || Ensure that the bugs are the same before linking || - ||<#fce94f> || [[ http://people.ubuntu.com/~brian/reports/no-package-attachments.html | Bugs without a package with attachment(s) ]] || [[https://wiki.ubuntu.com/Bugs/FindRightPackage|Find the Right Package]] || ||<#fce94f> || [[https://bugs.edge.launchpad.net/hundredpapercuts/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_patch=on&field.has_cve.used=&field.tag=&field.tags_combinator=ANY|Patch available! Please package and test.]] || || ||<#fce94f> || [[https://bugs.edge.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.component-empty-marker=1&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_patch=on&field.has_cve.used=&field.tag=&field.tags_combinator=ANY&field.has_no_package.used=&search=Search|Bugs with Patches to be reviewed]] || || ##|| || [[http://qa.ubuntu.com/reports/bugnumbers/yesterday.html|Bugs with a New status and reported since yesterday]] || || @@ -29, +27 @@ ||<#fce94f> || [[https://bugs.edge.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=date_last_updated&search=Search&field.status%3Alist=CONFIRMED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.component-empty-marker=1&field.tag=&field.tags_combinator=ANY&field.status_upstream-empty-marker=1&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_no_package.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on|Least recently changed bugs with a Confirmed status]] || || ||<#fce94f> || [[https://bugs.edge.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=date_last_updated&search=Search&field.status%3Alist=FIXCOMMITTED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.component-empty-marker=1&field.tag=&field.tags_combinator=ANY&field.status_upstream-empty-marker=1&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_no_package.used=&field.has_patch.used=&field.has_branches.used=&field.has_branches=on&field.has_no_branches.used=&field.has_no_branches=on|Least recently changed bugs with a Fix Committed status]] || || ||<#ef2929> || [[https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=bitesize|Bitesize bug reports]] || [[Bugs/HowToFix|How to fix bugs]] || - ||<#ef2929> || [[https://bugs.edge.launchpad.net/ubuntu/+mentoring|Reports Offering Mentorship]] || [[Bugs/HowToFix|How to fix bugs]] || ||<#ef2929> || Kernel bugs with patches attached: [[https://bugs.launchpad.net/ubuntu/+source/linux/+bugs?field.status:list=NEW&field.status:list=INCOMPLETE_WITH_RESPONSE&field.status:list=INCOMPLETE_WITHOUT_RESPONSE&field.status:list=CONFIRMED&field.status:list=TRIAGED&field.has_patch=on|linux]], [[https://bugs.launchpad.net/ubuntu/+source/linux-fsl-imx51/+bugs?field.status:list=NEW&field.status:list=INCOMPLETE_WITH_RESPONSE&field.status:list=INCOMPLETE_WITHOUT_RESPONSE&field.status:list=CONFIRMED&field.status:list=TRIAGED&field.has_patch=on|linux-fsl-imx51]], [[https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bugs?field.status:list=NEW&field.status:list=INCOMPLETE_WITH_RESPONSE&field.status:list=INCOMPLETE_WITHOUT_RESPONSE&field.status:list=CONFIRMED&field.status:list=TRIAGED&field.has_patch=on|linux-ec2]], [[https://bugs.launchpad.net/ubuntu/+source/linux-mvl-dove/+bugs?field.status:list=NEW&field.status:list=INCOMPLETE_WITH_RESPONSE&field.status:list=INCOMPLETE_WITHOUT_RESPONSE&field.status:list=CONFIRMED&field.status:list=TRIAGED&field.has_patch=on|linux-mvl-dove]] || [[KernelTeam/KernelPatches|How to handle Kernel bugs with patches]] || <> From webmaster at ubuntu.com Sat May 5 20:52:49 2012 From: webmaster at ubuntu.com (Help Ubuntu) Date: Sat, 05 May 2012 20:52:49 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_fabiomarconi?= Message-ID: <20120505205249.17096.10680@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Community Ubuntu Documentation" for change notification. The "ReportingBugs" page has been changed by fabiomarconi: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=171&rev2=172 * [[http://www.ubuntu.ro/documentatie/comunitate/RaportareErori |română]] * [[ReportingBugs_ru|Русский]] * [[ReportingBugs_zh-cn|中文(中国)-- 建设中]] - + * [[ReportingBugs-it|Italiano (in progress)]] [[#Top|Back to top]] = See Also = From noreply at ubuntu.com Sun May 6 19:26:24 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 06 May 2012 19:26:24 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Unity/FilingBugs=22_by_fabiomarc?= =?utf-8?q?oni?= Message-ID: <20120506192624.10859.70993@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Unity/FilingBugs" page has been changed by fabiomarconi: http://wiki.ubuntu.com/Unity/FilingBugs?action=diff&rev1=48&rev2=49 ## page was renamed from UnityFilingBugs + <> ||<>|| + + == Available languages == + [[https://wiki.ubuntu.com/Unity/FilingBugs_it| Italiano]], = Introduction = From noreply at ubuntu.com Sun May 6 19:15:07 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 06 May 2012 19:15:07 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Unity/FilingBugs=5Fit=22_by_fabi?= =?utf-8?q?omarconi?= Message-ID: <20120506191507.10889.34896@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Unity/FilingBugs_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/Unity/FilingBugs_it Comment: Italian translation New page: ##unity ##Traduzione debugging unity = Introduzione = Questa pagina fornisce istruzioni su come segnalare bugs relativi ad Unity, fornire le necessarie informazioni di debugging ed eseguirne il triage. = Segnalare bugs = == Problemi tecnici == Utilizzare lo strumento standard di Ubuntu per la raccolta di informazioni dettagliate inerenti la vostra configurazione di sistema. Da linea di comando: {{{ubuntu-bug unity}}} Quando nel vostro sistema avviene un crash, apparirà una finestra di dialogo che vi inviterà a segnalare il problema. Raccoglierà inoltre, automaticamente, informazioni necessarie al debugging. Ma è possibile rendersi ulteriormente utili aggiungendo informazioni alla segnalazione del bug che ne faciliteranno il lavoro di analisi: * Fornire il risultato del comado glxinfo. Esso contiene importanti informazioni grafiche utili nell'identificazione del problema (glxinfo è fornito dal pacchetto mesa-utils ed è automaticamente in esecuzione in Natty) * fornire una completa descrizione della vostra GPU e quanta RAM video ha. Per esempio, il nome commerciale della vostra scheda video potrebbe essere Radeon HD 4650 oppure NVidia Geforce GTX 280. Per le schede video integrate Intel non è necessario fornire alcuna informazione. * La risoluzione del monitor e le modalità dello schermo (singolo, doppio monitor, triplo monitor) Se la finestra di dialogo non dovesse apparire consultare la sezione "avanzata" descritta più avanti. Anche se il problema è attualmente in [[http://bugs.launchpad.net/compiz|Compiz]], è ragionevole riportare il bug contro Unity, provvederemo noi comunque a gestire le cose in modo da coinvolgere anche Compiz. Lavoriamo a stretto contatto con il progetto Compiz. Se invece siete certi che il problema risieda realmente in Compiz allora leggete la relativa sezione [[DebuggingCompiz]]. == Problemi di design ed usabilità == Siccome Unity è un'interfaccia utente, qualsiasi bug relativo alla funzionalità deve essere segnalato all' [[http://design.canonical.com/|Unity design team]]. Per riportare un bug nell'interfaccia utente: * Segnalare il bug contro il progetto [[https://bugs.launchpad.net/ayatana-design|Ayatana Design]] (NON contro il progetto Unity) * Impostare l'importanza come ti sembra corretto * Se il bug è urgente pingare ''JohnLea'' nel canale IRC #ayatana su freenode. == Consigli utili == * La precedenza è data ai bugs che si verificano in una installazione standard, quindi se è stata forzata l'installazione del cubo od altri plugin disabilitati bisogna prima riprodurre il bug in una installazione standard, ricordando che se alcuni plugin sono stati disabilitati c'è un valido motivo. * È utile riferire i passi da compiere per riprodurre il bug, è altresì utile sapere se avviene solamente con alcuni temi o in tutti. * Eseguendo nel terminale `unity --reset` avverrà il reset delle impostazioni di Unity, può anche essere utile creare un nuovo utente e verificare se il bug è ancora riproducibile. = Procedure di debugging avanzate = == Crashers bloccati == Se apport non si avvia automaticamente proponendovi di segnalare il bug potete verificare se una traccia del crasher è stata raccolta nella directory {{{/var/crash}}}. Controllate l'esistenza di un file il cui nome contenga 'compiz'. {{{ls -altr /var/crash}}} per listarli in ordine cronologico. Per segnalare un bug utilizzando un crashfile: * Rimanere nella attuale sessione di X. * Aggiungere un gestore finestre da una TTY se necessario, es. CTRL-ALT-F1, autenticarsi, {{{DISPLAY=:0 metacity --replace}}} * Dalla vostra sessione X eseguire: {{{apport-bug -c /var/crash/}}} e seguire la procedura nella pagina web che si aprirà. Attenzione, problemi di focalizzazione potrebbero impedire la comparsa della pagina, controllare quindi sullo spazio di lavoro l'apertura di una nuova finestra del browser web. == Ottenere uno stack trace == Se per una qualsiasi ragione apport non sia abilitato sul vostro sistema oppure avete un problema riproducibile, vi chiediamo di investigare spiegandovi come ottenere uno stack trace in modo da ispezionare le variabili interne. Assicurasi di avere installato i [[https://wiki.ubuntu.com/DebuggingProgramCrash#Hardy 8.04 and Newer|debugging symbols]] per i pacchetti compiz, nux ed unity. Altrimenti, da tty1 (Ctrl + Alt + F1) {{{ $ unity --advanced-debug GNU gdb (GDB) 7.2-ubuntu Copyright (C) 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i686-linux-gnu". For bug reporting instructions, please see: ... (gdb) set logging file unity.log (gdb) set logging on (gdb) b _exit Function "_exit" not defined. Make breakpoint pending on future shared library load? (y or [n]) [Rispondere yes (y)] (gdb) run [ e quando avviene il crash di compiz/unity eseguire...] (gdb) bt full [ quindi CTRL-D o riavviare compiz per continuare il lavoro ] (gdb) run }}} È anche possibile ottenere una traccia con valgrind eseguendo {{{valgrind compiz --replace &}}} in un terminale. Questo sistema è un po' più lento poichè esegue compiz sotto emulazione ma consente di ottenere maggiori informazioni di quelle avute tramite gdb. In circostanze estreme potrebbe esservi richiesto di utilizzare un plugin gestore di crash scaricabile da [[http://git.compiz.org/compiz/plugins/crashhandler|git]] ed abilitarlo in ccsm. Se si è afflitti da un freeze, ma è possibile utilizzare Ctrl-Alt-F1 per ottenere TTY1, è possibile usare gdb per connettere il processo compiz in esecuzione ed ottenere una traccia. Questa informazione è utilissima per il debugging del problema. Per connettere il processo in esecuzione, andare su TTY1 e seguire le seguenti istruzioni: {{{ $ sudo gdb compiz `pgrep compiz` (gdb) set logging file unity.log (gdb) set logging on (gdb) bt full [ quindi CTRL-D o riavviare compiz per continuare il lavoro ] (gdb) run }}} È quindi possibile ritornare ad Unity premendo Ctrl-Alt-F7. = Istruzioni per il triage = == Procedure operative standard == La mancata osservanza di queste semplici linee guida potrebbe causare seri danni alle mani di lamalex e didrocks. === Mantenenre gli stati Upstream e Downstream sincronizzati === Il flusso di lavoro upstream e downstream per un'esperienza desktop è leggermente differente dagli altri progetti. Siccome non esiste alcuna distro che produce patch per i progetti di esperienze desktop, i bugs sono una frazione estremamente piccola di quelli segnalati. Per questa ragione il flusso di lavoro è il seguente: 1. Assicurarsi che il bug sia segnalato sia upstream che downstream. 2. Mantenere i due status sincronizzati. * Upstream è il pricipale. Sincronizzare lo status downstream come quello upstream. * Quì l'eccezione è per i pacchetti che vengono fixati downstream. Occasionalmente un fix potrà essere preso da un codice di esperienza desktop non ancora rilasciato e pacchettizzato per fixare un problema con status critical. In questo caso non si deve sincronizzare lo status upstream a quello downstream. === Marcare i componenti afflitti === Spesso, durante il triage di un bug, capita che il problema risieda in un componente base. Se ciò dovesse verificarsi è imperativo aprire la segnalazione anche contro il componente base. Se ad esempio un bug in nux fa crashare unity dovremo segnalare, nello stesso report, che il bug affligge sia unity che nux, syncronizzando i due status riferendoci a nux come principale. Per fare ciò utilizzare la funzione 'Also afflict project Similmente, se un bug è riportato contro un progetto componente, una segnalazione dovrà essere aperta anche contro il super progetto, nella medesima pagina. Per esempio, se un reporter apre una segnalazione contro nux, bamf, dee, etc. una segnalazione deve essere aperta anche contro unity in modo da avere traccia di tutti i componenti affetti in un unica pagina. == Bugs inerenti il design == Alcuni bugs non sono difetti tecnici, bensì comportamentali o visuali. Questi spesso richiedono valutazioni da parte del design team prima di essere corretti. Quando si è stabilito che un bug è un bug di design deve essere segnalato anche contro ''Ayatana design'' e lo status relativo ad unity deve essere impostato ad ''incomplete'' con l'aggiunta del tag ''needs design''. Dopo che il team design si sarà pronunciato in merito lo status di unity potrà essere cambiato in ''Triaged'' dato che contiene tutte le informazioni necessarie agli sviluppatoriche dovranno fixare il bug. Vedi anche la risposta precompilata ''Bloccato in atttesa di decisione del team design''. Un esempio concreto di bug nel design: [[https://bugs.launchpad.net/unity/+bug/649560]] == Risposte precompilate == || '''Situazione''' || '''Risposta''' || '''Note''' || || L'autore della patch non ha sottoscritto il 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. || || || Bloccato in atttesa di decisione del team design || 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. || Marcare lo status come ''incomplete'', aggiungere il tag ''needs-design'' fino alla risposta dal team design || || bug in Unity funzionante su clutter || 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. || impostare il bug come WONTFIX, e lasciare che l'utente lo riapra || || Bugs che non sembrano affatto correlati ad Unity || 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 per i quali è necessaria una 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? || || = Tags dei bug = Queste tags consentono di isolare i bugs in sottogruppi, fornendo un facile e veloce sistema per lavorare su uno specifico problema. || '''Tag''' || '''Use case''' || || [[https://launchpad.net/ubuntu/+source/compiz/+bugs?field.tag=unity|`unity`]] || Bugs in Compiz che affliggono Unity || || [[https://launchpad.net/ubuntu/+bugs?field.tag=running-unity|`running-unity`]] || Bugs segnalati quando Unity è in esecuzione || || [[https://launchpad.net/unity/+bugs?field.tag=bitesize|`bitesize`]] || Piccoli bugs che possone essere l'ideale per nuovi contributori. || || [[https://launchpad.net/unity/+bugs?field.tag=needs-design|`needs-design`]] || Un bug che necessita un UI design. || || ... || ... || = Testare un fix = Talvolta uno sviluppatore potrebbe richiedere di testare una veloce patch chiedendovi: check the [[https://launchpad.net/~unity/+archive/daily|Daily builds PPA]] per valutare se il problema è stato risolto in una versione aggiornata di Unity. Siate cauti nel fare ciò dato che questi sono rilasci giornalieri che potrebbero danneggiare altre parti del sistema e sono da considerarsi instabili. Meglio testare su macchine virtuali. = Bugs noti = Bugs noti o funzioni mancanti sono tracciati in Launchpad ed assegnati a milestones per indicare quando è pianificato il loro fixing o rilascio. * Milestones di Unity: https://bugs.launchpad.net/unity/+milestones * https://launchpad.net/unity/+milestone/3.4 - milestones di ubuntu * https://launchpad.net/unity/+milestone/3.4.4 - milestones settimanali * https://launchpad.net/unity/+milestone/3.4.4 * https://launchpad.net/unity/+milestone/3.6 * https://launchpad.net/unity/+milestone/3.8 ------ [[https://wiki.ubuntu.com/Unity/FilingBugs|Documento originale]] ---- CategoryBugSquad CategoryDesktopTeam CategoryDebugging From noreply at ubuntu.com Sun May 6 19:39:06 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 06 May 2012 19:39:06 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingAyatana=5Fit=22_by_fabi?= =?utf-8?q?omarconi?= Message-ID: <20120506193906.16002.59433@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingAyatana_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/DebuggingAyatana_it New page: ##Traduzione debugging Ayatana https://wiki.ubuntu.com/DebuggingProcedures Il progetto [[https://wiki.ubuntu.com/Ayatana|Ayatana]] consiste in molti sottoprogetti di diversa natura. Tuttavia, poiché è sviluppato all'interno del progetto stesso da parte dello stesso gruppo di persone all'interno della medesima società e siccome condividono componenti è possibile dare alcuni consigli generali sul debugging di Ayatana. <> = informazioni generali = Questa sezione fornisce informazioni generiche sui vari progetti che costituiscono [[https://wiki.ubuntu.com/Ayatana|Ayatana]]. == Cos'è? == Il progetto contenitore di Ayatana in Launchpad è ''[[https://launchpad.net/ayatana|ayatana]]'' ed in virtù di ciò non si potranno aprire segnalazioni contro tutto il progetto, bensì, quando si utilizzano i pacchetti di Ubuntu, occorrerà fare riferimento ai pacchetti sorgente dei pacchetti in Launchpad. || '''Proprio progetto Launchpad''' ||'''Pacchetto sorgente Ubuntu'''|| '''Descrizione''' || || [[https://launchpad.net/indicator-application|Application Indicator]] ||''[[https://launchpad.net/ubuntu/+source/indicator-application|indicator-application]]''|| L'indicatore che mostra gli indicatori delle applicazioni, così come la libreria che consente alle applicazioni di registrare i loro indicatori delle applicazioni. || || [[https://launchpad.net/indicator-appmenu|Application Menu]] ||''[[https://launchpad.net/ubuntu/+source/indicator-appmenu|indicator-appmenu]]''|| l'indicatore che ospita i menu estratti dalle applicazioni che usano ''appmenu-gtk'' e ''appmenu-qt''. || || [[https://launchpad.net/appmenu-gtk|AppMenu GTK+]] ||''[[https://launchpad.net/ubuntu/+source/appmenu-gtk|appmenu-gtk]]''|| Il modulo GTK+ che fa apparire i menu nel applicazione del pannello ''indicator-appmenu'', utilizzando {{{GtkMenuProxy}}}.|| || [[https://launchpad.net/bamf|BAMF]] ||''[[https://launchpad.net/ubuntu/+source/bamf|bamf]]''|| Fornisce un demone DBus ed una libreria C per le istanze di accoppiamento applicazione/finestra. Utilizzato da Unity per garantire che ogni applicazione appaia una sola volta nel lanciatore. || || [[https://launchpad.net/clutk|Clutter Toolkit]] ||''[[https://launchpad.net/ubuntu/+source/clutk|clutk]]''|| Una libreria toolkit Clutter utilizzata dal lanciatore in Unity. || || [[https://launchpad.net/indicator-datetime|Date and Time Indicator]] ||''[[https://launchpad.net/ubuntu/+source/indicator-datetime|indicator-datetime]]''|| L'indicatore che ha sostituito l'applicazione orologio e che mostra data, ora ed un calendario. || || [[https://launchpad.net/dbusmenu|DBus Menu]] ||''[[https://launchpad.net/ubuntu/+source/libdbusmenu|libdbusmenu]]''|| Libreria per passare i {{{GtkMenus}}} su DBus. Utilizzata da quasi tutti i progetti indicatore. || || [[https://launchpad.net/evolution-indicator|Evolution Indicator]] ||''[[https://launchpad.net/ubuntu/+source/evolution-indicator|evolution-indicator]]''|| Utilizza {{{libindicate}}} per visualizzare una voce per Evolution nel menu messaggi. || || [[https://launchpad.net/indicator-applet|Indicator Applet]] ||''[[https://launchpad.net/ubuntu/+source/indicator-applet|indicator-applet]]''|| L'applicazione che contiene i più importanti indicatori. || || [[https://launchpad.net/libdbusmenu-qt|libdbusmenu-qt]] ||''[[https://launchpad.net/ubuntu/+source/libdbusmenu-qt|libdbusmenu-qt]]''|| Mentre la normale libreria DBus Menu è per il passaggio di {{{GtkMenus}}} su DBus, questa libreria è utilizzata per passare i menu QT su DBus. || || [[https://launchpad.net/libindicate|Libindicate]] ||''[[https://launchpad.net/ubuntu/+source/libindicate|libindicate]]''|| La libreria utilizzata dalle applicazioni per apparire nel menu messaggiThe library used by applications to appear in the Messaging Menu, anche se teoricamente può essere utilizzata anche per altri scopi. || || [[https://launchpad.net/libindicate-qt|libindicate-qt]] ||''[[https://launchpad.net/ubuntu/+source/libindicate-qt|libindicate-qt]]''|| I bindings QT per {{{libindicate}}}. || || [[https://.launchpad.net/libindicator|libindicator|Libindicator]] ||''[[https://launchpad.net/ubuntu/+source/libindicator|libindicator]]''|| La libreria per la creazione di indicatori, pertanto usata da tutti gli indicatori.The library for creating indicators, therefore used by all indicators. utilizzata anche da Indicator Applet e Session Menu per raggruppare gli indicatori che che si vogliono visualizzare partendo da una lista statica. || || [[https://launchpad.net/indicator-me|Me Menu]] ||''[[https://launchpad.net/ubuntu/+source/indicator-me|indicator-me]]''|| L'indicatore che mostra il nome utente e provvede all'integrazione degli account chat ed ha voci per l'aggiornamento dello status microblogging. || || [[https://launchpad.net/indicator-network|Network Menu]] ||''[[https://launchpad.net/ubuntu/+source/indicator-network|indicator-network]]''|| Il gestore connessioni basato sull'indicatore network, ha sostituito nm-applet. Per ora utilizzato solo in Ubuntu Netbook Edition. || || [[https://launchpad.net/notify-osd|Notify OSD]] ||''[[https://launchpad.net/ubuntu/+source/notify-osd|notify-osd]]''|| Il demone delle notifiche dal progetto Ayatana || ||[[https://launchpad.net/plasma-widget-menubar|Plasma Menu Bar]] ||''[[https://launchpad.net/ubuntu/+source/plasma-widget-menubar|plasma-widget-menubar]]''|| La barra menu plasma che mostra i menu applicazione, estratta sia da applicazioni appmenu-gtk o appmenu-qt, prima che siano esportate su DBus. || || [[https://launchpad.net/indicator-sound|Sound Menu]] ||''[[https://launchpad.net/ubuntu/+source/indicator-sound|indicator-sound]]''|| L'indicatore per variare il volume o controllare il player musicale. || || [[https://launchpad.net/unity|Unity]] ||''[[https://launchpad.net/ubuntu/+source/unity|unity]]''|| L'interfaccia Ubuntu Netbook Edition che fornisce un lanciatore, un pannello superiore ud una interfaccia di ricerca. Non usa l'Indicator Applet, implementando un proprio visualizzatore. Utilizza {{{libbamf}}} e {{{libclutk}}}.|| === Una nota su Indicator Applet === Indicator Applet è l'applicazione che visualizza tutti gli indicatori nel pannello. Non è limitato solo al menu messaggi ma si estende aanche agli indicatori applicazione e il menu audio. L'applicazione ''indicator-applet'' include solo questi tre, Session Indicator e Me Menu sono mostrati come un applicazione separata: ''indicator-session''. L'applicazione che li comprende tutti è: ''indicator-applet-complete'', che include sia ''indicator-applet'' che ''indicator-session''. Ricordare che un bug deve essere segnalato innanzitutto contro il proprio indicatore, mentre contro Indicator Applet solamente quando si è assolutamente sicuri che il problema risiede li. == Dove cercare informazioni == L'autenticazione della sessione utente avviene in {{{$XDG_CACHE_HOME}}}, predefinitivamente in {{{$HOME/.cache}}} o {{{~/.cache}}}. In questa directory vi sono molti file interessanti, relativi al progetto [[https://wiki.ubuntu.com/Ayatana|Ayatana]]: * indicator-applet.log * indicator-applet-appmenu.log * indicator-applet-complete.log * indicator-applet-session.log * notify-osd.log Nella directory {{{$XDG_CACHE_HOME/indicators/}}} sono depositati i collegamenti ai file desktop registrati da Message Indicator e Sound Menu, rispettivamente in {{{$XDG_CACHE_HOME/indicators/messages/seen-db.keyfile}}} e {{{$XDG_CACHE_HOME/indicators/sound/familiar-players-db.keyfile}}}. Mentre per Application Indicators, sono situati in {{{$XDG_CONFIG_HOME/indicators/application/lru-file.json}}}. == Osservando DBus == Il progetto Ayatana fa un uso intensivo di DBus per comunicare. È quindi consigliabile controllare le comunicazioni di DBus per analizzare meglio cosa sta succedendo. Per osservare in diretta le comunicazioni di DBus usare il comando: {{{ dbus-monitor --session }}} Con il succitato comando, si potranno osservare anche le comunicazioni di altre applicazioni che stanno usando DBus, per evitare ciò è necessario specificare quali informazioni si vogliono. Per visualizzare solamente le comunicazioni su DBus derivanti da {{{org.ayatana.indicator.application.service}}} DBus interface ,che praticamente sono tutte comunicazioni fra il registro di Application-Indicators e l'attuale indicatore di Application-Indicators, usare il comando: {{{ dbus-monitor "interface='org.ayatana.indicator.application.service'" --session }}} Se invece si vuole visualizzare la comunicazione fra l'applicazione ed il registro Application Indicators usare il comando: {{{ dbus-monitor "interface='org.kde.StatusNotifierItem'" --session }}} ---- [[https://wiki.ubuntu.com/DebuggingAyatana|Documento originale]] CategoryBugSquad CategoryAyatana CategoryDebugging From noreply at ubuntu.com Sun May 6 19:40:08 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 06 May 2012 19:40:08 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingAyatana=5Fit=22_by_fabi?= =?utf-8?q?omarconi?= Message-ID: <20120506194008.16038.74129@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingAyatana_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/DebuggingAyatana_it?action=diff&rev1=1&rev2=2 Comment: Italian translation ##Traduzione debugging Ayatana https://wiki.ubuntu.com/DebuggingProcedures Il progetto [[https://wiki.ubuntu.com/Ayatana|Ayatana]] consiste in molti sottoprogetti di diversa natura. Tuttavia, poiché è sviluppato all'interno del progetto stesso da parte dello stesso gruppo di persone all'interno della medesima società e siccome condividono componenti è possibile dare alcuni consigli generali sul debugging di Ayatana. - <> + = informazioni generali = Questa sezione fornisce informazioni generiche sui vari progetti che costituiscono [[https://wiki.ubuntu.com/Ayatana|Ayatana]]. - == Cos'è? == + == Cosa è ? == Il progetto contenitore di Ayatana in Launchpad è ''[[https://launchpad.net/ayatana|ayatana]]'' ed in virtù di ciò non si potranno aprire segnalazioni contro tutto il progetto, bensì, quando si utilizzano i pacchetti di Ubuntu, occorrerà fare riferimento ai pacchetti sorgente dei pacchetti in Launchpad. || '''Proprio progetto Launchpad''' ||'''Pacchetto sorgente Ubuntu'''|| '''Descrizione''' || From noreply at ubuntu.com Sun May 6 19:49:18 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 06 May 2012 19:49:18 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingAyatana=22_by_fabiomarc?= =?utf-8?q?oni?= Message-ID: <20120506194918.16032.28034@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingAyatana" page has been changed by fabiomarconi: http://wiki.ubuntu.com/DebuggingAyatana?action=diff&rev1=6&rev2=7 #language en #title Debugging Ayatana + Available languages :[[https://wiki.ubuntu.com/DebuggingAyatana_it|Italiano]], + <> + ----- - == Available languages == - [[https://wiki.ubuntu.com/DebuggingAyatana_it|Italiano]], - The [[Ayatana]] project concerns several sub-projects of a diverse nature. However, because it is developed within the same project by the same group of people within the same company and because they share components it is possible to give some general advise on debugging for results of Ayatana. ||<>|| From noreply at ubuntu.com Sun May 6 20:05:23 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 06 May 2012 20:05:23 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingEmacs=22_by_fabiomarcon?= =?utf-8?q?i?= Message-ID: <20120506200523.21188.2168@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingEmacs" page has been changed by fabiomarconi: http://wiki.ubuntu.com/DebuggingEmacs?action=diff&rev1=10&rev2=11 + Available languages : [[https://wiki.ubuntu.com/DebuggingEmacs_it| Italiano]], <> - Available languages : [[https://wiki.ubuntu.com/DebuggingEmacs_it| Italiano]], ||'''Contents'''<
><>|| = Introduction = From noreply at ubuntu.com Sun May 6 20:16:27 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 06 May 2012 20:16:27 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingEvince=5Fit=22_by_fabio?= =?utf-8?q?marconi?= Message-ID: <20120506201627.21194.46107@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingEvince_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/DebuggingEvince_it New page: ##Traduzione debugging Evince = Introduzione = [[http://gnome.org/projects/evince/|Evince]] in Ubuntu è l'applicazione predefinita per visualizzare file .pdf, .ps, .djvu ed altri tipi similari. La maggior parte dei bug relativi ad Evince ricadono in tre categorie: 1. Evince crasha quando viene aperto uno specifico documento (oppure quando si esegue una specifica azione, quale lo scorrimento, lo zoom, la rotazione). 1. Evince non visualizza correttamente il documento. 1. Evince visualizza il documento ma non lo stampa correttamente. = Problemi comuni = == File .dvi == Evince utilizza texlive per renderizzare i file .dvi. Se non si riesce ad aprire un file .dvi (messaggio d'errore "Impossibile aprire il documento. Il formato .DVI non è corretto"), installare il pacchetto '''texlive''' e riprovare. (Vedere [[https://bugs.launchpad.net/ubuntu/+source/evince/+bug/42410|bug report #42410]] inerente la correzione di questo errore) == CJK fonts == CJK sta per Chinese-Japanese-Korean. Un pdf che include testo ma mancano i font incorporati non sarà visualizzato correttamente fino a quando non sarà installato il pacchetto '''poppler-data'''. = Procedura di debugging = == Crash o Freeze == In caso di crash di Evince, seguire le procedure standard [[DebuggingProgramCrash]]. == Problemi di visualizzazione == Se un crash o una cattiva visualizzazione avvengono solo con uno specifico documento è necessario poterlo analizare. In seguito la risposta standard da usare in questo caso: '''Inglese''' {{{ Thank you for taking the time to report this bug and helping to make Ubuntu even better! It would be quite helpful if you attach the document you are having a problem with so we can better recreate this bug and work on fixing it. Thanks in advance. }}} Una volta ottenuto il documento e verificato che il problema sussite, bisogna cercare il pacchetto affetto dal bug. Evince utilizza: * [[http://poppler.freedesktop.org/|libpoppler]] per visualizzare i file pdf * [[http://libspectre.freedesktop.org/|libspectre]] per visualizzare i file postscript * [[http://www.pango.org/|libpango]], [[http://www.freetype.org/|libfreetype]] e [[http://fontconfig.org/|fontconfig]] per la scelta dei font e la visualizzazione * [[http://cairographics.org/|libcairo]] per la grafica vettoriale 2D Provare ad aprire il documento con altri visualizzatori per cercare di isolare il problema: * Adobe Reader (pacchetto '''acroread''', scaricabile dal repository [[http://medibuntu.org/|Medibuntu]]) * Xpdf (pacchetto '''xpdf-reader''') * ePdfView * okular * per i file .ps: ghostscript * per i file .djvu: djVuLibre (pacchetto '''djview4''') Quando un file pdf non include i font incorporati usati nel documento, quindi se Ubuntu non ha lo specifico font installato, cercherà l'equivalete più simile utilizzando '''fc-match '''. Può anche essere utile usare gli strumenti '''pdfinfo''' e '''pdffonts''' (inclusi nel pacchetto poppler-utils). == Problemi di stampa == Talvolta, se la stampa di un documento da Evince non avviene correttamente, non è un problema in Evince ma piuttosto in cups o altri specifici driver della stampante. = Altri problemi = == Come avanzare == * I bug di Evince vengono inviati upstream a http://bugzilla.gnome.org/browse.cgi?product=evince * I bug di Poppler vengono inviati upstream a http://bugs.freedesktop.org/query.cgi == Riporto dei fix == I pacchetti riparati, sono generalmete riportati a tutti i rilasci di Ubuntu ancora supportati (è possibile vedere quali versioni sono ancora supportate [[http://en.wikipedia.org/wiki/List_of_Ubuntu_releases#Release_history|qui]]). Purtroppo ciò non è sempre possibile, se ad esempio l'architettura del codice è cambiata significativamente. Ciò significa che talvolta una segnalazione è marcata come "Fix Released" anche se il problema è stato risolto solo nelle versioni recenti di evince/poppler/ecc. ---- CategoryDebugging CategoryBugSquad From noreply at ubuntu.com Sun May 6 20:18:56 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 06 May 2012 20:18:56 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingEvince=5Fit=22_by_fabio?= =?utf-8?q?marconi?= Message-ID: <20120506201856.21218.25975@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingEvince_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/DebuggingEvince_it?action=diff&rev1=1&rev2=2 Se un crash o una cattiva visualizzazione avvengono solo con uno specifico documento è necessario poterlo analizare. In seguito la risposta standard da usare in questo caso: - '''Inglese''' - {{{ - Thank you for taking the time to report this bug and helping to make Ubuntu even better! It would be quite helpful if you attach the document you are having a problem with so we can better recreate this bug and work on fixing it. Thanks in advance. + ''Thank you for taking the time to report this bug and helping to make Ubuntu even better! It would be quite helpful if you attach the document you are having a problem with so we can better recreate this bug and work on fixing it. Thanks in advance.'' - }}} + Una volta ottenuto il documento e verificato che il problema sussite, bisogna cercare il pacchetto affetto dal bug. Evince utilizza: * [[http://poppler.freedesktop.org/|libpoppler]] per visualizzare i file pdf From noreply at ubuntu.com Sun May 6 20:24:04 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 06 May 2012 20:24:04 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingEvince=5Fit=22_by_fabio?= =?utf-8?q?marconi?= Message-ID: <20120506202404.21206.97241@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingEvince_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/DebuggingEvince_it?action=diff&rev1=2&rev2=3 ##Traduzione debugging Evince - + <> = Introduzione = [[http://gnome.org/projects/evince/|Evince]] in Ubuntu è l'applicazione predefinita per visualizzare file .pdf, .ps, .djvu ed altri tipi similari. From noreply at ubuntu.com Sun May 6 20:25:05 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 06 May 2012 20:25:05 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingEvince=5Fit=22_by_fabio?= =?utf-8?q?marconi?= Message-ID: <20120506202505.21109.56598@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingEvince_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/DebuggingEvince_it?action=diff&rev1=3&rev2=4 ##Traduzione debugging Evince - <> + ||<>|| + = Introduzione = [[http://gnome.org/projects/evince/|Evince]] in Ubuntu è l'applicazione predefinita per visualizzare file .pdf, .ps, .djvu ed altri tipi similari. From noreply at ubuntu.com Mon May 7 08:05:16 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 07 May 2012 08:05:16 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingKeyboardDetection=22_by?= =?utf-8?q?_penalvch?= Message-ID: <20120507080516.12531.26808@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingKeyboardDetection" page has been changed by penalvch: http://wiki.ubuntu.com/DebuggingKeyboardDetection?action=diff&rev1=15&rev2=16 Comment: Removed LaptopTestingTeam/HotkeyResearch link as it is an empty article ||<>|| = Introduction = - - If you have a laptop and the hotkeys don't work please follow the steps described here: LaptopTestingTeam/HotkeyResearch. Problems with keyboard detection typically fall into one off these categories: 1. Your keyboard doesn't work at all. From noreply at ubuntu.com Mon May 7 13:33:28 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 07 May 2012 13:33:28 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingProgramCrash=5Fit=22_by?= =?utf-8?q?_fabiomarconi?= Message-ID: <20120507133328.4661.80667@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingProgramCrash_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/DebuggingProgramCrash_it Comment: Italian translation New page: <> ||<>|| Questo documento spiega come installare i pacchetti di debug in Ubuntu che forniranno utili informazioni inerenti l'anomalia. == Paccheti contenenti i simboli di debug == Innanzitutto verificare se esiste, nei repository main, un pacchetto equivalente ma con sufffisso -dbg. Questi sono i pacchetti contenenti i siboli di debug ed equivalgono a '-dbgsym' descritto più avanti.bed below. È possibile usare in tutta sicurezza il pacchetto di debuging, ma non entrambi contemporaneamente. Provare ad installare il pacchetto aggiungendo -dbg al suo nome, per esempio: {{{ sudo apt-get install xserver-xorg-core-dbg }}} se il pachetto in questione è ''xserver-xorg-core''. Altrimenti se il pacchetto -dbg non esiste: 1. Creare un `/etc/apt/sources.list.d/ddebs.list` eseguendo la seguente linea in un terminale: {{{ echo "deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe multiverse" | \ sudo tee -a /etc/apt/sources.list.d/ddebs.list }}} 1. I rilasci stabili (non alpha e beta) richiedono l'aggiunta di altre tre linee al medesimo file, quindi eseguire il seguente comando nel terminale: {{{ echo "deb http://ddebs.ubuntu.com $(lsb_release -cs)-updates main restricted universe multiverse deb http://ddebs.ubuntu.com $(lsb_release -cs)-security main restricted universe multiverse deb http://ddebs.ubuntu.com $(lsb_release -cs)-proposed main restricted universe multiverse" | \ sudo tee -a /etc/apt/sources.list.d/ddebs.list }}} È possibile anche aggiungere queste linee usando Ubuntu Software Center: * Avviare ''Software Center'' e nella barra superiore scegliere ''Modifica'' -> ''Sorgenti Software''. * Choose ''Software Sources'' or ''Repositories'' via the ''Settings'' menu, and click on the ''Third-Party Software'' tab. * Scegliere ''Altro software'' -> ''Aggiungi'' ed inserire le tre linee una alla volta. 1. Importare l'archivio dei simboli di debug tramita chiave: {{{ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 428D7C01 }}} 1. Quindi eseguire {{{ sudo apt-get update }}} per aggiornare la vostra lista di pacchetti. 1. I pacchetti con i simboli di debug hanno il suffisso '-dbgsym' quindi per installare il pacchetto 'yelp' si dovrà eseguire: {{{ apt-cache policy yelp }}} Ciò mostrerà la versione attualmente installata (si userà 2.22.1-0ubuntu2.8.04.1 in questo esempio). '''NOTA:''' 'yelp' [che è il nome del pacchetto per "Aiuto e Supporto"] è ''solo un esempio'' e '''non''' e non una parte del comando: 'yelp' è usato solamente per mostrare la procedura. Si dovra cambiare 'yelp' con il nome del pacchetto di cui si vuole il debug. 1. Installazione dei simboli di debug: {{{ sudo apt-get install yelp-dbgsym=2.22.1-0ubuntu2.8.04.1 }}} È anche possibile usare Ubuntu Software Center e cercare 'yelp-dbgsym' ed installarlo da lì. La procedura sopra descritta installerà la simbologia di debug per il solo pacchetto 'yelp'. Potrebbe però accadere che il pacchetto yelp utilizzi delle librerie condivise in altri pacchetti, sarà quindi necessario dover installare anche la simbologia di debug anche per quei pacchetti per avere uno stacktrace utilizzzabile. Per ovviare scaricare lo script [[attachment:list-dbgsym-packages-v2.sh]] ed eseguirlo (dopo un chmod a+x list-symbols-packages-v2.sh) in questo modo: /!\ aggiornare [[attachment:list-dbgsym-packages-v2.sh]] a list-symbols-packages-v2.sh. Questo è il primo passo per renderlo compatibile con il nuovo GDB (che per impostazine predefinita non carica più tutte le librerie all'avvio). -v2 attualmente funziona solo in rapporto ad un binario attualmente in esecuzione (es., con '-p $(pidof ') {{{ bash list-symbols-packages-v2.sh yelp }}} per ottenere una lista completa di pacchetti da installare. Lo script può anche essere aggregato ad un processo in esecuzione ed in questo caso, raccomandabile, si avrà una lista ancora più completa di pacchetti da installare, semprechè il vostro problema non vi impedisca l'esecuzione del programma. È possibile ottenere l'ID di un processo tramite pidof, cos' mentre si avrà yelp in esecuzione si potrà eseguire: {{{ bash list-symbols-packages-v2.sh -p $(pidof -s yelp) }}} per ottenere una lista di pacchetti utile a fornire le migliori informazioni di debug. Se il proceso in esecuzione è un server (demone), sarà necessario eseguire 'list-symbols-packages.sh' con sudo. a. Ora è possibile ottenere una [[Backtrace]]. a. Oppure anche eseguire [[Valgrind]], se il programma crasha con un errore di segmentazione "Segmentation fault" o un errore di bus "Bus error". a. Opzionalmente, vi potrà essere richiesto di produrre una [[Strace]]. a. È sempre utile fornire il file : '''~/.xsession-errors''' === Come rimuovere tutto ciò e tornare ad un sistema normale dopo aver fornito la traccia? === È possibile rimuovere tutti i simboly di debug ed i repository ddebs con il seguenti comandi: {{{ sudo apt-get remove \.*-dbgsym sudo rm /etc/apt/sources.list.d/ddebs.list sudo apt-get update }}} === Riferimenti === * Announcement: https://lists.ubuntu.com/archives/ubuntu-devel-announce/2006-September/000195.html == Il server Xorg == Il server X, in maniera predefinita, intrappola i soui crash e dump in una stack trace in /var/log/Xorg.0.log. Tuttavia, questo stack viene modificato dal gestore di segnale stesso. Per ottenere un crash "normale" che attiverà un core dump (e segnalazione da parte di "Apport"), aggiungere al file /etc/X11/xorg.conf: {{{ Section "ServerFlags" Option "NoTrapSignals" "true" EndSection }}} Vi preghiamo di fare riferimento a debug Xorg server crashes. == Info for the BugSquad == If you're trying to `apport-retrace` a crash report from a bug that didn't happen on the same Ubuntu release as the one you're running, do the following: Say that you're running `Gutsy` and the crash happened on `Feisty`: 0. This will create a minimal `feisty` system. {{{ sudo mkdir -p /chroots/feisty sudo debootstrap feisty /chroots/feisty/}}} 0. Now you change into this minimal `feisty` system. {{{ sudo chroot /chroots/feisty}}} 0. edit `/etc/apt/sources/list` and all the repositories you need, especially Martin's ddeb repository. 0. {{{ apt-get update; apt-get install gdb apport}}} 0. use `apport-retrace` as you're used to. For more information on dealing with bug reports [[Apport]] see [[Bugs/ApportRetraces]]. ---- CategoryBugSquad CategoryDebugging From noreply at ubuntu.com Sun May 6 19:43:46 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 06 May 2012 19:43:46 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingAyatana=22_by_fabiomarc?= =?utf-8?q?oni?= Message-ID: <20120506194346.16032.89022@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingAyatana" page has been changed by fabiomarconi: http://wiki.ubuntu.com/DebuggingAyatana?action=diff&rev1=5&rev2=6 #language en #title Debugging Ayatana <> + + == Available languages == + [[https://wiki.ubuntu.com/DebuggingAyatana_it|Italiano]], The [[Ayatana]] project concerns several sub-projects of a diverse nature. However, because it is developed within the same project by the same group of people within the same company and because they share components it is possible to give some general advise on debugging for results of Ayatana. From noreply at ubuntu.com Sun May 6 20:03:12 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 06 May 2012 20:03:12 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingEmacs=5Fit=22_by_fabiom?= =?utf-8?q?arconi?= Message-ID: <20120506200312.21200.95074@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingEmacs_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/DebuggingEmacs_it Comment: Italian translation New page: ## traduzione Debugging emacs = Introduzione = Esistono molteplici pacchetti di Emacs, collettivamente chiamati "Emacsen". Dipendono tutti da un pacchetto chiamato `emacsen-common` e sono divisi in versioni. Le versioni principali sono GNU Emacs (ossia Emacs FSF; `emacs23` ed `emacs-snapshot`) e `xemacs21`. A loro volta sono divisi in più pacchetti, al fine di separare i componenti generici (per i quali un solo pacchetto è necessario) da quelli che dipendono dall'architettura del sistema e componenti consigliati tra quelli opzionali. Se si desidera una versione Emacs, attualmente la più cosigliata e quella stabile, GNU Emacs (attualmente `emacs23`). `emacs-snapshot` contiene una versione relativamente recente e non rilasciata versione dei sorgenti di sviluppo, ma è anche possibile ottenere versioni più recenti da un PPA o da altre risorse. `xemacs21` è la versione più vecchia ed oramai non molto attivamente supportata. Sono disponibile una moltitudine di pacchetti aggiuntivi, molti dei quali supportati in tutte le versioni, ed alcuni che forniscono nuovi e/o differenti versioni dei componenti normalmente inclusi in una installazione base, ad esempio Gnus. = Procedura di debugging = Se Emacs non funziona a dovere, provare ad eseguire `emacs -Q` per vedere se il problema svanisce. Questa istruzione disabilita la lettura del proprio file `.emacs` ed altre modifiche locali. Se il problema svanisce è dovuto a qualche personalizzazione locale. Se si riceve un messaggio di errore da parte di Emacs, è possibile ottenere una traccia che mostri quali funzioni Lisp venivano processate al momento dell'errore. Abilitare il tracciamento con il comando `M-: (setq debug-on-error t)` ed allegare il file `*Backtrace*` alla segnalazione. == Errori dovuti all'installazione di pacchetti == Un apparente errore di Emacs è spesso dovuto all'installazione di qualche pacchetto aggiuntivo che contiene un bug o è incompatibile con la versione di Emacs installata. Se `dpkg` riferisce un messaggio di errore indicante che il pacchetto `postinst` ha fallito, L'attuale messaggio d'errore è probabilmente poche linee prima di questo messaggio di `dpkg`. == Errori Byte-compilation == Un particolare tipo di errore durante l'installazione è il byte-compilation error. Con `emacs22` ed `emacs-snapshot` il log nel terminal conterrà un messaggio come questo: `!! Byte-compilation for <> failed!`<
> `!! This indicates a bug in one of the add-on packages`<
> `!! installed on your system, or a bug in Emacs itself.`<
> `!! Please file a bug report against <>`<
> `!! and attach the file /tmp/<>.<>` Il nome del file sarà differente ogni volta. Questo file è necessario per l'analisi del problema. = Come segnalare bug = È possibile segnalare bug contro Emacs utilizzando Apport. Esiste anche lo strumento `M-x emacs-bug-report` ma non è completamente adattato per l'invio di segnalazioni ad Ubuntu. = Bug tags = (Developers: please update this section) = Come eseguire il Triage = I bug riconosciuti da Apport sono generalmente dovuti a pacchetti che hanno fallito l'installazionee solitamente includono allegati i file DpkgTerminalLog o VarDistUpgradeTermLog; Questi file sono i primi da esaminare. Molto probabilmente conterranno un messaggio d'errore, circa alla fine, che indicherà quale pacchetto ha fallito l'installazione e perchè. Se questo file è mancante, deve essere richiesto. Vedere una delle seguenti risposte precompilate. Se il messaggio indica un errore di byte-compilation in un pacchetto aggiuntivo (vedi sopra), il file temporaneo nel messaggio d'errore deve essere allegato alla segnalazione, se non lo è deve essere richiesto. Vedere una delle seguenti risposte precompilate. == Risposte generiche == '''TODO''' How to produce and attach a backtrace === Log del terminale mancante === ||Grazie per avere segnalato questo bug che ci aiuta a rendere Ubuntu migliore. Per poter analizzare questo problema è necessario allegare alla segnalazione il contenuto del file /var/log/apt/term.log.Ricordiamo che normalmente è necessario l'uso dei privilegi sudo per leggere o copiare questo file.<
><
>Se questo errore si è verificato durante un avanzamento di versione di ubuntu, il file da allegare sarà /var/log/dist-upgrade/apt-term.log<
><
>Ringraziamo anticipatamente!|| === Log Byte Compilation mancante === ||Se avete ancora questo file nel vostro sistema, vi preghiamo di allegarlo a questa segnalazione. Comunque i file nella directory /tmp vengono cancellati al riavvio; se il file è stato rimosso, è necessario ripetere l'operazione che ha generato l'errore per poter ottenere il suddetto file. Ricordiamo che il nuovo file generato avrà un nome leggermente diverso ogni volta; fare riferimento alla parte terminale di /var/log/apt/term.log per vedere il nome esatto del file generato. Sono necessari i privilegi sudo per leggere il logfile nel terminale.|| '''TODO''' The Bugs/Responses page should include these replies. == Come avanzare == L' upstream fondamentale per i bug in Emacs è http://debbugs.gnu.org/ che esegue lo stesso software di Debian BTS. I pachetti Ubuntu sono generalmente derivati da Debian, quindi Debian è un valido upstream; e ovviamente per i bug della pacchettizzazione Debian è solitamente l'unico upstream. = Bug noti = Descrizione di bug noti che possono ricevere segnalazioni duplicate e come riconoscerle. questa informazioni possono essere ottenute indirizzando la ricerca ai bug taggati come "metabug". '''Aperti''' || '''Bug''' || '''Soggetto''' || '''Sintomo''' || || [[https://launchpad.net/bugs/8896|8896]] || Il soggetto da LP || questo bug può essere identificato da ... || '''Chiusi''' || '''Bug''' || '''Soggetto''' || '''Sintomo''' || || [[https://launchpad.net/bugs/467446|467446]] || update-alternatives: error: alternative path /usr/bin/xemacs21 doesn't exist || Fixed in a recent version of `xemacs21` but still affects people runnng older Ubuntu releases || || [[https://launchpad.net/bugs/464587|464587]] || ocaml-mode: Invalid syntax description flag: "()1n" || Fixed in a recent version of `ocaml` but still affects people runnng older Ubuntu releases and `xemacs21` || || [[https://launchpad.net/bugs/222870|222870]] || anjsp: Wrong number of arguments: require, 3 || `anjsp` is not compatible with `xemacs21`. It no longer ships with Ubuntu but still affects people running older Ubuntu releases || || [[https://launchpad.net/bugs/396038|396038]] || Group `staff` missing; Emacs installation failed || This rare error was never properly debugged, but it did occur more than once || = Non-bug = Attualmente,basandoci su tutte le nostre conoscenze, questo non è un bug in Emacs, ma sovente si manifesta durante la sua installazione: || '''Bug''' || '''Soggetto''' || '''Sintomo''' || || [[https://launchpad.net/bugs/512096|512096]] || Exec format error: package failed to install/remove || Seems to often affect `emacsen-common` -- `00debian-vars.el` or similar file missing even though package apparently installed. See also bug [[https://launchpad.net/bugs/582341|#582341]] || ---- CategoryBugSquad CategoryDebugging From noreply at ubuntu.com Mon May 7 13:35:11 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 07 May 2012 13:35:11 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingProgramCrash=5Fit=22_by?= =?utf-8?q?_fabiomarconi?= Message-ID: <20120507133511.4713.83694@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingProgramCrash_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/DebuggingProgramCrash_it?action=diff&rev1=1&rev2=2 == Paccheti contenenti i simboli di debug == - Innanzitutto verificare se esiste, nei repository main, un pacchetto equivalente ma con sufffisso -dbg. Questi sono i pacchetti contenenti i siboli di debug ed equivalgono a '-dbgsym' descritto più avanti.bed below. È possibile usare in tutta sicurezza il pacchetto di debuging, ma non entrambi contemporaneamente. Provare ad installare il pacchetto aggiungendo -dbg al suo nome, per esempio: + Innanzitutto verificare se esiste, nei repository main, un pacchetto equivalente ma con sufffisso -dbg. Questi sono i pacchetti contenenti i siboli di debug ed equivalgono a '-dbgsym' descritto più avanti. È possibile usare in tutta sicurezza il pacchetto di debuging, ma non entrambi contemporaneamente. Provare ad installare il pacchetto aggiungendo -dbg al suo nome, per esempio: {{{ sudo apt-get install xserver-xorg-core-dbg }}} From noreply at ubuntu.com Tue May 8 16:35:32 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 08 May 2012 16:35:32 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22MozillaTeam/Bugs=5Fit=22_by_fabi?= =?utf-8?q?omarconi?= Message-ID: <20120508163532.24154.81854@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "MozillaTeam/Bugs_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/MozillaTeam/Bugs_it?action=diff&rev1=6&rev2=7 === Invio dei Crashes a Mozilla === - If you are using the release or beta channel, the preferred way to submit crash data is to send it directly to Mozilla when the crash dialog appears. In most cases it isn't necessary to open a bug in Launchpad when you do this, especially if the crash report you submitted is already linked to a bug report in the upstream Bugzilla, or the crash is being experienced on non-Ubuntu systems (eg, other Linux distros, or even Windows or Mac OS). If the crash you submit appears to be unique to Ubuntu and it doesn't have a bug open in the upstream Bugzilla (or you just feel that Ubuntu developers need to be made aware of it), then feel free to open a bug in Launchpad. + Se si sta utilizzando un canale rilascio o beta, la maniera più giusta per sottoporre ad analisi una segnalazione è di inviarla direttamente a Mozilla quando la segnalazione di crash appare. In molti casi non è necessario segnalare il bug anche in Launchpad, specialmente se la segnalazione di crash è già linkata ad una segnalazione upstream su Bugzilla, oppure il crash è già stato sperimentato su un sistema diverso da Ubuntu (es. altre distribuzioni Linux o anche Windows e Mac OS). Se si è certi che il problema si presenta solo su Ubuntu e non è già stato segnalato su upstream bugzilla (oppure se ritenete che gli sviluppatori Ubuntu ne debbano essere a conoscenza) è possibile aprire un bug in Launchpad. - If you do open a bug report in Launchpad, you '''must''' provide the crash ID of the crash report you submitted, and '''please use Apport'''. + Nel momento in cui si dovrà segnalare l'anomalia anche in Launchpad si '''deve''' anche fornire l' ID della segnalazione fatta, e '''per cortesia utilizzare Apport'''. - To find the ID's of crash reports that you have submitted, go to Help -> Troubleshooting Information and click on the about:crashes link in the "Application Basics" section. This is applicable to Firefox and Thunderbird. + Per trovare l'ID del crash che avete riportato, andare nel menù Aiuto -> Risoluzione dei problemi e fare clic sul link about:crashes. Ciò si applica sia a Firefox che a Thunderbird. - Note that the Apport hook provided from Firefox and Thunderbird 13 will automatically attach the ID's of crash reports you submitted to Mozilla, so you don't need to look for these manually '''as long as you submit the bug report using Apport!''' + Nota: Le segnalazioni fatte tramite Apport di Firefox o Thunderbird 13 conterranno automaticamente l'ID della segnalazione fatta su Bugzilla. - === Run Firefox in a Debugger === + === Eseguire Firefox in un Debugger === - If you are using Aurora or Nightly builds (which don't have the crash reporter turned on), then you will need to get a stacktrace manually using gdb. In some cases, a developer may ask you to do this in order to see local stack variables, which aren't visible in the upstream Socorro interface. + Se si sta usando una versdione Aurora o Nightly (che hanno il segnalatore di crash disabilitato) si dovrà ottenere la stacktrace manualmente utilizzando gdb. In taluni casi unio sviluppatore potrebbe chiedervi ciò per poter analizzare la stack delle variabili locali, che non sono visibili nell'interfaccia upstream Socorro. - To begin, please install gdb + Innanzitutto installare gdb: {{{ sudo apt-get install gdb }}} - Then install the necessary debugging symbols. + Quindi i necessari simboli di debugging. - For Firefox: + Per Firefox: {{{ sudo apt-get install firefox-dbg }}} - And Thunderbird: + Per Thunderbird: {{{ sudo apt-get install thunderbird-dbg }}} - These symbols will also be useful in most cases for both Firefox and Thunderbird. Please install them: + Questi altri sono utili per entrambi, per installarli: {{{ sudo apt-get install libgtk2.0-0-dbg libglib2.0-0-dbg libx11-6-dbg libpango1.0-0-dbg libc6-dbg }}} - After closing all instances of Firefox, start Firefox from the terminal with the following command: {{{ + Dopo avere chiuso completamente Firefox, avviare Firefox dal terminale con il comando: {{{ firefox -g 2>&1 | tee ~/gdb.txt (gdb) handle SIG33 pass nostop noprint (gdb) set pagination 0 @@ -124, +124 @@ (gdb) info registers (gdb) quit }}} - 2. Now ~/gdb.txt will contain the info we need to initially process your crash bug. So, please attach that file to your bug report. + 2. Ora ~/gdb.txt conterrà le informazioni necessarie a processare la vostra segnalazione. Quindi siete pregati di allegarlo alla segnalazione. - Please use the same steps for Thunderbird, but replacing "firefox" with "thunderbird" instead. + Utilizza e il medesimo procedimento per Thunderbird, sostituendo "firefox" con "thunderbird". == Hangs, or excessive CPU usage == From noreply at ubuntu.com Tue May 8 16:49:55 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 08 May 2012 16:49:55 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22MozillaTeam/Bugs=5Fit=22_by_fabi?= =?utf-8?q?omarconi?= Message-ID: <20120508164955.24130.17800@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "MozillaTeam/Bugs_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/MozillaTeam/Bugs_it?action=diff&rev1=7&rev2=8 Comment: Italian translation == Introduzione == - È possibile aiutare gli sviluppatori di Ubuntu a migliorare Firefox o Thunderbird fornendo loro ''utili'' segnalazioni di anomalie. Ciò implica dover fornire il maggior numero di informazioni possibili per descrivere l'anomalia (consultare [[http://www.chiark.greenend.org.uk/~sgtatham/bugs.html|How to report Bugs]]). + È possibile aiutare gli sviluppatori di Ubuntu a migliorare Firefox o Thunderbird fornendo loro ''utili'' segnalazioni di anomalie. Ciò implica dover fornire il maggior numero di informazioni possibili per descriverla (consultare [[http://www.chiark.greenend.org.uk/~sgtatham/bugs.html|How to report Bugs]]). È possibile che per alcune di queste istruzioni si debba usare il terminale, se non si è certi di come fare, consultare la guida sul [[http://wiki.ubuntu-it.org/AmministrazioneSistema/RigaDiComando|terminale]] per una veloce introduzione. @@ -18, +18 @@ == Utilizzo di Apport == - Tutte le anomalie inerenti Firefox e Thunderbird '''devono''' essere inviate tramite Apport (a meno di problemi che ne impediscano l'uso). Per Firefox, è possibile fare ciò scegliendo la voce "Segnala un problema..." dal menu Aiuto, oppure premendo Alt+F2 e digitare `ubuntu-bug firefox`. + Tutte le anomalie inerenti Firefox e Thunderbird '''devono''' essere inviate tramite Apport (a meno di problemi che ne impediscano l'uso). Per Firefox, è possibile fare ciò scegliendo la voce "Segnala un problema..." dal menu Aiuto, oppure premendo Alt+F2 e digitando `ubuntu-bug firefox`. Per Thunderbird, premere Alt+F2 e digitare `ubuntu-bug thunderbird`. - Utilizzando Apport, verranno automaticamente allegati i file necessari, risparmiando così il tempo che si perderebbe per richiederli. Vi peghiamo di avviare segnalazioni di anomalie in Firefox o Thunderbird utilizzando l'iterfaccia Launchpad. Nella maggior parte dei casi non sarano presi in considerazioni e sarannno chiusi con la richiesta di risegnalarla utilizzando Apport. Per cortesia non sciupate il tempo degli sviluppatori o dei bug triagers utilizzando l'interfaccia Launchpad. + Utilizzando Apport, verranno automaticamente allegati i file necessari, risparmiando così il tempo che si perderebbe per richiederli. Vi preghiamo di '''non''' avviare segnalazioni di anomalie in Firefox o Thunderbird utilizzando l'iterfaccia Launchpad. Nella maggior parte dei casi non sarano prese in considerazioni e sarannno chiuse con la richiesta di risegnalarla utilizzando Apport. Per cortesia non sciupate il tempo degli sviluppatori o dei bug triagers utilizzando l'interfaccia Launchpad. == Provare l'esecuzione in modalità sicura == - Alcuni problemi sono causati da temi di terze parti, addons e plugins, oppure personalizzazioni nascostein about:config. Tutto ciò può essere disabilitato temporaneamente eseguendo Firefox o Thunderbird in modalità sicura. + Alcuni problemi sono causati da temi di terze parti, addons e plugins, oppure personalizzazioni nascoste in about:config. Tutto ciò può essere disabilitato temporaneamente eseguendo Firefox o Thunderbird in modalità sicura. Per eseguire Firefox in modalità sicura occorre accertarsi che sia completamente chiuso, premere Alt+F2 ed eseguire `firefox -safe-mode`. Per eseguire Thunderbird in modalità sicura occorre chiuderne tutte le finestre, premere Alt+F2 ed eseguire `thunderbird -safe-mode`. @@ -37, +37 @@ == Siate specifici == - Assicuratevi che lo sviluppatore possa riprodurre l'anomalia. Fornite ogni dettaglio possibile riguardante il bug, in particolare una sequenza esplicita delle azioni da compiere per riprodurre il bug. Si prega di non pensare che solo perché si verifica un bug sia facile per gli altri riprodurlo. + Assicurarsi che lo sviluppatore possa riprodurre l'anomalia. Fornire ogni dettaglio possibile riguardante il bug, in particolare una sequenza esplicita delle azioni da compiere per riprodurlo. Si prega di non pensare che solo perché si verifica un bug sia facile per gli altri riprodurlo. == Controllare se il bug è già stato segnalato == - Preghiamo di verificare che il bug non sia già stato segnalato. Comprendiamo che a volte è difficile sapere cosa cercare, e che lo è ancora di più in mezzo ad una moltitudine di altre segnalazioni, ma èuno sforzo necessario. + Preghiamo di verificare che il bug non sia già stato segnalato. Comprendiamo che a volte è difficile sapere cosa cercare, e che lo è ancora di più in mezzo ad una moltitudine di altre segnalazioni, ma è uno sforzo necessario. == Cercare il proprio problema in SUMO == - Controllare su [[http://support.mozilla.org/|http://support.mozilla.org/]], per vedere se qualcuno ha già richiesto supporto per un problema simile al vostro. Potreste scoprire che il problema non è realmente un bug oppure che è già stato segnalato. Potreste anche trovare un a soluzione temporanea. + Controllare su [[http://support.mozilla.org/|http://support.mozilla.org/]], per vedere se qualcuno ha già richiesto supporto per un problema simile al vostro. Potreste scoprire che il problema non è realmente un bug oppure che è già stato segnalato. Potreste anche trovare una soluzione temporanea. == Problemi con uno specifico sito web == - Se Firefox non visualiza correttamente un sito web è '''necessario''' fornire le seguenti informazioni se posibile: + Se Firefox non visualiza correttamente un sito web è '''necessario''' fornire le seguenti informazioni se possibile: * Uno screenshot che mostri chiaramente il problema. - * Rammentiamo che il problema potrebbe non essere ovvio a chi non ha familiarità con il sito in questione e ptrebbe non sapere come dovrebbe apparire normalmente. In questo caso siete pregati di descrivere cosa è sbagliato. + * Rammentiamo che il problema potrebbe non essere ovvio a chi non ha familiarità con il sito in questione e potrebbe non sapere come dovrebbe apparire il sito normalmente. In questo caso siete pregati di descrivere cosa è sbagliato. * Rimuovere le informazioni personali dagli screenshot allegati. * L' URL della pagina che causa problemi (preferibilmente un URL che non richieda iscrizione, comprendiamo però che a volte ciò non è possibile). - Potreste restare sorpresi, ma riceviamo segnalazioni inerenti siti web non visualizzati corretamene, senza alcuna di queste informazioni fornita. Capirete senz'altro che richiedere e spiegare è una perdita di tempo. + Potreste restare sorpresi, ma riceviamo segnalazioni inerenti siti web non visualizzati correttamene, senza alcuna di queste informazioni fornita. Capirete senz'altro che richiedere e spiegare è una perdita di tempo. Quando si sperimenta un problema con un sito web, vi preghiamo di provare come segue: * Provare ad utilizzare un'altro browser (non-Gecko) tipo (es, Chromium o Epiphany). * Per cortesia nella descrizione segnalare quale altro browser è stato testato. - * Se il sito web funziona correttamente con un altro browser, aleegare uno screenshot di come dovrebbe apparire. + * Se il sito web funziona correttamente con un altro browser, allegare uno screenshot di come dovrebbe apparire. == Crash == === Alcune cose da considerare === - Per cortesia evitare il presupposto che se avete sperimentato un crash, anche chiunque altro possa riprodurlo agevolmente. Tutte le segnalazione di crash devono avere allegato una completa stacktrace ed una completa descrizione dei passi da seguire per riprodurre il crash. Se il problema si amnifesta solamente con uno specifico sito web, vi preghiamo di allegare l'URL. + Per cortesia evitare il presupposto che se avete sperimentato un crash, chiunque altro possa riprodurlo agevolmente. Tutte le segnalazione di crash devono avere allegato una completa stacktrace ed una completa descrizione dei passi da seguire per riprodurre il crash. Se il problema si amnifesta solamente con uno specifico sito web, vi preghiamo di allegare l'URL. Ad esempio, questi tipi di segnalazioni sono inutili e non riceveranno, nostro malgrado, alcuna attenzione: @@ -80, +80 @@ === Invio dei Crashes a Mozilla === - Se si sta utilizzando un canale rilascio o beta, la maniera più giusta per sottoporre ad analisi una segnalazione è di inviarla direttamente a Mozilla quando la segnalazione di crash appare. In molti casi non è necessario segnalare il bug anche in Launchpad, specialmente se la segnalazione di crash è già linkata ad una segnalazione upstream su Bugzilla, oppure il crash è già stato sperimentato su un sistema diverso da Ubuntu (es. altre distribuzioni Linux o anche Windows e Mac OS). Se si è certi che il problema si presenta solo su Ubuntu e non è già stato segnalato su upstream bugzilla (oppure se ritenete che gli sviluppatori Ubuntu ne debbano essere a conoscenza) è possibile aprire un bug in Launchpad. + Se si sta utilizzando un canale rilascio o beta, la maniera più giusta per sottoporre ad analisi una segnalazione è di inviarla direttamente a Mozilla quando la segnalazione di crash compare. In molti casi non è necessario segnalare il bug anche in Launchpad, specialmente se la segnalazione di crash è già linkata ad una segnalazione upstream su Bugzilla, oppure il crash è già stato sperimentato su un sistema diverso da Ubuntu (es. altre distribuzioni Linux o anche Windows e Mac OS). Se si è certi che il problema si presenta solo su Ubuntu e non è già stato segnalato su upstream Bugzilla (oppure se ritenete che gli sviluppatori Ubuntu ne debbano essere a conoscenza) è possibile aprire un bug in Launchpad. Nel momento in cui si dovrà segnalare l'anomalia anche in Launchpad si '''deve''' anche fornire l' ID della segnalazione fatta, e '''per cortesia utilizzare Apport'''. @@ -90, +90 @@ === Eseguire Firefox in un Debugger === - Se si sta usando una versdione Aurora o Nightly (che hanno il segnalatore di crash disabilitato) si dovrà ottenere la stacktrace manualmente utilizzando gdb. In taluni casi unio sviluppatore potrebbe chiedervi ciò per poter analizzare la stack delle variabili locali, che non sono visibili nell'interfaccia upstream Socorro. + Se si sta usando una versione Aurora o Nightly (che hanno il segnalatore di crash disabilitato) si dovrà ottenere la stacktrace manualmente utilizzando gdb. In taluni casi uno sviluppatore potrebbe chiedervi ciò per poter analizzare la stack delle variabili locali, che non sono visibili nell'interfaccia upstream Socorro. Innanzitutto installare gdb: @@ -128, +128 @@ Utilizza e il medesimo procedimento per Thunderbird, sostituendo "firefox" con "thunderbird". - == Hangs, or excessive CPU usage == + == Blocchi o eccessivo uso della CPU == If Firefox or Thunderbird appears to completely lock up, you must provide a stacktrace of the hung process with your bug report. In most cases, hangs are quite random and non-reproducible, so please don't submit reports without this information. From noreply at ubuntu.com Tue May 8 18:16:35 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 08 May 2012 18:16:35 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22MozillaTeam/Bugs=5Fit=22_by_fabi?= =?utf-8?q?omarconi?= Message-ID: <20120508181635.7433.60524@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "MozillaTeam/Bugs_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/MozillaTeam/Bugs_it?action=diff&rev1=8&rev2=9 Nota: Le segnalazioni fatte tramite Apport di Firefox o Thunderbird 13 conterranno automaticamente l'ID della segnalazione fatta su Bugzilla. - === Eseguire Firefox in un Debugger === + === Eseguire Firefox in un debugger === Se si sta usando una versione Aurora o Nightly (che hanno il segnalatore di crash disabilitato) si dovrà ottenere la stacktrace manualmente utilizzando gdb. In taluni casi uno sviluppatore potrebbe chiedervi ciò per poter analizzare la stack delle variabili locali, che non sono visibili nell'interfaccia upstream Socorro. @@ -130, +130 @@ == Blocchi o eccessivo uso della CPU == - If Firefox or Thunderbird appears to completely lock up, you must provide a stacktrace of the hung process with your bug report. In most cases, hangs are quite random and non-reproducible, so please don't submit reports without this information. + Se Firefox o Thunderbird sembrano completamente bloccati, assieme alla segnalazione è indispensabile fornire anche una stacktrace. In molti casi i blocchi sono casuali e non-riproducibili, quindi non si devono aprire segnalazioni senza queste informazioni. - If it appears to be using excessive CPU, please first try disabling addons and plugins. If the problem is with Firefox, are you viewing pages with Flash or video content, animated gif's or other animations? Does the problem stop when you no longer view these? + Se si rileva un eccessivo uso della CPU, provare prima a disabilitare addons e plugins.If it appears to be using excessive CPU, please first try disabling addons and plugins. Se il problema si verifica con Firefox, sis tanno per caso visualizzando pagine Flas, con contenuti video, gif animate o altre animazioni? Se non si visualizzano queste, il problema persiste ? - If none of your addons are causing excessive CPU usage, and you're not viewing videos or Flash content, then there are a couple of things you can do to make your bug report more useful. First, please get a stacktrace whilst the process is spinning the CPU. Secondly, it would be great if you could try to use something like sysprof, which is available in the Software Center (see [[http://sysprof.com/|Sysprof, System-wide Performance Profiler for Linux]] + Se nessun addons sta causando un eccesivo uso della CPU e non si stanno visualizzando contenuti Flash, allora ci sono ancora un paio di cose da fare per rendere ottimale la segnalazione. + Primo ottenere una stacktrace mentre il processo 'fa girare' la CPU. Secondo sarebbe grandioso effettuare una prova anche con uno strumento quele sysprof, che è possibile trovare nel Software Center (vedere [[http://sysprof.com/|Sysprof, System-wide Performance Profiler for Linux]] - Some people also run the application in strace when reporting issues with excessive CPU usage. In general, the output of strace is not all that useful when debugging an issue where the process is CPU bound. + Alcuni, quando eseguono la segnalazione, eseguono l'applicazione anche in strace per un'anomalia inerente un eccesssivo uso della CPU. In generale l'output di strace non è affatto utile nei casi in cui il processo limita la CPU. - === Getting a stacktrace of a hung process === + === Ottenere una stacktrace da un processo bloccato === - Getting a stacktrace of a hung process is quite easy. First, please install gdb and the required debugging symbols as advised in [[https://wiki.ubuntu.com/MozillaTeam/Bugs#Run_Firefox_in_a_Debugger|Run Firefox in a Debugger]]. + Ottenere una stack trace da un processo bloccato è abbastanza semplice. Innanzitutto installare i simboli di debugging come spiegato in [[https://wiki.ubuntu.com/MozillaTeam/Bugs_it#Eseguire_Firefox_in_un_debugger|Eseguire Firefox in un debugger]]. If the hang is reproducible, just run Firefox or Thunderbird as described in [[https://wiki.ubuntu.com/MozillaTeam/Bugs#Run_Firefox_in_a_Debugger|Run Firefox in a Debugger]] and get a stacktrace when the application has hung. From noreply at ubuntu.com Tue May 8 18:49:50 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 08 May 2012 18:49:50 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22MozillaTeam/Bugs=5Fit=22_by_fabi?= =?utf-8?q?omarconi?= Message-ID: <20120508184950.12790.8981@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "MozillaTeam/Bugs_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/MozillaTeam/Bugs_it?action=diff&rev1=9&rev2=10 Se Firefox o Thunderbird sembrano completamente bloccati, assieme alla segnalazione è indispensabile fornire anche una stacktrace. In molti casi i blocchi sono casuali e non-riproducibili, quindi non si devono aprire segnalazioni senza queste informazioni. - Se si rileva un eccessivo uso della CPU, provare prima a disabilitare addons e plugins.If it appears to be using excessive CPU, please first try disabling addons and plugins. Se il problema si verifica con Firefox, sis tanno per caso visualizzando pagine Flas, con contenuti video, gif animate o altre animazioni? Se non si visualizzano queste, il problema persiste ? + Se si rileva un eccessivo uso della CPU, provare prima a disabilitare addons e plugins. Se il problema si verifica con Firefox, si stanno per caso visualizzando pagine Flash, con contenuti video, gif animate o altre animazioni? Se non si stanno visualizzando queste, il problema persiste? Se nessun addons sta causando un eccesivo uso della CPU e non si stanno visualizzando contenuti Flash, allora ci sono ancora un paio di cose da fare per rendere ottimale la segnalazione. - Primo ottenere una stacktrace mentre il processo 'fa girare' la CPU. Secondo sarebbe grandioso effettuare una prova anche con uno strumento quele sysprof, che è possibile trovare nel Software Center (vedere [[http://sysprof.com/|Sysprof, System-wide Performance Profiler for Linux]] + Primo ottenere una stacktrace mentre il processo 'fa girare' la CPU. Secondo sarebbe grandioso effettuare una prova anche con uno strumento quele sysprof, che è possibile trovare nel Software Center (vedere [[http://sysprof.com/|Sysprof, System-wide Performance Profiler for Linux]]). Alcuni, quando eseguono la segnalazione, eseguono l'applicazione anche in strace per un'anomalia inerente un eccesssivo uso della CPU. In generale l'output di strace non è affatto utile nei casi in cui il processo limita la CPU. @@ -143, +143 @@ Ottenere una stack trace da un processo bloccato è abbastanza semplice. Innanzitutto installare i simboli di debugging come spiegato in [[https://wiki.ubuntu.com/MozillaTeam/Bugs_it#Eseguire_Firefox_in_un_debugger|Eseguire Firefox in un debugger]]. - If the hang is reproducible, just run Firefox or Thunderbird as described in [[https://wiki.ubuntu.com/MozillaTeam/Bugs#Run_Firefox_in_a_Debugger|Run Firefox in a Debugger]] and get a stacktrace when the application has hung. + Se il blocco è riproducibile, basta eseguire Firefox o Thunderbird come descritto in [[https://wiki.ubuntu.com/MozillaTeam/Bugs_it#Eseguire_Firefox_in_un_debugger|Eseguire Firefox in un debugger]]Run_Firefox_in_a_Debugger|Run Firefox in a Debugger]] ed ottenere la stacktrace quando l'applicazione si blocca. - If the hang is not reproducible and you want to get a stacktrace of an already hung process, you will need to attach gdb to it. To do this, first run: + Se il blocco non è riproducibile e volete ottenere una stacktrace di un processo già bloccato, è necessario allacciargli gdb. Per fare cio, innanzitutto eseguire: {{{ pidof firefox }}} - ..or.. + ..oppure.. {{{ pidof thunderbird-bin }}} - ...to get the PID of the process. Then do: + ...per ottenere il PID del processo. Quindi eseguire: {{{ gdb 2>&1 | tee ~/gdb.txt (gdb) handle SIG33 pass nostop noprint @@ -164, +164 @@ (gdb) attach }}} - ...now you can get a stacktrace as advised below (assuming the process was hung before attaching gdb) + ...ora si otterrà uno stacktrace come preannunciato (ammesso che il processo fosse realmente bloccato prima dell'allacciamento di gdb) {{{ (gdb) bt full (gdb) thread apply all backtrace full }}} - If you're debugging excessive CPU rather than a hang, please repeat the following steps a few times: + Se si sta eseguendo il debugging per un eccessivo uso della CPU invece di un blocco, vi peghiamo di eseguire i seguenti passi alcune volte: {{{ (gdb) continue - ...# now press CTRL+C to interrupt it again + ...# ora premere CTRL+C per interromperlo ancora (gdb) bt full (gdb) thread apply all backtrace full }}} - Then: + Quindi: {{{ (gdb) quit }}} - Please remember to attach the resulting file to your bug report. + Per cortesia ricordare di allegare i risultanti file alla vostra segnalazione. - == Excessive memory usage == + == Excessivo utilizzo della memoria == - If you are reporting a bug about excessive memory usage, you '''must''' copy and paste the contents of "about:memory" in to your bug report, once you have reported this with Apport. + Quando si segnala un bug inerente un eccessivo utilizzo della memoria, si '''deve''' copiare ed incollare il contenuto di "about:memory" eseguita tramite Apport. - In the future, we hope to automate this step. + In futuro speriamo di poter rendere automatico questo passaggio. - Note that debugging memory leaks in Firefox is quite involved. If you're feeling adventurous, please take a look at [[https://developer.mozilla.org/en/Debugging/Debugging_memory_leaks|Debugging memory leaks]] and [[https://developer.mozilla.org/en/Debugging_Mozilla_with_Valgrind|Debugging Mozilla with Valgrind]] + Si tenga presente che Firefox resta abbastanza coinvolto nel debugging di carenze di memoria. Se vi sentite avventurosi, consultare [[https://developer.mozilla.org/en/Debugging/Debugging_memory_leaks|Debugging memory leaks]] e [[https://developer.mozilla.org/en/Debugging_Mozilla_with_Valgrind|Debugging Mozilla with Valgrind]] - == Check the Error Console == + == Controllare la consle degli errori == - Some bugs may result in unhandled JS exceptions or other error messages being logged to the error console, and these may provide a strong clue as to the cause of a bug. To view these, open the error console from "Tools -> Web Developer -> Error Console", and select "Errors". + Alcuni bug possono scaturire da eccezioni JS non gestite "unhandled JS exceptions" o altri messaggi d'errore visibili nella console degli errori, e questi ultimi possono fornire un valido indizio sulla causa di un bug. Per visualizzarli, aprire la console degli errori da "Strumenti -> Sviluppo web -> Console degli errori" e selezionare "Errori". - Note, you many need to enable the menuitem to access the error console. To do this, open "about:config", and set "devtools.errorconsole.enabled" to "true" + Nota: potrebbe essere necessario abilitare la voce nel menù per poter accedere alla console degli errori. per fare ciò, aprire "about:config" ed impostare "devtools.errorconsole.enabled" su "true" - == Other specific issues == - === Problems with menus on systems that use a global menubar === + == Altri specifici problemi == + === Problemi coi menù in un sistema che usa una barra unica per i menù === By default, the unity shell shipped in Ubuntu 11.04 and newer displays application menubars in the top panel. Some other desktop environments may also provide similar functionality (there is a plasmoid for KDE which does this). From costamagnagianfranco at yahoo.it Wed May 9 15:48:02 2012 From: costamagnagianfranco at yahoo.it (Gianfranco Costamagna) Date: Wed, 9 May 2012 16:48:02 +0100 (BST) Subject: Boinc Help for bug 991179 Message-ID: <1336578482.80336.YahooMailNeo@web171203.mail.ir2.yahoo.com> Hi to all, I write here to ask for a bug fix. There is a patch in the precise boinc package that make it run with a computation error with 2 or more project. See [1] After trying some time we figured out that the cause is the patch MoreInformativeAppStartFailure.patch taken from debian. The debian mantainer already knows this problem (I take boinc directly from debian's git) and disabled the affected patch. So what I asking for is to disable this patch in the ubuntu repo, or maybe sync the latest 7.0.27 version from my recipe https://code.launchpad.net/~costamagnagianfranco/+recipe/boinc-daily that fixes the problem for some GPU cards. [1] https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/991179 Many thanks Gianfranco -------------- next part -------------- An HTML attachment was scrubbed... URL: From trekcaptainusa.tw at gmail.com Wed May 9 17:51:54 2012 From: trekcaptainusa.tw at gmail.com (Thomas Ward) Date: Wed, 9 May 2012 13:51:54 -0400 Subject: Boinc Help for bug 991179 In-Reply-To: References: <1336578482.80336.YahooMailNeo@web171203.mail.ir2.yahoo.com> Message-ID: Whoops, forgot to send this to bugsquad, when I replied. ------ Thomas LP: trekcaptainusa-tw Bug Squad Member Ubuntu Member ---------- Forwarded message ---------- From: Thomas Ward Date: Wed, May 9, 2012 at 1:40 PM Subject: Re: Boinc Help for bug 991179 To: Gianfranco Costamagna Gianfranco, Pardon my asking, but are you expecting this to be updated for Precise, or included in Quantal? If you want this updated in Precise, a fix will have to be produced, and then subsequently an SRU will need to be filed in order to get this updated in Precise. The Precise repos (now that Precise is released as stable) don't get updated for a majority of packages unless SRUs get filed (Stable Release Updates - https://wiki.ubuntu.com/StableReleaseUpdates) *------ Thomas LP: trekcaptainusa-tw Bug Squad Member Ubuntu Member* On Wed, May 9, 2012 at 11:48 AM, Gianfranco Costamagna < costamagnagianfranco at yahoo.it> wrote: > Hi to all, I write here to ask for a bug fix. > > There is a patch in the precise boinc package that make it run with a > computation error with 2 or more project. See [1] > > After trying some time we figured out that the cause is the patch > MoreInformative**AppStartFailure**.patch taken from debian. > The debian mantainer already knows this problem (I take boinc directly > from debian's git) and disabled the affected patch. > So what I asking for is to disable this patch in the ubuntu repo, or maybe > sync the latest 7.0.27 version from my recipe > https://code.launchpad.net/~costamagnagianfranco/+recipe/boinc-daily > that fixes the problem for some GPU cards. > > [1] https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/991179 > > > Many thanks > Gianfranco > > -- > 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 noreply at ubuntu.com Wed May 9 19:00:52 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Wed, 09 May 2012 19:00:52 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingGwibber=5Fit=22_by_fabi?= =?utf-8?q?omarconi?= Message-ID: <20120509190052.7062.1456@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingGwibber_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/DebuggingGwibber_it Comment: Italian translation started New page: <> ||'''Contents'''<
><>|| = Introduzione = Bugs relativi ai pacchetti gwibber e gwibber-service = Come segnalare un problema = Siete pregati di usare "Segnala un problema" nel menù Aiuto (Aiuto->Segnala un problema) = Peocedure per il debugging = Eseguire in un terminale: $pkill gwibber-service & gwibber-service -d -o $gwibber --debug = How to Triage = Todo... == Stock Replies == '''Gwibber Crashes''' @Username, Please could you run under latest version of gwibber: gwibber --debug > gwibber-debug.txt and attach resulted output of this file to your report (following your steps to reproduce this issue), Thanks! '''Gwibber-Service Issues''' @Username, Please could you run under latest version of gwibber: gwibber-service -d -o and attach all resulted output to a textfile (following your steps to reproduce this issue), Thanks! '''Try to reproduce it with PPA release''' Please could you try to reproduce this issue in latest version of gwibber daily ppa (you can get from https://launchpad.net/~gwibber-daily/+archive/ppa | or latest stable release https://launchpad.net/~gwibber-team/+archive/ppa) and check if this problem is still affecting you? Thanks in advance! == How to Forward to upstream tracker == Click on "Also affects project" and look up for "Gwibber" project, then press ok. = Known bugs = Description of known bug reports that may receive duplicates and how to recognise them. This information should be obtained by looking for bugs tagged as 'metabug'. '''The Hottest''' || '''Bug''' || '''Subject''' || '''Symptom''' || || [[https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/718359|718359]] || Can't start gwibber svg format image || svg images can't be loaded || || [[https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/658074|658074]] || Acents in hashtags support || hashtags are broken if you use acents || || [[https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/614742|614742]] || Facebook problems || Problems related to Facebook authentication and stuffs || || [[https://bugs.launchpad.net/gwibber/+bug/645512|645512]] || Twitter doesn't update || Twitter stop to update because you are following a 'special' user || || [[https://bugs.launchpad.net/gwibber/+bug/500927|500927]] || Retweets are not displayed correctly || Messages are truncated or not fully displayed || || [[https://bugs.launchpad.net/ubuntu/+source/pywebkitgtk/+bug/688732|688732]] || Gwibber can't start in Ubuntu Natty || Pywebkitgtk is causing gwibber crashed, there is a workaround available|| || [[https://bugs.launchpad.net/ubuntu/+source/gwibber/+bug/519262|519262]] || Provide ability to follow a user || there is no way to follow a user|| = Work Arounds = Some basic procedures to fix some common troubles: '''Gwibber can't start (using CouchDB as backend >=2.30.x releases)''' rm -fr ~/.cache/desktop-couch ~/.config/desktop-couch and ~/.local/share/desktop-couch and then start gwibber again. '''Avatars not loaded correctly''' rm -fr ~/.cache/gwibber/avatars/* '''Reset your settings (Gconf)''' 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 CategoryDebugging From noreply at ubuntu.com Wed May 9 19:52:28 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Wed, 09 May 2012 19:52:28 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22LibreOfficeBugWrangling=5Fit=22_?= =?utf-8?q?by_fabiomarconi?= Message-ID: <20120509195228.12197.15935@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "LibreOfficeBugWrangling_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/LibreOfficeBugWrangling_it Comment: Italian translation New page: <> ||'''Contents'''<
><>|| = Come fare una segnalazione = * Vi preghiamo di non segnalare bug inerenti LibreOffice senza avere prima letto questa pagina ed avere eseguito le necessarie azioni riportate in seguito. La mancata inosservanza causerà ritardi nell'indirizzamento della vostra segnalazione. * Vi preghiamo di segnalare tutti i vostri bug in LibreOffice eseguendo nel terminale: <
> {{{ubuntu-bug }}} <
> <
> dove è lo specifico pacchetto nel quale è stato rinvenuto il problema. Per esempio, se si ha un problema importando un documento con Writer: <
> {{{ubuntu-bug libreoffice-writer}}} * Un semplice modello di segnalazione di bug: <
> || 1) lsb_release -rd <
> <
> 2) apt-cache policy libreoffice-writer <
> <
> 3) What is expected to happen in Writer is (cosa dovrebbe succedere) . <
> <
> 4) What happened instead is...(cosa invece accade...) <
> <
> WORKAROUND: Perform the following steps:...|| * Per cortesia non riportare più di un bug per ogni segnalazione. * Per cortesia evitare commenti sul tempo necessario alla riparazione, specialmente se non si sono seguiti i fondamentali passi di debugging in seguito descritti. Siate consapevoli che noi tutti vorremmo vedere i bug riparati immediatamente, ma purtroppo gli ostacoli maggiori si incontrano nella riproducibilità e chiarezza della segnalazione. = Debugging Procedure = == Document Issues == === Bug importing a non-MS Office document === * If you are reporting about importing a non-MS Office document, please attach the document to the bug report before opening in LibreOffice or in any other program. As well, please post a screenshot of how it looks in LibreOffice with a specific description about how it should look. === Bug exporting to MS Office === * If you are reporting about how a document looks different exporting to MS Office, please attach the document to the bug report immediately after saving via LibreOffice, but before opening in MS Office. As well, please post a screenshot of how it looks in LibreOffice and then how it shows in MS Office. === Bug Importing from MS Office === * If you are reporting about how a document looks importing from MS Office, please save the file in MS Office, then before opening in any other program, attach the document to the bug report. As well, please post a screenshot of how it looks in LibreOffice and then how it shows in MS Office. === Bug Exporting to Adobe PDF === * If you are reporting about how a document looks exporting to Adobe Reader, please attach the file to the bug report before and after exporting to PDF. As well, provide screenshots of how it looks in LibreOffice and Adobe Reader. === Bug Importing PDF === * If you are reporting about how a PDF document looks importing into Draw, please attach the file to the bug report before importing into Draw. As well, provide screenshots of how it looks in LibreOffice and Adobe Reader. == Printing == * For issues printing from LibreOffice please report this against cups first via the Terminal: <
> {{{ubuntu-bug cups}}} <
> <
> It could end up being an issue with LibreOffice, but it's best to start with cups in order to rule it out. As well, please follow all steps noted in https://wiki.ubuntu.com/DebuggingPrintingProblems . == Crashes == === LibreOffice Crashes but System Still Functional === * For instances when only LibreOffice crashes but you can still use the OS without hard rebooting, please report this via via Apport and ensure you have all the LibreOffice debug symbols installed (libreoffice-dbg, uno-libs3-dbg, and ure-dbg). For more on this please see https://wiki.ubuntu.com/Apport . As well, if this happened while a particular document was open or you were manipulating the document, please attach that document to the bug report with detailed, click-for-click steps on how to reproduce the crash. * In the rare instance that after you followed the above, apport did not kick in, please provide a backtrace, valgrind, and strace following https://wiki.ubuntu.com/DebuggingProgramCrash . === The Whole System Hangs or Boots to the Login Screen === * For instances when your using LibreOffice and either the system hangs requiring a hard reset or your booted to the login screen, this is a bug in either xorg or the kernel. Please follow https://help.ubuntu.com/community/DebuggingSystemCrash . As well, if this happened while a particular document was open or you were manipulating the document, please attach that document to the bug report with detailed, click-for-click steps on how to reproduce the crash. == Regressions == * For regressions, it is helpful to perform a binary bisect ("bibisect") to narrow down which commit specifically caused the problem. For instructions please see http://sweetshark.livejournal.com/7683.html . == Wishlists == * For Wishlist reports, many of these are requests to implement a feature in LibreOffice found in MS Office. A broad but good rule of thumb is if you want LibreOffice to do something that MS Office does (MS Office compatibility expectation), please document how specifically MS Office does it, then how LibreOffice does not or does not do well that which you desire. Please keep in mind, pocket cases exist where LibreOffice intentionally does not do what MS Office does (ex. leap year implementation https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/456100). = Triaging LibreOffice Bugs = == Writer and Calc == * For bugs in Writer, it is helpful to check to see if the problem exists in AbiWord. For bugs in Calc, it is helpful to check to see if the problem exists in Gnumeric. Sometimes, AbiWord and Gnumeric give the bug reporter a usable workaround to the problem (and vice versa). If a workaround is found, feel free to document it in the report. As well, while not quite apples and oranges code wise, it gives LibreOffice developers code to base a patch on. == Wishlist Reports == * For Wishlist reports, they most likely should be marked Won't Fix Wishlist. This is due to how Ubuntu diverts very little from the LibreOffice upstream source release, and upstream's rapid maintenance cadence. <
> A Won't Fix Wishlist stock reply: ||Thank you for reporting this and helping making Ubuntu better. Regarding this report:<
>- This is a clearcut upstream issue. Your welcome to send this to the developers of the software by following the instructions at http://wiki.documentfoundation.org/BugReport . If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status.<
>- Marking LibreOffice Packaging and libreoffice (Ubuntu) => Won't Fix Wishlist. This does not mean the issue will not be cared about, but if it is cared about (even by Ubuntu/Canonical contributors), it is done upstream at LibreOffice.|| == How to Forward Bugs Upstream == * Once marked Triaged, a report may be filed upstream using the [[https://www.libreoffice.org/get-help/bug/|LibreOffice Bug Submission Assistant]] <>. * Once a remote bug watch has been added to a bug report, it is helpful to append [Upstream] to the beginning of the bug title. This helps in searching for bugs reports by title. Please do not append this unless a remote bug watch has been added to the report as this creates confusion on which bugs have been reported upstream and which have not. ---- CategoryBugSquad CategoryDebugging From noreply at ubuntu.com Wed May 9 16:11:53 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Wed, 09 May 2012 16:11:53 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22MozillaTeam/Bugs=5Fit=22_by_fabi?= =?utf-8?q?omarconi?= Message-ID: <20120509161153.7785.39242@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "MozillaTeam/Bugs_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/MozillaTeam/Bugs_it?action=diff&rev1=14&rev2=15 Comment: Italian translation done Vedere [[https://help.ubuntu.com/community/AppArmor|AppArmor]] - === "The bookmarks and history system will not be functional" === + === "Il segnalibri e la cronologia potrebbero non funzionare" === - If you see this error when starting Firefox and you are unable to access or modify your bookmarks, please take a look at this support article: [[http://support.mozilla.org/en-US/kb/The%20bookmarks%20and%20history%20system%20will%20not%20be%20functional|The bookmarks and history system will not be functional]]. + Se compare questo errore all'avvio di Firefox e non si riesce ad accedere o modificare il segnalibri, vi peghiamo di leggere questo testo di supporto: [[http://support.mozilla.org/en-US/kb/The%20bookmarks%20and%20history%20system%20will%20not%20be%20functional|The bookmarks and history system will not be functional]]. - This is not usually a bug, but is normally caused by a corrupt places.sqlite or broken permissions in your profile folder. Please don't report a bug about this, unless you are unable to resolve the issue by following the steps in the support article. + Solitamente questo non è un bug, ma è causato da un file places.sqlite corrotto o irregolarita nei permessi del vostro profilo. si prega di non segnalare un bug in merito a meno che non si riesca a risolvere con le spiegazioni del precedente testo di supporto. - === XML errors and broken UI after upgrade === + === Errori XML e UI guasta dopo un aggiornamento === - After each release, some of our users report bugs that look a bit like this: + Dopo ogni rilascio, alcuni utenti segnalano bug simili a questo: {{{ XML Parsing Error: error in processing external entity reference Location: jar:file:///usr/lib/firefox/chrome/toolkit.jar!/content/global/netError.xhtml @@ -316, +316 @@ --^ }}} - Other symptoms include missing UI elements after an upgrade or other kinds of XML errors in dialogue boxes or on firefox's stderr. + Altri sintomi sono rappresentati da parti mancanti dell'interfaccia utente dopo un aggiornamento, altri errori XML in box informativi oppure in firefox's stderr. - This is one of the things that typically happens if you don't restart your Firefox after an upgrade. Please do not report this as a bug. There is already a bug report open about this. + Generalmente questo accade se non si riavvia Firefox dopo l'aggiornamento. Siee pregati di non avviare segnalazioni in merito. Esiste gia una segnalazione aperta su questo problema. - = Closed Bug Reports = - If you find your bug report to be closed, it has been done by someone on our team for specific reasons. If you have a problem or wish to dispute the action, please use the bug report to ask for more information. + = Segnalazioni chiuse = + Se la vastra segnalazione viene chiusa, è stato fatto da qualcuno del nostro team per uno specifico motivo. Se non siete d'accordo richiedete chiarimenti sulla segnalazione stessa. - = Bug Triage and Procedures = + = Bug Triage e procedure = - Visit [[https://wiki.ubuntu.com/MozillaTeam/Bugs/Procedures|BugProcedures]] for an Introduction and best practices on how to process Mozilla bugs. + Visitare [[https://wiki.ubuntu.com/MozillaTeam/Bugs/Procedures|BugProcedures]] per una introduzione alle migliori pratiche su come trattare i bug in Mozilla. ---- [[CategoryMozillaTeam]], [[CategoryBugSquad]], [[CategoryDebugging]] From trinikrono at gmail.com Thu May 10 14:05:44 2012 From: trinikrono at gmail.com (kurt belgrave) Date: Thu, 10 May 2012 10:05:44 -0400 Subject: Bitesize Task In-Reply-To: <1677935.stiXnIh2mg@ce-bzr> References: <20120501154737.GA2879@murraytwins.com> <20120502150052.GC2879@murraytwins.com> <1677935.stiXnIh2mg@ce-bzr> Message-ID: i found a similar one in https://bugs.launchpad.net/bugs/995102 but it was a error in the/etc/default/locale file on line one . Can i go ahead and mark the bug invalid since the issue is fixed now then.? BTW you can find the errors in the VarLogDistupgradeApttermlog.gz attachment On Wed, May 2, 2012 at 11:16 AM, Maarten Bezemer wrote: > On Wednesday 02 May 2012 08:00:52 Brian Murray wrote: > > On Wed, May 02, 2012 at 04:50:46PM +0200, Marcel Stimberg wrote: > > > Hi Brian, > > > > > > > The example bug report shows how I handled the bug and how they > should > > > > be handled. I indicated that the reporter need to fix line 2 of > their > > > > /etc/environment file and that the bug was Invalid. > > > > > > actually, the linked example bug ( http://launchpad.net/bugs/778504 ) > > > does not have any response and is still at status "New"... > > > > Ah, I see what I did (or didn't) do there. > > > > http://launchpad.net/bugs/984562 > > That explains why I did not understood... :) > I'll take a look at these bugs soon. > > Greetings, > Maarten > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > -------------- next part -------------- An HTML attachment was scrubbed... URL: From m.m.bezemer at utwente.nl Thu May 10 14:16:51 2012 From: m.m.bezemer at utwente.nl (Maarten Bezemer) Date: Thu, 10 May 2012 16:16:51 +0200 Subject: Bitesize Task In-Reply-To: References: <20120501154737.GA2879@murraytwins.com> <1677935.stiXnIh2mg@ce-bzr> Message-ID: <1882218.zFIV70LBmc@ce-bzr> On Thursday 10 May 2012 10:05:44 kurt belgrave wrote: > i found a similar one in https://bugs.launchpad.net/bugs/995102 but it was > a error in the/etc/default/locale file on line one . > > Can i go ahead and mark the bug invalid since the issue is fixed now then.? > > BTW you can find the errors in the VarLogDistupgradeApttermlog.gz attachment Sure, the OP states that you solved his problem. As it turned out it was not a 'real' bug, setting the report to 'Invalid' seems a good choice. Regards, Maarten From brian at ubuntu.com Thu May 10 18:40:40 2012 From: brian at ubuntu.com (Brian Murray) Date: Thu, 10 May 2012 11:40:40 -0700 Subject: Bitesize Task In-Reply-To: References: <20120501154737.GA2879@murraytwins.com> <20120502150052.GC2879@murraytwins.com> <1677935.stiXnIh2mg@ce-bzr> Message-ID: <20120510184040.GA2879@murraytwins.com> On Thu, May 10, 2012 at 10:05:44AM -0400, kurt belgrave wrote: > i found a similar one in https://bugs.launchpad.net/bugs/995102 but it was > a error in the/etc/default/locale file on line one . > > Can i go ahead and mark the bug invalid since the issue is fixed now then.? > > BTW you can find the errors in the VarLogDistupgradeApttermlog.gz attachment Or in DpkgTerminalLog.txt which may also appear in the bug description if it is less than a certain number of lines. Brian -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From milljudgement+ubuntu at hotmail.com Thu May 10 20:17:51 2012 From: milljudgement+ubuntu at hotmail.com (Patrick Santos) Date: Thu, 10 May 2012 16:17:51 -0400 Subject: =?windows-1256?Q?Just_joine?= =?windows-1256?Q?d:_Advice_?= =?windows-1256?Q?before_I_s?= =?windows-1256?Q?tart_makin?= =?windows-1256?Q?g_changes=3F?= =?windows-1256?Q?=FE?= Message-ID: Hello all, I would like to help out working with Ubuntu bugs, and I just joined. Is there a meeting time or other event in the near future for me to sync up with someone on IRC or other live chat to guide me through working on simple tasks for the team? As some background, I am a Masters student with specialization in systems and machine intelligence (a.k.a. "AI"). Despite my "specialization", I try to keep my skills up in low-level programming (assembly, C not plus plus, Java, electronics) like I am now to not cripple my job seeking potential. I have been working with Linux on my home, workstation, and small fileservers since Debian "Sarge" / Ubuntu Dapper. I want to help with Ubuntu development to learn and pad my CV. Note my only experience with Linux is as a USER - my closest to development I've gotten so far is compiling my own kernel for video drivers a few years back. However, I have co-op work experience in both "sides" of bugs - 4+8 months as a tester creating test cases and filing bugs, 4 months as a developer fixing bugs (from other testers). Although I have no triage experience (aside from sending a bug back to triage if it doesn't apply to me), I would like to get involved in triage so I can get a good grasp of how everything "fits together" in the codebase. As noted, I don't want to jump in and make a mess of things, so I would like to have some guidance to get started on some of the easy tasks. Note my location is Canada, EST, but my schedule is extremely flexible at the moment. If a meeting can't be arranged, another idea is assign me some task and I'll report back when I've completed it or need help to complete it. Thank you, Patrick -------------- next part -------------- An HTML attachment was scrubbed... URL: From mathieu.tl at gmail.com Thu May 10 20:36:29 2012 From: mathieu.tl at gmail.com (Mathieu Trudel-Lapierre) Date: Thu, 10 May 2012 13:36:29 -0700 Subject: =?UTF-8?Q?Re=3A_Just_joined=3A_Advice_before_I_start_making_change?= =?UTF-8?Q?s=3F=E2=80=8F?= In-Reply-To: References: Message-ID: On Thu, May 10, 2012 at 1:17 PM, Patrick Santos wrote: [...] > As noted, I don't want to jump in and make a mess of things, so I would like > to have some guidance to get started on some of the easy tasks. Note my > location is Canada, EST, but my schedule is extremely flexible at the > moment. If a meeting can't be arranged, another idea is assign me some task > and I'll report back when I've completed it or need help to complete it. Hi Patrick! Don't be too worried about breaking things -- bug fixing depends on code review if you don't have upload privileges, and there is usually always a way to revert things when there are mistakes -- everyone makes them. Have you read the "How To Triage" wiki pages yet? If not, I encourage you to look them up: https://wiki.ubuntu.com/Bugs/HowToTriage ... And if what you want to do is fixing bugs, there's a page for that too: https://wiki.ubuntu.com/Bugs/HowToFix . On it, the link to Harvest is a great place to start to find things you can try to fix; and to be able to focus on easy fixes, or on specific packages that interest you. Feel free to join in on IRC, in the #ubuntu-bugs channel, that's where the collaboration on triaging bugs is being done. Don't be afraid to ask questions when you're unsure about things :) Regards, Mathieu Trudel-Lapierre Freenode: cyphermox, Jabber: mathieu.tl at gmail.com 4096R/EE018C93 1967 8F7D 03A1 8F38 732E FF82 C126 33E1 EE01 8C93 From trekcaptainusa.tw at gmail.com Sun May 13 16:11:11 2012 From: trekcaptainusa.tw at gmail.com (Thomas Ward) Date: Sun, 13 May 2012 12:11:11 -0400 Subject: [Bug #975197] Validity against 'linux' Message-ID: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/975197 This bug was referenced on IRC in #ubuntu-bugs on freenode. When I looked at this, it was marked 'confirmed' against the 'linux' package. I am not certain it is valid against the 'linux' package, as the package does not necessarily have anything to directly deal with mounting at boot time. Should this be marked as 'Opinion' and then filed as a bug against whatever controls samba mounting? ------ Thomas LP ID: trekcaptainusa-tw Ubuntu Member BugSquad Member -------------- next part -------------- An HTML attachment was scrubbed... URL: From exposito.m at orange.fr Sat May 12 15:13:40 2012 From: exposito.m at orange.fr (Maurice EXPOSITO) Date: Sat, 12 May 2012 17:13:40 +0200 (CEST) Subject: No subject Message-ID: <125788804.131834.1336835620368.JavaMail.www@wwinf1m31> Hi i ve got a problem with ubuntu recently i can't open the ubutu library and i've got this ;message instead   E:Encountered a section with no Package: header, E:Problem with MergeList /var/lib/apt/lists/archive.canonical.com_dists_precise_partner_binary-i386_Packages, E:The package lists or status file could not be parsed or opened.   can someone explain how to do? thank you   Maurice EXPOSITO -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at ubuntu.com Sun May 13 09:21:45 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 13 May 2012 09:21:45 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingScreenLocking/HowScreen?= =?utf-8?q?LockingWorks=22_by_aquaherd?= Message-ID: <20120513092145.16084.74212@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingScreenLocking/HowScreenLockingWorks" page has been changed by aquaherd: http://wiki.ubuntu.com/DebuggingScreenLocking/HowScreenLockingWorks?action=diff&rev1=12&rev2=13 Comment: Details for xubuntu added (This section needs to be completed.) - = XFCE (Xubuntu, Mythbuntu) = + = Xfce 4 (Xubuntu, Mythbuntu) = - (This section needs to be completed.) + Screen locking is handled by the `xflock4` script that is a small command dispatcher to the following commands: + + * `xscreensaver-command` when found `xscreensaver` running + * `gnome-screensaver-command` when found `gnome-screensaver` running + * `slock` when available + * `xlock` when the above three options failed + + First found from the above will be called with the appropriate parameters. ---- CategoryBugSquad From alessandro.menti at hotmail.it Sun May 13 16:38:59 2012 From: alessandro.menti at hotmail.it (Alessandro Menti) Date: Sun, 13 May 2012 18:38:59 +0200 Subject: "Encountered a section with no Package: header" solution (was: ) In-Reply-To: <125788804.131834.1336835620368.JavaMail.www@wwinf1m31> References: <125788804.131834.1336835620368.JavaMail.www@wwinf1m31> Message-ID: Il 12/05/2012 17:13, Maurice EXPOSITO ha scritto: > Hi > > i ve got a problem with ubuntu recently > > i can't open the ubutu library and i've got this ;message instead > > > > E:Encountered a section with no Package: header, E:Problem with MergeList /var/lib/apt/lists/archive.canonical.com_dists_precise_partner_binary-i386_Packages, E:The package lists or status file could not be parsed or opened. > > > > can someone explain how to do? > > thank you > > > > Maurice EXPOSITO > > > > Hi Maurice, this means that there the package list got corrupt in some way while it was downloaded and, as such, it could not be read by apt. Open a Terminal and type (on one line): sudo rm /var/lib/apt/lists/archive.canonical.com_dists_precise_partner_binary-i386_Packages then type "sudo apt-get update" to fix the problem. As a side note, this mailing list is reserved for members of the Ubuntu Bug Squad to discuss existing bug reports. Next time, please use Ubuntu Answers ([1]), the #ubuntu IRC channel ([2]) or Ask Ubuntu ([3]) for these questions. Hope this helps, Alessandro Menti [1] https://answers.launchpad.net/ubuntu [2] https://help.ubuntu.com/community/InternetRelayChat [3] http://askubuntu.com/ -- A neutron walks into a bar and asks how much for a drink. The bartender replies "for you, no charge". -- Sheldon Cooper, The Big Bang Theory From cjk at teamcharliesangels.com Sun May 13 17:01:16 2012 From: cjk at teamcharliesangels.com (Charlie Kravetz) Date: Sun, 13 May 2012 11:01:16 -0600 Subject: [Bug #975197] Validity against 'linux' In-Reply-To: References: Message-ID: <20120513110116.5f4661ee@teamcharliesangels.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 13 May 2012 12:11:11 -0400 Thomas Ward wrote: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/975197 > > This bug was referenced on IRC in #ubuntu-bugs on freenode. > > When I looked at this, it was marked 'confirmed' against the 'linux' > package. > > I am not certain it is valid against the 'linux' package, as the package > does not necessarily have anything to directly deal with mounting at boot > time. > > Should this be marked as 'Opinion' and then filed as a bug against whatever > controls samba mounting? > > ------ > Thomas > LP ID: trekcaptainusa-tw > Ubuntu Member > BugSquad Member No. By clicking on the arrow to the left of the 'Affects', which is linux now, you can change the package name to the correct package. You can also add a new package name, if it affects more than one package. The confirmed can be done automatically by Launchpad now, with whatever criteria is preset. Most bugs go confirmed if there are more than two comments, even though it is supposed to be two different names. - -- Charlie Kravetz Linux Registered User Number 425914 [http://counter.li.org/] Never let anyone steal your DREAM. [http://keepingdreams.com] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAEBAgAGBQJPr+jcAAoJEFNEIRz9dxbAPikH/jNEy+SW+IiU+R/4ClTKxL8q QeJZCU36Y+pq+Cn23Dy52Jkh/4A9xK3aBAalXSp9kJtF7HN0ReSsIuSfLppoFkUy 3bQu/IW6HJksUb3SaNGNHJtRhQX1BnbDoN/cgKQE5cL0WciyM72DRasJwl2PaOQw N55kT0HXNuYe0ftidFatjNrmKVG/x/CEimZ5wDBFqK7/wX6YQxOmKLZJFUZU04yY g/Yuvp9WN9OdogcJAE+ggfqzHLzXWZoYxnCbxAFOpl6qKwaHchogoPlGufyA+K6Y wbdG7H3sB9oQ5fF7lgNe7m8UhIP2zLSqDoviHKdB8hgkM/Rc9Gphhv7Zr1kZiGk= =a9F7 -----END PGP SIGNATURE----- From alo21 at ubuntu-it.org Sun May 13 17:53:52 2012 From: alo21 at ubuntu-it.org (Alessandro Losavio) Date: Sun, 13 May 2012 19:53:52 +0200 Subject: fixing bugs Message-ID: <4FAFF530.6050309@ubuntu-it.org> Hi all, I would like to make Ubuntu better fixing bugs. Could you give me some pages where I can find new bugs (quite easy, if possible), please? Also I would like to know if http://harvest.ubuntu.com/ is active and up to date. Thanks in advance -- Alessandro Losavio email: alo21(at)ubuntu-it.org wiki: http://wiki.ubuntu-it.org/AlessandroLosavio launchpad: https://launchpad.net/~alo21 From jmarsden at fastmail.fm Mon May 14 03:06:08 2012 From: jmarsden at fastmail.fm (Jonathan Marsden) Date: Sun, 13 May 2012 20:06:08 -0700 Subject: fixing bugs In-Reply-To: <4FAFF530.6050309@ubuntu-it.org> References: <4FAFF530.6050309@ubuntu-it.org> Message-ID: <4FB076A0.3000102@fastmail.fm> On 05/13/2012 10:53 AM, Alessandro Losavio wrote: > Hi all, I would like to make Ubuntu better fixing bugs. Could you > give me some pages where I can find new bugs (quite easy, if > possible), please? See https://wiki.ubuntu.com/Bugs/HowToFix for the basic info on how to fix bugs in Ubuntu. Note that bugs tagged with "bitesize" are smaller and easier than most, so those can be a good place to start. It also often helps if you start with a bug in a package you are already familiar with, and use regularly yourself. > Also I would like to know if http://harvest.ubuntu.com/ is active > and up to date. Yes and yes. Have fun! Jonathan From noreply at ubuntu.com Tue May 15 08:45:41 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 15 May 2012 08:45:41 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggerTalk=22_by_rocky-bernste?= =?utf-8?q?in?= Message-ID: <20120515084541.12004.9012@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggerTalk" page has been changed by rocky-bernstein: http://wiki.ubuntu.com/DebuggerTalk?action=diff&rev1=28&rev2=29 Comment: Revice for more recent activity In the practical arena, I could show how to use to debug an GNU automake project. There could be a theoretical area such as how to structure writing a debugger. (The ones for Ruby and Python are interesting here.) - In the past people have asked me in the past, ''"what's the fascination with the debugger thing?"'' Or another favorite remark from a contractor is "''I never use a debugger, I just '''write''' code''". As a systems administrator one is often confronted with lots of code that you didn't write. You suspect the code might not even be written all that well, but you are more sure that there isn't much in the way of documentation or comments in the code. And you've got a problem to solve. Here is where a debugger comes into play. + In the past people have asked me in the past, ''"what's the fascination with the debugger thing?"'' Or another favorite remark from a contractor is "''I never use a debugger, I just '''write''' code''". As a systems administrator one is often confronted with lots of code that you didn't write. You suspect the code might not even be written all that well, but you are more sure that there isn't much in the way of documentation or comments in the code. And you've got a problem to solve. Here is where a debugger comes into play. I've also heard the observation that you don't need a debugger because you go into a Bash, Python or Ruby shell and just start typing statements in the language. Again if you have a high-level idea of what's going on, that's great. However the hardest part here is getting the context correct. I need a `foo` object from class `Foo` and then need to hook the `bar` object from class `Bar` which means importing or requiring module `baz` into `foo` before I can call this method `fubar` that is of interest to me. With a debugger you work on code that purports to work and largely does. So for the most part, most of the necessary setup has been done for you. In a sense a ''good'' debugger is really not all that different than a shell, it's just that the context has already been set up for you. We'll see that in the Python debugger later. - === Why gdb? === + === Why model debuggers off of gdb? === - Because it is + Because it is * fairly complete --- suggests how to expand lesser debuggers (e.g. `pdb` and Ruby's `debug`). For example, consider signal handling. * well known --- learning one helps learn another. It helps ''programs'' learn too! * it's there --- why invent a new interface? Because is GPL can cull from gdb manual, with citation @@ -29, +29 @@ The sordid history of `trap DEBUG`. Originally like other signals, it came ''after'' a statement. But for debugging you need to stop before. Think "`rm -fr /`" and when you'd like to know about it. It took about 2 years after I posted a suggestion for the change to get into bash (and I never got an acknowledgment about this). Debug support was going way too slowly. About 4 years between those releases. - So I forked the bash code to add debug support and timestamped history. This code was incorporated into bash 3.0. Many thanks to Masatake YAMATO. + So I forked the bash code to add debug support and timestamped history. This code was incorporated into bash 3.0. Many thanks to Masatake YAMATO. === Practical example === @@ -37, +37 @@ * Using to debug SYSV start/stop scripts. * debugger `set_trace` trick? ''Note: `set_trace` is depricated in favor of `debugger`'' - Note: if you are going to debug `configure` scripts, you want the `readarray` builtin. + Note: if you are going to debug `configure` scripts, you want the `readarray` builtin. ''This has since been encorporated into bash 4.0 and is not needed in that and later versions'' - At this point we should have seen three paradigms of debugging that will come up over again in the other debuggers: + At this point we should have seen three paradigms of debugging that will come up over again in the other debuggers: * line tracing * invoking from the debugger at the outset * calling the debugger (somehow) from inside the program. @@ -49, +49 @@ === Work since the talk === - In 2008, I did something in between a port and a rewrite of this to support `ksh` and `zsh`. As before, changes were needed in the shells themselves to support more accurate location reporting and to be able to do more program introspection. Much to my delight, these enhancements were done quickly and with little involvement on my part. But this means you do need a recent release of these shells. The debugger code is maintained on `github`. See [[http://github.com/rocky/zshdb]] and [[http://github.com/rocky/kshdb]]. + In 2008, I did something in between a port and a rewrite of this to support `ksh` and `zsh` and colorized output via *pygments*. As before, changes were needed in the shells themselves to support more accurate location reporting and to be able to do more program introspection. Much to my delight, these enhancements were done quickly and with little involvement on my part. But this means you do need a recent release of these shells. The debugger code is maintained on `github`. See [[http://github.com/rocky/zshdb]] and [[http://github.com/rocky/kshdb]]. - + == GNU make == - I have a short (13 minute) [[http://showmedo.com/videos/video?name=linuxBernsteinMakeDebug1&fromSeriesID=40|video]] which is really intended to be the first part of a more extended example. + I have a short (13 minute) [[http://showmedo.com/videos/video?name=linuxBernsteinMakeDebug1&fromSeriesID=40|video]] which is really intended to be the first part of a more extended example. === Historical stuff === - It's [[http://freshmeat.net/articles/view/889/#comment-31152|deja vu all over again]]. Lessons learned in forking a project + It's [[http://freshmeat.net/articles/view/889/#comment-31152|deja vu all over again]]. What needed to be done (same as in bash): * better position location reporting @@ -71, +71 @@ * run again with `remake -x` * if above doesn't work narrow target and run with `remake -X` ''target'' - Show: + Show: * make basic debugging: `make -d basic` * make tracing: `remake -x` @@ -79, +79 @@ * 'step' and 'next' * showing dependencies and `write` command * Debugging a automake-generated Makefile. - + === Future === @@ -91, +91 @@ === Historical stuff === - There are two gdb-like debuggers. The stock python debugger, [[http://docs.python.org/lib/module-pdb.html|pdb]], and one that grew from that, called `pydb`. The name `pydb` is because at about the time `pdb` was developed Richard Wolff was working in parallel on a debugger to be embedded on [[http://www.gnu.org/software/ddd|ddd]]. He has since retired and with his blessing I've taken over the name and have been sort of maintaining the ddd embedding as well. + There are two gdb-like debuggers. The stock python debugger, [[http://docs.python.org/lib/module-pdb.html|pdb]], and one that grew from that, called `pydb`. The name `pydb` is because at about the time `pdb` was developed Richard Wolff was working in parallel on a debugger to be embedded on [[http://www.gnu.org/software/ddd|ddd]]. He has since retired and with his blessing I've taken over the name and have been sort of maintaining the ddd embedding as well. - Stack frame display dilemma: do Python programmers draw their trees with the [[http://groups.google.com/group/comp.lang.python/browse_thread/thread/90cbcd03f37294a1/caa85f727c28353a|roots at the bottom]]? + Stack frame display dilemma: do Python programmers draw their trees with the [[http://groups.google.com/group/comp.lang.python/browse_thread/thread/90cbcd03f37294a1/caa85f727c28353a|roots at the bottom]]? === Practical example === - I have a short 15-minute [[http://showmedo.com/videos/video?name=pythonBernsteinPydbIntro&fromSeriesID=28|video]] showing off some non-pdb things. + I have a short 15-minute [[http://showmedo.com/videos/video?name=pythonBernsteinPydbIntro&fromSeriesID=28|video]] showing off some non-pdb things. Example: how `ipython` handles `help` --- signal handling (initially added by Matt Fleming as part of a Google 2006 Summer-of-code project. Possibly some of the thread debugging features. @@ -106, +106 @@ Integration into [[http://ipython.scipy.org/moin/|ipython]] was recently done. Release 1.21 added a number of usability conveniences like better command completion, and [[http://docs.python.org/lib/module-pydoc.html|pydoc]] help. - Remote debugging. This is needed to hook into many IDEs like Eric, IDLE, winpdb (and therefore SPE), and Eclipse. The bad news though is that each IDE has defined it's own protocol for working remotely. + Remote debugging. This is needed to hook into many IDEs like Eric, IDLE, winpdb (and therefore SPE), and Eclipse. The bad news though is that each IDE has defined it's own protocol for working remotely. In late 2008, I started working on a complete rewrite. Some features planned: @@ -114, +114 @@ * much more modular (and more along the lines of `ruby-debug`) * distribution via egg package(s) + ''Code is available at http://code.google.com/p/pydbgr/'' + == Ruby == There are in fact two ruby debuggers. `debug` which comes with the base Ruby install and [[http://rubyforge.org/projects/ruby-debug/|ruby-debug]] by Kent Sibilev. Both are roughly gdb like. Kent's debugger is I think is coded the cleanest of any debugger I've seen (although it does have some warts). Each command is its own class. By way of comparison, - in the stock python debugger a command module is used. Commands are methods in this (sub)class whose names start with the "do_". This is a pattern akin to one used in unit testing where tests start with "test_". But having a class per command is cooler. It means that commands can have ''properties''. One property in `ruby-debug` is whether you can run this command if the program has crashed. (The `help` command you can run, but the `step` command you can't). + in the stock Python debugger a command module is used. Commands are methods in this (sub)class whose names start with the "do_". This is a pattern akin to one used in unit testing where tests start with "test_". But having a class per command is cooler. It means that commands can have ''properties''. One property in `ruby-debug` is whether you can run this command if the program has crashed. (The `help` command you can run, but the `step` command you can't). === Practical Example === - `require 'debug'` trick? Stopping in a Rails unit test. + `require 'debug'` trick? Stopping in a Rails unit test. ''Note: since this talk, `ruby-debug` has become the de-facto debugger that is used in Ruby, JRuby, Ruby/Rails, merb and other frameworks. The successor to the `require 'debug'` trick is now `require 'ruby-debug/debugger'` or some variation of that. See [[http://bashdb.sourceforge.net/ruby-debug.html#SEC18|Calling the debugger from inside your Ruby Program]] and [[http://bashdb.sourceforge.net/ruby-debug.html#SEC72|The Debugger Module]] for even more detail.'' @@ -132, +134 @@ * Documentation (largely done in 2007; see [[http://bashdb.sf.net/ruby-debug.html]] and [[http://bashdb.sf.net/ruby-debug/index.html]]) * Regression tests. (Largely done in 2007.) * More closely like gdb (Much progress here too; caused some incompatible changes.) - * Complete rewrite for Ruby 1.9? + * Complete rewrite for Ruby 1.9? ''This code is avaliable at https://github.com/rocky/rb-trepanning'' ---- CategoryDebugging From noreply at ubuntu.com Tue May 15 09:24:34 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 15 May 2012 09:24:34 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22LibreOfficeBugWrangling=5Fit=22_?= =?utf-8?q?by_fabiomarconi?= Message-ID: <20120515092434.17894.81402@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "LibreOfficeBugWrangling_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/LibreOfficeBugWrangling_it?action=diff&rev1=1&rev2=2 Comment: Italian translation * Per cortesia non riportare più di un bug per ogni segnalazione. * Per cortesia evitare commenti sul tempo necessario alla riparazione, specialmente se non si sono seguiti i fondamentali passi di debugging in seguito descritti. Siate consapevoli che noi tutti vorremmo vedere i bug riparati immediatamente, ma purtroppo gli ostacoli maggiori si incontrano nella riproducibilità e chiarezza della segnalazione. - = Debugging Procedure = - == Document Issues == + = Procedure per il debugging = + == Problemi con il documento == - === Bug importing a non-MS Office document === - * If you are reporting about importing a non-MS Office document, please attach the document to the bug report before opening in LibreOffice or in any other program. As well, please post a screenshot of how it looks in LibreOffice with a specific description about how it should look. + === Anomalia importando un documento non-MS Office === + * Se si intende riportare un bug che riguarda un documento non-MS Office, siete pregati di allegare il file alla segnalazione prima di averlo aperto con LibreOffice o qualsiasi altro programma. Si prega inoltre di allegare uno screenshot di come questo file appare in libreOffice ed una specifica descrizione di come invece dovrebbe apparire. - === Bug exporting to MS Office === - * If you are reporting about how a document looks different exporting to MS Office, please attach the document to the bug report immediately after saving via LibreOffice, but before opening in MS Office. As well, please post a screenshot of how it looks in LibreOffice and then how it shows in MS Office. + === Anomalie esportando in MS Office === + * Se si sta segnalando un'anomalia inerente un documento che viene visualizzato diverso esportandolo in MS Office, vi preghiamo di allegarlo alla segnalazione immediatamente dopo l'esportazione via LibreOffice. Inoltre allgare uno screenshot di come il documento appare in LibreOffice ed uno di come viene visualizzato inp MS Office. - === Bug Importing from MS Office === - * If you are reporting about how a document looks importing from MS Office, please save the file in MS Office, then before opening in any other program, attach the document to the bug report. As well, please post a screenshot of how it looks in LibreOffice and then how it shows in MS Office. + === Anomalie importando da MS Office === + * Se si sta segnalando un'anomalia riguardo a come un documento viene visualizzato se importato da MS Office, siete pregati di salvarlo in formato MS Office, quindi prima di aprirlo con qualsiasi altro programma, allegarlo alla segnalazione. Inoltre allegare uno screenshot di come il documento appare in LibreOffice e di come appare in MS Office. - === Bug Exporting to Adobe PDF === - * If you are reporting about how a document looks exporting to Adobe Reader, please attach the file to the bug report before and after exporting to PDF. As well, provide screenshots of how it looks in LibreOffice and Adobe Reader. + === Anomalie esportando in Adobe PDF === + * Se si sta segnalando un anomalia riguardo a come un documento viene visualizzato se esportato in formato Adobe Reader, siete pregati di allegare il file alla segnalazione prima e dopo l'esportazione in formato PDF. Inoltre allegare uno screenshot di come viene visualizzato sia in LibreOffice che in Adobe Reader. - === Bug Importing PDF === - * If you are reporting about how a PDF document looks importing into Draw, please attach the file to the bug report before importing into Draw. As well, provide screenshots of how it looks in LibreOffice and Adobe Reader. + === Anomalie importando PDF === + * Se si sta segnalando un'anomalia riguardo a come un documento PDF viene visualizzato iportandolo in Draw, siete pregati di allegare il file alla segnalazione prima di averlo importato in Draw. Inoltre, allegare uno screenshot di come il documento è visualizzato sia in LibreOffice che in Adobe Reader. - == Printing == - * For issues printing from LibreOffice please report this against cups first via the Terminal: <
> {{{ubuntu-bug cups}}} <
> <
> It could end up being an issue with LibreOffice, but it's best to start with cups in order to rule it out. As well, please follow all steps noted in https://wiki.ubuntu.com/DebuggingPrintingProblems . + == Stampa == + * Per problemi durante la stampa con LibreOffice, vi preghiamo di aprire la segnalazione dapprima contro cups via terminale: <
> {{{ubuntu-bug cups}}} <
> <
> Potrebbe anche essere un problema in LibreOffice, ma è meglio iniziare da cups in modo da poterlo così escludere. Inoltre vi preghiamo di seguire le istruzioni contenute in [[https://wiki.ubuntu.com/DebuggingPrintingProblems_it|DebuggingPrintingProblems_it]] . - == Crashes == + == Crash == - === LibreOffice Crashes but System Still Functional === - * For instances when only LibreOffice crashes but you can still use the OS without hard rebooting, please report this via via Apport and ensure you have all the LibreOffice debug symbols installed (libreoffice-dbg, uno-libs3-dbg, and ure-dbg). For more on this please see https://wiki.ubuntu.com/Apport . As well, if this happened while a particular document was open or you were manipulating the document, please attach that document to the bug report with detailed, click-for-click steps on how to reproduce the crash. - * In the rare instance that after you followed the above, apport did not kick in, please provide a backtrace, valgrind, and strace following https://wiki.ubuntu.com/DebuggingProgramCrash . + === LibreOffice crasha ma il sistema rimane funzionante === + * Nei casi in cui solamente LibreOffice crasha ed il sistema rimane comunque funzionante, vi preghiamo di segnalare il bug utilizzando [[https://wiki.ubuntu.com/Apport_it|Apport]] assicurandosi di avere preventivamente installato i simboli di debug (libreoffice-dbg, uno-libs3-dbg, and ure-dbg). Inoltre, se il bug si verifica durante l'apertura di un particolare documento o la sua lavorazione, vi preghiamo di allegarlo alla segnalazione fornendo anche una dettagliata descrizione, click per click, su come riprodurre il crash. + * Nei rari casi che anche seguendo la procedura sopraelencata Apport non si avvii, vi preghiamo di allegare alla segnalazione un backtrace, valgrind e strace seguendo le istruzioni in [[https://wiki.ubuntu.com/DebuggingProgramCrash_it|DebuggingProgramCrash_it]]. === The Whole System Hangs or Boots to the Login Screen === * For instances when your using LibreOffice and either the system hangs requiring a hard reset or your booted to the login screen, this is a bug in either xorg or the kernel. Please follow https://help.ubuntu.com/community/DebuggingSystemCrash . As well, if this happened while a particular document was open or you were manipulating the document, please attach that document to the bug report with detailed, click-for-click steps on how to reproduce the crash. From noreply at ubuntu.com Tue May 15 11:04:55 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 15 May 2012 11:04:55 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22LibreOfficeBugWrangling=5Fit=22_?= =?utf-8?q?by_fabiomarconi?= Message-ID: <20120515110455.7439.1327@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "LibreOfficeBugWrangling_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/LibreOfficeBugWrangling_it?action=diff&rev1=2&rev2=3 Comment: Italian translation done * Nei casi in cui solamente LibreOffice crasha ed il sistema rimane comunque funzionante, vi preghiamo di segnalare il bug utilizzando [[https://wiki.ubuntu.com/Apport_it|Apport]] assicurandosi di avere preventivamente installato i simboli di debug (libreoffice-dbg, uno-libs3-dbg, and ure-dbg). Inoltre, se il bug si verifica durante l'apertura di un particolare documento o la sua lavorazione, vi preghiamo di allegarlo alla segnalazione fornendo anche una dettagliata descrizione, click per click, su come riprodurre il crash. * Nei rari casi che anche seguendo la procedura sopraelencata Apport non si avvii, vi preghiamo di allegare alla segnalazione un backtrace, valgrind e strace seguendo le istruzioni in [[https://wiki.ubuntu.com/DebuggingProgramCrash_it|DebuggingProgramCrash_it]]. - === The Whole System Hangs or Boots to the Login Screen === - * For instances when your using LibreOffice and either the system hangs requiring a hard reset or your booted to the login screen, this is a bug in either xorg or the kernel. Please follow https://help.ubuntu.com/community/DebuggingSystemCrash . As well, if this happened while a particular document was open or you were manipulating the document, please attach that document to the bug report with detailed, click-for-click steps on how to reproduce the crash. + === Il sistema si blocca o compare la schermata di login === + * Nel caso in cui, utilizzando LibreOffice, il sistema si blocca o si riavvia la sessione si è di fronte ad un bug relativo a Xorg o al kernel. Si prega di consultare https://help.ubuntu.com/community/DebuggingSystemCrash . Inoltre, se ciò accade durante l'apertura o la lavorazione di un particolare documento, vi preghiamo di allegarlo alla segnalazione fornendo anche una dettagliata descrizione, click per click, su come riprodurre il crash. - == Regressions == + == Regressioni == - * For regressions, it is helpful to perform a binary bisect ("bibisect") to narrow down which commit specifically caused the problem. For instructions please see http://sweetshark.livejournal.com/7683.html . + * Per le regressioni, è di valido aiuto eseguire un binary bisect ("bibisect") per isolare la specifica commit che ha introdotto il bug. Per istruzioni vedere http://sweetshark.livejournal.com/7683.html . - == Wishlists == - * For Wishlist reports, many of these are requests to implement a feature in LibreOffice found in MS Office. A broad but good rule of thumb is if you want LibreOffice to do something that MS Office does (MS Office compatibility expectation), please document how specifically MS Office does it, then how LibreOffice does not or does not do well that which you desire. Please keep in mind, pocket cases exist where LibreOffice intentionally does not do what MS Office does (ex. leap year implementation https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/456100). + == Implementazioni == + * Usare le segnalazioni per l'implementazione in Libreoffice di una caratteristica presente in MS Office se si vuole ottenenere la stessa funzionalità (aspettativa di compatibilità con MS Office). Vi preghiamo di documentare specificamente come viene svolta da MS Office e quindi come LibreOfficenon la svolge o la svolge differentemente. Ricordiamo che in alcuni casi Libreoffice, intenzionalmente, non si comporta come MS Office (es. implementare il salto dell'anno https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/456100). - = Triaging LibreOffice Bugs = + = Triaging dei bug in LibreOffice = - == Writer and Calc == + == Writer e Calc == - * For bugs in Writer, it is helpful to check to see if the problem exists in AbiWord. For bugs in Calc, it is helpful to check to see if the problem exists in Gnumeric. Sometimes, AbiWord and Gnumeric give the bug reporter a usable workaround to the problem (and vice versa). If a workaround is found, feel free to document it in the report. As well, while not quite apples and oranges code wise, it gives LibreOffice developers code to base a patch on. + * Per i bug in Writer, è buona norma verificare su il bug si presenta anche in Abiword, mentre per i bug in Calc verificare se presenti anche in Gnumeric. Talvolta, AbiWord e Gnumeric forniscono un valida soluzione temporanea al problema (e vice versa). Se si trova una soluzione temporanea, si prega di documentarla nella segnalazione. Potrebbe anche fornire agli sviluppatori LibreOffice una base di codice per sviluppare una patch. - == Wishlist Reports == - * For Wishlist reports, they most likely should be marked Won't Fix Wishlist. This is due to how Ubuntu diverts very little from the LibreOffice upstream source release, and upstream's rapid maintenance cadence. <
> A Won't Fix Wishlist stock reply: + == Segnalazioni Wishlist == + * Per le segnalazioni Wishlist, esse saranno marcate Won't Fix Wishlist. Ciò è dovuto al fatto che la versione Ubuntu differisce molto poco dal rilascio upstream ed upstream ha una cadenza di manutenzione rapida. <
> A Won't Fix Wishlist stock reply: ||Thank you for reporting this and helping making Ubuntu better. Regarding this report:<
>- This is a clearcut upstream issue. Your welcome to send this to the developers of the software by following the instructions at http://wiki.documentfoundation.org/BugReport . If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status.<
>- Marking LibreOffice Packaging and libreoffice (Ubuntu) => Won't Fix Wishlist. This does not mean the issue will not be cared about, but if it is cared about (even by Ubuntu/Canonical contributors), it is done upstream at LibreOffice.|| - == How to Forward Bugs Upstream == + == Come avanzare i bug Upstream == - * Once marked Triaged, a report may be filed upstream using the [[https://www.libreoffice.org/get-help/bug/|LibreOffice Bug Submission Assistant]] <>. + * Una volta marcata Triaged, una segnalazione potrà essere inviata upstream utilizzando il [[https://www.libreoffice.org/get-help/bug/|LibreOffice Bug Submission Assistant]] <>. - * Once a remote bug watch has been added to a bug report, it is helpful to append [Upstream] to the beginning of the bug title. This helps in searching for bugs reports by title. Please do not append this unless a remote bug watch has been added to the report as this creates confusion on which bugs have been reported upstream and which have not. + * Dopo che un remote bug watch è stato aggiunto alla segnalazione, è utile farne precedere il titolo da [Upstream]. Ciò aiuterà nella ricerca delle segnalazioni in funzione del titolo. Per cortesia non aggiungere [Upstream] fino a quando un remote bug watch è stato aggiunto alla segnalazione onde evitare di creare confusione tra i bug segnalati upstream e quelli no. ---- CategoryBugSquad From trekcaptainusa.tw at gmail.com Wed May 16 01:21:32 2012 From: trekcaptainusa.tw at gmail.com (Thomas Ward) Date: Tue, 15 May 2012 21:21:32 -0400 Subject: Core vs. Non-Core definitions Message-ID: Hiya, all. This came up (during UDS) in a discussion I had with micahg on IRC, and came up again today in #ubuntu-bugs with roadmr. (NOTE: These are the users' IRC nicks, I do not have their names readily available) The definition of a bug's importance includes the difference between core and non-core on this page here: https://wiki.ubuntu.com/Bugs/Importance There is currently no clear definition of what core or non-core means. At every time I have run into a bug that needs its importance set, I've avoided identifying whether a bug is related to a core or non-core program (except for Universe and Multiverse package bugs), simply because there is no clear-cut definition of what is or is not core. This lack of a definition can sometimes make a recommendation for "medium" actually end up as "low", and vice versa, based on core-vs-noncore. This makes determining importance that much more difficult. Since this is a critical part of determining a bug's importance, we need to, in my opinion, do one of the following:: (a) clearly define what applications specifically are or are not core, and update with each release, or (b) define what constitutes a core or non-core application/program, or (c) rewrite the criterion (and therefore the guide) to remove the difference of core vs. non-core and redefine the bug importance criterion accordingly. micahg was in agreement with me that this needs to be defined, so I thought I would bring this onto the mailing list for discussion and potentially a final decision be made on this. So, thoughts? Opinions? ------ Thomas LP: trekcaptainusa-tw BugSquad Member Ubuntu Member -------------- next part -------------- An HTML attachment was scrubbed... URL: From trekcaptainusa.tw at gmail.com Wed May 16 02:22:38 2012 From: trekcaptainusa.tw at gmail.com (Thomas Ward) Date: Tue, 15 May 2012 22:22:38 -0400 Subject: Core vs. Non-Core definitions In-Reply-To: References: Message-ID: Whoops, this once again got direct-sent to the person i was replying to... ---------- Forwarded message ---------- From: Thomas Ward Date: Tue, May 15, 2012 at 10:13 PM Subject: Re: Core vs. Non-Core definitions To: Geoffrey Van Wyk How would we handle kubuntu-desktop packages? or xubuntu-desktop packages? If we restrict core to just ubuntu-desktop, then would bugs which would be "Medium" against Kubuntu or Xubuntu packages automatically be "Low" because at that point they're non-core? I'm in agreement, any package that is a dependency against [flavor]-desktop should be considered core, but it would be important to handle all the flavors of Ubuntu similarly, no? ------ Thomas LP: trekcaptainusa-tw BugSquad Member Ubuntu Member On Tue, May 15, 2012 at 9:39 PM, Geoffrey Van Wyk < geoffrey.vanwyk at bernadine.biz> wrote: > Hi all, > > Maybe a core application could be one which is a dependency for the > ubuntu-desktop package. One such application is Gwibber. > > Geoffrey > > > > -------- Original message -------- > Subject: Core vs. Non-Core definitions > From: Thomas Ward > To: ubuntu-bugsquad at lists.ubuntu.com > CC: > > > Hiya, all. > > This came up (during UDS) in a discussion I had with micahg on IRC, and > came up again today in #ubuntu-bugs with roadmr. (NOTE: These are the > users' IRC nicks, I do not have their names readily available) > > The definition of a bug's importance includes the difference between core > and non-core on this page here: https://wiki.ubuntu.com/Bugs/Importance > > > There is currently no clear definition of what core or non-core means. At > every time I have run into a bug that needs its importance set, I've > avoided identifying whether a bug is related to a core or non-core program > (except for Universe and Multiverse package bugs), simply because there is > no clear-cut definition of what is or is not core. > > This lack of a definition can sometimes make a recommendation for "medium" > actually end up as "low", and vice versa, based on core-vs-noncore. This > makes determining importance that much more difficult. > > Since this is a critical part of determining a bug's importance, we need > to, in my opinion, do one of the following:: > (a) clearly define what applications specifically are or are not core, and > update with each release, or > (b) define what constitutes a core or non-core application/program, or > (c) rewrite the criterion (and therefore the guide) to remove the > difference of core vs. non-core and redefine the bug importance criterion > accordingly. > > micahg was in agreement with me that this needs to be defined, so I > thought I would bring this onto the mailing list for discussion and > potentially a final decision be made on this. > > > So, thoughts? Opinions? > > ------ > Thomas > LP: trekcaptainusa-tw > BugSquad Member > Ubuntu Member > -------------- next part -------------- An HTML attachment was scrubbed... URL: From geoffrey.vanwyk at bernadine.biz Wed May 16 13:35:34 2012 From: geoffrey.vanwyk at bernadine.biz (Geoffrey van Wyk) Date: Wed, 16 May 2012 15:35:34 +0200 Subject: Core vs. Non-Core definitions In-Reply-To: References: Message-ID: <4FB3AD26.9070401@bernadine.biz> On 16/05/2012 04:22, Thomas Ward wrote: > Whoops, this once again got direct-sent to the person i was replying to... > > ---------- Forwarded message ---------- > From: *Thomas Ward* > > Date: Tue, May 15, 2012 at 10:13 PM > Subject: Re: Core vs. Non-Core definitions > To: Geoffrey Van Wyk > > > > How would we handle kubuntu-desktop packages? or xubuntu-desktop > packages? If we restrict core to just ubuntu-desktop, then would bugs > which would be "Medium" against Kubuntu or Xubuntu packages > automatically be "Low" because at that point they're non-core? > > I'm in agreement, any package that is a dependency against > [flavor]-desktop should be considered core, but it would be important > to handle all the flavors of Ubuntu similarly, no? > > > ------ > Thomas > LP: trekcaptainusa-tw > BugSquad Member > Ubuntu Member > > On Tue, May 15, 2012 at 9:39 PM, Geoffrey Van Wyk > > > wrote: > > Hi all, > > Maybe a core application could be one which is a dependency for > the ubuntu-desktop package. One such application is Gwibber. > > Geoffrey > > > > -------- Original message -------- > Subject: Core vs. Non-Core definitions > From: Thomas Ward > > To: ubuntu-bugsquad at lists.ubuntu.com > > CC: > > > Hiya, all. > > This came up (during UDS) in a discussion I had with micahg on > IRC, and came up again today in #ubuntu-bugs with roadmr. (NOTE: > These are the users' IRC nicks, I do not have their names readily > available) > > The definition of a bug's importance includes the difference > between core and non-core on this page here: > https://wiki.ubuntu.com/Bugs/Importance > > > There is currently no clear definition of what core or non-core > means. At every time I have run into a bug that needs its > importance set, I've avoided identifying whether a bug is related > to a core or non-core program (except for Universe and Multiverse > package bugs), simply because there is no clear-cut definition of > what is or is not core. > > This lack of a definition can sometimes make a recommendation for > "medium" actually end up as "low", and vice versa, based on > core-vs-noncore. This makes determining importance that much more > difficult. > > Since this is a critical part of determining a bug's importance, > we need to, in my opinion, do one of the following:: > (a) clearly define what applications specifically are or are not > core, and update with each release, or > (b) define what constitutes a core or non-core > application/program, or > (c) rewrite the criterion (and therefore the guide) to remove the > difference of core vs. non-core and redefine the bug importance > criterion accordingly. > > micahg was in agreement with me that this needs to be defined, so > I thought I would bring this onto the mailing list for discussion > and potentially a final decision be made on this. > > > So, thoughts? Opinions? > > ------ > Thomas > LP: trekcaptainusa-tw > BugSquad Member > Ubuntu Member > > > > > I agree with you. I did not think about the other desktops. -- Geoffrey van Wyk *Bernadine Software* /Email: geoffrey.vanwyk at bernadine.biz /Cell: 083 387 3458// -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2336 bytes Desc: S/MIME Cryptographic Signature URL: From maarten.bezemer at gmail.com Thu May 17 09:57:18 2012 From: maarten.bezemer at gmail.com (Maarten Bezemer) Date: Thu, 17 May 2012 11:57:18 +0200 Subject: New message for Bug/Responses#Release_has_reached_EOL Message-ID: <1751043.NCpg2i7bRq@i7> Hi, I would like to propose this text as the default message for Bug/Responses#Release_has_reached_EOL: Thank you for reporting this bug to Ubuntu. RELEASE reached EOL on DATE. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases I've tried recreating this bug with RELEASE and was unable to, given the information you've provided. Please either a) upgrade and test or b) increase the verbosity of the steps to recreate it so we can try again. Do feel free to report any other bugs you may find. I removed some 'please' words from the text, as I often do not include"I've tried recreating this bug with RELEASE and was unable to, given the information you've provided." because the issue is really too old or impossible to retry. When removing that part, there are 3 sentences starting with 'Please' directly under each other in the current default message. Any opinions about this proposed change? Is it too commanding/demanding without the 'Please' words? Regards, Maarten From fco.plj at gmail.com Thu May 17 12:59:28 2012 From: fco.plj at gmail.com (P.L. Francisco Javier) Date: Thu, 17 May 2012 07:59:28 -0500 Subject: New message for Bug/Responses#Release_has_reached_EOL In-Reply-To: <1751043.NCpg2i7bRq@i7> References: <1751043.NCpg2i7bRq@i7> Message-ID: It looks good for me, +1 On May 17, 2012 4:57 AM, "Maarten Bezemer" wrote: > Hi, > > I would like to propose this text as the default message for > Bug/Responses#Release_has_reached_EOL: > > Thank you for reporting this bug to Ubuntu. RELEASE reached EOL on DATE. > See this document for currently supported Ubuntu releases: > https://wiki.ubuntu.com/Releases > > I've tried recreating this bug with RELEASE and was unable to, given the > information you've provided. Please either a) upgrade and test or b) > increase the verbosity of the steps to recreate it so we can try again. > > Do feel free to report any other bugs you may find. > > > I removed some 'please' words from the text, as I often do not > include"I've tried recreating this bug with RELEASE and was unable to, > given the information you've provided." because the issue is really too old > or impossible to retry. > When removing that part, there are 3 sentences starting with 'Please' > directly under each other in the current default message. > > Any opinions about this proposed change? Is it too commanding/demanding > without the 'Please' words? > > Regards, > Maarten > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > -------------- next part -------------- An HTML attachment was scrubbed... URL: From george.patterson at gmail.com Thu May 17 13:19:52 2012 From: george.patterson at gmail.com (George Patterson) Date: Thu, 17 May 2012 23:19:52 +1000 Subject: New message for Bug/Responses#Release_has_reached_EOL In-Reply-To: References: <1751043.NCpg2i7bRq@i7> Message-ID: I also agree with the idea except that it should be a requirement to upgrade before re-testing otherwise those triaging will required to run a now EOL install (even a VM) in order to confirm the steps required to reproduce the bug and then do the same thing with the current release to check if it has been fixed or no longer an issue. The developers and other interested people will also need access to the older version of the release. This is assuming that I have read the proposed wording correctly. Regards George On 17 May 2012 22:59, P.L. Francisco Javier wrote: > It looks good for me, +1 > > On May 17, 2012 4:57 AM, "Maarten Bezemer" > wrote: >> >> Hi, >> >> I would like to propose this text as the default message for >> Bug/Responses#Release_has_reached_EOL: >> >> Thank you for reporting this bug to Ubuntu. RELEASE reached EOL on DATE. >> See this document for currently supported Ubuntu releases: >> https://wiki.ubuntu.com/Releases >> >> I've tried recreating this bug with RELEASE and was unable to, given the >> information you've provided. Please either a) upgrade and test or b) >> increase the verbosity of the steps to recreate it so we can try again. >> >> Do feel free to report any other bugs you may find. >> >> >> I removed some 'please' words from the text, as I often do not >> include"I've tried recreating this bug with RELEASE and was unable to, given >> the information you've provided." because the issue is really too old or >> impossible to retry. >> When removing that part, there are 3 sentences starting with 'Please' >> directly under each other in the current default message. >> >> Any opinions about this proposed change? Is it too commanding/demanding >> without the 'Please' words? >> >> Regards, >>  Maarten >> >> -- >> Ubuntu-bugsquad mailing list >> Ubuntu-bugsquad at lists.ubuntu.com >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > From maarten.bezemer at gmail.com Thu May 17 14:25:52 2012 From: maarten.bezemer at gmail.com (Maarten Bezemer) Date: Thu, 17 May 2012 16:25:52 +0200 Subject: New message for Bug/Responses#Release_has_reached_EOL In-Reply-To: References: <1751043.NCpg2i7bRq@i7> Message-ID: <20897767.WNYmegalzW@i7> I agree with the requirement to update to a non-EOL version, I had been wondering about this earlier as well. It was already in the original text and I did not want to modify it too much. How about this: Thank you for reporting this bug to Ubuntu. RELEASE reached EOL on DATE. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases I've tried recreating this bug with RELEASE and was unable to, given the information you've provided. Please upgrade, test again and if required increase the verbosity or update of the steps to reproduce it so we can try again. Do feel free to report any other bugs you may find. So it is (more) explicit that the OP should update to a non-EOL version before increasing the verbosity of the steps to reproduce. Regards, Maarten On Thursday 17 May 2012 23:19:52 George Patterson wrote: > I also agree with the idea except that it should be a requirement to > upgrade before re-testing otherwise those triaging will required to > run a now EOL install (even a VM) in order to confirm the steps > required to reproduce the bug and then do the same thing with the > current release to check if it has been fixed or no longer an issue. > The developers and other interested people will also need access to > the older version of the release. > > This is assuming that I have read the proposed wording correctly. > > Regards > > > George > > On 17 May 2012 22:59, P.L. Francisco Javier wrote: > > It looks good for me, +1 > > > > On May 17, 2012 4:57 AM, "Maarten Bezemer" > > wrote: > >> > >> Hi, > >> > >> I would like to propose this text as the default message for > >> Bug/Responses#Release_has_reached_EOL: > >> > >> Thank you for reporting this bug to Ubuntu. RELEASE reached EOL on DATE. > >> See this document for currently supported Ubuntu releases: > >> https://wiki.ubuntu.com/Releases > >> > >> I've tried recreating this bug with RELEASE and was unable to, given the > >> information you've provided. Please either a) upgrade and test or b) > >> increase the verbosity of the steps to recreate it so we can try again. > >> > >> Do feel free to report any other bugs you may find. > >> > >> > >> I removed some 'please' words from the text, as I often do not > >> include"I've tried recreating this bug with RELEASE and was unable to, given > >> the information you've provided." because the issue is really too old or > >> impossible to retry. > >> When removing that part, there are 3 sentences starting with 'Please' > >> directly under each other in the current default message. > >> > >> Any opinions about this proposed change? Is it too commanding/demanding > >> without the 'Please' words? > >> > >> Regards, > >> Maarten > >> > >> -- > >> Ubuntu-bugsquad mailing list > >> Ubuntu-bugsquad at lists.ubuntu.com > >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > > > > > -- > > Ubuntu-bugsquad mailing list > > Ubuntu-bugsquad at lists.ubuntu.com > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > From noreply at ubuntu.com Thu May 17 10:33:20 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Thu, 17 May 2012 10:33:20 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Responses=22_by_fabiomarcon?= =?utf-8?q?i?= Message-ID: <20120517103320.1242.32962@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Responses" page has been changed by fabiomarconi: http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=348&rev2=349 Determining whether a bug report is actually a support request can be quite challenging, but if you decide the bug is a support request you can convert it to such by clicking "Convert to a question" at the top of the bug's web page. This will mark the bug as "Invalid", create a new question in the answer tracker and link it to the bug. In the comment dialog that you receive, post a comment to inform the reporter about your action, and advise them to use the support tracker for any future problems. - || Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We understand the difficulties you are facing, but it is better to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. You can also find a valid support at http://askubuntu.com or posting your question in the support forum of your local Ubuntu's community. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs.|| + || Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We understand the difficulties you are facing, but it is better to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. You can also find a valid help posting your problem in the support forum of your [[http://loco.ubuntu.com/|local Ubuntu's community]] or asking at http://askubuntu.com. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs.|| It is also a good idea to change the source package beforehand if it's set incorrectly, so that the question will be associated with the correct package in the answer tracker, or edit the question afterwards and assign it to the correct package. If it doesn't pertain to a specific package, change it to "Ubuntu". From corbellini.andrea at gmail.com Thu May 17 14:44:30 2012 From: corbellini.andrea at gmail.com (Andrea Corbellini) Date: Thu, 17 May 2012 16:44:30 +0200 Subject: New message for Bug/Responses#Release_has_reached_EOL In-Reply-To: <1751043.NCpg2i7bRq@i7> References: <1751043.NCpg2i7bRq@i7> Message-ID: <4FB50ECE.1030902@gmail.com> Hi, On 17/05/12 11:57, Maarten Bezemer wrote: > I've tried recreating this bug with RELEASE and was unable to, > given the information you've provided. Please either a) upgrade > and test or b) increase the verbosity of the steps to recreate > it so we can try again. > > Do feel free to report any other bugs you may find. It looks good to me overall. There's just one thing that should be changed: I'd remove the "either" word and rephrase the sentence more or less in this way: "Please upgrade to the latest version and re-test. If the bug is still reproducible, increase the verbosity ..." I would also include a link to an help page explaining how to perform the upgrade, i.e. https://help.ubuntu.com/community/PreciseUpgrades Thanks, Andrea C. From webmaster at ubuntu.com Fri May 18 05:56:03 2012 From: webmaster at ubuntu.com (Help Ubuntu) Date: Fri, 18 May 2012 05:56:03 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_penalvch?= Message-ID: <20120518055603.31891.65552@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Community Ubuntu Documentation" for change notification. The "ReportingBugs" page has been changed by penalvch: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=174&rev2=175 Comment: Added note about how do not apport-collect unless O.R. or asked == Adding Apport Debug Information to an Existing Launchpad Bug == == Adding Apport Debug Information to an Existing Launchpad Bug == - If you have already reported a bug directly via Launchpad, but want to add additional debugging information via ''Apport'' to the bug report, you can do this by running the command `apport-collect bug_number` via "Run Application" or terminal window. + If you have already reported a bug directly via Launchpad, but want to add additional debugging information via ''Apport'' to the bug report, you can do this by running the command `apport-collect bug_number` via "Run Application" or terminal window. If you are not the original reporter, please do not apport-collect to a bug report unless specifically asked of you by a developer or triager. Running apport-collect when not asked creates spammy E-Mail traffic for those subscribed, clutters up the bug report with undesired attachments, and hinders the bug getting addressed quickly. Instead, please open a new report via ubuntu-bug. <> == Filing a translation bug == From noreply at ubuntu.com Fri May 18 15:40:35 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Fri, 18 May 2012 15:40:35 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggerTalk=5Fit=22_by_fabiomar?= =?utf-8?q?coni?= Message-ID: <20120518154035.28895.57103@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggerTalk_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/DebuggerTalk_it Comment: Italian translation started New page: ||<>|| == Introduzione == Praticamente affronteremo una discussione sui debugger che ho scrittto o sui quali ho lavorato [[http://bashdb.sf.net|GNU bash]], [[http://bashdb.sf.net/remake|GNU make]], [[http://bashdb.sf.net/pydb|Python]],e [[http://rubyforge.org/projects/ruby-debug/|Ruby]]. Gli agomenti affrontati andranno dallo storico al pratico. Nell'arena pratica, io posso mostrare come utilizzare per il debug un progetto GNU automake. Ad esempio, ci potrebbe essere un campo teorico su come strutturare la scrittura di un debugger. (There could be a theoretical area such as how to structure writing a debugger. (Quelli per ruby e Python sono interessanti qui). In passato, qualcuno mi chieset ''"cosa c'è di affascinante in un debugger?"'' Oppure un'osservazione fatta da un imprenditore fù "''Non ho mai usato un debugger, io '''scrivo''' codice''". As a systems administrator one is often confronted with lots of code that you didn't write. You suspect the code might not even be written all that well, but you are more sure that there isn't much in the way of documentation or comments in the code. And you've got a problem to solve. Here is where a debugger comes into play. I've also heard the observation that you don't need a debugger because you go into a Bash, Python or Ruby shell and just start typing statements in the language. Again if you have a high-level idea of what's going on, that's great. However the hardest part here is getting the context correct. I need a `foo` object from class `Foo` and then need to hook the `bar` object from class `Bar` which means importing or requiring module `baz` into `foo` before I can call this method `fubar` that is of interest to me. With a debugger you work on code that purports to work and largely does. So for the most part, most of the necessary setup has been done for you. In a sense a ''good'' debugger is really not all that different than a shell, it's just that the context has already been set up for you. We'll see that in the Python debugger later. === Why model debuggers off of gdb? === Because it is * fairly complete --- suggests how to expand lesser debuggers (e.g. `pdb` and Ruby's `debug`). For example, consider signal handling. * well known --- learning one helps learn another. It helps ''programs'' learn too! * it's there --- why invent a new interface? Because is GPL can cull from gdb manual, with citation === Issues in Writing or Using a Debugger === * Speed --- debuggers can slow down your program * Matching virtual reality to reality; which naturally leads to... * [[http://en.wikipedia.org/wiki/Heisenbug#Heisenbugs|Heisenbugs]] (and speed contributes to this as well) == GNU bash == === Historical stuff === The sordid history of `trap DEBUG`. Originally like other signals, it came ''after'' a statement. But for debugging you need to stop before. Think "`rm -fr /`" and when you'd like to know about it. It took about 2 years after I posted a suggestion for the change to get into bash (and I never got an acknowledgment about this). Debug support was going way too slowly. About 4 years between those releases. So I forked the bash code to add debug support and timestamped history. This code was incorporated into bash 3.0. Many thanks to Masatake YAMATO. === Practical example === * [[http://bashdb.sourceforge.net/bashdb.html#PS4|PS4]] trick * Using to debug SYSV start/stop scripts. * debugger `set_trace` trick? ''Note: `set_trace` is depricated in favor of `debugger`'' Note: if you are going to debug `configure` scripts, you want the `readarray` builtin. ''This has since been encorporated into bash 4.0 and is not needed in that and later versions'' At this point we should have seen three paradigms of debugging that will come up over again in the other debuggers: * line tracing * invoking from the debugger at the outset * calling the debugger (somehow) from inside the program. There's one more technique that's a little hard to use in bash but is more prevalent elsewhere * post-mortem debugging. === Work since the talk === In 2008, I did something in between a port and a rewrite of this to support `ksh` and `zsh` and colorized output via *pygments*. As before, changes were needed in the shells themselves to support more accurate location reporting and to be able to do more program introspection. Much to my delight, these enhancements were done quickly and with little involvement on my part. But this means you do need a recent release of these shells. The debugger code is maintained on `github`. See [[http://github.com/rocky/zshdb]] and [[http://github.com/rocky/kshdb]]. == GNU make == I have a short (13 minute) [[http://showmedo.com/videos/video?name=linuxBernsteinMakeDebug1&fromSeriesID=40|video]] which is really intended to be the first part of a more extended example. === Historical stuff === It's [[http://freshmeat.net/articles/view/889/#comment-31152|deja vu all over again]]. What needed to be done (same as in bash): * better position location reporting * keep target stack (like a call stack) * get tracing working first and then add a interactive command loop === Practical example === Method I use to solve a Makefile problem: * use normal make (until failure) * run again with `remake -x` * if above doesn't work narrow target and run with `remake -X` ''target'' Show: * make basic debugging: `make -d basic` * make tracing: `remake -x` * post-mortem debugging * 'step' and 'next' * showing dependencies and `write` command * Debugging a automake-generated Makefile. === Future === What's there now is good enough for me. If it's not for others, I encourage involvement. ;-) The original version was somewhere between 3.80 and 3.81. In 2008, a fresh conversion was done for 3.81 Some of this could possibly get folded back into GNU Make but it may mean a ''regression'' in coding style. (Dan Fabulich once expressed interest in doing this.) == Python == === Historical stuff === There are two gdb-like debuggers. The stock python debugger, [[http://docs.python.org/lib/module-pdb.html|pdb]], and one that grew from that, called `pydb`. The name `pydb` is because at about the time `pdb` was developed Richard Wolff was working in parallel on a debugger to be embedded on [[http://www.gnu.org/software/ddd|ddd]]. He has since retired and with his blessing I've taken over the name and have been sort of maintaining the ddd embedding as well. Stack frame display dilemma: do Python programmers draw their trees with the [[http://groups.google.com/group/comp.lang.python/browse_thread/thread/90cbcd03f37294a1/caa85f727c28353a|roots at the bottom]]? === Practical example === I have a short 15-minute [[http://showmedo.com/videos/video?name=pythonBernsteinPydbIntro&fromSeriesID=28|video]] showing off some non-pdb things. Example: how `ipython` handles `help` --- signal handling (initially added by Matt Fleming as part of a Google 2006 Summer-of-code project. Possibly some of the thread debugging features. === Recent and Future work === Integration into [[http://ipython.scipy.org/moin/|ipython]] was recently done. Release 1.21 added a number of usability conveniences like better command completion, and [[http://docs.python.org/lib/module-pydoc.html|pydoc]] help. Remote debugging. This is needed to hook into many IDEs like Eric, IDLE, winpdb (and therefore SPE), and Eclipse. The bad news though is that each IDE has defined it's own protocol for working remotely. In late 2008, I started working on a complete rewrite. Some features planned: * remote debugging * much more modular (and more along the lines of `ruby-debug`) * distribution via egg package(s) ''Code is available at http://code.google.com/p/pydbgr/'' == Ruby == There are in fact two ruby debuggers. `debug` which comes with the base Ruby install and [[http://rubyforge.org/projects/ruby-debug/|ruby-debug]] by Kent Sibilev. Both are roughly gdb like. Kent's debugger is I think is coded the cleanest of any debugger I've seen (although it does have some warts). Each command is its own class. By way of comparison, in the stock Python debugger a command module is used. Commands are methods in this (sub)class whose names start with the "do_". This is a pattern akin to one used in unit testing where tests start with "test_". But having a class per command is cooler. It means that commands can have ''properties''. One property in `ruby-debug` is whether you can run this command if the program has crashed. (The `help` command you can run, but the `step` command you can't). === Practical Example === `require 'debug'` trick? Stopping in a Rails unit test. ''Note: since this talk, `ruby-debug` has become the de-facto debugger that is used in Ruby, JRuby, Ruby/Rails, merb and other frameworks. The successor to the `require 'debug'` trick is now `require 'ruby-debug/debugger'` or some variation of that. See [[http://bashdb.sourceforge.net/ruby-debug.html#SEC18|Calling the debugger from inside your Ruby Program]] and [[http://bashdb.sourceforge.net/ruby-debug.html#SEC72|The Debugger Module]] for even more detail.'' === Future Work === * Aptana and Eclipse plugin (Done sometime in 2007 via ruby-debug-base.) * Documentation (largely done in 2007; see [[http://bashdb.sf.net/ruby-debug.html]] and [[http://bashdb.sf.net/ruby-debug/index.html]]) * Regression tests. (Largely done in 2007.) * More closely like gdb (Much progress here too; caused some incompatible changes.) * Complete rewrite for Ruby 1.9? ''This code is avaliable at https://github.com/rocky/rb-trepanning'' ---- CategoryDebugging From noreply at ubuntu.com Fri May 18 16:22:09 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Fri, 18 May 2012 16:22:09 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggerTalk=5Fit=22_by_fabiomar?= =?utf-8?q?coni?= Message-ID: <20120518162209.1902.46238@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggerTalk_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/DebuggerTalk_it?action=diff&rev1=1&rev2=2 Nell'arena pratica, io posso mostrare come utilizzare per il debug un progetto GNU automake. Ad esempio, ci potrebbe essere un campo teorico su come strutturare la scrittura di un debugger. (There could be a theoretical area such as how to structure writing a debugger. (Quelli per ruby e Python sono interessanti qui). - In passato, qualcuno mi chieset ''"cosa c'è di affascinante in un debugger?"'' Oppure un'osservazione fatta da un imprenditore fù "''Non ho mai usato un debugger, io '''scrivo''' codice''". As a systems administrator one is often confronted with lots of code that you didn't write. You suspect the code might not even be written all that well, but you are more sure that there isn't much in the way of documentation or comments in the code. And you've got a problem to solve. Here is where a debugger comes into play. + In passato, qualcuno mi chieset ''"cosa c'è di affascinante in un debugger?"'' Oppure un'osservazione fatta da un imprenditore fù "''Non ho mai usato un debugger, io a malapena '''scrivo''' codice''". In veste di amministratore di sistema, chiunque è sempre a confronto con una moltitudine di codice che non ha scritto. Si potrebbe sospettare che il codice non sia stato scritto perfettamente, e che sicuramente non ci sia molta documentazione o commenti nel codice. Nel caso si abbia un problema da risolvere, qui entra in gioco il debugger. - I've also heard the observation that you don't need a debugger because you go into a Bash, Python or Ruby shell and just start typing statements in the language. Again if you have a high-level idea of what's going on, that's great. However the hardest part here is getting the context correct. I need a `foo` object from class `Foo` and then need to hook the `bar` object from class `Bar` which means importing or requiring module `baz` into `foo` before I can call this method `fubar` that is of interest to me. With a debugger you work on code that purports to work and largely does. So for the most part, most of the necessary setup has been done for you. In a sense a ''good'' debugger is really not all that different than a shell, it's just that the context has already been set up for you. We'll see that in the Python debugger later. + Ho anche sentito dire che voi non avete bisogno di un debugger perchè state usando una shell Bash, Python o Ruby ed avete appena iniziato a scrivere le dichiarazioni. Io ho bisogno di un oggetto `foo` dalla classe `Foo` e quindi devo agganciare la `bar` aggetto dalla classe `Bar` che significa importare o richiedere il modulo `baz` in `foo` prima che io possa chiamare ciò `fubar` che è interessante per me. Con un debugger si lavora sul codice ed in maniera estesa. Quindi a grandi linee, la maggior parte dei necessari setup sono stati fatti per voi. Con il proposito che un buon debugger non è per nulla diverso da una shell, semplicemente il contesto è già stato preimpostato. Vedremo questo in seguito nel debugger Phyton. === Why model debuggers off of gdb? === From lars.duesing at camelotsweb.de Fri May 18 17:39:58 2012 From: lars.duesing at camelotsweb.de (=?utf-8?Q?Lars_D=C3=BCsing?=) Date: Fri, 18 May 2012 19:39:58 +0200 Subject: Adding a package special log file to apport Message-ID: <409D4772-C320-4088-A7D1-54767A1DA69C@camelotsweb.de> Hi all, Is there any way to add a log file to apport on crash of a specific package? I need /var/log/aiccu.log on crash of aiccu... Thanks, Lars From daniel.manrique at canonical.com Fri May 18 19:09:52 2012 From: daniel.manrique at canonical.com (Daniel Manrique) Date: Fri, 18 May 2012 15:09:52 -0400 Subject: Adding a package special log file to apport In-Reply-To: <409D4772-C320-4088-A7D1-54767A1DA69C@camelotsweb.de> References: <409D4772-C320-4088-A7D1-54767A1DA69C@camelotsweb.de> Message-ID: <4FB69E80.10803@canonical.com> On 12-05-18 01:39 PM, Lars Düsing wrote: > Hi all, > Is there any way to add a log file to apport on crash of a specific package? > I need /var/log/aiccu.log on crash of aiccu... > > Thanks, > Lars > Look here for information on how to add package hooks to do stuff like this: https://wiki.ubuntu.com/Apport/DeveloperHowTo#Package_Hooks In brief (and don't believe me too much, I've never done it, I'm just reading the docs and comparing against what a package I know does this has): - Add a Python script/file/hook to your package (say, aiccu.py) with something like this: from apport.hookutils import * def add_info(report, ui=None): attach_file_if_exists(report, '/var/log/aiccu.log', key='aiccuLog') report['SecretMessage'] = 'my hook was here' - Make sure your package installs it in /usr/share/apport/package-hooks/aiccu.py. - Daniel From brian at ubuntu.com Fri May 18 19:31:05 2012 From: brian at ubuntu.com (Brian Murray) Date: Fri, 18 May 2012 12:31:05 -0700 Subject: Adding a package special log file to apport In-Reply-To: <4FB69E80.10803@canonical.com> References: <409D4772-C320-4088-A7D1-54767A1DA69C@camelotsweb.de> <4FB69E80.10803@canonical.com> Message-ID: <20120518193105.GP2879@murraytwins.com> On Fri, May 18, 2012 at 03:09:52PM -0400, Daniel Manrique wrote: > On 12-05-18 01:39 PM, Lars Düsing wrote: > > Hi all, > > Is there any way to add a log file to apport on crash of a specific package? > > I need /var/log/aiccu.log on crash of aiccu... > > > > Thanks, > > Lars > > > > > Look here for information on how to add package hooks to do stuff like this: > > https://wiki.ubuntu.com/Apport/DeveloperHowTo#Package_Hooks > > In brief (and don't believe me too much, I've never done it, I'm just reading > the docs and comparing against what a package I know does this has): > > - Add a Python script/file/hook to your package (say, aiccu.py) with something > like this: > > from apport.hookutils import * > > def add_info(report, ui=None): > attach_file_if_exists(report, '/var/log/aiccu.log', key='aiccuLog') > report['SecretMessage'] = 'my hook was here' > > > - Make sure your package installs it in /usr/share/apport/package-hooks/aiccu.py. Well, if the aiccu package generates multiple binary packages then you'd want to name it source_aiccu.py so the package hook would be run for every binary package. There are also lots of examples on most ubuntu systems in /usr/share/apport/package-hooks. Additionally, there are some convenience functions for adding information in hookutils.py like attach_file_if_exists which was mentioned in the code snippet. Oh and you initially mentioned you only want this for crashes, so keepng in mind that package hooks are also run when someone uses 'ubuntu-bug aiccu', you'd probably want: if report['ProblemType'] == 'Crash': attach_file_if_exists(...) Also if you need the changes to package sponsored or SRU'ed (you'd probably want it in Precise), I am happy to help. -- Brian Murray From maarten.bezemer at gmail.com Sat May 19 08:57:15 2012 From: maarten.bezemer at gmail.com (Maarten Bezemer) Date: Sat, 19 May 2012 10:57:15 +0200 Subject: New message for Bug/Responses#Release_has_reached_EOL In-Reply-To: <20897767.WNYmegalzW@i7> References: <1751043.NCpg2i7bRq@i7> <20897767.WNYmegalzW@i7> Message-ID: <2988185.bLAbAgD02H@i7> Hello, I have updated the page with this text: Thank you for reporting this bug to Ubuntu. RELEASE reached EOL on DATE. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases I've tried recreating this bug with RELEASE and was unable to, given the information you've provided. Please upgrade to the latest version and re-test. If the bug is still reproducable, increase the verbosity of the steps to recreate it so we can try again. Do feel free to report any other bugs you may find. Thanks for your input. Regards, Maarten From lars.duesing at camelotsweb.de Sat May 19 10:21:48 2012 From: lars.duesing at camelotsweb.de (Lars Duesing) Date: Sat, 19 May 2012 12:21:48 +0200 Subject: apport: removing passwords from "modified.conffile..." Message-ID: <4FB7743C.2090309@camelotsweb.de> Hi again, I have another problem: How to remove passwords from apport-attachments which are automagically added? I have searched for modified_conffile throughout the sources, but cannot find anything, except in test-scenarios... In the file /etc/aiccu.conf and modified.conffile..etc.aiccu.conf.txt there are sensitive login-information: > username LxxxxxxE > password xxxxxxx maybe even in comments :( Lars -------------- next part -------------- An HTML attachment was scrubbed... URL: From lars.duesing at camelotsweb.de Fri May 18 21:01:52 2012 From: lars.duesing at camelotsweb.de (Lars Duesing) Date: Fri, 18 May 2012 23:01:52 +0200 Subject: Adding a package special log file to apport In-Reply-To: <20120518193105.GP2879@murraytwins.com> References: <409D4772-C320-4088-A7D1-54767A1DA69C@camelotsweb.de> <4FB69E80.10803@canonical.com> <20120518193105.GP2879@murraytwins.com> Message-ID: <4FB6B8C0.5070607@camelotsweb.de> Hi Brian, > Also if you need the changes to package sponsored or SRU'ed (you'd > probably want it in Precise), I am happy to help. Thanks for your offer! If you want to have a look at https://code.launchpad.net/~lars.duesing/ubuntu/precise/aiccu/aiccu-apport-fix I would be pleased! Lars From lars.duesing at camelotsweb.de Sat May 19 07:17:35 2012 From: lars.duesing at camelotsweb.de (Lars Duesing) Date: Sat, 19 May 2012 09:17:35 +0200 Subject: apport: removing passwords from "modified.conffile..." Message-ID: <4FB7490F.1040304@camelotsweb.de> Hi again, I have another problem: How to remove passwords from apport-attachments which are automagically added? I have searched for modified_conffile throughout the sources, but cannot find anything, except in test-scenarios... In the file /etc/aiccu.conf and modified.conffile..etc.aiccu.conf.txt there are sensitive login-information: > username LxxxxxxE > password xxxxxxx maybe even in comments :( Lars -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at ubuntu.com Sat May 19 08:55:54 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sat, 19 May 2012 08:55:54 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Responses=22_by_veger?= Message-ID: <20120519085554.17493.85049@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Responses" page has been changed by veger: http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=349&rev2=350 If the specific release has reached EOL per https://wiki.ubuntu.com/Releases and there is not enough information to work on the bug, then you can set to '''Incomplete''' and use the following response (Note RELEASE and DATE are placeholders): - ||Thank you for reporting this bug to Ubuntu. RELEASE reached EOL on DATE.<
>Please see this document for currently supported Ubuntu releases:<
>https://wiki.ubuntu.com/Releases <
><
>I've tried recreating this bug with RELEASE and was unable to, given the information you've provided. Please either a) upgrade and test or b) increase the verbosity of the steps to recreate it so we can try again.<
><
>Please feel free to report any other bugs you may find.|| + ||Thank you for reporting this bug to Ubuntu. RELEASE reached EOL on DATE.<
>See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases <
><
>I've tried recreating this bug with RELEASE and was unable to, given the information you've provided. Please upgrade to the latest version and re-test. If the bug is still reproducable, increase the verbosity of the steps to recreate it so we can try again.<
><
>Do feel free to report any other bugs you may find.|| == An idea to improve Ubuntu == Note: If it is a request to add a feature to a '''specific program''' it should be '''forwarded to the upstream developers instead.''' See: [[Bugs/HowToTriage#Forwarding%20upstream|Forwarding Bugs Upsteam]] From nigelbabu at ubuntu.com Sun May 20 16:45:13 2012 From: nigelbabu at ubuntu.com (Nigel Babu) Date: Sun, 20 May 2012 22:15:13 +0530 Subject: apport: removing passwords from "modified.conffile..." In-Reply-To: <4FB7743C.2090309@camelotsweb.de> References: <4FB7743C.2090309@camelotsweb.de> Message-ID: Hi Lars, You could probably look at what I had done for the rhythmbox apport hook.[1] Take a look at the mask_values() function. [1] http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/oneiric/rhythmbox/oneiric/view/head:/debian/source_rhythmbox.py Regards Nigel On Sat, May 19, 2012 at 3:51 PM, Lars Duesing wrote: > Hi again, > > I have another problem: How to remove passwords from apport-attachments > which are automagically added? > I have searched for modified_conffile throughout the sources, but cannot > find anything, except in test-scenarios... > In the file /etc/aiccu.conf and modified.conffile..etc.aiccu.conf.txt there > are sensitive login-information: >> username LxxxxxxE >> password xxxxxxx > maybe even in comments :( > > Lars > > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > From brian at ubuntu.com Mon May 21 14:53:22 2012 From: brian at ubuntu.com (Brian Murray) Date: Mon, 21 May 2012 07:53:22 -0700 Subject: [Ubuntu Wiki] Update of "Bugs/Responses" by veger In-Reply-To: <20120519085554.17493.85049@mangaba.canonical.com> References: <20120519085554.17493.85049@mangaba.canonical.com> Message-ID: <20120521145322.GV2879@murraytwins.com> On Sat, May 19, 2012 at 08:55:54AM -0000, Ubuntu Wiki wrote: > Dear Wiki user, > > You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. > > The "Bugs/Responses" page has been changed by veger: > http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=349&rev2=350 > > > If the specific release has reached EOL per https://wiki.ubuntu.com/Releases and there is not enough information to work on the bug, then you can set to '''Incomplete''' and use the following response (Note RELEASE and DATE are placeholders): > > - ||Thank you for reporting this bug to Ubuntu. RELEASE reached EOL on DATE.<
>Please see this document for currently supported Ubuntu releases:<
>https://wiki.ubuntu.com/Releases <
><
>I've tried recreating this bug with RELEASE and was unable to, given the information you've provided. Please either a) upgrade and test or b) increase the verbosity of the steps to recreate it so we can try again.<
><
>Please feel free to report any other bugs you may find.|| > + ||Thank you for reporting this bug to Ubuntu. RELEASE reached EOL on DATE.<
>See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases <
><
>I've tried recreating this bug with RELEASE and was unable to, given the information you've provided. Please upgrade to the latest version and re-test. If the bug is still reproducable, increase the verbosity of the steps to recreate it so we can try again.<
><
>Do feel free to report any other bugs you may find.|| Not everybody may know what EOL stands for, perhaps putting the words in it or avoiding the acronym at all would be more informative. -- Brian Murray Ubuntu Bug Master From tom at hill4u.com Mon May 21 16:34:45 2012 From: tom at hill4u.com (Tom Hill) Date: Mon, 21 May 2012 17:34:45 +0100 Subject: [Ubuntu Wiki] Update of "Bugs/Responses" by veger In-Reply-To: <20120521145322.GV2879@murraytwins.com> References: <20120519085554.17493.85049@mangaba.canonical.com> <20120521145322.GV2879@murraytwins.com> Message-ID: <58A4CFB8-B11E-4CEB-AC1D-5ED33911AC0A@hill4u.com> True, but adding the meaning next to it would teach them the meaning. On 21 May 2012, at 15:53, Brian Murray wrote: > On Sat, May 19, 2012 at 08:55:54AM -0000, Ubuntu Wiki wrote: >> Dear Wiki user, >> >> You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. >> >> The "Bugs/Responses" page has been changed by veger: >> http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=349&rev2=350 >> >> >> If the specific release has reached EOL per https://wiki.ubuntu.com/Releases and there is not enough information to work on the bug, then you can set to '''Incomplete''' and use the following response (Note RELEASE and DATE are placeholders): >> >> - ||Thank you for reporting this bug to Ubuntu. RELEASE reached EOL on DATE.<
>Please see this document for currently supported Ubuntu releases:<
>https://wiki.ubuntu.com/Releases <
><
>I've tried recreating this bug with RELEASE and was unable to, given the information you've provided. Please either a) upgrade and test or b) increase the verbosity of the steps to recreate it so we can try again.<
><
>Please feel free to report any other bugs you may find.|| >> + ||Thank you for reporting this bug to Ubuntu. RELEASE reached EOL on DATE.<
>See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases <
><
>I've tried recreating this bug with RELEASE and was unable to, given the information you've provided. Please upgrade to the latest version and re-test. If the bug is still reproducable, increase the verbosity of the steps to recreate it so we can try again.<
><
>Do feel free to report any other bugs you may find.|| > > Not everybody may know what EOL stands for, perhaps putting the words in > it or avoiding the acronym at all would be more informative. > > -- > Brian Murray > Ubuntu Bug Master > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad From noreply at ubuntu.com Mon May 21 16:01:58 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 21 May 2012 16:01:58 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Chromium/Debugging=22_by_uusijan?= =?utf-8?q?i?= Message-ID: <20120521160158.30732.98926@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Chromium/Debugging" page has been changed by uusijani: http://wiki.ubuntu.com/Chromium/Debugging?action=diff&rev1=9&rev2=10 Comment: restructuring, language ## page was renamed from Chromium/Debug + If Chromium crashes and you want to file a bug upstream, use their [[http://code.google.com/p/chromium/issues/entry?template=Defect%20on%20Linux|linux template]]. Always include the output from the following command: - When you want to file a bug, it should be filed '''upstream''' using this '''[[http://code.google.com/p/chromium/issues/entry?template=Defect%20on%20Linux|linux template]]'''. - Please always include the result of the following command: - {{{ - dpkg -l | grep chromium-}}} - - = Debugging Chromium crashes = - - If chromium crashes and if you want to file a '''[[http://code.google.com/p/chromium/issues/entry?template=Defect%20on%20Linux|bug upstream]]''', you need to provide a proper backtrace for your crash. - - It could be accomplished using '''gdb''' and some debug packages. - - If you know nothing about gdb, the generic instructions are available here: [[https://wiki.ubuntu.com/Backtrace|Backtraces with gdb]] - - The debug package for chromium is called '''chromium-browser-dbg''' (it's big, ~75MB). It could be installed and removed like any other packages. - - Note: you may need other debug packages if the backtrace shows lines like "#5 0x083949e0 in ?? ()". - In that case, you need the corresponding -dbg or -dbgsym packages. - Instructions about those are available in [[https://wiki.ubuntu.com/DebuggingProgramCrash|DebuggingProgramCrash]] - - Once done, open a terminal and proceed as follow: {{{ + $ dpkg -l | grep chromium- + }}} + + You'll need to provide a [[https://wiki.ubuntu.com/Backtrace|backtrace]]. It can be produced using gdb, with the help of debugging symbols. + + == Getting a backtrace == + Debugging symbols come in packages that can be [[InstallingSoftware|installed just any other software package]] in Ubuntu. The debugging symbols package for Chromium is called ''chromium-browser-dbg''. Once you've installed it, open a terminal and proceed as follows: + + {{{ - chromium-browser --debug 2>&1 | tee gdb-chromium.txt + $ chromium-browser --debug 2>&1 | tee gdb-chromium.txt (gdb) handle SIG33 pass nostop noprint (gdb) set pagination 0 (gdb) run }}} - do what you need to do to trigger the crash, then: + Do what you need to do to trigger the crash, then: {{{ (gdb) backtrace @@ -37, +27 @@ (gdb) quit }}} + If the backtrace shows lots of lines with question marks (such as "#5 0x083949e0 in ?? ()"), you're likely to need additional debugging symbols packages. To find out which libraries Chromium is loading, try: - Check the file '''gdb-chromium.txt''' to see if it contains symbols (as few "?? ()" as possible). - If not, please locate and install the missing debug package(s) and retry. - Note: ''ldd /usr/lib/chromium-browser/chromium-browser'' could give you a clue of which libs are loaded, and http://packages.ubuntu.com/ could tell you in which package they live. + {{{ + $ ldd /usr/lib/chromium-browser/chromium-browser + }}} - Once you feel it's good enough, you may attach the file '''gdb-chromium.txt''' to your bug report. + Then look for corresponding -dbg or -dbgsym packages in the repositories. - Note: since chromium is multi-process (it spawns several processes, such as the sandbox and all renderers), the stack may be useless, depending on where the crash occurs. You can then try with --single-process (after --debug). If it is still not enough, you can try inferring from the upstream chrome debugging tips: http://code.google.com/p/chromium/wiki/LinuxDebugging + == Debugging child processes == + Since Chromium normally spawns several processes (such as the sandbox and renderers), the backtrace from the browser process may not be useful (unless it is the main process that crashes). For catching backtraces from Chromium's child processes, you should run Chromium with --single-process: + + {{{ + $ chromium-browser --debug --single-process 2>&1 | tee gdb-chromium.txt + }}} + + Then proceed as above with gdb. + + Once you feel your backtrace file (gdb-chromium.txt) is sufficient, attach it to your bug report. + + == External links == + * [[http://code.google.com/p/chromium/wiki/LinuxDebugging|Upstream debugging instructions]] + ---- CategoryDebugging From noreply at ubuntu.com Mon May 21 16:02:45 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 21 May 2012 16:02:45 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Chromium/Debugging=22_by_uusijan?= =?utf-8?q?i?= Message-ID: <20120521160245.30656.94228@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Chromium/Debugging" page has been changed by uusijani: http://wiki.ubuntu.com/Chromium/Debugging?action=diff&rev1=10&rev2=11 Comment: typo: just +like any You'll need to provide a [[https://wiki.ubuntu.com/Backtrace|backtrace]]. It can be produced using gdb, with the help of debugging symbols. == Getting a backtrace == - Debugging symbols come in packages that can be [[InstallingSoftware|installed just any other software package]] in Ubuntu. The debugging symbols package for Chromium is called ''chromium-browser-dbg''. Once you've installed it, open a terminal and proceed as follows: + Debugging symbols come in packages that can be [[InstallingSoftware|installed just like any other software package]] in Ubuntu. The debugging symbols package for Chromium is called ''chromium-browser-dbg''. Once you've installed it, open a terminal and proceed as follows: {{{ $ chromium-browser --debug 2>&1 | tee gdb-chromium.txt From noreply at ubuntu.com Sat May 26 12:55:00 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sat, 26 May 2012 12:55:00 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggerTalk=5Fit=22_by_fabiomar?= =?utf-8?q?coni?= Message-ID: <20120526125500.17155.77925@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggerTalk_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/DebuggerTalk_it?action=diff&rev1=3&rev2=4 Ho anche sentito dire che voi non avete bisogno di un debugger perchè state usando una shell Bash, Python o Ruby ed avete appena iniziato a scrivere le dichiarazioni. Io ho bisogno di un oggetto `foo` dalla classe `Foo` e quindi devo agganciare la `bar` oggetto dalla classe `Bar` che significa importare o richiedere il modulo `baz` in `foo` prima che io possa chiamare ciò `fubar` che è ciò che mi serve. Con un debugger si lavora sul codice ed in maniera estesa. Quindi a grandi linee, la maggior parte dei necessari setup sono stati fatti per voi, con il proposito che un buon debugger non è per nulla diverso da una shell, semplicemente il contesto è già stato preimpostato. Vedremo questo in seguito nel debugger Phyton. - === Why model debuggers off of gdb? === + === Perchè creare debugger diversi da gdb? === - Because it is - * fairly complete --- suggests how to expand lesser debuggers (e.g. `pdb` and Ruby's `debug`). For example, consider signal handling. - * well known --- learning one helps learn another. It helps ''programs'' learn too! - * it's there --- why invent a new interface? Because is GPL can cull from gdb manual, with citation + Tutto sommato gdb è: + * piuttosto completo --- indica come espandere debugger inferiori (es. `pdb` e Ruby `debug`). Per esempio, considerare il signal handling. + * ben noto --- il suo `know-how` migliora l'apprendimento degli altri. Aiuta anche nell'apprendimento di programmi. + * è pronto --- perchè inventare un'altra interfaccia? Essendo GPL trae vantaggio dal manuale gdb, con citazioni - === Issues in Writing or Using a Debugger === + === Problemi nello scrivere o utilizzare un debugger === - * Speed --- debuggers can slow down your program - * Matching virtual reality to reality; which naturally leads to... + * Velocità --- i debugger possono rallentare i programmi + * Confrontando la realtà virtualizzata con la realtà; induce a.... - * [[http://en.wikipedia.org/wiki/Heisenbug#Heisenbugs|Heisenbugs]] (and speed contributes to this as well) + * [[http://en.wikipedia.org/wiki/Heisenbug#Heisenbugs|Heisenbugs]] (e come è influenzato dalla velocità) == GNU bash == - === Historical stuff === + === Cenni storici === The sordid history of `trap DEBUG`. Originally like other signals, it came ''after'' a statement. But for debugging you need to stop before. Think "`rm -fr /`" and when you'd like to know about it. It took about 2 years after I posted a suggestion for the change to get into bash (and I never got an acknowledgment about this). Debug support was going way too slowly. About 4 years between those releases. From noreply at ubuntu.com Sat May 26 15:15:35 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sat, 26 May 2012 15:15:35 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22LibreOfficeBugWrangling=22_by_pe?= =?utf-8?q?nalvch?= Message-ID: <20120526151535.11704.85108@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "LibreOfficeBugWrangling" page has been changed by penalvch: http://wiki.ubuntu.com/LibreOfficeBugWrangling?action=diff&rev1=10&rev2=11 Comment: Added note in "How to File" on mentioning what extensions are installed - Available languages: [[https://wiki.ubuntu.com/LibreOfficeBugWrangling_it| Italiano]], + Available languages: [[https://wiki.ubuntu.com/LibreOfficeBugWrangling_it| Italiano]] <> ||'''Contents'''<
><>|| @@ -10, +10 @@ * Please do not report a LibreOffice bug without first reading this wiki article and performing all the relevant actions mentioned here. Failure to do so will delay your bug getting addressed as quickly as possible. * Please file all your LibreOffice bugs by executing at the Terminal: <
> {{{ubuntu-bug }}} <
> <
> where is the specific package you found the problem in. For example, if you have a document import issue with Writer: <
> {{{ubuntu-bug libreoffice-writer}}} * Sample bug reporting template: <
> - || 1) lsb_release -rd <
> <
> 2) apt-cache policy libreoffice-writer <
> <
> 3) What is expected to happen in Writer is . <
> <
> 4) What happened instead is... <
> <
> WORKAROUND: Perform the following steps:...|| + || 1) lsb_release -rd <
> <
> 2) apt-cache policy libreoffice-writer <
> <
> 3) What is expected to happen in Writer is . <
> <
> 4) What happened instead is... <
> <
> I have the following extensions installed: lo-menubar, libreoffice-nlpsolver, ... <
> <
> WORKAROUND: Perform the following steps:...|| * Please do not stack multiple issues into one bug. * Please do not complain about how long it takes to fix a bug, the severity of your bug is high so it should be fixed immediately, "I cannot believe it's not fixed...", etc. Especially, if you have not completed the relevant, below mentioned debugging procedures, let alone contributed code upstream. This type of behavior is unconstructive, irritating to others who read your E-Mail, and spammy. We all want to see every bug fixed as soon as possible! Naturally, bugs being fixed is limited to reproducibility and clarity of the bug report, the actual impact the bug has on the community, and available developer resources. From noreply at ubuntu.com Tue May 29 16:42:41 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 29 May 2012 16:42:41 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22LibreOfficeBugWrangling=5Fit=22_?= =?utf-8?q?by_fabiomarconi?= Message-ID: <20120529164241.21038.32384@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "LibreOfficeBugWrangling_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/LibreOfficeBugWrangling_it?action=diff&rev1=4&rev2=5 * Vi preghiamo di non segnalare bug inerenti LibreOffice senza avere prima letto questa pagina ed avere eseguito le necessarie azioni riportate in seguito. La mancata inosservanza causerà ritardi nell'indirizzamento della vostra segnalazione. * Vi preghiamo di segnalare tutti i vostri bug in LibreOffice eseguendo nel terminale: <
> {{{ubuntu-bug }}} <
> <
> dove è lo specifico pacchetto nel quale è stato rinvenuto il problema. Per esempio, se si ha un problema importando un documento con Writer: <
> {{{ubuntu-bug libreoffice-writer}}} * Un semplice modello di segnalazione di bug: <
> - || 1) lsb_release -rd <
> <
> 2) apt-cache policy libreoffice-writer <
> <
> 3) What is expected to happen in Writer is (cosa dovrebbe succedere) . <
> <
> 4) What happened instead is...(cosa invece accade...) <
> <
> I have the following extensions installed: lo-menubar, libreoffice-nlpsolver, ... <
> <
> WORKAROUND: Perform the following steps:...|| + || 1) lsb_release -rd <
> <
> 2) apt-cache policy libreoffice-writer <
> <
> 3) What is expected to happen in Writer is (cosa dovrebbe succedere) . <
> <
> 4) What happened instead is...(cosa invece accade...) <
> <
> I have the following extensions installed: lo-menubar, libreoffice-nlpsolver, ... (le seguenti estensioni risultano installate: lo-menubar, libreoffice-nlpsolver,...<
> <
> WORKAROUND: Perform the following steps:...|| * Per cortesia non riportare più di un bug per ogni segnalazione. * Per cortesia evitare commenti sul tempo necessario alla riparazione, specialmente se non si sono seguiti i fondamentali passi di debugging in seguito descritti. Siate consapevoli che noi tutti vorremmo vedere i bug riparati immediatamente, ma purtroppo gli ostacoli maggiori si incontrano nella riproducibilità e chiarezza della segnalazione. From noreply at ubuntu.com Tue May 29 16:40:42 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 29 May 2012 16:40:42 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22LibreOfficeBugWrangling=5Fit=22_?= =?utf-8?q?by_fabiomarconi?= Message-ID: <20120529164042.21008.87396@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "LibreOfficeBugWrangling_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/LibreOfficeBugWrangling_it?action=diff&rev1=3&rev2=4 * Vi preghiamo di non segnalare bug inerenti LibreOffice senza avere prima letto questa pagina ed avere eseguito le necessarie azioni riportate in seguito. La mancata inosservanza causerà ritardi nell'indirizzamento della vostra segnalazione. * Vi preghiamo di segnalare tutti i vostri bug in LibreOffice eseguendo nel terminale: <
> {{{ubuntu-bug }}} <
> <
> dove è lo specifico pacchetto nel quale è stato rinvenuto il problema. Per esempio, se si ha un problema importando un documento con Writer: <
> {{{ubuntu-bug libreoffice-writer}}} * Un semplice modello di segnalazione di bug: <
> - || 1) lsb_release -rd <
> <
> 2) apt-cache policy libreoffice-writer <
> <
> 3) What is expected to happen in Writer is (cosa dovrebbe succedere) . <
> <
> 4) What happened instead is...(cosa invece accade...) <
> <
> WORKAROUND: Perform the following steps:...|| + || 1) lsb_release -rd <
> <
> 2) apt-cache policy libreoffice-writer <
> <
> 3) What is expected to happen in Writer is (cosa dovrebbe succedere) . <
> <
> 4) What happened instead is...(cosa invece accade...) <
> <
> I have the following extensions installed: lo-menubar, libreoffice-nlpsolver, ... <
> <
> WORKAROUND: Perform the following steps:...|| * Per cortesia non riportare più di un bug per ogni segnalazione. * Per cortesia evitare commenti sul tempo necessario alla riparazione, specialmente se non si sono seguiti i fondamentali passi di debugging in seguito descritti. Siate consapevoli che noi tutti vorremmo vedere i bug riparati immediatamente, ma purtroppo gli ostacoli maggiori si incontrano nella riproducibilità e chiarezza della segnalazione. From adisharoon at ptsteams.com Thu May 31 18:46:48 2012 From: adisharoon at ptsteams.com (Alec Disharoon) Date: Thu, 31 May 2012 13:46:48 -0500 Subject: Ubuntu bug #993187 in Launchpad marked fix released, but there is no fix Message-ID: It seems the many subscribers of this bug, including myself, do not know how to change it back. The bug was marked "fix released" by the user "florin", who, in comment #194 says:"Sorry to everyone, I see that for Ivy Bridge systems the problem is still unresolved, but I can't change the status of this bug to enithing else because it said: " Changable only by project maintainer or bug supervisor"." This is a serious bug (current "heat" is 652), and I'm worried it won't get looked at because of its status. https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/993187 Alec -------------- next part -------------- An HTML attachment was scrubbed... URL: From hggdh2 at ubuntu.com Thu May 31 19:13:46 2012 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Thu, 31 May 2012 14:13:46 -0500 Subject: Ubuntu bug #993187 in Launchpad marked fix released, but there is no fix In-Reply-To: References: Message-ID: <20120531141346.65d4a83b@xango3.home> On Thu, 31 May 2012 13:46:48 -0500 Alec Disharoon wrote: > It seems the many subscribers of this bug, including myself, do not > know how to change it back. The bug was marked "fix released" by the > user "florin", who, in comment #194 says:"Sorry to everyone, I see > that for Ivy Bridge systems the problem is still unresolved, but I > can't change the status of this bug to enithing else because it said: > " Changable only by project maintainer or bug supervisor"." > > This is a serious bug (current "heat" is 652), and I'm worried it > won't get looked at because of its status. > > https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/993187 > > Alec Indeed, and thank you for the heads up. I reset the bug back to Confirmed/High. Some bug status are restricted to developers, maintainers, or Bugcontrollers. Taking *out* of fix-released is one of the actions that are restricted. Cheers, ..C.. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: