I'll use this issue for the Office 365 porting project, please comment with clear comments and keep off topic discussions out of this.
Rules
- If your issue is already reported, just react to it, do not reply to it and do not re-post it, comment it only if you have more details to provide
- Do not ping/up an issue, just wait please
- If you want to reply a comment, only quote the relevant part, no big logs, no big texts, thanks
- Hide large texts like logs to a spoiler
- I can hide comments if they are just duplicated or merge them if needed
- Avoid comments like “does not work” provide details like logs.
Disclaimer
This is not a modified version of Office 365, it works using the original installer that offers a trial but needs to be activated with a Office 365 license, DO NOT ASK in this issue, how to pirate it, you'll get an instant-ban.
Current test build: soda-11.0-21-experimental.
This must be considered as unstable software, this issue and the installers exists exactly for helping me testing the software. Please be sure to read the Known Issues section before reporting anything.
No installers are built-in, the Bottles' installer uses the office-runtime dependency to download the setup.exe file and it downloads Office via Click-to-Run.
Known Issues
Please read here before reporting anything, do not report something already reported.
Common
- The cpak build can open an extra empty XWayland window. This is being worked on.
- Personal Microsoft account sign-in can still show a blank authentication window.
- The UI looks the old one pre-365, this is because it might actually be an old build. The new one has white splash screens, if yiu see the wrong one it is because during the install process, it picked up the wrong build. No issues, just open one of the Office apps, go to your account, enable updates and update it, then restart.
Word
- some selectors does not show their borders
- some fonts in the fonts selector does not get rendered correctly
Excel
- sometimes, clicking a cell drops you to the wrong one, I should have fixed it but it was a always-coming-back issue so I prefer to keep it in this list for now
- some features might cause a crash, I am still identifying which of them I did not have fixed yet
Access (NOT TESTED YET)
- nothing yet, need more testing
Teams (NOT TESTED YET)
- nothing yet, need more testing
Publisher (NOT TESTED YET)
- nothing yet, need more testing
OneNote
- the note canvas renders on top of other widgets
PowePoint
- nothing yet, need more testing
Tasks
- the page canvas renders on top of the navigation menu
Outlook Classic
- the canvas that renders the e-mail, appears on top of the window and other controls
- the controls in the e-mail canvas, appears in low quality
- search bar shows some glitches and missing borders once activated
- search results appears behind other widgets
Outlook Modern (web)
- many rendering issues
- the window is trimmed
- pages loads very slow
How to test
- Install latest Bottles using cpak (see the Bottles section); you can use latest flatpak build form artifacts but I am only testing with cpak for the moment, might produce different results; then run it (I suggest running it from terminal to catch more logs)
- Enable the
Pre-Release option in the Bottles' Main Settings
- Install
soda-11.0-21-experimental from the Runners tab
- Create a new Software's bottle using the Soda runner you just installed
- Open your bottle and go to
Programs, then check for Microsoft and install the version of Office you need
- Finish it (or collect logs if it crash) and launch it from the Programs list of your bottle, then collect as much logs as possible
- Report any bug here as a comment, put huge logs into a .log/txt file, do not drop them as plain text, then explain as much concise and clear as possible the issue you had and always provide the e way you installed Bottles.
Bottles
Ensure you have cpak v2.13.3 or greater.
Use
cpak install -b main github.com/bottlesdevs/bottles
If you still want to try the Flatpak, you can by using the latest bundle from the Github Actions but be aware I will still test on cpak only for the whole first stage of development.
Runners
Installers
Dependencies
FAQ
Why cpak and not ?
Because I use and control it and since I need control over the whole pipeline (and also needs to feel at ease on my own), I opted for it.
Will it be distributed to Flathub too?
Yes, once ready.
Do I need a specific Bottles version?
Yes, as I said we need a specific version, especially the one starting from commit 5cbb5be22795fc877cab063dc2e7066618f8a5d4 because that provides the changes needed for the Office installer. This is not just a Wine patch, it's a bunch of patches, a ne dependency, a new installer and a Bottles' update.
Can I still test using AUR/Flatpak?
Ofc, if you want, but the cpak environment is the one I am using to ensure everything works correctly, it contains every extra dependency I found (and will found) during my work.
Can I usedaily?
I suggest to not. Not yet. Wait.
I'll use this issue for the Office 365 porting project, please comment with clear comments and keep off topic discussions out of this.
Rules
Disclaimer
This is not a modified version of Office 365, it works using the original installer that offers a trial but needs to be activated with a Office 365 license, DO NOT ASK in this issue, how to pirate it, you'll get an instant-ban.
Current test build:
soda-11.0-21-experimental.This must be considered as unstable software, this issue and the installers exists exactly for helping me testing the software. Please be sure to read the Known Issues section before reporting anything.
No installers are built-in, the Bottles' installer uses the
office-runtimedependency to download thesetup.exefile and it downloads Office via Click-to-Run.Known Issues
Please read here before reporting anything, do not report something already reported.
Common
Word
Excel
Access (NOT TESTED YET)
Teams (NOT TESTED YET)
Publisher (NOT TESTED YET)
OneNote
PowePoint
Tasks
Outlook Classic
Outlook Modern (web)
How to test
Pre-Releaseoption in the Bottles' Main Settingssoda-11.0-21-experimentalfrom theRunnerstabPrograms, then check forMicrosoftand install the version of Office you needBottles
Ensure you have cpak v2.13.3 or greater.
Use
If you still want to try the Flatpak, you can by using the latest bundle from the Github Actions but be aware I will still test on cpak only for the whole first stage of development.
Runners
Installers
Dependencies
FAQ
Why cpak and not ?
Because I use and control it and since I need control over the whole pipeline (and also needs to feel at ease on my own), I opted for it.
Will it be distributed to Flathub too?
Yes, once ready.
Do I need a specific Bottles version?
Yes, as I said we need a specific version, especially the one starting from commit
5cbb5be22795fc877cab063dc2e7066618f8a5d4because that provides the changes needed for the Office installer. This is not just a Wine patch, it's a bunch of patches, a ne dependency, a new installer and a Bottles' update.Can I still test using AUR/Flatpak?
Ofc, if you want, but the cpak environment is the one I am using to ensure everything works correctly, it contains every extra dependency I found (and will found) during my work.
Can I usedaily?
I suggest to not. Not yet. Wait.