Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
SDDM black screen when qtXXX-5.6.1 was installed
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
Lucipher
Tux's lil' helper
Tux's lil' helper


Joined: 11 Feb 2007
Posts: 77

PostPosted: Sun Jul 24, 2016 5:31 am    Post subject: SDDM black screen when qtXXX-5.6.1 was installed Reply with quote

I have been running KDE5/Plasma for quite while so far with no problems. Today I left my computer updating - there was a lot of QtXXX-5.6.1 to update - and when I got back I saw a black screen saying the locker had crashed and I would need to go to a terminal and type "loginctl session-unlock" to be able to unlock the session. Well, there was no loginctl command available. I thought my compilation was still going on, but after looking at my CPU usage I noticed the session had crashed completely. So, I tried
Code:
/etc/init.d/xdm restart


And got a black screen, no X was running. I thought of recompiling SDDM, but it did not help either. I got a message saying
Quote:
/lib64/security/pam_system.so not found


WTH! I've never installed Systemd on my computer, I checked my profile and it was the way it has always been
Quote:
default/linux/amd64/13.0/desktop/plasma *


Are you guys having the same problem? Or, have I done something wrong in this last update?

I had to move back to qtXXX-5.5.1(-r1) so I could get my Plasma desktop back running.
Any thoughts?
Back to top
View user's profile Send private message
papas
n00b
n00b


Joined: 01 Dec 2014
Posts: 73
Location: Athens

PostPosted: Sun Jul 24, 2016 8:45 am    Post subject: Reply with quote

Good morning, (perhaps this solve your problem)
https://forums.gentoo.org/viewtopic-p-7931932.html?sid=7df0ebad6f04ef8ea9ccafa0ca42866b
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6825
Location: Austria

PostPosted: Sun Jul 24, 2016 9:16 am    Post subject: Reply with quote

SDDM is not involved here.

Pro tip: Don't do Qt upgrades from inside your Plasma session.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
Lucipher
Tux's lil' helper
Tux's lil' helper


Joined: 11 Feb 2007
Posts: 77

PostPosted: Mon Jul 25, 2016 1:14 am    Post subject: Reply with quote

@genstorm,

Except for a glitch or two (dolphin/kterm not starting while update is going on), I never had any big problem updating Qt libraries while running KDE at the same time. And everything would get itself fixed after a reboot. This was the first time such mess happened to me, and I have been a Gentoo/KDE user since 2004!

I get that SDDM has nothing to do with this problem but Qt5.6.1, so why after installing all of the following packages and rebooting I couldn't get my Plasma session back to work?

Quote:
dev-qt/qtcore-5.6.1
dev-qt/qtxml-5.6.1
dev-qt/qtnetwork-5.6.1
dev-qt/qttest-5.6.1
dev-qt/qtconcurrent-5.6.1
dev-qt/qtpaths-5.6.1
dev-qt/qtxmlpatterns-5.6.1
dev-qt/qtsql-5.6.1
dev-qt/qtdbus-5.6.1
dev-qt/qtgui-5.6.1
dev-qt/qdbus-5.6.1
dev-qt/qtwidgets-5.6.1
dev-qt/qtx11extras-5.6.1
dev-qt/qtdeclarative-5.6.1-r1
dev-qt/qtsvg-5.6.1
dev-qt/qtscript-5.6.1
dev-qt/qtopengl-5.6.1
dev-qt/qtimageformats-5.6.1
dev-qt/qtgraphicaleffects-5.6.1


From the suggested list of updates what was left behind was
Quote:
dev-qt/qtwebkit-5.6.1 [5.5.1-r1]
dev-qt/qtquickcontrols-5.6.1 [5.5.1-r1]
dev-qt/qtprintsupport-5.6.1 [5.5.1]
media-libs/phonon-4.9.0 [4.7.2] ABI_X86="32%* (64%*) (-x32)"
media-libs/phonon-vlc-0.9.0 [0.7.2]
kde-frameworks/frameworkintegration-5.21.0
kde-apps/kde-wallpapers-15.08.3-r2 [15.08.3]


Does any of the above packages would fix the mess caused by the Qt5.6.1 in my OpenRC environment? If so, I'll give a try, else Qt-5.6.1 is broken.
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6825
Location: Austria

PostPosted: Mon Jul 25, 2016 6:11 am    Post subject: Reply with quote

Lucipher wrote:
...and rebooting I couldn't get my Plasma session back to work?

That is new information to me. Your first post sounded like it happened within your session, which does happen. Qt-5.6.1 is not broken, it should work a lot better than 5.5.1. Perhaps your system crashed in between building and you ended up with only a partial Qt 5.6.1 install?
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
Lucipher
Tux's lil' helper
Tux's lil' helper


Joined: 11 Feb 2007
Posts: 77

PostPosted: Mon Jul 25, 2016 6:07 pm    Post subject: Reply with quote

@genstorm

