Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
J
jami-client-gnome
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 153
    • Issues 153
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Requirements
    • Requirements
    • List
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • savoirfairelinux
  • jami-client-gnome
  • Issues
  • #775

Closed
Open
Opened 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
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: savoirfairelinux/ring-client-gnome#775