Summary: | x11-drivers/nvidia-drivers-390.42 - Cannot login with lightdm, xfce4 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | thomas |
Component: | Current packages | Assignee: | David Seifert <soap> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | CC: | ionen, xfce |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Xorg.0.log |
Description
thomas
2018-03-17 10:54:43 UTC
No problems using x11-misc/slim. It would really help if you attached a relevant[1] Xorg*.log that might shed light on the problem. [1] I.e. not the one lightdm uses. The one after that. Created attachment 524228 [details]
Xorg.0.log
I don't know what you mean by the relevant one. I know only of one Xorg.0.log.
It may be I'm experiencing the same issue, using slim and xfce4. Like thomas says, after entering the password, the login manager disappears, "and that's it". I'm greeted with what looks like a grey undecorated window, and a mouse cursor. However, I found that switching to a text console (eg. CTRL-ALT-F1) and back to the X terminal, "the environment gets reset" for lack of a better phrase, and my usual desktop session appears as I would have expected it to in the first place. This started happening with >=nvidia-drivers-390 and persists through to the latest 396.18-r1. It does not happen with <=384.130. $ emerge --info Portage 2.3.24 (python 3.5.4-final-0, default/linux/amd64/17.0/desktop, gcc-6.4.0, glibc-2.25-r11, 4.15.15-gentoo x86_64) ================================================================= System uname: Linux-4.15.15-gentoo-x86_64-AMD_Ryzen_7_1800X_Eight-Core_Processor-with-gentoo-2.4.1 KiB Mem: 32941312 total, 18649788 free KiB Swap: 16777212 total, 16777212 free Timestamp of repository gentoo: Fri, 13 Apr 2018 01:30:01 +0000 Head commit of repository gentoo: 804a0d7244a06736d01c353b45c20daf324f0722 sh bash 4.4_p12 ld GNU ld (Gentoo 2.29.1 p3) 2.29.1 app-shells/bash: 4.4_p12::gentoo dev-java/java-config: 2.2.0-r4::gentoo dev-lang/perl: 5.24.3-r1::gentoo dev-lang/python: 2.7.14-r1::gentoo, 3.5.4-r1::gentoo dev-util/cmake: 3.9.6::gentoo dev-util/pkgconfig: 0.29.2::gentoo sys-apps/baselayout: 2.4.1-r2::gentoo sys-apps/openrc: 0.34.11::gentoo sys-apps/sandbox: 2.13::gentoo sys-devel/autoconf: 2.13::gentoo, 2.69-r4::gentoo sys-devel/automake: 1.11.6-r3::gentoo, 1.15.1-r2::gentoo sys-devel/binutils: 2.29.1-r1::gentoo sys-devel/gcc: 6.4.0-r1::gentoo sys-devel/gcc-config: 1.8-r1::gentoo sys-devel/libtool: 2.4.6-r3::gentoo sys-devel/make: 4.2.1::gentoo sys-kernel/linux-headers: 4.13::gentoo (virtual/os-headers) sys-libs/glibc: 2.25-r11::gentoo Same with 390.48. But the CTRL-ALT-F1 workaround helps. I cannot try >=391.0.0, because those won't work with my gfx card. The errors from the attached Xorg log: [ 16.872] (EE) NVIDIA(GPU-0): Unable to add conservative default mode "nvidia-auto-select". [ 16.872] (EE) NVIDIA(GPU-0): Unable to add "nvidia-auto-select" mode to ModePool. OK, so it is a bug in the Nvidia driver. ForceCompositionPipeline in xorg.conf (which gets rid of tearing in Xfce4) is the problem. Removing that option makes login work again. Never versions of the driver are supposed to fix that but they don't. Workaround is to enable ForceCompositionPipeline AFTER login, so for example as Autostart entry with the command: sh -c "sleep 5 && nvidia-settings --assign CurrentMetaMode=\"nvidia-auto-select +0+0 { ForceCompositionPipeline = On }\"" The sleep was necessary for me. You can read more here: https://forum.manjaro.org/t/nvidia-390-25-xfce-login-problem-workaround/42070 I use ForceCompositionPipeline and xfce4, so I assume this is obsolete. Please open a new bug if believe there's still something. I do remember having a similar sounding issue with xfce4 before though, reverting xfce4's display monitor settings to default had fixed it. |