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 587888 - GNOME Shell doesn't start when running it ./gnome-shell
GNOME Shell doesn't start when running it ./gnome-shell
Status: RESOLVED DUPLICATE of bug 578197
Product: gnome-shell
Classification: Core
Component: general
unspecified
Other All
: Normal critical
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2009-07-06 12:48 UTC by artirj
Modified: 2009-07-07 11:10 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description artirj 2009-07-06 12:48:13 UTC
Steps to reproduce:
1. Go to the src folder of gnome shell
2. Run ./gnome-shell
3. See the bug


Stack trace:
artir@JosePC:~/gnome-shell/source/gnome-shell/src$ ./gnome-shell
xauth:  creating new authority file /tmp/gnome-shell.JDkQFI/database
[dix] Could not init font path element /usr/share/fonts/X11/cyrillic, removing from list!
[config/dbus] couldn't take over org.x.config: org.freedesktop.DBus.Error.AccessDenied (Connection ":1.89" is not allowed to own the service "org.x.config.display12" due to security policies in the configuration file)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)
unrecognised device identifier!
(EE) config/hal: NewInputDeviceRequest failed (2)

(mutter:5307): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(mutter:5307): atk-bridge-WARNING **: IOR not set.

(mutter:5307): atk-bridge-WARNING **: Could not locate registry
      JS LOG: Loading tweener.js
      JS LOG: Loading tweenlist.js
      JS LOG: Done loading tweenlist.js
      JS LOG: Done loading tweener.js
    JS ERROR: !!!   Exception was: TypeError: icontheme.lookup_icon("gtk-find", 16, 0) is null
    JS ERROR: !!!     lineNumber = '130'
    JS ERROR: !!!     fileName = '/home/artir/gnome-shell/source/gnome-shell/js/ui/overlay.js'
    JS ERROR: !!!     stack = '((void 0))@/home/artir/gnome-shell/source/gnome-shell/js/ui/overlay.js:130
SearchEntry()@/home/artir/gnome-shell/source/gnome-shell/js/ui/overlay.js:113
()@/home/artir/gnome-shell/source/gnome-shell/js/ui/overlay.js:276
Dash()@/home/artir/gnome-shell/source/gnome-shell/js/ui/overlay.js:199
()@/home/artir/gnome-shell/source/gnome-shell/js/ui/overlay.js:751
Overlay()@/home/artir/gnome-shell/source/gnome-shell/js/ui/overlay.js:691
start()@/home/artir/gnome-shell/source/gnome-shell/js/ui/main.js:68
@<main>:1
'
    JS ERROR: !!!     message = 'icontheme.lookup_icon("gtk-find", 16, 0) is null'
Advertencia del gestor de ventanas: Log level 32: Execution of main.js threw exception: TypeError: icontheme.lookup_icon("gtk-find", 16, 0) is null

(gnomeshell-taskpanel:5325): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(gnomeshell-taskpanel:5325): atk-bridge-WARNING **: IOR not set.

(gnomeshell-taskpanel:5325): atk-bridge-WARNING **: Could not locate registry

Other information:
Comment 1 Owen Taylor 2009-07-07 10:25:26 UTC
What distribution and version?
What icon theme are you using?

 (Run gnome-appearance-properties, go to Customize/Icons)
Comment 2 Owen Taylor 2009-07-07 11:10:26 UTC

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