Version-Release number of selected component: menu-cache-0.4.1-3.fc20 Additional info: reporter: libreport-2.1.6 backtrace_rating: 4 cmdline: /usr/libexec/menu-cached crash_function: g_realloc executable: /usr/libexec/menu-cached kernel: 3.11.0-0.rc6.git4.1.fc21.x86_64 runlevel: N 5 uid: 1000 Truncated backtrace: Thread no. 1 (7 frames) #3 g_realloc at gmem.c:169 #4 g_string_maybe_expand at gstring.c:107 #5 g_string_sized_new at gstring.c:132 #6 g_io_channel_fill_buffer at giochannel.c:1500 #7 g_io_channel_read_line_backend at giochannel.c:1787 #8 g_io_channel_read_line at giochannel.c:1687 #9 on_client_data_in at menu-cached.c:601 Potential duplicate: bug 980909
Created attachment 789970 [details] File: backtrace
Created attachment 789971 [details] File: cgroup
Created attachment 789972 [details] File: core_backtrace
Created attachment 789973 [details] File: dso_list
Created attachment 789974 [details] File: environ
Created attachment 789975 [details] File: exploitable
Created attachment 789976 [details] File: limits
Created attachment 789977 [details] File: maps
Created attachment 789978 [details] File: open_fds
Created attachment 789979 [details] File: proc_pid_status
Created attachment 789980 [details] File: var_log_messages
You did not provide any reproduction information for this crash, and I've never seen it. Why would it constitute a blocker?
Client crashes are not typically regarded as security flaws if the only issue is a crash. Removing the security bits.
Discussed in 2013-11-06 Blocker Review Meeting [1]. Voted a RejectedBlocker because all [2] these crashes (reported by abrt) don't have reproducers and aren't in crucial components. Please re-propose them later when reproducers are known and we can reconsider blocker status. [1] http://meetbot.fedoraproject.org/fedora-blocker-review/2013-11-06/ [2] bug 1000669 bug 1000752 bug 1000756 bug 1007121 bug 1015347 bug 1016935
(In reply to Adam Williamson from comment #12) > You did not provide any reproduction information for this crash, and I've > never seen it. Why would it constitute a blocker? It happens on LXDE desktop. Work on it for a while and you get this crash.
Bugs in desktops other than GNOME and KDE cannot block release, per policy.
*** This bug has been marked as a duplicate of bug 973855 ***