[Desktop-packages] [Bug 2003266] Re: 22.04 package lacks GSSAPI support

2024-09-12 Thread Sergio Durigan Junior
** Also affects: neon27 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to neon27 in Ubuntu.
https://bugs.launchpad.net/bugs/2003266

Title:
  22.04 package lacks GSSAPI support

Status in neon27 package in Ubuntu:
  Confirmed
Status in neon27 source package in Jammy:
  New

Bug description:
  [ Impact ]

   * GSSAPI was disabled by accident as a side-effect of packaging a new 
release.
     Upstream renamed the environment variable used to setup the feature and the
     flag was not updated in d/rules.

   * Users get caught off-guard when updating from 20.04 to 22.04, 24.04 is not
     affected.

  [ Test Plan ]

   * Did not test the binary, confirmed the fix is effective by analyzing the
     build logs.

   * I've confirmed that the issue
     is solved by checking for the presence of the following string in the build
     logs:
    checking for krb5-config... /usr/bin/krb5-config.mit
     Whereas a build with the issue will instead output:
    checking for krb5-config... none

   * I believe the fix is non-intrusive enough that no further testing
  is needed.

  [ Where problems could occur ]

   * Enabling a new feature could have a side effect of disabling another
     mutually-exclusive feature, but I did not identify any.

   * Enabling a new feature could break a different feature which changes its
     behavior when this new feature is present, I also did not identify any such
     case.

  [ Other Info ]

   * Upstream bug reports:
     - https://github.com/notroj/neon/issues/102
     - https://github.com/notroj/neon/issues/52
   * Upstream breaking change:
     - 
https://github.com/notroj/neon/commit/b9b7425de38b35249e689c03c30c8fd8adfae806
   * Upstream change to avoid this from happening again:
     - 
https://github.com/notroj/neon/commit/4fdcff4a0ccbb0924f7dabcf8d213452aa33ab82
   * Launchpad bug:
     - https://bugs.launchpad.net/ubuntu/+source/neon27/+bug/2003266

  [ Original description ]

  For more information, please see
  https://github.com/notroj/neon/issues/102.

  The 22.04 built package of neon lacks GSSAPI support, whereas previous
  versions (e.g. 18.04) had this support built-in. This appears to be
  due to a recent-ish change in the build logic for neon, which changes
  when GSSAPI is compiled in to the library
  
(https://github.com/notroj/neon/commit/b9b7425de38b35249e689c03c30c8fd8adfae806)

  We were able to get a work around building from source with the
  following envvar during build-time:
  KRB5_CONF_TOOL=/usr/bin/krb5-config.mit ./configure. TL;DR:
  KRB5_CONFIG became KRB5_CONF_TOOL.

  Version information:

  $ lsb_release -rd
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04

  $ apt show libneon27
  Package: libneon27
  Version: 0.32.2-1
  Priority: optional
  Section: universe/libs
  Source: neon27
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Laszlo Boszormenyi (GCS) 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 233 kB
  Depends: libc6 (>= 2.33), libssl3 (>= 3.0.0~~alpha1), libxml2 (>= 2.7.4), 
zlib1g (>= 1:1.1.4)
  Homepage: https://notroj.github.io/neon/
  Download-Size: 102 kB
  APT-Manual-Installed: no
  APT-Sources: [corporate Launchpad mirror]
  Description: HTTP and WebDAV client library

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/neon27/+bug/2003266/+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 1945774] Re: openssl: breaks ssl-cert installation: 8022CB35777F0000:error:1200007A:random number generator:RAND_write_file:Not a regular file:../crypto/rand/randfile.c:190:Fil

2024-04-15 Thread Sergio Durigan Junior
This is not a bug in ssl-cert.  It's a bug in libapache2-mod-auth-
mellon, more specifically in the way it configures openssl to generate
its certificate.  From /usr/sbin/mellon_create_metadata:

cat >"$TEMPLATEFILE" < Triaged

** Changed in: ssl-cert (Ubuntu Jammy)
   Status: Confirmed => Fix Released

** Changed in: hplip (Ubuntu Jammy)
   Status: Confirmed => 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/1945774

Title:
  openssl: breaks ssl-cert installation:
  8022CB35777F:error:127A:random number
  generator:RAND_write_file:Not a regular
  file:../crypto/rand/randfile.c:190:Filename=/dev/urandom

Status in mod_auth_mellon:
  Unknown
Status in hplip package in Ubuntu:
  Fix Released
Status in libapache2-mod-auth-mellon package in Ubuntu:
  New
Status in ssl-cert package in Ubuntu:
  Fix Released
Status in hplip source package in Jammy:
  Fix Released
Status in libapache2-mod-auth-mellon source package in Jammy:
  Triaged
Status in ssl-cert source package in Jammy:
  Fix Released
Status in ssl-cert package in Debian:
  Fix Released

Bug description:
  Imported from Debian bug http://bugs.debian.org/990228:

  Package: openssl
  Version: 3.0.0~~alpha16-1
  Severity: serious
  User: debian...@lists.debian.org
  Usertags: piuparts

  Hi,

  during a test with piuparts I noticed your package causes other package
  to fail installation/upgrading.

  From the attached log (scroll to the bottom...):

  ...
Setting up openssl (3.0.0~~alpha16-1) ...
Setting up libbsd0:amd64 (0.11.3-1) ...
Setting up readline-common (8.1-2) ...
Setting up libxml2:amd64 (2.9.10+dfsg-6.7) ...
Setting up libgdbm6:amd64 (1.19-2) ...
Setting up postgresql-client-common (226) ...
Setting up libedit2:amd64 (3.1-20210522-1~exp1) ...
Setting up libreadline8:amd64 (8.1-2) ...
Setting up libldap-2.4-2:amd64 (2.4.57+dfsg-3) ...
Setting up libllvm11:amd64 (1:11.0.1-2) ...
Setting up ssl-cert (1.1.0+nmu1) ...
Could not create certificate. Openssl output was:
Generating a RSA private key

..+..+..+...+.+...+.+...+...+..+...+.+..+...+.+...+...+..+.+.+...+...+.+..++..+..+*.+*..+..++...+.+..+...++..+.++..++...++..+.+...+..+...+...+.+..+...+.++.+++.+..+.+.+..+..+.+...+.+.+.++.+.+.++++...+

..+.++...+...+...+..+..+.+...+.++...+.+..+..+..+*+...++..+...+..+...+..+.+..+*+..+...++..++..++.+..+...++.+.+..+.+.+..+.+..+..+..+.+++.++..+...+.+...+...+...+...+..++...+..+.+
Writing new private key to '/etc/ssl/private/ssl-cert-snakeoil.key'
-
Warning: No -copy_extensions given; ignoring any extensions in the request
Cannot write random bytes:
8022CB35777F:error:127A:random number generator:RAND_write_file:Not 
a regular file:../crypto/rand/randfile.c:190:Filename=/dev/urandom
dpkg: error processing package ssl-cert (--configure):
 installed ssl-cert package post-installation script subprocess returned 
error exit status 1
dpkg: dependency problems prevent configuration of postgresql-common:
 postgresql-common depends on ssl-cert (>= 1.0.11); however:
  Package ssl-cert is not configured yet.
  ...

  Hmm, well, yes, /dev/urandom is not a regular file. It's a character
  device node.

  
  cheers,

  Andreas

To manage notifications about this bug go to:
https://bugs.launchpad.net/mod-auth-mellon/+bug/1945774/+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 1945774] Re: openssl: breaks ssl-cert installation: 8022CB35777F0000:error:1200007A:random number generator:RAND_write_file:Not a regular file:../crypto/rand/randfile.c:190:Fil

2024-04-15 Thread Sergio Durigan Junior
Upstream fix:

https://github.com/latchset/mod_auth_mellon/commit/c6102de6ff651bf763400cb59202d9abe384f615

** Bug watch added: github.com/latchset/mod_auth_mellon/issues #105
   https://github.com/latchset/mod_auth_mellon/issues/105

** Also affects: mod-auth-mellon via
   https://github.com/latchset/mod_auth_mellon/issues/105
   Importance: Unknown
   Status: Unknown

** Tags added: bitesize

-- 
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/1945774

Title:
  openssl: breaks ssl-cert installation:
  8022CB35777F:error:127A:random number
  generator:RAND_write_file:Not a regular
  file:../crypto/rand/randfile.c:190:Filename=/dev/urandom

Status in mod_auth_mellon:
  Unknown
Status in hplip package in Ubuntu:
  Fix Released
Status in libapache2-mod-auth-mellon package in Ubuntu:
  New
Status in ssl-cert package in Ubuntu:
  Fix Released
Status in hplip source package in Jammy:
  Fix Released
Status in libapache2-mod-auth-mellon source package in Jammy:
  Triaged
Status in ssl-cert source package in Jammy:
  Fix Released
Status in ssl-cert package in Debian:
  Fix Released

Bug description:
  Imported from Debian bug http://bugs.debian.org/990228:

  Package: openssl
  Version: 3.0.0~~alpha16-1
  Severity: serious
  User: debian...@lists.debian.org
  Usertags: piuparts

  Hi,

  during a test with piuparts I noticed your package causes other package
  to fail installation/upgrading.

  From the attached log (scroll to the bottom...):

  ...
Setting up openssl (3.0.0~~alpha16-1) ...
Setting up libbsd0:amd64 (0.11.3-1) ...
Setting up readline-common (8.1-2) ...
Setting up libxml2:amd64 (2.9.10+dfsg-6.7) ...
Setting up libgdbm6:amd64 (1.19-2) ...
Setting up postgresql-client-common (226) ...
Setting up libedit2:amd64 (3.1-20210522-1~exp1) ...
Setting up libreadline8:amd64 (8.1-2) ...
Setting up libldap-2.4-2:amd64 (2.4.57+dfsg-3) ...
Setting up libllvm11:amd64 (1:11.0.1-2) ...
Setting up ssl-cert (1.1.0+nmu1) ...
Could not create certificate. Openssl output was:
Generating a RSA private key

..+..+..+...+.+...+.+...+...+..+...+.+..+...+.+...+...+..+.+.+...+...+.+..++..+..+*.+*..+..++...+.+..+...++..+.++..++...++..+.+...+..+...+...+.+..+...+.++.+++.+..+.+.+..+..+.+...+.+.+.++.+.+.++++...+

..+.++...+...+...+..+..+.+...+.++...+.+..+..+..+*+...++..+...+..+...+..+.+..+*+..+...++..++..++.+..+...++.+.+..+.+.+..+.+..+..+..+.+++.++..+...+.+...+...+...+...+..++...+..+.+
Writing new private key to '/etc/ssl/private/ssl-cert-snakeoil.key'
-
Warning: No -copy_extensions given; ignoring any extensions in the request
Cannot write random bytes:
8022CB35777F:error:127A:random number generator:RAND_write_file:Not 
a regular file:../crypto/rand/randfile.c:190:Filename=/dev/urandom
dpkg: error processing package ssl-cert (--configure):
 installed ssl-cert package post-installation script subprocess returned 
error exit status 1
dpkg: dependency problems prevent configuration of postgresql-common:
 postgresql-common depends on ssl-cert (>= 1.0.11); however:
  Package ssl-cert is not configured yet.
  ...

  Hmm, well, yes, /dev/urandom is not a regular file. It's a character
  device node.

  
  cheers,

  Andreas

To manage notifications about this bug go to:
https://bugs.launchpad.net/mod-auth-mellon/+bug/1945774/+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 2051895] Re: Lenovo XT99 BT headset can't work in HFP profile

2024-02-08 Thread Sergio Durigan Junior
Hello Hui,

The changes look good to me, but I have a few minor requests:

- Could you please expand the changelog entry and explain what the patch
fixes?  It doesn't need to be a long text or anything like that; just a
small sentence is enough.

- Could you add DEP-3 headers to the patch, please?  You can find more
information here:

https://dep-team.pages.debian.net/deps/dep3/

but basically, I'm looking for something like:

Origin: upstream, 
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/commit/d7dc04e8f5c404b1fa16409f69dcde7c56312f02
Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2051895

I'm unsubscribing ubuntu-sponsors from the bug for now.  Please
resubscribe it once you've addressed the points above.

Thanks.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/2051895

Title:
  Lenovo XT99 BT headset can't work in HFP profile

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Jammy:
  In Progress
Status in pulseaudio source package in Mantic:
  In Progress
Status in pulseaudio source package in Noble:
  In Progress

Bug description:
  [Summary]
  When use the ThinkPluse xt99 bluetooth head set to run the test 
com.canonical.certification::bluetooth/audio_record_playback, it cannot record 
the sound and playback.
  It seems this device cannot switch to Hand free mode in this platform.

  [Steps to reproduce]
  Connect the ThinkPluse xt99, use the Handfree mode, then try to record some 
voice.

  [Expected result]
  The bluetooth headset ThinkPluse xt99 can use as a MIC to input sound.

  [Actual result]
  The bluetooth headset xt99 cannot work in the Handfree mode.

  [Failure rate]
  100%

  
  [Impact]
  With the current Ubuntu 22.04 oem image, we try to connect the LENOVO
  XT99 bt headset and let it work in HFP mode, we select HFP profile
  from gnome sound-setting, but the microphone will not auto change to
  bt microphone and the bt output could not work too. So this BT headset
  could only work in A2DP mode with the current 22.04 OEM image.

  And we tried ubuntu 22.04 generic image, mantic image and noble image,
  none of them could make the headset work in HFP mode.
   
  [Fix]
  Cherry-pick a pulseaudio commit from upstream.

  [Test]
  Install the patched pulseaudio and reboot, connect to the LENOVO XT99
  bt headset, select it to work in HFP mode, tested playback and capture,
  all worked well.

  [Where problems could occur]
  This change will impact bt headset negotiation process in the pulseaudio,
  so the possiblity of regression is limited to bt headset, it could make
  the bt headset fail to connect, but this possibility is very low, we tested
  the patch with different bt headset and bt speaker, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2051895/+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 2007702] Re: [SRU] Deb version numbering is misleading

2023-12-07 Thread Sergio Durigan Junior
While I see Julian's point, I believe it's better to stick to the same
versioning scheme used in the Firefox deb, which is exactly what you did
for Noble:

 firefox | 1:1snap1-0ubuntu2   | jammy   | source, amd64, 
arm64, armhf
 firefox | 1:1snap1-0ubuntu3   | lunar   | source, amd64, 
arm64, armhf
 firefox | 1:1snap1-0ubuntu3   | mantic  | source, amd64, 
arm64, armhf
 firefox | 1:1snap1-0ubuntu3   | noble   | source, amd64, 
arm64, armhf

As Athos said above, I'm not entirely sure how "SRU-able" this is, but
either way, I went ahead and uploaded the debdiffs (after a minor typo
fix).

I'm unsubscribing ubuntu-sponsors from this bug; feel free to
resubscribe it if needed.

Thanks!

** Changed in: chromium-browser (Ubuntu Focal)
   Status: New => In Progress

** Changed in: chromium-browser (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: chromium-browser (Ubuntu Lunar)
   Status: New => In Progress

** Changed in: chromium-browser (Ubuntu Mantic)
   Status: New => In Progress

-- 
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/2007702

Title:
  [SRU] Deb version numbering is misleading

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Focal:
  In Progress
Status in chromium-browser source package in Jammy:
  In Progress
Status in chromium-browser source package in Lunar:
  In Progress
Status in chromium-browser source package in Mantic:
  In Progress

Bug description:
  [Impact]
  For Ubuntu >= Focal the transitional debs are frozen at the version number 
1:85...

  This might make one think[1][2] that it will install a critically
  outdated Chromium while it does not, because it installs the snap.

  [Test plan]

  Install the package and confirm the version change with e.g.

    dpkg -l | grep '^ii *chromium-browser *2:1snap1-0ubuntu1'

  [Regression potential]

  If the version were incorrectly constructed the deb build could fail.

  [1] 
https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/702591
  [2] https://askubuntu.com/q/1420925

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2007702/+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 2044654] Re: No debugging symbols found in libgdk-3.so.0

2023-11-28 Thread Sergio Durigan Junior
I've added ubuntu-debuginfod as an affected project and marked the bug
as Invalid for gtk-3.

BTW, this is a known issue that's being worked on.  Hopefully it should
be resolved in the next days.

Thanks for reporting the bug!

** Also affects: ubuntu-debuginfod
   Importance: Undecided
   Status: New

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2044654

Title:
  No debugging symbols found in libgdk-3.so.0

Status in ubuntu-debuginfod:
  New
Status in gtk+3.0 package in Ubuntu:
  Invalid

Bug description:
  Attach gdb to a running yelp process!

  (gdb) share libgdk
  Reading symbols from /lib/x86_64-linux-gnu/libgdk-3.so.0...
  (No debugging symbols found in /lib/x86_64-linux-gnu/libgdk-3.so.0)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgtk-3-0 3.24.33-1ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-1016.16~22.04.1-azure 6.2.16
  Uname: Linux 6.2.0-1016-azure x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 26 13:11:15 2023
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-debuginfod/+bug/2044654/+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 2038834] Re: GPU acceleration via VirGL is broken in qemu

2023-11-16 Thread Sergio Durigan Junior
Hello Mate,

I see that the debdiff you provided applies to Noble, but this bug is
also marked as affecting Mantic.  Could you provide an updated debdiff
for the Mantic version?  Thanks!

-- 
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/2038834

Title:
  GPU acceleration via VirGL is broken in qemu

Status in Release Notes for Ubuntu:
  New
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Mantic:
  New
Status in mesa source package in Noble:
  Fix Released

Bug description:
  
  [ Impact ] 
   * Enabling GPU acceleration can cause host-side crashes on mantic/noble VMs 

   * This was reported by someone else upstream and is already fixed by 
 https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25580.

  [ Test Plan ]

   * I've tested the patch on an affected macOS host running Ubuntu in UTM with 
 OpenGL enabled on both Mantic and Noble VMs.

   * Anyone else can do the same on an affected host by simply installing the 
 patched package and booting to the desktop.

  [ Where problems could occur ]

   * This patch fixes an upstream mesa regression which caused libvirglrendrer 
to 
 crash on the host side.

   * This makes a non-working use case work, VirGL on affected hosts cannot 
 regress as it simply didn't work before.

   * Risk of breakage is mainly from other packages possible affected by a mesa 
 rebuild.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2038834/+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 2035228] Re: ruby-gsl dep8 fails on ppc64el

2023-09-12 Thread Sergio Durigan Junior
I built a version of gsl using -O2 instead of -O3 on ppc64el and
confirmed that the problem went away.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gsl in Ubuntu.
https://bugs.launchpad.net/bugs/2035228

Title:
  ruby-gsl dep8 fails on ppc64el

Status in gsl package in Ubuntu:
  In Progress

Bug description:
  With the latest update of gsl from Debian, ruby-gsl's dep8 test start
  failing on ppc64el:

  421s 
===
  421s Failure: test_random32_bsd_0(RngTest):
  421s   random32-bsd, 1 steps (852261210 observed vs 1663114331 expected).
  421sis not true.
  421s /tmp/autopkgtest.r5vIrM/build.JWr/src/test/gsl/rng_test.rb:92:in `block 
(3 levels) in '
  421s 
===
  421s : (0.007176)
  421s test_random32_glibc2_0:  .: (0.001215)
  421s test_random32_libc5_0:   F
  421s 
===
  421s Failure: test_random32_libc5_0(RngTest):
  421s   random32-libc5, 1 steps (367802360 observed vs 1967452027 
expected).
  421sis not true.
  421s /tmp/autopkgtest.r5vIrM/build.JWr/src/test/gsl/rng_test.rb:92:in `block 
(3 levels) in '
  421s 
===
  421s : (0.002615)
  421s test_random64_bsd_0: F
  421s 
===
  421s Failure: test_random64_bsd_0(RngTest):
  421s   random64-bsd, 1 steps (210970120 observed vs 864469165 expected).
  421sis not true.
  421s /tmp/autopkgtest.r5vIrM/build.JWr/src/test/gsl/rng_test.rb:92:in `block 
(3 levels) in '
  421s 
===
  421s : (0.002551)
  421s test_random64_glibc2_0:  .: (0.001151)
  421s test_random64_libc5_0:   F
  421s 
===
  421s Failure: test_random64_libc5_0(RngTest):
  421s   random64-libc5, 1 steps (221021662 observed vs 2106639801 
expected).
  421sis not true.
  421s /tmp/autopkgtest.r5vIrM/build.JWr/src/test/gsl/rng_test.rb:92:in `block 
(3 levels) in '
  421s 
===
  421s : (0.002627)

  This looks like a precision problem caused by excessive optimization
  in the architecture.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gsl/+bug/2035228/+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 2035228] [NEW] ruby-gsl dep8 fails on ppc64el

2023-09-12 Thread Sergio Durigan Junior
Public bug reported:

With the latest update of gsl from Debian, ruby-gsl's dep8 test start
failing on ppc64el:

421s 
===
421s Failure: test_random32_bsd_0(RngTest):
421s   random32-bsd, 1 steps (852261210 observed vs 1663114331 expected).
421sis not true.
421s /tmp/autopkgtest.r5vIrM/build.JWr/src/test/gsl/rng_test.rb:92:in `block (3 
levels) in '
421s 
===
421s : (0.007176)
421s test_random32_glibc2_0:.: (0.001215)
421s test_random32_libc5_0: F
421s 
===
421s Failure: test_random32_libc5_0(RngTest):
421s   random32-libc5, 1 steps (367802360 observed vs 1967452027 expected).
421sis not true.
421s /tmp/autopkgtest.r5vIrM/build.JWr/src/test/gsl/rng_test.rb:92:in `block (3 
levels) in '
421s 
===
421s : (0.002615)
421s test_random64_bsd_0:   F
421s 
===
421s Failure: test_random64_bsd_0(RngTest):
421s   random64-bsd, 1 steps (210970120 observed vs 864469165 expected).
421sis not true.
421s /tmp/autopkgtest.r5vIrM/build.JWr/src/test/gsl/rng_test.rb:92:in `block (3 
levels) in '
421s 
===
421s : (0.002551)
421s test_random64_glibc2_0:.: (0.001151)
421s test_random64_libc5_0: F
421s 
===
421s Failure: test_random64_libc5_0(RngTest):
421s   random64-libc5, 1 steps (221021662 observed vs 2106639801 expected).
421sis not true.
421s /tmp/autopkgtest.r5vIrM/build.JWr/src/test/gsl/rng_test.rb:92:in `block (3 
levels) in '
421s 
===
421s : (0.002627)

This looks like a precision problem caused by excessive optimization in
the architecture.

** Affects: gsl (Ubuntu)
 Importance: High
 Assignee: Sergio Durigan Junior (sergiodj)
 Status: In Progress


** Tags: update-excuse

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gsl in Ubuntu.
https://bugs.launchpad.net/bugs/2035228

Title:
  ruby-gsl dep8 fails on ppc64el

