Arch Linux

Padfoot

Member

Registered: 2010-09-03

Posts: 381

[GNOME 3] Latest update (27/04/11) issues

Hi,

Just wondering if anyone else is experiencing similar issues to the below, after the latest updates:

1. Menu randomly shows duplicate entries and/or some applications randomly do not list.

2. User extensions no longer function (I had custom extensions to hide the ally icon and change "Activities" to the Arch icon) from ~/.local/share/gnome-shell/extensions

3. user extensions no longer function from /usr/share/gnome-shell/extensions either.

Grrrr.

Just when i got Gnome 3 customised the way I want it.....

All help appreciated.

Cheers.

[ADDITIONAL] gnome-shell-extensions-git from Aur, extensions no longer function either.

Last edited by Padfoot (2011-04-28 08:03:31)

hcjl

Member

From: berlin

Registered: 2007-06-29

Posts: 330

Re: [GNOME 3] Latest update (27/04/11) issues

Grrrr.

Just when i got Gnome 3 customised the way I want it.....

i think that's the reason why it's in testing;-)

stefanwilkens

Member

From: Enschede, the Netherlands

Registered: 2008-12-10

Posts: 624

Re: [GNOME 3] Latest update (27/04/11) issues

Hi,

Just wondering if anyone else is experiencing similar issues to the below, after the latest updates:

1. Menu randomly shows duplicate entries and/or some applications randomly do not list.

Confirmed, doesn't seem related to .desktop entries. This was going on before the update too. It's not happening constantly, rather randomly.

2. User extensions no longer function (I had custom extensions to hide the ally icon and change "Activities" to the Arch icon) from ~/.local/share/gnome-shell/extensions

3. user extensions no longer function from /usr/share/gnome-shell/extensions either.

[ADDITIONAL] gnome-shell-extensions-git from Aur, extensions no longer function either.

These points all seem related, hence I've bundled them. My extensions still function properly (using user-theme and dock)

Last edited by stefanwilkens (2011-04-28 08:22:35)

---

Arch i686 on Phenom X4 | GTX760

alexcriss

Member

Registered: 2010-05-24

Posts: 121

Re: [GNOME 3] Latest update (27/04/11) issues

2. User extensions no longer function (I had custom extensions to hide the ally icon and change "Activities" to the Arch icon) from ~/.local/share/gnome-shell/extensions

3. user extensions no longer function from /usr/share/gnome-shell/extensions either.

[ADDITIONAL] gnome-shell-extensions-git from Aur, extensions no longer function either.

Are you sure that the version field in the metadata.json file that is in each extension folder says the same as

gnome-shell --version

Padfoot

Member

Registered: 2010-09-03

Posts: 381

Re: [GNOME 3] Latest update (27/04/11) issues

Duh, I knew I was missing something simple...

For my local extensions (arch icon and no ally icon) was simply my version in the metadata. They are now working again.

But, gnome-shell-extensions-git are still not working. Looking at the extended status menu, metadata states version 3.0.1, gnome-shell is reporting 3.0.1, yet my Power Off option is not there.

Hmmm........ >:(

stefanwilkens

Member

From: Enschede, the Netherlands

Registered: 2008-12-10

Posts: 624

Re: [GNOME 3] Latest update (27/04/11) issues

p.s. mind sharing the arch icon extension ?

---

Arch i686 on Phenom X4 | GTX760

Padfoot

Member

Registered: 2010-09-03

Posts: 381

Re: [GNOME 3] Latest update (27/04/11) issues

@ stefanwilkens

https://bbs.archlinux.org/viewtopic.php?id=117495

enjoy.

caiocon

Member

From: SP - Brasil

Registered: 2011-04-29

Posts: 28

Re: [GNOME 3] Latest update (27/04/11) issues

Ok, I had the same problem, and solved it changing the version field in metadata.json... but that's not easy, should I do it at each gnome upgrade? don't you know a way I set a range of versions to that field?

Padfoot

Member

Registered: 2010-09-03

Posts: 381

Re: [GNOME 3] Latest update (27/04/11) issues

@caiocon

I would like to think you could set a range. I had a problem with the alternate status menu extension where it no longer worked after the upgrade to 3.0.1

Having a look at the metadata.json in that extension, it had version 3.0. I would have thought having 3.0 would cover things like 3.0.0, 3.0.1 etc, but it does not. After changing it to 3.0.1, the extension started to work again.

So it seems, at least for the moment, and anyone correct me if I am wrong, the version numbers must be an exact match or the extension will not work.

Cheers.

{ADDITIONAL} Looking at the current framework, it can be a list of versions
eg: "shell-version": ["3.0.1", "3.0.2"]
So, you can pre-empt version numbering, although that would not be a good idea. Ideally we should be able to do this:
"shell-version": ["=>3.0.1"]

Last edited by Padfoot (2011-04-30 02:06:01)