Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
G
GLib
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 936
    • Issues 936
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 59
    • Merge Requests 59
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GNOME
  • GLib
  • Issues
  • #1685

Closed
Open
Opened Feb 11, 2019 by Michael Gratton@mjog🍸Developer

Intermittent network unreachable error from GSocket connecting with non-functioning IPv6 network

Testing Geary master against Flatpak org.gnome.Sdk/x86_64/master over the last few days there's a good chance each time of geting an G_IO_ERROR_NETWORK_UNREACHABLE error from GSocket when connecting to a remote host that has both A and AAAA records, from a local host that has a functioning IPv4 interface and a configured-but-non-functional IPv6 interface. I.e. the local host is on a working IPv4 network, has "Automatic" selected under the IPv6 tab for the network (and hence has a fe80:: link-local address), but otherwise is not connected to an IPv6 network.

Since this happens often-but-intermittently for host names with both A and AAAA records (and not at all for hosts with only A records), I assume the error occurs when attempting and failing to connect to the AAAA address first, and doesn't when connecting first to the A record. Further, disabling IPv6 in the control panel seems to make it impossible to reproduce the error. Could be related to #1555 (closed), I guess?

Assignee
Assign to
2.59.3
Milestone
2.59.3 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: GNOME/glib#1685