http://bugzilla.opensuse.org/show_bug.cgi?id=1027691 http://bugzilla.opensuse.org/show_bug.cgi?id=1027691#c1 Fabian Vogt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt@suse.com Component|Usability |KDE Workspace (Plasma) Assignee|bnc-team-screening@forge.pr |opensuse-kde-bugs@opensuse. |ovo.novell.com |org --- Comment #1 from Fabian Vogt --- Please upload your ~/.xsession-errrors-:0. It should contain some valuable logging information. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1027691 http://bugzilla.opensuse.org/show_bug.cgi?id=1027691#c3 --- Comment #3 from Wolfgang Bauer --- PS, for reference see also this mailing list thread on plasma-devel: https://mail.kde.org/pipermail/plasma-devel/2017-January/064733.html And https://bugs.kde.org/show_bug.cgi?id=374023 In particular:

I'm sorry but your hardware is no longer supported. The error message thrown from a component we depend on is: "This program requires an X86 processor that supports SSE2 extension, at least a Pentium 4 or newer"

-- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1027691 http://bugzilla.opensuse.org/show_bug.cgi?id=1027691#c5 --- Comment #5 from Josh Zimmerman --- Of course I don't use an autologin usually, because it's unsecure so If I recall right; something about loading the login user selection screen made it to where I couldn't load the Desktop again. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1027691 http://bugzilla.opensuse.org/show_bug.cgi?id=1027691#c7 --- Comment #7 from Wolfgang Bauer --- (In reply to Josh Zimmerman from comment #6)

Well; I tried to load Tumbleweed 201660613 i586 onto this machine and it threw and error at startup of installation.

The error given to me was: Internal Error. Please report a bug report with logs.

Then please do that in a different bug report against the installer, with those logs. See also https://en.opensuse.org/openSUSE:Report_a_YaST_bug As YaST uses Qt5, it may be related, or not. So you may want to provide a link to this bug report too. At least you should definitely specify that you are trying to install on an old AMD CPU without SSE2 support. According to the error message, it might as well be ruby that doesn't support SSE1-only either meanwhile. Or it might be a completely different problem... But in any way, the KDE team is not responsible for such installation problems in the first place. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1027691 http://bugzilla.opensuse.org/show_bug.cgi?id=1027691#c9 --- Comment #9 from Josh Zimmerman --- I tried to submit the bug backtrace information, but there is already a duplicate on KDE's website. I don't recall what the title of the bug was though. Used to; I couldn't even do that, because the debugging stuff wouldn't install, but it went smoother this time and I did see the message about SSE2, but what I can never figure out is why people take things and make them obsolete so that older hardware can't work if it isn't not impacting anything significantly enough to need removal. In other words; why remove old drivers if they are not taking up too much space? Why remove old kernel modules if they are not affecting the operating system in a negative way? Why remove support for old hardware if it's not hurting anything? Least of all; Why remove support for SSE1 in the QT package if there was already a patch that made it work? I recall having to recompile the kernel once to turn on support for parallel port scanners. To me; it seems like removing support for things that are already there and working properly just cause more headaches than would happen if you just let them be in the installation or configuration of SUSE. Like 32 bit installations of OpenSUSE is obsolete. I recall thinking that, but was there really a reason to remove support for 32 machines that was too time consuming to spin a release of the 32-bit versions? The only things I think that should be removed and be made obsolete are bugs that prevent any software or hardware from working properly and if the bug fix causes a regression; fix that with everything enabled. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1027691 http://bugzilla.opensuse.org/show_bug.cgi?id=1027691#c11 --- Comment #11 from Wolfgang Bauer --- (In reply to Josh Zimmerman from comment #10)

Created attachment 718720 [details] This is my xsession file.

This confirms the cause of your problems at least. I have bad news for you though: Apparently Tumbleweed doesn't even boot any more without SSE2, see bug#1032165. If that's true in general and SSE2 is now "officially" required, trying to get Qt5 (or Plasma) to works without it would just be a waste of time. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1027691 http://bugzilla.opensuse.org/show_bug.cgi?id=1027691#c13 --- Comment #13 from Wolfgang Bauer --- (In reply to Josh Zimmerman from comment #12)

I wonder if this has anything to do with it:

Nouveau DRI/3d Mesa-dri-nouveau is installerd while it has known issues with the KDE display environment especially.

I don't see how. As mentioned, QtQuick (and Plasma5 therefore) requires SSE2 currently, regardless of the graphics driver in use (AFAIK). You can of course try to uninstall Mesa-dri-nouveau and see if it helps, but I don't think it will. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1027691 http://bugzilla.opensuse.org/show_bug.cgi?id=1027691#c15 --- Comment #15 from Wolfgang Bauer --- (In reply to Josh Zimmerman from comment #14)

How do I get that patch for SSE2?

I had a look, and it seems we do still ship a SSE1-only version of qtbase (libQt5Core5 and libQt5Gui5). But libqt5-declarative (QtQuick) requires SSE2 nowadays as mentioned. The previous patch (that got removed in 5.6.0) is here: https://build.opensuse.org/package/view_file/KDE:Qt5/libqt5-qtdeclarative/sse2_nojit.patch?expand=0&rev=f59267527b66226a15e1636a61496260 AFAICS it basically disables the JIT compiler, and "downgrades" the error message to a warning. Whether that would still work or not is a different question though. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1027691 http://bugzilla.opensuse.org/show_bug.cgi?id=1027691#c17 --- Comment #17 from Josh Zimmerman --- Created attachment 723223 --> http://bugzilla.opensuse.org/attachment.cgi?id=723223&action=edit Bug Info Output This is the bug information output after logging in. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1027691 http://bugzilla.opensuse.org/show_bug.cgi?id=1027691#c19 --- Comment #19 from Wolfgang Bauer --- Sorry, I somehow "forgot" to actually apply the patch. (TBH, it did surprise me a bit that the package built fine just like that...) Fixed now, I had to adjust the patch slightly but managed to get it to build. Please try again with the latest package from the same place. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1027691 http://bugzilla.opensuse.org/show_bug.cgi?id=1027691#c21 --- Comment #21 from Josh Zimmerman --- Worked under Plasma5 session login also. Thanks :) The way I feel about all this is that there is no reason to take away functionality just because something is old like I recall one time I had to recompile the Kernel just to turn on Parallel Scanner support. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1027691 http://bugzilla.opensuse.org/show_bug.cgi?id=1027691#c23 --- Comment #23 from Wolfgang Bauer --- (In reply to Josh Zimmerman from comment #21)

Worked under Plasma5 session login also. Thanks :) The way I feel about all this is that there is no reason to take away functionality just because something is old like I recall one time I had to recompile the Kernel just to turn on Parallel Scanner support.

We did not take away functionality. Qt just does not support SSE1-only CPUs any more in Qt5. Adding that would mean to rewrite the Javascript JIT engine from scratch and maintain two completely different versions. The Qt developers are not willing to do that. See also the discussion here: https://bugreports.qt.io/browse/QTBUG-35430 The only option is to actively disable the JIT engine on build time and only use the run-time interpreter, which is of course slower, but you also need to patch it to not abort if it detects SSE2 missing. As I wrote, I do not know why that patch got removed in our package, I'm actually not really involved in Qt packaging. The patch does have a downside though: the lib needs to be compiled *twice*, with and without SSE2, to not cause performance degradation on 32bit systems with SSE2 support (including 32bit apps on 64bit systems). (In reply to Josh Zimmerman from comment #20)

I think you should include this in the stable release if it works for more than just me.

I think your confirmation is sufficient, I noticed that Fedory does still have basically the same patch in their latest qtdeclarative package (they remove the error message completely though). I submitted the "fixed" package to the devel project, let's see if it gets accepted. https://build.opensuse.org/request/show/494707 (In reply to Josh Zimmerman from comment #22)

Until I did a distribution upgrade. It quit working for some reason.

Running "zypper dup" will reinstall the original version included in the distribution (which requires SSE2). You should be able to lock the package ("Taboo" in YaST or "zypper al libQtQuick5") to prevent that. Or add the posted link as repo, with a higher priority if you want to be "safe". -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1027691 http://bugzilla.opensuse.org/show_bug.cgi?id=1027691#c25 --- Comment #25 from Wolfgang Bauer --- FYI, the change is in the standard Tumbleweed repos now, together with the update to Qt 5.9.0. I deleted my test package therefore, you shouldn't need it any more (and it would likely cause problems as it is version 5.7.1). -- You are receiving this mail because: You are on the CC list for the bug.