Bug 1018328

Summary: [abrt] anjuta-3.8.4-1.fc19: g_type_check_instance_cast: Process /usr/bin/anjuta was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: A.J. Bonnema <gbonnema>
Component: anjutaAssignee: Cosimo Cecchi <ccecchi>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: ccecchi, jhs, kalevlember, rakesh.pandit
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:5a9ac2dd98d25198f6ca317bb747423218486e5b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 17:38:11 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 A.J. Bonnema 2013-10-11 17:28:21 UTC 
Description of problem:
I was looking at the Fedora sources of the game Astromenace. The sources contain Russian characters. As I do not know Russian, I wanted to copy the comments from Russion into Google translator and paste some english back.
Anjuta imported the project from source without problem. However, when I opened the source file main.cpp in astromenacesources directory, the anjuta program barfed before showing anything.

Probably the Russion characters are the problem. i can understand that, but the question is whether Anjuta should choke on it.

Version-Release number of selected component:
anjuta-3.8.4-1.fc19

Additional info:
reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        anjuta
crash_function: g_type_check_instance_cast
executable:     /usr/bin/anjuta
kernel:         3.11.3-201.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_type_check_instance_cast at gtype.c:4032
 #1 preferences_changed at terminal.c:250
 #2 g_cclosure_marshal_VOID__STRINGv at gmarshal.c:1004
 #3 _g_closure_invoke_va at gclosure.c:840
 #6 g_settings_real_change_event at gsettings.c:288
 #7 ffi_call_unix64 at ../src/x86/unix64.S:76
 #8 ffi_call at ../src/x86/ffi64.c:522
 #9 g_cclosure_marshal_generic_va at gclosure.c:1550
 #10 _g_closure_invoke_va at gclosure.c:840
 #13 settings_backend_path_changed at gsettings.c:363
Comment 1 A.J. Bonnema 2013-10-11 17:28:26 UTC 
Created attachment 811304 [details]
File: backtrace
Comment 2 A.J. Bonnema 2013-10-11 17:28:29 UTC 
Created attachment 811305 [details]
File: cgroup
Comment 3 A.J. Bonnema 2013-10-11 17:28:33 UTC 
Created attachment 811306 [details]
File: core_backtrace
Comment 4 A.J. Bonnema 2013-10-11 17:28:36 UTC 
Created attachment 811307 [details]
File: dso_list
Comment 5 A.J. Bonnema 2013-10-11 17:28:40 UTC 
Created attachment 811308 [details]
File: environ
Comment 6 A.J. Bonnema 2013-10-11 17:28:43 UTC 
Created attachment 811309 [details]
File: limits
Comment 7 A.J. Bonnema 2013-10-11 17:28:47 UTC 
Created attachment 811310 [details]
File: maps
Comment 8 A.J. Bonnema 2013-10-11 17:28:50 UTC 
Created attachment 811311 [details]
File: open_fds
Comment 9 A.J. Bonnema 2013-10-11 17:28:53 UTC 
Created attachment 811312 [details]
File: proc_pid_status
Comment 10 A.J. Bonnema 2013-10-11 17:28:57 UTC 
Created attachment 811313 [details]
File: var_log_messages
Comment 11 Fedora End Of Life 2015-01-09 20:13:05 UTC 
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

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 19 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 12 Fedora End Of Life 2015-02-17 17:38:11 UTC 
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.