Status in gsl package in Ubuntu:
  In Progress

Bug description:
  With the latest update of gsl from Debian, ruby-gsl's dep8 test start
  failing on ppc64el:

  421s 
===
  421s Failure: test_random32_bsd_0(RngTest):
  421s   random32-bsd, 1 steps (852261210 observed vs 1663114331 expected).
  421sis not true.
  421s /tmp/autopkgtest.r5vIrM/build.JWr/src/test/gsl/rng_test.rb:92:in `block 
(3 levels) in '
  421s 
===
  421s : (0.007176)
  421s test_random32_glibc2_0:  .: (0.001215)
  421s test_random32_libc5_0:   F
  421s 
===
  421s Failure: test_random32_libc5_0(RngTest):
  421s   random32-libc5, 1 steps (367802360 observed vs 1967452027 
expected).
  421sis not true.
  421s /tmp/autopkgtest.r5vIrM/build.JWr/src/test/gsl/rng_test.rb:92:in `block 
(3 levels) in '
  421s 
===
  421s : (0.002615)
  421s test_random64_bsd_0: F
  421s 
===
  421s Failure: test_random64_bsd_0(RngTest):
  421s   random64-bsd, 1 steps (210970120 observed vs 864469165 expected).
  421sis not true.
  421s /tmp/autopkgtest.r5vIrM/build.JWr/src/test/gsl/rng_test.rb:92:in `block 
(3 levels) in '
  421s 
===
  421s : (0.002551)
  421s test_random64_glibc2_0:  .: (0.001151)
  421s test_random64_libc5_0:   F
  421s 
===
  421s Failure: test_random64_libc5_0(RngTest):
  421s   random64-libc5, 1 steps (221021662 observed vs 2106639801 
expected).
  421sis not true.
  421s /tmp/autopkgtest.r5vIrM/build.JWr/src/test/gsl/rng_test.rb:92:in `block 
(3 levels) in '
  421s 
===
  421s : (0.002627)

  This looks like a precision problem caused by excess

[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list

2023-07-13 Thread Sergio Durigan Junior
I'm unsubscribing Ubuntu Sponsors.

** Changed in: ubuntu-drivers-common (Ubuntu Jammy)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1990341

Title:
  [SRU] Support to install nvidia driver by allowing list

Status in OEM Priority Project:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  In Progress
Status in ubuntu-drivers-common source package in Lunar:
  Fix Released

Bug description:
  [ Impact ]

   * In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
  OEM/ODM for production.

  In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
  to use a specific nvidia version to development/production.

  NVIDIA and OEN/ODM will announce the next generation combination at
  the same time usually when the factory ready to ship the product.

  We made Ubuntu as a leading distribution supports many cutting edge
  devices, it's time to have an official way to make the nvidia
  installation consistent in unannounced (yet) nvidia devices to support
  OEM/ODM factory shipment for our growing counterparts.

  [ Test Plan ]

   * Steps to make sure it works:

  1. pick a cutting edge nvidia graphic.
  2. remove nv-525 from the pool by removing restricted in jammy-updates and 
jammy-security
  3. check the nv support status:
  ```
  $ ubuntu-drivers list
  oem-fix-gfx-nvidia-ondemandmode
  libfprint-2-tod1-broadcom
  oem-somerville-cinccino-meta
  ```
  4. modify custom file
  ```
  $ cat /etc/custom_supported_gpus.json
  {
    "chips": [
  {
    "devid": "0x24BA",
    "name": "TEST 24BA",
    "branch": "580.1234",
    "features": [
  "runtimepm"
    ]
  },
  {
    "devid": "0x25BC",
    "name": "TEST 25BC",
    "branch": "510",
    "features": [
  "runtimepm"
    ]
  }
    ]
  }
  ```
  5. make sure the hook works
  ```
  $ ubuntu-drivers list
  nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
  oem-fix-gfx-nvidia-ondemandmode
  libfprint-2-tod1-broadcom
  oem-somerville-cinccino-meta

  [ Where problems could occur ]

   * This feature only impact target system has a custom file
  "/etc/custom_supported_gpus.json". And it won't generate automatically
  which should not impact normal users

  [ Other Info ]

   * the patches are picked from
     - 
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
     - 
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
     - 
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
   * Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+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 1990341] Re: [SRU] Support to install nvidia driver by allowing list

2023-07-13 Thread Sergio Durigan Junior
Hello Dirk,

I took the liberty to fix a nit in the changelog entry:

 18[ Jeremy Szu ]   

   
 19* README, README.md, 

   
 20  UbuntuDrivers/detect.py,   

   
 21  tests/test_ubuntu_drivers.py:  

   
 22  - Let OEM images locally extend the NVIDIA driver  

   
 23supported PCI IDs for cutting edge silicons by specifying

   
 24related information in /etc/custom_supported_gpus.json file. 

   
 25(LP: #1990341)   

   
 26  - Fix pkg.candidate.record retired from apt_pkg library

   
 27  - Support autopkgtest for force install Nvidia and update  

   
 28related section in README.   

   

I changed the "- Let OEM..." sentence, and made sure that "LP" is
uppercase.

Otherwise I believe everything has been properly addressed so I'm
uploading this package:

$ dput ubuntu-drivers-common_0.9.6.2~0.22.04.5_source.changes
Trying to upload package to ubuntu
Checking signature on .changes
gpg: 
/home/sergio/work/ubuntu-drivers-common/ubuntu-drivers-common_0.9.6.2~0.22.04.5_source.changes:
 Valid signature from 106DA1C8C3CBBF14
Checking signature on .dsc
gpg: 
/home/sergio/work/ubuntu-drivers-common/ubuntu-drivers-common_0.9.6.2~0.22.04.5.dsc:
 Valid signature from 106DA1C8C3CBBF14
Uploading to ubuntu (via ftp to upload.ubuntu.com):
  Uploading ubuntu-drivers-common_0.9.6.2~0.22.04.5.dsc: done.
  Uploading ubuntu-drivers-common_0.9.6.2~0.22.04.5.tar.xz: done.  
  Uploading ubuntu-drivers-common_0.9.6.2~0.22.04.5_source.buildinfo: done. 
  Uploading ubuntu-drivers-common_0.9.6.2~0.22.04.5_source.changes: done.
Successfully uploaded packages.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1990341

Title:
  [SRU] Support to install nvidia driver by allowing list

Status in OEM Priority Project:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common source package in Jammy:
  In Progress
Status in ubuntu-drivers-common source package in Lunar:
  Fix Released

Bug description:
  [ Impact ]

   * In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
  OEM/ODM for production.

  In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
  to use a specific nvidia version to development/production.

  NVIDIA and OEN/ODM will announce the next generation combination at
  the same time usually when the factory ready to ship the product.

  We made Ubuntu as a leading distribution supports many cutting edge
  devices, it's time to have an official way to make the nvidia
  installation consistent in unannounced (yet) nvidia devices to support
  OEM/ODM factory shipment for our growing counterparts.

  [ Test Plan ]

   * Steps to make sure it works:

  1. pick a cutting edge nvidia graphic.
  2. remove nv-525 from the pool by removing restricted in jammy-updates and 
jammy-security
  3. check the nv support status:
  ```
  $ ubuntu-drivers list
  oem-fix-gfx-nvidia-ondemandmode
  libfprint-2-tod1-broadcom
  oem-somerville-cinccino-meta
  ```
  4. modify custom file
  ```
  $ cat /etc/custom_supported_gpus.json
  {
    "chips": [
  {
    "devid": "0x24BA",
    "name": "TEST 24BA",
    "branch": "580.1234",
    "features": [
  "runtimepm"
    ]
  },
  {
    "devid": "0x25BC",
    "name": "TEST 25BC",
  

[Desktop-packages] [Bug 2024064] [NEW] libssh dep8 fails on ppc64el/s390x

2023-06-15 Thread Sergio Durigan Junior
Public bug reported:

Reporting this bug for documentation purposes.  libssh's dep8 test is
failing on ppc64el/s390x.

I tried reproducing it in a ppc64el canonistack box, but the test always
passes there.  migration-reference/0 didn't help.

It's interesting to notice that the test succeeds on debci, which leads
me to believe that this is something really particular to our
autopkgtest infra.

** Affects: libssh (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: update-excuse

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libssh in Ubuntu.
https://bugs.launchpad.net/bugs/2024064

Title:
  libssh dep8 fails on ppc64el/s390x

Status in libssh package in Ubuntu:
  New

Bug description:
  Reporting this bug for documentation purposes.  libssh's dep8 test is
  failing on ppc64el/s390x.

  I tried reproducing it in a ppc64el canonistack box, but the test
  always passes there.  migration-reference/0 didn't help.

  It's interesting to notice that the test succeeds on debci, which
  leads me to believe that this is something really particular to our
  autopkgtest infra.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libssh/+bug/2024064/+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 2008919] [NEW] [FFe] Implement support for "buttercup_eval"

2023-03-01 Thread Sergio Durigan Junior
Public bug reported:

dh-elpa supports the "ert_eval" directive inside d/elpa-test, which
allows the package to provide custom Elisp code to be executed before
ERT is invoked.  Unfortunately, a similar feature is missing for
buttercup tests.  This means that, whenever a package uses buttercup to
run its tests, the maintainer needs to override dh_elpa_test and invoke
buttercup by hand.  This, however, only works during build time; dh-elpa
is also used to run autopkgtest, and in that specific scenario it's not
possible to execute custom Elisp code using buttercup at all.

Why is this important, you might ask.  Well, I've been investigating a
bug in Emacs 28.2's native compilation mechanism which affects a bunch
of packages (see bug #2006963 for more details).  One of those affected
packages is flycheck, which uses buttercup.  I uploaded a fix for a
flycheck FTBFS which addresses the problem, but the package still fails
its autopkgtest because of the problem mentioned above.

Long story short, I've implemented the support for a new dh-elpa
directive called "buttercup_eval" and would like it to Lunar.  I also
proposed the feature to Debian here: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1032202

** Affects: dh-elpa (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: dh-elpa (Debian)
 Importance: Unknown
 Status: Unknown

** Bug watch added: Debian Bug tracker #1032202
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032202

** Also affects: dh-elpa (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032202
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dh-elpa in Ubuntu.
https://bugs.launchpad.net/bugs/2008919

Title:
  [FFe] Implement support for "buttercup_eval"

Status in dh-elpa package in Ubuntu:
  New
Status in dh-elpa package in Debian:
  Unknown

Bug description:
  dh-elpa supports the "ert_eval" directive inside d/elpa-test, which
  allows the package to provide custom Elisp code to be executed before
  ERT is invoked.  Unfortunately, a similar feature is missing for
  buttercup tests.  This means that, whenever a package uses buttercup
  to run its tests, the maintainer needs to override dh_elpa_test and
  invoke buttercup by hand.  This, however, only works during build
  time; dh-elpa is also used to run autopkgtest, and in that specific
  scenario it's not possible to execute custom Elisp code using
  buttercup at all.

  Why is this important, you might ask.  Well, I've been investigating a
  bug in Emacs 28.2's native compilation mechanism which affects a bunch
  of packages (see bug #2006963 for more details).  One of those
  affected packages is flycheck, which uses buttercup.  I uploaded a fix
  for a flycheck FTBFS which addresses the problem, but the package
  still fails its autopkgtest because of the problem mentioned above.

  Long story short, I've implemented the support for a new dh-elpa
  directive called "buttercup_eval" and would like it to Lunar.  I also
  proposed the feature to Debian here: https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=1032202

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dh-elpa/+bug/2008919/+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 2006674] Re: GTK-3.0 themes not working with 22.04

2023-02-09 Thread Sergio Durigan Junior
** Also affects: gtk4 (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: sssd (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk4 in Ubuntu.
https://bugs.launchpad.net/bugs/2006674

Title:
  GTK-3.0 themes not working with 22.04

Status in gtk4 package in Ubuntu:
  New

Bug description:
  I am trying to migrate my customized theme on ubuntu 22.04 , but it is not 
taking effect .
  I read through different portals and found that in 22.04 themes are migrated 
to gtk-4.0 and there should be a folder present with the name gtk-4.0 inside 
the theme.

  I tried migrating my gtk-3.0 to gtk-4.0 but still not able to apply
  the theme .

  Can you please help me out are their any specific steps which needs to
  be done for migrating my customized theme.

  
  I am trying to change the color of the dialog which comes if we are closing 
any unsaved file from red to blue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/2006674/+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 1994141] Re: incompatible versions of network-manager-openvpn and openvpn delivered in ubuntu22.10

2022-10-31 Thread Sergio Durigan Junior
Thank you for your bug report.  This seems to be a problem with network-
manager-openvpn, so I took the liberty to remove Ubuntu and the openvpn
package from the list of affected projects.  I also pinged the person
that backported the upstream fixes to Kinetic.

** No longer affects: ubuntu

** No longer affects: openvpn (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/1994141

Title:
  incompatible versions of network-manager-openvpn and openvpn delivered
  in ubuntu22.10

Status in network-manager-openvpn package in Ubuntu:
  Confirmed

Bug description:
  After installing  network-manager-openvpn(1.10.0-1ubuntu2),
  openvpn(2.6.0~git20220818-1ubuntu1) is installed as a dependency.

  Mentioned NM plugin uses openvpn option `--cipher` instead of `--data-
  ciphers`. With openvpn2.6.0+ this breaks existing setups - connection
  never establishes and fails with message like:

  ```
  DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in 
--data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores 
--cipher for cipher negotiations.
  ```
  and
  ```
  Connection reset, restarting [0]
  ```

  reproducer: configure openVPN client against openVPN server with
  cipher set to 'AES-256-CBC'.

  workaround: manually install openvpn 2.5.x from sources and mask
  distribution-provided openvpn 2.6.x.

  proposed solution:

  deliver compatible combination of network-manager-openvpn and openvpn.

  
  system info:
  Description:Ubuntu 22.10
  Release:22.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1994141/+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 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)

2022-06-14 Thread Sergio Durigan Junior
This has been fixed since sssd 2.4.0.

** Changed in: sssd (Ubuntu)
   Status: Incomplete => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1792544

Title:
  demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2
  (10.x)

Status in aide package in Ubuntu:
  Incomplete
Status in anope package in Ubuntu:
  Incomplete
Status in apache2 package in Ubuntu:
  Triaged
Status in apr-util package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Fix Released
Status in exim4 package in Ubuntu:
  In Progress
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in grep package in Ubuntu:
  Incomplete
Status in haproxy package in Ubuntu:
  Fix Released
Status in libpam-mount package in Ubuntu:
  Fix Released
Status in libselinux package in Ubuntu:
  Fix Released
Status in nginx package in Ubuntu:
  Incomplete
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php-defaults package in Ubuntu:
  Fix Released
Status in php7.2 package in Ubuntu:
  Won't Fix
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  Invalid
Status in rasqal package in Ubuntu:
  Incomplete
Status in slang2 package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in tilix package in Ubuntu:
  New
Status in ubuntu-core-meta package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in wget package in Ubuntu:
  Fix Released
Status in zsh package in Ubuntu:
  Incomplete
Status in zsh package in Debian:
  Confirmed

Bug description:
  https://people.canonical.com/~ubuntu-
  archive/transitions/html/pcre2-main.html

  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  --
  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just poorly 
named.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+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 1962389] Re: Sync upower 0.99.16-2 (main) from Debian unstable (main)

2022-02-27 Thread Sergio Durigan Junior
This bug was fixed in the package upower - 0.99.16-2
Sponsored for Rik Mills (rikmills)

---
upower (0.99.16-2) unstable; urgency=medium

  * Cherry-pick FD handling fixes from upstream (Closes: #1006368)

 -- Michael Biebl   Sat, 26 Feb 2022 10:43:19 +0100

** Changed in: upower (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/1962389

Title:
  Sync upower 0.99.16-2 (main) from Debian unstable (main)

Status in upower package in Ubuntu:
  Fix Released

Bug description:
  Please sync upower 0.99.16-2 (main) from Debian unstable (main)

  Changelog entries since current jammy version 0.99.16-1:

  upower (0.99.16-2) unstable; urgency=medium

* Cherry-pick FD handling fixes from upstream (Closes: #1006368)

   -- Michael Biebl   Sat, 26 Feb 2022 10:43:19 +0100

  As per https://gitlab.freedesktop.org/upower/upower/-/issues/174

  this should fix KDE not registering and acting on laptop lid closure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1962389/+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 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

2021-11-24 Thread Sergio Durigan Junior
** Tags removed: server-todo

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1718227

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  Invalid
Status in ethtool package in Ubuntu:
  Triaged
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  Fix Released
Status in ntp package in Ubuntu:
  Won't Fix
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  Fix Released
Status in openvpn package in Ubuntu:
  Confirmed
Status in openvswitch package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  Fix Released
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+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 1945774] Re: openssl: breaks ssl-cert installation: 8022CB35777F0000:error:1200007A:random number generator:RAND_write_file:Not a regular file:../crypto/rand/randfile.c:190:Fil

2021-11-10 Thread Sergio Durigan Junior
hplip has also built successfully:

https://launchpad.net/ubuntu/+source/hplip/3.21.8+dfsg0-2

So I'm marking this bug as Fix Released for it.

** Changed in: hplip (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/1945774

Title:
  openssl: breaks ssl-cert installation:
  8022CB35777F:error:127A:random number
  generator:RAND_write_file:Not a regular
  file:../crypto/rand/randfile.c:190:Filename=/dev/urandom

Status in hplip package in Ubuntu:
  Fix Released
Status in ssl-cert package in Ubuntu:
  Fix Released
Status in ssl-cert package in Debian:
  Fix Released

Bug description:
  Imported from Debian bug http://bugs.debian.org/990228:

  Package: openssl
  Version: 3.0.0~~alpha16-1
  Severity: serious
  User: debian...@lists.debian.org
  Usertags: piuparts

  Hi,

  during a test with piuparts I noticed your package causes other package
  to fail installation/upgrading.

  From the attached log (scroll to the bottom...):

  ...
Setting up openssl (3.0.0~~alpha16-1) ...
Setting up libbsd0:amd64 (0.11.3-1) ...
Setting up readline-common (8.1-2) ...
Setting up libxml2:amd64 (2.9.10+dfsg-6.7) ...
Setting up libgdbm6:amd64 (1.19-2) ...
Setting up postgresql-client-common (226) ...
Setting up libedit2:amd64 (3.1-20210522-1~exp1) ...
Setting up libreadline8:amd64 (8.1-2) ...
Setting up libldap-2.4-2:amd64 (2.4.57+dfsg-3) ...
Setting up libllvm11:amd64 (1:11.0.1-2) ...
Setting up ssl-cert (1.1.0+nmu1) ...
Could not create certificate. Openssl output was:
Generating a RSA private key

..+..+..+...+.+...+.+...+...+..+...+.+..+...+.+...+...+..+.+.+...+...+.+..++..+..+*.+*..+..++...+.+..+...++..+.++..++...++..+.+...+..+...+...+.+..+...+.++.+++.+..+.+.+..+..+.+...+.+.+.++.+.+.++++...+

..+.++...+...+...+..+..+.+...+.++...+.+..+..+..+*+...++..+...+..+...+..+.+..+*+..+...++..++..++.+..+...++.+.+..+.+.+..+.+..+..+..+.+++.++..+...+.+...+...+...+...+..++...+..+.+
Writing new private key to '/etc/ssl/private/ssl-cert-snakeoil.key'
-
Warning: No -copy_extensions given; ignoring any extensions in the request
Cannot write random bytes:
8022CB35777F:error:127A:random number generator:RAND_write_file:Not 
a regular file:../crypto/rand/randfile.c:190:Filename=/dev/urandom
dpkg: error processing package ssl-cert (--configure):
 installed ssl-cert package post-installation script subprocess returned 
error exit status 1
dpkg: dependency problems prevent configuration of postgresql-common:
 postgresql-common depends on ssl-cert (>= 1.0.11); however:
  Package ssl-cert is not configured yet.
  ...

  Hmm, well, yes, /dev/urandom is not a regular file. It's a character
  device node.

  
  cheers,

  Andreas

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1945774/+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 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

2021-10-14 Thread Sergio Durigan Junior
MR for the Debian postfix package also submitted:

https://salsa.debian.org/postfix-team/postfix-dev/-/merge_requests/13

** Changed in: postfix (Ubuntu)
   Status: New => Triaged

** Changed in: postfix (Ubuntu)
 Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1718227

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  Invalid
Status in ethtool package in Ubuntu:
  Triaged
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  Triaged
Status in ntp package in Ubuntu:
  Won't Fix
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  Fix Released
Status in openvpn package in Ubuntu:
  Confirmed
Status in openvswitch package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  Triaged
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+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 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

2021-10-13 Thread Sergio Durigan Junior
I've also submitted a Merge Request against the Debian clamav package:

https://salsa.debian.org/clamav-team/clamav/-/merge_requests/4

Hopefully it will be accepted & merged into Ubuntu soon. If not, I will
submit an MP to add this change as a delta to our package.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1718227

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  Invalid
Status in ethtool package in Ubuntu:
  Triaged
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  Triaged
Status in ntp package in Ubuntu:
  Won't Fix
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  Fix Released
Status in openvpn package in Ubuntu:
  Confirmed
Status in openvswitch package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+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 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

2021-10-13 Thread Sergio Durigan Junior
FWIW, I submitted a Merge Request against the Debian nss-pam-ldapd here:

https://salsa.debian.org/debian/nss-pam-ldapd/-/merge_requests/2

Hopefully it will be accepted & merged into Ubuntu soon.  If not, I will
submit an MP to add this change as a delta to our package.

** Changed in: nss-pam-ldapd (Ubuntu)
   Status: New => Triaged

** Changed in: nss-pam-ldapd (Ubuntu)
 Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1718227

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  Invalid
Status in ethtool package in Ubuntu:
  Triaged
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  Triaged
Status in ntp package in Ubuntu:
  Won't Fix
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  Fix Released
Status in openvpn package in Ubuntu:
  Confirmed
Status in openvswitch package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+subscriptions


-- 
Mailing list: https:/

[Desktop-packages] [Bug 1945713] Re: Flaky test brotli/basic on focal amd64?

2021-10-06 Thread Sergio Durigan Junior
I spent some time trying to get to the bottom of the issue, but
unfortunately I was not able to make much progress here.

As expected, the very first thing to do here is to reproduce the bug
locally.  I tried many things:

- I built the package locally and ran autopkgtest against it.  Passed.

- I built the package inside a Focal LXD container and then ran
autopkgtest there.  Passed.

- Still inside the Focal LXD container, I tried to invoke the failing
test manually.  Passed.

- I know that Ubuntu's autopkgtest infra uses a Bionic host to run the
tests.  I created a Bionic VM, and inside it I git cloned the
development version of autopkgtest.  Then, I invoked autopkgtest against
the Focal source package for libsoup2.4, using a Focal LXD container as
the testbed.  Passed.

I ran out of ideas on what to try locally, and given that Bryce was able
to add a hint for the failure and unblock apache2, I am giving up (at
least for now).  The way I see it, a person interested in continuing
debugging this could:

- Add debugging statements to the libsoup2.4 code, upload the modified
package to a PPA, and run autopkgtests using the Ubuntu infra.  This
should be able to provide more useful information regarding the array
manipulation that's happening in the test.

- If the above doesn't work, one could try to add debugging statements
to the libglib code that's responsible for array manipulations.


Lastly, it's important to mention that this may very well be something 
unrelated to libsoup2.4/glib.  It can even be a hardware issue, who knows...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libsoup2.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1945713

Title:
  Flaky test brotli/basic on focal amd64?

Status in libsoup2.4 package in Ubuntu:
  New

Bug description:
  The brotli/basic test case periodically fails.  It appears that a few
  retriggers can result in a pass:

  https://autopkgtest.ubuntu.com/packages/libs/libsoup2.4/focal/amd64

  The failures look like this in autopkgtest logs:

  ERROR:../tests/brotli-decompressor-test.c:59:test_brotli:
  assertion failed ((char*)out_bytes->data == contents): ("***\nU" ==
  "***\n")

  I've replaced most of the text with '***' to highlight the difference
  is a 'U' character appended.

  The test case is essentially doing a decompression of 'brotli-
  data/compressed.br' and comparing that it matches 'brotli-
  data/uncompressed.txt'.  I've done this manually using the brotli cli,
  and the files do indeed have the same content.  I've also built the
  package and run the test case locally in a focal lxc container on
  amd64:

  $ cd 
libsoup2.4-gu/debian/libsoup2.4-tests/usr/libexec/installed-tests/libsoup-2.4
  $ while : ; do ./brotli-decompressor-test | grep 'brotli/basic';  sleep 
0.1; done

  I left that to run several hundred cycles but no failures reported at
  all.

  There are a bunch of instances of this failure, here's a few for
  reference:

  
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20210602_152107_d1d56@/log.gz
  
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20210531_201241_8b1be@/log.gz
  
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/libs/libsoup2.4/20200508_211619_2aec8@/log.gz

  That last link is the earliest instance I've been able to find.

  You'll notice in the second two links they also have a failure "not ok
  2 /ssl/tls-interaction", but the first link shows only the brotli
  failure.

  Interestingly, I've not found instances of this failure against other
  architectures than amd64, nor have I seen it on releases other than
  focal.  No dice from googling for bug reports or other reports of test
  failures with libsoup2.4 + brotli.

  The test's code is doing this, basically:

  SoupBrotliDecompressor *dec = soup_brotli_decompressor_new ();
  do {
  result = g_converter_convert (G_CONVERTER (dec), in_buf, 
length, out_buf, sizeof out_buf, 0,
&bytes_read, &bytes_written, 
&error);
  g_byte_array_append (out_bytes, out_buf, bytes_written);
in_buf += bytes_read;
  length -= bytes_read;

  } while (result == G_CONVERTER_CONVERTED);

  soup_brotli_decompressor's code is here:

  https://gitlab.gnome.org/GNOME/libsoup/-/blob/master/libsoup/content-
  decoder/soup-brotli-decompressor.c

  But I'm not spotting anything that would obviously cause a 'U' to be
  randomly appended sometimes.  And why 'U'?  UINT? Unknown? User error?

  There are some interesting bug reports in GNOME about brotli in
  libsoup's bug tracker (e.g. #106, #146, #119, and #193), but none that
  match this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1945713/+subscriptions


-- 
Mailing list: https

[Desktop-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

2021-10-06 Thread Sergio Durigan Junior
** Changed in: clamav (Ubuntu)
 Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1718227

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  Invalid
Status in ethtool package in Ubuntu:
  Triaged
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  Won't Fix
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  Fix Released
Status in openvpn package in Ubuntu:
  Confirmed
Status in openvswitch package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+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 1939916] Re: FTBFS 0.99.25-0ubuntu1 error: ‘__builtin_memcpy’ writing 5 bytes into a region of size 0 overflows the destination [-Werror=stringop-overflow=]

2021-08-13 Thread Sergio Durigan Junior
Thanks for the investigative work, Athos.

As we discussed in private, I'm going to do a sync of sane-airscan from
Debian experimental, which contains the patch necessary for this fix.
The sync should also close this bug.

Cheers.

** Changed in: sane-airscan (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-airscan in Ubuntu.
https://bugs.launchpad.net/bugs/1939916

Title:
  FTBFS 0.99.25-0ubuntu1 error: ‘__builtin_memcpy’ writing 5 bytes into
  a region of size 0 overflows the destination [-Werror=stringop-
  overflow=]

Status in sane-airscan package in Ubuntu:
  Fix Released

Bug description:
  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html

  https://launchpadlibrarian.net/552666330/buildlog_ubuntu-impish-
  amd64.sane-airscan_0.99.25-0ubuntu1_BUILDING.txt.gz

  In function ‘strcpy’,
  inlined from ‘trace_open’ at airscan-trace.c:113:5:
  /usr/include/x86_64-linux-gnu/bits/string_fortified.h:79:10: error: 
‘__builtin_memcpy’ writing 5 bytes into a region of size 0 overflows the 
destination [-Werror=stringop-overflow=]
 79 |   return __builtin___strcpy_chk (__dest, __src, __glibc_objsize 
(__dest));
|  ^
  lto1: all warnings being treated as errors
  make[2]: *** [/tmp/ccRt7B21.mk:2: /tmp/cc0DKpF3.ltrans0.ltrans.o] Error 1
  lto-wrapper: fatal error: make returned 2 exit status
  compilation terminated.
  /usr/bin/ld: error: lto-wrapper failed
  collect2: error: ld returned 1 exit status
  make[1]: *** [Makefile:167: test-zeroconf] Error 1

  Upstream patch is available at https://github.com/alexpevzner/sane-
  airscan/commit/0b9be6d0c5cce6f8717eae51c218d4e8f967e79b

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-airscan/+bug/1939916/+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


Re: [Desktop-packages] [Bug 1939640] Re: libvpx FTBFS with LTO enabled

2021-08-13 Thread Sergio Durigan Junior
On Friday, August 13 2021, Graham Inggs wrote:

> libvpx was added to the '# packages not in main:' section.
>
> Please only use lto-disabled-list for packages not in main. Packages in
> main should either be fixed or worked around in the package itself.

Sorry about that.  doko had pinged me about this mistake as well.  I
have removed libvpx from lto-disabled-list and uploaded the package
again.  I will fix the issue on libvpx.

Thanks,

-- 
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0  EB2F 106D A1C8 C3CB BF14

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libvpx in Ubuntu.
https://bugs.launchpad.net/bugs/1939640

Title:
  libvpx FTBFS with LTO enabled

Status in libvpx package in Ubuntu:
  Confirmed
Status in lto-disabled-list package in Ubuntu:
  Fix Released

Bug description:
  libvpx FTBFS with LTO enabled on GCC 11, as can be seen here:

  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#ubuntu-server

  https://launchpadlibrarian.net/552670245/buildlog_ubuntu-impish-
  amd64.libvpx_1.9.0-1_BUILDING.txt.gz

  g++ -Wl,-Bsymbolic-functions -flto=auto -Wl,-z,relro -Wl,-z,now -m64 -o 
test_libvpx ivfenc.c.o md5_utils.c.o test/active_map_refresh_test.cc.o 
test/active_map_test.cc.o test/alt_ref_aq_segment_test.cc.o 
test/altref_test.cc.o test/aq_segment_test.cc.o test/bench.cc.o 
test/borders_test.cc.o test/byte_alignment_test.cc.o test/config_test.cc.o 
test/cpu_speed_test.cc.o test/cq_test.cc.o test/decode_api_test.cc.o 
test/decode_corrupted.cc.o test/decode_svc_test.cc.o 
test/decode_test_driver.cc.o test/encode_api_test.cc.o 
test/encode_test_driver.cc.o test/error_resilience_test.cc.o 
test/external_frame_buffer_test.cc.o test/frame_size_tests.cc.o 
test/invalid_file_test.cc.o test/keyframe_test.cc.o test/level_test.cc.o 
test/realtime_test.cc.o test/resize_test.cc.o test/svc_datarate_test.cc.o 
test/svc_end_to_end_test.cc.o test/svc_test.cc.o test/test_libvpx.cc.o 
test/test_vector_test.cc.o test/test_vectors.cc.o test/timestamp_test.cc.o 
test/user_priv_test.cc.o test/vp8_datarate_test.cc.o 
test/vp9_datarate_test.cc.o test/vp9_end_to_end_test.cc.o 
test/vp9_ethread_test.cc.o test/vp9_lossless_test.cc.o 
test/vp9_motion_vector_test.cc.o test/vp9_skip_loopfilter_test.cc.o 
test/y4m_test.cc.o third_party/libwebm/mkvparser/mkvparser.cc.o 
third_party/libwebm/mkvparser/mkvreader.cc.o webmdec.cc.o y4menc.c.o 
y4minput.c.o -L. -lvpx -lgtest -lpthread -lm -lpthread
  ln -sf  libvpx.so.6.3.0 vpx-vp8-vp9-x86_64-linux-v1.9.0/lib/libvpx.so.6
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x1586f): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158a5): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b2): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b7): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158dd): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x15903): more 
undefined references to `gtest_all.cc.5c9bdf8f' follow
  collect2: error: ld returned 1 exit status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1939640/+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 1939640] Re: libvpx FTBFS with LTO enabled

2021-08-12 Thread Sergio Durigan Junior
Thanks for the review, Lucas.

Uploaded:

$ dput lto-disabled-list_15_source.changes
Trying to upload package to ubuntu
Checking signature on .changes
gpg: /home/sergio/work/lto-disabled-list/lto-disabled-list_15_source.changes: 
Valid signature from 106DA1C8C3CBBF14
Checking signature on .dsc
gpg: /home/sergio/work/lto-disabled-list/lto-disabled-list_15.dsc: Valid 
signature from 106DA1C8C3CBBF14
Uploading to ubuntu (via ftp to upload.ubuntu.com):
  Uploading lto-disabled-list_15.dsc: done.
  Uploading lto-disabled-list_15.tar.xz: done.  
  Uploading lto-disabled-list_15_source.buildinfo: done.
  Uploading lto-disabled-list_15_source.changes: done.
Successfully uploaded packages.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libvpx in Ubuntu.
https://bugs.launchpad.net/bugs/1939640

Title:
  libvpx FTBFS with LTO enabled

Status in libvpx package in Ubuntu:
  Confirmed
Status in lto-disabled-list package in Ubuntu:
  New

Bug description:
  libvpx FTBFS with LTO enabled on GCC 11, as can be seen here:

  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#ubuntu-server

  https://launchpadlibrarian.net/552670245/buildlog_ubuntu-impish-
  amd64.libvpx_1.9.0-1_BUILDING.txt.gz

  g++ -Wl,-Bsymbolic-functions -flto=auto -Wl,-z,relro -Wl,-z,now -m64 -o 
test_libvpx ivfenc.c.o md5_utils.c.o test/active_map_refresh_test.cc.o 
test/active_map_test.cc.o test/alt_ref_aq_segment_test.cc.o 
test/altref_test.cc.o test/aq_segment_test.cc.o test/bench.cc.o 
test/borders_test.cc.o test/byte_alignment_test.cc.o test/config_test.cc.o 
test/cpu_speed_test.cc.o test/cq_test.cc.o test/decode_api_test.cc.o 
test/decode_corrupted.cc.o test/decode_svc_test.cc.o 
test/decode_test_driver.cc.o test/encode_api_test.cc.o 
test/encode_test_driver.cc.o test/error_resilience_test.cc.o 
test/external_frame_buffer_test.cc.o test/frame_size_tests.cc.o 
test/invalid_file_test.cc.o test/keyframe_test.cc.o test/level_test.cc.o 
test/realtime_test.cc.o test/resize_test.cc.o test/svc_datarate_test.cc.o 
test/svc_end_to_end_test.cc.o test/svc_test.cc.o test/test_libvpx.cc.o 
test/test_vector_test.cc.o test/test_vectors.cc.o test/timestamp_test.cc.o 
test/user_priv_test.cc.o test/vp8_datarate_test.cc.o 
test/vp9_datarate_test.cc.o test/vp9_end_to_end_test.cc.o 
test/vp9_ethread_test.cc.o test/vp9_lossless_test.cc.o 
test/vp9_motion_vector_test.cc.o test/vp9_skip_loopfilter_test.cc.o 
test/y4m_test.cc.o third_party/libwebm/mkvparser/mkvparser.cc.o 
third_party/libwebm/mkvparser/mkvreader.cc.o webmdec.cc.o y4menc.c.o 
y4minput.c.o -L. -lvpx -lgtest -lpthread -lm -lpthread
  ln -sf  libvpx.so.6.3.0 vpx-vp8-vp9-x86_64-linux-v1.9.0/lib/libvpx.so.6
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x1586f): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158a5): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b2): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b7): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158dd): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x15903): more 
undefined references to `gtest_all.cc.5c9bdf8f' follow
  collect2: error: ld returned 1 exit status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1939640/+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 1939640] Re: libvpx FTBFS with LTO enabled

2021-08-12 Thread Sergio Durigan Junior
Actually, I *can* reproduce the bug using git HEAD.  As it turns out I
was using an incomplete set of build flags that didn't trigger the
problem.  So yeah, the problem is still present in git HEAD.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libvpx in Ubuntu.
https://bugs.launchpad.net/bugs/1939640

Title:
  libvpx FTBFS with LTO enabled

Status in libvpx package in Ubuntu:
  Confirmed
Status in lto-disabled-list package in Ubuntu:
  New

Bug description:
  libvpx FTBFS with LTO enabled on GCC 11, as can be seen here:

  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#ubuntu-server

  https://launchpadlibrarian.net/552670245/buildlog_ubuntu-impish-
  amd64.libvpx_1.9.0-1_BUILDING.txt.gz

  g++ -Wl,-Bsymbolic-functions -flto=auto -Wl,-z,relro -Wl,-z,now -m64 -o 
test_libvpx ivfenc.c.o md5_utils.c.o test/active_map_refresh_test.cc.o 
test/active_map_test.cc.o test/alt_ref_aq_segment_test.cc.o 
test/altref_test.cc.o test/aq_segment_test.cc.o test/bench.cc.o 
test/borders_test.cc.o test/byte_alignment_test.cc.o test/config_test.cc.o 
test/cpu_speed_test.cc.o test/cq_test.cc.o test/decode_api_test.cc.o 
test/decode_corrupted.cc.o test/decode_svc_test.cc.o 
test/decode_test_driver.cc.o test/encode_api_test.cc.o 
test/encode_test_driver.cc.o test/error_resilience_test.cc.o 
test/external_frame_buffer_test.cc.o test/frame_size_tests.cc.o 
test/invalid_file_test.cc.o test/keyframe_test.cc.o test/level_test.cc.o 
test/realtime_test.cc.o test/resize_test.cc.o test/svc_datarate_test.cc.o 
test/svc_end_to_end_test.cc.o test/svc_test.cc.o test/test_libvpx.cc.o 
test/test_vector_test.cc.o test/test_vectors.cc.o test/timestamp_test.cc.o 
test/user_priv_test.cc.o test/vp8_datarate_test.cc.o 
test/vp9_datarate_test.cc.o test/vp9_end_to_end_test.cc.o 
test/vp9_ethread_test.cc.o test/vp9_lossless_test.cc.o 
test/vp9_motion_vector_test.cc.o test/vp9_skip_loopfilter_test.cc.o 
test/y4m_test.cc.o third_party/libwebm/mkvparser/mkvparser.cc.o 
third_party/libwebm/mkvparser/mkvreader.cc.o webmdec.cc.o y4menc.c.o 
y4minput.c.o -L. -lvpx -lgtest -lpthread -lm -lpthread
  ln -sf  libvpx.so.6.3.0 vpx-vp8-vp9-x86_64-linux-v1.9.0/lib/libvpx.so.6
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x1586f): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158a5): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b2): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b7): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158dd): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x15903): more 
undefined references to `gtest_all.cc.5c9bdf8f' follow
  collect2: error: ld returned 1 exit status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1939640/+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 1939640] Re: libvpx FTBFS with LTO enabled

2021-08-12 Thread Sergio Durigan Junior
Good point, Oibaf.  I've just tested git HEAD and verified that the bug
seems to have been fixed there, indeed.  I commented on the bug report.
Thanks.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libvpx in Ubuntu.
https://bugs.launchpad.net/bugs/1939640

Title:
  libvpx FTBFS with LTO enabled

Status in libvpx package in Ubuntu:
  Confirmed
Status in lto-disabled-list package in Ubuntu:
  New

Bug description:
  libvpx FTBFS with LTO enabled on GCC 11, as can be seen here:

  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#ubuntu-server

  https://launchpadlibrarian.net/552670245/buildlog_ubuntu-impish-
  amd64.libvpx_1.9.0-1_BUILDING.txt.gz

  g++ -Wl,-Bsymbolic-functions -flto=auto -Wl,-z,relro -Wl,-z,now -m64 -o 
test_libvpx ivfenc.c.o md5_utils.c.o test/active_map_refresh_test.cc.o 
test/active_map_test.cc.o test/alt_ref_aq_segment_test.cc.o 
test/altref_test.cc.o test/aq_segment_test.cc.o test/bench.cc.o 
test/borders_test.cc.o test/byte_alignment_test.cc.o test/config_test.cc.o 
test/cpu_speed_test.cc.o test/cq_test.cc.o test/decode_api_test.cc.o 
test/decode_corrupted.cc.o test/decode_svc_test.cc.o 
test/decode_test_driver.cc.o test/encode_api_test.cc.o 
test/encode_test_driver.cc.o test/error_resilience_test.cc.o 
test/external_frame_buffer_test.cc.o test/frame_size_tests.cc.o 
test/invalid_file_test.cc.o test/keyframe_test.cc.o test/level_test.cc.o 
test/realtime_test.cc.o test/resize_test.cc.o test/svc_datarate_test.cc.o 
test/svc_end_to_end_test.cc.o test/svc_test.cc.o test/test_libvpx.cc.o 
test/test_vector_test.cc.o test/test_vectors.cc.o test/timestamp_test.cc.o 
test/user_priv_test.cc.o test/vp8_datarate_test.cc.o 
test/vp9_datarate_test.cc.o test/vp9_end_to_end_test.cc.o 
test/vp9_ethread_test.cc.o test/vp9_lossless_test.cc.o 
test/vp9_motion_vector_test.cc.o test/vp9_skip_loopfilter_test.cc.o 
test/y4m_test.cc.o third_party/libwebm/mkvparser/mkvparser.cc.o 
third_party/libwebm/mkvparser/mkvreader.cc.o webmdec.cc.o y4menc.c.o 
y4minput.c.o -L. -lvpx -lgtest -lpthread -lm -lpthread
  ln -sf  libvpx.so.6.3.0 vpx-vp8-vp9-x86_64-linux-v1.9.0/lib/libvpx.so.6
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x1586f): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158a5): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b2): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b7): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158dd): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x15903): more 
undefined references to `gtest_all.cc.5c9bdf8f' follow
  collect2: error: ld returned 1 exit status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1939640/+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 1939640] Re: libvpx FTBFS with LTO enabled

