This is still a bug in Ubuntu 21.04 and 21.10.
--
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/1848534
Title:
[Microsoft Hyper-V guest] System shows graphic artifacts for a moment,
t
Thanks for the reminder! I just realized Ubuntu 20.02 was already
released on 4/23. We should try it.
For the CPU firmware (CPU microcode?) update issue: sorry, it's
completely out of my scope -- I only work on Linux. Hopefully that issue
will be resolved in the near future.
--
You received this
Honestly speaking two notes:
1. forget Ubuntu 19.10 -> there is LTS 20.04
2. after ca. 5 or 6 months Microsoft has not updated firmware for my CPU
in standard Windows Update packages and because of it I'm still not
interested in using HyperV (it's interfering with driver updating
microcode for me
Sorry, I made a typo above: systemd.dsystemd.default_standard_output=kmsg ==>
systemd.default_standard_output=kmsg.
BTW, it looks systemd.show_status=true makes no difference for me. I don't see
any status info during the boot-up time -- not sure if I did something wrong.
--
You received this b
I don't have much knowledge bout systemd, either :-) I just did a "man
systemd" and found the options of systemd. "man systemd" says that we
can use pass these kernel parameters to systemd:
systemd.service_watchdogs=true systemd.show_status=true
systemd.log_level=debug systemd.dsystemd.default_st
Since Alt-SysRq-w gives nothing, I'm sure the long delay is not a
kernel/driver issue but a user space issue. It looks due to some reason
I just can not reproduce the long delay. :-(
In the Hyper-V Virtual Machine Connection window's "View" menu, there is
an item "Enhanced Session". In my Ubuntu 1
I followed your instructions of 4/21 regarding changing kernel
parameters and attaching PuTTY etc. Screenshot of the edited parameters
is next to your email attached (if attachment won't get published, I
will post online). I can send the PuTTY output, but I don't think we
learned anything we didn'
I also tried xrdp mode and the VM booted up to the xrdp login window in
14 seconds, which is faster than the "native Xorg GUI mode" (which needs
30s)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https://bugs.launchpa
Sorry, I did miss this part of your previous reply:
root@stock19:~# systemctl list-jobs
JOB UNIT TYPE STATE
48 setvtrgb.service start waiting
137 system-getty.slice start waiting
1 graphical.target start waiting
102 systemd-update-utmp-runlevel.service start waiting
83 plymouth-quit-wait.servi
To clarify, I say the purple login screen is "more native" because
that's what I get on the monitor of a physically independent machine
(not a VM) running Ubunutu; naturally I do not get an (X)RDP screen on
that machine ever.
--
You received this bug notification because you are a member of Ubunt
You missed that I did include the output of 'systemctl list-jobs' during
the crucial interval of delay.
I will follow your instructions regarding boot parameters etc. and post
results asap.
I expect there is an enormous difference between accessing the VM via
RPD (XRDP) protocol and accessing the
I created a Ubuntu 19.10 VM via "Quick Create..." and still can not
reproduce the long delay of > 1 minute: the VM can boot up to the Xorg
GUI desktop in 26 seconds.
My Windows 10 has the same version info: Version 1909 (OS Build
18363.778).
At the grub screen, can you press 'e' and, manually edi
It looks #48 shows some service is causing the long delay -- can you try
'systemctl list-jobs' to see active jobs, as the "Hint" says? :-)
--
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/
Now we are getting somewhere.
X windows system implicated. Though the 2d video shows how fast the
shortcut boot is, I thought I should get a firm number so I did the
shortcut boot and logged in to get output of 'systemd-analyze critical-
chain' and I got the following very interesting responses, s
I've created a 2m35s desktop video showing a boot of stock 18.04 and
19.10 on my system, posted at https://chaetura.net/ms-
vid1-bug-1848534.webm (18MB, renders in Chrome window for me, or use VLC
to watch).
I've posted a second video showing the shortcut to boot 19.10 quickly
that I described ear
A stray click sent my previous message before I had finished editing it,
and I see no way to edit my post. I will post fully complete/edited
version momentarily. I hope an admin will delete this message and my
prior message to avoid cruft in this thread.
--
You received this bug notification beca
I've created a 2m35s desktop video showing a boot of stock 18.04 and
19.10 on my system, posted at https://chaetura.net/ms-
vid1-bug-1848534.webm (18MB, renders in Chrome window for me, or use VLC
to watch).
I've posted a second video showing the shortcut to boot 19.10 quickly
that I described ear
@msgallery: BTW, you mentioned 'The "restart" button is not functional'
-- actually it is not functional only when we try to click the button by
mouse -- if we press Tab to focus on the button and then press Enter,
the VM should reboot. :-) I'll try to mention this to Hyper-V team, but
I'm not sur
BTW, my Linux kernel version is 5.3.0-46-generic #38-Ubuntu (17:37:05,
3/27/2020).
The "graphic artifact" is somehow caused by the "$vt_hanoff" kernel parameter
(check "cat /proc/cmdline").
If I manually remove the "$vt_hanoff" at the grub screen, I won't see the
"graphic artifact" -- Ubuntu gu
Today I installed a Generation-2 VM (4 virtual CPUS, 4 GB memory) from the this
.iso file:
http://releases.ubuntu.com/19.10/ubuntu-19.10-desktop-amd64.iso.
My host is Win10: Version 1909 (OS Build 18383.720) -- I got the info by
running the built-in "winver.exe" program.
The CPU type is Intel C
This is the screenshot of the graphic artifact mentioned in the previous
comment.
** Attachment added: "graphic_artifact.png"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1848534/+attachment/5352858/+files/graphic_artifact.png
--
You received this bug notification because you are a me
I reproduced this with Win10 x64 up to date on 4/11/2020 and the stock
"quick create" versions of Ubuntu 18.04 and 19.10 as referenced and
selected from the Hyper-V manager. Default options all the way. No
updates installed after initial installation. This machine has AMD Ryzen
7 3800X and 32GB mem
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.
https://bugs.launchpad.net/bugs/1848534
apport info was sent on 18 Oct...
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1848534
Title:
[Microsoft Hyper-
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1848534
Title:
[Microsoft Hyper-V guest] System shows graphic artifacts f
Anybody? Or will be it just ignored ?
(info from #34 looks OK)
--
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/1848534
Title:
[Microsoft Hyper-V guest] System shows graphic artifacts
it's not X to blame, but the one that starts it so moving to gdm3 hoping
that someone would have a clue
** Package changed: xorg-server (Ubuntu) => gdm3 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gdm3 in Ubuntu.
https:/
27 matches
Mail list logo
