** No longer affects: mesa (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1723577
Title:
Artful won't start with Wayland activated (AMD?)
To manage notifications
This bug was fixed in the package gnome-shell - 3.26.1-0ubuntu4
---
gnome-shell (3.26.1-0ubuntu4) artful; urgency=medium
* revert_023b50e7a7002226d6176bede22930d96da074a9.patch,
revert_5c37facc083078564faaeec4aa58084857c56ee1.patch,
and comment
** Bug watch added: GNOME Bug Tracker #789153
https://bugzilla.gnome.org/show_bug.cgi?id=789153
** Also affects: gnome-shell via
https://bugzilla.gnome.org/show_bug.cgi?id=789153
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member
** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1723577
Title:
Artful won't start with Wayland activated (AMD?)
To
Yes, I donwgraded in chroot Gnome Shell to this version :
https://launchpad.net/ubuntu/+source/gnome-shell/3.26.0-0ubuntu2/+build/13517504
After it boots normally and I get the login screen, then the Ubuntu
Gnome Shell session, all works.
Developers are testing commits: I tried the 2 here
So with this gnome-shell downgrade you can get past Plymouth into GDM
reliably? I will try at home as well...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1723577
Title:
Artful
So with this gnome-shell downgrade you can get past Plymouth into GDM
reliably? I will try at home as well...
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1723577
Title:
Artful
Tried to downgrade Gnome Shell :
sudo dpkg -i gnome-shell_3.26.0-0ubuntu2_amd64.deb gnome-shell-
common_3.26.0-0ubuntu2_all.deb
root@ubuntu:/home/GShell# sudo dpkg -i gnome-shell_3.26.0-0ubuntu2_amd64.deb
gnome-shell-common_3.26.0-0ubuntu2_all.deb
dpkg: avertissement: dégradation (« downgrade
My home is encrypted (ecryptFS) so gdm can't access to
~/.config/monitors.xml
There is not another one :
root@ubuntu:/# sudo updatedb
root@ubuntu:/# locate monitors.xml
root@ubuntu:/#
I added to /etc/environment :
export MUTTER_VERBOSE=1
export MUTTER_VERBOSE=1
export MUTTER_DEBUG=1
export
And the last syslog...
** Attachment added: "Syslog4"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1723577/+attachment/4974766/+files/Syslog4
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
** Changed in: gdm3 (Ubuntu)
Importance: High => Critical
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1723577
Title:
Artful won't start with Wayland activated (AMD?)
To manage
amano@amano-desktop:~$ uname -r
4.14.0-rc5-lp1723619+revert
So the revert there in the patched 4.14 kernel doesn't affect me :(
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1723577
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723619 is (sadly)
not my issue. It took again 4 tries to have GDM appearing :(
Having me regress at the same time as the many ATI users seems too much
of an incident.
--
You received this bug notification because you are a member of Ubuntu
In /etc/gdm3/custom.conf, on [debug] section, I activated Enable=true,
here is the complete startup log.
But following command didn't work in chroot (to get more infos from gdm)
:
root@ubuntu:/# sudo journalctl -b -u gdm
No journal files were found.
-- No entries --
** Attachment added:
After having also downgraded libdrm (of course I did not reapply updates
on my main system after other reverts), it still doesn't start and stays
at Ubuntu screen (UID 121)...
Logs attached to help.
** Attachment added: "Libdrm"
** Attachment added: "Syslog2"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1723577/+attachment/4973287/+files/Syslog2
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1723577
A new idea: libdrm was also upgraded on 5 October:
https://launchpad.net/ubuntu/+source/libdrm/2.4.83-1
That might cause this problem since it provides:
libdrm-amdgpu1
So try downgrading to:
https://launchpad.net/ubuntu/+source/libdrm/2.4.82-1/+build/13171669
--
You received this bug
Daniel, sorry, I did not complete my post after #18 and apt policy
result - we were discussing with didrocks and frenchy82 on the French
forum with the details, I tried to resume here all steps in order other
people and developers involved in bug also got the informations.
i've tested to revert mesa AND mutter but didn't help
** Attachment added: "mesa"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1723577/+attachment/4973252/+files/mesa
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in
Thanks. We can /probably/ exclude Mesa then.
Next I would suggest downgrading mutter which is used to render gdm3
(and because the 3.26.1 release happened at the time of the bug too) but
comment #21 seems to suggest that's already been tried.
Still, we can't definitively exclude Mesa or Mutter
I've made too the revert to mesa 17.2.1-0ubuntu1_amd64 but it didn't
help
** Attachment added: "mesa"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1723577/+attachment/4973251/+files/mesa
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is
I don't really understand comment #17-#18 but it looks like nobody has
successfully tested downgrading Mesa yet (per comment #13).
You may have to download and install the previous version manually:
https://launchpad.net/ubuntu/+source/mesa/17.2.1-0ubuntu1/+build/13388627
That's the version
Tried also reverts on :
https://launchpad.net/ubuntu/+source/xserver-xorg-video-ati/1:7.9.0-1/+build/12843201
https://launchpad.net/ubuntu/+source/xorg-server/2:1.19.3-1ubuntu6/+build/13313736
Still boot bug...
Hope I did not miss an instruction which would eliminate the good
direction to solve
I tried to boot from grub on kernels :
4.13.0-12
4.13.0-11
4.12.0-13
4.12.0-12
4.11.0-13
Still have the boot bug.
I also tried to downgrade Mutter :
https://launchpad.net/ubuntu/+source/mutter/3.26.0+20170925~ea214fb-
1ubuntu1/+build/13517498
sudo dpkg -i
amano@amano-desktop:~$ uname -r
4.12.13-041213-generic
It took 3 tries to bring up GDM.
So confirmed that this isn't a kernel regression.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
[code]
amano@amano-desktop:~$ uname -r
4.12.13-041213-generic
[/code]
It took 3 tries to bring up GDM.
So confirmed that this isn't a kernel regression.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
** Attachment removed: "Apt policy mesa"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1723577/+attachment/4972649/+files/Mesa-1710
** Attachment added: "Apt policy mesa"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1723577/+attachment/4972651/+files/Mesa-1710-2
--
You
As suggested in french forum, I looked at the previous version :
https://launchpad.net/ubuntu/+source/mesa/17.2.1-0ubuntu1/+build/13388627
Attached is the file with 'apt policy' results
** Attachment added: "Apt policy mesa"
Timo, i was on 4.13.0.12 when noticing the regression. And reverted back
to 4.13.0.11, which didn't change anything. So I don't think that a
kernel update broke my Wayland.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in
Did you have 4.13 kernel before the upgrade? If not sure, try mainline
4.12 build from
http://kernel.ubuntu.com/~kernel-ppa/mainline/
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
Yes, for me all worked fine until 6th October, on this Friday evening I
did the 17.10 updates of the week, and on 7th morning the start process
was frozen on the "Ubuntu" screen - I'm sure I didn't make the updates
on the 5th, so it could be this Mesa upgrade.
--
You received this bug
The dates in comments #7 and #10 make me suspect the Mesa upgrade that
was released on 5 October.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpad.net/bugs/1723577
Title:
Artful won't start
32 matches
Mail list logo
