Bug 544322

Summary: segfault at 11e ip 003fb9e1 sp bfd3b260 error 6 in libSM.so.6.0.0[3fa000+7000]
Product: [Fedora] Fedora Reporter: Eddie Lania <eddie>
Component: metacityAssignee: Owen Taylor <otaylor>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: masao-takahashi, otaylor
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-12-17 19:22:16 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Eddie Lania 2009-12-04 15:54:06 UTC 
Description of problem: Metacity segfaults:
kernel: metacity[1519]: segfault at 11e ip 003fb9e1 sp bfd3b260 error 6 in libSM.so.6.0.0[3fa000+7000]


Version-Release number of selected component (if applicable):
metacity-2.28.0-11.fc12.i686

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:segfault


Expected results:no segfault


Additional info:[root@p3000fedora ~]# grep metacity /var/log/messages
Nov 30 19:00:27 p3000fedora kernel: metacity[1556]: segfault at 11e ip 003fb9e1 sp bf8cb310 error 6 in libSM.so.6.0.0[3fa000+7000]
Dec  2 17:25:57 p3000fedora yum: Updated: metacity-2.28.0-11.fc12.i686
Dec  2 17:26:18 p3000fedora yum: Updated: metacity-devel-2.28.0-11.fc12.i686
Dec  2 21:29:27 p3000fedora kernel: metacity[1528]: segfault at 11f ip 003fb9e1 sp bff969c0 error 6 in libSM.so.6.0.0[3fa000+7000]
Dec  3 19:03:07 p3000fedora yum: Updated: gnome-python2-metacity-2.28.0-2.fc12.i686
Dec  3 20:24:09 p3000fedora kernel: metacity[1519]: segfault at 11e ip 003fb9e1 sp bfd3b260 error 6 in libSM.so.6.0.0[3fa000+7000]
Comment 1 Owen Taylor 2009-12-17 19:22:16 UTC 
Guessing that this is the same as bug 539905, since that's a common cash inside libSM. I'm not aware of any way to turn the kernel reported crash address into a more exact line number.

*** This bug has been marked as a duplicate of bug 539905 ***