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
Created attachment 872194 [details] File: backtrace
Created attachment 872195 [details] File: cgroup
Created attachment 872196 [details] File: core_backtrace
Created attachment 872197 [details] File: dso_list
Created attachment 872198 [details] File: environ
Created attachment 872199 [details] File: exploitable
Created attachment 872200 [details] File: limits
Created attachment 872201 [details] File: maps
Created attachment 872202 [details] File: open_fds
Created attachment 872203 [details] File: proc_pid_status
Created attachment 872204 [details] File: var_log_messages
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
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.
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.