'Oh no! Something has gone wrong.', but nothing went wrong really...

English Install/Boot/Login
1

When I login I see an ‘Oh no! Something has gone wrong.’ message for a very short moment and then successfully get the GNOME desktop.
I have an intel and an nvidia graphics card with an optimus switch (I read this might be related) and I succesfully installed bumblebee and nvidia-bumblebee (etc.) and I can run optirun glxspheres.
My journalctl -b:

Dec 22 10:43:04 opensuse org.a11y.Bus[1927]: Activating service name='org.a11y.atspi.Registry'
Dec 22 10:43:04 opensuse org.a11y.Bus[1927]: Successfully activated service 'org.a11y.atspi.Registry'
Dec 22 10:43:04 opensuse org.a11y.atspi.Registry[1943]: SpiRegistry daemon is running with well-known name - org.a11y.atspi.Registry
Dec 22 10:43:04 opensuse org.a11y.atspi.Registry[1943]: Xlib:  extension "XEVIE" missing on display ":0".
Dec 22 10:43:04 opensuse gnome-session[1888]: gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
Dec 22 10:43:04 opensuse gnome-session[1888]: gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
Dec 22 10:43:04 opensuse gnome-session[1888]: gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
Dec 22 10:43:04 opensuse gnome-session[1888]: gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
Dec 22 10:43:04 opensuse gnome-keyring-daemon[1734]: couldn't allocate secure memory to keep passwords and or keys from being written to the disk
Dec 22 10:43:04 opensuse gnome-session[1888]: GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1
Dec 22 10:43:04 opensuse gnome-session[1888]: GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1
Dec 22 10:43:04 opensuse gnome-session[1888]: GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1
Dec 22 10:43:04 opensuse gnome-session[1888]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Dec 22 10:43:04 opensuse gnome-session[1888]: GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1
Dec 22 10:43:04 opensuse gnome-session[1888]: SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
Dec 22 10:43:06 opensuse gnome-session[1888]: Gjs-Message: JS LOG: Failed to launch ibus-daemon: Failed to execute child process "ibus-daemon" (No such file or directory)
Dec 22 10:43:06 opensuse org.gnome.OnlineAccounts[1927]: goa-daemon-Message: goa-daemon version 3.16.4.1 starting
Dec 22 10:43:06 opensuse org.gtk.Private.AfcVolumeMonitor[1927]: Volume monitor alive
Dec 22 10:43:06 opensuse gnome-session[1888]: (uint32 1,)
Dec 22 10:43:06 opensuse gnome-session[1888]: Failed to play sound: File or data not found
Dec 22 10:43:06 opensuse gnome-session[1888]: Window manager warning: "XF86Help" is not a valid accelerator
Dec 22 10:43:11 opensuse org.gnome.ControlCenter.SearchProvider[1927]: ** (process:2291): WARNING **: Ignoring broken panel ca.desrt.dconf-editor (missing desktop file)
Dec 22 10:43:11 opensuse org.gnome.ControlCenter.SearchProvider[1927]: ** (process:2291): WARNING **: Ignoring broken panel gpk-prefs (missing desktop file)
Dec 22 10:43:11 opensuse org.gnome.ControlCenter.SearchProvider[1927]: ** (process:2291): WARNING **: Ignoring broken panel tracker-preferences (missing desktop file)
Dec 22 10:43:11 opensuse org.gnome.ControlCenter.SearchProvider[1927]: ** (process:2291): WARNING **: Ignoring broken panel itweb-settings (missing desktop file)
Dec 22 10:43:11 opensuse org.gnome.ControlCenter.SearchProvider[1927]: ** (process:2291): WARNING **: Ignoring broken panel gnome-tweak-tool (missing desktop file)
Dec 22 10:43:11 opensuse org.gnome.ControlCenter.SearchProvider[1927]: ** (process:2291): WARNING **: Ignoring broken panel YaST (missing desktop file)
Dec 22 10:43:11 opensuse obexd[2338]: OBEX daemon 5.35
Dec 22 10:43:11 opensuse org.gnome.Documents[1927]: Gjs-Message: JS LOG: Can't find a valid getting started PDF document

The ‘Failed to play sound: File or data not found’ has to do with missing sounds from sound-theme-freedesktop (there is no system-ready, desktop-login, …)
How can I get rid of this alert at login?

2

Seems harmless, possibly linked to the time it takes to load the Nvidia driver or something. I saw the same with nvidia-bumblebee, but that disappeared with auto-login enabled.
Otherwise everything works as charms and had no other side effect in almost two months…

3

Yeah, I think it is indeed harmless. But are there ways to repress the message? I don’t like auto login because it leaves my computer kinda unprotected.

4

Don’t know, really, but if it is linked to the display manager you might try lightdm or xdm to replace gdm.

5

On Tue, 22 Dec 2015 17:36:01 +0000, hermanbergwerf wrote:

> Yeah, I think it is indeed harmless. But are there ways to repress the
> message? I don’t like auto login because it leaves my computer kinda
> unprotected.

When GNOME throws this error, it usually is a faulty extension. Try
disabling any extensions you have enabled, then log in. If it works OK,
then enable them one by one until you find the one that’s causing the
error.

Jim

–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C

6

For now I have no shell extensions installed (if thats what you mean).
It could be related to nvidia/bumblebee. I just find the flashing alert a little annoying.
Does switching gdm have other implication. I would think gdm is the best dm if you are using GNOME (else why would folks have built gdm)

7

It is not the best it is just one of many and gnome uses gdm because gnome need a DM like KDE needs a DM but they are more or less interchangeable

if you installed the NVIDIA driver and did not remove it before installing nvida-bumblebee It may have made changes that is causing the problem

8

No, not related to gnome shell extensions (none installed here too).
No, not related to upstream Nvidia (never fiddled with that here, only “reviewed” SDB style nvidia-bumblebee).

And the “Oh No!” thing shows here too for a fraction of a second just before the desktop (default) wallpaper shows up.