Red Hat Bugzilla – Bug 1290891
[abrt] menu-cache: g_path_is_absolute(): menu-cached killed by SIGSEGV
Last modified: 2016-11-24 09:45:16 EST
Version-Release number of selected component:
cmdline: /usr/libexec/menu-cache/menu-cached /tmp/.menu-cached-:0-mastaiza
runlevel: N 5
Thread no. 1 (10 frames)
#0 g_path_is_absolute at gfileutils.c:2100
#1 canonicalize_filename at glocalfile.c:204
#2 _g_local_file_new at glocalfile.c:302
#3 g_daemon_vfs_get_file_for_path at gdaemonvfs.c:383
#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:1600
#9 _g_closure_invoke_va at gclosure.c:864
Potential duplicate: bug 882441
Created attachment 1104774 [details]
Created attachment 1104775 [details]
Created attachment 1104776 [details]
Created attachment 1104777 [details]
Created attachment 1104778 [details]
Created attachment 1104779 [details]
Created attachment 1104780 [details]
Created attachment 1104781 [details]
Created attachment 1104782 [details]
Created attachment 1104783 [details]
Created attachment 1104784 [details]
Created attachment 1104785 [details]
Created attachment 1104786 [details]
Another user experienced a similar problem:
uninstalling LXQT group
cmdline: /usr/libexec/menu-cache/menu-cached /tmp/.menu-cached-:0-cheese
reason: menu-cached killed by SIGSEGV
runlevel: N 5
Created attachment 1116643 [details]
This is probably upstream issue https://github.com/lxde/menu-cache/issues/8:
menu-cached crashes when the *.menu file it's monitoring gets removed, the small time span the file isn't available when it's corresponding package gets updated is sufficient to trigger the crash.
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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'
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 23 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.