[Bug 1751813] Comment bridged from LTC Bugzilla
--- Comment From naveed...@in.ibm.com 2018-05-04 01:38 EDT--- (In reply to comment #84) > The scan is forced to be done synchronously, however the ipr driver is > available and is loaded much earlier in the install process, thus it should > not significantly affect the overall install time. > > One may be able to notice the difference a bit more with a fully-automated > preseed install. Noted, Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751813 Title: Ubuntu 18.04 installer does not detect any IPR based HDD/RAID array [S822L] [ipr] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1751813/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769038] [NEW] GRUB installation failed - installing Ubuntu Budgie 18.10 on USB issue
Public bug reported: While trying to install Ubuntu Budgie on a USB i got the following error message: "GRUB installation failed: The 'grub-efi-amd64-signed'package failed to install into / target/. Without the GRUB boot loader, the installation system will not boot". kindly need your help to solve this issue. Thank you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: Budgie Date: Fri May 4 08:39:17 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-budgie.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14 ubuntu-budgie -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769038 Title: GRUB installation failed - installing Ubuntu Budgie 18.10 on USB issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1769038/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765233] Re: tweak location formatting
** Changed in: gnome-initial-setup (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765233 Title: tweak location formatting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1765233/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769039] [NEW] Ubuntu1804 installer is not able to detect SAN disks(mulitpath disks) with 'No disk drive was detected' message.
Public bug reported: Problem Description: === Ubuntu1804 installer is not able to detect SAN disks(mulitpath disks) with 'No disk drive was detected' message. Steps to re-create: == > on Witherspoon test system, tried to install latest ubuntu1804 build using netboot install. > Selected appropriate fields and then when it entres detect disk screen > It throws below messgae lqqu [!] Detect disks tqqqk x x x No disk drive was detected. If you know the name of the driver needed x x by your disk drive, you can select it from the list.x x x x Driver needed for your disk drive: x x x x continue with no disk drive x x login to iSCSI targets x x cryptoloop x x ipr x x virtio_scsi x x none of the above x x x xx x x mqj > Installer not able to detect the SAN disk(mulitpath disks) and so not able to proceed with installation. > Unable to proceed with ubutnu1804 installation as installer not able to detect the disk (SAN disks) using netboot install method > Attached /var/log/syslog messages from installer Attached /var/log/syslog files from installer shell prompt == Comment: #13 - Frederic Bonnard- 2018-04-30 09:00:21 == Hi, - did you install install with "disk-detect/multipath/enable=true" ? ( https://help.ubuntu.com/lts/serverguide/multipath-setting-up-dm-multipath.html.en ) - check /var/log/syslog to see you didn't fail to download any udeb related to disk management and make sure there isn't any error . - check availability of disks with lsblk or "find /dev/disk/ -ls" F. == Comment: #14 - INDIRA P. JOGA - 2018-05-02 04:55:55 == (In reply to comment #12) > Hi Indira, thanks for the bug. I have some questions I would like to > understand better: > > What are the device subsystem that this disks are connected to? Is it a > Fibre Channel connection? > > Do you have explicit two connections to the same disk? I.e, you would see > two disks that the multipathd would need to detect that they are the same, > or, your subsystem would handle the multi path configuration? > > How many disks do you have? Hi Breno, System has both SAS card with mulitpath & SAN card with mulitpath. Yes we have two connections to same disk. FYI - SAN - mpathb (3600507680183050d280002a3) dm-1 IBM,2145 size=100G features='1 queue_if_no_path' hwhandler='0' wp=rw |-+- policy='service-time 0' prio=50 status=active | |- 2:0:1:1 sdaa 65:160 active ready running | `- 3:0:1:1 sdag 66:0 active ready running `-+- policy='service-time 0' prio=10 status=enabled |- 2:0:0:1 sdx 65:112 active ready running `- 3:0:0:1 sdad 65:208 active ready running SAS - mpathl (35000c50076564663) dm-35 IBM,ST300MP0064 size=279G features='0' hwhandler='0' wp=rw |-+- policy='service-time 0' prio=1 status=active | `- 1:0:8:0 sdi 8:128 active ready running `-+- policy='service-time 0' prio=1 status=enabled `- 1:0:19:0 sds 65:32 active ready running == Comment: #15 - INDIRA P. JOGA - 2018-05-02 05:01:21 == (In reply to comment #13) > Hi, > - did you install install with "disk-detect/multipath/enable=true" ? ( > https://help.ubuntu.com/lts/serverguide/multipath-setting-up-dm-multipath. > html.en ) > - check /var/log/syslog to see you didn't fail to download any udeb related > to disk management and make sure there isn't any error . > - check availability of disks with lsblk or "find /dev/disk/ -ls" > > F. Yes i have tried both with multipath enable true & without multipath in both cases it failed. when problem reported guest has 3 disks and still not able to detect those disks. == Comment: #19 - Breno Leitao - 2018-05-03 09:02:54 == Let's get this mirrored to canonical for their awareness. ** Affects: debian-installer (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-167240 severity-high targetmilestone-inin--- **
[Bug 1769039] boslcp3g1 guest xml
Default Comment by Bridge ** Attachment added: "boslcp3g1 guest xml" https://bugs.launchpad.net/bugs/1769039/+attachment/5133415/+files/boslcp3g1_guest_xml.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769039 Title: Ubuntu1804 installer is not able to detect SAN disks(mulitpath disks) with 'No disk drive was detected' message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1769039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769039] boslcp3g3_guest xml
Default Comment by Bridge ** Attachment added: "boslcp3g3_guest xml" https://bugs.launchpad.net/bugs/1769039/+attachment/5133416/+files/boslcp3g3_guest_xml.txt ** Changed in: ubuntu Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** Package changed: ubuntu => debian-installer (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769039 Title: Ubuntu1804 installer is not able to detect SAN disks(mulitpath disks) with 'No disk drive was detected' message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1769039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768996] Re: Nautilus "Software caused connection abort" when copying file from smb share
** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768996 Title: Nautilus "Software caused connection abort" when copying file from smb share To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1768996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769039] ubuntu1804_netboot_install fails
Default Comment by Bridge ** Attachment added: "ubuntu1804_netboot_install fails" https://bugs.launchpad.net/bugs/1769039/+attachment/5133414/+files/ubunu1804_netbootinstaller_syslogfile.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769039 Title: Ubuntu1804 installer is not able to detect SAN disks(mulitpath disks) with 'No disk drive was detected' message. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1769039/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled
** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu) Status: Confirmed => 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/1767648 Title: Top bar and shell dialogs are not displayed properly when zoom is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1767648/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768649] Re: [CVE] Access to privileged files
This bug was fixed in the package kwallet-pam - 4:5.12.4-0ubuntu1.1 --- kwallet-pam (4:5.12.4-0ubuntu1.1) bionic-security; urgency=medium * SECURITY UPDATE: Access to privileged files (LP: #1768649): - fix-CVE-2018-10380-1.patch - fix-CVE-2018-10380-2.patch - CVE-2018-10380 -- Simon QuigleyThu, 03 May 2018 16:06:06 -0500 ** Changed in: kwallet-pam (Ubuntu Xenial) 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/1768649 Title: [CVE] Access to privileged files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwallet-pam/+bug/1768649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768649] Re: [CVE] Access to privileged files
This bug was fixed in the package kwallet-pam - 4:5.5.5-0ubuntu1.1 --- kwallet-pam (4:5.5.5-0ubuntu1.1) xenial-security; urgency=medium * SECURITY UPDATE: Access to privileged files (LP: #1768649): - fix-CVE-2018-10380-1.patch - fix-CVE-2018-10380-2.patch - CVE-2018-10380 -- Simon QuigleyThu, 03 May 2018 16:32:17 -0500 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768649 Title: [CVE] Access to privileged files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwallet-pam/+bug/1768649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769036] [NEW] package libcilkrts5:amd64 5.4.0-6ubuntu1~16.04.9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libcilkrts5:amd64 5.4.0-6ubuntu1~16.04.9 ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117 Uname: Linux 4.4.0-122-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Thu May 3 17:21:39 2018 Dependencies: gcc-5-base 5.4.0-6ubuntu1~16.04.9 gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu10 libgcc1 1:6.0.1-0ubuntu1 libstdc++6 5.4.0-6ubuntu1~16.04.9 DpkgHistoryLog: Start-Date: 2018-05-03 17:21:03 Commandline: aptdaemon role='role-commit-packages' sender=':1.96' Install: linux-headers-4.4.0-122:amd64 (4.4.0-122.146, automatic), linux-image-4.4.0-122-generic:amd64 (4.4.0-122.146, automatic), linux-signed-image-4.4.0-122-generic:amd64 (4.4.0-122.146, automatic), linux-image-extra-4.4.0-122-generic:amd64 (4.4.0-122.146, automatic), linux-headers-4.4.0-122-generic:amd64 (4.4.0-122.146, automatic) Upgrade: linux-headers-generic:amd64 (4.4.0.121.127, 4.4.0.122.128), linux-libc-dev:amd64 (4.4.0-121.145, 4.4.0-122.146), ifupdown:amd64 (0.8.10ubuntu1.2, 0.8.10ubuntu1.3), linux-image-generic:amd64 (4.4.0.121.127, 4.4.0.122.128), linux-signed-image-generic:amd64 (4.4.0.121.127, 4.4.0.122.128), linux-signed-generic:amd64 (4.4.0.121.127, 4.4.0.122.128), linux-generic:amd64 (4.4.0.121.127, 4.4.0.122.128) DuplicateSignature: package:libcilkrts5:amd64:5.4.0-6ubuntu1~16.04.9 Processing triggers for ureadahead (0.100.0-19) ... ureadahead will be reprofiled on next reboot dpkg: error processing package libcilkrts5:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-03-06 (58 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: gcc-5 Title: package libcilkrts5:amd64 5.4.0-6ubuntu1~16.04.9 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gcc-5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769036 Title: package libcilkrts5:amd64 5.4.0-6ubuntu1~16.04.9 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/gcc-5/+bug/1769036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768649] Re: [CVE] Access to privileged files
This bug was fixed in the package kwallet-pam - 4:5.10.5-0ubuntu1.1 --- kwallet-pam (4:5.10.5-0ubuntu1.1) artful-security; urgency=medium * SECURITY UPDATE: Access to privileged files (LP: #1768649): - fix-CVE-2018-10380-1.patch - fix-CVE-2018-10380-2.patch - CVE-2018-10380 -- Simon QuigleyThu, 03 May 2018 16:25:43 -0500 ** Changed in: kwallet-pam (Ubuntu Artful) Status: Fix Committed => Fix Released ** Changed in: kwallet-pam (Ubuntu Bionic) 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/1768649 Title: [CVE] Access to privileged files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwallet-pam/+bug/1768649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769037] [NEW] package nvidia-kernel-common-390 390.48-0ubuntu3 failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-384 384.111-0ub
Public bug reported: It seems ubuntu 18 LTS is falling to install/upgrade on Gigabyte. Specs :- Processor : Intel code i7 7th Gen RAM amount: 16308292 kB Dual storage (SSD and HDD) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: nvidia-kernel-common-390 390.48-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 Date: Fri May 4 07:09:32 2018 Dependencies: ErrorMessage: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-384 384.111-0ubuntu0.17.10.1 InstallationDate: Installed on 2018-04-26 (7 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.5.1 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-kernel-common-390 390.48-0ubuntu3 failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-384 384.111-0ubuntu0.17.10.1 UpgradeStatus: Upgraded to bionic on 2018-05-04 (0 days ago) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic ** Attachment added: "That's my gigabyte pc specs" https://bugs.launchpad.net/bugs/1769037/+attachment/5133400/+files/20180504_073343.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769037 Title: package nvidia-kernel-common-390 390.48-0ubuntu3 failed to install/upgrade: trying to overwrite '/lib/udev/rules.d/71-nvidia.rules', which is also in package nvidia-384 384.111-0ubuntu0.17.10.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1769037/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 843431] Re: Logitech camera microphone does not work / makes "chipmunk" sound
I'm affraid it's not fixed...because i still got chipmunks on xubuntu 18 fresh install -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/843431 Title: Logitech camera microphone does not work / makes "chipmunk" sound To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/843431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752053] Re: nvidia-390 fails to boot graphical display
For PRIME users: as a workaround you can make you X session work with Intel driver with this minimal xorg.conf Section "ServerLayout" Identifier "layout" Screen 0 "Screen0" 0 0 Option "Xinerama" "0" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Unknown" ModelName "Unknown" Option "DPMS" "on" EndSection Section "Device" Identifier "intel" Driver "intel" Option "AccelMethod" "sna" Option "TearFree" "true" BusID "PCI:0@0:2:0" EndSection Section "Screen" Identifier "intel" Device "intel" Monitor"Monitor0" EndSection Section "Screen" Identifier "Screen0" Device "intel" Monitor"Monitor0" DefaultDepth24 SubSection "Display" Virtual 1920 1080 Depth 24 EndSubSection EndSection Make sure to put your own BusID and screen size. Both are mandatory. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume
I'm not suggesting waiting for 5.49, kind of. This bug will be fixed in an update to 5.48. Policy however requires that we always fix the development release first. So Ubuntu 18.10 will probably need to receive bluez 5.49 before we can get approval for a bluez 5.48 update to Ubuntu 18.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759628 Title: bluez regression: Bluetooth audio fails to reconnect after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768906] Re: Xorg crash
Be sure to purge the previous used nvidia driver before testing a new one (settings removal). Do you get the same issue if 'nouveau' driver is used ? (nvidia purged, and reboot) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768906 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769035] Re: Could not delete variable: No space left on device (package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subproces
*** This bug is a duplicate of bug 1767570 *** https://bugs.launchpad.net/bugs/1767570 ** Summary changed: - package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 + Could not delete variable: No space left on device (package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1) ** This bug has been marked a duplicate of bug 1767570 Could not delete variable: No space left on device (package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769035 Title: Could not delete variable: No space left on device (package shim- signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim- signed package post-installation script subprocess returned error exit status 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1769035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 843431] Re: Logitech camera microphone does not work / makes "chipmunk" sound
I all, i just run a fresh install of xubuntu 18 and the issue is still there $ lsusb Bus 003 Device 002: ID 046d:0809 Logitech, Inc. Webcam Pro 9000 $ uname -a Linux MS-7756 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/843431 Title: Logitech camera microphone does not work / makes "chipmunk" sound To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/843431/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768906] Re: Xorg crash
Same symptoms with a brand new GTX 1070 ti :( ** Changed in: xorg (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768906 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
To monitor the latest news about a fix look at: https://gitlab.gnome.org/GNOME/gnome-shell/issues/227 And when that's available, we will update this bug with information about an Ubuntu fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume
So far, I can't wait for 5.49 when 5.46 is fixing my trouble. So I downgraded to have my audio chain usable, which was not the case at with 5.48 : Can't connect at ll my UE BOOM with Dell 5540. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759628 Title: bluez regression: Bluetooth audio fails to reconnect after resume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1759628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769035] [NEW] package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1
Public bug reported: Happened during installation. I'm a newbie Ubuntu user, so don't know any details about it. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: shim-signed 1.34.9+13-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 .proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No such file or directory: '/proc/sys/kernel/moksbstate_disabled' ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu May 3 22:59:10 2018 EFITables: May 03 23:03:38 imtiaz kernel: efi: EFI v2.40 by American Megatrends May 03 23:03:38 imtiaz kernel: efi: ESRT=0xacf77118 ACPI=0xac353000 ACPI 2.0=0xac353000 SMBIOS=0xf05b0 MPS=0xfd620 May 03 23:03:38 imtiaz kernel: secureboot: Secure boot could not be determined (mode 0) May 03 23:03:38 imtiaz kernel: esrt: Reserving ESRT space from 0xacf77118 to 0xacf77150. ErrorMessage: installed shim-signed package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-04-20 (13 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SecureBoot: 6 0 0 0 0 SourcePackage: shim-signed Title: package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-05-04 (0 days ago) ** Affects: shim-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic 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/1769035 Title: package shim-signed 1.34.9+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1769035/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766823] 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 1766823 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/1766823 Title: zram module not found in 4.4/4.15 KVM kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768546] Re: package virtualbox-ext-pack 5.2.10-3 failed to install/upgrade: installed virtualbox-ext-pack package post-installation script subprocess returned error exit status 1
satya@satya-VirtualBox:~$ sudo apt-get install virtualbox virtualbox-ext-pack Reading package lists... Done Building dependency tree Reading state information... Done virtualbox is already the newest version (5.2.10-dfsg-6). The following NEW packages will be installed: virtualbox-ext-pack 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/10.1 kB of archives. After this operation, 128 kB of additional disk space will be used. Do you want to continue? [Y/n] y Preconfiguring packages ... Selecting previously unselected package virtualbox-ext-pack. (Reading database ... 131741 files and directories currently installed.) Preparing to unpack .../virtualbox-ext-pack_5.2.10-3_all.deb ... License has already been accepted. Unpacking virtualbox-ext-pack (5.2.10-3) ... Setting up virtualbox-ext-pack (5.2.10-3) ... virtualbox-ext-pack: downloading: http://download.virtualbox.org/virtualbox/5.2.10/Oracle_VM_VirtualBox_Extension_Pack-5.2.10.vbox-extpack The file will be downloaded into /usr/share/virtualbox-ext-pack Hash mismatch Oracle_VM_VirtualBox_Extension_Pack-5.2.10.vbox-extpack: expected 8c31bc1d0337e6668e0d9140defc6deaf265087f855783dd09b873a064a70703, or wrong accept-license key dpkg: error processing package virtualbox-ext-pack (--configure): installed virtualbox-ext-pack package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: virtualbox-ext-pack E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768546 Title: package virtualbox-ext-pack 5.2.10-3 failed to install/upgrade: installed virtualbox-ext-pack package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox-ext-pack/+bug/1768546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769013] Re: Please merge ca-certificates-java 20180413 (main) from Debian unstable (main)
The attachment "ca-certificates- java_20170930ubuntu1_debdiff_20180413ubuntu1.patch" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769013 Title: Please merge ca-certificates-java 20180413 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1769013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766823] Re: zram module not found in 4.4/4.15 KVM kernel
This module does not exist in 4.4 kvm as well. Can be fixed by CONFIG_ZRAM=m ** Summary changed: - zram module not found in 4.15 KVM kernel + zram module not found in 4.4/4.15 KVM kernel ** Tags added: xenial ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766823 Title: zram module not found in 4.4/4.15 KVM kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
Is there a fix for this or not?. Please tell me there is -^- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769030] [NEW] package palapeli-data 4:15.12.3-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/icons/hicolor/128x128/apps/palapeli.png', which is also in package palapeli 4:15
Public bug reported: I was doing apt-get upgrade after switching to 18.04. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: palapeli-data 4:15.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-122.146-generic 4.4.117 Uname: Linux 4.4.0-122-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Fri May 4 00:23:05 2018 Dependencies: DuplicateSignature: package:palapeli-data:4:15.12.3-0ubuntu1 Unpacking palapeli-data (4:17.12.3-0ubuntu2) over (4:15.12.3-0ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-iQHMgW/687-palapeli-data_4%3a17.12.3-0ubuntu2_all.deb (--unpack): trying to overwrite '/usr/share/icons/hicolor/128x128/apps/palapeli.png', which is also in package palapeli 4:15.12.3-0ubuntu1 ErrorMessage: trying to overwrite '/usr/share/icons/hicolor/128x128/apps/palapeli.png', which is also in package palapeli 4:15.12.3-0ubuntu1 InstallationDate: Installed on 2014-10-31 (1280 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: palapeli Title: package palapeli-data 4:15.12.3-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/icons/hicolor/128x128/apps/palapeli.png', which is also in package palapeli 4:15.12.3-0ubuntu1 UpgradeStatus: Upgraded to bionic on 2018-05-02 (2 days ago) ** Affects: palapeli (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic need-duplicate-check package-conflict -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769030 Title: package palapeli-data 4:15.12.3-0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/share/icons/hicolor/128x128/apps/palapeli.png', which is also in package palapeli 4:15.12.3-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/palapeli/+bug/1769030/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766612] Re: linux-raspi2: 4.4.0-1088.96 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766612 Title: linux-raspi2: 4.4.0-1088.96 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766608] Re: linux-snapdragon: 4.4.0-1091.96 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766608 Title: linux-snapdragon: 4.4.0-1091.96 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766593] Re: linux-raspi2: 4.13.0-1018.19 -proposed tracker
** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Invalid ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766593 Title: linux-raspi2: 4.13.0-1018.19 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769029] [NEW] Display on Dell 1440x900 is not available
Public bug reported: Monitor resolution is limited to 1024x768 with no option for higher resolution ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 4 09:44:54 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd 82945G/GZ Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2018-05-03 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Gigabyte Technology Co., Ltd. 945GZM-S2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=2429ce45-7592-4cb5-974d-7446cb495a5b ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2007 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FG dmi.board.name: 945GZM-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFG:bd04/26/2007:svnGigabyteTechnologyCo.,Ltd.:pn945GZM-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn945GZM-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: 945GZM-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769029 Title: Display on Dell 1440x900 is not available To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769027] 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 1769027 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/1769027 Title: perf record crash: refcount_inc assertion failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767204] Re: perf record crash due to swapped xyarray function signatures
Confirmed I didn't get the error with your perf binary. However, I found another bug and patch. I'll open another bug and tag you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767204 Title: perf record crash due to swapped xyarray function signatures To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1753335] Re: Error with Windows 10 and Linux Mint 17
[Expired for ubiquity (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubiquity (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/1753335 Title: Error with Windows 10 and Linux Mint 17 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1753335/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1759300] Re: Gnome Shell: Touchpad right click (bottom right) area does not work
Mike, I agree we need smarter defaults and have proposed that for 18.10 here: https://trello.com/c/i3JvebJ9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759300 Title: Gnome Shell: Touchpad right click (bottom right) area does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1759300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1682049] Re: package ubuntu-app-launch 0.9+16.10.20160928-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1
[Expired for ubuntu-app-launch (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-app-launch (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/1682049 Title: package ubuntu-app-launch 0.9+16.10.20160928-0ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-app-launch/+bug/1682049/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769028] [NEW] package kodi-addons-dev (not installed) failed to install/upgrade: a tentar sobre-escrever '/usr/include/kodi/AEChannelData.h', que também está no pacote kodi-addon-dev 2:18.0+git2
Public bug reported: How I explain. I do not know what happened. I'm installing whit synaptic but I have many package broken. Sorry my English. in Portuguese is more simple ProblemType: Package DistroRelease: Ubuntu 18.04 Package: kodi-addons-dev (not installed) ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Fri May 4 04:45:05 2018 ErrorMessage: a tentar sobre-escrever '/usr/include/kodi/AEChannelData.h', que também está no pacote kodi-addon-dev 2:18.0+git20180504.0201-eb1e22e-0bionic Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: kodi Title: package kodi-addons-dev (not installed) failed to install/upgrade: a tentar sobre-escrever '/usr/include/kodi/AEChannelData.h', que também está no pacote kodi-addon-dev 2:18.0+git20180504.0201-eb1e22e-0bionic UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kodi (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/1769028 Title: package kodi-addons-dev (not installed) failed to install/upgrade: a tentar sobre-escrever '/usr/include/kodi/AEChannelData.h', que também está no pacote kodi-addon-dev 2:18.0+git20180504.0201-eb1e22e-0bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1769028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769027] [NEW] perf record crash: refcount_inc assertion failed
Public bug reported: Trying to run perf record ... --cgroup=mycgroup causes an immediate assertion failure: refcount_inc: Assertion `!(!refcount_inc_not_zero(r))' failed. Confirmed fixed by patching my linux-tools package with this upstream commit (on top of the commit in bug #1767204): https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux- stable.git/commit/tools/perf/util/cgroup.c?id=cd8dd032f61abeb08d2c03bab4968a9de231a1be ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: patch patch-accepted-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769027 Title: perf record crash: refcount_inc assertion failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1769027/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769026] [NEW] la instalacion paró luego del soporte de idiomas y de detectar hardware, cuando estaba instalando GRUB2 creo que es debido a un error mío con las particiones, estoy mareado con lo
Public bug reported: la instalacion paró luego del soporte de idiomas y de detectar hardware, cuando estaba instalando GRUB2 creo que es debido a un error mío con las particiones, estoy mareado con lo del gpt, el bios y el UEFI algo hice mal... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity 2.21.63.6 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-lowlatency 4.13.13 Uname: Linux 4.13.0-36-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CasperVersion: 1.376.2 Date: Fri May 4 01:07:14 2018 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntustudio.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-Studio 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: LANGUAGE=es_UY.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_UY.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-2.21.63.6 ubuntustudio xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769026 Title: la instalacion paró luego del soporte de idiomas y de detectar hardware, cuando estaba instalando GRUB2 creo que es debido a un error mío con las particiones, estoy mareado con lo del gpt, el bios y el UEFI algo hice mal... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1769026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769026] Re: la instalacion paró luego del soporte de idiomas y de detectar hardware, cuando estaba instalando GRUB2 creo que es debido a un error mío con las particiones, estoy mareado con lo de
Espero solucionarlo y saber luego como comentar este reporte porque la verdad nunca me hab{ia pasado -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769026 Title: la instalacion paró luego del soporte de idiomas y de detectar hardware, cuando estaba instalando GRUB2 creo que es debido a un error mío con las particiones, estoy mareado con lo del gpt, el bios y el UEFI algo hice mal... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1769026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1641290] Re: [04f3:0903] Elan Microelectronics Corp fingerprint reader not recognised
Hi, img_capture worked, but enroll didn't. Subsequent attempts with img_capture failed with similar problem as enroll. Maybe device not released properly? Will try to reboot the laptop and if things change will post again. Thanks for your efforts! lsusb output: ... Bus 001 Device 007: ID 04f3:0903 Elan Microelectronics Corp. ... uname -a Linux Asus-UX430U 4.13.0-39-generic #44-Ubuntu SMP Thu Apr 5 14:25:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux examples/img_capture fp:debug [fp_init] fp:debug [register_driver] registered driver upekts fp:debug [register_driver] registered driver aes3500 fp:debug [register_driver] registered driver aes4000 fp:debug [register_driver] registered driver aes2501 fp:debug [register_driver] registered driver aes2550 fp:debug [register_driver] registered driver uru4000 fp:debug [register_driver] registered driver vcom5s fp:debug [register_driver] registered driver upeksonly fp:debug [register_driver] registered driver aes1610 fp:debug [register_driver] registered driver aes1660 fp:debug [register_driver] registered driver aes2660 fp:debug [register_driver] registered driver vfs101 fp:debug [register_driver] registered driver vfs301 fp:debug [register_driver] registered driver vfs5011 fp:debug [register_driver] registered driver upektc fp:debug [register_driver] registered driver upektc_img fp:debug [register_driver] registered driver etes603 fp:debug [register_driver] registered driver vfs0050 fp:debug [register_driver] registered driver elan fp:debug [find_supporting_driver] driver elan supports USB device 04f3:0903 fp:debug [find_supporting_driver] selected driver elan supports USB device 04f3:0903 Found device claimed by ElanTech Fingerprint Sensor driver sync:debug [fp_dev_open] async:debug [fp_async_dev_open] elan:debug [dev_init] async:debug [fpi_drvcb_open_complete] status 0 sync:debug [sync_open_cb] status 0 Opened device. It's now time to scan your finger. sync:debug [fp_dev_img_capture] to be handled by elan async:debug [fp_async_capture_start] fp:debug [generic_acquire_start] action 4 elan:debug [dev_activate] elan:debug [elan_activate] elan:debug [elan_dev_reset] drv:debug [__ssm_call_handler] 0x5583508ce660 entering state 0 elan:debug [elan_run_cmd] 4019 elan:debug [elan_cmd_cb] elan:debug [elan_cmd_read] elan:debug [elan_cmd_cb] 0135 elan:debug [elan_cmd_done] drv:debug [__ssm_call_handler] 0x5583508ce660 entering state 1 elan:debug [activate_run_state] FW ver 0x0135 drv:debug [__ssm_call_handler] 0x5583508ce660 entering state 2 elan:debug [elan_run_cmd] 000c elan:debug [elan_cmd_cb] elan:debug [elan_cmd_read] elan:debug [elan_cmd_cb] 6000... (4 bytes) elan:debug [elan_cmd_done] drv:debug [__ssm_call_handler] 0x5583508ce660 entering state 3 elan:debug [activate_run_state] sensor dimensions, WxH: 96x96 drv:debug [__ssm_call_handler] 0x5583508ce660 entering state 4 elan:debug [elan_run_cmd] 402a elan:debug [elan_run_cmd] skipping for this device elan:debug [elan_cmd_done] drv:debug [fpi_ssm_mark_completed] 0x5583508ce660 completed with status 0 elan:debug [activate_complete] elan:debug [elan_calibrate] elan:debug [elan_dev_reset] drv:debug [__ssm_call_handler] 0x5583508cad10 entering state 0 elan:debug [elan_run_cmd] 0009 elan:debug [elan_cmd_cb] elan:debug [elan_cmd_read] elan:debug [elan_cmd_cb] 2a18... (18432 bytes) elan:debug [elan_cmd_done] drv:debug [__ssm_call_handler] 0x5583508cad10 entering state 1 elan:debug [elan_save_background] elan:debug [elan_save_frame] elan:debug [calibrate_run_state] FW does not support calibration drv:debug [fpi_ssm_mark_completed] 0x5583508cad10 completed with status 0 elan:debug [calibrate_complete] fp:debug [fpi_imgdev_activate_complete] status 0 async:debug [fpi_drvcb_capture_started] elan:debug [dev_change_state] 1 poll:debug [fpi_timeout_add] in 10ms poll:debug [get_next_timeout_expiry] next timeout in 0.009985s poll:debug [get_next_timeout_expiry] next timeout in 0.009963s poll:debug [get_next_timeout_expiry] first timeout already expired poll:debug [handle_timeout] elan:debug [elan_change_state] changing to 1 elan:debug [elan_capture] elan:debug [elan_dev_reset] drv:debug [__ssm_call_handler] 0x5583508cad10 entering state 0 elan:debug [elan_run_cmd] 4031 elan:debug [elan_cmd_cb] elan:debug [elan_cmd_read] elan:debug [elan_cmd_read] skipping read, not expecting anything elan:debug [elan_cmd_done] drv:debug [__ssm_call_handler] 0x5583508cad10 entering state 1 elan:debug [elan_run_cmd] 403f elan:debug [elan_cmd_cb] elan:debug [elan_cmd_read] elan:debug [elan_cmd_cb] 55 elan:debug [elan_cmd_done] drv:debug [__ssm_call_handler] 0x5583508cad10 entering state 2 fp:debug [fpi_imgdev_report_finger_status] finger on sensor elan:debug [dev_change_state] 2 elan:debug [elan_run_cmd] 0009 elan:debug [elan_cmd_cb] elan:debug [elan_cmd_read] elan:debug [elan_cmd_cb] f617... (18432 bytes) elan:debug [elan_cmd_done] drv:debug [__ssm_call_handler] 0x5583508cad10 entering state 3 elan:debug
[Bug 1759300] Re: Gnome Shell: Touchpad right click (bottom right) area does not work
I had GNOME (rather than Unity) as my default desktop before upgrading to 18.04, and I strongly believe that my settings should have been respected rather than overridden to the installation default. Whatever the merits of the choice of installation default, it seems clear error to impose it over a previously existing GNOME installation. My touchpad has hardware left and right buttons, and it is my understanding that it should therefore not default to "finger" mode but should instead default to "area" mode. I was not able to get two-finger secondary click to work in "finger" mode at all. The laptop is an Acer V3-574 and the touchpad identifies in dmesg as follows: hid-multitouch 0018:04F3:300B.0001: Ignoring the extra HID_DG_INPUTMODE input: ELAN0501:00 04F3:300B Touchpad as /devices/pci:00/INT3432:00/i2c-0/i2c-ELAN0501:00/0018:04F3:300B.0001/input/input8 hid-multitouch 0018:04F3:300B.0001: input,hidraw0: I2C HID v1.00 Mouse [ELAN0501:00 04F3:300B] on i2c-ELAN0501:00 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759300 Title: Gnome Shell: Touchpad right click (bottom right) area does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1759300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1315342] Re: Stop appending 3rd party PPA names with warnings
> The ammendments "# disabled on upgrade to trusty" is a comment and subsequently has not effect on the entry. Nope, it makes the name of every PPA in the software properties dialog the same: 'disabled on upgrade to bionic'. Extremely annoying and difficult to manage. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1315342 Title: Stop appending 3rd party PPA names with warnings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1315342/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769022] [NEW] ubuntu 18.04 freezes after the login
Public bug reported: I am not able to log to ubuntu 18.04 after the upgrade. When I login I get setup screen with the word "Welcome" and the system freezes ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu May 3 23:29:56 2018 DistUpgraded: 2018-05-03 01:59:32,397 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6520G] [1002:9647] (prog-if 00 [VGA controller]) Subsystem: Lenovo BeaverCreek [Radeon HD 6520G] [17aa:3971] InstallationDate: Installed on 2016-11-19 (530 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 129925U ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=91dffd26-787f-4656-94b0-9568086633ac ro radeon.dpm=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago) dmi.bios.date: 07/20/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 54CN18WW dmi.board.asset.tag: Base Board Asset Tag Unknown dmi.board.name: Torpedo dmi.board.vendor: LENOVO dmi.board.version: 109-C06210-00B dmi.chassis.asset.tag: Chassis Asset Tag Unknown dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Chassis Version Unknown dmi.modalias: dmi:bvnLENOVO:bvr54CN18WW:bd07/20/2011:svnLENOVO:pn129925U:pvrIdeapadZ575:rvnLENOVO:rnTorpedo:rvr109-C06210-00B:cvnLENOVO:ct10:cvrChassisVersionUnknown: dmi.product.family: IDEAPAD dmi.product.name: 129925U dmi.product.version: Ideapad Z575 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu May 3 22:52:41 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769022 Title: ubuntu 18.04 freezes after the login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769022/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767968] Re: systemd-udev cause high cpu load after upgrade to bionic
Have a look here: https://dev.solus-project.com/T5224 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767968 Title: systemd-udev cause high cpu load after upgrade to bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1767968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768906] Re: Xorg crash
Should I set this back to new? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768906 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768906/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769013] Re: Please merge ca-certificates-java 20180413 (main) from Debian unstable (main)
Updated debdiffs with the right LP fix number (bug #1739631 instead of #1767726). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769013 Title: Please merge ca-certificates-java 20180413 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1769013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769013] Re: Please merge ca-certificates-java 20180413 (main) from Debian unstable (main)
Debdiff from Debian version 20180413. ** Patch added: "ca-certificates-java_20180413_debdiff_20180413ubuntu1.patch" https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1769013/+attachment/5133329/+files/ca-certificates-java_20180413_debdiff_20180413ubuntu1.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769013 Title: Please merge ca-certificates-java 20180413 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1769013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769013] Re: Please merge ca-certificates-java 20180413 (main) from Debian unstable (main)
Debdiff from Ubuntu version 20170930ubuntu1. ** Patch removed: "ca-certificates-java_20170930ubuntu1_debdiff_20180413ubuntu1.patch" https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1769013/+attachment/5133321/+files/ca-certificates-java_20170930ubuntu1_debdiff_20180413ubuntu1.patch ** Patch removed: "ca-certificates-java_20180413_debdiff_20180413ubuntu1.patch" https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1769013/+attachment/5133322/+files/ca-certificates-java_20180413_debdiff_20180413ubuntu1.patch ** Patch added: "ca-certificates-java_20170930ubuntu1_debdiff_20180413ubuntu1.patch" https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1769013/+attachment/5133328/+files/ca-certificates-java_20170930ubuntu1_debdiff_20180413ubuntu1.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769013 Title: Please merge ca-certificates-java 20180413 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1769013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767410] Re: linux-hwe-edge: 4.15.0-21.22~16.04.1 -proposed tracker
** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1767397 phase: Uploaded -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767410 Title: linux-hwe-edge: 4.15.0-21.22~16.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1767410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768830] Re: the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04
This is the debdiff. Sponsor team, please help submit the build request to the queue. thx. ** Description changed: Steps: 1. Install the ubuntu 18.04 on the machine of Lenovo P520. 2. Login system. 3. Plug in an external headset to record and playback in front and rear panel. Expected result: Output and input audio should work in front and rear panel. Actual result: Front panel audio doesn't work at all. Just output audio working, input audio does't work in rear panel. + SRU Document: - So far the ubuntu 18.04 just imported alsa-lib v1.1.3-5 from debian.org. + [Impact] - And we have several Lenovo machines like Lenovo P520 which have 2 - analogue audio codecs on them, to make the audio work on those machines, - the kernel needs 3 patches for alsa driver, and those 3 patches are - already in the linux kernel from linux-4.12, kernel is not a blocking - issue under ubuntu 18.04: + We have several Lenovo machines like Lenovo P520 which have 2 analogue + audio codecs on them, the internal speaker and front headset are + connected to the 1st codec, the Rear mic, Line in and Line out are + connected to the 2nd codec. So far, under ubuntu 18.04 with the alsa- + lib/libasound2 v1.1.3-5, only the audio devices (internal speaker and + front headset) on the 1st codec can work. To make all audio devices work + on this machine, upstream provided 3 patches for kernel audio driver and + 5 patches for alsa-lib. The kernel patches are already in the + linux-4.12, so this is not a problem anymore under 18.04 since we use + linux-4.15 in 18.04. For the 5 patches of alsa-lib, we need to backport + them to v1.1.3-5, the 5 patches are list as below: - 7beb3a6e ALSA: hda - Support Gigabyte Gaming board with dual Realtek codecs - 56798e6b ALSA: hda - Use a helper function for renaming kctl names - ca169cc2 ALSA: hda/realtek - Add Dual Codecs support for Lenovo P520/420 + 2b9b3f01 ucm: Assure the user input card name not to exceed max size of card long name (it is in the alsa-lib v1.1.4) + 4b9297e6 ucm: Load device-specific configuration file based on the card long name (it is in the alsa-lib v1.1.4) + b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is in the alsa-lib v1.1.6) + 181f8e25 ucm: adding the folder of card_long_name when finding verb conf file (it is in the alsa-lib v1.1.6+) + 81db276f conf/ucm: increase the input volume for LineIn (it is in the alsa-lib v1.1.6+) + Some explanation for these 5 patches, to make the audio work, the alsa- + lib needs to add an audio configuration file and verb conf file for + lenovo machines with dual codecs, these two files are put in a folder + named by card_long_name, and the name of configuration file itself is + also named by card_long_name, this is implemented by the patches of NO. + 3rd and 5th. - Besides those 3 patches for kernel, we also need 5 more patches for alsa-lib. Because the ucm configuration files are named by card_long_name, these 5 patches intends to introduce the card_long_name searching for ucm and the configuration folder/files for Lenovo machines with dual analogue codecs. the 5 patches are: + But the alsa-lib v1.1.3-5 itself doesn't support to search conf file with card_long_name, it only support searching with card_name, So we need to backport 3 patches to let alsa-lib v1.1.3-5 support to search with card_long_name, these 3 patches are No. 1st, 2nd and 4th. + + [Test Case] - 2b9b3f01 ucm: Assure the user input card name not to exceed max size of - card long name (it is in the alsa-lib v1.1.4) + On the Lenovo machines with dual codecs (p520), I insatlled the + libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the + alsa-lib can find the conf file and can parse the conf file + successfully, and I tested the internal speaker, front headset, rear + mic, line out and line in, all audio devices work well. - 4b9297e6 ucm: Load device-specific configuration file based on the card - long name (it is in the alsa-lib v1.1.4) + On a HP and Dell machines without dual codecs, I insatlled the + libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the + alsa-lib can't find conf file by card_long_name and card_name, the + pulseaudio will drive the sound card as before, so all audio functions + worked well as before. - b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is in - the alsa-lib v1.1.6) + [Regression Potential] - 181f8e25 ucm: adding the folder of card_long_name when finding verb conf - file (it is in the alsa-lib v1.1.6+) + After adding these 5 patches, there 2 two changes introduced into the + alsa-lib v1.1.3-5ubuntu1: - 81db276f conf/ucm: increase the input volume for LineIn (it is in the - alsa-lib v1.1.6+) + 1) before: only have folder and conf files named by card_name; after: has one folder and conf file named by card_long_name, this folder and conf file will not affect others, + 2) before: the ucm parser will search the conf
[Bug 1768121] Re: Mainline Kernel since 4.16.4 has postinstall script error
this same issue installing every kernel above v4.16.3 (which works) I was forced to reinstall ubuntu on restart during the v4.16.6 all was lost and unrecoverable. ** Attachment added: "screenshot of last attempted install" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768121/+attachment/5133323/+files/Screenshot%20from%202018-05-03%2023-01-23.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768121 Title: Mainline Kernel since 4.16.4 has postinstall script error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769013] Re: Please merge ca-certificates-java 20180413 (main) from Debian unstable (main)
Debdiff from Debian version 20180413. ** Patch added: "ca-certificates-java_20180413_debdiff_20180413ubuntu1.patch" https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1769013/+attachment/5133322/+files/ca-certificates-java_20180413_debdiff_20180413ubuntu1.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769013 Title: Please merge ca-certificates-java 20180413 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1769013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769013] Re: Please merge ca-certificates-java 20180413 (main) from Debian unstable (main)
Debdiff from Ubuntu version 20170930ubuntu1. ** Patch added: "ca-certificates-java_20170930ubuntu1_debdiff_20180413ubuntu1.patch" https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1769013/+attachment/5133321/+files/ca-certificates-java_20170930ubuntu1_debdiff_20180413ubuntu1.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769013 Title: Please merge ca-certificates-java 20180413 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1769013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769016] [NEW] nsswitch.conf doesn't specify 'resolve' to support systemd-resolved
Public bug reported: After upgrading from Ubuntu 16.04 to 18.04, my openconnect vpn connection stopped working. The problem appeared to be related to DNS resolution. After some digging, I discovered that the vpnc-script hook executed by openconnect was adding my VPN DNS servers to /etc/resolv.conf, which systemd-resolve --status was reporting as part of the global config instead of being associated with my VPN interface (tun0). This appeared to break all VPN and non-VPN traffic in my configuration. I found that vpnc-script needed to find 'resolve' in /etc/nsswitch.conf in order to correctly configure the VPN DNS servers with systemd- resolved instead of prepending them to /etc/resolv.conf. http://git.infradead.org/users/dwmw2/vpnc- scripts.git/commitdiff/62e86babac9f734ba031a547501cbe8e5940d83b Adding 'resolve' to the 'hosts:' line in my /etc/nsswitch.conf allowed normal traffic flow. It seems like if 18.04 defaults to using systemd-resolve for DNS resolutions, then the default nsswitch.conf configuration should also declare 'resolve' in the 'hosts:' line, which does not appear to be the case. This would have allowed my VPN connection to continue working successfully after the upgrade. $ lsb_release -rd Description:Ubuntu 18.04 LTS Release:18.04 $ dpkg -l libc-bin openconnect systemd vpnc-scripts Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionArchitecture Description +++-=-==-=- ii libc-bin 2.27-3ubuntu1 amd64 GNU C Library: Binaries ii openconnect 7.08-3 amd64 open client for Cisco AnyConnect VPN ii systemd 237-3ubuntu10 amd64 system and service manager ii vpnc-scripts 0.1~git20171005-1 all Network configuration scripts for VPNC and OpenConnect ** Affects: glibc (Ubuntu) Importance: Undecided Status: New ** Tags: openconnect systemd-resolve vpnc-script -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769016 Title: nsswitch.conf doesn't specify 'resolve' to support systemd-resolved To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1769016/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769013] [NEW] Please merge ca-certificates-java 20180413 (main) from Debian unstable (main)
Public bug reported: There's a new ca-certificates-java package in debian unstable versioned 20180413 which conflicts with cosmic's version 20170930ubuntu1 [1] and requires a merge. The following changes should be kept: 1) debian/control: Bump javahelper build dependency. 2) debian/rules: 2a) Explicitly depend on openjdk-11-jre-headless, needed to configure. 2b) Replace javac arguments '-source 1.7 -target 1.7' with '--release 7' as, per JEP-247, it also takes care of setting the right -bootclasspath argument. And a new change should be considered: - remove the creation of a default jvm-*.cfg file from debian/jks-keystore.hook.in as openjdk packages already provides a default jvm with the right configuration. [1] https://merges.ubuntu.com/main.html?query=ca-certificates-java ** Affects: ca-certificates-java (Ubuntu) Importance: Undecided Status: New ** Tags: cosmic upgrade-software-version ** Tags added: cosmic ** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769013 Title: Please merge ca-certificates-java 20180413 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1769013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720438] Re: brightness control broken nvidia
** Changed in: gnome-power Status: Unknown => Confirmed ** Changed in: gnome-power 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/1720438 Title: brightness control broken nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/1720438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766607] Re: linux-lts-xenial: 4.4.0-123.147~14.04.1 -proposed tracker
4.4.0-123.147~14.04.1 - generic Regression test CMPL. Issue to note in amd64: ubuntu_ecryptfs - extend-file-random.sh.btrfs (bug 1684788) trunc-file.sh.btrfs (bug 1684789) ubuntu_kvm_smoke_test - uvt-kvm wait issue (bug 1732883) ubuntu_kvm_unit_tests - 27 failed on amaura, 26 failed on pepe ubuntu_qrt_apparmor - longpath test failed with permission denied (bug 1768784) Issue to note in arm64: hwclock - issue for HP m400 (bug 1716603) ubuntu_cts_kernel - lp1262692 failed, bug for iproute2 (bug 1715376) ubuntu_ecryptfs - extend-file-random.sh.btrfs (bug 1684788) trunc-file.sh.btrfs (bug 1684789) ubuntu_kvm_smoke_test - unable to create KVM with uvtool (bug 1749427) ubuntu_qrt_apparmor - longpath test failed with permission denied (bug 1768784), test_old_trusty_regression_testsuite failed to build (bug 1699987) ubuntu_qrt_kernel_security - 050 failed (bug 1684776) Issue to note in i386: ubuntu_ecryptfs - extend-file-random.sh.btrfs (bug 1684788) trunc-file.sh.btrfs (bug 1684789) ubuntu_kvm_smoke_test - uvt-kvm wait issue (bug 1732883) ubuntu_kvm_unit_tests - failed to build (bug 1765366) ubuntu_qrt_apparmor - longpath test failed with permission denied (bug 1768784) Issue to note in ppc64le: ubuntu_cts_kernel - lp1262692 failed, bug for iproute2 (bug 1715376) ubuntu_kvm_smoke_test - uvtool issue (bug 1729854) ubuntu_qrt_apparmor - longpath test failed with permission denied (bug 1768784) Switching this task to Incomplete due to the error reported by the ubuntu_qrt_apparmor test, bug 1768784, which is a potential regression. ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Incomplete ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766607 Title: linux-lts-xenial: 4.4.0-123.147~14.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1766607/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720438] Re: brightness control broken nvidia
Please try the 'xbacklight' command. And see also https://bugzilla.gnome.org/show_bug.cgi?id=688052 ** Also affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New ** Bug watch added: GNOME Bug Tracker #688052 https://bugzilla.gnome.org/show_bug.cgi?id=688052 ** Also affects: gnome-power via https://bugzilla.gnome.org/show_bug.cgi?id=688052 Importance: Unknown Status: Unknown ** Changed in: gnome-power-manager (Ubuntu) Status: New => Confirmed ** Changed in: gnome-power-manager (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720438 Title: brightness control broken nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-power/+bug/1720438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768991] 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 1768991 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/1768991 Title: [bytchtes8316] Sound does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768994] Re: Upgrade to 18.04 resets touchpad behavior to default, overriding existing GNOME settings
*** This bug is a duplicate of bug 1759300 *** https://bugs.launchpad.net/bugs/1759300 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1759300, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1759300 Gnome Shell: Touchpad right click (bottom right) area does not work -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768994 Title: Upgrade to 18.04 resets touchpad behavior to default, overriding existing GNOME settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1768994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768993] Re: Upgrade from 17.10 to 18.04 does not start gdm3 on boot
It sounds like you have a fix. Can you reproduce the bug after more reboots? ** Tags added: radeon ** Summary changed: - Upgrade from 17.10 to 18.04 does not start gdm3 on boot + [radeon] Upgrade from 17.10 to 18.04 does not start gdm3 on boot ** Changed in: gdm3 (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/1768993 Title: [radeon] Upgrade from 17.10 to 18.04 does not start gdm3 on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1768993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768991] Re: outputsounddoesnotwork
I agree, that looks relevant: [ 4849.250374] Audio Port: ASoC: no backend DAIs enabled for Audio Port which comes from the kernel, sound/soc/soc-pcm.c: /* there is no point preparing this FE if there are no BEs */ if (list_empty(>dpcm[stream].be_clients)) { dev_err(fe->dev, "ASoC: no backend DAIs enabled for %s\n", fe->dai_link->name); ret = -EINVAL; goto out; } ** Summary changed: - outputsounddoesnotwork + [bytchtes8316] Sound does not work ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Linux Kernel Bug Tracker #189261 https://bugzilla.kernel.org/show_bug.cgi?id=189261 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768991 Title: [bytchtes8316] Sound does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768991] Re: [bytchtes8316] Sound does not work
The same hardware is mentioned in https://bugzilla.kernel.org/show_bug.cgi?id=189261, although it appears that's not what the original reporter of that bug has. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768991 Title: [bytchtes8316] Sound does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767166] Re: IBMCloud datasource does not recognize provisioning in debug mode.
Validated against Xenial and Artful, while IBMCloud doesn't have any publicly available artful images, we've contrived an example upgrade from public xenial instance to artful to ensure it doesn't break. Abridged validation logs below === BEGIN SRU Validation Xenial === root@publishing:~# cat > runcmd.yaml < #cloud-config > hostname: SRU-worked > runcmd: > - [sh, '-c', 'cat /proc/uptime > /run/runcmd-ran.txt'] > EOF root@publishing:~# VM_IP=`launch-softlayer --pubkey-file ~/.ssh/id_rsa.pub -u runcmd.yaml -i xenial | awk '/primary ip/{printf "root@%s", $3}'` Destroy instance with: slcli virtual cancel 54555262 root@publishing:~# ssh $VM_IP -- cat /run/cloud-init/result.json { "v1": { "datasource": "DataSourceConfigDrive [net,ver=2][source=/var/lib/cloud/seed/config_drive]", "errors": [] } } root@publishing:~# ssh $VM_IP -- cloud-init analyze show; -- Boot Record 01 -- The total time elapsed since completing an event is printed after the "@" character. The time the event takes is printed after the "+" character. Starting stage: init-local |`->no cache found @00.01600s +00.0s |`->found local data from DataSourceConfigDrive @00.05300s +00.00500s Finished stage: (init-local) 00.24200 seconds Starting stage: init-network |`->restored from cache with run check: DataSourceConfigDrive [net,ver=2][source=/var/lib/cloud/seed/config_drive] @01.00900s +00.00500s |`->reading and applying user-data @01.10100s +00.00500s |`->reading and applying vendor-data @01.10600s +00.0s |`->config-migrator ran successfully @01.42800s +00.0s |`->config-seed_random ran successfully @01.42900s +00.00500s |`->config-bootcmd ran successfully @01.43400s +00.00100s |`->config-write-files ran successfully @01.43500s +00.00100s |`->config-growpart ran successfully @01.43700s +00.24800s |`->config-resizefs ran successfully @01.68600s +00.04900s |`->config-disk_setup ran successfully @01.73500s +00.00200s |`->config-mounts ran successfully @01.73700s +00.22200s |`->config-set_hostname ran successfully @01.96000s +00.01500s |`->config-update_hostname ran successfully @01.97600s +00.00200s |`->config-update_etc_hosts ran successfully @01.97800s +00.00200s |`->config-ca-certs ran successfully @01.98000s +00.00100s |`->config-rsyslog ran successfully @01.98200s +00.00100s |`->config-users-groups ran successfully @01.98300s +00.06100s |`->config-ssh ran successfully @02.04400s +00.58000s Finished stage: (init-network) 01.64600 seconds Starting stage: modules-config |`->config-emit_upstart ran successfully @05.04800s +00.0s |`->config-snap_config ran successfully @05.04800s +00.00100s |`->config-ssh-import-id ran successfully @05.05000s +00.00100s |`->config-locale ran successfully @05.05100s +01.30800s |`->config-set-passwords ran successfully @06.36000s +00.08500s |`->config-grub-dpkg ran successfully @06.44500s +00.50100s |`->config-apt-pipelining ran successfully @06.94600s +00.00400s |`->config-apt-configure ran successfully @06.95000s +00.19600s |`->config-ntp ran successfully @07.14700s +00.00100s |`->config-timezone ran successfully @07.14900s +00.00100s |`->config-disable-ec2-metadata ran successfully @07.15000s +00.0s |`->config-runcmd ran successfully @07.15100s +00.00200s |`->config-byobu ran successfully @07.15300s +00.00100s Finished stage: (modules-config) 02.16900 seconds Starting stage: modules-final |`->config-snappy ran successfully @26.36800s +00.00300s |`->config-package-update-upgrade-install ran successfully @26.37100s +00.00100s |`->config-fan ran successfully @26.37200s +00.00100s |`->config-landscape ran successfully @26.37400s +00.00100s |`->config-lxd ran successfully @26.37500s +00.00100s |`->config-puppet ran successfully @26.37600s +00.00100s |`->config-chef ran successfully @26.37700s +00.00100s |`->config-salt-minion ran successfully @26.37900s +00.00100s |`->config-mcollective ran successfully @26.38000s +00.00100s |`->config-rightscale_userdata ran successfully @26.38100s +00.00100s |`->config-scripts-vendor ran successfully @26.38300s +00.0s |`->config-scripts-per-once ran successfully @26.38400s +00.00100s |`->config-scripts-per-boot ran successfully @26.38500s +00.0s |`->config-scripts-per-instance ran successfully @26.38600s +00.00100s |`->config-scripts-user ran successfully @26.38700s +00.00700s |`->config-ssh-authkey-fingerprints ran successfully @26.39500s +00.01500s |`->config-keys-to-console ran successfully @26.41100s +00.09900s |`->config-phone-home ran successfully @26.51100s +00.00200s |`->config-final-message ran successfully @26.51300s +00.00600s |`->config-power-state-change ran successfully @26.51900s +00.00100s Finished stage: (modules-final) 00.21400 seconds Total Time: 4.27100 seconds -- Boot Record 02 -- The total time elapsed since completing an event is printed after the "@" character. The time the event takes is printed after the "+" character. Starting stage: init-local |`->restored from checked cache: DataSourceConfigDrive
[Bug 1673292] Re: dep3changelog fails to extract Launchpad bug # due to whitespace
This bug was fixed in the package devscripts - 2.18.2ubuntu1 --- devscripts (2.18.2ubuntu1) cosmic; urgency=medium * debian/tests/control: Depend on python3-pyftpdlib for the ftp tests. -- Adam ConradThu, 03 May 2018 15:18:46 -0600 ** Changed in: devscripts (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/1673292 Title: dep3changelog fails to extract Launchpad bug # due to whitespace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/devscripts/+bug/1673292/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768877] Re: localedef assert failure: malloc(): memory corruption
No, it does not make any difference. Just to be sure I've changed the default locale to C (because en_US.UTF-8 was not compiled neither), reboot and tried locale-gen again. Same error. Seth, I've installed a bunch of packages after this error appears. It was surprising to me too that a deep malloc error doesn't stopped the machine to install and configure packages. Anyway I'll do a new fresh ubuntu 18.04 installation ASAP. The problem is that this machine is a headless computing node, so the installation procedure is by netboot packages only (PXE, tfpboot etc). And, if this error continues, I'll do another try with ubuntu 17.10. Thanks in advance! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768877 Title: localedef assert failure: malloc(): memory corruption To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1768877/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720438] Re: brightness control broken nvidia
Also, obviously, the above only works in Xorg logins. ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** 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/1720438 Title: brightness control broken nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769011] [NEW] The signed binary grubx64.efi does not include the tga module
Public bug reported: When secure boot is enabled on an EFI system, it is not possible to display background images in TGA format because the tga module is not pre-loaded by the signed grubx64.efi binary and it is not possible to insmod the module in a secure boot environment. The jpeg and png modules are pre-loaded and it is possible to display background images in those formats. Since the backgrounds in the grub2-splashimages package are distributed as TGA images I believe this should be considered a bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: grub-efi-amd64-signed 1.93+2.02-2ubuntu8 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: KDE Date: Fri May 4 11:51:07 2018 InstallationDate: Installed on 2018-05-02 (1 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: grub2-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769011 Title: The signed binary grubx64.efi does not include the tga module To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1769011/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720438] Re: brightness control broken nvidia
Note to developers: The tricky thing about this bug is that you may need a pure Nvidia system. Not a hybrid. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720438 Title: brightness control broken nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767993] Re: Lubuntu: X11 freezing/low resolution on N3150 intel graphics
Please be more polite. I committed more time to researching this bug report yesterday than any other. What the motherboard is capable of is at least relevant and you should be aware of it. While you are using the kernel parameter "nomodeset", the default X graphics driver ("modesetting") will be limited to 1024x768. That is not a bug. If you would like to get back to the older graphics driver that may work better for you (and may ignore the "nomodeset"), then you will need to force it to use the intel driver instead of modesetting: Section "Device" Identifier "devname" Driver "intel" EndSection in /etc/X11/xorg.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767993 Title: Lubuntu: X11 freezing/low resolution on N3150 intel graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1767993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1720438] Re: brightness control broken nvidia
If your backlight is wired through Nvidia then I think you may need to use the xbacklight interface. You can do it manually by installing: sudo apt install xbacklight and running xbacklight ... If that works for you then I think the problem is that mutter/gnome- shell isn't using/supporting/checking the X backlight interface. Only the kernel interfaces. ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Incomplete ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1720438 Title: brightness control broken nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1246981] Re: Bluetooth mouse fails to re-connect after sleep.
** Changed in: bluez (Ubuntu) Importance: High => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1246981 Title: Bluetooth mouse fails to re-connect after sleep. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752530] Re: Logitech touchpad hesitates or stops
** Changed in: libinput (Ubuntu) Status: Incomplete => Triaged ** Changed in: libinput (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/1752530 Title: Logitech touchpad hesitates or stops To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1752530/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766137] Re: [regression] Password accepted but login fails (blank purple screen and mouse pointer only)
That's not a bug. There's nothing on F7. Your session is on F2, and the login screen is F1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766137 Title: [regression] Password accepted but login fails (blank purple screen and mouse pointer only) To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1766137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763977] Re: Sddm service fails in Bionic
** Changed in: sddm (Ubuntu) Assignee: Simon Quigley (tsimonq2) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763977 Title: Sddm service fails in Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1763977/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757644] Re: Please port your package away from Qt 4
** Changed in: gammaray (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757644 Title: Please port your package away from Qt 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gammaray/+bug/1757644/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
** Description changed: The Ubuntu installer crashes on hiDPI machines (QHD/UHD etc). Although it was working some weeks/months ago, so this is a recent regression. + + Update: Actually the crash occurs on slow-ish systems due to a race + condition. It's not strictly only hi-DPI machines - that's just the most + common place it is experienced. --- https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77 https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15 https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7 https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524 --- WORKAROUND: 1. Boot into the live session. 2. Settings > Devices > Displays > Scale = 100% 3. Click Apply. 4. Proceed with installation: Click "Install Ubuntu 18.04 LTS". --- Crashed in a VM in the middle of installation. The host is Bionic up to date. From the journal Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 ip:7f5a76936961 sp:7ffde5090c50 error:0 in libglib-2.0.so.0.5400.1[7f5a768e6000+111000] Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation: Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last): Feb 23 12:52:41 ubuntu /install.py[6858]: File "/usr/share/ubiquity/install.py", line 757, in Feb 23 12:52:41 ubuntu /install.py[6858]: install.run() Feb 23 12:52:41 ubuntu /install.py[6858]: File "/usr/share/ubiquity/install.py", line 135, in run Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all() Feb 23 12:52:41 ubuntu /install.py[6858]: File "/usr/share/ubiquity/install.py", line 505, in copy_all Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + copy_progress) Feb 23 12:52:41 ubuntu /install.py[6858]: File "/usr/lib/python3/dist-packages/debconf.py", line 83, in Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: self.command(command, *args, **kw)) Feb 23 12:52:41 ubuntu /install.py[6858]: File "/usr/lib/python3/dist-packages/debconf.py", line 104, in command Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status) Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for int() with base 10: '' ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CasperVersion: 1.388 Date: Fri Feb 23 12:52:28 2018 ExecutablePath: /usr/lib/ubiquity/bin/ubiquity InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr keyboard-configuration/variantcode=oss InterpreterPath: /usr/bin/python3.6 LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 Signal: 5 SourcePackage: ubiquity StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: ubiquity crashed with signal 5 in _XEventsQueued() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751252 Title: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: '' To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1751252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757749] Re: Please port your package away from Qt 4
** Changed in: linkchecker (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1757749 Title: Please port your package away from Qt 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linkchecker/+bug/1757749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1757618] Re: Please port your package away from Qt 4
** Changed in: collatinus (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: collatinus (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/1757618 Title: Please port your package away from Qt 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/collatinus/+bug/1757618/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769010] Re: BBC weather dataengine broken due to changed RSS feed
Backporting the patch will take a bit of effort + time (that I don't have right now). ** Changed in: plasma-workspace (Ubuntu Xenial) Assignee: Simon Quigley (tsimonq2) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769010 Title: BBC weather dataengine broken due to changed RSS feed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1769010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''
You will get the same behaviour using the cairo fix too: https://bugs.freedesktop.org/show_bug.cgi?id=98883#c6 ** Changed in: cairo (Ubuntu) Importance: Undecided => High ** Changed in: cairo (Ubuntu Bionic) Importance: Undecided => High ** No longer affects: glib2.0 (Ubuntu) ** No longer affects: glib2.0 (Ubuntu Bionic) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751252 Title: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: '' To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1751252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769010] [NEW] BBC weather dataengine broken due to changed RSS feed
Public bug reported: The URLs of the BBC weather feeds seem to have changed, resulting in the dataengine to use no longer existing URLs. [Impact] This is a user-impacting regression that could result in weather feeds being non-functional for some users. [Test Case] Existing configured weather applets using a location from a BBC weather service should work again. Newly configured weather applets using a BBC weather service should also work. [Regression Potential] The regression happened in the first place due to the RSS feeds changing on the BBC site. If they change again, this will regress again. ** Affects: plasma-workspace (Ubuntu) Importance: Medium Status: Fix Released ** Affects: plasma-workspace (Ubuntu Xenial) Importance: Medium Status: In Progress ** Also affects: plasma-workspace (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: plasma-workspace (Ubuntu Trusty) 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/1769010 Title: BBC weather dataengine broken due to changed RSS feed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1769010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769010] Re: BBC weather dataengine broken due to changed RSS feed
Bionic will be addressed when Plasma 5.12.5 is SRUed. Other releases need explicit SRUs to them. ** Changed in: plasma-workspace (Ubuntu) Status: New => Fix Released ** Changed in: plasma-workspace (Ubuntu) Importance: Undecided => High ** Changed in: plasma-workspace (Ubuntu Trusty) Importance: Undecided => High ** Changed in: plasma-workspace (Ubuntu) Importance: High => Medium ** Changed in: plasma-workspace (Ubuntu Trusty) Importance: High => Medium ** Changed in: plasma-workspace (Ubuntu Xenial) Importance: Undecided => High ** Changed in: plasma-workspace (Ubuntu Xenial) Status: New => In Progress ** Changed in: plasma-workspace (Ubuntu Trusty) Status: New => In Progress ** Changed in: plasma-workspace (Ubuntu Xenial) Importance: High => Medium ** Changed in: plasma-workspace (Ubuntu Xenial) Assignee: (unassigned) => Simon Quigley (tsimonq2) ** Changed in: plasma-workspace (Ubuntu Trusty) Assignee: (unassigned) => Simon Quigley (tsimonq2) ** No longer affects: plasma-workspace (Ubuntu Trusty) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769010 Title: BBC weather dataengine broken due to changed RSS feed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1769010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1246981] Re: Bluetooth mouse fails to re-connect after sleep.
I am having this issue with Ubuntu 18.04 fresh install on Gigabyte Aero 15X v8. Mouse is bluetooth Digio2 Trackball. After sleep, on/off switch is broken. Must remove and re-add from bluetooth settings. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1246981 Title: Bluetooth mouse fails to re-connect after sleep. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246981/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1698083] Re: Middle-click titlebar actions (like maximizing vertically) don't work in Wayland sessions
"Expired" is a misnomer. It just moved to https://gitlab.gnome.org/GNOME/gtk/issues/539 Since we can't change that status, and shouldn't, I have just removed the gtk task. See the above link instead. ** No longer affects: gtk ** Description changed: + Upstream: https://gitlab.gnome.org/GNOME/gtk/issues/539 + In Gnome Tweak Tool you can configure vertical maximizing for: Windows > Titlebar Actions > Middle-Click However this feature seems to get ignored in Wayland sessions (it just maximizes fully instead). It only works correctly in Xorg Gnome sessions. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu6 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Thu Jun 15 14:46:04 2017 DisplayManager: lightdm InstallationDate: Installed on 2017-05-03 (43 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1698083 Title: Middle-click titlebar actions (like maximizing vertically) don't work in Wayland sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1698083/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748565] Re: Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f)
This is probably not a showstopper. You are confusing Bluetooth bugs for a probably harmless bluetooth log message. This but is about the latter. If something is "completely unusable" then please log a new bug for that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1748565 Title: Kernel regularly logs: Bluetooth: hci0: last event is not cmd complete (0x0f) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1748565/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1687246] Re: GNOME Shell should support fractional (non-integer) Hi-DPI scaling
I also recall SGI workstations had some nice arbitrary scaling in the 1990's. But this is not about the state of the art, it's about the state of gnome-shell :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1687246 Title: GNOME Shell should support fractional (non-integer) Hi-DPI scaling To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1687246/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768764] Re: disable wayland by default - nvidia proprietary drivers backlight
Please run this command to tell us more information about your system: apport-collect 1768764 ** Changed in: gdm3 (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/1768764 Title: disable wayland by default - nvidia proprietary drivers backlight To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1768764/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768649] Re: [CVE] Access to privileged files
Updated packages are in the security proposed PPA. I have tested all three in fresh, fully updated virtual machines of each release, and all three work. The Trusty backport is pending a review, but I would call the Xenial, Artful, and Bionic updates good. ** Changed in: kwallet-pam (Ubuntu Artful) Status: New => Fix Committed ** Changed in: kwallet-pam (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: kwallet-pam (Ubuntu Xenial) Status: New => Fix Committed ** No longer affects: kwallet-pam (Ubuntu Trusty) ** No longer affects: pam-kwallet (Ubuntu Xenial) ** No longer affects: pam-kwallet (Ubuntu Artful) ** No longer affects: pam-kwallet (Ubuntu Bionic) ** No longer affects: pam-kwallet (Ubuntu Cosmic) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768649 Title: [CVE] Access to privileged files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kwallet-pam/+bug/1768649/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768688] Re: Please remove unmaintained gtk2 themes
** Also affects: industrialtango-theme (Ubuntu) Importance: Undecided Status: New ** Also affects: human-netbook-theme (Ubuntu) Importance: Undecided Status: New ** Also affects: gray-theme (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/1768688 Title: Please remove unmaintained gtk2 themes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blubuntu-look/+bug/1768688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768995] Re: The "Unlock" button of user administration asks for wrong user
Adding to a sudo-enabled group is not enough? Since /etc/passwd and /etc/shadow do not have 'account type' fields, what does it mean to be an administrator? Belong to the admin group? adm? sudo? Why did gnome-control-center asked specifically for patola's password? What if there were two people with 'administrator' types? Should it instead ask for the root password then? [22:08] [7973] [patola@buzinskas patola]% id uid=1000(patola) gid=1000(patola) groups=1000(patola),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),116(lpadmin),126(sambashare),1001(procer3d) [22:08] [7974] [patola@buzinskas patola]% id razgriz uid=1002(razgriz) gid=1003(razgriz) groups=1003(razgriz),1001(procer3d) [22:08] [7975] [patola@buzinskas patola]% id felipe uid=1001(felipe) gid=1002(felipe) groups=1002(felipe),1001(procer3d) [22:08] [7976] [patola@buzinskas patola]% id ayrton uid=1003(ayrton) gid=1004(ayrton) groups=1004(ayrton),1001(procer3d) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768995 Title: The "Unlock" button of user administration asks for wrong user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1768995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769008] [NEW] package libhbaapi-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/include/hbaapi.h', which is also in package zfcp-hbaapi-dev 2.1.1-0ubuntu2
Public bug reported: apport wanted to submit this Occurred while installing the package ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libhbaapi-dev (not installed) ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu May 3 20:54:00 2018 DuplicateSignature: package:libhbaapi-dev:(not installed) Unpacking libhaapi-dev (2.2.1-0ubuntu3) ... dpkg: error processing archive /tmp/apt-dpkg-install-j8UzvA/7245-libhaapi-dev_2.2.1-0ubuntu3_amd64.deb (--unpack): trying to overwrite '/usr/include/hbaapi.h', which is also in package zfcp-hbaapi-dev 2.1.1-0ubuntu2 ErrorMessage: trying to overwrite '/usr/include/hbaapi.h', which is also in package zfcp-hbaapi-dev 2.1.1-0ubuntu2 InstallationDate: Installed on 2018-05-02 (1 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-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: libhbaapi Title: package libhbaapi-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/include/hbaapi.h', which is also in package zfcp-hbaapi-dev 2.1.1-0ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libhbaapi (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic need-duplicate-check package-conflict -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769008 Title: package libhbaapi-dev (not installed) failed to install/upgrade: trying to overwrite '/usr/include/hbaapi.h', which is also in package zfcp-hbaapi-dev 2.1.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libhbaapi/+bug/1769008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768830] Re: the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04
** Changed in: alsa-lib (Ubuntu) Assignee: (unassigned) => Hui Wang (hui.wang) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768830 Title: the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1768830/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768688] Re: Please remove unmaintained gtk2 themes
** Also affects: silicon-theme (Ubuntu) Importance: Undecided Status: New ** Also affects: outdoors-theme (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/1768688 Title: Please remove unmaintained gtk2 themes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/blubuntu-look/+bug/1768688/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752053] Re: nvidia-390 fails to boot graphical display
Same problem here with a Dell XPS 15 9560 after Kubuntu 17.10 -> 18.04 upgrade. Finally solved after lots of retries and reboots. I have now: Graphics Drivers PPA (https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa) - sudo add-apt-repository ppa:graphics-drivers/ppa - sudo apt update - sudo apt dist-upgrade Replaced manually nvidia 390 drivers by the newest 396 Purged nouveau package because I saw a "segmentation fault" log in /var/log/Xorg.0.log - sudo apt purge xserver-xorg-video-nouveau - sudo vi /etc/X11/xorg.conf -> uncomment line #Driver "nvidia" of Section "Device". So my xorg.conf file is exactly the same as the pasted in comment #77 without the last Section "Monitor". - sudo reboot After the reboot I see my previous sddm login screen instead of a tty and I can login normally :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1660574] Re: IPv4 Address Lost 8 Days After Previous DHCP Allocation
I had this issue yesterday on 17.10. The IPV4 address for my Ethernet interface vanished. I could not find any option in the network portion of settings to ask the DHCP for the IP address, and sudo service network-manager restart did not recover, so I rebooted the system. This is obviously an extremely rare situation and I do not know how to reproduce it. If there is no notification that the network manager can register for to detect this situation automatically then there should be a reinitialize button in the network settings GUI. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1660574 Title: IPv4 Address Lost 8 Days After Previous DHCP Allocation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1660574/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs