[Bug 1906729] [NEW] Suspend and hibernate work, but hybrid-suspend does not
Public bug reported: I have a Lenovo e585, if it's relevant. I'm running Ubuntu 20.04, and `systemd 245 (245.4-4ubuntu3.3)`. Suspend on my system doesn't wake up consistently, but hibernate does. Hybrid suspend would make an excellent fallback if wake fails. Since both work independently, they *should* work together. Happy to help debug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 3 16:58:44 2020 InstallationDate: Installed on 2020-05-06 (210 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20KVCTO1WW ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-56-generic root=UUID=17333443-bf13-4111-b659-028e71aff61a ro rootflags=subvol=@ resume=UUID=5d93ce37-7478-43d9-9564-618e60725242 quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: [MASKED] /etc/systemd/system/samba-ad-dc.service → /usr/lib/systemd/system/samba-ad-dc.service [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0UET74W (1.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0UET74W(1.54):bd07/23/2019:svnLENOVO:pn20KVCTO1WW:pvrThinkPadE585:rvnLENOVO:rn20KVCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E585 dmi.product.name: 20KVCTO1WW dmi.product.sku: LENOVO_MT_20KV_BU_Think_FM_ThinkPad E585 dmi.product.version: ThinkPad E585 dmi.sys.vendor: LENOVO mtime.conffile..etc.systemd.sleep.conf: 2020-12-03T16:22:33.696671 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session ** Description changed: I have a Lenovo e585, if it's relevant. I'm running Ubuntu 20.04, and `systemd 245 (245.4-4ubuntu3.3)`. - Suspend on my system doesn't wake up consistently, but hibernate does. Hybrid suspend would make an excellent fallback if wake fails. Since both work independently, they *should* work together. Happy to help debug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.3 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Dec 3 16:58:44 2020 InstallationDate: Installed on 2020-05-06 (210 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20KVCTO1WW ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-56-generic root=UUID=17333443-bf13-4111-b659-028e71aff61a ro rootflags=subvol=@ resume=UUID=5d93ce37-7478-43d9-9564-618e60725242 quiet splash vt.handoff=7 SourcePackage: systemd SystemdDelta: - [MASKED] /etc/systemd/system/samba-ad-dc.service → /usr/lib/systemd/system/samba-ad-dc.service - [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf - [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf - - 3 overridden configuration files found. + [MASKED] /etc/systemd/system/samba-ad-dc.service → /usr/lib/systemd/system/samba-ad-dc.service + [EXTENDED] /usr/lib/systemd/system/rc-local.service → /usr/lib/systemd/system/rc-local.service.d/debian.conf + [EXTENDED] /usr/lib/systemd/system/user@.service → /usr/lib/systemd/system/user@.service.d/timeout.conf + + 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0UET74W (1.54 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None
[Bug 1877785] [NEW] [bluetooth] Audio device reconnects after explicitly turning connection off
Public bug reported: I have a Logitech BT Adapter for playing audio. I am unable to (permanently) disconnect from the device without removing it. This is, presumably, the opposite problem to #1331642 (which exists for good reason). Since the device is paired, it auto-reconnects (which is good) instead of following preferences (which is bad). Current behavior: * If the device is paired, it connects. * Turning the connection off (without unpairing) causes the device to disconnect, then reconnect. Desired behavior (option 1, clean UI): * If I turn the connection off, it should stay off * If I turn it on, it should stay on * If (and only if) the connection has not been explicitly turned off, it should reconnect if not connected Desired behavior (option 2, fairly clean UI, plus configurability to avoid annoyance situations): * In the individual device dialog, devices would have a 'Reconnect Automatically' option, on by default, below the 'Connection' switch. * If I turn the connection off, it should stay off. * If I turn it on, it should attempt to connect. * If 'Reconnect automatically" is checked, and I have not explicitly turned the device off, it should consistently attempt to reconnect at the appropriate times as normal. Unpairing, in case that is suggested, is not a reasonable solution. This is a regularly used device (house bluetooth speakers) that takes intermittent use. This behavior is a regression from previous versions of Ubuntu (19.10 and earlier) which worked as described -- Switching the connection off stayed off until explicitly reconnected. ** Affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New ** Tags: bluetooth -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877785 Title: [bluetooth] Audio device reconnects after explicitly turning connection off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1877785/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825234] [NEW] Python3: After do-release-upgrade, all apt-installed modules need to be reinstalled, or they fail
Public bug reported: I was running 18.10, and used do-release-upgrade from the cli. It seemed to end successfully, and asked to reboot. Upon reboot, many/most python-related programs (apport, chrome-gnome- shell, ubuntu-bug) failed to work with `ModuleNotFoundError: No module named 'certifi'.`. I verified that the version being used was Python 3.7 (3.7.3), and that python3 pointed to that executable. After an `apt install --reinstall` for `certifi` and `idna`, critical things like apport are working. I don't know if the '--reinstall' was necessary, unfortunately. I'd fixed it before I determined that. I did "clear out obsolete packages" during the upgrade. My guess is that the requests lib (or some other package) is missing some dependencies, but I'm not sure. I'm not that familiar with the mechanics of debian packaging. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ubuntu-release-upgrader-core 1:19.04.16 Uname: Linux 5.0.8-050008-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: GNOME Date: Wed Apr 17 14:37:03 2019 InstallationDate: Installed on 2018-11-17 (150 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to disco on 2019-04-17 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco dist-upgrade 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/1825234 Title: Python3: After do-release-upgrade, all apt-installed modules need to be reinstalled, or they fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1825234/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1163886] Re: software-center crashed with signal 5 with the GNOME3 PPA on 13.04
** Summary changed: - Can You Buy Soma Online Overnight? + software-center crashed with signal 5 with the GNOME3 PPA on 13.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1163886 Title: software-center crashed with signal 5 with the GNOME3 PPA on 13.04 To manage notifications about this bug go to: https://bugs.launchpad.net/webkit-open-source/+bug/1163886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758918] Re: Ubuntu-Budgie: could not found /etc/profile.d/vte.sh
It appears libvte-common was somehow stuck at 2.90 on my system, even though a newer one was available. My guess is that this was from a PPA. ** Changed in: budgie-desktop (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758918 Title: Ubuntu-Budgie: could not found /etc/profile.d/vte.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1758918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758918] Re: Ubuntu-Budgie: could not found /etc/profile.d/vte.sh
I've got an issue that may be the same or related, but is occurring on install: ``` dpkg: error processing archive /var/cache/apt/archives/budgie-desktop-common_0.9.9ubuntu1_all.deb (--unpack): trying to overwrite '/etc/profile.d/vte.sh', which is also in package libvte-2.90-common 1:0.36.3-1ubuntu2 ``` ..does this provide the missing info needed to fix this bug, or is this unrelated? ** Changed in: budgie-desktop (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758918 Title: Ubuntu-Budgie: could not found /etc/profile.d/vte.sh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1758918/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
