[Pkg-chromium-maint] Bug#854925: closed by Michael Gilbert <mgilbert at debian.org> (Re: Bug#854925: chromium: Chromium does not start -- execv failed: No such file or directory)

Fri Feb 17 19:28:10 UTC 2017

HI, Michael,

Thank you for your answer. The problem is I have deleted the 
corresponding Chromium profile from /etc/apparmor.d/, restarted apparmor 
service and it still does not work. Please, check the output of 
aa-status below: there is no active Chromium-related profile!

alex at PCDELL:~$ sudo aa-status
[sudo] password for alex:
apparmor module is loaded.
68 profiles are loaded.
42 profiles are in enforce mode.
    /bin/netstat
    /bin/ping
    /home/alex/tor-browser_en-US/Browser/firefox
    /usr/bin/dbus-daemon//sanitized_helper
    /usr/bin/gimp-2.8
    /usr/bin/gsettings
    /usr/bin/gsettings-data-convert
    /usr/bin/gwenview
    /usr/bin/gwenview//sanitized_helper
    /usr/bin/irssi
    /usr/bin/jondo
    /usr/bin/jondo//browser_java
    /usr/bin/jondo//browser_openjdk
    /usr/bin/liferea
    /usr/bin/liferea//sanitized_helper
    /usr/bin/okular
    /usr/bin/pidgin
    /usr/bin/pidgin//launchpad_integration
    /usr/bin/pidgin//sanitized_helper
    /usr/bin/pulseaudio
    /usr/bin/skype
    /usr/bin/totem
    /usr/bin/totem-audio-preview
    /usr/bin/totem-video-thumbnailer
    /usr/bin/transmission-qt
    /usr/lib/cups/backend/cups-pdf
    /usr/lib/firefox-esr/firefox-esr
    /usr/lib/firefox-esr/firefox-esr//sanitized_helper
    /usr/lib/icedove/icedove
    /usr/lib/libvirt/virt-aa-helper
    /usr/sbin/apt-cacher-ng
    /usr/sbin/avahi-daemon
    /usr/sbin/cups-browsed
    /usr/sbin/cupsd
    /usr/sbin/cupsd//third_party
    /usr/sbin/dnsmasq
    /usr/sbin/ntpd
    /usr/sbin/tcpdump
    /usr/{sbin/traceroute,bin/traceroute.db}
    firejail-default
    gst_plugin_scanner
    system_tor
26 profiles are in complain mode.
    /sbin/klogd
    /sbin/syslog-ng
    /sbin/syslogd
    /usr/bin/dbus-daemon
    /usr/bin/dbus-daemon//null-1
    /usr/bin/dbus-daemon//null-1//null-2
    /usr/bin/dbus-daemon//null-3
    /usr/bin/dbus-daemon//null-4
    /usr/bin/dbus-daemon//null-4//null-5
    /usr/bin/dbus-daemon//null-4//null-5//null-6
    /usr/bin/dbus-daemon//null-7
    /usr/bin/dbus-daemon//null-8
    /usr/bin/dbus-daemon//null-9
    /usr/bin/dbus-daemon//null-a
    /usr/bin/dbus-daemon//null-b
    /usr/bin/dbus-daemon//null-c
    /usr/bin/dbus-daemon//null-d
    /usr/lib/gvfs/gvfsd
    /usr/sbin/dovecot
    /usr/sbin/identd
    /usr/sbin/mdnsd
    /usr/sbin/nmbd
    /usr/sbin/nscd
    /usr/sbin/smbd
    /usr/sbin/smbldap-useradd
    /usr/sbin/smbldap-useradd///etc/init.d/nscd
27 processes have profiles defined.
10 processes are in enforce mode.
    /usr/bin/jondo//browser_openjdk (1635)
    /usr/bin/liferea (1894)
    /usr/bin/skype (1674)
    /usr/lib/firefox-esr/firefox-esr (24538)
    /usr/lib/icedove/icedove (25537)
    /usr/sbin/avahi-daemon (764)
    /usr/sbin/avahi-daemon (839)
    /usr/sbin/cups-browsed (846)
    /usr/sbin/cupsd (845)
    /usr/sbin/ntpd (837)
17 processes are in complain mode.
    /usr/bin/dbus-daemon (767)
    /usr/bin/dbus-daemon (1234)
    /usr/bin/dbus-daemon (5992)
    /usr/bin/dbus-daemon (6935)
    /usr/bin/dbus-daemon (21295)
    /usr/bin/dbus-daemon//null-3 (1342)
    /usr/bin/dbus-daemon//null-4 (1898)
    /usr/bin/dbus-daemon//null-4//null-5 (1902)
    /usr/bin/dbus-daemon//null-4//null-5//null-6 (1905)
    /usr/bin/dbus-daemon//null-7 (1920)
    /usr/bin/dbus-daemon//null-8 (5962)
    /usr/bin/dbus-daemon//null-9 (5969)
    /usr/bin/dbus-daemon//null-a (5973)
    /usr/bin/dbus-daemon//null-b (5978)
    /usr/bin/dbus-daemon//null-c (5982)
    /usr/bin/dbus-daemon//null-d (31853)
    /usr/lib/gvfs/gvfsd (1926)
0 processes are unconfined but have a profile defined.

Also, I have created apparmor profiles for many other applications in 
Jessie from scratch -- including Akregator, Dropbox, Filezilla, 
Firefox-ESR, Icedove, JonDo, Liferea, Owncloud Client, Skype, Tor 
Browser Bundle, Transmission-Qt, among others -- and I have always 
managed to make them work after a little effort of study and review. 
This definitely does not seem a simple profile bug issue.

Thank you again for your attention,

Alexei

Às 01:00 de 17-02-2017, Debian Bug Tracking System escreveu:
> This is an automatic notification regarding your Bug report
> which was filed against the chromium package:
>
> #854925: chromium: Chromium does not start -- execv failed: No such file or directory
>
> It has been closed by Michael Gilbert <mgilbert at debian.org>.
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Michael Gilbert <mgilbert at debian.org> by
> replying to this email.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-chromium-maint/attachments/20170217/45d17588/attachment.html>