When switching a bug's type from Public to Public Security, please
clarify what about it leads you to suspect it represents an exploitable
vulnerability. I'm switching it back to a regular Public bug in the
meantime.
If this was triggered by the earlier mention of a use-after-free
condition, it
Please don't set OpenStack bugs to Public Security without some
explanation as to why you believe this to be an exploitable risk which
needs attention from the OpenStack vulnerability managers for
coordinating a possible security advisory. I'm switching this back to a
normal Public bug for now,
Slawek is one of the upstream Neutron developers. One of the Ubuntu
package maintainers will need to take care of Ubuntu's package updates.
It's probably mildly confusing that this bug report is marked as
affecting the upstream project (where it's been fixed for months) but
also the Ubuntu
I too am entirely out of my comfort zone with Javascript, so my level of
certainty is low, based solely on the text of CVE-2019-8331 which says
(all?) Bootstrap versions prior to 3.4.1 are affected. I also did not
check the rdepends for python3-xstatic-bootstrap-scss in Ubuntu and
perhaps
Public bug reported:
Installed Ubuntu 18.04 final release and I tried setting up a swap with
the pre-seed config but the swap value fails to go above 2GB.
Here's my configuration:
```
## Partitioning regular
d-i partman-auto/disk string /dev/sda
d-i partman-auto/method string regular
d-i
I've faced the same issue on Fedora 32, Ubuntu 20.04 and Pop OS 20.04. Don't
know if it help just thought of sharing.
Let me know if I can help by uploading any logs. More than happy to help.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
The summary says it all. While apt says, package version is 8.0.1, which
would correspond to the most recent release of zyGrib, the actual
version of the installed binary is 7.0.0.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: zygrib (not installed)
** Summary changed:
- Credentials API allows listing and retrieving of all users credentials
+ [OSSA-2019-006] Credentials API allows listing and retrieving of all users
credentials (CVE-2019-19687)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
- This issue is being treated as a potential security risk under embargo.
- Please do not make any public mention of embargoed (private) security
- vulnerabilities before their coordinated publication by the OpenStack
- Vulnerability Management Team in the form of an
** 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/1533724
Title:
[SRU] keystone-signing folders fill /tmp and seriously slow down
reboots
To manage
Just to get confirmation, this bug was only introduced as of Stein,
right? It's not present in Rocky or earlier?
Gage, assuming the above is true, and if nobody has any other concerns
about your proposed impact description in comment #17, you can probably
go ahead and request a CVE assignment for
Somewhat of a grammar nit on the updated title, but it would be "every
user's" or "all users'" (placement of the apostrophe in possessive nouns
is significant for indicating plurality, and "every" modifies a singular
noun as opposed to "all" which modifies a plural). This nuance in the
English
Daniel, is there any organization you want credited along with you for
reporting this defect?
Gage, I think the use of "user's" in the title (copied from the report
itself) incorrectly suggests that a user only has access to credentials
for their own user rather than, as the description explains,
The OpenStack VMT will request a CVE assignment from MITRE once we agree
on a complete impact description for this report. If you're interested
in the details of our report handling processes, you can find them here:
https://security.openstack.org/vmt-process.html#process
** Description changed:
Public bug reported:
upgrading from Ubuntu 16.04 to 16.10
ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: virtualbox-dkms 6.0.14-dfsg-1
ProcVersionSignature: Ubuntu 5.3.0-20.21-generic 5.3.7
Uname: Linux 5.3.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.1
Architecture: amd64
Since this has come up again in bug 1581977 as representing a security-
related concern, I'm adding the security bugtag to it for increased
visibility. Note this is not the same as treating it as a security
vulnerability, and I don't have the impression that any CVE assignment
or security advisory
I'm seeing this problem, past the middle of year 2019!
What would you like to know about my configuration?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1714302
Title:
Mirror displays not offered,
The way to make it work is to place the EFI on a separate GPT raided
partition, outside the LVM PV. Which I forgot about when I wrote the idea
earlier.
On 1 July 2019 8:54:49 am John Robinson <1466...@bugs.launchpad.net>
wrote:
> You can use 0.90 or 1.0 metadata. Both leave the partitions
> I have EFI partitions on both disks but it is not possible to RAID1 these
> as they are FAT32.
Actually it is possible to RAID1 FAT32. The problem is that the default
RAID format places a header at the front of the partition, which stuffs up
the boot loader. But if you use the 0.9.0 format
** Changed in: ossa
Status: Confirmed => Fix Released
** Summary changed:
- [SRU] Unable to install new flows on compute nodes when having broken
security group rules (CVE-2019-10876)
+ [SRU] [OSSA-2019-002] Unable to install new flows on compute nodes when
having broken security group
In that case, as we expect stable/ocata is unaffected, the affects line
should be revised as follows:
Affects: >=11.0.0 <11.0.7, >=12.0.0 <12.0.6, >=13.0.0 <13.0.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks Gage, your proposed impact description in comment #43 looks great
(modulo decisions on any stable/ocata backport altering the "affects"
line).
** Changed in: ossa
Status: Incomplete => Confirmed
** Changed in: ossa
Assignee: (unassigned) => Gage Hugo (gagehugo)
** Changed in:
I see backports to pike, queens, rocky and the stein release candidate
branches have been proposed according to
https://review.openstack.org/#/q/I17ab643abbd2ec21eda4ae1dfb9abf2d4b0657f2
and have been positively scored by some stable branch reviewers, so I'm
going to take that as a sign the
Thanks for the heads up, Joshua!
The OpenStack VMT is, in turn, waiting for the reporter, Neutron
reviewers or, well, anybody really to clarify the impact of this bug and
indicate whether a fix will be implemented in stable branches (per my
comment #35).
--
You received this bug notification
Is there a chance anyone's working on backporting
I17ab643abbd2ec21eda4ae1dfb9abf2d4b0657f2 upstream to stable/pike
through stable/rocky? Is the impact roughly similar in nature to
https://security.openstack.org/ossa/OSSA-2019-001.html or can someone
make an attempt at describing a viable exploit
Chris: I don't doubt that this could be a crippling incident, but you
say you took down your own cloud and did so accidentally... can you
provide a similar scenario where a non-admin user is able to
intentionally bring about the same result? That's mostly what I'm
looking for to be able to
Thanks! I'm mostly looking for an exploit scenario whereby a malicious
actor can intentionally cause harm/deny access to the operating
environment for other users. Absent this, we'd probably not bother to
issue a security advisory about it.
--
You received this bug notification because you are a
Is the denial of service concern that an authenticated user could
engineer a build failure (perhaps by attempting to boot an intentionally
corrupt image they uploaded) and perform that action repeatedly to cause
the environment to no longer to be able to schedule instances to any of
the hypervisor
A CVE can be requested by anyone for any defect. The OpenStack VMT
doesn't generally request CVEs for projects it doesn't oversee, but we
have a brief overview of what we'd generally recommend putting in
MITRE's CVE Request form documented at https://security.openstack.org
Starting from Linux Kernel 4.19, the Asus USB-AC51 is supported.
See
https://github.com/torvalds/linux/blob/v4.19/drivers/net/wireless/mediatek/mt76/mt76x0/usb.c#L30
You might wanna give it a try.
(Try install all the following debian packages:
(In reply to Marco Bonardo [::mak] from comment #106)
> So, we apparently do:
> ctrl => .com
> shift => .net
> ctrl + shift => .org
>
> First, I'm not convinced .net and .org are more important than the other
> many tlds around, for example in a localized build it would be far more
> interesting
While remote connection is enabled for chrome-remote-desktop
There are environment variables for GUI login session. Such as:
CHROME_REMOTE_DESKTOP_SESSION=1
CHROME_USER_DATA_DIR=/home/vagrant/.config/chrome-remote-desktop/chrome-profile
--
You received this bug notification because you are a
I found that this issue could also be triggered by chrome-remote-desktop
After uninstall chrome-remote-desktop, this issue is gone.
(In fact, disable remote connections also helps. Not necessary uninstall
chrome-remote-desktop.)
DistroRelease: Ubuntu 18.04.1
Package: gnome-terminal
This bug also affects
lsb_release -a
LSB Version:
core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch
Distributor ID: Ubuntu
Description:Ubuntu 16.04.5 LTS
Release:16.04
The failing tests:
*** FATAL ERROR - COMPUTED RESULT IS LESS THAN HALF ACCURATE ***
EXPECTED RESULTCOMPUTED RESULT
1 ( 0.277223, -0.348651) ( 0.110137E+13, 0.164627E+13)
2 ( 0.806693, -0.492507) (
This also happens on Power9. I was able to reproduce it with upstream's
trunk as of last week.
** Bug watch added: Mozilla Bugzilla #1477176
https://bugzilla.mozilla.org/show_bug.cgi?id=1477176
** Also affects: firefox via
https://bugzilla.mozilla.org/show_bug.cgi?id=1477176
Importance:
The error is due to clang using this header:
/usr/include/powerpc64le-linux-gnu/c++/8/bits/c++config.h
The difference between this header for gcc7 and gcc8:
--- /usr/include/powerpc64le-linux-gnu/c++/7/bits/c++config.h 2018-07-20
21:27:51.0 +0930
+++
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84654
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1783705
Title:
clang errors with __float128 is not supported on this target on
ppc64le
To manage
Reproduced with 4.17-rc7
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1782716
Title:
With -rc7:
[ 333.596521] EEH: PHB#33 failure detected, location: N/A
[ 333.596563] CPU: 12 PID: 811 Comm: kworker/u257:1 Not tainted
4.18.0-041800rc7-generic #201807292230
[ 333.596576] Workqueue: events_unbound commit_work [drm_kms_helper]
[ 333.596578] Call Trace:
[ 333.596582]
With upstream kernels I get this (and a frozen desktop):
[ 2604.488694] [drm] dce_get_required_clocks_state: clocks unsupported disp_clk
681000 pix_clk 154000
[ 2634.551719] cfg80211: Loading compiled-in X.509 certificates for regulatory
database
[ 2634.554170] cfg80211: Loaded X.509 cert
Public bug reported:
Running Ubuntu cosmic on ppc64le, since the GCC 8 update I am unable to
compile programs with clang that include cmath:
$ cat foo.cpp
#include
int main() { }
$ clang++ foo.cpp
In file included from foo.cpp:1:
In file included from
After that, it fails to recover:
2372.712463] [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:43:crtc-0]
hw_done or flip_done timed out
[ 2538.367847] INFO: task kworker/u257:2:8785 blocked for more than 120 seconds.
[ 2538.367917] Not tainted 4.17.0-5-generic #6-Ubuntu
[ 2538.367968]
Public bug reported:
Running the 4.17.0-5-generic kernel on a ppc64le machine with a Radeon
R9 Fury GPU
0033:01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
Fiji [Radeon R9 FURY / NANO Series] (rev ff)
[ 2361.958847] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring
** Changed in: oem-priority
Status: Confirmed => 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/1772844
Title:
snapd didn't initialize all the seeded snaps
To manage
** Changed in: oem-priority
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/1772374
Title:
ubiquity need mount point /sys/firmware/efi/efivars
To manage
https://packages.ubuntu.com/bionic/gnocchi-api seems to indicate it's
coming straight through an import from Debian, where the current
OpenStack ecosystem is packaged to use only Python 3.x. This probably
makes it incompatible with the official Ubuntu OpenStack packaging which
still relies on
In Ubuntu 16.04 I made this work by adding the following to crontab -e
@reboot sleep 15; /sbin/sysctl -p
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/50093
Title:
Some sysctls are ignored on boot
I've confirmed #10 works. File merge proposal:
https://code.launchpad.net/~swem/ubuntu-seeds/ubuntu.cosmic/+merge/346726
https://code.launchpad.net/~swem/ubuntu-seeds/ubuntu.bionic/+merge/346727
** Package changed: snapd (Ubuntu) => ubuntu-meta (Ubuntu)
** Also affects: snapd
Importance:
** Attachment added: "seed.yaml"
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1772844/+attachment/5143203/+files/seed.yaml
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772844
Title:
The snapd stuck here:
$ snap watch --last=seed
Automatically connect eligible plugs and slots of snap "gnome-calculator"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772844
Title:
snapd didn't
output of:
snap list
** Attachment added: "snap-list.txt"
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1772844/+attachment/5143198/+files/snap-list.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
output of
snap tasks --last=seed
** Attachment added: "snap-tasks-last-seed.txt"
https://bugs.launchpad.net/oem-priority/+bug/1772844/+attachment/5143197/+files/snap-tasks-last-seed.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
UNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: snapd
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: oem-priority
Importance: Undecided
Assignee: Chen-Han Hsiao (Stanley) (swem)
Status: New
** Affects: snapd (Ubuntu)
Importance:
$ ll /var/lib/snapd/seed/snaps/
total 305668
drwxr-xr-x 2 root root 4096 May 22 04:17 ./
drwxr-xr-x 4 root root 4096 May 22 04:17 ../
-rw-r--r-- 2 root root 90812416 May 22 04:15 core_4650.snap
-rw-r--r-- 2 root root 146276352 May 22 04:15 gnome-3-26-1604_64.snap
-rw-r--r-- 2 root root
Proposed for merging:
https://code.launchpad.net/~swem/ubiquity/+git/ubiquity/+merge/346665
https://code.launchpad.net/~swem/ubiquity/+git/ubiquity/+merge/34
** Changed in: oem-priority
Assignee: (unassigned) => Chen-Han Hsiao (Stanley) (swem)
--
You received this bug notificat
This issue fixed in daily build bionic-desktop-amd64.iso (20180522)
** Changed in: oem-priority
Status: Confirmed => Fix Committed
** Changed in: oem-priority
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
http://manpages.ubuntu.com/manpages/bionic/man8/efibootmgr.8.html
Note: efibootmgr requires that the kernel support access to EFI non-
volatile variables through /sys/firmware/efi/vars or
/sys/firmware/efi/efivars/.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
My patch to fix this issue:
** Patch removed: "0001-add-mount-point-LP-1759196.patch"
https://bugs.launchpad.net/oem-priority/+bug/1772374/+attachment/5142254/+files/0001-add-mount-point-LP-1759196.patch
** Patch added: "0001-add-mount-point-LP-1772374.patch"
installation failed:
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1772374/+attachment/5142253/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Without mount point /sys/firmware/efi/efivars for target system,
ubiquity sometimes failed to install bootloader on target system.
May 21 08:21:55 ubuntu ubiquity[29387]: Setting up grub-efi-amd64
(2.02-2ubuntu8) ...
May 21 08:21:56 ubuntu ubiquity[29387]:
May 21 08:21:56
My patch to fix this issue:
** Patch added: "0001-add-mount-point-LP-1759196.patch"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1772374/+attachment/5142254/+files/0001-add-mount-point-LP-1759196.patch
** Also affects: oem-priority
Importance: Undecided
Status: New
--
** Attachment added: "sosreport-u-Inspiron-5379-20180511040643.tar.xz"
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1770580/+attachment/5137649/+files/sosreport-u-Inspiron-5379-20180511040643.tar.xz
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Device: Dell Inspiron 5379 2-in-1 laptop
Image: ubuntu-18.04-desktop-amd64.iso
2-in-1 laptop won't auto-rotate after finishing installation.
iio-sensor-proxy.service is stopped during oem installation. But not restarted
after install.
This issue will gone after reboot
** Also affects: ubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
** Changed in: ubuntu-meta (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also proposed code changes to ubuntu seeds:
https://code.launchpad.net/~swem/ubuntu-seeds/ubuntu.cosmic/+merge/345355
https://code.launchpad.net/~swem/ubuntu-seeds/ubuntu.bionic/+merge/345356
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
gtk-common-themes is not published in channel "stable/ubuntu-18.04",
thus the image building will fail.
Hi, chipaca
Could you help to publish gtk-common-themes in channel "stable/ubuntu-18.04".
Ref:
$ SNAPPY_STORE_NO_CDN=1 snap download --channel=stable/ubuntu-18.04
gtk-common-themes
Fetching
Code for fetching seeded snap while image building:
https://git.launchpad.net/ubuntu/+source/livecd-rootfs/tree/live-
build/functions?id=af65a5affaecdf538c2d7e90775e9e5c4de8af09#n387
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: oem-priority
Assignee: (unassigned) => Chen-Han Hsiao (Stanley) (swem)
** Changed in: oem-priority
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Note that this issue doesn't happen with official released image
ubuntu-18.04-desktop-amd64.iso.
But does happen with daily build image http://cdimage.ubuntu.com/bionic
/daily-live/pending/bionic-desktop-amd64.iso (For example, 20180508)
I think this issue is introduced between 2018-04-24 and
output of "snap tasks --last=seed"
This issue could be reproduced on every platform.
** Attachment added: "snap-tasks-seed.txt"
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1767896/+attachment/5136966/+files/snap-tasks-seed.txt
--
You received this bug notification because you are
After finishing the installation and reboot, this issue could be observed
before connecting to internet. snapd restarts again and again and consuming
high percentage of cpu.
(Daily Build image: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180508)%)
May 9 06:40:11 u-XPS-13-9360
seeded snap in Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180508)%
$ ll /var/lib/snapd/seed/snaps/
total 273560
drwxr-xr-x 2 root root 4096 May 8 04:23 ./
drwxr-xr-x 4 root root 4096 May 8 04:23 ../
-rw-r--r-- 2 root root 90828800 May 8 04:22 core_4571.snap
-rw-r--r-- 2
Public bug reported:
Don't really remember
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CasperVersion: 1.394
I could reproduce this issue with oem image (somerville 20170614-0).
With exactly the same error "dpkg: cycle found while processing
triggers:"
But can't reproduce this issue with oem image (columbia 20161201-0).
Attachment is the log for oem image (columbia 20161201-0).
** Attachment added:
I'll keep identifying root cause for this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766890
Title:
package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade:
triggers looping,
For Intel GLK user: There is a upstream bug opened and fixed:
https://bugs.freedesktop.org/show_bug.cgi?id=100302
And this patch works for me on Intel Gemini Lake platform:
https://github.com/torvalds/linux/commit/ed69cd40685c949ec9c65701758bbf9e6840240f
This patch is merged starting from
** Changed in: ossa
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/1664931
Title:
[OSSA-2017-005] nova rebuild ignores all image properties and
Headset mode is supported after upgrade linux-generic 4.13.0.16.17 to
4.13.0.17.18.
Install: linux-image-extra-4.13.0-17-generic:amd64 (4.13.0-17.20, automatic),
linux-headers-4.13.0-17-generic:amd64 (4.13.0-17.20, automatic),
linux-headers-4.13.0-17:amd64 (4.13.0-17.20, automatic),
Check on Wyse 3040
with Ubuntu Desktop 17.10
This issue is gone after upgrade linux-generic from 4.13.0.16.17 to
4.13.0.17.18
Install: linux-signed-image-4.13.0-17-generic:amd64 (4.13.0-17.20, automatic),
linux-image-extra-4.13.0-17-generic:amd64 (4.13.0-17.20, automatic),
Public bug reported:
I see this in the kernel log at every boot:
[2.709788] irq 171, desc: a038fa08a600, depth: 1, count: 0, unhandled: 0
[2.709790] ->handle_irq(): 810e5b60,
[2.709793] handle_bad_irq+0x0/0x230
[2.709794] ->irq_data.chip(): 81f711a0,
[
I've also encountered this issue.
$ dpkg --list | grep chromium
ii chromium-browser 60.0.3112.78-0ubuntu0.16.04.1293
amd64Chromium web browser, open-source version of Chrome
ii chromium-browser-l10n
Public bug reported:
$ i3status -v
i3status 2.11 (2017-01-21) © 2008 Michael Stapelberg and contributors
$ i3status
internal error in cfg_init_defaults(order)
/etc/i3status.conf:9: no such option 'general'
$ head /etc/i3status.conf
# i3status configuration file.
# see "man i3status" for
Public bug reported:
https://help.ubuntu.com/11.04/ubuntu-help/session-fingerprint.html
Page contains link https://help.ubuntu.com/11.04/ubuntu-help/hardware.html#auth
Returns "Not Found
The requested URL /11.04/ubuntu-help/hardware.html was not found on this
server."
Stan Ralph
** Affects:
This is fixed by the weather-util 2.3-2 source package in Artful, if
someone wants to attempt an SRU of that to Trusty and/or Xenial.
** Changed in: weather-util (Ubuntu)
Status: New => Fix Released
** Changed in: weather-util (Ubuntu)
Assignee: (unassigned) => Jeremy Stanley
It's been 50 days since I upgraded from 16.04 kernel 4.4 to LTS
Enablement Stack kernel 4.8 and I haven't had this issue again.
https://wiki.ubuntu.com/Kernel/LTSEnablementStack#Ubuntu_16.04_LTS_-
_Xenial_Xerus
$ lspci -nn | egrep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation
This is fixed by the weather-util-data 2.3-1 package in Zesty, but that
version of weather-util contains a nasty Py3k incompatibility which is
fixed in the 2.3-2 package which just migrated to Debian testing today
and so should probably get auto-imported to Zesty soon (after which we
can think
After enabled xenial-proposed and upgrade wget to 1.17.1-1ubuntu1.2,
this issue is fixed.
Reproduce Step:
1. download
http://old-releases.ubuntu.com/releases/16.04.0/ubuntu-16.04-desktop-amd64.manifest
via wget within narrow terminal (< 40 characters)
wget 1.17.1-1ubuntu1.1
$ wget
** Description changed:
+ [Impact]
+ * wget will crash while displaying progress bar under narrow terminal
+ * Upstream already has fixed this issue in commit 7099f489 and 7cb9efa6
+ Steps to reproduce:
+ 1. execute "wget
Hi, Murray
Thanks you help, I will update the bug description.
Also, after checking the latest wget source code, I think upstream
commit
http://git.savannah.gnu.org/cgit/wget.git/commit/?id=7cb9efa668f80ab5ca4d25133c3133e10473d1ef
is also needed.
>From 7cb9efa668f80ab5ca4d25133c3133e10473d1ef
Hi,
I made a testing PPA at ppa:swem/lp1573307
Please help to check if it can fix this issue for you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573307
Title:
wget crashed with SIGSEGV in
This issue could be reproduced with following command. More easily to be
reproduced with narrow terminal (such as 40 characters width)
wget http://old-releases.ubuntu.com/releases/16.04.0/ubuntu-16.04
-desktop-amd64.iso
This issue has been fixed by the following commit
I observed the same messages in /var/log/syslog.
Reconfiguring apparmor as shown in #19 solved the problem for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1594902
Title:
Failed to upgrade to
This was fixed in the 2.3-1 upload to Debian/sid, subsequently imported
to Ubuntu/zesty.
** Changed in: weather-util (Ubuntu)
Assignee: (unassigned) => Jeremy Stanley (fungi)
** Changed in: weather-util (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notifi
you can reproduce with the following:
git clone git://git.denx.de/u-boot
cd u-boot
CROSS_COMPILE=arm-linux-gnueabi- make rock2_defconfig
CROSS_COMPILE=arm-linux-gnueabi- make
I spoke with Alan Modra, and the current theory is that it needs to be
worked around in u-boot. I've submitted a patch
Prior to this commit linking works:
https://sourceware.org/git/gitweb.cgi?p=binutils-
gdb.git;a=commit;h=1a9ccd70f9a7
"Fix the linker so that it will not silently generate ELF binaries with
invalid program headers. Fix readelf to report such invalid binaries."
--
You received this bug
Public bug reported:
With GNU ld (GNU Binutils for Ubuntu) 2.27.51.20161202 (arm-linux-
gnueabi), building my u-boot target fails:
LD u-boot
arm-linux-gnueabi-ld.bfd: u-boot: Not enough room for program headers, try
linking with -N
arm-linux-gnueabi-ld.bfd: final link failed: Bad value
Public bug reported:
#0 cmsGetColorSpace (hProfile=0x0) at cmsio0.c:934
#1 0x7f174b47b438 in GfxICCBasedColorSpace::parse(Array*, OutputDev*,
GfxState*, int) ()
from /usr/lib/x86_64-linux-gnu/libpoppler.so.61
#2 0x7f174b47a952 in GfxColorSpace::parse(GfxResources*, Object*,
libpoppler61:
Installed: 0.44.0-3ubuntu2
liblcms2-2:
Installed: 2.7-1ubuntu1
evince:
Installed: 3.22.0-0ubuntu1
On Ubuntu 16.10 amd64.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640670
** Summary changed:
- qemu-img calls need to be restricted by ulimit (CVE-2015-5162)
+ [OSSA 2016-012] qemu-img calls need to be restricted by ulimit (CVE-2015-5162)
** Changed in: ossa
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of
1 - 100 of 651 matches
Mail list logo
