Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • J jami-daemon
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 112
    • Issues 112
    • 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-daemon
  • Issues
  • #110

Closed
Open
Created May 20, 2019 by Maxim Cournoyer@mcournoyerMaintainer

Wrong settings can cause crashes at start, or block and prevent use of client

Reproduction steps are unclear, but:

  1. There was 3 accounts configured, one SIP and two Jami
  2. I disabled both the Jami accounts.
  3. I modified the SIP account, attempting to make it use TLS

The client froze on the settings. Attempting to restart it didn't help much, the client did not come back (I presume the settings were causing the SIP account to be waiting on some event/timing out before the client would be drawn).

Eventually the client came up, but was unusable. Attempting to restart it returned me to the previous situation (client is not drawn/hung by something).

Bad settings and other events in the daemon should not block the rendering of client.

Assignee
Assign to
Time tracking