[Bug 2078961] Re: v4l2loopback-dkms compilation fails on apt-get upgrade in Ubuntu 22.04
Same here. Prevents me from driving my Canon Camera from linux :( (used to work on 20.04) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2078961 Title: v4l2loopback-dkms compilation fails on apt-get upgrade in Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/v4l2loopback/+bug/2078961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2029480] Re: SyntaxWarnings with Python3.12
after sudo apt update && sudo apt upgrade Atteint :1 http://fr.archive.ubuntu.com/ubuntu noble InRelease Atteint :2 http://fr.archive.ubuntu.com/ubuntu noble-updates InRelease Atteint :3 http://fr.archive.ubuntu.com/ubuntu noble-backports InRelease Atteint :4 http://security.ubuntu.com/ubuntu noble-security InRelease Atteint :5 https://dl.google.com/linux/chrome/deb stable InRelease Atteint :6 https://ppa.launchpadcontent.net/tomtomtom/woeusb/ubuntu noble InRelease Atteint :7 https://ppa.launchpadcontent.net/yannubuntu/boot-repair/ubuntu noble InRelease Lecture des listes de paquets... Fait Construction de l'arbre des dépendances... Fait Lecture des informations d'état... Fait Tous les paquets sont à jour. Lecture des listes de paquets... Fait Construction de l'arbre des dépendances... Fait Lecture des informations d'état... Fait Calcul de la mise à jour... Fait Get more security updates through Ubuntu Pro with 'esm-apps' enabled: libcjson1 libavdevice60 ffmpeg libpostproc57 libavcodec60 libavutil58 libswscale7 libswresample4 libavformat60 libavfilter9 Learn more about Ubuntu Pro at https://ubuntu.com/pro 0 mis à jour, 0 nouvellement installés, 0 à enlever et 0 non mis à jour. 3 partiellement installés ou enlevés. Après cette opération, 0 o d'espace disque supplémentaires seront utilisés. Souhaitez-vous continuer ? [O/n] o Paramétrage de python3 (3.12.3-0ubuntu2) ... running python rtupdate hooks for python3.12... /usr/share/hplip/base/imagesize.py:186: SyntaxWarning: invalid escape sequence '\#' re.compile('\#define\s+\S+\s+\d+') : ('image/x-xbitmap', xbmsize), /usr/share/hplip/base/imagesize.py:187: SyntaxWarning: invalid escape sequence '\/' re.compile('\/\* XPM \*\/'): ('image/x-xpixmap', xpmsize), /usr/share/hplip/base/imagesize.py:189: SyntaxWarning: invalid escape sequence '\*' re.compile('^II\*\x00'): ('image/tiff', tiffsize), /usr/share/hplip/fax/ledmfax.py:46: SyntaxWarning: invalid escape sequence '\d' http_result_pat = re.compile(b"""HTTP/\d.\d\s(\d+)""", re.I) Traceback (most recent call last): File "/usr/bin/py3clean", line 210, in main() File "/usr/bin/py3clean", line 196, in main pfiles = set(dpf.from_package(options.package)) ^^ File "/usr/share/python3/debpython/files.py", line 55, in from_package raise Exception("cannot get content of %s" % package_name) Exception: cannot get content of inkscape error running python rtupdate hook inkscape Traceback (most recent call last): File "/usr/bin/py3clean", line 210, in main() File "/usr/bin/py3clean", line 196, in main pfiles = set(dpf.from_package(options.package)) ^^ File "/usr/share/python3/debpython/files.py", line 55, in from_package raise Exception("cannot get content of %s" % package_name) Exception: cannot get content of libglib2.0-dev-bin error running python rtupdate hook libglib2.0-dev-bin dpkg: erreur de traitement du paquet python3 (--configure) : le sous-processus paquet python3 script post-installation installé a renvoyé un état de sortie d'erreur 4 dpkg: des problèmes de dépendances empêchent la configuration de python3-distupgrade : python3-distupgrade dépend de python3:any; cependant : Le paquet python3 n'est pas encore configuré. dpkg: erreur de traitement du paquet python3-distupgrade (--configure) : problèmes de dépendances - laissé non configuré dpkg: des problèmes de dépendances empêchent la configuration de ubuntu-release-upgrader-core : ubuntu-release-upgrader-core dépend de python3:any; cependant : Le paquet python3 n'est pas encore configuré. ubuntu-release-upgrader-core dépend de python3-distupgrade (= 1:24.04.22); cependant : Le paquet python3-distupgrade n'est pas encore configuré. dpkg: erreur de traitement du paquet ubuntu-release-upgrader-core (--configure) : problèmes de dépendances - laissé non configuré Aucun rapport « apport » n'a été créé car le message d'erreur indique une erreur consécutive à un échec précédent. Aucun rapport « apport » n'a été créé car le message d'erreur indique une erreur consécutive à un échec précédent. Des erreurs ont été rencontrées pendant l'exécution : python3 python3-distupgrade ubuntu-release-upgrader-core E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a me
Re: [Bug 2058395] Re: pbuilder-dist noble create fails on jammy
There is a new version in proposed. That solved the issue On Sat, May 18, 2024, 15:45 Camden Narzt <2058...@bugs.launchpad.net> wrote: > Does Jammy have a newer dpkg available? All I see is 1.21.1. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2058395 > > Title: > pbuilder-dist noble create fails on jammy > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/2058395/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058395 Title: pbuilder-dist noble create fails on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/2058395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066041] [NEW] merge_slashes is not handled properly
Public bug reported: lsb_release: Description:Ubuntu 24.04 LTS Release:24.04 When a request has repeated slashes and the merge_slashes parameter is set to False on the Map the slashes are merged and it returns a redirect response instead of a 404 not found. This bug is know in the upstream: https://github.com/pallets/werkzeug/issues/2834 And is fixed here : https://github.com/pallets/werkzeug/pull/2860 The upstream versions affected are 2.2.0 up to 3.0.1 Fixed in 3.0.2 Here is a small snippet of code to reproduce: >>> from werkzeug import routing >>> url_map = routing.Map([routing.Rule("/url/bad", endpoint="nowhere", >>> merge_slashes=False),]) >>> x = url_map.bind("localhost", "/") >>> x.match("/url//bad") ('nowhere', {}) But it should result in a Traceback with werkzeug.exceptions.NotFound: 404 Not Found: The requested URL was not found on the server. If you entered the URL manually please check your spelling and try again. Thanks ** Affects: python-werkzeug (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066041 Title: merge_slashes is not handled properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-werkzeug/+bug/2066041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2007742] Re: Can't update stage views actor (regarding MetaWindowGroup, MetaWindowActorX11, MetaSurfaceActorX11)
Same issue on Ubuntu 24.04 noble LTS: - gnome-shell: 46.0-0ubuntu5 - linux 6.8.0-19-generic #19-Ubuntu SMP PREEMPT_DYNAMIC Thu Mar 14 14:56:46 UTC 2024 x86_64 - DisplayManager: lightdm 1.30.0-0ubuntu14 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2007742 Title: Can't update stage views actor (regarding MetaWindowGroup, MetaWindowActorX11, MetaSurfaceActorX11) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2007742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058395] Re: pbuilder-dist noble create fails on jammy
ok thanks. any workaround or should we wait for a fix ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058395 Title: pbuilder-dist noble create fails on jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/2058395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058395] [NEW] pbuilder-dist noble create fails on jammy
Public bug reported: I try to create the pbuilder setup using pbuilder-dist to build noble packages on jammy. However the command fails as follows > pbuilder-dist noble create --mirror http://miroir.univ-lorraine.fr/ubuntu/ Warning: Unknown distribution "noble". Do you want to continue [y|N]? y I: Logging to /home/u2/prudhomm/pbuilder/noble_result/last_operation.log W: cgroups are not available on the host, not using them. I: Distribution is noble. I: Current time: Tue Mar 19 16:13:52 CET 2024 I: pbuilder-time-stamp: 1710861232 I: Building the build environment I: running debootstrap /usr/sbin/debootstrap I: Target architecture can be executed I: Retrieving InRelease I: Checking Release signature I: Valid Release signature (key id F6ECB3762474EDA9D21B7022871920D1991BC93C) I: Retrieving Packages I: Validating Packages I: Resolving dependencies of required packages... I: Resolving dependencies of base packages... I: Checking component main on http://miroir.univ-lorraine.fr/ubuntu... I: Validating apt 2.7.12 I: Validating base-files 13ubuntu7 I: Validating base-passwd 3.6.3 I: Validating bash 5.2.21-2ubuntu2 I: Validating binutils 2.42-3ubuntu1 I: Validating binutils-common 2.42-3ubuntu1 I: Validating binutils-x86-64-linux-gnu 2.42-3ubuntu1 I: Validating bsdutils 1:2.39.3-6ubuntu2 I: Validating build-essential 12.10ubuntu1 I: Validating bzip2 1.0.8-5ubuntu1 I: Validating coreutils 9.4-2ubuntu4 I: Validating cpp 4:13.2.0-7ubuntu1 I: Validating cpp-13 13.2.0-17ubuntu2 I: Validating cpp-13-x86-64-linux-gnu 13.2.0-17ubuntu2 I: Validating cpp-x86-64-linux-gnu 4:13.2.0-7ubuntu1 I: Validating dash 0.5.12-6ubuntu4 I: Validating debconf 1.5.86 I: Validating debianutils 5.16 I: Validating diffutils 1:3.10-1 I: Validating dpkg 1.22.4ubuntu5 I: Validating dpkg-dev 1.22.4ubuntu5 I: Validating e2fsprogs 1.47.0-2ubuntu1 I: Validating findutils 4.9.0-5 I: Validating g++ 4:13.2.0-7ubuntu1 I: Validating g++-13 13.2.0-17ubuntu2 I: Validating g++-13-x86-64-linux-gnu 13.2.0-17ubuntu2 I: Validating g++-x86-64-linux-gnu 4:13.2.0-7ubuntu1 I: Validating gcc 4:13.2.0-7ubuntu1 I: Validating gcc-13 13.2.0-17ubuntu2 I: Validating gcc-13-base 13.2.0-17ubuntu2 I: Validating gcc-13-x86-64-linux-gnu 13.2.0-17ubuntu2 I: Validating gcc-14-base 14-20240303-1ubuntu1 I: Validating gcc-x86-64-linux-gnu 4:13.2.0-7ubuntu1 I: Validating gpgv 2.4.4-2ubuntu7 I: Validating grep 3.11-4 I: Validating gzip 1.12-1ubuntu2 I: Validating hostname 3.23+nmu2ubuntu1 I: Validating init-system-helpers 1.66ubuntu1 I: Validating libacl1 2.3.2-1 I: Validating libapt-pkg6.0 2.7.12 I: Validating libasan8 14-20240303-1ubuntu1 I: Validating libassuan0 2.5.6-1 I: Validating libatomic1 14-20240303-1ubuntu1 I: Validating libattr1 1:2.5.2-1 I: Validating libaudit-common 1:3.1.2-2 I: Validating libaudit1 1:3.1.2-2 I: Validating libbinutils 2.42-3ubuntu1 I: Validating libblkid1 2.39.3-6ubuntu2 I: Validating libbz2-1.0 1.0.8-5ubuntu1 I: Validating libc-bin 2.39-0ubuntu2 I: Validating libc-dev-bin 2.39-0ubuntu2 I: Validating libc6 2.39-0ubuntu2 I: Validating libc6-dev 2.39-0ubuntu2 I: Validating libcap-ng0 0.8.4-2 I: Validating libcap2 1:2.66-5ubuntu1 I: Validating libcc1-0 14-20240303-1ubuntu1 I: Validating libcom-err2 1.47.0-2ubuntu1 I: Validating libcrypt-dev 1:4.4.36-4 I: Validating libcrypt1 1:4.4.36-4 I: Validating libctf-nobfd0 2.42-3ubuntu1 I: Validating libctf0 2.42-3ubuntu1 I: Validating libdb5.3 5.3.28+dfsg2-4 I: Validating libdebconfclient0 0.271ubuntu1 I: Validating libdpkg-perl 1.22.4ubuntu5 I: Validating libext2fs2 1.47.0-2ubuntu1 I: Validating libffi8 3.4.6-1 I: Validating libgcc-13-dev 13.2.0-17ubuntu2 I: Validating libgcc-s1 14-20240303-1ubuntu1 I: Validating libgcrypt20 1.10.3-2 I: Validating libgdbm-compat4 1.23-5 I: Validating libgdbm6 1.23-5 I: Validating libgmp10 2:6.3.0+dfsg-2ubuntu4 I: Validating libgnutls30 3.8.3-1ubuntu1 I: Validating libgomp1 14-20240303-1ubuntu1 I: Validating libgpg-error0 1.47-3build1 I: Validating libgprofng0 2.42-3ubuntu1 I: Validating libgssapi-krb5-2 1.20.1-5build1 I: Validating libhogweed6 3.9.1-2 I: Validating libhwasan0 14-20240303-1ubuntu1 I: Validating libidn2-0 2.3.7-2 I: Validating libisl23 0.26-3 I: Validating libitm1 14-20240303-1ubuntu1 I: Validating libjansson4 2.14-2 I: Validating libk5crypto3 1.20.1-5build1 I: Validating libkeyutils1 1.6.3-3 I: Validating libkrb5-3 1.20.1-5build1 I: Validating libkrb5support0 1.20.1-5build1 I: Validating liblsan0 14-20240303-1ubuntu1 I: Validating liblz4-1 1.9.4-1 I: Validating liblzma5 5.4.5-0.3 I: Validating libmd0 1.1.0-2 I: Validating libmount1 2.39.3-6ubuntu2 I: Validating libmpc3 1.3.1-1 I: Validating libmpfr6 4.2.1-1 I: Validating libncursesw6 6.4+20240113-1ubuntu1 I: Validating libnettle8 3.9.1-2 I: Validating libnpth0 1.6-3build2 I: Validating libnsl-dev 1.3.0-3 I: Validating libnsl2 1.3.0-3 I: Validating libp11-kit0 0.25.3-4ubuntu1 I: Validating libpam-modules 1.5.2-9.1ubuntu3 I: Validating libpam-modules-bin 1.5.2-9.1ubuntu3 I: Validating libpam-runtime 1.5.2-9.1ubun
[Bug 2056625] [NEW] important regressions in gmsh 4.12
Public bug reported: Gmsh 4.12 has important regressions which are discussed here with examples and fixes https://gitlab.onelab.info/gmsh/gmsh/-/issues/2815 the current version distributed needs to be patched ** Affects: gmsh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056625 Title: important regressions in gmsh 4.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gmsh/+bug/2056625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1524523] Re: pmount unable to mount exfat file systems
Thanks ~ginggs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1524523 Title: pmount unable to mount exfat file systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pmount/+bug/1524523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1524523] Re: pmount unable to mount exfat file systems
** Merge proposal linked: https://code.launchpad.net/~mig-christophe/ubuntu/+source/pmount/+git/pmount/+merge/461165 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1524523 Title: pmount unable to mount exfat file systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pmount/+bug/1524523/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1977689] [NEW] Wrong error msg: "state file /var/lib/logrotate/status is world-readable" although it is not
Public bug reported: Ubuntu 22.04 logrotate 3.19.0-1ubuntu1.1 Every hour, I receive this wrong message: Subject:Cron >cd / && run-parts --report /etc/cron.hourly /etc/cron.hourly/logrotate: error: state file /var/lib/logrotate/status is world-readable and thus can be locked from other unprivileged users. Skipping lock acquisition... despite: # ls -al /var/lib/logrotate total 40 drwxr-x--- 2 root root 4096 Jun 5 17:17 . drwxr-xr-x 66 root root 4096 Jun 3 20:02 .. -rw-r- 1 root root 31974 Jun 5 17:17 status ** Affects: logrotate (Ubuntu) Importance: Undecided Status: New ** Description changed: Ubuntu 22.04 logrotate 3.19.0-1ubuntu1.1 Every hour, I receive this wrong message: + + Subject: Cron >cd / && run-parts --report /etc/cron.hourly /etc/cron.hourly/logrotate: error: state file /var/lib/logrotate/status is world-readable and thus can be locked from other unprivileged users. Skipping lock acquisition... despite: # ls -al /var/lib/logrotate total 40 drwxr-x--- 2 root root 4096 Jun 5 17:17 . drwxr-xr-x 66 root root 4096 Jun 3 20:02 .. -rw-r- 1 root root 31974 Jun 5 17:17 status -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1977689 Title: Wrong error msg: "state file /var/lib/logrotate/status is world- readable" although it is not To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1977689/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1964392] Re: gimp refuse to start
Hello, In fact, my installation is not quite standard, and apport is no longer installed. On the other hand, I have the problem changed a few minutes ago by replacing the obsolete PPA of otto-kesselgulasch by that of ubuntuhandbook, and by uninstalling, then reinstalling Gimp. Another error message appeared: -- christophe@Arcturus:~$ gimp GEGL-Message: 10:32:48.007: Erreur de chargement du module « /usr/lib/x86_64-linux-gnu/gegl-0.4/sdl2-display.so » : /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0: undefined symbol: wl_proxy_get_tag thread '' panicked at 'cannot access a Thread Local Storage value during or after destruction: AccessError', /usr/src/rustc-1.43.0/src/libstd/thread/local.rs:239:9 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace fatal runtime error: failed to initiate panic, error 5 gimp: fatal error: Abandon 26 ../sysdeps/unix/sysv/linux/read.c: Aucun fichier ou dossier de ce type. christophe@Arcturus:~$ export RUST_BACKTRACE=1 christophe@Arcturus:~$ gimp GEGL-Message: 10:34:44.855: Erreur de chargement du module « /usr/lib/x86_64-linux-gnu/gegl-0.4/sdl2-display.so » : /usr/lib/x86_64-linux-gnu/libSDL2-2.0.so.0: undefined symbol: wl_proxy_get_tag thread panicked while processing panic. aborting. Instruction non permise -- I think the original problem arose during a failed attempt to update FFmpeg for a recent version of Blender which I was unable to clean completely. I continue to investigate on my side, but perhaps should close the open bug since the symptoms have changed? Best regards Le jeu. 10 mars 2022 à 10:25, lotuspsychje <1964...@bugs.launchpad.net> a écrit : > Thank you for taking the time to report this bug and helping to make > Ubuntu better. Please execute the following command only once, as it > will automatically gather debugging information, in a terminal: > > apport-collect 1964392 > > When reporting bugs in the future please use apport by using 'ubuntu- > bug' and the name of the package affected. You can learn more about this > functionality at https://wiki.ubuntu.com/ReportingBugs. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1964392 > > Title: > gimp refuse to start > > Status in gimp package in Ubuntu: > New > > Bug description: > > > > ``` > GNU Image Manipulation Program version 2.10.30 > git-describe: GIMP_2_10_30 > Build: unknown rev 0 for linux > # C compiler # > Using built-in specs. > COLLECT_GCC=gcc > COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper > OFFLOAD_TARGET_NAMES=nvptx-none:hsa > OFFLOAD_TARGET_DEFAULT=1 > Target: x86_64-linux-gnu > Configured with: ../src/configure -v --with-pkgversion='Ubuntu > 9.3.0-17ubuntu1~20.04' > --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs > --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 > --prefix=/usr --with-gcc-major-version-only --program-suffix=-9 > --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id > --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix > --libdir=/usr/lib --enable-nls --enable-clocale=gnu > --enable-libstdcxx-debug --enable-libstdcxx-time=yes > --with-default-libstdcxx-abi=new --enable-gnu-unique-object > --disable-vtable-verify --enable-plugin --enable-default-pie > --with-system-zlib --with-target-system-zlib=auto --enable-objc-gc=auto > --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 > --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic > --enable-offload-targets=nvptx-none=/build/gcc-9-HskZEa/gcc-9-9.3.0/debian/tmp-nvptx/usr,hsa > --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu > --host=x86_64-linux-gnu --target=x86_64-linux-gnu > Thread model: posix > gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) > > # Libraries # > using babl version 0.1.88 (compiled against version 0.1.88) > using GEGL version 0.4.34 (compiled against version 0.4.34) > using GLib version 2.64.6 (compiled against version 2.64.6) > using GdkPixbuf version 2.40.0 (compiled against version 2.40.0) > using GTK+ version 2.24.32 (compiled against version 2.24.32) > using Pango version 1.44.7 (compiled against version 1.44.7) > using Fontconfig version 2.13.1 (compiled against version 2.13.1) > using Cairo version 1.16.0 (compiled against version 1.16.0) > > ``` > > fatal error: Erreur de segmentation > > Stack trace: > ``` > > # Stack traces obtained from PID 37855 - Thread 37855 # > > [New L
[Bug 1964392] [NEW] gimp refuse to start
Public bug reported: ``` GNU Image Manipulation Program version 2.10.30 git-describe: GIMP_2_10_30 Build: unknown rev 0 for linux # C compiler # Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/9/lto-wrapper OFFLOAD_TARGET_NAMES=nvptx-none:hsa OFFLOAD_TARGET_DEFAULT=1 Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 9.3.0-17ubuntu1~20.04' --with-bugurl=file:///usr/share/doc/gcc-9/README.Bugs --enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++,gm2 --prefix=/usr --with-gcc-major-version-only --program-suffix=-9 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-plugin --enable-default-pie --with-system-zlib --with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-offload-targets=nvptx-none=/build/gcc-9-HskZEa/gcc-9-9.3.0/debian/tmp-nvptx/usr,hsa --without-cuda-driver --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) # Libraries # using babl version 0.1.88 (compiled against version 0.1.88) using GEGL version 0.4.34 (compiled against version 0.4.34) using GLib version 2.64.6 (compiled against version 2.64.6) using GdkPixbuf version 2.40.0 (compiled against version 2.40.0) using GTK+ version 2.24.32 (compiled against version 2.24.32) using Pango version 1.44.7 (compiled against version 1.44.7) using Fontconfig version 2.13.1 (compiled against version 2.13.1) using Cairo version 1.16.0 (compiled against version 1.16.0) ``` > fatal error: Erreur de segmentation Stack trace: ``` # Stack traces obtained from PID 37855 - Thread 37855 # [New LWP 37856] [New LWP 37857] [New LWP 37858] [New LWP 37859] [New LWP 37860] [New LWP 37861] [New LWP 37862] [New LWP 37863] [New LWP 37864] [New LWP 37865] [New LWP 37866] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". __libc_read (nbytes=256, buf=0x7ffc73a50300, fd=11) at ../sysdeps/unix/sysv/linux/read.c:26 Id Target Id Frame * 1Thread 0x7f5bf6acee80 (LWP 37855) "gimp" __libc_read (nbytes=256, buf=0x7ffc73a50300, fd=11) at ../sysdeps/unix/sysv/linux/read.c:26 2Thread 0x7f5bf5fe7700 (LWP 37856) "worker"syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 3Thread 0x7f5bf57e6700 (LWP 37857) "worker"syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 4Thread 0x7f5bf4fe5700 (LWP 37858) "worker"syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 5Thread 0x7f5bf47e4700 (LWP 37859) "worker"syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 6Thread 0x7f5bebfe3700 (LWP 37860) "worker"syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 7Thread 0x7f5bf3fe3700 (LWP 37861) "worker"syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 8Thread 0x7f5bf37e2700 (LWP 37862) "worker"syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 9Thread 0x7f5bf255b700 (LWP 37863) "gmain" 0x7f5bf793c9cf in __GI___poll (fds=0x55fd5dcc42b0, nfds=1, timeout=5493) at ../sysdeps/unix/sysv/linux/poll.c:29 10 Thread 0x7f5bf1d5a700 (LWP 37864) "gdbus" 0x7f5bf793c9cf in __GI___poll (fds=0x55fd5dcd7b50, nfds=2, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 11 Thread 0x7f5bd1e9a700 (LWP 37865) "async" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 12 Thread 0x7f5bd1699700 (LWP 37866) "pool-gimp" syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 Thread 12 (Thread 0x7f5bd1699700 (LWP 37866)): #0 syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 No locals. #1 0x7f5bf7c35746 in g_cond_wait_until () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #2 0x7f5bf7bb8581 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #3 0x7f5bf7c124ca in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #4 0x7f5bf7c11ad1 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 No symbol table info available. #5 0x7f5bf7a24609 in start_thread (arg=) at pthread_create.c:477 ret = pd = unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140032332109568, -6750578873719838447, 140722248684110, 140722248684111, 140722248684256,
[Bug 1959503] [NEW] boost 1.74 2 years old and not C++20 compatible
Public bug reported: Hi boost 1.74 is 2 years old and not C++20 compatible. C++20 is out for 2 years now, G++ and Clang now support it quite well boost 1.74 is not compatible with C++20. Please add support for a Boost compatible version, like 1.77 or 1.78 Otherwise, jammy will not be a C++ dev platform of choice and will force using user installed version. That would be a pity ** Affects: boost-defaults (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1959503 Title: boost 1.74 2 years old and not C++20 compatible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/boost-defaults/+bug/1959503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1956212] Re: No Diodon applet in the Notification Zone
Hello, > So one thing is that you verify that you have https://github.com/mate- > desktop/mate-indicator-applet installed (there should be a deb package) > and the applet is actually added to the panel. In fact, the mate-indicator-applet package is not installed on either of my two machines. (this should be?) The notification zone should be provided by something else. (how to know?) However, I noticed that on the machine which does not show the diodon applet, the package ayatana-indicator-application is also present (relating to some previous use of xfce4?) Surprisingly, removing this package fix the issue! (and reinstalling it cause the issue again) This package may somehow divert the notification feature. (?) So: Bingo! There is a workaround to this issue: remove the ayatana-indicator-application package. It's good to know (but this does not provide too many explanations on the why ... ) Many thanks for your help. Best regards, Christophe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956212 Title: No Diodon applet in the Notification Zone To manage notifications about this bug go to: https://bugs.launchpad.net/diodon/+bug/1956212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1956212] Re: No Diodon applet in the Notification Zone
Le 11/01/2022 à 07:13, Oliver Sauder a écrit : > I have a feeling the issue is most likely not Diodon related but > indicator related. > > So to confirm this do you have another app which uses the libayatana- > indicator and see whether that shows up? I may need some guidance. Which app may I test? I notice that Skype Zoom Slack does not appears in the indicator zone of the "bad" mate session (but it does in the "good" mate session) This tends to confirm that this is an indicator problem. Here are applets that works well in the indication zone: NetworkManager SoundManager IBus Clock What else? > Another idea which came to my mind is that you might have a different > theme on the two different machines and it cannot find the icon in one > of them. But most likely this is not the case but wanted to throw in > there to be sure. The two machines uses the same theme "Menta" of the mate package... I tested the others proposed themes, without success. Regards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956212 Title: No Diodon applet in the Notification Zone To manage notifications about this bug go to: https://bugs.launchpad.net/diodon/+bug/1956212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1956212] Re: No Diodon applet in the Notification Zone
Le 07/01/2022 à 18:54, Oliver Sauder a écrit : > I have found this https://github.com/ubuntu-mate/ubuntu-mate- > settings/blob/master/usr/share/glib-2.0/schemas/30_ubuntu- > mate.gschema.override#L46 > > Maybe comparing those settings between the two MATE desktop you have > might reveal where the problem is. Files are the sames on the two PCs. ( /usr/share/glib-2.0/schemas/org.mate.panel.applet.notification-area.gschema.xml /usr/share/glib-2.0/schemas/net.launchpad.Diodon.gschema.xml ) Y also look at values of relating dconf keys... it's the same... :-( I can't understand. well... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956212 Title: No Diodon applet in the Notification Zone To manage notifications about this bug go to: https://bugs.launchpad.net/diodon/+bug/1956212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1956212] Re: No Diodon applet in the Notification Zone
Hello, Is there any way to check if the problem could be with the Notification Zone rather than Diodon? Regards Christophe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956212 Title: No Diodon applet in the Notification Zone To manage notifications about this bug go to: https://bugs.launchpad.net/diodon/+bug/1956212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1956212] Re: No Diodon applet in the Notification Zone
Le 05/01/2022 à 12:42, Oliver Sauder a écrit : > I tried to reproduce this on Debian Stable with Mate and the indicator > appeared without any problem. To be honest, I have to admit that I have another PC with the same versions of debian mate diodon, and on which the applet works well... There is something mysterious (magic?). It is very disturbing. > So could you try to run the following: > > dconf write /net/launchpad/diodon/plugins/active-plugins "['indicator']" > > > this ensures that the indicator plugin is enabled in your configuration. > Before trying this, I do: $ dconf read /net/launchpad/diodon/plugins/active-plugins ['indicator'] hum... Then: $ dconf write /net/launchpad/diodon/plugins/active-plugins "['indicator']" Unfortunately, it still doesn't work (I restarted the session, to be sure) ;-) Regards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956212 Title: No Diodon applet in the Notification Zone To manage notifications about this bug go to: https://bugs.launchpad.net/diodon/+bug/1956212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947192] Re: [SRU] version 0.185
Hi there, is there an ETA for u-d-t 0.185/6 in focal with the fix to use pbuilder- dist for bullseye ? thanks for your work Best regards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947192 Title: [SRU] version 0.185 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1947192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934452] Re: pbuilder-dist on focal fails with debian bullseye
ok thanks !! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934452 Title: pbuilder-dist on focal fails with debian bullseye To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1934452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947762] [NEW] package grub2-common 2.04-1ubuntu26.13 failed to install/upgrade: problèmes de dépendances - laissé non configuré
Public bug reported: the error window appears when loading the desktop ProblemType: Package DistroRelease: Ubuntu 20.04 Package: grub2-common 2.04-1ubuntu26.13 ProcVersionSignature: Ubuntu 5.11.0-38.42~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 AptOrdering: linux-modules-extra-5.11.0-36-generic:amd64: Remove linux-modules-5.11.0-36-generic:amd64: Remove linux-image-5.11.0-36-generic:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Oct 19 11:51:56 2021 ErrorMessage: problèmes de dépendances - laissé non configuré InstallationDate: Installed on 2021-03-07 (226 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-38-generic root=UUID=fd8ba57d-f002-4ff5-ac14-909ac7d7f275 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: grub2 Title: package grub2-common 2.04-1ubuntu26.13 failed to install/upgrade: problèmes de dépendances - laissé non configuré UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947762 Title: package grub2-common 2.04-1ubuntu26.13 failed to install/upgrade: problèmes de dépendances - laissé non configuré To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1947762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940920] Re: upgrade problem when using packages from security (docker.io and containerd)
Looks related to https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1939140 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940920 Title: upgrade problem when using packages from security (docker.io and containerd) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1940920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934452] [NEW] pbuilder-dist on focal fails with debian bullseye
Public bug reported: pbuilder-dist has been fixed to support debian bullseye on impish however it still fails on focal fossa which is an LTS. Would it be possible to backport ubuntu-dev-tools to focal and fix the issues with respect to bullseye ? ** Affects: ubuntu-dev-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934452 Title: pbuilder-dist on focal fails with debian bullseye To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1934452/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928981] Re: Compilation of MPI C/C++ codes fails with mpich
** Changed in: mpich (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928981 Title: Compilation of MPI C/C++ codes fails with mpich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpich/+bug/1928981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928981] Re: Compilation of MPI C/C++ codes fails with mpich
Solution: reinstall mpich ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928981 Title: Compilation of MPI C/C++ codes fails with mpich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mpich/+bug/1928981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928981] [NEW] Compilation of MPI C/C++ codes fails with mpich
Public bug reported: A few days ago, I have upgraded several machines from Ubuntu 20.10 to 21.04. Since then, I cannot compile anymore the C++ code that I am working on. The compilation (actually linking) with mpic++ fails with the following message /usr/bin/ld: /usr/lib/x86_64-linux-gnu/libmpich.a(lib_libmpich_la-ch3_init.o): undefined reference to symbol 'pthread_mutexattr_init@@GLIBC_2.2.5' /usr/bin/ld : /lib/x86_64-linux-gnu/libpthread.so.0 : erreur lors de l'ajout de symboles : DSO missing from command line collect2: error: ld returned 1 exit status I tried to add -pthread -lpthread. I now get the message /usr/bin/ld : /usr/lib/x86_64-linux-gnu/libmpich.a(ad_iwrite.o) : dans la fonction « ADIOI_GEN_aio_wait_fn » : (.text+0x137) : référence indéfinie vers « aio_suspend » /usr/bin/ld : (.text+0x191) : référence indéfinie vers « aio_error » /usr/bin/ld : (.text+0x1a4) : référence indéfinie vers « aio_return » /usr/bin/ld : /usr/lib/x86_64-linux-gnu/libmpich.a(ad_iwrite.o) : dans la fonction « ADIOI_GEN_aio_poll_fn » : (.text+0x32a) : référence indéfinie vers « aio_error » /usr/bin/ld : (.text+0x345) : référence indéfinie vers « aio_return » /usr/bin/ld : /usr/lib/x86_64-linux-gnu/libmpich.a(ad_iwrite.o) : dans la fonction « ADIOI_GEN_aio » : (.text+0x471) : référence indéfinie vers « aio_write » /usr/bin/ld : (.text+0x501) : référence indéfinie vers « aio_read » collect2: error: ld returned 1 exit status Note that my code still compiles on other machines with older Ubuntu distribution. The problem can be reproduced with the much simpler MPI example (taken from https://mpitutorial.com/tutorials/mpi-hello-world/) #include #include int main(int argc, char** argv) { // Initialize the MPI environment MPI_Init(NULL, NULL); // Get the number of processes int world_size; MPI_Comm_size(MPI_COMM_WORLD, &world_size); // Get the rank of the process int world_rank; MPI_Comm_rank(MPI_COMM_WORLD, &world_rank); // Get the name of the processor char processor_name[MPI_MAX_PROCESSOR_NAME]; int name_len; MPI_Get_processor_name(processor_name, &name_len); // Print off a hello world message printf("Hello world from processor %s, rank %d out of %d processors\n", processor_name, world_rank, world_size); // Finalize the MPI environment. MPI_Finalize(); } The compilation with the command mpicc test.c returns the error message /usr/bin/ld : /usr/lib/x86_64-linux-gnu/libmpich.a(lib_libmpich_la-init_async.o) : dans la fonction « MPIR_Finalize_async_thread » : (.text+0x4d2) : référence indéfinie vers « pthread_join » /usr/bin/ld : /usr/lib/x86_64-linux-gnu/libmpich.a(lib_libmpich_la-ch3_init.o) : dans la fonction « split_type » : (.text+0x159) : référence indéfinie vers « pthread_mutexattr_init » /usr/bin/ld : (.text+0x166) : référence indéfinie vers « pthread_mutexattr_setpshared » /usr/bin/ld : (.text+0x170) : référence indéfinie vers « pthread_mutexattr_destroy » /usr/bin/ld : /usr/lib/x86_64-linux-gnu/libmpich.a(lib_libmpich_la-ch3_init.o) : dans la fonction « MPIDI_CH3I_Shm_supported » : (.text+0x243) : référence indéfinie vers « pthread_mutexattr_init » /usr/bin/ld : (.text+0x250) : référence indéfinie vers « pthread_mutexattr_setpshared » /usr/bin/ld : (.text+0x25a) : référence indéfinie vers « pthread_mutexattr_destroy » /usr/bin/ld : /usr/lib/x86_64-linux-gnu/libmpich.a(lib_libmpich_la-ch3_win_fns.o) : dans la fonction « MPIDI_CH3I_Win_allocate_shm » : (.text+0x13a9) : référence indéfinie vers « pthread_mutexattr_init » /usr/bin/ld : (.text+0x13ca) : référence indéfinie vers « pthread_mutexattr_setpshared » /usr/bin/ld : (.text+0x1408) : référence indéfinie vers « pthread_mutexattr_destroy » /usr/bin/ld : /usr/lib/x86_64-linux-gnu/libmpich.a(mpl_thread_posix.o) : dans la fonction « MPL_thread_create » : (.text+0x70) : référence indéfinie vers « pthread_create » /usr/bin/ld : /usr/lib/x86_64-linux-gnu/libmpich.a(ad_iwrite.o) : dans la fonction « ADIOI_GEN_aio_wait_fn » : (.text+0x137) : référence indéfinie vers « aio_suspend » /usr/bin/ld : (.text+0x191) : référence indéfinie vers « aio_error » /usr/bin/ld : (.text+0x1a4) : référence indéfinie vers « aio_return » /usr/bin/ld : /usr/lib/x86_64-linux-gnu/libmpich.a(ad_iwrite.o) : dans la fonction « ADIOI_GEN_aio_poll_fn » : (.text+0x32a) : référence indéfinie vers « aio_error » /usr/bin/ld : (.text+0x345) : référence indéfinie vers « aio_return » /usr/bin/ld : /usr/lib/x86_64-linux-gnu/libmpich.a(ad_iwrite.o) : dans la fonction « ADIOI_GEN_aio » : (.text+0x471) : référence indéfinie vers « aio_write » /usr/bin/ld : (.text+0x501) : référence indéfinie vers « aio_read » My system is up-to-date: lsb_release -rd Description:Ubuntu 21.04 Release:21.04 dpkg -l "*mpich*" Souhait=inconnU/Installé/suppRimé/Purgé/H=à garder | État=Non/Installé/fichier-Config/dépaqUeté/échec-conFig/H=semi-installé/W=attend-traitement-déclenchements |/ Err?=(aucune)/besoin Réins
[Bug 1922811] UbiquityDebug.txt
apport information ** Attachment added: "UbiquityDebug.txt" https://bugs.launchpad.net/bugs/1922811/+attachment/5485361/+files/UbiquityDebug.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922811 Title: Choosing differente timezones in ubiquity instalation process and going back to previous options crashes ubiquity process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1922811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922811] Re: Choosing differente timezones in ubiquity instalation process and going back to previous options crashes ubiquity process
Hi there, first of all thank you very much for having the time to look at the bug reported. As suggested i used the "apport-collect 1922811" and I also took a screenshot of the problem. ** Attachment added: "Screenshot from 2021-04-07 23-14-13.png" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1922811/+attachment/5485365/+files/Screenshot%20from%202021-04-07%2023-14-13.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922811 Title: Choosing differente timezones in ubiquity instalation process and going back to previous options crashes ubiquity process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1922811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922811] UbiquitySyslog.txt
apport information ** Attachment added: "UbiquitySyslog.txt" https://bugs.launchpad.net/bugs/1922811/+attachment/5485364/+files/UbiquitySyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922811 Title: Choosing differente timezones in ubiquity instalation process and going back to previous options crashes ubiquity process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1922811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922811] UbiquityPartman.txt
apport information ** Attachment added: "UbiquityPartman.txt" https://bugs.launchpad.net/bugs/1922811/+attachment/5485363/+files/UbiquityPartman.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922811 Title: Choosing differente timezones in ubiquity instalation process and going back to previous options crashes ubiquity process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1922811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922811] UbiquityDm.txt
apport information ** Attachment added: "UbiquityDm.txt" https://bugs.launchpad.net/bugs/1922811/+attachment/5485362/+files/UbiquityDm.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922811 Title: Choosing differente timezones in ubiquity instalation process and going back to previous options crashes ubiquity process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1922811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922811] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1922811/+attachment/5485360/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922811 Title: Choosing differente timezones in ubiquity instalation process and going back to previous options crashes ubiquity process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1922811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922811] Re: Choosing differente timezones in ubiquity instalation process and going back to previous options crashes ubiquity process
apport information ** Tags added: apport-collected hirsute ubiquity-21.04.13 ubuntu-budgie ** Description changed: In the installation process of ubuntu budgie 21.04, after choosing different timezones and clicking return to previous options makes ubiquity crash showing the initial process options with error popup with 3 options "Quit,Continue Anyway,Try Again", the option "try again" does nothing, the option continue anyway permits the installation process but makes ubiquity crash on the final installation stage. - The iso used was Ubuntu Budgie daily-live/20210406 and the procedure was - done on a virtual machine using virtual manager. + The iso used was Ubuntu Budgie daily-live/20210406 and the procedure was done on a virtual machine using virtual manager. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu61 + Architecture: amd64 + CasperMD5CheckResult: pass + CasperVersion: 1.461 + CurrentDesktop: Budgie:GNOME + DistroRelease: Ubuntu 21.04 + InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-budgie.seed maybe-ubiquity quiet splash --- + LiveMediaBuild: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Beta amd64 (20210406) + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: ubiquity 21.04.13 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=pt_PT.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 + Tags: hirsute ubiquity-21.04.13 ubuntu-budgie + Uname: Linux 5.11.0-13-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Casper.txt" https://bugs.launchpad.net/bugs/1922811/+attachment/5485358/+files/Casper.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922811 Title: Choosing differente timezones in ubiquity instalation process and going back to previous options crashes ubiquity process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1922811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922812] UbiquityDm.txt
apport information ** Attachment added: "UbiquityDm.txt" https://bugs.launchpad.net/bugs/1922812/+attachment/5485370/+files/UbiquityDm.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922812 Title: After ubiquity shows the partition layout if we click the return to the previous options the install button gets disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1922812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922812] UbiquitySyslog.txt
apport information ** Attachment added: "UbiquitySyslog.txt" https://bugs.launchpad.net/bugs/1922812/+attachment/5485372/+files/UbiquitySyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922812 Title: After ubiquity shows the partition layout if we click the return to the previous options the install button gets disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1922812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922811] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1922811/+attachment/5485359/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922811 Title: Choosing differente timezones in ubiquity instalation process and going back to previous options crashes ubiquity process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1922811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922812] Re: After ubiquity shows the partition layout if we click the return to the previous options the install button gets disabled
Hi there, first of all thank you very much for taking time to look at the bug i reported. As suggested i used the "apport-collect 1922812" and took a screenshot aswell. ** Attachment added: "Screenshot from 2021-04-07 23-12-50.png" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1922812/+attachment/5485373/+files/Screenshot%20from%202021-04-07%2023-12-50.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922812 Title: After ubiquity shows the partition layout if we click the return to the previous options the install button gets disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1922812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922812] UbiquityPartman.txt
apport information ** Attachment added: "UbiquityPartman.txt" https://bugs.launchpad.net/bugs/1922812/+attachment/5485371/+files/UbiquityPartman.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922812 Title: After ubiquity shows the partition layout if we click the return to the previous options the install button gets disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1922812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922812] UbiquityDebug.txt
apport information ** Attachment added: "UbiquityDebug.txt" https://bugs.launchpad.net/bugs/1922812/+attachment/5485369/+files/UbiquityDebug.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922812 Title: After ubiquity shows the partition layout if we click the return to the previous options the install button gets disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1922812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922812] Re: After ubiquity shows the partition layout if we click the return to the previous options the install button gets disabled
apport information ** Tags added: apport-collected hirsute ubiquity-21.04.13 ubuntu-budgie ** Description changed: After choosing fresh install using the total of the disk and clicking next, ubiquity will show the suggest layout of the partitions if we click return to previous options the install button gets disable without the possibility of being clicked again. - Thist test was done on a live session of Ubuntu Budgie 21.04 Beta with - the iso daily-live/20210406/ on a virtual machine using virtual manager. + Thist test was done on a live session of Ubuntu Budgie 21.04 Beta with the iso daily-live/20210406/ on a virtual machine using virtual manager. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu61 + Architecture: amd64 + CasperMD5CheckResult: pass + CasperVersion: 1.461 + CurrentDesktop: Budgie:GNOME + DistroRelease: Ubuntu 21.04 + InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-budgie.seed maybe-ubiquity quiet splash --- + LiveMediaBuild: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Beta amd64 (20210406) + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: ubiquity 21.04.13 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=pt_PT.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 + Tags: hirsute ubiquity-21.04.13 ubuntu-budgie + Uname: Linux 5.11.0-13-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Casper.txt" https://bugs.launchpad.net/bugs/1922812/+attachment/5485366/+files/Casper.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922812 Title: After ubiquity shows the partition layout if we click the return to the previous options the install button gets disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1922812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922812] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1922812/+attachment/5485367/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922812 Title: After ubiquity shows the partition layout if we click the return to the previous options the install button gets disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1922812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922812] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1922812/+attachment/5485368/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922812 Title: After ubiquity shows the partition layout if we click the return to the previous options the install button gets disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1922812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922805] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1922805/+attachment/5485356/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922805 Title: On live session of ubuntu budgie, plank doesn't respect screen resolution changes (position on screen) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plank/+bug/1922805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922805] Re: On live session of ubuntu budgie, plank doesn't respect screen resolution changes (position on screen)
ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 21.04 LiveMediaBuild: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Beta amd64 (20210406) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: plank 0.11.89-3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 SuspiciousXErrors.txt: Tags: hirsute Uname: Linux 5.11.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True ** Tags added: apport-collected hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922805 Title: On live session of ubuntu budgie, plank doesn't respect screen resolution changes (position on screen) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plank/+bug/1922805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922805] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1922805/+attachment/5485357/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922805 Title: On live session of ubuntu budgie, plank doesn't respect screen resolution changes (position on screen) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plank/+bug/1922805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922812] [NEW] After ubiquity shows the partition layout if we click the return to the previous options the install button gets disabled
Public bug reported: After choosing fresh install using the total of the disk and clicking next, ubiquity will show the suggest layout of the partitions if we click return to previous options the install button gets disable without the possibility of being clicked again. Thist test was done on a live session of Ubuntu Budgie 21.04 Beta with the iso daily-live/20210406/ on a virtual machine using virtual manager. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922812 Title: After ubiquity shows the partition layout if we click the return to the previous options the install button gets disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1922812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922811] [NEW] Choosing differente timezones in ubiquity instalation process and going back to previous options crashes ubiquity process
Public bug reported: In the installation process of ubuntu budgie 21.04, after choosing different timezones and clicking return to previous options makes ubiquity crash showing the initial process options with error popup with 3 options "Quit,Continue Anyway,Try Again", the option "try again" does nothing, the option continue anyway permits the installation process but makes ubiquity crash on the final installation stage. The iso used was Ubuntu Budgie daily-live/20210406 and the procedure was done on a virtual machine using virtual manager. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922811 Title: Choosing differente timezones in ubiquity instalation process and going back to previous options crashes ubiquity process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1922811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922805] Re: On live session of ubuntu budgie, plank doesn't respect screen resolution changes (position on screen)
Hi there, I had the same bug on live session and after installation on a virtual machine using virtual manager. Here is the screenshot that shows how plank behaves after changing the monitor resolution: https://imgur.com/a/0Nc5Mxl If plank is closed and reopen it behaves the normal way. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922805 Title: On live session of ubuntu budgie, plank doesn't respect screen resolution changes (position on screen) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plank/+bug/1922805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920615] Re: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net when symlinks are used for configuration and/or
Thnaks for your backchannel with the upstream. :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920615 Title: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net when symlinks are used for configuration and/or database folders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1920615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920615] Re: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net when symlinks are used for configuration and/or
** Summary changed: - getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net + getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net when symlinks are used for configuration and/or database folders -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920615 Title: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net when symlinks are used for configuration and/or database folders To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1920615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920615] Re: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net
@Lucas Kanashiro (lucaskanashiro) Thanks for taking the time to read and answer it. You're right, it is not a bug per se, more a serious shortcoming. If we install the required packages, everything works fine. However, if we modify one of the aforementioned folders to a symlink which points to another folder with the same contents, then the issue described in this thread pops up. This is the first time I encounter this strange "symlink sensitivity" by any Ubuntu package and I believe this should never happen on Linux. I understand that clamav is also implemented on Windows and this could explain this undesired behavior on Linux. I have already posted a "feature request" on the clamav- de...@lists.clamav.net mailing list, but there is no response so far. @Utkarsh Gupta (utkarsh) Try this: # sudo systemctl stop clamav-daemon # sudo systemctl stop clamav-freshclam # sudo mv -f /etc/clamav /etc/clamav.sav # sudo ln -fsv /etc/clamav.sav /etc/clamav '/etc/clamav' -> '/etc/clamav.sav' # sudo systemctl restart clamav-daemon # sudo systemctl restart clamav-freshclam # sudo systemctl status clamav-freshclam ● clamav-freshclam.service - ClamAV virus database updater Loaded: loaded (/lib/systemd/system/clamav-freshclam.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2021-03-23 18:45:15 CET; 5s ago Docs: man:freshclam(1) man:freshclam.conf(5) https://www.clamav.net/documents Process: 2460871 ExecStart=/usr/bin/freshclam -d --foreground=true (code=exited, status=2) Main PID: 2460871 (code=exited, status=2) Mar 23 18:45:15 host systemd[1]: Started ClamAV virus database updater. Mar 23 18:45:15 host freshclam[2460871]: ERROR: Can't open/parse the config file /etc/clamav/freshclam.conf Mar 23 18:45:15 host systemd[1]: clamav-freshclam.service: Main process exited, code=exited, status=2/INVALIDARGUMENT Mar 23 18:45:15 host systemd[1]: clamav-freshclam.service: Failed with result 'exit-code'. Then back to normal: # sudo rm -f /etc/clamav # sudo mv -f /etc/clamav.sav /etc/clamav # sudo systemctl restart clamav-daemon # sudo systemctl restart clamav-freshclam # sudo systemctl status clamav-freshclam ● clamav-freshclam.service - ClamAV virus database updater Loaded: loaded (/lib/systemd/system/clamav-freshclam.service; enabled; vendor preset: enabled) Active: active (running) since Tue 2021-03-23 18:55:53 CET; 5s ago Docs: man:freshclam(1) man:freshclam.conf(5) https://www.clamav.net/documents Main PID: 2511510 (freshclam) Tasks: 1 (limit: 18975) Memory: 2.1M CGroup: /system.slice/clamav-freshclam.service └─2511510 /usr/bin/freshclam -d --foreground=true Mar 23 18:55:53 host systemd[1]: Started ClamAV virus database updater. Mar 23 18:55:53 host freshclam[2511510]: Tue Mar 23 18:55:53 2021 -> ClamAV update process started at Tue Mar 23 18:55:53 2021 Mar 23 18:55:53 host freshclam[2511510]: Tue Mar 23 18:55:53 2021 -> daily.cld database is up to date (version: 26118, sigs: 3965203, f-level: 63,> Mar 23 18:55:53 host freshclam[2511510]: Tue Mar 23 18:55:53 2021 -> main.cld database is up to date (version: 59, sigs: 4564902, f-level: 60, bui> Mar 23 18:55:53 host freshclam[2511510]: Tue Mar 23 18:55:53 2021 -> bytecode.cvd database is up to date (version: 333, sigs: 92, f-level: 63, bui> -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920615 Title: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1920615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920615] Re: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net
I have found the cause of the issue: clamav does not support symlinks for any of the following: - /etc/clamav - /etc/ssl - /etc/ssl/certs - /var/lib/clamav If I make sure there is no symlink anymore for any of the above folders, then the issue is worked around: # freshclam --debug --verbose ... * Trying 104.16.219.84:443... * Connected to database.clamav.net (104.16.219.84) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /etc/ssl/certs/ca-certificates.crt * CApath: /etc/ssl/certs * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 * ALPN, server accepted to use h2 * Server certificate: * subject: C=US; ST=CA; L=San Francisco; O=Cloudflare, Inc.; CN=sni.cloudflaressl.com * start date: Aug 15 00:00:00 2020 GMT * expire date: Aug 15 12:00:00 2021 GMT * subjectAltName: host "database.clamav.net" matched cert's "database.clamav.net" * issuer: C=US; O=Cloudflare, Inc.; CN=Cloudflare Inc ECC CA-3 * SSL certificate verify ok. * Using HTTP2, server supports multi-use * Connection state changed (HTTP/2 confirmed) * Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0 * Using Stream ID: 1 (easy handle 0x55631ca7a1e0) > GET /safebrowsing.cvd HTTP/2 Host: database.clamav.net user-agent: ClamAV/0.103.0 (OS: linux-gnu, ARCH: x86_64, CPU: x86_64) accept: */* I'm not sure whether this symlink sensitivity is by design or a bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920615 Title: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1920615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920615] Re: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net
** Description changed: Ubuntu 21.04 clamav-freshclam: 0.103.0+dfsg-3.1 + + /etc/clamav/freshclam.conf: + -- + DatabaseOwner clamav + UpdateLogFile /var/log/clamav/freshclam.log + LogVerbose false + LogSyslog false + LogFacility LOG_LOCAL6 + LogFileMaxSize 0 + LogRotate true + LogTime true + Foreground false + Debug true + MaxAttempts 5 + DatabaseDirectory /var/lib/clamav + DNSDatabaseInfo current.cvd.clamav.net + ConnectTimeout 30 + ReceiveTimeout 30 + TestDatabases yes + ScriptedUpdates yes + CompressLocalDatabase no + SafeBrowsing true + Bytecode true + NotifyClamd /etc/clamav/clamd.conf + # Check for new database 24 times a day + Checks 24 + DatabaseMirror db.fr.clamav.net + DatabaseMirror database.clamav.net Commands executed as root: # systemctl stop clamav-freshclam # freshclam --debug --verbose Sat Mar 20 16:00:21 2021 -> ClamAV update process started at Sat Mar 20 16:00:21 2021 Sat Mar 20 16:00:21 2021 -> *Current working dir is /var/lib/clamav/ Sat Mar 20 16:00:21 2021 -> *Querying current.cvd.clamav.net Sat Mar 20 16:00:21 2021 -> *TTL: 1623 Sat Mar 20 16:00:21 2021 -> *fc_dns_query_update_info: Software version from DNS: 0.103.1 Sat Mar 20 16:00:21 2021 -> *Current working dir is /var/lib/clamav/ Sat Mar 20 16:00:21 2021 -> *check_for_new_database_version: No local copy of "daily" database. Sat Mar 20 16:00:21 2021 -> *query_remote_database_version: daily.cvd version from DNS: 26115 Sat Mar 20 16:00:21 2021 -> daily database available for download (remote version: 26115) Sat Mar 20 16:00:21 2021 -> *Retrieving https://database.clamav.net/daily.cvd Sat Mar 20 16:00:21 2021 -> *downloadFile: Download source: https://database.clamav.net/daily.cvd Sat Mar 20 16:00:21 2021 -> *downloadFile: Download destination: /var/lib/clamav/tmp.5ee08cf0a0/clamav-746b5f842a022ff02206be76e0c77fe8.tmp * Trying 104.16.219.84:443... * Connected to database.clamav.net (104.16.219.84) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * error setting certificate verify locations: CAfile: /etc/ssl/certs/ca-certificates.crt CApath: /etc/ssl/certs * Closing connection 0 Sat Mar 20 16:00:21 2021 -> ^Download failed (77) Sat Mar 20 16:00:21 2021 -> ^ Message: Problem with the SSL CA cert (path? access rights?) Sat Mar 20 16:00:21 2021 -> ^getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd Sat Mar 20 16:00:21 2021 -> Trying again in 5 secs... The alleged "error setting certificate verify locations" is false: # sudo -u clamav -EH ls -al /etc/ssl/certs/ca-certificates.crt -rw-r--r-- 1 root root 186336 Mar 15 08:45 /etc/ssl/certs/ca-certificates.crt # sudo -u clamav -EH ls -al /etc/ssl/certs total 556 drwxr-xr-x 3 root root 12288 Mar 15 08:45 . ... Also, it is possible to contact the website as clamav user, meaning there is no CA access issue for that user: # sudo -u clamav -EH wget https://database.clamav.net --2021-03-20 16:21:12-- https://database.clamav.net/ Resolving database.clamav.net (database.clamav.net)... 104.16.219.84, 104.16.218.84, 2606:4700::6810:da54, ... Connecting to database.clamav.net (database.clamav.net)|104.16.219.84|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: ‘index.html’ index.html [ <=> ] 1.14K --.-KB/sin 0s 2021-03-20 16:21:12 (21.3 MB/s) - ‘index.html’ saved [1166] # more index.html - - http://www.clamav.net"; http-equiv="Refresh"> - ClamAV database mirror + + http://www.clamav.net"; http-equiv="Refresh"> + ClamAV database mirror + src="//www.clamav.net/assets/clamav-trademark.png"> You reached one of ClamAV virus database mirrors: http://database.clamav.net";>database.clamav.net + style="font-style: italic;" href="http://database.clamav.net";>database.clamav.net is a round robin record that tries to equally balance the traffic between all the database mirrors. For a complete list of our mirrors visit http://www.clamav.net/mirrors.html";>http://www.clamav.net/mirrors.html + href="http://www.clamav.net/mirrors.html";>http://www.clamav.net/mirrors.html You'll be redirected to ClamAV home page (http://www.clamav.net";>http://www.clamav.net) in 15 + href="http://www.clamav.net";>http://www.clamav.net) in 15 seconds... This mirror is sponsored by This is a very strange issue. Any suggestion on how to debug/workaround that issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920615 Title: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+so
[Bug 1920615] Re: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net
There is no such issue on another Ubuntu device with the **exact** same SSL and freshclam configurations and located on the same private network as the failing device sharing the same IP public address. Is it possible that cloudflare enforces a limit on the number of devices which are allowed to download from https://database.clamav.net/daily.cvd? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920615 Title: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1920615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1920615] [NEW] getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net
Public bug reported: Ubuntu 21.04 clamav-freshclam: 0.103.0+dfsg-3.1 Commands executed as root: # systemctl stop clamav-freshclam # freshclam --debug --verbose Sat Mar 20 16:00:21 2021 -> ClamAV update process started at Sat Mar 20 16:00:21 2021 Sat Mar 20 16:00:21 2021 -> *Current working dir is /var/lib/clamav/ Sat Mar 20 16:00:21 2021 -> *Querying current.cvd.clamav.net Sat Mar 20 16:00:21 2021 -> *TTL: 1623 Sat Mar 20 16:00:21 2021 -> *fc_dns_query_update_info: Software version from DNS: 0.103.1 Sat Mar 20 16:00:21 2021 -> *Current working dir is /var/lib/clamav/ Sat Mar 20 16:00:21 2021 -> *check_for_new_database_version: No local copy of "daily" database. Sat Mar 20 16:00:21 2021 -> *query_remote_database_version: daily.cvd version from DNS: 26115 Sat Mar 20 16:00:21 2021 -> daily database available for download (remote version: 26115) Sat Mar 20 16:00:21 2021 -> *Retrieving https://database.clamav.net/daily.cvd Sat Mar 20 16:00:21 2021 -> *downloadFile: Download source: https://database.clamav.net/daily.cvd Sat Mar 20 16:00:21 2021 -> *downloadFile: Download destination: /var/lib/clamav/tmp.5ee08cf0a0/clamav-746b5f842a022ff02206be76e0c77fe8.tmp * Trying 104.16.219.84:443... * Connected to database.clamav.net (104.16.219.84) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * error setting certificate verify locations: CAfile: /etc/ssl/certs/ca-certificates.crt CApath: /etc/ssl/certs * Closing connection 0 Sat Mar 20 16:00:21 2021 -> ^Download failed (77) Sat Mar 20 16:00:21 2021 -> ^ Message: Problem with the SSL CA cert (path? access rights?) Sat Mar 20 16:00:21 2021 -> ^getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd Sat Mar 20 16:00:21 2021 -> Trying again in 5 secs... The alleged "error setting certificate verify locations" is false: # sudo -u clamav -EH ls -al /etc/ssl/certs/ca-certificates.crt -rw-r--r-- 1 root root 186336 Mar 15 08:45 /etc/ssl/certs/ca-certificates.crt # sudo -u clamav -EH ls -al /etc/ssl/certs total 556 drwxr-xr-x 3 root root 12288 Mar 15 08:45 . ... Also, it is possible to contact the website as clamav user, meaning there is no CA access issue for that user: # sudo -u clamav -EH wget https://database.clamav.net --2021-03-20 16:21:12-- https://database.clamav.net/ Resolving database.clamav.net (database.clamav.net)... 104.16.219.84, 104.16.218.84, 2606:4700::6810:da54, ... Connecting to database.clamav.net (database.clamav.net)|104.16.219.84|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: ‘index.html’ index.html [ <=> ] 1.14K --.-KB/sin 0s 2021-03-20 16:21:12 (21.3 MB/s) - ‘index.html’ saved [1166] # more index.html http://www.clamav.net"; http-equiv="Refresh"> ClamAV database mirror You reached one of ClamAV virus database mirrors: http://database.clamav.net";>database.clamav.net is a round robin record that tries to equally balance the traffic between all the database mirrors. For a complete list of our mirrors visit http://www.clamav.net/mirrors.html";>http://www.clamav.net/mirrors.html You'll be redirected to ClamAV home page (http://www.clamav.net";>http://www.clamav.net) in 15 seconds... This mirror is sponsored by This is a very strange issue. Any suggestion on how to debug/workaround that issue? ** Affects: clamav (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920615 Title: getcvd: Can't download daily.cvd from https://database.clamav.net/daily.cvd despite correct connection to https://database.clamav.net To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1920615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874662] Re: Corrupted installation medium
I got this problem. With ubuntu 20.04 and 20.10. The downloaded iso was ok. Checked by SHA-256 hash sum. Bootable usb device made with Rufus under Windows 8.1. Got bloc errors : 2. But no problems found with chkdsk. The check at the linux set up start gives 1 error too. The squashfs errors occur. With ubuntu 20.10. On the usb device there is a directory casper with a large file filesystem.squashfs. Compare for that file the SHA-256 hash sum between original iso and usb device one : got different. But sizes was the same. Just rewrite this erroneous file from the original iso to the usb device. Ok with a simple drag and drop. Usb device file SHA-256 hash sum now OK. Check at the linux set up start now OK. And finally linux install was OK, with no more the SQUASHFS errors. Chris. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874662 Title: Corrupted installation medium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1874662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1919341] Re: kernel package linux-headers-5.11.0-11-generic is not supported
Solved by: xtables-addons-common: 3.13-1ubuntu2 xtables-addons-dkms: 3.13-1ubuntu2 Preparing to unpack .../xtables-addons-common_3.13-1ubuntu2_amd64.deb ... Unpacking xtables-addons-common (3.13-1ubuntu2) over (3.13-1) ... Preparing to unpack .../xtables-addons-dkms_3.13-1ubuntu2_all.deb ... ... Building initial module for 5.11.0-11-generic Done. xt_ACCOUNT.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ compat_xtables.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_pknock.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_CHAOS.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_DELUDE.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_DHCPMAC.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_DNETMAP.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_ECHO.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_IPMARK.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_LOGMARK.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_PROTO.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_SYSRQ.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_TARPIT.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_condition.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_fuzzy.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_geoip.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_iface.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_ipp2p.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_ipv4options.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_length2.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_lscan.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_psd.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ xt_quota2.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.11.0-11-generic/updates/dkms/ depmod DKMS: i
[Bug 1919341] [NEW] kernel package linux-headers-5.11.0-11-generic is not supported
Public bug reported: Ubuntu 21.04 xtables-addons-common: 3.13-1 xtables-addons-dkms: 3.13-1 Upgrading the linux kernel leads to: Setting up linux-headers-5.11.0-11-generic (5.11.0-11.12) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 5.11.0-11-generic Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area... make -j8 KERNELRELEASE=5.11.0-11-generic -C /lib/modules/5.11.0-11-generic/build M=/var/lib/dkms/xtables-addons/3.13/build/extensions XA_ABSTOPSRCDIR=/var/lib/dkms/xtables- addons/3.13/build XA_TOPSRCDIR=/var/lib/dkms/xtables-addons/3.13/build V=1 modules ; find /var/lib/dkms/xtables-addons/3.13/build -name '*.ko' -exec mv -v {} /var/lib/dkms/ xtables-addons/3.13/build \;... ERROR (dkms apport): kernel package linux-headers-5.11.0-11-generic is not supported Error! Build of xt_ACCOUNT.ko failed for: 5.11.0-11-generic (x86_64) Make sure the name of the generated module is correct and at the root of the build directory, or consult make.log in the build directory /var/lib/dkms/xtables-addons/3.13/build/ for more information. ...done. /var/lib/dkms/xtables-addons/3.13/build/make.log is attached. ** Affects: xtables-addons (Ubuntu) Importance: Undecided Status: New ** Attachment added: "make.log" https://bugs.launchpad.net/bugs/1919341/+attachment/5477272/+files/make.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919341 Title: kernel package linux-headers-5.11.0-11-generic is not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xtables-addons/+bug/1919341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918107] [NEW] renderPM can't set font
Public bug reported: Since the `gsfonts` dependency was removed in bug #1862641, some reportlab functionalities are failing. It can be reproduced with a simple example. First, ensure that `gsfonts` package is not installed. In python3: ``` from reportlab.graphics.barcode import createBarcodeDrawing barcode = createBarcodeDrawing('EAN13', value='1234') barcode.asString('png') ``` This leads to the following traceback: ``` Warn: Can't find .pfb for face 'Times-Roman' Traceback (most recent call last): File "/usr/lib/python3/dist-packages/reportlab/graphics/renderPM.py", line 242, in _setFont gs.setFont(fontName,fontSize) ValueError: _renderPM.gstate_setFont: Can't find font! During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/reportlab/graphics/renderPM.py", line 248, in _setFont _renderPM.makeT1Font(fontName,f.face.findT1File(),f.encoding.vector,open_and_read) TypeError: makeT1Font() argument 2 must be str, not None During handling of the above exception, another exception occurred: Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/reportlab/graphics/shapes.py", line 854, in asString return renderPM.drawToString(self, fmt=format,showBoundary=getattr(self,'showBorder', File "/usr/lib/python3/dist-packages/reportlab/graphics/renderPM.py", line 685, in drawToString drawToFile(d,s,fmt=fmt, dpi=dpi, bg=bg, configPIL=configPIL) File "/usr/lib/python3/dist-packages/reportlab/graphics/renderPM.py", line 680, in drawToFile c = drawToPMCanvas(d, dpi=dpi, bg=bg, configPIL=configPIL, showBoundary=showBoundary) File "/usr/lib/python3/dist-packages/reportlab/graphics/renderPM.py", line 666, in drawToPMCanvas draw(d, c, 0, 0, showBoundary=showBoundary) File "/usr/lib/python3/dist-packages/reportlab/graphics/renderPM.py", line 51, in draw R.draw(renderScaledDrawing(drawing), canvas, x, y, showBoundary=showBoundary) File "/usr/lib/python3/dist-packages/reportlab/graphics/renderbase.py", line 204, in draw self.initState(x,y) #this is the push() File "/usr/lib/python3/dist-packages/reportlab/graphics/renderPM.py", line 98, in initState self.applyState() File "/usr/lib/python3/dist-packages/reportlab/graphics/renderPM.py", line 92, in applyState self._canvas.setFont(s['fontName'], s['fontSize']) File "/usr/lib/python3/dist-packages/reportlab/graphics/renderPM.py", line 399, in setFont _setFont(self._gs,fontName,fontSize) File "/usr/lib/python3/dist-packages/reportlab/graphics/renderPM.py", line 251, in _setFont raise RenderPMError("Can't setFont(%s) missing the T1 files?\nOriginally %s: %s" % (fontName,s1,s2)) reportlab.graphics.renderPM.RenderPMError: Can't setFont(Times-Roman) missing the T1 files? Originally : makeT1Font() argument 2 must be str, not None ``` After installing the `gsfonts` package, the traceback does not occurs and the code works as expected. lsb release: Ubuntu 20.04.1 LTS python3-renderpm:amd64 3.5.34-1ubuntu1 ** Affects: python-reportlab (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918107 Title: renderPM can't set font To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-reportlab/+bug/1918107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916633] [NEW] pbuilder-dist bullseye create fails
Public bug reported: the command pbuilder-dist bullseye create fails with the following error at the very end I: redirecting /dev/ptmx to /dev/pts/ptmx I: installing dummy policy-rc.d Ign:1 http://security.debian.org bullseye/updates InRelease Err:2 http://security.debian.org bullseye/updates Release 404 Not Found [IP: 151.101.130.132 80] Get:3 http://deb.debian.org/debian bullseye-proposed-updates InRelease [39.4 kB] Hit:4 http://deb.debian.org/debian bullseye InRelease Get:5 http://deb.debian.org/debian bullseye/non-free amd64 Packages [98.7 kB] Get:6 http://deb.debian.org/debian bullseye/contrib amd64 Packages [51.0 kB] Reading package lists... E: The repository 'http://security.debian.org bullseye/updates Release' does not have a Release file. I: unmounting dev/ptmx filesystem I: unmounting dev/pts filesystem I: unmounting dev/shm filesystem I: unmounting proc filesystem I: unmounting sys filesystem I: cleaning the build env I: removing directory /var/cache/pbuilder/build/2585888 and its subdirectories ** Affects: ubuntu-dev-tools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916633 Title: pbuilder-dist bullseye create fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1916633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912883] Re: Please sync aacgain from debian testing
This software is uses by QtGain (GUI for mp3gain, vorbisgain and aacgain). QtGain is in Ubuntu. So it's a lack for it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912883 Title: Please sync aacgain from debian testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1912883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912883] [NEW] Please sync aacgain from debian testing
Public bug reported: [needs-packaging] aacgain Aacgain is a sound utility wich normalize sound for aac/m4a files. It is in debian 9, 10, 11 and sid, but it is never sync in Ubuntu (since a least 16.04). URL: https://debian.pkgs.org/11/multimedia-main-amd64/aacgain_1.9-dmo4_amd64.deb.html URL: http://aacgain.altosdesign.com/ License: GPL Notes: ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912883 Title: Please sync aacgain from debian testing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1912883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899750] Re: Conflict wich libnvidia-compute-450
Hello, Thank you for the fix. Sorry I'm newbie, but where can i find the package pycuda - 2020.1~dfsg-1 Thank you -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899750 Title: Conflict wich libnvidia-compute-450 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycuda/+bug/1899750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910932] Re: clang-10 crash on ubuntu 20.10
** Attachment added: "cpp code that crashes clang-10" https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-10/+bug/1910932/+attachment/5451544/+files/qs_adr-b8a3e6.cpp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910932 Title: clang-10 crash on ubuntu 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-10/+bug/1910932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910932] [NEW] clang-10 crash on ubuntu 20.10
Public bug reported: On ubuntu 20.10 clang-10 (and 11) crash on some C++ code which compile fine the same compiler on focal(20.04) ** Affects: llvm-toolchain-10 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "shell script generated by clang" https://bugs.launchpad.net/bugs/1910932/+attachment/5451543/+files/qs_adr-b8a3e6.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910932 Title: clang-10 crash on ubuntu 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-10/+bug/1910932/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910863] Re: Clang 11 crash on Ubuntu 20.10: sorry, this include generates a translation unit too large for Clang to process.
** Summary changed: - Clang 11 crashes on Ubuntu 20.10: sorry, this include generates a translation unit too large for Clang to process. + Clang 11 crash on Ubuntu 20.10: sorry, this include generates a translation unit too large for Clang to process. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910863 Title: Clang 11 crash on Ubuntu 20.10: sorry, this include generates a translation unit too large for Clang to process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-11/+bug/1910863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910863] Re: Clang 11 crashes on Ubuntu 20.10: sorry, this include generates a translation unit too large for Clang to process.
** Attachment added: "shell script generated by clang" https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-11/+bug/1910863/+attachment/5451541/+files/qs_adr-d57687.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910863 Title: Clang 11 crashes on Ubuntu 20.10: sorry, this include generates a translation unit too large for Clang to process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-11/+bug/1910863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910863] Re: Clang 11 crashes on Ubuntu 20.10: sorry, this include generates a translation unit too large for Clang to process.
** Attachment added: "cpp code that crashes clang-11" https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-11/+bug/1910863/+attachment/5451542/+files/qs_adr-d57687.cpp -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910863 Title: Clang 11 crashes on Ubuntu 20.10: sorry, this include generates a translation unit too large for Clang to process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-11/+bug/1910863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910863] [NEW] Clang 11 crashes on Ubuntu 20.10: sorry, this include generates a translation unit too large for Clang to process.
Public bug reported: clang11 provided by ubuntu on 20.10 crashes on some C++ code with the message: sorry, this include generates a translation unit too large for Clang to process. Installing clang-11 from llvm fixes the issue. This issue occur only on 20.10 ** Affects: llvm-toolchain-11 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910863 Title: Clang 11 crashes on Ubuntu 20.10: sorry, this include generates a translation unit too large for Clang to process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-11/+bug/1910863/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909369] [NEW] linux-headers-5.10.3-051003-generic is not supported
Public bug reported: > $ lsb_release -rd Description:Ubuntu 20.04.1 LTS Release:20.04 > $ sudo apt-cache policy bcmwl-kernel-source bcmwl-kernel-source: Installé : (aucun) Candidat : 6.30.223.271+bdcom-0ubuntu5 Table de version : 6.30.223.271+bdcom-0ubuntu5 500 500 http://fr.archive.ubuntu.com/ubuntu focal/restricted amd64 Packages Hello, I tried to install a wireless network adapter broadcom BCM4360, i nned to install the package bcmwl-kernel-source but when i try to install it i have the following error : "ERROR (dkms apport): kernel package linux-headers-5.10.3-051003-generic is not supported Error! Bad return status for module build on kernel: 5.10.3-051003-generic (x86_64) " ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source (not installed) Uname: Linux 5.10.3-051003-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Dec 26 21:16:07 2020 InstallationDate: Installed on 2020-01-05 (356 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/usr/bin/zsh SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909369 Title: linux-headers-5.10.3-051003-generic is not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1909369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883352] Re: impossible to migrate from 18.04 to 20.04
This is still not working even after removing all ppa except the official Ubuntu ones and two that I cannot remove for unknown reasons. decebal@decebal-PORTEGE-Z30-B:~$ grep -Rn --include=\*.list ^[^\#] /etc/apt/ /etc/apt/sources.list:5:deb http://fr.archive.ubuntu.com/ubuntu/ bionic main restricted /etc/apt/sources.list:10:deb http://fr.archive.ubuntu.com/ubuntu/ bionic-updates main restricted /etc/apt/sources.list:16:deb http://fr.archive.ubuntu.com/ubuntu/ bionic universe /etc/apt/sources.list:18:deb http://fr.archive.ubuntu.com/ubuntu/ bionic-updates universe /etc/apt/sources.list:26:deb http://fr.archive.ubuntu.com/ubuntu/ bionic multiverse /etc/apt/sources.list:28:deb http://fr.archive.ubuntu.com/ubuntu/ bionic-updates multiverse /etc/apt/sources.list:36:deb http://fr.archive.ubuntu.com/ubuntu/ bionic-backports main restricted universe multiverse /etc/apt/sources.list:43:deb http://archive.canonical.com/ubuntu bionic partner /etc/apt/sources.list:46:deb http://fr.archive.ubuntu.com/ubuntu/ bionic-security main restricted /etc/apt/sources.list:48:deb http://fr.archive.ubuntu.com/ubuntu/ bionic-security universe /etc/apt/sources.list:50:deb http://fr.archive.ubuntu.com/ubuntu/ bionic-security multiverse /etc/apt/sources.list.d/playonlinux.list:1:deb http://deb.playonlinux.com/ bionic main /etc/apt/sources.list.d/skype-stable.list:1:deb [arch=amd64] https://repo.skype.com/deb stable main -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883352 Title: impossible to migrate from 18.04 to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1883352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1662244] Re: lightdm causes all greeters to fail to start
Upgrading to (K)Ubuntu 18.04.5 LTS basically broke the system as X was not restarting correctly (black screen instead of lightdm display or even infinite loop of X crashes based on BIOS/EFI config). This is critical for non-savvy users as my parents. The issue is the same as can be seen in /var/log/lightdm/seat0-greeter.log with repeated messages like **MEMORY-ERROR***: unity-greeter[1647]: GSlice: failed to allocate 2040 bytes (alignment: 2048)... **MEMORY-ERROR***: unity-greeter[1647]: GSlice: failed to allocate 2040 bytes (alignment: 2048)... **MEMORY-ERROR***: unity-greeter[1647]: GSlice: failed to allocate 2040 bytes (alignment: 2048)... The workaround is indded updating the memlock limits as described above (adding the 2 lines of the above comment to /etc/security/limits.con). Thanks for the workaround :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1662244 Title: lightdm causes all greeters to fail to start To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1662244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899750] Re: Conflict wich libnvidia-compute-450
Sorry it's libnvidia-compute-435 not libnvidia-compute-350 so I must downgrade to nvidia-driver-435? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899750 Title: Conflict wich libnvidia-compute-450 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycuda/+bug/1899750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899750] [NEW] Conflict wich libnvidia-compute-450
Public bug reported: This package depends from libnvidia-compute-350 but ubuntu-drivers recommends the nvidia-driver-450 drivers for my cuda card (GeForce GTX 1080). Will a new version of this package link against libnvidia-compute-450 or must I downgrade my driver to nvidia-driver-350? Is-it really a bug? Thank you Sorry for my poor english ** Affects: pycuda (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899750 Title: Conflict wich libnvidia-compute-450 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pycuda/+bug/1899750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890611] Re: Client cannot connect to remote mysql-server when the latter is configured with ssl parameters using a public CA
Same issue with mysql-server 8.0.21-1 on groovy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1890611 Title: Client cannot connect to remote mysql-server when the latter is configured with ssl parameters using a public CA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1890611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890611] Re: Client cannot connect to remote mysql-server when the latter is configured with ssl parameters using a public CA
Sorry: I have inadvertently tested with a port matching another service (853 instead of 3306), so my previous post must be ignored. This issue is still there, even on groovy. Let me answer your questions again: 0) with a service answering correctly to TLS connections requests, we get with a wildcard server certificate: ... SSL_connect:SSLv3/TLS write finished --- Certificate chain 0 s:CN = *.domain i:C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3 -BEGIN CERTIFICATE- As my first post shows, there is an initial error in the connection preventing openssl to show the CA used or the server certificate: ... SSL_connect:error in error 139858538362176:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../ssl/record/ssl3_record.c:331: --- no peer certificate available --- 1) The full SSL configuration (besides the 3 parameters already described in my first post) also includes the following parameters which are IMHO not relevant because his issue still happens if I remove them: ssl-cipher=... tls-version=... require_secure_transport=ON 2) You don't seem to understand this issue. The client don't need special configuration, other than at least one matching cipher and required TLS version if they are specified on the server side. 3)I have already tried that: same issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1890611 Title: Client cannot connect to remote mysql-server when the latter is configured with ssl parameters using a public CA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1890611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890611] Re: Client cannot connect to remote mysql-server when the latter is configured with ssl parameters using a public CA
** Changed in: mysql-8.0 (Ubuntu) Status: Fix Released => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1890611 Title: Client cannot connect to remote mysql-server when the latter is configured with ssl parameters using a public CA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1890611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890611] Re: Client cannot connect to remote mysql-server when the latter is configured with ssl parameters using a public CA
1. already shared in my first post 2. You don't seem to understand this issue. Not a problem, because in the meantime, I have upgraded to groovy with: mysql-server-8.0: Installed: 8.0.21-0ubuntu4 Now I get: ... SSL_connect:SSLv3/TLS write finished --- Certificate chain 0 s:CN = *.domain i:C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3 -BEGIN CERTIFICATE- This issue has been solved on groovy. FYI, the systemd service continues to show an incorrect warning: [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed ** Changed in: mysql-8.0 (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1890611 Title: Client cannot connect to remote mysql-server when the latter is configured with ssl parameters using a public CA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1890611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890611] Re: Client cannot connect to remote mysql-server when the latter is configured with ssl parameters using a public CA
I suggest you try to configure your mysql-server with SSL parameters using a public CA, since this is the use case of this issue. ** Changed in: mysql-8.0 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1890611 Title: Client cannot connect to remote mysql-server when the latter is configured with ssl parameters using a public CA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1890611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890611] Re: Client cannot connect to remote mysql-server when the latter is configured with ssl parameters using a public CA
I changed the title to better reflect the core issue of this thread. ** Summary changed: - mysql-server does not take into account configured ssl parameters + Client cannot connect to remote mysql-server when the latter is configured with ssl parameters using a public CA -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1890611 Title: Client cannot connect to remote mysql-server when the latter is configured with ssl parameters using a public CA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1890611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890611] Re: mysql-server does not take into account configured ssl parameters
I meant let's encrypt as a public certificate ... authority. Also, if it is of any help: mysql> status -- mysql Ver 8.0.21-0ubuntu4 for Linux on x86_64 ((Ubuntu)) Connection id: 31 Current database: Current user: root@localhost SSL:Not in use Current pager: stdout Using outfile: '' Using delimiter:; Server version: 8.0.21-0ubuntu4 (Ubuntu) Protocol version: 10 Connection: Localhost via UNIX socket Server characterset:utf8mb4 Db characterset:utf8mb4 Client characterset:utf8mb4 Conn. characterset:utf8mb4 UNIX socket:/var/run/mysqld/mysqld.sock Binary data as: Hexadecimal Uptime: 15 hours 45 min 24 sec -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1890611 Title: mysql-server does not take into account configured ssl parameters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1890611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890611] Re: mysql-server does not take into account configured ssl parameters
I appreciate the time you took to answer. However, your example is a different use case: you're using a self-signed certificate with a private CA. My use case use a public CA (namely let's encrypt, but it could be anything else). In my setup, client and servers are on totally different machines. They should be able to communicate over TLS like you're using your browser right now to communicate over https with the remote server https://bugs.launchpad.net/ which happens to also use let's encrypt as a public certificate. I am aware that the official mysql doc only displays SSL examples using only a private CA. I suspect this issue to come from an inability to perform correctly with a public CA/certificate. ** Changed in: mysql-8.0 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1890611 Title: mysql-server does not take into account configured ssl parameters To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1890611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891020] Re: No IPv4 iptable kernel module can be loaded
Yes, the issue is solved: # uname -r 5.8.0-16-generic # lsmod | grep iptable_ iptable_filter 16384 1 iptable_nat16384 1 nf_nat 49152 3 ip6table_nat,iptable_nat,xt_MASQUERADE iptable_mangle 16384 1 ip_tables 32768 13 iptable_filter,iptable_nat,iptable_mangle x_tables 45056 19 ebtables,ip6table_filter,xt_conntrack,iptable_filter,xt_NFLOG,xt_tcpudp,xt_addrtype,xt_CHECKSUM,ip6t_rt,xt_geoip,ip6_tables,ipt_REJECT,ip_tables,xt_limit,xt_hl,ip6table_mangle,xt_MASQUERADE,ip6t_REJECT,iptable_mangle # systemctl status netfilter-persistent ● netfilter-persistent.service - netfilter persistent configuration Loaded: loaded (/lib/systemd/system/netfilter-persistent.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/netfilter-persistent.service.d └─iptables.conf Active: active (exited) since Thu 2020-08-13 00:45:54 CEST; 6min ago Docs: man:netfilter-persistent(8) Main PID: 1073 (code=exited, status=0/SUCCESS) Tasks: 0 (limit: 18998) Memory: 0B CGroup: /system.slice/netfilter-persistent.service Aug 13 00:45:53 samsung5-ubuntu systemd[1]: Starting netfilter persistent configuration... Aug 13 00:45:53 samsung5-ubuntu netfilter-persistent[1084]: run-parts: executing /usr/share/netfilter-persistent/plugins.d/15-ip4tables start Aug 13 00:45:54 samsung5-ubuntu netfilter-persistent[1084]: run-parts: executing /usr/share/netfilter-persistent/plugins.d/25-ip6tables start Aug 13 00:45:54 samsung5-ubuntu systemd[1]: Finished netfilter persistent configuration. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891020 Title: No IPv4 iptable kernel module can be loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891020] Re: No IPv4 iptable kernel module can be loaded
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891020 Title: No IPv4 iptable kernel module can be loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891020] Re: No IPv4 iptable kernel module can be loaded
Something has changed since my first post: now, right after boot, iptable_filter is loaded, but not the other IPv4 iptable kernel modules: # lsmod | grep iptable_ iptable_filter 16384 0 ip_tables 32768 1 iptable_filter x_tables 45056 14 ebtables,ip6table_filter,xt_conntrack,iptable_filter,xt_NFLOG,xt_tcpudp,ip6t_rt,xt_geoip,ip6_tables,ip_tables,xt_limit,xt_hl,ip6table_mangle,ip6t_REJECT # systemctl status netfilter-persistent ● netfilter-persistent.service - netfilter persistent configuration Loaded: loaded (/lib/systemd/system/netfilter-persistent.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/netfilter-persistent.service.d └─iptables.conf Active: failed (Result: exit-code) since Wed 2020-08-12 10:09:33 CEST; 5min ago Docs: man:netfilter-persistent(8) Process: 1108 ExecStart=/usr/sbin/netfilter-persistent start (code=exited, status=1/FAILURE) Main PID: 1108 (code=exited, status=1/FAILURE) Aug 12 10:09:32 samsung5-ubuntu systemd[1]: Starting netfilter persistent configuration... Aug 12 10:09:33 samsung5-ubuntu netfilter-persistent[1113]: run-parts: executing /usr/share/netfilter-persistent/plugins.d/15-ip4tables start Aug 12 10:09:33 samsung5-ubuntu netfilter-persistent[1126]: iptables-restore v1.8.5 (legacy): iptables-restore: unable to initialize table 'mangle' Aug 12 10:09:33 samsung5-ubuntu netfilter-persistent[1126]: Error occurred at line: 2 Aug 12 10:09:33 samsung5-ubuntu netfilter-persistent[1126]: Try `iptables-restore -h' or 'iptables-restore --help' for more information. Aug 12 10:09:33 samsung5-ubuntu netfilter-persistent[1113]: run-parts: /usr/share/netfilter-persistent/plugins.d/15-ip4tables exited with return code 2 Aug 12 10:09:33 samsung5-ubuntu netfilter-persistent[1113]: run-parts: executing /usr/share/netfilter-persistent/plugins.d/25-ip6tables start Aug 12 10:09:33 samsung5-ubuntu systemd[1]: netfilter-persistent.service: Main process exited, code=exited, status=1/FAILURE Aug 12 10:09:33 samsung5-ubuntu systemd[1]: netfilter-persistent.service: Failed with result 'exit-code'. Aug 12 10:09:33 samsung5-ubuntu systemd[1]: Failed to start netfilter persistent configuration. It is possible to load the other IPv4 iptable kernel modules, but it seems useless since the iptables cannot be loaded: # for module in iptable_nat iptable_mangle > do > insmod > /lib/modules/5.8.0-12-generic/kernel/net/ipv4/netfilter/${module}.ko > done # lsmod | grep iptable_ iptable_mangle 16384 0 iptable_nat16384 0 iptable_filter 16384 0 nf_nat 49152 2 ip6table_nat,iptable_nat ip_tables 32768 3 iptable_filter,iptable_nat,iptable_mangle x_tables 45056 15 ebtables,ip6table_filter,xt_conntrack,iptable_filter,xt_NFLOG,xt_tcpudp,ip6t_rt,xt_geoip,ip6_tables,ip_tables,xt_limit,xt_hl,ip6table_mangle,ip6t_REJECT,iptable_mangle # systemctl restart netfilter-persistent Job for netfilter-persistent.service failed because the control process exited with error code. See "systemctl status netfilter-persistent.service" and "journalctl -xe" for details. # systemctl status netfilter-persistent ● netfilter-persistent.service - netfilter persistent configuration Loaded: loaded (/lib/systemd/system/netfilter-persistent.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/netfilter-persistent.service.d └─iptables.conf Active: failed (Result: exit-code) since Wed 2020-08-12 10:18:55 CEST; 3s ago Docs: man:netfilter-persistent(8) Process: 5762 ExecStart=/usr/sbin/netfilter-persistent start (code=exited, status=1/FAILURE) Main PID: 5762 (code=exited, status=1/FAILURE) Aug 12 10:18:55 samsung5-ubuntu systemd[1]: Starting netfilter persistent configuration... Aug 12 10:18:55 samsung5-ubuntu netfilter-persistent[5764]: run-parts: executing /usr/share/netfilter-persistent/plugins.d/15-ip4tables start Aug 12 10:18:55 samsung5-ubuntu netfilter-persistent[5766]: iptables-restore v1.8.5 (legacy): iptables-restore: unable to initialize table 'mangle' Aug 12 10:18:55 samsung5-ubuntu netfilter-persistent[5766]: Error occurred at line: 2 Aug 12 10:18:55 samsung5-ubuntu netfilter-persistent[5766]: Try `iptables-restore -h' or 'iptables-restore --help' for more information. Aug 12 10:18:55 samsung5-ubuntu netfilter-persistent[5764]: run-parts: /usr/share/netfilter-persistent/plugins.d/15-ip4tables exited with return code 2 Aug 12 10:18:55 samsung5-ubuntu netfilter-persistent[5764]: run-parts: executing /usr/share/netfilter-persistent/plugins.d/25-ip6tables start Aug 12 10:18:55 samsung5-ubuntu systemd[1]: netfilter-persistent.service: Main process exited, code=exited, status=1/FAILURE Aug 12 10:18:55 samsung5-ubuntu systemd[1]: netfilter-persistent.service: Failed with result 'exit-code'. Aug 12 10:18:55 samsung5-ubuntu systemd[1]: Failed to start netfilter persistent con
[Bug 1891020] Re: No IPv4 iptable kernel module can be loaded
** Summary changed: - iptable_filter and ip6table_filter cannot be loaded with 5.8 kernel + No IPv4 iptable kernel module can be loaded -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891020 Title: No IPv4 iptable kernel module can be loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890961] Re: can't release upgrade from 19.10
Hello, after looking at the /var/log/dist-upgrade/ i saw that there are many errors coming from Qgis software, and postgresql10 with extension postgis. I uninstalled completely Qgis and postgresql10 with extension postgis, and tried again to do a : do-release-upgrade and now, i don't have problem and make the release upgrade normally. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890961 Title: can't release upgrade from 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1890961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890961] [NEW] can't release upgrade from 19.10
Public bug reported: Hello, after i update and upgrade (full-upgrade) via apt, i make a: do-release-upgrade and the beginning of the release-upgrade begins. After it has changed the /etc/apt/sources.list for add sources of focal fossa, it does calculate the modifications, and then write "impossible to evaluate the release upgrade. A non solvable problem came while calculate the release upgrade" After have open the apt.log, i see : Starting pkgProblemResolver with broken count: 16 and : Starting 2 pkgProblemResolver with broken count: 16 Here are the next lines: Investigating (0) libqt5core5a:amd64 < 5.12.4+dfsg-4ubuntu1.1 -> 5.12.8+dfsg-0ubuntu1 @ii umU Ib > Broken libqt5core5a:amd64 Casse on libqtcore4:amd64 < 4:4.8.7+dfsg-7ubuntu3 @ii gK > (< 4:4.8.7+dfsg-20~) Considering libqtcore4:amd64 54 as a solution to libqt5core5a:amd64 811 Added libqtcore4:amd64 to the remove list Fixing libqt5core5a:amd64 via remove of libqtcore4:amd64 MarkDelete libqtcore4:amd64 < 4:4.8.7+dfsg-7ubuntu3 @ii gK > FU=0 Investigating (0) libgcc1:amd64 < 1:9.2.1-9ubuntu2 -> 1:10-20200411-0ubuntu1 @ii umU Ib > Broken libgcc1:amd64 Est en conflit avec on libgcc1:i386 < 1:9.2.1-9ubuntu2 -> 1:10-20200411-0ubuntu1 @ii umU Ib > Considering libgcc1:i386 3 as a solution to libgcc1:amd64 154 Added libgcc1:i386 to the remove list Conflicts//Breaks against version 1:9.2.1-9ubuntu2 for libgcc1 but that is not InstVer, ignoring Fixing libgcc1:amd64 via remove of libgcc1:i386 MarkDelete libgcc1:i386 < 1:9.2.1-9ubuntu2 -> 1:10-20200411-0ubuntu1 @ii umU Ib > FU=0 Investigating (0) libuno-sal3:amd64 < none -> 1:6.4.4-0ubuntu0.20.04.1 @un uN Ib > Broken libuno-sal3:amd64 Casse on uno-libs3:amd64 < 6.3.5-0ubuntu0.19.10.1 @ii mK > Considering uno-libs3:amd64 -8 as a solution to libuno-sal3:amd64 104 Added uno-libs3:amd64 to the remove list Fixing libuno-sal3:amd64 via remove of uno-libs3:amd64 MarkDelete uno-libs3:amd64 < 6.3.5-0ubuntu0.19.10.1 @ii mK > FU=0 Investigating (0) gdal-data:amd64 < 2.4.2+dfsg-1build2 -> 3.0.4+dfsg-1build3 @ii umU Ib > Broken gdal-data:amd64 Casse on libgdal20:amd64 < 2.4.2+dfsg-1build2 @ii mK > (< 2.5.0~) Considering libgdal20:amd64 10 as a solution to gdal-data:amd64 22 Added libgdal20:amd64 to the remove list Fixing gdal-data:amd64 via remove of libgdal20:amd64 MarkDelete libgdal20:amd64 < 2.4.2+dfsg-1build2 @ii mK > FU=0 Investigating (0) libqtdbus4:amd64 < 4:4.8.7+dfsg-7ubuntu3 @ii gK Ib > Broken libqtdbus4:amd64 Dépend on libqtcore4:amd64 < 4:4.8.7+dfsg-7ubuntu3 @ii gR > (= 4:4.8.7+dfsg-7ubuntu3) Considering libqtcore4:amd64 54 as a solution to libqtdbus4:amd64 12 Removing libqtdbus4:amd64 rather than change libqtcore4:amd64 MarkDelete libqtdbus4:amd64 < 4:4.8.7+dfsg-7ubuntu3 @ii gK Ib > FU=0 Investigating (0) libqtgui4:amd64 < 4:4.8.7+dfsg-7ubuntu3 @ii gK Ib > Broken libqtgui4:amd64 Dépend on libqtcore4:amd64 < 4:4.8.7+dfsg-7ubuntu3 @ii gR > (= 4:4.8.7+dfsg-7ubuntu3) Considering libqtcore4:amd64 54 as a solution to libqtgui4:amd64 11 Removing libqtgui4:amd64 rather than change libqtcore4:amd64 MarkDelete libqtgui4:amd64 < 4:4.8.7+dfsg-7ubuntu3 @ii gK Ib > FU=0 Investigating (0) libqt4-xml:amd64 < 4:4.8.7+dfsg-7ubuntu3 @ii gK Ib > Broken libqt4-xml:amd64 Dépend on libqtcore4:amd64 < 4:4.8.7+dfsg-7ubuntu3 @ii gR > (= 4:4.8.7+dfsg-7ubuntu3) Considering libqtcore4:amd64 54 as a solution to libqt4-xml:amd64 10 Removing libqt4-xml:amd64 rather than change libqtcore4:amd64 MarkDelete libqt4-xml:amd64 < 4:4.8.7+dfsg-7ubuntu3 @ii gK Ib > FU=0 IInvestigating (0) libqt4-declarative:amd64 < 4:4.8.7+dfsg-7ubuntu3 @ii gK Ib > Broken libqt4-declarative:amd64 Dépend on libqtcore4:amd64 < 4:4.8.7+dfsg-7ubuntu3 @ii gR > (= 4:4.8.7+dfsg-7ubuntu3) Considering libqtcore4:amd64 54 as a solution to libqt4-declarative:amd64 10 Removing libqt4-declarative:amd64 rather than change libqtcore4:amd64 MarkDelete libqt4-declarative:amd64 < 4:4.8.7+dfsg-7ubuntu3 @ii gK Ib > FU=0 Investigating (0) qt-at-spi:amd64 < 0.4.0-9 @ii gK Ib > Broken qt-at-spi:amd64 Dépend on libqtcore4:amd64 < 4:4.8.7+dfsg-7ubuntu3 @ii gR > (>= 4:4.8~) Considering libqtcore4:amd64 54 as a solution to qt-at-spi:amd64 8 Removing qt-at-spi:amd64 rather than change libqtcore4:amd64 MarkDelete qt-at-spi:amd64 < 0.4.0-9 @ii gK Ib > FU=0 Investigating (0) libqt4-network:amd64 < 4:4.8.7+dfsg-7ubuntu3 @ii gK Ib > Broken libqt4-network:amd64 Dépend on libqtcore4:amd64 < 4:4.8.7+dfsg-7ubuntu3 @ii gR > (= 4:4.8.7+dfsg-7ubuntu3) Considering libqtcore4:amd64 54 as a solution to libqt4-network:amd64 7 Removing libqt4-network:amd64 rather than change libqtcore4:amd64 MarkDelete libqt4-network:amd64 < 4:4.8.7+dfsg-7ubuntu3 @ii gK Ib > FU=0 Investigating (0) libqt4-sql:amd64 < 4:4.8.7+dfsg-7ubuntu3 @ii gK Ib > Broken libqt4-sql:amd64 Dépend on libqtcore4:amd64 < 4:4.8.7+dfsg-7ubuntu3 @ii gR > (= 4:4.8.7+dfsg-7ubuntu3) Considering libqtcore4:amd64 54 as a solution to libqt4-sql:amd64 5 Removing li
[Bug 1887891] Re: dav/davs behind proxy doesn't work
It's done : https://gitlab.gnome.org/GNOME/gvfs/-/issues/495 ** Bug watch added: gitlab.gnome.org/GNOME/gvfs/-/issues #495 https://gitlab.gnome.org/GNOME/gvfs/-/issues/495 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887891 Title: dav/davs behind proxy doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1887891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887891] [NEW] dav/davs behind proxy doesn't work
Public bug reported: I'm using Ubuntu 20.04 behind manual proxy. When I want to connect on a server with webdav, I have a message : "Erreur HTTP : Erreur de résolution de cloud.rochodc.com : Nom ou service inconnu" -> DNS Error Name ou service not known I can connect to a webdav server on my private network. I can connect to cloud.rochodc.com with Firefox and the proxy I use for the system. I can connect to cloud.rochodc.com with Ubuntu 18.04 with the same proxy and nautilus. Online account with parameters doesen't work at all. JC ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Jul 17 08:22:05 2020 InstallationDate: Installed on 2020-07-09 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887891 Title: dav/davs behind proxy doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1887891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887553] [NEW] fresh installation bug to install grub2
Public bug reported: failed to install grub2 after fresh installation of ubuntu mate 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445 Date: Tue Jul 14 18:51:55 2020 InstallCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz root=UUID=CCF3-468C iso-scan/filename=/ubuntu-mate-20.04-desktop-amd64.iso file=/cdrom/preseed/ubuntustudio.seed noprompt quiet splash --- maybe-ubiquity debian-installer/language=fr keyboard-configuration/layoutcode?=fr keyboard-configuration/variantcode?=oss LiveMediaBuild: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANGUAGE=fr_FR.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15 ubuntustudio -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887553 Title: fresh installation bug to install grub2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1887553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880041] Re: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later
I confirm the same issue with kernel 5.3.0-53-generic #47~18.04.1 Using Ubuntu 18.04.4 on a Lenovo IdeaPad-S540-14API CPU0: AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx (family: 0x17, model: 0x18, stepping: 0x1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880041 Title: Failing to shutdown/power off or reboot on AMD Ryzen CPUs on kernel versions 5.3.0-52 and later To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe/+bug/1880041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875181] Re: dgesdd gets stuck for size 40+
I experienced the same problem with the routine LAPACKE_dsyevd with a 6x6 matrix. I tried to check the eigenvalues with GNU/Octave and .. it got stuck as well! The code was working a few days ago with Ubuntu 19.10 before the upgrade to 20.04. The backtrace is: #0 0x7599f70b in sched_yield () at ../sysdeps/unix/syscall-template.S:78 #1 0x7614cfa5 in exec_blas_async_wait () from /usr/lib/x86_64-linux-gnu/libopenblas.so.0 #2 0x7614d07c in exec_blas () from /usr/lib/x86_64-linux-gnu/libopenblas.so.0 #3 0x75f693cc in dsymv_thread_U () from /usr/lib/x86_64-linux-gnu/libopenblas.so.0 #4 0x75f251ae in dsymv_ () from /usr/lib/x86_64-linux-gnu/libopenblas.so.0 #5 0x77ad09f5 in dsytd2_ () from /usr/lib/x86_64-linux-gnu/libopenblas.so.0 #6 0x77ad536d in dsytrd_ () from /usr/lib/x86_64-linux-gnu/libopenblas.so.0 #7 0x77ac66cc in dsyevd_ () from /usr/lib/x86_64-linux-gnu/libopenblas.so.0 #8 0x75cd76e0 in LAPACKE_dsyevd_work () from /usr/lib/x86_64-linux-gnu/liblapacke.so.3 #9 0x75cd70b7 in LAPACKE_dsyevd () from /usr/lib/x86_64-linux-gnu/liblapacke.so.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875181 Title: dgesdd gets stuck for size 40+ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lapack/+bug/1875181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1876815] Re: wifi issue with 5.4.0-28 lowlatency kernel
thank you for your quick answer Problem is fixed after removing backport-iwlwifi-dkms driver ... seems I was the bug ! thank you for your help ! take care for your health, bye Le 05/05/2020 à 02:52, You-Sheng Yang a écrit : > Please remove backport-iwlwifi-dkms for this adapter. You don't need it > as in tree driver has better support. > > ** Tags added: hwe-networking-wifi > > ** Also affects: backport-iwlwifi-dkms (Ubuntu) > Importance: Undecided > Status: New > > ** No longer affects: linux (Ubuntu) > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876815 Title: wifi issue with 5.4.0-28 lowlatency kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1876815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876815] [NEW] wifi issue with 5.4.0-28 lowlatency kernel
Public bug reported: hello, after fresh ubuntustudio 20.04 install, everything worked out the box But after 5.4.0-28 lowlatency kernel update, wifi does not work properly Connection to the wifi modem is ok, but network is abnormaly slow. Come bake to the previous kernel 5.4.0-26 fix the issue (both kernel using same backport-iwlwifi-dkms driver) Hope this will help, and the issue will be fixed in the next released, be safe, bye ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-lowlatency 5.4.0.28.33 ProcVersionSignature: Ubuntu 5.4.0-28.32-lowlatency 5.4.30 Uname: Linux 5.4.0-28-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: transistor 2177 F pulseaudio /dev/snd/controlC2: transistor 2177 F pulseaudio /dev/snd/controlC1: transistor 2177 F pulseaudio /dev/snd/controlC0: transistor 2177 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon May 4 22:59:26 2020 InstallationDate: Installed on 2020-04-27 (7 days ago) InstallationMedia: Ubuntu-Studio 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Micro-Star International Co., Ltd. GL75 9SE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-lowlatency root=UUID=5f15-7a39-4245-8672-0f0aec9592f7 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-28-lowlatency N/A linux-backports-modules-5.4.0-28-lowlatency N/A linux-firmware 1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/25/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17E5IMS.103 dmi.board.asset.tag: Default string dmi.board.name: MS-17E5 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17E5IMS.103:bd06/25/2019:svnMicro-StarInternationalCo.,Ltd.:pnGL759SE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17E5:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: GL dmi.product.name: GL75 9SE dmi.product.sku: 17E5.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876815 Title: wifi issue with 5.4.0-28 lowlatency kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876815/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876504] [NEW] Gdebi close when trying to install a .deb with right-clic
Public bug reported: In focal(20.04), gdebi 0.9.5.7+nmu3 has a problem. In a terminal : sudo gdebi xxx.deb works (but no graphic mode) In a terminal : sudo gdebi-gtk launch gdebi. Then, in the graphic UI, choose a .deb file ("file > open"), then clic on "install" and it's works. BUT right-clic on the .deb, then "open with gdebi" => gdebi launch, et show the .deb file. But clic on "install" button, and gdebi close without any installation. Solution / workaround : change in gdebi.desktop the line exec=gdebi-gtk %f by : exec=sh -c "gdebi-gtk %f" And it's works perfectly. Please, change the gdebi.desktop in gdebi.deb on focal. ** Affects: gdebi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876504 Title: Gdebi close when trying to install a .deb with right-clic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1876504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875351] [NEW] Upgrade to 20.04 fails
Public bug reported: Checking package manager Reading package lists... Done Building dependency tree Reading state information... Done Invalid package information After updating your package information, the essential package 'ubuntu-minimal' could not be located. This may be because you have no official mirrors listed in your software sources, or because of excessive load on the mirror you are using. See /etc/apt/sources.list for the current list of configured software sources. In the case of an overloaded mirror, you may want to try the upgrade again later. Restoring original system state Aborting Reading package lists... Done Building dependency tree Reading state information... Done ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CrashDB: ubuntu Date: Mon Apr 27 14:12:23 2020 InstallationDate: Installed on 2018-12-13 (501 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to eoan on 2020-04-27 (0 days ago) VarLogDistupgradeAptlog: Log time: 2020-04-27 12:40:15.852774 Log time: 2020-04-27 12:40:30.189388 Log time: 2020-04-27 14:12:22.668365 Log time: 2020-04-27 14:12:25.440373 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875351 Title: Upgrade to 20.04 fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1875351/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866875] Re: option 'geoip-directory' was not enabled at compile time
I don't know what you mean by "MIR"; the following libmaxminddb0 was already installed before I upgraded bind9 to **1:9.16.0-1ubuntu3**: # apt-cache policy libmaxminddb0 libmaxminddb0: Installed: 1.3.2-1 Candidate: 1.3.2-1 Version table: *** 1.3.2-1 500 500 http://fr.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status I had no such issue with previous bind9 versions in /etc/bind/named.conf.options: options { ... geoip-directory "/usr/share/some/geoip/folder"; ... }; Upgrading to bind9 **1:9.16.0-1ubuntu4** does NOT solve this issue: bind9: Installed: 1:9.16.0-1ubuntu4 # systemctl restart bind9 # systemctl status bind9 ● named.service - BIND Domain Name Server Loaded: loaded (/lib/systemd/system/named.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Wed 2020-03-11 19:44:18 CET; 5s ago Docs: man:named(8) Process: 57887 ExecStart=/usr/sbin/named -f $OPTIONS (code=exited, status=1/FAILURE) Main PID: 57887 (code=exited, status=1/FAILURE) Mar 11 19:44:18 samsung6-ubuntu named[57887]: adjusted limit on open files from 524288 to 1048576 Mar 11 19:44:18 samsung6-ubuntu named[57887]: found 8 CPUs, using 8 worker threads Mar 11 19:44:18 samsung6-ubuntu named[57887]: using 8 UDP listeners per interface Mar 11 19:44:18 samsung6-ubuntu named[57887]: using up to 21000 sockets Mar 11 19:44:18 samsung6-ubuntu named[57887]: loading configuration from '/etc/bind/named.conf' Mar 11 19:44:18 samsung6-ubuntu named[57887]: /etc/bind/named.conf.options:48: option 'geoip-directory' was not enabled at compile time Mar 11 19:44:18 samsung6-ubuntu named[57887]: loading configuration: failure Mar 11 19:44:18 samsung6-ubuntu named[57887]: exiting (due to fatal error) Mar 11 19:44:18 samsung6-ubuntu systemd[1]: named.service: Main process exited, code=exited, status=1/FAILURE Mar 11 19:44:18 samsung6-ubuntu systemd[1]: named.service: Failed with result 'exit-code'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866875 Title: option 'geoip-directory' was not enabled at compile time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1866875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866875] [NEW] option 'geoip-directory' was not enabled at compile time
Public bug reported: Ubuntu 20.04 bind9 1:9.16.0-1ubuntu3 # systemctl status bind9 ● named.service - BIND Domain Name Server Loaded: loaded (/lib/systemd/system/named.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2020-03-10 18:22:42 CET; 2min 21s ago Docs: man:named(8) Main PID: 46665 (code=exited, status=1/FAILURE) Mar 10 18:22:42 samsung6-ubuntu named[46665]: adjusted limit on open files from 524288 to 1048576 Mar 10 18:22:42 samsung6-ubuntu named[46665]: found 8 CPUs, using 8 worker threads Mar 10 18:22:42 samsung6-ubuntu named[46665]: using 8 UDP listeners per interface Mar 10 18:22:42 samsung6-ubuntu named[46665]: using up to 21000 sockets Mar 10 18:22:42 samsung6-ubuntu named[46665]: loading configuration from '/etc/bind/named.conf' Mar 10 18:22:42 samsung6-ubuntu named[46665]: /etc/bind/named.conf.options:48: option 'geoip-directory' was not enabled at compile time Mar 10 18:22:42 samsung6-ubuntu named[46665]: loading configuration: failure Mar 10 18:22:42 samsung6-ubuntu named[46665]: exiting (due to fatal error) Mar 10 18:22:42 samsung6-ubuntu systemd[1]: named.service: Main process exited, code=exited, status=1/FAILURE Mar 10 18:22:42 samsung6-ubuntu systemd[1]: named.service: Failed with result 'exit-code'. ** Affects: bind9 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866875 Title: option 'geoip-directory' was not enabled at compile time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1866875/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs