Bug 1289509

Summary: [abrt] ristretto: rstto_file_get_display_name(): ristretto killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Tomáš Hykel <mail+rh>
Component: ristrettoAssignee: Mukundan Ragavan <nonamedotc>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: christoph.wickert, nonamedotc
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/be5cc4f37d36d02cfeb3bb9f360ab05f068047b7
Whiteboard: abrt_hash:1ce9bdcba42350c392f0fefa6ff11c98ddf351ee;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 18:34:56 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 Tomáš Hykel 2015-12-08 11:29:45 UTC 
Description of problem:
Sequentially deleted all pictures in the folder via Ristretto, then pressed delete in the blank window that appeared when there were no images left.

Version-Release number of selected component:
ristretto-0.8.0-1.fc22

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        ristretto /home/thykel/Desktop/Screenshot_2015-12-04_19-09-18.png
crash_function: rstto_file_get_display_name
executable:     /usr/bin/ristretto
global_pid:     11010
kernel:         4.2.6-201.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (2 frames)
 #0 rstto_file_get_display_name at file.c:321
 #1 cb_rstto_main_window_delete at main_window.c:3313
Comment 1 Tomáš Hykel 2015-12-08 11:29:50 UTC 
Created attachment 1103546 [details]
File: backtrace
Comment 2 Tomáš Hykel 2015-12-08 11:29:51 UTC 
Created attachment 1103547 [details]
File: cgroup
Comment 3 Tomáš Hykel 2015-12-08 11:29:52 UTC 
Created attachment 1103548 [details]
File: core_backtrace
Comment 4 Tomáš Hykel 2015-12-08 11:29:54 UTC 
Created attachment 1103549 [details]
File: dso_list
Comment 5 Tomáš Hykel 2015-12-08 11:29:55 UTC 
Created attachment 1103550 [details]
File: environ
Comment 6 Tomáš Hykel 2015-12-08 11:29:56 UTC 
Created attachment 1103551 [details]
File: limits
Comment 7 Tomáš Hykel 2015-12-08 11:29:58 UTC 
Created attachment 1103552 [details]
File: maps
Comment 8 Tomáš Hykel 2015-12-08 11:29:59 UTC 
Created attachment 1103553 [details]
File: mountinfo
Comment 9 Tomáš Hykel 2015-12-08 11:30:00 UTC 
Created attachment 1103554 [details]
File: namespaces
Comment 10 Tomáš Hykel 2015-12-08 11:30:02 UTC 
Created attachment 1103555 [details]
File: open_fds
Comment 11 Tomáš Hykel 2015-12-08 11:30:03 UTC 
Created attachment 1103556 [details]
File: proc_pid_status
Comment 12 Tomáš Hykel 2015-12-08 11:30:04 UTC 
Created attachment 1103557 [details]
File: var_log_messages
Comment 13 Mukundan Ragavan 2015-12-09 01:27:00 UTC 
I think this best bumped upstream. 

Would you be willing (and kind) to file an upstream report or would you rather prefer that I do?
Comment 14 Tomáš Hykel 2015-12-11 09:30:09 UTC 
I think it would be much quicker if you took care of that as I am quite pressed for time right now... 

Thanks!
Comment 15 Mukundan Ragavan 2015-12-15 02:22:07 UTC 
No worries. I will file it upstream ..
Comment 16 Fedora End Of Life 2016-07-19 18:34:56 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.