[Bug 1809709] Re: package gir1.2-ibus-1.0:amd64 1.5.17-3ubuntu4 failed to install/upgrade: installed gir1.2-ibus-1.0:amd64 package pre-removal script subprocess returned error exit status 127
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809709 Title: package gir1.2-ibus-1.0:amd64 1.5.17-3ubuntu4 failed to install/upgrade: installed gir1.2-ibus-1.0:amd64 package pre-removal script subprocess returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1809709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809712] [NEW] Not responding to input after switch user to auto-login account
Public bug reported: Step: 1. There are two users, A and B. A is adminstrator, B is standard user, B is automatic login. 2. Boot into Ubuntu 18.04.1 LTS, it will automatically login to user B. 3. Switch User to user A without logging out. 4. Switch User back to user B, either by logging out from user A or not. Expected: it will be back to user B normally. Actual: it backs to user B but become not responding to keyboard, touchpad, or mouse input. Closing the lid is responded normally, which is locking the screen, the three-arrows in the lock screen is animated normally, clock is updated. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Dec 25 14:19:34 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:183a] Advanced Micro Devices, Inc. [AMD/ATI] Thames [Radeon HD 7500M/7600M Series] [1002:6840] (rev ff) (prog-if ff) InstallationDate: Installed on 2018-12-23 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP Pavilion g4 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=3182b497-aa0e-491d-aad5-e1c8e049dda1 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.01 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 183A dmi.board.vendor: Hewlett-Packard dmi.board.version: 56.0E dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.01:bd01/18/2012:svnHewlett-Packard:pnHPPaviliong4NotebookPC:pvr07911020561620100:rvnHewlett-Packard:rn183A:rvr56.0E:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion g4 Notebook PC dmi.product.version: 07911020561620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809712 Title: Not responding to input after switch user to auto-login account To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1809712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809709] [NEW] package gir1.2-ibus-1.0:amd64 1.5.17-3ubuntu4 failed to install/upgrade: installed gir1.2-ibus-1.0:amd64 package pre-removal script subprocess returned error exit status 127
Public bug reported: I removed python and it caused the gui to go, so i installed gnome through tty1 and then later installed ubuntu-desktop . After this all these happened ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gir1.2-ibus-1.0:amd64 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Mon Dec 24 20:56:01 2018 DuplicateSignature: package:gir1.2-ibus-1.0:amd64:1.5.17-3ubuntu4 Removing gir1.2-ibus-1.0:amd64 (1.5.17-3ubuntu4) ... /var/lib/dpkg/info/gir1.2-ibus-1.0:amd64.prerm: 6: /var/lib/dpkg/info/gir1.2-ibus-1.0:amd64.prerm: py3clean: not found dpkg: error processing package gir1.2-ibus-1.0:amd64 (--remove): installed gir1.2-ibus-1.0:amd64 package pre-removal script subprocess returned error exit status 127 ErrorMessage: installed gir1.2-ibus-1.0:amd64 package pre-removal script subprocess returned error exit status 127 InstallationDate: Installed on 2018-12-17 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: ibus Title: package gir1.2-ibus-1.0:amd64 1.5.17-3ubuntu4 failed to install/upgrade: installed gir1.2-ibus-1.0:amd64 package pre-removal script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809709 Title: package gir1.2-ibus-1.0:amd64 1.5.17-3ubuntu4 failed to install/upgrade: installed gir1.2-ibus-1.0:amd64 package pre-removal script subprocess returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1809709/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809704] Re: efivarfs test in ubuntu_kernel_selftest failed on the second run with Xenial AMD64
** Summary changed: - efivarfs test in ubuntu_kernel_selftest failed on Xenial AMD64 + efivarfs test in ubuntu_kernel_selftest failed on the second run with Xenial AMD64 ** Description changed: - The open(O_WRONLY) test in test_create_read failed with premission denied. + This seems to be an issue to the test case, if you run the test suite + twice, it will fail on the second run. + + The first run will create the test file: + $ ll /sys/firmware/efi/efivars/test_create_read-210be57c-9849-4fc7-a635-e6382d1aec27 + -rw--- 1 root root 0 Dec 24 07:16 /sys/firmware/efi/efivars/test_create_read-210be57c-9849-4fc7-a635-e6382d1aec27 + + This is cause the open(O_WRONLY) test in test_create_read failed with premission denied on the second run. This issue can be reproduced with upstream kernel tree on Xenial as well. - $ sudo make -C linux/tools/testing/selftests TARGETS=efivarfs run_tests make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' for TARGET in efivarfs; do \ - make -C $TARGET; \ + make -C $TARGET; \ done; make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs' make[1]: Nothing to be done for 'all'. make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs' for TARGET in efivarfs; do \ - make -C $TARGET run_tests; \ + make -C $TARGET run_tests; \ done; make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs' running test_create ./efivarfs.sh: line 48: /sys/firmware/efi/efivars/test_create-210be57c-9849-4fc7-a635-e6382d1aec27: Permission denied - [PASS] + [PASS] running test_create_empty ./efivarfs.sh: line 65: /sys/firmware/efi/efivars/test_create_empty-210be57c-9849-4fc7-a635-e6382d1aec27: Permission denied - [PASS] + [PASS] running test_create_read open(O_WRONLY): Permission denied - [FAIL] + [FAIL] running test_delete - [PASS] + [PASS] running test_zero_size_delete - [PASS] + [PASS] running test_open_unlink - [PASS] + [PASS] running test_valid_filenames - [PASS] + [PASS] running test_invalid_filenames - [PASS] + [PASS] selftests: efivarfs.sh [FAIL] make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-141-generic 4.4.0-141.167 ProcVersionSignature: User Name 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic x86_64 AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Dec 24 05:10 seq - crw-rw 1 root audio 116, 33 Dec 24 05:10 timer + total 0 + crw-rw 1 root audio 116, 1 Dec 24 05:10 seq + crw-rw 1 root audio 116, 33 Dec 24 05:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: - [92859.670497] smpboot: CPU 111 is now offline - [92859.723040] kvm: disabled by bios - [92859.750562] smpboot: Booting Node 1 Processor 111 APIC 0x7d - [92859.821706] kvm: disabled by bios + [92859.670497] smpboot: CPU 111 is now offline + [92859.723040] kvm: disabled by bios + [92859.750562] smpboot: Booting Node 1 Processor 111 APIC 0x7d + [92859.821706] kvm: disabled by bios Date: Tue Dec 25 06:30:01 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 0b1f:03e9 Insyde Software Corp. - Bus 001 Device 002: ID :0001 - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 0b1f:03e9 Insyde Software Corp. + Bus 001 Device 002: ID :0001 + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation S2600WFT PciMultimedia: - + ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-141-generic.efi.signed root=UUID=e93f24ed-4e90-4ccb-ba6d-f3b97fe0436f ro console=ttyS0,115200n8
[Bug 1733557] Re: Login screen showing Authentication Failure Switch to greeter...
Same issue on Ubuntu 18.04 LTS using Unity / lgihtdm / Compiz. Every time I lock the screen, I have to "switch to greeter" as it shows. So...Any solution to fix this now? I'm not sure if the information below would help. ➜ ~ tail /var/log/auth.log Dec 25 14:54:05 gadflysu-ubuntu lightdm: pam_unix(lightdm-greeter:session): session opened for user lightdm by (uid=0) Dec 25 14:54:05 gadflysu-ubuntu systemd: pam_unix(systemd-user:session): session opened for user lightdm by (uid=0) Dec 25 14:54:05 gadflysu-ubuntu systemd-logind[973]: New session c7 of user lightdm. Dec 25 14:54:06 gadflysu-ubuntu lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Dec 25 14:54:06 gadflysu-ubuntu lightdm: PAM adding faulty module: pam_kwallet.so Dec 25 14:54:06 gadflysu-ubuntu lightdm: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory Dec 25 14:54:06 gadflysu-ubuntu lightdm: PAM adding faulty module: pam_kwallet5.so Dec 25 14:54:06 gadflysu-ubuntu lightdm: pam_succeed_if(lightdm:auth): requirement "user ingroup nopasswdlogin" not met by user "gadflysu" Dec 25 14:54:41 gadflysu-ubuntu systemd-logind[973]: Removed session c7. Dec 25 14:54:41 gadflysu-ubuntu systemd: pam_unix(systemd-user:session): session closed for user lightdm ➜ ~ lightdm --show-config [Seat:*] A allow-guest=false C greeter-wrapper=/usr/lib/lightdm/lightdm-greeter-session D guest-wrapper=/usr/lib/lightdm/lightdm-guest-session G user-session=unity F greeter-session=unity-greeter H xserver-command=X -core I type=xlocal I display-setup-script=/sbin/prime-offload I display-stopped-script=/sbin/prime-switch [LightDM] B backup-logs=false Sources: A /usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf B /usr/share/lightdm/lightdm.conf.d/50-disable-log-backup.conf C /usr/share/lightdm/lightdm.conf.d/50-greeter-wrapper.conf D /usr/share/lightdm/lightdm.conf.d/50-guest-wrapper.conf E /usr/share/lightdm/lightdm.conf.d/50-ubuntu.conf F /usr/share/lightdm/lightdm.conf.d/50-unity-greeter.conf G /usr/share/lightdm/lightdm.conf.d/50-unity.conf H /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf I /usr/share/lightdm/lightdm.conf.d/90-nvidia.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1733557 Title: Login screen showing Authentication Failure Switch to greeter... To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1733557/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809706] [NEW] package libc6:amd64 2.26-0ubuntu2 failed to install/upgrade: package libc6:amd64 is already installed and configured
Public bug reported: i have no idea ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libc6:amd64 2.26-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 AptdaemonVersion: 1.1.1+bzr982-0ubuntu17 Architecture: amd64 Date: Tue Dec 25 12:07:01 2018 Dependencies: gcc-7-base 7.2.0-8ubuntu3 libc6 2.26-0ubuntu2 libgcc1 1:7.2.0-8ubuntu3 ErrorMessage: package libc6:amd64 is already installed and configured InstallationDate: Installed on 2017-04-11 (622 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5 SourcePackage: dpkg Title: package libc6:amd64 2.26-0ubuntu2 failed to install/upgrade: package libc6:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dpkg (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809706 Title: package libc6:amd64 2.26-0ubuntu2 failed to install/upgrade: package libc6:amd64 is already installed and configured To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1809706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809704] 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 1809704 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/1809704 Title: efivarfs test in ubuntu_kernel_selftest failed on Xenial AMD64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1809704/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804733] Re: package libc-bin 2.27-3ubuntu1 failed to install/upgrade: triggers looping, abandoned
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: glibc (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/1804733 Title: package libc-bin 2.27-3ubuntu1 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1804733/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809704] [NEW] efivarfs test in ubuntu_kernel_selftest failed on Xenial AMD64
Public bug reported: The open(O_WRONLY) test in test_create_read failed with premission denied. This issue can be reproduced with upstream kernel tree on Xenial as well. $ sudo make -C linux/tools/testing/selftests TARGETS=efivarfs run_tests make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' for TARGET in efivarfs; do \ make -C $TARGET; \ done; make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs' make[1]: Nothing to be done for 'all'. make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs' for TARGET in efivarfs; do \ make -C $TARGET run_tests; \ done; make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs' running test_create ./efivarfs.sh: line 48: /sys/firmware/efi/efivars/test_create-210be57c-9849-4fc7-a635-e6382d1aec27: Permission denied [PASS] running test_create_empty ./efivarfs.sh: line 65: /sys/firmware/efi/efivars/test_create_empty-210be57c-9849-4fc7-a635-e6382d1aec27: Permission denied [PASS] running test_create_read open(O_WRONLY): Permission denied [FAIL] running test_delete [PASS] running test_zero_size_delete [PASS] running test_open_unlink [PASS] running test_valid_filenames [PASS] running test_invalid_filenames [PASS] selftests: efivarfs.sh [FAIL] make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/efivarfs' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-141-generic 4.4.0-141.167 ProcVersionSignature: User Name 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 24 05:10 seq crw-rw 1 root audio 116, 33 Dec 24 05:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [92859.670497] smpboot: CPU 111 is now offline [92859.723040] kvm: disabled by bios [92859.750562] smpboot: Booting Node 1 Processor 111 APIC 0x7d [92859.821706] kvm: disabled by bios Date: Tue Dec 25 06:30:01 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b1f:03e9 Insyde Software Corp. Bus 001 Device 002: ID :0001 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation S2600WFT PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-141-generic.efi.signed root=UUID=e93f24ed-4e90-4ccb-ba6d-f3b97fe0436f ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.4.0-141-generic N/A linux-backports-modules-4.4.0-141-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2016 dmi.bios.vendor: Intel Corporation dmi.bios.version: SE5C620.86B.01.00.0336.112920161700 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: S2600WFT dmi.board.vendor: Intel Corporation dmi.board.version: H48104-410 dmi.chassis.asset.tag: dmi.chassis.type: 23 dmi.chassis.vendor: ... dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorporation:bvrSE5C620.86B.01.00.0336.112920161700:bd11/29/2016:svnIntelCorporation:pnS2600WFT:pvr:rvnIntelCorporation:rnS2600WFT:rvrH48104-410:cvn...:ct23:cvr..: dmi.product.name: S2600WFT dmi.product.version: dmi.sys.vendor: Intel Corporation ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug uec-images xenial ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809704 Title:
[Bug 1809703] [NEW] Buy Soma 350mg (Carisoprodol) | Take Soma to Counter Muscular Pain, Strain & Sprain
Public bug reported: Get Soma 350mg for Muscle Pain Buy Soma Online, overall causes of muscle pain come under a few groups, such as drug side effects, obstructed blood flow, infection, muscle and neurological disorders, autoimmune disease, stress, and injury. The signs of muscle injuries include cramping, swelling, bruising, weakness and pain. Whatever may be the cause or symptoms of muscle pain, people can get the better of distress and pain in a proper manner through Soma 350mg, which is a strong sedating skeletal muscle relaxant. The drug incorporates tribasic calcium phosphate, potassium sorbate, and starch, which help alleviate pain and relax muscles in and around the affected area. Order Here: https://pharmacyonline247.com/product/buy-soma-online/ https://pharmacyonline247.com/product/buy-soma-online/ Soma Online Soma Online USA Buy Soma Online with credit card Buy Soma Overnight 50 mg Soma Soma 50mg Online Buy Soma 100mg Online Best place to Buy Soma Online Buy cheap Soma Buy cheap Soma Online Buy generic Soma Online Buy Soma Buy Soma Online cheap Buy Soma Online legit Buy Soma Online USA Buy Soma pills Online Buy liquid Soma Online Buy Online Soma Buying Soma Online can i Buy Soma Online can yOu Buy Soma Online cheap Soma cheap Soma Online get Soma Online grapefruit Soma how to Buy Soma how to Buy Soma Online how to get Soma Online Soma Buy Soma Buy Online Soma On line Soma Online cheap Soma Online cod Soma Online for sale Soma Online from Mexico Soma Online Order Soma Online pharmacy Soma Overnight delivery Soma pills for sale Soma price Soma where to Buy Online Soma Order Soma Order Soma Online Order Soma Online cheap Order Soma Online Overnight Order Soma Overnight price of Soma purchase Soma purchasing Soma where can i Buy Soma where can i Buy Soma Online where to Buy Soma where to Buy Soma Online ** Affects: gcc-4.4 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809703 Title: Buy Soma 350mg (Carisoprodol) | Take Soma to Counter Muscular Pain, Strain & Sprain To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.4/+bug/1809703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809701] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809701 Title: cpu_hot_plug test in ubuntu_kernel_selftest failed on Moonshot ARM64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1809701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809701] [NEW] cpu_hot_plug test in ubuntu_kernel_selftest failed on Moonshot ARM64
Public bug reported: Test failed with "Operation not supported" when trying to offline a CPU: echo 0 > $SYSFS/devices/system/cpu/cpu$1/online This issue cannot be reproduced on CaviumThunderX ARM64 server, just the moonshots. $ sudo make -C linux/tools/testing/selftests TARGETS=cpu-hotplug run_tests make: Entering directory '/home/ubuntu/linux/tools/testing/selftests' make[1]: Entering directory '/home/ubuntu/linux/tools/testing/selftests/cpu-hotplug' make[1]: Nothing to be done for 'all'. make[1]: Leaving directory '/home/ubuntu/linux/tools/testing/selftests/cpu-hotplug' make[1]: Entering directory '/home/ubuntu/linux/tools/testing/selftests/cpu-hotplug' TAP version 13 selftests: cpu-hotplug: cpu-on-off-test.sh pid 8132's current affinity mask: ff pid 8132's new affinity mask: 1 CPU online/offline summary: Cpus in online state: 0-7 Cpus in offline state: 0 Limited scope test: one hotplug cpu (leaves cpu in the original state): online to offline to online: cpu 7 ./cpu-on-off-test.sh: line 92: echo: write error: Operation not supported offline_cpu_expect_success 7: unexpected fail not ok 1..1 selftests: cpu-hotplug: cpu-on-off-test.sh [FAIL] make[1]: Leaving directory '/home/ubuntu/linux/tools/testing/selftests/cpu-hotplug' make: Leaving directory '/home/ubuntu/linux/tools/testing/selftests' The CPU hotplug config was enabled on this SUT: $ cat /boot/config-`uname -r` | grep HOTPLUG | grep CPU CONFIG_HOTPLUG_CPU=y CONFIG_ACPI_HOTPLUG_CPU=y # CONFIG_CPU_HOTPLUG_STATE_CONTROL is not set ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: User Name 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 25 04:01 seq crw-rw 1 root audio 116, 33 Dec 25 04:01 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.1 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Dec 25 04:54:54 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 cosmic uec-images ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809701 Title: cpu_hot_plug test in ubuntu_kernel_selftest failed on Moonshot ARM64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1809701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809699] 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 1809699 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/1809699 Title: cpu_hot_plug test in ubuntu_kernel_selftest always return 0 on Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1809699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809699] [NEW] cpu_hot_plug test in ubuntu_kernel_selftest always return 0 on Xenial
Public bug reported: This test will always return PASSED even if there are some failures there, commit 8fe6e53a8ed5f0 can fix this issue: $ sudo make -C linux/tools/testing/selftests TARGETS=cpu-hotplug run_tests make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' for TARGET in cpu-hotplug; do \ make -C $TARGET; \ done; make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/cpu-hotplug' make[1]: Nothing to be done for 'all'. make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/cpu-hotplug' for TARGET in cpu-hotplug; do \ make -C $TARGET run_tests; \ done; make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/cpu-hotplug' pid 25001's current affinity mask: 3 pid 25001's new affinity mask: 1 CPU online/offline summary: Cpus in online state: 0-1 Cpus in offline state: 2 Limited scope test: one hotplug cpu (leaves cpu in the original state): online to offline to online: cpu 1 offline to online to offline: cpu 2 ./cpu-on-off-test.sh: line 78: /sys/devices/system/cpu/cpu2/online: No such file or directory online_cpu_expect_success 2: unexpected fail ./cpu-on-off-test.sh: line 83: /sys/devices/system/cpu/cpu2/online: No such file or directory offline_cpu_expect_success 2: unexpected fail selftests: cpu-on-off-test.sh [PASS] make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/cpu-hotplug' make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests' For Trusty, it's missing another 20 commits to reach 8fe6e53: 4813d2e736 (tools: memory-hotplug fix unexpected operator error) da9bc4 (tools: selftests - create a separate hotplug target for full range test) a88cc108f6 (lib: Export interval_tree) 93e9ef83f4 (test: add minimal module for verification testing) 3e2a4c183a (test: check copy_to/from_user boundary validation) 64a8946b44 (net: filter: BPF testsuite) 7069a97a14 (selftests/net: move test out of Makefile into a shell script) 3c25fa14f0 (selftests/user: move test out of Makefile into a shell script) 24fe831c17 (tools/testing/selftests/sysctl: validate sysctl_writes_strict) 0a8adf5847 (test: add firmware_class loader test) 6e68e6c5e4 (ftracetest: Initial commit for ftracetest) 4f5ce5e8d7 (selftests: add memfd_create() + sealing tests) c9b26b81af (syscalls: add selftest for execveat(2)) 3ce51050fa (selftest: size: Add size test for Linux kernel) backport with context arrangement 87b2d44026 (selftests: add memfd/sealing page-pinning tests) 498b473af9 (tools: selftests: fix build issue with make kselftests target) ce6a144a0d (selftests/memfd: Run test on all architectures) 5e29a9105b (selftests: Introduce minimal shared logic for running tests) cc16782169 (selftests: change cpu on-off-test.sh name to be unique) 8c749ce93e (selftests: create test-specific kconfig fragments) 8fe6e53a8e (selftests/cpu-hotplug: exit with failure when test occured unexpected behaviors) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-141-generic 4.4.0-141.167 ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Mon Dec 24 04:08:18 2018 HibernationDevice: RESUME=UUID=ca468a9c-9563-442c-85c6-6055e800a66e IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=b65b756a-ba4e-4c53-aa32-0db2bdb50bb3 crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.4.0-141-generic N/A linux-backports-modules-4.4.0-141-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug s390x third-party-packages xenial ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification
[Bug 1807077] Re: [SRU] mountall crashes on udev node with missing devname
** Description changed: [Impact] - * udev block nodes without a devname will crash mountall, resulting in + * udev block nodes without a devname will crash mountall, resulting in an unbootable system (emergency root shell) - * While this is not likely to happen in a matched distro/kernel + * While this is not likely to happen in a matched distro/kernel environment (it was discovered while needing to run a bionic 4.15 kernel on trusty), it is possible. - * The code in try_udev_device() assumes a block subsystem will always + * The code in try_udev_device() assumes a block subsystem will always have a devname; the SRU patches explicitly check for a devname and return if null. [Test Case] - * HPE DL385 Gen10, Samsung a822 NVMe controller, trusty install + * HPE DL385 Gen10, Samsung a822 NVMe controller, trusty install - * Kernels <4.15 (or possibly 4.14) do not expose nvme0c33n1 and do not + * Kernels <4.15 (or possibly 4.14) do not expose nvme0c33n1 and do not trigger the bug. Tested on 4.13, 4.4 and 3.13. - * Kernel 4.15 exposes nvme0c33n1 in udev but does not have a devname, + * Kernel 4.15 exposes nvme0c33n1 in udev but does not have a devname, mountall crash ensues. [Regression Potential] - * Patch might ignore legitimate block devices on existing + * Patch might ignore legitimate block devices on existing installations. Unlikely, since the logic path for null devname leads directly to a program crash. [Other Info] - - * Additional context for Canonical employees: PS4.5 is a trusty backend cloud, but we now have Gen10 hardware incoming (this was discovered while adding new nova-compute hardware). Older kernels are not usable because Gen10 requires ilorest, which requires a >4.4 kernel (at least artful 4.13 is known good). So trusty+4.15 is the only viable combination for continued support of the cloud while adding new hardware. This is done via apt pinning of bionic for the kernel packages, and, mountall notwithstanding, is working fine so far. + + * Additional context for Canonical employees: PS4.5 is a trusty backend + cloud, but we now have Gen10 hardware incoming (this was discovered + while adding new nova-compute hardware). Older kernels are not usable + because Gen10 requires ilorest, which requires a >4.4 kernel (at least + artful 4.13 is known good). So trusty+4.15 is the only viable + combination for continued support of the cloud while adding new + hardware. This is done via apt pinning of bionic for the kernel + packages, and, mountall notwithstanding, is working fine so far. + + TEST CASE: + 1. Enable -proposed + 2. apt-get install mountall=2.53ubuntu1 + 3. update-initramfs -k all -u + 4. Reboot + + VERIFICATION DONE + Rebooted successfully on affected Gen10 systems. Confirmed no regression on unaffected systems. Original description: Running bionic's 4.15 kernel on trusty on an HPE DL385 Gen10 results in a device node for the NVMe controller, /devices/pci:40/:40:03.1/:43:00.0/nvme/nvme0/nvme0c33n1 which itself does not have a devname. When mountall gets to it: fsck_update: updating check priorities try_mount: /srv/nova/instances waiting for device try_udev_device: ignored /dev/loop5 (not yet ready?) try_udev_device: ignored /dev/loop6 (not yet ready?) try_udev_device: ignored /dev/loop1 (not yet ready?) try_udev_device: ignored /dev/loop0 (not yet ready?) try_udev_device: block (null) (null) (null) and then crashes, leaving the boot at an emergency root shell. A successful scan looks like this for comparison: try_udev_device: block /dev/sdb (null) (null) try_udev_device: block /dev/sdb (null) (null) try_udev_device: block /dev/sda (null) (null) try_udev_device: block /dev/nvme0n1 ed56e3a9-60f7-4636-85a2-b53137b598e7 (null) try_udev_device: block /dev/bcache0 756cb2c6-b999-4905-a021-c2e688e81a86 instances The debdiffs check for a null devname in try_udev_device() and will not attempt to process it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807077 Title: [SRU] mountall crashes on udev node with missing devname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1807077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807077] Re: [SRU] mountall crashes on udev node with missing devname
** Tags removed: verification-needed verification-needed-trusty ** Tags added: verification-done verification-done-trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807077 Title: [SRU] mountall crashes on udev node with missing devname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1807077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799083] Re: virtual console unavailable with upgrade of cosmic or Ubuntu 18.10
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799083 Title: virtual console unavailable with upgrade of cosmic or Ubuntu 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729851] Re: Thunar segfaults while failing to unmount USB flash drive
[Expired for thunar (Ubuntu) because there has been no activity for 60 days.] ** Changed in: thunar (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/1729851 Title: Thunar segfaults while failing to unmount USB flash drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1729851/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1709686] Re: Thunar crashes with error "Bus error (core dumped)" when opening "Properties" of a file if thunar-gtkhash is installed
[Expired for gtkhash (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gtkhash (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/1709686 Title: Thunar crashes with error "Bus error (core dumped)" when opening "Properties" of a file if thunar-gtkhash is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtkhash/+bug/1709686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770675] Re: Android phone reported in Thunar as MyCDROM, MyCDROM1, MyCDROM3
[Expired for thunar (Ubuntu) because there has been no activity for 60 days.] ** Changed in: thunar (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/1770675 Title: Android phone reported in Thunar as MyCDROM, MyCDROM1, MyCDROM3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1770675/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795807] Re: package grub-efi-amd64-signed 1.93.7+2.02-2ubuntu8.6 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status
[Expired for grub2-signed (Ubuntu) because there has been no activity for 60 days.] ** Changed in: grub2-signed (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795807 Title: package grub-efi-amd64-signed 1.93.7+2.02-2ubuntu8.6 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1795807/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1726878] Re: thunar crashed with SIGSEGV
[Expired for gtkhash (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gtkhash (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/1726878 Title: thunar crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtkhash/+bug/1726878/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799973] Re: package lxd 1:0.4 failed to install/upgrade: new lxd package pre-installation script subprocess was killed by signal (Terminated)
[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-release-upgrader (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/1799973 Title: package lxd 1:0.4 failed to install/upgrade: new lxd package pre- installation script subprocess was killed by signal (Terminated) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1799973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799789] Re: gnome-shell segfaults when external monitor attached or detached
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (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/1799789 Title: gnome-shell segfaults when external monitor attached or detached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805079] Re: click/pop noise in the headphone on several lenovo laptops
I also have the quiet sound after the boot (but not too quiet).
About the noise you mentioned, I didn't hear that yet.
About the "Line Out Playback Volume" and "{Headphone,Speaker} Playback
Volume, without my patch, the Headphone and Speaker has its own
independent DAC, with my patch, they share one DAC, then the mixer name
is changed to "Line Out".
Could you generate 2 alsa-info.txt?
1) under the quiet sound condition, sudo echo 1 >
/sys/modules/snd_hda_codec/parameters/dump_coef; alsa-info.sh; then
upload the generated alsa-info.txt-quiet-headphone
2) after the sound change back to normal (quiet->not quiet), sudo echo 1
> /sys/modules/snd_hda_codec/parameters/dump_coef; alsa-info.sh; then
upload the generated alsa-info.txt-notquiet-headphone.
thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805079
Title:
click/pop noise in the headphone on several lenovo laptops
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805079/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1772677] Re: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)
Hi all, In Ubuntu 18.10 this bug is still here, my /var/log/syslog went to 38 GB in two hours. $ uname -a Linux plutot 4.18.0-13-generic #14-Ubuntu SMP Wed Dec 5 09:04:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ dpkg -l |grep gnome-shell ii chrome-gnome-shell 10.1-1 all GNOME Shell extensions integration for web browsers ii gnome-shell 3.30.1-2ubuntu1.18.10.1 amd64 graphical shell for the GNOME desktop ii gnome-shell-common 3.30.1-2ubuntu1.18.10.1 all common files for the GNOME shell ii gnome-shell-extension-appindicator 22-1 all AppIndicator/KStatusNotifierItem support for GNOME Shell ii gnome-shell-extension-ubuntu-dock 63ubuntu1 all Ubuntu Dock for GNOME Shell ii yaru-theme-gnome-shell 18.10.6 all Yaru GNOME Shell desktop theme from the Ubuntu Community $ cat /var/log/syslog ... [millions of similar lines ] Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #6 556ac620a830 i self-hosted:977 (7f36100f0280 @ 413) Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: == Stack trace for context 0x556ac2a75260 == Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #0 7fff170d96b0 b resource:///org/gnome/shell/ui/osdWindow.js:224 (7f35c7ac79d0 @ 273) Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #1 7fff170d9780 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f36100b0b80 @ 71) Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #2 7fff170d9840 b self-hosted:977 (7f36100f0280 @ 413) Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #3 7fff170d9930 b resource:///org/gnome/gjs/modules/signals.js:128 (7f36100c18b0 @ 386) Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #4 556ac620a998 i resource:///org/gnome/shell/ui/layout.js:538 (7f35c7a043a0 @ 127) Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #5 556ac620a8f0 i resource:///org/gnome/gjs/modules/_legacy.js:82 (7f36100b0b80 @ 71) Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #6 556ac620a830 i self-hosted:977 (7f36100f0280 @ 413) Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: == Stack trace for context 0x556ac2a75260 == Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #0 7fff170d96b0 b resource:///org/gnome/shell/ui/osdWindow.js:223 (7f35c7ac79d0 @ 231) Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #1 7fff170d9780 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f36100b0b80 @ 71) Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #2 7fff170d9840 b self-hosted:977 (7f36100f0280 @ 413) Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #3 7fff170d9930 b resource:///org/gnome/gjs/modules/signals.js:128 (7f36100c18b0 @ 386) Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #4 556ac620a998 i resource:///org/gnome/shell/ui/layout.js:538 (7f35c7a043a0 @ 127) Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #5 556ac620a8f0 i resource:///org/gnome/gjs/modules/_legacy.js:82 (7f36100b0b80 @ 71) Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #6 556ac620a830 i self-hosted:977 (7f36100f0280 @ 413) Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: == Stack trace for context 0x556ac2a75260 == Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #0 7fff170d96b0 b resource:///org/gnome/shell/ui/osdWindow.js:224 (7f35c7ac79d0 @ 273) Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #1 7fff170d9780 b resource:///org/gnome/gjs/modules/_legacy.js:82 (7f36100b0b80 @ 71) Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #2 7fff170d9840 b self-hosted:977 (7f36100f0280 @ 413) Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #3 7fff170d9930 b resource:///org/gnome/gjs/modules/signals.js:128 (7f36100c18b0 @ 386) Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #4 556ac620a998 i resource:///org/gnome/shell/ui/layout.js:538 (7f35c7a043a0 @ 127) Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #5 556ac620a8f0 i resource:///org/gnome/gjs/modules/_legacy.js:82 (7f36100b0b80 @ 71) Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: #6 556ac620a830 i self-hosted:977 (7f36100f0280 @ 413) Dec 24 03:51:59 pluto org.gnome.Shell.desktop[1940]: == Stack trace for context 0x556ac2a75260 == ... ... .. I saw above that this has been fixed upstream, what is the ETA to have the fix in 18.04 and 18.10? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772677 Title: gnome-shell filling up syslog with thousands of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772677/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809454] Re: [SRU] nova rbd auth fallback uses cinder user with libvirt secret
Reviewed: https://review.openstack.org/626897 Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=47b7c4f3cc582bf463fd0c796df84736a0074f48 Submitter: Zuul Branch:master commit 47b7c4f3cc582bf463fd0c796df84736a0074f48 Author: Corey Bryant Date: Fri Dec 21 08:23:32 2018 -0500 Ensure rbd auth fallback uses matching credentials As of Ocata, cinder config is preferred for rbd auth values with a fallback to nova values [1]. The fallback path, for the case when rbd_user is configured in cinder.conf and rbd_secret_uuid is not configured in cinder.conf, results in the mismatched use of cinder rbd_user with nova rbd_secret_uuid. This fixes that fallback path to use nova rbd_user from nova.conf with rbd_secret_uuid from nova.conf. [1] See commit f2d27f6a8afb62815fb6a885bd4f8ae4ed287fd3 Thanks to David Ames for this fix. Change-Id: Ieba216275c07ab16414065ee47e66915e9e9477d Co-Authored-By: David Ames Closes-Bug: #1809454 ** Changed in: nova 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/1809454 Title: [SRU] nova rbd auth fallback uses cinder user with libvirt secret To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1809454/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809692] [NEW] distorted lines when using google chrome browser
Public bug reported: I get dynamically changing distorted lines when using google chrome browser, I suppose it is due to my graphics card. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162 Uname: Linux 4.4.0-140-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Dec 25 04:18:51 2018 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07d0] InstallationDate: Installed on 2018-04-12 (256 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0c45:6717 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5480 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-140-generic.efi.signed root=UUID=72a3879f-b71f-40a0-b09b-ceb983af1dbf ro acpi_rev_override quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/30/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 0D0XXK dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd01/30/2018:svnDellInc.:pnLatitude5480:pvr:rvnDellInc.:rn0D0XXK:rvrA02:cvnDellInc.:ct10:cvr: dmi.product.name: Latitude 5480 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Dec 24 22:28:33 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1368 vendor LGD xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809692 Title: distorted lines when using google chrome browser To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1809692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809630] Re: seccomp in ubuntu_kernel_selftest failed on B s390x KVM
With Cosmic s390x KVM, 6 failures reported in our source tree and in the
upstream source tree:
[ RUN ] TRACE_syscall.ptrace_syscall_dropped
TRACE_syscall.ptrace_syscall_dropped: Test failed at step #127
[ FAIL ] TRACE_syscall.ptrace_syscall_dropped
[ RUN ] TRACE_syscall.syscall_dropped
TRACE_syscall.syscall_dropped: Test failed at step #2
[ FAIL ] TRACE_syscall.syscall_dropped
[ RUN ] TRACE_syscall.skip_after_RET_TRACE
seccomp_bpf.c:1884:TRACE_syscall.skip_after_RET_TRACE:Expected -1
(18446744073709551615) == syscall(20) (728)
seccomp_bpf.c:1885:TRACE_syscall.skip_after_RET_TRACE:Expected 1 (1) ==
(*__errno_location ()) (0)
TRACE_syscall.skip_after_RET_TRACE: Test failed at step #12
[ FAIL ] TRACE_syscall.skip_after_RET_TRACE
[ RUN ] TRACE_syscall.kill_after_RET_TRACE
TRACE_syscall.kill_after_RET_TRACE: Test exited normally instead of by signal
(code: 0)
[ FAIL ] TRACE_syscall.kill_after_RET_TRACE
[ RUN ] TRACE_syscall.skip_after_ptrace
seccomp_bpf.c:1946:TRACE_syscall.skip_after_ptrace:Expected -1
(18446744073709551615) == syscall(20) (728)
seccomp_bpf.c:1947:TRACE_syscall.skip_after_ptrace:Expected 1 (1) ==
(*__errno_location ()) (0)
TRACE_syscall.skip_after_ptrace: Test failed at step #15
[ FAIL ] TRACE_syscall.skip_after_ptrace
[ RUN ] TRACE_syscall.kill_after_ptrace
TRACE_syscall.kill_after_ptrace: Test exited normally instead of by signal
(code: 0)
[ FAIL ] TRACE_syscall.kill_after_ptrace
With Xenail s390x KVM, the test suite is outdated and it will pass with 54
tests there. With the upstream source tree, there will be 8 failures:
[ RUN ] global.KILL_process
seccomp_bpf.c:727:global.KILL_process:Expected 0 (0) != (((signed char)
__extension__ (((union { __typeof(status) __in; int __i; }) { .__in =
(status) }).__i))) & 0x7f) + 1) >> 1) > 0) (0)
global.KILL_process: Test terminated by assertion
[ FAIL ] global.KILL_process
[ RUN ] TRACE_syscall.ptrace_syscall_dropped
TRACE_syscall.ptrace_syscall_dropped: Test failed at step #223
[ FAIL ] TRACE_syscall.ptrace_syscall_dropped
[ RUN ] TRACE_syscall.syscall_dropped
TRACE_syscall.syscall_dropped: Test failed at step #2
[ FAIL ] TRACE_syscall.syscall_dropped
[ RUN ] TRACE_syscall.skip_after_RET_TRACE
seccomp_bpf.c:1884:TRACE_syscall.skip_after_RET_TRACE:Expected -1
(18446744073709551615) == syscall(20) (5486)
seccomp_bpf.c:1885:TRACE_syscall.skip_after_RET_TRACE:Expected 1 (1) ==
(*__errno_location ()) (0)
TRACE_syscall.skip_after_RET_TRACE: Test failed at step #12
[ FAIL ] TRACE_syscall.skip_after_RET_TRACE
[ RUN ] TRACE_syscall.kill_after_RET_TRACE
TRACE_syscall.kill_after_RET_TRACE: Test exited normally instead of by signal
(code: 0)
[ FAIL ] TRACE_syscall.kill_after_RET_TRACE
[ RUN ] TRACE_syscall.skip_after_ptrace
seccomp_bpf.c:1946:TRACE_syscall.skip_after_ptrace:Expected -1
(18446744073709551615) == syscall(20) (5486)
seccomp_bpf.c:1947:TRACE_syscall.skip_after_ptrace:Expected 1 (1) ==
(*__errno_location ()) (0)
TRACE_syscall.skip_after_ptrace: Test failed at step #15
[ FAIL ] TRACE_syscall.skip_after_ptrace
[ RUN ] TRACE_syscall.kill_after_ptrace
TRACE_syscall.kill_after_ptrace: Test exited normally instead of by signal
(code: 0)
[ FAIL ] TRACE_syscall.kill_after_ptrace
[ RUN ] global.get_metadata
seccomp_bpf.c:2923:global.get_metadata:Expected sizeof(md) (16) == ret
(18446744073709551615)
seccomp_bpf.c:2933:global.get_metadata:Expected sizeof(md) (16) == ret
(18446744073709551615)
seccomp_bpf.c:2934:global.get_metadata:Expected md.flags (2) == 0 (0)
global.get_metadata: Test failed at step #6
[ FAIL ] global.get_metadata
** Summary changed:
- seccomp in ubuntu_kernel_selftest failed on B s390x KVM
+ seccomp in ubuntu_kernel_selftest failed on X/B/C s390x KVM
** Tags added: cosmic xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809630
Title:
seccomp in ubuntu_kernel_selftest failed on X/B/C s390x KVM
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1809630/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809639] Re: ftrace test in ubuntu_kernel_selftest failed on X/B/C s390x KVM
** Tags added: cosmic xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809639 Title: ftrace test in ubuntu_kernel_selftest failed on X/B/C s390x KVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1809639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809639] Re: ftrace test in ubuntu_kernel_selftest failed on B s390x KVM
For Cosmic s390x KVM, it's: [12] ftrace - function glob filters [FAIL] [35] event trigger - test inter-event combined histogram trigger[FAIL] [44] event trigger - test histogram trigger [FAIL] [49] trace_marker trigger - test snapshot trigger [FAIL] [64] (instance) event trigger - test histogram trigger [FAIL] For Xenial s390x KVM, the test case number is smaller, and does not include these tests. So I have it tested with the upstream kernel tree, here are the failures: [9] event tracing - restricts events based on pid [FAIL] [15] ftrace - function glob filters [FAIL] [16] ftrace - function pid filters [FAIL] [19] ftrace - test for function event triggers [FAIL] [20] ftrace - function trace on module [FAIL] [23] ftrace - test reading of set_ftrace_filter [FAIL] [24] ftrace - Max stack tracer [FAIL] [36] Kprobe event auto/manual naming[FAIL] [68] (instance) Basic test for tracers [FAIL] [69] (instance) Basic trace clock test [FAIL] [70] (instance) Change the ringbuffer size [FAIL] [71] (instance) Snapshot and tracing setting [FAIL] [72] (instance) trace_pipe and trace_marker[FAIL] [73] (instance) event tracing - enable/disable with event level files [FAIL] [74] (instance) event tracing - restricts events based on pid [FAIL] [75] (instance) event tracing - enable/disable with subsystem level files [FAIL] [76] (instance) ftrace - stacktrace filter command [FAIL] [77] (instance) ftrace - test for function event triggers [FAIL] [78] (instance) ftrace - test for function traceon/off triggers[FAIL] [79] (instance) event trigger - test event enable/disable trigger [FAIL] [80] (instance) event trigger - test trigger filter[FAIL] [81] (instance) event trigger - test histogram modifiers [FAIL] [82] (instance) event trigger - test histogram trigger [FAIL] [83] (instance) event trigger - test multiple histogram triggers [FAIL] [84] (instance) trace_marker trigger - test histogram trigger [FAIL] [85] (instance) trace_marker trigger - test snapshot trigger [FAIL] ** Summary changed: - ftrace test in ubuntu_kernel_selftest failed on B s390x KVM + ftrace test in ubuntu_kernel_selftest failed on X/B/C s390x KVM -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809639 Title: ftrace test in ubuntu_kernel_selftest failed on X/B/C s390x KVM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1809639/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805079] Re: click/pop noise in the headphone on several lenovo laptops
Hui Wang,
Apologies for the slow reply.
Do you mean that you also have quiet sound after the boot?
Today I upgraded to 4.19.12, and the results seem the same. I'm running
Funtoo Linux with "gentoo-sources" kernel, HDA and the Realtek codec as
modules and plain ALSA with no daemons. I tried to compile them into
the main kernel image, but the results were the same, except that the
LEDs didn't work.
Here are sone more details:
The noise level I hear does not change with the playback volume. It's
stronger when I play something (e.g., with mplayer) or touch the
touchpad.
Without the 0x12 line, alsamixer shows heasphone and speaker controls at
100%, and "alsactl store" has {Headphone,Speaker} Playback
{Volume,Switch}. Under the standard kernel (with your patch), the
aforementioned controls in alsamixer show up as "00" in a box, and
alsactl has only "Line Out Playback Volume" (and the two Switches). Is
it possible that "line out" is treated differently from "headphone" by
the hardware, or is it just a name?
With the standard kernel, the output of "alsactl store" is identical
whether the sound is in the "too quiet" state or in the "noisy
headphone" state.
Sometimes after I warm-reboot from a standard kernel to a kernel without
the 0x12 line, I hear clicks when muting and unmuting the output, or
noise, but they disappear after I play something.
I put my kernel config and alsactl store output under
http://www.vygo.net/hda/ but I don't know if it aids debugging in any
way. Do you think it may help if I try your kernel config?
Thank you for your efforts and, if appropriate, merry Christmas.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805079
Title:
click/pop noise in the headphone on several lenovo laptops
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805079/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809687] Re: package linux-modules-4.15.0-39-generic 4.15.0-39.42~16.04.1 failed to install/upgrade: package linux-modules-4.15.0-39-generic is not ready for configuration cannot configure (curre
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809687 Title: package linux-modules-4.15.0-39-generic 4.15.0-39.42~16.04.1 failed to install/upgrade: package linux-modules-4.15.0-39-generic is not ready for configuration cannot configure (current status 'half-installed') To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1809687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809687] [NEW] package linux-modules-4.15.0-39-generic 4.15.0-39.42~16.04.1 failed to install/upgrade: package linux-modules-4.15.0-39-generic is not ready for configuration cannot configure (cur
Public bug reported: Well, I am new here. I do not know what further information you need to proceed. I just ran software updater and then show to click partial upgrade. I chose partial update and then this error occurred. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-modules-4.15.0-39-generic 4.15.0-39.42~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Dec 25 07:20:39 2018 Dependencies: DpkgHistoryLog: Start-Date: 2018-12-25 07:20:31 Requested-By: mohammadsheam (1000) Install: ubuntu-desktop:amd64 (1.361.2), ubuntu-software:amd64 (3.20.5-0ubuntu0.16.04.11, automatic), pulseaudio-module-bluetooth:amd64 (1:8.0-0ubuntu3.10, automatic) Upgrade: qbittorrent-nox:amd64 (4.1.4.99~201811190650-6594-0061b75~ubuntu16.04.1, 4.1.5.99~201812242205-6679-3f0e0a3~ubuntu16.04.1), qbittorrent:amd64 (4.1.4.99~201811190650-6594-0061b75~ubuntu16.04.1, 4.1.5.99~201812242205-6679-3f0e0a3~ubuntu16.04.1) DuplicateSignature: package:linux-modules-4.15.0-39-generic:4.15.0-39.42~16.04.1 Processing triggers for mime-support (3.59ubuntu1) ... dpkg: error processing package linux-modules-4.15.0-39-generic (--configure): package linux-modules-4.15.0-39-generic is not ready for configuration ErrorMessage: package linux-modules-4.15.0-39-generic is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-09-18 (97 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: linux-hwe Title: package linux-modules-4.15.0-39-generic 4.15.0-39.42~16.04.1 failed to install/upgrade: package linux-modules-4.15.0-39-generic is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809687 Title: package linux-modules-4.15.0-39-generic 4.15.0-39.42~16.04.1 failed to install/upgrade: package linux-modules-4.15.0-39-generic is not ready for configuration cannot configure (current status 'half-installed') To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1809687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789199] Re: python3-numpy shouldn't pull in *both* py3.6 and py3.7
** Changed in: python-numpy (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789199 Title: python3-numpy shouldn't pull in *both* py3.6 and py3.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-numpy/+bug/1789199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699660] Re: systemd-resolve breaks resolution of local network hostnames
IIRC what could be happening is that the additional timeout introduced by systemd-resolved first doing the newly implemented LLMNR lookup (which fails if not implemented by any device) causes some network tools to not even try doing a DNS lookup using the DHCP- or user-supplied DNS search domain suffixes. The second invocation then maybe finds a cached result which is however invalidated after some time - thus the varying or seemingly random results. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699660 Title: systemd-resolve breaks resolution of local network hostnames To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1699660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1699660] Re: systemd-resolve breaks resolution of local network hostnames
Hi, Ubuntu 18.10 using systemd version 239-7ubuntu10.5: I also see random results for dot-less domain or host names, i.e. it seems after a certain timeout, a hostname is not found e.g. when trying to establish an SSH connection to that machine using a single-label name. Immediately followed by a second try however, all is working again. This looks like a time-out or caching issue. Quoting https://github.com/systemd/systemd/issues/6224#issuecomment-312639959: "LLMNR lookups for missing names need to time out (because it is a true multicasting peer-to-peer protocol, and a name that doesn't exist means that there's nobody responding to an LLMNR query), but the host command on the client side times out even earlier than that, and then doesn't continue with the search domains, as search domains have to be honoured client-side, i.e. inside the "host" command." I have now disabled LLMNR in /etc/systemd/resolved.conf and will observer in the next days if this changes the behaviour. ** Bug watch added: github.com/systemd/systemd/issues #6224 https://github.com/systemd/systemd/issues/6224 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1699660 Title: systemd-resolve breaks resolution of local network hostnames To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1699660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809686] [NEW] Audio Crash , then trouble rebooting
Public bug reported: I will try my best to explain . Early this month (December 2018) I purchased a system 76 Gazelle with a POP OS Linux 18.10 . on about the 20th the audio crashes and I reboot and it would not boot up. I used my old laptop and found in a forum start up holding the space bar to enter a choice screen . I tried top to the 3rd for restore . Audio restores , but only a little while. I use my laptop a lot for you tube and FB . I go through the routine up till a choice to install and restart. ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: affects audio crash rebooting -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809686 Title: Audio Crash , then trouble rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1809686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809685] [NEW] The evince application often freezes
Public bug reported: Hi! The evince application (pdf document viewer) often freezes. Thanks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Dec 25 07:12:13 2018 InstallationDate: Installed on 2018-05-06 (232 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809685 Title: The evince application often freezes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1809685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809682] Re: "systemctl enable corosync-qdevice.service" fails
I forgot to mention, this bug report concerns: Ubuntu 18.04 Package: corosync-qdevice Version: 2.4.3-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809682 Title: "systemctl enable corosync-qdevice.service" fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1809682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809425] Re: [06cb:009a] Validity / Synaptic driver request
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libfprint (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/1809425 Title: [06cb:009a] Validity / Synaptic driver request To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1809425/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809682] [NEW] "systemctl enable corosync-qdevice.service" fails
Public bug reported: "systemctl enable corosync-qdevice.service" fails: Synchronizing state of corosync-qdevice.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install enable corosync-qdevice update-rc.d: error: corosync-qdevice Default-Start contains no runlevels, aborting. Reason is that an init.d script as well as a systemd service definition exists: # dpkg -L corosync-qdevice /lib/systemd/system/corosync-qdevice.service /etc/init.d/corosync-qdevice Therefore, using pcs to add a qdevice to the cluster fails: pcs quorum device add model net host=qdevice-host algorithm=ffsplit Log: I, [2018-12-24T22:39:00.208158 #149] INFO -- : Running: systemctl enable corosync-qdevice.service I, [2018-12-24T22:39:00.208322 #149] INFO -- : CIB USER: hacluster, groups: I, [2018-12-24T22:39:00.463878 #149] INFO -- : Return Value: 1 E, [2018-12-24T22:39:00.464110 #149] ERROR -- : Enabling corosync-qdevice failed Workaround is to manually remove the "/etc/init.d/corosync-qdevice" script. Solution is to remove the "/etc/init.d/corosync-qdevice" file from the "corosync-qdevice" package. ** Affects: corosync (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809682 Title: "systemctl enable corosync-qdevice.service" fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1809682/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1698979] Re: ftbfs with python 3.6
** Changed in: autopilot (Ubuntu) Status: New => Triaged ** Changed in: autopilot (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1698979 Title: ftbfs with python 3.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopilot/+bug/1698979/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
I managed to solve it in my Asus ZenBook UX433F. I'm running Ubuntu 18.04. I upgraded the Kernel to v4.19.11 as to Jorge Castro's answer to this question: https://askubuntu.com/questions/119080/how-to-update-kernel-to-the- latest-mainline-version-without-any-distro-upgrade Here are the exact steps I followed: 1. Download the appropriate files from: https://kernel.ubuntu.com/~kernel-ppa/mainline/ For example: linux-headers-4.19.11-041911_4.19.11-041911.201812191931_all.deb linux-headers-4.19.11-041911-generic_4.19.11-041911.201812191931_amd64.deb linux-image-unsigned-4.19.11-041911-generic_4.19.11-041911.201812191931_amd64.deb linux-modules-4.19.11-041911-generic_4.19.11-041911.201812191931_amd64.deb 2. Install each one in the appropriate order: sudo dpkg -i linux-headers-4.19.11-041911_4.19.11-041911.201812191931_all.deb sudo dpkg -i linux-headers-4.19.11-041911-generic_4.19.11-041911.201812191931_amd64.deb sudo dpkg -i linux-modules-4.19.11-041911-generic_4.19.11-041911.201812191931_amd64.deb sudo dpkg -i linux-image-unsigned-4.19.11-041911-generic_4.19.11-041911.201812191931_amd64.deb 3. Restart. In GRUB choose "Advanced options for Ubuntu". Select the new Kernel version. Cheers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1784485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
Yea, while a simple command may fix it, it should not be present on an out of the box install. A security bug as serious as this, should never have been left to the administrators to find out the hard way that data may be compromised because there was nothing in known-issues demonstrating that this flaw even existed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769383 Title: Ubuntu dock/launcher is shown on the lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779340] Re: systemd-networkd-wait-online.service Failed to start Wait for Network to be Configured with bridge
My setup is a little bit different, but the problem is the same. I have a bridge device for LXD. This is an extra bridge for testing purpose. root@rapper:~# cat /etc/netplan/91-test-bridges.yaml network: version: 2 renderer: networkd bridges: # the key name is the name for virtual (created) interfaces; # no ‘match’ or ‘set-name’ attributes are allowed. testbr0: addresses: - 10.82.0.1/24 # gateway4: 192.168.178.1 At startup there are no containers using this bridge, and that causes the 2 minute timeout of systemd-networkd-wait-online root@rapper:~# networkctl IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 enp2s0 ether carrier configured 3 testbr0 ether no-carrier configuring 4 br0 ether routableconfigured root@rapper:~# /lib/systemd/systemd-networkd-wait-online --timeout=20 --interface testbr0 ignoring: lo Event loop failed: Connection timed out I couldn't find a way to skip my test bridge for this online check, and still keep it controlled by networkd. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779340 Title: systemd-networkd-wait-online.service Failed to start Wait for Network to be Configured with bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1779340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758023] Re: Mouse acceleration not configurable in Xubuntu 18.04
In the end I upgraded to Xubuntu 18.10, and I've now got things how I want. However, the GUI still doesn't work properly: it has acceleration, which works, but no sensitivity. In that sense the upgrade was a waste of time. However I managed to get my trackball working by using xinput. I don't know whether these options would work in 18.04, because I've only just found the one that makes the difference on the following page: https://unix.stackexchange.com/questions/358016/increase-mouse-speed- xinput Here's what I did to make my trackball responsive. (You can run "xinput list" to find the name of your pointing device - mine is a 'Logitech USB Trackball'.) xinput set-prop 'Logitech USB Trackball' 'libinput Accel Speed' 1.0 xinput set-prop 'Logitech USB Trackball' 'libinput Accel Profile Enabled' 1 0 xinput set-prop 'Logitech USB Trackball' 'Coordinate Transformation Matrix' 6 0 0 0 6 0 0 0 2 The last line is what I was missing before when trying things on 18.04. The 3 non-zero arguments are horizontal speed (higher is faster), vertical speed (higher is faster), and sensitivity (lower is more sensitive - maybe pixel distance before acceleration?). The default values are 1 1 1, but 6 6 2 works better for me. Don't change the zero arguments otherwise crazy things can happen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758023 Title: Mouse acceleration not configurable in Xubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1758023/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779340] Re: systemd-networkd-wait-online.service Failed to start Wait for Network to be Configured with bridge
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (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/1779340 Title: systemd-networkd-wait-online.service Failed to start Wait for Network to be Configured with bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1779340/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809657] Re: software-updater crashes everytime after upgrading to Lubuntu 18.04
I ran update-manager in the terminal and made it crash as I mentioned, however no useful input was shown in terminal :/ any idea? ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809657 Title: software-updater crashes everytime after upgrading to Lubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809678] [NEW] It showed something like grub amd64 was unable to install so the system won't work without it
Public bug reported: It showed something like grub amd64 was unable to install so the system won't work without it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.6 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 Date: Mon Dec 24 22:20:41 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash --- LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) 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.6 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809678 Title: It showed something like grub amd64 was unable to install so the system won't work without it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1809678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
Interesting, thanks I will try that fix. I do agree that it's not good that it's still occurring as it's present on vanilla installs straight out of the box On Mon, 24 Dec 2018, 21:05 Yan Li While I wholeheartedly agree that we urgently need an official fix, I > also want to point out that > > gsettings set org.gnome.shell.extensions.dash-to-dock transparency-mode > FIXED > > is an effective workaround for me. On my Cosmic, I have never seen the > dock again on the lock screen. I'm using vanilla Ubuntu docker with no > dash-to-docker or any other customization to the dock. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1769383 > > Title: > Ubuntu dock/launcher is shown on the lock screen > > Status in gnome-shell package in Ubuntu: > Invalid > Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: > Fix Released > Status in gnome-shell source package in Bionic: > Invalid > Status in gnome-shell-extension-ubuntu-dock source package in Bionic: > In Progress > Status in gnome-shell source package in Cosmic: > Invalid > Status in gnome-shell-extension-ubuntu-dock source package in Cosmic: > In Progress > Status in gnome-shell source package in Disco: > Invalid > Status in gnome-shell-extension-ubuntu-dock source package in Disco: > Fix Released > > Bug description: > [Impact] > When entering the lock-screen mode, gnome-shell disables all the > extensions. It can happen that under certain conditions ubuntu-dock > re-enables itself, causing the ubuntu-dock to appear in the lock-screen, > exposing sensitive information. One possible way to reproduce this is to > enable dash-to-dock and ubuntu-dock at the same time. > > [Test Case] > 1. Make sure ubuntu-dock is enabled > 2. Enable dash-to-dock too > 3. Lock the screen > 4. Make sure the dock does not appear on the lock screen > 5. Make sure there is no warning is the journal > > [Possible Regressions] > Even if it's something we don't really support please make sure that you > can use dash-to-dock without uninstalling ubuntu-dock. > > [Original Bug] > > After an update from ubuntu 16.04 to 18.04 the dock is aviable on the > lockscreen after user login. > I did not configure this knowingly. Also i can start every application > which is available on the dock. > Settings, virtual box, visualstudio code and so on. > > After the update to 18.04 i just configure the screen frequency to > 144Hz and the night mode on. And attach the dock on bottom. > > I later undid these customizations back to configuration before, but > the dock is stil aviable on lockscreen. > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: gnome-settings-daemon 3.28.1-0ubuntu1 > ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 > Uname: Linux 4.15.0-20-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.9-0ubuntu7 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Sat May 5 18:30:16 2018 > InstallationDate: Installed on 2018-04-08 (27 days ago) > InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 > (20180228) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=de_DE.UTF-8 >SHELL=/bin/bash > SourcePackage: gnome-settings-daemon > UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago) > --- > ApportVersion: 2.20.9-0ubuntu7 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > DistroRelease: Ubuntu 18.04 > InstallationDate: Installed on 2018-04-08 (27 days ago) > InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 > (20180228) > NonfreeKernelModules: nvidia_modeset nvidia > Package: gnome-shell-extension-ubuntu-dock 0.9.1 > PackageArchitecture: all > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=de_DE.UTF-8 >SHELL=/bin/bash > ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 > Tags: bionic > Uname: Linux 4.15.0-20-generic x86_64 > UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo > _MarkForUpload: True > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769383 Title: Ubuntu dock/launcher is shown on the lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809669] Re: error unknow-package shim-signed 1.37~18.04.3+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: problemas de dependencias - se deja sin configurar
Thank you for reporting this bug and helping to improve Ubuntu. The message in your log is: E: Your kernels are unsigned. This system will fail to boot in a secure boot environment. This is not a bug in Ubuntu, but rather, a deliberate check to prevent your bootloader from being upgraded and leaving the system unbootable due to a change in security policy. According to your bug report, the kernel version you have booted is 4.19.1-041901-generic. This is not a kernel version that comes from the Ubuntu archive; it looks like it may be an upstream kernel build provided by the Ubuntu kernel team, but those kernels are not signed and are not bootable under Secure Boot without further configuration changes. If you wish to use this upstream kernel version, the easiest way to handle this is to turn Secure Boot off in your firmware. After turning Secure Boot off, you should be able to complete the package upgrade. If you wish to keep Secure Boot turned on, you should reboot your system to the kernel that comes from the Ubuntu archive, then uninstall the mainline 4.19.1-041901-generic kernel packages from your system, after which you should be able to complete the package upgrade. ** Changed in: shim-signed (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/1809669 Title: error unknow-package shim-signed 1.37~18.04.3+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: problemas de dependencias - se deja sin configurar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1809669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
While I wholeheartedly agree that we urgently need an official fix, I also want to point out that gsettings set org.gnome.shell.extensions.dash-to-dock transparency-mode FIXED is an effective workaround for me. On my Cosmic, I have never seen the dock again on the lock screen. I'm using vanilla Ubuntu docker with no dash-to-docker or any other customization to the dock. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769383 Title: Ubuntu dock/launcher is shown on the lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764669] Re: [Power]Failed to open Preferences
This bug was fixed in the package ukui-power-manager - 1.1.2-0ubuntu1 --- ukui-power-manager (1.1.2-0ubuntu1) disco; urgency=medium * Fix the error that can't open preferences dialog. (LP: #1764669) * Drop the depends on libgnome-keyring. (LP: #1767165) -- handsome_feng Mon, 24 Dec 2018 11:47:10 +0800 ** Changed in: ukui-power-manager (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/1764669 Title: [Power]Failed to open Preferences To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1764669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767165] Re: ukui-power-manager should not depend on libgnome-keyring
This bug was fixed in the package ukui-power-manager - 1.1.2-0ubuntu1 --- ukui-power-manager (1.1.2-0ubuntu1) disco; urgency=medium * Fix the error that can't open preferences dialog. (LP: #1764669) * Drop the depends on libgnome-keyring. (LP: #1767165) -- handsome_feng Mon, 24 Dec 2018 11:47:10 +0800 ** Changed in: ukui-power-manager (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/1767165 Title: ukui-power-manager should not depend on libgnome-keyring To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ukui-power-manager/+bug/1767165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
Being that it's been 7 months since this has been reported, why has it not been fixed yet? Are we trying to make Ubuntu's security a complete joke? Because that's where we are heading with this. This should have been fixed 7 months ago and top priority. There are people who use Ubuntu in enterprise environments, and considering 18.04 is LTS, it is disgusting that this has not been fixed yet. Get your act together Canonical. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769383 Title: Ubuntu dock/launcher is shown on the lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731318] Re: NVIDIA systems will not suspend with lid close and no external monitors
The attachment "fix_nvidia_suspend.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731318 Title: NVIDIA systems will not suspend with lid close and no external monitors To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1731318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769137] Re: after 17.10->18.4 upgrade, the system did not start due to missing libGL.so.1 and libGLESv2.so.2 files
Yes! Same issue for my days and hair strands up Solution: (same like Yaroslav and Danny) but my machine was a Dell 2950 server upgraded to 18.04 with Ubuntu desktop with --no-install- recommends => this was working on 16.04 before upgrade to 18.04 sudo ln -s /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1 /usr/lib/x86_64 -linux-gnu/libGL.so.1 sudo ln -s /usr/lib/x86_64-linux-gnu/mesa/libGLESv2.so.2 /usr/lib/x86_64 -linux-gnu/libGLESv2.so.2 lspci | grep -i VGA 0f:0d.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] ES1000 (rev 02) Hope this help! God blesses!!! Best regards, Sanyaade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769137 Title: after 17.10->18.4 upgrade, the system did not start due to missing libGL.so.1 and libGLESv2.so.2 files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1769137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799430] Re: Icon dock visible on lock screen
*** This bug is a duplicate of bug 1769383 *** https://bugs.launchpad.net/bugs/1769383 I have this as well as seen here: https://i.imgur.com/Om2BHoW.jpg This is a massive security risk and needs to be solved ASAP! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799430 Title: Icon dock visible on lock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-dashtodock/+bug/1799430/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770685] Re: Unable to change date format shown in nautilus
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nautilus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770685 Title: Unable to change date format shown in nautilus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1770685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808861] Re: chromium-browser crash Unreportable - Invalid core dump: BFD: warning: apport_core is truncated
Just had this happen again with a systemd-journald system problem error report. /var/crash/_lib_systemd_systemd-journald.0.crash: "Invalid core dump: BFD: warning: /tmp/apport_core_4z_uh8nz is truncated: expected core file size >= 18833408, found: 274432" apport log: ERROR: apport (pid 6651) Mon Dec 24 14:33:49 2018: called for pid 314, signal 6, core limit 0, dump mode 1 ERROR: apport (pid 6651) Mon Dec 24 14:33:49 2018: executable: /lib/systemd/systemd-journald (command line "/lib/systemd/systemd-journald") ERROR: apport (pid 6651) Mon Dec 24 14:33:50 2018: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 6651) Mon Dec 24 14:45:33 2018: wrote report /var/crash/_lib_systemd_systemd-journald.0.crash ** Summary changed: - chromium-browser crash Unreportable - Invalid core dump: BFD: warning: apport_core is truncated + Problem crashes Unreportable - Invalid core dump: BFD: warning: apport_core is truncated -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808861 Title: Problem crashes Unreportable - Invalid core dump: BFD: warning: apport_core is truncated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1808861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737614] Re: Low sound volume with Sunrise Point-LP HD Audio (ALC3227) in HP 15-BS576TX laptop
Bug is still present in 18.04 LTS. Very low sound/volume with this sound card in Ubuntu. Works fine in Windows 10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737614 Title: Low sound volume with Sunrise Point-LP HD Audio (ALC3227) in HP 15-BS576TX laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1737614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1514474] Re: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
I've had problems with this ever since I installed a ssd and installed it. The computer never shuts down properly, and I've never been able to upgrade. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1514474 Title: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1514474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793322] Re: “Domain” field missing when editing WPA2 Enterprise connection
Reported at https://gitlab.gnome.org/GNOME/gnome-control- center/issues/325 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793322 Title: “Domain” field missing when editing WPA2 Enterprise connection To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1793322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731318] Re: NVIDIA systems will not suspend with lid close and no external monitors
At System76, we've been carrying this patch for 18.04 and 18.10, to solve the issue. ** Patch added: "fix_nvidia_suspend.patch" https://bugs.launchpad.net/gnome-desktop/+bug/1731318/+attachment/5224694/+files/fix_nvidia_suspend.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731318 Title: NVIDIA systems will not suspend with lid close and no external monitors To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-desktop/+bug/1731318/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789924] Re: Missing Intel GPU pci-id's
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu Cosmic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809670] [NEW] package phpmyadmin 4:4.6.6-5 failed to install/upgrade: installed phpmyadmin package post-installation script subprocess returned error exit status 1
Public bug reported: Creating config file /etc/phpmyadmin/config-db.php with new version checking privileges on database phpmyadmin for phpmyadmin@localhost: user creation needed. granting access to database phpmyadmin for phpmyadmin@localhost: failed. error encountered creating user: mysql said: ERROR 1044 (42000) at line 1: Access denied for user 'debian-sys-maint'@'localhost' to database 'phpmyadmin' dbconfig-common: phpmyadmin configure: trying again. Determining localhost credentials from /etc/mysql/debian.cnf: succeeded. dbconfig-common: writing config to /etc/dbconfig-common/phpmyadmin.conf checking privileges on database phpmyadmin for phpmyadmin@localhost: user creation needed. granting access to database phpmyadmin for phpmyadmin@localhost: failed. error encountered creating user: mysql said: ERROR 1044 (42000) at line 1: Access denied for user 'debian-sys-maint'@'localhost' to database 'phpmyadmin' dbconfig-common: phpmyadmin configure: aborted. dbconfig-common: flushing administrative password dpkg: error processing package phpmyadmin (--configure): installed phpmyadmin package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: phpmyadmin E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: phpmyadmin 4:4.6.6-5 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Mon Dec 24 22:13:42 2018 ErrorMessage: installed phpmyadmin package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-12-24 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: phpmyadmin Title: package phpmyadmin 4:4.6.6-5 failed to install/upgrade: installed phpmyadmin package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: phpmyadmin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809670 Title: package phpmyadmin 4:4.6.6-5 failed to install/upgrade: installed phpmyadmin package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/phpmyadmin/+bug/1809670/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806258] Re: uBlock Origin icons are not displayed correctly
** Changed in: ublock-origin (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806258 Title: uBlock Origin icons are not displayed correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ublock-origin/+bug/1806258/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809669] [NEW] error unknow-package shim-signed 1.37~18.04.3+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: problemas de dependencias - se deja sin configurar
Public bug reported: i can not upgrade ubuntu, it has an error in kernel secure efi boot or something like that. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: shim-signed 1.37~18.04.3+15+1533136590.3beb971-0ubuntu1 Uname: Linux 4.19.1-041901-generic x86_64 .proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No existe el archivo o el directorio: '/proc/sys/kernel/moksbstate_disabled' ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: linux-libc-dev:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sun Dec 23 10:13:27 2018 ErrorMessage: problemas de dependencias - se deja sin configurar GrubDiff: Los archivos binarios /boot/efi/EFI/ubuntu/grubx64.efi y /usr/lib/grub/x86_64-efi-signed/grubx64.efi.signed son distintos InstallationDate: Installed on 2018-10-02 (83 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SecureBoot: 6 0 0 0 1 SourcePackage: shim-signed Title: package shim-signed 1.37~18.04.3+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: problemas de dependencias - se deja sin configurar UpgradeStatus: Upgraded to bionic on 2018-11-12 (41 days ago) ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809669 Title: error unknow-package shim-signed 1.37~18.04.3+15+1533136590.3beb971-0ubuntu1 failed to install/upgrade: problemas de dependencias - se deja sin configurar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1809669/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809668] Re: packagekitd crashed with SIGABRT
*** This bug is a duplicate of bug 1796315 *** https://bugs.launchpad.net/bugs/1796315 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1796315, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1809668/+attachment/5224666/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1809668/+attachment/5224668/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1809668/+attachment/5224671/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1809668/+attachment/5224672/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1809668/+attachment/5224673/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1809668/+attachment/5224674/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1809668/+attachment/5224675/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1796315 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809668 Title: packagekitd crashed with SIGABRT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1809668/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808861] Re: chromium-browser crash Unreportable - Invalid core dump: BFD: warning: apport_core is truncated
Not much to go off of in the apport log ** Attachment added: "apport.log" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1808861/+attachment/5224676/+files/apport.log ** Changed in: apport (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808861 Title: chromium-browser crash Unreportable - Invalid core dump: BFD: warning: apport_core is truncated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1808861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809662] Re: unable to upgrade from 17.04 to 18.04
** Tags added: artful2bionic ** Tags added: third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809662 Title: unable to upgrade from 17.04 to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1809662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768976] Re: Ubuntu 18.04 is overheating after upgrade from 16.04
The issue persists in version 18.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768976 Title: Ubuntu 18.04 is overheating after upgrade from 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768976/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803960] Re: 4.18.0 kernels hang system randomly
I almost forgot about this; 4.17.19-041719-lowlatency has been running fine now for 16 days. I'm going to switch to 4.18.0-13-lowlatency and confirm the problem still exists. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803960 Title: 4.18.0 kernels hang system randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803960/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809664] Re: gnuradio-companion requires python-gtk2 but it is not depended on
** Tags added: cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809664 Title: gnuradio-companion requires python-gtk2 but it is not depended on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnuradio/+bug/1809664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809664] [NEW] gnuradio-companion requires python-gtk2 but it is not depended on
Public bug reported: Hello, On Ubuntu 18.10, python-gtk2 is not installed as a dependency of the gnuradio package. Consequently, the gnuradio-companion application fails to run: $ gnuradio-companion ImportError Failed to initialize GTK. If you are running over ssh, did you enable X forwarding and start ssh with -X? (No module named gtk) Installing python-gtk2 manually fixes the problem. Also see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910001 ** Affects: gnuradio (Ubuntu) Importance: Undecided Status: New ** Tags: cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809664 Title: gnuradio-companion requires python-gtk2 but it is not depended on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnuradio/+bug/1809664/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809663] [NEW] package nvidia-utils-390 (not installed) failed to install/upgrade: tentata sovrascrittura di "/usr/bin/nvidia-bug-report.sh" presente anche nel pacchetto nvidia-340 340.107-0ubunt
Public bug reported: i dont know..has problem of dependecies... ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-utils-390 (not installed) ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 AptOrdering: libcuda1-340:amd64: Remove nvidia-opencl-icd-340:amd64: Remove libnvidia-compute-390:amd64: Install nvidia-utils-390:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Mon Dec 24 16:00:31 2018 ErrorMessage: tentata sovrascrittura di "/usr/bin/nvidia-bug-report.sh" presente anche nel pacchetto nvidia-340 340.107-0ubuntu0.18.04.1 InstallationDate: Installed on 2018-12-21 (2 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-utils-390 (not installed) failed to install/upgrade: tentata sovrascrittura di "/usr/bin/nvidia-bug-report.sh" presente anche nel pacchetto nvidia-340 340.107-0ubuntu0.18.04.1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809663 Title: package nvidia-utils-390 (not installed) failed to install/upgrade: tentata sovrascrittura di "/usr/bin/nvidia-bug-report.sh" presente anche nel pacchetto nvidia-340 340.107-0ubuntu0.18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1809663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737112] Re: ds9 is not using the ubuntu tcl/tk framework
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: saods9 (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/1737112 Title: ds9 is not using the ubuntu tcl/tk framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/saods9/+bug/1737112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737112] Re: ds9 is not using the ubuntu tcl/tk framework
See bug #1782692 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737112 Title: ds9 is not using the ubuntu tcl/tk framework To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/saods9/+bug/1737112/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782692] Re: ds9 crashes when start from command line
Ok, bug #1737112 is related: https://bugs.launchpad.net/ubuntu/+source/saods9/+bug/1737112 I installed miniconda3 a few days ago. When I removed it from the path (commented export PATH="/usr/local/miniconda3/bin:$PATH" in my ~/.bashrc file), I could start ds9 normally (the reason it worked with sudo permissions is probably because it didn't have miniconda3 in the path). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782692 Title: ds9 crashes when start from command line To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/saods9/+bug/1782692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782692] Re: ds9 crashes when start from command line
This happens to me too with Ubuntu 18.04.1 and saods9 7.5+repack1-2, although
previously it worked with no special problems.
When I run it with root permissions ("sudo ds9"), it works.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782692
Title:
ds9 crashes when start from command line
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/saods9/+bug/1782692/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782692] Re: ds9 crashes when start from command line
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: saods9 (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/1782692 Title: ds9 crashes when start from command line To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/saods9/+bug/1782692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809662] [NEW] unable to upgrade from 17.04 to 18.04
Public bug reported: While updating system the popup show error message about unabling installing new version of OS ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-release-upgrader-core 1:17.10.11 [modified: usr/bin/do-release-upgrade] ProcVersionSignature: Ubuntu 4.13.0-46.51-generic 4.13.16 Uname: Linux 4.13.0-46-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.9 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Dec 24 17:33:19 2018 InstallationDate: Installed on 2016-07-25 (882 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to artful on 2018-12-24 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful dist-upgrade wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809662 Title: unable to upgrade from 17.04 to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1809662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809660] Re: When starting new user session, gdm session may start twice or thrice
** Attachment added: "Output of 'ps -fA'" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1809660/+attachment/5224651/+files/ps-fA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809660 Title: When starting new user session, gdm session may start twice or thrice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1809660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809660] [NEW] When starting new user session, gdm session may start twice or thrice
Public bug reported: Sometimes, when user start new session, gdm session may spawn several times. Example: - System started, gdm session at tty1. - User eugene enter. Eugene session at tty2. - User vladik start new session from locked screen. Vladik session at tty4, and, unexpected, second gdm session at tty3! - After some logins/logouts with another users gdm session spawns more. Attached output of 'ps -fU gdm'. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.3 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Mon Dec 24 16:05:34 2018 SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic gdm gdm3 nvidia ** Attachment added: "ps-fU_gdm.txt" https://bugs.launchpad.net/bugs/1809660/+attachment/5224647/+files/ps-fU_gdm.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809660 Title: When starting new user session, gdm session may start twice or thrice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1809660/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809659] [NEW] Nautilus breadcrumbs aren't visible till hovered
Public bug reported: The breadcrumb is dark grey with no text visible until hovered over with default yaru theming ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: yaru-theme-gnome-shell 18.10.6 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 24 09:14:09 2018 Dependencies: InstallationDate: Installed on 2018-12-24 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181217) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Attachment added: "Screenshot from 2018-12-24 09-18-01.png" https://bugs.launchpad.net/bugs/1809659/+attachment/5224645/+files/Screenshot%20from%202018-12-24%2009-18-01.png ** Summary changed: - Nautilus breadcrumbs are visible till hovered + Nautilus breadcrumbs aren't visible till hovered -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809659 Title: Nautilus breadcrumbs aren't visible till hovered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1809659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1412672] Re: gnome-terminal crashes when requested to open a new tab
Can't reproduce in Ubuntu 18.10. ** Changed in: gnome-terminal (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/1412672 Title: gnome-terminal crashes when requested to open a new tab To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1412672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788829] Re: [SRU] Update to new maintenance release
** Changed in: borgbackup (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788829 Title: [SRU] Update to new maintenance release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/borgbackup/+bug/1788829/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809658] [NEW] package libsensors4 1:3.4.0-2 failed to install/upgrade: tentative de remplacement de « /etc/sensors.d/.placeholder », qui est différent d'autres instances du paquet libsensors4:i3
Public bug reported: Description:Ubuntu 16.04.5 LTS Release:16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libsensors4 1:3.4.0-2 ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128 Uname: Linux 4.4.0-127-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Dec 23 17:59:24 2018 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 ErrorMessage: tentative de remplacement de « /etc/sensors.d/.placeholder », qui est différent d'autres instances du paquet libsensors4:i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29 SourcePackage: lm-sensors Title: package libsensors4 1:3.4.0-2 failed to install/upgrade: tentative de remplacement de « /etc/sensors.d/.placeholder », qui est différent d'autres instances du paquet libsensors4:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lm-sensors (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809658 Title: package libsensors4 1:3.4.0-2 failed to install/upgrade: tentative de remplacement de « /etc/sensors.d/.placeholder », qui est différent d'autres instances du paquet libsensors4:i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lm-sensors/+bug/1809658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789171] 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 1789171 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/1789171 Title: upgrade changed my font size in tty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808626] Re: Triple buffer flickering and weird display updating
I've been running the same setup and it runs absolutely perfectly if I boot up with editing the Ubuntu command line in grub and add video=VGA-1:e BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID= ro drm_kms_helper.edid_firmware=VGA-1:edid/hannsg.bin video=VGA-1:e adding the video=VGA-1:e will allow the drm_kms_helper.edid_firmware parameter to work and I get my proper display. If I don't add the video=VGA-1:e line it will come up at 1024x768 mode and give a "Could not apply the stored configuration for monitors". After I do this following xrandr command and the stored configuration is restored I get the flickering problem virtually INSTANTLY. $ xrandr --newmode "1920x1080R" 138.50 1920 1968 2000 2080 1080 1083 1088 +hsync -vsync; xrandr --addmode VGA-1 "1920x1080R" With the video=VGA-1:e the stored configuration comes up properly on initial boot and the video drivers work perfectly, no flickering. https://ptouchman.blogspot.com/2018/12/my-edid-was-going-unrecognized- until-i.html I'll post a video when I dig out my digital camera. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808626 Title: Triple buffer flickering and weird display updating To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1808626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809657] 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 1809657 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/1809657 Title: software-updater crashes everytime after upgrading to Lubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789171] Re: upgrade changed my font size in tty
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1789171 Title: upgrade changed my font size in tty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1789171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809657] [NEW] software-updater crashes everytime after upgrading to Lubuntu 18.04
Public bug reported: I am running a virtualbox with Lubuntu 18.04. I upgraded to this version from the previous LTS through the software-updater, and everything worked fine, except for the software updater- Whenever I run it manually to see if there are updates, or when it pop-out automatically and I click, it crashes. I tried to run it from terminal to see if it showed some error but I couldn't find a way to do so. Any help? If I run "sudo apt-get upgrade" I can update the software without problem. I tried it on another virtualbox with the same set-up (host Lubuntu 16.04.3 guest Lubuntu 18.04) and the problems happens too. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809657 Title: software-updater crashes everytime after upgrading to Lubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809656] [NEW] Small windows output corrupted in XWayland clients
Public bug reported: Ubuntu 18.04 Pop!_OS flavour, AMD RX 560, AMD Ryzen 5 2400G (video disabled), proprietary AMD drivers 18.40, Gnome Wayland session, 4k monitor. I tried to use ubuntu-bug, but it says, that xwayland is not officially supported package and quit. Feel free to ask any logs or command output. The problem is, that the output is corrupted in a small windows, like popup menus that contains less than 4 lines, or certain applications that can make a window size small — like glxgears. This happens only for xwayland clients, native wayland apps are OK. See screenshot attached. ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Снимок экрана от 2018-12-24 13-38-38.png" https://bugs.launchpad.net/bugs/1809656/+attachment/5224638/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202018-12-24%2013-38-38.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809656 Title: Small windows output corrupted in XWayland clients To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1809656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766945] Re: (EFI on top of legacy install) choosing "replace" or "resize" options in partitioning may lead to an install failure
** Changed in: ubiquity (Ubuntu) Assignee: yehia elshenawy (yehia99) => cdattu...@gmail.com (dattu123) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766945 Title: (EFI on top of legacy install) choosing "replace" or "resize" options in partitioning may lead to an install failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1766945/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1024150] Re: Nautilus crashes when opening a new tab on a opening usb
** Changed in: nautilus 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/1024150 Title: Nautilus crashes when opening a new tab on a opening usb To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1024150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809655] Re: Items in the panel menu not aligned properly
I managed to correct this by adding the following CSS snippet to Yaru's
gnome-shell.css file:
.popup-menu StIcon {
width: 20px;
}
Maybe this should be added to the Yaru theme by default.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809655
Title:
Items in the panel menu not aligned properly
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1809655/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809655] [NEW] Items in the panel menu not aligned properly
Public bug reported: Items in the popup menu on the right hand side of the panel (panel- status-indicators-box menu) are not properly horizontally aligned. This is most visible when switching to a different font instead of the default Ubuntu font. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: yaru-theme-gnome-shell 18.10.6 [modified: usr/share/gnome-shell/theme/Yaru/gnome-shell.css] ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 24 13:37:41 2018 Dependencies: InstallationDate: Installed on 2018-12-01 (22 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809655 Title: Items in the panel menu not aligned properly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1809655/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 492598] Re: "extract here" doesn't refresh nautilus directory GUI
** Changed in: nautilus (Ubuntu) Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/492598 Title: "extract here" doesn't refresh nautilus directory GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/492598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
