** Changed in: taglib
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to taglib in Ubuntu.
https://bugs.launchpad.net/bugs/1800012
Title:
ogg vorbis corruption
Status in TagLib:
Fix Re
** Also affects: taglib (Ubuntu Groovy)
Importance: Undecided
Status: Confirmed
** Also affects: taglib (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: taglib (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: taglib (Ubuntu Focal)
OK, thanks. So it's kind of working as designed and kind of not...
If you would like to get this fixed then please open a new bug upstream:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues
with a title like:
switch-on-connect mistakes startup for USB hotplug
** Changed in: pul
After trying to roll forward again I saw the output from ldconfig
/lib/x86_64-linux-gnu/libseccomp.so.2.2.0 is not a symbolic link
Looks like I had duplicate versions of libseccomp2 lying around on my
LD_LIBRARY_PATH
dpkg -L libseccomp2
/usr/lib/x86_64-linux-gnu/libseccomp.so.2.4.3
So I delete
Hi Daneil!
Commenting out "load-module module-switch-on-connect" in
/etc/pulse/default.pa did indeed work.
--
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/1877194
Title:
** Tags added: regression-release
--
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/1876065
Title:
After unplug headphones and plug them again no sound can be heard
Statu
It was flaky and now resolved in proposed migration.
But I'd want to understand why we fail 4/5 times.
So the debugging tests in the bileto ticket [1] will go on for a bit.
[1]: https://bileto.ubuntu.com/#/ticket/4049
--
You received this bug notification because you are a member of Ubuntu
Touc
Public bug reported:
My /tmp folder has dozens of empty folders with names like grilo-plugin-
cache-ABCDEF. I don't know anything about grilo-plugins, but surely they
can do their job without leaving endless garbage directories behind when
they're done?
$ lsb_release -a
No LSB modules are availab
We configure PulseAudio by default to automatically choose hotplugged
devices so it might be thinking booting with USB counts as hotplugging.
To avoid this you should just be able to comment out:
load-module module-switch-on-connect
from /etc/pulse/default.pa
** Changed in: pulseaudio (Ubuntu
Public bug reported:
Problem keeps appearing when video is played. video keeps playing but no
sound is heard thru headphones.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic
*** 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 look
This is something to do with linux 5 kernel api
You need to manually downgrade systemd - well - that's what I did.
when you boot with grub or refind - edit default entry and change the
init=/bin/init to init=/bin/bash
That will bypass systemd starting up and drop you straight into a shell.
moun
Sure. This issue is also reproducible with pre-compiled version of
0.2.62ubuntu0.4.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1872560
Title:
integer overflow in whoo
** Description changed:
Similar to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570
Only difference is that it does not reset to HDMI output, but to one of
my USB-outputs. It does not respect the change I made after reboot.
+
+ In short:
+ 1. Boot system
+ 2. "Analogu
All autopkgtests for the newly accepted evolution-data-server (3.36.2-0ubuntu1)
for focal have finished running.
The following regressions have been reported in tests triggered by the package:
libreoffice/1:6.4.3-0ubuntu0.20.04.1 (ppc64el, armhf)
Please visit the excuses page listed below and i
In the generic kernel CONFIG_RT_GROUP_SCHED is still enabled. It was
only disabled for the lowlatency kernel.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rtkit in Ubuntu.
https://bugs.launchpad.net/bugs/1875665
Title:
** Description changed:
Similar to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570
Only difference is that it does not reset to HDMI output, but to one of
my USB-outputs. It does not respect the change I made after reboot.
-
- (Notice that I swapped out my username w
Sorry, I meant "Are you able to reproduce the issue with the pre-
compiled version of Whoopsie that comes with it?"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to whoopsie in Ubuntu.
https://bugs.launchpad.net/bugs/1872560
T
** Description changed:
Similar to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570
- Only difference is that it does not reset to and HDMI output, but to one
- of my USB-outputs. It does not respect the change I made after reboot.
+ Only difference is that it does not res
Attached is the output from journalctl -b 0, where the error occurs.
Apologies - no vagrant skills here, but I can confirm Kai's replication
method - kvm qemu clean 20.04 server install, then add pulseaudio,
docker.io, reboot and the issue occurs.
** Attachment added: "20.04 boot log showing rt
Public bug reported:
Similar to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570
Only difference is that it does not reset to HDMI output, but to one of
my USB-outputs. It does not respect the change I made after reboot.
(Notice that I swapped out my username with $USER in the
I"ve had this problem on a clean install of 20.04 on a new laptop, with
two headsets that support both profiles.
```
Name: Soundcore Life 2
Alias: Soundcore Life 2
Class: 0x00240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Headset
seems like from the other bug that it got turn off again in -26.30 which
is the revision in use by the report here according to the apport
report?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rtkit in Ubuntu.
https://bugs.l
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: vim (Ubuntu)
Status: New => Confirmed
--
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/
*** This bug is a duplicate of bug 1875665 ***
https://bugs.launchpad.net/bugs/1875665
** This bug has been marked a duplicate of bug 1875665
rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after
upgrade to 20.04
--
You received this bug notification because you are
FYI, there is a pending update that will go out either tomorrow or early
next week. Please base your next upload on this update.
--
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/
I retested the armhf autopkgtest failures and update-manager and update-
notifier have now both passed.
--
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/1872902
Title:
Upgra
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:
apport-collect 1877182
When reporting bugs in the future please use apport by using 'ubuntu-
bug' and t
*** This bug is a duplicate of bug 1872778 ***
https://bugs.launchpad.net/bugs/1872778
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-online-accounts (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a
Public bug reported:
libmysqlclient.so.21 causes a segfault on shutdown.
Test case attached ==> "Removed database" will not be reported.
Backtrace:
#0 0x714c330f in ?? () from /lib/x86_64-linux-gnu/libmysqlclient.so.21
#1 0x714c8823 in ?? () from /lib/x86_64-linux-gnu/libmysqlc
Public bug reported:
It just does not work if I set it to never or to 15 MIN it does not work
it is stuck at one min
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 5.4.0-29-generic x86_64
NonfreeKern
Public bug reported:
Happening while trying to upgrade from 18.04 to 20.04.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6
ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18
Uname: Linux 5.3.0-51-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
** Tags removed: need-duplicate-check
--
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/1877181
Title:
package initramfs-tools 0.136ubuntu6 failed to install/upgrade:
Testing on an Ubuntu 18.04 LTS system with ubuntu-desktop and chrony
installed.
bdmurray@clean-bionic-amd64:/tmp/u-r-u-proposed$ apt-cache policy chrony
chrony:
Installed: 3.5-6ubuntu6
Candidate: 3.5-6ubuntu6
Version table:
*** 3.5-6ubuntu6 500
500 http://192.168.10.7/ubuntu focal/m
on xenial, additional fix is needed for bug 1877176 for complete fix for
this bug, but this patch introduces no regressions and allows networkd
to continue requesting the lease for invalid hostnames.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done v
Public bug reported:
[impact]
a systemd with a 64-character hostname (the maximum hostname length for
Linux) will cause a dhcp server to reject its dhcp lease due to passing
the invalid hostname in the dhcp lease request.
[test case]
$ cat /etc/systemd/network/10-ens3.network
[Match]
Name=ens3
The missing rule for boot_id was added to Apparmor 2.13
(https://gitlab.com/apparmor/apparmor/-/blob/apparmor-2.13/profiles/apparmor.d/abstractions/nameservice#L35)
and was later refined in the master branch. As such, marking as fix
committed.
** Changed in: apparmor (Ubuntu)
Status: New =
On 2020-05-06 2:49 p.m., Andreas Hasenack wrote:
> There are many alternatives here.
IIRC, `chmod -x` snippets from /etc/update-motd.d/ was the way to go a
few releases ago when it was consumed by run-parts.
> I think fixing this doesn't warrant an SRU, but should be considered for
> the devel re
Yay, this appears to have been fixed in focal:
$ namei -l /etc/ssl/private/ssl-cert-snakeoil.key
f: /etc/ssl/private/ssl-cert-snakeoil.key
drwxr-xr-x root root /
drwxr-xr-x root root etc
drwxr-xr-x root root ssl
drwx--x--- root ssl-cert private
ssl-cert-snakeoi
Testing in an Ubuntu 18.04 LTS lxc container.
root@bionic:/tmp/u-r-u-proposed# apt-cache policy chrony
chrony:
Installed: 3.5-6ubuntu6
Candidate: 3.5-6ubuntu6
Version table:
*** 3.5-6ubuntu6 500
500 http://192.168.10.7/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/statu
There are many alternatives here. What you describe is one, and you
could then also add a systemd override with that exec check. A bit
cumbersome, though.
Another one is specific to this service, and that is to set ENABLED=0 in
/etc/default/motd-news.
I think fixing this doesn't warrant an SRU, b
This was fixed in Debian at version 244.2-1, which is earlier than the
version in focal, so this is fix released for focal.
** Changed in: systemd (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pac
TEST-21 did not fail for any arch for autopkgtests on bionic and eoan.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-eoan
** Tags added: verification-done verification-done-bionic verification-done-eoan
--
You received this bug notification because you are
I also tested upgrading an 19.10 Ubuntu desktop install with chrony
installed to 20.04 LTS and chrony remained installed.
bdmurray@clean-eoan-amd64:/tmp/u-r-u-proposed$ apt-cache policy chrony
chrony:
Installed: 3.5-6ubuntu6
Candidate: 3.5-6ubuntu6
Version table:
*** 3.5-6ubuntu6 500
autopkgtest now passes on arm64:
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/s/systemd/20200428_033750_621b2@/log.gz
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verifi
no build failures to verify this bug with, but manually adding build
test failure shows both bionic and eoan correctly display the build test
failure summary:
bionic:
OK: 233
FAIL: 1
SKIP: 20
TIMEOUT:0
The output from the failed tests:
50/254 test-network
** Also affects: systemd (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Statu
I tested upgrading an lxc container with chrony installed by downloading
the tarball from http://archive.ubuntu.com/ubuntu/dists/focal-
proposed/main/dist-upgrader-all/current/ as the meta-release files have
not been updated for Focal. During the upgrade process chrony was kept
and systemd-timesync
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1877167
Title:
package dbus 1.12.16-2ubuntu2 failed to install/upgrade: triggers
loopin
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu.
https://bugs.launchpad.net/bugs/1877165
Title:
package libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-3 failed to
install/u
xenial:
ubuntu@lp1858412-x:~$ dpkg -l systemd|grep systemd
ii systemd229-4ubuntu21.27 amd64system and service manager
ubuntu@lp1858412-x:~$ du -sh /var/log/journal/remote
65M /var/log/journal/remote
ubuntu@lp1858412-x:~$ sudo journalctl -D /var/log/journal/remote
--vacuum-siz
Public bug reported:
upgrade from 18.04.4 to 20.04 server
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libgdk-pixbuf2.0-0:amd64 2.40.0+dfsg-3
ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
Uname: Linux 4.15.0-99-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture
Public bug reported:
upgrade from 18.04.4 to 20.04 server
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: dbus 1.12.16-2ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18
Uname: Linux 4.15.0-99-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5
After many hours of tinkering around, I made the headset with microphone
to be fully recognized and working on Dell Latitude 7389! The
combination was to set pin 0x21 to "Headphones" as Jeff metioned using
hdajackretask. Then, setting the ALSA config to model "alc256-asus-mic"
adding "options snd-h
bionic:
ubuntu@lp1858412-b:~$ dpkg -l systemd|grep systemd
ii systemd237-3ubuntu10.39 amd64system and service manager
ubuntu@lp1858412-b:~$ du -sh /var/log/journal/remote
417M/var/log/journal/remote
ubuntu@lp1858412-b:~$ sudo journalctl -D /var/log/journal/remote/
--vacuum-s
sorry, i missed that it was already verified for bionic
--
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/1858412
Title:
systemd vacuuming does not work for remote journals
All autopkgtests for the newly accepted ubuntu-release-upgrader (1:20.04.19)
for focal have finished running.
The following regressions have been reported in tests triggered by the package:
update-manager/1:20.04.10 (armhf)
update-notifier/3.192.30 (armhf)
Please visit the excuses page listed b
Just upgraded to 20.04LTS and the problem has not changed.
--
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/1829568
Title:
[GL703VD, Realtek ALC295, Black Headphone left
This bug was fixed in the package base-files - 11ubuntu7
---
base-files (11ubuntu7) groovy; urgency=medium
[ Simon Deziel ]
* motd/50-motd-news: abort early if curl is missing (LP: #1875644)
-- Andreas Hasenack Wed, 06 May 2020 09:25:15
-0300
** Changed in: base-files (Ubuntu
This issue should be resolved by
https://git.kernel.org/linus/1dace0116d0b, which appeared in v4.2. If
the kernel contains that commit, the "pci=use_crs" boot parameter should
not be needed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Public bug reported:
This morning, our 2 Bionic machine configured with the wireguard's PPA
and using systemd-networkd to configure the wireguard tunnel started
misbehaving. Why this started just now is unclear ATM but their dmesg
was filled with this:
validate_nla: 100 callbacks suppressed
netli
** Description changed:
- When you download a DEB file within 20.04 Ubuntu Beta and you double
- click it the file is opened by the archive manager. I would expect the
- installer to open the file just like in previous versions of Ubuntu.
+ [Impact]
+
+ * When a deb is downloaded the default ha
Public bug reported:
After suspend to RAM sound device changes from default HDMI to S/PDIF. After
changing it again to HDMI right speaker stops to respond. I can hear only the
sound from left speaker during sound test from the settings menu.
After the first wake from suspend you can find in mess
Please see attached systemd log
** Attachment added: "jrn"
https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1877129/+attachment/5367437/+files/jrn
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to jackd2 in Ubuntu.
htt
I can confirm this still occurs in Ubuntu 20.04 on my Dell Latitude 7389 (also
using ALC3253).
On a fresh install, the audio jack does not even recognize when a headset is
connected at all. After following Jeff Conner suggestion on comment #5, it now
recognizes them and sound output works as ex
Enabling, but not configuring CONFIG_RT_GROUP_SCHED seems likely to be the
cause of this:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/?h=master-next&id=9b039fc517876d312e7fa0955571101a299c91f5
Some discussion of this WRT lowlatency kernel is here:
https://bugs.
Same probleme with the modification you suggest.
root@bowser:~# cat /etc/systemd/system/mnt-nas.mount
[Unit]
Description=NAS devices
After=network-online.target
[Mount]
What=192.168.1.20:/volume2/media
Where=/mnt/nas
Type=nfs
Options=_netdev,auto
[Install]
WantedBy=multi-user.target
root@bowser:
eoan:
ubuntu@lp1858412-e:~$ dpkg -l systemd|grep systemd
ii systemd242-7ubuntu3.7 amd64system and service manager
ubuntu@lp1858412-e:~$ du -sh /var/log/journal/remote
273M/var/log/journal/remote
ubuntu@lp1858412-e:~$ sudo journalctl -D /var/log/journal/remote
--vacuum-size=10
Hello Christian, or anyone else affected,
Accepted ubuntu-release-upgrader into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-release-upgrader/1:20.04.19 in a few hours, and then in the
-proposed repository.
Please help us by testing t
Could you add a 'journalctl -b 0' log from a session having the issue?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rtkit in Ubuntu.
https://bugs.launchpad.net/bugs/1875665
Title:
rtkit-daemon[*]: Failed to make ourselve
Thank you for your bug report, bug #1875665 has similar warnings
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.net/bugs/1877129
Title:
jackd won't run in realtime
Status in jackd2
Could you add a 'journalctl -b 0' log from a session having the issue?
** Changed in: jackd2 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to jackd2 in Ubuntu.
https://bugs.launchpad.n
No i have not changed anything i just pulled my laptop out of sleep mode
and i got the error
On Wed, May 6, 2020 at 4:02 AM Sebastien Bacher
wrote:
> Thank you for your bug report, the log has
>
> Failed to restart cups.service: Unit -.mount is masked.
>
> Did you do any change to the cups syste
I have restarted it again on LP in case it was a flaky network after
all.
At the same time I have added some debug statements and prepare a bileto
ticket to run the tests there as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subsc
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a membe
Public bug reported:
Was using jackd2 for ages, never had this issue. The usual limits.conf
tweaks are present. Jackd won't run in realtime even as root. It's very
easy to reproduce in Focal.
Before upgrade, was working:
Ubuntu 18.04.4 LTS
uname -r
kernel 5.3.0-51-generic
jackd --version
jackdmp
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a membe
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: apport (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
Ha, that was a good red-herring
It doesn't fail at this test despite all the error messages thrown out.
It does
1. build chrony without root (works with tests skipped as it isn't root)
2. passes other tests as it ERRORs but detects that the environment is the
reason for that
The actual error is:
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a membe
At the actual build time it is skipped for being "non-root".
But I think this is as easy as now trying to set HW-time in a container.
** Also affects: chrony (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: apport (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: grub2 (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of U
It is the build phase that fails.
Reproduced in armhf container on canonistack.
1. get the source and build deps
2. build that until it breaks
3. re-run via
$ cd ~/chrony-3.5/test/system
$ ./run -i 20 -m 2
In this repro environment I get two extra fails at:
005-scfilter Testing system call
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a membe
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a membe
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a membe
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a membe
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a membe
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a membe
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: apport (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member o
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a membe
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member o
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a membe
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member o
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a membe
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member o
** Tags removed: sts-sponsor
** Tags added: sts-sponsor-ddstreet
--
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/1876600
Title:
cookie overruns can cause org.freedesktop.sy
This issue has sat incomplete for more than 60 days now. I'm going to
close it as invalid. Please feel free re-open if this is still an issue
for you. Thank you.
** Changed in: alsa-driver (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a membe
1 - 100 of 262 matches
Mail list logo
