[Bug 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected
As mentioned in the bug description, this bug only ever occurred on Intel 8265 with the M337 on bionic. All other issues should be discussed in other bugs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: [regression] Logitech M337 mice are automatically disconnected after connected To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected
This bug is not about suspending and resuming. And I can't test resuming because my system becomes too unstable (for other reasons). As for system reboot, I have always had problems with some Bluetooth devices reconnecting on reboot. But that problem is not confined to mice. It happens with audio too. I think the mice fixes in comment #50 are worth having, but this is the wrong bug to discuss them in. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: [regression] Logitech M337 mice are automatically disconnected after connected To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822239] [NEW] NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] doesn't support 3D capabilities on Disco 19.04 beta
Public bug reported: Summary: I use a Dell Precision 5530 (I+N) machine and switch to Nivida card. (The Nvidia driver installed via Additional driver of Software & Update - nvida-driver-390) Try to run glxgears and got the error - Error: couldn't get an RGB, Double-buffered visual Steps to reproduce: 1. Install the tool: $ sudo apt install mesa-utils 2. Run glxgears $ glxgears Expected result: Open up a window with an OpenGL rendering of a simple arrangement of three rotating gears. Actual result: An error returns: Error: couldn't get an RGB, Double-buffered visual Failure rate: 100% - CPU: Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz (12x) GPU: 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b system-product-name: Precision 5530 bios-version: 1.6.0 system-manufacturer: Dell Inc. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: ce-qa-concern disco hwe-graphics -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822239 Title: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] doesn't support 3D capabilities on Disco 19.04 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1822239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822237] Re: 19.04 BIOS full-disk install with encryption failed to boot (grub-rescue)
** Description changed: Lubuntu 19.04 full-disk encrypted install (BIOS) Install went perfectly, rebooted on request however resulted in finding myself in grub-rescue + + error: no such device: 969bff21-1ee3-490a-8922-6fc36941da6f + error: unknown filesystem + Entering rescue mode.. + grub rescue > + + // please note the ^ messages were written down & later transcribed + here; no guarantee on being letter perfect I rebooted the install-media, and mounted the disk (using my passphrase) and a cursory glance showed no issues. /boot & a few other folders looked like I expected. (This is the third install on this box last couple of hours as I work down Lubuntu 19.04 checklist so I doubt I did anything wrong, but I have done wrong or in error. I have not re-attempted an encrypted install, but I have re-attempted booting this box since install). first line of /etc/apt/sources.list deb cdrom:[Lubuntu 19.04 _Disco Dingo_ - Alpha amd64 (20190326.1)]/ disco main multiverse restricted universe ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: calamares 3.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 .etc.calamares.modules.automirror.conf: --- baseUrl: archive.ubuntu.com distribution: Lubuntu geoIpUrl: https://ipapi.co/json .etc.calamares.modules.finished.conf: --- restartNowChecked: true restartNowEnabled: true restartNowCommand: "systemctl -i reboot" .etc.calamares.modules.partition.conf: efiSystemPartition: "/boot/efi" enableLuksAutomatedPartitioning: true neverCreateSwap: true drawNestedPartitions: true .etc.calamares.modules.shellprocess_logs.conf: --- dontChroot: true timeout: 30 script: - calamares-logs-helper @@ROOT@@ .etc.calamares.modules.unpackfs.conf: --- unpack: - source: "/cdrom/casper/filesystem.squashfs" sourcefs: "squashfs" destination: "" ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CasperVersion: 1.402 CurrentDesktop: LXQt Date: Fri Mar 29 05:24:53 2019 LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) RelatedPackageVersions: calamares-settings-ubuntu-common 1:19.04.3 calamares-settings-lubuntu 1:19.04.3 xfsprogs 4.15.1-1ubuntu1 btrfs-progs 4.20.2-1 SourcePackage: calamares UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822237 Title: 19.04 BIOS full-disk install with encryption failed to boot (grub- rescue) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1822237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822239] Re: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] doesn't support 3D capabilities on Disco 19.04 beta
Automatically attached ** Attachment added: "snap_list.log" https://bugs.launchpad.net/bugs/1822239/+attachment/5250432/+files/snap_list.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822239 Title: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] doesn't support 3D capabilities on Disco 19.04 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1822239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814919] Re: dpdk 18.11-5 ADT test failure with linux 5.0.0-3.4
I guess this was a bot right? I just forgot to also switch the second tag - Thanks Bot or Brian (whoever it was) for reminding me :-) ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814919 Title: dpdk 18.11-5 ADT test failure with linux 5.0.0-3.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1814919/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822239] Re: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] doesn't support 3D capabilities on Disco 19.04 beta
Automatically attached ** Attachment added: "acpidump.log" https://bugs.launchpad.net/bugs/1822239/+attachment/5250431/+files/acpidump.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822239 Title: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] doesn't support 3D capabilities on Disco 19.04 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1822239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822239] Re: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] doesn't support 3D capabilities on Disco 19.04 beta
Automatically attached ** Attachment added: "sosreport-u-Precision-5530-20190329134737.tar.gz" https://bugs.launchpad.net/bugs/1822239/+attachment/5250430/+files/sosreport-u-Precision-5530-20190329134737.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822239 Title: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] [10de:1cbb] doesn't support 3D capabilities on Disco 19.04 beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1822239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819624] Re: linux: 4.18.0-17.18 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819623 (bionic/linux-hwe) derivatives: bug 1819612 (linux-raspi2), bug 1819614 (linux-aws), bug 1819618 (linux-azure), bug 1819620 (linux-gcp), bug 1819621 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Friday, 15. March 2019 23:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819624 Title: linux: 4.18.0-17.18 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819624/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811900] Re: SRU 3.28 latest git to bionic
fossfreedom, Since this is a blocking issue please also report it to the GNOME developers at: https://gitlab.gnome.org/GNOME/mutter/issues It would obviously be best if we could get a proper fix without any reverts. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811900 Title: SRU 3.28 latest git to bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1811900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822230] Re: lubuntu 19.04 install dual screen; login user/password boxes on both displays allowing password entry
** Description changed: Lubuntu 19.04 (x86_64) QA-Test install dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) On first boot, i expected to see (on either display) a single login box for username/password. Instead I got a box on each display (as if mirrored) but noted the password was only appearing as dots on one screen. With experimentation, I can enter different passwords on each display - if I press whilst inside the valid-password box I get logged in, if I press on an invalid password screen (with valid password on the other screen) I get login failed correctly. As such I don't see how this could be mis-used, but it is a little confusing/distracting, but minor. After login, if I logout I get the same two user/boxes allowing different entry in each. At this time I have not rebooted; it's still initial boot (post-install) My displays are differently aligned to the default; but this occurred on reboot before any adjustments were made to displays (to match my having one tilted-left so portrait mode etc) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: sddm 0.18.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: LXQt Date: Fri Mar 29 14:26:22 2019 InstallationDate: Installed on 2019-03-29 (0 days ago) InstallationMedia: Lubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) SourcePackage: sddm UpgradeStatus: No upgrade log present (probably fresh install) -- The following (snippet) is from my QA-test comments --- (between steps 2 & 3 I had to use lxqt.prefs-monitor.settings to adjust my display to match portrait & my display organization for the little sanity i have left..) // maybe the display change caused this??? I forgot I did that... I'll add comment on https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1822230 --- Could it be that the LXQt.Prefs -> Monitor.Settings change I made before install impacted this?? Even if this change has caused issue, it shouldn't... + + --- + first line of /etc/apt/source.list + deb cdrom:[Lubuntu 19.04 _Disco Dingo_ - Alpha amd64 (20190326.1)]/ disco main multiverse restricted universe -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822230 Title: lubuntu 19.04 install dual screen; login user/password boxes on both displays allowing password entry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1822230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822237] [NEW] 19.04 BIOS full-disk install with encryption failed to boot (grub-rescue)
Public bug reported: Lubuntu 19.04 full-disk encrypted install (BIOS) Install went perfectly, rebooted on request however resulted in finding myself in grub-rescue I rebooted the install-media, and mounted the disk (using my passphrase) and a cursory glance showed no issues. /boot & a few other folders looked like I expected. (This is the third install on this box last couple of hours as I work down Lubuntu 19.04 checklist so I doubt I did anything wrong, but I have done wrong or in error. I have not re-attempted an encrypted install, but I have re-attempted booting this box since install). first line of /etc/apt/sources.list deb cdrom:[Lubuntu 19.04 _Disco Dingo_ - Alpha amd64 (20190326.1)]/ disco main multiverse restricted universe ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: calamares 3.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 .etc.calamares.modules.automirror.conf: --- baseUrl: archive.ubuntu.com distribution: Lubuntu geoIpUrl: https://ipapi.co/json .etc.calamares.modules.finished.conf: --- restartNowChecked: true restartNowEnabled: true restartNowCommand: "systemctl -i reboot" .etc.calamares.modules.partition.conf: efiSystemPartition: "/boot/efi" enableLuksAutomatedPartitioning: true neverCreateSwap: true drawNestedPartitions: true .etc.calamares.modules.shellprocess_logs.conf: --- dontChroot: true timeout: 30 script: - calamares-logs-helper @@ROOT@@ .etc.calamares.modules.unpackfs.conf: --- unpack: - source: "/cdrom/casper/filesystem.squashfs" sourcefs: "squashfs" destination: "" ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CasperVersion: 1.402 CurrentDesktop: LXQt Date: Fri Mar 29 05:24:53 2019 LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) RelatedPackageVersions: calamares-settings-ubuntu-common 1:19.04.3 calamares-settings-lubuntu 1:19.04.3 xfsprogs 4.15.1-1ubuntu1 btrfs-progs 4.20.2-1 SourcePackage: calamares UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: calamares (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Attachment added: "sudo lshw >lshw.txt" https://bugs.launchpad.net/bugs/1822237/+attachment/5250413/+files/lshw.txt ** Description changed: Lubuntu 19.04 full-disk encrypted install (BIOS) Install went perfectly, rebooted on request however resulted in finding myself in grub-rescue I rebooted the install-media, and mounted the disk (using my passphrase) and a cursory glance showed no issues. /boot & a few other folders looked like I expected. + (This is the third install on this box last couple of hours as I work + down Lubuntu 19.04 checklist so I doubt I did anything wrong, but I have + done wrong or in error. I have not re-attempted an encrypted install, + but I have re-attempted booting this box since install). - (This is the third install on this box last couple of hours as I work down Lubuntu 19.04 checklist so I doubt I did anything wrong, but I have done wrong or in error. I have not re-attempted an encrypted install, but I have re-attempted booting this box since install). + first line of /etc/apt/sources.list + deb cdrom:[Lubuntu 19.04 _Disco Dingo_ - Alpha amd64 (20190326.1)]/ disco main multiverse restricted universe + ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: calamares 3.2.4-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 .etc.calamares.modules.automirror.conf: - --- - baseUrl: archive.ubuntu.com - distribution: Lubuntu - geoIpUrl: https://ipapi.co/json + --- + baseUrl: archive.ubuntu.com + distribution: Lubuntu + geoIpUrl: https://ipapi.co/json .etc.calamares.modules.finished.conf: - --- - restartNowChecked: true - restartNowEnabled: true - restartNowCommand: "systemctl -i reboot" + --- + restartNowChecked: true + restartNowEnabled: true + restartNowCommand: "systemctl -i reboot" .etc.calamares.modules.partition.conf: - efiSystemPartition: "/boot/efi" - enableLuksAutomatedPartitioning: true - neverCreateSwap: true - drawNestedPartitions: true + efiSystemPartition: "/boot/efi" + enableLuksAutomatedPartitioning: true + neverCreateSwap: true + drawNestedPartitions: true .etc.calamares.modules.shellprocess_logs.conf: - --- - dontChroot: true - timeout: 30 - script: - - calamares-logs-helper @@ROOT@@ + --- + dontChroot: true + timeout: 30 + script: + - calamares-logs-helper @@ROOT@@ .etc.calamares.modules.unpackfs.conf: - --- - unpack: - - source: "/cdrom/casper/filesystem.squashfs" - sourcefs: "squashfs" - destination: "" + --- + unpack: + - source: "/cdrom/casper/filesystem.squashfs" + sourcefs: "squashfs" + destination: "" ApportVersion: 2.20.10-0ubuntu23 Architecture:
[Bug 1821936] Re: No sound output on Zen AIO 27 Z272SD_Z272SD
Does kernel parameter "snd_hda_intel.model=alc256-asus-aio" help? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821936 Title: No sound output on Zen AIO 27 Z272SD_Z272SD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1821936/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819624] Re: linux: 4.18.0-17.18 -proposed tracker
4.18.0-17.18 - generic Regression test CMPL, RTB. Issue to note in amd64: ubuntu_kernel_selftests - rtnetlink.sh in net (bug 1812978) psock_snd in net (bug 1812618) ubuntu_kvm_unit_tests - apic-split timeouted (bug 1821390) apic timeouted (bug 1748103) vmware_backdoors (bug 1821393) svm (bug 1821903) ubuntu_ltp - failed to fork child on some tests ubuntu_ltp_syscalls - fanotify09-2 (bug 1804594) sync_file_range02 (bug 1819116) xfstests - failed to build on C (bug 1802486) Issue to note in arm64: hwclock - issue for HP m400 (bug 1716603) ubuntu_bpf - Failed sockmap unexpected timeout on ARM64 (bug 1805806) ubuntu_kernel_selftests - cpu-hotplug failed on moonshot (bug 1809701) rtnetlink.sh in net (bug 1812978) psock_snd in net (bug 1812618) ubuntu_kvm_unit_tests - gicv2-mmio-up and gicv2-mmio-3p failed on Moonshot ARM64 (bug 1802492) ubuntu_ltp_syscalls - fanotify09-2 (bug 1804594) sync_file_range02 (bug 1819116) xfstests - failed to build on C (bug 1802486) Issue to note in i386: ubuntu_bpf - Some test in test_verifier failed on i386 Bionic (bug 1788578) ubuntu_btrfs_kernel_fixes - ff76b05 failed (bug 1812988) ubuntu_kernel_selftests - rtnetlink.sh in net (bug 1812978) psock_snd in net (bug 1812618) Kprobe event string type argument in ftrace (bug 1812645) ubuntu_kvm_smoke_test - timed out waiting for dnsmasq lease (bug 1802056) ubuntu_kvm_unit_tests - all 29 test failed on i386 (bug 1822235) ubuntu_ltp_syscalls - fanotify09-2 (bug 1804594) sync_file_range02 (bug 1819116) ubuntu_lttng_smoke_test - lttng-smoke test failed on i386 4.18 kernel (bug 1802495) xfstests - failed to build on C (bug 1802486) Issue to note in ppc64le (P8): ubuntu_bpf - test_map failed on PowerPC (bug 1802474) ubuntu_btrfs_kernel_fixes - ff76b05 failed (bug 1812988) ubuntu_kernel_selftests - reuseport_bpf_numa in net (bug 1812638) psock_snd in net (bug 1812618) TRACE_syscall.ptrace_syscall_dropped in seccomp (bug 1812796) ebb in powerpc (bug 1812805) ubuntu_kvm_unit_tests - sprs timed out (bug 1740017) ubuntu_ltp_syscalls - fallocate05 (bug 1783880) fanotify09-2 (bug 1804594) sync_file_range02 (bug 1819116) xfstests - failed to build on C (bug 1802486) 48 / 49 tests were run, missing: xfstests Issue to note in ppc64le (P9): hwclock - hwclock test failed on PowerPC due to 0.x sec difference (bug 1802233) ubuntu_bpf - test_map failed on PowerPC (bug 1802474) ubuntu_btrfs_kernel_fixes - ff76b05 failed (bug 1812988) ubuntu_kernel_selftests - reuseport_bpf_numa in net (bug 1812638) psock_snd in net (bug 1812618) TRACE_syscall.ptrace_syscall_dropped in seccomp (bug 1812796) ebb in powerpc (bug 1812805) ubuntu_kvm_unit_tests - sprs timed out (bug 1740017) ubuntu_ltp_syscalls - fallocate05 (bug 1783880) fanotify09-2 (bug 1804594) sync_file_range02 (bug 1819116) 47 / 48 tests were run, missing: ubuntu_btrfs_kernel_fixes Issue to note in s390x (KVM): ubuntu_bpf - test_verifier in ubuntu_bpf test failed with 'Failed to load prog' on Cosmic s390x (bug 1801033) ubuntu_kernel_selftests - reuseport_dualstack in net (bug 1812843) rtnetlink.sh in net (bug 1812978) msg_zerocopy in net (bug 1812620) psock_snd in net (bug 1812618) TRACE_syscall in ftrace (bug 1812824) ubuntu_ltp_syscalls - fanotify09-2 (bug 1804594) msgstress03 (bug 1797341) ubuntu_lxc - Container "reboot" is defined (bug 1788574) 47 / 48 tests were run, missing: ubuntu_btrfs_kernel_fixes Issue to note in s390x (Ubuntu on LPAR): ubuntu_bpf - test_verifier in ubuntu_bpf test failed with 'Failed to load prog' on Cosmic s390x (bug 1801033) ubuntu_kernel_selftests - reuseport_dualstack in net (bug 1812843) rtnetlink.sh in net (bug 1812978) psock_snd in net (bug 1812618) TRACE_syscall in ftrace (bug 1812824) ubuntu_ltp_syscalls - fanotify09-2 (bug 1804594) sync_file_range02 (bug 1819116) ubuntu_lxc - lxc-test-api-reboot failed (bug 1776381) Container "reboot" is defined (bug 1788574) 47 / 48 tests were run, missing: ubuntu_btrfs_kernel_fixes Issue to note in s390x (zVM): ubuntu_bpf - test_verifier in ubuntu_bpf test failed with 'Failed to load prog' on Cosmic s390x (bug 1801033) ubuntu_kernel_selftests - reuseport_dualstack in net (bug 1812843) rtnetlink.sh in net (bug 1812978) psock_snd in net (bug 1812618) TRACE_syscall in ftrace (bug 1812824) ubuntu_kvm_unit_tests - skey failed (bug 1778705) ubuntu_ltp_syscalls - fanotify09-2 (bug 1804594) msgstress03 (bug 1797341) sync_file_range02 (bug 1819116) ubuntu_lxc - Container "reboot" is defined (bug 1788574) Note: No xfstests for P9 as it does not have a scratch drive Note: Missing ubuntu_btrfs_kernel_fixes for s390x (bug 1809860) ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- You
[Bug 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected
No it's not specific to Intel 8265. Can your M337 reconnect automatically after system suspend or system reboot? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773897 Title: [regression] Logitech M337 mice are automatically disconnected after connected To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822235] Re: All 29 tests in kvm-unit-test failed (timeouted) on i386
Could be found on other kernels as well, for X/T the test will failed to build. https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1798007 ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822235 Title: All 29 tests in kvm-unit-test failed (timeouted) on i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1822235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821677] Re: dl_open segment fault in ubuntu18.10 glibc2.28
This regression caused by following patch. It is mostly arm code but
also affecting x86. If I remove this patch segfault will go away.
$ cat unsubmitted-ldso-abi-check.diff
---
elf/dl-load.c | 219 ++
1 file changed, 219 insertions(+)
--- a/elf/dl-load.c
+++ b/elf/dl-load.c
@@ -1438,6 +1438,209 @@
_dl_debug_printf_c ("\t\t(%s)\n", what);
}
+#ifdef __arm__
+/* Read an unsigned leb128 value from P, store the value in VAL, return
+ P incremented past the value. We assume that a word is large enough to
+ hold any value so encoded; if it is smaller than a pointer on some target,
+ pointers should not be leb128 encoded on that target. */
+static unsigned char *
+read_uleb128 (unsigned char *p, unsigned long *val)
+{
+ unsigned int shift = 0;
+ unsigned char byte;
+ unsigned long result;
+
+ result = 0;
+ do
+{
+ byte = *p++;
+ result |= (byte & 0x7f) << shift;
+ shift += 7;
+}
+ while (byte & 0x80);
+
+ *val = result;
+ return p;
+}
+
+
+#define ATTR_TAG_FILE 1
+#define ABI_VFP_args 28
+#define VFP_ARGS_IN_VFP_REGS 1
+
+/* Check consistency of ABI in the ARM attributes. Search through the
+ section headers looking for the ARM attributes section, then
+ check the VFP_ARGS attribute. */
+static int
+check_arm_attributes_hfabi(int fd, ElfW(Ehdr) *ehdr, bool *is_hf)
+{
+ unsigned int i;
+ ElfW(Shdr) *shdrs;
+ int sh_size = ehdr->e_shentsize * ehdr->e_shnum;
+
+ /* Load in the section headers so we can look for the attributes
+ * section */
+ shdrs = alloca(sh_size);
+ __lseek (fd, ehdr->e_shoff, SEEK_SET);
+ if ((size_t) __libc_read (fd, (void *) shdrs, sh_size) != sh_size)
+return -1;
+
+ for (i = 0; i < ehdr->e_shnum; i++)
+{
+ if (SHT_ARM_ATTRIBUTES == shdrs[i].sh_type)
+{
+ /* We've found a likely section. Load the contents and
+ * check the tags */
+ unsigned char *contents = alloca(shdrs[i].sh_size);
+ unsigned char *p = contents;
+ unsigned char * end;
+
+ __lseek (fd, shdrs[i].sh_offset, SEEK_SET);
+ if ((size_t) __libc_read (fd, (void *) contents, shdrs[i].sh_size) !=
shdrs[i].sh_size)
+ return -1;
+
+ /* Sanity-check the attribute section details. Make sure
+ * that it's the "aeabi" section, that's all we care
+ * about. */
+ if (*p == 'A')
+{
+ unsigned long len = shdrs[i].sh_size - 1;
+ unsigned long namelen;
+ p++;
+
+ while (len > 0)
+{
+ unsigned long section_len = p[0] | p[1] << 8 | p[2] << 16 |
p[3] << 24;
+ if (section_len > len)
+{
+ _dl_debug_printf_c ("invalid section len %lu, max
remaining %lu\n", section_len, len);
+ section_len = len;
+}
+
+ p += 4;
+ len -= section_len;
+ section_len -= 4;
+
+ if (0 != strcmp((char *)p, "aeabi"))
+{
+ _dl_debug_printf_c ("ignoring unknown attr section
%s\n", p);
+ p += section_len;
+ continue;
+}
+ namelen = strlen((char *)p) + 1;
+ p += namelen;
+ section_len -= namelen;
+
+ /* We're in a valid section. Walk through this
+ * section looking for the tag we care about
+ * (ABI_VFP_args) */
+ while (section_len > 0)
+{
+ unsigned long val = 0;
+ unsigned long tag;
+ unsigned long size;
+
+ end = p;
+ tag = (*p++);
+
+ size = p[0] | p[1] << 8 | p[2] << 16 | p[3] << 24;
+ if (size > section_len)
+{
+ _dl_debug_printf_c ("invalid subsection length
%lu, max allowed %lu\n", size, section_len);
+ size = section_len;
+}
+ p += 4;
+
+ section_len -= size;
+ end += size;
+ if (ATTR_TAG_FILE != tag)
+{
+ /* ignore, we don't care */
+ _dl_debug_printf_c ("ignoring unknown subsection
with type %lu length %lu\n", tag, size);
+ p = end;
+ continue;
+}
+ while (p < end)
+{
+ p = read_uleb128 (p, );
+ /* Handle the different types of tag. */
+ if ( (tag == 4) || (tag == 5) || (tag == 67) )
+{
+ /*
[Bug 1822235] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux (Ubuntu Cosmic) 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/1822235 Title: All 29 tests in kvm-unit-test failed (timeouted) on i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1822235/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822235] [NEW] All 29 tests in kvm-unit-test failed (timeouted) on i386
Public bug reported: All the available tests in kvm-unit-test have failed on Cosmic i386 with node "onza". They all timeout with the default 90 second threshold. TESTNAME=smptest TIMEOUT=90s ACCEL= ./x86/run x86/smptest.flat -smp 2 FAIL smptest (timeout; duration=90s) TESTNAME=smptest3 TIMEOUT=90s ACCEL= ./x86/run x86/smptest.flat -smp 3 FAIL smptest3 (timeout; duration=90s) TESTNAME=vmexit_cpuid TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -append 'cpuid' FAIL vmexit_cpuid (timeout; duration=90s) TESTNAME=vmexit_vmcall TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -append 'vmcall' FAIL vmexit_vmcall (timeout; duration=90s) TESTNAME=vmexit_mov_from_cr8 TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -append 'mov_from_cr8' FAIL vmexit_mov_from_cr8 (timeout; duration=90s) TESTNAME=vmexit_mov_to_cr8 TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -append 'mov_to_cr8' FAIL vmexit_mov_to_cr8 (timeout; duration=90s) TESTNAME=vmexit_inl_pmtimer TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -append 'inl_from_pmtimer' FAIL vmexit_inl_pmtimer (timeout; duration=90s) TESTNAME=vmexit_ipi TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 2 -append 'ipi' FAIL vmexit_ipi (timeout; duration=90s) TESTNAME=vmexit_ipi_halt TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 2 -append 'ipi_halt' FAIL vmexit_ipi_halt (timeout; duration=90s) TESTNAME=vmexit_ple_round_robin TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -append 'ple_round_robin' FAIL vmexit_ple_round_robin (timeout; duration=90s) TESTNAME=vmexit_tscdeadline TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -cpu qemu64,+x2apic,+tsc-deadline -append tscdeadline FAIL vmexit_tscdeadline (timeout; duration=90s) TESTNAME=vmexit_tscdeadline_immed TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -cpu qemu64,+x2apic,+tsc-deadline -append tscdeadline_immed FAIL vmexit_tscdeadline_immed (timeout; duration=90s) TESTNAME=smap TIMEOUT=90s ACCEL= ./x86/run x86/smap.flat -smp 1 -cpu host FAIL smap (timeout; duration=90s) TESTNAME=eventinj TIMEOUT=90s ACCEL= ./x86/run x86/eventinj.flat -smp 1 FAIL eventinj (timeout; duration=90s) TESTNAME=hypercall TIMEOUT=90s ACCEL= ./x86/run x86/hypercall.flat -smp 1 FAIL hypercall (timeout; duration=90s) TESTNAME=msr TIMEOUT=90s ACCEL= ./x86/run x86/msr.flat -smp 1 FAIL msr (timeout; duration=90s) TESTNAME=port80 TIMEOUT=90s ACCEL= ./x86/run x86/port80.flat -smp 1 FAIL port80 (timeout; duration=90s) TESTNAME=realmode TIMEOUT=90s ACCEL= ./x86/run x86/realmode.flat -smp 1 FAIL realmode (timeout; duration=90s) TESTNAME=s3 TIMEOUT=90s ACCEL= ./x86/run x86/s3.flat -smp 1 FAIL s3 (timeout; duration=90s) TESTNAME=sieve TIMEOUT=90s ACCEL= ./x86/run x86/sieve.flat -smp 1 FAIL sieve (timeout; duration=90s) TESTNAME=tsc TIMEOUT=90s ACCEL= ./x86/run x86/tsc.flat -smp 1 -cpu kvm64,+rdtscp FAIL tsc (timeout; duration=90s) TESTNAME=tsc_adjust TIMEOUT=90s ACCEL= ./x86/run x86/tsc_adjust.flat -smp 1 -cpu host FAIL tsc_adjust (timeout; duration=90s) TESTNAME=taskswitch TIMEOUT=90s ACCEL= ./x86/run x86/taskswitch.flat -smp 1 FAIL taskswitch (timeout; duration=90s) TESTNAME=taskswitch2 TIMEOUT=90s ACCEL= ./x86/run x86/taskswitch2.flat -smp 1 FAIL taskswitch2 (timeout; duration=90s) TESTNAME=kvmclock_test TIMEOUT=90s ACCEL= ./x86/run x86/kvmclock_test.flat -smp 2 --append "1000 `date +%s`" FAIL kvmclock_test (timeout; duration=90s) TESTNAME=umip TIMEOUT=90s ACCEL= ./x86/run x86/umip.flat -smp 1 -cpu qemu64,+umip FAIL umip (timeout; duration=90s) TESTNAME=hyperv_synic TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev FAIL hyperv_synic (timeout; duration=90s) TESTNAME=hyperv_connections TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_connections.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev FAIL hyperv_connections (timeout; duration=90s) TESTNAME=hyperv_stimer TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_stimer.flat -smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev FAIL hyperv_stimer (timeout; duration=90s) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-16-generic 4.18.0-16.17 ProcVersionSignature: User Name 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 29 05:08 seq crw-rw 1 root audio 116, 33 Mar 29 05:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.2 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Fri Mar 29 05:09:30 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: Dell Inc. PowerEdge R310 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine:
[Bug 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected
I am using a Logitech M337 on Ubuntu 18.04 via Intel 8265 right now and cannot reproduce any bug. If the problem ever was specific to Intel 8265 then it might have been fixed in firmware updates already here: https://launchpad.net/ubuntu/+source/linux-firmware While comment #50 is interesting, I don't think it is relevant to this bug at all. And this bug doesn't seem to exist any more anyway. ** No longer affects: gnome-bluetooth (Ubuntu) ** Changed in: oem-priority 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/1773897 Title: [regression] Logitech M337 mice are automatically disconnected after connected To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1773897/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1362848] Re: black/blank screen and freeze at startup after installing nvidia driver (with hybrid graphic card)
** Changed in: nvidia-graphics-drivers-364 (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1362848 Title: black/blank screen and freeze at startup after installing nvidia driver (with hybrid graphic card) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331/+bug/1362848/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821724] Re: linux: 4.4.0-145.171 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819658 (trusty/linux-aws), bug 1819659 (trusty/linux-lts-xenial) derivatives: bug 1819654 (linux-euclid), bug 1820326 (linux-fips), bug 1821712 (linux-kvm), bug 1821713 (linux-raspi2), bug 1821723 (linux-snapdragon), bug 1821726 (linux-aws) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Wednesday, 27. March 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-candidate: Pending -- snap not in amd64:latest/candidate,i386:latest/candidate + snap-release-to-candidate: Pending -- snap not in i386:latest/candidate,amd64:latest/candidate channel verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821724 Title: linux: 4.4.0-145.171 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1821724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576859] Re: [nvidia] Graphics corruption when resuming from suspend
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 > IIRC I asked for all the bug reports that I made to be closed OK we will use bug 1809407 instead. Aside from anything else, JournalErrors.txt above is showing this bug is from Nvidia driver version 364.19 which doesn't seem to have ever been officially released so is not supported: https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-364 But regardless of the driver version, Nvidia is closed source so neither Canonical nor the community have any power to fix it. We can only track its bugs. ** This bug has been marked a duplicate of bug 1809407 [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576859 Title: [nvidia] Graphics corruption when resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1576859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809407] Re: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-418 (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/1809407 Title: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809407] Re: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm3 (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/1809407 Title: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809407] Re: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything.
** This bug is no longer a duplicate of bug 1576859 [nvidia] Graphics corruption when resuming from suspend -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809407 Title: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809407] Re: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything.
** No longer affects: gdm3 (Ubuntu) ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Tags added: disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809407 Title: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809407] Re: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything.
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1809407 Title: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809407] Re: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-390 (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/1809407 Title: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822230] Re: lubuntu 19.04 install dual screen; login user/password boxes on both displays allowing password entry
I added all updates, did a reboot & same cosmetic issue remained. I've also just done a no-internet install now (lubuntu 19.04 checklist); with me resisting the urge to correct screen orientation this time. Identical issue on no-network install; without any changes to screen setup from default. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822230 Title: lubuntu 19.04 install dual screen; login user/password boxes on both displays allowing password entry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1822230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822179] Re: Resuming from sleep breaks desktop and lock screen background in GNOME
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 ** This bug is no longer a duplicate of bug 1576859 [nvidia] Graphics corruption when resuming from suspend ** This bug has been marked a duplicate of bug 1809407 [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822179 Title: Resuming from sleep breaks desktop and lock screen background in GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822179/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809407] Re: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything.
** Also affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-418 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809407 Title: [nvidia] After resume the unlock screen is a black background with pixel garbage. Bitmap garbage flashes on the screen when interacting with anything. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818690] Re: Touchpad not detected
Possible to find the exact "i8042.*" that makes it work? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818690 Title: Touchpad not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822184] Re: clear_console locks up video when X is running and you log out from a plain text console
** Changed in: xorg-server Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822184 Title: clear_console locks up video when X is running and you log out from a plain text console To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1822184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822233] Re: package shim-signed 1.38+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1
Thank you for taking the time to report this problem and help to improve Ubuntu. Unfortunately, the DpkgTerminalLog.txt that was attached to your bug report includes no output from the attempt to install the shim-signed package, so it is impossible to diagnose this problem. Please check /var/log/apt/term.log on your system for information about the failure to install the shim-signed package, and if information is present, please attach it to this bug report. ** Changed in: shim-signed (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/1822233 Title: package shim-signed 1.38+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1822233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821972] Re: Installation error with Ununty Server 18.04 LTS - curthooks
** Package changed: shim-signed (Ubuntu) => efibootmgr (Ubuntu) ** Also affects: curtin (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821972 Title: Installation error with Ununty Server 18.04 LTS - curthooks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1821972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822234] [NEW] hard drive will not allow me to DL due to age or issue
Public bug reported: trying to download ubuntu budgie my pc stated it was unable to finish ddue to old HDD or corrupt HDD ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.12 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CasperVersion: 1.394 Date: Thu Mar 28 21:22:03 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-budgie.seed boot=casper quiet splash --- LiveMediaBuild: Ubuntu-Budgie 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.12 ubuntu-budgie -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822234 Title: hard drive will not allow me to DL due to age or issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1822234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822233] Re: package shim-signed 1.38+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1
Thank you for taking the time to report this problem and help to improve Ubuntu. Unfortunately, the DpkgTerminalLog.txt that was attached to your bug report includes no output from the attempt to install the shim-signed package, so it is impossible to diagnose this problem. Please check /var/log/apt/term.log on your system for information about the failure to install the shim-signed package, and if information is present, please attach it to this bug report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822233 Title: package shim-signed 1.38+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1822233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818766] Re: Update to 1.47
Now I double check snapd-glib is not published in 18.04 yet - I must have tested the locally installed version. Will retest when published. ** Tags removed: verification-done-bionic ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818766 Title: Update to 1.47 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1818766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818811] Re: The swapfile on the Btrfs file system is not activated
Does "sudo chattr +C /swapfile" help? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818811 Title: The swapfile on the Btrfs file system is not activated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814481] Re: bluetooth keyboard not working
So it's not a kernel bug. I am not sure which update fixed it though... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814481 Title: bluetooth keyboard not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1046548] Re: epiphany-browser crashed with SIGABRT in g_assertion_message()
[Expired for epiphany-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: epiphany-browser (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/1046548 Title: epiphany-browser crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1046548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 976648] Re: epiphany-browser crashed with SIGSEGV
[Expired for epiphany-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: epiphany-browser (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/976648 Title: epiphany-browser crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/976648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 974924] Re: epiphany-browser crashed with SIGSEGV
[Expired for epiphany-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: epiphany-browser (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/974924 Title: epiphany-browser crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/974924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1000518] Re: epiphany-browser crashed with SIGSEGV in g_unix_fd_message_append_fd()
[Expired for epiphany-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: epiphany-browser (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/1000518 Title: epiphany-browser crashed with SIGSEGV in g_unix_fd_message_append_fd() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1000518/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1309095] Re: Epiphany parou de responder
[Expired for epiphany-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: epiphany-browser (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/1309095 Title: Epiphany parou de responder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1309095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772374] Re: ubiquity need mount point /sys/firmware/efi/efivars
** Changed in: oem-priority Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772374 Title: ubiquity need mount point /sys/firmware/efi/efivars To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1772374/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812918] Re: Bose QC35 bluetooth audio cuts out and is disjoined in 18.04
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (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/1812918 Title: Bose QC35 bluetooth audio cuts out and is disjoined in 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1812918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813505] Re: package shim-signed 1.37~18.04.3+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit statu
[Expired for shim-signed (Ubuntu) because there has been no activity for 60 days.] ** Changed in: shim-signed (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/1813505 Title: package shim-signed 1.37~18.04.3+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1813505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813352] Re: confined applications show as unconfined
[Expired for gnome-software (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-software (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/1813352 Title: confined applications show as unconfined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1813352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812918] Re: Bose QC35 bluetooth audio cuts out and is disjoined in 18.04
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (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/1812918 Title: Bose QC35 bluetooth audio cuts out and is disjoined in 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1812918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576859] Re: [nvidia] Graphics corruption when resuming from suspend
Seriously, what the actual fuck? This bug(and others!) was reported 3 goddamn years ago and you people are still resurrecting it by adding useless tags that in no shape or form help the problem getting solved. If you have no interest in actually fixing the issue then mark it as "won't fix" and let it die since there is clearly *NO* intention of EVER fixing it. Ubuntu is a buggy pile of bovine manure and Canonical and related community members seem to have little to no interest in changing that. I installed Ubuntu 18.04 LTS only to instantly run into a bug where the launcher would appear on the lock screen and being completely functional. How the actual fuck did that not get fixed in the beta? IIRC I asked for all the bug reports that I made to be closed since -despite being mostly critical- they were never going to be fixed. If no one at canonical or the surrounding community can at least have the decency to try to fix *CRITICAL* bugs in the software in their distro then at least have the decency to not resurrect *YEARS OLD* dead bug reports that will never get fixed. I'm not asking much here. inb4 "Ubuntu is a community project and relies on community volunteers" Sorry, you don't get to use that defense after shouting from the rooftops how (metaphorically) big your dicks are compared to the competition. You want to be a big boy OS? Start actually supporting your distro. There is ZERO reason why an LTS distro should have critical -easy-to-run-into bugs 6 months after it's release(looking at you Ubuntu Gnome, but much probably applies to standard Ubuntu). You drop a deuce of a distro release and then drop another 6 months later. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576859 Title: [nvidia] Graphics corruption when resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1576859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821709] Re: Ubuntu 19.04 breaks grub keyboard input on XPS 15
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: grub2 (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/1821709 Title: Ubuntu 19.04 breaks grub keyboard input on XPS 15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1821709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819623] Re: linux-hwe: 4.18.0-17.18~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1819622 (linux-hwe-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1819624 phase: Testing phase-changed: Monday, 18. March 2019 16:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819623 Title: linux-hwe: 4.18.0-17.18~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822230] Re: lubuntu 19.04 install dual screen; login user/password boxes on both displays allowing password entry
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1822230 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822230 Title: lubuntu 19.04 install dual screen; login user/password boxes on both displays allowing password entry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1822230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822233] [NEW] package shim-signed 1.38+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1
Public bug reported: I were installing the ubuntu pack language. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: shim-signed 1.38+15+1533136590.3beb971-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: wl .proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No existe el archivo o el directorio: '/proc/sys/kernel/moksbstate_disabled' ApportVersion: 2.20.10-0ubuntu13 AptOrdering: shim:amd64: Install shim-signed:amd64: Install NULL: ConfigurePending Architecture: amd64 BootEFIContents: BOOTX64.CSV grub.cfg grubx64.efi mmx64.efi shimx64.efi Date: Thu Mar 28 21:43:10 2019 EFITables: mar 28 15:52:29 mainor-HP-Notebook kernel: efi: EFI v2.40 by INSYDE Corp. mar 28 15:52:29 mainor-HP-Notebook kernel: efi: SMBIOS=0x9c0ef000 ESRT=0x9c1fb018 ACPI 2.0=0x9cffd014 TPMEventLog=0x81b95018 mar 28 15:52:29 mainor-HP-Notebook kernel: secureboot: Secure boot enabled mar 28 15:52:29 mainor-HP-Notebook kernel: esrt: Reserving ESRT space from 0x9c1fb018 to 0x9c1fb050. mar 28 21:54:40 mainor-HP-Notebook fwupd[4883]: disabling plugin because: failed to startup dell_esrt: UEFI firmware already supported ErrorMessage: installed shim-signed package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-03-29 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SecureBoot: 6 0 0 0 1 SourcePackage: shim-signed Title: package shim-signed 1.38+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822233 Title: package shim-signed 1.38+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1822233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819716] Re: linux: 4.15.0-47.50 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819713 (xenial/linux-azure), bug 1819715 (xenial/linux-hwe) derivatives: bug 1819691 (linux-raspi2), bug 1819692 (linux-oem), bug 1819694 (linux-aws), bug 1819698 (linux-gcp), bug 1819699 (linux-kvm), bug 1819701 (linux-ibm-gt), bug 1819704 (linux-oracle), bug 1819707 (linux-fips), bug 1822167 (linux) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Friday, 15. March 2019 23:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819716 Title: linux: 4.15.0-47.50 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821724] Re: linux: 4.4.0-145.171 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819658 (trusty/linux-aws), bug 1819659 (trusty/linux-lts-xenial) derivatives: bug 1819654 (linux-euclid), bug 1820326 (linux-fips), bug 1821712 (linux-kvm), bug 1821713 (linux-raspi2), bug 1821723 (linux-snapdragon), bug 1821726 (linux-aws) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Wednesday, 27. March 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-candidate: Pending -- snap not in i386:latest/candidate,amd64:latest/candidate + snap-release-to-candidate: Pending -- snap not in amd64:latest/candidate,i386:latest/candidate channel verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821724 Title: linux: 4.4.0-145.171 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1821724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819623] Re: linux-hwe: 4.18.0-17.18~18.04.1 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru- testing/bionic/4.18.0-17.18~18.04.1/bionic-4.18-proposed-published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing 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/1819623 Title: linux-hwe: 4.18.0-17.18~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819623/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818766] Re: Update to 1.47
Correction gnome-initial-setup is on 18.10 - tested this and it is showing promoted snaps with updated snapd-glib. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818766 Title: Update to 1.47 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1818766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818766] Re: Update to 1.47
Tested snapd-glib 1.47-0ubuntu0.18.04.0 in Ubuntu 18.104 LTS (bionic). GNOME software able to install/remove/launch snaps (moon-buggy tested), pulse audio still working, gnome-initial-setup showing promoted snaps. ** 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/1818766 Title: Update to 1.47 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1818766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1787775] Re: touchpad not working on lenovo yoga 530
The driver has landed to upstream, I'll build a test kernel to let everyone verify. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1787775 Title: touchpad not working on lenovo yoga 530 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822184] Re: clear_console locks up video when X is running and you log out from a plain text console
** Changed in: xorg-server (Debian) Status: Unknown => Confirmed ** Changed in: xorg (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822184 Title: clear_console locks up video when X is running and you log out from a plain text console To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1822184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822095] Re: [SRU] chktex FTBFS with TeX-Live 2018
** Changed in: chktex (Debian) 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/1822095 Title: [SRU] chktex FTBFS with TeX-Live 2018 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chktex/+bug/1822095/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820695] Re: 5.0.0 kernels (5.0.0-7 and 5.0.0-8) don't boot
A reverse bisection to find which commit between 5.0 and 5.1-rc1 fixes the issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820695 Title: 5.0.0 kernels (5.0.0-7 and 5.0.0-8) don't boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820695/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822043] Re: as enrolling mok, the font is too small in hi-dpi monitor
MokManager only uses the UEFI console interface. If the UEFI text console API renders text too small to be legible, I think that should be considered a bug in the UEFI implementation, not a bug in MokManager. ** Summary changed: - as enrolling mok, the font is too samll in hi-dpi monitor + as enrolling mok, the font is too small in hi-dpi monitor -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822043 Title: as enrolling mok, the font is too small in hi-dpi monitor To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1822043/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818766] Re: Update to 1.47
Tested snapd-glib 1.47-0ubuntu0.18.10.0 in Ubuntu 18.10 (cosmic). GNOME software able to install/remove/launch snaps (moon-buggy tested), pulse audio still working, gnome-initial-setup not present on this system. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818766 Title: Update to 1.47 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1818766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819716] Re: linux: 4.15.0-47.50 -proposed tracker
Hardware Certification have completed testing this -proposed kernel. No regressions were observed, results are available here: http://people.canonical.com/~hwcert/sru-testing/bionic/4.15.0-47.50 /bionic-proposed-published.html ** Tags added: certification-testing-passed ** Changed in: kernel-sru-workflow/certification-testing 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/1819716 Title: linux: 4.15.0-47.50 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1819716/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822026] Re: [Dell Precision with Nvidia Quadro P1000] Live USB freezes or cannot complete install when nouveau driver is loaded (crashing in GP100 code)
** Summary changed: - Live USB freezes or cannot complete install when nouveau driver is loaded (crashing in GP100 code) + [Dell Precision with Nvidia Quadro P1000] Live USB freezes or cannot complete install when nouveau driver is loaded (crashing in GP100 code) ** Summary changed: - [Dell Precision with Nvidia Quadro P1000] Live USB freezes or cannot complete install when nouveau driver is loaded (crashing in GP100 code) + [Dell Precision 7530/5530 with Nvidia Quadro P1000] Live USB freezes or cannot complete install when nouveau driver is loaded (crashing in GP100 code) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822026 Title: [Dell Precision 7530/5530 with Nvidia Quadro P1000] Live USB freezes or cannot complete install when nouveau driver is loaded (crashing in GP100 code) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818881] Re: ath10k_pci crashing
dmi.product.name: XPS 13 9380? If it's not enough we should let apport-collect collect more info. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818881 Title: ath10k_pci crashing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822230] [NEW] lubuntu 19.04 install dual screen; login user/password boxes on both displays allowing password entry
Public bug reported: Lubuntu 19.04 (x86_64) QA-Test install dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) On first boot, i expected to see (on either display) a single login box for username/password. Instead I got a box on each display (as if mirrored) but noted the password was only appearing as dots on one screen. With experimentation, I can enter different passwords on each display - if I press whilst inside the valid-password box I get logged in, if I press on an invalid password screen (with valid password on the other screen) I get login failed correctly. As such I don't see how this could be mis-used, but it is a little confusing/distracting, but minor. After login, if I logout I get the same two user/boxes allowing different entry in each. At this time I have not rebooted; it's still initial boot (post-install) My displays are differently aligned to the default; but this occurred on reboot before any adjustments were made to displays (to match my having one tilted-left so portrait mode etc) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: sddm 0.18.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: LXQt Date: Fri Mar 29 14:26:22 2019 InstallationDate: Installed on 2019-03-29 (0 days ago) InstallationMedia: Lubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) SourcePackage: sddm UpgradeStatus: No upgrade log present (probably fresh install) -- The following (snippet) is from my QA-test comments --- (between steps 2 & 3 I had to use lxqt.prefs-monitor.settings to adjust my display to match portrait & my display organization for the little sanity i have left..) // maybe the display change caused this??? I forgot I did that... I'll add comment on https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1822230 --- Could it be that the LXQt.Prefs -> Monitor.Settings change I made before install impacted this?? Even if this change has caused issue, it shouldn't... ** Affects: sddm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Attachment added: "sudo lshw >~/lshw.txt" https://bugs.launchpad.net/bugs/1822230/+attachment/5250382/+files/lshw.txt ** Description changed: Lubuntu 19.04 (x86_64) QA-Test install dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 5000/6000/7350/8350) On first boot, i expected to see (on either display) a single login box for username/password. Instead I got a box on each display (as if mirrored) but noted the password was only appearing as dots on one screen. With experimentation, I can enter different passwords on each display - if I press whilst inside the valid-password box I get logged in, if I press on an invalid password screen (with valid password on the other screen) I get login failed correctly. As such I don't see how this could be mis-used, but it is a little confusing/distracting, but minor. After login, if I logout I get the same two user/boxes allowing different entry in each. At this time I have not rebooted; it's still initial boot (post-install) My displays are differently aligned to the default; but this occurred on reboot before any adjustments were made to displays (to match my having one tilted-left so portrait mode etc) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: sddm 0.18.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: LXQt Date: Fri Mar 29 14:26:22 2019 InstallationDate: Installed on 2019-03-29 (0 days ago) InstallationMedia: Lubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) SourcePackage: sddm UpgradeStatus: No upgrade log present (probably fresh install) + + -- + The following (snippet) is from my QA-test comments + --- + (between steps 2 & 3 I had to use lxqt.prefs-monitor.settings to adjust my display to match portrait & my display organization for the little sanity i have left..) + // maybe the display change caused this??? I forgot I did that... I'll add comment on https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1822230 + --- + + Could it be that the LXQt.Prefs -> Monitor.Settings change I made before install impacted this?? + Even if this change has caused issue, it shouldn't... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822230 Title: lubuntu 19.04 install dual screen; login user/password boxes on both displays allowing password entry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1822230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822072] Re: User selector doesn't have focus from login screen after screen turned off
** No longer affects: gnome-shell -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822072 Title: User selector doesn't have focus from login screen after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821426] Re: [nvidia] Ubuntu 19.14 disco will not boot on Dell Precision5530
*** This bug is a duplicate of bug 1822026 *** https://bugs.launchpad.net/bugs/1822026 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1822026, so it 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. Feel free to continue to report any other bugs you may find. ** Summary changed: - Ubuntu 19.14 disco will not boot on Dell Precision5530 + [nvidia] Ubuntu 19.14 disco will not boot on Dell Precision5530 ** Tags added: nvidia ** Summary changed: - [nvidia] Ubuntu 19.14 disco will not boot on Dell Precision5530 + Ubuntu 19.14 disco will not boot on Dell Precision 5530 with Quadro P1000 Mobile ** Summary changed: - Ubuntu 19.14 disco will not boot on Dell Precision 5530 with Quadro P1000 Mobile + Ubuntu 19.04 disco will not boot on Dell Precision 5530 with Quadro P1000 Mobile ** This bug has been marked a duplicate of bug 1822026 [Dell Precision 7530/5530 with Nvidia Quadro P1000] Live USB freezes or cannot complete install when nouveau driver is loaded (crashing in GP100 code) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821426 Title: Ubuntu 19.04 disco will not boot on Dell Precision 5530 with Quadro P1000 Mobile To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1821426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822184] Re: clear_console locks up video when X is running and you log out from a plain text console
** Bug watch added: Debian Bug tracker #866898 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866898 ** Also affects: xorg (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866898 Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #810660 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810660 ** Also affects: xorg-server (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810660 Importance: Unknown Status: Unknown ** Bug watch added: gitlab.freedesktop.org/xorg/xserver/issues #492 https://gitlab.freedesktop.org/xorg/xserver/issues/492 ** Also affects: xorg-server via https://gitlab.freedesktop.org/xorg/xserver/issues/492 Importance: Unknown Status: Unknown ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: bash (Ubuntu) Status: Confirmed => Opinion ** Changed in: xorg-server (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/1822184 Title: clear_console locks up video when X is running and you log out from a plain text console To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1822184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821724] Re: linux: 4.4.0-145.171 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819658 (trusty/linux-aws), bug 1819659 (trusty/linux-lts-xenial) derivatives: bug 1819654 (linux-euclid), bug 1820326 (linux-fips), bug 1821712 (linux-kvm), bug 1821713 (linux-raspi2), bug 1821723 (linux-snapdragon), bug 1821726 (linux-aws) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Wednesday, 27. March 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-candidate: Pending -- snap not in amd64:latest/candidate,i386:latest/candidate + snap-release-to-candidate: Pending -- snap not in i386:latest/candidate,amd64:latest/candidate channel verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821724 Title: linux: 4.4.0-145.171 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1821724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818881] Re: ath10k_pci crashing
@sfabel thanks for your report. Do you convenient help to get sosreport for us to clarify which generation of xps 13 for this issue? The steps of getting sosreport is: 1. sudo apt-get install sosreport 2. sudo sosreport --batch --case-id xps13 3. upload the tarball generated here -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818881 Title: ath10k_pci crashing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818881/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821426] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1821426/+attachment/5250380/+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/1821426 Title: Ubuntu 19.14 disco will not boot on Dell Precision5530 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1821426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818766] Re: Update to 1.47
Test packages now accepted and 1.47 is available in -proposed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818766 Title: Update to 1.47 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1818766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820850] Re: [FFe] Distro patch GNOME hi-dpi support for x11 sessions
This bug was fixed in the package mutter - 3.32.0-1ubuntu1 --- mutter (3.32.0-1ubuntu1) disco; urgency=medium * debian/control: - Update VCS flags to point to launchpad - Update maintainer to ubuntu * debian/gbp.conf: update branch to point to ubuntu/master * debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch: - X11: Add support for fractional scaling using Randr (LP: #1820850) -- Marco Trevisan (Treviño) Wed, 27 Mar 2019 06:48:11 +0100 ** Changed in: mutter (Ubuntu) Status: Triaged => Fix Released ** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820850 Title: [FFe] Distro patch GNOME hi-dpi support for x11 sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1820850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821426] Re: Ubuntu 19.14 disco will not boot on Dell Precision5530
apport information ** Tags added: apport-collected disco ** Description changed: I'm uncertain which package is causing the problem, though I strongly suspect it may be nvidia related. This laptop runs 18.10 just fine, but attempting to boot 19.04 from a USB disk (tried multiple USB boot disks) results in a blank screen after Grub. The video will go between black with back light and black without back light. I cannot switch to a TTY, I cannot get further, keyboard seems to respond (lights up when keys are pressed). Additionally, when trying to upgrade from 18.10 the same result happens. After running the upgrade and rebooting, I cannot get it to boot unless I first start in recovery mode from grub. After that I can get to the desktop (nouveau driver seems to be installed by default). Any attempt to boot normally results in a black screen. Attempting to switch to proprietary nvidia driver results in never getting the luks screen (encrypted disk). I get no luks screen when booting normally either. lspci 00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07) 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07) 00:02.0 VGA compatible controller: Intel Corporation Device 3e9b 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 07) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10) 00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) 00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10) 00:15.0 Serial bus controller [0c80]: Intel Corporation Device a368 (rev 10) 00:15.1 Serial bus controller [0c80]: Intel Corporation Device a369 (rev 10) 00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10) 00:17.0 SATA controller: Intel Corporation Device a353 (rev 10) 00:1b.0 PCI bridge: Intel Corporation Device a340 (rev f0) 00:1c.0 PCI bridge: Intel Corporation Device a338 (rev f0) 00:1c.4 PCI bridge: Intel Corporation Device a33c (rev f0) 00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port 9 (rev f0) 00:1f.0 ISA bridge: Intel Corporation Device a30e (rev 10) 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10) 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10) 01:00.0 3D controller: NVIDIA Corporation GP107GLM [Quadro P1000 Mobile] (rev a1) 3b:00.0 Network controller: Intel Corporation Wireless-AC 9260 (rev 29) 3c:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader (rev 01) 3d:00.0 Non-Volatile memory controller: Toshiba America Info Systems Device 011a + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu23 + Architecture: amd64 + CasperVersion: 1.402 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.04 + LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) + Package: gnome-shell + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 + Tags: disco + Uname: Linux 5.0.0-7-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + mtime.conffile..etc.gdm3.custom.conf: 2019-03-29T03:07:48.704000 ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1821426/+attachment/5250379/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821426 Title: Ubuntu 19.14 disco will not boot on Dell Precision5530 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1821426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822037] Re: Click the lock screen button, no response
This bug was fixed in the package ukui-screensaver - 2.0.5-0ubuntu1 --- ukui-screensaver (2.0.5-0ubuntu1) disco; urgency=medium * Bugfix only: - Fix the wrong activated condition. (LP: #1822037) -- handsome_feng Thu, 28 Mar 2019 16:38:31 +0800 ** Changed in: ukui-screensaver (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/1822037 Title: Click the lock screen button, no response To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1822037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820850] Re: [FFe] Distro patch GNOME hi-dpi support for x11 sessions
This bug was fixed in the package gnome-control-center - 1:3.32.0.1-1ubuntu6 --- gnome-control-center (1:3.32.0.1-1ubuntu6) disco; urgency=medium * debian/patches/display-Don-t-always-set-the-primary-monitor-to-the-first.patch: - Make sure the display panel primary monitor matches configured one * debian/patches/display-Support-UI-scaled-logical-monitor-mode.patch: - Support scaled logical monitors using UI scale as it could happen when using the X11 Randr scaling (LP: #1820850) -- Marco Trevisan (Treviño) Wed, 27 Mar 2019 06:10:59 +0100 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820850 Title: [FFe] Distro patch GNOME hi-dpi support for x11 sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1820850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822072] Re: User selector doesn't have focus from login screen after screen turned off
** Changed in: gnome-shell Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822072 Title: User selector doesn't have focus from login screen after screen turned off To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1822072/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821426] modified.conffile..etc.gdm3.custom.conf.txt
apport information ** Attachment added: "modified.conffile..etc.gdm3.custom.conf.txt" https://bugs.launchpad.net/bugs/1821426/+attachment/5250381/+files/modified.conffile..etc.gdm3.custom.conf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821426 Title: Ubuntu 19.14 disco will not boot on Dell Precision5530 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1821426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822228] [NEW] ubuntu 14.04 - could not install "text-common"
Public bug reported: I was ugrading to ubuntu 14.04 but the system had an error stating that it could not install "tex-common" or that the package was not in a working state.? How do I fix this problem please? ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/188 Title: ubuntu 14.04 - could not install "text-common" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821426] Re: Ubuntu 19.14 disco will not boot on Dell Precision5530
I can get to the desktop by adding nomodeset Tried it on the latest 19.04 from 3/26 Without nomodeset it continues its flashing black screen However it reports as "unknown display" and I can not get it to detect an external display. Attaching the apport-collect but it is from a live disk, I'm not sure if that'll be helpful. Unfortunately I cannot install ubuntu 19.04 at this time because I need use of the computer which works fine under 18.10. It looks like I cannot disable the GPU in BIOS on this machine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821426 Title: Ubuntu 19.14 disco will not boot on Dell Precision5530 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1821426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821261] Re: nfsiostat broken and exits with traceback
Attached is the debdiff for nfs-utils for cosmic. Please SRU once disco package is released. ** Patch added: "nfs-utils debdiff for cosmic" https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1821261/+attachment/5250377/+files/lp1821261-cosmic.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821261 Title: nfsiostat broken and exits with traceback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1821261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821261] Re: nfsiostat broken and exits with traceback
Attached is the debdiff for nfs-utils for bionic. Please SRU once disco package has been released. ** Patch added: "nfs-utils debdiff for bionic" https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1821261/+attachment/5250378/+files/lp1821261-bionic.debdiff ** Tags added: sts-sponsor -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821261 Title: nfsiostat broken and exits with traceback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1821261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821261] Re: nfsiostat broken and exits with traceback
Builds have been done in a ppa, and can be pulled for testing here: https://launchpad.net/~mruffell/+archive/ubuntu/nfs-utils-testing autopkgtests pass for all builds. ** Description changed: - nfsiostat, in nfs-common-1.3.4-2, is broken in bionic, cosmic and disco. + [Impact] - When you run the command nfsiostat, either as root or a regular user, + * nfsiostat, in nfs-common-1.3.4-2, is broken in bionic, cosmic and + disco. + + * nfsiostat will not run at all, and is unusuable when users run the + command. Users should be able to run the command and see output of their + nfs mounts. + + * The bug is caused by the 'list' reserved word being used as a + variable name in list_nfs_mounts(), and is explained here: + https://askubuntu.com/questions/1123319/nfsiostat-failing- + on-18-04/1123336#1123336?s=a1e9150fbf284e849efe6fe084e7c7b8 + + [Test Case] + + * When you run the command nfsiostat, either as root or a regular user, the following traceback is printed: $ nfsiostat Traceback (most recent call last): - File "/usr/sbin/nfsiostat", line 640, in - iostat_command(prog) - File "/usr/sbin/nfsiostat", line 593, in iostat_command - devices = list_nfs_mounts(origdevices, mountstats) - File "/usr/sbin/nfsiostat", line 495, in list_nfs_mounts - for device, descr in list(mountstats.items()): + File "/usr/sbin/nfsiostat", line 640, in + iostat_command(prog) + File "/usr/sbin/nfsiostat", line 593, in iostat_command + devices = list_nfs_mounts(origdevices, mountstats) + File "/usr/sbin/nfsiostat", line 495, in list_nfs_mounts + for device, descr in list(mountstats.items()): TypeError: 'list' object is not callable - This is caused by the 'list' reserved word being used as a variable name - in list_nfs_mounts(), and is explained here: - https://askubuntu.com/questions/1123319/nfsiostat-failing- - on-18-04/1123336#1123336?s=a1e9150fbf284e849efe6fe084e7c7b8 + * Instead, the correct behaviour is not crash, and do something like the + following on a system with no current nfs mounts: - I will send a patch to upstream shortly. + $ nfsiostat + No NFS mount points were found + + [Regression Potential] + + * There is only one file modified, which is the nfsiostat python + script. There is no other changes to any other executable in the + package. Since nfsiostat was in complete failure before, the fix makes + it work again, there should not be any cause for concern regarding + regressions. + + * In the event of a regression, worst case scenario is that users are impacted in getting the status of their nfs mounts, while still being able to freely mount and use such devices, since they are handled by other packages. + + * I have built and tested all versions of packages in a ppa, which you can find here: + https://launchpad.net/~mruffell/+archive/ubuntu/nfs-utils-testing + + [Other Info] + + * The impacted code is present in xenial and trusty, since it was merged into upstream in 2009. However, due to how the function works, the program executes fine and does not crash. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821261 Title: nfsiostat broken and exits with traceback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1821261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821194] Re: [nvidia] Screen frozen after switch to other tty and do login & logout
*** This bug is a duplicate of bug 1822184 *** https://bugs.launchpad.net/bugs/1822184 Updates from bug 1804607, this is a known xorg issue and duplicates bug 1822184 that can be worked around by disable clear_console in the $HOME/.bash_logout: $ cat $HOME/.bash_logout # ~/.bash_logout: executed by bash(1) when login shell exits. # when leaving the console clear the screen to increase privacy if [ "$SHLVL" = 1 ]; then # [ -x /usr/bin/clear_console ] && /usr/bin/clear_console -q fi ** This bug has been marked a duplicate of bug 1822184 clear_console locks up video when X is running and you log out from a plain text console -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821194 Title: [nvidia] Screen frozen after switch to other tty and do login & logout To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1821194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821261] Re: nfsiostat broken and exits with traceback
Attached is the debdiff for nfs-utils in disco. ** Patch added: "nfs-utils debdiff for disco" https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1821261/+attachment/5250376/+files/lp1821261-disco.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821261 Title: nfsiostat broken and exits with traceback To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1821261/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822184] Re: clear_console locks up video when X is running and you log out from a plain text console
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bash (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/1822184 Title: clear_console locks up video when X is running and you log out from a plain text console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1822184/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1761379] Comment bridged from LTC Bugzilla
--- Comment From grom...@br.ibm.com 2019-03-28 23:03 EDT--- (In reply to comment #38) > Can you try the kernel at ppa:cascardo/linux, and see if that works for you? Hi Cascardo. It looks good. I'm able to get a jit profile using the agent found in linux-tools-5.0.0-8-generic with: $ sudo perf record -k 1 -e instructions:u ./java -agentpath:/usr/lib/linux-tools-5.0.0-8/libperf-jvmti.so crc32 $ sudo perf inject -i ./perf.data -j -o ./perf.data.jitted $ sudo perf report -f -i ./perf.data.jitted Thank you. Cheers, Gustavo -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1761379 Title: [18.04/18.10] File libperf-jvmti.so is missing in linux-tools-common deb on Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1761379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821724] Re: linux: 4.4.0-145.171 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1819658 (trusty/linux-aws), bug 1819659 (trusty/linux-lts-xenial) derivatives: bug 1819654 (linux-euclid), bug 1820326 (linux-fips), bug 1821712 (linux-kvm), bug 1821713 (linux-raspi2), bug 1821723 (linux-snapdragon), bug 1821726 (linux-aws) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Wednesday, 27. March 2019 12:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-candidate: Pending -- snap not in i386:latest/candidate,amd64:latest/candidate + snap-release-to-candidate: Pending -- snap not in amd64:latest/candidate,i386:latest/candidate channel verification-testing: Ongoing -- testing in progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821724 Title: linux: 4.4.0-145.171 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1821724/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822225] [NEW] package python-mysql.connector 2.1.6-1 failed to install/upgrade: installed python-mysql.connector package post-installation script subprocess returned error exit status 1
Public bug reported: for my laptop security ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python-mysql.connector 2.1.6-1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Mar 28 17:34:15 2019 Dependencies: ErrorMessage: installed python-mysql.connector package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-03-09 (385 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.3 SourcePackage: mysql-connector-python Title: package python-mysql.connector 2.1.6-1 failed to install/upgrade: installed python-mysql.connector package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-connector-python (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/185 Title: package python-mysql.connector 2.1.6-1 failed to install/upgrade: installed python-mysql.connector package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-connector-python/+bug/185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822225] Re: package python-mysql.connector 2.1.6-1 failed to install/upgrade: installed python-mysql.connector package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/185 Title: package python-mysql.connector 2.1.6-1 failed to install/upgrade: installed python-mysql.connector package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-connector-python/+bug/185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576859] Re: [nvidia] Graphics corruption when resuming from suspend
Status changed to 'Confirmed' because the bug affects multiple users. ** 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/1576859 Title: [nvidia] Graphics corruption when resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1576859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576859] Re: [nvidia] Graphics corruption when resuming from suspend
** Tags added: 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/1576859 Title: [nvidia] Graphics corruption when resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1576859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758544] Re: [nvidia] On resume, a black screen delays login screen
** Summary changed: - On unsuspend, a black screen delays login screen + [nvidia] On resume, a black screen delays login screen -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758544 Title: [nvidia] On resume, a black screen delays login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1758544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817817] Re: To add power setting bin file for SAR support (QCA6174)
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority 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/1817817 Title: To add power setting bin file for SAR support (QCA6174) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1817817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
