[Bug 2067096] [NEW] dont update to 24.04 ver
Public bug reported: dont update to 24.04 ver ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-release-upgrader-core 1:23.10.14 ProcVersionSignature: Ubuntu 6.5.0-35.35-generic 6.5.13 Uname: Linux 6.5.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri May 24 20:14:15 2024 InstallationDate: Installed on 2022-05-11 (744 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: LANG=uk_UA.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to mantic on 2024-05-24 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade mantic wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2067096 Title: dont update to 24.04 ver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2067096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059721] Re: ovn db upgrade
Nah, I guess I just meant - after it. I just spotted that DB schema was updated only when ovn-northd -> ovn-central are restarted. For me ovn- central did not start on it's own, but I cut couple of corners while trying to reproduce the issue. Eventually, I just upgraded a host rather then re-install it. So that's why it could be working in my test env, as database was present on the expected location during OVN startup, rather then it needs to fetch it and convert. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059721 Title: ovn db upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ansible/+bug/2059721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059721] Re: ovn db upgrade
Actually, I do have `2024-03-29T11:34:33.886Z|00041|main|INFO|OVNSB commit failed, force recompute next time.` - but I do get it on ovn- controller (compute) node which was not upgraded yet. Also I do not see that message right after service restart anymore: https://paste.openstack.org/show/bJDQ7Gx5e9zmzv4zN7HQ/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059721 Title: ovn db upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ansible/+bug/2059721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059721] Re: ovn db upgrade
No, I do not. That is basically the whole log I got on one of isntances: https://paste.openstack.org/show/brE4aA8VFptpmMkGn8EE/ Though keep in mind, that I tried that on dummy sandbox. Also question - you've upgraded controllers or re-installed? As I assume you did rebuild ovn-northd containers afterwards? I'm just trying to find a way reproducing that in any way. And I indeed do see couple of chicken-egg situations already - as you've mentioned ordering of compute/controller upgrade. As eventually, to successfully upgrade compute you'd need to have at least 1 upgraded repo container for building wheels, otherwise OpenStack infrastructure could be exposed to quite heavy load if you'd deploy XX amount of computes at the same time... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2059721 Title: ovn db upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ansible/+bug/2059721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059721] Re: ovn db upgrade
Hi, So, I totally see issues in ordering of tasks for OVN upgrade and couple of missing handlers we obviously need to cover. However, I was able to launch OVN cluster after upgrade. Basically, these steps should be taken for successful upgrade: 1. Upgrade/restart all ovn-controllers 2. Upgrade ovn-northd. Once it's upgraded you need to restart ovn-northd service and ovn-central right after it. Once 2 out of 3 ovn-northd are upgraded, DB upgrade will be performed to the new schema. So eventually, I've updated 1st ovn-northd container to 22.04 and I got same output as you did: root@aio1-neutron-ovn-northd-container-519166b6:/# ovn-nbctl --version ovn-nbctl 23.03.1 Open vSwitch Library 3.1.2 DB Schema 7.0.0 root@aio1-neutron-ovn-northd-container-519166b6:/# ovsdb-client get-schema-version unix:/var/run/ovn/ovnnb_db.sock 6.1.0 root@aio1-neutron-ovn-northd-container-519166b6:/# Then, I've updated second container to 22.04 and restarted ovn-northd and ovn-central, and got new schema on the first one right away: root@aio1-neutron-ovn-northd-container-519166b6:/# ovsdb-client get-schema-version unix:/var/run/ovn/ovnnb_db.sock 7.0.0 root@aio1-neutron-ovn-northd-container-519166b6:/# I will work on role/playbooks to cover upgrade process ordering and found nits. ** Changed in: openstack-ansible 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/2059721 Title: ovn db upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ansible/+bug/2059721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2059721] Re: ovn db upgrade
Hey, Thanks for reporting that. I believe OpenStack-Ansible indeed miss a required step for proper OVN upgrade on OS resetup. I will check on the issue in a timely manner. ** Changed in: openstack-ansible 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/2059721 Title: ovn db upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ansible/+bug/2059721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964558] [NEW] apt-transport-s3 fails with TypeError: decoding str is not supported
Public bug reported: Ubuntu Release -- Description:Ubuntu Jammy Jellyfish (development branch) Release:22.04 Package --- Package: apt-transport-s3 Version: 2.0.0-2 Expected Result --- "apt-get update" correctly updates the package database from an S3-based APT repository. Actual Result - When using the EC2 instance's IAM role credentials, "apt-get update" fails as follows. Traceback (most recent call last): File "/usr/lib/apt/methods/s3", line 597, in method = S3_method(config) File "/usr/lib/apt/methods/s3", line 384, in __init__ self.iam.get_credentials() File "/usr/lib/apt/methods/s3", line 191, in get_credentials str(self.credentials_metadata, 'utf-8'), TypeError: decoding str is not supported Hit:1 http://us-east-1.ec2.archive.ubuntu.com/ubuntu jammy InRelease Hit:2 http://us-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates InRelease Hit:3 http://us-east-1.ec2.archive.ubuntu.com/ubuntu jammy-backports InRelease Hit:4 http://security.ubuntu.com/ubuntu jammy-security InRelease Reading package lists... Done E: Method s3 has died unexpectedly! E: Sub-process s3 returned an error code (1) E: Method /usr/lib/apt/methods/s3 did not start correctly E: Failed to fetch s3:///private/ubuntu/dists/jammy/InRelease E: Some index files failed to download. They have been ignored, or old ones used instead. ** Affects: apt-transport-s3 (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/1964558 Title: apt-transport-s3 fails with TypeError: decoding str is not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-transport-s3/+bug/1964558/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911893] Re: latest microcode is not working properly on intel core i9
Hello Asus delivered new BIOS update for the laptop - " Version 309 2021/12/06" (https://rog.asus.com/laptops/rog-flow/rog-g703-series/helpdesk_bios) with description "Optimize system performance". After upgrading BIOS problem solved and I can use laptop with the latest intel microcode. It a SHAME for the ASUS ROG due to fix was delivered AFTER 2 years! Also there is no info about fix, just description "Optimize system performance". Unfortunately premium ASUS ROG laptop with bad quality support. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911893 Title: latest microcode is not working properly on intel core i9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1911893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879387] Re: Opus module fail to load (Ubuntu 20.04)
Previous patch does not work because pbuilder redefines LDFLAGS. Fixed. ** Patch added: "1005_make_explicit_libs.patch" https://bugs.launchpad.net/ubuntu/+source/asterisk-opus/+bug/1879387/+attachment/5518436/+files/1005_make_explicit_libs.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879387 Title: Opus module fail to load (Ubuntu 20.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/asterisk-opus/+bug/1879387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879387] Re: Opus module fail to load (Ubuntu 20.04)
This is an ubuntu-specific issue. I fixed it as described here: https://lists.ubuntu.com/archives/ubuntu-devel/2010-November/031991.html ** Patch added: "1005_make_explicit_libs.patch" https://bugs.launchpad.net/ubuntu/+source/asterisk-opus/+bug/1879387/+attachment/5518386/+files/1005_make_explicit_libs.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879387 Title: Opus module fail to load (Ubuntu 20.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/asterisk-opus/+bug/1879387/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845765] Re: asterisk-modules package built without amr_codec.so
** Changed in: asterisk (Ubuntu) Status: Triaged => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845765 Title: asterisk-modules package built without amr_codec.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1845765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845765] Re: asterisk-modules package built without amr_codec.so
This module depends on opencore-amrnb, opencore-amrwb and vo-amrwbenc together. Because the libvo-amrwbenc-dev package was not found in the build environment, the compilation of this module was silently skipped. To solve this problem, add libvo-amrwbenc-dev to build dependencies in debian/control file and rebuild the package. I copied this module to existing installation and reload asterisk: Connected to Asterisk 16.2.1~dfsg-2ubuntu1 currently running on vserver3 (pid = 6653) vserver3*CLI> module show like codec_amr Module Description Use Count Status Support Level codec_amr.so AMR Coder/Decoder0 Running core 1 modules loaded -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845765 Title: asterisk-modules package built without amr_codec.so To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/asterisk/+bug/1845765/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911893] Re: latest microcode is not working properly on intel core i9
Hello Half a year since issue posted in https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/50 but is seems like nobody support intel microcode and I still can't use my laptop with ubuntu and latest intel-microcode(which already installed out of the box on ubuntu). Also as I can see other customers have another issues with intel microcode but there is still no response/fixes. Is it possible to exclude intel-microcode package from next ubuntu releases? What is the positive things when intel microcode installed on ubuntu? With hope Thanks in Advance -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911893 Title: latest microcode is not working properly on intel core i9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1911893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911893] Re: latest microcode is not working properly on intel core i9
Thanks. But daily-live also is not working with the latest intel- microcode due to intel-microcode still not fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911893 Title: latest microcode is not working properly on intel core i9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1911893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911893] Re: latest microcode is not working properly on intel core i9
Just downloaded latest LTS here - https://ubuntu.com/download/desktop /thank-you?version=20.04.2.0=amd64. I thought that iso img should also with latest intel-microcode but as I can see it is not like that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911893 Title: latest microcode is not working properly on intel core i9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1911893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911893] Re: latest microcode is not working properly on intel core i9
In any case still not fixed intel-microcode. https://github.com/intel /Intel-Linux-Processor-Microcode-Data-Files/issues/50 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911893 Title: latest microcode is not working properly on intel core i9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1911893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911893] Re: latest microcode is not working properly on intel core i9
If it is available in all ubuntu releases then why I can see in Ubuntu 20.04.2.0 LTS intel-microcode3.20201110.0ubuntu0.20.04.2? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911893 Title: latest microcode is not working properly on intel core i9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1911893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911893] Re: latest microcode is not working properly on intel core i9
Hello Finally I have got email about new intel microcode release - https://github.com/intel/Intel-Linux-Processor-Microcode-Data- Files/releases/tag/microcode-20210608. Can somebody update live usb with latest microcode and I will test it with intel core i9? With hope Thanks in Advance -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911893 Title: latest microcode is not working properly on intel core i9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1911893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1776013] Re: systemd-networkd: DHCP lease lost (Ubuntu 18.04)
To fix it with cloud-init we need to create an override-file for netplan like this: /etc/netplan/99-critical-dhcp.yaml network: version: 2 ethernets: ens2: dhcp4: true critical: true -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1776013 Title: systemd-networkd: DHCP lease lost (Ubuntu 18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1776013/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858810] Re: [19.10] Boot hangs at "loading initial ramdisk"
there is a lot issues with intel microcode package and it seems like nobody don't want properly support it - https://bugs.launchpad.net/ubuntu/+source/intel- microcode/+bug/1911893?comments=all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858810 Title: [19.10] Boot hangs at "loading initial ramdisk" To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1858810/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911893] Re: latest microcode is not working properly on intel core i9
Hello What we can do if still no response from intel on github. Maybe it is not supporting anymore. https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/50 It is pity :) ** Bug watch added: github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues #50 https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/50 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911893 Title: latest microcode is not working properly on intel core i9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1911893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902293] Re: fixed_network_name still exists in drivers except heat
I've reported bug to magnum https://storyboard.openstack.org/#!/story/2008596 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902293 Title: fixed_network_name still exists in drivers except heat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/magnum/+bug/1902293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902293] Re: fixed_network_name still exists in drivers except heat
fedora-coreos worked for me as well. That totally sounds like magnum bug... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902293 Title: fixed_network_name still exists in drivers except heat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/magnum/+bug/1902293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909843] Re: high CPU usage when running nothing
Also I'd suggest joining #openstack-ansible IRC channel on Freenode for futher community help with solving out this issue ** Changed in: openstack-ansible Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909843 Title: high CPU usage when running nothing To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ansible/+bug/1909843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909843] Re: high CPU usage when running nothing
In case it's openstack-ansible, I'd suggest decreasing amount of workers you're using since they may cause high load in small systems. ie for CI we're using https://opendev.org/openstack/openstack- ansible/src/branch/master/tests/roles/bootstrap- host/templates/user_variables.aio.yml.j2#L50-L176 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909843 Title: high CPU usage when running nothing To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ansible/+bug/1909843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909843] Re: high CPU usage when running nothing
I'm not sure it's realted to openstack-ansible, at least according to screenshot, since we support lxd at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909843 Title: high CPU usage when running nothing To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ansible/+bug/1909843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911893] Re: latest microcode is not working properly on intel core i9
Al BIOS version is here - https://rog.asus.com/laptops/rog- series/rog-g703-series/helpdesk_bios/. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911893 Title: latest microcode is not working properly on intel core i9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1911893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911893] Re: latest microcode is not working properly on intel core i9
I'm using latest BIOS version for my notebook. Also as mentioned above 3.20191115.1ubuntu3_amd64.deb is working properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911893 Title: latest microcode is not working properly on intel core i9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1911893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911893] Re: latest microcode is not working properly on intel code i9
More details can be found here - https://forums.linuxmint.com/viewtopic.php?f=49=339625 ** Summary changed: - latest microcode is not working properly on intel code i9 + latest microcode is not working properly on intel core i9 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911893 Title: latest microcode is not working properly on intel core i9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1911893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911893] [NEW] latest microcode is not working properly on intel core i9
Public bug reported: When using latest ubuntu LTS I can see black screen. Latest working version 3.20191115.1ubuntu3. Please fix the bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: intel-microcode 3.20200609.0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 10:13:34 2021 LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: intel-microcode UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: intel-microcode (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911893 Title: latest microcode is not working properly on intel core i9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1911893/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900701] [NEW] Keyboard layout does not switch in Citrix Workspace
Public bug reported: Usecase: On VDI (VMware vSphere) installed Ubuntu 18.04.4 LTS (Bionic Beaver). Switching between layouts works correctly through the vSphere console. But if I switch layout through the Citrix Workspace it doesnt's work. 1) The "lsb_release -rd" result is: Description:Ubuntu 18.04.4 LTS Release:18.04 2) - 3) I'm expecting to switch the layout to Russian 4) Layout still in us ** Affects: ubuntu Importance: Undecided Status: New ** Tags: citrix layout -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900701 Title: Keyboard layout does not switch in Citrix Workspace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1900701/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1741247] Re: Upgrade from Ocata fails with timeout
** Changed in: openstack-ansible 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/1741247 Title: Upgrade from Ocata fails with timeout To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ansible/+bug/1741247/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1850439] Re: No sound on ASUS UX534FT
Helped this first 2 commands from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/comments/170 But after reboot, sound doesn't work again -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1850439 Title: No sound on ASUS UX534FT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881874] Re: Unable to launch Loadbalancer from Horizon Dashboard
This is now merged to the stable train and will be released with upcoming 20.1.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881874 Title: Unable to launch Loadbalancer from Horizon Dashboard To manage notifications about this bug go to: https://bugs.launchpad.net/openstack-ansible/+bug/1881874/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1881319] Re: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel)
I also have a Lenovo IdeaPad 5 15ARE05 with no touchpad working, but xinput list shows "GTCH7503:00 2A94:D64D" with no mention of Elan at all. I installed Linux Mint. I tried 15 different solutions and none of them worked. Please advised. Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1881319 Title: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867372] Re: Auditd failed when changing the Rsyslog configuration
After many experiments, I discovered an inconspicuous syntax error in audit.rules Here are two seemingly identical lines: -a exit,always -F arch=b64 -F euid=0 -S execve –k root_actions -a exit,always -F arch=b64 -F euid=0 -S execve -k root_actions Their only difference is that in the first line (copy-pasted from another source), the dash before "–k" is not the standard dash character, although it appears exactly the same in the console. When changing to a standard dash, the mentioned error is "error in line 6 of /etc/audit/audit.rules" was eliminated. I absolutely don`t understand the role of Rsyslog configuration changes in this. But paradoxically, this error in the dash character only manifests itself in this case. Before that, a string with a non-standard dash in audit.rules was accepted by auditd without problems on both my servers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867372 Title: Auditd failed when changing the Rsyslog configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1867372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867372] [NEW] Auditd failed when changing the Rsyslog configuration
Public bug reported: I found that when changing the Rsyslog configuration (/etc/rsyslog.d/50-default.conf) an Auditd failure occurs with distinctive strings in syslog: ExecStartPost=/sbin/augenrules --load (code=exited, status=1/FAILURE) . There was an error in line 6 of /etc/audit/audit.rules Other sign: # systemctl status auditd ● auditd.service - Security Auditing Service Loaded: loaded (/lib/systemd/system/auditd.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2020-03-13 17:49:55 MSK; 12min ago Docs: man:auditd(8) https://github.com/linux-audit/audit-documentation Process: 985 ExecStartPost=/sbin/augenrules --load (code=exited, status=1/FAILURE) Process: 883 ExecStart=/sbin/auditd (code=exited, status=0/SUCCESS) Main PID: 928 (auditd) Tasks: 4 (limit: 4915) CGroup: /system.slice/auditd.service ├─928 /sbin/auditd └─932 /sbin/audispd The problem was confirmed on two modern physical Linux Ubuntu servers with all the latest system updates. Ubuntu 18.04.4 LTS (GNU/Linux 4.15.0-88-generic x86_64) --- auditd/bionic,now 1:2.8.2-1ubuntu1 amd64 [installed] libaudit-common/bionic,bionic,now 1:2.8.2-1ubuntu1 all [installed] libaudit1/bionic,now 1:2.8.2-1ubuntu1 amd64 [installed] + rsyslog/bionic,now 8.32.0-1ubuntu4 amd64 [installed,automatic] The first time I found a problem trying to reconfigure Auditd logging according to the recommendations: https://serverfault.com/questions/792766/what-is-the-syslog-facility-for-auditd-logs When I found the problem, I checked its causes on the Rsyslog side on another server. It is confirmed that it is not associated with changes in the configuration of Auditd. Example of replication: --- 1. Edit /etc/rsyslog.d/50-default.conf Insert strings for new log facility: *.*;auth,authpriv.none,cron.none,mail.none,local5.none,local6.none -/var/log/syslog ### ###*.*;auth,authpriv.none,cron.none,mail.none,local5.none -/var/log/syslog local6.*/var/log/audit/audit_syslog.log 2. # systemctl restart rsyslog 3. # systemctl restart auditd 4. # systemctl status auditd ● auditd.service - Security Auditing Service Loaded: loaded (/lib/systemd/system/auditd.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2020-03-13 18:12:32 MSK; 6s ago Docs: man:auditd(8) https://github.com/linux-audit/audit-documentation Process: 3211 ExecStartPost=/sbin/augenrules --load (code=exited, status=1/FAILURE) Process: 3183 ExecStart=/sbin/auditd (code=exited, status=0/SUCCESS) Main PID: 3186 (auditd) Tasks: 4 (limit: 4915) CGroup: /system.slice/auditd.service ├─3186 /sbin/auditd └─3190 /sbin/audispd Mar 13 18:12:32 uk1 augenrules[3211]: failure 1 Mar 13 18:12:32 uk1 augenrules[3211]: pid 3186 Mar 13 18:12:32 uk1 augenrules[3211]: rate_limit 0 Mar 13 18:12:32 uk1 augenrules[3211]: backlog_limit 8192 Mar 13 18:12:32 uk1 augenrules[3211]: lost 0 Mar 13 18:12:32 uk1 augenrules[3211]: backlog 0 Mar 13 18:12:32 uk1 augenrules[3211]: backlog_wait_time 0 Mar 13 18:12:32 uk1 systemd[1]: Started Security Auditing Service. Mar 13 18:12:32 uk1 auditctl[3225]: There was an error in line 6 of /etc/audit/audit.rules Mar 13 18:12:32 uk1 audispd[3190]: node=uk1 type=SERVICE_START msg=audit(1584112352.783:142): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=auditd comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' But the main problem is that this failure cannot be fixed by deleting changes from the Rsyslog configuration file. It remains even after restarting the server! I have attached snippets of the system log. The first part corresponds to restarting the system after rolling back Rsyslog changes. The second part corresponds to the processes after the Auditd restart. In General, it looks like Auditd is working normally. Logs show its working status. But in the system status auditd is issued: ExecStartPost=/sbin/augenrules --load (code=exited, status=1/FAILURE) And this cannot be eliminated. ** Affects: audit (Ubuntu) Importance: Undecided Status: New ** Tags: augenrules rsyslog ** Attachment added: "Logs and configs" https://bugs.launchpad.net/bugs/1867372/+attachment/5336591/+files/auditd+rsyslog_bug.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867372 Title: Auditd failed when changing the Rsyslog configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audit/+bug/1867372/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827822] Re: kernel null pointer dereference
[Wed Feb 5 20:09:17 2020] vfio-pci :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [Wed Feb 5 20:09:17 2020] BUG: kernel NULL pointer dereference, address: 0008 [Wed Feb 5 20:09:17 2020] #PF: supervisor write access in kernel mode [Wed Feb 5 20:09:17 2020] #PF: error_code(0x0002) - not-present page [Wed Feb 5 20:09:17 2020] PGD 0 P4D 0 [Wed Feb 5 20:09:17 2020] Oops: 0002 [#1] SMP NOPTI [Wed Feb 5 20:09:17 2020] CPU: 3 PID: 3306 Comm: tee Not tainted 5.3.0-28-generic #30~18.04.1-Ubuntu [Wed Feb 5 20:09:17 2020] Hardware name: System manufacturer System Product Name/PRIME H310T, BIOS 2602 07/24/2019 [Wed Feb 5 20:09:17 2020] RIP: 0010:mutex_lock+0x1d/0x40 [Wed Feb 5 20:09:17 2020] Code: 5d c3 90 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 55 48 89 e5 53 48 89 fb e8 9e e6 ff ff 65 48 8b 14 25 c0 6b 01 00 31 c0 48 0f b1 13 75 03 5b 5d c3 48 89 df e8 b1 ff ff ff 5b 5d c3 0f [Wed Feb 5 20:09:17 2020] RSP: 0018:9d4a42817d38 EFLAGS: 00010246 [Wed Feb 5 20:09:17 2020] RAX: RBX: 0008 RCX: [Wed Feb 5 20:09:17 2020] RDX: 8cd6d8f6da00 RSI: RDI: 0008 [Wed Feb 5 20:09:17 2020] RBP: 9d4a42817d40 R08: 8cd6dbc036c0 R09: 8cd6dbc03718 [Wed Feb 5 20:09:17 2020] R10: R11: 8285d518 R12: [Wed Feb 5 20:09:17 2020] R13: c05b R14: 9d4a42817ee8 R15: fff2 [Wed Feb 5 20:09:17 2020] FS: 7f32cfe5f540() GS:8cd6ddd8() knlGS: [Wed Feb 5 20:09:17 2020] CS: 0010 DS: ES: CR0: 80050033 [Wed Feb 5 20:09:17 2020] CR2: 0008 CR3: 000458984003 CR4: 003626e0 [Wed Feb 5 20:09:17 2020] Call Trace: [Wed Feb 5 20:09:17 2020] snd_sof_ipc_free+0x20/0x40 [snd_sof] [Wed Feb 5 20:09:17 2020] snd_sof_device_remove+0x33/0xa0 [snd_sof] [Wed Feb 5 20:09:17 2020] sof_pci_remove+0x19/0x30 [sof_pci_dev] [Wed Feb 5 20:09:17 2020] pci_device_remove+0x3e/0xc0 [Wed Feb 5 20:09:17 2020] device_release_driver_internal+0xe0/0x1b0 [Wed Feb 5 20:09:17 2020] device_driver_detach+0x14/0x20 [Wed Feb 5 20:09:17 2020] unbind_store+0xd1/0x130 [Wed Feb 5 20:09:17 2020] drv_attr_store+0x27/0x40 [Wed Feb 5 20:09:17 2020] sysfs_kf_write+0x3c/0x50 [Wed Feb 5 20:09:17 2020] kernfs_fop_write+0x125/0x1a0 [Wed Feb 5 20:09:17 2020] __vfs_write+0x1b/0x40 [Wed Feb 5 20:09:17 2020] vfs_write+0xb1/0x1a0 [Wed Feb 5 20:09:17 2020] ksys_write+0xa7/0xe0 [Wed Feb 5 20:09:17 2020] __x64_sys_write+0x1a/0x20 [Wed Feb 5 20:09:17 2020] do_syscall_64+0x5a/0x130 [Wed Feb 5 20:09:17 2020] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Wed Feb 5 20:09:17 2020] RIP: 0033:0x7f32cf963154 [Wed Feb 5 20:09:17 2020] Code: 89 02 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 8d 05 b1 07 2e 00 8b 00 85 c0 75 13 b8 01 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 54 f3 c3 66 90 41 54 55 49 89 d4 53 48 89 f5 [Wed Feb 5 20:09:17 2020] RSP: 002b:7ffeacffedb8 EFLAGS: 0246 ORIG_RAX: 0001 [Wed Feb 5 20:09:17 2020] RAX: ffda RBX: 000d RCX: 7f32cf963154 [Wed Feb 5 20:09:17 2020] RDX: 000d RSI: 7ffeacffeea0 RDI: 0003 [Wed Feb 5 20:09:17 2020] RBP: 7ffeacffeea0 R08: 000d R09: 7f32cfe5f540 [Wed Feb 5 20:09:17 2020] R10: 01b6 R11: 0246 R12: 55781994c460 [Wed Feb 5 20:09:17 2020] R13: 000d R14: 7f32cfc3a760 R15: 000d [Wed Feb 5 20:09:17 2020] Modules linked in: vhost_net vhost tap xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 xt_tcpudp ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bpfilter vfio_pci vfio_virqfd vfio_iommu_type1 vfio bridge stp llc intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel mei_hdcp sof_pci_dev snd_sof_intel_hda_common snd_sof_intel_hda nls_iso8859_1 snd_sof_intel_byt aesni_intel snd_sof_intel_ipc snd_sof aes_x86_64 crypto_simd cryptd glue_helper intel_cstate snd_sof_xtensa_dsp snd_soc_skl intel_rapl_perf snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi snd_hda_codec snd_hda_core eeepc_wmi asus_wmi sparse_keymap wmi_bmof snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine btusb snd_usb_audio btrtl snd_usbmidi_lib btbcm snd_hwdep btintel snd_rawmidi bluetooth snd_seq_device snd_pcm uvcvideo [Wed Feb 5 20:09:17 2020] videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_timer videobuf2_common ecdh_generic ecc snd cdc_acm soundcore videodev mei_me mc mei ie31200_edac mac_hid acpi_tad acpi_pad sch_fq_codel coretemp ip_tables x_tables autofs4 r8169 ahci realtek libahci wmi video [Wed Feb 5 20:09:17 2020] CR2: 0008 [Wed Feb 5 20:09:17 2020] ---[ end trace
[Bug 1861251] Re: 'extended_part_no' referenced before assignment error during install
Vinorcola, sorry for late reply - you could just try to install Ubuntu with old hard drive switched off, I made so for recent installation on another server where faced same bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861251 Title: 'extended_part_no' referenced before assignment error during install To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1861251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861251] Re: 'extended_part_no' referenced before assignment error during install
Attached content of /var/log/installer/block ** Attachment added: "var_log_installer_block.tar.gz" https://bugs.launchpad.net/curtin/+bug/1861251/+attachment/5324366/+files/var_log_installer_block.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861251 Title: 'extended_part_no' referenced before assignment error during install To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1861251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861251] Re: 'extended_part_no' referenced before assignment error during install
Actually I've got around this problem by deleting sda5 which was small swap partition and successfully installed system (after tweaking system datetime cause without Internet access datetime on server was Jan 2018 and installer complained on invalid Ubuntu certificate and failed). But I was able to reproduce problem on VirtualBox. Here is steps to do it: 1. Create virtual machine with two disks - on first (20 GB for example) create msdos partition table (I used gparted from ubuntu-19.10-desktop-amd64.iso) with 1 primary partition (I've created 18.5 GB ext4, it will be sda1) and 1 extended partition (sda2) consisting of 1 logical partition (e.g. 1.5 GB swap, sda5), second leave as is (sdb, I've created 10 GB disk). 2. Load VM from ubuntu-18.04.3-live-server-amd64.iso, pass to disk selection, select entire disk and choose second one (sdb, without partitions), apply (settings should looke like this https://ibb.co/YZBSMvR), curtin will start to work and will fail just like on our physical server (https://ibb.co/4f4rJRY, https://ibb.co/nfQ8S0z). Attached /var/log/installer/subiquity-curtin-install.conf as Ryan Harper have asked. ** Attachment added: "subiquity-curtin-install.conf" https://bugs.launchpad.net/curtin/+bug/1861251/+attachment/5324077/+files/subiquity-curtin-install.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861251 Title: 'extended_part_no' referenced before assignment error during install To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1861251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1101647] Re: ID 138a:003d Validity Sensors, Inc.
Agree, nothing changed untill now -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1101647 Title: ID 138a:003d Validity Sensors, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1101647/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851562] [NEW] Kubuntu 18.04 installer crashes after Disk Setup
Public bug reported: Traceback (most recent call last): File "/usr/lib/ubiquity/ubiquity/frontend/kde_components/PartitionModel.py", line 66, in setData item.partman_column_format_toggled(value.toBool()) AttributeError: 'int' object has no attribute 'toBool' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.12 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: KDE Date: Wed Nov 6 20:09:54 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed boot=casper maybe-ubiquity quiet splash --- LiveMediaBuild: Kubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic kubuntu ubiquity-18.04.14.12 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851562 Title: Kubuntu 18.04 installer crashes after Disk Setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1851562/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837314] Re: My english very bad. I don't know what need say
i don't know why "architecture is AMD64" because i haven't AMD processor or videocard. What's problem? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837314 Title: My english very bad. I don't know what need say To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1837314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837314] [NEW] My english very bad. I don't know what need say
Public bug reported: I don't know what happened. Just problem. It's my first install Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.14.12 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 21 12:51:34 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: LANGUAGE=ru_RU.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubiquity-18.04.14.12 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1837314 Title: My english very bad. I don't know what need say To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1837314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1286910] Re: Lock screen uses last active window's language instead of default keyboard language
Still got this issue on ubuntu 18.04 . 22nd of April, 2019 extremely irritates issue raised on 2014 for how long would it be unfixed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1286910 Title: Lock screen uses last active window's language instead of default keyboard language To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1286910/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1388770] Re: Keyboard layouts switch with delay
*** This bug is a duplicate of bug 1370953 *** https://bugs.launchpad.net/bugs/1370953 Did you find resolve it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1388770 Title: Keyboard layouts switch with delay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1388770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1501206] Re: router:dhcp ports are open resolvers
Probably this bugfix is worth backporting at least to rocky? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1501206 Title: router:dhcp ports are open resolvers To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1501206/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804762] Re: libomp5 packaging problem: *.so are in -dev package
Ok, I got it. In my case error was thrown by libmkl_intel_thread.so, it dlopen() libiomp5.so. This thread describes the reason: https://software.intel.com/en-us/forums/intel-math-kernel-library/topic/402497 So I chose the wrong package, must be libmkl-rt. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804762 Title: libomp5 packaging problem: *.so are in -dev package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openmprtl/+bug/1804762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804762] Re: libomp5 packaging problem: *.so are in -dev package
Hi! This doesn't really matter. I'm building dlib (http://dlib.net/) with Intel MKL libraries. One of them loads libiomp5.so dynamically and that causes "undefined symbol" error. Real reason or error -- wrong packaging. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804762 Title: libomp5 packaging problem: *.so are in -dev package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openmprtl/+bug/1804762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1804762] [NEW] libomp5 packaging problem: *.so are in -dev package
Public bug reported: Recently I built a library with Intel MKL as a dependency (libmkl-dev package). Trying to run an application threw me an error message: "undefined symbol: omp_get_num_procs". The problem turned up to be old and known (https://software.intel.com/en-us/forums/intel-system- studio/topic/611682) -- missing libiomp5.so. Examining dependencies of libmkl-dev leads to chain: libmkl-dev -> libmkl-rt -> libomp5 which must contain libiomp5.so. The last one depends only on libc6. But package libomp5 only contains documentation, not the library: $ apt-file show libomp5 libomp5: /usr/lib/x86_64-linux-gnu/libomp.so.5 libomp5: /usr/share/doc/libomp5/changelog.Debian.gz libomp5: /usr/share/doc/libomp5/copyright libomp5: /usr/share/lintian/overrides/libomp5 All libraries are packed into libomp-dev: $ apt-file show libomp-dev libomp-dev: /usr/include/omp.h libomp-dev: /usr/include/ompt.h libomp-dev: /usr/lib/x86_64-linux-gnu/libgomp.so libomp-dev: /usr/lib/x86_64-linux-gnu/libiomp5.so libomp-dev: /usr/lib/x86_64-linux-gnu/libomp.so libomp-dev: /usr/lib/x86_64-linux-gnu/libomptarget.so libomp-dev: /usr/share/doc/libomp-dev/changelog.Debian.gz libomp-dev: /usr/share/doc/libomp-dev/copyright ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libomp5 6.0.1-1build1 Uname: Linux 4.18.19-041819-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Nov 23 13:04:04 2018 Dependencies: gcc-8-base 8.2.0-7ubuntu1 libc6 2.28-0ubuntu1 libgcc1 1:8.2.0-7ubuntu1 libidn2-0 2.0.5-1 libunistring2 0.9.10-1ubuntu1 InstallationDate: Installed on 2018-03-27 (240 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) SourcePackage: openmprtl UpgradeStatus: Upgraded to cosmic on 2018-10-19 (34 days ago) ** Affects: openmprtl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1804762 Title: libomp5 packaging problem: *.so are in -dev package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openmprtl/+bug/1804762/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803849] Re: libgl1-mesa-dri:i386 can not be installed
WTF??? Does this mean you want to get rid of the problem without solving it? There is definitely a dependency problem either in libgl1-mesa-dri:i386 or in libllvm7:i386. == $ apt policy Package files: 100 /var/lib/dpkg/status release a=now 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/main i386 Packages release v=18.10,o=Ubuntu,a=cosmic-proposed,n=cosmic,l=Ubuntu,c=main,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 Packages release v=18.10,o=Ubuntu,a=cosmic-proposed,n=cosmic,l=Ubuntu,c=main,b=amd64 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/multiverse i386 Packages release v=18.10,o=Ubuntu,a=cosmic-proposed,n=cosmic,l=Ubuntu,c=multiverse,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/multiverse amd64 Packages release v=18.10,o=Ubuntu,a=cosmic-proposed,n=cosmic,l=Ubuntu,c=multiverse,b=amd64 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/universe i386 Packages release v=18.10,o=Ubuntu,a=cosmic-proposed,n=cosmic,l=Ubuntu,c=universe,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-proposed/universe amd64 Packages release v=18.10,o=Ubuntu,a=cosmic-proposed,n=cosmic,l=Ubuntu,c=universe,b=amd64 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-security/multiverse i386 Packages release v=18.10,o=Ubuntu,a=cosmic-security,n=cosmic,l=Ubuntu,c=multiverse,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-security/multiverse amd64 Packages release v=18.10,o=Ubuntu,a=cosmic-security,n=cosmic,l=Ubuntu,c=multiverse,b=amd64 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-security/universe i386 Packages release v=18.10,o=Ubuntu,a=cosmic-security,n=cosmic,l=Ubuntu,c=universe,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-security/universe amd64 Packages release v=18.10,o=Ubuntu,a=cosmic-security,n=cosmic,l=Ubuntu,c=universe,b=amd64 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-security/main i386 Packages release v=18.10,o=Ubuntu,a=cosmic-security,n=cosmic,l=Ubuntu,c=main,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-security/main amd64 Packages release v=18.10,o=Ubuntu,a=cosmic-security,n=cosmic,l=Ubuntu,c=main,b=amd64 origin archive.ubuntu.com 500 http://archive.canonical.com/ubuntu cosmic/partner i386 Packages release v=18.10,o=Canonical,a=cosmic,n=cosmic,l=Partner archive,c=partner,b=i386 origin archive.canonical.com 500 http://archive.canonical.com/ubuntu cosmic/partner amd64 Packages release v=18.10,o=Canonical,a=cosmic,n=cosmic,l=Partner archive,c=partner,b=amd64 origin archive.canonical.com 500 http://archive.ubuntu.com/ubuntu cosmic-updates/multiverse i386 Packages release v=18.10,o=Ubuntu,a=cosmic-updates,n=cosmic,l=Ubuntu,c=multiverse,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-updates/multiverse amd64 Packages release v=18.10,o=Ubuntu,a=cosmic-updates,n=cosmic,l=Ubuntu,c=multiverse,b=amd64 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-updates/universe i386 Packages release v=18.10,o=Ubuntu,a=cosmic-updates,n=cosmic,l=Ubuntu,c=universe,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-updates/universe amd64 Packages release v=18.10,o=Ubuntu,a=cosmic-updates,n=cosmic,l=Ubuntu,c=universe,b=amd64 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-updates/main i386 Packages release v=18.10,o=Ubuntu,a=cosmic-updates,n=cosmic,l=Ubuntu,c=main,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages release v=18.10,o=Ubuntu,a=cosmic-updates,n=cosmic,l=Ubuntu,c=main,b=amd64 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic/multiverse i386 Packages release v=18.10,o=Ubuntu,a=cosmic,n=cosmic,l=Ubuntu,c=multiverse,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic/multiverse amd64 Packages release v=18.10,o=Ubuntu,a=cosmic,n=cosmic,l=Ubuntu,c=multiverse,b=amd64 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic/universe i386 Packages release v=18.10,o=Ubuntu,a=cosmic,n=cosmic,l=Ubuntu,c=universe,b=i386 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages release v=18.10,o=Ubuntu,a=cosmic,n=cosmic,l=Ubuntu,c=universe,b=amd64 origin archive.ubuntu.com 500 http://archive.ubuntu.com/ubuntu cosmic/restricted i386 Packages release
[Bug 1751517] Re: ubuntu bionic grub can't boot zstd compressed filesystem
Results (using btrfs-compsize tool): $ sudo compsize /boot/ /bin/ /usr/ Processed 240794 files, 88025 regular extents (89183 refs), 162022 inline. Type Perc Disk Usage Uncompressed Referenced TOTAL 50% 2.7G 5.3G 5.4G none 100% 1.1G 1.1G 1.1G lzo 46% 9.1M 19M 19M zstd37% 1.5G 4.1G 4.2G -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751517 Title: ubuntu bionic grub can't boot zstd compressed filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1751517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751517] Re: ubuntu bionic grub can't boot zstd compressed filesystem
Seems that btrfs ignores compression attribute if compression was set using mount option. So, the solution is to set compression attributes per-directory: 1) remove 'compress=zstd' from your fstab root record 2) sudo btrfs property set /boot compression lzo # ensure this dir will remain readable by grub 3) sudo btrfs filesystem defragment -vrclzo /boot # ensure /boot gets recompressed 4) for $d in bin etc lib lib64 opt sbin snap srv usr var; do sudo btrfs property set /$d compression zstd; done Directory list is for Ubuntu 18, check and adjust for your own needs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751517 Title: ubuntu bionic grub can't boot zstd compressed filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1751517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803853] [NEW] gedit git plugin crashes on local git repository
Public bug reported: I get the following output in console: dmig@dmig-Inspiron-5379:~$ gedit workspace/howdy-test.py Traceback (most recent call last): File "/usr/lib/x86_64-linux-gnu/gedit/plugins/git/appactivatable.py", line 89, in get_repository repo = self.__git_repos[repo_uri] KeyError: 'file:///home/dmig/workspace/form-observer/.git' During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/x86_64-linux-gnu/gedit/plugins/git/windowactivatable.py", line 298, in inserted repo = self.get_repository(location, msg.is_directory) File "/usr/lib/x86_64-linux-gnu/gedit/plugins/git/windowactivatable.py", line 282, in get_repository return self.app_activatable.get_repository(location, is_dir) File "/usr/lib/x86_64-linux-gnu/gedit/plugins/git/appactivatable.py", line 95, in get_repository head = repo.get_head() gi.repository.GLib.Error: ggit-error: reference 'refs/heads/master' not found (-9) The reason is simple ~/workspace/form-observer/ is a local-only repository, it has no remotes. But it is weird for me, why this plugin scan subdirectories? ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gedit-plugin-git 3.30.1-2 Uname: Linux 4.19.2-041902-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 18 12:18:27 2018 InstallationDate: Installed on 2018-03-27 (235 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) SourcePackage: gedit-plugins UpgradeStatus: Upgraded to cosmic on 2018-10-19 (29 days ago) ** Affects: gedit-plugins (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803853 Title: gedit git plugin crashes on local git repository To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit-plugins/+bug/1803853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803849] [NEW] libgl1-mesa-dri:i386 can not be installed
Public bug reported: Steam client tries to install a set of i386 libraries. One of them is libgl1-mesa-dri:i386. But since upgrade to Ubuntu 18.10 this package got broken dependency and thus installation fails. >The following packages have unmet dependencies: > libgl1-mesa-dri:i386 : Depends: libllvm7:i386 (>= 1:7~svn298832-1~) but it is > not going to be installed ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libgl1-mesa-dri:i386 (not installed) Uname: Linux 4.19.2-041902-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Nov 18 09:54:04 2018 DistUpgraded: 2018-10-19 13:34:56,068 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: exfat, 1.2.10, 4.18.0-11-generic, x86_64: installed exfat, 1.2.10, 4.18.0-12-generic, x86_64: installed exfat, 1.2.10, 4.19.1-041901-generic, x86_64: installed exfat, 1.2.10, 4.19.2-041902-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0804] InstallationDate: Installed on 2018-03-27 (235 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: Dell Inc. Inspiron 5379 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.19.2-041902-generic root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: mesa UpgradeStatus: Upgraded to cosmic on 2018-10-19 (29 days ago) dmi.bios.date: 07/19/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.product.sku: 0804 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803849 Title: libgl1-mesa-dri:i386 can not be installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1803849/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1751517] Re: ubuntu bionic grub can't boot zstd compressed filesystem
The simplest workaround for the moment: sudo btrfs property set /boot compression lzo # ensure this dir will remain readable by grub sudo btrfs filesystem defragment -vr /boot # ensure /boot gets recompressed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1751517 Title: ubuntu bionic grub can't boot zstd compressed filesystem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1751517/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697229] Re: GNOME extensions deactivated after lock unlock
Started experiencing this bug after Ubuntu update 18.04->18.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697229 Title: GNOME extensions deactivated after lock unlock To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1697229/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1789781] [NEW] package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1
Public bug reported: start sistem ProblemType: Package DistroRelease: Ubuntu 16.04 Package: initramfs-tools 0.122ubuntu8.11 ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Tue Aug 28 10:44:36 2018 ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 InstallationDate: Installed on 2018-02-07 (203 days ago) InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: initramfs-tools Title: package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (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/1789781 Title: package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1789781/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1783516] [NEW] Upgrade from 14.04 to 16.04 issue
Public bug reported: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.5 LTS Release:16.04 Codename: xenial $ cat /var/log/installer/media-info Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Some problems with update from 14.04 to 16.04 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:0.220.10 ProcVersionSignature: Ubuntu 3.13.0-153.203-generic 3.13.11-ckt39 Uname: Linux 3.13.0-153-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Wed Jul 25 11:48:50 2018 InstallationDate: Installed on 2015-02-05 (1266 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to xenial on 2018-07-23 (1 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1783516 Title: Upgrade from 14.04 to 16.04 issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1783516/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779777] Re: Wifi Broadcom Limited BCM43142 dont working 4.15.0-24
Apparently you mean a popritarian driver? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779777 Title: Wifi Broadcom Limited BCM43142 dont working 4.15.0-24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779777] Re: Wifi Broadcom Limited BCM43142 dont working 4.15.0-24
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779777 Title: Wifi Broadcom Limited BCM43142 dont working 4.15.0-24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779777] Re: Wifi Broadcom Limited BCM43142 dont working 4.15.0-24
kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779777 Title: Wifi Broadcom Limited BCM43142 dont working 4.15.0-24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779777] Re: Wifi Broadcom Limited BCM43142 dont working 4.15.0-24
The problem occurred after the kernel was automatically updated to version 4.16. This is not the first time when the kernel is updated, and I tried to reinstall bcmwl-kernel-sourse. It did not help, I tried other recipes on the net, but they also did not help. On the previous kernels 4.15 4.13 everything worked, after updating and attempts to restore the work of the wifi, work only on version 4.4 of my installed. With versions of the system above 4.16 there are complications they are not correctly installed due to the lack of the libssl1.1 module, with its installation there are problems. The driver, on reinstallation, produces errors that can not be installed and there is no WL module help me please -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779777 Title: Wifi Broadcom Limited BCM43142 dont working 4.15.0-24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779777] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1779777/+attachment/5158981/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779777 Title: Wifi Broadcom Limited BCM43142 dont working 4.15.0-24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779777] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1779777/+attachment/5158982/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779777 Title: Wifi Broadcom Limited BCM43142 dont working 4.15.0-24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779777] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1779777/+attachment/5158979/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779777 Title: Wifi Broadcom Limited BCM43142 dont working 4.15.0-24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779777] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1779777/+attachment/5158980/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779777 Title: Wifi Broadcom Limited BCM43142 dont working 4.15.0-24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779777] Re: Wifi Broadcom Limited BCM43142 dont working 4.15.0-24
apport information ** Tags added: apport-collected xenial ** Description changed: bcmwl-kernel-source reinstall Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-130-generic/updates/dkms/ depmod DKMS: install completed. Building initial module for 4.15.0-24-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bcmwl-kernel-source.0.crash' Error! Bad return status for module build on kernel: 4.15.0-24-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/make.log for more information. update-initramfs: deferring update (trigger activated) Обрабатываются триггеры для initramfs-tools (0.122ubuntu8.11) … update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic + --- + ApportVersion: 2.20.1-0ubuntu2.18 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: koyot 2253 F pulseaudio + /dev/snd/controlC0: koyot 2253 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=ea4730dd-6bdc-4245-9aef-e549591c72c6 + InstallationDate: Installed on 2017-11-22 (222 days ago) + InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) + IwConfig: + enp4s0no wireless extensions. + + lono wireless extensions. + MachineType: Hewlett-Packard HP 15 Notebook PC + Package: linux (not installed) + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=7061dbfa-fff5-4781-a257-9761d42e9c5c ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-24-generic N/A + linux-backports-modules-4.15.0-24-generic N/A + linux-firmware 1.157.18 + RfKill: + 0: hci0: Bluetooth + Soft blocked: yes + Hard blocked: no + Tags: xenial + Uname: Linux 4.15.0-24-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers + _MarkForUpload: True + dmi.bios.date: 12/23/2014 + dmi.bios.vendor: Insyde + dmi.bios.version: F.33 + dmi.board.asset.tag: Base Board Asset Tag + dmi.board.name: 21F7 + dmi.board.vendor: Hewlett-Packard + dmi.board.version: 52.3A + dmi.chassis.asset.tag: Chassis Asset Tag + dmi.chassis.type: 10 + dmi.chassis.vendor: Hewlett-Packard + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnInsyde:bvrF.33:bd12/23/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr098E121600087:rvnHewlett-Packard:rn21F7:rvr52.3A:cvnHewlett-Packard:ct10:cvrChassisVersion: + dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV + dmi.product.name: HP 15 Notebook PC + dmi.product.version: 098E121600087 + dmi.sys.vendor: Hewlett-Packard ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1779777/+attachment/5158970/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779777 Title: Wifi Broadcom Limited BCM43142 dont working 4.15.0-24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779777] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1779777/+attachment/5158977/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779777 Title: Wifi Broadcom Limited BCM43142 dont working 4.15.0-24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779777] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1779777/+attachment/5158973/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779777 Title: Wifi Broadcom Limited BCM43142 dont working 4.15.0-24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779777] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1779777/+attachment/5158976/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779777 Title: Wifi Broadcom Limited BCM43142 dont working 4.15.0-24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779777] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1779777/+attachment/5158978/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779777 Title: Wifi Broadcom Limited BCM43142 dont working 4.15.0-24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779777] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1779777/+attachment/5158974/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779777 Title: Wifi Broadcom Limited BCM43142 dont working 4.15.0-24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779777] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1779777/+attachment/5158975/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779777 Title: Wifi Broadcom Limited BCM43142 dont working 4.15.0-24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779777] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1779777/+attachment/5158971/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779777 Title: Wifi Broadcom Limited BCM43142 dont working 4.15.0-24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779777] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1779777/+attachment/5158972/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779777 Title: Wifi Broadcom Limited BCM43142 dont working 4.15.0-24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779777] [NEW] Wifi Broadcom Limited BCM43142 dont working 4.15.0-24
Public bug reported: bcmwl-kernel-source reinstall Running module version sanity check. - Original module - Installation - Installing to /lib/modules/4.4.0-130-generic/updates/dkms/ depmod DKMS: install completed. Building initial module for 4.15.0-24-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/bcmwl-kernel-source.0.crash' Error! Bad return status for module build on kernel: 4.15.0-24-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/make.log for more information. update-initramfs: deferring update (trigger activated) Обрабатываются триггеры для initramfs-tools (0.122ubuntu8.11) … update-initramfs: Generating /boot/initrd.img-4.15.0-24-generic ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779777 Title: Wifi Broadcom Limited BCM43142 dont working 4.15.0-24 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779777/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773973] Re: Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting with 4.15.0-22-generic kernel.
Short comparison -
Ubuntu 18.04 LTS LIVECD - kernel version Ubuntu 4.15.0-20.21-generic
4.15.17 - boots fine, without current issue errors
Ubuntu 18.04 LTS NetInstall - kernel version Ubuntu 4.15.0-22.24-generic
4.15.17 - has errors in console log like metioned above in this issue
("Bad kernel stack pointer", stack_trace with fast_exception_return,
etc.).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773973
Title:
Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting
with 4.15.0-22-generic kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1773973/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1773973] Re: Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting with 4.15.0-22-generic kernel.
That's may be interesting to this ticket. If one use Ubuntu LIVECD which has linux kernel version 4.15.0-20.21-generic 4.15.17, than the current issue boot errors doesn't appear in console log and operating system boots fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1773973 Title: Ubuntu 18.04 [ Garrison P8 ]: Machine crashes with oops while booting with 4.15.0-22-generic kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1773973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769297] Re: resume from hibernation broken when resume image is autodetected
How to check you have this issue: 1) get provided resume script, replace /usr/share/initramfs-tools/scripts/local-premount/resume with it 2) sudo update-initramfs -k $(uname -r) -u 3) sudo systemctl hibernate 4) edit grub menu entry, add 'debug' parameter to kernel command line, boot 5) look into /run/initramfs/initramfs.debug, if you see following lines, you have this issue: + /scripts/local-premount/resume Success: Resume device: 'UUID=106238b0-707d-4422-866d-a7534da50702' () Failure: Failed to get /sys/class/block//dev major/minor ** Attachment added: "resume script with extra debug messages" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769297/+attachment/5134182/+files/resume -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769297 Title: resume from hibernation broken when resume image is autodetected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769297] Re: resume from hibernation broken when resume image is autodetected
Here is a fix for this bug. This makes hibernation functional for me. ** Patch added: "init.patch" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769297/+attachment/5134187/+files/init.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769297 Title: resume from hibernation broken when resume image is autodetected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769297] Re: resume from hibernation broken when resume image is autodetected
This bug is actually a regression. I remember hibernation was functional around a year ago in ubuntu 17.04 with any kernel, but at some point it became broken. Probably in 17.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769297 Title: resume from hibernation broken when resume image is autodetected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769297/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1769297] [NEW] resume from hibernation broken when resume image is autodetected
Public bug reported:
I found a reason of non-functioning resume from hibernation when resume
partition/file is autodetected by intiramfs hook /usr/share/initramfs-
tools/hooks/resume.
Here is the scenario:
1) hook /usr/share/initramfs-tools/hooks/resume creates config
conf/conf.d/zz-resume-auto saved in initrd image, containing one variable:
RESUME=UUID=106238b0-707d-4422-866d-a7534da50702 in my case
2) during boot init script sets 'resume' variable to 'RESUME' value from
conf/conf.d/zz-resume-auto, then it executes local-premount scripts
including local-premount/resume
3) resuming script local-premount/resume
(/usr/share/initramfs-tools/scripts/local-premount/resume) tries to get resume
device major-minor numbers by these lines:
DEV=$(readlink ${resume})
DEV=/sys/class/block/${DEV##*/}/dev
if [ -r "$DEV" ]; then
read MAJMIN < "$DEV"
fi
4) next check fails and resume process silently aborts:
if [ -z "$MAJMIN" ]; then
exit 1
fi
Resuming script fails to get device major-minor because
resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- it's not resolved
into device path in init script.
Commonly mentioned workaround is to explicitly specify kernel parameter
resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- only in this case
init script resolves it to device path.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3
Uname: Linux 4.16.6-041606-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat May 5 11:32:31 2018
InstallationDate: Installed on 2018-03-27 (38 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
PackageArchitecture: all
SourcePackage: initramfs-tools
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
** Description changed:
I found a reason of non-functioning resume from hibernation when resume
partition/file is autodetected by intiramfs hook /usr/share/initramfs-
tools/hooks/resume.
Here is the scenario:
1) hook /usr/share/initramfs-tools/hooks/resume creates config
conf/conf.d/zz-resume-auto saved in initrd image, containing one variable:
RESUME=UUID=106238b0-707d-4422-866d-a7534da50702 in my case
- 2) when resuming script local-premount/resume
(/usr/share/initramfs-tools/scripts/local-premount/resume) tries to get resume
device major-minor numbers by these lines:
+ 2) resuming script local-premount/resume
(/usr/share/initramfs-tools/scripts/local-premount/resume) tries to get resume
device major-minor numbers by these lines:
DEV=$(readlink ${resume})
DEV=/sys/class/block/${DEV##*/}/dev
if [ -r "$DEV" ]; then
- read MAJMIN < "$DEV"
+ read MAJMIN < "$DEV"
fi
- 3) then next check fails and resume process silently aborts:
+ 3) next check fails and resume process silently aborts:
if [ -z "$MAJMIN" ]; then
- exit 1
+ exit 1
fi
-
- Resuming script fails to get device major-minor because
resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- it's not resolved into
device path in init script.
+ Resuming script fails to get device major-minor because
+ resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- it's not resolved
+ into device path in init script.
Commonly mentioned workaround is to explicitly specify kernel parameter
resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- only in this case
init script resolves it to device path.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3
Uname: Linux 4.16.6-041606-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat May 5 11:32:31 2018
InstallationDate: Installed on 2018-03-27 (38 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
PackageArchitecture: all
SourcePackage: initramfs-tools
UpgradeStatus: No upgrade log present (probably fresh install)
** Description changed:
I found a reason of non-functioning resume from hibernation when resume
partition/file is autodetected by intiramfs hook /usr/share/initramfs-
tools/hooks/resume.
Here is the scenario:
1) hook /usr/share/initramfs-tools/hooks/resume creates config
conf/conf.d/zz-resume-auto saved in initrd image, containing one variable:
RESUME=UUID=106238b0-707d-4422-866d-a7534da50702 in my case
- 2) resuming script local-premount/resume
(/usr/share/initramfs-tools/scripts/local-premount/resume) tries to get resume
device major-minor numbers by these lines:
+ 2) during boot init script sets 'resume' variable to 'RESUME' value from
+ conf/conf.d/zz-resume-auto, then it executes local-premount scripts
+ including local-premount/resume
+
+ 3) resuming script local-premount/resume
(/usr/share/initramfs-tools/scripts/local-premount/resume) tries to get resume
device major-minor
[Bug 1762382] Re: scan code → meaning map
Confirmation by other person https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762385/comments/8 ** Changed in: systemd (Ubuntu) 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/1762382 Title: scan code → meaning map To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1762382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762385] Re: dell_wmi: Unknown key codes
Enough guessing. Gnome bug is a different one. And it has no connection to this bug. In my case rfkill didn't work because keycode 88 was set to UNKNOWN by this generic dell rule: https://github.com/systemd/systemd/blob/c5896b6a8cfcfd1b94f25450a96a1411384f1108/hwdb/60-keyboard.hwdb#L267 My rule https://github.com/systemd/systemd/blob/c5896b6a8cfcfd1b94f25450a96a1411384f1108/hwdb/60-keyboard.hwdb#L303-L305 was accepted and it is a correct solution, because it refines key code for exact model. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762385 Title: dell_wmi: Unknown key codes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762385] Re: dell_wmi: Unknown key codes
Rfkill key produces 2 events: keyboard and one, that should be handled by dell-wmi. Hwdb record is for keyboard event. Release emulation is required, at least for my model. Otherwise evtest shows only 1 EV_KEY event. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762385 Title: dell_wmi: Unknown key codes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762385] Re: dell_wmi: Unknown key codes
I found one more missing key definition: FN-Lock key - Lock icon with 'Fn' on it, it toggles Fn row behavior between F1-F12 and media keys. I'm not sure with keycode it should have assigned, so I set it to IGNORE in patch. ** Summary changed: - dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed + dell_wmi: Unknown key codes ** Patch added: "This is a patch to dell-wmi.c kernel module adding 2 new key definitions" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762385/+attachment/5117689/+files/dell-wmi.c.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762385 Title: dell_wmi: Unknown key codes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762382] Re: scan code → meaning map
Until systemd gets updated, following file can be used. Put it to /etc/udev/hwdb.d ** Attachment added: "my-rfkill.hwdb" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1762382/+attachment/5116245/+files/my-rfkill.hwdb -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762382 Title: scan code → meaning map To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1762382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762382] Re: scan code → meaning map
Pull request merged upstream: https://github.com/systemd/systemd/pull/8715 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762382 Title: scan code → meaning map To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1762382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763588] Re: package trousers 0.3.14+fixed1-1build1 failed to install/upgrade: installed trousers package post-installation script subprocess returned error exit status 1
Donal don't write such silly things. This patch is intended to fix that behavior. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763588 Title: package trousers 0.3.14+fixed1-1build1 failed to install/upgrade: installed trousers package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/trousers/+bug/1763588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763588] Re: package trousers 0.3.14+fixed1-1build1 failed to install/upgrade: installed trousers package post-installation script subprocess returned error exit status 1
This fixes script error: Apr 13 13:27:13 dmig-Inspiron-5379 trousers[18286]: /etc/init.d/trousers: 32: [: /dev/tpm0: unexpected operator ** Patch added: "fix-check.patch" https://bugs.launchpad.net/ubuntu/+source/trousers/+bug/1763588/+attachment/5113365/+files/fix-check.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763588 Title: package trousers 0.3.14+fixed1-1build1 failed to install/upgrade: installed trousers package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/trousers/+bug/1763588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763588] [NEW] package trousers 0.3.14+fixed1-1build1 failed to install/upgrade: installed trousers package post-installation script subprocess returned error exit status 1
Public bug reported: Here is piece of install log: Setting up trousers (0.3.14+fixed1-1build1) ... Job for trousers.service failed because the control process exited with error code. See "systemctl status trousers.service" and "journalctl -xe" for details. invoke-rc.d: initscript trousers, action "start" failed. ● trousers.service - LSB: starts tcsd Loaded: loaded (/etc/init.d/trousers; generated) Active: failed (Result: exit-code) since Fri 2018-04-13 13:18:00 +07; 4ms ago Docs: man:systemd-sysv-generator(8) Process: 10997 ExecStart=/etc/init.d/trousers start (code=exited, status=30) Apr 13 13:18:00 dmig-Inspiron-5379 trousers[10997]: * Starting Trusted Computing daemon tcsd Apr 13 13:18:00 dmig-Inspiron-5379 trousers[10997]: /etc/init.d/trousers: 32: [: /dev/tpm0: unexpected operator Apr 13 13:18:00 dmig-Inspiron-5379 trousers[10997]: * TPM device owner for /dev/tpmrm0 is not 'tss', this can cause problems. Apr 13 13:18:00 dmig-Inspiron-5379 tcsd[11006]: TCSD TDDL[11006]: TrouSerS ioctl: (25) Inappropriate ioctl for device Apr 13 13:18:00 dmig-Inspiron-5379 tcsd[11006]: TCSD TDDL[11006]: TrouSerS Falling back to Read/Write device support. Apr 13 13:18:00 dmig-Inspiron-5379 tcsd[11006]: TCSD TCS[11006]: TrouSerS ERROR: TCS GetCapability failed with result = 0x1e Apr 13 13:18:00 dmig-Inspiron-5379 trousers[10997]:...fail! Apr 13 13:18:00 dmig-Inspiron-5379 systemd[1]: trousers.service: Control process exited, code=exited status=30 Apr 13 13:18:00 dmig-Inspiron-5379 systemd[1]: trousers.service: Failed with result 'exit-code'. Apr 13 13:18:00 dmig-Inspiron-5379 systemd[1]: Failed to start LSB: starts tcsd. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: trousers 0.3.14+fixed1-1build1 Uname: Linux 4.16.2-041602-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 Date: Fri Apr 13 13:17:20 2018 ErrorMessage: installed trousers package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2018-03-27 (16 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~beta1 SourcePackage: trousers Title: package trousers 0.3.14+fixed1-1build1 failed to install/upgrade: installed trousers package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: trousers (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763588 Title: package trousers 0.3.14+fixed1-1build1 failed to install/upgrade: installed trousers package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/trousers/+bug/1763588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763584] [NEW] ureadahead service fails with error Error while tracing: No such file or directory
Public bug reported: I'm reporting this as duplicate of #1176536 to provide more info. dmig@dmig-Inspiron-5379:~$ systemctl status ureadahead.service ● ureadahead.service - Read required files in advance Loaded: loaded (/lib/systemd/system/ureadahead.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2018-04-13 13:09:41 +07; 10min ago Main PID: 379 (code=exited, status=5) Apr 13 13:09:41 dmig-Inspiron-5379 ureadahead[379]: ureadahead: Error while tracing: No such file or directory Apr 13 13:09:41 dmig-Inspiron-5379 ureadahead[379]: Counted 8 CPUs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ureadahead 0.100.0-20 Uname: Linux 4.16.2-041602-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 13 13:13:26 2018 InstallationDate: Installed on 2018-03-27 (16 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) SourcePackage: ureadahead UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ureadahead (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/1763584 Title: ureadahead service fails with error Error while tracing: No such file or directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1763584/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762385] Re: dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed
According to
https://github.com/torvalds/linux/blob/master/drivers/platform/x86/dell-wmi.c
this key isn't supported by kernel.
To add support record { KE_IGNORE, 0xe008, { KEY_RFKILL } } must be added to
array dell_wmi_keymap_type_0010. Right now it exists only in
dell_wmi_keymap_type_.
Here is a piece of kern.log on mainline kernel 4.16.2:
Apr 13 12:35:07 dmig-Inspiron-5379 kernel: [ 1597.752396]dell_wmi: Unknown key
with type 0x0010 and code 0xe008 pressed
Apr 13 12:35:07 dmig-Inspiron-5379 kernel: [
1598.160367]dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed
Apr 13 12:35:08
dmig-Inspiron-5379 kernel: [ 1598.461929]dell_wmi: Unknown key with type 0x0010
and code 0xe008 pressed
Apr 13 12:35:08 dmig-Inspiron-5379 kernel: [ 1598.731117]dell_wmi:
Unknown key with type 0x0010 and code 0xe008 pressed
Apr 13 12:35:08 dmig-Inspiron-5379
kernel: [ 1598.990486]dell_wmi: Unknown key with type 0x0010 and code 0xe008
pressed
Apr 13 12:35:09 dmig-Inspiron-5379 kernel: [ 1599.287094]dell_wmi: Unknown key
with type 0x0010 and code 0xe008 pressed
Apr 13 12:35:09 dmig-Inspiron-5379 kernel: [
1599.556158]dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed
Apr 13 12:35:09
dmig-Inspiron-5379 kernel: [ 1599.812597]dell_wmi: Unknown key with type 0x0010
and code 0xe008 pressed
Apr 13 12:35:09 dmig-Inspiron-5379 kernel: [ 1600.109678]dell_wmi:
Unknown key with type 0x0010 and code 0xe008 pressed
Apr 13 12:35:10 dmig-Inspiron-5379
kernel: [ 1600.373923]dell_wmi: Unknown key with type 0x0010 and code 0xe008
pressed
Apr 13 12:35:10 dmig-Inspiron-5379 kernel: [ 1600.650719]dell_wmi: Unknown key
with type 0x0010 and code 0xe008 pressed
Apr 13 12:35:10 dmig-Inspiron-5379 kernel: [
1600.900744]dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed
Apr 13 12:35:10
dmig-Inspiron-5379 kernel: [ 1601.149327]dell_wmi: Unknown key with type 0x0010
and code 0xe008 pressed
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1762385
Title:
dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762385/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763578] [NEW] gpu-manager syslog reported errors
Public bug reported: syslog contains following error messages: Apr 13 10:31:36 dmig-Inspiron-5379 gpu-manager[858]: /etc/modprobe.d is not a file Apr 13 10:31:36 dmig-Inspiron-5379 gpu-manager[858]: Error: can't open /lib/modules/4.15.0-15-generic/updates/dkms Apr 13 10:31:36 dmig-Inspiron-5379 gpu-manager[858]: Error: can't open /lib/modules/4.15.0-15-generic/updates/dkms None of them represent a real error, gpu-manager shouldn't complain about this ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-drivers-common 1:0.5 Uname: Linux 4.16.2-041602-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 13 12:36:47 2018 InstallationDate: Installed on 2018-03-27 (16 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) SourcePackage: ubuntu-drivers-common UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-drivers-common (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/1763578 Title: gpu-manager syslog reported errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1763578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763577] [NEW] failed to load modules crypto and mdraid
Public bug reported: udisks daemon complains about loading libbd_crypto and libbd_mdraid, but seems to work fine. I fixed the issue by manually installing packages libblockdev-crypto2 and libblockdev-mdraid2. udisks should depend on these packages or doesn't complain about missing libraries. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udisks2 2.7.6-2ubuntu6 Uname: Linux 4.16.2-041602-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 70-snap.spotify.rules Date: Fri Apr 13 12:22:11 2018 InstallationDate: Installed on 2018-03-27 (16 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: Dell Inc. Inspiron 5379 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.16.2-041602-generic root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet splash vt.handoff=1 SourcePackage: udisks2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. ** Affects: udisks2 (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/1763577 Title: failed to load modules crypto and mdraid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1763577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1763577] Re: failed to load modules crypto and mdraid
** Attachment added: "console output showing problem and solution" https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1763577/+attachment/5113324/+files/console.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1763577 Title: failed to load modules crypto and mdraid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1763577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762382] Re: scan code → meaning map
Looks like, this key is supported by systemd, but for another model: https://github.com/systemd/systemd/blob/master/hwdb/60-keyboard.hwdb#L321 So, new DMI match string should be added -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762382 Title: scan code → meaning map To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1762382/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762385] [NEW] dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed
Public bug reported: RFKill key produces these messages in kernel log: dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed This key code is a notification and should be added as KEY_IGNORE here: https://github.com/torvalds/linux/blob/master/drivers/platform/x86/dell- wmi.c#L263 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-generic 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmig 2737 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 18:09:03 2018 InstallationDate: Installed on 2018-03-27 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: Dell Inc. Inspiron 5379 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic package-from-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762385 Title: dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
