gnome-system-log crashed with SIGSEGV in g_closure_invoke()

[Daniel Hermansson]

Binary package hint: gnome-utils

gnome-system-log crashes when I click back and forth between logs. I think it's related to some logs being flooded (by poopaudio and drm) making them really big, up to 100 MB

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Sun Oct 4 05:04:42 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/gnome-system-log
Package: gnome-utils 2.28.0-0ubuntu1
ProcCmdline: gnome-system-log
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=sv_SE.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-11.38-generic
SegvAnalysis:
 Segfault happened at: 0x40fe4d: mov 0x8(%r14),%r15
 PC (0x0040fe4d) ok
 source "0x8(%r14)" (0x7f9ad4a7a5d8) not located in a known VMA region (needed readable region)!
 destination "%r15" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-utils
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: gnome-system-log crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.31-11-generic x86_64
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse kvm libvirtd lpadmin netdev plugdev sambashare scanner tape vboxusers video

[Apport retracing service (apport)]

StacktraceTop:active_log_changed_cb (manager=<value optimized out>, log=0x22f2b10,
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

[Pedro Villavicencio (pedro)]

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at: https://bugzilla.gnome.org/show_bug.cgi?id=597553