[Bug 123386] Re: pidgin crashed with signal 5 in g_logv()

2008-12-01 Thread Chris Coulson
zertyz - if you are experiencing a crash, then please have Apport submit a new crash report so it can be processed properly by the retracer. You haven't posted anything here to suggest that you are experiencing the same bug. To do this, you might need to enable Apport in /etc/default/apport and

[Bug 123386] Re: pidgin crashed with signal 5 in g_logv()

2008-11-17 Thread zertyz
I'd like to reopen this bug since it still happens and I have more information to provide. Please see my post. Thanks ** Changed in: pidgin (Ubuntu) Status: Invalid = New -- pidgin crashed with signal 5 in g_logv() https://bugs.launchpad.net/bugs/123386 You received this bug notification

[Bug 123386] Re: pidgin crashed with signal 5 in g_logv()

2008-11-17 Thread zertyz
Using Pidgin 2.4.3 on an updated system it quits suddenly from time to time. Investigating by running pidgin -d I found that it attempts to allocate a huge amount of memory which is, of course, denied and then it quits. Investigating a little further I found the pattern: whenever pidgin tried to

[Bug 123386] Re: pidgin crashed with signal 5 in g_logv()

2008-11-17 Thread zertyz
... It just happened again: here is the last log lines that use to happen just before pidgin quits: (18:04:15) msn: C: SB 025: MSG 20 D 143 (18:04:15) msn: C: NS 000: PNG (18:04:15) msn: S: SB 025: ACK 20 (18:04:15) msn: S: NS 000: QNG 49 (18:04:17) msn: C: SB 024: MSG 11 D 795 (18:04:17) msn:

[Bug 123386] Re: pidgin crashed with signal 5 in g_logv()

2008-05-06 Thread Pedro Villavicencio
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on

[Bug 123386] Re: pidgin crashed with signal 5 in g_logv()

2008-04-05 Thread Jérôme Guelfucci
Thank you for your bug report. Have you been able to reproduce this with an up to date Ubuntu system ? ** Changed in: pidgin (Ubuntu) Status: Triaged = Incomplete -- pidgin crashed with signal 5 in g_logv() https://bugs.launchpad.net/bugs/123386 You received this bug notification because

[Bug 123386] Re: pidgin crashed with signal 5 in g_logv()

2007-07-02 Thread Sebastien Bacher
Thank you for your bug ** Changed in: pidgin (Ubuntu) Status: New = Triaged -- pidgin crashed with signal 5 in g_logv() https://bugs.launchpad.net/bugs/123386 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs

[Bug 123386] Re: pidgin crashed with signal 5 in g_logv()

2007-07-01 Thread BenChina
** Attachment added: CoreDump.gz http://launchpadlibrarian.net/8272638/CoreDump.gz ** Attachment added: Dependencies.txt http://launchpadlibrarian.net/8272639/Dependencies.txt ** Attachment added: Disassembly.txt http://launchpadlibrarian.net/8272640/Disassembly.txt ** Attachment

[Bug 123386] Re: pidgin crashed with signal 5 in g_logv()

2007-07-01 Thread Apport retracing service
StacktraceTop:IA__g_logv (log_domain=value optimized out, log_level=G_LOG_LEVEL_ERROR, format=0xb775c12c %s: failed to allocate %lu bytes, IA__g_log (log_domain=0xb7755146 GLib, log_level=G_LOG_LEVEL_ERROR, format=0xb775c12c %s: failed to allocate %lu bytes) IA__g_malloc (n_bytes=4294967291)

[Bug 123386] Re: pidgin crashed with signal 5 in g_logv()

2007-07-01 Thread RainCT
** Changed in: pidgin (Ubuntu) Importance: Undecided = Medium -- pidgin crashed with signal 5 in g_logv() https://bugs.launchpad.net/bugs/123386 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list