DistroRelease: Kali 2.0
Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support or fix your particular bug.
DistroRelease: Kali 2017.1
Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support or fix your particular
DistroRelease: Kali 2017.1
Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support or fix your particular
DistroRelease: Kali 2017.1
Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support or fix your particular
DistroRelease: Kali 2016.2
Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support or fix your particular
libjpeg8:amd64 (8d1-2)
Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support or fix your particular bug.
DistroRelease: Kali 2016.2
Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support or fix your particular
DistroRelease: Kali 2016.1
libjpeg8-dev:amd64 (8d1-2)
Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not
DistroRelease: Kali 2016.1
libjpeg8:amd64 (8d1-2)
Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support or
The attachment "procps debdiff for Groovy" seems to be a debdiff. The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag,
** Summary changed:
- Bluetooth is disabled in gui, but audio reciever's action button still
controls Ubuntu
+ Intel Wireless 8260 [8086:24f3] Subsystem [8086:9010] Bluetooth is disabled
in gui, but audio reciever's action button still controls Ubuntu
--
You received this bug notification
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1659719
Title:
ssh can't call a binary from a snap without the full path
Status in Snappy:
Fix
DistroRelease: SparkyLinux 4
libjpeg8:amd64 (8d1-2)
Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support
** Tags added: hwe-bluetooth
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1885496
Title:
Intel Wireless 8260 [8086:24f3] Subsystem [8086:9010] Bluetooth is
disabled in
libjpeg8:amd64 (8d1-2)
Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not support or fix your particular bug.
DistroRelease: Kali 2018.2
libjpeg8:amd64 8d-1+deb7u1
Thank you for taking the time to report this bug and trying to help make
Ubuntu better. However, it seems that you are not using a software
package provided by the official Ubuntu repositories. Because of this
the Ubuntu project can not
Public bug reported:
Description:Ubuntu 18.04.4 LTS
Release:18.04
systemd-resolve --version
systemd 237
+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN
-PCRE2 default-hierarchy=hybrid
It's easy enough to unconditionally add /snap/bin to path, see attached,
but I can't really see a clean way to only have it present in the $PATH
when snapd is installed (without code changes to pam_env, anyway).
** Patch added: "pam_1.3.1-5ubuntu4_1.3.1-5ubuntu5.patch"
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1886115/+attachment/5389206/+files/UdevDb.txt
** Description changed:
After applying updates to Ubuntu 18.04 my desktop (apple mini with
i5-2415M CPU) failed to complete the boot process. A few
apport information
** Attachment added: "SystemdFailedUnits.txt"
https://bugs.launchpad.net/bugs/1886115/+attachment/5389205/+files/SystemdFailedUnits.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
apport information
** Attachment added: "SystemdDelta.txt"
https://bugs.launchpad.net/bugs/1886115/+attachment/5389204/+files/SystemdDelta.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1886115/+attachment/5389207/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1886115/+attachment/5389208/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1886115/+attachment/5389196/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1886115/+attachment/5389197/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1886115/+attachment/5389202/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1886115/+attachment/5389199/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1886115/+attachment/5389203/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1886115/+attachment/5389201/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1886115/+attachment/5389198/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1886115/+attachment/5389200/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
apport information
** Tags added: apport-collected bionic
** Description changed:
After applying updates to Ubuntu 18.04 my desktop (apple mini with
i5-2415M CPU) failed to complete the boot process. A few seconds into
the boot, the last message displayed is "/var mounted". The system
Attached is a debdiff for procps on Groovy. It adds a commented out
entry to 10-kernel-hardening.conf which users can use to disable the
setting if they wish.
** Patch added: "procps debdiff for Groovy"
> have you customised the syscall filtering in this profile at all?
Don't know what you mean by profile there. The OS runs on bare-metal here.
The only related modification I made has been (now) the reported commenting-out
of
--8<--
SystemCallFilter=~@clock @cpu-emulation @debug @keyring
You can specify the package name using `-p` - so perhaps:
apport-collect -p systemd 1886115
apport-collect -p libseccomp2 1886115
Would do the trick?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Description changed:
- target machine does not have built-in speaker, and the monitor does not
- have an audio output (like d-sub VGA)
+ For linux kernel (oem-b):
+
+ [Impact]
+ On a Dell machine without internal spk and internal mic, after freshly
+ install the bionic on it, and users plug a
If this is indeed related to the Gentoo bug, I cannot see anywhere in
libseccomp where the environment is being modified. As such I suspect
this is likely actually a bug in systemd where it is modifying the
environment across the exec() and the libseccomp update has just caused
it to actually
This bug was fixed 11 years ago. Please open a new bug for any new
problem you are having.
--
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/320875
Title:
pulseaudio
The first package I wanted to try was matterhorn -- I had some trouble
with it earlier today and this was an excellent opportunity to report
the bug 'formally', beyond just a pastebin on irc:
$ ubuntu-bug matterhorn
*** Collecting problem information
The collected information can be sent to the
> apport-collect 1886115
That doesn't seem to succeed (because the installed package is libseccomp2, but
here listed as libseccomp since the former isn't known to launchpad).
I tried
$ apport-bug -u 1886115 libseccomp2
but that appears to attempt to create a new bug, rather then updating the
*** This bug is a duplicate of bug 1867668 ***
https://bugs.launchpad.net/bugs/1867668
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1867668, so it is being marked as such. Please
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1882248
and then change the status of the bug to 'Confirmed'.
If, due to the
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1885496
Title:
Bluetooth is
bluetoothd still running is correct and not a bug. Also, rfkill appears
to show that the GUI/BlueZ has disabled the kernel device as much as it
can:
0: hci0: Bluetooth
Soft blocked: yes
So this is either a kernel bug or something missing from BlueZ's soft-
blocking support.
** Changed
I think we need help from a systemd expert.
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Also affects: oem-priority/bionic
Importance: Undecided
Status: New
** No longer affects: oem-priority/bionic
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: pulseaudio (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also
We don't support Unity8 now and have no way to verify or test it.
** Changed in: unity8 (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: qtdeclarative-opensource-src (Ubuntu)
Status: New => Won't
To capture some more details that might help debug this issue, could you
please run
apport-collect 1886115
in a terminal? This should automatically capture various details and
upload them to this bug report.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Thanks for reporting this issue. I am not able to reproduce it myself -
have you customised the syscall filtering in this profile at all?
** Changed in: libseccomp (Ubuntu)
Assignee: (unassigned) => Alex Murray (alexmurray)
--
You received this bug notification because you are a member of
Public bug reported:
After applying updates to Ubuntu 18.04 my desktop (apple mini with
i5-2415M CPU) failed to complete the boot process. A few seconds into
the boot, the last message displayed is "/var mounted". The system then
appears to hang indefinitely.
Luckily, the 'rescue' boot
Public bug reported:
[Impact]
This bug implements the enablement of CONFIG_SECURITY_DMESG_RESTRICT
feature by default for Groovy onward, proposed to ubuntu-devel:
https://lists.ubuntu.com/archives/ubuntu-devel/2020-June/041063.html
The kernel log buffer contains a wealth of sensitive
Kernel is fix-committed as per:
Mailing list:
https://lists.ubuntu.com/archives/ubuntu-devel/2020-July/041079.html
Commit:
https://kernel.ubuntu.com/git/ubuntu/unstable.git/commit/?id=25e6c851704a47c81e78e1a82530ac4b328098a6
--
You received this bug notification because you are a member of
Here's an annotated strace output of the dbus process when it fails. In
another terminal, I ran 'systemctl status ntp' which triggers the dbus
query. As Zahid mentioned above, this is with the permissions on
/etc/ldap.conf set to 440, so the dbus-daemon user doesn't have
permissions to read it.
@ddstreet
I'm not sure where upstream is going just yet. For Ubuntu; I think
1) Adjusting the bcache-tools patch to use the full path to bcache-
super-show should change;
2) If we fix (1) then I think we can drop the systemd patch from a bug
fixing perspective; on the openSUSE image I did
I'm marking this as wontfix for Eoan, as it's EOL in just a few weeks;
please upgrade to Focal if still affected by this bug.
** Changed in: systemd (Ubuntu Eoan)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Sorry, Eoan is EOL in just a few weeks, and I don't think this will make
it. please upgrade to Focal if still affected by this bug.
** Changed in: systemd (Ubuntu Eoan)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
> > status: Unknown → Fix Released
>
> Still affects me too. I don't see fix released for Bionic.
that refers to the status in upstream systemd, not Bionic.
As I noted in the bug description, this requires a quite large patchset
to fix in Bionic; I'm not sure when/if that might get backported.
@rbalint @raharper a commit is in the ubuntu-focal git repo for this:
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3c228b1d9c5d83d7f0f7b7d8f2053a81de57f33c
I was prepping focal for upload, but on reading the last few comments,
should I revert that commit from the
** Changed in: apt (Ubuntu Disco)
Status: Fix Committed => Won't Fix
--
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/1844634
Title:
Removals keep removing dependencies
** Changed in: systemd (Ubuntu Disco)
Status: New => Won't Fix
--
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/1814596
Title:
DynamicUser can create setuid binaries
** Changed in: apt (Ubuntu Disco)
Status: Fix Committed => Won't Fix
--
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/1840995
Title:
check_stamp() function of
** Changed in: systemd (Ubuntu Disco)
Status: New => Won't Fix
--
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/1840435
Title:
Systemd >=240 sets a clamp of 64MB for
** Changed in: shadow (Ubuntu Disco)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1840375
Title:
groupdel doesn't support
** Description changed:
+ [impact]
+
+ systemd-networkd double-free causes crash under some circumstances, such
+ as adding/removing ip rules
+
+ [test case]
+
+ see original description
+
+ [regression potential]
+
+ this strdup's strings during addition of routing policy rules, so any
+
I started the SRU verification of this and I'm confused about why apport
thinks I have two versions of subiquity installed.
bdmurray@clean-focal-amd64:~$ apport-cli subiquity
*** Collecting problem information
The collected information can be sent to the developers to improve the
application.
** Changed in: linux (Ubuntu Disco)
Status: New => Won't Fix
--
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/1814373
Title:
storage / luks / dmsetup regressed (or
** Changed in: resolvconf (Ubuntu Disco)
Status: Triaged => Won't Fix
--
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/1811471
Title:
local resolver stub fails to
The version of less from focal-proposed resolved the issue and I'm now
able to view the diff.
Configuration file '/etc/default/smartmontools'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ?
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1883027
Title:
dump_acpi_tables.py: fix incorrect
** Changed in: cloud-init (Ubuntu Disco)
Status: New => Won't Fix
--
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/1671951
Title:
networkd should allow configuring
** Changed in: apt (Ubuntu Disco)
Status: Confirmed => Won't Fix
--
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/1796193
Title:
DistUpgradeViewNonInteractive crashes /
** Changed in: systemd (Ubuntu Disco)
Status: New => Won't Fix
--
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/1830746
Title:
memlock setting in systemd (pid 1) too
** Changed in: icu (Ubuntu Disco)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to icu in Ubuntu.
https://bugs.launchpad.net/bugs/1827391
Title:
Japanese era Reiwa SRU
Status in icu
** Changed in: initramfs-tools (Ubuntu Disco)
Status: Confirmed => Won't Fix
--
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/1832042
Title:
static ip=
** Changed in: systemd (Ubuntu Disco)
Status: New => Won't Fix
--
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/1846405
Title:
MSI GS65 8RF key between space and
** Changed in: nss (Ubuntu Disco)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to nss in Ubuntu.
https://bugs.launchpad.net/bugs/1837734
Title:
libnss3 reads fips_enabled flag and
** Changed in: linux-kvm (Ubuntu Disco)
Status: New => Won't Fix
--
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/1847816
Title:
storage autopkgtest always fails
Proposed package is tested (version below) and this fixes
dump_acpi_tables.py.
~$ lsb_release -c ; apt-cache policy apport
Codename: focal
apport:
Installed: 2.20.11-0ubuntu27.4
Candidate: 2.20.11-0ubuntu27.4
** Tags removed: verification-needed verification-needed-focal
** Tags
** Package changed: wpa (Ubuntu) => wpasupplicant (Ubuntu)
--
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/1886087
Title:
dbus Method “SignalPoll” is returning incorrect type
** Changed in: systemd (Ubuntu Disco)
Status: Confirmed => Won't Fix
--
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/1788048
Title:
systemd journald failed
** Changed in: isc-dhcp (Ubuntu Cosmic)
Status: Triaged => Won't Fix
** Changed in: isc-dhcp (Ubuntu Disco)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
** Changed in: curl (Ubuntu Disco)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in Ubuntu.
https://bugs.launchpad.net/bugs/1832882
Title:
libcurl-gnutls segfaults spotify
** Changed in: linux (Ubuntu Disco)
Status: Confirmed => Won't Fix
** Changed in: linux (Ubuntu Cosmic)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
Ubuntu 19.04 reached end of life on January 23, 2020. I am therefore
marking this bug 'wontfix' for that release.
** Changed in: linux-meta (Ubuntu Disco)
Status: Triaged => Won't Fix
** Changed in: linux-meta-hwe (Ubuntu Disco)
Status: Triaged => Won't Fix
--
You received this
the commit seb128 mentions for freetype is present in freetype 2.10.1-1
which is present in focal+.
** Changed in: freetype (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Is this issue still present after some years? I don't have any low-DPI
system at hand (I really only have hi-DPI screens… :P)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
marking Eoan as wontfix; it's EOL in weeks and this is a minor bug
** Changed in: linux-kvm (Ubuntu Eoan)
Status: New => Won't Fix
** Changed in: systemd (Ubuntu Eoan)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch
marking Eoan as wontfix; it's EOL in weeks
** Changed in: systemd (Ubuntu Eoan)
Status: In Progress => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
> systemd behaviour could be better for domains without '.'
One thing that would help with these confusing NXDOMAIN errors in
general (not just from NetworkManager) is for systemd to provide a more
verbose and possibly less "private"[*] mode that shows the requested
domains somewhere without
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1885496
Title:
Bluetooth is disabled in gui, but audio
Public bug reported:
The SignalPoll method should return a 'a{sv}' type as shown by
introspection:
$ gdbus introspect -y -d fi.w1.wpa_supplicant1 -o
/fi/w1/wpa_supplicant1/Interfaces/0 | grep SignalPoll
SignalPoll(out a{sv} args);
instead a 'v' type is returned:
$ gdbus call -y
** Description changed:
[impact]
systemd autopkgtest 'boot-and-services' fails when running with linux-
kvm kernel, because that kernel does not set CONFIG_DM_MULTIPATH, so the
test detects failed services.
[test case]
check the autopkgtest results, e.g.:
In my testing, using rootbinddn and separating LDAP info and LDAP creds
to separate files with ldap.conf as 444 and ldap.secret as 400 didn't
work for dbus.
I did change the group to messagebus and that worked.
--
You received this bug notification because you are a member of Ubuntu
Touch
We have ldap.conf set to mode 440 as there is a sensitive password used
in our config to bind to LDAP. This works for everything else that
needs it even at the user level via normal system calls.
However from what I can tell, dbus seems to need to be able to read the
file from an strace my
@xnox @juliank IMO there is no real need for different boot time and
post-boot governor.
I think where we would like to save power or be less noisy the
(possibly) faster boot does not have huge impact on user satisfaction.
I agree that fans should not be on all the time in laptops/desktops.
If
Looks fixed to me in focal. Thx!!!
--
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/1837245
Title:
Failed to bump fs.file-max, ignoring: Invalid argument
Status in systemd
Will there be a fix for this on focal too?
--
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/1876884
Title:
netplan using incorrect renderer
Status in dropbear
All autopkgtests for the newly accepted less (551-1ubuntu0.1) for focal have
finished running.
The following regressions have been reported in tests triggered by the package:
mercurial/5.3.1-1ubuntu1 (s390x)
Please visit the excuses page listed below and investigate the failures,
proceeding
This is related with systemd and dbus. Possibly nsswitch, ldap and
nscd.
However dbus sees the user as not being authenticated. As such, I'm
switching this over to dbus.
We see this issue every now and then depending on what we install so I
feel there's a race condition taking place which
This was (possibly) fixed upstream in a similar way to comment 7:
https://github.com/systemd/systemd/pull/15836
essentially instead of calling mkswap inside flock, it calls systemd-
makefs swap, which itself flocks the block device.
--
You received this bug notification because you are a member
1 - 100 of 168 matches
Mail list logo
