On Monday 2016-06-20 22:48, Dominique Leuenberger / DimStar wrote:
it shows that barely any developer and maintainer is using i586 systems anymore: once again, the snapshot is basically ready but fails on i586 tests (not exactly as bad as last time around, when the kernel would not even boot)
This time, it's 'just' KDEs screenlocker that is crashing
The i686 machinery I still have or are in purview of is servers which will pretty much never run KDE, and only X very little (via ssh -X).
How is the feeling amongst i586 users? Shall I hold this snapshot back until the KDE Team can potentially find out what's wrong (I don't think there is currently any lead, so this can be a long wait).
Unless it's a systematic issue -- kernel, libc or runtimes like perl as a whole and messing up the layers above it --, it almost always turns out to be some original and software-specific error. Unaligned access, shitty thread locking, you name it. As a die-hard developer, I would want to know about all bugs in my own software. But who knows where KDE's priorities are :) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org