[apport] gaim crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()

Bug #96681 reported by Julius
2
Affects Status Importance Assigned to Milestone
gaim (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gaim

previous a window poped up saying "buddy 1 couldn't be added to contact list" and that i might have the maximum number of buddys already, which is not true.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Mon Mar 26 23:30:35 2007
Disassembly: 0xb6321f40:
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/gaim
Package: gaim 1:2.0.0+beta6-1ubuntu2
PackageArchitecture: i386
ProcCmdline: gaim
ProcCwd: /home/julius
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=de_DE.UTF-8@euro
Signal: 11
SourcePackage: gaim
StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID__VOID ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 ?? ()
Uname: Linux r112048 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

Revision history for this message
Julius (caesar-bs) wrote :
Revision history for this message
Daniel Holbach (dholbach) wrote :

Thanks for your bug report.

Changed in gaim:
importance: Undecided → Medium
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
IA__g_cclosure_marshal_VOID__VOID (closure=0x8591160, return_value=0x0, n_param_values=1, param_values=0xbf922a2c, invocation_hint=0xbf92293c,
IA__g_closure_invoke (closure=0x8591160, return_value=0x0, n_param_values=1, param_values=0xbf922a2c, invocation_hint=0xbf92293c) at gclosure.c:490
signal_emit_unlocked_R (node=0x8176028, detail=0, instance=0x821b498, emission_return=0x0, instance_and_params=0xbf922a2c) at gsignal.c:2440
IA__g_signal_emit_valist (instance=0x821b498, signal_id=25, detail=0, var_args=0xbf922c6c "ZE޷�\213�230�!\b�,\222�\017��\230�!\b@\004") at gsignal.c:2199

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
IA__g_cclosure_marshal_VOID__VOID (closure=0x8591160, return_value=0x0, n_param_values=1, param_values=0xbf922a2c, invocation_hint=0xbf92293c,
IA__g_closure_invoke (closure=0x8591160, return_value=0x0, n_param_values=1, param_values=0xbf922a2c, invocation_hint=0xbf92293c) at gclosure.c:490
signal_emit_unlocked_R (node=0x8176028, detail=0, instance=0x821b498, emission_return=0x0, instance_and_params=0xbf922a2c) at gsignal.c:2440
IA__g_signal_emit_valist (instance=0x821b498, signal_id=25, detail=0, var_args=0xbf922c6c "ZE޷�\213�230�!\b�,\222�\017��\230�!\b@\004") at gsignal.c:2199

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

Changed in gaim:
status: Unconfirmed → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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