Description of problem: I make a minimal installation of cauldron: - deselect all package - then select "with X' and deselect 'with suggests' - I reboot with xdm and IceWM Then, install sddm and modify the display manager with MCC By reboot, I have well the screens of grub and plymouth, then the black screen, without prompt. I verify systemd-cgls => prefdm.service => 645 /usr/bin/sddm -nodaemon Thanks to the indications of Jüri Ivask, I make systemctl disable prefdm.service && systemctl enable sddm.service I always fall again on a black screen I verify systemd-cgls => sddm.service => 636 /usr/bin/sddm Version-Release number of selected component (if applicable): sddm-0.9.0-6 Reproducible: Steps to Reproduce:
Assignee: bugsquad => mageia
it's better to keep sddm.service disabled. and prefdm.service enabled. but, (and this only related to systemd minimal install), you still have to set systemctl set-default graphical.target that should get you going. i myself am testing with minimal install too... it's not because you install with X, that grahical boot should be default.
CC: (none) => alien
I redid a new installation, always in the same way. I restart with xdm and IceWM Then, install sddm and modify the display manager with MCC. I left prefdm.service. In the restart, always black screenI verify at first: /etc/systemd/system/default.target. The link => runlevel5 The graphic server is thus already activated. What is normal because I installed by IceWM.
Anything in the logs at the time where sddm should be started? In either ~/.xsession-errors or seen via journalctl -b ? systemctl status sddm doesn't show anything in the log section? What's of sddm the status at that time ?
CC: (none) => doktor5000
Created attachment 5402 [details] journalctl -b | tail -50 output after sddm start I've just checked, and here sddm seems to segfault, probably some issues with libc or the virtualbox opengl extensions. Maybe it just needs a rebuild? From what I remember, it worked just fine some weeks back.
Created attachment 5403 [details] The same journal, on my computer We notice that the graphical interface is launched. But it is never question of sddm. A little later, I opened a console root
Created attachment 5404 [details] ps waxf The reading of ps waxf also gives information. /usr/bin/sddm -nodaemon is launched, but no sddm-greeter
I have just redone a try. I installed the Xfce desktop from the DVD Mga5 alpha2. I then made the update of the packages. I installed sddm with MCC. I configure DM with MCC and reboot. => Display Grub: OK Display plymouth: OK Then: black screen, w/o prompt. => Ctrl+Alt+F2, login root journalctl -b | tail -150 => sddm:[713]: Initializing ... sddm[713]: Still 3 times this line without information sddm[713]: Starting sddm[713]: Still 15 times this line without information You can deduct something from it?
Source RPM: sddm-0.9.0-6 => sddm-0.9.0-6, sddm-0.9.0-9
I wonder if the problem is not bound to the processor type : Athlon XP (w/o sse2). I have a problem with adminpanel-qt while adminpanel-gtk work. It would be necessary to verify if the different lib of qt5 use the instructions sse2. It seems that debian had problems with qt5. See http://metadata.ftp-master.debian.org/changelogs//main/q/qtbase-opensource-src/qtbase-opensource-src_5.3.2+dfsg-4_changelog "Add support for non-sse2 processors (Closes: #754894)." (Debian) Is this option used at Mageia?
Summary: Sddm does not work with a minimal installation => Sddm does not work with a older processor
I cannot reproduce with latest sddm. But for reference, here's a link to the Debian discussion thread, seems the problem exists since QT 5.3 enabled SSE2 by default. https://lists.debian.org/debian-qt-kde/2014/07/msg00169.html Bugreport: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754894 Relevant Fedora commit: http://pkgs.fedoraproject.org/cgit/qt5-qtbase.git/commit/?id=d68f9fa0b8ef163fc9a4a4e7699b5f777bb64423 Bugreport: https://bugzilla.redhat.com/show_bug.cgi?id=1103185 @KDE team: WDYT?
CC: (none) => lmenutSummary: Sddm does not work with a older processor => Sddm crashes with an older processor without SSE2 - QT5 >= 5.3 requires SSE2 by default
Depends on: (none) => 14418
*** Bug 14491 has been marked as a duplicate of this bug. ***
(In reply to Florian Hubold from comment #9) > Relevant Fedora commit: > http://pkgs.fedoraproject.org/cgit/qt5-qtbase.git/commit/ > ?id=d68f9fa0b8ef163fc9a4a4e7699b5f777bb64423 > Bugreport: https://bugzilla.redhat.com/show_bug.cgi?id=1103185 > > @KDE team: WDYT? My svn diff for qtbase5 is currently as follows: ââ[user1@localhost]â[17:18:04]â[~/qtbase5] ââââ¼ svn diff Index: SPECS/qtbase5.spec =================================================================== --- SPECS/qtbase5.spec (revision 793492) +++ SPECS/qtbase5.spec (working copy) @@ -1189,6 +1189,9 @@ %else -no-sql-odbc \ %endif +%ifarch %{ix86} + -no-sse2 \ +%endif %if %without docs -nomake docs \ -nomake demos \ Although I only have a VM for testing, and building QT5 would take ages there ...
Assignee: mageia => lmenutSource RPM: sddm-0.9.0-6, sddm-0.9.0-9 => qtbase5CC: (none) => mageia
*** Bug 14418 has been marked as a duplicate of this bug. ***
*** Bug 14229 has been marked as a duplicate of this bug. ***
Assignee: lmenut => mageia
Should be fixed with http://svnweb.mageia.org/packages?view=revision&revision=799846 and qtbase5-5.3.1-7.mga5 packages. SSE2 is disabled per default on i586/%ix86, and an SSE2-enabled library is located in %{_qt5_libdir}/sse2/ . Please test once the -7.mga5 packages hit your mirror.
See Also: (none) => https://bugreports.qt-project.org/browse/QTBUG-35430, http://bugs.debian.org/754894, https://bugzilla.redhat.com/show_bug.cgi?id=1103185Assignee: mageia => doktor5000
Hello Florian, I tested this morning. I updated my local mirror. I installed with the CD stemming from the last boot-nonfree.iso. I chose the LXQT environment. The installation is made with no problem. But sddm does not still display (black screen, without prompt). It may be necessary to recompile sddm with the news libs ?
You lack basic information. Did you verify that the newer QT packages are installed? Did you check why sddm did not start? systemctl status sddm "journalctl -b | tail -50" output after sddm start
Created attachment 5672 [details] journalctl Hello, I did not have time to make other investigations yesterday. Yes the newer lib are installed Ex. libqt5coe5-5.3.1-7.mga5 I had to make tail -200 to have the information on sddm It is in attachment.
Can't see any issues, filtered output by sddm, here's the relevant excerpt déc. 01 09:14:31 sauve sddm[676]: Greeter starting... déc. 01 09:14:32 sauve sddm-helper[1001]: [PAM] Starting... déc. 01 09:14:32 sauve sddm-helper[1001]: [PAM] Authenticating... déc. 01 09:14:32 sauve sddm-helper[1001]: [PAM] returning. déc. 01 09:14:32 sauve sddm-helper[1001]: pam_unix(sddm-greeter:session): session opened for user sddm by (uid=0) déc. 01 09:14:32 sauve systemd-logind[602]: New session c1 of user sddm. déc. 01 09:14:32 sauve systemd[1014]: pam_tcb(systemd-user:session): Session opened for sddm by (uid=0) déc. 01 09:14:32 sauve sddm[676]: Greeter session started successfully déc. 01 09:14:33 sauve sddm-helper[1001]: [PAM] Ended. déc. 01 09:14:33 sauve sddm[676]: Auth: sddm-helper exited successfully déc. 01 09:14:33 sauve sddm[676]: Greeter stopped.
Status: NEW => ASSIGNED
CC: (none) => anaselli
I have now the second computer of test, equipped with a processor supporting. SSE2. I can so compare both behavior. On the computer with support of SSE2, I stopped when sddm is shown, without connecting me. On both machines I pass then to terminal2 (Ctrl+Alt+F2). Systemd-cgls sends back the same output, with exactly the same commands. There is every time prefdm.service with /usr/bin/sddm -nodaemon and /etc/X11/X :0 ... I then redid searches on the Internet and I found : sddm-greeter --test-mode --theme /usr/share/sddm/breeze And this command gives: GREETER : This program requires an x86 processor that suports SSE2 extension. Abandon. Here is thus the culprit. Nota bene : If I use xdm to connect, LXQt works on this computer. A good news to start 2015 !!!
(In reply to Georges Eckenschwiller from comment #19) > I then redid searches on the Internet and I found : > sddm-greeter --test-mode --theme /usr/share/sddm/breeze > And this command gives: > GREETER : This program requires an x86 processor that suports SSE2 > extension. Abandon. Thanks a lot, so now that's an easily reproducible test case. But now it seems not of a QT issue, but that sddm really requires/enforces SSE2, we cannot really fix that.
Hello, Florian I think in the same way. For my old computer I shall use xdm. I am going to close this report.
Resolution: (none) => WONTFIXStatus: ASSIGNED => RESOLVED
i'm curious, what kind of machine doesn't support SSE2?
(In reply to AL13N from comment #22) > i'm curious, what kind of machine doesn't support SSE2? See the linked QT bugreport for a lengthy discussion upon that, including some specific models, like some older AMD processors that are pretty widespread.