Bug 731625 - get Fail dialog on first F16Alpha Live autologin
Summary: get Fail dialog on first F16Alpha Live autologin
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 16
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2011-08-18 06:39 UTC by Jens Petersen
Modified: 2013-02-13 19:48 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2013-02-13 19:48:18 UTC

Attachments (Terms of Use)

Description Jens Petersen 2011-08-18 06:39:34 UTC
Description of problem:
When gnome-shell starts in F16Alpha Live (i686)
I see a Fail dialog the first time after autologin.

Version-Release number of selected component (if applicable):

How reproducible:
every time

Steps to Reproduce:
1. Boot Fedora-16-Alpha-i686-Live-Desktop.iso from USB.
Actual results:
Fail whale dialog appears hiding gnome-shell

Expected results:
No fail dialog.

Additional info:
~/.xsession-errors contains:

    JS ERROR: !!!   Exception was: Error: Too few arguments to method St.load_from_raw expected 7 got 6
    JS ERROR: !!!     lineNumber = '0'
    JS ERROR: !!!     fileName = '"gjs_throw"'
    JS ERROR: !!!     stack = '"("Too few arguments to method St.load_from_raw expected 7 got 6")@gjs_throw:0
("",[object Object],24)@/usr/share/gnome-shell/js/ui/notificationDaemon.js:126
([object Object],[object Object])@/usr/share/gnome-shell/js/ui/notificationDaemon.js:298
    JS ERROR: !!!     message = '"Too few arguments to method St.load_from_raw expected 7 got 6"'
    JS ERROR: !!!   Exception was: Error: Argument 'str2' (type utf8) may not be null
    JS ERROR: !!!     lineNumber = '0'
    JS ERROR: !!!     fileName = '"gjs_throw"'
    JS ERROR: !!!     stack = '"("Argument 'str2' (type utf8) may not be null")@gjs_throw:0
([object Object],[object Object])@/usr/share/gnome-shell/js/ui/status/network.js:1168
([object _private_NMClient_DeviceWifi],[object _private_NMClient_AccessPoint])@/usr/share/gnome-shell/js/ui/status/network.js:1248
([object _private_NMClient_DeviceWifi],[object _private_NMClient_AccessPoint])@/usr/share/gjs-1.0/lang.js:110
    JS ERROR: !!!     message = '"Argument 'str2' (type utf8) may not be null"'

After closing the dialog with Alt-F4, the desktop is actually working fine.

Comment 1 Fedora End Of Life 2013-01-16 16:17:56 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: 

Comment 2 Fedora End Of Life 2013-02-13 19:48:22 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.

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