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
  • #518

Closed
Open
Created Oct 13, 2016 by RingBot@RingBotOwner

GNOME: account migration fails for disabled account

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

If the RING account is disabled, migration fails. The daemon log contains:

[1476376570.357|30155|ringaccount.cpp:1386    ] Account must be enabled and active to register, ignoring


Also, it takes \~30 secons after I see that log in the daemon for it to actual fail in the UI. Maybe it would be easier to just check before attempting migration if the account is dissabled and offer to enable it to perform the migration?

Afterwards, the account can be enabled in the settings, but the RingID remains blank (at least in the UI) even though the account registers.

Assignee
Assign to
Time tracking