I've checked in the /vat/tmp/portage and the only package left there was dev-qt/qtwebkit-5.6.1, so I think is safe to assume all other packages previously installed were done properly. Unless login session does need one of those packages left behind like qtwebkit (hard to think it is related), kde-frameworks/frameworkintegration-5.21.0, or dev-qt/qtquickcontrols-5.6.1. What puzzles me most is the fact that pam_systemd.so not found. I have never installed Systemd in that computer.
Back to top
View user's profile Send private message
toralf
Developer
Developer


Joined: 01 Feb 2004
Posts: 3647
Location: Hamburg

PostPosted: Mon Jul 25, 2016 6:44 pm    Post subject: Reply with quote

Lucipher wrote:
@genstorm What puzzles me most is the fact that pam_systemd.so not found. I have never installed Systemd in that computer.
IIRC preceeding such a line with "-" suppresses an error message
Back to top
View user's profile Send private message
Lucipher
Tux's lil' helper
Tux's lil' helper


Joined: 11 Feb 2007
Posts: 77

PostPosted: Tue Jul 26, 2016 3:50 am    Post subject: Reply with quote

@toralf

I didn't get your point.
Back to top
View user's profile Send private message
Fitzcarraldo
Veteran
Veteran


Joined: 30 Aug 2008
Posts: 1633
Location: United Kingdom

PostPosted: Tue Jul 26, 2016 5:49 am    Post subject: Reply with quote

Lucipher wrote:
What puzzles me most is the fact that pam_systemd.so not found. I have never installed Systemd in that computer.

When I recently upgraded from KDE 4 to Plasma 5.5.5 in Gentoo Stable (with OpenRC, not systemd) I had that message too:

Code:
Jul 17 04:32:37 clevow230ss sddm-helper[3245]: PAM unable to dlopen(/lib64/security/pam_systemd.so): /lib64/security/pam_systemd.so: cannot open shared object file: No such file or directory
Jul 17 04:32:37 clevow230ss sddm-helper[3245]: PAM adding faulty module: /lib64/security/pam_systemd.so

and all I got was a black screen instead of the SDDM greeter. Despite having followed the upgrade instructions in the Gentoo Wiki and trying everything in the Gentoo Wiki to get SDDM to work, I had no success, so I switched to LightDM which works fine: https://forums.gentoo.org/viewtopic-p-7947104.html#7947104
_________________
Clevo W230SS: amd64 OpenRC elogind nvidia-drivers & xf86-video-intel.
Compal NBLB2: ~amd64 OpenRC elogind xf86-video-ati. Dual boot Win 7 Pro 64-bit.
KDE on both.

Fitzcarraldo's blog
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6825
Location: Austria

PostPosted: Tue Jul 26, 2016 3:11 pm    Post subject: Reply with quote

You can safely ignore the pam_systemd.so message.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
Lucipher
Tux's lil' helper
Tux's lil' helper


Joined: 11 Feb 2007
Posts: 77

PostPosted: Wed Jul 27, 2016 5:16 am    Post subject: Reply with quote

OK! I'll give another try this weekend.
Back to top
View user's profile Send private message
pallaert
n00b
n00b


Joined: 29 Apr 2005
Posts: 26

PostPosted: Wed Jul 27, 2016 12:47 pm    Post subject: Reply with quote

I'm having the exact same issue as you.

Upgraded yesterday from plasma 5.5 to 5.6 as well as kde-frameworks to 5.23.
This, in turn, upgraded qt from 5.5 to 5.6.

