Version: 0.7 (using KDE KDE 3.1.3) Installed from: Compiled From Sources Compiler: gcc gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5) OS: Linux Just compiled 0.7 using konstruct. 0.6 compiled and worked, but 0.7 is completely broken. Choosing any plugin (e.g., aim), then account/new, then aim in wizard, says "Impossible to load protocol: AIM" (for example).
Subject: Re: [Kopete-devel] New: Plugins broken with 0.7! On Tuesday August 5 2003 17:00, nbecker@fred.net wrote: > Compiler: gcc gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5) RedCrap *sigh* > Just compiled 0.7 using konstruct. 0.6 compiled and worked, but 0.7 is > completely broken. Choosing any plugin (e.g., aim), then account/new, then > aim in wizard, says "Impossible to load protocol: AIM" (for example). start kopete in a konsole and look out for klibloader complaining, you probably installed into the wrong --prefix. Bye, Stefan aka mETz
Subject: Re: Plugins broken with 0.7! On Tuesday 05 August 2003 11:09 am, you wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=62194 > > > > > ------- Additional Comments From sgehn@gmx.net 2003-08-05 17:09 ------- > Subject: Re: [Kopete-devel] New: Plugins broken with 0.7! > > On Tuesday August 5 2003 17:00, nbecker@fred.net wrote: > > Compiler: gcc gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5) > > RedCrap *sigh* > > > Just compiled 0.7 using konstruct. 0.6 compiled and worked, but 0.7 is > > completely broken. Choosing any plugin (e.g., aim), then account/new, > > then aim in wizard, says "Impossible to load protocol: AIM" (for > > example). > > start kopete in a konsole and look out for klibloader complaining, you > probably installed into the wrong --prefix. > > Bye, Stefan aka mETz No, it was built/installed along with all of kde3.1.3, all using the same settings. I tried running from a console and saw no message when trying to load plugin. Only this at first startup (which I don't think is relevant): QObject::connect: No such slot KopeteContactListView::slotAddTemporaryContact() QObject::connect: (sender name: 'actionAddTemporaryContact') QObject::connect: (receiver name: 'unnamed') I also made sure to rerun /sbin/ldconfig after kopete was installed. I built 0.6 the exact same way on the same environment, and no pb. I also renamed ~/.kde/apps/kopete and ~/.kde/config/kopeterc (or whatever it was called) to make sure that wasn't the pb.
Subject: Re: [Kopete-devel] Plugins broken with 0.7! On Tuesday 05 August 2003 17:20, Neal D.Becker wrote: > No, it was built/installed along with all of kde3.1.3, all using the same > settings. > > I tried running from a console and saw no message when trying to load > plugin. I think konstruct turns off debug messages by default. Could you try to check how to remove the --disable-debug flag from compilation and rebuild? It should give you a LOT more output. Even better is --enable-debug=full, but that gives a full debug build and eats disk space alive. > Only this at first startup (which I don't think is relevant): > QObject::connect: No such slot > KopeteContactListView::slotAddTemporaryContact() > QObject::connect: (sender name: 'actionAddTemporaryContact') > QObject::connect: (receiver name: 'unnamed') No, it's not relevant (though a bit unprofessional that we didn't remove it before release, hmm... :) I personally think you're mixing components of 0.6 and 0.7, but the only way to confirm that is to remove everything kopete (or at least one protocol for testing) from your $KDEDIR, make install again and check if the plugin still appears in the list at all.
Subject: Re: Plugins broken with 0.7! On Tuesday 05 August 2003 11:47 am, Martijn Klingens wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=62194 > > > > > ------- Additional Comments From klingens@kde.org 2003-08-05 17:47 ------- > Subject: Re: [Kopete-devel] Plugins broken with 0.7! > > On Tuesday 05 August 2003 17:20, Neal D.Becker wrote: > > No, it was built/installed along with all of kde3.1.3, all using the same > > settings. > > > > I tried running from a console and saw no message when trying to load > > plugin. > > I think konstruct turns off debug messages by default. Could you try to > check how to remove the --disable-debug flag from compilation and rebuild? > It should give you a LOT more output. Even better is --enable-debug=full, > but that gives a full debug build and eats disk space alive. I'm doing that now. For your reference, here is what I did: 1. Edit konstruct/apps/category.mk to comment out: CONFIGURE_ARGS += --disable-debug 2. Make clean 3. Make install I'll let you know the result in about 1 hour.
Subject: Re: Plugins broken with 0.7! On Tuesday 05 August 2003 11:47 am, you wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=62194 > > > > > ------- Additional Comments From klingens@kde.org 2003-08-05 17:47 ------- > Subject: Re: [Kopete-devel] Plugins broken with 0.7! > > On Tuesday 05 August 2003 17:20, Neal D.Becker wrote: > > No, it was built/installed along with all of kde3.1.3, all using the same > > settings. > > > > I tried running from a console and saw no message when trying to load > > plugin. > > I think konstruct turns off debug messages by default. Could you try to > check how to remove the --disable-debug flag from compilation and rebuild? > It should give you a LOT more output. Even better is --enable-debug=full, > but that gives a full debug build and eats disk space alive. > OK, I rebuilt without --disable-debug and tried it. Strangely, now it works fine. I'll rebuild again with --disable-debug and confirm it still works. If so, problem mysteriously disappeared.
I'm also having the same problem, however compiling with or without the option --disable-debug produces the same results. When I start kopete the plugins appear but regarless of the plugin I select it does not stay. I click apply and then ok to close preferences and then I open it up again and all plugins show unchecked, which is why when I try to add an account it tells me 'Impossible to load protocol:' for any protocol I choose. Any help figuring out this would be appreciated!
Subject: Re: Plugins broken with 0.7! On Tuesday 05 August 2003 02:33 pm, Raul wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=62194 > > > > > ------- Additional Comments From raul@tenkwizard.com 2003-08-05 20:33 > ------- I'm also having the same problem, however compiling with or without > the option --disable-debug produces the same results. When I start kopete > the plugins appear but regarless of the plugin I select it does not stay. I > click apply and then ok to close preferences and then I open it up again > and all plugins show unchecked, which is why when I try to add an account > it tells me 'Impossible to load protocol:' for any protocol I choose. Any > help figuring out this would be appreciated! That's EXACTLY what happened. Then I did make clean, make install, and the problem is gone. No clue.
I've done a couple of make cleans with no such luck......I thought it was maybe due to some old kopete settings but that did not help...I've done a couple of make cleans and no luck either....you can tell where it is writing to the file kopeterc the plugin name when I press apply but when I hit enter it has disappeared....it is odd...I have a friend who tried compiling it and running it and he receives the same problem....
Just to add a little more information, I have tried to compile and run kopete and have run into the same problem. Although if I run kopete as root and not another user it works! It seems there is something different for kopete when it is run on another user than root for some reason.
Just another point: I have never run kopete as root. I saw the problem running as myself.
Subject: Re: [Kopete-devel] Plugins broken with 0.7! On Wednesday 06 August 2003 22:12, Jean-Francois Gadoury wrote: > Just to add a little more information, I have tried to compile and > run kopete and have run into the same problem. Although if I run kopete as > root and not another user it works! It seems there is something different > for kopete when it is run on another user than root for some reason. Permissions? Broken umask during make install? find /wherever/kopete/is/installed -user 0 -perm 600 -o -user 0 -perm 700 might give a clue.
Ran the find and got nothing back? [jeff@localhost httpd]$ find /usr/local/kopete-0.7 -user 0 -perm 600 -o -user 0 -perm 700 [jeff@localhost httpd]$ have any ideas of anything else I can test?
Subject: Re: [Kopete-devel] Plugins broken with 0.7! On Thursday 07 August 2003 17:28, Jean-Francois Gadoury wrote: > have any ideas of anything else I can test? Actually, no :( Are you sure you have permissions to open the files as a normal user?
Subject: Re: Plugins broken with 0.7! On Thursday 07 August 2003 02:33 pm, Martijn Klingens wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=62194 > > > > > ------- Additional Comments From klingens@kde.org 2003-08-07 20:33 ------- > Subject: Re: [Kopete-devel] Plugins broken with 0.7! > > On Thursday 07 August 2003 17:28, Jean-Francois Gadoury wrote: > > have any ideas of anything else I can test? > > Actually, no :( > > Are you sure you have permissions to open the files as a normal user? Don't forget that I had the same problem symptoms, and I am absolutely certain it was not a permission problem, as I build and install all of kde as me, never as root.
Created attachment 2183 [details] Debug output when loading accounts from the wizard Could anyone who experiences this bug try one or both of the following? 1. Try loading plugins through the normal Kopete prefs instead of the Add Account wizard. Does that work ok? Are the plugins listed there? 2. Apply this patch and try again through the wizard (using a build with debug output and running from a console). Does it say anything useful (i.e. the new strings in the patch)? Martijn
is that fixed in kopete 0.7.1? if not, and if it is an issue it's a showstoper for kopete 0.7.2 please reply, thanks
*** Bug 62214 has been marked as a duplicate of this bug. ***
This seems to be a non issue now. I'm closing as FIXED since no replies have been received, and I am currently unable to reproduce this with either a 0.7.x release or current CVS. Please re-open this bug if this still occurs with the 0.7.2 release. Thanks.