Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problems starting gdm after minimal installation #210

Closed
ghost opened this issue Sep 21, 2018 · 21 comments
Closed

Problems starting gdm after minimal installation #210

ghost opened this issue Sep 21, 2018 · 21 comments
Assignees
Labels
bug desktop Affects Desktop experience

Comments

@ghost
Copy link

ghost commented Sep 21, 2018

I followed the steps detailed on the bare metal install guide and the create and enable a new userspace one. [EDIT: I also have tried the VMWare disk image installation] I tried them both on a bare metal compatible system and on VMware Player 14 and in both cases when I reach the systemctl start gdm step nothing happens

gdm_not_working

Steps to reproduce the behavior

  1. Install the system following the aforementioned guides

Expected behaviour
The gdm interface should start and connect to the Xorg server

Screenshots
Xorg verbose output after trying to start it for the first time:
startx_not_working_first_start

Xorg verbose output anfter trying to start it at subsequent times:
startx_not_working

Environment:

  • Clear Linux OS version:
    NAME="Clear Linux OS"
    VERSION=1
    ID=clear-linux-os
    VERSION_ID=25140
    PRETTY_NAME="Clear Linux OS"
    ANSI_COLOR="1;35"
    HOME_URL="https://clearlinux.org"
    SUPPORT_URL="https://clearlinux.org"
    BUG_REPORT_URL="mailto:dev@lists.clearlinux.org"
    PRIVACY_POLICY_URL="http://www.intel.com/privacy"
  • Bundles:
    bootloader
    c-basic
    containers-basic
    desktop
    desktop-apps
    desktop-assets
    desktop-gnomelibs
    desktop-locales
    dev-utils
    dev-utils-dev
    editors
    emacs
    ethtool
    git
    go-basic
    iproute2
    joe
    kernel-native
    koji
    kvm-host
    libX11client
    mail-utils
    mail-utils-dev
    mixer
    network-basic
    network-basic-dev
    openssh-server
    openssl
    os-clr-on-clr
    os-core
    os-core-dev
    os-core-update
    os-core-update-dev
    os-installer
    p11-kit
    package-utils
    perl-basic
    perl-basic-dev
    python2-basic
    python3-basic
    storage-utils
    storage-utils-dev
    sudo
    sysadmin-basic
    sysadmin-basic-dev
    telemetrics
    vim
    web-server-basic
    which
    wpa_supplicant
    xemacs

I also attach the Xorg.0.log
file for further troubleshooting

@puneetse
Copy link
Contributor

@Alec423 while I believe the steps you followed should have worked and there is an addressable issue here, I just want to add a tip that there is a preconfigured VMware disk image available too: https://clearlinux.org/documentation/clear-linux/get-started/virtual-machine-install/vmw-player-preconf

It may help you get up and running sooner. The preconfigured disk image includes an optimized kernel for VMware guests and likely includes the missing Xorg driver.

@ghost
Copy link
Author

ghost commented Sep 24, 2018

@puneetse I’m sorry, but I tried the preconfigured disk image too and gives the same problems

@puneetse
Copy link
Contributor

@Alec423 ah, thanks for trying and confirming.

@ahkok ahkok added the bug label Sep 24, 2018
@ahkok
Copy link
Contributor

ahkok commented Sep 24, 2018

Confirmed, this seems to be breaking on xwayland, which is crashing.

@ahkok
Copy link
Contributor

ahkok commented Sep 24, 2018

On my Atom processor, I get:

(EE) Illegal instruction at address 0x...

Whether this is the same root cause as the other reports, I do not yet know. However, this is certainly a bug we should be able to fix.

@ahkok
Copy link
Contributor

ahkok commented Sep 24, 2018

If you are seeing this issue and you have Xwayland errors in journalctl, you can try the following:

# cat /etc/gdm/custom.conf 
[daemon]
WaylandEnable=false

That will force gdm not to use Xwayland and may work around the issue (It did for me)

@ghost
Copy link
Author

ghost commented Sep 25, 2018

@ahkok In the base install there is nothing of such kind, the folder /etc/gdm/ isn't even present, let alone the config file to edit

@mrkz
Copy link

mrkz commented Sep 25, 2018

@Alec423 yes, we ship empty /etc/ due to stateless, but you can safely do

# mkdir -p /etc/gdm

# cat > /etc/gdm/custom.conf << EOF
[daemon]
WaylandEnable=false
EOF

@miguelinux
Copy link
Member

miguelinux commented Sep 25, 2018 via email

@ghost
Copy link
Author

ghost commented Sep 25, 2018

@mrkz unfortunately it still doesn’t work even after creating the folder and the conf file

@ahkok
Copy link
Contributor

ahkok commented Sep 25, 2018

@Alec423 make sure to restart your system. Can you post the output of journalctl -b somewhere (e.g. gist.github.com?) and include a link to it? Are you seeing Illegal Instruction anywhere?

@ghost
Copy link
Author

ghost commented Sep 25, 2018

@ahkok this is an extract from the complete log showing a typical boot + login + poweroff case, didn't find any Illegal Instruction

https://gist.github.com/Alec423/7fd9ee338a74cb72ddad54625f426d7a

@ahkok
Copy link
Contributor

ahkok commented Sep 25, 2018

Yeah, it seems the VMware virtual machine is a different error path and unrelated to the Illegal Instruction (it doesn't use Xwayland afaics, even)

@ghost
Copy link
Author

ghost commented Sep 25, 2018

@ahkok I don't have any powerful computer to install clearlinux quickly on and confront the journalctl; is this suggesting that both the VMWare installation and the bare metal one have the same gdm problem but generating from a different source?

@miguelinux
Copy link
Member

I got a coredump when I use my laptop in lid and connected with external monitor

$ coredumpctl 
TIME                            PID   UID   GID SIG COREFILE  EXE
Tue 2018-09-25 14:45:57 CDT     713   311   311  11 error     /usr/bin/gnome-shell
Tue 2018-09-25 14:45:57 CDT     721   311   311   6 error     /usr/bin/Xwayland

BUT

When I set /etc/gdm/custom.conf, it works well.

@ahkok
Copy link
Contributor

ahkok commented Sep 25, 2018

different problem entirely.

@ahkok
Copy link
Contributor

ahkok commented Oct 4, 2018

25400 solves the SIGILL problem. Other issues may remain, so, I'm keeping this bug open

@yakuizhao
Copy link

Any progress about this issue?

@ahkok
Copy link
Contributor

ahkok commented Oct 15, 2018

Someone needs to try/test on VMware, which was the original bug report.

@mountainerd
Copy link

Not sure if it's directly applicable here but the symptoms and error output look similar. Recently, when I did a minimal install, then installed the desktop, then tried to login, it barfed like this. Turns out the installer set the ownership on my home directory to root:root. Once I resolved that, errors went away,

@iphutch iphutch added this to Not yet started in Developer desktop Nov 8, 2018
@mrkz
Copy link

mrkz commented Apr 5, 2019

@Alec423 could you please try to verify the VMware issue still persists? As far as I can see, we are providing /usr/lib64/dri/vmwgfx_dri.so (verified on CLR release 28610). Otherwise we should be able to close this bug now.

Thanks!

@iphutch iphutch added the desktop Affects Desktop experience label Jun 4, 2019
@mrkz mrkz closed this as completed Jun 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug desktop Affects Desktop experience
Projects
No open projects
Developer desktop
  
Open for contributions
Development

No branches or pull requests

8 participants