From brian at ubuntu.com Wed Jan 6 18:11:02 2016 From: brian at ubuntu.com (Brian Murray) Date: Wed, 6 Jan 2016 10:11:02 -0800 Subject: Launchpad Greasemonkey Scripts In-Reply-To: <20151118232636.GM6296@murraytwins.com> References: <20151118232636.GM6296@murraytwins.com> Message-ID: <20160106181102.GN4032@murraytwins.com> On Wed, Nov 18, 2015 at 03:26:36PM -0800, Brian Murray wrote: > I've worked on and use some greasemonkey scripts[1] that modify Launchpad > and make some tasks easier. One of them, lp_button_tags, isn't currently > working and I thought this would make a good Google Code In project. > Having said that it wouldn't be very rewarding if I'm the only person > still using these. > > So is anybody else still using these scripts? > > Or have you never heard of them and do you want the script which makes > it easier to tag bugs working again? The button tags script is working again thanks to Evan McIntire who fixed the Google Code In task I created. He also updated the tags xml file so those are now current! -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: Digital signature URL: From noreply at ubuntu.com Sun Jan 10 22:39:26 2016 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 10 Jan 2016 22:39:26 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22X/Troubleshooting=22_by_penalvch?= Message-ID: <20160110223926.22177.72513@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "X/Troubleshooting" page has been changed by penalvch: http://wiki.ubuntu.com/X/Troubleshooting?action=diff&rev1=61&rev2=62 Comment: Initial consolidation of X/Debugging et. al. into X/Troubleshooting. <> - For hard bugs the analysis phase is the most important, and most challenging part of bug work. Depending on how the bug is behaving, there are multiple directions to investigate the issue. Here's some different approaches: + || {{https://launchpadlibrarian.net/10142846/xswat-192.png}} || + ||<>|| - === Common Problems === + = Identifying if the issue is a bug or not = + + If you aren't sure if you have encountered a software bug in Ubuntu, then you would want to seek help in determining if the issue is a bug or not from [[https://help.ubuntu.com/community/ReportingBugs|here]]. + + If you have confirmed the issue is a bug, please read on. + + = Determining which type of bug you have = + + Not all bugs where X seems to be the root cause are in fact an X related bug. Hence, here is documentation on potential root causes: + + Booting + * [[https://help.ubuntu.com/community/BootOptions|Boot Options]] + * [[DebuggingKernelBoot|Debugging Kernel Boot Problems]] + + Display Issues + * [[X/Troubleshooting/3D|3D / GLX corruption and other issues]] + * [[Kernel/Debugging/Backlight|Backlight issues]] + * [[X/Troubleshooting/BlankScreen|Blank Screen on startup issues]] + * [[X/i8xxUnsupported|i855 is Unsupported]] - Explanation of why i845, i855, i865, etc. chips aren't supported + * [[X/Troubleshooting/HugeFonts|Fonts displayed way too big]] + * [[X/Troubleshooting/Freeze|Freeze issues]] + * [[X/Troubleshooting/IntelPerformance|Intel graphics performance issues]] + * [[X/MonitorDetection|Monitor detection]] + * [[X/Troubleshooting/Resolution|Resolution detection]] + * [[X/Troubleshooting/VideoDriverDetection|Video driver detection]] + General Issues * [[X/Glossary|Glossary]] - Common error messages and terminology * [[X/Troubleshooting/HighCPU|High CPU usage issues]] * [[X/Troubleshooting/HighMemory|High memory usage issues]] + * [[X/Bugs/Transitions|X Transitions]] - Explanation for "installing xserver-xorg-core would break existing software" + * [[X/Troubleshooting/XError|Program received an X Window System error]] * [[DebuggingKernelSuspend|Suspend and Resume issues]] - * [[X/Troubleshooting/XError|Program received an X Window System error]] - * [[X/Bugs/Transitions|X Transitions]] - Explanation for "installing xserver-xorg-core would break existing software" - - Display Issues - * [[X/Troubleshooting/VideoDriverDetection|Video driver detection]] - * [[X/MonitorDetection|Monitor detection]] - * [[X/Troubleshooting/Resolution|Resolution detection]] - * [[X/Troubleshooting/Freeze|Freeze issues]] - * [[Kernel/Debugging/Backlight|Backlight issues]] - * [[X/Troubleshooting/BlankScreen|Blank Screen on startup issues]] - * [[X/Troubleshooting/3D|3D / GLX corruption and other issues]] - * [[X/Troubleshooting/HugeFonts|Fonts displayed way too big]] - * [[X/Troubleshooting/IntelPerformance|Intel graphics performance issues]] - * [[X/i8xxUnsupported|i855 is Unsupported]] - Explanation of why i845, i855, i865, etc. chips aren't supported Input Issues + * [[DebuggingKeyboardDetection|Keyboard detection]] * [[Hotkeys/Troubleshooting|Multimedia hotkey problems]] - * [[DebuggingKeyboardDetection|Keyboard detection]] * [[DebuggingTouchpadDetection|Touchpad detection]] - === Troubleshooting Techniques === - Booting - * [[https://help.ubuntu.com/community/BootOptions|Boot Options]] - * [[DebuggingKernelBoot|Debugging Kernel Boot Problems]] + = Reporting a confirmed X bug to Launchpad = + + == Initial filing of the report == + + First, one will want to familiarize themselves with how to report bugs effectively as per [[https://wiki.ubuntu.com/ReportingBugs|here]]. + + Once this is reviewed, please file a new bug report with Ubuntu via a terminal: + {{{ + ubuntu-bug xorg + }}} Please ensure you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information. + + == Including enough information for a developer to work on it == + + One will want to answer the following questions: + * Does the report include debugging information from the relevant article relating to the reported issue? + * Is this a regression? + * Does this happen in the latest version of Ubuntu? + * Does this happen in the latest version available from upstream? + + = Debugging techniques = + * [[X/NonGraphicalBoot|Non-Graphical Booting]] - Running X manually, without a display manager (like lightdm, kdm, gdm...) * [[X/Debugging/WirelessWithoutX|Wireless Without X]] - How to get a wireless network connection without X. * [[X/Debugging/WiredWithoutRouter|Direct Wired Without WAP]] - How to connect two laptops with direct ethernet cord. - Crashes and Freezes + Crashes and Freezes * [[X/Backtracing|X Backtracing]] - How to collect a backtrace for an X crash - * [[X/FixingCrashes|X Crash Fixing]] - How to fix X crashes * [[X/InterpretingIntelGpuDump|Interpreting GPU Dumps]] - Ringbuffers, batchbuffers, and the meaning of `intel_gpu_dump` output * [[X/DebuggingWithValgrind|Valgrind]] - Debugging memory leaks Other Techniques + * [[X/Dev/DeviceTreeHWDetection|Device Tree]] * [[X/Bisecting|X Bisecting]] - Using bisection techniques to solve regressions or backport fixes * [[X/Testing/Touch]] - Touchscreen and multi-touch testing + + = Triaging and tagging X bugs = + + Please see [[https://wiki.ubuntu.com/X/Triaging|here]] for more on triaging X bugs, and [[https://wiki.ubuntu.com/X/Tagging|here]] for tagging. + + = Fixing an X crash = + + * For more on this, please see [[https://wiki.ubuntu.com/X/FixingCrashes|here]]. - * [[X/Quirks|X Quirks]] - Fixes for some common hardware-specific issues + * [[X/Quirks|X Quirks]] - Fixes for some common hardware-specific issues. - * [[X/Dev/DeviceTreeHWDetection|Device Tree]] + + = Other Resources = + + * [[https://help.ubuntu.com/community/Video|Video Resources]] at help.ubuntu.com + * For installing [[https://help.ubuntu.com/community/BinaryDriverHowto/AMD|fglrx]] or [[https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia|nvidia]] proprietary drivers. ---- CategoryDebugging From noreply at ubuntu.com Tue Jan 12 03:08:20 2016 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 12 Jan 2016 03:08:20 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingKernelSuspend=22_by_pen?= =?utf-8?q?alvch?= Message-ID: <20160112030820.12782.57029@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingKernelSuspend" page has been changed by penalvch: http://wiki.ubuntu.com/DebuggingKernelSuspend?action=diff&rev1=48&rev2=49 Comment: The article as it stands is largely utilized by non-developers, who don't go beyond what's directly asked of them. Hence, expanded requested tests to maximize information provided is valuable. = Introduction = - This page describes how to debug Suspend to RAM/Resume problems on your computer. Do not confuse this with Suspend to disk (also known as hibernate). [[UnderstandingSuspend]] may have useful background information on where problems can occur. + This page describes how to debug suspend to RAM, and resume from suspend to RAM problems with your computer. - Suspend and Resume use facilities within your BIOS called ACPI, or Advanced Configuration and Power Interface. Linux provides an ACPI subsystem that manages the suspend and resume process. Usually problems occur when resuming, and normally the culprit is a device driver that does not recover from a powered down state. If your computer successfully performs a suspend, then it is quite likely any resume problems are due to another device driver and not the ACPI subsystem. + For issues regarding suspend to disk (i.e. hibernate), please see [[https://wiki.ubuntu.com/DebuggingKernelHibernate|here]]. + Suspend and resume use facilities within your BIOS called ACPI, or Advanced Configuration and Power Interface. Linux provides an ACPI subsystem that manages the suspend and resume process. Usually problems occur when resuming, and normally the culprit is a device driver that does not recover from a powered down state. If your computer successfully performs a suspend, then it is quite likely any resume problems are due to another device driver and not the ACPI subsystem. + - The debugging procedure described below assumes you have the latest BIOS from your vendor, and requires a linux kernel with the capability of "/sys/power/pm_trace". You can ensure that pm_trace'ing is possible by looking in the directory /sys/power/ (from a terminal type {{{ls /sys/power/}}}) + The debugging procedure described below assumes you have already installed the latest BIOS from your vendor, and requires a linux kernel with the capability of "/sys/power/pm_trace". You can ensure that pm_trace'ing is possible by looking in the directory /sys/power/ (from a terminal type {{{ls /sys/power/}}}) to see if a file called pm_trace exists. = Debugging information to provide in your bug report = + In order to identify the root cause of the issue, all of the following information needs to be provided, uncompressed and untarred, in order for a developer to work on it. + 1. Which part of the process does the issue occur with, the suspend to ram, or resuming from? - 1. Please advise on how you suspended, and resumed specifically. For example: + 1. Please advise how you suspended specifically. For example: * Executing at a terminal pm-suspend * Shutting the lid of your laptop, which is set to suspend on close. * Clicking the word Suspend in the GUI. * The computer suspends automatically on inactivity. + 1. Please advise how you resumed specifically. For example: + * Pressed the power button + * Lifted the lid + * Clicked a key on the keyboard - 1. While booted into the latest [[https://wiki.ubuntu.com/Kernel/MainlineBuilds|non-daily mainline kernel]], please attach to your report: {{{ + 1. While booted into the latest [[https://wiki.ubuntu.com/Kernel/MainlineBuilds|non-daily mainline kernel]], execute at a terminal: {{{ cat /proc/acpi/wakeup > wakeup }}} - 1. While booted into the latest [[https://wiki.ubuntu.com/Kernel/MainlineBuilds|non-daily mainline kernel]], please attach to your report the resume trace mentioned below. + 1. While booted into the latest [[https://wiki.ubuntu.com/Kernel/MainlineBuilds|non-daily mainline kernel]], execute at a terminal:{{{ + sudo su + echo freezer > /sys/power/pm_test + exit + }}} Please attach to your report the resume trace mentioned below. + 1. While booted into the latest [[https://wiki.ubuntu.com/Kernel/MainlineBuilds|non-daily mainline kernel]], execute at a terminal:{{{ + sudo su + echo devices > /sys/power/pm_test + exit + }}} Please attach to your report the resume trace mentioned below. + 1. While booted into the latest [[https://wiki.ubuntu.com/Kernel/MainlineBuilds|non-daily mainline kernel]], execute at a terminal:{{{ + sudo su + echo platform > /sys/power/pm_test + exit + }}} Please attach to your report the resume trace mentioned below. + 1. While booted into the latest [[https://wiki.ubuntu.com/Kernel/MainlineBuilds|non-daily mainline kernel]], execute at a terminal:{{{ + sudo su + echo processors > /sys/power/pm_test + exit + }}} Please attach to your report the resume trace mentioned below. + 1. While booted into the latest [[https://wiki.ubuntu.com/Kernel/MainlineBuilds|non-daily mainline kernel]], execute at a terminal:{{{ + sudo su + echo core > /sys/power/pm_test + exit + }}} Please attach to your report the resume trace mentioned below. + 1. While booted into the latest [[https://wiki.ubuntu.com/Kernel/MainlineBuilds|non-daily mainline kernel]], execute at a terminal:{{{ + {{{ + sudo su + echo none > /sys/power/pm_test + exit + }}} Please attach to your report the resume trace mentioned below. + 1. Please provide the output of the following terminal command: {{{ + cat /sys/kernel/debug/suspend_stats }}} - 1. If you have a graphics related issue after resume (corruption, display blank, etc.) please [[https://help.ubuntu.com/community/DebuggingSystemCrash#SSH|SSH]] into your machine and capture both /var/log/Xorg.0.log and /var/log/Xorg.0.log.old . + 1. If you have a graphics related issue after resume (corruption, display blank, etc.) please [[https://help.ubuntu.com/community/DebuggingSystemCrash#SSH|SSH]] into your machine and capture both /var/log/Xorg.0.log and /var/log/Xorg.0.log.old. == "resume-trace" debugging procedure for finding buggy drivers == - Resume problems are difficult to debug. The approach used here needs to make notes on progress during resume and be able to recover them after a manual reboot. But there is no non-volatile storage available at the time resume is bringing up your computer. The only hardware on a PC motherboard that retains information across power cycles is the real time clock (RTC), so that is what is used. For those that want to know the details, please read Documentation/power/s2ram.txt in your kernel sources, or see [[https://www.kernel.org/doc/Documentation/power/s2ram.txt|here]]. The implementation of suspend/resume debug trace is in drivers/base/power/trace.c. + Resume problems are difficult to debug. The approach used here needs to make notes on progress during resume and be able to recover them after a manual reboot. But there is no non-volatile storage available at the time resume is bringing up your computer. The only hardware on a PC motherboard that retains information across power cycles is the real time clock (RTC), so that is what is used. For those that want to know the details, please read Documentation/power/s2ram.txt in your kernel sources, or see [[https://www.kernel.org/doc/Documentation/power/s2ram.txt|here]]. The implementation of suspend/resume debug trace is in drivers/base/power/trace.c. Caveat Emptor: Using the following debug suggestions will radically change the values in your RTC chip, so much so that your file system will think it has been eons since the last fsck. You can avoid a long fsck delay by using 'tune2fs'. For example, 'tune2fs -i 0 /dev/sda1' disables fsck on boot. But first you'll want to use 'tune2fs -l ' to find your current settings - look at the "Check interval" setting. From a fresh install, the default time interval is 15552000, which is 6 months. - Remember that when you are all done, you'll want to set your RTC clock back. Note that NTP by itself is not sufficient to recover the correct time of day, since by default NTP is configured to do nothing if the time is off by more than 1000 seconds. You must first use the 'ntpdate' or 'date' command to get the clock close. + Remember that when you are all done, you'll want to set your RTC clock back. Note that NTP by itself is not sufficient to recover the correct time of day, since by default NTP is configured to do nothing if the time is off by more than 1000 seconds. You must first use the 'ntpdate' or 'date' command to get the clock close. - OK. With that understood.... In order to simulate your suspend/resume process, enter the following commands: + In order to simulate your suspend/resume process, enter the following commands: - {{{ sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend" }}} @@ -44, +83 @@ At this point your computer should enter the suspend state within a few seconds. Usually the power LED will slowly flash when in the suspended state. When that has happened, initiate the resume process by pressing the power button. Observe closely if the disk light comes on briefly. This indicates that resume has begun. If resume fails to complete, then press the power button until the computer turns off. Power on your computer making sure that it loads the same kernel that exhibited the resume problem. You have about 3 minutes to start this boot process before the information saved in the RTC gets corrupted. Start a console and enter: - {{{ dmesg > dmesg.txt }}} You can edit this file and find lines similar to these: - {{{ [ 11.323206] Magic number: 0:798:264 [ 11.323257] hash matches drivers/base/power/resume.c:46 }}} There may well be another 'hash matches' line beyond that. If so, then you are in luck because the last one is the likely culprit. For example: - {{{ hash matches device i2c-9191 }}} - The only way to prove this is to remove the module prior to initiating suspend. Repeat as needed... + The only way to prove this is to remove the module prior to initiating suspend. Repeat as needed. - If you get a device number rather than name, lspci and /sys/devices/pci* are your friends. + If you get a device number rather than a name, lspci and /sys/devices/pci* are your friends. As well, please attach your dmesg.txt to your bug report. - = Further hints = + = Further reading = [[http://ubuntuforums.org/showthread.php?p=3066404|Detailed analysis of ACPI kernel code for debugging a suspend problem]] ------ '''Also see:''' + * [[https://wiki.ubuntu.com/UnderstandingSuspend]] * [[DebuggingKernelHibernate]] * [[http://lxr.linux.no/linux/Documentation/power/s2ram.txt|How to get s2ram working]] * [[http://lxr.linux.no/linux/Documentation/power/basic-pm-debugging.txt|Testing suspend to disk (hibernate)]] From noreply at ubuntu.com Sun Jan 24 20:49:57 2016 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 24 Jan 2016 20:49:57 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22LibreOfficeBugWrangling=22_by_pe?= =?utf-8?q?nalvch?= Message-ID: <20160124204957.9028.24959@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=27&rev2=28 Comment: 1) RM'ed commented out preface. 2) Added triage statement requesting document. 3) RM'ed footnote syntax as it puts it after categories, which looks odd. 4) Minor presentation fixes. - ## 20121122 https://launchpad.net/~penalvch When one files a bug via apport against libreoffice via ubuntu-bug libreoffice and did not install the libreoffice meta package, the filed bug report tends not to provide enough information to triage appropriately. Ex. https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1080509 one has no idea what specific LO packages they actually have installed. Hence, asking for apt-show-versions -r libreoffice* in the bug reporting template section is an extremely helpful way an original reporter can provide information for triagers to work on the problem without asking for follow up information, and waiting for the response. However, not all packages in https://launchpad.net/ubuntu/+source/libreoffice have libreoffice in the name, so some will be missed (ex. ure, python-uno, etc.). If a more comprehensive command exists to provide all the installed packages for libreoffice with versions compactly, that does not contain the word libreoffice in the package name, please replace. I just have not come across a more relevant one. Thank you for your understanding. - Available languages: [[https://wiki.ubuntu.com/LibreOfficeBugWrangling_it| Italiano]] <> @@ -10, +8 @@ = How to file a bug = * 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 may delay your bug getting addressed as quickly as possible. - * First, before filing a bug report, please make sure you uninstall all openoffice.org packages first, then install the full LibreOffice suite to avoid [[https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-libreoffice-split|package split collatoral damage]], by executing at a terminal: + * First, before filing a bug report, please make sure you remove all openoffice.org packages first, then install the full LibreOffice suite to avoid [[https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-libreoffice-split|package split collateral damage]], by executing at a terminal: || {{{sudo apt-get -y install libreoffice}}}|| * 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}}} @@ -19, +17 @@ || 1) lsb_release -rd <
> <
> 2) apt-cache policy <
> <
> apt-show-versions -r libreoffice* <
> <
> 3) What is expected to happen in Writer is . <
> <
> 4) What happened instead is... <
> <
> I have the following extensions installed: lo-menubar... <
> <
> WORKAROUND: Perform the following steps:...|| /!\ Please note the above 1) and 2) are terminal commands to execute, and post the results of when initially filing your bug report. As well, you may need to install the package [[https://launchpad.net/ubuntu/+source/apt-show-versions|apt-show-versions]]. * 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. + * 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 nonconstructive, irritating to others who read your E-Mail, and perceived as spam. 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. = Debugging = @@ -57, +55 @@ * Please consult https://wiki.ubuntu.com/Apport to ensure Apport is enabled. * Please make sure LibreOffice debug symbols are installed (libreoffice-dbg, uno-libs3-dbg, and ure-dbg). * If this happened while a particular document was open or you were manipulating the document in a certain way, please attach that document to the bug report with detailed, click-for-click steps on how to reproduce the crash. - * For suspected GUI/desktop environment driven crashes (ex. reproducible in Kubuntu but not Xubuntu), please uninstall the packages libreoffice-gtk, libreoffice-gnome, libreoffice-gtk3, and libreoffice-kde and comment on if this changes anything. + * For suspected GUI/desktop environment driven crashes (ex. reproducible in Kubuntu but not Xubuntu), please remove the packages libreoffice-gtk, libreoffice-gnome, libreoffice-gtk3, and libreoffice-kde and comment on if this changes anything. == The Whole system hangs or boots to the login screen == @@ -69, +67 @@ = Triaging LibreOffice bugs = + == Requesting a document == + + Many bugs are dependent on the document. Hence, it is vital the original reporter provide a minimal test case that demonstrates the issue. An example triaging statement: + ||Thank you for reporting this and helping make Ubuntu better. Regarding this report:<
>Could you please attach to this report a document that reproduces this problem? Please ensure that:<
>1) If a concern of privacy exists due to the sensitive information in the document, you need to remove it. Please do not directly e-mail anyone the sensitive document as this puts an undue burden on the other person to maintain a chain of custody that is not legally maintainable. + 2) Please reduce the document so that it has the least amount of content possible, but still demonstrates this problem. The bigger the document, the harder it is for a developer to quickly review the document, and provide a fix.<
><
> Thank you for your understanding.|| + == 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. @@ -79, +83 @@ * 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). * For Wishlist reports, they would typically 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. <
> An appropriate [[https://wiki.ubuntu.com/Bugs/Bug%20statuses|Won't Fix]] [[https://wiki.ubuntu.com/Bugs/Bug%20importances|Wishlist]] reply: - ||Thank you for reporting this and helping making Ubuntu better. Regarding this report:<
>- This is a clearcut upstream issue. You are 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. <
><
> Thank you for your understanding.|| + ||Thank you for reporting this and helping make Ubuntu better. Regarding this report:<
>- This is a clearcut upstream issue. Could you please send this to the developers of the software by following the instructions at [[http://wiki.documentfoundation.org/BugReport]]? Please provide a URL of the upstream bug, so a bugwatch may be added that will advise 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. <
><
> Thank you for your understanding.|| == Apache OpenOffice / OpenOffice.org bugs == @@ -90, +94 @@ == How to forward bugs Upstream == - * Once marked Triaged, a bug that is reproducible in the upstream release would want to be filed upstream using the [[https://www.libreoffice.org/get-help/bug/|LibreOffice Bug Submission Assistant]] <>. + * Once marked Triaged, a bug that is reproducible in the upstream release would want to be filed upstream using the [[https://www.libreoffice.org/get-help/bug/|LibreOffice Bug Submission Assistant]], or in the old fashioned way at https://bugs.freedesktop.org/enter_bug.cgi?product=LibreOffice. * 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.