I have a working openSUSE 12.3, 3.7.10-1.11-desktop x86_64 with Gnome 3.6.3.1. I have also tried a Gnome 3.8 upgrade for the 12.3 kernel and got it to work (nouveau, intel xeon, Nvidia).
So I tried to upgrade a parallell root installation on the same hardware (dual boot, common /home) to Tumbleweed 3.9.4-11.g51bf0ff-desktop with Gnome 3.8.2, and got a broken GDM login with the message:
“Oh no! Something has gone wrong. A problem has occurred and the system can’t
recover. All extensions have disabled as a precaution. [Logout]”
Now I have also tried openSUSE 13.1 Milestone 1 and Milestone 2, 3.9.0-1-desktop x86_64 and Gnome 3.8.x, and get the same broken GDM login problem.
Has anybody success with 13.1 Milestone 1 and 2 Gnome login?
What can possibly be done to fix this login, there is no longer fallback mode? (KDE works ok)
Gnome 3.8.1 (on Milestone 1) and 3.8.2 (on Milestone 2) both seem to be working here.
I am using KDM, rather than GDM.
I did try GDM with Milestone 1, and Gnome worked with that. However, icewm gave problems when started from GDM. I’ll try switching to GDM on M2 later today, though I mostly want to see if icewm is still broken when started from GDM. (I don’t like GDM). Incidentally, I see the same GDM/icewm breakage with 12.3 Tumbleweed/Gnome 3.8.2.
I also have an older 32-bit system with radeon graphics. Earlier versions of Gnome have either failed with the “something has gone wrong” message, or have dropped to fallback. I tried Gnome 3.8.1 (from Milestone 1), and it actually worked. However, it was unusably slow. Presumably the fancy graphics is all being done with software emulation, and that system doesn’t have the horsepower. Being a glutton for punishment, I tried switching to GDM. It took a long time for the login screen to come up, but it eventually did. However, login to Gnome from GDM failed. It looked as if GDM was looping.
My suggestion: try KDM or lightdm. Perhaps your problem is with GDM.
I don’t think my Gnome session login problem is caused by GDM, because login to a KDE session from GDM has worked ok.
Now I have also tried KDM. Login to KDE works, login to Gnome breaks as before.
The common denominator I’ve noticed, is that after upgrade to newer kernels than 3.7.x (3.8.x, 3.9.x and 3.10), the Gnome 3.8 login has been broken!?
As I said initially, also Gnome 3.8 worked on openSUSE 12.3 with kernel 3.7.x.
Isn’t there any Gnome log files that tells what’s going wrong?
My successful login is leaving some messages in “$HOME/.xsession-errors-:0”
Yes, there looks to be something?
~.xsession-errors-:0
/etc/X11/xim: Checking whether an input method should be started.
sourcing /etc/sysconfig/language to get the value of INPUT_METHOD
INPUT_METHOD is not set or empty (no user selected input method).
Trying to start a default input method for the locale nb_NO.UTF-8 ...
There is no default input method for the current locale.
Dummy input method "none" (do not use any fancy input method by default)
gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
GNOME_KEYRING_CONTROL=/run/user/1000/keyring-3mT0k2
SSH_AUTH_SOCK=/run/user/1000/keyring-3mT0k2/ssh
GNOME_KEYRING_PID=1143
gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
GNOME_KEYRING_CONTROL=/run/user/1000/keyring-3mT0k2
SSH_AUTH_SOCK=/run/user/1000/keyring-3mT0k2/ssh
GPG_AGENT_INFO=/run/user/1000/keyring-3mT0k2/gpg:0:1
GNOME_KEYRING_CONTROL=/run/user/1000/keyring-3mT0k2
SSH_AUTH_SOCK=/run/user/1000/keyring-3mT0k2/ssh
GPG_AGENT_INFO=/run/user/1000/keyring-3mT0k2/gpg:0:1
GNOME_KEYRING_CONTROL=/run/user/1000/keyring-3mT0k2
SSH_AUTH_SOCK=/run/user/1000/keyring-3mT0k2/ssh
GPG_AGENT_INFO=/run/user/1000/keyring-3mT0k2/gpg:0:1
(gnome-settings-daemon:1137): mouse-plugin-WARNING **: Error setting normal scroll for "SynPS/2 Synaptics TouchPad"
JS LOG: IBus version is too old
**
Bluetooth:ERROR:rfkill-glib.c:83:type_to_string: code should not be reached
gnome-session[1017]: WARNING: Application 'gnome-shell.desktop' killed by signal 6
JS LOG: IBus version is too old
**
Bluetooth:ERROR:rfkill-glib.c:83:type_to_string: code should not be reached
gnome-session[1017]: WARNING: Application 'gnome-shell.desktop' killed by signal 6
gnome-session[1017]: WARNING: App 'gnome-shell.desktop' respawning too quickly
(zeitgeist-datahub:1333): GLib-GObject-WARNING **: invalid (NULL) pointer instance
(zeitgeist-datahub:1333): GLib-GObject-CRITICAL **: g_signal_connect_data: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
Failed to play sound: File or data not found
(gnome-settings-daemon:1137): GLib-CRITICAL **: g_variant_builder_end: assertion `!GVSB(builder)->uniform_item_types || GVSB(builder)->prev_item_type != NULL || g_variant_type_is_definite (GVSB(builder)->type)' failed
(gnome-settings-daemon:1137): GLib-CRITICAL **: g_variant_get_type: assertion `value != NULL' failed
(gnome-settings-daemon:1137): GLib-CRITICAL **: g_variant_type_is_subtype_of: assertion `g_variant_type_check (type)' failed
(gnome-settings-daemon:1137): GLib-CRITICAL **: g_variant_get_type_string: assertion `value != NULL' failed
(gnome-settings-daemon:1137): GLib-ERROR **: g_variant_new: expected GVariant of type `a(su)' but received value has type `(null)'
gnome-session[1017]: WARNING: Application 'gnome-settings-daemon.desktop' killed by signal 5
** Message: applet now removed from the notification area
/usr/share/system-config-printer/applet.py:439: PyGIDeprecationWarning: MainLoop is deprecated; use GLib.MainLoop instead
loop = GObject.MainLoop ()
(gnome-settings-daemon:1373): mouse-plugin-WARNING **: Error setting normal scroll for "SynPS/2 Synaptics TouchPad"
(gnome-settings-daemon:1373): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed
(gnome-settings-daemon:1373): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed
(gnome-settings-daemon:1373): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed
(gnome-settings-daemon:1373): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed
(gnome-settings-daemon:1373): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed
(gnome-settings-daemon:1373): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed
(gnome-settings-daemon:1373): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed
(gnome-settings-daemon:1373): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed
(gnome-settings-daemon:1373): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed
(gnome-settings-daemon:1373): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed
(gnome-settings-daemon:1373): wacom-plugin-CRITICAL **: gsd_wacom_device_get_device_type: assertion `GSD_IS_WACOM_DEVICE (device)' failed
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
after 11 requests (11 known processed) with 0 events remaining.
(evolution-alarm-notify:1318): Gdk-WARNING **: evolution-alarm-notify: Fatal IO error 11 (Ressursen midlertidig utilgjengelig) on X server :0.
** (zeitgeist-datahub:1333): WARNING **: zeitgeist-datahub.vala:226: Unable to get name "org.gnome.zeitgeist.datahub" on the bus!
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.
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->'Terminert'
(nm-applet:1328): Gdk-WARNING **: nm-applet: Fatal IO error 11 (Ressursen midlertidig utilgjengelig) on X server :0.
(gnome-settings-daemon:1373): GLib-GIO-WARNING **: Error releasing name org.gnome.SettingsDaemon.Orientation: Tilkoblingen er lukket
(gnome-settings-daemon:1373): Gdk-WARNING **: gnome-settings-daemon: Fatal IO error 3 (Ingen slik prosess) on X server :0.
(tracker-miner-fs:1334): GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor org.gtk.Private.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
(tracker-miner-fs:1334): GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor org.gtk.Private.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
(tracker-miner-fs:1334): GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor org.gtk.Private.AfcVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
(tracker-miner-fs:1334): GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor org.gtk.Private.GoaVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
(tracker-miner-fs:1334): GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor org.gtk.Private.MTPVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
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->'Terminert'
(tracker-miner-fs:1334): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: Tilkoblingen er lukket
(tracker-miner-fs:1334): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: Tilkoblingen er lukket
(tracker-miner-fs:1334): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: Tilkoblingen er lukket
OK
And more detailed system information with inxi
inxi -Fz
System: Host: linux-sg1m.site Kernel: 3.10.0-rc4-1-desktop x86_64 (64 bit)
Desktop: KDE 4.10.4 Distro: openSUSE 13.1 Milestone 2 (Bottle)
Machine: System: Hewlett-Packard (portable) product: HP Compaq 8710w version: F.0F
Mobo: Hewlett-Packard model: 30C3 version: KBC Version 73.31
Bios: Hewlett-Packard version: 68MAD Ver. F.0F date: 11/25/2008
CPU: Dual core Intel Core2 Duo CPU T9500 (-MCP-) cache: 6144 KB flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx)
Clock Speeds: 1: 800.00 MHz 2: 800.00 MHz
Graphics: Card: NVIDIA G92M [Quadro FX 3600M]
X.Org: 1.14.1 drivers: nouveau (unloaded: fbdev,nv,vesa) Resolution: 1920x1200@60.0hz
GLX Renderer: Gallium 0.4 on NV92 GLX Version: 3.0 Mesa 9.1.3
Audio: Card: Intel 82801H (ICH8 Family) HD Audio Controller driver: snd_hda_intel Sound: ALSA ver: k3.10.0-rc4-1-desktop
Network: Card-1: Intel PRO/Wireless 4965 AG or AGN [Kedron] Network Connection driver: iwl4965
IF: wlp16s0 state: down mac: <filter>
Card-2: Intel 82566MM Gigabit Network Connection driver: e1000e
IF: enp0s25 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives: HDD Total Size: 160.0GB (38.1% used) 1: id: /dev/sda model: INTEL_SSDSA2CW16 size: 160.0GB
Partition: ID: / size: 20G used: 6.0G (32%) fs: ext4 ID: swap-1 size: 2.15GB used: 0.00GB (0%) fs: swap
RAID: No RAID devices detected - /proc/mdstat and md_mod kernel raid module present
Sensors: None detected - is lm-sensors installed and configured?
Info: Processes: 171 Uptime: 0:06 Memory: 844.0/3897.9MB Client: Shell (bash) inxi: 1.8.47
A few more thoughts.
On my older, slower box, when I first tried Gnome (with milestone 1/2), I got the “something has gone wrong” message.
I then deleted most of the setting files from home directory (most files with name that begins ‘.’). After that, a login worked.
It seems that if there is something in your settings that says to use fallback, then Gnome will fail.
See also Bug 817612
My hp8710p is still fairly fast (2.6GHz dual core cpu, Nvidia Quadro FX 3600M, 4 GB RAM and upgraded with SSD) and has driven Gnome 3.x up to 3.6 very well. While I had a temporary Gnome login issue when I first installed the 12.3 Nvidia proprietary driver, nouveau has been a safe default installation all the time.
And to be sure that not my dual boot with 12.3 and 13.1 was affected by the common /home, I have also installed 13.1 Milestone 1 and 2 without mounting the old /home but use a clean /home on its root file system instead. Else it is a quite default and automatic Gnome desktop installation, where I added the KDE pattern with zypper afterwards, after the Gnome login issue arised.
Now I will try to install 13.1 M2 also on my AM3 based machine, which runs dual boot 12.3 and Tumbleweed, both with Gnome 3.8.2 and kernel 3.7.10.
.
Yeap, 13.1 Milestone 2 Gnome login works ok on my AMD based workstation:
CPU: Triple core AMD Athlon II X3 445 (-MCP-) cache: 1536 KB flags: (lm nx sse sse2 sse3 sse4a svm)
Clock Speeds: 1: 800.00 MHz 2: 3100.00 MHz 3: 800.00 MHz
Graphics: Card: Advanced Micro Devices [AMD] nee ATI RS880 [Radeon HD 4290]
X.Org: 1.14.1 drivers: ati,radeon (unloaded: fbdev,vesa) Resolution: 1920x1080@60.0hz
GLX Renderer: Gallium 0.4 on AMD RS880 GLX Version: 3.0 Mesa 9.1.3
terje@linux-621f:~> cat /etc/*release
NAME=openSUSE
VERSION="13.1 Milestone 2 (Bottle)"
VERSION_ID="13.1milestone2"
PRETTY_NAME="openSUSE 13.1 Milestone 2 (Bottle) (x86_64)"
ID=opensuse
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:opensuse:13.1"
openSUSE 13.1 Milestone 2 (x86_64)
VERSION = 13.1
CODENAME = Bottle
terje@linux-621f:~> uname -r
3.10.0-rc4-1-desktop
terje@linux-621f:~>
terje@linux-621f:~> gnome-shell --version
GNOME Shell 3.9.1
This was a fresh new 13.1 Milestone 2 NET installation from scratch using DVD and selecting Gnome desktop.
I’ll now try the same on my hp8710p Intel/Nvidia based machine, which was installed from Milestone 1 NET and next upgraded with ‘zypper dup’ to Milestone 2.
The corresponding installation on my hp8710p Intel/Nvidia based machine using Milestone 2 NET iso on DVD didn’t succeed at all.
The first installation restart caused a machine freeze and the system didn’t startup automatically as it should. I think this happened also with the previous Milestone 1 installation, but that time I thought this was due to some screen or power save .
After power off and on the final installation setup continued. But next the system stopped again (the last console message visible was ‘Started Cups printing’) without displaying the GDM login screen… Ctrl-Alt-F1 and login to console mode was possible, and I verified the system was in run-level 5. Even after ‘zypper dup’ and a few package installed, gui login didn’t succeed.
Now I try to download the Gnome Live iso to see if it works better.
No, still the same Gnome login error. Both when I tried to login using the Live DVD, and after I had installed Milestone 2 from this Live DVD.
Same issue in current release candidate.
ryanbach wrote:
>
> Same issue in current release candidate.
>
>
Regarding your thread heading. Isn’t 13.1 going for GNOME 3.10. Why do
you have 3.8 on your machine?
–
GNOME 3.6.2
openSUSE Release 12.3 (Dartmouth) 64-bit
Kernel Linux 3.7.10-1.16-desktop
same problem on my 13.1 final release 64bit Gnome with all latest updates installed… this started 1 week ago… i cant login with my user when i write my password it hangs…if i click cancel and click not listed button and write same user and password i can login… its very strange… any clue?