Yesterday at work:
me: "Codex, figure out why <component> doesn't see <hardware>, even though <hardware> is clearly present on machine."
(left unsaid: component runs in container, other stuff (also in containers) sees hardware fine).
*2 minutes later*
Codex: "You have foo installed at version X (likely from ubuntu repositories), vendor's hardware support matrix page says that <hardware> only supports Foo at versions y+, I advise you to install from official vendor repo. If you run foo, it shows a "hardware not recognized" warning."
Me: "You don't have sudo, write a sh script runnable with sudo."
Codex: "script is at ..."
Me: "./script.sh; reboot"
*2 minutes later*
Oh that worked. Would have taken me hours of debugging otherwise.
The whole thing took about 15 minutes, most of which was installing packages over a slow network connection.

Bri🥰
in reply to JamminJerry • • •JamminJerry
in reply to Bri🥰 • • •Kyle Smith
in reply to JamminJerry • • •JamminJerry
in reply to Kyle Smith • • •Kyle Smith
in reply to JamminJerry • • •Bri🥰
in reply to Kyle Smith • • •Kyle Smith
in reply to Bri🥰 • • •JamminJerry
in reply to Kyle Smith • • •Kyle Smith
in reply to JamminJerry • • •JamminJerry
in reply to Kyle Smith • • •Kyle Smith
in reply to JamminJerry • • •JamminJerry
in reply to Kyle Smith • • •Kyle Smith
in reply to JamminJerry • • •JamminJerry
in reply to Kyle Smith • • •Bri🥰
in reply to JamminJerry • • •Kyle Smith
in reply to Bri🥰 • • •Bri🥰
in reply to Kyle Smith • • •