Bug 994305

Summary: [abrt] mscore-1.2-2.fc18: g_markup_vprintf_escaped: Process /usr/bin/mscore was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: redwarriorb
Component: mscoreAssignee: Brendan Jones <brendan.jones.it>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: brendan.jones.it
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:2b62114a54f043f84b70f9c3514169132b30fdb8
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 22:14:55 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: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description redwarriorb 2013-08-07 02:51:52 UTC
Version-Release number of selected component:
mscore-1.2-2.fc18

Additional info:
reporter:       libreport-2.1.5
backtrace_rating: 3
cmdline:        mscore
crash_function: g_markup_vprintf_escaped
executable:     /usr/bin/mscore
kernel:         3.6.10-4.fc18.x86_64
uid:            1000
xsession_errors: 

Truncated backtrace:
Thread no. 1 (3 frames)
 #4 g_markup_vprintf_escaped at /lib64/libglib-2.0.so.0
 #6 shortcuts_key_press_event_cb at /lib64/libgtk-x11-2.0.so.0
 #7 update_current_folder_get_info_cb at /lib64/libgtk-x11-2.0.so.0

Comment 1 redwarriorb 2013-08-07 02:51:56 UTC
Created attachment 783625 [details]
File: backtrace

Comment 2 redwarriorb 2013-08-07 02:51:59 UTC
Created attachment 783626 [details]
File: cgroup

Comment 3 redwarriorb 2013-08-07 02:52:02 UTC
Created attachment 783627 [details]
File: core_backtrace

Comment 4 redwarriorb 2013-08-07 02:52:05 UTC
Created attachment 783628 [details]
File: dso_list

Comment 5 redwarriorb 2013-08-07 02:52:08 UTC
Created attachment 783629 [details]
File: environ

Comment 6 redwarriorb 2013-08-07 02:52:11 UTC
Created attachment 783630 [details]
File: limits

Comment 7 redwarriorb 2013-08-07 02:52:16 UTC
Created attachment 783631 [details]
File: maps

Comment 8 redwarriorb 2013-08-07 02:52:22 UTC
Created attachment 783632 [details]
File: open_fds

Comment 9 redwarriorb 2013-08-07 02:52:24 UTC
Created attachment 783633 [details]
File: proc_pid_status

Comment 10 redwarriorb 2013-08-07 02:52:27 UTC
Created attachment 783634 [details]
File: var_log_messages

Comment 11 Fedora End Of Life 2013-12-21 14:26:51 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

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 prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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 to Fedora 18's end of life.

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 12 Fedora End Of Life 2014-02-05 22:14:55 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.