RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1254632 - Empathy: Not able to Invite participant to conversation
Summary: Empathy: Not able to Invite participant to conversation
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: empathy
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Debarshi Ray
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-08-18 14:18 UTC by Lukas Vacek
Modified: 2020-02-11 14:34 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-11 14:34:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Lukas Vacek 2015-08-18 14:18:28 UTC
Description of problem:
Nothing happens when user tries to add participant to open conversation

Version-Release number of selected component (if applicable):
kernel-3.10.0-304.el7.x86_64
empathy-3.12.10-2.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Run empathy with at least 2 contacts
2.Open conversation with first contact
3.Click Conversation->Invite participant and choose second contact
4.Press invite

Actual results:
Nothing happens, Invite participant window is closed but second contact is not added to conversation, also no notification with invitation is not sent to second contact

Expected results:
Invitation is sent to second contact and after confirmation is added to conversation

Comment 2 Petr Schindler 2018-08-21 12:04:03 UTC
The behaviour is different now, but the problem persists.

Now after new participant is added with dialog a new chat room is open but there is no other participant (only me) and no invitation is sent. I tested this with three different accounts on xmpp.jp server.

Comment 3 customercare 2018-12-16 19:31:15 UTC
this bus is not RHEL only,it's for all Empathy versions.

Comment 4 Debarshi Ray 2020-02-11 14:34:12 UTC
RHEL 7 is approaching its Extended Life Cycle Support phase; and the application Empathy, and it's underlying messaging framework Telepathy, has been dead upstream for a while now. Given the non-critical nature of this bug, it's not fit for RHEL 7 anymore, and the Empathy/Telepathy stack isn't part of RHEL 8.

Comment 5 RHEL Program Management 2020-02-11 14:34:20 UTC
Development Management has reviewed and declined this request. You may appeal this decision by using your Red Hat support channels, who will make certain  the issue receives the proper prioritization with product and development management.

https://www.redhat.com/support/process/production/#howto


Note You need to log in before you can comment on or make changes to this bug.