Looks like same error with 1.7.x and 1.8.x using sof-tgl.ri
[2.993700] sof-audio-pci :00:1f.3: SoundWire enabled on CannonLake+
platform, using SOF driver
[2.993714] sof-audio-pci :00:1f.3: enabling device ( -> 0002)
[2.993959] sof-audio-pci :00:1f.3: DSP detected
Missing file now. (sof-tgl.ri)
[2.977845] snd_hda_intel :00:1f.3: DSP detected with PCI
class/subclass/prog-if info 0x040100
[2.978089] snd_hda_intel :00:1f.3: SoundWire enabled on CannonLake+
platform, using SOF driver
[2.978153] snd_hda_intel :01:00.1: enabling
Removed the link for sof-tgl-h.ri in /lib/firmware/intel/sof/. No
errors about file not found. Same error as above.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
Tried sof-tgl-h.ri 1.7 and 1.8 signed and RC2 of both. Speakers are
still showing dummy output. Still getting:
[5.999872] sof-audio-pci :00:1f.3: error: firmware boot failure
[5.999879] sof-audio-pci :00:1f.3: status: fw entered - code 0005
[5.999885] sof-audio-pci
Public bug reported:
No audio/mic from internal speakers/build in microphone running Ubuntu
20.04, 20.10 or 21.04 . Can connect via USB headset and audio will
work. Tried suggestions from Dell XPS 17 (9700) but this is the new
model and fixes do not work. Currently running 21.04 with
> Other than the obvious approach of enabling systemd-userdb for Ubuntu,
I don't see how that would help, given that sytemd-userdb.service has
RestrictAddressFamilies=AF_UNIX AF_NETLINK AF_INET AF_INET6
You basically have the same issue as with systemd-logind.service. Or am I
missing
1) Include drop-in conf files for systemd-logind and systemd-udevd to
remove the networking sandbox
Those drop-in configs should be shipped in the nis package. I don't see
a reason to ship a drop-in for systemd-udevd, fwiw.
--
You received this bug notification because you are a member of
I can confirm that installing nscd also solves the problem without
needing to fiddle with the systemd-logind restrictions. However, I am no
fan of nscd. Caching passwords for ten minutes (its default) causes all
sorts of confusion when a user changes his password, or requests a
password reset, for
** Bug watch added: Debian Bug tracker #878625
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878625
--
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/1915502
Title:
See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=878625
Am Do., 10. Juni 2021 um 20:23 Uhr schrieb Michael Biebl :
>
> The relevant upstream bug report afaics is
> https://github.com/systemd/systemd/issues/7074
>
> Am Do., 10. Juni 2021 um 20:14 Uhr schrieb Michael Biebl
The relevant upstream bug report afaics is
https://github.com/systemd/systemd/issues/7074
Am Do., 10. Juni 2021 um 20:14 Uhr schrieb Michael Biebl :
>
> Am Do., 10. Juni 2021 um 14:50 Uhr schrieb Dan Streetman
> <1915...@bugs.launchpad.net>:
> >
> > Ok, so it does soun
Am Do., 10. Juni 2021 um 14:50 Uhr schrieb Dan Streetman
<1915...@bugs.launchpad.net>:
>
> Ok, so it does sound like this and bug 1916235 are the same issue. And
> this might be 'as designed', since upstream systemd wants systemd-logind
> to talk to systemd-userdb instead of directly connecting to
Thanks for that. I can confirm that
systemctl daemon-reload; systemctl restart systemd-logind
(in that order) avoids the need for a reboot, and for a couple of my
machines I am very grateful for this information.
--
You received this bug notification because you are a member of Ubuntu
Touch
A little more information, after some investigation.
The issue affects xdm logins at the console, as well as remote ssh
logins. This also means that audio at the console fails to work, as ACLs
for the console's user are not added to the audio devices.
It seem that it can be solved by putting in
workaround: sudo apt purge libtss2-esys0 libsrt1-gnutls manpages-de
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1539689
Title:
package lvm2 2.02.133-1ubuntu4 failed to
This looks mostly ok but the merge doesn't seem to account for the
apport hooks being in debian now -- the changelog still lists it as a
difference, the package-hooks dir is in the .dirs files twice, and I
think they might be installed twice.
--
You received this bug notification because you are
Fixed in 0.140ubuntu2.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Fix Released
--
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/1926658
Title:
Public bug reported:
After updating the initramfs-tools 0.140ubuntu1, the system no longer
boots. Instead, the busybox shell is started. The error says that
"/init" cannot be started due to error -13.
In investigated and figured out that the error occurs because the
That said, we could fix this issue in curtin by searching for a device
with specified serial by just looking through the udev db directly
rather than by globbing in /dev/disk/by-id. In fact I thought we already
did that! But apparently not.
--
You received this bug notification because you are a
The upstream bug request has a PR that seems to fix the issue already. I
guess if it gets accepted upstream we can think about backporting the
fix to stable releases in the fullness of time.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
On the first login of the week, xdm (1.1.11-3ubuntu2) fails to start on
Ubuntu 20.04.
More correctly, it does start, but exits almost immediately on signal
12. It leaves /var/run/xdm.pid behind, and also a running X server with
no clients. This makes it hard to restart, for
** Package changed: snapd (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/1920107
Title:
Failed messages of sd-umoun show with reboot/shutdown
Much appreciated, thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1922464
Title:
GNOME 40: GTK3 apps crash with: Settings schema 'org.gnome.settings-
As you're no doubt aware, using a PPA is at the moment the only way to
use GNOME 40 without compiling it from scratch or switching to another
distro. However the PPA does not ship GTK3, only GTK4 - hence this is a
bug in an Ubuntu package.
Since this bug occurs in Ubuntu's packaged version of
A good idea, but it made no difference for me. I even went a little
further and tried
[Service]
RestrictAddressFamilies=AF_INET
IPAddressAllow=any
SystemCallFilter=
ProtectSystem=off
CapabilityBoundingSet=
but still no change, even after a reboot. Logins produce the pair of
lines
Apr 5
I just rebuilt the current packaged version of GTK 3 with the patch from
the MR and can confirm it fixes the crash.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1922464
Public bug reported:
Applications running with GTK < 3.24.26 crash when running under GNOME
40. This was fixed in GTK 3.24.26 by MR
https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/3219
Please package either current GTK 3 (3.24.28) or include the given MR in
the current build.
Thanks!
I think I am suffering from the same issue.
I have always run without "UsePAM yes" in sshd_config, but I recently
tried turning it on in order to get XDG_ variables set correctly and
proper systemd sessions for ssh logins.
In 18.04 it worked as expected, but in 20.04 I get
sshd[387766]:
*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794
Correction to #81, I meant to say on the A2DP I've got no microphone (as
I understand it this is expected as A2DP is unidirectional) and on the
HSP/HFP profile I have access to the microphone, but the audio
*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794
I'm experiencing this issue as well. On the HSP/HFP profile, the audio
output comes through crystal clear, but the microphone is lost. On the
A2DP profile, I get the microphone back, but the sound quality
I can confirm that I am seeing this same behavior. The proposed fix also
worked for me.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1901373
Title:
isc-dhcp-server
Fwiw, mysql-8.0 is also affected:
$ dpkg -c libmysqlclient21_8.0.23-3_amd64.deb|grep buildd
drwxr-xr-x buildd/buildd 0 2021-02-11 10:32 ./
[many more]
And some more:
$ dpkg -c libqt5xdg3_3.6.0-1ubuntu2_amd64.deb |grep buildd
-rw-r--r-- buildd/buildd 268440 2021-02-11 21:58
Thanks, this looks good to me but out of an abundance of caution (this
is sudo, after all), I'm going to get Marc from the security team to
take a look -- it seems the upstream fixes for the CVE are a bit
different from the ones currently in Ubuntu and I'd like him to verify
that we think upstream
Hi, this looks mostly very good! I have some tiny nitpicks:
1) It's good to mention the patches that are being dropped in the changelog
entry.
2) There are some whitespace changes in the bottom of the changelog that you
could drop if you felt like it.
--
You received this bug notification
After discussing this we decided that we will leave cgroups v1 support
for 21.04 because the snapd team will not be able to port all features
to v2 in time. But early in the 21.10 cycle v1 is turned off and snapd
needs to be ported to full v2 support.
--
You received this bug notification
These seem to have both passed on retry...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to vim in Ubuntu.
https://bugs.launchpad.net/bugs/1891486
Title:
vim ftbfs in focal (armhf, ppc64el)
Status in vim package in Ubuntu:
@rbalint Thanks for this heads up. Unfortunately we are not ready for
cgroups v2. Snapd is working on v2 systems but a lot of the
functionality is not ported. AIUI it requires quite a bit of work on our
side and the two are quite different :/
--
You received this bug notification because you are
@rbalint Do you have a timeline when you plan this? The changes required
make this most likely something we can only tackle during the 21.10
cycle :/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
I can't reproduce this anymore.
I'm not sure what changed in the two weeks since the last message.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
https://bugs.launchpad.net/bugs/1906101
Title:
no
*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794
Problem has been fixed for my setup:
- Kernel: 5.4.0-56-generic
- OS: Xubuntu 20.04.01 LTS
- Machine: HP-ZBook-14u-G6
- Headset: FreeVoice Space Stereo
--
You received this bug notification because you
Problem has been fixed for my setup:
- Kernel: 5.4.0-56-generic
- OS: Xubuntu 20.04.01 LTS
- Machine: HP-ZBook-14u-G6
- Headset: FreeVoice Space Stereo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
I can confirm this same bug while using DisplayPort output on an AMD R5
240 OEM. I'm using Mint 19 (Ubuntu 18.04)
--
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/1810574
@Sebastien I will test it today. Sorry for the delay
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1899262
Title:
Broken dbus GetAll message to wpa supplicant interface
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1906101/+attachment/5440190/+files/acpidump.txt
** Changed in: alsa-lib (Ubuntu)
Status: New => Confirmed
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1906101/+attachment/5440189/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1906101/+attachment/5440188/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
It seems I may have spoken too soon. A couple of days following my
previous message, I have no sound again.
I'll run apport-collect and update the bug as the bot requested.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1906101/+attachment/5440187/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1906101/+attachment/5440186/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1906101/+attachment/5440185/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1906101/+attachment/5440184/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1906101/+attachment/5440182/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1906101/+attachment/5440183/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1906101/+attachment/5440177/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1906101/+attachment/5440175/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1906101/+attachment/5440181/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1906101/+attachment/5440176/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1906101/+attachment/5440174/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1906101/+attachment/5440180/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1906101/+attachment/5440179/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1906101/+attachment/5440178/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1906101/+attachment/5440173/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-lib in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
I recently upgraded from 18.04 to 20.04. The sound worked without
problems before upgrade, but now I don'get any sound at all from the
speakers or the headphone jack.
This seems similar to
I managed to get sound working by following the steps here:
https://help.ubuntu.com/community/SoundTroubleshooting
More specifically, I ran this command:
sudo apt --purge reinstall linux-sound-base alsa-base alsa-utils
linux-image-`uname -r` libasound2
After a restart, sound was available
** Summary changed:
- no sound via speakers or headphone port on Carbon X1
+ no sound via speakers or headphone port on Carbon X1 6th
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
Public bug reported:
I recently upgraded from 18.04 to 20.04. The sound worked without
problems before upgrade, but now I don'get any sound at all from the
speakers or the headphone jack.
This seems similar to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860697 (although
that bug is
Public bug reported:
Attempted to uninstall AisleRiot Solitaire which was preinstalled with
Ubuntu 20.04. Received an error that the process was locked by aptd,
rebooted, retried, crashed.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: tzdata 2020d-0ubuntu0.20.04
ProcVersionSignature:
apport information
** Attachment added: "RebootRequiredPkgs.txt"
https://bugs.launchpad.net/bugs/1905076/+attachment/5436630/+files/RebootRequiredPkgs.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1905076/+attachment/5436624/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1905076/+attachment/5436625/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1905076/+attachment/5436629/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1905076/+attachment/5436628/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
apport information
** Attachment added: "PaInfo.txt"
https://bugs.launchpad.net/bugs/1905076/+attachment/5436626/+files/PaInfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1905076/+attachment/5436627/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in
apport information
** Attachment added: "AudioDevicesInUse.txt"
https://bugs.launchpad.net/bugs/1905076/+attachment/5436623/+files/AudioDevicesInUse.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in
apport information
** Tags added: apport-collected groovy
** Description changed:
Loading the pulseaudio module 'module-alsa-sink' with the "control"
argument causes pulseaudio to segfault on my system.
In /etc/pulse/default.pa find this line:
#load-module module-alsa-sink
Public bug reported:
Loading the pulseaudio module 'module-alsa-sink' with the "control"
argument causes pulseaudio to segfault on my system.
In /etc/pulse/default.pa find this line:
#load-module module-alsa-sink
and change it to this:
load-module module-alsa-sink control=Master
then restart
Nice to see it works for 20.10.
however, I'd like to keep on the LTS version and expect to get a fix soon.
--
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/1871794
Title:
Dear Sebastian, the problem that the station patch was backported
already but wrongly. I have just fixed in this package
This is coming from change log
wpa (2:2.6-15ubuntu1) bionic; urgency=low
* Merge from Debian unstable. Remaining changes:
-
Are you using ubuntu 18.04? or are you using Focal Fossa?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1899262
Title:
Broken dbus GetAll message to wpa supplicant interface
debdiff show the difference between the 18.04 ubuntu. In the 20.04 wpa
supplicant was bump to newer version so station attribute was added in
the right way
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
As I said Interfaces/1 or /2 or /3 depends on how they are enumerated.
That is just an example
Using d-feet to find your interface. Today is /4 on my laptop (and must
be a wifi)
** Attachment added: "Screenshot from 2020-11-03 17-25-40.png"
org.freedesktop.DBus.Properties.GetAll
string:fi.w1.wpa_supplicant1.Interface
[sudo] password for michael:
method return time=1603398113.528196 sender=:1.4 -> destination=:1.267
serial=476 reply_serial=2
array [
dict entry(
string "Capabilities"
variant
** Changed in: autofs (Ubuntu)
Status: Incomplete => Invalid
** Changed in: autofs (Ubuntu Focal)
Status: Incomplete => Invalid
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
** Changed in: systemd (Ubuntu Focal)
Status: Incomplete => Invalid
--
You
This error has gone with the latest updates, but, unfortunately, I still
have the same transient issues with autofs. I see some other strange
things in logs and will continue investigation on my side. I think this
ticket can be closed (I will open a new ticket if any). Thank you a lot.
--
You
wpa_supplicant exponse properties of the interface that you can read
using dbus command such as. Now if the property is empy you should just
expose as empty and not fail as it is in the code.
sudo dbus-send --system --print-reply --dest=fi.w1.wpa_supplicant1
/fi/w1/wpa_supplicant1/Interfaces/1
** Changed in: wpa (Ubuntu)
Assignee: (unassigned) => Michael Nazzareno Trimarchi
(michael-t16qijz8x59bnuup5)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1899262
Ti
Public bug reported:
When installed within the `ubuntu` Docker container, `tzdata` sets
`etc/timezone` to `/UTC`, not `Etc/UTC`, which breaks applications that
are reading `etc/timezone` and expecting a valid timezone name.
I'm guess that this wasn't noticed, since technically
** Patch added:
"0001-dbus-Fix-GetAll-message-if-ap_ifaces-are-not-availab.patch"
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1899262/+attachment/5420793/+files/0001-dbus-Fix-GetAll-message-if-ap_ifaces-are-not-availab.patch
--
You received this bug notification because you are a
The attach is a debdiff. If it's not fine let me know
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1899262
Title:
Broken dbus GetAll message to wpa supplicant interface
Public bug reported:
dbus-send is able to read the properties of interface using GetAll. Those
information include interface name, status, encryption method, etc.
The regression was introduced when someone try to have the Station attribute
supported
** Affects: wpa (Ubuntu)
Importance:
Public bug reported:
dbus-send is able to read the properties of interface using GetAll. Those
information include interface name, status, encryption method, etc.
The regression was introduced when someone try to have the Station attribute
supported
** Affects: wpa (Ubuntu)
Importance:
Thank you a lot for this investigation, I'll try to reproduce with these
parameters and with new version on this week.
--
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/1880193
And verified on xenial:
(client-server-5)mwhudson@anduril:~/src/subiquity$ ssh ubuntu@10.187.142.193
"sh -c 'dpkg-query -W libpam-modules; type go '"
libpam-modules:amd641.1.8-3.2ubuntu2.1
go: not found
(client-server-5)mwhudson@anduril:~/src/subiquity$ lxc exec lp1659719-xenial --
apt
Verified the new upload on xenial:
root@xenial-pam-play:~# dpkg -l libpam-modules
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name
** Changed in: pam (Ubuntu Xenial)
Status: Won't Fix => In Progress
** Changed in: pam (Ubuntu Xenial)
Assignee: Don van der Haghen (donvdh) => Michael Hudson-Doyle (mwhudson)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Same problem affects me on Ubuntu 20.04 system. I have wifi adapter configured
as hotspot. The hotspot also seems to be working normally but the log files are
full of messages:
wpa_supplicant[1359]: wlp9s0: CTRL-EVENT-SCAN-FAILED ret=-95 retry=1
Best regards,
Michael.
--
You received this bug
Turns out, the missing fsck progress bar is a regression:
https://github.com/systemd/systemd/issues/17157
** Bug watch added: github.com/systemd/systemd/issues #17157
https://github.com/systemd/systemd/issues/17157
--
You received this bug notification because you are a member of Ubuntu
>From my personal POV, I consider the progress bar more important then the
>ability to interrupt fsck with CTRL+C.
Nowadays, SSDs are much more common and enable_periodic_fsck = 0 has been the
default for many years now. So this is much less of an issue today then it was
back in 2015, I think.
As for text-only boot: Maybe we could convince upstream to enable
verbose mode once an fsck takes longer then say 30s (similar to how the
eye-of-cyclon animation kicks in when services take a long time to
start). With something like that implemented, dropping fsckd might be an
option, I think.
--
201 - 300 of 4360 matches
Mail list logo
