Comment # 8 on bug 1008677 from
(In reply to Markus Elfring from comment #7)
> (In reply to Wolfgang Bauer from comment #4)
> > SDDM crashes with a segfault if Xorg cannot be started.
> 
> I was not really aware about this software behaviour before.
> Do any more bug reports exist for such a detail?

Yes, https://github.com/sddm/sddm/pull/725 as you mentioned yourself.

And that should be fixed in the next Tumbleweed update, as I wrote.

> > the main one is that Xorg doesn't start in the first place
> 
> I am curious about further corresponding failure reasons.

As I already tried to explain to you half a year ago in the openSUSE Forums and
you were also told in your bug report about xdm, this is to be expected after
every major update to the kernel, Xorg or Mesa.

You need to reinstall the nvidia driver afterwards.

> > We do not support "special software combinations"...
> 
> I got an other impression on how automatic quality assurance could
> eventually improve the situation also around the evolution of components
> from openSUSE Tumbleweed.

Tumbleweed is tested, but only the software that is included.
If you use "special software combinations", you are on your own.

And especially the nvidia driver is not tested, nor supported, by openSUSE.
It is explicitly *not* recommended to use it on Tumbleweed.

You may do so, but you are on your own.

You will have to reinstall it after cerain updates as mentioned, and it may not
even work because it may not support the latest kernel or Xorg versions.

But I already told you this half a year ago.
And it's unrelated to SDDM or KDE at all.

> > is just "cosmetical".
> 
> I imagine that the added destructor can prevent further hiccups, can't it?

Yes, and it has been done.
But it won't fix the problem that Xorg fails to start, it will (or should) only
fix SDDM's segfault.
Nothing more can be done from SDDM's side.

Oh, and it would probably be a nice gesture from your side if you re-checked
the other displaymanagers you filed bug reports about (see comment#2), and
close those bug reports yourself if they work after you fixed your nvidia
installation.

I very much doubt that all (or anyone) of them are broken... ;-)


You are receiving this mail because: