[Mashimo]

I work in software development for Danish hospitals, and some regions already used OpenOffice, now libre office, for .. well over 15 years. At least in parts.

We integrate with an API into libreoffice, and it more or less did not change in well over a decade. But sometimes libreoffice crashes and you can't figure out why. There are just no logs. It feels like a black box at times.

But I don't think they will be switching away from Teams as quickly. Will be interesting for sure.

Slightly off topic, but does anyone know why libreoffice stopped publishing artefacts to mvn repo? https://mvnrepository.com/artifact/org.libreoffice/libreoffi...

[buovjaga]

LibreOffice release builds should offer to send a crash report. Ideally, you should then create a bug report referencing the crash report. Besides that, you can do your own build with debug symbols and get backtraces or debug the program.

At The Document Foundation we are always interested in helping deployments. It is also nice to do writeups for our blog. Let me know, if your organisation needs help: [e-mail]

I recommend to consider our certification program: https://www.documentfoundation.org/certification-program/

I asked about the Maven artifacts and our release engineer will update them later this week.

[rbanffy]

> you should then create a bug report referencing the crash report

Reducing friction would be nice here - I don't remember encountering the crash log screen, but if you could file a bug report right from that screen, that'd be perfect. A lot of information can be pre-collected at that stage - precise version, build, OS, architecture, processor type, etc. All that'd be left is the "What I was trying to do", my e-mail, and a checkbox if I agree with the privacy policies and if I want to receive e-mail updates about this bug report.

> you can do your own build with debug symbols

It'd be great if the Document Foundation helped distros to offer libreoffice-*-debug packages for this case - if it's crashing for you, install the debug version and your crash logs will be a lot easier to read.

[trinsic2]

Why does libreoffice have such an annoying document recovery mechanism that I can't turn off or modify? It takes like three clicks to cancel that process every time I open a new doc

[deanc]

I think if we're to move to away from these US products to open source ones, then governments should also provide resources or funding to develop them using the licensing fees they save. Is the Danish government contributing back to libreoffice?

[hermanzegerman]

The German State of Schleswig Holstein does

https://euro-stack.com/blog/2025/3/schleswig-holstein-open-s...

[toomuchtodo]

Indeed, take what you're paying US Big Tech and direct it to domestic EU enterprises, corporate or non profit.

[trinsic2]

Agreed. There should be some structure setup for open source projects to request contribution fees. Having stuff like this in plain sight might help orgs play nice.

[staticlibs]

> sometimes libreoffice crashes and you can't figure out why > why libreoffice stopped publishing artefacts to mvn repo

I think both questions would be a perfect fit for the paid support bugtracker of LibreOffice maintainers. Hopefully paid by some hospital funds that are not spent on MS Office licenses.

[andix]

Switching from Word/Excel to LibreOffice is comparably easy. A lot of other Microsoft Products are much harder to get rid of.

I've never seen a European corporation that doesn't do user management with ActiveDirectory. Some still have it on their own Windows servers, but most browser based applications still go through Entra (Azure Cloud based AD). Just shut off their Entra/AAD and most of their software is blocked because nobody can log in.

[close04]

This is the elephant in the room that most comments on this page miss. Office may be hard to replace, Teams maybe even harder, but the real pain comes when you touch identity and access management. The usual initial optimism that "yeah but [insert solution name here] does this, problem solved" dissolves very fast as you start going through the inventory of requirements for managing users, devices, authentication, etc.

It's not just the technical hurdle which maybe you'll whip your admins into finding workarounds (-keep praying that your admins don't leave because it will be painful to find replacements who understand and can maintain the spaghetti pasta monster your infra ended up being-). In overall non-technical organizations the user experience always ends up hobbled even just by asking people to keep track of multiple identities.

MS is still entrenched because they give a turnkey solution with Eeeeeverything™ and your CTO doesn't need to struggle with any uncertainty. SaaS made it so easy to just "outsource" everything to MS, they'll be responsible and accountable for operations, infra, security, processes, etc. Even less headache for your C-level people. See no evil, hear no evil, you pay MS to take the shit and your job is safe. If you throw a stone out the window you'll hit someone with general "MS administration" skills. And users are usually familiar with MS tools, Windows, Office, so they aren't bothered (you hear a lot of complaints about Teams on HN but not so much from normal users). So this covers the tech, the skills, and the UX.

[dijit]

Agreed, and even things like Keycloak/FreeIPA are only partial solutions.

FreeIPA in particular is a beast to maintain, it puts kubernetes-cowboys to shame.

[flopsamjetsam]

> But I don't think they will be switching away from Teams as quickly.

I'm interested to know why Teams is so sticky for the team. Are there not good replacements available? I've used it a little, but am by no means a power user.

[close04]

On top of what sibling comment says, Teams benefits from other network effects. If all your partners use Teams and the federation is a enabled, next time you consider a replacement that can do all of this, the bar will be that much higher to find a suitable alternative.

If an inter-operable protocols were enforced by some regulation it would alleviate the situation a bit.

[trinsic2]

It's buggy as hell. That's one thing. But they rolled teams out with office anti-competitively to lock orgs in and on that premise it should be abandoned. Market saturation by a company that is contributing to an authoritarian government by way of anti-competition needs to be black listed everywhere.

[wiredpancake]

Because 'Teams' isn't just a simple meeting application. It's very feature rich. If you ever have to deal with the admin.teams.microsoft portal you'll know how many options and toggles it has.

Alongside this many businesses deploy 'Teams Supported' or 'Teams Enabled' devices into meeting and conference rooms. Yealink is a popular brand, they don't have baked in support for LibreMeet or whatever meeting products exist.

[PeterStuer]

Could you expand on the Teams remark? What exactly is the lock=in?

[trinsic2]

Did you try running Libra office from command line to see the console output?