[Bug 1727356] Re: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed
With 18.04 the situation got worse. Apparently, the login screen tries to run now on Wayland as well, so the opportunity to turn it off is gone. Booting simply stops at the Ubuntu logo, with the first of these five dots filled. Booting in recovery mode, then choosing 'continue'(?) gives a black screen most of the time, with some text blinking up shortly from time to time. Managed to catch it, see attached picture. The only way I could get this PC up running after the 18.04 upgrade was to boot into recovery mode, then get a root shell, then edit /etc/gdm3/custom.conf to remove the comment sign in front of WaylandEnable..., then reboot. ** Attachment added: "Screen photograph" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727356/+attachment/5134590/+files/DSCF1218.JPG -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1727356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727356] Re: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed
> "cannot open display" either means ... Thank you! This is valuable information. So far I thought that the bug is about gnome-shell not starting. With this solved, it's now mutter. Well, interesting adventure game :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1727356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727356] Re: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed
I fully agree this bug is valid and needs to be fixed. I only disagree with Sebastian's selection of High importance in the bigger picture. "cannot open display" either means it's an X app and XOpenDisplay failed (Xwayland isn't running because mutter failed to start). Or it means it's a native Wayland client and it can't start because mutter failed to start. Either way, "cannot open display" is an expected error that's a side-effect of this bug (mutter failed to start). But it's not the cause of this bug and not relevant. I have some older hardware laying around that might experience this or similar issues. So I'll try to get to testing it out before we're too far into the new year. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1727356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727356] Re: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed
Daniel, your current efforts apparently put much emphasis on alienating users capable of fixing bugs. Also on getting rid of allies for low end hardware support. I really wish you had put half as much efforts into explaining the software situation a bit. For example, what does this "cannot open display" mean? To my understanding, Wayland has no display server. What could get into the way of opening this display? How could one mimick a Wayland session from within a Xorg session? How could one start something Wayland-graphical from the recovery console (which is apparently the only way to get a command line without the display being occupied)? Elaboration on that would really help. And also fix bugs for these people believing that they need a dedicated graphics card. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1727356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727356] Re: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed
Let me emphasise that I have been the champion of supporting "older" hardware. I have spent weeks of my life just getting Mir working on the original Atom chips. And before that even trying to support Pentium 3's. But the decision isn't up to me. My work on Pentium 3 graphics was cut off by Mesa (v8.0?) dropping support for the hardware. And my work on the original Atoms is now also nullified by Ubuntu dropping support for 32-bit installations. I have tried really hard to make sure we can support everyone's hardware, but there are other opposing forces. On the simple matter of priorities though, I think we need to be paying more attention to Ubuntu 17.10's issues on Radeon and Nvidia hardware more than this. Simply because many more people are affected by those problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1727356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727356] Re: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed
Success, part II: When attempting a Wayland session, the relevant syslog section grew from 107 lines to 396 lines. 'gnome-shell' messages are gone, it looks like a session gets actually started. And then there are now a lot of messages like this one: Oct 31 18:08:01 piccard gnome-screensav[2194]: Anzeige kann nicht geöffnet werden: Oct 31 18:08:01 piccard org.gnome.SettingsDaemon.Power.desktop[2208]: Anzeige kann nicht geöffnet werden: Oct 31 18:08:01 piccard org.gnome.SettingsDaemon.Clipboard.desktop[2242]: Anzeige kann nicht geöffnet werden: "Anzeige kann nicht geöffnet werden" = "can't open display". So far no idea how this display should be set/activated/opened. ** Attachment added: "GDM-debug-shader-code-removed" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727356/+attachment/5001320/+files/GDM-debug-shader-code-removed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1727356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727356] Re: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed
Success! Applying the attached Diff keeps gnome-shell working for Xorg, still makes these shader compilation errors going away. More of this success see next comment here. This Diff is not a solution, of course, but it should narrow down the problematic area a lot. ** Patch added: "remove-shader-code.diff" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727356/+attachment/5001319/+files/remove-shader-code.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1727356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727356] Re: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1727356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727356] Re: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed
You should both be aware you're preaching to the converted. When we encountered these kinds of problems in Compiz/Mir/Unity8, I was the one fighting to keep old hardware supported and performing well. I will still fight to keep older hardware working well because there's no reason why the software should not work. I've been using OpenGL for 20 years so yes I know it should just work, and it should work efficiently. This is just a bug... My point is only that the bug will affect very few people, and we likely will never be able to get similar old hardware to test on, or can justify spending or money time on it. So probably not "High". Plus there is a workaround; just use "Ubuntu on Xorg". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1727356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727356] Re: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed
Having the default desktop not working on a class of hardware seems an High issue indeed, the GNOME bug tracker might be a better place to discuss it though since that's where the people working most on gnome- shell are more likely to read the comments ** Changed in: gnome-shell (Ubuntu) Importance: Medium => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1727356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727356] Re: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed
Intel integrated graphics is probably the most widely used PC graphics on this planet. The problem is apparently that shaders are called without being present, which applies to many most recent hardware platforms as well. Calling it High is more than accurate. Instead of trying to discuss the problem away it'd be much better to give instructions on how to find a way to actually solve the problem. To get an idea about what's going on I dedicated a full day on finding a starting point, but failed. Re-building gnome-shell from sources is a snap, but startup procedures are obfuscated enough to not allow a mere user to change or intercept it somehow. Instructions (or documentation pointers) on how to start up a Wayland session manually, without GDM, would be very helpful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1727356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727356] Re: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed
As the G33 graphics chipset is 10 years old it will be difficult for developers to find hardware to test on. And unlikely very many users will encounter the problem. We definitely want to fix this, but calling it High importance is probably not accurate. ** Changed in: gnome-shell (Ubuntu) Importance: High => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1727356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727356] Re: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed
** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1727356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727356] Re: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1727356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727356] Re: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed
apport information ** Tags added: apport-collected artful package-from-proposed third- party-packages ** Description changed: $ 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 ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1727356/+attachment/4996314/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1727356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1727356] Re: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed
** Changed in: gnome-shell Status: Unknown => Confirmed ** Changed in: gnome-shell Importance: Unknown => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727356 Title: Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33": Shader compilation failed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1727356/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
