[Bug 1811203] [NEW] upgrade from Ubuntu 16.04 to 18.04 failed
Public bug reported: The upload GUI said a new version was available and would I like to upgrade. I clicked yes and it went off and tried to do its thing but failed with: "Could not determine the upgrade An unresolvable problem occurred while calculating the upgrade. This can be caused by: * Upgrading to a pre-release version of Ubuntu * Running the current pre-release version of Ubuntu * Unofficial software packages not provided by Ubuntu If none of this applies, then please report this bug using the command 'ubuntu-bug ubuntu-release-upgrader-core' in a terminal." So I ran the requested command and ended up here... Now I do have some third party channels in /etc/apt/sources.list.d but there is no information in the GUI telling me what went wrong. I tried upgrading from the command line with: sudo apt-get upgrade sudo apt-get dist-upgrade Both of these seem to think I am already up to date. "0 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade." ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.26 ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: GNOME-Classic:GNOME Date: Thu Jan 10 07:34:04 2019 PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to xenial on 2019-01-10 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811203 Title: upgrade from Ubuntu 16.04 to 18.04 failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1811203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811204] [NEW] login console don't show up when switching from graphic.target to multi-user.target
Public bug reported: We found the login console, like tty1, can't show up when we did below command in 18.04.1. $ sudo systemctl isolate multi-user.target or $ sudo init 3 After above command, it will show a cursor with black screen. I could switch to tty1 with 'Ctrl+Alt+F1', and login into system. $ sudo systemctl isolate graphical.target or $ sudo init 5 It could show the login GUI. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Summary changed: - No login console when switching from graphic.target to multi-user.target + login console don't show up when switching from graphic.target to multi-user.target -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811204 Title: login console don't show up when switching from graphic.target to multi-user.target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811204] Re: login console don't show up when switching from graphic.target to multi-user.target
https://ubuntuforums.org/showthread.php?t=2330707 Here is the similar issue on 16.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811204 Title: login console don't show up when switching from graphic.target to multi-user.target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows
This bug has also started to appear for me. I found a quick temporary fix: Click on the top bar of the window and nouse clicks starts to work again. A possible factor that may caused problem to start appearing might be that i changed the font size from 12 to 10. The gnome do have lots of bugs so this isn't big surprise. Bugs like right scrollbar partly covering rightmost text character, dropdown list showing only one item (there are many), goetemp extension showing weather warnings always in german and the annoying font size change and rewrap when mouse hovering over a text block. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1181666 Title: gnome-shell randomly blocks mouse clicks from working in app windows To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1181666/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559491] Re: Unread notifications dot mostly never appears, even when it should
Maybe it's theme-related and improved in 18.10 with the introduction of Yaru? ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559491 Title: Unread notifications dot mostly never appears, even when it should To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1559491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1559491] Re: Inconsistent behaviour from the unread notifications dot
I feel that the dot reliability improved in 18.10/19.04 but am not sure exactly what version. ** Tags added: bionic ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Tags removed: wily ** Summary changed: - Inconsistent behaviour from the unread notifications dot + Unread notifications dot mostly never appears, even when it should -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1559491 Title: Unread notifications dot mostly never appears, even when it should To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1559491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811194] Re: raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic
** Description changed: - This issue cannot be reproduced across all of our SUTs, issue found on - node secchi. + This issue cannot be reproduced across all of our SUTs, issue found on node secchi (3 out of 3). + And sometimes on node amaura (2 out of 4) selftests: raw_skew WARNING: ADJ_OFFSET in progress, this will cause inaccurate results Estimating clock drift: 29.255(est) 30.529(act) [FAILED] Bail out! Pass 0 Fail 0 Xfail 0 Xpass 0 Skip 0 Error 0 1..0 not ok 1..7 selftests: raw_skew [FAIL] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Jan 10 03:58 seq - crw-rw 1 root audio 116, 33 Jan 10 03:58 timer + total 0 + crw-rw 1 root audio 116, 1 Jan 10 03:58 seq + crw-rw 1 root audio 116, 33 Jan 10 03:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 10 06:25:41 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': '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.15.0-43-generic root=UUID=9210e07a-fd34-474c-b77e-f7508f27e234 ro console=ttyS0,115200n8 RelatedPackageVersions: - linux-restricted-modules-4.15.0-43-generic N/A - linux-backports-modules-4.15.0-43-generic N/A - linux-firmware 1.173.2 + linux-restricted-modules-4.15.0-43-generic N/A + linux-backports-modules-4.15.0-43-generic N/A + linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2016 dmi.bios.vendor: Intel Corporation dmi.bios.version: SE5C620.86B.01.00.0294.101220161543 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.0294.101220161543:bd10/12/2016:svnIntelCorporation:pnS2600WFT:pvr:rvnIntelCorporation:rnS2600WFT:rvrH48104-410:cvn...:ct23:cvr..: dmi.product.family: Family dmi.product.name: S2600WFT dmi.product.version: dmi.sys.vendor: Intel Corporation -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811194 Title: raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1811194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811200] [NEW] Add Cavium ThunderX2 SoC UNCORE PMU driver
Public bug reported: [Impact] No driver for PMU of L3 cache controller (L3C) and the DDR4 Memory Controller (DMC) for Cavium ThunderX2 SoC [Test Case] sudo perf stat -a -e \ > uncore_dmc_0/cnt_cycles/,\ > uncore_dmc_0/data_transfers/,\ > uncore_dmc_0/read_txns/,\ > uncore_dmc_0/write_txns/ sleep 1 sudo perf stat -a -e \ > uncore_l3c_0/read_request/,\ > uncore_l3c_0/read_hit/,\ > uncore_l3c_0/inv_request/,\ > uncore_l3c_0/inv_hit/ sleep 1 sudo perf stat -a -e uncore_dmc_0/cnt_cycles/ sleep 1 [Fix] Backport patches 82975c46da perf: Export perf_event_update_userpage d6310a3f33 Documentation: perf: Add documentation for ThunderX2 PMU uncore driver 69c32972d5 drivers/perf: Add Cavium ThunderX2 SoC UNCORE PMU driver and enable CONFIG_THUNDERX2_PMU=m [Regression Risk] This driver only loaded when CAV901C in ACPI table, lowest risk for other platform. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ike Panhc (ikepanhc) 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/1811200 Title: Add Cavium ThunderX2 SoC UNCORE PMU driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743054] Re: Notifications - disappear, regression since xenial
** Changed in: hexchat (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/1743054 Title: Notifications - disappear, regression since xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1743054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811198] Re: virt-manager fail to start on huawei arm server
** Summary changed: - Remove arbitrary limit on socket_id/core_id + virt-manager fail to start on huawei arm server -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811198 Title: virt-manager fail to start on huawei arm server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1811198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811199] Re: package ca-certificates 20180409 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** 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/1811199 Title: package ca-certificates 20180409 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1811199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811199] [NEW] package ca-certificates 20180409 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: software center has a lot of issues installing almost everything I have tried so far ProblemType: Package DistroRelease: Ubuntu 18.04 Package: ca-certificates 20180409 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 Architecture: amd64 Date: Wed Jan 9 23:21:45 2019 DuplicateSignature: package:ca-certificates:20180409 Processing triggers for systemd (237-3ubuntu10.9) ... dpkg: error processing package openssl (--configure): package is in a very bad inconsistent state; you should ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2019-01-10 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6 SourcePackage: ca-certificates Title: package ca-certificates 20180409 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ca-certificates (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/1811199 Title: package ca-certificates 20180409 failed to install/upgrade: dependency problems - leaving triggers unprocessed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1811199/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811198] Re: Remove arbitrary limit on socket_id/core_id
https://www.redhat.com/archives/libvir-list/2018-August/msg00798.html While in most cases the values are going to be much smaller than our arbitrary 4096 limit, there is really no guarantee that would be the case: in fact, a few aarch64 servers have been spotted in the wild with core_id as high as 6216. Take advantage of virBitmap's ability to automatically alter its size at runtime to accomodate such values. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811198 Title: Remove arbitrary limit on socket_id/core_id To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1811198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811198] [NEW] Remove arbitrary limit on socket_id/core_id
Public bug reported: We met an issue when run virt-manager on huawei arm server with 18.04.1. Error polling connection 'qemu:///system': internal error: Socket 5418 can't be handled (max socket is 4095) ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New ** Attachment added: "error_virt.png" https://bugs.launchpad.net/bugs/1811198/+attachment/5228179/+files/error_virt.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811198 Title: Remove arbitrary limit on socket_id/core_id To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1811198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811194] 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/1811194 Title: raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1811194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811196] [NEW] raspi3-firmware includes old versions of the bootloader in bionic
Public bug reported: raspi3-firmware still includes old versions of the Raspberry Pi bootloader (*.elf, *.dat, bootcode.bin). Since these files are from December 2017, Pi models that use the second revision of the BCM2837 SoC (BCM2837B0) do not boot using raspi3-firmware since the bootloader included in this package is incompatible with the new SoC. For these models to boot, newer bootloader files are needed. disco already has a raspi3-firmware package based on the latest bootloader files, so it shouldn't be too hard to implement these into bionic. ** Affects: raspi3-firmware (Ubuntu) Importance: Undecided Status: New ** Description changed: raspi3-firmware still includes old versions of the Raspberry Pi bootloader (*.elf, *.dat, bootcode.bin). Since these files are from December 2017, Pi models that use the second revision of the BCM2837 SoC (BCM2837B0) do not boot using raspi3-firmware since the bootloader included in this package is incompatible with the new SoC. - For the Pi 3B+ to boot, newer bootloader files are needed. disco already - has a raspi3-firmware package based on the latest bootloader files, so - it shouldn't be too hard to implement these into bionic. + For these models to boot, newer bootloader files are needed. disco + already has a raspi3-firmware package based on the latest bootloader + files, so it shouldn't be too hard to implement these into bionic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811196 Title: raspi3-firmware includes old versions of the bootloader in bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/raspi3-firmware/+bug/1811196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811190] Re: package arc-theme (not installed) failed to install/upgrade: trying to overwrite '/usr/share/themes/Arc/cinnamon/cinnamon.css', which is also in package lite-themes 2.0-0130-linuxlit
The problem is that your base OS is not an official flavour. Linux lite has apparently packaged arc in something called lite-themes which clashes with the official arc package. You need to start from official ubuntu budgie media first. We cannot support other operating systems since they are of an unknown configuration ** Changed in: arc-theme (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/1811190 Title: package arc-theme (not installed) failed to install/upgrade: trying to overwrite '/usr/share/themes/Arc/cinnamon/cinnamon.css', which is also in package lite-themes 2.0-0130-linuxlite To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/arc-theme/+bug/1811190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811195] [NEW] Kernel in bionic hasn't received updates since April 2018 and is based on an EOL release of the Linux kernel
Public bug reported: In bionic and bionic-updates, the linux-raspi2 kernel hasn't received any updates since April 2018 and is based on Linux kernel 4.15, which is now past End of Life. This means it doesn't include the latest security patches and bug fixes. cosmic and cosmic-updates have a newer version of the linux-raspi2 kernel (4.18), but this has also reached End of Life. The linux-raspi2 kernel should be updated alongside the generic kernels, or should at least be based on a recent LTS version that is still receiving updates. ** Affects: linux-raspi2 (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/1811195 Title: Kernel in bionic hasn't received updates since April 2018 and is based on an EOL release of the Linux kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1811195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811194] [NEW] raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic
Public bug reported: This issue cannot be reproduced across all of our SUTs, issue found on node secchi. selftests: raw_skew WARNING: ADJ_OFFSET in progress, this will cause inaccurate results Estimating clock drift: 29.255(est) 30.529(act) [FAILED] Bail out! Pass 0 Fail 0 Xfail 0 Xpass 0 Skip 0 Error 0 1..0 not ok 1..7 selftests: raw_skew [FAIL] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-43-generic 4.15.0-43.46 ProcVersionSignature: User Name 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 10 03:58 seq crw-rw 1 root audio 116, 33 Jan 10 03:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 10 06:25:41 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': '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.15.0-43-generic root=UUID=9210e07a-fd34-474c-b77e-f7508f27e234 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.15.0-43-generic N/A linux-backports-modules-4.15.0-43-generic N/A linux-firmware 1.173.2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/12/2016 dmi.bios.vendor: Intel Corporation dmi.bios.version: SE5C620.86B.01.00.0294.101220161543 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.0294.101220161543:bd10/12/2016:svnIntelCorporation:pnS2600WFT:pvr:rvnIntelCorporation:rnS2600WFT:rvrH48104-410:cvn...:ct23:cvr..: dmi.product.family: Family 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 bionic 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/1811194 Title: raw_skew in timer from the ubuntu_kernel_selftests failed on Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1811194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811192] Re: package libreoffice-common (not installed) failed to install/upgrade: 正试图覆盖 /usr/bin/soffice，它同时被包含于软件包 openoffice-debian-menus 4.1.6-9790
I'm the reporter of this bug, before it happens, i installed "apache openoffice" and "wps office", I wonder if this two software lead to the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811192 Title: package libreoffice-common (not installed) failed to install/upgrade: 正试图覆盖 /usr/bin/soffice，它同时被包含于软件包 openoffice-debian-menus 4.1.6-9790 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1811192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811193] [NEW] can't upgrade to 18.10
Public bug reported: when i am upgrading my ubuntu from 18.04 to 18.10 it didn't upgraded ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.29 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 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Jan 10 11:40:12 2019 InstallationDate: Installed on 2018-12-12 (28 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2019-01-10 (0 days ago) VarLogDistupgradeTermlog: mtime.conffile..etc.update-manager.release-upgrades: 2019-01-09T00:27:36.160386 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811193 Title: can't upgrade to 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1811193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811192] [NEW] package libreoffice-common (not installed) failed to install/upgrade: 正试图覆盖 /usr/bin/soffice，它同时被包含于软件包 openoffice-debian-menus 4.1.6-9790
Public bug reported: OS info: Ubuntu18.10 GNOME Shell 3.30.1 libreoffice: 已安装：1:6.1.3-0ubuntu0.18.10.2 候选： 1:6.1.3-0ubuntu0.18.10.2 when execute command "sudo apt install libreoffice" ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libreoffice-common (not installed) 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 Date: Thu Jan 10 14:05:54 2019 ErrorMessage: 正试图覆盖 /usr/bin/soffice，它同时被包含于软件包 openoffice-debian-menus 4.1.6-9790 InstallationDate: Installed on 2019-01-03 (7 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180521) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: libreoffice Title: package libreoffice-common (not installed) failed to install/upgrade: 正试图覆盖 /usr/bin/soffice，它同时被包含于软件包 openoffice-debian-menus 4.1.6-9790 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811192 Title: package libreoffice-common (not installed) failed to install/upgrade: 正试图覆盖 /usr/bin/soffice，它同时被包含于软件包 openoffice-debian-menus 4.1.6-9790 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1811192/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805607] Re: Power leakage at S5 with Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter
** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805607 Title: Power leakage at S5 with Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1805607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811190] [NEW] package arc-theme (not installed) failed to install/upgrade: trying to overwrite '/usr/share/themes/Arc/cinnamon/cinnamon.css', which is also in package lite-themes 2.0-0130-linuxl
Public bug reported: can see boxes and selection after i upgraded to bionic 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: arc-theme (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: arc-theme:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Thu Jan 10 00:19:19 2019 DpkgTerminalLog: Preparing to unpack .../arc-theme_20180114-1ubuntu1_all.deb ... Unpacking arc-theme (20180114-1ubuntu1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/arc-theme_20180114-1ubuntu1_all.deb (--unpack): trying to overwrite '/usr/share/themes/Arc/cinnamon/cinnamon.css', which is also in package lite-themes 2.0-0130-linuxlite ErrorMessage: trying to overwrite '/usr/share/themes/Arc/cinnamon/cinnamon.css', which is also in package lite-themes 2.0-0130-linuxlite InstallationDate: Installed on 2017-06-28 (560 days ago) InstallationMedia: Linux Lite 3.2 - Release amd64 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: arc-theme Title: package arc-theme (not installed) failed to install/upgrade: trying to overwrite '/usr/share/themes/Arc/cinnamon/cinnamon.css', which is also in package lite-themes 2.0-0130-linuxlite UpgradeStatus: Upgraded to xenial on 2019-01-08 (1 days ago) ** Affects: arc-theme (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/1811190 Title: package arc-theme (not installed) failed to install/upgrade: trying to overwrite '/usr/share/themes/Arc/cinnamon/cinnamon.css', which is also in package lite-themes 2.0-0130-linuxlite To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/arc-theme/+bug/1811190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1745990] Re: nautilus don't show all items in context menu "new document" and "scripts"
** Changed in: nautilus Status: Unknown => Confirmed ** Changed in: nautilus Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1745990 Title: nautilus don't show all items in context menu "new document" and "scripts" To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1745990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1801227] Re: smbc_opendir returns EEXIST if login credentials are incorrect, breaking SMB shares in Kodi
samba 2:4.7.6+dfsg~ubuntu-0ubuntu2.6 (https://launchpad.net/ubuntu/+source/samba/2:4.7.6+dfsg~ubuntu- 0ubuntu2.6) in the proposed pocket was used for verification. Follow the testing steps in https://code.launchpad.net/~kstenerud/ubuntu/+source/samba/+git/samba/+merge/359602 except instead of adding the PPA, add the sources list entry: deb http://archive.ubuntu.com/ubuntu bionic-proposed main ** Changed in: samba (Ubuntu Bionic) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801227 Title: smbc_opendir returns EEXIST if login credentials are incorrect, breaking SMB shares in Kodi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1801227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1802050] Re: Kernel module crash 4.18.0-10 after upgrade from 18.04 to 18.10
redhat fixed it https://bugzilla.redhat.com/show_bug.cgi?id=1570493 debian followed also with the same patch https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901919 still affects me: kubuntu 18.10 linux-image-4.18.0-13-generic = 4.18.0-13.14 nvidia-driver-390 = 390.87-0ubuntu1 ** Bug watch added: Red Hat Bugzilla #1570493 https://bugzilla.redhat.com/show_bug.cgi?id=1570493 ** Bug watch added: Debian Bug tracker #901919 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901919 ** Package changed: linux (Ubuntu) => nvidia-graphics-drivers-390 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802050 Title: Kernel module crash 4.18.0-10 after upgrade from 18.04 to 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1802050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806534] Re: Fix USB2 device wrongly detected as USB1
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806534 Title: Fix USB2 device wrongly detected as USB1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
Hi all, Just wanted to add my experience with this. I also have found that my Synaptics touchpad becomes unresponsive after waking from a suspend. It isn't restored by a modprobe -r psmouse / modprobe psmouse. The only thing that restores it is a shutdown (without -r option) followed by a fresh boot. I noticed also that, when it is showing this unresponsive touchpad symptom, sudo cat /dev/input/event8 | hexdump produces nothing at all when i move my finger around on the touchpad (event8 is the touchpad in my system, as shown by /proc/bus/input/devices). Yet, doing: sudo cat /dev/input/event16 | hexdump (which is my usb wireless mouse) does produce output when I move my mouse around. I'm not very familiar with kernel, drivers, firmware, etc. I did think the bit about /dev/input/event8 was interesting though, but I'm not sure what to do with that information. If anyone is interested, please feel free to suggest a set of commands and their output you might want to see, or procedures to try. I hope this new data point is useful. Thanks in advance! Henry Some other things: henry@henry-gs65:~$ uname -a Linux henry-gs65 4.15.0-43-generic #46-Ubuntu SMP Thu Dec 6 14:45:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux henry@henry-gs65:~$ sudo lshw | head -n 25 henry-gs65 description: Notebook product: GS65 Stealth Thin 8RF (16Q2.1) vendor: Micro-Star International Co., Ltd. version: REV:1.0 serial: 9S716Q211405ZI883 width: 64 bits capabilities: smbios-3.1 dmi-3.1 smp vsyscall32 configuration: boot=normal chassis=notebook family=GS sku=16Q2.1 uuid=FCEFF7B9-5244-47ED-B96D-2A2CF506C220 *-core description: Motherboard product: MS-16Q2 vendor: Micro-Star International Co., Ltd. physical id: 0 version: REV:1.0 serial: BSS-0123456789 slot: Default string *-firmware description: BIOS vendor: American Megatrends Inc. physical id: 1 version: E16Q2IMS.110 date: 10/08/2018 size: 64KiB capacity: 15MiB henry@henry-gs65:~$ grep -B 1 -A 10 Synaptics /proc/bus/input/devices I: Bus=0011 Vendor=0002 Product=0001 Version= N: Name="PS/2 Synaptics TouchPad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input34 U: Uniq= H: Handlers=mouse0 event8 B: PROP=1 B: EV=7 B: KEY=7 0 0 0 0 B: REL=3 henry@henry-gs65:~$ journalctl -b 0 | grep -i touchpad | grep kernel Jan 06 21:02:58 henry-gs65 kernel: psmouse serio1: synaptics: Your touchpad (PNP: SYN150d SYN1500 SYN0002 PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1 and report this to linux-in...@vger.kernel.org. Jan 06 21:02:58 henry-gs65 kernel: psmouse serio1: synaptics: Touchpad model: 1, fw: 8.16, id: 0x1e2b1, caps: 0xf00123/0x840300/0x12e800/0x40, board id: 3414, fw id: 2667658 Jan 06 21:02:58 henry-gs65 kernel: input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input6 Jan 09 19:40:09 henry-gs65 kernel: psmouse serio1: synaptics: Your touchpad (PNP: SYN150d SYN1500 SYN0002 PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1 and report this to linux-in...@vger.kernel.org. Jan 09 19:40:09 henry-gs65 kernel: psmouse serio1: synaptics: Touchpad model: 1, fw: 8.16, id: 0x1e2b1, caps: 0xf00123/0x840300/0x12e800/0x40, board id: 3414, fw id: 2667658 Jan 09 19:40:09 henry-gs65 kernel: input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input24 Jan 09 19:43:16 henry-gs65 kernel: input: PS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input26 Jan 09 19:49:15 henry-gs65 kernel: input: PS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input28 Jan 09 20:15:08 henry-gs65 kernel: input: PS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input30 Jan 09 20:15:21 henry-gs65 kernel: psmouse serio1: synaptics: Your touchpad (PNP: SYN150d SYN1500 SYN0002 PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting psmouse.synaptics_intertouch to 1 and report this to linux-in...@vger.kernel.org. Jan 09 20:15:21 henry-gs65 kernel: psmouse serio1: synaptics: Touchpad model: 1, fw: 8.16, id: 0x1e2b1, caps: 0xf00123/0x840300/0x12e800/0x40, board id: 3414, fw id: 2667658 Jan 09 20:15:21 henry-gs65 kernel: input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input32 Jan 09 20:30:49 henry-gs65 kernel: input: PS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input34 Jan 06 21:02:58 henry-gs65 kernel: psmouse serio1: synaptics: Your touchpad (PNP: SYN150d SYN1500 SYN0002 PNP0f13) says it can support a different bus. If i2c-hid and hid-rmi are not used, you might want to try setting
[Bug 1709877] Comment bridged from LTC Bugzilla
--- Comment From sathe...@in.ibm.com 2019-01-10 00:15 EDT--- (In reply to comment #33) > This is just the libvirt as in Xenial plus the requested patches. > I don't see anything obvious to be wrong except if the requested changes > were incomplete. > > Could it be that the use case you are testing is affected by two things: > 1. the one we are trying to fix here > 2. a second one that is exposed once the first is fixed? > Looks like the we are hitting the second one, from the reference of this related bz comment for 17.04, https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1667805/comments/9, cpu hotplug feature for pseries was not complete/had to use different approach(device_add instead of cpu-add) in qemu 2.5 version which xenial and due to the fix of initial issue reported here, we hit now with actual failure, though error message here is misleading. >From my previous bug reports, have learnt that vcpu hotplug for pseries works >from zesty(17.04), reference, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670315 and I could not find any working reference for vcpu hotplug on xenial for pseries neither supported/not-supported statement from ubuntu wiki aswell. If there are no plans to support vcpu hotplug for pseries in xenial, my suggestion would be having the error statement while trying hotplug be improved saying hotplug is not supported with version of qemu/libvirt, or we can bring in all the necessary changes required for vcpu hotplug in xenial aswell. please advice. Thanks a lot for the continued support on this. Regards, -Satheesh > In that case one would have to identify the further changes that would be > needed. > If you or one of your dev's knows about extra changes needed for #2 let me > know and we can give it a try. > > But given that this seems more Lab than Field issue (there were no other > examples so far) this gets more and more complex but I wonder for what. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1709877 Title: CPU hotplug fails in the system with empty numa nodes, "Invalid value '0-1,16-17' for 'cpuset.mems': Invalid argument" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1709877/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811188] Re: package gimp 2.8.22-1 failed to install/upgrade: installed gimp package post-installation 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/1811188 Title: package gimp 2.8.22-1 failed to install/upgrade: installed gimp package post-installation script subprocess returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1811188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811188] [NEW] package gimp 2.8.22-1 failed to install/upgrade: installed gimp package post-installation script subprocess returned error exit status 127
Public bug reported: Python version compatibility issue, I think. Not sure which Python package package needs to be fixed ProblemType: Package DistroRelease: Ubuntu 18.04 Package: gimp 2.8.22-1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jan 10 10:31:05 2019 DuplicateSignature: package:gimp:2.8.22-1 Setting up libccolamd2:amd64 (1:5.1.2-2) ... dpkg: error processing package python-requests (--configure): package is in a very bad inconsistent state; you should ErrorMessage: installed gimp package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2018-05-28 (226 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 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.3ubuntu0.1 SourcePackage: gimp Title: package gimp 2.8.22-1 failed to install/upgrade: installed gimp package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gimp (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/1811188 Title: package gimp 2.8.22-1 failed to install/upgrade: installed gimp package post-installation script subprocess returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1811188/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807334] Re: Add support for ALC3277 codec on new Dell edge gateways
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807334 Title: Add support for ALC3277 codec on new Dell edge gateways To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1807334/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798790] Re: Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it)
Uncommenting this line worked for me. This bug occurred after a fresh install of 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/1798790 Title: Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811187] [NEW] Upgrade from 16.04 to 18.04 fails, can't tell where the problem is
Public bug reported: I don't know what to check to see where my process is failing, so apologies for a possible duplicate bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.26 ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Wed Jan 9 20:38:55 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2016-10-10 (821 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to xenial on 2019-01-10 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811187 Title: Upgrade from 16.04 to 18.04 fails, can't tell where the problem is To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1811187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811182] 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/1811182 Title: Ubuntu crashed totally. Nothing responded. Could not even shut down. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1740804] Re: Remove old vte package from Ubuntu
** Changed in: vte (Ubuntu) Status: Expired => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1740804 Title: Remove old vte package from Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1740804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1740804] Re: Remove old vte package from Ubuntu
[Expired for vte (Ubuntu) because there has been no activity for 60 days.] ** Changed in: vte (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/1740804 Title: Remove old vte package from Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vte/+bug/1740804/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782890] Re: package thunderbird 1:52.8.0+build1-0ubuntu0.18.04.1 failed to install/upgrade: impossible de copier les données extraites pour « ./usr/lib/thunderbird/libxul.so » vers « /usr/lib/th
[Expired for thunderbird (Ubuntu) because there has been no activity for 60 days.] ** Changed in: thunderbird (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/1782890 Title: package thunderbird 1:52.8.0+build1-0ubuntu0.18.04.1 failed to install/upgrade: impossible de copier les données extraites pour « ./usr/lib/thunderbird/libxul.so » vers « /usr/lib/thunderbird/libxul.so.dpkg-new » : fin de fichier ou de flux inattendue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1782890/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760424] Re: FF crashing on opening a file dialogue
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (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/1760424 Title: FF crashing on opening a file dialogue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1760424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785991] Re: package thunderbird-locale-ru 1:52.9.1+build3-0ubuntu0. 18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con
[Expired for thunderbird (Ubuntu) because there has been no activity for 60 days.] ** Changed in: thunderbird (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/1785991 Title: package thunderbird-locale-ru 1:52.9.1+build3-0ubuntu0. 18.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1785991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 218781] [Review update] master
*** This bug is a duplicate of bug 192630 *** https://bugs.launchpad.net/bugs/192630 Review in progress for https://review.opencontrail.org/48589 Submitter: amudha ramachandran (amu...@juniper.net) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/218781 Title: qemulator.py crashed with TypeError in on_treeviewBootimages_cursor_changed() To manage notifications about this bug go to: https://bugs.launchpad.net/juniperopenstack/+bug/218781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 218781] [Review update] master
*** This bug is a duplicate of bug 192630 *** https://bugs.launchpad.net/bugs/192630 Review in progress for https://review.opencontrail.org/48558 Submitter: amudha ramachandran (amu...@juniper.net) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/218781 Title: qemulator.py crashed with TypeError in on_treeviewBootimages_cursor_changed() To manage notifications about this bug go to: https://bugs.launchpad.net/juniperopenstack/+bug/218781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811182] [NEW] Ubuntu crashed totally. Nothing responded. Could not even shut down.
Public bug reported: Ubuntu MATE 18.10 on AMD 64-bit machine. Working fine until suddenly Ubuntu stops responding to the mouse buttons or keyboard (PS2 keyboard). No warning. Was using VueScan and running two bash scripts using tesseract and VisualWorks. Chrome and Pluma running but not being used. No other symptoms visible. This is the second time in a week that Ubuntu crashed in the same way and I have had to do a hardware reset to restart. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 2268 F pulseaudio /dev/snd/controlC0: robert 2268 F pulseaudio CurrentDesktop: MATE Date: Wed Jan 9 22:53:15 2019 InstallationDate: Installed on 2018-12-16 (24 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=737f341d-e214-40a2-b2a3-5a8b1b7ed378 ro quiet splash vt.handoff=1 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: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (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/1811182 Title: Ubuntu crashed totally. Nothing responded. Could not even shut down. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811182/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810630] Re: Boot up is hung on a purple screen
Just run: dpkg -l > allpackages.txt and then send us the file 'allpackages.txt'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810630 Title: Boot up is hung on a purple screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1810630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1810630] Re: Boot up is hung on a purple screen
Thank you for the guidance. I actually installed these PPA's early on, in an effort to get around hanging at the purple screen on boot. I was unable to use ppa-purge. Perhaps my syntax was wrong? Instead, I have removed all the PPAs through Software & Updates. Or was there just one PPA that needed to be removed? I restarted the computer, and it again hung at the purple screen when booting up. I think all the PPA's are gone, but cannot be sure. Is there an easy way to find out? Thank you Alex On Wed, Jan 9, 2019 at 7:55 PM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > Oh! I failed to notice right at the beginning of this bug that you are > using unsupported graphics packages from a PPA. That is almost certainly > the problem. It also means this bug is 'Invalid' for standard Ubuntu. > > Please remove the PPAs from your system using 'ppa-purge'. We can't > support PPAs. If you have any problems after that then please log a new > bug. > > In an unrelated note, if your system has received any recent updates > then that should include a fix for bug 1727356 (mutter >= > 3.28.3-2~ubuntu18.04.2). That means you can comment out this workaround: > > WaylandEnable=false > > and you will then get Wayland login options. > > ** Changed in: ubuntu >Status: Incomplete => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1810630 > > Title: > Boot up is hung on a purple screen > > Status in Ubuntu: > Invalid > > Bug description: > Despite updating drivers for video through xorg, display cannot change > from 1024x768. Default video card is still listed as llvmpipe. > > 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: Sat Jan 5 15:19:12 2019 > DistUpgraded: Fresh install > DistroCodename: bionic > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated > Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) > Subsystem: Intel Corporation Mobile 945GM/GMS, 943/940GML Express > Integrated Graphics Controller [8086:7270] > Subsystem: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express > Integrated Graphics Controller [8086:7270] > InstallationDate: Installed on 2018-12-24 (12 days ago) > InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 > (20180725) > MachineType: Apple Inc. MacBook2,1 > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic > root=UUID=2d93d825-1bcb-4155-aad5-cfdb5dce95ab ro quiet splash nomodeset > vt.handoff=1 > SourcePackage: xorg > Symptom: display > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 06/27/07 > dmi.bios.vendor: Apple Inc. > dmi.bios.version: MB21.88Z.00A5.B07.0706270922 > dmi.board.asset.tag: Base Board Asset Tag > dmi.board.name: Mac-F4208CAA > dmi.board.vendor: Apple Inc. > dmi.board.version: PVT > dmi.chassis.asset.tag: Asset Tag > dmi.chassis.type: 10 > dmi.chassis.vendor: Apple Inc. > dmi.chassis.version: Mac-F4208CAA > dmi.modalias: > dmi:bvnAppleInc.:bvrMB21.88Z.00A5.B07.0706270922:bd06/27/07:svnAppleInc.:pnMacBook2,1:pvr1.0:rvnAppleInc.:rnMac-F4208CAA:rvrPVT:cvnAppleInc.:ct10:cvrMac-F4208CAA: > dmi.product.family: MacBook > dmi.product.name: MacBook2,1 > dmi.product.version: 1.0 > dmi.sys.vendor: Apple Inc. > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.96+git1901040630.403f3c~oibaf~b > version.libgl1-mesa-dri: libgl1-mesa-dri > 19.0~git1901050730.884737~oibaf~b > version.libgl1-mesa-glx: libgl1-mesa-glx > 19.0~git1901050730.884737~oibaf~b > 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.1.99+git1812281934.803f87~oibaf~b > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git1812031933.e5ff8e~oibaf~b > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau > 1:1.0.15+git1812100734.a4283f~oibaf~b > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+bug/1810630/+subscriptions > -- Alexander A Theiler, MHS, MS, PA-C CAQ in Emergency Medicine -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810630 Title: Boot
[Bug 1811159] 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/1811159 Title: temporary freeze under opengl, not xrender, 18.10 & kernel 4.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 559331] Re: Permanent "Printer-out-of-paper" message.
im having this issue ... canon MX490 Linux Mint 18.2 Sonya \n \l if i comment out the "media" lines in printers.conf and restart the service.. the printer error goes away.. but as soon as i send a test print to the printer i get a pop up saying the paper is empty and cups overwrites the conf file and puts the 2 media lines back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/559331 Title: Permanent "Printer-out-of-paper" message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/559331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811094] Re: iptables connlimit allows more connections than the limit when using multiple CPUs
** Description changed:
- The following iptables connlimit rule can be breached
- with a multithreaded client and network device driver,
- due to a race in the conncount/connlimit code:
+ [Impact]
- # iptables -A INPUT -p tcp -m tcp --syn --dport \
- -m connlimit --connlimit-above 2000 --connlimit-mask 0 \
- -j DROP
+ * The iptables connection count/limit rules can be breached
+with multithreaded network driver/server/client (common)
+due to a race in the conncount/connlimit code.
- NOTE: Patches will be sent to the kernel-team mailing list
- and more details/testing will be provided later today.
+ * For example:
+
+# iptables -A INPUT -p tcp -m tcp --syn --dport \
+ -m connlimit --connlimit-above 2000 --connlimit-mask 0 \
+ -j DROP
+
+ * The fix is a backport from an upstream commit that resolves
+the problem (plus dependencies for a cleaner backport) that
+address the race condition:
+
+commit b36e4523d4d5 ("netfilter: nf_conncount: fix garbage
+collection confirm race").
+
+ [Test Case]
+
+ * Server-side: (relevant kernel side)
+(limit TCP port to only 2000 connections)
+
+# iptables -A INPUT -p tcp -m tcp --syn --dport \
+ -m connlimit --connlimit-above 2000 --connlimit-mask 0 \
+ -j DROP
+
+# ulimit -SHn 65000 # increase number of open files
+# ruby server.rb # multi-threaded server
+
+ * Client-side:
+
+# ulimit -SHn 65000
+# ruby client.rb<# threads>
+
+
+ * Results with Original kernel:
+(client achieves target of 6000 connections > limit of 2000 connections)
+
+# ruby client.rb 10.230.56.100 6000 3
+1
+2
+3
+<...>
+6000
+Target reached. Thread finishing
+6001
+Target reached. Thread finishing
+6002
+Target reached. Thread finishing
+Threads done. 6002 connections
+press enter to exit
+
+ * Results with Modified kernel:
+(client is limited to 2000 connections, and times out afterward)
+
+# ruby client.rb 10.230.56.100 6000 3
+1
+2
+3
+<...>
+2000
+<... blocks for a few minutes ...>
+failed to create connection: Connection timed out - connect(2) for
"10.230.56.100" port
+failed to create connection: Connection timed out - connect(2) for
"10.230.56.100" port
+failed to create connection: Connection timed out - connect(2) for
"10.230.56.100" port
+Threads done. 2000 connections
+press enter to exit
+
+ * Test cases possibly available upon request,
+depending on original author's permission.
+
+ [Regression Potential]
+
+ * The patchset has been reviewed by a netfilter maintainer [1] in
+stable mailing list, and was considered OK for 4.14, and that's
+essentially the same backport for 4.15 and 4.4.
+
+ * The changes are limited to netfilter conncount/connlimit (names
+change between older/newer kernel versions).
+
+ [Other Info]
+
+ * The backport for 4.14 [2] is applied as of 4.14.92.
+
+ [1] https://www.spinics.net/lists/stable/msg276883.html
+ [2] https://www.spinics.net/lists/stable/msg276910.html
** Description changed:
[Impact]
- * The iptables connection count/limit rules can be breached
-with multithreaded network driver/server/client (common)
-due to a race in the conncount/connlimit code.
+ * The iptables connection count/limit rules can be breached
+ with multithreaded network driver/server/client (common)
+ due to a race in the conncount/connlimit code.
- * For example:
+ * For example:
-# iptables -A INPUT -p tcp -m tcp --syn --dport \
- -m connlimit --connlimit-above 2000 --connlimit-mask 0 \
- -j DROP
+ # iptables -A INPUT -p tcp -m tcp --syn --dport \
+ -m connlimit --connlimit-above 2000 --connlimit-mask 0 \
+ -j DROP
- * The fix is a backport from an upstream commit that resolves
-the problem (plus dependencies for a cleaner backport) that
-address the race condition:
+ * The fix is a backport from an upstream commit that resolves
+ the problem (plus dependencies for a cleaner backport) that
+ address the race condition:
-commit b36e4523d4d5 ("netfilter: nf_conncount: fix garbage
-collection confirm race").
+ commit b36e4523d4d5 ("netfilter: nf_conncount: fix garbage
+ collection confirm race").
[Test Case]
- * Server-side: (relevant kernel side)
-(limit TCP port to only 2000 connections)
+ * Server-side: (relevant kernel side)
+ (limit TCP port to only 2000 connections)
-# iptables -A INPUT -p tcp -m tcp --syn --dport \
- -m connlimit --connlimit-above 2000 --connlimit-mask 0 \
- -j DROP
+ # iptables -A INPUT -p tcp -m tcp --syn --dport \
+ -m connlimit --connlimit-above 2000 --connlimit-mask 0 \
+ -j DROP
-# ulimit -SHn 65000 # increase number of open files
-# ruby server.rb # multi-threaded
[Bug 1810998] Re: CPU hard lockup with rigorous writes to NVMe drive
Patch series posted to kernel-team mailing list: [SRU B][PATCH 00/13] blk-wbt: fix for LP#1810998 https://lists.ubuntu.com/archives/kernel-team/2019-January/097675.html [SRU C][PATCH 0/8] blk-wbt: fix for LP#1810998 https://lists.ubuntu.com/archives/kernel-team/2019-January/097689.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810998 Title: CPU hard lockup with rigorous writes to NVMe drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810998/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1485955]
Jim Raykowski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/47e9db9c8490167e265b17ae44bb790a160703b5%5E%21 tdf#82504 writer table cell background color SvxColorItem uno function It will be available in 6.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1485955 Title: [upstream] EDITING: Background Color button from Table toolbar should change cell background instead of paragraph background To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1485955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1485955] Re: [upstream] EDITING: Background Color button from Table toolbar should change cell background instead of paragraph background
** Changed in: df-libreoffice 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/1485955 Title: [upstream] EDITING: Background Color button from Table toolbar should change cell background instead of paragraph background To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1485955/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810998] Re: CPU hard lockup with rigorous writes to NVMe drive
** Description changed:
- [NOTE]
-
- * Patches will be sent to the kernel-team mailing list
- once the test kernel has been verified by the reporter.
-
[Impact]
* Users may experience cpu hard lockups when performing
rigorous writes to NVMe drives.
* The fix addresses an scheduling issue in the original
implementation of wbt/writeback throttling
* The fix is commit 2887e41b910b ("blk-wbt: Avoid lock
contention and thundering herd issue in wbt_wait"),
plus its fix commit 38cfb5a45ee0 ("blk-wbt: improve
waking of tasks").
* There are additional commits to help with a cleaner
backport and future maintenance:
- Cosmic: total of 8 clean cherry picks.
- Bionic: total of 13 commits, 9 clean cherry-picks
and 4 backports, which are just changes to context
lines (i.e. refresh) without any functional changes
in the backport itself.
[Test Case]
* This command has been reported to reproduce the problem:
$ sudo iozone -R -s 5G -r 1m -S 2048 -i 0 -G -c -o -l 128 -u 128 -t
128
* It generates stack traces as below in the original kernel,
-and does not generate them in the modified/patched kernel.
+ and does not generate them in the modified/patched kernel.
- * The user/reporter verified the test kernel with these patches
-resolved the problem.
+ * The user/reporter verified the test kernel with these patches
+ resolved the problem.
- * The developer verified in 2 systems (4-core and 24-core but
-no NVMe) for regressions, and no error messages were logged
-to dmesg.
+ * The developer verified in 2 systems (4-core and 24-core but
+ no NVMe) for regressions, and no error messages were logged
+ to dmesg.
[Regression Potential]
* The commits have been verified for fixes in later commits in
linux-next as of 2019-01-08 and all known fix commits are in.
* The regression potential is mostly contained in the writeback
throttling (block/blk-wbt.*), as almost all of the 13 patches
change exclusively that, except for 4 of them (2 of which are
sysfs):
- blk-rq-qos: refactor out common elements of blk-wbt (block/)
- block: Protect less code with sysfs_lock in blk_{un,}register_queue()
(blk-sysfs.c)
- block: Protect less code with sysfs_lock in blk_{un,}register_queue()
(blk-{mq-}sysfs.c)
- block: pass struct request instead of struct blk_issue_stat to wbt
(block/, still mostly blk-wbt.*)
[Other Info]
* Alternatively, it is probably possible to introduce just the
two commits that fix this with some changes to their code in
the backport, but since the 'blk-rq-qos: refactor ..' commit
may become a dependency for many additional/future fixes, it
seemed interesting to pull it in earlier in the 18.04 cycle.
* The problem has been introduced with the blk-wbt mechanism,
in v4.10-rc1, and the fix commits in v4.19-rc1 and -rc2,
so only Bionic and Cosmic needs this.
[Stack Traces]
[ 393.628647] NMI watchdog: Watchdog detected hard LOCKUP on cpu 30
...
[ 393.628704] CPU: 30 PID: 0 Comm: swapper/30 Tainted: P OE 4.15.0-20-generic
#21-Ubuntu
...
[ 393.628720] Call Trace:
[ 393.628721]
[ 393.628724] enqueue_task_fair+0x6c/0x7f0
[ 393.628726] ? __update_load_avg_blocked_se.isra.37+0xd1/0x150
[ 393.628728] ? __update_load_avg_blocked_se.isra.37+0xd1/0x150
[ 393.628731] activate_task+0x57/0xc0
[ 393.628735] ? sched_clock+0x9/0x10
[ 393.628736] ? sched_clock+0x9/0x10
[ 393.628738] ttwu_do_activate+0x49/0x90
[ 393.628739] try_to_wake_up+0x1df/0x490
[ 393.628741] default_wake_function+0x12/0x20
[ 393.628743] autoremove_wake_function+0x12/0x40
[ 393.628744] __wake_up_common+0x73/0x130
[ 393.628745] __wake_up_common_lock+0x80/0xc0
[ 393.628746] __wake_up+0x13/0x20
[ 393.628749] __wbt_done.part.21+0xa4/0xb0
[ 393.628749] wbt_done+0x72/0xa0
[ 393.628753] blk_mq_free_request+0xca/0x1a0
[ 393.628755] blk_mq_end_request+0x48/0x90
[ 393.628760] nvme_complete_rq+0x23/0x120 [nvme_core]
[ 393.628763] nvme_pci_complete_rq+0x7a/0x130 [nvme]
[ 393.628764] __blk_mq_complete_request+0xd2/0x140
[ 393.628766] blk_mq_complete_request+0x18/0x20
[ 393.628767] nvme_process_cq+0xe1/0x1b0 [nvme]
[ 393.628768] nvme_irq+0x23/0x50 [nvme]
[ 393.628772] __handle_irq_event_percpu+0x44/0x1a0
[ 393.628773] handle_irq_event_percpu+0x32/0x80
[ 393.628774] handle_irq_event+0x3b/0x60
[ 393.628778] handle_edge_irq+0x7c/0x190
[ 393.628779] handle_irq+0x20/0x30
[ 393.628783] do_IRQ+0x46/0xd0
[ 393.628784] common_interrupt+0x84/0x84
[ 393.628785]
...
[ 393.628794] ? cpuidle_enter_state+0x97/0x2f0
[ 393.628796] cpuidle_enter+0x17/0x20
[ 393.628797] call_cpuidle+0x23/0x40
[ 393.628798] do_idle+0x18c/0x1f0
[ 393.628799] cpu_startup_entry+0x73/0x80
[ 393.628802] start_secondary+0x1a6/0x200
[ 393.628804] secondary_startup_64+0xa5/0xb0
[
[Bug 1811159] Re: temporary freeze under opengl, not xrender, 18.10 & kernel 4.20
It appears the nouveau kernel driver is crashing, which may well be the main problem here. And thanks for testing kernel 4.20 already. As a workaround please try installing the official Nvidia driver. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Package changed: xorg-server (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/1811159 Title: temporary freeze under opengl, not xrender, 18.10 & kernel 4.20 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811096] Re: gnome-shell[2843]: The offending signal was destroy on StBoxLayout 0x5606a3267650.
Those stack traces in the log are unfortunately likely unrelated to any gnome-shell freeze. And I assume the freeze is the main issue that you're reporting(?). Please start by uninstalling these extensions: 'mediapla...@patapon.info' 'system-moni...@paradoxxx.zero.gmail.com' reboot and then tell us if the problem goes away. Please also clarify what the problem is exactly. Is it a full screen freeze? ** No longer affects: wayland (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811096 Title: gnome-shell[2843]: The offending signal was destroy on StBoxLayout 0x5606a3267650. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1811096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811084] Re: Screen flickers after opening lid...
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811084 Title: Screen flickers after opening lid... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1811084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810861] Re: USB type C audio adapter (from a Pixel 3) doesn't produce any sound
No, don't put a semicolon (;) in front. The semicolon is a comment character which tells the system to ignore everything after it. Just use: realtime-scheduling = no anywhere in that file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810861 Title: USB type C audio adapter (from a Pixel 3) doesn't produce any sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810630] Re: Boot up is hung on a purple screen
Oh! I failed to notice right at the beginning of this bug that you are using unsupported graphics packages from a PPA. That is almost certainly the problem. It also means this bug is 'Invalid' for standard Ubuntu. Please remove the PPAs from your system using 'ppa-purge'. We can't support PPAs. If you have any problems after that then please log a new bug. In an unrelated note, if your system has received any recent updates then that should include a fix for bug 1727356 (mutter >= 3.28.3-2~ubuntu18.04.2). That means you can comment out this workaround: WaylandEnable=false and you will then get Wayland login options. ** Changed in: 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/1810630 Title: Boot up is hung on a purple screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1810630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1514057] Re: Incorrect(?) reporting of freeness of third-party nVidia drivers from graphic-drivers PPA
I believe this is due to a simplistic handling of "freeness" in
UbuntuDrivers.detect._is_package_free() – any package not from
restricted or multiverse is considered free:
# it would be better to check the actual license, as we do not have
# the component for third-party packages; but this is the best we can do
# at the moment
if pkg.candidate.section.startswith('restricted') or \
pkg.candidate.section.startswith('multiverse'):
return False
return True
Possibly it would be better to do the logic the other way around ("if
it's in main/universe/whatever, then it's free, otherwise it's
nonfree"), but really a better solution is needed.
However, I notice that the Nvidia drivers on my system are from section
"non-free/libs" – the following patch fixes the problem for me:
--- a/UbuntuDrivers/detect.py 2019-01-10 02:30:54.326668673 +
+++ b/UbuntuDrivers/detect.py 2019-01-10 02:36:24.707733516 +
@@ -165,7 +165,8 @@
# the component for third-party packages; but this is the best we can do
# at the moment
if pkg.candidate.section.startswith('restricted') or \
-pkg.candidate.section.startswith('multiverse'):
+pkg.candidate.section.startswith('multiverse') or \
+pkg.candidate.section.startswith('non-free'):
return False
return True
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1514057
Title:
Incorrect(?) reporting of freeness of third-party nVidia drivers from
graphic-drivers PPA
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1514057/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810354] Re: non-idiomatic date/time display for Chinese language
Thanks. Moved to: https://gitlab.gnome.org/GNOME/gnome-desktop/issues/98 ** Description changed: + https://gitlab.gnome.org/GNOME/gnome-desktop/issues/98 + + --- + On the top panel, the date/time info are displayed as: 四 1月3 09:38 It should be displayed as: 星期四 1月3日 09:38 If I switch off the date part, it is correct: 星期四 09:38 Is it because of the width limitation of date/time widget, or something wrong with i18n? ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810354 Title: non-idiomatic date/time display for Chinese language To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1810354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809783] Re: Bluetooth always on when power on my laptop (Budgie Desktop)
John, please run: dpkg -l > allpackages.txt and then send us the resulting file 'allpackages.txt'. ** Changed in: budgie-desktop (Ubuntu) Status: New => Incomplete ** Package changed: budgie-desktop (Ubuntu) => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809783 Title: Bluetooth always on when power on my laptop (Budgie Desktop) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1809783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809692] Re: distorted lines when using chrome/chromium browser
** Changed in: chromium-browser (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/1809692 Title: distorted lines when using chrome/chromium browser To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1809692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809488] Re: armhf guests fail to boot in EFI mode
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809488 Title: armhf guests fail to boot in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809488/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810998] Re: CPU hard lockup with rigorous writes to NVMe drive
** Description changed:
[NOTE]
* Patches will be sent to the kernel-team mailing list
once the test kernel has been verified by the reporter.
[Impact]
* Users may experience cpu hard lockups when performing
rigorous writes to NVMe drives.
* The fix addresses an scheduling issue in the original
implementation of wbt/writeback throttling
* The fix is commit 2887e41b910b ("blk-wbt: Avoid lock
contention and thundering herd issue in wbt_wait"),
plus its fix commit 38cfb5a45ee0 ("blk-wbt: improve
waking of tasks").
* There are additional commits to help with a cleaner
backport and future maintenance:
- Cosmic: total of 8 clean cherry picks.
- Bionic: total of 13 commits, 9 clean cherry-picks
and 4 backports, which are just changes to context
lines (i.e. refresh) without any functional changes
in the backport itself.
[Test Case]
* This command has been reported to reproduce the problem:
$ sudo iozone -R -s 5G -r 1m -S 2048 -i 0 -G -c -o -l 128 -u 128 -t
128
- * It generates stack traces as included below.
+ * It generates stack traces as below in the original kernel,
+and does not generate them in the modified/patched kernel.
+
+ * The user/reporter verified the test kernel with these patches
+resolved the problem.
+
+ * The developer verified in 2 systems (4-core and 24-core but
+no NVMe) for regressions, and no error messages were logged
+to dmesg.
[Regression Potential]
* The commits have been verified for fixes in later commits in
linux-next as of 2019-01-08 and all known fix commits are in.
* The regression potential is mostly contained in the writeback
throttling (block/blk-wbt.*), as almost all of the 13 patches
change exclusively that, except for 4 of them (2 of which are
sysfs):
- blk-rq-qos: refactor out common elements of blk-wbt (block/)
- block: Protect less code with sysfs_lock in blk_{un,}register_queue()
(blk-sysfs.c)
- block: Protect less code with sysfs_lock in blk_{un,}register_queue()
(blk-{mq-}sysfs.c)
- block: pass struct request instead of struct blk_issue_stat to wbt
(block/, still mostly blk-wbt.*)
[Other Info]
* Alternatively, it is probably possible to introduce just the
two commits that fix this with some changes to their code in
the backport, but since the 'blk-rq-qos: refactor ..' commit
may become a dependency for many additional/future fixes, it
seemed interesting to pull it in earlier in the 18.04 cycle.
* The problem has been introduced with the blk-wbt mechanism,
in v4.10-rc1, and the fix commits in v4.19-rc1 and -rc2,
so only Bionic and Cosmic needs this.
[Stack Traces]
[ 393.628647] NMI watchdog: Watchdog detected hard LOCKUP on cpu 30
...
[ 393.628704] CPU: 30 PID: 0 Comm: swapper/30 Tainted: P OE 4.15.0-20-generic
#21-Ubuntu
...
[ 393.628720] Call Trace:
[ 393.628721]
[ 393.628724] enqueue_task_fair+0x6c/0x7f0
[ 393.628726] ? __update_load_avg_blocked_se.isra.37+0xd1/0x150
[ 393.628728] ? __update_load_avg_blocked_se.isra.37+0xd1/0x150
[ 393.628731] activate_task+0x57/0xc0
[ 393.628735] ? sched_clock+0x9/0x10
[ 393.628736] ? sched_clock+0x9/0x10
[ 393.628738] ttwu_do_activate+0x49/0x90
[ 393.628739] try_to_wake_up+0x1df/0x490
[ 393.628741] default_wake_function+0x12/0x20
[ 393.628743] autoremove_wake_function+0x12/0x40
[ 393.628744] __wake_up_common+0x73/0x130
[ 393.628745] __wake_up_common_lock+0x80/0xc0
[ 393.628746] __wake_up+0x13/0x20
[ 393.628749] __wbt_done.part.21+0xa4/0xb0
[ 393.628749] wbt_done+0x72/0xa0
[ 393.628753] blk_mq_free_request+0xca/0x1a0
[ 393.628755] blk_mq_end_request+0x48/0x90
[ 393.628760] nvme_complete_rq+0x23/0x120 [nvme_core]
[ 393.628763] nvme_pci_complete_rq+0x7a/0x130 [nvme]
[ 393.628764] __blk_mq_complete_request+0xd2/0x140
[ 393.628766] blk_mq_complete_request+0x18/0x20
[ 393.628767] nvme_process_cq+0xe1/0x1b0 [nvme]
[ 393.628768] nvme_irq+0x23/0x50 [nvme]
[ 393.628772] __handle_irq_event_percpu+0x44/0x1a0
[ 393.628773] handle_irq_event_percpu+0x32/0x80
[ 393.628774] handle_irq_event+0x3b/0x60
[ 393.628778] handle_edge_irq+0x7c/0x190
[ 393.628779] handle_irq+0x20/0x30
[ 393.628783] do_IRQ+0x46/0xd0
[ 393.628784] common_interrupt+0x84/0x84
[ 393.628785]
...
[ 393.628794] ? cpuidle_enter_state+0x97/0x2f0
[ 393.628796] cpuidle_enter+0x17/0x20
[ 393.628797] call_cpuidle+0x23/0x40
[ 393.628798] do_idle+0x18c/0x1f0
[ 393.628799] cpu_startup_entry+0x73/0x80
[ 393.628802] start_secondary+0x1a6/0x200
[ 393.628804] secondary_startup_64+0xa5/0xb0
[ 393.628805] Code: ...
[ 405.981597] nvme nvme1: I/O 393 QID 6 timeout, completion polled
[ 435.597209] INFO: rcu_sched detected stalls on CPUs/tasks:
[ 435.602858] 30-...0: (1 GPs behind) idle=e26/1/0 softirq=6834/6834 fqs=4485
[
[Bug 602071]
There should be a way to write the driver, the Latitude E6420 has the sensor built in and if you do some hardware hacking then you can monitor the chip's io. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/602071 Title: [0a5c:5801] Broadcom fingerprint reader not working To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/602071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803831] Re: [radeon] Can't login to Ubuntu and unity desktop, screen loops up
** Summary changed: - Can't login to Ubuntu and unity desktop,screen loops up + [radeon] Can't login to Ubuntu and unity desktop,screen loops up ** Tags added: radeon ** Changed in: gdm3 (Ubuntu) Status: Incomplete => Invalid ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid ** Changed in: mutter (Ubuntu) Status: Incomplete => Invalid ** Changed in: xorg-server (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/1803831 Title: [radeon] Can't login to Ubuntu and unity desktop,screen loops up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803831/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799686] Re: Enable v4l2 hardware accelerated video decode
*** This bug is a duplicate of bug 1424201 *** https://bugs.launchpad.net/bugs/1424201 Thanks for the information all. We would need to find out if video decoding hardware exists behind V4L2 in the desktop case, or if that's just for Pi/ARM hardware. I strongly suspect it's the latter. Also, since bug 1424201 is older and more generalized, I think this bug should be marked as a duplicate of that. It's always a bad idea to describe a solution in a bug rather than just the problem. Because most of the time that solution turns out to be the wrong one for the problem. P.S. I am not working on video decoding any more. Only triaging bugs. ** This bug has been marked a duplicate of bug 1424201 Web browsers lacking hardware-accelerated video decoding -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799686 Title: Enable v4l2 hardware accelerated video decode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1799686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810328] Re: iommu - need to effectively disable iommu if "intel_iommu=off" is passed as a kernel parameter
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810328 Title: iommu - need to effectively disable iommu if "intel_iommu=off" is passed as a kernel parameter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810328/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809699] Re: cpu-hotplug test in ubuntu_kernel_selftest always return 0 on Xenial
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809699 Title: cpu-hotplug 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 1801102] Re: Please include this patch in bionic kernel https://www.spinics.net/lists/linux-wireless/msg169994.html
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1801102 Title: Please include this patch in bionic kernel https://www.spinics.net/lists/linux-wireless/msg169994.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801102/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810891] Re: audio output has constant noise on a Dell machine
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: In Progress => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810891 Title: audio output has constant noise on a Dell machine To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1810891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809868] Re: 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 in btrfs_kernel_fixes failed on T
** Changed in: linux (Ubuntu Trusty) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809868 Title: 29d6d30f5c8aa58b04f40a58442df3bcaae5a1d5 in btrfs_kernel_fixes failed on T To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1809868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810998] Re: CPU hard lockup with rigorous writes to NVMe drive
** Description changed:
[NOTE]
* Patches will be sent to the kernel-team mailing list
once the test kernel has been verified by the reporter.
[Impact]
* Users may experience cpu hard lockups when performing
rigorous writes to NVMe drives.
* The fix addresses an scheduling issue in the original
implementation of wbt/writeback throttling
* The fix is commit 2887e41b910b ("blk-wbt: Avoid lock
contention and thundering herd issue in wbt_wait"),
plus its fix commit 38cfb5a45ee0 ("blk-wbt: improve
waking of tasks").
* There are additional commits to help with a cleaner
backport and future maintenance:
- Cosmic: total of 8 clean cherry picks.
- - Bionic: So, of 13 commits, 9 are clean cherry-picks
+ - Bionic: total of 13 commits, 9 clean cherry-picks
and 4 backports, which are just changes to context
lines (i.e. refresh) without any functional changes
in the backport itself.
[Test Case]
* This command has been reported to reproduce the problem:
$ sudo iozone -R -s 5G -r 1m -S 2048 -i 0 -G -c -o -l 128 -u 128 -t
128
* It generates stack traces as included below.
[Regression Potential]
* The commits have been verified for fixes in later commits in
linux-next as of 2019-01-08 and all known fix commits are in.
* The regression potential is mostly contained in the writeback
throttling (block/blk-wbt.*), as almost all of the 13 patches
change exclusively that, except for 4 of them (2 of which are
sysfs):
- blk-rq-qos: refactor out common elements of blk-wbt (block/)
- block: Protect less code with sysfs_lock in blk_{un,}register_queue()
(blk-sysfs.c)
- block: Protect less code with sysfs_lock in blk_{un,}register_queue()
(blk-{mq-}sysfs.c)
- block: pass struct request instead of struct blk_issue_stat to wbt
(block/, still mostly blk-wbt.*)
[Other Info]
* Alternatively, it is probably possible to introduce just the
two commits that fix this with some changes to their code in
the backport, but since the 'blk-rq-qos: refactor ..' commit
may become a dependency for many additional/future fixes, it
seemed interesting to pull it in earlier in the 18.04 branch.
* The problem has been introduced with the blk-wbt mechanism,
in v4.10-rc1, and the fix commits in v4.19-rc1 and -rc2,
so only Bionic and Cosmic needs this.
[Stack Traces]
[ 393.628647] NMI watchdog: Watchdog detected hard LOCKUP on cpu 30
...
[ 393.628704] CPU: 30 PID: 0 Comm: swapper/30 Tainted: P OE 4.15.0-20-generic
#21-Ubuntu
...
[ 393.628720] Call Trace:
[ 393.628721]
[ 393.628724] enqueue_task_fair+0x6c/0x7f0
[ 393.628726] ? __update_load_avg_blocked_se.isra.37+0xd1/0x150
[ 393.628728] ? __update_load_avg_blocked_se.isra.37+0xd1/0x150
[ 393.628731] activate_task+0x57/0xc0
[ 393.628735] ? sched_clock+0x9/0x10
[ 393.628736] ? sched_clock+0x9/0x10
[ 393.628738] ttwu_do_activate+0x49/0x90
[ 393.628739] try_to_wake_up+0x1df/0x490
[ 393.628741] default_wake_function+0x12/0x20
[ 393.628743] autoremove_wake_function+0x12/0x40
[ 393.628744] __wake_up_common+0x73/0x130
[ 393.628745] __wake_up_common_lock+0x80/0xc0
[ 393.628746] __wake_up+0x13/0x20
[ 393.628749] __wbt_done.part.21+0xa4/0xb0
[ 393.628749] wbt_done+0x72/0xa0
[ 393.628753] blk_mq_free_request+0xca/0x1a0
[ 393.628755] blk_mq_end_request+0x48/0x90
[ 393.628760] nvme_complete_rq+0x23/0x120 [nvme_core]
[ 393.628763] nvme_pci_complete_rq+0x7a/0x130 [nvme]
[ 393.628764] __blk_mq_complete_request+0xd2/0x140
[ 393.628766] blk_mq_complete_request+0x18/0x20
[ 393.628767] nvme_process_cq+0xe1/0x1b0 [nvme]
[ 393.628768] nvme_irq+0x23/0x50 [nvme]
[ 393.628772] __handle_irq_event_percpu+0x44/0x1a0
[ 393.628773] handle_irq_event_percpu+0x32/0x80
[ 393.628774] handle_irq_event+0x3b/0x60
[ 393.628778] handle_edge_irq+0x7c/0x190
[ 393.628779] handle_irq+0x20/0x30
[ 393.628783] do_IRQ+0x46/0xd0
[ 393.628784] common_interrupt+0x84/0x84
[ 393.628785]
...
[ 393.628794] ? cpuidle_enter_state+0x97/0x2f0
[ 393.628796] cpuidle_enter+0x17/0x20
[ 393.628797] call_cpuidle+0x23/0x40
[ 393.628798] do_idle+0x18c/0x1f0
[ 393.628799] cpu_startup_entry+0x73/0x80
[ 393.628802] start_secondary+0x1a6/0x200
[ 393.628804] secondary_startup_64+0xa5/0xb0
[ 393.628805] Code: ...
[ 405.981597] nvme nvme1: I/O 393 QID 6 timeout, completion polled
[ 435.597209] INFO: rcu_sched detected stalls on CPUs/tasks:
[ 435.602858] 30-...0: (1 GPs behind) idle=e26/1/0 softirq=6834/6834 fqs=4485
[ 435.610203] (detected by 8, t=15005 jiffies, g=6396, c=6395, q=146818)
[ 435.617025] Sending NMI from CPU 8 to CPUs 30:
[ 435.617029] NMI backtrace for cpu 30
[ 435.617031] CPU: 30 PID: 0 Comm: swapper/30 Tainted: P OE 4.15.0-20-generic
#21-Ubuntu
...
[ 435.617047] Call Trace:
[ 435.617048]
[ 435.617051]
[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)
I suspect it's just a matter of no one else on the Desktop team is aware of this bug. To remedy that, I have already put it on their TODO list here: https://trello.com/c/17nGGFFL -- 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 1809996] Re: PXE network boot fails when Intel SW Guard Extensions (SGX) are enabled
** Summary changed: - PXE network boot fails when 1 NIC is disabled + PXE network boot fails when Intel SW Guard Extensions (SGX) are enabled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809996 Title: PXE network boot fails when Intel SW Guard Extensions (SGX) are enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1809996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811173] Re: package apacheds 2.0.0~M15-4 failed to install/upgrade: installed apacheds package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811173 Title: package apacheds 2.0.0~M15-4 failed to install/upgrade: installed apacheds package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache-directory-server/+bug/1811173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811173] [NEW] package apacheds 2.0.0~M15-4 failed to install/upgrade: installed apacheds package post-installation script subprocess returned error exit status 1
Public bug reported: I don't understand ProblemType: Package DistroRelease: Ubuntu 18.04 Package: apacheds 2.0.0~M15-4 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: Thu Jan 10 08:39:26 2019 ErrorMessage: installed apacheds package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-12-01 (39 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: apache-directory-server Title: package apacheds 2.0.0~M15-4 failed to install/upgrade: installed apacheds package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apache-directory-server (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/1811173 Title: package apacheds 2.0.0~M15-4 failed to install/upgrade: installed apacheds package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache-directory-server/+bug/1811173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810772] Re: firefox/thunderbird: please drop llvm-4.0 and switch to versionless alternative
This bug was fixed in the package firefox - 64.0.2+build1-0ubuntu2
---
firefox (64.0.2+build1-0ubuntu2) disco; urgency=medium
* Revert previous change back to versioned clang/llvm build dependencies,
a micro release update is not the right place for such a change
- update debian/control{,.in}
-- Olivier Tilloy Wed, 09 Jan 2019
17:12:09 +0100
** Changed in: firefox (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/1810772
Title:
firefox/thunderbird: please drop llvm-4.0 and switch to versionless
alternative
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1810772/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 667963] Re: vpnc disconnects after 7-8 hours consistently
I've tested @Ralph Schmieder's patch and it gets the job done. Prevents my VPN from hanging at the expiration of the IKE key lifetime. You can find a slightly cleaned-up source tree with it applied here: https://github.com/dlenski/vpnc/commit/27a7a1b9daee88e000c18001222e2e53e348e378 Any reason the Ubuntu maintainers didn't apply this one already? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/667963 Title: vpnc disconnects after 7-8 hours consistently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vpnc/+bug/667963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806532] Re: The line-out on the Dell Dock station can't work
** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806532 Title: The line-out on the Dell Dock station can't work To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1806532/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810354] Re: non-idiomatic date/time display for Chinese language
Here is the upstream report I just created: https://gitlab.gnome.org/GNOME/gnome-shell/issues/898 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810354 Title: non-idiomatic date/time display for Chinese language To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1810354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773637] Re: Distribution upgrade to 18.04: used nvidia display driver is commented out
I tested this upgrade process and it worked for me, setting to verification-done. bdmurray@clean-bionic-amd64:/tmp/ubuntu-release-upgrader-0vo0ih0i$ grep "release-upgrader version" /var/log/dist-upgrade/main.log 2019-01-09 15:50:20,150 INFO release-upgrader version '18.10.11.3' started bdmurray@clean-bionic-amd64:/tmp/ubuntu-release-upgrader-0vo0ih0i$ cat /etc/X11/xorg.conf Section "Device" Identifier "nvidia" EndSection bdmurray@clean-bionic-amd64:/tmp/ubuntu-release-upgrader-0vo0ih0i$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.10 ** Tags removed: verification-needed verification-needed-cosmic ** Tags added: verification-done verification-done-cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773637 Title: Distribution upgrade to 18.04: used nvidia display driver is commented out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1773637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 900213] Re: programme closes spuriously
** Tags added: oneiric -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/900213 Title: programme closes spuriously To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gopchop/+bug/900213/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811162] Re: Turn on CONFIG_REFCOUNT_FULL for non-x86 arches
** 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/1811162 Title: Turn on CONFIG_REFCOUNT_FULL for non-x86 arches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811152] Re: Locally installed services can't add dbus configuration
I did not check upstream yet no, thanks for checking. I'll report it upsteam as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811152 Title: Locally installed services can't add dbus configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1811152/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791758] Re: ldisc crash on reopened tty
** Changed in: linux (Ubuntu Xenial) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791758 Title: ldisc crash on reopened tty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811169] [NEW] Device firmware update does not detect AC power
Public bug reported: On a freshly installed Ubuntu 18.10 on a Lenovo T580, the Gnome Software center after awhile proposes to install a couple of firmware related updates. At first the AC wasn't connected, and upon trying to install either of the updates, a popup appears saying that the update cannot continue without the AC being plugged in. This is so far expected behavior. But even after connecting the laptop to the AC power supply, the message persists, making it not possible to continue with the firmware updates. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-software 3.30.2-0ubuntu8 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: Thu Jan 10 00:59:20 2019 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2019-01-09 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.30.2-0ubuntu8 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic lvfs -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811169 Title: Device firmware update does not detect AC power To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1811169/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1791758] Re: ldisc crash on reopened tty
** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Cosmic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1791758 Title: ldisc crash on reopened tty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791758/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1810630] Re: Boot up is hung on a purple screen
1. Please see attached for another documented failed boot, saved as failedboot2.txt. 2. There were no files named xorg.conf in /etc 3. Custom.conf is attached as well. Thank you Alex On Tue, Jan 8, 2019 at 10:58 PM Alex Thëil wrote: > Comment 10 being the reproduce a failed boot, then successful boot and > save the failed boot log? > > On Tue, Jan 8, 2019 at 8:55 PM Daniel van Vugt < > daniel.van.v...@canonical.com> wrote: > >> Thanks. I can't yet see any failures in failedboot.txt. What's strange >> is that it claims to be using Xorg and rendering on the 1280x800 laptop >> screen successfully. >> >> 1. Please check again that you followed the steps in comment #10 >> exactly, and redo them. >> >> 2. Please also run this command: >> >>find /etc -name xorg.conf >> >>and if it finds any files named xorg.conf then attach them here. >> >> 3. Please also attach your file /etc/gdm3/custom.conf >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1810630 >> >> Title: >> Boot up is hung on a purple screen >> >> Status in Ubuntu: >> Incomplete >> >> Bug description: >> Despite updating drivers for video through xorg, display cannot change >> from 1024x768. Default video card is still listed as llvmpipe. >> >> 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: Sat Jan 5 15:19:12 2019 >> DistUpgraded: Fresh install >> DistroCodename: bionic >> DistroVariant: ubuntu >> ExtraDebuggingInterest: Yes, if not too technical >> GraphicsCard: >>Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated >> Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) >> Subsystem: Intel Corporation Mobile 945GM/GMS, 943/940GML Express >> Integrated Graphics Controller [8086:7270] >> Subsystem: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML >> Express Integrated Graphics Controller [8086:7270] >> InstallationDate: Installed on 2018-12-24 (12 days ago) >> InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 >> (20180725) >> MachineType: Apple Inc. MacBook2,1 >> ProcEnviron: >>TERM=xterm-256color >>PATH=(custom, no user) >>XDG_RUNTIME_DIR= >>LANG=en_US.UTF-8 >>SHELL=/bin/bash >> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic >> root=UUID=2d93d825-1bcb-4155-aad5-cfdb5dce95ab ro quiet splash nomodeset >> vt.handoff=1 >> SourcePackage: xorg >> Symptom: display >> UpgradeStatus: No upgrade log present (probably fresh install) >> dmi.bios.date: 06/27/07 >> dmi.bios.vendor: Apple Inc. >> dmi.bios.version: MB21.88Z.00A5.B07.0706270922 >> dmi.board.asset.tag: Base Board Asset Tag >> dmi.board.name: Mac-F4208CAA >> dmi.board.vendor: Apple Inc. >> dmi.board.version: PVT >> dmi.chassis.asset.tag: Asset Tag >> dmi.chassis.type: 10 >> dmi.chassis.vendor: Apple Inc. >> dmi.chassis.version: Mac-F4208CAA >> dmi.modalias: >> dmi:bvnAppleInc.:bvrMB21.88Z.00A5.B07.0706270922:bd06/27/07:svnAppleInc.:pnMacBook2,1:pvr1.0:rvnAppleInc.:rnMac-F4208CAA:rvrPVT:cvnAppleInc.:ct10:cvrMac-F4208CAA: >> dmi.product.family: MacBook >> dmi.product.name: MacBook2,1 >> dmi.product.version: 1.0 >> dmi.sys.vendor: Apple Inc. >> version.compiz: compiz N/A >> version.libdrm2: libdrm2 2.4.96+git1901040630.403f3c~oibaf~b >> version.libgl1-mesa-dri: libgl1-mesa-dri >> 19.0~git1901050730.884737~oibaf~b >> version.libgl1-mesa-glx: libgl1-mesa-glx >> 19.0~git1901050730.884737~oibaf~b >> 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.1.99+git1812281934.803f87~oibaf~b >> version.xserver-xorg-video-intel: xserver-xorg-video-intel >> 2:2.99.917+git1812031933.e5ff8e~oibaf~b >> version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau >> 1:1.0.15+git1812100734.a4283f~oibaf~b >> >> To manage notifications about this bug go to: >> https://bugs.launchpad.net/ubuntu/+bug/1810630/+subscriptions >> > -- > Alexander A Theiler, MHS, MS, PA-C > CAQ in Emergency Medicine > -- Alexander A Theiler, MHS, MS, PA-C CAQ in Emergency Medicine ** Attachment added: "failedboot2.txt" https://bugs.launchpad.net/bugs/1810630/+attachment/5228086/+files/failedboot2.txt ** Attachment added: "custom.conf" https://bugs.launchpad.net/bugs/1810630/+attachment/5228087/+files/custom.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810630
[Bug 1773637] Re: Distribution upgrade to 18.04: used nvidia display driver is commented out
** Description changed: Impact -- - Users who have manually configured and xorg.conf file with nvidia enabled as a driver will be surprised to have disabled on upgrade to a new release of Ubuntu and won't have a graphical display. + Users who have manually configured an xorg.conf file with nvidia enabled as a driver will be surprised to have disabled on upgrade to a new release of Ubuntu and won't have a graphical display. Test Case - If you don't have a system with nvidia hardware to upgrade this is a bit convoluted but still works. 1) Run do-release-upgrade (use -d if upgrading to disco) 2) Cancel the upgrade 3) Create an /etc/X11/xorg.conf file with a Device section listed in the original description using the nvidia driver. 4) cd to /tmp/ubuntu-release-upgrader-$TEMPNAME 5) run ./$target-release-name --frontend DistUpgradeViewText 6) Observe the Driver line is commented out of xorg.conf When testing the release-upgrader from -proposed you'll need to use the -p switch to get the right tarball. Additionally, you'll want to add a step 4.5 where you modify xorg_fix_proprietary.py so nvidia defaults to True instead of False (line 106) this'll simulate the nvidia driver being loaded. Regression Potential This just changes how xorg_fix_proprietary check for nvidia being in use and it only affects people who have an /etc/X11/xorg.conf so the impact of a regression is rather small. Additionally, the logic used to determine if nvidia in use is the same logic used in the apport package hook for all xorg packages so is well tested. Original Description I upgraded my system from 17.10 to 18.04 Bionic Beaver via do-release-upgrade. After the installation had finished, Xorg wouldn't start. I later found out that this was because the installation routine had commented out the nvidia display driver I used in the xorg.conf: Section "Device" Identifier "nvidia" #Driver "nvidia" BusID "PCI:10@0:0:0" Option "ConstrainCursor" "off" EndSection As the installtion routine backuped my xorg.conf I could verify that the line hadn't been commented out before upgrading. Removing the "#" solved the problem. ProblemType: BugDistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia .proc.driver.nvidia.gpus..0a.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:0a:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 27 11:43:16 2018 DistUpgraded: 2018-05-21 10:52:35,978 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed nvidia, 390.48, 4.15.0-20-generic, x86_64: installed nvidia, 390.48, 4.15.0-22-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:229d] Subsystem: Hewlett-Packard Company GM108M [GeForce 840M] [103c:229d] InstallationDate: Installed on 2017-11-02 (205 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic root=UUID=2c76a9d7-c435-4600-abc9-2ecd10fc3001 ro quiet splash vt.handoff=1SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-05-21 (6 days ago) dmi.bios.date: 11/28/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.33 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 229D dmi.board.vendor: Hewlett-Packard dmi.board.version: 78.15 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.33:bd11/28/2014:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr097312405F1620180:rvnHewlett-Packard:rn229D:rvr78.15:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV X=Null dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 097312405F1620180 dmi.sys.vendor: Hewlett-Packard
[Bug 1807686] Re: efi-lockdown patch causes -EPERM for some debugfs files even though CONFIG_LOCK_DOWN_KERNEL is not set
** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807686 Title: efi-lockdown patch causes -EPERM for some debugfs files even though CONFIG_LOCK_DOWN_KERNEL is not set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1807686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811165] [NEW] /usr/lib/docky/Docky.exe:free(): invalid pointer
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding docky. This problem was most recently seen with package version 2.2.1.1-1, the problem page at https://errors.ubuntu.com/problem/1dd935448efe5101fdc6044eaa7820315e8b6363 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: docky (Ubuntu) Importance: Undecided Status: New ** Tags: bionic 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/1811165 Title: /usr/lib/docky/Docky.exe:free(): invalid pointer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docky/+bug/1811165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811162] 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 1811162 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/1811162 Title: Turn on CONFIG_REFCOUNT_FULL for non-x86 arches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811164] [NEW] apt cannot find linux-libc-dev
Public bug reported: Running: xenial Problem: After running apt-get update, I still get this upon apt-get install: Err:60 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 linux-libc-dev amd64 4.4.0-140.166 404 Not Found [IP: 91.189.88.161 80] All other packages install fine. Looking at the package repo at http://archive.ubuntu.com/ubuntu/dists /xenial-updates/main/ it appears the amd64 entry was updated today, so I assume that's when the error was introduced. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: linux-libc-dev xenial-updates -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811164 Title: apt cannot find linux-libc-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811164] 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 1811164 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/1811164 Title: apt cannot find linux-libc-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800238] Re: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18
In addition to above commit 255095fa7f62ff09b6f61393414535c59c6b4cb0 media: dvb-usb-v2: Fix incorrect use of transfer_flags URB_FREE_BUFFER -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800238 Title: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800238] Re: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18
Sorry I meant 4.20.1 ** Tags removed: kernel-bug-exists-upstream ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800238 Title: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800238] Re: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18
Kernel 4.21.1 and 4.19.14 have all the fixes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800238 Title: TechnoTrend TT-TVStick CT2-4400 (v2) stopped working with kernel 4.18 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1368411] Re: Cannot insert IPV6 rule before IPV4 rules
** Changed in: ufw (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: ufw (Ubuntu Cosmic) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1368411 Title: Cannot insert IPV6 rule before IPV4 rules To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1368411/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 570944] Re: passwd : gives "Authentication token manipulation error"
Ah, thank you, I missed that On Wed, Jan 9, 2019, 18:34 Mathieu Parent <570...@bugs.launchpad.net wrote: > It is. Closed by me: > > samba (2:4.9.1+dfsg-2) unstable; urgency=medium > [ Mathieu Parent ] > * Allow one to change password via passwd in default config > - third_party: Update pam_wrapper to version 1.0.7 > - third_party: Add pam_set_items.so from pam_wrapper > - nsswitch: Add try_authtok option to pam_winbind > - tests: Check pam_winbind pw change with different options > - Patch for previous 4 commits > - debian/winbind.pam-config: Use the new try_authtok option allowing > password change while preserving current behavior with password strength > modules (Closes: #858923, LP: #570944) > > -- > You received this bug notification because you are subscribed to samba > in Ubuntu. > https://bugs.launchpad.net/bugs/570944 > > Title: > passwd : gives "Authentication token manipulation error" > > Status in samba package in Ubuntu: > Triaged > > Bug description: > Binary package hint: samba > >`passwd` for ActiveDirectory account gives "Authentication token > manipulation error" > > I have latest and greatest of LucidLynx updates. > > winbind2:3.4.7~dfsg-1ubuntu3 > samba 2:3.4.7~dfsg-1ubuntu3 > > I have ActiveDirectory integration with Samba/Winbind. (not > Likewise-Open) > Logging into Console window or `ssh`-ing into machine works fine using > DOMAIN\first.last account names. > > Trying to change password with the `passwd` program: > > $ passwd > Changing password for DOMAIN\first.last > (current) NT password: > passwd: Authentication token manipulation error > passwd: password unchanged > $ > > In the /var/log/auth.log file I get this output in conjunction with > the above passwd attempt: > > pam_unix(passwd:chauthtok): user "DOMAIN\first.last" does not exist in > /etc/passwd > passwd[16109]: pam_winbind(passwd:chauthtok): getting password > (0x002a) > > passwd[16109]: pam_winbind(passwd:chauthtok): user 'DOMAIN\first.last' > granted access > passwd[16109]: pam_unix(passwd:chauthtok): user "DOMAIN\first.last" does > not exist in /etc/passwd > passwd[16109]: pam_winbind(passwd:chauthtok): getting password > (0x0012) > > I don't see anything particularly wrong with that output, other > than it seems to stop prematurely. > > This is my default-created /etc/pam.d/common-password file: > > password [success=2 default=ignore] pam_unix.so obscure sha512 > password [success=1 default=ignore] pam_winbind.so use_authtok > try_first_pass > password requisite pam_deny.so > password required pam_permit.so > password optional pam_gnome_keyring.so > > I've Googled for "Authentication token manipulation error", but most > cases involve local Linux accounts or other uninteresting problems. > > I don't think any entries in smb.conf have an effect on passwd, but > here's a snippet of entries with the word "pass" or "encrypt" in them: > > password server = machine.domain.com > encrypt passwords = true > passdb backend = tdbsam > unix password sync = yes > passwd program = /usr/bin/passwd %u > passwd chat = *Enter\snew\s*\spassword:* %n\n > *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . > pam password change = yes > encrypt passwords = true > > > I can successfully change password, using `passwd` for a local Linux > account. > > $ passwd > Changing password for localAccount. > (current) UNIX password: > Enter new UNIX password: > Retype new UNIX password: > passwd: password updated successfully > $ > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/samba/+bug/570944/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: distribution=ubuntu; sourcepackage=samba; component=main; > status=Triaged; importance=Medium; assignee=None; > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: ahasenack gasinvein guy-moore janitor > lorenzetto-luca math-parent nacc ttx urusha vorlon > Launchpad-Bug-Reporter: gmoore777 (guy-moore) > Launchpad-Bug-Modifier: Mathieu Parent (math-parent) > Launchpad-Message-Rationale: Subscriber (samba in Ubuntu) > Launchpad-Message-For: ahasenack > -- You received this bug notification because you are a member of Ubuntu Server, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/570944 Title: passwd : gives "Authentication token manipulation error" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/570944/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
