Berkley Packet Filter handling, error with ESET NOD32 Antivirus 4 and Chromium

Bug #1399333 reported by crysman
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

I installed ESET NOD32 Antivirus 4 Business Edition on my Xubuntu. After that, Chromium browser has stopped working ("awgh" error or something like that). According to help I've tried to use new default profile, without success. After uninstalling ESET NOD32 it has started to work again.

So I contacted ESET to tell them they've got a bug in their application. To my surprise, they replied no they had not, and, quote:
"""
...That is a bug in Berkley Packet Filter handling. SRWare Iron browser is suffering this issue, too. Other browsers do not, it is not a problem of ESET NOD32...
"""

So now I am handing it over to you, guys...

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: chromium-browser 39.0.2171.65-0ubuntu0.14.04.1.1064
ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
Uname: Linux 3.13.0-29-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Dec 4 21:09:46 2014
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationDate: Installed on 2013-10-26 (404 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to trusty on 2014-06-11 (176 days ago)
modified.conffile..etc.default.chromium.browser: [deleted]

Revision history for this message
crysman (crysman) wrote :
Chad Miller (cmiller)
Changed in chromium-browser (Ubuntu):
status: New → Incomplete
Revision history for this message
Chad Miller (cmiller) wrote :

Please attach info about the crash. At a terminal, "dmesg > attach-to-lp1399333", after you get a crash.

Revision history for this message
crysman (crysman) wrote :

dmesg log

Revision history for this message
crysman (crysman) wrote :

chromium browser debug log

Revision history for this message
crysman (crysman) wrote :

screenshot with chromium malfunction

Changed in chromium-browser (Ubuntu):
status: Incomplete → New
Chad Miller (cmiller)
Changed in chromium-browser (Ubuntu):
assignee: nobody → Chad Miller (cmiller)
importance: Undecided → Medium
summary: - Berkley Packet Filter handling bug
+ Berkley Packet Filter handling, error with ESET NOD32 Antivirus 4 and
+ Chromium
Revision history for this message
Mikhail Novosyolov (mikhailnov) wrote :

Did you try a newer kernel?
sudo apt update
sudo apt install linux-generic-lts-xenial
sudo reboot

Revision history for this message
crysman (crysman) wrote :

currently, I am not experiencing any issues (Xubuntu 16.10, system keeping up2date)

Revision history for this message
Olivier Tilloy (osomon) wrote :

Closing per last comment. Thanks for the feedback!

Changed in chromium-browser (Ubuntu):
status: New → Invalid
assignee: Chad Miller (cmiller) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.