Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
J
jami-lrc
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 20
    • Issues 20
    • 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-lrc
  • Issues
  • #322

Closed
Open
Opened 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 admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: savoirfairelinux/ring-lrc#322