Gnome3 'normal look' disabled in F16 how to re-enable?

[Kaya Saman]

Hi,

my OS disabled the 'new' Gnome3 look theme stating that I don't have the GFX support for it to run. That's balony as the machine is a brandnew i7 based system using the Intel X3000 or whatever HD graphics card.

Yep the GPU is too new for the drivers as they or rather Gnome doesn't know what type of graphics card I'm using.

Is there a way to re-enable what Gnome3 calls the 'normal' experience as currently am running in non-forced Classic mode.

Basically I just want control over my system back. I'm pretty sure if I get rid of the user account then re-build it, everything will be fine but that's currently not what I want to do.


Has anyone got any ideas??

As stated the system is not being put into classic mode by:

System Settings -> System Info -> Graphics -> Force Classic mode

but nonetheless it still is in Classic mode.


Thanks for any support!

[Dan]

Deleting the user account won't change a thing, so there isn't any reason I can see to do that.

Spend some time searching the forum. I don't remember for sure but I think this (or something very similar) has been discussed by adamw.

[Kaya Saman]

Ok this is weird as Gnome3 works fine if I login from root???? - run startx from root user account - Don't use GDM!

I discovered this thread:

http://forums.fedoraforum.org/showth...+gnome3&page=2

Which is probably what you mentioned and the erros am getting are here:

glxinfo | grep direct

yes

$ vainfo
libva: libva version 0.32.0
libva: va_getDriverName() returns 0
libva: Trying to open /usr/lib64/dri/i965_drv_video.so
libva: va_openDriver() returns 0
vainfo: VA API version: 0.32
vainfo: Driver version: i965 Driver 0.1
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple            :	VAEntrypointVLD
      VAProfileMPEG2Main              :	VAEntrypointVLD
      VAProfileH264Baseline           :	VAEntrypointVLD
      VAProfileH264Baseline           :	VAEntrypointEncSlice
      VAProfileH264Main               :	VAEntrypointVLD
      VAProfileH264Main               :	VAEntrypointEncSlice
      VAProfileH264High               :	VAEntrypointVLD
      VAProfileH264High               :	VAEntrypointEncSlice
      VAProfileVC1Simple              :	VAEntrypointVLD
      VAProfileVC1Main                :	VAEntrypointVLD
      VAProfileVC1Advanced            :	VAEntrypointVLD

from the other thread provides me with tihs:

vainfo
libva: VA-API version 0.32.0
libva: va_getDriverName() returns 0
libva: Trying to open /usr/lib64/dri/i965_drv_video.so
libva: va_openDriver() returns -1
vaInitialize failed with error code -1 (unknown libva error),exit

Well reading further in that thread the last post and solution seemed to be this:

So, in order to disable this I went in as root and edited /etc/default/grub and removed the 'nomodeset' from the GRUB_CMDLINE_LINUX option.

However within my grub file under default that option hasn't even been enabled:

GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Fedora"
GRUB_DEFAULT=saved
GRUB_CMDLINE_LINUX="rd.md=0 rd.lvm=0 rd.dm=0 quiet SYSFONT=latarcyrheb-sun16 rhgb  KEYTABLE=uk rd.luks=0 LANG=en_US.UTF-8"

Hmm...... have no idea!

[Dan]

Hmmm.

Ok. Create a new user account (but do not remove the old one) and make sure it's in the administrator's group, and try booting to RL3 and running startx from there.

[Kaya Saman]

I don't have an Admin group....

what I did was just add myself to these groups:

daemon sys audio cdrom dbus usbmuxd jackuser pulse pulse-access

I will try doing the same for the new user too but will wait before, if there are any other groups I should be included in.

Oh btw since then I installed:

xorg-x11-drv-vesa
xorg-x11-drv-fbdev

as after installing glxinfo and vainfo my X stopped working??

---------- Post added at 06:33 PM ---------- Previous post was at 06:22 PM ----------

Just created user test with same group additions as mine and failed to activate full-blown Gnome3 again.

I think it means that I'm not added to a particular group that I need to be!

The graphics drivers seem to be sorted out now so I just need to figure out the groups....

[Kaya Saman]

Ok for anyone wanting to know WHY the new look Gnome3 isn't working.....

I am using run level 3 or init level 3..... this has certain restrictions I believe stopping the system knowing what's going on graphically from a software point of view.


If I run init 5 or runlevel 5..... Gnome3 is normal! and how it should be.


For anyone who doesn't know how to switch between level 3 and 5 open up a terminal and go to:

/etc/systemd/system

type ls -l | grep default and you should get presented with a symlink:

# ls -l /etc/systemd/system
total 36
drwxr-xr-x. 2 root root 4096 Jan 26 11:41 basic.target.wants
drwxr-xr-x. 2 root root 4096 Jan 26 12:40 bluetooth.target.wants
lrwxrwxrwx. 1 root root   40 Jan 26 12:37 dbus-org.freedesktop.Avahi.service -> /lib/systemd/system/avahi-daemon.service
lrwxrwxrwx. 1 root root   42 Jan 26 12:40 dbus-org.freedesktop.NetworkManager.service -> /lib/systemd/system/NetworkManager.service
lrwxrwxrwx. 1 root root   36 Jan 26 16:48 default.target -> /lib/systemd/system/runlevel3.target
drwxr-xr-x. 2 root root 4096 Jan 26 11:41 default.target.wants
drwxr-xr-x. 2 root root 4096 Jan 26 11:41 getty.target.wants
drwxr-xr-x. 2 root root 4096 Jan 26 12:17 graphical.target.wants
drwxr-xr-x. 2 root root 4096 Jan 27 08:31 multi-user.target.wants
drwxr-xr-x. 2 root root 4096 Jan 26 11:41 network.target.wants
drwxr-xr-x. 2 root root 4096 Jan 26 13:21 sockets.target.wants
drwxr-xr-x. 2 root root 4096 Jan 26 12:38 sysinit.target.wants

The default.target is what you have to change to runlevel5.target while keeping the same dir path.


If anyone knows how to get the full Gnome3 experience whlie loading X from runlevel 3 please respond and that is intention of the original thread, however, apart from that issue everything is in order!!!!