Bug 210793 - reconnect automatically on boot and after resume from s2ram
Summary: reconnect automatically on boot and after resume from s2ram
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (show other bugs)
Version: 0.80.2
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
: 215901 253184 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-10-16 16:14 UTC by Elmar Stellnberger (AT/K)
Modified: 2023-01-22 05:05 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Elmar Stellnberger (AT/K) 2009-10-16 16:14:51 UTC 
Version:           0.80.2 (using 4.3.1 (KDE 4.3.1) "release 3", openSUSE Factory)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.31.1-3-desktop

KDE4-Kopete should reconnect automatically on boot and after resume from s2ram. The way things are now I am always offline if I forget to connect manually.
Comment 1 Alexander Potashev 2011-01-09 22:11:03 UTC 
Duplicate of bug#253184
Comment 2 Lamarque V. Souza 2011-03-20 04:28:53 UTC 
*** Bug 253184 has been marked as a duplicate of this bug. ***
Comment 3 Lamarque V. Souza 2011-03-20 04:29:22 UTC 
*** Bug 215901 has been marked as a duplicate of this bug. ***
Comment 4 Andrew Crouthamel 2018-11-06 15:16:46 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 5 Andrew Crouthamel 2018-11-18 03:37:51 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 6 Justin Zobel 2022-12-23 00:28:11 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 7 Bug Janitor Service 2023-01-07 05:21:39 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 8 Bug Janitor Service 2023-01-22 05:05:53 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!