Comment 22 for bug 1841826

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 <email address hidden>
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
>