Bug 1271318

Summary: [abrt] nautilus: jpc_qmfb_join_colgrp(): nautilus killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Ryan Sawhill <rsawhill>
Component: nautilusAssignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: ccecchi, jwright, mclasen
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/1d8325981da8b9bc32294486e68b0025e2eef6a5
Whiteboard: abrt_hash:e51a930678a0889c8e009d205c5d89447fccde59;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 18:12:22 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: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Ryan Sawhill 2015-10-13 15:37:20 UTC 
Description of problem:
Using nautilus to view a directory with jp2 image files while preview is enabled causes crash

Version-Release number of selected component:
nautilus-3.16.2-2.fc22

Additional info:
reporter:       libreport-2.6.2
backtrace_rating: 4
cmdline:        /usr/bin/nautilus --gapplication-service
crash_function: jpc_qmfb_join_colgrp
executable:     /usr/bin/nautilus
global_pid:     31497
kernel:         4.1.8-200.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 jpc_qmfb_join_colgrp at jpc_qmfb.c:732
 #1 jpc_ns_synthesize at jpc_qmfb.c:3067
 #2 jpc_tsfb_synthesize2 at jpc_tsfb.c:170
 #7 jpc_tsfb_synthesize at jpc_tsfb.c:154
 #8 jpc_dec_tiledecode at jpc_dec.c:1066
 #9 jpc_dec_process_sod at jpc_dec.c:621
 #10 jpc_dec_decode at jpc_dec.c:390
 #11 jpc_decode at jpc_dec.c:254
 #12 jp2_decode at jp2_dec.c:215
 #13 jas_image_decode at jas_image.c:379

Potential duplicate: bug 735659
Comment 1 Ryan Sawhill 2015-10-13 15:37:23 UTC 
Created attachment 1082483 [details]
File: backtrace
Comment 2 Ryan Sawhill 2015-10-13 15:37:24 UTC 
Created attachment 1082484 [details]
File: cgroup
Comment 3 Ryan Sawhill 2015-10-13 15:37:25 UTC 
Created attachment 1082485 [details]
File: core_backtrace
Comment 4 Ryan Sawhill 2015-10-13 15:37:26 UTC 
Created attachment 1082486 [details]
File: dso_list
Comment 5 Ryan Sawhill 2015-10-13 15:37:27 UTC 
Created attachment 1082487 [details]
File: environ
Comment 6 Ryan Sawhill 2015-10-13 15:37:28 UTC 
Created attachment 1082488 [details]
File: limits
Comment 7 Ryan Sawhill 2015-10-13 15:37:29 UTC 
Created attachment 1082489 [details]
File: maps
Comment 8 Ryan Sawhill 2015-10-13 15:37:30 UTC 
Created attachment 1082490 [details]
File: mountinfo
Comment 9 Ryan Sawhill 2015-10-13 15:37:31 UTC 
Created attachment 1082491 [details]
File: namespaces
Comment 10 Ryan Sawhill 2015-10-13 15:37:31 UTC 
Created attachment 1082492 [details]
File: open_fds
Comment 11 Ryan Sawhill 2015-10-13 15:37:32 UTC 
Created attachment 1082493 [details]
File: proc_pid_status
Comment 12 Ryan Sawhill 2015-10-13 15:37:33 UTC 
Created attachment 1082494 [details]
File: var_log_messages
Comment 13 Fedora End Of Life 2016-07-19 18:12:22 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.