Bug 752689 - gnome-shell-extension-remove-accessibility-icon does not work in FC16
Summary: gnome-shell-extension-remove-accessibility-icon does not work in FC16
Keywords:
Status: CLOSED DUPLICATE of bug 752192
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell-extension-remove-accessibility-icon
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Fabian Affolter
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-10 06:11 UTC by Brad Hess
Modified: 2011-11-10 10:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-11-10 10:13:16 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Brad Hess 2011-11-10 06:11:45 UTC 
Description of problem:
Version of gnome-shell-extension-remove-accessibility-icon provided in FC16 repos is not compatible with the version of Gnome or GJS in the repos

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

How reproducible:
Always

Steps to Reproduce:
1. Install the extension (yum install gnome-shell-extension-remove-accessibility-icon)
2. Restart gnome (alt+f2, r)
3. View error in lg (alt+f2, lg)
  
Actual results:
Extension dock at "remove-accessibility-icon" had error: extension is not compatible with current GNOME Shell and/or GJS version

Expected results:
No error message
Comment 1 Elder Marco 2011-11-10 10:12:33 UTC 
Hello,

This extension has been updated, but the current status is pending on bodhi:

https://admin.fedoraproject.org/updates/gnome-shell-extension-remove-accessibility-icon-20111008-1.fc16

Please, wait 1 or 2 days and then:

# yum update --enablerepo=testing gnome-shell-extension-remove-accessibility-icon

I'll mark this bug as duplicate of the bug #752192
Comment 2 Elder Marco 2011-11-10 10:13:16 UTC 

*** This bug has been marked as a duplicate of bug 752192 ***
Note You need to log in before you can comment on or make changes to this bug.