Description of problem: After an update (I believe to gnome-shell-3.1.91) Alternative Status Menu Extension causes gnome-shell to crash and pop up with the fail screen which offers to let you disable extensions. Disabling just the Alternative Status Menu Extension allows login to proceed. Version-Release number of selected component (if applicable): gnome-shell-3.1.91-2.fc16.x86_64 gnome-shell-extension-alternative-status-menu-3.1.91-2.fc16.noarch How reproducible: always Steps to Reproduce: 1. Enable Alternative Status Menu Extension 2. Logout/Login 3. Fail screen appears Actual results: Fail screen appears. Expected results: Successful login. No fail screen. Alternative Status Menu shows up. Additional info: Other installed extensions: gnome-shell-extension-alternate-tab-3.1.91-2.fc16.noarch gnome-shell-extension-common-3.1.91-2.fc16.noarch gnome-shell-extension-cpu-temperature-0-0.1.git712153f.fc16.noarch gnome-shell-extension-places-menu-3.1.91-2.fc16.noarch gnome-shell-extension-presentation-mode-0-0.2.gitc3ce6b2.fc16.noarch Only enabled extensions when this issue happens: Alternative Status Menu Extension Places Status Indicator Extension
Same here, I have just alternative-status-menu installed.
*** Bug 745453 has been marked as a duplicate of this bug. ***
It's not a surprise, it was already announced in the update release notes: https://admin.fedoraproject.org/updates/FEDORA-2011-13770 Bug already reported upstream: https://bugzilla.gnome.org/show_bug.cgi?id=660520
*** Bug 748461 has been marked as a duplicate of this bug. ***
*** Bug 750746 has been marked as a duplicate of this bug. ***
For those interested to getting things working: just select a "user image".
*** Bug 751365 has been marked as a duplicate of this bug. ***
Bit me here. I rely on this extension as the keyboard is physically covered on the kid's laptop (to prevent broken keys) so I can't easily hold down the ALT key to properly shutdown.
Setting a user image worked as a workaround. Thanks Dietrich (comment #6)
*** Bug 753086 has been marked as a duplicate of this bug. ***
This bug is still present in gnome-shell-extension-alternative-status-menu-3.2.0-1.fc16.noarch. Workaround still works.
*** Bug 754793 has been marked as a duplicate of this bug. ***
bug still there in fc16_64 bit as on 18,Nov,2011. (duly updated). Workout of adding user image works.
Bug still reproduces with gnome-shell-extension-alternative-status-menu-3.2.0-2.fc16.noarch.
Could someone help me find the workaround. What you mean above: select a "user image"? Select from where? Thanks.
(In reply to comment #15) > Could someone help me find the workaround. What you mean above: select a "user > image"? > Select from where? > Thanks. Select an image for your user, click in your username at the top right of your screen, then click in the image square to select an image for you user. ;)
Nice workaround indeed - and it works! Thanks:)
Just a warning, it appears that once you select a non-default picture, you can't go back to the original one, even though the picture selection GUI makes it look like you could. Of the 25 pictures in the 5x5 grid, 24 are in /usr/share/pixmaps/faces, and the remaining generic icon can't be selected. Is this a known bug, and if not, what component should it be filed against?
subscribing to this bug...
Filed bug 757257 against control-center for not being able to return to no user image.
The problem also exists on an i686 machine. I have the following. Name : gnome-shell-extension-alternative-status-menu Arch : noarch Version : 3.2.0 Name : gnome-shell Arch : i686 Version : 3.2.1 with this OS information: 3.1.2-1.fc16.i686.PAE
Suggested workaround doesn't work for me. Fail screen appears at login/gnome-shell restart even with the user image selected. I'm running the following: Kernel : 3.1.2-1.fc16.x86_64 Gnome Shell : gnome-shell.x86_64 3.2.1-2.fc16 Extension : gnome-shell-extension-alternative-status-menu.noarch 3.2.0-2.fc16
gnome-shell-extensions-3.2.1-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/gnome-shell-extensions-3.2.1-1.fc16
Too bad I won't be able to test the fix, since it's impossible for me to go back to no user image (bug 757257).
After applying the accountsservice update in bug 757257, was able to get back to the default user image and test this update, and it does appear to fix the bug.
*** Bug 753254 has been marked as a duplicate of this bug. ***
Still having the issue (crash at login): yum info gnome-shell-extension-alternative-status-menu Installed Packages Name : gnome-shell-extension-alternative-status-menu Arch : noarch Version : 3.2.0 Release : 2.fc16
(In reply to comment #27) > Still having the issue (crash at login): > > yum info gnome-shell-extension-alternative-status-menu > > Installed Packages > Name : gnome-shell-extension-alternative-status-menu > Arch : noarch > Version : 3.2.0 > Release : 2.fc16 Please try the latest version 3.2.1, in updates-testing repo.
yum --enablerepo=updates-testing update gnome-shell-extension-alternative-status-menu ... Setting up Update Process No Packages marked for Update yum info gnome-shell-extension-alternative-status-menu ... Installed Packages Name : gnome-shell-extension-alternative-status-menu Arch : noarch Version : 3.2.0 Release : 2.fc16 ... Wasn't the new package pushed on the updates-testing repo or am I messing things up?
(In reply to comment #29) > Wasn't the new package pushed on the updates-testing repo or am I messing > things up? It is still in pending status, indeed, sorry for having written my previous message too fast. You can test the updated packages from their Koji page: http://koji.fedoraproject.org/koji/buildinfo?buildID=276388
(In reply to comment #30) > (In reply to comment #29) > > Wasn't the new package pushed on the updates-testing repo or am I messing > > things up? > It is still in pending status, indeed, sorry for having written my previous > message too fast. You can test the updated packages from their Koji page: > http://koji.fedoraproject.org/koji/buildinfo?buildID=276388 I tested the koji packages, and the "Power Off" menu item doesn't appear until 6 or 7 seconds after the rest of the desktop environment has loaded. While it is non-critical, I would still consider it a bug.
I noticed that too, but couldn't be sure if it's different from previous behavior, since I don't normally bring up the User Menu immediately after logging in.
> I tested the koji packages, and the "Power Off" menu item doesn't appear until > 6 or 7 seconds after the rest of the desktop environment has loaded. While it > is non-critical, I would still consider it a bug. This *is* the fix. The crash is due to a race condition. To avoid it, a delay has been added in the update to load the extension after 10 seconds.
(In reply to comment #32) > I noticed that too, but couldn't be sure if it's different from previous > behavior, since I don't normally bring up the User Menu immediately after > logging in. That is just my definition of testing. (In reply to comment #33) > This *is* the fix. The crash is due to a race condition. To avoid it, a delay > has been added in the update to load the extension after 10 seconds. I see. Forgive my naivete, but is there not some type of queue system that the extensions are loaded in? This is good for this extension, but if this happens in the future with other extensions, then each extension would have to have a unique delay programmmed into it, right?
(In reply to comment #33) > > I tested the koji packages, and the "Power Off" menu item doesn't appear until > > 6 or 7 seconds after the rest of the desktop environment has loaded. While it > > is non-critical, I would still consider it a bug. > This *is* the fix. The crash is due to a race condition. To avoid it, a delay > has been added in the update to load the extension after 10 seconds. I'd rather not consider a delay as a fix. This is a workaround not a fix. To fix the problem you have to check if something is available. If it is not available wait until it is available (not a fixed amount of time)!
> I'd rather not consider a delay as a fix. This is a workaround not a fix. To > fix the problem you have to check if something is available. If it is not > available wait until it is available (not a fixed amount of time)! Patches are welcome, as usual.
Package gnome-shell-extensions-3.2.1-1.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gnome-shell-extensions-3.2.1-1.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-16656/gnome-shell-extensions-3.2.1-1.fc16 then log in and leave karma (feedback).
gnome-shell-extensions-3.2.1-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
The hibernate and power off options does not appear when the extension is installed on fedora 16. Power off appears only when the alt button is pressed. I installed gnome-shell-extensions-3.2.1-1.fc16
The hibernate and power off options "do" not appear when the extension is installed on fedora 16. Power off appears only when the alt button is pressed. I installed gnome-shell-extensions-3.2.1-1.fc16
(In reply to comment #40) > The hibernate and power off options "do" not appear when the extension is > installed on fedora 16. Power off appears only when the alt button is pressed. > > I installed gnome-shell-extensions-3.2.1-1.fc16 did you enable the extension using gnome-tweak-tool? for me it's working now.