[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-10-17 Thread Mathew Hodson
** No longer affects: openjdk-lts (Ubuntu Disco) ** No longer affects: openjdk-lts (Ubuntu) ** Tags removed: verification-needed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu.

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-07-03 Thread Launchpad Bug Tracker
This bug was fixed in the package libreoffice-l10n - 1:6.0.7-0ubuntu0.18.04.7 --- libreoffice-l10n (1:6.0.7-0ubuntu0.18.04.7) bionic; urgency=medium * debian/patches/cpdmgr-check-dbus-desc.diff (LP: #1798074): - Only create CPDManager if D-Bus descriptions present. - Fixes

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-06-26 Thread Marcus Tomlinson
Upgraded libreoffice-l10n from 1:6.0.7-0ubuntu0.18.04.6 to 1:6.0.7-0ubuntu0.18.04.7 from bionic-proposed in a clean and up-to-date bionic amd64 VM, and verified that the test case passes. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-06-25 Thread Marcus Tomlinson
** Changed in: libreoffice-l10n (Ubuntu Bionic) Importance: Undecided => High ** Changed in: libreoffice-l10n (Ubuntu Bionic) Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson) -- You received this bug notification because you are a member of Desktop Packages, which is

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-06-25 Thread Steve Langasek
Hello Olivier, or anyone else affected, Accepted libreoffice-l10n into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /libreoffice-l10n/1:6.0.7-0ubuntu0.18.04.7 in a few hours, and then in the -proposed repository. Please help us by testing

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-06-19 Thread Bug Watch Updater
** Changed in: libreoffice (Debian) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1822839 Title: LibreOffice doesn't detect JVM because of

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-05-30 Thread Launchpad Bug Tracker
This bug was fixed in the package libreoffice - 1:5.1.6~rc2-0ubuntu1~xenial7 --- libreoffice (1:5.1.6~rc2-0ubuntu1~xenial7) xenial; urgency=medium [ Ikuya Awashiro ] * debian/patches/new-japanese-era-name.patch (LP: #1827451): Add new Japanse era name "Reiwa" support which

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-05-30 Thread Launchpad Bug Tracker
This bug was fixed in the package libreoffice - 1:6.0.7-0ubuntu0.18.04.6 --- libreoffice (1:6.0.7-0ubuntu0.18.04.6) bionic; urgency=medium [ Ikuya Awashiro ] * debian/patches/new-japanese-era-name.patch (LP: #1827451): Add new Japanse era name "Reiwa" support which taken from

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-05-24 Thread Marcus Tomlinson
Upgraded libreoffice from 1:6.0.7-0ubuntu0.18.04.5 to 1:6.0.7-0ubuntu0.18.04.6 from bionic-proposed in a clean and up-to-date bionic amd64 VM, and verified that the [Test Case] now passes. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-05-24 Thread Marcus Tomlinson
Upgraded libreoffice from 1:5.1.6~rc2-0ubuntu1~xenial6 to 1:5.1.6~rc2-0ubuntu1~xenial7 from xenial-proposed in a clean and up-to- date xenial amd64 VM, and verified that the [Test Case] now passes. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-05-23 Thread Łukasz Zemczak
Hello Olivier, or anyone else affected, Accepted libreoffice into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libreoffice/1:5.1.6~rc2-0ubuntu1~xenial7 in a few hours, and then in the -proposed repository. Please help us by testing this new

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-05-23 Thread Łukasz Zemczak
Hello Olivier, or anyone else affected, Accepted libreoffice into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libreoffice/1:6.0.7-0ubuntu0.18.04.6 in a few hours, and then in the -proposed repository. Please help us by testing this new

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-05-16 Thread Launchpad Bug Tracker
This bug was fixed in the package libreoffice - 1:6.2.3-0ubuntu0.19.04.1 --- libreoffice (1:6.2.3-0ubuntu0.19.04.1) disco; urgency=medium [ Olivier Tilloy ] * debian/patches/java.vendor-Ubuntu.patch: update to also recognize "Private Build" as java.vendor (for custom PPA

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-05-16 Thread Launchpad Bug Tracker
This bug was fixed in the package libreoffice-l10n - 1:6.2.3-0ubuntu0.19.04.1 --- libreoffice-l10n (1:6.2.3-0ubuntu0.19.04.1) disco; urgency=medium [ Olivier Tilloy ] * debian/patches/java.vendor-Ubuntu.patch: update to also recognize "Private Build" as java.vendor (for

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-05-10 Thread Marcus Tomlinson
Upgraded libreoffice to 1:6.2.3-0ubuntu0.19.04.1 from disco-proposed in a clean and up-to-date disco amd64 VM, and successfully ran test plan at https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice. ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-05-09 Thread Marcus Tomlinson
** Changed in: libreoffice-l10n (Ubuntu Disco) Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson) ** Changed in: libreoffice-l10n (Ubuntu Disco) Importance: Undecided => High ** Changed in: libreoffice-l10n (Ubuntu) Status: New => Fix Released ** Changed in:

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-05-09 Thread Łukasz Zemczak
Hello Olivier, or anyone else affected, Accepted libreoffice into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libreoffice/1:6.2.3-0ubuntu0.19.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-05-09 Thread Marcus Tomlinson
** Description changed: [Impact]  * A recent OpenJDK update changes the value of the "java.vendor" property from "Oracle Corporation" to "Private Build". This breaks the code in LibreOffice that detects an installed JVM.  * The fix is currently in LibreOffice 6.2.3 on eoan.

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-05-08 Thread Olivier Tilloy
** Changed in: libreoffice (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: libreoffice (Ubuntu Xenial) Status: Triaged => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu.

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-05-07 Thread Marcus Tomlinson
** Changed in: libreoffice (Ubuntu Bionic) Importance: Undecided => High ** Changed in: libreoffice (Ubuntu Disco) Importance: Undecided => High ** Changed in: libreoffice (Ubuntu Xenial) Importance: Undecided => High -- You received this bug notification because you are a member of

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-05-07 Thread Marcus Tomlinson
** Description changed: - libreoffice autopkgtests are failing on disco with openjdk - 11.0.3+4-2ubuntu1. + [Impact] - The likely culprit is that change: + * A recent OpenJDK update changes the value of the "java.vendor" + property from "Oracle Corporation" to "Private Build". This breaks the

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-05-06 Thread Marcus Tomlinson
** Changed in: libreoffice (Ubuntu Disco) Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1822839 Title:

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-05-06 Thread Łukasz Zemczak
Can we get an SRU template for this bug? At least a viable test-case could be enough, with bonus points for everything else. ** Also affects: libreoffice (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: openjdk-lts (Ubuntu Disco) Importance: Undecided Status:

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-05-03 Thread Marcus Tomlinson
** Also affects: libreoffice (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: openjdk-lts (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: libreoffice (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: openjdk-lts

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-04-09 Thread Bug Watch Updater
** Changed in: df-libreoffice Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1822839 Title: LibreOffice doesn't detect JVM because of

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-04-04 Thread Launchpad Bug Tracker
This bug was fixed in the package libreoffice - 1:6.2.2-0ubuntu2 --- libreoffice (1:6.2.2-0ubuntu2) disco; urgency=medium [ Rene Engelhard ] * debian/patches/java.vendor-Debian.diff: make jvmfwk recognize "Debian" as java.vendor as that's what is set in openjdk 11 >=

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-04-04 Thread Olivier Tilloy
** Changed in: libreoffice (Ubuntu) Status: Triaged => In Progress ** Changed in: libreoffice (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu.

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-04-04 Thread Adolfo Jayme
** Changed in: libreoffice (Ubuntu) Status: New => Triaged ** Changed in: libreoffice (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu.

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-04-03 Thread Bug Watch Updater
** Changed in: df-libreoffice Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1822839 Title: LibreOffice doesn't detect JVM because of unexpected

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-04-03 Thread Bug Watch Updater
** Changed in: libreoffice (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1822839 Title: LibreOffice doesn't detect JVM because of

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-04-03 Thread Olivier Tilloy
** Bug watch added: Debian Bug tracker #926009 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926009 ** Also affects: libreoffice (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926009 Importance: Unknown Status: Unknown -- You received this bug notification

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-04-02 Thread Bug Watch Updater
Launchpad has imported 1 comments from the remote bug at https://bugs.documentfoundation.org/show_bug.cgi?id=124503. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at

[Desktop-packages] [Bug 1822839] Re: LibreOffice doesn't detect JVM because of unexpected java.vendor property value

2019-04-02 Thread Olivier Tilloy
** Bug watch added: Document Foundation Bugzilla #124503 https://bugs.documentfoundation.org/show_bug.cgi?id=124503 ** Also affects: df-libreoffice via https://bugs.documentfoundation.org/show_bug.cgi?id=124503 Importance: Unknown Status: Unknown -- You received this bug