gnome-system-log crashed with SIGSEGV in g_closure_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-utils |
New
|
Critical
|
|||
gnome-system-log (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
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/
Package: gnome-utils 2.28.0-0ubuntu1
ProcCmdline: gnome-system-log
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, user)
LANG=sv_SE.UTF-8
ProcVersionSign
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/
g_signal_
g_signal_emit () from /usr/lib/
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
Changed in gnome-utils: | |
importance: | Unknown → Critical |
status: | Unknown → New |
affects: | gnome-utils (Ubuntu) → gnome-system-log (Ubuntu) |
Changed in gnome-system-log (Ubuntu): | |
assignee: | Ubuntu Desktop Bugs (desktop-bugs) → nobody |
StacktraceTop: active_ log_changed_ cb (manager=<value optimized out>, log=0x22f2b10, libgobject- 2.0.so. 0 emit_valist () libgobject- 2.0.so. 0
g_closure_invoke ()
?? () from /usr/lib/
g_signal_
g_signal_emit () from /usr/lib/