Following a suggestion in a discussion among the Bug Coordination Team about how to further improve bug report quality, I have spent the last couple of days making a tool to help with reporting bugs:
Bugger! for Sailfish OS
Bugger! is a little tool to assist reporting bugs on https://forum.sailfishos.org, following the more or less standardized template in use here.
It tries to detect as much of the relevant info itself, lets you add description etc, and will at the end open the Browser to create a (draft) post here.
Reporting bugs in this way should improve Jollas ability to pick them up and track them internally.
For more information about the Bug Coordination effort, see the Help link.
Binary packages are available in the SailfishOS Chum repo (best installed through Chum GUI ), and on the Releases page of the source code repo.
For those who prefer to use Openrepos, the same package is also published here.
Preview/Alpha versions sometimes at chum-testing
Source code is here.
This lives in the sailfishos-chum GitHub org in the hopes that improving it will be a community effort, so please add your issues, enhancements, and other contributions!
It would be interesting to hear about whether this works on older SFOS Releases as it is currently only tested with 4.4.
If you have a device with an older version, and find something interesting to report, please do so at Issue #12
EDIT: my timing sucks. Not only did I release this too late to make this instalment of the Newsletter, it brings the sad news that the forum is incompatible with older SFOS versions now.
Still, through the usage of alternative/Android browsers to submit, it may be possible to have it functioning on older releases.
edit:
" <It tries to detect as much of the relevant info itself, lets you add description etc, and will at the end open the Browser to create a (draft) post here.> "
Detect infos itself ist very important and useful, because many users canât collect all relevant infos from hidden or unknown logfiles etc.
Automatic interaction with browser and as few as possible necessary user interaction is also very helpful. Very good idea! Thank you @nephros !
I like these references and as my mother tongue isnât English, I am not disturbed by this name.
If ever it would have to change, something related to
Autofill
would be very explicit and appealing for the lazy humans that we are (I am) :â)
Installed Bugger right now on one of my Xperia 10âs. Starts without any issues, and happily I saw that the device informations are filled in automatically. Canât report any bug at the moment because there is no.
On Volla installation also succeeded.
Installation on the other X10 also successful, but also no bug at the moment.
Taking into account how âwellâ the reply/writing dialog works with Browser (and Android Firefox too), this application is a great tool to have! I still pretty much always use a desktop computer for it, because of the convenience of having a keyboard and grabbing logs from the phone via SSH. This might shake the balance, though! I also like the name; itâs nice and blatant in describing the application, and it also rolls nicely off the tongue when a bug happens
This release adds a new feature where, if you select a bug âCategoryâ in the UI, it will present some help information on a separate page.
Help is separated into
Links: Links to (mainly official) documentation, forum posts, or Wiki pages
Scripts: actual shell commands to execute (they will not be run by Bugger!, but you can copy them to clipboard)
Community Tips: Some short text to show in case thereâs some information thatâs neither a Wiki/documentation article, nor a script.
One good example on how it can look like is selecting âBluetoothâ as Bug Category, it has all three.
Please contribute to these if you would like to see more, either by using the built-in âSuggestâ feature, by filing an issue, or by submitting Pull Request against meta.js.
The latest Forum software/discourse update broke posting somehow.
Maybe Iâll have to implement API posting (including all the auth thing) but of course that nullifies choice of browser and immediate editing in the browser.
I didnât want this to become a Forum client.
If someone figures out a trick how to get this working again via URL Iâd be grateful.
?_escaped_fragment_ doesnât work, although it should.
For anyone using Privoxy if you have problems, (or any other discourse or other heavy sites), you can either set privoxy buffer-limit to a larger value, or disable brotli compression. See the link above.
and IMO it fits the usage in a way. Maybe I should add an exclamation mark?
