Arch Linux

Rukiri

Member

Registered: 2011-11-08

Posts: 45

Gnome-Shell: Oh no somthing has gone wrong

currently trying to boot into the gnome3 desktop, but I get an error stating oh no something has gone wrong.
When I uninstall gnome-shell it will boot into fallback mode just fine.

I currently have the Nvidia drivers installed, and all of the gnome and gnome-extra packages.

Is this a known issue with Nvidia? as KDE loads just fine however I do prefer gnome3 when I have it modified to my liking.

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,424

Website

Re: Gnome-Shell: Oh no somthing has gone wrong

Given the fact that the error message is worse than useless, you might want to look through your logs to see what the problem is...

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Rukiri

Member

Registered: 2011-11-08

Posts: 45

Re: Gnome-Shell: Oh no somthing has gone wrong

What log would that be?  Xorg.0.log didn't provide any answers.

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,424

Website

Re: Gnome-Shell: Oh no somthing has gone wrong

Your session log would be the first place I would look...

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

akspecs

Member

Registered: 2012-02-11

Posts: 179

Re: Gnome-Shell: Oh no somthing has gone wrong

how are you starting X?  If it's through startx, you have to have a properly configured .xinitrc file in your ~/ directory.

The main thing is to be sure to comment out the if ... fi block.

#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)

#if [ -d /etc/X11/xinit/xinitrc.d ]; then
# for f in /etc/X11/xinit/xinitrc.d/*; do
#    [ -x "$f" ] && . "$f"
#  done
#  unset f
#fi

exec ck-launch-session gnome-session
# exec startkde
# exec ck-launch-session dbus-launch startxfce4
# ...or the Window Manager of your choice

Also, make sure the dbus daemon is running.  It's best to have it in the daemons section in /etc/rc.conf

DAEMONS=(... dbus ...)

The dbus daemon is always required for gnome no matter how you try to run it.

All of this is in the gnome arch wiki:
https://wiki.archlinux.org/index.php/GNOME

Last edited by akspecs (2012-06-21 22:32:56)

Rukiri

Member

Registered: 2011-11-08

Posts: 45

Re: Gnome-Shell: Oh no somthing has gone wrong

how are you starting X?  If it's through startx, you have to have a properly configured .xinitrc file in your ~/ directory.

The main thing is to be sure to comment out the if ... fi block.

#!/bin/sh
#
# ~/.xinitrc
#
# Executed by startx (run your window manager from here)

#if [ -d /etc/X11/xinit/xinitrc.d ]; then
# for f in /etc/X11/xinit/xinitrc.d/*; do
#    [ -x "$f" ] && . "$f"
#  done
#  unset f
#fi

exec ck-launch-session gnome-session
# exec startkde
# exec ck-launch-session dbus-launch startxfce4
# ...or the Window Manager of your choice

Also, make sure the dbus daemon is running.  It's best to have it in the daemons section in /etc/rc.conf

DAEMONS=(... dbus ...)

The dbus daemon is always required for gnome no matter how you try to run it.

All of this is in the gnome arch wiki:
https://wiki.archlinux.org/index.php/GNOME

Yes, I have dbus in rc.conf, and your ~/.xinitrc is the same as mine.

Would it be a video issue?  I have the propitery Nvidia indrivers installed, works great in kde.
Where would Gnome's session be stored? I tried to searc for them but didn't find anything.

dejavu

Member

Registered: 2008-05-26

Posts: 103

Re: Gnome-Shell: Oh no somthing has gone wrong

I had probably the same issue recently and I didn't found any useful information too. What I have seen was, that in my case the gnome-shell was segfaulted in the gnome-shell. But I didn't found out why.
I would recommend you to rename the folder <home_directory>/.config/dconf to dconf_ and then log in again. In this file there are your gnome settings only and therefore it shouldn't take more than five minutes to set them again.
If you still can't login then you have another issue. Then I would rename the folder back again and you should provide more logfiles.

Last edited by dejavu (2012-06-21 22:52:46)

wonder

Developer

