Hide Forgot
Description of problem: When choosing "Unavailable" status from user menu or within Empathy contact list window, gnome-shell crashes. Version-Release number of selected component (if applicable): gnome-shell-3.2.1-2.fc16.x86_64 empathy-3.2.1.2-1.fc16.x86_64 How reproducible: 8/10 (very rarely works fine, didn't find any correlation yet) Steps to Reproduce: 1. Set IM status to Available. 2. Set IM status to Unavailable/Offline (either via user menu or Empathy). 3. Desktop crashes. Actual results: Desktop crashes and reloads (sometimes reloads with black screen suggesting one of the extensions caused trouble). Expected results: IM status changes to offline. Additional info: * Output in /var/log/messages - when status changed via user menu: Nov 25 09:41:42 v3350 kernel: [37600.340051] gnome-shell[27205]: segfault at 20 ip 000000367e41aee8 sp 00007fffea7d07a0 error 6 in libglib-2.0.so.0.3000.1[367e400000+11e000] Nov 25 09:41:42 v3350 gnome-session[6955]: WARNING: Application 'gnome-shell.desktop' killed by signal * Output in /var/log/messages - when status changed in Empathy: Nov 25 09:51:15 v3350 kernel: [38173.042617] empathy[32586]: segfault at 20 ip 000000367e41aee8 sp 00007fff9c113c60 error 6 in libglib-2.0.so.0.3000.1[367e400000+11e000] Nov 25 09:51:15 v3350 kernel: [38173.043449] gnome-shell[31163]: segfault at 20 ip 000000367e41aee8 sp 00007ffffa552140 error 6 in libglib-2.0.so.0.3000.1[367e400000+11e000] Nov 25 09:51:15 v3350 gnome-session[6955]: WARNING: Application 'gnome-shell.desktop' killed by signal * Shell extensions installed: gnome-shell-extension-apps-menu-3.2.0-2.fc16.noarch gnome-shell-theme-atolm-1.0-1.fc16.noarch gnome-shell-extension-icon-manager-0-0.4.gitc34779c.fc16.noarch gnome-shell-extension-native-window-placement-3.2.0-2.fc16.noarch gnome-shell-extension-common-3.2.0-2.fc16.noarch gnome-shell-extension-user-theme-3.2.0-2.fc16.noarch gnome-shell-extension-alternative-status-menu-3.2.0-2.fc16.noarch gnome-shell-extension-theme-selector-0.9-3.fc16.noarch
Probably the same as bug 748200 - without a detailed traceback (as reported by ABRT) it's hard to be completely sure. *** This bug has been marked as a duplicate of bug 748200 ***