Public bug reported:
I cant update and download anything.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libavahi-client3:amd64 0.6.32~rc+dfsg-1ubuntu2
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion:
please solve above problem as soon as possible
** Changed in: perl (Ubuntu)
Assignee: (unassigned) => Deepinder Singh (deepinder.singh)
** Description changed:
an error occurred broken count>0
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: perl-base 5.22.1-9ubuntu0.5
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1794734
Title:
package libavahi-client3:amd64 0.6.32~rc+dfsg-1ubuntu2 failed to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cups (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
bash. This problem was most recently seen with package version
4.4.18-2ubuntu1, the problem page at
https://errors.ubuntu.com/problem/c41e9045833aba7b3134d7fb0f0c579757728ac4
contains more
same here, this occured after updating from 17 to 18:
:~$ systemd-analyze
Startup finished in 9.891s (firmware) + 2.196s (loader) + 33.839s (kernel) +
22.189s (userspace) = 1min 8.115s
graphical.target reached after 22.184s in userspace
:~$ systemd-analyze blame
20.698s
It seems like this wants a re-sync from Debian.
--
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/1768026
Title:
echo message hides cursor
Status in vim:
Fix Released
Status
None of the u.e.c crashes linked on top post have been recorded on
nautilus 3.26.4 (available in cosmic for a while, other than proposed),
so we can safely mark this as verified.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done
** Tags removed: verification-needed-done
** Tags added: verification-bionic-done
** Tags removed: verification-bionic-done
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in
They both sound awfully "generic" (pun intended), but I can't really
come up with an example for a bad match, so lets just try it I guess.
That said, isn't the "deeper" problem that these metapackages can be
removed easily even through they are important to keep the kernel up-to-
date (and hence
So, this is a multipath disk, whose parent is the nvme-subsys0 device,
not nvme0 device. The latter is a PCI device, but the former is a
virtual one. Some code to add slaves/holders relationships was added,
but reverted. I will investigate any further discussion about this
upstream, or look into
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
Public bug reported:
It has started happening to me recently, than when I do:
> grep -R something
besides the normal expected output which is of the form:
filename: match
filename: match
...
I also get some lines like this:
clean:filename: match
where the word "clean" appears
Verification done on Xenial by following the test case.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
Verification failed on Bionic when following the test case, the postinst
script has a bad check for the previous version of initramfs-tools it
expected - it is testing against a version from Xenial, not the Bionic
version.
** Tags removed: verification-needed verification-needed-bionic
** Tags
Verification done in Xenial and Bionic as per the test case. It works
fine and will prevent update-initramfs from being stuck in the described
scenarios.
** Tags removed: verification-needed-bionic verification-needed-xenial
** Tags added: verification-done-bionic verification-done-xenial
**
** Merge proposal linked:
https://code.launchpad.net/~tdaitx/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/355789
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
This bug was fixed in the package nautilus - 1:3.26.4-0~ubuntu18.04.1
---
nautilus (1:3.26.4-0~ubuntu18.04.1) bionic; urgency=medium
* New upstream release: 3.26.4 (LP: #1782681, LP: #1765776)
* debian/patches/query-add-recursive-flags-and-use-it-in-search-engines.patch,
** Merge proposal linked:
https://code.launchpad.net/~tdaitx/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/355789
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
Public bug reported:
Hello,
https://packages.debian.org/source/sid/gstreamer1.0
'Source Package: gstreamer1.0 (1.14.3-1)'
Best regards,
--
Cristian Aravena Romero (caravena)
---
https://gstreamer.freedesktop.org/releases/1.14/#1.14.3
== 1.14.3 ==
The third 1.14 bug-fix release (1.14.3) was
S... Running from kvm itself it seems that this is reproducible but
seems related to some lower level issue (both using sil's command and
adding -vga qxl):
journalctl: https://paste.ubuntu.com/p/rdkvsqs8Rs/ (with vga
https://paste.ubuntu.com/p/vJsWbvwdDR/)
xorg.log:
FYI to reproduce I've done this:
# Create the disk
qemu-img create -f qcow2 /tmp/disk.qcow2 10G
# Boot from the iso and install
kvm -drive if=virtio,file=/tmp/disk.qcow2 -m 4096 -cdrom
cosmic-desktop-amd64.iso -boot once=d -vga std
# After install... Then run with just:
kvm -drive
Ah, one more thing to notice, if starting in recovery mode from grub,
and then resuming the run, it was always working (with std vga too).
Thus this looks like a race in initializing the things that xorg needs
to initialize vbe driver
** Changed in: gdm3 (Ubuntu)
Status: Confirmed =>
Hello Stéphane, or anyone else affected,
Accepted lxc into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/3.0.2-0ubuntu1~18.04.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: tzdata (Ubuntu)
Status: Confirmed => Fix Released
** Also affects: tzdata (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: tzdata (Ubuntu Trusty)
Importance: Undecided
Status: New
--
You received this bug notification because you are
Public bug reported:
This is to track the private-files-strict and user-files portion of
https://bugs.launchpad.net/apparmor/+bug/1794820
** Affects: apparmor
Importance: Undecided
Assignee: Jamie Strandboge (jdstrand)
Status: Fix Released
** Affects: apparmor (Ubuntu)
https://gitlab.com/apparmor/apparmor/merge_requests/203/ was committed
upstream.
** Changed in: apparmor
Status: In Progress => Fix Released
** Summary changed:
- private-files-strict abstraction should also limit access to directories
+ private-files-strict and user-files abstractions
I don’t know if this should be a different bug or a note added here.
I have tried to setup Ubuntu 18.04 (bionic) server as a router. I was
trying to set it up with both IPv4 & IPv6 but the installation (dynamic)
would not allow me to get IP from my ISP after setup was complete. When
starting
I have prepared a new merge proposal that includes the right version
check in the postinst for Bionic. This has been uploaded to the Bionic
queue as 0.130ubuntu3.5.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Changed in: xorg (Ubuntu Cosmic)
Importance: Undecided => Critical
--
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/1794280
Title:
gdm doesn't start on a fresh
Hello Tiago, or anyone else affected,
Accepted initramfs-tools into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.130ubuntu3.5 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello tbenst, or anyone else affected,
Accepted initramfs-tools into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.130ubuntu3.5 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
A feature freeze exception is not required for bug fix releases like
this one.
https://wiki.ubuntu.com/FreezeExceptionProcess#FeatureFreeze_for_bugfix-
only_updates
** Summary changed:
- FFe: New release of 'gstreamer1.0' (1.14.3-1) in Debian
+ New release of 'gstreamer1.0' (1.14.3-1) in Debian
lxc-copy is no longer working for me since this "SRU".
Command used:
lxc-copy -n bionic-template -N bionic-new -s
Gives in strace:
ioctl(4, BTRFS_IOC_SNAP_CREATE_V2, {fd=0, flags=0, name="rootfs"}) = -1 EXDEV
(Invalid cross-device link)
Apparently the "fd=0" is wrong. I guess that commit
Seems to be tracked in https://github.com/lxc/lxc/issues/2612 .
** Bug watch added: LXC bug tracker #2612
https://github.com/lxc/lxc/issues/2612
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
** Summary changed:
- ISST-LTE:PNV:Ubuntu180401:Witherspoon:woo: After triggering crash,kdump is
not working and system enters into initramfs state
+ nvme multipath does not report path relationships
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
So, the hidden disk was introduced by hch as commit
8ddcd653257c18a669fcb75ee42c37054908e0d6 just to support nvme multipath.
This thing prevented lsblk from working when there were slaves under the
multipath nvme, as lsblk would postpone processing those, and lsblk
could not process the paths
As a workaround, I suggest setting nvme-core.ko multipath=0 parameter.
Can you try that, rebooting, recreating the kdump-tools initrd, then
crashing?
Cascardo.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools
** Summary changed:
- Upgrade TZ do address 2018-19's Brazilian DST
+ Upgrade TZ to address 2018-19's Brazilian DST
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1750627
Verified that initramfs-tools 0.130ubuntu3.5 in bionic-proposed now
works as expected after following through the testcase.
As expected orphaned old-dkms files are properly removed and no other
files are affected.
** Tags removed: verification-needed verification-needed-bionic
** Tags added:
The verification of the Stable Release Update for cross-toolchain-base-
ports has completed successfully and the package has now been released
to -updates. Subsequently, the Ubuntu Stable Release Updates Team is
being unsubscribed and will not receive messages about this bug report.
In the event
The verification of the Stable Release Update for binutils has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
The verification of the Stable Release Update for binutils has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
The verification of the Stable Release Update for binutils has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter
This bug was fixed in the package gcc-defaults - 1.176ubuntu2.1
---
gcc-defaults (1.176ubuntu2.1) bionic-proposed; urgency=medium
* SRU: LP: #1769657. Bump GCC 8 based versions to 8.2.0.
* Build armel, armhf and arm64 packages on ppc64el.
-- Matthias Klose Mon, 17 Sep 2018
This bug was fixed in the package gcc-7 - 7.3.0-27ubuntu1~18.04
---
gcc-7 (7.3.0-27ubuntu1~18.04) bionic-proposed; urgency=medium
* SRU: LP: #1769657. Update the package to the current version in
cosmic.
gcc-7 (7.3.0-27ubuntu1) cosmic; urgency=medium
* Merge with Debian;
This bug was fixed in the package gcc-8-cross - 18ubuntu0.1
---
gcc-8-cross (18ubuntu0.1) bionic-proposed; urgency=medium
* SRU: LP: #1769657. Build using gcc 8.2.0-1ubuntu2
* Build armel, armhf and arm64 cross packages on ppc64el.
gcc-8-cross (18ubuntu3) cosmic; urgency=medium
This bug was fixed in the package gcc-defaults-ports - 1.176ubuntu1.1
---
gcc-defaults-ports (1.176ubuntu1.1) bionic-proposed; urgency=medium
* SRU: LP: #1769657. Bump GCC 8 based versions to 8.2.0.
-- Matthias Klose Mon, 17 Sep 2018 09:16:43 +0200
** Changed in:
This bug was fixed in the package gcc-7-cross-ports - 17ubuntu0.1
---
gcc-7-cross-ports (17ubuntu0.1) bionic-proposed; urgency=medium
* SRU: LP: #1769657. Build using 7.3.0-18ubuntu0.1.
gcc-7-cross-ports (17ubuntu2) cosmic; urgency=medium
* Build using 7.3.0-18ubuntu2.
Did the testcase verification again for the new 0.130ubuntu3.5 bionic-
proposed upload and I confirm again that it works as expected.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a
This bug was fixed in the package gcc-8 - 8.2.0-1ubuntu2~18.04
---
gcc-8 (8.2.0-1ubuntu2~18.04) bionic-proposed; urgency=medium
* SRU: LP: #1769657. Update the package to the current version in
cosmic.
gcc-8 (8.2.0-1ubuntu2) cosmic; urgency=medium
* Update to SVN 20180727
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu-mate
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
*** This bug is a duplicate of bug 1545811 ***
https://bugs.launchpad.net/bugs/1545811
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1545811, so is being marked as such.
This bug was fixed in the package binutils - 2.30-21ubuntu1~18.04
---
binutils (2.30-21ubuntu1~18.04) bionic-proposed; urgency=medium
* SRU: LP: #1769657
* Build cross packages for armel, armhf, arm64 on ppc64el.
binutils (2.30-21ubuntu1) cosmic; urgency=medium
* Merge with
Bionic only changes the timezone rules for North Korea. Testing results:
TZ=America/Los_Angeles date -d '2018-09-27 00:00:00 UTC'
TZ=America/Los_Angeles date -d '2018-12-27 00:00:00 UTC'
TZ=Asia/Pyongyang date -d '2018-01-27 00:00:00 UTC'
TZ=Asia/Pyongyang date -d '2018-05-04 00:00:00 UTC'
This bug was fixed in the package binutils - 2.30-21ubuntu1~18.04
---
binutils (2.30-21ubuntu1~18.04) bionic-proposed; urgency=medium
* SRU: LP: #1769657
* Build cross packages for armel, armhf, arm64 on ppc64el.
binutils (2.30-21ubuntu1) cosmic; urgency=medium
* Merge with
Hello faleiros, or anyone else affected,
Accepted tzdata into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/tzdata/2018e-
0ubuntu0.14.04 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package binutils - 2.30-21ubuntu1~18.04
---
binutils (2.30-21ubuntu1~18.04) bionic-proposed; urgency=medium
* SRU: LP: #1769657
* Build cross packages for armel, armhf, arm64 on ppc64el.
binutils (2.30-21ubuntu1) cosmic; urgency=medium
* Merge with
This bug was fixed in the package binutils - 2.30-21ubuntu1~18.04
---
binutils (2.30-21ubuntu1~18.04) bionic-proposed; urgency=medium
* SRU: LP: #1769657
* Build cross packages for armel, armhf, arm64 on ppc64el.
binutils (2.30-21ubuntu1) cosmic; urgency=medium
* Merge with
This bug was fixed in the package gcc-7-cross - 21ubuntu0.1
---
gcc-7-cross (21ubuntu0.1) bionic-proposed; urgency=medium
* SRU: LP: #1769657. Build using 7.3.0-18ubuntu0.1.
* Build armel, armhf and arm64 cross packages on ppc64el.
gcc-7-cross (21ubuntu2) cosmic; urgency=medium
This bug was fixed in the package cross-toolchain-base - 26ubuntu0.1
---
cross-toolchain-base (26ubuntu0.1) bionic-proposed; urgency=medium
* SRU: LP: #1769657.
- Fix ARM32 multilib installations.
- Fix binutils installation in the build chroot.
-- Matthias Klose Mon,
This bug was fixed in the package cross-toolchain-base-ports -
22ubuntu0.3
---
cross-toolchain-base-ports (22ubuntu0.3) bionic-proposed; urgency=medium
* SRU: LP: #1769657. Rebuild using updated toolchain packages.
* Don't go beyond the first version available in cosmic.
--
This bug was fixed in the package gcc-8-cross-ports - 9ubuntu0.1
---
gcc-8-cross-ports (9ubuntu0.1) bionic-proposed; urgency=medium
* SRU: LP: #1769657. Build using gcc 8.2.0-1ubuntu0.1.
-- Matthias Klose Mon, 17 Sep 2018 13:51:47 +0200
** Changed in: binutils (Ubuntu Bionic)
Hello faleiros, or anyone else affected,
Accepted tzdata into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/tzdata/2018e-
0ubuntu0.16.04 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://gitlab.com/apparmor/apparmor/merge_requests/206/ has additional
fixes.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1794848
Title:
private-files-strict and
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1789234
and then change the status of the bug to 'Confirmed'.
If, due to the
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: ubuntu-mate
--
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/1775068
** Changed in: apparmor (Ubuntu Cosmic)
Status: In Progress => Fix Committed
** Changed in: apparmor (Ubuntu Trusty)
Status: Triaged => In Progress
** Changed in: apparmor (Ubuntu Xenial)
Status: Triaged => Fix Committed
** Changed in: apparmor (Ubuntu Bionic)
Trusty:
--- trusty-before.log 2018-09-27 14:13:54.747814714 -0700
+++ trusty-after.log2018-09-27 14:11:31.437082432 -0700
@@ -2,10 +2,10 @@
Wed Dec 26 16:00:00 PST 2018
Sat Jan 27 08:30:00 KST 2018
Fri May 4 08:30:00 KST 2018
-Sun May 6 08:30:00 KST 2018
+Sun May 6 09:00:00 KST 2018
Xenial results:
--- xenial-before.log 2018-09-27 13:08:20.984673287 -0700
+++ xenial-after.log2018-09-27 14:07:46.572361764 -0700
@@ -2,10 +2,10 @@
Wed Dec 26 16:00:00 PST 2018
Sat Jan 27 08:30:00 KST 2018
Fri May 4 08:30:00 KST 2018
-Sun May 6 08:30:00 KST 2018
+Sun May 6 09:00:00
The error exists for a good reason: an amd64 processor usually cannot
execute programs that are compiled to run on an ARM architecture.
** Changed in: gccgo-4.9 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
This bug was fixed in the package tzdata - 2018e-0ubuntu0.16.04
---
tzdata (2018e-0ubuntu0.16.04) xenial; urgency=medium
* New upstream release. LP: #1750627
-- Steve Langasek Thu, 27 Sep 2018
08:57:44 -0700
** Changed in: tzdata (Ubuntu Xenial)
Status: Fix Committed
This bug was fixed in the package tzdata - 2018e-0ubuntu0.14.04
---
tzdata (2018e-0ubuntu0.14.04) trusty; urgency=medium
* New upstream release. LP: #1750627.
-- Steve Langasek Thu, 27 Sep 2018
09:05:21 -0700
** Changed in: tzdata (Ubuntu Trusty)
Status: Fix Committed
For precise ESM:
--- precise-before.log 2018-09-27 15:23:25.293064963 -0700
+++ precise-after.log 2018-09-27 15:29:21.681574534 -0700
@@ -2,10 +2,10 @@
Wed Dec 26 16:00:00 PST 2018
Sat Jan 27 08:30:00 KST 2018
Fri May 4 08:30:00 KST 2018
-Sun May 6 08:30:00 KST 2018
+Sun May 6 09:00:00
The verification of the Stable Release Update for tzdata has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
i downloaded that, and tried to poke it.
First of all, i've never seen a 77MB tarball of /sys alone.
Also unpacking that, is dangerous as it does explode in size. However, is
debugging that, please only _list_ the files present in the tarball and only
extract things you need/want.
Reuploaded to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gtk+3.0 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nautilus (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
This workaround can be used also:
1) Run command 'xinput' (without quotes) in a terminal. In the output
identify ID of your mouse.
2) Run command 'xinput -list-props 12' in a terminal where 12 is an
example of your mouse ID. Look for property like 'libinput Accel Speed
(297): 0.00' ...
--- Comment From hbath...@in.ibm.com 2018-09-27 22:06 EDT---
(In reply to comment #61)
> As a workaround, I suggest setting nvme-core.ko multipath=0 parameter. Can
> you try that, rebooting, recreating the kdump-tools initrd, then crashing?
Hi Cascardo,
Where/How to set this parameters?
This bug was fixed in the package mesa - 18.2.1-1ubuntu1
---
mesa (18.2.1-1ubuntu1) cosmic; urgency=medium
* Merge from Debian experimental. (LP: #1714178, #1792873)
* glvnd-fix-a-segfault-in-eglgetprocaddess.diff: Dropped, upstream.
mesa (18.2.1-1) experimental; urgency=medium
This bug was fixed in the package mesa - 18.2.1-1ubuntu1
---
mesa (18.2.1-1ubuntu1) cosmic; urgency=medium
* Merge from Debian experimental. (LP: #1714178, #1792873)
* glvnd-fix-a-segfault-in-eglgetprocaddess.diff: Dropped, upstream.
mesa (18.2.1-1) experimental; urgency=medium
--- Comment From hbath...@in.ibm.com 2018-09-27 02:42 EDT---
Cascardo/Canonical, Did you get a chance to look at the logs attached?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
** Also affects: libxkbcommon (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxkbcommon in Ubuntu.
https://bugs.launchpad.net/bugs/1772512
Title:
Unable to
This bug was fixed in the package apport - 2.20.9-0ubuntu7.4
---
apport (2.20.9-0ubuntu7.4) bionic; urgency=medium
* Handle old reports generated pre-apport with "remember" option.
If the option isn't there, consider as false. (LP: #1791324)
-- Didier Roche Mon, 10 Sep 2018
*** This bug is a duplicate of bug 1772512 ***
https://bugs.launchpad.net/bugs/1772512
** This bug has been marked a duplicate of bug 1772512
Unable to install i386 and amd64 arch at the same time
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libxkbcommon (Ubuntu Bionic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxkbcommon in Ubuntu.
** Description changed:
[Impact]
0.8.2 has completed the fuzzing work started in 0.8.1, so backport the
package from cosmic to fix these CVE's:
CVE-2018-15853 CVE-2018-15854 CVE-2018-15855 CVE-2018-15856
CVE-2018-15857 CVE-2018-15858 CVE-2018-15859 CVE-2018-15861
CVE-2018-15862
** Description changed:
+ [Impact]
+ libxkbcommon-dev:i386/amd64 can't be installed at the same time, because the
package isn't properly multi-archified in bionic
+
+ [Test case]
+ apt install libxkbcommon-dev:i386 libxkbcommon-dev:amd64
+
+ should succeed
+
+ [Regression potential]
+ not
Reproduced in xenial by:
Swapping "quickly enough" between input sources of the same headset (Corsair
HS40 gives Analog and Digital output). Also crashed the settings sound dialog.
In-between crashing, the enumerated sources doubled.
Changing the volume too fast (my volume control is a wheel:
Switching the other tasks to Triaged as well since those changes are
required for the base 1.1.1 feature to be completed.
** Changed in: python2.7 (Ubuntu)
Status: New => Triaged
** Changed in: python3.6 (Ubuntu)
Status: New => Triaged
--
You received this bug notification
** Summary changed:
- failed unit tests during build & autopkgtest fails with openssl 1.1.1 pre3
+ python 2.7 test_ssl hits AttributeError with openssl 1.1.1
** Bug watch added: Python Roundup #34818
http://bugs.python.org/issue34818
** Also affects: python via
*** This bug is a duplicate of bug 1792932 ***
https://bugs.launchpad.net/bugs/1792932
** This bug has been marked a duplicate of bug 1792932
Cosmic Desktop fails to boot in vbox: Xorg assert failure: Xorg:
../../../../dix/privates.c:384: dixRegisterPrivateKey: Assertion
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. You may find it helpful
to read "How to report bugs effectively"
Can confirm this part
>The same thing happens with some gtk3 window shadows, e.g. the gnome
>calculator: Underlying
> windows cannot be brought into focus near the window border in the shadow
> area.
Ubuntu 18.04 gnome shell, multiple monitors, nvidia.
I first noticed as I had a window full
The verification of the Stable Release Update for apport has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a
Could this be backported to bionic with the next SRU? We're possibly
seeing the same timeout issues there.
--
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/1780767
Title:
** Description changed:
- autopkgtest fails with openssl1.1.1 pre3
+ autopkgtest fails with openssl1.1.1
As seen at:
-
- https://bileto.ubuntu.com/excuses/3217/bionic.html
-
- test test_ftplib failed -- multiple errors occurred; run in verbose mode
- for details
-
- test test_ssl failed
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. You may find it helpful
to read "How to report bugs effectively"
Public bug reported:
[Impact]
0.8.2 has completed the fuzzing work started in 0.8.1, so backport the package
from cosmic to fix these CVE's:
CVE-2018-15853 CVE-2018-15854 CVE-2018-15855 CVE-2018-15856
CVE-2018-15857 CVE-2018-15858 CVE-2018-15859 CVE-2018-15861
CVE-2018-15862 CVE-2018-15863
1 - 100 of 103 matches
Mail list logo
