You are not logged in.
Hi,
once installed gonme3, gnome does not start. When trying to login with GDM gnome says that something went wrong and I can only click on logout... can you help me? Which log can I check to give you some more info?
Linux Registered User: #431529 - http://counter.li.org/
Offline
same thing happened to me, I fixed it by reinstalling the gnome meta package (pacman -S gnome). it downloaded some extra things that weren't downloaded when I ran pacman -Syu
Offline
Already done, I installed it with
yaourt -S gnome-shell gnome gnome-extra notification-daemon
the error persists...
Linux Registered User: #431529 - http://counter.li.org/
Offline
I had the same problem with compiz and fusion-icon. It seems that if compiz starts with session, gnome shell fails to load.
Offline
I've already disinistalled compiz, the error persists ![]()
Linux Registered User: #431529 - http://counter.li.org/
Offline
I have the same issue, so unfortunately no help here ![]()
To be exact, it does start once right after I've rebooted, but not after that.
Starting with gdm gives the "Oops"-message and startx causes gnome-shell to hog all my memory and fail.
There are some warnings in .xsession-errors about 'gnome-settings-daemon' receiving and X Windows System error, but I'm not sure whether it is related. KDE and Xfce4 works fine though and so did Gnome 2 before the upgrade. A bit disheartening to say at least.
Offline
found the problem!
It's double monitor configuration in xorg.conf... one deleted xorg.conf file gnome starts.
Is it possibile that gnome 3 does not start with two monitors????? It's a shame!!!
Linux Registered User: #431529 - http://counter.li.org/
Offline
That's a different problem as mine then as I do not have a xorg.conf and only one monitor. Shame indeed.
Offline
I have noticed that gnome-shell will crash for sure if you leave KWIN in fusion-icon after a visit in KDE. When set to Compiz it works with gnome-shell.
I also got the "Oh no something went wrong try to log out" (and that never works) on several other occasions. I suspected having gkrellm in the startup programs could have caused it.
When this happens I have to remove gnome-shell, log in to fallback mode, then reinstall gnome-shell and everything works again. I use the Slim login manager
Good ol' gnome was very stable. Gnome3 is not - so far. That is a shame.
Last edited by viking60 (2011-05-04 09:09:26)
"Common sense is not common"
Offline
I have the same issue, so unfortunately no help here. I have tried to remove gnome-shell, and then reinstall gnome-shell but it does not help.
Offline
When you log in after having removed gnome-shell; Do you get in to the fallback mode? Does that chrash as well?
Edit:
The fix for the crash above::
When "dual booting" with KDE I need fusion-icon to set the Kwin in KDE. Fusion-icon has the options Compiz Metacity and Kwin. If I leave it at Kwin and log out to log into Gnome 3 it will crash every time. Also if it is set it to metacity it will crash every time without exception.
To fix it I have to log in to KDE and set the fusion-icon to Compiz and log out, and then log into Gnome3.
Last edited by viking60 (2011-05-06 13:13:53)
"Common sense is not common"
Offline
I am able to start gnome 3 in fallback mode by removing gnome-shell, but with gnome-shell I just get that error and the only option is to kill the X session.
Why did they decide to switch the defaults all over to unstable software?
############ EDIT ################
In no particular order, I was messing around with some things. I did an -Syuu with the testing repository, then an -Syuu without it, trashed compiz, then started X with a GNOME fallback mode session, installed GNOME-Shell while in fallback mode, then in the terminal said "gnome-shell --replace" and voodoo magic happened.
Doing any of those things without each other in the non-magic order did not make GNOME-shell work.
Now my real question: Why are they emulating the OS X interface? I stuck to GNOME because it's not so flashy. Too bad LXDE has font problems in both Midori and Firefox (but nothing else), so I'm stuck in Fallback Mode for a little bit.
###############################
Last edited by jenovanomusuko (2011-05-08 17:42:53)
Offline
I can confirm the first post.
First I thought it is a bug with gnome3, because no way to launch gnome neither on a virtual machine nor on a physical one (each upon fresh install).
I was slowly getting crazy but changing the display manager to slim made the trick for me.
It seems that it has something to do with gdm although I'me not sure.
P.-S.: Starting with just .xinitrc also went wrong.
Last edited by eddilein (2011-05-08 15:09:15)
Offline
Greetings
I had this problem after my last update. Gnome 3 would start up, show the desktop for a brief moment - and them give me the "Opps...." message and throw me back to the command line. Complaining about everything form ConsoleKit to Dbus.
Anyway - I am rambling on here...
I solved it this way form the command line
Restarting the hardware clock and dbus
sudo /etc/rc.d/hwclock restart
sudo /etc/rc.d/dbus restartAnd - remembering something from the wiki entry on GNOME 3 set hwclock to my DAEMONS line in rc.conf
vi +/DAEMONS /etc/rc.conf
DAEMONS=(...hwclock...)Hope this helps
Cheers
E5o
Offline
As an addendum, I think maybe restart dbus is enough.
YMMV
Cheers
E5o
Offline
Hi,
I start Gnome3 via $HOME/.xinitrc
exec ck-launch-session gnome-session
and than startx. I had only the background image of the desktop until I uncheck the save the desktop state in the Options tab of gnome-session-properties. It look like if the directory $HOME/.config/gnome-session/saved-session/ must be empty, specially empty of the mutter.desktop file. Weird, look to me to be an incompatibility between Gnome 2 and Gnome 3.
Offline
Hi,
I start Gnome3 via $HOME/.xinitrcexec ck-launch-session gnome-session
and than startx. I had only the background image of the desktop until I uncheck the save the desktop state in the Options tab of gnome-session-properties. It look like if the directory $HOME/.config/gnome-session/saved-session/ must be empty, specially empty of the mutter.desktop file. Weird, look to me to be an incompatibility between Gnome 2 and Gnome 3.
Maybe this will help you?
https://bbs.archlinux.org/viewtopic.php … 33#p933533
Offline