hi
after my daily cooker update, Licq suddently doesnt work anymore.
the gtk_gui and gnome_gui plugins coredumps when started
the kde-gui and qt-gui plugins gives the folowing error:
licq: relocation error: /usr/lib/libXft.so.2: undefined symbol: FcInit
best regards
Kim
http://download.sourceforge.net/licq/licq-1.2.3.tar.bz2
--
Regards // Oden Eriksson, Deserve-IT.com
--- licq.spec 2002-08-26 14:32:00.0 +0200
+++ licq.spec.oden 2003-01-09 14:48:58.0 +0100
@@ -1,8 +1,8 @@
%define name licq
-%define version 1.2.0a
+%define version 1.2.3
# needed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On November 20, 2002 16:27 pm, andre wrote:
On Tuesday 19 November 2002 08:20, Vox wrote:
This time J.P. Pasnak [EMAIL PROTECTED]
becomes daring and writes:
!,
Anyone else having a problem with LICQ w/kde-gui pinning the
processor
On Tuesday 19 November 2002 08:20, Vox wrote:
This time J.P. Pasnak [EMAIL PROTECTED]
becomes daring and writes:
!,
Anyone else having a problem with LICQ w/kde-gui pinning the processor
with the Set AutoResponse window stuck open? Cookered right up...
maybe a problem with new
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
!,
Anyone else having a problem with LICQ w/kde-gui pinning the processor
with the Set AutoResponse window stuck open? Cookered right up...
maybe a problem with new libqt3?
- --
Live fast, die young,
you're sucking up my bandwidth.
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On November 18, 2002 23:26 pm, J.P. Pasnak wrote:
!,
Anyone else having a problem with LICQ w/kde-gui pinning the
processor with the Set AutoResponse window stuck open? Cookered
right up... maybe a problem with new libqt3?
That should
This time J.P. Pasnak [EMAIL PROTECTED]
becomes daring and writes:
!,
Anyone else having a problem with LICQ w/kde-gui pinning the processor
with the Set AutoResponse window stuck open? Cookered right up...
maybe a problem with new libqt3?
I am, tho not with the autoresponse,
hello after catching up with cooker on yesterday ( 7th Nov.) licq when
put in away mode pops up the away message dialog box and stops responding
with cpu usage at 99% and does not resplod to any click on close or cancel
buttons only way out is to close down licq. this only started since
I second this, although it's freezing for me while I'm
gone, so I don't know exactly what's triggering it. I
guess we should probably report this to Licq though.
I wonder if Qt did it.
--- parag shah [EMAIL PROTECTED] wrote:
hello after catching up with cooker on yesterday (
7th Nov.) licq
Geoffrey Lee [EMAIL PROTECTED] writes:
fcntl: No locks available
Licq Segmentation Violation Detected.
Backtrace:
/lib/i686/libpthread.so.0 [0x4012ce55]
Attempting to generate core file.
hmm I don't have this problem, can you tell me how to reproduce this?
Note: the backtrace it goes
Hi,
When starting licq crashes with this error:
Loading required GL library /usr/X11R6/lib/libGL.so.1.2
Licq Segmentation Violation Detected.
Backtrace:
/lib/i686/libpthread.so.0 [0x40142e55]
Attempting to generate core file.
licq-1.2.0a-4mdk
I have seen this problem one time on this list,
sorry.. i didn't have the licq-kde package installed
--
Mr. Jeremy Salch -- Network Administrator
Granbury.com Inc.
[EMAIL PROTECTED] -- cooker mailling list e-mail
www.granbury.com -- Business website
[salch@tblx-p salch]$ licq -p kde-gui
05:36:07: [WRN] Licq: Ignoring stale lockfile (pid 5637)
05:36:07: [ERR] Unable to load plugin (kde-gui):
/usr/lib/licq/licq_kde-gui.so: cannot open shared object file: No such file
or directory.
[salch@tblx-p salch]$
--
Mr. Jeremy Salch -- Network
I have just freshened to latest cooker and when I try and run licq from
the menu, it doesn't start. When I call it from a terminal, it runs but
I get this:
[root@host root]# licq
23:25:00: [WRN] Licq: Ignoring stale lockfile (pid 26053)
I have to keep the terminal open for it to stay running
On Mon, Aug 26, 2002 at 11:27:43PM +1200, [EMAIL PROTECTED] wrote:
I have just freshened to latest cooker and when I try and run licq from
the menu, it doesn't start. When I call it from a terminal, it runs but
I get this:
[root@host root]# licq
23:25:00: [WRN] Licq: Ignoring stale
--- Han [EMAIL PROTECTED] wrote:
Let's put it this way. Licq _is_ broken. I know
nothing about coding but
boy did I see funny thing during the compiling on
either OpenBSD and
Mandrake. It is a sheer miracle it works at all on
mandrake.
I don't even think it should be in cooker, it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On August 17, 2002 10:09 am, David Walser wrote:
--- Han [EMAIL PROTECTED] wrote:
Let's put it this way. Licq _is_ broken. I know
nothing about coding but
boy did I see funny thing during the compiling on
either OpenBSD and
Mandrake. It
Op Saturday 17 August 2002 19:28, schreef iemand (J.P. Pasnak waarschijnlijk):
1.2.0a works great, and LICQ _is_ IMNSHO, the best ICQ client.
CenterICQ rulez :)
Sorry, had to do that, or that big red guy without pants would have knocked
me on the head with a frying pan... I'll go to sleep
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
!,
# urpmi licq
installing /var/cache/urpmi/rpms/licq-1.2.0-2mdk.i586.rpm
Installation failed:
libstdc++.so.5(GLIBCPP_3.1) is needed by licq-1.2.0-2mdk
I'll assume that it needs to be rebuilt, but doing so myself ended up
with a package
--- J.P. Pasnak [EMAIL PROTECTED] wrote:
# urpmi licq
installing
/var/cache/urpmi/rpms/licq-1.2.0-2mdk.i586.rpm
Installation failed:
libstdc++.so.5(GLIBCPP_3.1) is needed by
licq-1.2.0-2mdk
I'll assume that it needs to be rebuilt, but doing
so myself ended up
with a package
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On August 16, 2002 19:14 pm, David Walser wrote:
--- J.P. Pasnak [EMAIL PROTECTED] wrote:
# urpmi licq
installing
/var/cache/urpmi/rpms/licq-1.2.0-2mdk.i586.rpm
Installation failed:
libstdc++.so.5(GLIBCPP_3.1) is needed by
It needs to be upgraded to 1.2.0a, 1.2.0 is broken in
other ways also. Geoff Lee (aka snailtalk) said he
was going to do it, but it appears he is on vacation now.
Thanks. Maybe I'll try slipping the 1.2.0a code into the spec file,
and see if that works.
uhh, no I've just not
--- Geoffrey Lee [EMAIL PROTECTED] wrote:
It needs to be upgraded to 1.2.0a, 1.2.0 is
broken in
other ways also. Geoff Lee (aka snailtalk) said
he
was going to do it, but it appears he is on
vacation now.
Thanks. Maybe I'll try slipping the 1.2.0a code
into the spec file,
On Sat, Aug 17, 2002 at 03:24:59AM +0200, Danny Tholen wrote:
I can upload it again to incoming but I think it will get ignored untill geoff is
back anyway.
well it's compiling as we speak :)
-- G.
--- Geoffrey Lee [EMAIL PROTECTED] wrote:
well it's compiling as we speak :)
/me gives Geoff a hug :o)
__
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com
Just compile it yourself :) I just couldn't wait myself so I did.
On Friday 16 August 2002 09:54 pm, David Walser wrote:
--- Geoffrey Lee [EMAIL PROTECTED] wrote:
It needs to be upgraded to 1.2.0a, 1.2.0 is
broken in
other ways also. Geoff Lee (aka snailtalk) said
he
I probably should have, though I kinda wanted it to be
in official Cooker. In the meantime I shut down my
test box during a thunderstorm and just haven't
bothered to turn it back on again. Using an older
Licq that works fine on my production workstation,
will switch back to the test machine
On Fri, Aug 16, 2002 at 10:07:18PM -0400, Jason Straight wrote:
Just compile it yourself :) I just couldn't wait myself so I did.
I'm having the followin gissue rebuilding gtk+licq:
user_info_dialog.cpp: In function `int fill_in_licq_info(GtkWidget*,
long unsigned int)':
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On August 16, 2002 19:35 pm, Geoffrey Lee wrote:
On Sat, Aug 17, 2002 at 03:24:59AM +0200, Danny Tholen wrote:
I can upload it again to incoming but I think it will get ignored
untill geoff is back anyway.
well it's compiling as we speak :)
David Walser ([EMAIL PROTECTED]) wrote:
--- J.P. Pasnak [EMAIL PROTECTED] wrote:
[snip: licq seems broken]
I'll assume that it needs to be rebuilt, but doing so myself ended
up with a package that segfaults.
It needs to be upgraded to 1.2.0a, 1.2.0 is broken in other ways also.
Hi, not trying to be impatient, but I'm just wondering
if a Licq 1.2.0a package is heading our way. Thanks.
__
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 02 August 2002 04:37, Geoffrey LEE wrote:
I was going to do it, but it didn't compile of ot the box. I needs a patch
for the vector.h configure test.
oops sorry, had to compile for mandrake-club so figured I could redo the cooker rpm as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I uploaded a new licq (1.2.0a).
This one includes the missing files that were absent from 1.2.0.
Danny
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
Here is a diff, problem should be obvious:
--- licq-1.1.0-0.9mdk.list 2002-07-30
11:08:12.0 -0400
+++ licq-1.2.0-2mdk.list2002-07-30
11:07:20.0 -0400
-1,34 +1,31
/usr/bin/licq
/usr/bin/licq-ssl
-/usr/bin/viewurl-lynx.sh
-/usr/bin/viewurl-ncftp.sh
On Tue, Jul 30, 2002 at 11:37:19AM -0700, David Walser wrote:
Some lines removed from the %files part of the spec
between 1.1.0-0.10mdk and 1.2.0-1mdk (shown here:
http://cvs.mandrakesoft.com/cgi-bin/cvsweb.cgi/SPECS/licq/licq.spec.diff?r1=1.66r2=1.67
) explains some of it, but it still
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On July 27, 2002 08:11 am, Maks Orlovich wrote:
On Saturday 27 July 2002 10:08 am, you wrote:
plugin's code... An important question to ask is thus: what version
of the glibc package do you have installed?
[pasnak@neo pasnak]$ rpm -qa|grep glibc
The bug at sourceforge got closed saying it's fixed.
I'll see when I update my Cooker when the gcc 3.2
updates are done (hope somebody says something).
--- J.P. Pasnak [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On July 27, 2002 08:11 am, Maks Orlovich wrote:
Hi,
On July 27, 2002 08:11 am, Maks Orlovich wrote:
On Saturday 27 July 2002 10:08 am, you wrote:
plugin's code... An important question to ask is thus: what version
of the glibc package do you have installed?
[pasnak@neo pasnak]$ rpm -qa|grep glibc
glibc-2.2.5-14mdk
On Sunday 28 July 2002 06:22 am, Gwenole Beauchesne wrote:
Hi,
On July 27, 2002 08:11 am, Maks Orlovich wrote:
On Saturday 27 July 2002 10:08 am, you wrote:
plugin's code... An important question to ask is thus: what version
of the glibc package do you have installed?
[pasnak@neo
On Saturday 27 July 2002 10:08 am, you wrote:
On July 26, 2002 07:49 am, Maks Orlovich wrote:
On Friday 26 July 2002 04:51 am, Geoffrey Lee wrote:
I thought was hi-color KDE, but going in and switching it
helped. And if I switch it to KDE Default, it fails with:
fcntl: Bad
The licq errors happen when the kde-style is set to default.
If the style is changed to hi-color KDE then the problem goes away.
The problem is now pretty easy to replicate by changing style in the kde
control panel and trying to restart licq with -p qt-gui.
--
Brandon Long
[EMAIL PROTECTED]
[walser@mario walser]$ licq
00:09:20: [WRN] Licq: Ignoring stale lockfile (pid
31970)
00:09:23: [ERR] IniFile: Warning, failed to find key.
File= /home/walser/.licq/licq.conf
Section = [groups]
Key = Group1.id
00:09:23: [ERR] IniFile:
fcntl: No locks available
Licq Segmentation Violation Detected.
Backtrace:
/lib/i686/libpthread.so.0 [0x4012ce55]
Attempting to generate core file.
hmm I don't have this problem, can you tell me how to reproduce this?
Note: the backtrace it goes here is going to be inaccurate, but it
I re-installed my entire system, wondering if there might be some decaying rpm
matter from unremoved rpm's from pre 8.2 still messing things up. I still
have the problem on fresh install, I did notice though that I can run licq
with qt-gui as root, so it's a perms problem apparently but I
On Wed, Jul 17, 2002 at 08:20:52AM -0400, Jason Straight wrote:
I re-installed my entire system, wondering if there might be some decaying rpm
matter from unremoved rpm's from pre 8.2 still messing things up. I still
have the problem on fresh install, I did notice though that I can run licq
Hrm - nothing there.
Here's the strace tail from mine failing licq -p qt-gui as normal user though.
open(/home/junfan/.licq/owner.uin, O_RDONLY) = 10
fstat64(10, {st_mode=S_IFREG|0600, st_size=1044, ...}) = 0
read(10, \n[user]\nAlias = Lee Jun Fan\nPass..., 1044) = 1044
close(10)
I don't know about this one. The guy sitting next to me got his working, we
still aren't sure how but licq is coreing with the qt plugin, console works.
I get the same results compiling licq cvs or snapshot myself on my system.
I'm not sure what to point my finger at.
licq-kde-1.1.0-0.8mdk
On Tue, Jul 16, 2002 at 09:40:57AM -0400, Jason Straight wrote:
I don't know about this one. The guy sitting next to me got his working, we
still aren't sure how but licq is coreing with the qt plugin, console works.
I get the same results compiling licq cvs or snapshot myself on my system.
On Tue, 2002-07-16 at 09:39, Geoffrey Lee wrote:
On Tue, Jul 16, 2002 at 09:40:57AM -0400, Jason Straight wrote:
I don't know about this one. The guy sitting next to me got his working, we
still aren't sure how but licq is coreing with the qt plugin, console works.
I get the same results
that works and then stop, copy back the old history / contact list (I assume you
must want that back!), reload licq and see if that helps.
Change the ~/.licq/licq.conf to use the kde-gui plugin instead of
qt-gui.
Uhh, no, I can personally say that the qt-gui works.
-- G.
hehe, maybe it's time for a re-install. I've been running cooker since pre
8.2. I verfied all the RPM's like glibc, libstdc++, licq, qt, etc... and
nothing came up as changed.
On Tuesday 16 July 2002 10:51, Geoffrey Lee wrote:
that works and then stop, copy back the old history / contact
On Tuesday 16 July 2002 17:03, Brad Felmey wrote:
Change the ~/.licq/licq.conf to use the kde-gui plugin instead of
qt-gui.
I get a core if I use kde-gui plugin (licq -p kde-gui) and not if I use
qu-gui plugin...
I'm using licq and qt/kde form cooker.
Licq Segmentation Violation Detected
) and not if I use
qu-gui plugin...
I'm using licq and qt/kde form cooker.
Licq Segmentation Violation Detected.
Backtrace:
licq(licq_handle_sigsegv+0xca) [0x80bca8a]
/lib/libpthread.so.0 [0x4012e5bb]
/lib/libc.so.6 [0x4026b478]
/lib/libc.so.6(__libc_free+0xb8) [0x402bdbe8]
/usr/X11R6/lib/X11/locale
On Tue, Jul 16, 2002 at 07:09:31PM -0400, Jason Straight wrote:
hrm - the only thing that works here is console licq
I really can't reproduce it on cooker.
Someone who can give me a reliable way to reproduce this, it would be
appreciated.
-- G.
Hi,
Could the configure stuff in the licq package please be changed so it will
build on ML8.2 too?
[snip]
checking for X11/extensions/scrnsaver.h... yes
checking for QT libraries... yes, lib: -lqt-mt in /usr/lib/qt2/lib
checking for QT includes... /usr/lib/qt2/include
checking for QT = 2.1...
Hi,
Sorry if this is OT, but you know how it is...
Everytime I start X this has changed in the licq.conf file since my last X
session:
[plugins]
NumPlugins = 0
Plugin1 = qt-gui
It should be:
[plugins]
NumPlugins = 1
Plugin1 = qt-gui
I wonder if anyone else has noticed this..., is it a bug?
It should be:
[plugins]
NumPlugins = 1
Plugin1 = qt-gui
Not sure but yes it should be one, Im using the CVS and that doesn't happen.
- g.
On Wednesdayen den 10 April 2002 11.18, Geoffrey Lee wrote:
It should be:
[plugins]
NumPlugins = 1
Plugin1 = qt-gui
Not sure but yes it should be one, Im using the CVS and that doesn't
happen.
licq refuses to start if I don't manually add the 1. And this happens at
every new X
On Wednesday 10 April 2002 04:02 pm, you wrote:
On Wednesdayen den 10 April 2002 11.18, Geoffrey Lee wrote:
It should be:
[plugins]
NumPlugins = 1
Plugin1 = qt-gui
Not sure but yes it should be one, Im using the CVS and that doesn't
happen.
licq refuses to start if I don't
can find here:
https://kenobi.mandrakesoft.com/~snailtalk/RPM
Iv'e just tested to sent Messages with umlauts to german friens of mine,
with your LICQ version but it seems 8Bit support is totally screwed up.
The pulldown menu says I am using ISO-8859-1.
I heard from the Licq
Es schrieb Geoffrey Lee:
can find here:
https://kenobi.mandrakesoft.com/~snailtalk/RPM
Iv'e just tested to sent Messages with umlauts to german friens of mine,
with your LICQ version but it seems 8Bit support is totally screwed up.
The pulldown menu says I am using
Am 2001-11-29, um 20:52:24 (+1100) schrieb Geoffrey Lee:
[p.s. I assume that when you receive such a message you also get garbled
characters? Or not?]
Correct, I only recieve 7 bit:
Nachricht from cahei
Wed Nov 28 10:58:47 2001 []
The pulldown menu says I am using ISO-8859-1.
I heard from the Licq author this pulldown might disappear soon since v8 uses
utf-8 as I understand.
What happens if you try and send in utf-8?
Oh. Urrrgh. Righteo. I'll check to see what can be done.
It looks like that you will
Hi,
Es schrieb Geoffrey:
I have taken the time to compile a V8_BRANCH enabled Licq package, which you
can find here:
https://kenobi.mandrakesoft.com/~snailtalk/RPM
Iv'e just tested to sent Messages with umlauts to german friens of mine,
with your LICQ version but it seems 8Bit
On Sat, Nov 24, 2001 at 03:23:47PM +0100, Oden Eriksson wrote:
On Saturdayen den 24 November 2001 05.00, Geoffrey Lee wrote:
https://kenobi.mandrakesoft.com/~snailtalk/RPM
Also you may want to use this too:
-
When attempting to install licq-1.0.3-14mdk I get the error:
installing /var/cache/urpmi/rpms/licq-1.0.3-14mdk.i586.rpm
error: unpacking of archive failed on file /usr/share/licq/qt-gui/dock.console: cpio:
rename failed - Is a directory
This occcurs on 2 different systems.
Charles
On Sun, Oct 21, 2001 at 07:50:26AM -0400, Charles A Edwards wrote:
When attempting to install licq-1.0.3-14mdk I get the error:
installing /var/cache/urpmi/rpms/licq-1.0.3-14mdk.i586.rpm
error: unpacking of archive failed on file /usr/share/licq/qt-gui/dock.console:
cpio: rename failed -
licq-kde-1.0.3-13mdk
licq-1.0.3-13mdk
From the plugins menu, trying to load the kde plugin causes licq to crash.
Licq Segmentation Violation Detected.
Backtrace:
licq(licq_handle_sigsegv+0x84) [0x1004f908]
/lib/libpthread.so.0(pthread_kill+0x1c8) [0xfe4d0bc]
[0x7f3fea18]
/* snip */
It could be it seems.
Don't you think strange that Licq crashs always (and only) when trying
to change message type?
Yes.
It seems that licq was not doing proper type casting.
www.memtest86.com or stop overclocking your processor.
If it happens at the same place every
Sylvain OBEGI ([EMAIL PROTECTED]) wrote:
Signal 11
Google on signal 11 and behold it's not a software mistake.
www.memtest86.com or stop overclocking your processor.
Cya, Han.
On dim, 2001-09-16 at 10:57, Han wrote:
Sylvain OBEGI ([EMAIL PROTECTED]) wrote:
Signal 11
Google on signal 11 and behold it's not a software mistake.
It could be it seems.
Don't you think strange that Licq crashs always (and only) when trying
to change message type?
Sylvain OBEGI wrote:
On dim, 2001-09-16 at 10:57, Han wrote:
Sylvain OBEGI ([EMAIL PROTECTED]) wrote:
Signal 11
Google on signal 11 and behold it's not a software mistake.
It could be it seems.
Don't you think strange that Licq crashs always (and only) when trying
to change message type?
On Mon, May 21, 2001 at 08:41:42AM -0700, SI Reasoning wrote:
I do use latest, except when bug reports scream not
to.
No clue at all, as it doesn't happen here ... sorry. :(
But if you do want this debugged, I would suggest that you try the 'standard'
say to debug. Try running with strace
I do use latest, except when bug reports scream not
to.
--- Geoffrey Lee [EMAIL PROTECTED] wrote:
On Sun, May 20, 2001 at 12:53:22PM -0700, SI
Reasoning wrote:
More clue it happened again. This time it
happened
when there was no konqueror running and I again
clicked on yahoo
On Sat, May 19, 2001 at 07:41:34PM -0700, SI Reasoning wrote:
the kde plugin from contrib... It is probably where
the problem is... but it is so nice to have the
dockable icon!
What? Are you sure?
The KDE plugin for Licq is in /main.
--
Geoffrey Lee [EMAIL PROTECTED]
李長風
licq-kde-1.0.3-5mdk
is what I am using... I think I plucked it from
contrib but could be wrong. It was packaged by you
though. The only reason I think it might be that
plugin is when it segfaults and I try to exit licq...
the docked flower is half there. I have to run a
killall licq to fully exit
One possible clue. The latest time licq crashed was
when I opened my yahoo email using yahoo messenger's
alert linked to konqueror alpha. I do this often
though and licq does not crash everytime I do it.
--- Geoffrey Lee [EMAIL PROTECTED] wrote:
On Sat, May 19, 2001 at 07:41:34PM -0700, SI
More clue it happened again. This time it happened
when there was no konqueror running and I again
clicked on yahoo messengers email alert and it opened
konqueror alpha and licq segfaulted.
--- SI Reasoning [EMAIL PROTECTED] wrote:
One possible clue. The latest time licq crashed was
when I
the kde plugin from contrib... It is probably where
the problem is... but it is so nice to have the
dockable icon!
kded is a different issue
--- Geoffrey Lee [EMAIL PROTECTED] wrote:
On Fri, May 18, 2001 at 03:40:05PM -0700, SI
Reasoning wrote:
licq seems to keep crashing on me... and I
licq seems to keep crashing on me... and I keep having
problems with a kded race (from root) that I have to
do a full KILL on.
=
SI Reasoning
[EMAIL PROTECTED]
gnupg/pgp key id 035213BC
__
Do You Yahoo!?
Yahoo! Auctions - buy the things you
On Fri, May 18, 2001 at 03:40:05PM -0700, SI Reasoning wrote:
licq seems to keep crashing on me... and I keep having
problems with a kded race (from root) that I have to
do a full KILL on.
What plugin are you using? I am using the latest ones from cooker and it
is working ..
--
When i tryed to save licq configs it said that there is no section
[floaties] in ~/.licq/licq-qt.conf
--
óÌÕÈÉ Ï ÍÏÅÊ ÓÍÅÒÔÉ ÎÅÓËÏÌØËÏ ÐÒÅÕ×ÅÌÉÞÅÎÎÙ.
On Fri, May 04, 2001 at 06:01:12PM -0400, Yura Gusev wrote:
When i tryed to save licq configs it said that there is no section
[floaties] in ~/.licq/licq-qt.conf
Can you tell me what menubox that you checked / unchecked etc so I can
try and reproduce ..
--
Geoffrey Lee [EMAIL PROTECTED]
On Tuesday 24 April 2001 08:37, Geoffrey Lee wrote:
Yo, can you make it unified diff?
Foobar :p. *unified* diff, ok, here it is. should have RTFI (read the ...
info), mea culpa
Michel
--- licq.spec.old Tue Apr 24 02:28:17 2001
+++ licq.spec Tue Apr 24 06:18:04 2001
@@ -1,7 +1,7 @@
)
(which all provide licq-plugin, and require licq-base)
Would that work?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Geoffrey Lee
Sent: Saturday, March 17, 2001 4:57 AM
To: [EMAIL PROTECTED]
Subject: Re: Re: [Cooker] licq qt-gui plugin question
On Sat
On Sun, Mar 18, 2001 at 12:15:40PM -0600, Aaron Cohen wrote:
I think perhaps the best way to do this would be to split licq up into:
licq-base (which provides licq-base, requires licq-plugin)
and
licq-plugin-qt-with-kde
licq-plugin-qt-no-kde
licq-plugin-console
: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Geoffrey Lee
Sent: Sunday, March 18, 2001 12:46 PM
To: [EMAIL PROTECTED]
Subject: Re: Re: [Cooker] licq qt-gui plugin question
On Sun, Mar 18, 2001 at 12:15:40PM -0600, Aaron Cohen wrote:
I think perhaps the best way to do this would be to split
However:
A plugin is *required* for licq to work. If I split it up and only
licq-base
gets installed which requires licq-plugin then how will someone know
which plugin to install? Then again, if I split it up into licq-base
and then have it require the default no-KDE Qt plugin then there is
no
It's a compile time flag unfortunately, Con :\
-Original Message-
Could you not include two plugins in the base file and have a
different
menu entry for kde versus the rest of the wms?
__
Get your free
I got it working on my Cooker system. The --with-kde option goes on the
./configure line for qt-gui and you have to have the kde-devel rpm installed.
The only difference AFAIK is the docking behavior. But to me that is almost
vital for an ICQ client. Maybe if the user selects KDE during
On Sat, Mar 17, 2001 at 04:43:11AM -0600, Stephen Magill wrote:
I got it working on my Cooker system. The --with-kde option goes on the
./configure line for qt-gui and you have to have the kde-devel rpm installed.
The only difference AFAIK is the docking behavior. But to me that is almost
I never quite understood why licq which runs the qt-gui plugin by
default
doesn't dock in the panel in kde2+. There is a dock option but it
simply
creates another window. Am I missing something here?
__
Get your free Australian
Hello Con,
It runs the qt-gui by default because it is hard coded in to do so by
the author.
Friday, March 16, 2001, 7:12:14 AM, you wrote:
CK I never quite understood why licq which runs the qt-gui plugin by
CK default
CK doesn't dock in the panel in kde2+. There is a dock option but it
CK
The qt-gui will dock in KDE 2 if you do "configure --with-kde" when you
compile it. It worked quite well for me with Mandrake 7.2. My question is:
why isn't the licq rpm in the distribution set up this way?
On Friday 16 March 2001 09:59, you wrote:
Hello Con,
It runs the qt-gui by
Thanks I'll do it.
I agree with you. Why isn't it by default? Maybe like many of these
things as soon as they see these messages new RPMS will apper in
cooker ;-)
Original message from: Stephen Magill
[EMAIL PROTECTED]
The qt-gui will dock in KDE 2 if you do "configure --with-kde" when
you
On Sat, Mar 17, 2001 at 10:40:46AM +1000, Con Kolivas wrote:
Thanks I'll do it.
I agree with you. Why isn't it by default? Maybe like many of these
things as soon as they see these messages new RPMS will apper in
cooker ;-)
Well --with-kde will definitely make non-KDE users unhappy ...
I rpm -bb the spec file for licq after changing the spec file to compile
./configure --with-kde but no changes were noted still the same little icon
kind of like a kde1 dock icon being used in kde2. Any other suggestions
On Friday 16 March 2001 09:11 pm, you wrote:
On Sat, Mar 17, 2001 at
On Fri, Mar 16, 2001 at 10:07:34PM -0500, Salane King wrote:
I rpm -bb the spec file for licq after changing the spec file to compile
./configure --with-kde but no changes were noted still the same little icon
Are you sure? From ldd:
[...]
libGL.so.1 = /usr/X11R6/lib/libGL.so.1
I meant that as far as changes in the way it behaves. It looks like a kde1
docked icon when viewed in kde2. ie up in the upper left corner and not down
in the taskbar. Unless it can be used in kde2 the way kicq can ( which is
stll broken in cvs the last i checked) then why bother enabling it,
Just a recomendation, If you can get it to work properly then put it into
contrib instead of cooker and give people the option of downloading or not.
On Saturday 17 March 2001 12:43 am, you wrote:
I meant that as far as changes in the way it behaves. It looks like a kde1
docked icon when
1 - 100 of 160 matches
Mail list logo
