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
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
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
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
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
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
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
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
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
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
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
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
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.
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.
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.
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
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.
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
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"
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
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.
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.
● 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
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
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
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
*** 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
27 matches
Mail list logo
