[Desktop-packages] [Bug 2046971] [NEW] RM signon from noble
Public bug reported: signond was merged from Debian, making this signon a source package providing no binaries. Please kick it out ** Affects: signon (Ubuntu) Importance: Undecided Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/2046971 Title: RM signon from noble Status in signon package in Ubuntu: New Bug description: signond was merged from Debian, making this signon a source package providing no binaries. Please kick it out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/2046971/+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 2037527] Re: [Ffe] libwebp
Hello, it is needed for new libavif, as explained in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022001 Having the new version will make easier to build it with finally the sharpyuv functionality. That said, will be anyway autosync next time we open, so there should be plenty of time to fix it properly before 24.04. My idea was to ship in 23.10 to let users broadly test before next LTS. Not a big deal, I'll close this bug and let it sync for NANIMAL ** Bug watch added: Debian Bug tracker #1022001 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022001 ** Changed in: libwebp (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwebp in Ubuntu. https://bugs.launchpad.net/bugs/2037527 Title: [Ffe] libwebp Status in libwebp package in Ubuntu: Invalid Bug description: - 9/13/2023: version 1.3.2 This is a binary compatible release. * security fix for lossless decoder (chromium: #1479274, CVE-2023-4863) - 6/23/2023: version 1.3.1 This is a binary compatible release. * security fixes for lossless encoder (#603, chromium: #1420107, #1455619, CVE-2023-1999) * improve error reporting through WebPPicture error codes * fix upsampling for RGB565 and RGBA in NEON builds * img2webp: add -sharp_yuv & -near_lossless * Windows builds: - fix compatibility with clang-cl (#607) - improve Arm64 performance with cl.exe - add Arm64EC support * fix webp_js with emcc >= 3.1.27 (stack size change, #614) * CMake fixes (#592, #610, #612) * further updates to the container and lossless bitstream docs (#581, #611) - 12/16/2022: version 1.3.0 This is a binary compatible release. * add libsharpyuv, which exposes -sharp_yuv/config.use_sharp_yuv functionality to other libraries; libwebp now depends on this library * major updates to the container and lossless bitstream docs (#448, #546, #551) * miscellaneous warning, bug & build fixes (#576, #583, #584) Moreover the LP: #2013083 can be closed in this release. The non-bugfix changes are related to a new library added, that is used probably by firefox and chromium (next releases? or maybe they are using the embedded library) Changes since mantic version 1.2.4-0.3 == libwebp (1.3.2-0.3) unstable; urgency=medium * Non-maintainer upload. * Fix invalid incremental decoding check. (Closes: #1052447) * Fix next is invalid pointer when WebPSafeMalloc fails * Fix static analyzer warnings. -- Salvatore Bonaccorso Fri, 22 Sep 2023 09:41:18 +0200 libwebp (1.3.2-0.2) unstable; urgency=medium * Non-maintainer upload. * debian/control: Add missing dependency libwebp-dev => libsharpyuv-dev. (Closes: #1052355) -- Boyuan Yang Wed, 20 Sep 2023 15:59:13 -0400 libwebp (1.3.2-0.1) unstable; urgency=medium * Non-maintainer upload. * Upload to unstable. -- Boyuan Yang Wed, 20 Sep 2023 11:03:28 -0400 libwebp (1.3.2-0.1~exp2) experimental; urgency=medium * Non-maintainer upload. [ Gianfranco Costamagna ] * Also install .a files again. * Make sure we have built and installed anim_dump and anim_diff. (Closes: #1023482) -- Boyuan Yang Fri, 15 Sep 2023 14:41:40 -0400 libwebp (1.3.2-0.1~exp1) experimental; urgency=medium * Non-maintainer upload. * New upstream release 1.3.2. + The 1.3.x branch introduces libsharpyuv, which will be introduced as separate Debian binary packages. (Closes: #1040970) + CVE-2023-4863 is handled in this release. (LP: #2035220) * debian/gbp.conf: Use ignore-branch=True to avoid limitation on experimental branch. * debian/control: + Drop unnecessary build-dependency on autotools-related packages. + Add build-dependency on pkg-config. + Migrate buildsystem to cmake. (Closes: #1040972, LP: #2013083) + Apply RPATH-related hotfix before debhelper compat level 14. + Add new binary packages: libsharpyuv-dev, libsharpyuv0, libwebpdecoder3. * debian/libwebp-dev.install: Do not install static library anymore since CMake is not building them by default. * debian/rules: + Enforce --buildsystem=cmake. + Drop explicit option --enable-aligned, this option has been removed by libwebp upstream (see upstream ChangeLog). * debian/docs: Rename to libwebp-dev.docs to avoid confusion. * debian/patches: Drop all old patches, merged upstream. * debian/patches/: + 0001-CMakeLists.txt-Install-CMake-Config-to-arch-dep-loca.patch: Add patch to install CMake Config files to architecture-dependent location instead to retain Multi-Arch property of dev packages. * debian/copyright: Completely rewritten in machine-readable copyright format. -- Boyuan Yang Thu, 14
[Desktop-packages] [Bug 2013083] Re: libwebp-dev doesn't install CMake configs
This is fixed in Debian sid/testing, will be fixed for mantic if bug: 2037527 is accepted, or to 24.04 otherwise. Setting right now as fix released. ** Changed in: libwebp (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwebp in Ubuntu. https://bugs.launchpad.net/bugs/2013083 Title: libwebp-dev doesn't install CMake configs Status in libwebp package in Ubuntu: Fix Released Bug description: Libwebp source archive ships Cmake configs. Unlike vcpkg, the Ubuntu package doesn't install them. This prevents client applications from using the recommended find_package(WebP) functionality. Please install the CMake configs along with the pkg-config files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwebp/+bug/2013083/+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 2037527] [NEW] [Ffe] libwebp
Public bug reported: - 9/13/2023: version 1.3.2 This is a binary compatible release. * security fix for lossless decoder (chromium: #1479274, CVE-2023-4863) - 6/23/2023: version 1.3.1 This is a binary compatible release. * security fixes for lossless encoder (#603, chromium: #1420107, #1455619, CVE-2023-1999) * improve error reporting through WebPPicture error codes * fix upsampling for RGB565 and RGBA in NEON builds * img2webp: add -sharp_yuv & -near_lossless * Windows builds: - fix compatibility with clang-cl (#607) - improve Arm64 performance with cl.exe - add Arm64EC support * fix webp_js with emcc >= 3.1.27 (stack size change, #614) * CMake fixes (#592, #610, #612) * further updates to the container and lossless bitstream docs (#581, #611) - 12/16/2022: version 1.3.0 This is a binary compatible release. * add libsharpyuv, which exposes -sharp_yuv/config.use_sharp_yuv functionality to other libraries; libwebp now depends on this library * major updates to the container and lossless bitstream docs (#448, #546, #551) * miscellaneous warning, bug & build fixes (#576, #583, #584) Moreover the LP: #2013083 can be closed in this release. The non-bugfix changes are related to a new library added, that is used probably by firefox and chromium (next releases? or maybe they are using the embedded library) ** Affects: libwebp (Ubuntu) Importance: Undecided Assignee: Ubuntu Release Team (ubuntu-release) Status: New ** Changed in: libwebp (Ubuntu) Assignee: (unassigned) => Ubuntu Release Team (ubuntu-release) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwebp in Ubuntu. https://bugs.launchpad.net/bugs/2037527 Title: [Ffe] libwebp Status in libwebp package in Ubuntu: New Bug description: - 9/13/2023: version 1.3.2 This is a binary compatible release. * security fix for lossless decoder (chromium: #1479274, CVE-2023-4863) - 6/23/2023: version 1.3.1 This is a binary compatible release. * security fixes for lossless encoder (#603, chromium: #1420107, #1455619, CVE-2023-1999) * improve error reporting through WebPPicture error codes * fix upsampling for RGB565 and RGBA in NEON builds * img2webp: add -sharp_yuv & -near_lossless * Windows builds: - fix compatibility with clang-cl (#607) - improve Arm64 performance with cl.exe - add Arm64EC support * fix webp_js with emcc >= 3.1.27 (stack size change, #614) * CMake fixes (#592, #610, #612) * further updates to the container and lossless bitstream docs (#581, #611) - 12/16/2022: version 1.3.0 This is a binary compatible release. * add libsharpyuv, which exposes -sharp_yuv/config.use_sharp_yuv functionality to other libraries; libwebp now depends on this library * major updates to the container and lossless bitstream docs (#448, #546, #551) * miscellaneous warning, bug & build fixes (#576, #583, #584) Moreover the LP: #2013083 can be closed in this release. The non-bugfix changes are related to a new library added, that is used probably by firefox and chromium (next releases? or maybe they are using the embedded library) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwebp/+bug/2037527/+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 1212525] Re: Libraw package does not contain demosaic packs
Looks like fixed now ** Changed in: libraw (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libraw in Ubuntu. https://bugs.launchpad.net/bugs/1212525 Title: Libraw package does not contain demosaic packs Status in libraw package in Ubuntu: Fix Released Bug description: It would be useful to have libraw compiled with the demosaicing packs so that programs can have access to different demosaicing algorithms like AMaZE. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libraw/+bug/1212525/+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 2012305] Re: 2.39 opengles issue on armhf
** Changed in: webkit2gtk (Ubuntu) Status: New => Fix Released ** Bug watch added: Debian Bug tracker #1033230 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033230 ** Also affects: webkit via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033230 Importance: Unknown Status: Unknown ** No longer affects: webkit ** Also affects: webkit2gtk (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033230 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/2012305 Title: 2.39 opengles issue on armhf Status in webkit2gtk package in Ubuntu: Fix Released Status in webkit2gtk package in Debian: Unknown Bug description: Reported also to Debian on https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=1033230 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/2012305/+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 1997338] [NEW] libatk-bridge2.0-0 uninstallable on i386
Public bug reported: https://autopkgtest.ubuntu.com/results/autopkgtest- lunar/lunar/i386/v/vlc/20221121_104906_b4207@/log.gz Starting pkgProblemResolver with broken count: 9 Starting 2 pkgProblemResolver with broken count: 9 Investigating (0) libvlccore9:i386 < none -> 3.0.17.4-5 @un puN Ib > Broken libvlccore9:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libvlccore9:i386 32 Considering libdbus-1-3:i386 0 as a solution to libvlccore9:i386 32 Investigating (0) libqt5dbus5:i386 < none -> 5.15.6+dfsg-1 @un puN Ib > Broken libqt5dbus5:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libqt5dbus5:i386 4 Considering libdbus-1-3:i386 0 as a solution to libqt5dbus5:i386 4 Investigating (0) libpulse0:i386 < none -> 1:16.1+dfsg1-1ubuntu3 @un puN Ib > Broken libpulse0:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libpulse0:i386 4 Considering libdbus-1-3:i386 0 as a solution to libpulse0:i386 4 Investigating (0) libavahi-client3:i386 < none -> 0.8-6ubuntu1 @un puN Ib > Broken libavahi-client3:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libavahi-client3:i386 2 Considering libdbus-1-3:i386 0 as a solution to libavahi-client3:i386 2 Investigating (0) libatspi2.0-0:i386 < none -> 2.46.0-3 @un puN Ib > Broken libatspi2.0-0:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libatspi2.0-0:i386 0 Considering libdbus-1-3:i386 0 as a solution to libatspi2.0-0:i386 0 Investigating (0) vlc-plugin-base:i386 < none -> 3.0.17.4-5 @un puN Ib > Broken vlc-plugin-base:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to vlc-plugin-base:i386 0 Considering libdbus-1-3:i386 0 as a solution to vlc-plugin-base:i386 0 Investigating (0) libfluidsynth3:i386 < none -> 2.2.8-1 @un puN Ib > Broken libfluidsynth3:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libfluidsynth3:i386 0 Considering libdbus-1-3:i386 0 as a solution to libfluidsynth3:i386 0 Investigating (0) libatk-bridge2.0-0:i386 < none -> 2.46.0-3 @un puN Ib > Broken libatk-bridge2.0-0:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering libdbus-1-3:i386 0 as a solution to libatk-bridge2.0-0:i386 0 Considering libdbus-1-3:i386 0 as a solution to libatk-bridge2.0-0:i386 0 Investigating (0) libdebuginfod1:i386 < none -> 0.187-4 @un puN Ib > Broken libdebuginfod1:i386 Depends on libcurl3-gnutls:i386 < none | 7.85.0-1 @un uH > (>= 7.28.0) Considering libcurl3-gnutls:i386 0 as a solution to libdebuginfod1:i386 0 Considering libcurl3-gnutls:i386 0 as a solution to libdebuginfod1:i386 0 Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libatk-bridge2.0-0:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed libatspi2.0-0:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed libavahi-client3:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed libdebuginfod1:i386 : Depends: libcurl3-gnutls:i386 (>= 7.28.0) but it is not going to be installed libfluidsynth3:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed libpulse0:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed libqt5dbus5:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed libvlccore9:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed vlc-plugin-base:i386 : Depends: libdbus-1-3:i386 (>= 1.9.14) but it is not going to be installed E: Unable to correct problems, you have held broken packages. autopkgtest: WARNING: Test dependencies are unsatisfiable - calling apt install on test deps directly for further data about failing dependencies in test logs Note, using file '/tmp/autopkgtest.8eagGS/3-autopkgtest-satdep.dsc' to get the build dependencies Reading package lists... Building dependency tree... Reading state information... Starting pkgProblemResolver with broken count: 9 Starting 2 pkgProblemResolver with broken count: 9 Investigating (0) libvlccore9:i386 < none -> 3.0.17.4-5 @un puN Ib > Broken libvlccore9:i386 Depends on libdbus-1-3:i386 < none | 1.14.0-2ubuntu2 @un uH > (>= 1.9.14) Considering
[Desktop-packages] [Bug 1993800] Re: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2>
Fix uploaded in Debian, will be syncd in some hours. ** Changed in: llvm-toolchain-15 (Ubuntu) Status: Confirmed => Fix Released ** Changed in: mesa (Ubuntu) Status: Confirmed => Fix Released -- 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/1993800 Title: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2> Status in LLVM: Fix Released Status in llvm-toolchain-15 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in llvm-toolchain-15 package in openSUSE: Unknown Bug description: LLVM ERROR: Cannot select: 0x2f689c8: v4i32 = ARMISD::VCMPZ 0x2f696b8, Constant:i32<2> 0x2f696b8: v4i32,ch = ARMISD::VLD1DUP<(load (s32) from %ir.212)> 0x2aad434, 0x2f84090:1, Constant:i32<4> 0x2f84090: i32,i32,ch = load<(load (s32) from %ir.209, align 8), > 0x2aad434, 0x2f63a30, Constant:i32<64> 0x2f63a30: i32,ch = CopyFromReg 0x2aad434, Register:i32 %23 0x2f51c10: i32 = Register %23 0x2f82500: i32 = Constant<64> 0x2f81b28: i32 = Constant<4> 0x2f81e40: i32 = Constant<2> In function: fs_variant_partial [https://launchpadlibrarian.net/629171689/buildlog_ubuntu-kinetic- armhf.mutter_43.0-1ubuntu3_BUILDING.txt.gz] Although "LLVM ERROR: Cannot select" seems to be from LLVM, I can't determine what project "fs_variant_partial" is in. Sounds like it might be in some old version of Mesa? The start of the log suggests it's running on focal. To manage notifications about this bug go to: https://bugs.launchpad.net/llvm/+bug/1993800/+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 1990804] Re: package cmake-data 3.22.1-1ubuntu1.22.04.1 failed to install/upgrade: installed cmake-data package post-installation script subprocess returned error exit status 1
** Changed in: emacsen-common (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacsen-common in Ubuntu. https://bugs.launchpad.net/bugs/1990804 Title: package cmake-data 3.22.1-1ubuntu1.22.04.1 failed to install/upgrade: installed cmake-data package post-installation script subprocess returned error exit status 1 Status in emacsen-common package in Ubuntu: Incomplete Bug description: Routine update failure whilst using Ubuntu software updater ProblemType: Package DistroRelease: Ubuntu 22.04 Package: cmake-data 3.22.1-1ubuntu1.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Sep 26 13:41:02 2022 Dependencies: dh-elpa-helper 2.0.9ubuntu1 emacsen-common 3.0.4 ErrorMessage: installed cmake-data package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-09-08 (17 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: cmake Title: package cmake-data 3.22.1-1ubuntu1.22.04.1 failed to install/upgrade: installed cmake-data package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacsen-common/+bug/1990804/+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 1990804] Re: package cmake-data 3.22.1-1ubuntu1.22.04.1 failed to install/upgrade: installed cmake-data package post-installation script subprocess returned error exit status 1
Setting up cmake-data (3.22.1-1ubuntu1.22.04.1) ... Install emacsen-common for emacs emacsen-common: Handling install of emacsen flavor emacs /usr/lib/emacsen-common/packages/install/emacsen-common: 17: emacs: not found ERROR: install script from emacsen-common package failed dpkg: error processing package cmake-data (--configure): installed cmake-data package post-installation script subprocess returned error exit status 1 looks more an emacsen-common failure? ** Package changed: cmake (Ubuntu) => emacsen-common (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacsen-common in Ubuntu. https://bugs.launchpad.net/bugs/1990804 Title: package cmake-data 3.22.1-1ubuntu1.22.04.1 failed to install/upgrade: installed cmake-data package post-installation script subprocess returned error exit status 1 Status in emacsen-common package in Ubuntu: New Bug description: Routine update failure whilst using Ubuntu software updater ProblemType: Package DistroRelease: Ubuntu 22.04 Package: cmake-data 3.22.1-1ubuntu1.22.04.1 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Sep 26 13:41:02 2022 Dependencies: dh-elpa-helper 2.0.9ubuntu1 emacsen-common 3.0.4 ErrorMessage: installed cmake-data package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-09-08 (17 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) PackageArchitecture: all Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.7 SourcePackage: cmake Title: package cmake-data 3.22.1-1ubuntu1.22.04.1 failed to install/upgrade: installed cmake-data package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacsen-common/+bug/1990804/+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 1974198] Re: Please merge pipewire 0.3.51-1 (main) from Debian unstable
Hello Nathan, thanks for your nice contribution, however I did the merge by myself and didn't see this bug, not sure why. I'm reuploading with the changelog from you, so you get the contribution credits and I'm closing this bug as "done" Some nitpicks on your delta: - trailing newline on last changelog entry (this is a bug in MoM I know, I usually remove it by hand) - you changed libpulse-dev -> to libpulse-dev (>= 11.1) this was changed from Debian and was making MoM fail with a conflict. Next time, before re instantiating it, check if it is part of Ubuntu delta or not, and try to fix the "merge" manually. In this case taking the control file from Debian and deleting one line was sufficient to have a clean-enough merge, specially because its already satisfied since bionic libpulse-dev | 1:11.1-1ubuntu7 | bionic | amd64, arm64, armhf, i386, ppc64el, s390x libpulse-dev | 1:11.1-1ubuntu7.11 | bionic-security | amd64, arm64, armhf, i386, ppc64el, s390x libpulse-dev | 1:11.1-1ubuntu7.11 | bionic-updates | amd64, arm64, armhf, i386, ppc64el, s390x libpulse-dev | 1:13.99.1-1ubuntu3 | focal | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x libpulse-dev | 1:13.99.1-1ubuntu3.8 | focal-security | amd64, arm64, armhf, i386, ppc64el, s390x libpulse-dev | 1:13.99.1-1ubuntu3.13| focal-updates | amd64, arm64, armhf, i386, ppc64el, s390x libpulse-dev | 1:15.0+dfsg1-1ubuntu2| impish | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x libpulse-dev | 1:15.0+dfsg1-1ubuntu2.1 | impish-updates | riscv64 libpulse-dev | 1:15.0+dfsg1-1ubuntu2.2 | impish-updates | amd64, arm64, armhf, i386, ppc64el, s390x libpulse-dev | 1:15.99.1+dfsg1-1ubuntu1 | jammy | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x libpulse-dev | 1:15.99.1+dfsg1-1ubuntu1 | kinetic | amd64, arm64, armhf, i386, ppc64el, riscv64, s390x ** Changed in: pipewire (Ubuntu) Status: Confirmed => Does Not Exist ** Changed in: pipewire (Ubuntu) Status: Does Not Exist => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pipewire in Ubuntu. https://bugs.launchpad.net/bugs/1974198 Title: Please merge pipewire 0.3.51-1 (main) from Debian unstable Status in pipewire package in Ubuntu: Fix Released Bug description: Please merge pipewire 0.3.51-1 from Debian unstable. Built successfully with pbuilder build. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pipewire/+bug/1974198/+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 1446133] Re: package libspeexdsp1:amd64 1.2~rc1.1-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting co
should be ok now ** Changed in: speex (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speex in Ubuntu. https://bugs.launchpad.net/bugs/1446133 Title: package libspeexdsp1:amd64 1.2~rc1.1-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in speex package in Ubuntu: Fix Released Bug description: Problem occurred during update ProblemType: Package DistroRelease: Ubuntu 14.10 Package: libspeexdsp1:amd64 1.2~rc1.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-34.47-generic 3.16.7-ckt8 Uname: Linux 3.16.0-34-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.4 Architecture: amd64 Date: Mon Apr 20 05:48:47 2015 Dependencies: gcc-4.9-base 4.9.1-16ubuntu6 libc6 2.19-10ubuntu2.3 libgcc1 1:4.9.1-16ubuntu6 multiarch-support 2.19-10ubuntu2.3 DuplicateSignature: package:libspeexdsp1:amd64:1.2~rc1.1-1ubuntu1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-04-03 (16 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) SourcePackage: speex Title: package libspeexdsp1:amd64 1.2~rc1.1-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speex/+bug/1446133/+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 1424903] Re: package libspeexdsp1:i386 1.2~rc1.1-1ubuntu1 failed to install/upgrade: package libspeexdsp1:i386 is already installed and configured
should be ok now ** Changed in: speex (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speex in Ubuntu. https://bugs.launchpad.net/bugs/1424903 Title: package libspeexdsp1:i386 1.2~rc1.1-1ubuntu1 failed to install/upgrade: package libspeexdsp1:i386 is already installed and configured Status in speex package in Ubuntu: Fix Released Bug description: I was trying to install the app called Wine, then the Ubuntu Software Center crashes ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libspeexdsp1:i386 1.2~rc1.1-1ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 AptdaemonVersion: 1.1.1-1ubuntu5.1 Architecture: amd64 Date: Mon Feb 23 21:00:33 2015 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.19-0ubuntu6.5 libgcc1 1:4.9.1-0ubuntu1 multiarch-support 2.19-0ubuntu6.5 DuplicateSignature: package:libspeexdsp1:i386:1.2~rc1.1-1ubuntu1:package libspeexdsp1:i386 is already installed and configured ErrorMessage: package libspeexdsp1:i386 is already installed and configured InstallationDate: Installed on 2015-02-23 (0 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) PackageArchitecture: i386 SourcePackage: speex Title: package libspeexdsp1:i386 1.2~rc1.1-1ubuntu1 failed to install/upgrade: package libspeexdsp1:i386 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speex/+bug/1424903/+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 1841783] Re: Update to 1.2.0?
** Changed in: speex (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to speex in Ubuntu. https://bugs.launchpad.net/bugs/1841783 Title: Update to 1.2.0? Status in speex package in Ubuntu: Fix Released Status in speex package in Debian: Fix Released Bug description: The source was split in rc2, Debian didn't follow the change, and we are in sync, do we want to update? Speex and SpeexDSP https://gitlab.xiph.org/xiph/speex https://gitlab.xiph.org/xiph/speexdsp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speex/+bug/1841783/+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 1780680] Re: Older version in bionic than in xenial
** Changed in: fuse-umfuse-ext2 (Ubuntu) Status: New => Fix Released -- 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/1780680 Title: Older version in bionic than in xenial Status in fuse-umfuse-ext2 package in Ubuntu: Fix Released Status in libclc package in Ubuntu: Won't Fix Status in libdrm package in Ubuntu: Won't Fix Status in linux-meta-azure package in Ubuntu: Fix Released Status in linux-meta-gcp package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Won't Fix Status in patch package in Ubuntu: Invalid Status in python-pyvmomi package in Ubuntu: Invalid Status in snapcraft package in Ubuntu: Fix Released Status in wireless-regdb package in Ubuntu: Fix Released Bug description: These packages have an older version in artful than in xenial. fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1 libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1 libdrm 2.4.83-1 < 2.4.91-2~16.04.1 mesa 17.2.8-0ubuntu0~17.10.1 < 18.0.5-0ubuntu0~16.04.1 patch 2.7.5-1ubuntu0.2 < 2.7.5-1ubuntu0.16.04.1 python-pyvmomi 5.5.0-2014.1.1-3 < 6.5.0.2017.5-0ubuntu1~16.04.1 snapcraft 2.42+17.10 < 2.42.1 wireless-regdb 2016.06.10-0ubuntu1 < 2018.05.09-0ubuntu1~16.04.1 Some of these are older in bionic than in xenial too. Shouldn’t there be an automated check for this? (See also: bug 1780679, bug 1780681.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse-umfuse-ext2/+bug/1780680/+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 1919114] Re: not installable due libssh-4 dependency problem
Hello, looks like you are not using the correct libssh-4 from the archive. It might be providing a broken "Provides" field, and then not compatible with remmina. ** Changed in: remmina (Ubuntu) Status: New => Opinion ** Changed in: remmina (Ubuntu) Status: Opinion => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1919114 Title: not installable due libssh-4 dependency problem Status in remmina package in Ubuntu: Invalid Bug description: Ubuntu 18.04.5 LTS remmina 1.2.0-rcgit.29+dfsg-1ubuntu1.2 Version table: 1.2.0-rcgit.29+dfsg-1ubuntu1.2 500 500 http://at.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Package `apt install remmina` shows: The following packages have unmet dependencies: remmina : Depends: libssh-4 (>= 0.6.1) but it is not going to be installed But libssh-4 is already installed in version 0.9.5 (which is higher than 0.6.1) ii libssh-4:amd64 0.9.5-0ubuntu1~18.04.sav0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1919114/+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 1895134] Re: [Ffe] openexr
** Changed in: openexr (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to openexr in Ubuntu. https://bugs.launchpad.net/bugs/1895134 Title: [Ffe] openexr Status in openexr package in Ubuntu: Fix Released Bug description: Openexr in Ubuntu is dated 2018, and suffers from lots of bugs, fixed in the last two years by upstream. Also some security fixes have been added in the Ubuntu packaging, but they are now superseeded by the new upstream changes. The sync will bring the package again in a good shape, and I already prepared the transition in bileto, with no issues and no regressions in buildability. the changes between 2.3.0 and 2.5.3 are listed here https://github.com/AcademySoftwareFoundation/openexr/blob/master/CHANGES.md#version-240-september-19-2019 and the bileto/autopkgtests are here: https://bileto.ubuntu.com/#/ticket/4246 (note: kio-extras has a missing b-d in proposed pocket, unrelated to this) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openexr/+bug/1895134/+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 1897962] Re: Out of Memory Error with Brother DCP-J7720W
Hello, looks like the diff between groovy and focal releases is 425k lines of code changed, not something that is easily checkable for regressions, backports might be a really better area to cover this issue. As said by the Debian maintainer in the Debian bug report, this bug is not easily fixable, if not with a new release (however I didn't try to spot the change by looking at the git log) I would like to know if release team has a different opinion, because uploading the groovy one into focal might be a no-go ** Changed in: sane-backends (Ubuntu) Status: Confirmed => Fix Released ** Also affects: sane-backends (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: sane-backends (Ubuntu Focal) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1897962 Title: Out of Memory Error with Brother DCP-J7720W Status in sane-backends package in Ubuntu: Fix Released Status in sane-backends source package in Focal: New Bug description: Installed XSane from the repository but when I scan the viewer screen is blank and if I try to save I get "Error during save: out of memory" I believe that escl driver in 20.04 sane-backends is a problem and it is related to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962539 sane-backends 1.0.31 should be considered for focal-backports and that if possible, escl driver could be individually SRU (Stable release update) in focal-updates. ppa:sane-project/sane-git fixes the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1897962/+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 1895134] [NEW] [Ffe] openexr
Public bug reported: Openexr in Ubuntu is dated 2018, and suffers from lots of bugs, fixed in the last two years by upstream. Also some security fixes have been added in the Ubuntu packaging, but they are now superseeded by the new upstream changes. The sync will bring the package again in a good shape, and I already prepared the transition in bileto, with no issues and no regressions in buildability. the changes between 2.3.0 and 2.5.3 are listed here https://github.com/AcademySoftwareFoundation/openexr/blob/master/CHANGES.md#version-240-september-19-2019 and the bileto/autopkgtests are here: https://bileto.ubuntu.com/#/ticket/4246 (note: kio-extras has a missing b-d in proposed pocket, unrelated to this) ** Affects: openexr (Ubuntu) Importance: Undecided Assignee: Ubuntu Release Team (ubuntu-release) Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to openexr in Ubuntu. https://bugs.launchpad.net/bugs/1895134 Title: [Ffe] openexr Status in openexr package in Ubuntu: New Bug description: Openexr in Ubuntu is dated 2018, and suffers from lots of bugs, fixed in the last two years by upstream. Also some security fixes have been added in the Ubuntu packaging, but they are now superseeded by the new upstream changes. The sync will bring the package again in a good shape, and I already prepared the transition in bileto, with no issues and no regressions in buildability. the changes between 2.3.0 and 2.5.3 are listed here https://github.com/AcademySoftwareFoundation/openexr/blob/master/CHANGES.md#version-240-september-19-2019 and the bileto/autopkgtests are here: https://bileto.ubuntu.com/#/ticket/4246 (note: kio-extras has a missing b-d in proposed pocket, unrelated to this) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openexr/+bug/1895134/+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 1869513] Re: package openexr 2.3.0-6build1 failed to install/upgrade: installed openexr package post-installation script subprocess returned error exit status 1
might be fixed in updates and security pocket ** Changed in: openexr (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to openexr in Ubuntu. https://bugs.launchpad.net/bugs/1869513 Title: package openexr 2.3.0-6build1 failed to install/upgrade: installed openexr package post-installation script subprocess returned error exit status 1 Status in openexr package in Ubuntu: Fix Released Bug description: /usr/bin/ld: warning: libIlmImf-2_2.so.22, needed by /usr/local/lib/libopencv_imgcodecs.so, not found (try using -rpath or -rpath-link) /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::ChannelList::insert(char const*, Imf_2_2::Channel const&)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::hasChromaticities(Imf_2_2::Header const&)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::InputFile::readPixels(int, int)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::InputFile::setFrameBuffer(Imf_2_2::FrameBuffer const&)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::Header::channels() const' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::InputFile::InputFile(char const*, int)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::FrameBuffer::insert(char const*, Imf_2_2::Slice const&)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::chromaticities(Imf_2_2::Header const&)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::globalThreadCount()' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::InputFile::header() const' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::OutputFile::writePixels(int)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::Channel::Channel(Imf_2_2::PixelType, int, int, bool)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::FrameBuffer::begin()' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::Slice::Slice(Imf_2_2::PixelType, char*, unsigned long, unsigned long, int, int, double, bool, bool)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::OutputFile::setFrameBuffer(Imf_2_2::FrameBuffer const&)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::Header::dataWindow() const' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::Header::channels()' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::Header::~Header()' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::OutputFile::OutputFile(char const*, Imf_2_2::Header const&, int)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::ChannelList::findChannel(char const*) const' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::FrameBuffer::end()' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::Header::Header(int, int, float, Imath_2_2::Vec2 const&, float, Imf_2_2::LineOrder, Imf_2_2::Compression)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::Chromaticities::Chromaticities(Imath_2_2::Vec2 const&, Imath_2_2::Vec2 const&, Imath_2_2::Vec2 const&, Imath_2_2::Vec2 const&)' /usr/bin/ld: /usr/local/lib/libopencv_imgcodecs.so: undefined reference to `Imf_2_2::OutputFile::~OutputFile()' collect2: error: ld returned 1 exit status ProblemType: Package DistroRelease: Ubuntu 20.04 Package: openexr 2.3.0-6build1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 AptOrdering: NULL: ConfigurePending Architecture: amd64 Date: Fri Mar 27 15:58:19 2020 ErrorMessage: installed openexr package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-11-27 (121 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 2.0.1 SourcePackage: openexr Title: package openexr 2.3.0-6build1 failed to install/upgrade: installed openexr package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-03-26 (1 days ago) To manage notifications about this bug go to:
[Desktop-packages] [Bug 1891613] [NEW] libraspberrypi0 not installable
Public bug reported: dpkg: error processing archive /tmp/apt-dpkg-install-IzpqYj/460-libraspberrypi0_0~20200520+git2fe4ca3-0ubuntu1_armhf.deb (--unpack): trying to overwrite '/usr/lib/arm-linux-gnueabihf/libEGL.so', which is also in package libegl-dev:armhf 1.3.2-1 (mythtv fails to build on armhf) ^^ I uploaded a 2:31.0+fixes.20200323.9579662cdc-0ubuntu5 version without that libraspberrypi-dev [armhf] | hello dependency, so we can progress with x265 transition. Please have a look, and declare breaks/replaces or stop shipping that library! ** Affects: libglvnd (Ubuntu) Importance: Undecided Status: Invalid ** Affects: raspberrypi-userland (Ubuntu) Importance: High Assignee: Dave Jones (waveform) Status: Confirmed ** Changed in: raspberrypi-userland (Ubuntu) Status: New => Confirmed ** Changed in: raspberrypi-userland (Ubuntu) Importance: Undecided => High ** Changed in: raspberrypi-userland (Ubuntu) Assignee: (unassigned) => Dave Jones (waveform) ** Also affects: libglvnd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1891613 Title: libraspberrypi0 not installable Status in libglvnd package in Ubuntu: Invalid Status in raspberrypi-userland package in Ubuntu: Confirmed Bug description: dpkg: error processing archive /tmp/apt-dpkg-install-IzpqYj/460-libraspberrypi0_0~20200520+git2fe4ca3-0ubuntu1_armhf.deb (--unpack): trying to overwrite '/usr/lib/arm-linux-gnueabihf/libEGL.so', which is also in package libegl-dev:armhf 1.3.2-1 (mythtv fails to build on armhf) ^^ I uploaded a 2:31.0+fixes.20200323.9579662cdc-0ubuntu5 version without that libraspberrypi-dev [armhf] | hello dependency, so we can progress with x265 transition. Please have a look, and declare breaks/replaces or stop shipping that library! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1891613/+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 1882185] Re: Firefox 78 requires nodejs >= 10.21
Uploaded with some little changes, such as: - keep PYTHON=python2 exported in rules file (not sure if still needed, but better safe than sorry) - revert the node-acorn change in dependencies, it looks like not needed anymore since now acorn provides it correctly. -- 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/1882185 Title: Firefox 78 requires nodejs >= 10.21 Status in firefox package in Ubuntu: Triaged Status in nodejs package in Ubuntu: In Progress Bug description: Firefox 78 RC week starts at 22th June 2020 with a bumped nodejs requirement to 10.21 (https://bugzilla.mozilla.org/show_bug.cgi?id=1641863). https://hg.mozilla.org/releases/mozilla-beta/rev/2e5f70995d3a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1882185/+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 1881906] Re: [MIR] libnma
and it migrated! thanks! ** Changed in: libnma (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnma in Ubuntu. https://bugs.launchpad.net/bugs/1881906 Title: [MIR] libnma Status in libnma package in Ubuntu: Fix Released Bug description: * Availability The library was provided by network-manager-applet and split to be standalone upstream and in Debian, autosync failed since the new source takes over existing binaries so there is no build in Ubuntu yet * Rationale As described before, it's a split of an existing library to its own source. The applet is a legacy component while the library isn't. * Security No known security issues https://security-tracker.debian.org/tracker/source-package/libnma https://launchpad.net/ubuntu/+source/libnma/+cve * Quality assurance - desktop-packages is subscribed to the package - the library has a .symbols - no downstream reports, only one minor upstream one https://bugs.launchpad.net/ubuntu/+source/libnma https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libnma https://gitlab.gnome.org/GNOME/libnma/-/issues There is one test which is part of the build and working, no autopkgtest. That's not ideal but also not different from the current situation in network-manager-applet which is already in main * Dependencies The dependencies for the library are in main. * Standards compliance 4.5.0, using dh13, simple packaging * Maintenance Maintained in Debian by the utopia team https://salsa.debian.org/utopia-team/libnma To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnma/+bug/1881906/+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 1876882] Re: Backport packages for 18.04.5 HWE stack
Hello, this patch [1] based on
https://gitlab.freedesktop.org/mesa/mesa/-/commit/3dd299c3d5b88114894ec30d1fac85fba688201f
did the trick.
I'll add as part of my ongoing SRU request.
[1]
--- virtualbox-5.2.42-dfsg.orig/include/VBox/HostServices/glxext.h
+++ virtualbox-5.2.42-dfsg/include/VBox/HostServices/glxext.h
@@ -573,7 +573,7 @@ typedef GLXFBConfigSGIX ( * PFNGLXGETFBC
#ifdef GLX_GLXEXT_PROTOTYPES
extern GLXPbufferSGIX glXCreateGLXPbufferSGIX (Display *, GLXFBConfigSGIX,
unsigned int, unsigned int, int *);
extern void glXDestroyGLXPbufferSGIX (Display *, GLXPbufferSGIX);
-extern int glXQueryGLXPbufferSGIX (Display *, GLXPbufferSGIX, int, unsigned
int *);
+extern void glXQueryGLXPbufferSGIX (Display *, GLXPbufferSGIX, int, unsigned
int *);
extern void glXSelectEventSGIX (Display *, GLXDrawable, unsigned long);
extern void glXGetSelectedEventSGIX (Display *, GLXDrawable, unsigned long *);
#endif /* GLX_GLXEXT_PROTOTYPES */
--- virtualbox-5.2.42-dfsg.orig/src/VBox/Additions/common/crOpenGL/dri_glx.h
+++ virtualbox-5.2.42-dfsg/src/VBox/Additions/common/crOpenGL/dri_glx.h
@@ -111,7 +111,7 @@ extern DECLEXPORT(const char *) VBOXGLXT
extern DECLEXPORT(GLXPbufferSGIX) VBOXGLXTAG(glXCreateGLXPbufferSGIX)
(Display *dpy, GLXFBConfigSGIX config, unsigned int width, unsigned int
height, int *attrib_list);
-extern DECLEXPORT(int) VBOXGLXTAG(glXQueryGLXPbufferSGIX)
+extern DECLEXPORT(void) VBOXGLXTAG(glXQueryGLXPbufferSGIX)
(Display *dpy, GLXPbuffer pbuf, int attribute, unsigned int *value);
extern DECLEXPORT(GLXFBConfigSGIX *) VBOXGLXTAG(glXChooseFBConfigSGIX)
--- virtualbox-5.2.42-dfsg.orig/src/VBox/Additions/common/crOpenGL/glx.c
+++ virtualbox-5.2.42-dfsg/src/VBox/Additions/common/crOpenGL/glx.c
@@ -763,7 +763,7 @@ DECLEXPORT(void) VBOXGLXTAG(glXGetSelect
(void) mask;
}
-DECLEXPORT(int) VBOXGLXTAG(glXQueryGLXPbufferSGIX)(Display *dpy, GLXPbuffer
pbuf,
+DECLEXPORT(void) VBOXGLXTAG(glXQueryGLXPbufferSGIX)(Display *dpy, GLXPbuffer
pbuf,
int attribute, unsigned int
*value)
{
(void) dpy;
@@ -771,7 +771,7 @@ DECLEXPORT(int) VBOXGLXTAG(glXQueryGLXPb
(void) attribute;
(void) value;
crWarning("glXQueryGLXPbufferSGIX not implemented by Chromium");
-return 0;
+return;
}
DECLEXPORT(int) VBOXGLXTAG(glXGetFBConfigAttribSGIX)(Display *dpy,
GLXFBConfig config,
--
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/1876882
Title:
Backport packages for 18.04.5 HWE stack
Status in libclc package in Ubuntu:
Invalid
Status in libdrm package in Ubuntu:
Invalid
Status in llvm-toolchain-10 package in Ubuntu:
Invalid
Status in mesa package in Ubuntu:
Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
Invalid
Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu:
Invalid
Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu:
Invalid
Status in libclc source package in Bionic:
New
Status in libdrm source package in Bionic:
Fix Committed
Status in llvm-toolchain-10 source package in Bionic:
Fix Committed
Status in mesa source package in Bionic:
Fix Committed
Status in xorg-server-hwe-18.04 source package in Bionic:
Fix Committed
Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic:
Fix Committed
Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic:
Fix Committed
Bug description:
[Impact]
These are needed for 18.04.5 images.
[Test case]
Boot a daily image, see that it still has the necessary stack
installed and working.
Check upgrade from stock bionic.
[Regression potential]
libdrm: very minimal chance for regressions
llvm-10: a new package, no regression potential on it's own
libclc: more or less just adds support for new llvm
mesa: a new major release, but we'll pull the final stable release of
20.0.x series, so there shouldn't be any regressions left at that
point
xserver: a new point-release
xorg drivers: modest updates, if any
[Other info]
mesa and libclc will migrate to llvm-10 in a separate upload
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1876882/+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 1876882] Re: Backport packages for 18.04.5 HWE stack
Hello, this broke virtualbox builds. gcc -c -O2 -g -pipe -Wshadow -Wall -Wextra -Wno-missing-field-initializers -Wno-unused -Wno-trigraphs -fdiagnostics-show-option -Wno-unused-parameter -Wlogical-op -Wno-variadic-macros -Wno-long-long -Wunused-variable -Wunused-function -Wunused-label -Wunused-parameter -Wmissing-prototypes -Wstrict-prototypes -Wmissing-declarations -Werror-implicit-function-declaration -Wno-variadic-macros -O2 -mtune=generic -fno-omit-frame-pointer -fno-strict-aliasing -fvisibility=hidden -DVBOX_HAVE_VISIBILITY_HIDDEN -DRT_USE_VISIBILITY_DEFAULT -fPIC -Wno-overlength-strings -include /<>/include/iprt/linux/symvers.h -fno-stack-protector -m64 -I/<>/src/VBox/GuestHost/OpenGL/include -I/<>/out/obj/VBoxOGLgen -I/<>/out/obj/VBoxEGL/dtrace -I/<>/include -I/<>/out -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_REM -DVBOX_WITH_RAW_MODE -DRT_OS_LINUX -D_FILE_OFFSET_BITS=64 -DRT_ARCH_AMD64 -D__AMD64__ -DVBOX_WITH_DEBUGGER -DVBOX_WITH_HARDENING -DRTPATH_APP_PRIVATE=\"/usr/share/virtualbox\" -DRTPATH_APP_PRIVATE_ARCH=\"/usr/lib/virtualbox\" -DRTPATH_SHARED_LIBS=\"/usr/lib/virtualbox\" -DRTPATH_APP_DOCS=\"/usr/share/doc/virtualbox\" -DIN_RING3 -DVBOX_WITH_DTRACE -DVBOX_WITH_DTRACE_R3 -DIN_GUEST -DIN_GUEST_R3 -DIN_RT_R3 -DGC_ARCH_BITS=64 -DPIC -DVBOX_WITH_HGCM -DLOG_USE_C99 -DRT_WITHOUT_EXEC_ALLOC -DLinux=1 -D_GNU_SOURCE -Wp,-MD,/<>/out/obj/VBoxEGL/egl.o.dep -Wp,-MT,/<>/out/obj/VBoxEGL/egl.o -Wp,-MP -o /<>/out/obj/VBoxEGL/egl.o /<>/src/VBox/Additions/common/crOpenGL/egl.c In file included from /<>/src/VBox/Additions/common/crOpenGL/glx.c:32:0: /<>/src/VBox/Additions/common/crOpenGL/dri_glx.h:114:35: error: conflicting types for ‘glXQueryGLXPbufferSGIX’ extern DECLEXPORT(int) VBOXGLXTAG(glXQueryGLXPbufferSGIX) ^ /<>/src/VBox/Additions/common/crOpenGL/dri_glx.h:31:27: note: in definition of macro ‘VBOXGLXTAG’ #define VBOXGLXTAG(Func) Func ^~~~ In file included from /usr/include/GL/glx.h:328:0, from /<>/src/VBox/GuestHost/OpenGL/include/chromium.h:99, from /<>/src/VBox/Additions/common/crOpenGL/glx.c:26: /usr/include/GL/glxext.h:861:6: note: previous declaration of ‘glXQueryGLXPbufferSGIX’ was here void glXQueryGLXPbufferSGIX (Display *dpy, GLXPbufferSGIX pbuf, int attribute, unsigned int *value); ^~ kmk_builtin_append -n "/<>/out/obj/VBoxOGL/context.o.dep" "" "/<>/src/VBox/Additions/common/crOpenGL/context.c:" "" kBuild: Creating directory /<>/out/obj/pam_vbox/ kmk_builtin_mkdir -p -- /<>/out/obj/pam_vbox/ kBuild: Compiling pam_vbox - /<>/src/VBox/Additions/common/pam/pam_vbox.cpp => /<>/out/obj/pam_vbox/pam_vbox.o kmk_builtin_rm -f -- /<>/out/obj/pam_vbox/pam_vbox.o.dep /<>/out/obj/pam_vbox/pam_vbox.o g++ -c -O2 -g -pipe -pedantic -Wshadow -Wall -Wextra -Wno-missing-field-initializers -Wno-unused -Wno-trigraphs -fdiagnostics-show-option -Wno-unused-parameter -Wlogical-op -Wno-variadic-macros -Wno-long-long -Wunused-variable -Wunused-function -Wunused-label -Wunused-parameter -Wno-overloaded-virtual -Wno-variadic-macros -O2 -mtune=generic -fno-omit-frame-pointer -fno-strict-aliasing -fvisibility=hidden -DVBOX_HAVE_VISIBILITY_HIDDEN -DRT_USE_VISIBILITY_DEFAULT -fvisibility-inlines-hidden -fno-exceptions -fPIC -fno-exceptions -include /<>/include/iprt/linux/symvers.h -fno-stack-protector -m64 -I/<>/out/obj/pam_vbox/dtrace -I/<>/include -I/<>/out -DVBOX -DVBOX_OSE -DVBOX_WITH_64_BITS_GUESTS -DVBOX_WITH_REM -DVBOX_WITH_RAW_MODE -DRT_OS_LINUX -D_FILE_OFFSET_BITS=64 -DRT_ARCH_AMD64 -D__AMD64__ -DVBOX_WITH_DEBUGGER -DVBOX_WITH_HARDENING -DRTPATH_APP_PRIVATE=\"/usr/share/virtualbox\" -DRTPATH_APP_PRIVATE_ARCH=\"/usr/lib/virtualbox\" -DRTPATH_SHARED_LIBS=\"/usr/lib/virtualbox\" -DRTPATH_APP_DOCS=\"/usr/share/doc/virtualbox\" -DIN_RING3 -DVBOX_WITH_DTRACE -DVBOX_WITH_DTRACE_R3 -DIN_GUEST -DIN_GUEST_R3 -DIN_RT_R3 -DGC_ARCH_BITS=64 -DPIC -DLOG_TO_BACKDOOR -DVBOX_WITH_HGCM -DVBOX_WITH_GUEST_PROPS -DLOG_USE_C99 -DRT_WITHOUT_EXEC_ALLOC -Wp,-MD,/<>/out/obj/pam_vbox/pam_vbox.o.dep -Wp,-MT,/<>/out/obj/pam_vbox/pam_vbox.o -Wp,-MP -o /<>/out/obj/pam_vbox/pam_vbox.o /<>/src/VBox/Additions/common/pam/pam_vbox.cpp In file included from /<>/src/VBox/Additions/common/crOpenGL/glx.c:32:0: /<>/src/VBox/Additions/common/crOpenGL/glx.c:766:28: error: conflicting types for ‘glXQueryGLXPbufferSGIX’ DECLEXPORT(int) VBOXGLXTAG(glXQueryGLXPbufferSGIX)(Display *dpy, GLXPbuffer pbuf, ^ /<>/src/VBox/Additions/common/crOpenGL/dri_glx.h:31:27: note: in definition of macro ‘VBOXGLXTAG’ #define VBOXGLXTAG(Func) Func ^~~~ In file included from /usr/include/GL/glx.h:328:0, from /<>/src/VBox/GuestHost/OpenGL/include/chromium.h:99, from /<>/src/VBox/Additions/common/crOpenGL/glx.c:26: /usr/include/GL/glxext.h:861:6: note: previous declaration of
[Desktop-packages] [Bug 1881906] Re: [MIR] libnma
** Package changed: ubuntu => libnma (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnma in Ubuntu. https://bugs.launchpad.net/bugs/1881906 Title: [MIR] libnma Status in libnma package in Ubuntu: New Bug description: * Availability The library was provided by network-manager-applet and split to be standalone upstream and in Debian, autosync failed since the new source takes over existing binaries so there is no build in Ubuntu yet * Rationale As described before, it's a split of an existing library to its own source. The applet is a legacy component while the library isn't. * Security No known security issues https://security-tracker.debian.org/tracker/source-package/libnma https://launchpad.net/ubuntu/+source/libnma/+cve * Quality assurance - desktop-packages is subscribed to the package - the library has a .symbols - no downstream reports, only one minor upstream one https://bugs.launchpad.net/ubuntu/+source/libnma https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libnma https://gitlab.gnome.org/GNOME/libnma/-/issues There is one test which is part of the build and working, no autopkgtest. That's not ideal but also not different from the current situation in network-manager-applet which is already in main * Dependencies The dependencies for the library are in main. * Standards compliance 4.5.0, using dh13, simple packaging * Maintenance Maintained in Debian by the utopia team https://salsa.debian.org/utopia-team/libnma To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnma/+bug/1881906/+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 1863026] Re: Remove my_bool typedef workaround
mysql-ocaml patched. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to redland in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: Fix Released Status in asterisk package in Ubuntu: Fix Released Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: Fix Released Status in dballe package in Ubuntu: Fix Released Status in gambas3 package in Ubuntu: Fix Released Status in gearmand package in Ubuntu: Fix Released Status in gerbera package in Ubuntu: Fix Released Status in gnokii package in Ubuntu: Fix Released Status in gnunet package in Ubuntu: Fix Released Status in hoel package in Ubuntu: Fix Released Status in isc-kea package in Ubuntu: In Progress Status in jabberd2 package in Ubuntu: Fix Released Status in kannel package in Ubuntu: In Progress Status in libgda5 package in Ubuntu: In Progress Status in libodb-mysql package in Ubuntu: In Progress Status in lyricue package in Ubuntu: In Progress Status in motion package in Ubuntu: In Progress Status in mysql-8.0 package in Ubuntu: Fix Released Status in mysql-ocaml package in Ubuntu: In Progress Status in mysqltcl package in Ubuntu: In Progress Status in opendnssec package in Ubuntu: In Progress Status in opensmtpd-extras package in Ubuntu: In Progress Status in orthanc-mysql package in Ubuntu: In Progress Status in pike8.0 package in Ubuntu: In Progress Status in pvpgn package in Ubuntu: In Progress Status in qt4-x11 package in Ubuntu: In Progress Status in redland package in Ubuntu: In Progress Status in tango package in Ubuntu: In Progress Status in tntdb package in Ubuntu: In Progress Status in voms-mysql-plugin package in Ubuntu: In Progress Status in vtk7 package in Ubuntu: Fix Released Status in w1retap package in Ubuntu: In Progress Status in zoneminder package in Ubuntu: In Progress Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+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 1863026] Re: Remove my_bool typedef workaround
I did work on vtk7 because it failed (I syncd the Debian version). Please forward the patch... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to redland in Ubuntu. https://bugs.launchpad.net/bugs/1863026 Title: Remove my_bool typedef workaround Status in argus-clients package in Ubuntu: Fix Released Status in asterisk package in Ubuntu: Fix Released Status in clickhouse package in Ubuntu: In Progress Status in cppdb package in Ubuntu: Fix Released Status in dballe package in Ubuntu: Fix Released Status in gambas3 package in Ubuntu: Fix Released Status in gearmand package in Ubuntu: In Progress Status in gerbera package in Ubuntu: In Progress Status in gnokii package in Ubuntu: In Progress Status in gnunet package in Ubuntu: In Progress Status in hoel package in Ubuntu: In Progress Status in isc-kea package in Ubuntu: In Progress Status in jabberd2 package in Ubuntu: In Progress Status in kannel package in Ubuntu: In Progress Status in libgda5 package in Ubuntu: In Progress Status in libodb-mysql package in Ubuntu: In Progress Status in lyricue package in Ubuntu: In Progress Status in motion package in Ubuntu: In Progress Status in mysql-8.0 package in Ubuntu: In Progress Status in mysql-ocaml package in Ubuntu: In Progress Status in mysqltcl package in Ubuntu: In Progress Status in opendnssec package in Ubuntu: In Progress Status in opensmtpd-extras package in Ubuntu: In Progress Status in orthanc-mysql package in Ubuntu: In Progress Status in pike8.0 package in Ubuntu: In Progress Status in pvpgn package in Ubuntu: In Progress Status in qt4-x11 package in Ubuntu: In Progress Status in redland package in Ubuntu: In Progress Status in tango package in Ubuntu: In Progress Status in tntdb package in Ubuntu: In Progress Status in voms-mysql-plugin package in Ubuntu: In Progress Status in vtk7 package in Ubuntu: In Progress Status in w1retap package in Ubuntu: In Progress Status in zoneminder package in Ubuntu: In Progress Bug description: During the previous development cycle, when mysql 8 was introduced, too many reverse deps failed due to the my_bool removal. It was then decided to put that back in to let the reverse dependencies build again. Now we should try to drop it one more time, and instead fix the reverse dependencies. Either by updating them, if upstream fixed it, or reintroducing only this my_bool typedef in the reverse dependency itself, instead of in mysql as it's now. This bug will track these tasks: - remove my_bool workaround from Ubuntu's mysql 8 package - fix the build of the reverse dependencies, each one a task of this bug. PPA with test builds: https://launchpad.net/~ahasenack/+archive/ubuntu/mysql8-my-bool- removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/argus-clients/+bug/1863026/+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 1715931] Re: Update to exiv2 version 0.27
reuploaded thanks Rico! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1715931 Title: Update to exiv2 version 0.27 Status in exiv2 package in Ubuntu: Fix Committed Status in exiv2 source package in Focal: Fix Committed Status in exiv2 package in Debian: Fix Released Bug description: 0.26 was released in April http://www.exiv2.org/whatsnew.html "This release contains a large collection of new features, new lenses and bugfixes across all areas of Exiv2. " Presumably debian stretch freeze interfered with a prompter update Currently in debian exp here: https://packages.debian.org/experimental/exiv2 I was hoping to to get a new feature release of the very popular Digikam (5.7.0) into artful under a FFE, but that has bumped the minimum exiv2 build depend from 0.25 -> 0.26. If due to rdeps etc an update in artful turns out not to be possible, I would like to target this for early in 18.04 LTS cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1715931/+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 1715931] Re: Update to exiv2 version 0.27
I got tricked because the very same patch was applied on the function 10 lines above... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1715931 Title: Update to exiv2 version 0.27 Status in exiv2 package in Ubuntu: Fix Committed Status in exiv2 source package in Focal: Fix Committed Status in exiv2 package in Debian: Fix Released Bug description: 0.26 was released in April http://www.exiv2.org/whatsnew.html "This release contains a large collection of new features, new lenses and bugfixes across all areas of Exiv2. " Presumably debian stretch freeze interfered with a prompter update Currently in debian exp here: https://packages.debian.org/experimental/exiv2 I was hoping to to get a new feature release of the very popular Digikam (5.7.0) into artful under a FFE, but that has bumped the minimum exiv2 build depend from 0.25 -> 0.26. If due to rdeps etc an update in artful turns out not to be possible, I would like to target this for early in 18.04 LTS cycle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1715931/+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 1855993] Re: Navit FTBFS - cmake fix needed to work with newer pango
** Changed in: cmake (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1855993 Title: Navit FTBFS - cmake fix needed to work with newer pango Status in cmake package in Ubuntu: Fix Released Status in navit package in Ubuntu: Fix Released Status in pango1.0 package in Ubuntu: Won't Fix Bug description: ## Cmake ## A change in Pango [1] broke builds using GTK2 as the pango source will include hb.h but miss the proper include paths. A fix was brought up in [2] and should be added to cmake in Focal to allow things to build with the new pango. Focal currently is at cmake 3.15.4-1 and [3] is a backport of that change to the 3.15 series. Note: after that is resolved navit will need a no change rebuild to pick up libgpsd25 which got me initially to find this issue. [1]: https://gitlab.gnome.org/GNOME/pango/commit/a7b17aa2bad77c485943c860a20aedc2b2b115ff [2]: https://gitlab.kitware.com/cmake/cmake/issues/19531 [3]: https://gitlab.kitware.com/cmake/cmake/commit/e4b1b79abb2b6e1ad07d36d4734554972c9ce4a9 --- original report --- ## Navit ## In file included from /usr/include/pango-1.0/pango/pango-font.h:25, from /usr/include/pango-1.0/pango/pango-attributes.h:25, from /usr/include/pango-1.0/pango/pango.h:25, from /usr/include/gtk-2.0/gdk/gdktypes.h:37, from /usr/include/gtk-2.0/gdk/gdkscreen.h:32, from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:31, from /usr/include/gtk-2.0/gdk/gdk.h:32, from /usr/include/gtk-2.0/gtk/gtk.h:32, from /<>/navit-0.5.3+dfsg.1/navit/graphics/gtk_drawing_area/graphics_gtk_drawing_area.c:26: /usr/include/pango-1.0/pango/pango-coverage.h:28:10: fatal error: hb.h: No such file or directory 28 | #include | ^~ compilation terminated. In file included from /usr/include/pango-1.0/pango/pango-font.h:25, from /usr/include/pango-1.0/pango/pango-attributes.h:25, from /usr/include/pango-1.0/pango/pango.h:25, from /usr/include/gtk-2.0/gdk/gdktypes.h:37, from /usr/include/gtk-2.0/gdk/gdkscreen.h:32, from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:31, from /usr/include/gtk-2.0/gdk/gdk.h:32, from /usr/include/gtk-2.0/gtk/gtk.h:32, from /<>/navit-0.5.3+dfsg.1/navit/gui/gtk/datawindow.c:24: /usr/include/pango-1.0/pango/pango-coverage.h:28:10: fatal error: hb.h: No such file or directory 28 | #include | ^~ compilation terminated. These are from no change rebuilds needed for libgps25, but something else made them break. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cmake/+bug/1855993/+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 1841437] Re: Don't update to 1.3.5
I'm the TIL for the package, and I have already prepared a package that I'll upload after EOAN is released https://launchpad.net/~costamagnagianfranco/+archive/ubuntu/locutusofborg-ppa/+sourcepub/10612180/+listing-archive-extra Closing because I'm sure I'll forget about this one, and nobody should steal my merge anyway :) ** Changed in: remmina (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1841437 Title: Don't update to 1.3.5 Status in remmina package in Ubuntu: Fix Released Bug description: The new version is in Debian but includes new features, we would need a ffe if you want to update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1841437/+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 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish
and eoan, of course
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1731459
Title:
genesys_gl847 scanners produce a black band in scanned images on
Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish
Status in sane-backends:
Unknown
Status in sane-backends package in Ubuntu:
In Progress
Status in sane-backends source package in Bionic:
In Progress
Status in sane-backends source package in Disco:
In Progress
Status in sane-backends package in Debian:
Unknown
Bug description:
[Impact]
When using a Genesys GL847 scanner, the documents get disfigured by a
discolored bar. The proposed uploads should fix the issue. They are
available in this PPA:
https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends
[Test case]
1. Install the libsane (libsane1 in bionic), libsane-common
and sane-utils packages from {bionic,disco]-proposed.
2. Use an affected device to scan, and find that the issue is
no longer present.
[Regression risk]
Upstream commit, focused bug fix => low regression risk
[Original description]
On Windows it works but on my Ubuntu 17.10, 18.04 and 18.10 I see a
black band on scanned image. The scanner is Canon CanoScan LIDE100.
Libsane version is 1.0.27-1~experimental2ubuntu1
To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1731459/+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 1731459] Re: genesys_gl847 scanners produce a black band in scanned images on Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish
sponsored in bionic and disco, after removing "~ppa" from the changelog
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/1731459
Title:
genesys_gl847 scanners produce a black band in scanned images on
Ubuntu 17.10+, 18.04 LTS and 18.10 Cosmic cuttlefish
Status in sane-backends:
Unknown
Status in sane-backends package in Ubuntu:
In Progress
Status in sane-backends source package in Bionic:
In Progress
Status in sane-backends source package in Disco:
In Progress
Status in sane-backends package in Debian:
Unknown
Bug description:
[Impact]
When using a Genesys GL847 scanner, the documents get disfigured by a
discolored bar. The proposed uploads should fix the issue. They are
available in this PPA:
https://launchpad.net/~gunnarhj/+archive/ubuntu/sane-backends
[Test case]
1. Install the libsane (libsane1 in bionic), libsane-common
and sane-utils packages from {bionic,disco]-proposed.
2. Use an affected device to scan, and find that the issue is
no longer present.
[Regression risk]
Upstream commit, focused bug fix => low regression risk
[Original description]
On Windows it works but on my Ubuntu 17.10, 18.04 and 18.10 I see a
black band on scanned image. The scanner is Canon CanoScan LIDE100.
Libsane version is 1.0.27-1~experimental2ubuntu1
To manage notifications about this bug go to:
https://bugs.launchpad.net/sane-backends/+bug/1731459/+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
** Changed in: virtualbox-hwe (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in fonts-liberation2 package in Ubuntu: Fix Released Status in gatk-native-bindings package in Ubuntu: New Status in geogebra package in Ubuntu: New Status in gkl package in Ubuntu: New Status in htsjdk package in Ubuntu: New Status in jameica package in Ubuntu: New Status in jameica-datasource package in Ubuntu: New Status in jameica-util package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in libjogl2-java package in Ubuntu: Fix Released Status in libpdfbox-java package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in metro-policy package in Ubuntu: New Status in mongo-java-driver package in Ubuntu: New Status in octave package in Ubuntu: New Status in openhft-chronicle-threads package in Ubuntu: New Status in saaj package in Ubuntu: New Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Status in activemq source package in Bionic: Fix Released Status in afterburner.fx source package in Bionic: Fix Released Status in annotation-indexer source package in Bionic: Fix Released Status in apache-directory-server source package in Bionic: Fix Released Status in aspectj source package in Bionic: Fix Released Status in aspectj-maven-plugin source package in Bionic: Fix Released Status in batik source package in Bionic: Fix Released Status in bindex source package in Bionic: Fix Released Status in bridge-method-injector source package in Bionic: Fix Released Status in carrotsearch-hppc source package in Bionic: Fix Released Status in clojure source package in Bionic: Fix Released Status in clojure1.8 source package in Bionic: Fix Released Status in commons-httpclient source package in Bionic: Fix Released Status in dd-plist source package in Bionic: Fix Released Status in ecj source package in Bionic: Fix Released Status in eclipselink source package in Bionic: Fix Released Status in elki source package in Bionic: Fix Released Status in figtree source package in Bionic: Fix Released Status in fontawesomefx source package in Bionic: Fix Released Status in geogebra source package in Bionic: Fix Released Status in gettext source package in Bionic: Fix Released Status in gluegen2 source package in Bionic: Fix Released Status in gradle source package in Bionic: Fix Released Status in gradle-debian-helper source package in Bionic: Fix Released Status in groovy source package in Bionic: Fix Released Status in hikaricp source package in Bionic: Fix Released Status in hsqldb source package in Bionic: Fix Released Status in hsqldb1.8.0 source package in Bionic: Fix Released Status in insubstantial source package in Bionic: Fix Released Status in jabref source package in Bionic: Fix Released Status in jackson-core source package in Bionic: Fix Released Status in jackson-databind source package in Bionic: Fix Released Status in jackson-dataformat-xml source package in Bionic: Fix Released Status in jackson-module-jaxb-annotations source package in Bionic: Fix Released Status in java-common source package in Bionic: Fix Released Status in javafxsvg source package in Bionic: Fix Released Status in javamail source package in Bionic: Fix Released Status in javatools source package in Bionic: Fix Released Status in jboss-classfilewriter source package in Bionic: Fix Released Status in jboss-jdeparser2 source package in Bionic: Fix Released Status in jboss-modules source package in Bionic: Fix Released Status in jcommander source package in Bionic: Fix Released Status in jersey1 source package in Bionic: Fix Released Status in jftp source package in Bionic: Fix Released Status in jhove source package in Bionic: Fix Released Status in jmdns source package in Bionic: Fix Released Status in jnr-posix source package in Bionic: Fix Released Status in jruby source package in Bionic: Fix Released Status in jruby-openssl source package in Bionic: Fix Released Status in jtreg source package in Bionic: Fix Released Status in jts source package in Bionic: Fix Released Status in junit4 source package in Bionic: Fix Released Status in jxgrabkey source package in Bionic: Fix Released Status in jython source package in Bionic: Fix Released Status in libapache-poi-java source package in Bionic: Fix Released Status in libbtm-java source package in Bionic: Fix Released Status in
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
** No longer affects: virtualbox (Ubuntu Cosmic) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-liberation2 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 fonts-liberation2 package in Ubuntu: Fix Released Status in gatk-native-bindings package in Ubuntu: New Status in geogebra package in Ubuntu: New Status in gkl package in Ubuntu: New Status in htsjdk package in Ubuntu: New Status in jameica package in Ubuntu: New Status in jameica-datasource package in Ubuntu: New Status in jameica-util package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in libjogl2-java package in Ubuntu: Fix Released Status in libpdfbox-java package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in metro-policy package in Ubuntu: New Status in mongo-java-driver package in Ubuntu: New Status in octave package in Ubuntu: New Status in openhft-chronicle-threads package in Ubuntu: New Status in saaj package in Ubuntu: New Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: New Status in activemq source package in Bionic: Fix Released Status in afterburner.fx source package in Bionic: Fix Released Status in annotation-indexer source package in Bionic: Fix Released Status in apache-directory-server source package in Bionic: Fix Released Status in aspectj source package in Bionic: Fix Released Status in aspectj-maven-plugin source package in Bionic: Fix Released Status in batik source package in Bionic: Fix Released Status in bindex source package in Bionic: Fix Released Status in bridge-method-injector source package in Bionic: Fix Released Status in carrotsearch-hppc source package in Bionic: Fix Released Status in clojure source package in Bionic: Fix Released Status in clojure1.8 source package in Bionic: Fix Released Status in commons-httpclient source package in Bionic: Fix Released Status in dd-plist source package in Bionic: Fix Released Status in ecj source package in Bionic: Fix Released Status in eclipselink source package in Bionic: Fix Released Status in elki source package in Bionic: Fix Released Status in figtree source package in Bionic: Fix Released Status in fontawesomefx source package in Bionic: Fix Released Status in geogebra source package in Bionic: Fix Released Status in gettext source package in Bionic: Fix Released Status in gluegen2 source package in Bionic: Fix Released Status in gradle source package in Bionic: Fix Released Status in gradle-debian-helper source package in Bionic: Fix Released Status in groovy source package in Bionic: Fix Released Status in hikaricp source package in Bionic: Fix Released Status in hsqldb source package in Bionic: Fix Released Status in hsqldb1.8.0 source package in Bionic: Fix Released Status in insubstantial source package in Bionic: Fix Released Status in jabref source package in Bionic: Fix Released Status in jackson-core source package in Bionic: Fix Released Status in jackson-databind source package in Bionic: Fix Released Status in jackson-dataformat-xml source package in Bionic: Fix Released Status in jackson-module-jaxb-annotations source package in Bionic: Fix Released Status in java-common source package in Bionic: Fix Released Status in javafxsvg source package in Bionic: Fix Released Status in javamail source package in Bionic: Fix Released Status in javatools source package in Bionic: Fix Released Status in jboss-classfilewriter source package in Bionic: Fix Released Status in jboss-jdeparser2 source package in Bionic: Fix Released Status in jboss-modules source package in Bionic: Fix Released Status in jcommander source package in Bionic: Fix Released Status in jersey1 source package in Bionic: Fix Released Status in jftp source package in Bionic: Fix Released Status in jhove source package in Bionic: Fix Released Status in jmdns source package in Bionic: Fix Released Status in jnr-posix source package in Bionic: Fix Released Status in jruby source package in Bionic: Fix Released Status in jruby-openssl source package in Bionic: Fix Released Status in jtreg source package in Bionic: Fix Released Status in jts source package in Bionic: Fix Released Status in junit4 source package in Bionic: Fix Released Status in jxgrabkey source package in Bionic: Fix Released Status in jython source package in Bionic: Fix Released Status in libapache-poi-java source package in Bionic: Fix Released Status in libbtm-java source package in Bionic: Fix Released Status in libcommons-collections3-java source package
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
** No longer affects: virtualbox-hwe (Ubuntu Cosmic) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-liberation2 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 fonts-liberation2 package in Ubuntu: Fix Released Status in gatk-native-bindings package in Ubuntu: New Status in geogebra package in Ubuntu: New Status in gkl package in Ubuntu: New Status in htsjdk package in Ubuntu: New Status in jameica package in Ubuntu: New Status in jameica-datasource package in Ubuntu: New Status in jameica-util package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in libjogl2-java package in Ubuntu: Fix Released Status in libpdfbox-java package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in metro-policy package in Ubuntu: New Status in mongo-java-driver package in Ubuntu: New Status in octave package in Ubuntu: New Status in openhft-chronicle-threads package in Ubuntu: New Status in saaj package in Ubuntu: New Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: New Status in activemq source package in Bionic: Fix Released Status in afterburner.fx source package in Bionic: Fix Released Status in annotation-indexer source package in Bionic: Fix Released Status in apache-directory-server source package in Bionic: Fix Released Status in aspectj source package in Bionic: Fix Released Status in aspectj-maven-plugin source package in Bionic: Fix Released Status in batik source package in Bionic: Fix Released Status in bindex source package in Bionic: Fix Released Status in bridge-method-injector source package in Bionic: Fix Released Status in carrotsearch-hppc source package in Bionic: Fix Released Status in clojure source package in Bionic: Fix Released Status in clojure1.8 source package in Bionic: Fix Released Status in commons-httpclient source package in Bionic: Fix Released Status in dd-plist source package in Bionic: Fix Released Status in ecj source package in Bionic: Fix Released Status in eclipselink source package in Bionic: Fix Released Status in elki source package in Bionic: Fix Released Status in figtree source package in Bionic: Fix Released Status in fontawesomefx source package in Bionic: Fix Released Status in geogebra source package in Bionic: Fix Released Status in gettext source package in Bionic: Fix Released Status in gluegen2 source package in Bionic: Fix Released Status in gradle source package in Bionic: Fix Released Status in gradle-debian-helper source package in Bionic: Fix Released Status in groovy source package in Bionic: Fix Released Status in hikaricp source package in Bionic: Fix Released Status in hsqldb source package in Bionic: Fix Released Status in hsqldb1.8.0 source package in Bionic: Fix Released Status in insubstantial source package in Bionic: Fix Released Status in jabref source package in Bionic: Fix Released Status in jackson-core source package in Bionic: Fix Released Status in jackson-databind source package in Bionic: Fix Released Status in jackson-dataformat-xml source package in Bionic: Fix Released Status in jackson-module-jaxb-annotations source package in Bionic: Fix Released Status in java-common source package in Bionic: Fix Released Status in javafxsvg source package in Bionic: Fix Released Status in javamail source package in Bionic: Fix Released Status in javatools source package in Bionic: Fix Released Status in jboss-classfilewriter source package in Bionic: Fix Released Status in jboss-jdeparser2 source package in Bionic: Fix Released Status in jboss-modules source package in Bionic: Fix Released Status in jcommander source package in Bionic: Fix Released Status in jersey1 source package in Bionic: Fix Released Status in jftp source package in Bionic: Fix Released Status in jhove source package in Bionic: Fix Released Status in jmdns source package in Bionic: Fix Released Status in jnr-posix source package in Bionic: Fix Released Status in jruby source package in Bionic: Fix Released Status in jruby-openssl source package in Bionic: Fix Released Status in jtreg source package in Bionic: Fix Released Status in jts source package in Bionic: Fix Released Status in junit4 source package in Bionic: Fix Released Status in jxgrabkey source package in Bionic: Fix Released Status in jython source package in Bionic: Fix Released Status in libapache-poi-java source package in Bionic: Fix Released Status in libbtm-java source package in Bionic: Fix Released Status in libcommons-collections3-java source
[Desktop-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
** Changed in: virtualbox (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in fonts-liberation2 package in Ubuntu: Fix Released Status in gatk-native-bindings package in Ubuntu: New Status in geogebra package in Ubuntu: New Status in gkl package in Ubuntu: New Status in htsjdk package in Ubuntu: New Status in jameica package in Ubuntu: New Status in jameica-datasource package in Ubuntu: New Status in jameica-util package in Ubuntu: New Status in jasperreports package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in libjogl2-java package in Ubuntu: Fix Released Status in libpdfbox-java package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in metro-policy package in Ubuntu: New Status in mongo-java-driver package in Ubuntu: New Status in octave package in Ubuntu: New Status in openhft-chronicle-threads package in Ubuntu: New Status in saaj package in Ubuntu: New Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: New Status in activemq source package in Bionic: Fix Released Status in afterburner.fx source package in Bionic: Fix Released Status in annotation-indexer source package in Bionic: Fix Released Status in apache-directory-server source package in Bionic: Fix Released Status in aspectj source package in Bionic: Fix Released Status in aspectj-maven-plugin source package in Bionic: Fix Released Status in batik source package in Bionic: Fix Released Status in bindex source package in Bionic: Fix Released Status in bridge-method-injector source package in Bionic: Fix Released Status in carrotsearch-hppc source package in Bionic: Fix Released Status in clojure source package in Bionic: Fix Released Status in clojure1.8 source package in Bionic: Fix Released Status in commons-httpclient source package in Bionic: Fix Released Status in dd-plist source package in Bionic: Fix Released Status in ecj source package in Bionic: Fix Released Status in eclipselink source package in Bionic: Fix Released Status in elki source package in Bionic: Fix Released Status in figtree source package in Bionic: Fix Released Status in fontawesomefx source package in Bionic: Fix Released Status in geogebra source package in Bionic: Fix Released Status in gettext source package in Bionic: Fix Released Status in gluegen2 source package in Bionic: Fix Released Status in gradle source package in Bionic: Fix Released Status in gradle-debian-helper source package in Bionic: Fix Released Status in groovy source package in Bionic: Fix Released Status in hikaricp source package in Bionic: Fix Released Status in hsqldb source package in Bionic: Fix Released Status in hsqldb1.8.0 source package in Bionic: Fix Released Status in insubstantial source package in Bionic: Fix Released Status in jabref source package in Bionic: Fix Released Status in jackson-core source package in Bionic: Fix Released Status in jackson-databind source package in Bionic: Fix Released Status in jackson-dataformat-xml source package in Bionic: Fix Released Status in jackson-module-jaxb-annotations source package in Bionic: Fix Released Status in java-common source package in Bionic: Fix Released Status in javafxsvg source package in Bionic: Fix Released Status in javamail source package in Bionic: Fix Released Status in javatools source package in Bionic: Fix Released Status in jboss-classfilewriter source package in Bionic: Fix Released Status in jboss-jdeparser2 source package in Bionic: Fix Released Status in jboss-modules source package in Bionic: Fix Released Status in jcommander source package in Bionic: Fix Released Status in jersey1 source package in Bionic: Fix Released Status in jftp source package in Bionic: Fix Released Status in jhove source package in Bionic: Fix Released Status in jmdns source package in Bionic: Fix Released Status in jnr-posix source package in Bionic: Fix Released Status in jruby source package in Bionic: Fix Released Status in jruby-openssl source package in Bionic: Fix Released Status in jtreg source package in Bionic: Fix Released Status in jts source package in Bionic: Fix Released Status in junit4 source package in Bionic: Fix Released Status in jxgrabkey source package in Bionic: Fix Released Status in jython source package in Bionic: Fix Released Status in libapache-poi-java source package in Bionic: Fix Released Status in libbtm-java source package in Bionic: Fix Released Status in libcommons-collections3-java
[Desktop-packages] [Bug 1525454] Re: bootstrapping mono compiler fails at mdoc
Debian decided to just stop building mdocs on s390x with the following patch on rules file (applied conditionally on s390x only). +CONF_FLAGS += --with-mcs-docs=no I dropped the Ubuntu delta, now that s390x builds fine, and the optimization level is back to the default one (I think no docs is better than not optimized binary!) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mono in Ubuntu. https://bugs.launchpad.net/bugs/1525454 Title: bootstrapping mono compiler fails at mdoc Status in mono package in Ubuntu: Fix Released Bug description: mdoc fails when bootstrapping mono To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mono/+bug/1525454/+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 1823707] Re: GUI with PyQt5 QtGui do not start on VirtualBox VM
this should be good in later virtualbox releases ** Changed in: virtualbox-hwe (Ubuntu) Status: New => Fix Released ** Changed in: virtualbox (Ubuntu) Status: New => Fix Released ** Changed in: pyqt5 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1823707 Title: GUI with PyQt5 QtGui do not start on VirtualBox VM Status in hplip package in Ubuntu: Invalid Status in pyqt5 package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Fix Released Status in virtualbox-hwe package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1. Install Ubuntu 19.04 on VirtualBox VM (5.1.38 host in my case) 2. Enable 3D acceleration on the VM 3. Install VirtualBox guest additions into guest with `sudo apt-get install virtualbox-guest-x11` (or `sudo apt-get install virtualbox-guest-x11-hwe`) and reboot VM 4a. Install HPLIP GUI with `sudo apt-get install hplip-gui` 4b. Install Retext with `sudo apt-get install retext` 5a. Try to launch HPLIP Toolbox with `hp-toolbox` 5b. Try to launch Retext with `retext` Expected results: * HPLIP Toolbox is shown and have trayicon ; Retext launched Actual results: * HPLIP Toolbox window is not shown, trayicon is not shown. ; Retext is not launched. Got error message in the terminal: ``` error: /lib/VBoxOGLcrutil.so: undefined symbol: crypt_r ``` ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: hplip-gui 3.19.1+dfsg0-1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 CurrentDesktop: MATE Date: Mon Apr 8 14:42:12 2019 InstallationDate: Installed on 2019-04-08 (0 days ago) InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Alpha amd64 (20190408) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox PackageArchitecture: all Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic root=UUID=b256c639-5b80-4c01-a5b2-672fb0e29114 ro quiet splash SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1823707/+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 1823707] Re: GUI with PyQt5 QtGui do not start on VirtualBox VM
This looks like an upstream issue... can you please open an upstream ticket? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1823707 Title: GUI with PyQt5 QtGui do not start on VirtualBox VM Status in hplip package in Ubuntu: Invalid Status in pyqt5 package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Bug description: Steps to reproduce: 1. Install Ubuntu 19.04 on VirtualBox VM (5.1.38 host in my case) 2. Enable 3D acceleration on the VM 3. Install VirtualBox guest additions into guest with `sudo apt-get install virtualbox-guest-x11` (or `sudo apt-get install virtualbox-guest-x11-hwe`) and reboot VM 4a. Install HPLIP GUI with `sudo apt-get install hplip-gui` 4b. Install Retext with `sudo apt-get install retext` 5a. Try to launch HPLIP Toolbox with `hp-toolbox` 5b. Try to launch Retext with `retext` Expected results: * HPLIP Toolbox is shown and have trayicon ; Retext launched Actual results: * HPLIP Toolbox window is not shown, trayicon is not shown. ; Retext is not launched. Got error message in the terminal: ``` error: /lib/VBoxOGLcrutil.so: undefined symbol: crypt_r ``` ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: hplip-gui 3.19.1+dfsg0-1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 CurrentDesktop: MATE Date: Mon Apr 8 14:42:12 2019 InstallationDate: Installed on 2019-04-08 (0 days ago) InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Alpha amd64 (20190408) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox PackageArchitecture: all Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic root=UUID=b256c639-5b80-4c01-a5b2-672fb0e29114 ro quiet splash SourcePackage: hplip UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1823707/+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 1813587] Re: libunistring and libidn ftbfs on 18.04 LTS
its a build fix... anyway, its a library, so not that easy to test, but I picked up gnome-characters, one of its reverse-dependencies that uses a lot of unicode, and it still works gnome-characters Gtk-Message: 09:13:35.039: Failed to load module "canberra-gtk-module" Gtk-Message: 09:13:35.039: Failed to load module "canberra-gtk-module" Gjs-Message: 09:13:35.042: JS LOG: Characters Application started Gjs-Message: 09:13:38.057: JS LOG: Characters Application exiting dpkg -l |grep unistr ii libunistring2:amd640.9.10-1ubuntu1.18.10.1 amd64 Unicode string library for C ii libidn11:amd64 1.33-2.2ubuntu1.1 amd64 GNU Libidn library, implementation of IETF IDN specifications ii libidn2-0:amd642.0.5-1 amd64 Internationalized domain names (IDNA2008/TR46) library to test libidn I installed and started successfully vlc. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring and libidn ftbfs on 18.04 LTS Status in libidn package in Ubuntu: Fix Released Status in libunistring package in Ubuntu: Fix Released Status in libidn source package in Bionic: Fix Committed Status in libunistring source package in Bionic: Fix Released Status in libidn source package in Cosmic: Fix Committed Status in libunistring source package in Cosmic: Fix Released Status in libunistring package in Debian: New Bug description: Impact -- libunistring doesn't build from source which means someone would need to fix that problem before fixing any bugs in the libunistring package for Ubuntu 18.04 LTS. Test Case - Does libunistring build successfully? Regression Potential We are simply backporting the workaround we applied in Ubuntu 19.04. Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813587/+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 1813587] Re: libunistring and libidn ftbfs on 18.04 LTS
This is something that is currently fixing just a build failure, not something that the end user is affected... Marking as verification done (and I'm using the package because my system is on bionic) ** Tags removed: verification-needed verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done verification-done-bionic verification-done-cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring and libidn ftbfs on 18.04 LTS Status in libidn package in Ubuntu: Fix Released Status in libunistring package in Ubuntu: Fix Released Status in libidn source package in Bionic: Fix Committed Status in libunistring source package in Bionic: Fix Committed Status in libidn source package in Cosmic: Fix Committed Status in libunistring source package in Cosmic: Fix Committed Status in libunistring package in Debian: New Bug description: Impact -- libunistring doesn't build from source which means someone would need to fix that problem before fixing any bugs in the libunistring package for Ubuntu 18.04 LTS. Test Case - Does libunistring build successfully? Regression Potential We are simply backporting the workaround we applied in Ubuntu 19.04. Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813587/+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 1813587] Re: libunistring and libidn ftbfs on 18.04 LTS
@Brian Now the disco fix is in both cosmic and bionic queues. please accept them :) I checked if wl-asneeded was removed from rules, if the patch was added, and also the upgrade path for versioning was correct for bionic->cosmic->disco please double check! I also fixed the description ** Changed in: libunistring (Ubuntu Cosmic) Assignee: (unassigned) => Gianfranco Costamagna (costamagnagianfranco) ** Changed in: libunistring (Ubuntu) Assignee: Jeremy Bicha (jbicha) => (unassigned) ** Changed in: libidn (Ubuntu Cosmic) Assignee: (unassigned) => Gianfranco Costamagna (costamagnagianfranco) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring and libidn ftbfs on 18.04 LTS Status in libidn package in Ubuntu: Fix Released Status in libunistring package in Ubuntu: Fix Released Status in libidn source package in Bionic: In Progress Status in libunistring source package in Bionic: Fix Committed Status in libidn source package in Cosmic: In Progress Status in libunistring source package in Cosmic: In Progress Status in libunistring package in Debian: New Bug description: Impact -- libunistring doesn't build from source which means someone would need to fix that problem before fixing any bugs in the libunistring package for Ubuntu 18.04 LTS. Test Case - Does libunistring build successfully? Regression Potential We are simply backporting the workaround we applied in Ubuntu 19.04. Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813587/+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 1813587] Re: libunistring and libidn ftbfs on 18.04 LTS
libunistring backport patch to cosmic from Disco: diff -Nru libunistring-0.9.10/debian/changelog libunistring-0.9.10/debian/changelog --- libunistring-0.9.10/debian/changelog2018-07-23 16:46:28.0 +0200 +++ libunistring-0.9.10/debian/changelog2019-03-27 12:21:30.0 +0100 @@ -1,3 +1,10 @@ +libunistring (0.9.10-1ubuntu1.18.10.1) cosmic; urgency=medium + + * Cherry-pick pthread fix from upstream and disco release. +(LP: #1813587) + + -- Gianfranco Costamagna Wed, 27 Mar 2019 12:21:30 +0100 + libunistring (0.9.10-1ubuntu1) cosmic; urgency=medium * Do not set as-needed, to work-around a testsuite failure diff -Nru libunistring-0.9.10/debian/patches/cca32830b57e91f837c01d15b8732f23ff97fc36.patch libunistring-0.9.10/debian/patches/cca32830b57e91f837c01d15b8732f23ff97fc36.patch --- libunistring-0.9.10/debian/patches/cca32830b57e91f837c01d15b8732f23ff97fc36.patch 1970-01-01 01:00:00.0 +0100 +++ libunistring-0.9.10/debian/patches/cca32830b57e91f837c01d15b8732f23ff97fc36.patch 2019-03-27 12:21:14.0 +0100 @@ -0,0 +1,15 @@ +Description: Fix link failure with upstream gnulib patch +Origin: https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=cca32830b57e91f837c01d15b8732f23ff97fc36 +Last-Update: 2019-03-20 + +--- libunistring-0.9.10.orig/tests/glthread/thread.h libunistring-0.9.10/tests/glthread/thread.h +@@ -133,8 +133,6 @@ extern int glthread_in_use (void); +call to foo(...) in the same function. To avoid this, we test the +address of a function in libpthread that we don't use. */ + +-# pragma weak pthread_create +- + # ifndef pthread_sigmask /* Do not declare rpl_pthread_sigmask weak. */ + # pragma weak pthread_sigmask + # endif diff -Nru libunistring-0.9.10/debian/patches/series libunistring-0.9.10/debian/patches/series --- libunistring-0.9.10/debian/patches/series 2018-07-23 16:46:28.0 +0200 +++ libunistring-0.9.10/debian/patches/series 2019-03-27 12:21:14.0 +0100 @@ -1,2 +1,3 @@ 0100-float-endian-detection.patch 0700-multiarch-libc.patch +cca32830b57e91f837c01d15b8732f23ff97fc36.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring and libidn ftbfs on 18.04 LTS Status in libidn package in Ubuntu: Fix Released Status in libunistring package in Ubuntu: Fix Released Status in libidn source package in Bionic: In Progress Status in libunistring source package in Bionic: Fix Committed Status in libidn source package in Cosmic: In Progress Status in libunistring source package in Cosmic: In Progress Status in libunistring package in Debian: New Bug description: Impact -- libunistring doesn't build from source which means someone would need to fix that problem before fixing any bugs in the libunistring package for Ubuntu 18.04 LTS. Test Case - Does libunistring build successfully? Regression Potential We are simply backporting the workaround we applied in Ubuntu 19.04. Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813587/+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 1813587] Re: libunistring and libidn ftbfs on 18.04 LTS
Ok Brian, so lets backport the fix from 19.04 and fix also 18.10 ** Also affects: libidn (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: libunistring (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: libunistring (Ubuntu Cosmic) Status: New => In Progress ** Changed in: libidn (Ubuntu Cosmic) Status: New => In Progress ** Changed in: libidn (Ubuntu Bionic) Status: Incomplete => In Progress ** Description changed: Impact -- libunistring doesn't build from source which means someone would need to fix that problem before fixing any bugs in the libunistring package for Ubuntu 18.04 LTS. Test Case - Does libunistring build successfully? Regression Potential - We are simply backporting the workaround we applied in Ubuntu 18.10. + We are simply backporting the workaround we applied in Ubuntu 19.04. Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring and libidn ftbfs on 18.04 LTS Status in libidn package in Ubuntu: Fix Released Status in libunistring package in Ubuntu: Fix Released Status in libidn source package in Bionic: In Progress Status in libunistring source package in Bionic: Fix Committed Status in libidn source package in Cosmic: In Progress Status in libunistring source package in Cosmic: In Progress Status in libunistring package in Debian: New Bug description: Impact -- libunistring doesn't build from source which means someone would need to fix that problem before fixing any bugs in the libunistring package for Ubuntu 18.04 LTS. Test Case - Does libunistring build successfully? Regression Potential We are simply backporting the workaround we applied in Ubuntu 19.04. Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813587/+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 1816736] Re: llvm-toolchain-4.0: Remove from disco
Decrufting thunderbird-testsuite should be enough to let it migrate and then llvm-toolchain-4.0 removed from the archive. ** Changed in: llvm-toolchain-4.0 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1816736 Title: llvm-toolchain-4.0: Remove from disco Status in firefox package in Ubuntu: Fix Released Status in llvm-toolchain-4.0 package in Ubuntu: Fix Released Status in thunderbird package in Ubuntu: Fix Committed Bug description: This needs to be removed from disco, only remaining reverse-deps are firefox and thunderbird. We should limit the number of llvm versions in the archive due to the difficulty of maintaining them all (specially now that has gone from Debian, and won't probably even build in disco) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1816736/+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 1813587] Re: libunistring and libidn ftbfs on 18.04 LTS
In the same way, I'm uploading a fix for libidn, I think it is really better to have as-needed used for the binary size, so better use the upstream patch and revert the package currently in updates. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring and libidn ftbfs on 18.04 LTS Status in libidn package in Ubuntu: Fix Released Status in libunistring package in Ubuntu: Fix Released Status in libidn source package in Bionic: In Progress Status in libunistring source package in Bionic: In Progress Status in libunistring package in Debian: Won't Fix Bug description: Impact -- libunistring doesn't build from source which means someone would need to fix that problem before fixing any bugs in the libunistring package for Ubuntu 18.04 LTS. Test Case - Does libunistring build successfully? Regression Potential We are simply backporting the workaround we applied in Ubuntu 18.10. Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813587/+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 1813587] Re: libunistring ftbfs on 18.04 LTS
I uploaded the upstream patch in the unapproved queue, thanks! ** Changed in: libunistring (Ubuntu Bionic) Assignee: Jeremy Bicha (jbicha) => Gianfranco Costamagna (costamagnagianfranco) ** Summary changed: - libunistring ftbfs on 18.04 LTS + libunistring and libidn ftbfs on 18.04 LTS ** Also affects: libidn (Ubuntu) Importance: Undecided Status: New ** Changed in: libidn (Ubuntu) Status: New => Fix Released ** Changed in: libidn (Ubuntu Bionic) Status: New => In Progress ** Changed in: libidn (Ubuntu Bionic) Assignee: (unassigned) => Gianfranco Costamagna (costamagnagianfranco) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring and libidn ftbfs on 18.04 LTS Status in libidn package in Ubuntu: Fix Released Status in libunistring package in Ubuntu: Fix Released Status in libidn source package in Bionic: In Progress Status in libunistring source package in Bionic: In Progress Status in libunistring package in Debian: Won't Fix Bug description: Impact -- libunistring doesn't build from source which means someone would need to fix that problem before fixing any bugs in the libunistring package for Ubuntu 18.04 LTS. Test Case - Does libunistring build successfully? Regression Potential We are simply backporting the workaround we applied in Ubuntu 18.10. Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813587/+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 1340250] Re: "#pragma weak" symbol is 0 even when defined
https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=cca32830b57e91f837c01d15b8732f23ff97fc36
Upstream fix
** Changed in: libidn (Ubuntu)
Status: New => Fix Released
** Changed in: libunistring (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libunistring in Ubuntu.
https://bugs.launchpad.net/bugs/1340250
Title:
"#pragma weak" symbol is 0 even when defined
Status in binutils package in Ubuntu:
Invalid
Status in gcc-defaults package in Ubuntu:
Invalid
Status in libidn package in Ubuntu:
Fix Released
Status in libunistring package in Ubuntu:
Fix Released
Bug description:
This compiler bug is making the gnulib tests dump core; see:
http://lists.gnu.org/archive/html/bug-gnulib/2014-07/msg00039.html
Compile and run the following program t.c with the shell commands "gcc
u.c -lm; ./a.out; echo $?"
#include
#pragma weak tgamma
int
main (void)
{
if (!tgamma)
return 2;
if (tgamma (1) == 1)
return 0;
return 1;
}
The program will exit with status 2. It should exit with status 0,
because the math library does have a tgamma function and the function
pointer should be non-null.
I observe this problem with Ubuntu 14.04 x86-64 (GCC Ubuntu
4.8.2-19ubuntu1), but not on Fedora 20 or on RHEL 6.5.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: gcc 4:4.8.2-1ubuntu6
ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
Uname: Linux 3.13.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jul 10 07:39:11 2014
InstallationDate: Installed on 2012-12-21 (566 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
SourcePackage: gcc-defaults
UpgradeStatus: Upgraded to trusty on 2014-04-18 (83 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1340250/+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 1816736] [NEW] llvm-toolchain-4.0: Remove from disco
Public bug reported: This needs to be removed from disco, only remaining reverse-deps are firefox and thunderbird. We should limit the number of llvm versions in the archive due to the difficulty of maintaining them all (specially now that has gone from Debian, and won't probably even build in disco) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Affects: llvm-toolchain-4.0 (Ubuntu) Importance: Undecided Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Also affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Remove from disco + llvm-toolchain-4.0: Remove from disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1816736 Title: llvm-toolchain-4.0: Remove from disco Status in firefox package in Ubuntu: New Status in llvm-toolchain-4.0 package in Ubuntu: New Status in thunderbird package in Ubuntu: New Bug description: This needs to be removed from disco, only remaining reverse-deps are firefox and thunderbird. We should limit the number of llvm versions in the archive due to the difficulty of maintaining them all (specially now that has gone from Debian, and won't probably even build in disco) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1816736/+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 1685037] Re: In 16.04 the package suggests vital, but non-existent packages chromedriver and firefoxdriver
*** This bug is a duplicate of bug 1667208 *** https://bugs.launchpad.net/bugs/1667208 and looks really similar to 1685037 ** This bug has been marked a duplicate of bug 1667208 Ubuntu's selenium hardcodes a path that is valid for Debian, but not for Ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1685037 Title: In 16.04 the package suggests vital, but non-existent packages chromedriver and firefoxdriver Status in chromium-browser package in Ubuntu: Fix Released Status in python-selenium package in Ubuntu: Fix Released Bug description: In Xenial this package suggests two other packgages: chromedriver and firefoxdriver. These packgages are not available in Xenial. Only Chromium-chromedriver is. Unfortunately, python-selenium does not provide webdrivers, so they have to be installed separately. Why aren’t they available? This greatly hampers the usefulness of python-selenium. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1685037/+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 1685037] Re: In 16.04 the package suggests vital, but non-existent packages chromedriver and firefoxdriver
*** This bug is a duplicate of bug 1667208 *** https://bugs.launchpad.net/bugs/1667208 This is ongoing to be fixed in disco, feel free to convert in an SRU. ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Fix Released ** Changed in: python-selenium (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1685037 Title: In 16.04 the package suggests vital, but non-existent packages chromedriver and firefoxdriver Status in chromium-browser package in Ubuntu: Fix Released Status in python-selenium package in Ubuntu: Fix Released Bug description: In Xenial this package suggests two other packgages: chromedriver and firefoxdriver. These packgages are not available in Xenial. Only Chromium-chromedriver is. Unfortunately, python-selenium does not provide webdrivers, so they have to be installed separately. Why aren’t they available? This greatly hampers the usefulness of python-selenium. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1685037/+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 1667208] Re: Ubuntu's selenium hardcodes a path that is valid for Debian, but not for Ubuntu
This will be fixed in chromium itself, to behave how Debian does
** Package changed: python-selenium (Ubuntu) => chromium (Ubuntu)
** Package changed: chromium (Ubuntu) => chromium-browser (Ubuntu)
** Also affects: python-selenium (Ubuntu)
Importance: Undecided
Status: New
** Changed in: python-selenium (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1667208
Title:
Ubuntu's selenium hardcodes a path that is valid for Debian, but not
for Ubuntu
Status in chromium-browser package in Ubuntu:
Confirmed
Status in python-selenium package in Ubuntu:
Invalid
Bug description:
Hi.
The package python{,3}-selenium uses a hardcoded path of
'/usr/lib/chromium/chromedriver' when instantiating a Chrome
webdriver.
That path is correct for Debian (in particular, it was directly
inherited from https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=805733#5), but since Ubuntu uses chromium-
browser instead of Debian's chromium naming. The package chromium-
chromedriver in Ubuntu installs the webdriver at '/usr/lib/chromium-
browser/chromedriver'.
There needs to be a synchronization between the selenium Python module
and the webdriver package.
Thanks,
Rogério Brito.
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: python3-selenium 2.53.2+dfsg1-1
Uname: Linux 4.10.0-041000-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: MATE
Date: Thu Feb 23 01:38:24 2017
Dependencies:
InstallationDate: Installed on 2016-12-11 (73 days ago)
InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64
(20161012.1)
PackageArchitecture: all
SourcePackage: python-selenium
UpgradeStatus: Upgraded to zesty on 2017-01-31 (23 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1667208/+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 1813587] Re: libunistring ftbfs on 18.04 LTS
yes, it is the same, but unfortunately I don't know if the fix is sane or not. the real bug is this one https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1340250 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring ftbfs on 18.04 LTS Status in libunistring package in Ubuntu: New Status in libunistring source package in Bionic: New Bug description: according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunistring/+bug/1813587/+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 1810772] Re: firefox/thunderbird: please drop llvm-4.0 and switch to versionless alternative
Looks like 6.0 works for thunderbird, while firefox fails due to cbindgen failing to connect to github (not sure how/if this relates to llvm) llvm 7 seems to make thunderbird fail, as well as llvm-8, but I think llvm-6 is a safe bet, since we are going to ship cosmic with it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1810772 Title: firefox/thunderbird: please drop llvm-4.0 and switch to versionless alternative Status in firefox package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: As said, we want to remove llvm-toolchain-4.0 from the archive, and firefox/thunderbird are the two last blockers. Debian has already switched to the versionless alternative. thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1810772/+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 1810772] Re: firefox/thunderbird: please drop llvm-4.0 and switch to versionless alternative
Olivier, can you please have a look? firefox with the switch does build everywhere except armhf ppc64el s390x while the current thunderbird in the archive is ftbfs even without changes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1810772 Title: firefox/thunderbird: please drop llvm-4.0 and switch to versionless alternative Status in firefox package in Ubuntu: New Status in thunderbird package in Ubuntu: New Bug description: As said, we want to remove llvm-toolchain-4.0 from the archive, and firefox/thunderbird are the two last blockers. Debian has already switched to the versionless alternative. thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1810772/+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 1810772] [NEW] firefox/thunderbird: please drop llvm-4.0 and switch to versionless alternative
Public bug reported: As said, we want to remove llvm-toolchain-4.0 from the archive, and firefox/thunderbird are the two last blockers. Debian has already switched to the versionless alternative. thanks ** Affects: firefox (Ubuntu) Importance: High Status: New ** Affects: thunderbird (Ubuntu) Importance: High Status: New ** Changed in: thunderbird (Ubuntu) Importance: Undecided => High ** Also affects: firefox (Ubuntu) Importance: Undecided Status: New ** Changed in: firefox (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1810772 Title: firefox/thunderbird: please drop llvm-4.0 and switch to versionless alternative Status in firefox package in Ubuntu: New Status in thunderbird package in Ubuntu: New Bug description: As said, we want to remove llvm-toolchain-4.0 from the archive, and firefox/thunderbird are the two last blockers. Debian has already switched to the versionless alternative. thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1810772/+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 1802586] Re: sane-backends library name issues
we should probably ask debian to provide a transitional package too -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1802586 Title: sane-backends library name issues Status in sane-backends package in Ubuntu: New Bug description: There is a dispute in Debian about the package name for the sane library. See especially https://bugs.debian.org/913346 Also https://bugs.debian.org/913125 & https://bugs.debian.org/908681 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1802586/+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 1771031] Re: Please remove libgnome from Ubuntu
Syncd shortly ** Changed in: p4vasp (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libbonobo in Ubuntu. https://bugs.launchpad.net/bugs/1771031 Title: Please remove libgnome from Ubuntu Status in gbonds package in Ubuntu: New Status in gjiten package in Ubuntu: New Status in gnome-color-chooser package in Ubuntu: New Status in gnome-commander package in Ubuntu: New Status in gnome-translate package in Ubuntu: New Status in grdesktop package in Ubuntu: New Status in gresolver package in Ubuntu: New Status in libbonobo package in Ubuntu: New Status in libbonoboui package in Ubuntu: New Status in libgnome package in Ubuntu: New Status in libgnomeui package in Ubuntu: New Status in linsmith package in Ubuntu: New Status in p4vasp package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: Invalid Status in resapplet package in Ubuntu: New Status in winefish package in Ubuntu: New Bug description: libgnome has been removed from Debian Testing and will not be included in the Debian 10 "Buster" release. We should do the same. If we do it now, maybe some projects will do the needed porting work away from libgnome (porting to gtk3 is probably needed) in time for Ubuntu 20.04 LTS or Debian 10. Users who are hurt by these removals can keep using Ubuntu 18.04 LTS for a few years. This bug depends on these other removals: gnome-python LP: #1739800 gnome-sharp2 LP: #1771025 DONE: shutter LP: #1771030 The libgnome removal in turn blocks these other removals: gnome-vfs LP: #1771035 libgnome-keyring LP: #1771036 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gbonds/+bug/1771031/+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 1771031] Re: Please remove libgnome from Ubuntu
Removed from disco ** Changed in: pike7.8 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libbonobo in Ubuntu. https://bugs.launchpad.net/bugs/1771031 Title: Please remove libgnome from Ubuntu Status in gbonds package in Ubuntu: New Status in gjiten package in Ubuntu: New Status in gnome-color-chooser package in Ubuntu: New Status in gnome-commander package in Ubuntu: New Status in gnome-translate package in Ubuntu: New Status in grdesktop package in Ubuntu: New Status in gresolver package in Ubuntu: New Status in libbonobo package in Ubuntu: New Status in libbonoboui package in Ubuntu: New Status in libgnome package in Ubuntu: New Status in libgnomeui package in Ubuntu: New Status in linsmith package in Ubuntu: New Status in p4vasp package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: Invalid Status in resapplet package in Ubuntu: New Status in winefish package in Ubuntu: New Bug description: libgnome has been removed from Debian Testing and will not be included in the Debian 10 "Buster" release. We should do the same. If we do it now, maybe some projects will do the needed porting work away from libgnome (porting to gtk3 is probably needed) in time for Ubuntu 20.04 LTS or Debian 10. Users who are hurt by these removals can keep using Ubuntu 18.04 LTS for a few years. This bug depends on these other removals: gnome-python LP: #1739800 gnome-sharp2 LP: #1771025 DONE: shutter LP: #1771030 The libgnome removal in turn blocks these other removals: gnome-vfs LP: #1771035 libgnome-keyring LP: #1771036 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gbonds/+bug/1771031/+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 1792811] Re: Transmission-gtk startup crash: doesn't start on 18.10
After opening with apport the crash dump, I can see a crash in the above mentioned Core was generated by `transmission-gtk /tmp/mozilla_intilinux0/edubuntu-12.04.5-dvd-i386.iso.torrent'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7fbbb9be123f in gtk_css_node_ensure_style (cssnode=0x5594cd1f1a20, current_time=current_time@entry=8576248389) at ../../../../gtk/gtkcssnode.c:987 ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => High ** Changed in: transmission (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1792811 Title: Transmission-gtk startup crash: doesn't start on 18.10 Status in gtk+3.0 package in Ubuntu: New Status in transmission package in Ubuntu: New Bug description: It's impossibile to run transmission-gtk (segmentation fault). transmission-gtk 2.94 (d8e60ee44f) warning: core file may not match specified executable file. [New LWP 19206] [New LWP 19207] [New LWP 19210] [New LWP 19209] [New LWP 19211] [New LWP 19213] [New LWP 19212] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `transmission-gtk /tmp/mozilla_intilinux0/edubuntu-12.04.5-dvd-i386.iso.torrent'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7fbbb9be123f in gtk_css_node_ensure_style (cssnode=0x5594cd1f1a20, current_time=current_time@entry=8576248389) at ../../../../gtk/gtkcssnode.c:987 987 ../../../../gtk/gtkcssnode.c: No such file or directory. [Current thread is 1 (Thread 0x7fbbb14c6c80 (LWP 19206))] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1792811/+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 1792811] Re: Transmission-gtk startup crash: doesn't start on 18.10
I can't run gdb with that crash (it can't be loaded) ** Changed in: transmission (Ubuntu) Assignee: Gianfranco Costamagna (costamagnagianfranco) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1792811 Title: Transmission-gtk startup crash: doesn't start on 18.10 Status in transmission package in Ubuntu: New Bug description: It's impossibile to run transmission-gtk (segmentation fault). transmission-gtk 2.94 (d8e60ee44f) warning: core file may not match specified executable file. [New LWP 19206] [New LWP 19207] [New LWP 19210] [New LWP 19209] [New LWP 19211] [New LWP 19213] [New LWP 19212] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `transmission-gtk /tmp/mozilla_intilinux0/edubuntu-12.04.5-dvd-i386.iso.torrent'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7fbbb9be123f in gtk_css_node_ensure_style (cssnode=0x5594cd1f1a20, current_time=current_time@entry=8576248389) at ../../../../gtk/gtkcssnode.c:987 987 ../../../../gtk/gtkcssnode.c: No such file or directory. [Current thread is 1 (Thread 0x7fbbb14c6c80 (LWP 19206))] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1792811/+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 1792811] Re: Transmission-gtk crash: doesn't start on 18.10
please run apport-collect 1792811 ** Changed in: transmission (Ubuntu) Assignee: (unassigned) => Gianfranco Costamagna (costamagnagianfranco) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1792811 Title: Transmission-gtk startup crash: doesn't start on 18.10 Status in transmission package in Ubuntu: New Bug description: It's impossibile to run transmission-gtk (segmentation fault). transmission-gtk 2.94 (d8e60ee44f) warning: core file may not match specified executable file. [New LWP 19206] [New LWP 19207] [New LWP 19210] [New LWP 19209] [New LWP 19211] [New LWP 19213] [New LWP 19212] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `transmission-gtk /tmp/mozilla_intilinux0/edubuntu-12.04.5-dvd-i386.iso.torrent'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7fbbb9be123f in gtk_css_node_ensure_style (cssnode=0x5594cd1f1a20, current_time=current_time@entry=8576248389) at ../../../../gtk/gtkcssnode.c:987 987 ../../../../gtk/gtkcssnode.c: No such file or directory. [Current thread is 1 (Thread 0x7fbbb14c6c80 (LWP 19206))] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/1792811/+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
