Re: Problem with gnome-shell-extension-prefs on GNOME 3.4.2

[Craig Rob l300lvl <atz3 yahoo ca>]

It would be ok to test it out I think, but I'm not very confident
patching and all that. When you say its at the top of the git-tree,
which version of gjs is that that it might be patched in and sent
upstream.

Is that the version of the rpms built that have to be forced? I'm sure
theres not a whole lot that can go wrong forcing the install and if so I
can always revert via runlevel 3.

> On Sun, 2012-09-02 at 02:51 -0500, Craig Rob l300lvl wrote:
> > Thanks.
> > 
> > I do believe I did everything correctly, but I'm missing something. I
> > downloaded gjs from
> > http://download.opensuse.org/factory-snapshot/repo/source/suse/src/gjs-1.32.0-2.2.2.src.rpm extracted the source and applied the gobject patch and the other patch in that rpm, I tried buildrpm with spec file but I failed at modifying spec correctly I think(i just added the new patch to it in 2 places). I then did a ./configure, make, sudo make install and rebooted. Yast is still showing the previous install date, and I still get the crashing, so I think I'm not installing correctly.
> > 
> 
> Craig:
> 
> I was able to get the RPMs built. I did a few things that I would not
> recommend as usual practice. The patch that Jasper referred you to is at
> the top of the git tree which is several changes past version 1.32.  I
> changed the spec file and got it to go through with the patch by setting
> the global fuzz to 125 after several attempts at smaller values.  I
> checked the patched source and saw no apparent damage. You could patch
> it by hand but running the whole RPM build process gives you three RPMs
> that need to be installed with --force.
> 
> I installed the RPMs and the extensions prefs no longer crash because of
> using GOjects in prefs.js.  If you want I can give you the steps I found
> to build the RPMs.
> 
> This patch needs to be applied at the affected distros.
> 
> I haven't tested every extension I have tested the following:
> 
> Activities Text - OK
> Activities Configurator - OK
> Status Area Horizontal Spacing - OK
> Workspace Indicator - OK
> Window Buttons - OK
> 
> Window Options - Get red ERROR on website but it is installed and can be
> configured locally
> 
> Maximus - Fails  Error: Error invoking bindtextdomain, at argument 1
> (domain): Object is not a string, cannot convert to UTF-8 ...
> maximus mathematical coffee gmail com/prefs.js:25....
> 
> 
> Norman