Bug 902291 - [abrt] workrave-1.9.911-0.1.20130107git6f9bc5d.fc18: Process /usr/bin/workrave was killed by signal 11 (SIGSEGV)
Summary: [abrt] workrave-1.9.911-0.1.20130107git6f9bc5d.fc18: Process /usr/bin/workrav...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: workrave
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomas Mraz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5181a27a1f80d3f17cdc63c6163...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-21 10:18 UTC by Christof Damian
Modified: 2014-02-05 15:30 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-05 15:30:27 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (17.98 KB, text/plain)
2013-01-21 10:18 UTC, Christof Damian
no flags Details
File: cgroup (138 bytes, text/plain)
2013-01-21 10:18 UTC, Christof Damian
no flags Details
File: core_backtrace (1.39 KB, text/plain)
2013-01-21 10:18 UTC, Christof Damian
no flags Details
File: dso_list (10.95 KB, text/plain)
2013-01-21 10:18 UTC, Christof Damian
no flags Details
File: environ (2.05 KB, text/plain)
2013-01-21 10:18 UTC, Christof Damian
no flags Details
File: limits (1.29 KB, text/plain)
2013-01-21 10:18 UTC, Christof Damian
no flags Details
File: maps (56.47 KB, text/plain)
2013-01-21 10:18 UTC, Christof Damian
no flags Details
File: open_fds (270 bytes, text/plain)
2013-01-21 10:19 UTC, Christof Damian
no flags Details
File: proc_pid_status (922 bytes, text/plain)
2013-01-21 10:19 UTC, Christof Damian
no flags Details
File: smolt_data (2.66 KB, text/plain)
2013-01-21 10:19 UTC, Christof Damian
no flags Details
File: var_log_messages (1020 bytes, text/plain)
2013-01-21 10:19 UTC, Christof Damian
no flags Details

Description Christof Damian 2013-01-21 10:18:39 UTC
Description of problem:
Login into a session. Workrave started automatically. 

Version-Release number of selected component:
workrave-1.9.911-0.1.20130107git6f9bc5d.fc18

Additional info:
backtrace_rating: 3
cmdline:        workrave --sm-client-id 107d9150028d2ab0e7135875949023439300000024640052
executable:     /usr/bin/workrave
kernel:         3.7.2-201.fc18.x86_64
remote_result:  NOTFOUND
uid:            1000

Truncated backtrace:
Thread no. 1 (6 frames)
 #0 ??
 #1 RecordInputMonitor::~RecordInputMonitor at RecordInputMonitor.cc:122
 #3 ActivityMonitor::~ActivityMonitor at ActivityMonitor.cc:91
 #5 Core::~Core at Core.cc:136
 #7 GUI::~GUI at GUI.cc:164
 #9 run at main.cc:70

Comment 1 Christof Damian 2013-01-21 10:18:43 UTC
Created attachment 684204 [details]
File: backtrace

Comment 2 Christof Damian 2013-01-21 10:18:46 UTC
Created attachment 684205 [details]
File: cgroup

Comment 3 Christof Damian 2013-01-21 10:18:49 UTC
Created attachment 684206 [details]
File: core_backtrace

Comment 4 Christof Damian 2013-01-21 10:18:51 UTC
Created attachment 684207 [details]
File: dso_list

Comment 5 Christof Damian 2013-01-21 10:18:53 UTC
Created attachment 684208 [details]
File: environ

Comment 6 Christof Damian 2013-01-21 10:18:55 UTC
Created attachment 684209 [details]
File: limits

Comment 7 Christof Damian 2013-01-21 10:18:58 UTC
Created attachment 684210 [details]
File: maps

Comment 8 Christof Damian 2013-01-21 10:19:00 UTC
Created attachment 684211 [details]
File: open_fds

Comment 9 Christof Damian 2013-01-21 10:19:02 UTC
Created attachment 684212 [details]
File: proc_pid_status

Comment 10 Christof Damian 2013-01-21 10:19:04 UTC
Created attachment 684213 [details]
File: smolt_data

Comment 11 Christof Damian 2013-01-21 10:19:06 UTC
Created attachment 684214 [details]
File: var_log_messages

Comment 12 alberth289346 2013-02-19 19:07:28 UTC
Confirmed, workrave crashes reliably here when you quit the application (and also when shutting down KDE, it seems. At least I am seeing crash reports from around that time, and the machine waits a long time before going down.).


