Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
X does not login after boot, only after restarting service
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
Massimo B.
Veteran
Veteran


Joined: 09 Feb 2005
Posts: 1579
Location: Germany

PostPosted: Mon Jul 29, 2019 7:20 am    Post subject: X does not login after boot, only after restarting service Reply with quote

Hi, beside my issue [1] I have an issue that X starts fine, but every first login fails in a black screen. I always need to
Code:
rc-service xdm restart
from a root terminal first, then I can login as usual.
This machine has 1 internal intel graphics and 1 PCIe radeon:

Code:
# lspci |grep -e VGA -e Display
00:02.0 Display controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09)
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos XT [Radeon HD 7470/8470 / R5 235/310 OEM]

# dmidecode -t system
# dmidecode 3.2
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.

Handle 0x0001, DMI type 1, 27 bytes
System Information
   Manufacturer: Hewlett-Packard
   Product Name: HP Compaq Pro 6300 SFF
   Version: Not Specified
   Serial Number: ##########
   UUID: #########-####-####-####-###########
   Wake-up Type: Power Switch
   SKU Number: H4U29ES#ABD
   Family: 103C_53307F G=D

Handle 0x000A, DMI type 32, 20 bytes
System Boot Information
   Status: No errors detected

But the same issue I also have on a HP EliteDesk 800 G1 SFF that has only 1 single intel graphics. As the setup is quite equal, this could also be something with my custom installation.
_________________
ppc:PowerBook5,8 15"(1440)-G4/1.67,2G|amd64:HP EliteBook 8560w,i7-2620M,16G|Acer Z5610 (Core2QuadQ8200),8G|amd64-prefix:OpenSuse|HP EliteDesk 800G1 i7-4790|HP Compaq Pro 6300 i7-3770
Lila-Theme
Back to top
View user's profile Send private message
Massimo B.
Veteran
Veteran


Joined: 09 Feb 2005
Posts: 1579
Location: Germany

PostPosted: Mon Jul 29, 2019 7:27 am    Post subject: Reply with quote

Here are the logs after such a failed login:

Xorg.0.log doesn't have any related (WW) or (EE)

