Your message dated Thu, 16 Feb 2017 21:57:59 -0500
with message-id 
<CANTw=MOG3TQP5kGGaxPggCM+sZdCY45Q=qmdvqtwjq+2xqg...@mail.gmail.com>
and subject line Re: Bug#854925: chromium: Chromium does not start -- execv 
failed: No such file or directory
has caused the Debian Bug report #854925,
regarding chromium: Chromium does not start -- execv failed: No such file or 
directory
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 ow...@bugs.debian.org
immediately.)


-- 
854925: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854925
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: chromium
Version: 56.0.2924.76-1~deb8u1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

   * What led up to the situation?

Installed chromium but it won't start. Tried purge and reinstall, same result.
When starting via the command line, here is the output:

alex@PCDELL:~$ chromium
execv failed: No such file or directory
[31913:31913:0211/233130.544882:FATAL:zygote_host_impl_linux.cc(182)] Check
failed: ReceiveFixedMessage(fds[0], kZygoteBootMessage,
sizeof(kZygoteBootMessage), &boot_pid).
#0 0x7fb25819483e <unknown>
#1 0x7fb2581a8f7b <unknown>
#2 0x7fb2579e8045 <unknown>
#3 0x7fb2579e725e <unknown>
#4 0x7fb2579e784e <unknown>
#5 0x7fb25767c72c <unknown>
#6 0x7fb25768436d <unknown>
#7 0x7fb25767bdcc <unknown>
#8 0x7fb257dfb64b <unknown>
#9 0x7fb257df9fa0 <unknown>
#10 0x7fb2569d21bc ChromeMain
#11 0x7fb24e9b1b45 __libc_start_main
#12 0x7fb2569d2069 <unknown>

Abortado

I've tried to change permissions of the ~/.config/chromium folder. Also, I
deleted the Apparmor profile from /etc/apparmor.d/ and restarted apparmor
service. None of this worked.

Thank you for your attention,

Alexei



-- System Information:
Debian Release: 8.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=pt_BR.UTF-8, LC_CTYPE=pt_BR.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.0.28-1
ii  libatk1.0-0          2.14.0-1
ii  libc6                2.19-18+deb8u7
ii  libcairo2            1.14.0-2.1+deb8u2
ii  libcups2             1.7.5-11+deb8u1
ii  libdbus-1-3          1.8.22-0+deb8u1
ii  libexpat1            2.1.0-6+deb8u3
ii  libfontconfig1       2.11.0-6.3+deb8u1
ii  libfreetype6         2.5.2-3+deb8u1
ii  libgcc1              1:4.9.2-10
ii  libgdk-pixbuf2.0-0   2.31.1-2+deb8u5
ii  libglib2.0-0         2.42.1-1+b1
ii  libgtk2.0-0          2.24.25-3+deb8u1
ii  libjpeg62-turbo      1:1.3.1-12
ii  libnspr4             2:4.12-1+debu8u1
ii  libnss3              2:3.26-1+debu8u1
ii  libpango-1.0-0       1.36.8-3
ii  libpangocairo-1.0-0  1.36.8-3
ii  libpng12-0           1.2.50-2+deb8u3
ii  libstdc++6           4.9.2-10
ii  libwebp5             0.4.1-1.2+b2
ii  libwebpdemux1        0.4.1-1.2+b2
ii  libx11-6             2:1.6.2-3
ii  libx11-xcb1          2:1.6.2-3
ii  libxcb1              1.10-3+b1
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.1-2+b2
ii  libxi6               2:1.7.4-1+b2
ii  libxml2              2.9.1+dfsg1-5+deb8u4
ii  libxrandr2           2:1.4.2-1+b1
ii  libxrender1          1:0.9.8-1+b1
ii  libxslt1.1           1.1.28-2+deb8u2
ii  libxss1              1:1.2.2-1
ii  libxtst6             2:1.2.2-1+b1
ii  x11-utils            7.7+2
ii  xdg-utils            1.1.0~rc1+git20111210-7.4

chromium recommends no packages.

Versions of packages chromium suggests:
pn  chromium-inspector  <none>
pn  chromium-l10n       <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
The apparmor profile for chromium in jessie does not work correctly,
you will need to update it (see #742829).

Best wishes,
Mike

--- End Message ---

Reply via email to