2021-08-12 Thread Sergio Durigan Junior
I have filed an upstream bug report:

https://bugs.chromium.org/p/webm/issues/detail?id=1736

Unfortunately it seems like a Google account is needed in order to
view/comment on it.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libvpx in Ubuntu.
https://bugs.launchpad.net/bugs/1939640

Title:
  libvpx FTBFS with LTO enabled

Status in libvpx package in Ubuntu:
  Confirmed
Status in lto-disabled-list package in Ubuntu:
  New

Bug description:
  libvpx FTBFS with LTO enabled on GCC 11, as can be seen here:

  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#ubuntu-server

  https://launchpadlibrarian.net/552670245/buildlog_ubuntu-impish-
  amd64.libvpx_1.9.0-1_BUILDING.txt.gz

  g++ -Wl,-Bsymbolic-functions -flto=auto -Wl,-z,relro -Wl,-z,now -m64 -o 
test_libvpx ivfenc.c.o md5_utils.c.o test/active_map_refresh_test.cc.o 
test/active_map_test.cc.o test/alt_ref_aq_segment_test.cc.o 
test/altref_test.cc.o test/aq_segment_test.cc.o test/bench.cc.o 
test/borders_test.cc.o test/byte_alignment_test.cc.o test/config_test.cc.o 
test/cpu_speed_test.cc.o test/cq_test.cc.o test/decode_api_test.cc.o 
test/decode_corrupted.cc.o test/decode_svc_test.cc.o 
test/decode_test_driver.cc.o test/encode_api_test.cc.o 
test/encode_test_driver.cc.o test/error_resilience_test.cc.o 
test/external_frame_buffer_test.cc.o test/frame_size_tests.cc.o 
test/invalid_file_test.cc.o test/keyframe_test.cc.o test/level_test.cc.o 
test/realtime_test.cc.o test/resize_test.cc.o test/svc_datarate_test.cc.o 
test/svc_end_to_end_test.cc.o test/svc_test.cc.o test/test_libvpx.cc.o 
test/test_vector_test.cc.o test/test_vectors.cc.o test/timestamp_test.cc.o 
test/user_priv_test.cc.o test/vp8_datarate_test.cc.o 
test/vp9_datarate_test.cc.o test/vp9_end_to_end_test.cc.o 
test/vp9_ethread_test.cc.o test/vp9_lossless_test.cc.o 
test/vp9_motion_vector_test.cc.o test/vp9_skip_loopfilter_test.cc.o 
test/y4m_test.cc.o third_party/libwebm/mkvparser/mkvparser.cc.o 
third_party/libwebm/mkvparser/mkvreader.cc.o webmdec.cc.o y4menc.c.o 
y4minput.c.o -L. -lvpx -lgtest -lpthread -lm -lpthread
  ln -sf  libvpx.so.6.3.0 vpx-vp8-vp9-x86_64-linux-v1.9.0/lib/libvpx.so.6
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x1586f): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158a5): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b2): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b7): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158dd): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x15903): more 
undefined references to `gtest_all.cc.5c9bdf8f' follow
  collect2: error: ld returned 1 exit status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1939640/+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 1939640] Re: libvpx FTBFS with LTO enabled

2021-08-12 Thread Sergio Durigan Junior
This patch adds libvpx to the lto-disabled-list package, thus working
around the problem and disabling LTO for libvpx.

** Patch added: "fix-ftbfs-libvpx-lto.patch"
   
https://bugs.launchpad.net/ubuntu/+source/lto-disabled-list/+bug/1939640/+attachment/5517532/+files/fix-ftbfs-libvpx-lto.patch

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libvpx in Ubuntu.
https://bugs.launchpad.net/bugs/1939640

Title:
  libvpx FTBFS with LTO enabled

Status in libvpx package in Ubuntu:
  Confirmed
Status in lto-disabled-list package in Ubuntu:
  New

Bug description:
  libvpx FTBFS with LTO enabled on GCC 11, as can be seen here:

  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#ubuntu-server

  https://launchpadlibrarian.net/552670245/buildlog_ubuntu-impish-
  amd64.libvpx_1.9.0-1_BUILDING.txt.gz

  g++ -Wl,-Bsymbolic-functions -flto=auto -Wl,-z,relro -Wl,-z,now -m64 -o 
test_libvpx ivfenc.c.o md5_utils.c.o test/active_map_refresh_test.cc.o 
test/active_map_test.cc.o test/alt_ref_aq_segment_test.cc.o 
test/altref_test.cc.o test/aq_segment_test.cc.o test/bench.cc.o 
test/borders_test.cc.o test/byte_alignment_test.cc.o test/config_test.cc.o 
test/cpu_speed_test.cc.o test/cq_test.cc.o test/decode_api_test.cc.o 
test/decode_corrupted.cc.o test/decode_svc_test.cc.o 
test/decode_test_driver.cc.o test/encode_api_test.cc.o 
test/encode_test_driver.cc.o test/error_resilience_test.cc.o 
test/external_frame_buffer_test.cc.o test/frame_size_tests.cc.o 
test/invalid_file_test.cc.o test/keyframe_test.cc.o test/level_test.cc.o 
test/realtime_test.cc.o test/resize_test.cc.o test/svc_datarate_test.cc.o 
test/svc_end_to_end_test.cc.o test/svc_test.cc.o test/test_libvpx.cc.o 
test/test_vector_test.cc.o test/test_vectors.cc.o test/timestamp_test.cc.o 
test/user_priv_test.cc.o test/vp8_datarate_test.cc.o 
test/vp9_datarate_test.cc.o test/vp9_end_to_end_test.cc.o 
test/vp9_ethread_test.cc.o test/vp9_lossless_test.cc.o 
test/vp9_motion_vector_test.cc.o test/vp9_skip_loopfilter_test.cc.o 
test/y4m_test.cc.o third_party/libwebm/mkvparser/mkvparser.cc.o 
third_party/libwebm/mkvparser/mkvreader.cc.o webmdec.cc.o y4menc.c.o 
y4minput.c.o -L. -lvpx -lgtest -lpthread -lm -lpthread
  ln -sf  libvpx.so.6.3.0 vpx-vp8-vp9-x86_64-linux-v1.9.0/lib/libvpx.so.6
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x1586f): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158a5): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b2): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b7): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158dd): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x15903): more 
undefined references to `gtest_all.cc.5c9bdf8f' follow
  collect2: error: ld returned 1 exit status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1939640/+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 1939640] Re: libvpx FTBFS with LTO enabled

