Black screen after starting session for 2 minutes

[thelocotauren]

Hi, I've been running debian 9 unstable for about a year and a half without any issues, but two days ago, after updating the system, plasma broke down (I think its plasma). Basically the only two changes I see are a failed job trying to mount my encrypted swap partition and after logging in, I just see a black screen for 10 seconds aprox until the mouse cursor shows up. After that I have 1:30 minutes aprox of a black screen with the mouse cursor working correctly, and then my session starts correctly. I've checked Xorg.log.0 and syslog and they don't show any error. I've also tried creating a new user to check if it wasn't some sort of permissions issue and that didin't work either. I commented my swap partition out of /etc/fstab and that fixed the failing job on startup, but the black screen remains the same. After trying everything I said, I gave up and proceeded to reinstall Debian, and after upgrading to unstable again with a clean install, the same issue appears.

Here's my sources.list:

Code: Select all

#------------------------------------------------------------------------------#
#                   OFFICIAL DEBIAN REPOS                    
#------------------------------------------------------------------------------#

###### Debian Main Repos
deb http://deb.debian.org/debian/ unstable main contrib non-free
deb-src http://deb.debian.org/debian/ unstable main contrib non-free

#------------------------------------------------------------------------------#
#                      UNOFFICIAL  REPOS                       
#------------------------------------------------------------------------------#

###### 3rd Party Binary Repos
###Debian Multimedia
deb [arch=amd64,i386] http://www.deb-multimedia.org sid main non-free

###MariaDB
deb [arch=amd64,i386] http://mirror.23media.de/mariadb/repo/10.2/debian sid main
deb-src [arch=amd64,i386] http://mirror.23media.de/mariadb/repo/10.2/debian sid main

###PostgreSQL
deb [arch=amd64,i386] http://apt.postgresql.org/pub/repos/apt/ sid-pgdg main

###Spotify
deb http://repository.spotify.com stable non-free

###TOR
deb [arch=i386,amd64,armel,armhf] http://deb.torproject.org/torproject.org unstable main
deb-src [arch=i386,amd64,armel,armhf] http://deb.torproject.org/torproject.org unstable main

###Wine
deb [arch=i386] https://dl.winehq.org/wine-builds/debian/ sid main

Any idea on what the problem could be?
My computer's a Dell Latitude 7490.

[None1975]

Any idea on what the problem could be?

This (Spotify), plus development version of the Debian distribution.

[Head_on_a_Stick]

My money's on deb-multimedia[1] but who knows, really?

@OP: what does the systemd journal have to say? Is anything printed to the journal during the delay?

[1] It has a bad reputation on these boards.

[xepan]

If you reinstalled and the problem occured before adding the third party repos, then it probably isn't related to those.
sidenote: adding lots of third party repos isn't recommended anyway.
If it occured after upgrading to sid, then it probably relates to Sid.
Usually you also would test if a different user has the same problem (you just reinstalled, so pointeless here).
And test if a window-manager or a different DE also has problems.
Then you will know ( a bit ) more.

[piper]

All you need right now in sid is a little patience

You have the qt5-transition 30% done causing some problems and will have hell right now with plasma5

Last/this week some people were downgrading from systemd 240 back to 239 until a temp fix was found (this should help your slow starting session)

Code: Select all

From: Michael Biebl <biebl@debian.org>

For a (temporary) workaround you can create a file
/etc/security/limits.d/systemd.conf containing:

* hard nofile 524288

This will make pam_limits behave properly.

https://bugs.debian.org/cgi-bin/bugrepo ... =917167#37