Bug 340203 - ktp-contactlist only appears once
Summary: ktp-contactlist only appears once
Status: RESOLVED NOT A BUG
Alias: None
Product: telepathy
Classification: Frameworks and Libraries
Component: contactlist (show other bugs)
Version: 0.9.0
Platform: openSUSE Linux
: NOR major
Target Milestone: Future
Assignee: Telepathy Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-21 16:50 UTC by S
Modified: 2021-03-09 12:27 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description S 2014-10-21 16:50:47 UTC 
Hello,

This bug is for KTP 0.9.0 from openSUSE KDE:Extra. 

The first time I open ktp-contactlist, it works fine. Then, I close it, and it won't re-open again. I have tried this with the KTP Presence plasmoid enabled and also disabled, and it still acts the same. If I kill the ktp-contactlist process I can again open it one time.

Thanks for looking into it!

Reproducible: Always
Comment 1 David Edmundson 2014-10-21 16:56:01 UTC 
So the contact list stays running after you close it?
Comment 2 S 2014-10-21 16:59:35 UTC 
(In reply to David Edmundson from comment #1)
> So the contact list stays running after you close it?

Correct.

Thanks for looking into this!
Comment 3 S 2014-10-23 18:40:16 UTC 
This same bug is also present on the default openSUSE 0.8.80 version too.
Comment 4 Alexander Potashev 2015-05-05 15:33:26 UTC 
Can you please try the newest version of KTP from KDE Applications 15.04.0?

If the problem persists, please run ktp-contactlist in a terminal in GDB (just run "gdb ktp-contactlist" in terminal and enter the "run" command in GDB), then close the Contact List window as usual and after that click Ctrl+C in GDB to stop the hung up process and finally enter the "thread apply all backtrace" command to get the backtraces. We need this to understand what's going on.
Comment 5 Justin Zobel 2021-03-09 07:25:50 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.