Re: [Licq-main] licq kde problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 28 November 2002 09:38 pm, Brishen Viaud wrote: Any thoughts? Run 'licq -d31 -p kde-gui' from an xterm and e-mail the output of this command to the list. Jon __ Jon KeatingICQ #16325723 [EMAIL PROTECTED] GPG ID: 0x2290A71F emostar on irc.openprojects.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQE966tMld1KayKQpx8RApEjAKCta9WN1IikRXom77+KAY6te9PS8ACgjlsQ yllUAhM35RtrZbzErVSPEhE= =FIpL -END PGP SIGNATURE- --- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en ___ LICQ-Main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main
Re: [Licq-main] licq kde problems
Brishen Viaud wrote: Hi. I have been running licq for quite a few months now (1.2.0a, on a slackware 8.0 system). It seemed to crash every few days, but I would just kill the processes and start it up again. Today when it crashed, I wasn't able to get it to start up again. I tried getting rid of the .licq directory but it didn't help matters. I decided to install a new version in case some how files had been corrupted (I was getting no error messages from kde and it just wouldn't start from bash). I grabbed the latest from the CVS today and compiled it, as well as compiling the console and the qt-gui with-kde. Now I am having no problems running licq using the console, everything seems to work just fine. But when trying to start it up with kde-gui it will load for a short time, and then crash out giving the error message that it caused the signal 11 (SIGSEGV) Starting from bash (licq -p kde-gui) I get: KCrash: crashing crashRecursionCounter = 2 KCrash: Application Name = licq path = unknown pid = 23775 Any thoughts? Hi, you propably configured withouth the --with-kde switch. In this case you only rebuilded the qt-gui plugin, having the old kde-gui plugin laying around (which is incompatible with your new version of licq). try if calling licq -p qt-gui on console helps. If this works for you, then you might want to recompile the gui plugin and pass the --with-kde switch to the configure script: cd plugins/qt-gui rm config.cache (just in case) ./configure --with-kde make su -c 'make install' then call licq -p kde-gui and see if it works again. If this does not help, we need a better description of the error. Bye, Thomas --- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en ___ LICQ-Main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main
Re: [Licq-main] licq kde problems
On Fri, 29 Nov 2002, Thomas Reitelbach wrote: Brishen Viaud wrote: Hi. I have been running licq for quite a few months now (1.2.0a, on a slackware 8.0 system). It seemed to crash every few days, but I would just kill the processes and start it up again. Today when it crashed, I wasn't able to get it to start up again. I tried getting rid of the .licq directory but it didn't help matters. I decided to install a new version in case some how files had been corrupted (I was getting no error messages from kde and it just wouldn't start from bash). I grabbed the latest from the CVS today and compiled it, as well as compiling the console and the qt-gui with-kde. Now I am having no problems running licq using the console, everything seems to work just fine. But when trying to start it up with kde-gui it will load for a short time, and then crash out giving the error message that it caused the signal 11 (SIGSEGV) Starting from bash (licq -p kde-gui) I get: KCrash: crashing crashRecursionCounter = 2 KCrash: Application Name = licq path = unknown pid = 23775 Any thoughts? Hi, you propably configured withouth the --with-kde switch. In this case you only rebuilded the qt-gui plugin, having the old kde-gui plugin laying around (which is incompatible with your new version of licq). No I did make sure to configure it with the --with-kde switch. I went into my plugin directory and the only two there are console and kde-gui. I even just removed the kde ones and re installed them in case there had been some problem, but I am getting the same result. But you made me think about trying the qt-gui plugin itself. I just finished compiling it and it seems to be running just fine. So the only problem is with the kde option. It's nothing that I can't live without, but it's slightly irritating to see it working one day and then not the next. I'm not sure what else to say about my problem. There was nothing special about my last crash with my previous working version of licq. But this time it just didn't want to start. There weren't any error messages occuring when I tried to start it up, and there wasn't anything crashing, it just wouldn't actually start up. I didn't have the console plugin at the time so I couldn't check to see if it was a kde problem or not. Thanks for the help. Brishen --- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en ___ LICQ-Main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main
[Licq-main] licq kde problems
Hi. I have been running licq for quite a few months now (1.2.0a, on a slackware 8.0 system). It seemed to crash every few days, but I would just kill the processes and start it up again. Today when it crashed, I wasn't able to get it to start up again. I tried getting rid of the .licq directory but it didn't help matters. I decided to install a new version in case some how files had been corrupted (I was getting no error messages from kde and it just wouldn't start from bash). I grabbed the latest from the CVS today and compiled it, as well as compiling the console and the qt-gui with-kde. Now I am having no problems running licq using the console, everything seems to work just fine. But when trying to start it up with kde-gui it will load for a short time, and then crash out giving the error message that it caused the signal 11 (SIGSEGV) Starting from bash (licq -p kde-gui) I get: KCrash: crashing crashRecursionCounter = 2 KCrash: Application Name = licq path = unknown pid = 23775 Any thoughts? Brishen --- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en ___ LICQ-Main mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-main
