Description of problem: I did not even know it happened... Version-Release number of selected component: xfdesktop-4.10.2-4.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: xfdesktop --display :0.0 --sm-client-id 28061416a-494b-4a4e-b1f1-711acb0948b8 crash_function: magazine_chain_pop_head executable: /usr/bin/xfdesktop kernel: 3.17.0-301.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1005 Truncated backtrace: Thread no. 1 (10 frames) #0 magazine_chain_pop_head at gslice.c:539 #1 thread_memory_magazine1_alloc at gslice.c:842 #2 g_slice_alloc at gslice.c:998 #3 g_list_prepend at glist.c:308 #4 pango_attr_iterator_next at pango-attributes.c:1710 #5 pango_attr_list_get_iterator at pango-attributes.c:1634 #6 pango_layout_check_lines at pango-layout.c:3926 #7 pango_layout_get_extents_internal at pango-layout.c:2587 #8 pango_layout_get_pixel_extents at pango-layout.c:2808 #9 xfdesktop_icon_view_setup_pango_layout at xfdesktop-icon-view.c:2778 Potential duplicate: bug 1049119
Created attachment 947549 [details] File: backtrace
Created attachment 947550 [details] File: cgroup
Created attachment 947551 [details] File: core_backtrace
Created attachment 947552 [details] File: dso_list
Created attachment 947553 [details] File: environ
Created attachment 947554 [details] File: exploitable
Created attachment 947555 [details] File: limits
Created attachment 947556 [details] File: maps
Created attachment 947557 [details] File: open_fds
Created attachment 947558 [details] File: proc_pid_status
Created attachment 947559 [details] File: var_log_messages
Do you see this regularly or often?
No just one so far.... As said, I didn't even know it crashed, nor do I know what caused it.
Another user experienced a similar problem: starting with my current session. reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: xfdesktop --display :0.0 --sm-client-id 2bf6021a5-ba62-4071-895d-2d3341461d41 crash_function: magazine_chain_pop_head executable: /usr/bin/xfdesktop kernel: 3.17.4-301.fc21.x86_64 package: xfdesktop-4.10.3-1.fc21 reason: xfdesktop killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1001
Another user experienced a similar problem: Starting my current session with xfce desktop. reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: xfdesktop --display :0.0 --sm-client-id 2bf6021a5-ba62-4071-895d-2d3341461d41 crash_function: magazine_chain_pop_head executable: /usr/bin/xfdesktop kernel: 3.17.4-301.fc21.x86_64 package: xfdesktop-4.10.3-1.fc21 reason: xfdesktop killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1001
Another user experienced a similar problem: I do not know. I walked away from the keyboard for about 20 minutes and when I returned I noticed the Abort system had placed an icon in the system tray. When I opened it I found that xfdesktop had aborted with SIGSEGV (even though the desktop appears to be running normally; this bug report has been filed from that supposedly aborted desktop). reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: xfdesktop --display :0.0 --sm-client-id 21739ae64-e05b-4d50-8568-73b0cd901010 crash_function: magazine_chain_pop_head executable: /usr/bin/xfdesktop kernel: 3.18.7-200.fc21.x86_64 package: xfdesktop-4.10.3-3.fc21 reason: xfdesktop killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1002
Another user experienced a similar problem: Once xfdesktop starts crashing in this manner it seems to keep doing it multiple times. I am not sure what exactly causes. I believe I was using firefox when the initial crash occured. reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: xfdesktop --display :0.0 --sm-client-id 291ba51e1-898e-42de-b2f7-15efa52d86e3 crash_function: magazine_chain_pop_head executable: /usr/bin/xfdesktop kernel: 3.18.5-201.fc21.x86_64 package: xfdesktop-4.10.3-3.fc21 reason: xfdesktop killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 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.