Bug 1167855
Summary: | gdm does now show up, startx works | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Martin Žember <mzember> |
Component: | xorg-x11-drv-intel | Assignee: | Adam Jackson <ajax> |
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | CC: | ebenes, sdodson, tpelka |
Target Milestone: | rc | Keywords: | OtherQA |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-11-19 04:23:55 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Martin Žember
2014-11-25 14:15:12 UTC
# journalctl -u gdm.service -- Logs begin at Tue 2014-11-25 13:44:26 CET, end at Tue 2014-11-25 15:52:11 CET. -- Nov 25 13:45:11 dhcp-25-60.brq.redhat.com systemd[1]: Starting GNOME Display Manager... Nov 25 13:45:11 dhcp-25-60.brq.redhat.com systemd[1]: Started GNOME Display Manager. Nov 25 13:45:36 dhcp-25-60.brq.redhat.com gdm[2450]: Failed to set slave bus name on parent: Timeout was reached The kernel traceback is the same as in Bug 1163074 FWIW. RHEL-7.1-Beta-1.5 has the same issue. In the startx mode, I encounter states when the screen flashes like a discotheque and I am able to reproduce it. But I doubt it will be dealt with, it is a low severity issue anyway. I wonder what have I done to the system to break the gdm. GDM works now. I am trying to find what has caused this, but I do not know. I have tried this command (and similar yum commands), but I see only an error: # yum history packages-list Error: Failed history packages-list Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2015-2198.html |