From: Bucharest, Romania

Registered: 2006-07-05

Posts: 5,941

Website

Re: Gnome-Shell: Oh no somthing has gone wrong

it would be cool to post the entire startx output, since you do not use gdm to have the logs stored in ~/.xsession-errors

---

Give what you have. To someone, it may be better than you dare to think.

Rukiri

Member

Registered: 2011-11-08

Posts: 45

Re: Gnome-Shell: Oh no somthing has gone wrong

Startx.log

X.Org X Server 1.12.2
Release Date: 2012-05-29
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.0.32-1-lts x86_64 
Current Operating System: Linux archbox 3.4.3-1-ARCH #1 SMP PREEMPT Mon Jun 18 08:28:29 CEST 2012 x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=/dev/mapper/arch-root ro quiet add_efi_memmap
Build Date: 30 May 2012  07:24:13PM
 
Current version of pixman: 0.26.0
	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Jun 21 18:22:37 2012
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using config directory: "/etc/X11/xorg.conf.d"
gnome-session[10094]: WARNING: Could not connect to ConsoleKit: Could not get owner of name 'org.freedesktop.ConsoleKit': no such name
gnome-session[10094]: WARNING: Could not connect to ConsoleKit: Could not get owner of name 'org.freedesktop.ConsoleKit': no such name
GNOME_KEYRING_CONTROL=/root/.cache/keyring-H49iMa
GNOME_KEYRING_PID=10112
GNOME_KEYRING_CONTROL=/root/.cache/keyring-H49iMa
GPG_AGENT_INFO=/root/.cache/keyring-H49iMa/gpg:0:1
SSH_AUTH_SOCK=/root/.cache/keyring-H49iMa/ssh
GNOME_KEYRING_CONTROL=/root/.cache/keyring-H49iMa
GPG_AGENT_INFO=/root/.cache/keyring-H49iMa/gpg:0:1
GNOME_KEYRING_CONTROL=/root/.cache/keyring-H49iMa
GPG_AGENT_INFO=/root/.cache/keyring-H49iMa/gpg:0:1
SSH_AUTH_SOCK=/root/.cache/keyring-H49iMa/ssh

** (gnome-settings-daemon:10109): WARNING **: Failed to connect context: OK

** (gnome-settings-daemon:10109): WARNING **: Failed to get session for pid: GDBus.Error:org.freedesktop.ConsoleKit.Manager.GeneralError: Unable to lookup session information for process '10109'

** (gnome-settings-daemon:10109): WARNING **: Failed to get session for pid: GDBus.Error:org.freedesktop.ConsoleKit.Manager.GeneralError: Unable to lookup session information for process '10109'
Initializing tracker-store...
Tracker-Message: Setting up monitor for changes to config file:'/root/.config/tracker/tracker-store.cfg'
Initializing tracker-miner-fs...
Tracker-Message: Setting up monitor for changes to config file:'/root/.config/tracker/tracker-store.cfg'
Starting log:
  File:'/root/.local/share/tracker/tracker-store.log'
Tracker-Message: Setting up monitor for changes to config file:'/root/.config/tracker/tracker-miner-fs.cfg'
Starting log:
  File:'/root/.local/share/tracker/tracker-miner-fs.log'
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Compat map for group 2 redefined
>                   Using new definition
> Warning:          Compat map for group 3 redefined
>                   Using new definition
> Warning:          Compat map for group 4 redefined
>                   Using new definition
Errors from xkbcomp are not fatal to the X server
W: [pulseaudio] main.c: This program is not intended to be run as root (unless --system is specified).
Failed to play sound: Not available

** (nm-applet:10209): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: Launch helper exited with unknown return code 1
** Message: applet now removed from the notification area

** (nm-applet:10209): WARNING **: fetch_connections_done: error fetching connections: (25) Launch helper exited with unknown return code 1.

** (nm-applet:10209): WARNING **: Failed to register as an agent: (25) Launch helper exited with unknown return code 1
process 10201: D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/etc/machine-id": No such file or directory
See the manual page for dbus-uuidgen to correct this issue.
  D-Bus not built with -rdynamic so unable to print a backtrace
