[Desktop-packages] [Bug 1226962] Re: Keyboard shortcuts (hotkeys) not functional in some cases in non-latin keyboard layouts
** No longer affects: openjdk-7 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1226962 Title: Keyboard shortcuts (hotkeys) not functional in some cases in non-latin keyboard layouts Status in aptana-studio-installer: New Status in Default settings and artwork for Baltix OS: New Status in LibreOffice: Fix Released Status in ibus: New Status in Indicator keyboard: Fix Released Status in Inkscape: Fix Released Status in Intellij Idea: New Status in monodevelop: New Status in Mutter: Fix Released Status in okular: New Status in OpenOffice: New Status in sigram: New Status in Unity: Fix Released Status in Visual Studio Code: New Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-terminal package in Ubuntu: Triaged Status in kdevelop package in Ubuntu: Confirmed Status in mc package in Ubuntu: Confirmed Status in terminator package in Ubuntu: Confirmed Status in unity package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: In Progress Status in gnome-settings-daemon source package in Xenial: Triaged Status in gnome-terminal source package in Xenial: Triaged Status in kdevelop source package in Xenial: Confirmed Status in mc source package in Xenial: Confirmed Status in terminator source package in Xenial: Confirmed Status in unity source package in Xenial: Fix Released Status in unity-settings-daemon source package in Xenial: In Progress Status in gnome-shell package in Fedora: Won't Fix Status in openoffice package in Fedora: Won't Fix Bug description: Keyboard shortcuts are key combinations like Alt+F (usually opens the File menu) and Ctrl+O (usually opens the File→Open... dialog box). There is an issue with non-latin keyboard layouts that the keys under F or O (for Alt+F and Ctrl+O respectively) would correspond to some other character. What should happen then? There is some smart functionality (at least in the GTK+ library) that when we press a shortcut, it will try to make Alt+F or Ctrl+O work, even if the active keyboard layout is not English. For this smart functionality to work, it requires us to have as first keyboard layout the English (en) layout. Then, GTK+ will be able to check whether the shortcut makes sense for English, and if so, will run it. All that even if the active layout is Greek or Russian or something else. This report has over 300 comments and these comments include all sort of corner cases that indeed shortcuts do not work. In general, shortcuts work, but in specific cases there are issues that need to be fixed. What we need to do, is collect those corner cases and create new separate reports. Here are the corner cases: 1. In Dash (in Unity 7), shortcuts like Super+S/W work (for example, Greek, Russian), but they do not work for Super+A/F/M/C/V. Report: 2. Java GUI applications on Linux do not support shortcuts in non-latin languages. This is an issue with Java and should be reported there. Java GUI apps are not included in any of the Ubuntu ISOs. Report: 3. Shortcuts that use Ctrl on LibreOffice work for several languages (like Greek, Russian), but has been reported not to work on Hebrew. This should be a separate bug report specific to Hebrew and other languages affected in the same way. Report: To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1226962] Re: Keyboard shortcuts (hotkeys) not functional in some cases in non-latin keyboard layouts
** No longer affects: openjdk-7 (Ubuntu Xenial) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1226962 Title: Keyboard shortcuts (hotkeys) not functional in some cases in non-latin keyboard layouts Status in aptana-studio-installer: New Status in Default settings and artwork for Baltix OS: New Status in LibreOffice: Fix Released Status in ibus: New Status in Indicator keyboard: Fix Released Status in Inkscape: Fix Released Status in Intellij Idea: New Status in monodevelop: New Status in Mutter: Fix Released Status in okular: New Status in OpenOffice: New Status in sigram: New Status in Unity: Fix Released Status in Visual Studio Code: New Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-terminal package in Ubuntu: Triaged Status in kdevelop package in Ubuntu: Confirmed Status in mc package in Ubuntu: Confirmed Status in openjdk-7 package in Ubuntu: Incomplete Status in terminator package in Ubuntu: Confirmed Status in unity package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: In Progress Status in gnome-settings-daemon source package in Xenial: Triaged Status in gnome-terminal source package in Xenial: Triaged Status in kdevelop source package in Xenial: Confirmed Status in mc source package in Xenial: Confirmed Status in terminator source package in Xenial: Confirmed Status in unity source package in Xenial: Fix Released Status in unity-settings-daemon source package in Xenial: In Progress Status in gnome-shell package in Fedora: Won't Fix Status in openoffice package in Fedora: Won't Fix Bug description: Keyboard shortcuts are key combinations like Alt+F (usually opens the File menu) and Ctrl+O (usually opens the File→Open... dialog box). There is an issue with non-latin keyboard layouts that the keys under F or O (for Alt+F and Ctrl+O respectively) would correspond to some other character. What should happen then? There is some smart functionality (at least in the GTK+ library) that when we press a shortcut, it will try to make Alt+F or Ctrl+O work, even if the active keyboard layout is not English. For this smart functionality to work, it requires us to have as first keyboard layout the English (en) layout. Then, GTK+ will be able to check whether the shortcut makes sense for English, and if so, will run it. All that even if the active layout is Greek or Russian or something else. This report has over 300 comments and these comments include all sort of corner cases that indeed shortcuts do not work. In general, shortcuts work, but in specific cases there are issues that need to be fixed. What we need to do, is collect those corner cases and create new separate reports. Here are the corner cases: 1. In Dash (in Unity 7), shortcuts like Super+S/W work (for example, Greek, Russian), but they do not work for Super+A/F/M/C/V. Report: 2. Java GUI applications on Linux do not support shortcuts in non-latin languages. This is an issue with Java and should be reported there. Java GUI apps are not included in any of the Ubuntu ISOs. Report: 3. Shortcuts that use Ctrl on LibreOffice work for several languages (like Greek, Russian), but has been reported not to work on Hebrew. This should be a separate bug report specific to Hebrew and other languages affected in the same way. Report: To manage notifications about this bug go to: https://bugs.launchpad.net/aptana-studio-installer/+bug/1226962/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 4: * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 5: * groovy 2.4.16-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) [2019-02-22] Packages in stage 3 that are waiting for security team review. Copy only after OK is received. PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage3 Please copy them in the following order/grouping. Group 1: * java-common 0.68ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-21) * javatools 0.72.1~18.04.1 Tiago Stürmer Daitx (2019-02-20) * openjdk-lts 11.0.2+9-3ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-07) Group 2: * gettext 0.19.8.1-6ubuntu0.2 Matthias Klose (18 hours ago) * insubstantial 7.3+dfsg3-4~18.04.1 Tiago Stürmer Daitx (2019-02-20) * jython 2.7.1+repack-5~18.04 Matthias Klose (2019-02-20) * libgpars-groovy-java 1.2.1-10~18.04.1 Tiago Stürmer Daitx (2019-02-20) * logback 1:1.2.3-2ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-20) * maven-javadoc-plugin 3.0.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-20) * openjdk-11-jre-dcevm 11.0.1+7-1ubuntu0.1 Matthias Klose (2019-02-19) * openjfx 11.0.2+1-1~18.04.1 Matthias Klose (2019-02-19) * saaj 1.4.0-3~18.04.1 Tiago Stürmer Daitx (2019-02-20) * scala 2.11.12-4~18.04 Matthias Klose (2019-02-20) Packages from stage 4 and later are not yet reviewed and should not be uploaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/activemq/+bug/1814133/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814133]
: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 4: * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 5: * groovy 2.4.16-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) [2019-02-22] Packages in stage 3 that are waiting for security team review. Copy only after OK is received. PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage3 Please copy them in the following order/grouping. Group 1: * java-common 0.68ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-21) * javatools 0.72.1~18.04.1 Tiago Stürmer Daitx (2019-02-20) * openjdk-lts 11.0.2+9-3ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-07) Group 2: * gettext 0.19.8.1-6ubuntu0.2 Matthias Klose (18 hours ago) * insubstantial 7.3+dfsg3-4~18.04.1 Tiago Stürmer Daitx (2019-02-20) * jython 2.7.1+repack-5~18.04 Matthias Klose (2019-02-20) * libgpars-groovy-java 1.2.1-10~18.04.1 Tiago Stürmer Daitx (2019-02-20) * logback 1:1.2.3-2ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-20) * maven-javadoc-plugin 3.0.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-20) * openjdk-11-jre-dcevm 11.0.1+7-1ubuntu0.1 Matthias Klose (2019-02-19) * openjfx 11.0.2+1-1~18.04.1 Matthias Klose (2019-02-19) * saaj 1.4.0-3~18.04.1 Tiago Stürmer Daitx (2019-02-20) * scala 2.11.12-4~18.04 Matthias Klose (2019-02-20) Packages from stage 4 and later are not yet reviewed and should not be uploaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/activemq/+bug/1814133/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
** Also affects: jabref (Ubuntu) Importance: Undecided Status: New ** Also affects: octave (Ubuntu) Importance: Undecided Status: New ** Also affects: pdfsam (Ubuntu) Importance: Undecided Status: New ** Also affects: scilab (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in groovy package in Ubuntu: New Status in insubstantial package in Ubuntu: New Status in jabref package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in java-common package in Ubuntu: New Status in javatools package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libgpars-groovy-java package in Ubuntu: New Status in libhibernate-validator-java package in Ubuntu: New Status in logback package in Ubuntu: New Status in maven-bundle-plugin package in Ubuntu: New Status in maven-enforcer package in Ubuntu: New Status in maven-javadoc-plugin package in Ubuntu: New Status in maven-jaxb2-plugin package in Ubuntu: New Status in maven-plugin-tools package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in octave package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in pdfsam package in Ubuntu: New Status in saaj package in Ubuntu: New Status in scala package in Ubuntu: New Status in scilab package in Ubuntu: New Status in clojure1.8 source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in groovy source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-compiler-plugin source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in surefire source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2019-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019
[Desktop-packages] [Bug 1814133]
affects Ubuntu/jabref affects Ubuntu/scilab affects Ubuntu/scilab affects Ubuntu/pdfsam -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in groovy package in Ubuntu: New Status in insubstantial package in Ubuntu: New Status in jabref package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in java-common package in Ubuntu: New Status in javatools package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libgpars-groovy-java package in Ubuntu: New Status in libhibernate-validator-java package in Ubuntu: New Status in logback package in Ubuntu: New Status in maven-bundle-plugin package in Ubuntu: New Status in maven-enforcer package in Ubuntu: New Status in maven-javadoc-plugin package in Ubuntu: New Status in maven-jaxb2-plugin package in Ubuntu: New Status in maven-plugin-tools package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in octave package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in pdfsam package in Ubuntu: New Status in saaj package in Ubuntu: New Status in scala package in Ubuntu: New Status in scilab package in Ubuntu: New Status in clojure1.8 source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in groovy source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-compiler-plugin source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in surefire source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2019-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 4: * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 5: * groovy 2.4.16-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) [2019-02-22] Packages in stage 3
Re: [Desktop-packages] [Openjdk] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
> > Just a question, is this update going to affect these packages: > > jabref > > scilab > > octave > > pdfsam > > ? > > > > Also, I hope this update brings 18.04 LTS closer to Debian 10 regarding > > OpenJdk-11 and its dependant packages to facilitate the maintenance > > burden. > > Yes, we are planning to update java apps that are affected by this transition. To be more specific, any package that fails to run correctly with openjdk-11 will be investigated and is a candidate for a update. The update does not necessarily imply we will use the latest version: we might simply apply or backport changes that allow them to work under openjdk-11. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in groovy package in Ubuntu: New Status in insubstantial package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in java-common package in Ubuntu: New Status in javatools package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libgpars-groovy-java package in Ubuntu: New Status in libhibernate-validator-java package in Ubuntu: New Status in logback package in Ubuntu: New Status in maven-bundle-plugin package in Ubuntu: New Status in maven-enforcer package in Ubuntu: New Status in maven-javadoc-plugin package in Ubuntu: New Status in maven-jaxb2-plugin package in Ubuntu: New Status in maven-plugin-tools package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in saaj package in Ubuntu: New Status in scala package in Ubuntu: New Status in clojure1.8 source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in groovy source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-compiler-plugin source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in surefire source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2019-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle 4.4.1-3~18.04.1 Tia
Re: [Desktop-packages] [Openjdk] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
> Just a question, is this update going to affect these packages: > jabref > scilab > octave > pdfsam > ? > > Also, I hope this update brings 18.04 LTS closer to Debian 10 regarding > OpenJdk-11 and its dependant packages to facilitate the maintenance > burden. Yes, we are planning to update java apps that are affected by this transition. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in groovy package in Ubuntu: New Status in insubstantial package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in java-common package in Ubuntu: New Status in javatools package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libgpars-groovy-java package in Ubuntu: New Status in libhibernate-validator-java package in Ubuntu: New Status in logback package in Ubuntu: New Status in maven-bundle-plugin package in Ubuntu: New Status in maven-enforcer package in Ubuntu: New Status in maven-javadoc-plugin package in Ubuntu: New Status in maven-jaxb2-plugin package in Ubuntu: New Status in maven-plugin-tools package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in saaj package in Ubuntu: New Status in scala package in Ubuntu: New Status in clojure1.8 source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in groovy source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-compiler-plugin source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in surefire source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2019-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 4: * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 5: *
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
** Also affects: libhibernate-validator-java (Ubuntu) Importance: Undecided Status: New ** Also affects: jasperreports (Ubuntu) Importance: Undecided Status: New ** Also affects: maven-bundle-plugin (Ubuntu) Importance: Undecided Status: New ** Also affects: maven-enforcer (Ubuntu) Importance: Undecided Status: New ** Also affects: maven-jaxb2-plugin (Ubuntu) Importance: Undecided Status: New ** Also affects: maven-plugin-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in groovy package in Ubuntu: New Status in insubstantial package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in java-common package in Ubuntu: New Status in javatools package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libgpars-groovy-java package in Ubuntu: New Status in libhibernate-validator-java package in Ubuntu: New Status in logback package in Ubuntu: New Status in maven-bundle-plugin package in Ubuntu: New Status in maven-enforcer package in Ubuntu: New Status in maven-javadoc-plugin package in Ubuntu: New Status in maven-jaxb2-plugin package in Ubuntu: New Status in maven-plugin-tools package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in saaj package in Ubuntu: New Status in scala package in Ubuntu: New Status in clojure1.8 source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in groovy source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-compiler-plugin source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in surefire source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2019-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
** Also affects: logback (Ubuntu) Importance: Undecided Status: New ** Also affects: maven-javadoc-plugin (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in groovy package in Ubuntu: New Status in insubstantial package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in java-common package in Ubuntu: New Status in javatools package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libgpars-groovy-java package in Ubuntu: New Status in libhibernate-validator-java package in Ubuntu: New Status in logback package in Ubuntu: New Status in maven-javadoc-plugin package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in saaj package in Ubuntu: New Status in scala package in Ubuntu: New Status in clojure1.8 source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in groovy source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-compiler-plugin source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in surefire source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2019-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 4: * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 5: * groovy 2.4.16-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) [2019-02-22] Packages in stage 3 that are waiting for security team review. Copy only after OK is received. PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage3 Please copy them in the following order/grouping. Group 1: * java-common 0.68ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-21) * javatools 0.72.1
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
** Description changed: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic- security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. - [2018-02-21] + [2019-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 4: * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 5: * groovy 2.4.16-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) - Packages from stage 3 and later are not yet reviewed and should not be + + [2019-02-22] + Packages in stage 3 that are waiting for security team review. Copy only after OK is received. + + PPAs: + https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage3 + + Please copy them in the following order/grouping. + Group 1: + * java-common 0.68ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-21) + * javatools 0.72.1~18.04.1 Tiago Stürmer Daitx (2019-02-20) + * openjdk-lts 11.0.2+9-3ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-07) + + Group 2: + * gettext 0.19.8.1-6ubuntu0.2 Matthias Klose (18 hours ago) + * insubstantial 7.3+dfsg3-4~18.04.1 Tiago Stürmer Daitx (2019-02-20) + * jython 2.7.1+repack-5~18.04 Matthias Klose (2019-02-20) + * libgpars-groovy-java 1.2.1-10~18.04.1 Tiago Stürmer Daitx (2019-02-20) + * logback 1:1.2.3-2ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-20) + * maven-javadoc-plugin 3.0.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-20) + * openjdk-11-jre-dcevm 11.0.1+7-1ubuntu0.1 Matthias Klose (2019-02-19) + * openjfx 11.0.2+1-1~18.04.1 Matthias Klose (2019-02-19) + * saaj 1.4.0-3~18.04.1 Tiago Stürmer Daitx (2019-02-20) + * scala 2.11.12-4~18.04 Matthias Klose (2019-02-20) + + Packages from stage 4 and later are not yet reviewed and should not be uploaded. ** Also affects: java-common (Ubuntu) Importance: Undecided Status: New ** Also affects: javatools (Ubuntu) Importance: Undecided Status: New ** Also affects: insubstantial (Ubuntu) Importance: Undecided Status: New ** No longer affects: saaj-ri (Ubuntu) ** Also affects: libgpars-groovy-java (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in groovy package in Ubuntu: New Status in insubstantial package in Ubuntu: New Status in java-common package in Ubuntu: New Status in javatools package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libgpars-groovy-java package in Ubuntu: New Status in metro-policy package in Ubuntu: New
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
** Description changed: Transition OpenJDK 11 to 18.04 LTS. - This transition is a security update of openjdk-lts and requires new dependencies as well as package backports and SRU fixes to go into the security pocket for a couple reasons: - - openjdk-lts 11 needs newer build dependencies - - various packages have runtime failures when run with openjdk-11 + This transition is a security update of openjdk-lts from openjdk-10 to + openjdk-11. This introduces runtime and FTBFS issues which requires + backports of multiple packages into the security pocket as well. - A few packages *must* be updated/patched before openjdk-11 itself is uploaded: - TBD + The packages are being build on PPAs under the + https://launchpad.net/~openjdk-11-transition team. The PPAs depend + solely on the security pocket and are separated in stages. + + The agreed process among foundations and the security team is that + packages in the PPAs will be binary copied into bionic-proposed, checked + for migration issues, and - no issues pending - copied into bionic- + security. + + A few packages might also need to be updated in Cosmic, but as an + exception that will be done after the Bionic transition is worked out. + + + [2018-02-21] + Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. + + Notes: + - jtreg and testng are new versions required as build dependencies of openjdk-11 + - all other packages are backports that must be build/bootstrapped with openjdk-10 + + PPAs: + https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 + https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 + + + Please copy them in the following order/grouping. + + Group 1: + * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) + + Group 2: + * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) + * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) + * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) + * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) + + Please upload libcommons-lang3-java from stage 2 (ignore the version in + stage 1). + + Group 3: + * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) + * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) + * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) + * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) + * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) + + Group 4: + * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) + + Group 5: + * groovy 2.4.16-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) + + + Packages from stage 3 and later are not yet reviewed and should not be uploaded. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in clojure1.8 package in Ubuntu: New Status in dd-plist package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in gradle-debian-helper package in Ubuntu: New Status in groovy package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jtreg package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libcommons-lang3-java package in Ubuntu: New Status in maven-compiler-plugin package in Ubuntu: New Status in maven-debian-helper package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in plexus-languages package in Ubuntu: New Status in saaj package in Ubuntu: New Status in saaj-ri package in Ubuntu: New Status in scala package in Ubuntu: New Status in surefire package in Ubuntu: New Status in testng package in Ubuntu: New Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. A few packages might also
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
** Description changed: - update to openjdk 11 in 18.04 LTS + Transition OpenJDK 11 to 18.04 LTS. + + This transition is a security update of openjdk-lts and requires new dependencies as well as package backports and SRU fixes to go into the security pocket for a couple reasons: + - openjdk-lts 11 needs newer build dependencies + - various packages have runtime failures when run with openjdk-11 + + A few packages *must* be updated/patched before openjdk-11 itself is uploaded: + TBD -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in clojure1.8 package in Ubuntu: New Status in dd-plist package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in gradle-debian-helper package in Ubuntu: New Status in groovy package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jtreg package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in libcommons-lang3-java package in Ubuntu: New Status in maven-compiler-plugin package in Ubuntu: New Status in maven-debian-helper package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in plexus-languages package in Ubuntu: New Status in saaj package in Ubuntu: New Status in saaj-ri package in Ubuntu: New Status in scala package in Ubuntu: New Status in surefire package in Ubuntu: New Status in testng package in Ubuntu: New Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts and requires new dependencies as well as package backports and SRU fixes to go into the security pocket for a couple reasons: - openjdk-lts 11 needs newer build dependencies - various packages have runtime failures when run with openjdk-11 A few packages *must* be updated/patched before openjdk-11 itself is uploaded: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1814133/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
** Also affects: jtreg (Ubuntu) Importance: Undecided Status: New ** Also affects: libcommons-lang3-java (Ubuntu) Importance: Undecided Status: New ** Also affects: testng (Ubuntu) Importance: Undecided Status: New ** Also affects: gradle (Ubuntu) Importance: Undecided Status: New ** Also affects: gradle-debian-helper (Ubuntu) Importance: Undecided Status: New ** Also affects: clojure1.8 (Ubuntu) Importance: Undecided Status: New ** Also affects: dd-plist (Ubuntu) Importance: Undecided Status: New ** Also affects: maven-compiler-plugin (Ubuntu) Importance: Undecided Status: New ** Also affects: maven-debian-helper (Ubuntu) Importance: Undecided Status: New ** Also affects: plexus-languages (Ubuntu) Importance: Undecided Status: New ** Also affects: saaj (Ubuntu) Importance: Undecided Status: New ** Also affects: surefire (Ubuntu) Importance: Undecided Status: New ** Also affects: ca-certificates-java (Ubuntu) Importance: Undecided Status: New ** Also affects: groovy (Ubuntu) Importance: Undecided Status: New ** Also affects: jaxws-api (Ubuntu) Importance: Undecided Status: New ** Also affects: jws-api (Ubuntu) Importance: Undecided Status: New ** Also affects: metro-policy (Ubuntu) Importance: Undecided Status: New ** Also affects: saaj-ri (Ubuntu) Importance: Undecided Status: New ** Also affects: junit4 (Ubuntu) Importance: Undecided Status: New ** Also affects: gettext (Ubuntu) Importance: Undecided Status: New ** Also affects: scala (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in clojure1.8 package in Ubuntu: New Status in dd-plist package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in gradle-debian-helper package in Ubuntu: New Status in groovy package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jtreg package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in libcommons-lang3-java package in Ubuntu: New Status in maven-compiler-plugin package in Ubuntu: New Status in maven-debian-helper package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in plexus-languages package in Ubuntu: New Status in saaj package in Ubuntu: New Status in saaj-ri package in Ubuntu: New Status in scala package in Ubuntu: New Status in surefire package in Ubuntu: New Status in testng package in Ubuntu: New Bug description: update to openjdk 11 in 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1814133/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1796361] Re: autopkgtests fail with openjdk 11~28-3ubuntu1 in cosmic-proposed
Thanks Olivier, I confirm your test results: ignoring the DocumentView$1.class is fine with both openjdk-10 and openjdk-11. I agree that JEP-181 is the most probable cause as to why this access bridge class is no longer generated - there's a small discussion on why access bridge classes were necessary at https://github.com/immutables/immutables/issues/1#issuecomment-31525561. Thanks for driving this. ** Bug watch added: github.com/immutables/immutables/issues #1 https://github.com/immutables/immutables/issues/1 -- 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/1796361 Title: autopkgtests fail with openjdk 11~28-3ubuntu1 in cosmic-proposed Status in libreoffice package in Ubuntu: Triaged Bug description: libreoffice 6.1.2 autopkgtests pass with openjdk 10.0.2+13-1ubuntu1 that's currently in cosmic. When upgrading openjdk to 11~28-3ubuntu1 in cosmic-proposed, the test called odk-build-examples reliably fails. I'm attaching the log of the failed test, ran separately in an up-to- date amd64 cosmic VM with cosmic-proposed. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 5 17:55:10 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (824 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: libreoffice UpgradeStatus: Upgraded to cosmic on 2018-09-14 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1796361/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1788250] Re: AWT applications fail with java.awt.AWTError: Assistive Technology not found: org.GNOME.Accessibility.AtkWrapper
Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug is being tracked and a fix has been proposed to the openjdk-lts package. The package fix comments out 'assistive_technologies=org.GNOME.Accessibility.AtkWrapper' in /etc/java-11-openjdk/accessibility.properties as well as moves libatk-wrapper-java-jni to Recommends. A new package release with the fix is expected soon. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to java-atk-wrapper in Ubuntu. https://bugs.launchpad.net/bugs/1788250 Title: AWT applications fail with java.awt.AWTError: Assistive Technology not found: org.GNOME.Accessibility.AtkWrapper Status in jEdit: New Status in JOSM: Unknown Status in 389-console package in Ubuntu: New Status in aladin package in Ubuntu: New Status in alter-sequence-alignment package in Ubuntu: New Status in arduino package in Ubuntu: New Status in drmips package in Ubuntu: New Status in emboss package in Ubuntu: New Status in freeplane package in Ubuntu: New Status in geotranz package in Ubuntu: New Status in gpsprune package in Ubuntu: Confirmed Status in jaligner package in Ubuntu: New Status in java-atk-wrapper package in Ubuntu: New Status in jaxe package in Ubuntu: New Status in jedit package in Ubuntu: New Status in jftp package in Ubuntu: New Status in jhdf package in Ubuntu: New Status in jmol package in Ubuntu: New Status in logisim package in Ubuntu: New Status in neobio package in Ubuntu: New Status in openjdk-8 package in Ubuntu: New Status in openjdk-lts package in Ubuntu: Confirmed Status in opticalraytracer package in Ubuntu: New Status in plantuml package in Ubuntu: New Status in proalign package in Ubuntu: New Status in runescape package in Ubuntu: New Status in spread-phy package in Ubuntu: New Status in starjava-topcat package in Ubuntu: New Status in sunflow package in Ubuntu: New Status in thepeg package in Ubuntu: New Status in treeview package in Ubuntu: New Bug description: After recently upgrading to 10.0.2+13-1ubuntu0.18.04.1 in bionic, all AWT applications have started failing with this exception: (using jedit as an example, but it happens for lots of apps): ~ jedit 18:12:48 [main] [error] main: Exception in thread "main" 18:12:48 [main] [error] main: java.awt.AWTError: Assistive Technology not found: org.GNOME.Accessibility.AtkWrapper 18:12:48 [main] [error] main: at java.desktop/java.awt.Toolkit.newAWTError(Toolkit.java:472) 18:12:48 [main] [error] main: at java.desktop/java.awt.Toolkit.fallbackToLoadClassForAT(Toolkit.java:488) 18:12:48 [main] [error] main: at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183) 18:12:48 [main] [error] main: at java.base/java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:177) 18:12:48 [main] [error] main: at java.base/java.util.HashMap$KeySpliterator.forEachRemaining(HashMap.java:1608) 18:12:48 [main] [error] main: at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:484) 18:12:48 [main] [error] main: at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:474) 18:12:48 [main] [error] main: at java.base/java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150) 18:12:48 [main] [error] main: at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173) 18:12:48 [main] [error] main: at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) 18:12:48 [main] [error] main: at java.base/java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:497) 18:12:48 [main] [error] main: at java.desktop/java.awt.Toolkit.loadAssistiveTechnologies(Toolkit.java:532) 18:12:48 [main] [error] main: at java.desktop/java.awt.Toolkit.getDefaultToolkit(Toolkit.java:613) 18:12:48 [main] [error] main: at java.desktop/java.awt.EventQueue.invokeAndWait(EventQueue.java:1342) 18:12:48 [main] [error] main: at java.desktop/javax.swing.SwingUtilities.invokeAndWait(SwingUtilities.java:1480) 18:12:48 [main] [error] main: at org.gjt.sp.jedit.GUIUtilities.showSplashScreen(GUIUtilities.java:1957) 18:12:48 [main] [error] main: at org.gjt.sp.jedit.jEdit.main(jEdit.java:389) 18:12:48 [main] [error] main: Caused by: java.lang.ClassNotFoundException: org.GNOME.Accessibility.AtkWrapper 18:12:48 [main] [error] main: at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:582) 18:12:48 [main] [error] main: at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:190) 18:12:48 [main] [error] main: at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:499) 18:12:48 [main] [error] main: at java.base/java.lang.Class.forName0(Native Method) 18:12:48 [main] [error] main: at
[Desktop-packages] [Bug 1765914] Re: Java windows and fonts are huge running in openjdk-11-jre
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I have been trying to track down which component/application is actually
responsible for creating and maintaining /com/ubuntu/user-interface
/scale-factor, but so far no luck.
It seems to be related to Unity according to the few Google results I
can see, so the question is whether a package failed to remove/move that
setting or if OpenJDK should change what it looks at and/or in which
order.
OpenJDK currently looks for:
- /com/ubuntu/user-interface/scale-factor
- com/canonical/Unity/Interface/text-scaling-factor
- org/gnome/desktop/interface/text-scaling-factor
in that order, using the first one it finds.
Weirdly enough it does not look for org/gnome/desktop/interface/scaling-
factor.
These changes were introduced by JDK-8149115 in commit
http://hg.openjdk.java.net/jdk/jdk/rev/a3cc7e551a48 but neither the bug
nor the Mailing list discussion state why they picked those items and in
this particular order.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1765914
Title:
Java windows and fonts are huge running in openjdk-11-jre
Status in openjdk-lts package in Ubuntu:
New
Status in unity-settings-daemon package in Ubuntu:
New
Bug description:
If I run a Java application with oracle-java-8 in an X session, the
windows and fonts are all normal size. When I run the same application
with openjdk-11-jre, everything is scaled up to double size (see
attached image, which shows an application on the left running in Java
8 and the same application on the right running in Java 10 (from the
package openjdk-11, not openjdk-10 for some reason).
My normal screen layout is 1920x1080 with two screens, so the command
"xrandr -q | awk -F'current' -F',' 'NR==1 {gsub("(
|current)","");print $2}'" shows 1920x2160.
One of the screens is 4K, so presumably Java *might* be detecting this
and deciding it needs to double everything in size, but this is
clearly an error since I'm not even using this mode.
If I set the laptop to use a single external 1920x1080 monitor, it
makes no difference - the Java applications are still double the size
that they should be.
There's no problem if I run in a Wayland session - the app windows run
at a normal size whether in java 10 or 8.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: openjdk-11-jre 10.0.1+10-1ubuntu2
Uname: Linux 4.17.0-041700rc1-generic x86_64
ApportVersion: 2.20.9-0ubuntu6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 21 14:12:39 2018
InstallationDate: Installed on 2017-08-16 (247 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: openjdk-lts
UpgradeStatus: Upgraded to bionic on 2017-11-17 (154 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1765914/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765914] Re: Java windows and fonts are huge running in openjdk-11-jre
** Also affects: unity-settings-daemon (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1765914
Title:
Java windows and fonts are huge running in openjdk-11-jre
Status in openjdk-lts package in Ubuntu:
New
Status in unity-settings-daemon package in Ubuntu:
New
Bug description:
If I run a Java application with oracle-java-8 in an X session, the
windows and fonts are all normal size. When I run the same application
with openjdk-11-jre, everything is scaled up to double size (see
attached image, which shows an application on the left running in Java
8 and the same application on the right running in Java 10 (from the
package openjdk-11, not openjdk-10 for some reason).
My normal screen layout is 1920x1080 with two screens, so the command
"xrandr -q | awk -F'current' -F',' 'NR==1 {gsub("(
|current)","");print $2}'" shows 1920x2160.
One of the screens is 4K, so presumably Java *might* be detecting this
and deciding it needs to double everything in size, but this is
clearly an error since I'm not even using this mode.
If I set the laptop to use a single external 1920x1080 monitor, it
makes no difference - the Java applications are still double the size
that they should be.
There's no problem if I run in a Wayland session - the app windows run
at a normal size whether in java 10 or 8.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: openjdk-11-jre 10.0.1+10-1ubuntu2
Uname: Linux 4.17.0-041700rc1-generic x86_64
ApportVersion: 2.20.9-0ubuntu6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 21 14:12:39 2018
InstallationDate: Installed on 2017-08-16 (247 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: openjdk-lts
UpgradeStatus: Upgraded to bionic on 2017-11-17 (154 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1765914/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767010] Re: [SRU] java-atk-wrapper: replace javah usage with a call to javac
This debdiff removed the javah check in configure.ac ** Patch added: "java-atk-wrapper_0.33.3-20_debdiff_0.33.3-20ubuntu0.1.patch" https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/1767010/+attachment/5127356/+files/java-atk-wrapper_0.33.3-20_debdiff_0.33.3-20ubuntu0.1.patch ** Description changed: [Impact] Currently java-atk-wrapper 0.33.3-20 FTBFS during the Bionic rebuild [1] because it can't find the javah binary. The javah binary has been removed from OpenJDK 10 and the java compiler should be used in its place to build native headers by calling "javac -h". [Test Case] Build java-atk-wrapper 0.33.3-20 in Bionic with a current default-jdk (ie. depends on openjdk-11-jdk), it should FTBFS with: checking for javah... no configure: error: Java 1.6 or later is required to build java-access-bridge When fixed the build is build is expected to succeed. [Regression Potential] No regression is expected as javah is not used by java-atk-wrapper. [Other Info] - * java-atk-wrapper does not use javah although it is currently declared in configure.ac4, the build succeeds by simply removing the javah check. + * java-atk-wrapper does not use javah although it is currently declared in configure.ac, the build succeeds by simply removing the javah check. [References] [1] http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20180408-bionic.html ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to java-atk-wrapper in Ubuntu. https://bugs.launchpad.net/bugs/1767010 Title: [SRU] java-atk-wrapper: replace javah usage with a call to javac Status in java-atk-wrapper package in Ubuntu: New Bug description: [Impact] Currently java-atk-wrapper 0.33.3-20 FTBFS during the Bionic rebuild [1] because it can't find the javah binary. The javah binary has been removed from OpenJDK 10 and the java compiler should be used in its place to build native headers by calling "javac -h". [Test Case] Build java-atk-wrapper 0.33.3-20 in Bionic with a current default-jdk (ie. depends on openjdk-11-jdk), it should FTBFS with: checking for javah... no configure: error: Java 1.6 or later is required to build java-access-bridge When fixed the build is build is expected to succeed. [Regression Potential] No regression is expected as javah is not used by java-atk-wrapper. [Other Info] * java-atk-wrapper does not use javah although it is currently declared in configure.ac, the build succeeds by simply removing the javah check. [References] [1] http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20180408-bionic.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/1767010/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767010] [NEW] [SRU] java-atk-wrapper: replace javah usage with a call to javac
Public bug reported: [Impact] Currently java-atk-wrapper 0.33.3-20 FTBFS during the Bionic rebuild [1] because it can't find the javah binary. The javah binary has been removed from OpenJDK 10 and the java compiler should be used in its place to build native headers by calling "javac -h". [Test Case] Build java-atk-wrapper 0.33.3-20 in Bionic with a current default-jdk (ie. depends on openjdk-11-jdk), it should FTBFS with: checking for javah... no configure: error: Java 1.6 or later is required to build java-access-bridge When fixed the build is build is expected to succeed. [Regression Potential] No regression is expected as javah is not used by java-atk-wrapper. [Other Info] * java-atk-wrapper does not use javah although it is currently declared in configure.ac, the build succeeds by simply removing the javah check. [References] [1] http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20180408-bionic.html ** Affects: java-atk-wrapper (Ubuntu) Importance: Undecided Status: New ** Tags: bionic ftbfs patch ** Tags added: bionic ftbfs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to java-atk-wrapper in Ubuntu. https://bugs.launchpad.net/bugs/1767010 Title: [SRU] java-atk-wrapper: replace javah usage with a call to javac Status in java-atk-wrapper package in Ubuntu: New Bug description: [Impact] Currently java-atk-wrapper 0.33.3-20 FTBFS during the Bionic rebuild [1] because it can't find the javah binary. The javah binary has been removed from OpenJDK 10 and the java compiler should be used in its place to build native headers by calling "javac -h". [Test Case] Build java-atk-wrapper 0.33.3-20 in Bionic with a current default-jdk (ie. depends on openjdk-11-jdk), it should FTBFS with: checking for javah... no configure: error: Java 1.6 or later is required to build java-access-bridge When fixed the build is build is expected to succeed. [Regression Potential] No regression is expected as javah is not used by java-atk-wrapper. [Other Info] * java-atk-wrapper does not use javah although it is currently declared in configure.ac, the build succeeds by simply removing the javah check. [References] [1] http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20180408-bionic.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/1767010/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1699772] Re: linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux-image-3.13.0-121-generic Regression: many user-space apps crashing
Regarding OpenJDK 8, it crashes as soon as Xss is set to (or higher
than) 1141K in a i386 JVM (32-bit).
I used the example code from bug #1700270. Please note that there is no
need to even use the java class: the program will segfault while
starting the JVM, so do remove lines 30-34 from either test_case1.c or
test_case2.c and set Xss to 1441K (or bigger).
The OpenJDK part where the stack location and size are calculated is in
os::Linux::capture_initial_stack() [1], specially
_initial_thread_stack_bottom [2].
>From GDB I was able to collect the following data from that function:
(gdb) p max_size
$1 = 1171456
Note: max_size is Xss rounded to vm_page_size(), thus 1144K [3].
(gdb) info locals
rlim = {rlim_cur = 8388608, rlim_max = 4294967295}
stack_size = 8380416
stack_start = 4294956864
p = 0xf7ffcf34 <__libc_stack_end>
stack_top = 4294959104
low = 0xfffdd000 ""
high = 0xe000
(gdb) x p
0xf7ffcf34 <__libc_stack_end>: 0xd740
(gdb) x stack_top
0xe000: Cannot access memory at address 0xe000
(gdb) x low
0xfffdd000: 0x
(gdb) x high
0xe000: Cannot access memory at address 0xe000
(gdb) p _initial_thread_stack_size
$43 = 1171456
(gdb) x _initial_thread_stack_bottom
0xffee: 0x
Backtrace:
(gdb) bt
#0 os::Linux::capture_initial_stack (max_size=1171456) at
./src/hotspot/src/os/linux/vm/os_linux.cpp:1272
#1 0xf7394287 in os::init_2 () at
./src/hotspot/src/os/linux/vm/os_linux.cpp:4939
#2 0xf74ee886 in Threads::create_vm (args=0xd62c, canTryAgain=0xd5bf)
at ./src/hotspot/src/share/vm/runtime/thread.cpp:3361
#3 0xf7151423 in JNI_CreateJavaVM (vm=0xd684, penv=0xd624,
args=0xd62c) at ./src/hotspot/src/share/vm/prims/jni.cpp:5220
#4 0x5655561f in create_vm (jvm=0xd684) at test_case.c:16
#5 0x56555685 in main (argc=1, argv=0xd744) at test_case.c:25
That information is used by os::Linux::default_guard_size() [4] to fetch both
'bottom' and 'size' used to indicate the start of the guard page - and it has a
nice doc explaining the stack layout. The values from default_guard_size are in
turn used by os::current_stack_base() [5] to calculate what should be the stack
base.
Let me know if there's any additional information I can help with.
[1]
http://hg.openjdk.java.net/jdk8u/jdk8u/hotspot/file/tip/src/os/linux/vm/os_linux.cpp#l1081
[2]
http://hg.openjdk.java.net/jdk8u/jdk8u/hotspot/file/tip/src/os/linux/vm/os_linux.cpp#l1271
[3]
http://hg.openjdk.java.net/jdk8u/jdk8u/hotspot/file/tip/src/os/linux/vm/os_linux.cpp#l5010
[4]
http://hg.openjdk.java.net/jdk8u/jdk8u/hotspot/file/tip/src/os_cpu/linux_x86/vm/os_linux_x86.cpp#l714
[5]
http://hg.openjdk.java.net/jdk8u/jdk8u/hotspot/file/tip/src/os_cpu/linux_x86/vm/os_linux_x86.cpp#l745
--
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/1699772
Title:
linux-image-4.10.0-24-generic, linux-image-4.8.0-56-generic, linux-
image-4.4.0-81-generic, linux-image-3.13.0-121-generic Regression:
many user-space apps crashing
Status in LibreOffice:
Won't Fix
Status in commons-daemon package in Ubuntu:
Confirmed
Status in eclipse package in Ubuntu:
Confirmed
Status in imagej package in Ubuntu:
Confirmed
Status in libreoffice package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Status in octave package in Ubuntu:
Confirmed
Status in python-jpype package in Ubuntu:
Confirmed
Status in rustc package in Ubuntu:
Confirmed
Status in scilab package in Ubuntu:
Confirmed
Status in linux package in Debian:
Confirmed
Bug description:
Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10)
linux-image-4.4.0-81-generic appears to contain a regression, probably
related to the CVE-2017-1000364 fix backport / patch.
Using this kernel, the Oracle Java browser plugin always crashes
during stack-related actions on initialization. This means, the plugin
completely stopped working.
It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to
CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also
contains a fix for CVE-2017-1000364.
uname -a:
> Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as
well as Iceweasel / Firefox/3.5.16 in a chroot.
Using linux-image-4.4.0-81-generic it crashes in all combinations
while with both other kernels it works.
I was not able to obtain any detailed crash information from Firefox 51.0.1,
but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace
which shows the relation to stack operations performed by the plugin, even
without proper debug symbols:
> (gdb) bt full
> #0 0x7fa06d805307 in _expand_stack_to(unsigned char*) () from
[Desktop-packages] [Bug 1699599] Re: libqmi 1.18.0-1 FTBFS when building against glib2.0-2.53.1-1 (or later)
Debdiff between 1.18.0-1 (Artful) and 1.18.0-1ubuntu1 (to sponsor a new
upload).
** Patch added: "libqmi_1.18.0-1_1.18.0-1ubuntu1.debdiff"
https://bugs.launchpad.net/debian/+source/libqmi/+bug/1699599/+attachment/4901193/+files/libqmi_1.18.0-1_1.18.0-1ubuntu1.debdiff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libqmi in Ubuntu.
https://bugs.launchpad.net/bugs/1699599
Title:
libqmi 1.18.0-1 FTBFS when building against glib2.0-2.53.1-1 (or
later)
Status in libqmi package in Ubuntu:
New
Status in libqmi package in Debian:
Unknown
Bug description:
After the Debian sync that update libqmi from 1.16.2-1 to 1.18.0-1,
the package FTBFS due to a new step in the test setup for the test-
generated suite.
== Current FTBFS (from the our artful buildlog) ==
TEST: test-generated... (pid=17634)
/libqmi-glib/generated/core:
(/<>/src/libqmi-glib/test/.libs/test-generated:17634):
GLib-CRITICAL **: g_file_test: assertion 'filename != NULL' failed
FAIL
== Expected (from Debian's buildlog) ==
TEST: test-generated... (pid=8773)
/libqmi-glib/generated/core: OK
/libqmi-glib/generated/dms/get-ids: OK
/libqmi-glib/generated/dms/uim-get-pin-status: OK
/libqmi-glib/generated/dms/uim-verify-pin: OK
/libqmi-glib/generated/dms/get-time: OK
/libqmi-glib/generated/nas/network-scan: OK
/libqmi-glib/generated/nas/get-cell-location-info: OK
PASS: test-generated
== Backtrace ==
#0 0x77113ff1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x771152ed in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7711544f in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x770fa42a in g_file_test () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x77a1ca03 in __qmi_utils_get_driver (cdc_wdm_path=)
at qmi-utils.c:746
#5 0x77a21be7 in device_open_context_step (ctx=0x5576b0f0) at
qmi-device.c:2157
#6 0x7b5e in test_fixture_setup (fixture=0x5576ba00) at
test-fixture.c:156
#7 0x771352c5 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x771356ae in g_test_run_suite () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x771356d1 in g_test_run () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7352 in main (argc=, argv=)
at test-generated.c:665
== strace ==
lstat("/sys", {st_dev=makedev(0, 18), st_ino=1, st_mode=S_IFDIR|0555,
st_nlink=13, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0,
st_atime=2017-06-21T16:17:32+.691480392,
st_mtime=2017-06-19T06:48:49+.50419,
st_ctime=2017-06-19T06:48:49+.50419}) = 0
lstat("/sys/class", {st_dev=makedev(0, 18), st_ino=10, st_mode=S_IFDIR|0755,
st_nlink=73, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0,
st_atime=2017-06-21T15:46:45+.176007545,
st_mtime=2017-06-19T06:48:49+.532000158,
st_ctime=2017-06-19T06:48:49+.532000158}) = 0
lstat("/sys/class/usbmisc", {st_dev=makedev(0, 18), st_ino=107497,
st_mode=S_IFDIR|0755, st_nlink=2, st_uid=0, st_gid=0, st_blksize=4096,
st_blocks=0, st_size=0, st_atime=2017-06-21T15:46:45+.27699,
st_mtime=2017-06-21T15:46:45+.196007673,
st_ctime=2017-06-21T15:46:45+.196007673}) = 0
lstat("/sys/class/usbmisc/qmi00031419", 0x7ffc6fc9ec20) = -1 ENOENT (No
such file or directory)
getpeername(2, 0x7ffc6fc9e800, [128]) = -1 ENOTSOCK (Socket operation on
non-socket)
futex(0x7f2423d66e28, FUTEX_WAKE_PRIVATE, 2147483647) = 0
ioctl(2, TCGETS, {c_iflags=0x4500, c_oflags=0x5, c_cflags=0xbf,
c_lflags=0x8a3b, c_line=0,
c_cc="\x03\x1c\x7f\x15\x04\x00\x01\x00\x11\x13\x1a\x00\x12\x0f\x17\x16\x00\x00\x00"})
= 0
brk(0x5567ac071000) = 0x5567ac071000
brk(0x5567ac069000) = 0x5567ac069000
write(2,
"\n(/build/libqmi-cr4ivg/libqmi-1.18.0/src/libqmi-glib/test/.libs/test-generated:31419):
GLib-\33[1;35mCRITICAL\33[0m **: g_file_test: assertion 'filename != NULL'
failed\n", 165) = 165
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
== Error source ==
The following (snipped) patch introduced the new test that is now failing:
--- libqmi-1.16.2/src/libqmi-glib/qmi-utils.c 2016-07-13 07:27:23.0
-0700
+++ libqmi-1.18.0/src/libqmi-glib/qmi-utils.c 2017-03-21 06:26:54.0
-0700
@@ -1078,27 +720,49 @@
/*/
+gchar *
+__qmi_utils_get_driver (const gchar
[Desktop-packages] [Bug 1699599] Re: libqmi 1.18.0-1 FTBFS when building against glib2.0-2.53.1-1 (or later)
Upstream patch with DEP3 header.
** Bug watch added: Debian Bug tracker #865579
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865579
** Also affects: libqmi (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865579
Importance: Unknown
Status: Unknown
** Patch added: "fix-g-file-test-null-assertion.diff"
https://bugs.launchpad.net/debian/+source/libqmi/+bug/1699599/+attachment/4901192/+files/fix-g-file-test-null-assertion.diff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libqmi in Ubuntu.
https://bugs.launchpad.net/bugs/1699599
Title:
libqmi 1.18.0-1 FTBFS when building against glib2.0-2.53.1-1 (or
later)
Status in libqmi package in Ubuntu:
New
Status in libqmi package in Debian:
Unknown
Bug description:
After the Debian sync that update libqmi from 1.16.2-1 to 1.18.0-1,
the package FTBFS due to a new step in the test setup for the test-
generated suite.
== Current FTBFS (from the our artful buildlog) ==
TEST: test-generated... (pid=17634)
/libqmi-glib/generated/core:
(/<>/src/libqmi-glib/test/.libs/test-generated:17634):
GLib-CRITICAL **: g_file_test: assertion 'filename != NULL' failed
FAIL
== Expected (from Debian's buildlog) ==
TEST: test-generated... (pid=8773)
/libqmi-glib/generated/core: OK
/libqmi-glib/generated/dms/get-ids: OK
/libqmi-glib/generated/dms/uim-get-pin-status: OK
/libqmi-glib/generated/dms/uim-verify-pin: OK
/libqmi-glib/generated/dms/get-time: OK
/libqmi-glib/generated/nas/network-scan: OK
/libqmi-glib/generated/nas/get-cell-location-info: OK
PASS: test-generated
== Backtrace ==
#0 0x77113ff1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x771152ed in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7711544f in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x770fa42a in g_file_test () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x77a1ca03 in __qmi_utils_get_driver (cdc_wdm_path=)
at qmi-utils.c:746
#5 0x77a21be7 in device_open_context_step (ctx=0x5576b0f0) at
qmi-device.c:2157
#6 0x7b5e in test_fixture_setup (fixture=0x5576ba00) at
test-fixture.c:156
#7 0x771352c5 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x771356ae in g_test_run_suite () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x771356d1 in g_test_run () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7352 in main (argc=, argv=)
at test-generated.c:665
== strace ==
lstat("/sys", {st_dev=makedev(0, 18), st_ino=1, st_mode=S_IFDIR|0555,
st_nlink=13, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0,
st_atime=2017-06-21T16:17:32+.691480392,
st_mtime=2017-06-19T06:48:49+.50419,
st_ctime=2017-06-19T06:48:49+.50419}) = 0
lstat("/sys/class", {st_dev=makedev(0, 18), st_ino=10, st_mode=S_IFDIR|0755,
st_nlink=73, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0,
st_atime=2017-06-21T15:46:45+.176007545,
st_mtime=2017-06-19T06:48:49+.532000158,
st_ctime=2017-06-19T06:48:49+.532000158}) = 0
lstat("/sys/class/usbmisc", {st_dev=makedev(0, 18), st_ino=107497,
st_mode=S_IFDIR|0755, st_nlink=2, st_uid=0, st_gid=0, st_blksize=4096,
st_blocks=0, st_size=0, st_atime=2017-06-21T15:46:45+.27699,
st_mtime=2017-06-21T15:46:45+.196007673,
st_ctime=2017-06-21T15:46:45+.196007673}) = 0
lstat("/sys/class/usbmisc/qmi00031419", 0x7ffc6fc9ec20) = -1 ENOENT (No
such file or directory)
getpeername(2, 0x7ffc6fc9e800, [128]) = -1 ENOTSOCK (Socket operation on
non-socket)
futex(0x7f2423d66e28, FUTEX_WAKE_PRIVATE, 2147483647) = 0
ioctl(2, TCGETS, {c_iflags=0x4500, c_oflags=0x5, c_cflags=0xbf,
c_lflags=0x8a3b, c_line=0,
c_cc="\x03\x1c\x7f\x15\x04\x00\x01\x00\x11\x13\x1a\x00\x12\x0f\x17\x16\x00\x00\x00"})
= 0
brk(0x5567ac071000) = 0x5567ac071000
brk(0x5567ac069000) = 0x5567ac069000
write(2,
"\n(/build/libqmi-cr4ivg/libqmi-1.18.0/src/libqmi-glib/test/.libs/test-generated:31419):
GLib-\33[1;35mCRITICAL\33[0m **: g_file_test: assertion 'filename != NULL'
failed\n", 165) = 165
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
== Error source ==
The following (snipped) patch introduced the new test that is now failing:
--- libqmi-1.16.2/src/libqmi-glib/qmi-utils.c 2016-07-13 07:27:23.0
-0700
+++ libqmi-1.18.0/src/libqmi-glib/qmi-utils.c 2017-03-21
[Desktop-packages] [Bug 1699599] Re: libqmi 1.18.0-1 FTBFS when building against glib2.0-2.53.1-1 (or later)
** Summary changed:
- libqmi 1.18.0-1 FTBFS on artful due to test failure
+ libqmi 1.18.0-1 FTBFS when building against glib2.0-2.53.1-1 (or later)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libqmi in Ubuntu.
https://bugs.launchpad.net/bugs/1699599
Title:
libqmi 1.18.0-1 FTBFS when building against glib2.0-2.53.1-1 (or
later)
Status in libqmi package in Ubuntu:
New
Bug description:
After the Debian sync that update libqmi from 1.16.2-1 to 1.18.0-1,
the package FTBFS due to a new step in the test setup for the test-
generated suite.
== Current FTBFS (from the our artful buildlog) ==
TEST: test-generated... (pid=17634)
/libqmi-glib/generated/core:
(/<>/src/libqmi-glib/test/.libs/test-generated:17634):
GLib-CRITICAL **: g_file_test: assertion 'filename != NULL' failed
FAIL
== Expected (from Debian's buildlog) ==
TEST: test-generated... (pid=8773)
/libqmi-glib/generated/core: OK
/libqmi-glib/generated/dms/get-ids: OK
/libqmi-glib/generated/dms/uim-get-pin-status: OK
/libqmi-glib/generated/dms/uim-verify-pin: OK
/libqmi-glib/generated/dms/get-time: OK
/libqmi-glib/generated/nas/network-scan: OK
/libqmi-glib/generated/nas/get-cell-location-info: OK
PASS: test-generated
== Backtrace ==
#0 0x77113ff1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x771152ed in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7711544f in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x770fa42a in g_file_test () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x77a1ca03 in __qmi_utils_get_driver (cdc_wdm_path=)
at qmi-utils.c:746
#5 0x77a21be7 in device_open_context_step (ctx=0x5576b0f0) at
qmi-device.c:2157
#6 0x7b5e in test_fixture_setup (fixture=0x5576ba00) at
test-fixture.c:156
#7 0x771352c5 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x771356ae in g_test_run_suite () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x771356d1 in g_test_run () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7352 in main (argc=, argv=)
at test-generated.c:665
== strace ==
lstat("/sys", {st_dev=makedev(0, 18), st_ino=1, st_mode=S_IFDIR|0555,
st_nlink=13, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0,
st_atime=2017-06-21T16:17:32+.691480392,
st_mtime=2017-06-19T06:48:49+.50419,
st_ctime=2017-06-19T06:48:49+.50419}) = 0
lstat("/sys/class", {st_dev=makedev(0, 18), st_ino=10, st_mode=S_IFDIR|0755,
st_nlink=73, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0,
st_atime=2017-06-21T15:46:45+.176007545,
st_mtime=2017-06-19T06:48:49+.532000158,
st_ctime=2017-06-19T06:48:49+.532000158}) = 0
lstat("/sys/class/usbmisc", {st_dev=makedev(0, 18), st_ino=107497,
st_mode=S_IFDIR|0755, st_nlink=2, st_uid=0, st_gid=0, st_blksize=4096,
st_blocks=0, st_size=0, st_atime=2017-06-21T15:46:45+.27699,
st_mtime=2017-06-21T15:46:45+.196007673,
st_ctime=2017-06-21T15:46:45+.196007673}) = 0
lstat("/sys/class/usbmisc/qmi00031419", 0x7ffc6fc9ec20) = -1 ENOENT (No
such file or directory)
getpeername(2, 0x7ffc6fc9e800, [128]) = -1 ENOTSOCK (Socket operation on
non-socket)
futex(0x7f2423d66e28, FUTEX_WAKE_PRIVATE, 2147483647) = 0
ioctl(2, TCGETS, {c_iflags=0x4500, c_oflags=0x5, c_cflags=0xbf,
c_lflags=0x8a3b, c_line=0,
c_cc="\x03\x1c\x7f\x15\x04\x00\x01\x00\x11\x13\x1a\x00\x12\x0f\x17\x16\x00\x00\x00"})
= 0
brk(0x5567ac071000) = 0x5567ac071000
brk(0x5567ac069000) = 0x5567ac069000
write(2,
"\n(/build/libqmi-cr4ivg/libqmi-1.18.0/src/libqmi-glib/test/.libs/test-generated:31419):
GLib-\33[1;35mCRITICAL\33[0m **: g_file_test: assertion 'filename != NULL'
failed\n", 165) = 165
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
== Error source ==
The following (snipped) patch introduced the new test that is now failing:
--- libqmi-1.16.2/src/libqmi-glib/qmi-utils.c 2016-07-13 07:27:23.0
-0700
+++ libqmi-1.18.0/src/libqmi-glib/qmi-utils.c 2017-03-21 06:26:54.0
-0700
@@ -1078,27 +720,49 @@
/*/
+gchar *
+__qmi_utils_get_driver (const gchar *cdc_wdm_path)
+{
+static const gchar *subsystems[] = { "usbmisc", "usb" };
+guint i;
+gchar *device_basename;
+gchar *driver = NULL;
+
+
[Desktop-packages] [Bug 1699599] Re: libqmi 1.18.0-1 FTBFS on artful due to test failure
Tracked the error down to glib2.0 version update from 2.52.0-1 to
2.53.1-1 (and later versions).
They introduced an additional NULL check to g_file_test [1] that now
breaks this particular test, as the code in qmi-utils.c provides a NULL
`path` to g_file_test.
[1] https://bugzilla.gnome.org/show_bug.cgi?id=755046
** Bug watch added: GNOME Bug Tracker #755046
https://bugzilla.gnome.org/show_bug.cgi?id=755046
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libqmi in Ubuntu.
https://bugs.launchpad.net/bugs/1699599
Title:
libqmi 1.18.0-1 FTBFS on artful due to test failure
Status in libqmi package in Ubuntu:
New
Bug description:
After the Debian sync that update libqmi from 1.16.2-1 to 1.18.0-1,
the package FTBFS due to a new step in the test setup for the test-
generated suite.
== Current FTBFS (from the our artful buildlog) ==
TEST: test-generated... (pid=17634)
/libqmi-glib/generated/core:
(/<>/src/libqmi-glib/test/.libs/test-generated:17634):
GLib-CRITICAL **: g_file_test: assertion 'filename != NULL' failed
FAIL
== Expected (from Debian's buildlog) ==
TEST: test-generated... (pid=8773)
/libqmi-glib/generated/core: OK
/libqmi-glib/generated/dms/get-ids: OK
/libqmi-glib/generated/dms/uim-get-pin-status: OK
/libqmi-glib/generated/dms/uim-verify-pin: OK
/libqmi-glib/generated/dms/get-time: OK
/libqmi-glib/generated/nas/network-scan: OK
/libqmi-glib/generated/nas/get-cell-location-info: OK
PASS: test-generated
== Backtrace ==
#0 0x77113ff1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x771152ed in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7711544f in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x770fa42a in g_file_test () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x77a1ca03 in __qmi_utils_get_driver (cdc_wdm_path=)
at qmi-utils.c:746
#5 0x77a21be7 in device_open_context_step (ctx=0x5576b0f0) at
qmi-device.c:2157
#6 0x7b5e in test_fixture_setup (fixture=0x5576ba00) at
test-fixture.c:156
#7 0x771352c5 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x771356ae in g_test_run_suite () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x771356d1 in g_test_run () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7352 in main (argc=, argv=)
at test-generated.c:665
== strace ==
lstat("/sys", {st_dev=makedev(0, 18), st_ino=1, st_mode=S_IFDIR|0555,
st_nlink=13, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0,
st_atime=2017-06-21T16:17:32+.691480392,
st_mtime=2017-06-19T06:48:49+.50419,
st_ctime=2017-06-19T06:48:49+.50419}) = 0
lstat("/sys/class", {st_dev=makedev(0, 18), st_ino=10, st_mode=S_IFDIR|0755,
st_nlink=73, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0,
st_atime=2017-06-21T15:46:45+.176007545,
st_mtime=2017-06-19T06:48:49+.532000158,
st_ctime=2017-06-19T06:48:49+.532000158}) = 0
lstat("/sys/class/usbmisc", {st_dev=makedev(0, 18), st_ino=107497,
st_mode=S_IFDIR|0755, st_nlink=2, st_uid=0, st_gid=0, st_blksize=4096,
st_blocks=0, st_size=0, st_atime=2017-06-21T15:46:45+.27699,
st_mtime=2017-06-21T15:46:45+.196007673,
st_ctime=2017-06-21T15:46:45+.196007673}) = 0
lstat("/sys/class/usbmisc/qmi00031419", 0x7ffc6fc9ec20) = -1 ENOENT (No
such file or directory)
getpeername(2, 0x7ffc6fc9e800, [128]) = -1 ENOTSOCK (Socket operation on
non-socket)
futex(0x7f2423d66e28, FUTEX_WAKE_PRIVATE, 2147483647) = 0
ioctl(2, TCGETS, {c_iflags=0x4500, c_oflags=0x5, c_cflags=0xbf,
c_lflags=0x8a3b, c_line=0,
c_cc="\x03\x1c\x7f\x15\x04\x00\x01\x00\x11\x13\x1a\x00\x12\x0f\x17\x16\x00\x00\x00"})
= 0
brk(0x5567ac071000) = 0x5567ac071000
brk(0x5567ac069000) = 0x5567ac069000
write(2,
"\n(/build/libqmi-cr4ivg/libqmi-1.18.0/src/libqmi-glib/test/.libs/test-generated:31419):
GLib-\33[1;35mCRITICAL\33[0m **: g_file_test: assertion 'filename != NULL'
failed\n", 165) = 165
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
== Error source ==
The following (snipped) patch introduced the new test that is now failing:
--- libqmi-1.16.2/src/libqmi-glib/qmi-utils.c 2016-07-13 07:27:23.0
-0700
+++ libqmi-1.18.0/src/libqmi-glib/qmi-utils.c 2017-03-21 06:26:54.0
-0700
@@ -1078,27 +720,49 @@
[Desktop-packages] [Bug 1699599] Re: libqmi 1.18.0-1 FTBFS on artful due to test failure
** Tags added: ftbfs
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libqmi in Ubuntu.
https://bugs.launchpad.net/bugs/1699599
Title:
libqmi 1.18.0-1 FTBFS on artful due to test failure
Status in libqmi package in Ubuntu:
New
Bug description:
After the Debian sync that update libqmi from 1.16.2-1 to 1.18.0-1,
the package FTBFS due to a new step in the test setup for the test-
generated suite.
== Current FTBFS (from the our artful buildlog) ==
TEST: test-generated... (pid=17634)
/libqmi-glib/generated/core:
(/<>/src/libqmi-glib/test/.libs/test-generated:17634):
GLib-CRITICAL **: g_file_test: assertion 'filename != NULL' failed
FAIL
== Expected (from Debian's buildlog) ==
TEST: test-generated... (pid=8773)
/libqmi-glib/generated/core: OK
/libqmi-glib/generated/dms/get-ids: OK
/libqmi-glib/generated/dms/uim-get-pin-status: OK
/libqmi-glib/generated/dms/uim-verify-pin: OK
/libqmi-glib/generated/dms/get-time: OK
/libqmi-glib/generated/nas/network-scan: OK
/libqmi-glib/generated/nas/get-cell-location-info: OK
PASS: test-generated
== Backtrace ==
#0 0x77113ff1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x771152ed in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7711544f in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x770fa42a in g_file_test () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x77a1ca03 in __qmi_utils_get_driver (cdc_wdm_path=)
at qmi-utils.c:746
#5 0x77a21be7 in device_open_context_step (ctx=0x5576b0f0) at
qmi-device.c:2157
#6 0x7b5e in test_fixture_setup (fixture=0x5576ba00) at
test-fixture.c:156
#7 0x771352c5 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x771356ae in g_test_run_suite () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x771356d1 in g_test_run () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7352 in main (argc=, argv=)
at test-generated.c:665
== strace ==
lstat("/sys", {st_dev=makedev(0, 18), st_ino=1, st_mode=S_IFDIR|0555,
st_nlink=13, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0,
st_atime=2017-06-21T16:17:32+.691480392,
st_mtime=2017-06-19T06:48:49+.50419,
st_ctime=2017-06-19T06:48:49+.50419}) = 0
lstat("/sys/class", {st_dev=makedev(0, 18), st_ino=10, st_mode=S_IFDIR|0755,
st_nlink=73, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0,
st_atime=2017-06-21T15:46:45+.176007545,
st_mtime=2017-06-19T06:48:49+.532000158,
st_ctime=2017-06-19T06:48:49+.532000158}) = 0
lstat("/sys/class/usbmisc", {st_dev=makedev(0, 18), st_ino=107497,
st_mode=S_IFDIR|0755, st_nlink=2, st_uid=0, st_gid=0, st_blksize=4096,
st_blocks=0, st_size=0, st_atime=2017-06-21T15:46:45+.27699,
st_mtime=2017-06-21T15:46:45+.196007673,
st_ctime=2017-06-21T15:46:45+.196007673}) = 0
lstat("/sys/class/usbmisc/qmi00031419", 0x7ffc6fc9ec20) = -1 ENOENT (No
such file or directory)
getpeername(2, 0x7ffc6fc9e800, [128]) = -1 ENOTSOCK (Socket operation on
non-socket)
futex(0x7f2423d66e28, FUTEX_WAKE_PRIVATE, 2147483647) = 0
ioctl(2, TCGETS, {c_iflags=0x4500, c_oflags=0x5, c_cflags=0xbf,
c_lflags=0x8a3b, c_line=0,
c_cc="\x03\x1c\x7f\x15\x04\x00\x01\x00\x11\x13\x1a\x00\x12\x0f\x17\x16\x00\x00\x00"})
= 0
brk(0x5567ac071000) = 0x5567ac071000
brk(0x5567ac069000) = 0x5567ac069000
write(2,
"\n(/build/libqmi-cr4ivg/libqmi-1.18.0/src/libqmi-glib/test/.libs/test-generated:31419):
GLib-\33[1;35mCRITICAL\33[0m **: g_file_test: assertion 'filename != NULL'
failed\n", 165) = 165
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
== Error source ==
The following (snipped) patch introduced the new test that is now failing:
--- libqmi-1.16.2/src/libqmi-glib/qmi-utils.c 2016-07-13 07:27:23.0
-0700
+++ libqmi-1.18.0/src/libqmi-glib/qmi-utils.c 2017-03-21 06:26:54.0
-0700
@@ -1078,27 +720,49 @@
/*/
+gchar *
+__qmi_utils_get_driver (const gchar *cdc_wdm_path)
+{
+static const gchar *subsystems[] = { "usbmisc", "usb" };
+guint i;
+gchar *device_basename;
+gchar *driver = NULL;
+
+device_basename = g_path_get_basename (cdc_wdm_path);
+
+for (i = 0; !driver && i < G_N_ELEMENTS (subsystems); i++) {
+gchar *tmp;
+
[Desktop-packages] [Bug 1699599] Re: libqmi 1.18.0-1 FTBFS on artful due to test failure
** Summary changed:
- [FTBFS] libqmi 1.18.0-1 fails test during build time
+ libqmi 1.18.0-1 FTBFS on artful due to test failure
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libqmi in Ubuntu.
https://bugs.launchpad.net/bugs/1699599
Title:
libqmi 1.18.0-1 FTBFS on artful due to test failure
Status in libqmi package in Ubuntu:
New
Bug description:
After the Debian sync that update libqmi from 1.16.2-1 to 1.18.0-1,
the package FTBFS due to a new step in the test setup for the test-
generated suite.
== Current FTBFS (from the our artful buildlog) ==
TEST: test-generated... (pid=17634)
/libqmi-glib/generated/core:
(/<>/src/libqmi-glib/test/.libs/test-generated:17634):
GLib-CRITICAL **: g_file_test: assertion 'filename != NULL' failed
FAIL
== Expected (from Debian's buildlog) ==
TEST: test-generated... (pid=8773)
/libqmi-glib/generated/core: OK
/libqmi-glib/generated/dms/get-ids: OK
/libqmi-glib/generated/dms/uim-get-pin-status: OK
/libqmi-glib/generated/dms/uim-verify-pin: OK
/libqmi-glib/generated/dms/get-time: OK
/libqmi-glib/generated/nas/network-scan: OK
/libqmi-glib/generated/nas/get-cell-location-info: OK
PASS: test-generated
== Backtrace ==
#0 0x77113ff1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x771152ed in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7711544f in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x770fa42a in g_file_test () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x77a1ca03 in __qmi_utils_get_driver (cdc_wdm_path=)
at qmi-utils.c:746
#5 0x77a21be7 in device_open_context_step (ctx=0x5576b0f0) at
qmi-device.c:2157
#6 0x7b5e in test_fixture_setup (fixture=0x5576ba00) at
test-fixture.c:156
#7 0x771352c5 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x771356ae in g_test_run_suite () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x771356d1 in g_test_run () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7352 in main (argc=, argv=)
at test-generated.c:665
== strace ==
lstat("/sys", {st_dev=makedev(0, 18), st_ino=1, st_mode=S_IFDIR|0555,
st_nlink=13, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0,
st_atime=2017-06-21T16:17:32+.691480392,
st_mtime=2017-06-19T06:48:49+.50419,
st_ctime=2017-06-19T06:48:49+.50419}) = 0
lstat("/sys/class", {st_dev=makedev(0, 18), st_ino=10, st_mode=S_IFDIR|0755,
st_nlink=73, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0,
st_atime=2017-06-21T15:46:45+.176007545,
st_mtime=2017-06-19T06:48:49+.532000158,
st_ctime=2017-06-19T06:48:49+.532000158}) = 0
lstat("/sys/class/usbmisc", {st_dev=makedev(0, 18), st_ino=107497,
st_mode=S_IFDIR|0755, st_nlink=2, st_uid=0, st_gid=0, st_blksize=4096,
st_blocks=0, st_size=0, st_atime=2017-06-21T15:46:45+.27699,
st_mtime=2017-06-21T15:46:45+.196007673,
st_ctime=2017-06-21T15:46:45+.196007673}) = 0
lstat("/sys/class/usbmisc/qmi00031419", 0x7ffc6fc9ec20) = -1 ENOENT (No
such file or directory)
getpeername(2, 0x7ffc6fc9e800, [128]) = -1 ENOTSOCK (Socket operation on
non-socket)
futex(0x7f2423d66e28, FUTEX_WAKE_PRIVATE, 2147483647) = 0
ioctl(2, TCGETS, {c_iflags=0x4500, c_oflags=0x5, c_cflags=0xbf,
c_lflags=0x8a3b, c_line=0,
c_cc="\x03\x1c\x7f\x15\x04\x00\x01\x00\x11\x13\x1a\x00\x12\x0f\x17\x16\x00\x00\x00"})
= 0
brk(0x5567ac071000) = 0x5567ac071000
brk(0x5567ac069000) = 0x5567ac069000
write(2,
"\n(/build/libqmi-cr4ivg/libqmi-1.18.0/src/libqmi-glib/test/.libs/test-generated:31419):
GLib-\33[1;35mCRITICAL\33[0m **: g_file_test: assertion 'filename != NULL'
failed\n", 165) = 165
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
== Error source ==
The following (snipped) patch introduced the new test that is now failing:
--- libqmi-1.16.2/src/libqmi-glib/qmi-utils.c 2016-07-13 07:27:23.0
-0700
+++ libqmi-1.18.0/src/libqmi-glib/qmi-utils.c 2017-03-21 06:26:54.0
-0700
@@ -1078,27 +720,49 @@
/*/
+gchar *
+__qmi_utils_get_driver (const gchar *cdc_wdm_path)
+{
+static const gchar *subsystems[] = { "usbmisc", "usb" };
+guint i;
+gchar *device_basename;
+gchar *driver = NULL;
+
+device_basename = g_path_get_basename
[Desktop-packages] [Bug 1699599] Re: [FTBFS] libqmi 1.18.0-1 fails test during build time
** Description changed:
After the Debian sync that update libqmi from 1.16.2-1 to 1.18.0-1, the
package FTBFS due to a new step in the test setup for the test-generated
suite.
- From the buildlogs:
-
+ == Current FTBFS (from the our artful buildlog) ==
TEST: test-generated... (pid=17634)
/libqmi-glib/generated/core:
(/<>/src/libqmi-glib/test/.libs/test-generated:17634):
GLib-CRITICAL **: g_file_test: assertion 'filename != NULL' failed
FAIL
- Backtrace:
+
+ == Expected (from Debian's buildlog) ==
+ TEST: test-generated... (pid=8773)
+ /libqmi-glib/generated/core: OK
+ /libqmi-glib/generated/dms/get-ids: OK
+ /libqmi-glib/generated/dms/uim-get-pin-status: OK
+ /libqmi-glib/generated/dms/uim-verify-pin: OK
+ /libqmi-glib/generated/dms/get-time: OK
+ /libqmi-glib/generated/nas/network-scan: OK
+ /libqmi-glib/generated/nas/get-cell-location-info: OK
+ PASS: test-generated
+
+
+ == Backtrace ==
#0 0x77113ff1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x771152ed in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7711544f in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x770fa42a in g_file_test () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x77a1ca03 in __qmi_utils_get_driver (cdc_wdm_path=)
at qmi-utils.c:746
#5 0x77a21be7 in device_open_context_step (ctx=0x5576b0f0) at
qmi-device.c:2157
#6 0x7b5e in test_fixture_setup (fixture=0x5576ba00) at
test-fixture.c:156
#7 0x771352c5 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x771356ae in g_test_run_suite () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x771356d1 in g_test_run () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7352 in main (argc=, argv=)
at test-generated.c:665
- strace:
+ == strace ==
lstat("/sys", {st_dev=makedev(0, 18), st_ino=1, st_mode=S_IFDIR|0555,
st_nlink=13, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0,
st_atime=2017-06-21T16:17:32+.691480392,
st_mtime=2017-06-19T06:48:49+.50419,
st_ctime=2017-06-19T06:48:49+.50419}) = 0
lstat("/sys/class", {st_dev=makedev(0, 18), st_ino=10, st_mode=S_IFDIR|0755,
st_nlink=73, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0,
st_atime=2017-06-21T15:46:45+.176007545,
st_mtime=2017-06-19T06:48:49+.532000158,
st_ctime=2017-06-19T06:48:49+.532000158}) = 0
lstat("/sys/class/usbmisc", {st_dev=makedev(0, 18), st_ino=107497,
st_mode=S_IFDIR|0755, st_nlink=2, st_uid=0, st_gid=0, st_blksize=4096,
st_blocks=0, st_size=0, st_atime=2017-06-21T15:46:45+.27699,
st_mtime=2017-06-21T15:46:45+.196007673,
st_ctime=2017-06-21T15:46:45+.196007673}) = 0
lstat("/sys/class/usbmisc/qmi00031419", 0x7ffc6fc9ec20) = -1 ENOENT (No
such file or directory)
getpeername(2, 0x7ffc6fc9e800, [128]) = -1 ENOTSOCK (Socket operation on
non-socket)
futex(0x7f2423d66e28, FUTEX_WAKE_PRIVATE, 2147483647) = 0
ioctl(2, TCGETS, {c_iflags=0x4500, c_oflags=0x5, c_cflags=0xbf,
c_lflags=0x8a3b, c_line=0,
c_cc="\x03\x1c\x7f\x15\x04\x00\x01\x00\x11\x13\x1a\x00\x12\x0f\x17\x16\x00\x00\x00"})
= 0
brk(0x5567ac071000) = 0x5567ac071000
brk(0x5567ac069000) = 0x5567ac069000
write(2,
"\n(/build/libqmi-cr4ivg/libqmi-1.18.0/src/libqmi-glib/test/.libs/test-generated:31419):
GLib-\33[1;35mCRITICAL\33[0m **: g_file_test: assertion 'filename != NULL'
failed\n", 165) = 165
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
- The following (snipped) patch introduced the new test that is now
- failing:
+
+ == Error source ==
+ The following (snipped) patch introduced the new test that is now failing:
--- libqmi-1.16.2/src/libqmi-glib/qmi-utils.c 2016-07-13 07:27:23.0
-0700
+++ libqmi-1.18.0/src/libqmi-glib/qmi-utils.c 2017-03-21 06:26:54.0
-0700
@@ -1078,27 +720,49 @@
/*/
+gchar *
+__qmi_utils_get_driver (const gchar *cdc_wdm_path)
+{
+static const gchar *subsystems[] = { "usbmisc", "usb" };
+guint i;
+gchar *device_basename;
+gchar *driver = NULL;
+
+device_basename = g_path_get_basename (cdc_wdm_path);
+
+for (i = 0; !driver && i < G_N_ELEMENTS (subsystems); i++) {
+gchar *tmp;
+gchar *path;
+
+/* driver sysfs can be built directly using subsystem and name; e.g.
for subsystem
+ * usbmisc and name
[Desktop-packages] [Bug 1699599] Re: [FTBFS] libqmi 1.18.0-1 fails test during build time
** Description changed:
After the Debian sync that update libqmi from 1.16.2-1 to 1.18.0-1, the
package FTBFS due to a new step in the test setup for the test-generated
suite.
From the buildlogs:
TEST: test-generated... (pid=17634)
/libqmi-glib/generated/core:
(/<>/src/libqmi-glib/test/.libs/test-generated:17634):
GLib-CRITICAL **: g_file_test: assertion 'filename != NULL' failed
FAIL
Backtrace:
#0 0x77113ff1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x771152ed in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7711544f in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x770fa42a in g_file_test () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x77a1ca03 in __qmi_utils_get_driver (cdc_wdm_path=)
at qmi-utils.c:746
#5 0x77a21be7 in device_open_context_step (ctx=0x5576b0f0) at
qmi-device.c:2157
#6 0x7b5e in test_fixture_setup (fixture=0x5576ba00) at
test-fixture.c:156
#7 0x771352c5 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x771356ae in g_test_run_suite () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x771356d1 in g_test_run () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7352 in main (argc=, argv=)
at test-generated.c:665
strace:
lstat("/sys", {st_dev=makedev(0, 18), st_ino=1, st_mode=S_IFDIR|0555,
st_nlink=13, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0,
st_atime=2017-06-21T16:17:32+.691480392,
st_mtime=2017-06-19T06:48:49+.50419,
st_ctime=2017-06-19T06:48:49+.50419}) = 0
lstat("/sys/class", {st_dev=makedev(0, 18), st_ino=10, st_mode=S_IFDIR|0755,
st_nlink=73, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0,
st_atime=2017-06-21T15:46:45+.176007545,
st_mtime=2017-06-19T06:48:49+.532000158,
st_ctime=2017-06-19T06:48:49+.532000158}) = 0
lstat("/sys/class/usbmisc", {st_dev=makedev(0, 18), st_ino=107497,
st_mode=S_IFDIR|0755, st_nlink=2, st_uid=0, st_gid=0, st_blksize=4096,
st_blocks=0, st_size=0, st_atime=2017-06-21T15:46:45+.27699,
st_mtime=2017-06-21T15:46:45+.196007673,
st_ctime=2017-06-21T15:46:45+.196007673}) = 0
lstat("/sys/class/usbmisc/qmi00031419", 0x7ffc6fc9ec20) = -1 ENOENT (No
such file or directory)
getpeername(2, 0x7ffc6fc9e800, [128]) = -1 ENOTSOCK (Socket operation on
non-socket)
futex(0x7f2423d66e28, FUTEX_WAKE_PRIVATE, 2147483647) = 0
ioctl(2, TCGETS, {c_iflags=0x4500, c_oflags=0x5, c_cflags=0xbf,
c_lflags=0x8a3b, c_line=0,
c_cc="\x03\x1c\x7f\x15\x04\x00\x01\x00\x11\x13\x1a\x00\x12\x0f\x17\x16\x00\x00\x00"})
= 0
brk(0x5567ac071000) = 0x5567ac071000
brk(0x5567ac069000) = 0x5567ac069000
write(2,
"\n(/build/libqmi-cr4ivg/libqmi-1.18.0/src/libqmi-glib/test/.libs/test-generated:31419):
GLib-\33[1;35mCRITICAL\33[0m **: g_file_test: assertion 'filename != NULL'
failed\n", 165) = 165
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
The following (snipped) patch introduced the new test that is now
failing:
--- libqmi-1.16.2/src/libqmi-glib/qmi-utils.c 2016-07-13 07:27:23.0
-0700
+++ libqmi-1.18.0/src/libqmi-glib/qmi-utils.c 2017-03-21 06:26:54.0
-0700
@@ -1078,27 +720,49 @@
/*/
+gchar *
+__qmi_utils_get_driver (const gchar *cdc_wdm_path)
+{
+static const gchar *subsystems[] = { "usbmisc", "usb" };
+guint i;
+gchar *device_basename;
+gchar *driver = NULL;
+
+device_basename = g_path_get_basename (cdc_wdm_path);
+
+for (i = 0; !driver && i < G_N_ELEMENTS (subsystems); i++) {
+gchar *tmp;
+gchar *path;
+
+/* driver sysfs can be built directly using subsystem and name; e.g.
for subsystem
+ * usbmisc and name cdc-wdm0:
+ *$ realpath /sys/class/usbmisc/cdc-wdm0/device/driver
+ */sys/bus/usb/drivers/qmi_wwan
+ */
+tmp = g_strdup_printf ("/sys/class/%s/%s/device/driver",
subsystems[i], device_basename);
+path = canonicalize_file_name (tmp);
+g_free (tmp);
+
+if (g_file_test (path, G_FILE_TEST_EXISTS))
+driver = g_path_get_basename (path);
+g_free (path);
+}
+
+g_free (device_basename);
+
+return driver;
+}
+
+/*/
--- libqmi-1.16.2/src/libqmi-glib/qmi-device.c 2016-11-07 01:58:29.0
-0800
+++ libqmi-1.18.0/src/libqmi-glib/qmi-device.c 2017-03-21 06:26:54.0
-0700
@@ -2285,6 +2153,60 @@
[Desktop-packages] [Bug 1699599] Re: [FTBFS] libqmi 1.18.0-1 fails test during build time
** Description changed:
After the Debian sync that update libqmi from 1.16.2-1 to 1.18.0-1, the
package FTBFS due to a new step in the test setup for the test-generated
suite.
From the buildlogs:
TEST: test-generated... (pid=17634)
- /libqmi-glib/generated/core:
+ /libqmi-glib/generated/core:
(/<>/src/libqmi-glib/test/.libs/test-generated:17634):
GLib-CRITICAL **: g_file_test: assertion 'filename != NULL' failed
FAIL
-
Backtrace:
#0 0x77113ff1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x771152ed in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7711544f in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x770fa42a in g_file_test () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x77a1ca03 in __qmi_utils_get_driver (cdc_wdm_path=)
- at qmi-utils.c:746
+ at qmi-utils.c:746
#5 0x77a21be7 in device_open_context_step (ctx=0x5576b0f0) at
qmi-device.c:2157
#6 0x7b5e in test_fixture_setup (fixture=0x5576ba00) at
test-fixture.c:156
#7 0x771352c5 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x771356ae in g_test_run_suite () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x771356d1 in g_test_run () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7352 in main (argc=, argv=)
- at test-generated.c:665
+ at test-generated.c:665
strace:
lstat("/sys", {st_dev=makedev(0, 18), st_ino=1, st_mode=S_IFDIR|0555,
st_nlink=13, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0,
st_atime=2017-06-21T16:17:32+.691480392,
st_mtime=2017-06-19T06:48:49+.50419,
st_ctime=2017-06-19T06:48:49+.50419}) = 0
lstat("/sys/class", {st_dev=makedev(0, 18), st_ino=10, st_mode=S_IFDIR|0755,
st_nlink=73, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0,
st_atime=2017-06-21T15:46:45+.176007545,
st_mtime=2017-06-19T06:48:49+.532000158,
st_ctime=2017-06-19T06:48:49+.532000158}) = 0
lstat("/sys/class/usbmisc", {st_dev=makedev(0, 18), st_ino=107497,
st_mode=S_IFDIR|0755, st_nlink=2, st_uid=0, st_gid=0, st_blksize=4096,
st_blocks=0, st_size=0, st_atime=2017-06-21T15:46:45+.27699,
st_mtime=2017-06-21T15:46:45+.196007673,
st_ctime=2017-06-21T15:46:45+.196007673}) = 0
lstat("/sys/class/usbmisc/qmi00031419", 0x7ffc6fc9ec20) = -1 ENOENT (No
such file or directory)
getpeername(2, 0x7ffc6fc9e800, [128]) = -1 ENOTSOCK (Socket operation on
non-socket)
futex(0x7f2423d66e28, FUTEX_WAKE_PRIVATE, 2147483647) = 0
ioctl(2, TCGETS, {c_iflags=0x4500, c_oflags=0x5, c_cflags=0xbf,
c_lflags=0x8a3b, c_line=0,
c_cc="\x03\x1c\x7f\x15\x04\x00\x01\x00\x11\x13\x1a\x00\x12\x0f\x17\x16\x00\x00\x00"})
= 0
brk(0x5567ac071000) = 0x5567ac071000
brk(0x5567ac069000) = 0x5567ac069000
write(2,
"\n(/build/libqmi-cr4ivg/libqmi-1.18.0/src/libqmi-glib/test/.libs/test-generated:31419):
GLib-\33[1;35mCRITICAL\33[0m **: g_file_test: assertion 'filename != NULL'
failed\n", 165) = 165
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
-
The following (snipped) patch introduced the new test that is now
failing:
--- libqmi-1.16.2/src/libqmi-glib/qmi-utils.c 2016-07-13 07:27:23.0
-0700
+++ libqmi-1.18.0/src/libqmi-glib/qmi-utils.c 2017-03-21 06:26:54.0
-0700
@@ -1078,27 +720,49 @@
-
-
/*/
-
+
+
/*/
+
+gchar *
+__qmi_utils_get_driver (const gchar *cdc_wdm_path)
+{
+static const gchar *subsystems[] = { "usbmisc", "usb" };
+guint i;
+gchar *device_basename;
+gchar *driver = NULL;
+
+device_basename = g_path_get_basename (cdc_wdm_path);
+
+for (i = 0; !driver && i < G_N_ELEMENTS (subsystems); i++) {
+gchar *tmp;
+gchar *path;
+
+/* driver sysfs can be built directly using subsystem and name; e.g.
for subsystem
+ * usbmisc and name cdc-wdm0:
+ *$ realpath /sys/class/usbmisc/cdc-wdm0/device/driver
+ */sys/bus/usb/drivers/qmi_wwan
+ */
+tmp = g_strdup_printf ("/sys/class/%s/%s/device/driver",
subsystems[i], device_basename);
+path = canonicalize_file_name (tmp);
+g_free (tmp);
+
+if (g_file_test (path, G_FILE_TEST_EXISTS))
+driver = g_path_get_basename (path);
+g_free (path);
+}
+
+g_free (device_basename);
+
+return driver;
+}
+
[Desktop-packages] [Bug 1699599] [NEW] [FTBFS] libqmi 1.18.0-1 fails test during build time
Public bug reported:
After the Debian sync that update libqmi from 1.16.2-1 to 1.18.0-1, the
package FTBFS due to a new step in the test setup for the test-generated
suite.
>From the buildlogs:
TEST: test-generated... (pid=17634)
/libqmi-glib/generated/core:
(/<>/src/libqmi-glib/test/.libs/test-generated:17634):
GLib-CRITICAL **: g_file_test: assertion 'filename != NULL' failed
FAIL
Backtrace:
#0 0x77113ff1 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x771152ed in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x7711544f in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x770fa42a in g_file_test () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x77a1ca03 in __qmi_utils_get_driver (cdc_wdm_path=)
at qmi-utils.c:746
#5 0x77a21be7 in device_open_context_step (ctx=0x5576b0f0) at
qmi-device.c:2157
#6 0x7b5e in test_fixture_setup (fixture=0x5576ba00) at
test-fixture.c:156
#7 0x771352c5 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#8 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#9 0x7713549f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x771356ae in g_test_run_suite () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x771356d1 in g_test_run () at
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x7352 in main (argc=, argv=)
at test-generated.c:665
strace:
lstat("/sys", {st_dev=makedev(0, 18), st_ino=1, st_mode=S_IFDIR|0555,
st_nlink=13, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0,
st_atime=2017-06-21T16:17:32+.691480392,
st_mtime=2017-06-19T06:48:49+.50419,
st_ctime=2017-06-19T06:48:49+.50419}) = 0
lstat("/sys/class", {st_dev=makedev(0, 18), st_ino=10, st_mode=S_IFDIR|0755,
st_nlink=73, st_uid=0, st_gid=0, st_blksize=4096, st_blocks=0, st_size=0,
st_atime=2017-06-21T15:46:45+.176007545,
st_mtime=2017-06-19T06:48:49+.532000158,
st_ctime=2017-06-19T06:48:49+.532000158}) = 0
lstat("/sys/class/usbmisc", {st_dev=makedev(0, 18), st_ino=107497,
st_mode=S_IFDIR|0755, st_nlink=2, st_uid=0, st_gid=0, st_blksize=4096,
st_blocks=0, st_size=0, st_atime=2017-06-21T15:46:45+.27699,
st_mtime=2017-06-21T15:46:45+.196007673,
st_ctime=2017-06-21T15:46:45+.196007673}) = 0
lstat("/sys/class/usbmisc/qmi00031419", 0x7ffc6fc9ec20) = -1 ENOENT (No
such file or directory)
getpeername(2, 0x7ffc6fc9e800, [128]) = -1 ENOTSOCK (Socket operation on
non-socket)
futex(0x7f2423d66e28, FUTEX_WAKE_PRIVATE, 2147483647) = 0
ioctl(2, TCGETS, {c_iflags=0x4500, c_oflags=0x5, c_cflags=0xbf,
c_lflags=0x8a3b, c_line=0,
c_cc="\x03\x1c\x7f\x15\x04\x00\x01\x00\x11\x13\x1a\x00\x12\x0f\x17\x16\x00\x00\x00"})
= 0
brk(0x5567ac071000) = 0x5567ac071000
brk(0x5567ac069000) = 0x5567ac069000
write(2,
"\n(/build/libqmi-cr4ivg/libqmi-1.18.0/src/libqmi-glib/test/.libs/test-generated:31419):
GLib-\33[1;35mCRITICAL\33[0m **: g_file_test: assertion 'filename != NULL'
failed\n", 165) = 165
--- SIGTRAP {si_signo=SIGTRAP, si_code=SI_KERNEL} ---
+++ killed by SIGTRAP (core dumped) +++
The following (snipped) patch introduced the new test that is now
failing:
--- libqmi-1.16.2/src/libqmi-glib/qmi-utils.c 2016-07-13 07:27:23.0
-0700
+++ libqmi-1.18.0/src/libqmi-glib/qmi-utils.c 2017-03-21 06:26:54.0
-0700
@@ -1078,27 +720,49 @@
/*/
+gchar *
+__qmi_utils_get_driver (const gchar *cdc_wdm_path)
+{
+static const gchar *subsystems[] = { "usbmisc", "usb" };
+guint i;
+gchar *device_basename;
+gchar *driver = NULL;
+
+device_basename = g_path_get_basename (cdc_wdm_path);
+
+for (i = 0; !driver && i < G_N_ELEMENTS (subsystems); i++) {
+gchar *tmp;
+gchar *path;
+
+/* driver sysfs can be built directly using subsystem and name; e.g.
for subsystem
+ * usbmisc and name cdc-wdm0:
+ *$ realpath /sys/class/usbmisc/cdc-wdm0/device/driver
+ */sys/bus/usb/drivers/qmi_wwan
+ */
+tmp = g_strdup_printf ("/sys/class/%s/%s/device/driver",
subsystems[i], device_basename);
+path = canonicalize_file_name (tmp);
+g_free (tmp);
+
+if (g_file_test (path, G_FILE_TEST_EXISTS))
+driver = g_path_get_basename (path);
+g_free (path);
+}
+
+g_free (device_basename);
+
+return driver;
+}
+
+/*/
--- libqmi-1.16.2/src/libqmi-glib/qmi-device.c 2016-11-07 01:58:29.0
-0800
+++ libqmi-1.18.0/src/libqmi-glib/qmi-device.c 2017-03-21 06:26:54.0
-0700
@@ -2285,6 +2153,60 @@
ctx->step++;
/* Fall down */
+case DEVICE_OPEN_CONTEXT_STEP_DRIVER:
+ctx->driver = __qmi_utils_get_driver
[Desktop-packages] [Bug 1640320] Re: FTBFS in zesty
I believe that the failed builds were re-run since the first report by Dimitri and then failed due to googletest. After fixing the googletest issues then we end up with another FTBFS caused by missing 'vector' includes. I have added a merge proposal with the fixes in place. ** Branch linked: lp:~tdaitx/location-service/lp-1640320-ftbfs-fix ** Changed in: location-service (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1640320 Title: FTBFS in zesty Status in location-service package in Ubuntu: Confirmed Bug description: FTBFS in zesty during a no change rebuild against new boost Please see build logs at: https://launchpad.net/ubuntu/+source /location-service/3.0.0+16.10.20160912-0ubuntu2 Please help fix this [ 10%] Building CXX object src/location_service/com/ubuntu/location/CMakeFiles/ubuntu-location-service-connectivity.dir/connectivity/wireless_network.cpp.o cd /<>/location-service-3.0.0+16.10.20160912/obj-x86_64-linux-gnu/src/location_service/com/ubuntu/location && /usr/bin/g++ -DCOM_UBUNTU_LOCATION_SERVICE_HAVE_NET_CPP=1 -DCOM_UBUNTU_LOCATION_SERVICE_HAVE_UBUNTU_PLATFORM_HARDWARE_API -DCOM_UBUNTU_LOCATION_SERVICE_PROVIDERS_GEOCLUE -DCOM_UBUNTU_LOCATION_SERVICE_PROVIDERS_GPS -Dubuntu_location_service_connectivity_EXPORTS -I/<>/location-service-3.0.0+16.10.20160912/3rd-party -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/json-c -I/<>/location-service-3.0.0+16.10.20160912/include/location_service -I/<>/location-service-3.0.0+16.10.20160912/src/location_service -I/<>/location-service-3.0.0+16.10.20160912/obj-x86_64-linux-gnu/src/location_service -I/usr/include/ubuntu -g -O2 -fdebug-prefix-map=/<>/location-service-3.0.0+16.10.20160912=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 -Wall -fno-strict-aliasing -pedantic -Wextra -fPIC -Wno-error=unused-local-typedefs -fPIC -o CMakeFiles/ubuntu-location-service-connectivity.dir/connectivity/wireless_network.cpp.o -c /<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/connectivity/wireless_network.cpp In file included from /<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/sntp_client.h:21:0, from /<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/sntp_client.cpp:19: /<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:57:14: error: ‘vector’ in namespace ‘std’ does not name a template type std::vector xtra_hosts ^~ /<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:59:10: warning: extra ‘;’ [-Wpedantic] }; ^ /<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:66:18: error: ‘vector’ in namespace ‘std’ does not name a template type virtual std::vector download_xtra_data(const Configuration& config) = 0; ^~ make -f po/CMakeFiles/pofiles_70.dir/build.make po/CMakeFiles/pofiles_70.dir/depend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1640320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 913434] Re: ImageIO crashes (core dumped) while reading many image files
IcedTea #1896 tracks the LCMS 2.7 update. The fix for this bug was tracked under IcedTea #3020. ** Bug watch added: Iced Tea Bugzilla #3020 http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=3020 ** Changed in: openjdk Importance: Medium => Unknown ** Changed in: openjdk Status: Fix Released => Unknown ** Changed in: openjdk Remote watch: Iced Tea Bugzilla #1896 => Iced Tea Bugzilla #3020 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lcms2 in Ubuntu. https://bugs.launchpad.net/bugs/913434 Title: ImageIO crashes (core dumped) while reading many image files Status in OpenJDK: Unknown Status in lcms2 package in Ubuntu: Invalid Status in openjdk-7 package in Ubuntu: Fix Released Bug description: Code that uses ImageIO.read() to read many image files (on my system: 270 files, totalling 522.9 MiB) crashes the JVM. ~~~ My system information: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 11.10 Release: 11.10 Codename: oneiric $ uname -a Linux dowah 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux $ javac -version javac 1.7.0_147 $ java -version java version "1.7.0_147-icedtea" ~~~ To reproduce the error: $ javac BugIIO.java $ ulimit -c unlimited # to enable core dump $ java BugIIO ~~~ Terminal output that signifies the error: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fb5babe31f8, pid=4978, tid=140418842154752 # # JRE version: 7.0_147-b147 # Java VM: OpenJDK 64-Bit Server VM (21.0-b17 mixed mode linux-amd64 compressed oops) # Derivative: IcedTea7 2.0 # Distribution: Ubuntu 11.10, package 7~b147-2.0-0ubuntu0.11.10.1 # Problematic frame: # C [liblcms2.so.2+0x121f8] cmsSaveProfileToIOhandler+0x38 # # Core dump written. Default location: /home/joshua/core or core.4978 # # An error report file with more information is saved as: # /home/joshua/hs_err_pid4978.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ # Dibatalkan (core didump) ~~~ PS When I tried to compile BugIIO.java on openjdk-6 and run it on openjdk-6, the program finishes normally (no crash). To clarify: 1. This bug affect OpenJDK 7 (7~b147-2.0-0ubuntu0.11.10.1) (tested on oneiric). 2. This bug does *not* affect OpenJDK 6 (6b23~pre11-0ubuntu1.11.10) (tested on oneiric). To manage notifications about this bug go to: https://bugs.launchpad.net/openjdk/+bug/913434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 913434] Re: ImageIO crashes (core dumped) while reading many image files
This bug was not related to lcms, but to OpenJDK. Invalidating it for LCMS. ** Changed in: lcms2 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lcms2 in Ubuntu. https://bugs.launchpad.net/bugs/913434 Title: ImageIO crashes (core dumped) while reading many image files Status in OpenJDK: Unknown Status in lcms2 package in Ubuntu: Invalid Status in openjdk-7 package in Ubuntu: Fix Released Bug description: Code that uses ImageIO.read() to read many image files (on my system: 270 files, totalling 522.9 MiB) crashes the JVM. ~~~ My system information: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 11.10 Release: 11.10 Codename: oneiric $ uname -a Linux dowah 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux $ javac -version javac 1.7.0_147 $ java -version java version "1.7.0_147-icedtea" ~~~ To reproduce the error: $ javac BugIIO.java $ ulimit -c unlimited # to enable core dump $ java BugIIO ~~~ Terminal output that signifies the error: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fb5babe31f8, pid=4978, tid=140418842154752 # # JRE version: 7.0_147-b147 # Java VM: OpenJDK 64-Bit Server VM (21.0-b17 mixed mode linux-amd64 compressed oops) # Derivative: IcedTea7 2.0 # Distribution: Ubuntu 11.10, package 7~b147-2.0-0ubuntu0.11.10.1 # Problematic frame: # C [liblcms2.so.2+0x121f8] cmsSaveProfileToIOhandler+0x38 # # Core dump written. Default location: /home/joshua/core or core.4978 # # An error report file with more information is saved as: # /home/joshua/hs_err_pid4978.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ # Dibatalkan (core didump) ~~~ PS When I tried to compile BugIIO.java on openjdk-6 and run it on openjdk-6, the program finishes normally (no crash). To clarify: 1. This bug affect OpenJDK 7 (7~b147-2.0-0ubuntu0.11.10.1) (tested on oneiric). 2. This bug does *not* affect OpenJDK 6 (6b23~pre11-0ubuntu1.11.10) (tested on oneiric). To manage notifications about this bug go to: https://bugs.launchpad.net/openjdk/+bug/913434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 913434]
Created attachment 1529 testcase to reproduce it Provide jpeg files (at least 128 of them) in a ./jpg directory Run using something like: $ while ! timeout --preserve-status 10 java Lp9133434Imageio; do echo " done."; done as the bug doesn't happen on every run (seem to depend on the jpeg files under test, I can get it once about every 5 runs). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lcms2 in Ubuntu. https://bugs.launchpad.net/bugs/913434 Title: ImageIO crashes (core dumped) while reading many image files Status in OpenJDK: Confirmed Status in lcms2 package in Ubuntu: Incomplete Status in openjdk-7 package in Ubuntu: Incomplete Bug description: Code that uses ImageIO.read() to read many image files (on my system: 270 files, totalling 522.9 MiB) crashes the JVM. ~~~ My system information: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 11.10 Release: 11.10 Codename: oneiric $ uname -a Linux dowah 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux $ javac -version javac 1.7.0_147 $ java -version java version "1.7.0_147-icedtea" ~~~ To reproduce the error: $ javac BugIIO.java $ ulimit -c unlimited # to enable core dump $ java BugIIO ~~~ Terminal output that signifies the error: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fb5babe31f8, pid=4978, tid=140418842154752 # # JRE version: 7.0_147-b147 # Java VM: OpenJDK 64-Bit Server VM (21.0-b17 mixed mode linux-amd64 compressed oops) # Derivative: IcedTea7 2.0 # Distribution: Ubuntu 11.10, package 7~b147-2.0-0ubuntu0.11.10.1 # Problematic frame: # C [liblcms2.so.2+0x121f8] cmsSaveProfileToIOhandler+0x38 # # Core dump written. Default location: /home/joshua/core or core.4978 # # An error report file with more information is saved as: # /home/joshua/hs_err_pid4978.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ # Dibatalkan (core didump) ~~~ PS When I tried to compile BugIIO.java on openjdk-6 and run it on openjdk-6, the program finishes normally (no crash). To clarify: 1. This bug affect OpenJDK 7 (7~b147-2.0-0ubuntu0.11.10.1) (tested on oneiric). 2. This bug does *not* affect OpenJDK 6 (6b23~pre11-0ubuntu1.11.10) (tested on oneiric). To manage notifications about this bug go to: https://bugs.launchpad.net/openjdk/+bug/913434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 913434]
I was able to reproduce this issue on Ubuntu's IcedTea 2.6.6 running: - the integrated lcms library (disable-system-lcms) - lcms 2.5 and 2.6 system library (enable-system-lcms) For some reason that I haven't been able to track down yet it does depend on the JPEG file under test - a initial sample I grabbed from the internet ran just fine, only when I tested it against bunch grabbed from `locate .jpg` was I able to reproduce it. I haven't tested it against 3.x, but OpenJDK 8u91 runs just fine when using the same lcms 2.6 so I would expect similar results. Let me know if hs_err and/or core files would be of any help, as well as running it against an upstream IcedTea build (Ubuntu does not patch anything related to lcms). Started a few testes after an Ubuntu user reported running into this issue (https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/913434). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lcms2 in Ubuntu. https://bugs.launchpad.net/bugs/913434 Title: ImageIO crashes (core dumped) while reading many image files Status in OpenJDK: Confirmed Status in lcms2 package in Ubuntu: Incomplete Status in openjdk-7 package in Ubuntu: Incomplete Bug description: Code that uses ImageIO.read() to read many image files (on my system: 270 files, totalling 522.9 MiB) crashes the JVM. ~~~ My system information: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 11.10 Release: 11.10 Codename: oneiric $ uname -a Linux dowah 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux $ javac -version javac 1.7.0_147 $ java -version java version "1.7.0_147-icedtea" ~~~ To reproduce the error: $ javac BugIIO.java $ ulimit -c unlimited # to enable core dump $ java BugIIO ~~~ Terminal output that signifies the error: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fb5babe31f8, pid=4978, tid=140418842154752 # # JRE version: 7.0_147-b147 # Java VM: OpenJDK 64-Bit Server VM (21.0-b17 mixed mode linux-amd64 compressed oops) # Derivative: IcedTea7 2.0 # Distribution: Ubuntu 11.10, package 7~b147-2.0-0ubuntu0.11.10.1 # Problematic frame: # C [liblcms2.so.2+0x121f8] cmsSaveProfileToIOhandler+0x38 # # Core dump written. Default location: /home/joshua/core or core.4978 # # An error report file with more information is saved as: # /home/joshua/hs_err_pid4978.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ # Dibatalkan (core didump) ~~~ PS When I tried to compile BugIIO.java on openjdk-6 and run it on openjdk-6, the program finishes normally (no crash). To clarify: 1. This bug affect OpenJDK 7 (7~b147-2.0-0ubuntu0.11.10.1) (tested on oneiric). 2. This bug does *not* affect OpenJDK 6 (6b23~pre11-0ubuntu1.11.10) (tested on oneiric). To manage notifications about this bug go to: https://bugs.launchpad.net/openjdk/+bug/913434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 913434]
Got together a bunch of images from the various hs_err I had at hand. I was unable to keep the file under 1 MB for upload, thus I uploaded it here: https://drive.google.com/open?id=0Bw-FF32TRkU3MFdFOXF4dlZ0c2s -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lcms2 in Ubuntu. https://bugs.launchpad.net/bugs/913434 Title: ImageIO crashes (core dumped) while reading many image files Status in OpenJDK: Confirmed Status in lcms2 package in Ubuntu: Incomplete Status in openjdk-7 package in Ubuntu: Incomplete Bug description: Code that uses ImageIO.read() to read many image files (on my system: 270 files, totalling 522.9 MiB) crashes the JVM. ~~~ My system information: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 11.10 Release: 11.10 Codename: oneiric $ uname -a Linux dowah 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux $ javac -version javac 1.7.0_147 $ java -version java version "1.7.0_147-icedtea" ~~~ To reproduce the error: $ javac BugIIO.java $ ulimit -c unlimited # to enable core dump $ java BugIIO ~~~ Terminal output that signifies the error: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fb5babe31f8, pid=4978, tid=140418842154752 # # JRE version: 7.0_147-b147 # Java VM: OpenJDK 64-Bit Server VM (21.0-b17 mixed mode linux-amd64 compressed oops) # Derivative: IcedTea7 2.0 # Distribution: Ubuntu 11.10, package 7~b147-2.0-0ubuntu0.11.10.1 # Problematic frame: # C [liblcms2.so.2+0x121f8] cmsSaveProfileToIOhandler+0x38 # # Core dump written. Default location: /home/joshua/core or core.4978 # # An error report file with more information is saved as: # /home/joshua/hs_err_pid4978.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ # Dibatalkan (core didump) ~~~ PS When I tried to compile BugIIO.java on openjdk-6 and run it on openjdk-6, the program finishes normally (no crash). To clarify: 1. This bug affect OpenJDK 7 (7~b147-2.0-0ubuntu0.11.10.1) (tested on oneiric). 2. This bug does *not* affect OpenJDK 6 (6b23~pre11-0ubuntu1.11.10) (tested on oneiric). To manage notifications about this bug go to: https://bugs.launchpad.net/openjdk/+bug/913434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 913434] Re: ImageIO crashes (core dumped) while reading many image files
I was unable to reproduce it yesterday, but it was due to the jpeg files I was using. I repeated it today with different jpeg files and reproduced it. Got a crash on OpenJDK 7u101 with both LCMS 2.5 (Trusty) and 2.6 (Wily), also reproduced when using the LCMS lib that comes with OpenJDK (by default Ubuntu uses the lib from lcms2-2 package). OpenJDK 8 on Wily uses the same LCMS and does not crash. I will report this upstream. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lcms2 in Ubuntu. https://bugs.launchpad.net/bugs/913434 Title: ImageIO crashes (core dumped) while reading many image files Status in OpenJDK: Fix Released Status in lcms2 package in Ubuntu: Incomplete Status in openjdk-7 package in Ubuntu: Incomplete Bug description: Code that uses ImageIO.read() to read many image files (on my system: 270 files, totalling 522.9 MiB) crashes the JVM. ~~~ My system information: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 11.10 Release: 11.10 Codename: oneiric $ uname -a Linux dowah 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux $ javac -version javac 1.7.0_147 $ java -version java version "1.7.0_147-icedtea" ~~~ To reproduce the error: $ javac BugIIO.java $ ulimit -c unlimited # to enable core dump $ java BugIIO ~~~ Terminal output that signifies the error: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fb5babe31f8, pid=4978, tid=140418842154752 # # JRE version: 7.0_147-b147 # Java VM: OpenJDK 64-Bit Server VM (21.0-b17 mixed mode linux-amd64 compressed oops) # Derivative: IcedTea7 2.0 # Distribution: Ubuntu 11.10, package 7~b147-2.0-0ubuntu0.11.10.1 # Problematic frame: # C [liblcms2.so.2+0x121f8] cmsSaveProfileToIOhandler+0x38 # # Core dump written. Default location: /home/joshua/core or core.4978 # # An error report file with more information is saved as: # /home/joshua/hs_err_pid4978.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ # Dibatalkan (core didump) ~~~ PS When I tried to compile BugIIO.java on openjdk-6 and run it on openjdk-6, the program finishes normally (no crash). To clarify: 1. This bug affect OpenJDK 7 (7~b147-2.0-0ubuntu0.11.10.1) (tested on oneiric). 2. This bug does *not* affect OpenJDK 6 (6b23~pre11-0ubuntu1.11.10) (tested on oneiric). To manage notifications about this bug go to: https://bugs.launchpad.net/openjdk/+bug/913434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 913434] Re: ImageIO crashes (core dumped) while reading many image files
Mauro, Thanks for the additional information. Your and IcedTea's reports seem to indicate that LCMS 2.5 is the culprit for not being thread safe. I will try to reproduce it later on so I can test if a newer version does indeed fix this issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lcms2 in Ubuntu. https://bugs.launchpad.net/bugs/913434 Title: ImageIO crashes (core dumped) while reading many image files Status in OpenJDK: Fix Released Status in lcms2 package in Ubuntu: Incomplete Status in openjdk-7 package in Ubuntu: Incomplete Bug description: Code that uses ImageIO.read() to read many image files (on my system: 270 files, totalling 522.9 MiB) crashes the JVM. ~~~ My system information: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 11.10 Release: 11.10 Codename: oneiric $ uname -a Linux dowah 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux $ javac -version javac 1.7.0_147 $ java -version java version "1.7.0_147-icedtea" ~~~ To reproduce the error: $ javac BugIIO.java $ ulimit -c unlimited # to enable core dump $ java BugIIO ~~~ Terminal output that signifies the error: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fb5babe31f8, pid=4978, tid=140418842154752 # # JRE version: 7.0_147-b147 # Java VM: OpenJDK 64-Bit Server VM (21.0-b17 mixed mode linux-amd64 compressed oops) # Derivative: IcedTea7 2.0 # Distribution: Ubuntu 11.10, package 7~b147-2.0-0ubuntu0.11.10.1 # Problematic frame: # C [liblcms2.so.2+0x121f8] cmsSaveProfileToIOhandler+0x38 # # Core dump written. Default location: /home/joshua/core or core.4978 # # An error report file with more information is saved as: # /home/joshua/hs_err_pid4978.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ # Dibatalkan (core didump) ~~~ PS When I tried to compile BugIIO.java on openjdk-6 and run it on openjdk-6, the program finishes normally (no crash). To clarify: 1. This bug affect OpenJDK 7 (7~b147-2.0-0ubuntu0.11.10.1) (tested on oneiric). 2. This bug does *not* affect OpenJDK 6 (6b23~pre11-0ubuntu1.11.10) (tested on oneiric). To manage notifications about this bug go to: https://bugs.launchpad.net/openjdk/+bug/913434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 913434] Re: ImageIO crashes (core dumped) while reading many image files
Mauro, Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: * Is this reproducible? * If so, what specific steps should we take to recreate this bug? * Does it affect OpenJDK 6 as well? Please post or attach the error output so we can verify it is actually the same bug. This will help us to find and resolve the problem. ** Changed in: lcms2 (Ubuntu) Status: Confirmed => Incomplete ** Changed in: openjdk-7 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lcms2 in Ubuntu. https://bugs.launchpad.net/bugs/913434 Title: ImageIO crashes (core dumped) while reading many image files Status in OpenJDK: Fix Released Status in lcms2 package in Ubuntu: Incomplete Status in openjdk-7 package in Ubuntu: Incomplete Bug description: Code that uses ImageIO.read() to read many image files (on my system: 270 files, totalling 522.9 MiB) crashes the JVM. ~~~ My system information: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 11.10 Release: 11.10 Codename: oneiric $ uname -a Linux dowah 3.0.0-14-generic #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux $ javac -version javac 1.7.0_147 $ java -version java version "1.7.0_147-icedtea" ~~~ To reproduce the error: $ javac BugIIO.java $ ulimit -c unlimited # to enable core dump $ java BugIIO ~~~ Terminal output that signifies the error: # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fb5babe31f8, pid=4978, tid=140418842154752 # # JRE version: 7.0_147-b147 # Java VM: OpenJDK 64-Bit Server VM (21.0-b17 mixed mode linux-amd64 compressed oops) # Derivative: IcedTea7 2.0 # Distribution: Ubuntu 11.10, package 7~b147-2.0-0ubuntu0.11.10.1 # Problematic frame: # C [liblcms2.so.2+0x121f8] cmsSaveProfileToIOhandler+0x38 # # Core dump written. Default location: /home/joshua/core or core.4978 # # An error report file with more information is saved as: # /home/joshua/hs_err_pid4978.log # # If you would like to submit a bug report, please include # instructions on how to reproduce the bug and visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-7/ # Dibatalkan (core didump) ~~~ PS When I tried to compile BugIIO.java on openjdk-6 and run it on openjdk-6, the program finishes normally (no crash). To clarify: 1. This bug affect OpenJDK 7 (7~b147-2.0-0ubuntu0.11.10.1) (tested on oneiric). 2. This bug does *not* affect OpenJDK 6 (6b23~pre11-0ubuntu1.11.10) (tested on oneiric). To manage notifications about this bug go to: https://bugs.launchpad.net/openjdk/+bug/913434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1373543] Re: package libatk-wrapper-java (not installed) failed to install/upgrade: dependency problems - leaving unconfigured
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running only once: apport-collect 1373543 and any other logs that are relevant for this particular issue. ** Changed in: java-atk-wrapper (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to java-atk-wrapper in Ubuntu. https://bugs.launchpad.net/bugs/1373543 Title: package libatk-wrapper-java (not installed) failed to install/upgrade: dependency problems - leaving unconfigured Status in java-atk-wrapper package in Ubuntu: Incomplete Bug description: I installed java 6. Then updated and later wantd to remoove it. I tried ubunte software centre first, then synaptic package manager. I encountered the wrapper problem and now can not reinstall or remove java 6. I can not install flash player as a result and i can no update anymore. Please help. ProblemType: Package DistroRelease: Ubuntu 12.04 Package: libatk-wrapper-java (not installed) ProcVersionSignature: Ubuntu 3.2.0-68.102-generic 3.2.62 Uname: Linux 3.2.0-68-generic i686 ApportVersion: 2.0.1-0ubuntu17.7 Architecture: i386 Date: Wed Sep 24 19:54:33 2014 DuplicateSignature: package:libatk-wrapper-java:(not installed):dependency problems - leaving unconfigured ErrorMessage: dependency problems - leaving unconfigured InstallationMedia: Xubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 (20140205.2) MarkForUpload: True SourcePackage: java-atk-wrapper Title: package libatk-wrapper-java (not installed) failed to install/upgrade: dependency problems - leaving unconfigured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/java-atk-wrapper/+bug/1373543/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 659309] Re: Firefox crashes on Fronter Platform
Thank you for taking the time to report this bug and helping to make Ubuntu better. The bug is set as fixed upstream but no changelog entry recorded that fix. Closing it as invalid. ** Changed in: openjdk-6 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/659309 Title: Firefox crashes on Fronter Platform Status in Iced Tea: Fix Released Status in firefox package in Ubuntu: Invalid Status in openjdk-6 package in Ubuntu: Invalid Status in Fedora: Unknown Bug description: Binary package hint: firefox Since I installed Maverick (2 days ago) everytime I want to use the Fronter Platform (some e-learning platform the University of Vienna uses) Firefox crashes. I allready tried to deinstall all Add-ons and I also deleted my ~/.mozilla folder to get rid of all settings. Nothing changes - Firefox crashes almost everytime I try to work on the platform. I'm not yet sure if other sites are affected aswell... ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.10+build1+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 Architecture: i386 Date: Tue Oct 12 17:53:38 2010 FirefoxPackages: firefox 3.6.10+build1+nobinonly-0ubuntu3 firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3 firefox-branding 3.6.10+build1+nobinonly-0ubuntu3 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcEnviron: LANG=de_AT.utf8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/icedtea/+bug/659309/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 751909] Re: Java Swing applications displayed with wrong name
** Changed in: openjdk-7 (Ubuntu) Status: Confirmed => Invalid ** Changed in: openjdk-6 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/751909 Title: Java Swing applications displayed with wrong name Status in BAMF: Fix Released Status in Unity: Fix Released Status in bamf package in Ubuntu: Fix Released Status in openjdk-6 package in Ubuntu: Invalid Status in openjdk-7 package in Ubuntu: Invalid Status in unity package in Ubuntu: Fix Released Bug description: Binary package hint: unity On launcher, all Java Swing applications are with wrong name. Their tooltip shows the Java class name, with the dots changed by hiphens. For example, Netbeans icon itself gets inactive after startup. Then an icon with a '?' shows up indicating "java-lang-Thread" on mouseover. -- Treviño: this issue is java related (affecting javaws apps as well) and it's caused by the fact that the Java apps doesn't correctly set the WM_CLASS X property on their windows. There was a bug for it (including a patch): http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6528430 The ubuntu java package should probably include it. A workaround to fix it is to use this window matching agent: https://github.com/jelmerk/window-matching-agent then you need to update the application .desktop file to change the Exec value including -javaagent:agent.jar= and adding StartupWMClass=. To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/751909/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 932274] Re: Regression: Unreadable menu bar with Ambiance theme in Java/Swing GTK L
** Bug watch added: Iced Tea Bugzilla #2757 http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=2757 ** Also affects: icedtea via http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=2757 Importance: Unknown Status: Unknown ** Changed in: openjdk-6 (Ubuntu) Assignee: (unassigned) => Tiago Stürmer Daitx (tdaitx) ** Changed in: openjdk-6 (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to light-themes in Ubuntu. https://bugs.launchpad.net/bugs/932274 Title: Regression: Unreadable menu bar with Ambiance theme in Java/Swing GTK L Status in Iced Tea: Unknown Status in light-themes: Invalid Status in OpenJDK: Fix Committed Status in light-themes package in Ubuntu: Invalid Status in openjdk-6 package in Ubuntu: In Progress Status in openjdk-7 package in Ubuntu: Invalid Bug description: Hi, I have a problem in netbeans (and other java applications) with Ambiance theme. The menu bar has a dark foreground color and the menu titles are unreadable. This problem didn't occur in Oneiric. To manage notifications about this bug go to: https://bugs.launchpad.net/icedtea/+bug/932274/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 932274] Re: Regression: Unreadable menu bar with Ambiance theme in Java/Swing GTK L
OpenJDK 7 has the fix since 7u45 was released - the actual fix came with IcedTea 2.4.0 [1]. Setting OpenJDK 7 bug report as invalid according to Ubuntu's bug status policy [2]. [1] http://blog.fuseyism.com/index.php/2013/06/10/icedtea-2-4-0-released/ [2] https://wiki.ubuntu.com/Bugs/Bug%20statuses ** Changed in: openjdk-7 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to light-themes in Ubuntu. https://bugs.launchpad.net/bugs/932274 Title: Regression: Unreadable menu bar with Ambiance theme in Java/Swing GTK L Status in light-themes: Invalid Status in OpenJDK: Fix Committed Status in light-themes package in Ubuntu: Invalid Status in openjdk-6 package in Ubuntu: Confirmed Status in openjdk-7 package in Ubuntu: Invalid Bug description: Hi, I have a problem in netbeans (and other java applications) with Ambiance theme. The menu bar has a dark foreground color and the menu titles are unreadable. This problem didn't occur in Oneiric. To manage notifications about this bug go to: https://bugs.launchpad.net/light-themes/+bug/932274/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1503450] [NEW] mesa FTBFS due to missing Requires in mirclient
Public bug reported:
mesa currently FTBFS due to a missing mirclient dependency during build
time.
Failed build at
https://launchpad.net/ubuntu/+source/mesa/11.0.2-1ubuntu2/+build/8082519
Build log:
===
/bin/bash ../../libtool --tag=CC --mode=compile gcc -DPACKAGE_NAME=\"Mesa\"
-DPACKAGE_TARNAME=\"mesa\" -DPACKAGE_VERSION=\"11.0.2\"
-DPACKAGE_STRING=\"Mesa\ 11.0.2\"
-DPACKAGE_BUGREPORT=\"https://bugs.freedesktop.org/enter_bug.cgi\?product=Mesa\;
-DPACKAGE_URL=\"\" -DPACKAGE=\"mesa\" -DVERSION=\"11.0.2\" -DSTDC_HEADERS=1
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DYYTEXT_POINTER=1
-DHAVE___BUILTIN_BSWAP32=1 -DHAVE___BUILTIN_BSWAP64=1 -DHAVE___BUILTIN_CLZ=1
-DHAVE___BUILTIN_CLZLL=1 -DHAVE___BUILTIN_CTZ=1 -DHAVE___BUILTIN_EXPECT=1
-DHAVE___BUILTIN_FFS=1 -DHAVE___BUILTIN_FFSLL=1 -DHAVE___BUILTIN_POPCOUNT=1
-DHAVE___BUILTIN_POPCOUNTLL=1 -DHAVE___BUILTIN_UNREACHABLE=1
-DHAVE_FUNC_ATTRIBUTE_CONST=1 -DHAVE_FUNC_ATTRIBUTE_FLATTEN=1
-DHAVE_FUNC_ATTRIBUTE_FORMAT=1 -DHAVE_FUNC_ATTRIBUTE_MALLOC=1
-DHAVE_FUNC_ATTRIBUTE_PACKED=1
-DHAVE_FUNC_ATTRIBUTE_PURE=1 -DHAVE_FUNC_ATTRIBUTE_UNUSED=1
-DHAVE_FUNC_ATTRIBUTE_WARN_UNUSED_RESULT=1 -DHAVE_DLADDR=1
-DHAVE_CLOCK_GETTIME=1 -DHAVE_PTHREAD=1 -I. -I../../../../src/egl
-D_FORTIFY_SOURCE=2 -I../../../../include -I../../../../src/egl/main
-I../../../../src/gbm/main -I../../../../src -D__STDC_LIMIT_MACROS
-D_GNU_SOURCE -DUSE_SSE41 -DNDEBUG -DTEXTURE_FLOAT_ENABLED -DUSE_X86_64_ASM
-DHAVE_XLOCALE_H -DHAVE_SYS_SYSCTL_H -DHAVE_STRTOF -DHAVE_MKOSTEMP
-DHAVE_DLOPEN -DHAVE_POSIX_MEMALIGN -DHAVE_LIBDRM -DGLX_USE_DRM -DHAVE_LIBUDEV
-DGLX_INDIRECT_RENDERING -DGLX_DIRECT_RENDERING -DGLX_USE_TLS -DHAVE_ALIAS
-DHAVE_DRI3 -DHAVE_MINCORE -DHAVE_LLVM=0x0306 -DMESA_LLVM_VERSION_PATCH=2
-fvisibility=hidden -I/usr/include/libdrm
-D_EGL_NATIVE_PLATFORM=_EGL_PLATFORM_X11 -DHAVE_X11_PLATFORM
-DHAVE_WAYLAND_PLATFORM -DHAVE_DRM_PLATFORM -DHAVE_MIR_PLATFORM
-I/usr/include/mirplatform -I/usr/include/mircommon -I../../../../src/loader
-I../../../../src/egl/drivers/dri2 -I../../../../src/
gbm/backends/dri -I../../../../src/egl/wayland/wayland-egl
-I../../../../src/egl/wayland/wayland-drm -I../../src/egl/wayland/wayland-drm
-DDEFAULT_DRIVER_DIR=\"/usr/lib/x86_64-linux-gnu/dri:\${ORIGIN}/dri:/usr/lib/dri\"
-D_EGL_BUILT_IN_DRIVER_DRI2 -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -Wall -Wall -std=c99
-Werror=implicit-function-declaration -Werror=missing-prototypes
-fno-strict-aliasing -fno-math-errno -fno-trapping-math -fno-builtin-memcmp
-MT main/eglfallbacks.lo -MD -MP -MF $depbase.Tpo -c -o main/eglfallbacks.lo
../../../../src/egl/main/eglfallbacks.c &&\
In file included from ../../../../src/egl/main/egldisplay.c:61:0:
/usr/include/mirplatform/mir_toolkit/mesa/native_display.h:22:38: fatal error:
mir_toolkit/client_types.h: No such file or directory
compilation terminated.
make[3]: *** [main/egldisplay.lo] Error 1
** Affects: mesa (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1503450
Title:
mesa FTBFS due to missing Requires in mirclient
Status in mesa package in Ubuntu:
New
Bug description:
mesa currently FTBFS due to a missing mirclient dependency during
build time.
Failed build at
https://launchpad.net/ubuntu/+source/mesa/11.0.2-1ubuntu2/+build/8082519
Build log:
===
/bin/bash ../../libtool --tag=CC --mode=compile gcc
-DPACKAGE_NAME=\"Mesa\" -DPACKAGE_TARNAME=\"mesa\" -DPACKAGE_VERSION=\"11.0.2\"
-DPACKAGE_STRING=\"Mesa\ 11.0.2\"
-DPACKAGE_BUGREPORT=\"https://bugs.freedesktop.org/enter_bug.cgi\?product=Mesa\;
-DPACKAGE_URL=\"\" -DPACKAGE=\"mesa\" -DVERSION=\"11.0.2\" -DSTDC_HEADERS=1
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DYYTEXT_POINTER=1
-DHAVE___BUILTIN_BSWAP32=1 -DHAVE___BUILTIN_BSWAP64=1 -DHAVE___BUILTIN_CLZ=1
-DHAVE___BUILTIN_CLZLL=1 -DHAVE___BUILTIN_CTZ=1 -DHAVE___BUILTIN_EXPECT=1
-DHAVE___BUILTIN_FFS=1 -DHAVE___BUILTIN_FFSLL=1 -DHAVE___BUILTIN_POPCOUNT=1
-DHAVE___BUILTIN_POPCOUNTLL=1 -DHAVE___BUILTIN_UNREACHABLE=1
-DHAVE_FUNC_ATTRIBUTE_CONST=1 -DHAVE_FUNC_ATTRIBUTE_FLATTEN=1
-DHAVE_FUNC_ATTRIBUTE_FORMAT=1 -DHAVE_FUNC_ATTRIBUTE_MALLOC=1
-DHAVE_FUNC_ATTRIBUTE_PACKED=
1 -DHAVE_FUNC_ATTRIBUTE_PURE=1 -DHAVE_FUNC_ATTRIBUTE_UNUSED=1
-DHAVE_FUNC_ATTRIBUTE_WARN_UNUSED_RESULT=1 -DHAVE_DLADDR=1
-DHAVE_CLOCK_GETTIME=1 -DHAVE_PTHREAD=1 -I. -I../../../../src/egl
-D_FORTIFY_SOURCE=2 -I../../../../include -I../../../../src/egl/main
-I../../../../src/gbm/main -I../../../../src
[Desktop-packages] [Bug 1503450] Re: mesa FTBFS due to missing Requires in mirclient
This patch adds "Requires: mirclient = @MIR_VERSION@" in
src/platforms/mesa/mir-client-platform-mesa-dev.pc.in
** Patch added: "mir patch: add "Requires: mirclient"
mir-client-platform-mesa-dev.pc.in"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1503450/+attachment/4486550/+files/add-mirclient-requires.patch
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1503450
Title:
mesa FTBFS due to missing Requires in mirclient
Status in Mir:
New
Status in mesa package in Ubuntu:
New
Bug description:
mesa currently FTBFS due to a missing mirclient dependency during
build time.
Failed build at
https://launchpad.net/ubuntu/+source/mesa/11.0.2-1ubuntu2/+build/8082519
Build log:
===
/bin/bash ../../libtool --tag=CC --mode=compile gcc
-DPACKAGE_NAME=\"Mesa\" -DPACKAGE_TARNAME=\"mesa\" -DPACKAGE_VERSION=\"11.0.2\"
-DPACKAGE_STRING=\"Mesa\ 11.0.2\"
-DPACKAGE_BUGREPORT=\"https://bugs.freedesktop.org/enter_bug.cgi\?product=Mesa\;
-DPACKAGE_URL=\"\" -DPACKAGE=\"mesa\" -DVERSION=\"11.0.2\" -DSTDC_HEADERS=1
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DYYTEXT_POINTER=1
-DHAVE___BUILTIN_BSWAP32=1 -DHAVE___BUILTIN_BSWAP64=1 -DHAVE___BUILTIN_CLZ=1
-DHAVE___BUILTIN_CLZLL=1 -DHAVE___BUILTIN_CTZ=1 -DHAVE___BUILTIN_EXPECT=1
-DHAVE___BUILTIN_FFS=1 -DHAVE___BUILTIN_FFSLL=1 -DHAVE___BUILTIN_POPCOUNT=1
-DHAVE___BUILTIN_POPCOUNTLL=1 -DHAVE___BUILTIN_UNREACHABLE=1
-DHAVE_FUNC_ATTRIBUTE_CONST=1 -DHAVE_FUNC_ATTRIBUTE_FLATTEN=1
-DHAVE_FUNC_ATTRIBUTE_FORMAT=1 -DHAVE_FUNC_ATTRIBUTE_MALLOC=1
-DHAVE_FUNC_ATTRIBUTE_PACKED=
1 -DHAVE_FUNC_ATTRIBUTE_PURE=1 -DHAVE_FUNC_ATTRIBUTE_UNUSED=1
-DHAVE_FUNC_ATTRIBUTE_WARN_UNUSED_RESULT=1 -DHAVE_DLADDR=1
-DHAVE_CLOCK_GETTIME=1 -DHAVE_PTHREAD=1 -I. -I../../../../src/egl
-D_FORTIFY_SOURCE=2 -I../../../../include -I../../../../src/egl/main
-I../../../../src/gbm/main -I../../../../src -D__STDC_LIMIT_MACROS
-D_GNU_SOURCE -DUSE_SSE41 -DNDEBUG -DTEXTURE_FLOAT_ENABLED -DUSE_X86_64_ASM
-DHAVE_XLOCALE_H -DHAVE_SYS_SYSCTL_H -DHAVE_STRTOF -DHAVE_MKOSTEMP
-DHAVE_DLOPEN -DHAVE_POSIX_MEMALIGN -DHAVE_LIBDRM -DGLX_USE_DRM -DHAVE_LIBUDEV
-DGLX_INDIRECT_RENDERING -DGLX_DIRECT_RENDERING -DGLX_USE_TLS -DHAVE_ALIAS
-DHAVE_DRI3 -DHAVE_MINCORE -DHAVE_LLVM=0x0306 -DMESA_LLVM_VERSION_PATCH=2
-fvisibility=hidden -I/usr/include/libdrm
-D_EGL_NATIVE_PLATFORM=_EGL_PLATFORM_X11 -DHAVE_X11_PLATFORM
-DHAVE_WAYLAND_PLATFORM -DHAVE_DRM_PLATFORM -DHAVE_MIR_PLATFORM
-I/usr/include/mirplatform -I/usr/include/mircommon -I../../../../src/loader
-I../../../../src/egl/drivers/dri2 -I../../../../sr
c/gbm/backends/dri -I../../../../src/egl/wayland/wayland-egl
-I../../../../src/egl/wayland/wayland-drm -I../../src/egl/wayland/wayland-drm
-DDEFAULT_DRIVER_DIR=\"/usr/lib/x86_64-linux-gnu/dri:\${ORIGIN}/dri:/usr/lib/dri\"
-D_EGL_BUILT_IN_DRIVER_DRI2 -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -Wall -Wall -std=c99
-Werror=implicit-function-declaration -Werror=missing-prototypes
-fno-strict-aliasing -fno-math-errno -fno-trapping-math -fno-builtin-memcmp
-MT main/eglfallbacks.lo -MD -MP -MF $depbase.Tpo -c -o main/eglfallbacks.lo
../../../../src/egl/main/eglfallbacks.c &&\
In file included from ../../../../src/egl/main/egldisplay.c:61:0:
/usr/include/mirplatform/mir_toolkit/mesa/native_display.h:22:38: fatal
error: mir_toolkit/client_types.h: No such file or directory
compilation terminated.
make[3]: *** [main/egldisplay.lo] Error 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1503450/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1503450] Re: mesa FTBFS due to missing Requires in mirclient
This patch forces autoconf to use mirclient in addition to mir-client-
platform-mesa-dev
** Also affects: mir
Importance: Undecided
Status: New
** Patch added: "force mirclient dependency"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1503450/+attachment/4486549/+files/mesa_11.0.2-1ubuntu3.debdiff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1503450
Title:
mesa FTBFS due to missing Requires in mirclient
Status in Mir:
New
Status in mesa package in Ubuntu:
New
Bug description:
mesa currently FTBFS due to a missing mirclient dependency during
build time.
Failed build at
https://launchpad.net/ubuntu/+source/mesa/11.0.2-1ubuntu2/+build/8082519
Build log:
===
/bin/bash ../../libtool --tag=CC --mode=compile gcc
-DPACKAGE_NAME=\"Mesa\" -DPACKAGE_TARNAME=\"mesa\" -DPACKAGE_VERSION=\"11.0.2\"
-DPACKAGE_STRING=\"Mesa\ 11.0.2\"
-DPACKAGE_BUGREPORT=\"https://bugs.freedesktop.org/enter_bug.cgi\?product=Mesa\;
-DPACKAGE_URL=\"\" -DPACKAGE=\"mesa\" -DVERSION=\"11.0.2\" -DSTDC_HEADERS=1
-DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1
-DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1
-DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DYYTEXT_POINTER=1
-DHAVE___BUILTIN_BSWAP32=1 -DHAVE___BUILTIN_BSWAP64=1 -DHAVE___BUILTIN_CLZ=1
-DHAVE___BUILTIN_CLZLL=1 -DHAVE___BUILTIN_CTZ=1 -DHAVE___BUILTIN_EXPECT=1
-DHAVE___BUILTIN_FFS=1 -DHAVE___BUILTIN_FFSLL=1 -DHAVE___BUILTIN_POPCOUNT=1
-DHAVE___BUILTIN_POPCOUNTLL=1 -DHAVE___BUILTIN_UNREACHABLE=1
-DHAVE_FUNC_ATTRIBUTE_CONST=1 -DHAVE_FUNC_ATTRIBUTE_FLATTEN=1
-DHAVE_FUNC_ATTRIBUTE_FORMAT=1 -DHAVE_FUNC_ATTRIBUTE_MALLOC=1
-DHAVE_FUNC_ATTRIBUTE_PACKED=
1 -DHAVE_FUNC_ATTRIBUTE_PURE=1 -DHAVE_FUNC_ATTRIBUTE_UNUSED=1
-DHAVE_FUNC_ATTRIBUTE_WARN_UNUSED_RESULT=1 -DHAVE_DLADDR=1
-DHAVE_CLOCK_GETTIME=1 -DHAVE_PTHREAD=1 -I. -I../../../../src/egl
-D_FORTIFY_SOURCE=2 -I../../../../include -I../../../../src/egl/main
-I../../../../src/gbm/main -I../../../../src -D__STDC_LIMIT_MACROS
-D_GNU_SOURCE -DUSE_SSE41 -DNDEBUG -DTEXTURE_FLOAT_ENABLED -DUSE_X86_64_ASM
-DHAVE_XLOCALE_H -DHAVE_SYS_SYSCTL_H -DHAVE_STRTOF -DHAVE_MKOSTEMP
-DHAVE_DLOPEN -DHAVE_POSIX_MEMALIGN -DHAVE_LIBDRM -DGLX_USE_DRM -DHAVE_LIBUDEV
-DGLX_INDIRECT_RENDERING -DGLX_DIRECT_RENDERING -DGLX_USE_TLS -DHAVE_ALIAS
-DHAVE_DRI3 -DHAVE_MINCORE -DHAVE_LLVM=0x0306 -DMESA_LLVM_VERSION_PATCH=2
-fvisibility=hidden -I/usr/include/libdrm
-D_EGL_NATIVE_PLATFORM=_EGL_PLATFORM_X11 -DHAVE_X11_PLATFORM
-DHAVE_WAYLAND_PLATFORM -DHAVE_DRM_PLATFORM -DHAVE_MIR_PLATFORM
-I/usr/include/mirplatform -I/usr/include/mircommon -I../../../../src/loader
-I../../../../src/egl/drivers/dri2 -I../../../../sr
c/gbm/backends/dri -I../../../../src/egl/wayland/wayland-egl
-I../../../../src/egl/wayland/wayland-drm -I../../src/egl/wayland/wayland-drm
-DDEFAULT_DRIVER_DIR=\"/usr/lib/x86_64-linux-gnu/dri:\${ORIGIN}/dri:/usr/lib/dri\"
-D_EGL_BUILT_IN_DRIVER_DRI2 -g -O2 -fstack-protector-strong -Wformat
-Werror=format-security -Wall -Wall -std=c99
-Werror=implicit-function-declaration -Werror=missing-prototypes
-fno-strict-aliasing -fno-math-errno -fno-trapping-math -fno-builtin-memcmp
-MT main/eglfallbacks.lo -MD -MP -MF $depbase.Tpo -c -o main/eglfallbacks.lo
../../../../src/egl/main/eglfallbacks.c &&\
In file included from ../../../../src/egl/main/egldisplay.c:61:0:
/usr/include/mirplatform/mir_toolkit/mesa/native_display.h:22:38: fatal
error: mir_toolkit/client_types.h: No such file or directory
compilation terminated.
make[3]: *** [main/egldisplay.lo] Error 1
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1503450/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
