Great to see you're into supporting "old" hardware. I'm pretty sure the times when people bought new hardware every other year are long gone. This G33 PC is a Core2Duo 2.1 GHz and it's perfectly up to speed for all the daily tasks, including software development.
"Older" hardware also comes with advantages. Just try to get something like CoreBoot running on recent hardware - it won't work. There's a reason why many hackers still use IBM ThinkPads. And then there's the observation that newer hardware isn't all high end. Instead of faster and faster hardware, newer trends go into smaller form factors and shared hardware. Think of MiniITX boards, Raspberry Pis, BeagleBones or virtual machines. They do what they're expected to do and some have no OpenGL at all. Certainly they should be able to run Ubuntu. Xorg is expected to go away, so Wayland bugs have to be fixed sooner or later. Back to the bug: having more capable hardware might even be an advantage for solving this bug. If OpenGL features shaders, one can turn this feature off, but one can't turn it on on hardware not featuring shaders. ... and I'm not too sure about the last one. Mesa has software renderers. I've searched for the error messages logged: $ grep -rn 'linking with uncompiled shader' /usr Binary file /usr/lib/i386-linux-gnu/dri/r200_dri.so matches Binary file /usr/lib/i386-linux-gnu/dri/nouveau_vieux_dri.so matches ... 13 of 18 drivers existing in each, i386 and x86_64, match, including i915 and i965. I've looked into gnome-shell sources. To my surprise I found not kind of a traditional application there, but lots of CSS and JavaScript. Not too bad, I'm fairly good at web development. Next plan is to remove all code which mentions 'shader' in the C sources and see whether this makes the error messages going away. And if somebody happens to know whether this JS stuff can use shaders, too, please let me know. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Triaged Bug description: $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 Upgraded from 17.04 today. Steps to reproduce: - Start the PC or log out/end session in case it's running with an Xorg desktop already. - Attempt to log in, using 'Ubuntu' Expected to happen: Desktop appears. Actually happening: 5 seconds of black screen, then the login screen appears again. Partial diagnosis: - Logging in using 'Ubuntu on Xorg' works fine and as expected. - Extracted a syslog of such a failed attempt, see attached file. --- ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2016-05-04 (539 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Package: gnome-shell 3.26.1-0ubuntu5 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Tags: artful package-from-proposed third-party-packages Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: Upgraded to artful on 2017-10-25 (0 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1727356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
