Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: Black screen for one user after upgrade from 13.2 -> 42.1 -> 42.2 (really stuck...)

  1. #1

    Default Black screen for one user after upgrade from 13.2 -> 42.1 -> 42.2 (really stuck...)

    Really stuck and would really appreciate some help, please


    I've upgraded from openSUSE 13.2 to leap 42.1 and then 42.2, I've read at length the article here:


    https://forums.opensuse.org/showthre...-and-libQt-5-9


    And many many others. I'm using what I believe to be stock repos:


    Code:
    zypper lr -d
    Repository priorities are without effect. All enabled repositories share the same priority.
    
    
    
    
    # | Alias               | Name                         | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                               | Service
    --+---------------------+------------------------------+---------+-----------+---------+----------+--------+-------------------------------------------------------------------+--------
    1 | repo-non-oss        | openSUSE-leap/42.2-Non-Oss   | Yes     | (r ) Yes  | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/leap/42.2/repo/non-oss/ |
    2 | repo-oss            | openSUSE-leap/42.2-Oss       | Yes     | (r ) Yes  | Yes     |   99     | yast2  | http://download.opensuse.org/distribution/leap/42.2/repo/oss/     |
    3 | repo-update         | openSUSE-42.2-Update         | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/leap/42.2/oss/                |
    4 | repo-update-non-oss | openSUSE-42.2-Update-Non-Oss | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/leap/42.2/non-oss/            |

    I can log in as root and the desktop is fine, I can log in as a new local user and the desktop is fine, but if I log in with my network credentials (I'm at work - home dir is auto-mounted and available as I can ssh in) then I only see the wallpaper, the mouse icon and nothing else (tried plasma 5, Gnome and Gnome Classic). If I use a VM with leap 42.2 installed and log in with my network credentials it works fine... There's something about my account on this particular machine. I have tried deleting all .* files in $HOME but that doesn't work either.


    I have access to IceWM and was able to replicate this:


    Code:
    sddm-greeter --test-mode
    [21:44:36.633] (WW) GREETER: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-ralph'
    [21:44:36.661] (II) GREETER: Reading from "/usr/share/xsessions/default.desktop"
    [21:44:36.661] (II) GREETER: Reading from "/usr/share/xsessions/gnome-classic.desktop"
    [21:44:36.662] (II) GREETER: Reading from "/usr/share/xsessions/gnome.desktop"
    [21:44:36.662] (II) GREETER: Reading from "/usr/share/xsessions/icewm-session.desktop"
    [21:44:36.662] (II) GREETER: Reading from "/usr/share/xsessions/icewm.desktop"
    [21:44:36.663] (II) GREETER: Reading from "/usr/share/xsessions/kde-plasma.desktop"
    [21:44:36.663] (II) GREETER: Reading from "/usr/share/xsessions/plasma5.desktop"
    [21:44:36.663] (II) GREETER: Reading from "/usr/share/xsessions/sle-classic.desktop"
    [21:44:36.663] (II) GREETER: Reading from "/usr/share/xsessions/xsession.desktop"
    [21:44:36.670] (EE) GREETER: Socket error:  "QLocalSocket::connectToServer: Invalid name"
    [21:44:36.731] (WW) GREETER: file:///Main.qml: No such file or directory
    Segmentation fault (core dumped)

    My machine appears to be up to date:


    Code:
    sudo zypper up
    Loading repository data...
    Reading installed packages...
    
    
    
    
    Nothing to do.

    Code:
    sudo zypper patch
    Loading repository data...
    Reading installed packages...
    Resolving package dependencies...
    
    
    
    
    Nothing to do.



    I'm not sure what else to try?

  2. #2

    Default Re: Black screen for one user after upgrade from 13.2 -> 42.1 -> 42.2 (really stuck...)

    Quote Originally Posted by ihube View Post
    I can log in as root and the desktop is fine, I can log in as a new local user and the desktop is fine, but if I log in with my network credentials (I'm at work - home dir is auto-mounted and available as I can ssh in) then I only see the wallpaper, the mouse icon and nothing else (tried plasma 5, Gnome and Gnome Classic). If I use a VM with leap 42.2 installed and log in with my network credentials it works fine... There's something about my account on this particular machine. I have tried deleting all .* files in $HOME but that doesn't work either.
    Maybe a permission problem?
    Qt's QML/QtQuick (used by SDDM and Plasma) uses OpenGL which in turn requires direct access to the graphics hardware.
    And also GNOME uses OpenGL.

    What does glxinfo (package Mesa-demo-x) say when run as this user?

    Try adding the user to the group "video".

  3. #3

    Default Re: Black screen for one user after upgrade from 13.2 -> 42.1 -> 42.2 (really stuck...)

    Can anyone throw me a bone? Something to investigate? Here is the output of .xsession-errors-machineName1:0:

    Code:
    Loading stage  "initial" 172
    startkde: Starting up...
    Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
    Initializing  "kcm_access" :  "kcminit_access"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/recentdocumentsnotifier.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/baloosearchmodule.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/statusnotifierwatcher.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/networkstatus.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/desktopnotifier.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/networkmanagement.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/ktimezoned.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/networkwatcher.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/appmenu.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/device_automounter.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/freespacenotifier.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/keyboard.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/bluedevil.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/soliduiserver.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/khotkeys.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/ksysguard.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/remotedirnotify.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/kscreen.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/proxyscout.so"
    kf5.kded: No X-KDE-DBus-ServiceName found in "/usr/lib64/qt5/plugins/kf5/kded/solidautoeject.so"
    Initializing  "kded_touchpad" :  "kcminit_touchpad"
    Initializing  "kcm_kgamma" :  "kcminit_kgamma"
    Initializing  "kcm_style" :  "kcminit_style"
    kf5.kded: found kded module "printmanager" by prepending 'kded_' to the library path, please fix your metadata.
    kf5.kcoreaddons.kaboutdata: Could not initialize the equivalent properties of Q*Application: no instance (yet) existing.
    detected kglobalaccel restarting, re-registering all shortcut keys
    I see much of the same when I successfully log in to another machine except the file contains much more output!

    Are there configuration files stored outside of my home directory that relate to my login on this particular machine? I found and removed /var/tmp/kdecache-userName, is there more?

    Here is a snippet from /var/log/Xorg.0.log that shows a single error:

    Code:
    [ 59309.814] (II) LoadModule: "fglrx"
    [ 59309.815] (WW) Warning, couldn't open module fglrx
    [ 59309.815] (II) UnloadModule: "fglrx"
    [ 59309.815] (II) Unloading fglrx
    [ 59309.815] (EE) Failed to load module "fglrx" (module does not exist, 0)
    [ 59309.815] (II) LoadModule: "ati"
    [ 59309.815] (II) Loading /usr/lib64/xorg/modules/drivers/ati_drv.so
    [ 59309.815] (II) Module ati: vendor="X.Org Foundation"
    [ 59309.815]    compiled for 1.18.3, module version = 7.7.1
    [ 59309.815]    Module class: X.Org Video Driver
    [ 59309.815]    ABI class: X.Org Video Driver, version 20.0
    [ 59309.815] (II) LoadModule: "radeon"
    [ 59309.815] (II) Loading /usr/lib64/xorg/modules/drivers/radeon_drv.so
    [ 59309.815] (II) Module radeon: vendor="X.Org Foundation"
    [ 59309.815]    compiled for 1.18.3, module version = 7.7.1
    [ 59309.815]    Module class: X.Org Video Driver
    [ 59309.815]    ABI class: X.Org Video Driver, version 20.0
    I think this benign given as I can log in as another user on the same machine... Here's what I try removing form my home directory:

    Code:
     
    rm -rf .xsession-errors-machineName2:0 .xsession-errors-machineName1:0 .Xauthority .cache .config .xsession-errors .dmrc .kde4 .xdg_menu_cache .esd_auth .gtkrc-2.0 .dbus .local
    Thanks for reading this far. Still really stuck!

  4. #4

    Default Re: Black screen for one user after upgrade from 13.2 -> 42.1 -> 42.2 (really stuck...)

    Quote Originally Posted by ihube View Post
    Can anyone throw me a bone? Something to investigate?
    Apparently you missed my previous reply...

    Are there configuration files stored outside of my home directory that relate to my login on this particular machine? I found and removed /var/tmp/kdecache-userName, is there more?
    Config files are stored in ~/.config/. What you deleted are temporary files/caches for KDE4, Plasma5/KF5 uses ~/.cache/ instead.

    Here is a snippet from /var/log/Xorg.0.log that shows a single error:
    That's no error.
    You don't have fglrx installed, so it cannot be loaded and the system uses radeon instead.

  5. #5

    Default Re: Black screen for one user after upgrade from 13.2 -> 42.1 -> 42.2 (really stuck...)

    Quote Originally Posted by wolfi323 View Post
    Maybe a permission problem?
    Qt's QML/QtQuick (used by SDDM and Plasma) uses OpenGL which in turn requires direct access to the graphics hardware.
    And also GNOME uses OpenGL.

    What does glxinfo (package Mesa-demo-x) say when run as this user?

    Try adding the user to the group "video".
    Thank you for responding, I think we were posting at the same time and I missed your response.

    I looked the video group using YasT and note that gdm was the only user, the local user and the network user were not members of this group. I've added both users to the video group.

    I then logged in with my broken user account using iceWM, here's the head of glxinfo:

    Code:
    name of display: :0
    display: :0  screen: 0
    direct rendering: Yes
    server glx vendor string: SGI
    server glx version string: 1.4
    server glx extensions:
        GLX_ARB_create_context, GLX_ARB_create_context_profile,
        GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float,
        GLX_ARB_framebuffer_sRGB, GLX_ARB_multisample,
        GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile,
        GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB,
        GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info,
        GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer,
        GLX_OML_swap_method, GLX_SGIS_multisample, GLX_SGIX_fbconfig,
        GLX_SGIX_pbuffer, GLX_SGIX_visual_select_group, GLX_SGI_swap_control
    client glx vendor string: Mesa Project and SGI
    client glx version string: 1.4
    client glx extensions:
        GLX_ARB_create_context, GLX_ARB_create_context_profile,
        GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float,
        GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample,
        GLX_EXT_buffer_age, GLX_EXT_create_context_es2_profile,
        GLX_EXT_create_context_es_profile, GLX_EXT_fbconfig_packed_float,
        GLX_EXT_framebuffer_sRGB, GLX_EXT_import_context,
        GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info, GLX_EXT_visual_rating,
        GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer,
        GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
        GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control,
        GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
        GLX_SGIX_visual_select_group, GLX_SGI_make_current_read,
        GLX_SGI_swap_control, GLX_SGI_video_sync
    GLX version: 1.4
    GLX extensions:
        GLX_ARB_create_context, GLX_ARB_create_context_profile,
        GLX_ARB_create_context_robustness, GLX_ARB_fbconfig_float,
        GLX_ARB_framebuffer_sRGB, GLX_ARB_get_proc_address, GLX_ARB_multisample,
        GLX_EXT_create_context_es2_profile, GLX_EXT_create_context_es_profile,
        GLX_EXT_fbconfig_packed_float, GLX_EXT_framebuffer_sRGB,
        GLX_EXT_import_context, GLX_EXT_texture_from_pixmap, GLX_EXT_visual_info,
        GLX_EXT_visual_rating, GLX_INTEL_swap_event, GLX_MESA_copy_sub_buffer,
        GLX_MESA_multithread_makecurrent, GLX_MESA_query_renderer,
        GLX_MESA_swap_control, GLX_OML_swap_method, GLX_OML_sync_control,
        GLX_SGIS_multisample, GLX_SGIX_fbconfig, GLX_SGIX_pbuffer,
        GLX_SGIX_visual_select_group, GLX_SGI_make_current_read,
        GLX_SGI_swap_control, GLX_SGI_video_sync
    Extended renderer info (GLX_MESA_query_renderer):
        Vendor: X.Org (0x1002)
        Device: AMD REDWOOD (DRM 2.43.0, LLVM 3.8.0) (0x68c8)
        Version: 11.2.2
        Accelerated: yes
        Video memory: 1024MB
        Unified memory: no
        Preferred profile: core (0x1)
        Max core profile version: 3.3
        Max compat profile version: 3.0
        Max GLES1 profile version: 1.1
        Max GLES[23] profile version: 3.0
    OpenGL vendor string: X.Org
    OpenGL renderer string: Gallium 0.4 on AMD REDWOOD (DRM 2.43.0, LLVM 3.8.0)
    OpenGL core profile version string: 3.3 (Core Profile) Mesa 11.2.2
    OpenGL core profile shading language version string: 3.30
    OpenGL core profile context flags: (none)
    OpenGL core profile profile mask: core profile
    OpenGL core profile extensions:
    I'm not sure how much you need to see, please let me know if you want more output, I piped the output to a file (glxinfo > temp.txt). I'm using a separate computer and ssh'ing to the machine.

  6. #6
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    19,803
    Blog Entries
    14

    Default Re: Black screen for one user after upgrade from 13.2 -> 42.1 -> 42.2 (really stuck...)

    Just a thought: could there be 'older' widgets involved?
    A trick: logout, go to the console, login with your affected username, and
    Code:
    mkdir SAVED_PLASMA_CONFIG
    mv ~/.config/plasm* SAVED_PLASMA_CONFIG
    logout, return to login screen, login and see if it works now.

    Another one I ran into: remove ~/local/share/kscreen
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    https://en.opensuse.org/openSUSE:Board#Members
    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  7. #7

    Default Re: Black screen for one user after upgrade from 13.2 -> 42.1 -> 42.2 (really stuck...)

    Quote Originally Posted by ihube View Post
    I then logged in with my broken user account using iceWM, here's the head of glxinfo:
    Looks good, but that's after you added your user to the group "video".
    Did you try if Plasma starts now?

  8. #8

    Default Re: Black screen for one user after upgrade from 13.2 -> 42.1 -> 42.2 (really stuck...)

    Quote Originally Posted by wolfi323 View Post
    Looks good, but that's after you added your user to the group "video".
    Did you try if Plasma starts now?
    Yes - it still didn't work, I changed from iceWM to Plasma5 on the login screen. Just trying Knurpht's trick right now.

    Thanks you for helping.

  9. #9

    Default Re: Black screen for one user after upgrade from 13.2 -> 42.1 -> 42.2 (really stuck...)

    Quote Originally Posted by Knurpht View Post
    Just a thought: could there be 'older' widgets involved?
    A trick: logout, go to the console, login with your affected username, and
    Code:
    mkdir SAVED_PLASMA_CONFIG
    mv ~/.config/plasm* SAVED_PLASMA_CONFIG
    logout, return to login screen, login and see if it works now.

    Another one I ran into: remove ~/local/share/kscreen
    As mentioned above, I've essentially tried this by removing everything in ~/. (all .* files and directories). I tried the move anyway (from my ssh console) and then tried logging back in again. Before I did this a can confirm that ~/.local/share only contains a directory called kactivitymanagerd (no kscreen dir/file), this then contains a resources directory which contains:

    -rw-r--r-- 1 user group 12288 Jun 22 10:06 .nfs00000000000000e800000010 (changed to user and group to protect the innocent!)

    The login still did not work.

  10. #10

    Default Re: Black screen for one user after upgrade from 13.2 -> 42.1 -> 42.2 (really stuck...)

    Fixed! I wish I could leave explicit details for those who follow but I did a whole bunch of things (including deleting a lot of old files)... From a remote shell I watched the system using journalctl -f, this clued me in to the fact that the display manager was using kdm so I switched it over to sddm by editing /etc/sysconfig/displaymanager, the file now contains this:

    Code:
    # Here you can set the default Display manager (kdm/xdm/gdm/wdm/entrance/console).
    # all changes in this file require a restart of the displaymanager
    #
    DISPLAYMANAGER="sddm"
    I was suspicious of how my home directory is mounted in /etc/fstab (the setting seemed very basic) so I made some adjustments to the mount and rebooted. Just before rebooting and while logged out of the troublesome account I used lsof /usr5 (/usr5 is the mount point where our home directories reside) to see if anything was still using this filesystem, which it was (not good and perhaps the root behind the suspected permission issues?!). I did the reboot and then removed the .* files again (from a remote ssh console session). And hey presto it works...

    Certainly the journalctl -f helped get me started!

    Thanks for helping me guys, it's really appreciated.

Page 1 of 2 12 LastLast

Posting Permissions

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