gnome-session[10094]: WARNING: Application 'gnome-shell.desktop' killed by signal 6
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Compat map for group 2 redefined
>                   Using new definition
> Warning:          Compat map for group 3 redefined
>                   Using new definition
> Warning:          Compat map for group 4 redefined
>                   Using new definition
Errors from xkbcomp are not fatal to the X server
process 10255: D-Bus library appears to be incorrectly set up; failed to read machine uuid: Failed to open "/etc/machine-id": No such file or directory
See the manual page for dbus-uuidgen to correct this issue.
  D-Bus not built with -rdynamic so unable to print a backtrace
gnome-session[10094]: WARNING: Application 'gnome-shell.desktop' killed by signal 6
gnome-session[10094]: WARNING: App 'gnome-shell.desktop' respawning too quickly
gnome-session[10094]: WARNING: Unable to determine session: Unable to lookup session information for process '10094'
gnome-session[10094]: WARNING: Unable to determine session: Unable to lookup session information for process '10094'

(gnome-settings-daemon:10109): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed

(gnome-settings-daemon:10109): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
[1340320959,000,xklavier.c:xkl_engine_start_listen/] 	The backend does not require manual layout management - but it is provided by the application
xinit: connection to X server lost

waiting for X server to shut down 
Received signal:1->'Hangup'
Received signal:1->'Hangup'
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.

Received signal:15->'Terminated'

(tracker-miner-fs:10206): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed

(tracker-miner-fs:10206): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed

(tracker-miner-fs:10206): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
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.

Received signal:15->'Terminated'
OK


OK

Server terminated successfully (0). Closing log file.

Last edited by Rukiri (2012-06-21 23:25:49)

wonder

Developer

From: Bucharest, Romania

Registered: 2006-07-05

Posts: 5,941

Website

Re: Gnome-Shell: Oh no somthing has gone wrong

gnome-session[10094]: WARNING: Could not connect to ConsoleKit: Could not get owner of name 'org.freedesktop.ConsoleKit': no such name

did you removed consolekit by any chance?

---

Give what you have. To someone, it may be better than you dare to think.

Rukiri

Member

Registered: 2011-11-08

Posts: 45

Re: Gnome-Shell: Oh no somthing has gone wrong

Hmm no, as I have ck-launch-session for kde and I'm in kde right now.
I'm kinda mystified about that error.

wonder

Developer

From: Bucharest, Romania

Registered: 2006-07-05

Posts: 5,941

Website

Re: Gnome-Shell: Oh no somthing has gone wrong

Hmm no, as I have ck-launch-session for kde and I'm in kde right now.
I'm kinda mystified about that error.

just reinstall consolekit and see if is working.

---

Give what you have. To someone, it may be better than you dare to think.

Rukiri

Member

Registered: 2011-11-08

Posts: 45

Re: Gnome-Shell: Oh no somthing has gone wrong

Tried and nothing, removed gnome-shell and can at least boot into fallback.
Seems to be a gnome-shell issue.

Am I missing any dependancies?

Edit:
Don't know if it matters but I have a Nvidia geforce gtx 680 graphics card, maybe it's not supported yet?

Last edited by Rukiri (2012-06-22 00:29:42)

dejavu

Member

Registered: 2008-05-26

Posts: 103

Re: Gnome-Shell: Oh no somthing has gone wrong

Just curious: Why aren't you trying my suggestion?

Last edited by dejavu (2012-06-22 01:09:49)

wonder

Developer

From: Bucharest, Romania

Registered: 2006-07-05

Posts: 5,941

Website

Re: Gnome-Shell: Oh no somthing has gone wrong

do you have multiple monitors? i know there is a bug in nvidia driver with gnome-shell and multiple monitors.

---

Give what you have. To someone, it may be better than you dare to think.

Rukiri

Member

Registered: 2011-11-08

Posts: 45

Re: Gnome-Shell: Oh no somthing has gone wrong

Yes 3, but only 1 is conneted.

Gnome fallback works fine, gnome3 works perfectly in ubuntu, fedora, haven't tried gentoo but I think the experience would be the same and don't want to wait 3 hrs to find out or not.

I think it's the video driver that's the issue or it's the package as gnome 3.4 works perfectly in the distros I just mentioned.

wonder

Developer

From: Bucharest, Romania

Registered: 2006-07-05

Posts: 5,941

Website

Re: Gnome-Shell: Oh no somthing has gone wrong

Yes 3, but only 1 is conneted.

Gnome fallback works fine, gnome3 works perfectly in ubuntu, fedora, haven't tried gentoo but I think the experience would be the same and don't want to wait 3 hrs to find out or not.

I think it's the video driver that's the issue or it's the package as gnome 3.4 works perfectly in the distros I just mentioned.

i think is this bug: http://www.nvnews.net/vbulletin/showthread.php?t=184455
try to downgrade to 295.59

---

Give what you have. To someone, it may be better than you dare to think.

Rukiri

Member

Registered: 2011-11-08

Posts: 45

Re: Gnome-Shell: Oh no somthing has gone wrong

The guys issue is close to mine, however gnome 3 doesn't fall back to fallback mode I just get an uh oh unless I remove gnome-shell.

Though is the nvidia packages in arch version 3 and not 2?  I know arch loves to be bleeding edge and is the KISS philosphy?

I'm more or less going to start fresh with an LVM, currently in windows as I've heard I need to install photoshop cs5 or 6 onto windows first than move them over to my wines program files folder.

So if Nvidia drivers Version 3.XX don't support or don't seem to support 3D acceleration ugh I'm confused and frustraited...

