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 87
    • Issues 87
    • 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
  • #775
Closed
Open
Created Nov 24, 2017 by RingBot@RingBotOwner

GNOME client crash when starting call

Issue generated from Tuleap's migration script. Originally submitted by: Anthony Léonard (aleonard)

How to reproduce :

  • Type a ringID (without “ring:” prefix) in the search bar
  • Double click on the temporary item or click on call button in conversation view
  • Boom !

It may be not necessary to omit the “ring:” prefix but it is the way it happened on my machine.

Double clicking in conversation list or clicking on call button in conversation panel gives backtraces with little differences.
backtrace.txt

Assignee
Assign to
Time tracking