MC-WAIT-FOR-NAME(1)
π mc-wait-for-name β the manual page, but make it cute π
okay bestie, sit down, grab a strawberry π, because this one is short and iconic. it's mc-wait-for-name, from the Utilities corner of the manual, and honestly? it does exactly one thing and it does it flawlessly. main character energy, no notes. π
β¨ NAME β¨
mc-wait-for-name β literally just sit there and vibe until a D-Bus name shows up on the session bus. that's it. that's the whole job. π
πΈ SYNOPSIS πΈ
mc-wait-for-name WELL-KNOWN-NAME
and here's the lil glow-up version, the way you'd actually see it written out in a [D-Bus Service] file π¦:
[D-Bus Service]
Name=org.freedesktop.Telepathy.Client.Something
Exec=/usr/bin/mc-wait-for-name org.freedesktop.Telepathy.Client.Something
like, that's the whole vibe. one argument, one job, one slay. β¨
π DESCRIPTION π
so here's the tea: mc-wait-for-name runs until a bus name appears, and then it exits successfully. periodt. π«Ά
why would you even want that? because it's a service-activation helper π. some bus names can't be activated directly, no cap β but the desktop session will hand them over automatically after a while. so instead of standing there refreshing like an iphone on 2% battery, you let mc-wait-for-name hold your spot in the group chat until the name finally pulls up. then it dips, successfully. iconic behaviour. π
π EXIT STATUS π
okay this part actually matters, so lock in π₯:
0β the bus name eventually appeared. yay!! we ate!! π64(EX_USAGE) β invocation error. that means too many or too few arguments, or the bus name you gave wasn't a syntactically valid well-known bus name. bestie. the name has to be well-formed. π69(EX_UNAVAILABLE) βmc-wait-for-namecouldn't connect to the session bus at all. it's not you, it's the bus. π75(EX_TEMPFAIL) β the name didn't show up within a reasonable time. it ghosted. π
ngl, if you're scripting this, 75 is your "try again later" signal β it's a tempfail, not a forever-fail. π«Ά
π OPTIONS π
literally none. there are no additional command-line options. zero. zilch. the options section is giving minimalism and honestly? obsessed. β¨
π BUGS π
the "reasonable time" to wait is currently hard-coded. so there's no dial to turn, no flag to pass, no settings page. the patience level is baked in, like a cake you cannot un-bake. ππ«
Telepathy Β· July 2009 β yeah bestie, this lil page has been serving since 2009 and it's still cute. π thanks for reading, now go wait for your name to appear. π¦π πΈ
π¦ where this page comes from
- alpine 3.24: telepathy-mission-control-doc 5.16.6-r3 Β· LGPL-2.1-or-later
- arch rolling: telepathy-mission-control 5.16.6-4 Β· LGPL-2.1-only
- debian bookworm: telepathy-mission-control-5 1:5.16.5-2 Β· LGPL-2.1-only
- debian trixie: telepathy-mission-control-5 1:5.16.5-2.2+b1 Β· LGPL-2.1-only
- fedora 43: telepathy-mission-control 1:5.16.5-14.fc43 Β· LicenseRef-Callaway-LGPLv2
- fedora 43: telepathy-mission-control 1:5.16.5-14.fc43 Β· LicenseRef-Callaway-LGPLv2
- fedora 44: telepathy-mission-control 1:5.16.5-15.fc44 Β· LicenseRef-Callaway-LGPLv2
- fedora 44: telepathy-mission-control 1:5.16.5-15.fc44 Β· LicenseRef-Callaway-LGPLv2
- opensuse-leap 16.0: telepathy-mission-control 5.16.6-bp160.1.12 Β· LGPL-2.1-only
- opensuse-leap 16.0: telepathy-mission-control 5.16.6-bp160.1.12 Β· LGPL-2.1-only
- opensuse-leap 16.0: telepathy-mission-control 5.16.6-bp160.1.12 Β· LGPL-2.1-only
- opensuse-leap 16.0: telepathy-mission-control 5.16.6-bp160.1.12 Β· LGPL-2.1-only
- ubuntu jammy: telepathy-mission-control-5 1:5.16.5-2ubuntu1 Β· LGPL-2.1-only
- ubuntu noble: telepathy-mission-control-5 1:5.16.5-2.1ubuntu7 Β· LGPL-2.1-only
- ubuntu questing: telepathy-mission-control-5 1:5.16.6-2
- ubuntu resolute: telepathy-mission-control-5 1:5.16.6-2build1 Β· LGPL-2.1-or-later
- ubuntu stonking: telepathy-mission-control-5 1:5.16.6-2build1 Β· LGPL-2.1-or-later
- Copyright Β© 2009 Collabora Ltd. <http://www.collabora.co.uk/>
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms