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

Closed
Open
Opened Apr 11, 2018 by Marco Cirillo@marandaContributor

Gajim doesn't properly cancel the first configuration form of a room.

Steps to reproduce the problem

Create a MUC Room, server sends status 201 and Gajim retrieves the configuration form, if I cancel the form Gajim silently dismiss it without cancelling with the server.

Expected behavior

Whenever a room is in a locked state the room owner MUST configure the new room with either the defaults, mainly requesting an instant room, or with his data. In case the owner cancels the first configuration form, Gajim should send a form cancel to the server (see 10.1, example 162) or we might end with an indefinitely locked room.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gajim/gajim#9069