If loading a protocol plugin when the configuration already has a configured owner, Licq crashes.
This is not a normal use case, but it should not be a problem and it has worked fine before.
Steps to reproduce:
Configure Licq with at least one account
Shut down Licq
Edit ~/.licq/licq.conf and set NumProtoPlugins=0
Start Licq
From the Account Manager, try and load the protocol again.
Actual crash is triggered by the assert at licq/src/plugin/plugininstance.cpp, line 112
Fault only happens if using 131fbba3db27ad5a658270d6a48cc78993a002aa or later.
As this is before the release of Licq 1.8.0 both master and 1.8-stable are affected.
If loading a protocol plugin when the configuration already has a configured owner, Licq crashes. This is not a normal use case, but it should not be a problem and it has worked fine before.
Steps to reproduce:
Actual crash is triggered by the assert at licq/src/plugin/plugininstance.cpp, line 112
Fault only happens if using 131fbba3db27ad5a658270d6a48cc78993a002aa or later. As this is before the release of Licq 1.8.0 both master and 1.8-stable are affected.