s/when started from another DM/when started/

(not sure I really tried again from another DM since sddm works well!)

Should not be in bugzilla but in our errata if there's nothing we can fix IMHO.
Also according to upstream this particular bug should be fixed in 0.13, can you still reproduce in cauldron?

Assignee: bugsquad => doktor5000
CC: (none) => doktor5000
Hardware: i586 => All

(In reply to Florian Hubold from comment #2)
> Should not be in bugzilla but in our errata if there's nothing we can fix
> IMHO.

Well, I was hoping for an upstream fix :-)
(And we don't start filling the errata this early in the development cycle)

> Also according to upstream this particular bug should be fixed in 0.13, can
> you still reproduce in cauldron?

Thanks for having spotted that. There is no way I can test, because this system is now affected by bug 17221 (sddm-greeter: Failed to create OpenGL context for format QSurfaceFormat), even on bare metal.

Assuming it's fixed, though, since you already pushed sddm-0.13.0 over a month ago.

Resolution: (none) => FIXED
Status: NEW => RESOLVED

(In reply to Marja van Waes from comment #3)
> (In reply to Florian Hubold from comment #2)
> > Should not be in bugzilla but in our errata if there's nothing we can fix
> > IMHO.
> 
> Well, I was hoping for an upstream fix :-)
> (And we don't start filling the errata this early in the development cycle)

development cycle? - that would have also affected mga5, so not early :p

> Assuming it's fixed, though, since you already pushed sddm-0.13.0 over a
> month ago.

Please reopen if it reoccurs.

(In reply to Florian Hubold from comment #4)
> (In reply to Marja van Waes from comment #3)
> > (In reply to Florian Hubold from comment #2)
> > > Should not be in bugzilla but in our errata if there's nothing we can fix
> > > IMHO.
> > 
> > Well, I was hoping for an upstream fix :-)
> > (And we don't start filling the errata this early in the development cycle)
> 
> development cycle? - that would have also affected mga5, so not early :p

:-)

Mga6 development cycle

> 
> > Assuming it's fixed, though, since you already pushed sddm-0.13.0 over a
> > month ago.
> 
> Please reopen if it reoccurs.

after commenting
    Option "DRI"  "false"

it occurs again.

sddm-greeter segfaults and before that the "sddm-greeter qopenglshader: could not create shader" that made me find the upstream bug report, is still there.

I'll attach journalctl -b and Xorg.0.log (no errors, only one warning) later

Resolution: FIXED => (none)
Status: RESOLVED => REOPENED

Created attachment 7286 [details]
journalctl -b output

Created attachment 7287 [details]
Xorg.0.log

In reply to (on IRC):

> 2015:12:17:16:00 < doktor5000> marja: for 
>                  https://bugs.mageia.org/show_bug.cgi?id=16544 - if you run
>                  startx do you get a normal X session ?

I never use startx, so don't know what is normal.

The following is all with 
   #    Option "DRI"  "false"
instead of
        Option "DRI"  "false"
:
 
When I run startx as root it starts an IceWM session as root (it looks normal to me, the background is red as it should be for root). 

When I run startx as normal user, then xinit loses the connection to X server.

When I use lightdm, then I can login to XFCE as normal user. 
However, I don't manage to login to anything else than XFCE, no matter how I try to toggle the "XF" button in the lightdm screen (nor left nor right clicking work)

and XFCE works fine, then :-)

Bug 19798 seems to be about the same issue, and was also in a 32bit installation.

I'm hoping for some more information in that bug report than is available now.


Reassigning this bug to kde-team, since neoclust / kde team now maintains SDDM

Summary: sddm shows nothing but a black screen (and the mouse cursor) => sddm shows nothing but a black screen & cursor (sddm-greeter: QOpenGLShader: could not create shader)
Assignee: doktor5000 => kde

Still valid for Mageia-6-sta2-i586-DVD.iso of December 16.

After adding 

    Option "DRI"  "false"


again, SDDM and Plasma5 start fine

Still valid for Mageia-6-sta2-LiveDVD-Plasma-i586-DVD.iso of January 6 
(from mageia6-pretesting, but it'll probably be made available for all QA testers, soon)

*** Bug 19798 has been marked as a duplicate of this bug. ***

CC: (none) => swbutler38

Upgraded a mga5 1586 which was uptodate with updates using the online upgrade path to the released mga6. It booted to a back screen with a blinking cursor.

If I used a ALT-F2 login to root and drakdm changed to xdm I got a x greeter. Here I could login and got an icewm session. Running a terminal here I could run startkde and get the normal login plasma session.

Searching through journal logs I found error messages saying "no user sddm".

Searching online I found threads saying that user sddm had to be added to the video group.

So I did an "adduser sddm" and an "usermod -a -G video sddm", then a drakdm to reselect sddm and then rebooted. Everything was fine and dandy.

So for my online upgrade i586 mga5 to mga6 somewhere sddm user and group membership was not setup correctly.

Hope this helps.

CC: (none) => phil

I can't tell whether this bug is still valid, because I do no longer have the ThinkPad R50e which suffered from it.

@ Herman

Do you know whether SDDM now works in current cauldron on that laptop without needing the workaround from comment #0 (so from the Description)?

CC: (none) => herman.viaene

I very much doubt I can test this as the regular M7 iso can be installed but does not boot unless in recovery mode.

This is not fixed upstream and seems to be stale for a while. They commented about bad videos drivers with old graphic cards.

Unsure what to do with this 6 years bug report.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution and even upgrading their hardware, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

Status: REOPENED => RESOLVED
Resolution: (none) => OLD
CC: (none) => ouaurelien