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, shell
dialogue copied below. The same processes (I would assume) are hanging
for 1m44s, but the shortcut somehow allows the user to log in while
waiting for them to finish (as well as solving the other problems of
clipboard and screen size, which seem to go with the more primitive
login screen). Whether those processes should take 1m44s or not, I don't
know, maybe it is normal, but the user should be able to log in before
they are complete, as I can do with shortcut boot. If those processes
are taking inordinately long, then shortcut boot gives opportunity to
log in and catch them as they struggle, as seen below. The time I had to
wait to get the critical-chain result was about as long as I had to wait
to log in at all, under stock 19.10 without shortcut-boot procedure:
wift@stock19:~$ sudo -i
[sudo] password for swift:
root@stock19:~# systemd-analyze critical-chain
Bootup is not yet finished
(org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0).
Please try again later.
Hint: Use 'systemctl list-jobs' to see active jobs
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.service start running
2 multi-user.target start waiting
6 jobs listed.
root@stock19:~# systemd-analyze critical-chain
Bootup is not yet finished
(org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0).
Please try again later.
Hint: Use 'systemctl list-jobs' to see active jobs
root@stock19:~# systemd-analyze critical-chain
Bootup is not yet finished
(org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0).
Please try again later.
Hint: Use 'systemctl list-jobs' to see active jobs
root@stock19:~# systemd-analyze critical-chain
Bootup is not yet finished
(org.freedesktop.systemd1.Manager.FinishTimestampMonotonic=0).
Please try again later.
Hint: Use 'systemctl list-jobs' to see active jobs
root@stock19:~# date
Sun 19 Apr 2020 10:50:27 PM EDT
root@stock19:~# systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @1min 44.881s
└─multi-user.target @1min 44.881s
└─xrdp.service @1.496s +1.036s
└─xrdp-sesman.service @1.474s +20ms
└─network.target @1.470s
└─NetworkManager.service @1.381s +88ms
└─dbus.service @1.379s
└─basic.target @1.375s
└─sockets.target @1.375s
└─snapd.socket @1.373s +1ms
└─sysinit.target @1.372s
└─systemd-timesyncd.service @1.175s +196ms
└─systemd-tmpfiles-setup.service @1.160s +10ms
└─local-fs.target @1.158s
└─home-swift-shared\x2ddrives.mount @11.731s
└─local-fs-pre.target @177ms
└─lvm2-monitor.service @116ms +61ms
└─dm-event.socket @115ms
└─system.slice @110ms
└─-.slice @110ms
root@stock19:~#
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1848534
Title:
[Microsoft Hyper-V guest] System shows graphic artifacts for a moment,
then text cursor for about minute and then starts
Status in gdm3 package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
AFter upgrade system shows graphic artefacts for a moment and then
text cursor for about minute (it looks like hanged) and then starts.
In 19.04 startup required 1 or 2 seconds.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ubuntu-release-upgrader-core 1:19.10.15
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 17 17:42:27 2019
InstallationDate: Installed on 2019-07-04 (104 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: dist-upgrade
UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
VarLogDistupgradeLspcitxt:
VarLogDistupgradeXorgFixuplog:
INFO:root:/usr/bin/do-release-upgrade running
INFO:root:No xorg.conf, exiting
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
DistUpgraded: 2019-10-17 17:03:47,139 DEBUG Running PostInstallScript:
'./xorg_fix_proprietary.py'
DistroCodename: eoan
DistroRelease: Ubuntu 19.10
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
InstallationDate: Installed on 2019-07-04 (105 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
IwConfig:
eth0 no wireless extensions.
lo no wireless extensions.
Lspci:
Lsusb: Error: command ['lsusb'] failed with exit code 1:
MachineType: Microsoft Corporation Virtual Machine
Package: xorg-server (not installed)
ProcFB: 0 hyperv_fb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic
root=UUID=17409d40-25e9-4051-9fd9-758e2a02ebc3 ro quiet splash
video=hyperv_fb:1900x900 elevator=noop vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
RelatedPackageVersions:
linux-restricted-modules-5.3.0-18-generic N/A
linux-backports-modules-5.3.0-18-generic N/A
linux-firmware 1.183
RfKill:
Tags: eoan ubuntu
Uname: Linux 5.3.0-18-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/30/2019
dmi.bios.vendor: Microsoft Corporation
dmi.bios.version: Hyper-V UEFI Release v4.0
dmi.board.asset.tag: None
dmi.board.name: Virtual Machine
dmi.board.vendor: Microsoft Corporation
dmi.board.version: Hyper-V UEFI Release v4.0
dmi.chassis.asset.tag: 2831-3616-6111-5725-4803-1162-28
dmi.chassis.type: 3
dmi.chassis.vendor: Microsoft Corporation
dmi.chassis.version: Hyper-V UEFI Release v4.0
dmi.modalias:
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:
dmi.product.family: Virtual Machine
dmi.product.name: Virtual Machine
dmi.product.sku: None
dmi.product.version: Hyper-V UEFI Release v4.0
dmi.sys.vendor: Microsoft Corporation
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1848534/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
