[Bug 1825195] Update Released
The verification of the Stable Release Update for libvirt has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825195 Title: qemu dropped osxsave/ospke feature triggering upgrade issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1825195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829244] Update Released
The verification of the Stable Release Update for gnome-shell-extension- desktop-icons has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829244 Title: [SRU] 19.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1829244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819129] Update Released
The verification of the Stable Release Update for ubuntu-report has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819129 Title: No CPU record on Virtualbox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/1819129/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825195] Re: qemu dropped osxsave/ospke feature triggering upgrade issues
This bug was fixed in the package libvirt - 5.0.0-1ubuntu2.2 --- libvirt (5.0.0-1ubuntu2.2) disco; urgency=medium * d/p/ubuntu/lp-1825195-*.patch: fix issues with old guests that defined the never functional osxsave and ospke features (LP: #1825195). -- Christian Ehrhardt Thu, 16 May 2019 10:42:09 +0200 ** Changed in: libvirt (Ubuntu Disco) Status: Fix Committed => Fix Released ** Changed in: libvirt (Ubuntu Disco) 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/1825195 Title: qemu dropped osxsave/ospke feature triggering upgrade issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1825195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825195] Re: qemu dropped osxsave/ospke feature triggering upgrade issues
This bug was fixed in the package libvirt - 5.0.0-1ubuntu2.2 --- libvirt (5.0.0-1ubuntu2.2) disco; urgency=medium * d/p/ubuntu/lp-1825195-*.patch: fix issues with old guests that defined the never functional osxsave and ospke features (LP: #1825195). -- Christian Ehrhardt Thu, 16 May 2019 10:42:09 +0200 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825195 Title: qemu dropped osxsave/ospke feature triggering upgrade issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1825195/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829244] Re: [SRU] 19.04.3
This bug was fixed in the package gnome-shell-extension-desktop-icons - 19.01.3-1~ubuntu19.04.1 --- gnome-shell-extension-desktop-icons (19.01.3-1~ubuntu19.04.1) disco; urgency=medium * Backport new upstream release from eoan to disco (LP: #1829244) - Fixes insecure commandline construction problem (LP: #1825396) gnome-shell-extension-desktop-icons (19.01.3-1) experimental; urgency=medium * New upstream release * Drop all patches, since they are included upstream -- Iain Lane Wed, 15 May 2019 15:13:51 +0100 ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Disco) 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/1829244 Title: [SRU] 19.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1829244/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825396] Update Released
The verification of the Stable Release Update for gnome-shell-extension- desktop-icons has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825396 Title: "Open in Terminal" returns "Text ended before matching quote was found for '" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1825396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831026] Re: package cups-browsed 1.8.3-2ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831026 Title: package cups-browsed 1.8.3-2ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1831026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831026] [NEW] package cups-browsed 1.8.3-2ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: steam crashed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-browsed 1.8.3-2ubuntu3.5 ProcVersionSignature: Ubuntu 4.15.0-50.54~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue May 28 23:22:14 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-07-28 (305 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: cups-filters Title: package cups-browsed 1.8.3-2ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cups-filters (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831026 Title: package cups-browsed 1.8.3-2ubuntu3.5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1831026/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1785778] Re: Hash Sum mismatch Ubuntu Server 18.04.1 LTS
Today I got same issue and @pujanm's suggestion is solved the problem. # apt-get update Get:1 http://archive.ubuntu.com/ubuntu bionic InRelease [242 kB] Get:2 http://security.ubuntu.com/ubuntu bionic-security InRelease [88,7 kB] Get:3 https://repo.skype.com/deb stable InRelease [4.487 B] Ign:4 http://dl.google.com/linux/chrome/deb stable InRelease Get:5 http://archive.canonical.com/ubuntu bionic InRelease [10,2 kB] Ign:6 http://repo.vivaldi.com/stable/deb stable InRelease Get:7 http://dl.google.com/linux/chrome/deb stable Release [943 B] Get:8 http://repo.vivaldi.com/stable/deb stable Release [3.831 B] Get:9 http://repo.vivaldi.com/stable/deb stable Release.gpg [833 B] Get:10 http://archive.canonical.com/ubuntu bionic/partner amd64 Packages [2.320 B] Get:11 http://dl.google.com/linux/chrome/deb stable Release.gpg [819 B] Get:12 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88,7 kB] Ign:13 http://packages.linuxmint.com tessa InRelease Get:14 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages [265 kB] Get:15 http://archive.canonical.com/ubuntu bionic/partner i386 Packages [2.320 B] Get:16 http://archive.canonical.com/ubuntu bionic/partner Translation-en [1.276 B] Get:17 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74,6 kB] Get:18 https://repo.skype.com/deb stable/main amd64 Packages [2.274 B] Get:19 http://repo.vivaldi.com/stable/deb stable/main i386 Packages [1.193 B] Get:20 http://packages.linuxmint.com tessa Release [24,1 kB] Get:21 http://archive.ubuntu.com/ubuntu bionic/main i386 Packages [1.007 kB] Ign:22 https://artifacts.elastic.co/packages/7.x/apt stable InRelease Get:23 http://repo.vivaldi.com/stable/deb stable/main amd64 Packages [1.197 B]
[Bug 1826629] Update Released
The verification of the Stable Release Update for deepin-qt5dxcb-plugin has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826629 Title: deepin-screenshot: can't find dxcb Qt plugin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deepin-qt5dxcb-plugin/+bug/1826629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826629] Re: deepin-screenshot: can't find dxcb Qt plugin
This bug was fixed in the package deepin-qt5dxcb-plugin - 1.1.22-1ubuntu1.1 --- deepin-qt5dxcb-plugin (1.1.22-1ubuntu1.1) disco; urgency=medium * Rebuild against qtbase ≥ 5.12.2+dfsg-4 (LP: #1826629). * Build-depend on libxcb-xinput-dev to fix build failure. -- Dmitry Shachnev Sun, 19 May 2019 18:14:38 +0300 ** Changed in: deepin-qt5dxcb-plugin (Ubuntu Disco) 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/1826629 Title: deepin-screenshot: can't find dxcb Qt plugin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/deepin-qt5dxcb-plugin/+bug/1826629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831025] Re: apt update fails with ` 404 Not Found [IP: 91.189.95.83 80]`. Possible cause: three dots in the sources.list
Dear Adam, the log you provided does not seem to indicate an issue with acquiring data from http://ppa.launchpad.net/jtaylor/keepass/ubuntu but from http://ppa.launchpad.net/daniel.pavel/solaar/ubuntu - a PPA which does not support your Ubuntu release (18.04 / bionic). So this appears to not be a bug, just use of an incompatible PPA, making this more of a support request. I'm therefore changing the status to "invalid" - should I have missed relevant facts you are welcome to undo this change. Should you need further support with this, please consider one of the following options: https://www.ubuntu.com/support https://www.ubuntu.com/support/community-support Thanks, Tom -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831025 Title: apt update fails with ` 404 Not Found [IP: 91.189.95.83 80]`. Possible cause: three dots in the sources.list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1831025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831025] Re: apt update fails with ` 404 Not Found [IP: 91.189.95.83 80]`. Possible cause: three dots in the sources.list
That's the wrong source, please read the error message carefully - the solaar ppa for which the error occurs does not provide any bionic packages. ** Changed in: apt (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831025 Title: apt update fails with ` 404 Not Found [IP: 91.189.95.83 80]`. Possible cause: three dots in the sources.list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1831025/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830941] Re: linux: 4.4.0-150.176 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830941 Title: linux: 4.4.0-150.176 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1830941/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824743] Re: Fonts look bad after scaling display in Kubuntu Disco
Hi Nathan, thanks for the bug report. This is currently a known issue with non-integer scaling factors in KDE [1]. There's unfortunately no big fix for everyone yet, just small fixes that work for some and not for others. Keep up-to-date with KDE updates and it's likely the issue will eventually go away (as it seems to have for some people [2]). If you don't mind, it may a good idea to log this particular bug upstream with KDE [3]. Once reported, please share the link here on this bug. Thank you! [1] https://wiki.archlinux.org/index.php/HiDPI#KDE (There's a suggested workaround here too) [2] https://www.reddit.com/r/kde/comments/bpqbr9/noninteger_scaling_factors_not_buggy_anymore/?ref=readnext [3] https://community.kde.org/Get_Involved/Bug_Reporting -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824743 Title: Fonts look bad after scaling display in Kubuntu Disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1824743/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822133] Re: Azure Instance never recovered during series of instance reboots.
I see now 5.0.0-1007.7 is also available for 19.04, but I'll wait and see what you advise @Dexuan after looking at my serial log. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822133 Title: Azure Instance never recovered during series of instance reboots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831025] [NEW] apt update fails with ` 404 Not Found [IP: 91.189.95.83 80]`. Possible cause: three dots in the sources.list
Public bug reported: The following file siteated in /etc/apt/sources.d/jtaylor-ubuntu- keepass-bionic.list: deb http://ppa.launchpad.net/jtaylor/keepass/ubuntu bionic main causes sudo apt update to fail for this entry with the error: 404 Not Found [IP: 91.189.95.83 80] Full transcript: $ sudo apt update Hit:1 http://deb.playonlinux.com bionic InRelease Hit:2 http://pl.archive.ubuntu.com/ubuntu bionic InRelease Hit:3 http://ppa.launchpad.net/bookworm-team/bookworm/ubuntu bionic InRelease Hit:4 http://pl.archive.ubuntu.com/ubuntu bionic-updates InRelease Ign:5 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 InRelease Hit:6 http://pl.archive.ubuntu.com/ubuntu bionic-backports InRelease Hit:7 http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 Release Hit:8 http://cran.rstudio.com/bin/linux/ubuntu bionic-cran35/ InRelease Hit:9 http://pl.archive.ubuntu.com/ubuntu bionic-proposed InRelease Ign:10 http://ppa.launchpad.net/daniel.pavel/solaar/ubuntu bionic InRelease Hit:11 https://repo.skype.com/deb stable InRelease Hit:12 http://ppa.launchpad.net/elementary-os/stable/ubuntu bionic InRelease Hit:13 http://ppa.launchpad.net/fixnix/netspeed/ubuntu bionic InRelease Hit:14 http://dl.winehq.org/wine-builds/ubuntu bionic InRelease Hit:15 http://ppa.launchpad.net/graphics-drivers/ppa/ubuntu bionic InRelease Hit:16 http://ppa.launchpad.net/jtaylor/keepass/ubuntu bionic InRelease Hit:18 http://ppa.launchpad.net/noobslab/themes/ubuntu bionic InRelease Hit:20 http://ppa.launchpad.net/team-xbmc/ppa/ubuntu bionic InRelease Hit:21 http://ppa.launchpad.net/unity7maintainers/unity7-desktop/ubuntu bionic InRelease Hit:22 http://ppa.launchpad.net/yktooo/ppa/ubuntu bionic InRelease Err:23 http://ppa.launchpad.net/daniel.pavel/solaar/ubuntu bionic Release 404 Not Found [IP: 91.189.95.83 80] Ign:17 https://attic.owncloud.com/org/download/repositories/10.0/Ubuntu_18.04 InRelease Hit:24 http://download.owncloud.org/download/repositories/10.0/Ubuntu_18.04 Release Hit:26 http://security.ubuntu.com/ubuntu bionic-security InRelease Reading package lists... Done E: The repository 'http://ppa.launchpad.net/daniel.pavel/solaar/ubuntu bionic Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details. Possible cause: three dots in the source confused the parser and it improperly handles TCP port. Please note, that when I connect through acng with Acquire::http::Proxy "http://192.168.10.2:3142;; the error turns into ` 404 Not Found [IP: 192.168.10.2 3142]`. Further info: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic $ uname -a Linux n56vz-bionic
[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
** Description changed: + [Impact] + + The documentation allows the following types of arguments for the PreserveJobHistory parameter: + PreserveJobHistory Yes + PreserveJobHistory No + PreserveJobHistory seconds + + The value in seconds is treated in the same as 'No' resulting in immediate removing of jobs from history, while it is supposed to save it for . + + [Test Case] + + * Set PreserveJobHistory to 300. + * Schedule a job for printing. + * Check the error_log. + + Expected result: + Job is save for at least 300 seconds. + + Actual results: + Job is immediately removed from history. + + [Regression Potential] + + * With the fix the jobs will be saved longer than before, so in tight + conditions (low disk space) and heavy workload it may affect memory/disk + space consumption and lead to running out of free space in worst case. + + [Other Info] + + * Original bug description: + 1) Ubuntu Release Description: Ubuntu 16.04.3 LTS Release: 16.04 2) Version of the package cups: - Installed: 2.1.3-4ubuntu0.3 - Candidate: 2.1.3-4ubuntu0.3 - Version table: - *** 2.1.3-4ubuntu0.3 500 - 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages + Installed: 2.1.3-4ubuntu0.3 + Candidate: 2.1.3-4ubuntu0.3 + Version table: + *** 2.1.3-4ubuntu0.3 500 + 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 3) What I expected to happen: from man cupsd.conf - PreserveJobFiles Yes + PreserveJobFiles Yes -PreserveJobFiles No + PreserveJobFiles No -PreserveJobFiles seconds - Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved - for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). + PreserveJobFiles seconds + Specifies whether job files (documents) are preserved after a job is printed. If a numeric value is specified, job files are preserved + for the indicated number of seconds after printing. The default is "86400" (preserve 1 day). -PreserveJobHistory Yes + PreserveJobHistory Yes -PreserveJobHistory No + PreserveJobHistory No -PreserveJobHistory seconds - Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for - the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default - is "Yes". + PreserveJobHistory seconds + Specifies whether the job history is preserved after a job is printed. If a numeric value is specified, the job history is preserved for + the indicated number of seconds after printing. If "Yes", the job history is preserved until the MaxJobs limit is reached. The default + is "Yes". 4) What happens instead If I put the following directives in cupsd.conf the job files and history are deleted immediately. PreserveJobFiles 604800 PreserveJobHistory 604800 - Debug log showing history being purged: d [06/Feb/2018:15:11:59 -0600] cupsdCheckJobs: 0 active jobs, sleeping=0, ac-power=-1, reload=0, curtime=1517951519 d [06/Feb/2018:15:11:59 -0600] cupsdCleanJobs: MaxJobs=100, JobHistory=604800, JobFiles=604800 D [06/Feb/2018:15:11:59 -0600] [Job 106] Removing from history. D [06/Feb/2018:15:11:59 -0600] [Job 106] Unloading... ** Changed in: cups (Ubuntu) Importance: Undecided => Medium ** Also affects: cups (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: cups (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: cups (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830629] Re: Errors when extracting ZIP files. It can not differentiate between files and directories
Thanks for reporting this issue - this would appear to have potential security implications, however as it is already public I see no reason to keep this private - if a CVE were to be assigned then this could be fixed via a security update by the security team, otherwise this would be fixed via the normal SRU process[1]. As such, please feel free to file a CVE request with MITRE[2] and if one is assigned, please update this bug report with the CVE ID and we can fix it via the security team. [1] https://wiki.ubuntu.com/StableReleaseUpdates [2] https://cve.mitre.org/cve/request_id.html ** Information type changed from Private Security to Public Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830629 Title: Errors when extracting ZIP files. It can not differentiate between files and directories To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1830629/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822133] Re: Azure Instance never recovered during series of instance reboots.
I got the VM back by force stopping, then starting. It looks like 5.0.0-1007.7 only comes with 19.10, which is not available yet on Azure? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822133 Title: Azure Instance never recovered during series of instance reboots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
This has been fixed in 19.10 for cups 2.2.10-6 (backport from upstream). ** Changed in: cups (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/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747765] Re: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747765 Title: PreserveJobHistory and PreserveJobLog do not respect numeric input as outlined in the docs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1747765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1830582] Re: nvidia-384 384.130-0ubuntu0.16.04.2: nvidia-384 kernel module failed to build [arch/x86/Makefile:245: *** You are building kernel with non-retpoline compiler, please update your
On Wed, May 29, 2019 at 7:15 PM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > We tell build failure bugs apart according to their error messages. So > the error message should go in the title. > > In this case it suggests you have an unusual C compiler installed as the > default compiler. Can you check what this command tells you? > > cc --version > zot (1): which cc /usr/bin/cc zot (2): cc --version cc (Ubuntu 7.4.0-1ubuntu1~18.04) 7.4.0 Copyright (C) 2017 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. zot (3): lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.2 LTS Release: 18.04 Codename: bionic It is a stock 18.04 installation. I didn't build the kernel. > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1830582 > > Title: > nvidia-384 384.130-0ubuntu0.16.04.2: nvidia-384 kernel module failed > to build [arch/x86/Makefile:245: *** You are building kernel with non- > retpoline compiler, please update your compiler.. Stop.] > > Status in nvidia-graphics-drivers-384 package in Ubuntu: > New > > Bug description: > not sure what tickled it. > > ProblemType: Package > DistroRelease: Ubuntu 16.04 > Package: nvidia-384 384.130-0ubuntu0.16.04.2 > ProcVersionSignature: Ubuntu 4.15.0-47.50~16.04.1-generic 4.15.18 > Uname: Linux 4.15.0-47-generic x86_64 > NonfreeKernelModules: nvidia_uvm wl nvidia_drm nvidia_modeset nvidia > ApportVersion: 2.20.1-0ubuntu2.18 > Architecture: amd64 > DKMSKernelVersion: 4.15.0-50-generic > Date: Sun May 26 22:48:29 2019 > InstallationDate: Installed on 2017-09-29 (604 days ago) > InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 > (20170801) > PackageVersion: 384.130-0ubuntu0.16.04.2 > RelatedPackageVersions: >dpkg 1.18.4ubuntu1.5 >apt 1.2.31 > SourcePackage: nvidia-graphics-drivers-384 > Title: nvidia-384 384.130-0ubuntu0.16.04.2: nvidia-384 kernel module > failed to build > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1830582/+subscriptions > -- Eric B. Decker Senior (over 50 :-) Researcher -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830582 Title: nvidia-384 384.130-0ubuntu0.16.04.2: nvidia-384 kernel module failed to build [arch/x86/Makefile:245: *** You are building kernel with non- retpoline compiler, please update your compiler.. Stop.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1830582/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831020] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831020 Title: BTRS Raid boot failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830711] Re: Include Upstream commit fixing mac address change issue in bond (and bridged) interfaces
** Description changed: + When an interface is added to a bond interface, if it is the first + interface added, the MAC address of the bond interface is changed + to the MAC address of the added interface. When subsequent interfaces + are added, their MAC addresses are changed to that of the bond + interface. + + Issue #1112 identified that if a bond interface is deleted and + recreated, the gratuitous ARPs were sent with the wrong source MAC + address. + + Upstream commit [0] updates interface MAC addresses from the + netlink RTM_NEWLINK messages, so that the correct MAC address + is always used. + + [0] + https://github.com/acassen/keepalived/commit/322679cd8d74f5992a10c842e867d427a083ef6a + + + = Original description = + As explained in the upstream bug report: https://github.com/acassen/keepalived/issues/1112 please include the fix of the commit to ubuntu LTS: https://github.com/acassen/keepalived/commit/322679cd8d74f5992a10c842e867d427a083ef6a ** Description changed: When an interface is added to a bond interface, if it is the first interface added, the MAC address of the bond interface is changed to the MAC address of the added interface. When subsequent interfaces are added, their MAC addresses are changed to that of the bond interface. - Issue #1112 identified that if a bond interface is deleted and + Uptream issue [0] identified that if a bond interface is deleted and recreated, the gratuitous ARPs were sent with the wrong source MAC address. - Upstream commit [0] updates interface MAC addresses from the + Upstream commit [1] updates interface MAC addresses from the netlink RTM_NEWLINK messages, so that the correct MAC address is always used. - [0] - https://github.com/acassen/keepalived/commit/322679cd8d74f5992a10c842e867d427a083ef6a - + [0] https://github.com/acassen/keepalived/issues/1112 + [1] https://github.com/acassen/keepalived/commit/322679cd8d74f5992a10c842e867d427a083ef6a = Original description = As explained in the upstream bug report: https://github.com/acassen/keepalived/issues/1112 please include the fix of the commit to ubuntu LTS: https://github.com/acassen/keepalived/commit/322679cd8d74f5992a10c842e867d427a083ef6a ** Also affects: keepalived (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: keepalived (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: keepalived (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: keepalived (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: keepalived (Ubuntu Xenial) Status: New => Triaged ** Changed in: keepalived (Ubuntu Bionic) Status: New => Triaged ** Changed in: keepalived (Ubuntu Disco) Status: New => Triaged ** Changed in: keepalived (Ubuntu Eoan) Status: New => Triaged ** Summary changed: - Include Upstream commit fixing mac address change issue in bond (and bridged) interfaces + If a bond interface is deleted and recreated, the gratuitous ARPs are sent with the wrong MAC address ** Tags added: server-triage-discuss -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1830711 Title: If a bond interface is deleted and recreated, the gratuitous ARPs are sent with the wrong MAC address To manage notifications about this bug go to: https://bugs.launchpad.net/keepalived/+bug/1830711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831021] Re: Extremely high memory consumption under heavy workload
After some analysis I believe the very high default value of LogDebugHistory (9) is to blame for this (attaching massif report from the test case). With a high number of jobs it's very easy to get hunderds-thousands of messages in LogDebugHistory which in turn will lead to enormous memory consumption, e.g. 4 jobs * 2000 lines * (16 bytes for cupsd_joblog_t structure + 50-60 chars per message on average) - 5.66 GB. After setting LogDebugHistory to 0 the memory consumption never exceeded 300 MB in my tests under the same heavy load. That's a very significant difference. The possible workarounds: 1. Decrease LogDebugHistory to a low value (even to 0, upstream it's set to 200 by default). 2. Change LogLevel to debug (it will slow down cupsd operation significantly, but at the price of lower memory consumption as the LogDebugHistory is unused). 3. Make sure jobs are cleaned periodically by setting e.g. PreserveJobHistory 300. I am wondering what was the rationale behind increasing LogDebugHistory to such a high value. ** Attachment added: "massif.out.xz" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1831021/+attachment/5267574/+files/massif.out.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831021 Title: Extremely high memory consumption under heavy workload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1831021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831021] [NEW] Extremely high memory consumption under heavy workload
Public bug reported: Under heavy workload conditions cups can reach irrationally high memory consumption very quickly (tens of GBs). Test case: 1. Set MaxJobs to 4 in cupsd.conf. 2. sudo apt install cups-pdf 3. Fill the queue with jobs: while [ 1 ]; lp -d PDF /usr/share/cups/data/default.pdf; done 4. Cancel all jobs cancel -a PDF 5. Restart cups. 6. Start filling the queue again (as in step 3). Expected result: Jobs are processed and memory consumption is proportional to the number of jobs. Actual result: After step 5 or at latest step 6 memory consumption starts to increase exponentially - from ~150-200 MB to 8+GB. Without foreseeing this it's very easy to get cups killed by OOM killer. ** Affects: cups (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/1831021 Title: Extremely high memory consumption under heavy workload To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1831021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831020] [NEW] BTRS Raid boot failure
Public bug reported: After upgrading from Ubuntu 18.10 to 19.04 my BTRFS Raid0 based system doesn't boot anymore. It drops to busybox because of an error mounting the root file system. Manually trying to mount root reveals an error message saying that the second raid volume could not be found by UUID. But the output from `blkid` shows that the volume with the UUID in question exists. Booting the system using the previous kernel 4.18 from advanced boot options works flawlessly. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-generic 5.0.0.15.16 ProcVersionSignature: Ubuntu 4.18.0-20.21-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pwuertz1702 F pulseaudio Date: Thu May 30 09:03:47 2019 HibernationDevice: RESUME=UUID=d477a5f5-0176-4b8a-937a-b97db8fef8d4 InstallationDate: Installed on 2016-04-28 (1126 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Sony Corporation VPCZ21C5E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-20-generic root=UUID=aa8fbe5e-c722-43e9-b8fc-9d7f60818a46 ro rootflags=subvol=@ quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-20-generic N/A linux-backports-modules-4.18.0-20-generic N/A linux-firmware 1.178.1 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-05-30 (0 days ago) dmi.bios.date: 06/16/2011 dmi.bios.vendor: INSYDE dmi.bios.version: R0170H5 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnINSYDE:bvrR0170H5:bd06/16/2011:svnSonyCorporation:pnVPCZ21C5E:pvrJ004QCLG:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: VAIO dmi.product.name: VPCZ21C5E dmi.product.sku: N/A dmi.product.version: J004QCLG dmi.sys.vendor: Sony Corporation ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831020 Title: BTRS Raid boot failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831020/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1830909] Re: package mysql-server-5.7 5.7.26-0ubuntu0.16.04.1 failed to install/upgrade: il sottoprocesso installato script di post-installation ha restituito lo stato di errore 1
Thank you for your report. The mysql log (Logs.var.log.mysql.error.log.txt) shows that mysqld was failing to start even before the upgrade, e.g.: 190529 15:55:01 [Note] Server hostname (bind-address): '192.168.4.153'; port: 3306 190529 15:55:01 [Note] - '192.168.4.153' resolves to '192.168.4.153'; 190529 15:55:01 [Note] Server socket created on IP: '192.168.4.153'. 190529 15:55:01 [ERROR] Can't start server: Bind on TCP/IP port: Cannot assign requested address 190529 15:55:01 [ERROR] Do you already have another mysqld server running on port: 3306 ? 190529 15:55:01 [ERROR] Aborting Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete. If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community- Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. ** Changed in: mysql-5.7 (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/1830909 Title: package mysql-server-5.7 5.7.26-0ubuntu0.16.04.1 failed to install/upgrade: il sottoprocesso installato script di post- installation ha restituito lo stato di errore 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1830909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824111] Re: Backport packages for 18.04.3 HWE stack
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824111 Title: Backport packages for 18.04.3 HWE stack To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1824111/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822133] Re: Azure Instance never recovered during series of instance reboots.
How do I upgrade the kernel to 5.0.0-1007.7 if that is what is recommended to avoid this issue? apt-get dist-upgrade on another vm with 4.18.0-1018-azure did not upgrade the kernel. Thank God it restarted! Or is 5.0.0-1007.7 not an Azure kernel so I would need to switch to stock Ubuntu kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822133 Title: Azure Instance never recovered during series of instance reboots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822133] Re: Azure Instance never recovered during series of instance reboots.
@Dexuan I emailed you my serial log. I restarted via portal a number of times without success. I tried to redeploy twice and it failed. Trying to restart via cli now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822133 Title: Azure Instance never recovered during series of instance reboots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783499] Re: systemd: Failed to send signal
I have found that if I set the reboot once at 15 min, the server works for 5-6 days. If the reboots are done once at 10 min, the server get stuck in 24-48h max. Now I'm testing the reboots once at 20min, it should take 10 days or more until is stuck. Also, I have tried all "reboot=" grub options, nothing helps. The only way to keep he server online is to set the reboot time less often. Odd! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783499 Title: systemd: Failed to send signal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1783499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822133] Re: Azure Instance never recovered during series of instance reboots.
@Kirk: I suppose you can get your VM back by Restarting the VM by force via Azure Portal (or Azure cmd line)? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822133 Title: Azure Instance never recovered during series of instance reboots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1829306] Re: ethtool identify command doesn't blink LED on Hi1620 NICs
** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1829306 Title: ethtool identify command doesn't blink LED on Hi1620 NICs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822133] Re: Azure Instance never recovered during series of instance reboots.
@Kirk: Can you please share the VM's serial log, which can be obtained from Azure portal's Boot Diagnostics -> Serial log? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822133 Title: Azure Instance never recovered during series of instance reboots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822133] Re: Azure Instance never recovered during series of instance reboots.
kernel is 4.18.0-1018-azure -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822133 Title: Azure Instance never recovered during series of instance reboots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1822133/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
