Reporting Bugs to GitHub or on bugs.documentfoundation.org against LOOL?

I just found instructions to report bugs in CODE against the Collabora Online GitHub issue tracker.

So far I always reported it against the LOOL component on https://bugs.documentfoundation.org/ .

Are there any guidelines which issue to report where, and where the report will bring most benefit for the developers, other users (which will benefit from fixed issues) and, of course, myself? :wink:

I started to wonder as a bug I had reported there against CODE 3.x and 4.x was fixed in CODE 6.4, but my report in the Documentfoundation buzgilla was confirmed by another user, but not actually handled otherwise. We now closed it as “works for me” in CODE 6.4.

Examples for further bugs are:

  • Bug 138098 - Frequent Crashes in LOOL 6.4 (Collabora CODE 6.4 Docker)
  • Bug 138099 - “Jumpy” Sheets When Switching Sheets and Editing in LOOL Calc 6.4 (Collabora CODE 6.4 Docker)
  • Bug 138101 - Comment Popup Frequently Auto-closes Suddenly and Unexpectedly (CODE 6.4)
  • Bug 123403 - Spreadsheet comments behave strangely in LOOL if copy-pasted
  • Bug 136045 - Rows and Column Headers And Cell Selection Marker Frequently Get “Out Of Sync” With Calc Table
1 Like

@GOhrner Good question! :slight_smile:

Currently, all development effort is effectively on GitHub (since October 01, 2020), and we are tracking the issues on GitHub. You are also more than welcome to test the old bugs/reports on bugzilla against latest version of CODE, and create respective issues on the GitHub repo if they are still valid.

So if you see a general issue affecting both LibreOffice and CODE, then its place is on bugzilla, but if it only affects CODE, then it belongs to the issue tracker on the GitHub repo. :wink:

1 Like

Mh, I’m still confused - how can I check if a bug affects LibreOffice Online in general, and not only CODE? CODE is the only easily installable LOOL distribution I know of… Is there a public non-CODE LOOL instance I could use to determine this?

The bugs I referenced above are all specific to LibreOffice Online (they have nothing to do with the desktop office suite), and they are all reproducible with CODE 6.4 (which is the latest released to my knowledge) or were even introduced only with LOOL from CODE 6.4.

They are filed against the LOOL product in the LibreOffice bugzilla:
image

However, from their behaviour I assume/guess they are not specific to CODE, but affect all LOOL distributions.

So basically all bugs I find in CODE belong into the LibreOffice Bugzilla, except if I assume it’s a packaging issue (or I somehow assume it’s related to some Collabora specific LOOL patch - but how can I know this?) - then I file it against CODE on GitHub?

Hi,

how can I check if a bug affects LibreOffice Online in general, and not only CODE?

Often it will be clear from the bug. A dialog that is broken in the desktop version, will also be broken in Online. I read that you were able to judge the situation with the bugs you refer to.

However, from their behaviour I assume/guess they are not specific to CODE, but affect all LOOL distributions.

For the bug mentioned: yes.

So basically all bugs I find in CODE belong into the LibreOffice Bugzilla, except if I assume it’s a packaging issue …

No. Since recent the code moved to GitHub and the development takes place here. Therefore reporting bugs in GitHub now, is the way to go.
It is the old versus the new situation.
And when the older bugs, reported in bugzilla, are fixed, it of of course reported there too.

HTH - Cor

1 Like

Obviously, but I’m exclusively talking about LibreOffice Online all the time, not about any desktop version, see above - how can I determine if a bug is specific to CODE or occurs in LibreOffice Online in general?

Or maybe there’s some misunderstanding and while I was talking about LibreOffice Online / LOOL everywhere, @kara was referring to the desktop LibreOffice instead in

So if you see a general issue affecting both LibreOffice and CODE, then its place is on bugzilla, but if it only affects CODE, then it belongs to the issue tracker on the GitHub repo. :wink:

?

So was this the case, i.e. all bugs against LibreOffice Online shall be filed on GitHub from now on?

Would it make sense in this case to remove the “LibreOffice Online” product from the Documentfoundation Bugzilla?

Shall I re-report recent bugs currently filed in Bugzilla but relevant for CODE 6.4 on GitHub (and somehow link the issues)?

So was this the case, i.e. all bugs against LibreOffice Online shall be filed on GitHub from now on?

Yes pls do. Sorry for the confusing situation :wink:

Would it make sense in this case to remove the “LibreOffice Online” product from the Documentfoundation Bugzilla?

That is something for TDF and people managing BugZilla there. Unless you are involved there, I would just leave and see what comes up.

Shall I re-report recent bugs currently filed in Bugzilla but relevant for CODE 6.4 on GitHub (and somehow link the issues)?

To be honest, I do not know if there is a general policy here. prolly @kara… does know?

So short on the initial question:

Only brief guidelines: GitHub :slight_smile:
Thanks for your help - much appreciated!!

@GOhrner I see that @cornouws has already asnwered your questions, but let me confirm a few points. Without context (the move to GitHub), I guess it might be a bit confusing.

All development effort of the online repo on TDF infra (what you refer to as LibreOffice Online, which was never released as a package under that name, but only lived there as source code) has been moved to GitHub on October 01, and there is practically no one working on the old repo any more. (What will happen to it (deletion, archival, or something else) will be decided by TDF.) So if I wished to see some bugs fixed as per CODE/Collabora-Online/Online, I would definitely report them on GitHub. :wink:

When I say LibreOffice, I refer to the desktop office suite (LibreOffice core). Sorry if it confused you. Checking the FAQ may also help to clear the fog if any. :slight_smile:

(And if curious about what happened since the move to GitHub, you may check our community roundups as a series of weekly summaries.)

Thanks, that clarifies a lot.

Will the existing bugs filed against the LOOL product in bugzilla be moved here automatically, or shall I re-report the bugs I consider to be relevant?

:wink: I think none applies. Devs are aware of the situation, so keep an eye on what is needed here.

BTW, LibreOffice Online was also always being referred to on https://www.collaboraoffice.com/code/ in the past, that’s were I actually got this name from (and later also found it as a “Product” entry in the Document Foundation Bugzilla)

https://www.collaboraoffice.com/code/ used to contain a categorization of LibreOffice Online, Collabora CODE and Collabora Online, explaining that LOOL was on the edge of development, but also most experimental and CODE more or less being a staging area for Collabora Online, which in turn was intended for productive use for Collabora customers.

(Edit: Concerning the remainder of the first version of this post related to the switch to GitHub, sorry, I should have read the FAQ first. It’s explained there. Thanks.)

@GOhrner Yeah, it can be a bit confusing. No worries. Pleasure! :slight_smile: