Bug 1074159

Summary: [abrt] workrave: __pthread_mutex_lock(): workrave killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Matthew Cline <matt>
Component: workraveAssignee: Christopher Meng <i>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: d33tah, i, metherid, Wilhelm.Buchmueller
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/0955f51661dcea741655df541708b502ef9664d9
Whiteboard: abrt_hash:323a7eb51fdc0473a22ba873b52344156f591d07
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 19:21:18 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 Matthew Cline 2014-03-08 11:43:46 UTC 
Description of problem:
There were two instances of Workrave in the systray.  I quit from both of them, and the crash happened.


The two instances might have happened because I'd set up Workrave to autostart with KDE (via ~/.kde/Autostart) but also had Workrave restarted by the KDE session manager.  However, there was only on instance of the workrave process.

Version-Release number of selected component:
workrave-1.10-4.fc20

Additional info:
reporter:       libreport-2.1.12
backtrace_rating: 4
cmdline:        workrave --sm-client-id 1028c1d320b210000139420652900000014900166
crash_function: __pthread_mutex_lock
executable:     /usr/bin/workrave
kernel:         3.13.5-202.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 __pthread_mutex_lock at ../nptl/pthread_mutex_lock.c:66
 #1 g_mutex_lock at gthread-posix.c:213
 #2 g_system_thread_wait at gthread-posix.c:1170
 #3 g_thread_join at gthread.c:964
 #4 Thread::wait at GlibThread.cc:74
 #5 RecordInputMonitor::~RecordInputMonitor at RecordInputMonitor.cc:121
 #7 ActivityMonitor::~ActivityMonitor at ActivityMonitor.cc:91
 #9 Core::~Core at Core.cc:136
 #11 GUI::~GUI at GUI.cc:164
 #13 run at main.cc:70

Potential duplicate: bug 952068
Comment 1 Matthew Cline 2014-03-08 11:43:51 UTC 
Created attachment 872194 [details]
File: backtrace
Comment 2 Matthew Cline 2014-03-08 11:43:52 UTC 
Created attachment 872195 [details]
File: cgroup
Comment 3 Matthew Cline 2014-03-08 11:43:54 UTC 
Created attachment 872196 [details]
File: core_backtrace
Comment 4 Matthew Cline 2014-03-08 11:43:55 UTC 
Created attachment 872197 [details]
File: dso_list
Comment 5 Matthew Cline 2014-03-08 11:43:57 UTC 
Created attachment 872198 [details]
File: environ
Comment 6 Matthew Cline 2014-03-08 11:43:58 UTC 
Created attachment 872199 [details]
File: exploitable
Comment 7 Matthew Cline 2014-03-08 11:44:00 UTC 
Created attachment 872200 [details]
File: limits
Comment 8 Matthew Cline 2014-03-08 11:44:01 UTC 
Created attachment 872201 [details]
File: maps
Comment 9 Matthew Cline 2014-03-08 11:44:03 UTC 
Created attachment 872202 [details]
File: open_fds
Comment 10 Matthew Cline 2014-03-08 11:44:04 UTC 
Created attachment 872203 [details]
File: proc_pid_status
Comment 11 Matthew Cline 2014-03-08 11:44:05 UTC 
Created attachment 872204 [details]
File: var_log_messages
Comment 12 Jacek Wielemborek 2014-10-04 17:19:49 UTC 
Another user experienced a similar problem:

I ran two workraves at once. I don't really remember - either I tried to close one or ran "break" mode manually.

reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/bin/workrave
crash_function: __pthread_mutex_lock
executable:     /usr/bin/workrave
kernel:         3.16.3-200.fc20.x86_64
package:        workrave-1.10-4.fc20
reason:         workrave killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 13 Fedora End Of Life 2015-05-29 11:11:41 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 14 Fedora End Of Life 2015-06-29 19:21:18 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.