lightdm.log:
[+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
[+0.00s] DEBUG: Starting Light Display Manager 1.30.0, UID=0 PID=3677
[+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d
[+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf
[+0.00s] DEBUG:   [LightDM] contains unknown option session-wrapper
[+0.00s] DEBUG: Registered seat module local
[+0.00s] DEBUG: Registered seat module xremote
[+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
[+0.09s] DEBUG: Monitoring logind for seats
[+0.09s] DEBUG: New seat added from logind: seat0
[+0.09s] DEBUG: Seat seat0: Loading properties from config section Seat:*
[+0.09s] DEBUG: Seat seat0: Starting
[+0.09s] DEBUG: Seat seat0: Creating greeter session
[+0.09s] DEBUG: Seat seat0: Creating display server of type x
[+0.09s] DEBUG: posix_spawn avoided (fd close requested)
[+0.09s] DEBUG: Could not run plymouth --ping: Failed to execute child process “plymouth” (No such file or directory)
[+0.09s] DEBUG: Using VT 7
[+0.09s] DEBUG: Seat seat0: Starting local X display on VT 7
[+0.09s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log
[+0.09s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0
[+0.09s] DEBUG: XServer 0: Launching X Server
[+0.09s] DEBUG: Launching process 3726: /usr/bin/X :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
[+0.09s] DEBUG: XServer 0: Waiting for ready signal from X server :0
[+0.09s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
[+0.09s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
[+0.14s] DEBUG: Loading users from org.freedesktop.Accounts
[+0.14s] DEBUG: User /org/freedesktop/Accounts/User1005 added
[+0.15s] DEBUG: User /org/freedesktop/Accounts/User1001 added
[+0.16s] DEBUG: User /org/freedesktop/Accounts/User1003 added
[+0.16s] DEBUG: User /org/freedesktop/Accounts/User1002 added
[+0.17s] DEBUG: User /org/freedesktop/Accounts/User4728 added
[+0.17s] DEBUG: User /org/freedesktop/Accounts/User1007 added
[+0.87s] DEBUG: Got signal 10 from process 3726
[+0.87s] DEBUG: XServer 0: Got signal from X server :0
[+0.87s] DEBUG: XServer 0: Connecting to XServer :0
[+0.87s] DEBUG: posix_spawn avoided (fd close requested) (child_setup specified)
[+0.87s] DEBUG: Seat seat0: Display server ready, starting session authentication
[+0.87s] DEBUG: Session pid=3967: Started with service 'lightdm-greeter', username 'lightdm'
[+0.90s] DEBUG: Session pid=3967: Authentication complete with return value 0: Success
[+0.90s] DEBUG: Seat seat0: Session authenticated, running command
[+0.90s] DEBUG: Session pid=3967: Running command /usr/sbin/lightdm-gtk-greeter
[+0.90s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm
[+0.90s] DEBUG: Session pid=3967: Logging to /var/log/lightdm/seat0-greeter.log
[+0.91s] DEBUG: Activating VT 7
[+0.91s] DEBUG: Activating login1 session 1
[+0.91s] DEBUG: Seat seat0 changes active session to 1
[+0.91s] DEBUG: Session 1 is already active
[+1.12s] DEBUG: Greeter connected version=1.30.0 api=1 resettable=false
[+1.36s] DEBUG: Greeter start authentication
[+1.36s] DEBUG: Session pid=3999: Started with service 'lightdm', username '(null)'
[+1.36s] DEBUG: Session pid=3999: Got 1 message(s) from PAM
[+1.36s] DEBUG: Prompt greeter with 1 message(s)
[+4.37s] DEBUG: Seat seat0 changes active session to
[+4.69s] DEBUG: Seat seat0 changes active session to 1
[+4.69s] DEBUG: Session 1 is already active
[+6.21s] DEBUG: Greeter start authentication for mb
[+6.21s] DEBUG: Session pid=3999: Sending SIGTERM
[+6.21s] DEBUG: Session pid=4199: Started with service 'lightdm', username 'mb'
[+6.21s] DEBUG: Session pid=3999: Terminated with signal 15
[+6.21s] DEBUG: Session: Failed during authentication
[+6.21s] DEBUG: Seat seat0: Session stopped
[+6.22s] DEBUG: Session pid=4199: Got 1 message(s) from PAM
[+6.22s] DEBUG: Prompt greeter with 1 message(s)
[+10.19s] DEBUG: Continue authentication
[+10.22s] DEBUG: Session pid=4199: Authentication complete with return value 0: Success
[+10.22s] DEBUG: Authenticate result for user mb: Success
[+10.22s] DEBUG: User mb authorized
[+10.22s] DEBUG: Greeter sets language de_DE.utf8
[+10.23s] DEBUG: Greeter closed communication channel
[+10.23s] DEBUG: Session pid=3967: Exited with return value 1
[+10.23s] DEBUG: Seat seat0: Session stopped
[+10.23s] DEBUG: Seat seat0: Stopping; failed to start a greeter
[+10.23s] DEBUG: Seat seat0: Stopping
[+10.23s] DEBUG: Seat seat0: Stopping display server
[+10.23s] DEBUG: Sending signal 15 to process 3726
[+10.23s] DEBUG: Seat seat0: Stopping session
[+10.23s] DEBUG: Seat seat0 changes active session to
[+10.23s] DEBUG: Session pid=4199: Exited with return value 0
[+10.23s] DEBUG: Seat seat0: Session stopped
[+10.38s] DEBUG: Process 3726 exited with return value 0
[+10.38s] DEBUG: XServer 0: X server stopped
[+10.38s] DEBUG: Releasing VT 7
[+10.38s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0
[+10.38s] DEBUG: Seat seat0: Display server stopped
[+10.38s] DEBUG: Seat seat0: Stopped
[+10.38s] DEBUG: Required seat has stopped
[+10.38s] DEBUG: Stopping display manager
[+10.38s] DEBUG: Display manager stopped
[+10.38s] DEBUG: Stopping daemon
[+10.39s] DEBUG: Exiting with return value 1
seat0-greeter.log:
** Message: 07:02:34.839: Starting lightdm-gtk-greeter 2.0.6 (Sep 17 2018, 15:03:15)
** Message: 07:02:34.842: [Configuration] Reading file: /etc/lightdm/lightdm-gtk-greeter.conf

** (lightdm-gtk-greeter:3970): WARNING **: 07:02:35.022: [PIDs] Failed to execute command: upstart

(lightdm-gtk-greeter:3970): Gtk-WARNING **: 07:02:35.236: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)

(lightdm-gtk-greeter:3970): Gtk-WARNING **: 07:02:38.609: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)

(lightdm-gtk-greeter:3970): Gtk-WARNING **: 07:02:44.056: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node menubar owner GreeterMenuBar)
Invalid MIT-MAGIC-COOKIE-1 key
** (lightdm-gtk-greeter:3970): WARNING **: 07:02:44.077: [Background] Failed to create root pixmap
x-0.log:
X.Org X Server 1.20.5
X Protocol Version 11, Revision 0
Build Operating System: Linux 5.1.7-gentoo x86_64 Gentoo
Current Operating System: Linux burchm71 5.2.2-gentoo #1 SMP PREEMPT Tue Jul 23 15:47:15 CEST 2019 x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-5.2.2-gentoo root=UUID=########-####-####-####-############ ro rootflags=subvol=volumes/root rd.vconsole.font=ter-u12n rd.vconsole.keymap=de-latin1-nodeadkeys rd.locale.LANG=de_DE.UTF-8 rd.lvm=0 rd.md=0 rd.dm=0 rd.luks.uuid=########-####-####-####-############ rd.luks.allow-discards=########-####-####-####-############ root=LABEL=gentoo rootflags=subvol=volumes/root video.allow_duplicates=1
Build Date: 06 June 2019  04:36:58PM
 
Current version of pixman: 0.38.4
   Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
   (++) from command line, (!!) notice, (II) informational,
   (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Jul 29 07:02:33 2019
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
(II) [KMS] Kernel modesetting enabled.
(II) modeset(G0): Initializing kms color map for depth 24, 8 bpc.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported high keycode 372 for name <I372> ignored
>                   X11 cannot support keycodes above 255.
>                   This warning only shows for the first high keycode.
> Internal error:   Could not resolve keysym XF86MonBrightnessCycle
> Internal error:   Could not resolve keysym XF86RotationLockToggle
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported high keycode 372 for name <I372> ignored
>                   X11 cannot support keycodes above 255.
>                   This warning only shows for the first high keycode.
> Internal error:   Could not resolve keysym XF86MonBrightnessCycle
> Internal error:   Could not resolve keysym XF86RotationLockToggle
Errors from xkbcomp are not fatal to the X server
(II) AIGLX: Suspending AIGLX clients for VT switch
(II) Server terminated successfully (0). Closing log file.

_________________
ppc:PowerBook5,8 15"(1440)-G4/1.67,2G|amd64:HP EliteBook 8560w,i7-2620M,16G|Acer Z5610 (Core2QuadQ8200),8G|amd64-prefix:OpenSuse|HP EliteDesk 800G1 i7-4790|HP Compaq Pro 6300 i7-3770
Lila-Theme
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum