Public bug reported:
Test skipped on Moonshot ARM64:
SKIP timer (KVM acceleration is probably not supported)
But failed on ThunderX instead:
FAIL: ptimer-busy-loop: interrupt received after TVAL/WFI
# TESTNAME=timer TIMEOUT=2s ACCEL= ./arm/run arm/timer.flat -smp 1
timeout -k 1s --foreground
Dependency error of linux-headers-4.15.0-1035-raspi2 package. This is
required itself.
dpkg: package dependencies do not allow configuring the
linux-headers-4.15.0-1035-raspi2 package:
linux-headers-4.15.0-1035-raspi2 depends on linux-raspi2-headers-4.15.0-1035,
however:
The
Thank you for your bug report. What Ubuntu/nautilus version do you use?
Does "gio ls dav://:..." has the same issue or is it specific to nautilus?
** Changed in: nautilus (Ubuntu)
Importance: Undecided => Low
** Changed in: nautilus (Ubuntu)
Status: New => Incomplete
--
You received
This bug was fixed in the package ubuntu-dev-tools - 0.168
---
ubuntu-dev-tools (0.168) eoan; urgency=medium
* grep-merges: flake8-clean.
-- Steve Langasek Tue, 07 May 2019
21:26:05 -0700
** Changed in: ubuntu-dev-tools (Ubuntu)
Status: Fix Committed => Fix Released
--
No, the fix is not yet available.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812527
Title:
[bionic][regression] gnome-shell crashes with SIGSEGV in
meta_window_actor_is_destroyed(self=NULL)
I've returned to non-hwe
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827725
Title:
linux-image-4.15.0-48-lowlatency doesn't boot after update
(16.04)(i386)
To manage notifications about this
@Luca-mg: What your computer sees is the following:
- You attach a device whose USB ID doesn't match any udev rule => the device
is accessible for the root user only.
- then you as the root user start a program that uploads something to the
device.
- the device disconnects and
- a new device
My ubuntu 18.04 have already been updated to the latest state!
But it still crash when I swich workspace.
Is any package I need to install to solve this bug? Or other suggestion?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821867
Title:
network interface is down after post-install reboot of a
kern.log has nothing about it
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827725
Title:
linux-image-4.15.0-48-lowlatency doesn't boot after update
(16.04)(i386)
To manage notifications about
[Expired for autofs (Ubuntu) because there has been no activity for 60
days.]
** Changed in: autofs (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1050021
[Expired for Ubuntu because there has been no activity for 60 days.]
** Changed in: ubuntu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819104
Title:
chyba
@ Chris Rainey: no such a thing in my system.
@ PeterPall: the scanner works properly now, it only didn't on the very
first time using it. Weird, isn't it?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for mutter (Ubuntu) because there has been no activity for 60
days.]
** Changed in: mutter (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1700465
[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for nautilus (Ubuntu) because there has been no activity for 60
days.]
** Changed in: nautilus (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817420
Public bug reported:
All the gicv2 related tests have failed on the ARM64 ThunderX testing
node with X-HWE kernel:;
FAIL gicv2-ipi (terminated on SIGABRT)
FAIL gicv2-mmio (terminated on SIGABRT)
FAIL gicv2-mmio-up (terminated on SIGABRT)
FAIL gicv2-mmio-3p (terminated on SIGABRT)
FAIL
[Expired for mysql-5.7 (Ubuntu) because there has been no activity for
60 days.]
** Changed in: mysql-5.7 (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
If I understand the keepalived > 2.0.x behavior referred to by cdmiller
above (see 2019-03-07 comment) that is not the appropriate response to
the problem. Granted, it mitigates the consequences butr doesn't
address the underlying issue. A systemd-source issue should not cause
keepalived failover
** Tags added: cherry-pick
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1270676
Title:
SD Card Reader broken on UX302LG
To manage notifications about this bug go to:
shadowvzs, it will help immensely if you use Ubuntu with the computer the
problem is reproducible with and file a new report via a terminal to provide
necessary debugging logs:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You received this bug notification because you are a
** Changed in: linux (Ubuntu)
Status: Fix Committed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812561
Title:
[MacBookPro11,5] wakes up and suspends in a loop while closed
** Tags added: latest-bios-3304
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/595047
Title:
Frequent swapping causes system to hang
To manage notifications about this bug go to:
PaulSchulz, it will help immensely if you use Ubuntu with the computer the
problem is reproducible with and file a new report via a terminal to provide
necessary debugging logs:
ubuntu-bug linux
Please feel free to subscribe me to it.
--
You received this bug notification because you are a
Cool, I will try that!
As a heads up though, this sound quality is only after uninstalling and
reinstalling pulse audio and maybe something else (apologies for not
giving better details there, I didn't think to submit a bug until I ran
out of things to try). Before I did that, a voice recorded by
** Tags added: disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1775717
Title:
CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
To manage notifications about this bug go to:
Could you downgrade your linux version until there is no crackling
noise, then we will compare two versions to get what introduced this
issue.
Or maybe it is a HW/motherbord issue, let us wait for one more user to
report this issue on the same computer too.
--
You received this bug notification
** Changed in: pulseaudio
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1583801
Title:
No sound via headphones (headset) when Ubuntu boots with them plugged
in
To
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579410
Title:
Cannot suspend HP ProLiant SE316M1R2
To
As per
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1694225/comments/31
.
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: linux (Ubuntu)
Status: Expired => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1579410
Title:
Cannot suspend HP ProLiant SE316M1R2
To manage notifications about this bug
*** Bug 1549613 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/27867
Title:
Background color is always white, top banner is never displayed in
Public bug reported:
Installing clang caused gnustep to be installed. This is completely
and totally unacceptable. An entire useless suite of applications,
hundereds of packages, was installed just because something depended on
a compiler.
Technically it was a suggests rather than a depend
Public bug reported:
System information
$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
$ apt-cache policy advancecomp
advancecomp:
Installed: 2.1-1ubuntu0.18.04.1
Candidate:
Please update https://help.ubuntu.com/community/UbuntuTime under "Using
the Command Line (unattended)" with the new behavior.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1554806
Title:
Change of
The attached file AudioDevicesInUse.txt suggests that 'audacity' is
stealing the hardware device from pulseaudio -- bypassing it.
If that is the issue then it's unfortunately not a bug. You need to be
sure that all audio software (including audacity) is configured to use
PulseAudio only, and not
I'm a little confused here. What does audacity have to do with the fact
that there is no sound after a reboot? Audacity happens to be running
now...perhaps that's why it's the only program using ALSA. (Is ALSA
deprecated?) But audacity does not start automatically at boot, so it
is irrelevant
And the same bug is not in 19.10.
** Summary changed:
- No animation when GNOME Activities overview is opened
+ [regression] No window spread animation
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry, yes, I failed to notice the attached video.
The bug I was thinking of is different and I can still reproduce this
one.
** Changed in: gnome-shell (Ubuntu Bionic)
Status: Incomplete => Confirmed
** Changed in: gnome-shell (Ubuntu Eoan)
Status: Opinion => Invalid
--
You
I have the issue in Disco... and have since I upgraded to it, as I
mentioned
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1778322/comments/35.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Strange. I do now have the animation in bionic today (gnome-shell
version 3.28.3+git20190124-0ubuntu18.04.2), providing I use the mouse
and not Super+A. So the "regression" I was thinking of isn't in bionic
with the Ubuntu Dock at least.
I will still bisect to see what/where things might have
FWIW, I did basically the same process on 19.04 and it didn't crash.
I also didn't boot because the installer fails to recognize the
encrypted root and doesn't even appear to attempt making a crypttab.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Looks like this was misfiled against logcheck rather than logwatch
** Package changed: logcheck (Ubuntu) => logwatch (Ubuntu)
** Project changed: logcheck => logwatch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
It appears 'audacity' is the exclusive user of /dev/snd/seq according to
your AudioDevicesInUse.txt.
Please try:
1. Reconfiguring Audacity to use PulseAudio and not ALSA or OSS.
2. Uninstalling 'audacity'.
** Summary changed:
- [, Realtek ALC892, Grey SPDIF Out, Rear] No sound at all
+
** Changed in: debian
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822590
Title:
Found storing user fingerprints without encryption
To manage notifications
** Bug watch added: PulseAudio #193
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/193
** Changed in: pulseaudio
Importance: Medium => Unknown
** Changed in: pulseaudio
Remote watch: freedesktop.org Bugzilla #106834 => PulseAudio #193
--
You received this bug notification
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1828066
When reporting bugs in the future please use apport by using 'ubuntu-
Public bug reported:
After rebooting I have no sound. My sound device doesn't show up at all
in the mixer.
Running "sudo alsa force-reload" corrects the problem, until the next
reboot.
This problem started in 18.10 and persists now in 19.04.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Wow, that's a pretty significant chain of deps. Thanks for pruning this
one.
I had started in on libheif but not much beyond inspecting a few
Coverity results. (More in the spirit of learning Coverity than
inspecting libheif, I must be honest.)
I passed along the Coverity results to upstream on
*** This bug is a duplicate of bug 1583801 ***
https://bugs.launchpad.net/bugs/1583801
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 1583801, so it is being marked as such. Please
Also, since the bug was only in 3.30.0 and older (fixed in 3.30.1), that
makes it Invalid for cosmic and later. Because cosmic and later never
had the bug and never needed a fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The fix is not released yet. At the top of the bug you will find "Bionic
In Progress".
** Changed in: gnome-shell (Ubuntu Cosmic)
Status: Fix Released => Invalid
** Changed in: gnome-shell (Ubuntu Eoan)
Status: Fix Released => Invalid
--
You received this bug notification because
apport information
** Tags added: apport-collected
** Description changed:
Issue:
Audio Crackling
Video play back and during games seems to be when the issue is the worst.
Scrolling on pages or hovering over UI objects also seems to trigger it too
though
Testing:
There is crackling
Update: After some unmeasured amount of time, for the first time since
ubuntu install on this machine (2017), there is no crackling sound at
any moment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
[Impact]
New Intel CyclonePeak Wifi cards require new firmware to enable.
[Fix]
To avoid conflicts, also update 9000 series firmware to ABI 46 which has been
added since v5.1-rc1 from iwlwifi/for-upstream
95a93535 iwlwifi: update -46 firmwares for 22260 and
Resubmitted SRU for B,C for this kernel cycle.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794232
Title:
Geneve tunnels don't work when ipv6 is disabled
To manage notifications about this bug
Also note, the following sequence seems to avoid the problem so far (4/4
in testing, not conclusive, but it's looking good):
```
dpb@aries:~[]$ sudo modprobe -r iwlmvm
# Suspend/Resume, then...
dpb@aries:~[]$ sudo modprobe iwlmvm
```
--
You received this bug notification because you are a
This is as expected, the root partition in the registered image will not
match the size of the disk that is deployed. It will be large enough to
contain the root partition and provide some blank space. This is by
design and allows VMs to be started with variable size disks. This is
seen early
This bug was fixed in the package livecd-rootfs - 2.581
---
livecd-rootfs (2.581) eoan; urgency=medium
* Remove device nodes later for ubuntu-base:minimized (i.e. docker) builds.
(LP: #1828118)
-- Michael Hudson-Doyle Wed, 08 May 2019
09:59:35 +1200
** Changed in:
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828134
Title:
Wifi not working after suspend/resume
Public bug reported:
About 75% of the time for the past few weeks (I don't have a time where
this started), my wifi is not working after resume from suspend. I'm
happy to provide more debugging info if needed.
I have tried an rmmod/modprobe on on the iwlwifi,iwlmvm modules just to
see after the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825378
Title:
Hi all, could the package maintainer(s) please take a look at this?
This breaks (almost) any WireGuard endpoint configured by systemd-
networkd. Worse, it breaks them silently, which makes for a fun
debugging adventure.
The fixed patch (https://github.com/systemd/systemd-stable/pull/39) has
been
Hi, guys! I saw that this problem has been fixed. My system was updated
today(apt-get update/upgrade), but I'm still facing the crashes. I'm not
familiar with this, but how do I force an update to benefit of this fix?
Sorry for this question.
--
You received this bug notification because you are
Public bug reported:
[Impact]
New Intel CyclonePeak Wifi cards require new firmware to enable.
[Fix]
To avoid conflicts, also update 9000 series firmware to ABI 46 which has been
added since v5.1-rc1 from iwlwifi/for-upstream
95a93535 iwlwifi: update -46 firmwares for 22260 and 9000 series
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.04.4
---
netplan.io (0.96-0ubuntu0.18.04.4) bionic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.04.4
---
netplan.io (0.96-0ubuntu0.18.04.4) bionic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.10.3
---
netplan.io (0.96-0ubuntu0.18.10.3) cosmic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676149
Title:
mate-screenshot crashed with SIGSEGV in g_build_filename()
To manage notifications
** Changed in: ibus
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580463
Title:
Snap blocks access to system input methods (ibus, fcitx, ...)
To manage
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.10.3
---
netplan.io (0.96-0ubuntu0.18.10.3) cosmic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.04.4
---
netplan.io (0.96-0ubuntu0.18.04.4) bionic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
I had this issue and what I did to solve it was:
Deleted relevant files in /etc/apparmor.d/libvirt, e.g.:
1. sudo rm /etc/apparmor.d/libvirt/libvirt-
2. sudo rm /etc/apparmor.d/libvirt/libvirt-.files
3. Restart machine
And then it worked
--
You received this bug notification because you are a
*** This bug is a duplicate of bug 1676149 ***
https://bugs.launchpad.net/bugs/1676149
** This bug has been marked a duplicate of bug 1676149
mate-screenshot crashed with SIGSEGV in g_build_filename()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1676149 ***
https://bugs.launchpad.net/bugs/1676149
** This bug has been marked a duplicate of bug 1676149
mate-screenshot crashed with SIGSEGV in g_build_filename()
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mate-utils (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1676149
Title:
** Changed in: lxqt
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821433
Title:
LXQt save dialogs don't automatically add file extensions
To manage notifications
Public bug reported:
I'm trying to use https://virt-manager.org/ / QEMU. I migrated over a
Ubuntu Guest from Virtualbox, added it to virt-manager, and launch. It
opens the window, then the system freezes.
I don't know if it's a bug in QEMU, libvirt, or virt-manager, or nvidia.
Nvidia is working
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.10.3
---
netplan.io (0.96-0ubuntu0.18.10.3) cosmic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.04.4
---
netplan.io (0.96-0ubuntu0.18.04.4) bionic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.04.4
---
netplan.io (0.96-0ubuntu0.18.04.4) bionic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.04.4
---
netplan.io (0.96-0ubuntu0.18.04.4) bionic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.10.3
---
netplan.io (0.96-0ubuntu0.18.10.3) cosmic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.10.3
---
netplan.io (0.96-0ubuntu0.18.10.3) cosmic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.10.3
---
netplan.io (0.96-0ubuntu0.18.10.3) cosmic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.04.4
---
netplan.io (0.96-0ubuntu0.18.04.4) bionic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.10.3
---
netplan.io (0.96-0ubuntu0.18.10.3) cosmic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.10.3
---
netplan.io (0.96-0ubuntu0.18.10.3) cosmic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.10.3
---
netplan.io (0.96-0ubuntu0.18.10.3) cosmic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.04.4
---
netplan.io (0.96-0ubuntu0.18.04.4) bionic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.10.3
---
netplan.io (0.96-0ubuntu0.18.10.3) cosmic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.10.3
---
netplan.io (0.96-0ubuntu0.18.10.3) cosmic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.10.3
---
netplan.io (0.96-0ubuntu0.18.10.3) cosmic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.10.3
---
netplan.io (0.96-0ubuntu0.18.10.3) cosmic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
This bug was fixed in the package netplan.io - 0.96-0ubuntu4.1
---
netplan.io (0.96-0ubuntu4.1) disco; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
pass; it
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.04.4
---
netplan.io (0.96-0ubuntu0.18.04.4) bionic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.04.4
---
netplan.io (0.96-0ubuntu0.18.04.4) bionic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.04.4
---
netplan.io (0.96-0ubuntu0.18.04.4) bionic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
This bug was fixed in the package netplan.io - 0.96-0ubuntu0.18.10.3
---
netplan.io (0.96-0ubuntu0.18.10.3) cosmic; urgency=medium
* debian/patches/git_revert_explicit_renderer_def_ebc212a.patch: revert
commit ebc212a: make renderer values explicit at the end of each parsing
1 - 100 of 594 matches
Mail list logo
