Bug 1000756

Summary: [abrt] menu-cache-0.4.1-3.fc20: g_realloc: Process /usr/libexec/menu-cached was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Moez Roy <moez.roy>
Component: menu-cacheAssignee: Christoph Wickert <christoph.wickert>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: awilliam, christoph.wickert, moez.roy, mruckman, robatino
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:8def4e61f8831ffccec1ccc3c43ca753dde4af90 RejectedBlocker
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-14 14:27:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Moez Roy 2013-08-24 23:01:38 UTC 
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
Comment 1 Moez Roy 2013-08-24 23:01:42 UTC 
Created attachment 789970 [details]
File: backtrace
Comment 2 Moez Roy 2013-08-24 23:01:44 UTC 
Created attachment 789971 [details]
File: cgroup
Comment 3 Moez Roy 2013-08-24 23:01:47 UTC 
Created attachment 789972 [details]
File: core_backtrace
Comment 4 Moez Roy 2013-08-24 23:01:49 UTC 
Created attachment 789973 [details]
File: dso_list
Comment 5 Moez Roy 2013-08-24 23:01:51 UTC 
Created attachment 789974 [details]
File: environ
Comment 6 Moez Roy 2013-08-24 23:01:54 UTC 
Created attachment 789975 [details]
File: exploitable
Comment 7 Moez Roy 2013-08-24 23:01:56 UTC 
Created attachment 789976 [details]
File: limits
Comment 8 Moez Roy 2013-08-24 23:01:59 UTC 
Created attachment 789977 [details]
File: maps
Comment 9 Moez Roy 2013-08-24 23:02:01 UTC 
Created attachment 789978 [details]
File: open_fds
Comment 10 Moez Roy 2013-08-24 23:02:03 UTC 
Created attachment 789979 [details]
File: proc_pid_status
Comment 11 Moez Roy 2013-08-24 23:02:06 UTC 
Created attachment 789980 [details]
File: var_log_messages
Comment 12 Adam Williamson 2013-11-06 05:15:17 UTC 
You did not provide any reproduction information for this crash, and I've never seen it. Why would it constitute a blocker?
Comment 13 Vincent Danen 2013-11-06 17:26:55 UTC 
Client crashes are not typically regarded as security flaws if the only issue is a crash.  Removing the security bits.
Comment 14 Mike Ruckman 2013-11-06 17:40:45 UTC 
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
Comment 15 Moez Roy 2013-11-07 09:26:37 UTC 
(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.
Comment 16 Adam Williamson 2013-11-07 09:39:24 UTC 
Bugs in desktops other than GNOME and KDE cannot block release, per policy.
Comment 17 Christoph Wickert 2013-11-14 14:27:24 UTC 

*** This bug has been marked as a duplicate of bug 973855 ***