Core was generated by `/usr/bin/workrave'.
Program terminated with signal 11, Segmentation fault.
#0  g_thread_join (thread=0x10) at gthread.c:960
960	gthread.c: No such file or directory.

Thread 2 (Thread 0x7f5375bb0700 (LWP 1438)):
#0  0x0000003748ae998d in poll () at ../sysdeps/unix/syscall-template.S:81
No locals.
#1  0x0000003748647d24 in g_main_context_poll (priority=2147483647, n_fds=3, fds=0x7f53680010c0, timeout=-1, context=0xf823a0) at gmain.c:3584
        poll_func = 0x3748655e00 <g_poll>
#2  g_main_context_iterate (context=0xf823a0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3285
        max_priority = 2147483647
        timeout = -1
        some_ready = <optimized out>
        nfds = 3
        allocated_nfds = <optimized out>
        fds = 0x7f53680010c0
#3  0x0000003748648182 in g_main_loop_run (loop=0xf04910) at gmain.c:3484
        __PRETTY_FUNCTION__ = "g_main_loop_run"
#4  0x000000375c6cc546 in gdbus_shared_thread_func (user_data=0xf82370) at gdbusprivate.c:277
        data = 0xf82370
#5  0x000000374866b605 in g_thread_proxy (data=0xf80630) at gthread.c:797
        thread = 0xf80630
#6  0x0000003749207d15 in start_thread (arg=0x7f5375bb0700) at pthread_create.c:308
        __res = <optimized out>
        pd = 0x7f5375bb0700
        now = <optimized out>
        unwind_buf = {cancel_jmp_buf = {{jmp_buf = {139996434204416, -7322345490761748724, 0, 237435490304, 139996434204416, 16262000, 7261815700624666380, -7345547108753576180}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
        not_first_call = 0
        pagesize_m1 = <optimized out>
        sp = <optimized out>
        freesize = <optimized out>
#7  0x0000003748af246d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114
No locals.

Thread 1 (Thread 0x7f537c7a39c0 (LWP 1436)):
#0  g_thread_join (thread=0x10) at gthread.c:960
        _g_boolean_var_ = <optimized out>
        real = 0x10
        retval = <optimized out>
        __PRETTY_FUNCTION__ = "g_thread_join"
#1  0x00000000004eb1b2 in Thread::wait (this=0xf09010) at GlibThread.cc:74
No locals.
#2  0x00000000004bbb98 in Core::~Core (this=0xeffb10, __in_chrg=<optimized out>) at Core.cc:132
No locals.
#3  0x00000000004bbe09 in Core::~Core (this=0xeffb10, __in_chrg=<optimized out>) at Core.cc:153
No locals.
#4  0x0000000000474647 in GUI::~GUI (this=0xe5cbf0, __in_chrg=<optimized out>) at GUI.cc:164
No locals.
#5  0x00000000004747f9 in GUI::~GUI (this=0xe5cbf0, __in_chrg=<optimized out>) at GUI.cc:177
No locals.
#6  0x0000000000496a98 in run (argc=1, argv=0x7fffb6e9def8) at main.cc:70
        gui = 0xe5cbf0
#7  0x0000003748a21a05 in __libc_start_main (main=0x4670d0 <main(int, char**)>, argc=1, ubp_av=0x7fffb6e9def8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffb6e9dee8) at libc-start.c:225
        result = <optimized out>
        unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, -7322345490761748724, 4625212, 140736262168304, 0, 0, 7322466249080205068, -7345550391296364788}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x4f3270 <__libc_csu_init>, 0x7fffb6e9def8}, data = {prev = 0x0, cleanup = 0x0, canceltype = 5190256}}}
        not_first_call = <optimized out>
#8  0x0000000000469365 in _start ()
        Gtk::PAPER_NAME_A3 = {static npos = 18446744073709551615, string_ = "iso_a3"}
        Gtk::PAPER_NAME_B5 = {static npos = 18446744073709551615, string_ = "iso_b5"}
        Gtk::PAPER_NAME_A4 = {static npos = 18446744073709551615, string_ = "iso_a4"}
        Gtk::PAPER_NAME_A5 = {static npos = 18446744073709551615, string_ = "iso_a5"}
        Gtk::PAPER_NAME_LEGAL = {static npos = 18446744073709551615, string_ = "na_legal"}
        Gtk::PAPER_NAME_LETTER = {static npos = 18446744073709551615, string_ = "na_letter"}
        Gtk::PAPER_NAME_EXECUTIVE = {static npos = 18446744073709551615, string_ = "na_executive"}

Comment 13 Lukas Marek 2013-07-03 14:13:45 UTC
Related to bug 968138 on F19. 

The bug is related to workrave ini configuration. I've compiled it with GConf configuration and the crashing is gone.

Note: I've compiled it right from the git (not using rpm build) but it was crashing with ini configuration files and was resolved by using gconf configuration.

Comment 14 James 2013-09-08 14:45:01 UTC
Workrave reports a problem at every login with XFCE desktop. I am running an up-to-date Fedora 18.

reporter:       libreport-2.1.6
backtrace_rating: 3
cmdline:        workrave
executable:     /usr/bin/workrave
kernel:         3.10.10-100.fc18.x86_64
package:        workrave-1.9.911-0.1.20130107git6f9bc5d.fc18
reason:         Process /usr/bin/workrave was killed by signal 11 (SIGSEGV)
runlevel:       N 5
uid:            1000

Comment 15 Alex 2013-11-17 16:41:17 UTC
Workrave is still crashing when exiting the program from inside KDE.
I have just updated all packages in Fedora 19 as of today.
I am goign to uninstall it anyway.

Comment 16 Fedora End Of Life 2013-12-21 10:39:01 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 17 Lukas Marek 2014-02-04 14:37:00 UTC
Just for completeness, bug 968138 is probably not related to this bug.

However, as it is still crashing in F-20, I've tried to properly debug the problem and filled a bug in Workrave bugzilla http://issues.workrave.org/show_bug.cgi?id=1148

Comment 18 Fedora End Of Life 2014-02-05 15:30:38 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.


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