[Bug 2012915] Re: version update needed

[Derrick Stanley]

I'm also having issues with DCO not working with the latest "normal"
non-LTS Ubuntu release. All previous releases prior to Ubuntu Server
24.xx noble seemed to work fine.. this new kernel 6.8.0-31-generic does
not work with the current version of DCO 0.0+git20231103-1. I have to
uninstall the openvpn dco dkms module for a client to be able to connect
if not it just hangs.. For some reason it can't create a tun0 device
when the module is loaded. I tried compiling the latest version from
github but that didn't work.. it resulted in the same issue... I'm going
to see if I can rollback the kernel and see if that works.. I see no
reason why it shouldn't work after doing a rollback to manic minotaur
kernel + dco version.


This is the dmesg error I get..

ubuntu kernel: ovpn: cannot retrieve device in ovpn_netlink_dump_peers:
-19


I've changed nothing with my routine setup.. so I'm assuming it's a issue with 
the new kernel.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2012915

Title:
   version update needed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openvpn-dco-dkms/+bug/2012915/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2066907] [NEW] crash wile upgrading from 23.10 to 24.04

[Crystopher Stanley Carpenter]

Public bug reported:

This is the error generated during upgrade:

Could not calculate the upgrade

An unresolvable problem occurred while calculating the upgrade.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: ubuntu-release-upgrader-core 1:23.10.14
ProcVersionSignature: Ubuntu 6.5.0-35.35-generic 6.5.13
Uname: Linux 6.5.0-35-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Thu May 23 10:09:21 2024
InstallationDate: Installed on 2023-11-08 (197 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to mantic on 2024-05-23 (0 days ago)
VarLogDistupgradeTermlog:

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug dist-upgrade mantic third-party-packages 
wayland-session

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2066907

Title:
  crash wile upgrading from 23.10 to 24.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2066907/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2042744] Re: su -s /bin/sh -c "keystone-manage db_sync" keystone

[Jeremy Stanley]

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 didn't seem to imply that the underlying bug was inside
keystone, but maybe should be filed against the eventlet project
instead.

** Information type changed from Public Security 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/2042744

Title:
  su -s /bin/sh -c "keystone-manage db_sync" keystone

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/2042744/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1452641] Re: Static Ceph mon IP addresses in connection_info can prevent VM startup

[Jeremy Stanley]

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, but if you suspect this report represents an
actual security risk then please explain and set it to Public Security
again. Thanks!

** Information type changed from Public Security 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/1452641

Title:
  Static Ceph mon IP addresses in connection_info can prevent VM startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1452641/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1939733] Re: [OSSA-2021-005] Arbitrary dnsmasq reconfiguration via extra_dhcp_opts (CVE-2021-40085)

[Jeremy Stanley]

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 packages which still need the report triaged.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939733

Title:
  [OSSA-2021-005] Arbitrary dnsmasq reconfiguration via extra_dhcp_opts
  (CVE-2021-40085)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1939733/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1940450] Re: XSS The data-template attribute of the tooltip and popover plugins lacks input sanitization and may allow attacker to execute arbitrary JavaScript.

[Jeremy Stanley]

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 incorrectly assumed it might be used by more packages or by
unpackaged software on people's systems.

I'll continue trying to get one of the Horizon developers to provide
input on this report... I am but a humble vulnerability coordinator in
this particular case, far from being a subject matter expert on the
software.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1940450

Title:
  XSS The data-template attribute of the tooltip and popover plugins
  lacks input sanitization and may allow attacker to execute arbitrary
  JavaScript.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1940450/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1930651] [NEW] Ubuntu installer doesn't allow setting swap higher than 2GB

[Stanley Phoong]

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 partman-auto/choose_recipe select atomic

# Swap Memory
d-i partman-auto/cap-ram string 4096
d-i partman-basicfilesystems/no_swap boolean false
#d-i partman-swapfile/percentage string 50
d-i partman-swapfile/size string 4096

