Bug 1047159 - [abrt] easytag: node_get_pos(): easytag killed by SIGSEGV
Summary: [abrt] easytag: node_get_pos(): easytag killed by SIGSEGV
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: easytag
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David King
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:b46895f65ed127c6f05334ed21c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-29 16:02 UTC by mazdac
Modified: 2016-04-25 11:06 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-02-28 19:45:17 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (28.47 KB, text/plain)
2013-12-29 16:02 UTC, mazdac 		no flags Details
File: cgroup (172 bytes, text/plain)
2013-12-29 16:02 UTC, mazdac 		no flags Details
File: core_backtrace (16.46 KB, text/plain)
2013-12-29 16:02 UTC, mazdac 		no flags Details
File: dso_list (9.88 KB, text/plain)
2013-12-29 16:02 UTC, mazdac 		no flags Details
File: environ (1.37 KB, text/plain)
2013-12-29 16:03 UTC, mazdac 		no flags Details
File: exploitable (117 bytes, text/plain)
2013-12-29 16:03 UTC, mazdac 		no flags Details
File: limits (1.29 KB, text/plain)
2013-12-29 16:03 UTC, mazdac 		no flags Details
File: maps (57.07 KB, text/plain)
2013-12-29 16:03 UTC, mazdac 		no flags Details
File: open_fds (927 bytes, text/plain)
2013-12-29 16:03 UTC, mazdac 		no flags Details
File: proc_pid_status (936 bytes, text/plain)
2013-12-29 16:03 UTC, mazdac 		no flags Details
File: var_log_messages (418 bytes, text/plain)
2013-12-29 16:03 UTC, mazdac 		no flags Details
View All

Description mazdac 2013-12-29 16:02:46 UTC 
Version-Release number of selected component:
easytag-2.1.7-4.fc20

Additional info:
reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        easytag
crash_function: node_get_pos
executable:     /usr/bin/easytag
kernel:         3.12.5-302.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 node_get_pos at gsequence.c:1673
 #1 g_sequence_iter_get_position at gsequence.c:1414
 #2 gtk_list_store_get_path at gtkliststore.c:461
 #3 gtk_tree_selection_select_iter at gtktreeselection.c:822
 #4 Browser_List_Select_File_By_DLM at browser.c:1690
 #5 Cddb_Track_List_Row_Selected at cddb.c:1372
 #6 _g_closure_invoke_va at gclosure.c:840
 #12 gtk_real_button_released at gtkbutton.c:1712
 #13 _g_closure_invoke_va at gclosure.c:840
 #16 gtk_button_button_release at gtkbutton.c:1604
Comment 1 mazdac 2013-12-29 16:02:51 UTC 
Created attachment 843086 [details]
File: backtrace
Comment 2 mazdac 2013-12-29 16:02:53 UTC 
Created attachment 843087 [details]
File: cgroup
Comment 3 mazdac 2013-12-29 16:02:56 UTC 
Created attachment 843088 [details]
File: core_backtrace
Comment 4 mazdac 2013-12-29 16:02:58 UTC 
Created attachment 843089 [details]
File: dso_list
Comment 5 mazdac 2013-12-29 16:03:00 UTC 
Created attachment 843090 [details]
File: environ
Comment 6 mazdac 2013-12-29 16:03:01 UTC 
Created attachment 843091 [details]
File: exploitable
Comment 7 mazdac 2013-12-29 16:03:03 UTC 
Created attachment 843092 [details]
File: limits
Comment 8 mazdac 2013-12-29 16:03:06 UTC 
Created attachment 843093 [details]
File: maps
Comment 9 mazdac 2013-12-29 16:03:08 UTC 
Created attachment 843094 [details]
File: open_fds
Comment 10 mazdac 2013-12-29 16:03:09 UTC 
Created attachment 843095 [details]
File: proc_pid_status
Comment 11 mazdac 2013-12-29 16:03:11 UTC 
Created attachment 843096 [details]
File: var_log_messages
Comment 12 David King 2014-01-29 16:35:53 UTC 
Hi, now that easytag-2.1.9-1 is in F20, and I cannot seen to reproduce this crash with that version. Can you test the latest version and attach a new stacktrace and steps to reproduce the crash if you still have the problem? Thanks!
Comment 13 David King 2014-02-28 19:45:17 UTC 
The information we've requested above is required in order to review this problem report further and diagnose or fix the issue if it is still present. Since it has been thirty days or more since we first requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem.
Setting status to "CLOSED: INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report.
Note You need to log in before you can comment on or make changes to this bug.