Bug 130965 - Kopete automatically connects even if the option is disabled
Summary: Kopete automatically connects even if the option is disabled
Status: RESOLVED WORKSFORME
Alias: None
Product: kopete
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-17 11:38 UTC by Frédéric COIFFIER
Modified: 2006-09-17 12:43 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Frédéric COIFFIER 2006-07-17 11:38:39 UTC
Version:           0.12.1 (using KDE KDE 3.5.3)
Installed from:    Gentoo Packages
Compiler:          gcc (GCC) 4.1.1 (Gentoo 4.1.1) 
OS:                Linux

When Kopete is started, it automatically connects all account whereas the checkbox isn't checked.
In 0.12.1, I see no "connection status" plugin.
Comment 1 Roman Jarosz 2006-07-17 12:26:23 UTC
If you want connection status plugin in 0.12.1 in gentoo you have to enable connectionstatus use flag

USE="connectionstatus" emerge net-im/kopete

emerge -vp net-im/kopete will print you all available flags
Comment 2 Frédéric COIFFIER 2006-07-17 13:21:50 UTC
Thank you for this information.
But it doesn't explain why, by default, Kopete connects all accounts even if the checkbox "Automatically login" isn't checked.
Comment 3 Olivier Goffart 2006-07-26 19:45:38 UTC
I cannot reproduce.

does it connect if you type
kopete --noconnect
in the console ?
Comment 4 Frédéric COIFFIER 2006-07-28 11:27:21 UTC
I think I made the following operations :
1. I had a Kopete WITH "connectionstatus" which was ENABLED (so, automatically connection was normal)
2. I upgraded Kopete WITHOUT "connectionstatus" plugin and "Automatically login" NOT checked. But Kopete still connected automatically.

Is it possible Kopete follows the old "connectionstatus" configuration even if the plugin is no more present ? 
Comment 5 Roman Jarosz 2006-07-30 20:48:08 UTC
Do you have rsibreak program?
If yes than it's probably bug 130023
Comment 6 Olivier Goffart 2006-08-04 21:01:19 UTC
> Is it possible Kopete follows the old "connectionstatus" configuration even if the plugin is no more present ?

This is hardly possible.  The connectionstatus code need to be loaded in memory in order to operate :-)

Do you still have the problem even if you have the plugin now marked as disabled ?
Comment 7 Frédéric COIFFIER 2006-08-16 10:49:36 UTC
No : If I disabled it, it works fine (no automatic connection).

You should close this report. If one day, I succeed to reproduce the problem, I'll try to investigate it better. Thank you.
Comment 8 Olivier Goffart 2006-09-17 12:43:31 UTC
ok.