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

Closed
Open
Created Apr 15, 2016 by RingBot@RingBotOwner

Got a ghost call

Issue generated from Tuleap's migration script. Originally submitted by: GDR! (gdr)

I tried Ring about a month ago, did not set it up to run at startup - installed, tested and forgot about it. I'm 100% sure I did not see its icon in the tray.

Just a few minutes ago, Ring UI showed up because number 1010 was calling me. I picked up out of curiosity, but there was no sound. My contact list is empty (because of the UI not working properly on my system) so I don't think it's someone I know calling.

This raises a major concern: how did Ring start and why was it enabled without the user's consent or any kind of UI indicator?

And a minor one: you seem to have a bug with ghost calls.

This incident was followed by apt-get purge ring so I won't be able to provide you with additional information. This behavior is very creepy for an app which markets itself as secure, private etc.

Assignee
Assign to
Time tracking