Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • J jami-client-gnome
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 88
    • Issues 88
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • savoirfairelinux
  • jami-client-gnome
  • Issues
  • #517
Closed
Open
Created Oct 12, 2016 by RingBot@RingBotOwner

GNOME: connectivity changed always called on client start

Issue generated from Tuleap's migration script. Originally submitted by: Stepan Salenikovich (ssalenik)

It seems that the "notify::primary-connection" is always emitted (at least on some sytems) after connecting to it for the first time, even if the primary connection didn't change. This results in the gnome client calling connection changed on startup each time. This isn't necessarily bad, but it causes the accounts to re-register one more time for no reason.

Assignee
Assign to
Time tracking