Some packages have been re-emerged by portage (no obvious reason, I haven't seen any new flag added) like: sddm, nvidia-drivers, systemd.

Since then: sddm shows a black screen only.

I am running Gentoo Linux with profile: default/linux/amd64/13.0/desktop/plasma/systemd with an nvidia card.
sddm worked well until now.

I checked the common stuff:

Code:
 $ groups sddm
video sddm


Code:
 $ ls -dla /var/lib/sddm/
drwxr-xr-x 4 sddm root 4096 10 avr 00:54 /var/lib/sddm/


Code:
$ sudo eselect opengl list
Available OpenGL implementations:
  [1]   nvidia *
  [2]   xorg-x11

_________________
Patrick ALLAERT
Open Source Web Developer
http://patrickallaert.blogspot.com/
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6825
Location: Austria

PostPosted: Wed Jul 27, 2016 3:33 pm    Post subject: Reply with quote

Check that /etc/sddm.conf exists and remove any mention of gles* in your USE flags, should there be any.
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
pallaert
n00b
n00b


Joined: 29 Apr 2005
Posts: 26

PostPosted: Wed Jul 27, 2016 4:04 pm    Post subject: Reply with quote

genstorm wrote:
Check that /etc/sddm.conf exists and remove any mention of gles* in your USE flags, should there be any.


I forgot to mention that /etc/sddm.conf already existed, I created it initially with:

Code:
sddm --example-config > /etc/sddm.conf


I checked the output of that command and diff'ed the result with my current /etc/sddm.conf and they are still identical.

I haven't added a gles/gles2 flag to my config, except for media-libs/mesa where "gles2" was used. I don't remember why I did that in the past, but I think it was to fix the "blank screen" issue I had at that time.

I already removed that flag and recompiled mesa and rebooted, but I keep having a black screen.

Using lightdm doesn't solve the issue, same black screen. I also tried to start "X" with startx, but there I have a black screen as well.
_________________
Patrick ALLAERT
Open Source Web Developer
http://patrickallaert.blogspot.com/
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 6825
Location: Austria

PostPosted: Wed Jul 27, 2016 4:06 pm    Post subject: Reply with quote

does it work when you switch to xorg-x11?
_________________
backend.cpp:92:2: warning: #warning TODO - this error message is about as useful as a cooling unit in the arctic
Back to top
View user's profile Send private message
pallaert
n00b
n00b


Joined: 29 Apr 2005
Posts: 26

PostPosted: Wed Jul 27, 2016 4:17 pm    Post subject: Reply with quote

Some suspicious (EE) lines from my /var/log/Xorg.0.log:

Code:

(EE) systemd-logind: failed to get session: PID 417 does not belong to any known session
...



When using "startx", I've had the following output, suggesting issues with dbus:

Code:

 $ startx
xauth:  file /home/patrick.allaert/.serverauth.18605 does not exist


X.Org X Server 1.17.4
Release Date: 2015-10-28
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.6-gentoo x86_64 Gentoo
Current Operating System: Linux steroid 4.4.6-gentoo #2 SMP Fri Jun 10 16:15:50 CEST 2016 x86_64
Kernel command line: init=/usr/lib/systemd/systemd root=PARTUUID=0B0A5AB4-4628-4E4C-AF35-F212EE31EE9C rootfstype=ext4 BOOT_IMAGE=/vmlinuz-4.4.6-gentoo root=/dev/sda3 ro drm_kms_helper.edid_firmware=edid/laptop.bin
Build Date: 27 July 2016  11:31:52AM

Current version of pixman: 0.32.8
        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: Wed Jul 27 18:07:46 2016
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Loading stage  "initial" 201
startkde: Starting up...
dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
Service started, version: 7.0.0

Baloo File Indexing has been disabled



^C <== Pressing CTRL+C here



xinit: connection to X server lost

waiting for X server to shut down klauncher: Exiting on signal 1
Fin de la connexion (raccroché)
GOT SIGHUP
Could not connect to D-Bus server: org.freedesktop.DBus.Error.Spawn.ExecFailed: /usr/bin/dbus-launch terminated abnormally with the following error: Autolaunch error: X11 initialization failed.

startkde: Shutting down...
kdeinit5_wrapper: Warning: connect(/run/user/1000/kdeinit5__0) failed: : No such file or directory
Error: Can not contact kdeinit5!
xprop:  unable to open display ':0'
xprop:  unable to open display ':0'
startkde: Done.
KCrash: Application 'kdeinit5' crashing...
KCrash: Attempting to start /usr/lib64/libexec/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0
Warning: connect() failed: : Aucun fichier ou dossier de ce type
KCrash: Attempting to start /usr/lib64/libexec/drkonqi directly
(II) Server terminated successfully (0). Closing log file.

xinit: unexpected signal 2


And the Xorg.0.log contained after using startx the following (EE) entries:

Code:

[  6958.412] (EE) systemd-logind: failed to take device /dev/dri/card1: Operation not permitted
[  6958.412] (II) xfree86: Adding drm device (/dev/dri/card0)
[  6958.412] (EE) systemd-logind: failed to take device /dev/dri/card0: Operation not permitted
...
[  6958.702] (EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X
[  6958.702] (EE) NVIDIA(0):     log file that the GLX module has been loaded in your X
[  6958.702] (EE) NVIDIA(0):     server, and that the module is the NVIDIA GLX module.  If
[  6958.702] (EE) NVIDIA(0):     you continue to encounter problems, Please try
[  6958.702] (EE) NVIDIA(0):     reinstalling the NVIDIA driver.
...
[  6959.622] (EE) AIGLX: reverting to software rendering
...
[  6959.678] (EE) systemd-logind: failed to take device /dev/input/event10: Operation not permitted


This makes me think that the problem is not at sddm level, but rather somewhere between systemd, Qt and Xorg...
_________________
Patrick ALLAERT
Open Source Web Developer
http://patrickallaert.blogspot.com/
Back to top
View user's profile Send private message
pallaert
n00b
n00b


Joined: 29 Apr 2005
Posts: 26

PostPosted: Wed Jul 27, 2016 4:19 pm    Post subject: Reply with quote

genstorm wrote:
does it work when you switch to xorg-x11?


Nope, I did that too and also tried with eselect qtgraphicssystem set to "native" but I came back to "raster (default)", no results :(
_________________
Patrick ALLAERT
Open Source Web Developer
http://patrickallaert.blogspot.com/
Back to top
View user's profile Send private message
Lucipher
Tux's lil' helper
Tux's lil' helper


Joined: 11 Feb 2007
Posts: 77

PostPosted: Sun Jul 31, 2016 10:53 pm    Post subject: Reply with quote

Follow up. I've tried this weekend again and this time all worked just fine. I did notice that this time more packages came along, including sddm-kcm. Anyways, this time it went through without major issues.
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