Bug#572718: Same bug now appeared in testing (A.K.A. "Not fixed")

Lutz webmaster at phatsonic.de
Mon Mar 15 19:44:54 UTC 2010


I just ran an upgrade and now gnome-shell is broken in testing, too.


       JS LOG: conforming method: IntrospectRemote for 
org.freedesktop.DBus.Introspectable
     JS ERROR: !!!   Exception was: Error: Requiring Shell, version 
none: Requiring namespace 'Meta' version '2.28', but '2.29' is already 
loaded
     JS ERROR: !!!     lineNumber = '0'
     JS ERROR: !!!     fileName = 'gjs_throw'
     JS ERROR: !!!     stack = 'Error("Requiring Shell, version none: 
Requiring namespace 'Meta' version '2.28', but '2.29' is already loaded")@:0
("Requiring Shell, version none: Requiring namespace 'Meta' version 
'2.28', but '2.29' is already loaded")@gjs_throw:0
@/usr/share/gnome-shell/js/ui/main.js:11
'
     JS ERROR: !!!     message = 'Requiring Shell, version none: 
Requiring namespace 'Meta' version '2.28', but '2.29' is already loaded'
     JS ERROR: !!!   Exception was: Error: Requiring Shell, version 
none: Requiring namespace 'Meta' version '2.28', but '2.29' is already 
loaded
     JS ERROR: !!!     lineNumber = '0'
     JS ERROR: !!!     fileName = 'gjs_throw'
     JS ERROR: !!!     stack = 'Error("Requiring Shell, version none: 
Requiring namespace 'Meta' version '2.28', but '2.29' is already loaded")@:0
("Requiring Shell, version none: Requiring namespace 'Meta' version 
'2.28', but '2.29' is already loaded")@gjs_throw:0
@/usr/share/gnome-shell/js/ui/main.js:11
'
     JS ERROR: !!!     message = 'Requiring Shell, version none: 
Requiring namespace 'Meta' version '2.28', but '2.29' is already loaded'
Fensterverwalter-Warnung:Log level 32: Execution of main.js threw 
exception: Error: Requiring Shell, version none: Requiring namespace 
'Meta' version '2.28', but '2.29' is already loaded
bid at bid-notebook:~$ Cannot register the panel shell: there is already 
one running.
Warnung der Fensterverwaltung:Ungültiges WM_TRANSIENT_FOR-Fenster 
0x2a0002d festgelegt für 0x2a00110 (Starting a).


The bug doesn't really look that fixed... ;)






More information about the pkg-gnome-maintainers mailing list