2021-08-12 Thread Sergio Durigan Junior
** Changed in: lto-disabled-list (Ubuntu)
 Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libvpx in Ubuntu.
https://bugs.launchpad.net/bugs/1939640

Title:
  libvpx FTBFS with LTO enabled

Status in libvpx package in Ubuntu:
  Confirmed
Status in lto-disabled-list package in Ubuntu:
  New

Bug description:
  libvpx FTBFS with LTO enabled on GCC 11, as can be seen here:

  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#ubuntu-server

  https://launchpadlibrarian.net/552670245/buildlog_ubuntu-impish-
  amd64.libvpx_1.9.0-1_BUILDING.txt.gz

  g++ -Wl,-Bsymbolic-functions -flto=auto -Wl,-z,relro -Wl,-z,now -m64 -o 
test_libvpx ivfenc.c.o md5_utils.c.o test/active_map_refresh_test.cc.o 
test/active_map_test.cc.o test/alt_ref_aq_segment_test.cc.o 
test/altref_test.cc.o test/aq_segment_test.cc.o test/bench.cc.o 
test/borders_test.cc.o test/byte_alignment_test.cc.o test/config_test.cc.o 
test/cpu_speed_test.cc.o test/cq_test.cc.o test/decode_api_test.cc.o 
test/decode_corrupted.cc.o test/decode_svc_test.cc.o 
test/decode_test_driver.cc.o test/encode_api_test.cc.o 
test/encode_test_driver.cc.o test/error_resilience_test.cc.o 
test/external_frame_buffer_test.cc.o test/frame_size_tests.cc.o 
test/invalid_file_test.cc.o test/keyframe_test.cc.o test/level_test.cc.o 
test/realtime_test.cc.o test/resize_test.cc.o test/svc_datarate_test.cc.o 
test/svc_end_to_end_test.cc.o test/svc_test.cc.o test/test_libvpx.cc.o 
test/test_vector_test.cc.o test/test_vectors.cc.o test/timestamp_test.cc.o 
test/user_priv_test.cc.o test/vp8_datarate_test.cc.o 
test/vp9_datarate_test.cc.o test/vp9_end_to_end_test.cc.o 
test/vp9_ethread_test.cc.o test/vp9_lossless_test.cc.o 
test/vp9_motion_vector_test.cc.o test/vp9_skip_loopfilter_test.cc.o 
test/y4m_test.cc.o third_party/libwebm/mkvparser/mkvparser.cc.o 
third_party/libwebm/mkvparser/mkvreader.cc.o webmdec.cc.o y4menc.c.o 
y4minput.c.o -L. -lvpx -lgtest -lpthread -lm -lpthread
  ln -sf  libvpx.so.6.3.0 vpx-vp8-vp9-x86_64-linux-v1.9.0/lib/libvpx.so.6
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x1586f): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158a5): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b2): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b7): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158dd): undefined 
reference to `gtest_all.cc.5c9bdf8f'
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x15903): more 
undefined references to `gtest_all.cc.5c9bdf8f' follow
  collect2: error: ld returned 1 exit status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvpx/+bug/1939640/+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 1939640] [NEW] libvpx FTBFS with LTO enabled

