[Bug 1831899] Re: Kernel Oops 3b in libc-2.23 unable to handle pointer dereference in kernel virtual address space
Thx Robert, worked now. Downloaded and transferred them to Canonical server 'mombin', folder ~fheimes/1831899 ** Changed in: ubuntu-z-systems Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831899 Title: Kernel Oops 3b in libc-2.23 unable to handle pointer dereference in kernel virtual address space To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1831899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832295] [NEW] lighttpd broken by OpenSSL update
Public bug reported: After installing today's bionic OpenSSL update (1.1.0g-2ubuntu4.3 -> 1.1.1-1ubuntu2.1~18.04.1 and associated libraries) SSL is broken in lighttpd 1.4.45-1ubuntu3. The logs are full of messages of the form: 2019-06-11 12:02:20: (connections-glue.c.126) SSL: renegotiation initiated by client, killing connection Perhaps problem with TLS v1.3 negotiation? (And the version of lighttpd is too old to have the ssl.openssl.ssl-conf-cmd directive to try to disable it.) Description:Ubuntu 18.04.2 LTS Release:18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lighttpd 1.4.45-1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18 Uname: Linux 4.15.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 Date: Tue Jun 11 14:18:55 2019 SourcePackage: lighttpd UpgradeStatus: Upgraded to bionic on 2018-06-10 (365 days ago) modified.conffile..etc.lighttpd.conf-available.10-cgi.conf: [modified] modified.conffile..etc.lighttpd.lighttpd.conf: [modified] mtime.conffile..etc.lighttpd.conf-available.10-cgi.conf: 2015-07-16T10:18:19.857892 mtime.conffile..etc.lighttpd.lighttpd.conf: 2019-06-11T12:01:59.493213 ** Affects: lighttpd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832295 Title: lighttpd broken by OpenSSL update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lighttpd/+bug/1832295/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820130] Re: [SRU] modem-manager-gui fails to start after modemmanager is upgraded to 1.10.0-1
Jan, no the Disco package needs to be tested on Disco. If you don't have access to another computer, a live CD, or virtual machine with USB pass-through could work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820130 Title: [SRU] modem-manager-gui fails to start after modemmanager is upgraded to 1.10.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modem-manager-gui/+bug/1820130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820323] Re: amdgpu-pro xorg crash
** Changed in: xorg-server (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820323 Title: amdgpu-pro xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1820323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1445970] Re: In the driver manager of Kubuntu: It looks like pressing "OK" was the same as pressing "Cancel".
The problem still exist in 19.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1445970 Title: In the driver manager of Kubuntu: It looks like pressing "OK" was the same as pressing "Cancel". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-driver-manager/+bug/1445970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772512] Re: Unable to install i386 and amd64 arch at the same time
use another method to install, it's there -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772512 Title: Unable to install i386 and amd64 arch at the same time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1772512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1740894] Re: KEY_RFKILL is not passed to userspace
** Tags removed: verification-failed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740894 Title: KEY_RFKILL is not passed to userspace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832292] [NEW] reboot reboots system when -h is passed
Public bug reported: -h is a fairly common shortcut for --help. reboot, however, reboots the machine when one issues the command: reboot -h Now looking at the man page, there is an entry for --halt and --help, but NOTHING for -h at all. reboot should return the same as --help when -h is passed, or at the very least it should error out and not reboot the system, instead perhaps dumping a message like "-h unknown argument". ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu10.21 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Jun 11 00:50:22 2019 InstallationDate: Installed on 2016-02-11 (1215 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832292 Title: reboot reboots system when -h is passed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1832292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832110] Re: Resource Sharing with multiple sshd services
Robbie, If I upload the sshd.c proposed change, will that be possibility? I have diffed the sshd.c code against the OpenSSH 7.6p1 source. Ubuntu has made significant and substantial changes to all of the OpenSSH source. So I know Ubuntu does not use the original OpenSSH code verbatim. Is there anyway to change your mind from "Won't Fix" to "Investigating"? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832110 Title: Resource Sharing with multiple sshd services To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1832110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832074] Re: base-files '/etc/update-motd.d/50-motd-news' reports system use to Ubuntu
Thank you for your interest in improving the default experience in Ubuntu. We do understand that not everyone wants their machines to be talking to the Ubuntu servers, which is why there are several ways to disable this functionality. - on a per-machine basis, you can set ENABLED=0. - on a site-wide basis, you can firewall motd.ubuntu.com. There is a factual inaccuracy in your report, which is to say that this feature can be used to track login activity on machines. The update- motd script in question contains the following check: # If we're not forcing an update, and we have a cached motd-news file, # then just print it and exit as quickly as possible, for login performance. # Note that systemd should keep this cache file up to date, asynchronously if [ "$FORCED" != "1" ]; then if [ -r $CACHE ]; then echo safe_print $CACHE else : > $CACHE fi exit 0 fi Thus, aside from a possible execution at first login, systems will only contact motd.ubuntu.com twice per day with no correlation with user logins. It is also the case that Ubuntu systems already talk to Ubuntu servers daily by default, as apt will check twice daily for updates from archive.ubuntu.com and security.ubuntu.com, so the behavior of this update-motd script in base-files is consistent with the existing experience. Finally, you've raised the concern that this script exposes information about the system that could be used to exploit said system. Canonical takes the security of Ubuntu users very seriously. This is why, by default, security updates are applied to all Ubuntu systems daily in 18.04. This is why we offer a kernel livepatch service that enables users of Ubuntu 18.04 to fix high and critical kernel vulnerabilities outside of scheduled maintenance windows. If motd.ubuntu.com were ever to leak information to an attacker about what machines on the Internet were vulnerable to a particular attack, the root problem there would not be that information was shared with motd.ubuntu.com; the root problem would be that Ubuntu machines connected to the Internet had not had necessary security updates applied to them. Because on the Internet at large, attackers do not wait for a service like motd.ubuntu.com to tell them which machines are vulnerable before exploiting them. On the other hand, motd.ubuntu.com is a very important source of information for US about what versions of Ubuntu are in use in the wild - information that can be used, among other things, to identify problems with the rollout of kernel security updates to our users. So while it's understandable that some users will not want this behavior, I believe that it is defensible as default behavior in Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832074 Title: base-files '/etc/update-motd.d/50-motd-news' reports system use to Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1832074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832074] Re: base-files '/etc/update-motd.d/50-motd-news' reports system use to Ubuntu
This bug report touches on a number of issues, which are variously 'invalid', 'wontfix', or 'opinion'. Since the bug title appears to refer to the (incorrect) claim that the update-motd script will expose information to the server about when users are logging in to the system, I am closing as invalid. ** Changed in: base-files (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/1832074 Title: base-files '/etc/update-motd.d/50-motd-news' reports system use to Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1832074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818985] Re: segfault in libmysqlclient when reconnecting using QMYSQL
[Expired for mysql-5.7 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mysql-5.7 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818985 Title: segfault in libmysqlclient when reconnecting using QMYSQL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1818985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824330] Re: crashed when tried to do gedit textname
[Expired for gedit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gedit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824330 Title: crashed when tried to do gedit textname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1824330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820323] Re: amdgpu-pro xorg crash
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820323 Title: amdgpu-pro xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1820323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824385] Re: Drain battery on lenovo ideapad 100 15ibd intel i5 4288u
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824385 Title: Drain battery on lenovo ideapad 100 15ibd intel i5 4288u To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824230] Re: Download not resumed for base snap when using "snap install --dangerous"
[Expired for snapd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: snapd (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824230 Title: Download not resumed for base snap when using "snap install --dangerous" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1824230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832290] [NEW] Raspberry Pi 3 B+: Load average always reported as 4.0 even when idle
Public bug reported: $ uptime 12:40:44 up 1 day, 10:56, 1 user, load average: 4.00, 4.02, 4.00 The load is always reported as higher than 4 even on an idle system. Seems to be this upstream: https://github.com/raspberrypi/linux/issues/2881 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1009-raspi2 5.0.0-1009.9 ProcVersionSignature: Ubuntu 5.0.0-1009.9-raspi2 5.0.8 Uname: Linux 5.0.0-1009-raspi2 aarch64 ApportVersion: 2.20.10-0ubuntu27 Architecture: arm64 Date: Tue Jun 11 12:33:57 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-raspi2 UpgradeStatus: Upgraded to disco on 2019-05-22 (19 days ago) ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832290 Title: Raspberry Pi 3 B+: Load average always reported as 4.0 even when idle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1832290/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806031] Re: ubuntu_quota_smoke_test failed
With bug 1803334 fixed, this issue can no longer be reproduced. Marking this as fix released. ** Changed in: linux-azure-edge (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-azure-edge (Ubuntu Bionic) Status: Confirmed => Fix Released ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: ubuntu-kernel-tests Status: Confirmed => Fix Released ** Summary changed: - ubuntu_quota_smoke_test failed + ubuntu_quota_smoke_test failed on Azure-edge / GKE -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806031 Title: ubuntu_quota_smoke_test failed on Azure-edge / GKE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1806031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830533] Re: not able to set grub
Please specify which Ideapad 320 model -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830533 Title: not able to set grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1830533/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832282] Re: Lenovo Ideapad 320-15IAP unable to install on UEFI - Grub install crashes
** Summary changed: - Lenovo Ideapad 320 unable to install on UEFI - Grub install crashes + Lenovo Ideapad 320-15IAP unable to install on UEFI - Grub install crashes -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832282 Title: Lenovo Ideapad 320-15IAP unable to install on UEFI - Grub install crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1832282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811981] Re: test_410_config_lock_down_kernel in ubuntu_kernel_security test failed on B/C/D KVM
** Changed in: linux-kvm (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux-kvm (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Changed in: linux-kvm (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811981 Title: test_410_config_lock_down_kernel in ubuntu_kernel_security test failed on B/C/D KVM To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1811981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803334] Re: linux-modules-extra-azure-edge should point to 4.18 package
** Tags added: amd64 azure ** Changed in: ubuntu-kernel-tests Status: Confirmed => Fix Released ** Changed in: linux-azure-edge (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803334 Title: linux-modules-extra-azure-edge should point to 4.18 package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1803334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
Process follows directly from previous comment. - Updated to network-manager 1.10.14-0ubuntu2 (from bionic-proposed) - Rebooted and ran dig twice to mirror previous test, never resolved to expected result. :( - Log file from reboot until after the second dig attached. Ran dig a few more times over a couple of minutes, but never resolved successfully. ** Attachment added: "nm-1.10.14.log" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+attachment/5270070/+files/nm-1.10.14.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829566 Title: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
Can only attach one file at a time, so this and the next comment are heavily linked. - Updated to systemd 237-3ubuntu10.22 (from bionic-updates) - Enabled debug logging for network manager and disabled flood protection on journald. - Rebooted and successfully ran dig (second attempt) - First run did not return expected IP. - Second run onwards resolved as expected. - Log file from reboot until after the second dig attached. ** Attachment added: "nm-1.10.6.log" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+attachment/5270066/+files/nm-1.10.6.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829566 Title: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806031] Re: ubuntu_quota_smoke_test failed
** Tags added: ubuntu-quota-smoke-test -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806031 Title: ubuntu_quota_smoke_test failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1806031/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793960] Re: Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog
Does anyone know which kernel DOES have this fix so I can upgrade ? This is an annoyance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793960 Title: Lenovo Ideapad 320-15IAP trackpad spams kernel errors in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
WORKING
This is a comment summarising a bit the statement of work in this bug:
Bellow are the commits (and the merge requests they came from) that I
could identify by the previous comments. Judging by the selected
commits, the intent is to allow MSR supportability to be queried by
guest through CPUID MSR query emulation <-> kvm ioctls interface.
Every feature to be reported has to have its MSR declared for the CPU
type to be used AND the kvm ioctl backend + kernel support (to query
the actual hardware).
(1)
Request is to allow the following features to be reported by QEMU/KVM:
CPUID.(EAX=7H,ECX=0):EDX[26] (Enable/Disable IBRS/IBPB feature flag):
Enumerates support for indirect branch restricted speculation
(IBRS) and the indirect branch predictor barrier (IBPB).
Processors that set this bit support the IA32_SPEC_CTRL MSR and
the IA32_PRED_CMD MSR. They allow software to set
IA32_SPEC_CTRL[0] (IBRS) and IA32_PRED_CMD[0] (IBPB).
and
CPUID.(EAX=7H,ECX=0):EDX[29] (IA32_ARCH_CAPABILITIES feature flag)
Enumerates support for the IA32_ARCH_CAPABILITIES MSR, allowing
MSR index 10AH to be read:
- (bit 0) RDCL_NO: not susceptible to rogue data cache
- (bit 1) IBRS_ALL: processor supports IBRS
- (bit 2) RSBA: processor supports RSB alternate (retpol off)
- (bit 3) SKIP_L1DFL_VMENTRY: vm entry don't flush L1D on VM entry
- (bit 4) SSB_NO: processor not susceptible to spec store bypass
(2)
There is *no current request* to allow following features to be
reported by EAX_7H_ECX_0_EDX QEMU/KVM right now:
* CPUID.(EAX=7H,ECX=0):EDX[27] STIBP support flag.
* CPUID.(EAX=7H,ECX=0):EDX[28] L1D_FLUSH support flag.
* CPUID.(EAX=7H,ECX=0):EDX[31] SSBD support flag.
OBS: I haven't checked patch dependencies yet, not sure if more
patches are needed yet, just realized that SSBD support flag wasn't
being asked to be backported (nor present in 2.11 version, Bionic
version which we are targetting this to). That explains the small
"statement of work" above.
For now the request was fully understood: I'll work tomorrow in a
backport attempt to check if big pieces in between 2.11 and something
around the v3.0.0-152-g8c80c99fcc .. v4.0.0-rc0-2-g014018e19b range
are missing that would require a major refactoring that would not be
possible to be done.
(3)
Possible points of pain:
- arch_capabilities unmigratable flag inside cpu data structure
(while CPUID was being developed) turned later on into migratable
later.
- data structure changes to support MSR based features.
QEMU:
MERGE REQUEST
21ee4787e53367590f284915bf4c30c684e65bdf
174a78a8a5c0cf421236fe14efc5559717f050df
bb4928c7cafe50ab2137a0034e350ef1bfa044d9
014018e19b3c54dd1bf5072bc912ceffea40abe8 +
485b1d256bcb0874bcde0223727c159b6837e6f8 +
commit 014018e19b3c54dd1bf5072bc912ceffea40abe8 - v4.0.0-rc0-2-g014018e19b
Author: Eduardo Habkost
Date: Fri Jan 25 20:06:06 2019
i386: Make arch_capabilities migratable
Now that kvm_arch_get_supported_cpuid() will only return
arch_capabilities if QEMU is able to initialize the MSR properly,
we know that the feature is safely migratable.
Signed-off-by: Eduardo Habkost
Message-Id: <20190125220606.4864-3-ehabk...@redhat.com>
Signed-off-by: Eduardo Habkost
commit 485b1d256bcb0874bcde0223727c159b6837e6f8 - v4.0.0-rc0-1-g485b1d256b
Author: Eduardo Habkost
Date: Fri Jan 25 20:06:05 2019
i386: kvm: Disable arch_capabilities if MSR can't be set
KVM has two bugs in the handling of MSR_IA32_ARCH_CAPABILITIES:
1) Linux commit commit 1eaafe91a0df ("kvm: x86:
IA32_ARCH_CAPABILITIES is always supported") makes
GET_SUPPORTED_CPUID return arch_capabilities even if running on
SVM. This makes "-cpu host,migratable=off" incorrectly expose
arch_capabilities on CPUID on AMD hosts (where the MSR is not
emulated by KVM).
2) KVM_GET_MSR_INDEX_LIST does not return
MSR_IA32_ARCH_CAPABILITIES if the MSR is not supported by the
host CPU. This makes QEMU not initialize the MSR properly at
kvm_put_msrs() on those hosts.
Work around both bugs on the QEMU side, by checking if the MSR
was returned by KVM_GET_MSR_INDEX_LIST before returning the
feature flag on kvm_arch_get_supported_cpuid().
This has the unfortunate side effect of making arch_capabilities
unavailable on hosts without hardware support for the MSR until
bug #2 is fixed on KVM, but I can't see another way to work
around bug #1 without that side effect.
Signed-off-by: Eduardo Habkost
Message-Id: <20190125220606.4864-2-ehabk...@redhat.com>
Signed-off-by: Eduardo Habkost
possibly just one:
commit b0a1980384fc265d91de7e09aa5fe531a69e6288 - v3.1.0-1228-gb0a1980384
Author: Tao Xu
Date: Thu Dec 27 00:43:03 2018
i386: Update stepping of Cascadelake-Server
Update the stepping from 5 to 6, in order that
the Cascadelake-Server CPU model can support AVX512VNNI
and MSR based
[Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
Sorry, last comment was posted 3 timex due to bad wrapping and mix of chars because of that. Fixed now, I've hidden 2 broken comments. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828495 Title: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM. To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1828495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
WORKING
This is a comment summarising a bit the statement of work in this bug:
Bellow are the commits (and the merge requests they came from) that I
could identify by the previous comments. Judging by the selected
commits, the intent is to allow MSR supportability to be queried by
guest through CPUID MSR query emulation <-> kvm ioctls interface.
Every feature to be reported has to have its MSR declared for the CPU
type to be used AND the kvm ioctl backend + kernel support (to query
the actual hardware).
(1)
Request is to allow the following features to be reported by QEMU/KVM:
CPUID.(EAX=7H,ECX=0):EDX[26] (Enable/Disable IBRS/IBPB feature flag):
Enumerates support for indirect branch restricted speculation
(IBRS) and the indirect branch predictor barrier (IBPB).
Processors that set this bit support the IA32_SPEC_CTRL MSR and
the IA32_PRED_CMD MSR. They allow software to set
IA32_SPEC_CTRL[0] (IBRS) and IA32_PRED_CMD[0] (IBPB).
and
CPUID.(EAX=7H,ECX=0):EDX[29] (IA32_ARCH_CAPABILITIES feature flag)
Enumerates support for the IA32_ARCH_CAPABILITIES MSR, allowing
MSR index 10AH to be read:
- (bit 0) RDCL_NO: not susceptible to rogue data cache bit 1)
- (IBRS_ALL: processor supports IBRS bit 2) RSBA: processor
- (supports RSB alternate (if retpoline off) bit 3)
- (SKIP_L1DFL_VMENTRY: vm entry don't need to flush L1D on VM
- (entry bit 4) SSB_NO: processor not susceptible to spec store
- (bypass
(2)
There is *no current request* to allow following features to be
reported by EAX_7H_ECX_0_EDX QEMU/KVM right now:
* CPUID.(EAX=7H,ECX=0):EDX[27] STIBP support flag.
* CPUID.(EAX=7H,ECX=0):EDX[28] L1D_FLUSH support flag.
* CPUID.(EAX=7H,ECX=0):EDX[31] SSBD support flag.
OBS: I haven't checked patch dependencies yet, not sure if more
patches are needed yet, just realized that SSBD support flag wasn't
being asked to be backported (nor present in 2.11 version, Bionic
version which we are targetting this to). That explains the small
"statement of work" above.
For now the request was fully understood: I'll work tomorrow in a
backport attempt to check if big pieces in between 2.11 and something
around the v3.0.0-152-g8c80c99fcc .. v4.0.0-rc0-2-g014018e19b range
are missing that would require a major refactoring that would not be
possible to be done.
(3)
Possible points of pain:
- arch_capabilities unmigratable flag inside cpu data structure
(while CPUID was being developed) turned later on into migratable
later.
- data structure changes to support MSR based features.
QEMU:
MERGE REQUEST
21ee4787e53367590f284915bf4c30c684e65bdf
174a78a8a5c0cf421236fe14efc5559717f050df
bb4928c7cafe50ab2137a0034e350ef1bfa044d9
014018e19b3c54dd1bf5072bc912ceffea40abe8 +
485b1d256bcb0874bcde0223727c159b6837e6f8 +
commit 014018e19b3c54dd1bf5072bc912ceffea40abe8 (v4.0.0-rc0-2-g014018e19b)
Author: Eduardo Habkost
Date: Fri Jan 25 20:06:06 2019
i386: Make arch_capabilities migratable
Now that kvm_arch_get_supported_cpuid() will only return
arch_capabilities if QEMU is able to initialize the MSR properly,
we know that the feature is safely migratable.
Signed-off-by: Eduardo Habkost
Message-Id: <20190125220606.4864-3-ehabk...@redhat.com>
Signed-off-by: Eduardo Habkost
commit 485b1d256bcb0874bcde0223727c159b6837e6f8 (v4.0.0-rc0-1-g485b1d256b)
Author: Eduardo Habkost
Date: Fri Jan 25 20:06:05 2019
i386: kvm: Disable arch_capabilities if MSR can't be set
KVM has two bugs in the handling of MSR_IA32_ARCH_CAPABILITIES:
1) Linux commit commit 1eaafe91a0df ("kvm: x86: IA32_ARCH_CAPABILITIES
is always supported") makes GET_SUPPORTED_CPUID return
arch_capabilities even if running on SVM. This makes "-cpu
host,migratable=off" incorrectly expose arch_capabilities on CPUID on
AMD hosts (where the MSR is not emulated by KVM).
2) KVM_GET_MSR_INDEX_LIST does not return MSR_IA32_ARCH_CAPABILITIES if
the MSR is not supported by the host CPU. This makes QEMU not
initialize the MSR properly at kvm_put_msrs() on those hosts.
Work around both bugs on the QEMU side, by checking if the MSR
was returned by KVM_GET_MSR_INDEX_LIST before returning the
feature flag on kvm_arch_get_supported_cpuid().
This has the unfortunate side effect of making arch_capabilities
unavailable on hosts without hardware support for the MSR until bug #2
is fixed on KVM, but I can't see another way to work around bug #1
without that side effect.
Signed-off-by: Eduardo Habkost
Message-Id: <20190125220606.4864-2-ehabk...@redhat.com>
Signed-off-by: Eduardo Habkost
possibly just one:
commit b0a1980384fc265d91de7e09aa5fe531a69e6288 (v3.1.0-1228-gb0a1980384)
Author: Tao Xu
Date: Thu Dec 27 00:43:03 2018
i386: Update stepping of Cascadelake-Server
Update the stepping from 5 to 6, in order that
the Cascadelake-Server CPU model can support
[Bug 1832184] Re: nvidia-kernel-source-390 390.116-0ubuntu0.18.10.1: nvidia kernel module failed to build
during RTL pass: cprop /var/lib/dkms/nvidia/390.116/build/nvidia-uvm/uvm8_page_tree_test.c: In function ‘alloc_64k_memory_kepler’: /var/lib/dkms/nvidia/390.116/build/nvidia-uvm/uvm8_page_tree_test.c:1112:1: internal compiler error: Naruszenie ochrony pamięci } ^ Please submit a full bug report, with preprocessed source if appropriate. See for instructions. ** Package changed: nvidia-graphics-drivers-390 (Ubuntu) => gcc-8 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832184 Title: nvidia-kernel-source-390 390.116-0ubuntu0.18.10.1: nvidia kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-8/+bug/1832184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
This is a comment summarising a bit the statement of work in this bug:
Bellow are the commits (and the merge requests they came from) that I could
identify by the previous comments. Judging by the selected commits, the intent
is to allow MSR supportability to be queried by guest through CPUID MSR query
emulation <-> kvm ioctls interface. Every feature to be reported has to have
its MSR declared for the CPU type to be used AND the kvm ioctl backend +
kernel support (to query the actual hardware).
(1)
Request is to allow the following features to be reported by QEMU/KVM:
CPUID.(EAX=7H,ECX=0):EDX[26] (Enable/Disable IBRS/IBPB feature flag):
Enumerates support for indirect branch restricted speculation (IBRS) and
the indirect branch predictor barrier (IBPB). Processors that set this bit
support the IA32_SPEC_CTRL MSR and the IA32_PRED_CMD MSR. They allow
software to set IA32_SPEC_CTRL[0] (IBRS) and IA32_PRED_CMD[0] (IBPB).
and
CPUID.(EAX=7H,ECX=0):EDX[29] (IA32_ARCH_CAPABILITIES feature flag)
Enumerates support for the IA32_ARCH_CAPABILITIES MSR, allowing MSR index
10AH to be read:
- (bit 0) RDCL_NO: not susceptible to rogue data cache
- (bit 1) IBRS_ALL: processor supports IBRS
- (bit 2) RSBA: processor supports RSB alternate (if retpoline off)
- (bit 3) SKIP_L1DFL_VMENTRY: vm entry don't need to flush L1D on VM entry
- (bit 4) SSB_NO: processor not susceptible to spec store bypass
(2)
There is *no current request* to allow following features to be reported by
EAX_7H_ECX_0_EDX QEMU/KVM right now:
* CPUID.(EAX=7H,ECX=0):EDX[27] STIBP support flag.
* CPUID.(EAX=7H,ECX=0):EDX[28] L1D_FLUSH support flag.
* CPUID.(EAX=7H,ECX=0):EDX[31] SSBD support flag.
OBS: I haven't checked patch dependencies yet, not sure if more patches are
needed yet, just realized that SSBD support flag wasn't being asked to be
backported (nor present in 2.11 version, Bionic version which we are
targeting this to). That explains the small "statement of work" above.
For now the request was fully understood: I'll work tomorrow in a backport
attempt to check if big pieces in between 2.11 and something around the
v3.0.0-152-g8c80c99fcc..v4.0.0-rc0-2-g014018e19b range are missing that would
require a major refactoring that would not be possible to be done.
(3)
Possible points of pain:
- arch_capabilities non migratable flag inside cpu data structure
(while CPUID was being developed) turned later on into migratable
later.
- data structure changes to support MSR based features.
QEMU:
MERGE REQUEST
21ee4787e53367590f284915bf4c30c684e65bdf
174a78a8a5c0cf421236fe14efc5559717f050df
bb4928c7cafe50ab2137a0034e350ef1bfa044d9
014018e19b3c54dd1bf5072bc912ceffea40abe8 +
485b1d256bcb0874bcde0223727c159b6837e6f8 +
commit 014018e19b3c54dd1bf5072bc912ceffea40abe8 (v4.0.0-rc0-2-g014018e19b)
Author: Eduardo Habkost
Date: Fri Jan 25 20:06:06 2019
i386: Make arch_capabilities migratable
Now that kvm_arch_get_supported_cpuid() will only return
arch_capabilities if QEMU is able to initialize the MSR properly,
we know that the feature is safely migratable.
Signed-off-by: Eduardo Habkost
Message-Id: <20190125220606.4864-3-ehabk...@redhat.com>
Signed-off-by: Eduardo Habkost
commit 485b1d256bcb0874bcde0223727c159b6837e6f8 (v4.0.0-rc0-1-g485b1d256b)
Author: Eduardo Habkost
Date: Fri Jan 25 20:06:05 2019
i386: kvm: Disable arch_capabilities if MSR can't be set
KVM has two bugs in the handling of MSR_IA32_ARCH_CAPABILITIES:
1) Linux commit commit 1eaafe91a0df ("kvm: x86: IA32_ARCH_CAPABILITIES
is always supported") makes GET_SUPPORTED_CPUID return
arch_capabilities even if running on SVM. This makes "-cpu
host,migratable=off" incorrectly expose arch_capabilities on CPUID on
AMD hosts (where the MSR is not emulated by KVM).
2) KVM_GET_MSR_INDEX_LIST does not return MSR_IA32_ARCH_CAPABILITIES if
the MSR is not supported by the host CPU. This makes QEMU not
initialize the MSR properly at kvm_put_msrs() on those hosts.
Work around both bugs on the QEMU side, by checking if the MSR
was returned by KVM_GET_MSR_INDEX_LIST before returning the
feature flag on kvm_arch_get_supported_cpuid().
This has the unfortunate side effect of making arch_capabilities
unavailable on hosts without hardware support for the MSR until bug #2
is fixed on KVM, but I can't see another way to work around bug #1
without that side effect.
Signed-off-by: Eduardo Habkost
Message-Id: <20190125220606.4864-2-ehabk...@redhat.com>
Signed-off-by: Eduardo Habkost
possibly just one:
commit b0a1980384fc265d91de7e09aa5fe531a69e6288 (v3.1.0-1228-gb0a1980384)
Author: Tao Xu
Date: Thu Dec 27 00:43:03 2018
i386: Update stepping of Cascadelake-Server
Update the stepping from 5 to 6, in order that
the Cascadelake-Server CPU model can support AVX512VNNI
and MSR
[Bug 1832133] Re: Mouse unresponsive on Ubuntu 18.04
Please reproduce the problem again and then immediately run this command in a Terminal window: dmesg > dmesg.txt That will create a new file called 'dmesg.txt'. We would like you to then attach that new file to this bug in a new comment. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832133 Title: Mouse unresponsive on Ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832268] Re: Low performance when I play a game
Thanks for the bug report. It does sound strange that pressing Escape improves performance. I wonder if that's a quirk of the game itself. Does pressing Escape work only in one specific game or multiple games? ** Tags added: nvidia ** Summary changed: - Low performance when I play a game + [nvidia] Low performance when I play a game ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Changed in: mutter (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/1832268 Title: [nvidia] Low performance when I play a game To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1832268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831037] Re: Acer Aspire ES1-311 - some keyboard keys like D do not respond correctly.
Thanks. If you could describe the keyboard problem in more detail then it would help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831037 Title: Acer Aspire ES1-311 - some keyboard keys like D do not respond correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769384] Re: SDDM does not unlock gnome-keyring on login
Can confirm that SDDM has trouble unlocking the default keyring. While it always seems to unlock it after a cold boot, at some point trouble arises when logging out and back in again, along with after resuming from suspend / hibernate. In those situations, the keyring remains locked far more often than not. I am experiencing this under Lubuntu 19.04. The issue has been occurring both before and after I migrated data over from an install of Ubuntu Xenial. I have not made changes to sddm configs, as the other user who filed this bug has. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769384 Title: SDDM does not unlock gnome-keyring on login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1769384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824855] Re: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..."
What model machine are you seeing this bug on? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824855 Title: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1824855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 508522] Re: Mic is not available with A2DP Bluetooth profile
Duplicate bug 1828393 suggests Bluetooth theoretically allows for two profiles to be enabled simultaneously. That would resolve this, but I don't know if it's true. If it is true then any fix would require modifying PulseAudio and the GUI in gnome-control-center. Maybe it's not really simultaneous. Maybe it's just smarter automatic switching. There is an upstream bug for that already: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/81 ** Bug watch added: PulseAudio #81 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/81 ** Also affects: pulseaudio via https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/81 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/508522 Title: Mic is not available with A2DP Bluetooth profile To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/508522/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769384] Re: SDDM does not unlock gnome-keyring on login
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: sddm (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/1769384 Title: SDDM does not unlock gnome-keyring on login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1769384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821457] Re: wrapper-2.0 crashed with SIGSEGV in magazine_chain_pop_head()
** Tags added: eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821457 Title: wrapper-2.0 crashed with SIGSEGV in magazine_chain_pop_head() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1821457/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832284] Re: wrapper-2.0 crashed with SIGSEGV
*** This bug is a duplicate of bug 1821457 *** https://bugs.launchpad.net/bugs/1821457 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1821457, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1832284/+attachment/5270038/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1832284/+attachment/5270040/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1832284/+attachment/5270043/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1832284/+attachment/5270044/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1832284/+attachment/5270045/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1832284/+attachment/5270046/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1832284/+attachment/5270047/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1821457 wrapper-2.0 crashed with SIGSEGV in magazine_chain_pop_head() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832284 Title: wrapper-2.0 crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1832284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824216] Re: Linux 5.0 black screen on boot, display flickers (i915 regression with certain laptop panels)
Asus vivobook s15 s530uf has the same new BIOS 304 released, You need to test it before posting here https://www.asus.com/za/Laptops/ASUS-VivoBook-S15-S530UF/HelpDesk_BIOS/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824216 Title: Linux 5.0 black screen on boot, display flickers (i915 regression with certain laptop panels) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824216] Re: Linux 5.0 black screen on boot, display flickers (i915 regression with certain laptop panels)
can't even install Ubuntu 19.04 on Asus vivobook s15 s530uf. Black screen, even the installer USB stops blinking. But I can install it using the `safe graphics` option. But when I reboot it gets stuck at the black screen. Frustrated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824216 Title: Linux 5.0 black screen on boot, display flickers (i915 regression with certain laptop panels) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832120] Re: i386 - Test fails 'test_get_file_package_uninstalled_multiarch'
This bug was fixed in the package apport - 2.20.11-0ubuntu3 --- apport (2.20.11-0ubuntu3) eoan; urgency=medium * test/test_backend_apt_dpkg.py: Now that there are per architecture cache files we need to make all of them outdated rather than just the first one. (LP: #1832120) -- Brian Murray Mon, 10 Jun 2019 16:02:32 -0700 ** Changed in: apport (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/1832120 Title: i386 - Test fails 'test_get_file_package_uninstalled_multiarch' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1832120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832283] [NEW] /usr/bin/gnome-software:double free or corruption (out)
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-software. This problem was most recently seen with package version 3.30.6-2ubuntu4, the problem page at https://errors.ubuntu.com/problem/90c2b072fcbf913fd3cd8d6314f822fa198163c2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: bionic cosmic disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832283 Title: /usr/bin/gnome-software:double free or corruption (out) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1832283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800196] Re: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
Hi all, We have found a workaround, for the display not usable. I give it here for people like me who were stuck... with dell. Since I cannot comment my post #24, here a summary: Step to reproduce: Plug HDMI cable 4k ready, of course connected to 4k screen. Actual result: Purpul screen (default color of my background) on both screen... To have any things displayed I need to use CTRL + ALT + F1. Using "Screen Mode" key (i.e. F8) we were able to have display properly set. Hope this helps... BR Eric. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800196 Title: spice-vdagent[1345]: Cannot access vdagent virtio channel /dev/virtio- ports/com.redhat.spice.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice-vdagent/+bug/1800196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816468] Fix merged to cinder (stable/rocky)
Reviewed: https://review.opendev.org/664262 Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=00cfd67d00885c32a9618734a102d7f5f9f26b39 Submitter: Zuul Branch:stable/rocky commit 00cfd67d00885c32a9618734a102d7f5f9f26b39 Author: Michal Arbet Date: Wed Feb 6 16:11:28 2019 +0100 Fix python3 compatibility of rbd get_fsid In python3 librados's get_fsid() function is represented as binary. Because of this, conditional where fsid is compared with fsid parsed from glance's direct url is not true, then cinder-glance acceleration is not working. This patch is fixing this. More informations are in closing bug. Closes-Bug: #1816468 Change-Id: I69d0685ec845355329f771f27f8894d9e988ae35 (cherry picked from commit ed84f34562da21a53b6d45611a5bcf9e3edd1e84) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816468 Title: Acceleration cinder - glance with ceph not working To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1816468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816468] Re: Acceleration cinder - glance with ceph not working
Reviewed: https://review.opendev.org/663607 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=e8b6b0bc78ec229803d1d27f8a4706e2c425bd77 Submitter: Zuul Branch:master commit e8b6b0bc78ec229803d1d27f8a4706e2c425bd77 Author: Edward Hope-Morley Date: Thu Jun 6 12:26:26 2019 +0100 Fix python3 compatibility of rbd get_fsid In py3 librados's get_fsid() function returns a binary string which breaks comparison when compared with the same value as a string. This is currently breakin the logic that compares ceph cluster fsids when deciding whether the image used to boot an instance is cow-clonable. Change-Id: I79b40ca40400c67b0805926096317afd875ffabb Closes-Bug: #1816468 ** Changed in: nova Status: In Progress => Fix Released ** Changed in: cloud-archive/rocky Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816468 Title: Acceleration cinder - glance with ceph not working To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1816468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832282] [NEW] Lenovo Ideapad 320 unable to install on UEFI - Grub install crashes
Public bug reported: This particular laptop has issues installing Grub in UEFI. For Ubuntu and many others Limux distro . Ultimately I have worked on this error and always get an input/output error in efibootmgr. So i am not sure if this still counts as a Grub issue or if it is ultimately solely an efibootmgr issue. Whether I install to sda or sda1 I get the same issue.. by the way, the error in efibootmgr is unable to register the boot entry input/output error. I am certain the issue is not related to space. To test it I tried to install bootloader to an sda1 partition with 8000MB of space. Is there someplace on the motherboard perhaps that needs to be wiped clean somehow? I do not know. I hope all of this info helps ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ubiquity 19.04.9 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CasperVersion: 1.405 Date: Mon Jun 10 20:11:42 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubiquity-19.04.9 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832282 Title: Lenovo Ideapad 320 unable to install on UEFI - Grub install crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1832282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832257] Re: regression: sudo returns exit code 0 if child is killed with SIGTERM
awesome, thanks so much -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832257 Title: regression: sudo returns exit code 0 if child is killed with SIGTERM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1832257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1168915] Re: Visit Homepage link is non-functional
In Mint Mate 19.1, problem still exists. "Visit Homepage" links *are* colored and underlined, but when you click on them you get error box "Profile Missing Your Firefox profile cannot be loaded. It may be missing or inaccessible." If your firefox is already running before you run synaptic, then the problem doesn't occur. That is a workaround but not a fix. Apparently the problem is what Mark says above (running firefox as wrong user) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1168915 Title: Visit Homepage link is non-functional To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/1168915/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1828171] Re: New toolchain updates need to be rebuilt against -security only
Note one can create .deb packages with arbitrary version numbers not matching what is listed in debian/changelog. And this package does that, for Spaß and clarity. And both builds appear to produce binaries with version numbers matching the underlying source gcc versions e.g. both builds produce: gccgo-alpha-linux-gnu-4:8.3.0-1ubuntu1.2 Which launchpad will not allow to publish. Also I don't think you need to strictly rebuild and republish gcc-defaults-ports and similar packages. as they should be metapackages only and don't contain any toolchains (and i.e. are safe to copy into -security pocket) -- Regards, Dimitri. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828171 Title: New toolchain updates need to be rebuilt against -security only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1828171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770195] Re: OpenSSL missing ciphers
No, we do not wish to support weak-ssl-ciphers, they are long obsolete and dead. If you need to access acient servers or use acient clients you can e.g. launch precise in a lxd container with $ lxc launch ubuntu:precise Which ones are you specifically after? ** Changed in: openssl (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/1770195 Title: OpenSSL missing ciphers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1770195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810129] Re: blake2b512 / sha3-512 invalid digest type
(specifically published RFCs defining the relevant digest-algo / signature types format to be used in x.509 certificates / or any pki generically. Just the definition of the math to calculate the digest is not enough) ** Changed in: openssl (Ubuntu) Status: Incomplete => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810129 Title: blake2b512 / sha3-512 invalid digest type To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1810129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832120] Re: i386 - Test fails 'test_get_file_package_uninstalled_multiarch'
** Branch linked: lp:~ubuntu-core-dev/ubuntu/eoan/apport/ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832120 Title: i386 - Test fails 'test_get_file_package_uninstalled_multiarch' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1832120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810129] Re: blake2b512 / sha3-512 invalid digest type
I don't think it follows.
For example, with an RSA key I can use SHA3-512.
Signature Algorithm: RSA-SHA3-512
The point is, that digests are not independant, and one cannot just use
any as they need to have well known identifiers as specified in the
relevant RFCs.
Ie.
https://tools.ietf.org/html/rfc5280
https://tools.ietf.org/html/rfc3279
https://tools.ietf.org/html/rfc4055
And similar.
The SHA3 algorithms are being added in this draft:
https://tools.ietf.org/html/draft-turner-lamps-adding-sha3-to-pkix-01#ref-I-D.ietf-curdle-pkix
But it looks like it has expired
https://datatracker.ietf.org/doc/draft-turner-lamps-adding-sha3-to-pkix/
So i'm not sure what openssl is basing their implementation on. Maybe
something published by IEEE?!
For elliptic curve keys it seems like the supported digests are all the usual
suspects:
if (EVP_MD_type((const EVP_MD *)p2) != NID_sha1 &&
EVP_MD_type((const EVP_MD *)p2) != NID_ecdsa_with_SHA1 &&
EVP_MD_type((const EVP_MD *)p2) != NID_sha224 &&
EVP_MD_type((const EVP_MD *)p2) != NID_sha256 &&
EVP_MD_type((const EVP_MD *)p2) != NID_sha384 &&
EVP_MD_type((const EVP_MD *)p2) != NID_sha512) {
ECerr(EC_F_PKEY_EC_CTRL, EC_R_INVALID_DIGEST_TYPE);
return 0;
}
For RSA keys slightly larger list:
case NID_sha1:
case NID_sha224:
case NID_sha256:
case NID_sha384:
case NID_sha512:
case NID_md5:
case NID_md5_sha1:
case NID_md2:
case NID_md4:
case NID_mdc2:
case NID_ripemd160:
case NID_sha3_224:
case NID_sha3_256:
case NID_sha3_384:
case NID_sha3_512:
return 1;
If there are algos for which there are published RFCs please open a bug
upstream about adding those. If there are none defined, please submit
RFC to IETF to get them defined such that new digest algos can be added
across the internet - and not be specific to just openssl.
It's not up to Ubuntu to define new digest types in x.509, thus i'm
closing this bug report as opinion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810129
Title:
blake2b512 / sha3-512 invalid digest type
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1810129/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820130] Re: [SRU] modem-manager-gui fails to start after modemmanager is upgraded to 1.10.0-1
Graham, I'm on Bionc. Can I test the disco package on bionic? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820130 Title: [SRU] modem-manager-gui fails to start after modemmanager is upgraded to 1.10.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modem-manager-gui/+bug/1820130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828171] Re: New toolchain updates need to be rebuilt against -security only
Hey Colin! I'm EOD now so I didn't have time to look into it (and am probably too sleepy to look at this sanely) but what do you mean by 'versions overlapping'? 1.176ubuntu1.2 and 1.178ubuntu1.2 seem like different versions (1.176 for bionic and 1.178 for cosmic), and one is smaller than the other. How does the overlap look like? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828171 Title: New toolchain updates need to be rebuilt against -security only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1828171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832257] Re: regression: sudo returns exit code 0 if child is killed with SIGTERM
I'll release it tomorrow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832257 Title: regression: sudo returns exit code 0 if child is killed with SIGTERM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1832257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832257] Re: regression: sudo returns exit code 0 if child is killed with SIGTERM
I've uploaded it to build in the following PPA: https://launchpad.net/~ubuntu-security- proposed/+archive/ubuntu/ppa/+packages You can get it from there if you need it before tomorrow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832257 Title: regression: sudo returns exit code 0 if child is killed with SIGTERM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1832257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820130] Re: [SRU] modem-manager-gui fails to start after modemmanager is upgraded to 1.10.0-1
modem-manager-gui (0.0.19.1-1ubuntu0.18.04.1) bionic-proposed – tested, fixes the bug. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820130 Title: [SRU] modem-manager-gui fails to start after modemmanager is upgraded to 1.10.0-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modem-manager-gui/+bug/1820130/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824855] Re: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..."
I was wondering why it took so long to be able to unlock my laptop and it looks like it is this bug. Jun 10 15:34:30 speedy dbus-daemon[989]: [system] Activating via systemd: service name='net.reactivated.Fprint' unit='fprintd.service' requested by ':1.335' (uid=1000 pid=3119 comm="/usr/bin/gnome-shell " label="unconfined") Jun 10 15:34:30 speedy systemd[1]: Starting Fingerprint Authentication Daemon... Jun 10 15:34:55 speedy dbus-daemon[989]: [system] Failed to activate service 'net.reactivated.Fprint': timed out (service_start_timeout=25000ms) Jun 10 15:34:55 speedy gnome-shell[3119]: Failed to connect to Fprint service: Error calling StartServiceByName for net.reactivated.Fprint: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'net.reactivated.Fprint ** Changed in: gnome-shell (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/1824855 Title: Unlocking the screen takes a long time after "Starting Fingerprint Authentication Daemon..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1824855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832120] Re: i386 - Test fails 'test_get_file_package_uninstalled_multiarch'
** Changed in: apport (Ubuntu) Status: New => In Progress ** Changed in: apport (Ubuntu) Importance: Undecided => High ** Changed in: apport (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832120 Title: i386 - Test fails 'test_get_file_package_uninstalled_multiarch' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1832120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828171] Re: New toolchain updates need to be rebuilt against -security only
I had to remove gcc-defaults-ports from cosmic-proposed: https://launchpad.net/ubuntu/+source/gcc-defaults-ports/1.176ubuntu1.2 and https://launchpad.net/ubuntu/+source/gcc-defaults- ports/1.178ubuntu1.2 have overlapping binary versions in different builds, so these were unpublishable and were causing the publisher to OOPS frequently. Could you please sort out a non-overlapping version scheme here? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828171 Title: New toolchain updates need to be rebuilt against -security only To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1828171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714092] Re: crashes on launch
This bug also occurs on Ubuntu 18.04 and is worked around by the change described in Comment #4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714092 Title: crashes on launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qreator/+bug/1714092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752002] Comment bridged from LTC Bugzilla
--- Comment From mranw...@us.ibm.com 2019-06-10 17:45 EDT--- Anju - I tried this with both the 4.15.0-50 kernel (that has the first patch) and the test kernel in the above comment and I see the same behavior. No call trace, but on both the test ends: == Starting fuzzing at 2019-06-10 16:35:58 == Watchdog triggered; failed to progress for 60 seconds; killing Trying to shut ourselves down: 4986, last child 0 This is on a dd 2.3 witherspoon. Any ideas? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752002 Title: [P9,POwer NV][WSP][DD2.1][Ubuntu 1804][Perf fuzzer] : Call trace is seen while running perf fuzzer (perf:) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1752002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1744372] Re: gparted does not start - Unit -.mount does not exist, proceeding anyway.
*** This bug is a duplicate of bug 1652282 *** https://bugs.launchpad.net/bugs/1652282 I did not delete libgtk-x11-2.0.so.0. I installed 19.04 a few days ago. Unit tmp.mount does not exist, proceeding anyway. /usr/sbin/gpartedbin: error while loading shared libraries: libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 19.04 Release:19.04 Codename: disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1744372 Title: gparted does not start - Unit -.mount does not exist, proceeding anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gparted/+bug/1744372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826419] Fix merged to neutron (stable/queens)
Reviewed: https://review.opendev.org/663293 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=8c7c26c5bdb87ab7c30b5b50ec925c49ac4c01d4 Submitter: Zuul Branch:stable/queens commit 8c7c26c5bdb87ab7c30b5b50ec925c49ac4c01d4 Author: James Page Date: Mon Jun 3 09:38:16 2019 +0100 Revert "Pass network's dns_domain to dnsmasq conf" The dns_domain attribute of a network is intended for use by neutron when creating DNS records in an external DNS system such as Designate. By using the networks dns_domain, the configured search path on booted instances mismatches with the generated dns assignments for instance ports in the hosts file for dnsmasq which creates a mismatched forward/reverse lookup behaviour. This reverts commit 28b90f6c14659500694f321eedbf313d83a2ae9c. Change-Id: I26b5e8c35233718d97e58cfd5735c62d1684b4b0 Closes-Bug: 1826419 Depends-On: I145144c042b100f7e12a02a8ac7e0fbbe41e984d -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826419 Title: dhcp agent configured with mismatching domain and host entries To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1826419/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832257] Re: regression: sudo returns exit code 0 if child is killed with SIGTERM
do you have any guidance on how long a fix like this generally takes to land? we're deciding whether or not to roll our own, as this has some immediately undesirable effects in our environment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832257 Title: regression: sudo returns exit code 0 if child is killed with SIGTERM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1832257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832144] Re: Ubuntu 19.04 suspend freeze on Dell inspiron 7373
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832144 Title: Ubuntu 19.04 suspend freeze on Dell inspiron 7373 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832144/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS
built and passed all autopkgtests on all architectures. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797386 Title: [SRU] OpenSSL 1.1.1 to 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwww-perl/+bug/1797386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827995] Re: Request to integrate Microsoft's new Azure Linux Agent 2.2.40
This bug was fixed in the package walinuxagent - 2.2.40-0ubuntu1 --- walinuxagent (2.2.40-0ubuntu1) eoan; urgency=medium * New upstream release (LP: #1827995) * debian/patches/CVE-2019-0804.patch: dropped; included in upstream release. -- Mathieu Trudel-Lapierre Wed, 05 Jun 2019 15:26:47 -0400 ** Changed in: walinuxagent (Ubuntu) Status: Triaged => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-0804 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827995 Title: Request to integrate Microsoft's new Azure Linux Agent 2.2.40 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1827995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831666] Re: Add lsp-plugins to ubuntustudio-meta seed
** Changed in: ubuntustudio-meta Status: Fix Committed => Fix Released ** Changed in: ubuntustudio-meta (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831666 Title: Add lsp-plugins to ubuntustudio-meta seed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntustudio-meta/+bug/1831666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832223] Re: glusterfs in bionic is EOL
** Description changed: According to glusterfs release schedule[0], the glusterfs version[1] found in bionic 'universe' reached EOL at upstream level. + + 3.13 was a short term maintenance release, it reached end of life (EOL) + with the release of 4.0.0.[2] As I create this bug, only 4.1 and late are still 'maintained' [0]- https://www.gluster.org/release-schedule/ [1]- rmadison: glusterfs-server | 3.13.2-1build1 | bionic/universe glusterfs-server | 3.13.2-1ubuntu1 | bionic-proposed/universe + + [2]- https://docs.gluster.org/en/latest/release-notes/4.0.0/ ** Summary changed: - glusterfs in bionic is EOL + glusterfs in bionic/xenial is EOL ** Description changed: According to glusterfs release schedule[0], the glusterfs version[1] - found in bionic 'universe' reached EOL at upstream level. + found in Bionic and Xenial 'universe' reached EOL at upstream level. 3.13 was a short term maintenance release, it reached end of life (EOL) with the release of 4.0.0.[2] As I create this bug, only 4.1 and late are still 'maintained' [0]- https://www.gluster.org/release-schedule/ [1]- rmadison: - glusterfs-server | 3.13.2-1build1 | bionic/universe - glusterfs-server | 3.13.2-1ubuntu1 | bionic-proposed/universe + glusterfs | 3.7.6-1ubuntu1 | xenial/universe | source + glusterfs | 3.13.2-1build1 | bionic/universe | source + glusterfs | 3.13.2-1ubuntu1 | bionic-proposed/universe | source + glusterfs | 3.13.2-1ubuntu1 | bionic-updates/universe | source [2]- https://docs.gluster.org/en/latest/release-notes/4.0.0/ ** Also affects: glusterfs (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: glusterfs (Ubuntu Xenial) Importance: Undecided => Low ** Description changed: According to glusterfs release schedule[0], the glusterfs version[1] found in Bionic and Xenial 'universe' reached EOL at upstream level. - 3.13 was a short term maintenance release, it reached end of life (EOL) - with the release of 4.0.0.[2] + 3.7 has been released in November 2015. + 3.13 has been released in January 2018. + + Note: 3.13 was a short term maintenance release, it reached end of life + (EOL) with the release of 4.0.0.[2] As I create this bug, only 4.1 and late are still 'maintained' [0]- https://www.gluster.org/release-schedule/ [1]- rmadison: - glusterfs | 3.7.6-1ubuntu1 | xenial/universe | source - glusterfs | 3.13.2-1build1 | bionic/universe | source - glusterfs | 3.13.2-1ubuntu1 | bionic-proposed/universe | source - glusterfs | 3.13.2-1ubuntu1 | bionic-updates/universe | source + glusterfs | 3.7.6-1ubuntu1 | xenial/universe | source + glusterfs | 3.13.2-1build1 | bionic/universe | source + glusterfs | 3.13.2-1ubuntu1 | bionic-proposed/universe | source + glusterfs | 3.13.2-1ubuntu1 | bionic-updates/universe | source [2]- https://docs.gluster.org/en/latest/release-notes/4.0.0/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832223 Title: glusterfs in bionic/xenial is EOL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1832223/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832258] Re: Need to backport fix for inability to add Canon printers
** Changed in: cups 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/1832258 Title: Need to backport fix for inability to add Canon printers To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1832258/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1819198] Re: DBus/MPRIS2: GnomeMusic should send "Stopped" message when audio-track ends
Nice. My audio-recorder is quite old software, and it needs a complete re-design and re-coding. Let us see what happens on that. Nevertheless, thanks making GnomeMusic better and better. It counts a lot. Christopher <1819...@bugs.launchpad.net> escreveu no dia segunda, 10/06/2019 à(s) 11:41: > The developer now changed when the stop signal is send. Please see > https://gitlab.gnome.org/GNOME/gnome-music/merge_requests/430 and > https://gitlab.gnome.org/GNOME/gnome-music/issues/282 for more info. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1819198 > > Title: > DBus/MPRIS2: GnomeMusic should send "Stopped" message when audio-track > ends > > Status in gnome-music package in Ubuntu: > Fix Released > > Bug description: > Re-hi, > > GnomeMusic (via Dbus/MPRIS2) does not send "Stopped" message even > audio-track ends in the playlist. > GnomeMusic simply sends PlaybackStatus="Playing" for each new track. > This confuses other applications that listen to the DBus/MPRIS2 messages. > Other apps do not know that gnome-music changed track. > > GnomeMusic should send: >PlaybackStatus = "Palying" at start. >... >... >Send PlaybackStatus = "Stopped" >When track ends, or user stops playing, or user quits the application. > > Please see: > > https://specifications.freedesktop.org/mpris-spec/latest/Player_Interface.html#Property:PlaybackStatus > > Please fix this too. > https://bugs.launchpad.net/ubuntu/+source/gnome-music/+bug/1819037 > > Thank you for GnomeMusic. > > Most kindly > Moma & Bica (a small kind dog) > Portugal > > ProblemType: Bug > DistroRelease: Ubuntu 19.04 > Package: gnome-music 3.31.90-1 > ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 > Uname: Linux 4.19.0-13-generic x86_64 > ApportVersion: 2.20.10-0ubuntu23 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Fri Mar 8 17:37:52 2019 > InstallationDate: Installed on 2019-03-06 (1 days ago) > InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) > SourcePackage: gnome-music > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-music/+bug/1819198/+subscriptions > -- Sent from my PC, laptop or phone with Ubuntu-Linux. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819198 Title: DBus/MPRIS2: GnomeMusic should send "Stopped" message when audio-track ends To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-music/+bug/1819198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831710] Re: Touchpad not working (Lenevo Ideapad 330 series)
Boot into Ubuntu 18.04, in terminal check> mokutil --sb-state as Secure Boot will need to be disabled Then do in terminal sudo apt install git build-essential dkms git clone https://github.com/jeremyb31/mouse-4.18.git sudo dkms add ./mouse-4.18 sudo dkms install mouse/1.0 Reboot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831710 Title: Touchpad not working (Lenevo Ideapad 330 series) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831710/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832268] [NEW] Low performance when I play a game
Public bug reported: Low performance when I play a game, i have a 18 fps frame rate, but when I press "Esc" the frame rate come back to usual performance! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jun 10 17:30:56 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.15.0-51-generic, x86_64: installed nvidia, 390.116, 4.18.0-20-generic, x86_64: installed nvidia, 390.116, 4.18.0-21-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050] [10de:1c81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GP107 [GeForce GTX 1050] [1462:8c97] InstallationDate: Installed on 2019-05-14 (27 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic root=UUID=ffe2dbb1-cd8c-415e-91c3-d382f32bb40e ro locale=pt_BR quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0502 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A78L-M PLUS/USB3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0502:bd11/18/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MPLUS/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic performance ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832268 Title: Low performance when I play a game To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1832268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822129] Re: [SRU] leave device name empty so that nova can determine it instead
** Changed in: horizon (Ubuntu Xenial) Assignee: Eric Desrochers (slashd) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822129 Title: [SRU] leave device name empty so that nova can determine it instead To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1822129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827995] Re: Request to integrate Microsoft's new Azure Linux Agent 2.2.40
Tests performed: - Booted a VM and checked proper package version - Checked to make sure waagent was running and that the /var/log/waagent.log was error-free - Rebooted the VM and confirmed that waagent was still running and log was error-free - Verified that cloud-init still worked - Ran through azure-specific regression tests (correct disk size, correct kernel, billing tags, etc.) - Ran through basic ubuntu regression tests ( can SSH, correct packages, snaps working, lxd working, etc.) - Verified that our lxd start/stop regression testing passed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827995 Title: Request to integrate Microsoft's new Azure Linux Agent 2.2.40 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1827995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1712748] Re: package glusterfs-server 3.11.2-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1830615 *** https://bugs.launchpad.net/bugs/1830615 This bug was fixed in the package glusterfs - 3.13.2-1ubuntu1 For more details, see LP: #1830615 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1712748 Title: package glusterfs-server 3.11.2-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1712748/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827995] Re: Request to integrate Microsoft's new Azure Linux Agent 2.2.40
Removing block-proposed. Patviafore confirmed that manual tests are passing. Pat, could you please give details here? ** Tags removed: block-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827995 Title: Request to integrate Microsoft's new Azure Linux Agent 2.2.40 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1827995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821957] Re: Turning off a monitor unlocks the computer
** Changed in: gnome-screensaver (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1821957 Title: Turning off a monitor unlocks the computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntubudgie/+bug/1821957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831713] Re: Security update to libpam-u2f from Yubico
** Changed in: pam-u2f (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1831713 Title: Security update to libpam-u2f from Yubico To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam-u2f/+bug/1831713/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832041] Re: The mouse stops working
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832041 Title: The mouse stops working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1832041/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778844] Re: nvme multipath does not report path relationships
I installed cosmic on power9 (boston) a non-nvme system, installed initramfs-tools from -proposed and install kdump-tools. Triggered a dump, but I got a kernel panic. Please let me know if I am doing something wrong here. ubuntu@tiselius:~$ uname -a Linux tiselius 4.18.0-21-generic #22-Ubuntu SMP Wed May 15 13:12:45 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux ubuntu@tiselius:~$ ubuntu@tiselius:~$ apt policy initramfs-tools initramfs-tools: Installed: 0.131ubuntu15.2 Candidate: 0.131ubuntu15.2 Version table: *** 0.131ubuntu15.2 500 500 http://ports.ubuntu.com/ubuntu-ports cosmic-proposed/main ppc64el Packages ubuntu@tiselius:~$ ubuntu@tiselius:~$ apt policy kdump-tools kdump-tools: Installed: 1:1.6.5-1ubuntu1~18.10.1 Candidate: 1:1.6.5-1ubuntu1~18.10.1 Version table: *** 1:1.6.5-1ubuntu1~18.10.1 500 500 http://ports.ubuntu.com/ubuntu-ports cosmic-updates/main ppc64el Packages 100 /var/lib/dpkg/status 1:1.6.4-2ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports cosmic/main ppc64el Packages ubuntu@tiselius:~$ ubuntu@tiselius:~$ sudo kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.18.0-21-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.18.0-21-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=295f571b-b731-4ebb-b752-60aadc80fc1b ro console=hvc0 nr_cpus=1 systemd.unit=kdump-tools-dump.service irqpoll noirqdistrib nousb" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz ubuntu@tiselius:~$ ubuntu@tiselius:~$ cat /proc/cmdline root=UUID=295f571b-b731-4ebb-b752-60aadc80fc1b ro console=hvc0 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M@128M ubuntu@tiselius:~$ ubuntu@tiselius:~$ dmesg | grep Reser [0.00] Reserving 4096MB of memory at 128MB for crashkernel (System RAM: 131072MB) [0.00] cma: Reserved 6560 MiB at 0x200e6200 ubuntu@tiselius:~$ root@tiselius:/home/ubuntu# echo 1 > /proc/sys/kernel/sysrq root@tiselius:/home/ubuntu# echo c > /proc/sysrq-trigger tiselius login: [ 150.167288] cloud-init[4529]: Cloud-init v. 19.1-1-gbaa47854-0ubuntu1~18.10.1 running 'modules:final' at Mon, 10 Jun 2019 19:53:40 +. Up 149.80 seconds. [ 150.167687] cloud-init[4529]: Cloud-init v. 19.1-1-gbaa47854-0ubuntu1~18.10.1 finished at Mon, 10 Jun 2019 19:53:40 +. Datasource DataSourceMAAS [http://10-245-64-0--21.maas-internal:5248/MAAS/metadata/]. Up 150.11 seconds [ 360.313029] kdump-tools[4915]: Stopping kdump-tools: * unloaded kdump kernel [ 376.552452] kdump-tools[10449]: Starting kdump-tools: * Creating symlink /var/lib/kdump/vmlinuz [ 376.553743] kdump-tools[10449]: * Creating symlink /var/lib/kdump/initrd.img [ 376.585085] kdump-tools[10449]: Modified cmdline:root=UUID=295f571b-b731-4ebb-b752-60aadc80fc1b ro console=hvc0 nr_cpus=1 systemd.unit=kdump-tools-dump.service irqpoll noirqdistrib nousb elfcorehdr=158784K [ 376.953223] kdump-tools[10449]: * loaded kdump kernel [ 398.517900] sysrq: SysRq : Trigger a crash [ 398.517952] Unable to handle kernel paging request for data at address 0x [ 398.518000] Faulting instruction address: 0xc082a3a8 [ 398.518071] Oops: Kernel access of bad area, sig: 11 [#1] [ 398.518115] LE SMP NR_CPUS=2048 NUMA PowerNV [ 398.518172] Modules linked in: joydev input_leds mac_hid vmx_crypto ofpart crct10dif_vpmsum ipmi_powernv ipmi_devintf at24 uio_pdrv_genirq ipmi_msghandler uio cmdlinepart powernv_flash mtd opal_prd ibmpowernv sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure scsi_transport_sas hid_generic usbhid hid ast i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm crc32c_vpmsum i40e aacraid drm_panel_orientation_quirks [ 398.518769] CPU: 0 PID: 10529 Comm: bash Kdump: loaded Not tainted 4.18.0-21-generic #22-Ubuntu [ 398.518881] NIP: c082a3a8 LR: c082b234 CTR: c082a380 [ 398.518976] REGS: c00b9b88ba00 TRAP: 0300 Not tainted (4.18.0-21-generic) [ 398.519068] MSR: 90009033 CR: 4842 XER: 2004 [ 398.519161] CFAR: c082b230 DAR: DSISR: 4200 IRQMASK: 0 [ 398.519161] GPR00: c082b234 c00b9b88bc80 c178ca00 0063 [ 398.519161] GPR04: 0001 036a 90009033 31c40058 [ 398.519161] GPR08: 0007 0001 90001003 [ 398.519161] GPR12: c082a380 c1b0 0a452fe89760
[Bug 1831666] Re: Add lsp-plugins to ubuntustudio-meta seed
** Changed in: ubuntustudio-meta Status: In Progress => Fix Committed ** Changed in: ubuntustudio-meta (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831666 Title: Add lsp-plugins to ubuntustudio-meta seed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntustudio-meta/+bug/1831666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1832101/+attachment/5269979/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1832101/+attachment/5269976/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1832101/+attachment/5269978/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1832101/+attachment/5269983/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1832101/+attachment/5269982/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1832101/+attachment/5269980/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1832101/+attachment/5269981/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] Re: systemd-networkd: Lost carrier e1000
apport information ** Tags added: apport-collected ** Description changed: Just installed a fresh installation of ubuntu 19 on our server and we're having a lot of carrier-lost erros. There is no really good indicaton why this is hapening. Tried the following : disabled ipv6 (just to be sure), on nic set GSO,GRO,TSO to off. removed netplan, switched to systemd-networkd and added configurewithoutcarrier to true, the option ignorecarrierlost is not accepted by systemd. Description:Ubuntu 19.04 Release:19.04 Kernel Log Jun 8 12:11:17 mc2 kernel: [30304.199050] [ cut here ] Jun 8 12:11:17 mc2 kernel: [30304.199052] NETDEV WATCHDOG: eno1 (e1000e): transmit queue 0 timed out Jun 8 12:11:17 mc2 kernel: [30304.199062] WARNING: CPU: 8 PID: 0 at net/sched/sch_generic.c:461 dev_watchdog+0x221/0x230 Jun 8 12:11:17 mc2 kernel: [30304.199062] Modules linked in: intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 crypto_simd cryptd glue_helper intel_cstate intel_rapl_perf intel_wmi_thunderbolt wmi_bmof intel_pch_thermal mac_hid acpi_pad ip6t_REJE CT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_multiport xt_limit xt_tcpudp xt_addrtype sch_fq_codel xt_conntrack ip6 table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter ip_ tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 e1000e nvme ahci i2c_i801 libahci nvme_core wmi video pinctrl_cannonlake pinctrl_intel Jun 8 12:11:17 mc2 kernel: [30304.199080] CPU: 8 PID: 0 Comm: swapper/8 Not tainted 5.0.0-16-generic #17-Ubuntu Jun 8 12:11:17 mc2 kernel: [30304.199081] Hardware name: Gigabyte Technology Co., Ltd. B360 HD3P-LM/B360HD3PLM-CF, BIOS F4 HZ 04/30/2019 Jun 8 12:11:17 mc2 kernel: [30304.199082] RIP: 0010:dev_watchdog+0x221/0x230 Jun 8 12:11:17 mc2 kernel: [30304.199083] Code: 00 49 63 4e e0 eb 92 4c 89 ef c6 05 9a 92 f0 00 01 e8 13 38 fc ff 89 d9 4c 89 ee 48 c7 c7 68 5e da 95 48 89 c2 e8 71 f1 79 ff <0f> 0b eb c0 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 Jun 8 12:11:17 mc2 kernel: [30304.199083] RSP: 0018:93adff203e68 EFLAGS: 00010286 Jun 8 12:11:17 mc2 kernel: [30304.199084] RAX: RBX: RCX: 0006 Jun 8 12:11:17 mc2 kernel: [30304.199084] RDX: 0007 RSI: 0096 RDI: 93adff216440 Jun 8 12:11:17 mc2 kernel: [30304.199084] RBP: 93adff203e98 R08: 0001 R09: 0c61 Jun 8 12:11:17 mc2 kernel: [30304.199085] R10: 0004 R11: R12: 0001 Jun 8 12:11:17 mc2 kernel: [30304.199085] R13: 93adec48 R14: 93adec4804c0 R15: 93adeca74080 Jun 8 12:11:17 mc2 kernel: [30304.199086] FS: () GS:93adff20() knlGS: Jun 8 12:11:17 mc2 kernel: [30304.199086] CS: 0010 DS: ES: CR0: 80050033 Jun 8 12:11:17 mc2 kernel: [30304.199086] CR2: 7f7783ea4300 CR3: 00043920e003 CR4: 003606e0 Jun 8 12:11:17 mc2 kernel: [30304.199087] DR0: DR1: DR2: Jun 8 12:11:17 mc2 kernel: [30304.199087] DR3: DR6: fffe0ff0 DR7: 0400 Jun 8 12:11:17 mc2 kernel: [30304.199087] Call Trace: Jun 8 12:11:17 mc2 kernel: [30304.199088] Jun 8 12:11:17 mc2 kernel: [30304.199090] ? pfifo_fast_enqueue+0x120/0x120 Jun 8 12:11:17 mc2 kernel: [30304.199091] call_timer_fn+0x30/0x130 Jun 8 12:11:17 mc2 kernel: [30304.199092] run_timer_softirq+0x3e4/0x420 Jun 8 12:11:17 mc2 kernel: [30304.199093] ? ktime_get+0x3c/0xa0 Jun 8 12:11:17 mc2 kernel: [30304.199095] ? lapic_next_deadline+0x26/0x30 Jun 8 12:11:17 mc2 kernel: [30304.199096] ? clockevents_program_event+0x93/0xf0 Jun 8 12:11:17 mc2 kernel: [30304.199097] __do_softirq+0xdc/0x2f3 Jun 8 12:11:17 mc2 kernel: [30304.199099] irq_exit+0xc0/0xd0 Jun 8 12:11:17 mc2 kernel: [30304.199099] smp_apic_timer_interrupt+0x79/0x140 Jun 8 12:11:17 mc2 kernel: [30304.199100] apic_timer_interrupt+0xf/0x20 Jun 8 12:11:17 mc2 kernel: [30304.199101] Jun 8 12:11:17 mc2 kernel: [30304.199102] RIP: 0010:cpuidle_enter_state+0xbd/0x450 Jun 8 12:11:17 mc2 kernel: [30304.199103] Code: ff e8 87 36 87 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 63 03 00 00 31 ff e8 ba 65 8d ff fb 66 0f 1f 44 00 00 < 45> 85 ed 0f 88 8d 02 00 00 49 63 cd 48 8b 75 d0 48 2b 75 c8 48 8d Jun 8 12:11:17 mc2 kernel: [30304.199103] RSP: 0018:bd934635be60 EFLAGS: 0246
[Bug 1832101] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1832101/+attachment/5269975/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832101] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1832101/+attachment/5269977/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832101 Title: systemd-networkd: Lost carrier e1000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832101/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832259] [NEW] Parole fails to clear all recent items initially
Public bug reported: Odd one. Clearing recent items fails to do so. However - play something from the recent items - then clear - does remove that item. HArd to describe - so attached a vid ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: parole 1.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu2 Architecture: amd64 CurrentDesktop: XFCE Date: Mon Jun 10 20:35:57 2019 InstallationDate: Installed on 2018-08-27 (287 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180824) SourcePackage: parole UpgradeStatus: Upgraded to eoan on 2018-10-14 (239 days ago) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2018-09-21T16:30:23.845026 ** Affects: parole (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages ** Attachment added: "video of bug" https://bugs.launchpad.net/bugs/1832259/+attachment/5269984/+files/parole%20bug-2019-06-10_20.34.20.mp4 ** Summary changed: - Parole fails to clear recent items + Parole fails to clear all recent items initially -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832259 Title: Parole fails to clear all recent items initially To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/parole/+bug/1832259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832257] Re: regression: sudo returns exit code 0 if child is killed with SIGTERM
Oh wow, I'm not sure how that happened. I'll release an update for this. ** Changed in: sudo (Ubuntu) Status: New => Confirmed ** Changed in: sudo (Ubuntu) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Also affects: sudo (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: sudo (Ubuntu) Status: Confirmed => Fix Released ** Changed in: sudo (Ubuntu Xenial) Status: New => Confirmed ** Changed in: sudo (Ubuntu Xenial) Assignee: (unassigned) => Marc Deslauriers (mdeslaur) ** Changed in: sudo (Ubuntu Xenial) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832257 Title: regression: sudo returns exit code 0 if child is killed with SIGTERM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1832257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832258] [NEW] Need to backport fix for inability to add Canon printers
Public bug reported: The following bug was reported and fixed in cups 2.2.11. https://github.com/apple/cups/issues/5484 Without the fix, it is not possible to add or use a number of Canon printers. Currently, 19.04 ships with 2.2.10 + some backports, but those backports do not include the fix for this problem. We either need the fix backported or an update to 2.2.11. Release: Ubuntu 19.04 Version: 2.2.10-4ubuntu2 What you expected: Adding a canon printer works What happened instead: Adding a canon printer fails with a useless error and log investigation lead to upstream issue. ** Affects: cups Importance: Unknown Status: Unknown ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Bug watch added: github.com/apple/cups/issues #5484 https://github.com/apple/cups/issues/5484 ** Also affects: cups via https://github.com/apple/cups/issues/5484 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832258 Title: Need to backport fix for inability to add Canon printers To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1832258/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1832257] [NEW] regression: sudo returns exit code 0 if child is killed with SIGTERM
Public bug reported: hey there- it looks like we accidentally removed the patch that fixed this problem when releasing sudo 1.8.16-0ubuntu1.6 - https://git.launchpad.net/ubuntu/+source/sudo/commit/?h=ubuntu/xenial- updates=15345b19b82f587498573b38554e24ec0ab816cb note that `terminate-with-commands-signal.patch` is removed from debian/patches/series in that commit and the behavior described in the original bug (LP 1686803) has returned in xenial. can we get this back into the current sudo package? the fix still exists upstream so it feels like this was an accidental reversion. ** Affects: sudo (Ubuntu) Importance: Undecided Status: New ** Tags: regression-release -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1832257 Title: regression: sudo returns exit code 0 if child is killed with SIGTERM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1832257/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
