error
Luise Kunkle
A few weeks ago I encountered a fatal error, which is still with me.
I got the mask:
**************
Licq has encountered a fatal error.
Please report this error either by creating a new ticket at
http://trac.licq.org/ or by sending an e-mail to the mailing list
licq...@googlegroups.com (you must be registered to be able to post, see
http://trac.licq.org/wiki/MailingList).
To help us debug the error, please include a full description of what you
did when the error occurred. Additionally, please include the following
files (if they exist):
/home/net/.licq//licq.backtrace
/home/net/.licq//licq.backtrace.gdb
Thanks, The Licq Team
**********
I tried to do what you asked but could not get through - the confirmation
for subscribing to the list also did not work, so I did not know how to
proceed.
Much to my surprise I started receiving mails from you two days ago:-o
So what happened - then and now (the crash re-occurred for the same reason
with the identical mask, which is what is quoted above):
On my licq icon it says "4 messages" (4 Nachrichten). The crash occurs
when I double-click on this message, in order to raise the messages.Not on
the first attempt. Then a message will pop up (I use the email
mode) - when I click on "close" it does close but the number of messages
listed has not been reduced. On second try it will crash.
licq.backtrace
*********
time: 1257544099
licq(licq_handle_sigabrt+0x34d) [0x811cccd]
[0xb804d400]
/lib/tls/i686/cmov/libc.so.6(abort+0x188) [0xb7bfe098]
licq [0x811cfbd]
[0xb804d400]
**********
licq.backtrace.gdb
**************
Thread 6 (Thread 0xb6e26b90 (LWP 10621)):
#0 0xb804d430 in __kernel_vsyscall ()
#1 0xb7cad7b1 in select () from /lib/tls/i686/cmov/libc.so.6
#2 0x080dc22a in MonitorSockets_tep ()
#3 0xb7e8f4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#4 0xb7cb549e in clone () from /lib/tls/i686/cmov/libc.so.6
Thread 5 (Thread 0xb6625b90 (LWP 10622)):
#0 0xb804d430 in __kernel_vsyscall ()
#1 0xb7cad7b1 in select () from /lib/tls/i686/cmov/libc.so.6
#2 0x080db767 in Ping_tep ()
#3 0xb7e8f4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#4 0xb7cb549e in clone () from /lib/tls/i686/cmov/libc.so.6
Thread 4 (Thread 0xb5e24b90 (LWP 10623)):
#0 0xb804d430 in __kernel_vsyscall ()
#1 0xb7cad7b1 in select () from /lib/tls/i686/cmov/libc.so.6
#2 0x080db0f6 in UpdateUsers_tep ()
#3 0xb7e8f4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#4 0xb7cb549e in clone () from /lib/tls/i686/cmov/libc.so.6
Thread 3 (Thread 0xb5623b90 (LWP 10624)):
#0 0xb804d430 in __kernel_vsyscall ()
#1 0xb7e930e5 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/tls/i686/cmov/libpthread.so.0
#2 0x080def07 in OscarServiceSendQueue_tep ()
#3 0xb7e8f4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#4 0xb7cb549e in clone () from /lib/tls/i686/cmov/libc.so.6
Thread 2 (Thread 0xb4e22b90 (LWP 10625)):
#0 0xb804d430 in __kernel_vsyscall ()
#1 0xb7e9703b in waitpid () from /lib/tls/i686/cmov/libpthread.so.0
#2 0x0811cbe4 in licq_handle_sigabrt ()
#3 <signal handler called>
#4 0xb804d430 in __kernel_vsyscall ()
#5 0xb7bfc6d0 in raise () from /lib/tls/i686/cmov/libc.so.6
#6 0xb7bfe098 in abort () from /lib/tls/i686/cmov/libc.so.6
#7 0x0811cfbd in licq_handle_sigsegv ()
#8 <signal handler called>
#9 0xb7794bbc in ?? () from /usr/lib/libqt-mt.so.3
#10 0x00000000 in ?? ()
Thread 1 (Thread 0xb7bb96d0 (LWP 10614)):
#0 0xb804d430 in __kernel_vsyscall ()
#1 0xb7e930e5 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/tls/i686/cmov/libpthread.so.0
#2 0x0807c85c in CLicq::Main ()
#3 0x080814e2 in main ()
#0 0xb804d430 in __kernel_vsyscall ()
*******
Let me add, though, that licq may be running in an unstable
environment. (On ubuntu jaunty) I run it by using "sux [different user]".
On calling up licq I always get on my terminal the message:
*******
net@xubuntu:~$ licq
Session management error: Authentication Rejected, reason : None of the
authentication protocols specified are supported and host-based
authentication failed
********
Licq has worked ok, however, except for these recent "happenings".
The installed package is: licq 1.3.6-0ubuntu1
Regards
Luise
--
One thought to all who, free of doubt,
So definitely know what's true:
2 and 2 is 22 -
and 2 times 2 is 2:-)
==========> ICQ yinyang 96391801 <==========
Anders Olofsson
>
> A few weeks ago I encountered a fatal error, which is still with me.
>
> for subscribing to the list also did not work, so I did not know how to
> proceed.
>
> Much to my surprise I started receiving mails from you two days ago:-o
>
> So what happened - then and now (the crash re-occurred for the same reason
> with the identical mask, which is what is quoted above):
>
> On my licq icon it says "4 messages" (4 Nachrichten). The crash occurs
> when I double-click on this message, in order to raise the messages.Not on
> the first attempt. Then a message will pop up (I use the email
> mode) - when I click on "close" it does close but the number of messages
> listed has not been reduced. On second try it will crash.
>
> environment. (On ubuntu jaunty) I run it by using "sux [different user]".
> On calling up licq I always get on my terminal the message:
>
> *******
> net@xubuntu:~$ licq
> Session management error: Authentication Rejected, reason : None of the
> authentication protocols specified are supported and host-based
> authentication failed
> ********
>
> Licq has worked ok, however, except for these recent "happenings".
>
> The installed package is: licq 1.3.6-0ubuntu1
>
> Regards
>
> Luise
Hi,
unfortunately, the web site is a bit unstable and has been down recently.
I would recommend you to create a ticket for this now that the site is
back up.
However, I can give you the first reply for the ticket right here so you
can include those answers as well:
* Did the crash happen on startup (offline or old messages) or with
messages received while Licq was running?
* Does the crash happen just once or will Licq crash again every time
you restart it and try to read the messages again?
* Were there anything special in those messages that caused the crash?
i.e. special non-english characters, URLs, etc...?
* Does it still crash if use use chat mode?
* Can you try Licq 1.3.7 instead and check if problem persist in that
version?
Regarding the "Session management error", I'm pretty sure that's not
from Licq but from something else in your environment (probably X window
system).
/Anders
Luise Kunkle
Hi Anders,
Since it says in the mask that I can use this list for the purpose, I'll
just go on here.
> However, I can give you the first reply for the ticket right here so you can
> include those answers as well:
My answers:
> * Did the crash happen on startup (offline or old messages) or with messages
> received while Licq was running?
It started while I was online. The other side kept sending messages while
I was still busy doing waht was said in the previous message - so they
accumulated.
> * Does the crash happen just once or will Licq crash again every time you
> restart it and try to read the messages again?
It will do it after every re-start.
> * Were there anything special in those messages that caused the crash? i.e.
> special non-english characters, URLs, etc...?
I do not think there was.
> * Does it still crash if use use chat mode?
No. It shows the messages but does not
> * Can you try Licq 1.3.7 instead and check if problem persist in that
> version?
>
No - this is the latest licq version ubuntu provides as a package. I have
not yet graaduated to using programs outside of those packages:-)
>
> Regarding the "Session management error", I'm pretty sure that's not from
> Licq but from something else in your environment (probably X window system).
>
Yes - I realize that. I thought that perhaps this flaw in the environment
caused by my using it al a different user might in turn cause licq to be
more unstable.
Regards
Luise
------------
One thought to all who, free from doubt,
Anders Olofsson
>> messages received while Licq was running?
>
> It started while I was online. The other side kept sending messages
> while I was still busy doing waht was said in the previous message - so
> they accumulated.
Has this happen several times or just once? Do you know how many
messages it was before it crashed?
Can you reproduce the situation and make it crash again?
If you can, then please provide the backtrace files from the first
crash, before restarting Licq and crashing it again which will overwrite
the backtrace files.
>> * Does the crash happen just once or will Licq crash again every time
>> you restart it and try to read the messages again?
>
> It will do it after every re-start.
Does it crash on start or when opening the message dialog?
If it's on start, do you have licq to auto logon on start and unread
messages auto popup?
>> * Does it still crash if use use chat mode?
>
> No. It shows the messages but does not
So at least you have a workaround, that's good.
>> * Can you try Licq 1.3.7 instead and check if problem persist in that
>> version?
>>
> No - this is the latest licq version ubuntu provides as a package. I
> have not yet graaduated to using programs outside of those packages:-)
Ok, that's understandable. As 1.3.7 is released I guess it will be
picked up by Ubuntu and included in next version some time soon.
I did some attempts to reproduce this (with latest version) but I could
not get it to crash by just sending messages while message dialog was open.
/Anders
Luise Kunkle
Hi Anders,
On Wed, 11 Nov 2009, Anders Olofsson wrote:
>
>>> * Did the crash happen on startup (offline or old messages) or with
>>> messages received while Licq was running?
>>
>> It started while I was online. The other side kept sending messages while I
>> was still busy doing waht was said in the previous message - so they
>> accumulated.
>
> Has this happen several times or just once?
Just once.
> Do you know how many messages it
> was before it crashed?
>
Not exactly - but is was an unusual large number. Perhaps 9 of them.
> Can you reproduce the situation and make it crash again?
Not now - perhaps in a few days I can; for certain in about 2 weeks.
> If you can, then please provide the backtrace files from the first crash,
> before restarting Licq and crashing it again which will overwrite the
> backtrace files.
>
Will do when I have the chance.
>
>>> * Does the crash happen just once or will Licq crash again every time you
>>> restart it and try to read the messages again?
>>
>> It will do it after every re-start.
>
> Does it crash on start or when opening the message dialog?
>
It happens *on the second attempt* that I try to get the message by
double-clicking on the notification on the icon. Other than that licq
works ok.
> If it's on start, do you have licq to auto logon on start and unread messages
> auto popup?
>
>
>>> * Does it still crash if use use chat mode?
>>
>> No. It shows the messages but does not
>
> So at least you have a workaround, that's good.
>
Yes
>
>>> * Can you try Licq 1.3.7 instead and check if problem persist in that
>>> version?
>>>
>> No - this is the latest licq version ubuntu provides as a package. I have
>> not yet graaduated to using programs outside of those packages:-)
>
> Ok, that's understandable. As 1.3.7 is released I guess it will be picked up
> by Ubuntu and included in next version some time soon.
>
> I did some attempts to reproduce this (with latest version) but I could not
> get it to crash by just sending messages while message dialog was open.
>
Thank you for trying to help.