# Testing and bug fixing for Collabora Desktop

**URL:** <https://forum.collaboraonline.com/t/testing-and-bug-fixing-for-collabora-desktop/4603>\
**Category:** Development\
**Created:** [April 16, 2026, 9:10am UTC](https://forum.collaboraonline.com/t/testing-and-bug-fixing-for-collabora-desktop/4603 "2026-04-16T09:10:11Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![Regina](https://avatars.discourse-cdn.com/v4/letter/r/d78d45/32.png) [@Regina](https://forum.collaboraonline.com/u/Regina)\
**Post date:** [April 16, 2026, 9:10am UTC](https://forum.collaboraonline.com/t/testing-and-bug-fixing-for-collabora-desktop/4603/1 "2026-04-16T09:10:11Z")

</div>

I want to test the current developments on SmartArt and provide patches in case I know why something is wrong. I need help in starting with that.

I work on Windows 11 and use its WSL2 and Visual Studio 2022. I want to use a Windows version of Collabora Desktop, not a Linux version. I do not want to work on Collabora Online.

I’m no professional developer thus treat me as newcomer in you answers.

(A) Does Collabora provide something similar to the “daily builds” of LibreOffice?

(B) Is there a bugtracker where I can see known bugs and report bugs I find?

(C) I guess, that I need to start using `git clone`. From where?

(D) Needs Collabora Desktop other or additional externals than LibreOffice?

(E) Is the build process configured by an autogen.input file, executed by autogen.sh as in LibreOffice?

(F) Which license is used for the code? Which license agreement do you need from me?

Kind regards,

Regina Henschel

---

<div class="post-metadata">

**Author:** ![vmiklos](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.collaboraonline.com/vmiklos/32/787_2.png) [@vmiklos](https://forum.collaboraonline.com/u/vmiklos)\
**Post date:** [April 16, 2026, 9:19am UTC](https://forum.collaboraonline.com/t/testing-and-bug-fixing-for-collabora-desktop/4603/2 "2026-04-16T09:19:15Z")

</div>

Hi Regina,

> (B) Is there a bugtracker where I can see known bugs and report bugs I find?

Please see here: [Issues · CollaboraOnline/online · GitHub](https://github.com/CollaboraOnline/online/issues/)

> (C) I guess, that I need to start using `git clone`. From where?

See [Build Collabora Office for Windows | Collabora Online - Community Page](https://collaboraonline.github.io/post/build-co-windows/)

> (D) Needs Collabora Desktop other or additional externals than LibreOffice?

If you just follow the instructions, you should be fine.

> (E) Is the build process configured by an autogen.input file, executed by autogen.sh as in LibreOffice?

There is an ‘autogen.py’ to take options from ‘autogen.input’, like core.git does. But it’s optional.

> (F) Which license is used for the code? Which license agreement do you need from me?

No need to send a license statement, just sign off your commits with ‘git commit -s’. See [online/CONTRIBUTING.md at main · CollaboraOnline/online · GitHub](https://github.com/CollaboraOnline/online/blob/main/CONTRIBUTING.md#sign-your-work)

Regards,

Miklos

---

<div class="post-metadata">

**Author:** ![Timur](https://avatars.discourse-cdn.com/v4/letter/t/c67d28/32.png) [@Timur](https://forum.collaboraonline.com/u/Timur)\
**Post date:** [April 16, 2026, 10:36am UTC](https://forum.collaboraonline.com/t/testing-and-bug-fixing-for-collabora-desktop/4603/3 "2026-04-16T10:36:06Z")

</div>

> [@Regina](#):
>
> (A) Does Collabora provide something similar to the “daily builds” of LibreOffice?

For desktop Collabora Office, builds are at [https://www.collaboraoffice.com/downloads/CODA-Hd7wwbJWxm/](https://www.collaboraoffice.com/downloads/CODA-Hd7wwbJWxm/)  
For Collabora Office Classic, snapshot builds are at [https://www.collaboraoffice.com/downloads/Collabora-Office-25-Snapshot/Windows/](https://www.collaboraonline.com/collabora-office-latest-snapshots/) (let us see why Windows not so current)  
Best, Timur

---

<div class="post-metadata">

**Author:** ![Regina](https://avatars.discourse-cdn.com/v4/letter/r/d78d45/32.png) [@Regina](https://forum.collaboraonline.com/u/Regina)\
**Post date:** [April 16, 2026, 11:50am UTC](https://forum.collaboraonline.com/t/testing-and-bug-fixing-for-collabora-desktop/4603/4 "2026-04-16T11:50:25Z")

</div>

> [@Timur](#):
>
> For desktop Collabora Office, builds are at [https://www.collaboraoffice.com/downloads/CODA-Hd7wwbJWxm/](https://www.collaboraoffice.com/downloads/CODA-Hd7wwbJWxm/)

I’ve got it. But I do not see the SmartArt work of Armin. LibreOffice has it, if experimental features are on. Is it contained in the build at all? If yes, how do I activate it?

---

<div class="post-metadata">

**Author:** ![alalg](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.collaboraonline.com/alalg/32/2023_2.png) [@alalg](https://forum.collaboraonline.com/u/alalg)\
**Post date:** [April 16, 2026, 2:03pm UTC](https://forum.collaboraonline.com/t/testing-and-bug-fixing-for-collabora-desktop/4603/5 "2026-04-16T14:03:50Z")

</div>

Hi Regina,  
In principle the same as for office: use ‘ACTIVATE\_ADVANCED\_DIAGRAM\_FEATURES’. I am not sure for CODA, but for COOL this means to use

‘ACTIVATE\_ADVANCED\_DIAGRAM\_FEATURES=1 make run’  
instead of  
‘make run’

I just cherry-picked the development that I did on LO so far to COOL\_26\_04, so it’s on it’s way there and thus also for CODA. I will continue development now there, I do not want to do more harm to others.

---

<div class="post-metadata">

**Author:** ![Regina](https://avatars.discourse-cdn.com/v4/letter/r/d78d45/32.png) [@Regina](https://forum.collaboraonline.com/u/Regina)\
**Post date:** [April 16, 2026, 4:08pm UTC](https://forum.collaboraonline.com/t/testing-and-bug-fixing-for-collabora-desktop/4603/6 "2026-04-16T16:08:25Z")

</div>

> [@alalg](#):
>
> ‘ACTIVATE\_ADVANCED\_DIAGRAM\_FEATURES=1 make run’  
> instead of  
> ‘make run’

I start the program with `Collabora Office.exe`. I’m on Windows. I do not have an own build yet. `ACTIVATE_ADVANCED_DIAGRAM_FEATURES=1` is in my Windows environment variables. But when I open a pptx with SmartArt, it is converted to a group of shapes.

> [@alalg](#):
>
> I just cherry-picked the development that I did on LO so far to COOL\_26\_04, so it’s on it’s way there and thus also for CODA.

That means, that I need to wait?

---

<div class="post-metadata">

**Author:** ![alalg](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.collaboraonline.com/alalg/32/2023_2.png) [@alalg](https://forum.collaboraonline.com/u/alalg)\
**Post date:** [April 16, 2026, 6:41pm UTC](https://forum.collaboraonline.com/t/testing-and-bug-fixing-for-collabora-desktop/4603/7 "2026-04-16T18:41:16Z")

</div>

It is in ‘core’ of new repro, if you have that you can use Cool as I described above. I have not checked with CODA but you need to set that EnvVar for it - not sure if that just works on starting it, you will have to try that.  
And: I hope all really important stuff is good on your side..? Thought on it and pressed thumbs…

---

<div class="post-metadata">

**Author:** ![Regina](https://avatars.discourse-cdn.com/v4/letter/r/d78d45/32.png) [@Regina](https://forum.collaboraonline.com/u/Regina)\
**Post date:** [April 17, 2026, 11:12am UTC](https://forum.collaboraonline.com/t/testing-and-bug-fixing-for-collabora-desktop/4603/8 "2026-04-17T11:12:44Z")

</div>

> [@vmiklos](#):
>
> See [Build Collabora Office for Windows | Collabora Online - Community Page](https://collaboraonline.github.io/post/build-co-windows/)

The build instructions contain the remark, “Note that you will not end up with a runnable normal desktop Collabora Office.” What will I need to do to run the office?

---

<div class="post-metadata">

**Author:** ![mst](https://avatars.discourse-cdn.com/v4/letter/m/e0b2c6/32.png) [@mst](https://forum.collaboraonline.com/u/mst)\
**Post date:** [April 17, 2026, 3:12pm UTC](https://forum.collaboraonline.com/t/testing-and-bug-fixing-for-collabora-desktop/4603/9 "2026-04-17T15:12:05Z")

</div>

This is slightly confusing. So originally there was a Collabora Office that was basically rebranded LO, and that is what this “runnable normal desktop Collabora Office” refers to. Now there is the new Collabora Office based on the same browser-UI as Online - and the previous product was renamed to Collabora Office Classic.

The build instructions need to be fixed to be less confusing.

To build Office, just continue with the instructions, zstd/poco, online…

To build Classic, don’t use `--with-distro=CODAWindows` … but at the moment it’s a bit unclear how much of a future that has on the `main` branch.

---

<div class="post-metadata">

**Author:** ![tml1024](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.collaboraonline.com/tml1024/32/438_2.png) [@tml1024](https://forum.collaboraonline.com/u/tml1024)\
**Post date:** [April 20, 2026, 8:26am UTC](https://forum.collaboraonline.com/t/testing-and-bug-fixing-for-collabora-desktop/4603/10 "2026-04-20T08:26:16Z")

</div>

(The instructions have been updated now.)
