Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Update: KDE goes blank with cursor after SDDM login
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
HilhilPoly
n00b
n00b


Joined: 12 May 2019
Posts: 16

PostPosted: Sun Jun 02, 2019 3:37 pm    Post subject: Update: KDE goes blank with cursor after SDDM login Reply with quote

Hi guys, I have a fresh install in which I decided to use Plasma. I put the right profile, installed xorg-server, with VIDEO_CARDS="nvidia", because I want to use the nvidia-drivers, there is a GTX 1060. Then I emerged consolekit and sddm, and I emerged plasma-meta. I set the xdm display manager to sddm, I set ~/.xinitrc like this http://dpaste.com/10CHZRK and I added xdm, consolekit and dbus at default level. Then, I rebooted.
Unfortunately, the screens(this PC has two monitors) stay blank, with a cursor within them. I thought that it was a sddm problem, so I launched CTRL+ALT+F1, I emerged lightdm, and set it in /etc/conf.d/xdm. Rebooting, I didn't see any attempt to run a X server, because a shell apperead. I set up sddm in xdm again, but I don't know what to do.

This is /var/log/Xorg.0.log https://bpaste.net/raw/411ec8c4524a
then /var/log/Xorg.1.log https://bpaste.net/raw/f4d877641cd3
then /var/log/sddm.log https://bpaste.net/raw/43d006ea4d6e
at the end of this there is the log of sddm issued by the shell https://bpaste.net/raw/a0ddb813c66a
then dmesg https://bpaste.net/raw/22492f9c4325
this is emerge --info https://bpaste.net/raw/466311a1d117

What could I do? Thank you.


Last edited by HilhilPoly on Mon Jun 03, 2019 10:58 pm; edited 1 time in total
Back to top
View user's profile Send private message
koschi
Tux's lil' helper
Tux's lil' helper


Joined: 09 Oct 2004
Posts: 121
Location: Tianjin, CN

PostPosted: Mon Jun 03, 2019 4:27 am    Post subject: Reply with quote

If it's a PRIME setup, do you have these lines in your "/usr/share/sddm/scripts/Xsetup" or ".xinitrc"? As mentioned in the wiki https://wiki.gentoo.org/wiki/NVIDIA/Optimus#Simple_Desktop_Display_Manager_.28SDDM.29?

Code:
xrandr --setprovideroutputsource modesetting NVIDIA-0
xrandr --auto


BTW I also see the following line in your Xorg. 0.log. Similar like my issue. Can you login if you're dropped into the shell or is it just a blinking cursor? https://forums.gentoo.org/viewtopic-t-1097502.html
Code:
(EE) Failed to open authorization file "/var/run/sddm/{8b560417-85bc-4709-bd4d-fc24e367c40e}": No such file or directory

_________________
Der Digitalrechner ist ein Vollidiot mit einer einseitigen Begabung im schnellen Addieren.
Back to top
View user's profile Send private message
HilhilPoly
n00b
n00b


Joined: 12 May 2019
Posts: 16

PostPosted: Mon Jun 03, 2019 3:27 pm    Post subject: Reply with quote

