You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
I got similar pidgin crashes with libskype_dbus.so and libskype.so.
What is the expected output? What do you see instead?
$ pidgin -d
...
(17:01:25) account: Connecting to account incubus.
(17:01:25) connection: Connecting. gc = 0x80a719b80
(17:01:25) GThread: file gthread-posix.c: line 254
(g_cond_timed_wait_posix_impl): error 'Operation not permitted' during
'pthread_cond_timedwait'
$ gdb pidgin
...
Program received signal SIGABRT, Aborted.
[Switching to Thread 8058041c0 (LWP 100280)]
0x00000008054a3e1c in thr_kill () from /lib/libc.so.7
(gdb) bt
#0 0x00000008054a3e1c in thr_kill () from /lib/libc.so.7
#1 0x0000000805533d13 in abort () from /lib/libc.so.7
#2 0x0000000804a1abdb in IA__g_logv (log_domain=0x804579256 "GThread",
log_level=G_LOG_LEVEL_ERROR,
format=0x804579228 "file %s: line %d (%s): error '%s' during '%s'",
args1=0x7fffffffdce0) at gmessages.c:549
#3 0x0000000804a1ad6c in IA__g_log (log_domain=0x804579256 "GThread",
log_level=G_LOG_LEVEL_ERROR,
format=0x804579228 "file %s: line %d (%s): error '%s' during '%s'") at
gmessages.c:569
#4 0x0000000804577e94 in g_cond_timed_wait_posix_impl (cond=0x80a76d340,
entered_mutex=0x80a0c9f48, abs_time=0x7fffffffdef0)
at gthread-posix.c:254
#5 0x0000000809fbdf22 in skype_send_message (message_format=0x809fc656b
"NAME %s") at skype_messaging.c:229
#6 0x0000000809fc1003 in skype_login (acct=0x805938980) at libskype.c:1507
#7 0x00000008038d928e in purple_accounts_restore_current_statuses () at
account.c:2743
#8 0x000000000047c3e9 in main ()
What version of the plugin are you using? On what operating system?
Latest svn version
$ uname -srm
FreeBSD 9.0-CURRENT amd64
$ pidgin -v
Pidgin 2.6.4 (libpurple 2.6.4)
$ skype -v
Skype 2.0.0.72-oss
Copyright (c) 2004-2007, Skype Limited
Original issue reported on code.google.com by logvi...@nm.ru on 8 Jan 2010 at 9:07
Original issue reported on code.google.com by
logvi...@nm.ru
on 8 Jan 2010 at 9:07The text was updated successfully, but these errors were encountered: