Results 1 to 3 of 3

Thread: Gnome kicks me back to login page few seconds after logon

  1. #1

    Default Gnome kicks me back to login page few seconds after logon

    Hi,
    After booting the PC up, the login screen appears. When I try to log in, it succeeds and gnome session appears. After a while (about 1-5 seconds) the screen goes dark and I am suddenly back at the login page. This happens no matter I do anything or do nothing at all in the opened session. The Gnome session crashes.

    A day before the first occurence, I did an update of libxcb and libxcb-* packages (about 34 packages in total). I downgraded these packages back to their original version but that did not help.

    For the brand new user, the Gnome session runs fine. (The new user has only default settings, my own user account has few gnome plugins active but those were running fine before.)
    Maybe something in ~/.cache?

    Xorg log looks ok, there are some errors about not finding "nvidia" module but this is fine, I run nouveau modules.
    Here is what i managed to get out of other logs.

    ~/.xsession-errors-:0

    Gjs-Message: JS LOG: Failed to add search provider /usr/share/gnome-shell/search-providers/org.gnome.bijiben-search-provider.ini: TypeError: appInfo is null
    ** (gnome-settings-daemon:3190): WARNING **: Schemas 'org.gnome.desktop.a11y' has not been setup
    Gjs-Message: JS LOG: pidgin-im-gs: Gio.DBusError: GDBus.Errorrg.freedesktop.DBus.Error.ServiceUnknown: The name im.pidgin.purple.PurpleService was not provided by any .service files

    ... there are just some tracker-extract warnings ...

    libva info: VA-API version 0.39.0
    libva info: va_getDriverName() returns -1
    libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)
    libva info: VA-API version 0.39.0
    libva info: va_getDriverName() returns -1
    libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)
    libva info: VA-API version 0.39.0
    libva info: va_getDriverName() returns 0
    libva info: Trying to open /usr/lib64/dri/gallium_drv_video.so
    libva info: va_openDriver() returns -1
    libva info: VA-API version 0.39.0
    XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
    after 11 requests (11 known processed) with 0 events remaining.
    (gnome-software:3217): Gdk-WARNING **: gnome-software: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
    (evolution-alarm-notify:3205): Gdk-WARNING **: evolution-alarm-notify: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
    (gnome-settings-daemon:3190): Gdk-WARNING **: gnome-settings-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
    (gnome-shell:3081): Gdk-WARNING **: gnome-shell: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
    gnome-session-binary[2971]: WARNING: App 'gnome-settings-daemon.desktop' exited with code 1
    gnome-session-binary[2971]: WARNING: App 'org.gnome.Shell.desktop' exited with code 1
    (deja-dup-monitor:3223): GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
    (deja-dup-monitor:3223): GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor org.gtk.vfs.MTPVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
    (deja-dup-monitor:3223): GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor org.gtk.vfs.AfcVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
    (deja-dup-monitor:3223): GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
    (deja-dup-monitor:3223): GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor org.gtk.vfs.GoaVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
    (tracker-miner-fs:3218): GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor org.gtk.vfs.UDisks2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
    (tracker-miner-fs:3218): GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor org.gtk.vfs.MTPVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
    (tracker-miner-fs:3218): GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor org.gtk.vfs.AfcVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
    (tracker-miner-fs:3218): GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor org.gtk.vfs.GPhoto2VolumeMonitor disconnected from the bus; removing drives/volumes/mounts
    (tracker-miner-fs:3218): GVFS-RemoteVolumeMonitor-WARNING **: Owner of volume monitor org.gtk.vfs.GoaVolumeMonitor disconnected from the bus; removing drives/volumes/mounts
    (tracker-miner-fs:3218): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
    (tracker-miner-fs:3218): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
    (tracker-miner-fs:3218): GLib-GIO-CRITICAL **: Error while sending AddMatch() message: The connection is closed
    gnome-session-binary[2971]: WARNING: Lost name on bus: org.gnome.SessionManager
    Unable to init server: Could not connect: Connection refused
    ** (gnome-session-failed:3373): WARNING **: Cannot open display:
    (gnome-shell:3365): Clutter-CRITICAL **: Unable to initialize Clutter: Unable to open display ':0'
    (gnome-shell:3365): mutter-WARNING **: Unable to initialize Clutter.
    ** (gnome-settings-daemon:3367): WARNING **: Unable to initialize GTK+
    0-greeter.log:
    gnome-session-is-accelerated: llvmpipe detected.
    ** (gnome-settings-daemon:5543): WARNING **: Schemas 'org.gnome.desktop.a11y' has not been setup
    I also managed to grab a coredump if it's of any use. It is without debug symbols, I encountered a problem installing them. :-/
    PID: 4818 (Xorg)
    UID: 0 (root)
    GID: 0 (root)
    Signal: 6 (ABRT)
    Timestamp: Sun 2018-01-14 18:03:23 CET (14min ago)
    Command Line: /usr/bin/Xorg :0 -background none -noreset -verbose -auth /run/gdm/auth-for-gdm-5y7hQw/database -seat seat0 vt7
    Executable: /usr/bin/Xorg
    Control Group: /system.slice/display-manager.service
    Unit: display-manager.service
    Slice: system.slice
    Boot ID: 0c52d57c16c2405a8a763cf684991bf9
    Machine ID: 89c660865c00403a9bacef32b6828556
    Hostname: mothership
    Coredump: /var/lib/systemd/coredump/core.Xorg.0.0c52d57c16c2405a8a763cf684991bf9.4818.1515949403000000.xz
    Message: Process 4818 (Xorg) of user 0 dumped core.


    GNU gdb (GDB; openSUSE Leap 42.2) 8.0.1
    ... blah blah GDB MOTD here ...
    Reading symbols from /usr/bin/Xorg...(no debugging symbols found)...done.
    [New LWP 4818]
    [New LWP 4824]
    [New LWP 4825]
    [New LWP 4823]
    [New LWP 4826]
    [Thread debugging using libthread_db enabled]
    Using host libthread_db library "/lib64/libthread_db.so.1".
    Core was generated by `/usr/bin/Xorg :0 -background none -noreset -verbose -auth /run/gdm/auth-for-gdm'.
    Program terminated with signal SIGABRT, Aborted.
    #0 0x00007fe4883a98d7 in raise () from /lib64/libc.so.6
    [Current thread is 1 (Thread 0x7fe48a851a00 (LWP 4818))]
    Missing separate debuginfos, use: zypper install xorg-x11-server-debuginfo-7.6_1.18.3-12.26.1.x86_64
    (gdb) bt
    #0 0x00007fe4883a98d7 in raise () from /lib64/libc.so.6
    #1 0x00007fe4883aacaa in abort () from /lib64/libc.so.6
    #2 0x00007fe4883a2866 in __assert_fail_base () from /lib64/libc.so.6
    #3 0x00007fe4883a2912 in __assert_fail () from /lib64/libc.so.6
    #4 0x0000000000426f03 in ?? ()
    #5 0x000000000055c912 in DRI2Authenticate ()
    #6 0x000000000055d607 in ?? ()
    #7 0x000000000043948e in ?? ()
    #8 0x000000000043d1cb in ?? ()
    #9 0x00007fe4883956e5 in __libc_start_main () from /lib64/libc.so.6
    #10 0x0000000000428719 in _start ()
    (gdb) quit
    Thanks for the help.

  2. #2

    Default Re: Gnome kicks me back to login page few seconds after logon

    Ok, found the problem - too new Nvidia graphics card (as per many unlucky Arch users trying to solve something similar). So far it was working but with some update the new version of nouveau drivers came in.
    Lead to the core problem was following errors in the ~/.xsesssion-errors log.
    Code:
    libva info: VA-API version 0.39.0
    libva info: va_getDriverName() returns -1
    libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)
    libva info: VA-API version 0.39.0
    libva info: va_getDriverName() returns -1
    libva error: va_getDriverName() failed with unknown libva error,driver_name=(null)
    libva info: VA-API version 0.39.0
    libva info: va_getDriverName() returns 0
    libva info: Trying to open /usr/lib64/dri/gallium_drv_video.so
    libva info: va_openDriver() returns -1
    libva info: VA-API version 0.39.0
    XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
          after 11 requests (11 known processed) with 0 events remaining.
    Running vdpauinfo gave me that it cannot load vdpau_nvidia.so driver. After specifying VDPAU_DRIVER=va_gl the vdpauinfo stopped protesting and gave the output.

    So I stopped using nouveau drivers and moved to the Nvidia ones as described here: https://en.opensuse.org/SDB:NVIDIA_drivers .

    Everything works like a charm now.
    Last edited by Fiisch; 23-Feb-2018 at 13:08. Reason: rewording, added info

  3. #3
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    23,703
    Blog Entries
    1

    Default Re: Gnome kicks me back to login page few seconds after logon

    Well done with resolving and thanks for sharing this.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •