pidgin crashed with SIGSEGV in settings_notify_cb()

Bug #1054910 reported by Special Agent Stulle
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pidgin (Ubuntu)
New
Medium
Unassigned

Bug Description

using quantal

uname -a:
quantal 3.5.0-15-generic #22-Ubuntu SMP Wed Sep 19 20:01:43 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

apt-cache policy pidgin:
1:2.10.6-0ubuntu2

sudden crash
i'm using gtalk, jabber, icq-, facebook- and twitter protocols

works fine most of the time, sudden crashes appear seldom

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: pidgin 1:2.10.6-0ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
Uname: Linux 3.5.0-15-generic x86_64
ApportVersion: 2.5.2-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Sun Sep 23 11:19:16 2012
ExecutablePath: /usr/bin/pidgin
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
ProcCmdline: pidgin
ProcEnviron:
 LANGUAGE=de_DE:en
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fa7f1062db4: mov 0x38(%rbx),%rdi
 PC (0x7fa7f1062db4) ok
 source "0x38(%rbx)" (0x00000038) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: pidgin
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libdbusmenu-gtk.so.4
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: pidgin crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Special Agent Stulle (cooltimbo) wrote :
Revision history for this message
Special Agent Stulle (cooltimbo) wrote :

i also get sudden crashes in docky, also concerning

" /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0"

so maybe problem is in libgobject. i'm using

"gnome-shell 3.5.92-0ubuntu1"

maybe that could be important, too

visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 settings_notify_cb (settings=0x7fa8187f4400, pspec=<optimized out>, data=<optimized out>) at /build/buildd/libdbusmenu-12.10.1/./libdbusmenu-gtk/parser.c:1341
 g_closure_invoke (closure=0x7fa819836080, return_value=0x0, n_param_values=2, param_values=0x7fffc5161e90, invocation_hint=0x7fffc5161e30) at /build/buildd/glib2.0-2.33.14/./gobject/gclosure.c:777
 signal_emit_unlocked_R (node=node@entry=0x7fa8187cda90, detail=detail@entry=3025, instance=instance@entry=0x7fa8187f4400, emission_return=emission_return@entry=0x0, instance_and_params=instance_and_params@entry=0x7fffc5161e90) at /build/buildd/glib2.0-2.33.14/./gobject/gsignal.c:3551
 g_signal_emit_valist (instance=0x7fa8187f4400, signal_id=<optimized out>, detail=3025, var_args=var_args@entry=0x7fffc51620e8) at /build/buildd/glib2.0-2.33.14/./gobject/gsignal.c:3300
 g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at /build/buildd/glib2.0-2.33.14/./gobject/gsignal.c:3356

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in pidgin (Ubuntu):
importance: Undecided → Medium
summary: - pidgin crashed with SIGSEGV in g_closure_invoke()
+ pidgin crashed with SIGSEGV in settings_notify_cb()
tags: removed: need-amd64-retrace
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.