libreport version: 2.0.7 abrt_version: 2.0.6 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: magazine_chain_pop_head executable: /usr/bin/gnome-shell kernel: 3.1.4-1.fc16.x86_64 pid: 2022 pwd: /home/lancelot reason: Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV) time: Sun 11 Dec 2011 11:36:27 PM HKT uid: 1000 username: lancelot backtrace: Text file, 86768 bytes build_ids: Text file, 6562 bytes dso_list: Text file, 20483 bytes environ: Text file, 2719 bytes maps: Text file, 81289 bytes smolt_data: Text file, 3360 bytes var_log_messages: Text file, 14805 bytes xsession_errors: :(gnome-shell:1834): folks-DEBUG: individual-aggregator.vala:305: Setting primary store IDs to defaults. :(gnome-shell:1834): folks-DEBUG: individual-aggregator.vala:333: Primary store IDs are 'eds' and 'system'. :(gnome-shell:1834): folks-WARNING **: Failed to find primary PersonaStore with type ID 'eds' and ID 'system'. :(gnome-shell:1834): Clutter-WARNING **: Unable to compile the GLSL shader: Fragment shader failed to compile with the following errors: :gnome-shell-calendar-server[1961]: Got HUP on stdin - exiting :gnome-session[1595]: WARNING: Application 'gnome-shell.desktop' killed by signal :(gnome-shell:2111): folks-DEBUG: individual-aggregator.vala:305: Setting primary store IDs to defaults. :(gnome-shell:2111): folks-DEBUG: individual-aggregator.vala:333: Primary store IDs are 'eds' and 'system'. :(gnome-shell:2111): folks-WARNING **: Failed to find primary PersonaStore with type ID 'eds' and ID 'system'. :(gnome-shell:2111): Clutter-WARNING **: Unable to compile the GLSL shader: Fragment shader failed to compile with the following errors:
Created attachment 545355 [details] File: dso_list
Created attachment 545356 [details] File: environ
Created attachment 545357 [details] File: build_ids
Created attachment 545358 [details] File: smolt_data
Created attachment 545359 [details] File: var_log_messages
Created attachment 545360 [details] File: maps
Created attachment 545361 [details] File: backtrace
*** This bug has been marked as a duplicate of bug 768143 ***