Bug 1276703

Summary: [abrt] parole: cogl_pipeline_new(): parole killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Emiliano Barrionuevo <genarg>
Component: paroleAssignee: Christoph Wickert <christoph.wickert>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: albertofusari73, christoph.wickert, jylo06g, kevin, nonamedotc
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/373c4760e700235a6dffde1fa3900bcaed7357ad
Whiteboard: abrt_hash:18b72141d9a595063e173fcb767df0409acba6f1;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-20 15:15:59 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: mountinfo
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Emiliano Barrionuevo 2015-10-30 14:39:30 UTC
Description of problem:
Daily use.

Version-Release number of selected component:
parole-0.8.0-3.fc23

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        parole '/home/pulgafree/Descargas/Star Wars - El Despertar de la Fuerza \xe2\x80\x93 Tr\xc3\xa1iler Oficial-5eKLdSDGh9k.mp4'
crash_function: cogl_pipeline_new
executable:     /usr/bin/parole
global_pid:     5458
kernel:         4.2.3-300.fc23.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 cogl_pipeline_new at cogl-pipeline.c:435
 #1 clutter_texture_init at deprecated/clutter-texture.c:1316
 #2 g_type_create_instance at gtype.c:1874
 #3 g_object_constructor at gobject.c:2064
 #4 clutter_actor_constructor at clutter-actor.c:6243
 #5 g_object_new_with_custom_constructor at gobject.c:1697
 #6 g_object_new_internal at gobject.c:1777
 #7 g_object_new_valist at gobject.c:2038
 #9 parole_clutter_init at parole-clutter.c:337
 #10 g_type_create_instance at gtype.c:1874

Comment 1 Emiliano Barrionuevo 2015-10-30 14:39:35 UTC
Created attachment 1087947 [details]
File: backtrace

Comment 2 Emiliano Barrionuevo 2015-10-30 14:39:36 UTC
Created attachment 1087948 [details]
File: cgroup

Comment 3 Emiliano Barrionuevo 2015-10-30 14:39:38 UTC
Created attachment 1087949 [details]
File: core_backtrace

Comment 4 Emiliano Barrionuevo 2015-10-30 14:39:40 UTC
Created attachment 1087950 [details]
File: dso_list

Comment 5 Emiliano Barrionuevo 2015-10-30 14:39:41 UTC
Created attachment 1087951 [details]
File: environ

Comment 6 Emiliano Barrionuevo 2015-10-30 14:39:43 UTC
Created attachment 1087952 [details]
File: exploitable

Comment 7 Emiliano Barrionuevo 2015-10-30 14:39:44 UTC
Created attachment 1087953 [details]
File: limits

Comment 8 Emiliano Barrionuevo 2015-10-30 14:39:47 UTC
Created attachment 1087954 [details]
File: maps

Comment 9 Emiliano Barrionuevo 2015-10-30 14:39:49 UTC
Created attachment 1087955 [details]
File: mountinfo

Comment 10 Emiliano Barrionuevo 2015-10-30 14:39:50 UTC
Created attachment 1087956 [details]
File: open_fds

Comment 11 Emiliano Barrionuevo 2015-10-30 14:39:52 UTC
Created attachment 1087957 [details]
File: proc_pid_status

Comment 12 Emiliano Barrionuevo 2015-10-30 14:39:53 UTC
Created attachment 1087958 [details]
File: var_log_messages

Comment 13 Kevin Fenzi 2015-10-30 18:01:47 UTC
Can you get it to crash the same way on the same file? Or it's somewhat sporadic?

Comment 14 Emiliano Barrionuevo 2015-11-03 13:16:56 UTC
Yes. Any file being mvk with h264 codec.

I didn't add rpmfusion repo.

Comment 15 Jia Yuan Lo 2016-04-14 18:02:15 UTC
Similar problem has been detected:

switched to clutter (opengl), closed and restart application, crashed...

reporter:       libreport-2.6.4
backtrace_rating: 4
cmdline:        parole
crash_function: cogl_pipeline_new
executable:     /usr/bin/parole
global_pid:     5652
kernel:         4.4.6-301.fc23.x86_64
package:        parole-0.8.0-3.fc23
reason:         parole killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 16 Alberto 2016-05-05 15:16:37 UTC
*** Bug 1333472 has been marked as a duplicate of this bug. ***

Comment 17 Fedora End Of Life 2016-11-24 12:59:37 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 '23'.

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 23 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 18 Fedora End Of Life 2016-12-20 15:15:59 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.