On 05/02/2011 07:01 PM, Aljosha Papsch wrote:

...

/M

It's a design pattern of the GNOME Shell. Switching between windows work application based, not window based. Which means, if a Webbrowser is opened and two Shells, you won't switch between the shells but between Firefox and the last focused shell. You can get back the old behavior, though. Just install gnome-shell-extensions-git from AUR.

i don't suggest to install all extensions since gnome-shell will load them all. Install only specific extension, only what you need. You can find them in aur too -- Ionuț

On Mon, May 2, 2011 at 17:54, Damien Churchill wrote:

You can disable extensions, taken from the Gnome Shell extensions page [1]

"Per-user and systemwide extensions can be disabled with the GSettings key org.gnome.shell.disabled-extensions"

[1] http://live.gnome.org/GnomeShell/Extensions

Yes, indeed it does say that, but it doesn't say how to actually disable them :-) I've tried to disable AlternateTab without success. Here's what I've tried so far: % gsettings set org.gnome.shell disabled-extensions "@as ['AlternateTab'] % gsettings set org.gnome.shell disabled-extensions "@as ['alternate-tab'] Has anyone else managed to disable extensions? /M -- Magnus Therning                      OpenPGP: 0xAB4DFBA4 email: magnus@therning.org   jabber: magnus@therning.org twitter: magthe               http://therning.org/magnus

On Thu, May 5, 2011 at 07:38, Casey Peter wrote:

On 05/04/2011 11:56 PM, Magnus Therning wrote:

...

On Mon, May 2, 2011 at 17:54, Damien Churchill  wrote:

...

You can disable extensions, taken from the Gnome Shell extensions page [1]

"Per-user and systemwide extensions can be disabled with the GSettings key org.gnome.shell.disabled-extensions"

[1] http://live.gnome.org/GnomeShell/Extensions

Yes, indeed it does say that, but it doesn't say how to actually disable them :-)

I've tried to disable AlternateTab without success.  Here's what I've tried so far:

% gsettings set org.gnome.shell disabled-extensions "@as ['AlternateTab'] % gsettings set org.gnome.shell disabled-extensions "@as ['alternate-tab']

Has anyone else managed to disable extensions?

/M

Yes.  Disabling the extension is pretty simple.  Just go into the /usr/share/gnome-shell/extensions directory, rename the extension folder to .backup or something like .disabled. (just keep the original folder name in case you want to re-enable later).  You can then do an alt-f2 "lg" and enter and go to the extensions tab to verify what is/is not there.  To make the change alt+f2 "r" enter to restart the gnome-shell.

I'd very much like to avoid doing something like that, because it's "icky". Renaming a system directory, owned by an installed package? That's not good practice for system administration in my opinion. The Gnome 3 docs say it's possible to disable installed extensions on a per-user basis, I'd much prefer doing it that way. /M -- Magnus Therning                      OpenPGP: 0xAB4DFBA4 email: magnus@therning.org   jabber: magnus@therning.org twitter: magthe               http://therning.org/magnus

On Thu, May 5, 2011 at 09:17, Casey Peter wrote:

On 05/05/2011 01:43 AM, Magnus Therning wrote:

...

On Thu, May 5, 2011 at 07:38, Casey Peter  wrote:

...

On 05/04/2011 11:56 PM, Magnus Therning wrote:

...

On Mon, May 2, 2011 at 17:54, Damien Churchill  wrote:

...

You can disable extensions, taken from the Gnome Shell extensions page [1]

"Per-user and systemwide extensions can be disabled with the GSettings key org.gnome.shell.disabled-extensions"

[1] http://live.gnome.org/GnomeShell/Extensions

Yes, indeed it does say that, but it doesn't say how to actually disable them :-)

I've tried to disable AlternateTab without success.  Here's what I've tried so far:

% gsettings set org.gnome.shell disabled-extensions "@as ['AlternateTab'] % gsettings set org.gnome.shell disabled-extensions "@as ['alternate-tab']

Has anyone else managed to disable extensions?

/M

Yes.  Disabling the extension is pretty simple.  Just go into the /usr/share/gnome-shell/extensions directory, rename the extension folder to .backup or something like .disabled. (just keep the original folder name in case you want to re-enable later).  You can then do an alt-f2 "lg" and enter and go to the extensions tab to verify what is/is not there.  To make the change alt+f2 "r" enter to restart the gnome-shell.

I'd very much like to avoid doing something like that, because it's "icky".  Renaming a system directory, owned by an installed package? That's not good practice for system administration in my opinion.  The Gnome 3 docs say it's possible to disable installed extensions on a per-user basis, I'd much prefer doing it that way.

/M