I prefer using Linux that's why I want to switch over, but I need the latest drivers as autodesk maya, 3dsmax and mudbox won't run otherwise(just something I've read not experienced).

Here's what I use,
3DSmax
Maya
Mudbox
Zbrush
Adobe Photoshop

There's also a few games I play as well.
Assassins Creed(currently playing 3)
Crysis2
Left 4 Dead 2
Team Fortress 2
StartCraft 2
World of Warcraft(I think this has an official linux port..)

And various racers and fighting games on Steam.

So you're saying version 2.95.59 is the version I should be using?

dejavu

Member

Registered: 2008-05-26

Posts: 103

Re: Gnome-Shell: Oh no somthing has gone wrong

Now the same problem happened to me again. If I am doing the steps which I have described in my first post in this thread then everything is working fine again.

.xsession-errors:

/etc/gdm/Xsession: Beginning session setup...
localuser:paul being added to access control list
/etc/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- gnome-session
GNOME_KEYRING_CONTROL=/home/paul/.cache/keyring-iHuttf
SSH_AUTH_SOCK=/home/paul/.cache/keyring-iHuttf/ssh
GNOME_KEYRING_CONTROL=/home/paul/.cache/keyring-iHuttf
SSH_AUTH_SOCK=/home/paul/.cache/keyring-iHuttf/ssh
GPG_AGENT_INFO=/home/paul/.cache/keyring-iHuttf/gpg:0:1
GNOME_KEYRING_CONTROL=/home/paul/.cache/keyring-iHuttf
SSH_AUTH_SOCK=/home/paul/.cache/keyring-iHuttf/ssh
GPG_AGENT_INFO=/home/paul/.cache/keyring-iHuttf/gpg:0:1
GNOME_KEYRING_CONTROL=/home/paul/.cache/keyring-iHuttf
SSH_AUTH_SOCK=/home/paul/.cache/keyring-iHuttf/ssh
GPG_AGENT_INFO=/home/paul/.cache/keyring-iHuttf/gpg:0:1

(gnome-settings-daemon:1147): color-plugin-WARNING **: failed to get edid: unable to get EDID for output

(gnome-settings-daemon:1147): color-plugin-WARNING **: unable to get EDID for xrandr-LVDS: unable to get EDID for output
Initializing tracker-store...
Tracker-Message: Setting up monitor for changes to config file:'/home/paul/.config/tracker/tracker-store.cfg'
Tracker-Message: Setting up monitor for changes to config file:'/home/paul/.config/tracker/tracker-store.cfg'
Starting log:
  File:'/home/paul/.local/share/tracker/tracker-store.log'
Initializing tracker-miner-fs...
Tracker-Message: Setting up monitor for changes to config file:'/home/paul/.config/tracker/tracker-miner-fs.cfg'
Starting log:
  File:'/home/paul/.local/share/tracker/tracker-miner-fs.log'
Failed to play sound: File or data not found

** (-c:1234): WARNING **: AT-SPI: Error in GetItems, sender=org.freedesktop.DBus, error=The name :1.9 was not provided by any .service files
** Message: applet now removed from the notification area

** (-c:1234): WARNING **: AT-SPI: Error in GetItems, sender=org.freedesktop.DBus, error=The name :1.4 was not provided by any .service files
gnome-session[1119]: WARNING: Application 'gnome-shell.desktop' killed by signal 11

** (-c:1234): WARNING **: AT-SPI: Error in GetItems, sender=org.freedesktop.DBus, error=The name :1.12 was not provided by any .service files
gnome-session[1119]: WARNING: Application 'gnome-shell.desktop' killed by signal 11
gnome-session[1119]: WARNING: App 'gnome-shell.desktop' respawning too quickly

dmesg:

[   80.409951] gnome-shell[1193]: segfault at 31 ip 0000000000000031 sp 00007fffc2146de8 error 14 in gnome-shell[400000+3000]
[   81.871519] gnome-shell[1304]: segfault at 31 ip 0000000000000031 sp 00007ffff1fb54d8 error 14 in gnome-shell[400000+3000]

I think the problem started when I have added a second monitor. I am using the catalyst driver with a hd3450 graphics adapter. As far as I can remember the problem appeared also with the open source driver.

Rukiri

Member

Registered: 2011-11-08

Posts: 45

Re: Gnome-Shell: Oh no somthing has gone wrong

It was a Nvidia issue, I didn't solve the issue as I had to be somewhere for a few days.  Nvidia has decent linux support, AMD not so much..  I think it's an nvidia issue anyway, I did try your suggestion dejavu but it didn't solve my issue which lead me to believe it's an nvidia issue.

I tried both the open source and closed source Nvidia drivers and the same result, I'm sticking with closed source drivers as they're directly from the manufacture and they're known to support linux.

I'm going to try Wonder's suggestion and install the drivers manually or downgrade the package.

Rukiri

Member

Registered: 2011-11-08

Posts: 45

Re: Gnome-Shell: Oh no somthing has gone wrong

Ok guys it was indefinetly a driver issue and is now solved, it was either the nvidia driver or the kernel but at any rate it's now fixed.
And oh, Nvidia picked up all 3 monitors!

dejavu

Member

Registered: 2008-05-26

Posts: 103

Re: Gnome-Shell: Oh no somthing has gone wrong

Oh my god!
I have finally found what my problem caused.
It was the virtual "Screen Keyboard".
If I have enabled it, logged out and logged in again then the problem occured.

I can reproduce it independent of the graphics driver!
Probably someone can try it, so I can fill a bug!

So solution for me was:
- Installing e.g.: openbox
- Installing dconf-editor
- Log in at openbox
- Run dconf-editor
- Reset following key: /org/gnome/desktop/a11y/applications/screen-keyboard-enabled

iam

Member

Registered: 2012-08-26

Posts: 1

Re: Gnome-Shell: Oh no somthing has gone wrong

exactly the same thing happens to me in Ubuntu 12.04 precise...confirmed. reinstalling at-spi did nothing.

dconf reset -f "/org/gnome/desktop/a11y/"

and manually climbing up the tree in dconf-editor helped me narrow it down to the same conclusive key, you can even with a terminal .... so is onboard the problem? is another somehow related dconf key? lock-screen / screensaving related...?

where to bug? onboard? at-spi2?!?