Bug 1010637 - [abrt] gnome-abrt-0.3.1-1.fc19: Process /usr/bin/python2.7 was killed by signal 11 (SIGSEGV) [NEEDINFO]
Summary: [abrt] gnome-abrt-0.3.1-1.fc19: Process /usr/bin/python2.7 was killed by sign...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-abrt
Version: 19
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jakub Filak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a03b7fcddd3badb4304a845ce9e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-22 07:58 UTC by mamii
Modified: 2016-12-01 00:45 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 17:17:43 UTC
Type: ---
Embargoed:
jfilak: needinfo?


Attachments (Terms of Use)
File: backtrace (65.47 KB, text/plain)
2013-09-22 07:58 UTC, mamii
no flags Details
File: cgroup (141 bytes, text/plain)
2013-09-22 07:58 UTC, mamii
no flags Details
File: core_backtrace (3.77 KB, text/plain)
2013-09-22 07:58 UTC, mamii
no flags Details
File: dso_list (13.38 KB, text/plain)
2013-09-22 07:58 UTC, mamii
no flags Details
File: environ (1.89 KB, text/plain)
2013-09-22 07:58 UTC, mamii
no flags Details
File: exploitable (82 bytes, text/plain)
2013-09-22 07:58 UTC, mamii
no flags Details
File: limits (1.29 KB, text/plain)
2013-09-22 07:58 UTC, mamii
no flags Details
File: maps (62.25 KB, text/plain)
2013-09-22 07:58 UTC, mamii
no flags Details
File: open_fds (3.83 KB, text/plain)
2013-09-22 07:59 UTC, mamii
no flags Details
File: proc_pid_status (928 bytes, text/plain)
2013-09-22 07:59 UTC, mamii
no flags Details
File: var_log_messages (795 bytes, text/plain)
2013-09-22 07:59 UTC, mamii
no flags Details

Description mamii 2013-09-22 07:58:32 UTC
Version-Release number of selected component:
gnome-abrt-0.3.1-1.fc19

Additional info:
reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        /usr/bin/python /usr/bin/gnome-abrt -p /home/dlepe/.cache/abrt/spool/oops-2013-09-22-08:42:28-2810-1
executable:     /usr/bin/python2.7
kernel:         3.11.1-200.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 ??
 #1 Oxygen::Style::renderWindowBackground at /usr/src/debug/oxygen-gtk3-1.2.0/src/oxygenstyle.cpp:348
 #2 Oxygen::Style::renderHoleBackground at /usr/src/debug/oxygen-gtk3-1.2.0/src/oxygenstyle.cpp:792
 #4 Oxygen::render_frame at /usr/src/debug/oxygen-gtk3-1.2.0/src/oxygenthemingengine.cpp:1320
 #5 gtk_render_frame at gtkstylecontext.c:3959
 #6 gtk_scrolled_window_draw at gtkscrolledwindow.c:1556
 #7 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:85
 #8 gtk_widget_draw_marshaller at gtkwidget.c:855
 #13 _gtk_widget_draw_internal at gtkwidget.c:6165
 #14 gtk_container_propagate_draw at gtkcontainer.c:3375

Comment 1 mamii 2013-09-22 07:58:36 UTC
Created attachment 801115 [details]
File: backtrace

Comment 2 mamii 2013-09-22 07:58:39 UTC
Created attachment 801116 [details]
File: cgroup

Comment 3 mamii 2013-09-22 07:58:42 UTC
Created attachment 801117 [details]
File: core_backtrace

Comment 4 mamii 2013-09-22 07:58:45 UTC
Created attachment 801118 [details]
File: dso_list

Comment 5 mamii 2013-09-22 07:58:48 UTC
Created attachment 801119 [details]
File: environ

Comment 6 mamii 2013-09-22 07:58:51 UTC
Created attachment 801120 [details]
File: exploitable

Comment 7 mamii 2013-09-22 07:58:54 UTC
Created attachment 801121 [details]
File: limits

Comment 8 mamii 2013-09-22 07:58:57 UTC
Created attachment 801122 [details]
File: maps

Comment 9 mamii 2013-09-22 07:59:04 UTC
Created attachment 801123 [details]
File: open_fds

Comment 10 mamii 2013-09-22 07:59:06 UTC
Created attachment 801124 [details]
File: proc_pid_status

Comment 11 mamii 2013-09-22 07:59:09 UTC
Created attachment 801125 [details]
File: var_log_messages

Comment 12 Jakub Filak 2013-09-23 08:19:45 UTC
Thank you for the bug report. This seems more like a bug in oxygen-gtk or gtk3. Unfortunately, we need to know how this happened. If you have time and can still reproduce the bug, please provide a textual description or better a demonstrative video [1].


1: https://fedoraproject.org/wiki/Bugs_and_feature_requests?rd=BugsAndFeatureRequests#Graphical_User_Interfaces

Comment 13 Fedora End Of Life 2015-01-09 19:55:59 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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-02-17 17:17:43 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.