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
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
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
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
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.
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
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
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.
@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
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
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
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
Hi, I'm using Ubuntu 14.04.2 LTS, is there a .deb package I can
directly dpkg -i?
Or, can I use apt-get install xxx to get the updated correct binary?
Thanks a lot!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in
13 matches
Mail list logo
