I would try and figure out what chip is used in the Ultradock; It might have been like the Cypress based one I had, which also worked fine before Ubuntu upgrade, broke, and then worked fine with current Ubuntu after a firmware update to the chip.
If the Ultradock uses a thunderbolt connection, then getting another thunderbolt dock via USB-C adapter, like perhaps maybe the $50 one I was able to upgrade into working state, and testing it, to isolate the software issue to the platform or the dock may be helpful. One outcome would be to say to the Ultradock folks to say that other thunderbolt docks are working, but the Ultradock is not. i.e. Fix the dock to work with modern drivers Another outcome would be that you have 2 thunderbolt docks that behave the same way to add to the issue. i.e. Hey Ubuntu neither of these docks (one of which works on other platforms) is working with my platform Finding a maintainer and sending a generic non-functional dock (or your more expensive entire setup if you are an enterprise that wants this solved) might be a third option, as there is probably a quirk that could be added to the kernel to make it behave like it used to for broken chips, another common practice when the hardware vendors don't come up for air on these issues. Marvell PCI disk controllers with VT-d enabled comes to mind :) On Mon, May 3, 2021 at 12:55 PM Tim Wetzel <1841...@bugs.launchpad.net> wrote: > Agree that this is a serious issue. Like EAB, each of our setups remains > constant: same laptop, dock, display, etc. This issue continues to recur > probably 11 out of 12 startups when docked lid down. Notably, I have > almost never seen it when the laptop is running standalone (out of the > dock). > > Note that I do NOT try to hot dock or undock; these are all full > shutdown/cold starts or manual suspend/later resume. And I rarely > attempt the suspend/resume. That is only if I've been using the machine > stand alone and suspended it, expecting to resume again standalone but > instead wind up at my desk in the office. > > On the rare occasions when it's docked and doesn't suspend at the login > prompt, it will then often throw an error like unable to lock due to > application when it would (abnormally) suspend; and then when it reaches > the desktop the wifi won't work or the dock's usb mouse won't work or > something. Also, on the next restart after that, after suspending and my > pressing the dock power again, I will often get a timing error instead > of video on the external display. I have to then open the laptop lid in > the dock and sometimes can take control to shut down. Other times I have > to force power down at that point. Once that happens, I have to take the > laptop out of the dock, start it stand alone, shut it fully down, dock > it, and try again.... > > PLEASE fix this. Again: this was NOT an issue until the September 2020 > Ubuntu updates to 20.04.1 which I believe also included a kernel update > to address a security vulnerability? In any case, this started shortly > after that. And yes: this should not be happening in an LTS version. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1907687). > https://bugs.launchpad.net/bugs/1841826 > > Title: > Going to sleep instead of logging in while lid closed & external > display > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1841826/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1841826 Title: Going to sleep instead of logging in while lid closed & external display Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I have the above described problem, which seems to be very similar to bug #1716160 - laptop is in docking station and 2 monitors are connected (HDMI, DVI) - If the lid is closed and I boot the laptop I can input my credentials in the login screen and after hitting ENTER the laptop goes to sleep - If I then press the power button of the docking station the laptop wakes up and goes straight to the ubuntu environment w/o any user identification The device is a Lenovo T420 with classic docking station. Ubuntu 18.04.3 LTS. Internal graphics Intel integrated grafics and dedicated Nvidia Quadro NVS 4200M with propriety driver 390.116. Behavior independent of the graphics used. I do not know what to do now since the latest state of bug #1716160 is "fix released" and so I guess it should be part of the ubuntu version I use? Thank you very much. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.1 ProcVersionSignature: Ubuntu 5.0.0-25.26~18.04.1-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 28 20:10:15 2019 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'show-battery-percentage' b'true' b'org.gnome.desktop.interface' b'clock-show-date' b'true' InstallationDate: Installed on 2019-08-13 (14 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=<set> LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1841826/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
