Actions
Bug #3369
closedmetacity: Segfault in libSM.so.6`SmcCloseConnection+0x18()
Start date:
2012-11-16
Due date:
% Done:
100%
Estimated time:
Difficulty:
Medium
Tags:
needs-triage
Description
Metacity crashed today with this stack:
> ::status debugging core file of metacity (32-bit) from telcontar file: /usr/bin/metacity initial argv: metacity threading model: native threads status: process terminated by SIGSEGV (Segmentation Fault), addr=4 > ::stack libSM.so.6`SmcCloseConnection+0x18(0, 0, 0, 80914d4) disconnect+0x1b(8138a64, 0, 8047508, feced68d, 81a01a8, 1) process_ice_messages+0x2c(81a01a8, 1, 819dce8, feced659) libglib-2.0.so.0.2501.0`g_io_unix_dispatch+0x45(81b7128, 80914bc, 819dce8, 8047570) libglib-2.0.so.0.2501.0`g_main_context_dispatch+0x25f(8138a60, 0, 81d23a0, 9) libglib-2.0.so.0.2501.0`g_main_context_iterate+0x46d(8138a60, 1, 1, 8131a90) libglib-2.0.so.0.2501.0`g_main_loop_run+0x1d7(8132450, 8, 8047a68, 8089513) main+0x892(1, 8047a98, 8047aa0, 8047a8c) _start+0x7d(1, 8047b98, 0, 8047ba1, 8047bcf, 8047c0a) >Here are similar reports:
Updated by Marcel Telka about 11 years ago
Please find the core file here:
http://telka.sk/illumos/3369/core.metacity.101.1353090962.bz2
Updated by Ken Mays almost 11 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
This is resolved in the newer JDS package release. Please update.
Actions