Bug 1046005 - [abrt] xfwm4: strchr(): xfwm4 killed by SIGSEGV
Summary: [abrt] xfwm4: strchr(): xfwm4 killed by SIGSEGV
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xfwm4
Version: 20
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kevin Fenzi
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:51f36ac7009f238aa439bed446d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-23 07:48 UTC by Herbert Carl Meyer
Modified: 2015-06-30 00:47 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-30 00:47:51 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (31.55 KB, text/plain)
2013-12-23 07:48 UTC, Herbert Carl Meyer
no flags Details
File: cgroup (159 bytes, text/plain)
2013-12-23 07:48 UTC, Herbert Carl Meyer
no flags Details
File: core_backtrace (4.10 KB, text/plain)
2013-12-23 07:48 UTC, Herbert Carl Meyer
no flags Details
File: dso_list (3.26 KB, text/plain)
2013-12-23 07:48 UTC, Herbert Carl Meyer
no flags Details
File: environ (1.52 KB, text/plain)
2013-12-23 07:48 UTC, Herbert Carl Meyer
no flags Details
File: exploitable (82 bytes, text/plain)
2013-12-23 07:48 UTC, Herbert Carl Meyer
no flags Details
File: limits (1.29 KB, text/plain)
2013-12-23 07:48 UTC, Herbert Carl Meyer
no flags Details
File: maps (28.09 KB, text/plain)
2013-12-23 07:48 UTC, Herbert Carl Meyer
no flags Details
File: open_fds (303 bytes, text/plain)
2013-12-23 07:48 UTC, Herbert Carl Meyer
no flags Details
File: proc_pid_status (785 bytes, text/plain)
2013-12-23 07:48 UTC, Herbert Carl Meyer
no flags Details
File: var_log_messages (518 bytes, text/plain)
2013-12-23 07:48 UTC, Herbert Carl Meyer
no flags Details

Description Herbert Carl Meyer 2013-12-23 07:48:29 UTC
Description of problem:
fighting with rhythmbox about mp3 plugins

Version-Release number of selected component:
xfwm4-4.10.1-2.fc20

Additional info:
reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        xfwm4 --display :0.0 --sm-client-id 23eba379c-43a9-4c7a-9436-293a11981ee8
crash_function: strchr
executable:     /usr/bin/xfwm4
kernel:         3.12.5-302.fc20.i686+PAE
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 strchr at ../sysdeps/i386/i686/multiarch/strchr-sse2.S:90
 #1 frameDrawWin at frame.c:964
 #2 update_frame_idle_cb at frame.c:1224
 #8 gtk_main at gtkmain.c:1257
 #9 clientButtonPress at client.c:3743
 #10 handleButtonPress at events.c:929
 #11 handleEvent at events.c:2250
 #12 xfwm4_event_filter at events.c:2345
 #13 eventXfwmFilter at event_filter.c:158
 #14 gdk_event_apply_filters at gdkevents-x11.c:356

Potential duplicate: bug 879696

Comment 1 Herbert Carl Meyer 2013-12-23 07:48:33 UTC
Created attachment 840708 [details]
File: backtrace

Comment 2 Herbert Carl Meyer 2013-12-23 07:48:35 UTC
Created attachment 840709 [details]
File: cgroup

Comment 3 Herbert Carl Meyer 2013-12-23 07:48:37 UTC
Created attachment 840710 [details]
File: core_backtrace

Comment 4 Herbert Carl Meyer 2013-12-23 07:48:40 UTC
Created attachment 840711 [details]
File: dso_list

Comment 5 Herbert Carl Meyer 2013-12-23 07:48:41 UTC
Created attachment 840712 [details]
File: environ

Comment 6 Herbert Carl Meyer 2013-12-23 07:48:43 UTC
Created attachment 840713 [details]
File: exploitable

Comment 7 Herbert Carl Meyer 2013-12-23 07:48:44 UTC
Created attachment 840714 [details]
File: limits

Comment 8 Herbert Carl Meyer 2013-12-23 07:48:46 UTC
Created attachment 840715 [details]
File: maps

Comment 9 Herbert Carl Meyer 2013-12-23 07:48:48 UTC
Created attachment 840716 [details]
File: open_fds

Comment 10 Herbert Carl Meyer 2013-12-23 07:48:49 UTC
Created attachment 840717 [details]
File: proc_pid_status

Comment 11 Herbert Carl Meyer 2013-12-23 07:48:51 UTC
Created attachment 840718 [details]
File: var_log_messages

Comment 12 Kevin Fenzi 2013-12-23 17:07:00 UTC
Can you get this crash to happen again? Or is it sporadic/unknown to reproduce?

Comment 13 Herbert Carl Meyer 2013-12-23 19:42:17 UTC
I don't know. I was repeatably closing dialog boxes on rhythmbox, it is too stupid to recognize that I have the required codec installed. 

Compounding the error is a small (1024x600) display on the netbook in use. If if reoccurs, I will report it. 

Don't worry, I remain clumsy and short tempered, at 2am. Good QA tester.

Comment 14 Fedora End Of Life 2015-05-29 10:07:38 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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'
of '20'.

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 20 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.

Comment 15 Fedora End Of Life 2015-06-30 00:47:51 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.


Note You need to log in before you can comment on or make changes to this bug.