It might be "icky", but you asked a question...I answered it.  I have it working and do it that way for now, it works a charm, as some of those extensions I am not fond of, having gotten used to the defaults during the testing phase.  Adding a .xxx to the end of the file disables it and keeps the basic folder name structure intact so later if I want it back "on" I know exactly what to change.

 The package(s) are in AUR anyway, and until we get a better method of handling the stuff, this works for me.  As for good practice...its my own machine in my own home, and I know what goes on in exquisite detail on that box...so hey.  :D  (not knocking what you are saying for sys admin purposes.)

Indeed, you answered exactly the question I asked. In the end I modified the PKGBUILD to only build the extensions I want. The packages in AUR (-git) seem to build broken software at the moment. Modifying them to build the source tagged 3.0.1 results in working extensions. I just hope there's a documented way to control enabled extensions per-use once there's an extension package in [extra]/[community].

I really do like the looking glass tool though.  That is one nifty little idsoftware kinda tool.  :-)

Yes, I agree... the only thing that bugs we with it is getting rid of it. Pressing 'ESC' to kill the window only works for me when I'm on the evaluator tab. /M -- Magnus Therning                      OpenPGP: 0xAB4DFBA4 email: magnus@therning.org   jabber: magnus@therning.org twitter: magthe               http://therning.org/magnus

On Thu, May 5, 2011 at 10:25, Casey Peter wrote:

On 05/05/2011 03:20 AM, Magnus Therning wrote:

...

On Thu, May 5, 2011 at 09:17, Casey Peter  wrote:

...

On 05/05/2011 01:43 AM, Magnus Therning wrote:

...

On Thu, May 5, 2011 at 07:38, Casey Peter    wrote:

...

On 05/04/2011 11:56 PM, Magnus Therning wrote:

...

On Mon, May 2, 2011 at 17:54, Damien Churchill  wrote: > > You can disable extensions, taken from the Gnome Shell extensions > page > [1] > > "Per-user and systemwide extensions can be disabled with the > GSettings > key org.gnome.shell.disabled-extensions" > > [1] http://live.gnome.org/GnomeShell/Extensions

Yes, indeed it does say that, but it doesn't say how to actually disable them :-)

I've tried to disable AlternateTab without success.  Here's what I've tried so far:

% gsettings set org.gnome.shell disabled-extensions "@as ['AlternateTab'] % gsettings set org.gnome.shell disabled-extensions "@as ['alternate-tab']

Has anyone else managed to disable extensions?

/M

Yes.  Disabling the extension is pretty simple.  Just go into the /usr/share/gnome-shell/extensions directory, rename the extension folder to .backup or something like .disabled. (just keep the original folder name in case you want to re-enable later).  You can then do an alt-f2 "lg" and enter and go to the extensions tab to verify what is/is not there.  To make the change alt+f2 "r" enter to restart the gnome-shell.

I'd very much like to avoid doing something like that, because it's "icky".  Renaming a system directory, owned by an installed package? That's not good practice for system administration in my opinion.  The Gnome 3 docs say it's possible to disable installed extensions on a per-user basis, I'd much prefer doing it that way.

/M

It might be "icky", but you asked a question...I answered it.  I have it working and do it that way for now, it works a charm, as some of those extensions I am not fond of, having gotten used to the defaults during the testing phase.  Adding a .xxx to the end of the file disables it and keeps the basic folder name structure intact so later if I want it back "on" I know exactly what to change.

 The package(s) are in AUR anyway, and until we get a better method of handling the stuff, this works for me.  As for good practice...its my own machine in my own home, and I know what goes on in exquisite detail on that box...so hey.  :D  (not knocking what you are saying for sys admin purposes.)

Indeed, you answered exactly the question I asked.  In the end I modified the PKGBUILD to only build the extensions I want.

The packages in AUR (-git) seem to build broken software at the moment.  Modifying them to build the source tagged 3.0.1 results in working extensions.

I just hope there's a documented way to control enabled extensions per-use once there's an extension package in [extra]/[community].

...

I really do like the looking glass tool though.  That is one nifty little idsoftware kinda tool.  :-)

Yes, I agree... the only thing that bugs we with it is getting rid of it.  Pressing 'ESC' to kill the window only works for me when I'm on the evaluator tab.

/M

I just hope that extensions gets a nice gui to match the look/n/feel of the desktop itself.  I'm actually a little surprised it didn't from the get-go as this would have assuaged a LOT of folks who wanted to change said "defaults" in the first place...but hey, I'm part of the great 'unwashed'.  heh heh

Off topic: Yep re: the escape in Looking glass, but apparently that is by design.  I read the docs online for that and its very specific as to how to leave it...and the escape in eval is it.  I'm guessing its to avoid leaving the app prematurely...but just guessing there.

Do you happen to remember the URL for that (unless it's http://live.gnome.org/GnomeShell/LookingGlass I haven't been able to find anything talking about keyboard short cuts). It's a developer tool, so I'm hoping there's some way of navigating between panes without having to reach for the mouse. /M -- Magnus Therning                      OpenPGP: 0xAB4DFBA4 email: magnus@therning.org   jabber: magnus@therning.org twitter: magthe               http://therning.org/magnus

