pidgin crashed with signal 5 in g_return_if_fail_warning()

Bug #187545 reported by Dmitry Olyenyov
20
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: pidgin

Somebody sent me a message through lotus sametime protocol

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Thu Jan 31 11:09:38 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: hsfengine ath_hal nvidia
Package: pidgin 1:2.3.1-2ubuntu1
PackageArchitecture: i386
ProcCmdline: pidgin --session 110a331208000120114567300000117080003 --display :0.0
ProcCwd: /home/dema
ProcEnviron:
 PATH=/home/dema/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=ru_RU.UTF-8
 SHELL=/usr/bin/zsh
Signal: 5
SourcePackage: pidgin
StacktraceTop:
 g_return_if_fail_warning () from /usr/lib/libglib-2.0.so.0
 purple_conversation_get_ui_ops ()
 ?? ()
 ?? ()
Title: pidgin crashed with signal 5 in g_return_if_fail_warning()
Uname: Linux dema-ubuntu 2.6.24-5-generic #1 SMP Thu Jan 24 19:45:21 UTC 2008 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev sambashare scanner video

Tags: apport-crash
Revision history for this message
Dmitry Olyenyov (dmitry-olyenyov) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:IA__g_return_if_fail_warning (log_domain=0x0,
purple_conversation_get_ui_ops (conv=0x0) at ../../libpurple/conversation.c:584
received_im_msg_cb (account=0x818b4a0,
purple_marshal_VOID__POINTER_POINTER_POINTER_POINTER_UINT (cb=0x80971d0 <received_im_msg_cb>,
purple_signal_emit_vargs (instance=0xb7955d44, signal=0xb793d1e9 "received-im-msg",

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in pidgin:
importance: Undecided → Medium
Revision history for this message
Andreas Moog (ampelbein) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Changed in pidgin:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

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 the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in pidgin:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.