Bug 329904 - Telepathy duplicate a group if I rename it
Summary: Telepathy duplicate a group if I rename it
Status: RESOLVED WORKSFORME
Alias: None
Product: telepathy
Classification: Frameworks and Libraries
Component: contactlist (show other bugs)
Version: 0.7.1
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: Future
Assignee: Telepathy Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-13 06:55 UTC by Brallan Aguilar
Modified: 2023-02-07 03:55 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Separates the act of adding contact and removing contact from a group. (1.56 KB, patch)
2014-02-21 20:18 UTC, mayank
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Brallan Aguilar 2014-01-13 06:55:59 UTC
When I rename a group in Telepathy, appear it and the old group name too. Both groups have the same contacts. I have to kill telepathy process and restart it to get the expected results.

Reproducible: Always




It happened after this bug https://bugs.kde.org/show_bug.cgi?id=329901
Comment 1 mayank 2014-02-21 20:18:15 UTC
Created attachment 85265 [details]
Separates the act of adding contact and removing contact from a group.
Comment 2 mayank 2014-02-21 20:24:55 UTC
This is review request at the reviewboard https://git.reviewboard.kde.org/r/115943/.
Comment 3 Andrew Crouthamel 2018-11-11 04:33:44 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-11-21 04:31:13 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Justin Zobel 2023-01-08 22:45:00 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 6 Bug Janitor Service 2023-01-23 05:04:52 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Bug Janitor Service 2023-02-07 03:55:21 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!