Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
gajim
gajim
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 210
    • Issues 210
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 22
    • Merge Requests 22
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • gajim
  • gajimgajim
  • Issues
  • #10128

Closed
Open
Opened May 25, 2020 by Neustradamus@Neustradamus

Resource change needs account to be deactivated/reactivated

I have found a new bug:

1/ Connect an XMPP account

2/ Look the resource/priority in XMPP Account group tooltip (it is not in self-contact tooltip)

3/ Disconnect the account

4/ Go to Settings of same XMPP account and changes the resource name "gajim" by "gajim.test" (for example), close the Settings window

5/ Reconnect the same XMPP account

6/ Look the resource/priority in XMPP Account group tooltip (it is not in self-contact tooltip) : It is always same, the old resource name (not the new resource name)

PS : If we change the resource name with a connected XMPP account, and when we close the Settings window, there is a Re-login request dialog window, if we Re-Login, after the reconnection, the resource name has been changed.

Edited Sep 08, 2020 by Daniel Brötzmann
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gajim/gajim#10128