Bug 115534 (LibreOffice-Flatpak) - [META] LibreOffice Flatpak package bugs
Summary: [META] LibreOffice Flatpak package bugs
Status: NEW
Alias: LibreOffice-Flatpak
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on: 111436 155553 164232 171406 105037 106364 106760 112150 113061 113114 114474 114889 115127 125721 125870 131623 150632 150902 156387 163328
Blocks: Installer
  Show dependency treegraph
 
Reported: 2018-02-07 23:51 UTC by Yousuf Philips (jay) (retired)
Modified: 2026-04-25 17:35 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Yousuf Philips (jay) (retired) 2018-02-07 23:51:27 UTC
Bugs only found in the flatpak edition of LibreOffice.

http://www.libreoffice.org/download/flatpak/

All bugs will be set to NOTOURBUG/RESOLVED-MOVED if it only occurs in the sandboxed Flatpak package and doesnt happen in a regular TDF build.

Please report these bugs to LibreOffice flatpak issue tracker
https://github.com/flathub/org.libreoffice.LibreOffice/issues
Comment 1 Lazuli 2026-04-25 17:35:25 UTC
(In reply to Yousuf Philips (jay) (retired) from comment #0)
> Bugs only found in the flatpak edition of LibreOffice.
> 
> http://www.libreoffice.org/download/flatpak/
> 
> All bugs will be set to NOTOURBUG/RESOLVED-MOVED if it only occurs in the
> sandboxed Flatpak package and doesnt happen in a regular TDF build.
> 
> Please report these bugs to LibreOffice flatpak issue tracker
> https://github.com/flathub/org.libreoffice.LibreOffice/issues

Hi Mr. Philips. I'm the original reporter from related bug #171406.

In my case, I'm unable to report to the Flatpak issue tracker because for uninown reasons for me my IP and accounts have been permanently blocked. I don't know the reasons and they do not explain

I assume other people reporting in my bug report are experiencing the same.

I really hope this issue could somehow be resolved. It has been dragged along one more iteration of the software by now.

Thank you!