2021-08-11 Thread Sergio Durigan Junior
Public bug reported:

libvpx FTBFS with LTO enabled on GCC 11, as can be seen here:

https://people.canonical.com/~doko/ftbfs-report/test-
rebuild-20210805-impish-impish.html#ubuntu-server

https://launchpadlibrarian.net/552670245/buildlog_ubuntu-impish-
amd64.libvpx_1.9.0-1_BUILDING.txt.gz

g++ -Wl,-Bsymbolic-functions -flto=auto -Wl,-z,relro -Wl,-z,now -m64 -o 
test_libvpx ivfenc.c.o md5_utils.c.o test/active_map_refresh_test.cc.o 
test/active_map_test.cc.o test/alt_ref_aq_segment_test.cc.o 
test/altref_test.cc.o test/aq_segment_test.cc.o test/bench.cc.o 
test/borders_test.cc.o test/byte_alignment_test.cc.o test/config_test.cc.o 
test/cpu_speed_test.cc.o test/cq_test.cc.o test/decode_api_test.cc.o 
test/decode_corrupted.cc.o test/decode_svc_test.cc.o 
test/decode_test_driver.cc.o test/encode_api_test.cc.o 
test/encode_test_driver.cc.o test/error_resilience_test.cc.o 
test/external_frame_buffer_test.cc.o test/frame_size_tests.cc.o 
test/invalid_file_test.cc.o test/keyframe_test.cc.o test/level_test.cc.o 
test/realtime_test.cc.o test/resize_test.cc.o test/svc_datarate_test.cc.o 
test/svc_end_to_end_test.cc.o test/svc_test.cc.o test/test_libvpx.cc.o 
test/test_vector_test.cc.o test/test_vectors.cc.o test/timestamp_test.cc.o 
test/user_priv_test.cc.o test/vp8_datarate_test.cc.o 
test/vp9_datarate_test.cc.o test/vp9_end_to_end_test.cc.o 
test/vp9_ethread_test.cc.o test/vp9_lossless_test.cc.o 
test/vp9_motion_vector_test.cc.o test/vp9_skip_loopfilter_test.cc.o 
test/y4m_test.cc.o third_party/libwebm/mkvparser/mkvparser.cc.o 
third_party/libwebm/mkvparser/mkvreader.cc.o webmdec.cc.o y4menc.c.o 
y4minput.c.o -L. -lvpx -lgtest -lpthread -lm -lpthread
ln -sf  libvpx.so.6.3.0 vpx-vp8-vp9-x86_64-linux-v1.9.0/lib/libvpx.so.6
/usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x1586f): undefined 
reference to `gtest_all.cc.5c9bdf8f'
/usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158a5): undefined 
reference to `gtest_all.cc.5c9bdf8f'
/usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b2): undefined 
reference to `gtest_all.cc.5c9bdf8f'
/usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158b7): undefined 
reference to `gtest_all.cc.5c9bdf8f'
/usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x158dd): undefined 
reference to `gtest_all.cc.5c9bdf8f'
/usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x15903): more 
undefined references to `gtest_all.cc.5c9bdf8f' follow
collect2: error: ld returned 1 exit status

** Affects: libvpx (Ubuntu)
 Importance: Undecided
 Assignee: Sergio Durigan Junior (sergiodj)
 Status: Confirmed

