Description of problem: Not clear how to reproduce. I think I'd just edited the text of an existing line in an account (Although looking at the backtrace I wonder if this is oxygen-gtk related?) Version-Release number of selected component: gnucash-2.4.13-5.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/bin/gnucash crash_function: gtk_widget_queue_draw executable: /usr/bin/gnucash kernel: 3.11.10-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 gtk_widget_queue_draw at gtkwidget.c:3779 #2 Oxygen::ToolBarStateData::delayedUpdate at /usr/src/debug/oxygen-gtk2-1.4.0/src/animations/oxygentoolbarstatedata.cpp:330 #3 Oxygen::ToolBarStateData::updateState at /usr/src/debug/oxygen-gtk2-1.4.0/src/animations/oxygentoolbarstatedata.cpp:176 #4 Oxygen::ToolBarStateData::childEnterNotifyEvent at /usr/src/debug/oxygen-gtk2-1.4.0/src/animations/oxygentoolbarstatedata.cpp:285 #5 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86 #10 gtk_widget_event_internal at gtkwidget.c:5017 #11 gtk_widget_event at gtkwidget.c:4814 #12 gtk_main_do_event at gtkmain.c:1698 #18 gtk_main at gtkmain.c:1257 #19 gnc_ui_start_event_loop at gnc-gnome-utils.c:668
Created attachment 833918 [details] File: backtrace
Created attachment 833919 [details] File: cgroup
Created attachment 833920 [details] File: core_backtrace
Created attachment 833921 [details] File: dso_list
Created attachment 833922 [details] File: environ
Created attachment 833923 [details] File: exploitable
Created attachment 833924 [details] File: limits
Created attachment 833925 [details] File: maps
Created attachment 833926 [details] File: proc_pid_status
Created attachment 833927 [details] File: var_log_messages
Can you reproduce this error at will? If so, can you try without the oxygen theme?
No, sorry - it doesn't seem to repeat
Hmm just hit the same one, as I say not repeatable at will, but does happen. The backtrace looks the same to me; gtk_widget_queue_draw->Oxygen::ToolBarStateData::delayedUpdate->updateState->childEnterNotifyEvent
*** Bug 1045950 has been marked as a duplicate of this bug. ***
CC'ing oxygen-gtk2 maintainers.
Is it crashes with oxygen-gtk2-1.4.1 ?
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
I'll give it a go with the newer oxygen, but since it's only does it ever month or two I'm not sure I could be sure either way,
Moving to oxygen-gtk2, in any case - the crash is in that component.
Current oxygen-gtk2 version 1.4.6 https://admin.fedoraproject.org/updates/FEDORA-2014-13566 Is it still crashes?
I haven't seen a crash in quite a while now. Also, I'm now moving over to xfce and thus away from oxygen-gtk so probably can't sensibly test.
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.