[Bug 1814896] Re: upgrade Docker snap to 18.09.1
** Changed in: docker (Ubuntu) Assignee: (unassigned) => Ian Johnson (anonymouse67) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814896 Title: upgrade Docker snap to 18.09.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/docker/+bug/1814896/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823410] [NEW] utils.py's url_downloadable doesn't support https
Public bug reported: In the interest of improving release upgrades for users of PPAs a check was added to ubuntu-release-upgrader to see if the release to which the system is being upgraded is provided by a sources list entry and if it is not that entry is disabled. This check uses the function url_downloadable which is provided by update-manager's utils.py. Come to find out the url_downloadable check only supports ftp and http, not https. This can cause a situation where upgrades to the next release of Ubuntu fail if the system's mirror of the Ubuntu archive is using https. This is mentioned here - https://bugs.launchpad.net/ubuntu/+source /ubuntu-release-upgrader/+bug/1807043/comments/10. While the bug manifests itself in ubuntu-release-upgrader it needs fixing in update-manager. ** Affects: update-manager (Ubuntu) Importance: High Status: Triaged ** Changed in: update-manager (Ubuntu) Importance: Undecided => High ** Changed in: update-manager (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/1823410 Title: utils.py's url_downloadable doesn't support https To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1823410/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822820] Re: linux: 4.15.0-48.51 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822817 (xenial/linux-azure), bug 1822819 (xenial/linux-hwe) derivatives: bug 1822802 (linux-raspi2), bug 1822803 (linux-oem), bug 1822805 (linux-aws), bug 1822808 (linux-gcp), bug 1822809 (linux-kvm), bug 1822810 (linux-ibm-gt), bug 1822812 (linux-oracle), bug 1822813 (linux-fips), bug 1822981 (linux), bug 1823254 (linux) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Thursday, 04. April 2019 18:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: 'Pending -- snap pc-kernel not in expected channel(s): i386:18/beta - amd64:18/beta armhf:18/beta' + armhf:18/beta amd64:18/beta' snap-release-to-edge: 'Pending -- snap pc-kernel not in expected channel(s): i386:18/edge - amd64:18/edge armhf:18/edge' + armhf:18/edge amd64:18/edge' verification-testing: Ongoing -- testing 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/1822820 Title: linux: 4.15.0-48.51 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1714264] Re: mtpaint's desktop file uses URL instead of file when opening
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mtpaint (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/1714264 Title: mtpaint's desktop file uses URL instead of file when opening To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtpaint/+bug/1714264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821034] Re: release-upgrade-motd can't update message
While you've identified a legitimate bug, the lack of https support, in url_downloadable that function isn't actually used to get the meta- release file. (Wacky I know!) This can be seen by reading UpdateManager/Core/MetaRelease.py's download function. Please try running do-release-upgrade with the DEBUG_UPDATE_MANAGER environmental variable set e.g. DEBUG_UPDATE_MANAGER=1 do-release- upgrade -c. Thanks again for your help! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821034 Title: release-upgrade-motd can't update message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1821034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 277281] Re: pptp does not start automatically in Intrepid
Setting WONTFIX as requested. ** Changed in: pptp-linux (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/277281 Title: pptp does not start automatically in Intrepid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/knetworkmanager/+bug/277281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 277281] Re: pptp does not start automatically in Intrepid
This bug is still Undecided in the pptp-linux project, however, the comment above says the bug will not be fixed but another applet is available in KDE4 for Kubuntu 9.10. Please set to "Won't Fix" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/277281 Title: pptp does not start automatically in Intrepid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/knetworkmanager/+bug/277281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS
needs a test case for libnet-ssleay-perl. ** Also affects: libnet-ssleay-perl (Ubuntu) Importance: Undecided Status: New ** No longer affects: libnet-ssleay-perl (Ubuntu) ** Changed in: libnet-ssleay-perl (Ubuntu Bionic) 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/1797386 Title: [SRU] OpenSSL 1.1.1 to 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1797386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823405] Re: baobab crashed with SIGSEGV in gtk_tree_model_get_valist()
** Description changed: + [Impact] + By opening the 'baobab' program and choosing to set up a u...@gmail.com basin, and then setting up the gmail account. And I hit a click to open a folder of u...@gmail.com crashes 'baobab'. + + [Test Case] + 1. Open baobab + 2. Mount u...@gmail.com + 3. Wait for the content of the account u...@gmail.com to be displayed in baobab + 3. Select a folder of the account u...@gmail.com + 4. Click on it to display the options in that folder + 5. Select 'Open Folder' + 6. baobab crashes + + Original Description + Opening a folder in baobab with connection to google drive. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: baobab 3.32.0-1 Uname: Linux 5.0.6-050006-generic x86_64 ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 5 17:40:41 2019 ExecutablePath: /usr/bin/baobab InstallationDate: Installed on 2018-12-02 (124 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/baobab --gapplication-service ProcEnviron: - SHELL=/bin/bash - XDG_RUNTIME_DIR= - PATH=(custom, no user) - LANGUAGE=es_CL:es - LANG=es_CL.UTF-8 + SHELL=/bin/bash + XDG_RUNTIME_DIR= + PATH=(custom, no user) + LANGUAGE=es_CL:es + LANG=es_CL.UTF-8 SegvAnalysis: - Segfault happened at: 0x7f57537d00ee : mov0x30(%rax),%rdi - PC (0x7f57537d00ee) ok - source "0x30(%rax)" (0x0030) not located in a known VMA region (needed readable region)! - destination "%rdi" ok + Segfault happened at: 0x7f57537d00ee : mov0x30(%rax),%rdi + PC (0x7f57537d00ee) ok + source "0x30(%rax)" (0x0030) not located in a known VMA region (needed readable region)! + destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: baobab StacktraceTop: - gtk_tree_model_get_valist () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 - gtk_tree_model_get () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 - baobab_window_open_item () - ?? () - g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 + gtk_tree_model_get_valist () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 + gtk_tree_model_get () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 + baobab_window_open_item () + ?? () + g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: baobab crashed with SIGSEGV in gtk_tree_model_get_valist() UpgradeStatus: Upgraded to disco on 2018-12-02 (124 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Information type changed from Private to Public ** Description changed: + https://gitlab.gnome.org/GNOME/baobab/issues/20 + + --- + [Impact] By opening the 'baobab' program and choosing to set up a u...@gmail.com basin, and then setting up the gmail account. And I hit a click to open a folder of u...@gmail.com crashes 'baobab'. [Test Case] 1. Open baobab 2. Mount u...@gmail.com 3. Wait for the content of the account u...@gmail.com to be displayed in baobab 3. Select a folder of the account u...@gmail.com 4. Click on it to display the options in that folder 5. Select 'Open Folder' 6. baobab crashes Original Description Opening a folder in baobab with connection to google drive. ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: baobab 3.32.0-1 Uname: Linux 5.0.6-050006-generic x86_64 ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 5 17:40:41 2019 ExecutablePath: /usr/bin/baobab InstallationDate: Installed on 2018-12-02 (124 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/baobab --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 SegvAnalysis: Segfault happened at: 0x7f57537d00ee : mov0x30(%rax),%rdi PC (0x7f57537d00ee) ok source "0x30(%rax)" (0x0030) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: baobab StacktraceTop: gtk_tree_model_get_valist () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_tree_model_get () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 baobab_window_open_item () ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: baobab crashed with SIGSEGV in gtk_tree_model_get_valist() UpgradeStatus: Upgraded to disco on 2018-12-02 (124 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: ** Description changed: https://gitlab.gnome.org/GNOME/baobab/issues/20 --- [Impact] - By opening the 'baobab' program and choosing to set up a u...@gmail.com basin, and then setting up the gmail account. And I hit a click to open a folder of
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
+1. Purged snap until it's fixed! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 277281] Re: pptp not start automatically in Intrepid
** Summary changed: - pptp not starts sutomatically in Intrepid + pptp not start automatically in Intrepid ** Summary changed: - pptp not start automatically in Intrepid + pptp does not start automatically in Intrepid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/277281 Title: pptp does not start automatically in Intrepid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/knetworkmanager/+bug/277281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821760] Re: CVE-2019-9917 - Invalid encoding crash
** Changed in: znc (Ubuntu Disco) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821760 Title: CVE-2019-9917 - Invalid encoding crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/znc/+bug/1821760/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768352] Proposed package upload rejected
An upload of mate-screensaver to bionic-proposed has been rejected from the upload queue for the following reason: "rejected due to lack of adequate SRU test case as requested on the bug". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768352 Title: mate-screensaver screen lock can be bypassed by power cycling monitor To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1768352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821034] Re: release-upgrade-motd can't update message
** Changed in: update-manager (Ubuntu) Status: Triaged => Incomplete ** Changed in: update-manager (Ubuntu) Importance: High => Undecided -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821034 Title: release-upgrade-motd can't update message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1821034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822616] Re: [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_screen_size
Can you please test packages from this PPA [1] and see if the issue is fixed for you? If not I can be even more conservative in the checks :) [1] https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3695 ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: budgie-desktop (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822616 Title: [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_screen_size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1822616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1784224] Re: gvedit executable is not included in graphviz package
Still a problem for all releases including upcoming 19.04 - see https://packages.ubuntu.com/search?suite=disco=any=exactfilename=contents=gvedit . But the package may be successfully compiled manually using my method - https://askubuntu.com/q/1060516/66509 . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1784224 Title: gvedit executable is not included in graphviz package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/graphviz/+bug/1784224/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821034] Re: release-upgrade-motd can't update message
** Changed in: update-manager (Ubuntu) Status: Incomplete => Triaged ** Changed in: update-manager (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821034 Title: release-upgrade-motd can't update message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1821034/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823407] [NEW] net and ftrace selftests failures due to missing test modules
Public bug reported: SRU Justification Impact: The test_bpf net selftest and a couple of ftrace selftests are failing due to missing modules. These modules are only for test purposes and have no other use, so they are not wanted in the linux-modules package. Fix: Change the tests to treat the missing modules as skipped tests rather than failures. Regression Potential: Minimal, since the changes are only to test cases which are already failing. Test Case: Run the test cases with the patch applied and observe that they behave as skipped tests rather than failures. ** Affects: linux-aws (Ubuntu) Importance: High Assignee: Seth Forshee (sforshee) Status: In Progress ** Description changed: SRU Justification Impact: The test_bpf net selftest and a couple of ftrace selftests are failing due to missing modules. These modules are only for test purposes and have no other use, so they are not wanted in the linux-modules package. Fix: Change the tests to treat the missing modules as skipped tests rather than failures. Regression Potential: Minimal, since the changes are only to test cases which are already failing. + + Test Case: Run the test cases with the patch applied and observe that + they behave as skipped tests rather than failures. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823407 Title: net and ftrace selftests failures due to missing test modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1823407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748943] Re: Gnome-Terminal Giant terminal icon is blocking out the Terminal window buttons
*** This bug is a duplicate of bug 1718238 *** https://bugs.launchpad.net/bugs/1718238 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-terminal (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/1748943 Title: Gnome-Terminal Giant terminal icon is blocking out the Terminal window buttons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1748943/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776563]
That is not clear if their bios should meet the standards or not. It's also not clear if we should accept that they support Win10 only. I don't really know. Maybe this is something which is relate to this. What do you think? https://github.com/torvalds/linux/commit/8aafaaf2212192012f5bae305bb31cdf7681d777 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776563]
Market share cannot be an excuse in this case, i've read myriad reviews about lenovo-hp-asus laptops that either worked out of the box with linux, or had a quick bios fix that resolved the issue, acer is just sloppy and lazy.They dont have to support linux directly, but at the very least they could make their bios iasl compliant in order to work with the acpi spec. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776563]
Kung Lao, the market share of Linux desktop is very low so supporting it hasn't got high priority, unfortunately. However the manufacturers should be more flexible because of the future opportunities. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776563]
Hi Adam, Thanks for your answer. We are waiting the patches. Best Regards Richard Yang, Adam <*> 2019. 04. 05., P, 17:04 Hi all, We're still currently verifying the patches (not one patch but a lot) so please be patient and be careful about your upgrades from old working kernel (which we are so sorry for the inconvenience). I'll comment and change status about related issues if the patches are merged and *released* as upgrades. Thanks for your patience. -- Software Engineer, MLSE AMD, Advanced Micro Devices Phone: * Adam Yang From: boun...@canonical.com on behalf of Richard Baka <*> Sent: Saturday, April 6, 2019 12:52:52 AM To: Yang, Adam Subject: Acer notebook firmware issue Dear Adam, Regarding this bug: https://bugs.launchpad.net/bugs/1776563 I would like to ask you where/how will the released fix be appeared. Is there any kernel commit or we should wait for the manufacturer's reaction? Thanks, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776563]
Yea, well said, i spent 400 euros for this acer laptop and it came with linux pre-installed(as an average consumer i thought that this meant linux is supported out of the box), at least they try to fix the issue, but already a year has passed and the results from many bios updates are mixed.If anyone considers buying an acer laptop in the future and want to run linux, isuggest read a review first before buying, because things like these can get really frustrating. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776563]
Siya market share defines the percentage of workers that get assigned to each problem. So even though Richard is correct that fewer people use Linux on their Acer laptop it still is false-advertising to sell Acer laptop with linux preinstalled when the only thing that boots is their ancient and ultra rare distro. I also noticed from what someone mentioned above that fixes start from flagship models and find their way to the lowest tier. We are probably lucky that same components and BIOS were used with expensive models. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776563]
Thanks for the informative paste Richard, sorry for my frustration but for most of us the waranty of the laptop is almost expired and the issue still exists. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776563]
Something doesnt sound right here, it's been over a year that this problem is known and nobody from AMD team commented on this, not even that they are working on it. Now out of a sudden one of their engineers claims they solved it but doesnt attach any kernel patch or info on the issue, just marks it as fix released. Another thing that is weird is that we are almost sure its a BIOS issue according to posts above, so this "fix" might be the same thing that ivrs kernel options do. As for the issue you can verify its existance by the buzzing sound that power components do on the Acer's mainboard when ACPI doesnt work like it should. At Windows 10 the buzzing sound if you take close attention exists where the power management works correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820048] Re: Samba share not automounted
Please add information on what Ubuntu distribution you experienced this problem, and what "resolve package" and version that solved it. Thanks! ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820048 Title: Samba share not automounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1820048/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822820] Re: linux: 4.15.0-48.51 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822817 (xenial/linux-azure), bug 1822819 (xenial/linux-hwe) derivatives: bug 1822802 (linux-raspi2), bug 1822803 (linux-oem), bug 1822805 (linux-aws), bug 1822808 (linux-gcp), bug 1822809 (linux-kvm), bug 1822810 (linux-ibm-gt), bug 1822812 (linux-oracle), bug 1822813 (linux-fips), bug 1822981 (linux), bug 1823254 (linux) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Thursday, 04. April 2019 18:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-beta: 'Pending -- snap pc-kernel not in expected channel(s): armhf:18/beta - amd64:18/beta i386:18/beta' - snap-release-to-edge: 'Pending -- snap pc-kernel not in expected channel(s): armhf:18/edge - amd64:18/edge i386:18/edge' + snap-release-to-beta: 'Pending -- snap pc-kernel not in expected channel(s): i386:18/beta + amd64:18/beta armhf:18/beta' + snap-release-to-edge: 'Pending -- snap pc-kernel not in expected channel(s): i386:18/edge + amd64:18/edge armhf:18/edge' verification-testing: Ongoing -- testing 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/1822820 Title: linux: 4.15.0-48.51 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822834] Re: linux: 4.4.0-146.172 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822832 (trusty/linux-aws), bug 1822833 (trusty/linux-lts-xenial) derivatives: bug 1822824 (linux-aws), bug 1822825 (linux-euclid), bug 1822826 (linux-kvm), bug 1822828 (linux-raspi2), bug 1822829 (linux-snapdragon), bug 1822830 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Thursday, 04. April 2019 18:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-beta: 'Pending -- snap pc-kernel not in expected channel(s): amd64:latest/beta - i386:latest/beta' - snap-release-to-edge: 'Pending -- snap pc-kernel not in expected channel(s): amd64:latest/edge - i386:latest/edge' + snap-release-to-beta: 'Pending -- snap pc-kernel not in expected channel(s): i386:latest/beta + amd64:latest/beta' + snap-release-to-edge: 'Pending -- snap pc-kernel not in expected channel(s): i386:latest/edge + amd64:latest/edge' verification-testing: Ongoing -- testing 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/1822834 Title: linux: 4.4.0-146.172 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823404] [NEW] Memory errors reported by valgrind for gdebi-gtk
Public bug reported: This is for gdebi version 0.9.5.7+nmu2. When running gdebi-gtk through valgrind, for example like this: valgrind gdebi-gtk -h that shows lots of memory errors, for example: - Conditional jump or move depends on uninitialised value(s) - Use of uninitialised value of size 8 - Invalid read of size 4 - Address 0x4e68020 is 304 bytes inside a block of size 2,208 free'd and so on. So there are bugs in the code that can cause the program to crash. One example of a used that got a crash is here: https://askubuntu.com/questions/1131516/gdebi-gtk-segmentation-fault-core-dumped ** Affects: gdebi (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/1823404 Title: Memory errors reported by valgrind for gdebi-gtk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1823404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728238] Re: update-initramfs not adding i915 GuC firmware for Kaby Lake, firmware fails to load
Complement : loading a previous version (from the same sources) of the kernel, but without being patched, seems to work: me@MyMachine~ $ dmesg | grep i915 [2.016454] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [2.016960] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin (v1.1) [2.029825] [drm] HuC: Loaded firmware i915/kbl_huc_ver02_00_1810.bin (version 2.0) [2.040335] [drm] GuC: Loaded firmware i915/kbl_guc_ver9_14.bin (version 9.14) [2.054780] i915 :00:02.0: GuC submission enabled (firmware i915/kbl_guc_ver9_14.bin [version 9.14]) [2.055282] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 [2.514905] i915 :00:02.0: fb0: inteldrmfb frame buffer device [9.433635] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) => i915/kbl_guc_ver9_14.bin => i915/kbl_huc_ver02_00_1810.bin So, IMHO, the Intel blob had no problem at all, and it was maybe simply an issue caused by the server on Intel site uname -a : Linux MintPro 4.15.21 #2 SMP Thu Apr 4 00:38:03 CEST 2019 x86_64 x86_64 x86_64 GNU/Linux HTH -- qɔᴉɹə L'association EducOOo : http://www.educoo.org (dérivé d'OpenOffice) https://framagit.org/ericb/miniDart (logiciel Handball) https://github.com/ebachard (logiciels variés) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1728238 Title: update-initramfs not adding i915 GuC firmware for Kaby Lake, firmware fails to load To manage notifications about this bug go to: https://bugs.launchpad.net/initramfs-tools/+bug/1728238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822820] Re: linux: 4.15.0-48.51 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822817 (xenial/linux-azure), bug 1822819 (xenial/linux-hwe) derivatives: bug 1822802 (linux-raspi2), bug 1822803 (linux-oem), bug 1822805 (linux-aws), bug 1822808 (linux-gcp), bug 1822809 (linux-kvm), bug 1822810 (linux-ibm-gt), bug 1822812 (linux-oracle), bug 1822813 (linux-fips), bug 1822981 (linux), bug 1823254 (linux) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Thursday, 04. April 2019 18:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-beta: 'Pending -- snap pc-kernel not in expected channel(s): amd64:18/beta - armhf:18/beta i386:18/beta' - snap-release-to-edge: 'Pending -- snap pc-kernel not in expected channel(s): amd64:18/edge - armhf:18/edge i386:18/edge' + snap-release-to-beta: 'Pending -- snap pc-kernel not in expected channel(s): armhf:18/beta + amd64:18/beta i386:18/beta' + snap-release-to-edge: 'Pending -- snap pc-kernel not in expected channel(s): armhf:18/edge + amd64:18/edge i386:18/edge' verification-testing: Ongoing -- testing 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/1822820 Title: linux: 4.15.0-48.51 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 151440] Re: standard output: Resource temporarily unavailable
And...this problem goes away if I run the same "tail -f" or "read -t 1" loop on a text-only TTY, or under a "screen" session within a terminal emulator. So it's probably a problem with the terminal emulators (MATE terminal and konsole). I'm guessing screen is able to insulate the TTY environment from the GUI emulator enough to sidestep this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/151440 Title: standard output: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/151440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822820] Re: linux: 4.15.0-48.51 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822817 (xenial/linux-azure), bug 1822819 (xenial/linux-hwe) derivatives: bug 1822802 (linux-raspi2), bug 1822803 (linux-oem), bug 1822805 (linux-aws), bug 1822808 (linux-gcp), bug 1822809 (linux-kvm), bug 1822810 (linux-ibm-gt), bug 1822812 (linux-oracle), bug 1822813 (linux-fips), bug 1822981 (linux), bug 1823254 (linux) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Thursday, 04. April 2019 18:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-beta: 'Pending -- snap pc-kernel not in expected channel(s): armhf:18/beta - amd64:18/beta i386:18/beta' - snap-release-to-edge: 'Pending -- snap pc-kernel not in expected channel(s): armhf:18/edge - amd64:18/edge i386:18/edge' + snap-release-to-beta: 'Pending -- snap pc-kernel not in expected channel(s): amd64:18/beta + armhf:18/beta i386:18/beta' + snap-release-to-edge: 'Pending -- snap pc-kernel not in expected channel(s): amd64:18/edge + armhf:18/edge i386:18/edge' verification-testing: Ongoing -- testing 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/1822820 Title: linux: 4.15.0-48.51 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756608] Re: Applications Menu plugin clips panel icon.
After some comments from Thaddäus I managed to reproduce the problem and pushed a fix to git master: https://git.xfce.org/xfce/xfce4-panel/commit/?id=3abbe78bfa3c643f7d31338e97682d8490a09a59 ** Changed in: xfce4-panel (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: xfce4-panel (Ubuntu) Assignee: (unassigned) => Simon Steinbeiß (ochosi) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756608 Title: Applications Menu plugin clips panel icon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1756608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823401] [NEW] rpl command error on docker container
Public bug reported: Using Ubuntu 18.04 on host, vm and Docker images. However, when I try to change a line in the container I get this error message: rpl "ALLOWED_HOSTS = []" "ALLOWED_HOSTS = ['*']" path/file . Replacing "ALLOWED_HOSTS = []" with "ALLOWED_HOSTS = ['*']" (case sensitive) (partial words matched) .Traceback (most recent call last): File "/usr/bin/rpl", line 314, in main() File "/usr/bin/rpl", line 246, in main matches = blockrepl(f, o, regex, old_str, new_str, 1024) File "/usr/bin/rpl", line 92, in blockrepl parts = (after.join(parts)).encode(encoding=encoding, errors='ignore') TypeError: encode() argument 1 must be str, not None Same command in a vm: rpl "ALLOWED_HOSTS = []" "ALLOWED_HOSTS = ['*']" path/file . Replacing "ALLOWED_HOSTS = []" with "ALLOWED_HOSTS = ['*']" (case sensitive) (partial words matched) . A Total of 1 matches replaced in 1 file searched. ** Affects: rpl (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/1823401 Title: rpl command error on docker container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rpl/+bug/1823401/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823400] [NEW] Kontact fails to start: KSycoca unavailable.
Public bug reported: $ lsb_release -rd Description:Ubuntu 18.04.2 LTS Release:18.04 $ apt-cache policy kontact kontact: Installed: 4:17.12.3-0ubuntu1 Candidate: 4:17.12.3-0ubuntu1 Version table: *** 4:17.12.3-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status Steps to reproduce: 1. sudo apt-get install kontact 2. kontact Expected results: Kontact starts Actual result: The following error message: KSycoca unavailable. Kontact will be unable to find plugins. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: kontact 4:17.12.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 5 15:52:50 2019 InstallationDate: Installed on 2019-03-09 (27 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: kontact UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: kontact (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/1823400 Title: Kontact fails to start: KSycoca unavailable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kontact/+bug/1823400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822359] Re: package mangement system broken apt-get install -f wont fix
*** This bug is a duplicate of bug 1208419 *** https://bugs.launchpad.net/bugs/1208419 I had the exact same problem and error reports (as the OP above) a couple of weeks ago. Running sudo dpkg -i --force-overwrite /var/cache/apt/archives/libuhd3.14.0_3.14.0.0-0ubuntu1~xenial1_amd64.deb seems to have fixed it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822359 Title: package mangement system broken apt-get install -f wont fix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1822359/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815509] Re: Shutdown hung by firmware update daemon
Thanks for the comment. If it's gone with disco I'll close this. Please anyone who encounters it, turn on fwupd verbose logging so we can figure out what is happening if it's fwupd. It's also possible this is the last visible message but it's some other script running at this time. This will be evidenced in a verbose log. ** Changed in: fwupd (Ubuntu) Status: Incomplete => Invalid ** Changed in: systemd (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/1815509 Title: Shutdown hung by firmware update daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1815509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822883] Re: linux: 3.13.0-169.219 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822883 Title: linux: 3.13.0-169.219 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823399] [NEW] package grub-pc 2.02+dfsg1-5ubuntu8.3 failed to install/upgrade: Unterprozess installed grub-pc package post-installation script gab den Fehler-Ausgangsstatus 1 zurück
Public bug reported: it is not possible to actualize the Grub-Bootloader. ProblemType: Package DistroRelease: Ubuntu 18.10 Package: grub-pc 2.02+dfsg1-5ubuntu8.3 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 AptOrdering: grub-efi-amd64-bin:amd64: Install grub-efi-amd64-signed:amd64: Install grub-efi-amd64-dbg:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri Apr 5 20:42:57 2019 ErrorMessage: Unterprozess installed grub-pc package post-installation script gab den Fehler-Ausgangsstatus 1 zurück InstallationDate: Installed on 2017-12-19 (472 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=8de754af-8177-4dff-b2d4-3cdc941f6933 ro recovery nomodeset Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.4 SourcePackage: grub2 Title: package grub-pc 2.02+dfsg1-5ubuntu8.3 failed to install/upgrade: Unterprozess installed grub-pc package post-installation script gab den Fehler-Ausgangsstatus 1 zurück UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823399 Title: package grub-pc 2.02+dfsg1-5ubuntu8.3 failed to install/upgrade: Unterprozess installed grub-pc package post-installation script gab den Fehler-Ausgangsstatus 1 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1823399/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807138] Re: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected
I have an identical setup and problem. ** Changed in: alsa-driver (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807138 Title: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1807138/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823398] [NEW] setvtrgb causes boot delays in clouds
Public bug reported: systemd-analyze output of cloud images shows that setvtrgb.service can take a measureable amount of time to complete. Setting the color pallete for a graphical console on a cloud instance that we have no graphical console access to is not something that should be allowed to slow down boot. Reproduced with disco on a Google GCE instance of type N1_Standard_2. ** Affects: console-setup (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/1823398 Title: setvtrgb causes boot delays in clouds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1823398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1659534] Reminder of SRU verification policy change
Thank you for taking the time to verify this stable release fix. We have noticed that you have used the verification-done tag for marking the bug as verified and would like to point out that due to a recent change in SRU bug verification policy fixes now have to be marked with per-release tags (i.e. verification-done-$RELEASE). Please remove the verification-done tag and add one for the release you have tested the package in. Thank you! https://wiki.ubuntu.com/StableReleaseUpdates#Verification -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1659534 Title: userdel doesn't supports extrausers To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1659534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1728238] Re: update-initramfs not adding i915 GuC firmware for Kaby Lake, firmware fails to load
Disclaimer : what I did concerns 4.15.0 kernel only, on Intel machine (Assus Zenbook pro, x86_64, model: UX410UAR) Hello, Sorry for coming late, but I had the same issue some days ago (never tested before):something like Guc not loading, while Huc did. Of course I hit this page, and some other without find a complete solution. **But** after one day searching, I finaly make it work (!!) , and I'll try to explain what I did (I do not recommend to do the same, but I'll attach a patch (under MIT license, or whatever you need, just ask). The problems: 1. when you download the kbl_guc_ver9_14.bin blob from Intel site, looks like the downloaded file is an .xml file in fact, but not a binary at all. Maybe the site has an issue ? (sorry, not a website specialist) // Can someone verify btw ? 2. IIRC Intel made kbl_guc_ver9_xy.bin for Kabylake, and I simply tried to make the kbl_guv_ver9_39.bin work. Important: I found kbl_guv_ver9_39.bin blob there : http://archive.ubuntu.com/ubuntu/pool/main/l/linux-firmware/ What I did : - I extracted kbl_guv_ver9_39.bin from linux-firmware_1.178_all.deb, and put it in /lib/firmware/i915 After that, I downloaded the most recent 4.15.0 kernel sources (on my LinuxMint 18.3) : => apt-get source linux-source-4.15.0 provided : Réception de :1 http://ubuntu.mirrors.ovh.net/ftp.ubuntu.com/ubuntu xenial-updates/main linux-hwe 4.15.0-47.50~16.04.1 (dsc) [6 511 B] Réception de :2 http://ubuntu.mirrors.ovh.net/ftp.ubuntu.com/ubuntu xenial-updates/main linux-hwe 4.15.0-47.50~16.04.1 (tar) [158 MB] After I downloaded the sources, I copied initrd.img-4.15.0-34-generic as .config in the kernel tree, and I simply patched the following files (in drivers/gpu/drm/i915 : - intel_guc_fw.c - intel_uc.c Comments : - In the first one, I simply modified the binary version (changing KBL_FW_MINOR from 14 to 39) - In the second one, I followed Robert M. Fosha advice (link : https://patchwork.kernel.org/patch/10877903/), allowing to avoind timeout and retry when trying to load the blob => see the attached patch. For the record, my current /etc/modprobe.d/i915.conf contains : options i915 enable_fbc=1 fastboot=1 enable_guc_loading=1 enable_guc_submission=1 Next step was to build the kernel, the Debian way (using make -j8 deb-pkg), and after installing the debs, I got everything working at the end, including the 9_34 version of kbl_guc blob :-) : me@MyMachine ~ $ dmesg | grep i915 [2.018994] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [2.019493] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin (v1.1) [2.031452] [drm] HuC: Loaded firmware i915/kbl_huc_ver02_00_1810.bin (version 2.0) [2.041847] [drm] GuC: Loaded firmware i915/kbl_guc_ver9_39.bin (version 9.39) [2.058753] i915 :00:02.0: GuC submission enabled (firmware i915/kbl_guc_ver9_39.bin [version 9.39]) [2.059299] [drm] Initialized i915 1.6.0 20171023 for :00:02.0 on minor 0 [2.519645] i915 :00:02.0: fb0: inteldrmfb frame buffer device [9.408643] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Conclusion : we can use kbl_guc_ver9_34 with 4.1.5.x kernel. Not sure it is perfect, but "# cat /sys/kernel/debug/dri/0/i915_huc_load_status" returns : HuC firmware: i915/kbl_huc_ver02_00_1810.bin status: fetch SUCCESS, load SUCCESS version: wanted 2.0, found 2.0 header: offset 0, size 128 uCode: offset 128, size 218304 RSA: offset 218432, size 256 HuC status 0x6080: And "# cat /sys/kernel/debug/dri/0/i915_guc_load_status" returns: GuC firmware: i915/kbl_guc_ver9_39.bin status: fetch SUCCESS, load SUCCESS version: wanted 9.39, found 9.39 header: offset 0, size 128 uCode: offset 128, size 147392 RSA: offset 147520, size 256 GuC status 0x800330ec: Bootrom status = 0x76 uKernel status = 0x30 MIA Core status = 0x3 Scratch registers: 0: 0xf000 1: 0x1 2: 0xfede7000 3: 0x5f5e100 4: 0x600 5: 0xcdfd3 6: 0x0 7: 0x8 8: 0x3 9: 0x70240 10: 0x0 11: 0x0 12: 0x0 13: 0x0 14: 0x0 15: 0x0 Last but not least, thanks to Intel people for their work : the HD 620** UHD works very well with mesa 19.1 devel / vulkan 1.1 ! (inxi -G returns Card: Intel UHD Graphics 620) -- qɔᴉɹə L'association EducOOo : http://www.educoo.org (dérivé d'OpenOffice) https://framagit.org/ericb/miniDart (logiciel Handball) https://github.com/ebachard (logiciels variés) ** Patch added: "For testing purpose : this patch can break your machine. If you decice to use it, it is at your own risks."
[Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
well, this is what software updater reports: Installed version: 4.15.0-46.49 (as of #77, which works) Available version: 4.15.0-46.49 (does not work) The available version is the VERY SAME, either with proposed enabled or disabled in software updater !! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1719612] Re: non-us keyboard layout not setup in initramfs
** Changed in: console-setup (Ubuntu Artful) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1719612 Title: non-us keyboard layout not setup in initramfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1719612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783283] Re: setvtrgb.service incorrectly ordered [with patchy]
I don't understand why you are (were) seeing a bug here. There are several other units that declare themselves After=plymouth-quit- wait.service without After=plymouth-quit.service, including getty itself, and I'm not aware of any reports that getty fails to start for users because of this race. This sounds to me like a bug in the calamares-based ISO and its integration with the existing standard systemd units in Ubuntu, not a bug in console-setup. ** Changed in: console-setup (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/1783283 Title: setvtrgb.service incorrectly ordered [with patchy] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1783283/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822380] Re: right-click menu
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: thunar (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/1822380 Title: right-click menu To manage notifications about this bug go to: https://bugs.launchpad.net/thunar/+bug/1822380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1481835]
For the sake of completeness: confirmed in LO 6.2 with original attachment. Details: Version: 6.2.2.2 Build ID: 1:6.2.2-0ubuntu0.18.04.1~lo1 CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: en-AU (en_AU.UTF-8); UI-Language: en-US -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1481835 Title: [UPSTREAM] Unable to group raster image(s) with drawing object(s) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1481835/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756612] Re: Launch and Directory Menu items icons are too small
I cannot confirm this with xfce4-panel 4.13.4 on cosmic with Adwaita. See the attached screenshot. On the left is whiskermenu, on the right a launcher (firefox, but with the whiskermenu icon), both at the same size. ** Attachment added: "left: whiskermenu, right: launcher" https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1756612/+attachment/5253195/+files/Screenshot_2019-04-05_21-01-26.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756612 Title: Launch and Directory Menu items icons are too small To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1756612/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756608] Re: Applications Menu plugin clips panel icon.
I can't confirm the bug with xfce4-panel 4.13.4 (self-built) on cosmic (18.10). I added a screenshot that shows whiskermenu (on the left, dark blue) and the internal applications menu plugin (light blue, on the right) on a 20px tall panel with Adwaita. Both icons are equally un-clipped. ** Attachment added: "xfce4-panel 4.13.4 with whisker and applications-menu" https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1756608/+attachment/5253194/+files/Screenshot_2019-04-05_20-52-54.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1756608 Title: Applications Menu plugin clips panel icon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfce4-panel/+bug/1756608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823391] [NEW] /lib/systemd/system/grub-initrd-fallback.service may be sequenced too early
Public bug reported: The new /lib/systemd/system/grub-initrd-fallback.service introduced in disco and related to initramfsless fallback handling declares itself a dependency of the sysinit.target, which is quite early in boot. This shows up in boot charts of various cloud guest instances, implying that it does have an impact on boot speed. We should evaluate if this can be made a dependency of multi-user.target + rescue.target + emergency.target instead (which, per bootup(7), I believe covers all of the relevant targets we might be booting to). ** Affects: grub2 (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/1823391 Title: /lib/systemd/system/grub-initrd-fallback.service may be sequenced too early To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1823391/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809206]
Created attachment 282133 acpidump data from HP Envy x360 15-cp0xxx New info with kernel 5.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809206 Title: Amd ACPI Error To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1809206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806437]
I am also receiving this message as described in the Ubuntu bug tracker linked above -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806437 Title: acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1756647] Re: clementine crashed with SIGSEGV in QStandardItem::rowCount()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: clementine (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/1756647 Title: clementine crashed with SIGSEGV in QStandardItem::rowCount() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/clementine/+bug/1756647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1477234] Re: SIGSEGV - Segmentation fault on start
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: livemix (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/1477234 Title: SIGSEGV - Segmentation fault on start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livemix/+bug/1477234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1746585] Re: [Latitude E6420, IDT 92HD90BXX, Black Headphone Out, Left] No sound at all
Hi Daniel, Thank you for reaching out. I ran sudo apt remove timidity* and then rebooted. It did not fix the issue. Thanks, -- Ryan Viertel On Sun, Mar 31, 2019 at 11:40 PM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > Please try uninstalling 'timidity' and all 'timidity' related packages. > Then reboot. > > ** Changed in: alsa-driver (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1746585 > > Title: > [Latitude E6420, IDT 92HD90BXX, Black Headphone Out, Left] No sound at > all > > Status in alsa-driver package in Ubuntu: > Incomplete > > Bug description: > Speakers and HDMI sound work fine, only headphones not working. I went > through all of the steps on > > https://help.ubuntu.com/community/SoundTroubleshootingProcedure > https://help.ubuntu.com/community/SoundTroubleshooting > and > https://wiki.ubuntu.com/DebuggingSoundProblems > > and submitted this report with ubuntu-bug -s audio > > Some possibly relevant information: This installation of Ubuntu was > originally installed on a Dell Inspiron 15, but I cloned the partition > onto an SSD that I installed on the Latitude 6420. It is the Latitude > that is affected, the headphones work fine on the Inspiron. > > Let me know if any more information is required. > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu5 > ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 > Uname: Linux 4.13.0-32-generic x86_64 > ApportVersion: 2.20.1-0ubuntu2.15 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/pcmC0D0p: rviertel 2881 F...m pulseaudio >/dev/snd/controlC0: rviertel 2881 F pulseaudio > rviertel 4589 F alsamixer > CurrentDesktop: Unity > Date: Wed Jan 31 12:22:17 2018 > InstallationDate: Installed on 2015-04-27 (1009 days ago) > InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 > (20150218.1) > PackageArchitecture: all > SourcePackage: alsa-driver > Symptom: audio > Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed > Symptom_Card: Built-in Audio - HDA Intel PCH > Symptom_DevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/pcmC0D0p: rviertel 2881 F...m pulseaudio >/dev/snd/controlC0: rviertel 2881 F pulseaudio > rviertel 4589 F alsamixer >/dev/snd/seq:timidity 1191 F timidity > Symptom_Jack: Black Headphone Out, Left > Symptom_Type: No sound at all > Title: [Latitude E6420, IDT 92HD90BXX, Black Headphone Out, Left] No > sound at all > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 07/11/2011 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: A06 > dmi.board.name: 0K0DNP > dmi.board.vendor: Dell Inc. > dmi.board.version: A02 > dmi.chassis.type: 9 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: > dmi:bvnDellInc.:bvrA06:bd07/11/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn0K0DNP:rvrA02:cvnDellInc.:ct9:cvr: > dmi.product.name: Latitude E6420 > dmi.product.version: 01 > dmi.sys.vendor: Dell Inc. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1746585/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1746585 Title: [Latitude E6420, IDT 92HD90BXX, Black Headphone Out, Left] No sound at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1746585/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822820] Re: linux: 4.15.0-48.51 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822817 (xenial/linux-azure), bug 1822819 (xenial/linux-hwe) derivatives: bug 1822802 (linux-raspi2), bug 1822803 (linux-oem), bug 1822805 (linux-aws), bug 1822808 (linux-gcp), bug 1822809 (linux-kvm), bug 1822810 (linux-ibm-gt), bug 1822812 (linux-oracle), bug 1822813 (linux-fips), bug 1822981 (linux), bug 1823254 (linux) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Thursday, 04. April 2019 18:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-beta: 'Pending -- snap pc-kernel not in expected channel(s): i386:18/beta - amd64:18/beta armhf:18/beta' - snap-release-to-edge: 'Pending -- snap pc-kernel not in expected channel(s): i386:18/edge - amd64:18/edge armhf:18/edge' + snap-release-to-beta: 'Pending -- snap pc-kernel not in expected channel(s): armhf:18/beta + amd64:18/beta i386:18/beta' + snap-release-to-edge: 'Pending -- snap pc-kernel not in expected channel(s): armhf:18/edge + amd64:18/edge i386:18/edge' verification-testing: Ongoing -- testing 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/1822820 Title: linux: 4.15.0-48.51 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770173] Re: 18.04 install stuck on grub install when a zfs disk is present
Even after removing all drive partitions from the ZFS drives, I am still having this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770173 Title: 18.04 install stuck on grub install when a zfs disk is present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1770173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822834] Re: linux: 4.4.0-146.172 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822832 (trusty/linux-aws), bug 1822833 (trusty/linux-lts-xenial) derivatives: bug 1822824 (linux-aws), bug 1822825 (linux-euclid), bug 1822826 (linux-kvm), bug 1822828 (linux-raspi2), bug 1822829 (linux-snapdragon), bug 1822830 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Thursday, 04. April 2019 18:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-beta: 'Pending -- snap pc-kernel not in expected channel(s): i386:latest/beta - amd64:latest/beta' - snap-release-to-edge: 'Pending -- snap pc-kernel not in expected channel(s): i386:latest/edge - amd64:latest/edge' + snap-release-to-beta: 'Pending -- snap pc-kernel not in expected channel(s): amd64:latest/beta + i386:latest/beta' + snap-release-to-edge: 'Pending -- snap pc-kernel not in expected channel(s): amd64:latest/edge + i386:latest/edge' verification-testing: Ongoing -- testing 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/1822834 Title: linux: 4.4.0-146.172 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822834/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822134] Re: Ubuntu Studio Installation - Black Text on Dark Gray
Tried with the latest daily ISO for Ubuntu Studio, and the bug still exists. ** Changed in: materia-gtk-theme (Ubuntu) Status: Fix Released => Confirmed ** Changed in: ubuntustudio Status: Fix Committed => 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/1822134 Title: Ubuntu Studio Installation - Black Text on Dark Gray To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntustudio/+bug/1822134/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823259] Re: Update from grub-common AMD64 2.02-2ubuntu8.12 to 2.02-2ubuntu8.13 removed some Grub settings
Could you please run: sudo debconf-show grub-pc sudo debconf-show grub-efi-amd64 I've attempted to reproduce this; by first downgrading to a previous version, changing settings in /etc/default/grub, and proceeding with the upgrade, but no matter what I do, the changes do remain in /etc/default/grub. I've tried simply setting i915.modeset=1, but also reverting again (so i915.modeset=1 is present in debconf to begin with) and adding another entry to be in GRUB_LINUX_CMDLINE_DEFAULT; and also the same with GRUB_LINUX_CMDLINE. As far as I call tell, the update works correctly, so we need to look if there's anything special in the debconf database in case that would affect the behavior. Note for developers: the ucf code is only in grub-pc.postinst or grub- efi-amd64.postinst; so this affects those packages rather than grub(2?)-common. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823259 Title: Update from grub-common AMD64 2.02-2ubuntu8.12 to 2.02-2ubuntu8.13 removed some Grub settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1823259/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822820] Re: linux: 4.15.0-48.51 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822817 (xenial/linux-azure), bug 1822819 (xenial/linux-hwe) derivatives: bug 1822802 (linux-raspi2), bug 1822803 (linux-oem), bug 1822805 (linux-aws), bug 1822808 (linux-gcp), bug 1822809 (linux-kvm), bug 1822810 (linux-ibm-gt), bug 1822812 (linux-oracle), bug 1822813 (linux-fips), bug 1822981 (linux), bug 1823254 (linux) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Thursday, 04. April 2019 18:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: 'Pending -- snap pc-kernel not in expected channel(s): i386:18/beta - armhf:18/beta amd64:18/beta' + amd64:18/beta armhf:18/beta' snap-release-to-edge: 'Pending -- snap pc-kernel not in expected channel(s): i386:18/edge - armhf:18/edge amd64:18/edge' + amd64:18/edge armhf:18/edge' verification-testing: Ongoing -- testing 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/1822820 Title: linux: 4.15.0-48.51 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability
The patch got also merged into the 3.24 branch of GTK: https://gitlab.gnome.org/GNOME/gtk/merge_requests/717 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763520 Title: after upgrade to bionic, printing fails without explanation / logs / debuggability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1763520/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819924] Re: System hangs when hot-plugging dual monitor dock
I don't think this issue is related to LP #1820811. In #1820811, the hang always occurs when hot-plugging. With this issue, if the device is cold plugged (plugged in at boot), it can be disconencted and re-connected without issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819924 Title: System hangs when hot-plugging dual monitor dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1819924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823346] 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/1823346 Title: SD card stays locked even when unlocked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823386] [NEW] [MRE] Please update to latest upstream release 7.2.17 & 7.3.4
*** This bug is a security vulnerability *** Public security bug reported: Upstream has released microversions addressing security issues (pending CVE attribution) and other bug fixes. PHP 7.2.16 / 7.3.3 (07 Mar 2019): * The CVEs addressed were backported by the security team already PHP 7.2.17 / 7.3.4 (04 Apr 2019): * https://bugs.php.net/bug.php?id=77753 / CVE-pending * https://bugs.php.net/bug.php?id=77831 / CVE-pending Changelog: https://secure.php.net/ChangeLog-7.php ** Affects: php7.2 (Ubuntu) Importance: Undecided Status: New ** 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/1823386 Title: [MRE] Please update to latest upstream release 7.2.17 & 7.3.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php7.2/+bug/1823386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816808] Re: [disco] OSK does not appear under wayland when a text-entry is focused
it's not a hard requirement anymore, actually.. so, fixing cosmic is 'nice to have' if you can provide the fix and test it, but not strictly required -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816808 Title: [disco] OSK does not appear under wayland when a text-entry is focused To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1816808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814369] Re: update toolchain packages for bionic
Hello Matthias, or anyone else affected, Accepted gcc-7-cross into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gcc-7-cross/26ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gcc-7-cross (Ubuntu Cosmic) Status: New => Fix Committed ** Changed in: gcc-7-cross-ports (Ubuntu Cosmic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814369 Title: update toolchain packages for bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eclipse-titan/+bug/1814369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766076] Re: USB over thunderbolt turns off every once in a while
I had seen this issue on a Precision 5510. I am running the 5.0.x kernel series for a while now and haven't had any issues so far. Currently on 5.0.6. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766076 Title: USB over thunderbolt turns off every once in a while To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1766076/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814369] Please test proposed package
Hello Matthias, or anyone else affected, Accepted gcc-7-cross-ports into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gcc-7 -cross-ports/21ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814369 Title: update toolchain packages for bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eclipse-titan/+bug/1814369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823383] [NEW] grub-efi fails to register boot entry
Public bug reported: Every time grub is updating it removes an already existing efi boot entry and tries to create a new one. In my case it fails to make new entry with an error: grub-install: error: efibootmgr failed to register the boot entry: Input/output error. Due to this failure, system becomes unbootable since there is no boot entry in efivar. I have to then manually boot system with efi_no_storage_paranoia kernel parameter in order for grub to successfully install. There is already patch available for the main grub repository to fix grub-install to not re-create efi boot entry if one already exists. The patch can be found here: https://salsa.debian.org/grub-team/grub/commit/c3ab38fcac862d07eceefe3c56fa22b140f37410 Link to the issue it fixes: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891434 ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Description changed: - Every time grub is updating it removes an already existing efi boot entry and tries to create a new one. This fails with an error: + Every time grub is updating it removes an already existing efi boot entry and tries to create a new one. In my case it to fails to make new entry with an error: grub-install: error: efibootmgr failed to register the boot entry: Input/output error. Due to this failure system becomes unbootable since there is no boot entry in efivar. I have to then manually boot system with efi_no_storage_paranoia kernel parameter in order for grub to successfully install. There is already patch available for the main grub repository to fix grub-install to not re-create efi boot entry if one already exists. The patch can be found here: https://salsa.debian.org/grub-team/grub/commit/c3ab38fcac862d07eceefe3c56fa22b140f37410 Link to the issue it fixes: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891434 ** Description changed: - Every time grub is updating it removes an already existing efi boot entry and tries to create a new one. In my case it to fails to make new entry with an error: + Every time grub is updating it removes an already existing efi boot entry and tries to create a new one. In my case it fails to make new entry with an error: grub-install: error: efibootmgr failed to register the boot entry: Input/output error. Due to this failure system becomes unbootable since there is no boot entry in efivar. I have to then manually boot system with efi_no_storage_paranoia kernel parameter in order for grub to successfully install. There is already patch available for the main grub repository to fix grub-install to not re-create efi boot entry if one already exists. The patch can be found here: https://salsa.debian.org/grub-team/grub/commit/c3ab38fcac862d07eceefe3c56fa22b140f37410 Link to the issue it fixes: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891434 ** Description changed: Every time grub is updating it removes an already existing efi boot entry and tries to create a new one. In my case it fails to make new entry with an error: grub-install: error: efibootmgr failed to register the boot entry: Input/output error. - Due to this failure system becomes unbootable since there is no boot + Due to this failure, system becomes unbootable since there is no boot entry in efivar. I have to then manually boot system with efi_no_storage_paranoia kernel parameter in order for grub to successfully install. There is already patch available for the main grub repository to fix grub-install to not re-create efi boot entry if one already exists. The patch can be found here: https://salsa.debian.org/grub-team/grub/commit/c3ab38fcac862d07eceefe3c56fa22b140f37410 Link to the issue it fixes: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891434 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823383 Title: grub-efi fails to register boot entry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1823383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822402] Re: gnome calendar automatically moves event back 1 day
** Changed in: gnome-calendar (Ubuntu) Status: Incomplete => Opinion ** Changed in: gnome-calendar (Ubuntu) Status: Opinion => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822402 Title: gnome calendar automatically moves event back 1 day To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1822402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823382] [NEW] backport openssl 1.1.1 fixes to bionic and cosmic
Public bug reported: [Impact] * neon27 doesn't work with openssl 1.1.1 * backport fixes from disco to cosmic and bionic to resolve that [Test Case] * does not FTBFS [Regression Potential] * currently broken in cosmic, and will break once openssl is upgraded in bionic, so for all practical purposes it's completely busted at the moment. [Other Info] * Fixes already in disco and unstable. ** Affects: neon27 (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: neon27 (Ubuntu Bionic) Importance: Undecided Status: In Progress ** Affects: neon27 (Ubuntu Cosmic) Importance: Undecided Status: In Progress ** Affects: neon27 (Ubuntu Disco) Importance: Undecided Status: Fix Released ** Also affects: neon27 (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: neon27 (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: neon27 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: neon27 (Ubuntu Disco) Status: New => Fix Released ** Changed in: neon27 (Ubuntu Cosmic) Status: New => In Progress ** Changed in: neon27 (Ubuntu Bionic) Status: New => 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/1823382 Title: backport openssl 1.1.1 fixes to bionic and cosmic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/neon27/+bug/1823382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823336] Re: Scrolling the sound panel with the mouse wheel can result in sliders being moved by mistake
Unsure it's really a bug, mouse wheel scrolling is supposed to scroll on sliders and it's always a chance that you end up over a slider depending of the UI/screen size parameters ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Critical ** Changed in: gnome-control-center (Ubuntu) Importance: Critical => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823336 Title: Scrolling the sound panel with the mouse wheel can result in sliders being moved by mistake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1823336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS
** Description changed: [Impact] * OpenSSL 1.1.1 is an LTS release upstream, which will continue to receive security support for much longer than 1.1.0 series will. * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to be rapidly adopted due to increased set of supported hashes & algoes, as well as improved handshake [re-]negotiation. * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities. * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some software is sensitive to the negotiation handshake and may either need patches/improvements or clamp-down to maximum v1.2. [Test Case] * Rebuild all reverse dependencies * Execute autopkg tests for all of them * Clamp down to TLS v1.2 software that does not support TLS v1.3 (e.g. mongodb) * Backport TLS v1.3 support patches, where applicable [Test cases for the python updates] python3.7 is a preview in bionic as a non-supported/non-default version of python3. Passing it's own autopkgtests is sufficient validation for python3.7. It includes a point release update, with OpenSSL 1.1.1 compat and features. python3.6 not only has OpenSSL 1.1.1 compat and features patches, but also includes a point release update to 3.6.8. It has been part of the full-archive rebuild and regression analysis. Autopkgtests were triggered for python3.6 and python3-defaults with regressions already fixed in the individual packages as appropriate. python2.7 has the update from .15~rc1 to .15 final, with OpenSSL 1.1.1 compat only. It has been part of the full-archive rebuild and regression analysis. Autopkgtests were triggered for python2.7 and python-defaults with regressions already fixed in the individual packages as appropriate. + + The archive rebuilds done, were commulative with OpenJDK 11, OpenSSL 1.1.1 and python point releases as seen in: + http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html + http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-test-bionic.html + + And analyzed in + https://docs.google.com/spreadsheets/d/1tMIwlwoHH_1h5sbvUbNac6-HIPKi3e0Xr8ebchIOU1A/edit#gid=147857652 [Regression Potential] * Connectivity interop is the biggest issues which will be unavoidable with introducing TLS v1.3. However, tests on cosmic demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and negotiate TLS v1.3 without issues. * Mitigation of discovered connectivity issues will be possible by clamping down to TLS v1.2 in either server-side or client-side software or by backporting relevant support fixes * Notable changes are listed here https://wiki.openssl.org/index.php/TLS1.3 * Most common connectivity issues so far: - client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname. Solution is client change to set hostname, or to clamp down the client to TLSv1.2. - session negotiation is different in TLSv1.3, existing client code may fail to create/negotiate/resume session. Clients need to learn how to use session callback. * This update bundles python 3.6 and 3.7 point releases [Other Info] * Previous FFe for OpenSSL in 18.10 is at https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092 * TLS v1.3 support in NSS is expected to make it to 18.04 via security updates * TLS v1.3 support in GnuTLS is expected to be available in 19.04 * Test OpenSSL is being prepared in https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3473 [Autopkgtest Regressions] dovecot/armhf - flakey libnet-ssleay-perl - awaiting sru accept into proposed of libnet-ssleay-perl and libio-socket-ssl-perl due to fixes and versioned breaks. linux* - rebuild testcases passes (for some edge flavours the build fails in non-ssl portions of the build), ubuntu-regression-suite testcase fails for a few variants but should have been skipped (in progress to be fixed in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823056) openvswitch/i386 - extremely flakey, errors out or fails mostly -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797386 Title: [SRU] OpenSSL 1.1.1 to 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1797386/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822816] Re: linux-azure: 4.15.0-1042.46~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-trusty ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1822817 - phase: Holding before Promote to Proposed - phase-changed: Friday, 05. April 2019 14:41 UTC + phase: Ready for Promote to Proposed + phase-changed: Friday, 05. April 2019 17:41 UTC reason: - promote-to-proposed: Holding -- builds not complete + promote-to-proposed: Pending -- ready for review -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822816 Title: linux-azure: 4.15.0-1042.46~14.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822816/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823346] Re: SD card stays locked even when unlocked
it's more likely a kernel issue, reassigning ** Package changed: udisks2 (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823346 Title: SD card stays locked even when unlocked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823346/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823354] Re: printer is no longer visable
Thank you for your bug report. Could you make a screenshot showing the issue? What printer do you use and how is it connected to the system? ** Package changed: xorg (Ubuntu) => gnome-control-center (Ubuntu) ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-control-center (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/1823354 Title: printer is no longer visable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1823354/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (using "foreign grub")
just some summary thoughts in addition to point to some anomalies .. the "failures in lightdm appear to correspond with shorter journal logs .. so certain processes are not running as expected .. plymouth also does not appear on the screen .. as it needs the proper graphics support .. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1821609 Title: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870 (using "foreign grub") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1821609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822820] Re: linux: 4.15.0-48.51 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822817 (xenial/linux-azure), bug 1822819 (xenial/linux-hwe) derivatives: bug 1822802 (linux-raspi2), bug 1822803 (linux-oem), bug 1822805 (linux-aws), bug 1822808 (linux-gcp), bug 1822809 (linux-kvm), bug 1822810 (linux-ibm-gt), bug 1822812 (linux-oracle), bug 1822813 (linux-fips), bug 1822981 (linux), bug 1823254 (linux) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Thursday, 04. April 2019 18:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff snap-release-to-beta: 'Pending -- snap pc-kernel not in expected channel(s): i386:18/beta - amd64:18/beta armhf:18/beta' + armhf:18/beta amd64:18/beta' snap-release-to-edge: 'Pending -- snap pc-kernel not in expected channel(s): i386:18/edge - amd64:18/edge armhf:18/edge' + armhf:18/edge amd64:18/edge' verification-testing: Ongoing -- testing 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/1822820 Title: linux: 4.15.0-48.51 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820811] Re: Thunderbolt3 dock freezes X on hotplug when used with external displays
Yes, hang re-occurs regardless of whether the device was plugged in at boot or not. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820811 Title: Thunderbolt3 dock freezes X on hotplug when used with external displays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823004] Re: Upgrade to 19.04 - cannot install 'install-info'
** Tags added: rls-dd-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823004 Title: Upgrade to 19.04 - cannot install 'install-info' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1823004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823379] [NEW] Apparmor enforcement failure in lxc selftests
Public bug reported: The lxc apparmor tests are failing with linux 5.0.0-9.10. The test expects an open of /sys/kernel/uevent_helper to fail, but it succeeds: FAIL: lxc-tests: lxc-test-apparmor (2s) --- failed - opened /sys/kernel/uevent_helper --- Full test log: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-disco-canonical-kernel-team- bootstrap/disco/amd64/l/lxc/20190405_07_d0e52@/log.gz ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823379 Title: Apparmor enforcement failure in lxc selftests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823325] Re: Sync opensaml 3.0.1-1 (universe) from Debian unstable (main)
** 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/1823325 Title: Sync opensaml 3.0.1-1 (universe) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opensaml/+bug/1823325/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822886] Re: universe missing after bionic->cosmic do-release-upgrade
** Also affects: ubuntu-release-upgrader (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: ubuntu-release-upgrader (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: ubuntu-release-upgrader (Ubuntu Bionic) Importance: Undecided => Critical ** Changed in: ubuntu-release-upgrader (Ubuntu Cosmic) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822886 Title: universe missing after bionic->cosmic do-release-upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1822886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823380] [NEW] package policykit-1 0.105-14.1ubuntu0.4 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
Public bug reported: was able to boot into ubuntu generic but unable to boot into regular mode would get flip_done time out if I attempted to boot normally Computer is dual booted with Windows 7 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: policykit-1 0.105-14.1ubuntu0.4 ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Apr 5 13:08:57 2019 ErrorMessage: subprocess new pre-installation script returned error exit status 1 InstallationDate: Installed on 2019-01-15 (80 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SourcePackage: policykit-1 Title: package policykit-1 0.105-14.1ubuntu0.4 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: policykit-1 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1823380 Title: package policykit-1 0.105-14.1ubuntu0.4 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1823380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822790] Re: linux-azure: 4.18.0-1015.15~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1822789 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822791 - phase: Promote to Proposed - phase-changed: Friday, 05. April 2019 09:10 UTC + phase: Testing + phase-changed: Friday, 05. April 2019 17:12 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for mirror - sync - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Stalled -- testing FAILED + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + snap-release-to-beta: 'Pending -- snap azure-kernel not in expected channel(s): + amd64:18/beta' + snap-release-to-edge: 'Pending -- snap azure-kernel not in expected channel(s): + amd64:18/edge' + stakeholder-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing 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/1822790 Title: linux-azure: 4.18.0-1015.15~18.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822790/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823380] Re: package policykit-1 0.105-14.1ubuntu0.4 failed to install/upgrade: subprocess new pre-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/1823380 Title: package policykit-1 0.105-14.1ubuntu0.4 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1823380/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822812] Re: linux-oracle: 4.15.0-1011.13 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822811 (xenial/linux-oracle) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 - phase: Promote to Proposed - phase-changed: Friday, 05. April 2019 11:06 UTC + phase: Testing + phase-changed: Friday, 05. April 2019 17:07 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Stalled -- testing FAILED + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing 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/1822812 Title: linux-oracle: 4.15.0-1011.13 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822616] Re: [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_screen_size
** 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/1822616 Title: [regression][nvidia] gnome-shell/budgie-wm crashed with SIGABRT "assertion failed: (width > 0 && height > 0 && scale > 0)" in meta_monitor_manager_xrandr_update_screen_size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1822616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697959] Re: late package version collection can cause confusion
When looking at bug 1822395 it occurred to me that this could also be an issue if an application were to crash during the release upgrade process and the data collection were done after the upgrade. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697959 Title: late package version collection can cause confusion To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1697959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822833] Re: linux-lts-xenial: 4.4.0-146.172~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1822834 - phase: Packaging - phase-changed: Friday, 05. April 2019 07:37 UTC + phase: Holding before Promote to Proposed + phase-changed: Friday, 05. April 2019 17:10 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Holding -- builds not complete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1822833 Title: linux-lts-xenial: 4.4.0-146.172~14.04.1 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822817] Re: linux-azure: 4.15.0-1042.46 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822816 (trusty/linux-azure) derivatives: bug 1822814 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1822820 - phase: Promote to Proposed - phase-changed: Friday, 05. April 2019 09:36 UTC + phase: Testing + phase-changed: Friday, 05. April 2019 17:08 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for mirror - sync - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Stalled -- testing FAILED + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + snap-release-to-beta: 'Pending -- snap azure-kernel not in expected channel(s): + amd64:latest/beta' + snap-release-to-edge: 'Pending -- snap azure-kernel not in expected channel(s): + amd64:latest/edge' + stakeholder-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing 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/1822817 Title: linux-azure: 4.15.0-1042.46 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822817/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1822820] Re: linux: 4.15.0-48.51 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1822817 (xenial/linux-azure), bug 1822819 (xenial/linux-hwe) derivatives: bug 1822802 (linux-raspi2), bug 1822803 (linux-oem), bug 1822805 (linux-aws), bug 1822808 (linux-gcp), bug 1822809 (linux-kvm), bug 1822810 (linux-ibm-gt), bug 1822812 (linux-oracle), bug 1822813 (linux-fips), bug 1822981 (linux), bug 1823254 (linux) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Thursday, 04. April 2019 18:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff - snap-release-to-beta: 'Pending -- snap pc-kernel not in expected channel(s): armhf:18/beta - i386:18/beta amd64:18/beta' - snap-release-to-edge: 'Pending -- snap pc-kernel not in expected channel(s): armhf:18/edge - i386:18/edge amd64:18/edge' + snap-release-to-beta: 'Pending -- snap pc-kernel not in expected channel(s): i386:18/beta + amd64:18/beta armhf:18/beta' + snap-release-to-edge: 'Pending -- snap pc-kernel not in expected channel(s): i386:18/edge + amd64:18/edge armhf:18/edge' verification-testing: Ongoing -- testing 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/1822820 Title: linux: 4.15.0-48.51 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822820/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820811] Re: Thunderbolt3 dock freezes X on hotplug when used with external displays
Sorry for the delayed followup, but if your machine is booted with it plugged in, are you then able to unplug and re-plug the device without issue? Or does the hang re-occur regardless of whether the device was plugged in at boot or not? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820811 Title: Thunderbolt3 dock freezes X on hotplug when used with external displays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1823376] [NEW] Please add ${distro_id}ESM:${distro_codename}-security to allowed origins (on Ubuntu)
Public bug reported:
.
** Affects: unattended-upgrades (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/1823376
Title:
Please add ${distro_id}ESM:${distro_codename}-security to allowed
origins (on Ubuntu)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1823376/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776563]
He has changed the bug status to "Fix Released" on Ubuntu's Launchpad. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
