Page 1 of 4 123 ... LastLast
Results 1 to 10 of 33

Thread: Graphical Desktop Problem

  1. #1

    Default Graphical Desktop Problem

    First, new to forum.

    I inherited support of a server running Leap. It is supposed to boot to a graphical display with login options. It does not.
    It boots to a black screen with a large mouse cursor.

    I can CTL-ALT-F1, log in as root, init-3 and startx and the graphical desktop loads fine. If I log in as any of the other 6 users on the system the startx fails.

    My Linux skills are old. I'm sure it's a simple fix but I have not found it yet.

    Additionally, if I do an update install on Leap everything works just fine.

    I have the two test servers side by side now and I'm trying to track down what configuration file or files are suspect but not having any luck just yet.

    Can someone tell me procedures from when linux starts the graphical load ?

    Or can someone help point me in a direction ?

    Thanks

  2. #2
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    18,951
    Blog Entries
    1

    Default Re: Graphical Desktop Problem

    Quote Originally Posted by ms171892 View Post
    First, new to forum.
    Welcome aboard.

    I inherited support of a server running Leap. It is supposed to boot to a graphical display with login options. It does not.
    It boots to a black screen with a large mouse cursor.

    I can CTL-ALT-F1, log in as root, init-3 and startx and the graphical desktop loads fine. If I log in as any of the other 6 users on the system the startx fails.

    My Linux skills are old. I'm sure it's a simple fix but I have not found it yet.

    Additionally, if I do an update install on Leap everything works just fine.
    I'm not quite sure what you mean by this? Is the updated server booting to a complete functioning desktop? Login screen?

    I have the two test servers side by side now and I'm trying to track down what configuration file or files are suspect but not having any luck just yet.
    Information about the display manager might be useful...
    Code:
    systemctl status display-manager
    Is auto-login configured?
    Code:
    grep "AUTO" /etc/sysconfig/displaymanager
    Can someone tell me procedures from when linux starts the graphical load ?

    Or can someone help point me in a direction ?

    Thanks
    To get an overview of the execution tree of systemd units (current init system) do
    Code:
    sudo systemd-analyze critical-chain
    You'll see that display-manager.service is triggered by graphical.target
    Code:
    cat /usr/lib/systemd/system/display-manager.service
    Code:
    sudo systemctl cat graphical.target 
    # /usr/lib/systemd/system/graphical.target
    #  This file is part of systemd.
    #
    #  systemd is free software; you can redistribute it and/or modify it
    #  under the terms of the GNU Lesser General Public License as published by
    #  the Free Software Foundation; either version 2.1 of the License, or
    #  (at your option) any later version.
    
    [Unit]
    Description=Graphical Interface
    Documentation=man:systemd.special(7)
    Requires=multi-user.target
    Wants=display-manager.service
    Conflicts=rescue.service rescue.target
    After=multi-user.target rescue.service rescue.target display-manager.service
    AllowIsolate=yes
    openSUSE Leap 15.0; KDE Plasma 5

  3. #3
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    18,951
    Blog Entries
    1

    Default Re: Graphical Desktop Problem

    Some more information about your graphics hardware/drivers might be useful here as well
    Code:
    /sbin/lspci -nnk|egrep -iA3 "vga|graphics"
    Code:
    inxi -Gxx
    openSUSE Leap 15.0; KDE Plasma 5

  4. #4

    Default Re: Graphical Desktop Problem

    hms-agserver64:~# /sbin/lspci -nnk|egrep -iA3 "vga|graphics"
    00:02.0 VGA compatible controller [0300]: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03)
    Subsystem: Lenovo ThinkCentre M6258 [17aa:3048]
    Kernel modules: i915
    00:02.1 Display controller [0380]: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e13] (rev 03)
    Subsystem: Lenovo Device [17aa:3048]
    00:03.0 Communication controller [0780]: Intel Corporation 4 Series Chipset HECI Controller [8086:2e14] (rev 03)
    Subsystem: Lenovo Device [17aa:3048]
    hms-agserver64:~#

    I did try to reply to all the info you requested in your first reply. I must have not done it incorrectly so I will try again.

  5. #5

    Default Re: Graphical Desktop Problem

    In answer to your first response, I do have two servers next to each other. One in it's original state of not working correctly and one that works correctly after an 'update' install of Leap.

    systemctl status display-manager
    ● display-manager.service - X Display Manager
    Loaded: loaded (/usr/lib/systemd/system/display-manager.service; enabled; vendor preset: enabled)
    Active: inactive (dead) since Wed 2018-09-26 19:27:41 MDT; 8min ago
    Process: 1611 ExecStop=/usr/lib/X11/display-manager stop (code=exited, status=0/SUCCESS)
    Process: 1254 ExecStart=/usr/lib/X11/display-manager start (code=exited, status=0/SUCCESS)
    Main PID: 1383 (code=exited, status=0/SUCCESS)

    Sep 26 19:26:12 hms-agserver64 sddm-helper[1463]: [PAM] Starting...
    Sep 26 19:26:12 hms-agserver64 sddm-helper[1463]: [PAM] Authenticating...
    Sep 26 19:26:12 hms-agserver64 sddm-helper[1463]: [PAM] returning.
    Sep 26 19:26:12 hms-agserver64 sddm[1383]: Authenticated successfully
    Sep 26 19:26:12 hms-agserver64 sddm-helper[1463]: pam_unix(sddm-autologin:session): session opened for user appgen by (uid=0)
    Sep 26 19:26:32 hms-agserver64 sddm[1383]: Session started
    Sep 26 19:26:33 hms-agserver64 sddm[1383]: Auth: sddm-helper exited with 1
    Sep 26 19:27:41 hms-agserver64 systemd[1]: Stopping X Display Manager...
    Sep 26 19:27:41 hms-agserver64 display-manager[1611]: Shutting down service sddm..done
    Sep 26 19:27:41 hms-agserver64 systemd[1]: Stopped X Display Manager.

    grep "AUTO" /etc/sysconfig/displaymanager
    DISPLAYMANAGER_AUTOLOGIN="appgen"
    # DISPLAYMANAGER_AUTOLOGIN is empty.

    I'm looking at the other checks / info you posted.

    Thanks

  6. #6

    Default Re: Graphical Desktop Problem

    inxi -Gxx
    Resuming in non X mode: glxinfo not found. For package install advice run: inxi --recommends
    Graphics: Card: Intel 4 Series Integrated Graphics Controller
    bus-ID: 00:02.0 chip-ID: 8086:2e12
    Display Server: X.org 1.18.3 drivers: fbdev (unloaded: modesetting,vesa)
    tty size: 80x33 Advanced Data: N/A for root
    hms-agserver64:~#

  7. #7
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    10,521
    Blog Entries
    3

    Default Re: Graphical Desktop Problem

    You are set for auto-login as user "appgen".

    My first suggestion would be to disable auto-login. To do that, edit the file "/etc/sysconfig/displaymanager" (as root), and change that "appgen" to just "".

    When you then reboot, you should now get a graphic login screen. That's provided by SDDM, your display manager.

    If you instead still get a black screen, then that tells us something about where things are going wrong. My best guess is that you will get a login screen.

    Near the bottom left corner of the login screen, there is a menu. On that menu, you can select which desktop you wish to use. The choices depend on what software you have installed. One of the choices should be "Icewm" (or maybe it says "Icewm session". It is a very simple desktop, and should work. Maybe try that as a test.

    The other choices should include "Plasma" and "Plasma (Wayland)" or something similar. Before you do anything, make a note of the selected session (before you change it). That will be useful to know.

    I'm guessing (and this is a wild guess), that you were set to use "Plasma (Wayland)". The reason that I am guessing this, is that Plasma (Wayland) has a particularly large cursor arrow. And you mentioned that as a symptom. Some graphic hardware might have problems with Wayland graphics. So try just the plain "Plasma" (or it might say "Plasma (X11)" or similar). That's more likely to work than the Wayland version.
    opensuse Leap 15.0; KDE Plasma 5;
    opensuse tumbleweed; KDE Plasma 5 (test system);

  8. #8
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    18,951
    Blog Entries
    1

    Default Re: Graphical Desktop Problem

    Quote Originally Posted by ms171892 View Post
    In answer to your first response, I do have two servers next to each other. One in it's original state of not working correctly and one that works correctly after an 'update' install of Leap.
    When you say 'update install', which version did you upgrade from?

    The display-manager service output looks ok, and I can see that it is configured to auto-login (appgen user account).
    openSUSE Leap 15.0; KDE Plasma 5

  9. #9

    Default Re: Graphical Desktop Problem

    Non-working versions are:

    openSUSE Leap 42.3
    KDE Plasma Versioin 5.8.7
    KDE Frameworks Version 5.32.0
    Qt Version 5.6.2
    Kernel Version 4.4.138-59-default
    OS Type 64-bit

    Working machine versions are:

    openSUSE Leap 15.0
    KDE Plasma Version 5.12.6
    KDE Frameworks Version 5.45.0
    Qt Version 5.9.4
    Kernel Version 4.12.14-lp150.12.16-default
    OS Type 64-bit

  10. #10

    Default Re: Graphical Desktop Problem

    Turning off 'Auto Login' did not alter the boot progress. System still stops at black screen with a rather large mouse cursor.

Page 1 of 4 123 ... 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
  •