Bug 1026733 - [abrt] gnome-shell-3.10.1-2.fc20: unowned: Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnome-shell-3.10.1-2.fc20: unowned: Process /usr/bin/gnome-shell was k...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 20
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:64d3aa9c91b68903a05db08bd3a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-05 10:22 UTC by Maciek Borzecki
Modified: 2015-06-29 12:48 UTC (History)
44 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 12:48:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (60.26 KB, text/plain)
2013-11-05 10:22 UTC, Maciek Borzecki
no flags Details
File: cgroup (159 bytes, text/plain)
2013-11-05 10:22 UTC, Maciek Borzecki
no flags Details
File: core_backtrace (23.18 KB, text/plain)
2013-11-05 10:22 UTC, Maciek Borzecki
no flags Details
File: dso_list (23.47 KB, text/plain)
2013-11-05 10:22 UTC, Maciek Borzecki
no flags Details
File: environ (1.62 KB, text/plain)
2013-11-05 10:22 UTC, Maciek Borzecki
no flags Details
File: exploitable (82 bytes, text/plain)
2013-11-05 10:22 UTC, Maciek Borzecki
no flags Details
File: limits (1.29 KB, text/plain)
2013-11-05 10:22 UTC, Maciek Borzecki
no flags Details
File: maps (113.59 KB, text/plain)
2013-11-05 10:23 UTC, Maciek Borzecki
no flags Details
File: open_fds (4.94 KB, text/plain)
2013-11-05 10:23 UTC, Maciek Borzecki
no flags Details
File: proc_pid_status (943 bytes, text/plain)
2013-11-05 10:23 UTC, Maciek Borzecki
no flags Details
File: var_log_messages (28.75 KB, text/plain)
2013-11-05 10:23 UTC, Maciek Borzecki
no flags Details

Description Maciek Borzecki 2013-11-05 10:22:22 UTC
Description of problem:
Just crashed unexpectedly.

Version-Release number of selected component:
gnome-shell-3.10.1-2.fc20

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: unowned
executable:     /usr/bin/gnome-shell
kernel:         3.11.6-302.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 unowned at /usr/src/debug/mozjs17.0.0/js/src/jsscope.h:373
 #1 StackShape at /usr/src/debug/mozjs17.0.0/js/src/jsscope.h:989
 #2 js::Shape::removeChild at /usr/src/debug/mozjs17.0.0/js/src/jspropertytree.cpp:119
 #3 js::Shape::finalize at /usr/src/debug/mozjs17.0.0/js/src/jspropertytree.cpp:211
 #4 finalize<js::Shape> at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:355
 #5 FinalizeTypedArenas<js::Shape> at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:419
 #6 js::gc::FinalizeArenas at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:460
 #7 foregroundFinalize at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:3803
 #8 SweepPhase at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:3823
 #9 IncrementalCollectSlice at /usr/src/debug/mozjs17.0.0/js/src/jsgc.cpp:4245

Comment 1 Maciek Borzecki 2013-11-05 10:22:32 UTC
Created attachment 819626 [details]
File: backtrace

Comment 2 Maciek Borzecki 2013-11-05 10:22:35 UTC
Created attachment 819627 [details]
File: cgroup

Comment 3 Maciek Borzecki 2013-11-05 10:22:40 UTC
Created attachment 819628 [details]
File: core_backtrace

Comment 4 Maciek Borzecki 2013-11-05 10:22:44 UTC
Created attachment 819629 [details]
File: dso_list

Comment 5 Maciek Borzecki 2013-11-05 10:22:48 UTC
Created attachment 819630 [details]
File: environ

Comment 6 Maciek Borzecki 2013-11-05 10:22:52 UTC
Created attachment 819631 [details]
File: exploitable

Comment 7 Maciek Borzecki 2013-11-05 10:22:56 UTC
Created attachment 819632 [details]
File: limits

Comment 8 Maciek Borzecki 2013-11-05 10:23:00 UTC
Created attachment 819633 [details]
File: maps

Comment 9 Maciek Borzecki 2013-11-05 10:23:04 UTC
Created attachment 819634 [details]
File: open_fds

Comment 10 Maciek Borzecki 2013-11-05 10:23:08 UTC
Created attachment 819635 [details]
File: proc_pid_status

Comment 11 Maciek Borzecki 2013-11-05 10:23:12 UTC
Created attachment 819636 [details]
File: var_log_messages

Comment 12 Boricua 2013-12-01 12:18:41 UTC
I woke up the computer from suspended mode when the crash took place.

reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: unowned
executable:     /usr/bin/gnome-shell
kernel:         3.11.9-300.fc20.x86_64
package:        gnome-shell-3.10.2.1-3.fc20
reason:         Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV)
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 13 Boricua 2013-12-03 11:58:59 UTC
It happened after coming up from suspension mode.

reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: unowned
executable:     /usr/bin/gnome-shell
kernel:         3.11.9-300.fc20.x86_64
package:        gnome-shell-3.10.2.1-3.fc20
reason:         Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV)
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 14 Richard Ruhland 2013-12-25 08:38:54 UTC
Another user experienced a similar problem:

unlock screensaver

reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: unowned
executable:     /usr/bin/gnome-shell
kernel:         3.12.5-302.fc20.x86_64
package:        gnome-shell-3.10.2.1-3.fc20
reason:         gnome-shell killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 15 Aditya 2013-12-29 01:41:41 UTC
Another user experienced a similar problem:

It occured randomly this time

reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: unowned
executable:     /usr/bin/gnome-shell
kernel:         3.12.5-302.fc20.x86_64
package:        gnome-shell-3.10.2.1-3.fc20
reason:         gnome-shell killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 16 david sutherland 2014-01-13 03:34:59 UTC
Another user experienced a similar problem:

It happened while using firefox 26 menu customize

reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: unowned
executable:     /usr/bin/gnome-shell
kernel:         3.12.6-300.fc20.x86_64
package:        gnome-shell-3.10.2.1-3.fc20
reason:         gnome-shell killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 17 Pratyush Sahay 2014-01-19 05:59:03 UTC
Another user experienced a similar problem:

keeps crashing. Dont know exact reason.

reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: unowned
executable:     /usr/bin/gnome-shell
kernel:         3.12.6-300.fc20.i686
package:        gnome-shell-3.10.2.1-3.fc20
reason:         gnome-shell killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 18 Daniel Brodie 2014-01-23 06:42:32 UTC
Another user experienced a similar problem:

Resumed the laptop from suspend

reporter:       libreport-2.1.11
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: unowned
executable:     /usr/bin/gnome-shell
kernel:         3.12.8-300.fc20.x86_64
package:        gnome-shell-3.10.2.1-3.fc20
reason:         gnome-shell killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 19 Yang Lifu 2014-02-07 06:57:18 UTC
Another user experienced a similar problem:

I turned off wireless swith and found air plane mode activated and I turned off air plane mode, that where at least I think gnome-shell crashed. 

reporter:       libreport-2.1.12
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: unowned
executable:     /usr/bin/gnome-shell
kernel:         3.12.9-301.fc20.x86_64
package:        gnome-shell-3.10.3-3.fc20
reason:         gnome-shell killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 20 lray+redhatbugzilla 2014-02-17 18:53:54 UTC
Another user experienced a similar problem:

Nothing done, really.. it was not under pressure, no user interaction taking place.

reporter:       libreport-2.1.12
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: unowned
executable:     /usr/bin/gnome-shell
kernel:         3.12.10-300.fc20.x86_64
package:        gnome-shell-3.10.3-4.fc20
reason:         gnome-shell killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 21 Solomon Peachy 2014-02-28 13:33:17 UTC
Another user experienced a similar problem:

I tried to unlock the screen after being away from the system for about ten hours.

reporter:       libreport-2.1.12
backtrace_rating: 4
cmdline:        gnome-shell --sm-client-id 10564bda675ac06b6d139321122396324900000016210000
crash_function: unowned
executable:     /usr/bin/gnome-shell
kernel:         3.13.3-201.fc20.x86_64
package:        gnome-shell-3.10.4-1.fc20
reason:         gnome-shell killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 22 Louis LeBlanc 2014-03-03 15:51:28 UTC
Another user experienced a similar problem:

This was pretty much out of the blue.  No idea what could have triggered it.

reporter:       libreport-2.1.12
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: unowned
executable:     /usr/bin/gnome-shell
kernel:         3.13.5-200.fc20.x86_64
package:        gnome-shell-3.10.4-1.fc20
reason:         gnome-shell killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 23 Szabo Akos 2014-03-30 13:22:56 UTC
Another user experienced a similar problem:

Open a child windows, eg from evolution open a compose new message window, or open a movie, or a picture /big picture, about 8-12Mpixel/

reporter:       libreport-2.2.0
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: unowned
executable:     /usr/bin/gnome-shell
kernel:         3.13.6-200.fc20.x86_64
package:        gnome-shell-3.10.4-2.fc20
reason:         gnome-shell killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1001

Comment 24 jeremiah.mans 2014-04-01 15:25:37 UTC
Another user experienced a similar problem:

Clicking between windows.  Happens roughly every 6 hours.

reporter:       libreport-2.2.0
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: unowned
executable:     /usr/bin/gnome-shell
kernel:         3.13.6-200.fc20.x86_64
package:        gnome-shell-3.10.4-2.fc20
reason:         gnome-shell killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 25 rich 2014-04-03 19:29:16 UTC
Earlier this week I upgraded Gnome to 3.12 using the instructions here:  http://fedoramagazine.org/running-gnome-3-12-on-fedora-20/

So far I have not seen this crash happen, where it had been happening several times a day when running 3.10.

Comment 26 mswal28462 2014-04-05 14:39:59 UTC
(In reply to rich from comment #25)
> Earlier this week I upgraded Gnome to 3.12 using the instructions here: 
> http://fedoramagazine.org/running-gnome-3-12-on-fedora-20/
> 
> So far I have not seen this crash happen, where it had been happening
> several times a day when running 3.10.

I decided to try the same as I've been experience the crash multiple times per day also.  So far, after 1 day, so good.  

I'll post back in a few days with further results.

By the way, the only issue I had with doing the upgrade was getting Cairo-Dock working again.  I had to compile myself and it's only partially working.  But, so far, all other applications are working.

Comment 27 Boricua 2014-04-05 14:47:33 UTC
I upgraded too to Gnome 3.12 and so far not a single crash on my desktop nor my laptop.

Comment 28 mswal28462 2014-04-09 14:19:40 UTC
So I've been on the new Gnome 3.12 for about a week and no crashes.  It is running quite well, actually!  The only item that was difficult about the migration was getting Cairo-Dock to work again (had to compile it myself).

Comment 29 Solomon Peachy 2014-04-21 19:35:08 UTC
FWIW I'm more than a week into using the Gnome 3.12 COPR builds, and not a single crash on three systems -- Coming from multiple crashes daily.

Comment 30 Jesse Kahtava 2014-04-22 21:00:38 UTC
Another user experienced a similar problem:

Went to copy and paste something from Libreoffice to Gnome terminal and it crashed

reporter:       libreport-2.2.1
backtrace_rating: 4
cmdline:        /usr/bin/gnome-shell
crash_function: unowned
executable:     /usr/bin/gnome-shell
kernel:         3.13.9-200.fc20.x86_64
package:        gnome-shell-3.10.4-2.fc20
reason:         gnome-shell killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000

Comment 31 Fedora End Of Life 2015-05-29 09:41:35 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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 20 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 32 Fedora End Of Life 2015-06-29 12:48:44 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.


Note You need to log in before you can comment on or make changes to this bug.