Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
poezio
poezio
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 178
    • Issues 178
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 8
    • Merge Requests 8
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • poezio
  • poeziopoezio
  • Issues
  • #3551

Closed
Open
Opened Aug 30, 2021 by southerntofu@southerntofuContributor

Private conversation wrongfully appears as MUC private messages

When talking with a specific person, i get their resource name as tab name, and poezio seems to believe their account is a MUC according to status bar: dino.123456 from room user@jabber.systemli.org active Conversation in this tab can be two-way, but i believe no presence is shown.

I have a second tab called user correctly displaying status bar: [user@jabber.systemli.org] [|] active omemo, in which remote presence are displayed. I can post in this tab, and messages are received by the remote user, but don't receive anything back (incoming messages are displayed in the other tab).

Closing the second tab (normal user tab) seemed to take an extraordinarily long time (>1m fully unresponsive) without using much CPU/memory. Not sure what happened there.

After closing all tabs, initiating a conversation from either way does not seem to reproduce the bug. I have no idea how to reproduce it. From a quick look at windows/info_wins.py it appears the wrong kind of InfoWin was instantiated for some reason, and i have not dug deeper.

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: poezio/poezio#3551