Bug 1293158

Summary: [abrt] menu-cache: g_path_is_absolute(): menu-cached killed by SIGSEGV
Product: [Fedora] Fedora Reporter: James Caldwell <forummail>
Component: menu-cacheAssignee: Christoph Wickert <christoph.wickert>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: christoph.wickert, mtasaka
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/ec08342042115ac4a4e08e2012fed2d4cbd12193
Whiteboard: abrt_hash:4410a83149c7f3ead40833f458f5e3397c605199;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 18:37:15 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: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description James Caldwell 2015-12-20 20:27:59 UTC
Version-Release number of selected component:
menu-cache-0.5.1-3.fc22

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        /usr/libexec/menu-cache/menu-cached
crash_function: g_path_is_absolute
executable:     /usr/libexec/menu-cache/menu-cached
global_pid:     2628
kernel:         4.2.7-200.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_path_is_absolute at gfileutils.c:2100
 #1 canonicalize_filename at glocalfile.c:205
 #2 _g_local_file_new at glocalfile.c:303
 #3 g_daemon_vfs_get_file_for_path at gdaemonvfs.c:385
 #4 do_reload at menu-cached.c:285
 #5 on_file_changed at menu-cached.c:382
 #6 ffi_call_unix64 at ../src/x86/unix64.S:76
 #7 ffi_call at ../src/x86/ffi64.c:525
 #8 g_cclosure_marshal_generic_va at gclosure.c:1561
 #9 _g_closure_invoke_va at gclosure.c:831

Potential duplicate: bug 882441

Comment 1 James Caldwell 2015-12-20 20:28:04 UTC
Created attachment 1108015 [details]
File: backtrace

Comment 2 James Caldwell 2015-12-20 20:28:05 UTC
Created attachment 1108017 [details]
File: cgroup

Comment 3 James Caldwell 2015-12-20 20:28:06 UTC
Created attachment 1108018 [details]
File: core_backtrace

Comment 4 James Caldwell 2015-12-20 20:28:07 UTC
Created attachment 1108019 [details]
File: dso_list

Comment 5 James Caldwell 2015-12-20 20:28:08 UTC
Created attachment 1108021 [details]
File: environ

Comment 6 James Caldwell 2015-12-20 20:28:09 UTC
Created attachment 1108022 [details]
File: limits

Comment 7 James Caldwell 2015-12-20 20:28:10 UTC
Created attachment 1108024 [details]
File: maps

Comment 8 James Caldwell 2015-12-20 20:28:11 UTC
Created attachment 1108025 [details]
File: mountinfo

Comment 9 James Caldwell 2015-12-20 20:28:12 UTC
Created attachment 1108026 [details]
File: namespaces

Comment 10 James Caldwell 2015-12-20 20:28:13 UTC
Created attachment 1108027 [details]
File: open_fds

Comment 11 James Caldwell 2015-12-20 20:28:14 UTC
Created attachment 1108029 [details]
File: proc_pid_status

Comment 12 James Caldwell 2015-12-20 20:28:15 UTC
Created attachment 1108031 [details]
File: var_log_messages

Comment 13 Fedora End Of Life 2016-07-19 18:37:15 UTC
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.