[Bug 1861556] Re: g-ir-scanner doesn't work
gobject-introspection needs proper dependencies. See the Debian report. ** Bug watch added: Debian Bug tracker #950267 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950267 ** Also affects: gobject-introspection (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950267 Importance: Unknown Status: Unknown ** Changed in: python3-defaults (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/1861556 Title: g-ir-scanner doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gobject-introspection/+bug/1861556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802994] Re: gnucash 3.3 crashes upon keypress in transaction
I experience the same problem in Linux Mint with gnuash version 3.8 Is there a solution (other than running gnucash as root)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802994 Title: gnucash 3.3 crashes upon keypress in transaction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnucash/+bug/1802994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748861] Re: Upgrade package to libwebsockets >= 2.3.0 for 18.04 LTS
> Why is the version kept at v2.0.3 ? In general, newer versions are packaged in newer Ubuntu releases. They are sometimes backported, but older releases are mostly unchanged except for security issues or critical bugs. See https://answers.launchpad.net/ubuntu/+faq/3037 for more details. The good news is that libwebsockets 3.2.1-3 is currently proposed for the upcoming Ubuntu Focal (https://bugs.launchpad.net/ubuntu/+source/libwebsockets/3.2.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/1748861 Title: Upgrade package to libwebsockets >= 2.3.0 for 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwebsockets/+bug/1748861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861554] Re: Radeon mobility HD3450 (RV620) heavy screen flickering after trying to upgrade kernel 4.15.0-54
** Attachment added: "flickering latest 4.15.0-76 kernel" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861554/+attachment/5324758/+files/apport.linux.latest_4.15.0-76_flickering.apport -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861554 Title: Radeon mobility HD3450 (RV620) heavy screen flickering after trying to upgrade kernel 4.15.0-54 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861251] Re: 'extended_part_no' referenced before assignment error during install
Hello here, I'm affected by the same bug. I do have a hard drive configured with an extended partition (msdos partition table and DOS extended partition). I've created a bright new GPT partition on a new installed hard drive. And this error pops when I'm trying to install Ubuntu 18.04.3 on this disk. I don't want the installation to touch anything of the legacy disk. During the install, I only select the new drive mount "/". The other drives are left untouched. Yet, I still have the error. Is there a workaround I can use? May that be to tell Ubuntu to not touch the first hard drive. Or maybe, use a previous Ubuntu ISO (18.04.1, 16.04 ?) Thanks for the help! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861251 Title: 'extended_part_no' referenced before assignment error during install To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1861251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861113] Re: xenial/linux-raspi2: 4.4.0-1129.138 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1861122 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Friday, 31. January 2020 12:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 186 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861113 Title: xenial/linux-raspi2: 4.4.0-1129.138 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861609] [NEW] login impossible from GUI on fresh Ubuntu 20.04 install
Public bug reported: I installed the latest Ubuntu 20.04 daily today (Feb. 2, 2020). The installation went fine and I created a user "minime". After reboot the login screen is displayed. However, after logging in, the login screen is displayed again. There are no error messages or anything. When I switch to the console, I can perform the login on the console. I hope the attached copy of the syslog file will help to find the issue. My last failed login attempt was around "Feb 2 14:12:50". ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "copy of the syslog file" https://bugs.launchpad.net/bugs/1861609/+attachment/5324770/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861609 Title: login impossible from GUI on fresh Ubuntu 20.04 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1861609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1859545] Re: Sticky keys repeat indefinitely unless if pressed again
I was able to test on Mate and the same problem was observed: sticky keys with the right timing to release the keys. It also seems independent from the guest, even a Windows 10 guest was affected by this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1859545 Title: Sticky keys repeat indefinitely unless if pressed again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1859545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861610] [NEW] 'Elan touchpad' not detected in 'Ubuntu 19.04' on 'Lenovo ThinkBook 15 IIL'
Public bug reported: The Elan touchpad on my Lenovo Thinkbook isn't being detected, and hence isn't working. `sudo acpidump | grep -C3 ELAN` gives me the device's ACPI id: ```bash ghosthawkzero@EchelonV:~$ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p. IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/bugs/1861610/+attachment/5324771/+files/devices -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861610 Title: 'Elan touchpad' not detected in 'Ubuntu 19.04' on 'Lenovo ThinkBook 15 IIL' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10
I'm running Eoan. After studying the comments here, I installed libgtk-3-0 from focal (https://packages.ubuntu.com/focal/libgtk-3-0). This forced me to upgrade CUPS. I'm not sure if printing still works, but the cut/copy/paste issue appears to be resolved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1655111] Re: LibVirt Apparmor profile has qemu-bridge-helper listed in the wrong directory
This bug was fixed in the package libvirt - 6.0.0-0ubuntu1
---
libvirt (6.0.0-0ubuntu1) focal; urgency=medium
* Merged with Debian 5.6.0-4 from experimental and v6.0.0 from upstream
Among many other new features and fixes this includes fixes for:
- LP: #1859253 - rbd driver fails to create a new volume
- LP: #1858341 - rbd driver does not list all volumes in pool
- LP: #1845506 - Libvirt snapshot doesn't update apparmor profile
- LP: #1854653 - slow libvirt-guests.sh during shutdown if service is off
- LP: #1848229 - enable ppc64el to use ccf-assist feature
- LP: #1853315 - Enable CPU Model Comparison and Baselining on s390x
- LP: #1853317 - CCW IPL support to boot from ECKD DASDs
- LP: #1859506 - security: AppArmor profile fixes for swtpm
Remaining changes:
- Disable libssh2 support (universe dependency)
- Disable firewalld support (universe dependency)
- Set qemu-group to kvm (for compat with older ubuntu)
- Additional apport package-hook
- Autostart default bridged network (As upstream does, but not Debian).
In addition to just enabling it our solution provides:
+ do not autostart if subnet is already taken (e.g. in guests).
+ iterate some alternative subnets before giving up
- d/p/ubuntu/Allow-libvirt-group-to-access-the-socket.patch: This is
the group based access to libvirt functions as it was used in Ubuntu
for quite long.
+ d/p/ubuntu/daemon-augeas-fix-expected.patch fix some related tests
due to the group access change.
+ d/libvirt-daemon-system.postinst: add users in sudo to the libvirt
group.
- ubuntu/parallel-shutdown.patch: set parallel shutdown by default.
- Update Vcs-Git and Vcs-Browser fields to point to launchpad
- Update README.Debian with Ubuntu changes
- Enable some additional features on ppc64el and s390x (for arch parity)
+ systemtap, zfs, numa and numad on s390x.
+ systemtap on ppc64el.
- d/p/ubuntu/ubuntu_machine_type.patch: accept ubuntu types as pci440fx
- Further upstreamed apparmor Delta, especially any new one
Our former delta is split into logical pieces and is either Ubuntu only
or is part of a continuous upstreaming effort.
Listing related remaining changes in debian/patches/ubuntu-aa/:
- fix autopkgtests
+ d/t/control, d/t/smoke-qemu-session: fixup smoke-qemu-session by making
vmlinuz available and accessible (Debian bug 848314)
+ d/t/control: fix smoke-qemu-session by ensuring the service will run
installing libvirt-daemon-system
+ d/t/smoke-lxc: fix smoke-lxc by ignoring potential issues on destroy as
long as the following undefine succeeds
+ d/t/smoke-lxc: use systemd instead of sysV to restart the service
- dnsmasq related enhancements
+ run dnsmasq as libvirt-dnsmasq (LP: 1743718)
+ d/libvirt-daemon-system.postinst: add libvirt-dnsmasq user and group
+ d/libvirt-daemon-system.postrm: remove libvirt-dnsmasq user and group
on purge
+ d/p/ubuntu/dnsmasq-as-priv-user: write dnsmasq config with user
libvirt-dnsmasq and adapt the self tests to expect that config
+ d/libvirt-daemon-system.postinst: fix old libvirt-dnsmasq users group
+ Add dnsmasq configuration to work with system wide dnsmasq-base
- debian/rules: disable the netcf backend. (LP: 1764314)
- debian/patches/ubuntu/ovmf_paths.patch: adjust paths to secboot.fd UEFI
Secure Boot enabled variants of the OVMF firmware and variable store for
the paths where we ship these files in Ubuntu.
- d/rules: install virtlockd correctly with defaults file (LP: 1729516)
- d/rules: also check build time self test results on all architectures
- d/p/ubuntu/set-default-machine-to-ubuntu.patch: to select default
machine type correctly with newer qemu/libvirt
- d/rules: add --no-restart-after-upgrade to services that are supposed to
stay up through upgrades - this also applies to related sockets.
- Apparmor Delta that is Ubuntu specific or yet to be upstreamed
split into logical pieces. File names in debian/patches/ubuntu-aa/:
+ 0003-apparmor-libvirt-qemu-Allow-read-access-to-overcommi.patch:
apparmor, libvirt-qemu: Allow read access to overcommit_memory
+ 0007-apparmor-libvirt-qemu-Allow-owner-read-access-to-PRO.patch:
apparmor, libvirt-qemu: Allow owner read access to @{PROC}/*/auxv
+ 0017-apparmor-virt-aa-helper-Allow-access-to-tmp-director.patch:
apparmor, virt-aa-helper: Allow access to tmp directories
+ 0020-virt-aa-helper-ubuntu-storage-paths.patch:
apparmor, virt-aa-helper: Allow various storage pools and image
locations
+ 0021-apparmor-virt-aa-helper-Add-openvswitch-support.patch:
apparmor, virt-aa-helper: Add openvswitch support
+ 0029-appmor-libvirt-qemu-Add-9p-support.patch: appmor,
[Bug 1854653] Re: during shutdown libvirt-guests.sh shouldn't run if libvirtd isn't running
This bug was fixed in the package libvirt - 6.0.0-0ubuntu1
---
libvirt (6.0.0-0ubuntu1) focal; urgency=medium
* Merged with Debian 5.6.0-4 from experimental and v6.0.0 from upstream
Among many other new features and fixes this includes fixes for:
- LP: #1859253 - rbd driver fails to create a new volume
- LP: #1858341 - rbd driver does not list all volumes in pool
- LP: #1845506 - Libvirt snapshot doesn't update apparmor profile
- LP: #1854653 - slow libvirt-guests.sh during shutdown if service is off
- LP: #1848229 - enable ppc64el to use ccf-assist feature
- LP: #1853315 - Enable CPU Model Comparison and Baselining on s390x
- LP: #1853317 - CCW IPL support to boot from ECKD DASDs
- LP: #1859506 - security: AppArmor profile fixes for swtpm
Remaining changes:
- Disable libssh2 support (universe dependency)
- Disable firewalld support (universe dependency)
- Set qemu-group to kvm (for compat with older ubuntu)
- Additional apport package-hook
- Autostart default bridged network (As upstream does, but not Debian).
In addition to just enabling it our solution provides:
+ do not autostart if subnet is already taken (e.g. in guests).
+ iterate some alternative subnets before giving up
- d/p/ubuntu/Allow-libvirt-group-to-access-the-socket.patch: This is
the group based access to libvirt functions as it was used in Ubuntu
for quite long.
+ d/p/ubuntu/daemon-augeas-fix-expected.patch fix some related tests
due to the group access change.
+ d/libvirt-daemon-system.postinst: add users in sudo to the libvirt
group.
- ubuntu/parallel-shutdown.patch: set parallel shutdown by default.
- Update Vcs-Git and Vcs-Browser fields to point to launchpad
- Update README.Debian with Ubuntu changes
- Enable some additional features on ppc64el and s390x (for arch parity)
+ systemtap, zfs, numa and numad on s390x.
+ systemtap on ppc64el.
- d/p/ubuntu/ubuntu_machine_type.patch: accept ubuntu types as pci440fx
- Further upstreamed apparmor Delta, especially any new one
Our former delta is split into logical pieces and is either Ubuntu only
or is part of a continuous upstreaming effort.
Listing related remaining changes in debian/patches/ubuntu-aa/:
- fix autopkgtests
+ d/t/control, d/t/smoke-qemu-session: fixup smoke-qemu-session by making
vmlinuz available and accessible (Debian bug 848314)
+ d/t/control: fix smoke-qemu-session by ensuring the service will run
installing libvirt-daemon-system
+ d/t/smoke-lxc: fix smoke-lxc by ignoring potential issues on destroy as
long as the following undefine succeeds
+ d/t/smoke-lxc: use systemd instead of sysV to restart the service
- dnsmasq related enhancements
+ run dnsmasq as libvirt-dnsmasq (LP: 1743718)
+ d/libvirt-daemon-system.postinst: add libvirt-dnsmasq user and group
+ d/libvirt-daemon-system.postrm: remove libvirt-dnsmasq user and group
on purge
+ d/p/ubuntu/dnsmasq-as-priv-user: write dnsmasq config with user
libvirt-dnsmasq and adapt the self tests to expect that config
+ d/libvirt-daemon-system.postinst: fix old libvirt-dnsmasq users group
+ Add dnsmasq configuration to work with system wide dnsmasq-base
- debian/rules: disable the netcf backend. (LP: 1764314)
- debian/patches/ubuntu/ovmf_paths.patch: adjust paths to secboot.fd UEFI
Secure Boot enabled variants of the OVMF firmware and variable store for
the paths where we ship these files in Ubuntu.
- d/rules: install virtlockd correctly with defaults file (LP: 1729516)
- d/rules: also check build time self test results on all architectures
- d/p/ubuntu/set-default-machine-to-ubuntu.patch: to select default
machine type correctly with newer qemu/libvirt
- d/rules: add --no-restart-after-upgrade to services that are supposed to
stay up through upgrades - this also applies to related sockets.
- Apparmor Delta that is Ubuntu specific or yet to be upstreamed
split into logical pieces. File names in debian/patches/ubuntu-aa/:
+ 0003-apparmor-libvirt-qemu-Allow-read-access-to-overcommi.patch:
apparmor, libvirt-qemu: Allow read access to overcommit_memory
+ 0007-apparmor-libvirt-qemu-Allow-owner-read-access-to-PRO.patch:
apparmor, libvirt-qemu: Allow owner read access to @{PROC}/*/auxv
+ 0017-apparmor-virt-aa-helper-Allow-access-to-tmp-director.patch:
apparmor, virt-aa-helper: Allow access to tmp directories
+ 0020-virt-aa-helper-ubuntu-storage-paths.patch:
apparmor, virt-aa-helper: Allow various storage pools and image
locations
+ 0021-apparmor-virt-aa-helper-Add-openvswitch-support.patch:
apparmor, virt-aa-helper: Add openvswitch support
+ 0029-appmor-libvirt-qemu-Add-9p-support.patch: appmor,
[Bug 1845506] Re: Libvirt snapshot doesn't update apparmor profile
This bug was fixed in the package libvirt - 6.0.0-0ubuntu1
---
libvirt (6.0.0-0ubuntu1) focal; urgency=medium
* Merged with Debian 5.6.0-4 from experimental and v6.0.0 from upstream
Among many other new features and fixes this includes fixes for:
- LP: #1859253 - rbd driver fails to create a new volume
- LP: #1858341 - rbd driver does not list all volumes in pool
- LP: #1845506 - Libvirt snapshot doesn't update apparmor profile
- LP: #1854653 - slow libvirt-guests.sh during shutdown if service is off
- LP: #1848229 - enable ppc64el to use ccf-assist feature
- LP: #1853315 - Enable CPU Model Comparison and Baselining on s390x
- LP: #1853317 - CCW IPL support to boot from ECKD DASDs
- LP: #1859506 - security: AppArmor profile fixes for swtpm
Remaining changes:
- Disable libssh2 support (universe dependency)
- Disable firewalld support (universe dependency)
- Set qemu-group to kvm (for compat with older ubuntu)
- Additional apport package-hook
- Autostart default bridged network (As upstream does, but not Debian).
In addition to just enabling it our solution provides:
+ do not autostart if subnet is already taken (e.g. in guests).
+ iterate some alternative subnets before giving up
- d/p/ubuntu/Allow-libvirt-group-to-access-the-socket.patch: This is
the group based access to libvirt functions as it was used in Ubuntu
for quite long.
+ d/p/ubuntu/daemon-augeas-fix-expected.patch fix some related tests
due to the group access change.
+ d/libvirt-daemon-system.postinst: add users in sudo to the libvirt
group.
- ubuntu/parallel-shutdown.patch: set parallel shutdown by default.
- Update Vcs-Git and Vcs-Browser fields to point to launchpad
- Update README.Debian with Ubuntu changes
- Enable some additional features on ppc64el and s390x (for arch parity)
+ systemtap, zfs, numa and numad on s390x.
+ systemtap on ppc64el.
- d/p/ubuntu/ubuntu_machine_type.patch: accept ubuntu types as pci440fx
- Further upstreamed apparmor Delta, especially any new one
Our former delta is split into logical pieces and is either Ubuntu only
or is part of a continuous upstreaming effort.
Listing related remaining changes in debian/patches/ubuntu-aa/:
- fix autopkgtests
+ d/t/control, d/t/smoke-qemu-session: fixup smoke-qemu-session by making
vmlinuz available and accessible (Debian bug 848314)
+ d/t/control: fix smoke-qemu-session by ensuring the service will run
installing libvirt-daemon-system
+ d/t/smoke-lxc: fix smoke-lxc by ignoring potential issues on destroy as
long as the following undefine succeeds
+ d/t/smoke-lxc: use systemd instead of sysV to restart the service
- dnsmasq related enhancements
+ run dnsmasq as libvirt-dnsmasq (LP: 1743718)
+ d/libvirt-daemon-system.postinst: add libvirt-dnsmasq user and group
+ d/libvirt-daemon-system.postrm: remove libvirt-dnsmasq user and group
on purge
+ d/p/ubuntu/dnsmasq-as-priv-user: write dnsmasq config with user
libvirt-dnsmasq and adapt the self tests to expect that config
+ d/libvirt-daemon-system.postinst: fix old libvirt-dnsmasq users group
+ Add dnsmasq configuration to work with system wide dnsmasq-base
- debian/rules: disable the netcf backend. (LP: 1764314)
- debian/patches/ubuntu/ovmf_paths.patch: adjust paths to secboot.fd UEFI
Secure Boot enabled variants of the OVMF firmware and variable store for
the paths where we ship these files in Ubuntu.
- d/rules: install virtlockd correctly with defaults file (LP: 1729516)
- d/rules: also check build time self test results on all architectures
- d/p/ubuntu/set-default-machine-to-ubuntu.patch: to select default
machine type correctly with newer qemu/libvirt
- d/rules: add --no-restart-after-upgrade to services that are supposed to
stay up through upgrades - this also applies to related sockets.
- Apparmor Delta that is Ubuntu specific or yet to be upstreamed
split into logical pieces. File names in debian/patches/ubuntu-aa/:
+ 0003-apparmor-libvirt-qemu-Allow-read-access-to-overcommi.patch:
apparmor, libvirt-qemu: Allow read access to overcommit_memory
+ 0007-apparmor-libvirt-qemu-Allow-owner-read-access-to-PRO.patch:
apparmor, libvirt-qemu: Allow owner read access to @{PROC}/*/auxv
+ 0017-apparmor-virt-aa-helper-Allow-access-to-tmp-director.patch:
apparmor, virt-aa-helper: Allow access to tmp directories
+ 0020-virt-aa-helper-ubuntu-storage-paths.patch:
apparmor, virt-aa-helper: Allow various storage pools and image
locations
+ 0021-apparmor-virt-aa-helper-Add-openvswitch-support.patch:
apparmor, virt-aa-helper: Add openvswitch support
+ 0029-appmor-libvirt-qemu-Add-9p-support.patch: appmor,
[Bug 1858341] Re: rbd driver does not list all volumes in pool
This bug was fixed in the package libvirt - 6.0.0-0ubuntu1
---
libvirt (6.0.0-0ubuntu1) focal; urgency=medium
* Merged with Debian 5.6.0-4 from experimental and v6.0.0 from upstream
Among many other new features and fixes this includes fixes for:
- LP: #1859253 - rbd driver fails to create a new volume
- LP: #1858341 - rbd driver does not list all volumes in pool
- LP: #1845506 - Libvirt snapshot doesn't update apparmor profile
- LP: #1854653 - slow libvirt-guests.sh during shutdown if service is off
- LP: #1848229 - enable ppc64el to use ccf-assist feature
- LP: #1853315 - Enable CPU Model Comparison and Baselining on s390x
- LP: #1853317 - CCW IPL support to boot from ECKD DASDs
- LP: #1859506 - security: AppArmor profile fixes for swtpm
Remaining changes:
- Disable libssh2 support (universe dependency)
- Disable firewalld support (universe dependency)
- Set qemu-group to kvm (for compat with older ubuntu)
- Additional apport package-hook
- Autostart default bridged network (As upstream does, but not Debian).
In addition to just enabling it our solution provides:
+ do not autostart if subnet is already taken (e.g. in guests).
+ iterate some alternative subnets before giving up
- d/p/ubuntu/Allow-libvirt-group-to-access-the-socket.patch: This is
the group based access to libvirt functions as it was used in Ubuntu
for quite long.
+ d/p/ubuntu/daemon-augeas-fix-expected.patch fix some related tests
due to the group access change.
+ d/libvirt-daemon-system.postinst: add users in sudo to the libvirt
group.
- ubuntu/parallel-shutdown.patch: set parallel shutdown by default.
- Update Vcs-Git and Vcs-Browser fields to point to launchpad
- Update README.Debian with Ubuntu changes
- Enable some additional features on ppc64el and s390x (for arch parity)
+ systemtap, zfs, numa and numad on s390x.
+ systemtap on ppc64el.
- d/p/ubuntu/ubuntu_machine_type.patch: accept ubuntu types as pci440fx
- Further upstreamed apparmor Delta, especially any new one
Our former delta is split into logical pieces and is either Ubuntu only
or is part of a continuous upstreaming effort.
Listing related remaining changes in debian/patches/ubuntu-aa/:
- fix autopkgtests
+ d/t/control, d/t/smoke-qemu-session: fixup smoke-qemu-session by making
vmlinuz available and accessible (Debian bug 848314)
+ d/t/control: fix smoke-qemu-session by ensuring the service will run
installing libvirt-daemon-system
+ d/t/smoke-lxc: fix smoke-lxc by ignoring potential issues on destroy as
long as the following undefine succeeds
+ d/t/smoke-lxc: use systemd instead of sysV to restart the service
- dnsmasq related enhancements
+ run dnsmasq as libvirt-dnsmasq (LP: 1743718)
+ d/libvirt-daemon-system.postinst: add libvirt-dnsmasq user and group
+ d/libvirt-daemon-system.postrm: remove libvirt-dnsmasq user and group
on purge
+ d/p/ubuntu/dnsmasq-as-priv-user: write dnsmasq config with user
libvirt-dnsmasq and adapt the self tests to expect that config
+ d/libvirt-daemon-system.postinst: fix old libvirt-dnsmasq users group
+ Add dnsmasq configuration to work with system wide dnsmasq-base
- debian/rules: disable the netcf backend. (LP: 1764314)
- debian/patches/ubuntu/ovmf_paths.patch: adjust paths to secboot.fd UEFI
Secure Boot enabled variants of the OVMF firmware and variable store for
the paths where we ship these files in Ubuntu.
- d/rules: install virtlockd correctly with defaults file (LP: 1729516)
- d/rules: also check build time self test results on all architectures
- d/p/ubuntu/set-default-machine-to-ubuntu.patch: to select default
machine type correctly with newer qemu/libvirt
- d/rules: add --no-restart-after-upgrade to services that are supposed to
stay up through upgrades - this also applies to related sockets.
- Apparmor Delta that is Ubuntu specific or yet to be upstreamed
split into logical pieces. File names in debian/patches/ubuntu-aa/:
+ 0003-apparmor-libvirt-qemu-Allow-read-access-to-overcommi.patch:
apparmor, libvirt-qemu: Allow read access to overcommit_memory
+ 0007-apparmor-libvirt-qemu-Allow-owner-read-access-to-PRO.patch:
apparmor, libvirt-qemu: Allow owner read access to @{PROC}/*/auxv
+ 0017-apparmor-virt-aa-helper-Allow-access-to-tmp-director.patch:
apparmor, virt-aa-helper: Allow access to tmp directories
+ 0020-virt-aa-helper-ubuntu-storage-paths.patch:
apparmor, virt-aa-helper: Allow various storage pools and image
locations
+ 0021-apparmor-virt-aa-helper-Add-openvswitch-support.patch:
apparmor, virt-aa-helper: Add openvswitch support
+ 0029-appmor-libvirt-qemu-Add-9p-support.patch: appmor,
[Bug 1859253] Re: rbd driver fails to create a new volume
This bug was fixed in the package libvirt - 6.0.0-0ubuntu1
---
libvirt (6.0.0-0ubuntu1) focal; urgency=medium
* Merged with Debian 5.6.0-4 from experimental and v6.0.0 from upstream
Among many other new features and fixes this includes fixes for:
- LP: #1859253 - rbd driver fails to create a new volume
- LP: #1858341 - rbd driver does not list all volumes in pool
- LP: #1845506 - Libvirt snapshot doesn't update apparmor profile
- LP: #1854653 - slow libvirt-guests.sh during shutdown if service is off
- LP: #1848229 - enable ppc64el to use ccf-assist feature
- LP: #1853315 - Enable CPU Model Comparison and Baselining on s390x
- LP: #1853317 - CCW IPL support to boot from ECKD DASDs
- LP: #1859506 - security: AppArmor profile fixes for swtpm
Remaining changes:
- Disable libssh2 support (universe dependency)
- Disable firewalld support (universe dependency)
- Set qemu-group to kvm (for compat with older ubuntu)
- Additional apport package-hook
- Autostart default bridged network (As upstream does, but not Debian).
In addition to just enabling it our solution provides:
+ do not autostart if subnet is already taken (e.g. in guests).
+ iterate some alternative subnets before giving up
- d/p/ubuntu/Allow-libvirt-group-to-access-the-socket.patch: This is
the group based access to libvirt functions as it was used in Ubuntu
for quite long.
+ d/p/ubuntu/daemon-augeas-fix-expected.patch fix some related tests
due to the group access change.
+ d/libvirt-daemon-system.postinst: add users in sudo to the libvirt
group.
- ubuntu/parallel-shutdown.patch: set parallel shutdown by default.
- Update Vcs-Git and Vcs-Browser fields to point to launchpad
- Update README.Debian with Ubuntu changes
- Enable some additional features on ppc64el and s390x (for arch parity)
+ systemtap, zfs, numa and numad on s390x.
+ systemtap on ppc64el.
- d/p/ubuntu/ubuntu_machine_type.patch: accept ubuntu types as pci440fx
- Further upstreamed apparmor Delta, especially any new one
Our former delta is split into logical pieces and is either Ubuntu only
or is part of a continuous upstreaming effort.
Listing related remaining changes in debian/patches/ubuntu-aa/:
- fix autopkgtests
+ d/t/control, d/t/smoke-qemu-session: fixup smoke-qemu-session by making
vmlinuz available and accessible (Debian bug 848314)
+ d/t/control: fix smoke-qemu-session by ensuring the service will run
installing libvirt-daemon-system
+ d/t/smoke-lxc: fix smoke-lxc by ignoring potential issues on destroy as
long as the following undefine succeeds
+ d/t/smoke-lxc: use systemd instead of sysV to restart the service
- dnsmasq related enhancements
+ run dnsmasq as libvirt-dnsmasq (LP: 1743718)
+ d/libvirt-daemon-system.postinst: add libvirt-dnsmasq user and group
+ d/libvirt-daemon-system.postrm: remove libvirt-dnsmasq user and group
on purge
+ d/p/ubuntu/dnsmasq-as-priv-user: write dnsmasq config with user
libvirt-dnsmasq and adapt the self tests to expect that config
+ d/libvirt-daemon-system.postinst: fix old libvirt-dnsmasq users group
+ Add dnsmasq configuration to work with system wide dnsmasq-base
- debian/rules: disable the netcf backend. (LP: 1764314)
- debian/patches/ubuntu/ovmf_paths.patch: adjust paths to secboot.fd UEFI
Secure Boot enabled variants of the OVMF firmware and variable store for
the paths where we ship these files in Ubuntu.
- d/rules: install virtlockd correctly with defaults file (LP: 1729516)
- d/rules: also check build time self test results on all architectures
- d/p/ubuntu/set-default-machine-to-ubuntu.patch: to select default
machine type correctly with newer qemu/libvirt
- d/rules: add --no-restart-after-upgrade to services that are supposed to
stay up through upgrades - this also applies to related sockets.
- Apparmor Delta that is Ubuntu specific or yet to be upstreamed
split into logical pieces. File names in debian/patches/ubuntu-aa/:
+ 0003-apparmor-libvirt-qemu-Allow-read-access-to-overcommi.patch:
apparmor, libvirt-qemu: Allow read access to overcommit_memory
+ 0007-apparmor-libvirt-qemu-Allow-owner-read-access-to-PRO.patch:
apparmor, libvirt-qemu: Allow owner read access to @{PROC}/*/auxv
+ 0017-apparmor-virt-aa-helper-Allow-access-to-tmp-director.patch:
apparmor, virt-aa-helper: Allow access to tmp directories
+ 0020-virt-aa-helper-ubuntu-storage-paths.patch:
apparmor, virt-aa-helper: Allow various storage pools and image
locations
+ 0021-apparmor-virt-aa-helper-Add-openvswitch-support.patch:
apparmor, virt-aa-helper: Add openvswitch support
+ 0029-appmor-libvirt-qemu-Add-9p-support.patch: appmor,
[Bug 1861609] Re: login impossible from GUI on fresh Ubuntu 20.04 install
** Description changed: - I installed the latest Ubuntu 20.04 daily today (Feb. 2, 2020). The - installation went fine and I created a user "minime". After reboot the - login screen is displayed. However, after logging in, the login screen - is displayed again. There are no error messages or anything. + I installed the latest Ubuntu 20.04 daily today (Feb. 2, 2020). During + the installation I created a user "minime". After reboot the login + screen is displayed. However, after entering the credentials and logging + in, the login screen just reappears. There are no error messages or + anything. When I switch to the console, I can perform the login on the console. I hope the attached copy of the syslog file will help to find the issue. My last failed login attempt was around "Feb 2 14:12:50". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861609 Title: login impossible from GUI on fresh Ubuntu 20.04 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1861609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861179] Re: bionic/linux-aws-5.0: 5.0.0-1025.28 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1861192 packages: lrm: linux-restricted-modules-aws-5.0 main: linux-aws-5.0 meta: linux-meta-aws-5.0 phase: Testing phase-changed: Friday, 31. January 2020 09:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861179 Title: bionic/linux-aws-5.0: 5.0.0-1025.28 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1846367] Re: udev /dev/null incorrect permissions after package auto upgrades
Problem still occurs from time to time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1846367 Title: udev /dev/null incorrect permissions after package auto upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1846367/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1651635] Re: XPS 13 9360 trackpad locks into scroll mode
@ads-launchpad, that looks like a separate issue. Please make a new report (especially as this is in the project(?)/category(?) *dell- sputnik* in Launchpad, and also upstream. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1651635 Title: XPS 13 9360 trackpad locks into scroll mode To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1651635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744507] Re: *** Error in `stubby': double free or corruption (!prev): 0x0000561985221410 ***
** Bug watch added: github.com/getdnsapi/getdns/issues #222 https://github.com/getdnsapi/getdns/issues/222 ** Also affects: getdns via https://github.com/getdnsapi/getdns/issues/222 Importance: Unknown Status: Unknown ** Changed in: getdns (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/1744507 Title: *** Error in `stubby': double free or corruption (!prev): 0x561985221410 *** To manage notifications about this bug go to: https://bugs.launchpad.net/getdns/+bug/1744507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861598] [NEW] lightdm assumes pam-kwallet to be always installed
Public bug reported: During boot, I see this error: > Feb 02 10:50:05 myhost lightdm[3224]: PAM unable to dlopen(pam_kwallet.so): > /lib/security/pam_kwallet.so: cannot open shared object file: No such file or > directory > Feb 02 10:50:05 myhost lightdm[3224]: PAM adding faulty module: pam_kwallet.so > Feb 02 10:50:05 myhost lightdm[3224]: PAM unable to dlopen(pam_kwallet5.so): > /lib/security/pam_kwallet5.so: cannot open shared object file: No such file > or directory > Feb 02 10:50:05 myhost lightdm[3224]: PAM adding faulty module: > pam_kwallet5.so which I guess it's caused by this: > # grep kwallet /etc/pam.d/lightd* > /etc/pam.d/lightdm:authoptionalpam_kwallet.so > /etc/pam.d/lightdm:authoptionalpam_kwallet5.so > /etc/pam.d/lightdm:session optionalpam_kwallet.so auto_start > /etc/pam.d/lightdm:session optionalpam_kwallet5.so auto_start > /etc/pam.d/lightdm-greeter:authoptionalpam_kwallet.so > /etc/pam.d/lightdm-greeter:authoptionalpam_kwallet5.so > /etc/pam.d/lightdm-greeter:session optionalpam_kwallet.so auto_start > /etc/pam.d/lightdm-greeter:session optionalpam_kwallet5.so auto_start kwallet is a KDE program, which is not installed on MATE (and I think it shouldn't be), so I guess that such modules should not be [attempted to be] loaded. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Sun Feb 2 11:03:53 2020 InstallationDate: Installed on 2020-01-20 (12 days ago) InstallationMedia: Ubuntu-MATE 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1861598 Title: lightdm assumes pam-kwallet to be always installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1861598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861411] Re: systemd unit startup timeout too short
Hi Dennis! Thank you for your report. This a already been fixed, see: https://github.com/MariaDB/server/commit/d78f02d73d5b Also, if 900 is not sufficient (it can be in some cases), you also have the option of setting it as infinite, see: https://mariadb.com/kb/en/systemd/#configuring-the-systemd-service-timeout Faustin -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861411 Title: systemd unit startup timeout too short To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1861411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1855892] Re: nvme SSD disk not appearing at S3 resume
Problem apparently solved (i.e., SDD wakes up from S3, can remove "mem_sleep_default=shallow" from grub) with today's BIOS update to 2.0.2. Or with some firmware update associated with it. The problem with Dell is that these firmware updates declare to address only obscure security tickets, not the real problems... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1855892 Title: nvme SSD disk not appearing at S3 resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1855892/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852903] Re: systemd Caught , dumped core
Yes, it is our custom service: # cat /var/tmp/keepsessions.service [Unit] Description=SiteTools keep sessions Wants=network-online.target Wants=docker.service After=network-online.target After=docker.service [Service] ExecStart=/opt/sitetools/keepsessions ExecStartPost=/opt/sitetools/onstart Restart=always WatchdogSec=5m Type=simple [Install] WantedBy=multi-user.target It does usual stuff, like open/close files, connect to consul, etc. Written in python3, nothing special. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852903 Title: systemd Caught , dumped core To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1852903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854573] Re: Seccomp check skipped for syscall -1 in straced process and PTRACE_SYSEMU broken
** Also affects: linux (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/1854573 Title: Seccomp check skipped for syscall -1 in straced process and PTRACE_SYSEMU broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854573] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1854573 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854573 Title: Seccomp check skipped for syscall -1 in straced process and PTRACE_SYSEMU broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861604] [NEW] [wishlist] Allow switching Ethernet LEDs state
Public bug reported: The official Raspberry Pi kernel allows the user to turn off the Ethernet port LEDs on the Raspberry Pi 4B. (this was added in this pull request: https://github.com/raspberrypi/linux/pull/3316) ** Affects: linux-raspi2-5.3 (Ubuntu) Importance: Undecided Status: New ** Package changed: gnome-media (Ubuntu) => linux-raspi2 (Ubuntu) ** Package changed: linux-raspi2 (Ubuntu) => linux-raspi2-5.3 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861604 Title: [wishlist] Allow switching Ethernet LEDs state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2-5.3/+bug/1861604/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1547971] Re: provide glob2-dbg package
glob2-dbgsym is available. ** Changed in: glob2 (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/1547971 Title: provide glob2-dbg package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glob2/+bug/1547971/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854404] Re: [MIR] libslirp (as it was part of QEMU)
Now showing up in component mismatch due to new qemu, ready for promotion by AA -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854404 Title: [MIR] libslirp (as it was part of QEMU) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libslirp/+bug/1854404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790856] Re: [MIR] pmdk
This seems to auto-inclue way too much: From https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.html Rescued from pmdk (Uploader: ahasenack), libpmemblk-dev, libpmemblk1-debug, libpmemlog-dev, libpmemobj-dev, libpmempool-dev, librpmem-dev, libvmem-dev, libvmmalloc-dev Let us add those to extra-excludes to only pull in libpmem1 itself and libpmem-dev. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790856 Title: [MIR] pmdk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pmdk/+bug/1790856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854404] Re: [MIR] libslirp (as it was part of QEMU)
Subscribed Archive Admins to be aware - correctly linked in https://people.canonical.com/~ubuntu-archive/component-mismatches- proposed.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854404 Title: [MIR] libslirp (as it was part of QEMU) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libslirp/+bug/1854404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848229] Re: [Power9][WSP][DD2.3] cap-ibs=workaround defaults to "full software flush sequence" though "hardware assisted flush" is available
** Changed in: ubuntu-power-systems 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/1848229 Title: [Power9][WSP][DD2.3] cap-ibs=workaround defaults to "full software flush sequence" though "hardware assisted flush" is available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1848229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838048] Re: [chtrt5645 - chtrt5645, playback] Playback problem - Headphone jack inverted status as previously described 1824259 - hack quirk not fixing
I have updated to Ubuntu Studio 19.10 $ uname -a Linux coolflex11 5.3.0-29-generic #31-Ubuntu SMP Fri Jan 17 17:27:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838048 Title: [chtrt5645 - chtrt5645, playback] Playback problem - Headphone jack inverted status as previously described 1824259 - hack quirk not fixing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1838048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838048] Re: [chtrt5645 - chtrt5645, playback] Playback problem - Headphone jack inverted status as previously described 1824259 - hack quirk not fixing
I can NOT change status to CONFIRMED as it is not responding. I have verified that the headphones are still INVERTED status. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838048 Title: [chtrt5645 - chtrt5645, playback] Playback problem - Headphone jack inverted status as previously described 1824259 - hack quirk not fixing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1838048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860315] Re: Default installation should be Local Only
My question remains: what do you get with the current default of Internet Site that is different to No Configuration? For instance, do you automatically get outbound email working out of the box, i.e. if I install it and then fire up mutt and send a message to somebody @gmail.com or at, say @ubuntu.com, will they actually receive it? Or is there more configuration you are expected to put in before it works? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860315 Title: Default installation should be Local Only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1860315/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
I tried it, however, no sound from my subwoofer. During a sound check, just a very faint swoosh can be heared. Nevertheless - nice try! Thank you! regards, HSS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861556] Re: g-ir-scanner doesn't work
** Changed in: gobject-introspection (Debian) 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/1861556 Title: g-ir-scanner doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gobject-introspection/+bug/1861556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861251] Re: 'extended_part_no' referenced before assignment error during install
Here is my probe-data.json file ** Attachment added: "probe-data.json" https://bugs.launchpad.net/curtin/+bug/1861251/+attachment/5324761/+files/probe-data.json -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861251 Title: 'extended_part_no' referenced before assignment error during install To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1861251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861601] Re: Memory leak and incorrect behaviour of generated bindings
** Also affects: sip4 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: sip4 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: sip4 (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861601 Title: Memory leak and incorrect behaviour of generated bindings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sip4/+bug/1861601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861187] Re: bionic/linux-gke-5.0: 5.0.0-1030.31 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1861192 packages: main: linux-gke-5.0 meta: linux-meta-gke-5.0 signed: linux-signed-gke-5.0 phase: Testing phase-changed: Friday, 31. January 2020 12:57 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gke-5.0/gke-kernel: bug 1861186 variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861187 Title: bionic/linux-gke-5.0: 5.0.0-1030.31 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838456] Re: Changelog missing entries
I've looked at this it and I think the difference might be due to the programs focusing on different things when it comes to changelogs. For update-manager you are getting a newer versions of packages already installed. The focus here is on what the changes include, which issues are involved and what you might need to know before installing. Any historical changelog entries are less relevant since they discuss bugs or issues which are already resolved due to the fact that this is already installed on your system. For synaptic, which is a full-fledged package manager it makes more sense to be able to see the complete changelog for packages to see what has changed since the dawn of time, including when it was initially packaged 20 years ago. Sot it looks like this is intentional behaviour, though I've also added synaptic as affected, so we might get a more official confirm or deny. ** Changed in: update-manager (Ubuntu) Status: New => Incomplete ** Also affects: synaptic (Ubuntu) Importance: Undecided Status: New ** Changed in: synaptic (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838456 Title: Changelog missing entries To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1838456/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861608] [NEW] package libgs9-common 9.27~dfsg+0-0ubuntu3.1 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración
Public bug reported: i dont know what happen with this script, but i report that. ProblemType: Package DistroRelease: Ubuntu 19.10 Package: libgs9-common 9.27~dfsg+0-0ubuntu3.1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sat Feb 1 11:39:38 2020 ErrorMessage: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. InstallationDate: Installed on 2020-01-31 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: ghostscript Title: package libgs9-common 9.27~dfsg+0-0ubuntu3.1 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ghostscript (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861608 Title: package libgs9-common 9.27~dfsg+0-0ubuntu3.1 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/1861608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763144] Re: Significantly lower power and thermal limits on ThinkPad T480s (and probably others) than on Windows
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: thermald (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/1763144 Title: Significantly lower power and thermal limits on ThinkPad T480s (and probably others) than on Windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763144] Re: Significantly lower power and thermal limits on ThinkPad T480s (and probably others) than on Windows
I'm affected too (Ubuntu focal, kernel 5.4). I found a simple workaround here using thermald : https://forums.lenovo.com/t5/Other-Linux-Discussions/X1C6-T480s-low-cTDP-and-trip-temperature-in-Linux/m-p/4637873#M14378 helped from here : https://github.com/intel/thermal_daemon/issues/215 It's just a workaround... and I don't really understand how it does make the limits higher, but it's better than nothing. ** Bug watch added: github.com/intel/thermal_daemon/issues #215 https://github.com/intel/thermal_daemon/issues/215 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763144 Title: Significantly lower power and thermal limits on ThinkPad T480s (and probably others) than on Windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1763144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861610] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (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/1861610 Title: 'Elan touchpad' not detected in 'Ubuntu 19.04' on 'Lenovo ThinkBook 15 IIL' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861611] [NEW] hata tespit edildi
Public bug reported: çözümü var mı? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Feb 2 16:54:46 2020 DistUpgraded: 2018-09-17 00:42:01,428 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.34, 4.15.0-74-generic, x86_64: installed virtualbox, 5.2.34, 4.15.0-76-generic, x86_64: installed DpkgLog: GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05ea] InstallationDate: Installed on 2016-04-18 (1385 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=02b4eaff-edeb-4552-88e7-1a11c01edcb0 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-16 (503 days ago) dmi.bios.date: 07/30/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0N7YKW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A11 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd07/30/2018:svnDellInc.:pnInspiron3537:pvrA11:rvnDellInc.:rn0N7YKW:rvrA00:cvnDellInc.:ct8:cvrA11: dmi.product.family: 00 dmi.product.name: Inspiron 3537 dmi.product.version: A11 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Sep 16 22:10:59 2018 xserver.configfile: default xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861611 Title: hata tespit edildi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1861611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861411] Re: systemd unit startup timeout too short
Link to Jira discussion: https://jira.mariadb.org/browse/MDEV-17571 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861411 Title: systemd unit startup timeout too short To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1861411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861599] [NEW] Kdenlive fills memory and swap very quickly. As a result, the system hangs
Public bug reported: Possible problem in ffmpeg ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: kdenlive 4:19.12.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Sun Feb 2 13:13:59 2020 InstallationDate: Installed on 2020-01-28 (4 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200128) ProcEnviron: LANGUAGE=ru TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: kdenlive UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kdenlive (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdenlive in Ubuntu. https://bugs.launchpad.net/bugs/1861599 Title: Kdenlive fills memory and swap very quickly. As a result, the system hangs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdenlive/+bug/1861599/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1861411] Re: systemd unit startup timeout too short
Fix is going to be integrated from upstream in next 10.1.44 release for 18.04. ** Changed in: mariadb-10.1 (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861411 Title: systemd unit startup timeout too short To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1861411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861601] [NEW] Memory leak and incorrect behaviour of generated bindings
Public bug reported: Happening on all release of sip from 4.16.8 until 4.19.20, so Xenial and newer are all affected. I have tested this on both Xenial(sip 4.17) and Bionic(4.19.7). My request is to update all affected releases to 4.19.21. [Impact] Since the release of sip 4.16.8, but especially commit https://www.riverbankcomputing.com/hg/sip/rev/11a92ebd4840, sip contains two bugs. The code being generated doesn't keep the correct references and a memory leak. The reference problem: (generateVariableGetter in sipgen/gencode.c) In the get function of a class member, there isn't a reference kept to the containing class. Therefore if no other references are kept to the containing class, the containing class in cpp is deleted, also if there are still references to the member. This causes also the member in cpp to be deleted, while in python there is still a reference to the member. Which can't be accessed anymore. Fixed in: https://www.riverbankcomputing.com/hg/sip/rev/137b9be794a1 https://www.riverbankcomputing.com/hg/sip/rev/6a057b2d8537 https://www.riverbankcomputing.com/hg/sip/rev/699facc95914 The memory leak problem: (sip_api_get_reference in siplib/siplib.c) A new reference to "key_obj" is obtained from PyLong_FromLong/PyInt_FromLong. but the reference count is not decreased. Therefore "key_obj" stays alive and produces a memory leak. Fixed in: https://www.riverbankcomputing.com/hg/sip/rev/82ec38dc0e63 Both problems are fixed in 4.19.21. Also the entire changelog between 4.19.20 and 4.19.21 is related to fixing only these two problems. The converstation between me and the develop of sip can be read here: http://python.6.x6.nabble.com/sip-Accessing-members-results-in- incorrect-missing-data-td5266521.html, which might provide some more insight. [Test Case] As sip is a library to generate python bindings. So my test case will be an "applied" test case. My test case is focused on the 'python_orocos_kdl', https://github.com/orocos/orocos_kinematics_dynamics, library. For this test case, please use the "test/sip_bug" branch of my fork of the library, https://github.com/MatthijsBurgh/orocos_kinematics_dynamics. To test the reference problem, follow the steps from travis config. (Of course skipping the installation of python-sip-dev if testing with other sip versions.) To test the memory leak, run the following code (After running the steps from the travis config): ``` import PyKDL as kdl F = kdl.Frame( kdl.Rotation.Quaternion(0, 1, 0, 0), kdl.Vector(1, 2, 3)) while True: v = F.p ``` See http://python.6.x6.nabble.com/sip-Accessing-members-results-in-incorrect-missing-data-tp5266521p5267154.html including plot of the memory usage, http://python.6.x6.nabble.com/file/t383425/mem_leak.png. [Regression Potential] Different versions of SIP have been released on multiple distributions. No bugs have been reported of these versions. I have tested multiple versions of SIP in the affected range on both Xenial and Bionic. I didn't experience any bugs other than the two reported here. [Other Info] Already mentioned, but the conversation between me and the developer, http://python.6.x6.nabble.com/sip-Accessing-members-results-in-incorrect-missing-data-td5266521.html. ** Affects: sip4 (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/1861601 Title: Memory leak and incorrect behaviour of generated bindings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sip4/+bug/1861601/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860917] Re: uas_eh_abort_handler uas-tag inflight OUT
** Attachment added: "File contains three scripts to make the bug" https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+attachment/5324759/+files/BUG13.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860917 Title: uas_eh_abort_handler uas-tag inflight OUT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860917] Re: uas_eh_abort_handler uas-tag inflight OUT
Hello. Thank you for your involvement in this problem. My goal is to make ubuntu better. I accidentally encountered this incident in a real context. I knew that changing partition size is risky and impossible with a partition in use. That's why I duplicated it on an external disk. I found that the problem was reproducible. As the partition size was around 300 GiB, this took a long time. I managed to make a 40 GB test game. I was then able to reproduce the incident on 12 partitions. I think I eliminated the material cause by doing the tests - Badblocks with a partition making up the entire disk. - Writing single sectors on approximately 95% of the disk space then re-reading with control of what is read is indeed what is expected. - Impossible to reproduce the incident if using the ext3 format - Impossible to reproduce the incident in the same session. A boot or a disconnection must take place for each incident. - Unable to carry out the incident in version 18.04.03 My diagnosis is that there is a functioning problem in the hard drive application link when the UAS driver is used. I worked as much as possible to reduce the size of the partition so that the execution times were acceptable. Now, I cause the incident systematically with an 8 GB partition. I do not know how to do less despite all the possible tests. I find it important to diagnose the problem to avoid that the future version 20.04 also have this behavior. I don't know if it's in the UAS module, the resize2fs module or maybe the mount module. You will find attached a file containing the mode of realization of the incident with 1) a script making 250 files of 30 Mio. 2) a script formatting the partition and transferring the files then deleting the first files. it seems to me that this is the key element in the making of the incident. 3) A script doing the size reduction. Another file contained resulted from an execution. I was able to do the incidents with the following quantities of files: 250 - 150 250 - 125 200 - 125 176 - 102 I cannot produce the incident with the couple 174-100. This seems to me to be a problem of volumetry that UAS treats badly. I remain available to put the trace options that you will advise me. I am ready to open a new problem with the mount module and the UAS module because there is not the same function as in version 18.04.3 for the management of logical partitions which are not in the same order as the physical structure. The UAS module is now automatically disabled. It's probably better this way. I use google translation to answer you Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860917 Title: uas_eh_abort_handler uas-tag inflight OUT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860917] Re: uas_eh_abort_handler uas-tag inflight OUT
ATTENTION This error is new. and it is because of use of logical device not un good order!!! Feb 02 10:59:19 a systemd[1315]: mnt-USBsdb3.mount: Succeeded. Feb 02 10:59:39 a kernel: blk_update_request: I/O error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Feb 02 10:59:39 a kernel: blk_update_request: I/O error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Feb 02 10:59:39 a kernel: blk_update_request: I/O error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Feb 02 10:59:39 a kernel: blk_update_request: I/O error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 Feb 02 10:59:57 a kernel: usb 4-2: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd ** Attachment added: "Trace of one execution" https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+attachment/5324760/+files/Bug1857914-102-176-8192Mo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860917 Title: uas_eh_abort_handler uas-tag inflight OUT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1860917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811504] Re: scan with Laserjet MFP-M28 fails
Hi all, just wanted to add my experience to this. I'm using hplip 3.19.12 with the plugin installed, on Ubuntu 19.10 with xsane 0.999-7. I can scan at 300 dpi in either color or grey, but setting 200 or 600 dpi, as well as trying to get a preview, fails with a 503. I also tried to add a sleep to the scan.py script and found it works with just 3-5 seconds delay. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811504 Title: scan with Laserjet MFP-M28 fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1811504/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825636] Re: Battery drain during sleep. System suspended before kernel suspends all tasks
Any update on this? I am using Ubuntu 19.10 on my XPS 15 9560 and I am facing this behavior, however, I am not using the signed kernel package, I believe it applies to the mainline as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825636 Title: Battery drain during sleep. System suspended before kernel suspends all tasks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1825636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848229] Re: [Power9][WSP][DD2.3] cap-ibs=workaround defaults to "full software flush sequence" though "hardware assisted flush" is available
This bug was fixed in the package libvirt - 6.0.0-0ubuntu1
---
libvirt (6.0.0-0ubuntu1) focal; urgency=medium
* Merged with Debian 5.6.0-4 from experimental and v6.0.0 from upstream
Among many other new features and fixes this includes fixes for:
- LP: #1859253 - rbd driver fails to create a new volume
- LP: #1858341 - rbd driver does not list all volumes in pool
- LP: #1845506 - Libvirt snapshot doesn't update apparmor profile
- LP: #1854653 - slow libvirt-guests.sh during shutdown if service is off
- LP: #1848229 - enable ppc64el to use ccf-assist feature
- LP: #1853315 - Enable CPU Model Comparison and Baselining on s390x
- LP: #1853317 - CCW IPL support to boot from ECKD DASDs
- LP: #1859506 - security: AppArmor profile fixes for swtpm
Remaining changes:
- Disable libssh2 support (universe dependency)
- Disable firewalld support (universe dependency)
- Set qemu-group to kvm (for compat with older ubuntu)
- Additional apport package-hook
- Autostart default bridged network (As upstream does, but not Debian).
In addition to just enabling it our solution provides:
+ do not autostart if subnet is already taken (e.g. in guests).
+ iterate some alternative subnets before giving up
- d/p/ubuntu/Allow-libvirt-group-to-access-the-socket.patch: This is
the group based access to libvirt functions as it was used in Ubuntu
for quite long.
+ d/p/ubuntu/daemon-augeas-fix-expected.patch fix some related tests
due to the group access change.
+ d/libvirt-daemon-system.postinst: add users in sudo to the libvirt
group.
- ubuntu/parallel-shutdown.patch: set parallel shutdown by default.
- Update Vcs-Git and Vcs-Browser fields to point to launchpad
- Update README.Debian with Ubuntu changes
- Enable some additional features on ppc64el and s390x (for arch parity)
+ systemtap, zfs, numa and numad on s390x.
+ systemtap on ppc64el.
- d/p/ubuntu/ubuntu_machine_type.patch: accept ubuntu types as pci440fx
- Further upstreamed apparmor Delta, especially any new one
Our former delta is split into logical pieces and is either Ubuntu only
or is part of a continuous upstreaming effort.
Listing related remaining changes in debian/patches/ubuntu-aa/:
- fix autopkgtests
+ d/t/control, d/t/smoke-qemu-session: fixup smoke-qemu-session by making
vmlinuz available and accessible (Debian bug 848314)
+ d/t/control: fix smoke-qemu-session by ensuring the service will run
installing libvirt-daemon-system
+ d/t/smoke-lxc: fix smoke-lxc by ignoring potential issues on destroy as
long as the following undefine succeeds
+ d/t/smoke-lxc: use systemd instead of sysV to restart the service
- dnsmasq related enhancements
+ run dnsmasq as libvirt-dnsmasq (LP: 1743718)
+ d/libvirt-daemon-system.postinst: add libvirt-dnsmasq user and group
+ d/libvirt-daemon-system.postrm: remove libvirt-dnsmasq user and group
on purge
+ d/p/ubuntu/dnsmasq-as-priv-user: write dnsmasq config with user
libvirt-dnsmasq and adapt the self tests to expect that config
+ d/libvirt-daemon-system.postinst: fix old libvirt-dnsmasq users group
+ Add dnsmasq configuration to work with system wide dnsmasq-base
- debian/rules: disable the netcf backend. (LP: 1764314)
- debian/patches/ubuntu/ovmf_paths.patch: adjust paths to secboot.fd UEFI
Secure Boot enabled variants of the OVMF firmware and variable store for
the paths where we ship these files in Ubuntu.
- d/rules: install virtlockd correctly with defaults file (LP: 1729516)
- d/rules: also check build time self test results on all architectures
- d/p/ubuntu/set-default-machine-to-ubuntu.patch: to select default
machine type correctly with newer qemu/libvirt
- d/rules: add --no-restart-after-upgrade to services that are supposed to
stay up through upgrades - this also applies to related sockets.
- Apparmor Delta that is Ubuntu specific or yet to be upstreamed
split into logical pieces. File names in debian/patches/ubuntu-aa/:
+ 0003-apparmor-libvirt-qemu-Allow-read-access-to-overcommi.patch:
apparmor, libvirt-qemu: Allow read access to overcommit_memory
+ 0007-apparmor-libvirt-qemu-Allow-owner-read-access-to-PRO.patch:
apparmor, libvirt-qemu: Allow owner read access to @{PROC}/*/auxv
+ 0017-apparmor-virt-aa-helper-Allow-access-to-tmp-director.patch:
apparmor, virt-aa-helper: Allow access to tmp directories
+ 0020-virt-aa-helper-ubuntu-storage-paths.patch:
apparmor, virt-aa-helper: Allow various storage pools and image
locations
+ 0021-apparmor-virt-aa-helper-Add-openvswitch-support.patch:
apparmor, virt-aa-helper: Add openvswitch support
+ 0029-appmor-libvirt-qemu-Add-9p-support.patch: appmor,
[Bug 1859506] Re: swtmp fails in focal with apparor
This bug was fixed in the package libvirt - 6.0.0-0ubuntu1
---
libvirt (6.0.0-0ubuntu1) focal; urgency=medium
* Merged with Debian 5.6.0-4 from experimental and v6.0.0 from upstream
Among many other new features and fixes this includes fixes for:
- LP: #1859253 - rbd driver fails to create a new volume
- LP: #1858341 - rbd driver does not list all volumes in pool
- LP: #1845506 - Libvirt snapshot doesn't update apparmor profile
- LP: #1854653 - slow libvirt-guests.sh during shutdown if service is off
- LP: #1848229 - enable ppc64el to use ccf-assist feature
- LP: #1853315 - Enable CPU Model Comparison and Baselining on s390x
- LP: #1853317 - CCW IPL support to boot from ECKD DASDs
- LP: #1859506 - security: AppArmor profile fixes for swtpm
Remaining changes:
- Disable libssh2 support (universe dependency)
- Disable firewalld support (universe dependency)
- Set qemu-group to kvm (for compat with older ubuntu)
- Additional apport package-hook
- Autostart default bridged network (As upstream does, but not Debian).
In addition to just enabling it our solution provides:
+ do not autostart if subnet is already taken (e.g. in guests).
+ iterate some alternative subnets before giving up
- d/p/ubuntu/Allow-libvirt-group-to-access-the-socket.patch: This is
the group based access to libvirt functions as it was used in Ubuntu
for quite long.
+ d/p/ubuntu/daemon-augeas-fix-expected.patch fix some related tests
due to the group access change.
+ d/libvirt-daemon-system.postinst: add users in sudo to the libvirt
group.
- ubuntu/parallel-shutdown.patch: set parallel shutdown by default.
- Update Vcs-Git and Vcs-Browser fields to point to launchpad
- Update README.Debian with Ubuntu changes
- Enable some additional features on ppc64el and s390x (for arch parity)
+ systemtap, zfs, numa and numad on s390x.
+ systemtap on ppc64el.
- d/p/ubuntu/ubuntu_machine_type.patch: accept ubuntu types as pci440fx
- Further upstreamed apparmor Delta, especially any new one
Our former delta is split into logical pieces and is either Ubuntu only
or is part of a continuous upstreaming effort.
Listing related remaining changes in debian/patches/ubuntu-aa/:
- fix autopkgtests
+ d/t/control, d/t/smoke-qemu-session: fixup smoke-qemu-session by making
vmlinuz available and accessible (Debian bug 848314)
+ d/t/control: fix smoke-qemu-session by ensuring the service will run
installing libvirt-daemon-system
+ d/t/smoke-lxc: fix smoke-lxc by ignoring potential issues on destroy as
long as the following undefine succeeds
+ d/t/smoke-lxc: use systemd instead of sysV to restart the service
- dnsmasq related enhancements
+ run dnsmasq as libvirt-dnsmasq (LP: 1743718)
+ d/libvirt-daemon-system.postinst: add libvirt-dnsmasq user and group
+ d/libvirt-daemon-system.postrm: remove libvirt-dnsmasq user and group
on purge
+ d/p/ubuntu/dnsmasq-as-priv-user: write dnsmasq config with user
libvirt-dnsmasq and adapt the self tests to expect that config
+ d/libvirt-daemon-system.postinst: fix old libvirt-dnsmasq users group
+ Add dnsmasq configuration to work with system wide dnsmasq-base
- debian/rules: disable the netcf backend. (LP: 1764314)
- debian/patches/ubuntu/ovmf_paths.patch: adjust paths to secboot.fd UEFI
Secure Boot enabled variants of the OVMF firmware and variable store for
the paths where we ship these files in Ubuntu.
- d/rules: install virtlockd correctly with defaults file (LP: 1729516)
- d/rules: also check build time self test results on all architectures
- d/p/ubuntu/set-default-machine-to-ubuntu.patch: to select default
machine type correctly with newer qemu/libvirt
- d/rules: add --no-restart-after-upgrade to services that are supposed to
stay up through upgrades - this also applies to related sockets.
- Apparmor Delta that is Ubuntu specific or yet to be upstreamed
split into logical pieces. File names in debian/patches/ubuntu-aa/:
+ 0003-apparmor-libvirt-qemu-Allow-read-access-to-overcommi.patch:
apparmor, libvirt-qemu: Allow read access to overcommit_memory
+ 0007-apparmor-libvirt-qemu-Allow-owner-read-access-to-PRO.patch:
apparmor, libvirt-qemu: Allow owner read access to @{PROC}/*/auxv
+ 0017-apparmor-virt-aa-helper-Allow-access-to-tmp-director.patch:
apparmor, virt-aa-helper: Allow access to tmp directories
+ 0020-virt-aa-helper-ubuntu-storage-paths.patch:
apparmor, virt-aa-helper: Allow various storage pools and image
locations
+ 0021-apparmor-virt-aa-helper-Add-openvswitch-support.patch:
apparmor, virt-aa-helper: Add openvswitch support
+ 0029-appmor-libvirt-qemu-Add-9p-support.patch: appmor,
[Bug 1744507] Re: *** Error in `stubby': double free or corruption (!prev): 0x0000561985221410 ***
** Changed in: getdns Status: Unknown => 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/1744507 Title: *** Error in `stubby': double free or corruption (!prev): 0x561985221410 *** To manage notifications about this bug go to: https://bugs.launchpad.net/getdns/+bug/1744507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860592] Re: Test t/06190 hangs on arm64
** Changed in: gscan2pdf (Debian) 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/1860592 Title: Test t/06190 hangs on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/1860592/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861345] Re: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1
Sorry, I don't understand the difference between Kernels. I have the Ubuntu Kernel 5.5.1 installed from Ubuntu. Not the official Kernel from Kernel.org. I downgraded to the official kernel that works with 18.04 LTS that is installed by default for filling out this bug report. I am still uncertain with Ubuntu because have not been using it long as I have occasionally stopped using it because of hardware limitations with newer hardware. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861345 Title: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1861345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861345] Re: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1
So the mainline kernel from Kernel.org is not tested. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861345 Title: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1861345/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 635406] Re: armel build failure (no thumb support)
** Changed in: moon (Ubuntu) Assignee: Jo Shields (directhex) => bos (bosmutus) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/635406 Title: armel build failure (no thumb support) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgc/+bug/635406/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861628] [NEW] I'm next to computer illiterate
Public bug reported: I guess i thought most of this would happen automatically, but am eager and willing to aid the ubuntu community in what ever ways don't require money or sexual favors. i just ran the debug thingy-muh-doodle to see what would happen cause i kept getting system-d shim error readings while upgrading from 16.04. Don't know if that helps but hope it tells you something useful. Also, i really like the beaver theme wallpaper and how slick everything has gotten. Linux4Life ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Feb 2 09:26:49 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:21de] InstallationDate: Installed on 2019-12-31 (32 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: HP HP 15 Notebook PC ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=68bdfa38-e528-4538-b4fe-0ec3bc7d0b1d ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.35 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 233F dmi.board.vendor: Hewlett-Packard dmi.board.version: 06.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.35:bd04/25/2017:svnHP:pnHP15NotebookPC:pvrType1-ProductConfigId:rvnHewlett-Packard:rn233F:rvr06.27:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP 15 Notebook PC dmi.product.version: Type1 - ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Feb 1 23:51:20 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1634 vendor BOE xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861628 Title: I'm next to computer illiterate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1861628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1753267] Re: "Create new Document" Right click missing in Ubuntu 17.10
*** This bug is a duplicate of bug 1632027 *** https://bugs.launchpad.net/bugs/1632027 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (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/1753267 Title: "Create new Document" Right click missing in Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1753267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1313914] Re: Rhythmbox zeitgeist plugin doesn't activate when selected in Rhythmbox plugin preferences
** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/issues #1304 https://gitlab.gnome.org/GNOME/rhythmbox/issues/1304 ** Changed in: rhythmbox Status: Fix Released => Unknown ** Changed in: rhythmbox Remote watch: Debian Bug tracker #728532 => gitlab.gnome.org/GNOME/rhythmbox/issues #1304 ** Also affects: rhythmbox (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728532 Importance: Unknown Status: Unknown ** Changed in: rhythmbox (Ubuntu) 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/1313914 Title: Rhythmbox zeitgeist plugin doesn't activate when selected in Rhythmbox plugin preferences To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/1313914/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852364] Re: iwlwifi: Microcode SW error detected
*** This bug is a duplicate of bug 1848921 *** https://bugs.launchpad.net/bugs/1848921 Same here. Ubuntu 19.10 with 5.3.0-26-generic kernel. [90731.026595] iwlwifi :04:00.0: Microcode SW error detected. Restarting 0x0. [90731.026982] iwlwifi :04:00.0: Start IWL Error Log Dump: [90731.026984] iwlwifi :04:00.0: Status: 0x0080, count: 6 [90731.026986] iwlwifi :04:00.0: Loaded firmware version: 46.6bf1df06.0 [90731.026988] iwlwifi :04:00.0: 0x22CE | ADVANCED_SYSASSERT [90731.026989] iwlwifi :04:00.0: 0x0590A2F3 | trm_hw_status0 [90731.026991] iwlwifi :04:00.0: 0x | trm_hw_status1 [90731.026992] iwlwifi :04:00.0: 0x0048853E | branchlink2 [90731.026993] iwlwifi :04:00.0: 0x00479392 | interruptlink1 [90731.026994] iwlwifi :04:00.0: 0x | interruptlink2 [90731.026996] iwlwifi :04:00.0: 0x012C | data1 [90731.026997] iwlwifi :04:00.0: 0x | data2 [90731.026998] iwlwifi :04:00.0: 0x0400 | data3 [90731.027000] iwlwifi :04:00.0: 0x0FC189F2 | beacon time [90731.027001] iwlwifi :04:00.0: 0x2AFC5614 | tsf low [90731.027002] iwlwifi :04:00.0: 0x0100 | tsf hi [90731.027003] iwlwifi :04:00.0: 0x | time gp1 [90731.027005] iwlwifi :04:00.0: 0x13217A21 | time gp2 [90731.027006] iwlwifi :04:00.0: 0x0001 | uCode revision type [90731.027007] iwlwifi :04:00.0: 0x002E | uCode version major [90731.027009] iwlwifi :04:00.0: 0x6BF1DF06 | uCode version minor [90731.027010] iwlwifi :04:00.0: 0x0321 | hw version [90731.027011] iwlwifi :04:00.0: 0x00C89004 | board version [90731.027012] iwlwifi :04:00.0: 0x0B5C001C | hcmd [90731.027014] iwlwifi :04:00.0: 0x27F93882 | isr0 [90731.027015] iwlwifi :04:00.0: 0x00044000 | isr1 [90731.027016] iwlwifi :04:00.0: 0x10081802 | isr2 [90731.027017] iwlwifi :04:00.0: 0x4041FDC1 | isr3 [90731.027019] iwlwifi :04:00.0: 0x | isr4 [90731.027020] iwlwifi :04:00.0: 0x0B5B001C | last cmd Id [90731.027021] iwlwifi :04:00.0: 0x0001ACA2 | wait_event [90731.027023] iwlwifi :04:00.0: 0x4288 | l2p_control [90731.027024] iwlwifi :04:00.0: 0x1C20 | l2p_duration [90731.027025] iwlwifi :04:00.0: 0x03BF | l2p_mhvalid [90731.027026] iwlwifi :04:00.0: 0x00E7 | l2p_addr_match [90731.027028] iwlwifi :04:00.0: 0x000D | lmpm_pmg_sel [90731.027029] iwlwifi :04:00.0: 0x08081424 | timestamp [90731.027030] iwlwifi :04:00.0: 0x13683838 | flow_handler [90731.027176] iwlwifi :04:00.0: Start IWL Error Log Dump: [90731.027178] iwlwifi :04:00.0: Status: 0x0080, count: 7 [90731.027179] iwlwifi :04:00.0: 0x2070 | NMI_INTERRUPT_LMAC_FATAL [90731.027180] iwlwifi :04:00.0: 0x | umac branchlink1 [90731.027182] iwlwifi :04:00.0: 0xC00E | umac branchlink2 [90731.027183] iwlwifi :04:00.0: 0xC0084414 | umac interruptlink1 [90731.027184] iwlwifi :04:00.0: 0xC0084414 | umac interruptlink2 [90731.027185] iwlwifi :04:00.0: 0x0800 | umac data1 [90731.027187] iwlwifi :04:00.0: 0xC0084414 | umac data2 [90731.027188] iwlwifi :04:00.0: 0xDEADBEEF | umac data3 [90731.027189] iwlwifi :04:00.0: 0x002E | umac major [90731.027190] iwlwifi :04:00.0: 0x6BF1DF06 | umac minor [90731.027192] iwlwifi :04:00.0: 0x13217BDE | frame pointer [90731.027193] iwlwifi :04:00.0: 0xC088627C | stack pointer [90731.027194] iwlwifi :04:00.0: 0x0058010C | last host cmd [90731.027196] iwlwifi :04:00.0: 0x | isr status reg [90731.027224] iwlwifi :04:00.0: Fseq Registers: [90731.027236] iwlwifi :04:00.0: 0xE6DDAFAF | FSEQ_ERROR_CODE [90731.027249] iwlwifi :04:00.0: 0x | FSEQ_TOP_INIT_VERSION [90731.027261] iwlwifi :04:00.0: 0x550F7912 | FSEQ_CNVIO_INIT_VERSION [90731.027273] iwlwifi :04:00.0: 0xA371 | FSEQ_OTP_VERSION [90731.027285] iwlwifi :04:00.0: 0x419848ED | FSEQ_TOP_CONTENT_VERSION [90731.027297] iwlwifi :04:00.0: 0xD98868FC | FSEQ_ALIVE_TOKEN [90731.027309] iwlwifi :04:00.0: 0xD384C635 | FSEQ_CNVI_ID [90731.027320] iwlwifi :04:00.0: 0x86D9FFB7 | FSEQ_CNVR_ID [90731.027332] iwlwifi :04:00.0: 0x01000200 | CNVI_AUX_MISC_CHIP [90731.027347] iwlwifi :04:00.0: 0x01300202 | CNVR_AUX_MISC_CHIP [90731.027361] iwlwifi :04:00.0: 0x485B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM [90731.027425] iwlwifi :04:00.0: 0x0BADCAFE | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR [90731.027438] iwlwifi :04:00.0: Collecting data: trigger 2 fired. [90731.027443] ieee80211 phy0: Hardware restart was requested [90731.027487] iwlwifi :04:00.0: FW error in SYNC CMD SCAN_CFG_CMD [90731.027491] CPU: 4 PID: 7423 Comm: kworker/4:1 Tainted: P OEL 5.3.0-26-generic #28-Ubuntu [90731.027506] Workqueue: events iwl_mvm_tcm_work [iwlmvm] [90731.027507] Call Trace: [90731.027512] dump_stack+0x6d/0x9a [90731.027524] iwl_pcie_send_hcmd_sync+0x497/0x4b0 [iwlwifi] [90731.027527]
[Bug 1861616] [NEW] Please remove from focal archive
Public bug reported: Please removed from focal archive, binaries and source. Requires wxwidgets3.0 gtk2 to build and depends on the gtk2 binaries, that no longer exists in wxwidgets3.0 in -proposed https://tracker.debian.org/news/1075374/accepted-wxwidgets30-304dfsg-15 -source-into-unstable/ pcsx2 was therefore removed from debian testing in update_output_notest.txt it can be seen that pcsx2 will block a reasonably large transition if left in focal for now. https://paste.ubuntu.com/p/NVB7nHpKrR/ ** Affects: pcsx2 (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/1861616 Title: Please remove from focal archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsx2/+bug/1861616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861615] Re: package libldap-2.4-2:amd64 2.4.45+dfsg-1ubuntu1.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861615 Title: package libldap-2.4-2:amd64 2.4.45+dfsg-1ubuntu1.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1861615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861627] [NEW] ubuntu install crashed when installing grub boot loader.
Public bug reported: attempting to setup ubuntu with encrypted LVM. tried again after erasing disk. is my install media corrupt? will verify it and try again. Install worked before on this laptop ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.12 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 2 13:28:04 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.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.12 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861627 Title: ubuntu install crashed when installing grub boot loader. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1861627/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1856896] Re: Only check the vendor ID if the device has one set
** No longer affects: fwupd (Ubuntu Xenial) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1856896 Title: Only check the vendor ID if the device has one set To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1856896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861084] Re: new qemu triggers illegal instruction on boot on ppc64el
** Changed in: ubuntu-power-systems Status: In Progress => 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/1861084 Title: new qemu triggers illegal instruction on boot on ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1861084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861615] [NEW] package libldap-2.4-2:amd64 2.4.45+dfsg-1ubuntu1.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: didnt work ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libldap-2.4-2:amd64 2.4.45+dfsg-1ubuntu1.4 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_29_31_generic_42 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Feb 2 08:12:58 2020 DuplicateSignature: package:libldap-2.4-2:amd64:2.4.45+dfsg-1ubuntu1.4 Setting up libkf5notifications-data (5.44.0-0ubuntu1) ... dpkg: error processing package libldap-2.4-2:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-02-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.3 SourcePackage: openldap Title: package libldap-2.4-2:amd64 2.4.45+dfsg-1ubuntu1.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openldap (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861615 Title: package libldap-2.4-2:amd64 2.4.45+dfsg-1ubuntu1.4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1861615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861609] Re: login impossible from GUI on fresh Ubuntu 20.04 install
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/1861609/+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/1861609 Title: login impossible from GUI on fresh Ubuntu 20.04 install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1861609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831215] Re: tkvars man page missing
Thanks for reporting and help making Ubuntu better. It looks like tk8.5-doc (previous version) contained such a man page (http://manpages.ubuntu.com/cgi-bin/search.py?q=tkvars), but for some reason it is missing from tk8.6-doc. ** Changed in: tk8.6 (Ubuntu) Status: New => Confirmed ** Tags added: bionic eoan focal manpage packaging -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831215 Title: tkvars man page missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tk8.6/+bug/1831215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858092] Re: Network Manager not saving OpenVPN password
Tested with network-manager 1.20.4-2ubuntu2.2 from proposed on eoan. Result: VPN passwords are saved correctly again! Thank you so much! I built a vpn benchmark script that relies on the password being able to be saved. It uses the nmcli tool to add new connections and set the password. It can now run again. ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858092 Title: Network Manager not saving OpenVPN password To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1858092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580451] Re: mutter does not remember position of extra displays
I am not reproducing this bug on latest stable mutter. mutter: Installed: 3.34.3-1ubuntu1 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E] (rev 87) I'm running a 6-head system on focal-devel, with gnome-shell/mutter and a radeon card. I do have troubles getting all the monitors working properly, and invariably am having to rejigger the positions of the extra screens. However, merely powering the monitor on and off does not trigger this behavior, at least not for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580451 Title: mutter does not remember position of extra displays To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1580451/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861626] [NEW] Touchpad not detected
Public bug reported: The touchpad of my Lenovo laptop stopped working suddenly possibly after an update. Apparently it seems that the touchpad isn't even recognised by the operating system yet external mouse works perfectly fine. I tried updating the kernel but it didn't fix the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-28-generic 5.3.0-28.30~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Feb 2 23:52:07 2020 InstallationDate: Installed on 2018-09-19 (501 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1861626 Title: Touchpad not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1861626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861084] Re: new qemu triggers illegal instruction on boot on ppc64el
My changes are in Debian now and synced to Focal ** Changed in: slof (Ubuntu) Status: In Progress => 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/1861084 Title: new qemu triggers illegal instruction on boot on ppc64el To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1861084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790856] Re: [MIR] pmdk
@Andreas - take a look at these and ack+push if you are ok with that: => https://code.launchpad.net/~paelzer/ubuntu-seeds/+git/ubuntu/+merge/378435 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790856 Title: [MIR] pmdk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pmdk/+bug/1790856/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853506] Re: [MIR] ndctl
\o/ glad you found this! @andreas: While I was at PMDK adding one more was easy, MP suggestion for the seed change: https://code.launchpad.net/~paelzer/ubuntu-seeds/+git/platform/+merge/378436 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853506 Title: [MIR] ndctl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ndctl/+bug/1853506/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861655] Re: [Ubu 20.04][kernel-5.4.0-12-generic][WSP-DD2.3] Unable to install Ubu 20.4 on NVMe disk
** Also affects: ubuntu-power-systems Importance: Undecided Status: New ** Changed in: ubuntu-power-systems Importance: Undecided => High ** Changed in: ubuntu-power-systems Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861655 Title: [Ubu 20.04][kernel-5.4.0-12-generic][WSP-DD2.3] Unable to install Ubu 20.4 on NVMe disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1861655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820768] Re: [SRU] support new cab and new docking firmware upgrade in fwupd 1.2.10
per test 1.2.10-1ubuntu2~ubuntu18.04.3, it fix the regression mentioned in #60. Will to saninty check for other test cases very soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820768 Title: [SRU] support new cab and new docking firmware upgrade in fwupd 1.2.10 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1820768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861137] Re: bionic/linux-oem: 4.15.0-1068.78 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1861165 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem - phase: Ready for Packaging - phase-changed: Saturday, 01. February 2020 01:17 UTC + phase: Packaging + phase-changed: Monday, 03. February 2020 07:31 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-lrm: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded variant: debs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861137 Title: bionic/linux-oem: 4.15.0-1068.78 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861556] Re: g-ir-scanner doesn't work
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gobject-introspection (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/1861556 Title: g-ir-scanner doesn't work (so can't build gnome packages any more) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gobject-introspection/+bug/1861556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861655] [NEW] [Ubu 20.04][kernel-5.4.0-12-generic][WSP-DD2.3] Unable to install Ubu 20.4 on NVMe disk
Public bug reported: [Ubu 20.04][kernel-5.4.0-12-generic][WSP-DD2.3] Unable to install Ubu 20.4 on NVMe disk Contact Information = kalsh...@in.ibm.com, navee...@in.ibm.com, nasas...@in.ibm.com ---uname output--- [Ubu 20.04][kernel-5.4.0-12-generic] Machine Type = Witherspoon DD2.3 Test Environment: * Hardware: Witherspoon-DD2.3 * Ubuntu 20.04 * kernel: 5.4.0-12-generic #15-Ubuntu Steps: 1. Kick start Ubu 20.4 on Witherspoon-DD2.3 baremetal 2. Select NVMe disk for installation, at the end of the install seen Grub boot loader issue ??? Select and install software ??? ? ? ?? [!!] Install the GRUB boot loader on a hard disk ?? ? ? ? ? Unable to install GRUB in /dev/nvme0n1p1 ? ? ? ? Executing 'grub-install /dev/nvme0n1p1' failed.? ? ? ?? ? ? Running "? This is a fatal error. ? ? ? ?? ? ? ? ?? ?? ? [!!] Install the GRUB boot loader on a hard disk ?? ? ? ? Installation step failed ? ? An installation step failed. You can try to run the failing item ? ? again from the menu, or skip it and choose something else. The? ? failing step is: Install the GRUB boot loader on a hard disk ? ? ? ? ? ? ? ? moves; selects; activates buttons Complete install screenshot attached... grub-install doesn't seem to install the bootloader on the nvme device. -- Logs below - Jan 31 16:01:51 in-target: Installing for powerpc-ieee1275 platform.^M Jan 31 16:01:52 in-target: grub-install: error: unknown filesystem.^M Jan 31 16:01:52 in-target: Failed: grub-install --target=powerpc-ieee1275 /dev/sda1 ^M Jan 31 16:01:52 in-target: WARNING: Bootloader is not properly installed, system may not be bootable^M .. .. Jan 31 16:01:57 40grub2: debug: parsing: fi Jan 31 16:01:57 40grub2: debug: parsing: ### END /etc/grub.d/41_custom ### Jan 31 16:01:57 50mounted-tests: debug: /usr/lib/linux-boot-probes/mounted/40grub2 succeeded Jan 31 16:01:57 linux-boot-prober: debug: linux detected by /usr/lib/linux-boot-probes/50mounted-tests Jan 31 16:01:57 grub-installer: info: Installing grub on '/dev/nvme0n1p1' Jan 31 16:01:57 grub-installer: info: grub-install does not support --no-floppy Jan 31 16:01:57 grub-installer: info: Running chroot /target grub-install --force "/dev/nvme0n1p1" Jan 31 16:01:57 grub-installer: Installing for powerpc-ieee1275 platform. Jan 31 16:01:58 grub-installer: grub-install: error: unknown filesystem. Jan 31 16:01:58 grub-installer: error: Running 'grub-install --force "/dev/nvme0n1p1"' failed. ** Affects: ubuntu-power-systems Importance: High Assignee: Canonical Foundations Team (canonical-foundations) Status: New ** Affects: grub-installer (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-183542 severity-critical targetmilestone-inin2004 ** Tags added: architecture-ppc64le bugnameltc-183542 severity-critical targetmilestone-inin2004 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861655 Title: [Ubu 20.04][kernel-5.4.0-12-generic][WSP-DD2.3] Unable to install Ubu 20.4 on NVMe disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1861655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861655] correct install screenshot
Default Comment by Bridge ** Attachment added: "correct install screenshot" https://bugs.launchpad.net/bugs/1861655/+attachment/5324936/+files/bz183542_Ubu2004_install_fail_correct_log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861655 Title: [Ubu 20.04][kernel-5.4.0-12-generic][WSP-DD2.3] Unable to install Ubu 20.4 on NVMe disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1861655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861655] hw summary
Default Comment by Bridge ** Attachment added: "hw summary" https://bugs.launchpad.net/bugs/1861655/+attachment/5324937/+files/hardware-summary.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861655 Title: [Ubu 20.04][kernel-5.4.0-12-generic][WSP-DD2.3] Unable to install Ubu 20.4 on NVMe disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1861655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861655] syslog
Default Comment by Bridge ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/1861655/+attachment/5324938/+files/syslog.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861655 Title: [Ubu 20.04][kernel-5.4.0-12-generic][WSP-DD2.3] Unable to install Ubu 20.4 on NVMe disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1861655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861655] partman
Default Comment by Bridge ** Attachment added: "partman" https://bugs.launchpad.net/bugs/1861655/+attachment/5324939/+files/partman.gz ** Changed in: ubuntu Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Package changed: ubuntu => grub-installer (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861655 Title: [Ubu 20.04][kernel-5.4.0-12-generic][WSP-DD2.3] Unable to install Ubu 20.4 on NVMe disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1861655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861655] install console sceeenshot
Default Comment by Bridge ** Attachment added: "install console sceeenshot" https://bugs.launchpad.net/bugs/1861655/+attachment/5324935/+files/bz183542_Ubu2004_install_fail_console -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861655 Title: [Ubu 20.04][kernel-5.4.0-12-generic][WSP-DD2.3] Unable to install Ubu 20.4 on NVMe disk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1861655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861216] Re: Dummy Output for audio output device after upgrade to focal
*** This bug is a duplicate of bug 1860697 *** https://bugs.launchpad.net/bugs/1860697 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (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/1861216 Title: Dummy Output for audio output device after upgrade to focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1861216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1707212] Re: The package doesn't set up a lua-interpreter alternative and thus doesn't seamlessly provide lua cli
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lua5.3 (Ubuntu Xenial) 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/1707212 Title: The package doesn't set up a lua-interpreter alternative and thus doesn't seamlessly provide lua cli To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lua5.3/+bug/1707212/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861610] Re: 'Elan touchpad' not detected in 'Ubuntu 19.04' on 'Lenovo ThinkBook 15 IIL'
The output of your first command is attached with this comment (sys-bus- i2c-devices.txt) The output of your second command is: ```bash ghosthawkone@EchelonV:~$ ls /sys/bus/acpi/devices ACPI0003:00 device:0e device:20 device:32 device:44 device:56 device:68 device:7a device:8cINT3403:01 LNXCPU:09LNXSYBUS:00 PNP0C0A:00 ACPI000C:00 device:0f device:21 device:33 device:45 device:57 device:69 device:7b device:8dINT3403:02 LNXCPU:0aLNXSYBUS:01 PNP0C0C:00 ACPI000E:00 device:10 device:22 device:34 device:46 device:58 device:6a device:7c device:8eINT3403:03 LNXCPU:0bLNXSYSTM:00 PNP0C0D:00 CRQ0340:00 device:11 device:23 device:35 device:47 device:59 device:6b device:7d device:8fINT340E:00 LNXCPU:0cLNXVIDEO:00 PNP0C0E:00 device:00device:12 device:24 device:36 device:48 device:5a device:6c device:7e device:90INT3455:00 LNXCPU:0dMSFT0001:00 PNP0C14:00 device:01device:13 device:25 device:37 device:49 device:5b device:6d device:7f device:91INT3519:00 LNXCPU:0eMSFT0003:00 PNP0C14:01 device:02device:14 device:26 device:38 device:4a device:5c device:6e device:80 device:92INT3F0D:00 LNXCPU:0fPNP:00 PNP0C14:02 device:03device:15 device:27 device:39 device:4b device:5d device:6f device:81 device:93INTC5000:00 LNXPOWER:00 PNP0100:00 PNP0C14:03 device:04device:16 device:28 device:3a device:4c device:5e device:70 device:82 device:94LIC0001:00 LNXPOWER:01 PNP0103:00 PNP0C14:04 device:05device:17 device:29 device:3b device:4d device:5f device:71 device:83 device:95LNXCPU:00LNXPOWER:02 PNP0A08:00 PNP0C14:05 device:06device:18 device:2a device:3c device:4e device:60 device:72 device:84 device:96LNXCPU:01LNXPOWER:03 PNP0B00:00 PRP1:00 device:07device:19 device:2b device:3d device:4f device:61 device:73 device:85 device:97LNXCPU:02LNXPOWER:04 PNP0C02:00 SYNA2B60:00 device:08device:1a device:2c device:3e device:50 device:62 device:74 device:86 ELAN0634:00 LNXCPU:03LNXPOWER:05 PNP0C02:01 USBC000:00 device:09device:1b device:2d device:3f device:51 device:63 device:75 device:87 INT0E0C:00 LNXCPU:04LNXPOWER:06 PNP0C02:02 VPC2004:00 device:0adevice:1c device:2e device:40 device:52 device:64 device:76 device:88 INT3394:00 LNXCPU:05LNXPOWER:07 PNP0C02:03 YMC2017:00 device:0bdevice:1d device:2f device:41 device:53 device:65 device:77 device:89 INT33A1:00 LNXCPU:06LNXPOWER:08 PNP0C02:04 device:0cdevice:1e device:30 device:42 device:54 device:66 device:78 device:8a INT3400:00 LNXCPU:07LNXPOWER:09 PNP0C04:00 device:0ddevice:1f device:31 device:43 device:55 device:67 device:79 device:8b INT3403:00 LNXCPU:08LNXPWRBN:00 PNP0C09:00 ghosthawkone@EchelonV:~$ ls /sys/bus/acpi/devices > sys-bus-acpi-devices.txt ``` ** Attachment added: "sys-bus-i2c-devices.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+attachment/5324940/+files/sys-bus-i2c-devices.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861610 Title: 'Elan touchpad' not detected in 'Ubuntu 19.04' on 'Lenovo ThinkBook 15 IIL' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]
On a similar Asus netbook (with an Intel Atom x5-Z8300) I find that Ubuntu 19.10 boots perfectly from USB. Oddly, 20.04 does not. With 20.04 I experience a blank screen more like this bug. To get around it I just avoided the live session. At the 20.04 boot menu, choose 'Install Ubuntu (safe graphics)'. Then it installs and boots successfully (http://cdimage.ubuntu.com/daily-live/20200124/). So I have the feeling this is close to being fixed in some future live session of 20.04. I wouldn't worry about 19.10 for too long because it will reach end-of-life in July (https://wiki.ubuntu.com/Releases). I suggest the next step in this bug is for you to follow comment #10 and try 20.04 for yourself. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860754 Title: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860754/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861137] Re: bionic/linux-oem: 4.15.0-1068.78 -proposed tracker
** Summary changed: - bionic/linux-oem: -proposed tracker + bionic/linux-oem: 4.15.0-1068.78 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => AceLan Kao (acelankao) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => AceLan Kao (acelankao) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => AceLan Kao (acelankao) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => AceLan Kao (acelankao) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861137 Title: bionic/linux-oem: 4.15.0-1068.78 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861340] Re: All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development)
The status is just a mapping launchpad does from the gitlab closed state, if you look carrefully you will notice that the Ubuntu line is set as 'triaged'. I'm not sure we want to stay on an older serie for the LTS only to workaround that issue though... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861340 Title: All bitmap fonts no longer visible after upgrade 19.10 -> Focal (development) To manage notifications about this bug go to: https://bugs.launchpad.net/pango/+bug/1861340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861556] Re: g-ir-scanner doesn't work
** Tags added: champagne regression ** Changed in: gobject-introspection (Ubuntu) Importance: Undecided => High ** Summary changed: - g-ir-scanner doesn't work + g-ir-scanner doesn't work (so can't build gnome packages any more) ** Changed in: gobject-introspection (Ubuntu) Importance: High => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861556 Title: g-ir-scanner doesn't work (so can't build gnome packages any more) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gobject-introspection/+bug/1861556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814611] Re: turning off "Send error reports to Canonical" prevents using ubuntu-bug
So, um, this has been broken since Bionic and still not fixed, despite the fact that ubuntu-bug is the only supported way for reporting bugs? This seems highly sub-optimal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814611 Title: turning off "Send error reports to Canonical" prevents using ubuntu- bug To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1814611/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 712829] Re: Evolution - Message sort order by time incorrect
https://help.gnome.org/users/evolution/stable/mail-sorting-message- list.html.en Shortcut - CTRL T -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/712829 Title: Evolution - Message sort order by time incorrect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/712829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861631] Re: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information."
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: appstream (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/1861631 Title: "The AppStream system cache was updated, but some components were ignored. Refer to the verbose log for more information." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1861631/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
