Bug 972408

Summary: [abrt] xfce4-power-manager-1.2.0-7.fc18: strcmp: Process /usr/bin/xfce4-power-manager was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Filippo <effeffe99>
Component: xfce4-power-managerAssignee: Christoph Wickert <christoph.wickert>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: admiller, christoph.wickert
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:da164f9dc9d127d3f609c0ce1d391dd3ddb81a9e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 21:44:21 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: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Filippo 2013-06-09 08:10:26 UTC 
Description of problem:
I don't know how reproduce it. I had finished my update with #yum update and it has crash, but not only it, all xfcs. I'm writing by my root account because my user account has totally crashed

Version-Release number of selected component:
xfce4-power-manager-1.2.0-7.fc18

Additional info:
reporter:       libreport-2.1.4
backtrace_rating: 4
cmdline:        xfce4-power-manager
crash_function: strcmp
executable:     /usr/bin/xfce4-power-manager
kernel:         3.6.10-4.fc18.x86_64
runlevel:       unknown
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 strcmp at ../sysdeps/x86_64/multiarch/strcmp-sse42.S:162
 #1 cache_glob_lookup_literal at xdgmimecache.c:387
 #2 cache_glob_lookup_file_name at xdgmimecache.c:637
 #3 __gio_xdg_cache_get_mime_types_from_file_name at xdgmimecache.c:835
 #4 _gio_xdg_get_mime_types_from_file_name at xdgmime.c:590
 #5 g_content_type_guess at gcontenttype.c:658
 #6 get_content_type at glocalfileinfo.c:1236
 #7 _g_local_file_info_get at glocalfileinfo.c:1701
 #8 g_local_file_query_info at glocalfile.c:1216
 #9 icon_info_ensure_scale_and_pixbuf at gtkicontheme.c:2906
Comment 1 Filippo 2013-06-09 08:10:31 UTC 
Created attachment 758692 [details]
File: backtrace
Comment 2 Filippo 2013-06-09 08:10:34 UTC 
Created attachment 758693 [details]
File: cgroup
Comment 3 Filippo 2013-06-09 08:10:37 UTC 
Created attachment 758694 [details]
File: core_backtrace
Comment 4 Filippo 2013-06-09 08:10:40 UTC 
Created attachment 758695 [details]
File: dso_list
Comment 5 Filippo 2013-06-09 08:10:43 UTC 
Created attachment 758696 [details]
File: environ
Comment 6 Filippo 2013-06-09 08:10:46 UTC 
Created attachment 758697 [details]
File: limits
Comment 7 Filippo 2013-06-09 08:10:50 UTC 
Created attachment 758698 [details]
File: maps
Comment 8 Filippo 2013-06-09 08:10:54 UTC 
Created attachment 758699 [details]
File: open_fds
Comment 9 Filippo 2013-06-09 08:10:58 UTC 
Created attachment 758700 [details]
File: proc_pid_status
Comment 10 Filippo 2013-06-09 08:11:01 UTC 
Created attachment 758701 [details]
File: var_log_messages
Comment 11 Fedora End Of Life 2013-12-21 13:55:49 UTC 
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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.
Comment 12 Fedora End Of Life 2014-02-05 21:44:21 UTC 
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.