Chromium is not honoring IP version priority

Bug #1792473 reported by Vasya Pupkin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
New
Undecided
Unassigned

Bug Description

Starting from version 69.0.3497.81 Chromium browser stopped honoring IP version priority configured in /etc/gai.conf. I have the following entry there:
===
# For sites which prefer IPv4 connections change the last line to
#
precedence ::ffff:0:0/96 100
===
Which should prioritize IPv4 over IPv6, but Chromium still uses IPv6 when available.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: chromium-browser 69.0.3497.81-0ubuntu0.16.04.1
ProcVersionSignature: Ubuntu 4.15.0-34.37~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: Unity
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted
DRM.card0-DP-1:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64:
 modes:
DRM.card0-DP-2:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64:
 modes:
DRM.card0-HDMI-A-1:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64:
 modes:
DRM.card0-HDMI-A-2:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64:
 modes:
DRM.card0-eDP-1:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: AP///////wANruUVAAAAABQaAQSVIhN4Aihll1lUjiceUFQAAAABAQEBAQEBAQEBAQEBAQEBtDuASnE4NEBQNmgAWMEQAAAYAAAA/gBOMTU2SENBLUVBQQogAAAA/gBDTU4KICAgICAgICAgAAAA/gBOMTU2SENBLUVBQQogANM=
 modes: 1920x1080
Date: Fri Sep 14 01:38:33 2018
Desktop-Session:
 'ubuntu'
 '/etc/xdg/xdg-ubuntu:/usr/share/upstart/xdg:/etc/xdg'
 '/usr/share/ubuntu:/usr/share/gnome:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
DetectedPlugins:

Env:
 'None'
 'None'
Load-Avg-1min: 0.32
Load-Processes-Running-Percent: 0.1%
Lsusb:
 Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp.
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 13d3:5619 IMC Networks
 Bus 001 Device 002: ID 8087:0a2b Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20HAS20T00
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic root=/dev/mapper/afaians--ub16--vg-root ro quiet
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/07/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N1VET40W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HAS20T00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrN1VET40W(1.30):bd02/07/2018:svnLENOVO:pn20HAS20T00:pvrThinkPadT570:rvnLENOVO:rn20HAS20T00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T570
dmi.product.name: 20HAS20T00
dmi.product.version: ThinkPad T570
dmi.sys.vendor: LENOVO
modified.conffile..etc.default.chromium-browser: [deleted]

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

I found two upstream bugs that look related, but they seems to imply that the problem has existed for a long time, not a regression introduced by chromium 69:

    https://bugs.chromium.org/p/chromium/issues/detail?id=516305

    https://bugs.chromium.org/p/chromium/issues/detail?id=216388

Revision history for this message
Vasya Pupkin (shadowlmd) wrote :

Yes, the problem existed in Google Chrome for quite a long time, but Chromium was not affected until the latest update.

Revision history for this message
Vasya Pupkin (shadowlmd) wrote :

At least not Ubuntu build of Chromium. Maybe there was a patch that was dropped, I don't know. But I am working with IPv6 all the time and instantly noticed the change of behavior.

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

No distro-patch related to IPv6 was dropped/added in chromium, so it must be an upstream change that triggered the change in behaviour.
Can you comment on one of the upstream bugs to try and get attention from the developers at Google?

Revision history for this message
Vasya Pupkin (shadowlmd) wrote :

https://bugs.chromium.org/p/chromium/issues/detail?id=216388 is not related to the issue I am reporting.
https://bugs.chromium.org/p/chromium/issues/detail?id=516305 - left a comment here, but I am sure Google will not care. Looks like Chromium needs a patch disabling Async DNS feature.

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.