Bug 920194

Summary: [abrt] gnome-shell-3.6.3.1-1.fc18: window_backed_app_get_window: Process /usr/bin/gnome-shell was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Avvocato Andrea Marengoni <avv.marengoni>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: admiller, fmuellner, otaylor, samkraju, walters
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:8d8cc78feb7c12aa1c1a2e13272d3f787c19f3ab
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 19:52:05 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: build_ids
none
File: cgroup
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 Avvocato Andrea Marengoni 2013-03-11 14:23:59 UTC 
Description of problem:
It happens from time to time that Gnome-shell to crash when opening attachments that must read one of the programs of the office productivity suite that Libre-Office ; momentarily goes away everything, then, after a bit of seconds, everything returns to normal and the attachment is opened. Precise that i have the version 4.0.1 of Libre Office downloaded from the site. 
I would like to take this opportunity to point out that problems occur when using any software program to automatically change the wallpaper (as Wallpapoz or extension for gnome-shell backslide): the system crashes, the background continues to change alone, but especially any window you are trying to open is black, the entire workspace becomes black, 
The terminal window is transparent and unreadable. It could depend on or from the plugin of gnome-settings-daemon which manages the background or by xorg or gnome-shell; if from the command gnome-shell replace (standing careful to type correctly because the terminal, I repeat, and unmanageable, You cannot see anything) there are signals of type error windows not in stack and other related Clutter; i blew it with another. Cordial greetings 

Version-Release number of selected component:
gnome-shell-3.6.3.1-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
core_backtrace: 
crash_function: window_backed_app_get_window
executable:     /usr/bin/gnome-shell
kernel:         3.8.1-201.fc18.i686
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #5 window_backed_app_get_window at shell-app.c:145
 #6 shell_app_get_name at shell-app.c:369
 #8 ffi_call_SYSV at ../src/x86/sysv.S:64
 #9 ffi_call at ../src/x86/ffi.c:303
 #10 gjs_invoke_c_function at gi/function.c:893
 #11 function_call at gi/function.c:1204
 #12 CallJSNative at jscntxtinlines.h:701
 #13 js::Invoke at jsinterp.cpp:696
 #14 js::Interpret at jsinterp.cpp:4810
 #15 js::RunScript at jsinterp.cpp:653

Potential duplicate: bug 836336
Comment 1 Avvocato Andrea Marengoni 2013-03-11 14:24:09 UTC 
Created attachment 708410 [details]
File: backtrace
Comment 2 Avvocato Andrea Marengoni 2013-03-11 14:24:12 UTC 
Created attachment 708411 [details]
File: build_ids
Comment 3 Avvocato Andrea Marengoni 2013-03-11 14:24:14 UTC 
Created attachment 708412 [details]
File: cgroup
Comment 4 Avvocato Andrea Marengoni 2013-03-11 14:24:16 UTC 
Created attachment 708413 [details]
File: dso_list
Comment 5 Avvocato Andrea Marengoni 2013-03-11 14:24:19 UTC 
Created attachment 708414 [details]
File: environ
Comment 6 Avvocato Andrea Marengoni 2013-03-11 14:24:21 UTC 
Created attachment 708415 [details]
File: limits
Comment 7 Avvocato Andrea Marengoni 2013-03-11 14:24:24 UTC 
Created attachment 708416 [details]
File: maps
Comment 8 Avvocato Andrea Marengoni 2013-03-11 14:24:27 UTC 
Created attachment 708417 [details]
File: open_fds
Comment 9 Avvocato Andrea Marengoni 2013-03-11 14:24:30 UTC 
Created attachment 708419 [details]
File: proc_pid_status
Comment 10 Avvocato Andrea Marengoni 2013-03-11 14:24:32 UTC 
Created attachment 708420 [details]
File: var_log_messages
Comment 11 Fedora End Of Life 2013-12-21 12:04:06 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 19:52:05 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.