[apport] pidgin crashed with SIGSEGV in g_closure_invoke()

Bug #240788 reported by Miia Sample
10
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: pidgin

closed pidgin with clicking on the notification tray icon and choosing close.

Using hardy-proposed xubuntu.

ProblemType: Crash
Architecture: amd64
Date: Wed Jun 18 00:04:31 2008
Disassembly: 0x7f3a99729d50:
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: fglrx
Package: pidgin 1:2.4.1-1ubuntu2
PackageArchitecture: amd64
ProcCmdline: pidgin
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 ?? ()
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
 g_signal_emit () from /usr/lib/libgobject-2.0.so.0
Title: pidgin crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.24-19-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin plugdev scanner

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

StacktraceTop:?? ()
IA__g_closure_invoke (closure=0x10ebdd0, return_value=0x0, n_param_values=3,
signal_emit_unlocked_R (node=0xa09260, detail=0, instance=0xadb160,
IA__g_signal_emit_valist (instance=0xadb160, signal_id=<value optimized out>,
IA__g_signal_emit (instance=0xadb160, signal_id=24084400, detail=16328832)

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

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the final release of Hardy Heron 8.04.1 or Intrepid Ibex 8.10. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks again and we appreciate your help.

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.

Other bug subscribers

Remote bug watches

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