@Brian M:
As you suggest that my or my problem reported likely by Dan van Vugt
with my install of Ubuntu-MATE 20.10 had this similar problem of long
strings of "Failed to start " items in the TTY and very long boot times
. . . wasn't exactly "fixed" by trashing the /var/crash directory as he
This bug was fixed in the package apport - 2.20.11-0ubuntu48
---
apport (2.20.11-0ubuntu48) groovy; urgency=medium
* data/whoopsie-upload-all: When processing reports if a .crash file already
has a corresponding .uploaded file which is newer than the .crash file
remove the
** Changed in: ntp (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1891953
Title:
CVE-2019-8936
Status in ntp package in
This is likely a duplicate of bug 1891657.
--
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/1893952
Title:
Repeated apport failures causing long boot delays
Status in
*** This bug is a duplicate of bug 1891657 ***
https://bugs.launchpad.net/bugs/1891657
** This bug has been marked a duplicate of bug 1891657
systemd 100% cpu usage apport-autoreport.service: Failed with result
'start-limit-hit'
--
You received this bug notification because you are a
** Branch linked: lp:~ubuntu-core-dev/ubuntu/groovy/apport/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/1891657
Title:
systemd 100% cpu usage
I sponsored the procps changes to Groovy.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1886112
Title:
Enabling DMESG_RESTRICT in Groovy Onward
Status in linux
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information.
At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the
problem.
2.
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Medium
--
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/1893563
Title:
netplan: can't login to
** Package changed: netplan.io (Ubuntu) => network-manager (Ubuntu)
** Also affects: network-manager via
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/83
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of
You have been subscribed to a public bug:
I've setup my wifi cards as ap over a bridge using netplan.
If I add:
auth:
key-management: psk
password: "testinglang"
then my clients are unable to connect.
If I remove those lines above in netplan then the clients are able to connect
but without
** Changed in: ntp (Ubuntu)
Importance: Undecided => Medium
** Bug watch added: Debian Bug tracker #924228
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924228
** Also affects: ntp (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924228
Importance: Unknown
Public bug reported:
Ubuntu 18.04.5
iproute2 4.15.0-2ubuntu1.2
iproute2-doc 4.15.0-2ubuntu1.2
Most of the subcommands for /sbin/ip are documented in a manpage with a name of
the form "ip-$SUBCOMMAND(8)", for example "ip address" is documented at
"ip-address(8)".
However, ip tuntap seems to
On Fri, Sep 25, 2020 at 07:13:52PM -, Nicolas Bock wrote:
> On Fri, Sep 25 2020, Brian Murray wrote:
>
> > The issue with PathChanged is that /var/crash is used for writing three
> > types of files. The .crash file, the .upload file (which signifies the
> > crash is ready to be uploaded), and
** Changed in: iptables (Ubuntu)
Status: New => Fix Committed
** Changed in: iptables (Ubuntu)
Assignee: (unassigned) => Alex Murray (alexmurray)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in
@philippe734: No surprise as metacity is no compositing window manager. The
issue is caused by enabling xpresent for xfwm4 and marco while amdgpu being
buggy.
It's fixed upstream, with the current amdgpu from git this issue does not
appear, so it must be backported into
On Fri, Sep 25 2020, Brian Murray wrote:
> The issue with PathChanged is that /var/crash is used for writing three
> types of files. The .crash file, the .upload file (which signifies the
> crash is ready to be uploaded), and the .uploaded file (which contains
> the UUID of the crash in the error
Yes, this bug is still present on my Lenovo W530 under Xubuntu 18.04.5!
>From time to time, I can't record with audacity using the headphone
attached to the jack. Absolutely no sound appears to be recorded. If I
unplug the headset and try to use the builtin microphone, also no
recording. The
There is no this issue when using metacity.
sudo apt install metacity
metacity --replace
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxcb in Ubuntu.
https://bugs.launchpad.net/bugs/1873895
Title:
Regression:
*** This bug is a duplicate of bug 1891657 ***
https://bugs.launchpad.net/bugs/1891657
** This bug has been marked a duplicate of bug 1891657
systemd 100% cpu usage apport-autoreport.service: Failed with result
'start-limit-hit'
--
You received this bug notification because you are a
I updated my Xubuntu system 2 days ago but only rebooted last night, and now my
system won't boot.
So I tried to reinstall, had it download updates during installation, and the
installer crashed and sent me here.
was installing Xubuntu 20.04.1 LTS from USB on:
2013 Alienware Aurora
some i7
** Changed in: gdm3 (Ubuntu Groovy)
Importance: Low => Medium
--
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/1865226
Title:
gdm-smartcard pam config needs to be updated
** Changed in: ubiquity (Ubuntu)
Assignee: pooria aghapour (pan2020) => (unassigned)
--
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/1871268
Title:
Installation fails
On Fri, Sep 25, 2020 at 03:42:00PM -, Nicolas Bock wrote:
> @balint I was wondering why we don't use `PathChanged` in the systemd
> path file. This checks for any changes in the path and will pick up new
> crash files... But after reading the systemd docs again I guess the
> reason is that we
It has been brought to my attention by a UA customer that they are
suffering from which seems a similar situation:
"
Our only currently working SmartCard access from Linux, over SSSD, to AD, is on
RHEL7.
I was able to get SSH access on Ubuntu 20.04LTS, after adding
"ad_gpo_access_control =
1) There are no changes with the cryptsetup in bionic-updates.
This is expected, because the changes in initramfs-tools
are gated by a file introduced in the patched cryptsetup.
Thus no regression from the initramfs-tools side.
...
And, additional testing with the _patched_ cryptsetup,
just in
** Attachment added: "lp1879980 verification-bionic.log"
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1879980/+attachment/5414278/+files/lp1879980%20verification-bionic.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
In the benefit of the initramfs-tools upload to move on:
I have verified that it has no regressions with current
cryptsetup in bionic-updates and works as expected with
the patched version (in upload queue, not -proposed yet.)
Verification details in the next comment and detailed
topology and
** Changed in: ubiquity (Ubuntu)
Assignee: (unassigned) => pooria aghapour (pan2020)
--
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/1871268
Title:
Installation fails
All autopkgtests for the newly accepted apport (2.20.9-0ubuntu7.18) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
apport/2.20.9-0ubuntu7.18 (amd64)
Please visit the excuses page listed below and investigate the failures,
Yeah, sorry, I don't think that's a reproducer for the bug. You killed
dbus, gdm and everything else, and they obligingly died on you. :)
My feeling is that this bug is about a deadlock that somehow happens
when dbus and/or systemd are reloaded, possibly at the same time. It
looks like dbus stops
Well, more correctly -1 means to all processes you can send to, and if
you're root, well it's everyone.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1871538
kill(-1, SIGINT) kills all processes on the system with SIGINT, so this
is hardly surprising.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1871538
Title:
dbus
Hey people, adding "me too" comments does not add anything useful to the
bug. Please click the "affects me" kind of button at the top instead if
you want to express your being affected.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
builds ok, test results look ok.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python2.7 in Ubuntu.
Public bug reported:
xdiagnose
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-119.120-generic 4.15.18
Uname: Linux 4.15.0-119-generic i686
.tmp.unity_support_test.0:
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: i386
** Package changed: ubuntu => xorg (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/1897295
Title:
freeze display and no more toothead wheel high of the screen for
You have been subscribed to a public bug:
-often I need several reboot for a clean ubuntu installation, the courant
problem is
sceen freeze in the middle of ubuntu installation
-often ubuntu freeze during the session, and I must restart the computer
-parameters wheel is lost
-I don't
Public bug reported:
After last update, I have lost the sound of my Asus Monitor which has
got speakers.
It is a problem with ALSA Audio because, the last update installed some
patch of ALSA.
Now, when I use for example VLC and try to change to my HDMI Audio
Controller, it works well, but If I
When I disconnect the headphones and next launch DOTA 2 with HDMI Audio
Device, It works, but I need to disconnect my headphones all the time.
Is annoying to do that all the time.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Hello Brian, or anyone else affected,
Accepted apport into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.1-0ubuntu2.25 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Brian, or anyone else affected,
Accepted apport into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.9-0ubuntu7.18 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
@balint I was wondering why we don't use `PathChanged` in the systemd
path file. This checks for any changes in the path and will pick up new
crash files... But after reading the systemd docs again I guess the
reason is that we want the service to activate if the crash directory
already contains a
** Description changed:
SRU Description
[Impact]
- data/apport which processes core files expects a certain quantity of
arguments in a specific order. This ended up causing an issue with some
security updates where we were trying to support a new version of apport on a
host system and
By chance (while developing some netplan code), I seem to have found a
reproducer for this bug... I don't know what is going on, but calling
the 'Trigger' method from the attached 'dbus.c' file will kill the GDM
session in a reproducible way.
The invalid `kill(-1, SIGINT);` of line 21, seems to
aligned state to LP 1893170
** Changed in: zlib (Ubuntu Focal)
Status: New => Confirmed
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
** Changed in: zlib (Ubuntu Focal)
Status: Confirmed => Fix Committed
--
You received this bug notification because
aligned state to LP 1893170
** Changed in: zlib (Ubuntu Focal)
Status: New => Fix Committed
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1893170
Title:
[Ubuntu 20.10] zlib: DFLTCC
Just installed a new system and the bug is still there, leading me straight
back to this bug report for the 'fix'.
I was really hoping that this bug would have been addressed in 20.04.1.
Not sure why no one from the dev team is picking this up to rectify it.
--
You received this bug
Hello bugproxy, or anyone else affected,
Accepted zlib into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/zlib/1:1.2.11.dfsg-
2ubuntu1.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hi, I just got this error when installing Ubuntu 20.04.1 LTS from USB Drive.
My laptop details are below:
Model: Illegear Onyx V Ryzen
Processor: AMD Ryzen 7 4800H with Radeon Graphics 2.90 GHz
RAM: 16GB
System Type: 64-bit, x-64 based processor
--
You received this bug notification because you
Hello Pierre, or anyone else affected,
Accepted pulseaudio into focal-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu3.7 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello Kai-Heng, or anyone else affected,
Accepted pulseaudio into focal-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu3.7 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (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.
Public bug reported:
At random times I get two bluetooth indicators on the bottom of the
screen instead of one.
See the screenshot.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux
5.8.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu47
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.452
Date: Fri Sep 25 11:58:18 2020
LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Alp
6_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu47
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.452
Date: Fri Sep 25 11:58:18 2020
LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200925)
ProcEnviron:
TERM
ion: 2.20.11-0ubuntu47
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.452
Date: Fri Sep 25 11:58:18 2020
LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200925)
ProcEnviron:
TERM=linux
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
1.452
Date: Fri Sep 25 11:58:18 2020
LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200925)
ProcEnviron:
TERM=linux
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-meta
UpgradeStatus: No upgrade log present (
2020
LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200925)
ProcEnviron:
- TERM=linux
- PATH=(custom, no user)
- XDG_RUNTIME_DIR=
- LANG=C.UTF-8
- SHELL=/bin/bash
+ TERM=linux
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=C.UTF-8
+ SHELL=/bin/bash
SourceP
: 2.20.11-0ubuntu47
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.452
Date: Fri Sep 25 11:58:18 2020
LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200925)
ProcEnviron:
TERM=linux
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
Sou
Public bug reported:
My preferred sound output is HDMI which works fine.
Occasionally I use some bluetooth headphones which work fine too.
Once the headphones are switched off though, ubuntu reverts to speaker output -
instead of the expected HDMI output, hence I have to manually select HDMI
I just got this error when installing ubuntu-20.04.1-desktop-amd64.iso
from USB stick on Lenovo Think Pad X1 Extreme Gen 2 I9.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
Public bug reported:
System get crashed after few hour of working.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
** Description changed:
[Impact]
In some cases, the wow is not configured and the
NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable
management of wake-on-LAN in NetworkManager).
The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE
bit.
But,
@Kai Kasurinen
>probably fixed on shared-mime-info 2.0:
>https://gitlab.freedesktop.org/xdg/shared-mime-info/-/commit/18bb7cfc6c43d710ecf60339b5dd9bd19c297cdf
Yeah, well. It's if they only used the same database.
--
You received this bug notification because you are a member of Ubuntu
Touch
If you wrap string in the proper tags you will get the same result, but
with different offset (28 chars):
tee "index.html" <
`printf "x"%.0s {1..228}`
use strict
eol # -> text/html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
#ＩＮＴＲＯ
After digging up for a while I've found where the issue comes from for both
`.html` and `.py` (bug #1857824) files.
#ＳＨＯＲＴ
The culprit responsible for misidentification resides in `.xml` database which
specifies how to match mime-type against input data. It can be found here [2].
#ＬＯＮＧ
** Also affects: pulseaudio (Ubuntu)
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/1896774
Title:
Headphone output stopped
Public bug reported:
when opening software source
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
BootLog: Error: [Errno
Right, yes, please do go ahead. It was pointed out before that this
would be desirable after we switched away from -legacy due to the nature
of the fixes.
I had thought from the diff of debian/tests/control that the test
coverage of the nft backend was being reduced, but then I took a look at
** Changed in: ubuntu-cdimage
Assignee: Hoa (thuythumattroi1999) => (unassigned)
--
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/1871268
Title:
Installation fails with
Well, it's 2020 now. I'm stunned to see that Ubuntu chooses VPN as the
IPv6 default route, even when choosing IPv6 "Disable" in the VPN
settings :( (completely ignored by the way).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Attachment added: "Full "vagrant up" log"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1871268/+attachment/5414080/+files/vagrant.log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
Occurs to me in a daily CI/CD vagrant build since Sep 23, 2020 3:30 AM:
default: Processing triggers for libc-bin (2.31-0ubuntu9) ...
default: E
default: :
default: Could not configure 'libc6:i386'.
default: E
default: :
default: Could not perform immediate
Error on install Dell Precision 7510
--
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/1871268
Title:
Installation fails with Could not configure 'libc6:i386'. , E:Could
not
76 matches
Mail list logo
