Once up and running, Gnome 3/gnome-shell really works well… I can’t even boot the Fedora 15 version because of an install bug they have with my Via C7 CPU and the Ubuntu 11.10 Beta is all kinds of buggy getting in and getting out.
I am becoming a big gnome-shell fan… significant speed and polish… and using the <Super> button to get to the switching screen has made jumping between applications quite manageable. It seems the ultimate purpose is to keep the user focused on what they are working on vs. providing distractions on screen to tempt you to go application hopping… which is great for those that actually want to accomplish something rather than those multi-tasking “…masters of none”.
The 2 issues with the Beta I’ve come across:
Upon Install, the network is set up for manual activation, i.e., when I logged on I did not have an internet connection… but just had to go to yast in the network section and change the radio button from manual to automatic connection and all worked fine and was a permanent solution
It is a known concern that gnome-shell does not come with a power-off button/option… have to log -off and power off from the login screen… however now with this beta, even more bizarrely, there is no power off option in the login screen, so to turn off my computer I have to hold in my power button on my physical computer every time… I’ve not figured out the solution here. While there are Gnome Shell Extensions that should add the power off button option to the gnome-shell menu, the extensions in yast downloaded but are not accessible/activatible, I’m thinking a compatibility problem with the latest gnome version
In summary, I’m real excited where things are at but this power off issue is a pretty bad thing, but understandable in a beta version.
I see with Gnome 3.2 that they have changed the shell’s workspace switcher behaviour a little. Before on Gnome 3.0 it used to autohide until you moused near it, whereupon it sprang into life. Now with 3.2 it is always visible. While this has certain practical benefits, I much prefer the old autohide behaviour. Are there any settings or extensions in Gnome 3.2 to enable a user to keep the older autohide behaviour in 3.2? Thanks.
Now obviously I would be changing the value to the 3.0 default of 32px to get my autohiding workspace back. I’ll be thrilled if this works though. It might seem like a silly thing, but I have really become accustomed to the tactility of the Gnome 3 desktop, and this small feature helps to add to that for me. Nice if it can be put back by the user, but I would love to see a friendlier extension created for these little things. Hopefully this will happen in time.
God I love Gnome 3. Can’t wait for the new openSUSE.
The workspace switcher in the overview remains expanded by keeping its full width displayed when you are using more than one workspace.
I was basically requesting a way to change this behaviour back to the way it was in Gnome 3.0, where the workspace switcher in the shell autohides until you mouse over it. I just prefer this tactile feedback to the “always on” nature of the feature in Gnome 3.2. I think the above customisation is what I’m looking for, for when I do make the change from openSUSE 11.4 to 12.1. Am I mistaken?
I was not aware of the <alt> menu trick in gnome-shell to get the power-off option. Very helpful… One more item is my system always starts with numlock off. I went into yast /ets/sysconfig/editor and changed the numlock option from bios to yes and it still did nothing.
lø., 08.10.2011 kl. 17.56 +0000, skrev tseg:
> I was not aware of the <alt> menu trick in gnome-shell to get the
> power-off option. Very helpful… One more item is my system always
> starts with numlock off. I went into yast /ets/sysconfig/editor and
> changed the numlock option from bios to yes and it still did nothing.
Activate numlock upon login
Install numlockx. Then, add a startup command to launch numlockx.
zypper in numlockx
Then as user
The above command opens the Startup Applications Preferences applet.
Click Add and enter the following:
Command: /usr/bin/numlockx on
Comment: Turns on numlock.
This is not a system-wide appearance tweak. Repeat these steps for each
user wishing to activate numlock upon login.
Don’t feel bad, I wasn’t aware of this trick either! Like you, I had to resort to holding down the power button on my laptop, which can’t be all that good for the OS - at least, until I remembered that I could shut it down from the command line. It seems very non-intuitive to hide such important options – I mean, what new user is going to think, “oh, just press the ALT key when all I see are ‘Log Out’ and ‘Suspend’”? I do hope this is addressed before 12.1 is officially released.
Since this is my first post here, I suppose a quick introduction is in order here. I’m a fairly seasoned Linux user, having cut my teeth on Linux with Ubuntu 7.04. It’s still a learning experience for me, as I’m still learning new tricks and ways to do things. When it was released earlier this year, I switched from Ubuntu to Mint 11. However, since Ubuntu seems committed to Unity, and Mint seems to want to stay with Gnome 2, I’m trying out various Gnome 3 -based distros, and have taken a bit of a liking to OpenSUSE. It’s going to be a bit of a challenge switching from a Debian-based system to an RPM based system, but I think I can handle it, with a little bit of help from the OpenSUSE community .
I’ve tried out the 12.1 Gnome LiveCD on a USB stick for a while and, beyond the aforementioned hidden shutdown feature, and the apparent lack of subpixel font smoothing, I haven’t run into any real issues with the LiveCD environment. I am now downloading the DVD and considering cannonballing right on into the pool here. Anyone know of any issues I should be aware of, beyond the usual beta release disclaimers?
I can’t see the ‘hibernate’ option on the menu ( I can see suspend but no hibernate ), any idea why ?
The hibernation feature does work if I use command line ‘pm-hibernate’.
And something else, in the terminal or xterm , some paths are not added to the default SHELL. For instant if I want to type ‘sudo reboot’ it will tell me ‘reboot command doesn’t exist’ so I need to give the full path which is ridiculous ‘sudo /sbin/reboot’ …
> And something else, in the terminal or xterm , some paths are not added
> to the default SHELL. For instant if I want to type ‘sudo reboot’ it
> will tell me ‘reboot command doesn’t exist’ so I need to give the full
> path which is ridiculous ‘sudo /sbin/reboot’ …
yep, that is by design (why so designed i’m not sure…ask the
devs)…but it is pretty easy fix: ask your administrator to add
openSUSE®, the “German Automobiles” of operating systems