First of all, bless you, because I was completely unaware of the NVIDIA/Optimus guide, I re-compiled the kernel for the integrated Intel VGA module and I wrote the xrandr(after emerging it) commands on the sddm script. I also added the NVIDIA modules to be loaded during boot, and eventually, I added the daily user to the video group(I don't know why it wasn't there, I'm pretty sure that I added it during the installation).
Then, the miracle: rebooting, SDDM started, I was able to log in. The first time only a window asked us what mode X should use for the two screen, and I chose Extended Right. Then, I saw the loading screen of Plasma, but then the screens went blank again, with the default KDE cursor able to move within them as a unique screen. At the very end, this happened https://i.imgur.com/iCmJBPK.jpg
That means the problem is with X, I guess.
Now that we are able to log in,
This is /var/log/Xorg.1.log https://bpaste.net/raw/73769631255e
This is /var/log/Xorg.0.log https://bpaste.net/raw/2f83fc223b8d
This is xorg.conf (I tried to run X with and without it) https://bpaste.net/raw/fbaa33ead2e1
This is /etc/X11/xorg.conf.d./20opengl.conf (same thing as above) http://bpaste.net/raw/cfd868607e4e

nvidia-xconfig creates the same xorg.conf
xrandr says "can't open display"

should I try to manually configure X?
what else could I do? Thank you.
Back to top
View user's profile Send private message
HilhilPoly
n00b
n00b


Joined: 12 May 2019
Posts: 16

PostPosted: Mon Jun 03, 2019 10:57 pm    Post subject: Reply with quote

Update, after logging I can see KDE loading screen, but then the screen goes blank and I can only move the cursor.
If I press CTRL+ALT+F1(or F2) I can log in via shh and stop sddm.
If I do this, and then I issue startx, I can see the KDE loading screen again, but with a different(actually higher and optimal) resolution. But after that the screen goes blank again, only the cursor works.

This is dmesg https://bpaste.net/raw/b80edf5f8878
this is /var/log/Xorg.0.log https://bpaste.net/raw/f46eaf7d440b
this is /var/log/Xorg1.log https://bpaste.net/raw/c4c72d8f80d7
this is /var/log/sddm.log https://bpaste.net/raw/7af70c052c75

In the last log I saw a problem with a qt plugin, xcb, I'll try to emerge it and I'll let you know it.

P.S. I'm reading on different threads about people that uploaded the kernel have this problem, which they don't have using older kernel, or using specific mesa versions and deleting /var/lib/sddm/.cache
Do nvidia propetary drivers use mesa?
Could they be a workaround?
Back to top
View user's profile Send private message
koschi
Tux's lil' helper
Tux's lil' helper


Joined: 09 Oct 2004
Posts: 121
Location: Tianjin, CN

PostPosted: Tue Jun 04, 2019 3:01 am    Post subject: Reply with quote

You got some segfaults at the end of your dmesg. I guess that's why you're getting kicked out. But I have no idea what causes this. Maybe somebody else can comment on this?

Code:
[   29.220967] plasmashell[5805]: segfault at 10 ip 00007f7c32ad1b65 sp 00007ffd0892a0f0 error 4 in libQt5Core.so.5.12.3[7f7c32a00000+28d000]
[   29.220972] Code: 53 10 48 8b 56 28 89 7b 14 48 63 42 08 48 01 c8 4c 8d 64 c2 10 4c 89 e7 e8 48 7e f7 ff 84 c0 75 63 49 8b 04 24 31 d2 48 89 c5 <48> 03 68 10 74 45 8b 40 04 85 c0 74 3e 80 7d 00 00 48 8d 4d 01 74
[   90.151485] plasmashell[6038]: segfault at 10 ip 00007f10a084db65 sp 00007ffc8014d580 error 4 in libQt5Core.so.5.12.3[7f10a077c000+28d000]
[   90.151490] Code: 53 10 48 8b 56 28 89 7b 14 48 63 42 08 48 01 c8 4c 8d 64 c2 10 4c 89 e7 e8 48 7e f7 ff 84 c0 75 63 49 8b 04 24 31 d2 48 89 c5 <48> 03 68 10 74 45 8b 40 04 85 c0 74 3e 80 7d 00 00 48 8d 4d 01 74
[  159.311231] X (5842) used greatest stack depth: 11776 bytes left
[  273.392286] plasmashell[6291]: segfault at 10 ip 00007f014e41db65 sp 00007fff1a5cba60 error 4 in libQt5Core.so.5.12.3[7f014e34c000+28d000]
[  273.392291] Code: 53 10 48 8b 56 28 89 7b 14 48 63 42 08 48 01 c8 4c 8d 64 c2 10 4c 89 e7 e8 48 7e f7 ff 84 c0 75 63 49 8b 04 24 31 d2 48 89 c5 <48> 03 68 10 74 45 8b 40 04 85 c0 74 3e 80 7d 00 00 48 8d 4d 01 74
[  368.357796] kscreenlocker_g[6323]: segfault at 10 ip 00007f0cf7dbab65 sp 00007ffcf0848c80 error 4 in libQt5Core.so.5.12.3[7f0cf7ce9000+28d000]
[  368.357801] Code: 53 10 48 8b 56 28 89 7b 14 48 63 42 08 48 01 c8 4c 8d 64 c2 10 4c 89 e7 e8 48 7e f7 ff 84 c0 75 63 49 8b 04 24 31 d2 48 89 c5 <48> 03 68 10 74 45 8b 40 04 85 c0 74 3e 80 7d 00 00 48 8d 4d 01 74
[  368.672535] kscreenlocker_g[6333]: segfault at 10 ip 00007f5be06a7b65 sp 00007ffdce058300 error 4 in libQt5Core.so.5.12.3[7f5be05d6000+28d000]
[  368.672540] Code: 53 10 48 8b 56 28 89 7b 14 48 63 42 08 48 01 c8 4c 8d 64 c2 10 4c 89 e7 e8 48 7e f7 ff 84 c0 75 63 49 8b 04 24 31 d2 48 89 c5 <48> 03 68 10 74 45 8b 40 04 85 c0 74 3e 80 7d 00 00 48 8d 4d 01 74
[  368.990893] kscreenlocker_g[6341]: segfault at 10 ip 00007fee32b27b65 sp 00007ffd02bee1c0 error 4 in libQt5Core.so.5.12.3[7fee32a56000+28d000]
[  368.990898] Code: 53 10 48 8b 56 28 89 7b 14 48 63 42 08 48 01 c8 4c 8d 64 c2 10 4c 89 e7 e8 48 7e f7 ff 84 c0 75 63 49 8b 04 24 31 d2 48 89 c5 <48> 03 68 10 74 45 8b 40 04 85 c0 74 3e 80 7d 00 00 48 8d 4d 01 74
[  369.305018] kscreenlocker_g[6356]: segfault at 10 ip 00007f5e6e257b65 sp 00007fff0418ffa0 error 4 in libQt5Core.so.5.12.3[7f5e6e186000+28d000]
[  369.305023] Code: 53 10 48 8b 56 28 89 7b 14 48 63 42 08 48 01 c8 4c 8d 64 c2 10 4c 89 e7 e8 48 7e f7 ff 84 c0 75 63 49 8b 04 24 31 d2 48 89 c5 <48> 03 68 10 74 45 8b 40 04 85 c0 74 3e 80 7d 00 00 48 8d 4d 01 74


PS: I would stay with the proprietary nvidia drivers for now. You are getting closer to the root of the issue. Changing to the nouveau drivers requires a different Kernel/Xorg configuration. That would change too much now.
_________________
Der Digitalrechner ist ein Vollidiot mit einer einseitigen Begabung im schnellen Addieren.
Back to top
View user's profile Send private message
HilhilPoly
n00b
n00b


Joined: 12 May 2019
Posts: 16

PostPosted: Tue Jun 04, 2019 2:38 pm    Post subject: Reply with quote

koschi wrote:
You got some segfaults at the end of your dmesg. I guess that's why you're getting kicked out. But I have no idea what causes this. Maybe somebody else can comment on this?

Code:
[   29.220967] plasmashell[5805]: segfault at 10 ip 00007f7c32ad1b65 sp 00007ffd0892a0f0 error 4 in libQt5Core.so.5.12.3[7f7c32a00000+28d000]
[   29.220972] Code: 53 10 48 8b 56 28 89 7b 14 48 63 42 08 48 01 c8 4c 8d 64 c2 10 4c 89 e7 e8 48 7e f7 ff 84 c0 75 63 49 8b 04 24 31 d2 48 89 c5 <48> 03 68 10 74 45 8b 40 04 85 c0 74 3e 80 7d 00 00 48 8d 4d 01 74
[   90.151485] plasmashell[6038]: segfault at 10 ip 00007f10a084db65 sp 00007ffc8014d580 error 4 in libQt5Core.so.5.12.3[7f10a077c000+28d000]
[   90.151490] Code: 53 10 48 8b 56 28 89 7b 14 48 63 42 08 48 01 c8 4c 8d 64 c2 10 4c 89 e7 e8 48 7e f7 ff 84 c0 75 63 49 8b 04 24 31 d2 48 89 c5 <48> 03 68 10 74 45 8b 40 04 85 c0 74 3e 80 7d 00 00 48 8d 4d 01 74
[  159.311231] X (5842) used greatest stack depth: 11776 bytes left
[  273.392286] plasmashell[6291]: segfault at 10 ip 00007f014e41db65 sp 00007fff1a5cba60 error 4 in libQt5Core.so.5.12.3[7f014e34c000+28d000]
[  273.392291] Code: 53 10 48 8b 56 28 89 7b 14 48 63 42 08 48 01 c8 4c 8d 64 c2 10 4c 89 e7 e8 48 7e f7 ff 84 c0 75 63 49 8b 04 24 31 d2 48 89 c5 <48> 03 68 10 74 45 8b 40 04 85 c0 74 3e 80 7d 00 00 48 8d 4d 01 74
[  368.357796] kscreenlocker_g[6323]: segfault at 10 ip 00007f0cf7dbab65 sp 00007ffcf0848c80 error 4 in libQt5Core.so.5.12.3[7f0cf7ce9000+28d000]
[  368.357801] Code: 53 10 48 8b 56 28 89 7b 14 48 63 42 08 48 01 c8 4c 8d 64 c2 10 4c 89 e7 e8 48 7e f7 ff 84 c0 75 63 49 8b 04 24 31 d2 48 89 c5 <48> 03 68 10 74 45 8b 40 04 85 c0 74 3e 80 7d 00 00 48 8d 4d 01 74
[  368.672535] kscreenlocker_g[6333]: segfault at 10 ip 00007f5be06a7b65 sp 00007ffdce058300 error 4 in libQt5Core.so.5.12.3[7f5be05d6000+28d000]
[  368.672540] Code: 53 10 48 8b 56 28 89 7b 14 48 63 42 08 48 01 c8 4c 8d 64 c2 10 4c 89 e7 e8 48 7e f7 ff 84 c0 75 63 49 8b 04 24 31 d2 48 89 c5 <48> 03 68 10 74 45 8b 40 04 85 c0 74 3e 80 7d 00 00 48 8d 4d 01 74
[  368.990893] kscreenlocker_g[6341]: segfault at 10 ip 00007fee32b27b65 sp 00007ffd02bee1c0 error 4 in libQt5Core.so.5.12.3[7fee32a56000+28d000]
[  368.990898] Code: 53 10 48 8b 56 28 89 7b 14 48 63 42 08 48 01 c8 4c 8d 64 c2 10 4c 89 e7 e8 48 7e f7 ff 84 c0 75 63 49 8b 04 24 31 d2 48 89 c5 <48> 03 68 10 74 45 8b 40 04 85 c0 74 3e 80 7d 00 00 48 8d 4d 01 74
[  369.305018] kscreenlocker_g[6356]: segfault at 10 ip 00007f5e6e257b65 sp 00007fff0418ffa0 error 4 in libQt5Core.so.5.12.3[7f5e6e186000+28d000]
[  369.305023] Code: 53 10 48 8b 56 28 89 7b 14 48 63 42 08 48 01 c8 4c 8d 64 c2 10 4c 89 e7 e8 48 7e f7 ff 84 c0 75 63 49 8b 04 24 31 d2 48 89 c5 <48> 03 68 10 74 45 8b 40 04 85 c0 74 3e 80 7d 00 00 48 8d 4d 01 74


PS: I would stay with the proprietary nvidia drivers for now. You are getting closer to the root of the issue. Changing to the nouveau drivers requires a different Kernel/Xorg configuration. That would change too much now.


I think that the last part of these segfaults are linked to the broken screenlocker that one can see in the pic I posted.
Anyway, I followed the two last posts of this topic https://forums.gentoo.org/viewtopic-t-1075938.html and I got black screen with a window which said that ksplashqml crashed. I tried to get a log, but the window said that there wasn't gdb, which I immediately emerged. I re-created the crash and this is the log https://bpaste.net/raw/24053ae82b91

P.S. Seeing that nobody has even a hint after 265 visualization is pretty discouraging :oops:
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