** Tags added: cscc
--
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/1794280
Title:
gdm doesn't start on a fresh installation of Cosmic Desktop
To manage notifications about this bug
the bug got fixed in xorg, there is no need to target an xorg fix to
cosmic
** Changed in: xorg-server (Ubuntu Cosmic)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
This bug was fixed in the package gdm3 - 3.30.1-1ubuntu5
---
gdm3 (3.30.1-1ubuntu5) cosmic; urgency=medium
* Remove accidental addition of Install/Alias info in gdm service
file.
-- Adam Conrad Tue, 16 Oct 2018 14:06:38 -0600
** Changed in: gdm3 (Ubuntu Cosmic)
Status:
** Merge proposal linked:
https://code.launchpad.net/~3v1n0/ubuntu/+source/gdm3/+git/gdm3/+merge/356861
--
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/1794280
Title:
gdm doesn't
** Changed in: gdm3 (Ubuntu)
Status: Won't Fix => Incomplete
** Changed in: gdm3 (Ubuntu Cosmic)
Status: Won't Fix => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
** Description changed:
ubuntu cosmic desktop 20180925
After installation gdm fails to start and there is only a black screen
with a blinking cursor on the top left of the screen.
- gdm3 can be started manually from a tty
+ gdm3 can be started manually from a tty.
+ Switching to
Could be related to this:
https://gitlab.gnome.org/GNOME/gdm/merge_requests/37
--
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/1794280
Title:
gdm doesn't start on a fresh installation
Hi,
I have the same problem since 3 weeks on a fresh install of Ubuntu
Cosmic, with Wayland session enabled by default : 2/3 of the time, login
screen doesn't appear and screen remains black, pushing power button
makes Ubuntu background visible again and computer stops.
I join some Auth.log
It still seem to crash in my kvm installation:
ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ apt-cache policy
xserver-xorg-video-fbdev
xserver-xorg-video-fbdev:
Installed: 1:0.5.0-1ubuntu1
Candidate: 1:0.5.0-1ubuntu1
Version table:
*** 1:0.5.0-1ubuntu1 500
500
This bug was fixed in the package xserver-xorg-video-fbdev -
1:0.5.0-1ubuntu1
---
xserver-xorg-video-fbdev (1:0.5.0-1ubuntu1) cosmic; urgency=medium
* revert-ae0aeffae665746.diff: Revert a commit which broke using grub
with gfxpayload=keep. (LP: #1794280)
-- Timo Aaltonen
** Also affects: xserver-xorg-video-fbdev (Ubuntu)
Importance: Undecided
Status: New
--
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/1794280
Title:
gdm doesn't start on a
@jibel, as a workaround can you please test if switching VTs kicks the
machine into action? Just Alt+F2, Alt+F1, and maybe then the login
screen will appear. If that works for you then maybe we can declare bug
1795637 a duplicate of this one.
--
You received this bug notification because you are
well, bisected already, will discuss with upstream tomorrow
--
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/1794280
Title:
gdm doesn't start on a fresh installation of Cosmic Desktop
the issue seen with kvm -vga std is a regression in x-x-v-fbdev 0.5.0,
same thing happens on bionic if that version is used there. It doesn't
have a huge number of commits, so it should be easy to bisect.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
I've moved linux/kmod tasks to enable bochs-drm to bug 1795857
** Changed in: linux (Ubuntu Cosmic)
Status: Confirmed => Invalid
** Changed in: kmod (Ubuntu Cosmic)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: kmod (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
Hi - new here, can confirm that this issue also occurs when logging out.
Black screen and hardware completely unresponsive. How can I contribute
my system details?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
** Package changed: xorg (Ubuntu Cosmic) => xorg-server (Ubuntu Cosmic)
--
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/1794280
Title:
gdm doesn't start on a fresh installation of
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu Cosmic)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
and compared to Debian, our kernel doesn't seem to enable bochs-drm
because of an old bug
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648
which probably should be re-enabled by now
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux
while enabling bochs-drm just works around the actual bug, I think it's
best for cosmic at this stage
--
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/1794280
Title:
gdm doesn't start
and again comparing to Debian, it doesn't have efifb messing around at
any stage, though it's enabled in the kernel config
--
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/1794280
Title:
The difference between live-image and installed system is that the live-
image session doesn't have /dev/fb0 around while an installed system
does (by efifb). I've no idea why that is.
but for some reason fbdev fails to use that device set up by efifb
--
You received this bug notification
** Changed in: xorg (Ubuntu Cosmic)
Importance: Undecided => 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/1794280
Title:
gdm doesn't start on a fresh installation of
Ah, one more thing to notice, if starting in recovery mode from grub,
and then resuming the run, it was always working (with std vga too).
Thus this looks like a race in initializing the things that xorg needs
to initialize vbe driver
** Changed in: gdm3 (Ubuntu)
Status: Confirmed =>
FYI to reproduce I've done this:
# Create the disk
qemu-img create -f qcow2 /tmp/disk.qcow2 10G
# Boot from the iso and install
kvm -drive if=virtio,file=/tmp/disk.qcow2 -m 4096 -cdrom
cosmic-desktop-amd64.iso -boot once=d -vga std
# After install... Then run with just:
kvm -drive
S... Running from kvm itself it seems that this is reproducible but
seems related to some lower level issue (both using sil's command and
adding -vga qxl):
journalctl: https://paste.ubuntu.com/p/rdkvsqs8Rs/ (with vga
https://paste.ubuntu.com/p/vJsWbvwdDR/)
xorg.log:
Jean-Baptiste, that's what I did... It's the 4th time now. But still, no
way to reproduce here (in a bionic host, if that matters).
Any kvm config I should set?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
** Tags added: rls-cc-incoming
** Tags removed: rls-cc-incoming
** Tags added: rls-cc-tracking
--
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/1794280
Title:
gdm doesn't start on a
** Description changed:
ubuntu cosmic desktop 20180925
After installation gdm fails to start and there is only a black screen
with a blinking cursor on the top left of the screen.
+
+ gdm3 can be started manually from a tty
+
+ When this issue happens there is a plymouth crash reported
There is also the crash reported in bug 1794292 when this happens. Not
sure if it's related or not
--
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/1794280
Title:
gdm doesn't start on
@Marco, can you try to deselect "Download updates" and select "Minimal
installation"?
--
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/1794280
Title:
gdm doesn't start on a fresh
Still I can't find a way to reproduce this here...
Using that command fails here as probably my user isn't part of libvirtd
or something similar (I'm getting qemu-system-x86_64: failed to
initialize KVM: Permission denied).
While installing from virt-manager seem to work properly.
If you've
I have reproduced it running the beta image on a local kvm instance. Command
line used:
kvm -cdrom cosmic-desktop-amd64.iso -drive if=virtio,file=hdd.qcow2 -m 2048
-boot c
Got the black screen + blinking cursor on first boot. Trying to see if
gdm will eventually start.
--
You received this
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm3 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1794280
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs,
reproduced again.
** Changed in: gdm3 (Ubuntu Cosmic)
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/1794280
Title:
gdm doesn't start on a fresh
Lowering because it is not reproducible. It seems that first boot takes
a lot of time but eventually gdm will start.
** Changed in: gdm3 (Ubuntu Cosmic)
Importance: Critical => High
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to
** Changed in: gdm3 (Ubuntu Cosmic)
Importance: Undecided => 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/1794280
Title:
gdm doesn't start on a fresh installation of
marco's going to look at this
for what it's worth, I tried with today's daily and didn't manage to
reproduce (virt-manager/qemu, cosmic host, qxl)
** Changed in: gdm3 (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Also affects: gdm3 (Ubuntu Cosmic)
Importance:
journal from a failed boot
** Attachment added: "journal.log"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1794280/+attachment/5192752/+files/journal.log
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
43 matches
Mail list logo
