Description of problem: Happened during basic use of the Shell in a 2014-12-04 Rawhide nightly Workstation image, in a qemu/kvm qxl/SPICE virt guest. Version-Release number of selected component: gnome-shell-3.15.2-1.fc22 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: check_fontmap_changed executable: /usr/bin/gnome-shell kernel: 3.18.0-0.rc7.git1.1.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 check_fontmap_changed at pango-context.c:1858 #1 pango_context_get_serial at pango-context.c:1891 #2 check_context_changed at pango-layout.c:1316 #3 pango_layout_check_lines at pango-layout.c:3911 #4 pango_layout_get_extents_internal at pango-layout.c:2587 #5 pango_layout_get_extents at pango-layout.c:2782 #6 clutter_text_paint at ./clutter-text.c:2339 #7 _g_closure_invoke_va at gclosure.c:831 #10 clutter_actor_continue_paint at ./clutter-actor.c:3955 #11 clutter_actor_paint at ./clutter-actor.c:3875 Potential duplicate: bug 1009605
Created attachment 964834 [details] File: backtrace
Created attachment 964835 [details] File: cgroup
Created attachment 964836 [details] File: core_backtrace
Created attachment 964837 [details] File: dso_list
Created attachment 964838 [details] File: environ
Created attachment 964839 [details] File: exploitable
Created attachment 964840 [details] File: limits
Created attachment 964841 [details] File: maps
Created attachment 964842 [details] File: open_fds
Created attachment 964843 [details] File: proc_pid_status
Created attachment 964844 [details] File: var_log_messages
Proposing as F22 Final blocker, criterion "There must be no SELinux denial notifications or crash notifications on boot of or during installation from a release-blocking live image, or at first login after a default install of a release-blocking desktop." - https://fedoraproject.org/wiki/Fedora_21_Final_Release_Criteria#SELinux_and_crash_notifications , this happened near the end of a live install, though I think it was just coincidence and it might've crashed just sitting at or playing around in the desktop.
Discussed at today's blocker review meeting [1]. We decided to delay the decision. This bug might have gone stale in the past month. Will revisit next week after we've attempted to reproduce with more recent media. [1] http://meetbot.fedoraproject.org/fedora-blocker-review/2015-01-07/
I re-tested with 2015-01-01 (the last time live nightly compose succeeded) and didn't see this again, so either it's been fixed or it's random...removing blocker proposal at least. GNOME folks, might this have got fixed upstream?
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.