From webmaster at ubuntu.com Sat Sep 3 20:30:19 2016 From: webmaster at ubuntu.com (Help Ubuntu) Date: Sat, 03 Sep 2016 20:30:19 -0000 Subject: =?utf-8?q?=5BCommunity_Help_Wiki=5D_Update_of_=22ReportingBugs=22_by_pena?= =?utf-8?q?lvch?= Message-ID: <20160903203019.28882.74124@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Community Help Wiki" for change notification. The "ReportingBugs" page has been changed by penalvch: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=294&rev2=295 Comment: RM'ed etiquette requesting non-announcing as going against a river current. * '''Please do not report bugs about software in [[PPA]]s.''' <
> This is because software in PPAs are not provided by the official Ubuntu repositories, and in turn not supported. Instead, the PPA homepage would have a contact point and preference of the PPA provider. The exception is [[LibreOffice]] as per [[https://lists.launchpad.net/libreoffice/msg00072.html|this mail]], as LibreOffice is too big to be tracked via email: as described in the mail, file a bug on Launchpad with tag `ppa`. * '''Please do not report upgrade failures when you have installed software that is self-compiled, from a third party deb not provided by the Ubuntu repositories, or from a PPA.''' In order to maximize your upgrade success, all this software would need to be uninstalled, or replaced with the corresponding software from the Ubuntu repositories if it is mandatory to keep. * '''Please do not add project tasks to bug reports that are invalid because they are not supported'''. <
> For example, if you were using the LibreOffice PPA and reported a bug against the package libreoffice (Ubuntu), which would be marked Status Invalid, please do not add the Launchpad Project [[https://launchpad.net/df-libreoffice|df-libreoffice]] to the report, or change the package libreoffice (Ubuntu) to the project df-libreoffice. The purposes of adding the upstream project to a report is to track valid bugs in Ubuntu that are valid upstream, and may have been reported upstream, not to start another upstream bug tracker. - * '''Please do not announce in a report you did not file, that you filed a new report.''' * '''Many of the triagers and developers who are providing support to you, are volunteers doing so out of altruism. Please keep this in mind when making your comments.''' * '''Please do not compress/tar attachments when posting them to a bug report.''' <
> Launchpad doesn't have the same attachment size restriction as other bug reporting platforms. Hence, one may attach large files without fear of rejection. While it is appreciated that one is being considerate and efficient regarding reducing network bandwidth traffic, and storage requirements, this is counteracted by hindering the speed with which a triager or developer may begin analyzing the logs you provide. * '''Please test the latest version of the software from upstream.''' <
> Testing the latest upstream release helps in finding out if the issue is a downstream (Ubuntu) issue, or an upstream one as well. If an upstream, then they may also be engaged in seeking support for the problem. From noreply at ubuntu.com Tue Sep 6 20:02:27 2016 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 06 Sep 2016 20:02:27 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingProgramCrash=22_by_mter?= =?utf-8?q?ry?= Message-ID: <20160906200227.24637.2@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingProgramCrash" page has been changed by mterry: http://wiki.ubuntu.com/DebuggingProgramCrash?action=diff&rev1=123&rev2=124 Comment: Add info for getting dbgsym packages from PPAs sudo apt-get install yelp-dbgsym=2.22.1-0ubuntu2.8.04.1 }}} You can also use the Synaptic Package Manager to search for yelp-dbgsym and install it from there. + === Installing dbgsym packages from a PPA === + + If you are debugging a PPA package, have no fear! You can still install `-dbgsym` packages for them. Where normally you would have a line like: + + {{{ + deb http://ppa.launchpad.net/TEAM/PPA/ubuntu RELEASE main + }}} + + Simply add '''`main/debug`''' at the end, like so: + + {{{ + deb http://ppa.launchpad.net/TEAM/PPA/ubuntu RELEASE main main/debug + }}} + + Then `apt update` and `apt install` the `-dbgsym` packages you want. + == Manually finding required debug symbols == The above procedure will install the debug symbol package for yelp only. For many packages, they use libraries shared between different packages. Hence, in order to obtain a readable/more readable stacktrace, or perform other debugging tasks, one must find the debug symbols for these shared libraries. For example, if one had attached gdb to an application and got the following output:{{{ From noreply at ubuntu.com Sun Sep 11 17:11:48 2016 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 11 Sep 2016 17:11:48 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Upstream/kernel=22_by_penal?= =?utf-8?q?vch?= Message-ID: <20160911171148.5906.40666@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Upstream/kernel" page has been changed by penalvch: http://wiki.ubuntu.com/Bugs/Upstream/kernel?action=diff&rev1=8&rev2=9 Comment: Added source URL for page in # comment as FYI. + # The page contents are sourced from https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_upstream_kernel_bugs <> <> From brian at ubuntu.com Thu Sep 15 22:49:05 2016 From: brian at ubuntu.com (Brian Murray) Date: Thu, 15 Sep 2016 15:49:05 -0700 Subject: Bug pattern and cleanup Message-ID: <20160915224905.GX6405@murraytwins.com> I was recently writing an apport bug pattern[1] for a bug report and discovered a set of bugs (32!) which could use a pattern and some consolidation. If anybody is interested in learning how to write a bug pattern let me know or find me on freenode irc (bdmurray). [1] https://code.launchpad.net/~ubuntu-bugcontrol/apport/ubuntu-bugpatterns/ -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: not available URL: From es20490446e at gmail.com Fri Sep 16 10:13:37 2016 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Fri, 16 Sep 2016 12:13:37 +0200 Subject: Bug pattern and cleanup In-Reply-To: <20160915224905.GX6405@murraytwins.com> References: <20160915224905.GX6405@murraytwins.com> Message-ID: <681dbcd8-df8a-1b28-f443-f97e36390b80@gmail.com> Brian Murray: > If anybody is interested in learning how to write a bug > pattern let me know or find me on freenode irc (bdmurray). Perhaps having some of it at (https://wiki.ubuntu.com/Bugs/Triage) could help, although that page obviously needs a clean up. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4747 bytes Desc: S/MIME Cryptographic Signature URL: From noreply at ubuntu.com Wed Sep 28 17:45:27 2016 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Wed, 28 Sep 2016 17:45:27 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Bug_statuses=22_by_es204904?= =?utf-8?q?46e?= Message-ID: <20160928174527.27750.89271@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Bug statuses" page has been changed by es20490446e: http://wiki.ubuntu.com/Bugs/Bug%20statuses?action=diff&rev1=76&rev2=77 * Upstream task: the fix is in bzr/CVS/git/SVN, or committed to some place. * '''Fix Released''': - * Ubuntu task: a fix was uploaded to an official Ubuntu repository. - * N.B. This '''does not''' include -proposed (i.e. trusty-proposed). - * Please don't hesitate to add a changelog as a comment, so people know in which package version the fix was released in. - * If the current development release has the fix applied, it is {{{Fix Released}}}. If a [[StableReleaseUpdates|stable release needs to be fixed]] also, use the "Target to release" link to nominate it for that release. - * Upstream task: a release tarball was announced and is publicly available. + * Ubuntu task: fixed in the latest Ubuntu release, as a standard upgrade. + * /!\ If the bug stills affects an older Ubuntu release, please nominate it for that series. Otherwise people won't know it isn't fixed there! + * Indicate which package version the fix was released in. + + * Upstream task: fix available in a tarball. * '''Won't Fix''': * This status is sometimes used when the fix is too controversial.