ERROR:nss_util.cc(856) NSS error code: -8018

Bug #1382929 reported by dino99 on 2014-10-19
22
This bug affects 5 people
Affects Status Importance Assigned to Milestone
nss-mdns (Ubuntu)
High
Unassigned

Bug Description

when i report an issue from the terminal (ubuntu-gnome-desktop) i get that error when chromium-browser 37 open the login page:

oem@u32:~$ ubuntu-bug ubuntu-gnome-default-settings
oem@u32:~$ Created new window in existing browser session.
[4094:4133:1019/095113:ERROR:nss_util.cc(856)] After loading Root Certs, loaded==false: NSS error code: -8018
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0221
^C
oem@u32:~$ ubuntu-bug libnss-mdns
oem@u32:~$ Created new window in existing browser session.
[5458:5497:1019/100037:ERROR:nss_util.cc(856)] After loading Root Certs, loaded==false: NSS error code: -8018

That system is using systemd-boot as default, and is a single desktop without lan/wan or sharing, but with wine installed. So that bug can affect an other package.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: libnss-mdns 0.10-6
ProcVersionSignature: Ubuntu 3.16.0-23.30-generic 3.16.4
Uname: Linux 3.16.0-23-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.14.7-0ubuntu7
Architecture: i386
CurrentDesktop: GNOME
Date: Sun Oct 19 10:00:25 2014
SourcePackage: nss-mdns
UpgradeStatus: No upgrade log present (probably fresh install)

dino99 (9d9) wrote :
description: updated
tags: added: systemd-boot
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nss-mdns (Ubuntu):
status: New → Confirmed
Martin Pitt (pitti) wrote :

dino99, I only want "systemd-boot" tags for bugs which are specific to booting with systemd and are regressions compared to booting with upstart. This does *not* mean "the system was booted with systemd". Thanks!

tags: removed: systemd-boot
Changed in nss-mdns (Ubuntu):
importance: Undecided → Medium
importance: Medium → High
dino99 (9d9) wrote :

Does not get that issue with Vivid i386

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers