| Summary: | Kopete stop trying to connect after few attempt, after reconnection to the internet. | ||
|---|---|---|---|
| Product: | [Unmaintained] kopete | Reporter: | Alexander <vo.zaeb> |
| Component: | Connection Status Plugin | Assignee: | Kopete Developers <kopete-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Alexander
2011-05-04 15:11:10 UTC
> https://bugs.kde.org/show_bug.cgi?id=181883#c6
> Try to reconnect harder. 3 times with 10s interval and then after
> 1,3,5,7,9,11,13,15 minutes intervals.
There are no words. Would be better if you'll set one hour timeout... or even better two, we all have plenty of time for waiting. Why do not a background check every 5 seconds? 5 seconds it is already a lot. I don't know about programming on linux, but perhaps there is a way to register a system callback for checking when network is down immediately?
For example, you can see how it works in windows clients. They don't wait for half an hour. The connection is down — status offline, once the connection has been restored — status restored immediately. Also, almost every time when internet connection is lost, my accounts going to offline not immediately. Sometimes it takes a few minutes, before I'll be able to see that I am not online. Linux Skype client has no such problems. I even don't seen when it reconnects, but kopete sent 10-15 notifications, but in the end icq and jabber accounts are not connected. 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! 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! 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! 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! 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! |