You are not logged in.
I've installed gnome3 and gnome-shell from testing, when I log in and gnome-shell starts up it will respond for a second and then freezes. Xorg.0.log and ~/.xsession-errors do not show and error messages in them.
I tried switching to nouveau but gnome-shell is very slow with it.
My graphics card is a GeForce 7300 LE
Offline
Gnome 3 is still in testing. Please open threads in the appropriate forums.
Moving to [testing].
As for the issues, Search the [testing] forum they are known issues and there are dedicated threads on them.
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
rivernate, Gnome-Shell does not seem to play very nice with Nvidia proprietary drivers, try switching to Nouveau.
A.J.
Offline
Erh... No problem here with gnome-testing and nvidia driver.
[fred@fredo-arch]$ pacman -Qi nvidia | grep Version
Version : 270.30-4
I have a nvidia GT210 pcie card in my computer.
Offline
The animations were slow for me, using the closed Nvidia drivers.
Could you please post the listing and content of your /etc/X11/xorg.conf.d/?
Thanks
Offline
The animations were slow for me, using the closed Nvidia drivers.
Could you please post the listing and content of your /etc/X11/xorg.conf.d/?Thanks
This is a known bug, unfortunately you can't report about this bug because its the driver fault.
You always can try Nouveau for using gnome3, i am using it and the animations are very fast.
Last edited by soomsoom (2011-04-09 06:39:56)
Offline
I have the same problem, too. any idea to resolve?
Offline
Please read what I wrote to @ajschwartz before you ask for resolution, because i gave it already.
Offline
I'm also having the same problem. testing gnome 3 on laptop with a go 7400 graphics card.
gnome-shell freezes after 1-2 seconds with proprietary drivers. works fine in fallback mode.
with nouveau gnome-shell is very slow and after 10-20 minutes of use gnome-shell no longer renders properly and the desktop becomes utterly unusable. once this occurs gnome no longer works for the initial 10-20 minutes and immediately bugs out even after restarting X and/or rebooting.
the only way I've been able to resolve the issue is to reboot once with proprietary drivers installed. after that I can reinstall nouveau and play around with gnome for another 10-20 minutes before the whole thing repeats itself.
any advice, hints, or tips on the matter would be greatly appreciated.
Offline
I've tried it with the nouveau driver, but I get very slow animations, can't really even drag around windows. When I try the Fedora based livecd though everything is smooth. I've tried both the nouveau in the repositories, and building it from git with the same result.
my /etc/X11/xorg.conf.d directory contains: 10-evdev.conf 10-quirks.conf 20-nvidia.conf
10-evdev.conf contains
#
# Catch-all evdev loader for udev-based systems
# We don't simply match on any device since that also adds accelerometers
# and other devices that we don't really want to use. The list below
# matches everything but joysticks.
Section "InputClass"
Identifier "evdev pointer catchall"
MatchIsPointer "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "evdev keyboard catchall"
MatchIsKeyboard "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "evdev touchpad catchall"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "evdev tablet catchall"
MatchIsTablet "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "evdev touchscreen catchall"
MatchIsTouchscreen "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
10-quirks.conf contains
# Collection of quirks and blacklist/whitelists for specific devices.
# Accelerometer device, posts data through ABS_X/ABS_Y, making X unusable
# http://bugs.freedesktop.org/show_bug.cgi?id=22442
Section "InputClass"
Identifier "ThinkPad HDAPS accelerometer blacklist"
MatchProduct "ThinkPad HDAPS accelerometer data"
Option "Ignore" "on"
EndSection
and 20-nvidia.conf contains
Section "Device"
Identifier "Default nvidia Device"
Driver "nvidia"
Option "NoLogo" "True"
EndSection
Offline
If you're trying to use Nouveau, you should have 20-nouveau.conf in /etc/X11/xorg.conf.c, not 20-nvidia.conf.
Take a look at the Wiki, and make sure the Nvidia module is blocked.
A.J.
Offline
For my own, Nvidia closed drivers version 260 (the one stated as "current" on the NVidia site) worked perfectly with Gnome3. Unfortunately, this module is build against 2.6.37 and doesn't work anymore with the new kernel... The 270 version allows me to login via a DM then show the Gnome Shell, but nothing more...
Nouveau is not seriously usable, here (lags of the interface, font garbled, etc.).
I've tried to googleize to build a 2.6.38 version of the nvidia driver but it seems it's out of my current knowledge
My next laptop will have a Intel GPU... My tiny IEEEPC 701 works without any problem!
Offline
As for the slowness, try to check this topic as well:
Offline
I've tried to googleize to build a 2.6.38 version of the nvidia driver but it seems it's out of my current knowledge
Take a look at https://wiki.archlinux.org/index.php/AB … he_ABS_way
In the PKGBUILD, you'll need to edit this line : _kernver='2.6.38-ARCH' and the depends/makedepends to suit your kernel version. Never tried, but should be working.
Offline
Take a look at https://wiki.archlinux.org/index.php/AB … he_ABS_way.
Yep, i spend some hours to play with ABS. I've managed to build the 260 nvidia driver against 2.6.38 but, on reboot, i get a warning that the ABI of the server have changed
If i set the option IgnoreAbi to true, the driver complains it doesn't find any screen...
So, i give up with Nvidia driver, and i will do my best with Nouveau waiting for enhancements...
Offline
Just lurking here because i am curious about gnome3 so please just ignore this if it is way of. But did you need to rebuild the drivers? Anyways if so I think a new release just hit and you could give it a go?
270.41.03 for Linux x86/x86_64 released - http://aur.archlinux.org/packages.php?ID=19224 - https://aur.archlinux.org/packages.php?ID=15152
Last edited by cell (2011-04-11 22:48:01)
Offline
Anyways if so I think a new release just hit and you could give it a go?
Already tested... No change... It seems the 270.x versions of Nvidia driver are not for me... And as the 260.x versions are now obsoleted by the new kernel, the only options for me are :
1) revert to the 2.6.37 kernel and enjoy the 260.x Nvidia drivers
2) forget the Nvidia driver and using Nouveau (with its current slowness)
3) forget Gnome3 and other composite wm.
4) throw my laptop in a trash, playing poker, win and buy a new laptop with anything but a NVidia card.
Last edited by jaco (2011-04-11 23:27:35)
Offline
this seems weird. after installing gnome-shell-extensions-git from the aur, gnome-shell is running much much smoother with nouveau. I can wait for the updated nvidia driver a little bit longer now
edit: but it can't be related to gnome-shell-extensions I guess. there must have been something else which has been upgraded or changed..
Last edited by martin_herndl (2011-04-12 15:25:41)
Offline
I re installed the nouveau and it's the same super slow animations. I also tried the new nvidia drivers with no change, Gnome-shell still locks up.
The /et/X11/xorg.conf.d/ now contains:
10-evdev.conf 10-quirks.conf 20-nouveau.conf
10-evdev.conf
#
# Catch-all evdev loader for udev-based systems
# We don't simply match on any device since that also adds accelerometers
# and other devices that we don't really want to use. The list below
# matches everything but joysticks.
Section "InputClass"
Identifier "evdev pointer catchall"
MatchIsPointer "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "evdev keyboard catchall"
MatchIsKeyboard "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "evdev touchpad catchall"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "evdev tablet catchall"
MatchIsTablet "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "evdev touchscreen catchall"
MatchIsTouchscreen "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
10-quirks.conf
# Collection of quirks and blacklist/whitelists for specific devices.
# Accelerometer device, posts data through ABS_X/ABS_Y, making X unusable
# http://bugs.freedesktop.org/show_bug.cgi?id=22442
Section "InputClass"
Identifier "ThinkPad HDAPS accelerometer blacklist"
MatchProduct "ThinkPad HDAPS accelerometer data"
Option "Ignore" "on"
EndSection
20-nouveau.conf
Section "Device"
Identifier "n"
Driver "nouveau"
EndSection
Offline
Could you post your output of pacman -Qs nouveau?
I have now (with fast animations which were slow before):
pacman -Qs nouveau
local/nouveau-dri 7.10.2-2
Mesa classic DRI + Gallium3D drivers for Nouveau
local/xf86-video-nouveau 0.0.16_git20110316-2
Open Source 3D acceleration driver for nVidia cards (experimental)
What I basically did was installing the patched nvidia packages from this thread => https://bbs.archlinux.org/viewtopic.php?id=116558
Afterwards I uninstalled nouvea and tried the nvidia driver again which still froze.
Then I uninstalled nvidia, installed nouveau again and I also installed gnome-shell-extensions-git from aur.
Afterwards I suddenly got fast animations. I then uninstalled gnome-shell-extensions-git and have still fast animations with nouveau. I just can't really understand why.
edit: I just saw that the patched packages are down because of the new nvidia driver. I'm going to try it out.
edit2: ok, unfortunately still freezes with the new drivers
Last edited by martin_herndl (2011-04-12 19:20:01)
Offline
here is the output of pacman -Qs
local/nouveau-dri 7.10.2-2
Mesa classic DRI + Gallium3D drivers for Nouveau
local/xf86-video-nouveau 0.0.16_git20110316-2
Open Source 3D acceleration driver for nVidia cards (experimental)
I tried installing gnome-shell-extensions-git from aur as well with no effect, tough it pulled in other things like gnome-common-git with it. I tried the new nvidia drivers and they didn't do anything either
Offline
I just saw that my testing updated libgl, nouveau-dri and mesa. maybe this new versions fix things up for you? but still it won't explain why it got smoother for me.
My pacman.log said that I also updated gnome-sharp yesterday, but I don't expect this to be the cause either.
Maybe there is something related to this issue in your xorg.log?
Offline
i just -Syu to nvidia 270.41.03-1, gnome-shell 3.0.0.2-2 and a bunch of other stuff, after that gnome-shell is working smooth for me. Great work
Last edited by kolos (2011-04-13 23:43:41)
och noes!
Offline
I tried it again both with the latest nvidia and nouveau driver. I'm still having the same behaviors, my Xorg.0.log doesn't show any warnings or errors, and with the nvidia driver I'm not getting anything userful in my xesession-errors, with the nouveau driver I get the following in my xsession-errors:
/etc/gdm/Xsession: Beginning session setup...
/etc/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- gnome-session
nvfx_screen_get_param:87 - Warning: unknown PIPE_CAP 36
nvfx_screen_get_param:87 - Warning: unknown PIPE_CAP 45
nvfx_screen_get_param:87 - Warning: unknown PIPE_CAP 43
nvfx_screen_get_param:87 - Warning: unknown PIPE_CAP 44
GNOME_KEYRING_CONTROL=/tmp/keyring-49qpGt
GPG_AGENT_INFO=/tmp/keyring-49qpGt/gpg:0:1
GNOME_KEYRING_CONTROL=/tmp/keyring-49qpGt
GPG_AGENT_INFO=/tmp/keyring-49qpGt/gpg:0:1
GNOME_KEYRING_CONTROL=/tmp/keyring-49qpGt
GPG_AGENT_INFO=/tmp/keyring-49qpGt/gpg:0:1
SSH_AUTH_SOCK=/tmp/keyring-49qpGt/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-49qpGt
GPG_AGENT_INFO=/tmp/keyring-49qpGt/gpg:0:1
SSH_AUTH_SOCK=/tmp/keyring-49qpGt/ssh
(gnome-settings-daemon:3232): keybindings-plugin-WARNING **: Key binding (screenreader) is incomplete
(gnome-settings-daemon:3232): keybindings-plugin-WARNING **: Key binding (magnifier) is incomplete
(gnome-settings-daemon:3232): keybindings-plugin-WARNING **: Key binding (onscreenkeyboard) is incomplete
nvfx_screen_get_param:87 - Warning: unknown PIPE_CAP 36
nvfx_screen_get_param:87 - Warning: unknown PIPE_CAP 45
nvfx_screen_get_param:87 - Warning: unknown PIPE_CAP 43
nvfx_screen_get_param:87 - Warning: unknown PIPE_CAP 44
** Message: applet now removed from the notification area
JS LOG: GNOME Shell started at Thu Apr 14 2011 08:56:11 GMT-0600 (MDT)
** Message: applet now embedded in the notification area
ConfigBase::load: Unable to open /home/nate/.config/terminator/config ([Errno 2] No such file or directory: '/home/nate/.config/terminator/config')
Warning: python-keybinder is not installed. This means the hide_window shortcut will be unavailable
Unable to bind hide_window key, another instance/window has it.
<Window object at 0x2142640 (terminatorlib+window+Window at 0x24ca0c0)> is not in registered window list
Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen!
(gnome-settings-daemon:3232): Gdk-WARNING **: gnome-settings-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
gnome-session[3196]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
(nm-applet:3289): Gdk-WARNING **: nm-applet: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
(gdu-notification-daemon:3287): Gdk-WARNING **: gdu-notification-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
(gnome-screensaver:3288): Gdk-WARNING **: gnome-screensaver: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
applet.py: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
[1302792965,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the application
Window manager warning: Log level 16: gnome-shell: Fatal IO error 104 (Connection reset by peer) on X server :0.
gnome-shell-calendar-server[3295]: Lost (or failed to acquire) the name org.gnome.Shell.CalendarServer - exiting
g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
Offline
Don't try to find a way to fix this by your own. This is a known bug. There are a lot of similar problems here: http://www.nvnews.net/vbulletin/forumdisplay.php?f=14 Just follow the threads till there is a solution. I also daily checking this.
Offline