Re: [Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
On 2019-05-21 05:28:18, Mark wrote: > > If that doesn't work, can you try to boot with 'mitigations=off' > > passed on the kernel command line? > > on the other hand, mitigations=off did cut it! > I guess now we're to find which of the mitigations is causing it? Do > you have a hint? Which are all the params for turning kernel > mitigations,please? Oh, that is interesting. On an Intel processor, mitigations=off is equivalent to these options: nopti nospectre_v2 spectre_v2_user=off spec_store_bypass_disable=off l1tf=off mds=off So, if you could cycle through those options individually to identify which one allows you to boot, I think it would really help a lot in getting better information to Intel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
PS, #dmesg | grep microcode # returns nothing on the ubuntu hwe-edge kernel with mitigations=off (=problematic ucode otherwise loaded) Actually, is the microcode loaded at all? # cat /sys/devices/system/cpu/cpu0/microcode/version cat: /sys/devices/system/cpu/cpu0/microcode/version: No such file or directory # uname -a Linux mmm-U2442 5.0.0-15-generic #16~18.04.1-Ubuntu SMP Tue May 7 14:17:37 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@mmm-U2442:~# dmesg |grep -i microcode # apt list --installed |grep microcode amd64-microcode/bionic-updates,now 3.20180524.1~ubuntu0.18.04.2 amd64 [installed,automatic] intel-microcode/bionic-security,bionic-updates,now 3.20190514.0ubuntu0.18.04.2 amd64 [installed,automatic] # cat /proc/cmdline BOOT_IMAGE=/vmlinuz-5.0.0-15-generic root=UUID=XXX ro rootflags=subvol=@ubuntu ro kaslr resume=/dev/mapper/swapDevice mem_sleep_default=deep dm_mod.use_blk_mq=1 acpi_osi=Linux acpi_backlight=vendor dis_ucode_ldr mitigations=off -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1537635] Re: Reduce zlib compression level for massive performance increase
This bug was fixed in the package apport - 2.20.11-0ubuntu2 --- apport (2.20.11-0ubuntu2) eoan; urgency=medium * test/test_backend_apt_dpkg.py: as of r3211 an error is not raised if the binary is not found. Cherry picked from upstream r3248. * backends/packaging-apt-dpkg.py: writing the contents mapping pickle file can Traceback on systems with little memory so don't write it. Cherry picked from upstream r3250. * test/test_apport_valgrind.py: skip test_sandbox_cache_options if system has little memory. -- Brian Murray Mon, 20 May 2019 18:39:46 -0700 ** Changed in: apport (Ubuntu Eoan) 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/1537635 Title: Reduce zlib compression level for massive performance increase To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1537635/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824002] Re: python3-launchpadlib needs promotion from suggests
This bug was fixed in the package apport - 2.20.11-0ubuntu2 --- apport (2.20.11-0ubuntu2) eoan; urgency=medium * test/test_backend_apt_dpkg.py: as of r3211 an error is not raised if the binary is not found. Cherry picked from upstream r3248. * backends/packaging-apt-dpkg.py: writing the contents mapping pickle file can Traceback on systems with little memory so don't write it. Cherry picked from upstream r3250. * test/test_apport_valgrind.py: skip test_sandbox_cache_options if system has little memory. -- Brian Murray Mon, 20 May 2019 18:39:46 -0700 ** Changed in: apport (Ubuntu Eoan) 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/1824002 Title: python3-launchpadlib needs promotion from suggests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1824002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
Tyler, > Can you try to boot with the latest Ubuntu kernel, with the problematic microcode, using 'mds=off' on the kernel command line? (Note that it is 'off' instead of 'no') I tried with mds=off, but no avail. > If that doesn't work, can you try to boot with 'mitigations=off' passed on the kernel command line? on the other hand, mitigations=off did cut it! I guess now we're to find which of the mitigations is causing it? Do you have a hint? Which are all the params for turning kernel mitigations,please? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829812] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1829812 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829812 Title: Regression for ubuntu_bpf test case in 5.0.0-16 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829812] [NEW] Regression for ubuntu_bpf test case in 5.0.0-16
Public bug reported:
This test will failed to build on 5.0.0-16 Disco.
5.0.0-16 Disco + 5.0.0-15 source code - build OK
5.0.0-16 Disco + 5.0.0-16 source code - Failed
make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
gcc -o
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/urandom_read
-static urandom_read.c -Wl,--build-id
make -C ../../../lib/bpf
OUTPUT=/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/
make[2]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/lib/bpf'
Auto-detecting system features:
...libelf: [ on ]
... bpf: [ on ]
HOSTCC
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/fixdep.o
HOSTLD
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/fixdep-in.o
LINK
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/fixdep
CC
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/libbpf.o
CC
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/bpf.o
CC
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/nlattr.o
CC
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/btf.o
CC
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/libbpf_errno.o
CC
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/str_error.o
CC
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/netlink.o
CC
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/bpf_prog_linfo.o
LD
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/libbpf-in.o
LINK
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/libbpf.a
LINK
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/libbpf.so
LINK
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/test_libbpf
make[2]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/lib/bpf'
gcc -Wall -O2 -I../../../include/uapi -I../../../lib -I../../../lib/bpf
-I../../../../include/generated -I../../../includetest_verifier.c
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/libbpf.a
-lcap -lelf -lrt -lpthread -o
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/test_verifier
make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf'
make: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests'
stderr:
Warning: Kernel ABI header at 'tools/include/uapi/linux/if_link.h' differs
from latest version at 'include/uapi/linux/if_link.h'
test_verifier.c: In function ‘do_test_single’:
test_verifier.c:15951:22: warning: implicit declaration of function
‘bpf_probe_prog_type’; did you mean ‘bpf_program__set_type’?
[-Wimplicit-function-declaration]
if (fd_prog < 0 && !bpf_probe_prog_type(prog_type, 0)) {
^~~
bpf_program__set_type
/usr/bin/ld: /tmp/ccRNIovw.o: in function `do_test_single':
test_verifier.c:(.text+0xf41): undefined reference to `bpf_probe_prog_type'
collect2: error: ld returned 1 exit status
make[1]: *** [../lib.mk:152:
/home/ubuntu/autotest/client/tmp/ubuntu_bpf/src/linux/tools/testing/selftests/bpf/test_verifier]
Error 1
make: *** [Makefile:90: all] Error 2
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-16-generic 5.0.0-16.17
ProcVersionSignature: User Name 5.0.0-16.17-generic 5.0.8
Uname: Linux 5.0.0-16-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 May 21 04:54 seq
crw-rw 1 root audio 116, 33 May 21 04:54 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
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:
CurrentDmesg:
Date: Tue May 21 05:08:27 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic
root=UUID=8595ef43-8a93-42a9-9f7b-92ebcc44df3f ro
RelatedPackageVersions:
[Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
Mark, one more request for now. You say that you can boot up a non- Ubuntu kernel with the problematic microcode. Can you boot up one of those kernels and then verify the microcode revision with the following command: $ sudo cat /sys/devices/system/cpu/cpu0/microcode/version Please paste the results. Also, the kernel version would be useful. Thanks again! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
Simon, can you post the contents of /proc/cpuinfo as well? It'd help with tracking down which processors might be affected by this. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794283] Re: nautilus throws error during copying file
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (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/1794283 Title: nautilus throws error during copying file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1794283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821169] Re: Jumpy touchpad input on Dell XPS 9370 when upgrading to 19.04 from 18.04
[Expired for libinput (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libinput (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/1821169 Title: Jumpy touchpad input on Dell XPS 9370 when upgrading to 19.04 from 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1821169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829568] Re: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all
After the sound quit I ran Alsa-info and got the following: !! !!ALSA Information Script v 0.4.64 !! !!Script ran on: Tue May 21 03:48:17 UTC 2019 !!Linux Distribution !!-- Ubuntu 19.04 \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 19.04" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 19.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=disco !!DMI Information !!--- Manufacturer: ASUSTeK COMPUTER INC. Product Name: GL703VD Product Version: 1.0 Firmware Version: GL703VD.308 Board Vendor: ASUSTeK COMPUTER INC. Board Name:GL703VD !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ACPI0003:00/status 15 /sys/bus/acpi/devices/ACPI000C:00/status 15 /sys/bus/acpi/devices/ATK4002:00/status 15 /sys/bus/acpi/devices/ELAN1200:00/status 15 /sys/bus/acpi/devices/INT33A1:00/status 15 /sys/bus/acpi/devices/INT33D0:00/status 15 /sys/bus/acpi/devices/INT340E:00/status 15 /sys/bus/acpi/devices/INT345D:00/status 15 /sys/bus/acpi/devices/INT3F0D:00/status 15 /sys/bus/acpi/devices/LNXPOWER:00/status 1 /sys/bus/acpi/devices/LNXPOWER:01/status 1 /sys/bus/acpi/devices/LNXPOWER:02/status 1 /sys/bus/acpi/devices/LNXPOWER:03/status 1 /sys/bus/acpi/devices/LNXPOWER:04/status 1 /sys/bus/acpi/devices/LNXPOWER:05/status 1 /sys/bus/acpi/devices/LNXPOWER:06/status 1 /sys/bus/acpi/devices/LNXPOWER:07/status 1 /sys/bus/acpi/devices/LNXPOWER:08/status 1 /sys/bus/acpi/devices/LNXPOWER:09/status 1 /sys/bus/acpi/devices/LNXPOWER:0a/status 1 /sys/bus/acpi/devices/LNXPOWER:0b/status 1 /sys/bus/acpi/devices/LNXPOWER:0c/status 1 /sys/bus/acpi/devices/LNXPOWER:0d/status 1 /sys/bus/acpi/devices/LNXPOWER:0e/status 1 /sys/bus/acpi/devices/LNXPOWER:0f/status 1 /sys/bus/acpi/devices/LNXPOWER:10/status 1 /sys/bus/acpi/devices/LNXPOWER:11/status 1 /sys/bus/acpi/devices/LNXPOWER:12/status 1 /sys/bus/acpi/devices/LNXPOWER:13/status 1 /sys/bus/acpi/devices/LNXPOWER:14/status 1 /sys/bus/acpi/devices/LNXPOWER:15/status 1 /sys/bus/acpi/devices/LNXPOWER:16/status 1 /sys/bus/acpi/devices/MSFT0101:00/status 15 /sys/bus/acpi/devices/PNP0103:00/status 15 /sys/bus/acpi/devices/PNP0C02:01/status 15 /sys/bus/acpi/devices/PNP0C02:03/status 3 /sys/bus/acpi/devices/PNP0C02:05/status 3 /sys/bus/acpi/devices/PNP0C02:06/status 15 /sys/bus/acpi/devices/PNP0C04:00/status 31 /sys/bus/acpi/devices/PNP0C09:01/status 15 /sys/bus/acpi/devices/PNP0C0A:00/status 31 /sys/bus/acpi/devices/PNP0C0C:00/status 15 /sys/bus/acpi/devices/PNP0C0E:00/status 11 /sys/bus/acpi/devices/PNP0C0F:00/status 9 /sys/bus/acpi/devices/PNP0C0F:01/status 9 /sys/bus/acpi/devices/PNP0C0F:02/status 9 /sys/bus/acpi/devices/PNP0C0F:03/status 9 /sys/bus/acpi/devices/PNP0C0F:04/status 9 /sys/bus/acpi/devices/PNP0C0F:05/status 9 /sys/bus/acpi/devices/PNP0C0F:06/status 9 /sys/bus/acpi/devices/PNP0C0F:07/status 9 /sys/bus/acpi/devices/device:69/status 15 /sys/bus/acpi/devices/device:79/status 11 !!Kernel Information !!-- Kernel release:5.0.0-15-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.0.0-15-generic Library version:1.1.8 Utilities version: 1.1.8 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xdf42 irq 133 !!PCI Soundcards installed in the system !!-- 00:1f.3 Audio device: Intel Corporation CM238 HD Audio Controller (rev 31) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0403: 8086:a171 (rev 31) Subsystem: 1043:1bc0 !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2
[Bug 1829568] Re: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all
shut down windos and rebooted Ubuntu. No Sound As SU ran echo 1 > parameters/dump_coef Speaker sound works for about 10 seconds. The following is the report from alsa-info !! !!ALSA Information Script v 0.4.64 !! !!Script ran on: Tue May 21 03:41:46 UTC 2019 !!Linux Distribution !!-- Ubuntu 19.04 \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 19.04" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 19.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=disco !!DMI Information !!--- Manufacturer: ASUSTeK COMPUTER INC. Product Name: GL703VD Product Version: 1.0 Firmware Version: GL703VD.308 Board Vendor: ASUSTeK COMPUTER INC. Board Name:GL703VD !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ACPI0003:00/status 15 /sys/bus/acpi/devices/ACPI000C:00/status 15 /sys/bus/acpi/devices/ATK4002:00/status 15 /sys/bus/acpi/devices/ELAN1200:00/status 15 /sys/bus/acpi/devices/INT33A1:00/status 15 /sys/bus/acpi/devices/INT33D0:00/status 15 /sys/bus/acpi/devices/INT340E:00/status 15 /sys/bus/acpi/devices/INT345D:00/status 15 /sys/bus/acpi/devices/INT3F0D:00/status 15 /sys/bus/acpi/devices/LNXPOWER:00/status 1 /sys/bus/acpi/devices/LNXPOWER:01/status 1 /sys/bus/acpi/devices/LNXPOWER:02/status 1 /sys/bus/acpi/devices/LNXPOWER:03/status 1 /sys/bus/acpi/devices/LNXPOWER:04/status 1 /sys/bus/acpi/devices/LNXPOWER:05/status 1 /sys/bus/acpi/devices/LNXPOWER:06/status 1 /sys/bus/acpi/devices/LNXPOWER:07/status 1 /sys/bus/acpi/devices/LNXPOWER:08/status 1 /sys/bus/acpi/devices/LNXPOWER:09/status 1 /sys/bus/acpi/devices/LNXPOWER:0a/status 1 /sys/bus/acpi/devices/LNXPOWER:0b/status 1 /sys/bus/acpi/devices/LNXPOWER:0c/status 1 /sys/bus/acpi/devices/LNXPOWER:0d/status 1 /sys/bus/acpi/devices/LNXPOWER:0e/status 1 /sys/bus/acpi/devices/LNXPOWER:0f/status 1 /sys/bus/acpi/devices/LNXPOWER:10/status 1 /sys/bus/acpi/devices/LNXPOWER:11/status 1 /sys/bus/acpi/devices/LNXPOWER:12/status 1 /sys/bus/acpi/devices/LNXPOWER:13/status 1 /sys/bus/acpi/devices/LNXPOWER:14/status 1 /sys/bus/acpi/devices/LNXPOWER:15/status 1 /sys/bus/acpi/devices/LNXPOWER:16/status 1 /sys/bus/acpi/devices/MSFT0101:00/status 15 /sys/bus/acpi/devices/PNP0103:00/status 15 /sys/bus/acpi/devices/PNP0C02:01/status 15 /sys/bus/acpi/devices/PNP0C02:03/status 3 /sys/bus/acpi/devices/PNP0C02:05/status 3 /sys/bus/acpi/devices/PNP0C02:06/status 15 /sys/bus/acpi/devices/PNP0C04:00/status 31 /sys/bus/acpi/devices/PNP0C09:01/status 15 /sys/bus/acpi/devices/PNP0C0A:00/status 31 /sys/bus/acpi/devices/PNP0C0C:00/status 15 /sys/bus/acpi/devices/PNP0C0E:00/status 11 /sys/bus/acpi/devices/PNP0C0F:00/status 9 /sys/bus/acpi/devices/PNP0C0F:01/status 9 /sys/bus/acpi/devices/PNP0C0F:02/status 9 /sys/bus/acpi/devices/PNP0C0F:03/status 9 /sys/bus/acpi/devices/PNP0C0F:04/status 9 /sys/bus/acpi/devices/PNP0C0F:05/status 9 /sys/bus/acpi/devices/PNP0C0F:06/status 9 /sys/bus/acpi/devices/PNP0C0F:07/status 9 /sys/bus/acpi/devices/device:69/status 15 /sys/bus/acpi/devices/device:79/status 11 !!Kernel Information !!-- Kernel release:5.0.0-15-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.0.0-15-generic Library version:1.1.8 Utilities version: 1.1.8 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xdf42 irq 133 !!PCI Soundcards installed in the system !!-- 00:1f.3 Audio device: Intel Corporation CM238 HD Audio Controller (rev 31) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0403: 8086:a171 (rev 31) Subsystem: 1043:1bc0 !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m:
[Bug 1812988] Re: ff76b0565523319d7c1c0b51d5a5a8915d33efab in ubuntu_btrfs_kernel_fixes generate kernel traces on Cosmic
I found this issue on B-hwe 4.18, node "gonzo" (passed on another node amaura) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812988 Title: ff76b0565523319d7c1c0b51d5a5a8915d33efab in ubuntu_btrfs_kernel_fixes generate kernel traces on Cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802495] Re: lttng-smoke test failed on i386 4.18 kernel
This is something that's failing for a while (was affected by bug 1802443, and then this one since 4.18.0-13.14~18.04.1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802495 Title: lttng-smoke test failed on i386 4.18 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829651] Re: Caps Lock indicator on screen
** Changed in: gnome-shell (Ubuntu) Importance: Low => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829651 Title: Caps Lock indicator on screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829568] Re: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all
In theory, adding model=auto (comment #3) doesn't affect your sound driver since even without model=auto, the audio driver doesn't apply any fixup models to your machine. Please do a test: cd /sys/module/snd_hda_codec sudo su echo 1 > parameters/dump_coef Then test your speaker, when the speaker can output sound, please run alsa-info.sh and upload the log After the speaker can't output sound anymore, please run alsa-info.sh again, and upload the log. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829568 Title: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1829568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)
Update: The patches have been merged to drm-tip: https://cgit.freedesktop.org/drm- tip/commit/?id=1a74fc0b3f49a0603f230b6f087da33bda3d7c66. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) To manage notifications about this bug go to: https://bugs.launchpad.net/dri/+bug/1714178/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828637] Re: sru cloud-init (18.5-45 to 19.1.1) Xenial, Bionic, Cosmic, Disco
Attach file openstack-sru-19.1.1.txt. ** Attachment added: "openstack-sru-19.1.1.txt" https://bugs.launchpad.net/bugs/1828637/+attachment/5265184/+files/openstack-sru-19.1.1.txt ** Description changed: == Begin SRU Template == [Impact] This release sports both bug-fixes and new features and we would like to make sure all of our supported customers have access to these improvements. The notable ones are: - - Azure: Return static fallback address as if failed to find endpoint - [Jason Zions (MSFT)] - - cc_mounts: check if mount -a on no-change fstab path [Jason Zions (MSFT)] - - replace remaining occurrences of LOG.warn - - DataSourceAzure: Adjust timeout for polling IMDS [Anh Vo] - - Azure: Changes to the Hyper-V KVP Reporter [Anh Vo] - - packages: update rpm specs for new bash completion path - - setup.py: install bash completion script in new location - - mount_cb: do not pass sync and rw options to mount [Gonéri Le Bouder] - - cc_apt_configure: fix typo in apt documentation [Dominic Schlegel] - - Revert "DataSource: move update_events from a class to an instance..." - - Change DataSourceNoCloud to ignore file system label's case. - [Risto Oikarinen] - - cmd:main.py: Fix missing 'modules-init' key in modes dict - [Antonio Romito] - - ubuntu_advantage: rewrite cloud-config module - - Azure: Treat _unset network configuration as if it were absent - [Jason Zions (MSFT)] - - DatasourceAzure: add additional logging for azure datasource [Anh Vo] - - Azure: Ensure platform random_seed is always serializable as JSON. - [Jason Zions (MSFT)] - - net: Fix ipv6 static routes when using eni renderer [Raphael Glon] - - Add ubuntu_drivers config module - - DataSource: move update_events from a class to an instance attribute - + - Azure: Return static fallback address as if failed to find endpoint + [Jason Zions (MSFT)] + - cc_mounts: check if mount -a on no-change fstab path [Jason Zions (MSFT)] + - replace remaining occurrences of LOG.warn + - DataSourceAzure: Adjust timeout for polling IMDS [Anh Vo] + - Azure: Changes to the Hyper-V KVP Reporter [Anh Vo] + - packages: update rpm specs for new bash completion path + - setup.py: install bash completion script in new location + - mount_cb: do not pass sync and rw options to mount [Gonéri Le Bouder] + - cc_apt_configure: fix typo in apt documentation [Dominic Schlegel] + - Revert "DataSource: move update_events from a class to an instance..." + - Change DataSourceNoCloud to ignore file system label's case. + [Risto Oikarinen] + - cmd:main.py: Fix missing 'modules-init' key in modes dict + [Antonio Romito] + - ubuntu_advantage: rewrite cloud-config module + - Azure: Treat _unset network configuration as if it were absent + [Jason Zions (MSFT)] + - DatasourceAzure: add additional logging for azure datasource [Anh Vo] + - Azure: Ensure platform random_seed is always serializable as JSON. + [Jason Zions (MSFT)] + - net: Fix ipv6 static routes when using eni renderer [Raphael Glon] + - Add ubuntu_drivers config module + - DataSource: move update_events from a class to an instance attribute See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/CloudinitUpdates The cloud-init team will be in charge of attaching the artifacts and console output of the appropriate run to the bug. cloud-init team members will not mark ‘verification-done’ until this has happened. * Automated Test Results TODO: attach automated cloud-init-proposed test artifacts - sru-artifact-lxd-artful sru-artifact-lxc-xenial + sru-artifact-lxd-(xenial|bionic|cosmic|disco) TODO: attach automated cloud-init-proposed test artifacts from tests for each release with kvm artifacts sru-artifact-kvm-artful sru-artifact-kvm-xenial TODO: attach Solutions Testing team test results for each LTS sru-artifact-solutions-qa-xenial TODO: attach MAAS Team test results for each LTS sru-artifact-maas-xenial * Manual Test Results - TODO: attach manual cloud-init-proposed test artifacts from tests for each release on ec2 datasource - sru-artifact-manual-ec2 - TODO: attach manual cloud-init-proposed test artifacts from tests for each release on gce datasource - sru-artifact-manual-gce - TODO: attach manual cloud-init-proposed test artifacts from tests for each release on azure datasource - sru-artifact-manual-azure + DONE: attach manual cloud-init-proposed test artifacts from tests for each release on ec2 datasource + ec2-sru-19.1.1.txt + + DONE: attach manual cloud-init-proposed test artifacts from tests for each release on gce datasource + gce-sru-19.1.1.txt + + DONE: attach manual cloud-init-proposed test artifacts from tests for each release
[Bug 1828637] Re: sru cloud-init (18.5-45 to 19.1.1) Xenial, Bionic, Cosmic, Disco
Attach file azure-sru-19.1.1.txt. ** Attachment added: "azure-sru-19.1.1.txt" https://bugs.launchpad.net/bugs/1828637/+attachment/5265183/+files/azure-sru-19.1.1.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828637 Title: sru cloud-init (18.5-45 to 19.1.1) Xenial, Bionic, Cosmic, Disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1828637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828637] Re: sru cloud-init (18.5-45 to 19.1.1) Xenial, Bionic, Cosmic, Disco
Attach file ec2-sru-19.1.1.txt. ** Attachment added: "ec2-sru-19.1.1.txt" https://bugs.launchpad.net/bugs/1828637/+attachment/5265181/+files/ec2-sru-19.1.1.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828637 Title: sru cloud-init (18.5-45 to 19.1.1) Xenial, Bionic, Cosmic, Disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1828637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828637] Re: sru cloud-init (18.5-45 to 19.1.1) Xenial, Bionic, Cosmic, Disco
Attach file gce-sru-19.1.1.txt. ** Attachment added: "gce-sru-19.1.1.txt" https://bugs.launchpad.net/bugs/1828637/+attachment/5265182/+files/gce-sru-19.1.1.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828637 Title: sru cloud-init (18.5-45 to 19.1.1) Xenial, Bionic, Cosmic, Disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1828637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829806] Re: I don't Know
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: 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/1829806 Title: I don't Know To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1829806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829801] Re: problem with login to user account. Keeps going back to login window
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Tags added: amdgpu ** Summary changed: - problem with login to user account. Keeps going back to login window + [amdgpu] Problem with login to user account. Keeps going back to login window -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829801 Title: [amdgpu] Problem with login to user account. Keeps going back to login window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1829801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829801] Re: problem with login to user account. Keeps going back to login window
Please be sure to only report one problem per bug. We will make this bug about the first problem you report only. ** Summary changed: - misc. problems + problem with login to user account. Keeps going back to login window -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829801 Title: [amdgpu] Problem with login to user account. Keeps going back to login window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1829801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829621] Re: [HP Laptop 14-ma0xxx] No sound after suspend
Thanks, but we will need more data points. We need to know at least one kernel version which does not have the bug (if a version exists). And then we need to know the earliest version where the bug was introduced. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829621 Title: [HP Laptop 14-ma0xxx] No sound after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1829621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827791] Re: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily
Yes those messages themselves are safe, but I think they may suggest the kernel got stuck for a while (somewhere, anywhere). And that would correlate with this bug. If there were any other kernel log messages around that time then please paste them here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827791 Title: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823583] Re: Xorg freeze ( also Nvidia freeze (tested) )
I can't see anything else in that log which might explain the freeze. First, if you have any nonstandard gnome-shell extensions installed then please uninstall them. Next, please follow the steps in comment #4 in case the freeze is a crash, of something. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823583 Title: Xorg freeze ( also Nvidia freeze (tested) ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1823583/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823516] Re: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions
Someone probably needs to find a relevant upstream Xorg bug link to see where/if it is being discussed there. This is not the place where Xorg developers discuss such things. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823516 Title: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1823516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829809] [NEW] grub error when installing ubuntu 18 on intel optane and hdd
Public bug reported: BIOS Information Vendor: Dell Inc. Version: 1.1.5 Release Date: 04/03/2018 Address: 0xF Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported Japanese floppy for NEC 9800 1.2 MB is supported (int 13h) 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.1 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: Mon May 20 21:58:01 2019 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.12 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829809 Title: grub error when installing ubuntu 18 on intel optane and hdd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1829809/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801494] Re: dock missing
I can't see any reason for the dock going permanently missing in that log. It might be a good idea if anyone experiencing this problem opens a new bug with all the required attachments, by running: ubuntu-bug gnome-shell which will do it automatically. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801494 Title: dock missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1801494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829568] Re: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all
Another reboot from Ubuntu back to Ubuntu and the Headset is still silent, BUT now the speaker sound works. Connecting and disconnecting the headset now has no effect on speaker sound except to mute when the headset is plugged in. I apologize for scattershot troubleshooting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829568 Title: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1829568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1702151] Re: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets()
** Tags added: disco eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1702151 Title: gnome-shell crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a() from g_object_ref() from st_theme_get_custom_stylesheets() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1702151/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819413] Re: [ICL] S0ix Enabling
On Intel ICL-Y SDP(alpha): Before patched short idle: 13.46w long idle: 12.94w s2idle: 12.67w After patched: short idle: 13.45w long idle: 13.06w s2idle: 12.87w -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819413 Title: [ICL] S0ix Enabling To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1819413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829568] Re: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all
Correction. The sound through the speakers only lasts for about 10 seconds. When I plug the headset in there still no sound in the headset, but when I unplug the headset the sound through the speakers resumes but then quits after about 10 seconds. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829568 Title: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1829568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829568] Re: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all
In accordance with this: https://docs.slackware.com/howtos:hardware :audio_and_snd-hda-intel#how_to_find_the_right_options I ran this: sudo echo "options snd-hda-intel model=auto" > /etc/modprobe.d/snd-hda-intel.conf and rebooted. That resulted in both the speakers and headphones working. But in gnome-control-center the sound test gave no sound on either. I have a dual boot system with windows 10 and I heard that there may be issues when quitting windows and loading Ubuntu. So I rebooted into windows and then rebooted back into Ubuntu. The speakers still worked, but the headset no longer works. I then rebooted ubuntu again with no change. Speakers work headset doesn't and the gnome-control-center doesn't' make any sound on either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829568 Title: [GL703VD, Realtek ALC295, Black Headphone left and right ] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1829568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829806] [NEW] I don't Know
Public bug reported: Don't have details about the issue! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompositorRunning: None Date: Mon May 20 22:03:38 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GF108 [GeForce GT 430] [3842:1335] InstallationDate: Installed on 2019-03-27 (54 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic root=/dev/mapper/ubuntu--vg-root ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2009 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: ASUS P5N-E SLI ACPI BIOS Revision 1406 dmi.board.name: P5N-E SLI dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: 1.XX dmi.chassis.asset.tag: 123456789000 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSP5N-ESLIACPIBIOSRevision1406:bd11/18/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5N-ESLI:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Apr 24 21:29:22 2019 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829806 Title: I don't Know To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1829806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829805] Re: Lubuntu Eoan Daily Image fails to boot after install on KVM
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/1829805 ** 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/1829805 Title: Lubuntu Eoan Daily Image fails to boot after install on KVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1829805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827967] Re: There are 4 HDMI/Displayport audio output listed in sound setting without attach any HDMI/DP monitor
** 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/1827967 Title: There are 4 HDMI/Displayport audio output listed in sound setting without attach any HDMI/DP monitor To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1827967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829805] Re: Lubuntu Eoan Daily Image fails to boot after install on KVM
** Attachment added: "Screenshot_eoan_2019-05-20_20:27:48.png" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1829805/+attachment/5265149/+files/Screenshot_eoan_2019-05-20_20%3A27%3A48.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829805 Title: Lubuntu Eoan Daily Image fails to boot after install on KVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1829805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829805] [NEW] Lubuntu Eoan Daily Image fails to boot after install on KVM
Public bug reported: Context: The live environment appears to function properly and install proceeds as expected with no noticeable errors. Expected results: After a system reboot the virtual machine enters the graphical environment Actual Results: After rebooting the virtual machine a kernel panic error screen appears. I will attempt to attach the screenshot after submitting this bug report. The collected data is from the live environment as the installed environment will not boot. lubuntu@lubuntu:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Eoan Ermine (development branch) Release:19.10 Codename: eoan lubuntu@lubuntu:~$ apt-cache policy grub2 grub2: Installed: (none) Candidate: 2.02+dfsg1-12ubuntu2 Version table: 2.02+dfsg1-12ubuntu2 500 500 cdrom://Lubuntu 19.10 _Eoan Ermine_ - Alpha amd64 (20190519) eoan/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu eoan/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: grub2 (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CasperVersion: 1.407 CurrentDesktop: LXQt Date: Tue May 21 00:30:39 2019 LiveMediaBuild: Lubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190519) SourcePackage: grub2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan 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/1829805 Title: Lubuntu Eoan Daily Image fails to boot after install on KVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1829805/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829203] Re: linux-fips: 4.4.0-1011.14 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1829209 - phase: Holding before Promote to Proposed - phase-changed: Monday, 20. May 2019 19:37 UTC + phase: Ready for Promote to Proposed + phase-changed: Tuesday, 21. May 2019 00:37 UTC reason: - promote-to-proposed: Holding -- builds not complete in ppa + promote-to-proposed: Pending -- ready for review -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829203 Title: linux-fips: 4.4.0-1011.14 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829756] Re: driver for Synaptics, Inc. 06cb:009a Fingerprint reader
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe (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/1829756 Title: driver for Synaptics, Inc. 06cb:009a Fingerprint reader To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1829756/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829255] Re: Sever performance degradation after updating to 5.0.0-15 due to mds mitigation
I'll point out that munbi is seeing this hit using the following CPU sig and microcode revision: sig=0x306c3, pf=0x10, revision=0x27 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829255 Title: Sever performance degradation after updating to 5.0.0-15 due to mds mitigation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829255] Re: Sever performance degradation after updating to 5.0.0-15 due to mds mitigation
Hello and thanks for the bug report. We hate to hear that you're seeing such a performance hit on your application when the MDS mitigations are enabled. Unfortunately, we are simply following Intel's recommendations[1] for mitigating MDS attacks. The kernel changes are relatively simple and the overhead comes from the kernel calling into the CPU microcode to flush the internal CPU buffers as well as the inefficiencies involved with flushing such buffers. Since the recommendation includes flushing the buffers before exiting from the kernel to userspace, workloads which are syscall heavy are likely to see the largest performance hit. I like your idea of alerting the user of such a potential performance hit, on the surface. However, the vast majority of users won't know how to handle that information and, even worse, it could scare users out of taking the update even though the mitigations may not significantly impact their typical usage. Very few users will have the need to bisect kernel changes to identify a performance decrease that they've measured. Another problem is that there's not a consistent way to alert users with pertinent information. The updates are provided to desktop systems, to headless servers, packaged in pre-built cloud images, delivered automatically to IoT devices that don't support typical user logins, etc. Even across something like desktop systems, users apply the updates in a variety of ways (manually with apt, automatically with unattended- upgrades, with a GUI such as update-manager, etc.). This is why we provide out-of-band information like this in Ubuntu Security Announcements[2] and, in some cases, more verbose KnowledgeBase articles. What I can promise is that we'll continue to work with Intel and the upstream kernel community in the case that future improvements are identified for the existing MDS mitigations. Thanks again for opening this bug report and please don't take the "Won't Fix" bug status as your voice being ignored. At the very least, when writing up the next KnowledgeBase article, I now know that any time we spend describing performance impacts will be much appreciated by someone out there. :) [1] https://software.intel.com/security-software-guidance/insights/deep-dive-intel-analysis-microarchitectural-data-sampling [2] https://usn.ubuntu.com ** Changed in: linux (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/1829255 Title: Sever performance degradation after updating to 5.0.0-15 due to mds mitigation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829255/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829801] [NEW] misc. problems
Public bug reported: a) problem with login to user account. Keeps going back to login window b) screen freeze after suspension. amdgup needs update ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6 Uname: Linux 5.0.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CompositorRunning: None Date: Mon May 20 16:20:30 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev eb) (prog-if 00 [VGA controller]) Subsystem: Dell Stoney [Radeon R2/R3/R4/R5 Graphics] [1028:087e] InstallationDate: Installed on 2019-05-20 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Dell Inc. Inspiron 3180 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic root=UUID=c4e1f2e7-71de-4e41-a62f-dd9e5e3a5f98 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0918N8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.0 dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd03/09/2018:svnDellInc.:pnInspiron3180:pvr1.3.0:rvnDellInc.:rn0918N8:rvrA00:cvnDellInc.:ct10:cvr1.3.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3180 dmi.product.sku: 087E dmi.product.version: 1.3.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829801 Title: misc. problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1829801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829784] Re: acpi(probably) random hang on boot
** Attachment added: "Add dmesg" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1829784/+attachment/5265133/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829784 Title: acpi(probably) random hang on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1829784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829745] Re: 3.20190514.0ubuntu0 actually contains version 20190507 Release
Hi, thanks for the report, the 0514 release was supposed to be unchanged from the 0507 beta, but was not. There is also supposed to be an update for Sandy Bridge forthcoming. ** Changed in: intel-microcode (Ubuntu) Status: New => In Progress ** Changed in: intel-microcode (Ubuntu) Assignee: (unassigned) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1829745 Title: 3.20190514.0ubuntu0 actually contains version 20190507 Release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829753] Re: package mysql-server-5.7 5.7.26-0ubuntu0.16.04 failed to install/upgrade: subprocess insalled post-insallation script retourned error exi status 1
Hello, I noticed several problems in the logs: First, it appears the filesystems may have problems: [86759.038651] EXT4-fs (dm-0): error count: 13 [86759.038661] EXT4-fs (dm-0): initial error at 1504970654: ext4_journal_start_sb:327 [86759.038665] EXT4-fs (dm-0): last error at 1505132213: ext4_put_super:819 [173218.112237] EXT4-fs (dm-0): error count: 13 [173218.112241] EXT4-fs (dm-0): initial error at 1504970654: ext4_journal_start_sb:327 [173218.112244] EXT4-fs (dm-0): last error at 1505132213: ext4_put_super:819 Second, it appears that your mysql database has been moved and perhaps the AppArmor policy hasn't been updated to reflect the changed location. Can you double-check your /etc/apparmor.d/local/usr.sbin.mysqld file and make sure you've added appropriate policy lines for the new mysql data locations? [252337.085739] type=1400 audit(1558357939.928:45): apparmor="DENIED" operation="open" parent=1558 profile="/usr/sbin/mysqld" name="/proc/1559/status" pid=1559 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [252337.085796] type=1400 audit(1558357939.928:46): apparmor="DENIED" operation="open" parent=1558 profile="/usr/sbin/mysqld" name="/sys/devices/system/node/" pid=1559 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [252337.085859] type=1400 audit(1558357939.928:47): apparmor="DENIED" operation="open" parent=1558 profile="/usr/sbin/mysqld" name="/proc/1559/status" pid=1559 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [252337.147250] type=1400 audit(1558357939.988:48): apparmor="DENIED" operation="mknod" parent=1558 profile="/usr/sbin/mysqld" name="/data/mysql/testflweb32.lower-test" pid=1559 comm="mysqld" requested_mask="c" denied_mask="c" fsuid=0 ouid=0 [252337.205848] type=1400 audit(1558357940.048:49): apparmor="DENIED" operation="mknod" parent=1558 profile="/usr/sbin/mysqld" name="/data/mysql/testflweb32.lower-test" pid=1559 comm="mysqld" requested_mask="c" denied_mask="c" fsuid=0 ouid=0 [252337.205869] type=1400 audit(1558357940.048:50): apparmor="DENIED" operation="mknod" parent=1558 profile="/usr/sbin/mysqld" name="/data/mysql/testflweb32.lower-test" pid=1559 comm="mysqld" requested_mask="c" denied_mask="c" fsuid=0 ouid=0 [252337.465182] type=1400 audit(1558357940.308:51): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/mysqld" pid=1573 comm="apparmor_parser" [252337.854376] type=1400 audit(1558357940.696:52): apparmor="STATUS" operation="profile_replace" name="/usr/sbin/mysqld" pid=1624 comm="apparmor_parser" [252337.859040] type=1400 audit(1558357940.704:53): apparmor="DENIED" operation="open" parent=1625 profile="/usr/sbin/mysqld" name="/proc/1626/status" pid=1626 comm="mysqld" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Third, it appears your ntp daemon is being prevented from accessing the network: [17901.858164] type=1400 audit(1558123373.318:26): apparmor="DENIED" operation="create" parent=1 profile="/usr/sbin/ntpd" pid=22481 comm="ntpd" family="unspec" sock_type="dgram" protocol=0 [17901.858205] type=1400 audit(1558123373.318:27): apparmor="DENIED" operation="create" parent=1 profile="/usr/sbin/ntpd" pid=22481 comm="ntpd" family="unspec" sock_type="dgram" protocol=0 [17901.858215] type=1400 audit(1558123373.318:28): apparmor="DENIED" operation="create" parent=1 profile="/usr/sbin/ntpd" pid=22481 comm="ntpd" family="unspec" sock_type="dgram" protocol=0 [17901.858224] type=1400 audit(1558123373.318:29): apparmor="DENIED" operation="create" parent=1 profile="/usr/sbin/ntpd" pid=22481 comm="ntpd" family="unspec" sock_type="dgram" protocol=0 [17901.858234] type=1400 audit(1558123373.318:30): apparmor="DENIED" operation="create" parent=1 profile="/usr/sbin/ntpd" pid=22481 comm="ntpd" family="unspec" sock_type="dgram" protocol=0 Does this sound familiar? I hope this helps. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829753 Title: package mysql-server-5.7 5.7.26-0ubuntu0.16.04 failed to install/upgrade: subprocess insalled post-insallation script retourned error exi status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1829753/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801757] Re: all app indicators disappear
Same here in Ubuntu 18.04. Monitor manager and other gnome extensions are disappearing from the top panel. Alt-F2 r, like other said, helps to get them back. Extensions are still running though when the bug appears. I noticed this behavior some time ago, maybe 3-4 months ago, after an upgrade but yet it is regular. When I lock/unlock the screen the bug happens but maybe in other situations too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801757 Title: all app indicators disappear To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1801757/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829740] Re: it told that it cant install properly
Hello, it looks like you had trouble connecting to WiFi, and perhaps other hardware problems: May 20 11:20:44 ubuntu wpa_supplicant[1323]: wlp1s0: SME: Trying to authenticate with 92:2a:a8:9a:a4:98 (SSID='srh-welcome' freq=2437 MHz) May 20 11:20:44 ubuntu kernel: [ 669.922382] wlp1s0: authenticate with 92:2a:a8:9a:a4:98 May 20 11:20:44 ubuntu NetworkManager[1325]: [1558351244.2275] device (wlp1s0): supplicant interface state: scanning -> authenticating May 20 11:20:44 ubuntu kernel: [ 669.927259] wlp1s0: send auth to 92:2a:a8:9a:a4:98 (try 1/3) May 20 11:20:44 ubuntu kernel: [ 669.979965] wlp1s0: send auth to 92:2a:a8:9a:a4:98 (try 2/3) May 20 11:20:44 ubuntu kernel: [ 670.039459] wlp1s0: send auth to 92:2a:a8:9a:a4:98 (try 3/3) May 20 11:20:44 ubuntu kernel: [ 670.107457] wlp1s0: authentication with 92:2a:a8:9a:a4:98 timed out May 20 11:20:44 ubuntu NetworkManager[1325]: [1558351244.4400] device (wlp1s0): supplicant interface state: authenticating -> disconnected May 20 11:20:44 ubuntu kernel: [ 670.235359] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 May 20 11:20:44 ubuntu kernel: [ 670.235367] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) May 20 11:20:44 ubuntu kernel: [ 670.235370] pcieport :00:1d.0: device [8086:9d18] error status/mask=0001/2000 May 20 11:20:44 ubuntu kernel: [ 670.235372] pcieport :00:1d.0:[ 0] Receiver Error (First) May 20 11:20:44 ubuntu NetworkManager[1325]: [1558351244.5402] device (wlp1s0): supplicant interface state: disconnected -> scanning May 20 11:20:44 ubuntu wpa_supplicant[1323]: wlp1s0: SME: Trying to authenticate with 92:2a:a8:c7:e3:29 (SSID='srh-welcome' freq=2412 MHz) May 20 11:20:44 ubuntu kernel: [ 670.489868] wlp1s0: authenticate with 92:2a:a8:c7:e3:29 May 20 11:20:44 ubuntu kernel: [ 670.490243] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 May 20 11:20:44 ubuntu kernel: [ 670.490252] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) May 20 11:20:44 ubuntu kernel: [ 670.490256] pcieport :00:1d.0: device [8086:9d18] error status/mask=0001/2000 May 20 11:20:44 ubuntu kernel: [ 670.490258] pcieport :00:1d.0:[ 0] Receiver Error (First) May 20 11:20:44 ubuntu kernel: [ 670.494076] wlp1s0: send auth to 92:2a:a8:c7:e3:29 (try 1/3) May 20 11:20:44 ubuntu NetworkManager[1325]: [1558351244.7960] device (wlp1s0): supplicant interface state: scanning -> authenticating May 20 11:20:44 ubuntu kernel: [ 670.565413] wlp1s0: send auth to 92:2a:a8:c7:e3:29 (try 2/3) May 20 11:20:44 ubuntu kernel: [ 670.616462] wlp1s0: send auth to 92:2a:a8:c7:e3:29 (try 3/3) May 20 11:20:44 ubuntu kernel: [ 670.680999] wlp1s0: authentication with 92:2a:a8:c7:e3:29 timed out May 20 11:20:45 ubuntu NetworkManager[1325]: [1558351245.0067] device (wlp1s0): supplicant interface state: authenticating -> disconnected May 20 11:20:45 ubuntu kernel: [ 670.802070] pcieport :00:1d.0: AER: Corrected error received: :00:1d.0 May 20 11:20:45 ubuntu kernel: [ 670.802078] pcieport :00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) May 20 11:20:45 ubuntu kernel: [ 670.802081] pcieport :00:1d.0: device [8086:9d18] error status/mask=0001/2000 May 20 11:20:45 ubuntu kernel: [ 670.802083] pcieport :00:1d.0:[ 0] Receiver Error (First) I hope this helps. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829740 Title: it told that it cant install properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1829740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829745] Re: 3.20190514.0ubuntu0 actually contains version 20190507 Release
** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829745 Title: 3.20190514.0ubuntu0 actually contains version 20190507 Release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829740] Re: it told that it cant install properly
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829740 Title: it told that it cant install properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1829740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829653] Re: I havn't signatures loaded by clamav scan
Hello, this appears to be using a freshclam and clamav installed outside of the packaging system. I suggest using the packaged versions of these tools. If that's not an option for whatever reason, then the clamav community would be a better place to ask for help. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829653 Title: I havn't signatures loaded by clamav scan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1829653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829655] Re: web pages are not loading and showing up with error "server not found" when connected to wifi
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829655 Title: web pages are not loading and showing up with error "server not found" when connected to wifi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1829655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829653] Re: I havn't signatures loaded by clamav scan
Thank you for using Ubuntu and taking the time to report a bug. Your report should contain, at a minimum, the following information so we can better find the source of the bug and work to resolve it. Submitting the bug about the proper source package is essential. For help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally, in the report please include: 1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> About Ubuntu. 2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by checking in Synaptic. 3) What happened and what you expected to happen. The Ubuntu community has also created debugging procedures for a wide variety of packages at https://wiki.ubuntu.com/DebuggingProcedures . Following the debugging instructions for the affected package will make your bug report much more complete. Thanks! ** Information type changed from Private Security to Public ** Changed in: clamav (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829653 Title: I havn't signatures loaded by clamav scan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1829653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829655] Re: web pages are not loading and showing up with error "server not found" when connected to wifi
Hello, it looked like you had some problems connecting to wifi -- and perhaps other hardware problems as well. I hope this helps: [ 2164.414923] wlp1s0: deauthenticating from 26:0d:65:1e:76:1d by local choice (Reason: 3=DEAUTH_LEAVING) [ 2164.541523] wlp1s0: authenticate with 5c:99:60:97:1a:d0 [ 2164.546685] wlp1s0: send auth to 5c:99:60:97:1a:d0 (try 1/3) [ 2164.549965] wlp1s0: authenticated [ 2164.556084] wlp1s0: associate with 5c:99:60:97:1a:d0 (try 1/3) [ 2164.560253] wlp1s0: RX AssocResp from 5c:99:60:97:1a:d0 (capab=0x411 status=0 aid=1) [ 2164.562377] wlp1s0: associated [ 2297.562542] pcieport :00:1c.0: AER: Corrected error received: :00:1c.0 [ 2297.562554] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 2297.562564] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 2297.562572] pcieport :00:1c.0:[ 0] Receiver Error (First) [ 2379.359481] ACPI Error: Cannot release Mutex [PATM], not acquired (20180531/exmutex-359) [ 2379.359506] No Local Variables are initialized for Method [_Q66] [ 2379.359511] No Arguments are initialized for method [_Q66] [ 2379.359516] ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.ECDV._Q66, AE_AML_MUTEX_NOT_ACQUIRED (20180531/psparse-516) [ 2479.371981] wlp1s0: deauthenticating from 5c:99:60:97:1a:d0 by local choice (Reason: 3=DEAUTH_LEAVING) [ 2479.507812] wlp1s0: authenticate with 26:0d:65:1e:76:1d [ 2479.512234] wlp1s0: send auth to 26:0d:65:1e:76:1d (try 1/3) [ 2479.517885] wlp1s0: authenticated [ 2479.520215] wlp1s0: associate with 26:0d:65:1e:76:1d (try 1/3) [ 2479.533060] wlp1s0: RX AssocResp from 26:0d:65:1e:76:1d (capab=0x431 status=0 aid=1) [ 2479.536553] wlp1s0: associated [ 2522.681743] wlp1s0: deauthenticating from 26:0d:65:1e:76:1d by local choice (Reason: 3=DEAUTH_LEAVING) [ 2522.809107] wlp1s0: authenticate with 5c:99:60:97:1a:d0 [ 2522.813864] wlp1s0: send auth to 5c:99:60:97:1a:d0 (try 1/3) [ 2522.817755] wlp1s0: authenticated [ 2522.820144] wlp1s0: associate with 5c:99:60:97:1a:d0 (try 1/3) [ 2522.824192] wlp1s0: RX AssocResp from 5c:99:60:97:1a:d0 (capab=0x411 status=0 aid=1) [ 2522.826018] wlp1s0: associated [ 2717.880069] wlp1s0: deauthenticating from 5c:99:60:97:1a:d0 by local choice (Reason: 3=DEAUTH_LEAVING) [ 2717.908924] wlp1s0: authenticate with 26:0d:65:1e:76:1d [ 2717.912723] wlp1s0: send auth to 26:0d:65:1e:76:1d (try 1/3) [ 2717.916517] wlp1s0: authenticated [ 2717.920089] wlp1s0: associate with 26:0d:65:1e:76:1d (try 1/3) [ 2717.926439] wlp1s0: RX AssocResp from 26:0d:65:1e:76:1d (capab=0x431 status=0 aid=1) [ 2717.931564] wlp1s0: associated [ 2767.989594] wlp1s0: deauthenticating from 26:0d:65:1e:76:1d by local choice (Reason: 3=DEAUTH_LEAVING) [ 2772.205542] wlp1s0: authenticate with 5c:99:60:97:1a:d0 [ 2772.209731] wlp1s0: send auth to 5c:99:60:97:1a:d0 (try 1/3) [ 2772.220085] wlp1s0: authenticated [ 2772.224303] wlp1s0: associate with 5c:99:60:97:1a:d0 (try 1/3) [ 2772.228441] wlp1s0: RX AssocResp from 5c:99:60:97:1a:d0 (capab=0x411 status=0 aid=1) [ 2772.230047] wlp1s0: associated [ 2875.097215] pcieport :00:1c.0: AER: Corrected error received: :00:1c.0 [ 2875.097226] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 2875.097237] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 2875.097244] pcieport :00:1c.0:[ 0] Receiver Error (First) Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829655 Title: web pages are not loading and showing up with error "server not found" when connected to wifi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1829655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829745] [NEW] 3.20190514.0ubuntu0 actually contains version 20190507 Release
*** This bug is a security vulnerability *** You have been subscribed to a public security bug by Seth Arnold (seth-arnold): intel-microcode 3.20190514.0ubuntu0 contents does not match https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files but rather seems to be version 20190507 according to the package releasenote. At least the Bionic and Xenial packages are affected. This is confirmed by the fact that the Pentium N35xx microcode update needed for the MDS flaws is missing on a laptop with a N3540 CPU. https://github.com/intel/Intel-Linux-Processor-Microcode-Data- Files/tree/master/intel-ucode has an update file named 06-37-08 and this file is indeed missing in the Ubuntu package. The other files listed as new platforms in the Intel releasenote are also missing, ie 06-37-09, 06-4c-03 and 06-4c-04. Please remake the Ubuntu intel-microcode 20190514 packages, this time including the actual Intel 20190514 upstream files... ** Affects: intel-microcode (Ubuntu) Importance: Undecided Status: New -- 3.20190514.0ubuntu0 actually contains version 20190507 Release https://bugs.launchpad.net/bugs/1829745 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829657] Re: Ubuntu 16.04 with kernel 4.4.0-148 hangs on boot on a ThinkPad L460 while 4.4.0-145 doesnt
I have almost the same problem. i run ubuntu 14.04 and for me its linux 4.4.0-146 that starts normal 148 only give the purple ubutu screen, but nothing after that 148 recovery stops after initial RAM disk -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829657 Title: Ubuntu 16.04 with kernel 4.4.0-148 hangs on boot on a ThinkPad L460 while 4.4.0-145 doesnt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1829657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829650] Re: OpenGl
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829650 Title: OpenGl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1829650/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721909] Re: Goodix GF3208 (fingerprint reader) not being recognised by lsusb(usbutils)
I have found a code for Goodix fingerprint sensor. That code is mainly written for Android devices. I have tried to compile it for Ubuntu 19.04. This code would be helpful to write a new driver. This code is written for the SPI interface. It would be useful if someone can try to rewrite this code for the USB interface. https://github.com/adnanjee/Goodix-GF3208 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721909 Title: Goodix GF3208 (fingerprint reader) not being recognised by lsusb(usbutils) To manage notifications about this bug go to: https://bugs.launchpad.net/usbutils/+bug/1721909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1721909] Re: Goodix GF3208 (fingerprint reader) not being recognised by lsusb(usbutils)
I have found a code for Goodix fingerprint sensor. That code is mainly written for Android devices. I have tried to compile it for Ubuntu 19.04. This code would be helpful to write a new driver. https://github.com/adnanjee/Goodix-GF3208 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1721909 Title: Goodix GF3208 (fingerprint reader) not being recognised by lsusb(usbutils) To manage notifications about this bug go to: https://bugs.launchpad.net/usbutils/+bug/1721909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1753677] Re: es2gears_wayland on mutter sticks to 119 FPS on a 59.95Hz display
** Changed in: mesa 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/1753677 Title: es2gears_wayland on mutter sticks to 119 FPS on a 59.95Hz display To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1753677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829785] Re: Evince: ∞ not found
** Changed in: evince 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/1829785 Title: Evince: ∞ not found To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1829785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810557] Re: GIMP crashed with a fatal error: fatal error: Segmentation failure
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gimp (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/1810557 Title: GIMP crashed with a fatal error: fatal error: Segmentation failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1810557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829171] Re: linux-hwe-edge: 5.0.0-16.17~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 -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1829173 phase: Holding before Promote to Proposed phase-changed: Monday, 20. May 2019 14:34 UTC reason: - promote-to-proposed: Holding -- builds not complete in ppa + promote-to-proposed: Holding -- another kernel is currently pending 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/1829171 Title: linux-hwe-edge: 5.0.0-16.17~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829510] Re: snapd connectivity check did not change fastly cdn
Hm so it sounds like snapd's behaviour is what Dimitri is asking for here? Has this changed in snapd recently (note that this behaviour was observed during the disco release sprint, so April 2019). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829510 Title: snapd connectivity check did not change fastly cdn To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1829510/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1322784] Re: Firefox crashes in flag_qsort during spellchecker initialization on x86 due to gcc bug
** Changed in: gcc-4.8 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1322784 Title: Firefox crashes in flag_qsort during spellchecker initialization on x86 due to gcc bug To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1322784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 568272] Re: unclear string for translators: country
Bug report refers to the bbc plug-in which no longer exists Closing as report is no longer valid ** Changed in: totem (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/568272 Title: unclear string for translators: country To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/568272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827791] Re: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily
In comment 28, the freeze happened just before taking the log, yet the last log entry was from ~1 minute earlier, so it doesn't look like there were any relevant log entries. However just now I had a freeze, and there are some messages in dmesg: [10980.231902] perf: interrupt took too long (2512 > 2500), lowering kernel.perf_event_max_sample_rate to 79500 [11986.082217] perf: interrupt took too long (3142 > 3140), lowering kernel.perf_event_max_sample_rate to 63500 [16384.901113] perf: interrupt took too long (3928 > 3927), lowering kernel.perf_event_max_sample_rate to 50750 Also in journalctl -b0: May 20 22:30:09 daniel-XPS-13-9380 kernel: perf: interrupt took too long (3928 > 3927), lowering kernel.perf_event_max_sample_rate to 50750 The previous journalctl message is from a few minutes prior. Searching for the error message suggests that perhaps these messages aren't any major cause for concern though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827791 Title: Dell XPS 13 9380 - Screen and input freezes / hangs temporarily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1827791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827750] Re: Not boot with EFI
Take care, current kernel 4.15.0-1036.38 still not bootable with EFI. ** Changed in: linux-raspi2 (Ubuntu) Status: Fix Committed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1827750 Title: Not boot with EFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1827750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829788] Re: backtrace on attach: KeyError: 'effectiveTo'
** Changed in: ubuntu-advantage-script 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/1829788 Title: backtrace on attach: KeyError: 'effectiveTo' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-advantage-script/+bug/1829788/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1735071] Re: Ctrl + F search disengages immediately after CTRL + F pressed
It's committed in the disco packaging repository, but not uploaded. I planned on bundling that change with other changes in an SRU. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1735071 Title: Ctrl + F search disengages immediately after CTRL + F pressed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1735071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827426] Re: ubuntu-cpc: parallel build targets produce different root FS output
** Merge proposal linked: https://code.launchpad.net/~rcj/livecd-rootfs/+git/livecd-rootfs/+merge/366862 ** Merge proposal linked: https://code.launchpad.net/~rcj/livecd-rootfs/+git/livecd-rootfs/+merge/366863 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827426 Title: ubuntu-cpc: parallel build targets produce different root FS output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1827426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829785] Re: Evince: ∞ not found
Sebastien, though the Russians the same symbol in mathematics for the infinity, the infinity symbol ∞ itself is not Cyrillic. Have you tested their solution, whatever it may be, simply to make sure that that's the same issue? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829785 Title: Evince: ∞ not found To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1829785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829692] Re: test_530_config_binfmt_aout in ubuntu_qrt_kernel_security failed on B-i386
Correct, the qrt script needed to catch up to the config changes that have landed in the 4.4, 4.15, and 4.18 kernel branches. I've done this in https://git.launchpad.net/qa-regression- testing/commit/?id=fca40854ff8d65c1fb4a19f57a8e541e3655aab9 . Closing tasks, thanks. ** Changed in: qa-regression-testing Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829692 Title: test_530_config_binfmt_aout in ubuntu_qrt_kernel_security failed on B-i386 To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1829692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801494] Re: dock missing
OK, I've attached the requested info from my system. It goes back 4 days, so it should include the period when it stopped working. Unfortunately I can't tell you exactly when that was - having the dock autohide means it's pretty much hidden until I need it. ** Attachment added: "currentjournal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1801494/+attachment/5265130/+files/currentjournal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801494 Title: dock missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1801494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 977228] Re: gnome-screenshot forgets "last-save-directory"
also on 18.04.02 LTS, also other people mentioned in comments https://askubuntu.com/questions/114429/default-save-directory-for-gnome- screenshot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/977228 Title: gnome-screenshot forgets "last-save-directory" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screenshot/+bug/977228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829651] Re: Caps Lock indicator on screen
@Sebastien Bacher, another screenshot of "Volume mute" attached. Caps Lock indicator also should be "on screen" looks like other indicators. not on top bar or anywhere else. for example when Caps Lock is on bright white A logo in the box, and when Caps Lock is off gray crossed A looks like the volume mute indicator in the box. you can add settings like to do it permanent on screen when Caps Lock is ON and temporary when it is OFF or both can be visible permanent on screen. those can be optional in my suggestion. as a suggestion maybe you can put Num Lock and Scroll Lock indicators as well. thank you all in advance for your hard works and contributions to make Ubuntu the best. ** Attachment added: "Volume mute indicator" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+attachment/5265129/+files/Screenshot%20from%202019-05-20%2023-32-51.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829651 Title: Caps Lock indicator on screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829651] Re: Caps Lock indicator on screen
Hi. i am expecting a Caps Lock indicator by default (without need of usage any 3rd party app which are not working proper tested few) like the screenshot of Volume indicator as an example i attached. thanks. ** Attachment added: "example - Volume indicator on screen" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+attachment/5265128/+files/Screenshot%20from%202019-05-20%2023-32-46.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829651 Title: Caps Lock indicator on screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827961] Re: Lenovo dock MAC Address pass through doesn't work in Ubuntu
Thank you for your reply and for looking into this issue. I will contact Lenovo but I won't get my hopes up. Operating the dock w/o MAC passthrough is luckily not a big deal for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827961 Title: Lenovo dock MAC Address pass through doesn't work in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1827961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818552] Re: disable a.out support
$ grep BINFMT_AOUT /boot/config-4.18.0-2[01]-generic /boot/config-4.18.0-20-generic:CONFIG_BINFMT_AOUT=m /boot/config-4.18.0-21-generic:# CONFIG_BINFMT_AOUT is not set Marking cosmic as verification-done. ** 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/1818552 Title: disable a.out support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818552/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829325] Re: raid installs are failing with edge
This bug was fixed in the package mdadm - 4.1-2ubuntu2 --- mdadm (4.1-2ubuntu2) eoan; urgency=medium * Drop broken and unused init scripts in favor of native systemd units, which can cause failure to reconfigure mdadm package under certain confiment types. LP: #1829325 -- Dimitri John Ledkov Mon, 20 May 2019 19:57:41 +0100 ** Changed in: mdadm (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829325 Title: raid installs are failing with edge To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1829325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829620] Re: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
Mark, thanks for all the testing. Unfortunately, I asked Steve to have you try the wrong 'mds=' option. Can you try to boot with the latest Ubuntu kernel, with the problematic microcode, using 'mds=off' on the kernel command line? (Note that it is 'off' instead of 'no') If that doesn't work, can you try to boot with 'mitigations=off' passed on the kernel command line? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829620 Title: intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1829620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829699] Re: Switches are gone from the VPN menu
Could you add your journalctl log to the bug? 3.32.1 is also in disco-proposed so it would be good to also test if the problem exist there/is really with gnome-shell ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (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/1829699 Title: Switches are gone from the VPN menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829785] Re: Evince: ∞ not found
The issue has been reported upstream in https://gitlab.gnome.org/GNOME/evince/issues/1116 ** Bug watch added: gitlab.gnome.org/GNOME/evince/issues #1116 https://gitlab.gnome.org/GNOME/evince/issues/1116 ** Changed in: evince (Ubuntu) Status: New => Triaged ** Also affects: evince via https://gitlab.gnome.org/GNOME/evince/issues/1116 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829785 Title: Evince: ∞ not found To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1829785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728681] Re: postinst script fails if data_path not set in client.conf
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: landscape-client (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/1728681 Title: postinst script fails if data_path not set in client.conf To manage notifications about this bug go to: https://bugs.launchpad.net/landscape-client/+bug/1728681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829651] Re: Caps Lock indicator on screen
Could you give details on what sort of indicator you expect? One in the top panel? One in password/text widgets? ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829651 Title: Caps Lock indicator on screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1829651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771836] Re: landscape-client fails when doing system upgrade
*** This bug is a duplicate of bug 1728681 *** https://bugs.launchpad.net/bugs/1728681 Thank you for your bug report, that looks like it already got reported as bug #1728681. Do you know how that line went missing? ** This bug has been marked a duplicate of bug 1728681 postinst script fails if data_path not set in client.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771836 Title: landscape-client fails when doing system upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1771836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1821729] Re: UEFI in ovmf package causes kernel panic
On Mon, May 20, 2019 at 2:15 AM Riccardo Pittau <1821...@bugs.launchpad.net> wrote: > > Hi Dann, > > Please find recent logs here: > > This is the correct output on bionic using virtio + ovmf package from xenial: > http://logs.openstack.org/90/644590/8/gate/ironic-tempest-ipa-partition-uefi-pxe_ipmitool-tinyipa/6232932/controller/logs/ironic-bm-logs/node-0_no_ansi_2019-05-18-12:09:41_log.txt.gz > > Job on bionic using virtio + new package from your repo: > http://logs.openstack.org/07/645507/10/check/ironic-tempest-ipa-partition-uefi-pxe_ipmitool-tinyipa/d9a0a64/controller/logs/ironic-bm-logs/node-0_no_ansi_2019-05-18-10:13:23_log.txt.gz > > Job on bionic using e1000 + new package from your repo: > http://logs.openstack.org/38/648938/5/check/ironic-tempest-ipa-partition-uefi-pxe_ipmitool-tinyipa/90c5126/controller/logs/ironic-bm-logs/node-0_no_ansi_2019-05-18-10:08:08_log.txt.gz (Attaching these logs here for safe keeping) ** Attachment added: "bionic_e1000_ppa-ovmf.txt" https://bugs.launchpad.net/bugs/1821729/+attachment/5265123/+files/bionic_e1000_ppa-ovmf.txt ** Attachment added: "bionic_virtio_ppa-ovmf.txt" https://bugs.launchpad.net/bugs/1821729/+attachment/5265124/+files/bionic_virtio_ppa-ovmf.txt ** Attachment added: "bionic_virtio_xenial-ovmf.txt" https://bugs.launchpad.net/bugs/1821729/+attachment/5265125/+files/bionic_virtio_xenial-ovmf.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821729 Title: UEFI in ovmf package causes kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1821729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731417] Re: Installed network printer removed automatically when turned off
This bug was fixed in the package cups-filters - 1.23.0-1 --- cups-filters (1.23.0-1) experimental; urgency=medium * New upstream version 1.23.0 - cups-browsed: When removing a local queue on shutdown or when DNS-SD reports the printer as disappeared check whether the local queue got overwritten by an external process as sometimes the shutdown or disappearing event comes too close for cups-browsed receiving a printer-modified notification from CUPS before (LP: #1731417) -- Didier Raboud Fri, 17 May 2019 10:01:20 +0200 ** Changed in: cups-filters (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731417 Title: Installed network printer removed automatically when turned off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1731417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822403] Re: ibus-engine-libpinyin assert failure: ibus-engine-libpinyin: bdb_utils.h:63: bool pinyin::copy_bdb(DB*, DB*): Assertion `DB_NOTFOUND == ret' failed.
Closing then, it would be interesting to know if that can be trigger again with some config (and which one) or if that was some sort of corruption ** Changed in: ibus-libpinyin (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822403 Title: ibus-engine-libpinyin assert failure: ibus-engine-libpinyin: bdb_utils.h:63: bool pinyin::copy_bdb(DB*, DB*): Assertion `DB_NOTFOUND == ret' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1822403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801494] Re: dock missing
it expired because no-one added the info requested in comment #18 ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801494 Title: dock missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1801494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829772] Re: The Samba 'panic action'
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: samba (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/1829772 Title: The Samba 'panic action' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1829772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828887] Re: [MIR] thin-provisioning-tools
ubuntu-server is now subscribed to bugs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1828887 Title: [MIR] thin-provisioning-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thin-provisioning-tools/+bug/1828887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1777165] Re: [SRU] metaphlan2 is not installable in bionic
Hi, Robie. Tested install from bionic-proposed under Ubuntu-MATE 18.04.2 LTS with 4.18.0-20-generic kernel: Install was successful, and no errors reported. Thanks, Tony. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1777165 Title: [SRU] metaphlan2 is not installable in bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/metaphlan2/+bug/1777165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829788] Re: backtrace on attach: KeyError: 'effectiveTo'
** Description changed:
+ [Impact]
+ Due to a server-side change, an expected key is no longer being sent to the
client during an attach operation. This causes the client to backtrace with a
KeyError exception:
+
Traceback (most recent call last):
- File "/usr/bin/ua", line 11, in
+ File "/usr/bin/ua", line 11, in
load_entry_point('ubuntu-advantage-tools==19.2', 'console_scripts',
'ubuntu-advantage')()
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 371, in main
return args.action(args, cfg)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 241, in
action_attach
action_status(args=None, cfg=cfg)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 295, in
action_status
contractInfo['effectiveTo'], '%Y-%m-%dT%H:%M:%SZ')
KeyError: 'effectiveTo'
+
+ The client should default to a "no expiration" value in this case.
+ Upstream already handles this, but the fix is missing for disco and
+ eoan.
+
+ [Test Case]
+ Run "sudo ua attach":
+ $ sudo ua attach
+ Email: andr...@canonical.com
+ Password:
+ Second-factor auth: nn
+ This machine is now attached to 'andreas.hasen...@canonical.com'.
+
+ Traceback (most recent call last):
+ File "/usr/bin/ua", line 11, in
+ load_entry_point('ubuntu-advantage-tools==19.2', 'console_scripts',
'ubuntu-advantage')()
+ File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 373, in main
+ return args.action(args, cfg)
+ File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 241, in
action_attach
+ action_status(args=None, cfg=cfg)
+ File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 311, in
action_status
+ contract_expiry=expiry.date(),
+ AttributeError: 'str' object has no attribute 'date'
+
+ With the fixed package, you should see "n/a" for the "Valid until" header and
it should not crash:
+ Email: andr...@canonical.com
+ Password:
+ Second-factor auth: pp
+ This machine is now attached to 'andreas.hasen...@canonical.com'.
+
+ Account: andreas.hasen...@canonical.com
+ Subscription: andreas.hasen...@canonical.com
+ Valid until: n/a
+ Technical support level: not included
+ ...
+
+
+ [Regression Potential]
+ The fix is just setting a "n/a" text value to the expiration date in the case
one isn't provided, and that is exactly the expected outcome, and what the
(already heavily modified) upstream code does.
+ No existing tests were affected by the change, which means it's not covered.
Upstream has already changed a lot, and includes a test for this.
+ Finally, the UA offerings are currently not available for non-LTS releases,
so there is nothing to regress here. A crash is a bad bug, though, so we do
want to get it fixed.
+
+ [Other Info]
+ None at this time.
** Description changed:
- [Impact]
+ [Impact]
Due to a server-side change, an expected key is no longer being sent to the
client during an attach operation. This causes the client to backtrace with a
KeyError exception:
Traceback (most recent call last):
File "/usr/bin/ua", line 11, in
load_entry_point('ubuntu-advantage-tools==19.2', 'console_scripts',
'ubuntu-advantage')()
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 371, in main
return args.action(args, cfg)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 241, in
action_attach
action_status(args=None, cfg=cfg)
File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 295, in
action_status
contractInfo['effectiveTo'], '%Y-%m-%dT%H:%M:%SZ')
KeyError: 'effectiveTo'
The client should default to a "no expiration" value in this case.
Upstream already handles this, but the fix is missing for disco and
eoan.
[Test Case]
Run "sudo ua attach":
$ sudo ua attach
Email: andr...@canonical.com
- Password:
+ Password:
Second-factor auth: nn
This machine is now attached to 'andreas.hasen...@canonical.com'.
Traceback (most recent call last):
- File "/usr/bin/ua", line 11, in
- load_entry_point('ubuntu-advantage-tools==19.2', 'console_scripts',
'ubuntu-advantage')()
- File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 373, in main
- return args.action(args, cfg)
- File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 241, in
action_attach
- action_status(args=None, cfg=cfg)
- File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 311, in
action_status
- contract_expiry=expiry.date(),
+ File "/usr/bin/ua", line 11, in
+ load_entry_point('ubuntu-advantage-tools==19.2', 'console_scripts',
'ubuntu-advantage')()
+ File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 373, in main
+ return args.action(args, cfg)
+ File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 241, in
action_attach
+ action_status(args=None, cfg=cfg)
+ File "/usr/lib/python3/dist-packages/uaclient/cli.py", line 311, in
action_status
+ contract_expiry=expiry.date(),
AttributeError: 'str' object has no attribute 'date'
[Bug 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
Looks like that the new version of network-manager is not working correctly with the systemd-resolved of Bionic. ** Tags added: regression-update ** Also affects: network-manager (Ubuntu Bionic) 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/1829566 Title: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829785] Re: Evince: ∞ not found
** Changed in: evince (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829785 Title: Evince: ∞ not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1829785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768166] Re: Random crashes
** Description changed:
+ [Impact]
+
+ ibus-libpinyin has proved to crash far too often. One or more files in
+ ~/.cache/ibus/libpinyin get corrupted somehow, and emptying that
+ directory allows the user to keep using ibus-libpinyin.
+
+ In disco (and eoan) ibus-libpinyin 1.11.0 and libpinyin 2.2.2 are
+ present, and the number of crashes has been reduced significantly:
+
+ https://errors.ubuntu.com/?package=ibus-libpinyin=month
+
+ Upstream ChangeLog ibus-libpinyin:
+ --
+ version 1.11.0
+ * fixes keypad decimal
+ * fixes emoji candidates
+ * support configurable opencc config
+
+ version 1.10.92
+ * fixes Enter handling
+
+ version 1.10.91
+ * support ime.register_trigger in lua extension
+ * support predicted candidates
+ * support emoji input
+
+ version 1.10.0
+ * bug fixes
+
+ version 1.9.91
+ * migrate to use GSettings
+ * fixes lyx short cut issue
+
+ version 1.9.3
+ * translate input method name in ibus menu
+
+ Upstream ChangeLog libpinyin:
+ -
+ version 2.2.2
+ * minor fixes
+
+ version 2.2.1
+ * fixes predicted candidates
+
+ version 2.2.0
+ * bug fixes
+
+ The proposal is to backport the disco versions of those packages to
+ bionic and cosmic in an attempt to prevent crashes. Proposed uploads are
+ available in this PPA:
+
+ https://launchpad.net/~gunnarhj/+archive/ubuntu/ibus-libpinyin
+
+ [Test Case]
+
+ * Install from {bionic,cosmic}-proposed:
+ - libpinyin13
+ - libpinyin-data
+ - ibus-libpinyin
+
+ * Use "Intelligent Pinyin" for typing and confirm that no new issues
+ show up when doing so.
+
+ (This is apparently not a confirmation that the upload really fixes the
+ bug. Time will tell.)
+
+ [Regression Potential]
+
+ The changes are mostly bug fixes, so the regression risk should be
+ limited. Also consider that the starting point is a rather unstable
+ functionality.
+
+ [Original description]
+
I have experienced random ibus-libpinyin crashes in bionic. I cannot
reproduce it, but it occurred at least a few times, even after the
official bionic release. Same crashes were also reported in the Ubuntu
Chinese forum.
Currently, the workaround is to delete the ~/.cache/ibus/libpinyin
folder.
I talked to Peng Wu, ibus-libpinyin's creator and main maintainer, he
suggested that we update the version of ibus-libpinyin to 1.10.
Can we give this update a trial?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1768166
Title:
Random crashes
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus-libpinyin/+bug/1768166/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
