this is the debdiff which applied the patch , and I also host the
modified code there :
https://code.launchpad.net/~alextu/ubuntu/+source/bluez/+git/bluez/+ref/lp1887910
-bluetoothd-segv-keyboard
** Patch added: "bluez_5.48-0ubuntu3.5.debdiff"
after this patch, the issue can not be reproduced:
commit 24249e091ab3a935f6ea87b7f7355c689c045a80 (HEAD -> refs/heads/master)
Author: Luiz Augusto von Dentz
Date: Mon Apr 9 14:48:41 2018 +0300
shared/queue: Handle NULL as direct match on queue_remove_if
As with queue_find when
bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp
7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000]
** Affects: oem-priority
Importance: Critical
Assignee: Alex Tu (alextu)
Status: In Progress
** Affects: bluez (Ubuntu)
Importance: Undecided
S
This is what the attached script gives me now (Fedora 32, Glibc 2.31):
getaddrinfo host="None" hints.ai_flags=AI_ADDRCONFIG:
::1
127.0.0.1
getaddrinfo host="localhost" hints.ai_flags=AI_ADDRCONFIG:
::1
127.0.0.1
getaddrinfo host="127.0.0.1" hints.ai_flags=AI_ADDRCONFIG:
127.0.0.1
Public bug reported:
Freezes randomly without any traceable pattern. Windows become unresponsive
while the cursor works.
To unfreeze I have to press the OFF button of my HP ProBook and then click on
"Cancel" in the shutdown dialogue. That unfreezes the windows. May happen
several times per
finally it's fixed after last update to 4.15.0-109
--
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/1877542
Title:
Ubuntu 18.04.4 Inspiron 5379 No sound ALC3253
Thanks - in Ubuntu releases 18.04 onwards debug symbols are provided via
the separate -dbgsyms packages which require extra configuration -
https://wiki.ubuntu.com/DebuggingProgramCrash
TL;DR:
echo "deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe
multiverse" | sudo tee
Ok, since I can't reproduce this locally, if you are interested / able
to help with debugging it, could you please attach the core dump. Or if
this contains potentially sensitive details, you could install the dbg
versions of the packages and reproduce the crash and this would provide
a more
I am confused - in the initial bug report you mention
/etc/systemd/system/dbus-org.freedesktop.resolve1.service as the systemd
unit but now you also mention /etc/systemd/system/dbus-
org.freedesktop.ModemManager1.service - can you confirm which one you
have had to disable the SystemCallFilter?
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.
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
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 mem
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
I am not sure how packages.ubuntu.com generates its list but they were
published for all architectures on launchpad:
https://launchpad.net/ubuntu/+source/libseccomp/2.4.3-1ubuntu3.20.04.2
Also the debs are present on ports.ubuntu.com: http://ports.ubuntu.com
Ping @jdstrand / @sil2100 - I am not sure what more I need to do to try
and progress this SRU - I believe the systemd/eoan update still needs to
be sponsored from the security-proposed PPA - but I don't have
permission to upload this myself - could one of you please do that on my
behalf? Also if
This is still an issue in Focal (20.04).
I think it is because the "postrotate" line of the default
/etc/logrotate.d/ufw file reads:
```
invoke-rc.d rsyslog rotate >/dev/null 2>&1 || true
```
Which will not function on a systemd system.
Using the example from /etc/logrotate.d/rsyslog would
@ddstreet - is there anything I can / still need to do to get this into
-updates?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1877633
Title:
libseccomp 2.4.3 (and
@brian-murray,
Bug description is updated. Please keep me posted if it needs more
information. Thanks
** Description changed:
+ [Impact]
+
+ dump_acpi_tables.py does not always generate 4-char table names (which
+ is defined by ACPI spec) and can miss or duplicate data of ACPI tables
+ in
** Tags added: oem-priority originate-from-1880192
--
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/1882161
Title:
module-switch-on-port-avaiable: switch the port on ucm
Ah thanks Dan! - I realise now that perhaps I should have had just the 1
bug report for both issues to make things simpler as having two seems to
have complicated things too much.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
The systemd update for eoan is not in -proposed but the libseccomp
updates (for all releases) are - the systemd update for eoan needs to be
released in conjunction with the libseccomp update as it fixes a
regression in systemd/eoan/i386 when used in conjunction with the
libseccomp updates.
The
Yes, like previous libseccomp updates, we plan to publish this to both
-security and -updates.
--
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/1876055
Title:
SRU: Backport
systemd-242-7ubuntu3.11 passes autopkgtest for eoan/i386 and resolves
the FTBFS for arm64 -
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-eoan-ubuntu-security-proposed-
ppa/eoan/i386/s/systemd/20200615_102850_82300@/log.gz
@jdstrand can you
Public bug reported:
some error occurs when upgrade through "sudo apt upgrade"
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: dbus 1.10.6-1ubuntu3.6
ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223
Uname: Linux 4.4.0-184-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.23
** Also affects: apport (Ubuntu)
Importance: Undecided
Status: New
--
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
@jdstrand - thanks but unfortunately that version FTBFS on arm64 - I've
uploaded an updated verion (ubuntu3.11 -
https://launchpadlibrarian.net/484321608/systemd_242-7ubuntu3.11_source.changes)
to the security-proposed PPA with an additional upstream fix for the
arm64 FTBFS - this is currently
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: systemd (Ubuntu Xenial)
** No longer affects: systemd (Ubuntu Bionic)
** No longer affects: systemd (Ubuntu Focal)
** No longer affects: systemd (Ubuntu Groovy)
--
You received this bug
** Patch added: "systemd_242-7ubuntu3.10.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876055/+attachment/5383164/+files/systemd_242-7ubuntu3.10.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
** Attachment added:
"systemd-242-7ubuntu3.10-i386-autopkgtest-libseccomp-proposed-upgrade.log.gz"
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876055/+attachment/5383166/+files/systemd-242-7ubuntu3.10-i386-autopkgtest-libseccomp-proposed-upgrade.log.gz
--
You received this
I have confirmed the attached debdiff for systemd resolves this failure
on i386 with libseccomp 2.4.3 - see attached for the autopkgtest log of
a local run.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in
@jdstrand - could you please review and sponsor the systemd debdiff to
eoan-proposed?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1876055
Title:
SRU: Backport
I can reproduce the systemd eoan/i386 autopkgtest failure locally - this
is similar to LP #1853852 - testing a rebuild of systemd 242-7ubuntu3.9
with the patch from that bug backported.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Verified on focal using the following procedure - full log attached as
well:
# install seccomp
$ apt install seccomp
# try resolving getrlimit for aarch64
$ scmp_sys_resolver -a aarch64 getrlimit
-10180
# on the current focal version this fails to resolve correctly and
returns -10180
# enable
Successful test log for seccomp 2.4.3-1ubuntu3.18.04.2 from bionic-
proposed
** Attachment added: "libseccomp-bionic-proposed-test.log"
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876055/+attachment/5382295/+files/libseccomp-bionic-proposed-test.log
** Tags removed:
Successful test log for seccomp 2.4.3-1ubuntu3.20.04.2 from focal-
proposed
** Attachment added: "libseccomp-focal-proposed-test.log"
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876055/+attachment/5382297/+files/libseccomp-focal-proposed-test.log
** Tags removed:
Successful test log for seccomp 2.4.3-1ubuntu3.19.10.2 from eoan-
proposed
** Attachment added: "libseccomp-eoan-proposed-test.log"
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876055/+attachment/5382296/+files/libseccomp-eoan-proposed-test.log
** Tags removed:
Successful test log for seccomp 2.4.3-1ubuntu3.16.04.2 from xenial-
proposed
** Attachment added: "libseccomp-xenial-proposed-test.log"
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876055/+attachment/5382294/+files/libseccomp-xenial-proposed-test.log
** Tags removed:
Verified on xenial/bionic/eoan/focal as follows:
# install seccomp
$ apt install seccomp
# try resolving getrlimit for aarch64
$ scmp_sys_resolver -a aarch64 getrlimit
# on the current focal version this fails to resolve correctly and returns
-10180
# on other releases this succeeds as
** Summary changed:
- SRU: Backport 2.4.3-1ubuntu2 from groovy to focal/eoan/bionic/xenial for
newer syscalls for core20 base
+ SRU: Backport 2.4.3-1ubuntu3 from groovy to focal/eoan/bionic/xenial for
newer syscalls for core20 base and test suite robustness
--
You received this bug
** Changed in: pulseaudio (Ubuntu)
Assignee: Kai-Chuan Hsieh (kchsieh) => (unassigned)
** Changed in: oem-priority
Assignee: (unassigned) => Kai-Chuan Hsieh (kchsieh)
** Description changed:
[Impact]
- * Some Intel platform bionic user audio function will be broken after
+ *
** Also affects: oem-priority
Importance: Undecided
Status: New
--
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/1881094
Title:
Support kernel 5.4 Intel sound
** Also affects: libseccomp (Ubuntu Groovy)
Importance: Medium
Status: New
** Also affects: libseccomp (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: libseccomp (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: libseccomp (Ubuntu
** Description changed:
[Impact]
- snap-confine from snapd uses libseccomp to filter various system calls
- for confinement. The current version in eoan/bionic/xenial (2.4.1) is
- missing knowledge of various system calls for various architectures. As
- such this causes strange issues like
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
One more thing - I expect your phone has USB Tethering enabled - and so
presents itself as an rndis USB/ethernet device - and then network
manager uses this as a preferred interface to route traffic through
rather than the wireless interface.
--
You received this bug notification because you are
This doesn't seem like a security issue to me - I believe this is the
default behaviour when using network manager for tethering - it will
route traffic via the tethered device. I am reassigning this against
network-manager which is likely doing the route setup.
** Information type changed from
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
** Patch added: "libseccomp_2.4.3-1ubuntu3.20.04.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876055/+attachment/5374699/+files/libseccomp_2.4.3-1ubuntu3.20.04.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Patch added: "groovy"
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876055/+attachment/5374698/+files/libseccomp_2.4.3-1ubuntu3.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
** Patch removed: "focal"
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876055/+attachment/5374693/+files/libseccomp_2.4.3-1ubuntu3.20.04.1.debdiff
** Patch removed: "eoan"
** Patch added: "focal"
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876055/+attachment/5374693/+files/libseccomp_2.4.3-1ubuntu3.20.04.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in
** Description changed:
- Placeholder to start preparing SRU for
- https://github.com/snapcore/core20/issues/48
+ [Impact]
+
+ snap-confine from snapd uses libseccomp to filter various system calls
+ for confinement. The current version in eoan/bionic/xenial (2.4.1) is
+ missing knowledge of
** Patch added: "xenial"
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876055/+attachment/5374696/+files/libseccomp_2.4.3-1ubuntu3.16.04.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in
** Patch added: "bionic"
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876055/+attachment/5374695/+files/libseccomp_2.4.3-1ubuntu3.18.04.1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in
** Patch added: "eoan"
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876055/+attachment/5374694/+files/libseccomp_2.4.3-1ubuntu3.19.10.1.debdiff
** Patch removed: "Update for groovy solely to add the test suite change to be
in-line with older releases"
** Summary changed:
- SRU: Backport 2.4.3-1ubuntu1 from focal to eoan/bionic/xenial for newer
syscalls for core20 base
+ SRU: Backport 2.4.3-1ubuntu2 from groovy to focal/eoan/bionic/xenial for
newer syscalls for core20 base
--
You received this bug notification because you are a member of
** Tags added: oem-priority originate-from-1878141 somerville
** Changed in: oem-priority
Assignee: (unassigned) => Kai-Chuan Hsieh (kchsieh)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Public bug reported:
When in both Firefox and Opera hardware acceleration is on and browser
is running it will trigger freeze with X.OrgX driver on.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux
** 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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1878177
Title:
CVE-2020-3810 out-of-bound stack reads in
For the issue of not being able to save files to / from external drives,
you need to manually connect the removable-media interface for the
audacity snap - so either in Ubuntu Software search again for audacity
and then via the 'Permissions' button ensure the 'Read/write files on
removable storage
@jdstrand would you be willing to sponsor that for me to groovy and then
I'll update this bug for SRU of this back to focal (and will add this
change also for the existing libseccomp SRU for eoan/bionic/xenial in LP
#1876055)
--
You received this bug notification because you are a member of
Tested on an up-to-date groovy install:
amurray@sec-groovy-amd64:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Groovy Gorilla (development branch)
Release:20.10
Codename: groovy
amurray@sec-groovy-amd64:~$ dpkg -l seccomp
** Patch added: "libseccomp_2.4.3-1ubuntu2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633/+attachment/5370131/+files/libseccomp_2.4.3-1ubuntu2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
See attached for a debdiff to fix this in groovy - this backports the PR
mentioned above to add these missing syscalls for aarch64.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libseccomp in Ubuntu.
Hello Sebastien,
I was too happy at the first place. Yes there is the sound on speakers (I
didn't managed yet to check HDMI), but there is neither nor sound nor the
possibility to connect with BT headphones (all of my 3 sets are failed to
connect).
And regarding the booting previous kernel: sound
Salut Sebastien,
Thanks for your letter. Log file is in attachment.
And yay it works again, but not from the first time on 4.15.0-96. I had to
reboot it second time at safemode(without any applied changes in the menu )
and it sounded well.
Thanks again for you help, I'm not the first-timer on
When generating the list of systems calls for aarch64, libseccomp uses
the generic kernel API headers rather than the architecture specific
ones - and so misses the definitions of getrlimit, setrlimit and clone3
for aarch64 - if this is changed to use arch-specific headers then we
can regenerate
** Summary changed:
- Ubuntu 18.04 No sound ALC3253 alsa-driver
+ Ubuntu 18.04.4 Inspiron 5379 No sound ALC3253 alsa-driver
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
Public bug reported:
Hello,
After last general update sound stops working on all interfaces. speakers,
headphones nor HDMI provide any sound output even bluetooth headphones can't be
connected.
It seems that interface is connected to HDMI
aplay -l
List of PLAYBACK Hardware Devices
Sorry, I didn't mean to come off so rude. Anyway, I looked into things
and it's not fixable because `apport-bug -w` actually uses xprops which
will return on any mouse press.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Apparently in the intervening 9 years nobody bothered to check. It took
me 90 seconds to verify this behaviour is still present in apport
2.20.9-0ubuntu7.14
Linux kol 5.3.0-51-generic #44~18.04.2-Ubuntu SMP Thu Apr 23 14:27:18
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
Close as wontfix if you
Public bug reported:
Placeholder to start preparing SRU for
https://github.com/snapcore/core20/issues/48
** Affects: libseccomp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
@Paolo, the test kernel does fix the problem for me.
--
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/1871182
Title:
[RTL810xE] No ethernet connection
Status in
After doing some research I'm quite sure that this bug was introduced by [1] in
the 5.4.29 mainline kernel and the 5.4.0-22.26 ubuntu kernel.
The bug was already fixed by [2] in the 5.4.32 mainline kernel. At least that's
the case on my machine [3] and Heiner Kallweit also pointed in this
** Attachment added: "2020-04-15_01-41.png"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872788/+attachment/5354040/+files/2020-04-15_01-41.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Public bug reported:
compare to bionic, bionic will show complete icon when I press super key
and type prefix of application.
But in Focal, the icon is incomplete as attache screenshot.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu
No, there's no desktop MaaS Focal image yet.
For auto sanity of device team and SRU verification of certification
team, we convert OEM iso to MaaS compatible image by script.
It works well on bionic but failed on Focal by LP: #1868915 and LP:
#1869181.
For this issue, it looks upstream accepted
Thanks for taking the time to report this bug and helping to make Ubuntu
better. Since the package referred to in this bug is in universe or
multiverse, it is community maintained. If you are able, I suggest
coordinating with upstream and posting a debdiff for this issue. When a
debdiff is
Has this been reported to the upstream libgsm developers?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libgsm in Ubuntu.
https://bugs.launchpad.net/bugs/1860414
Title:
ZDI-CAN-9867: Canonical libgsm AssertFailure
** 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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1862933
Title:
Apport crash report & cron script
** 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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1862348
Title:
Apport lock file root privilege
-generic #154-Ubuntu SMP Tue Dec 20 09:57:27 UTC 2016 x86_64
x86_64 x86_64 GNU/Linux
Any clue about what's going on?
Thanks,
Alex
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1659590/+subscriptions
--
Mailing list: https://launchpad.net
sure, it's there
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/398
** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/issues
#398
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/398
** Description changed:
+ Also created bug on
** Attachment added: "dmesg.log"
https://bugs.launchpad.net/oem-priority/+bug/1868915/+attachment/5341768/+files/dmesg.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
It seems this issue only happens to machine which eth port be renamed as eno1.
It can not be reproduced on another machine which eth port be renamed to enp2s0.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager
** Also affects: maas
Importance: Undecided
Status: New
** Changed in: oem-priority
Assignee: (unassigned) => Alex Tu (alextu)
** Changed in: oem-priority
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch
Public bug reported:
This issue will cause "NetworkManager-wait-online.service: Failed with result
'exit-code'."
And cloud-init.service is counting on this service for network status.
So this issue will finally cause MaaS deploying failed.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package:
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
gnome-shell is responsible for the lock screen so reassigning to that
** Package changed: shadow (Ubuntu) => gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
** 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 lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1706770
Title:
Lock screen can be bypassed when
of CAPTURE Hardware Devices
card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: alex 4221 F mixer_applet2
Card0.Amixer.info:
Card
** Tags added: oem-priority originate-from-1863233
--
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/1859754
Title:
add ucm to make alsa/sof driver work under PA (variants
I had the same issue and I had to reinstall 19.04, but anyway I want to
use the latest Ubuntu, so I afraid to install it again.
Question: How can I check compatibility before updating?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Relevant parts from journalctl:
Feb 11 13:03:53 slate systemd[6652]: Starting Notification regarding a crash
report...
Feb 11 13:03:53 slate update-notifier-crash[260823]: /usr/bin/whoopsie
Feb 11 13:03:54 slate update-notifier-crash[260837]: /var/crash/libdleyna-core-1
Feb 11 13:04:19 slate
Public bug reported:
If a crash report is triggered automatically (say from a program crash
etc) then the Apport UI pops up asking whether to report this - if I
choose to proceed, after about 30 seconds gedit pops up with a HTML
document showing 'OpenID transaction in progress' - which is the
Can you try adding the following to
/etc/apparmor.d/local/usr.sbin.dhcpd:
network packet dgram,
And then running
sudo apparmor_parser -rT /etc/apparmor.d/usr.sbin.dhcpd
And see if restart dhcpd then works?
--
You received this bug notification because you are a member of Ubuntu
Touch
-050300-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: alex 3395 F pulseaudio
/dev/snd/pcmC0D0c: alex 3395 F...m pulseaudio
/dev/snd/pcmC0D0p
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libgsm in Ubuntu.
https://bugs.launchpad.net/bugs/1860414
Title:
ZDI-CAN-9867: Canonical libgsm AssertFailure
: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13
Uname: Linux 5.3.0-26-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: alex 2760 F
301 - 400 of 982 matches
Mail list logo