On Mon, May 02, 2011 at 05:01:43PM +0100, Aljosha Papsch wrote:

...

This is such a basic issue that I refuse to believe I'm the first to

...

bump into this behaviour.  Hence I ask here first for some help.

I recently upgraded to Gnome3 and switching between windows with alt+tab is rather broken for me.  Here's why I say that:

1. I make sure I have two non-overlapping windows on the screen at the   same time. 2. I position the mouse pointer in one of the window. 3. At this point I can't switch focus to the other window with   alt+tab.

Basically I have two options:

1. Move the mouse pointer so that it's not in any window, then I can   use alt+tab. 2. Move the mouse to switch focus.

Neither of these is very convenient.

Does anyone recognise this?

/M

It's a design pattern of the GNOME Shell. Switching between windows work application based, not window based. Which means, if a Webbrowser is opened and two Shells, you won't switch between the shells but between Firefox and the last focused shell. You can get back the old behavior, though. Just install gnome-shell-extensions-git from AUR.

No, you misunderstand me. No matter what two windows I have, whether they are two different applications or not, I still see the same behaviour. I also see the same behaviour when switching between two windows of the same application (using alt+` on my machine). /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus Perl is another example of filling a tiny, short-term need, and then being a real problem in the longer term. -- Alan Kay

On Tue, May 03, 2011 at 11:08:50PM +0200, Christoph Glaubitz wrote:

On Mon, 2 May 2011 16:37:47 +0100 Magnus Therning wrote:

...

This is such a basic issue that I refuse to believe I'm the first to bump into this behaviour. Hence I ask here first for some help.

I recently upgraded to Gnome3 and switching between windows with alt+tab is rather broken for me. Here's why I say that:

1. I make sure I have two non-overlapping windows on the screen at the same time. 2. I position the mouse pointer in one of the window. 3. At this point I can't switch focus to the other window with alt+tab.

Basically I have two options:

1. Move the mouse pointer so that it's not in any window, then I can use alt+tab. 2. Move the mouse to switch focus.

Neither of these is very convenient.

Does anyone recognise this?

/M

Are you using focus follow mouse? $ gconftool-2 -g /apps/metacity/general/focus_mode sloppy

Indeed I was.

If you switch this to "click", you are able to switch via alt+tab or alt+^, again. But it's really hard to get used to "click" after more than a decade of using sloppy :(

Yes, changing to click sorted me out, but as you say it's hard to get used to. Even harder to get used to is the clunky WM ;-)

Seems to be a known upstream bug for quite a long timenow: https://bugzilla.gnome.org/show_bug.cgi?id=597190 and there is also a new dup for this bug https://bugzilla.gnome.org/show_bug.cgi?id=647232

btw. Seems not to be a gnome3 problem only, since Ubuntu 11.04 with unity has the same problem if you use "sloppy".

That's disappointing; that it has been know for long and still is unfixed. /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus I invented the term Object-Oriented, and I can tell you I did not have C++ in mind. -- Alan Kay

Am 06.05.2011 15:22, schrieb Steve Holmes:

Hey, I also just installed / upgraded to gnome3 and have run into some strange problems with keyboard navigation. First off, I cannot get into the desktop; also I can't find a reliable way to get into the system menu.

Keep in mind here, I'm totally blind and do not use the mouse. I rely strictly on use of the keyboard to navigate around the environment. With gnome2, one can use Ctrl+Alt+d to open the desktop from anywhere in gnome and the system menu was simply part of the main menu structure. Now the application and places menus are side by side but no system menu. Also, the key combination to focus the desktop doesn't work. In fact, when I use the Ctrl+Alt+Tab key combination to cycle focus between the top and botom panels, there is no desktop there either. In gnome2, the desktop was also included in that rotation.

Any ideas on how to fix this? Is this another sign of broken functionality in gnome3?

Hi Steve, I just had a look on Gnome’s website to see the status of their accessibility efforts for Gnome 3. It seems like Gnome Shell is currently not meant to be usable with a screen reader. It is on the roadmap for Gnome 3.2 though. As for your question about the behaviour of the desktop and panel: Gnome 3 no longer has icons on the desktop enabled by default. The concept of the panels also changed a lot. There no longer is a real bottom panel, all it offers are the notifications and icons that used to be in the system tray in Gnome 2. The taskbar is completely gone now, you can access your open applications by pressing the windows key and type in the name of the application. If the fallback mode works for you, I would just stick with it. It might also be a good idea addressing your questions according to Gnome’s accessibility directly to the upstream mailing list, as few people here have experience with it. The URL for signing up is http://mail.gnome.org/mailman/listinfo/gnome-accessibility-list -Gunnar