After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 667187 - Name 'extensionjs_path' is not defined in "/usr/bin/gnome-shell-extension-tool", line 151
Name 'extensionjs_path' is not defined in "/usr/bin/gnome-shell-extension-too...
Status: RESOLVED DUPLICATE of bug 661623
Product: gnome-shell
Classification: Core
Component: st
3.2.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2012-01-03 15:05 UTC by Jakub Dorňák
Modified: 2012-01-03 15:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jakub Dorňák 2012-01-03 15:05:21 UTC 
gnome-shell-extension-tool fails creating new GNOME extension ending up with

NameError: name 'extensionjs_path' is not defined

Output:

$ gnome-shell-extension-tool --create-extension

Name should be a very short (ideally descriptive) string.
Examples are: "Click To Focus",  "Adblock", "Shell Window Shrinker".

Name: Click To Focus

Description is a single-sentence explanation of what your extension does.
Examples are: "Make windows visible on click", "Block advertisement popups"
              "Animate windows shrinking on minimize"

Description: Make windows visible on click

Uuid is a globally-unique identifier for your extension.
...
use an extension title clicktofocus@janedoe.example.com.
Uuid [Click_To_Focus@qb.usersys.redhat.com]: 
Created extension in '/home/jdornak/.local/share/gnome-shell/extensions/Click_To_Focus@qb.usersys.redhat.com'
Traceback (most recent call last):

+ Trace 229379

  • File "/usr/bin/gnome-shell-extension-tool", line 151 in <module> 
    subprocess.Popen(['gnome-open', extensionjs_path])
NameError: name 'extensionjs_path' is not defined 






Comment 1


Jasper St. Pierre (not reading bugmail)





          2012-01-03 15:23:56 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 661623 ***