[Bug 267999] Re: Sometimes Caps Lock works inverted
Yep it's back in 24.04. Lenovo Thinkpad T14S 5th Gen (Intel), and likely indeed after coming out of sleep. There are other issues when the device resumes from sleep as well. ** Changed in: linux (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/267999 Title: Sometimes Caps Lock works inverted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/267999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060400] Re: Remmina crashes instantly when trying to open a remote session
fwiw, the snap works, however it won't import my (many) RDP profiles
from ~/.local/share/remmina ("cannot import {file}").
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060400
Title:
Remmina crashes instantly when trying to open a remote session
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/2060400/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913775] Re: Copy from Firefox Wayland fails to be pasted anywhere else
Thanks. I also just wanted to be sure that I was installing the right packages. May I ask, how did you know that these are the ones you need to apt install? I'm confused because the official package is called gtk+3.0 but when I use apt I need to specify all of those? Those are also fewer packages than listed in on the Launchpad page's "binaries built by this package". Anyway I've now successfully installed the packages above. This doesn't require a reboot, does it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913775 Title: Copy from Firefox Wayland fails to be pasted anywhere else To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1913775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913775] Re: Copy from Firefox Wayland fails to be pasted anywhere else
Excellent news. I've previously installed: libgtk-3-common/now 3.24.30-3ubuntu2 and its dependencies from jammy and I've not seen the problem re-appear for a while. Is this the exact same software? In that case I'd vouch for the bug being solved. That said, I'd feel more comfortable installing from the impish-proposed repo, but I'm a little confused about how to, even with the guide. I've activated impish-proposed, added the preferences file, but I'm unsure what I should put or search for as the package name, so I put * which I assume stands for "all". Using aptitude, however, I couldn't find a package called "gtk+3.0". Should I just take libgtk-3-0_3.24.30-1ubuntu1.1_i386.deb? And will this install nicely over my (newer?) 3.24.30-3ubuntu2? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913775 Title: Copy from Firefox Wayland fails to be pasted anywhere else To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1913775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913775] Re: Copy from Firefox Wayland fails to be pasted anywhere else
I would also like to request a port of this fix to impish and hirsute. I've currently worked around this by upgrading gtk+3.0 in a probably slightly unorthodox way, but I'd much prefer if the package was offered through the official Ubuntu impish repository. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1913775 Title: Copy from Firefox Wayland fails to be pasted anywhere else To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1913775/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956581] [NEW] make gtk 3.24.31 available in Ubuntu 21.*
Public bug reported: A very annoying GTK bug (which breaks copying and pasting, the computer user's favourite activity) has been fixed in GTK 3.24.31. Unfortunately, Ubuntu 21.10 is still stuck on 3.24.30. I'd think that making 3.24.31 available wouldn't break much, but would help a lot of us out. Can this be 'backported' (is this the correct jargon?) or am I better off upgrading to Jammy Jellyfish even though it's still unstable? Bug: https://gitlab.gnome.org/GNOME/gtk/-/issues/4340 ** Affects: gtk+3.0 (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/1956581 Title: make gtk 3.24.31 available in Ubuntu 21.* To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1956581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952766] Re: Disconnecting monitor crashes shell (wayland, gnome)
Thanks for the explanation, I can understand the difficulty and hope misbehaving external extensions don't affect the image of GNOME too much. I will reactivate the dock and repeat the steps in comments #1 and #3 at the next crash, although I'm unsure how that will bring new information as I would imagine we'll get the same information as when it happened before? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952766 Title: Disconnecting monitor crashes shell (wayland, gnome) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1952766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952766] Re: Disconnecting monitor crashes shell (wayland, gnome)
I'm sure the discussion has been held elsewhere, and there's been made a case against sandboxing them or handling their crashes, as lack of freedom would defeat the very purpose of these extensions? At any rate I'm happy to have reached a solution. 3 monitor unplugs without crashes convinces me that that was the problem. Many thanks for your intervention! I don't miss the Dock very much but it'd be interesting to see where it has been patched and when to expect it in a release. Is there any info on that? On the bug you shared, it only says "fix committed" but I am too dumb to find out where I can see the code change. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952766 Title: Disconnecting monitor crashes shell (wayland, gnome) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952766] Re: Disconnecting monitor crashes shell (wayland, gnome)
After a few more disconnects with the Ubuntu Dock disabled and no crashes, it sounds like the culprit may be the Ubuntu Dock. The solution should be relatively simple then (although I'm a bit shocked that it can take down mutter) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952766 Title: Disconnecting monitor crashes shell (wayland, gnome) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952766] Re: Disconnecting monitor crashes shell (wayland, gnome)
Funnily, after disabling the Ubuntu Dock (have not yet logged out and in again) and unplugging my cable, there was no crash. Then again, the crashes are not consistent so I'll try again. This interferes with my work so much that I cannot test this constantly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952766 Title: Disconnecting monitor crashes shell (wayland, gnome) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952766] Re: Disconnecting monitor crashes shell (wayland, gnome)
Hello Daniel, thanks for your help. Please find the requested information attached. Two extra points: - I set the external monitor as my primary monitor, with the dock and title bar displaying here - Since 40.1 already contains the fix for the symptoms you quoted from my report, while they are then probably unrelated to this bug, it is strange that those symptoms are still present in 40.5. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952766 Title: Disconnecting monitor crashes shell (wayland, gnome) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952766] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1952766/+attachment/5545671/+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/1952766 Title: Disconnecting monitor crashes shell (wayland, gnome) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952766] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1952766/+attachment/5545673/+files/monitors.xml.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952766 Title: Disconnecting monitor crashes shell (wayland, gnome) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952766] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1952766/+attachment/5545670/+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/1952766 Title: Disconnecting monitor crashes shell (wayland, gnome) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952766] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1952766/+attachment/5545672/+files/ShellJournal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952766 Title: Disconnecting monitor crashes shell (wayland, gnome) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952766] Re: Disconnecting monitor crashes shell (wayland, gnome)
apport information ** Tags added: apport-collected impish third-party-packages wayland- session ** Description changed: This bug has been persisting since I've bought an external monitor for my laptop and started using Wayland (first on Ubuntu 20.04) until today (Ubuntu 21.10). It isn't consistent, but it occurs about 90% of the time when I'm on Wayland. On Xorg, this has never occurred. When I unplug my USB-C monitor from my laptop, the laptop screen freezes for a while before presenting me with the login screen. When I log back in, all my open applications have been shut down. I assume Mutter crashes, taking the entire session with it. Dmesg doesn't seem to contain anything useful. - A lot of other people seem to have this problem (see - https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1733127), but - all have been asked to file their own bug reports, so here I am. + A lot of other people seem to have this problem (see https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1733127), but all have been asked to file their own bug reports, so here I am. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu71 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 21.10 + InstallationDate: Installed on 2020-04-01 (613 days ago) + InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) + Package: gnome-shell 40.5-1ubuntu2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 + RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 + Tags: wayland-session impish third-party-packages + Uname: Linux 5.13.0-22-generic x86_64 + UpgradeStatus: Upgraded to impish on 2021-10-05 (61 days ago) + UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + modified.conffile..etc.apport.crashdb.conf: [modified] + mtime.conffile..etc.apport.crashdb.conf: 2021-12-01T17:24:37.722144 ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1952766/+attachment/5545668/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952766 Title: Disconnecting monitor crashes shell (wayland, gnome) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952766] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1952766/+attachment/5545669/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952766 Title: Disconnecting monitor crashes shell (wayland, gnome) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754687] Re: gnome-shell crashes with meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed
Hello Daniel, coming over here as requested from the other bug (1952766). Two questions: 1. How can you tell from that page that the code change has arrived in 40.1? I can only see when it was merged, but am unable to tell whether this particular fix is in that version. 2. Since I'm on gnome-shell version 40.5, it seems this is either a regression or the fix has gone somewhere else? ``` ~$ gnome-shell --version GNOME Shell 40.5 ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754687 Title: gnome-shell crashes with meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1754687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952766] Re: Disconnecting monitor crashes shell (wayland, gnome)
attached is a log after reproducing the bug, crashing, logging in, waiting 10 seconds, rebooting, and logging. NOTE: edited for privacy reasons (names, references to VPN connections) ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952766/+attachment/5545021/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952766 Title: Disconnecting monitor crashes shell (wayland, gnome) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952766] Re: Disconnecting monitor crashes shell (wayland, gnome)
Thanks. The bug report is now attached to this bug. (Some asides about the bug-uploading process:) There was already a _usr_bin_gnome-shell.1000.crash.uploaded file, however I cannot see my bug in errors.ubuntu.com. So I went and tried doing it manually: ``` $ ubuntu-bug _usr_bin_gnome-shell.1000.crash No such schema “org.gnome.settings-daemon.peripherals.mouse” No such schema “org.gnome.settings-daemon.peripherals.mouse” ``` Still no uploaded bugs in errors.ubuntu.com, so I comment out the line mentioned in bug 994921. I retried with ubuntu-bug. This time a progress indicator appeared, but it said HTTP Error 503: service unavailable. I retried again, then it seemed to have gone through. After the bug report is uploaded, it suggested this bug and I selected "yes it affects me" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952766 Title: Disconnecting monitor crashes shell (wayland, gnome) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952766] [NEW] Disconnecting monitor crashes shell (wayland, gnome)
Public bug reported: This bug has been persisting since I've bought an external monitor for my laptop and started using Wayland (first on Ubuntu 20.04) until today (Ubuntu 21.10). It isn't consistent, but it occurs about 90% of the time when I'm on Wayland. On Xorg, this has never occurred. When I unplug my USB-C monitor from my laptop, the laptop screen freezes for a while before presenting me with the login screen. When I log back in, all my open applications have been shut down. I assume Mutter crashes, taking the entire session with it. Dmesg doesn't seem to contain anything useful. A lot of other people seem to have this problem (see https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1733127), but all have been asked to file their own bug reports, so here I am. ** Affects: gnome-shell (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/1952766 Title: Disconnecting monitor crashes shell (wayland, gnome) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1952766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933633] Re: Failed to activate service 'net.reactivated.Fprint'
I've used the 21.04 latest kernel and it worked OK most of the time. I'm now on 21.10 with the 5.13 kernel and it also works OK. I'd close this then -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933633 Title: Failed to activate service 'net.reactivated.Fprint' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1933633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933633] Re: Failed to activate service 'net.reactivated.Fprint'
● fprintd.service - Fingerprint Authentication Daemon Loaded: loaded (/lib/systemd/system/fprintd.service; static) Active: failed (Result: exit-code) since Fri 2021-06-25 20:07:55 CEST; 4min 34s ago Docs: man:fprintd(1) Process: 108264 ExecStart=/usr/libexec/fprintd (code=exited, status=226/NAMESPACE) Main PID: 108264 (code=exited, status=226/NAMESPACE) jun 25 20:07:45 tuhao2 systemd[1]: Starting Fingerprint Authentication Daemon... jun 25 20:07:55 tuhao2 systemd[108264]: fprintd.service: Failed to set up mount namespacing: /run/systemd/unit> jun 25 20:07:55 tuhao2 systemd[108264]: fprintd.service: Failed at step NAMESPACE spawning /usr/libexec/fprint> jun 25 20:07:55 tuhao2 systemd[1]: fprintd.service: Main process exited, code=exited, status=226/NAMESPACE jun 25 20:07:55 tuhao2 systemd[1]: fprintd.service: Failed with result 'exit-code'. jun 25 20:07:55 tuhao2 systemd[1]: Failed to start Fingerprint Authentication Daemon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933633 Title: Failed to activate service 'net.reactivated.Fprint' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1933633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1933633] [NEW] Failed to activate service 'net.reactivated.Fprint'
Public bug reported: Since a few days, the fingerprint reader won't work anymore (Dell XPS 9300, Goodix Fingerprint reader Ubuntu 21.04, Mutter). Notably it started happening after kernel 5.11.22 was installed. $ fprintd-list Failed to get Fprintd manager: Error calling StartServiceByName for net.reactivated.Fprint: Failed to activate service 'net.reactivated.Fprint': timed out (service_start_timeout=25000ms) This causes long delays on the login screen and elsewhere. I could turn off the fingerprint reader pam, but I wish to keep using it. Journalctl -b 0 output attached. ** Affects: libfprint (Ubuntu) Importance: Undecided Status: New ** Attachment added: "journalctl -b 0 output" https://bugs.launchpad.net/bugs/1933633/+attachment/5506968/+files/fprint-log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1933633 Title: Failed to activate service 'net.reactivated.Fprint' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1933633/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901312] Re: tpm module malfunctions
Hello Woodrow I think already at steps 1 and 2 something's going wrong: 1. sudo cp /sys/kernel/security/tpm0/binary_bios_measurements ~/temp/ Killed (a 0-byte file now exists with this name in ~/temp/ - I assume it will be of no use to include it here) $ sudo fwts tpmevlogdump Running 1 tests, results appended to results.log Test: Dump Tpm2 Event Log. Killed Tpm2 Event Log. $ cat results.log Results generated by fwts: Version V20.09.00 (2020-09-17 18:08:13). Some of this work - Copyright (c) 1999 - 2020, Intel Corp. All rights reserved. Some of this work - Copyright (c) 2010 - 2020, Canonical. Some of this work - Copyright (c) 2016 - 2020, IBM. Some of this work - Copyright (c) 2017 - 2020, ARM Ltd. This test run on 26/10/20 at 08:10:05 on host Linux tuhao2 5.4.0-52-generic #57-Ubuntu SMP Thu Oct 15 10:57:00 UTC 2020 x86_64. Command: "fwts tpmevlogdump". Running tests: tpmevlogdump. tpmevlogdump: Dump Tpm2 Event Log. Test 1 of 1: Dump Tpm2 Event Log. tpm0 Happy to go on with step 3 if it is still necessary (I'd rather not reboot right now if not necessary yet because I'd have to restart some work) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1901312 Title: tpm module malfunctions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1901312] [NEW] tpm module malfunctions
Public bug reported: I originally filed a bug against the fwupd software (https://github.com/fwupd/fwupd/issues/2508) from where it transpired that this problem was with the tpm package rather than with fwupd. Some evidence is in: $ sudo cat /sys/kernel/security/tpm0/binary_bios_measurements Killed The device is an XPS 13 9300 (2020 model). I can reproduce the problem on kernels 5.8, 5.9 and 5.9.1 too. Haven't tried any other kernel versions. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-52-generic 5.4.0-52.57 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sander 2665 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 24 14:29:34 2020 HibernationDevice: # RESUME=UUID=e2b4846f-867a-4f84-a3d7-0f5d10d24a33 resume_offset=31260671 # RESUME=UUID=6a9d6823-9903-4887-bd63-11831c1218c0 # RESUME=/dev/nvme0n1p7 resume_offset=31260671 # RESUME=/dev/nvme0n1p7 # Resume from /swapfile InstallationDate: Installed on 2020-04-01 (206 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 9300 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=e1b4846f-867a-4f84-a3d7-0f5d10d24a33 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-52-generic N/A linux-backports-modules-5.4.0-52-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-24 (183 days ago) dmi.bios.date: 08/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 0Y4GNJ dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd08/13/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0Y4GNJ:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. ** Affects: linux (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/1901312 Title: tpm module malfunctions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1901312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa
*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Same issue. Had some promising results with pali's branch of pulseaudio which contains fixes for HSP/HFP profiles. But then a pulseaudio/kernel/idk update borked it all and I don't have the mental bandwidth to try it all again. https://gitlab.freedesktop.org/pali/pulseaudio Kernel v 5.9.1 (but all previous versions I tried had the same issue) Ubuntu 20.04 XPS 13 9300 Sony WH-1000XM3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
