Yousef, Canonical should and does notify people of known problems in the
release notes [1]. We only failed/forgot to mention this one and its
workaround in the release notes. Although scrolling up, it appears
nobody figured out what the workaround was until after 18.04 was
released. And even then o
Oh, Ubuntu does boot on such hardware just fine. And seeing how well it
works I'd feel guilty of wasting money and polluting the environment
when buying newer hardware.
It does not boot all up into native Wayland. Nevertheless, one can run
X11 just fine.
How to turn Wayland off? Key is to disable
I'm facing the same problem on my Intel Core 2 duo E8500 with G33
graphics Ubuntu 18.04 can't boot
shouldn't canonical at least notified us that Bionic Beaver doesn't work
on old hardware so no one tries it ??
--
You received this bug notification because you are a member of Desktop
Packages, wh
Also seen today on:
Core(TM)2 Duo CPU E8500 (bug 1780077)
and perhaps also:
Intel® Core™ i3-380M Processor (bug 1779888)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1727356
Tit
Maybe related:
https://gitlab.gnome.org/GNOME/mutter/issues/127
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1727356
Title:
Wayland sessions (including the login screen itself) don't
And:
Intel Core2 Duo E7200
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1727356
Title:
Wayland sessions (including the login screen itself) don't start up on
older Intel GPUs (pre
Also the original reporter:
Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1727356
Title:
Wayland sessions (including the login screen itself) do
Also recently seen on:
Intel(R) Core(TM)2 Duo CPU E6750 @ 2.66GHz
Intel(R) Pentium(R) M processor 1.86GHz
Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz
** Summary changed:
- Wayland sessions (including the login screen itself) don't start up on older
Intel GPUs.
+ Wayland sessions (including the
Bug confirmed by more users, including:
Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz
Intel(R) Atom(TM) CPU N550 @ 1.50GHz
This is reminiscent of bug 1583532, so we may need to review the shaders
used in mutter/clutter/cogl.
I now agree with "High" importance.
--
You received this bug notification be
** Summary changed:
- Wayland does not start up on "Integrated Graphics Chipset: Intel(R) G33":
Shader compilation failed
+ Wayland sessions (including the login screen itself) don't start up on older
Intel GPUs.
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** C
10 matches
Mail list logo
