[Bug 1852911] Re: CriticalPowerAction=Suspend should be supported
I would like to add my voice here and say that a patch, either to upstream UPower or to Ubuntu's version would be much appreciated. I've lost work several times as neither HybridSleep nor Hibernate work on my laptop so it simply shuts down, and due to a quirk of the batter management the delay between the notification of low % and then the critical threshold and shutdown is often only mere seconds. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852911 Title: CriticalPowerAction=Suspend should be supported To manage notifications about this bug go to: https://bugs.launchpad.net/upower/+bug/1852911/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875274] Re: usrmerge breaks perf symbol lookup
This is still broken in 20.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875274 Title: usrmerge breaks perf symbol lookup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885973] Re: user-data not being run on 20.04 ARM Graviton 2 instances
Here's the cloud-init archive as requested. This is without sudo (running the command exactly as requested). Next I'll attach a sudo one. ** Attachment added: "output of cloud-init collect-logs" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1885973/+attachment/5390022/+files/cloud-init.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/1885973 Title: user-data not being run on 20.04 ARM Graviton 2 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1885973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885973] Re: user-data not being run on 20.04 ARM Graviton 2 instances
Here's the output of sudo cloud-init collect-logs ** Attachment added: "output of sudo cloud-init collect-logs" https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1885973/+attachment/5390023/+files/cloud-init-sudo.tar.gz ** Changed in: cloud-init (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885973 Title: user-data not being run on 20.04 ARM Graviton 2 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1885973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885973] Re: user-data not being run on 20.04 ARM Graviton 2 instances
The linked duplicate: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1885974 has additional log files from the same machine (obtained from running apport again with sudo). ** Description changed: Start a 20.04 ARM instance using the Canonical provided 20.04 AMI (ubuntu-focal-20.04-arm64-server-20200609 (ami-091fa45b154a839b0)), and provide any script as user-data in Instance Details. For example, this script: #!/bin/bash /bin/echo "zzz running cloud init" /bin/echo hello > /tmp/hello /bin/echo hello > ~/hello - Start the instances. The script should run, but it does not. The - /tmp/hello file is not created. The /var/log/cloud-init-output.log does - not indicate the script has run (the "zzz running..." output does not - appear). The cloud-init.log indicates that many parts of the init that - run on other AMIs are not being run: it stops at init-network: + Start the instance with any Graviton 2 instance type, like c6g.medium. + The script should run, but it does not. The /tmp/hello file is not + created. The /var/log/cloud-init-output.log does not indicate the script + has run (the "zzz running..." output does not appear). The cloud- + init.log indicates that many parts of the init that run on other AMIs + are not being run: it stops at init-network: - $ tail /var/log/cloud-init.log + $ tail /var/log/cloud-init.log 2020-07-02 01:19:42,417 - util.py[DEBUG]: Read 3287 bytes from /etc/ssh/sshd_config 2020-07-02 01:19:42,417 - util.py[DEBUG]: Writing to /root/.ssh/authorized_keys - wb: [600] 541 bytes 2020-07-02 01:19:42,417 - util.py[DEBUG]: Changing the ownership of /root/.ssh/authorized_keys to 0:0 2020-07-02 01:19:42,417 - handlers.py[DEBUG]: finish: init-network/config-ssh: SUCCESS: config-ssh ran successfully 2020-07-02 01:19:42,417 - main.py[DEBUG]: Ran 15 modules with 0 failures 2020-07-02 01:19:42,418 - atomic_helper.py[DEBUG]: Atomically writing to file /var/lib/cloud/data/status.json (via temporary file /var/lib/cloud/data/tmpe9uo7rsu) - w: [644] 518 bytes/chars 2020-07-02 01:19:42,418 - util.py[DEBUG]: Reading from /proc/uptime (quiet=False) 2020-07-02 01:19:42,418 - util.py[DEBUG]: Read 10 bytes from /proc/uptime 2020-07-02 01:19:42,418 - util.py[DEBUG]: cloud-init mode 'init' took 0.828 seconds (0.83) 2020-07-02 01:19:42,418 - handlers.py[DEBUG]: finish: init-network: SUCCESS: searching for network datasources - $ wc -l /var/log/cloud-init.log + $ wc -l /var/log/cloud-init.log 712 /var/log/cloud-init.log Only 712 lines vs 930 on 18.04. This problem does not occur on 20.04 x86 AMI, or 18.04 ARM AMI, it seems to be specific to 20.04 ARM. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cloud-init 20.1-10-g71af48df-0ubuntu5 ProcVersionSignature: User Name 5.4.0-1015.15-aws 5.4.41 Uname: Linux 5.4.0-1015-aws aarch64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: arm64 CasperMD5CheckResult: skip CloudName: Amazon - Ec2 Date: Thu Jul 2 01:31:27 2020 Ec2AMI: ami-091fa45b154a839b0 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2d Ec2InstanceType: m6g.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) logs.tgz: Error: [Errno 2] No such file or directory: '/tmp/cloud-init-logs.tgz' user_data.txt: Error: [Errno 13] Permission denied: '/var/lib/cloud/instance/user-data.txt' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885973 Title: user-data not being run on 20.04 ARM Graviton 2 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1885973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885974] [NEW] Details for 1885973
*** This bug is a duplicate of bug 1885973 *** https://bugs.launchpad.net/bugs/1885973 Public bug reported: This bug has additional files for: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1885973 ... because I ran `ubuntu-bug` with sudo this time so various files that couldn't be accessed before were uploaded. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cloud-init 20.1-10-g71af48df-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-1015.15-aws 5.4.41 Uname: Linux 5.4.0-1015-aws aarch64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: arm64 CasperMD5CheckResult: skip CloudName: Amazon - Ec2 Date: Thu Jul 2 01:41:42 2020 Ec2AMI: ami-091fa45b154a839b0 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2d Ec2InstanceType: m6g.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) cloud-init-log-warnings: 2020-07-02 01:19:38,255 - DataSourceEc2.py[DEBUG]: strict_mode: warn, cloud_name=aws cloud_platform=ec2 user_data.txt: #!/bin/bash /bin/echo "zzz running cloud init" /bin/echo hello > /tmp/hello /bin/echo hello > ~/hello ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 ec2-images focal ** This bug has been marked a duplicate of bug 1885973 user-data not being run on 20.04 ARM Graviton 2 instances -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885974 Title: Details for 1885973 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1885974/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1885973] [NEW] user-data not being run on 20.04 ARM Graviton 2 instances
Public bug reported: Start a 20.04 ARM instance using the Canonical provided 20.04 AMI (ubuntu-focal-20.04-arm64-server-20200609 (ami-091fa45b154a839b0)), and provide any script as user-data in Instance Details. For example, this script: #!/bin/bash /bin/echo "zzz running cloud init" /bin/echo hello > /tmp/hello /bin/echo hello > ~/hello Start the instances. The script should run, but it does not. The /tmp/hello file is not created. The /var/log/cloud-init-output.log does not indicate the script has run (the "zzz running..." output does not appear). The cloud-init.log indicates that many parts of the init that run on other AMIs are not being run: it stops at init-network: $ tail /var/log/cloud-init.log 2020-07-02 01:19:42,417 - util.py[DEBUG]: Read 3287 bytes from /etc/ssh/sshd_config 2020-07-02 01:19:42,417 - util.py[DEBUG]: Writing to /root/.ssh/authorized_keys - wb: [600] 541 bytes 2020-07-02 01:19:42,417 - util.py[DEBUG]: Changing the ownership of /root/.ssh/authorized_keys to 0:0 2020-07-02 01:19:42,417 - handlers.py[DEBUG]: finish: init-network/config-ssh: SUCCESS: config-ssh ran successfully 2020-07-02 01:19:42,417 - main.py[DEBUG]: Ran 15 modules with 0 failures 2020-07-02 01:19:42,418 - atomic_helper.py[DEBUG]: Atomically writing to file /var/lib/cloud/data/status.json (via temporary file /var/lib/cloud/data/tmpe9uo7rsu) - w: [644] 518 bytes/chars 2020-07-02 01:19:42,418 - util.py[DEBUG]: Reading from /proc/uptime (quiet=False) 2020-07-02 01:19:42,418 - util.py[DEBUG]: Read 10 bytes from /proc/uptime 2020-07-02 01:19:42,418 - util.py[DEBUG]: cloud-init mode 'init' took 0.828 seconds (0.83) 2020-07-02 01:19:42,418 - handlers.py[DEBUG]: finish: init-network: SUCCESS: searching for network datasources $ wc -l /var/log/cloud-init.log 712 /var/log/cloud-init.log Only 712 lines vs 930 on 18.04. This problem does not occur on 20.04 x86 AMI, or 18.04 ARM AMI, it seems to be specific to 20.04 ARM. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cloud-init 20.1-10-g71af48df-0ubuntu5 ProcVersionSignature: User Name 5.4.0-1015.15-aws 5.4.41 Uname: Linux 5.4.0-1015-aws aarch64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: arm64 CasperMD5CheckResult: skip CloudName: Amazon - Ec2 Date: Thu Jul 2 01:31:27 2020 Ec2AMI: ami-091fa45b154a839b0 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2d Ec2InstanceType: m6g.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) logs.tgz: Error: [Errno 2] No such file or directory: '/tmp/cloud-init-logs.tgz' user_data.txt: Error: [Errno 13] Permission denied: '/var/lib/cloud/instance/user-data.txt' ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 ec2-images focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885973 Title: user-data not being run on 20.04 ARM Graviton 2 instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1885973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1839237] Re: snapd disk write usage very high on 19.04 with snapd 2.39.3
I am suffering the same issue. snapd writing at 2 MB/s for almost 5 straight days. I have poor internet connectivity. Most of the time network monitor shows zero network activity, so snap is not "actually" downloading anything. $snap changes ID Status Spawn Ready Summary 54 Doing today at 10:35 -04 - Auto-refresh snap "chromium" $ sudo fnotifystat Total Open Close Read Write PID Process Pathname 55.0 18.0 18.0 19.00.0 13786 snapd /var/lib/snapd/assertions/asserts-v0/model/16/generic/generic-classic 54.0 18.0 18.0 18.00.0 13786 snapd /var/lib/snapd/assertions/asserts-v0/model/16/generic/generic-classic/active 54.0 18.0 18.0 18.00.0 13786 snapd /var/lib/snapd/assertions/asserts-v0/serial/generic/generic-classic/d4eca5b4-8c2b-4ec1-a6b2-4ed7a8e76fbe 54.0 18.0 18.0 18.00.0 13786 snapd /var/lib/snapd/assertions/asserts-v0/serial/generic/generic-classic/d4eca5b4-8c2b-4ec1-a6b2-4ed7a8e76fbe/active 36.0 18.0 18.00.00.0 13786 snapd /var/lib/snapd 26.00.0 13.00.0 13.0 13786 snapd /var/lib/snapd/state.json 4.01.01.00.02.0 13786 snapd /var/lib/snapd/state.json.8s9NlHqn9hgk~ 4.01.01.00.02.0 13786 snapd /var/lib/snapd/state.json.9K7JVycntjF2~ 4.01.01.00.02.0 13786 snapd /var/lib/snapd/state.json.DQF0MS3WKj05~ 4.01.01.00.02.0 13786 snapd /var/lib/snapd/state.json.Llsbh5NnGHgK~ 4.01.01.00.02.0 13786 snapd /var/lib/snapd/state.json.hkfJT9N0htBG~ 2.01.00.00.01.0 13786 snapd /var/lib/snapd/state.json.4XgMb38QNtrW~ 2.01.00.00.01.0 13786 snapd /var/lib/snapd/state.json.6vHSRf3xbRS5~ 2.01.00.00.01.0 13786 snapd /var/lib/snapd/state.json.FwlhlyDlFXLp~ 2.01.00.00.01.0 13786 snapd /var/lib/snapd/state.json.G64fgNkBmr2x~ 2.01.00.00.01.0 13786 snapd /var/lib/snapd/state.json.Kp061JNgygDv~ 2.01.00.00.01.0 13786 snapd /var/lib/snapd/state.json.PQ5byShcJ5Ym~ 2.01.00.00.01.0 13786 snapd /var/lib/snapd/state.json.Q6PC97T8x9rm~ 2.01.00.00.01.0 13786 snapd /var/lib/snapd/state.json.RWkVcKbtsGw4~ 2.01.00.00.01.0 13786 snapd /var/lib/snapd/state.json.Wr5BSmHwg0k1~ 2.01.00.00.01.0 13786 snapd /var/lib/snapd/state.json.brJjjjMnyrmB~ 2.01.00.00.01.0 13786 snapd /var/lib/snapd/state.json.cbv2dSN9YH8r~ 2.01.00.00.01.0 13786 snapd /var/lib/snapd/state.json.pPjJXh9CQRG6~ 2.01.00.00.01.0 13786 snapd /var/lib/snapd/state.json.rwSwHlQ95nv7~ This is chewing up my SSD and my last SSD failed at only 10% write life used, so it is a real concern for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1839237 Title: snapd disk write usage very high on 19.04 with snapd 2.39.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1839237/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875274] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1875274/+attachment/5362130/+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/1875274 Title: usrmerge breaks perf symbol lookup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875274] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1875274/+attachment/5362132/+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/1875274 Title: usrmerge breaks perf symbol lookup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875274] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1875274/+attachment/5362131/+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/1875274 Title: usrmerge breaks perf symbol lookup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875274] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1875274/+attachment/5362134/+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/1875274 Title: usrmerge breaks perf symbol lookup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875274] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1875274/+attachment/5362135/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875274 Title: usrmerge breaks perf symbol lookup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875274] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1875274/+attachment/5362136/+files/UdevDb.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/1875274 Title: usrmerge breaks perf symbol lookup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875274] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1875274/+attachment/5362137/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875274 Title: usrmerge breaks perf symbol lookup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875274] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1875274/+attachment/5362133/+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/1875274 Title: usrmerge breaks perf symbol lookup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875274] Re: usrmerge breaks perf symbol lookup
apport information ** Tags added: apport-collected eoan ** Description changed: In 19.10, perf cannot find the symbols for libc even after installing libc-dbg. The symbols for libc are in: /usr/lib/debug/lib/x86_64-linux-gnu/ but libc is in: /usr/lib/x86_64-linux-gnu/ so applications expect to find the corresponding symbols at: /usr/lib/debug/usr/lib/x86_64-linux-gnu/ + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8.8 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: tdowns 1637 F pulseaudio + /dev/snd/pcmC1D0p: tdowns 1637 F...m pulseaudio + /dev/snd/controlC0: tdowns 1637 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.10 + InstallationDate: Installed on 2020-02-14 (73 days ago) + InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) + MachineType: Dell Inc. XPS 15 9550 + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=0a6fd287-c693-42a9-baa6-d90a59e83b42 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-45-generic N/A + linux-backports-modules-5.3.0-45-generic N/A + linux-firmware1.183.5 + Tags: eoan + Uname: Linux 5.3.0-45-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 12/12/2019 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.13.1 + dmi.board.name: 0N7TVV + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 9 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: + dmi.product.family: XPS + dmi.product.name: XPS 15 9550 + dmi.product.sku: 06E4 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1875274/+attachment/5362123/+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/1875274 Title: usrmerge breaks perf symbol lookup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875274] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1875274/+attachment/5362124/+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/1875274 Title: usrmerge breaks perf symbol lookup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875274] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1875274/+attachment/5362129/+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/1875274 Title: usrmerge breaks perf symbol lookup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875274] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1875274/+attachment/5362125/+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/1875274 Title: usrmerge breaks perf symbol lookup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875274] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1875274/+attachment/5362128/+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/1875274 Title: usrmerge breaks perf symbol lookup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875274] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1875274/+attachment/5362127/+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/1875274 Title: usrmerge breaks perf symbol lookup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875274] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1875274/+attachment/5362126/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875274 Title: usrmerge breaks perf symbol lookup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875274] Re: usrmerge breaks perf symbol lookup
This is the same issue as: https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/1808508 ... where the fix was to manually path the Valgrind debug info lookup path, but this doesn't seem feasible for every application that might care about symbols. Better to put the symbols in the right place or set up symlinks to ensure that is the case? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875274 Title: usrmerge breaks perf symbol lookup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875274] [NEW] usrmerge breaks perf symbol lookup
Public bug reported: In 19.10, perf cannot find the symbols for libc even after installing libc-dbg. The symbols for libc are in: /usr/lib/debug/lib/x86_64-linux-gnu/ but libc is in: /usr/lib/x86_64-linux-gnu/ so applications expect to find the corresponding symbols at: /usr/lib/debug/usr/lib/x86_64-linux-gnu/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Package changed: valgrind (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875274 Title: usrmerge breaks perf symbol lookup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875274/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808508] Re: Valgrind doesn't work in disco [Fatal error at startup: a function redirection which is mandatory for this platform-tool combination cannot be set up.]
> we can't think of anything besides gdb, valgrind, and libunwind that uses /usr/lib/debug That seems like quite an incredible statement! I can imagine that many debugging and profiling tools will want symbols. For example, this change is breaking perf right now, as it looks for say libc symbols in /usr/lib/debug/usr/lib/x86_64-linux-gnu/, but the symbols are actually in /usr/lib/debug/lib/x86_64-linux-gnu/. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808508 Title: Valgrind doesn't work in disco [Fatal error at startup: a function redirection which is mandatory for this platform-tool combination cannot be set up.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1808508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875213] [NEW] Internal NVMe SSD fails after soft reboot
Public bug reported:
I have a Dell 3000-series Insprion, with the stock 128 GB NVMe SSD. On a
cold boot, it boots fine, but any restart gives me errors in grub
("error: command not found") or drops me immediately to grub command
line where the SSD is not accessible.
Manual power off (or choosing shutdown rather than restart) and power on
and it works fine.
I believe this is a problem with NVMe power management. If I add:
nvme_core.default_ps_max_latency_us=0
to the boot parameters, the problem stops.
I have tried other Inspirons of the same model and the same problem
occurs. There are a series of similar problems with other Dell models
going back to 2015 at least, so perhaps there is a common cause.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: udisks2 2.8.4-1
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
Uname: Linux 5.3.0-46-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
CustomUdevRuleFiles: 70-snap.core.rules
Date: Sun Apr 26 13:13:24 2020
InstallationDate: Installed on 2019-12-26 (121 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD
Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 3493
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic
root=UUID=724b42e1-24f3-4728-96e3-b5bacac356b1 ro quiet splash
nvme_core.default_ps_max_latency_us=0 vt.handoff=7
SourcePackage: udisks2
Symptom: storage
Title: Internal hard disk partition cannot be mounted manually
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/26/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.0
dmi.board.name: 088RVF
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.2.0:bd09/26/2019:svnDellInc.:pnInspiron3493:pvr:rvnDellInc.:rn088RVF:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 3493
dmi.product.sku: 0978
dmi.sys.vendor: Dell Inc.
Here is the output of nvme ctrl-id in case that's useful:
$ sudo nvme id-ctrl /dev/nvme0
NVME Identify Controller:
vid : 0x15b7
ssvid : 0x15b7
sn: 193631800750
mn: PC SN520 NVMe WDC 128GB
fr: 20220012
rab : 4
ieee : 001b44
cmic : 0
mdts : 7
cntlid: 1
ver : 10300
rtd3r : 7a120
rtd3e : f4240
oaes : 0x200
ctratt: 0x2
rrls : 0
oacs : 0x17
acl : 4
aerl : 7
frmw : 0x14
lpa : 0x2
elpe : 255
npss : 4
avscc : 0x1
apsta : 0x1
wctemp: 355
cctemp: 359
mtfa : 50
hmpre : 0
hmmin : 0
tnvmcap : 128035676160
unvmcap : 0
rpmbs : 0
edstt : 16
dsto : 1
fwug : 1
kas : 0
hctma : 0x1
mntmt : 273
mxtmt : 359
sanicap : 0
hmminds : 0
hmmaxd: 0
nsetidmax : 0
anatt : 0
anacap: 0
anagrpmax : 0
nanagrpid : 0
sqes : 0x66
cqes : 0x44
maxcmd: 0
nn: 1
oncs : 0x1f
fuses : 0
fna : 0
vwc : 0x1
awun : 0
awupf : 0
nvscc : 1
nwpc : 0
acwu : 0
sgls : 0
mnan : 0
subnqn: nqn.2018-01.com.wdc:nguid:E8238FA6BF53-0001-001B448B442C2CD4
ioccsz: 0
iorcsz: 0
icdoff: 0
ctrattr : 0
msdbd : 0
ps0 : mp:2.50W operational enlat:0 exlat:0 rrt:0 rrl:0
rwt:0 rwl:0 idle_power:- active_power:-
ps1 : mp:2.50W operational enlat:0 exlat:0 rrt:1 rrl:1
rwt:1 rwl:1 idle_power:- active_power:-
ps2 : mp:1.70W operational enlat:0 exlat:0 rrt:2 rrl:2
rwt:2 rwl:2 idle_power:- active_power:-
ps3 : mp:0.0250W non-operational enlat:5000 exlat:9000 rrt:3 rrl:3
rwt:3 rwl:3 idle_power:- active_power:-
ps4 : mp:0.0025W non-operational enlat:5000 exlat:44000 rrt:4 rrl:4
rwt:4 rwl:4 idle_power:- active_power:-
** Affects: ubuntu
Importance: Undecided
Status: New
** Tags: amd64 apport-bug eoan
** Description changed:
I have a Dell 3000-series Insprion, with the stock 128 GB NVMe SSD. On a
cold boot, it boots fine, but any restart gives me errors in grub
("error: command not found") or drops me immediately to grub command
line where the SSD is not accessible.
- Manual power off and power on and it works find.
+ Manual power off (or choosing shutdown rather than restart) and power on
+ and it works fine.
I believe this is a problem with NVMe power management. If I add:
nvme_core.default_ps_max_latency_us=0
to the boot parameters, the problem stops.
I have tried other Inspirons of the same model and the same problem
occurs. There are a series of similar problems with other Dell models
going back to 2015 at least, so perhaps there
[Bug 1622571] Re: NetworkManager crashed with SIGSEGV in nm_dns_manager_end_updates()
I believe I'm also having this problem. I've uploaded the whoopsie dump with apport but I can't see where it is being tracked (see http://askubuntu.com/questions/900191/where-do-i-look-to-see-if-my- whoopsie-is-being-tracked). The stack looks the same: SegvAnalysis: Segfault happened at: 0x7fc79f90e830 <__libc_start_main+240>: mov%eax,%edi PC (0x7fc79f90e830) ok source "%eax" ok destination "%edi" ok SP (0x7ffc12fba2c0) ok Reason could not be automatically determined. SourcePackage: network-manager Stacktrace: #0 0x0048cc66 in nm_dns_manager_end_updates () #1 0x7fc79d566e40 in ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 #2 0x7fc79d5668ab in ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 #3 0x7fc7a01f5cf5 in g_cclosure_marshal_generic_va () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #4 0x7fc7a01f51d4 in ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #5 0x7fc7a020f9a6 in g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 #6 0x7fc7a021008f in g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 This started happening when I commented out the dns=dnsmasq line in my NetworkManager.conf and indeed the crash happens in DNS related code. The often occurs after resuming from suspend, but not always - it may also just occur while using the host. Here's a link to the whoopise upload - I don't have perms to see it, but perhaps someone who does can associate it with this bug? https://errors.ubuntu.com/oops/f3ce1fb0-1957-11e7-968c-fa163e8d4bab -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1622571 Title: NetworkManager crashed with SIGSEGV in nm_dns_manager_end_updates() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1622571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631241] Re: Name resolution stops working after resume from suspend
I just started seeing this recently in 16.04. I used the workaround suggested here: http://askubuntu.com/questions/837575/dns-resolution-fails-after-wakeup- from-standby-ubuntu-16-10 of commenting out the dnsmasq entry in /etc/NetworkManager/NetworkManager.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631241 Title: Name resolution stops working after resume from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/dnsmasq/+bug/1631241/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
