pidgin crashed with SIGSEGV in set_current_error()

[Vojtěch Látal]

Binary package hint: pidgin

I hibernated the computer, then woken it up. Did nothing special.

I hope this report will help someone.

$ apt-cache policy pidgin
pidgin:
  Installed: 1:2.4.0-1ubuntu1
  Candidate: 1:2.4.0-1ubuntu1

ProblemType: Crash
Architecture: i386
Date: Sat Mar 29 18:16:28 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/pidgin
Package: pidgin 1:2.4.0-1ubuntu1
PackageArchitecture: i386
ProcCmdline: pidgin --session 117f000101000120668799400000068150012 --display :0.0
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 set_current_error (account=0x1, new_err=0x8cf23f0)
 connection_error_cb (gc=0x8a17098,
 purple_marshal_VOID__POINTER_INT_POINTER (
 purple_signal_emit_vargs (instance=0xb798b034,
 purple_signal_emit (instance=0xb798b034,
Title: pidgin crashed with SIGSEGV in set_current_error()
Uname: Linux 2.6.24-8-generic i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse games lpadmin mythtv netdev plugdev postgres powerdev pulse sambashare scanner tape users video

[Apport retracing service (apport)]

StacktraceTop:set_current_error (account=0x1, new_err=0x8cf23f0)
connection_error_cb (gc=0x8a17098,
purple_marshal_VOID__POINTER_INT_POINTER (
purple_signal_emit_vargs (instance=0xb798b034,
purple_signal_emit (instance=0xb798b034,

[Michael Elkins (sigpipe)]

I can confirm this same issue on multiple machines. If I hibernate the computer while pidgin is running, it will crash consistently when the computer is resumed.

[Chafnan (chafnan)]

I confirm this bug on my system. Started 2 days ago.

[washeck (vrehak)]

Jonathan, do you have the latest version installed? The bug was fixed upstream in 2.4.1 and I don't see the problem anymore in 1:2.4.1-1ubuntu2.

[Chafnan (chafnan)]

I do have 2.4.1 installed.

I was taking a look at it again and this is the error that I am getting when
I load the program. Actually looking at it now, I think I posted in the
wrong bug. Let me know what you think.
---------------------------------------------------
$ pidgin
*** glibc detected *** pidgin: double free or corruption (fasttop):
0x086163f0 ***
======= Backtrace: =========
/lib/tls/i686/cmov/libc.so.6[0xb7664a85]
/lib/tls/i686/cmov/libc.so.6(cfree+0x90)[0xb76684f0]
/usr/lib/libglib-2.0.so.0(g_free+0x31)[0xb77c58b1]
/usr/lib/libpurple.so.0(purple_dnsquery_destroy+0x90)[0xb78f0d57]
/usr/lib/libpurple.so.0[0xb78ef9cb]
/usr/lib/libpurple.so.0[0xb78f09f5]
pidgin[0x80abca3]
/usr/lib/libglib-2.0.so.0[0xb77f1c5d]
/usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x178)[0xb77bdbf8]
/usr/lib/libglib-2.0.so.0[0xb77c0e5e]
/usr/lib/libglib-2.0.so.0(g_main_loop_run+0x1e7)[0xb77c11e7]
/usr/lib/libgtk-x11-2.0.so.0(gtk_main+0xb4)[0xb7c7f244]
pidgin(main+0xbbc)[0x80c70d5]
/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe0)[0xb760f450]
pidgin[0x806c821]
======= Memory map: ========
08048000-08115000 r-xp 00000000 fe:01 694420 /usr/bin/pidgin
08115000-08118000 rw-p 000cc000 fe:01 694420 /usr/bin/pidgin
08118000-0867c000 rw-p 08118000 00:00 0 [heap]
b2b00000-b2b21000 rw-p b2b00000 00:00 0
b2b21000-b2c00000 ---p b2b21000 00:00 0
b2c40000-b2ca0000 rw-s 00000000 00:09 4358199 /SYSV00000000 (deleted)
b2ca0000-b2d00000 rw-s 00000000 00:09 4259890 /SYSV00000000 (deleted)
b2d00000-b2d1f000 r-xp 00000000 fe:01 692511 /usr/lib/libjpeg.so.62.0.0
b2d1f000-b2d20000 rw-p 0001e000 fe:01 692511 /usr/lib/libjpeg.so.62.0.0
b2d36000-b2d3a000 r-xp 00000000 fe:01 754555
/usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-jpeg.so
b2d3a000-b2d3b000 rw-p 00003000 fe:01 754555
/usr/lib/gtk-2.0/2.10.0/loaders/libpixbufloader-jpeg.so
b2d3b000-b2e3f000 rw-p b2d3b000 00:00 0
b2e3f000-b2ec6000 r--p 00000000 fe:01 1000027
/usr/share/fonts/truetype/ttf-dejavu/DejaVuSans-Bold.ttf
b2ec6000-b2edd000 r--s 00000000 fe:01 263108
/var/lib/aspell/en_US-wo_accents-only.rws
b2edd000-b3165000 r--s 00000000 fe:01 263097
/var/lib/aspell/en-common.rws
b3169000-b326d000 rw-p b3169000 00:00 0
b326d000-b326f000 r-xp 00000000 fe:01 754494
/usr/lib/pango/1.6.0/modules/pango-basic-fc.so
b326f000-b3270000 rw-p 00001000 fe:01 754494
/usr/lib/pango/1.6.0/modules/pango-basic-fc.so
b3270000-b3301000 r--p 00000000 fe:01 1000026
/usr/share/fonts/truetype/ttf-dejavu/DejaVuSans.ttf
b3301000-b3307000 r--s 00000000 fe:01 262415
/var/cache/fontconfig/945677eb7aeaf62f1d50efc3fb3ec7d8-x86.cache-2
b3307000-b330a000 r--s 00000000 fe:01 262413
/var/cache/fontconfig/e383d7ea5fbe662a33d9b44caf393297-x86.cache-2
b330a000-b330b000 r--s 00000000 fe:01 262250
/var/cache/fontconfig/fc14e3aff40829fbb7132d5e06a8168b-x86.cache-2
b330b000-b330d000 r--s 00000000 fe:01 49918
/var/cache/fontconfig/52728cdc49031813f272d4aa720952ff-x86.cache-2
b330d000-b3311000 r--s 00000000 fe:01 262750
/var/cache/fontconfig/926e794c3d5e5dffcaf2fa83ef8d36c2-x86.cache-2
b3311000-b3314000 r--s 00000000 fe:01 262410
/var/cache/fontconfig/a755afe4a08bf5b97852ceb7400b47bc-x86.cache-2
b3314000-b331b000 r--s 00000000 fe:01 26...

[RosaI (rosai54)]

Hi, it is me again, sorry to bog you up, this program is working just fine, failed after the up grade restart, but worked right away after.
Thank you

[RosaI (rosai54)]

Well I sang too fast, the program is working apparently without problems, but keeps appearing the crash sing, same with the rhytmbox program. Should I just ignore them?

[Brian Curtis (bcurtiswx)]

Do you still experience this issue (specifically with pidgin)?

[Chris Wulff (crwulff)]

I have not seen this issue in quite some time.

On Thu, 2008-08-21 at 22:30 +0000, Brian Curtis wrote:
> Do you still experience this issue (specifically with pidgin)?
>
> ** Changed in: pidgin (Ubuntu)
> Status: Confirmed => Incomplete
>

[christpunk01 (christpunk01)]

No. I have not experienced this problem in some time. In fact, I don' even remember submitting the bug.

 EMAILING FOR THE GREATER GOOD
Join me

> From: <email address hidden>
> To: <email address hidden>
> Date: Thu, 21 Aug 2008 22:30:25 +0000
> Subject: [Bug 208890] Re: pidgin crashed with SIGSEGV in set_current_error()
>
> Do you still experience this issue (specifically with pidgin)?
>
> ** Changed in: pidgin (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> pidgin crashed with SIGSEGV in set_current_error()
> https://bugs.launchpad.net/bugs/208890
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “pidgin” source package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: pidgin
>
> I hibernated the computer, then woken it up. Did nothing special.
>
> I hope this report will help someone.
>
> $ apt-cache policy pidgin
> pidgin:
> Installed: 1:2.4.0-1ubuntu1
> Candidate: 1:2.4.0-1ubuntu1
>
> ProblemType: Crash
> Architecture: i386
> Date: Sat Mar 29 18:16:28 2008
> DistroRelease: Ubuntu 8.04
> ExecutablePath: /usr/bin/pidgin
> Package: pidgin 1:2.4.0-1ubuntu1
> PackageArchitecture: i386
> ProcCmdline: pidgin --session 117f000101000120668799400000068150012 --display :0.0
> Signal: 11
> SourcePackage: pidgin
> StacktraceTop:
> set_current_error (account=0x1, new_err=0x8cf23f0)
> connection_error_cb (gc=0x8a17098,
> purple_marshal_VOID__POINTER_INT_POINTER (
> purple_signal_emit_vargs (instance=0xb798b034,
> purple_signal_emit (instance=0xb798b034,
> Title: pidgin crashed with SIGSEGV in set_current_error()
> Uname: Linux 2.6.24-8-generic i686
> UserGroups: adm admin audio cdrom dialout dip fax floppy fuse games lpadmin mythtv netdev plugdev postgres powerdev pulse sambashare scanner tape users video

[Andreas Moog (ampelbein)]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

This bug report is being closed due to your last comment regarding this
being fixed for you.

 status invalid
 subscribe

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkivA7cACgkQ06FgkPZwicSzlACfb+s5sZRBCQpjLlL0YTzJ5jws
+AcAoIFMqWuKEjkgzebJcgYka5yEWiEY
=UV2s
-----END PGP SIGNATURE-----

[Alex Ruddick (alexrudd0)]

I created a new bug and reported it as a duplicate so I could attach the apport info.
https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/268259
Occured after resuming from Hibernate on up-to-date Intrepid.

I'll mark it as public as soon as someone can confirm that the information attached doesn't include my passwords or anything. ;)

[LimCore (limcore)]

Perhaps it is not issue of hibernation, but of reconnecting to the network etc?

It happened for me right when my net connection got reseted by ISP (also IP change)
This happens often but only this time crash
Probably because I had an XMPP console opened at that time (plugin).

[New Thread 0x7f9f075e96f0 (LWP 10512)]
[New Thread 0x41dd9950 (LWP 10519)]
[New Thread 0x425da950 (LWP 10522)]

Program received signal SIGPIPE, Broken pipe.
[Switching to Thread 0x7f9f075e96f0 (LWP 10512)]
0x00007f9f04491b51 in send () from /lib/libpthread.so.0
(gdb)
(gdb) bt
#0 0x00007f9f04491b51 in send () from /lib/libpthread.so.0
#1 0x00007f9ef9410b48 in ?? () from /usr/lib/libnspr4.so.0d
#2 0x00007f9ef7d90e37 in ?? () from /usr/lib/libssl3.so.1d
#3 0x00007f9ef7d835b9 in ?? () from /usr/lib/libssl3.so.1d
#4 0x00007f9ef7d839ce in ?? () from /usr/lib/libssl3.so.1d
#5 0x00007f9ef7d942d3 in ?? () from /usr/lib/libssl3.so.1d
#6 0x00007f9ef10f097d in ?? () from /usr/lib/purple-2/ssl-nss.so
#7 0x00007f9f050b8105 in purple_ssl_close () from /usr/lib/libpurple.so.0
#8 0x00007f9ef0ac2234 in jabber_close () from /usr/lib/purple-2/libjabber.so.0
#9 0x00007f9f0507e758 in purple_connection_destroy () from /usr/lib/libpurple.so.0
#10 0x00007f9f050647ea in purple_account_disconnect () from /usr/lib/libpurple.so.0
#11 0x00007f9f0507eef5 in ?? () from /usr/lib/libpurple.so.0
#12 0x00007f9f04958abb in ?? () from /usr/lib/libglib-2.0.so.0
#13 0x00007f9f04958364 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#14 0x00007f9f0495b675 in ?? () from /usr/lib/libglib-2.0.so.0
#15 0x00007f9f0495b995 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#16 0x00007f9f0609ef03 in IA__gtk_main () at /build/buildd/gtk+2.0-2.12.9/gtk/gtkmain.c:1163
#17 0x0000000000486c0a in main ()

[Brian Curtis (bcurtiswx)]

Since Pidgin has newer versions since the latest post. Can you please let me know if you get these errors on the most recent version of pidgin? This way I can forward this upstream if needed.

[christpunk01 (christpunk01)]

We're good. No more problems.

 EMAILING FOR THE GREATER GOOD
Join me

> Date: Fri, 20 Feb 2009 16:13:16 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 208890] Re: pidgin crashed with SIGSEGV in set_current_error()
>
> Since Pidgin has newer versions since the latest post. Can you please
> let me know if you get these errors on the most recent version of
> pidgin? This way I can forward this upstream if needed.
>
> --
> pidgin crashed with SIGSEGV in set_current_error()
> https://bugs.launchpad.net/bugs/208890
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “pidgin” source package in Ubuntu: New
>
> Bug description:
> Binary package hint: pidgin
>
> I hibernated the computer, then woken it up. Did nothing special.
>
> I hope this report will help someone.
>
> $ apt-cache policy pidgin
> pidgin:
> Installed: 1:2.4.0-1ubuntu1
> Candidate: 1:2.4.0-1ubuntu1
>
> ProblemType: Crash
> Architecture: i386
> Date: Sat Mar 29 18:16:28 2008
> DistroRelease: Ubuntu 8.04
> ExecutablePath: /usr/bin/pidgin
> Package: pidgin 1:2.4.0-1ubuntu1
> PackageArchitecture: i386
> ProcCmdline: pidgin --session 117f000101000120668799400000068150012 --display :0.0
> Signal: 11
> SourcePackage: pidgin
> StacktraceTop:
> set_current_error (account=0x1, new_err=0x8cf23f0)
> connection_error_cb (gc=0x8a17098,
> purple_marshal_VOID__POINTER_INT_POINTER (
> purple_signal_emit_vargs (instance=0xb798b034,
> purple_signal_emit (instance=0xb798b034,
> Title: pidgin crashed with SIGSEGV in set_current_error()
> Uname: Linux 2.6.24-8-generic i686
> UserGroups: adm admin audio cdrom dialout dip fax floppy fuse games lpadmin mythtv netdev plugdev postgres powerdev pulse sambashare scanner tape users video

[RosaI (rosai54)]

o key...
I made the first report
it was a wail ago,
that first crash happened right after the version's upgrade, from the
7/10 to the 8/4 it didn't happen again, works just fine, and what it
remains is an error that shows every time I initiate pidgin:

"Error al leer blist.xml

Se ha encontrado un error al leer su lista de amigos. No se ha cargado,
y el archivo antiguo se ha renombrado a /home/rosai/.purple/blist.xml~."

But doesn't seem to affect its functionality

RosaI

El vie, 20-02-2009 a las 16:23 +0000, christpunk01 escribió:

> We're good. No more problems.
>
>
>
> EMAILING FOR THE GREATER GOOD
> Join me
>
> > Date: Fri, 20 Feb 2009 16:13:16 +0000
> > From: <email address hidden>
> > To: <email address hidden>
> > Subject: [Bug 208890] Re: pidgin crashed with SIGSEGV in set_current_error()
> >
> > Since Pidgin has newer versions since the latest post. Can you please
> > let me know if you get these errors on the most recent version of
> > pidgin? This way I can forward this upstream if needed.
> >
> > --
> > pidgin crashed with SIGSEGV in set_current_error()
> > https://bugs.launchpad.net/bugs/208890
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
> > Status in “pidgin” source package in Ubuntu: New
> >
> > Bug description:
> > Binary package hint: pidgin
> >
> > I hibernated the computer, then woken it up. Did nothing special.
> >
> > I hope this report will help someone.
> >
> > $ apt-cache policy pidgin
> > pidgin:
> > Installed: 1:2.4.0-1ubuntu1
> > Candidate: 1:2.4.0-1ubuntu1
> >
> > ProblemType: Crash
> > Architecture: i386
> > Date: Sat Mar 29 18:16:28 2008
> > DistroRelease: Ubuntu 8.04
> > ExecutablePath: /usr/bin/pidgin
> > Package: pidgin 1:2.4.0-1ubuntu1
> > PackageArchitecture: i386
> > ProcCmdline: pidgin --session 117f000101000120668799400000068150012 --display :0.0
> > Signal: 11
> > SourcePackage: pidgin
> > StacktraceTop:
> > set_current_error (account=0x1, new_err=0x8cf23f0)
> > connection_error_cb (gc=0x8a17098,
> > purple_marshal_VOID__POINTER_INT_POINTER (
> > purple_signal_emit_vargs (instance=0xb798b034,
> > purple_signal_emit (instance=0xb798b034,
> > Title: pidgin crashed with SIGSEGV in set_current_error()
> > Uname: Linux 2.6.24-8-generic i686
> > UserGroups: adm admin audio cdrom dialout dip fax floppy fuse games lpadmin mythtv netdev plugdev postgres powerdev pulse sambashare scanner tape users video
>

--
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.24.1.1">
</HEAD>
<BODY>
<PRE>
<TT><FONT COLOR="#1a1a1a"><A HREF="http://www.somosunoradio.org">www.somosunoradio.org</A></FONT></TT>
</PRE>
<TT><FONT COLOR="#1a1a1a">Humildemente retomando a&nbsp; </FONT></TT><TT><FONT COLOR="#1a1a1a"><B>Ignacio Ramonet</B></FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">Director de &quot;</FONT></TT><TT><FONT COLOR="#1a1a1a"><I>Le Monde Diplomatique</I></FONT></TT><TT><FONT COLOR="#1a1a1a">&quot;</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">&quot;... No podemos seguir viviendo en un mundo donde m&#225;s de la mit...

[Brian Curtis (bcurtiswx)]

We have found an error reading your list of friends. Has not been charged,
and the old file is renamed to / home / Rosai / .purple / blist.xml ~.

Your .purple directory may be the culprit, as things can get messed up... As long as you don't mind having your settings reset, just go into /home/<you> and remove .purple (make sure pidgin is closed) and then re-load pidgin and hopefully the issue will be fixed. If not, you may want to jot down all your friends screen names and clear your buddy list, reinstall pidgin. But that last idea is only a last resort.

I will wait to hear back from LimCore and anyone else from duplicate bugs for a few more days before I make any attempts to close this bug report.

Thanks for your help in making ubuntu better!

[RosaI (rosai54)]

o key...
I did everything you say, at least the first part of it, I think,

Remove the purple folder,
Set pidgin up again

and nothing
the error sign appeared again

I' don't know how to do your last suggestion:
"to jot down all your friends screen names and clear your buddy list"

I can't find any way to do so.
i' don't know if un-installing pidgin with the add | un-install toll,
will be enough

I went into the
~home / rosai / .purple / blist.xml
and it had this message:

Error de parseo XML: referencia a un número de caracter inválido
Lugar: file:///home/rosai/.purple/blist.xml
Línea 1986, Columna 17: <group name='u&#x5;Redes'>
------------------------------^

and the system can't open the other file
"No se pudo mostrar «/home/rosai/.purple/blist.xml~»."
no existe una aplicación instalada para este tipo de archivo, no es un
directorio

my best guess its that something in a gmail account isn't functioning
right

I don't know if I should just let it be
because even with the error message, this error doesn't mess with the
functionality of the pidgin program.
Thank you

RosaI

El sáb, 21-02-2009 a las 19:25 +0000, Brian Curtis escribió:

> We have found an error reading your list of friends. Has not been charged,
> and the old file is renamed to / home / Rosai / .purple / blist.xml ~.
>
> Your .purple directory may be the culprit, as things can get messed
> up... As long as you don't mind having your settings reset, just go into
> /home/<you> and remove .purple (make sure pidgin is closed) and then re-
> load pidgin and hopefully the issue will be fixed. If not, you may want
> to jot down all your friends screen names and clear your buddy list,
> reinstall pidgin. But that last idea is only a last resort.
>
> I will wait to hear back from LimCore and anyone else from duplicate
> bugs for a few more days before I make any attempts to close this bug
> report.
>
> Thanks for your help in making ubuntu better!
>

--
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
  <META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
  <META NAME="GENERATOR" CONTENT="GtkHTML/3.24.1.1">
</HEAD>
<BODY>
<PRE>
<TT><FONT COLOR="#1a1a1a"><A HREF="http://www.somosunoradio.org">www.somosunoradio.org</A></FONT></TT>
</PRE>
<TT><FONT COLOR="#1a1a1a">Humildemente retomando a&nbsp; </FONT></TT><TT><FONT COLOR="#1a1a1a"><B>Ignacio Ramonet</B></FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">Director de &quot;</FONT></TT><TT><FONT COLOR="#1a1a1a"><I>Le Monde Diplomatique</I></FONT></TT><TT><FONT COLOR="#1a1a1a">&quot;</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">&quot;... No podemos seguir viviendo en un mundo donde m&#225;s de la mitad de la humanidad vive en la miseria... hemos querido crear este foro porque creemos que </FONT></TT><TT><FONT COLOR="#1a1a1a"><B><I>otro mundo es posible</I></B></FONT></TT><TT><FONT COLOR="#1a1a1a">.</FONT></TT><TT> </TT><TT><FONT COLOR="#1a1a1a">Hay que conseguirlo sin violencia, de una manera pac&#237;fica y pol&#237;tica, mediante las urnas,</FONT></TT><TT> </TT><TT><FONT COLOR="#1a1a1a">pero lo que s&#237; pensamos es que el mundo tal como est&#225; funcionando no puede ser satisfactorio...&quot;</...

[Brian Curtis (bcurtiswx)]

Rosai, it appears theres a fix listed in http://blog.gudigundla.com/
The following pertains to your error:
"When I looked at blist.xml file xmlChar 5 it turned out that there were two groups with same names from two different messengers. I then deleted that group, Quit Pidgin and then deleted blist.xml & blist.xml~ from /home/sai/.purple/ folder. After this when I started Pidgin that error was gone."

Let me know if this fixes your problem.

[Brian Curtis (bcurtiswx)]

Rosai: I just wanted to confirm that you got my previous response. Please check the bug page on launchpad to see if the fix I mentioned fixes your problem. Then let me know of the results.

[RosaI (rosai54)]

sorry I didn't answer before, I sow your former message, I quit didn't
understand pretty well then, so I didn't do it, now with your second
message, I just read it again and it sounds pretty easy to fix, rigth now
I've not the computer with me, as soon as I got it back I will do it and
report it.
thank you
RosaI

2009/3/20 Brian Curtis <email address hidden>

> Rosai: I just wanted to confirm that you got my previous response.
> Please check the bug page on launchpad to see if the fix I mentioned
> fixes your problem. Then let me know of the results.
>
> --
> pidgin crashed with SIGSEGV in set_current_error()
> https://bugs.launchpad.net/bugs/208890
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “pidgin” source package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: pidgin
>
> I hibernated the computer, then woken it up. Did nothing special.
>
> I hope this report will help someone.
>
> $ apt-cache policy pidgin
> pidgin:
> Installed: 1:2.4.0-1ubuntu1
> Candidate: 1:2.4.0-1ubuntu1
>
> ProblemType: Crash
> Architecture: i386
> Date: Sat Mar 29 18:16:28 2008
> DistroRelease: Ubuntu 8.04
> ExecutablePath: /usr/bin/pidgin
> Package: pidgin 1:2.4.0-1ubuntu1
> PackageArchitecture: i386
> ProcCmdline: pidgin --session 117f000101000120668799400000068150012
> --display :0.0
> Signal: 11
> SourcePackage: pidgin
> StacktraceTop:
> set_current_error (account=0x1, new_err=0x8cf23f0)
> connection_error_cb (gc=0x8a17098,
> purple_marshal_VOID__POINTER_INT_POINTER (
> purple_signal_emit_vargs (instance=0xb798b034,
> purple_signal_emit (instance=0xb798b034,
> Title: pidgin crashed with SIGSEGV in set_current_error()
> Uname: Linux 2.6.24-8-generic i686
> UserGroups: adm admin audio cdrom dialout dip fax floppy fuse games lpadmin
> mythtv netdev plugdev postgres powerdev pulse sambashare scanner tape users
> video
>

--
SomosUno Radio
http://www.somosunoradio.org/

Humildemente retomando a Ignacio Ramonet
Director de "Le Monde Diplomatique"

...."No podemos seguir viviendo en un mundo donde más de la mitad de la
humanidad vive en la miseria"..., .... "hemos querido crear este foro porque
creemos que otro mundo es posible. Hay que conseguirlo sin violencia, de una
manera pacífica y política, mediante las urnas, pero lo que sí pensamos es
que el mundo tal como está funcionando no puede ser satisfactorio"...

[Sebastien Bacher (seb128)]

the issue is similar to http://developer.pidgin.im/ticket/4815 and duplicates are hardy ones, seems to be fixed in the current version and jaunty