# This makes partman automatically partition without confirmation, provided
d-i partman-partitioning/confirm_write_new_label boolean true
d-i partman/choose_partition select finish
d-i partman/confirm boolean true
d-i partman/confirm_nooverwrite boolean true
```

I've seen others facing similar issues and their recommendation was to
use `d-i partman-auto/cap-ram` to configure the value but I've tried
setting it to false as well as a larger value and it still doesn't work.

What we are expected to see if the swap value increase to 4GB as shown
in the pre-seed config.

Possible related issue: https://bugs.launchpad.net/ubuntu/+source
/partman-auto/+bug/1767299

Any help?

** Affects: partman-auto (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930651

Title:
  Ubuntu installer doesn't allow setting swap higher than 2GB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1930651/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1878279] Re: Touchpad not recognized on Lenovo Ideapad 5 14IIL05 81YH

[Stanley Fernandes]

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 Ubuntu.
https://bugs.launchpad.net/bugs/1878279

Title:
  Touchpad not recognized on Lenovo Ideapad 5 14IIL05 81YH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1878279/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1880595] [NEW] program version is 7.0.0 instead of 8.0.1

[Stanley]

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)
ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18
Uname: Linux 4.15.0-101-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.14
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon May 25 20:08:17 2020
InstallationDate: Installed on 2018-04-28 (758 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: zygrib
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: zygrib (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880595

Title:
  program version is 7.0.0 instead of 8.0.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zygrib/+bug/1880595/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1855080] Re: [OSSA-2019-006] Credentials API allows listing and retrieving of all users credentials (CVE-2019-19687)

[Jeremy Stanley]

** 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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855080

Title:
  [OSSA-2019-006] Credentials API allows listing and retrieving of all
  users credentials (CVE-2019-19687)

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1855080/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1613423] Re: Mitaka + Trusty (kernel 3.13) not using apparmor capability by default, when it does, live migration doesn't work (/tmp/memfd-XXX can't be created)

[Jeremy Stanley]

** 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 official OpenStack
- Security Advisory. This includes discussion of the bug or associated
- fixes in public forums such as mailing lists, code review systems and
- bug trackers. Please also avoid private disclosure to other individuals
- not already approved for access to this information, and provide this
- same reminder to those who are made aware of the issue prior to
- publication. All discussion should remain confined to this private bug
- report, and any proposed fixes should be added to the bug as
- attachments.
- 
- 
- 
- In my environment: Trusty (3.13) + JuJu (1.25) w/ latest charms + Kilo 
upgraded to Mitaka (already using non-tunnelled live migrations, after latest 
SRU to disable tunnelled live migrations)
+ In my environment: Trusty (3.13) + JuJu (1.25) w/ latest charms + Kilo
+ upgraded to Mitaka (already using non-tunnelled live migrations, after
+ latest SRU to disable tunnelled live migrations)
  
  BUG #1
  
  My compute nodes are NOT loading "apparmor" libvirt capability by
  default:
  
  inaddy@tkcompute01:~$ virsh capabilities | grep apparmor | echo $?
  1
  inaddy@tkcompute02:~$ virsh capabilities | grep apparmor | echo $?
  1
  inaddy@tkcompute03:~$ virsh capabilities | grep apparmor | echo $?
  1
  
  Because "libvirt" is loaded before apparmor profile is loaded and
  qemu.conf doesn't specify 'security_driver = "apparmor' in its file. If
  you try to add the security driver to the file, libvirt and nova-compute
  won't start because apparmor isn't started when they start. For trusty,
  apparmor is started as a legacy SYS-V init script, at the end of
  initialisation, causing this problem.
  
  After re-starting libvirt-bin service, apparmor starts being used:
  
  inaddy@tkcompute01:~$ sudo service libvirt-bin restart
  libvirt-bin stop/waiting
  libvirt-bin start/running, process 7031
  inaddy@tkcompute01:~$ virsh capabilities | grep apparmor | echo $?
  0
  
  inaddy@tkcompute02:~$ sudo service libvirt-bin restart
  libvirt-bin stop/waiting
  libvirt-bin start/running, process 7031
  inaddy@tkcompute02:~$ virsh capabilities | grep apparmor | echo $?
  0
  
  inaddy@tkcompute03:~$ sudo service libvirt-bin restart
  libvirt-bin stop/waiting
  libvirt-bin start/running, process 7031
  inaddy@tkcompute03:~$ virsh capabilities | grep apparmor | echo $?
  0
  
  BUG #2 (after fixing BUG #1)
  
  And, when libvirt starts using apparmor, and creating apparmor profiles
  for every virtual machine created in the compute nodes, mitaka qemu
  (2.5) uses a fallback mechanism for creating shared memory for live-
  migrations. This fall back mechanism, on kernels 3.13 - that don't have
  memfd_create() system-call, try to create files on /tmp/ directory and
  fails.. causing live-migration not to work.
  
  Trusty with kernel 3.13 + Mitaka with qemu 2.5 + apparmor capability =
  can't live migrate.
  
  From qemu 2.5, logic is on :
  
  void *qemu_memfd_alloc(const char *name, size_t size, unsigned int seals, int 
*fd)
  {
  if (memfd_create)... ### only works with HWE kernels
  
  else ### 3.13 kernels, gets blocked by apparmor
     tmpdir = g_get_tmp_dir
     ...
     mfd = mkstemp(fname)
  }
  
  And you can see the errors:
  
  From the host trying to send the virtual machine:
  
  2016-08-15 16:36:26.160 1974 ERROR nova.virt.libvirt.driver 
[req-0cac612b-8d53-4610-b773-d07ad6bacb91 691a581cfa7046278380ce82b1c38ddd 
133ebc3585c041aebaead8c062cd6511 - - -] [instance: 
2afa1131-bc8c-43d2-9c4a-962c1bf7723e] Migration operation has aborted
  2016-08-15 16:36:26.248 1974 ERROR nova.virt.libvirt.driver 
[req-0cac612b-8d53-4610-b773-d07ad6bacb91 691a581cfa7046278380ce82b1c38ddd 
133ebc3585c041aebaead8c062cd6511 - - -] [instance: 
2afa1131-bc8c-43d2-9c4a-962c1bf7723e] Live Migration failure: internal error: 
unable to execute QEMU command 'migrate': Migration disabled: failed to 
allocate shared memory
  
  From the host trying to receive the virtual machine:
  
  Aug 15 16:36:19 tkcompute01 kernel: [ 1194.356794] type=1400 
audit(1471289779.791:72): apparmor="STATUS" operation="profile_load" 
profile="unconfined" name="libvirt-2afa1131-bc8c-43d2-9c4a-962c1bf7723e" 
pid=12565 comm="apparmor_parser"
  Aug 15 16:36:19 tkcompute01 kernel: [ 1194.357048] type=1400 
audit(1471289779.791:73): apparmor="STATUS" operation="profile_load" 
profile="unconfined" name="qemu_bridge_helper" pid=12565 comm="apparmor_parser"
  Aug 15 16:36:20 tkcompute01 kernel: [ 1194.877027] type=1400 
audit(1471289780.311:74): apparmor="STATUS" operation="profile_replace" 
profile="unconfined" name="libvirt-2afa1131-bc8c-43d2-9c4a-962c1bf7723e" 
pid=12613 comm="apparmor_parser"
  Aug 15 16:36:20 

[Bug 1533724] Re: [SRU] keystone-signing folders fill /tmp and seriously slow down reboots

[Jeremy Stanley]

** 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 notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1533724/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1855080] Re: Credentials API allows listing and retrieving of all users credentials

[Jeremy Stanley]

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 this so we can proceed with
the advisory, since the fix has already merged to master and it looks
like stable backports are in the process of getting proposed.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855080

Title:
  Credentials API allows listing and retrieving of all users credentials

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1855080/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1855080] Re: Credentials API allows listing and retrieving of all users' credentials

[Jeremy Stanley]

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 language is why I suggested dodging "users'" or "user's" and
picking different, less ambiguous phrasing so as to avoid confusion for
non-native readers of English when skimming the advisory title.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855080

Title:
  Credentials API allows listing and retrieving of all users'
  credentials

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1855080/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1855080] Re: Credentials API allows listing and retrieving of all user's credentials

[Jeremy Stanley]

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, for all
users in that project. Instead maybe try "Credentials API allows listing
and retrieving of project credentials" or something like that? As for
the affects line, assuming this problem was only introduced in Stein,
you want "==15.0.0, ==16.0.0" (wow, were there really no stable/stein
point releases?!?) or alternatively ">=15.0.0 <15.0.1, >=16.0.0 <16.0.1"
to accurately reflect that any point releases will contain the fix.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855080

Title:
  Credentials API allows listing and retrieving of all user's
  credentials

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1855080/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1855080] Re: Credentials API allows listing and retrieving of all user's credentials

[Jeremy Stanley]

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:

- 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 official OpenStack
- Security Advisory. This includes discussion of the bug or associated
- fixes in public forums such as mailing lists, code review systems and
- bug trackers. Please also avoid private disclosure to other individuals
- not already approved for access to this information, and provide this
- same reminder to those who are made aware of the issue prior to
- publication. All discussion should remain confined to this private bug
- report, and any proposed fixes should be added to the bug as
- attachments.
- 
  Tested against Stein and Train.
  
  # User creating a credential, i.e totp or similar
  $ OS_CLOUD=1 openstack token issue
  | project_id | c3caf1b55bb84b78a795fd81838e5160
  | user_id| 9971b0f13d2d4a578212d028a53c3209
  $ OS_CLOUD=1 openstack credential create --type test 
9971b0f13d2d4a578212d028a53c3209 test-data
  $ OS_CLOUD=1 openstack credential list
  
+--+--+--+---++
  | ID   | Type | User ID  
| Data  | Project ID |
  
+--+--+--+---++
  | 0a3a2d3b7dad4886b0bbf61b6cd7d2b0 | test | 9971b0f13d2d4a578212d028a53c3209 
| test-data | None   |
  
+--+--+--+---++
  
  # Different User but same Project
  $ OS_CLOUD=2 openstack token issue
  | project_id | c3caf1b55bb84b78a795fd81838e5160
  | user_id| 6b28a0b073fc4ac7843f33190ebc5c3c
  $ OS_CLOUD=2 openstack credential list
  
+--+--+--+---++
  | ID   | Type | User ID  
| Data  | Project ID |
  
+--+--+--+---++
  | 0a3a2d3b7dad4886b0bbf61b6cd7d2b0 | test | 9971b0f13d2d4a578212d028a53c3209 
| test-data | None   |
  
+--+--+--+---++
  
  # Different User and Different Project
  $ OS_CLOUD=3 openstack token issue
  | project_id | d43f20ae5a7e4f36b701710277384401
  | user_id| 2e48f1a7d1474391a826a2b9700e5949
  $ OS_CLOUD=3 openstack credential list
  
+--+--+--+---++
  | ID   | Type | User ID  
| Data  | Project ID |
  
+--+--+--+---++
  | 0a3a2d3b7dad4886b0bbf61b6cd7d2b0 | test | 9971b0f13d2d4a578212d028a53c3209 
| test-data | None   |
  
+--+--+--+---++
  
  As shown anyone who's authenticated can retrieve any credentials
  including their 'secret'.
  
  This is a rather severe information disclosure vulnerability and
  completely defies the purpose of TOTP or MFA as these credentials are
  not kept secure or private whatsoever.
  
  If Auth-rules are configured allow login with only 'topt' it would be
  extremely easy to assume a different user's identity.
  
  A CVE should be issued for this. I can take care of that paperwork.
  
  Versions affected and tested:
  
  Train/ubuntu:
  $ dpkg -l | grep keystone
  ii  keystone 2:16.0.0-0ubuntu1~cloud0 
   all  OpenStack identity service - Daemons
  ii  keystone-common  2:16.0.0-0ubuntu1~cloud0 
   all  OpenStack identity service - Common files
  ii  python-keystoneauth1 3.13.1-0ubuntu1~cloud0   
   all  authentication library for OpenStack 
Identity - Python 2.7
  ii  python-keystoneclient1:3.19.0-0ubuntu1~cloud0 
   all  client library for the OpenStack Keystone 
API - Python 2.x
  ii  python-keystonemiddleware6.0.0-0ubuntu1~cloud0
   all  Middleware for OpenStack Identity 
(Keystone) - Python 2.x
  ii  python3-keystone 2:16.0.0-0ubuntu1~cloud0 
   

[Bug 1850718] [NEW] package virtualbox-dkms 6.0.14-dfsg-1 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess returned error exit status 10

[Stanley Park]

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
Date: Wed Oct 30 21:51:58 2019
ErrorMessage: installed virtualbox-dkms package post-installation script 
subprocess returned error exit status 10
InstallationDate: Installed on 2019-07-27 (95 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
PackageArchitecture: all
Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.4
SourcePackage: virtualbox
Title: package virtualbox-dkms 6.0.14-dfsg-1 failed to install/upgrade: 
installed virtualbox-dkms package post-installation script subprocess returned 
error exit status 10
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: virtualbox (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package eoan

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1850718

Title:
  package virtualbox-dkms 6.0.14-dfsg-1 failed to install/upgrade:
  installed virtualbox-dkms package post-installation script subprocess
  returned error exit status 10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1850718/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818239] Re: scheduler: build failure high negative weighting

[Jeremy Stanley]

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 is warranted for this.

** Information type changed from Public Security to Public

** Also affects: ossa
   Importance: Undecided
   Status: New

** Changed in: ossa
   Status: New => Won't Fix

** Tags added: security

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818239

Title:
  scheduler: build failure high negative weighting

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-nova-cloud-controller/+bug/1818239/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1714302]

[Stanley-king]

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, buggy

To manage notifications about this bug go to:
https://bugs.launchpad.net/xfce4-settings/+bug/1714302/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1466150] Re: grub-install breaks when ESP is on raid

[Ben Stanley]

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 underneath
> looking like it has a simple (non-RAID) filesystem on each disc of a
> mirror when the EFI or BIOS looks at the drives. I think that's what
> they need to boot from, so I don't think there's any chance of booting
> from a /boot/efi which is an lv in a vg on several pvs. Maybe LinuxBIOS?
>
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1466150
>
>
> Title:
>  grub-install breaks when ESP is on raid
>
>
> Status in grub-installer package in Ubuntu:
>  Triaged
>
>
> Bug description:
>  I run a server with mirrored (RAID1) disks using grub-efi.
>
>
>  Root and /boot and /boot/grub are on mirrored partitions.
>
>
>  I have EFI partitions on both disks but it is not possible to RAID1
>  these as they are FAT32.  On an EFI system grub-install will only
>  install to one of the EFI partitions and so after running install-grub
>  you have to remember to copy the EFI file across.
>
>
>  Could grub configuration and grub-install be amended to automatically
>  install to multiple disks?
>
>
>  Searching around there seem to be many people asking this question
>  without any elegant solution.
>
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1466150/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466150

Title:
  grub-install breaks when ESP is on raid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1466150/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1466150] Re: grub-install breaks when ESP is on raid

[Ben Stanley]

> 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 with mdadm, header is 
placed at the end of the partition instead. This allows the boot loader to 
function as normal while the partition is RAID1. Just don't expect Windows 
to respect the RAID1.


However even using this trick my system won't grub-install to a RAID1 
partition. Reports problems with EFI.

Sorry I'm not next to my system as I write this so details are from memory 
instead of tested on the system.

On 1 July 2019 7:59:39 am Jack Ostroff 
wrote:

> I'm having the same problem with a new Gentoo install, but with a twist.
> I am using lvm2 with a vg of two whole disk pvs and raid1 lvs for /,
> /boot, and /boot/efi.  Since I'm not using mdadm, the script in comment
> #18 doesn't work for me, and I'm not able to modify it for my case,
> although I try a bit more.
>
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1466150
>
>
> Title:
>  grub-install breaks when ESP is on raid
>
>
> Status in grub-installer package in Ubuntu:
>  Triaged
>
>
> Bug description:
>  I run a server with mirrored (RAID1) disks using grub-efi.
>
>
>  Root and /boot and /boot/grub are on mirrored partitions.
>
>
>  I have EFI partitions on both disks but it is not possible to RAID1
>  these as they are FAT32.  On an EFI system grub-install will only
>  install to one of the EFI partitions and so after running install-grub
>  you have to remember to copy the EFI file across.
>
>
>  Could grub configuration and grub-install be amended to automatically
>  install to multiple disks?
>
>
>  Searching around there seem to be many people asking this question
>  without any elegant solution.
>
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1466150/+subscriptions

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1466150

Title:
  grub-install breaks when ESP is on raid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1466150/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1813007] Re: [SRU] Unable to install new flows on compute nodes when having broken security group rules (CVE-2019-10876)

[Jeremy Stanley]

** 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 rules (CVE-2019-10876)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813007

Title:
  [SRU] [OSSA-2019-002] Unable to install new flows on compute nodes
  when having broken security group rules (CVE-2019-10876)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1813007/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1813007] Re: [SRU] Unable to install new flows on compute nodes when having broken security group rules

[Jeremy Stanley]

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.
https://bugs.launchpad.net/bugs/1813007

Title:
  [SRU] Unable to install new flows on compute nodes when having broken
  security group rules

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1813007/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1813007] Re: [SRU] Unable to install new flows on compute nodes when having broken security group rules

[Jeremy Stanley]

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: ossa
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813007

Title:
  [SRU] Unable to install new flows on compute nodes when having broken
  security group rules

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1813007/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1813007] Re: [SRU] Unable to install new flows on compute nodes when having broken security group rules

[Jeremy Stanley]

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 solution is acceptably backportable.
I'll draft an impact description in a forthcoming bug comment to solicit
further feedback.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813007

Title:
  [SRU] Unable to install new flows on compute nodes when having broken
  security group rules

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1813007/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1813007] Re: [SRU] Unable to install new flows on compute nodes when having broken security group rules

[Jeremy Stanley]

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 because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813007

Title:
  [SRU] Unable to install new flows on compute nodes when having broken
  security group rules

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1813007/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1813007] Re: [SRU] Unable to install new flows on compute nodes when having broken security group rules

[Jeremy Stanley]

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 scenario so we can draft
an appropriate impact description?

** Tags added: pike-backport-potential queens-backport-potential rocky-
backport-potential

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813007

Title:
  [SRU] Unable to install new flows on compute nodes when having broken
  security group rules

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1813007/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818239] Re: scheduler: build failure high negative weighting

[Jeremy Stanley]

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 formulate an appropriate impact description
for a possible security vulnerability advisory publication.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818239

Title:
  scheduler: build failure high negative weighting

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-nova-cloud-controller/+bug/1818239/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818239] Re: scheduler: build failure high negative weighting

[Jeremy Stanley]

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 member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818239

Title:
  scheduler: build failure high negative weighting

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-nova-cloud-controller/+bug/1818239/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1818239] Re: scheduler: build failure high negative weighting

[Jeremy Stanley]

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 hosts through which their build failures rotated?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818239

Title:
  scheduler: build failure high negative weighting

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-nova-cloud-controller/+bug/1818239/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1811098] Re: [SRU] ceilometer writing snmp credentials to log file

[Jeremy Stanley]

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
/vmt-process.html#send-cve-request if you're interested in following a
similar process. Note that for an already-public report like this one,
there are fewer bits to worry about (the process documentation attempts
to call out the difference between what you'd do for still private
embargoed reports vs already public reports).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811098

Title:
  [SRU] ceilometer writing snmp credentials to log file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ceilometer/+bug/1811098/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1529715] Re: ASUSTek Computer, Inc. AC51 Wireless Adapter [Mediatek MT7610/Ralink RT2870] doesn't work on ubuntu 14.04 LTS &15.10 with kernel 3.19&4.2 & 4.4

[Chen-Han Hsiao (Stanley)]

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:
 linux-image-unsigned-4.19.0-041900-generic_4.19.0-041900.201810221809_amd64.deb
 linux-modules-4.19.0-041900-generic_4.19.0-041900.201810221809_amd64.deb


 from https://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19/ )

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1529715

Title:
  ASUSTek Computer, Inc. AC51 Wireless Adapter [Mediatek MT7610/Ralink
  RT2870]  doesn't work on ubuntu 14.04 LTS &15.10 with kernel 3.19&4.2
  & 4.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1529715/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 66566]

[Stanley Chan]

(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 to canonize to the local tld (for example .it for italian). I'd
> totally support ctrl+shift to complete to the localized tld rather than .org
> (though this would require localization support).
> Second, I'd like if ctrl would be the necessary key to activate canonization
> in general, so all the shortcuts should required ctrl to be pressed. Shift
> is far too common when typing and as I said it's already used by
> tab/tabshifted, it's just confusing.
> I understand changing this we could break muscle memory of a minority, but
> it's for a totally undiscoverable feature on less critical tlds than .com.
> and we're changing cmd on Mac already, for which we'll want a relnote.
> I'd honestly propose to drop the shift and ctrl+shift behaviors completely.

Color me surprised when I updated to Nightly 64.0 and found out that the
keyboard shortcuts that I've relied on Firefox having for the past 15
years apparently requires some rewiring of muscle memory. This change
does make sense and does indeed make it more consistent all around --
but will definitely catch A LOT of long-time macOS Firefox users off-
guard if not announced gracefully. This goes the same for keybord-
shortcut aficionados/ power users.

It will also require documentation updates (i.e.
https://support.mozilla.org/en-US/kb/keyboard-shortcuts-perform-firefox-
tasks-quickly#w_miscellaneous_2 and https://blog.mozilla.org/firefox
/keyboard-shortcuts-command-qwerty/) since this is literally 15 year old
behavior that is changing. It's also been blogged about over the years
throughout various websites that cater to the power user (such as
LifeHacker and How-To-Geek), but that's nothing that Mozilla controls.

That being said, can we get about:config options to configure the Ctrl-
Shift and Shift-Enter shortcuts in the address bar? When this feature
was first added, .com, .net. and .org were the most popular of TLD
suffixes. Today, I can see how that is different, and I will admit that
I do not complete .net and .org domains as often. I agree that not many
people used it, but perhaps it can be more accessible if a user can
configure those prefixes and suffixes directly.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/66566

Title:
  Inconsistent shortcuts for new tab

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/66566/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1740106] Re: Gnome terminal not starting, timeout reached (bionic)

[Chen-Han Hsiao (Stanley)]

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 member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740106

Title:
  Gnome terminal not starting, timeout reached (bionic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1740106/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1740106] Re: Gnome terminal not starting, timeout reached (bionic)

[Chen-Han Hsiao (Stanley)]

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 3.28.2-1ubuntu1~18.04.1
Uname: Linux 4.15.0-34-generic x86_64

chrome-remote-desktop  69.0.3497.7

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1740106

Title:
  Gnome terminal not starting, timeout reached (bionic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1740106/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1569970] Re: Nautilus does not start on 16.04

[Stanley]

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
Codename:   xenial

apt policy nautilus
nautilus:
  Installed: 1:3.18.4.is.3.14.3-0ubuntu6
  Candidate: 1:3.18.4.is.3.14.3-0ubuntu6

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569970

Title:
  Nautilus does not start on 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1569970/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1708735] Re: lapack fails the testsuite on ppc64el when built with -O3

[Joel Stanley]

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)  (  -0.940210E+09,   0.547188E+12)
   3  (   0.966533,   0.442557)  (  -0.275106E+12,  -0.136729E+10)
   4  (0.0,0.0)  (  -0.452662E+20,  -0.498356E+20)
   5  (   0.926573,   0.106893)  (   0.197802E+20,  -0.154845E+20)
   6  (   0.956543,  -0.100899)  (   0.239256E+09,  -0.503443E+10)
   7  (   0.686813,  -0.156843)  (   0.176324E+10,   0.214785E+09)
   8  (   0.247253,  -0.292707)  (   0.247253,  -0.292707)
   9  (   0.774226E-01,   0.989011E-01)  (   0.774226E-01,   0.989011E-01)
 *** CTRSV  FAILED ON CALL NUMBER:
195: CTRSV ('U','N','U',  9, A, 10, X, 2)   
.

 CTBSV  PASSED THE TESTS OF ERROR-EXITS

 CTBSV  PASSED THE COMPUTATIONAL TESTS (   961 CALLS)

 CTPSV  PASSED THE TESTS OF ERROR-EXITS

 *** 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)  (  -0.940210E+09,   0.547188E+12)
   3  (   0.966533,   0.442557)  (  -0.275106E+12,  -0.136729E+10)
   4  (0.0,0.0)  (  -0.452662E+20,  -0.498356E+20)
   5  (   0.926573,   0.106893)  (   0.197802E+20,  -0.154845E+20)
   6  (   0.956543,  -0.100899)  (   0.239256E+09,  -0.503443E+10)
   7  (   0.686813,  -0.156843)  (   0.176324E+10,   0.214785E+09)
   8  (   0.247253,  -0.292707)  (   0.247253,  -0.292707)
   9  (   0.774226E-01,   0.989011E-01)  (   0.774226E-01,   0.989011E-01)
 *** CTPSV  FAILED ON CALL NUMBER:
195: CTPSV ('U','N','U',  9, AP, X, 2)  
.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1708735

Title:
  lapack fails the testsuite on ppc64el when built with -O3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lapack/+bug/1708735/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1784349] Re: SEGV during startup on Power 8 system

[Joel Stanley]

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: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1784349

Title:
  SEGV during startup on Power 8 system

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1784349/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1783705] Re: clang errors with __float128 is not supported on this target on ppc64le

[Joel Stanley]

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
+++ /usr/include/powerpc64le-linux-gnu/c++/8/bits/c++config.h   2018-07-28 
15:23:29.0 +0930
@@ -1550,7 +1531,7 @@ namespace std
 #define _GLIBCXX_USE_FCHMODAT 1
 
 /* Define if __float128 is supported on this host. */
-/* #undef _GLIBCXX_USE_FLOAT128 */
+#define _GLIBCXX_USE_FLOAT128 1
 
 /* Defined if gettimeofday is available. */
 #define _GLIBCXX_USE_GETTIMEOFDAY 1


$ dpkg -S /usr/include/powerpc64le-linux-gnu/c++/8/bits/c++config.h 
libstdc++-8-dev:ppc64el: 
/usr/include/powerpc64le-linux-gnu/c++/8/bits/c++config.h


$ apt-cache policy libstdc++-8-dev
libstdc++-8-dev:
  Installed: 8.2.0-1ubuntu2

Upstream gcc has this change to c++config which would fix clang:

/* Define if __float128 is supported on this host. */
#if defined(__FLOAT128__) || defined(__SIZEOF_FLOAT128__)
#define _GLIBCXX_USE_FLOAT128
#endif


https://gcc.gnu.org/viewcvs/gcc?view=revision=260043

PR libstdc++/84654 Disable __float128 specializations for -mno-float128

2018-05-01  Tulio Magno Quites Machado Filho  

PR libstdc++/84654
* acinclude.m4: Set ENABLE_FLOAT128 instead of 
_GLIBCXX_USE_FLOAT128.
* config.h.in: Remove references to _GLIBCXX_USE_FLOAT128.
* configure: Regenerate.
* include/Makefile.am: Replace the value of _GLIBCXX_USE_FLOAT128
based on ENABLE_FLOAT128.
* include/Makefile.in: Regenerate.
* include/bits/c++config: Define _GLIBCXX_USE_FLOAT128.
[!defined(__FLOAT128__) && !defined(__SIZEOF_FLOAT128__)]: Undefine
_GLIBCXX_USE_FLOAT128.


** Bug watch added: GCC Bugzilla #84654
   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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-defaults/+bug/1783705/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1783705] Re: clang errors with __float128 is not supported on this target on ppc64le

[Joel Stanley]

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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-defaults/+bug/1783705/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1782716] Re: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout

[Joel Stanley]

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:
  [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782716/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1782716] Re: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout

[Joel Stanley]

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] [c00fec1036c0] [c0d4d6fc] dump_stack+0xb0/0xf4 
(unreliable)
[  333.596587] [c00fec103700] [c003b114] 
eeh_dev_check_failure+0x514/0x5e0
[  333.596589] [c00fec1037a0] [c003b26c] eeh_check_failure+0x8c/0xd0
[  333.596616] [c00fec1037e0] [c0080d5119f8] amdgpu_mm_rreg+0x240/0x2a0 
[amdgpu]
[  333.596649] [c00fec103840] [c0080d623250] 
amdgpu_cgs_read_register+0x28/0x50 [amdgpu]
[  333.596685] [c00fec103860] [c0080d6ce81c] 
dce110_timing_generator_get_vblank_counter+0x44/0x70 [amdgpu]
[  333.596717] [c00fec103880] [c0080d6f4430] 
dc_stream_get_vblank_counter+0x88/0xb0 [amdgpu]
[  333.596752] [c00fec1038a0] [c0080d67f5f4] 
dm_vblank_get_counter+0x4c/0xa8 [amdgpu]
[  333.596774] [c00fec103900] [c0080d518630] 
amdgpu_get_vblank_counter_kms+0xa8/0x250 [amdgpu]
[  333.596808] [c00fec1039b0] [c0080d67c1b8] 
amdgpu_dm_do_flip+0xd0/0x3b0 [amdgpu]
[  333.596844] [c00fec103b00] [c0080d6801a0] 
amdgpu_dm_atomic_commit_tail+0x7f8/0xf20 [amdgpu]
[  333.596850] [c00fec103c60] [c0080cb72da4] commit_tail+0x6c/0xe0 
[drm_kms_helper]
[  333.596853] [c00fec103c90] [c01385f0] 
process_one_work+0x2b0/0x560
[  333.596855] [c00fec103d20] [c0138928] worker_thread+0x88/0x610
[  333.596858] [c00fec103dc0] [c01415dc] kthread+0x1ac/0x1c0
[  333.596861] [c00fec103e30] [c000b65c] 
ret_from_kernel_thread+0x5c/0x80
[  333.596886] EEH: Detected error on PHB#33
[  333.596890] EEH: This PCI device has failed 1 times in the last hour and 
will be permanently disabled after 5 failures.
[  333.596891] EEH: Notify device drivers to shutdown
[  333.596895] EEH: Beginning: 'error_detected(IO frozen)'
[  333.596898] EEH: PE#1fe (PCI 0033:00:00.0): no driver
[  333.596900] EEH: PE#0 (PCI 0033:01:00.1): driver not EEH aware
[  333.596902] EEH: PE#0 (PCI 0033:01:00.0): driver not EEH aware
[  333.596904] EEH: Finished:'error_detected(IO frozen)' with aggregate 
recovery state:'none'
[  333.596908] EEH: Collect temporary log
[  333.596910] PHB4 PHB#51 Diag-data (Version: 1)
[  333.596911] brdgCtl:0002
[  333.596913] RootSts:0020 00402000 e9010008 00100107 
[  333.596915] nFir:   8000 0030001c 8000
[  333.596916] PhbSts: 0018 0018
[  333.596918] Lem:000400010100  0001
[  333.596919] PhbErr: 05a0 0080 214898000240 
a0084000
[  333.596921] PhbTxeErr:  2000 2000 4000 

[  333.596923] RxeMrgErr:  0001 0001  

[  333.596925] PblErr: 0800 0800  
028de410
[  333.596926] RegbErr:00100010 0010 483c 
0200
[  333.596929] EEH: Reset with hotplug activity
[  334.084373] iommu: Removing device 0033:01:00.1 from group 3
[  334.084445] pci 0033:01:00.1: Dropping the link to 0033:01:00.0
[  334.085057] [drm] amdgpu: finishing device.
[  343.769080] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, 
last signaled seq=590, last emitted seq=591
[  343.769186] [drm] GPU recovery disabled.
[  344.281128] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma1 timeout, 
last signaled seq=349, last emitted seq=350
[  344.281189] [drm:amdgpu_dm_atomic_check [amdgpu]] *ERROR* [CRTC:43:crtc-0] 
hw_done or flip_done timed out
[  344.281390] [drm] GPU recovery disabled.

-- 
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:
  [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782716/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1782716] Re: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout

[Joel Stanley]

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 'sforshee: 00b28ddf47aef9cea7'
[ 3060.974388] [drm] dce_get_required_clocks_state: clocks unsupported disp_clk 
681000 pix_clk 154000
[ 3510.632708] [drm] dce_get_required_clocks_state: clocks unsupported disp_clk 
681000 pix_clk 154000
[ 3527.956089] [drm] dce_get_required_clocks_state: clocks unsupported disp_clk 
681000 pix_clk 154000
[ 4992.501324] [drm] dce_get_required_clocks_state: clocks unsupported disp_clk 
681000 pix_clk 154000
[ 5015.179529] [drm] dce_get_required_clocks_state: clocks unsupported disp_clk 
681000 pix_clk 154000
[ 5189.342133] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, 
last signaled seq=4657, last emitted seq=4658
[ 5189.342233] [drm] GPU recovery disabled.
[ 5317.867388] INFO: task kworker/u257:3:54387 blocked for more than 120 
seconds.
[ 5317.867471]   Not tainted 4.18.0-041800rc6-generic #201807221830
[ 5317.867548] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[ 5317.867656] kworker/u257:3  D0 54387  2 0x0808
[ 5317.867675] Workqueue: events_unbound commit_work [drm_kms_helper]
[ 5317.867677] Call Trace:
[ 5317.867680] [c00fe3447460] [002a] 0x2a (unreliable)
[ 5317.867688] [c00fe3447630] [c001c430] __switch_to+0x260/0x4c0
[ 5317.867694] [c00fe3447690] [c0d67b44] __schedule+0x304/0xad0
[ 5317.867697] [c00fe3447760] [c0d68358] schedule+0x48/0xc0
[ 5317.867701] [c00fe3447780] [c0d6d1b8] 
schedule_timeout+0x348/0x510
[ 5317.867707] [c00fe3447880] [c0928b60] 
dma_fence_default_wait+0x2b0/0x350
[ 5317.867710] [c00fe34478f0] [c092780c] 
dma_fence_wait_timeout+0x6c/0x1b0
[ 5317.867714] [c00fe3447930] [c092aeb0] 
reservation_object_wait_timeout_rcu+0x320/0x3d0
[ 5317.867774] [c00fe34479b0] [c0080d5fc220] 
amdgpu_dm_do_flip+0x138/0x3b0 [amdgpu]
[ 5317.867831] [c00fe3447b00] [c0080d6001a0] 
amdgpu_dm_atomic_commit_tail+0x7f8/0xf20 [amdgpu]
[ 5317.867840] [c00fe3447c60] [c0080cb72da4] commit_tail+0x6c/0xe0 
[drm_kms_helper]
[ 5317.867846] [c00fe3447c90] [c0138720] 
process_one_work+0x2b0/0x560
[ 5317.867850] [c00fe3447d20] [c0138a58] worker_thread+0x88/0x610
[ 5317.867854] [c00fe3447dc0] [c01416fc] kthread+0x1ac/0x1c0
[ 5317.867859] [c00fe3447e30] [c000b65c] 
ret_from_kernel_thread+0x5c/0x80
[ 5438.711397] INFO: task kworker/u257:3:54387 blocked for more than 120 
seconds.
[ 5438.711473]   Not tainted 4.18.0-041800rc6-generic #201807221830
[ 5438.711552] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.

If I kill the wayland session:

[ 7012.419912] EEH: Frozen PHB#33-PE#0 detected
[ 7012.419919] EEH: PE location: CPU2 Slot1 (16x), PHB location: N/A
[ 7012.419923] CPU: 74 PID: 126541 Comm: pulseaudio Not tainted 
4.18.0-041800rc6-generic #201807221830
[ 7012.419924] Call Trace:
[ 7012.419932] [c000200b3600] [c0d4ce3c] dump_stack+0xb0/0xf4 
(unreliable)
[ 7012.419936] [c000200b3640] [c003b0ac] 
eeh_dev_check_failure+0x4ac/0x5e0
[ 7012.419938] [c000200b36e0] [c003b26c] eeh_check_failure+0x8c/0xd0
[ 7012.419945] [c000200b36333420] [c00816342ae8] pci_azx_readw+0x80/0xb0 
[snd_hda_intel]
[ 7012.419950] [c000200b36333450] [c008161c5790] 
snd_hdac_bus_send_cmd+0x78/0x210 [snd_hda_core]
[ 7012.419956] [c000200b363334a0] [c008162a20ec] azx_send_cmd+0x34/0x390 
[snd_hda_codec]
[ 7012.419959] [c000200b36333530] [c008161c0274] 
snd_hdac_bus_exec_verb_unlocked+0x7c/0x280 [snd_hda_core]
[ 7012.419964] [c000200b36333590] [c0081629240c] codec_exec_verb+0xb4/0x1f0 
[snd_hda_codec]
[ 7012.419967] [c000200b36333630] [c008161c1a10] 
snd_hdac_exec_verb+0x38/0x90 [snd_hda_core]
[ 7012.419971] [c000200b36333650] [c008161c4158] hda_reg_write+0x120/0x3b0 
[snd_hda_core]
[ 7012.419974] [c000200b363336c0] [c08c87e8] _regmap_write+0x98/0x190
[ 7012.419977] [c000200b36333710] [c08ca5b4] regmap_write+0x74/0xc0
[ 7012.419981] [c000200b36333750] [c008161c47e4] 
snd_hdac_regmap_write_raw+0x4c/0x130 [snd_hda_core]
[ 7012.419985] [c000200b36333790] [c00816485d80] hdmi_pcm_open+0x168/0x4a0 
[snd_hda_codec_hdmi]
[ 7012.419989] [c000200b36333820] [c008162a12e8] azx_pcm_open+0x1b0/0x3d0 
[snd_hda_codec]
[ 7012.419995] [c000200b36333890] [c008160ab3dc] 
snd_pcm_open_substream+0xb4/0x1a0 [snd_pcm]
[ 7012.419998] [c000200b36333920] [c008160ab5d4] snd_pcm_open+0x10c/0x2e0 
[snd_pcm]
[ 7012.420002] [c000200b363339b0] [c008160ab8c4] 
snd_pcm_playback_open+0x6c/0xa8 [snd_pcm]
[ 7012.420008] [c000200b363339f0] [c0080f9c0750] snd_open+0x108/0x240 [snd]
[ 7012.420011] 

[Bug 1783705] [NEW] clang errors with __float128 is not supported on this target on ppc64le

[Joel Stanley]

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 
/usr/bin/../lib/gcc/powerpc64le-linux-gnu/8/../../../../include/c++/8/cmath:47:
/usr/bin/../lib/gcc/powerpc64le-linux-gnu/8/../../../../include/c++/8/bits/std_abs.h:102:7:
 error: 
  __float128 is not supported on this target
  abs(__float128 __x)
  ^
/usr/bin/../lib/gcc/powerpc64le-linux-gnu/8/../../../../include/c++/8/bits/std_abs.h:101:3:
 error: 
  __float128 is not supported on this target
  __float128
  ^
2 errors generated.

GCC works fine. If I add -mfloat128, it fails with this error:

$ clang++ -mfloat128 foo.cpp 
In file included from foo.cpp:1:
In file included from 
/usr/bin/../lib/gcc/powerpc64le-linux-gnu/8/../../../../include/c++/8/cmath:45:
In file included from /usr/include/math.h:43:
/usr/include/powerpc64le-linux-gnu/bits/floatn.h:72:52: error: unknown machine 
mode '__KC__'
typedef _Complex float __cfloat128 __attribute__ ((__mode__ (__KC__)));
   ^

$ clang++ --version
clang version 6.0.1-2ubuntu1 (tags/RELEASE_601/final)
Target: powerpc64le-unknown-linux-gnu


libc6: 2.27-3ubuntu1
clang: 6.0-41ubuntu1
gcc: 4:8.1.0-2ubuntu1

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: clang 1:6.0-41ubuntu1
Uname: Linux 4.18.0-041800rc6-generic ppc64le
ApportVersion: 2.20.10-0ubuntu5
Architecture: ppc64el
Date: Thu Jul 26 16:27:16 2018
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcLoadAvg: 0.15 1.70 2.08 1/1654 18418
ProcLocks:
 1: FLOCK  ADVISORY  WRITE 4151 00:32:46558 0 EOF
 2: FLOCK  ADVISORY  WRITE 3971 00:1a:62741 0 EOF
 3: FLOCK  ADVISORY  WRITE 3418 00:32:85157 0 EOF
 4: FLOCK  ADVISORY  WRITE 3104 00:17:44175 0 EOF
 5: POSIX  ADVISORY  WRITE 3109 00:17:39081 0 EOF
ProcSwaps:
 Filename   TypeSizeUsedPriority
 /swapfile   file   2097088 0   -2
ProcVersion: Linux version 4.18.0-041800rc6-generic (kernel@tangerine) (gcc 
version 8.1.0 (Ubuntu 8.1.0-11ubuntu1)) #201807221830 SMP Sun Jul 22 23:58:55 
UTC 2018
SourcePackage: llvm-defaults
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDump_list: total 0
cpu_cores: Number of cores present = 32
cpu_coreson: Number of cores online = 32
cpu_smt: SMT=4

** Affects: llvm-defaults (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug cosmic ppc64el

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-defaults/+bug/1783705/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1782716] Re: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout

[Joel Stanley]

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] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[ 2538.368053] kworker/u257:2  D0  8785  2 0x0800
[ 2538.368067] Workqueue: events_unbound commit_work [drm_kms_helper]
[ 2538.368069] Call Trace:
[ 2538.368072] [c00fcfb33460] [0014] 0x14 (unreliable)
[ 2538.368078] [c00fcfb33630] [c001cd3c] __switch_to+0x2ec/0x4c0
[ 2538.368081] [c00fcfb33690] [c0d42550] __schedule+0x330/0xa90
[ 2538.368083] [c00fcfb33760] [c0d42cf0] schedule+0x40/0xc0
[ 2538.368086] [c00fcfb33780] [c0d47b88] 
schedule_timeout+0x258/0x4f0
[ 2538.368090] [c00fcfb33880] [c0923b90] 
dma_fence_default_wait+0x2b0/0x370
[ 2538.368093] [c00fcfb338f0] [c0922f64] 
dma_fence_wait_timeout+0x74/0x190
[ 2538.368096] [c00fcfb33930] [c0925fc0] 
reservation_object_wait_timeout_rcu+0x2f0/0x3e0
[ 2538.368141] [c00fcfb339b0] [c0080d10d108] 
amdgpu_dm_do_flip+0x130/0x3b0 [amdgpu]
[ 2538.368184] [c00fcfb33b00] [c0080d1113c8] 
amdgpu_dm_atomic_commit_tail+0xcb0/0xf90 [amdgpu]
[ 2538.368191] [c00fcfb33c60] [c0080c762b94] commit_tail+0x6c/0xe0 
[drm_kms_helper]
[ 2538.368194] [c00fcfb33c90] [c0137928] 
process_one_work+0x298/0x580
[ 2538.368197] [c00fcfb33d20] [c0137c98] worker_thread+0x88/0x610
[ 2538.368200] [c00fcfb33dc0] [c0140958] kthread+0x1a8/0x1b0
[ 2538.368203] [c00fcfb33e30] [c000b658] 
ret_from_kernel_thread+0x5c/0x84
[ 2659.214902] INFO: task kworker/u257:2:8785 blocked for more than 120 seconds.
[ 2659.214976]   Not tainted 4.17.0-5-generic #6-Ubuntu
[ 2659.215019] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this 
message.
[ 2659.215126] kworker/u257:2  D0  8785  2 0x0800
[ 2659.215141] Workqueue: events_unbound commit_work [drm_kms_helper]
[ 2659.215142] Call Trace:
[ 2659.215145] [c00fcfb33460] [0014] 0x14 (unreliable)
[ 2659.215151] [c00fcfb33630] [c001cd3c] __switch_to+0x2ec/0x4c0
[ 2659.215154] [c00fcfb33690] [c0d42550] __schedule+0x330/0xa90
[ 2659.215157] [c00fcfb33760] [c0d42cf0] schedule+0x40/0xc0
[ 2659.215160] [c00fcfb33780] [c0d47b88] 
schedule_timeout+0x258/0x4f0
[ 2659.215163] [c00fcfb33880] [c0923b90] 
dma_fence_default_wait+0x2b0/0x370
[ 2659.215166] [c00fcfb338f0] [c0922f64] 
dma_fence_wait_timeout+0x74/0x190
[ 2659.215169] [c00fcfb33930] [c0925fc0] 
reservation_object_wait_timeout_rcu+0x2f0/0x3e0
[ 2659.215217] [c00fcfb339b0] [c0080d10d108] 
amdgpu_dm_do_flip+0x130/0x3b0 [amdgpu]
[ 2659.215264] [c00fcfb33b00] [c0080d1113c8] 
amdgpu_dm_atomic_commit_tail+0xcb0/0xf90 [amdgpu]
[ 2659.215272] [c00fcfb33c60] [c0080c762b94] commit_tail+0x6c/0xe0 
[drm_kms_helper]
[ 2659.215275] [c00fcfb33c90] [c0137928] 
process_one_work+0x298/0x580
[ 2659.215278] [c00fcfb33d20] [c0137c98] worker_thread+0x88/0x610
[ 2659.215281] [c00fcfb33dc0] [c0140958] kthread+0x1a8/0x1b0
[ 2659.215284] [c00fcfb33e30] [c000b658] 
ret_from_kernel_thread+0x5c/0x84

-- 
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:
  [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782716/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1782716] [NEW] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout

[Joel Stanley]

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 gfx timeout, 
last signaled seq=8777, last emitted seq=8778
[ 2362.080397] EEH: Frozen PHB#33-PE#0 detected
[ 2362.080470] EEH: PE location: CPU2 Slot1 (16x), PHB location: N/A
[ 2362.080568] CPU: 53 PID: 874 Comm: kworker/53:1 Not tainted 4.17.0-5-generic 
#6-Ubuntu
[ 2362.080575] Workqueue: events drm_sched_job_timedout [gpu_sched]
[ 2362.080577] Call Trace:
[ 2362.080584] [c000fb7078f0] [c0d275ac] dump_stack+0xb0/0xf4 
(unreliable)
[ 2362.080590] [c000fb707930] [c003ba0c] 
eeh_dev_check_failure+0x5bc/0x5e0
[ 2362.080593] [c000fb7079e0] [c003babc] eeh_check_failure+0x8c/0xd0
[ 2362.080628] [c000fb707a20] [c0080cfa1b88] amdgpu_mm_rreg+0x280/0x2a0 
[amdgpu]
[ 2362.080676] [c000fb707a70] [c0080d04cf68] 
gmc_v8_0_check_soft_reset+0x30/0xe0 [amdgpu]
[ 2362.080711] [c000fb707aa0] [c0080cfa1194] 
amdgpu_device_ip_check_soft_reset.part.1+0x8c/0x140 [amdgpu]
[ 2362.080745] [c000fb707b30] [c0080cfa649c] 
amdgpu_device_gpu_recover+0x854/0xa40 [amdgpu]
[ 2362.080799] [c000fb707c00] [c0080d0b97a4] 
amdgpu_job_timedout+0x5c/0x80 [amdgpu]
[ 2362.080805] [c000fb707c70] [c0080c8f0040] 
drm_sched_job_timedout+0x38/0x60 [gpu_sched]
[ 2362.080810] [c000fb707c90] [c0137928] 
process_one_work+0x298/0x580
[ 2362.080813] [c000fb707d20] [c0137c98] worker_thread+0x88/0x610
[ 2362.080817] [c000fb707dc0] [c0140958] kthread+0x1a8/0x1b0
[ 2362.080822] [c000fb707e30] [c000b658] 
ret_from_kernel_thread+0x5c/0x84
[ 2362.080827] [drm] IP block:gmc_v8_0 is hung!
[ 2362.080832] [drm] IP block:tonga_ih is hung!
[ 2362.080843] [drm] IP block:gfx_v8_0 is hung!
[ 2362.080845] EEH: Detected PCI bus error on PHB#33-PE#0
[ 2362.080847] EEH: This PCI device has failed 1 times in the last hour
[ 2362.080849] EEH: Notify device drivers to shutdown
[ 2362.080850] [drm] IP block:sdma_v3_0 is hung!
[ 2362.080856] [drm] IP block:uvd_v6_0 is hung!
[ 2362.080858] EEH: Collect temporary log
[ 2362.080866] [drm] IP block:vce_v3_0 is hung!
[ 2362.080867] [drm] GPU recovery disabled.
[ 2362.080903] EEH: of node=0033:01:00.1
[ 2362.080905] EEH: PCI device/vendor: 
[ 2362.080907] EEH: PCI cmd/status register: 
[ 2362.080908] EEH: PCI-E capabilities and status follow:
[ 2362.080915] EEH: PCI-E 00:     
[ 2362.080920] EEH: PCI-E 10:     
[ 2362.080921] EEH: PCI-E 20:  
[ 2362.080922] EEH: PCI-E AER capability register set follows:
[ 2362.080928] EEH: PCI-E AER 00:     
[ 2362.080933] EEH: PCI-E AER 10:     
[ 2362.080938] EEH: PCI-E AER 20:     
[ 2362.080940] EEH: PCI-E AER 30:   
[ 2362.080941] EEH: of node=0033:01:00.0
[ 2362.080943] EEH: PCI device/vendor: 
[ 2362.080945] EEH: PCI cmd/status register: 
[ 2362.080945] EEH: PCI-E capabilities and status follow:
[ 2362.080951] EEH: PCI-E 00:     
[ 2362.080956] EEH: PCI-E 10:     
[ 2362.080957] EEH: PCI-E 20:  
[ 2362.080958] EEH: PCI-E AER capability register set follows:
[ 2362.080964] EEH: PCI-E AER 00:     
[ 2362.080969] EEH: PCI-E AER 10:     
[ 2362.080974] EEH: PCI-E AER 20:     
[ 2362.080975] EEH: PCI-E AER 30:   
[ 2362.080977] PHB4 PHB#51 Diag-data (Version: 1)
[ 2362.080978] brdgCtl:0002
[ 2362.080979] RootSts:00060020 00402000 c1010008 00100107 
[ 2362.080980] RootErrSts:  0020 
[ 2362.080981] PhbSts: 001c 001c
[ 2362.080982] Lem:0001  0001
[ 2362.080983] PhbErr: 00c0 0080 214898000240 
a0084000
[ 2362.080984] RegbErr:0090 0010 483c 
0200
[ 2362.080985] PE[000] A/B: 8000 8000
[ 2362.080987] PE[..1fe] A/B: as above
[ 2362.080988] PE[1ff] A/B: b740002a0100 8000
[ 2362.080988] EEH: Reset with hotplug activity
[ 2362.579139] iommu: Removing device 0033:01:00.1 from group 3
[ 2362.579206] pci 0033:01:00.1: Dropping the link to 0033:01:00.0
[ 2362.579665] [drm] amdgpu: finishing device.
[ 2363.495059] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring sdma1 timeout, 
last signaled seq=8052, last emitted seq=8054
[ 2363.495192] [drm] IP block:gmc_v8_0 is hung!
[ 2363.495197] [drm] IP block:tonga_ih is hung!
[ 2363.495208] [drm] IP block:gfx_v8_0 is 

[Bug 1772844] Re: snapd didn't initialize all the seeded snaps

[Chen-Han Hsiao (Stanley)]

** 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 notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772844/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772374] Re: ubiquity need mount point /sys/firmware/efi/efivars

[Chen-Han Hsiao (Stanley)]

** 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 notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772374/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1746992] Re: gnocchi-api in Bionic uses python3, and libapache2-mod-wsgi-py3 conflicts with the python 2 version

[Jeremy Stanley]

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 Python 2.7. If I were to guess, Gnocchi isn't included
due to it not officially being part of OpenStack any longer (the
developers decided to move out of OpenStack and form their own community
around Gnocchi in March of 2017).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746992

Title:
  gnocchi-api in Bionic uses python3, and libapache2-mod-wsgi-py3
  conflicts with the python 2 version

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnocchi/+bug/1746992/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50093] Re: Some sysctls are ignored on boot

[Stanley Sisneros]

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772844] Re: snapd didn't initialize all the seeded snaps

[Chen-Han Hsiao (Stanley)]

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: Undecided
   Status: New

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772844/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772844] Re: snapd didn't initialize all the seeded snaps

[Chen-Han Hsiao (Stanley)]

** 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:
  snapd didn't initialize all the seeded snaps

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772844/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772844] Re: snapd didn't initialize all the seeded snaps

[Chen-Han Hsiao (Stanley)]

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 initialize all the seeded snaps

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772844/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772844] Re: snapd didn't initialize all the seeded snaps

[Chen-Han Hsiao (Stanley)]

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.
https://bugs.launchpad.net/bugs/1772844

Title:
  snapd didn't initialize all the seeded snaps

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772844/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772844] Re: snapd didn't initialize all the seeded snaps

[Chen-Han Hsiao (Stanley)]

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 Ubuntu.
https://bugs.launchpad.net/bugs/1772844

Title:
  snapd didn't initialize all the seeded snaps

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772844/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772844] [NEW] snapd didn't initialize all the seeded snaps

[Chen-Han Hsiao (Stanley)]

Public bug reported:

snapd didn't initialize all the seeded snaps

bionic-desktop-amd64.iso (20180522)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: snapd 2.32.9+18.04
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue May 22 22:59:18 2018
InstallationDate: Installed on 2018-05-23 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180522)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_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: Undecided
 Status: New


** Tags: amd64 apport-bug bionic package-from-proposed third-party-packages

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
 Assignee: (unassigned) => Chen-Han Hsiao (Stanley) (swem)

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772844/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772844] Re: snapd didn't initialize all the seeded snaps

[Chen-Han Hsiao (Stanley)]

$ 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   2428928 May 22 04:15 gnome-calculator_167.snap
-rw-r--r-- 1 root root  13594624 May 22 04:16 gnome-characters_86.snap
-rw-r--r-- 1 root root  22609920 May 22 04:16 gnome-logs_31.snap
-rw-r--r-- 1 root root   3813376 May 22 04:16 gnome-system-monitor_39.snap
-rw-r--r-- 1 root root  33460224 May 22 04:17 gtk-common-themes_3.snap

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772844/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772374] Re: ubiquity need mount point /sys/firmware/efi/efivars

[Chen-Han Hsiao (Stanley)]

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 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 notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772374/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767896] Re: Live 18.04 with broken seed causes snapd high CPU usage

[Chen-Han Hsiao (Stanley)]

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, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767896

Title:
  Live 18.04 with broken seed causes snapd high CPU usage

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1767896/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772374] Re: ubiquity need mount point /sys/firmware/efi/efivars

[Chen-Han Hsiao (Stanley)]

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, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772374

Title:
  ubiquity need mount point /sys/firmware/efi/efivars

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772374/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772374] Re: ubiquity need mount point /sys/firmware/efi/efivars

[Chen-Han Hsiao (Stanley)]

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"
   
https://bugs.launchpad.net/oem-priority/+bug/1772374/+attachment/5142256/+files/0001-add-mount-point-LP-1772374.patch

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772374/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772374] Re: ubiquity need mount point /sys/firmware/efi/efivars

[Chen-Han Hsiao (Stanley)]

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.
https://bugs.launchpad.net/bugs/1772374

Title:
  ubiquity need mount point /sys/firmware/efi/efivars

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772374/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772374] [NEW] ubiquity need mount point /sys/firmware/efi/efivars

[Chen-Han Hsiao (Stanley)]

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 ubuntu ubiquity[29387]: Creating config file /etc/default/grub 
with new version
May 21 08:21:56 ubuntu ubiquity[29387]: Installing for x86_64-efi platform.
May 21 08:21:57 ubuntu ubiquity[29387]: Skipping unreadable variable 
"Boot": Input/output error
May 21 08:21:57 ubuntu ubiquity[29387]: Could not prepare Boot variable: 
Input/output error
May 21 08:21:57 ubuntu ubiquity[29387]: grub-install: error: efibootmgr failed 
to register the boot entry: Input/output error.
May 21 08:21:57 ubuntu ubiquity[29387]: Failed: grub-install --target=x86_64-efi
May 21 08:21:57 ubuntu ubiquity[29387]: WARNING: Bootloader is not properly 
installed, system may not be bootable
May 21 08:21:57 ubuntu ubiquity[29387]: Setting up grub-efi-amd64-signed 
(1.93+2.02-2ubuntu8) ...
May 21 08:21:57 ubuntu ubiquity[29387]: Installing for x86_64-efi platform.
May 21 08:21:58 ubuntu ubiquity[29387]: Skipping unreadable variable 
"Boot": Input/output error
May 21 08:21:58 ubuntu ubiquity[29387]: Could not prepare Boot variable: 
Input/output error
May 21 08:21:58 ubuntu ubiquity[29387]: grub-install: error: efibootmgr failed 
to register the boot entry: Input/output error.
May 21 08:21:58 ubuntu ubiquity[29387]: dpkg: error processing package 
grub-efi-amd64-signed (--configure):
May 21 08:21:58 ubuntu ubiquity[29387]:  installed grub-efi-amd64-signed 
package post-installation script subprocess returned error exit status 1
May 21 08:21:58 ubuntu ubiquity[29387]: Errors were encountered while 
processing:
May 21 08:21:58 ubuntu ubiquity[29387]:  grub-efi-amd64-signed

** Affects: oem-priority
 Importance: Undecided
 Status: New

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772374/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772374] Re: ubiquity need mount point /sys/firmware/efi/efivars

[Chen-Han Hsiao (Stanley)]

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

-- 
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 notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772374/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770580] Re: 2-in-1 laptop won't auto-rotate after installation

[Chen-Han Hsiao (Stanley)]

** 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, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770580

Title:
  2-in-1 laptop won't auto-rotate after installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1770580/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770580] [NEW] 2-in-1 laptop won't auto-rotate after installation

[Chen-Han Hsiao (Stanley)]

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 once.

** Affects: oem-priority
 Importance: Undecided
 Status: New

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: oem-priority
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770580

Title:
  2-in-1 laptop won't auto-rotate after installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1770580/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767896] Re: Live 18.04 with broken seed causes snapd high CPU usage

[Chen-Han Hsiao (Stanley)]

** 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.
https://bugs.launchpad.net/bugs/1767896

Title:
  Live 18.04 with broken seed causes snapd high CPU usage

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1767896/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767896] Re: Live 18.04 with broken seed causes snapd high CPU usage

[Chen-Han Hsiao (Stanley)]

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 Ubuntu.
https://bugs.launchpad.net/bugs/1767896

Title:
  Live 18.04 with broken seed causes snapd high CPU usage

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1767896/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767896] Re: Live 18.04 with broken seed causes snapd high CPU usage

[Chen-Han Hsiao (Stanley)]

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 snap "gtk-common-themes"
error: cannot find snap "gtk-common-themes": snap not found

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767896

Title:
  Live 18.04 with broken seed causes snapd high CPU usage

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1767896/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767896] Re: Live 18.04 with broken seed causes snapd high CPU usage

[Chen-Han Hsiao (Stanley)]

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.
https://bugs.launchpad.net/bugs/1767896

Title:
  Live 18.04 with broken seed causes snapd high CPU usage

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1767896/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767896] Re: Live 18.04 with persistence snapd high CPU usage

[Chen-Han Hsiao (Stanley)]

** 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.net/bugs/1767896

Title:
  Live 18.04 with persistence snapd high CPU usage

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1767896/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767896] Re: Live 18.04 with persistence snapd high CPU usage

[Chen-Han Hsiao (Stanley)]

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 2018-04-30

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767896

Title:
  Live 18.04 with persistence snapd high CPU usage

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1767896/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767896] Re: Live 18.04 with persistence snapd high CPU usage

[Chen-Han Hsiao (Stanley)]

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 a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767896

Title:
  Live 18.04 with persistence snapd high CPU usage

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1767896/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767896] Re: Live 18.04 with persistence snapd high CPU usage

[Chen-Han Hsiao (Stanley)]

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 systemd[1]: Starting Snappy daemon...
May  9 06:40:11 u-XPS-13-9360 systemd[1]: Started Snappy daemon.
May  9 06:40:17 u-XPS-13-9360 systemd[1]: snapd.service: Service hold-off time 
over, scheduling restart.
May  9 06:40:17 u-XPS-13-9360 systemd[1]: Stopped Snappy daemon.
May  9 06:40:17 u-XPS-13-9360 systemd[1]: Starting Snappy daemon...
May  9 06:40:18 u-XPS-13-9360 systemd[1]: Started Snappy daemon.
May  9 06:40:22 u-XPS-13-9360 systemd[1]: snapd.service: Service hold-off time 
over, scheduling restart.
May  9 06:40:22 u-XPS-13-9360 systemd[1]: Stopped Snappy daemon.
May  9 06:40:22 u-XPS-13-9360 systemd[1]: Starting Snappy daemon...
May  9 06:40:22 u-XPS-13-9360 systemd[1]: Started Snappy daemon.
May  9 06:40:29 u-XPS-13-9360 systemd[1]: snapd.service: Service hold-off time 
over, scheduling restart.
May  9 06:40:29 u-XPS-13-9360 systemd[1]: Stopped Snappy daemon.
May  9 06:40:29 u-XPS-13-9360 systemd[1]: Starting Snappy daemon...
May  9 06:40:30 u-XPS-13-9360 systemd[1]: Started Snappy daemon.


$ snap version 
snap2.32.6
snapd   2.32.6
series  16
ubuntu  18.04
kernel  4.15.0-20-generic

$ snap changes 
ID   Status  Spawn Ready Summary
1Error   2018-05-09T10:40:16Z  2018-05-09T10:40:23Z  Initialize system state
2Done2018-05-09T10:40:16Z  2018-05-09T10:45:20Z  Initialize device
3Error   2018-05-09T10:40:27Z  2018-05-09T10:40:35Z  Initialize system state
4Error   2018-05-09T10:40:38Z  2018-05-09T10:40:45Z  Initialize system state
5Error   2018-05-09T10:40:48Z  2018-05-09T10:40:56Z  Initialize system state
6Error   2018-05-09T10:40:59Z  2018-05-09T10:41:07Z  Initialize system state
7Error   2018-05-09T10:41:10Z  2018-05-09T10:41:18Z  Initialize system state
8Error   2018-05-09T10:41:21Z  2018-05-09T10:41:30Z  Initialize system state
9Error   2018-05-09T10:41:33Z  2018-05-09T10:41:42Z  Initialize system state
10   Error   2018-05-09T10:41:45Z  2018-05-09T10:41:54Z  Initialize system state
11   Error   2018-05-09T10:41:57Z  2018-05-09T10:42:07Z  Initialize system state
12   Error   2018-05-09T10:42:10Z  2018-05-09T10:42:19Z  Initialize system state
13   Error   2018-05-09T10:42:22Z  2018-05-09T10:42:32Z  Initialize system state
14   Error   2018-05-09T10:42:35Z  2018-05-09T10:42:45Z  Initialize system state
15   Error   2018-05-09T10:42:48Z  2018-05-09T10:42:58Z  Initialize system state
16   Error   2018-05-09T10:43:02Z  2018-05-09T10:43:13Z  Initialize system state
17   Error   2018-05-09T10:43:16Z  2018-05-09T10:43:27Z  Initialize system state
18   Error   2018-05-09T10:43:30Z  2018-05-09T10:43:42Z  Initialize system state
19   Error   2018-05-09T10:43:46Z  2018-05-09T10:43:58Z  Initialize system state
20   Error   2018-05-09T10:44:01Z  2018-05-09T10:44:13Z  Initialize system state
21   Error   2018-05-09T10:44:16Z  2018-05-09T10:44:28Z  Initialize system state
22   Error   2018-05-09T10:44:31Z  2018-05-09T10:44:50Z  Initialize system state
23   Error   2018-05-09T10:44:53Z  2018-05-09T10:46:37Z  Initialize system state

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767896

Title:
  Live 18.04 with persistence snapd high CPU usage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1767896/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767896] Re: Live 18.04 with persistence snapd high CPU usage

[Chen-Han Hsiao (Stanley)]

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 root root 146841600 May  8 04:22 gnome-3-26-1604_62.snap
-rw-r--r-- 2 root root   2428928 May  8 04:22 gnome-calculator_167.snap
-rw-r--r-- 2 root root  13594624 May  8 04:23 gnome-characters_86.snap
-rw-r--r-- 2 root root  22609920 May  8 04:23 gnome-logs_31.snap
-rw-r--r-- 2 root root   3813376 May  8 04:23 gnome-system-monitor_39.snap

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767896

Title:
  Live 18.04 with persistence snapd high CPU usage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1767896/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770041] [NEW] I dont remember, something about one package failing to install

[STANLEY PAUL MIKU]

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
CurrentDesktop: ubuntu:GNOME
Date: Tue May  8 18:21:45 2018
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic ubiquity-18.04.14 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770041

Title:
  I dont remember, something about one package failing to install

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1770041/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned

[Chen-Han Hsiao (Stanley)]

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: "sosreport-u-VirtualBox-20180502021308.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-menus/+bug/1766890/+attachment/5131826/+files/sosreport-u-VirtualBox-20180502021308.tar.xz

-- 
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, abandoned

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1766890/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned

[Chen-Han Hsiao (Stanley)]

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, abandoned

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1766890/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1550779] Re: [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

[Chen-Han Hsiao (Stanley)]

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 v4.15-rc1

** Bug watch added: freedesktop.org Bugzilla #100302
   https://bugs.freedesktop.org/show_bug.cgi?id=100302

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1550779

Title:
  [i915]] *ERROR* CPU pipe A FIFO underrun - Xorg glitches

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550779/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1664931] Re: [OSSA-2017-005] nova rebuild ignores all image properties and scheduler filters (CVE-2017-16239)

[Jeremy Stanley]

** 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
  scheduler filters (CVE-2017-16239)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1664931/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1723913] Re: [Artful] Support headset mode for DELL WYSE

[Chen-Han Hsiao (Stanley)]

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), 
linux-image-4.13.0-17-generic:amd64 (4.13.0-17.20, automatic)
Upgrade: linux-headers-generic:amd64 (4.13.0.16.17, 4.13.0.17.18), 
linux-image-generic:amd64 (4.13.0.16.17, 4.13.0.17.18), linux-generic:amd64 
(4.13.0.16.17, 4.13.0.17.18)
End-Date: 2017-11-13  02:49:00


** Tags removed: verification-needed-artful
** Tags added: verification-done-artful

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723913

Title:
  [Artful] Support headset mode for DELL WYSE

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1723913/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1723915] Re: [Artful] Some Dell Monitors Doesn't Work Well with Dell/Wyse 3040

[Chen-Han Hsiao (Stanley)]

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), 
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), 
linux-image-4.13.0-17-generic:amd64 (4.13.0-17.20, automatic)
Upgrade: linux-headers-generic:amd64 (4.13.0.16.17, 4.13.0.17.18), 
linux-image-generic:amd64 (4.13.0.16.17, 4.13.0.17.18), 
linux-signed-image-generic:amd64 (4.13.0.16.17, 4.13.0.17.18), 
linux-signed-generic:amd64 (4.13.0.16.17, 4.13.0.17.18), linux-generic:amd64 
(4.13.0.16.17, 4.13.0.17.18)
End-Date: 2017-11-13  02:24:30

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723915

Title:
  [Artful] Some Dell Monitors Doesn't Work Well with Dell/Wyse 3040

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1723915/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1727689] [NEW] irq error at boot on ASUS E402SA

[Joel Stanley]

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, 
[2.709796] chv_gpio_irqchip+0x0/0x120
[2.709797] ->action():   (null)
[2.709798]IRQ_NOPROBE set
[2.709815] irq 171, desc: a038fa08a600, depth: 1, count: 0, unhandled: 0
[2.709817] ->handle_irq():  810e5b60, 
[2.709820] handle_bad_irq+0x0/0x230
[2.709821] ->irq_data.chip(): 81f711a0, 
[2.709824] chv_gpio_irqchip+0x0/0x120
[2.709825] ->action():   (null)
[2.709826]IRQ_NOPROBE set
[2.709843] irq 171, desc: a038fa08a600, depth: 1, count: 0, unhandled: 0
[2.709845] ->handle_irq():  810e5b60, 
[2.709848] handle_bad_irq+0x0/0x230
[2.709849] ->irq_data.chip(): 81f711a0, 
[2.709851] chv_gpio_irqchip+0x0/0x120
[2.709852] ->action():   (null)
[2.709853]IRQ_NOPROBE set

The machine is running the latest BIOS from the ASUS.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  joel   2523 F pulseaudio
CurrentDesktop: i3
Date: Thu Oct 26 19:05:06 2017
HibernationDevice: RESUME=UUID=373eae03-72b7-4875-a600-caa904e497d8
InstallationDate: Installed on 2017-10-09 (17 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 0bda:57de Realtek Semiconductor Corp. 
 Bus 001 Device 004: ID 07b4:012e Olympus Optical Co., Ltd 
 Bus 001 Device 003: ID 091e:240c Garmin International 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. E402SA
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-16-generic N/A
 linux-backports-modules-4.13.0-16-generic  N/A
 linux-firmware 1.169
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/20/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E402SA.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: E402SA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE402SA.300:bd07/20/2016:svnASUSTeKCOMPUTERINC.:pnE402SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE402SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: E
dmi.product.name: E402SA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727689

Title:
  irq error at boot on ASUS E402SA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1727689/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1711756] Re: Chromium crashes when changing profiles

[Chen-Han Hsiao (Stanley)]

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  60.0.3112.78-0ubuntu0.16.04.1293 
all  chromium-browser language packages
ii  chromium-codecs-ffmpeg-extra   60.0.3112.78-0ubuntu0.16.04.1293 
amd64Extra ffmpeg codecs for the Chromium Browser
ii  unity-scope-chromiumbookmarks  0.1+13.10.20130723-0ubuntu1  
all  Chromium bookmarks scope for Unity

DistroRelease: Ubuntu 16.04
Uname: Linux 4.10.0-33-generic x86_64
"Use system title bar and borders" is turned off.



Received signal 11 SEGV_MAPERR 
#0 0x7ff82038e3f7 base::debug::StackTrace::StackTrace()
#1 0x7ff82038df6f 
#2 0x7ff820b31390 
  r8: 55ba72b2cc90  r9:  r10: 0008588a r11: 
7ff806d96350
 r12: 55ba71b80b60 r13: 55ba71d975c0 r14: 55ba72c92a80 r15: 
7fffa20bacc0
  di: 55ba722d6868  si: 55ba72c92a80  bp: 7fffa20bb110  bx: 
7fffa20baca0
  dx: 0003  ax: 55ba722d7be0  cx: 0002  sp: 
7fffa20bac98
  ip:  efl: 00010202 cgf: 002b0033 erf: 
0014
 trp: 000e msk:  cr2: 
[end of stack trace]
Calling _exit(1). Core file will not be generated.
[1:1:0100/00.715193:ERROR:broker_posix.cc(41)] Invalid node channel message
[1:1:0100/00.715989:ERROR:broker_posix.cc(41)] Invalid node channel message

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711756

Title:
  Chromium crashes when changing profiles

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1711756/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1710560] [NEW] i3status cannot parse it's configuration file

[Joel Stanley]

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 documentation.

# It is important that this file is edited as UTF-8.
# The following line should contain a sharp s:
# ß
# If the above line is not correctly displayed, fix your editor first!

general {
colors = true

This looks to be related to the issue reported at
https://github.com/i3/i3status/issues/225

However, that bug says a fix in libconfuse 3.2 should resolve the issue.
I am running libconfuse 3.2:

$ apt-cache policy libconfuse1
libconfuse1:
  Installed: 3.2+dfsg-1

I used apt-get source to download and build a local copy of i3status.
This was able to parse the config file fine.

I did a build of i3status against libconfuse 3.0, and it fails to run
against the system copy (version 3.2).

It looks like i3status needs to be rebuilt against the libconfuse 3.2
that is in the archive.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: i3status 2.11-1
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu5
Architecture: amd64
CurrentDesktop: i3
Date: Mon Aug 14 16:34:35 2017
InstallationDate: Installed on 2016-05-12 (459 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
SourcePackage: i3status
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: i3status (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug artful

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1710560

Title:
  i3status cannot parse it's configuration file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/i3status/+bug/1710560/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1697218] [NEW] Official DocumentationOfficial Documentation Ubuntu Documentation » Ubuntu 11.04 » Ubuntu Desktop Guide » Hardware › Smart cards and fingerprint readers » page contains broken link

[Stanley Ralph]

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: ubuntu-docs (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697218

Title:
  Official DocumentationOfficial Documentation Ubuntu Documentation »
  Ubuntu 11.04 » Ubuntu Desktop Guide » Hardware › Smart cards and
  fingerprint readers » page contains broken link

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1697218/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1663462] Re: weather-util needs updated due to NWS changes

[Jeremy Stanley]

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 (fungi)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1663462

Title:
  weather-util needs updated due to NWS changes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/weather-util/+bug/1663462/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1573959] Re: On-screen text disappears after suspend

[Chen-Han Hsiao (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 4th Gen Core 
Processor Integrated Graphics Controller [8086:0416] (rev 06)

$ uname -a
Linux USER-PC 4.8.0-46-generic #49~16.04.1-Ubuntu SMP Fri Mar 31 14:51:03 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573959

Title:
  On-screen text disappears after suspend

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1573959/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1663462] Re: weather-util needs updated due to NWS changes

[Jeremy Stanley]

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 about an SRU).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1663462

Title:
  weather-util needs updated due to NWS changes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/weather-util/+bug/1663462/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1573307] Re: wget crashed with SIGSEGV in __memset_avx2()

[Chen-Han Hsiao (Stanley)]

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 
http://old-releases.ubuntu.com/releases/16.04.0/ubuntu-16.04-desktop-amd64.manifest
--2017-03-28 07:06:55--  
http://old-releases.ubuntu.com/releases/16.04.0/ubuntu-16.04-desktop-amd64.manifest
Resolving old-releases.ubuntu.com (old-releases.ubuntu.com)... 91.189.88.17
Connecting to old-releases.ubuntu.com 
(old-releases.ubuntu.com)|91.189.88.17|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 64142 (63K) [application/x-ms-manifest]
Saving to: 'ubuntu-16.04-desktop-amd64.manifest.2'

Segmentation fault (core dumped)



 wget 1.17.1-1ubuntu1.2 
$ wget 
http://old-releases.ubuntu.com/releases/16.04.0/ubuntu-16.04-desktop-amd64.manifest
--2017-03-28 07:07:17--  
http://old-releases.ubuntu.com/releases/16.04.0/ubuntu-16.04-desktop-amd64.manifest
Resolving old-releases.ubuntu.com (old-releases.ubuntu.com)... 91.189.88.17
Connecting to old-releases.ubuntu.com 
(old-releases.ubuntu.com)|91.189.88.17|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 64142 (63K) [application/x-ms-manifest]
Saving to: 'ubuntu-16.04-desktop-amd64.manifest.3'

ubuntu-16.04-desktop-amd64.manifest.3
100%[==>]
62.64K  --.-KB/sin 0.007s

2017-03-28 07:07:17 (8.19 MB/s) - 'ubuntu-16.04-desktop-amd64.manifest.3' saved 
[64142/64142]


** Tags removed: verification-needed
** Tags added: verification-done

-- 
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 __memset_avx2()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1573307/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1573307] Re: wget crashed with SIGSEGV in __memset_avx2()

[Chen-Han Hsiao (Stanley)]

** 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 
http://old-releases.ubuntu.com/releases/16.04.0/ubuntu-16.04-desktop-amd64.manifest;
 under a narrow terminal (such as width less than 40 characters)
+ Problems:
+   1. The wget crash with segmentation fault
+ Expected behavior:
+   1. wget will not crash
+ 
+ [Test Case]
+   After upgrading to the new version, the repeating the above steps should 
give expected behavior.
+ 
+ [Regression Potential]
+   Potential of causing regression is relatively small for a two line change 
for assertion check
+ 
+ [Other Info]
+ 
+ 
+ 
  EDIT(other user): The crash actually happens when the terminal window is
  too small.
  
  When I try to download a big file with wget on Ubuntu 16.04 it crashes
  after a couple seconds.
  
  To reproduce the bug try the following:
  
  wget http://releases.ubuntu.com/16.04/ubuntu-16.04-desktop-amd64.iso
  
  I've asked another guy on IRC on channel #ubuntu-it to try and reproduce this 
bug
  and he said it was crashing also on his machine.
  
  evan@HPPC:~$ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  
  evan@HPPC:~$ apt-cache policy wget
  wget:
-   Installato: 1.17.1-1ubuntu1
-   Candidato:  1.17.1-1ubuntu1
-   Tabella versione:
-  *** 1.17.1-1ubuntu1 500
- 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installato: 1.17.1-1ubuntu1
+   Candidato:  1.17.1-1ubuntu1
+   Tabella versione:
+  *** 1.17.1-1ubuntu1 500
+ 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: wget 1.17.1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Apr 22 01:34:10 2016
  ExecutablePath: /usr/bin/wget
  InstallationDate: Installed on 2016-04-21 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: wget 
http://releases.ubuntu.com/16.04/ubuntu-16.04-desktop-amd64.iso
  SegvAnalysis:
-  Segfault happened at: 0x7f4eac3b7328 <__memset_avx2+392>:rep stos 
%al,%es:(%rdi)
-  PC (0x7f4eac3b7328) ok
-  source "%al" ok
-  destination "%es:(%rdi)" (0x562969134000) not located in a known VMA region 
(needed writable region)!
+  Segfault happened at: 0x7f4eac3b7328 <__memset_avx2+392>:rep stos 
%al,%es:(%rdi)
+  PC (0x7f4eac3b7328) ok
+  source "%al" ok
+  destination "%es:(%rdi)" (0x562969134000) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing unknown VMA
  Signal: 11
  SourcePackage: wget
  StacktraceTop:
-  __memset_avx2 () at ../sysdeps/x86_64/multiarch/memset-avx2.S:161
-  ?? ()
-  ?? ()
-  ?? ()
-  ?? ()
+  __memset_avx2 () at ../sysdeps/x86_64/multiarch/memset-avx2.S:161
+  ?? ()
+  ?? ()
+  ?? ()
+  ?? ()
  Title: wget crashed with SIGSEGV in __memset_avx2()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

-- 
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 __memset_avx2()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1573307/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1573307] Re: wget crashed with SIGSEGV in __memset_avx2()

[Chen-Han Hsiao (Stanley)]

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 Mon Sep 17 00:00:00 2001
From: Darshit Shah 
Date: Sat, 5 Mar 2016 11:58:53 +0100
Subject: [PATCH] Fix assertion in Progress bar

* src/progress.c (create_image): Fix off-by-one error in assert()
statement for progress bar width.
Reported-By: Gisle Vanem 
---
 src/progress.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/progress.c b/src/progress.c
index 8a5df21..481e21e 100644
--- a/src/progress.c
+++ b/src/progress.c
@@ -1164,7 +1164,7 @@ create_image (struct bar_progress *bp, double 
dl_total_time, bool done)
 }
 
   padding = bp->width - count_cols (bp->buffer);
-  assert (padding > 0 && "Padding length became non-positive!");
+  assert (padding >= 0 && "Padding length became non-positive!");
   padding = padding > 0 ? padding : 0;
   memset (p, ' ', padding);
   p += padding;
-- 
2.7.4


Update debdiff

** Patch added: "wget_1.17.1-1ubuntu1.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1573307/+attachment/4828036/+files/wget_1.17.1-1ubuntu1.2.debdiff

-- 
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 __memset_avx2()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1573307/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1573307] Re: wget crashed with SIGSEGV in __memset_avx2()

[Chen-Han Hsiao (Stanley)]

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 __memset_avx2()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1573307/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1573307] Re: wget crashed with SIGSEGV in __memset_avx2()

[Chen-Han Hsiao (Stanley)]

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
http://git.savannah.gnu.org/cgit/wget.git/commit/?id=7099f4899880eaefc2c40a3dc7693ab4174a819b

>From 7099f4899880eaefc2c40a3dc7693ab4174a819b Mon Sep 17 00:00:00 2001
From: Darshit Shah 
Date: Mon, 22 Feb 2016 15:08:15 +0100
Subject: [PATCH] Sanitize value sent to memset to prevent SEGFAULT

---
 src/progress.c | 5 +
 1 file changed, 5 insertions(+)

diff --git a/src/progress.c b/src/progress.c
index 93f6246..8a5df21 100644
--- a/src/progress.c
+++ b/src/progress.c
@@ -1164,6 +1164,8 @@ create_image (struct bar_progress *bp, double 
dl_total_time, bool done)
 }
 
   padding = bp->width - count_cols (bp->buffer);
+  assert (padding > 0 && "Padding length became non-positive!");
+  padding = padding > 0 ? padding : 0;
   memset (p, ' ', padding);
   p += padding;
   *p = '\0';
@@ -1174,6 +1176,9 @@ create_image (struct bar_progress *bp, double 
dl_total_time, bool done)
* from the release code since we do not want Wget to crash and burn when the
* assertion fails. Instead Wget should continue downloading and display a
* horrible and irritating progress bar that spams the screen with newlines.
+   *
+   * By default, all assertions are disabled in a Wget build and are enabled
+   * only with the --enable-assert configure option.
*/
   assert (count_cols (bp->buffer) == bp->width);
 }
-- 
2.7.4


** Patch added: "wget_1.17.1-1ubuntu1.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1573307/+attachment/4825717/+files/wget_1.17.1-1ubuntu1.2.debdiff

-- 
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 __memset_avx2()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1573307/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1594902] Re: Failed to upgrade to libvirt-bin 1.3.1-1ubuntu10.1 on Ubuntu 16.04 64-bit

[Ben Stanley]

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 libvirt-bin 1.3.1-1ubuntu10.1 on Ubuntu 16.04
  64-bit

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1594902/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1621179] Re: weather can not get data ( http://weather.noaa.gov has been discontinued)

[Jeremy Stanley]

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 notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1621179

Title:
  weather can not get data ( http://weather.noaa.gov has been
  discontinued)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/weather-util/+bug/1621179/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1648267] Re: Regression with Zesty binutils building u-boot

[Joel Stanley]

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 there:

 http://lists.denx.de/pipermail/u-boot/2016-December/275664.html

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1648267

Title:
  Regression with Zesty binutils building u-boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1648267/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1648267] Re: Regression with Zesty binutils building u-boot

[Joel Stanley]

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 notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1648267

Title:
  Regression with Zesty binutils building u-boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1648267/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1648267] [NEW] Regression with Zesty binutils building u-boot

[Joel Stanley]

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
Makefile:1187: recipe for target 'u-boot' failed

If I instad use the GNU ld (2.27-9ubuntu1+9) 2.27 (arm-none-eabi), the
same code links without issue.

** Affects: binutils (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1648267

Title:
  Regression with Zesty binutils building u-boot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1648267/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1640670] [NEW] Crash in GfxICCBasedColorSpace::parse

[Joel Stanley]

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*, 
OutputDev*, GfxState*, int) ()
   from /usr/lib/x86_64-linux-gnu/libpoppler.so.61
#3  0x7f174b4a0872 in Page::loadThumb(unsigned char**, int*, int*, int*) () 
from /usr/lib/x86_64-linux-gnu/libpoppler.so.61
#4  0x7f174bbb7de9 in poppler_page_get_thumbnail () from 
/usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8
#5  0x7f174bdf5b1b in ?? () from 
/usr/lib/x86_64-linux-gnu/evince/4/backends/libpdfdocument.so
#6  0x557297930bb2 in evince_thumbnail_pngenc_get (document=0x7f1744003700, 
thumbnail=0x5572995948c0 "/tmp/.gnome_desktop_thumbnail.ZD13QY", size=256) 
at evince-thumbnailer.c:182
#7  0x5572979307d0 in main (argc=, argv=) at 
evince-thumbnailer.c:301


getColorSpace, part of lcms, is passed a null pointer.

GfxICCBasedColorSpace::parse has this sequence of code:


  if (hp == 0) {
error(errSyntaxWarning, -1, "read ICCBased color space profile error");
  } else {
cmsHPROFILE dhp = (state != NULL && state->getDisplayProfile() != NULL) ? 
state->getDisplayProfile() : displayProfile;
if (dhp == NULL) dhp = RGBProfile;
unsigned int cst = getCMSColorSpaceType(cmsGetColorSpace(hp));
unsigned int dNChannels = getCMSNChannels(cmsGetColorSpace(dhp));
unsigned int dcst = getCMSColorSpaceType(cmsGetColorSpace(dhp));

hp can't be null, or else we wouldn't be calling cmsGetColorSpace. This
means dhp must be NULL, which can only happen if RGBProfile is null.

RGBProfile is set up in GfxColorSpace::setupColorProfiles(). Assuming
this function has been called, it does the following:

  RGBProfile = loadColorProfile("RGB.icc");
  if (RGBProfile == NULL) {
/* use built in sRGB profile */
RGBProfile = cmsCreate_sRGBProfile();
  }

cmsCreate_sRGBProfile can return NULL in a number of ways.

I'm not sure what the fix is though.

** Affects: poppler (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640670

Title:
  Crash in GfxICCBasedColorSpace::parse

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1640670/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs