© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Hi,
Paride is right, but didn't know about the background.
There are mulitple discussions upstream like:
https:/
https:/
https:/
And the reason is isn't fixed there is that the "new way" that is supported and coded on isn't affected at all anyway.
That might seem odd, but we've considered adding After=dbus.service in the Ubuntu packages when it came up the first time.
https:/
But it turned out that this will break more cases/setups than it will fix.
Therefore eventually even VMWare did ask to NOT set After=dbus.service by default and only published it for the affected as KB article.
This is a fairly complex case and I tried to summarize a bit here:
https:/
Essentially the one way out not breaking other setups is what I outlined therein as (B) which is upstream VMware to split the customization code/service into two and then one can be early and one can be later. But I guess since their new style of customization code doesn't have the issue they never started on that and with every passing month the benefit of doing so gets smaller.
Never the less - AFAIU the case - if we want to get this resolved we need to ring bells and whistles at upstream.
... This is one of the cases that makes me sad, I want to help but I cant :-/ ...
Marking as a duplicate to 1793715