** Description changed:
Description
When SEV-SNP is enabled on Ubuntu 24.04, RSA operations experience a
significant performance degradation (approximately 66% slower) compared
to when SEV-SNP is disabled. This appears to be caused by the loss of
crucial CPU instruction sets when SEV-
Hello Fabio,
Just wanted to check to see if after reproducing the behavior you were
able to identify any temporary fixes, or if any fixes are in the
pipeline.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Grasping at straws, I tried replacing pipewire with pulseaudio. It had
no effect.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098548
Title:
CubicSDR doesn't find audio devices
To manage notific
$ apt-cache rdepends libsoapysdr0.8
libsoapysdr0.8
Reverse Depends:
libsoapysdr-dev
welle.io
uhd-soapysdr
soapysdr0.8-module-xtrx
soapysdr0.8-module-uhd
soapysdr0.8-module-rtlsdr
soapysdr0.8-module-rfspace
soapysdr0.8-module-remote
soapysdr0.8-module-redpitaya
soapysdr0.8-modul
Seems this is a bug in libsoapysdr0.8.
$ SoapySDRUtil --find
##
## Soapy SDR -- the SDR abstraction library ##
##
[INFO] [UHD] linux; GNU C++ version 13.3.0; Boost_108300; UHD_4.7.0.0+d
** Attachment added: "strace"
https://bugs.launchpad.net/ubuntu/+source/cubicsdr/+bug/2098548/+attachment/5857684/+files/strace.dump
** Bug watch added: Debian Bug tracker #1084177
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084177
** Also affects: cubicsdr via
https://bugs.debia
Is CubicSDR compatible with pipewire?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2098548
Title:
CubicSDR doesn't find audio devices
To manage notifications about this bug go to:
https://bugs.lau
alsa-info
** Attachment added: "alsa-info.txt.hViGatePCu"
https://bugs.launchpad.net/ubuntu/+source/cubicsdr/+bug/2098548/+attachment/5857683/+files/alsa-info.txt.hViGatePCu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
ell output:
$ CubicSDR
Loading:: configuration file '/home/jon/.CubicSDR/config.xml'
Loaded 283 rig models via hamlib.
ALSA lib control.c:1570:(snd_ctl_open_noupdate) Invalid CTL pulse
ALSA lib control.c:1570:(snd_ctl_open_noupdate) Invalid CTL pulse
RtApi::getDeviceInfo: deviceId argumen
.flags;
ap->ops->qc_fill_rtf(qc);
+ qc->flags |= ATA_QCFLAG_RTF_FILLED;
}
static void ata_verify_xfer(struct ata_queued_cmd *qc)
All the best,
Jon Ivar
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-52-generic 6.8.0-52.53
ProcVersionSigna
without a bit of know-how and
remote logging, they might not be able to find neither the culprit nor
the workaround.
Cheers, and thanks for following up on the issue!
Jon Ivar
> 9. feb. 2025 kl. 22:51 skrev Matthew Ruffell <2097...@bugs.launchpad.net>:
>
> Yeah, looks like powe
sible and the system keeps
throwing I/O errors until I force a reboot.
All the best,
Jon Ivar
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-52-generic 6.8.0-52.53
ProcVersionSignature: Ubuntu 6.8.0-52.53-generic 6.8.12
Uname: Linux 6.8.0-52-generic x86_64
ApportVersio
Any updates on this? I'm seeing the same error when trying to update the
firmware on a Dell Latitude 7540
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2071940
Title:
Cannot update Lenovo firmware w
Looks like this was fixed upstream in version 2.4.1:
https://github.com/nagios-plugins/nagios-plugins/pull/649
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2095449
Title:
check_smtp can't ssl or tl
"default_ccache_name = FILE:/home/%{username}/krb5cc"
That's not a default nor a configuration that anyone routinely uses. It
will likely play merry hell with daemons such as sssd and winbind that
try to centrally refresh Kerberos tickets, on a system.
However, it might and probably will work bu
Hello Fabio,
Thank you for the quick response and for confirming the behavior.
You're right - the missing CPU flags (AVX, AVX2, VAES, etc.) when SEV-
SNP is enabled is expected behavior and occurs on both Ubuntu 24.04 and
AL2023. I apologize for the oversight.
I guess we are just puzzled on the
Public bug reported:
Description
When SEV-SNP is enabled on Ubuntu 24.04, RSA operations experience a
significant performance degradation (approximately 66% slower) compared
to when SEV-SNP is disabled. This appears to be caused by the loss of
crucial CPU instruction sets when SEV-SNP is enabled.
Thanks, works 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/2060753
Title:
mailman3-web needs DEFAULT_AUTO_FIELD setting
To manage notifications about this bug go to:
https://bugs.launchpad
It looks like this is also true in 22.04. I'm wondering if there is a
way to build it manually? I want to use OVS to manage the networks I use
with KVM virtual machines, but I've been unable to get it working due to
the lack of builtin network manager support.
I'd like to avoid moving to netplan i
I'm also seeing this on linux-image-6.8.0-50-generic package for Ubuntu
24.04, if I downgrade to linux-image-6.8.0-49-generic its fine.
The LUKS prompt shows up and the keyboard works for a split second, then
the display blinks off for a moment (like its changing video modes), and
when it comes ba
Builds with the suspect commit as mentioned above:
jon@C02F13YVQ05N jammy % git tag --contains 34192ba1338f
Ubuntu-5.15.0-125.135
Ubuntu-5.15.0-126.136
Ubuntu-5.15.0-127.137
Ubuntu-lowlatency-5.15.0-125.135
Ubuntu-lowlatency-5.15.0-126.136
Ubuntu-lowlatency-5.15.0-127.137
Builds with what should
Ok gotcha. Perhaps someone from Ubuntu side can help illuminate when
that would be available, I'm not familiar with the release cadence here.
We're certainly open to back-n-forth discussions here if this commit
doesn't fix the issue, or other issues remain, but given what we went
through on other
@Hans - thanks - our messages crossed in flight. I've cross posted the
tags where the fixing commit should live, as well as the bug ID that
brought in the fixing commit. It looks like it was brought in as normal
fit-n-finish backports, so this regression should find it self-solving
(knock on wood!)
Checked out the jammy source
jon@C02F13YVQ05N jammy % git clone
git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy
jon@C02F13YVQ05N jammy % git checkout Ubuntu-5.15.0-126.136
jon@C02F13YVQ05N jammy % git log --oneline -n 1 HEAD
87cad896a075 (HEAD, tag: Ubuntu-5.15.0-126.136
Hey Jon from Nutanix AHV R&D here - We also see this issue on RHEL,
SLE15, and vanilla kernels. In all three of those cases, the problem
wasn't with AHV, but with a problematic set of backport that was tagged
as a CVE, but caused a GSO-based performance regression. This can be
reproduc
Hey Jon from Nutanix AHV R&D here - We also see this issue on RHEL,
SLE15, and vanilla kernels. In all three of those cases, the problem
wasn't with AHV, but with a problematic set of backport that was tagged
as a CVE, but caused a GSO-based performance regression. This can be
reproduc
Public bug reported:
Ubuntu version:
Description:Ubuntu 24.04.1 LTS
Release:24.04
Package version:
libsqlite3-0:
Installed: 3.45.1-1ubuntu2
Candidate: 3.45.1-1ubuntu2
Version table:
*** 3.45.1-1ubuntu2 500
500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages
d issue, but it doesn't look like it went anywhere.
I'm happy to provide any testing required - it's not mission critical
(it's for a machine I use to support a family member) but it is
annoying, and I would like to improve things where I can. Just point me
at whatever you need!
Shotwell is still chugging along. 167GB disk read total, memory util is
stable at about 600MB.
Ship it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2080004
Title:
Shotwell bug - Out of memory #51
Running my own test case - shotwell version 0.32.6-1ubuntu2. Running
slideshow of entire library (27k+ photos) advancing at one-second
intervals. System monitor shows shotwell doesn't continue to consume and
not release memory like it used to. Will report again in 24 hours to
affirm shotwell is sti
I upgraded to the 550 drives, which did seem to remove the simple-drm
piece from my logs, but the issue still occurs.
What looks like the Relevant part of the logs:
```
Sep 16 21:26:40 toothbrush /usr/libexec/gdm-x-session[2580]: (WW) NVIDIA(0):
Failed to request fliplock.
Sep 16 21:26:40 tooth
I've re-upgraded to 24.04 and this is still happening. I will look into
the posted workarounds and see if I can gather more information.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064037
Title:
Happy to help, Sebastien. I feel silly for asking, but how should I
expect to get the patch now? Don't work too hard answering, just point
me at the answer. :D
Thanks!
Jon
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
with Shotwell
https://gitlab.gnome.org/GNOME/shotwell/-/issues/5123
And here's the case Jens Georg opened in response.
https://gitlab.gnome.org/GNOME/shotwell/-/commit/fa6884f73af83ccbc72b8fe0f7bc63a00630ee0b
Thank you!
- Jon Redinger
-
- jon_redin...@cfl.rr.com
+ Jon
--
Yo
** Bug watch added: gitlab.gnome.org/GNOME/shotwell/-/issues #5123
https://gitlab.gnome.org/GNOME/shotwell/-/issues/5123
** Also affects: shotwell via
https://gitlab.gnome.org/GNOME/shotwell/-/issues/5123
Importance: Unknown
Status: Unknown
--
You received this bug notification b
https://gitlab.gnome.org/GNOME/shotwell/-/issues/5123
And here's the case Jens Georg opened in response.
https://gitlab.gnome.org/GNOME/shotwell/-/commit/fa6884f73af83ccbc72b8fe0f7bc63a00630ee0b
Thank you!
Jon Redinger
jon_redin...@cfl.rr.com
** Affects: shotwell (Ubuntu)
Importance:
Hey! Thank you for the quick turnaround - confirmed that I was able to
start a 22.04 LTS VM on LXD, then install the linux-image and linux-
modules debs and both Cilium and Parca Agent functioned correctly wrt to
the BPF subsystem!
--
You received this bug notification because you are a member of
Hey - I initially raised this with @tomparrott because our new K8s uses
Cilium by default, and it felt wonky that it couldn't be deployed on LXD
VMs.
The requirements for Cilium are on this page:
https://docs.cilium.io/en/stable/operations/system_requirements/#base-
requirements
That said, Tom's
While it's not a fix coming from upstream, you can edit /etc/crypttab
and turn this:
```
dm_crypt-0 PARTUUID=decafbad-1234-abcd-5678-1234 /dev/urandom
swap,initramfs
```
into this:
```
dm_crypt-0 PARTUUID=decafbad-1234-abcd-5678-1234 /dev/urandom
swap,initramfs,cipher=aes-xts-p
o work
> fine. So, I downloaded the newest Kali .iso and tried that. again,
> nothing. So I dont know what to do at this point because I dont want
> to carry a usb keyboard around with me when i use my laptop. Any idea
> on what I can do? Thanks. - Jon
>
> To manage noti
the keyboard turns off as soon as the kali screen loads up where it asks
to select from live, live failsafe, install, advanced options. If i plug
in a USB keyboard, the USB keyboard works fine. It's the laptops
keyboard that dosent work at all. The laptops mouse works fine as well.
no issues there.
. - Jon
** 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/2072465
Title:
asus keyboard not working live usb
To manage
This is causing me issues. I installed mlocate in 22.04 (and from what I
understand that is an alias for plocate), but it is taking too long, and
I would rather just install other packages, but the dpkg lock is now in
use, and stopping the install seems to break things, so without
knowledge on how
I've reinstalled a fresh copy of 24.04 with extras enabled and
recommended proprietary software installed, and I recorded a set of
observations on a fresh system. I recorded journal logs and other stats
in a similar format.
I think I may have identified a culprit. The crash appears to only occur
w
I've updated my bios, but the issue seems to persist. It's still
inconsistent. Sometimes it un-blanks without issue, sometimes I get the
gray-screen-of-death, and sometimes it unblanks directly to the login
page without a GSOD.
I'll try any other debugging suggestions, including a OS-reinstall. Th
Oh boy, so I've spent the past two days recording observations on this
issue, and I see no clear patterns at all. I've created a zipfile with a
text document called update.txt which contains my actions and
observations.
The basic pattern is: I do stuff, wait for the screen blank, un-blank
and see
I made an interesting observation. If I unplug all bug one monitor (I
have been using 3 in tests up until now), the crash does not occur in
X11. I have not tried wayland yet.
I'm going to plug in a second monitor to check if it happens with 2, and
then verify that it still occurs with 3.
--
You
Here is prevboot.txt
Is my whoopsie-id something that should be kept private? I do have files
in /var/crash that have timestamps from yesterday and today, but they do
not seem to appear under https://errors.ubuntu.com/user/ even after
I ran `ubuntu-bug `
** Attachment added: "prevboot.txt"
ht
I have noticed that it will happen in the wrong place and then go away
from time to time. That bothers me a lot less than when it persists and
obscures something I want to look at. I have no idea how to replicate it
yet.
--
You received this bug notification because you are a member of Ubuntu
Bug
Update: I don't know what changed, (I did do an apt upgrade), but now
the crash is happening for Wayland too whenever the screen powers off.
It's very frustrating.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
I'm not sure if this is the same exact bug, my problem just seems to
happen randomly not when necessarily when I close something, I'm still
trying to identify a reproducible cause. My problem seems more similar
to https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-
ubuntu-dock/+bug/20
Is there a resource you could point me to where I can learn what the
security risks of public .crash files are? I'm interested to know what
sensitive information could be contained in them.
Interesting that the whoopsie-id seems to persist across OS installs, or maybe
it's tied to my Ubuntu One
I did have another "random" crash in the middle of a session. I was
moving a window around. So it's not rela.ted to the main reason for this
bug report, but I figure its relevant enough to attach the journalctl
logs
** Attachment added: "wayland_crash_journalctl.log"
https://bugs.launchpad.ne
On the matrix chat Nils mentioned that "im on nvidia 550 atm and on
wayland. i had some X11 crashes in the past and wayland does a much
better job so far"
So, I changed my session type to Wayland by logging out and using the
gear by my username to select wayland. Doing that seems to have an issue
Also attaching the results of `sudo journalctl --dmesg --priority
warning > journalctl_dmsg_warnings.log` it does seem to have some nvidia
errors and tracebacks. It doesn't mean much to me, but perhaps it has
useful information in it.
** Attachment added: "journalctl_dmsg_warnings.log"
https:/
I'm also experiencing intermittent crashes of the window manager -
either gnome-shell or gdm3, not 100% sure. What I am sure of is that I'm
getting forcibly logged out.
I just experienced a crash when discussion this issue in matrix chat.
There were a few things going on at the time. I did have st
Public bug reported:
I've written an AskUbuntu question about this:
https://askubuntu.com/questions/1511958/screen-lock-keeps-occuring-
on-24-04-even-though-i-believe-ive-disabled-it/1512075#1512075
Originally I thought it was gnome not respecting my setting to prevent
locking the screen after id
I've confirmed it does happen when just using super+arrow and no mouse
interaction. I still cannot get it to work reliably though.
My monitor setup looks roughly like this:
```
+--+
|2 | +--+
| | |1 |
+--+ | |
+--+ | |
|3 | |
I was able to get a screenshot of the issue. I edited the images to
remove sensitive information I was working with at the time, but the
point is that I was moving around windows (I forget if I was using
super+arrow or dragging to corners), and the issue happened. I'm still
not sure exactly how to
Public bug reported:
I've got a fresh install of the first 24.04 release, and I'm seeing
strange behavior related to super+arrow keys and the enhanced tiling.
I've disabled tiling popups and tiling groups, but I like the quad
blocks.
The issue is when I'm moving around windows, sometimes the oran
Thanks all for the details. Assuming it is safe to be removed and that
the new conflict in -proposed will help to do so automatically for users
that upgrade, once mainlined.
apt autoremove python3-distutils
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
I can confirm the behaviour after a recent upgrade from mantic to noble
and has also been reported in https://discourse.ubuntu.com/t/noble-dev-
branch-why-does-the-keyring-stay-locked-upon-login-also-why-did-apt-
install-work-but-apt-upgrade-fail/43979
Another oddity is, that I seem to have to typ
Public bug reported:
After upgrading mantic to noble, there are multiple SSH agents who are
independently trying to set SSH_AUTH_SOCK, none of which is successful.
1. ~/.config/autostart/gnome-keyring-ssh.desktop (identical to
/etc/xdg/autostart/gnome-keyring-ssh.desktop, if not modified)
This w
Public bug reported:
After upgrading to noble, there appears to be a regression between the
to-be-installed python3-distutils package and its dependency
python3-lib2to3. The old packages from mantic remain installed.
python3-distutils
Depends on: python3-lib2to3 (= 3.12.2-3ubuntu1.1)
Installa
This bug still exists on Ubuntu 23.10. HP Elitebook 840 G1.
inxi -Fxz
System:
Kernel: 6.5.0-21-generic arch: x86_64 bits: 64 compiler: N/A Desktop: GNOME
v: 45.2 Distro: Ubuntu 23.10 (Mantic Minotaur)
Machine:
Type: Laptop System: Hewlett-Packard product: HP EliteBook 840 G1
v: A3009DD
The SMB1 code should be entirely removed from the stack. It’s insecure and
deprecated everywhere.
On Tue, May 2, 2023 at 8:56 AM BloodyIron <1828...@bugs.launchpad.net>
wrote:
> Upgraded to Ubuntu 23.04 and the issue persists... Will this ever get
> fixed? This is now over 4 years old.
>
> --
>
Yes, I can second the notion that this seems independent from the two
proposed upstream issues, since this has also happened here when
upgrading to 22.04.
$ sudo cat /etc/default/keyboard
XKBLAYOUT="de,us"
XKBVARIANT=","
BACKSPACE="guess"
XKBMODEL="pc105"
XKBOPTIONS="grp:alt_caps_toggle,grp_led:sc
Removal of the package 'sabily-gdm-themes' and rebooting had no effect
on my situation.
Daniel, perhaps you have some insight into this. What information I've found
in my internet search says that gdm/gdm3 defaults to Adwaita icon theme. I'm
looked for "how to configure" type articles
about gd
** Attachment added: "login screen WITH Adwaita/cursors"
https://bugs.launchpad.net/ubuntu/+bug/1972080/+attachment/5588894/+files/login-screen-with-Adwaita-cursors.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
** Attachment added: "login screen without Adwaita/cursors"
https://bugs.launchpad.net/ubuntu/+bug/1972080/+attachment/5588893/+files/login-screen-without-Adwaita-cursors.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
** Attachment added: "list of installed packages"
https://bugs.launchpad.net/ubuntu/+bug/1972080/+attachment/5588892/+files/minis-packages.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972080
Adding MUTTER_DEBUG_DISABLE_HW_CURSORS=1 to /etc/environment and
rebooting had no effect on the issue. White square "mouse pointer" is
present on gdm login screen if /usr/share/icons/adwaita/cursors is
missing (renamed).
If instead I install a symbolic link .../Adwaita/cursors -> .../Yaru/cursors
The reported problem is during login, not after successful login.
I don't think mutter configuration has any effect before graphical login.
Ubuntu's cursor theme may come from 'yaru-theme-icon', but does gdm's?
Two files affect the observed condition:
/usr/share/icons/Adwaita/cursors/left_ptr
/u
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+bug/1972080/+attachment/5587825/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972080
Title:
gdm has inco
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+bug/1972080/+attachment/5587826/+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/1972080
Title:
gdm has incomple
I tried Fedora 35, and found the exact same behaviour (ie the boot
program recognises the keyboard, but the final linux image does not).
Jon Thackray
j...@pobox.com
0044 1223 276500 (home)
0044 7803 017991 (mobile)
0033 423354068 (France)
-- Original Message --
From: "Jon Tha
* log2 (180) hours, ie about 4 hours.
Jon Thackray
j...@pobox.com
0044 1223 276500 (home)
0044 7803 017991 (mobile)
0033 423354068 (France)
-- Original Message --
From: "Daniel van Vugt" <1930...@bugs.launchpad.net>
To: j...@pobox.com
Sent: 22/04/2022 03:00:03
Subject:
time next year, there will be no Ubuntu (or Debian I think,
given that Rapsbian doesn't work with the KVM either) distribution I can
use, as at that point 18.04 will be end of support. I shall then start
having to try and learn other distros to see if any of them have
fixed/failed to create
Public bug reported:
goverlay does not display its window and immediately exits, with the
following error if run from terminal:
can't get libdl.so
Tested on jammy beta, up to date as of 2022-04-20 1500 UTC.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: goverlay 0.7.1-2
ProcVersionSignat
From libvirt gitlib...
Daniel P. Berrangé 💬 @berrange · 2 months ago
Owner
The QEMU patches required to solve this are here
https://lists.gnu.org/archive/html/qemu-devel/2022-02/msg03279.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
I'm using Ubuntu 20.04.4 LTS and GNOME 3.36.8
Still having this problem. Very surprised it has lasted this long. In
any case, if it is fixed, will this change make it to the next LTS
update?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
Public bug reported:
I don't really know what happened.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2
I am also adding the output from boltctl, if you need any other info
please advise.
** Attachment added: "Boltctl output"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950780/+attachment/5540412/+files/boltctl.txt
--
You received this bug notification because you are a member of Ubun
Adding dmesg output from computer
** Attachment added: "Output from dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950780/+attachment/5540411/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
Public bug reported:
I have a Lenovo Thunderbolt 3 Gen 2 dock and wanted to use this with
Ubuntu 21.10. When booting an unmodified version the usb ports do not
work. After an inspection with journalctl I find the error message "No
bus number available for hot-added bridge" and a google search led
Public bug reported:
Doing a dist-upgrade from 18.04 to 20.04:
Errors were encountered while processing:
ubuntu-advantage-tools
Exception during pm.DoInstall(): E:Sub-process /usr/bin/dpkg returned an error
code (1)
*** Send problem report to the developers?
After the problem report has been
Confirmed! Finally. With the latest HWE:
$ apt show linux-image-5.11.0-37-generic
Package: linux-image-5.11.0-37-generic
Version: 5.11.0-37.41~20.04.2
...
No errors or warnings in dmesg or journalctl -b seen on my statem
anymore.
Motherboard: ASUS PRIME X570-PRO (latest BIOS v 4021)
CPU: Ryzen
Confirmed. Just updated and same.
Can you backport the fix to the 20.04 HWE kernel? I mean that's the one
Canonical recommends has as first choice if downloading Ubuntu from
ubuntu.com, for years now. And they've become more stable in my
experience than the ones between LTS versions, which is good
And will that kernel come to the Ubuntu 20.04 LTS HWE stack, say in
20.04.4? Kinda need to use LTS versions, us that need that stability at
least.
Not really interested in fixes for 21.10 or something... Focal.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
To be clear this issue started with Kernel 5.8.0-63 NOT 5.11 (on Focal /
20.04 HWE LTS)
Well Ubuntu Kernel Bot, that's exactly what I did in comment #14
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1937897/comments/14
Latest 5.13 kernel in -prosed on Focal (20.04.3) gets the same gpio
err
** Tags removed: verification-needed-focal
** Tags added: verification-failed-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1937897
Title:
GPIO error logs in start and dmesg after update of ke
Added tag 'verification-failed-hirsute'. Enabled proposed and installed
package 'linux-image-5.13.0-14-generic' version '5.13.0-14.14~20.04.4'
on my 20.04.3 LTS, and still get in dmesg:
[1.228729] gpio gpiochip1: (gpio_aaeon): tried to insert a GPIO chip with
zero lines
[1.228732] gpiochi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1929504
Title:
Add support for IO functions of AAEON devices
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lin
Hi,
The latest file shows as follows:
```
try:
fcntl.ioctl(sock, SIOCETHTOOL, packed) # Status ioctl() call
if _PY3:
res = status_cmd.tobytes()
else:
res = status_cmd.tostring()
speed, duplex = struct.unpack("12xHB28x", res)
```
Howeve
OK, but don't try to load the gpio-aaeon module on PCs that, if simply
one tries to load it manually, it simply says that no such device
exists... It shows twice in the boot log (dmesg + journalctl -b) but
even worse also on the monitors, although GRUB has "quiet" specified (no
splash).
Worst of a
Well OK there is a module with that name, however I did blacklist it and
same error still occurs. It happens very early in the boot process. Now
maybe it tries to load gpio-aaeon, but still early to load modules I
would say, it's still doing say GRUB kernel parameters like fsck ones.
Now I have co
Same on Ubuntu 20.04 both GA and HWE kernel.
Sure, it just takes this command to find which package has it:
$ apt-file search libbd_mdraid.so.2
And get "libblockdev-mdraid2", which does "fix" it, but I DON'T need it.
Depends on packages I don't need, MOST don't need:
$ apt show libblockdev-mdra
No, I can't, because there isn't a single module loaded with even the
name "gpio" in it.
So running: $ lsmod|grep gpio == No result
It's in the kernel, not a module. I reverted to the GA kernel and
although with that I've had some issue with on headless *Intel* NUC
running Virtual Machines that u
EDIT: To clarify both times these lines come they refer to "gpiochip1"
(so not 2 different ones).
I started getting the same 3 lines of errors TWICE at boot, with the now
latest official 5.8 HWE kernel. Without "splash", just "quiet" set for
GRUB it also shows on my monitors when booting. Honestly
Public bug reported:
After running a fresh installation the app crashed.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: ubiquity 21.04.19
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname: Linux 5.11.0-16-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvp
1 - 100 of 4086 matches
Mail list logo