** Affects: lto-disabled-list (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: ftbfs lto

** Also affects: lto-disabled-list (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libvpx in Ubuntu.
https://bugs.launchpad.net/bugs/1939640

Title:
  libvpx FTBFS with LTO enabled

Status in libvpx package in Ubuntu:
  Confirmed
Status in lto-disabled-list package in Ubuntu:
  New

Bug description:
  libvpx FTBFS with LTO enabled on GCC 11, as can be seen here:

  https://people.canonical.com/~doko/ftbfs-report/test-
  rebuild-20210805-impish-impish.html#ubuntu-server

  https://launchpadlibrarian.net/552670245/buildlog_ubuntu-impish-
  amd64.libvpx_1.9.0-1_BUILDING.txt.gz

  g++ -Wl,-Bsymbolic-functions -flto=auto -Wl,-z,relro -Wl,-z,now -m64 -o 
test_libvpx ivfenc.c.o md5_utils.c.o test/active_map_refresh_test.cc.o 
test/active_map_test.cc.o test/alt_ref_aq_segment_test.cc.o 
test/altref_test.cc.o test/aq_segment_test.cc.o test/bench.cc.o 
test/borders_test.cc.o test/byte_alignment_test.cc.o test/config_test.cc.o 
test/cpu_speed_test.cc.o test/cq_test.cc.o test/decode_api_test.cc.o 
test/decode_corrupted.cc.o test/decode_svc_test.cc.o 
test/decode_test_driver.cc.o test/encode_api_test.cc.o 
test/encode_test_driver.cc.o test/error_resilience_test.cc.o 
test/external_frame_buffer_test.cc.o test/frame_size_tests.cc.o 
test/invalid_file_test.cc.o test/keyframe_test.cc.o test/level_test.cc.o 
test/realtime_test.cc.o test/resize_test.cc.o test/svc_datarate_test.cc.o 
test/svc_end_to_end_test.cc.o test/svc_test.cc.o test/test_libvpx.cc.o 
test/test_vector_test.cc.o test/test_vectors.cc.o test/timestamp_test.cc.o 
test/user_priv_test.cc.o test/vp8_datarate_test.cc.o 
test/vp9_datarate_test.cc.o test/vp9_end_to_end_test.cc.o 
test/vp9_ethread_test.cc.o test/vp9_lossless_test.cc.o 
test/vp9_motion_vector_test.cc.o test/vp9_skip_loopfilter_test.cc.o 
test/y4m_test.cc.o third_party/libwebm/mkvparser/mkvparser.cc.o 
third_party/libwebm/mkvparser/mkvreader.cc.o webmdec.cc.o y4menc.c.o 
y4minput.c.o -L. -lvpx -lgtest -lpthread -lm -lpthread
  ln -sf  libvpx.so.6.3.0 vpx-vp8-vp9-x86_64-linux-v1.9.0/lib/libvpx.so.6
  /usr/bin/ld: /tmp/ccsyaUhJ.ltrans0.ltrans.o:(.debug_info+0x1586f): undefined 
refer

[Desktop-packages] [Bug 1910562] Re: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34

2021-04-21 Thread Sergio Durigan Junior
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux-signed-hwe-5.8 (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
https://bugs.launchpad.net/bugs/1910562

Title:
  Fans switching on and off every 10 seconds after update to kernel
  5.8.0-34

Status in linux package in Ubuntu:
  Incomplete
Status in linux-signed-hwe-5.8 package in Ubuntu:
  Invalid
Status in lm-sensors package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid

Bug description:
  After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel
  5.8.0-34 the fan on my machine started switching on (for an instant)
  and off every 10 seconds even when idle with CPU at 48/50°C.

  Switching back to previous kernel solves temporary the problem, i.e.
  fans are always off with light desktop work.

  The new behavior is really annoying and I guess not healthy for the
  fans.

  I'm on latest Dell bios, with every other package updated.

  Di something in the thermal policies change between those two kernels?
  Is it possible to go back to previous behavior ?

  Thanks in advance for help

  Machine: Dell Precison 7540, intel i7-9750

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18
  Uname: Linux 5.8.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  7 17:14:54 2021
  InstallationDate: Installed on 2020-05-06 (246 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910562/+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 1910562] Re: Fans switching on and off every 10 seconds after update to kernel 5.8.0-34

2021-04-21 Thread Sergio Durigan Junior
Hi Gabriele,

Thank you for the bug report and the help with the investigation!

I apologize that this bug was marked as Expired; this is done by an
automatic process after a period of inactivity.  Somehow this fell
through the cracks of our triage process, but now we're on it again :-).

Thank you for following up on Paride's request for further tests.  I'm
wondering here: I know that the 'sensors' command lets you specify which
chips you want to get the temperature for, and given that this problem
seems to happen every time you execute the command, then I think it's
worth trying to pinpoin which chip is causing the problem here.  Could
you please try to run the command several times, specifying the
different chip names each time, and see what happens?  Maybe there's
nothing to it, but we never know.

Another thing I was going to ask you is this: based on your comments, it
seemed to me that you were able to reproduce this problem not only in
Ubuntu, but also in other distributions.  Is that correct?  If it is, do
you think you could test a pristine Linux kernel (from
https://kernel.org)?  If the bug reproduces with it, then I would
recommend opening a bug report against the upstream Linux project.

For this specific bug, I think it's worth adding the Ubuntu Linux kernel
package and seeing what the kernel folks have to say.  Maybe they can
come up with other things you can try to determine what's going on.

I'm setting this bug status back to New and adding the Ubuntu Linux
package to it.  I'm also going to subscribe myself to this bug so that
we don't miss any more updates from you.  Thank you.

** Changed in: linux-signed-hwe-5.8 (Ubuntu)
   Status: Expired => New

** Changed in: lm-sensors (Ubuntu)
   Status: Expired => New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu.
https://bugs.launchpad.net/bugs/1910562

Title:
  Fans switching on and off every 10 seconds after update to kernel
  5.8.0-34

Status in linux-signed-hwe-5.8 package in Ubuntu:
  New
Status in lm-sensors package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid

Bug description:
  After updating via apt dist-upgrade from kernel 5.4.0-59 to kernel
  5.8.0-34 the fan on my machine started switching on (for an instant)
  and off every 10 seconds even when idle with CPU at 48/50°C.

  Switching back to previous kernel solves temporary the problem, i.e.
  fans are always off with light desktop work.

  The new behavior is really annoying and I guess not healthy for the
  fans.

  I'm on latest Dell bios, with every other package updated.

  Di something in the thermal policies change between those two kernels?
  Is it possible to go back to previous behavior ?

  Thanks in advance for help

  Machine: Dell Precison 7540, intel i7-9750

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-34-generic 5.8.0-34.37~20.04.2
  ProcVersionSignature: Ubuntu 5.8.0-34.37~20.04.2-generic 5.8.18
  Uname: Linux 5.8.0-34-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan  7 17:14:54 2021
  InstallationDate: Installed on 2020-05-06 (246 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: linux-signed-hwe-5.8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1910562/+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 1917887] Re: Network Manager OpenVPN nested connections fail to setup routes correctly

2021-03-10 Thread Sergio Durigan Junior
Unfortunately I don't know.  I would recommend commenting on the bug in
order to let upstream know that more people are affected by this
problem.  You can try posting your reproduction instructions there, and
provide more information if upstream needs it.

I am marking this bug as Triaged, although I have not reproduced it
myself.

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Triaged

** Changed in: openvpn (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1917887

Title:
  Network Manager OpenVPN nested connections fail to setup routes
  correctly

Status in OpenVPN:
  Unknown
Status in network-manager package in Ubuntu:
  Triaged
Status in openvpn package in Ubuntu:
  Invalid

Bug description:
  Setup:
  Host lan: 192.168.0.238/24
  Host Default gw: 192.168.0.1

  ip route:
  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 

  
  Primary OpenVPN (check "Use this connection only for resources on its 
network"):
  server ip: public a.b.c.d
  OpenVPN Tunnel: 192.168.1.0/24
  routes pushed: 192.168.100.0/24

  First VPN works OK:
  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 
  192.168.0.1 dev eno1 proto static scope link metric 100 
  192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 
  a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 

  
  Secondary OpenVPN  (check "Use this connection only for resources on its 
network"):
  server ip: private 192.168.100.10 
  OpenVPN Tunnel: 192.168.20.0/24
  routes pushed: 192.168.200.0/24

  Second VPN Connect OK, routing table is wrong:
  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  192.168.200.0/24 via 192.168.20.1 dev tun1 
  192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 
  192.168.0.1 dev eno1 proto static scope link metric 100 
  192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 
  a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 
  192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100 <- this is 
wrong, the openVPN#2 Gateway is not on the local lan

  Correct routing table using "sudo /usr/sbin/openvpn
  /path/to/config.openvpn" (same a Network Manager)

  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  192.168.200.0/24 via 192.168.20.1 dev tun1 
  192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 
  192.168.0.1 dev eno1 proto static scope link metric 100 
  192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 
  a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 

  It seems that Network Manager add a wrong additional route not added
  by the openvpn bin:

  192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openvpn 2.4.7-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  5 12:44:39 2021
  InstallationDate: Installed on 2021-02-19 (13 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/openvpn/+bug/1917887/+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 1917887] Re: Network Manager OpenVPN nested connections fail to setup routes correctly

2021-03-10 Thread Sergio Durigan Junior
Thank you for your reply, Riccardo.

I found the following upstream bug report that looks similar to yours:

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/204

Can you confirm that this is the same issue?

Your setup seems a bit complex to configure locally, and given that you
said you were able to reproduce this problem on more than one version of
CentOS, I am inclined to believe that, if this is indeed an issue, it
came from upstream.

** Bug watch added: 
gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #204
   https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/204

** Also affects: openvpn via
   https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/204
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1917887

Title:
  Network Manager OpenVPN nested connections fail to setup routes
  correctly

Status in OpenVPN:
  Unknown
Status in network-manager package in Ubuntu:
  Incomplete
Status in openvpn package in Ubuntu:
  Incomplete

Bug description:
  Setup:
  Host lan: 192.168.0.238/24
  Host Default gw: 192.168.0.1

  ip route:
  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 

  
  Primary OpenVPN (check "Use this connection only for resources on its 
network"):
  server ip: public a.b.c.d
  OpenVPN Tunnel: 192.168.1.0/24
  routes pushed: 192.168.100.0/24

  First VPN works OK:
  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 
  192.168.0.1 dev eno1 proto static scope link metric 100 
  192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 
  a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 

  
  Secondary OpenVPN  (check "Use this connection only for resources on its 
network"):
  server ip: private 192.168.100.10 
  OpenVPN Tunnel: 192.168.20.0/24
  routes pushed: 192.168.200.0/24

  Second VPN Connect OK, routing table is wrong:
  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  192.168.200.0/24 via 192.168.20.1 dev tun1 
  192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 
  192.168.0.1 dev eno1 proto static scope link metric 100 
  192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 
  a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 
  192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100 <- this is 
wrong, the openVPN#2 Gateway is not on the local lan

  Correct routing table using "sudo /usr/sbin/openvpn
  /path/to/config.openvpn" (same a Network Manager)

  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  192.168.200.0/24 via 192.168.20.1 dev tun1 
  192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 
  192.168.0.1 dev eno1 proto static scope link metric 100 
  192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 
  a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 

  It seems that Network Manager add a wrong additional route not added
  by the openvpn bin:

  192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openvpn 2.4.7-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  5 12:44:39 2021
  InstallationDate: Installed on 2021-02-19 (13 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/openvpn/+bug/1917887/+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 1903396] Re: libnl-route-3-200 unresolved symbols

2020-11-13 Thread Sergio Durigan Junior
For what it's worth, I created a Focal lxd container, followed the
instructions listed in the description, but could not reproduce the
issue.  I was able to successfully build wireshark without problems
here.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libnl3 in Ubuntu.
https://bugs.launchpad.net/bugs/1903396

Title:
  libnl-route-3-200 unresolved symbols

Status in libnl3 package in Ubuntu:
  Incomplete

Bug description:
  $ cat /etc/lsb-release 
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=20.04
  DISTRIB_CODENAME=focal
  DISTRIB_DESCRIPTION="Ubuntu 20.04.1 LTS"

  $ arch
  x86_64

  Getting a link error when trying to build Wireshark from source on
  Ubuntu Focal. I need to build Wireshark for plugin development.

  Steps to reproduce:
  1. Obtain source code from https://gitlab.com/wireshark/wireshark
  2. Install build dependencies as per CI ./tools/debian-setup.sh 
--install-optional --install-test-deps -y
  3. mkdir build
  4. cmake ..
  5. make
  6. Observer error:

  [ 88%] Linking CXX executable run/wireshark
  /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libnl-route-3.so: undefined reference 
to `nla_get_s32'
  /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libnl-route-3.so: undefined reference 
to `nl_strerror_l'
  collect2: error: ld returned 1 exit status
  make[2]: *** [CMakeFiles/wireshark.dir/build.make:567: run/wireshark] Error 1
  make[1]: *** [CMakeFiles/Makefile2:3713: CMakeFiles/wireshark.dir/all] Error 2
  make: *** [Makefile:141: all] Error 2

  Those two symbols are not present in any of the other libnl libraries,
  static or dynamic.

  /usr/include/libnl3/netlink/attr.h:119:extern int32_t
  nla_get_s32(const struct nlattr *);

  $ dpkg -S /usr/include/libnl3/netlink/attr.h
  libnl-3-dev:amd64: /usr/include/libnl3/netlink/attr.h

  $ dpkg -S /usr/lib/x86_64-linux-gnu/libnl-route-3.so.200.26.0
  libnl-route-3-200:amd64: /usr/lib/x86_64-linux-gnu/libnl-route-3.so.200.26.0

  I can build and install libnl-3.2.25 from source and I don't get the
  linking issues anymore if I replace the .so files installed by the
  .debs, so it's possible that there is soemthing wrong with the
  packaging of libnl-route-3-200.deb.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1903396/+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