** Tags added: amdgpu
** Summary changed:
- Artfull won't start with wayland activated
+ Artful won't start with Wayland activated
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723577
Title:
Artf
** Tags added: ubuntu-fr-artful
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723577
Title:
Artfull won't start with wayland activated
To manage notifications about this bug go to:
https://bugs.la
Xavier , as a workaround you can use the option nomodeset as boot option
and then disable wayland in custom.conf to start with xorg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723577
Title:
Artfu
Same here, all worked fine until 6th October, since 7th impossible to
boot : screen stays frozen at the Ubuntu logo step, nothing works (even
Ctrl Alt F1).
Last line says "Started User Manager for UID 121"
lspci -nn | grep VGA
07:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc.
If I get past Plymouth and into GDM (I have to try 4 times to succeed),
I can log into the “Ubuntu“ session reliably. So I think that this bug
is rather a GDM one than a gnome-shell one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Rather a GDM bug. I it doesn't get stuck on Plymouth, it starts up the
“Ubuntu“ gnome-shell session reliably for me.
** Package changed: gnome-shell (Ubuntu) => gdm3 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
For me it worked reliably the whole development cycle until the week
leading up to the 7th of October. It is borked just for about a week
now. On the 5th of October I remember it being fine, it was borked when
starting Ubuntu up on the morning of October 7th.
Now it seems like a dealbreaker worth
Even after the updates of today (with the new kernel and the gnome-shell
crash fix) the boot splash is getting stuck most of the time (certainly
3 out of 4 tries).
Only switching to the nvidia 340 blob fixes that (then it boots
reliably, not showing Plymouth at all).
I don't think that it is a Pl
More log:
journalctl -b -4 > gdm-wayland-full-log.txt
I had to reboot with sys magic key (alt + print screen + b)
** Attachment added: "full log"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723577/+attachment/4970935/+files/gdm-wayland-full-log.txt
--
You received this bug
With the debug option enabled in /etc/gdm3/custom.conf
journalctl -u gdm.service
** Attachment added: "journalctl log"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1723577/+attachment/4970922/+files/gdm-debug-wayland.log
--
You received this bug notification because you are a
Hi
I have the same problem, or at least the same consequences.
Maybe related to #1723602 ?
I no longer have an Radeon HD 6850 (since 2 weeks ^^), but an RX 560.
I tried weston a little bit to know if it was a wayland problem, but
weston works fine. I can launch some GTK apps on weston (gedit, n
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1723577
Title:
12 matches
Mail list logo
