** Package changed: upower (Ubuntu) => systemd (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2107283
Title:
Fans take several minutes so turn off after entering
Laptop is a Lenovo ThinkPad T14 Gen 3
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upower in Ubuntu.
https://bugs.launchpad.net/bugs/2107283
Title:
Fans take several minutes so turn off after entering S0ix
Status in upo
Public bug reported:
Current Behaviour: After putting Laptop into sleep mode (S0ix), cooling
fans slow down but keep spinning for several minutes (tested: 6
minutes).
Expected Behaviour: After putting laptop into sleep mode, cooling fans
get the system into a temperature range where fans can be t
After restarting the computer I checked things again. It is not so good
as I wrote above. I was not patient enough to watch the bluetooth button
for a sufficient time. The behavior (upon clicking the button in the On
state) is:
The button gets the pale colour, keeps is for about 1-2 seconds and th
Yes, bluetooth stays off after that command. The button got the pale
colour and the text output from the command was
CHG] Controller 98:5F:41:4E:7F:90 PowerState: on-disabling
hci0 class of device changed: 0x00
hci0 new_settings: ssp br/edr le secure-conn wide-band-speech cis-central
cis-peri
I ran the test case on both 24.04 and 24.10 with the respective
released/proposed versions. I confirm that the AA violation is gone with
the update. I also ran the originally triggering cockpit test
TestHistoryMetrics.testEvents and confirm that with the proposed version
the denial is gone there as
I can still reproduce the AppArmor violation with both the reproducer
here as well as with cockpit's TestJournal.testLogLevel test that
originally caused me to report this. I updated to -3ubuntu9.1 from
noble-proposed, and I confirm that everything works as advertised -- no
more AA violations, and
Public bug reported:
Description:Ubuntu Plucky Puffin (development branch)
Release:25.04
bluetooth:
Installed: (none)
Candidate: 5.79-2
Version table:
5.79-2 500
500 http://archive.ubuntu.com/ubuntu plucky/universe amd64 Packages
I expected that clicking on the blu
Public bug reported:
See conversation with Gemini for all details:
https://g.co/gemini/share/ba105661ef94
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-126.136-generic 5.15.167
Uname: Linux 5.15.0-126-generic x86_64
NonfreeKernelMod
Thanks! I pulled that version into our image in
https://github.com/cockpit-project/bots/pull/7176 and it all works
again. So removing my regression-proposed flag. However, I didn't
actually validate the bug fix, so not moving to v-done.
** Tags removed: regression-proposed
--
You received this b
Thanks Nathan and Sebastien for the fast fix! However, it failed to
build on most arches:
https://launchpad.net/ubuntu/+source/policykit-1/124-2ubuntu1.24.10.2
(without a log..). So the above autopkgtest message is rather
misleading.
--
You received this bug notification because you are a member
This update breaks firewalld:
# firewall-cmd --list-services
ERROR:dbus.proxies:Introspect error on :1.12:/org/fedoraproject/FirewallD1:
dbus.exceptions.DBusException: org.freedesktop.PolicyKit1.Error.Failed: Action
org.fedoraproject.FirewallD1.info is not registered
Error: Action org.fedoraproj
Here's a relatively minimal example:
```
$ sudo fips-mode-setup --check
FIPS mode is enabled.
$ uname -a
Linux hostname 4.18.0-553.8.1.el8_10.x86_64 #1 SMP Fri Jun 14 03:19:37 EDT 2024
x86_64 x86_64 x86_64 GNU/Linux
```
```
FROM ubuntu:24.04 AS builder
RUN . /etc/os-release && \
DEBIAN_FRON
We are seeing this as well when building an image with ubuntu:24.04 as
our base. Like the commenter above, we see the issue on our FIPS
system, but do not see it on our non-FIPS system. A workaround or any
information is certainly appreciated.
--
You received this bug notification because you ar
Slick Greeter is back in Ubuntu MATE 24.10 and has a configuration tool
for change the background. Closed via
https://launchpad.net/ubuntu/+source/ubuntu-mate-settings/24.10.1
** Changed in: ubuntu-mate
Status: New => Fix Released
--
You received this bug notification because you are a me
Closed for Ubuntu MATE via https://launchpad.net/ubuntu/+source/ubuntu-
mate-settings/24.10.1
** Changed in: ubuntu-mate
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
ht
OK, thanks for confirming!
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2073776
Title:
nsswitch.con
Yes, I had changed it with ansible
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2073776
Title:
nsswitch.conf "passwd" entry misses "systemd", breaking
DynamicUser=yes
My workaround is this command: "sudo fwts s4"
It hibernates the system without any change to the setup.
It is not very nice but works for now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.lau
I really need to ask:
Have you narrowed down which package causes the issue? If yes, can you
please un-tag packages that are unrelated to the issue?
If you're just generally commenting on the relevance of enabling IPv6 on
standard Ubuntu installations, tagging all packages that perform network
co
Well, with a new set of upgrades the problem seems to have resolved
itself.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2063154
Title:
Wireguard imported with N
Public bug reported:
Until a few days ago, after some upgrade, wireguard config imported with
Network manager worked ootb. Now, it does not, there is no handshake.
Activating the same config file with wg-quick does work.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: network-manager 1.46.0
** Changed in: ubuntu-mate-meta (Ubuntu Noble)
Status: Triaged => In Progress
** Changed in: ubuntu-mate-meta (Ubuntu Noble)
Assignee: (unassigned) => Martin Wimpress (flexiondotorg)
** Changed in: ubuntu-mate-meta (Ubuntu Noble)
Status: In Progress => Fix Committed
Public bug reported:
One of our Cockpit integration tests [1] spotted an AppArmor regression
in rsyslogd. This is coincidental, the test passes and it doesn't do
anything with rsyslogd -- just something happens to happen in the
background to trigger this (and I can actually reproduce it locally
qu
I also tried removing the Mesa Vulkan driver and set `export
LIBVA_DRIVER_NAME=i965`. That gets rid of the warning message but I
still get a hang with Vivaldi and nextcloud-desktop still does not work.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages
Thanks. Sounds similar. My nautilus and gnome-control center do work
strangely enough. But the more clues the better.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wayland in Ubuntu.
https://bugs.launchpad.net/bugs/206125
** Package changed: xorg (Ubuntu) => wayland
** Project changed: wayland => wayland (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2061257
Title:
After 24.04 upgrad
I tried the same upgrade and test on an old Sandy Bridge laptop.
Everything works as expected there. So a Haswell issue perhaps?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/
I tried the same test on an old Sandy Bridge laptop. Everything works
as expected there. So a Haswell issue?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2061257
Title:
A
** Summary changed:
- Many app failures under Wayland; no issues with Xorg
+ With 24.04: Many graphical app failures under Wayland; no issues with Xorg
** Summary changed:
- With 24.04: Many graphical app failures under Wayland; no issues with Xorg
+ After 24.04 upgrade, many graphical app fa
Public bug reported:
Many applications seem to fail under a Wayland session that work correctly with
an Xorg session. E.g.
- The nextcloud client app fails to contact the server and functions in the app
will not launch with Wayland while they work perfectly in Xorg
- The Vivaldi browser exits wi
I should also mention: this was an upgrade from 23.10 to 24.04 and all
of the apps worked correctly in 23.10.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2061257
Title:
Ma
Yeah, I could live with that -- but TBH I still consider this mostly a
bug in openssh. querying the status of sshd.service really should work.
Arch, RHEL, Fedora, OpenSUSE etc. all call this sshd.service.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packag
Timo: It doesn't fail on Debian. See the "That works in Debian
because.." in the description (TL/DR: Debian doesn't enable ssh.socket,
but ssh.service, which sets up the symlink)
** Description changed:
Joining a FreeIPA domain reconfigures SSH. E.g. it enables GSSAPI
authentication in /etc/s
Public bug reported:
Joining a FreeIPA domain reconfigures SSH. E.g. it enables GSSAPI
authentication in /etc/ssh/sshd_config.d/04-ipa.conf . After that, it
tries to restart sshd, but that fails as "sshd.service" is not a thing
on Ubuntu:
2024-04-12T03:10:57Z DEBUG args=['/bin/systemctl', 'is-act
Yay, today this is finally fixed, pbuilder creation and building a noble
VM image finally works again \o/ Thanks!
** Changed in: perl (Ubuntu Noble)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is s
Aside from curl this can be reproduced most quickly with
sudo /usr/sbin/debootstrap --include=build-essential noble /tmp/n
http://archive.ubuntu.com/ubuntu
Errors were encountered while processing:
perl
libdpkg-perl
libperl5.38t64:amd64
dpkg-dev
build-essential
These are all ultimately du
I wonder where that comes from --
https://launchpad.net/ubuntu/+source/perl/+publishinghistory says that
5.38.2-3 was deleted, but only from noble-updates. In noble proper it is
merely "superseded". https://launchpad.net/ubuntu/+source/perl/5.38.2-3
doesn't show it being published anyway, and it's
Public bug reported:
For the last two weeks, building noble VM images for our CI has been
broken. Most of it was uninstallability due to the xz reset, but for the
last three days, `pbuilder --create` has failed [2] because it gets perl
and perl-modules-5.38 in two different versions:
2024-04-08 0
** Changed in: ubuntu-mate-meta (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2017786
Title:
update script in ubuntu-meta not
tus in gnutls28 source package in Noble:
Won't Fix
Status in libvirt source package in Noble:
Won't Fix
Bug description:
Christian summarizes this after the great reports by Martin:
gnutls started to ship forceful disables in pkg/import/3.8.1-4ubuntu3
and added more later
Just to make sure that we really talk about the same thing: This bug
sounds like it is *intended* that
unshare --user --map-root-user /bin/bash -c whoami
(as unpriv user) now fails in current Ubuntu 24.04 noble. That still
worked in released 23.10.
I am starting to test Cockpit on the curren
Public bug reported:
There is an AppArmor regression in current noble. In cockpit we recently
started to test on noble (to prevent the "major regressions after
release" fiasco from 23.10 again).
For some weird reason, rsyslog is installed *by default* [1] in the
cloud images. That is a rather poi
Having the same issue as in #7 (id: ‘polkitd’: no such user, chown:
invalid group: ‘root:polkitd’). Managed to apply workaround to move with
the test upgrade from this stuck place by creating polkitd system group
using `groupadd -r polkitd`.
--
You received this bug notification because you are
Fun, this isn't even reliable. The first atttempt failed:
https://cockpit-logs.us-east-1.linodeobjects.com/image-refresh-
logs/ubuntu-stable-20231219-223939.log
I retried the build now, no package or environment changes. Only daytime
and timing (race conditions). Perhaps some interaction with
Argh -- I missed the alternative truth in that rescue-ssh.target shell
code. So this message should pretty much *always* appear -- it's
nonsense to actually try and restart rescue-ssh.target in the postinst,
*always*.
But it is a red herring due to the || true. The upgrade failed on
something else
Public bug reported:
In our project we regularly build Ubuntu VM images for current 23.10
(stable). In https://github.com/cockpit-project/bots/issues/5691 we ran
into an upgrade failure of openssh-server. It starts with the current
cloud image and then apt upgrades it, with
"DEBIAN_FRONTEND=nonint
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/2037703
Title:
dpkg-reconfigure openssh-server doesn't ask questions again
Status in openssh package in Ubuntu:
New
Bug d
We just ran into this in https://github.com/cockpit-
project/bots/issues/5691 when trying to refresh our Ubuntu 23.10 mantic
VM image. It starts with the current cloud image and then apt upgrades
it, with "DEBIAN_FRONTEND=noninteractive". openssh was updated a few
days ago indeed:
Setting up ope
Excellent, thanks Danilo for the super fast fix! ⭐
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2046158
Title:
Updating wireguard-peer.allowed-ips gets wrong def
** Description changed:
In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only connection:
# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
- version: 2
- tunnels:
- wg0:
- ren
Public bug reported:
In https://cockpit-project.org/ we have an integration test for
NM+wireguard integration. That test starts with an IPv4-only connection:
# cat /etc/netplan/90-NM-b5edee2d-c736-4827-bae3-c95e349cb73b.yaml
network:
version: 2
tunnels:
wg0:
renderer: NetworkManager
I also tried
aa-disable usr.bin.crun
but that doesn't work either. I guess it's not really crun, but
profile="containers-default-0.50.1", but that is created dynamically --
it's not anywhere in /etc/apparmor.d/. I grepped the whole file system
for that:
grep: /usr/lib/podman/rootlessport: bi
I tried a more targeted workaround, with
aa-complain /etc/apparmor.d/usr.bin.crun
or alternatively (without apparmor-utils, which isn't on the default
cloud image):
sed -i '/flags=/ s/unconfined/complain/' /etc/apparmor.d/usr.bin.crun
but for some reason that breaks podman entirely:
# podm
Public bug reported:
when I paste filename into the location bar (Ctrl+L) the file chooser
hangs.
The file happens to be in a folder with 30 other files and
GtkFileChooserDialog
tries to offer a filename typing suggestion dropdown which is slow and
eventually crashes.
When I then kill chro
Public bug reported:
root@localhost:/home/larsmartin# sudo apt update && sudo apt upgrade
Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease
Hit:2 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
Hit:3 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
Hit:4 http://archive.ubun
works to error when manage this file:
libgpod-common
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2044602
Title:
did not works to upgrade to 23.10
Status in apt package in
look like sudo dpkg --configure -a works to get it install? None
information about it?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/2044602
Title:
did not works to upgrade t
Also issue when select LightDM or gmd3 computer get black screen most reboot.
Nvidia grapic card GTX 1080 TI.
when i remove ubuntu-desktop libgpod-common need libsgutils2-1.46-2 (>= 1.27)
use «apt --fix-broken install
--
You received this bug notification because you are a member of Ubuntu
Tou
** Attachment added: "issue.png"
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2044602/+attachment/5723408/+files/issue.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bug
Public bug reported:
I have issue after upgrade its did not works
apt --fix-broken install
vil kanskje kjøre «apt --fix-broken install» for å rette på dette.
Følgende pakker har uinnfridde avhengighetsforhold:
libgpod-common : Avhenger av: libsgutils2-1.46-2 (>= 1.27) men er ikke
installert
E
Similar issue: https://gitlab.com/libvirt/libvirt/-/issues/548 . These
two may want a common fix with "allow qemu to read sysfs"?
** Bug watch added: gitlab.com/libvirt/libvirt/-/issues #548
https://gitlab.com/libvirt/libvirt/-/issues/548
--
You received this bug notification because you are
The process is Intellij IDEA, running on Java 17 in Xwayland.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2037641
Title:
amdgpu: [gfxhub0] no-retry page fault
Status in l
Unfortunately the problem is still reproducible even with the newest
mesa, even though it looks like it's much less frequent. Yesterday
evening I got another crash, with mesa 23.2.1-1ubuntu2:
```
2023-10-04T22:33:15.415854+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119146]
amdgpu :06:00.0: amdgp
Thanks Mario! I checked, and I have the newest mesa:
```
$ apt search mesa-vdpau
Sorting... Done
Full Text Search... Done
mesa-vdpau-drivers/mantic,now 23.2.1-1ubuntu2 amd64 [installed,automatic]
Mesa VDPAU video acceleration drivers
```
Funny thing is that the bug is no longer reproducible - e
There's a difference between "this package is required to allow people
to use our paid services" and "this package spams everyone who doesn't
pay for our paid services". This flies in the face of the whole ethos of
free software imo.
--
You received this bug notification because you are a member
Public bug reported:
martin@studio-as6:~$ sudo dmesg | egrep -i 'blue|firm'
[0.119642] Spectre V2 : Enabling Restricted Speculation for firmware calls
[0.278739] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[2.462372] [drm] Loading DMUB firmware via PSP: version=
Public bug reported:
sdo do-release-upgrade
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-75-generic 5.15.0-75.82
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvp
There is downstream software depending on python3-packaging to work
correctly. That library is affected, too, because it checks for strict
compliance to PEP 440. And, obviously, it can't be fixed by fixing the
packaging library, as it does its work correctly.
Example downstream usage: https://gith
> Setuptools is not in bionic
I don't understand. I clearly see it there:
https://webcache.googleusercontent.com/search?q=cache:fZGhFT_sSb8J:https://packages.ubuntu.com/bionic/python-
setuptools . Or am I missing something?
--
You received this bug notification because you are a member of Ubuntu
1) isc-dhcp-client doesn't do IPv6 well and cannot handle a dual-stack
case at all.
2) isc-dhcp-client is EOL upstream.
3) https://bugs.launchpad.net/ubuntu/+source/dhcpcd5/+bug/2019191
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subs
Could it Depends on dhcp-client and let APT decide which package
providing this has the highest priority?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2019722
Title:
Public bug reported:
ubuntu-minimal currently has a hard Depends on isc-dhcp-client. Unless
there is a compelling reason to depend on a specific DHCP
implementation, this should be changed to "isc-dhcp-client | dhcp-
client" instead.
** Affects: ubuntu-meta (Ubuntu)
Importance: Undecided
> We ship setuptools in Ubuntu, and the version of setuptools shipped
in these releases does not trigger the issue.
It does for me (on Bionic).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu.
https://bugs
https://github.com/martinpitt/umockdev/issues/208
Thanks Heinrich!
** Bug watch added: github.com/martinpitt/umockdev/issues #208
https://github.com/martinpitt/umockdev/issues/208
** Changed in: umockdev (Ubuntu)
Status: New => In Progress
--
You received this bug notification becaus
Hello,
On Ubuntu desktop 22.04 LTS, it seems that the hook is not executed. I'm
not sure how to verify that but sure thing is the DHCP is well
announcing the ntp server.
DHCP4.OPTION[8]:ntp_servers = X.X.X.X
DHCP4.OPTION[18]: requested_ntp_servers = 1
Ah, now I get it, thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-debian in Ubuntu.
https://bugs.launchpad.net/bugs/1991606
Title:
Invalid PEP440 package version breaking setuptools >= 60
Status in devscript
> Changed in python-debian (Ubuntu Bionic):
> status: New → Invalid
Can I ask about this change? How is it invalid for bionic? The name of
the package is wrong there, too... (for both python-distro-info an
python3-distro-info).
--
You received this bug notification because you are a membe
** Changed in: software-properties (Ubuntu)
Status: Expired => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1830914
Title:
software-properti
@dexter in #1, I also tried moving the `import requests_unixsocket` line
up out of the try-except block, and also found that it worked. (None of
the other proposed solutions, including reinstalling all of the proposed
packages, had any effect). Strangely, afer *undoing* those change, i.e.
moving th
I think this might be related:
journalctl -p 3 -xb
nov 15 12:53:55 cinnamon systemd-udevd[643]: event6: Failed to call
EVIOCSKEYCODE with scan code 0x7c, and key code 190: Invalid argument
sudo cat /proc/bus/input/devices | grep -C 5 event6
I: Bus=0019 Vendor= Product= Version=
N: N
Same for me on Ubuntu Mate 22.04 5.15.0-52-generic and Cinnamon 5.2.7
/etc/X11/Xsession.d/30x11-common_xresources: ligne 16: has_option : commande
introuvable
/etc/X11/Xsession.d/75dbus_dbus-launch: ligne 9: has_option : commande
introuvable
--
You received this bug notification because you are
** Summary changed:
- apt-add-repository fails if it encounters immutable sources.list.d entry
+ add-apt-repository fails if it encounters immutable sources.list.d entry
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to softwar
Public bug reported:
Reason:
We're trying to protect an internal APT source from trivial accidental
modification by users (who do have sudo as root).
Steps to reproduce:
echo '# dummy' > /etc/apt/sources.list.d/dummy.list
chattr +i /etc/apt/sources.list.d/dummy.list
add-apt-repository -y ppa:lo
Public bug reported:
s
ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-52-generic 5.15.0-52.58
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
Uname: Linux 5.15.0-52-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.
Public bug reported:
It seems that the current network-manager in Ubuntu 22.10 would like to
use iwd per default after the upgrade.
However, there's no dependency to the iwd package resulting in a lack of
wifi support after the upgrade.
** Affects: network-manager (Ubuntu)
Importance: Undec
I hit this too in my upgrade from 20.04 to 22.04.
I think it's because I had old commercial amdgpu drivers installed:
$ cat /etc/apt/sources.list.d/amdgpu.list
deb https://repo.radeon.com/amdgpu/22.10.2/ubuntu focal main
#deb-src https://repo.radeon.com/amdgpu/22.10.2/ubuntu focal main
I change
D'oh!
# cat /etc/ssh/sshd_config.d/10-cloudimg-settings.conf
PasswordAuthentication no
rm + restart sshd, everything is hunky-dory. Sorry for the noise!
** Changed in: openssh (Ubuntu Kinetic)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubun
I set LogLevel=DEBUG in /etc/ssh/sshd_config, systemctl restart sshd,
and I'm none the wiser:
debug1: Forked child 1652.
debug1: Set /proc/self/oom_score_adj to 0
debug1: rexec start in 5 out 5 newsock 5 pipe 7 sock 8
debug1: inetd sockets after dupping: 4, 4
Connection from 127.0.0.1 port 45396 o
Public bug reported:
I am in the process of updating our CI for Cockpit to kinetic [1]. I get
a lot of test failures because SSH password login is broken.
This can be replicated with a clean cloud instance, so it's not
something that our VM build scripts do:
curl -L -O
https://cloud-images.ub
Does dhcpcd5 version 9.4.1-0.1 solve the issue for you?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1713803
Title:
replacement of resolvconf with systemd needs
We're seeing this same issue. The postinst script in the 22.04 package
seems to be missing a few lines that were still there in 21.10, one of
which would be the one that executes systemctl enable pcscd.socket.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded p
@bkanbach I can version marco Recommends ensuring both packages update
in lockstep. I have spoken to the Ubuntu Security team and they will
handle the CVE assignment.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in
** Changed in: arctica-greeter (Ubuntu)
Status: In Progress => Fix Committed
** Changed in: marco (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
** Changed in: arctica-greeter (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1948339
Title:
Logon screen can be bypassed us
** Changed in: marco (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1948339
Title:
Logon screen can be bypassed using variou
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu-mate
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1892299
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu-mate
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1837765
** No longer affects: ubuntu-mate
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1874689
Title:
alsa force-reload needed to fix my sound after upgrade to 20.04
Status
** Changed in: ubuntu-mate-meta (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1706770
Title:
Lock screen can be bypas
1 - 100 of 1017 matches
Mail list logo
