Your message dated Sun, 11 Dec 2016 00:27:55 -0500
with message-id
<CANTw=mpwchf8ckakbxhgpdsjbe1wpzk4cxo92xu5ujl-c7g...@mail.gmail.com>
and subject line re: chromium: takes forever to start
has caused the Debian Bug report #839168,
regarding chromium: takes forever to start
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
839168: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839168
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: chromium
Version: 53.0.2785.113-1
Severity: important
Chromium takes very long to start, with these messages:
~$ chromium
[19933:19954:0929/194334:ERROR:file_path_watcher_linux.cc(264)]
inotify_init() failed: Too many open files
[19933:19966:0929/194334:ERROR:nss_util.cc(809)] After loading Root
Certs, loaded==false: NSS error code: -8018
[19989:19989:0929/194334:ERROR:sandbox_linux.cc(343)]
InitializeSandbox() called with multiple threads in process
gpu-process.
Gkr-Message: secret service operation failed: Did not receive a
reply. Possible causes include: the remote application did not send a
reply, the message bus security policy blocked the reply, the reply
timeout expired, or the network connection was broken.
The time taken is so long (about a minute) that I can start it only from
a terminal, because when I start it from the Mate menu, it gives up
after a while.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (990, 'testing'), (101, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages chromium depends on:
ii libasound2 1.1.2-1
ii libatk1.0-0 2.21.90-2
ii libavcodec57 10:3.1.3-dmo3
ii libavformat57 10:3.1.3-dmo3
ii libavutil55 10:3.1.3-dmo3
ii libc6 2.23-5
ii libcairo2 1.14.6-1+b1
ii libcups2 2.2.0-2
ii libdbus-1-3 1.10.10-1
ii libexpat1 2.2.0-1
ii libfontconfig1 2.11.0-6.7
ii libfreetype6 2.6.3-3+b1
ii libgcc1 1:6.1.1-11
ii libgdk-pixbuf2.0-0 2.34.0-1
ii libglib2.0-0 2.49.6-1
ii libgnome-keyring0 3.12.0-1+b1
ii libgtk-3-0 3.21.5-3
ii libharfbuzz0b 1.2.7-1+b1
ii libjpeg62-turbo 1:1.5.0-1
ii libnettle6 3.2-1
ii libnspr4 2:4.12-2
ii libnss3 2:3.26-2
ii libpango-1.0-0 1.40.2-1
ii libpangocairo-1.0-0 1.40.2-1
ii libpci3 1:3.3.1-1.1
ii libpulse0 9.0-3
ii libspeechd2 0.8.5-1
ii libstdc++6 6.1.1-11
ii libx11-6 2:1.6.3-1
ii libxcomposite1 1:0.4.4-1
ii libxcursor1 1:1.1.14-1+b1
ii libxdamage1 1:1.1.4-2+b1
ii libxext6 2:1.3.3-1
ii libxfixes3 1:5.0.2-1
ii libxi6 2:1.7.6-1
ii libxml2 2.9.4+dfsg1-2
ii libxrandr2 2:1.5.0-1
ii libxrender1 1:0.9.9-2
ii libxslt1.1 1.1.29-1
ii libxss1 1:1.2.2-1
ii libxtst6 2:1.2.2-1+b1
ii x11-utils 7.7+3
ii xdg-utils 1.1.1-1
Versions of packages chromium recommends:
ii fonts-liberation 1:1.07.4-2
Versions of packages chromium suggests:
pn chromium-l10n <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
version: 54.0.2840.101-1
The package is no longer built with support for gnome-keyring, which
should fix this. Please reopen if that isn't the case.
Best wishes,
Mike
--- End Message ---
