[Bug 1934129] Re: disable neutron-fwaas for >= victoria
This bug was fixed in the package neutron - 2:18.1.0+git2021090913.64bfeae21c-0ubuntu1 --- neutron (2:18.1.0+git2021090913.64bfeae21c-0ubuntu1) impish; urgency=medium * New upstream snapshot for OpenStack Xena. * d/control: Align (Build-)Depends with upstream. * d/control: Drop neutron-fwaas dependency as it is no longer maintained (LP: #1934129). * d/p/revert-rely-on-worker-count-for-hashring-caching.patch: Dropped. Fixed upstream by https://review.opendev.org/c/openstack/neutron/+/800679. * d/p/revert-sqlalchemy-upgrade.patch: Rebased. * d/p/revert-l3-ha-retry-when-setting-ha-router-gw-status.patch: Dropped. Fixed in new upstream snapshot. -- Corey Bryant Thu, 09 Sep 2021 13:01:27 -0400 ** Changed in: neutron (Ubuntu Impish) Status: Triaged => 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/1934129 Title: disable neutron-fwaas for >= victoria To manage notifications about this bug go to: https://bugs.launchpad.net/charm-guide/+bug/1934129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 413278]
gdb/dwarf: disable per-BFD resource sharing for -readnow objfiles
New in v2:
- Disable sharing only for -readnow objfiles, not all objfiles.
As described in PR 27541, we hit an internal error when loading a binary
the standard way and then loading it with the -readnow option:
$ ./gdb -nx -q --data-directory=data-directory ~/a.out -ex "set confirm
off" -ex "file -readnow ~/a.out"
Reading symbols from /home/simark/a.out...
Reading symbols from ~/a.out...
/home/simark/src/binutils-gdb/gdb/dwarf2/read.c:8098: internal-error:
void create_all_comp_units(dwarf2_per_objfile*): Assertion
`per_objfile->per_bfd->all_comp_units.empty ()' failed.
This is a recurring problem that exposes a design issue in the DWARF
per-BFD sharing feature. Things work well when loading a binary with
the same method (with/without index, with/without readnow) twice in a
row. But they don't work so well when loading a binary with different
methods. See this previous fix, for example:
efb763a5ea35 ("gdb: check for partial symtab presence in
dwarf2_initialize_objfile")
That one handled the case where the first load is normal (uses partial
symbols) and the second load uses an index.
The problem is that when loading an objfile with a method A, we create a
dwarf2_per_bfd and some dwarf2_per_cu_data and initialize them with the
data belonging to that method. When loading another obfile sharing the
same BFD but with a different method B, it's not clear how to re-use the
dwarf2_per_bfd/dwarf2_per_cu_data previously created, because they
contain the data specific to method A. https://komiya-dental.com/
I think the most sensible fix would be to not share a dwarf2_per_bfd
between two objfiles loaded with different methods. That means that two
objfiles sharing the same BFD and loaded the same way would share a
dwarf2_per_bfd. Two objfiles sharing the same BFD but loaded with
different methods would use two different dwarf2_per_bfd structures.
http://www.iu-bloomington.com/
However, this isn't a trivial change. So to fix the known issue quickly
(including in the gdb 10 branch), this patch just disables all
dwarf2_per_bfd sharing for objfiles using READNOW.
Generalize the gdb.base/index-cache-load-twice.exp test to test all
the possible combinations of loading a file with partial symtabs, index
and readnow. Move it to gdb.dwarf2, since it really exercises features
of the DWARF
gdb/dwarf: disable per-BFD resource sharing for -readnow objfiles
https://www.webb-dev.co.uk/
New in v2:
- Disable sharing only for -readnow objfiles, not all objfiles.
As described in PR 27541, we hit an internal error when loading a binary
the standard way and then loading it with the -readnow option:
https://waytowhatsnext.com/
$ ./gdb -nx -q --data-directory=data-directory ~/a.out -ex "set confirm
off" -ex "file -readnow ~/a.out"
Reading symbols from /home/simark/a.out...
Reading symbols from ~/a.out...
/home/simark/src/binutils-gdb/gdb/dwarf2/read.c:8098: internal-error:
void create_all_comp_units(dwarf2_per_objfile*): Assertion
`per_objfile->per_bfd->all_comp_units.empty ()' failed.
http://www.acpirateradio.co.uk/
This is a recurring problem that exposes a design issue in the DWARF
per-BFD sharing feature. Things work well when loading a binary with
the same method (with/without index, with/without readnow) twice in a
row. But they don't work so well when loading a binary with different
methods. See this previous fix, for example: http://www.logoarts.co.uk/
efb763a5ea35 ("gdb: check for partial symtab presence in
dwarf2_initialize_objfile")
That one handled the case where the first load is normal (uses partial
symbols) and the second load uses an index. http://www.slipstone.co.uk/
The problem is that when loading an objfile with a method A, we create a
dwarf2_per_bfd and some dwarf2_per_cu_data and initialize them with the
data belonging to that method. When loading another obfile sharing the
same BFD but with a different method B, it's not clear how to re-use the
dwarf2_per_bfd/dwarf2_per_cu_data previously created, because they
contain the data specific to method A. http://embermanchester.uk/
I think the most sensible fix would be to not share a dwarf2_per_bfd
between two objfiles loaded with different methods. http://connstr.net/
That means that two
objfiles sharing the same BFD and loaded the same way would share a
dwarf2_per_bfd. Two objfiles http://joerg.li/ sharing the same BFD but
loaded with
different methods would use two different dwarf2_per_bfd structures.
http://www.jopspeech.com/
However, this isn't a trivial change. So to fix the known
[Bug 1863162]
(In reply to xujing from comment #35) > (In reply to cvs-com...@gcc.gnu.org from comment #31) > > The master branch has been updated by Szabolcs Nagy : > > > > https://sourceware.org/git/gitweb.cgi?p=glibc.git; > > h=1387ad6225cf027790e3f460e31aa5dd2c54 > > > > commit 1387ad6225cf027790e3f460e31aa5dd2c54 > > Author: Szabolcs Nagy > > Date: Wed Dec 30 19:19:37 2020 + > > > > elf: Fix data races in pthread_create and TLS access [BZ #19329] > > > > DTV setup at thread creation (_dl_allocate_tls_init) is changed > > to take the dlopen lock, GL(dl_load_lock). Avoiding data races > > here without locks would require design changes: the map that is > > accessed for static TLS initialization here may be concurrently > > freed by dlclose. That use after free may be solved by only > > locking around static TLS setup or by ensuring dlclose does not > > free modules with static TLS, however currently every link map > > with TLS has to be accessed at least to see if it needs static > > TLS. And even if that's solved, still a lot of atomics would be > > needed to synchronize DTV related globals without a lock. So fix > > both bug 19329 and bug 27111 with a lock that prevents DTV setup > > running concurrently with dlopen or dlclose. > > > > _dl_update_slotinfo at TLS access still does not use any locks > > so CONCURRENCY NOTES are added to explain the synchronization. > > The early exit from the slotinfo walk when max_modid is reached > > is not strictly necessary, but does not hurt either. > > > > An incorrect acquire load was removed from _dl_resize_dtv: it > > did not synchronize with any release store or fence and > > synchronization is now handled separately at thread creation > > and TLS access time. > > > > There are still a number of racy read accesses to globals that > > will be changed to relaxed MO atomics in a followup patch. This > > should not introduce regressions compared to existing behaviour > > and avoid cluttering the main part of the fix. > > > > Not all TLS access related data races got fixed here: there are > > additional races at lazy tlsdesc relocations see bug 27137. > > > > Reviewed-by: Adhemerval Zanella > > this patch use dl_load_lock in _dl_allocate_tls_init, is there a problem > when dlopen a dynamic library which will call pthread_create? I think it > will cause dl_load_lock and dl_load_lock dead lock. dlopen will hold on dl_load_lock, and pthread_create will call _dl_allocate_tls_init and then will hold on dl_load_lock. Finally, it will cause dead lock. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863162 Title: Inconsistency detected by ld.so: dl-tls.c: 493: _dl_allocate_tls_init: Assertion `listp->slotinfo[cnt].gen <= GL(dl_tls_generation)' failed! To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1863162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863162]
(In reply to cvs-com...@gcc.gnu.org from comment #31) > The master branch has been updated by Szabolcs Nagy : > > https://sourceware.org/git/gitweb.cgi?p=glibc.git; > h=1387ad6225cf027790e3f460e31aa5dd2c54 > > commit 1387ad6225cf027790e3f460e31aa5dd2c54 > Author: Szabolcs Nagy > Date: Wed Dec 30 19:19:37 2020 + > > elf: Fix data races in pthread_create and TLS access [BZ #19329] > > DTV setup at thread creation (_dl_allocate_tls_init) is changed > to take the dlopen lock, GL(dl_load_lock). Avoiding data races > here without locks would require design changes: the map that is > accessed for static TLS initialization here may be concurrently > freed by dlclose. That use after free may be solved by only > locking around static TLS setup or by ensuring dlclose does not > free modules with static TLS, however currently every link map > with TLS has to be accessed at least to see if it needs static > TLS. And even if that's solved, still a lot of atomics would be > needed to synchronize DTV related globals without a lock. So fix > both bug 19329 and bug 27111 with a lock that prevents DTV setup > running concurrently with dlopen or dlclose. > > _dl_update_slotinfo at TLS access still does not use any locks > so CONCURRENCY NOTES are added to explain the synchronization. > The early exit from the slotinfo walk when max_modid is reached > is not strictly necessary, but does not hurt either. > > An incorrect acquire load was removed from _dl_resize_dtv: it > did not synchronize with any release store or fence and > synchronization is now handled separately at thread creation > and TLS access time. > > There are still a number of racy read accesses to globals that > will be changed to relaxed MO atomics in a followup patch. This > should not introduce regressions compared to existing behaviour > and avoid cluttering the main part of the fix. > > Not all TLS access related data races got fixed here: there are > additional races at lazy tlsdesc relocations see bug 27137. > > Reviewed-by: Adhemerval Zanella this patch use dl_load_lock in _dl_allocate_tls_init, is there a problem when dlopen a dynamic library which will call pthread_create? I think it will cause dl_load_lock and dl_load_lock dead lock. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863162 Title: Inconsistency detected by ld.so: dl-tls.c: 493: _dl_allocate_tls_init: Assertion `listp->slotinfo[cnt].gen <= GL(dl_tls_generation)' failed! To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1863162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928679] Re: Support importing mokx keys into revocation list from the mok table
** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.10 (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928679 Title: Support importing mokx keys into revocation list from the mok table To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1928679/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932029] Re: Support builtin revoked certificates
** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.10 (Ubuntu Xenial) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => Fix Committed ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932029 Title: Support builtin revoked certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941829] Re: ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page()
** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: In Progress => 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/1941829 Title: ubunut_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1941829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892213] Re: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/hirsute/impish
** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: In Progress => 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/1892213 Title: psock_snd.sh in net from ubuntu_kernel_selftests ADT failure with focal/groovy/hirsute/impish To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1892213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941696] Re: Fix Intel AC9560 BT function cannot turn on if BT turn off before S3 entry
** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: In Progress => 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/1941696 Title: Fix Intel AC9560 BT function cannot turn on if BT turn off before S3 entry To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1941696/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930754] Re: e1000e extremly slow
** Tags added: originate-from-1942834 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930754 Title: e1000e extremly slow To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1930754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934998] Re: MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many symbolic link levels: '/etc/mysql/my.cnf'
[Expired for mysql-8.0 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mysql-8.0 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934998 Title: MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Too many symbolic link levels: '/etc/mysql/my.cnf' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1934998/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942476] Re: autopkgtest: Invalid DATETIME test fails with mysql >= 8.0.24
** Changed in: ruby-mysql2 Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942476 Title: autopkgtest: Invalid DATETIME test fails with mysql >= 8.0.24 To manage notifications about this bug go to: https://bugs.launchpad.net/ruby-mysql2/+bug/1942476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943296] [NEW] Ubuntu 18 LTS won't install
Public bug reported: Ubuntu 18 LTS won't install because of a fatal error during installation process. I'm using a 500gb sata SSD that is freshly wiped, I partitioned it using the installation manual partitioner. I got Win 10 on another Drive (M.2) I chose to install alongside it and it just crashes. I chose the option of downloading specific drivers (I got a AMD 3100 CPU and a AMD 5700xt GPU). I tried many times with different configs and it just wont install. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.15 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CasperVersion: 1.394.3 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 10 23:46:21 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) ProcEnviron: LANGUAGE=en_CA.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.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 bionic ubiquity-18.04.14.15 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943296 Title: Ubuntu 18 LTS won't install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1943296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875062] Re: [20.04] Keyboard layout not enabled immediately during installation when typing username/password
Same problem during installation using Hirsute Hippo 21.04 Desktop ISO image on virtualbox 6.1. I choose "Français" at the beginning and setup changes correctly to French language. Then I pick "French" (topmost choice in keyboard mapping list) at the keyboard layout stage and I can confirm in the text bar, underneath the mapping list on the same screen, that the keyboard mapping is correct (AZERTY). Then during partitioning, I choose automated partitioning with LVM and Encryption First issue : Keyboard mapping is set back to US layout (confirmed by trying change the location of the security key and typing in the contextual folder path ). NOTE: All steps are displayed in French language as expected. Second issue : Again, during creation of the first user, the keyboard mapping is also set to US and not French. Upon restart, the disk decryption fails since the keyboard mapping was wrong during setup. => It seems the problem happens just after the change of keyboard mapping, it is not taken into account. Workaround : I typed the desired password in US mapping. IMPORTANT: Using the workaround, after restart at the end of installation, the mapping is correct from then on (disk decryption and login, etc ...). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875062 Title: [20.04] Keyboard layout not enabled immediately during installation when typing username/password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1875062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589853] Re: Keyframe not correctly marked
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: recordmydesktop (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589853 Title: Keyframe not correctly marked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/recordmydesktop/+bug/1589853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943294] Re: Cannot enable. Maybe the USB cable is bad?
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943294 Title: Cannot enable. Maybe the USB cable is bad? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1943294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786013] Autopkgtest regression report (linux-meta-aws/5.4.0.1057.60)
All autopkgtests for the newly accepted linux-meta-aws (5.4.0.1057.60) for focal have finished running. The following regressions have been reported in tests triggered by the package: backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (amd64, arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-aws [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions 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/1786013 Title: Packaging resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898912] Re: ath3k: probe of 2-1.3:1.0 failed with error -110
** Tags removed: impish ** 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/1898912 Title: ath3k: probe of 2-1.3:1.0 failed with error -110 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925246] Re: binderfs support is not enabled
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925246 Title: binderfs support is not enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1925246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937078] Re: Drivers: hv: vmbus: Fix duplicate CPU assignments within a device
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed- hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937078 Title: Drivers: hv: vmbus: Fix duplicate CPU assignments within a device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1937078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898912] Re: ath3k: probe of 2-1.3:1.0 failed with error -110
Broken again at 21.10 ** Changed in: linux (Ubuntu) Status: Fix Released => Confirmed ** Tags added: impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898912 Title: ath3k: probe of 2-1.3:1.0 failed with error -110 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898912/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943294] [NEW] Cannot enable. Maybe the USB cable is bad?
Public bug reported: my usb drive not able to connect in dmesg showing message like "[ 3129.107060] usb usb2-port2: Cannot enable. Maybe the USB cable is bad? [ 3130.075767] usb usb2-port2: Cannot enable. Maybe the USB cable is bad? [ 3130.075872] usb usb2-port2: unable to enumerate USB device [ 3673.272729] usb usb2-port2: Cannot enable. Maybe the USB cable is bad? [ 3674.239824] usb usb2-port2: Cannot enable. Maybe the USB cable is bad? [ 3674.239882] usb usb2-port2: attempt power cycle [ 3675.530699] usb usb2-port2: Cannot enable. Maybe the USB cable is bad? [ 3676.501862] usb usb2-port2: Cannot enable. Maybe the USB cable is bad? [ 3676.501960] usb usb2-port2: unable to enumerate USB device" but when I connecting any optical mouse and keyboard, these connected. Why usb problem creating for external media? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: usb-creator-gtk 0.3.7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Sep 11 07:15:19 2021 InstallationDate: Installed on 2021-07-10 (62 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: usb-creator UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: usb-creator (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943294 Title: Cannot enable. Maybe the USB cable is bad? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/1943294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786013] Autopkgtest regression report (linux-meta-gcp/5.4.0.1053.63)
All autopkgtests for the newly accepted linux-meta-gcp (5.4.0.1053.63) for focal have finished running. The following regressions have been reported in tests triggered by the package: backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-gcp [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions 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/1786013 Title: Packaging resync To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918179] Re: FFe: Sync 0ad 0.0.24b-1 (universe) from Debian experimental (main)
@Olivier > The easiest way to get alpha 25 on Ubuntu is to install the snap: It would be a better UX to have also the package up to date. Or maybe to not have an apt package and only the snap as a last resort if the maintenance burden is too high for multiplayer games (Minetest has also this issue). Depackaging to rely on Snap should also be a big decision to take formally by the project. I really hope it's possible to keep the package and have it up to date since it will in practice lead to everyone to have the right version to play with the rest of the community. Without having to know to avoid the main installation method. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918179 Title: FFe: Sync 0ad 0.0.24b-1 (universe) from Debian experimental (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/0ad/+bug/1918179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1918179] Re: FFe: Sync 0ad 0.0.24b-1 (universe) from Debian experimental (main)
Thanks to the people which made the package available to Impish (21.10). Which is the right place to raise the question of having alpha 25 backported? Since the alphas aren't network compatible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1918179 Title: FFe: Sync 0ad 0.0.24b-1 (universe) from Debian experimental (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/0ad/+bug/1918179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892369] Re: Impossible to skip integrity test for ubuntu-server 20.04.1 iso
Why is this still a problem with the 20.04.03 iso image? Seriously, are you under the impression that we all have nothing better to do with our very limited time on this earth, why the hell is an integrity check even the default in the first place? You can verify the checksum of the image before you mount the ISO image using your Baseboard Management Controller's Virtual Media. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892369 Title: Impossible to skip integrity test for ubuntu-server 20.04.1 iso To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1892369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943153] Re: Compilation fails with ffmpeg 4.4
** Changed in: mplayer (Debian) Status: Fix Committed => 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/1943153 Title: Compilation fails with ffmpeg 4.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mplayer/+bug/1943153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943287] Re: Can't start qemu on linux-5.14.2-051402-lowlatency
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1943287/+editstatus and add the package name in the text box next to the word Package. [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943287 Title: Can't start qemu on linux-5.14.2-051402-lowlatency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1943287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938999] Re: External displays not working on Thinkpad T490 with ThinkPad Thunderbolt 3 Dock
Thanks for the fix. I'm not sure to whom the previous message is addressed but I will not be able to test it because I'm will not be at the office until end of September. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938999 Title: External displays not working on Thinkpad T490 with ThinkPad Thunderbolt 3 Dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939413] Re: /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0
The rebuild of protobuf no longer has lto information according to objdump, but the reported version certainly does. The "bad" version was built during hirsute devel, so I took a current hirsute system and systematically downgraded build-deps to the versions in the log of the "bad" build. Turns out, the relevant difference is a couple libs from elfutils: libdw1 and libelf1. If I build protobuf w/ the 0.183-6 versions, I can reproduce the problem. 0.183-8 does not (0.183-7 FTBFS, so could not be tested). Strangely the delta between elfutils 0.183-6 and 0.183-8 appears innocuous - it all looks like packaging cleanup, no changes to upstream source. ** Also affects: elfutils (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/1939413 Title: /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/1939413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938043] Re: ubuntu-security-status
Hello Nikos, or anyone else affected, Accepted update-manager into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/update- manager/1:20.04.10.9 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: update-manager (Ubuntu Focal) Status: Triaged => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938043 Title: ubuntu-security-status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1938043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943288] Re: Soname change and transition started without a ffe
I've reviewed the history here; libffi8 has been in impish-proposed since June 30. So this is not something that requires a freeze exception, just follow-through on the migration. ** Changed in: libffi (Ubuntu) Status: New => 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/1943288 Title: Soname change and transition started without a ffe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1943288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935063] Re: gnome-initial-setup: cannot build on RISC-V
golang-1.16 (1.16.7-1ubuntu2) allows building dynamic link libraries (*.so) needed by ubuntu-report. https://github.com/ubuntu/ubuntu-report/pull/38 addresses remaining build problems on RISC-V. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935063 Title: gnome-initial-setup: cannot build on RISC-V To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1935063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943288] [NEW] Soname change and transition started without a ffe
Public bug reported: It seems the recent upload includes a soname change and is starting a transition, such changes at the point of the cycle would require a ffe ** Affects: libffi (Ubuntu) Importance: High Status: New ** Tags: block-proposed impish rls-ii-incoming ** Changed in: libffi (Ubuntu) Importance: Undecided => High ** Tags added: impish rls-ii-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943288 Title: Soname change and transition started without a ffe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1943288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937055] Re: OpenSBI: system reset support missing for HiFive Unmatched
There is no GPIO for system reset on the HiFive unmatched. Patches for an SBI based sysreset driver have been sent to upstream U-Boot. https://lists.denx.de/pipermail/u-boot/2021-September/460291.html The is an ongoing discussion about how UEFI runtime system reset drivers should be implemented. Some maintainers wish a driver model based solution and don't wont to follow the style of previous reset drivers like for PSCI. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937055 Title: OpenSBI: system reset support missing for HiFive Unmatched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opensbi/+bug/1937055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1])
Hi, Patricia. Can you clarify if you always need to run the hotplug test before reuseport_bpf_cpu in order to reproduce? I wonder what is the state that the hotplug test leaves the system in? How is it being run? The makefile runs it with the -a option, which in the systems I have available would fail to offline the last CPU (which is expected, different behavior from x86, where cpu0 cannot be offlined). Running it without any options would only offline the last CPU and online it again. I tried looking for differences between our kernels and 5.11.22 and the only cpuset changes I noticed were already present in the kernel you have just tested, and they were on paths unrelated to hotplug or BPF, so I am still baffled as to the real differences here. And given the different systems fail differently, it looks like this will require a dump or xmon so we can debug it. Thanks for all the help. I may ask for system access next week in order to help there. Cascardo. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936664] Re: buildmode=c-shared not supported on linux/risc-v
** Changed in: golang-1.16 (Ubuntu) Assignee: (unassigned) => Heinrich Schuchardt (xypron) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936664 Title: buildmode=c-shared not supported on linux/risc-v To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-1.16/+bug/1936664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943153] Re: Compilation fails with ffmpeg 4.4
New version released in Debian with fix. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994002 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943153 Title: Compilation fails with ffmpeg 4.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mplayer/+bug/1943153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942784] Re: makedumpfile not properly working on focal with 5.11 kernel
** Changed in: makedumpfile (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942784 Title: makedumpfile not properly working on focal with 5.11 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1942784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943160] Re: [SRU] It will take about 90+ seconds to open the 'Nvidia settings' app when 'Power Saving mode' running.
** Changed in: nvidia-settings (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943160 Title: [SRU] It will take about 90+ seconds to open the 'Nvidia settings' app when 'Power Saving mode' running. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943160/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943129] Re: Add support for riscv64
** Changed in: nx-libs (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943129 Title: Add support for riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nx-libs/+bug/1943129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943287] [NEW] Can't start qemu on linux-5.14.2-051402-lowlatency
Public bug reported: After installing kernel package linux-image- unsigned-5.14.2-051402-lowlatency from https://kernel.ubuntu.com/~kernel-ppa/mainline/ starting libvirtd, and thus qemu, results in 2 stack traces. Then libvirtd stops. Rolling back to 5.11.0-34-lowlatency fixes the problem. sep 10 17:07:37 kernel: invalid opcode: [#3] PREEMPT SMP NOPTI sep 10 17:07:37 kernel: CPU: 8 PID: 21670 Comm: daemon-init Tainted: G D W 5.14.2-051402-lowlatency #202109080331 sep 10 17:07:37 kernel: Hardware name: Supermicro C9X299-PG300F/C9X299-PG300F, BIOS 2.1 06/16/2020 sep 10 17:07:37 kernel: RIP: 0010:vmx_create_vcpu+0x6a7/0x6f0 [kvm_intel] sep 10 17:07:37 kernel: Code: 89 e7 48 8d 75 cc ba 04 00 00 00 e8 c3 58 fb d1 85 c0 74 d7 4c 89 ff 4c 89 f3 41 bd f2 ff ff ff e8 fe d9 5f d2 e9 0b fd ff ff <0f> 0b 4c 89 ff 45 89 e5 e8 ec d9 5f d2 45 85 e4 0f 84 34 fb ff ff sep 10 17:07:37 kernel: RSP: 0018:b976caa0fc78 EFLAGS: 00010202 sep 10 17:07:37 kernel: RAX: 9fce6af99db0 RBX: 9fce6af98000 RCX: 0007 sep 10 17:07:37 kernel: RDX: 0006 RSI: 0001 RDI: 0122 sep 10 17:07:37 kernel: RBP: b976caa0fcb8 R08: R09: 9fce6afa1080 sep 10 17:07:37 kernel: R10: 0293 R11: 9fdd3fc33588 R12: 0007 sep 10 17:07:37 kernel: R13: fff4 R14: 9fce6af98000 R15: sep 10 17:07:37 kernel: FS: 7f75e8b79640() GS:9fdd3fc0() knlGS: sep 10 17:07:37 kernel: CS: 0010 DS: ES: CR0: 80050033 sep 10 17:07:37 kernel: CR2: 7f75f8dc2800 CR3: 000314c88005 CR4: 003726e0 sep 10 17:07:37 kernel: DR0: DR1: DR2: sep 10 17:07:37 kernel: DR3: DR6: fffe0ff0 DR7: 0400 sep 10 17:07:37 kernel: Call Trace: sep 10 17:07:37 kernel: kvm_arch_vcpu_create+0x288/0x390 [kvm] sep 10 17:07:37 kernel: kvm_vm_ioctl_create_vcpu+0x188/0x420 [kvm] sep 10 17:07:37 kernel: ? obj_cgroup_uncharge_pages+0x69/0xe0 sep 10 17:07:37 kernel: kvm_vm_ioctl+0x546/0x7b0 [kvm] sep 10 17:07:37 kernel: ? kvm_uevent_notify_change.part.0+0x17b/0x210 [kvm] sep 10 17:07:37 kernel: ? kfree+0x22a/0x3e0 sep 10 17:07:37 kernel: ? __fget_files+0x74/0xa0 sep 10 17:07:37 kernel: __x64_sys_ioctl+0x8e/0xc0 sep 10 17:07:37 kernel: do_syscall_64+0x59/0xc0 sep 10 17:07:37 kernel: ? do_syscall_64+0x69/0xc0 sep 10 17:07:37 kernel: ? exit_to_user_mode_prepare+0x37/0xb0 sep 10 17:07:37 kernel: ? syscall_exit_to_user_mode+0x27/0x50 sep 10 17:07:37 kernel: ? do_syscall_64+0x69/0xc0 sep 10 17:07:37 kernel: ? exit_to_user_mode_prepare+0x37/0xb0 sep 10 17:07:37 kernel: ? syscall_exit_to_user_mode+0x27/0x50 sep 10 17:07:37 kernel: ? __x64_sys_close+0x11/0x40 sep 10 17:07:37 kernel: ? do_syscall_64+0x69/0xc0 sep 10 17:07:37 kernel: ? exit_to_user_mode_prepare+0x37/0xb0 sep 10 17:07:37 kernel: ? syscall_exit_to_user_mode+0x27/0x50 sep 10 17:07:37 kernel: ? __x64_sys_read+0x19/0x20 sep 10 17:07:37 kernel: ? do_syscall_64+0x69/0xc0 sep 10 17:07:37 kernel: ? asm_sysvec_apic_timer_interrupt+0xa/0x20 sep 10 17:07:37 kernel: entry_SYSCALL_64_after_hwframe+0x44/0xae sep 10 17:07:37 kernel: RIP: 0033:0x7f75f895aecb sep 10 17:07:37 kernel: Code: ff ff ff 85 c0 79 8b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 6d 1f 0d 00 f7 d8 64 89 01 48 sep 10 17:07:37 kernel: RSP: 002b:7f75e8b78498 EFLAGS: 0246 ORIG_RAX: 0010 sep 10 17:07:37 kernel: RAX: ffda RBX: 7f75b02d1260 RCX: 7f75f895aecb sep 10 17:07:37 kernel: RDX: RSI: ae41 RDI: 0022 sep 10 17:07:37 kernel: RBP: 7f75e8b78510 R08: R09: sep 10 17:07:37 kernel: R10: R11: 0246 R12: sep 10 17:07:37 kernel: R13: 7f75b02ddd18 R14: R15: 7f75b02ddd10 sep 10 17:07:37 kernel: Modules linked in: cpuid snd_seq_dummy snd_hrtimer ip6t_REJECT nf_reject_ipv6 xt_CHECKSUM xt_tcpudp ipt_REJECT nf_reject_ipv4 xt_set ip_set_hash_ip ip_set bridge stp llc xt_MASQUERADE xt_conntrack nft_compat nft_counter nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink zstd lz4 lz4_compress zram netconsole macvlan binfmt_misc dm_crypt nls_iso8859_1 intel_rapl_msr intel_rapl_common isst_if_common nfit x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio rapl intel_cstate snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_usb_audio snd_hda_codec snd_seq_midi snd_usbmidi_lib snd_hda_core snd_seq_midi_event mc snd_hwdep snd_rawmidi efi_pstore snd_pcm snd_seq xpad snd_seq_device ff_memless snd_timer snd soundcore input_leds joydev mei_me mei ioatdma mac_hid acpi_tad sch_fq_codel nct6775
[Bug 1685068] Re: ubuntu-archive: distributing files without license to distribute
The only one of these in a currently supported release of Ubuntu is webkitgtk 2.4.0, which is in trusty; trusty is in ESM support only and will stop being supported at all next April. We have already been distributing this binary for 7 years. In the absence of specific notice from the copyright holder, rather than doing the necessary archive surgery to remove this tarball, I'm inclined to let it age out next year. ** Changed in: ubuntu Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685068 Title: ubuntu-archive: distributing files without license to distribute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1685068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1935034] Re: Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04
I need an impact statement before I can submit this to the mailing list for approval. SRU Justification: [Impact] [FIXES] [TESTING] [REGRESSION RISK] [Other Info] (optional) Here is an additional reference. https://wiki.ubuntu.com/Kernel/Dev/StablePatchFormat -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1935034 Title: Update mpt3sas Driver to 38.100.00.00 for Ubuntu 21.10 and 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943286] Re: syncpackage crashed with urllib.error.URLError in do_open():
The issue resolved itself with the apache ssl update shortly after I filed this bug, but it still shouldn't fail as hard as it did. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943286 Title: syncpackage crashed with urllib.error.URLError in do_open(): To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1943286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1])
Krzysztof, you were on a PowerVM LPAR (P8LPAR05), just let me know if there's anything that need to be tested -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937070] Re: please RM stylish-haskell binaries on riscv64 and s390x
Removing packages from impish: stylish-haskell 0.11.0.0-1build1 in impish riscv64 stylish-haskell 0.11.0.0-1build1 in impish s390x Comment: ANAIS 2 packages successfully removed. ** Changed in: stylish-haskell (Ubuntu) Status: New => 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/1937070 Title: please RM stylish-haskell binaries on riscv64 and s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/stylish-haskell/+bug/1937070/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942607] Re: unifont-bin not installable on i386
Removing packages from impish-proposed: unifont-bin 1:13.0.06-1 in impish i386 Comment: Not for i386 1 package successfully removed. ** Changed in: unifont (Ubuntu) Status: New => 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/1942607 Title: unifont-bin not installable on i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unifont/+bug/1942607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1])
** Attachment added: "lscpu_entei" https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+attachment/5524453/+files/lscpu_entei -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1])
Also re-ran on `entei` it is also a POWER8 (8335-GTA) with Hirsute latest kernel (5.11.0-34-generic) hit the same error - second run of `reuseport_bpf_cpu`: ``` [ 232.349547] Oops: Exception in kernel mode, sig: 4 [#1] [ 232.349647] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV ... [ 232.355607] LR [08d19f3b15a8] 0x8d19f3b15a8 [ 232.355855] --- interrupt: c00 [ 232.355869] Instruction dump: [ 232.356114] [ 232.356374] [ 232.356905] ---[ end trace c99c88cea832039b ]--- [ 232.508560] [ 233.508662] Kernel panic - not syncing: Aiee, killing interrupt handler! [ 233.950570] Rebooting in 10 seconds.. ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927076] Re: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1])
Ok I've re-ran the test with latest kernel versions on the same systems: `thiel` (8001-22C) with focal-hwe (5.11.0-34-generic): ``` [ 3255.763649] Oops: Exception in kernel mode, sig: 5 [#1] [ 3255.763723] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV ``` And `gulpin` (8335-GTA) with hirsute (5.11.0-34-generic) 2nd run of `reuseport_bpf_cpu`: ``` [ 760.451968] BUG: Unable to handle kernel instruction fetch (NULL pointer?) [ 760.452035] Faulting instruction address: 0x [ 760.452196] Oops: Kernel access of bad area, sig: 11 [#1] [ 760.452212] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA PowerNV ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927076 Title: IPv6 TCP in reuseport_bpf_cpu from ubuntu_kernel_selftests/net crash P8 node entei on 5.8 kernel (Oops: Exception in kernel mode, sig: 4 [#1]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1927076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942894] Re: [SRU] libreoffice 7.1.6 for hirsute
Hello Rico, or anyone else affected, Accepted libreoffice into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libreoffice/1:7.1.6-0ubuntu0.21.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libreoffice (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942894 Title: [SRU] libreoffice 7.1.6 for hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1942894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943125] Re: devscripts breaks apt
from my (devscripts) side, no idea. also I have no clue how a command that has || in there can even "return an error code". I'm strongly convinced there is nothing special in devscripts that could cause this, so I'm not considering it a bug in there. ** Changed in: devscripts (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943125 Title: devscripts breaks apt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1943125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943260] Re: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
*** This bug is a duplicate of bug 1938978 *** https://bugs.launchpad.net/bugs/1938978 ** This bug has been marked a duplicate of bug 1938978 nvidia-340 kernel module failed to build (ERROR: Kernel configuration is invalid) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943260 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1943260/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943285] [NEW] login screen lagging.
Public bug reported: After boot or logout, login screen slow to appear, and I cannot type in my password for 4 to 5 seconds after login screen has appeared. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm 1.30.0-0ubuntu4~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Fri Sep 10 21:37:00 2021 InstallationDate: Installed on 2020-05-05 (493 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) LightdmConfig: [Seat:*] autologin-guest=false greeter-show-manual-login=false greeter-session=slick-greeter SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (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/1943285 Title: login screen lagging. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1943285/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943286] Re: syncpackage crashed with urllib.error.URLError in do_open():
** Tags removed: need-duplicate-check ** Changed in: ubuntu-dev-tools (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943286 Title: syncpackage crashed with urllib.error.URLError in do_open(): To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1943286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943286] [NEW] syncpackage crashed with urllib.error.URLError in do_open():
Public bug reported: Happened while trying to sync a package. Looks like it definitely should not fail like this. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: ubuntu-dev-tools 0.184 ProcVersionSignature: Ubuntu 5.13.0-14.14-lowlatency 5.13.1 Uname: Linux 5.13.0-14-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Sep 10 13:56:12 2021 ExecutablePath: /usr/bin/syncpackage InstallationDate: Installed on 2021-03-20 (173 days ago) InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 (20210320) InterpreterPath: /usr/bin/python3.9 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/syncpackage qxgedit Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1 PythonArgs: ['/usr/bin/syncpackage', 'qxgedit'] PythonDetails: N/A SourcePackage: ubuntu-dev-tools Title: syncpackage crashed with urllib.error.URLError in do_open(): UpgradeStatus: Upgraded to impish on 2021-06-13 (89 days ago) UserGroups: adm audio cdrom dip libvirt lpadmin plugdev sambashare sudo ** Affects: ubuntu-dev-tools (Ubuntu) Importance: Medium Status: New ** Tags: amd64 apport-crash impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943286 Title: syncpackage crashed with urllib.error.URLError in do_open(): To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools/+bug/1943286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936664] Re: buildmode=c-shared not supported on linux/risc-v
This bug was fixed in the package golang-1.16 - 1.16.7-1ubuntu2 --- golang-1.16 (1.16.7-1ubuntu2) impish; urgency=medium * Add support for c-archive and c-shared on RISC-V (LP: #1936664) - Apply patches from https://github.com/4a6f656c/go.git, branch riscv64-c-shared-go1.16: - d/patches/0001-runtime-cgo-save-and-restore-X3-aka-GP-for-crosscall.patch - d/patches/0002-runtime-save-and-restore-X3-aka-GP-for-asmcgocalls-o.patch - d/patches/0003-all-add-support-for-c-archive-and-c-shared-on-linux-.patch - d/patches/0004-runtime-change-riscv64-assembly-to-work-with-Go-1.16.patch -- Heinrich Schuchardt Tue, 07 Sep 2021 15:18:09 +0200 ** Changed in: golang-1.16 (Ubuntu) Status: Fix Committed => 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/1936664 Title: buildmode=c-shared not supported on linux/risc-v To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-1.16/+bug/1936664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1941963] Re: package shim-signed 1.40.7+15.4-0ubuntu9 failed to install/upgrade: kernel segfault. Hard lock
The only available logs are already attached. I have resolved my specific issue by removing the offending package, but the bug that triggered the segfault still remains when reinstalled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1941963 Title: package shim-signed 1.40.7+15.4-0ubuntu9 failed to install/upgrade: kernel segfault. Hard lock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942974] Re: troff crashed with SIGSEGV
This bug was fixed in the package groff - 1.22.4-7 --- groff (1.22.4-7) unstable; urgency=medium * Cherry-pick from upstream: - Fix SEGV arising from recursing destructor (LP: #1942974). -- Colin Watson Thu, 09 Sep 2021 18:20:47 +0100 ** Changed in: groff (Ubuntu) Status: Fix Committed => 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/1942974 Title: troff crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/groff/+bug/1942974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1939071] Re: Dual screen not working
Hi Chris, I have just loaded kernel "Linux 5.11.0-34-generic #36~20.04.1-Ubuntu SMP Fri Aug 27 08:06:32 UTC 2021" through the update manager : Dual screen is now working fine. Status of this bug 1939071 can be changed to "fixed". Thanks for your help Thanks to the team Denis -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1939071 Title: Dual screen not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943049] Re: Docker ubuntu:impish: Problem executing scripts DPkg::Post-Invoke 'rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true'
Just a quick comment saying that I agree with Lucas' analysis here. It also seems to me that the glibc approach might be the least impactful way forward here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943049 Title: Docker ubuntu:impish: Problem executing scripts DPkg::Post-Invoke 'rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true' To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1943049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803663] Re: installed android-androresolvd package post-installation script subprocess returned error exit status 1
** Changed in: android-androresolvd (Ubuntu) Status: Confirmed => Fix Released ** Changed in: android-androresolvd (Ubuntu) Assignee: (unassigned) => Роман Мизиченко (roru78) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803663 Title: installed android-androresolvd package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android-androresolvd/+bug/1803663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868502] Re: Synchronization with earlier Ubuntu versions or a recent Debian version fails
Sorry, but this advice is terribly wrong. rm -r ~/.unison This will not only delete *all* and not just the synchronization states, that cause trouble, it will furthermore delete all config files and includes. So don't do that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868502 Title: Synchronization with earlier Ubuntu versions or a recent Debian version fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unison/+bug/1868502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943049] Re: Docker ubuntu:impish: Problem executing scripts DPkg::Post-Invoke 'rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true'
After reading the comments from this bug and the upstream discussions, I tried to find an approach which would minimize the size of the patch we would need to carry. I tested the following scenarios: 1) There is a docker upstream PR where tianon is trying to backport the fix to the 20.10 branch (the one we currently have in the archive), during the discussion, one of the upstream maintainers mentioned we might need just a newer version of runc to fix the issue: https://github.com/moby/moby/pull/42836#issuecomment-916422920 After inspecting the runc git repo I found the following commit which seems to address the issue: https://github.com/opencontainers/runc/commit/960182fdf03d99eb848c111ae791 I did backport this patch to the current runc package we have in Impish and tried to run the test case @athos-ribeiro provided in comment #2, using the docker.io package from the archive. But it did not work, the failure was still reproducible. 2) Since in the comment of the docker upstream maintainer he said we could need runc version 1.0.2 (in Impish we have 1.0.1), I imported this new version to our runc package and ran the same test case using docker.io from the archive. The issue was still there. 3) I kept the runc/1.0.2 installed in my VM and added tianon's patch backporting the fix to the docker.io package: https://github.com/moby/moby/pull/42836/files With the patched docker.io and runc/1.0.2 I was still able to reproduce the issue. 4) I removed all the custom packages from my VM and built the source package present in the PPA @juliank linked in comment #9 targeting Impish, and finally got the issue fixed (as others already mentioned). However, I am not happy in adding a patch with 1800+ lines containing a bunch of refactoring, the fix itself is less than 80 lines. I'd prefer to wait until the PR backporting the fix is merged: https://github.com/moby/moby/pull/42836 For libpod, Sergio helped me to investigate this issue and he noticed that in Fedora (with glibc 2.34) it is working fine. There we can find a newer version of it compared to what we have in Ubuntu. I did some investigation in its upstream git repo and I did not find any specific patch addressing this issue to backport. The other option would be to update libpod to the Fedora's version but then it'd likely require the update of some dependencies. I do not believe we have time to do that and we are also in the Feature Freeze. Moreover, Reinhard, who is the libpod maintainer, would not be happy if we release Impish with a broken package. With all that said, I believe the easier and the least worse solution would be to disable clone3 syscall from glibc. WDYT? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943049 Title: Docker ubuntu:impish: Problem executing scripts DPkg::Post-Invoke 'rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var/cache/apt/*.bin || true' To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1943049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942684] Re: Kernel 5.14.0/1/5.13.14 fails to boot
It started to happen since rc7 I'm supposing that it is happening because of this: 10/09/21 16:18 CRIS-DELL kernel [3.880089] RIP: 0010:nv_drm_format_array_alloc+0xb3/0xb5 [nvidia_drm] 10/09/21 16:18 CRIS-DELL kernel [3.880094] Code: 16 5b 4c 89 c0 41 5c 5d c3 f3 48 0f bc c0 89 c1 83 f8 22 76 b2 eb e2 4c 89 c7 e8 c8 e6 ff ff 45 31 c0 5b 41 5c 4c 89 c0 5d c3 <0f> 0b 0f 1f 44 00 00 55 48 89 e5 41 56 41 55 41 54 49 89 fc 53 48 10/09/21 16:18 CRIS-DELL kernel [3.880095] RSP: 0018:ae2a00f83a58 EFLAGS: 00010212 10/09/21 16:18 CRIS-DELL kernel [3.880097] RAX: 0020 RBX: 0001efff RCX: 0020 10/09/21 16:18 CRIS-DELL kernel [3.880098] RDX: 32313050 RSI: 0001 RDI: 0012 10/09/21 16:18 CRIS-DELL kernel [3.880099] RBP: ae2a00f83a68 R08: 8fbf0770c580 R09: 8fbf0770c580 10/09/21 16:18 CRIS-DELL kernel [3.880100] R10: 8fbf06e90028 R11: 8fbf1888e808 R12: ae2a00f83a9c 10/09/21 16:18 CRIS-DELL kernel [3.880101] R13: 8fbf0708a000 R14: 8fbf077a6600 R15: 10/09/21 16:18 CRIS-DELL kernel [3.880102] FS: 7f0c3ba20d00() GS:8fc28bc4() knlGS: 10/09/21 16:18 CRIS-DELL kernel [3.880104] CS: 0010 DS: ES: CR0: 80050033 10/09/21 16:18 CRIS-DELL kernel [3.880105] CR2: 563d833a3000 CR3: 000100cb6001 CR4: 003706e0 10/09/21 16:18 CRIS-DELL kernel [3.880106] DR0: DR1: DR2: 10/09/21 16:18 CRIS-DELL kernel [3.880106] DR3: DR6: fffe0ff0 DR7: 0400 10/09/21 16:18 CRIS-DELL kernel [3.880107] Call Trace: 10/09/21 16:18 CRIS-DELL kernel [3.880109] nv_drm_plane_create+0x7d/0x2f0 [nvidia_drm] 10/09/21 16:18 CRIS-DELL kernel [3.880114] nv_drm_enumerate_crtcs_and_planes+0x13f/0x2a0 [nvidia_drm] 10/09/21 16:18 CRIS-DELL kernel [3.880117] nv_drm_load+0x253/0x3b4 [nvidia_drm] 10/09/21 16:18 CRIS-DELL kernel [3.880121] ? __cond_resched+0x1a/0x50 10/09/21 16:18 CRIS-DELL kernel [3.880123] ? nv_drm_master_drop+0x60/0x60 [nvidia_drm] 10/09/21 16:18 CRIS-DELL kernel [3.880127] drm_dev_register+0xd6/0x1c0 [drm] 10/09/21 16:18 CRIS-DELL kernel [3.880142] nv_drm_probe_devices+0x10b/0x1f0 [nvidia_drm] 10/09/21 16:18 CRIS-DELL kernel [3.880145] ? 0xc0b86000 10/09/21 16:18 CRIS-DELL kernel [3.880146] nv_drm_init+0x1e/0x50 [nvidia_drm] 10/09/21 16:18 CRIS-DELL kernel [3.880149] nv_linux_drm_init+0xe/0x1000 [nvidia_drm] 10/09/21 16:18 CRIS-DELL kernel [3.880152] do_one_initcall+0x46/0x1d0 10/09/21 16:18 CRIS-DELL kernel [3.880154] ? kmem_cache_alloc_trace+0x159/0x2c0 10/09/21 16:18 CRIS-DELL kernel [3.880157] do_init_module+0x62/0x290 10/09/21 16:18 CRIS-DELL kernel [3.880159] load_module+0xaa3/0xb30 10/09/21 16:18 CRIS-DELL kernel [3.880162] __do_sys_finit_module+0xbf/0x120 10/09/21 16:18 CRIS-DELL kernel [3.880164] __x64_sys_finit_module+0x18/0x20 10/09/21 16:18 CRIS-DELL kernel [3.880166] do_syscall_64+0x59/0xc0 10/09/21 16:18 CRIS-DELL kernel [3.880168] ? syscall_exit_to_user_mode+0x27/0x50 10/09/21 16:18 CRIS-DELL kernel [3.880170] ? __x64_sys_newfstatat+0x1c/0x20 10/09/21 16:18 CRIS-DELL kernel [3.880171] ? do_syscall_64+0x69/0xc0 10/09/21 16:18 CRIS-DELL kernel [3.880173] ? do_syscall_64+0x69/0xc0 10/09/21 16:18 CRIS-DELL kernel [3.880174] ? do_syscall_64+0x69/0xc0 10/09/21 16:18 CRIS-DELL kernel [3.880175] ? sysvec_call_function+0x4e/0x90 10/09/21 16:18 CRIS-DELL kernel [3.880176] ? asm_sysvec_call_function+0xa/0x20 10/09/21 16:18 CRIS-DELL kernel [3.880178] entry_SYSCALL_64_after_hwframe+0x44/0xae 10/09/21 16:18 CRIS-DELL kernel [3.880180] RIP: 0033:0x7f0c3bfba70d 10/09/21 16:18 CRIS-DELL kernel [3.880181] Code: 5b 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d f3 66 0f 00 f7 d8 64 89 01 48 10/09/21 16:18 CRIS-DELL kernel [3.880183] RSP: 002b:7fff8c8cbf48 EFLAGS: 0246 ORIG_RAX: 0139 10/09/21 16:18 CRIS-DELL kernel [3.880184] RAX: ffda RBX: 55c88ef2b280 RCX: 7f0c3bfba70d 10/09/21 16:18 CRIS-DELL kernel [3.880185] RDX: RSI: 55c88ef0ccb0 RDI: 0017 10/09/21 16:18 CRIS-DELL kernel [3.880186] RBP: 0002 R08: R09: 55c88ef0ff60 10/09/21 16:18 CRIS-DELL kernel [
[Bug 1943277] Re: libxml2 2.9.12+dfsg-3 causes regression
** Changed in: libxml2 (Ubuntu) Assignee: (unassigned) => Mattia Rizzolo (mapreri) ** Changed in: libxml2 (Ubuntu) Status: Triaged => 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/1943277 Title: libxml2 2.9.12+dfsg-3 causes regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1943277/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943280] [NEW] OpenLDAP's ufw profile is redundant and can be removed
Public bug reported: The openldap package currently carries its own ufw profile as a delta against its Debian counterpart. Ryan (Debian openldap maintainer) noticed that the ufw package already installs a profile that covers OpenLDAP as well as other related services: https://git.launchpad.net/ufw/tree/profiles/ufw-directoryserver I'm filing this bug to serve as a reminder to make sure that we remove this unnecessary delta from the openldap package. ** Affects: openldap (Ubuntu) Importance: Medium Status: Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943280 Title: OpenLDAP's ufw profile is redundant and can be removed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1943280/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942894] Re: [SRU] libreoffice 7.1.6 for hirsute
** Changed in: libreoffice (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942894 Title: [SRU] libreoffice 7.1.6 for hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1942894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1942895] Re: Build fails on riscv64
This package is in sync with Debian and by adding this patch the package will no longer be automatically imported from Debian. Which is fine for a short period of time, but we need a plan for getting the package back in sync. Could you forward your patch to Debian and upstream? Additionally, adding DEP-3 headers to the patch would be helpful. https://dep-team.pages.debian.net/deps/dep3/ Thanks for working on this! ** Changed in: pocl (Ubuntu) Status: New => In Progress ** Changed in: pocl (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1942895 Title: Build fails on riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pocl/+bug/1942895/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868502] Re: Synchronization with earlier Ubuntu versions or a recent Debian version fails
Unison does not support syncing between two different versions. Hence, syncing across different ubuntu releases this problem will necessarily occur unless they contain many unison versions in the future. Workaround: 1) On both machines delete the unison cache: rm -r ~/.unison 2) Make sure no version of unison is installed on the machine with the newer Ubuntu release. 3) On the machine with the newer Ubuntu release download the unison .deb file of the older release. For example the .deb file of the unison version of Ubuntu 18.04 can be found here: https://ubuntu.pkgs.org/18.04/ubuntu-universe- amd64/unison_2.48.4-1ubuntu1_amd64.deb.html Install this unison version via the graphical interface. 4) On the machine with the newer Ubuntu release freeze the unison version you just installed. Warning you will not get security updates! sudo apt-mark hold unison 5) Sync both machines using unison. Have fun! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868502 Title: Synchronization with earlier Ubuntu versions or a recent Debian version fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unison/+bug/1868502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943188] Re: Ensure chrony is configured (Automated)
I copied over this from another host (same results): = # Welcome to the chrony configuration file. See chrony.conf(5) for more # information about usuable directives. # This will use (up to): # - 4 sources from ntp.ubuntu.com which some are ipv6 enabled # - 2 sources from 2.ubuntu.pool.ntp.org which is ipv6 enabled as well # - 1 source from [01].ubuntu.pool.ntp.org each (ipv4 only atm) # This means by default, up to 6 dual-stack and up to 2 additional IPv4-only # sources will be used. # At the same time it retains some protection against one of the entries being # down (compare to just using one of the lines). See (LP: #1754358) for the # discussion. # # About using servers from the NTP Pool Project in general see (LP: #104525). # Approved by Ubuntu Technical Board on 2011-02-08. # See http://www.pool.ntp.org/join.html for more information. #pool ntp.ubuntu.comiburst maxsources 4 pool 0.pool.ntp.org iburst maxsources 4 pool 1.pool.ntp.org iburst maxsources 4 pool 2.pool.ntp.org iburst maxsources 4 pool 3.pool.ntp.org iburst maxsources 4 # This directive specify the location of the file containing ID/key pairs for # NTP authentication. keyfile /etc/chrony/chrony.keys # This directive specify the file into which chronyd will store the rate # information. driftfile /var/lib/chrony/chrony.drift # Uncomment the following line to turn logging on. #log tracking measurements statistics # Log files location. logdir /var/log/chrony # Stop bad estimates upsetting machine clock. maxupdateskew 100.0 # This directive enables kernel synchronisation (every 11 minutes) of the # real-time clock. Note that it can’t be used along with the 'rtcfile' directive. rtcsync # Step the system clock instead of slewing it if the adjustment is larger than # one second, but only in the first three clock updates. makestep 1 3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943188 Title: Ensure chrony is configured (Automated) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1943188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943189] Re: "cannot refresh whilst network offline" bug
Pull request has been merged. https://github.com/PackageKit/PackageKit/pull/506 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943189 Title: "cannot refresh whilst network offline" bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1943189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943124] Re: Upgrade fails due to "text file busy"
Additional info: switched in the BIOS to single CPU with no hyperthreading and booted into recovery mode (and checked with cat /proc/cpuinfo that there was only a single CPU present to Linux). No change, still bombed out with the same error on apt --fix-broken install . So if there is a race condition, it would not appear to depend on having multiple CPUs even though of course there still is preemptive scheduling even with a single CPU. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943124 Title: Upgrade fails due to "text file busy" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1943124/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1022317] Re: cppunit1 picked up in maintainance mode on freedesktop
aye, this happened a couple of months after this bug was filed. ** Changed in: cppunit (Ubuntu) Status: New => 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/1022317 Title: cppunit1 picked up in maintainance mode on freedesktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cppunit/+bug/1022317/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820816] Re: With gcc flag -Werror programs are not compiling using the lib
this was naturally fixed with the flow when 1.15 was imported. ** Changed in: cppunit (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/1820816 Title: With gcc flag -Werror programs are not compiling using the lib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cppunit/+bug/1820816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870087] Re: Old broker lockfile blocks landscape-client starts
** Changed in: landscape-client Status: In Progress => Fix Committed ** Changed in: landscape-client Status: Fix Committed => 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/1870087 Title: Old broker lockfile blocks landscape-client starts To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1870087/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943189] Re: "cannot refresh whilst network offline" bug
The packagekit maintainer (Richard Hughes) has requested this patch as a pull request, so this will be in packagekit upstream very, very soon. https://github.com/PackageKit/PackageKit/issues/336#issuecomment-91713 ** Bug watch added: github.com/PackageKit/PackageKit/issues #336 https://github.com/PackageKit/PackageKit/issues/336 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943189 Title: "cannot refresh whilst network offline" bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1943189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 985841] Re: Cppunit wont link without -Wl,--no-as-needed
currently, with cppunit 1.15.1, this works flawleslly, and I also doubt this had been a problem for long since --as-need has been default gcc behaviour in ubuntu for years already. ** Changed in: cppunit (Ubuntu) Status: New => 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/985841 Title: Cppunit wont link without -Wl,--no-as-needed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cppunit/+bug/985841/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925314] Re: no eject media message after install xubuntu
I am not getting the shutdown/eject in live in today's Lubuntu build, in either of my two normal test-cases. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925314 Title: no eject media message after install xubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1925314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870813] Re: Scilab does not start on bionic and focal
$ dput scilab_6.0.1-7ubuntu1\~18.04.2_source.changes Trying to upload package to ubuntu Checking signature on .changes gpg: /tmp/pkgs/bionic/scilab_6.0.1-7ubuntu1~18.04.2_source.changes: Valid signature from 1E918B66765B3E31 Checking signature on .dsc gpg: /tmp/pkgs/bionic/scilab_6.0.1-7ubuntu1~18.04.2.dsc: Valid signature from 1E918B66765B3E31 Uploading to ubuntu (via ftp to upload.ubuntu.com): Uploading scilab_6.0.1-7ubuntu1~18.04.2.dsc: done. Uploading scilab_6.0.1-7ubuntu1~18.04.2.debian.tar.xz: done. Uploading scilab_6.0.1-7ubuntu1~18.04.2_source.buildinfo: done. Uploading scilab_6.0.1-7ubuntu1~18.04.2_source.changes: done. Successfully uploaded packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870813 Title: Scilab does not start on bionic and focal To manage notifications about this bug go to: https://bugs.launchpad.net/scilab/+bug/1870813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925314] Re: no eject media message after install xubuntu
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: casper (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925314 Title: no eject media message after install xubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1925314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1934129] Re: disable neutron-fwaas for >= victoria
This is now fixed in all corresponing branches (victoria+) in package repository [1] and will be included with the next point release uploads [2]. [1] https://code.launchpad.net/~ubuntu-openstack-dev/ubuntu/+source/neutron/+git/neutron [2] https://review.opendev.org/c/openstack/releases/+/808012 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1934129 Title: disable neutron-fwaas for >= victoria To manage notifications about this bug go to: https://bugs.launchpad.net/charm-guide/+bug/1934129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1938477] Re: Screen brightness changing randomly with kernel 5.11.0-25
Since the -16 version of the kernel was not available anymore, the bug was back for me. I then downloaded and installed 5.11.1-051101-generic with mainline and the bug is NOT happening with this kernel version. Hope this info helps. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1938477 Title: Screen brightness changing randomly with kernel 5.11.0-25 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1938477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895549] Re: Revert dnspython to 1.16.0 in Groovy
It looks like there's been some progress with eventlet supporting dnspython 2.0: https://github.com/eventlet/eventlet/commit/aeb0390094a1c3f29bb4f25a8dab96587a86b3e8 I've sent an email to the openstack-discuss mailing list. I'm hoping for impish+1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895549 Title: Revert dnspython to 1.16.0 in Groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnspython/+bug/1895549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870813] Re: Scilab does not start on bionic and focal
$ dput scilab_6.1.0+dfsg1-1ubuntu3.1_source.changes Trying to upload package to ubuntu Checking signature on .changes gpg: /tmp/pkgs/focal/scilab_6.1.0+dfsg1-1ubuntu3.1_source.changes: Valid signature from 1E918B66765B3E31 Checking signature on .dsc gpg: /tmp/pkgs/focal/scilab_6.1.0+dfsg1-1ubuntu3.1.dsc: Valid signature from 1E918B66765B3E31 Uploading to ubuntu (via ftp to upload.ubuntu.com): Uploading scilab_6.1.0+dfsg1-1ubuntu3.1.dsc: done. Uploading scilab_6.1.0+dfsg1-1ubuntu3.1.debian.tar.xz: done. Uploading scilab_6.1.0+dfsg1-1ubuntu3.1_source.buildinfo: done. Uploading scilab_6.1.0+dfsg1-1ubuntu3.1_source.changes: done. Successfully uploaded packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870813 Title: Scilab does not start on bionic and focal To manage notifications about this bug go to: https://bugs.launchpad.net/scilab/+bug/1870813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943133] Re: Sync expat 2.4.1-1 (main) from Debian experimental (main)
** Attachment added: "expat_2.4.1-1_amd64.build" https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1943133/+attachment/5524437/+files/expat_2.4.1-1_amd64.build ** Summary changed: - Sync expat 2.4.1-1 (main) from Debian experimental (main) + [FFe] Sync expat 2.4.1-1 (main) from Debian experimental (main) ** Description changed: Please sync expat 2.4.1-1 (main) from Debian experimental (main) https://github.com/libexpat/libexpat/blob/R_2_4_1/expat/Changes CVE-2013-0340 https://github.com/libexpat/libexpat/pull/466/files Changelog entries since current impish version 2.3.0-1: expat (2.4.1-1) experimental; urgency=high * New upstream release: - fix CVE-2013-0340: protect against billion laughs attacks (denial-of-service; flavors targeting CPU time or RAM or both, leveraging general entities or parameter entities or both). * Update libexpat1 symbols. -- Laszlo Boszormenyi (GCS) Mon, 24 May 2021 10:14:11 +0200 - - Release 2.4.1 Sun May 23 2021 - Bug fixes: - #488 #490 Autotools: Fix installed header expat_config.h for multilib - systems; regression introduced in 2.4.0 by pull request #486 - - Other changes: - #491 #492 Version info bumped from 9:0:8 to 9:1:8; - see https://verbump.de/ for what these numbers do - - Release 2.4.0 Sun May 23 2021 - Security fixes: - #34 #466 #484 CVE-2013-0340/CWE-776 -- Protect against billion laughs attacks - (denial-of-service; flavors targeting CPU time or RAM or both, - leveraging general entities or parameter entities or both) - by tracking and limiting the input amplification factor - ( := ( + ) / ). - By conservative default, amplification up to a factor of 100.0 - is tolerated and rejection only starts after 8 MiB of output bytes - (= + ) have been processed. - The fix adds the following to the API: - - A new error code XML_ERROR_AMPLIFICATION_LIMIT_BREACH to - signals this specific condition. - - Two new API functions .. - - XML_SetBillionLaughsAttackProtectionMaximumAmplification and - - XML_SetBillionLaughsAttackProtectionActivationThreshold - .. to further tighten billion laughs protection parameters - when desired. Please see file "doc/reference.html" for details. - If you ever need to increase the defaults for non-attack XML - payload, please file a bug report with libexpat. - - Two new XML_FEATURE_* constants .. - - that can be queried using the XML_GetFeatureList function, and - - that are shown in "xmlwf -v" output. - - Two new environment variable switches .. - - EXPAT_ACCOUNTING_DEBUG=(0|1|2|3) and - - EXPAT_ENTITY_DEBUG=(0|1) - .. for runtime debugging of accounting and entity processing. - Specific behavior of these values may change in the future. - - Two new command line arguments "-a FACTOR" and "-b BYTES" - for xmlwf to further tighten billion laughs protection - parameters when desired. - If you ever need to increase the defaults for non-attack XML - payload, please file a bug report with libexpat. - - Bug fixes: - #332 #470 For (non-default) compilation with -DEXPAT_MIN_SIZE=ON (CMake) - or CPPFLAGS=-DXML_MIN_SIZE (GNU Autotools): Fix segfault - for UTF-16 payloads containing CDATA sections. - #485 #486 Autotools: Fix generated CMake files for non-64bit and - non-Linux platforms (e.g. macOS and MinGW in particular) - that were introduced with release 2.3.0 - - Other changes: - #468 #469 xmlwf: Improve help output and the xmlwf man page - #463 xmlwf: Improve maintainability through some refactoring - #477 xmlwf: Fix man page DocBook validity - #458 #459 CMake: Support absolute paths for both CMAKE_INSTALL_LIBDIR - and CMAKE_INSTALL_INCLUDEDIR - #471 #481 CMake: Add support for standard variable BUILD_SHARED_LIBS - #457 Unexpose symbol _INTERNAL_trim_to_complete_utf8_characters - #467 Resolve macro HAVE_EXPAT_CONFIG_H - #472 Delete unused legacy helper file "conftools/PrintPath" - #473 #483 Improve attribution - #464 #465 #477 doc/reference.html: Fix XHTML validity - #475 #478 doc/reference.html: Replace the 90s look
[Bug 1895549] Re: Revert dnspython to 1.16.0 in Groovy
Hi Oibaf, Let me check with upstream. They are still bound to 1.16.0 in their upper-constraints: https://github.com/openstack/requirements/blob/master/upper- constraints.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895549 Title: Revert dnspython to 1.16.0 in Groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnspython/+bug/1895549/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943133] Re: Sync expat 2.4.1-1 (main) from Debian experimental (main)
** Attachment added: "expat_2.4.1-1.changelog" https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1943133/+attachment/5524436/+files/expat_2.4.1-1.changelog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943133 Title: [FFe] Sync expat 2.4.1-1 (main) from Debian experimental (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1943133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943133] Re: Sync expat 2.4.1-1 (main) from Debian experimental (main)
** Patch added: "expat_2.4.1-1.debdiff" https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1943133/+attachment/5524435/+files/expat_2.4.1-1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943133 Title: [FFe] Sync expat 2.4.1-1 (main) from Debian experimental (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1943133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936664] Re: buildmode=c-shared not supported on linux/risc-v
** Changed in: golang-1.16 (Ubuntu) Status: New => Fix Committed ** Changed in: golang-1.16 (Ubuntu) Importance: Wishlist => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936664 Title: buildmode=c-shared not supported on linux/risc-v To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang-1.16/+bug/1936664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943133] Re: Sync expat 2.4.1-1 (main) from Debian experimental (main)
This has quite an impact with 264 reverse-depends, so does this security issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943133 Title: Sync expat 2.4.1-1 (main) from Debian experimental (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1943133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943277] [NEW] libxml2 2.9.12+dfsg-3 causes regression
Public bug reported:
root@i1:~# cat example.xml
fake-name
root@i1:~# cat xml.py
from lxml import etree
def parseXML(xmlFile):
# Parse the xml
with open(xmlFile) as fobj:
xml = fobj.read()
doc = etree.fromstring(xml)
ret = doc.findall('./devices/interface')
node_xml = etree.tostring(ret[0]).decode()
print("node_xml={}".format(node_xml))
if __name__ == "__main__":
parseXML("example.xml")
== Expected result ==
root@i1:~# python3 xml.py
node_xml=
== Actual Result ==
root@i1:~# python3 xml.py
node_xml=
This is broken in 2.9.12+dfsg-3 on impish.
It is not broken in 2.9.10+dfsg-6.3ubuntu0.1 on hirsute.
There are some fixes in master since the 2.9.12 release was cut.
https://gitlab.gnome.org/GNOME/libxml2/-/commits/master
I'm planning to pick all 3 of the following commits from upstream master
since they are all intertwined. With this patches the regression is
fixed.
85b1792e37b131e7a51af98a37f92472e8de5f3f:
Work around lxml API abuse. Make xmlNodeDumpOutput and htmlNodeDumpFormatOutput
work with corrupted parent pointers.
13ad8736d294536da4cbcd70a96b0a2fbf47070c:
Add patch from upstream to fix regression in xmlNodeDumpOutputInternal. Commit
85b1792e could cause additional whitespace if xmlNodeDump was called with a
non-zero starting level.
92d9ab4c28842a09ca2b76d3ff2f933e01b6cd6f:
Add patch from upstream to fix whitespace when serializing empty HTML documents.
** Affects: libxml2 (Ubuntu)
Importance: High
Status: Triaged
** Summary changed:
- libxml2 causes regression in python3-lxml2
+ libxml2 2.9.12+dfsg-3 causes regression
** Description changed:
- root@i1:~# cat example.xml
+ root@i1:~# cat example.xml
- fake-name
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+ fake-name
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
- root@i1:~# cat xml.py
+ root@i1:~# cat xml.py
from lxml import etree
def parseXML(xmlFile):
- # Parse the xml
- with open(xmlFile) as fobj:
- xml = fobj.read()
+ # Parse the xml
+ with open(xmlFile) as fobj:
+ xml = fobj.read()
- doc = etree.fromstring(xml)
- ret = doc.findall('./devices/interface')
- node_xml = etree.tostring(ret[0]).decode()
- print("node_xml={}".format(node_xml))
+ doc = etree.fromstring(xml)
+ ret = doc.findall('./devices/interface')
+ node_xml = etree.tostring(ret[0]).decode()
+ print("node_xml={}".format(node_xml))
if __name__ == "__main__":
- parseXML("example.xml")
+ parseXML("example.xml")
+ == Expected result ==
- Expected result:
+ root@i1:~# python3 xml.py
+ node_xml=
+
+
+
+
+
+
+
+
+
+
- root@i1:~# python3 xml.py
+ == Actual Result ==
+
+ root@i1:~# python3 xml.py
node_xml=
-
-
-
-
-
-
-
-
-
-
-
- Actual Result:
-
- root@i1:~# python3 xml.py
- node_xml=
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
This is broken in 2.9.12+dfsg-3 on impish.
It is not broken in 2.9.10+dfsg-6.3ubuntu0.1 on hirsute.
There are some fixes in master since the 2.9.12 release was cut.
https://gitlab.gnome.org/GNOME/libxml2/-/commits/master
I'm planning to pick all 3 of these from upstream master since they are all
intertwined. With this patches the regression is fixed.
85b1792e37b131e7a51af98a37f92472e8de5f3f:
Work around lxml API abuse. Make xmlNodeDumpOutput and
htmlNodeDumpFormatOutput work with corrupted parent pointers.
13ad8736d294536da4cbcd70a96b0a2fbf47070c:
Add patch from upstream to fix regression in xmlNodeDumpOutputInternal.
Commit 85b1792e could cause additional whitespace if xmlNodeDump was called
with a non-zero starting level.
92d9ab4c28842a09ca2b76d3ff2f933e01b6cd6f:
Add patch from upstream to fix whitespace when serializing empty HTML
documents.
** Description changed:
root@i1:~# cat example.xml
fake-name
root@i1:~# cat xml.py
from lxml import etree
def parseXML(xmlFile):
# Parse the xml
with open(xmlFile) as fobj:
xml = fobj.read()
doc = etree.fromstring(xml)
ret = doc.findall('./devices/interface')
node_xml = etree.tostring(ret[0]).decode()
[Bug 1903288] Comment bridged from LTC Bugzilla
--- Comment From naynj...@ibm.com 2021-09-10 13:31 EDT--- I have posted the patch today - https://lore.kernel.org/linux-integrity/20210910172515.8430-1-na...@linux.ibm.com/T/#u . It would be very helpful if someone from Canonical can test it and confirm. Thanks & Regards, - Nayna -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903288 Title: Power guest secure boot with static keys: kernel portion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1903288/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940450] Re: XSS The data-template attribute of the tooltip and popover plugins lacks input sanitization and may allow attacker to execute arbitrary JavaScript.
Hello, I've made several attempts at exploiting the XSS in horizon without the updated version. I will attach a video for one of those attempts. To me this seems like horizon it's using the scanned code at all, unless I've missed something so this could be a false positive in my opinion. Thank You, Heather Lemon ** Attachment added: "xsshorizon-2021-09-10_11.30.01" https://bugs.launchpad.net/horizon/+bug/1940450/+attachment/5524434/+files/xsshorizon-2021-09-10_11.30.01 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940450 Title: XSS The data-template attribute of the tooltip and popover plugins lacks input sanitization and may allow attacker to execute arbitrary JavaScript. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1940450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940450] Re: XSS The data-template attribute of the tooltip and popover plugins lacks input sanitization and may allow attacker to execute arbitrary JavaScript.
Oh please use VLC to see video ;) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940450 Title: XSS The data-template attribute of the tooltip and popover plugins lacks input sanitization and may allow attacker to execute arbitrary JavaScript. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1940450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940450] Re: XSS The data-template attribute of the tooltip and popover plugins lacks input sanitization and may allow attacker to execute arbitrary JavaScript.
Hello, I've made several attempts at exploiting the XSS in horizon without the updated version. I will attach a video for one of those attempts. To me this seems like horizon it's using the scanned code at all, unless I've missed something so this could be a false positive in my opinion. Thank You, Heather Lemon -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940450 Title: XSS The data-template attribute of the tooltip and popover plugins lacks input sanitization and may allow attacker to execute arbitrary JavaScript. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1940450/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1943133] Re: Sync expat 2.4.1-1 (main) from Debian experimental (main)
** Description changed: Please sync expat 2.4.1-1 (main) from Debian experimental (main) Changelog entries since current impish version 2.3.0-1: expat (2.4.1-1) experimental; urgency=high - * New upstream release: - - fix CVE-2013-0340: protect against billion laughs attacks - (denial-of-service; flavors targeting CPU time or RAM or both, - leveraging general entities or parameter entities or both). - * Update libexpat1 symbols. + * New upstream release: + - fix CVE-2013-0340: protect against billion laughs attacks + (denial-of-service; flavors targeting CPU time or RAM or both, + leveraging general entities or parameter entities or both). + * Update libexpat1 symbols. - -- Laszlo Boszormenyi (GCS) Mon, 24 May 2021 10:14:11 + -- Laszlo Boszormenyi (GCS) Mon, 24 May 2021 10:14:11 +0200 + + + Release 2.4.1 Sun May 23 2021 + Bug fixes: +#488 #490 Autotools: Fix installed header expat_config.h for multilib + systems; regression introduced in 2.4.0 by pull request #486 + + Other changes: +#491 #492 Version info bumped from 9:0:8 to 9:1:8; + see https://verbump.de/ for what these numbers do + + + Release 2.4.0 Sun May 23 2021 + Security fixes: +#34 #466 #484 CVE-2013-0340/CWE-776 -- Protect against billion laughs attacks + (denial-of-service; flavors targeting CPU time or RAM or both, + leveraging general entities or parameter entities or both) + by tracking and limiting the input amplification factor + ( := ( + ) / ). + By conservative default, amplification up to a factor of 100.0 + is tolerated and rejection only starts after 8 MiB of output bytes + (= + ) have been processed. + The fix adds the following to the API: + - A new error code XML_ERROR_AMPLIFICATION_LIMIT_BREACH to + signals this specific condition. + - Two new API functions .. + - XML_SetBillionLaughsAttackProtectionMaximumAmplification and + - XML_SetBillionLaughsAttackProtectionActivationThreshold + .. to further tighten billion laughs protection parameters + when desired. Please see file "doc/reference.html" for details. + If you ever need to increase the defaults for non-attack XML + payload, please file a bug report with libexpat. + - Two new XML_FEATURE_* constants .. + - that can be queried using the XML_GetFeatureList function, and + - that are shown in "xmlwf -v" output. + - Two new environment variable switches .. + - EXPAT_ACCOUNTING_DEBUG=(0|1|2|3) and + - EXPAT_ENTITY_DEBUG=(0|1) + .. for runtime debugging of accounting and entity processing. + Specific behavior of these values may change in the future. + - Two new command line arguments "-a FACTOR" and "-b BYTES" + for xmlwf to further tighten billion laughs protection + parameters when desired. + If you ever need to increase the defaults for non-attack XML + payload, please file a bug report with libexpat. + + Bug fixes: +#332 #470 For (non-default) compilation with -DEXPAT_MIN_SIZE=ON (CMake) + or CPPFLAGS=-DXML_MIN_SIZE (GNU Autotools): Fix segfault + for UTF-16 payloads containing CDATA sections. +#485 #486 Autotools: Fix generated CMake files for non-64bit and + non-Linux platforms (e.g. macOS and MinGW in particular) + that were introduced with release 2.3.0 + + Other changes: +#468 #469 xmlwf: Improve help output and the xmlwf man page + #463 xmlwf: Improve maintainability through some refactoring + #477 xmlwf: Fix man page DocBook validity +#458 #459 CMake: Support absolute paths for both CMAKE_INSTALL_LIBDIR + and CMAKE_INSTALL_INCLUDEDIR +#471 #481 CMake: Add support for standard variable BUILD_SHARED_LIBS + #457 Unexpose symbol _INTERNAL_trim_to_complete_utf8_characters + #467 Resolve macro HAVE_EXPAT_CONFIG_H + #472 Delete unused legacy helper file "conftools/PrintPath" +#473 #483 Improve attribution + #464 #465 #477 doc/reference.html: Fix XHTML validity +#475 #478 doc/reference.html: Replace the 90s look by OK.css + #479 Version info bumped from 8:0:7 to 9:0:8 + due to addition of new symbols and
[Bug 1943133] Re: Sync expat 2.4.1-1 (main) from Debian experimental (main)
Per our discussion in IRC given where we are in the release cycle this would require a Feature Freeze Exception. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1943133 Title: Sync expat 2.4.1-1 (main) from Debian experimental (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/expat/+bug/1943133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1937897] Re: GPIO error logs in start and dmesg after update of kernel
Added tag 'verification-failed-hirsute'. Enabled proposed and installed package 'linux-image-5.13.0-14-generic' version '5.13.0-14.14~20.04.4' on my 20.04.3 LTS, and still get in dmesg: [1.228729] gpio gpiochip1: (gpio_aaeon): tried to insert a GPIO chip with zero lines [1.228732] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to register, -22 [1.228735] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22 [7.238390] gpio gpiochip1: (gpio_aaeon): tried to insert a GPIO chip with zero lines [7.238396] gpiochip_add_data_with_key: GPIOs 0..-1 (gpio_aaeon) failed to register, -22 [7.238401] gpio-aaeon: probe of gpio-aaeon.0 failed with error -22 ** Tags removed: verification-needed-hirsute ** Tags added: verification-failed-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1937897 Title: GPIO error logs in start and dmesg after update of kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
