Version-Release number of selected component: xfdesktop-4.10.2-2.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: xfdesktop crash_function: magazine_chain_pop_head executable: /usr/bin/xfdesktop kernel: 3.12.6-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 magazine_chain_pop_head at gslice.c:545 #1 thread_memory_magazine1_alloc at gslice.c:848 #2 g_slice_alloc at gslice.c:1007 #3 gdk_threads_add_idle_full at gdk.c:595 #4 gdk_window_schedule_update at gdkwindow.c:5345 #5 gdk_window_invalidate_maybe_recurse_full at gdkwindow.c:5986 #6 gdk_window_invalidate_region_full at gdkwindow.c:6041 #7 gdk_window_invalidate_rect_full at gdkwindow.c:5823 #8 gdk_window_invalidate_rect at gdkwindow.c:5843 #9 gtk_widget_queue_draw_area at gtkwidget.c:3713
Created attachment 846433 [details] File: backtrace
Created attachment 846434 [details] File: cgroup
Created attachment 846435 [details] File: core_backtrace
Created attachment 846436 [details] File: dso_list
Created attachment 846437 [details] File: environ
Created attachment 846438 [details] File: exploitable
Created attachment 846439 [details] File: limits
Created attachment 846440 [details] File: maps
Created attachment 846441 [details] File: open_fds
Created attachment 846442 [details] File: proc_pid_status
Created attachment 846443 [details] File: var_log_messages
What were you doing when this happened? Can you duplicate it?
#1 cause of my xfdesktop crashes is pressing Alt+Space to get foreground app's window menu -- to close it by pressing C Had been happening for years, hard to replicate on purpose (most of the time everything works as expected)
Happened today again Likely same as much older abandoned bugs: bug 711220, bug 663516 Now that I've done a fresh install, ABRT works again and this bug is captured in its log...
ok. I'll try and make something of the traceback...
FYI, the bug keeps hitting me every day -- 2x on 6th, 2x on 7th, once on 8th, and once today (so far) Luckily, the window decorations come right back in a second, and there's no productivity/data loss.. it's just something annoying
11 times yesterday, according to ABRT.. if anyone is keeping count...
If you login to a text vty and do: export G_SLICE=always-malloc startxfce4 Does the problem show up on that session?
Didn't show up on that session, but I didn't leave that session running for too long - it had other bugs. I added the export statement to /etc/profile.d/foo.conf but it looks like that doesn't apply to the X process.. is there a better way than hacking a wrapper for /usr/sbin/lightdm? I'll try that, next
Try /etc/environment ?
added to /etc/environment That seems to cause bug 1063513
Another user experienced a similar problem: yum update reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: xfdesktop --display :0.0 --sm-client-id 2df3d52d9-2ee8-46a7-8885-16559c121628 crash_function: magazine_chain_pop_head executable: /usr/bin/xfdesktop kernel: 3.13.8-200.fc20.i686 package: xfdesktop-4.10.2-2.fc20 reason: xfdesktop killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.