Skip to content

GitLab

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

Closed
Open
Created Mar 23, 2016 by RingBot@RingBotOwner

LRC: QObject::connect: No such signal ConfigurationManagerInterface::incomingAccountMessage(QString,QString,QMap<QString, QString>) message

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

gnome client during runtime give the following message from qt:

QObject::connect: No such signal ConfigurationManagerInterface::incomingAccountMessage(QString,QString,QMap<QString, QString>)

from phonedirectorymodel.cpp:57

seems to be due to using the QMap<QString, QString> instead of the MapStringString typedef in the signal signature

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking