Bug 812667

Summary: gnome shell asks me for information it already has, then crashes.
Product: [Fedora] Fedora Reporter: David Woodhouse <dwmw2>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: collura, maxamillion, otaylor, samkraju, walters
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 20:30:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description David Woodhouse 2012-04-15 19:51:19 UTC
I just came back to my laptop, which had been idle for a while.

I had a black screen with a dialog in the middle of it, asking for the password for my local network. I hit 'cancel'. The normal screen lit up, and I could see IRC traffic scrolling past quite happily. It was connected.

Then gnome-shell crashed.

      JS LOG: Removing an access point that was never added
      JS LOG: Removing an access point that was never added
    JS ERROR: !!!   Exception was: TypeError: apObj.item.updateAccessPoints is not a function
    JS ERROR: !!!     lineNumber = '1228'
    JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/js/ui/status/network.js"'
    JS ERROR: !!!     stack = '"([object _private_NMClient_DeviceWifi],[object _private_NMClient_AccessPoint])@/usr/share/gnome-shell/js/ui/status/netwo
rk.js:1228
"'
    JS ERROR: !!!     message = '"apObj.item.updateAccessPoints is not a function"'
    JS ERROR: !!!   Exception was: TypeError: apObj.item.updateAccessPoints is not a function
    JS ERROR: !!!     lineNumber = '1228'
    JS ERROR: !!!     fileName = '"/usr/share/gnome-shell/js/ui/status/network.js"'
    JS ERROR: !!!     stack = '"([object _private_NMClient_DeviceWifi],[object _private_NMClient_AccessPoint])@/usr/share/gnome-shell/js/ui/status/netwo
rk.js:1228
"'
    JS ERROR: !!!     message = '"apObj.item.updateAccessPoints is not a function"'
gnome-session[1656]: WARNING: Application 'gnome-shell.desktop' killed by signal


When my desktop eventually came back, I had about a dozen dialog boxes asking me the *same* question. I hit cancel on them all, since I was already connected.

Comment 1 Fedora End Of Life 2013-01-16 16:37:51 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 '16'.

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 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Fedora End Of Life 2013-02-13 20:30:42 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.

Thank you for reporting this bug and we are sorry it could not be fixed.