I'm also sad to say that I no longer consider myself an active
developer. Even though it has been fun to work on Licq, I have found it
a bit lonely at times which has lowered my motivation to continue.
If someone else is interested in actively working on Licq, I'll hang
around and help but I
On 2014-10-05 18:08, Kevin Krammer wrote:
On Saturday, 2014-10-04, 10:27:12, Anders Olofsson wrote:
Good!
I had a quick look and the only thing I don't like is that you remove
the kde-gui. Do you know if KDE will move to Qt5 as well before Jessie
releases?
It is unlikely that Jessie
I would like to drop a few features that I think is no longer worth
keeping. This is basically a question if anyone disagrees and would like
these features to stay.
- Send to multiple contacts.
The only practical usage I can see for this is spamming which shouldn't
be the main usage for Licq.
Licq 1.8.2 is a bugfix release, mainly to solve some crashes and fix a
build problem.
Download and release notes:
http://sourceforge.net/projects/licq/files/licq/1.8.2/
The Licq Team
--
---
You received this message because you are subscribed to the Google Groups Licq Development group.
To
Sorry for the delay. I cut off the beginning. I hope there is no
sensitive information in the files.
A warning would be appreciated ;-)
Thank you. It looks like the packet was status related. The packet sets
an empty away message for the contact, probably some kind of auto-away
related
I'm able to rebuild the Debian package, but I'm not able to apply the Debug
option to the rules file (attached). I still get the ' No symbol table
info available.'
messages after a crash in my backtraces.
I got the git repository and tried to compile from source, but that
failed. Please
tell me
On 2014-03-27 07:44, Thorsten Bonow wrote:
I've applied the patch and rebuild the Debian package. I've attachted the
backtrace and the console output generated by starting licq with the
'-d15' option. Hope this helps.
Thanks, but it looks like you didn't get any debug information so I
can't
Hi,
looking from your backtrace, I believe this is the same issue that was
reported as https://github.com/licq-im/licq/issues/39, however that
issue was never resolved due to lack of information.
Could you please give us some more details of the problem.
- Which version of Licq are you
Licq 1.8.1 is a bugfix release, mainly to solve build problems and some
other issues that have been fixed since Licq 1.8.0.
Download and release notes:
http://sourceforge.net/projects/licq/files/licq/1.8.1/
The Licq Team
--
---
You received this message because you are subscribed to the
I've pushed an update to make the plugin reply to introspect queries. It
seems to work in qdbusviewer so I hope I got it right.
It is usually also a good idea to provide a D-Bus introspection XML
file as part of the sources, potentially even installing it.
It is a way of documenting which
available licq methods using e.g. qdbusviewer.
// Erik
On Sat, Oct 12, 2013 at 11:34 AM, Anders Olofsson fl...@licq.org
mailto:fl...@licq.org wrote:
I've just pushed the first version of a D-Bus interface plugin for Licq.
I mainly created this as a way to display notifications from Licq
On 2013-10-12 15:15, Kevin Krammer wrote:
On Saturday, 2013-10-12, Anders Olofsson wrote:
It should just be a matter of implementing
org.freedesktop.DBus.Introspectable. I think it should be pretty easy to
add. I'll give it a try.
It is usually also a good idea to provide a D-Bus
I would really like to have better support for multiuser chats in Licq
and have thought a bit on how to make that happen.
I was thinking to start simple by just getting support for named chat
rooms and only for Jabber protocol. (Because this is what I personally
need most right now.)
When we
Licq 1.8.0 add support for multiple accounts per protocol (currently
only for MSN and Jabber) and contains several bugfixes.
Download and release notes:
http://sourceforge.net/projects/licq/files/licq/1.8.0/
The Licq Team
--
---
You received this message because you are subscribed to the
Since everything seems quiet and the master branch has some undelivered
goodies I think it's time to make a Licq 1.8.0 delivery.
As there usually is nothing happening after the release candidates are
made available, I thought this time I would just make the final delivery
at once. If anything
I think there should still be some suffix and .picture is good, so do
the switch.
And it should be enough to only change the 1.8 upgrade function. Anyone
using master will have to live with doing manual upgrades some times.
And loosing the pictures isn't a big deal anyway, they should just be
Licq 1.7.1 is a bugfix release, mainly to solve some crashes and
deadlocks that have been found in Licq 1.7.0.
Download and release notes:
http://sourceforge.net/projects/licq/files/licq/1.7.1/
The Licq Team
--
On 2013-01-02 21:58, Erik Johansson wrote:
On Tue, Jan 1, 2013 at 10:03 PM, Anders Olofssonfl...@licq.org wrote:
Instead of making each plugin handle multiple owners, is it possible
to create multiple instances of the plugin's main class instead and
bind each owner to a separate instance?
I
On 2012-12-16 17:21, Anders Olofsson wrote:
I think the console plugin needs a big maintenance work to get up to
date with Licq.
There are, for example, several parts of it that still work as if Licq
is an ICQ only client and should to be rewritten to work properly with
multiple protocols. As I
I tried to latest version and noticed that what looks like a left-over
in licq.conf under [groups]. For each group I have
GroupX.ServerId.LicqUIN=Y and GroupX.ServerId.ICQ_UIN=Y. I'm guessing
that only the second one should be there?
Yes, one of the side effects of the switch from LICQ_PPID to
I think the console plugin needs a big maintenance work to get up to
date with Licq.
There are, for example, several parts of it that still work as if Licq
is an ICQ only client and should to be rewritten to work properly with
multiple protocols. As I don't use it myself, I'm not even sure it's
The final release of Licq 1.7.0 is here.
Licq 1.7.0 contains both bugfixes and new features.
Download and release notes:
http://sourceforge.net/projects/licq/files/licq/1.7.0/
The Licq Team
--
Hi,
I've been looking into making the MSN plugin use a newer protocol
version so we can get some more features in it. But after looking at
some other clients code it seems like a lot of work just to get through
the authentication steps.
So I though, maybe it would be possible to use an
On 2012-07-29 23:04, Erik Johansson wrote:
As of 3ae13d00 (Build example config file as default) master does not
build as the source file default_config.cpp does not exist.
// Erik
default_config.cpp is generated from licq_forwarder.conf when running
cmake for forwarder plugin.
Try clearing
The final release of Licq 1.6.1 is ready
Licq 1.6.1 is a bugfix release to resolve some issues, mainly in the
Qt4-Gui plugin and the ICQ protocol.
Download and release notes:
http://sourceforge.net/projects/licq/files/licq/1.6.1/
The Licq Team
The first release candidate for Licq 1.6.1 is ready for download.
Licq 1.6.1 is a bugfix release to resolv some issues, mainly in the
Qt4-Gui plugin and the ICQ protocol.
Download and release notes:
http://sourceforge.net/projects/licq/files/licq/1.6.1/
If you find any bugs, please notify us
On 2011-11-14 21:45, Jörg Mensmann wrote:
Anders Olofssonfl...@licq.org wrote:
According to [1], the -session parameter is mandatory. Is there any
KDE documentation indicating that this should be different for KDE
applications?
I couldn't find anything in the KApplication docs. However, all
The first release candidate for Licq 1.6.0 is ready for download.
Licq 1.6.0 contains both bugfixes and new features.
Download and release notes:
http://sourceforge.net/projects/licq/files/licq/1.6.0/
If you find any bugs, please notify us by creating an Issue in github:
On 2011-08-08 00:03, Jon Keating wrote:
On Mon, Aug 8, 2011 at 12:04 AM, Anders Olofssonfl...@licq.org wrote:
741 [icq] Checking if a user is invisible doesn't work
I left it open as a TODO to investigate if it could be done using a
different method.
I believe it can be closed and if
# Group 3 - Possibly bugs #
In general, I think we should only migrate bug reports with clear and
understandable descriptions. If we can't understand the report or
reproduce the problem it will probably never get fixed. In this case I
think less is more. If we miss to migrate a bug
I have gone through the list of tickets that we had in trac and tried to
figure out what to do with them. The following is my suggestion on how
to migrate them but I would appreciate feedback on this, especially on
some of the tickets that I'm not sure about.
I've divided the tickets into 6
We are happy to announce the final release of Licq 1.5.1.
Licq 1.5.1 is bugfix release to fix some things found since the release
of Licq 1.5.0. It also adds support for away messages in the jabber
protocol.
Download and release notes:
http://sourceforge.net/projects/licq/files/licq/1.5.1/
The first release candidate for Licq 1.5.1 is ready for download.
Licq 1.5.1 is bugfix release to fix some things found since the release
of Licq 1.5.0. It also adds support for away messages in the jabber
protocol.
Download and release notes:
We are happy to announce the final release of Licq 1.5.0.
Licq 1.5.0 introduces support for Jabber protocol and a new OSD plugin.
Other changes include separate auto-logon for each account and the
possibility to override sounds per user or per group.
Package is available for download:
The first release candidate for Licq 1.5.0 is ready for download.
The big news are support for Jabber protocol and a new OSD plugin.
Licq 1.5.0 also has major changes to the plugin API and marks the end
for old Qt3 based Qt-Gui in favour of Qt4-Gui.
Package is available for download:
On 2010-06-18 14:22, M Wedin wrote:
I don't know what went wrong. I was just greeted with this message.
Wed
Firstly, I would like to point out that it generally helps to figure out
what went wrong if you include some information on which version you're
running, what you were doing when it
The final release of Licq 1.3.9 is now available.
Licq 1.3.9 is a pure bugfix release that fixes several problems found
since the release of Licq 1.3.8.
Package is available for download from SourceForge:
https://sourceforge.net/projects/licq/files/
Release notes with full changelog:
On 2010-05-01 22:10, Erik Johansson wrote:
On Fri, Apr 30, 2010 at 17:57, Anders Olofssonfl...@licq.org wrote:
I had a quick look at the packaging script and it looks like it should work
fine for the branch. However the tag script is gone so I'll have to grab an
old version and see if I can
The first release candidate for Licq 1.3.9 is ready for download.
Licq 1.3.9 is a pure bugfix release that fixes several problems found
since the release of Licq 1.3.8.
Package is available for download:
https://sourceforge.net/projects/licq/files/
Release notes:
ver...@mail.mv.ru wrote:
Hi. When i try to open message or history from one of my contacts, licq
freezing and crashes.
Hi,
Which version of Licq are you using?
Did you build it yourself or was it pre-packaged? (If packaged, which
distribution?)
What do you mean with freezing and crashes?
The first release candidate for Licq 1.3.7 is ready for download.
Licq 1.3.7 contains many bugfixes, and several new features in the
Qt4-Gui such as spell checking and configurable keyboard shortcuts.
Package is available for download:
https://sourceforge.net/projects/licq/files/
Release
It's been another year and since not much is happening right now I think
this is a good time to release Licq 1.3.7 to make some more features and
bug fixes available to our users.
I believe that the current trunk as stable enough for a release as it is
right now so unless anyone objects I
pmx wrote:
Hello
I want to suggest to add the serverless messaging http://retroshare.sf.net
to licq
both apps are Qt so they could be merged.
Regards Max
Hi,
we always welcome tips and ideas for ways to enhance Licq. However, I
wouldn't expect to see RetroShare supported in Licq anytime
Rezobezandron wrote:
Hi, build 6612 crashes after logging in and staying online for a while.
r6613 should fix that. Thanks for reporting the problem.
/Anders
I haven't been able to reproduce this with latest dev build and I cannot
find any uses of std::string in CUserView::timerEvent so I currently see
where that call comes from.
Rezobezandron wrote:
This error occurs periodically. I'm using licq v1.6 with Qt-GUI
plugin v.1.6, it also patched
1) Protocol support
I've looked a bit at the libpurple code and I'm still not sure about the
full lib but at least the protocol plugins looks usable. However it
would require implementing part of the libpurple interface in Licq (not
sure how big parts though) and it's written in C, not C++,
Anders Olofsson wrote:
With the first release candidate out, the trunk is now in code freeze
until the final 1.3.6 package has been built.
That means that until then any commits should fall into one of the
following categories:
* (Important) bugfixes.
* Translations.
* Text files, code
Ok, I think I'm starting to get everything under control now.
Nobody has commented on the release note so I guess it's approved.
However, after reading commit comments, I've only found one name to add
under acknowledgments (Sergey Kononenko). All other commits were either
done by us core
Sergey Kononenko wrote:
Thank you for acknowledgment, and I think description of my patch would
be added to release note that appearance of large amount of buddy icons
in contact list would not be big surprise for users (I hope good
surprise :) ). Description can be something like:
ICQ: Partial
Sergey Kononenko wrote:
Also about release note, would it be mentioned that from now Boost
required to build Licq?
Added.
Thanks!
/Anders
I think it's time to make a new release with all the corrections,
improvements and updates that's been added since 1.3.5 was released.
I believe the current dev version is stable and complete enough to make
a new release and give some of the additions from the last year of
development to our
Ladislav Michnovič wrote:
Hello.
I tried compiled Licq from svn (qt3 plugin) and it crashes after
submitting user UIN and password.
Atttaching backtrace files.
Regards Ladislav.
Found and fixed it (r6449).
Fetch a new svn update and it should work now.
Thanks for reporting the problem.
Roman Duriska wrote:
Thread 6 (Thread 0xb6cdab90 (LWP 11699)):
#0 0xe430 in __kernel_vsyscall ()
#1 0xb7e28bab in waitpid () from /lib/libpthread.so.0
#2 0x0811beec in licq_handle_sigabrt ()
#3 signal handler called
#4 0xe430 in __kernel_vsyscall ()
#5 0xb7bac900 in raise () from
Samuel Blomqvist wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today I got kicked out of the server and then when I try to login I get
this:
19:40:17: [SRV] Requesting logon (#15834)...
19:40:17: [SRV] Connecting to login server.
19:40:17: [SRV] Resolving login.icq.com port 5190...
Danil Y. Zagornov wrote:
Hi
Licq-daily snapshot from 20080702 don't build on the freebsd
gmake[2]: Entering directory `/tmp/licq-20080702/src'
if g++ -DLOCALEDIR=\/opt/licq-20080702/share/locale\ -DHAVE_CONFIG_H -I. -I. -I..
-Wall -Wextra -I../include -D_THREAD_SAFE
Eugene Paskevich wrote:
On Wed, 02 Jul 2008 13:33:56 +0300, Danil Y. Zagornov
[EMAIL PROTECTED] wrote:
On Wed, 2 Jul 2008 15:05:55 +0600
Danil Y. Zagornov [EMAIL PROTECTED] wrote:
Hi
I change
char* inPtr = const_castchar*(array);
to
const char* inPtr = const_castchar*(array);
in file
On fre, 2008-03-28 at 13:20 +0200, Аляксей Вар'ят wrote:
Hi all,
Please apply attached patch that included final version of belorussian
translation for the QT3 based GUI.
Committed as r6116.
On fre, 2008-03-28 at 14:27 +0200, Аляксей Вар'ят wrote:
Hi all.
Please apply attached patch
Hello, all
Please add belarussian translations for the Licq daemon.
Commited as r6076. Thanks.
Excuse me, but I found one missed phrase in my translattion. Please correct it
in SVN using attached patch. Now count of phrases in template is equal to one
in
translations.
Committed as
Jon Keating wrote:
On Monday 25 June 2007 05:25, Erik Johansson wrote:
But I have yet to see such code and gcc will print a warning when you
compile it, so I don't think it's a strong argument. On the other
hand, the documentation and readability gains you get by using NULL is
well worth it,
Jon Keating wrote:
On Sunday 24 June 2007 02:16, Erik Johansson wrote:
I would like to get started with merging some code from erijo-dev to
the newapi branch. But first I think we should agree on a common
coding style. I have updated http://trac.licq.org/wiki/CodingStyle to
reflect a
Erik Johansson wrote:
2007/6/19, flynd [EMAIL PROTECTED]:
I guess either the makefiles needs to be put back or the README.LOCALES
needs to be updated with new instructions.
Done. make merge and make clean-merge now works in qt4 branch. Even
supports installing translations :)
// Erik
Looks good but I have a few comments as well.
* Adding features to the API should not stop older plugins from loading as
long as the new API is still backwards compatible with the version
required by the plugin.
This has already been mentioned in previous replies but I think this is
On Tue, 23 Jan 2007 02:31:11 +0100, Jon Keating [EMAIL PROTECTED]
wrote:
Please do not ever change tabs/spaces on an entire file when you
commit to SVN. It makes the diff completly unreadable and
unreviewable. Can you please provide a diff of the changes you did
without the space changes so
I've made my own plugin that, when a message is received, displays the
sender's name on an external display.
The plugin works great except for one problem. When I shutdown licq, licq
never terminates. I get debug printouts from all plugins (qt-gui, msn and
my own) that they are shutting down
64 matches
Mail list logo
